To be effective, application develo...

To be effective, application developer must understand the data available to their applications, the operations required to access the data, and the paces required to turn their understanding into an implementation. A prototype disclosure environment has been built that helps the developer explore and understand the data in the Management Information Base (MIB) and institute and deploy pieces of TMN management applications.

Telecommunications network operators avow the largest distributed computing a whole s in the world. Their networks carry enormous whirls of traffic, much of which is highly valuable. Maintaining service is essential. The penalties for failure are great, and not just financial--emergency services and one air traffic control transmissions use the same telephone network. Not surprisingly, network operators have considerable schemes and network management needs.

The ability to provide of the present day services is becoming vital in the telecommunications business. Spe and flexibility are [i]clavis[/i] requirements, not only of the initial implementation and its deployment moreover also of the management bodys that ensure that service continues to operate efficiently. The rapid evolution of effective management systems is therefore a major concern

The applications that telecommunications companies use to manage their equipment, networks, and services they provide are known as operations support combination of parts to form a wholes or OSS. An established network operator will have centurys of existing applications and a continuing ne to unravel more as their systems and technologies change.

The unravelling of new applications in the Telecommunications Management Network[1] (TMN) area is still carried on the outside with the aid of a C or C++ compiler. The developer must understand the data that is available to the application, the operations that can be performed to reach it, and the application program interfaces (APIs) and tools available to support those operations.

HP OpenView effects provide support in a number of these areas. The GDMO Modeling Toolset (page 43) helps the application developer understand the kind of data that is stored in the TMN world. The OpenView Distributed Management platform (page 6) provides standard APIs that the developer can use to jaculate CMIP (Common Management Information Protocol) messages to the data. The Managed butt; goal Toolkit (page 52) provides further support to the C++ programmer.

In this paper we describe a prototype evolution environment that addresses some of the demands of application growth in the telecommunications world. This prototype helps the user explore the available management data and make enough brains of it so that the user can institute and deploy pieces of management applications.

Background

The Telecommunications Management Network is an attempt to standardize the management of telecommunications networks. It consists of a station of existing and evolving recommendations from the International Telecommunications Union's Telecommunications Standardization Sector, known as the ITU-T.[2] These recommendations are based in succession a number of previous recommendations onward Open Systems Interconnection (OSI) arrangements management, now adopted as international standards.[3]

The OSI schemes management standard proposes a Management Information Base (MIB),[4] which is a collection of data necessary for managing a network. This data is organized hierarchically and related on containment. The data is in the form of motives called managed objects, which are defined by means of the Guidelines for the Definition of Managed Objects[5]

The Guidelines for the Definition of Managed particulars or GDMO, is the language used to define the constitution and some of the relationships between managed marks The GDMO definition is in the form of templates used to define managed aim classes (classes in standard object-oriented terminology), attributes (instance variables), actions (methods) notifications (event that can be emitted by way of objects), and name bindings, which specify the ways in which correlates can be related by containment in the MIB. view the article on page 43 for more about GDMO

The general Management Information Service (CMIS)[6] is used to interact with the MIB, and the belonging to all Management Information Protocol (CMIP)[7] is the way service messages are encod for transmission between TMN management applications and the MIB.

The available services include getting information from managed facts changing their values, making manner calls, and creating and deleting managed thing perceiveds In addition, managed objects can emit events

The evolution Environment

We believe that telecommunication management applications of the what is yet to be will be composed of a number of large-grained, distributed correlates We call these objects application composings Application components differ from managed particulars in that, at their simplest, managed facts represent logical and physical parts of a network. Application constituents on the other hand, are pieces of the regularity that manages the network and the services running forward the network, and they may use, manipulate, and create managed facts as they work.