KR100421544B1 - Method of Managing Commands in the Manager's Interface System - Google Patents

Abstract

The present invention relates to a command processing method in an operator interface system in which an operator provides various types of message output to an operator in accessing information of an EMS agent system through an element management system (EMS) in an operator interface system. .

The method includes receiving an operator command from an EMS and converting the result into a character string form after syntax analysis; Converting the command in the form of a character string into a first UDP packet data form and delivering the same to an EMS agent system; Analyzing data received in the form of first UDP packet data in the EMS agent system, performing a command, converting the result into a form of second UDP packet data, and delivering the result to the EMS; And displaying the result message received from the EMS agent system in the EMS as it is.

Description

How to handle commands in operator interface system {Method of Managing Commands in the Manager's Interface System}

The present invention relates to a command processing method in an operator interface system, and more particularly, to a command processing method in an operator interface system in which an operator provides various types of message output to an operator in accessing information of an EMS agent system through an EMS. .

In general, there are two methods of physically connecting the EMS agent system and the EMS through RS232C or LAN or IP (Internet Protocol) network. The S / W scheme using the physical connection network ( The scheme is briefly described as follows. Here, the EMS refers to a system that manages each element system in one place.

First, as shown in FIG. 1, by processing data using a serial port between an EMS agent system 11 and an EMS 12, various commands and a graphical interface of an operator are processed. And transmits the status information message generated by the system itself.

Secondly, as shown in FIG. 2, transmission and reception information between the operator and the management system using the LAN is transfer data between the EMS agent system 13 and the EMS 14 using a LAN, such as UDP or TCP (Transfer Control Protocol), It is delivered after encapsulation in the IP protocol.

3 is a block diagram illustrating mutual information transfer of text commands and system messages between a general EMS and an EMS agent system.

As shown in FIG. 3, fixed packet data is transmitted and received between the EMS 15 and the EMS agent system 16. The EMS 15 includes a manager process and a user interface block. And an UDP, IP, and a network-dependent protocol. The EMS agent system 16 includes an agent process, an EMS data interpretation and transport block, UDP, IP, It is composed of network dependent protocols and connects different networks in communication. In this case, the operator interface using UDP converts a text command into a UDP packet format and delivers the data to the EMS agent system in a fixed size. The GUI is also converted into a text command and converted into a UDP packet. After formatting, the message is transmitted to the EMS agent system 16, and the status related message generated by the EMS agent system 16 is also transmitted to the EMS 15 after the UDP packet is formatted.

4 is a diagram illustrating text command UDP packet data of an existing operator.

As shown in FIG. 4, the text command UDP packet data includes a message type MT, a type T0 to T2 and a value V0 to V2 within a predetermined size S, where the size S Represents the data size promised between EMS agent system and EMS, and the corresponding message type (MT) is a user command message, a user command response message, and an access gateway status message (eg, 'Alarm', 'Fault', 'Status', etc.). The type (T0 ~ T2) indicates the setting of the promised data type (eg, 'integer', 'short', 'char', etc.) between the EMS agent system and the EMS, and the corresponding value (V0 ~ V2). ) Represents a value set by the type (T0 to T2).

4 defines the data characteristics sent in the message type (MT) portion, the type (T0 ~ T2) and the value (V0 ~ V2) is not a flexible form is determined for each position between the EMS and EMS agent system The value according to is defined. Accordingly, the type (T0 ~ T2) and the number of values (V0 ~ V2) are defined and the value of the size (S) also has a fixed value according to the system, which is called fixed UDP data.

In addition, the EMS agent system and the EMS are interpreted in a fixed data format determined by the developer to perform a job corresponding to each command.

Meanwhile, the operator command processing function in text command format for the EMS agent system will be briefly described as follows.

When an operator inputs an operator command (eg, 'CHG-CLK-MSTR (Change Clock Master)') through the text command input window provided by EMS, the HMI block recognizes and processes the text command of the input operator. That is, after performing the text format parsing (String Format) of the operator, it is loaded in UDP in the already promised text format as shown in FIG. 4 and delivered to a specific port of the EMS agent system.

In this case, the EMS agent system sets a specific port as an operator text command dedicated port, receives the UDP message through the corresponding port, recognizes an operator command, and executes a command such as parsing.

Next, the GUI processing function for the EMS agent system will be briefly described as follows.

The EMS provides the operator with a graphical interface for more convenient equipment management. When the operator accesses the EMS agent system using the GUI provided by the EMS, the operator provides access to the operator in the block that provides the GUI function in the EMS. Is converted into the text command format of the operator as described above, and then transferred to the EMS agent system through the HMI block.

At this time, the EMS prepares a window for the result value separately and displays a message on the processing result in a window. The EMS is set as a user command response in FIG. 4.

The operation of the message output and the information graphic display of the status of the EMS agent system will be briefly described as follows.

The EMS agent system delivers the status-related message that needs to be informed to the operator in the form of UDP packet data and delivers it to the EMS.In this case, the EMS has a fixed format of data on the output format of the message. It sends the value in the form of parameter to each fixed output form and outputs it in the form of a text message to the operator.

In addition, the graphic display also delivers the same fixed parameter values as UDP packet data, and EMS assigns each parameter to the graphic display to display to the operator.

However, in the conventional technology as described above, the operator text command is a fixed format of the UDP data format, and various outputs for the operator's recognition are not possible. Therefore, when the specific message output is changed in the S / W block of the EMS agent system, There is a problem in that limited elements of the message output such as related data also need to be changed.

In order to solve the problems as described above, the present invention provides an operator interface system for equipment subjected to the operation maintenance control through the EMS, the operator to ensure that the operator has the optimal stability and convenience in EMS agent system management Its purpose is to implement the function of accessing information of EMS agent system through EMS.

In addition, the present invention transmits the operator text command to the EMS agent system in a flexible form rather than a fixed form in the operator interface system, the corresponding EMS agent system in each S / W block in a flexible form the processing result message By freely expressing in, it provides the operator with various forms of message output, and frees text command processing and message output changes according to S / W changes.

1 is a diagram illustrating an interface between an element management system (EMS) agent system and an EMS as an example.

2 is a diagram illustrating another example of an interface between an EMS agent system and an EMS.

3 is a block diagram illustrating mutual information transfer of a text command and a system message between a conventional EMS and an EMS agent system.

FIG. 4 is a diagram illustrating a text command UDP (User Datagram Protocol) packet data of an operator in FIG. 3. FIG.

5 is a diagram illustrating an interface between an EMS agent system and an EMS according to an embodiment of the present invention.

FIG. 6 is a diagram illustrating Human Machine Interface (HMI) UDP packet data transmitted from EMS to EMS agent system in FIG. 5; FIG.

FIG. 7 is a diagram illustrating HMI UDP packet data transmitted from an EMS agent system to an EMS in FIG. 5. FIG.

8 is a block diagram illustrating mutual information transfer of a graphical user interface (GUI) message between an EMS agent system and an EMS according to an embodiment of the present invention.

FIG. 9 illustrates the format of a Simple Network Management Protocol (SNMP) message for the GUI in FIG. 8; FIG.

10 is a block diagram illustrating an interface function between an EMS agent system and an EMS according to an embodiment of the present invention.

11 is a flowchart illustrating a command processing method in an operator interface system according to an exemplary embodiment of the present invention.

12 is a flowchart illustrating a GUI processing method in an operator interface system according to an exemplary embodiment of the present invention.

13 is a flowchart illustrating a system state information processing method in an operator interface system according to an exemplary embodiment of the present invention.

Explanation of symbols on the main parts of the drawings

20: EMS 30: LAN (Local Area Network)

40: EMS agent system

41: EIC (Element Interface Control)

42-1 ~ 42-3: S / W Block (Software Block)

In order to achieve the above object, a command processing method in an operator interface system according to an embodiment of the present invention includes: receiving an operator command from an EMS and converting a result into a character string after syntax analysis; Converting the command in the form of a character string into a first UDP packet data form and delivering the same to an EMS agent system; Analyzing data received in the form of first UDP packet data in the EMS agent system, performing a command, converting the result into a form of second UDP packet data, and delivering the result to the EMS; And displaying the result message received from the EMS agent system in the EMS as it is.

Preferably, the command processing method in the operator interface system according to an embodiment of the present invention is a process of dividing a corresponding message into a corresponding message size unit when the message size of one of the second UDP packet data is greater than or equal to a predetermined message size. and; Transferring the second UDP packet data after allocating the message sequence of the second UDP packet data in the partitioning unit; And recognizing the message sequence to continuously output the received message as continuous data.

The present invention is applied to an access gateway product for the first time, and solves the problem of the interface between the operator through the EMS and the EMS agent system to be managed network, the convenience and accessibility of the EMS agent system through the EMS of the operator EMS agent To secure the system's versatility, the operator interface between EMS and EMS agent system is replaced with a new S / W function. In the EMS agent system, user access through the GUI is implemented using SNMP and operator text commands are processed in the HMI block. And it is about to send its own status-related messages to the upper EMS and to send its own board and failure information to the upper EMS as a trap using SNMP. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

5 is a diagram illustrating an interface between an EMS agent system and an EMS according to an embodiment of the present invention.

As shown in FIG. 5, the interface between the EMS agent system and the EMS is composed of an EMS 20, a LAN 30, and an EMS agent system 40. The EMS agent system 40 includes an EIC 41. ), And a plurality of S / W blocks 42-1 to 42-3, and the corresponding EIC 41 is a block for interfacing with the agent's management system. 42-3) to the agent management system, and the corresponding S / W blocks 42-1 to 42-3 are used for handling errors, status management, loading, management information base (MIB) management, ATM-related call processing blocks, etc. Software function blocks. Herein, in the present invention, three structures have been greatly improved, and the improved structure will be described as follows.

