IP Library Granted Patent US 11,302,169
Granted Patent B1
US 11,302,169 · App. 16/853,370 · Granted Apr 12, 2022

System and process for distributed network of redundant central stations

Inventor: Stephen Scott Trundle (Falls Church, VA)
Assignee: Alarm.com Incorporated
G08B21/0261G06F8/71G06F9/44536G06F9/505G08B13/08G08B13/19697G08B21/0227G08B21/0255G08B21/0275G08B25/005G08B25/14H04L12/66H04L41/0213H04L41/0816H04L41/50G08B25/009
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 11,302,169
App. No.
16/853,370
Granted
Apr 12, 2022
Kind
B1
Abstract

Techniques are described for distributing, to a distributed network of central stations, alarm events detected in monitoring system data collected by sensors included in monitoring systems located at monitored properties. A system receives monitoring system data collected by sensors included in monitoring systems located at monitored properties, tracks alarm events detected within the monitoring system data, and generates, for central station servers in a distributed network of central stations, load profiles that reflect a volume of alarm events being handled at each of the central station servers at a particular period of time. The system determines capacities to handle additional alarm events for the central station servers, determines relative priorities for the central station remote servers based on the determined capacities, and directs subsequent alarm events to the central station servers based on the relative priorities.

Claims (32)

1. A method of evaluating status of a central station server and redirecting monitoring data traffic, the method comprising:

determining, by a monitoring system, a status of a central station server used by the monitoring system;

determining, by the monitoring system and based on the determined status, that the central station server has experienced a failure, is busy, or is operating atypically;

based on the determination that the central station server has experienced a failure, is busy, or is operating atypically, determining, by the monitoring system, that an adjustment or reevaluation of monitoring data flow is in order; and

based on the determination that an adjustment or reevaluation of monitoring data flow is in order, redirecting, by the monitoring system, monitoring data traffic from the central station server,

wherein determining, by the monitoring system, the status of the central station server used by the monitoring system comprises determining a load profile for the central station server that indicates a volume of monitoring data being handled by the central station server over a period of time, and

wherein determining the load profile for the central station server that indicates the volume of monitoring data being handled by the central station server over the period of time comprises calculating the load profile based on performance parameters, including CPU usage, memory usage, CPU usage history, memory usage history, and capacity of operators to handle alarm events and dispatch emergency services.

2. The method of claim 1 , wherein determining, by the monitoring system and based on the determined status, that the central station server has experienced a failure, is busy, or is operating atypically comprises determining, by the monitoring system and based on the determined status, that the central station server has experienced a failure.

3. The method of claim 1 , wherein determining, by the monitoring system and based on the determined status, that the central station server has experienced a failure, is busy, or is operating atypically comprises determining, by the monitoring system and based on the determined status, that the central station server is busy.

4. The method of claim 1 , wherein determining, by the monitoring system and based on the determined status, that the central station server has experienced a failure, is busy, or is operating atypically comprises determining, by the monitoring system and based on the determined status, that the central station server is operating atypically.

5. The method of claim 1 , wherein determining, by the monitoring system, the status of the central station server used by the monitoring system comprises determining a status of the central station server based on monitoring data received and events that have been sent to the central station server for processing.

6. The method of claim 1 , wherein determining, by the monitoring system, the status of the central station server used by the monitoring system comprises receiving a status report from the central station server and determining a status of the central station server based on the received status report.

7. The method of claim 1 , wherein redirecting, by the monitoring system, monitoring data traffic from the central station server comprises preventing monitoring data traffic from being directed to the central station server.

8. The method of claim 1 , wherein redirecting, by the monitoring system, monitoring data traffic from the central station server comprises communicating, to the central station server, a stop status to enable the central station server to determine that the central station server is not being used until it confirms that it is available to process events.

9. The method of claim 1 , wherein determining the load profile for the central station server that indicates the volume of monitoring data being handled by the central station server over the period of time comprises determining a load profile that includes a load axis and a temporal axis and that tracks load over the period of time on the temporal axis.

10. The method of claim 1 , wherein determining, by the monitoring system and based on the determined status, that the central station server has experienced a failure, is busy, or is operating atypically comprises evaluating the load profile against an upper additional capacity threshold and a lower additional capacity threshold.

11. A monitoring system comprising:

at least one processor; and

at least one computer-readable storage medium coupled to the at least one processor having stored thereon instructions which, when executed by the at least one processor, causes the at least one processor to perform operations comprising:

determining a status of a central station server used by the monitoring system;

determining, based on the determined status, that the central station server has experienced a failure, is busy, or is operating atypically;

based on the determination that the central station server has experienced a failure, is busy, or is operating atypically, determining that an adjustment or reevaluation of monitoring data flow is in order; and

based on the determination that an adjustment or reevaluation of monitoring data flow is in order, redirecting monitoring data traffic from the central station server,

wherein determining the status of the central station server used by the monitoring system comprises determining a load profile for the central station server that indicates a volume of monitoring data being handled by the central station server over a period of time, and

wherein determining the load profile for the central station server that indicates the volume of monitoring data being handled by the central station server over the period of time comprises calculating the load profile based on performance parameters, including CPU usage, memory usage, CPU usage history, memory usage history, and capacity of operators to handle alarm events and dispatch emergency services.

12. The monitoring system of claim 11 , wherein determining, based on the determined status, that the central station server has experienced a failure, is busy, or is operating atypically comprises determining, based on the determined status, that the central station server has experienced a failure.

13. The monitoring system of claim 11 , wherein determining, based on the determined status, that the central station server has experienced a failure, is busy, or is operating atypically comprises determining, based on the determined status, that the central station server is busy.

14. The monitoring system of claim 11 , wherein determining, based on the determined status, that the central station server has experienced a failure, is busy, or is operating atypically comprises determining, based on the determined status, that the central station server is operating atypically.

15. The monitoring system of claim 11 , wherein determining the status of the central station server used by the monitoring system comprises determining a status of the central station server based on monitoring data received and events that have been sent to the central station server for processing.

16. The monitoring system of claim 11 , wherein determining the status of the central station server used by the monitoring system comprises receiving a status report from the central station server and determining a status of the central station server based on the received status report.

17. The monitoring system of claim 11 , wherein redirecting monitoring data traffic from the central station server comprises preventing monitoring data traffic from being directed to the central station server.

18. The monitoring system of claim 11 , wherein redirecting monitoring data traffic from the central station server comprises communicating, to the central station server, a stop status to enable the central station server to determine that the central station server is not being used until it confirms that it is available to process events.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 6, 2020
From: TRUNDLE, STEPHEN SCOTT
To: ALARM.COM INCORPORATED
Reel/Frame 052593/0329 →
Continuity (5)
Continuation 16389526 · Apr 19, 2019
Continuation 15984676 · May 21, 2018
Continuation 15590147 · May 9, 2017
Continuation 15069517 · Mar 14, 2016
Provisional Application 62132419 · Mar 12, 2015