IP Library Granted Patent US 12,607,975
Granted Patent B2
US 12,607,975 · App. 18/379,561 · Granted Apr 21, 2026

Building management system with containerized engines

Inventors: Siva Naga Babu Kammela (Gunter, IN); Donald A Gottschalk, Jr. (Wauwatosa, WI); Daniel R Gottschalk (Racine, WI); Anand Bongale (Mumbai, IN); Pranay Joshi (Gurgaon, IN); Deepak Uppal (Pitampura, IN); Vivek V. Gupta (Menomonee Falls, WI); Peter J. Hazelberg (Dousman, WI)
Assignee: TYCO FIRE & SECURITY GMBH
G05B15/02
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,607,975
App. No.
18/379,561
Granted
Apr 21, 2026
Kind
B2
Abstract

The present disclosure relates to a building management system (BMS) comprising one or more field equipment controllers, and at least one containerized engine configured within a server to control the one or more field equipment controllers.

Claims (35)

1 . A building management system (BMS), comprising:

one or more field equipment controllers configured to communicate with one or more field equipment;

an engine creator configured to create at least one containerized engine configured within a server to control the one or more field equipment controllers; and

an intermediator configured to allow the at least one containerized engine to discover and associate with the one or more field equipment, wherein the at least one containerized engine is stored as a node in a device tree stored in a building model, wherein the building model is a digital representation and the device tree comprises additional nodes representing the one or more field equipment and the one or more field equipment controllers.

2 . The system of claim 1 , wherein the at least one containerized engine facilitates data transfer between the server and the one or more field equipment controllers.

3 . The system of claim 1 , wherein the at least one containerized engine controls one or more operational parameters of the one or more field equipment controllers.

4 . The system of claim 1 , the BMS comprises a user interface to allow a user to provide commands pertaining to:

creation of one or more additional containerized engines; or

deletion of the at least one containerized engine.

5 . The system of claim 1 , wherein the server is an on-premises server or an off-premises server.

6 . The system of claim 1 wherein the engine creator performs an audit to validate an action pertaining to the at least one containerized engine.

7 . The system of claim 1 , wherein the intermediator is configured to upload a configuration of the at least one containerized engine in a configuration archive.

8 . The system of claim 1 , wherein the at least one containerized engine is in a parent child relationship with the server.

9 . The system of claim 1 , wherein the building model further represents building points in the device tree.

10 . The system of claim 1 , wherein the at least one containerized engine facilitates data transfer between the server and the one or more field equipment controllers.

11 . A method comprising:

creating, by a server, at least one containerized engine;

associating, by the server, the at least one containerized engine with one or more field equipment controllers in response to an audit; and

controlling, by the server, the one or more field equipment controllers via the at least one containerized engine, wherein the at least one containerized engine is stored as a node in a device tree stored in a building model, wherein the building model is a digital representation and the device tree comprises additional nodes representing the one or more field equipment and the one or more field equipment controllers.

12 . The method of claim 11 , wherein the at least one containerized engine controls one or more operational parameters of the one or more field equipment controllers.

13 . The method of claim 11 , further comprising using a user interface to allow a user to provide commands pertaining to:

creation of one or more additional containerized engines; or

deletion of the at least one containerized engine.

14 . The method of claim 11 , wherein the server is an on-premises server or an off-premises server.

15 . The method of claim 11 , wherein an engine creator performs the audit to validate an action pertaining to the at least one containerized engine.

16 . The method of claim 11 , wherein an intermediator is configured to upload a configuration of the at least one containerized engine in a configuration archive.

17 . The method of claim 11 , wherein the at least one containerized engine is in a parent child relationship with the server.

18 . The method of claim 11 , wherein the device tree further comprises representations of building points.

19 . A processing circuit for a building management system (BMS) comprising one or more field equipment controllers in communication with one or more field equipment, the processing circuit comprising:

non-transitory memory; and

at least one processing component;

wherein the processing circuit is programed to provide:

an engine creator configured to create at least one containerized engine within a server, the engine creator being configured to control the one or more field equipment controllers; and

an intermediator configured to store the at least one containerized engine as a node in a device tree stored in a building model and to allow the at least one containerized engine to discover and associate with the one or more field equipment, wherein the building model is a digital representation and the device tree comprises additional nodes representing the one or more field equipment and the one or more field equipment controllers.

20 . The processing circuit of claim 19 , wherein the at least one containerized engine is in a parent child relationship with the server.