First, FIG. 6 is a diagram illustrating HMI UDP packet data used when the EMS 20 drops down to the EMS agent system 40. The HMI UDP packet data is 8 (Byte) which is encryption information for authentication. ), The operator text command is inserted, and the maximum size of the message is set to 1024 (Byte), for example, and the command is freely expressed as a character string within the corresponding range value.

In the text command of the EMS agent system through the EMS of the conventional operator, the form and the value of the instruction are set as the default (Default) and used, but in the present invention, as shown in FIG. In the text command of the EMS agent system 40 through the implementation of the variable packet data according to the size of the message and adding a community for authentication, the EMS 20 is performed. The text command of the operator is transmitted as the character string (char string) to the EMS agent system 40, the text in each S / W block (42-1 ~ 42-3) in the EMS agent system (40) It consists of parsing and parsing instructions.

Second, FIG. 7 is a diagram illustrating HMI UDP packet data used when the EMS agent system 40 uploads the EMS 20 to the EMS 20. The HMI UDP packet data is a message type of 2 bytes. ), A message sequence (Msg Seq) of 2 (Byte), and a message (Message) of 1024 (Byte).

When operating the EMS agent system 40, the GUI message and the text message are used to indicate the status information related to the system to the upper EMS 20. The GUI message extends the trap function among SNMP to indicate that the system is in a serious failure state. The alert displays alarm information, and the output of the text message can be divided into three categories: alarm, fault, and status. Each of these text messages is identified by the header of the message, for example, 'A ****', 'F ****' and 'S ****'. Assign a code number defined by the developer.

