Premises system management using status signal

• US 10,447,491 B2
• Filed: 08/21/2018
• Issued: 10/15/2019
• Est. Priority Date: 03/16/2004
• Status: Active Grant

• Current Assignee: iControl Networks, Inc. (Comcast Corporation)
• Original Assignee: iControl Networks, Inc. (Comcast Corporation)
• Inventors: Dawes, Paul J., Decenzo, Chris, Wales, Carolyn
• Primary Examiner(s): Nguyen, Phung
• Application Number:
  US16/107,568
• Publication Number:
  US 20190068394A1
• Time in Patent Office: 420 Days
• CPC Class Codes: G06Q 50/06 Energy or water supply
• CPC Class Codes: G06Q 50/08 Construction
• CPC Class Codes: G06Q 50/12 Hotels or restaurants
• CPC Class Codes: G06Q 50/16 Real estate
• CPC Class Codes: G06Q 50/26 Government or public services business processes related to the transportation industry G06Q50/40
• CPC Class Codes: G08B 25/14 Central alarm receiver or annunciator arrangements
• 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/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/2825 Reporting to a device located outside the home and the home network access arrangements H04L12/2856; for remote control or remote monitoring of applications H04L67/025; telephonic communication systems adapted for combination with telemetering systems H04M11/002
• CPC Class Codes: H04L 12/2834 Switching of information between an external network and a home network access arrangements H04L12/2856
• CPC Class Codes: H04L 2012/2841 Wireless
• CPC Class Codes: H04L 2012/2843 Mains power line
• CPC Class Codes: H04L 2012/285 Generic home appliances, e.g. refrigerators
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display
• CPC Class Codes: H04M 11/04 with alarm systems, e.g. fire, police or burglar alarm systems

Abstract

Methods and systems for managing a security system are described. A remote device located external to a premises may be in communication with a security system and a gateway device located at the premises. A heartbeat signal may be sent to the remote device. The remote device may send one or messages based on a failure of the heartbeat signal.

Claims

1. A method comprising:

receiving, by a first device located external to a premises, from a gateway device located at the premises, and at a first time, state data associated with one or more security devices located at the premises;

determining, based on the receiving the state data at the first time and a failure to receive a heartbeat signal at a second time after the first time, an event; and

sending, by the first device and to a second device, data indicative of the event.

2. The method of claim 1, wherein the state data indicates arming of a security system comprising the one or more security devices.

3. The method of claim 1, wherein the state data indicates detection of an alarm condition based on sensor data associated with the one or more security devices.

4. The method of claim 1, wherein the event is indicative of one or more of a failure to receive the heartbeat signal while a security system is armed, a failure to receive the heartbeat signal after a sensor of the security system is triggered, or a failure to receive the heartbeat signal after a change in the state data occurs.

5. The method of claim 1, further comprising determining the failure to receive the heartbeat signal at the second time.

6. The method of claim 1, wherein the heartbeat signal is initiated, based on the state data, by the gateway device.

7. The method of claim 1, further comprising enabling, by the first device and based on receiving the state data, an alert mode associated with monitoring for a communication failure associated with the gateway device, wherein the second time occurs while the alert mode is enabled.

8. A system comprising:

a gateway device in communication with one or more security devices, wherein the gateway device and the one or more security devices are located at a premises; and

a first device in communication with the gateway device and located external to the premises, and wherein the first device is configured to;

receive, from the gateway device and at a first time, state data associated with one or more security devices located at the premises;

determine, based on the receiving the state data at the first time and a failure to receive a heartbeat signal at a second time after the first time, an event; and

send, to a second device, data indicative of the event.

9. The system of claim 8, wherein the state data indicates arming of a security system comprising the one or more security devices.

10. The system of claim 8, wherein the state data indicates detection of an alarm condition based on sensor data associated with the one or more security devices.

11. The system of claim 8, wherein the event is indicative of one or more of a failure to receive the heartbeat signal while a security system is armed, a failure to receive the heartbeat signal after a sensor of the security system is triggered, or a failure to receive the heartbeat signal after a change in the state data occurs.

12. The system of claim 8, wherein the heartbeat signal is initiated based on the gateway device detecting the state data.

13. The system of claim 8, wherein the first device is configured to cause the gateway device to send the heartbeat signal.

14. The system of claim 8, wherein the first device is configured to enable, based on receiving the state data, an alert mode associated with monitoring for a communication failure associated with the gateway device, wherein the second time occurs while the alert mode is enabled.

15. A device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the device to;

receive, from a gateway device located at a premises and at a first time, state data associated with one or more security devices located at the premises;

determine, based on the receiving the state data at the first time and a failure to receive a heartbeat signal at a second time after the first time, an event; and

send, to a computing device, data indicative of the event.

16. The device of claim 15, wherein the state data indicates arming of a security system comprising the one or more security devices.

17. The device of claim 15, wherein the state data indicates detection of an alarm condition based on sensor data associated with the one or more security devices.

18. The device of claim 15, wherein the event is indicative of one or more of a failure to receive the heartbeat signal while a security system is armed, a failure to receive the heartbeat signal after a sensor of the security system is triggered, or a failure to receive the heartbeat signal after a change in the state data occurs.

19. The device of claim 15, wherein the heartbeat signal is initiated, based on the state data, by the gateway device.

20. The device of claim 15, wherein the instructions, when executed by the one or more processors, further cause the device to enable, based on receiving the state data, an alert mode associated with monitoring for a communication failure associated with the gateway device, wherein the second time occurs while the alert mode is enabled.

21. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors, cause:

receiving, from a gateway device located at a premises and at a first time, state data associated with one or more security devices located at the premises;

determining, based on the receiving the state data at the first time and a failure to receive a heartbeat signal at a second time after the first time, an event; and

sending, to a computing device, data indicative of the event.

22. The computer-readable medium of claim 21, wherein the state data indicates arming of a security system comprising the one or more security devices.

23. The computer-readable medium of claim 21, wherein the state data indicates detection of an alarm condition based on sensor data associated with the one or more security devices.

24. The computer-readable medium of claim 21, wherein the event is indicative of one or more of a failure to receive the heartbeat signal while a security system is armed, a failure to receive the heartbeat signal after a sensor of the security system is triggered, or a failure to receive the heartbeat signal after a change in the state data occurs.

25. The computer-readable medium of claim 21, wherein the heartbeat signal is initiated, based on the state data, by the gateway device.

26. The computer-readable medium of claim 21, wherein the instructions, when executed by the one or more processors, further cause enabling, based on receiving the state data, an alert mode associated with monitoring for a communication failure associated with the gateway device, wherein the second time occurs while the alert mode is enabled.