KR20040046882A - System and method of integrating and managing information of operators - Google Patents

Abstract

PURPOSE: A network system and a method for integrally managing operator information are provided to integrally manage the information for operators operating an EMS(Element Management System) and a CLI(Command Line Interface) through an MIB(Management Information Base) table set to an NE(Network Element), and prevent the same operator from logging-in repeatedly through the session management of the operator. CONSTITUTION: The EMS(200) includes an SNMP(Simple Network Management Protocol) administrator(202) and makes the operators logged in through the SNMP administrator order the corresponding operation by using an SNMP message. The NE(250) includes an SNMP proxy(254) performing a management operation by responding to the corresponding command, the CLI(252) that is the operator's interface, and the MIB table(258) for integrating/managing the information for the operators operating the EMS and the CLI.

Description

Network system and method for integrating and managing operator information {System and method of integrating and managing information of operators}

The present invention relates to a network system, and more particularly, to a network system and method for integrated management of operator information of an element management system (EMS) and a command interface (CLI).

Currently, network-related devices including the Internet mostly use a network management protocol based on the Simple Network Management Protocol (SNMP) to manage the network and monitor the operation of each network device. SNMP is the most common network management protocol, and its function has been improved by the evolution of V1 / V2 / V3 respectively. Most network systems use a Graphical User Interface (GUI) -based Element Management System (EMS) that utilizes SNMP, and a command line interface that directly receives and processes commands through external terminals. CLI).

1 is a block diagram illustrating a network system using a conventional SNMP. Referring to FIG. 1, a network system is composed of an element management system (EMS) 100 and a network element (NE) 150. EMS 100 is a database 104 that stores information of operators logged in via a log-in task 106 and an SNMP manager 102 that manages network elements 150 using SNMP messages by the operators. ). The network element 150 also includes a command line interface (CLI) 152, a database 156, an SNMP agent 154, and a management information base (MIB) 158. CLI 152 is operated by each operator logged in via terminal 180, and database 156 stores the information of these operators. The SNMP agent 154 transfers information necessary for network management using an SNMP message according to the request of the SNMP manager 102. MIB 158 stores all the information necessary to manage the communication network.

As such, in the conventional network system, both the EMS 100 and the CLI 152 are used to manage the network element 150, and they independently manage the databases 104 and 156 storing the respective operator information. .

As a result, the conventional network system illustrated in FIG. 1 has a disadvantage in that the operators of each EMS 100 and the CLI 152 are dually registered and the registered operator information must be separately managed. In addition, because different local information is used when the operator logs in through EMS 100 and CLI 152, the operator's period of use, i.e., the session, is not managed, which allows double login of the same operator. There is a problem that has been.

Accordingly, the present invention has been made to solve the above problems, by setting the management information base table in the network element, through which the information of the operators operating the element management system and the command interface through this, and manages the session of the operator It is an object of the present invention to provide a network system and method for integrated management of operator information that prevents the same operator from logging in twice through management.

1 is a block diagram illustrating a network system using a conventional simple network management protocol (SNMP).

2 is a block diagram illustrating a network system for integrated management of operator information of an element management system (EMS) and a command interface (CLI) according to the present invention;

3 is a view for explaining a MIB table according to the present invention;

4 is a flowchart illustrating a method for integrated management of EMS and CLI operator information according to an embodiment of the present invention;

5A through 5C are flowcharts for describing an operator information maintenance process in the operator information integrated management method illustrated in FIG. 3;

6 is a flow chart illustrating a method for unified management of operator information between an EMS and a CLI according to another embodiment of the present invention.

<Description of the symbols for the main parts of the drawings>

200: element management system 250: network element

202: SNMP manager 204: Database

252 command interface (CLI) 254: SNMP agent

258: MIB table

Network system for integrated management of the operator information according to the present invention for achieving this object, includes a simple network management protocol (SNMP) manager, a number of operators logged in through the SNMP manager using the SNMP message An element management system for instructing an operation; And an SNMP agent for performing management operations in response to the corresponding command, a command interface that is an operator interface, and management means for integrating and managing information of operators operating the element management system and operators operating the command interface. And a network element to include.

