KR102555796B1 - System and method for accurately detecting user location in IoT system - Google Patents

Abstract

Systems and methods for accurately detecting the location of a wireless device are described. For example, one embodiment of a method may include collecting signal strength data indicative of signal strength between a wireless device and a plurality of IoT devices and/or IoT hubs within a user's home; associating the signal strength data with locations within the user's home and storing the association in a location database; and determining the current location of the wireless device by comparing signal strength data in the database with current signal strength data representing current signal strength between the wireless device and a plurality of IoT devices and/or IoT hubs.

Description

System and method for accurately detecting user location in IoT system

The present invention relates generally to the field of computer systems. More specifically, the present invention relates to a system and method for accurately detecting a user location in an IoT system.

“Internet of Things” refers to the interconnection of uniquely identifiable embedded devices within the Internet infrastructure. Ultimately, the IoT will open up a new and widespread type of application in which virtually any type of physical object can provide information about itself or its surroundings and/or be remotely controlled via a client device over the Internet. expected to create

IoT development and adoption has been slow due to issues related to connectivity, power, and lack of standardization. For example, one obstacle to IoT development and adoption is the lack of any standard platform to allow developers to design and deliver new IoT devices and services. To enter the IoT market, developers must design an entire IoT platform from start to finish, including network protocols and infrastructure, hardware, software and services required to support a desired IoT implementation. As a result, each provider of IoT devices uses proprietary techniques for designing and connecting IoT devices, making adoption of multiple types of IoT devices a burden on end users. Another obstacle to IoT adoption is the difficulty associated with connecting and powering IoT devices. For example, connecting appliances such as refrigerators, garage door openers, environmental sensors, home security sensors/controllers, etc. requires an electrical source to power each connected IoT device, and such an electrical source is often convenient. not located

Another problem that exists is that the radio technologies used to interconnect IoT devices, such as Bluetooth LE, are generally short-range technologies. Thus, if the data collection hub for the IoT implementation is out of range of the IoT device, the IoT device will not be able to transmit data to the IoT hub (and vice versa). As a result, techniques are needed that enable an IoT device to provide data to an IoT hub (or other IoT device) that is out of range.

A better understanding of the present invention may be obtained from the following detailed description in conjunction with the drawings below.
1A and 1B illustrate different embodiments of an IoT system architecture.
2 illustrates an IoT device according to an embodiment of the present invention.
3 illustrates an IoT hub according to an embodiment of the present invention.
4A and 4B illustrate embodiments of the present invention for controlling and collecting data from IoT devices and generating notifications.
5 illustrates embodiments of the present invention for collecting data from IoT devices and generating notifications from an IoT hub and/or IoT service.
6 illustrates the problems associated with identifying a user in current wireless lock systems.
7 illustrates a system in which IoT devices and/or IoT hubs are used to accurately detect the location of a user of a wireless lock system.
8 illustrates another embodiment in which IoT devices and/or IoT hubs are used to accurately detect the location of a user of a wireless lock system.
9 illustrates one embodiment for calibrating a location detection system and detecting a user's location based on signal strength values.
10 illustrates a method for implementing a wireless lock system using IoT devices and/or IoT hubs.
11 illustrates one embodiment of a method for calibrating a wireless lock system.
12 illustrates one embodiment of the present invention for determining a user's location from signal strength values.
13 illustrates another embodiment for calibrating a location detection system and detecting a user's location based on signal strength values.
14 illustrates embodiments of the present invention that implement advanced security techniques such as encryption and digital signatures.
15 illustrates one embodiment of an architecture in which a Subscriber Identity Module (SIM) is used to store keys on an IoT device.
16A illustrates an embodiment in which an IoT device is registered using a barcode or QR code.
16B illustrates an embodiment in which pairing is performed using a barcode or QR code.
17 illustrates one embodiment of a method for programming a SIM using an IoT hub.
18 illustrates an embodiment of a method of registering an IoT device to an IoT hub and an IoT service.
19 illustrates an embodiment of a method of encrypting data to be transmitted to an IoT device.

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

One embodiment of the present invention includes an Internet of Things (IoT) platform that can be used by developers to design and build new IoT devices and applications. In particular, one embodiment includes an underlying hardware/software platform for IoT devices including an IoT hub and a predefined networking protocol stack through which IoT devices are coupled to the Internet. Additionally, one embodiment includes an IoT service through which IoT hubs and connected IoT devices can be accessed and managed as described below. Additionally, one embodiment of the IoT platform includes an IoT app or web application (eg, running on a client device) to access and configure IoT services, hubs, and connected devices. Existing online retailers and other website operators can leverage the IoT platform described herein to easily provide unique IoT capabilities to their existing user base.

1A illustrates an overview of an architectural platform on which embodiments of the present invention may be implemented. In particular, the illustrated embodiment provides a plurality of IoT devices communicatively coupled via a local communication channel 130 to a central IoT hub 110 that is itself communicatively coupled to an IoT service 120 via the Internet 220. It includes devices 101-105. Each of the IoT devices 101 - 105 may be initially paired to the IoT hub 110 (eg, using a pairing technique described below) to enable each of the local communication channels 130 . In one embodiment, the IoT service 120 includes an end user database 122 for maintaining user account information and data collected from each user's IoT device. For example, if the IoT device includes sensors (eg, temperature sensors, accelerometers, thermal sensors, motion detectors, etc.), database 122 continues to store data collected by IoT devices 101-105. can be updated The data stored in the database 122 is then accessed by the end user via an IoT app or browser installed on the user's device 135 (or via a desktop or other client computer system) and (e.g., via the IoT service 120). ) can be made accessible by web clients (such as websites 130 that have subscribed to).

The IoT devices 101 to 105 collect information about themselves and their surroundings, and provide the collected information to the IoT service 120, the user device 135, and/or an external website 130 through the IoT hub 110. Various types of sensors to provide may be mounted. Some of the IoT devices 101 to 105 may perform designated functions in response to a control command transmitted through the IoT hub 110 . Various specific examples of information and control commands collected by the IoT devices 101 - 105 are provided below. In one embodiment described below, IoT device 101 is a user input device designed to record user selections and transmit user selections to IoT services 120 and/or websites.

In one embodiment, IoT hub 110 uses a cellular radio to establish a connection to Internet 220 via cellular service 115 such as 4G (eg, mobile WiMAX, LTE) or 5G cellular data service. include Alternatively or additionally, IoT hub 110 may be a WiFi access point or router 116 that couples IoT hub 110 to the Internet (eg, via an Internet service provider that provides Internet services to end users). ) may include a WiFi radio for establishing a WiFi connection. Of course, it should be noted that the basic principles of the present invention are not limited to any particular type of communication channel or protocol.

In one embodiment, the IoT devices 101-105 are ultra-low power devices that can operate for long periods of time (eg, several years) on battery power. To conserve power, the local communication channel 130 may be implemented using a low power wireless communication technology such as Bluetooth Low Energy (LE). In this embodiment, each of the IoT devices 101 to 105 and the IoT hub 110 are equipped with a Bluetooth LE radio and protocol stack.

As noted, in one embodiment, the IoT platform is a user device to allow a user to access and configure connected IoT devices 101 - 105 , IoT hub 110 , and/or IoT service 120 . (135) includes IoT apps or web applications running on it. In one embodiment, an app or web application may be designed by the operator of website 130 to provide IoT functionality to its user base. As illustrated, the website may maintain a user database 131 containing account records associated with each user.

