Device control profile for a fabric network

• US 9,661,093 B2
• Filed: 02/22/2016
• Issued: 05/23/2017
• Est. Priority Date: 10/08/2014
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Logue, Jay D., Stebbins, Andrew W., Trimble, Taylor J.
• Primary Examiner(s): Pollack, Melvin H
• Application Number:
  US15/050,195
• Publication Number:
  US 20160173613A1
• Time in Patent Office: 456 Days
• Field of Search: 709227
• CPC Class Codes: F24F 11/30 for purposes related to the operation of the system, e.g. for safety or monitoring
• CPC Class Codes: F24F 11/58 using Internet communication
• CPC Class Codes: F24F 11/62 characterised by the type of control or by internal processing, e.g. using fuzzy logic, adaptive control or estimation of values
• CPC Class Codes: F24F 11/63 Electronic processing
• CPC Class Codes: G05B 15/02 electric
• CPC Class Codes: G05B 19/042 using digital processors G05B19/05 takes precedence
• CPC Class Codes: G05B 2219/2642 Domotique, domestic, home control, automation, smart house
• CPC Class Codes: G06F 16/33 Querying
• CPC Class Codes: G06F 16/38 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G08B 17/10 Actuation by presence of smoke or gases , e.g. automatic alarm devices for analysing flowing fluid materials by the use of optical means
• CPC Class Codes: G08B 25/001 Alarm cancelling procedures or alarm forwarding decisions, e.g. based on absence of alarm confirmation
• CPC Class Codes: G08B 29/02 Monitoring continuously signalling or alarm systems
• CPC Class Codes: H04L 12/2803 Home automation networks
• CPC Class Codes: H04L 12/2809 indicating that an appliance service is present in a home automation network monitoring functionality H04L43/0817; discovery or management thereof, e.g. service location protocol [SLP] or web services, H04L67/51
• CPC Class Codes: H04L 12/281 indicating a format for calling an appliance service function in a home automation network for remote control or remote monitoring of applications H04L67/025
• CPC Class Codes: H04L 12/2818 from a device located outside both the home and the home network access arrangements H04L12/2856; for remote control or remote monitoring of applications H04L67/025; arrangements for transmitting signals characterised by the use of a wireless eletrical link G08C17/00; telephonic communication systems adapted for combination with remote control systems H04M11/007
• 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/283 Processing of data at an internetworking point of a home automation network
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0816 : the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/0886 : Fully automatic configuration
• CPC Class Codes: H04L 43/0805 : by checking availability
• CPC Class Codes: H04L 45/02 : Topology update or discovery
• CPC Class Codes: H04L 45/74 : Address processing for routing
• CPC Class Codes: H04L 61/4511 : using domain name system [DNS]
• CPC Class Codes: H04L 61/4541 : Directories for service discovery
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• 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/0876 : based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 65/1069 : Session establishment or de-establishment
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 : for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/04 : specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/06 : specially adapted for file transfer, e.g. file transfer protocol [FTP]
• 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/141 : Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/143 : Termination or inactivation of sessions, e.g. event-controlled end of session
• CPC Class Codes: H04L 67/303 : Terminal profiles
• CPC Class Codes: H04L 67/53 : using third party service providers
• CPC Class Codes: H04L 67/55 : Push-based network services
• CPC Class Codes: H04L 69/16 : Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/28 : Timers or timing mechanisms used in protocols
• CPC Class Codes: H04L 69/40 : for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04W 12/04 : Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/50 : Secure pairing of devices
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]

Abstract

Methods, systems, and instructions for remotely controlling devices using device control profiles are described herein. The device control profile may include resetting configuration data in a remote device, arming and disarming failsafes on remote devices, or enabling and disabling connection monitoring links to maintain an active connection between remote devices.

Claims

1. A non-transitory, computer-readable medium having stored thereon instructions for enabling control of a receiving device in a remote network using a device control profile, wherein the instructions are configured to cause a processor of the receiving device to:

receive a reset configuration request that includes an indication of a network configuration, a fabric configuration, a service configuration, or a combination thereof to be reset in the receiving device by setting the corresponding to a known state; and

transmit a status report from the receiving device indicating a status of a configuration reset invoked by the reset configuration request.

2. The non-transitory, computer-readable medium of claim 1, wherein the reset configuration request includes a plurality of flags each indicating whether corresponding configuration details in the receiving device are to be reset in response to the reset configuration request.

3. The non-transitory, computer-readable medium of claim 2, wherein the plurality of flags comprise:

a service flag indicating that service configuration details are to be reset;

a fabric flag indicating that fabric configuration details are to be reset; and