In addition, the method for integrated management of the operator information according to the present invention for achieving the above object, the element management system including a simple network management protocol (SNMP) manager and SNMP agent, command interface and management information base (MIB) table In a network system consisting of a network element, comprising: information management of a plurality of operators of the element management system and the command line interface through the MIB table, wherein the log through any one of the element management system and the command interface Determining whether an operator ID and password inputted to be present exist in the MIB table; If it is determined that the operator ID and password exist in the MIB table, determining whether the operator's login flag is displayed in the MIB table as logged in; If the login flag is displayed as logged in, displaying it as an error; Setting the log-in flag to a log-in state if the log-in flag is displayed in the log-out state in step b); Determining the operator's level displayed in the MIB table when the login flag is set to a logged in state; Enabling to perform a corresponding function according to the determined operator's grade; And when the execution of the corresponding function is finished, setting a login flag of the MIB table to a logout state.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention.

2 is a block diagram illustrating a network system for integrated management of operator information of an element management system (EMS) and a command interface (CLI) according to the present invention. Referring to FIG. 2, a network system is composed of an element management system (EMS) 200, a network element (NE) 250, and a terminal 280.

The EMS 200 instructs the operation by using an SNMP message to monitor and control the performance of the network element 250, and by the logged in operator (LOG-IN TASK) 206 Is operated. EMS 200 includes an SNMP manager 202 and a database 204. The SNMP manager 202 performs an authentication procedure of operators logged in through the EMS 200, that is, a login / logout procedure and a registration, change and deletion procedure of a new operator through the EMS 200. The result of performing this procedure is registered in the MIB table 258 of the network element 250. In addition, the SNMP manager 202 exchanges SNMP messages with the SNMP agent 254 of the network element 250 to manage the network element 250.

The EMS 200 having such a configuration provides the SNMP manager 202 with an interface for viewing the situation of the entire network, and the database 204 to perform management (TASK) analysis of management data, fault management, and the like. Build it.

In addition, the network element 250 is managed by the EMS 200 via an SNMP message and has a management information base (MIB) having a command interface (CLI) 252, an SNMP agent 254, and a MIB table 258. (256). The SNMP agent 254 exchanges SNMP messages with the SNMP manager 202 and performs certain processing procedures for managing an operator's session under the management of the SNMP manager 202. Through this session management, the SNMP agent 254 controls the setting of the MIB table 258 included in the MIB 256, as described below. The command interface (CLI) 252 is operated by operators logged in via the terminal 280 and performs authentication procedures of registered operators and registration, modification and deletion procedures of new operators. The result of performing this procedure is transferred to the MIB table 258 and registered. Here, the CLI 252 is a user interface with a computer operating system or an application program, and a user (operator) inputs a command on a predetermined line when a prompt is displayed on the screen of the terminal 280, and the EMS 200 can access the command line. After receiving the response, it works by typing another command again. The MIB 256 holds all the information needed to manage the communication network and includes a MIB table 258 in accordance with the present invention. That is, the MIB table 258 records the information of the operators of the EMS 200 and the operators of the CLI 252, for example, an ID, a password, a log in / out state, and a class of operators in the form of a fixed table. .

As such, the network element 250 manages the information of the EMS 200 and the CLI 252 operators through the MIB table 258 and manages the session of each operator through the SNMP agent 254.

3 is a view for explaining the MIB table 258 according to the present invention.

As shown in FIG. 3, the MIB table 258 is composed of an operator ID field, a password field, a log-in flag field, and an operator class field. The operator ID field is a field for displaying an operator's ID, and the password field is a field for displaying an operator's password. The log-in flag is a field for indicating whether the current operator is logged in. The log-in flag is displayed as LOG_IN for logging in and LOG_OUT for logging out. Here, the log-in flag is updated with the latest information every time the operator logs in or out, and is used for a polling operation for managing the session of the operator. In addition, the grade field is a field for indicating the grade of the operator, for example, may be displayed as ADMIN (administrator) or OPERATOR (ordinary operator), and the service provided according to the grade of the operator may be limited.

As such, the result of the operator information maintenance work such as registration, change, and deletion of the operator's information through the EMS 200 or the CLI 252 should be reflected in the MIB table 258.

