Method and apparatus for automatically updating software components on end systems over a network

• US 6,009,274 A
• Filed: 06/24/1997
• Issued: 12/28/1999
• Est. Priority Date: 12/13/1996
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: 3Com Corporation (HP Inc.)
• Inventors: Lin, Pei-Chen, Fletcher, Rick
• Primary Examiner(s): Hafiz, Tariq R.
• Assistant Examiner(s): DAM, TUAN QUANG
• Application Number:
  US08/881,517
• Time in Patent Office: 917 Days
• Field of Search: 395/712, 395/651-653, 395/200.33, 395/200.32, 395/200.47, 395/200.49, 395/200.51, 395/200.52, 707/10, 707/203, 713/1, 713/2, 713/100, 709/221, 709/222, 709/202, 709/203, 709/217, 709/219
• US Class Current: 717/173
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 2012/5626 Network management, e.g. Intelligent nets
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/042 comprising distributed management centres cooperatively managing the network
• CPC Class Codes: H04L 41/044 comprising hierarchical management structures
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/142 using statistical or mathematical methods
• CPC Class Codes: H04L 41/28 Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 41/509 wherein the managed service relates to media content delivery, e.g. audio, video or TV
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 67/01 Protocols
• 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
• CPC Class Codes: H04W 24/08 Testing, supervising or monitoring using real traffic

Abstract

A method and apparatus for automatically updating software components in one or more agents (end systems) in a network. An ASU server generates a multicast request to agents within its network domain, identifying the newest, available versions of software components that may be installed on the agents. Agents compare installed versions with the newest versions and respond to the server request by indicating components that need to be updated. Components include network and non-network software as well as operating system (OS) software. The ASU server then transmits the requested components to the requesting agents in a self extracting compressed file. The file is installed and the components updated without rebooting system software.

Claims

1. A method of automatically updating software in a network including a server and an agent, comprising the steps of:

a) generating a server request, wherein said server request identifies the newest version level of a software component;

b) generating an agent update request if the agent needs said newest version level of said software component; and

c) updating the agent with said newest version level of said software component in response to said update request.

2. The method of claim 1, wherein said step b) of generating an agent update request includes the steps of:

i) comparing said newest version level with a version level of said software component that is currently installed on the agent; and

ii) generating said response only if there is a discrepancy between said newest version level and said currently installed version level.

3. The method of claim 1, wherein said update request indicates a version level of said software component that is currently running on the agent, and wherein said step c) of updating the agent includes the steps of:

i) comparing said newest and said current version levels; and

ii) updating the agent only if there is a discrepancy between said newest version level and said currently installed version level.

4. The method of claim 1, wherein said step of updating the agent includes the steps of:

i) transmitting the newest version of said software component to the agent; and

ii) installing said newest version of said software component without rebooting system software.

5. The method of claim 4, wherein said step of installing includes the steps of:

i) uncompressing said component;

ii) replacing said current version with said newest version;

iii) unloading the agent; and

iv) reloading and restarting the agent.

6. The method of claim 1, wherein said software component is dynamically loadable and unloadable.

7. The method of claim 1, wherein said software component includes one of network interface card driver software and desktop agent driver software.

8. The method of claim 1, wherein said software component includes an operating system (OS) software component.

9. A network comprising:

a) a server having a request generator, wherein said server generates a server request on a communication channel, and wherein said server request identifies the newest version level of a software component;

b) an agent, coupled to said communication channel and having an update request generator, wherein said agent receives said server request and generates an update request if said agent requires said newest version of said software component; and

c) wherein said server updates said agent with said newest version level of said software component in response to said update request.

10. The network of claim 9, wherein said agent compares said newest version level with a version level of said software component that is currently installed on said agent, and wherein said agent generates said update request only if there is a discrepancy between said newest version level and said currently installed version level.

11. The network of claim 9, wherein said update request indicates a version level of said software component that is currently installed on said agent, and wherein said server compares said newest version level with said currently installed version level, and wherein said server updates said agent only if there is a discrepancy between said newest version level and said currently installed version level.

12. The network of claim 9, wherein said server updates said agent by transmitting the newest version of said software component to said agent, and wherein said newest version of said software component is installed by said agent without rebooting system software.

13. The network of claim 12, wherein said component includes an installer, and wherein said installer

i) uncompresses said component;

ii) replaces said current version with said newest version;

iii) unloads the agent; and

iv) reloads and restarts the agent.

14. The network of claim 9, wherein said software component is dynamically loadable and unloadable.

15. The network of claim 9, wherein said software component includes one of network interface card driver software and desktop agent driver software.

16. The network of claim 9, wherein said software component includes an operating system (OS) software component.

17. A method of automatically updating software in a network including a server, a first agent and a second agent, comprising the steps of:

a) generating a multicast server request, wherein said multicast request identifies the newest version levels for a first software component and a second software component;

b) generating a first agent update request if the first agent needs said newest version of one of said first and second software components;

c) generating a second agent update request if the second agent needs said newest version of one of said first and second software components; and

d) updating the first and second agents with said newest version levels of said first and second software components in response to said first and second update requests.

18. The method of claim 17, wherein said step of generating a first agent update request includes the steps of:

i) comparing said newest version levels with version levels of said first and second components that are currently installed on the first agent; and

ii) generating said first update request only if there is a discrepancy between at least one of said newest version levels and said currently installed version levels of said first agent; and

wherein said step of generating a second agent update request includes the steps of;

i) comparing said newest version levels with version levels of said first and second components that are currently installed on the second agent; and

