Device integration framework

Patent metadata

Field	Value
Publication number	US-10423309-B2
Application number	US-201715645808-A
Country	US
Kind code	B2
Filing date	Jul 10, 2017
Priority date	Jun 12, 2007
Publication date	Sep 24, 2019
Grant date	Sep 24, 2019

Abstract

Systems, devices, and methods for managing a security system are described. A method may comprise receiving a request to join a security system by a user device. A whitelist may indicate devices, device types, device makes, device models, and/or device firmware versions authorized to join the security system. The method may further comprise enabling, based on a determination that the whitelist comprises an indication that the user device is authorized to join the security system, the user device to exchange data with the security system.

First claim

The invention claimed is:

1. A system comprising:
a security server configured to generate a whitelist of devices authorized to join a security system; and
a gateway device in communication with the security system, wherein the gateway device is configured to:
receive, from the security server, the whitelist and one or more rules for exchanging data with at least one of the authorized devices,
receive, from a user device, a request to join the security system, determine, based on the request, that the whitelist comprises an indication that the user device is authorized to join the security system, and
enable, based on the determination that the whitelist comprises the indication that the user device is authorized to join the security system, the user device to exchange data, using the one or more rules, with the security system.

2. The system of claim 1 , wherein the one or more rules for exchanging data with the at least one of the authorized devices comprises at least one of a device definition file, a rules engine, or security system device integration instructions.

3. The system of claim 1 , wherein the whitelist of devices authorized to join the security system comprises an indication of device makes, device models, or firmware versions authorized to join the security system.

4. The system of claim 1 , wherein the gateway device comprises a touchscreen.

5. The system of claim 1 , wherein enabling the user device to exchange data with the security system comprises updating a registry of authorized devices that are located at a premises to comprise an indication of the user device, wherein the registry of devices is stored on the gateway device.

6. The system of claim 1 , wherein the security server is further configured to receive an indication of a new authorized device type and update, based on the indication of the new authorized device type, the whitelist.

7. The system of claim 6 , wherein the security server is further configured to transmit, to the gateway device and based on updating the whitelist, the whitelist.

8. A method comprising:
receiving, by a gateway device located at a premises and from a user device located at the premises, a request to join a security system;
receiving, from a security server located external to the premises, a whitelist of devices authorized to join the security system and one or more rules for exchanging data with at least one of the authorized devices;
determining, based on the request, that the whitelist comprises an indication that the user device is authorized to join the security system; and
enabling, based on the determining that the whitelist comprises the indication that the user device is authorized to join the security system, the user device to exchange data, using the one or more rules, with the security system.

9. The method of claim 8 , wherein determining that the whitelist comprises the indication that the user device is authorized to join the security system comprises determining that the whitelist comprises an indication of at least one of an identification number or a name associated with the user device.

10. The method of claim 8 , wherein enabling the user device to exchange data with the security system comprises transmitting, to the security system, data from the user device.

11. The method of claim 8 , further comprising locally caching the one or more rules for exchanging data with the at least one of the authorized devices.

12. The method of claim 8 , further comprising transmitting, to the security server, a request for an updated whitelist.

13. The method of claim 8 , further comprising transmitting, to the security server and based on the request from the user device, a request for the whitelist.

14. The method of claim 8 , wherein the one or more rules for exchanging data with the at least one of the authorized devices comprise instructions for integrating the user device in the security system.

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 security server external to a premises, a whitelist of devices authorized to join a security system located at the premises and one or more rules for exchanging data with at least one of the authorized devices;
receive, from a user device, a request to join the security system;
determine, based on the request, that the whitelist comprises an indication that the user device is authorized to join the security system; and
enable, based on the determination that the whitelist comprises the indication that the user device is authorized to join the security system, the user device to exchange data, using the one or more rules, with the security system.

16. The device of claim 15 , wherein the instructions that, when executed by the one or more processors, cause the device to enable the user device to exchange data with the security system comprise instructions that, when executed by the one or more processors, cause the device to establish, using the one or more rules, a communication interface between the user device and the security system.

17. The device of claim 15 , wherein the instructions, that when executed by the one or more processors, cause the device to enable the user device to exchange data with the security system comprise instructions that, when executed by the one or more processors, cause the device to modify, using the one or more rules, firmware of the user device.

18. The device of claim 15 , wherein the instructions that, when executed by the one or more processors, cause the device to enable the user device to exchange data with the security system comprise instructions that, when executed by the one or more processors, cause the device to configure an application to facilitate exchange of data with the user device.

19. The device of claim 15 , wherein the one or more rules for exchanging data with the at least one of the authorized devices comprise a device definition file, and
wherein the instructions that, when executed by the one or more processors, cause the device to enable the user device to exchange data with the security system comprise instructions that, when executed by the one or more processors, cause the device to parse the device definition file and store representations of the user device from the device definition file.

20. The device of claim 15 , wherein the instructions that, when executed by the one or more processors, cause the device to enable the user device to exchange data with the security system comprise instructions that, when executed by the one or more processors, cause the device to initiate a communication session with the user device.

Assignees

• Icontrol Networks Inc

Inventors

• Kitchen Jim
• Dearman Clay
• Lea Thomas
• Bryan Mark
• Helen Adrian
• Proft David
• Speer Michael

Classifications

• H04L63/0227

  Filtering policies (mail message filtering H04L51/212) · CPC title

• H04L63/101

  Access control lists [ACL] · CPC title

• H04L67/025 Primary

  for remote control or remote monitoring of applications · CPC title

• G06F3/041

  Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means · CPC title

• G05B15/02

  electric · CPC title