KR20030019817A - Control Apparatus And Method For Configuration Management In EMS System - Google Patents

Abstract

PURPOSE: A device and a method for controlling configuration management in an EMS(Element Management System) are provided to manage operation calling information by a client and configuration information obtained with corresponding calling results according to network elements IDs, so as to reduce a call response time upon configuration management without program correction of the client. CONSTITUTION: A local server(40) receives configuration information on network elements to store and manage the received information in a data list according to network elements IDs, and performs operation calling to an EMS server(50) to receive state information changed in real time, then delivers the received state information by being included in the configuration information stored in the data list. A smart proxy(30) stores and manages the operation calling information by an EMS client(20) in a client calling history table according to network elements IDs, and performs operation calling for the EMS server(50) or the local server(40) according to results of client calling history table search the case of the operation calling by the EMS client(20), then receives configuration information about network elements with corresponding calling results to deliver the received information to the EMS client(20).

Description

Control Apparatus And Method For Configuration Management In EMS System

The present invention relates to configuration management in an element management system (EMS) system, and in particular, obtained by operation call information and a call result corresponding to a case where an EMS client obtains configuration information about a network element from an EMS server through a remote call. The present invention relates to a configuration management control apparatus and method in an EMS system that allows configuration information to be managed in a local area to enable more efficient configuration management of network elements.

In general, the configuration management function of an element management system (EMS) system using a CORBA interface is a device that is managed by an EMS client remotely calling an operation of an EMS server, that is, It takes a way to request and collect configuration information about network elements.

However, at this time, the configuration information of the network elements collected by the EMS server according to the request of the EMS client is mostly large, and the number of EMS clients requesting such configuration information collection is large. The EMS server that collects configuration information about network elements and reports them is burdened with continuous load.

In particular, when requesting configuration information on a network element by recalling an operation that was called once, the EMS server has a disadvantage in that the load burden increases as the operation of collecting configuration information from the network element must be performed again. .

In other words, the EMS system based on the conventional COVA environment has a default proxy automatically generated in the stub code at the time of compiling the EMS client 11 and COVA IDL, as shown in FIG. 1. Proxy (12), a configuration DB (Data Base) 14 for applying in real time the configuration information for the network element existing in the remote area and the EMS server 13 for managing it.

In this case, when the EMS client 11 calls the operation (getBoardInfoAll ()) of the default proxy 12 according to the internal mechanism of COVA to obtain configuration information about the network element (for example, the exchange) to be managed, The default proxy 12 remotely calls the operation (getBoardInfoAll ()) of the EMS server 13 corresponding to the operation call of the EMS client 11.

However, the configuration information that the EMS client 11 needs to obtain by invoking the operation of the EMS server 13 through the default proxy 12 is often large, and the operation is called for one EMS server 13. Therefore, since the number of EMS clients 11 requesting collection of configuration information about network elements is increased, the load on the EMS server 13 is increased.

Also, even when the EMS client 11 recalls the same operation, the EMS server 11 in the remote area collects configuration information about the network element in response to the operation call every time, and then the corresponding EMS client 11 Since it must be delivered to the, there was a problem that the overall configuration management function of the EMS system is inefficient.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and an object thereof is to implement a smart proxy and a local server in a local area in which an EMS client is located in an EMS system, and to perform operation call information by the client and configuration information obtained as a result of the call. Can be managed by the network element ID, and the smart proxy checks whether the operation call by the corresponding EMS client is the first call or the recall, and then executes the call through the remote call or the local server to manage the configuration without modifying the program of the client. To reduce the call response time.

In addition, another object of the present invention, when the operation call by the EMS client is recalled, only the information that is changed in real time through the remote call to provide the configuration information requested by the client and at the same time load burden To improve the overall performance of the system.

1 is a diagram showing a schematic configuration of an EMS system based on a conventional COVA environment.

2 is a schematic configuration diagram illustrating a configuration management control apparatus in an EMS system according to the present invention;

3 is a flowchart of a configuration management operation in the EMS system according to the present invention;

