Controller arrangement, method and computer program
US-2017142623-A1 · May 18, 2017 · US
US11050651B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11050651-B2 |
| Application number | US-201815862258-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 4, 2018 |
| Priority date | Jan 4, 2018 |
| Publication date | Jun 29, 2021 |
| Grant date | Jun 29, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for health monitoring and upgrade of a distributed controller are provided. According to one embodiment of the disclosure, a method for health monitoring and upgrade of a distributed controller may commence with receiving, by a lower level controller from a high-level controller, high-level control references. The method may further include generating low-level control references for a hardware asset based at least in part on the high-level control references. The method may include monitoring the network connection and detecting an error in the network connection. In response to the detection of the error in the network connection, a control of the hardware asset may be transferred to the low-level controller. The method may further include determining that the network connection has been restored. In response to the determination that the network connection has been restored, the control of the hardware asset may be transferred to the high-level controller.
Opening claim text (preview).
What is claimed is: 1. A system comprising: a high-level controller; a low-level controller in communication with the high-level controller via a network through a network connection, the low-level controller being configured to: receive high-level control references from the high-level controller via the network connection; generate low-level control references for a hardware asset based at least in part on the high-level control references; facilitate control of the hardware asset in response to an error in the network connection; and receive a series of heartbeat signals, wherein the error in the network connection is based at least in part on receipt of the series of heartbeat signals; a prioritization module, the prioritization module being configured to: prioritize one or more communications between the high-level controller and the low-level controller based at least in part on relative priorities of the one or more communications; and allocate a network bandwidth among the one or more communications based on the prioritization of the one or more communications; a counter communicated between the high-level controller and the low-level controller, the counter representing a number in the series of heartbeat signals; and a health monitoring module configured to: monitor the network connection; detect the error in the network connection; in response to the detection of the error in the network connection, transfer a control of the hardware asset to the low-level controller; determine time between the series of heartbeat signals; determine that the network connection has been restored; and in response to the determination that the network connection has been restored, transfer the control of the hardware asset to the high-level controller. 2. The system of claim 1 , further comprising an installation module configured to: interrupt communications in the network connection to temporarily transfer the control of the hardware asset to the low-level controller; install software on the high-level controller while the low-level controller is in control of the hardware asset; and restore the network connection, thereby causing a transfer of the control of the hardware asset back to the high-level controller. 3. The system of claim 1 , wherein the health monitoring module is configured to monitor the network connection by periodically sending at least one signal between the high-level controller and the low-level controller, wherein a lack of acknowledgment of receipt of the at least one signal is indicative of the error in the network connection. 4. The system of claim 1 , wherein the low-level controller is configured to operate in a fail-safe self-contained loop mode during a loss of communications. 5. The system of claim 1 , wherein the hardware asset includes a power generating asset. 6. The system of claim 1 , wherein the low-level controller is configured to control the hardware asset by providing the low-level control references to sensors and actuators associated with the hardware asset. 7. The system of claim 1 , wherein the prioritization module is further configured to: prioritize one or more applications associated with the high-level controller and the low-level controller based on respective relative priorities of the one or more applications; and allocate a central processing unit (CPU) clock time among the one or more applications based on the prioritization of the one or more applications. 8. The system of claim 7 , wherein the prioritization module is configured to allocate the CPU clock time for the one or more applications by defining a maximum execution duration for each allocated unit based on the relative priorities of the one or more applications. 9. The system of claim 1 , wherein the prioritization module is configured to allocate the network bandwidth for the one or more communications by defining a maximum bandwidth segment for each allocated unit based on the relative priorities of the one or more communications. 10. The system of claim 1 , wherein the health monitoring module is configured to transfer the control of the hardware asset by switching the control between the low-level controller and the high-level controller. 11. A method comprising: receiving, via a network connection, by a low-level controller from a high-level controller, high-level control references; generating, by the low-level controller, low-level control references for a hardware asset based at least in part on the high-level control references; receiving, by the low-level controller, a series of heartbeat signals; monitoring, by a health monitoring module, the network connection; prioritizing one or more communications between the high-level controller and the low-level controller based at least in part on relative priorities of the one or more communications; and allocating a network bandwidth among the one or more communications based on the prioritization of the one or more communications; communicating a counter between the high-level controller and the low-level controller, the counter representing a number in a series of heartbeat signals; detecting, by the health monitoring module, an error in the network connection, wherein the error in the network connection is based at least in part on receipt of the series of heartbeat signals; in response to the detection of the error in the network connection, transferring, by the health monitoring module, a control of the hardware asset to the low-level controller; determining, by the health monitoring module, that the network connection has been restored; and in response to the determination that the network connection has been restored, transferring, by the health monitoring module, the control of the hardware asset to the high-level controller. 12. The method of claim 11 , wherein the monitoring the network connection includes periodically sending, by the health monitoring module, at least one signal between the high-level controller and the low-level controller, wherein a lack of acknowledgment of receipt of the at least one signal is indicative of the error in the network connection. 13. The method of claim 11 , further comprising: forcing, by an installation module, the error in the network connection to temporarily transfer the control of the hardware asset to the low-level controller; installing, by the installation module, software on the high-level controller while the low-level controller is in control of the hardware asset; and restoring, by an installation module, the network connection, thereby causing a transfer of the control of the hardware asset back to the high-level controller. 14. The method of claim 11 , further comprising: prioritizing, by the prioritization module, one or more applications associated with the high-level controller and the low-level controller based on relative priorities of the one or more applications; and allocating, by the prioritization module, a central processing unit (CPU) clock time among the one or more applications based on the prioritization of the one or more applications. 15. The method of claim 14 , wherein the prioritizing of the one or more applications includes allocating, by the prioritization module, the CPU clock time for the one or more applications by defining a maximum execution duration for each allocated unit based on the relative priorities of the one or more applications. 16. The method of claim 11 , wherein the prioritizing of the one or more communications includes allocating, by the prioritization module, the network bandwidth
Active monitoring, e.g. heartbeat, ping or trace-route · CPC title
Errors, e.g. transmission errors · CPC title
comprising hierarchical management structures · CPC title
Switching into safety or degraded mode, e.g. protection and supervision after failure · CPC title
using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.