IP Library Granted Patent US 12,372,933
Granted Patent B2
US 12,372,933 · App. 18/407,149 · Granted Jul 29, 2025

Communicating with and controlling load control systems

Inventors: John B. Nill (North Wales, PA); Matthew Bamberger (Quakertown, PA); Jason M. Swails (Nazareth, PA); Christopher M. Jones (Downingtown, PA)
Assignee: Lutron Technology Company LLC
G05B19/042H02J13/00007H04L12/2823H04L12/2825H04L67/025H04L67/12G05B2219/2639H02J2310/14Y02B70/30Y02B90/20Y04S20/20Y04S20/221Y04S20/242Y04S40/121
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,372,933
App. No.
18/407,149
Granted
Jul 29, 2025
Kind
B2
Abstract

Systems and methods are disclosed for communicating with and controlling load control systems of respective user environments from locations that are remote from the user environments.

Claims (77)

1. An electric load control network interface system, comprising:

a web server that includes web server controller circuitry configured to:

translate a hypertext transport protocol (HTTP) message received from a network device to create a first message queuing telemetry transport (MQTT) message;

wherein the HTTP message includes a media access control (MAC) address assigned to a respective system controller included in a plurality of system controllers; and

cause a publication of the first MQTT message;

wherein the first MQTT message includes a first topic and uses a unique identifier assigned to the respective system controller; and

cause a communication of the first MQTT message to message broker circuitry; and

a message broker that includes message broker controller circuitry configured to:

determine whether the respective system controller has subscribed to the first topic based on the unique identifier assigned to the respective system controller; and

publish the first MQTT message responsive to the determination that the respective system controller has subscribed to the first topic.

2. The system of claim 1 :

wherein the message broker controller circuitry to further:

extract a unique identifier assigned to a network device from a received second MQTT message;

wherein the second MQTT message includes data representative of the unique identifier and data representative of a second topic;

determine whether the network device assigned to the unique identifier has subscribed to the second topic; and

publish the second MQTT message responsive to the determination that the network device has subscribed to the second topic; and

wherein the web server controller circuitry to further:

translate the second MQTT message received from the message broker controller circuitry to create a second HTTP message that includes the second topic and data representative of a MAC address assigned to the network device; and

cause a communication of the second HTTP message to the network device.

3. The system of claim 2 wherein the web server further comprises:

a subscription data structure that includes data for each of the plurality of system controllers, wherein data for each system controller included in the plurality of system controllers includes:

a media access control (MAC) address associated with the respective system controller; and

the unique identifier associated with the respective system controller; and

wherein to translate the HTTP message received from the network device to create the first MQTT message, the web server controller circuitry to further:

retrieve from the subscription data structure the unique identifier that corresponds to the received MAC address assigned to the respective system controller.

4. The system of claim 3 wherein to translate the second MQTT message received from the message broker controller circuitry to create the second HTTP message, the web server controller circuitry to further:

retrieve from the subscription data structure, the MAC address that corresponds to the received unique identifier assigned to the network device.

5. The system of claim 1 wherein the message broker controller circuitry to further:

store the first MQTT message responsive to the determination that the system controller has subscribed to the first topic.

6. The system of claim 2 wherein the message broker controller circuitry to further:

store the second MQTT message responsive to the determination that the network device has subscribed to the second topic.

7. An electric load control network interface method, comprising:

translating, by controller circuitry, a hypertext transfer protocol (HTTP) message received from a network device to create a first message queuing telemetry transport (MQTT) message;

wherein the HTTP message includes a media access control (MAC) address assigned to a respective system controller included in a plurality of system controllers, the received HTTP message;

causing, by the web server controller circuitry, a publication of a first MQTT message;

wherein the first MQTT message includes a first topic and uses a unique identifier assigned to the respective system controller;

causing, by the controller circuitry, a communication of the first MQTT message to message broker circuitry;

causing, by the controller circuitry, the message broker circuitry to determine whether the respective system controller has subscribed to the first topic based on the unique identifier assigned to the respective system controller; and

causing, by the controller circuitry, the message broker circuitry to publish the first MQTT message responsive to the determination that the respective system controller has subscribed to the first topic.

8. The method of claim 7 , further comprising:

causing, by the controller circuitry, the message broker circuitry to extract a unique identifier assigned to a network device from a received second MQTT message;

wherein the second MQTT message includes data representative of the unique identifier and data representative of a second topic;

causing, by the controller circuitry, the message broker circuitry to determine whether the network device assigned to the unique identifier has subscribed to the second topic;

causing, by the controller circuitry, the message broker circuitry to publish the second MQTT message responsive to the determination that the respective network device has subscribed to the second topic;

translating, by the controller circuitry, the second MQTT message received from the message broker circuitry to create a second HTTP message that includes the second topic and data representative of a MAC address assigned to the network device; and