ii) generating said second update request only if there is a discrepancy between at least one of said newest version levels and said currently installed version levels of said second agent.

19. The method of claim 17, wherein said first and second update requests indicate version levels of said first and second components that are currently installed on the first and second agents, and wherein said step of updating the first and second agents includes the steps of:

i) comparing said newest version levels with said currently installed version levels of said first agent;

ii) updating the first agent only if there is a discrepancy between at least one of said newest version levels and said currently installed version levels of said first agent;

iii) comparing said newest version levels with said currently installed version levels of said second agent; and

iv) updating the second agent only if there is a discrepancy between at least one of said newest version levels and said currently installed version levels of said second agent.

20. The method of claim 17, wherein said step of updating the first and second agents includes the steps of:

i) transmitting the newest version of said first and second software components to the first and second agents; and

ii) installing said newest versions of said first and second software components in said first and second agents without rebooting system software.

21. The method of claim 20, wherein said step of installing in said first agent includes the steps of:

i) uncompressing said components;

ii) replacing said first current versions with said newest versions;

iii) unloading the first agent; and

iv) reloading and restarting the first agent.

22. The method of claim 17, wherein said first and second software components are dynamically loadable and unloadable.

23. The method of claim 17, wherein said first software component includes one of network interface card driver software and desktop agent driver software.

24. The method of claim 17, wherein said step of updating the first and second agents includes the step of generating a table indicating the version levels of said first and second software components required by said first and second agent.

25. The method of claim 20, wherein said step of updating further includes the steps of:

updating said first agent with said newest version of said first software component if said first software component is indicated in said table;

thereafter

updating said second agent with said newest version of said first software component if said first software component is indicated in said table;

thereafter

updating said first agent with said newest version of said second software component if said second software component is indicated in said table; and

thereafter

updating said second agent with said newest version of said second software component if said second software component is indicated in said table.

26. The method of claim 20, wherein said step of updating further includes the steps of:

updating said first agent with said newest version of said first software component if said first software component is indicated in said table;

thereafter

updating said first agent with said newest version of said second software component if said second software component is indicated in said table;

thereafter

updating said second agent with said newest version of said first software component if said first software component is indicated in said table; and

thereafter

updating said second agent with said newest version of said second software component if said second software component is indicated in said table.

27. A network comprising:

a) a server having a request generator, wherein said server generates a server request on a communication channel, and wherein said server request identifies the newest version levels of a first software component and a second software component;

b) a first agent, coupled to said communication channel and having an update request generator, wherein said first agent receives said server request and generates an update request if said first agent requires said newest version of one of said first and second software components;

c) a second agent, coupled to said communication channel and having an update request generator, wherein said second agent receives said server request and generates an update request if said second agent requires said newest version of one of said first and second software components; and

c) wherein said server updates said first and second agents with said newest version levels of said first and second software components in response to said first and second update requests.

28. The network of claim 27, wherein said first agent compares said newest version levels with a version level of said first and second software components currently installed on said first agent, and wherein said first agent generates said first update request only if there is a discrepancy between at least one of said newest version levels and said currently installed version levels of said first agent.

29. The network of claim 27, wherein said first and second update requests indicate version levels of said first and second software components currently installed on said first and second agents, and wherein said server compares said newest version levels with said currently installed version levels, and wherein said server updates said first and second agents only if there is a discrepancy between at least one of said newest version levels and said currently installed version levels.

30. The network of claim 27, wherein said server updates said first and second agents by transmitting the newest version of said software components to said first and second agents, and wherein said newest version of said software components are installed by said agents without rebooting system software.

31. The network of claim 30, wherein said transmitted components each include an installer, and wherein said installer

i) uncompresses said component;

ii) replaces said current version with said newest version;

iii) unloads the agent; and

iv) reloads and restarts the agent.

32. The network of claim 27, wherein said first and second software components are dynamically loadable and unloadable.

33. The network of claim 27, wherein said first software component includes one of network interface card driver software and desktop agent driver software.

34. The network of claim 27, wherein said first software component includes an operating system (OS) software component.

35. The network of claim 27, wherein said server includes a table generator for generating a table indicating the version levels of said first and second software components required by said first and second agent.

36. A server for updating software components in agents, the server comprising:

a request generator for generating server requests on a communication channel, said server requests identifying available versions of software components to a plurality of agents;

a memory for storing agent update requests generated by any of said agents responding to server requests, wherein said server stores update requests received from said agents, said update requests identifying said available software components required by said responding agents; and

an update mechanism, wherein said server updates said responding agents with said required software components.

37. The server of claim 36, wherein said update requests are stored in said memory in a table format wherein each of said responding agents defines a column, and wherein each required software component defines a row.

38. The server of claim 37, wherein said server updates said responding agents with said required software components on a row-by-row basis.

39. The server of claim 37, wherein said server updates said responding agents with said required software components on a column-by column basis.

40. The server of claim 36, wherein said update mechanism is configurable to include a certain time period for updating, wherein updating occurs during said included time period.

41. The server of claim 36, wherein said update mechanism is configurable to exclude a certain time period for updating, wherein updating does not occur during said excluded time period.

42. The server of claim 36, wherein said request generator is configurable to generate a first server request for a first one of said available software components and a second server request for a second one of said available software components.

43. The server of claim 36, wherein said request generator is configurable to generate a first server request for a plurality of said available software components.

44. The server of claim 36, wherein said request generator is configurable to generate a multicast request to all of said plurality of agents simultaneously.

45. The server of claim 36, wherein said request generator is configurable to generate a first request to a first one of said plurality of agents and a second request to a second one of said plurality of agents.