US RE50,100 E1
Device-type handlers for remote control and monitoring of devices through a data network
Jeffrey Hagins, Santa Rosa, CA (US); and Alexander Hawkinson, Great Falls, VA (US)
Assigned to SAMSUNG ELECTRONICS CO., LTD., Suwon-si (KR)
Filed by SAMSUNG ELECTRONICS CO., LTD., Suwon-si (KR)
Filed on Apr. 3, 2020, as Appl. No. 16/839,822.
Application 16/839,822 is a continuation of application No. 13/838,687, filed on Mar. 15, 2013, granted, now 9,529,344, issued on Dec. 27, 2016.
Application 16/839,822 is a reissue of application No. 15/357,433, filed on Nov. 21, 2016, granted, now 10,386,807, issued on Aug. 20, 2019.
Int. Cl. G05B 19/00 (2006.01); G05B 15/02 (2006.01); G05B 19/042 (2006.01); H04L 12/24 (2006.01); H04L 41/00 (2022.01)
CPC G05B 19/042 (2013.01) [G05B 15/02 (2013.01); G05B 19/0423 (2013.01); H04L 41/00 (2013.01); G05B 2219/2642 (2013.01)] 15 Claims
OG exemplary drawing
 
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 comprising [ central 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] .