causing, by the controller circuitry, a communication of the second HTTP message to the network device.

9. The method of claim 8 wherein translating the HTTP message received from the network device to create the first MQTT message, further comprises:

retrieving by the controller circuitry, the unique identifier that corresponds to the received MAC address assigned to the respective system controller from a subscription data structure.

10. The method of claim 9 wherein translating the second MQTT message received from the message broker circuitry to create a second HTTP message, further comprises:

retrieving by the controller circuitry, the MAC address that corresponds to the received unique identifier assigned to the network device from the subscription data structure.

11. The method of claim 7 , further comprising:

causing, by the controller circuitry, the message broker circuitry to store the first MQTT message responsive to the determination that the system controller has subscribed to the first topic.

12. The method of claim 8 , further comprising:

causing, by the controller circuitry, the message broker circuitry to store the second MQTT message responsive to the determination that the network device has subscribed to the second topic.

13. A non-transitory, machine readable, storage device that includes instructions that, when executed by controller circuitry in an electric load control network interface system, causes the controller circuitry to:

translate an HTTP message received from a network device to create a first MQTT message;

wherein the HTTP message includes a media access control (MAC) address assigned to a respective system controller included in a plurality of system controllers;

cause a publication of the first MQTT message;

wherein the first MQTT message includes a first topic and uses a unique identifier assigned to the respective system controller;

cause a communication of the first MQTT message to message broker circuitry;

cause the message broker circuitry to determine whether the respective system controller has subscribed to the first topic based on the unique identifier assigned to the respective system controller; and

cause the message broker circuitry to publish the first MQTT message responsive to the determination that the respective system controller has subscribed to the first topic.

14. The non-transitory, machine readable, storage device of claim 13 wherein the instructions, when executed by the controller circuitry, further cause the controller circuitry to:

cause the message broker circuitry to extract a unique identifier assigned to a network device from a received second MQTT message;

wherein the second MQTT message includes data representative of the unique identifier and data representative of a second topic;

cause the message broker circuitry to determine whether the network device assigned to the unique identifier has subscribed to the second topic;

cause the message broker circuitry to publish the second MQTT message responsive to the determination that the network device has subscribed to the second topic;

translate the second MQTT message received from the message broker circuitry to create a second HTTP message that includes the second topic and data representative of a MAC address assigned to the network device; and

cause a communication of the second HTTP message to the network device.

15. The non-transitory, machine readable, storage device of claim 14 wherein the instructions that cause the controller circuitry to translate the HTTP message received from the network device to create the first MQTT message, further cause the controller circuitry to:

retrieve from a subscription data structure, the unique identifier that corresponds to the received MAC address assigned to the respective system controller.

16. The non-transitory, machine readable, storage device of claim 15 wherein the instructions that cause the controller circuitry to translate the second MQTT message received from the message broker circuitry to create the second HTTP message, further cause the controller circuitry to:

retrieve from the subscription data structure, the MAC address that corresponds to the received unique identifier assigned to the network device.

17. The non-transitory, machine readable, storage device of claim 13 wherein the instructions, when executed by the controller circuitry, further cause the controller circuitry to:

cause the message broker circuitry to store the first MQTT message responsive to the determination that the system controller has subscribed to the first topic.

18. The non-transitory, machine readable, storage device of claim 14 wherein the instructions, when executed by the controller circuitry, further cause the controller circuitry to:

