KR20000054741A - System Management for Telecommunications Information Networking Architecture(TINA) - Google Patents

Abstract

PURPOSE: A system for managing Telecommunications Information Networking Architecture(TINA) networks, is provided to supply independence between managing systems of TINA Element Management Layer(EML) components and a Simple Network Management Protocol(SNMP) or Telecommunications Management Networks(TMN) EML agents, and optimize management for TINA EML components, by implementing a TINA Generic Resource Object(TGRO) to a Common Object Request Broker(CORBA), with supplying a single TINA Generic Resource Interface(TGRI) with each TINA EML component and placing corresponding TGRO distribution individuals, after comprising a TGRA relaying module connecting to a Network Element Layer(NEL). CONSTITUTION: A system for managing Telecommunications Information Networking Architecture(TINA) networks, implements a TINA Generic Resource Object(TGRO) to a Common Object Request Broker(CORBA), by supplying a single TINA Generic Resource Interface(TGRI) with each TINA EML component and placing corresponding TGRO distribution individuals, after comprising a TGRA relaying module connecting to a Network Element Layer(NEL) of other managing systems. The TGRA operates as an EML agent in a TINA managing area and as an EML manager in managing areas of other managing systems, and guarantees conversions of an information model/managing protocol and independence.

Description

System Management for Telecommunications Information Networking Architecture (TINA)

The present invention relates to TINA (Telecommunications Information Networking Architecture) network management, and in particular, TINA suitable for incorporating existing network management systems such as TMN (Telecommunications Management Networks) and SNMP (Simple Network Management Protocol) into a TINA distributed network management environment system. A network management system.

Network management systems such as TMN of ITU-T (International Telecommunication Union-Telecommunication), SNMP of Internet Engineering Task Force (IETF), and TINA of TINA-C have been established for efficient management of modern complex communication networks.

In particular, TINA offers a distributed network management model based on the DPE (Distributed Processing Environment) / CORBA (Common Object Request Broker) by adopting the structure and advantages that are organized in the existing TMN and Open System Interconnection (OSI) management system. have. However, although the definition of network domain and service domain is defined in detail in such a TINA system, the specification for each network element (NE) is not defined. Therefore, at present, the TINA system alone cannot control the actual network components.

However, these heterogeneous network management systems use different information models and management protocols, so it is not possible to apply them directly. Therefore, functional modules are needed to relay and change information models and management protocols between different management systems.

Hereinafter, with reference to the accompanying drawings will be described in the conventional TINA network management as follows.

1 is a block diagram showing a TINA network management system using a conventional interworking module.

As shown in FIG. 1, in a method of incorporating a network element layer (NEL) layer of another management system into a TINA system, a function module having a different structure is designed and implemented according to the management system of the NEL layer. Therefore, the interface between the TINA-SNMP linkage module and the TINA-TMN linkage module is different, and it is impossible to replace a function module without changing the structure and source code. That is, the TINA-SNMP matching module, which combines the TINA system and the SNMP management system, does not support the TMN system by a simple replacement, and the TINA-TMN matching module does not immediately support the SNMP system.

Here, the EML (Element Management Layer) component of the TINA scheme must be designed and implemented in different ways depending on whether the lower matching module supports SNMP or TMN.

In order to solve the above problems, the present invention provides a single interface called TINA Generic Resource Interface (TGRI), which is independent of the TINA network management system for efficient interworking between the TINA network management system and network management systems such as SNMP and TMN. To give. Therefore, the object of the present invention is to provide a TINA network management system suitable for implementing TINA management components without being affected by other management functions.

1 is a block diagram showing a TINA network management system using a conventional conventional interworking module

2 is a conceptual diagram of a system according to an embodiment of the present invention;

3 is a detailed configuration diagram of a system according to an embodiment of the present invention;

Figure 4 is a block diagram of a TINA network management system according to an embodiment of the present invention

TINA network management system of the present invention for achieving the above object comprises a TGRA relay module that combines the NEL layer of the other management system to the TINA management system to provide a single TGRI interface for each TINA EML component and each of the TGRI TGRO distributed objects corresponding to are positioned to implement the TGRO in CORBA.

