|Publication number||US4015246 A|
|Application number||US 05/567,629|
|Publication date||Mar 29, 1977|
|Filing date||Apr 14, 1975|
|Priority date||Apr 14, 1975|
|Publication number||05567629, 567629, US 4015246 A, US 4015246A, US-A-4015246, US4015246 A, US4015246A|
|Inventors||Albert L. Hopkins, Jr., Thomas Basil Smith, III|
|Original Assignee||The Charles Stark Draper Laboratory, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (12), Referenced by (92), Classifications (20)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention is directed to the problem of designing a computer system that will continue to be able to exercise control despite the occurrence of a component fault. There are numerous applications where computer survival is critical, including military, space, and transportation applications. There are others where computers would be used if they were more dependable, including medical, and nuclear applications.
The earliest approach to enhanced computer system reliability was to have two or three computers each capable of control, and to switch from one to another when one failed. The problem is how to find out that one has failed, and to be able to restart the job on the next computer. Another approach has been to have two computers running in synchronism.
They will disagree when one has failed, thus solving the first part of the problem. Still another approach, three in synchronism, will not only show disagreement when one has failed but will indicate which one it was. The latter principle was employed by the Saturn V Launch Vehicle Digital Computer in the mid 1960's.
Another approach to the problem is to use coded representations for data that will be altered in an identifiable manner by any component fault. This has been used in various projects, notable the JPL STAR computer designed and built at the Jet Propulsion Laboratory. This approach is designed to avoid the expense of replicating to detect and correct faults. The disadvantages are that many non-standard circuits must be designed, manufactured, and understood by maintenance personnel, and also that it is difficult to verify at an arbitrary instant of time that all of the assumed protection is indeed present and in working order.
There are various ways in which one can employ the triple-redundancy principle. One is to triplicate small parts of a computer and vote on every input to each part. This is characteristic of the Saturn V computer design. Another way is to triplicate an entire system and vote on all inputs to the system. This represents an extreme measure, rather than a practical approach.
There are other more realistic approaches in which parts of the system are triplicated with voting at chosen points. Some systems, notable for aircraft, have used more than three of each part of a system in order to achieve immunity to more than one failure.
Another proposal was a computer system composed of numerous small processors and memory modules interconnected by a time-shared bus, in which three units operate together to perform a part of the total system job. Any triplet can fail, in which case the failure will be detected and the information necessary for restart will be salvaged and passed along to another triplet on the first occasion when another triplet is available.
Yet another approach was suggested, which comprised a group of individual non-redundant units each connected to a common bus system. The shortcoming with both of the last approaches has been that no mechanism had been devised that would allow units to be connected to the bus in such a way that they could be disconnected and reconnected when necessary despite the presence of faults, and that this ability to disconnect and reconnect could be dynamically verified.
Without this, there was the possibility that a single failure would either bring down the entire system, or else would go undetected until a second failure occurred which, together with the first, would bring down the system. In either case the desired fault tolerance is not achieved.
The invention presented here departs from the above in that it allows data connections to be reliably made and broken between processor, memory units, etc., and members of a redundant bus. Such connections can be changed only by two or three processors acting in synchronism. No single processor can change its own connection status, nor that of any other unit.
When a unit persistently disagrees with its assigned partners, it will have its power switched off and will be logically disconnected from the system, by other, correctly functioning, processors acting in synchronism.
This invention discloses a bus guardian unit for an ultra reliable computer system, said bus guardian unit being adapted to listen to signals from a plurality of processors, etc., and act in response to same to control the connection of a processor, memory, etc., to a particular bus of a plurality of buses.
In addition, the disclosure herein illustrates the utilization of a pair of bus guardian units connected to provide added reliability when used to control the access of a processor, memory, etc., to a bus.
An additional feature of this disclosure is the use of a bus guardian unit to turn off the power of a processor, memory, etc., in the event of a detected failure thereof based on instructions provided to the bus guardian unit from other processors.
FIG. 1 illustrates in block form an overview of a computer, memory, bus system employing the bus guardian units according to the disclosure;
FIG. 2 illustrates in block form an expanded view of a single processor/scratch pad and memory module in a bus system which employs bus guardian units according to the disclosure with power switch; and
FIG. 3 is a logic diagram of a bus guardian unit according to the disclosure.
Reference should now be had to FIGS. 1 and 2 which illustrate a fault tolerant computer system to set the stage for the invention. The buses of the system are labeled A, B and C. Each bus normally comprises two data lines D1 and D2 and one sync line S (see FIG. 2).
Processors P-1A, P-1B, P-1C, P-2A, P-2B and P-2C have access to the D1 and S lines using them for data transmission and bus control. Memory units M-1A, M-1B, M-1C M-2A, M-2B and M-2C have access to only the D2 lines and use them for the data transfers from memory to the processors. All three lines of each bus operate as wired OR lines; a line being high if any unit is pulling the line high. A complete schematic of this system is shown in FIG. 1 and clock lines (not shown) well known in the art distribute clock throughout the system and are also used to clock individual data bits on the bus. A suitable clock for a fault tolerant system is disclosed on pages 17 to 22 of a Digest of Papers, The State of The Art From Device Testing to Reconfigurable Systems FTC/3, 73, International Symposium on FAULT-TOLERANT COMPUTING, June 20-21-22, Palo Alto, Calif. by Daly, Hopkins and McKenna. Copyright 1973 by the Institute of Electrical and Electronics Engineers, Inc.
The nominal clock and bus data rate may be 20 megahertz. The sync line, S, is used in conjunction with the data line D1 to indicate start and end of transaction. The processor triad, e.g., P-1A, P-1B and P-1C or P-2A, P-2B and P-2C controlling the bus may indicate an end of transaction by holding both the D1 and S high for one bit period, and then dropping the D1 line to zero while continuing to hold S high.
It continues to hold the S line high until other processor triads wish to use the bus. Those triads then raise D1 high. This S-high D1-low followed by S-high D1-high is a major sync which signals the beginning of transaction and the next eight clock periods are devoted to competition for the bus. See U.S. Pat. No. 3,710,351 issued Jan. 9, 1973, which discloses bus competition in a computer system.
Processors desiring access to the bus signal beginning of transaction and then lower the S line to zero and begin to place their triad identifications onto the D1 line, one bit at a time starting with the highest order bits. After each bit, each competing processor triad compares the D1 data read in from the bus with the signal it tried to place on the bus.
If they disagree, those processors that tried to place zero drop out of the poll. After eight bit periods, this competition spells out the eight bit code of the next triad to use the bus. A message or series of messages from the controlling processor then follows, forming the text of the transaction.
The beginning of each message is signaled by a minor sync, S-high D1-low. The first four bits of each message are used to designate the message type. The message content then follows and its format is of course dependent on the type of message.
Multiple messages need not be tightly packed as the minor sync synchronizes the transmission and reception of each message in a series. The bus may be idle between messages and the processor still retains control of the bus. A transaction is terminated normally when the controlling processor signals an end of transaction.
Memory units can transmit only one type of message, a response to a request for data. This response is transmitted on the D2 bus lines. Each message may be 33 bits long and comprises a leading 1 followed by 32 bits of data, the content of one memory word. The leading 1 bit serves to align the incoming data as these messages may have idle space between adjoining messages. Note that since the D2 line is completely independent of the D1 and S lines, processor and memory originated messages may overlap.
All receiving devices examine the first four bits of a processor originated message. If the message type indicates that the message is directed toward it, the device processes the additional trailing bits using the applicable message format for that particular message type. Specifically, messages may be directed toward a simplex processor (0000), toward a simplex memory unit (0001), toward a bus guardian unit or BGU (0010), or toward a memory triad.
Messages directed toward a memory triad, e.g., M-1A, M-1B, and M-1C are either a request for data (1000) or a store data command (0100).
The general message format is shown as follows: ##STR1##
Basically, the control of the system configuration and the manipulation of the status of individual units of the system is accomplished by means of a triad of processors directing a manipulating command toward the various units or triads in the system.
It should also be understood that additional spares i.e., processor or memory units may be included in the system and may be switched into the system to form a triad in the event that one or more of the processor or memory units were to be disabled as will be described below.
Since the above overall description serves merely as a setting for the placement of the bus guardian units of this invention, no further detail will be disclosed.
In FIGS. 1 and 2 the bus guardian units are shown at 10. In the preferred form of the invention, the bus guardian units (BGU) 10 are replicated to reduce the likelihood of a catastrophic failure of the enabling logic so as to prevent simultaneous enabling of all bus isolation gates (BIG) 11 which would thus allow a single processor to act as a triad of processors.
As shown in FIG. 2 the bus guardian units are coupled to each of the bus data lines and sync lines and include listening logic for listening to information on these lines. The bus listening logic also includes logic for recognizing and responding to legitimate commands from processor triads. Each of the bus guardian units provides control signals to limit the access of the memory or processor which it controls, to one bus at a time so that outgoing data from that memory or processor is only transmitted on one bus at a time.
In order to control the processor access to the buses by the bus guardian units 10, there are provided six bus isolator "AND" gates 11, one for each bus data line D1 and one for each sync line S, as shown in FIG. 2.
The gates 11 preferably have failure modes biased toward fail open, thus reducing the probability of catastrophic failure of this component.
The replicated bus guardian units 10 each provide inputs to bus isolator gates 11 to control the flow of data from the processor P-1A (see FIG. 2) to data line D1 and the flow of sync signals to the sync line S.
On the memory side (see memory module M-1A) only three bus isolator gates are used inasmuch as all memory units transmit only on D2 lines.
As a further feature the bus guardian units also provide a suitable mechanism for shutting down the processor/scratch pads (temporary memory or storage) as well as the memories. As a preferred feature the bus guardian units may include a fourth enabling line used to control a power switch 12 through which power is applied to the processor or memory units.
The inclusion of power switches 12 provides both a convenient mechanism for saving power as well as a backup mechanism for the bus isolator gates 11.
Reference should now be had to FIG. 3 which shows a logic diagram of a preferred form of a bus guardian unit (BGU). In particular the bus guardian unit system comprises a sixteen bit shift register shown at 15. The shift register 15 receives data from the bus data lines D1A, D1B, and D1C through a voter network 16 comprising four "NAND" gates coupled together to provide a majority consensus, D1, of the data on these three lines at the output of the voter 16.
Similarly, the voter network 17 provides at its output a signal S which represents the majority consensus of the sync signals on bus lines SA, SB and SC.
The logic circuitry 23 acts on the major and minor sync signals disclosed above. An R-S flip-flop produces an output signal which is set by major sync and reset by the first subsequent minor sync.
The fault tolerant clock receiver 21 provides at its output a 20 megahertz clock signal C. Any other clock may be used for purposes of description as the bus guardian principle is independent of the fault tolerant characteristics of the clock. An example of a fault tolerant clock receiver is shown in the magazine Digital Design Volume 3, Number 10, Oct. 1973, pages 56 and 58.
A counter shown at 20 counts clock pulses C. The counter is reset to zero in between clock pulses by logic gates 25 and 26 during minor sync pulses and during the interval between a major sync pulse and the first following minor sync pulse.
When the counter 20 reaches a value of 16 a counter-feed back line inhibits further counting and an output line enables a comparison of the message identifier bits.
An identifier decoder 18 comprising hardwired and uniquely wired AND gates 18-a, 18-b, 18-c and 18-d are provided to look at bits 1-12 and determine if the message or information on the buses is directed to this particular bus guardian unit. As shown in this case, if the bits are 110000000100, then the address comparison signal at the output of the gate 18-a will be high, and will cause gating of bits 13 to 16 into the storage flip-flops 19.
In this case the rightmost four bits indicate that the message is intended for a BGU, and the next eight bits indicate that the information is directed to this particular BGU.
Three of the bits in this storage via enable lines 19a-c are then used to enable or disable the bus isolator gates to control access of the memory or processor to a particular data line. The fourth bit of storage via one enable line 19d is used to control power to the memory or processor unit as previously discussed. The configuration of these four bits is established by the processor triad that transmitted the 16 bit message.
Normally, only one output from the three BGU enable lines coupling to the bus isolation gates (BIG) will be high, thereby restricting access from the memory or processor unit to a single bus. By extending the number of control bits and enabling lines, the number of buses or other devices which may be controlled may be extended, by providing additional hardware equivalent to that shown.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US3510844 *||Jul 27, 1966||May 5, 1970||Gen Electric||Interprocessing multicomputer systems|
|US3560935 *||Mar 15, 1968||Feb 2, 1971||Burroughs Corp||Interrupt apparatus for a modular data processing system|
|US3651473 *||Mar 27, 1970||Mar 21, 1972||Burroughs Corp||Expandable interlock exchange for multiprocessing systems|
|US3665418 *||Jul 15, 1968||May 23, 1972||Ibm||Status switching in an automatically repaired computer|
|US3680058 *||Nov 28, 1969||Jul 25, 1972||Burroughs Corp||Information processing system having free field storage for nested processes|
|US3735356 *||Sep 13, 1971||May 22, 1973||Marconi Co Ltd||Data processing arrangements having convertible majority decision voting|
|US3750110 *||Nov 24, 1971||Jul 31, 1973||Ferranti Ltd||Data transfer systems|
|US3761879 *||May 8, 1972||Sep 25, 1973||Philips Corp||Bus transport system for selection information and data|
|US3787818 *||Jun 22, 1972||Jan 22, 1974||Plessey Handel Investment Ag||Mult-processor data processing system|
|US3810114 *||Dec 29, 1972||May 7, 1974||Tokyo Shibaura Electric Co||Data processing system|
|US3876987 *||Apr 24, 1973||Apr 8, 1975||Dalton Robin Edward||Multiprocessor computer systems|
|US3882455 *||Sep 14, 1973||May 6, 1975||Gte Automatic Electric Lab Inc||Configuration control circuit for control and maintenance complex of digital communications system|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US4150428 *||Nov 18, 1974||Apr 17, 1979||Northern Electric Company Limited||Method for providing a substitute memory in a data processing system|
|US4257100 *||Sep 29, 1978||Mar 17, 1981||Fraunhofer-Gesellschaft Zur Forderung Der Angewandten Forschung E.V.||Electronic data processing system for real time data processing|
|US4276645 *||May 25, 1979||Jun 30, 1981||Le Material Telephonique||Receiver for simultaneously transmitted clock and auxiliary signals|
|US4285037 *||May 9, 1979||Aug 18, 1981||Siemens Aktiengesellschaft||Circuit arrangement for a switching system|
|US4296469 *||Nov 17, 1978||Oct 20, 1981||Motorola, Inc.||Execution unit for data processor using segmented bus structure|
|US4306286 *||Jun 29, 1979||Dec 15, 1981||International Business Machines Corporation||Logic simulation machine|
|US4321666 *||Feb 5, 1980||Mar 23, 1982||The Bendix Corporation||Fault handler for a multiple computer system|
|US4323966 *||Feb 5, 1980||Apr 6, 1982||The Bendix Corporation||Operations controller for a fault-tolerant multiple computer system|
|US4342083 *||Feb 5, 1980||Jul 27, 1982||The Bendix Corporation||Communication system for a multiple-computer system|
|US4356546 *||Feb 5, 1980||Oct 26, 1982||The Bendix Corporation||Fault-tolerant multi-computer system|
|US4366535 *||Jan 14, 1980||Dec 28, 1982||Cselt - Centro Studi E Laboratori Telecomunicazioni S.P.A.||Modular signal-processing system|
|US4503534 *||Jun 30, 1982||Mar 5, 1985||Intel Corporation||Apparatus for redundant operation of modules in a multiprocessing system|
|US4503535 *||Jun 30, 1982||Mar 5, 1985||Intel Corporation||Apparatus for recovery from failures in a multiprocessing system|
|US4514808 *||May 11, 1982||Apr 30, 1985||Tokyo Shibaura Denki Kabushiki Kaisha||Data transfer system for a data processing system provided with direct memory access units|
|US4593396 *||Oct 8, 1982||Jun 3, 1986||August Systems||Process for a fault-tolerant data processing system with error detection and resistance to fault propagation|
|US4607365 *||Nov 14, 1983||Aug 19, 1986||Tandem Computers Incorporated||Fault-tolerant communications controller system|
|US4616312 *||Feb 28, 1983||Oct 7, 1986||International Standard Electric Corporation||2-out-of-3 Selecting facility in a 3-computer system|
|US4654857 *||Aug 2, 1985||Mar 31, 1987||Stratus Computer, Inc.||Digital data processor with high reliability|
|US4656580 *||Jun 11, 1982||Apr 7, 1987||International Business Machines Corporation||Logic simulation machine|
|US4683570 *||Sep 3, 1985||Jul 28, 1987||General Electric Company||Self-checking digital fault detector for modular redundant real time clock|
|US4723242 *||Jun 27, 1986||Feb 2, 1988||Sperry Corporation||Digital adaptive voting|
|US4744024 *||Jul 23, 1984||May 10, 1988||Burroughs Corporation||Method of operating a bus in a data processing system via a repetitive three stage signal sequence|
|US4750177 *||Sep 8, 1986||Jun 7, 1988||Stratus Computer, Inc.||Digital data processor apparatus with pipelined fault tolerant bus protocol|
|US4757442 *||Jun 16, 1986||Jul 12, 1988||Nec Corporation||Re-synchronization system using common memory bus to transfer restart data from non-faulty processor to failed processor|
|US4816990 *||Nov 5, 1986||Mar 28, 1989||Stratus Computer, Inc.||Method and apparatus for fault-tolerant computer system having expandable processor section|
|US4866604 *||Aug 1, 1988||Sep 12, 1989||Stratus Computer, Inc.||Digital data processing apparatus with pipelined memory cycles|
|US4868826 *||Aug 31, 1987||Sep 19, 1989||Triplex||Fault-tolerant output circuits|
|US4926315 *||Jul 29, 1987||May 15, 1990||Stratus Computer, Inc.||Digital data processor with fault tolerant peripheral bus communications|
|US4931922 *||Jul 29, 1987||Jun 5, 1990||Stratus Computer, Inc.||Method and apparatus for monitoring peripheral device communications|
|US4965879 *||Oct 13, 1988||Oct 23, 1990||United Technologies Corporation||X-wing fly-by-wire vehicle management system|
|US4967347 *||Apr 3, 1986||Oct 30, 1990||Bh-F (Triplex) Inc.||Multiple-redundant fault detection system and related method for its use|
|US4974144 *||Jun 16, 1989||Nov 27, 1990||Stratus Computer, Inc.||Digital data processor with fault-tolerant peripheral interface|
|US4974150 *||Jun 16, 1989||Nov 27, 1990||Stratus Computer, Inc.||Fault tolerant digital data processor with improved input/output controller|
|US5022076 *||Dec 9, 1988||Jun 4, 1991||The Exchange System Limited Partnership||Redundant encryption processor arrangement for use in an electronic fund transfer network|
|US5123047 *||Jan 25, 1991||Jun 16, 1992||The Exchange System Limited Partnership||Method of updating encryption device monitor code in a multichannel data encryption system|
|US5128996 *||Dec 9, 1988||Jul 7, 1992||The Exchange System Limited Partnership||Multichannel data encryption device|
|US5146589 *||Dec 17, 1990||Sep 8, 1992||Tandem Computers Incorporated||Refresh control for dynamic memory in multiple processor system|
|US5193175 *||Mar 6, 1991||Mar 9, 1993||Tandem Computers Incorporated||Fault-tolerant computer with three independently clocked processors asynchronously executing identical code that are synchronized upon each voted access to two memory modules|
|US5203004 *||Jan 8, 1990||Apr 13, 1993||Tandem Computers Incorporated||Multi-board system having electronic keying and preventing power to improperly connected plug-in board with improperly configured diode connections|
|US5210871 *||Jul 31, 1990||May 11, 1993||The Charles Stark Draper Labroatory, Inc.||Interprocessor communication for a fault-tolerant, mixed redundancy distributed information processing system|
|US5239641 *||Feb 20, 1991||Aug 24, 1993||Tandem Computers Incorporated||Method and apparatus for synchronizing a plurality of processors|
|US5276823 *||Mar 5, 1991||Jan 4, 1994||Tandem Computers Incorporated||Fault-tolerant computer system with redesignation of peripheral processor|
|US5289589 *||Sep 10, 1990||Feb 22, 1994||International Business Machines Corporation||Automated storage library having redundant SCSI bus system|
|US5295258 *||Jan 5, 1990||Mar 15, 1994||Tandem Computers Incorporated||Fault-tolerant computer system with online recovery and reintegration of redundant components|
|US5317726 *||Jun 26, 1991||May 31, 1994||Tandem Computers Incorporated||Multiple-processor computer system with asynchronous execution of identical code streams|
|US5317752 *||Nov 16, 1992||May 31, 1994||Tandem Computers Incorporated||Fault-tolerant computer system with auto-restart after power-fall|
|US5349654 *||Feb 20, 1992||Sep 20, 1994||The Boeing Company||Fault tolerant data exchange unit|
|US5353436 *||Dec 9, 1992||Oct 4, 1994||Tandem Computers Incorporated||Method and apparatus for synchronizing a plurality of processors|
|US5384906 *||Aug 23, 1993||Jan 24, 1995||Tandem Computers Incorporated||Method and apparatus for synchronizing a plurality of processors|
|US5388242 *||Nov 24, 1992||Feb 7, 1995||Tandem Computers Incorporated||Multiprocessor system with each processor executing the same instruction sequence and hierarchical memory providing on demand page swapping|
|US5392298 *||Jul 13, 1992||Feb 21, 1995||Nec Corporation||Testing apparatus for exactly discriminating defective product from acceptable product and testing method used therein|
|US5428769 *||Mar 31, 1992||Jun 27, 1995||The Dow Chemical Company||Process control interface system having triply redundant remote field units|
|US5452441 *||Mar 30, 1994||Sep 19, 1995||At&T Corp.||System and method for on-line state restoration of one or more processors in an N module redundant voting processor system|
|US5572685 *||Mar 3, 1995||Nov 5, 1996||International Computers Limited||Computer system|
|US5583769 *||Mar 16, 1995||Dec 10, 1996||Kabushiki Kaisha Toshiba||Automatic train operation apparatus incorporating security function with improved reliability|
|US5758113 *||Mar 10, 1997||May 26, 1998||Tandem Computers Incorporated||Refresh control for dynamic memory in multiple processor system|
|US5862315 *||May 12, 1997||Jan 19, 1999||The Dow Chemical Company||Process control interface system having triply redundant remote field units|
|US5890003 *||Sep 7, 1993||Mar 30, 1999||Tandem Computers Incorporated||Interrupts between asynchronously operating CPUs in fault tolerant computer system|
|US5923830 *||May 7, 1997||Jul 13, 1999||General Dynamics Information Systems, Inc.||Non-interrupting power control for fault tolerant computer systems|
|US5970226 *||Jan 26, 1995||Oct 19, 1999||The Dow Chemical Company||Method of non-intrusive testing for a process control interface system having triply redundant remote field units|
|US6038584 *||Mar 15, 1993||Mar 14, 2000||Texas Instruments Incorporated||Synchronized MIMD multi-processing system and method of operation|
|US6061809 *||Dec 19, 1996||May 9, 2000||The Dow Chemical Company||Process control interface system having triply redundant remote field units|
|US6073251 *||Jun 9, 1997||Jun 6, 2000||Compaq Computer Corporation||Fault-tolerant computer system with online recovery and reintegration of redundant components|
|US6141769 *||May 9, 1997||Oct 31, 2000||Resilience Corporation||Triple modular redundant computer system and associated method|
|US6240526||Oct 27, 1999||May 29, 2001||Resilience Corporation||Triple modular redundant computer system|
|US6349391||Oct 27, 1999||Feb 19, 2002||Resilience Corporation||Redundant clock system and method for use in a computer|
|US6434712 *||Apr 5, 1999||Aug 13, 2002||Daimlerchrysler Aerospace Ag||Method and apparatus for fault tolerant execution of computer programs|
|US6633996||Apr 13, 2000||Oct 14, 2003||Stratus Technologies Bermuda Ltd.||Fault-tolerant maintenance bus architecture|
|US6687851||Apr 13, 2000||Feb 3, 2004||Stratus Technologies Bermuda Ltd.||Method and system for upgrading fault-tolerant systems|
|US6691257||Apr 13, 2000||Feb 10, 2004||Stratus Technologies Bermuda Ltd.||Fault-tolerant maintenance bus protocol and method for using the same|
|US6708283||Apr 13, 2000||Mar 16, 2004||Stratus Technologies, Bermuda Ltd.||System and method for operating a system with redundant peripheral bus controllers|
|US6718474||Sep 21, 2000||Apr 6, 2004||Stratus Technologies Bermuda Ltd.||Methods and apparatus for clock management based on environmental conditions|
|US6735715||Apr 13, 2000||May 11, 2004||Stratus Technologies Bermuda Ltd.||System and method for operating a SCSI bus with redundant SCSI adaptors|
|US6766413||Mar 1, 2001||Jul 20, 2004||Stratus Technologies Bermuda Ltd.||Systems and methods for caching with file-level granularity|
|US6766479||Feb 28, 2001||Jul 20, 2004||Stratus Technologies Bermuda, Ltd.||Apparatus and methods for identifying bus protocol violations|
|US6802022||Sep 18, 2000||Oct 5, 2004||Stratus Technologies Bermuda Ltd.||Maintenance of consistent, redundant mass storage images|
|US6820213||Apr 13, 2000||Nov 16, 2004||Stratus Technologies Bermuda, Ltd.||Fault-tolerant computer system with voter delay buffer|
|US6862689||Apr 12, 2001||Mar 1, 2005||Stratus Technologies Bermuda Ltd.||Method and apparatus for managing session information|
|US6874102||Mar 5, 2001||Mar 29, 2005||Stratus Technologies Bermuda Ltd.||Coordinated recalibration of high bandwidth memories in a multiprocessor computer|
|US6948010||Dec 20, 2000||Sep 20, 2005||Stratus Technologies Bermuda Ltd.||Method and apparatus for efficiently moving portions of a memory block|
|US6996750||May 31, 2001||Feb 7, 2006||Stratus Technologies Bermuda Ltd.||Methods and apparatus for computer bus error termination|
|US7065672||Mar 28, 2001||Jun 20, 2006||Stratus Technologies Bermuda Ltd.||Apparatus and methods for fault-tolerant computing using a switching fabric|
|US7502973 *||May 4, 2004||Mar 10, 2009||Robert Bosch Gmbh||Method and device for monitoring a distributed system|
|US8805593||Nov 18, 2010||Aug 12, 2014||Energy Control Technologies, Inc.||Fault tolerant analog outputs for turbo compressors|
|US20020144175 *||Mar 28, 2001||Oct 3, 2002||Long Finbarr Denis||Apparatus and methods for fault-tolerant computing using a switching fabric|
|US20050164699 *||Nov 1, 2002||Jul 28, 2005||Christopher Temple||Remote switching a communication device in a communication network|
|US20060248409 *||May 4, 2004||Nov 2, 2006||Dietmar Baumann||Method and device for monitoring a distributed system|
|EP0317472A2 *||Sep 27, 1988||May 24, 1989||International Business Machines Corporation||Logic redundancy circuit scheme|
|EP0952520A2 *||Mar 5, 1999||Oct 27, 1999||DaimlerChrysler Aerospace AG||Device for fault tolerant execution of programs|
|WO1984003158A1 *||Feb 9, 1983||Aug 16, 1984||Ibm||A method for achieving multiple processor agreement optimized for no faults|
|WO1989002124A1 *||Aug 19, 1988||Mar 9, 1989||Triplex||Fault-tolerant output circuits|
|WO2000014636A2 *||Aug 12, 1999||Mar 16, 2000||Daimler Chrysler Ag||Device and method for coupling redundant electronic circuits via redundant buses without error propagation|
|U.S. Classification||714/12, 714/E11.069, 714/797, 714/820|
|International Classification||G06F13/42, G06F13/374, G06F11/20, G06F11/18|
|Cooperative Classification||G06F11/184, G06F11/2007, G06F13/374, G06F13/4217, G06F11/181, G06F11/202|
|European Classification||G06F13/42C1S, G06F13/374, G06F11/18E, G06F11/18N2, G06F11/20P, G06F11/20C4|