Broadcast remote firmware update
AssigneeMueller International, LLC
InventorsDale McLeod Magley, David Edwin Splitz, Gregory Caron, Brent Dukes
Life of this patent
Estimating the term…
Abstract
A method of broadcasting firmware updating messages in a communication system includes the steps of receiving a broadcast remote firmware update (BRFU) setup message from an upstream source, the BRFU setup message specifying a number of transmissions of a broadcast of a firmware file; broadcasting setup information from the BRFU setup message on a first channel to downstream devices, the setup information specifying at least one other channel to which each downstream device should listen to receive a copy of the firmware file; and repeatedly broadcasting the firmware file to the downstream devices in accordance with the BRFU setup message.
Claims23
A method of managing firmware update communications between devices in a communication system, comprising the steps of:
- retrieving, at an upstream source, a copy of a firmware file from a file storage source, wherein the upstream source is selected from one of a server and a network management tool;
- sending the copy of the firmware file from the upstream source to at least one transmitting device selected from a hub, a collector, and a repeater;
- receiving input of a predetermined number of times that the copy of the firmware file is to be repeatedly broadcasted by the at least one transmitting device to comprise one broadcast remote firmware update (BRFU);
- receiving input of a predefined limit of BRFUs to be executed within a session;
- sending a BRFU setup message from the upstream source to the at least one transmitting device, the BRFU setup message specifying a wake time at which downstream devices targeted by the BRFU setup message should wake from a sleeping state to receive the copy of the firmware file, such devices comprising targeted downstream devices, and specifying a channel to which each targeted downstream device should tune after waking;
- following completion of a BRFU, quantifying a number of unsuccessful downstream devices, the unsuccessful downstream devices comprising targeted downstream devices that did not successfully store an entire copy of the firmware file;
- determining whether the number of unsuccessful downstream devices falls below a predetermined threshold;
- responsive to a determination that the number of unsuccessful downstream devices falls below the predetermined threshold, conducting a directed firmware update addressed to each unsuccessful downstream device, comprising the steps of
- sending a direct setup message directly from the upstream source over a hailing channel to each unsuccessful downstream device, the direct setup message specifying a next wake time at which each unsuccessful downstream device should wake to again receive the copy of the firmware file and specifying a data channel to which each unsuccessful downstream device should tune after waking at the next wake time, and
- causing the at least one transmitting device to perform one of broadcasting the copy of the firmware file to each unsuccessful downstream device and sending the copy of the firmware file over the data channel to each unsuccessful downstream device;
- responsive to a determination that the number of unsuccessful downstream devices does not fall below the predetermined threshold, determining whether the predefined limit of BRFUs has been reached;
- responsive to a determination that the predefined limit of BRFUs has not been reached, initiating another BRFU by sending another BRFU setup message to the at least one transmitting device;
- and
- responsive to a determination that the predefined limit of BRFUs has been reached,
- sending a broadcast burn command to the at least one transmitting device, and
- receiving firmware information from the transmitting device, the firmware information identifying all targeted downstream devices that burned the firmware file into respective memories located in the targeted downstream devices, such downstream devices comprising successful downstream devices, and specifying a version of firmware running on the successful downstream devices.
A method of broadcasting firmware updating messages in a communication system, comprising the steps of:
- receiving a broadcast remote firmware update (BRFU) setup message from an upstream source;
- broadcasting, by a transmitting device, the BRFU setup message on a first channel to downstream devices targeted by the BRFU setup message, such devices comprising targeted downstream devices, the BRFU setup message specifying at least one other channel to which each targeted downstream device should listen to receive a copy of a firmware file;
- and
- repeatedly broadcasting the firmware file for a predetermined number of times to the targeted downstream devices in accordance with the BRFU setup message, wherein repeated broadcasting of the firmware file for the predetermined number of times comprises one BRFU, and wherein the BRFU setup message further specifies a predefined limit of BRFUs to be executed within a session;
- repeating the steps of receiving a BRFU setup message, broadcasting the BRFU setup message, and repeatedly broadcasting the firmware file for the predetermined number of times until the earlier of a determination that a quantified number of unsuccessful targeted downstream devices that did not receive a complete copy of the firmware file falls below a predetermined threshold, and a determination that the predefined limit of BRFUs has been reached;
- and
- responsive to the determination that the predefined limit of BRFUs has been reached,
- receiving a broadcast burn command from the upstream source,
- responsive to the broadcast burn command, sending a burn command to all targeted downstream devices,
- receiving firmware information from each targeted downstream device that successfully burned a copy of the firmware file into an internal memory, each such targeted downstream device comprising a successful downstream device, the firmware information identifying each successful downstream device and specifying a version of firmware running on each successful downstream device, and
- sending the firmware information received from each successful downstream device to the upstream source.
Dependencies are inferred from the claim text.