Efficient Communication for Devices of a Home Network

• US 20140376405A1
• Filed: 06/25/2013
• Published: 12/25/2014
• Est. Priority Date: 06/25/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Nest Labs Incorporated (Alphabet Inc.)
• Inventors: Erickson, Grant M., Logue, Jay D., Hardison, Osborne B., Schultz, Richard J., Boross, Christopher A., Smith, Zachary B., Gujjaru, Sunny P., Neeley, Matthew G.
• Granted Patent: US 9,191,209 B2
• Time in Patent Office: Days
• US Class Current: 370/254
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G08B 21/0415 detecting absence of activity per se
• CPC Class Codes: H04L 12/28 characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks] wireless communication networks H04W ; arrangements for dividing the transmission path H04W40/00
• CPC Class Codes: H04L 12/2803 Home automation networks
• CPC Class Codes: H04L 12/2814 Exchanging control software or macros for controlling appliance services in a home automation network arrangements for maintenance or administration involving configuration of the network and network elements H04L41/08
• CPC Class Codes: H04L 12/2823 Reporting information sensed by appliance or service execution status of appliance services in a home automation network device-related reporting H04L43/065; arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom H04Q9/00
• CPC Class Codes: H04L 12/56 Packet switching systems
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 2101/659 Internet protocol version 6 [IPv6] addresses
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 49/254 Centralised controller, i.e. arbitration or scheduling
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/5038 for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/52 : specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/535 : Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 69/165 : Combined use of TCP and UDP protocols; selection criteria therefor
• CPC Class Codes: H04L 69/22 : Parsing or analysis of headers
• CPC Class Codes: H04L 9/0861 : Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/14 : using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/30 : Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
• CPC Class Codes: H04L 9/32 : including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• CPC Class Codes: H04L 9/3247 : involving digital signatures
• CPC Class Codes: H04L 9/3263 : involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823
• CPC Class Codes: H04L 9/3265 : using certificate chains, trees or paths; Hierarchical trust model
• CPC Class Codes: H04W 12/0471 : Key exchange
• CPC Class Codes: H04W 12/069 : using certificates or pre-shared keys
• CPC Class Codes: H04W 24/04 : Arrangements for maintaining operational condition
• CPC Class Codes: H04W 24/10 : Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 4/029 : Location-based management or tracking services
• CPC Class Codes: H04W 40/246 : Connectivity information discovery
• CPC Class Codes: H04W 52/0212 : managed by the network, e.g. network or access point is master and terminal is slave
• CPC Class Codes: H04W 52/383 : power control in peer-to-peer links
• CPC Class Codes: H04W 60/00 : Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 72/53 : based on regulatory allocation policies
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 76/14 : Direct-mode setup
• CPC Class Codes: H04W 80/045 : involving different protocol versions, e.g. MIPv4 and MIPv6
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 84/18 : Self-organising networks, e.g. ad-hoc networks or sensor networks
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/04 : adapted for relaying to or from another terminal or user
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: Y02D 30/70 : in wireless communication networks
• CPC Class Codes: Y04S 40/18 : Network protocols supporting networked applications, e.g. including control of end-device applications over a network
• CPC Class Codes: Y04S 40/20 : Information technology specific aspects, e.g. CAD, simulation, modelling, system security

Abstract

Systems and methods are provided for efficient communication through a fabric network of devices in a home environment or similar environment. For example, an electronic device may efficiently control communication to balance power and reliability concerns, may efficiently communicate messages to certain preferred networks by analyzing Internet Protocol version 6 (IPv6) packet headers that use an Extended Unique Local Address (EULA), may efficiently communicate software updates and status reports throughout a fabric network, and/or may easily and efficiently join a fabric network.

Claims

1. An electronic device comprising:

a memory or storage device storing instructions to operate a network stack;

a processor configured to execute the instructions to operate the network stack; and

a network interface configured to join a network-connected fabric of devices and communicate a message to a target device of the fabric of devices using the network stack;

wherein the network stack comprises;

an application layer configured to provide an application payload comprising data to be transmitted in the message;