4 is a diagram showing a system flow for explaining the configuration management operation when the EMS client call is the first call in FIG.

FIG. 5 is a diagram showing a system flow for explaining the configuration management operation when the EMS client call is recalled in FIG. 3; FIG.

Explanation of symbols on the main parts of the drawings

20: EMS server 30: smart proxy

31: client call history table 40: local server

41: data list 50: EMS server

60: configuration DB

A feature of the present invention for achieving the object as described above, in the EMS system based on the COVA environment, receiving configuration information about the network element stored in the data list for each network element ID to manage and to the EMS server A local server for performing an operation call and receiving only state information changed in real time, and including the configuration information stored in the data list and delivering the result as a call result; Stores and manages operation call information by EMS client in the client call history table for each network element ID. When operation is invoked by the EMS client, operation call is made to the EMS server or the local server according to the result of the client call history table search. After performing, the configuration management control device in the EMS system including a smart proxy that receives the configuration information for the network element as a result of the call and delivers to the EMS client.

Here, the smart proxy performs an operation call to the EMS server when the operation call by the EMS client is the first call as a result of retrieving the client call history table, and calls the operation on the local server when the call is recall. When the operation call is made to the EMS server, the configuration information about the network element is received from the EMS server, delivered to the EMS client as a call result, and delivered to the local server. To manage the configuration information.

The local server is a server existing in a local area where the EMS client is located, and when the operation is called by the smart proxy, performs an operation call that brings only state information changed in real time from the EMS server.

Another feature of the present invention includes the steps of checking the client call history table in the smart proxy when the operation call of the EMS client to determine the first call; Adding the current call information to a client call history table and performing a remote call to an EMS server when the EMS client call is the first call; Searching for a configuration DB in an EMS server, extracting all configuration information about network elements, and delivering the configuration information to the smart proxy; A method of managing configuration in an EMS system, comprising: delivering configuration information transmitted from the EMS server to the EMS client as a result of a call; To provide.

In addition, the configuration management method in the above-mentioned EMS system, the step of retrieving the client call history table in the smart proxy when the EMS client call is confirmed as a call back, the proxy server to call the operation of the local server; Remotely calling an operation of bringing only state information changed in real time from the local server to receive only state information from the EMS server; And applying the state information received from the EMS server to the configuration information stored in the data list, and delivering the configuration information including the state information to the EMS client as a call result through the smart proxy. It is done.

The client call history table is a table that stores call information for operations that the EMS client has called up to each network element ID.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Configuration management control apparatus in the EMS system based on the KOVA environment according to the present invention is shown in Figure 2, the EMS client 20 and the configuration DB 60 and EMS server belonging to the existing EMS system In addition to (50), a local server 40 existing in the local area where the EMS client 20 is located, and a smart proxy 30, which is a mechanism supported by COVA, is provided.

The EMS client 20 calls a predetermined operation in order to show the shape of the network element as it is or to display detailed information, and the configuration DB 60 configures the configuration information (not changed during operation) of the network elements to be managed. Dynamic configuration information such as static configuration information and status information that is changed in real time), and the EMS server 50 extracts the configuration information in the configuration DB 60 and delivers it to the EMS client 20. And extracts only state information that is changed in real time.

The smart proxy 30 is a proxy defined by the developer by adding a class to the existing default proxy and adding an additional function. The smart proxy 30 is called in place of the corresponding default proxy to perform operation call information by the EMS client 20. It is stored and managed in the client call history table 31 for each network element ID (IDentifier), and when the operation call of the corresponding EMS client 20 is performed, the client call history table 31 is retrieved and the operation or local server of the EMS server 50 is managed. After performing the operation call of (40), and delivers the configuration information for the network element obtained as a result of the corresponding call to the EMS client 20. In addition, when the operation call of the EMS server 50 is performed, configuration information about the network element obtained as a result of the call is transmitted to the EMS client 20 in response, and at the same time, to the local server 40.