4 is a flowchart illustrating a method for integrated management of EMS and CLI operator information, and FIGS. 5A to 5C are flowcharts for explaining an operator information maintenance process of the integrated operator information management method shown in FIG. 4. .

Hereinafter, a method for integrated management of operator information of an EMS and a CLI according to the present invention will be described in detail with reference to FIGS. 2 to 5.

4 illustrates an operator authentication process performed by the SNMP manager 202 among the methods for integrating and managing the operator information of the EMS and the CLI. The operator inputs the login ID and password in the login information input window of the EMS 200. At this time, the process shown in FIG. 4 is executed internally in the SNMP manager 202. First, the SNMP manager 202 loads an operator ID from the operator ID field of the MIB table 258 (S400). The SNMP manager 202 determines whether the ID input by the current operator and the loaded operator ID match (S405). If it does not match, the MIB table 258 is searched while increasing the entry of the MIB table 258 (S410) to determine whether there is an ID that matches the currently input ID.

As such, the process of loading and retrieving the operator ID from the MIB table 258 may be performed by using GetRequest and GetNextRequest messages in the SNMP message. That is, in a network system using SNMP, messages such as GetRequest, GetNextRequest, SetRequest, etc. are used by the SNMP manager 202 of the EMS 200 to obtain and set necessary information from the SNMP agent 254 of the network element 250. In response to the request of the SNMP manager 202, a GetResponse or Trap message is used when the SNMP agent 254 informs the corresponding information or notifies a specific situation. Therefore, if there is a request for information from the SNMP manager 202 using the SNMP message, the SNMP agent 254 retrieves the information from the MIB 258 and informs the SNMP manager 202 of the information.

If it is determined that the operator ID input in S405 matches the operator ID loaded in the MIB table 258, the SNMP manager 202 loads the operator password from the MIB table 258 (S415). It is determined whether the input operator's password and the loaded password match (S420). If the password does not match, it is displayed as "error" (S425). If the password matches, the login flag of the operator is loaded from the MIB table 528 and checked (S430). If the login flag of the operator is set to a pre-operation state, that is, "LOG_IN", in order to prevent the same operator from logging in, it is displayed as "error" (S440). If the login flag of the operator is set to "LOG_OUT" in the MIB table 258, the login flag is set to normal "LOG_IN" (S445). As in the case of loading the operator ID, the process of loading the operator password and the login flag in the MIB table 258 may be performed using the above-described GetRequest and GetNextRequest messages. In addition, the process of setting the login flag of S445 may be performed through the above-described SetRequest message.

After S445, the SNMP manager 202 loads the operator class of the MIB table 258 (S450) and enables or disables corresponding functions according to the operator class. That is, in the embodiment of FIG. 4, it is determined whether the operator class is set to "ADMIN" (S455), and if the operator class is set to "ADMIN", enable maintenance functions such as registration, change, and deletion of the operator. To perform the corresponding function (S460). Performing such functions as registration, modification and deletion of the operator will be described in detail with reference to FIGS. 5A to 5C. If the operator grade is not "ADMIN" in S450, enable a function corresponding to other grades (S470). In addition, the SNMP manager 202 determines whether the function execution by the operator has ended (S480), and if so, sets the login flag of the MIB table 258 to "LOG_OUT" (S490).

As such, the operator information integrated management method of the present invention uses the login flag of the MIB table 258 to prevent double login of the same operator and to authenticate that it is a registered operator.

FIG. 5A is a flowchart illustrating an operator registration process performed by the SNMP manager 202 during an operator registration, change, and deletion process (S460) of the operator information integrated management method illustrated in FIG. 4. Referring to FIG. 5A, an operator ID registered in the MIB table 258 is loaded to search whether an ID identical to an operator ID to be registered exists in the MIB table 258 (S500). If it is determined that the ID to be registered and the loaded operator ID match (S505), since the ID is already registered by another operator, it is displayed as "ERROR" (S510). In addition, if it is determined that the ID to be registered does not match the loaded operator ID, the operator ID registered up to the last entry is searched while increasing the entry of the MIB table 258 (S520 and S525). If there is no ID that matches the ID to register until the last entry of the MIB table 258, the SNMP manager 202 increments the entry to register a new operator in the MIB table 258 (S530). In step S540, an entry for adding one row of the MIB table 258 is set using the SetRequest message. Accordingly, the SNMP manager 202 transmits a SetRequest message to the SNMP agent 254 to set a new operator ID and password in the corresponding field of the added row of the MIB table 258 (S550 and S560). At this time, the operator login flag field is set to "LOG_OUT" because the new operator is not currently logged in (S570). Similarly, a new operator's grade is set in the operator's grade field (S580).

