IP Library › Granted Patent US 12669988
Granted Patent B2
US 12669988 · App. 18/087,826 · Granted Jun 30, 2026

Systems and methods for updating information handling systems at a remote network location from the update repository

Inventors: Ravishankar Kanakapura Nanjundaswamy (Bangalore, IN); Suman Lal Banik (Bangalore, IN); Sandeep Venkatesh Pai (Bangalore, IN)
Assignee: DELL PRODUCTS L.P.
G06F8/65
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12669988
App. No.
18/087,826
Granted
Jun 30, 2026
Kind
B2
Abstract

For information handling systems at the edge of a network, updates must traverse an extensive network pathway from an update catalog to the information handling systems. Traversing a long network pathway involves handling by numerous devices. Each device that handles the updates along the pathway results in consumption of resources (e.g., processing resources, memory, power, time, etc.)—the more devices that handle the updates, the more overall resource cost for processing the updates. Thus, improving how updates are handled, particularly at edges of networks, yield significant savings. Presented herein are new and more efficient systems and methods that coordinate updates to information handling systems at remote locations.

Claims (63)

1 . A computer-implemented method for coordinating updates at a datacenter comprising a plurality of information handling systems, the method comprising:

receiving, at a first information handling system of a datacenter, broadcasted data from one or more other information handling systems at the datacenter that comprises one or more details about the one or more other information handling systems, one or more identifiers about the one or more other information handling systems, or both, in which at least some of the broadcasted data is used to cluster information handling systems by identifying information handling systems that share one or more similarities;

joining a cluster as a member of the cluster, in which membership of the cluster is determined using at least some of the broadcasted data in which members of the cluster share one or more similarities related to one or more updates, wherein the cluster is formed based on the broadcasted data without a pre-existing cluster leader or external management controller initiating formation of the cluster, and wherein the cluster comprises the first information handling system as a member and at least one other information handling system at the datacenter as a member; and

responsive to the first information handling system being designated a cluster leader for the cluster of which it is a member, wherein the first information handling system is designated as the cluster leader after the cluster is formed and from among the members of the cluster:

receiving from each of the members of the cluster an inventory list that comprises components of the member that are subject to being updated;

using the inventory lists from the members of the cluster to generate a compliance report that indicates which members have a component that has an update; and

providing, or causing to be provided, a location of a downloaded update at a local datastore to the members of the cluster that have the component that has not yet applied the update, in which the update is downloaded to the local datastore by an information handling system at the datacenter that has been designated to access and download the update on behalf of the members of the cluster that have the component that has not yet applied the update.

2 . The computer-implemented method of claim 1 further comprising:

designating the information handling system to access and download to the local datastore the update on behalf of the members of the cluster that have the component that has not yet applied the update.

3 . The computer-implemented method of claim 1 wherein:

responsive to the cluster not being in a mesh network topology, causing the designated information handling system to store the update in the local datastore that is a shared location, which is accessible by at least the members of the cluster that have the component that has not yet applied the update; and

responsive to the cluster being in a mesh network topology, causing the designated information handling system to store the update in the local datastore that is a memory location on a member of the cluster.

4 . The computer-implemented method of claim 1 further comprising:

broadcasting, from the first information handling system at the datacenter to one or more other information handling systems at the datacenter, data about the first information handling system comprising one or more details, one or more identifiers, or both about the first information handling system, in which at least some of the data is used to help form the cluster by identifying one or more other information handling systems that share one or more similarities related to updating with the first information handling system.

5 . The computer-implemented method of claim 1 wherein the datacenter is an edge datacenter.

6 . The computer-implemented method of claim 1 wherein the step of using the inventory lists from the members of the cluster to generate a compliance report that indicates which members have a component that has an update comprises:

using the inventory lists from the members of the cluster to generate a consolidated list of components of the cluster, including identifying components shared by two or more members of the cluster; and

using the consolidated list for the cluster and an update catalog to generate the compliance report.

7 . The computer-implemented method of claim 6 further comprising:

responsive to the datacenter comprising a plurality of clusters and each cluster comprises a cluster leader, sharing the consolidated list of components for the cluster with other cluster leaders to identify whether one or more components are common across clusters; and

responsive to one or more components being in common across two or more clusters, designating, or participating in designating, the designated information handling system to access and download to the local datastore the update on behalf of the members of the two or more clusters that have the component that has not yet applied the update.

8 . The computer-implemented method of claim 1 wherein the inventory list is a hash list format.

9 . The computer-implemented method of claim 1 further comprising:

receiving from at least one of the members of the cluster an updated inventory list; and

using the updated inventory list or lists to generate a compliance report.

10 . An information handling system at a datacenter, the information handling system comprising:

one or more processors; and

a non-transitory computer-readable medium or media comprising one or more sets of instructions which, when executed by at least one of the one or more processors, causes steps to be performed comprising:

receiving broadcasted data from one or more other information handling systems at the datacenter that comprises one or more details about the one or more other information handling systems, one or more identifiers about the one or more other information handling systems, or both, in which at least some of the broadcasted data is used to cluster information handling systems by identifying information handling systems that share one or more similarities related to one or more updates;

joining a cluster as a member of the cluster, in which membership of the cluster is determined using at least some of the broadcasted data in which members of the cluster share one or more similarities, wherein the cluster is formed based on the broadcasted data without a pre-existing cluster leader or external management controller initiating formation of the cluster, and wherein the cluster comprises the information handling system as a member and at least one other information handling system at the datacenter as a member; and