a network flag indicating that network configuration details are to be reset.

4. The non-transitory, computer-readable medium of claim 2, wherein the instructions are configured to cause the processor to reset the configuration details of the receiving device corresponding to one or more of the plurality of flags in response to the reset configuration request.

5. The non-transitory, computer-readable medium of claim 4, wherein the instructions are configured to cause the processor to transmit the status report to a requesting device prior to resetting the configuration details of the receiving device to reduce likelihood of loss of communication with the requesting device prior to sending the status report to the requesting device.

6. The non-transitory, computer-readable medium of claim 1, wherein the instructions are configured to cause the processor to reset configuration details indicated in the indication only after the status report has been transmitted from the receiving device to a requesting device that sent the reset configuration request.

7. The non-transitory, computer-readable medium of claim 1, wherein the instructions are configured to cause the processor to determine that the reset configuration request indicates an unsupported state, and wherein the status report includes an unsupported failsafe mode indicator that indicates the receiving device cannot perform the reset.

8. A method for remotely arming a failsafe mode for a first device using a device control profile, comprising:

receiving, at the first device, an arm failsafe request configured to cause the first device to arm a configuration failsafe, wherein the configuration failsafe is configured to prevent partial configuration or improper configuration of the first device;

determining, at the first device, whether the configuration failsafe has already been armed; and

transmitting, to a remote device that sent the arm failsafe request, a status report indicating whether the requested configuration failsafe is able to be armed.

9. The method of claim 8, comprising setting an indicator that the configuration failsafe has been armed.

10. The method of claim 8, wherein the arm failsafe request comprises:

a failsafe mode identifier that indicates a type of failsafe mode to be initiated; and

a failsafe token configured to indicate to other devices connecting to the first device that the first device has already had its configuration failsafe armed.

11. The method of claim 10, wherein the arm failsafe request is part of a provisioning process used to provision the first device for connection with the other devices as:

a fabric provisioning;

a service provisioning;

or

a network provisioning.

12. The method of claim 11, wherein a value of the failsafe token is unique to each provisioning attempt to indicate to the other devices connecting to the first device whether a session for the failsafe mode activated is a failsafe armed by the other devices or a different failsafe.

13. The method of claim 10, wherein the failsafe mode comprises:

a new failsafe mode indicating that a new failsafe is to be armed;

a reset failsafe mode indicating that a failsafe is to be armed regardless of a current status of the failsafe in the first device; and

a resume existing mode indicating that the failsafe may be armed or the failsafe may be resumed.

14. The method of claim 10, wherein:

the arm failsafe request fails if the failsafe mode is a new failsafe mode and a failsafe is already armed on the first device;

or

the arm failsafe request fails if the failsafe mode is a resume failsafe mode and the failsafe is already armed on the first device that does not match the failsafe token indicated in the arm failsafe request.

15. The method of claim 10, comprising:

receiving a disarm failsafe request; and

determining if the configuration failsafe is armed;

if the configuration failsafe is armed;

disarming the configuration failsafe in response to the disarm failsafe request by clearing the failsafe token; and

sending a success status report to the remote device that sent the disarm failsafe request; and

if the configuration failsafe is not armed, sending a failure status report to the remote device that sent the disarm failsafe request.

16. An electronic device, comprising:

a network interface;

memory; and

a processor configured to;

receive, via the network interface, an enable connection monitor request that is configured to enable a liveness monitor on a Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) connection monitoring between the electronic device and a remote device, wherein the enable connection monitor request comprises;

a connection monitor timeout field that indicates how long a connection monitor can remain idle before the connection monitor is terminated; and

a connection monitor interval field that indicates how frequently an update is sent to the remote device; and

send, via the network interface, a status report indicating whether the connection monitor has successfully been enabled.

17. The electronic device of claim 16, wherein the connection monitor timeout field is allocated two bytes of data, and the connection monitor interval field is allocated two bytes of data.

18. The electronic device of claim 16, wherein the processor is configured to:

send, via the network interface, an echo request with an exchange identifier; and

receive, via the network interface, an echo response with the exchange identifier, wherein the exchange identifier indicates that the echo response corresponds to the echo request.

19. The electronic device of claim 16, wherein the processor is configured to:

receive, via the network interface, a disable connection monitor request to terminate the connection monitor; and

send, via the network interface, a status report indicating whether a commissioning device has received the disable connection monitor and disabled the connection monitor.

20. The electronic device of claim 19, wherein the connection monitor request is configured to cause an active connection monitoring link to prevent unintended tunnel termination until a timeout indicated in the connection monitor timeout field has elapsed even if the remote device closes a read-write side of its connection to the electronic device through the tunnel.