Automated double firmware upgrade
View Patent ↗A method of upgrading the software load of a device includes receiving a configuration file and checking if a device software load matches load information (EE) of the configuration file. If the device software load does not match the EE of the configuration file, a check is made to determine if the device software load matches new load information (NE) of the configuration file.
1. A method comprising:
forming a configuration file using upstream network logic, the configuration file comprising software load information (EE) that older software loads of downstream devices will respond to, and further comprising software load information (NE) that only newer software loads of downstream devices will respond to;
communicating the configuration file to at least one downstream network device that does not comprise logic to examine and respond to the NE;
receiving a request from the downstream device for the EE software load;
communicating the EE software load to the downstream device, the EE software load comprising logic to examine and respond to the NE;
receiving a request from the downstream device for the NE software load; and
communicating the NE software load to the downstream device.
2. The method of claim 1 , wherein the forming a configuration file using upstream network logic further comprises:
forming the configuration file with management information base (MB) entries for the EE and the NE.
3. The method of claim 1 , wherein the communicating the configuration file to at least one downstream network device further comprises:
communicating the configuration file over a hybrid fiber coax (HFC) network using data over cable service interface specification (DOCSIS).
4. The method of claim 1 , wherein the communicating the configuration file to at least one downstream network device further comprises:
communicating the configuration file from a provisioning server.
5. The method of claim 1 , wherein the communicating the EE software load to the downstream device further comprises:
communicating the EE software load and the NE software load from a load server, the load server separate from a provisioning server that communicates the configuration file to the downstream device.
6. The method of claim 1 , wherein the communicating the EE software load to the downstream device further comprises:
communicating the EE software load and the NE software load from a load server, the load server also a provisioning server that communicates the configuration file to the downstream device.
7. A system comprising:
machine memory or circuits comprising upstream network logic adapted to form a configuration file comprising software load information (EE) that older software loads of downstream devices will respond to, and further comprising software load information (NE) that only newer software loads of downstream devices will respond to;
machine memory or circuits comprising upstream network logic to communicate the configuration file to at least one downstream network device that does not comprise logic to examine and respond to the NE;
machine memory or circuits comprising upstream network logic to receive a request from the downstream device for the EE software load;
machine memory or circuits comprising upstream network logic to communicate the EE software load to the downstream device, the EE software load comprising logic to examine and respond to the NE;
machine memory or circuits comprising upstream network logic to receive a request from the downstream device for the NE software load; and
upstream network logic to communicate the NE software load to the downstream device.
8. The system of claim 7 , wherein forming a configuration file using upstream network logic further comprises:
the upstream network logic forming the configuration file with management information base (MIB) entries for the EE and the NE.
9. The system of claim 7 , wherein communicating the configuration file to at least one downstream network device further comprises:
the upstream network logic communicating the configuration file over a hybrid fiber coax (HFC) network using data over cable service interface specification (DOCSIS).
10. The system of claim 7 , wherein communicating the configuration file to at least one downstream network device further comprises:
the upstream network logic communicating the configuration file from a provisioning server.
11. The system of claim 7 , wherein communicating the EE software load to the downstream device further comprises:
the upstream network logic communicating the EE software load and the NE software load from a load server, the load server separate from a provisioning server that communicates the configuration file to the downstream device.
12. The system of claim 7 , wherein communicating the EE software load to the downstream device further comprises:
the upstream network logic communicating the EE software load and the NE software load from a load server, the load server also a provisioning server that communicates the configuration file to the downstream device.