Communication between an application and a network element

• US 20020188719A1
• Filed: 04/05/2002
• Published: 12/12/2002
• Est. Priority Date: 05/29/2001
• Status: Abandoned Application

• Current Assignee: Alcatel SA (Nokia Corporation)
• Original Assignee: Alcatel SA (Nokia Corporation)
• Inventors: Pham, Hien-Thong, Batsleer, Claudine, Chantrain, Dominique
• Application Number:
  US10/116,039
• Publication Number:
  US 20020188719A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• 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: H04Q 3/0095 Specification, development or application of network management software, e.g. software re-use

Abstract

Network elements (NE) of a telecommunications network and an application platform (SP), which provides value-added services on top of the network, communicate with each other by means of triggers (T) and handles (H). Triggers (T) are notifications containing information to be sent by a network element to the application platform (SL) upon occurrence of predefined events and handles (H) are commands to be sent by the application platform (SL) requesting execution of predefined actions at said network element (NE). A network element (NE) includes a management information base (MIB) containing managed objects, which describe variables and parameters accessible by a network management system (NMS) to control and monitor the network element (NE). In order to allow systematic interrogation of the triggers and handles interface of a network element (NE), its management information base (MIB) stores additional managed objects which describe the triggers (T) and handles (H) supported by said network element (NE). A software module (NID), which is part of the application platform actively interrogates the network element (NE) to find out which triggers (T) and handles (H) the network element (NE) supports. The module sends requests to the network element and stores in a data model (THB) information on the interface received back from the network element (NE).

Claims

1. A management information base for a network element, said management information base being a database comprising managed objects describing variables and parameters accessible by a network management system to control and monitor said network element, wherein the management information base further comprising additional objects describing triggers and handles supported by said network element, said triggers being notifications containing information to be sent by said network element to an application upon occurrence of predefined events and said handles being commands to be sent by an application requesting execution of predefined actions at said network element.

2. A network element comprising a management information base being a database comprising managed objects describing variables and parameters accessible by a network management system to configure and control the network element, wherein the management information base further comprising additional objects describing triggers and handles supported by said network element, said triggers being notifications containing information to be sent by said network element to an application upon occurrence of predefined events and said handles being commands to be sent by an application requesting execution of predefined actions at said network element.

3. A network element according to claim 2, further comprising at least one software agent adapted to access and maintain said additional objects and serving to make upon request from an application the information on the supported triggers and handles available to the application.

4. A software module as part of an application, said software module being adapted to interrogate an interface of a network element to find out which triggers and handles the network element supports by sending requests to the network element and storing in a data model information on the interface received back from the network element, said triggers being notifications containing information to be sent by said network element to an application upon occurrence of predefined events and said handles being commands to be sent by an application requesting execution of predefined actions at said network element.

5. A software module as claimed in claim 4 using Simple Network Management Protocol to send said requests to a network element.

6. A software module as claimed in claim 4, wherein said requests comprising at least one request from the list

get list of supported triggers and handles;

for a given trigger, get the triggering event; and

for a given trigger or handle, get list of parameters supported.

7. An application comprising a software module adapted to interrogate an interface of a network element to find out which triggers and handles the network element supports by sending requests to the network element and storing in a data model information on the interface received back from the network element, said triggers being notifications containing information to be sent by said network element to an application upon occurrence of predefined events and said handles being commands to be sent by the application requesting execution of predefined actions at said network element.

8. A method of interrogating a network element by an application to find out which triggers and handles the network element supports, said triggers being notifications containing information to be sent by said network element to an application upon occurrence of predefined events and said handles being commands to be sent by an application requesting execution of predefined actions at said network element, said method comprising the steps of

sending at least one request to the network element and

storing in a data model information on the interface received back from the network element.

9. A method according to claim 8, further comprising the steps of

upon reception of the request at the network element, accessing managed objects to retrieve the requested information, said managed object being stored in a management information base in the network element and describing triggers and handles supported by said network element, and

sending the retrieved information back to the application that initiated the request.

10. A method according to claim 8, wherein said at least one request being one from the list

get list of supported triggers and handles;

for a given trigger, get the triggering event; and

for a given trigger or handle, get list of parameters supported.