Integrated services hub binary file trial run process

• US 7,409,435 B1
• Filed: 02/28/2002
• Issued: 08/05/2008
• Est. Priority Date: 02/28/2002
• Status: Expired due to Fees

• Current Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Bayerl, Thomas, Lilly, Steven R.
• Primary Examiner(s): Jaroenchonwanit; Bunjob
• Assistant Examiner(s): Chankong; Dohm
• Application Number:
  US10/086,101
• Time in Patent Office: 2,350 Days
• Field of Search: 709/221, 717/171, 717/173
• US Class Current: 709/217
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 8/654 using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/084 Configuration by using pre-existing information, e.g. using templates or copying from other elements
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The present invention discloses a method of automatically downloading and testing binary code for a customer premises telecommunications hub. When a new binary file is received by the hub, it is loaded into flash memory, but is not locked or designated as the currently active binary file. A trial run message is then written into SDRAM identifying the new file. The system if rebooted and starts up with the new file. A verification process is run to determine if the new file functions properly. If it does, the trial run message is deleted and the new file is locked into flash memory as the current binary. If the trial fails, the trial run message is deleted and the system is rebooted with the previous binary file.

Claims

1. A computer-implemented method of downloading a binary file to a customer premises telecommunications hub, the method comprising:

receiving a new binary file in the customer premises telecommunications hub,

configuring a non-volatile memory using a trial run parameter;

loading the new binary file into a location of non-volatile memory on the hub;

flagging, in the non-volatile memory, an old binary file as a currently active file;

soft rebooting the hub; and

checking, during the soft rebooting, whether a trial run message is stored in a volatile memory on the hub; and

if a trial run message is stored in the volatile memory,

identifying the location in non-volatile memory of the new binary file based on the trial run message,

deleting the trial run message,

operating the hub with the new binary file, and

verifying proper operation of the hub with the new binary file;

else

if the trial run message is not stored in the volatile memory,

operating the hub with the old binary file, and

deleting the trial run parameter.

2. The computer-implemented method of claim 1, further comprising:

if proper operation of the hub with the new binary file is verified,

deleting the trial run parameter; and

flagging, in the non-volatile memory, the new binary file as the currently active file for the hub.

3. The computer-implemented method of claim 1 wherein verifying proper operation of the hub with the new binary file comprises receiving an acknowledgment message from an external server.

4. The computer-implemented method of claim 1 wherein verifying proper operation of the hub with the new binary file comprises receiving a configuration file from an external server.

5. The computer-implemented method of claim 1 wherein:

proper operation of the binary file is verified by detecting the receipt of a domain name from an external server.

11. The computer-implemented method of claim 2, further comprising

if proper operation of the hub with the new binary file is not verified,

soft rebooting the hub;

operating the hub with the old binary file; and

deleting the trial run parameter.

6. A customer premises telecommunications hub comprising:

a nonvolatile memory having a first and second memory partition;

means for designating an old binary file in the first memory partition as currently active;

means for receiving a new binary file;

means for storing the new binary file into the second memory partition;

means for configuring the non-volatile memory using a trial run parameter;

means for soft rebooting the hub;

means for checking, during soft rebooting, whether a trial run message is stored in a volatile memory on the hub;

means for operating the hub with the new binary file stored in the second memory partition;

means for identifying a partition of non-volatile memory storing the new binary file based on the trial run message; and

means for deleting the trial run message.

7. The customer premises telecommunications hub according to claim 6, wherein:

said means for verifying proper operation comprises means for detecting the receipt of a signal by said hub from an external server.

8. The customer premises telecommunications hub according to claim 7, wherein:

said signal is an acknowledge message from a DHCP server.

9. The customer premises telecommunications hub according to claim 7, wherein:

said signal is a configuration file from a TFTP server.

12. The customer premises telecommunications hub of claim 6, further comprising:

means for operating the hub with the old binary file stored in the first memory partition; and

means for deleting the trial run parameter.

10. In a customer premises telecommunications hub, a method comprising;

storing a new binary file in a location of non-volatile memory;

flagging, in the non-volatile memory, an old binary file as a currently active binary file;

storing a trial run message in a volatile memory,

wherein the trial run message identifies the new binary file stored in the location of non-volatile memory;

soft rebooting the hub;

if the trial run message is still stored in the volatile memory,

deleting the trial run message; and

operating the hub with the new binary file, and

verifying proper operation of the hub with the new binary file, and

after verifying proper operation of the new binary file,

flagging, in the non-volatile memory, the new binary file as the currently active binary file, and

deleting the trial run parameter.

13. In the customer premises telecommunications hub of claim 10, the method further comprising:

soft rebooting the hub; and

if proper operation of the hub is not verified,

operating the hub with the old binary file; and

deleting the trial run parameter.

14. In the customer premises telecommunications hub of claim 10, the method further comprising:

if proper operation of the hub with the new binary file is verified,

flagging, in the non-volatile memory, the new binary file as the currently active binary file; and

deleting the trial run parameter.