The format of the message may be arbitrarily configured in a flexible form instead of a fixed format in each of the S / W blocks 42-1 to 42-3. The format of the message may be in C Lang. It is a free form such as 'printf' to be used, and the message is delivered to the upper EMS 20 on UDP, so that the corresponding message size is also defined in a flexible form.

If the message type output from each of the S / W blocks 42-1 to 42-3 is larger than 1024 (Byte), the value of the message sequence portion Msg Seq shown in FIG. 7 is set. In order to display a continuous message.

Third, FIG. 8 is a block diagram illustrating mutual information transfer of GUI messages between the EMS 20 and the EMS agent system 40. The EMS 20 includes a manager process, a user interface block, and an SNMP. And the UDP, IP, and network dependent protocols. The EMS agent system 40 includes agent processes, EMS data interpretation and transport blocks, SNMP, UDP, IP, and network dependent protocols. It is made to include.

The operator's command by the conventional GUI is transferred to the EMS agent system after being converted into a text command and the command response is also responded to the text, but in the present invention, the operator's GUI is operated through the SNMP defined in FIG. In addition, the operator command through the GUI is converted into a set request message of the SNMP and transmitted to the EMS agent system 40 to operate, and the response also operates as a get response of the SNMP. .

At this time, the format of the SNMP message for the GUI is composed of a version (Version), a community (Community), an SNMP PDU, as shown in Figure 9, the corresponding SNMP PDU is a PDU type (PDU Type), This includes request IDs and variable-bindings.

The GUI command is defined in a variable binding part of a format of the SNMP PDU, and the EMS agent system 40 defines the GUI command as a corresponding MIB attribute. In addition, the variable binding part includes an object identify value for accessing a specific MIB attribute defined in SNMP and a plurality of object values.

10 is a block diagram illustrating the overall function of an interface between an EMS agent system and an EMS according to an embodiment of the present invention.

As shown in FIG. 10, a function (S10) of processing a text command of an operator in the form of UDP packet data is large, a function (S20) of processing an operator command of a GUI in the form of an SNMP message, and an EMS agent system 40. It includes three functions (S30) of transmitting its status information to the operator through the upper EMS 20 as a GUI display or text message display using SNMP.