5B is a flowchart illustrating an operator change process performed by the SNMP manager 202 during an operator registration, change, and deletion process (S460) of the operator information integrated management method according to the present invention. Referring to FIG. 5B, an operator ID registered in the MIB table 258 is loaded to determine whether an operator ID to be changed exists in the MIB table 258 (S600). At this time, it is determined whether the operator ID to be changed matches the loaded operator ID (S610). If the operator ID to be changed does not match the loaded operator ID, the registered operator ID is searched by incrementing the entry to the last entry of the MIB table 258 to check whether the operator ID to be changed and the registered ID match. It determines (S620 and S630). If the operator ID of the last entry of the MIB table 258 also does not match the operator ID to be changed, the operator ID to be changed does not exist in the MIB table 258 and is displayed as "ERROR" (S640). . On the other hand, if it is determined in S610 that the operator ID to be changed matches the loaded operator ID, the SNMP manager 202 uses the SetRequest message to change the password and operator class of the operator (S650 and S660). Herein, the changed operator's information is not limited to the embodiment of FIG. 5B and may be variously set.

FIG. 5C is a flowchart illustrating an operator deletion process performed by the SNMP manager 202 during an operator registration, change, and deletion process (S460) of the operator information integrated management method according to the present invention. Referring to FIG. 5C, an operator ID registered in the MIB table 258 is loaded to determine whether an operator ID to be deleted exists in the MIB table 258 (S700). At this time, it is determined whether the operator ID to be deleted matches the loaded operator ID (S710). If the operator ID to be deleted does not match the loaded operator ID, the registered operator is searched while increasing the entry of the MIB table to the last entry of the MIB table 258. It is determined whether they match (S720 and S730). At this time, if the operator ID of the last entry of the MIB table 258 also does not match the operator ID to be deleted, the operator ID to be deleted does not exist in the MIB table 258 and is displayed as "ERROR" (S740). ). On the other hand, if it is determined in S710 that the operator ID to be deleted matches the loaded operator ID, the SNMP manager 202 sets an entry for deleting one row from the MIB table 258 (S750). The related information is deleted (S760).

As described above, when the operator's grade is ADMIN, the operator registration, change, and deletion functions illustrated in FIGS. 5A to 5C may be performed.

6 is a flowchart illustrating a method for integrated management of operator information according to another embodiment of the present invention. In particular, FIG. 6 shows a method of detecting and blocking an operator's dual login through session management of the operator performed by the SNMP agent 254. That is, when the operator is logged in, the SNMP manager 202 periodically uses the login flag of the MIB table 258 to check the SNMP agent 254 periodically to check the operator's login status (ALIVE). Poll. In other words, the SNMP manager 202 sends a polling message to the SNMP agent 254 at an appropriate interval (POLLING INTERVAL) so that the login flag of the MIB table 258 is set to "LOG_IN". Therefore, referring to FIG. 6, the SNMP agent 254 receives a polling message from the SNMP manager 202 (S800). Whenever the SNMP agent 254 receives a polling message from the SNMP manager 202, the SNMP agent 254 performs the following process to manage the usage period of the operator. The SNMP agent 254 determines whether the login flag of the MIB table 258 is set to the login state, that is, "LOG_IN" (S810). If it is set to "LOG_IN", the SNMP agent 254 operates an internal timer for checking the session of the operator to set the current count value to a predetermined value, for example, polling period * 3 (S820). . At this point, down counting is started to decrease the count value (S830), and it is determined whether the count value is "0" (S840). If the count value is "0", the login flag of the MIB table 258 is set to the "LOG_OUT" state (S850). That is, the count value is " 0 " means that the normal logout is not performed by the operator, and the EMS 200 is abnormally terminated so that the SNMP agent 254 does not receive the polling message within the given number of polling cycles. The case is shown. Therefore, even in such an abnormal case, since the log-in flag of the MIB table 258 is set to the log-out state again after a predetermined time has elapsed, the operator can later log in normally again. In addition, when the EMS 200 is normally terminated, the SNMP agent 254 receives a polling message before the down counting value becomes "0".

