KR100398725B1 - Interface Apparatus Between TMN Agent And MMS In Addition To System Management Method Using That Apparatus - Google Patents

Abstract

The present invention relates to an access device between a Telecommunication Agent Network (TMN) agent and an MMS and to a system management method using the device to use a binary message when managing an exchange system through a man-machine interface subsystem (MMS). In the case that TMN agent defines and accesses specific function blocks and specific signals and interfaces in the exchange system, when TMN agent adds, changes, or deletes certain management functions, it directly affects each function block of the TMN agent and the exchange system. When the TMN agent manages the switching system by accessing the MMS, the size of the message is large because the type of message sent and received is text, and it takes a long time to analyze and convert the message in the text form. There was a disadvantage of slow processing.

Accordingly, the present invention is to secure the management path between the TMN agent and the exchange system to collect management information corresponding to the management operation request of the TMN manager from the exchange system to the MMS, and then send and receive the message in binary form with the MMS By collecting the management information, it is possible to improve the scalability and maintainability due to the addition or change of new functions by the TMN manager, and to process the required management operation quickly.

Description

Interface Apparatus Between TMN Agent And MMS In Addition To System Management Method Using That Apparatus}

The present invention relates to an access device between a Telecommunication Management Network (TMN) agent and a Man-Machine Interface Subsystem (MMS) and a system management method using the device. In particular, the access path between the TMN agent and the switching system is limited to the MMS, The present invention relates to an access device between a TMN agent and an MMS that uses a binary message when managing an exchange system through the MMS, and a system management method using the device.

In general, a Telecommunication Management Network (TMN) is a network management structure proposed to provide management functions for communication networks and services and communication with the communication networks and services. By reflecting the status, it is possible to minimize the situation in which a low quality service occurs due to service disconnection or performance degradation in the communication network.

Therefore, it is necessary to know the situation in which the current communication network is operated by status report or collection from a switching system belonging to any communication network. However, if a large amount of management information is used for this purpose, real-time status collection becomes impossible due to the management information.

Meanwhile, the network management function is performed by the interaction between the TMN manager and the TMN agent. The TMN manager manages one or more management operations and requests the corresponding management operation service from the TMN agent. In response to the response, the TMN agent manages managed objects in its management area, performs a management operation service requested by the TMN manager, or informs the TMN manager of a notification message authorized from the managed object.

In addition, the TMN agent is required to manage a resource, that is, a hardware, software, data, and the like modeled as a managed object because a management operation in a real resource, that is, an exchange system, is required. The connection structure between the switching system is a structure that connects to transmit and receive information by defining specific signals between the corresponding TMN agent 12 and each functional block in the switching system 13 as shown in FIG. B) The TMN agent 12 is connected to the MMS (Man-Machine Interface Subsystem) 14 connected to the exchange system 13 to transmit and receive information in the form of text. System 13 management operations are performed as follows.

First, a system management operation in the case of transmitting and receiving information by defining a specific signal between the TMN agent 12 and each functional block in the switching system 13 will be described with reference to FIG. 2. The agent 12 defines a number of signals and interfaces capable of transmitting and receiving information with each of the functional blocks in the switching system 13 managed by the agent 12 (step S21), and then the management operation service is transmitted from the TMN manager 11 to the management operation service. It is ascertained whether a request is received (step S22).

At this time, when a request for a management operation service is received from the TMN manager 11, the TMN agent 12 signals a received management operation request, that is, a request in the form of a common management information protocol (CMIP), which is a network management protocol. It is converted into a function block inside the switching system 13 which actually needs to process the management operation request, and then transmitted to a corresponding function block of the switching system 13. Step S23).

Accordingly, the functional block inside the switching system 13 performs the corresponding management operation service according to the signal received from the TMN agent 12 (step S24), and then sends a signal predefined with the corresponding TMN agent 12. The result of performing the operation is transmitted (step S25).

Then, the TMN agent 12 receives the result of the operation performed by the functional block inside the switching system 13, converts it into CMIP type information, and transmits it to the TMN manager 11 (step S26).

At this time, when an event to be reported to the TMN agent 12 occurs in a specific function block inside the switching system 13, the function block transmits the event occurrence to the TMN agent 12 by using a predefined signal. The TMN agent 12 converts the event occurrence information of the received functional block into information in CMIP format and transmits the information to the TMN manager 11.

Secondly, a system management operation when the TMN agent 12 accesses the MMS 14 connected to the switching system 13 and transmits and receives textual information is described with reference to FIG. 3.

First, the TMN agent 12 checks whether a request for a management operation service is received from the TMN manager 11 (step S31), and receives a request for the management operation service from the TMN manager 11. The management operation request, that is, the request of the CMIP (Common Management Information Protocol) format, which is a network management protocol, into a text message in a form that can be recognized by the MMS 14 connected to the switching system 13 to the MMS 14. It transmits (step S32).

Accordingly, the MMS 14 that receives the management operation request in the form of a text message sent by the TMN agent 12 receives the corresponding functional block in the switching system 13 that must actually process the requested management operation. The management operation request is transmitted (step S33).

Then, the functional block inside the switching system 13 performs the necessary work according to the requested management operation, and then transmits the result of performing the work according to the management operation request to the MMS 14 (step S34). The received MMS 14 converts the message into a text message and transmits it to the TMN agent 12 (step S35).

Then, the TMN agent 12 analyzes the job execution result message according to the received management request in the form of text, converts the information into CMIP form, and transmits the information to the TMN manager 11 (step S36). In case of receiving a result message related to the failure, state change, etc. to be reported to the TMN manager 11 from the MMS 14, it is converted into information in CMIP form and transmitted to the corresponding TMN manager 11, and other result messages, In other words, the result message that does not need to be reported to the TMN manager 11 is discarded.

As described above, conventionally, when the TMN agent 12 defines and connects specific signals and interfaces with the respective functional blocks inside the switching system 13, there is no conversion operation for the message received at the corresponding TMN agent 12. By transmitting to the function block of the corresponding switching system 13, the message transmission and reception speed for system management is fast, while the modification of each function block stabilized by the system management function is inevitable, and addition to a predetermined function is performed. In the case of changing or deleting, there is a drawback that the TN agent 12 and the functional blocks of the switching system 13 are directly affected.

In addition, when the TMN agent 12 accesses the MMS 14 connected to the switching system 13 and transmits and receives a message in a text form, the TMN agent 12 affects each functional block of the corresponding switching system 13 that has been stabilized. The impact can be minimized, and when adding, changing, or deleting a certain function, it is very flexible to cope with the recombination of an existing MMC (Man Machine Command), the use of another MMC, and the application of a new MMC. Since the type of the message transmitted and received between the 12 and the MMS 14 is in the form of text, the size of the transmitted and received message is large, and the time for analyzing and converting the message in the corresponding text form is long, resulting in slow overall message processing. .

The present invention is to solve the problems as described above, the object is, after fixing the management path between the TMN agent and the exchange system to collect the management information corresponding to the management operation request of the TMN manager from the exchange system, MMS, By collecting the required management information by sending and receiving a message in binary form with the MMS, it is possible to improve the scalability and maintainability due to the addition or change of a new function by the TMN manager, and at the same time, perform the required management operation. To be able to do it quickly.

1 is a diagram illustrating a connection structure between a general TMN agent and a switching system.

2 is a flowchart illustrating a network management operation in the case of transmitting and receiving information by defining a specific signal between a conventional TMN agent and each functional block in a switching system.

3 is a flowchart illustrating a network management operation when a conventional TMN agent accesses an MMS and transmits and receives textual information.

4 is a diagram illustrating a connection device between a TMN agent and an MMS according to the present invention.

5 is a flowchart illustrating an operation for receiving and processing a management operation request from a TMN manager in the access device of FIG. 4.

6 illustrates a message structure in the form of a system ID transmitted to a TMN agent connection in the operation of FIG.

7 is a flowchart illustrating an operation of receiving and processing a notification message from an MMS in the access device of FIG. 4.