Assignments (2)
NUNC PRO TUNC ASSIGNMENT Recorded Jul 24, 2025
From: KAMMELA, SIVA NAGA BABU; GOTTSCHALK, DONALD A., JR.; GOTTSCHALK, DANIEL R.; BONGALE, ANAND; JOSHI, PRANAY; UPPAL, DEEPAK; GUPTA, VIVEK V.; HAZELBERG, PETER J.
To: JOHNSON CONTROLS TYCO IP HOLDINGS LLP
Reel/Frame 071823/0406 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 24, 2025
From: JOHNSON CONTROLS TYCO IP HOLDINGS LLP
To: TYCO FIRE & SECURITY GMBH
Reel/Frame 071823/0523 →
Priority Claims (3)
IN 202221058521 · Oct 13, 2022 · national
IN 202341008712 · Feb 10, 2023 · national
IN 202341040167 · Jun 13, 2023 · national
Continuity (2)
Continuation In Part 18375261 · Sep 29, 2023
Related Publication 20240126227A1 · Apr 18, 2024
References Cited (68)
US 7643891B2 · Rule et al. · 2010 [cited by applicant]
US 7835372B2 · Wang et al. · 2010 [cited by applicant]
US 10628135B2 · Sharma et al. · 2020 [cited by applicant]
US 10746428B2 · Przybylski et al. · 2020 [cited by applicant]
US 10831163B2 · Park · 2020 [cited by applicant]
US 10868857B2 · Park et al. · 2020 [cited by applicant]
US 10880107B2 · Gamroth et al. · 2020 [cited by applicant]
US 11050581B1 · Kavathekar · 2021 [cited by applicant]
US 11307538B2 · Park et al. · 2022 [cited by applicant]
US 11385605B2 · Wenzel et al. · 2022 [cited by applicant]
US 11625018B2 · Krishnan et al. · 2023 [cited by applicant]
US 12236254B1 · Gadalin et al. · 2025 [cited by applicant]
US 20020072391A1 · Itoh et al. · 2002 [cited by applicant]
US 20060274745A1 · Wang et al. · 2006 [cited by applicant]
US 20070016714A1 · Huotari et al. · 2007 [cited by applicant]
US 20090312853A1 · Kore et al. · 2009 [cited by applicant]
US 20110317548A1 · Pustylnik · 2011 [cited by applicant]
US 20130238144A1 · Shahapurkar · 2013 [cited by examiner]
US 20140207290A1 · Crawford et al. · 2014 [cited by applicant]
US 20140359524A1 · Sasaki et al. · 2014 [cited by applicant]
US 20160313749A1 · Frenz · 2016 [cited by applicant]
US 20160327296A1 · Leising et al. · 2016 [cited by applicant]
US 20170017247A1 · Fassier et al. · 2017 [cited by applicant]
US 20170353245A1 · Vardarajan · 2017 [cited by applicant]
US 20180232422A1 · Park et al. · 2018 [cited by applicant]
US 20180232423A1 · Park et al. · 2018 [cited by applicant]
US 20180232459A1 · Park et al. · 2018 [cited by applicant]
US 20180278434A1 · Maseng et al. · 2018 [cited by applicant]
US 20190102157A1 · Caldato et al. · 2019 [cited by applicant]
US 20190109907A1 · Duraisingh · 2019 [cited by applicant]
US 20190163215A1 · Cheng · 2019 [cited by examiner]
US 20190172165A1 · Verteletskyi et al. · 2019 [cited by applicant]
US 20190332683A1 · Thummala et al. · 2019 [cited by applicant]
US 20200050161A1 · Noboa · 2020 [cited by applicant]
US 20200133978A1 · Ramamurti et al. · 2020 [cited by applicant]
US 20200137185A1 · Parekh · 2020 [cited by applicant]
US 20200183660A1 · Lucas et al. · 2020 [cited by applicant]
US 20200228621A1 · Gamroth et al. · 2020 [cited by applicant]
US 20200233657A1 · Duraisingh et al. · 2020 [cited by applicant]
US 20200327371A1 · Sharma et al. · 2020 [cited by applicant]
US 20210191826A1 · Duraisingh et al. · 2021 [cited by applicant]
US 20210200807A1 · Ploegert et al. · 2021 [cited by applicant]
US 20210232369A1 · Sharma et al. · 2021 [cited by applicant]
US 20210282010A1 · Sugumar et al. · 2021 [cited by applicant]
US 20210326128A1 · Malladi et al. · 2021 [cited by applicant]
US 20210373509A1 · Borah et al. · 2021 [cited by applicant]
US 20210373510A1 · Borah et al. · 2021 [cited by applicant]
US 20210382449A1 · Krishnan · 2021 [cited by examiner]
US 20210382451A1 · Bharathi et al. · 2021 [cited by applicant]
US 20210382474A1 · Krishnan et al. · 2021 [cited by applicant]
US 20220018567A1 · Ock · 2022 [cited by examiner]
US 20220092500A1 · Drees et al. · 2022 [cited by applicant]
US 20220137936A1 · Lucas et al. · 2022 [cited by applicant]
US 20220191271A1 · Po · 2022 [cited by applicant]
US 20220377132A1 · Gupta et al. · 2022 [cited by applicant]
US 20230013555A1 · Kuckuk et al. · 2023 [cited by applicant]
US 20230041845A1 · Tsirkin et al. · 2023 [cited by applicant]
US 20230195485A1 · Nagasundaram et al. · 2023 [cited by applicant]
US 20230325303A1 · Jebbar et al. · 2023 [cited by applicant]
US 20230367559A1 · Sharma et al. · 2023 [cited by applicant]
US 20230418248A1 · Ozadowicz et al. · 2023 [cited by applicant]
CA 3108929C · 2021 [cited by applicant]
CA 3154167A1 · 2021 [cited by applicant]
WO WO2022171730A1 · 2022 [cited by applicant]
U.S. Appl. No. 18/215,990, filed Jun. 29, 2023. [cited by applicant]
Legrand, “Wattstopper—Wireless BACnet MS/TP Bridge,” Catalog No. WBT900, No. 25174—Feb. 2017 rev. 1 (4 pages). [cited by applicant]
Luo et al., “Towards a Wireless Building Management System Requiring no Change to Upper-layer Protocols,” The Hong Kong Polytechnic University, Harbin Institute of Technology, Building Integration Perfection Ltd., Nanch… [cited by applicant]
Press Release, “The new W-BACnet from Lumen Radio—an unparalleled wireless BACnet solution driving cost—and time savings for building automation,” https://lumenradio.com/stories/the-new-w-bacnet-from-lumenradio-an-unpar… [cited by applicant]