First, a command processing method in an operator interface system according to an embodiment of the present invention will be described in detail with reference to the flowchart of FIG. 11 as follows.

First, when an operator sends an operator command in a text command format to the EMS 20, the HMI block in the EMS 20 receives an operator command in the corresponding text command format and performs syntax analysis. Is converted into a character string form (step S10-1), and the converted character string form instruction is converted back into the first UDP packet data form as shown in FIG. 6 and transferred to the EMS agent system 40. (Step S10-2).

At this time, the first UDP packet data type transmitted to the EMS agent system 40 is transmitted through a specific port of the EMS agent system 40 in a variable size as a character string rather than a conventional fixed data type.

In this case, the EMS agent system 40 defines and uses a command port for text separately. In this case, it is determined whether the command syntax is normal by analyzing each data input as a character string (step S10-3). If the command syntax is normal in the corresponding step 10-3 (S10-3), the command and variable are transmitted to the S / W blocks 42-1 to 42-3 to execute the command (step S10-4).

Accordingly, in each of the S / W blocks 42-1 to 42-3, after receiving a command and a variable and performing the command (step S10-5), the EMS agent system 40 sends the processing result to the EMS agent 40. Through the command processing process included in the interlocking block EIC 41, the second block transmits the data to the upper EMS 20 in the form of the second UDP packet data as shown in FIG. 7 (step S10-6). At this time, the second UDP packet data delivered to the upper EMS 20 is also freely represented in the respective S / W blocks 42-1 to 42-3 in the form of a character string like the first UDP packet data.

Then, the upper EMS 20 does not display the Text Command Result Message in a fixed format, but rather from the EMS agent system 40 so that it is provided in the same manner as 'printf' in Sea Lang. The received message itself is displayed as it is (step S10-7).

At this time, if the size of one message to be sent from the EMS agent system 40 to the upper EMS 20 exceeds the preset maximum size (for example, 1024 (Byte)), the message is transmitted in units of 1024 (Byte). After dividing, the message sequence Msg Seq shown in FIG. 7 is allocated in the unit of division and sent to the upper EMS 20.

The upper EMS 20 recognizes the message sequence and continuously outputs the received message as continuous data.

Second, the GUI processing method in the operator interface system according to an embodiment of the present invention will be described in detail with reference to the flowchart of FIG. 12 as follows.

First, when the operator sends the operator command by the GUI to the EMS 20, the graphic command processing block in the EMS 20 to SNMP the corresponding graphic interface, as shown in Figs. Step S20-1), the corresponding SNMP messaging means configuring the message according to the SNMP standard. Here, FIG. 8 illustrates mutual communication using standardized SNMP and UDP / IP between the EMS 20 and the EMS agent system 40, and FIG. 9 illustrates an SNMP message format of GUI commands. At this time, in the S / W block which performs GUI processing in the EMS 20, it is inserted into the object value item shown in FIG. 9 in the form of a character string (step S20-2).

The SNMP messaged GUI command is transmitted to the EMS agent system 40 in a Set Request Format through an SNMP interface (step S20-3).

Accordingly, the EMS agent system 40 performs a syntax analysis and parsing operation on the SNMP message received through UDP (step S20-4), in which case the corresponding SNMP message is a set and the portion of the SNMP UDP message part is processed. It checks the MIB information set with the object identification value and checks the case of accessing the property corresponding to the command of a specific MIB and recognizes it as a GUI command.

Then, the object value shown in FIG. 9 is read and character string analysis is performed to recognize the parameters (step S20-5), and the signal is transmitted to the related block.

That is, the analyzed command is transmitted to the S / W blocks 42-1 to 42-3 where each command is to be actually executed, and the corresponding S / W blocks 42-1 to 42-3 are commanded. The requested operation is performed (step S20-6).

Then, each S / W block 42-1 through 42-3 sends the resulting message to the EIC 41, and the corresponding EIC 41 passes through each S / W block 42-1 through 42-. 3) After the result message delivered from the SNMP message (step S20-7), and delivers to the upper EMS 20 in the form of a get response (step S20-8), the upper EMS 20 receives this message Is displayed in the operator window (step S20-9).

