Asynchronous object oriented configuration control system for highly reliable distributed systems

• US 6,493,323 B1
• Filed: 05/14/1999
• Issued: 12/10/2002
• Est. Priority Date: 05/14/1999
• Status: Expired due to Term

• Current Assignee: WSOU Investments, LLC (WSOU Holdings, LLC)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Dobrowolski, Gregory Joseph, McKiou, Kevin Wayne
• Primary Examiner(s): NGO, RICKY QUOC
• Application Number:
  US09/312,747
• Time in Patent Office: 1,306 Days
• Field of Search: 370/252, 370/253, 370/254, 370/255, 370/256, 370/257, 370/229, 370/400, 370/465, 370/466, 370/467, 370/469, 709/220-221, 709/222, 709/223, 709/224, 709/225, 709/226, 709/230, 709/248, 709/249, 709/311
• US Class Current: 370/254
• CPC Class Codes: H04L 41/022 Multivendor or multi-standard integration
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/052 using standardised network management architectures, e.g. telecommunication management network [TMN] or unified network management architecture [UNMA]
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/0836 to enhance reliability, e.g. reduce downtime

Abstract

The configuration control system is implemented in an environment of multiple hardware platforms and operating systems and can be used to control hardware, software, data and system abstractions. The configuration control system gives the appearance of a unified maintenance environment even though it is controlling hardware and software from many vendors with multiple maintenance environments. It is designed to control the configuration of any system where there are dependencies among subsystems and loss of a subsystem has the potential to interrupt service. The maintenance configuration control protocol unifies Configuration Control to allow any subsystem to communicate with any other subsystem and to the user interface using a common messaging interface. It creates a common state model, relationship model, behavior model and request/response messaging interface for all subsystems whether they are hardware, software, or an abstraction. Furthermore, the maintenance configuration control protocol permits distributed maintenance which is data-driven. That is, it does not depend on a central intelligence to make Configuration Control decisions. Each subsystem is empowered to approve/disapprove a maintenance request and execute it autonomously based on its own data. That data includes its state and its relationships to other subsystems. Because each subsystem is autonomous, it is possible to have many concurrent configuration control requests executing in parallel. Race conditions and conflicts are handled by the common software representing the subsystem.

Claims

1. A method of operating a configuration control system for presenting a unified maintenance environment in an environment comprising a plurality of subsystems which are implemented in at least one of multiple hardware platforms and multiple operating systems, comprising the steps of:

operating a configuration control interface in each of said plurlaity of subsystems, which configuration control interface provides a common maintenance request interface, state model and behavior and operates asynchronously with respect to others of said configuration control interface in each of said plurlaity of subsystems;

assigning each of said plurality of subsystems its own logical address for messaging; and

exchanging messages among said configuration control interfaces installed in each of said plurlaity of subsystems.

2. The method of operating a configuration control system of claim 1 wherein said step of operating a configuration control interface comprises:

providing an interface to the underlying resources for other frameworks contained in said plurality of subsystems.

3. The method of operating a configuration control system of claim 2 wherein said step of operating a configuration control interface further comprises:

performing the steps of adding, deleting, setting, reporting the maintenance state of an associated one of said plurality of subsystems.

4. The method of operating a configuration control system of claim 3 wherein said step of performing comprises:

determining maintenance states which represent the presence and operational condition of said associated one of said plurality of subsystems.

5. The method of operating a configuration control system of claim 3 wherein said step of performing comprises:

implementing actions to initiate the transitions through a plurlaity of states of said associated one of said plurality of subsystems.

6. The method of operating a configuration control system of claim 3 wherein said step of performing comprises:

implementing relationships to define how said configuration control interface in each of said plurlaity of subsystems interact with each other.

7. The method of operating a configuration control system of claim 3 wherein said step of performing comprises:

executing a plurality of concurrent configuration control requests in parallel.

8. The method of operating a configuration control system of claim 2 wherein said step of providing an interface comprises:

creating interfaces and dependencies between subsystems which have different notions of state, relationships, behavior and request interfaces.

9. A configuration control system for presenting a unified maintenance environment in an environment comprising a plurality of subsystems which are implemented in at least one of multiple hardware platforms and multiple operating systems, comprising:

configuration control interface means, located in each of said plurlaity of subsystems, which configuration control interface means provides a common maintenance request interface, state model and behavior and operates asynchronously with respect to others of said configuration control interface in each of said plurlaity of subsystems;

means for assigning each of said plurality of subsystems its own logical address for messaging; and

means for exchanging messages among said configuration control interface means installed in each of said plurlaity of subsystems.

10. The configuration control system of claim 9 wherein said configuration control interface means comprises:

means for providing an interface to the underlying resources for other frameworks contained in said plurality of subsystems.

11. The configuration control system of claim 10 wherein said configuration control interface means further comprises:

means for performing the steps of adding, deleting, setting, reporting the maintenance state of an associated one of said plurality of subsystems.

12. The configuration control system of claim 11 wherein said means for performing comprises:

means for determining maintenance states which represent the presence and operational condition of said associated one of said plurality of subsystems.

13. The configuration control system of claim 11 wherein said means for performing comprises:

means for implementing actions to initiate the transitions through a plurlaity of states of said associated one of said plurality of subsystems.

14. The configuration control system of claim 11 wherein said means for performing comprises:

means for implementing relationships to define how said configuration control interface in each of said plurlaity of subsystems interact with each other.

15. The configuration control system of claim 11 wherein said means for performing comprises:

means for executing a plurality of concurrent configuration control requests in parallel.

16. The configuration control system of claim 10 wherein said means for providing an interface comprises:

means for creating interfaces and dependencies between subsystems which have different notions of state, relationships, behavior and request interfaces.