1B illustrates additional connectivity options for a plurality of IoT hubs 110, 111, 190. In such an embodiment, a single user may have multiple hubs 110, 111 field-installed on a single user premises 180 (eg, the user's home or business). This can be done, for example, to extend the wireless range needed to connect all of the IoT devices 101-105. As indicated, if a user has multiple hubs 110, 111, they may be connected via local communication channels (eg Wifi, Ethernet, power line networking, etc.). In one embodiment, each of the hubs 110, 111 may establish a direct connection to the IoT service 120 via a cellular 115 or WiFi 116 connection (not explicitly shown in FIG. 1B). Alternatively or additionally, one of the IoT hubs, such as IoT hub 110 (as indicated by the dotted line connecting IoT hub 110 and IoT hub 111), such as IoT hub 111 , can act as a “master” hub providing access and/or local service to all of the other IoT hubs on the user premises 180. For example, master IoT hub 110 may be the only IoT hub to establish a direct connection to IoT service 120 . In one embodiment, only the “master” IoT hub 110 is equipped with a cellular communication interface for establishing a connection to the IoT service 120. As such, all communication between the IoT service 120 and other IoT hubs 111 will flow through the master IoT hub 110. In this role, the master IoT hub 110 performs filtering operations on data exchanged between the other IoT hubs 111 and the IoT service 120 (eg servicing some data requests locally, if possible). You may be provided with additional program code to perform.

Regardless of how the IoT hubs 110, 111 are connected, in one embodiment, the IoT service 120 provides a single, comprehensive user interface (and/or browser- base interface) will logically associate the hub with the user and bind all of the attached IoT devices 101 to 105.

In this embodiment, the master IoT hub 110 and one or more slave IoT hubs 111 are connected via a local network, which may be a WiFi network 116, an Ethernet network, and/or using power-line communications (PLC) networking. (eg, where all or part of the network is powered via the user's power line). Additionally, for the IoT hub 110, 111, each of the IoT devices 101 to 105 can connect to the IoT using any type of local network channel, such as WiFi, Ethernet, PLC or Bluetooth LE, to name a few. Hubs 110 and 111 may be interconnected.

FIG. 1B also shows the IoT hub 190 installed in the second user premises 181 . A virtually unlimited number of such IoT hubs 190 may be installed and configured to collect data from IoT devices 191 and 192 at user premises around the world. In one embodiment, two user premises 180, 181 may be configured for the same user. For example, one user premises 180 may be the user's main home and another user premises 181 may be the user's vacation home. In such a case, the IoT service 120 connects the IoT hub 110, 111, 190 with the user under a single comprehensive user interface (and/or browser-based interface) accessible through the user device 135 on which the app is installed. It will logically associate and combine all of the attached IoT devices (101 to 105, 191, 192).

As illustrated in FIG. 2 , an exemplary embodiment of an IoT device 101 includes a memory 210 for storing program code and data 201-203 and a low-power microcontroller for executing the program code and processing the data. Includes (200). Memory 210 may be volatile memory, such as dynamic random access memory (DRAM), or may be non-volatile memory, such as flash memory. In one embodiment, non-volatile memory may be used for persistent storage, and volatile memory may be used for execution of program codes and data at runtime. Memory 210 may also be integrated within low power microcontroller 200 or coupled to low power microcontroller 200 via a bus or communication fabric. The basic principles of the present invention are not limited to any particular implementation of memory 210 .

As illustrated, the program code includes application program code 203 that defines an application-specific set of functions to be performed by IoT device 201 , and predefined ones that can be used by an application developer of IoT device 101 . library code 202 comprising a set of building blocks. In one embodiment, the library code 202 provides the basics required to implement an IoT device, such as the communication protocol stack 201 for enabling communication between each IoT device 101 and the IoT hub 110. It contains a set of functions. As mentioned, in one embodiment, communication protocol stack 201 includes a Bluetooth LE protocol stack. In this embodiment, the Bluetooth LE radio and antenna 207 may be integrated within the low power microcontroller 200. However, the basic principles of the present invention are not limited to any particular communication protocol.

The particular embodiment shown in FIG. 2 also includes a plurality of input devices or sensors 210 for receiving user input and providing user input to a low-power microcontroller, which includes application code 203 and library code User input is processed according to (202). In one embodiment, each of the input devices includes an LED 209 to provide feedback to the end user.

Additionally, the illustrated embodiment includes a battery 208 for powering the low power microcontroller. In one embodiment, a non-rechargeable coin cell battery is used. However, in an alternative embodiment, an integrated rechargeable battery may be used (eg rechargeable by connecting the IoT device to an AC power supply (not shown)).

A speaker 205 for generating audio is also provided. In one embodiment, low-power microcontroller 299 is used to decode audio from a compressed audio stream (e.g., such as an MPEG-4/Advanced Audio Coding (AAC) stream) to generate audio at speaker 205. Contains decoding logic. Alternatively, the low-power microcontroller 200 and/or application code/data 203 may provide a digitally sampled piece of audio to provide language feedback to the end user when the user enters a selection via the input device 210. (snippet) can be included.

In one embodiment, one or more other/alternative I/O devices or sensors 250 may be included on the IoT device 101 based on the specific application for which the IoT device 101 is designed. For example, environmental sensors may be included to measure temperature, pressure, humidity, and the like. If the IoT device is used as a security device, it may include a security sensor and/or a door lock opener. Of course, these examples are provided for illustrative purposes only. The basic principles of the present invention are not limited to any particular type of IoT device. In fact, given the highly programmable nature of the low-power microcontroller 200 loaded with library code 202, application developers can create new application code 203 to interface with the low-power microcontroller for virtually any type of IoT application. ) and new I/O devices 250 can be easily developed.

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 key may be secured in a Subscriber Identity Module (SIM).

In one embodiment, a wake-up receiver 207 is included to wake the IoT device from a very low power state where the IoT device is consuming virtually no power. In one embodiment, the wake-up receiver 207 causes the IoT device 101 to do this in response to a wake-up signal received from the wake-up transmitter 307 configured on the IoT hub 110 as shown in FIG. and is configured to exit a low power state. In particular, in one embodiment, transmitter 307 and receiver 207 together form an electrical resonant transformer circuit such as a Tesla coil. In operation, energy is transmitted from the transmitter 307 to the receiver 207 via a radio frequency signal when the hub 110 needs to wake the IoT device 101 from a very low power state. Because of the energy transfer, IoT device 101 can be configured to consume virtually no power when it is in its low power state, since (as is the case with network protocols that allow devices to be awake via network signals). Because it doesn't have to constantly "listen" to the signal from the hub. Rather, the microcontroller 200 of the IoT device 101 may be configured to wake up after being effectively powered down by using energy electrically transmitted from the transmitter 307 to the receiver 207 .

As illustrated in FIG. 3 , IoT hub 110 also includes hardware logic 301 , such as memory 317 for storing program codes and data 305 , and a microcontroller to execute program codes and process data. ). A wide area network (WAN) interface 302 and antenna 310 couple IoT hub 110 to cellular service 115 . Alternatively, as noted above, IoT hub 110 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, hardware logic 301 also includes a secure key store for storing encryption keys for encrypting communications and generating/verifying signatures. Alternatively, the key may be secured in a Subscriber Identity Module (SIM).

A local communication interface 303 and an antenna 311 establish a local communication channel with each of the IoT devices 101 to 105 . As noted above, in one embodiment, the local communication interface 303/antenna 311 implements the Bluetooth LE standard. However, the basic principles of the present invention are not limited to any particular protocol for establishing a local communication channel with IoT devices 101-105. Although illustrated as separate units in FIG. 3 , WAN interface 302 and/or local communication interface 303 may be embedded within the same chip as hardware logic 301 .

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. Additionally, device pairing program code and data 306 may be stored in memory to allow the IoT hub to pair with a new IoT device. In one embodiment, each new IoT device 101 - 105 is assigned a unique code that is communicated to the IoT hub 110 during the pairing process. For example, the unique code may be embedded in a barcode on the IoT device and may be read by barcode reader 106 or communicated via local communication channel 130 . In an alternative embodiment, a unique ID code is magnetically embedded on the IoT device, and the IoT hub has a radio frequency ID (ID) to detect the code when the IoT device 101 is moved within a few inches of the IoT hub 110. RFID) or near field communication (NFC) sensors.

In one embodiment, once the unique ID is communicated, the IoT hub 110 queries a local database (not shown), performs a hash to verify that the code is acceptable, and/or The unique ID may be verified by communicating with the IoT service 120, user device 135, and/or website 130 to verify the code. Once verified, in one embodiment, IoT hub 110 pairs IoT device 101 and stores pairing data in memory 317 (which, as noted, may include non-volatile memory). . Once pairing is complete, the IoT hub 110 can connect with the IoT device 101 to perform various IoT functions described herein.

In one embodiment, the organization running the IoT service 120 may provide the IoT hub 110 and underlying hardware/software platform to allow developers to easily design new IoT services. In particular, in addition to the IoT hub 110, a developer may be provided with a software development kit (SDK) for updating program codes and data 305 executed in the hub 110. Additionally, for the IoT device 101, the SDK includes the underlying IoT hardware (e.g., the low-power microcontroller 200 shown in FIG. 2 and other Component) may contain an extensive set of library code 202 designed for In one embodiment, the SDK includes a graphical design interface that requires the developer to specify only the inputs and outputs for the IoT device. All the networking code including the communication stack 201 that allows the IoT device 101 to connect to the hub 110 and services 120 is already in place for the developer. Additionally, in one embodiment, the SDK also includes a library code base to facilitate the design of apps for mobile devices (eg, iPhone and Android devices).

