Methods and systems for autonomously managing a network

• US 20050097146A1
• Filed: 08/23/2004
• Published: 05/05/2005
• Est. Priority Date: 08/21/2003
• Status: Abandoned Application

• Current Assignee: Trustees Of Columbia University In The City Of New York (Columbia University)
• Original Assignee: Trustees Of Columbia University In The City Of New York (Columbia University)
• Inventors: Konstantinou, Alexander V., Yemeni, Yechiam
• Application Number:
  US10/925,557
• Publication Number:
  US 20050097146A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24564 Applying rules; Deductive queries
• 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/0803 Configuration setting
• CPC Class Codes: H04L 41/0823 characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for optimising operational conditions of wireless networks H04W24/02
• CPC Class Codes: H04L 41/0866 Checking the configuration

Abstract

Methods and systems for autonomously managing computer networks are provided. In a preferred embodiment of the invention, management functions are organized in a novel two-layer peer-to-peer (P2P) architecture. The bottom layer organizes management information in a unified object-relationship model, that is instantiated in a distributed transactional object repository. The top layer unifies the traditional roles of managers and elements into a single autonomic management peering layer. Autonomic elements use the repository as a primary management repository, and effect autonomic behavior in terms of transactions over the shared model state. A novel autonomic policy model and language, Object Spreadsheet Language (OSL), in the form of acyclic spreadsheet change propagation rules, and declarative constraints is also provided.

Claims

1. A method for autonomously managing a network, comprising:

automatically detecting the identity and connection of objects in the network;

binding as an object-relationship model, a plurality of rules based upon the detected identity and connection of objects in the network, wherein the rules specify how a second configuration setting is to be changed based upon at least a change in a first configuration setting;

validating the at least one rule to prevent errors when the rule is being used to change the second configuration setting; and

automatically detecting a change in at least a first configuration setting in the network, and changing at least a second configuration setting based on the object-relationship model.

2. The method of claim 1, further comprising selecting the at least one rule from a library of rules.

3. The method of claim 2, wherein selecting the at least one rule from the library of rules is based upon the object to which the rule is to be related.

4. The method of claim 1, wherein the at least one rule is implemented using a non-Turing-complete instruction set.

5. The method of claim 1, wherein the validation is performed statically at design time.

6. The method of claim 1, wherein the validation prevents loops in the at least one rule.

7. The method of claim 6, wherein the validation prevents loops in the at least one rule based upon analyzing a triggering graph.

8. The method of claim 1, wherein the validation prevents ambiguity in the at least one rule.

9. The method of claim 8, wherein the validation prevents ambiguity in the at least one rule by preventing multiple assignments to the same configuration setting.

10. The method of claim 1, further comprising reversing the change to the second configuration setting.

11. A system for autonomously managing a network, comprising:

a processor that automatically detects the identity and connection of objects in the network, binds as an object-relationship model, a plurality of rules based upon the detected identity and connection of objects in the network, wherein the rules specify how a second configuration setting is to be changed based upon at least a change in a first configuration setting, validates the at least one rule to prevent errors when the rule is being used to change the second configuration setting, and automatically detects a change in at least a first configuration setting in the network, and changes at least a second configuration setting based on the object-relationship model.

12. The system of claim 11, wherein the processor selects the at least one rule from a library of rules.

13. The system of claim 12, wherein the processor selects the at least one rule from the library of rules is based upon the object to which the rule is to be related.

14. The system of claim 11, where in the at least one rule is implemented using a non-Turing-complete instruction set.

18. The system of claim 11, wherein the validation prevents ambiguity in the at least one rule.

19. The system of claim 18, wherein the validation prevents ambiguity in the at least one rule by preventing multiple assignments to the same configuration setting.

20. The system of claim 11, wherein the processor also reverses the change to the second configuration setting.

15. The system of claim 21, wherein the validation is performed statically at design time.

16. The system of claim 21, wherein the validation prevents loops in the at least one rule.

17. The system of claim 16, wherein the validation prevents loops in the at least one rule based upon analyzing a triggering graph.