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

• US 7,725,569 B2
• Filed: 09/02/2005
• Issued: 05/25/2010
• Est. Priority Date: 05/01/2002
• Status: Active Grant

• Current Assignee: Thales Avionics Incorporated (Thales SA)
• Original Assignee: Thales Avionics Incorporated (Thales SA)
• Inventors: Tsaur, Jyh-Fong, Yi, Jason Kyong-min, Weimholt, Andrew W., Norton, Lyle K., Brady, Kenneth A. Jr.
• Primary Examiner(s): Avellino; Joseph E
• Assistant Examiner(s): SHAW, PETER C
• Application Number:
  US11/218,823
• Publication Number:
  US 20060010438A1
• Time in Patent Office: 1,726 Days
• Field of Search: 709/223, 709/220, 709/221, 709/222, 713/100, 714/38
• US Class Current: 709/223
• 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. The file transfers utilize standard protocols, such as FTP.

Claims

1. 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 at least one configurable LRU, the LRU configuration file containing a list of current software components 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 as a desired software component; and

at least one configuration server in communication with the at least one configurable LRU which is operable to (i) detect the arrival of LRU configuration files transferred to the at least one configuration server by the 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 configuration server to reflect the LRU configuration files transferred by the at least one configurable LRU and by setting the previous SCDF data at the configuration 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 at least one configurable LRU are to receive at least one updated software component identified as a said desired software component from the configuration server and if so, (iv) identifying each of the at least one configurable LRU that are to receive the at least one updated software component as a target LRU, and (v) sending the at least one updated software component and a list of desired software components to each said target LRU;

wherein each said target LRU, upon receiving the at least one updated software component, updates the software components currently residing thereon in accordance with the at least one updated software component, and in doing so, deletes software components which are in the list of current software components but not in the list of desired software components; and

wherein the 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 respective configuration file data previously transferred to the at least one configuration server from the at least one configurable LRU, to determine inconsistencies there between, and to write the inconsistencies to an event log.

2. The system of claim 1, wherein the 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.

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

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

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

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

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

put”

command.

8. The system of claim 1, wherein the at least one configurable LRU transfers its respective LRU configuration file via FTP.

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

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

11. The system of claim 1, wherein said at least one of the LRUs automatically performs its operations (i) through (iii), and further automatically updates the software components currently residing thereon in accordance with the at least one updated software component, and automatically deletes the software components which are in the list of current software components but not in the list of desired software components.

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

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

(ii) transferring the at least one configurable LRU'"'"'s respective LRU configuration file to at least one configuration server;

(iii) requesting, at the configurable LRU, information pertaining to any updated software components that are identified by the at least one configuration server as a desired software component;

(iv) detecting, at the configuration server, the arrival of LRU configuration files transferred to the at least one configuration server by the at least one configurable LRU;

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

(vi) determining, after updating the SCDF at the configuration server, whether any of the at least one configurable LRU are to receive at least one updated software component identified as a said desired software component from the configuration server and if so,

(vii) identifying each of the at least one configurable LRU that are to receive the at least one updated software component as a target LRU, and

(viii) sending the at least one updated software component and a list of desired software components to each said target LRU;

(ix) updating the software components currently residing on each said target LRU in accordance with the at least one updated software component, and in doing so, deleting software components which are in the list of current software components but not in the list of desired software components; and

(x) comparing the respective LRU configuration file data transferred to the at least one configuration server to data from 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.

13. The method of claim 12, further comprising holding the LRU configuration files transferred to the at least one configuration server in a working directory at the at least one configuration server.

14. The method of claim 13, further comprising deleting the LRU configuration files from the working directory at the at least one configuration server.

15. The method of claim 12, wherein generating the LRU configuration file in the at least one configurable LRU is in response to manual initiation, and further comprising sending an initiation request from the at least one configuration server to that at least one configurable LRU.

16. The method of claim 15, wherein sending the initiation request from the at least one configuration server to the at least one configurable LRU is via an Ethernet multicast.

17. The method of claim 15, further comprising sending the initiation request from the at least one configuration server to multiple configurable LRUs via an Ethernet broadcast.

18. The method of claim 12, wherein transferring the at least one configurable LRU'"'"'s respective LRU configuration file is in response to the execution of an FTP “

put”

command.

19. The method of claim 12, wherein transferring the at least one configurable LRU'"'"'s respective LRU configuration file is via FTP.

20. The method of claim 12, further comprising storing at least part of the SCDF at the at least one configurable LRU.

21. The method of claim 12, further comprising storing the LRU configuration file at the respective at least one configurable LRU after generating the file.

22. The method of claim 12, wherein operations (i) through (iii) are automatically performed and further comprising automatically updating, at the at least one configurable LRU, the software components currently residing thereon in accordance with the at least one updated software component, and automatically deleting the software components which are in the list of current software components but not in the list of desired software components.