INTEGRATED CLOUD SYSTEM FOR PREMISES AUTOMATION
A system comprises premises equipment including premises devices located at a premises. The system includes a partner device located at the premises and configured to use a partner protocol different from a protocol of the premises equipment. The system includes a system server configured to interact with the premises devices. The system server is configured to interact with the partner device via a partner proxy corresponding to the partner device. The system includes automation rules coupled to the system server. The automation rules include actions and triggers for controlling interactions between at least one of the partner device and the premises devices. The system includes a user interface coupled to the system server and configured to interact with the premises devices and the partner device.
1 . A system comprising:
premises equipment comprising a plurality of premises devices located at a premises, wherein the premises equipment corresponds to a service provider;
a partner device located at the premises and configured to use a partner protocol different from a protocol of the premises equipment;
a system server configured to interact with the plurality of premises devices, wherein the system server is configured to interact with the partner device via a partner proxy corresponding to the partner device;
automation rules coupled to the system server, wherein the automation rules include actions and triggers for controlling interactions between at least one of the partner device and the plurality of premises devices;
a user interface coupled to the system server and configured to interact with the plurality of premises devices and the partner device.
2 . The system of claim 1 , wherein the user interface includes a partner user interface corresponding to the partner device, wherein the partner user interface configures the user interface to interact with the partner device.
3 . The system of claim 2 , wherein the partner user interface is configured to at least one of create and edit at least one rule of the automation rules.
4 . The system of claim 2 , wherein the partner user interface is configured to delete at least one rule of the automation rules.
5 . The system of claim 2 , wherein the partner proxy is configured to interact with a partner server and the partner device, wherein the partner server corresponds to the partner device and the partner proxy.
6 . The system of claim 5 , wherein the partner device at least one of controls and triggers automations in the plurality of premises devices via the partner server.
7 . The system of claim 6 , wherein the system server is configured to include the partner proxy and to communicate with the partner server via the partner proxy.
8 . The system of claim 5 , wherein the partner proxy is configured to proxy calls from the partner user interface to the partner server.
9 . The system of claim 5 , wherein the partner user interface is embedded in the user interface.
10 . The system of claim 5 , comprising an integration server coupled to the system server.
11 . The system of claim 10 , wherein the system server includes an integration application programming interface (API).
12 . The system of claim 11 , wherein integration server is coupled to the integration API.
13 . The system of claim 11 , comprising an event bus coupled to the system server and the integration server.
14 . The system of claim 10 , wherein the integration server is coupled to the partner server.
15 . The system of claim 10 , comprising an integration adapter coupled to the integration server.
16 . The system of claim 15 , wherein the integration adapter is configured to translate between protocols of the system server and the partner server.
17 . The system of claim 15 , wherein the integration adapter is coupled to the partner server.
18 . The system of claim 17 , wherein the integration adapter is configured to provide endpoints for associating with the partner device.
19 . The system of claim 17 , wherein the integration adapter is configured to process events coming from the integration server, wherein the events comprise device data corresponding to the partner device.
20 . The system of claim 19 , wherein the device data includes at least one of state data, control data, and command data.
21 . The system of claim 17 , wherein the integration adapter is configured to send events to the integration server.
22 . The system of claim 21 , wherein the integration adapter is configured to send events including acknowledgment of incoming system events.
23 . The system of claim 17 , wherein the integration adapter is configured as an endpoint for managed partner device events to be reported to the system server.
24 . The system of claim 5 , comprising a rules engine, wherein the rules engine is configured to run the automation rules.
25 . The system of claim 24 , wherein the rules engine is configured to run on the premises equipment.
26 . The system of claim 24 , wherein the rules engine is configured to run on the system server.
27 . The system of claim 24 , wherein the rules engine is configured to run on at least one of the system server and the premises equipment.
28 . The system of claim 24 , wherein the rules engine is configured to treat an event relating to the partner device as a trigger for at least one rule.
29 . The system of claim 28 , 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.
30 . The system of claim 5 , wherein the partner user interface includes a list comprising a plurality of partners, wherein the plurality of partners correspond to a plurality of partner devices.
31 . The system of claim 30 , wherein the partner user interface is configured with partner data of the partner device received from the system server in response to selection of a corresponding partner from the plurality of partners.
32 . The system of claim 31 , wherein the partner user interface is configured to authenticate with the partner server a user corresponding to the partner device.
33 . The system of claim 32 , wherein the system server is configured with information of the partner device as a result of authentication of the user.
34 . The system of claim 5 , wherein the partner user interface interacts with the partner server via the partner proxy.
35 . The system of claim 34 , wherein the partner user interface receives data relating to the partner device from the partner server.
36 . The system of claim 5 , comprising an integration descriptor, wherein the integration descriptor includes capabilities data of the partner device.
37 . The system of claim 36 , wherein the capabilities data includes at least one of attributes, actions, events, and associated parameters of the partner device.
38 . The system of claim 36 , wherein the integration descriptor is configured for use to provide access to capabilities of the system server.
39 . The system of claim 36 , comprising a rules template file including a description of available functionality of at least one of the plurality of premises devices and the partner device.
40 . A method comprising:
configuring a system server to interact with premises equipment including a plurality of premises devices located at the premises, wherein the premises equipment corresponds to a service provider;
configuring the system server to interact with a partner device at the premises via a partner proxy corresponding to the partner device, wherein the partner device is configured to use a partner protocol different from a protocol of the premises equipment;
configuring automation rules to control interactions between at least one of the partner device and the plurality of premises devices using actions and triggers;
configuring a user interface coupled to the system server to interact with the plurality of premises devices and the partner device.
41 . The method of claim 40 , comprising configuring the user interface to include a partner user interface corresponding to the partner device, wherein the partner user interface configures the user interface to interact with the partner device.
42 . The method of claim 41 , comprising configuring the partner user interface to at least one of create and edit at least one rule of the automation rules.
43 . The method of claim 41 , comprising configuring the partner user interface to delete at least one rule of the automation rules.
44 . The method of claim 41 , comprising configuring the partner proxy to interact with a partner server and the partner device, wherein the partner server corresponds to the partner device and the partner proxy.
45 . The method of claim 44 , comprising configuring the partner device to at least one of control and trigger automations in the plurality of premises devices via the partner server.
46 . The method of claim 45 , comprising configuring the system server to include the partner proxy and to communicate with the partner server via the partner proxy.
47 . The method of claim 44 , comprising configuring the partner proxy to proxy calls from the partner user interface to the partner server.
48 . The method of claim 44 , comprising embedding the partner user interface in the user interface.
49 . The method of claim 44 , comprising configuring an integration server to communicate with the system server.
50 . The method of claim 49 , comprising configuring the system server to include an integration application programming interface (API).
51 . The method of claim 50 , comprising configuring the integration server to communicate with the integration API.
52 . The method of claim 50 , comprising configuring an event bus to communicate with the system server and the integration server.
53 . The method of claim 49 , comprising configuring the integration server to communicate with the partner server.
54 . The method of claim 49 , comprising configuring the integration server to communicate with an integration adapter.
55 . The method of claim 54 , wherein the integration adapter is configured to translate between protocols of the system server and the partner server.
56 . The method of claim 54 , wherein the integration adapter is coupled to the partner server.
57 . The method of claim 56 , wherein the integration adapter is configured to provide endpoints for associating with the partner device.
58 . The method of claim 56 , wherein the integration adapter is configured to process events coming from the integration server, wherein the events comprise device data corresponding to the partner device.
59 . The method of claim 58 , wherein the device data includes at least one of state data, control data, and command data.
60 . The method of claim 56 , wherein the integration adapter is configured to send events to the integration server.
61 . The method of claim 60 , wherein the integration adapter is configured to send events including acknowledgment of incoming system events.
62 . The method of claim 56 , wherein the integration adapter is configured as an endpoint for managed partner device events to be reported to the system server.
63 . The method of claim 44 , comprising configuring a rules engine to run the automation rules.
64 . The method of claim 63 , comprising configuring the rules engine to run on the premises equipment.
65 . The method of claim 63 , comprising configuring the rules engine to run on the system server.
66 . The method of claim 63 , comprising configuring the rules engine to run on at least one of the system server and the premises equipment.
67 . The method of claim 63 , comprising configuring the rules engine to treat an event relating to the partner device as a trigger for at least one rule.
69 . The method of claim 68 , comprising, in response to the event, triggering with the at least one rule 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.
70 . The method of claim 44 , comprising configuring the partner user interface to include a list comprising a plurality of partners, wherein the plurality of partners correspond to a plurality of partner devices.
71 . The method of claim 70 , comprising configuring the partner user interface with partner data of the partner device received from the system server in response to selection of a corresponding partner from the plurality of partners.
72 . The method of claim 71 , comprising configuring the partner user interface to authenticate with the partner server a user corresponding to the partner device.
73 . The method of claim 72 , comprising configuring the system server with information of the partner device as a result of authentication of the user.
74 . The method of claim 44 , comprising configuring the partner user interface to interact with the partner server via the partner proxy.
75 . The method of claim 74 , comprising configuring the partner user interface to receive data relating to the partner device from the partner server.
76 . The method of claim 44 , comprising configuring an integration descriptor to include capabilities data of the partner device.
77 . The method of claim 76 , wherein the capabilities data includes at least one of attributes, actions, events, and associated parameters of the partner device.
78 . The method of claim 76 , comprising configuring the integration descriptor for use to provide access to capabilities of the system server.
79 . The method of claim 76 , comprising configuring a rules template file to include a description of available functionality of at least one of the plurality of premises devices and the partner device.