As described above, even through the operator session management of FIG. 6, even if the operator is abnormally logged out, the login flag of the MIB table 258 checks this and displays the logout state normally. Can be prevented.

Although the preferred embodiments of the present invention have been described in detail above, those skilled in the art will appreciate that the present invention may be modified without departing from the spirit and scope of the invention as defined in the appended claims. It will be appreciated that modifications or variations may be made. Therefore, changes in the future embodiments of the present invention will not be able to escape the technology of the present invention.

As described above, according to the present invention, since the EMS operator and the CLI operator information may not be managed separately from each other in the network system using the SNMP message, the EMS and CLI may be integrated and managed using the MIB table of the network element. There is an effect that the operator information between the two can be matched. In addition, according to the present invention, by using the log-in flag of the MIB table to accurately determine the log-in / out status of the operator, and by preventing the double log-in of the same operator through the session management of the operator, the operator is not suitable for the network This can fundamentally block access to the system, which in turn can enhance security.

Claims (10)

An element management system including a simple network management protocol (SNMP) manager, wherein a plurality of operators logged in through the SNMP manager instruct a corresponding operation using an SNMP message; And An SNMP agent performing a management operation in response to the corresponding command, a command interface that is an operator interface, and management means for integrating and managing information of operators operating the element management system and operators operating the command interface. And a network element. The management information base (MIB) table according to claim 1, wherein said management means is a management information base (MIB) table for registering, changing, and deleting information of operators of said element management system and said command interface. An operator ID field for indicating an operator ID; A password field for indicating a password of the operators; A login flag field for indicating a login status of the operators; And And a class field for indicating the class of the operators. The method of claim 2, wherein the MIB table, And the information of the operators of the element management system and the command line interface is updated each time. The method of claim 2, wherein the SNMP agent, And checking a session of each operator using a login flag field of the management information base table. In a network system consisting of an element management system including a simple network management protocol (SNMP) manager and a network element including an SNMP agent, a command interface and a management information base (MIB) table, multiple operators of the element management system and the command interface In the method of integrated management of the information through the MIB table, A first step of determining whether an operator ID and a password inputted to log in through one of the element management system and the command interface exist in the MIB table; If it is determined that the operator ID and password exist in the MIB table, determining whether the operator's login flag is displayed in the MIB table as being logged in; A third step of displaying the log in flag as an error if the log in flag is displayed in a log in state; A fourth step of setting the log-in flag to a log-in state when the log-in flag is displayed to be logged out in the second step; A fifth step of determining a grade of an operator displayed in the MIB table when the login flag is set to a logged in state; A sixth step of enabling a corresponding function according to the determined operator's level; And And if the execution of the corresponding function is finished, setting a login flag of the MIB table to a logout state. The method of claim 5, wherein the first step, And when the operator logs in through the element management system, the element management system searches for the MIB table using GetRequest and GetNextRequest messages in an SNMP message. The method of claim 5, wherein the second step, And when the operator logs in through the element management system, the element management system sets a login flag of the MIB table using a SetRequest message among SNMP messages. The method of claim 5, wherein the sixth step, If the operator's level is the administrator (ADMIN), the operator information integration management method, characterized in that it is allowed to perform the function of registering, changing and deleting the operator information. In a network system consisting of an element management system including a simple network management protocol (SNMP) manager and a network element including an SNMP agent, a command interface and a management information base (MIB) table, multiple operators of the element management system and the command interface In the method of integrated management of the information through the MIB table, Transmitting, by the SNMP manager, a polling message to the SNMP agent by using a login flag displayed in the MIB table; Receiving, by the SNMP agent, the polling message and determining whether the login flag is set to a login state; A third step of setting and down counting a current count value to a predetermined value by operating an internal timer for checking a session of the operator if the login flag is set to a logged in state; Setting a log-in flag of the MIB table to a logout state when the down counted value is “0”; And And if the down counted value is not "0", including a fifth step of performing the second step. The method of claim 9, wherein the third step, And setting the predetermined value to a polling period * 3.