responsive to being designated a cluster leader for the cluster of which it is a member, wherein the information handling system is designated as the cluster leader after the cluster is formed and from among the members of the cluster:

receiving from each of the members of the cluster an inventory list that comprises components of the member that are subject to being updated;

using the inventory lists from the members of the cluster to generate a compliance report that indicates which members have a component that has an update; and

providing, or causing to be provided, a location of a downloaded update at a local datastore to the members of the cluster that have the component that has not yet applied the update, in which the update is downloaded to the local datastore by a designated information handling system at the datacenter to access and download the update on behalf of at least the members of the cluster that have the component that has not yet applied the update.

11 . The information handling system of claim 10 wherein the non-transitory computer-readable medium or media further comprises one or more sequences of instructions which, when executed by at least one of the one or more processors, causes steps to be performed comprising:

designating the designated information handling system to access and download to the local datastore the update on behalf of at least the members of the cluster that have the component that has not yet applied the update.

12 . The information handling system of claim 11 wherein the designated information handling system is the information handling system or a member of the cluster.

13 . The information handling system of claim 10 wherein the non-transitory computer-readable medium or media further comprises one or more sequences of instructions which, when executed by at least one of the one or more processors, causes steps to be performed comprising:

responsive to the cluster not being in a mesh network topology, causing the designated information handling system to store the update in the local datastore that is a shared location, which is accessible by at least the members of the cluster that have the component that has not yet applied the update; and

responsive to the cluster being in a mesh network topology, causing the designated information handling system to store the update in the local datastore that is a memory location on a member of the cluster.

14 . The information handling system of claim 10 wherein the non-transitory computer-readable medium or media further comprises one or more sequences of instructions which, when executed by at least one of the one or more processors, causes steps to be performed comprising:

broadcasting to one or more other information handling systems at the datacenter, data about the information handling system comprising one or more details, one or more identifiers, or both about the information handling system, in which at least some of the data is used to help form the cluster by identifying one or more other information handling systems that share one or more similarities related to updating.

15 . The information handling system of claim 10 wherein the step of using the inventory lists from the members of the cluster to generate a compliance report that indicates which members have a component that has an update comprises:

using the inventory lists from the members of the cluster to generate a consolidated list of components of the cluster, including identifying components shared by two or more members of the cluster; and

using the consolidated list for the cluster and an update catalog to generate the compliance report.

16 . The information handling system of claim 10 wherein the non-transitory computer-readable medium or media further comprises one or more sequences of instructions which, when executed by at least one of the one or more processors, causes steps to be performed comprising:

sharing the consolidated list of components for the cluster with one or more other cluster leaders at the datacenter to identify whether one or more components are common across clusters; and

responsive to one or more components being in common across two or more clusters, designating, or allowing to be designated, the designated information handling system to access and download to the local datastore the update on behalf of the members of the two or more clusters that have the component that has not yet applied the update.

17 . The information handling system of claim 16 wherein the designated information handling system is a member of a different cluster than the information handling system.

18 . A non-transitory computer-readable medium or media comprising one or more sequences of instructions which, when executed by at least one processor, causes steps to be performed comprising:

receiving, at a first information handling system of a datacenter, broadcasted data from one or more other information handling systems at the datacenter that comprises one or more details about the one or more other information handling systems, one or more identifiers about the one or more other information handling systems, or both, in which at least some of the broadcasted data is used to cluster information handling systems by identifying information handling systems that share one or more similarities related to one or more updates;

joining a cluster as a member of the cluster, in which membership of the cluster is determined using at least some of the broadcasted data in which members of the cluster share one or more similarities, wherein the cluster is formed based on the broadcasted data without a pre-existing cluster leader or external management controller initiating formation of the cluster, and wherein the cluster comprises the first information handling system as a member and at least one other information handling system at the datacenter as a member; and

responsive to the first information handling system being designated a cluster leader for the cluster of which it is a member, wherein the first information handling system is designated as the cluster leader after the cluster is formed and from among the members of the cluster:

receiving from each of the members of the cluster an inventory list that comprises components of the member that are subject to being updated;

using the inventory lists from the members of the cluster to generate a compliance report that indicates which members have a component that has an update;

designating, or participating in designating, an information handling system to access and download to a local datastore the update on behalf of members of the cluster that have the component that has not yet applied the update; and

providing, or causing to be provided, a location of the downloaded update at the local datastore to the members of the cluster that have the component that has not yet applied the update.

19 . The non-transitory computer-readable medium or media of claim 18 wherein the step of using the inventory lists from the members of the cluster to generate a compliance report that indicates which members have a component that has an update comprises:

using the inventory lists from the members of the cluster to generate a consolidated list of components of the cluster, including identifying components shared by two or more members of the cluster; and

using the consolidated list for the cluster and an update catalog to generate the compliance report.

20 . The non-transitory computer-readable medium or media of claim 18 further comprising one or more sequences of instructions which, when executed by at least one processor, causes steps to be performed comprising:

sharing the consolidated list of components for the cluster with one or more other cluster leaders at the datacenter to identify whether one or more components are common across clusters; and

responsive to one or more components being in common across two or more clusters, designating, or allowing to be designated, the designated information handling system to access and download to the local datastore the update on behalf of the members of the two or more clusters that have the component that has not yet applied the update.