a platform layer configured to encapsulate the application payload in a general message format of the message;

a transport layer configured to selectably transport the message using either User Datagram Protocol (UDP) or Transmission Control Protocol (TCP); and

a network layer configured to communicate the message using Internet Protocol Version 6 (IPv6) via;

an 802.11 wireless network;

an 802.15.4 wireless network;

a powerline network;

a cellular network;

an Ethernet network;

or

any combination thereof;

wherein the application layer, the platform layer, the transport layer, the network layer, or any combination thereof, are configured to determine a property of the manner of communication of the message to the target node based at least in part on;

a type of the message;

the network over which the message is to be sent;

a distance over which the message may travel through the fabric;

power consumption behavior of the electronic device;

power consumption behavior of the target device;

power consumption behavior of an intervening device of the fabric of devices that is to communicate the message between the electronic device and the target device;

whether the target device comprises a service;

or

any combination thereof; and

wherein varying the property of the manner of communication is configured to cause the electronic device, the target device, or the intervening device, or any combination thereof, to consume different amounts of power and cause the message to more reliably or less reliably reach the target node.

2. The electronic device of claim 1, wherein the property of the manner of communication comprises:

a determination to select Transmission Control Protocol (TCP) to transport the message;

a determination to select User Datagram Protocol (UDP) to transport the message;

a determination to communicate the message using a lower-power network;

a determination to communicate the message using a higher-power network;

a determination to select a preferred network of the target device as a higher-power network indicated in an Extended Unique Local Address (EULA) encoded in an IPv6 packet header of the message;

a determination to select a preferred network of the target device as a lower-power network indicated in the Extended Unique Local Address (EULA) encoded in the IPv6 packet header of the message;

or

any combination thereof.

3. The electronic device of claim 1, wherein the application layer is configured to determine whether to transport the message using Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) depending on an urgency of the message.

4. The electronic device of claim 3, wherein the message comprises an urgent message when the message communicates a device alarm and wherein the message comprises a non-urgent message when the message communicates an indication of a non-hazardous environmental condition without a device alarm.

5. A tangible, non-transitory computer-readable medium comprising instructions configured to be executed by a first electronic device communicably coupled to other electronic devices of a fabric of devices in a home environment, the instructions comprising instructions to:

receive an Internet Protocol version 6 (IPv6) message at the first electronic device from a second electronic device over a first network of the fabric of devices, wherein the message is bound for a target electronic device;

identify an Extended Unique Local Address encoded in an IPv6 header of the message, wherein the Extended Unique Local Address indicates that a second network is preferred to reach the target electronic device; and

communicate the message through the fabric of devices toward the target electronic device using second network based at least in part on the Extended Unique Local Address.

6. The computer-readable medium of claim 5, wherein the Extended Unique Local Address of the IPv6 packet header comprises a first field identifying the fabric of devices, a second field identifying that the second network is preferred to reach the target electronic device, and a third field comprising an extended unique identifier of the target electronic device.

7. The computer-readable medium of claim 6, wherein the first field comprises 48 bits, the second field comprises 16 bits, and the third field comprises 64 bits.

8. A method for transferring a software update over a fabric network, the method comprising:

sending an image query message from a first device in the fabric network to a second device in the fabric network or a local or remote server, wherein the image query message comprises information regarding software stored on the first device and transfer capabilities of the first device;

receiving at the first device an image query response from the second device or the local or remote server, wherein the image query response indicates whether the software update is available and includes download information having a uniform resource identifier (URI) to enable the first device to download the software update, and wherein the image query message comprises;

sender information regarding software stored on a sender device and transfer capabilities of the sender device; and

an update priority; and

downloading the software update at the first device from the sender device using the URI, wherein the software is downloaded at a time based at least in part on the update priority and network traffic in the fabric network, and wherein the software is downloaded in a manner based at least in part on common transfer capabilities indicated in the image query and the image query response.

9. The method of claim 8, comprising receiving at the first device an image announce message from the second device or the local or remote server, wherein the image announce message comprises a reference to the software update, and wherein the image announce message is configured to cause the first device to send the image query message.

10. The method of claim 8, wherein the image query message is sent from the first device according to a polling schedule.

11. The method of claim 10, wherein the polling schedule is determined at least in part based on whether the first device is scheduled for an awake or sleep state.

12. The method of claim 8, wherein the image query is stored in a non-transitory computer-readable medium and comprises:

a frame control field configured to indicate whether the image query message includes vendor-specific information or locality information;

a product specification field configured to indicate;

a vendor and product for the software update; and

a revision number for software stored on the device and to be updated;

a version specification field configured to indicate a version of the software update;

an integrity types supported field configured to indicate an integrity type associated with the first device; and

an update schemes supported field configured to indicate schemes supported by the first device for the update transfer.

13. The method of 12, wherein the integrity types supported field indicates an integrity type comprising secure hash algorithm (SHA)-160, SHA-256, or SHA-512, or any combination thereof.

14. The method of 12, wherein the update schemes supported field indicates an update scheme comprising:

hypertext transfer protocol (HTTP);

hypertext transfer protocol secure (HTTPS);

secure file transfer protocol (SFTP);

or

a bulk data transfer protocol for the fabric.

15. The method of 8, comprising sending a download notification from the first device to the second device or the local or remote server, wherein the download notification indicates that the software update was downloaded successfully.

16. The method of 8, comprising sending an update notification from the first device to the second device or the local or remote server, wherein the update notification indicates that the software update was installed successfully.

17. The method of 8, comprising receiving at the first device a notify response from the second device or the local or remote server, wherein the notify response is received after the first device sends a download notification or an update notification, wherein the download notification indicates that the software update was downloaded successfully and wherein the update notification indicates that the software update was installed successfully.

18. A tangible, non-transitory computer-readable medium storing a status reporting format, wherein the status reporting format comprises:

a profile field configured to indicate a status update type of a plurality of status update types;

a status code configured to indicate a status being reported, wherein the status code is configured to be interpreted in a manner based at least in part on the status update type; and

a next status field configured to indicate whether an additional status is included in a status report formed using the status reporting format.

19. The computer-readable medium of claim 18, wherein the status reporting format comprises an additional status information field when the next status field indicates an additional status is included in the status report.

20. The computer-readable medium of claim 19, wherein the additional status information field comprises data stored in a tag-length-value (TLV) format.

21. The computer-readable medium of claim 18, wherein the profile field is configured to indicate a vendor of a device that the status report relates to.

22. A first electronic device comprising:

memory configured to store instructions to enable the first electronic device to pair with a fabric network comprising a second electronic device;

a processor configured to execute the instructions; and

a network interface configured to access 802.11 and 802.15.4 logical networks;

wherein the instructions comprise instructions to;

establish communication with the second electronic device via a first 802.15.4 logical network, wherein the second electronic device is paired with the fabric network and configured to communicate with a service via another logical network in the fabric network;

receive network configuration information from the service via the second electronic device to enable the first electronic device to join a first 802.11 logical network;

establish communication over the first 802.11 logical network;

connect to the service via the first 802.11 logical network; and

register to pair with the fabric network via communication with the service.

23. The first electronic device of claim 22, wherein the instructions to establish communication with the second electronic device via the first 802.15.4 logical network comprise instructions to create the first 802.15.4 logical network and receive communication from the second electronic device via a rendezvous address.

24. The first electronic device of claim 22, wherein the instructions comprise instructions to receive a code from the service via the second electronic device, wherein the code originates from a client device logged into the service, wherein the code is configured to confirm that a user of the client device is in possession of the first electronic device when the code matches an expected value stored in the memory of the first electronic device.

25. The first electronic device of claim 24, wherein the instructions comprise instructions to establish communication over the first 802.11 logical network only when the code matches the expected value.

26. The first electronic device of claim 22, wherein the instructions comprise instructions to:

disconnect from the first 802.15.4 logical network; and

establish communication over a second 802.15.4 associated with the fabric network when the first electronic device has registered to pair with the fabric network via the communication with the service.