US6640334B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method and apparatus of remotely updating firmware of a communication device
Assignee: RPX Clearinghouse LLC
•
Filing: 1999-09-27
•
Granted: 2003-10-28
•
Expires: 2019-09-27
Abstract
Abstract A method and apparatus for remotely updating firmware saved in a FLASH memory of a communication device connected to a network is presented. The FLASH memory is partitioned into at least a first and a second portion. A first firmware load is stored in the first portion. During run-time of the first firmware load, at least a portion of an updated firmware load is transmitted through the network to the communication device. The transmitted portion of the updated firmware load is temporarily stored in a buffer of the communication device. At least a portion of the first firmware load is copied into a random access memory (RAM) of the communication device. Execution, from the RAM, of the copied portion of the first firmware load is triggered. Under control of the copied portion of the first firmware load, the transmitted portion of the updated firmware load is saved to the second portion of the FLASH memory.
Inventors
- 👤 John H. Rasmussen
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-02 22:39
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/44; G06F9/4401; G06F8/00; G06F8/60; G06F8/65
Claims Analysis
Total Claims: 49
Claim 1
Independent Claim
176 words
A method of remotely updating firmware saved in a FLASH memory of a communication device connected to a network, the method comprising steps of: a) providing a boot page of the FLASH memory for storing a first firmware load; b) providing a pair of update pages of the FLASH memory, each update page being adapted to store a respective firmware load; c) designating one of the update pages as an active update page, and the other one of the update pages as an active update page; d) transmitting an updated firmware load through the network to the communication device; e) storing, under control of the first firmware load, the updated firmware load in the inactive update page of the FLASH memory; and f) rebooting the communication device under control of the first firmware load, including steps of: i) dynamically identifying, from among the firmware loads stored in the FLASH memory, a most recently stored valid firmware load; and ii) continuing operation of the communication device under control of the identified most recently stored valid firmware load.
Claim 2
Independent Claim
176 words
A method of remotely updating firmware saved in a FLASH memory of a communication device connected to a network, the method comprising steps of: a) providing a boot page of the FLASH memory for storing a first firmware load; b) providing a pair of update pages of the FLASH memory, each update page being adapted to store a respective firmware load; c) designating one of the update pages as an active update page, and the other one of the update pages as an active update page; d) transmitting an updated firmware load through the network to the communication device; e) storing, under control of the first firmware load, the updated firmware load in the inactive update page of the FLASH memory; and f) rebooting the communication device under control of the first firmware load, including steps of: i) dynamically identifying, from among the firmware loads stored in the FLASH memory, a most recently stored valid firmware load; and ii) continuing operation of the communication device under control of the identified most recently stored valid firmware load.
Claim 3
Dependent Claim
40 words
A method as claimed in claim 1 , wherein an entire updated firmware load is transmitted in a single download operation using a data channel of the communication device, and temporarily stored in an upstream buffer of the communication device.
Claim 4
Independent Claim
28 words
A method as claimed in claimed 2 , further comprising a step of placing the communication device into a loop-back mode prior to transmitting the updated firmware load.
Claim 5
Dependent Claim
26 words
A method as claimed in claim 1 , further comprising a step of preliminarily dividing the updated firmware load into a plurality of predetermined load portions.
Claim 6
Dependent Claim
27 words
A method as claimed in claim 4 , wherein each load portion is transmitted in a respective download operation using a message channel of the communication device.
Claim 7
Dependent Claim
27 words
A method as claimed in claim 5 , wherein in each download operation comprises transmitting a DnldData command including an address and the load portion as arguments.
Claim 8
Dependent Claim
38 words
A method as claimed in claim 6 , further comprising a step of saving the load portion in the FLASH memory starting at an address of the FLASH memory corresponding to the address included in the DnldData command.
Claim 9
Dependent Claim
28 words
A method as claimed in claim 4 , further comprising a step of determining whether or not the load portion has been correctly saved in the FLASH memory.
Claim 10
Dependent Claim
51 words
A method as claimed in claim 8 , wherein when the load portion has been correctly saved in the FLASH memory, transmitting another load portion to the communication device, and when the load portion has not been correctly saved in the FLASH memory, re-transmitting the load portion to the communication device.
Claim 11
Dependent Claim
23 words
A method as claimed in claim 4 , further comprising monitoring a download status of the updated firmware load to the communication device.
Claim 12
Dependent Claim
48 words
A method as claimed in claim 10 , wherein monitoring the download status comprises maintaining a database including a sequence number of a load portion correctly saved in the FLASH memory and incrementing the sequence number as each successive load portion is correctly saved in the FLASH memory.
Claim 13
Dependent Claim
44 words
A method as claimed in claim 1 , wherein the step of saving the updated firmware load in the inactive update page comprises a step of determining whether or not a complete updated firmware load has been successfully saved in the inactive update page.
Claim 14
Dependent Claim
56 words
A method as claimed in claim 12 , further comprising, when the updated firmware load has been successfully saved in the inactive update page, a step of modifying an active page flag to point to the inactive page, such that the inactive page will become the active page upon a subsequent re-boot of the communication device.
Claim 15
Dependent Claim
68 words
A method as claimed in claim 1 , wherein the step of dynamically identifying a most recently stored valid firmware load comprises steps of: a) accessing the active update page to determine the presence of a valid firmware load; and b) if a valid firmware load is not located in the active update page, accessing the inactive update page to determine the presence of a valid firmware load.
Claim 16
Dependent Claim
62 words
A method as claimed in claim 14 , wherein, if a valid firmware load is located in the active update page, the step of continuing operation of the communication device under control of the identified most recently stored valid firmware load comprises a step of continuing operation of the communication device under control of the firmware load in the active update page.
Claim 17
Dependent Claim
95 words
A method as claimed in claim 14 , wherein, if a valid firmware load is located in the inactive update page, the step of continuing operation of the communication device under control of the identified most recently stored valid firmware load comprises steps of: a) continuing operation of the communication device under control of the firmware load in the inactive update page; and b) modifying an active page flag to point to the inactive update page, whereby the inactive update page will become the active update page upon a subsequent re-boot of the communication device.
Claim 18
Dependent Claim
67 words
A method as claimed in claim 14 , wherein, if a valid firmware load is not located in the either the active of inactive update pages, the step of continuing operation of the communication device under control of the identified most recently stored valid firmware load comprises a step of continuing operation of the communication device under control of the first firmware load in the boot page.
Claim 19
Independent Claim
186 words
A system for remotely updating firmware saved in a FLASH memory of a communication device connected to a network, the system comprising: a) a boot page of the FLASH memory for storing a first firmware load; b) a pair of update pages of the FLASH memory, each update page being adapted to store a respective firmware load, one of the update pages being designated as an active update page, and the other one of the update pages as an inactive update page; c) a server operatively connected to the network and adapted for transmitting an updated firmware load through the network to the communication device; and d) a microprocessor operative to: i) store, under control of the first firmware load, the updated firmware load in the inactive update page of the FLASH memory; and ii) reboot the communication device under control of the first firmware load, including steps of: dynamically identifying, from among the firmware loads stored in the FLASH memory, a most recently stored valid firmware load; and continuing operation of the communication device under control of the identified most recently stored valid firmware load.
Claim 20
Independent Claim
186 words
A system for remotely updating firmware saved in a FLASH memory of a communication device connected to a network, the system comprising: a) a boot page of the FLASH memory for storing a first firmware load; b) a pair of update pages of the FLASH memory, each update page being adapted to store a respective firmware load, one of the update pages being designated as an active update page, and the other one of the update pages as an inactive update page; c) a server operatively connected to the network and adapted for transmitting an updated firmware load through the network to the communication device; and d) a microprocessor operative to: i) store, under control of the first firmware load, the updated firmware load in the inactive update page of the FLASH memory; and ii) reboot the communication device under control of the first firmware load, including steps of: dynamically identifying, from among the firmware loads stored in the FLASH memory, a most recently stored valid firmware load; and continuing operation of the communication device under control of the identified most recently stored valid firmware load.
Claim 21
Dependent Claim
31 words
A system as claimed in claim 18 , wherein the first firmware load includes a boot logic adapted to control operation of the microprocessor during a start-up of the communication device.
Claim 22
Dependent Claim
33 words
A system as claimed in claim 18 , wherein the server is adapted to transmit an entire updated firmware load in a single download operation using a data channel of the communication device.
Claim 23
Dependent Claim
38 words
A system as claimed in claim 20 , wherein the microprocessor is operative under control of the first firmware load to place the communication device into a loop-back mode in response to a message transmitted by the server.
Claim 24
Dependent Claim
27 words
A system as claimed in claim 18 , wherein the server is adapted to preliminarily divide the updated firmware load into a plurality of predetermined load portions.
Claim 25
Dependent Claim
31 words
A system as claimed in claim 22 , wherein the server is adapted to transmit each load portion in a respective download operation using a message channel of the communication device.
Claim 26
Dependent Claim
31 words
A system as claimed in claim 23 , wherein the server is adapted to transmit a DnldData command including an address and the load portion as arguments during each download operation.
Claim 27
Dependent Claim
50 words
A system as claimed in claim 24 , wherein the microprocessor is operative under control of the copied portion of the first firmware load to save the load portion in the FLASH memory starting at an address of the FLASH memory corresponding to the address included in the DnldData command.
Claim 28
Dependent Claim
25 words
A system as claimed in claim 22 , further comprising means for monitoring a download status of the updated firmware load to the communication device.
Claim 29
Dependent Claim
105 words
A system as claimed in claim 26 , wherein the means for monitoring a download status of the updated firmware load to the communication device comprises: a) a respective sequence number associated with each load portion transmitted by the server; b) a database including, in respect of the communication device, the sequence number corresponding to a load portion correctly saved in the FLASH memory; c) means for determining whether or not the load portion transmitted by the server has been correctly saved in the FLASH memory; and d) means for updating the database as each successive load portion is correctly saved in the FLASH memory.
Claim 30
Dependent Claim
16 words
A system as claimed in claim 27 , wherein the database is stored on the server.
Claim 31
Dependent Claim
30 words
A system as claimed in claim 18 , wherein the microprocessor is operative under control of the first firmware load to save the updated firmware load in the inactive page.
Claim 32
Dependent Claim
62 words
A system as claimed in claim 29 , wherein the microprocessor is operative under control of the first firmware load to modify the active page flag to point to the inactive update page in response to a message transmitted by the server, whereby the inactive update page will become the active update page upon a subsequent re boot of the communication device.
Claim 33
Dependent Claim
75 words
A system as claimed in claim 18 , wherein the microprocessor is operative under control of the first firmware load to dynamically identify a most recently stored valid firmware load by: a) accessing the active update page to determine the presence of a valid firmware load; and b) if a valid firmware load is not located in the active update page, accessing the inactive update page to determine the presence of a valid firmware load.
Claim 34
Dependent Claim
50 words
A system as claimed in claim 18 , wherein, if a valid firmware load is located in the active update page, the microprocessor is operative under control of the first firmware load to continue operation of the communication device under control of the firmware load in the active update page.
Claim 35
Dependent Claim
84 words
A system as claimed in claim 18 , wherein, if a valid firmware load is located in the inactive update page, the microprocessor is operative under control of the first firmware load to: a) modify an active page flag to point to the inactive update page, whereby the inactive update page will become the active update page upon a subsequent re-boot of the communication device; and b) continue operation of the communication device under control of the firmware load in the inactive update page.
Claim 36
Dependent Claim
55 words
A system as claimed in claim 18 , wherein, if a valid firmware load is not located in the either the active of inactive update pages, the microprocessor is operative under control of the first firmware load to continue operation of the communication device under control of the first firmware load in the boot page.
Claim 37
Dependent Claim
175 words
A communication device connected to a network and operative in accordance with firmware saved in a FLASH memory, the communication device comprising: a) a boot page of the FLASH memory for storing a first firmware load; b) a pair of update pages of the FLASH memory, each update page being adapted to store a respective firmware load, one of the update pages being designated as an active update page, and the other one of the update pages as an inactive update page; c) a buffer for receiving an updated firmware load through the network; and d) a microprocessor operative to: i) store, under control of the first firmware load, the updated firmware load in the inactive update page of the FLASH memory; and ii) reboot the communication device under control of the first firmware load, including steps of: dynamically identifying, from among the firmware loads stored in the FLASH memory, a most recently stored valid firmware load; and continuing operation of the communication device under control of the identified most recently stored valid firmware load.
Claim 38
Dependent Claim
175 words
A communication device connected to a network and operative in accordance with firmware saved in a FLASH memory, the communication device comprising: a) a boot page of the FLASH memory for storing a first firmware load; b) a pair of update pages of the FLASH memory, each update page being adapted to store a respective firmware load, one of the update pages being designated as an active update page, and the other one of the update pages as an inactive update page; c) a buffer for receiving an updated firmware load through the network; and d) a microprocessor operative to: i) store, under control of the first firmware load, the updated firmware load in the inactive update page of the FLASH memory; and ii) reboot the communication device under control of the first firmware load, including steps of: dynamically identifying, from among the firmware loads stored in the FLASH memory, a most recently stored valid firmware load; and continuing operation of the communication device under control of the identified most recently stored valid firmware load.
Claim 39
Dependent Claim
32 words
A communication device as claimed in claim 35 , wherein the first firmware load includes a boot logic adapted to control operation of the microprocessor during a start-up of the communication device.
Claim 40
Dependent Claim
35 words
A communication device as claimed in claim 35 , wherein the communication device is adapted to receive an entire updated firmware load in a single download operation using a data channel of the communication device.
Claim 41
Dependent Claim
39 words
A communication device as claimed in claim 37 , wherein the microprocessor is operative under control of the first firmware load to place the communication device into a loop-back mode in response to a message transmitted by the server.
Claim 42
Dependent Claim
48 words
A communication device as claimed in claim 35 , wherein the updated firmware load is preliminarily divided into a plurality of predetermined load portions, and the communication device is adapted to receive each load portion in a respective download operation using a message channel of the communication device.
Claim 43
Dependent Claim
69 words
A communication device as claimed in claim 39 , wherein each download operation comprises receiving a DnldData command including an address and the load portion as arguments, and the microprocessor is operative under control of the copied portion of the first firmware load to save the load portion in the FLASH memory starting at an address of the FLASH memory corresponding to the address included in the DnldData command.
Claim 44
Dependent Claim
31 words
A communication device as claimed in claim 35 , wherein the microprocessor is operative under control of the first firmware load to save the updated firmware load in the inactive page.
Claim 45
Dependent Claim
53 words
A communication device as claimed in claim 41 , wherein the microprocessor is operative under control of the first firmware load to modify the active page flag to point to the inactive update page, whereby the inactive update page will become the active update page upon a subsequent reboot of the communication device.
Claim 46
Dependent Claim
76 words
A communication device as claimed in claim 35 , wherein the microprocessor is operative under control of the first firmware load to dynamically identifying a most recently stored valid firmware load by: a) accessing the active update page to determine the presence of a valid firmware load; and b) if a valid firmware load is not located in the active update page, accessing the inactive update page to determine the presence of a valid firmware load.
Claim 47
Dependent Claim
51 words
A communication device as claimed in claim 35 , wherein, if a valid firmware load is located in the active update page, the microprocessor is operative under control of the first firmware load to continue operation of the communication device under control of the firmware load in the active update page.
Claim 48
Dependent Claim
86 words
A communication device as claimed in claim 35 , wherein, if a valid firmware load is located in the inactive update page, the microprocessor is operative under control of the first firmware load to: a) modify an active page flag to point to the inactive flit update page, whereby the inactive update page will become the active update page upon a subsequent re-boot of the communication device; and b) continue operation of the communication device under control of the firmware load in the inactive update page.
Claim 49
Dependent Claim
55 words
A communication device as claimed in claim 35 , wherein, if a valid firmware load is not located in either the active of inactive update pages, the microprocessor is operative under control of the first firmware load to continue operation of the communication device under control of the first firmware load in the boot page.
References Cited (Backward Citations)
US5414751A
Cited
US5268928A
Cited
US5878256A
Cited
US5418524A
Cited
US5787288A
Cited
US5822692A
Cited
US5781921A
Cited
US5812857A
Cited
US5937198A
Cited
US6073207A
Cited
US6141795A
Cited
US6253281B1
Cited
US6055632A
Cited
US6275931B1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2006-10-27 | 2007-04-28 | 2007-10-28 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2010-10-27 | 2011-04-28 | 2011-10-28 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2014-10-27 | 2015-04-28 | 2015-10-28 | $7700.00 | Window Closed / Lapsed |