Explanation of symbols on the main parts of the drawings

40: TMN Manager 50: TMN Agent

61: TMN agent connection unit 62: message processing unit

62-1: message analyzer 62-2: MMC result analyzer

62-3: MMS message format tree 63: MMS connection

70: MMS

A feature of the present invention for solving the above object is, in the connection device between the TMN agent and the MMS to collect and report the system management information according to the management operation request of the TMN manager by fixing the switching system management path to the MMS, A message processing unit for generating and performing a management task according to a management operation request of the TMN manager and terminating a corresponding management task when receiving a result message from the MMS side; A TMN agent access unit for transmitting and receiving management information in association with a specific process of the TMN agent, and performing a mutual conversion function on messages transmitted and received between the TMN agent and a message processing unit; Receives a notification message from the MMS and transmits it to the message processing unit, and transmits an MMC message according to a management operation in conjunction with the MMS or receives a result message according to the MMC message transmission to the message processing unit, It includes an MMS access unit that performs a mutual conversion function for the messages transmitted and received between the message processing unit.

The message processor may include a message analyzer configured to analyze a management operation request received from a TMN agent access unit, generate a corresponding MMC, and transmit the MMC to the MMS access unit; An MMS message format tree unit for storing an MMS message format tree for analyzing an MMC message; In response to the MMS message format tree unit, the result message or notification message delivered from the MMS access unit is analyzed and transmitted to the TMN agent access unit, and if there is a change in a predetermined MMC message, the MMS message format tree of the MMS message format tree unit is analyzed. Reconstruct the MMC result characterized in that it further comprises.

If the TMN agent connection unit releases a connection for a specific process of a TMN agent, the TMN agent connection unit instructs the message processing unit to terminate the operation for a corresponding management operation to terminate the corresponding operation. The MMS may be connected to the MMS using a login and password obtained by transmitting a specific signal to the MMS.

Another feature of the present invention includes the steps of converting a CMIP type management operation request received from a TMN manager into a message of a system ID type; Converting and transmitting the system ID message into a management operation request message that can be used by a message processor; Creating a task for the requested management operation and performing a corresponding management task; Sending an MMC message to the MMS, requesting a predetermined result message, and suspending the management work; Receiving the MMC result message from the MMS, converting the MMC result message into a binary message, and delivering the message to the message processor; Receiving and analyzing the binary message and resuming management by using the analyzed MMC result message; And collecting a result that satisfies the management operation request of the TMN manager and transmitting a corresponding job execution result message.

In addition, another aspect of the invention, the process of converting the notification message received from the MMS to a binary message that can be used in the message processing unit and transmitting; Analyzing the binary message using an MMS message format tree; Converting the analyzed notification message into a system ID message and transmitting the same to the TMN agent.

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

In the present invention, the TMN agent fixes the management path for collecting the necessary management information from the switching system according to the management operation request of the TMN manager to the MMS, and transmits and receives a binary message with the corresponding MMS, for this purpose the TMN agent and the MMS As shown in FIG. 4, the connection device between the two devices includes a TMN agent connection unit 61, a message processing unit 62, and an MMS connection unit 63.

The TMN agent connection unit 61 transmits and receives management information in association with a specific process of the TMN agent 50, performs a mutual conversion function for the message transmitted and received between the TMN agent 50 and the message processing unit 62, When the connection with the specific process of the TMN agent 50 is released, the message processing unit 62 instructs the end of the operation for the corresponding management operation.

When the message processing unit 62 receives a management operation request from the TMN agent connection unit 61, the message processing unit 62 generates and performs a job on the requested management operation, and receives a result message from the MMS connection unit 63. This includes ending the message analysis unit 62-1, the MMC result analysis unit 62-2, and the MMS message format tree unit 62-3.

Here, the message analyzer 62-1 analyzes a management operation request received from the TMN agent connection unit 61, generates a corresponding man-machine command (MMC), and transmits it to the MMS connection unit 63. When the job termination request message for the predetermined management operation is received from the agent connection unit 61, the corresponding job is terminated.

