Device control profile for a fabric network

Patent metadata

Field	Value
Publication number	US-2016173613-A1
Application number	US-201615050195-A
Country	US
Kind code	A1
Filing date	Feb 22, 2016
Priority date	Oct 8, 2014
Publication date	Jun 16, 2016
Grant date	—

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.

First claim

What is claimed is:

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, wherein the reset configuration request 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 resent 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 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 a status report has been transmitted from the receiving device to a requesting device that sent the reset configuration details 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, wherein the status report includes that an unsupported failsafe mode indicator that indicates that 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 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 a 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 other devices as a:
fabric provisioning; service provisioning; or network provisioning.

12 . The method of claim 11 , wherein a value of the failsafe token is unique to each provisioning attempt to indicate to 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 current status of a failsafe in the first device; and a resume existing mode indicating that a failsafe may be armed or a 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; and the arm failsafe request fails if the failsafe mode is a resume failsafe mode and a 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 remote device sending the disarm failsafe request; and
if the configuration failsafe is not armed, sending a failure status report to the remote device sending the disarm failsafe request.

16 . An electronic device, comprising:
a network interface; memory; and a processor, wherein the processor is 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 or uniform datagram protocol 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 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 field is allocated 2 bytes of data, and the connection monitor interval field is allocated 2 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 is configured to indicate 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 the 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 ti

Assignees

• Google Inc

Inventors

• Logue Jay D
• Stebbins Andrew W
• Trimble Taylor J

Classifications

• H04L69/28

  Timers or timing mechanisms used in protocols · CPC title

• H04L45/74

  Address processing for routing · CPC title

• G08B25/001

  Alarm cancelling procedures or alarm forwarding decisions, e.g. based on absence of alarm confirmation · CPC title

• H04L67/12

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

• G08B29/02

  Monitoring continuously signalling or alarm systems · CPC title