Referring back to the above description of the operation with reference to Figure 5, the GUI command entered by the operator is SNMP messaged and delivered to the EMS agent system 40 (part labeled 'S1'), the EMS agent system 40 ) The EIC 41 processing the SNMP interface receives the corresponding message to perform syntax analysis and parsing (parts marked as 'S2'), and the corresponding analyzed command is executed in the corresponding S / W where each command is actually executed. Signals are sent to blocks 42-1 through 42-3, and the corresponding S / W blocks 42-1 through 42-3 perform the corresponding operations required by the instruction (parts marked 'S3'), and as a result The message is delivered to the EIC 41 (indicated by 'S4'), and the EIC 41 gets the SNMP message after the result message delivered from each S / W block 42-1 to 42-3. The EMS 20 transmits the response to the EMS 20 and displays the message in the operator window. (Shown as 'S5').

Third, the system state information processing method in the operator interface system according to an embodiment of the present invention will be described in detail with reference to the flowchart of FIG. 13 as follows.

GUI display and text using SNMP to inform the operator of various system status information, that is, internal status of equipment, status of each board, visual failure status, etc. through the upper EMS 20 during operation of the EMS agent system 40. There are two types of message display. First, the EMS agent system 40 checks various system states during system operation to determine the format to be displayed on the EMS 20 side (step S30-1).

If the display format determined in step 30-1 (S30-1) is a GUI display format using SNMP, the EIC 41 in the EMS agent system 40 is assigned to each S / W block 42-1. 42-3) after the various system status information transmitted from the SNMP message as shown in Fig. 9 (step S30-2), and delivers to the upper EMS 20 in the form of a get response (step S30-3). The upper EMS 20, which receives this, displays the corresponding message in the operator window (step S30-4).

At this time, the GUI display uses the general trap information among the trap information to display system alarm information (for example, fault information such as system restart, booting, and link down). There is a graphical display, and the SNMP trap extension extends the trap function to graphically display alarm trap information that primarily conveys system alarm information (ie alarm information that indicates that the system is in serious failure). Here, the alarm information refers to information that can be physically displayed, such as a board function failure or a board delete.

On the other hand, when the display format determined in step 30-1 (S30-1) is a text message display format, the EIC 41 is transferred from each S / W block 42-1 to 42-3. Various system state information is converted into a text message of UDP data format as shown in FIG. 7 and transferred to the upper EMS 20 (step S30-5). At this time, the text message delivered to the EMS 20 is freely represented in the S / W blocks 42-1 to 42-3 in the form of a character string. In addition, as shown in FIG. 7, the text message delivered to the EMS 20 is provided with a message type value in a message type, and the message unit is divided into a predetermined size (for example, 1024 (Byte)). A consecutive number is assigned to the message sequence (Msg Seq) and the text message is put in a message item within the predetermined size and sent to the EMS 20.

At this time, the information of the text message is a status indicating a message level that informs a general operator, such as S / W alarm (Alarm) such as link failure information, subscriber status change in the EMS agent system 40 among the alarms (Status ), A fault indicating a message level indicating a slight error such as a data count mismatch in the EMS agent system 40, etc., may be displayed. Each fault is identified in the header of the message as, for example, 'A ****', 'F ****' and 'S ****'. Is assigned a code number defined by the developer.

Then, the EMS 20 does not display the text message transmitted from the EMS agent system 40 in a fixed format, but is provided in a flexible form in a free form such as 'printf' in Sea Lang, The message itself received from the EMS agent system 40 is displayed as it is. At this time, the message sequence is recognized and the received message is continuously displayed as continuous data (step S30-6).

As described above, according to the present invention, the operator text command is transmitted to the EMS agent system in a flexible form, and the EMS agent system enables the operator to freely express the processing result message in each S / W block in a flexible form. It provides various types of message output and can freely change text command processing and message output according to S / W change.

Claims (4)

Receiving an operator command from an EMS and converting the result into a character string form after syntax analysis; Converting the command in the form of a character string into a first UDP packet data form and delivering the same to an EMS agent system; Analyzing data received in the form of first UDP packet data in the EMS agent system, performing a command, converting the result into a form of second UDP packet data, and delivering the result to the EMS; And displaying the result message received from the EMS agent system in the EMS as it is. The method of claim 1, The first UDP packet data comprises a community which is encryption information for authentication, and a command that freely expresses an operator command as a character string within a preset message size range. The method of claim 1, The second UDP packet data comprises a message type, a message sequence, and a message freely expressed as a character string within a preset message size range. The method of claim 1, Dividing the corresponding message by a corresponding message size unit when the message size of the second UDP packet data is equal to or larger than a predetermined message size; Transferring the second UDP packet data after allocating the message sequence of the second UDP packet data in the partitioning unit; And recognizing the message sequence to continuously output the received message as continuous data.