IP Library › Granted Patent US 12,327,149
Granted Patent B2
US 12,327,149 · App. 17/346,809 · Granted Jun 10, 2025

Edge controller for a facility

Inventors: Joseph Majewski (Huntington, NY); Ivan Rares (Charlotte, NC); Daniel Giorgis (Glen Allen, VA); Robin Wilderson (Charlotte, NC); Rod Stein (Edmonton, CA); Robert E. Flasher (Charlotte, NC); Srinivasa Rangan (Charlotte, NC); Raymond A. Richards (Charlotte, NC); Amod Kamat (Charlotte, NC); Upender Paravastu (Bangalore, IN)
Assignee: HONEYWELL INTERNATIONAL INC.
G06F9/54G06F9/45558G06F9/5072G06F9/541H04L12/2823H04W84/02G06F2009/45562G06F2009/4557G06F2009/45575G06F2009/45595
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,327,149
App. No.
17/346,809
Granted
Jun 10, 2025
Kind
B2
Abstract

An edge controller may be used for obtaining device data from one or more local devices at a local facility and to provide a representation of at least some of the device data to a remote server. The edge controller may include a network communication port, a cellular communication port and a device communication port. A controller is operatively coupled to the network communication port, the cellular communication port and the device communication port and is configured to receive configuration information and to install the received configuration information on the edge controller. The installed configuration information configures the controller to obtain the device data from the one or more local devices and to send a representation of at least some of the device data to the remote server.

Claims (48)

1. An edge controller for providing an interface between a plurality of physical assets of a facility and a cloud server, the edge controller comprising:

one or more communication ports for communicating with a plurality of physical assets in the facility and the cloud server;

a controller operatively coupled to the one or more communication ports, the controller configured to:

receive first telemetry data and/or first metadata from a first asset of the plurality of physical assets of the facility via the one or more communication ports;

transform the first received telemetry data and/or first metadata, into transformed data, the transformed data having a unified data format in accordance with a common object model;

send at least a portion of the transformed data to the cloud server based on one or more process parameters required by the cloud server for one or more operations; and

determine, based on data-processing of the portion of the transformed data, a second asset of the plurality of assets from which second telemetry data and/or second metadata is to be received at the edge controller in a subsequent data transaction;

receiving a configuration information for the second asset from the cloud server based at least on the data-processing of the portion of the transformed data; and

controlling an operation of the second asset based on the configuration information.

2. The edge controller of claim 1 , wherein the controller is configured to receive first telemetry data from one or more of the plurality of physical assets, wherein the first telemetry data comprises time-series data including a plurality of data values collected over time.

3. The edge controller of claim 1 , wherein transforming the first received telemetry data and/or first metadata comprises one or more of:

normalizing at least some of the received first telemetry data and/or first metadata;

transforming at least some of the received first telemetry data and/or first metadata from a first format into a second format that supports the common object model; and

aggregating at least some of the received first telemetry data and/or first metadata from one or more of the plurality of physical assets.

4. The edge controller of claim 3 , wherein normalizing at least some of the received first telemetry data and/or first metadata comprises normalizing at least some of the received first telemetry data and/or first metadata based on a common unit of measure.

5. The edge controller of claim 3 , wherein aggregating at least some of the received first telemetry data and/or first metadata comprises averaging at least some of the received first telemetry data and/or metadata.

6. The edge controller of claim 1 , wherein the controller is configured to:

determine based on data processing using the common object model, one of a portion of the second telemetry data and/or the second metadata that is available from the plurality of physical assets is to be received by the edge controller; and/or

determine one of the portion of the transformed data that is to be sent to the cloud server.

7. The edge controller of claim 1 , wherein the common object model is compatible with one or more data analytics application or service supported by the cloud server.

8. The edge controller of claim 1 , wherein the first metadata, when received, comprises ancillary or contextual information associated with the corresponding physical asset.

9. The edge controller of claim 8 , wherein the first metadata comprises one or more of:

a geographical location of the corresponding physical asset within the facility;

a configuration setting of the corresponding physical asset;

a data type and/or data format associated data provided by the corresponding physical asset; and

a relationship between the corresponding physical asset and one or more other physical assets in the facility.

10. The edge controller of claim 1 , wherein the controller is further configured to discover and identify at least some of the plurality of physical assets communicatively coupled to the edge controller.

11. The edge controller of claim 1 , wherein the controller is configured to:

receive first telemetry data and/or first metadata from each of two or more of the plurality of physical assets in a format or data structure that is in accordance with a communication protocol between the edge controller and the corresponding physical asset.

12. The edge controller of claim 1 , wherein the controller executes one or more containerized packages that are configured based on configuration information from the cloud server, wherein the one or more containerized packages:

