Providing system reset information to service provider
View Patent ↗Methods for collection of device reset history from a network communication device comprising: (a) determining whether a reset condition is triggered by software or hardware, (b) for a software triggered reset: (i) upon a software exception, retrieving related reset information, (ii) upon an operator initiation, retrieving related reset information, (iii) allocating space in non-volatile memory, (iv) storing retrieved current reset information together with a corresponding reset time, and (v) adding the current reset information to historical reset information, (c) proceeding with the reset, (d) executing startup code during reboot, (e) upon a hardware triggered reset; (i) retrieving hardware registry and other residual hardware information still present, (ii) allocating space in non-volatile memory, (iii) storing the current retrieved reset information together with a current time that corresponds approximately to the reset and (iv) adding the reset information to historical reset information, and (f) continuing with normal operation of the device.
1. A method for collection of device reset history from a network communication device, the method comprising:
a. determining that a software reset condition has been triggered;
b. upon determination that the software reset condition is due to a software exception and prior to reset, retrieving reset information, wherein the reset information includes software exception information;
c. upon determination that the software reset condition is due to an operator or software initiation and prior to reset, retrieving reset information, wherein the reset information includes an identification of a software program responsible for the software reset;
d. allocating space in a non-volatile memory of the network communication device;
e. storing current reset information into the non-volatile memory, wherein the current reset information includes the reset information that has been retrieved together with a corresponding reset time; and
f. adding the current reset information to historical reset information within the nonvolatile memory.
2. The method of claim 1 , further comprising providing the historical reset information in response to an operator request.
3. The method of claim 1 , further comprising presenting the reset information to a management system for analysis and tracking of reset information in determination of reset conditions and reset causes.
4. The method of claim 1 , further comprising retrieving the historical reset information from the non-volatile memory and formatting the historical reset information into a data structure for subsequent retrieval by a high level management system.
5. The method of claim 1 , wherein the network communication device is one of the following: a telephony modem, a cable modem.
6. The method of claim 1 , wherein the non-volatile memory is one of the following: a flash memory, a hard drive, an optical disc.
7. The method of claim 1 , wherein the non-volatile memory is structured as a circular buffer.
8. The method of claim 1 , further comprising storing specified parameters within the non-volatile memory, wherein each specified parameter provides information related to status of the network communication device.
9. A method for collection of device reset history from a network communication device, the method comprising:
a. determining that a hardware reset has been triggered;
b. proceeding with the hardware reset of the network communication device;
c. executing startup code during reboot of the network communication device;
d. upon determination that the reboot was triggered by a hardware reset, retrieving reset information, wherein the reset information includes hardware registry information and other residual hardware information that is still present after the hardware reset;
e. allocating space in a non-volatile memory of the network communication device;
f. storing current reset information into the non-volatile memory, wherein the current reset information includes the reset information that has been retrieved together with a current time, wherein the current time corresponds approximately to the hardware reset; and
g. adding the current reset information to historical reset information within the nonvolatile memory.
10. The method of claim 9 , further comprising providing the historical reset information in response to an operator request.
11. The method of claim 9 , further comprising presenting the reset information to a management system for analysis and tracking of reset information in determination of reset conditions and reset causes.
12. The method of claim 9 , further comprising retrieving the historical reset information from the non-volatile memory and formatting the historical reset information into a data structure for subsequent retrieval by a high level management system.
13. The method of claim 9 , wherein the network communication device is one of the following: a telephony modem, a cable modem.
14. The method of claim 9 , wherein the non-volatile memory is one of the following: a flash memory, a hard drive, an optical disc.
15. The method of claim 9 , wherein the non-volatile memory is structured as a circular buffer.
16. The method of claim 9 , further comprising storing specified parameters within the non-volatile memory, wherein each specified parameter provides information related to status of the network communication device.
17. A method for collection of device reset history from a network communication device, the method comprising:
a. upon determination that a reset condition has been triggered, determining whether the reset condition is triggered by software or hardware;
b. for the reset condition triggered by software:
i. upon determination that the reset condition is due to a software exception, retrieving reset information, wherein the reset information includes software exception information;
ii. upon determination that the reset condition is due to an operator or software initiation, retrieving reset information, wherein the reset information includes an identification of a software program responsible for the reset condition;
iii. allocating space in a non-volatile memory of the network communication device;
iv. storing current reset information into the non-volatile memory, wherein the current reset information includes the reset information that has been retrieved together with a corresponding reset time; and
v. adding the current reset information to historical reset information within the non-volatile memory;
c. proceeding with a reset of the network communication device;
d. executing startup code during reboot of the network communication device;
e. upon determination that the reset condition was triggered by hardware:
i. retrieving reset information that includes hardware registry information and other residual hardware information that is still present after the hardware reset;
ii. allocating space in a non-volatile memory of the network communication device;
iii. storing the current reset information into the non-volatile memory, wherein the current reset information includes the reset information that has been retrieved together with a current time, wherein the current time corresponds approximately to the hardware reset; and
iv. adding the current reset information to historical reset information within the non-volatile memory; and
f. continuing with normal operation of the network communication device.
18. The method of claim 17 , the executing startup code further comprising:
a. retrieving hardware state information after the reset; and
b. determining whether the reset was triggered by software or hardware.
19. The method of claim 18 , wherein the hardware state information reflects the last known state of the hardware before reset.
20. The method of claim 18 , wherein the hardware state information includes residual effects of the reset in the hardware.
21. The method of claim 18 , further comprising retrieving the hardware state information from hardware registers that are not reset during a hardware reset.