# US 2017/0257257 A1 · Coordinated control of connected devices in a premise

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0257257 A1
- Document ID: US20170257257A1
- Status: Published application
- Kind: A1
- Application number: 15/292,866
- Filed: 2016-10-13
- Published: 2017-09-07
- Earliest claimed: 2008-08-11
- Inventors: Paul DAWES; Dana BURD; Chris DECENZO; Frank CHU; Ren BITONIO
- Web page: https://patentgrep.com/patent/US20170257257A1

## CPC

- H04L 41/06: Management of faults, events, alarms or notifications
- G06F 16/954: Navigation, e.g. using categorised browsing
- 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)}
- 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)}
- H04L 12/283: {Processing of data at an internetworking point of a home automation network}
- H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes}
- H04L 67/025: for remote control or remote monitoring of applications
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/166: {at the transport layer}
- H04L 2012/2841: {Wireless}
- H04L 2012/2843: {Mains power line}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system comprises a bridge server configured to exchange event data and control data with premises devices. An application server coupled to the bridge server is configured to exchange the event data and the control data with the bridge server. The application server includes virtual devices comprising logical models corresponding to the premises devices and configured to use the event data and the control data to maintain state of the premises devices. The application server includes a rules engine configured to control interaction among the premises devices. An application engine coupled to the application server communicates with a device application configured for execution when installed on a remote device. The device application generates a user interface configured to present the event data and state of the premises devices and receive as input the control data of the premises devices.

## Claims

### Claim 1

A system comprising:
a bridge server configured to exchange event data and control data with a plurality of premises devices installed in a premises, wherein the plurality of premises devices includes a plurality of data protocols;
an application server coupled to the bridge server and configured to exchange the event data and the control data with the bridge server, wherein the application server includes a plurality of virtual devices comprising logical models corresponding to the plurality of premises devices and configured to use the event data and the control data to maintain state of the plurality of premises devices, wherein the application server includes a rules engine configured to control interaction among the plurality of premises devices; and
an application engine coupled to the application server and configured to communicate with a device application, wherein the device application is configured for execution when installed on a remote device, wherein the device application is configured to present a user interface at the remote device, wherein the user interface is configured to present the event data and state of the plurality of premises devices and receive as input the control data of the plurality of premises devices.

### Claim 2 (depends on 1)

The system of claim 1, wherein the bridge server includes an event bus coupled to a plurality of device interfaces, wherein each device interface is configured to transfer the event data and the control data between a corresponding premises device and the event bus.

### Claim 3 (depends on 2)

The system of claim 2, wherein each device interface is specific to a protocol of the corresponding premises device.

### Claim 4 (depends on 3)

The system of claim 3, wherein each device interface includes a plug-in component.

### Claim 5 (depends on 2)

The system of claim 2, wherein the bridge server includes a subscriber interface coupled to the event bus, wherein the subscriber interface includes a plurality of agents, wherein each agent is configured to transfer the event data and the control data of a corresponding premises device.

### Claim 6 (depends on 5)

The system of claim 5, wherein the subscriber interface is configured to exchange the event data and the control data between the event bus and the application server.

### Claim 7 (depends on 5)

The system of claim 5, wherein each agent is specific to a protocol of the corresponding premises device.

### Claim 8 (depends on 1)

The system of claim 1, comprising a rules engine configured to control interaction among the plurality of premises devices.

### Claim 9 (depends on 8)

The system of claim 8, wherein the rules engine includes a rule set configured to control a state change of a first premises device in response to the event data of a second premises device.

### Claim 10 (depends on 8)

The system of claim 8, wherein at least one of the application server and a premises gateway hosts the rules engine.

### Claim 11 (depends on 10)

The system of claim 10, wherein the application server hosts a first component of the rules engine, wherein the first component is configured to run a first rule set configured to control a state change of a first premises device in response to the event data of a second premises device.

### Claim 12 (depends on 11)

The system of claim 11, wherein the premises gateway hosts a second component of the rules engine, wherein the second component is configured to run a second rule set configured to control a state change of a third premises device in response to the event data of a fourth premises device.

### Claim 13 (depends on 12)

