Low-power device recovery using a backup firmware image
US-10394542-B1 · Aug 27, 2019 · US
US11209889B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11209889-B2 |
| Application number | US-202016794287-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 19, 2020 |
| Priority date | Aug 13, 2019 |
| Publication date | Dec 28, 2021 |
| Grant date | Dec 28, 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.
Status information including remaining battery power is collected from a management target device. Subsequent operations of the device are identified from an operation schedule management collection. Battery consumptions corresponding to subsequent operations of the device are estimated from KPI management collection that includes information representing relationships between battery consumptions and operations with respect to each of a plurality of devices. The battery life of the device is predicted based on the estimated battery consumptions and the remaining battery power represented by the collected status information. A circuit schedule of a maintenance engineer is determined based on the predicted battery life, the schedule including necessity of dispatch of the maintenance engineer to the device.
Opening claim text (preview).
What is claimed is: 1. An energy saving device management method for improving accuracy of a management target device, comprising: collecting, from the management target device, status information representing status that include remaining battery power of the device; identifying a subsequent operation of the management target device, from operation schedule management information that is information representing schedules of operations of each of a plurality of management target devices; estimating battery consumptions corresponding to subsequent operations of the device, from KPI management information that includes information representing relationships between battery consumptions and the operations with respect to each of the plurality of management target devices; predicting battery life of the management target device, based on the estimated battery consumptions and the remaining battery power represented by the collected status information; determining a circuit schedule of a maintenance engineer, based on the predicted battery life, the circuit schedule including necessity of dispatch of the maintenance engineer to the management target device; creating an operation plan for reducing a period during which the remaining battery power of the device are insufficient, using the operation schedule management information and the circuit schedule, and updating the operation schedule management information in conformity with the operation plan; providing the operation plan and the circuit schedule to a terminal of the maintenance engineer; causing a date and time of executing an operation having a relatively high risk among the subsequent operations of the device to be close to a maintenance engineer dispatch date represented by the circuit schedule, based on risk management information representing a degree of risk of each operation; determining whether or not there is an operation having an execution period to which the maintenance engineer dispatch date represented by the circuit schedule does not belong, based on operation requirement information representing the execution period of each operation; and when there is an operation having the execution period to which the maintenance engineer dispatch date does not belong, scheduling an execution date of the operation to be a last day in the execution period of the operation. 2. The energy saving device management method according to claim 1 , further comprising: determining whether or not there is an operation having an execution period to which a day before the maintenance engineer dispatch date represented by the circuit schedule belongs, based on the operation requirement information representing the execution period of each operation; and when there is an operation having the execution period to which the day before the maintenance engineer dispatch date belongs, scheduling the execution date of the operation to be the day before the maintenance engineer dispatch date. 3. The energy saving device management method according to claim 1 , further comprising determining achievability of the operation according to the remaining battery power and an operation type, and scheduling the operation on a day before the maintenance engineer dispatch date in a case where a sufficient battery power remains even after execution of the operation. 4. The energy saving device management method according to claim 1 , further comprising: determining achievability of the operation according to the remaining battery power and an operation type, and scheduling the operation immediately after battery replacement in a case where execution of the operation is to exhaust the remaining battery power. 5. The energy saving device management method according to claim 1 , further comprising updating KPI management information, based on a past operation history and a remaining battery power history of the device. 6. The energy saving device management method according to claim 1 , further comprising setting priorities of the operations of the device according to importance of an IoT solution, and determining the schedule on a priority basis from the operations having high priorities. 7. An energy saving device management system for improving accuracy of a device management server, comprising: the device management server capable of collecting, from a management target device, status information representing status including remaining battery power of the management target device, and of estimating battery consumptions corresponding to subsequent operations of the management target device, from KPI management information that represents relationships between battery consumptions and operations on each of a plurality of management target devices, and includes risk information; a model part that predicts battery life, based on the estimated battery consumptions and the remaining battery power represented by the collected status information; a maintenance manager that determines necessity of dispatch of a maintenance engineer to the device, and a circuit schedule, based on the predicted battery life; a device controller that identifies subsequent operations of the management target device, from the circuit schedule determined by the maintenance manager, and from operation schedule management information that is information representing schedules of operations of each of the plurality of management target devices; and an operation schedule management information that stores an operation plan created by the device controller using the risk information and the circuit schedule so as to reduce a period during which a state of the device is unknown due to the operation and updating the operation schedule management information in conformity with the operation plan, wherein the maintenance engineer is allowed to view the created operation plan and the circuit schedule, a date and time of executing an operation having a relatively high risk among the subsequent operations of the device is caused to be close to a maintenance engineer dispatch date represented by the circuit schedule, based on risk management information representing a degree of risk of each operation, determining whether or not there is an operation having an execution period to which the maintenance engineer dispatch date represented by the circuit schedule does not belong, based on operation requirement information representing the execution period of each operation, and when there is an operation having the execution period to which the maintenance engineer dispatch date does not belong, scheduling an execution date of the operation to be a last day in the execution period of the operation.
by task scheduling · CPC title
Monitoring battery levels, e.g. power saving mode being initiated when battery voltage goes below a certain level · CPC title
Power saving in peripheral device · CPC title
managing power supply demand, e.g. depending on battery level · CPC title
Monitoring task completion, e.g. by use of idle timers, stop commands or wait commands · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.