Classifications

• • G—PHYSICS
  • G01—MEASURING; TESTING
  • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
  • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
  • G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
  • G01S5/0252—Radio frequency fingerprinting
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
• • G—PHYSICS
  • G01—MEASURING; TESTING
  • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
  • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
  • G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
  • G01S5/0252—Radio frequency fingerprinting
  • G01S5/02521—Radio frequency fingerprinting using a radio-map
  • G01S5/02524—Creating or updating the radio-map
  • G01S5/02525—Gathering the radio frequency fingerprints
• • H—ELECTRICITY
  • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
  • H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
  • H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
  • H05B47/10—Controlling the light source
  • H05B47/175—Controlling the light source by remote control
  • H05B47/19—Controlling the light source by remote control via wireless transmission

Definitions

• This invention relates generally to the field of computer systems. More particularly, the invention relates to a system and method for accurately sensing user location in an loT system.
• the "Internet of Things” refers to the interconnection of uniquely-identifiable embedded devices within the Internet infrastructure. Ultimately, loT is expected to result in new, wide-ranging types of applications in which virtually any type of physical thing may provide information about itself or its surroundings and/or may be controlled remotely via client devices over the Internet.
• loT development and adoption has been slow due to issues related to connectivity, power, and a lack of standardization.
• one obstacle to loT development and adoption is that no standard platform exists to allow developers to design and offer new loT devices and services.
• a developer In order enter into the loT market, a developer must design the entire loT platform from the ground up, including the network protocols and infrastructure, hardware, software and services required to support the desired loT implementation.
• each provider of loT devices uses proprietary techniques for designing and connecting the loT devices, making the adoption of multiple types of loT devices burdensome for end users.
• Another obstacle to loT adoption is the difficulty associated with connecting and powering loT devices.
• Connecting appliances such as refrigerators, garage door openers, environmental sensors, home security sensors/controllers, etc, for example, requires an electrical source to power each connected loT device, and such an electrical source is often not conveniently located.
• loT devices such as Bluetooth LE are generally short range technologies.
• the loT device will not be able to transmit data to the loT hub (and vice versa). Consequently, techniques are needed which would allow an loT device to provide data to an loT hub (or other loT device) which is out of range.
• FIGS. 1 A-B illustrates different embodiments of an loT system architecture
• FIG. 2 illustrates an loT device in accordance with one embodiment of the invention
• FIG. 3 illustrates an loT hub in accordance with one embodiment of the invention
• FIG. 4A-B illustrate embodiments of the invention for controlling and collecting data from loT devices, and generating notifications
• FIG. 5 illustrates embodiments of the invention for collecting data from loT devices and generating notifications from an loT hub and/or loT service
• FIG. 6 illustrates problems with identifying a user in current wireless lock systems
• FIG. 7 illustrates a system in which loT devices and/or loT hubs are employed to accurately detect the location of a user of a wireless lock system
• FIG. 8 illustrates another embodiment in which loT devices and/or loT hubs are employed to accurately detect the location of a user of a wireless lock system
• FIG. 9 illustrates one embodiment for calibrating a location detection system and detecting a location of a user based on signal strength values
• FIG 10 illustrates a method for implementing a wireless lock system using loT devices and/or loT hubs
• FIG. 11 illustrates one embodiment of a method for calibrating a wireless lock system
• FIG. 12 illustrates one embodiment of the invention for determining the location of a user with signal strength values
• FIG. 13 illustrates another embodiment for calibrating a location detection system and detecting a location of a user based on signal strength values
• FIG. 14 illustrates embodiments of the invention which implements improved security techniques such as encryption and digital signatures
• FIG. 15 illustrates one embodiment of an architecture in which a subscriber identity module (SIM) is used to store keys on loT devices;
• SIM subscriber identity module
• FIG. 16A illustrates one embodiment in which loT devices are registered using barcodes or QR codes
• FIG. 16B illustrates one embodiment in which pairing is performed using barcodes or QR codes
• FIG. 17 illustrates one embodiment of a method for programming a SIM using an loT hub
• FIG. 18 illustrates one embodiment of a method for registering an loT device with an loT hub and loT service
• FIG. 19 illustrates one embodiment of a method for encrypting data to be transmitted to an loT device.
• One embodiment of the invention comprises an Internet of Things (loT) platform which may be utilized by developers to design and build new loT devices and applications.
• a base hardware/software platform for loT devices including a predefined networking protocol stack and an loT hub through which the loT devices are coupled to the Internet.
• one embodiment includes an loT service through which the loT hubs and connected loT devices may be accessed and managed as described below.
• the loT platform includes an loT app or Web application (e.g., executed on a client device) to access and configured the loT service, hub and connected devices.
• existing online retailers and other Website operators may leverage the loT platform described herein to readily provide unique loT functionality to existing user bases.
• Figure 1 A illustrates an overview of an architectural platform on which embodiments of the invention may be implemented.
• the illustrated embodiment includes a plurality of loT devices 101 -105 communicatively coupled over local communication channels 130 to a central loT hub 1 10 which is itself
• the loT service 120 includes an end user database 122 for maintaining user account information and data collected from each user's loT devices.
• the loT devices include sensors (e.g., temperature sensors, accelerometers, heat sensors, motion detectore, etc)
• the database 122 may be continually updated to store the data collected by the loT devices 101 -105.
• the data stored in the database 122 may then be made accessible to the end user via the loT app or browser installed on the user's device 135 (or via a desktop or other client computer system) and to web clients (e.g., such as websites 130 subscribing to the loT service 120).
• the loT app or browser installed on the user's device 135 (or via a desktop or other client computer system) and to web clients (e.g., such as websites 130 subscribing to the loT service 120).
• the loT devices 101 -105 may be equipped with various types of sensors to collect information about themselves and their surroundings and provide the collected information to the loT service 120, user devices 135 and/or external Websites 130 via the loT hub 1 10. Some of the loT devices 101 -105 may perform a specified function in response to control commands sent through the loT hub 1 10. Various specific examples of information collected by the loT devices 101 -105 and control commands are provided below.
• the loT device 101 is a user input device designed to record user selections and send the user selections to the loT service 120 and/or Website.
• the loT hub 1 10 includes a cellular radio to establish a connection to the Internet 220 via a cellular service 1 15 such as a 4G (e.g., Mobile WiMAX, LTE) or 5G cellular data service.
• a cellular service 1 15 such as a 4G (e.g., Mobile WiMAX, LTE) or 5G cellular data service.
• the loT hub 1 10 may include a WiFi radio to establish a WiFi connection through a WiFi access point or router 1 16 which couples the loT hub 1 10 to the Internet (e.g., via an Internet Service Provider providing Internet service to the end user).
• a WiFi radio to establish a WiFi connection through a WiFi access point or router 1 16 which couples the loT hub 1 10 to the Internet (e.g., via an Internet Service Provider providing Internet service to the end user).
• the underlying principles of the invention are not limited to any particular type of communication channel or protocol.
• the loT devices 101 -105 are ultra low-power devices capable of operating for extended periods of time on battery power (e.g., years).
• the local communication channels 130 may be implemented using a low-power wireless communication technology such as Bluetooth Low Energy (LE).
• LE Bluetooth Low Energy
• each of the loT devices 101 -105 and the loT hub 1 10 are equipped with Bluetooth LE radios and protocol stacks.
• the loT platform includes an loT app or Web application executed on user devices 135 to allow users to access and configure the connected loT devices 101 -105, loT hub 1 10, and/or loT service 120.
• the app or web application may be designed by the operator of a Website 130 to provide loT functionality to its user base.
• the Website may maintain a user database 131 containing account records related to each user.
• Figure 1 B illustrates additional connection options for a plurality of loT hubs 1 10-1 1 1 , 190
• a single user may have multiple hubs 1 10-1 1 1 installed onsite at a single user premises 180 (e.g., the user's home or business). This may be done, for example, to extend the wireless range needed to connect all of the loT devices 101 -105.
• a user may be connected via a local communication channel (e.g., Wifi, Ethernet, Power Line
• each of the hubs 1 10-1 1 1 may establish a direct connection to the loT service 120 through a cellular 1 15 or WiFi 1 16 connection (not explicitly shown in Figure 1 B).
• one of the loT hubs such as loT hub 1 10 may act as a "master" hub which provides connectivity and/or local services to all of the other loT hubs on the user premises 180, such as loT hub 1 1 1 (as indicated by the dotted line connecting loT hub 1 10 and loT hub 1 1 1 ).
• the master loT hub 1 10 may be the only loT hub to establish a direct connection to the loT service 120.
• the master loT hub 1 10 is equipped with a cellular communication interface to establish the connection to the loT service 120. As such, all communication between the loT service 120 and the other loT hubs 1 1 1 will flow through the master loT hub 1 10.
• the master loT hub 1 10 may be provided with additional program code to perform filtering operations on the data exchanged between the other loT hubs 1 1 1 and loT service 120 (e.g., servicing some data requests locally when possible).
• the loT service 120 will logically associate the hubs with the user and combine all of the attached loT devices 101 -105 under a single comprehensive user interface, accessible via a user device with the installed app 135 (and/or a browser-based interface).
• the master loT hub 1 10 and one or more slave loT hubs 1 1 1 may connect over a local network which may be a WiFi network 1 16, an Ethernet network, and/or a using power-line communications (PLC) networking (e.g., where all or portions of the network are run through the user's power lines).
• a local network which may be a WiFi network 1 16, an Ethernet network, and/or a using power-line communications (PLC) networking (e.g., where all or portions of the network are run through the user's power lines).
• PLC power-line communications
• each of the loT devices 101 -105 may be interconnected with the loT hubs 1 10-1 1 1 using any type of local network channel such as WiFi, Ethernet, PLC, or Bluetooth LE, to name a few.
• Figure 1 B also shows an loT hub 190 installed at a second user premises 181 .
• loT hubs 190 may be installed and configured to collect data from loT devices 191 -192 at user premises around the world.
• the two user premises 180-181 may be configured for the same user.
• one user premises 180 may be the user's primary home and the other user premises 181 may be the user's vacation home.
• 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).
• 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.
• DRAM dynamic random access memory
• Flash memory non-volatile memory
• a non-volatile memory may be used for persistent storage and a volatile memory may be used for execution of the program code and data at runtime.
• the memory 210 may be integrated within the low power microcontroller 200 or may be coupled to the low power microcontroller 200 via a bus or communication fabric. The underlying principles of the invention are not limited to any particular implementation of the memory 210.
• the program code may include application program code 203 defining an application-specific set of functions to be performed by the loT device 201 and library code 202 comprising a set of predefined building blocks which may be utilized by the application developer of the loT device 101 .
• the library code 202 comprises a set of basic functions required to implement an loT device such as a communication protocol stack 201 for enabling communication between each loT device 101 and the loT hub 1 10.
• the loT device such as a communication protocol stack 201 for enabling communication between each loT device 101 and the loT hub 1 10.
• Bluetooth LE radio and antenna 207 may be integrated within the low power microcontroller 200.
• the underlying principles of the invention are not limited to any particular communication protocol.
• the particular embodiment shown in Figure 2 also includes a plurality of input devices or sensors 210 to receive user input and provide the user input to the low power microcontroller, which processes the user input in accordance with the application code 203 and library code 202.
• each of the input devices include an LED 209 to provide feedback to the end user.
• the illustrated embodiment includes a battery 208 for supplying power to the low power microcontroller.
• a non-chargeable coin cell battery is used.
• an integrated rechargeable battery may be used (e.g., rechargeable by connecting the loT device to an AC power supply (not shown)).
• a speaker 205 is also provided for generating audio.
• the low power microcontroller 299 includes audio decoding logic for decoding a compressed audio stream (e.g., such as an MPEG-4/Advanced Audio Coding (AAC) stream) to generate audio on the speaker 205.
• AAC Advanced Audio Coding
• the low power microcontroller 200 and/or the application code/data 203 may include digitally sampled snippets of audio to provide verbal feedback to the end user as the user enters selections via the input devices 210.
• one or more other/alternate I/O devices or sensors 250 may be included on the loT device 101 based on the particular application for which the loT device 101 is designed.
• an environmental sensor may be included to measure temperature, pressure, humidity, etc.
• a security sensor and/or door lock opener may be included if the loT device is used as a security device.
• these examples are provided merely for the purposes of illustration.
• the underlying principles of the invention are not limited to any particular type of loT device.
• an application developer may readily develop new application code 203 and new I/O devices 250 to interface with the low power microcontroller for virtually any type of loT application.
• the low power microcontroller 200 also includes a secure key store for storing encryption keys for encrypting communications and/or generating signatures.
• the keys may be secured in a subscriber identity module (SIM).
• SIM subscriber identity module
• a wakeup receiver 207 is included in one embodiment to wake the loT device from an ultra low power state in which it is consuming virtually no power.
• the wakeup receiver 207 is configured to cause the loT device 101 to exit this low power state in response to a wakeup signal received from a wakeup transmitter 307 configured on the loT hub 1 10 as shown in Figure 3.
• the transmitter 307 and receiver 207 together form an electrical resonant transformer circuit such as a Tesla coil. In operation, energy is transmitted via radio frequency signals from the transmitter 307 to the receiver 207 when the hub 1 10 needs to wake the loT device 101 from a very low power state.
• the loT device 101 may be configured to consume virtually no power when it is in its low power state because it does not need to continually "listen" for a signal from the hub (as is the case with network protocols which allow devices to be awakened via a network signal). Rather, the microcontroller 200 of the loT device 101 may be configured to wake up after being effectively powered down by using the energy electrically transmitted from the transmitter 307 to the receiver 207.
• the loT hub 1 10 also includes a memory 317 for storing program code and data 305 and hardware logic 301 such as a microcontroller for executing the program code and processing the data.
• a wide area network (WAN) interface 302 and antenna 310 couple the loT hub 1 10 to the cellular service 1 15.
• WAN wide area network
• the loT hub 1 10 may also include a local network interface (not shown) such as a WiFi interface (and WiFi antenna) or Ethernet interface for establishing a local area network communication channel.
• the hardware logic 301 also includes a secure key store for storing encryption keys for encrypting communications and generating/verifying signatures. Alternatively, the keys may be secured in a subscriber identiy module (SIM).
• SIM subscriber identiy module
• a local communication interface 303 and antenna 31 1 establishes local communication channels with each of the loT devices 101 -105.
• the local communication interface 303/antenna 31 1 implements the Bluetooth LE standard.
• the underlying principles of the invention are not limited to any particular protocols for establishing the local communication channels with the loT devices 101 -105.
• the WAN interface 302 and/or local communication interface 303 may be embedded within the same chip as the hardware logic 301 .
• the program code and data includes a communication protocol stack 308 which may include separate stacks for communicating over the local communication interface 303 and the WAN interface 302.
• device pairing program code and data 306 may be stored in the memory to allow the loT hub to pair with new loT devices.
• each new loT device 101 -105 is assigned a unique code which is communicated to the loT hub 1 10 during the pairing process.
• the unique code may be embedded in a barcode on the loT device and may be read by the barcode reader 106 or may be communicated over the local
• the unique ID code is embedded magnetically on the loT device and the loT hub has a magnetic sensor such as an radio frequency ID (RFID) or near field communication (NFC) sensor to detect the code when the loT device 101 is moved within a few inches of the loT hub 1 10.
• RFID radio frequency ID
• NFC near field communication
• the loT hub 1 10 may verify the unique ID by querying a local database (not shown), performing a hash to verify that the code is acceptable, and/or communicating with the loT service 120, user device 135 and/or Website 130 to validate the ID code. Once validated, in one embodiment, the loT hub 1 10 pairs the loT device 101 and stores the pairing data in memory 317 (which, as mentioned, may include non-volatile memory). Once pairing is complete, the loT hub 1 10 may connect with the loT device 101 to perform the various loT functions described herein.
• the organization running the loT service 120 may provide the loT hub 1 10 and a basic hardware/software platform to allow developers to easily design new loT services.
• developers may be provided with a software development kit (SDK) to update the program code and data 305 executed within the hub 1 10.
• the SDK may include an extensive set of library code 202 designed for the base loT hardware (e.g., the low power microcontroller 200 and other components shown in Figure 2) to facilitate the design of various different types of applications 101 .
• the SDK includes a graphical design interface in which the developer needs only to specify input and outputs for the loT device.
• the SDK also includes a library code base to facilitate the design of apps for mobile devices (e.g., iPhone and Android devices).
• the loT hub 1 10 manages a continuous bi-directional stream of data between the loT devices 101 -105 and the loT service 120.
• the loT hub may maintain an open TCP socket to provide regular updates to the user device 135 and/or external Websites 130.
• the specific networking protocol used to provide updates may be tweaked based on the needs of the underlying application. For example, in some cases, where may not make sense to have a continuous bi-directional stream, a simple request/response protocol may be used to gather information when needed.
• both the loT hub 1 10 and the loT devices 101 -105 are automatically upgradeable over the network.
• the loT hub 1 10 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).
• the loT hub 1 10 is powered via A/C power.
• the loT hub 1 10 may include a power unit 390 with a transformer for transforming A/C voltage supplied via an A/C power cord to a lower DC voltage.
• FIG. 4A illustrates one embodiment of the invention for performing universal remote control operations using the loT system.
• a set of loT devices 101 -103 are equipped with infrared (IR) and/or radio frequency (RF) blasters 401 -403, respectively, for transmitting remote control codes to control various different types of electronics equipment including air
• IR infrared
• RF radio frequency
• the loT devices 101 -103 are also equipped with sensors 404-406, respectively, for detecting the operation of the devices which they control, as described below.
• sensor 404 in loT device 101 may be a temperature and/or humidity sensor for sensing the current temperature/humidity and responsively controlling the air conditioner/heater 430 based on a current desired temperature.
• the air conditioner/heater 430 is one which is designed to be controlled via a remote control device (typically a remote control which itself has a temperature sensor embedded therein).
• the user provides the desired temperature to the loT hub 1 10 via an app or browser installed on a user device 135.
• Control logic 412 executed on the loT hub 1 10 receives the current
• 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.
• the loT service 421 may implement control logic 421 to control the electronics equipment 430-432 based on specified user preferences and stored control codes 422.
• loT device 102 in the illustrated example is used to control lighting 431 .
• sensor 405 in loT device 102 may photosensor or photodetector configured to detect the current brightness of the light being produced by a light fixture 431 (or other lighting apparatus).
• the user may specify a desired lighting level (including an indication of ON or OFF) to the loT hub 1 10 via the user device 135.
• the control logic 412 will transmit commands to the IR/RF blaster 402 to control the current brightness level of the lights 431 (e.g., increasing the lighting if the current brightness is too low or decreasing the lighting if the current brightness is too high; or simply turning the lights ON or OFF).
• loT device 103 in the illustrated example is configured to control audiovisual equipment 432 (e.g., a television, A/V receiver, cable/satellite receiver, AppleTVTM, etc).
• Sensor 406 in loT device 103 may be an audio sensor (e.g., a microphone and associated logic) for detecting a current ambient volume level and/or a photosensor to detect whether a television is on or off based on the light generated by the television (e.g., by measuring the light within a specified spectrum).
• sensor 406 may include a temperature sensor connected to the audiovisual equipment to detect whether the audio equipment is on or off based on the detected temperature.
• the control logic 412 may transmit commands to the audiovisual equipment via the IR blaster 403 of the loT device 103.
• the sensor data and commands are sent over the Bluetooth LE channel.
• the underlying principles of the invention are not limited to Bluetooth LE or any other communication standard.
• control codes required to control each of the pieces of electronics equipment are stored in a database 413 on the loT hub 1 10 and/or a database 422 on the loT service 120.
• the control codes may be provided to the loT hub 1 10 from a master database of control codes 422 for different pieces of equipment maintained on the loT service 120.
• the end user may specify the types of electronic (or other) equipment to be controlled via the app or browser executed on the user device 135 and, in response, a remote control code learning module 491 on the loT hub may retrieve the required IR/RF codes from the remote control code database 492 on the loT service 120 (e.g., identifying each piece of electronic equipment with a unique ID).
• the loT hub 1 10 is equipped with an IR/RF interface 490 to allow the remote control code learning module 491 to "learn" new remote control codes directly from the original remote control 495 provided with the electronic equipment.
• the remote control code learning module 491 may interact with the loT hub 1 10 via the app/browser on the user device 135 to teach the loT hub 1 10 the various control codes generated by the original remote control (e.g., increase temperature, decrease temperature, etc).
• the remote control codes may be stored in the control code database 413 on the loT hub 1 10 and/or sent back to the loT service 120 to be included in the central remote control code database 492 (and subsequently used by other users with the same air conditioner unit 430).
• each of the loT devices 101 -103 have an extremely small form factor and may be affixed on or near their respective electronics equipment 430- 432 using double-sided tape, a small nail, a magnetic attachment, etc.
• the loT device 101 For control of a piece of equipment such as the air conditioner 430, it would be desirable to place the loT device 101 sufficiently far away so that the sensor 404 can accurately measure the ambient temperature in the home (e.g., placing the loT device directly on the air conditioner would result in a temperature measurement which would be too low when the air conditioner was running or too high when the heater was running).
• the loT device 102 used for controlling lighting may be placed on or near the lighting fixture 431 for the sensor 405 to detect the current lighting level.
• loT hub 1 10 and/or loT service 120 transmits notifications to the end user related to the current status of each piece of electronics equipment.
• notifications may then be displayed on the display of the user's mobile device 135.
• the loT hub 1 10 and/or loT service 120 may send the user a notification that the air conditioner is not functioning properly.
• the user is not home (which may be detected via motion sensors or based on the user's current detected location), and the sensors 406 indicate that audiovisual equipment 430 is on or sensors 405 indicate that the lights are on, then a notification may be sent to the user, asking if the user would like to turn off the audiovisual equipment 432 and/or lights 431 .
• the same type of notification may be sent for any equipment type.
• the user may remotely control the electronics equipment 430-432 via the app or browser on the user device 135.
• the user device 135 is a touchscreen device and the app or browser displays an image of a remote control with user-selectable buttons for controlling the equipment 430-432.
• the user may open the graphical remote control and turn off or adjust the various different pieces of equipment.
• the user's selections may be forwarded from the loT service 120 to the loT hub 1 10 which will then control the equipment via the control logic 412.
• the user input may be sent directly to the loT hub 1 10 from the user device 135.
• the user may program the control logic 412 on the loT hub 1 10 to perform various automatic control functions with respect to the electronics equipment 430-432.
• the control logic 412 may automatically turn off the electronics equipment if certain conditions are detected. For example, if the control logic 412 detects that the user is not home and that the air conditioner is not functioning, it may automatically turn off the air conditioner. Similarly, if the user is not home, and the sensors 406 indicate that audiovisual equipment 430 is on or sensors 405 indicate that the lights are on, then the control logic 412 may automatically transmit commands via the IR/RF blasters 403 and 402, to turn off the audiovisual equipment and lights, respectively.
• FIG. 5 illustrates additional embodiments of loT devices 104-105 equipped with sensors 503-504 for monitoring electronic equipment 530-531 .
• the loT device 104 of this embodiment includes a temperature sensor 503 which may be placed on or near a stove 530 to detect when the stove has been left on.
• the loT device 104 transmits the current temperature measured by the temperature sensor 503 to the loT hub 1 10 and/or the loT service 120. If the stove is detected to be on for more than a threshold time period (e.g., based on the measured temperature), then control logic 512 may transmit a notification to the end user's device 135 informing the user that the stove 530 is on.
• a threshold time period e.g., based on the measured temperature
• the loT device 104 may include a control module 501 to turn off the stove, either in response to receiving an instruction from the user or automatically (if the control logic 512 is programmed to do so by the user).
• the control logic 501 comprises a switch to cut off electricity or gas to the stove 530.
• the control logic 501 may be integrated within the stove itself.
• 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.
• a motion sensor 504 for detecting the motion of certain types of electronics equipment such as a washer and/or dryer.
• Another sensor that may be used is an audio sensor (e.g., microphone and logic) for detecting an ambient volume level.
• this embodiment may transmit notifications to the end user if certain specified conditions are met (e.g., if motion is detected for an extended period of time, indicating that the washer/dryer are not turning off).
• loT device 105 may also be equipped with a control module to turn off the washer/dryer 531 (e.g., by switching off electric/gas), automatically, and/or in response to user input.
• a first loT device with control logic and a switch may be configured to turn off all power in the user's home and a second loT device with control logic and a switch may be configured to turn off all gas in the user's home.
• loT devices with sensors may then be positioned on or near electronic or gas-powered equipment in the user's home. If the user is notified that a particular piece of equipment has been left on (e.g., the stove 530), the user may then send a command to turn off all electricity or gas in the home to prevent damage.
• the control logic 512 in the loT hub 1 10 and/or the loT service 120 may be configured to automatically turn off electricity or gas in such situations.
• the loT hub 1 10 and loT service 120 communicate at periodic intervals. If the loT service 120 detects that the connection to the loT hub 1 10 has been lost (e.g., by failing to receive a request or response from the loT hub for a specified duration), it will communicate this information to the end user's device 135 (e.g., by sending a text message or app-specific notification).
• FIG. 6 illustrates an example in which a wireless lock 602 is triggered in response to a user with a wireless device 603 approaching from the outside of the door 601 , based on the signal strength of the signal from the wireless device 603.
• the wireless lock 602 may measure the received signal strength indicator (RSSI) from the wireless device 603 and, when it reaches a threshold (e.g., -60dbm), will unlock the door 601 .
• RSSI received signal strength indicator
• RSSI measurement is non-directional.
• the user may move around the home with the wireless device 603 and pass by the wireless lock 602 or garage door opener, thereby causing it to trigger.
• the use of wireless locks which operate based on user proximity detection has been limited.
• FIG. 7 illustrates one embodiment of the invention which an loT hub and/or loT device 710 is used to determine the location of the user with greater accuracy.
• this embodiment of the invention measures signal strength between the wireless device 703 and the loT lock device 702 and also measures signal strength between the wireless device 703 and one or more loT devices/hubs 710 to differentiate between cases where the user is outside the home and inside the home. For example, if the user is a particular distance from the loT lock 702 inside or outside the home, then the signal strength 761 from the position inside the home and signal strength 760 outside the home may be roughly the same. In prior systems, such as illustrated in
• the differences in signal strength measurements 750 and 751 measured between the loT hub/device 710 and the wireless device 703 when the user is outside the home and inside the home, respectively, are used to determine the location of the user.
• the signal strength 750 may be measurably different than the signal strength 751 when the wireless device 703 is at the inside location. While in most cases the signal strength 751 inside the home should be stronger, there may be instances where the signal strength 751 is actually weaker. The important point is that the signal strength may be used to differentiate the two positions.
• the signal strength values 760-761 , 750-751 may be evaluated at the loT hub/device 710 or at the loT lock 702 (if it has the intelligence to perform this
• loT hub 710 may then transmit a lock or unlock command (or no command if already locked/unlocked) to the loT lock 702 over a wireless communication channel 770 (e.g., BTLE) based on the results of the signal strength evaluation.
• a wireless communication channel 770 e.g., BTLE
• the same basic evaluation and result may be performed directly by the loT lock 702 if it is configured with the logic to perform the evaluation (e.g., where the signal strength values are provided to the loT lock 702).
• Figure 8 illustrates another embodiment which is capable of providing greater accuracy, because it utilizes the signal strength values from two loT hubs/devices 710- 71 1 .
• the signal strength 805 is measured between the wireless device 703 and (1 ) loT hub/device 71 1 ; (2) loT hub/device 710; and (3) loT lock 702.
• the wireless device is shown in a single position in Figure 8 for simplicity.
• all of the collected signal strength values are provided to one of the loT hub devices 710-71 1 , which then evaluate the values to determine the location of the user (e.g., inside or outside). If it is determined that the user is outside, then the loT hub/device 710 may send a command to the loT lock 702 to unlock the door. Alternatively, if the loT lock 702 has the logic to perform the evaluation, the loT hubs/devices 710-71 1 may transmit the signal strength values to the loT lock 702 which evaluates the signal strength values to determine the location of the user.
• a calibration module 910 on the loT hub 710 communicates with an app or browser-based code on the wireless device 703 to calibrate the signal strength measurements.
• the system calibration module 910 and/or calibration app may instruct the user to stand in certain locations outside the door and inside the door (e.g., outside 6 ft outside door 1 , 6 ft inside door 1 , 6 ft outside door 2, etc).
• the user may indicate that he/she is in the desired position by selecting a graphic on the user interface.
• the system calibration app and/or system calibration module 910 will then associate the collected signal strength values 900 with each location within a location database 901 on the loT hub/device 710.
• a signal strength analysis module 91 1 uses these values to determine whether to send loT lock commands 950 to lock/unlock the door based on the detected signal strength values.
• four exemplary locations are shown for two different doors: outside door 1 , inside door 1 , outside door 2, and inside door 2.
• the RSSI1 value is associated with the wireless lock and is set to a threshold value of -60dbm.
• the signal strength analysis module 91 1 will not perform its evaluation to determine the location of the user unless the RSSI1 value is at least -60dmb.
• the RSSI2 and RSSI3 values are signal strength values measured between the user's wireless device and two different loT hubs/devices.
• the signal strength analysis module 91 1 compares the current signal strength values 900 measured between the loT hubs/devices and the user's wireless device with the RSSI2/RSSI3 values from the location database 901 . If the current RSSI values are within a specified range of the values specified in the database for RSSI2 (e.g., for loT hub/device 710) and RSSI3 (e.g. for loT hub/device 71 1 ), then the wireless device is determined to be at or near the associated location.
• RSSI2 e.g., for loT hub/device 710
• RSSI3 e.g. for loT hub/device 71 1
• the RSSI2 value associated with the "outside door 1 " location is -90dbm (e.g., based on the measurement made during calibration)
• the RSSI2 comparison may be verified (assuming a specified range of ⁇ 3 dbm).
• the RSSI3 value associated with the "outside door 1 " location is -85dbm (e.g., based on the measurement made during calibration)
• the RSSI3 comparison may be verified.
• the signal strength analysis module 91 1 will send a command 950 to open the lock.
• the system avoids undesirable "unlock" events when the user passes within -60dbm of the loT lock from inside the home, because the RSSI measurements for RSSI2 and RSSI3 are used to differentiate the inside and outside cases.
• the signal strength analysis module 91 1 relies on on RSSI values which provide the greatest amount of differentiation between the inside and outside cases. For example, there may be some instances where the RSSI values for the inside and outside cases are equivalent or very close (e.g., such as the RSSI3 values of -96 dbm and -97 dbm for inside door 2 and outside door 2, respectively). In such a case, the signal strength analysis module will use the other RSSI value to differentiate the two cases.
• the signal strength analysis module 91 1 may dynamically adjust the RSSI ranges used for the comparison when the recorded RSSI values are close (e.g., making the ranges smaller when the measured RSSI values are closer). Thus, while ⁇ 3 dbm is used as a comparison range for the example above, various different ranges may be set for the comparison based on the how close the RSSI measurements are.
• the system calibration module 910 system continues to train the system by measuring dbm values each time the user enters through a door. For example, in response to the user successfully entering the home following the initial calibration, the system calibration module 910 may store additional RSSI values for RSSI2 and RSSI3. In this manner, a range of RSSI values may be stored for each case in the location/signal strength database 901 to further differentiate between the inside and outside cases. The end result is a far more accurate wireless lock system than currently available.
• FIG. 10 A method in accordance with one embodiment of the invention is illustrated in Figure 10. The method may be implemented within the context of the system
• the wireless signals strength between a user device and an loT lock is measured.
• the signal strength is above a specified threshold (i.e., indicating that the user is near the door)
• the wireless signal strength between the user device and one or more loT hubs/devices is measured.
• the collected wireless signal strength values are compared with previously collected and stored signal strength values to determine the location of the user. For example, if the RSSI values are within a specified range of RSSI values when the user was previously outside of the door, then it may be determined that the user is presently outside of the door.
• a determination is made as to whether the user is outside of the door. If so, then at 1005, the door is automatically unlocked using the loT lock.
• a method for calibrating the loT lock system is illustrated in Figure 11.
• the user is asked to stand outside of the door and at 1 102, the wireless signal strength data is collected between the user device and one or more loT devices/hubs.
• the request may be sent to the user via a user app installed on the user's wireless device.
• the user is asked to stand inside of the door and at 1 104, the wireless signal strength data is collected between the user device and the loT
• the signal strength data is stored in a database so that it may be used to compare signal strength values as described herein to determine the user's current location.
• a "map" of different user locations may be compiled. This map may then be used to provide services to the end user, such as directing audio to speakers in the room in which the user is presently located.
• FIG 12 provides an overview of an exemplary system in which RSSI values measured between the wireless device 703 and a plurality of loT devices 1 101 - 1 105 and loT hub 1 1 10 are used to determine whether the user is in Rooms A, B, or C.
• the loT hub 1 1 10 may determine that the user is presently in Room B, as illustrated.
• RSSI measurements between the wireless device 703 and loT devices 1 104-1 105 and loT hub 1 1 10 may then be used to determine that the user is in Room C. While only 3 RSSI measurements 1 121 -1 123 are shown in Figure 12, RSSI measurements may be made between any loT device or loT hub within range of the wireless device 703 to provide greater accuracy.
• the loT hub 1 1 10 may employ triangulation techniques based on RSSI values between itself and the various loT devices 1 101 -1 105 and the wireless device 703 to triangulate the location of the user.
• the RSSI triangle formed between loT device 1 102, the loT hub 1 1 10 and the wireless device 703 may be used to determine the present location of the wireless device 703, based on the RSSI values for each edge of the triangle.
• FIG 13 illustrates the system calibration module 910 which, as in the embodiments described above, communicates with an app or browser-based code on the wireless device 703 to calibrate the signal strength measurements.
• the system calibration module 910 and/or calibration app may instruct the user to stand in different rooms and in certain locations within each room, depending on the applications for which the loT system is being used.
• the user may indicate that he/she is in the desired position by selecting a graphic on the user interface.
• the system calibration app and/or system calibration module 910 will then associate the collected signal strength values 900 with each location within a location database 1301 on the loT hub/device 710.
• a signal strength analysis module 91 1 uses these values to control the various loT devices 1 101 -1 105 around the user's home. For example, if the loT devices 1 101 -1 105 comprise speakers or amplifiers for a home audio system, the signal strength analysis module 91 1 may transmit loT device commands 1302 to control the rooms in which the audio is being played back (e.g., turning on speakers in the room in which the user is present and turning off speakers in other rooms).
• the signal strength analysis module 91 1 may transmit loT device commands 1302 to turn on lights in the room in which the user is present and turn off lights in the other rooms.
• the underlying principles of the invention are not limited to any specific end-user applications.
• RSSI ranges are collected for each room by instructing the user to stand in different positions within the room. For example, for the user's Family Room, RSSI ranges of -99 dbm to -93 dbm, -1 1 1 dbm to -90 dbm and -1 15 dbm to -85 dbm are collected for RSSI1 , RSSI2, and RSSI3, respectively (i.e., collected from three different loT devices/hubs).
• the signal strength analysis module 91 1 When the current position of the wireless device 703 falls within each of these ranges, the signal strength analysis module 91 1 will determine that the user is in the Family Room and potentially send loT device commands 1302 to perform a specified set of functions (e.g., turn on lights, audio, etc). In addition, for specific points within the room, specific RSSI values may be collected. For example, in Figure 13, values of -88 dbm, -99 dbm, and -101 dbm have been collected when the user is sitting on the sofa in the family room. As in the embodiments described above, the signal strength analysis module 91 1 may determine that the user is on the couch if the RSSI values are within a specified range of the stored RSSI values (e.g., within while ⁇ 3 dbm).
• the system calibration module 910 may continue to collect data for the different locations to ensure that the RSSI values remain current. For example, if the user rearranges the Family Room, the position of the couch may move. In this case, the system calibration module 910 may ask the user if the user is currently sitting the couch (e.g., given the similarity of the RSSI values from those stored in the database), and update the signal strength database 1301 with the new values.
• the user's interaction with various types of loT devices may be used to determine the location of the user. For example, if the user's user's interaction with various types of loT devices may be used to determine the location of the user. For example, if the user's
• the lighting system comprises an loT system
• the system may automatically take RSSI measurements.
• the system may capture RSSI measurements and associate the measurements with these locations.
• the system calibration module 910 may collect signal strength values for both User A and User B to be stored in the signal strength database 1301 .
• the signal strength analysis module 91 1 may then identify the current location of Users A and B based on
• comparisons of signal strength measurements and send loT commands 1302 to control loT devices around the home of Users A and B e.g., keeping on lights/speakers in the rooms in which Users A and B are present.
• the wireless device 703 employed in the embodiments of the invention described herein may be a smartphone, tablet, wearable device (e.g., a smartwatch, token on a neckless or bracelet), or any other form of wireless device 703 capable of detecting RSSI values.
• the wireless device 703 communicates with the loT devices 1 101 -1 105 and loT hub 1 1 10 via a short range, low power wireless communication protocol such as Bluetooth LE (BTLE).
• BTLE Bluetooth LE
• the wireless device 703 communicates with the loT hub 1 1 10 via a longer range wireless protocol such as Wifi.
• the RSSI values may be gathered by the wireless device 703 and communicated back to the loT hub 1 1 10 using the longer range protocol.
• each of the individual loT devices 1 101 -1 105 may collect the RSSI values and communicate these values back to the loT hub 1 1 10 via the short range wireless protocol.
• the underlying principles of the invention are not limited to any specific protocol or technique used to collect the RSSI values.
• One embodiment of the invention uses the techniques described herein to locate an ideal position for a wireless extender to extend the range of the loT hub 1 1 10 using the short range wireless protocol. For example, in one embodiment, upon purchasing a new extender the system calibration module 910 will send instructions for the user to move into each of the rooms of the user's home with the wireless extender device (e.g., by sending instructions to the app on the wireless device 703). A connection wizard may also be executed on the wireless device 703 to step the user through the process. Following the instructions sent by the system calibration module 910 or from the wizard, the user will walk into each room and press a button on the wireless device 703.
• the loT hub 1 1 10 will then measure signal strength between itself and the extender and also the signal strength between the extender and all of the other loT devices in the system.
• the system calibration module 910 or wireless device wizard may then provide the user will a prioritized list of the best locations to place the wireless extender (i.e., selecting those locations with the highest signal strength between the wireless extender and the loT hub 1 1 10 and/or between the wireless extender and the loT devices 1 101 -1 105).
• the embodiments of the invention described above provide for fine-tuned location awareness within an loT system not found in current loT systems.
• the GPS system on the wireless device 703 may communicate precise GPS data to be used to provide an accurate map of the user's home which will include GPS data as well as RSSI data for each location.
• 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 14-19 and associated text).
• the keys may be secured in a subscriber identity module (SIM) as discussed below.
• SIM subscriber identity module
• Figure 14 illustrates a high level architecture which uses public key infrastructure (PKI) techniques and/or symmetric key exchange/encryption techniques to encrypt communications between the loT Service 120, the loT hub 1 10 and the loT devices 101 -102.
• PKI public key infrastructure
• Embodiments which use public/private key pairs will first be described, followed by embodiments which use symmetric key exchange/encryption techniques.
• a unique public/private key pair is associated with each loT device 101 -102, each loT hub 1 10 and the loT service 120.
• its public key is provided to the loT service 120 and when a new loT device 101 is set up, it's public key is provided to both the loT hub 1 10 and the loT service 120.
• Various techniques for securely exchanging the public keys between devices are described below.
• all public keys are signed by a master key known to all of the receiving devices (i.e., a form of certificate) so that any receiving device can verify the validity of the public keys by validating the signatures.
• a master key known to all of the receiving devices (i.e., a form of certificate) so that any receiving device can verify the validity of the public keys by validating the signatures.
• each loT device 101 , 102 includes a secure key storage 1401 , 1403, respectively, for security storing each device's private key.
• Security logic 1402, 1304 then utilizes the securely stored private keys to perform the encryption/decryption operations described herein.
• the loT hub 1 10 includes a secure storage 141 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 1412 for using the keys to perform encryption/decryption operations.
• the loT service 120 may include a secure storage 1421 for security storing its own private key, the public keys of various loT devices and loT hubs, and a security logic 1413 for using the keys to encrypt/decrypt communication with loT hubs and devices.
• a secure storage 1421 for security storing its own private key, the public keys of various loT devices and loT hubs, and a security logic 1413 for using the keys to encrypt/decrypt communication with loT hubs and devices.
• the loT hub 1 10 when the loT hub 1 10 receives a public key certificate from an loT device it can verify it (e.g., by validating the signature using the master key as described above), and then extract the public key from within it and store that public key in it's secure key store 141 1 .
• the security logic 1413 encrypts the data/command using the public key of the loT device 101 to generate an encrypted loT device packet. In one embodiment, it then encrypts the loT device packet using the public key of the loT hub 1 10 to generate an loT hub packet and transmits the loT hub packet to the loT hub 1 10.
• the service 120 signs the encrypted message with it's private key or the master key mentioned above so that the device 101 can verify it is receiving an unaltered message from a trusted source.
• the device 101 may then validate the signature using the public key corresponding to the private key and/or the master key.
• symmetric key exchange/encryption techniques may be used instead of public/private key encryption.
• the devices may each be provided with a copy of the same symmetric key to be used for encryption and to validate signatures.
• AES Advanced Encryption Standard
• each device 101 uses a symmetric key implementation to exchange a symmetric key with the loT hub 1 10.
• a secure key provisioning protocol such as the Dynamic Symmetric Key Provisioning Protocol (DSKPP) may be used to exchange the keys over a secure communication channel (see, e.g., Request for Comments (RFC) 6063).
• RRC Request for Comments
• the underlying principles of the invention are not limited to any particular key provisioning protocol.
• the symmetric keys may be used by each device 101 and the loT hub 1 10 to encrypt communications.
• the loT hub 1 10 and loT service 120 may perform a secure symmetric key exchange and then use the exchanged symmetric keys to encrypt communications.
• a new symmetric key is exchanged periodically between the devices 101 and the hub 1 10 and between the hub 1 10 and the loT service 120.
• a new symmetric key is exchanged with each new communication session between the devices 101 , the hub 1 10, and the service 120 (e.g., a new key is generated and securely exchanged for each communication session).
• the service 120 could negotiate a session key with the hub security module 1312 and then the security module 1412 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 1412 before being re-encrypted for transmission to the device 101 .
• a one-time (permanent) installation key may be negotiated between the device 101 and service 120 at installation time.
• the service 120 could first encrypt/MAC with this device installation key, then encrypt/MAC that with the hub's session key.
• the hub 1 10 would then verify and extract the encrypted device blob and send that to the device.
• a counter mechanism is implemented to prevent replay attacks.
• each successive communication from the device 101 to the hub 1 10 may be assigned a continually increasing counter value.
• Both the hub 1 10 and device 101 will track this value and verify that the value is correct in each successive communication between the devices.
• the same techniques may be implemented between the hub 1 10 and the service 120. Using a counter in this manner would make it more difficult to spoof the communication between each of the devices (because the counter value would be incorrect). However, even without this a shared installation key between the service and device would prevent network (hub) wide attacks to all devices.
• the loT hub 1 10 when using public/private key encryption, uses its private key to decrypt the loT hub packet and generate the encrypted loT device packet, which it transmits to the associated loT device 101 .
• the loT device 101 then uses its private key to decrypt the loT device packet to generate the
• each device would encrypt and decrypt with the shared symmetric key. If either case, each transmitting device may also sign the message with it's private key so that the receiving device can verify it's authenticity.
• a different set of keys may be used to encrypt communication from the loT device 101 to the loT hub 1 10 and to the loT service 120.
• the security logic 1402 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 1412 on the loT hub 1 10 may then decrypt the data packets using the loT hub's private key.
• the security logic 1402 on the loT device 101 and/or the security logic 1412 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 1413 on the loT service 120 using the service's private key).
• the device 101 and hub 1 10 may share a symmetric key while the hub and service 120 may share a different symmetric key.
• data/command itself is not encrypted, but a key is used to generate a signature over the data/command (or other data structure). The recipient may then use its key to validate the signature.
• the secure key storage on each loT device 101 is implemented using a programmable subscriber identity module (SIM) 1501 .
• SIM subscriber identity module
• the loT device 101 may initially be provided to the end user with an un-programmed SIM card 1501 seated within a SIM interface 1500 on the loT device 101 .
• the user takes the programmable SIM card 1501 out of the SIM interface 500 and inserts it into a SIM programming interface 1502 on the loT hub 1 10.
• Programming logic 1525 on the loT hub then securely programs the SIM card 1501 to register/pair the loT device 101 with the loT hub 1 10 and loT service 120.
• a public/private key pair may be randomly generated by the programming logic 1525 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 1501 .
• the programming logic 525 may store the public keys of the loT hub 1 10, the loT service 120, and/or any other loT devices 101 on the SIM card 1401 (to be used by the security logic 1302 on the loT device 101 to encrypt outgoing data).
• the new loT device 101 may be provisioned with the loT Service 120 using the SIM as a secure identifier (e.g., using existing techniques for registering a device using a SIM). Following provisioning, both the loT hub 1 10 and the loT service 120 will securely store a copy of the loT device's public key to be used when encrypting communication with the loT device 101 .
• the techniques described above with respect to Figure 15 provide enormous flexibility when providing new loT devices to end users. Rather than requiring a user to directly register each SIM with a particular service provider upon sale/purchase (as is currently done), the SIM may be programmed directly by the end user via the loT hub 1 10 and the results of the programming may be securely communicated to the loT service 120. Consequently, new loT devices 101 may be sold to end users from online or local retailers and later securely provisioned with the loT service 120.
• SIM Subscriber Identity Module
• the underlying principles of the invention are not limited to a "SIM" device. Rather, the underlying principles of the invention may be implemented using any type of device having secure storage for storing a set of encryption keys.
• the embodiments above include a removable SIM device, in one embodiment, the SIM device is not removable but the loT device itself may be inserted within the programming interface 1502 of the loT hub 1 10.
• the SIM is pre-programmed into the loT device 101 , prior to distribution to the end user.
• various techniques described herein may be used to securely exchange encryption keys between the loT hub 1 10/loT service 120 and the new loT device 101 .
• each loT device 101 or SIM 401 may be packaged with a barcode or QR code 1501 uniquely identifying the loT device 101 and/or SIM 1501 .
• the barcode or QR code 1601 comprises an encoded representation of the public key for the loT device 101 or SIM 1001 .
• the barcode or QR code 1601 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 601 may be printed on a separate card (as shown in Figure 16A) or may be printed directly on the loT device itself.
• the loT hub 1 10 is equipped with a barcode reader 206 for reading the barcode and providing the resulting data to the security logic 1012 on the loT hub 1 10 and/or the security logic 1013 on the loT service 120.
• the security logic 1012 on the loT hub 1 10 may then store the public key for the loT device within its secure key storage 101 1 and the security logic 1013 on the loT service 120 may store the public key within its secure storage 1021 (to be used for subsequent encrypted communication).
• the data contained in the barcode or QR code 1601 may also be captured via a user device 135 (e.g., such as an iPhone or Android device) with an installed loT app or browser-based applet designed by the loT service provider.
• a user device 135 e.g., such as an iPhone or Android device
• the barcode data may be securely communicated to the loT service 120 over a secure connection (e.g., such as a secure sockets layer (SSL) connection).
• SSL secure sockets layer
• the barcode data may also be provided from the client device 135 to the loT hub 1 10 over a secure local connection (e.g., over a local WiFi or Bluetooth LE connection).
• the security logic 1002 on the loT device 101 and the security logic 1012 on the loT hub 1 10 may be implemented using hardware, software, firmware or any combination thereof.
• the security logic 1002, 1012 is implemented within the chips used for establishing the local communication channel 130 between the loT device 101 and the loT hub 1 10 (e.g., the Bluetooth LE chip if the local channel 130 is Bluetooth LE).
• the security logic 1002, 1012 is designed to establish a secure execution environment for executing certain types of program code. This may be implemented, for example, by using TrustZone technology (available on some ARM processors) and/or Trusted Execution Technology (designed by Intel).
• TrustZone technology available on some ARM processors
• Trusted Execution Technology designed by Intel.
• the underlying principles of the invention are not limited to any particular type of secure execution technology.
• the barcode or QR code 1501 may be used to pair each loT device 101 with the loT hub 1 10.
• a pairing code embedded within the barcode or QR code 1501 may be provided to the loT hub 1 10 to pair the loT hub with the corresponding loT device.
• Figure 16B illustrates one embodiment in which the barcode reader 206 on the loT hub 1 10 captures the barcode/QR code 1601 associated with the loT device 101 .
• the barcode/QR code 1601 may be printed directly on the loT device 101 or may be printed on a separate card provided with the loT device 101 .
• the barcode reader 206 reads the pairing code from the barcode/QR code 1601 and provides the pairing code to the local communication module 1680.
• the local communication module 1680 is a Bluetooth LE chip and associated software, although the underlying principles of the invention are not limited to any particular protocol standard.
• the pairing code is received, it is stored in a secure storage containing pairing data 1685 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 685.
• the local communication module 1680 of the loT hub 1 10 may use the code as a key to encrypt communications over the local wireless channel with the loT device 101 .
• the local communication module 1590 stores pairing data within a local secure storage device 1595 indicating the pairing with the loT hub.
• the pairing data 1695 may include the pre-programmed pairing code identified in the barcode/QR code 1601 .
• the pairing data 1695 may also include pairing data received from the local communication module 1680 on the loT hub 1 10 required for establishing a secure local communication channel (e.g., an additional key to encrypt communication with the loT hub 1 10).
• the barcode/QR code 1601 may be used to perform local pairing in a far more secure manner than current wireless pairing protocols because the pairing code is not transmitted over the air.
• the same barcode/QR code 1601 used for pairing may be used to identify encryption keys to build a secure connection from the loT device 101 to the loT hub 1 10 and from the loT hub 1 10 to the loT service 120.
• FIG. 17 A method for programming a SIM card in accordance with one embodiment of the invention 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.
• a user receives a new loT device with a blank SIM card and, at 1602, the user inserts the blank SIM card into an loT hub.
• the user programs the blank SIM card with a set of one or more encryption keys.
• the loT hub may randomly generate a
• a programmable device other than a "SIM" card may be used to perform the same functions as the SIM card in the method shown in Figure 17.
• Figure 18 The method may be implemented within the system architecture described above, but is not limited to any particular system architecture.
• a user receives a new loT device to which an encryption key has been pre-assigned.
• the key is securely provided to the loT hub.
• this involves reading a barcode associated with the loT device to identify the public key of a public/private key pair assigned to the device.
• the barcode may be read directly by the loT hub or captured via a mobile device via an app or bowser.
• a secure communication channel such as a Bluetooth LE channel, 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.
• the loT hub may store and protect the key such as Secure Enclaves, Trusted Execution Technology (TXT), and/or Trustzone.
• TXT Trusted Execution Technology
• the key is securely transmitted to the loT service which stores the key in its own secure keystore. It may then use the key to encrypt communication with the loT device.
• the exchange may be implemented using a certificate/signed key.
• the hub 1 10 it is particularly important to prevent modification/addition/ removal of the stored keys.
• FIG. 19 A method for securely communicating commands/data to an loT device using public/private keys is illustrated in Figure 19. The method may be implemented within the system architecture described above, but is not limited to any particular system architecture.
• the loT service encrypts the data/commands using the loT device public key to create an loT device packet. It then encrypts the loT device packet using loT hub's public key to create the loT hub packet (e.g., creating an loT hub wrapper around the loT device packet).
• the loT service transmits the loT hub packet to the loT hub.
• the loT hub decrypts the loT hub packet using the loT hub's private key to generate the loT device packet.
• it transmits the loT device packet to the loT device which, at 1905, decrypts the loT device packet using the loT device private key to generate the data/commands.
• the loT device processes the data/commands.
• 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.
• Embodiments of the invention may include various steps, which have been described above.
• the steps may be embodied in machine-executable instructions which may be used to cause a general-purpose or special-purpose processor to perform the steps.
• these steps may be performed by specific hardware components that contain hardwired logic for performing the steps, or by any combination thereof
• instructions may refer to specific configurations of hardware such as application specific integrated circuits (ASICs) configured to perform certain operations or having a predetermined functionality or software instructions stored in memory embodied in a non-transitory computer readable medium.
• ASICs application specific integrated circuits
• the techniques shown in the figures can be implemented using code and data stored and executed on one or more electronic devices (e.g., an end station, a network element, etc.).
• Such electronic devices store and communicate (internally and/or with other electronic devices over a network) code and data using computer machine-readable media, such as non-transitory computer machine-readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and transitory computer machine-readable
• non-transitory computer machine-readable storage media e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory
• Such electronic devices typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (non-transitory machine- readable storage media), user input/output devices (e.g., a keyboard, a touchscreen, and/or a display), and network connections.
• the coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers).
• the storage device of a given electronic device typically stores code and/or data for execution on the set of one or more processors of that electronic device.
• code and/or data for execution on the set of one or more processors of that electronic device.
• one or more parts of an embodiment of the invention may be implemented using different combinations of software, firmware, and/or hardware.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Radar, Positioning & Navigation (AREA)
• Remote Sensing (AREA)
• Selective Calling Equipment (AREA)
• Position Fixing By Use Of Radio Waves (AREA)

Priority Applications (3)

Applications Claiming Priority (4)

Publications (1)

Family

ID=57007288

Family Applications (1)

Country Status (4)

Cited By (4)

Families Citing this family (3)

Citations (5)

Family Cites Families (12)

• 2016
  • 2016-03-30 JP JP2017551299A patent/JP6800881B2/ja active Active
  • 2016-03-30 KR KR1020177031056A patent/KR102555796B1/ko active Active
  • 2016-03-30 CN CN201680020486.2A patent/CN107430499B/zh active Active
  • 2016-03-30 WO PCT/US2016/025069 patent/WO2016161020A1/en not_active Ceased

Patent Citations (5)

Also Published As

Similar Documents

Legal Events