The system of claim 12, wherein the first premises device includes a first data protocol, and the second premises device includes a second data protocol different from the first data protocol.

### Claim 14 (depends on 11)

The system of claim 11, wherein the third premises device and the fourth premises device include a third data protocol.

### Claim 15 (depends on 8)

The system of claim 8, comprising automation rules running on the rules engine, wherein the automation rules include actions and triggers for controlling interactions between the plurality of premises devices.

### Claim 16 (depends on 15)

The system of claim 15, wherein the rules engine is configured to treat an event relating to a corresponding premises device as a trigger for at least one rule.

### Claim 17 (depends on 16)

The system of claim 16, wherein in response to the event the at least one rule triggers at least one action event to at least one of the partner device, at least one other partner device, and at least one of the plurality of devices.

### Claim 18 (depends on 8)

The system of claim 8, comprising a security system installed in the premises, wherein the security system is coupled to the bridge server, wherein the security system includes a plurality of security components.

### Claim 19 (depends on 18)

The system of claim 18, wherein the user interface is configured to present the event data and state of the security system and receive as input the control data of the security system.

### Claim 20 (depends on 18)

The system of claim 18, wherein the rules engine is configured to control interaction among the plurality of premises devices and the plurality of security components of the security system.

### Claim 21 (depends on 20)

The system of claim 20, wherein the rules engine includes a rule set configured to control a state change of a premises device in response to the event data of a security system component.

### Claim 22 (depends on 20)

The system of claim 20, wherein the rules engine includes a rule set configured to control a state change of the security system in response to the event data of a premises device.

### Claim 23 (depends on 1)

The system of claim 1, wherein each virtual device is configured to represent a state change of a corresponding premises device using at least one of control data and the event data of the corresponding premises device.

### Claim 24 (depends on 1)

The system of claim 1, comprising a premises gateway installed in a premises.

### Claim 25 (depends on 24)

The system of claim 24, wherein the premises gateway comprises a server connection component configured to communicate with at least one server.

### Claim 26 (depends on 25)

The system of claim 25, comprising a gateway server coupled to the application server and the premises gateway, wherein the gateway server is configured to manage gateway components of the premises gateway.

### Claim 27 (depends on 24)

The system of claim 24, wherein the premises gateway comprises a plurality of communication components configured to communicate with the plurality of premises devices.

### Claim 28 (depends on 27)

The system of claim 27, wherein the plurality of premises devices is coupled to the gateway.

### Claim 29 (depends on 27)

The system of claim 27, wherein at least one premises device of the plurality of premises devices are coupled to the gateway.

### Claim 30 (depends on 24)

The system of claim 24, wherein the premises gateway comprises a device management component configured to manage communications with the plurality of premises devices.

### Claim 31 (depends on 24)

The system of claim 24, wherein the premises gateway comprises a rules engine configured to control interaction among a set of premises devices of the plurality of premises devices.

### Claim 32

A method comprising:
configuring a bridge server to exchange event data and control data with a plurality of premises devices installed in a premises, wherein the plurality of premises devices includes a plurality of data protocols;
configuring an application server to exchange the event data and the control data with the bridge server, wherein the application server includes a plurality of virtual devices comprising logical models corresponding to the plurality of premises devices and configured to use the event data and the control data to maintain state of the plurality of premises devices, wherein the application server includes a rules engine configured to control interaction among the plurality of premises devices; and
configuring an application engine to communicate with a device application, wherein the device application is configured for execution when installed on a remote device, wherein the device application is configured to present a user interface at the remote device, wherein the user interface is configured to present the event data and state of the plurality of premises devices and receive as input the control data of the plurality of premises devices.

### Claim 33 (depends on 32)

The method of claim 32, comprising configuring the bridge server to include an event bus coupled to a plurality of device interfaces, wherein each device interface is configured to transfer the event data and the control data between a corresponding premises device and the event bus.

### Claim 34 (depends on 33)

The method of claim 33, wherein each device interface is specific to a protocol of the corresponding premises device.

### Claim 35 (depends on 34)

The method of claim 34, wherein each device interface includes a plug-in component.

### Claim 36 (depends on 33)