The MMC result analysis unit 62-2 analyzes the MMC type result message or notification message for the management operation transmitted from the MMS connection unit 63 in conjunction with the MMS message format tree unit 62-3 to connect the TMN agent. Configure the message to be forwarded to (61). When there is a change in the predetermined MMC message, the MMS message format tree of the MMS message format tree unit 62-3 is reconstructed.

The MMS message format tree unit 62-3 stores an MMS message format tree for analyzing an MMC type message.

In addition, the MMS access unit 63 receives a notification message from the MMS, and in connection with the MMS 70 transmits an MMC message according to a management operation or receives a result message according to the transmission of the MMC message, but the MMS 70. ) And the message conversion unit 62 performs a mutual conversion function for messages transmitted and received, wherein the connection with the corresponding MMS 70 is connected by using a login and password obtained by transmitting a specific signal to the MMS 70. After analyzing the result message obtained by transmitting the MMC message received from the message processing unit 62 to the MMS 70 after connecting with the corresponding MMS 70, a function failure or status message in the switching system from the MMS 70 is analyzed. If is received and delivers it to the message processing unit 62.

Meanwhile, the system management operation in the TMN agent 50 according to the present invention is divided into an operation of receiving and processing a management operation request from the TMN manager 40 and an operation of receiving and processing a notification message from the MMS 70. With reference to the accompanying drawings, each operation is as follows.

First, an operation of receiving and processing a management operation request from the TMN manager 40 will be described with reference to FIG. 5. Referring to FIG. 5, the TMN agent 50 requests a management operation service from the TMN manager 40. When it is received (step S51), the received management operation request, that is, a request of CMIP type, which is a network management protocol, is transmitted to the TMN agent connection unit 61. In this case, the TMN agent connection unit 61 can recognize the request. The message is converted into a message in the form of a system ID (System IDentifier), which is a message, and transmitted to the TMN agent connection unit 61 (step S52).