In one embodiment, IoT hub 110 manages a continuous bi-directional stream of data between IoT devices 101 - 105 and IoT service 120 . In situations where updates to/from the IoT devices 101 to 105 are required in real time (e.g., the user needs to view the current status of a security device or environmental measurement), the IoT hub sends regular updates to the user device ( 135) and/or maintain an open TCP socket for serving to external websites 130. The specific networking protocol used to provide updates can be fine-tuned based on the needs of the underlying application. For example, in some cases where it may not make sense to have a continuous bi-directional stream, a simple request/response protocol can be used to gather information when needed.

In one embodiment, both IoT hub 110 and IoT devices 101-105 are automatically upgradable over the network. In particular, if a new update is available to the IoT hub 110, it may automatically download and install the update from the IoT service 120. It can first copy the updated code to local memory, run it, and verify the update before replacing the old program code. Similarly, if an update is available to each of the IoT devices 101 - 105 , the update may initially be downloaded by the IoT hub 110 and pushed out to each of the IoT devices 101 - 105 . Then, each IoT device 101 to 105 may apply the update in a manner similar to that described above for the IoT hub and report the result of the update back to the IoT hub 110. If the update is successful, the IoT hub 110 deletes the update from its memory (e.g., so that it can keep checking for new updates to each IoT device) and updates the code installed on each IoT device. version can be recorded.

In one embodiment, IoT hub 110 is powered via A/C power. In particular, the IoT hub 110 may include a power unit 390 having a transformer to transform the A/C voltage supplied through the A/C power cord to a lower DC voltage.

4A illustrates one embodiment of the present invention for performing universal remote control operations using an IoT system. In particular, in this embodiment, the set of IoT devices 101 - 103 includes a variety of different types of electronic equipment including an air conditioner/heater 430 , a lighting system 431 and audiovisual equipment 432 (to name just a few). Infrared (IR) and/or radio frequency (RF) blasters 401 to 403 for transmitting a remote control code to control are mounted, respectively. In the embodiment shown in FIG. 4A , the IoT devices 101 - 103 are also equipped with sensors 404 - 406 respectively for detecting the operation of the devices they control, as described below.

For example, the sensor 404 in the IoT device 101 is a temperature and/or humidity sensor to sense the current temperature/humidity and in response to control the air conditioner/heater 430 based on the current desired temperature. can be In this embodiment, the air conditioner/heater 430 is designed to be controlled via a remote control device (typically a remote control which itself has a built-in temperature sensor). In one embodiment, the user provides the desired temperature to the IoT hub 110 through an app installed on the user device 135 or a browser. The control logic 412 running on the IoT hub 110 receives the current temperature/humidity data from the sensor 404 and, in response, controls the IR/RF blaster 401 according to the desired temperature/humidity. Send a command to (101). For example, if the temperature is lower than the desired temperature, the control logic 412 sends a command to the air conditioner/heater via the IR/RF blaster 401 (e.g., by turning the air conditioner off or turning the heater on) to temperature can be raised. The command may include the necessary remote control code stored in database 413 on IoT hub 110. Alternatively or additionally, IoT service 421 may implement control logic 421 to control electronic equipment 430 - 432 based on specified user preferences and stored control codes 422 .

IoT device 102 of the illustrated example is used to control lighting 431 . In particular, sensor 405 within IoT device 102 may be a photosensor or photodetector configured to detect the current brightness of light produced by lighting fixture 431 (or other lighting device). A user may designate a desired lighting level (including an on or off instruction) to the IoT hub 110 through the user device 135 . In response, the control logic 412 will send a command to the IR/RF blaster 402 to control the current brightness level of the illuminator 431 (e.g., increase the lighting if the current brightness is too low, or Dim the light if the current brightness is too high; simply turn the illuminator on or off).

The illustrated example IoT device 103 is configured to control audiovisual equipment 432 (eg, television, A/V receiver, cable/satellite receiver, AppleTV™, etc.). Sensors 406 within the IoT device 103 are audio sensors (e.g., microphones and associated logic) to detect current ambient volume levels and/or based on light generated by the television (e.g., specified light sensor to detect if the television is on or off (by measuring the light in the 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 user device 135 , control logic 412 may send commands to the audiovisual equipment via IR blaster 403 of IoT device 103 .

It should be noted that the foregoing is merely an illustrative example of one embodiment of the present invention. The basic principles of the present invention are not limited to any particular type of sensor or equipment to be controlled by an IoT device.

In embodiments where IoT devices 101-103 are coupled to IoT hub 110 via a Bluetooth LE connection, sensor data and commands are transmitted over a Bluetooth LE channel. However, the basic principles of the present invention are not limited to Bluetooth LE or any other communication standard.

In one embodiment, control codes required to control each electronic device are stored in database 413 on IoT hub 110 and/or database 422 on IoT service 120 . As illustrated in FIG. 4B , the control code may be provided to IoT hub 110 from a master database of control codes 422 for different equipment maintained on IoT service 120 . The end user can specify the type of electronic (or other) equipment to be controlled through an app or browser running on the user device 135, and in response, the remote control code learning module 491 on the IoT hub provides the IoT service 120 ) in the remote control code database 492 (eg, identifying each electronic device with a unique ID) for the required IR/RF code.

Additionally, in one embodiment, the IoT hub 110 has a remote control code learning module 491 IR that allows it to “learn” new remote control codes directly from the original remote control 495 provided with the electronic equipment. /RF interface 490 is mounted. For example, if the control code for the original remote control provided with the air conditioner 430 is not included in the remote control database, the user interacts with the IoT hub 110 through an app/browser on the user device 135. Thus, various control codes (eg, temperature increase, temperature decrease, etc.) generated by the original remote control may be taught to the IoT hub 110. Once the remote control codes are learned, they can be stored in the control code database 413 on the IoT hub 110 and/or sent back to the IoT service 120 for inclusion in the central remote control code database 492 (and subsequent and used by other users with the same air conditioner unit 430).

In one embodiment, each of the IoT devices 101-103 has an extremely small form factor and is attached to or near their respective electronic equipment 430-432 using double-sided tape, pegs, magnetic attachments, or the like. can be attached For control of equipment such as the air conditioner 430, it would be desirable to place the IoT device 101 far enough away so that the sensor 404 can accurately measure the ambient temperature in the house (e.g. directly on the air conditioner). Deploying IoT devices will result in temperature readings that are either too low when the air conditioner is running or too high when the heater is running). In contrast, an IoT device 102 used to control lighting may have a sensor 405 placed on or near the lighting fixture 431 to detect the current lighting level.

In addition to providing general control functions as described, one embodiment of IoT hub 110 and/or IoT service 120 sends notifications related to the current status of each electronic equipment to the end user. The notification, which may be a text message and/or app specific notification, may then be displayed on the display of the user's mobile device 135 . For example, if the user's air conditioner has been turned on for a long period of time but the temperature has not changed, the IoT hub 110 and/or the IoT service 120 may send a notification to the user that the air conditioner is not functioning properly. The user is not at home (which can be detected via a motion sensor or based on the user's current detected location), sensor 406 indicates that audiovisual equipment 430 is on, or sensor 405 indicates that audiovisual equipment 430 is on. If the illuminator indicates that it is turned on, a notification may be sent to the user asking if the user wants to turn off the audiovisual equipment 432 and/or the illuminator 431 . The same type of notification can be sent for any equipment type.

When the user receives the notification, he/she can remotely control the electronic equipment 430 - 432 via an app or browser on the user device 135 . In one embodiment, user device 135 is a touch screen device, and the app or browser displays an image of a remote control with buttons that a user can select to control equipment 430-432. Upon receiving the notification, the user can open the graphic remote control and turn off or adjust a variety of different equipment. When connected through the IoT service 120, the user's selection may be transmitted from the IoT service 120 to the IoT hub 110, and then the IoT hub 110 controls the equipment through the control logic 412. will be. Alternatively, user input may be sent directly from the user device 135 to the IoT hub 110 .

In one embodiment, a user may program control logic 412 on IoT hub 110 to perform various automatic control functions for electronic equipment 430 - 432 . In addition to maintaining the desired temperature, brightness level, and volume level as described above, the control logic 412 may automatically turn the electronic equipment off when certain conditions are detected. For example, if control logic 412 detects that the user is not at home and the air conditioner is not functioning, it can automatically turn the air conditioner off. Similarly, if the user is not at home and sensor 406 indicates that audiovisual equipment 430 is on or sensor 405 indicates that illuminators are on, control logic 412 will activate IR/RF blaster 403; A command may be automatically transmitted through 402) to turn off the audiovisual equipment and the luminous body respectively.