cause the message broker circuitry to store the second MQTT message responsive to the determination that the network device has subscribed to the second topic.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 9, 2024
From: LUTRON ELECTRONICS CO., INC.
To: LUTRON TECHNOLOGY COMPANY LLC
Reel/Frame 067373/0302 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2024
From: NILL, JOHN B.; BAMBERGER, MATTHEW; SWAILS, JASON M.; JONES, CHRISTOPHER M.
To: LUTRON ELECTRONICS CO., INC.
Reel/Frame 066684/0375 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2024
From: LUTRON ELECTRONICS CO., INC.
To: LUTRON TECHNOLOGY COMPANY LLC
Reel/Frame 066764/0326 →
Continuity (7)
Continuation 17888250 · Aug 15, 2022
Continuation 16893060 · Jun 4, 2020
Continuation 15908322 · Feb 28, 2018
Provisional Application 62485212 · Apr 13, 2017
Provisional Application 62465433 · Mar 1, 2017
Provisional Application 62464834 · Feb 28, 2017
Related Publication 20240345557A1 · Oct 17, 2024
References Cited (68)
US 4667193A · Cotie et al. · 1987 [cited by applicant]
US 5544036A · Brown, Jr. et al. · 1996 [cited by applicant]
US 6119125A · Gloudeman et al. · 2000 [cited by applicant]
US 6640141B2 · Bennett · 2003 [cited by applicant]
US 7349682B1 · Bennett, III et al. · 2008 [cited by applicant]
US 7634322B2 · Samudrala et al. · 2009 [cited by applicant]
US 7873441B2 · Synesiou et al. · 2011 [cited by applicant]
US 8443071B2 · Lu et al. · 2013 [cited by applicant]
US 8532839B2 · Drees et al. · 2013 [cited by applicant]
US 8731724B2 · Drees et al. · 2014 [cited by applicant]
US 8788097B2 · Drees et al. · 2014 [cited by applicant]
US 8838282B1 · Ratliff et al. · 2014 [cited by applicant]
US 9553451B2 · Zacharchuk et al. · 2017 [cited by applicant]
US 9606520B2 · Noboa et al. · 2017 [cited by applicant]
US 9753455B2 · Drees · 2017 [cited by applicant]
US 9838736B2 · Smith et al. · 2017 [cited by applicant]
US 9839101B2 · Clymer et al. · 2017 [cited by applicant]
US 9851735B2 · Bard et al. · 2017 [cited by applicant]
US 10091017B2 · Landow et al. · 2018 [cited by applicant]
US 10098074B2 · Baker et al. · 2018 [cited by applicant]
US 10101717B2 · Marten et al. · 2018 [cited by applicant]
US 10129047B2 · Voddhi et al. · 2018 [cited by applicant]
US 10326658B2 · Chen et al. · 2019 [cited by applicant]
US 20020152298A1 · Kikta et al. · 2002 [cited by applicant]
US 20030040812A1 · Gonzales et al. · 2003 [cited by applicant]
US 20030040813A1 · Gonzales et al. · 2003 [cited by applicant]
US 20050154494A1 · Ahmed · 2005 [cited by examiner]
US 20060058923A1 · Kruk et al. · 2006 [cited by applicant]
US 20080040479A1 · Bridge · 2008 [cited by examiner]
US 20080172312A1 · Synesiou et al. · 2008 [cited by applicant]
US 20080234837A1 · Samudrala · 2008 [cited by examiner]
US 20090287805A1 · Hawkins · 2009 [cited by examiner]
US 20100238001A1 · Veskovic · 2010 [cited by applicant]
US 20120022700A1 · Drees et al. · 2012 [cited by applicant]
US 20120056712A1 · Knode · 2012 [cited by applicant]
US 20120091213A1 · Altonen et al. · 2012 [cited by applicant]
US 20120150359A1 · Westergaard · 2012 [cited by applicant]
US 20120221163A1 · Forbes, Jr. · 2012 [cited by applicant]
US 20130253723A1 · Oh et al. · 2013 [cited by applicant]
US 20140001846A1 · Mosebrook et al. · 2014 [cited by applicant]
US 20140070790A1 · Fujiwara et al. · 2014 [cited by applicant]
US 20140180486A1 · Newman, Jr. et al. · 2014 [cited by applicant]
US 20140244040A1 · Alberth, Jr. · 2014 [cited by examiner]
US 20140265863A1 · Gajurel · 2014 [cited by examiner]
US 20140277753A1 · Eiynk et al. · 2014 [cited by applicant]
US 20140309758A1 · Morrow · 2014 [cited by applicant]
US 20150015377A1 · Bull et al. · 2015 [cited by applicant]
US 20150094825A1 · Kinoshita et al. · 2015 [cited by applicant]
US 20150160628A1 · Kalafut et al. · 2015 [cited by applicant]
US 20150179058A1 · Crafts et al. · 2015 [cited by applicant]
US 20150180678A1 · Nadeau · 2015 [cited by applicant]
US 20160028780A1 · Verzano · 2016 [cited by examiner]
US 20160036896A1 · Spivey · 2016 [cited by applicant]
US 20160056629A1 · Baker · 2016 [cited by examiner]
US 20160127187A1 · Chen et al. · 2016 [cited by applicant]
US 20160225240A1 · Voddhi et al. · 2016 [cited by applicant]
US 20160320760A1 · Brun et al. · 2016 [cited by applicant]
US 20170090492A1 · Baker · 2017 [cited by examiner]
US 20170090499A1 · Dolan · 2017 [cited by applicant]
US 20170191695A1 · Bruhn et al. · 2017 [cited by applicant]
US 20170244792A1 · Yin et al. · 2017 [cited by applicant]
US 20170279630A1 · Anderson · 2017 [cited by examiner]
US 20170345277A1 · Kurniawan et al. · 2017 [cited by applicant]
US 20180196402A1 · Glaser et al. · 2018 [cited by applicant]
US 20180270063A1 · Bard · 2018 [cited by examiner]
US 20190190741A1 · Wendt · 2019 [cited by applicant]
WO 2016057548A1 · 2016 [cited by applicant]
WO 2016070628A1 · 2016 [cited by applicant]