Here, the message in the form of a system ID transmitted to the TMN agent connection unit 61 is a simple data packet having a structure as shown in FIG. 6A, or a complex having a structure as shown in (B). The data packet is accommodated in the data packet. The data packet includes a field indicating version information of the packet, a field indicating packet information (simple data packet, a complex data packet), and the presence or absence of additional packets. A field for displaying information about the packet, a field for displaying the serial number of the packet (Sequence #), a field for displaying information about the packet sender, and a field for displaying information about the packet receiver. (Destination), a field indicating information on the length of the entire packet, a field indicating information on the function of the information in the packet, and a delimiter used when the same function is required multiple times. Display Field indicating the number of information units consisting of [Serial No] and [System ID: Type: Attribute Value] which are messages in the form of System ID contained in the packet. Count), the System ID field (System ID) indicating the attribute separator, the type field (Type) indicating the type of the attribute value separated by the system ID, and the attribute value field indicating the attribute value (divided by the system ID). Contains (Value).

On the other hand, the TMN agent connection unit 61 converts and transmits a message in the form of a system ID received from the TMN agent 50 into a management operation request message in a form that can be used by the message processing unit 62 (step S53). The MMS connection unit 63 of the message processing unit 62 having received this generates a job for the requested management operation, and then performs the created job (step S54).

At this time, the management operation request message transmitted to the message processing unit 62 includes a plurality of fields as shown in Table 1 below.

field Explanation xaiName Indicates the identifier of the TMN agent connection that received the management operation request from the TMN agent. sockNo Indicates the TCP / IP socket number on which a management action request from the TMN agent was received. primitive Display information about management action requests from TMN agents moreBitPktType Display information on the type of packet and the presence of additional packets serialNo Delimiter used when the same function is required multiple times attrGrpCnt Indicates the number of information units consisting of messages in the form of system IDs contained within the packet. seqNo Displays the serial number of the unit by which the management operation request from the TMN agent is decomposed into predetermined byte units. length Indicate the length in bytes of information that the current message holds. data Display information consisting of messages in the form of system IDs

In Table 1, the message in the form of a corresponding system ID is composed of [System ID: Type: Attribute Value].

If necessary, the MMC message is transmitted to the MMS 70 through the MMS connection unit 63 to request a predetermined result message, and the job is temporarily suspended until the corresponding MMC result message is received. At step S55, the MMC message transmitted from the message processor 62 to the MMS access unit 63 includes a plurality of fields as shown in Table 2 below.

field Explanation vmName Indicates the delimiter of the message processing unit that causes the MMC opId Display MMC Separator mmcStr Display a string representing the MMC

On the other hand, the MMS access unit 63 transmits the MMC message received from the message processor 62 to the MMS 70 connected thereto, and accordingly, when the MMC result message is received from the MMS 70, the message processor (MMS) is processed. 62 is converted into a MMC result message in binary form that can be used in step 62, and is transmitted to the message processing unit 62 (step S56).

Here, the MMC result message in binary form transmitted from the corresponding MMS access unit 63 to the message processor 62 includes a plurality of fields as shown in Table 3 below.

field Explanation portjob Displays port number used when MMS connection is connected with MMS and job number assigned to MMC by MMS. timeunit Indicate the transmission period (time × unit) when sending multiple messages rpts Display information about the end of the message type Indicates the type of fault or MMC result message (alarm message, fault message, status message, MMC message). prn Display the fault or MMC result number inputpid Indicates the process separator that requested the MMC opId Displays the MMC delimiter assigned by the message processor ctx Display MMC results in binary form

On the other hand, when the message processing unit 62 receives a binary MMC result message from the MMS connection unit 63 while suspending the operation for the requested management operation, and the MMS message format tree unit 62-3; After analyzing the MMC result message in binary form received in association (step S57), the operation is resumed using the analyzed MMC result message (step S58).

In this case, the analyzed MMC result message includes a plurality of fields as shown in Table 4 below.

field Explanation vmName Delimiter of the message processing part that originated MMC taskId Displays the job separator assigned by the message processor analNo Displays the MMC result message delimiter in binary form assigned by the message processor serialNo Delimiter assigned when the same function is required multiple times on the TMN agent flag Displays information about the success or failure of MMC messages in binary form. seqNo Display analysis result serial number for MMC message in binary form length Displays the length of the analysis result for binary MMC messages accepted by the current message. data Display analysis results for MMC messages in binary form

Subsequently, the message processing unit 62 checks whether a result meeting the management operation request of the TMN manager 40 has been collected while performing the operation for the requested management operation (step S59), and the satisfied result is collected. If not, the flow returns to step S54 to repeat the management operation associated with the corresponding MMS 70.

In addition, when the result of confirming whether the result satisfying the request of the TMN manager 40 is collected is collected, the message processing unit 62 transmits a task execution result message according to the requested management operation to the TMN agent connection unit 61. The TMN agent connection unit 61 converts the received result message into a message of a form as shown in FIG. 7 and transmits it to the TMN agent 50 connected thereto (step S60). The system management work in accordance with the management operation request of 40 is completed.

At this time, the job execution result message transmitted from the message processor 62 to the TMN agent access unit 61 includes a plurality of fields as shown in Table 5 below.

field Explanation xaiName Identifier of TMN agent connection to send response to management action request to TMN agent sockNo Indicates the TCP / IP socket number to which to send a response to a management action request to the TMN agent. primitive Display response information for management action requests sent to TMN agents pktType Display the type of packet serialNo Delimiter received from the TMN agent attrGrpCnt Indicates the number of information units consisting of messages in the form of system IDs contained within the packet seqNo Displays the serial number of the message sent to the TMN agent connection. length Indicate the length in bytes of information that the current message holds. data Display information stored in the current message

Secondly, the operation of receiving and processing a notification message from the MMS 70 will be described with reference to FIG. 7. When the TMN agent 50 and the MMS 70 are connected, they are transmitted from the MMS 70. When the MMS connection unit 63 receives the notification message to be used (step S71), the MMS connection unit 63 converts the received notification message into a notification message in binary form that can be used by the message processing unit 62, and then executes the message processing unit ( 62) (step S72), where the notification message includes the exchange system information that should be notified to the TMN manager 40, that is, information about a function failure or a state change for each functional block of the exchange system. do.

On the other hand, the MMC result analysis unit 62-2 of the message processing unit 62 that has received the binary notification message from the MMS connection unit 63 checks whether or not the corresponding notification message should be transmitted to the TMN agent 50 (step). S73) If it is not necessary to transmit to the TMN agent 50, the received notification message is ignored (step S74).