A preferred embodiment of the feature is that the TGRA operates as an EML agent in the TIAN management area and as an EML manager in the management area of another management system.

A preferred embodiment of the feature is that the TGRA ensures information model transformation, management protocol transformation and independence.

A preferred embodiment of the feature is that the TGRA is a distributed component operating on a DPE.

A preferred embodiment of the feature is that the TGRI is in a 1: 1 relationship with a TINA component.

A preferred embodiment of the feature is that the TGRO uses an EML agent of another management system to provide a service as an EML agent with a TINA EML component. A preferred embodiment of the feature is that the other management system is characterized in that the SNMP and TMN system.

A preferred embodiment of the feature is that an external database is used to manage all information objects in the TGRA, and a database interworking interface is used to use the external database.

Hereinafter, with reference to the accompanying drawings will be described in more detail with respect to the TINA network management system of the present invention.

2 is a conceptual diagram of a system according to an embodiment of the present invention, Figure 3 is a detailed configuration diagram of a system according to an embodiment of the present invention. 4 is a block diagram of a TINA network management system according to an embodiment of the present invention.

As shown in FIGS. 2 and 3, the TGRA, which combines the TINA management system with other management systems, is viewed from the layering point of the network management system. The TINA management area is an EML agent and an EML manager in an SNMP or TMN management area. )

Here, the TGRA provides the following functions.

First is the transformation of the information model between TINA information objects, SNMP MO (Managed Object) and TMN MOs.

Second is the management protocol conversion of TINA management protocol and SNMP and TMN management protocol.

Third, independence in sub-management systems, independence in sub-management protocols, and independence in manufacturers of sub-management systems.

Meanwhile, the components of the TINA EML layer are divided into several components according to division of management functional areas. Among them, the components corresponding to the base management functions are configuration management (EML-TC (Topology Configuration)), connection management (EML-CP (Connection Performer)), performance management (EML-PM (Performance Manager)) and fault management (EML). -FM (Fault Manager) component.

The TGRA is a distributed component that operates on a distributed processing environment (DPE), and requires a distributed interface for accessing and receiving the TGRA. Therefore, the TGRA provides an interface called TINA Generic Resource Interface (TGRI) for this purpose.

Here, since CORBA is assumed using the DPE, the TGRI is described through an Interface Definition Language (IDL) of an Object Management Group (OMG). The TGRI is described to be optimized for the tool of the TINA EML component and is described independently of the management technology of the EML agent.

Such a characteristic of TGRI is that a TINA EML component can use various EML agents only with knowledge of the TGRI, and the TGRI has a 1: 1 relationship with a TINA component to be serviced.

Thus, the TINA components can simultaneously access a single TGRA and request service.

And the TGRA provides such TGRI interfaces for each TINA EML component.

Meanwhile, interfaces belonging to the failure management include tgri_fm.idl and tgri_trap.idl. The tgri_fm.idl is an interface used when a TINA failure management component requests management to TGRA and receives the response. The tgri_trap.idl is a TINA failure management component in which TGRA actively prevents a failure. This is the interface used for "event reporting" to report to. At this time, the configuration management interface is tgri_tc.idl, the connection management interface is tgri_cp.idl, and the performance management interface is tgri_pm.idl.

In the TGRA, distributed objects called TGRO (TINA Generic Resource Object) corresponding to each TGRI are located. Since CORBA is assumed as a distributed environment, TGROs are implemented as CORBA objects, and when using CORBA, one CORBA object is created in one IDL interface. That is, as shown in Table 1, the TGRO is subdivided into respective management functions according to TGRI, and the TGRO objects each provide a service as an EML agent to a corresponding TINA EML component.

_domain ^function EML Manager EML Agent function Configuration management EML-TC Object for configuration Provide configuration information and change service of network components Connection management EML-CP Object for connection (OCONN) Provision of connection setting, disconnection and change of network components Performance Management EML-PM OPERF (object for performance) Providing performance information of network components and providing performance personalization service Fault Management EML-FM OFAUU (object for fault) Providing fault information of network components and providing fault recovery service Object for trap (OTRAP) Report failure of network component