The method of claim 33, comprising configuring the bridge server to include a subscriber interface coupled to the event bus, wherein the subscriber interface includes a plurality of agents, wherein each agent is configured to transfer the event data and the control data of a corresponding premises device.

### Claim 37 (depends on 36)

The method of claim 36, comprising configuring the subscriber interface to exchange the event data and the control data between the event bus and the application server.

### Claim 38 (depends on 36)

The method of claim 36, wherein each agent is specific to a protocol of the corresponding premises device.

### Claim 39 (depends on 32)

The method of claim 32, comprising configuring a rules engine to control interaction among the plurality of premises devices.

### Claim 40 (depends on 39)

The method of claim 39, comprising configuring a rule set of the rules engine to control a state change of a first premises device in response to the event data of a second premises device.

### Claim 41 (depends on 39)

The method of claim 39, wherein at least one of the application server and a premises gateway hosts the rules engine.

### Claim 42 (depends on 41)

The method of claim 41, comprising configuring the application server to host a first component of the rules engine, wherein the first component is configured to run a first rule set configured to control a state change of a first premises device in response to the event data of a second premises device.

### Claim 43 (depends on 42)

The method of claim 42, comprising configuring the premises gateway to host a second component of the rules engine, wherein the second component is configured to run a second rule set configured to control a state change of a third premises device in response to the event data of a fourth premises device.

### Claim 44 (depends on 43)

The method of claim 43, wherein the first premises device includes a first data protocol, and the second premises device includes a second data protocol different from the first data protocol.

### Claim 45 (depends on 42)

The method of claim 42, wherein the third premises device and the fourth premises device include a third data protocol.

### Claim 46 (depends on 39)

The method of claim 39, comprising configuring automation rules running on the rules engine to include actions and triggers for controlling interactions between the plurality of premises devices.

### Claim 47 (depends on 46)

The method of claim 46, comprising configuring the rules engine to treat an event relating to a corresponding premises device as a trigger for at least one rule.

### Claim 48 (depends on 47)

The method of claim 47, wherein in response to the event the at least one rule triggers at least one action event to at least one of the partner device, at least one other partner device, and at least one of the plurality of devices.

### Claim 49 (depends on 39)

The method of claim 39, wherein a security system is installed in the premises, wherein the security system is coupled to the bridge server, wherein the security system includes a plurality of security components.

### Claim 50 (depends on 49)

The method of claim 49, comprising configuring the user interface to present the event data and state of the security system and receive as input the control data of the security system.

### Claim 51 (depends on 49)

The method of claim 49, comprising configuring the rules engine to control interaction among the plurality of premises devices and the plurality of security components of the security system.

### Claim 52 (depends on 51)

The method of claim 51, wherein the rules engine includes a rule set configured to control a state change of a premises device in response to the event data of a security system component.

### Claim 53 (depends on 51)

The method of claim 51, wherein the rules engine includes a rule set configured to control a state change of the security system in response to the event data of a premises device.

### Claim 54 (depends on 32)

The method of claim 32, comprising configuring each virtual device to represent a state change of a corresponding premises device using at least one of control data and the event data of the corresponding premises device.

### Claim 55 (depends on 32)

The method of claim 32, wherein a premises gateway is installed in the premises.

### Claim 56 (depends on 55)

The method of claim 55, comprising configuring a server connection component of the premises gateway to communicate with at least one server.

### Claim 57 (depends on 56)

The method of claim 56, comprising configuring a gateway server, coupled to the application server and the premises gateway, to manage gateway components of the premises gateway.

### Claim 58 (depends on 55)

The method of claim 55, comprising configuring a plurality of communication components of the premises gateway to communicate with the plurality of premises devices.

### Claim 59 (depends on 58)

The method of claim 58, wherein the plurality of premises devices is coupled to the gateway.

### Claim 60 (depends on 58)

The method of claim 58, wherein at least one premises device of the plurality of premises devices are coupled to the gateway.

### Claim 61 (depends on 55)

The method of claim 55, comprising configuring a device management component of the premises gateway to manage communications with the plurality of premises devices.

### Claim 62 (depends on 55)

The method of claim 55, comprising configuring a rules engine of the premises gateway to control interaction among a set of premises devices of the plurality of premises devices.