5 illustrates a further embodiment of an IoT device 104 , 105 equipped with sensors 503 , 504 for monitoring electronic equipment 530 , 531 . In particular, the IoT device 104 of this embodiment includes a temperature sensor 503 that can be placed on or near the stove 530 to detect when the stove is left on. In one embodiment, IoT device 104 transmits the current temperature measured by temperature sensor 503 to IoT hub 110 and/or IoT service 120 . If it is detected that the stove has been on for more than a threshold period of time (eg, based on the measured temperature), the control logic 512 sends a notification to the user that the stove 530 is on, to the end user's device 135 ) can be transmitted. Further, in one embodiment, IoT device 104 controls to turn off the stove, either automatically (if control logic 512 is programmed to do so by the user) or in response to receiving an instruction from the user. module 501. In one embodiment, control logic 501 includes a switch that shuts off electricity or gas to stove 530 . However, in other embodiments, the control logic 501 may be integrated within the stove itself.

5 also illustrates an IoT device 105 having a motion sensor 504 for detecting motion of certain types of electronic equipment, such as a washing machine and/or dryer. Another sensor that may be used is an audio sensor (eg, microphone and logic) to detect the ambient volume level. As with the other embodiments described above, this embodiment provides a notification to the end user when some specified condition is met (eg, motion is detected for an extended period of time, indicating that the washer/dryer has not been turned off). can transmit Although not shown in FIG. 5 , IoT device 105 also includes a control module that turns off washer/dryer 531 automatically and/or in response to user input (eg, by switching off electricity/gas). can be mounted.

In one embodiment, a first IoT device with control logic and switches can be configured to turn off all power in the user's house, and a second IoT device with control logic and switches to turn off all gas in the user's house. can be configured to turn off. The IoT device with the sensor can then be placed on or near electronic or gas powered equipment in the user's home. When a user is notified that certain equipment (eg, stove 530) is left on, the user can send a command to turn off all electricity or gas in the house to prevent damage. Alternatively, control logic 512 within IoT hub 110 and/or IoT service 120 may be configured to automatically turn off electricity or gas in such circumstances.

In one embodiment, IoT hub 110 and IoT service 120 communicate at periodic intervals. When the IoT service 120 detects that it has lost connection to the IoT hub 110 (eg, by not receiving a request or response from the IoT hub for a specified duration), (eg, a text message or will communicate this information to the end user's device 135 (by sending an app-specific notification).

Apparatus and method for accurately detecting user location in IoT system

Current wireless “smart” locks and garage door openers allow an end user to control the lock and/or garage door via a mobile device. To operate these systems, a user must open an app on a mobile device and select an open/unlock or close/lock option. In response, a radio signal is transmitted to a receiver on or coupled to a radio lock or garage door that implements the desired action. Although the discussion below focuses on wireless “locks,” the term “lock” is used herein to refer to standard door locks, wireless garage door openers, and any other device for limiting access to a building or other location. Used extensively.

Some wireless locks attempt to determine when the user is outside the door and trigger an open/unlock function in response. For example, 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 outside a door 601 based on the signal strength of the signal from the wireless device 603. foreshadow For example, wireless lock 602 can measure a received signal strength indicator (RSSI) from wireless device 603 and unlock door 601 when it reaches a threshold (eg, -60 dbm). will be.

One obvious problem with these techniques is that RSSI measurements are non-directional. For example, a user may move around the house with wireless device 603 and pass by wireless lock 602 or garage door opener, causing it to be triggered. For this reason, the use of wireless locks that operate based on user proximity detection has been limited.

7 illustrates one embodiment of the present invention in which an IoT hub and/or IoT device 710 is used to determine a user's location with greater precision. In particular, this embodiment of the present invention measures the signal strength between the wireless device 703 and the IoT lock device 702 and also measures the signal strength between the wireless device 703 and one or more IoT devices/hubs 710. Thus, the case where the user is outside the house and the case where the user is inside the house are distinguished. For example, if the user is at a certain distance from the IoT lock 702 either inside or outside the home, the signal strength 761 from the location inside the home and the signal strength 760 outside the home may be approximately the same. In conventional systems, such as the one illustrated in FIG. 6, there is no way to differentiate between these two cases. However, in the embodiment shown in FIG. 7 , the signal strength measurements 750 and 751 measured between the IoT hub/device 710 and the wireless device 703 when the user is outside and inside the home, respectively. ) are used to determine the location of the user. For example, when wireless device 703 is at an outside location, signal strength 750 can be noticeably different from signal strength 751 when wireless device 703 is at an inside location. Although in most cases the signal strength 751 inside the house should be stronger, there may be cases where the signal strength 751 is actually weaker. An important point is that the signal strength can be used to differentiate between the two locations.

The signal strength values 760, 761, 750, 751 may be evaluated at the IoT hub/device 710 or at the IoT lock 702 (if it has the intelligence to perform this evaluation). The remainder of this discussion is that signal strength evaluation is performed by IoT hub 710, and then IoT hub 710 issues a lock or unlock command via wireless communication channel 770 (e.g., BTLE) based on the results of the evaluation. will be assumed to be able to send to the IoT lock 702 (or not send a command if it is already locked/unlocked). However, if the IoT lock 702 is configured with logic to perform the evaluation (eg, when signal strength values are provided to the IoT lock 702), then the same basic evaluation and result is performed by the IoT lock 702. It should be noted that this can be done directly.

8 illustrates another embodiment that can provide greater precision because it uses signal strength values from two IoT hubs/devices 710 and 711. In this embodiment, signal strength 805 is measured between wireless device 703 and (1) IoT hub/device 711; (2) IoT hub/device 710; and (3) the IoT lock 702. The wireless device is shown in a single location in FIG. 8 for simplicity.

In one embodiment, all of the collected signal strength values are provided to one of the IoT hub devices 710, 711, which then evaluates the values to determine the user's location (eg, inside or outside). If it is determined that the user is outside, the IoT hub/device 710 may send a command to the IoT lock 702 to unlock the door. Alternatively, if IoT lock 702 has logic to perform the evaluation, IoT hubs/devices 710, 711 can send signal strength values to IoT lock 702, which are evaluated to determine the user's location.

As illustrated in FIG. 9 , in one embodiment, calibration module 910 on IoT hub 710 communicates with an app or browser-based code on wireless device 703 to calibrate signal strength measurements. During calibration, the system calibration module 910 and/or the calibration app prompts the user at a location outside the door and within the door (e.g., 6 feet outside of door 1, within 6 feet of door 1, 6 feet of door 2). out of the pits, etc.). The user can indicate that he/she is at the desired location 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 in the location database 901 on the IoT hub/device 710 .

Once signal strength values for different known locations of the user are collected and stored in database 901, signal strength analysis module 911 uses these values to lock/unlock the door based on the detected signal strength values. Determines whether to transmit IoT lock commands 950 for locking. In the embodiment shown in FIG. 9 , four exemplary locations for two different doors are shown: door 1 outside, door 1 inside, door 2 outside and door 2 inside. The RSSI1 value is related to radio lock and is set to a threshold of -60 dbm. Thus, in one embodiment, the signal strength analysis module 911 will not perform its evaluation to determine the user's location unless the RSSI1 value is at least -60 dbm. The RSSI2 and RSSI3 values are the signal strength values measured between the user's wireless device and two different IoT hubs/devices.

Assuming that the RSSI1 threshold is reached, the signal strength analysis module 911 converts the current signal strength values 900 measured between the IoT hubs/devices and the user's wireless device to the RSSI2/RSSI2/ Compare with RSSI3 values. If the current RSSI values are within the specified range of values specified in the database for RSSI2 (e.g., for IoT hub/device 710) and RSSI3 (e.g., for IoT hub/device 711) , the wireless device is determined to be at or near the relevant location. For example, if the current measured signal strength for RSSI2 is -93 dbm to -87 dbm, since the RSSI2 value associated with the "Outside Door 1" location is -90 dbm (e.g., based on measurements made during calibration) , RSSI2 comparisons can be verified (assuming a specified range of ±3 dbm). Similarly, since the RSSI3 value associated with the "Outside Door 1" location is -85 dbm (e.g., based on measurements made during calibration), the current measured signal strength for RSSI3 is -88 dbm to -82 dbm. If so, the RSSI3 comparison can be verified. Thus, if the user is within the -60 dbm value for the IoT lock and within the ranges specified above for RSSI2 and RSSI3, the signal strength analysis module 911 will send a command 950 to open the lock. By comparing different RSSI values in this way, the system avoids undesirable "unlock" events when the user passes within -60 dbm of the IoT lock from inside the house, since RSSI measurements for RSSI2 and RSSI3 are internal and This is because it is used to distinguish between external instances.

