Browse Prior Art Database

Application for interface reporting and configuration updates

IP.com Disclosure Number: IPCOM000010433D
Original Publication Date: 2002-Dec-02
Included in the Prior Art Database: 2002-Dec-02
Document File: 9 page(s) / 64K

Publishing Venue

Motorola

Related People

Michael Landers: AUTHOR

Abstract

This paper describes a software application that can be used to automatically report on the configuration of elements in a network and can also be used to make changes to network elements when their configuration is incorrect.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 40% of the total text.

Application for interface reporting and configuration updates

by Michael Landers

Abstract

This paper describes a software application that can be used to automatically report on the configuration� of elements in a network and can also be used to make changes to network elements when their configuration is incorrect.

Introduction

In today’s telecom networks many network elements communicate via standardised interfaces. These interfaces are configured in the network elements by the network operators. Typically an operator will have equipment from many vendors and will have separate element managers to configure those network elements. A network operator may even have separate element managers from the same vendor to configure separate network element types from the vendor. This paper outlines a network management application that can assist the network operator to ensure that all network elements are configured correctly.

Problem(s) To Be Solved

When network elements are being configured to communicate with one another, via a standardised interface, very often the same configuration data must be maintained in the separate network elements. An example is the Gb interface in GPRS (General Packet Radio Service). The virtual circuits making up this interface must be configured in the SGSN (Serving GPRS Support Node) and in the PCU (Packet Control Unit) elements. The operator will have one element manager for the packet switched core network (which includes the SGSN) and one or more element managers for the radio access network (which includes the PCU).

In order to make sure that the same configuration data is present on the network elements supporting the interface, the operator must use the element managers to retrieve the configuration from the different network elements and then use some custom application to compare the data. Similarly to change the configuration, the operator must generate updates in a format which will be accepted by the element managers. This format is usually different from element manager to element manager.

This results in a time-consuming, error-prone and non-automated configuration management task for the network operator.

This situation is illustrated in Figures 1 and 2. Figure 1 shows how a network operator will use different element managers to retrieve configuration data from network elements communicating via a standardised interface. In order to compare the configuration data, the operator must implement a custom application. Similarly in order to update the network element configuration, the operator’s custom application must generate configuration data in a format acceptable by the various element managers involved. This is shown in Figure 2.

Proposed Solution to the Problem(s)

The idea is to provide an application for the customer which can be configured by them to support any standard interface from any network element. Using this application, the operator will be able to

-          read any interface configuration...