Method and system for configuration and download in a restricted architecture network

• US 20060010438A1
• Filed: 09/02/2005
• Published: 01/12/2006
• Est. Priority Date: 05/01/2002
• Status: Active Grant

• Current Assignee: Thales Avionics Incorporated (Thales SA)
• Original Assignee: Thales Avionics Incorporated (Thales SA)
• Inventors: Norton, Lyle K., Brady, Kenneth A. Jr., Tsaur, Jyh-Fong, Yi, Jason Kyong-min, Weimholt, Andrew W.
• Granted Patent: US 7,725,569 B2
• Time in Patent Office: Days
• US Class Current: 717/174
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• 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: H04L 41/0253 using browsers or web-pages for accessing management information
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• 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 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and system are provided for updating software configurations of line-replaceable unit (LRU) computers in a restricted architecture network such as an in-flight entertainment system (IFES). Operating in an efficient and parallel manner, each of the LRUs independently creates an individual configuration file that identifies current software components. Each of the LRUs transmits its respective configuration file to a configuration server either automatically upon startup or manually upon request. The configuration server updates a system configuration data file with the current configuration files received from the individual LRUs. In a downloading method, a download server sends a list of desired software components to the LRUs. Each of the LRUs independently and simultaneously transfer (download) the needed software from the download server. The LRU independently requests the download server to download the needed software components. To improve scalability and reliability, the file transfers utilize standard protocols, such as FTP.

Claims

1. A system for downloading software from a download server to at least one configurable LRU computer in a restricted architecture network, wherein the system comprises:

a device of the restricted architecture network which is operable to (i) select a list of desired software components representing software desired to be loaded onto one or more target LRUs, (ii) load a new software component from a storage medium connected to the download server, and (iii) send the list of desired software components from the download server to each of the target LRUs, wherein the device is a device other than any of the LRUs; and

at least one LRU which is operable to (i) compare its said list of desired software components against a list of current software components at each of the LRUs, (ii) determine its respective needed software components by comparing the list of desired software components and the list of current software components, (iii) request the respective needed software components from the download server, and (iv) delete its software components which are not in the list of desired software components.

2. The system of claim 1, wherein the device is the download server.

3. The system of claim 1, wherein the device is a management terminal of the restricted architecture network.

4. The system of claim 1, wherein at least one LRU is further operable to display the list of current software components.

5. The system of claim 1, wherein the download server is operable to store the new software component.

6. The system of claim 1, wherein at least one LRU is further operable to reboot after receiving the respective needed software components from the download server.

7. The system of claim 1, wherein at least one LRU is further operable check the integrity of and unpack the needed software components after downloading the components.

8. The system of claim 1, wherein the device is operable to send the list of desired software components to each of the LRUs using FTP.

9. The system of claim 8, wherein at least one LRU sends an instruction to download needed software components by executing an FTP “

get”

command identifying the needed components.

10. A system for checking a configuration of at least one configurable LRU within a restricted architecture network, wherein the system comprises:

at least one configurable LRU which is operable to (i) generate an LRU configuration file in response to an initiation request received at the at least one configurable LRU from a device other than the LRUs, the LRU configuration file containing a list that identifies software components currently residing on the at least one configurable LRU;

(ii) transfer its respective LRU configuration file to at least one configuration server; and

(iii) request information pertaining to any updated software components that are identified by the at least one configuration server; and

at least one configuration server in communication with the at least one LRU which is operable to (i) detect the arrival of LRU configuration files transferred to the at least one configuration server by at least one configurable LRU;

(ii) update a system configuration data file (SCDF) that contains data representing current and previous LRU configurations by setting the current SCDF data at the server to reflect the LRU configuration files transferred by the at least one configurable LRU and by setting the previous SCDF data at the server to reflect any configuration files previously transferred to the at least one configuration server by the at least one configurable LRU;

(iii) determining, after updating the SCDF, whether any of the LRUs are to receive at least one updated software component from the configuration server and if so, (iv) identifying each of those LRUs as a target LRU.

11. The system of claim 10, wherein at least one configuration server is further operable to hold the LRU configuration files transferred to the at least one configuration server in a working directory.

12. The system of claim 11, wherein at least one configuration server is further operable to delete the LRU configuration files from the working directory.

13. The system of claim 10, wherein at least one configurable LRU generates the LRU configuration file in response to manual initiation, and wherein at least one configuration server is further operable to send an initiation request to that at least one configurable LRU.

14. The system of claim 13, wherein at least one configuration server is operable to send an initiation request to at least one LRU via an Ethernet multicast.

15. The system of claim 13, wherein at least one configuration server is operable to send an initiation request to multiple LRUs via an Ethernet broadcast.

16. The system of claim 10, wherein at least one configurable LRU transfers its respective LRU configuration file in response to the execution of an FTP “

put”

command.

17. The system of claim 10, wherein at least one configurable LRU transfers its respective LRU configuration file via FTP.

18. The system of claim 10, wherein at least one configurable LRU is further operable to store at least part of the SCDF.

19. The system of claim 10, wherein at least one configuration server is further operable to compare the respective LRU configuration file data transferred to the at least one configuration server to data from a respective configuration file data previously transferred to the at least one configuration server from the at least one configurable LRU, to determine inconsistencies therebetween, and to write the inconsistencies to an event log.

20. The system of claim 10, wherein at least one configurable LRU is further operable to store the respective LRU configuration file after generating the file.