In one embodiment, the signal strength analysis module 911 relies on the RSSI values that provide the greatest positive distinction between inner and outer cases. For example, there may be some examples where the RSSI values for the inside and outside cases are equivalent or very similar (e.g., RSSI3 values of -96 dbm and -97 dbm for door 2 inside and door 2 outside, respectively). there is. In such a case, the signal strength analysis module will use different RSSI values to distinguish the two cases. Additionally, in one embodiment, the signal strength analysis module 911 may dynamically adjust the RSSI ranges used for comparison when the recorded RSSI values are similar (e.g., when the measured RSSI values are more similar). make ranges smaller). Thus, while ±3 dbm is used as the comparison range for the example above, a variety of different ranges can be set for comparison based on how similar the RSSI measurements are.

In one embodiment, the system calibration module 910 system continuously trains the system by measuring dbm values each time a user enters through a door. For example, in response to a user successfully entering home after initial calibration, system calibration module 910 may store additional RSSI values for RSSI2 and RSSI3. In this way, various RSSI values can be stored in the location/signal strength database 901 for each instance to further differentiate the inner case from the outer case. The end result is a wireless lock system that is far more precise than currently available.

A method according to one embodiment of the present invention is illustrated in FIG. 10 . The method may be implemented within the context of the system architecture described above, but is not limited to any particular system architecture.

At 1001, wireless signal strength between a user device and an IoT lock is measured. At 1002, if the signal strength exceeds a specified threshold (ie indicating that the user is near a door), at 1002, the wireless signal strength between the user device and one or more IoT hubs/devices is measured. At 1003, the collected wireless signal strength values are compared to 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 out of the door, it may be determined that the user is currently out of the door. At 1004, based on the evaluation, a determination is made as to whether the user is out of the door. If so, at 1005 the door is automatically unlocked using the IoT lock.

A method for calibrating an IoT lock system is illustrated in FIG. 11 . At 1101, the user is requested to stand outside the door, and at 1102, wireless signal strength data is collected between the user device and one or more IoT devices/hubs. As mentioned, the request may be sent to the user via a user app installed on the user's wireless device. At 1103, the user is requested to stand in the door, and at 1104, wireless signal strength data is collected between the user device and the IoT devices/hubs. At 1105, the signal strength data is stored in the database, so it can be used to compare signal strength values as described herein to determine the user's current location.

Note that although a user's home is used herein as an exemplary embodiment, embodiments of the present invention are not limited to consumer applications. For example, these same technologies could be used to provide access to businesses or other types of buildings.

In one embodiment, techniques similar to those described above are used to track the user throughout the user's home. For example, by tracking RSSI measurements between a user's wireless device and various IoT devices/hubs within the user's home, a “map” of different user locations can be aggregated. This map can then be used to provide services to the end user, such as directing audio to speakers in the room in which the user is currently located.

12 shows RSSI values measured between the wireless device 703 and the plurality of IoT devices 1101 to 1105 and the IoT hub 1110 to determine whether the user is in room A, room B, or room C. An overview of an exemplary system used to do so is provided. In particular, based on RSSI values 1121 to 1123 measured between wireless device 703 and IoT hub 1110, IoT device 1103 and IoT device 1102, IoT hub 1110, as illustrated, It may be determined that the user is currently in room B. Similarly, when a user moves into room C, RSSI measurements between wireless device 703 and IoT devices 1104, 1105 and IoT hub 1110 can then be used to determine that the user is in room C. . Although only three RSSI measurements 1121-1123 are shown in FIG. 12, RSSI measurements can be made between any IoT device or IoT hub within range of wireless device 703 to provide greater precision.

In one embodiment, IoT hub 1110 may triangulate the user's location using triangulation techniques based on RSSI values between itself and various IoT devices 1101 - 1105 and wireless device 703. there is. For example, using an RSSI triangle formed between IoT device 1102, IoT hub 1110, and wireless device 703, the current location of wireless device 703 based on the RSSI values for each side of the triangle. can decide

In one embodiment, signal strength values can be collected within each room using calibration techniques similar to those described above. 13 illustrates a system calibration module 910 that communicates with app or browser-based code on the wireless device 703 to calibrate signal strength measurements, as in the preceding embodiments. During calibration, the system calibration module 910 and/or the calibration app may instruct the user to stand in different rooms and at certain locations within each room depending on the applications for which the IoT system is being used. As mentioned above, the user can indicate that he/she is at the desired location 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 in the location database 1301 on the IoT hub/device 710 .

Once the signal strength values for the user's different known locations are collected and stored in the database 1301, the signal strength analysis module 911 uses these values to analyze the various IoT devices 1101-1105 around the user's home. to control For example, if the IoT devices 1101 to 1105 include speakers or amplifiers for a home audio system, the signal strength analysis module 911 provides IoT device commands ( 1302) may be transmitted (eg, turning on speakers in the room where the user is present and turning off speakers in other rooms). Similarly, if the IoT devices 1101 to 1105 include lighting control units, the signal strength analysis module 911 will use IoT device commands to turn on lights in the room where the user is present and turn off lights in other rooms. s 1302 can be transmitted. Of course, the basic principles of the present invention are not limited to any particular end user applications.

As mentioned, one embodiment of system calibration module 910 will collect RSSI data for different points in the room based on the application. In FIG. 13, RSSI ranges for each room are collected by instructing the user to stand at different locations within the room. For example, for a user's living room, RSSI ranges of -99 dbm to -93 dbm, -111 dbm to -90 dbm, and -115 dbm to -85 dbm are collected for RSSI1, RSSI2 and RSSI3, respectively (i.e. collected from 3 different IoT devices/hubs). When the current location of wireless device 703 falls within each of these ranges, signal strength analysis module 911 determines that the user is in a living room and potentially sends IoT device commands 1302 to perform a specified set of functions. (eg lights turn on, audio turn on, etc.). Moreover, for specific points in the room, specific RSSI values may be collected. For example, in FIG. 13 , values of -88 dbm, -99 dbm, and -101 dbm were collected when the user was sitting on a sofa in the living room. As in the foregoing embodiments, signal strength analysis module 911 may determine that a user is on the couch if the RSSI values are within a specified range of stored RSSI values (eg, within ±3 dbm). can Additionally, as in previous embodiments, system calibration module 910 may continue to collect data for different locations to ensure that RSSI values remain current. For example, if the user rearranges the living room, the location of the couch may change. In this case, the system calibration module 910 asks the user if the user is currently sitting on the couch (eg, given the similarity of RSSI values from those stored in the database) and returns the signal strength database 1301 to the new values. can be updated with

In one embodiment, the user's location may be determined using the user's interactions with various types of IoT devices. For example, if a user's refrigerator is equipped with an IoT device, the system can take RSSI measurements when it detects that the user has opened the refrigerator door. Similarly, if the lighting system includes an IoT system, the system can automatically take RSSI measurements when a user adjusts lights in different rooms of a home or business. As another example, when a user interacts with various appliances (eg, washer, dryer, dish dryer), audiovisual equipment (eg, television, audio equipment, etc.) or HVAC systems (eg, thermostat adjustment), the system can obtain RSSI measurements and relate the measurements to these locations.

Although described as a single user in the above embodiments, embodiments of the present invention may be implemented for multiple users. For example, system calibration module 910 may collect signal strength values for both user A and user B to be stored in signal strength database 1301 . The signal strength analysis module 911 then identifies the current location of user A and user B based on the comparisons of the signal strength measurements and sends IoT commands 1302 to IoT devices around the home of users A and user B. (e.g. keep lights/speakers on in rooms where user A and user B are present).