The local server 40 stores and manages the configuration information about the network element delivered by the smart proxy 30 in the data list 41 for each network element ID, and has the same format as the EMS server 50 in the remote area. After the operation is called by the smart proxy 30, the operation is called to get only the information (for example, status information) that is changed in real time from the EMS server 50, and the corresponding real-time status information is received and then the data list ( It is included in the configuration information stored in 41) and forwarded to the smart proxy 30 in response.

The configuration management operation in the EMS system according to the present invention configured as described above will be described with reference to FIG. 3 as follows, in order to facilitate the understanding of the EMS client 20 to the rack shape of a specific network element An example of requesting the EMS server 50 for all board information of a corresponding rack to draw will be described.

First, the EMS client 20 should define board information (BoardInfo) and an operation as COVA IDL in order to get all the board information of the rack for a specific network element. An example of defining such COBA IDL is as follows.

struct BoardInfo {struct StateInfo {

short A; short A;

short B; short B;

};

string Z;

};

typedef sequence <BoardInfo> BoardInfoSeq;

typedef sequence <StateInfo> StateInfoSeq;

short getBoardInfoAll (in short ID, out BoardInfoSeq boardInfoSeq);

short getStateInfo (in short ID, out StateInfoSeq stateInfoSeq);

In addition, since the number of data fields per board, that is, the board configuration information is large, but the state information (StateInfo) changed in real time is only a part of them, in order to obtain only such state information when recalling the same operation, the above COVA IDL is used. As in the definition example, first, the COBA IDL for the state information is defined, and an operation for importing only the state information is defined (step S31).

In this case, the execution time of the operation of bringing only the status information is considerably shorter than the operation execution time of bringing the configuration information of the whole board in the related art, so that the board configuration information required by the EMS client 20 can be quickly responded to. do.

In this way, while defining the COBA IDL for the rack information and the status information of the rack for the network element and an operation for importing each piece of information, the EMS client 20 selects the rack configuration information of the rack for the specific network element. (Step S32), where the operation call is coded on the program as if it is calling the EMS server 50 of the remote area directly, but the local where the EMS client 20 is located by the actual COVA system internal mechanism. The operation of the smart proxy 30 created in the area is called.

Accordingly, the smart proxy 30 retrieves the client call history table 31 as the EMS client 20 calls a predetermined operation call (step S33), so that the operation call by the EMS client 20 is the first time. It is determined whether the call is made (step S34), where the client call history table 31 refers to a table that stores call information for operations that the EMS client 20 has called up to each network element ID.

At this time, when the operation call by the EMS client 20 is the first call, the corresponding EMS system performs configuration management according to the system flow as shown in FIG. 4 attached to the drawing. After adding the operation call information (network element ID and operation name) by the current EMS client 20 to the client call history table 31 (step S35), perform a remote call to call the operation of the EMS server 50. (Step S36).

Accordingly, the EMS server 50 searches for configuration information stored in the configuration DB 60 according to the operation call of the smart proxy 30, extracts all configuration information of the corresponding board, and then transfers the configuration information to the smart proxy 30. Is given.

Then, the smart proxy 30 delivers the configuration information received as the result of the operation call from the EMS server 50 to the EMS client 20, and performs a remote call to the EMS server 50 when the operation is recalled. Instead of delivering the configuration information requested by the EMS client 20, the configuration information received as a result of the remote call from the EMS server 50 is transferred to the local server 40, and the local server 40 provides a smart proxy. The configuration information delivered by the 30, that is, the configuration information obtained through the operation call to the EMS server 50 located in the remote area is stored and managed in the data list 41 for each network element ID (step S37).

On the other hand, if the operation call by the EMS client 20 in step S34 is not the first call, that is, the recall, the EMS system performs configuration management according to the system flow as shown in FIG. Since the server does not perform a remote call to the EMS server 50 as the operation call by the EMS client 20 is confirmed as reentrant, the server of the local server 40 managing the configuration information received at the previous operation call. The operation is called (step S38).