However, when it is necessary to transmit the notification message received in step S73 to the TMN agent 50, the corresponding MMC result analysis unit 62-2 performs a corresponding message processing operation, at this time, the received notification message MMS message After analyzing in conjunction with the format tree 62-3 (step S75), the analyzed notification message is converted into a predetermined notification message for transmission to the TMN agent 50 side.

When the MMC result analyzer 62-2 of the message processor 62 completes the conversion of the notification message for transmission to the TMN agent 50, the corresponding message processing operation is terminated, and then the completed notification message is completed. Is transmitted to TMN agent connection part 61 (step S76).

Accordingly, the TMN agent connection unit 61 converts the received notification message into a message in the form of a system ID which is a defined message form with the TMN agent 50 and transmits the message to the TMN agent 50 connected thereto (step S77). .

As described above, in the present invention, the TMN agent 50 fixes the path for collecting necessary management information from the exchange system to the MMS 70, thereby satisfying the request of the TMN manager 40 in the TMN agent 50. While collecting sufficient management information, the impact on each stabilized functional block of the switching system can be minimized.

In addition, it is easy to expand or add new functions by the TMN manager 40, and to flexibly maintain the software related to the connection with the TMN agent 50 and the MMS 70 or the change of the MMS message format. You can cope.

In particular, in the management operation for each functional block of the switching system in association with the MMS 70, the size of the transmitted and received messages can be reduced by performing transmission and reception with the corresponding MMS 70 in a binary message. The conversion process is simplified, improving system management performance while using less resources.

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, according to the present invention, after the management path between the TMN agent and the exchange system for collecting management information corresponding to the management operation request of the TMN manager from the exchange system is fixed to the MMS, the message is transmitted and received in binary form with the corresponding MMS. By collecting the required management information, it is possible to improve the scalability and maintainability due to the addition or change of new functions by the TMN manager, and to promptly handle the required management operation.

Claims (12)