The wireless device 703 used in the embodiments of the invention described herein may be a smartphone, tablet, wearable device (e.g., a smartwatch, a token on a necklace or bracelet), or any device capable of detecting RSSI values. It may be another type of wireless device 703 . In one embodiment, wireless device 703 communicates with IoT devices 1101 - 1105 and IoT hub 1110 via a short range, low power wireless communication protocol such as Bluetooth LE (BTLE). Additionally, in one embodiment, the wireless device 703 communicates with the IoT hub 1110 via a long range wireless protocol such as Wifi. Thus, in this embodiment, RSSI values may be collected by wireless device 703 and communicated back to IoT hub 1110 using a long range protocol. Moreover, each of the individual IoT devices 1101 - 1105 can collect RSSI values and communicate these values back to the IoT hub 1110 via a short range wireless protocol. The basic principles of the present invention are not limited to any particular protocol or technology used to collect RSSI values.

One embodiment of the present invention uses the techniques described herein to find an ideal location for a wireless extender to extend the range of the IoT hub 1110 using a short-range wireless protocol. For example, in one embodiment, when a new expander is purchased, the system calibration module 910 (eg, by sending an instruction to an app on the wireless device 703) determines the user's home health status with the wireless expander device. It will send instructions to move the user into each of the rooms. A connection wizard may also be run on the wireless device 703 to allow the user to go through the process. After instructions are 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 IoT hub 1110 will then measure the signal strength between itself and the expander, and also between the expander and all other IoT devices in the system. The system calibration module 910 or wireless device wizard may then provide the user with a prioritized list of the best locations to place the wireless extender (i.e., between the wireless extender and IoT hub 1110 and/or the wireless extender). and the IoT devices 1101 to 1105 choose those locations with the highest signal strength).

Embodiments of the invention described above provide fine-tuned positional awareness within an IoT system not found in current IoT systems. Additionally, to improve location accuracy, the GPS system on the wireless device 703, in one embodiment, will be used to provide a precise map of the user's home that will include GPS data as well as RSSI data for each location. data can be communicated.

Embodiments for Improved Security

In one embodiment, the low-power microcontroller 200 of each IoT device 101 and the low-power logic/microcontroller 301 of the IoT hub 110 are secured to store encryption keys used by the embodiments described below. Includes a key store (see, eg, FIGS. 14-19 and associated text). Alternatively, the key may be secured in a Subscriber Identity Module (SIM) as discussed below.

14 is a high-level architecture that uses public key infrastructure (PKI) technology and/or symmetric key exchange/encryption technology to encrypt communications between IoT service 120, IoT hub 110, and IoT devices 101, 102. exemplify

An embodiment using a public/private key pair will be described first, followed by an embodiment using a symmetric key exchange/encryption technique. In particular, in embodiments using PKI, a unique public/private key pair is associated with each IoT device 101, 102, each IoT hub 110 and IoT service 120. In one embodiment, when a new IoT hub 110 is set up, its public key is provided to the IoT service 120, and when a new IoT device 101 is set up, its public key is provided to the IoT hub 110. ) and the IoT service 120 are both provided. Various techniques for securely exchanging public keys between devices are described below. In one embodiment, all public keys are signed by a master key that is known (ie, in the form of a certificate) to all receiving devices so that any receiving device can verify the validity of the public key by verifying the signature. Thus, rather than just exchanging the raw public key, these certificates will be exchanged.

As illustrated, in one embodiment, each IoT device 101, 102 includes a secure key store 1401, 1403, respectively, for securely storing the respective device's private key. Security logic 1402, 1304 then uses the securely stored private key to perform the encryption/decryption operations described herein. Similarly, IoT hub 110 has a secure storage 1411 for storing IoT hub private keys and public keys of IoT devices 101, 102 and IoT services 120, as well as encryption/decryption operations using keys. and security logic 1412 for performing. Finally, the IoT service 120 uses a secure storage 1421 for securely storing its own private key, the public keys of various IoT devices and IoT hubs, and the keys to encrypt/encrypt communications with the IoT hubs and devices. Security logic 1413 to decrypt. In one embodiment, when the IoT hub 110 receives the public key certificate from the IoT device, the IoT hub can verify it (eg, by verifying the signature using a master key as described above); It can then extract the public key from within it and store the public key in its secure key storage 1411 .

As an example, in one embodiment, the IoT service 120 sends a command or data (eg, a command to open a door, a request to read a sensor, data to be processed/displayed by the IoT device, etc.) to an IoT device ( When necessary to transmit to 101), the security logic 1413 encrypts the data/commands using the public key of the IoT device 101 to create an encrypted IoT device packet. In one embodiment, the security logic then encrypts the IoT device packet using the public key of the IoT hub 110 to create an IoT hub packet and transmits the IoT hub packet to the IoT hub 110 . In one embodiment, service 120 signs the encrypted message with its private key or the aforementioned master key, so device 101 can verify that it is receiving an unaltered message from a trusted source. . Then, the device 101 can verify the signature using the public key corresponding to the private key and/or the master key. As described above, a symmetric key exchange/encryption technique may be used instead of public/private key encryption. In these embodiments, rather than privately storing one key and providing the corresponding public key to other devices, the devices may each be provided with a copy of the same symmetric key used for encryption and for verifying signatures. One example of a symmetric key algorithm is the Advanced Encryption Standard (AES), but the principles underlying the present invention are not limited to any type of specific symmetric key.

Using a symmetric key implementation, each device 101 enters into a secure key exchange protocol to exchange a symmetric key with the IoT hub 110 . A secure key provisioning protocol, such as Dynamic Symmetric Key Provisioning Protocol (DSKPP), may be used to exchange keys over a secure communication channel (see, for example, Request for Comments (RFC) 6063). However, the basic principles of the present invention are not limited to any particular key provisioning protocol.

Once the symmetric key is exchanged, the symmetric key can be used by each device 101 and IoT hub 110 to encrypt communications. Similarly, IoT hub 110 and IoT service 120 may perform a secure symmetric key exchange and then use the exchanged symmetric key to encrypt communications. In one embodiment, new symmetric keys are periodically exchanged between device 101 and hub 110 and between hub 110 and IoT service 120 . In one embodiment, a new symmetric key is exchanged between device 101, hub 110 and service 120 with each new communication session (e.g., a new key is generated and during each communication session safely exchanged). In one embodiment, if the security module 1412 in the IoT hub is trusted, the service 120 can negotiate a session key with the hub security module 1312, and then the security module 1412 can ) to negotiate a session key. Messages from service 120 will then be decrypted and verified in hub security module 1412 before being re-encrypted for transmission to device 101 .

In one embodiment, a one-time (permanent) installation key may be negotiated between device 101 and service 120 at installation time to prevent compromise on hub security module 1412 . When sending a message to device 101, service 120 may first encrypt/MAC with this device installed key and then encrypt/MAC with the hub's session key. Hub 110 will then verify and extract the encrypted device blob and send it to the device.

In one embodiment of the invention, a counter mechanism is implemented to prevent replay attacks. For example, each successive communication from device 101 to hub 110 (or vice versa) may be assigned an ever-increasing counter value. Both hub 110 and device 101 will track this value and verify that this value is correct at each successive communication between devices. The same technique may be implemented between hub 110 and service 120 . Using a counter in this way will make it more difficult to spoof the communication between the respective devices (because the counter value will be inaccurate). However, even without this, a shared installation key between service and device would prevent network (hub) wide attacks on all devices.

In one embodiment, when using public/private key encryption, IoT hub 110 uses its private key to decrypt IoT hub packets and generate encrypted IoT device packets, which are sent to associated IoT devices 101. send. The IoT device 101 then decrypts the IoT device packet using its private key to generate commands/data originating from the IoT service 120 . The IoT device may then process data and/or execute commands. With symmetric encryption, each device will encrypt and decrypt using a shared symmetric key. In either case, each sending device can also sign the message with its private key, so the receiving device can verify its authenticity.

A different set of keys may be used to encrypt the communication from the IoT device 101 to the IoT hub 110 and to the IoT service 120 . For example, using a public/private key arrangement, in one embodiment, the security logic 1402 on the IoT device 101 uses the public key of the IoT hub 110 to transmit to the IoT hub 110. Encrypt data packets. Security logic 1412 on IoT hub 110 can then use the IoT hub's private key to decrypt the data packet. Similarly, security logic 1402 on IoT device 101 and/or security logic 1412 on IoT hub 110 use the public key of IoT service 120 to transmit data packets to IoT service 120. can be encrypted (the data packet can then be decrypted by the security logic 1413 on the IoT service 120 using the service's private key). When using symmetric keys, device 101 and hub 110 can share one symmetric key, while hub and service 120 can share different symmetric keys.

Although certain specific details have been set forth in the above description, it should be noted that the basic principles of the present invention may be implemented using a variety of different cryptographic techniques. For example, while some of the embodiments discussed above use asymmetric public/private key pairs, alternative embodiments can securely connect various IoT devices (101, 102), IoT hubs (110) and IoT services (120). You can use symmetric keys that are exchanged. Moreover, in some embodiments, the data/commands themselves are not encrypted, but a key is used to create a signature for the data/commands (or other data structures). The recipient can then verify the signature using its key.

As illustrated in FIG. 15 , in one embodiment, secure key storage on each IoT device 101 is implemented using a programmable subscriber identity module (SIM) 1501 . In this embodiment, the IoT device 101 may initially be provided to an end user with an unprogrammed SIM card 1501 seated within a SIM interface 1500 on the IoT device 101 . To program a SIM with one or more sets of cryptographic keys, a user takes a programmable SIM card 1501 from SIM interface 500 and inserts it into SIM programming interface 1502 on IoT hub 110. The programming logic 1525 on the IoT hub then securely programs the SIM card 1501 to register/pair the IoT device 101 to the IoT hub 110 and the IoT service 120 . In one embodiment, a public/private key pair may be randomly generated by programming logic 1525, and then the public key of the pair may be stored in the secure storage device 411 of the IoT hub, while the private key may be may be stored within the programmable SIM 1501. In addition, the programming logic 525 can store the public key of the IoT hub 110, the IoT service 120 and/or any other IoT device 101 (by the security logic 1302 on the IoT device 101 the outgoing data can be stored on the SIM card 1401 so that it can be used to encrypt . Once the SIM 1501 is programmed, the new IoT device 101 can be provisioned with the IoT service 120 using the SIM as a secure identifier (eg, using existing techniques for registering devices using the SIM). It can be. After provisioning, both IoT hub 110 and IoT service 120 will securely store a copy of the IoT device's public key to be used when encrypting communications with IoT device 101 .

The techniques described above with respect to FIG. 15 provide tremendous flexibility when providing new IoT devices to end users. Rather than requiring users to register each SIM directly with a specific service provider at the time of sale/purchase (as is currently done), SIMs can be directly programmed by the end user via the IoT hub 110 and require less programming. The result can be securely communicated to the IoT service 120. As a result, the new IoT device 101 can be sold to an end user either online or from a local retailer, and later securely provisioned with the IoT service 120 .

Although registration and encryption techniques are described above in the specific context of a SIM (Subscriber Identity Module), the basic principles of the present invention are not limited to "SIM" devices. Rather, the basic principles of the present invention can be implemented using any type of device having secure storage for storing a set of cryptographic keys. Also, while the above embodiment includes a movable SIM device, in one embodiment, the SIM device is not movable, but the IoT device itself can be inserted into the programming interface 1502 on the IoT hub 110.

In one embodiment, rather than requiring the user to program the SIM (or other device), the SIM is pre-programmed into the IoT device 101 prior to distribution to the end user. In this embodiment, when a user sets up an IoT device 101, various techniques described herein are used to securely exchange encryption keys between an IoT hub 110/IoT service 120 and a new IoT device 101. can be used to

For example, as illustrated in FIG. 16A , each IoT device 101 or SIM 401 has a barcode or QR code 1501 that uniquely identifies the IoT device 101 and/or SIM 1501 and can be packaged together. In one embodiment, barcode or QR code 1601 includes an encoded representation of a public key for IoT device 101 or SIM 1001 . Alternatively, a barcode or QR code 1601 may be used by IoT hub 110 and/or IoT service 120 to identify or generate a public key (e.g., a public key already stored in secure storage). can be used as a pointer to). The barcode or QR code 601 can be printed on a separate card (as shown in FIG. 16A) or can be printed directly on the IoT device itself. Regardless of where the barcode is printed, in one embodiment, IoT hub 110 reads the barcode and sends the resulting data to security logic 1012 on IoT hub 110 and/or security logic on IoT service 120 ( A barcode reader 206 for providing 1013 is mounted. Then, the security logic 1012 on the IoT hub 110 can store the public key for the IoT device in its secure key store 1011, and the security logic 1013 on the IoT service 120 can store the public key ( to be used for subsequent encrypted communications) in its secure storage 1021.

In one embodiment, the data contained in the barcode or QR code 1601 also sends a user device 135 (such as an iPhone or Android device) on which an IoT app or browser-based applet designed by an IoT service provider is installed. can be captured through Once captured, the barcode data can be securely communicated to the IoT service 120 via a secure connection (eg, a secure socket layer (SSL) connection). Barcode data may also be provided from the client device 135 to the IoT hub 110 via a secure local connection (eg, via a local WiFi or Bluetooth LE connection).

Security logic 1002 on IoT device 101 and security logic 1012 on IoT hub 110 may be implemented using hardware, software, firmware, or any combination thereof. For example, in one embodiment, security logic 1002, 1012 is a chip used to establish local communication channel 130 between IoT device 101 and IoT hub 110 (e.g., local channel If 130 is a Bluetooth LE, it is implemented in a Bluetooth LE chip). Regardless of the specific location of secure logic 1002, 1012, in one embodiment, secure logic 1002, 1012 is designed to establish a secure execution environment for executing certain types of program code. This may be implemented using, for example, TrustZone technology (available on some ARM processors) and/or Trusted Execution Technology (designed by Intel). Of course, the basic principles of the present invention are not limited to any particular type of secure implementation technology.

In one embodiment, a barcode or QR code 1501 may be used to pair each IoT device 101 with the IoT hub 110 . For example, rather than using the standard wireless pairing process currently used to pair a Bluetooth LE device, a pairing code embedded within a barcode or QR code 1501 can be used to pair an IoT hub with a corresponding IoT device ( 110) can be provided.

16B illustrates one embodiment where barcode reader 206 on IoT hub 110 captures barcode/QR code 1601 associated with IoT device 101 . As mentioned, the barcode/QR code 1601 can be printed directly on the IoT device 101 or can be printed on a separate card provided with the IoT device 101. In either case, barcode reader 206 reads the pairing code from barcode/QR code 1601 and provides the pairing code to local communication module 1680 . In one embodiment, the local communication module 1680 is a Bluetooth LE chip and related software, but the basic principles of the present invention are not limited to any particular protocol standard. Once the pairing code is received, it is stored in secure storage containing pairing data 1685, and the IoT device 101 and IoT hub 110 are automatically paired. Whenever an IoT hub is paired with a new IoT device in this way, pairing data for that pairing is stored in secure storage 685 . In one embodiment, once the local communication module 1680 of the IoT hub 110 receives the pairing code, it can use the code as a key to encrypt communications over the local wireless channel with the IoT device 101.

Similarly, on the IoT device 101 side, the local communication module 1590 stores pairing data indicating pairing with the IoT hub in the local secure storage device 1595. Pairing data 1695 may include a pre-programmed pairing code identified in barcode/QR code 1601 . Pairing data 1695 may also be pairing data received from local communication module 1680 on IoT hub 110, necessary to establish a secure local communication channel (e.g., for encrypting communication with IoT hub 110). additional keys).

Thus, the barcode/QR code 1601 can be used to perform local pairing in a much more secure manner than current wireless pairing protocols because the pairing code is not transmitted over the air. Also, in one embodiment, the same barcode/QR code 1601 used for pairing is used to establish a secure connection from the IoT device 101 to the IoT hub 110 and from the IoT hub 110 to the IoT service 120. It can be used to identify an encryption key for

A method of programming a SIM card according to one embodiment of the present invention is illustrated in FIG. 17 . The method may be implemented within the system architecture described above, but is not limited to any particular system architecture.

At 1701 the user receives a new IoT device with a blank SIM card, at 1602 the user inserts the blank SIM card into the IoT hub. At 1703, the user programs the blank SIM card to have one or more sets of encryption keys. For example, as described above, in one embodiment, the IoT hub may randomly generate a public/private key pair, store the private key on the SIM card and store the public key in its local secure storage. Also, at 1704, at least the public key is sent to the IoT service, so that it can be used to identify the IoT device and establish encrypted communication with the IoT device. As noted above, in one embodiment, a programmable device other than a “SIM” card may be used to perform the same functions as a SIM card in the method shown in FIG. 17 .

A method for integrating a new IoT device into a network is illustrated in FIG. 18 . The method may be implemented within the system architecture described above, but is not limited to any particular system architecture.

