Computing infrastructure
First Claim
1. A dynamically reconfigurable computing infrastructure comprising:
- a distributed network; and
at least one team of geographically distributed computing nodes, the team of computing nodes comprising at least n nodes configured to use coding theory to achieve Byzantine agreement, wherein agreement among at least k of the n nodes is sufficient to tolerate f unknown faulty or malicious nodes and c known crashes or unresponsive nodes when (c+2f)<
(n−
k); and
wherein a computing node comprises;
(a) a memory;
(b) at least one processor;
(c) a first component configured to perform computing and data processing functions which further comprise secure communications and access controls;
(d) a second component configured to recognize and differentiate between computing nodes by their cryptographic identities and the absence of anomalous behaviors, and to determine whether at least one of an object, a subject, and an interaction is authorized or unauthorized;
(e) a third component configured to establish trust between computing nodes and collaborate with computing nodes to establish teams of nodes;
(f) a fourth component configured to mutually associate nodes contained within the teams of nodes, wherein each such team of nodes is accountable for a portion of the aggregate responsibilities of the computing infrastructure; and
;
(g) a fifth component configured to timely publish selected aggregated resource information to the teams of nodes.
0 Assignments
0 Petitions
Accused Products
Abstract
An affordable, highly trustworthy, survivable and available, operationally efficient distributed supercomputing infrastructure for processing, sharing and protecting both structured and unstructured information. A primary objective of the SHADOWS infrastructure is to establish a highly survivable, essentially maintenance-free shared platform for extremely high-performance computing (i.e., supercomputing)—with “high performance” defined both in terms of total throughput, but also in terms of very low-latency (although not every problem or customer necessarily requires very low latency)—while achieving unprecedented levels of affordability at its simplest, the idea is to use distributed “teams” of nodes in a self-healing network as the basis for managing and coordinating both the work to be accomplished and the resources available to do the work. The SHADOWS concept of “teams” is responsible for its ability to “self-heal” and “adapt” its distributed resources in an “organic” manner. Furthermore, the “teams” themselves are at the heart of decision-making, processing, and storage in the SHADOWS infrastructure. Everything that'"'"'s important is handled under the auspices and stewardship of a team
56 Citations
20 Claims
-
1. A dynamically reconfigurable computing infrastructure comprising:
-
a distributed network; and at least one team of geographically distributed computing nodes, the team of computing nodes comprising at least n nodes configured to use coding theory to achieve Byzantine agreement, wherein agreement among at least k of the n nodes is sufficient to tolerate f unknown faulty or malicious nodes and c known crashes or unresponsive nodes when (c+2f)<
(n−
k); andwherein a computing node comprises; (a) a memory; (b) at least one processor; (c) a first component configured to perform computing and data processing functions which further comprise secure communications and access controls; (d) a second component configured to recognize and differentiate between computing nodes by their cryptographic identities and the absence of anomalous behaviors, and to determine whether at least one of an object, a subject, and an interaction is authorized or unauthorized; (e) a third component configured to establish trust between computing nodes and collaborate with computing nodes to establish teams of nodes; (f) a fourth component configured to mutually associate nodes contained within the teams of nodes, wherein each such team of nodes is accountable for a portion of the aggregate responsibilities of the computing infrastructure; and
;(g) a fifth component configured to timely publish selected aggregated resource information to the teams of nodes. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification