Telecommunications network management system interface

• US 6,718,377 B1
• Filed: 03/15/2000
• Issued: 04/06/2004
• Est. Priority Date: 08/13/1999
• Status: Expired due to Term

• Current Assignee: WSOU Investments, LLC (WSOU Holdings, LLC)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: O'Riordan, Mark Vincent, Bischoff, Timothy W.
• Primary Examiner(s): Coulter, Kenneth R.
• Assistant Examiner(s): Nguyen, Hai V.
• Application Number:
  US09/526,011
• Time in Patent Office: 1,483 Days
• Field of Search: 709/203, 709/220, 709/223, 709/315, 709/318, 707/103, 379/230
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0226 Mapping or translating multiple network management protocols
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A network includes an operations support system (20) for managing one or more network elements (40), and an interface (10) between the operations support system (20) and each network element (40). The interface (10) includes a network element side mediator object (14) and a corresponding operations support side proxy mediator object (14p). During initialization of the interface (10), method calls from the proxy mediator object (14p) to the mediator object (14) are employed by the operations support system (20) to obtain a list of data tables supported by the network element (40). The interface (10) also includes a network element side interface object (12) and a corresponding operations support system side proxy interface object (12p). In this case, during initialization of the interface (10), method calls from the proxy interface object (12p) to the interface object (12) are employed by the operations support system (20) to obtain a list of attributes for each data table listed. Preferably, the data tables passed across the interface (10) are carried in one of a finite number of distinct well defined containers, each container carrying data tables having a set of common characteristics. In this manner, a standarized extensible interface (10) is achieved.

Claims

1. A network comprising:

an operations support system for managing one or more network elements; and

,

an interface between the operations support system and each network element, said interface including;

a network element side mediator object and a corresponding operations support side proxy mediator object, wherein during initialization of the interface, method calls from the proxy mediator object to the mediator object are employed by the operations support system to obtain a list of data tables supported by the network element; and

,

a network element side interface object and a corresponding operations support system side proxy interface object, wherein during initialization of the interface, method calls from the proxy interface object to the interface object are employed by the operations support system to obtain a list of attributes for each data table listed.

2. The network according to claim 1, wherein the network is a communications network.

3. The network according to claim 2, wherein at least one of the network elements is a communications device.

4. The network according to claim 1, said network further comprising:

an element management system residing between the operations support system and one or more of the network elements such that the interface is between the operations support system and the element management system, said element management system incorporating the mediator object and a number of corresponding interface objects for each network element associated with the element management system.

5. The network according to claim 4, wherein during initialization of the interface, method calls from the proxy interface object to the mediator object are employed by the operations support system to obtain a list of the network elements associated with the element management system.

6. The network according to claim 1, wherein the proxy mediation object and each proxy interface object have an associated event gateway object through which the proxy mediation and interface objects, respectively, are notified of events from their corresponding mediation and interface objects.

7. The network according to claim 1, wherein the data tables supported by each network element are dynamically described via acquisition of the list of data tables and each data table'"'"'s list of attributes.

8. The network according to claim 1, wherein for at least one network element, the mediator object and network element'"'"'s associated interface object are incorporated in the network element.

9. The network according to claim 1, wherein data tables passed across the interface are carried in one of a finite number of distinct well defined containers, each container carrying data tables having a set of common characteristics.

10. The network according to claim 9, wherein the containers have predetermined handling instructions associated therewith.

11. The network according to claim 9, wherein the list of data tables includes an identification of which container type each data table is carried in.

12. In a network having an operations support system for managing one or more network elements, an interface between the operations support system and each network element, said interface including:

a network element side mediator object and a corresponding operations support side proxy mediator object, wherein during initialization of the interface, method calls from the proxy mediator object to the mediator object are employed by the operations support system to obtain a list of data tables supported by the network element; and

,

a network element side interface object and a corresponding operations support system side proxy interface object, wherein during initialization of the interface, method calls from the proxy interface object to the interface object are employed by the operations support system to obtain a list of attributes for each data table listed.

13. In a network, a method of interfacing an operations support system with network elements managed thereby, wherein the method comprises the steps of:

(a) defining a number of different container objects, each container object being used with a distinct data type having common characteristics;

(b) initializing the interface between the operations support system and the network elements, said initialization including dynamically describing data tables supported by the network elements, wherein the description includes an identification of the container objects each data table is associated with; and

,

(c) passing data tables between the operations support system and the network elements in their associated container objects.

14. The method according to claim 13, wherein step (b) comprises:

communicating to the operations support system a list of network elements;

communicating to the operations support system a list of the data tables supported for each network element listed; and

,

communicating to the operations support system a list of the attributes for each of the data tables listed.

15. The method according to claim 14, wherein the list of the data tables supported includes the identification of the container objects each data table is associated with.

16. The method according to claim 14, wherein step (b) further comprises:

determining from the list of data tables supported for each network element, which, if any, are not supported by the operations support system;

creating a modified list by removing from the list of data tables supported for each network element those that are not supported by the operations support system; and

,

communicating the modified list back to the network elements.

17. The method according to claim 13, wherein step (b) further comprises:

activating the interface for selected network elements, wherein communications with the operations support system is disabled for those network elements that do not have the interface activated.

18. The method according to claim 13, wherein step (b) further comprises:

populating selected data table supported by the network elements with reference data.