SYSTEM AND METHOD FOR DISTRIBUTED PATCH MANAGEMENT

• US 20130326494A1
• Filed: 07/31/2012
• Published: 12/05/2013
• Est. Priority Date: 06/01/2012
• Status: Abandoned Application

• Current Assignee: Top Patch, Inc.
• Original Assignee: Top Patch, Inc.
• Inventors: NUNEZ, Yonesy F.
• Application Number:
  US13/562,829
• Publication Number:
  US 20130326494A1
• Time in Patent Office: Days
• US Class Current: 717/172
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1091 Interfacing with client-server systems or between P2P systems
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A method and system for distributing patches (e.g., software patches) to network nodes in a peer-to-peer network. A plurality of network nodes may be designated or associated as server nodes. Each server node may be assigned to manage software patch distribution for a different zone, where each zone may include a different plurality of network nodes. Upon detecting a node in a zone to be a node in need of an update, a patch may be received from a patch source at the server node in the same zone as the node in need of the update. The patch may be transferred from the server node to the node in need of the update. The patch may be used to update the node in need of an update.

Claims

1. A method for distributing patches to network nodes in a peer-to-peer network, the method comprising:

designating a plurality of network nodes as server nodes, each server node assigned to manage software patch distribution for a different zone, each zone comprising a different plurality of network nodes;

upon detecting a node in a zone to be a node in need of an update;

receiving a patch from a patch source at the server node in the same zone as the node in need of the update;

transferring the patch from the server node to the node in need of the update; and

using the patch to update the node in need of the update.

2. The method of claim 1 comprising executing an optimization algorithm to determine the optimal partitioning of the network into zones and the optimal node to designate as a server node in each zone.

3. The method of claim 2, wherein the optimal node in each zone has, compared to other nodes in the zone, the fastest overall traffic speed when exchanging information with the other network nodes in the zone.

4. The method of claim 1, comprising, if the server node in a zone does not transmit the patch, re-designating another node to be a new server node for the zone.

7. The method of claim 1 comprising indexing each network node as a point in a coordinate space based on its logical distance to the other network nodes, wherein the network nodes are grouped into zones by dividing the coordinate space into a plurality of regions and grouping the nodes into the same zone that have indices in the same region.

8. The method of claim 1 comprising, for each network node:

assigning a key upon authorizing a network node to join the network;

associating the key with the index of the network node; and

comparing copies of the key stored at the network node and the server node that are associated with the network node index to authorize a network node, authenticate communication between nodes and coordinate the transferring of patches between nodes.

9. The method of claim 1, wherein the nodes are in a heterogeneous environment with multiple patch management protocols, and wherein the network of nodes is partitioned into a plurality of zones such that each zone supports a homogenous environment supporting a single patch management protocol at the server node.

10. The method of claim 1, wherein transferring comprises routing the patch from the server node to the network nodes along a path of minimum logical distance.

11. The method of claim 1, wherein said detecting a node in a zone to be a node in need of the update comprises determining that system components and/or applications in the node are missing a patch.

5. The method of claim 5, wherein the new server node is another network node in the same zone.

6. The method of claim 5, wherein the new server node is a server node in another logically adjacent zone.

12. A peer-to-peer system for distributing patches, the system comprising:

a plurality of network nodes, a subset of which are designated as server nodes, each server node comprising a processor configured to manage software patch distribution for an associated plurality of network nodes forming a zone, wherein each server node manages a different plurality of network nodes forming a different zone from other server nodes; and

a memory storing the association of the server nodes with the network nodes, wherein, upon determination that a network node in a zone is a node in need of an update, the processor of the server node, which is associated with the network node in the memory, is configured to;

receive a patch from a patch source; and

transfer the patch from the server node to the network node in need of the update to update the network node using the patch.

13. The system of claim 12 comprising a network server to associate a server node with each zone of network nodes.

14. The system of claim 13, wherein the network server is to execute an optimization algorithm to determine the optimal server node to associate with the network nodes in each zone.

15. The system of claim 13, wherein the network server indexes each network node as a point in a coordinate space based on its logical distance to the other network nodes in the zone and divides the coordinate space into a plurality of regions and groups the nodes into the same zone that have indices in the same region of the coordinate space.

16. The system of claim 12, wherein, for each network node assigned a key and associated with an index, the processor of the server node associated with the network node is to compare copies of the key stored at the network node and the server node that are associated with the network node'"'"'s index to authorize a network node to join the network, authenticate communication between nodes and coordinate the transfer of patches between nodes.

17. The system of claim 12, wherein, if the server node associated with a zone does not transmit the patch, the processor of a new server node transmits the patch.

18. The system of claim 17, wherein the new server node is another network node in the same zone.

19. A method for distributing a software update to network nodes, the method comprising:

if it is determined that a node in a zone needs a software update, each zone comprising a different plurality of network nodes, obtaining a software update at a server node in the same zone as the node in need of the update; and

transferring the software update from the server node to the node in need of the update.

20. The method of claim 19, wherein a plurality of network nodes are server nodes, each server node assigned to manage software update distribution for a different zone.