Device-type handlers for remote control and monitoring of devices through a data network

Abstract

A method for providing automatic control of one or more devices in an environment including assessing information for the devices being paired with a hub or with a central server where the hub and the central server are configured to receive status messages from the devices and to issue commands to the devices; determining device-type handlers to use with the devices; installing the device-type handlers at the hub or the central server; installing an automation application on the hub or on the central server where the automation application responds to an event and issuing a command in response to the event; receiving a device-specific message from a source device at the hub or the central server; generating, using a device-type handler associated with the source device, a normalized event message; and providing the normalized event message to a processor in the hub or the central server.

The invention claimed is: 
     
       1. A node arranged for use in an An automation system for providing automatic control of one or more devices in an environment, the automation system including comprising: 
 a central server and a hub paired with the one or more devices, the node being selected from the group consisting of the central server and the hub, 
 wherein the node comprisingcentral server comprises: 
 a processor; and  
 a memory coupled with the processor; and storing: 
 an automation application at least partially installed on the node central server and configured to execute in response to the receipt of a normalized event message from a source device and to issue a normalized command in response to the normalized event message; and 
 a first device-type handler installed on the node central server, the first device-type handler configured to receive the normalized command and to generate a device specific command to a target device among that is one of the one or more devices paired with the hub; and 
 
 wherein the memory is configured to provide the processor with instructions which when executed cause the processor to: 
 receive a the normalized event message, the normalized event message received from the source device via a second event handler installed on the hub and associated with a the source device, the normalized event message being generated based on a device-specific message from the source device; 
 in response to the normalized event message, execute the automation application on the node central server to cause the automation application to issue a the normalized command in response to the normalized event message; 
 use the first device-type handler installed at the node central server, to generate a the device-specific command based on the normalized command; and 
 send the device-specific command to the target device, 
 wherein both the hub and the central server include device-type handlers configured to translate between device-specific messages and normalized messages for communicating with the target device, and 
 wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to:
 install the automation application on the central server. 
 
 
     
     
       2. The node as recited in  claim 1  wherein the node is the first hub. 
     
     
       3. The node as recited in  claim 1  wherein the node is the central server. 
     
     
       4. The node as recited in  claim 1 , wherein the normalized event message is received from a second hub paired with the source device, and the memory is further configured to provide the processor with instructions which when executed cause the processor to cause the normalized event message to be stored at the central server. 
     
     
       5. The node automation system as recited in  claim 1 , wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to:
 obtain identifying information associated with the one or more devices paired with the hub; and 
 determine using the identifying information device-type handlers to use with each of the one or more devices. 
 
     
     
       6. The node automation server as recited in  claim 1 , wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to:
 determine a set of devices being paired with a the hub; 
 determine a set of device-type handlers to use with the set of devices; and 
 install the a set of device-type handlers, to use with the set of devices, at the hub. 
 
     
     
       7. The node automation system as recited in  claim 1 , wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to:
 determine a set of devices being paired with a the hub; 
 determine a set of device-type handlers to use with the set of devices; and 
 install a second device-type handler from the a set of device-type handlers, to use with the set of devices, at the hub when a second automation application is installed at the hub to be executed on the hub to control or monitor a first device, the first device-type handler being associated with the first device. 
 
     
     
       8. The node as recited in  claim 1  wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to:
 install the automation application on the central server. 
 
     
     
       9. The node as recited in  claim 1  wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to:
 determine whether device-type handlers should be installed at the central server or the hub; 
 based on the determination, install device type handlers at the hub and the central server. 
 
     
     
       10. The node as recited in  claim 1  wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to:
 determine whether device-type handlers should be installed at the central server or the hub; 
 based on the determination, install the device-type handler at the central server and not the hub. 
 
     
     
       11. A method for providing automatic control of one or more devices in an environment using an automation system that includes a central server and a hub paired with the one or more devices, the hub and the central server each having device-type handlers installed thereon and being configured to receive status messages from the devices and to issue commands to the devices, the method comprising:
 executing an automation application on a node selected from the group consisting of the central server and the hub, the automation application responding to an event and issuing a command in response to the event;   generating a normalized command for the target device at the node;   generating, using the device-type handler installed at the node, a device-specific command based on the normalized command; and   sending the device-specific command to the target device.   
     
     
       12. The method of  claim 11  wherein the node is the central server and the device-specific command is sent to the target device through the hub without using the device-type handler installed at the hub to generate the device-specific command. 
     
     
       13. The method of  claim 11  wherein the node is the hub, the normalized command is generated at the node and the device-specific command is generated at the node based on the normalized command. 
     
     
       14. The method of  claim 11 , wherein the hub is in communication with the central server through a data network, and a source device is paired with the hub, the method further comprising:
 receiving a device-specific message from the source device at the hub;   generating, using a device-type handler associated with the source device, a normalized event message at the hub;   providing the normalized event message to a processor in the hub;   sending the normalized event message from the hub to the central server; and   storing or processing the normalized event message at the central server.   
     
     
       15. The method of  claim 14 , wherein the hub is in communication with the central server through a data network, and the target device is paired with the hub, wherein the execution of the automation application is performed in response to the normalized event message. 
     
     
       16. The method of  claim 14 , wherein the device-specific message from the source device comprises a protocol-specific message from the source device, the protocol-specific message being related to the communication protocol used by the source device. 
     
     
       17. The method of  claim 14 , wherein the device-specific command for the target device comprises a protocol-specific command being related to the communication protocol used by the target device. 
     
     
       18. The method of  claim 11 , further comprising:
 receiving, at the hub, a device-specific message from a source device paired with the hub;   generating, using the device-type handler installed at the hub, a normalized event message based on the received device-specific message; and   providing the normalized event message to a processor in the nose wherein the execution of the automation application on the node is in response to the normalized event message and wherein the normalized command generated at the nose is based on the normalized event message.   
     
     
       19. The method of  claim 11  wherein at least some of the device-type handlers are installed at both the central server and the hub and are arranged to process device-specific messages for the same target device. 
     
     
       20. A system for providing automatic control of one or more devices, the system comprising:
 a central server, and   a hub,   wherein the central server comprises:
 a memory configured to stored instructions; and 
   at least one processor configured to execute the instructions to:
 control to receive a status message of a source device paired to a hub; 
 based on the status message being received, obtain, using an automation application that is installed on the central server, a first command for the source device; 
 translate, using a first translation component installed on the central server, the obtained first command to a second command for communicating with the source device, wherein the first command is a normalized command and the second command is a device-specific command; and 
 control to send, toward the source device, the second command to which the obtained first command is translated, 
   wherein a second translation component is installed on the hub for communicating control commands with the source device, and the first and second translation components are configured to translate to and from a first protocol, and   wherein the first command is generated by the central server, and   wherein the at least one processor is configured to install the automation application on the central server.    
     
     
       21. The system of  claim 20 , wherein the at least one processor is configured to translate, using the first translation component installed on the central server, the status message.  
     
     
       22. The system of  claim 20 , wherein the at least one processor is configured to execute the instructions to control to send the second command to the source device through the hub.  
     
     
       23. The system of  claim 20 , wherein the at least one processor is configured to execute the instructions to translate, using the first translation component, the first command to the second command of the first protocol.  
     
     
       24. The system of  claim 20 , wherein the at least one processor is configured to execute the instructions to control to receive the status message from the source device through the hub.  
     
     
       25. The system of  claim 20 , wherein the at least one processor is configured to execute the instructions to translate, using the first translation component, the status message of the first protocol.  
     
     
       26. The system of  claim 20 , wherein the at least one processor is configured to execute the instructions to translate, using the first translation component, the first command to the second command of the first protocol.  
     
     
       27. The system of  claim 26 , wherein the first protocol is a device-specific protocol.  
     
     
       28. The system of  claim 20 , wherein the at least one processor is configured to execute the instructions to:
 control to receive, at the central server, another status message of another source device that is not paired to the hub;   based on the other status message being received, obtain, using the automation application that is installed on the central server, a third command for the other source device;   translate, using the first translation component installed on the central server, the obtained third command to a fourth command for communicating with the other source device; and   control to send, toward the other source device, the fourth command to which the obtained third command is translated.    
     
     
       29. The system of  claim 28 , wherein the at least one processor is configured to execute the instructions to control to send the fourth command to the other source device directly.  
     
     
       30. The system of  claim 28 , wherein the at least one processor is configured to execute the instructions to control to send the fourth command to the other source device through another hub to which the other source device is paired.