Method and apparatus for high availability distributed processing across independent networked computer fault groups

• US 7,219,254 B2
• Filed: 03/19/2003
• Issued: 05/15/2007
• Est. Priority Date: 03/19/2003
• Status: Active Grant

• Current Assignee: Nokia of America Corporation (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Rathunde, Dale Frank, Rog, Jerome Edward, Witt, William E.
• Primary Examiner(s): Beausoliel; Robert
• Assistant Examiner(s): Ehne; Charles
• Application Number:
  US10/392,474
• Publication Number:
  US 20040199804A1
• Time in Patent Office: 1,518 Days
• Field of Search: 714/4, 714 10- 13
• US Class Current: 714/1
• CPC Class Codes: G06F 11/0712 in a virtual computing platform, e.g. logically partitioned systems
• CPC Class Codes: G06F 11/0724 in a multiprocessor or a multi-core unit multiprocessors per se G06F15/80
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/1415 at system level
• CPC Class Codes: G06F 11/2002 where interconnections or communication control functionality are redundant flexible arrangements for bus networks involving redundancy H04L12/40176
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A plurality of local network groups of computers (102) are coupled together by a network (104). Independent processing systems that execute a single operating system are coupled together by a network (220) to form the local network groups. The independent processing systems may have more than one CPU (202). One or more of the independent processing systems may share power, cooling and a housing, thereby forming a common fault processor group (200). An application is written to execute across multiple independent processing systems and common fault processor groups. That is, the application runs in many instances that each run on independent processing systems. The multiple instances of the application provide some measure of high availability by using N+K sparing or the like. The application is for example, call processing or radio control. A processor notification list (304) keeps track of the independent processing systems that cooperatively provide an application. The independent processing systems monitor state information for independent processing systems on its processor notification lists. Also, the independent processing systems exchange messages periodically with independent processing systems on its processor notification list. The failure to receive a message is noted as a failure that requires recovery.

Multiple high availability software systems are permitted to coexist under a single operating system by virtue of a new software layer that coordinates initialization and requires registration of all high availability software.

Claims

1. A high availability processing system comprising:

a plurality of independent processing systems coupled together via a network, each independent processing system including;

an operating system;

a process management component running under the operating system;

a plurality of high availability subsystems interacting with the process management system;

wherein the process management system maintains a number indicating a number of high availability subsystems that are available to run on the each independent processing system; and

wherein the process management system permits the independent processing system to operate if the plurality of high availability subsystems are operational.

2. The apparatus of claim 1 wherein the number indicating the number of high availability subsystems is maintained in non volatile storage such that the number is maintained even when the independent processing system is not operating.

3. The apparatus of claim 2 wherein the number indicating the number of high availability subsystems is maintained in non-volatile RAM.

4. The apparatus of claim 1 wherein the number indicating the number of high availability subsystems is updated as a result of high availability subsystem being taken out of service.

5. A method for coordinating among multiple high availability systems running on a processor, the method comprising the steps of:

initiating operation of an operating system on the processor;

initiating operation of a process management system;

determining whether the operating systems reaches an active operational state;

determining a number of previously registered high availability systems;

determining whether the number of previously registered high availability systems have indicated their availability for processing within a predetermined time; and

if the number of previously registered high availability systems have indicated their availability for processing within the predetermined time, then allowing the process management system to obtain an active state.

6. The method of claim 5 further comprising the step of:

if less than the number of previously registered high availability systems have indicated their availability for processing within the predetermined time, then rebooting or resetting the processor.

7. The method of claim 6 wherein the step of rebooting or resetting the processor is repeated only for a predetermined number of times, if less than the number of previously registered high availability systems indicates their availability for processing.

8. The method of claim of claim 5 further comprising the step of updating the number of previously registered high availability systems while the process management system is active in response to adding or removing a high availability system.

9. The method of claim 5 wherein the number of previously registered high availability systems is at least two.