At 1801, a user receives a new IoT device pre-assigned an encryption key. At 1802, the key is securely provided to the IoT hub. As noted above, in one embodiment, this involves reading a barcode associated with the IoT device to identify the public key of the public/private key pair assigned to the device. Barcodes can be read directly by the IoT hub or captured via an app or browser via a mobile device. In an alternative embodiment, 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 IoT device and the IoT hub to exchange keys. Regardless of how the key is transmitted, once received, it is stored in the IoT hub device's secure keystore. As mentioned above, various secure execution technologies such as Secure Enclave, Trusted Execution Technology (TXT) and/or TrustZone may be used on IoT hubs to store and protect keys. Also, at 1803, the key is securely transmitted to the IoT service, which stores the key in its own secure key store. The IoT service can then use the key to encrypt communication with the IoT device. Once again, the exchange can be implemented using certificates/signed keys. Within the hub 110, it is particularly important to prevent changes/additions/removals of stored keys.

A method of securely communicating commands/data to an IoT device using public/private keys is illustrated in FIG. 19 . The method may be implemented within the system architecture described above, but is not limited to any particular system architecture.

At 1901, the IoT service encrypts data/commands using the IoT device public key to generate IoT device packets. It then encrypts the IoT device packet using the IoT hub's public key to create an IoT hub packet (eg, creates an IoT hub wrapper around the IoT device packet). At 1902, the IoT service sends an IoT hub packet to the IoT hub. At 1903, the IoT hub decrypts the IoT hub packet using the IoT hub's private key to create an IoT device packet. At 1904, it then sends the IoT device packet to the IoT device, and the IoT device decrypts the IoT device packet at 1905 using the IoT device private key to generate data/commands. At 1906, the IoT device processes the data/commands.

In embodiments using symmetric keys, symmetric key exchanges may be negotiated between respective devices (eg, between each device and a hub and between a hub and a service). Once the key exchange is complete, each sending device uses the symmetric key to encrypt and/or sign each transmission before sending the data to the receiving device.

Embodiments of the present invention may include the various steps described above. A step may be embodied in machine-executable instructions that may be used to cause a general purpose or special-purpose processor to perform the step. Alternatively, these steps may be performed by specific hardware components that include hardwired logic to perform the steps, or by any combination of programmed computer components and custom hardware components.

As described herein, instructions may be software instructions stored in a memory that is configured to perform certain operations or embodied in a non-transitory computer readable medium or hardware such as an application specific integrated circuit (ASIC) having a predetermined function. may refer to a specific configuration. Accordingly, the techniques shown in the figures may be implemented using code and data stored on and executed on one or more electronic devices (eg, end stations, network elements, etc.). Such electronic devices include 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. To store code and data (internally and/or network to communicate with other electronic devices). Additionally, such electronic devices typically include one or more storage devices (non-transitory machine-readable storage media), user input/output devices (eg, keyboards, touch screens, and/or displays), and network connections, such as It includes a set of one or more processors coupled to one or more other components. The coupling of the set of processors with other components is typically through one or more buses and bridges (also referred to as bus controllers). A storage device and a signal carrying network traffic represent one or more machine-readable storage media and machine-readable communication media, respectively. Thus, the storage device of a given electronic device typically stores code and/or data for execution on a set of one or more processors of that electronic device. Of course, one or more portions of an embodiment of the invention may be implemented using different combinations of software, firmware, and/or hardware.

Throughout this detailed description, for purposes of explanation, numerous specific details have been set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. In some instances, well known structures and functions have not been described in detail in order to avoid obscuring the subject matter of the present invention. Accordingly, the scope and spirit of this invention should be judged in light of the claims that follow.

Claims (52)

As a system,
A system calibration module for collecting signal strength data indicative of signal strength between a wireless device and a plurality of Internet of Things (IoT) devices and/or IoT hubs within a user's home or business - the system calibration module performs the signal strength data associate with locations within the user's home or business and store the association in a location database;
The current location of the wireless device is determined by comparing the signal strength data in the location database with current signal strength data representing the current signal strength between the wireless device and one or more of the plurality of IoT devices and/or IoT hubs. signal strength analysis module to determine; and
a calibration app installed on the wireless device;
The calibration app communicates with the system calibration module when collecting the signal strength data, and the calibration app tells the user to 1) move to different rooms within the user's home or business and/or to different locations within each room. 2) instructing the calibration app to provide an indication when the user has reached each of the different rooms and/or different locations within each room;
system. delete The system of claim 1 , wherein the calibration app transmits current signal strength data between the wireless device and each of the plurality of IoT devices and/or IoT hubs when providing the indication. According to claim 1,
The system further comprises an IoT hub on which the system calibration module and signal strength analysis module are executed. 2. The system of claim 1, wherein the location database includes an identity of each location and a plurality of signal strength values associated with each location. The system of claim 5 , wherein the plurality of signal strength values include received signal strength indicator (RSSI) values measured between the wireless device and the plurality of IoT devices and/or IoT hubs at each location. . 7. The system of claim 6, wherein the signal strength analysis module receives a set of current signal strength values and compares the values to the signal strength data in the location database to determine the current location of the wireless device. 8. The system of claim 7, wherein the signal strength analysis module determines that the wireless device is in a particular location if the current signal strength values are within a specified range of the signal strength values specified in the location database. 9. The system of claim 8, wherein the signal strength analysis module sends one or more IoT device commands to control IoT devices in response to the determination that the wireless device is at the particular location. 10. The system of claim 9, wherein when the wireless device determines that it is within a particular room, the signal strength analysis module responsively turns on audio speakers within the room and/or turns on lights within the room. 11. The system of claim 10, wherein when the wireless device determines that it is in the particular room, the signal strength analysis module responsively turns off audio speakers in another room and/or turns off lights in the other room. . 2. The system of claim 1, wherein the signal strength analysis module performs triangulation techniques to determine the current location of the wireless device. 13. The system of claim 12, wherein the triangulation techniques include measuring signal strength values between the wireless device and the IoT hub, the wireless device and the IoT device, and signal strength between the IoT device and the IoT hub. . The system of claim 1 , wherein the signal strength data is collected by the wireless device and transmitted to a first IoT hub. 15. The method of claim 14, wherein the signal strength data is collected for wireless communication channels using a short-range wireless communication standard, and the signal strength data is transmitted from the wireless device to the first IoT hub using a different wireless communication standard. being, the system. 16. The system of claim 15, wherein the short range wireless communication standard comprises Bluetooth Low Energy (BTLE) and the different wireless communication standard comprises the Wifi standard. As a method,
Collecting signal strength data indicative of signal strength between a wireless device and a plurality of IoT devices and/or IoT hubs within a user's home or business - collecting signal strength data is performed by a calibration app on the wireless device and communicating with an IoT hub, wherein the calibration app instructs the user to 1) move to different rooms and/or different locations within each room within the user's home or business, and 2) the user instruct the calibration app to provide an indication when each of the different rooms and/or different locations within each room has been reached;
associating the signal strength data with locations within the user's home or business and storing the association in a location database; and
Current signal strength data of the wireless device in the home or business by comparing the signal strength data in the location database to current signal strength data representing the current signal strength between the wireless device and the plurality of IoT devices and/or IoT hubs. positioning step
Including, method. delete 18. The method of claim 17, wherein the calibration app transmits current signal strength data between the wireless device and each of the plurality of IoT devices and/or IoT hubs when providing the indication. 18. The method of claim 17, wherein the location database includes an identity of each location and a plurality of signal strength values associated with each location. 21. The method of claim 20, wherein the plurality of signal strength values comprises received signal strength indicator (RSSI) values measured between the wireless device and the plurality of IoT devices and/or IoT hubs at each location. . 22. The method of claim 21, determining a current location further comprises receiving a set of current signal strength values and comparing these values to the signal strength data in the location database to determine the current location of the wireless device. Including, how. 23. The method of claim 22, wherein determining the current location further comprises determining that the wireless device is in a particular location if the current signal strength values are within a specified range of the signal strength values specified in the location database. Including, how. 24. The method of claim 23, further comprising sending one or more IoT device commands to control IoT devices in response to the determination that the wireless device is at the particular location. 25. The method of claim 24, wherein when the wireless device determines to be within a particular room, it responsively turns on audio speakers within the room and/or turns on lights within the room. 26. The method of claim 25, wherein when the wireless device determines to be in the particular room, it responsively turns off audio speakers in another room and/or turns off lights in the other room. delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete

Images