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

• US 9,529,344 B1
• Filed: 03/15/2013
• Issued: 12/27/2016
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: SmartThings, Incorporated (Samsung Electronics Co. Ltd.)
• Inventors: Hagins, Jeffrey, Hawkinson, Alexander
• Primary Examiner(s): Lo, Kenneth M
• Assistant Examiner(s): CHANG, SUNRAY
• Application Number:
  US13/838,687
• Time in Patent Office: 1,383 Days
• US Class Current: 1/1
• CPC Class Codes: G05B 15/02 electric
• CPC Class Codes: G05B 19/042 using digital processors G05B19/05 takes precedence
• CPC Class Codes: G05B 19/0423 Input/output
• CPC Class Codes: G05B 2219/2642 Domotique, domestic, home control, automation, smart house
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/0226 Mapping or translating multiple network management protocols

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.

Claims

1. A method for providing automatic control of one or more devices in an environment, the method comprising:

assessing information for one or more devices being paired with a hub or with a central server, the one or more devices including a target device, the hub and the central server being configured to receive status messages from the devices and to issue commands to the devices;

determining device-type handlers to use with the one or more devices;

installing a device-type handler at the central server;

installing a device-type handler at the hub wherein the device-type handlers installed at the central server and the hub are arranged to process device-specific messages for the same target device;

installing an automation application on the central server, the automation application responding to an event and issuing a command in response to the event;

executing the automation application on the central server;

generating a normalized command for the target device at the central server;

generating, using the device-type handler installed at the central server, a device-specific command based on the normalized command; and

sending the device-specific command to the target device through the hub without using the device-type handler installed at the hub to generate the device-specific command.

2. The method of claim 1, 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.

3. The method of claim 2, 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.

4. The method of claim 2, 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.

5. The method of claim 1, wherein determining device-type handlers to use with the one or more devices comprises:

obtaining identifying information associated with one or more device paired with the hub or the central server; and

determining using the identifying information the device-type handlers to use with each of the one or more devices.

6. The method of claim 5, wherein the identifying information of a device comprises one or more of capabilities of the device, a manufacturer identification of the device, a product identification of the device, and an unique identifier for the device.

7. The method of claim 1, wherein installing the device-type handlers at the hub and the central server comprises:

determining a set of devices being paired with a hub;

determining a set of device-type handlers to use with the set of devices; and

installing the set of device-type handlers at the hub.

8. The method of claim 1, wherein installing the device-type handlers at the hub and the central server comprises:

determining a set of devices being paired with a hub;

determining a set of device-type handlers to use with the set of devices; and

installing a first device-type handler from the set of device-type handlers at the hub when an 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.

9. The method of claim 1, 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.

10. The method of claim 1, 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 central server wherein the execution of the automation application on the central server is in response to the normalized event message and wherein the normalized command generated at the central server is based on the normalized event message.

11. A central server arranged for use in a system for providing automatic control of one or more devices in an environment, the system including the central server and a hub paired with the one or more devices, the central server comprising:

a processor;

a memory coupled with the processor;

an automation application installed on the 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 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 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 normalized event message, the normalized event message received from a second event handler associated with a 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 central server to cause the automation application to issue a normalized command in response to the normalized event message;

use the first device-type handler installed at the central server, to generate a device-specific command based on the normalized command; and

send the device-specific command to the target device through the hub without requiring use of any device-type handler installed at the hub to generate the device-specific command.

12. The central server of claim 11, wherein the normalized event-specific 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:

store or process the normalized event message at the central server.

13. The central server of claim 11, 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.

14. The central server of claim 11, 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 hub;

determine a set of device-type handlers to use with the set of devices; and

install the set of device-type handlers at the hub.

15. The central server of claim 11, 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 hub;

determine a set of device-type handlers to use with the set of devices; and

install a second device-type handler from the set of device-type handlers 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.

16. The central server of claim 11 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.

17. The central server of claim 11 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.

18. The central server of claim 11 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.