determine the set of assets from amongst the plurality of assets from which the first telemetry data and/or the first metadata is to be received at the edge controller in the subsequent data transaction;

determine which and/or when first telemetry data and/or first metadata that is available from the plurality of physical assets is received by the edge controller;

determine how the received first telemetry data and/or first metadata is transformed into transformed data having the unified data format in accordance with the common object model; and/or

determine which of the transformed data is sent to the cloud server.

13. A non-transitory computer readable medium storing instructions thereon that when executed by one or more processors, cause the one or more processors to:

receive first telemetry data and/or first metadata from a first asset of a plurality of physical assets;

transform the received first telemetry data and/or first metadata into transformed data, the transformed data having a unified data format in accordance with a common object model;

send at least a portion of the transformed data to a cloud server based on one or more process parameters required by the cloud server for one or more operations; and

determine, based on data-processing of the portion of the transformed data, a second asset of the plurality of assets, from which second telemetry data and/or the second metadata is to be received at the edge controller in a subsequent data transaction;

receive a configuration information for the second asset from the cloud server based at least on the data-processing of the portion of the transformed data; and

control an operation of the second asset based on the configuration information.

14. The non-transitory computer readable medium of claim 13 , wherein the instructions cause the one or more processors to transform the received telemetry data and/or metadata by one or more of:

normalizing at least some of the received first telemetry data and/or first metadata;

transforming at least some of the received first telemetry data and/or first metadata from a first format into a second format that supports the common object model; and

aggregating at least some of the received first telemetry data and/or first metadata from one or more of the plurality of physical assets.

15. The non-transitory computer readable medium of claim 13 , wherein the instructions cause the one or more processors to:

determine based on data-processing using the common object model, one of a portion of the second telemetry data and/or the second metadata that is available from the plurality of physical assets is to be received; and/or

