IP Library Granted Patent US 10,741,057
Granted Patent B2
US 10,741,057 · App. 16/059,833 · Granted Aug 11, 2020

Method and system for processing security event data

Inventors: Alan Wade Cohn (Redwood City, CA); Gary Robert Faulkner (Redwood City, CA); James Edward Kitchen (Redwood City, CA); David Leon Proft (San Francisco, CA); Corey Wayne Quain (Redwood City, CA)
Assignee: iControl Networks, Inc.
G08B25/14G08B25/004
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,741,057
App. No.
16/059,833
Granted
Aug 11, 2020
Kind
B2
Abstract

Methods and systems for processing data associated with a premises management system are disclosed. The data may comprise alarm event data and non-alarm event data. The alarm event data and non-alarm event data may be processed to determine whether to send a notification.

Claims (39)

1. A method, comprising:

receiving, by a computing device located external to a premises, first data indicative of an alarm event associated with a premises management system located at the premises;

determining, by the computing device, second data indicative of a non-alarm event associated with the premises management system, wherein the non-alarm event comprises one or more of a time delay event, a loss of communication event, a restoration of communication event, a disarming event, or an arming event;

determining, by the computing device and based on an association of the alarm event and the non-alarm event, to send a notification associated with the premises management system; and

sending the notification.

2. The method of claim 1 , wherein determining to send the notification comprises determining that one or more of the alarm event or the non-alarm event is associated with a security breach at the premises.

3. The method of claim 1 , wherein determining to send the notification comprises determining one or more non-alarm events, comprising the non-alarm event, that occur within a threshold time period before or after the alarm event and analyzing the alarm event with the one or more non-alarm events.

4. The method of claim 1 , wherein determining to send the notification comprises determining that an occurrence of both the non-alarm event and the alarm event is associated with a type of notification.

5. The method of claim 1 , wherein determining to send the notification comprises determining that occurrence of the alarm event and the non-alarm event is associated with a priority level triggering sending the notification.

6. The method of claim 1 , wherein determining the second data indicative of the non-alarm event comprises one or more of receiving, from the premises management system, the second data indicative of the non-alarm event or generating, by the computing device, the second data indicative of the non-alarm event.

7. The method of claim 1 , wherein the notification comprises one or more of data indicative of the alarm event, data indicative of an event condition indicative of one or more of the alarm event or the non-alarm event, or data indicative of the premises management system being in an alarm state.

8. The method of claim 1 , wherein the computing device comprises one or more of a server device, a security server, or a central monitoring station.

9. 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, external to a premises, first data indicative of an alarm event associated with a premises management system located at the premises;

determine second data indicative of a non-alarm event associated with the premises management system, wherein the non-alarm event comprises one or more of a time delay event, a loss of communication event, a restoration of communication event, a disarming event, or an arming event;

determine, based on an association of the alarm event and the non-alarm event, to send a notification associated with the premises management system; and

send the notification.

10. The device of claim 9 , wherein the instructions that, when executed by the one or more processors, cause the device to determine to send the notification comprises instructions that, when executed by the one or more processors, cause the device to determine that at least one of the alarm event or the non-alarm event is associated with a security breach at the premises.

11. The device of claim 9 , wherein the instructions that, when executed by the one or more processors, cause the device to determine to send the notification comprises instructions that, when executed by the one or more processors, cause the device to determine one or more non-alarm events, comprising the non-alarm event, that occur within a threshold time period before or after the alarm event and analyze the alarm event with the one or more non-alarm events.

12. The device of claim 9 , wherein the instructions that, when executed by the one or more processors, cause the device to determine to send the notification comprises instructions that, when executed by the one or more processors, cause the device to determine that an occurrence of both the non-alarm event and the alarm event is associated with a type of notification.

13. The device of claim 9 , wherein the instructions that, when executed by the one or more processors, cause the device to determine to send the notification comprises instructions that, when executed by the one or more processors, cause the device to determine that occurrence of the alarm event and the non-alarm event is associated with a priority level triggering sending the notification.

14. The device of claim 9 , wherein the instructions that, when executed by the one or more processors, cause the device to determine the second data indicative of the non-alarm event comprises instructions that, when executed by the one or more processors, cause the device to one or more of: receive, from the premises management system, the second data indicative of the non-alarm event or generate the second data indicative of the non-alarm event.

15. The device of claim 9 , wherein the notification comprises one or more of data indicative of the alarm event, data indicative of an event condition indicative of one or more of the alarm event or the non-alarm event, or data indicative of the premises management system being in an alarm state.

16. A non-transitory computer-readable medium storing computer-executable instructions that, when executed, cause:

receiving, by a computing device located external to a premises, first data indicative of an alarm event associated with a premises management system located at the premises;

determining, by the computing device, second data indicative of a non-alarm event associated with the premises management system, wherein the non-alarm event comprises one or more of a time delay event, a loss of communication event, a restoration of communication event, a disarming event, or an arming event;

determining, by the computing device and based on an association of the alarm event and the non-alarm event, to send a notification associated with the premises management system; and

sending the notification.

17. The non-transitory computer-readable medium of claim 16 , wherein determining to send the notification comprises determining that at least one of the alarm event or the non-alarm event is associated with a security breach at the premises.

18. The non-transitory computer-readable medium of claim 16 , wherein determining to send the notification comprises determining one or more non-alarm events comprising the non-alarm event that occur within a threshold time period before or after the alarm event and analyzing the alarm event with the one or more non-alarm events.

19. The non-transitory computer-readable medium of claim 16 , wherein determining to send the notification comprises determining that an occurrence of both the non-alarm event and the alarm event is associated with a type of notification.

20. The non-transitory computer-readable medium of claim 16 , wherein determining to send the notification comprises determining that occurrence of the alarm event and the non-alarm event is associated with a priority level triggering sending the notification.

21. The non-transitory computer-readable medium of claim 16 , wherein determining the second data indicative of the non-alarm event comprises one or more of receiving, from the premises management system, the second data indicative of the non-alarm event or generating, by the computing device, the second data indicative of the non-alarm event.

22. The non-transitory computer-readable medium of claim 16 , wherein the notification comprises one or more of data indicative of the alarm event, data indicative of an event condition indicative of one or more of the alarm event or the non-alarm event, or data indicative of the premises management system being in an alarm state.

23. The method of claim 1 , wherein sending the notification comprises sending the notification to an additional computing device external to the premises, wherein the additional computing device comprises one or more of a device located external to the premises, a user device, a server device, a portal server, or a central monitoring station.

24. The method of claim 1 , wherein determining the second data comprises determining, by the computing device, a failure to receive a communication from the premises management system within a time threshold.

25. The method of claim 1 , wherein determining to send the notification comprises determining that occurrence of the alarm event and the non-alarm event satisfies a notification rule.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 9, 2019
From: COHN, ALAN WADE; FAULKNER, GARY ROBERT; KITCHEN, JAMES EDWARD; PROFT, DAVID LEON; QUAIN, COREY WAYNE
To: ICONTROL NETWORKS, INC.
Reel/Frame 050305/0405 →
Continuity (3)
Continuation 14852822 · Sep 14, 2015
Continuation 12971282 · Dec 17, 2010
Related Publication 20190114903A1 · Apr 18, 2019
Cited By (1)
US 12,272,229