IP Library Granted Patent US 7,085,830
Granted Patent B1
US 7,085,830 · App. 10/041,783 · Granted Aug 1, 2006

System and method to manage inconsistency problems between network management systems and network elements

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,085,830
App. No.
10/041,783
Granted
Aug 1, 2006
Kind
B1
Abstract

A system and method are provided for managing configuration inconsistencies between a network management system (NMS) and network elements (NEs). In one example, the system includes a user interface, which includes an object field configured to identify database objects of the network management system, wherein each database object corresponds to a network element; a network device field configured to identify a top level network device that contains the network element; a status field configured to display a database object state, wherein the database object state represents a relationship between the database object configuration and the network element configuration; and an input mechanism configured to issue a command to edit one of network element values and database object values.

Claims (52)

1. A system for managing configuration inconsistencies between a network management system (NMS) and network elements (NEs), the system comprising:

a user-interface including:

an object field configured to identify database objects of the network management system, wherein each database object corresponds to a network element;

a status field configured to display a database object state, wherein the database object state represents a relationship between a database object configuration and a network element configuration, wherein if an inconsistency is found between the database object configuration and the network element configuration, the inconsistency is shown as one of a plurality of configuration inconsistency types, the plurality of configuration inconsistency types including:

a first inconsistency type, meaning an inconsistency exists between the database object configuration and the network element configuration;

a second inconsistency type, meaning no network element exists for a selected database object; and

a third inconsistency type, meaning that a network element exists, but that no corresponding database object exists;

one or more selectable input mechanisms, each input mechanism performing a different action, wherein the inconsistency type shown is used to determine an input mechanism that, when selected by the user, performs an action that automatically resolves the inconsistency by editing the database object configuration and/or the network element configuration.

2. The system of claim 1 , wherein network element values define the configuration of the network element, and

wherein database object values define the configuration of the database object.

3. The system of claim 1 , wherein a state of the database object is;

normal, meaning both the database object and the network element have exactly the same configuration.

4. The system of claim 2 , wherein the inconsistency type is the first inconsistency type, and the input mechanism is configured to issue a command to have the network element acquire the database object values.

5. The system of claim 2 , wherein the inconsistency type is the first inconsistency type and the input mechanism is configured to issue a command to have the database object acquire the network element values.

6. The system of claim 2 , wherein the state of the inconsistency type is the second inconsistency type, and the input mechanism is configured to issue a command to create a network element having the database object values.

7. The system of claim 2 , wherein the state of the inconsistency type is the third inconsistency type, and the input mechanism is configured to issue a command to create a database object having the network element values.

8. A method for managing attribute inconsistencies between a network management system (NMS) and a network element (NE), the method comprising:

providing an object field in a user interface to identify database objects of the network management system, wherein each database object corresponds to a network element;

providing a status field configured to display a database object state, wherein the database object state represents a relationship between a database object configuration and a network element configuration;

if an inconsistency is found between the database object configuration and the network element configuration, displaying the inconsistency as one of a plurality of configuration inconsistency types, the plurality of configuration inconsistency types including:

a first inconsistency type, meaning an inconsistency exists between the database object configuration and the network element configuration;

a second inconsistency type, meaning no network element exists for a selected database object; and

a third inconsistency type, meaning that a network element exists, but that no corresponding database object exists;

receiving a selection of one or more input mechanisms, wherein each input mechanism performing a different action, wherein the inconsistency type shown is used to determine an input mechanism that performs an action that automatically resolves the inconsistency by editing the database object configuration and/or the network element configuration.

9. The method of claim 8 , wherein network element values define the configuration of the network element, and wherein database object values define the configuration of the database object.

10. The method of claim 8 , further comprising providing in the object field a state of the database object as being:

normal, meaning both the database object and the network element have exactly the same configuration.

11. The method of claim 9 , wherein the inconsistency type is the first inconsistency type, the method further comprising receiving a selection of an input mechanism to issue a command to have the network element acquire the database object values.

12. The method of claim 9 , wherein the inconsistency type is the first inconsistency type, the method further comprising receiving a selection of an input mechanism to issue a command to have the database object acquire the network element values.

13. The method of claim 9 , wherein the state of the inconsistency type is the second inconsistency type, the method further comprising receiving a selection of an input mechanism to issue a command to create a network element having the database object values.

14. The method of claim 9 , wherein the state of the inconsistency type is the third inconsistency type, the method further comprising receiving a selection of an input mechanism to issue a command to create a database object having the network element values.