determine the portion of the transformed data that is to be sent to the cloud server.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 13, 2023
From: MAJEWSKI, JOSEPH; RARES, IVAN; GIORGIS, DANIEL; WILDERSON, ROBIN; STEIN, ROD; FLASHER, ROBERT E.; RANGAN, SRINIVASA; RICHARDS, RAYMOND A.; KAMAT, AMOD; PARAVASTU, UPENDER
To: HONEYWELL INTERNATIONAL INC.
Reel/Frame 063070/0819 →
Continuity (3)
Provisional Application 63143633 · Jan 29, 2021
Provisional Application 63039300 · Jun 15, 2020
Related Publication 20210389968A1 · Dec 16, 2021
References Cited (85)
US 5249270A · Stewart et al. · 1993 [cited by applicant]
US 5297257A · Struger et al. · 1994 [cited by applicant]
US 5398336A · Tantry et al. · 1995 [cited by applicant]
US 5550980A · Pascucci et al. · 1996 [cited by applicant]
US 5598566A · Pascucci et al. · 1997 [cited by applicant]
US 5718767A · Crum et al. · 1998 [cited by applicant]
US 5805442A · Crater et al. · 1998 [cited by applicant]
US 5862052A · Nixon et al. · 1999 [cited by applicant]
US 6047222A · Burns et al. · 2000 [cited by applicant]
US 6067477A · Wewalaarachchi et al. · 2000 [cited by applicant]
US 6119125A · Gloudeman et al. · 2000 [cited by applicant]
US 6157943A · Meyer · 2000 [cited by applicant]
US 6189109B1 · Sheikh et al. · 2001 [cited by applicant]
US 6370448B1 · Eryurek · 2002 [cited by applicant]
US 6832120B1 · Frank et al. · 2004 [cited by applicant]
US 7240106B2 · Cochran et al. · 2007 [cited by applicant]
US 7424701B2 · Kendall et al. · 2008 [cited by applicant]
US 8046320B2 · De · 2011 [cited by applicant]
US 8145333B2 · Vrba et al. · 2012 [cited by applicant]
US 8290627B2 · Richards et al. · 2012 [cited by applicant]
US 8515736B1 · Duta · 2013 [cited by applicant]
US 8595245B2 · Cavestro et al. · 2013 [cited by applicant]
US 9020879B2 · Mcclung et al. · 2015 [cited by applicant]
US 9081847B2 · Casella Dos Santos et al. · 2015 [cited by applicant]
US 9128472B2 · Lawson et al. · 2015 [cited by applicant]
US 9239872B2 · Casella Dos Santos et al. · 2016 [cited by applicant]
US 9253054B2 · Maturana et al. · 2016 [cited by applicant]
US 9363336B2 · Lawson et al. · 2016 [cited by applicant]
US 9413852B2 · Lawson et al. · 2016 [cited by applicant]
US 9477936B2 · Lawson et al. · 2016 [cited by applicant]
US 9535411B2 · Wei et al. · 2017 [cited by applicant]
US 9565275B2 · Awson et al. · 2017 [cited by applicant]
US 9568908B2 · Lawson et al. · 2017 [cited by applicant]
US 9568909B2 · Lawson et al. · 2017 [cited by applicant]
US 9965562B2 · Lawson et al. · 2018 [cited by applicant]
US 10095207B2 · Ji et al. · 2018 [cited by applicant]
US 10116532B2 · Lawson et al. · 2018 [cited by applicant]
US 10139811B2 · Lawson et al. · 2018 [cited by applicant]
US 10401810B2 · Guthrie et al. · 2019 [cited by applicant]
US 10443357B2 · Weatherhead et al. · 2019 [cited by applicant]
US 10643136B2 · Sublett · 2020 [cited by applicant]
US 20020194223A1 · Meyers et al. · 2002 [cited by applicant]
US 20060020465A1 · Cousineau et al. · 2006 [cited by applicant]
US 20110035352A1 · Hale et al. · 2011 [cited by applicant]
US 20110118896A1 · Holloway · 2011 [cited by applicant]
US 20110246530A1 · Malafsky · 2011 [cited by applicant]
US 20110295790A1 · Zillner · 2011 [cited by applicant]
US 20120194502A1 · Smith et al. · 2012 [cited by applicant]
US 20130104244A1 · Qu et al. · 2013 [cited by applicant]
US 20130211870A1 · Lawson et al. · 2013 [cited by applicant]
US 20130212214A1 · Lawson et al. · 2013 [cited by applicant]
US 20130275448A1 · Mirhaji · 2013 [cited by applicant]
US 20140012950A1 · Doucette et al. · 2014 [cited by applicant]
US 20140032555A1 · Kiff et al. · 2014 [cited by applicant]
US 20140375431A1 · Cristache · 2014 [cited by applicant]
US 20170223110A1 · Lawson et al. · 2017 [cited by applicant]
US 20180309818A1 · Park et al. · 2018 [cited by applicant]
US 20180356800A1 · Chao et al. · 2018 [cited by applicant]
US 20190014180A1 · Lawson et al. · 2019 [cited by applicant]
US 20190094827A1 · Park et al. · 2019 [cited by applicant]
US 20190369984A1 · Malladi et al. · 2019 [cited by applicant]
US 20200003028A1 · Weatherhead et al. · 2020 [cited by applicant]
US 20200175105A1 · Falk et al. · 2020 [cited by applicant]
CA 2900767A1 · 2014 [cited by applicant]
CN 103679304A · 2014 [cited by applicant]
CN 104969133A · 2015 [cited by applicant]
EP 2660667A2 · 2013 [cited by applicant]
EP 2801935A1 · 2014 [cited by applicant]
EP 2954377A1 · 2015 [cited by applicant]
EP 3070548A2 · 2016 [cited by applicant]
JP 2017103981A · 2017 [cited by applicant]
JP 2018534651A · 2018 [cited by applicant]
MX 343533B · 2016 [cited by applicant]
WO 2013133967A1 · 2013 [cited by applicant]
WO 2014124353A1 · 2014 [cited by applicant]
WO 2016050257A1 · 2016 [cited by applicant]
WO 2017213771A1 · 2017 [cited by applicant]
WO 2018234741A1 · 2018 [cited by applicant]
WO 2020097221A1 · 2020 [cited by applicant]
Yang et al., “Big Data Driven Edge-Cloud Collaboration Architecture for Cloud Manufacturing: A Software Defined Perspective”, Feb. 7, 2020, IEEE Access, vol. 8, 2020. (Year: 2020). [cited by examiner]
Zhang et al; “An OWL/SWRL based diagnosis approach in a pervasive middleware”, 20th International Conference on Software Engineering and Knowledge Engineering; 2008, 6 pages. (Year: 2008). [cited by applicant]
“Pelion: a Flexible, Secure and Efficient IoT Platform—Arm®—Arm,” 13 pages, https://www.arm.com/products/iot/pelion-iot-platform accessed Jun. 15, 2020. [cited by applicant]
Byron et al; http://ww.coative.com/pages.wp9605lu.html, “A Technology Roadmap for Enterprise Connectivity to Control Networks”, Coactive White Papers, Nov. 5, 1998, pp. 1-13. [cited by applicant]
International Search Repost and Written Opinion dated Aug. 27, 2021 for International Application No. PCT/US2021/037213. [cited by applicant]
JP Final Decision of Rejection, JP Patent Application No. 2022-576365, Japanese Patent Office, Jun. 27, 2024 (3 pages) (English translation). [cited by applicant]