Accordingly, the local server 40 remotely calls the operation of bringing only board state information, which is information that is changed in real time according to an operation call of the smart proxy 30, and receives corresponding board state information from the EMS server 50. In this case, unlike the remote call made by the smart proxy 30, the operation call by the local server 40 brings only load of state information that is changed in real time, which is part of the configuration information of the board, from the EMS server 50. Can be reduced.

Thereafter, the local server 40 receives the state information changed in real time from the EMS server 50, and then applies the state information to the configuration information stored in the data list 41 managed by the local server 40 (step). S39), the configuration information including the corresponding state information is delivered to the smart proxy 30, the smart proxy 30, the EMS client 20 receives the configuration information received as a result of the operation call from the local server 40 Will be delivered (Step S40).

As a result, when the EMS client 20 recalls the same operation, it is possible to more quickly obtain configuration information having the same call result without performing a remote call to the EMS server 50.

In addition, the embodiments according to the present invention are not limited to the above-described embodiments, and various alternatives, modifications, and changes can be made within the scope apparent to those skilled in the art.

As described above, the present invention implements the smart proxy and the local server in the local area where the EMS client is located in the EMS system to manage operation call information by the client and configuration information obtained as a result of the call for each network element ID. By checking the smart proxy to determine whether the operation call by the EMS client is the first call or recall, the call response time can be shortened during configuration management without modifying the client program by executing the remote call or the call through the local server. .

In addition, when the operation call by the EMS client is recalled, the present invention obtains only the information that is changed in real time through the remote call and provides configuration information requested by the corresponding client. Since the call is only for getting information that changes in real time, it can reduce the load and improve the overall performance of the system.

Claims (7)

In the EMS system based on the COVA environment, Receives configuration information about network elements and stores them in the data list for each network element ID, manages them, and performs only the operation call to EMS server to receive only the status information that is changed in real time. A local server that includes and delivers the result of the call; Stores and manages operation call information by EMS client in the client call history table for each network element ID. When operation is invoked by the EMS client, operation call is made to the EMS server or the local server according to the result of the client call history table search. After performing, the configuration management control device in the EMS system characterized in that it comprises a smart proxy for receiving the configuration information for the network element as a result of the call to pass to the EMS client. The method of claim 1, The smart proxy performs an operation call to the EMS server when the operation call by the EMS client is the first call as a result of searching the client call history table, and performs an operation call to the local server when the call is recall. Configuration management control device in the EMS system, characterized in that. The method according to claim 1 or 2, When the smart proxy performs an operation call to the EMS server, the smart proxy receives configuration information about the network element from the EMS server, delivers the configuration information to the EMS client as a call result, and delivers the configuration information to the local server. Configuration management control device in the EMS system, characterized in that to manage. The method of claim 1 or 3, The local server is a server existing in a local area where an EMS client is located, and when the operation is invoked by the smart proxy, an EMS system which performs only an operation call for bringing only status information changed in real time from the EMS server. Configuration management control device in. Checking the client call history table in the smart proxy when the EMS client calls the operation to determine whether the call is the first call; Adding the current call information to a client call history table and performing a remote call to an EMS server when the EMS client call is the first call; Searching for a configuration DB in an EMS server, extracting all configuration information about network elements, and delivering the configuration information to the smart proxy; And delivering the configuration information transmitted from the EMS server to the EMS client as a result of the call and transmitting the configuration information to the local server to store and manage the data list for each network element ID in the EMS system. How to manage your configuration. The method of claim 5, Invoking an operation of a local server by a proxy server when the EMS client call is determined to be reentrant as a result of retrieving a client call history table from the smart proxy; Remotely calling an operation of bringing only state information changed in real time from the local server to receive only state information from the EMS server; And applying the state information received from the EMS server to the configuration information stored in the data list, and delivering the configuration information including the state information to the EMS client as a call result through the smart proxy. Configuration management method in the EMS system. The method of claim 5 or 6, The client call history table is a configuration management method of the EMS system, characterized in that for storing the call information for the operations that the EMS client has called up to each network element ID.