The TGRO uses an EML agent of SNMP or TMN to provide a service as an EML agent with a TINA EML component. At this time, the management request transmitted to the TGRO is a management command of the TINA system, and the EML agent available to the TGRO is an SNMP or TMN agent. Therefore, each TGRO needs a function to convert the requested management request into a management request of TMN or SNMP.

Here, the above transformation is divided into an information view and a protocol view. The conversion of the information point of view is a function of converting an information object of the TINA system into an SNMP or TMN information object, and the conversion of the protocol point of view is a function of converting a management message received from a TGRI interface into a management message of an SNMP or TMN.

Such conversion includes forward conversion from TINA system to SNMP or TMN system and reverse conversion from SNMP or TMN system to TINA system.

The reverse conversion is used when the TGRO needs to actively report and occasional event occurrence, and the OTRAP processes only aperiodic event reports generated by the EML agent of SNMP or TMN. Since only the object to the management information, the management information of the SNMP or TMN to perform the reverse conversion to convert the TINA.

Here, the conversion functions required for each information object are shown in Table 2.

Information, management message conversion direction function OCONF Forward (TINA⇒SNMP or TMN) Management request Reverse (SNMP or TMN⇒TINA) Management response OCONN Forward (TINA⇒SNMP or TMN) Management request Reverse (SNMP or TMN⇒TINA) Management response OPER Forward (TINA⇒SNMP or TMN) Management request Reverse (SNMP or TMN⇒TINA) Management response OFAUL Forward (TINA⇒SNMP or TMN) Management request Reverse (SNMP or TMN⇒TINA) Management response OTRAP Reverse (SNMP or TMN⇒TINA) Disability Report

As such, since the TGRO needs to provide a service only to the TINA EML component assigned to the TGRO, the TGRO may be optimized for a specific task, and the TGRA structure may be strictly modularized. Therefore, if the type of the upper TINA component requiring the TGRA increases, the TGRA itself adds a new TGRO without changing the structure, so that the entire structure can be reused. In addition, since the performance improvement of the TGRA can be performed in each TGRO unit, the performance of the TGRA can be improved only by replacing the TGRO.

Meanwhile, the TGRA provides a service as an EML agent to upper TINA EML components. Therefore, it maintains the information objects required to perform the management function as the TINA NEL agent.

In addition, since the EML agent of the SNMP or TMN system should be operated as an EML manager, it must also have information on MOs of the SNMP or TMN.

Since such information object MOs can be increased from as small as thousands to as many as hundreds of thousands, it is difficult to manage information on all MOs in the TGRA. Therefore, the TGRA uses an external database and has a database interworking interface for using an external database.

Here, Table 3 shows two database management according to the function of the TGRA.

Database function NEL-Agent Function TINAMIB Database for managing TINA NEL information objects EML-Manager Function SNMPMIB Database that manages MO information of SNMP TMNMIB Database that manages NEL MO information of TMN

As described above, the TINA network management system of the present invention has the following effects.

By integrating the EML agent into the TINA distributed network management system, it is possible to have independence between the TINA EML components and the management system of the SNMP or TMN EML agent.

And since TINA's EML components always use the same consistent TGRI interface regardless of the management system of the underlying EML agent, the software structure can be standardized.

In addition, TGRA acts as a complete TINA's EML agent, so it can be processed with a single administrative command, thus optimizing the management requirements for TINA EML components.

Claims (8)

TGRA relay module that combines NINA layer of other management system with TINA management system to provide TGRI single interface for each TINA EML component, and TGRO distributed objects corresponding to each TGRI are located to implement TGRO as CORBA. TINA network management system. The method of claim 1, The TGRA operates as an EML agent in the TIAN management area and as an EML manager in the management area of another management system. The method of claim 1, The TGRA is a TINA network management system, characterized in that to ensure information model conversion, management protocol conversion and independence. The method of claim 1, The TGRA is a TINA network management system, characterized in that the distributed component operating on the DPE. The method of claim 1, The TGRI has a 1: 1 relationship with the TINA component. The method of claim 1, The TGRO is a TINA EML component, TINA network management system, characterized in that to use the EML agent of another management system to provide services as an EML agent. The method of claim 1, The other management system is a TINA network management system, characterized in that the SNMP and TMN system. The method of claim 1, And an external database for managing all information objects in the TGRA, and having a database interworking interface for using the external database.