15. The method of claim 8 , further comprising:

resynchronizing the network management system and the network element; and

carrying out the command to edit one of the network element values and the database object values.

16. A computer-readable medium carrying one or more sequences of one or more instructions for managing attribute inconsistencies between a network management system (NMS) and a network element (NE), the one or more sequences of one or more instructions including instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of:

providing an object field in a user interface to identify database objects of the network management system, wherein each database object corresponds to a network element;

providing an agent field configured to identify the network element;

providing a status field configured to display a database object state, wherein the database object state represents a relationship between a database object configuration and a network element configuration;

if an inconsistency is found between the database object configuration and the network element configuration, displaying the inconsistency as one of a plurality of configuration inconsistency types, the plurality of configuration inconsistency types including:

a first inconsistency type, meaning an inconsistency exists between the database object configuration and the network element configuration;

a second inconsistency type, meaning no network element exists for a selected database object; and

a third inconsistency type, meaning that a network element exists, but that no corresponding database object exists;

receiving a selection of one or more input mechanisms, wherein each input mechanism performing a different action, wherein the inconsistency type shown is used to determine an input mechanism that performs an action that automatically resolves the inconsistency by editing the database object configuration and/or the network element configuration.

17. The computer-readable medium of claim 16 , wherein network element values define the configuration of the network element, and wherein the database object values define the configuration of the database object.

18. The computer-readable medium of claim 16 , wherein the instructions further cause the processor to carry out the step of providing in the object field a state of the database object as being:

normal, meaning both the database object and the network element have exactly the same configuration.

19. The computer-readable medium of claim 17 , wherein the inconsistency type is the first inconsistency type, and wherein the instructions further cause the processor to issue a command to have the network element acquire the database object values.

20. The computer-readable medium of claim 17 , wherein the inconsistency type is the first inconsistency type, and wherein the instructions further cause the processor to issue a command to have the database object acquire the network element values.

21. The computer-readable medium of claim 17 , wherein the inconsistency type is the second inconsistency type, and wherein the instructions further cause the processor to issue a command to create a network element having the database object values.

22. The computer-readable medium of claim 17 , wherein the inconsistency type is the third inconsistency type, and wherein the instructions farther cause the processor to issue a command to create a database object having the network element values.

23. The computer-readable medium of claim 16 , wherein the instructions further cause the processor to carry out the steps of:

resyncing the network management system and the network element; and carrying out the command to edit one of the network element values and the database object values.

Assignments (8)
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2024
From: CITIZENS BANK, N.A.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 067822/0433 →
TERMINATION AND RELEASE OF FIRST SUPPLEMENT OT PATENT SECURITY AGREEMENT AT R/F 049035/0939 Recorded Dec 6, 2021
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 058740/0265 →
SECURITY INTEREST Recorded Mar 3, 2020
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 052076/0905 →
CORRECTIVE ASSIGNMENT TO CORRECT THE SCHEDULE PREVIOUSLY RECORDED ON REEL 049035 FRAME 0939. ASSIGNOR(S) HEREBY CONFIRMS THE FIRST SUPPLEMENT TO PATENT SECURITY AGREEMENT. Recorded Aug 22, 2019
From: GENBAND US LLC; RIBBON COMMUNICATIONS OPERATING COMPANY, INC., FORMERLY KNOWN AS SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 050705/0001 →
FIRST SUPPLEMENT TO SECURITY AGREEMENT Recorded Apr 30, 2019
From: GENBAND US LLC; RIBBON COMMUNICATIONS OPERATING COMPANY, INC., FORMERLY KNOWN AS SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 049035/0939 →
CHANGE OF NAME Recorded Jan 16, 2019
From: SONUS NETWORKS, INC.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
Reel/Frame 048078/0036 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 18, 2017
From: NETWORK EQUIPMENT TECHNOLOGIES, INC.
To: SONUS NETWORKS, INC.
Reel/Frame 044904/0829 →
RELEASE OF SECURITY INTEREST Recorded Oct 24, 2017
From: BANK OF AMERICA, N.A.
To: SONUS NETWORKS, INC.; SONUS FEDERAL, INC.; NETWORK EQUIPMENT TECHNOLOGIES, INC.; PERFORMANCE TECHNOLOGIES, INCORPORATED; SONUS INTERNATIONAL, INC.; TAQUA, INC.
Reel/Frame 044283/0361 →