A connection device between a TMN agent and an MMS that fixes a switching system management path to an MMS and collects and reports system management information according to a management operation request of a TMN manager. A message processing unit for generating and performing a management task according to a management operation request of the TMN manager and terminating a corresponding management task when receiving a result message from the MMS side; A TMN agent access unit for transmitting and receiving management information in association with a specific process of the TMN agent, and performing a mutual conversion function on messages transmitted and received between the TMN agent and a message processing unit; Receives a notification message from the MMS and transmits it to the message processing unit, and transmits an MMC message according to a management operation in conjunction with the MMS or receives a result message according to the MMC message transmission to the message processing unit, And a MMS connection unit for performing a mutual conversion function on messages transmitted and received between message processing units. The method of claim 1, The message processor may include: a message analyzer configured to analyze a management operation request received from a TMN agent access unit, generate a corresponding MMC, and transmit it to an MMS access unit; an MMS message storing an MMS message format tree for analyzing an MMC type message; A format tree section; In response to the MMS message format tree unit, the result message or notification message delivered from the MMS access unit is analyzed and transmitted to the TMN agent access unit, and if there is a change in a predetermined MMC message, the MMS message format tree of the MMS message format tree unit is analyzed. Device for connecting between the MN agent and MMS further comprises a reconstructing MMC result analysis unit. The method of claim 1, The TMN agent connection unit, when the connection with a specific process of the TMN agent is released, instructs the message processing unit to terminate the operation for a corresponding management operation to terminate the corresponding job, characterized in that the connection between the TMS agent and MMS Device. The method of claim 1, The MMS access unit is connected to the MMS using the login and password obtained by transmitting a specific signal to the MMS to connect to the MMS agent and the MS. Converting the CMIP type management operation request received from the TMN manager into a system ID type message; Converting and transmitting the system ID message into a management operation request message that can be used by a message processor; Creating a task for the requested management operation and performing a corresponding management task; Sending an MMC message to the MMS, requesting a predetermined result message, and suspending the management work; Receiving the MMC result message from the MMS, converting the MMC result message into a binary message, and delivering the message to the message processor; Receiving and analyzing the binary message and resuming management by using the analyzed MMC result message; And collecting a result that satisfies the management operation request of the TMN manager and transmitting a corresponding job execution result message. The method of claim 5, The management operation request message includes a field indicating a delimiter for the TMN agent connection unit that has received the management operation request, a field indicating a TCP / IP socket number where the management operation request has been received, and information on the management operation request. Information consisting of a field, a field indicating information about a packet type and whether there is an additional packet, a field indicating a delimiter used when the same function is required multiple times, and a system ID message contained in the packet. A field indicating the number of units, a field indicating the serial number of the unit in which the management operation request is decomposed into predetermined bytes, a field indicating the length of information held in the message, and information stored in the message. And a field for displaying the system management method using a connection device between the T & M agent and the MS. The method of claim 5, The MMC message includes a field for displaying a separator for a message processing unit for generating an MMC, a field for displaying an MMC separator, and a field for displaying a string representing an MMC. System management method using device. The method of claim 5, The analyzed MMC result message may include a field indicating a separator of a message processing unit that generated the MMC, a field indicating a job separator allocated by the message processing unit, and a message separator of a binary form allocated by the message processing unit. Field, a field indicating a delimiter allocated when the same function is required several times in the TMN agent, a field indicating information on whether the analysis of the binary message is successful, and a message for the binary message. TN agent comprising a field indicating a serial number of an analysis result, a field indicating a length of an analysis result of the binary message, and a field displaying a result of the analysis of the binary message. System management method using a connection device between MMS. The method of claim 5, The work execution result message includes a field indicating a delimiter of a TMN agent connection unit to which a response to a management operation request is sent, a field indicating a TCP / IP socket number to which a response to the management operation request is sent, and a management operation request. Field indicating the number of information units consisting of a field indicating a response information for a packet, a field indicating a packet type, a field indicating a delimiter received from a TMN agent, and a system ID message contained in the packet. And a field indicating a serial number of a message transmitted to the TMN agent connection unit, a field indicating a length of information held by the message, and a field indicating information stored in the message. System management method using the connection device between TMS agent and MMS. Converting the notification message received from the MMS into a binary message that can be used by the message processor; Analyzing the binary message using an MMS message format tree; And converting the analyzed notification message into a message of a system ID form and transmitting the message to a TMN agent. The method of claim 5 or 10, The system ID type message is accommodated in a predetermined data packet, and the data packet includes a field indicating version information of the packet, a field indicating type information of the packet, a field indicating information about the presence or absence of an additional packet, and Field for displaying the serial number of the packet, field for information about the packet sender, field for information about the packet receiver, field for information about the length of the entire packet, A field for displaying information about a function, a field for displaying a delimiter used when the same function is required multiple times, a field for displaying the number of information units including a message of a system ID type contained in a packet, and an attribute. The system ID field indicating the delimiter, the type field indicating the type of the attribute value separated by the system ID, and the attribute value separated by the system ID System management method using a connection device between the T & M agent and the MS, characterized in that it comprises an attribute value field to display. The method of claim 5 or 10, The binary message may include a field indicating a port number used when connecting to the MMS and a job number assigned to the MMC by the MMS, a field indicating a transmission period when transmitting a plurality of messages, and information about the end of the message. Field indicating the type of fault or MMC result message, field indicating the fault or MMC result number, field indicating the process separator requesting MMC, and MMC identifier assigned by the message processor. And a field for displaying a MMC result in binary form, the system management method using a connection device between a T & M agent and an MS.