WO2017007725A1 - Apparatus and method for establishing secure communication channels in an internet of things (iot) system - Google Patents

Apparatus and method for establishing secure communication channels in an internet of things (iot) system Download PDF

Info

Publication number
WO2017007725A1
WO2017007725A1 PCT/US2016/040819 US2016040819W WO2017007725A1 WO 2017007725 A1 WO2017007725 A1 WO 2017007725A1 US 2016040819 W US2016040819 W US 2016040819W WO 2017007725 A1 WO2017007725 A1 WO 2017007725A1
Authority
WO
WIPO (PCT)
Prior art keywords
iot
encryption engine
key
service
secret
Prior art date
Application number
PCT/US2016/040819
Other languages
English (en)
French (fr)
Inventor
Joe BRITT
Omar ZAKARIA
Scott Zimmerman
Original Assignee
Afero, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/791,373 external-priority patent/US9699814B2/en
Priority claimed from US14/791,371 external-priority patent/US9729528B2/en
Application filed by Afero, Inc. filed Critical Afero, Inc.
Priority to CN201680038597.6A priority Critical patent/CN107710216B/zh
Priority to JP2018500307A priority patent/JP7122964B2/ja
Priority to KR1020187002323A priority patent/KR20180025903A/ko
Publication of WO2017007725A1 publication Critical patent/WO2017007725A1/en
Priority to HK18110529.9A priority patent/HK1251310A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0838—Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these
    • H04L9/0841—Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these involving Diffie-Hellman or related key agreement protocols
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/606—Protecting data by securing the transmission between two devices or processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/062—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key distribution, e.g. centrally by trusted party
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H04L9/0877—Generation of secret information including derivation or calculation of cryptographic keys or passwords using additional device, e.g. trusted platform module [TPM], smartcard, USB or hardware security module [HSM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/14—WLL [Wireless Local Loop]; RLL [Radio Local Loop]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/80—Wireless
    • H04L2209/805—Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/045—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply hybrid encryption, i.e. combination of symmetric and asymmetric encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Definitions

  • This invention relates generally to the field of computer systems. More particularly, the invention relates to an apparatus and method for establishing secure communication channels in an IoT system.
  • The“Internet of Things” refers to the interconnection of uniquely-identifiable embedded devices within the Internet infrastructure. Ultimately, IoT 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.
  • IoT development and adoption has been slow due to issues related to connectivity, power, and a lack of standardization.
  • one obstacle to IoT development and adoption is that no standard platform exists to allow developers to design and offer new IoT devices and services.
  • a developer In order enter into the IoT market, a developer must design the entire IoT platform from the ground up, including the network protocols and infrastructure, hardware, software and services required to support the desired IoT implementation.
  • each provider of IoT devices uses proprietary techniques for designing and connecting the IoT devices, making the adoption of multiple types of IoT devices burdensome for end users.
  • Another obstacle to IoT adoption is the difficulty associated with connecting and powering IoT 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 IoT device, and such an electrical source is often not conveniently located.
  • FIGS.1A-B illustrates different embodiments of an IoT system architecture
  • FIG.2 illustrates an IoT device in accordance with one embodiment of the invention
  • FIG.3 illustrates an IoT hub in accordance with one embodiment of the invention
  • FIG.4A-B illustrate embodiments of the invention for controlling and collecting data from IoT devices, and generating notifications
  • FIG.5 illustrates embodiments of the invention for collecting data from IoT devices and generating notifications from an IoT hub and/or IoT service
  • FIG.6 illustrates one embodiment of a system in which an intermediary mobile device collects data from a stationary IoT device and provides the data to an IoT hub;
  • FIG.7 illustrates intermediary connection logic implemented in one embodiment of the invention
  • FIG.8 illustrates a method in accordance with one embodiment of the invention
  • FIG.9A illustrates an embodiment in which program code and data updates are provided to the IoT device
  • FIG.9B illustrates an embodiment of a method in which program code and data updates are provided to the IoT device
  • FIG.10 illustrates a high level view of one embodiment of a security architecture
  • FIG.11 illustrates one embodiment of an architecture in which a subscriber identity module (SIM) is used to store keys on IoT devices;
  • SIM subscriber identity module
  • FIG.12A illustrates one embodiment in which IoT devices are registered using barcodes or QR codes
  • FIG.12B illustrates one embodiment in which pairing is performed using barcodes or QR codes
  • FIG.13 illustrates one embodiment of a method for programming a SIM using an IoT hub
  • FIG.14 illustrates one embodiment of a method for registering an IoT device with an IoT hub and IoT service; and [0022]
  • FIG.15 illustrates one embodiment of a method for encrypting data to be transmitted to an IoT device;
  • FIGS.16A-B illustrate different embodiments of the invention for encrypting data between an IoT service and an IoT device
  • FIG.17 illustrates embodiments of the invention for performing a secure key exchange, generating a common secret, and using the secret to generate a key stream;
  • FIG.18 illustrates a packet structure in accordance with one embodiment of the invention
  • FIG.19 illustrates techniques employed in one embodiment for writing and reading data to/from an IoT device without formally pairing with the IoT device
  • FIG.20 illustrates an exemplary set of command packets employed in one embodiment of the invention
  • FIG.21 illustrates an exemplary sequence of transactions using command packets
  • FIG.22 illustrates a method in accordance with one embodiment of the invention.
  • FIGS.23A-C illustrate a method for secure pairing in accordance with one embodiment of the invention.
  • One embodiment of the invention comprises an Internet of Things (IoT) platform which may be utilized by developers to design and build new IoT devices and applications.
  • IoT Internet of Things
  • one embodiment includes a base hardware/software platform for IoT devices including a predefined networking protocol stack and an IoT hub through which the IoT devices are coupled to the Internet.
  • one embodiment includes an IoT service through which the IoT hubs and connected IoT devices may be accessed and managed as described below.
  • one embodiment of the IoT platform includes an IoT app or Web application (e.g., executed on a client device) to access and configured the IoT service, hub and connected devices.
  • IoT app or Web application e.g., executed on a client device
  • FIG. 1A illustrates an overview of an architectural platform on which embodiments of the invention may be implemented.
  • the illustrated embodiment includes a plurality of IoT devices 101-105 communicatively coupled over local communication channels 130 to a central IoT hub 110 which is itself
  • the IoT service 120 includes an end user database 122 for maintaining user account information and data collected from each user’s IoT devices. For example, if the IoT 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 IoT devices 101-105.
  • sensors e.g., temperature sensors, accelerometers, heat sensors, motion detectore, etc
  • the data stored in the database 122 may then be made accessible to the end user via the IoT 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 IoT service 120).
  • the IoT 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 IoT service 120, user devices 135 and/or external Websites 130 via the IoT hub 110. Some of the IoT devices 101-105 may perform a specified function in response to control commands sent through the IoT hub 110. Various specific examples of information collected by the IoT devices 101-105 and control commands are provided below.
  • the IoT device 101 is a user input device designed to record user selections and send the user selections to the IoT service 120 and/or Website.
  • the IoT hub 110 includes a cellular radio to establish a connection to the Internet 220 via a cellular service 115 such as a 4G (e.g., Mobile WiMAX, LTE) or 5G cellular data service.
  • a cellular service 115 such as a 4G (e.g., Mobile WiMAX, LTE) or 5G cellular data service.
  • the IoT hub 110 may include a WiFi radio to establish a WiFi connection through a WiFi access point or router 116 which couples the IoT hub 110 to the Internet (e.g., via an Internet Service Provider providing Internet service to the end user).
  • WiFi Wireless Fidelity
  • the underlying principles of the invention are not limited to any particular type of communication channel or protocol.
  • the IoT 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 IoT devices 101-105 and the IoT hub 110 are equipped with Bluetooth LE radios and protocol stacks.
  • the IoT platform includes an IoT app or Web application executed on user devices 135 to allow users to access and configure the connected IoT devices 101-105, IoT hub 110, and/or IoT service 120.
  • the app or web application may be designed by the operator of a Website 130 to provide IoT functionality to its user base.
  • the Website may maintain a user database 131 containing account records related to each user.
  • FIG. 1B illustrates additional connection options for a plurality of IoT hubs 110-111, 190
  • a single user may have multiple hubs 110-111 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 IoT devices 101-105.
  • a user may be connected via a local communication channel (e.g., Wifi, Ethernet, Power Line
  • each of the hubs 110-111 may establish a direct connection to the IoT service 120 through a cellular 115 or WiFi 116 connection (not explicitly shown in Figure 1B).
  • one of the IoT hubs such as IoT hub 110 may act as a“master” hub which provides connectivity and/or local services to all of the other IoT hubs on the user premises 180, such as IoT hub 111 (as indicated by the dotted line connecting IoT hub 110 and IoT hub 111).
  • the master IoT hub 110 may be the only IoT hub to establish a direct connection to the IoT service 120.
  • only the“master” IoT hub 110 is equipped with a cellular communication interface to establish the connection to the IoT service 120. As such, all communication between the IoT service 120 and the other IoT hubs 111 will flow through the master IoT hub 110.
  • the master IoT hub 110 may be provided with additional program code to perform filtering operations on the data exchanged between the other IoT hubs 111 and IoT service 120 (e.g., servicing some data requests locally when possible).
  • the IoT service 120 will logically associate the hubs with the user and combine all of the attached IoT 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 IoT hub 110 and one or more slave IoT hubs 111 may connect over a local network which may be a WiFi network 116, 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 116, 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 IoT devices 101-105 may be interconnected with the IoT hubs 110-111 using any type of local network channel such as WiFi, Ethernet, PLC, or Bluetooth LE, to name a few.
  • Figure 1B also shows an IoT hub 190 installed at a second user premises 181.
  • IoT hubs 190 may be installed and configured to collect data from IoT 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 IoT service 120 will logically associate the IoT hubs 110-111, 190 with the user and combine all of the attached IoT 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 IoT 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 IoT device 201 and library code 202 comprising a set of predefined building blocks which may be utilized by the application developer of the IoT device 101.
  • the library code 202 comprises a set of basic functions required to implement an IoT device such as a communication protocol stack 201 for enabling communication between each IoT device 101 and the IoT hub 110.
  • the communication protocol stack 201 comprises a Bluetooth LE protocol stack.
  • 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 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 IoT 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 IoT device 101 based on the particular application for which the IoT 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 IoT 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 IoT device.
  • 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 identify module (SIM).
  • a wakeup receiver 207 is included in one embodiment to wake the IoT device from an ultra low power state in which it is consuming virtually no power.
  • the wakeup receiver 207 is configured to cause the IoT device 101 to exit this low power state in response to a wakeup signal received from a wakeup transmitter 307 configured on the IoT hub 110 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 110 needs to wake the IoT device 101 from a very low power state.
  • the IoT 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 IoT 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 IoT hub 110 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 IoT hub 110 to the cellular service 115.
  • the 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.
  • 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 identify module (SIM).
  • SIM subscriber identify module
  • a local communication interface 303 and antenna 311 establishes local communication channels with each of the IoT devices 101-105.
  • the local communication interface 303/antenna 311 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 IoT 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 IoT hub to pair with new IoT devices.
  • each new IoT device 101-105 is assigned a unique code which is communicated to the IoT hub 110 during the pairing process.
  • the unique code may be embedded in a barcode on the IoT device and may be read by the barcode reader 106 or may be communicated over the local communication channel 130.
  • the unique ID code is embedded magnetically on the IoT device and the IoT hub has a magnetic sensor such as an radio frequency ID (RFID) or near field communication (NFC) sensor to detect the code when the IoT device 101 is moved within a few inches of the IoT hub 110.
  • RFID radio frequency ID
  • NFC near field communication
  • the IoT hub 110 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 IoT service 120, user device 135 and/or Website 130 to validate the ID code. Once validated, in one embodiment, the IoT hub 110 pairs the IoT device 101 and stores the pairing data in memory 317 (which, as mentioned, may include non-volatile memory). Once pairing is complete, the IoT hub 110 may connect with the IoT device 101 to perform the various IoT functions described herein.
  • the organization running the IoT service 120 may provide the IoT hub 110 and a basic hardware/software platform to allow developers to easily design new IoT services.
  • developers may be provided with a software development kit (SDK) to update the program code and data 305 executed within the hub 110.
  • SDK software development kit
  • the SDK may include an extensive set of library code 202 designed for the base IoT 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 IoT 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 IoT hub 110 manages a continuous bi-directional stream of data between the IoT devices 101-105 and the IoT service 120.
  • the IoT 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 IoT hub 110 and the IoT devices 101-105 are automatically upgradeable over the network.
  • a new update is available for the IoT hub 110 it may automatically download and install the update from the IoT service 120. It may first copy the updated code into a local memory, run and verify the update before swapping out the older program code.
  • updates are available for each of the IoT devices 101-105, they may initially be downloaded by the IoT hub 110 and pushed out to each of the IoT devices 101-105. Each IoT device 101-105 may then apply the update in a similar manner as described above for the IoT hub and report back the results of the update to the IoT hub 110. If the update is successful, then the IoT hub 110 may delete the update from its memory and record the latest version of code installed on each IoT device (e.g., so that it may continue to check for new updates for each IoT device).
  • the IoT hub 110 is powered via A/C power.
  • the IoT hub 110 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 IoT system.
  • a set of IoT 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 IoT 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 IoT 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 IoT hub 110 via an app or browser installed on a user device 135.
  • Control logic 412 executed on the IoT hub 110 receives the current
  • temperature/humidity data from the sensor 404 and responsively transmits commands to the IoT device 101 to control the IR/RF blaster 401 in accordance with the desired temperature/humidity. For example, if the temperature is below the desired
  • control logic 412 may transmit a command to the air
  • the command may include the necessary remote control code stored in a database 413 on the IoT hub 110.
  • the IoT service 421 may implement control logic 421 to control the electronics equipment 430-432 based on specified user preferences and stored control codes 422.
  • IoT device 102 in the illustrated example is used to control lighting 431.
  • sensor 405 in IoT 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 IoT hub 110 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).
  • IoT device 103 in the illustrated example is configured to control audiovisual equipment 432 (e.g., a television, A/V receiver, cable/satellite receiver, AppleTV TM , etc).
  • Sensor 406 in IoT 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 IoT device 103.
  • the senor 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 IoT hub 110 and/or a database 422 on the IoT service 120.
  • the control codes may be provided to the IoT hub 110 from a master database of control codes 422 for different pieces of equipment maintained on the IoT 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 IoT hub may retrieve the required IR/RF codes from the remote control code database 492 on the IoT service 120 (e.g., identifying each piece of electronic equipment with a unique ID).
  • the IoT hub 110 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 to“learn” new remote control codes directly from the original remote control 495 provided with the electronic equipment.
  • the user may interact with the IoT hub 110 via the app/browser on the user device 135 to teach the IoT hub 110 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 IoT hub 110 and/or sent back to the IoT 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 IoT 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 IoT device 101 For control of a piece of equipment such as the air conditioner 430, it would be desirable to place the IoT device 101 sufficiently far away so that the sensor 404 can accurately measure the ambient temperature in the home (e.g., placing the IoT 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 IoT 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.
  • one embodiment of the IoT hub 110 and/or IoT service 120 transmits notifications to the end user related to the current status of each piece of electronics equipment.
  • the notifications which may be text messages and/or app-specific notifications, may then be displayed on the display of the user’s mobile device 135. For example, if the user’s air conditioner has been on for an extended period of time but the temperature has not changed, the IoT hub 110 and/or IoT service 120 may send the user a notification that the air conditioner is not functioning properly.
  • 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 IoT service 120 to the IoT hub 110 which will then control the equipment via the control logic 412.
  • the user input may be sent directly to the IoT hub 110 from the user device 135.
  • the user may program the control logic 412 on the IoT hub 110 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 IoT devices 104-105 equipped with sensors 503-504 for monitoring electronic equipment 530-531.
  • the IoT 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 IoT device 104 transmits the current temperature measured by the temperature sensor 503 to the IoT hub 110 and/or the IoT 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 IoT 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 IoT 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).
  • IoT 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 IoT device with control logic and a switch may be configured to turn off all power in the user’s home and a second IoT device with control logic and a switch may be configured to turn off all gas in the user’s home.
  • IoT 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 IoT hub 110 and/or the IoT service 120 may be configured to automatically turn off electricity or gas in such situations.
  • the IoT hub 110 and IoT service 120 communicate at periodic intervals. If the IoT service 120 detects that the connection to the IoT hub 110 has been lost (e.g., by failing to receive a request or response from the IoT 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).
  • the wireless technologies used to interconnect IoT devices such as Bluetooth LE are generally short range technologies, if the hub for an IoT implementation is outside the range of an IoT device, the IoT device will not be able to transmit data to the IoT hub (and vice versa).
  • one embodiment of the invention provides a mechanism for an IoT device which is outside of the wireless range of the IoT hub to periodically connect with one or more mobile devices when the mobile devices are within range. Once connected, the IoT device can transmit any data which needs to be provided to the IoT hub to the mobile device which then forwards the data to the IoT hub.
  • one embodiment includes an IoT hub 110, an IoT device 601 which is out of range of the IoT hub 110 and a mobile device 611.
  • the out of range IoT device 601 may include any form of IoT device capable of collecting and communicating data.
  • the IoT device 601 may comprise a data collection device configured within a refrigerator to monitor the food items available in the refrigerator, the users who consume the food items, and the current temperature.
  • the underlying principles of the invention are not limited to any particular type of IoT device.
  • the techniques described herein may be implemented using any type of IoT device including those used to collect and transmit data for smart meters, stoves, washers, dryers, lighting systems, HVAC systems, and audiovisual equipment, to name just a few.
  • the IoT device 611 illustrated in Figure 6 may be any form of mobile device capable of communicating and storing data.
  • the mobile device 611 is a smartphone with an app installed thereon to facilitate the techniques described herein.
  • the mobile device 611 comprises a wearable device such as a communication token affixed to a neckless or bracelet, a smartwatch or a fitness device.
  • the wearable token may be particularly useful for elderly users or other users who do not own a smartphone device.
  • the out of range IoT device 601 may periodically or continually check for connectivity with a mobile device 611. Upon establishing a connection (e.g., as the result of the user moving within the vicinity of the refrigerator) any collected data 605 on the IoT device 601 is automatically transmitted to a temporary data repository 615 on the mobile device 611.
  • the IoT device 601 and mobile device 611 establish a local wireless communication channel using a low power wireless standard such as BTLE.
  • the mobile device 611 may initially be paired with the IoT device 601 using known pairing techniques.
  • the mobile device 611 will transmit the data once communication is established with the IoT hub 110 (e.g., when the user walks within the range of the IoT hub 110).
  • the IoT hub may then store the data in a central data repository 413 and/or send the data over the Internet to one or more services and/or other user devices.
  • the mobile device 611 may use a different type of communication channel to provide the data to the IoT hub 110 (potentially a higher power communication channel such as WiFi).
  • the out of range IoT device 601, the mobile device 611, and the IoT hub may all be configured with program code and/or logic to implement the techniques described herein.
  • the IoT device 601 may be configured with intermediary connection logic and/or application
  • the mobile device 611 may be configured with an intermediary connection logic/application
  • the IoT hub 110 may be configured with an intermediary connection logic/application 721 to perform the operations described herein.
  • the intermediary connection logic/application on each device may be implemented in hardware, software, or any combination thereof.
  • the intermediary connection logic/application 701 of the IoT device 601 searches and establishes a connection with the intermediary connection
  • the intermediary connection logic/application 701 on the mobile device 611 then forwards the data to the intermediary connection logic/application on the IoT hub, which stores the data in the central data repository 413.
  • the intermediary connection logic/applications 701, 711, 721, on each device may be configured based on the application at hand. For example, for a refrigerator, the connection logic/application 701 may only need to transmit a few packets on a periodic basis. For other applications (e.g., temperature sensors), the connection logic/application 701 may need to transmit more frequent updates.
  • the IoT device 601 may be configured to establish a wireless connection with one or more intermediary IoT devices, which are located within range of the IoT hub 110.
  • any IoT devices 601 out of range of the IoT hub may be linked to the hub by forming a“chain” using other IoT devices.
  • the techniques described herein may be used to collect various different types of pertinent data.
  • the identity of the user may be included with the collected data 605.
  • the IoT system may be used to track the behavior of different users within the home. For example, if used within a refrigerator, the collected data 605 may then include the identify of each user who passes by fridge, each user who opens the fridge, and the specific food items consumed by each user. Different types of data may be collected from other types of IoT devices.
  • the system is able to determine, for example, which user washes clothes, which user watches TV on a given day, the times at which each user goes to sleep and wakes up, etc. All of this crowd-sourced data may then be compiled within the data repository 413 of the IoT hub and/or forwarded to an external service or user.
  • the mobile device 611 may be a very small token worn by the elderly user to collect the information in different rooms of the user’s home. Each time the user opens the refrigerator, for example, this data will be included with the collected data 605 and transferred to the IoT hub 110 via the token. The IoT hub may then provide the data to one or more external users (e.g., the children or other individuals who care for the elderly user). If data has not been collected for a specified period of time (e.g., 12 hours), then this means that the elderly user has not been moving around the home and/or has not been opening the refrigerator.
  • a specified period of time e.g. 12 hours
  • the IoT hub 110 or an external service connected to the IoT hub may then transmit an alert notification to these other individuals, informing them that they should check on the elderly user.
  • the collected data 605 may include other pertinent information such as the food being consumed by the user and whether a trip to the grocery store is needed, whether and how frequently the elderly user is watching TV, the frequency with which the elderly user washes clothes, etc.
  • the collected data may include an indication of a part that needs to be replaced.
  • a notification may be sent to a technician with a request to fix the problem. The technician may then arrive at the home with the needed replacement part.
  • FIG. 8 A method in accordance with one embodiment of the invention is illustrated in Figure 8. The method may be implemented within the context of the architectures described above, but is not limited to any particular architecture.
  • an IoT device which is out of range of the IoT hub periodically collects data (e.g., opening of the refrigerator door, food items used, etc).
  • the IoT device periodically or continually checks for connectivity with a mobile device (e.g., using standard local wireless techniques for establishing a connection such as those specified by the BTLE standard). If the connection to the mobile device is established, determined at 802, then at 803, the collected data is transferred to the mobile device at 803.
  • the mobile device transfers the data to the IoT hub, an external service and/or a user. As mentioned, the mobile device may transmit the data immediately if it is already connected (e.g., via a WiFi link).
  • the techniques described herein may be used to update or otherwise provide data to IoT devices.
  • Figure 9A shows an IoT hub 110 with program code updates 901 that need to be installed on an IoT device 601 (or a group of such IoT devices).
  • the program code updates may include system updates, patches, configuration data and any other data needed for the IoT device to operate as desired by the user.
  • the user may specify configuration options for the IoT device 601 via a mobile device or computer which are then stored on the IoT hub 110 and provided to the IoT device using the techniques described herein.
  • the intermediary connection logic/application 721 on the IoT hub 110 communicates with the intermediary connection logic/application 711 on the mobile device 611 to store the program code updates within a temporary storage 615.
  • the intermediary connection logic/application 711 on the mobile device 611 connects with the
  • intermediary/connection logic/application 701 on the IoT device 601 to provide the program code updates to the device.
  • the IoT device 601 may then enter into an automated update process to install the new program code updates and/or data.
  • a method for updating an IoT device is shown in Figure 9B.
  • the method may be implemented within the context of the system architectures described above, but is not limited to any particular system architectures.
  • new program code or data updates are made available on the IoT hub and/or an external service (e.g., coupled to the mobile device over the Internet).
  • the mobile device receives and stores the program code or data updates on behalf of the IoT device.
  • the IoT device and/or mobile device periodically check to determine whether a connection has been established at 902. If a connection is established, determined at 903, then at 904 the updates are transferred to the IoT device and installed.
  • the low power microcontroller 200 of each IoT device 101 and the low power logic/microcontroller 301 of the IoT hub 110 include a secure key store for storing encryption keys used by the embodiments described below (see, e.g., Figures 10-15 and associated text).
  • the keys may be secured in a subscriber identify module (SIM) as discussed below.
  • SIM subscriber identify module
  • FIG. 10 illustrates a high level architecture which uses public key infrastructure (PKI) techniques and/or symmetric key exchange/encryption techniques to encrypt communications between the IoT Service 120, the IoT hub 110 and the IoT 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 IoT device 101-102, each IoT hub 110 and the IoT service 120.
  • a new IoT hub 110 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, it’s public key is provided to both the IoT hub 110 and the IoT 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 IoT device 101, 102 includes a secure key storage 1001, 1003, respectively, for security storing each device’s private key.
  • Security logic 1002, 1304 then utilizes the securely stored private keys to perform the encryption/decryption operations described herein.
  • the IoT hub 110 includes a secure storage 1011 for storing the IoT hub private key and the public keys of the IoT devices 101-102 and the IoT service 120; as well as security logic 1012 for using the keys to perform encryption/decryption operations.
  • the IoT service 120 may include a secure storage 1021 for security storing its own private key, the public keys of various IoT devices and IoT hubs, and a security logic 1013 for using the keys to encrypt/decrypt communication with IoT hubs and devices.
  • a secure storage 1021 for security storing its own private key, the public keys of various IoT devices and IoT hubs, and a security logic 1013 for using the keys to encrypt/decrypt communication with IoT hubs and devices.
  • the IoT hub 110 when the IoT hub 110 receives a public key certificate from an IoT 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 1011.
  • the security logic 1013 encrypts the data/command using the public key of the IoT device 101 to generate an encrypted IoT device packet. In one embodiment, it then encrypts the IoT device packet using the public key of the IoT hub 110 to generate an IoT hub packet and transmits the IoT hub packet to the IoT hub 110.
  • 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 enters into a secure key exchange protocol to exchange a symmetric key with the IoT hub 110.
  • 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 IoT hub 110 to encrypt communications.
  • the IoT hub 110 and IoT 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 110 and between the hub 110 and the IoT service 120.
  • a new symmetric key is exchanged with each new communication session between the devices 101, the hub 110, 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 1012 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 1012 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 110 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 110 may be assigned a continually increasing counter value.
  • Both the hub 110 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 110 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 IoT hub 110 when using public/private key encryption, uses its private key to decrypt the IoT hub packet and generate the encrypted IoT device packet, which it transmits to the associated IoT device 101.
  • the IoT device 101 then uses its private key to decrypt the IoT 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 IoT device 101 to the IoT hub 110 and to the IoT service 120.
  • the security logic 1002 on the IoT device 101 uses the public key of the IoT hub 110 to encrypt data packets sent to the IoT hub 110.
  • the security logic 1012 on the IoT hub 110 may then decrypt the data packets using the IoT hub’s private key.
  • the security logic 1002 on the IoT device 101 and/or the security logic 1012 on the IoT hub 110 may encrypt data packets sent to the IoT service 120 using the public key of the IoT service 120 (which may then be decrypted by the security logic 1013 on the IoT service 120 using the service’s private key).
  • the device 101 and hub 110 may share a symmetric key while the hub and service 120 may share a different symmetric key.
  • the secure key storage on each IoT device 101 is implemented using a programmable subscriber identity module (SIM) 1101.
  • SIM subscriber identity module
  • the IoT device 101 may initially be provided to the end user with an un-programmed SIM card 1101 seated within a SIM interface 1100 on the IoT device 101.
  • the user takes the programmable SIM card 1101 out of the SIM interface 500 and inserts it into a SIM programming interface 1102 on the IoT hub 110.
  • Programming logic 1125 on the IoT hub then securely programs the SIM card 1101 to register/pair the IoT device 101 with the IoT hub 110 and IoT service 120.
  • a public/private key pair may be randomly generated by the programming logic 1125 and the public key of the pair may then be stored in the IoT hub’s secure storage device 411 while the private key may be stored within the programmable SIM 1101.
  • the programming logic 525 may store the public keys of the IoT hub 110, the IoT service 120, and/or any other IoT devices 101 on the SIM card 1401 (to be used by the security logic 1302 on the IoT device 101 to encrypt outgoing data).
  • the new IoT device 101 may be provisioned with the IoT Service 120 using the SIM as a secure identifier (e.g., using existing techniques for registering a device using a SIM).
  • both the IoT hub 110 and the IoT service 120 will securely store a copy of the IoT device’s public key to be used when encrypting communication with the IoT device 101.
  • the techniques described above with respect to Figure 11 provide enormous flexibility when providing new IoT 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 IoT hub 110 and the results of the programming may be securely communicated to the IoT service 120. Consequently, new IoT devices 101 may be sold to end users from online or local retailers and later securely provisioned with the IoT 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 IoT device itself may be inserted within the programming interface 1102 of the IoT hub 110.
  • the SIM is pre-programmed into the IoT device 101, prior to distribution to the end user. In this embodiment, when the user sets up the IoT device 101, various techniques described herein may be used to securely exchange encryption keys between the IoT hub 110/IoT service 120 and the new IoT device 101.
  • each IoT device 101 or SIM 401 may be packaged with a barcode or QR code 1501 uniquely identifying the IoT device 101 and/or SIM 1001.
  • the barcode or QR code 1201 comprises an encoded representation of the public key for the IoT device 101 or SIM 1001.
  • the barcode or QR code 1201 may be used by the IoT hub 110 and/or IoT 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 12A) or may be printed directly on the IoT device itself.
  • the IoT hub 110 is equipped with a barcode reader 206 for reading the barcode and providing the resulting data to the security logic 1012 on the IoT hub 110 and/or the security logic 1013 on the IoT service 120.
  • the security logic 1012 on the IoT hub 110 may then store the public key for the IoT device within its secure key storage 1011 and the security logic 1013 on the IoT 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 1201 may also be captured via a user device 135 (e.g., such as an iPhone or Android device) with an installed IoT app or browser-based applet designed by the IoT service provider.
  • a user device 135 e.g., such as an iPhone or Android device
  • the barcode data may be securely communicated to the IoT 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 IoT hub 110 over a secure local connection (e.g., over a local WiFi or Bluetooth LE connection).
  • the security logic 1002 on the IoT device 101 and the security logic 1012 on the IoT hub 110 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 IoT device 101 and the IoT hub 110 (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 IoT device 101 with the IoT hub 110.
  • a pairing code embedded within the barcode or QR code 1501 may be provided to the IoT hub 110 to pair the IoT hub with the corresponding IoT device.
  • Figure 12B illustrates one embodiment in which the barcode reader 206 on the IoT hub 110 captures the barcode/QR code 1201 associated with the IoT device 101.
  • the barcode/QR code 1201 may be printed directly on the IoT device 101 or may be printed on a separate card provided with the IoT device 101.
  • the barcode reader 206 reads the pairing code from the barcode/QR code 1201 and provides the pairing code to the local communication module 1280.
  • the local communication module 1280 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 1285 and the IoT device 101 and IoT hub 110 are automatically paired. Each time the IoT hub is paired with a new IoT device in this manner, the pairing data for that pairing is stored within the secure storage 685.
  • the local communication module 1280 of the IoT hub 110 may use the code as a key to encrypt communications over the local wireless channel with the IoT device 101.
  • the local communication module 1590 stores pairing data within a local secure storage device 1595 indicating the pairing with the IoT hub.
  • the pairing data 1295 may include the pre-programmed pairing code identified in the barcode/QR code 1201.
  • the pairing data 1295 may also include pairing data received from the local communication module 1280 on the IoT hub 110 required for establishing a secure local communication channel (e.g., an additional key to encrypt communication with the IoT hub 110).
  • the barcode/QR code 1201 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 1201 used for pairing may be used to identify encryption keys to build a secure connection from the IoT device 101 to the IoT hub 110 and from the IoT hub 110 to the IoT service 120.
  • a method for programming a SIM card in accordance with one embodiment of the invention is illustrated in Figure 13. 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 IoT device with a blank SIM card and, at 1602, the user inserts the blank SIM card into an IoT hub.
  • the user programs the blank SIM card with a set of one or more encryption keys.
  • the IoT hub may randomly generate a public/private key pair and store the private key on the SIM card and the public key in its local secure storage.
  • at least the public key is transmitted to the IoT service so that it may be used to identify the IoT device and establish encrypted communication with the IoT device.
  • 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 13.
  • FIG. 14 A method for integrating a new IoT device into a network is illustrated in Figure 14. 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 IoT device to which an encryption key has been pre-assigned.
  • the key is securely provided to the IoT hub.
  • this involves reading a barcode associated with the IoT device to identify the public key of a public/private key pair assigned to the device.
  • the barcode may be read directly by the IoT 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 IoT device and the IoT hub to exchange the key.
  • the key is transmitted, once received, it is stored in the secure keystore of the IoT hub device.
  • various secure execution technologies may be used on the IoT hub to 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 IoT service which stores the key in its own secure keystore. It may then use the key to encrypt communication with the IoT device.
  • the exchange may be implemented using a certificate/signed key. Within the hub 110 it is particularly important to prevent modification/addition/ removal of the stored keys.
  • FIG. 15 A method for securely communicating commands/data to an IoT device using public/private keys is illustrated in Figure 15. The method may be implemented within the system architecture described above, but is not limited to any particular system architecture.
  • the IoT service encrypts the data/commands using the IoT device public key to create an IoT device packet. It then encrypts the IoT device packet using IoT hub’s public key to create the IoT hub packet (e.g., creating an IoT hub wrapper around the IoT device packet).
  • the IoT service transmits the IoT hub packet to the IoT hub.
  • the IoT hub decrypts the IoT hub packet using the IoT hub’s private key to generate the IoT device packet.
  • the IoT device transmits the IoT device packet to the IoT device which, at 1505, decrypts the IoT device packet using the IoT device private key to generate the data/commands.
  • the IoT 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.
  • encryption and decryption of data is performed between the IoT service 120 and each IoT device 101, regardless of the intermediate devices used to support the communication channel (e.g., such as the user’s mobile device 611 and/or the IoT hub 110).
  • the intermediate devices used to support the communication channel e.g., such as the user’s mobile device 611 and/or the IoT hub 110.
  • the IoT service 120 includes an encryption engine 1660 which manages a set of“service session keys” 1650 and each IoT device 101 includes an encryption engine 1661 which manages a set of“device session keys” 1651 for encrypting/decrypting communication between the IoT device 101 and IoT service 120.
  • the encryption engines may rely on different hardware modules when performing the security/encryption techniques described herein including a hardware security module 1630-1631 for (among other things) generating a session public/private key pair and preventing access to the private session key of the pair and a key stream generation module 1640-1641 for generating a key stream using a derived secret.
  • the service session keys 1650 and the device session keys 1651 comprise related public/private key pairs.
  • the device session keys 1651 on the IoT device 101 include a public key of the IoT service 120 and a private key of the IoT device 101.
  • the public/private session key pairs, 1650 and 1651 are used by each encryption engine, 1660 and 1661, respectively, to generate the same secret which is then used by the SKGMs 1640-1641 to generate a key stream to encrypt and decrypt communication between the IoT service 120 and the IoT device 101. Additional details associated with generation and use of the secret in accordance with one embodiment of the invention are provided below.
  • FIG. 16A once the secret has been generated using the keys 1650- 1651, the client will always send messages to the IoT device 101 through the IoT service 120, as indicated by Clear transaction 1611.“Clear” as used herein is meant to indicate that the underlying message is not encrypted using the encryption techniques described herein.
  • a secure sockets layer (SSL) channel or other secure channel e.g., an Internet Protocol Security (IPSEC) channel
  • SSL secure sockets layer
  • IPSEC Internet Protocol Security
  • the encryption engine 1660 on the IoT service 120 then encrypts the message using the generated secret and transmits the encrypted message to the IoT hub 110 at 1602.
  • the secret and a counter value are used to generate a key stream, which is used to encrypt each message packet. Details of this embodiment are described below with respect to Figure 17.
  • an SSL connection or other secure channel may be established between the IoT service 120 and the IoT hub 110.
  • the IoT hub 110 (which does not have the ability to decrypt the message in one embodiment) transmits the encrypted message to the IoT device at 1603 (e.g., over a Bluetooth Low Energy (BTLE) communication channel).
  • the encryption engine 1661 on the IoT device 101 may then decrypt the message using the secret and process the message contents.
  • the encryption engine 1661 may generate the key stream using the secret and a counter value and then use the key stream for decryption of the message packet.
  • the message itself may comprise any form of communication between the IoT service 120 and IoT device 101.
  • the message may comprise a command packet instructing the IoT device 101 to perform a particular function such as taking a measurement and reporting the result back to the client device 611 or may include configuration data to configure the operation of the IoT device 101.
  • the encryption engine 1661 on the IoT device 101 uses the secret or a derived key stream to encrypt the response and transmits the encrypted response to the IoT hub 110 at 1604, which forwards the response to the IoT service 120 at 1605.
  • the encryption engine 1660 on the IoT service 120 then decrypts the response using the secret or a derived key stream and transmits the decrypted response to the client device 611 at 1606 (e.g., over the SSL or other secure communication channel).
  • Figure 16B illustrates an embodiment which does not require an IoT hub. Rather, in this embodiment, communication between the IoT device 101 and IoT service 120 occurs through the client device 611 (e.g., as in the embodiments described above with respect to Figures 6-9B). In this embodiment, to transmit a message to the IoT device 101 the client device 611 transmits an unencrypted version of the message to the IoT service 120 at 1611. The encryption engine 1660 encrypts the message using the secret or the derived key stream and transmits the encrypted message back to the client device 611 at 1612.
  • the client device 611 then forwards the encrypted message to the IoT device 101 at 1613, and the encryption engine 1661 decrypts the message using the secret or the derived key stream.
  • the IoT device 101 may then process the message as described herein. If a response is required, the encryption engine 1661 encrypts the response using the secret and transmits the encrypted response to the client device 611 at 1614, which forwards the encrypted response to the IoT service 120 at 1615.
  • the encryption engine 1660 then decrypts the response and transmits the decrypted response to the client device 611 at 1616.
  • Figure 17 illustrates a key exchange and key stream generation which may initially be performed between the IoT service 120 and the IoT device 101.
  • this key exchange may be performed each time the IoT service 120 and IoT device 101 establish a new communication session.
  • the key exchange may be performed and the exchanged session keys may be used for a specified period of time (e.g., a day, a week, etc). While no intermediate devices are shown in Figure 17 for simplicity, communication may occur through the IoT hub 110 and/or the client device 611.
  • the encryption engine 1660 of the IoT service 120 sends a command to the HSM 1630 (e.g., which may be such as a CloudHSM offered by Amazon®) to generate a session public/private key pair.
  • the HSM 1630 may subsequently prevent access to the private session key of the pair.
  • the encryption engine on the IoT device 101 may transmit a command to the HSM 1631 (e.g., such as an Atecc508 HSM from Atmel Corporation®) which generates a session public/private key pair and prevents access to the session private key of the pair.
  • the underlying principles of the invention are not limited to any specific type of encryption engine or manufacturer.
  • the IoT service 120 transmits its session public key generated using the HSM 1630 to the IoT device 101 at 1701.
  • the IoT device uses its HSM 1631 to generate its own session public/private key pair and, at 1702, transmits its public key of the pair to the IoT service 120.
  • the encryption engines 1660-1661 use an Elliptic curve Diffie–Hellman (ECDH) protocol, which is an anonymous key agreement that allows two parties with an elliptic curve public–private key pair, to establish a shared secret.
  • ECDH Elliptic curve Diffie–Hellman
  • the encryption engine 1660 of the IoT service 120 uses these techniques, at 1703, the encryption engine 1660 of the IoT service 120 generates the secret using the IoT device session public key and its own session private key.
  • the IoT service 120 and IoT device 101 have both generated the same secret to be used to encrypt communication as described below.
  • the encryption engines 1660- 1661 rely on a hardware module such as the KSGMs 1640-1641 respectively to perform the above operations for generating the secret.
  • the secret may be used by the encryption engines 1660 and 1661 to encrypt and decrypt data directly.
  • the encryption engines 1660-1661 send commands to the KSGMs 1640- 1641 to generate a new key stream using the secret to encrypt/decrypt each data packet (i.e., a new key stream data structure is generated for each packet).
  • the key stream generation module 1640-1641 implements a Galois/Counter Mode (GCM) in which a counter value is incremented for each data packet and is used in combination with the secret to generate the key stream.
  • GCM Galois/Counter Mode
  • the encryption engine 1661 of the IoT device 101 uses the secret and the current counter value to cause the KSGMs 1640-1641 to generate a new key stream and increment the counter value for generating the next key stream.
  • the newly-generated key stream is then used to encrypt the data packet prior to transmission to the IoT service 120.
  • the key stream is XORed with the data to generate the encrypted data packet.
  • the IoT device 101 transmits the counter value with the encrypted data packet to the IoT service 120.
  • the encryption engine 1660 on the IoT service then communicates with the KSGM 1640 which uses the received counter value and the secret to generate the key stream (which should be the same key stream because the same secret and counter value are used) and uses the generated key stream to decrypt the data packet.
  • data packets transmitted from the IoT service 120 to the IoT device 101 are encrypted in the same manner. Specifically, a counter is incremented for each data packet and used along with the secret to generate a new key stream. The key stream is then used to encrypt the data (e.g., performing an XOR of the data and the key stream) and the encrypted data packet is transmitted with the counter value to the IoT device 101.
  • the encryption engine 1661 on the IoT device 101 then communicates with the KSGM 1641 which uses the counter value and the secret to generate the same key stream which is used to decrypt the data packet.
  • the encryption engines 1660-1661 use their own counter values to generate a key stream to encrypt data and use the counter values received with the encrypted data packets to generate a key stream to decrypt the data.
  • each encryption engine 1660-1661 keeps track of the last counter value it received from the other and includes sequencing logic to detect whether a counter value is received out of sequence or if the same counter value is received more than once. If a counter value is received out of sequence, or if the same counter value is received more than once, this may indicate that a replay attack is being attempted. In response, the encryption engines 1660-1661 may disconnect from the communication channel and/or may generate a security alert.
  • Figure 18 illustrates an exemplary encrypted data packet employed in one embodiment of the invention comprising a 4-byte counter value 1800, a variable-sized encrypted data field 1801, and a 6-byte tag 1802.
  • the tag 1802 comprises a checksum value to validate the decrypted data (once it has been decrypted).
  • the session public/private key pairs 1650- 1651 exchanged between the IoT service 120 and IoT device 101 may be generated periodically and/or in response to the initiation of each new communication session.
  • One embodiment of the invention implements additional techniques for authenticating sessions between the IoT service 120 and IoT device 101.
  • hierarchy of public/private key pairs is used including a master key pair, a set of factory key pairs, and a set of IoT service key pairs, and a set of IoT device key pairs.
  • the master key pair comprises a root of trust for all of the other key pairs and is maintained in a single, highly secure location (e.g., under the control of the organization implementing the IoT systems described herein).
  • the master private key may be used to generate signatures over (and thereby authenticate) various other key pairs such as the factory key pairs. The signatures may then be verified using the master public key.
  • each factory which manufactures IoT devices is assigned its own factory key pair which may then be used to authenticate IoT service keys and IoT device keys.
  • a factory private key is used to generate a signature over IoT service public keys and IoT device public keys. These signature may then be verified using the corresponding factory public key.
  • these IoT service/device public keys are not the same as the“session” public/private keys described above with respect to Figures 16A-B.
  • the session public/private keys described above are temporary (i.e., generated for a service/device session) while the IoT service/device key pairs are permanent (i.e., generated at the factory).
  • one embodiment of the invention performs the following operations to provide additional layers of authentication and security between the IoT service 120 and IoT device 101:
  • the IoT service 120 initially generates a message containing the following:
  • the IoT service s serial number; • a Timestamp;
  • the Factory Certificate including:
  • IoT service session public key signature (e.g., signed with the IoT service's private key) B.
  • the message is sent to the IoT device on the negotiation channel (described below).
  • the IoT device parses the message and:
  • the IoT device then generates a message containing the following:
  • the IoT service then generates a message containing a signature of (IoT device session public key + IoT service session public key) signed with the IoT service's key.
  • the IoT device parses the message and:
  • the IoT device then sends a“messaging available” message. G.
  • the IoT service then does the following:
  • the IoT device receives the message and:
  • the IoT service recognizes the message payload contains a boomerang attribute update and:
  • IoT device sends a pairing complete message on the negotiator channel J.
  • IoT device receives the message and sets his paired state to true [00139] While the above techniques are described with respect to an“IoT service” and an“IoT device,” the underlying principles of the invention may be implemented to establish a secure communication channel between any two devices including user client devices, servers, and Internet services.
  • GATT is an acronym for the Generic Attribute Profile, and it defines the way that two Bluetooth Low Energy (BTLE) devices transfer data back and forth. It makes use of a generic data protocol called the Attribute Protocol (ATT), which is used to store Services, Characteristics and related data in a simple lookup table using 16-bit Characteristic IDs for each entry in the table. Note that while the“characteristics” are sometimes referred to as“attributes.”
  • ATT Attribute Protocol
  • Bluetooth devices the most commonly used characteristic is the devices “name” (having characteristic ID 10752 (0x2A00)).
  • a Bluetooth device may identify other Bluetooth devices within its vicinity by reading the“Name” characteristic published by those other Bluetooth devices using GATT.
  • Bluetooth device have the inherent ability to exchange data without formally pairing/bonding the devices (note that“paring” and“bonding” are sometimes used interchangeably; the remainder of this discussion will use the term“pairing”).
  • One embodiment of the invention takes advantage of this capability to communicate with BTLE-enabled IoT devices without formally pairing with these devices. Pairing with each individual IoT device would extremely inefficient because of the amount of time required to pair with each device and because only one paired connection may be established at a time.
  • FIG 19 illustrates one particular embodiment in which a Bluetooth (BT) device 1910 establishes a network socket abstraction with a BT communication module 1901 of an IoT device 101 without formally establishing a paired BT connection.
  • the BT device 1910 may be included in an IoT hub 110 and/or a client device 611 such as shown in Figure 16A.
  • the BT communication module 1901 maintains a data structure containing a list of characteristic IDs, names associated with those characteristic IDs and values for those characteristic IDs. The value for each characteristic may be stored within a 20-byte buffer identified by the characteristic ID in accordance with the current BT standard.
  • the underlying principles of the invention are not limited to any particular buffer size.
  • the“Name” characteristic is a BT-defined characteristic which is assigned a specific value of“IoT Device 14.”
  • One embodiment of the invention specifies a first set of additional characteristics to be used for negotiating a secure communication channel with the BT device 1910 and a second set of additional characteristics to be used for encrypted communication with the BT device 1910.
  • a“negotiation write” characteristic identified by characteristic ID ⁇ 65532> in the illustrated example, may be used to transmit outgoing negotiation messages and the “negotiation read” characteristic, identified by characteristic ID ⁇ 65533> may be used to receive incoming negotiation messages.
  • The“negotiation messages” may include messages used by the BT device 1910 and the BT communication module 1901 to establish a secure communication channel as described herein.
  • the IoT device 101 may receive the IoT service session public key 1701 via the“negotiation read” characteristic ⁇ 65533>.
  • the key 1701 may be transmitted from the IoT service 120 to a BTLE-enabled IoT hub 110 or client device 611 which may then use GATT to write the key 1701 to the negotiation read value buffer identified by characteristic ID ⁇ 65533>.
  • IoT device application logic 1902 may then read the key 1701 from the value buffer identified by characteristic ID ⁇ 65533> and process it as described above (e.g., using it to generate a secret and using the secret to generate a key stream, etc).
  • the key 1701 is greater than 20 bytes (the maximum buffer size in some current implementations), then it may be written in 20-byte portions.
  • the first 20 bytes may be written by the BT communication module 1903 to characteristic ID ⁇ 65533> and read by the IoT device application logic 1902, which may then write an acknowledgement message to the negotiation write value buffer identified by characteristic ID ⁇ 65532>.
  • the BT communication module 1903 may read this acknowledgement from characteristic ID ⁇ 65532> and responsively write the next 20 bytes of the key 1701 to the negotiation read value buffer identified by characteristic ID ⁇ 65533>.
  • a network socket abstraction defined by characteristic IDs ⁇ 65532> and ⁇ 65533> is established for exchanging negotiation messages used to establish a secure communication channel.
  • a second network socket abstraction is established using characteristic ID ⁇ 65534> (for transmitting encrypted data packets from IoT device 101) and characteristic ID ⁇ 65533> (for receiving encrypted data packets by IoT device). That is, when BT communication module 1903 has an encrypted data packet to transmit (e.g., such as encrypted message 1603 in Figure 16A), it starts writing the encrypted data packet, 20 bytes at a time, using the message read value buffer identified by characteristic ID ⁇ 65533>. The IoT device application logic 1902 will then read the encrypted data packet, 20 bytes at a time, from the read value buffer, sending acknowledgement messages to the BT communication module 1903 as needed via the write value buffer identified by characteristic ID ⁇ 65532>.
  • characteristic ID ⁇ 65534> for transmitting encrypted data packets from IoT device 101
  • characteristic ID ⁇ 65533> for receiving encrypted data packets by IoT device
  • the commands of GET, SET, and UPDATE described below are used to exchange data and commands between the two BT communication modules 1901 and 1903.
  • the BT communication module 1903 may send a packet identifying characteristic ID ⁇ 65533> and containing the SET command to write into the value field/buffer identified by characteristic ID ⁇ 65533> which may then be read by the IoT device application logic 1902.
  • the BT communication module 1903 may transmit a GET command directed to the value field/buffer identified by characteristic ID ⁇ 65534>.
  • the BT communication module 1901 may transmit an UPDATE packet to the BT communication module 1903 containing the data from the value field/buffer identified by characteristic ID ⁇ 65534>.
  • UPDATE packets may be transmitted automatically, in response to changes in a particular attribute on the IoT device 101. For example, if the IoT device is associated with a lighting system and the user turns on the lights, then an UPDATE packet may be sent to reflect the change to the on/off attribute associated with the lighting application.
  • Figure 20 illustrates exemplary packet formats used for GET, SET, and UPDATE in accordance with one embodiment of the invention.
  • these packets are transmitted over the message write ⁇ 65534> and message read ⁇ 65533> channels following negotiation.
  • a first 1-byte field includes a value (0X10) which identifies the packet as a GET packet.
  • a second 1-byte field includes a request ID, which uniquely identifies the current GET command (i.e., identifies the current transaction with which the GET command is associated).
  • each instance of a GET command transmitted from a service or device may be assigned a different request ID. This may be done, for example, by incrementing a counter and using the counter value as the request ID.
  • the underlying principles of the invention are not limited to any particular manner for setting the request ID.
  • the IoT device 101 is a security apparatus associated with
  • the SET packet 2002 and UPDATE packet 2003 illustrated in Figure 20 also include a first 1-byte field identifying the type of packet (i.e., SET and UPDATE), a second 1-byte field containing a request ID, and a 2-byte attribute ID field identifying an application-defined attribute.
  • the SET packet includes a 2-byte length value identifying the length of data contained in an n-byte value data field.
  • the value data field may include a command to be executed on the IoT device and/or configuration data to configure the operation of the IoT device in some manner (e.g., to set a desired parameter, to power down the IoT device, etc).
  • the UPDATE packet 2003 may be transmitted to provide an update of the results of the SET command.
  • the UPDATE packet 2003 includes a 2-byte length value field to identify the length of the n-byte value data field which may include data related to the results of the SET command.
  • a 1-byte update state field may identify the current state of the variable being updated. For example, if the SET command attempted to turn off a light controlled by the IoT device, the update state field may indicate whether the light was successfully turned off.
  • Figure 21 illustrates an exemplary sequence of transactions between the IoT service 120 and an IoT device 101 involving the SET and UPDATE commands.
  • the SET command 2101 is transmitted form the IoT service to the IoT device 101 and received by the BT communication module 1901 which responsively updates the GATT value buffer identified by the characteristic ID at 2102.
  • the SET command is read from the value buffer by the low power microcontroller (MCU) 200 at 2103 (or by program code being executed on the low power MCU such as IoT device application logic 1902 shown in Figure 19).
  • the MCU 200 or program code performs an operation in response to the SET command.
  • the SET command may include an attribute ID specifying a new configuration parameter such as a new temperature or may include a state value such as on/off (to cause the IoT device to enter into an“on” or a low power state).
  • a new configuration parameter such as a new temperature
  • a state value such as on/off (to cause the IoT device to enter into an“on” or a low power state).
  • the new value is set in the IoT device and an UPDATE command is returned at 2105 and the actual value is updated in a GATT value field at 2106.
  • the actual value will be equal to the desired value.
  • the updated value may be different (i.e., because it may take time for the IoT device 101 to update certain types of values).
  • the UPDATE command is transmitted back to the IoT service 120 containing the actual value from the GATT value field.
  • Figure 22 illustrates a method for implementing a secure communication channel between an IoT service and an IoT device in accordance with one embodiment of the invention.
  • the method may be implemented within the context of the network architectures described above but is not limited to any specific architecture.
  • the IoT service creates an encrypted channel to communicate with the IoT hub using elliptic curve digital signature algorithm (ECDSA) certificates.
  • the IoT service encrypts data/commands in IoT device packets using the a session secret to create an encrypted device packet.
  • the session secret may be independently generated by the IoT device and the IoT service.
  • the IoT service transmits the encrypted device packet to the IoT hub over the encrypted channel.
  • the IoT hub passes the encrypted devic packet to the IoT device.
  • the IoT device uses the session secret to decrypt the encrypted device packet.
  • this may be accomplished by using the secret and a counter value (provided with the encrypted device packet) to generate a key stream and then using the key stream to decrypt the packet.
  • the IoT device then extracts and processes the data and/or commands contained within the device packet.
  • bi-directional, secure network socket abstractions may be established between two BT-enabled devices without formally pairing the BT devices using standard pairing techniques. While these techniques are described above with respect to an IoT device 101 communicating with an IoT service 120, the underlying principles of the invention may be implemented to negotiate and establish a secure communication channel between any two BT-enabled devices.
  • Figures 23A-C illustrate a detailed method for pairing devices in accordance with one embodiment of the invention. The method may be implemented within the context of the system architectures described above, but is not limited to any specific system architectures.
  • the IoT Service creates a packet containing serial number and public key of the IoT Service.
  • the IoT Service signs the packet using the factory private key.
  • the IoT Service sends the packet over an encrypted channel to the IoT hub and at 2304 the IoT hub forwards the packet to IoT device over an unencrypted channel.
  • the IoT device verifies the signature of packet and, at 2306, the IoT device generates a packet containing the serial number and public key of the IoT Device.
  • the IoT device signs the packet using the factory private key and at 2308, the IoT device sends the packet over the unencrypted channel to the IoT hub.
  • the IoT hub forwards the packet to the IoT service over an encrypted channel and at 2310, the IoT Service verifies the signature of the packet.
  • the IoT Service generates a session key pair, and at 2312 the IoT Service generates a packet containing the session public key.
  • the IoT Service then signs the packet with IoT Service private key at 2313 and, at 2314, the IoT Service sends the packet to the IoT hub over the encrypted channel.
  • the IoT hub forwards the packet to the IoT device over the unencrypted channel at 2315 and, at 2316, the IoT device verifies the signature of packet.
  • the IoT device generates session key pair (e.g., using the techniques described above), and, at 2318, an IoT device packet is generated containing the IoT device session public key.
  • the IoT device signs the IoT device packet with IoT device private key.
  • the IoT device sends the packet to the IoT hub over the unencrypted channel and, at 2321, the IoT hub forwards the packet to the IoT service over an encrypted channel.
  • the IoT service verifies the signature of the packet (e.g., using the IoT device public key) and, at 2323, the IoT service uses the IoT service private key and the IoT device public key to generate the session secret (as described in detail above).
  • the IoT device uses the IoT device private key and IoT service public key to generate the session secret (again, as described above) and, at 2325, the IoT device generates a random number and encrypts it using the session secret.
  • the IoT service sends the encrypted packet to IoT hub over the encrypted channel.
  • the IoT hub forwards the encrypted packet to the IoT device over the unencrypted channel.
  • the IoT device decrypts the packet using the session secret.
  • the IoT device re-encrypts the packet using the session secret at 2329 and, at 2330, the IoT device sends the encrypted packet to the IoT hub over the unencrypted channel.
  • the IoT hub forwards the encrypted packet to the IoT service over the encrypted channel.
  • the IoT service decrypts the packet using the session secret at 2332.
  • the IoT service verifies that the random number matches the random number it sent.
  • the IoT service then sends a packet indicating that pairing is complete at 2334 and all subsequent messages are encrypted using the session secret at 2335.
  • 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 communication media (e.g., electrical, optical, acoustical or other form of propagated signals– such as carrier waves, infrared signals, digital signals, etc.).
  • 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
  • transitory computer machine-readable communication media e.g., electrical, optical, acoustical or other form of propagated signals– such as carrier waves, infrared signals, digital signals, etc.
  • such electronic devices typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (non-transitory machine- readable storage media), user input/output devices (e.g., a keyboard, a touchscreen, and/or a display), and network connections.
  • the coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers).
  • the storage device and signals carrying the network traffic respectively represent one or more machine-readable storage media and machine- readable communication media.
  • 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.
  • 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 Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Medical Informatics (AREA)
  • Selective Calling Equipment (AREA)
  • Telephonic Communication Services (AREA)
PCT/US2016/040819 2015-07-03 2016-07-01 Apparatus and method for establishing secure communication channels in an internet of things (iot) system WO2017007725A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201680038597.6A CN107710216B (zh) 2015-07-03 2016-07-01 用于在物联网(IoT)系统中建立安全通信信道的设备和方法
JP2018500307A JP7122964B2 (ja) 2015-07-03 2016-07-01 モノのインターネット（ＩｏＴ）システムに安全な通信チャネルを確立するための装置及び方法
KR1020187002323A KR20180025903A (ko) 2015-07-03 2016-07-01 사물 인터넷(IoT) 시스템에서 보안 통신 채널을 설정하기 위한 장치 및 방법
HK18110529.9A HK1251310A1 (zh) 2015-07-03 2018-08-16 用於在物聯網(iot)系統中建立安全通信信道的設備和方法

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US14/791,373 2015-07-03
US14/791,371 2015-07-03
US14/791,373 US9699814B2 (en) 2015-07-03 2015-07-03 Apparatus and method for establishing secure communication channels in an internet of things (IoT) system
US14/791,371 US9729528B2 (en) 2015-07-03 2015-07-03 Apparatus and method for establishing secure communication channels in an internet of things (IOT) system

Publications (1)

Publication Number Publication Date
WO2017007725A1 true WO2017007725A1 (en) 2017-01-12

Family

ID=57685680

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/040819 WO2017007725A1 (en) 2015-07-03 2016-07-01 Apparatus and method for establishing secure communication channels in an internet of things (iot) system

Country Status (5)

Country Link
JP (1) JP7122964B2 (zh)
KR (1) KR20180025903A (zh)
CN (2) CN113923052A (zh)
HK (1) HK1251310A1 (zh)
WO (1) WO2017007725A1 (zh)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018208425A1 (en) * 2017-05-11 2018-11-15 Microsoft Technology Licensing, Llc Secure cryptlet tunnel
US20180330078A1 (en) 2017-05-11 2018-11-15 Microsoft Technology Licensing, Llc Enclave pool shared key
US10238288B2 (en) 2017-06-15 2019-03-26 Microsoft Technology Licensing, Llc Direct frequency modulating radio-frequency sensors
WO2020081501A1 (en) * 2018-10-16 2020-04-23 Aeris Communications, Inc. Method and system for pairing wireless mobile device with iot device
US10637645B2 (en) 2017-05-11 2020-04-28 Microsoft Technology Licensing, Llc Cryptlet identity
US10664591B2 (en) 2017-05-11 2020-05-26 Microsoft Technology Licensing, Llc Enclave pools
WO2020139543A1 (en) * 2018-12-28 2020-07-02 T-Mobile Usa, Inc. 5g service compatible 4g sim
WO2020144527A1 (en) * 2019-01-10 2020-07-16 Innolab Engineering Sàrl Network-connectable sensing device
WO2020154205A1 (en) * 2019-01-24 2020-07-30 Zhnith Incorporated Multiple sentinels for securing communications
US10740455B2 (en) 2017-05-11 2020-08-11 Microsoft Technology Licensing, Llc Encave pool management
US10747905B2 (en) 2017-05-11 2020-08-18 Microsoft Technology Licensing, Llc Enclave ring and pair topologies
US11134376B2 (en) 2018-12-20 2021-09-28 T-Mobile Usa, Inc. 5G device compatibility with legacy SIM
US11488121B2 (en) 2017-05-11 2022-11-01 Microsoft Technology Licensing, Llc Cryptlet smart contract
US11637695B2 (en) 2017-12-29 2023-04-25 Vechain Global Technology Sarl IoT devices, block chain platforms and IoT systems for recording transportation data of objects and methods of using the same
US11716314B2 (en) 2018-12-04 2023-08-01 Citrix Systems, Inc. System and apparatus for enhanced QOS, steering and policy enforcement for HTTPS traffic via intelligent inline path discovery of TLS terminating node

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6919484B2 (ja) * 2017-10-10 2021-08-18 日本電信電話株式会社 暗号通信方法、暗号通信システム、鍵発行装置、プログラム
KR102411604B1 (ko) * 2018-03-22 2022-06-21 삼성전자주식회사 액세스 포인트 및 이의 통신 연결 방법
US11271746B2 (en) * 2018-08-01 2022-03-08 Otis Elevator Company Component commissioning to IoT hub using permissioned blockchain
CN108901023B (zh) * 2018-08-06 2021-07-09 山东华方智联科技股份有限公司 一种在物联网设备之间共享WiFi的方法及系统
RU2695487C1 (ru) * 2018-09-26 2019-07-23 Олег Дмитриевич Гурин Способ и система обеспечения взаимодействия устройств интернета вещей (iot)
CN109361507B (zh) * 2018-10-11 2021-11-02 杭州华澜微电子股份有限公司 一种数据加密方法及加密设备
CN109951479A (zh) * 2019-03-19 2019-06-28 中国联合网络通信集团有限公司 一种通信方法、设备及通信系统
US11233650B2 (en) 2019-03-25 2022-01-25 Micron Technology, Inc. Verifying identity of a vehicle entering a trust zone
US11323275B2 (en) * 2019-03-25 2022-05-03 Micron Technology, Inc. Verification of identity using a secret key
CN110012109B (zh) * 2019-04-15 2020-04-24 珠海格力电器股份有限公司 可实现高准确度的工程信息的建立方法
KR20240105515A (ko) * 2019-05-21 2024-07-05 에이치아이디 글로벌 코포레이션 물리적 액세스 제어 시스템 및 방법
US11296872B2 (en) * 2019-11-07 2022-04-05 Micron Technology, Inc. Delegation of cryptographic key to a memory sub-system
CN110933672B (zh) * 2019-11-29 2021-11-30 华为技术有限公司 一种密钥协商方法及电子设备
CN113242548B (zh) * 2021-07-09 2021-09-17 四川大学 5g网络环境下的无线物联网设备通信密钥交换方法
CN114338071A (zh) * 2021-10-28 2022-04-12 中能电力科技开发有限公司 一种基于风电场通信的网络安全身份认证方法
CN116321082A (zh) * 2021-12-21 2023-06-23 中兴通讯股份有限公司 基于短距离通信的组网方法、设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1054693A (zh) * 1990-03-07 1991-09-18 艾利森电话股份有限公司 网格通信系统的连续密码同步
US20110200188A1 (en) * 2010-02-18 2011-08-18 Lahouari Ghouti Method of performing cipher block chaining using elliptic polynomial cryptography
US20120331287A1 (en) * 2011-06-21 2012-12-27 Research In Motion Limited Provisioning a Shared Secret to a Portable Electronic Device and to a Service Entity
US20140270166A1 (en) * 2013-03-14 2014-09-18 Qualcomm Incorporated Master key encryption functions for transmitter-receiver pairing as a countermeasure to thwart key recovery attacks
US20150148989A1 (en) * 2013-11-22 2015-05-28 Qualcomm Incorporated System and method for implementing a vehicle configuration based on parameters that are specified by a mobile computing device when outside of a vehicle

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040210776A1 (en) * 2003-04-08 2004-10-21 Rachana Shah System and method for editing a profile
CN1977513B (zh) * 2004-06-29 2010-09-01 皇家飞利浦电子股份有限公司 用于有效认证医疗无线自组网节点的系统和方法
JP2006140743A (ja) * 2004-11-11 2006-06-01 Epson Toyocom Corp 共通鍵配送方法
US9590961B2 (en) * 2009-07-14 2017-03-07 Alcatel Lucent Automated security provisioning protocol for wide area network communication devices in open device environment
US8296567B2 (en) * 2009-07-15 2012-10-23 Research In Motion Limited System and method for exchanging key generation parameters for secure communications
JP5526747B2 (ja) * 2009-12-04 2014-06-18 パナソニック株式会社 復号化装置、暗号化装置、復号化方法、暗号化方法、および通信システム
TW201215070A (en) * 2010-06-14 2012-04-01 Revere Security Corp Key Management Systems and methods for shared secret ciphers
CN102316108B (zh) * 2011-09-09 2014-06-04 周伯生 建立网络隔离通道的设备及其方法
EP2792100B1 (en) * 2011-12-15 2020-07-29 Intel Corporation Method and device for secure communications over a network using a hardware security engine
US8971072B2 (en) * 2011-12-30 2015-03-03 Bedrock Automation Platforms Inc. Electromagnetic connector for an industrial control system
CN102882847B (zh) * 2012-08-24 2015-05-13 山东省计算中心 基于sd密码卡的物联网健康医疗服务系统的安全通信方法
US8762725B2 (en) * 2012-10-19 2014-06-24 Caterpillar Inc. Secure machine-to-machine communication protocol
US9438440B2 (en) * 2013-07-29 2016-09-06 Qualcomm Incorporated Proximity detection of internet of things (IoT) devices using sound chirps
CN103530767A (zh) * 2013-09-10 2014-01-22 潘之凯 一种用于计量量收费系统的信息安全方法
GB2535749B (en) * 2015-02-26 2021-10-20 Eseye Ltd Authentication module
CN104700237B (zh) * 2015-04-03 2018-05-15 成都吉普斯能源科技有限公司 一种基于物联网的车辆综合管理系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1054693A (zh) * 1990-03-07 1991-09-18 艾利森电话股份有限公司 网格通信系统的连续密码同步
US20110200188A1 (en) * 2010-02-18 2011-08-18 Lahouari Ghouti Method of performing cipher block chaining using elliptic polynomial cryptography
US20120331287A1 (en) * 2011-06-21 2012-12-27 Research In Motion Limited Provisioning a Shared Secret to a Portable Electronic Device and to a Service Entity
US20140270166A1 (en) * 2013-03-14 2014-09-18 Qualcomm Incorporated Master key encryption functions for transmitter-receiver pairing as a countermeasure to thwart key recovery attacks
US20150148989A1 (en) * 2013-11-22 2015-05-28 Qualcomm Incorporated System and method for implementing a vehicle configuration based on parameters that are specified by a mobile computing device when outside of a vehicle

Cited By (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11488121B2 (en) 2017-05-11 2022-11-01 Microsoft Technology Licensing, Llc Cryptlet smart contract
US20180332011A1 (en) 2017-05-11 2018-11-15 Microsoft Technology Licensing, Llc Secure cryptlet tunnel
US20180330078A1 (en) 2017-05-11 2018-11-15 Microsoft Technology Licensing, Llc Enclave pool shared key
WO2018208425A1 (en) * 2017-05-11 2018-11-15 Microsoft Technology Licensing, Llc Secure cryptlet tunnel
US10528722B2 (en) 2017-05-11 2020-01-07 Microsoft Technology Licensing, Llc Enclave pool shared key
US10833858B2 (en) 2017-05-11 2020-11-10 Microsoft Technology Licensing, Llc Secure cryptlet tunnel
US10637645B2 (en) 2017-05-11 2020-04-28 Microsoft Technology Licensing, Llc Cryptlet identity
US10664591B2 (en) 2017-05-11 2020-05-26 Microsoft Technology Licensing, Llc Enclave pools
US10747905B2 (en) 2017-05-11 2020-08-18 Microsoft Technology Licensing, Llc Enclave ring and pair topologies
US10740455B2 (en) 2017-05-11 2020-08-11 Microsoft Technology Licensing, Llc Encave pool management
US10238288B2 (en) 2017-06-15 2019-03-26 Microsoft Technology Licensing, Llc Direct frequency modulating radio-frequency sensors
US11637695B2 (en) 2017-12-29 2023-04-25 Vechain Global Technology Sarl IoT devices, block chain platforms and IoT systems for recording transportation data of objects and methods of using the same
WO2020081501A1 (en) * 2018-10-16 2020-04-23 Aeris Communications, Inc. Method and system for pairing wireless mobile device with iot device
US10959092B2 (en) 2018-10-16 2021-03-23 Aeris Communications, Inc. Method and system for pairing wireless mobile device with IoT device
US11716314B2 (en) 2018-12-04 2023-08-01 Citrix Systems, Inc. System and apparatus for enhanced QOS, steering and policy enforcement for HTTPS traffic via intelligent inline path discovery of TLS terminating node
US11134376B2 (en) 2018-12-20 2021-09-28 T-Mobile Usa, Inc. 5G device compatibility with legacy SIM
US11228903B2 (en) 2018-12-28 2022-01-18 T-Mobile Usa, Inc. 5G service compatible 4G SIM
WO2020139543A1 (en) * 2018-12-28 2020-07-02 T-Mobile Usa, Inc. 5g service compatible 4g sim
WO2020144527A1 (en) * 2019-01-10 2020-07-16 Innolab Engineering Sàrl Network-connectable sensing device
US11963003B2 (en) 2019-01-10 2024-04-16 Stefan Meyer Network-connectable sensing device
US11212319B2 (en) 2019-01-24 2021-12-28 Zhnith Incorporated Multiple sentinels for securing communications
WO2020154205A1 (en) * 2019-01-24 2020-07-30 Zhnith Incorporated Multiple sentinels for securing communications
US11792231B2 (en) 2019-01-24 2023-10-17 Zhnith Incorporated Multiple sentinels for securing communications

Also Published As

Publication number Publication date
JP2018525891A (ja) 2018-09-06
CN113923052A (zh) 2022-01-11
CN107710216A (zh) 2018-02-16
HK1251310A1 (zh) 2019-01-25
JP7122964B2 (ja) 2022-08-22
CN107710216B (zh) 2021-12-07
KR20180025903A (ko) 2018-03-09

Similar Documents

Publication Publication Date Title
US10659961B2 (en) Apparatus and method for sharing WiFi security data in an internet of things (IoT) system
US11153750B2 (en) Apparatus and method for sharing credentials in an internet of things (IoT) system
US10375044B2 (en) Apparatus and method for establishing secure communication channels in an internet of things (IoT) system
US10613499B2 (en) System and method for virtual internet of things (IoT) devices and hubs
US10841759B2 (en) Securely providing a password using an internet of things (IoT) system
US9699814B2 (en) Apparatus and method for establishing secure communication channels in an internet of things (IoT) system
US11221731B2 (en) System and method for sharing internet of things (IOT) devices
US10776080B2 (en) Integrated development tool for an internet of things (IOT) system
US10116573B2 (en) System and method for managing internet of things (IoT) devices and traffic using attribute classes
US10455452B2 (en) System and method for flow control in an internet of things (IoT) system
US10447784B2 (en) Apparatus and method for modifying packet interval timing to identify a data transfer condition
WO2017007725A1 (en) Apparatus and method for establishing secure communication channels in an internet of things (iot) system
US10405150B2 (en) System and method for reducing wireless traffic when connecting an IoT hub to an IoT device
US9858213B2 (en) Interface and method for efficient communication between a microcontroller and a communication module
US10146978B2 (en) Apparatus and method for accurate barcode scanning using dynamic timing feedback
WO2017106224A1 (en) System and method for secure internet of things (iot) device provisioning
US20170171241A1 (en) Apparatus and method for obscuring wireless communication patterns
US9626543B1 (en) Apparatus and method for accurate barcode scanning using dynamic timing feedback
US10116549B2 (en) Apparatus and method for modifying packet interval timing based on device characteristics

Legal Events

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

Ref document number: 16821857

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018500307

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20187002323

Country of ref document: KR

Kind code of ref document: A

122 Ep: pct application non-entry in european phase

Ref document number: 16821857

Country of ref document: EP

Kind code of ref document: A1