Nothing Special   »   [go: up one dir, main page]

WO2017210120A1 - Outil de développement intégré à fonctionnalité de prévisualisation pour un système de l'internet des objets (ido) - Google Patents

Outil de développement intégré à fonctionnalité de prévisualisation pour un système de l'internet des objets (ido) Download PDF

Info

Publication number
WO2017210120A1
WO2017210120A1 PCT/US2017/034734 US2017034734W WO2017210120A1 WO 2017210120 A1 WO2017210120 A1 WO 2017210120A1 US 2017034734 W US2017034734 W US 2017034734W WO 2017210120 A1 WO2017210120 A1 WO 2017210120A1
Authority
WO
WIPO (PCT)
Prior art keywords
lot
user
lot device
service
attributes
Prior art date
Application number
PCT/US2017/034734
Other languages
English (en)
Inventor
Erhard RIEDL
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 US15/172,459 external-priority patent/US9841968B1/en
Priority claimed from US15/172,520 external-priority patent/US9846577B1/en
Application filed by Afero, Inc. filed Critical Afero, Inc.
Publication of WO2017210120A1 publication Critical patent/WO2017210120A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates

Definitions

  • This invention relates generally to the field of computer systems. More particularly, the invention relates to an integrated development tool with preview functionality for an Internet of Things (loT) system.
  • LoT Internet of Things
  • the "Internet of Things” refers to the interconnection of uniquely-identifiable embedded devices within the Internet infrastructure. Ultimately, loT is expected to result in new, wide-ranging types of applications in which virtually any type of physical thing may provide information about itself or its surroundings and/or may be controlled remotely via client devices over the Internet.
  • loT development and adoption has been slow due to issues related to connectivity, power, and a lack of standardization.
  • one obstacle to loT development and adoption is that no standard platform exists to allow developers to design and offer new loT devices and services.
  • a developer In order enter into the loT market, a developer must design the entire loT platform from the ground up, including the network protocols and infrastructure, hardware, software and services required to support the desired loT implementation.
  • each provider of loT devices uses proprietary techniques for designing and connecting the loT devices, making the adoption of multiple types of loT devices burdensome for end users.
  • developers are expected to generate one set of program code for the loT device, another set of program code for an loT service, and yet another set of program code for a client-based user interface, resulting in significant inefficiencies.
  • FIGS. 1 A-B illustrates different embodiments of an loT system architecture
  • FIG. 2 illustrates an loT device in accordance with one embodiment of the invention
  • FIG. 3 illustrates an loT hub in accordance with one embodiment of the invention
  • FIG. 4A-B illustrate embodiments of the invention for controlling and collecting data from loT devices, and generating notifications
  • FIG. 5 illustrates embodiments of the invention for collecting data from loT devices and generating notifications from an loT hub and/or loT service
  • FIG. 6 illustrates one embodiment of a system in which an intermediary mobile device collects data from a stationary loT device and provides the data to an loT 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 loT device
  • FIG. 9B illustrates an embodiment of a method in which program code and data updates are provided to the loT 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 loT devices;
  • SIM subscriber identity module
  • FIG. 12A illustrates one embodiment in which loT 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 loT hub
  • FIG. 14 illustrates one embodiment of a method for registering an loT device with an loT hub and loT service
  • FIG. 15 illustrates one embodiment of a method for encrypting data to be transmitted to an loT device
  • FIGS. 16A-B illustrate different embodiments of the invention for encrypting data between an loT service and an loT 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 loT device without formally pairing with the loT 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
  • FIG. 24 illustrates one embodiment of an interface between a microcontroller unit and a secure communication module
  • FIG. 25 illustrates additional details for an embodiment of an interface between a microcontroller unit and a secure communication module
  • FIG. 26 illustrates a communication format employed in one embodiment of the invention
  • FIG. 27 illustrates an integrated development tool in accordance with one embodiment of the invention
  • FIG 28 illustrates a method in accordance with one embodiment of the invention
  • FIG. 29 illustrates one embodiment in which different types of attributes are utilized and synchronized between an loT device and loT service
  • FIG. 30 illustrates an one embodiment of the invention for generating a preview on a mobile app
  • FIGS. 31A-H illustrates exemplary interactions between a preview user interface of an integrated development application and a mobile app
  • FIGS. 32A-B illustrate a method in accordance with one embodiment of the invention.
  • One embodiment of the invention comprises an Internet of Things (loT) platform which may be utilized by developers to design and build new loT devices and applications.
  • a base hardware/software platform for loT devices including a predefined networking protocol stack and an loT hub through which the loT devices are coupled to the Internet.
  • one embodiment includes an loT service through which the loT hubs and connected loT devices may be accessed and managed as described below.
  • the loT platform includes an loT app or Web application (e.g., executed on a client device) to access and configured the loT service, hub and connected devices.
  • existing online retailers and other Website operators may leverage the loT platform described herein to readily provide unique loT functionality to existing user bases.
  • Figure 1 A illustrates an overview of an architectural platform on which embodiments of the invention may be implemented.
  • the illustrated embodiment includes a plurality of loT devices 101 -105 communicatively coupled over local communication channels 130 to a central loT hub 1 10 which is itself
  • the loT service 120 includes an end user database 122 for maintaining user account information and data collected from each user's loT devices.
  • the loT devices include sensors (e.g., temperature sensors, accelerometers, heat sensors, motion detectore, etc)
  • the database 122 may be continually updated to store the data collected by the loT devices 101 -105.
  • the data stored in the database 122 may then be made accessible to the end user via the loT app or browser installed on the user's device 135 (or via a desktop or other client computer system) and to web clients (e.g., such as websites 130 subscribing to the loT service 120).
  • the loT app or browser installed on the user's device 135 (or via a desktop or other client computer system) and to web clients (e.g., such as websites 130 subscribing to the loT service 120).
  • the loT devices 101 -105 may be equipped with various types of sensors to collect information about themselves and their surroundings and provide the collected information to the loT service 120, user devices 135 and/or external Websites 130 via the loT hub 1 10. Some of the loT devices 101 -105 may perform a specified function in response to control commands sent through the loT hub 1 10. Various specific examples of information collected by the loT devices 101 -105 and control commands are provided below.
  • the loT device 101 is a user input device designed to record user selections and send the user selections to the loT service 120 and/or Website.
  • the loT hub 1 10 includes a cellular radio to establish a connection to the Internet 220 via a cellular service 1 15 such as a 4G (e.g., Mobile WiMAX, LTE) or 5G cellular data service.
  • a cellular service 1 15 such as a 4G (e.g., Mobile WiMAX, LTE) or 5G cellular data service.
  • the loT hub 1 10 may include a WiFi radio to establish a WiFi connection through a WiFi access point or router 1 16 which couples the loT hub 1 10 to the Internet (e.g., via an Internet Service Provider providing Internet service to the end user).
  • a WiFi radio to establish a WiFi connection through a WiFi access point or router 1 16 which couples the loT hub 1 10 to the Internet (e.g., via an Internet Service Provider providing Internet service to the end user).
  • the underlying principles of the invention are not limited to any particular type of communication channel or protocol.
  • the loT devices 101 -105 are ultra low-power devices capable of operating for extended periods of time on battery power (e.g., years).
  • the local communication channels 130 may be implemented using a low-power wireless communication technology such as Bluetooth Low Energy (LE).
  • LE Bluetooth Low Energy
  • each of the loT devices 101 -105 and the loT hub 1 10 are equipped with Bluetooth LE radios and protocol stacks.
  • the loT platform includes an loT app or Web application executed on user devices 135 to allow users to access and configure the connected loT devices 101 -105, loT hub 1 10, and/or loT service 120.
  • the app or web application may be designed by the operator of a Website 130 to provide loT functionality to its user base.
  • the Website may maintain a user database 131 containing account records related to each user.
  • Figure 1 B illustrates additional connection options for a plurality of loT hubs 1 10-1 1 1 , 190
  • a single user may have multiple hubs 1 10-1 1 1 installed onsite at a single user premises 180 (e.g., the user's home or business). This may be done, for example, to extend the wireless range needed to connect all of the loT devices 101 -105.
  • a user may be connected via a local communication channel (e.g., Wifi, Ethernet, Power Line
  • each of the hubs 1 10-1 1 1 may establish a direct connection to the loT service 120 through a cellular 1 15 or WiFi 1 16 connection (not explicitly shown in Figure 1 B).
  • one of the loT hubs such as loT hub 1 10 may act as a "master" hub which provides connectivity and/or local services to all of the other loT hubs on the user premises 180, such as loT hub 1 1 1 (as indicated by the dotted line connecting loT hub 1 10 and loT hub 1 1 1 ).
  • the master loT hub 1 10 may be the only loT hub to establish a direct connection to the loT service 120.
  • the master loT hub 1 10 is equipped with a cellular communication interface to establish the connection to the loT service 120. As such, all communication between the loT service 120 and the other loT hubs 1 1 1 will flow through the master loT hub 1 10.
  • the master loT hub 1 10 may be provided with additional program code to perform filtering operations on the data exchanged between the other loT hubs 1 1 1 and loT service 120 (e.g., servicing some data requests locally when possible).
  • the loT service 120 will logically associate the hubs with the user and combine all of the attached loT devices 101 -105 under a single comprehensive user interface, accessible via a user device with the installed app 135 (and/or a browser-based interface).
  • the master loT hub 1 10 and one or more slave loT hubs 1 1 1 may connect over a local network which may be a WiFi network 1 16, an Ethernet network, and/or a using power-line communications (PLC) networking (e.g., where all or portions of the network are run through the user's power lines).
  • a local network which may be a WiFi network 1 16, an Ethernet network, and/or a using power-line communications (PLC) networking (e.g., where all or portions of the network are run through the user's power lines).
  • PLC power-line communications
  • each of the loT devices 101 -105 may be interconnected with the loT hubs 1 10-1 1 1 using any type of local network channel such as WiFi, Ethernet, PLC, or Bluetooth LE, to name a few.
  • Figure 1 B also shows an loT hub 190 installed at a second user premises 181 .
  • loT hubs 190 may be installed and configured to collect data from loT devices 191 -192 at user premises around the world.
  • the two user premises 180-181 may be configured for the same user.
  • one user premises 180 may be the user's primary home and the other user premises 181 may be the user's vacation home.
  • the loT service 120 will logically associate the loT hubs 1 10-1 1 1 , 190 with the user and combine all of the attached loT devices 101 -105, 191 -192 under a single comprehensive user interface, accessible via a user device with the installed app 135 (and/or a browser-based interface).
  • an exemplary embodiment of an loT device 101 includes a memory 210 for storing program code and data 201 -203 and a low power microcontroller 200 for executing the program code and processing the data.
  • the memory 210 may be a volatile memory such as dynamic random access memory (DRAM) or may be a non-volatile memory such as Flash memory.
  • DRAM dynamic random access memory
  • Flash memory non-volatile memory
  • a non-volatile memory may be used for persistent storage and a volatile memory may be used for execution of the program code and data at runtime.
  • the memory 210 may be integrated within the low power microcontroller 200 or may be coupled to the low power microcontroller 200 via a bus or communication fabric. The underlying principles of the invention are not limited to any particular implementation of the memory 210.
  • the program code may include application program code 203 defining an application-specific set of functions to be performed by the loT device 201 and library code 202 comprising a set of predefined building blocks which may be utilized by the application developer of the loT device 101 .
  • the library code 202 comprises a set of basic functions required to implement an loT device such as a communication protocol stack 201 for enabling communication between each loT device 101 and the loT hub 1 10.
  • the loT device such as a communication protocol stack 201 for enabling communication between each loT device 101 and the loT hub 1 10.
  • Bluetooth LE radio and antenna 207 may be integrated within the low power microcontroller 200.
  • the underlying principles of the invention are not limited to any particular communication protocol.
  • the particular embodiment shown in Figure 2 also includes a plurality of input devices or sensors 210 to receive user input and provide the user input to the low power microcontroller, which processes the user input in accordance with the application code 203 and library code 202.
  • each of the input devices include an LED 209 to provide feedback to the end user.
  • the illustrated embodiment includes a battery 208 for supplying power to the low power microcontroller.
  • a battery 208 for supplying power to the low power microcontroller.
  • a non-chargeable coin cell battery is used.
  • an integrated rechargeable battery may be used (e.g., rechargeable by connecting the loT device to an AC power supply (not shown)).
  • a speaker 205 is also provided for generating audio.
  • the low power microcontroller 299 includes audio decoding logic for decoding a compressed audio stream (e.g., such as an MPEG-4/Advanced Audio Coding (AAC) stream) to generate audio on the speaker 205.
  • AAC Advanced Audio Coding
  • the low power microcontroller 200 and/or the application code/data 203 may include digitally sampled snippets of audio to provide verbal feedback to the end user as the user enters selections via the input devices 210.
  • one or more other/alternate I/O devices or sensors 250 may be included on the loT device 101 based on the particular application for which the loT device 101 is designed.
  • an environmental sensor may be included to measure temperature, pressure, humidity, etc.
  • a security sensor and/or door lock opener may be included if the loT device is used as a security device.
  • these examples are provided merely for the purposes of illustration.
  • the underlying principles of the invention are not limited to any particular type of loT device.
  • an application developer may readily develop new application code 203 and new I/O devices 250 to interface with the low power microcontroller for virtually any type of loT application.
  • the low power microcontroller 200 also includes a secure key store for storing encryption keys for encrypting communications and/or generating signatures.
  • the keys may be secured in a subscriber identify module (SIM).
  • SIM subscriber identify module
  • a wakeup receiver 207 is included in one embodiment to wake the loT device from an ultra low power state in which it is consuming virtually no power.
  • the wakeup receiver 207 is configured to cause the loT device 101 to exit this low power state in response to a wakeup signal received from a wakeup transmitter 307 configured on the loT hub 1 10 as shown in Figure 3.
  • the transmitter 307 and receiver 207 together form an electrical resonant transformer circuit such as a Tesla coil. In operation, energy is transmitted via radio frequency signals from the transmitter 307 to the receiver 207 when the hub 1 10 needs to wake the loT device 101 from a very low power state.
  • the loT device 101 may be configured to consume virtually no power when it is in its low power state because it does not need to continually "listen" for a signal from the hub (as is the case with network protocols which allow devices to be awakened via a network signal). Rather, the microcontroller 200 of the loT device 101 may be configured to wake up after being effectively powered down by using the energy electrically transmitted from the transmitter 307 to the receiver 207.
  • the loT hub 1 10 also includes a memory 317 for storing program code and data 305 and hardware logic 301 such as a microcontroller for executing the program code and processing the data.
  • a wide area network (WAN) interface 302 and antenna 310 couple the loT hub 1 10 to the cellular service 1 15.
  • WAN wide area network
  • the loT hub 1 10 may also include a local network interface (not shown) such as a WiFi interface (and WiFi antenna) or Ethernet interface for establishing a local area network communication channel.
  • the hardware logic 301 also includes a secure key store for storing encryption keys for encrypting communications and generating/verifying signatures. Alternatively, the keys may be secured in a subscriber identify module (SIM).
  • SIM subscriber identify module
  • a local communication interface 303 and antenna 31 1 establishes local communication channels with each of the loT devices 101 -105.
  • the local communication interface 303/antenna 31 1 implements the Bluetooth LE standard.
  • the underlying principles of the invention are not limited to any particular protocols for establishing the local communication channels with the loT devices 101 -105.
  • the WAN interface 302 and/or local communication interface 303 may be embedded within the same chip as the hardware logic 301 .
  • the program code and data includes a communication protocol stack 308 which may include separate stacks for communicating over the local communication interface 303 and the WAN interface 302.
  • device pairing program code and data 306 may be stored in the memory to allow the loT hub to pair with new loT devices.
  • each new loT device 101 -105 is assigned a unique code which is communicated to the loT hub 1 10 during the pairing process.
  • the unique code may be embedded in a barcode on the loT device and may be read by the barcode reader 106 or may be communicated over the local
  • the unique ID code is embedded magnetically on the loT device and the loT hub has a magnetic sensor such as an radio frequency ID (RFID) or near field communication (NFC) sensor to detect the code when the loT device 101 is moved within a few inches of the loT hub 1 10.
  • RFID radio frequency ID
  • NFC near field communication
  • the loT hub 1 10 may verify the unique ID by querying a local database (not shown), performing a hash to verify that the code is acceptable, and/or communicating with the loT service 120, user device 135 and/or Website 130 to validate the ID code. Once validated, in one embodiment, the loT hub 1 10 pairs the loT device 101 and stores the pairing data in memory 317 (which, as mentioned, may include non-volatile memory). Once pairing is complete, the loT hub 1 10 may connect with the loT device 101 to perform the various loT functions described herein.
  • the organization running the loT service 120 may provide the loT hub 1 10 and a basic hardware/software platform to allow developers to easily design new loT services.
  • developers may be provided with a software development kit (SDK) to update the program code and data 305 executed within the hub 1 10.
  • the SDK may include an extensive set of library code 202 designed for the base loT hardware (e.g., the low power microcontroller 200 and other components shown in Figure 2) to facilitate the design of various different types of applications 101 .
  • the SDK includes a graphical design interface in which the developer needs only to specify input and outputs for the loT device.
  • the SDK also includes a library code base to facilitate the design of apps for mobile devices (e.g., iPhone and Android devices).
  • the loT hub 1 10 manages a continuous bi-directional stream of data between the loT devices 101 -105 and the loT service 120.
  • the loT hub may maintain an open TCP socket to provide regular updates to the user device 135 and/or external Websites 130.
  • the specific networking protocol used to provide updates may be tweaked based on the needs of the underlying application. For example, in some cases, where may not make sense to have a continuous bi-directional stream, a simple request/response protocol may be used to gather information when needed.
  • both the loT hub 1 10 and the loT devices 101 -105 are automatically upgradeable over the network.
  • a new update is available for the loT hub 1 10 it may automatically download and install the update from the loT service 120. It may first copy the updated code into a local memory, run and verify the update before swapping out the older program code.
  • updates are available for each of the loT devices 101 -105, they may initially be downloaded by the loT hub 1 10 and pushed out to each of the loT devices 101 -105. Each loT device 101 -105 may then apply the update in a similar manner as described above for the loT hub and report back the results of the update to the loT hub 1 10. If the update is successful, then the loT hub 1 10 may delete the update from its memory and record the latest version of code installed on each loT device (e.g., so that it may continue to check for new updates for each loT device).
  • the loT hub 1 10 is powered via A/C power.
  • the loT hub 1 10 may include a power unit 390 with a transformer for transforming A/C voltage supplied via an A/C power cord to a lower DC voltage.
  • Figure 4A illustrates one embodiment of the invention for performing universal remote control operations using the loT system.
  • a set of loT devices 101 -103 are equipped with infrared (IR) and/or radio frequency (RF) blasters 401 -403, respectively, for transmitting remote control codes to control various different types of electronics equipment including air
  • the loT devices 101 -103 are also equipped with sensors 404-406, respectively, for detecting the operation of the devices which they control, as described below.
  • sensor 404 in loT device 101 may be a temperature and/or humidity sensor for sensing the current temperature/humidity and responsively controlling the air conditioner/heater 430 based on a current desired temperature.
  • the air conditioner/heater 430 is one which is designed to be controlled via a remote control device (typically a remote control which itself has a temperature sensor embedded therein).
  • the user provides the desired temperature to the loT hub 1 10 via an app or browser installed on a user device 135.
  • Control logic 412 executed on the loT hub 1 10 receives the current
  • temperature/humidity data from the sensor 404 and responsively transmits commands to the loT device 101 to control the IR/RF blaster 401 in accordance with the desired temperature/humidity. For example, if the temperature is below the desired
  • control logic 412 may transmit a command to the air
  • the command may include the necessary remote control code stored in a database 413 on the loT hub 1 10.
  • the loT service 421 may implement control logic 421 to control the electronics equipment 430-432 based on specified user preferences and stored control codes 422.
  • loT device 102 in the illustrated example is used to control lighting 431 .
  • sensor 405 in loT device 102 may photosensor or photodetector configured to detect the current brightness of the light being produced by a light fixture 431 (or other lighting apparatus).
  • the user may specify a desired lighting level (including an indication of ON or OFF) to the loT hub 1 10 via the user device 135.
  • the control logic 412 will transmit commands to the IR/RF blaster 402 to control the current brightness level of the lights 431 (e.g., increasing the lighting if the current brightness is too low or decreasing the lighting if the current brightness is too high; or simply turning the lights ON or OFF).
  • loT device 103 in the illustrated example is configured to control audiovisual equipment 432 (e.g., a television, A/V receiver, cable/satellite receiver, AppleTVTM, etc).
  • Sensor 406 in loT device 103 may be an audio sensor (e.g., a microphone and associated logic) for detecting a current ambient volume level and/or a photosensor to detect whether a television is on or off based on the light generated by the television (e.g., by measuring the light within a specified spectrum).
  • sensor 406 may include a temperature sensor connected to the audiovisual equipment to detect whether the audio equipment is on or off based on the detected temperature.
  • the control logic 412 may transmit commands to the audiovisual equipment via the IR blaster 403 of the loT device 103.
  • the sensor data and commands are sent over the Bluetooth LE channel.
  • the underlying principles of the invention are not limited to Bluetooth LE or any other communication standard.
  • control codes required to control each of the pieces of electronics equipment are stored in a database 413 on the loT hub 1 10 and/or a database 422 on the loT service 120.
  • the control codes may be provided to the loT hub 1 10 from a master database of control codes 422 for different pieces of equipment maintained on the loT service 120.
  • the end user may specify the types of electronic (or other) equipment to be controlled via the app or browser executed on the user device 135 and, in response, a remote control code learning module 491 on the loT hub may retrieve the required IR/RF codes from the remote control code database 492 on the loT service 120 (e.g., identifying each piece of electronic equipment with a unique ID).
  • the loT hub 1 10 is equipped with an IR/RF interface 490 to allow the remote control code learning module 491 to "learn" new remote control codes directly from the original remote control 495 provided with the electronic equipment.
  • the remote control code learning module 491 may interact with the loT hub 1 10 via the app/browser on the user device 135 to teach the loT hub 1 10 the various control codes generated by the original remote control (e.g., increase temperature, decrease temperature, etc).
  • the remote control codes may be stored in the control code database 413 on the loT hub 1 10 and/or sent back to the loT service 120 to be included in the central remote control code database 492 (and subsequently used by other users with the same air conditioner unit 430).
  • each of the loT devices 101 -103 have an extremely small form factor and may be affixed on or near their respective electronics equipment 430-432 using double-sided tape, a small nail, a magnetic attachment, etc.
  • the loT device 101 For control of a piece of equipment such as the air conditioner 430, it would be desirable to place the loT device 101 sufficiently far away so that the sensor 404 can accurately measure the ambient temperature in the home (e.g., placing the loT device directly on the air conditioner would result in a temperature measurement which would be too low when the air conditioner was running or too high when the heater was running).
  • the loT device 102 used for controlling lighting may be placed on or near the lighting fixture 431 for the sensor 405 to detect the current lighting level.
  • one embodiment of the loT hub 1 10 and/or loT service 120 transmits notifications to the end user related to the current status of each piece of electronics equipment.
  • the notifications which may be text messages and/or app-specific notifications, may then be displayed on the display of the user's mobile device 135. For example, if the user's air conditioner has been on for an extended period of time but the temperature has not changed, the loT hub 1 10 and/or loT service 120 may send the user a notification that the air conditioner is not functioning properly.
  • a notification may be sent to the user, asking if the user would like to turn off the audiovisual equipment 432 and/or lights 431 .
  • the same type of notification may be sent for any equipment type.
  • the user may remotely control the electronics equipment 430-432 via the app or browser on the user device 135.
  • the user device 135 is a touchscreen device and the app or browser displays an image of a remote control with user-selectable buttons for controlling the equipment 430-432.
  • the user may open the graphical remote control and turn off or adjust the various different pieces of equipment.
  • the user's selections may be forwarded from the loT service 120 to the loT hub 1 10 which will then control the equipment via the control logic 412.
  • the user input may be sent directly to the loT hub 1 10 from the user device 135.
  • the user may program the control logic 412 on the loT hub 1 10 to perform various automatic control functions with respect to the electronics equipment 430-432.
  • the control logic 412 may automatically turn off the electronics equipment if certain conditions are detected. For example, if the control logic 412 detects that the user is not home and that the air conditioner is not functioning, it may automatically turn off the air conditioner. Similarly, if the user is not home, and the sensors 406 indicate that audiovisual equipment 430 is on or sensors 405 indicate that the lights are on, then the control logic 412 may automatically transmit commands via the IR/RF blasters 403 and 402, to turn off the audiovisual equipment and lights, respectively.
  • FIG. 5 illustrates additional embodiments of loT devices 104-105 equipped with sensors 503-504 for monitoring electronic equipment 530-531 .
  • the loT device 104 of this embodiment includes a temperature sensor 503 which may be placed on or near a stove 530 to detect when the stove has been left on.
  • the loT device 104 transmits the current temperature measured by the temperature sensor 503 to the loT hub 1 10 and/or the loT service 120. If the stove is detected to be on for more than a threshold time period (e.g., based on the measured temperature), then control logic 512 may transmit a notification to the end user's device 135 informing the user that the stove 530 is on.
  • a threshold time period e.g., based on the measured temperature
  • the loT device 104 may include a control module 501 to turn off the stove, either in response to receiving an instruction from the user or automatically (if the control logic 512 is programmed to do so by the user).
  • the control logic 501 comprises a switch to cut off electricity or gas to the stove 530.
  • the control logic 501 may be integrated within the stove itself.
  • Figure 5 also illustrates an loT device 105 with a motion sensor 504 for detecting the motion of certain types of electronics equipment such as a washer and/or dryer.
  • a motion sensor 504 for detecting the motion of certain types of electronics equipment such as a washer and/or dryer.
  • Another sensor that may be used is an audio sensor (e.g., microphone and logic) for detecting an ambient volume level.
  • this embodiment may transmit notifications to the end user if certain specified conditions are met (e.g., if motion is detected for an extended period of time, indicating that the washer/dryer are not turning off).
  • loT device 105 may also be equipped with a control module to turn off the washer/dryer 531 (e.g., by switching off electric/gas), automatically, and/or in response to user input.
  • a first loT device with control logic and a switch may be configured to turn off all power in the user's home and a second loT device with control logic and a switch may be configured to turn off all gas in the user's home.
  • loT devices with sensors may then be positioned on or near electronic or gas-powered equipment in the user's home. If the user is notified that a particular piece of equipment has been left on (e.g., the stove 530), the user may then send a command to turn off all electricity or gas in the home to prevent damage.
  • the control logic 512 in the loT hub 1 10 and/or the loT service 120 may be configured to automatically turn off electricity or gas in such situations.
  • the loT hub 1 10 and loT service 120 communicate at periodic intervals. If the loT service 120 detects that the connection to the loT hub 1 10 has been lost (e.g., by failing to receive a request or response from the loT hub for a specified duration), it will communicate this information to the end user's device 135 (e.g., by sending a text message or app-specific notification).
  • loT devices such as Bluetooth LE are generally short range technologies, if the hub for an loT implementation is outside the range of an loT device, the loT device will not be able to transmit data to the loT hub (and vice versa).
  • one embodiment of the invention provides a mechanism for an loT device which is outside of the wireless range of the loT hub to periodically connect with one or more mobile devices when the mobile devices are within range. Once connected, the loT device can transmit any data which needs to be provided to the loT hub to the mobile device which then forwards the data to the loT hub.
  • one embodiment includes an loT hub 1 10, an loT device 601 which is out of range of the loT hub 1 10 and a mobile device 61 1 .
  • the out of range loT device 601 may include any form of loT device capable of collecting and communicating data.
  • the loT 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 loT device.
  • the techniques described herein may be implemented using any type of loT 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 mobile device 61 1 illustrated in Figure 6 may be any form of mobile device capable of communicating and storing data.
  • the mobile device 61 1 is a smartphone with an app installed thereon to facilitate the techniques described herein.
  • the mobile device 61 1 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 loT device 601 may periodically or continually check for connectivity with a mobile device 61 1 .
  • any collected data 605 on the loT device 601 is automatically transmitted to a temporary data repository 615 on the mobile device 61 1 .
  • the loT device 601 and mobile device 61 1 establish a local wireless communication channel using a low power wireless standard such as BTLE.
  • the mobile device 61 1 may initially be paired with the loT device 601 using known pairing techniques.
  • the mobile device 61 1 will transmit the data once communication is established with the loT hub 1 10 (e.g., when the user walks within the range of the loT hub 1 10).
  • the loT 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 61 1 may use a different type of communication channel to provide the data to the loT hub 1 10 (potentially a higher power communication channel such as WiFi).
  • the out of range loT device 601 , the mobile device 61 1 , and the loT hub may all be configured with program code and/or logic to implement the techniques described herein.
  • the loT device 601 may be configured with intermediary connection logic and/or application
  • the mobile device 61 1 may be configured with an intermediary connection logic/application
  • the loT hub 1 10 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 loT device 601 searches and establishes a connection with the intermediary connection
  • the intermediary connection logic/application 701 on the mobile device 61 1 then forwards the data to the
  • the intermediary connection logic/applications 701 , 71 1 , 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 loT device 601 may be configured to establish a wireless connection with one or more intermediary loT devices, which are located within range of the loT hub 1 10.
  • any loT devices 601 out of range of the loT hub may be linked to the hub by forming a "chain" using other loT 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 loT system may be used to track the behavior of different users within the home.
  • the collected data 605 may then include the identity 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 loT 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 loT hub and/or forwarded to an external service or user.
  • the mobile device 61 1 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 loT hub 1 10 via the token. The loT 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 loT hub 1 10 or an external service connected to the loT 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 loT device which is out of range of the loT hub periodically collects data (e.g., opening of the refrigerator door, food items used, etc).
  • the loT 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 loT 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 loT devices.
  • Figure 9A shows an loT hub 1 10 with program code updates 901 that need to be installed on an loT device 601 (or a group of such loT devices).
  • the program code updates may include system updates, patches, configuration data and any other data needed for the loT device to operate as desired by the user.
  • the user may specify configuration options for the loT device 601 via a mobile device or computer which are then stored on the loT hub 1 10 and provided to the loT device using the techniques described herein.
  • the intermediary connection logic/application 721 on the loT hub 1 10 communicates with the intermediary connection logic/application 71 1 on the mobile device 61 1 to store the program code updates within a temporary storage 615.
  • the intermediary connection logic/application 71 1 on the mobile device 61 1 connects with the
  • the intermediary/connection logic/application 701 on the loT device 601 may then enter into an automated update process to install the new program code updates and/or data.
  • FIG. 9B A method for updating an loT 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 loT 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 loT device.
  • the loT 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 loT device and installed.
  • the low power microcontroller 200 of each loT device 101 and the low power logic/microcontroller 301 of the loT hub 1 10 include a secure key store for storing encryption keys used by the embodiments described below (see, e.g., Figures 10-15 and associated text). Alternatively, the keys may be secured in a subscriber identify module (SIM) as discussed below.
  • SIM subscriber identify module
  • Figure 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 loT Service 120, the loT hub 1 10 and the loT devices 101 -102.
  • PKI public key infrastructure
  • Embodiments which use public/private key pairs will first be described, followed by embodiments which use symmetric key exchange/encryption techniques.
  • a unique public/private key pair is associated with each loT device 101 -102, each loT hub 1 10 and the loT service 120.
  • a new loT hub 1 10 when a new loT hub 1 10 is set up, its public key is provided to the loT service 120 and when a new loT device 101 is set up, it's public key is provided to both the loT hub 1 10 and the loT service 120.
  • Various techniques for securely exchanging the public keys between devices are described below.
  • all public keys are signed by a master key known to all of the receiving devices (i.e., a form of certificate) so that any receiving device can verify the validity of the public keys by validating the signatures.
  • a master key known to all of the receiving devices (i.e., a form of certificate) so that any receiving device can verify the validity of the public keys by validating the signatures.
  • each loT device 101 , 102 includes a secure key storage 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 loT hub 1 10 includes a secure storage 101 1 for storing the loT hub private key and the public keys of the loT devices 101 -102 and the loT service 120; as well as security logic 1012 for using the keys to perform encryption/decryption operations.
  • the loT service 120 may include a secure storage 1021 for security storing its own private key, the public keys of various loT devices and loT hubs, and a security logic 1013 for using the keys to encrypt/decrypt communication with loT hubs and devices.
  • a secure storage 1021 for security storing its own private key, the public keys of various loT devices and loT hubs, and a security logic 1013 for using the keys to encrypt/decrypt communication with loT hubs and devices.
  • the loT hub 1 10 when the loT hub 1 10 receives a public key certificate from an loT device it can verify it (e.g., by validating the signature using the master key as described above), and then extract the public key from within it and store that public key in it's secure key store 101 1 .
  • the security logic 1013 encrypts the data/command using the public key of the loT device 101 to generate an encrypted loT device packet. In one embodiment, it then encrypts the loT device packet using the public key of the loT hub 1 10 to generate an loT hub packet and transmits the loT hub packet to the loT hub 1 10.
  • the service 120 signs the encrypted message with it's private key or the master key mentioned above so that the device 101 can verify it is receiving an unaltered message from a trusted source.
  • the device 101 may then validate the signature using the public key corresponding to the private key and/or the master key.
  • symmetric key exchange/encryption techniques may be used instead of public/private key encryption.
  • the devices may each be provided with a copy of the same symmetric key to be used for encryption and to validate signatures.
  • AES Advanced Encryption Standard
  • each device 101 enters into a secure key exchange protocol to exchange a symmetric key with the loT hub 1 10.
  • a secure key provisioning protocol such as the Dynamic Symmetric Key Provisioning Protocol (DSKPP) may be used to exchange the keys over a secure communication channel (see, e.g., Request for Comments (RFC) 6063).
  • RRC Request for Comments
  • the underlying principles of the invention are not limited to any particular key provisioning protocol.
  • the symmetric keys may be used by each device 101 and the loT hub 1 10 to encrypt communications.
  • the loT hub 1 10 and loT service 120 may perform a secure symmetric key exchange and then use the exchanged symmetric keys to encrypt communications.
  • a new symmetric key is exchanged periodically between the devices 101 and the hub 1 10 and between the hub 1 10 and the loT service 120.
  • a new symmetric key is exchanged with each new communication session between the devices 101 , the hub 1 10, and the service 120 (e.g., a new key is generated and securely exchanged for each communication session).
  • the service 120 could negotiate a session key with the hub security module 1312 and then the security module 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 1 10 would then verify and extract the encrypted device blob and send that to the device.
  • a counter mechanism is implemented to prevent replay attacks.
  • each successive communication from the device 101 to the hub 1 10 may be assigned a continually increasing counter value.
  • Both the hub 1 10 and device 101 will track this value and verify that the value is correct in each successive communication between the devices.
  • the same techniques may be implemented between the hub 1 10 and the service 120. Using a counter in this manner would make it more difficult to spoof the communication between each of the devices (because the counter value would be incorrect). However, even without this a shared installation key between the service and device would prevent network (hub) wide attacks to all devices.
  • the loT hub 1 10 when using public/private key encryption, uses its private key to decrypt the loT hub packet and generate the encrypted loT device packet, which it transmits to the associated loT device 101 .
  • the loT device 101 then uses its private key to decrypt the loT device packet to generate the
  • each device would encrypt and decrypt with the shared symmetric key. If either case, each transmitting device may also sign the message with it's private key so that the receiving device can verify it's authenticity.
  • a different set of keys may be used to encrypt communication from the loT device 101 to the loT hub 1 10 and to the loT service 120.
  • the security logic 1002 on the loT device 101 uses the public key of the loT hub 1 10 to encrypt data packets sent to the loT hub 1 10.
  • the security logic 1012 on the loT hub 1 10 may then decrypt the data packets using the loT hub's private key.
  • the security logic 1002 on the loT device 101 and/or the security logic 1012 on the loT hub 1 10 may encrypt data packets sent to the loT service 120 using the public key of the loT service 120 (which may then be decrypted by the security logic 1013 on the loT service 120 using the service's private key).
  • the device 101 and hub 1 10 may share a symmetric key while the hub and service 120 may share a different symmetric key.
  • the underlying principles of the invention may be implemented using various different encryption techniques. For example, while some embodiments discussed above use asymmetric public/private key pairs, an alternate embodiment may use symmetric keys securely exchanged between the various loT devices 101 -102, loT hubs 1 10, and the loT service 120.
  • the security logic 1002 on the loT device 101 and/or the security logic 1012 on the loT hub 1 10 may encrypt data packets sent to the loT service 120 using the public key of the loT service 120 (which may then be decrypted by the security logic 1013 on the loT service
  • data/command itself is not encrypted, but a key is used to generate a signature over the data/command (or other data structure). The recipient may then use its key to validate the signature.
  • the secure key storage on each loT device 101 is implemented using a programmable subscriber identity module (SIM) 1 101 .
  • SIM subscriber identity module
  • the loT device 101 may initially be provided to the end user with an un-programmed SIM card 1 101 seated within a SIM interface 1 100 on the loT device 101 .
  • the user takes the programmable SIM card 1 101 out of the SIM interface 500 and inserts it into a SIM programming interface 1 102 on the loT hub 1 10.
  • Programming logic 1 125 on the loT hub then securely programs the SIM card 1 101 to register/pair the loT device 101 with the loT hub 1 10 and loT service 120.
  • a public/private key pair may be randomly generated by the programming logic 1 125 and the public key of the pair may then be stored in the loT hub's secure storage device 41 1 while the private key may be stored within the programmable SIM 1 101 .
  • the programming logic 525 may store the public keys of the loT hub 1 10, the loT service 120, and/or any other loT devices 101 on the SIM card 1401 (to be used by the security logic 1302 on the loT device 101 to encrypt outgoing data).
  • the new loT device 101 may be provisioned with the loT Service 120 using the SIM as a secure identifier (e.g., using existing techniques for registering a device using a SIM). Following provisioning, both the loT hub 1 10 and the loT service 120 will securely store a copy of the loT device's public key to be used when encrypting communication with the loT device 101 .
  • the techniques described above with respect to Figure 11 provide enormous flexibility when providing new loT devices to end users. Rather than requiring a user to directly register each SIM with a particular service provider upon sale/purchase (as is currently done), the SIM may be programmed directly by the end user via the loT hub 1 10 and the results of the programming may be securely communicated to the loT service 120. Consequently, new loT devices 101 may be sold to end users from online or local retailers and later securely provisioned with the loT service 120.
  • SIM Subscriber Identity Module
  • the underlying principles of the invention are not limited to a "SIM" device. Rather, the underlying principles of the invention may be implemented using any type of device having secure storage for storing a set of encryption keys.
  • the embodiments above include a removable SIM device, in one embodiment, the SIM device is not removable but the loT device itself may be inserted within the programming interface 1 102 of the loT hub 1 10.
  • the SIM is pre-programmed into the loT device 101 , prior to distribution to the end user.
  • various techniques described herein may be used to securely exchange encryption keys between the loT hub 1 10/loT service 120 and the new loT device 101 .
  • each loT device 101 or SIM 401 may be packaged with a barcode or QR code 1501 uniquely identifying the loT device 101 and/or SIM 1001 .
  • the barcode or QR code 1201 comprises an encoded representation of the public key for the loT device 101 or SIM 1001 .
  • the barcode or QR code 1201 may be used by the loT hub 1 10 and/or loT service 120 to identify or generate the public key (e.g., used as a pointer to the public key which is already stored in secure storage).
  • the barcode or QR code 601 may be printed on a separate card (as shown in Figure 12A) or may be printed directly on the loT device itself.
  • the loT hub 1 10 is equipped with a barcode reader 206 for reading the barcode and providing the resulting data to the security logic 1012 on the loT hub 1 10 and/or the security logic 1013 on the loT service 120.
  • the security logic 1012 on the loT hub 1 10 may then store the public key for the loT device within its secure key storage 101 1 and the security logic 1013 on the loT service 120 may store the public key within its secure storage 1021 (to be used for subsequent encrypted communication).
  • the data contained in the barcode or QR code 1201 may also be captured via a user device 135 (e.g., such as an iPhone or Android device) with an installed loT app or browser-based applet designed by the loT service provider.
  • a user device 135 e.g., such as an iPhone or Android device
  • the barcode data may be securely communicated to the loT service 120 over a secure connection (e.g., such as a secure sockets layer (SSL) connection).
  • SSL secure sockets layer
  • the barcode data may also be provided from the client device 135 to the loT hub 1 10 over a secure local connection (e.g., over a local WiFi or Bluetooth LE connection).
  • the security logic 1002 on the loT device 101 and the security logic 1012 on the loT hub 1 10 may be implemented using hardware, software, firmware or any combination thereof.
  • the security logic 1002, 1012 is implemented within the chips used for establishing the local communication channel 130 between the loT device 101 and the loT hub 1 10 (e.g., the Bluetooth LE chip if the local channel 130 is Bluetooth LE).
  • the security logic 1002, 1012 is designed to establish a secure execution environment for executing certain types of program code. This may be implemented, for example, by using TrustZone technology (available on some ARM processors) and/or Trusted Execution Technology (designed by Intel).
  • TrustZone technology available on some ARM processors
  • Trusted Execution Technology designed by Intel.
  • the underlying principles of the invention are not limited to any particular type of secure execution technology.
  • the barcode or QR code 1501 may be used to pair each loT device 101 with the loT hub 1 10.
  • a pairing code embedded within the barcode or QR code 1501 may be provided to the loT hub 1 10 to pair the loT hub with the corresponding loT device.
  • Figure 12B illustrates one embodiment in which the barcode reader 206 on the loT hub 1 10 captures the barcode/QR code 1201 associated with the loT device 101 .
  • the barcode/QR code 1201 may be printed directly on the loT device 101 or may be printed on a separate card provided with the loT device 101 .
  • the barcode reader 206 reads the pairing code from the barcode/QR code 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 loT device 101 and loT hub 1 10 are automatically paired. Each time the loT hub is paired with a new loT device in this manner, the pairing data for that pairing is stored within the secure storage 685.
  • the local communication module 1280 of the loT hub 1 10 may use the code as a key to encrypt communications over the local wireless channel with the loT device 101 .
  • the local communication module 1590 stores pairing data within a local secure storage device 1595 indicating the pairing with the loT hub.
  • the pairing data 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 loT hub 1 10 required for establishing a secure local communication channel (e.g., an additional key to encrypt communication with the loT hub 1 10).
  • the barcode/QR code 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 loT device 101 to the loT hub 1 10 and from the loT hub 1 10 to the loT 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 loT device with a blank SIM card and, at 1602, the user inserts the blank SIM card into an loT hub.
  • the user programs the blank SIM card with a set of one or more encryption keys.
  • the loT hub may randomly generate a
  • a programmable device other than a "SIM" card may be used to perform the same functions as the SIM card in the method shown in Figure 13.
  • 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 loT device to which an encryption key has been pre-assigned.
  • the key is securely provided to the loT hub.
  • this involves reading a barcode associated with the loT device to identify the public key of a public/private key pair assigned to the device.
  • the barcode may be read directly by the loT hub or captured via a mobile device via an app or bowser.
  • a secure communication channel such as a Bluetooth LE channel, a near field communication (NFC) channel or a secure WiFi channel may be established between the loT device and the loT hub to exchange the key. Regardless of how the key is transmitted, once received, it is stored in the secure keystore of the loT hub device.
  • the loT hub may store and protect the key such as Secure Enclaves, Trusted Execution Technology (TXT), and/or Trustzone.
  • TXT Trusted Execution Technology
  • the key is securely transmitted to the loT service which stores the key in its own secure keystore. It may then use the key to encrypt communication with the loT device.
  • the exchange may be implemented using a certificate/signed key.
  • the hub 1 10 it is particularly important to prevent modification/addition/ removal of the stored keys.
  • FIG. 15 A method for securely communicating commands/data to an loT 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 loT service encrypts the data/commands using the loT device public key to create an loT device packet. It then encrypts the loT device packet using loT hub's public key to create the loT hub packet (e.g., creating an loT hub wrapper around the loT device packet).
  • the loT service transmits the loT hub packet to the loT hub.
  • the loT hub decrypts the loT hub packet using the loT hub's private key to generate the loT device packet.
  • it transmits the loT device packet to the loT device which, at 1505, decrypts the loT device packet using the loT device private key to generate the data/commands.
  • the loT device processes the data/commands.
  • a symmetric key exchange may be negotiated between each of the devices (e.g., each device and the hub and between the hub and the service). Once the key exchange is complete, each transmitting device encrypts and/or signs each transmission using the symmetric key before transmitting data to the receiving device.
  • encryption and decryption of data is performed between the loT service 120 and each loT device 101 , regardless of the intermediate devices used to support the communication channel (e.g., such as the user's mobile device 61 1 and/or the loT hub 1 10).
  • the intermediate devices used to support the communication channel e.g., such as the user's mobile device 61 1 and/or the loT hub 1 10.
  • the loT service 120 includes an encryption engine 1660 which manages a set of "service session keys" 1650 and each loT device 101 includes an encryption engine 1661 which manages a set of "device session keys” 1651 for encrypting/decrypting communication between the loT device 101 and loT 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 loT device 101 include a public key of the loT service 120 and a private key of the loT 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 loT service 120 and the loT device 101 . Additional details associated with generation and use of the secret in accordance with one embodiment of the invention are provided below.
  • 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. [00133] As illustrated, an SSL connection or other secure channel may be established between the loT service 120 and the loT hub 1 10.
  • the loT hub 1 10 (which does not have the ability to decrypt the message in one embodiment) transmits the encrypted message to the loT device at 1603 (e.g., over a Bluetooth Low Energy (BTLE) communication channel).
  • the encryption engine 1661 on the loT 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 loT service 120 and loT device 101 .
  • the message may comprise a command packet instructing the loT device 101 to perform a particular function such as taking a measurement and reporting the result back to the client device 61 1 or may include configuration data to configure the operation of the loT device 101 .
  • the encryption engine 1661 on the loT device 101 uses the secret or a derived key stream to encrypt the response and transmits the encrypted response to the loT hub 1 10 at 1604, which forwards the response to the loT service 120 at 1605.
  • the encryption engine 1660 on the loT service 120 then decrypts the response using the secret or a derived key stream and transmits the decrypted response to the client device 61 1 at 1606 (e.g., over the SSL or other secure communication channel).
  • Figure 16B illustrates an embodiment which does not require an loT hub. Rather, in this embodiment, communication between the loT device 101 and loT service 120 occurs through the client device 61 1 (e.g., as in the embodiments described above with respect to Figures 6-9B). In this embodiment, to transmit a message to the loT device 101 the client device 61 1 transmits an unencrypted version of the message to the loT service 120 at 161 1 .
  • 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 61 1 at 1612.
  • the client device 61 1 then forwards the encrypted message to the loT device 101 at 1613, and the encryption engine 1661 decrypts the message using the secret or the derived key stream.
  • the loT 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 61 1 at 1614, which forwards the encrypted response to the loT service 120 at 1615.
  • the encryption engine 1660 then decrypts the response and transmits the decrypted response to the client device 61 1 at 1616.
  • Figure 17 illustrates a key exchange and key stream generation which may initially be performed between the loT service 120 and the loT device 101 .
  • this key exchange may be performed each time the loT service 120 and loT 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 loT hub 1 10 and/or the client device 61 1 .
  • the encryption engine 1660 of the loT 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 loT 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 loT service 120 transmits its session public key generated using the HSM 1630 to the loT device 101 at 1701 .
  • the loT 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 loT 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 loT service 120 uses these techniques, at 1703, the encryption engine 1660 of the loT service 120 generates the secret using the loT device session public key and its own session private key.
  • the loT service 120 and loT 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 one embodiment of the key stream generation module 1640-1641
  • GCM Galois/Counter Mode
  • the key stream is XORed with the data to generate the encrypted data packet.
  • the loT device 101 transmits the counter value with the encrypted data packet to the loT service 120.
  • the encryption engine 1660 on the loT 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 loT service 120 to the loT device 101 are encrypted in the same manner. Specifically, a counter is
  • 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 loT device 101 .
  • the encryption engine 1661 on the loT 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 loT service 120 and loT 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 loT service 120 and loT 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 loT service key pairs, and a set of loT 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 loT 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 loT devices is assigned its own factory key pair which may then be used to authenticate loT service keys and loT device keys.
  • a factory private key is used to generate a signature over loT service public keys and loT device public keys. These signature may then be verified using the corresponding factory public key.
  • these loT 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 loT 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 loT service 120 and loT device 101 :
  • the loT service 120 initially generates a message containing the following:
  • the Factory Certificate including:
  • loT service session public key signature (e.g., signed with the loT service's private key)
  • the message is sent to the loT device on the negotiation channel (described below).
  • the loT device parses the message and:
  • the loT device then generates a message containing the following:
  • Class of unique ID i.e., loT device
  • This message is sent back to the loT service.
  • the loT service parses the message and:
  • the loT service then generates a message containing a signature of (loT device session public key + loT service session public key) signed with the loT service's key.
  • the loT device parses the message and:
  • the loT device then sends a "messaging available" message.
  • the loT device receives the message and:
  • the loT service recognizes the message payload contains a boomerang attribute update and:
  • J. loT device receives the message and sets his paired state to true
  • 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
  • BTLE Bluetooth Low Energy
  • Characteristic IDs for each entry in the table. Note that while the “characteristics” are sometimes referred to as “attributes.”
  • 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"
  • 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 loT devices without formally pairing with these devices. Pairing with each individual loT 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 loT device 101 without formally establishing a paired BT connection.
  • the BT device 1910 may be included in an loT hub 1 10 and/or a client device 61 1 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 "loT 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 loT device 101 may receive the loT service session public key 1701 via the "negotiation read" characteristic ⁇ 65533>.
  • the key 1701 may be transmitted from the loT service 120 to a BTLE-enabled loT hub 1 10 or client device 61 1 which may then use GATT to write the key 1701 to the negotiation read value buffer identified by characteristic ID ⁇ 65533>.
  • loT 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 loT 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 loT device 101 ) and characteristic ID ⁇ 65533> (for receiving encrypted data packets by loT 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 loT 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 loT device 101
  • characteristic ID ⁇ 65533> for receiving encrypted data packets by loT 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 loT 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 loT device 101 . For example, if the loT 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 loT device 101 is a security apparatus associated with a door
  • 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 loT device and/or configuration data to configure the operation of the loT device in some manner (e.g., to set a desired parameter, to power down the loT device, etc). For example, if the loT device 101 controls the speed of a fan, the value field may reflect the current fan speed.
  • 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 loT device, the update state field may indicate whether the light was successfully turned off.
  • Figure 21 illustrates an exemplary sequence of transactions between the loT service 120 and an loT device 101 involving the SET and UPDATE commands.
  • the SET command 2101 is transmitted form the loT service to the loT 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 loT 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 loT 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 loT device to enter into an "on" or a low power state).
  • the new value is set in the loT 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 loT device 101 to update certain types of values).
  • the UPDATE command is transmitted back to the loT service 120 containing the actual value from the GATT value field.
  • Figure 22 illustrates a method for implementing a secure communication channel between an loT service and an loT 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 loT service creates an encrypted channel to communicate with the loT hub using elliptic curve digital signature algorithm (ECDSA) certificates.
  • the loT service encrypts data/commands in loT device packets using the a session secret to create an encrypted device packet.
  • the session secret may be independently generated by the loT device and the loT service.
  • the loT service transmits the encrypted device packet to the loT hub over the encrypted channel.
  • the loT hub passes the encrypted devic packet to the loT device.
  • the loT 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 loT 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 loT device 101 communicating with an loT 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 loT Service creates a packet containing serial number and public key of the loT Service.
  • the loT Service signs the packet using the factory private key.
  • the loT Service sends the packet over an encrypted channel to the loT hub and at 2304 the loT hub forwards the packet to loT device over an unencrypted channel.
  • the loT device verifies the signature of packet and, at 2306, the loT device generates a packet containing the serial number and public key of the loT Device.
  • the loT device signs the packet using the factory private key and at 2308, the loT device sends the packet over the unencrypted channel to the loT hub.
  • the loT hub forwards the packet to the loT service over an encrypted channel and at 2310, the loT Service verifies the signature of the packet.
  • the loT Service generates a session key pair, and at 2312 the loT Service generates a packet containing the session public key.
  • the loT Service then signs the packet with loT Service private key at 2313 and, at 2314, the loT Service sends the packet to the loT hub over the encrypted channel.
  • the loT hub forwards the packet to the loT device over the unencrypted channel at 2315 and, at 2316, the loT device verifies the signature of packet.
  • the loT device generates session key pair (e.g., using the
  • an loT device packet is generated containing the loT device session public key.
  • the loT device signs the loT device packet with loT device private key.
  • the loT device sends the packet to the loT hub over the unencrypted channel and, at 2321 , the loT hub forwards the packet to the loT service over an encrypted channel.
  • the loT service verifies the signature of the packet (e.g., using the loT device public key) and, at 2323, the loT service uses the loT service private key and the loT device public key to generate the session secret (as described in detail above).
  • the loT device uses the loT device private key and loT service public key to generate the session secret (again, as described above) and, at 2325, the loT device generates a random number and encrypts it using the session secret.
  • the loT service sends the encrypted packet to loT hub over the encrypted channel.
  • the loT hub forwards the encrypted packet to the loT device over the unencrypted channel.
  • the loT device decrypts the packet using the session secret.
  • the loT device re-encrypts the packet using the session secret at 2329 and, at 2330, the loT device sends the encrypted packet to the loT hub over the unencrypted channel.
  • the loT hub forwards the encrypted packet to the loT service over the encrypted channel.
  • the loT service decrypts the packet using the session secret at 2332.
  • the loT service verifies that the random number matches the random number it sent.
  • the loT service then sends a packet indicating that pairing is complete at 2334 and all subsequent messages are encrypted using the session secret at 2335.
  • a dedicated loT hub 1 10 is illustrated in many embodiments above, a dedicated loT hub hardware platform is not required for complying with the underlying principles of the invention.
  • the various loT hubs described above may be implemented as software executed within various other networking devices such as iPhones® and Android® devices (e.g., an loT device App).
  • the loT hubs described herein may be implemented on any device capable of communicating with loT devices (e.g., using BTLE or other local wireless protocol) and establishing a connection over the Internet (e.g., to an loT service using a WiFi or cellular data connection).
  • each loT device includes a secure communication module for establishing a secure communication channel with an loT service and a microcontroller unit (MCU) which executes program code to perform application-specific functions (e.g., in accordance with the specific functions to be performed by the loT device).
  • MCU microcontroller unit
  • a serial communication interface is communicatively coupled between the MCU and the secure communication module.
  • FIG 24 illustrates one particular embodiment in which a serial peripheral interface (SPI) 2410 is used to provide bi-directional communication between the MCU 2401 and secure communication module 2402.
  • SPI interface 2410 is a synchronous serial communication interface specification used for short distance communication, primarily in embedded systems.
  • the MCU 2401 operates as the Master and the secure communication module 2402 operates as a Slave in accordance with the SPI communication protocol. Accordingly, in some embodiments described below, the MCU will simply be referred to as the "Master" and the secure
  • the SPI interface 2410 refers to both the SPI bus lines connecting the Master 2401 with the Slave 2402 and the SPI interface circuitry on the Master and Slave (described in greater detail below).
  • the communication bus lines of the SPI interface 2410 include a system clock (SCK) generated by the Master 2401 , a chip select (CS) controlled by the Master 2401 , a Master-out-Slave-ln (MOSI) communication line for transmitting data from the Master 2401 to the Slave 2402 and a Master-in-Slave-out (MISO) communication line for transmitting data from the Slave 2402 to the Master 2041 .
  • SCK system clock
  • CS chip select
  • MISO Master-out-Slave-ln
  • the standard SPI protocol requires the Master to initiate all communication with the Slave.
  • the Master must control the chip select (CS) line and indicate to the slave that it needs data or needs to transmit data. After a period of time (which may be as much as 2ms), when the Slave is ready to respond, it will send the data. Because of the amount of handshaking and waiting time in order to coordinate the communication between the Master and Slave, the current SPI protocol is inefficient, particularly when large amounts of data need to be streamed between the Master and the Slave.
  • a control line 2410 is added to improve the speed at which the SPI interface can be run between the Master 2401 and the Slave 2402.
  • the Master 2401 or the Slave 2402 pulls the control line 2410 low, informing the other that it is ready to send data.
  • This coordinates all of the transactions on the SPI interface 2410 in a more efficient manner because if the Slave 2402 wants to send data, it pulls the control line 2401 low and, upon seeing that the line is low, the Master 2401 initiates the transaction using the SPI interface 2410. The Slave 2402 then transmits the data.
  • the transaction is bi-directional so data can be streamed concurrently in both directions.
  • bother the Master 2401 and the Slave 2402 release the control line 2410, which goes high again, indicating to both the Master and Slave that either party may initiate a new transaction.
  • Figure 25 illustrates additional details of one embodiment of the invention including interface circuitry 2550 on the Master 2401 and interface circuitry 2560 on the Slave 2402 which include components such as bus drivers to transmit and receive digital data over the MOSI and MISO bus lines.
  • Control logic 2552, 2562 controls the communication as described above by pulling the control line 2410 low when either the Master 2401 or the Slave 2402 needs to initiate a new transaction.
  • the control logic 2562 of the Slave is electrically coupled to the base of a first transistor 2402 and the control logic 2552 of the Master 2401 is electrically coupled to the base of a second transistor 2503.
  • each transistor is connected to ground (GND) and the source of each transistor is coupled to a pull up resistor 2501 on a line to which a voltage is supplied (V).
  • the transistors 2502-2503 may be any type of transistors including bipolar junction transistors (BJTs) or field-effect transistors (FETs).
  • BJTs bipolar junction transistors
  • FETs field-effect transistors
  • either the Master 2401 or the Slave 2402 may pull the control line low, indicating that a transaction is in progress.
  • neither the Master nor the slave will attempt to initiate a transaction when the control line is pulled low, thereby ensuring coordination between the Master 2401 and Slave 2402.
  • this coordination is used to establish a bi-directional streaming interface between the Master 2401 and the Slave 2402 operating at a significantly greater speed than current SPI interfaces.
  • the Master 2401 and Slave 2402 include small (e.g., 10Byte) data buffers, 2551 and 2561 , respectively, to buffer data streamed between the Master 2401 and the Slave 2402. Consequently, when an amount of data greater than the size of the data buffers 2551 , 2561 needs to be transmitted between the Master and the Slave, the control line 2410 may be pulled and maintained low by the party initiating the transaction to ensure that the other party does not attempt to take control of the interface before the transaction is complete.
  • the Slave 2402 may take control by pulling the control line 2410 low, transmit the first 10 Bytes, and keep the control line low 2410 while the Master receives the first 10 Bytes.
  • the Slave 2402 transmits the next 10 Bytes.
  • the Slave 2402 releases the control line 2410 (allowing it to be pulled high) to indicate that the Master may take control.
  • the Master may also keep the control line 2410 low while it is receiving and processing each 10Byte buffer of data. Once it has completed receiving and processing the data, it will release the control line 2410.
  • a general purpose input/output (GPIO) line may be shared between the Master 2401 and Slave 2402 to enable this communication.
  • the GPIO line may operate in substantially the same manner as described above - i.e., when one party wants to enter into a transaction, it pulls the GPIO line low informing the other party that a transaction is in process.
  • One embodiment of the invention utilizes a special arrangement of bytes to enable bi-direction communication and signaling between the Master 2401 and the Slave 2402.
  • Figure 26 illustrates an exemplary 10 Byte segment, identified as Bytes 0- 9, in which Bytes 0 and 1 are used for error correction and control and Bytes 2-9 are used for data.
  • Byte 0 comprises a checksum over the Bytes 1 -9, which may be used by the receiving party to detect transmission errors. For example, the receiving party may calculate its own checksum over Bytes 1 -9 and compare the result with the checksum in Byte 0. If the result is the same, then it may be assumed that no errors were introduced. If the checksum is not the same, then the receiving party may request retransmission of the 10 Byte segment.
  • Byte 1 is arranged into a predetermined sequence of bits 2601 (e.g., 001 in the example) used by the receiving party to identify the beginning of the data sequence.
  • the fourth bit 2602 is used to indicate whether the transmission is the end of a data packet. For example, in as discussed above for a data packet of 100 Bytes, the value 2602 may be set to 1 when the last 10 Bytes is transmitted. The receiving party will then know when the packet transmission is complete. In one embodiment, the next four bytes 2603 (identified as nnnn) are set to indicate the number of Bytes of valid data stored in Bytes 2-9.
  • the value of 2603 may be 0001 ; if both Bytes 2 and 3 include valid data, then the value of 2603 may be 0010, and so on.
  • the receiving side will then process only the valid data and ignore the rest.
  • the 10 Byte segment is transmitted in both directions (i.e., one from the Master to the Slave and one from the Slave to the Master).
  • a party has no data to send, it will simply set the nnnn value 2603 equal to 0000. If both parties have data to send then they will each send the data concurrently, and indicate the number of valid Bytes by adjusting the nnnn value 2603.
  • the above techniques significantly increase the speed at which current SPI interfaces are capable of running, establishing a bi-directional streaming protocol over standard SPI bus lines.
  • an application 2503 running on the MCU 2401 can efficiently stream data to the loT service 120 and, at the same time, the loT service can efficiently stream data to the application 2403.
  • the secure communication module 2402 establishes a secure
  • One embodiment of the invention includes an integrated development tool to allow loT developers to readily design new loT devices, services, and client apps for end users.
  • the integrated development tool allows the developer to indicate the input/output functions to be performed by each loT device, the GUI features to be available to end users, and the back-end functions to be performed by the loT service.
  • the integrated development tool generates a first profile for the loT device, a second profile for a client device app, and a third profile for the loT service to realize an end-to-end, fully-functional loT implementation with limited effort.
  • Figure 27 illustrates one embodiment of an integrated development tool platform 2701 which includes a development application 2720 with a graphical user interface 2721 usable by a developer to design new loT implementations.
  • the integrated development tool (IDT) platform 2701 comprises a computer system with a storage device and memory for storing program code of the development application 2720 and a processor for processing the program code during runtime.
  • the various other modules illustrated in Figure 27 e.g., 2730- 2732
  • a development database 2710 is loaded and continually updated with data related to different loT device configurations, user interface features for client-side apps, and loT service configurations.
  • the development database 2710 may include data related to different types of input/output (I/O) functions to be performed by each of the loT devices 101 -102 including, but not limited to analog-to-digital (A/D) functions (e.g., capturing an analog voltage level), digital-to-analog (D/A) functions (e.g., providing an analog voltage output)., binary on/off functions (e.g., unlocking a door, triggering an alarm, turning on a light, etc), and various General Purpose I/O (GPIO) functions.
  • A/D analog-to-digital
  • D/A digital-to-analog
  • GPIO General Purpose I/O
  • the developer may specify whether the loT device 102 is to be designed with a stand-alone secure communication module 2402 or whether the loT device 101 is to be designed with both a secure communication nodule 2402 and MCU 2401 (e.g., interconnected via an SPI interface as discussed above).
  • a stand-alone implementation may be used for relatively simpler loT implementations such as those which perform simple on/off functions (e.g., a switch integrated on a lightbulb) whereas the MCU implementation may be used for more complex data collection and monitoring (e.g., a remotely-controllable video camera triggered by a motion sensor).
  • an loT device engine 2730 uses the configuration data provided from the development application to generate an loT device profile 2740, specifying the configuration parameters for the secure communication module 2402. This may include, for example, the mode that the secure communication module is in, including whether the secure communication module 2402 is in a stand-alone mode or coupled to an MCU 2401 . If in stand-alone mode, the loT device profile 2740 configures the various I/O lines 2407 of the secure communication module 2402 to perform the functions required by the loT device 102.
  • the loT device profile 2740 may configure the I/O lines 2407 of the secure communication module 2402 and the I/O lines 2408 of the MCU and may also specify how the secure communication module 2402 is to interact with the MCU 2401 (e.g., communicating over an SPI bus to exchange data and commands with the application executed on the MCU as described above).
  • the loT device profile 2740 may be loaded into a nonvolatile memory on the secure communication module 2402 (e.g., Flash memory) to implement the loT functions (see, e.g., Figure 2 showing app code 203, library code 202, and communication stack code 201 executed by the low power uC 200).
  • the loT device profile 2740 may be used to configure an application-specific integrated circuit or field-programmable gate array (FPGA).
  • FPGA field-programmable gate array
  • an loT device engine 2730 uses the configuration data from the development application to generate a user experience (UX) profile 2741 to be used to implement the loT app or application on the client device 61 1 .
  • the UX profile may specify various graphical I/O elements to be displayed within the GUI of the loT app or application and the configurations to be used for those graphical I/O elements.
  • the UX profile may include a simple on/off switch to control the loT device 102.
  • the loT device 101 is a video capture device then the UX profile may specify a graphical element to cause video to be displayed on the client 61 1 and the specific parameters for displaying the video (e.g., scaling to be used, location on the client display, etc).
  • the UX profile may specify a graphical element to cause video to be displayed on the client 61 1 and the specific parameters for displaying the video (e.g., scaling to be used, location on the client display, etc).
  • an loT service engine 2732 generates a cloud API profile 2742 to accommodate the service-side requirements of the new loT devices 101 -102.
  • This may include, for example, the manner in which the loT service 120 is to exchange commands and data with the new loT devices and/or notifications to be sent to the user's client device 61 1 in response to data received from the loT devices.
  • the cloud API profile may specify that a notification is to be sent to the client device 61 1 whenever the door is opened and the user is not home.
  • the cloud API profile 2742 may specify the commands to be used to control the new loT devices.
  • the cloud API profile 2742 specifies the manner in which the loT service 120 is to communicate with external loT services such as the loT services run by the designer of the new loT devices 101 -102 (e.g., exposing an API to the external loT services).
  • FIG. 28 A method implemented by an integrated development tool for an loT system is illustrated in Figure 28. The method may be implemented within the context of the system architectures described above, but is not limited to any particular system architecture.
  • the designer enters parameters for the new loT device via the GUI of the development application. This may include, for example, the I/O functions to be performed by the loT device and the manner in which the loT device is to interact with the loT service.
  • the loT device engine uses data from the development application, the loT device engine generates an loT device profile. In addition to the I/O function specification, this may include an indication as to whether the secure communication module is in standalone mode or used with an MCU.
  • the loT device profile is applied to the loT device. In one embodiment, this involves copying the program code to a non-volatile storage on the loT device.
  • the client app engine uses data from the development application, the client app engine generates a UX profile specifying (among other things) the user interface to be displayed on the client when interacting with the new loT devices.
  • the UX profile is applied to the client.
  • the loT service engine uses data from the development application, the loT service engine generates a cloud API profile specifying the manner in which the loT service is to interoperate with the new loT devices, the client device and/or any external loT services.
  • the loT service may expose an API to enable communication with one or more external loT services.
  • the cloud API profile is applied to the loT cloud service.
  • a developer can concurrently program a new loT device, an loT service, and a user app, thereby saving a significant amount of time and effort compared with current
  • loT devices may be used to perform different functions in a given location.
  • certain loT devices may be used to collect data such as temperature and status (e.g., on/off status) and report this data back to the loT service, where it may be accessed by an end user and/or used to generate various types of alert conditions.
  • one embodiment of the invention manages collected data, system data, and other forms of data using different types of attribute classes.
  • Figure 29 illustrates one embodiment of an loT device which includes a secure wireless communication module 2918 which communicates with a
  • microcontroller unit (MCU) 2915 over a serial interface 2916 such as an Serial
  • the secure wireless communication module 2918 manages the secure communication with the loT service 120 using the techniques described above and the MCU 2915 executes program code to perform an application- specific function of the loT device 101 .
  • the attributes include application attributes 2910, system attributes 291 1 , and priority notification attributes 2912.
  • the application attributes 2910 comprise attributes related to the application-specific function performed by the loT device 101 .
  • the loT device comprises a security sensor
  • the application attributes 2910 may include a binary value indicating whether a door or window has been opened.
  • the loT device comprises a temperature sensor
  • the application attributes 2910 may include a value indicating a current temperature.
  • a virtually unlimited number of other application-specific attributes may be defined.
  • the MCU 2915 executes application-specific program code and is only provided with access to the application-specific attributes 2910.
  • an application developer may purchase the loT device 101 with the secure wireless communication module 2918 and design application program code to be executed by the MCU 2915. Consequently, the application developer will need to have access to application attributes but will not need to have access to the other types of attributes described below.
  • the system attributes 291 1 are used for defining operational and configuration attributes for the loT device 101 and the loT system.
  • the system attributes may include network configuration settings (e.g., such as the flow control parameters discussed above), the device ID, software versions, advertising interval selection, security implementation features (as described above) and various other low level variables required to allow the loT device 101 to securely communicate with the loT service.
  • a set of priority notification attributes 2912 are defined based on a level of importance or severity associated with those attributes. For example, if a particular attribute is associated with a hazardous condition such as a temperature value reaching a threshold (e.g., when the user accidentally leaves the stove on or when a heat sensor in the user's home triggers) then this attribute may be assigned to a priority notification attribute class. As mentioned above, priority notification attributes may be treated differently than other attributes. For example, when a particular priority notification attribute reaches a threshold, the loT hub may pass the value of the attribute to the loT service, regardless of the current flow control mechanisms being implemented by the loT hub. In one embodiment, the priority notification attributes may also trigger the loT service to generate notifications to the user and/or alarm conditions within the user's home or business (e.g., to alert the user of a potentially hazardous condition).
  • the current state of the application attributes 2910, system attributes 291 1 and priority notification attributes 2912 are duplicated/mirrored within the device database 2851 on the loT service 120.
  • the secure wireless communication module 2918 communicates the change to the device management logic 2921 on the loT service 120, which responsively updates the value of the attribute within the device database 2851 .
  • the attribute change will be transmitted from the device management logic 2921 to the secure wireless communication module 2918 which will then update its local copy of the attribute.
  • the attributes are maintained in a consistent manner between the loT device 101 and the loT service 120.
  • the attributes may also be accessed from the loT service 120 via a user device with an loT app or application installed and/or by one or more external services 2970.
  • the loT service 120 may expose an application programming interface (API) to provide access to the various different classes of attributes.
  • API application programming interface
  • priority notification processing logic 2922 may perform rule-based operations in response to receipt of a notification related to a priority notification attribute 2912. For example, if a priority notification attribute indicates a hazardous condition (e.g., such as an iron or stove being left on by the user), then the priority notification processing logic 2922 may implement a set of rules to attempt to turn off the hazardous device (e.g., sending an "off" command to the device if possible). In one embodiment, the priority notification processing logic 2922 may utilize other related data such as the current location of the user to determine whether to turn off the hazardous device (e.g., if the user is detected leaving the home when the hazardous device in an "on" state). In addition, the priority notification processing logic 2922 may transmit an alert condition to the user's client device to notify the user of the condition. Various other types of rule sets may be implemented by the priority notification processing logic 2922 to attempt to address a potentially hazardous or otherwise undesirable condition.
  • a hazardous condition e.g., such as an iron or stove being left on by the user
  • BTLE attributes 2905 may be used to establish the read and write ports as described above with respect to Figures 19-20.
  • the attribute address decoder 2907 reads a unique ID code associated with each attribute to determine which attribute is being received/transmitted and process the attribute accordingly (e.g., identify where the attribute is stored within the secure wireless communication module 2918).
  • One embodiment of the invention generates a preview of client device and loT device functionality from within the integrated development application.
  • one embodiment allows developers to preview a user interface defined within the development application (e.g., the UX profile 2741 discussed above) including different attribute definitions on all mobile apps where they are logged in with the same user account.
  • Figure 30 illustrates one embodiment in which virtual device generation logic 3005 on the loT service 120 generates a virtual device 3010 using the loT device profile 2740 and the user experience profile 2741 specified by the user within the development application 2720. The user may then interact with and test the virtual device 3010 via the development application 2720 and/or a mobile app 3022 executed on a mobile client device 3020.
  • the virtual device 3010 includes virtualization program code which interprets the device attributes 301 1 of the loT device profile 2740 and the presentation definitions 3012 from the UX profile 2741 to render a virtual representation of the loT device 3010. The resulting virtual representation may then be rendered within the client mobile app 3022.
  • the user may modify the device attributes 301 1 and/or presentation definitions 3012 via a preview graphical user interface (GUI) 3021 of the development application 2720 (some examples of which are provided below).
  • GUI graphical user interface
  • the user after making modifications to the device attributes 301 1 and/or presentation definitions 3012, the user manually transfers those changes to the service 120, either by initiating a preview via a preview button 3150 or by publishing them via a publish option 3151 (shown, for example, in Figure 31 G).
  • any changes made by the user may be automatically transferred to the service in real time or periodically.
  • the virtual device 3010 will apply the changes made by the user via the preview GUI 3021 and the attributes and presentation features will be updated within the mobile app 3022.
  • the preview Ul button 3150 may be used to update attributes on an loT device which will then be dynamically reflected in the mobile app 3022.
  • the user may modify attributes from the mobile app 3022 (e.g., by selecting graphical elements) and view the modifications within the preview GUI 3021 .
  • Figure 31 A illustrates one embodiment of the preview GUI 3021 of the development application 2720 comprising a plurality of graphical elements 3015 which may be selected and updated by the user, and a preview Ul button 3150 for generating a preview of the updates on the mobile client 3020.
  • the graphical elements 3015 comprise a group of controls or widgets representing one or more attributes to be managed by the loT device and synchronized with the loT service as described above.
  • a user makes changes to the attributes and/or graphical features associated with the graphical elements 3015, and then selects the preview Ul button 3150, those changes are updated within the virtual device 3010 on the loT service and transmitted to the mobile client 3020 over the account channel (where they are reflected in the Ul of the mobile app 3022).
  • FIG. 31 B the user has selected a particular graphical element (an "LED” element to turn an LED ON/OFF ) revealing an "attribute tester" window which includes a plurality of fields 3101 -3104 through which the user can make changes to the attribute.
  • the user may change the attribute name 3101 , the data type 3102 used to store data associated with the attribute, and the current attribute value 3103.
  • the user can only change the value of writable attributes on this screen.
  • Read-only attributes are displayed only to show the user value changes on the device side. Read-only attributes and fields may be grayed out.
  • An update button 3104 is provided to implement the changes.
  • the preview user interface generated on the client 3020 shows graphical elements 31 10-31 1 1 associated with this particular attribute - i.e., an ON element 31 10 to indicate when the LED is on and an OFF element 31 1 1 to indicate when the LED is off.
  • the attribute value is initially set to 0, resulting in an ON state displayed within the preview GUI (i.e., element 31 10 is highlighted).
  • the user has modified the attribute value to a 1 and, after selecting the update button 3104, the OFF graphical element 31 1 1 becomes highlighted within the preview GUI on the client 3020 (and the highlight is removed from the ON graphical element 31 10), thereby dynamically reflecting the changes entered by the user.
  • the attribute value change is first reflected within the device attributes 301 1 of the virtual device 3010 and is then propagated out to the client 3020 via the account channel.
  • FIG 31 D the user may select a particular graphic, causing the preview GUI 3021 to open a field 3120 for modifying the name of the graphical element (in this case the LED element).
  • an icon button 3121 is provided which generates a window containing a plurality of selectable icons 3130 as shown in Figure 31 E. Selecting a particular icon 3130 causes the icon to be displayed within the graphical element, as shown at 3140 of Figure 31 F. In one embodiment, the new icon is updated within the presentation definitions 3012 of the virtual device 3010.
  • this change may or may not be dynamically propagated over the account channel to the client 3020, resulting in the new icon 3141 being rendered in Figure 31 F.
  • the updates transmitted over the account channel connecting the client 3020 to the loT service 120 are bi-directional.
  • user input provided by the user via the mobile app 3022 may be updated within the virtual device 3010 or real loT device and reflected within the Attribute Tester dialog shown in Figures 31 B-C.
  • the attribute change will be updated within the device attributes 301 1 of the virtual device 3010 or real loT device and displayed within the Attribute Tester dialog. In this manner, the user can test the operation of the mobile app 3022 and review the results within the Attribute Tester dialog .
  • Figure 31 G when the user initially selects button 3051 , the corresponding OFF button 3153 is highlighted and the corresponding attribute value 3160 is displayed within the preview GUI (a value of 1 in the example).
  • the user has selected an ON button 3152 from within the mobile app 3022, thereby changing the attribute value. The change is propagated through the device attributes 301 1 of the virtual device 3010 and displayed within the attribute value field 3160 of the preview GUI 3021 (a value of 0 in the example).
  • the loT service searches for a corresponding virtual loT device and, if none is found, configures a virtual loT device with the given device attributes and presentation and associates it to the user's account.
  • the loT service then sends a notification on the account channel about this new device. Any listener on the account channel may act on this message, including the mobile app 3022 which will refresh its Ul and display a new device on the user's account with the new Ul.
  • the user can interact with the preview device, but no real action will be taken. In one embodiment, if the user closes the mobile app and opens it again, the preview device will be reset to its default state.
  • FIG. 32A A method in accordance with one embodiment of the invention is illustrated in Figure 32A. The method may be implemented within the context of the architectures described above but is not limited to any particular architecture.
  • a search is performed for a device type definition that has a specific virtual device class set (i.e., "PreviewVirtualClass").
  • a specific virtual device class set i.e., "PreviewVirtualClass”
  • an internet-accessible database of loT devices may be provided by the user's partner (i.e., the business entity or individual who designed, manufactured or sold the loT device).
  • the underlying principles of the invention are not limited to any particular business arrangement between a user and a partner (and, in fact, the user and partner may be the same entity or individual).
  • the user's account is then searched first for an existing device of the aforementioned type.
  • the preview device type of the user's partner may also be searched for a device that is not associated with an account. If found, then at 2207, the existing device is used. If not, then at 2208, a virtual device of the preview device type is created and associated with the user's account.
  • the uploaded device description e.g., device attributes
  • presentation are then associated with the preview device.
  • the account channel is then notified of the new or updated device at 2210. Any listener on the account channel such as the mobile app 3022 will receive and process the notification.
  • bi-directional interaction between the preview GUI 3021 and the mobile app 3022 may be performed using raw attribute values as discussed above. For example, if an update to an attribute is provided from the preview GUI at 221 1 , then the mobile app is updated over the account channel at 2212. For example, if the user modifies the device attribute, the effect of that modification will be presented to the user within the mobile app (e.g., highlighting a different button within the GUI).
  • the embodiments of the invention described herein allow users such as developers to interact with any device on their account using the development application 2720.
  • the development application 2720 does not communicate through the account channel as other apps do.
  • the development application 2720 may render a hierarchical Ul of all control groups, their controls and the attributes which allows users to then enter the raw attribute value for a particular attribute and send it to the device. As this value is propagating through the platform all mobile apps will display the changes and the device will act on the value sent.
  • the development application 2720 monitors the attribute history and updates the attribute values on the preview GUI 3021 to changes initiated, for example, by a mobile app or on the device itself.
  • Embodiments of the invention may include various steps, which have been described above.
  • the steps may be embodied in machine-executable instructions which may be used to cause a general-purpose or special-purpose processor to perform the steps.
  • these steps may be performed by specific hardware components that contain hardwired logic for performing the steps, or by any combination thereof
  • instructions may refer to specific configurations of hardware such as application specific integrated circuits (ASICs) configured to perform certain operations or having a predetermined functionality or software instructions stored in memory embodied in a non-transitory computer readable medium.
  • ASICs application specific integrated circuits
  • the techniques shown in the figures can be implemented using code and data stored and executed on one or more electronic devices (e.g., an end station, a network element, etc.).
  • Such electronic devices store and communicate (internally and/or with other electronic devices over a network) code and data using computer machine-readable media, such as non-transitory computer machine-readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and transitory computer machine-readable
  • non-transitory computer machine-readable storage media e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory
  • Such electronic devices typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (non-transitory machine- readable storage media), user input/output devices (e.g., a keyboard, a touchscreen, and/or a display), and network connections.
  • the coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers).
  • the storage device of a given electronic device typically stores code and/or data for execution on the set of one or more processors of that electronic device.
  • code and/or data for execution on the set of one or more processors of that electronic device.
  • one or more parts of an embodiment of the invention may be implemented using different combinations of software, firmware, and/or hardware.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Telephone Function (AREA)

Abstract

L'invention concerne un système et un procédé de génération d'une prévisualisation interactive pour un dispositif de l'IdO. Par exemple, selon un mode de réalisation, l'invention concerne un système qui comprend : une application de développement de l'internet des objets (IdO) comprenant une interface d'utilisateur graphique (IUG) grâce à laquelle un utilisateur doit spécifier une configuration pour un nouveau dispositif de l'IdO, l'application de développement incluant un composant d'IUG de prévisualisation pour permettre à l'utilisateur de représenter une prévisualisation d'IU mobile sur un client mobile ; un service de l'IdO incluant une logique de génération de dispositif virtuel pour générer un dispositif virtuel répondant à la configuration spécifiée pour le nouveau dispositif de l'IdO, le dispositif virtuel comprenant une représentation virtualisée du nouveau dispositif de l'IdO ; et le dispositif virtuel servant à établir un canal de communication avec une application mobile exécutée sur un client, le dispositif virtuel servant à communiquer dynamiquement des actualisations à l'application mobile à mesure que l'utilisateur procède à des changements d'attributs de dispositif de l'IdO et/ou de définitions de présentation depuis l'IUG de prévisualisation.
PCT/US2017/034734 2016-06-03 2017-05-26 Outil de développement intégré à fonctionnalité de prévisualisation pour un système de l'internet des objets (ido) WO2017210120A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US15/172,520 2016-06-03
US15/172,459 US9841968B1 (en) 2016-06-03 2016-06-03 Integrated development tool with preview functionality for an internet of things (IoT) system
US15/172,520 US9846577B1 (en) 2016-06-03 2016-06-03 Integrated development tool with preview functionality for an internet of things (IoT) system
US15/172,459 2016-06-03

Publications (1)

Publication Number Publication Date
WO2017210120A1 true WO2017210120A1 (fr) 2017-12-07

Family

ID=60477850

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/034734 WO2017210120A1 (fr) 2016-06-03 2017-05-26 Outil de développement intégré à fonctionnalité de prévisualisation pour un système de l'internet des objets (ido)

Country Status (1)

Country Link
WO (1) WO2017210120A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019143842A1 (fr) 2018-01-17 2019-07-25 Kymeta Corporation Procédé et appareil de mise à jour à distance de dispositifs satellites
EP3696673A1 (fr) * 2019-02-12 2020-08-19 Citrix Systems, Inc. Système informatique permettant l'intégration des applications saas avec des capteurs d'internet des objets (ido) grâce à la génération automatique d'une interface de programme d'application (api) et procédés associés

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110161478A1 (en) * 2009-12-28 2011-06-30 Telefonaktiebolaget Lm Ericsson (Publ) Social web of objects
US8380359B2 (en) * 2008-12-10 2013-02-19 Somfy Sas Method of operating a home automation system
US20140108943A1 (en) * 2012-10-16 2014-04-17 Korea Electronics Technology Institute Method for browsing internet of things and apparatus using the same
US20150019553A1 (en) * 2013-07-11 2015-01-15 Neura, Inc. Data consolidation mechanisms for internet of things integration platform
US20150019342A1 (en) * 2013-07-09 2015-01-15 Qualcomm Incorporated Real-time context aware recommendation engine based on a user internet of things environment
US20150195365A1 (en) * 2014-01-07 2015-07-09 Korea Advanced Institute Of Science And Technology Smart Access Point and Method for Controlling Internet of Things Apparatus Using the Smart Access Point Apparatus
US20150295897A1 (en) * 2014-04-11 2015-10-15 Samsung Electronics Co., Ltd. Method and device for controlling security screen in electronic device
US20150370615A1 (en) * 2014-06-23 2015-12-24 Google Inc. Methods and apparatus for using smart environment devices via application program interfaces
US20160147402A1 (en) * 2014-11-24 2016-05-26 C-Labs Corporation Method for dynamic and automatic creation of user interfaces
US20160149767A1 (en) * 2014-11-21 2016-05-26 Kiban Labs, Inc. Internet of things device for registering user selections
US20170005820A1 (en) * 2015-07-03 2017-01-05 Kiban Labs, Inc. System and method for virtual internet of things (iot) devices and hubs

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8380359B2 (en) * 2008-12-10 2013-02-19 Somfy Sas Method of operating a home automation system
US20110161478A1 (en) * 2009-12-28 2011-06-30 Telefonaktiebolaget Lm Ericsson (Publ) Social web of objects
US20140108943A1 (en) * 2012-10-16 2014-04-17 Korea Electronics Technology Institute Method for browsing internet of things and apparatus using the same
US20150019342A1 (en) * 2013-07-09 2015-01-15 Qualcomm Incorporated Real-time context aware recommendation engine based on a user internet of things environment
US20150019553A1 (en) * 2013-07-11 2015-01-15 Neura, Inc. Data consolidation mechanisms for internet of things integration platform
US20150195365A1 (en) * 2014-01-07 2015-07-09 Korea Advanced Institute Of Science And Technology Smart Access Point and Method for Controlling Internet of Things Apparatus Using the Smart Access Point Apparatus
US20150295897A1 (en) * 2014-04-11 2015-10-15 Samsung Electronics Co., Ltd. Method and device for controlling security screen in electronic device
US20150370615A1 (en) * 2014-06-23 2015-12-24 Google Inc. Methods and apparatus for using smart environment devices via application program interfaces
US20160149767A1 (en) * 2014-11-21 2016-05-26 Kiban Labs, Inc. Internet of things device for registering user selections
US20160147402A1 (en) * 2014-11-24 2016-05-26 C-Labs Corporation Method for dynamic and automatic creation of user interfaces
US20170005820A1 (en) * 2015-07-03 2017-01-05 Kiban Labs, Inc. System and method for virtual internet of things (iot) devices and hubs

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019143842A1 (fr) 2018-01-17 2019-07-25 Kymeta Corporation Procédé et appareil de mise à jour à distance de dispositifs satellites
EP3741097A4 (fr) * 2018-01-17 2021-10-13 Kymeta Corporation Procédé et appareil de mise à jour à distance de dispositifs satellites
US11397571B2 (en) 2018-01-17 2022-07-26 Kymeta Corporation Method and apparatus for remotely updating satellite devices
EP3696673A1 (fr) * 2019-02-12 2020-08-19 Citrix Systems, Inc. Système informatique permettant l'intégration des applications saas avec des capteurs d'internet des objets (ido) grâce à la génération automatique d'une interface de programme d'application (api) et procédés associés
US10819797B2 (en) 2019-02-12 2020-10-27 Citrix Systems, Inc. Computing system providing SaaS application integration with internet of things (IoT) sensors through automated application program interface (API) generation and related methods

Similar Documents

Publication Publication Date Title
US10248407B2 (en) Integrated development tool with preview functionality for an internet of things (IoT) system
US10223101B2 (en) Integrated development tool with preview functionality for an internet of things (IoT) system
US11153750B2 (en) Apparatus and method for sharing credentials in an internet of things (IoT) system
US10659961B2 (en) Apparatus and method for sharing WiFi security data in an internet of things (IoT) system
US10613499B2 (en) System and method for virtual internet of things (IoT) devices and hubs
US10776080B2 (en) Integrated development tool for an internet of things (IOT) system
US10375044B2 (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
KR102723973B1 (ko) 사물 인터넷(IoT) 시스템에서 보안 통신 채널을 설정하기 위한 장치 및 방법
US9699814B2 (en) Apparatus and method for establishing secure communication channels in an internet of things (IoT) system
US10447784B2 (en) Apparatus and method for modifying packet interval timing to identify a data transfer condition
US9858213B2 (en) Interface and method for efficient communication between a microcontroller and a communication module
US20180316658A1 (en) Securely providing a password using an using an internet of things (iot) system
US11469957B2 (en) System and method for managing and configuring attributes of internet of things (IoT) devices
WO2017210120A1 (fr) Outil de développement intégré à fonctionnalité de prévisualisation pour un système de l'internet des objets (ido)

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17807291

Country of ref document: EP

Kind code of ref document: A1