KR100694230B1 - Remote engineering system and method by simple network management protocal standard management information base - Google Patents

Abstract

A remote engine system using SNMP(Simple Network Management Protocol) standard items and a method thereof are provided to manage an NE(Network Element) through a standard MIB(Management Information Base) according to mapping table information of a private MIB and the standard MIB. An SNMP manager(10) performs the remote engine according to an SNMP operation for at least one standard item. A management item mapper(20) converts result information of a private item mapped to the standard item processed from the NE according to the SNMP operation requested from the SNMP manager into the result information of the standard item and informs the SNMP manager of the converted result information. The management item mapper includes an SNMP agent module(23) checking private item information and common interface information mapped to the standard item from a mapping table loaded to a memory, a converting module(24), and a common interface module(25) providing a common interface between the SNMP module and the NE(30).

Description

REMOTE ENGINEERING SYSTEM AND METHOD BY SIMPLE NETWORK MANAGEMENT PROTOCAL STANDARD MANAGEMENT INFORMATION BASE}

1 is a diagram illustrating an example of a recompile process according to a change of a private MIB management item.

2 is an illustration of a remote engineering system using SNMP standard items in accordance with the present invention.

3 is a diagram illustrating a mapping template structure between a Standard MIB and a Private MIB according to the present invention;

4 illustrates a common interface structure in accordance with the present invention.

5 is a diagram illustrating a relationship between a Standard MIB and a Private MIB according to the present invention.

6 illustrates an example of a mapping template between a Standard MIB and a Private MIB according to the present invention.

7 is a diagram illustrating an example of a mapping table between a Standard MIB and a Private MIB according to the present invention.

8A and 8B illustrate a remote engineering process using a Standard MIB in accordance with the present invention.

Explanation of symbols on the main parts of the drawings

10: SNMP Manager 20: Network Equipment

21: Private MIB 22: Standard MIB

23: SNMP Agent 24: Converting Module

25: common interface unit 30: network elements

The present invention relates to a remote engineering system and method using SNP standard items.

Simple Network Management Protocol (SNMP) is a protocol for managing network information by a remote user. Most network devices operating in an IP network are managed using SNMP. Accordingly, SNMP models can easily change or inspect all management information functions.

Digital set-top boxes, which are currently used as network equipment, are home appliances that can watch and listen to video and audio, and are used as network equipment with IP (Internet Protocol). A service provider having such a set-top box manages a set-top box device of a service user remotely through a network.

For this purpose, the network equipment must implement SNMP, which is mostly used as a management protocol, so that remote engineering can be managed remotely.

In other words, in order to perform remote engineering, an SNMP agent must be implemented in a set-top box. In general, a commercial development tool is used to implement an SNMP agent. In this case, a MIB (Management Information Base) which selects items to be managed in a set-top box and changes them into a standard format defined by SNMP. Justice is needed.

The Management Information Base (MIB) is a collection-integrated information of all objects controlled by a specific agent or manager. The MIB is a very simple table that is easy to operate and is configured to connect quickly and effectively to most systems. It is.

In other words, the MIB is input to the SNMP development tool to generate the necessary code, and the vender specific code is inserted to operate the SNMP. Set-top box manufacturers must define the management items for the equipment they provide as MIBs. These MIBs are defined as the management items that are specific to the devices they develop. It is called.

Therefore, after implementing the SNMP agent by defining the MIB, and informs the operator to the private MIB, the SNMP manager (SNMP Manager) can manage the set-top box (vender specific).

In other words, the operator has a set-top box supplied from various manufacturers who provide various network equipments and receives a new vendor-specific management item every time, and it is a great burden to implement a new SNMP manager. The tendency is to create and manage standard items (hereinafter referred to as Standard MIBs) for items that need to be managed for each network device or home appliance that is used frequently.

Therefore, if the operator wants to manage the network equipment with SNMP by supplying the network equipment from several manufacturers, and if the product is classified as the same network equipment rather than remote engineering with a private MIB, Standard defined as a standard item. Remote engineering with the MIB is efficient. This makes network management easier, regardless of the vendor specific product.

However, when developing most products, development proceeds without recognizing the SNMP Standard MIB structure and management items. This is especially true for products that are not considered network equipment (Set-top box). As described above, in this case, the manufacturer defines and implements a vendor specific MIB.

In other words, operators usually want the standard MIB to operate for network device management, but the actual product's SNMP operation does not. Since the items or structures defined in the Standard MIB do not consider the vendor-specific program method or management structure, it is very difficult to implement the management items in the Standard MIB after the network equipment is developed.

As such, in the related art, a manufacturer defines a vendor specific MIB to implement an SNMP agent and provides a vendor specific MIB to a provider for SNMP operation. Accordingly, operators have no choice but to manage network equipment based on vendor specific MIBs provided by manufacturers.

In addition, if the manufacturer changes the management item (Private MIB) again and informs the operator of the changed management item information, the operator performs remote engineering through different management methods for each product. This is inconvenient because the vendor-managed items do not follow the standards.

In other words, when remote engineering is required, the manufacturer does not use the SNMP standard MIB, and the manufacturer defines a vendor specific MIB and provides it to the service provider. However, in the case of network equipment, a standard MIB exists and an operator requires standard MIB support for easier management. In the case of equipment that does not support the standard MIB, there was a problem that it is difficult to program the existing data structure or programming method accordingly.

Accordingly, an object of the present invention is to solve the above problems, the remote engineering system using the SNMP standard items to manage the network equipment through the Standard MIB according to the mapping table information of the Private MIB and Standard MIB and its In providing a method.

According to an aspect of a remote engineering system using an SNMP standard item according to the present invention for achieving the above object, from the SNMP manager for performing remote engineering in accordance with the SNMP operation on at least one standard item, and from the SNMP manager And a management item mapping unit for notifying the network manager by changing the result information of the private item mapped to the standard item processed from the corresponding network element according to the required SNMP operation.

The management item mapping unit may include: an SNMP agent module configured to check private item information and common interface related information mapped to the standard item from a mapping table loaded in a memory when receiving an SNMP operation for the at least one standard item; The result information of the private item mapped to the standard item processed from the corresponding network element is changed to the result information of the standard item according to the private item information mapped to the standard item identified from the SNMP agent module and the common interface related information. And a converting module for notifying an agent module and a common interface module for providing a common interface between the SNMP agent module and at least one network element.

The mapping table includes mapping table information between a Standard MIB and a Private MIB defining at least one standard item, and at least one table information among common interface table information.

The common interface table information may include at least one of table (privInfoTable) information about a network element that processes management items for at least one or more SNMP operations and transfer factor related table (privParamTable) information that is transmitted to the network element. Include.

The table (privInfoTable) information on the network element may include command index (privCmdIndex) information of the at least one SNMP operation, target IP (privTargetIP) information to perform the private MIB management item, and perform the private MIB management item. Target port (privTargetPort) information, command identifier (privCmdIdentifier) information to perform the private MIB management item, propagation factor number (privNumberOfParameter) information delivered to the target to perform the private MIB management item, and the private MIB management item. After the target command is executed, it includes at least one piece of information of result separator (privTransactionId) information.

The target IP (privTargetIP) information on which the Private MIB management item is to be performed is at least one of local IP information and remote IP information.

The propagation factor related table (privParamTable) information includes a value (privCmdExtnIndex) corresponding to the command index (privCmdIndex) of the table for the network element (privInfoTable), propagation factor index (privParamIndex) information, and propagation factor type (privParamType). Information, at least one of a propagation factor length (privParamLength) information and a propagation factor value (privParamValue).

Meanwhile, according to an aspect of a remote engineering method using an SNMP standard item according to the present invention for achieving the above object, a template indicating a mapping relationship between a standard MIB for at least one standard item and a private MIB for a private item ( creating a template, generating mapping table information between the standard MIB and the private MIB as XML information based on the created template, and receiving and analyzing the generated XML information when the SNMP agent is executed. Loading mapping table information into internal memory according to the analyzed XML information, recognizing a relationship structure between the Standard MIB and the Private MIB, and processing from the corresponding network element according to an SNMP operation request specified as a standard item. Changes the result information of the private item to the result information of the standard item. It consists of the system.

Meanwhile, according to an aspect of the method for setting a mapping table using an SNMP standard item according to the present invention for achieving the above object, a template indicating a mapping relationship between a standard MIB for at least one standard item and a private MIB for a private item creating a template, generating mapping table information between the standard MIB and a private MIB as XML information based on the created template, and receiving and analyzing the generated XML information when an SNMP agent is executed; And loading mapping table information into an internal memory according to the analyzed XML information, and recognizing a relationship structure between the standard MIB and the private MIB.

Meanwhile, according to one aspect of the method for converting mapping information using an SNMP standard item according to the present invention for achieving the above object, transmitting mapping table information loaded in an internal memory in response to an SNMP operation request designated as a standard item. And requesting an SNMP operation of the corresponding private MIB item from the corresponding network element according to the mapping table information, and converting a result value of the private MIB item processed and transmitted from the network element into a result value of the standard MIB item. And returning a result value of the converted Standard MIB item.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, detailed descriptions of preferred embodiments of the present invention will be described with reference to the accompanying drawings. It should be noted that reference numerals and like elements among the drawings are denoted by the same reference numerals and symbols as much as possible even though they are shown in different drawings. In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

1 is a diagram illustrating an example of a recompile process according to a change of a private MIB management item.

As shown in FIG. 1, first, an existing software and a management item definition file are redefined to a management item having a form defined in SNMP (S1).

Subsequently, after generating a private MIB (S2) to generate a handler source using an SNMP tool (S3), the generated handler source is modified (S4), and the existing software is modified (S5).

Such a method is a management method using a non-standard MIB method, and whenever a vendor-specific management item is changed, a manager and an SNMP agent recompilation process are continuously performed according to the change of the private MIB.

2 is a diagram illustrating a remote engineering system using an SNMP standard item according to the present invention.

As shown in FIG. 2, the network device management system of the present invention is largely composed of an SNMP manager 10, a network device 20, and a plurality of network elements 30.

The SNMP manager 10 commands an SNMP operation (get / get-next / get-bulk / set, notification) designated as a standard OID (Object ID) to the SNMP agent 23 of the network device 20.

Here, the get operation is an SNMP operation requesting a result value for a management item of a private MIB mapped to a standard OID (Object ID), and the set operation is a response message for a management item of a private MIB mapped to a standard OID (Object ID). An SNMP operation that requires ("OK" or "NOK").

And, notification means the status information that the SNMP manager 10 is periodically transmitted from the SNMP agent 23 of the network device 20.

The network device 20 is a device having an IP on the network, and includes a private MIB 21, a Standard MIB 22, an SNMP agent 23, a converting module 24, and a common interface unit ( Common Interface) 25.

The private MIB 21 is information that a manufacturer defines a management item of a corresponding network device according to a vendor specific method to implement an SNMP agent.

The Standard MIB 22 is standard MIB related information generated using a commercial tool, and the SNMP agent 23 generates mapping table information through the Private MIB 21 and the Standard MIB 22.

When the SNMP agent 23 receives an SNMP operation (get / get-next / get-bulk / set, notification) command designated as a standard OID (Object ID) from the SNMP manager 10, a mapping table loaded in the internal memory. The converting module 24 informs the converting module 24 of private MIB item information and common interface related table information mapped to the designated standard OID (Object ID) in the information.

The converting module 24 requests the SNMP operation to the corresponding network element through the common interface 25 according to the SNMP operation of the SNMP agent 23 and the SNMP of the requested private MIB item. When the operation result value is received from the corresponding network element, the private MIB item is converted into a standard OID (Object ID) mapped thereto, and the SNMP operation result for the converted standard OID (Object ID) is converted into the SNMP agent ( 23).

The network element 30 is an element for managing the management items defined through the private MIB of the network device for each item, and performs the SNMP operation of the requested private MIB item according to the SNMP operation request from the converting module 24. The result is transmitted to the converting module 24.

3 is a diagram illustrating a mapping template structure between a Standard MIB and a Private MIB according to the present invention.

As shown in Fig. 3, a template representing a mapping relationship between the Standard MIB and the structure used for the internal program of the network equipment is created. This template will contain information about elements that handle private structures.

The tag of TARGET_POSITION indicates the position of an element that handles a managed item, the COMMAND_ID tag is an identifier for classifying commands for a structure where the element that handles a managed item, and the OBJECTS tag is managed on a network device. Shows the relationship between the item and the standard MIB.

This mapping relationship is performed at the compiler stage. After reading the template above and converting it to XML format and providing it as an input value when executing the SNMP agent, the SNMP agent parses the XML and parses the Standard MIB. And Privet MIB relation structure is recognized and operated.

4 is a diagram illustrating a common interface structure according to the present invention.

As shown in FIG. 4, a mapping relationship is first formed, and an SNMP agent must provide a common interface to a network element that processes a management item. This is because the method designed above can operate at run-time only when a common interface is provided.

That is, as shown in FIG. 4, two structures should be defined for the relationship between the private MIB information and the common interface.

The first structure is a structure necessary for an SNMP agent to know information about a network element processing a management item, and the details thereof are as follows.

First, "unsigned int privCmdIndex; //" is a command index obtained from the SNMP manager, which means the number of commands.

And, "unsigned char privTargetIP [17]; //" means a target IP to perform a private MIB management item, and "unsigned short privTargetPort; //" means a target port to perform a private MIB management item. do.

And, "unsigned long privCmdIdentifier; //" means the command delimiter to perform the private MIB management item, "unsigned ing privNumberOfParameter; //" means the number of passed arguments to the target to perform the private MIB management item, "unsigned long privTransactionId; //" means the result separator after executing the target command of Private MIB management item.

The second structure is transfer factor information that the SNMP agent should deliver to the network element that processes the management item. The details of this are as follows.

"unsigned int privCmdExtnIndex; //" means the value that matches privCmdIndex in privInfoTable, "unsigned int privParamIndex; //" is the argument argument index, "unsigned short privParamType; //" is the argument type, " unsigned int privParamLength; // "means the length of the argument and" unsigned char * privParamValue; // "means the value of the argument.

For example, if you look at the argument information in Afunc (char * ptr), "char *" means that the type of the argument is an octet string, where the length of the string is in bytes and the value of the argument is a pointer. (pointer).

5 is a diagram illustrating a relationship between a Standard MIB and a Private MIB according to the present invention.

As shown in FIG. 5, the MAC address information of the interface among the items of the MIB-2 (RFC 1213) most commonly used in the standard MIB shows the mapping relationship with the private MIB when the SNMP Get command is executed. .

That is, although the standard MIB structure A and the private MIB structure B used in the network equipment are different from each other, the information required by the standard MIB and the structure structure defined in the private MIB are related.

As shown in FIG. 5, when the SNMP manager issues a command such as "Get 1.3.6.1.2.1.3.1.1.2.1" to the SNMP agent, the SNMP agent may include the "addressingDVBMACAddress" item and the Standard MIB in the private MIB structure (B). The structure of the relationship with the "atPhysAddress" item in the structure A is recognized. Here, the "1.3.6.1.2.1.3.1.1.2.1" means a standard Object ID (OID).

In addition, when the SNMP manager issues a command such as "Get 1.3.6.1.2.1.3.1.1.2.2" to the SNMP agent, the SNMP agent is assigned to the "addressingCMMACAddress" item of the private MIB structure (B) and the standard MIB structure (A). Recognizes the relationship structure with the "atPhysAddress" entry in.

In addition, when the SNMP manager issues a command such as "Get 1.3.6.1.2.1.3.1.1.2.3" to the SNMP agent, the SNMP agent is assigned to the "addressingCPEDeviceMACAddress" item in the private MIB structure (B) and the standard MIB structure (A). Recognizes the relationship structure with the "atPhysAddress" entry in.

In addition, when the SNMP manager issues a command such as "Get 1.3.6.1.2.1.3.1.1.2.4" to the SNMP agent, the SNMP agent is assigned to the "addressingCPEDeviceMACAddress" item of the private MIB structure (B) and the standard MIB structure (A). Recognizes the relationship structure with the "atPhysAddress" entry in.

6 is a diagram illustrating an example of a mapping template between a standard MIB and a private MIB according to the present invention.

As shown in Fig. 6, a template representing a mapping relationship between the Standard MIB and the structure used for the internal program of the network equipment is created. This template contains element information for processing a private structure.

First, in the case where TARGET_POSITION is LOCAL, the tag of TARGET_POSITION indicates that the position of the element that handles the management item is "local" and that the COMMAND TYPE tag is "GET". tag indicates "Ox1000".

In particular, the OBJECTS tag shows the relationship between the management items in the network equipment and the standard MIB. The "addressingDVBMACAddress" item in the private MIB is mapped to the "atPhysAddress" item in the standard MIB during the Get command of the SNMP manager.

In addition, the "addressingCMMACAddress" item of the private MIB is mapped to the "atPhysAddress" item of the standard MIB, and the "addressingSTBIPAddress" item of the private MIB is mapped to the "ipAdEntAddr" item of the standard MIB.

Meanwhile, referring to a case where TARGET_POSITION is a network element other than LOCAL, the tag of TARGET_POSITION indicates that the position of an element that handles a management item is “10.0.0.254:61000” and is COMMAND. The TYPE tag indicates "GET" and the COMMAND_ID tag indicates "Ox1002".

In particular, the OBJECTS tag represents the relationship between the management items in the network equipment and the standard MIB. It indicates that the "addressingCPEDeviceMACAddress" item in the private MIB is mapped to the "atPhysAddress" item in the standard MIB when the SNMP manager Get command is issued.

This mapping relationship is performed at the compiler stage. Based on the template created above, the relation between the standard MIB and the private MIB and the common interface related information are generated in XML. In this case, the reason for making XML is that the XML document format is an official document format that conforms to the standard, so that the program can be changed later or the program can be easily ported between different types.

When the generated information is provided as an input value when the SNMP agent is executed, the SNMP agent can recognize the structure of the relationship between the Standard MIB and the Privet MIB by parsing XML, and the information is shown in the table shown in FIG. 6 below. The information is loaded into the SNMP agent's memory.

7 is a diagram illustrating an example of a mapping table between a Standard MIB and a Private MIB according to the present invention.

As shown in FIG. 7, in the mapping information between the Standard MIB and the related Private MIB, the Object ID (OID) atPhysAddress.1 of the Standard MIB is mapped to the addressingDVBMACAddress of the related Private MIB, and atPhysAddress.2 is mapped to the addressingCMMACAddress of the related Private MIB. Mapped.

The Object ID (OID) atPhysAddress.3 of the Standard MIB is mapped to the addressingCPEDeviceAddress of the related private MIB, and atPhysAddress.4 is mapped to the addressingCPEDeviceAddress of the related Private MIB.

Meanwhile, in the common interface related information, privCmdIndex "1" is a command index (SN) from the SNMP manager, which means that the number of commands is 1, and privTargetIP "127.0.0.1" is a target to perform a private MIB management item. In this case, the target IP "127.0.0.1" means a local IP.

And, privTargetPort "0" means that the target port (Port) to perform the private MIB management item is 0, privCmdIdentifier "0x1000" means that the command identifier to perform the Private MIB management item is "0x1000".

And, privNumberOfParameter "1" means that the number of the transfer arguments delivered to the target to perform the private MIB management item is 1, privTransactionId "1" means that the result separator is 1 after the execution of the private MIB management item target command.

In addition, privCmdIndex "2" of the second line is the command index (SN) from the SNMP manager, which means that the number of commands is 2, and privTargetIP "127.0.0.1" means the target IP to perform the private MIB management item. At this time, the target IP "127.0.0.1" means a local IP.

And, privTargetPort "0" means that the target port (Port) to perform the private MIB management item is 0, privCmdIdentifier "0x1000" means that the command identifier to perform the Private MIB management item is "0x1000".

In addition, privNumberOfParameter "1" means that the number of the transfer factors delivered to the target to perform the Private MIB management item is 1, and privTransactionId "2" means that the result separator is 2 after executing the target command of the Private MIB management item.

In addition, privCmdIndex "3" of the third line is the command index from the SNMP manager, which means that the number of commands is 3, and privTargetIP "10.0.0.254" means the target IP to perform the private MIB management item. At this time, the target IP "10.0.0.254" means a remote IP (remote IP).

And, privTargetPort "61000" means that the target port (Port) to perform the Private MIB management item is 61000, privCmdIdentifier "0x1002" means that the command identifier to perform the Private MIB management item is "0x1002".

In addition, privNumberOfParameter "2" means that the number of the transfer arguments delivered to the target to perform the Private MIB management item is 2, privTransactionId "3" means that the result separator is 3 after the execution of the Private MIB management item target command.

On the other hand, in the transfer factor information that the SNMP agent of the common interface related information should pass to the network element processing the management item, privCmdExtnIndex "1" is a value that matches the privCmdIndex of the privInfoTable. Means.

And, privParamIndex "1" means that the transfer argument index (index) is 1, privParamType "octec string" means that the transfer argument type is a string.

And, privParamLength "17" means that the length of the transfer argument is 17 bytes, privParamValue "pointer" means the value of the transfer argument.

As such, since the SNMP agent recognizes the mapping information between the standard MIB and the private MIB, the network device developer can program without worrying about the standard MIB structure while following the standard in terms of network device management.

8A and 8B illustrate a remote engineering process using a standard MIB according to the present invention.

As shown in the drawing, first, a template representing a mapping relationship between a Standard MIB and a structure used for an internal program of a network device is created (S10) (see FIG. 6). This template contains element information for processing a private structure.

Subsequently, the relation between the standard MIB and the private MIB and the common interface related information are generated as XML based on the created template (S20). In this case, the reason for making XML is that the XML document format is an official document format that conforms to the standard, so that the program can be changed later or the program can be easily ported between different types.

Subsequently, if the SNMP agent is executed (S30) and the generated XML is input as an input value when the SNMP agent is executed (S40), the SNMP agent parses the XML information (S50) and maps it to the internal memory. The table information is loaded (S60). Here, the mapping table information means mapping information between the standard MIB and the related private MIB and information related to the common interface (common interface) (see FIG. 7).

Accordingly, the SNMP agent recognizes the standard MIB and Privet MIB relationship structure according to the mapping table information loaded in the internal memory (S70).

As such, when the mapping table information is loaded into the memory, the SNMP agent checks whether an SNMP operation (get / get-next / get-bulk / set) designated as a standard OID (Object ID) is received from the SNMP manager (S80). If an SNMP operation designated as a standard OID (Object ID) is received, the SNMP agent informs the converting module of mapping table information loaded in the internal memory (S90). Here, the mapping table information means private MIB item information and common interface related table information mapped to the standard OID (Object ID).

Accordingly, the converting module requests (S100) the SNMP operation of the corresponding Private MIB item to the corresponding network element through the common interface according to the SNMP operation of the SNMP agent.

Accordingly, the corresponding network element performs an SNMP operation of the corresponding private MIB item (S110) and transmits the result value to the converting module.

Subsequently, when the converting module receives the SNMP operation result value of the private MIB item from the corresponding network element (S120), the converting module converts the private MIB item into a standard OID (Object ID) mapped thereto (S130) and converts the converted MIB item. The SNMP operation result value for the standard OID (Object ID) is transmitted to the SNMP agent (S140).

In the above, specific preferred embodiments of the present invention have been illustrated and described. However, the present invention is not limited to the above-described embodiment, and various modifications can be made by any person having ordinary skill in the art without departing from the gist of the present invention attached to the claims. will be.

According to the present invention, by managing the network equipment through the Standard MIB according to the mapping table information of the Private MIB and the Standard MIB, there is an effect that it is possible to more efficiently manage the network equipment using a standard method without changing the existing program.

In addition, the standard method facilitates the development of network equipment, increases the portability of the corresponding program, and has the effect of performing the SNMP operation without defining a new data structure and changing the program for SNMP.

Claims (25)

An SNMP management unit for performing remote engineering in accordance with SNMP operations on at least one standard item; And a management item mapping unit for notifying the network manager by changing the result information of the private item mapped to the standard item processed from the corresponding network element according to the SNMP operation required by the SNMP manager to the result information of the standard item. Remote engineering system using SNMP standard item. The method of claim 1, The management item mapping unit, An SNMP agent module for checking private item information and common interface related information mapped to the standard item from a mapping table loaded in a memory when receiving an SNMP operation for the at least one standard item; The result information of the private item mapped to the standard item processed from the corresponding network element is changed to the result information of the standard item according to the private item information mapped to the standard item identified from the SNMP agent module and the common interface related information. A converting module for notifying the SNMP agent module; And And a common interface module for providing a common interface between the SNMP agent module and at least one network element. The method of claim 2, The mapping table, A remote engineering system using an SNMP standard item, comprising mapping table information between a Standard MIB and a private MIB defining at least one standard item, and at least one table information among common interface table information. The method of claim 3, The common interface table information, Using an SNMP standard item including at least one of table (privInfoTable) information on a network element processing a management item for at least one SNMP operation and information on a transfer factor related table (privParamTable) transmitted to the network element. Remote engineering systems. The method of claim 4, wherein Table (privInfoTable) information for the network element, Command index (privCmdIndex) information of the at least one SNMP operation, target IP (privTargetIP) information to perform the private MIB management item, target port (privTargetPort) information to perform the private MIB management item, and the private MIB At least one of command identifier (privCmdIdentifier) information to perform a management item, information on the number of transfer factors (privNumberOfParameter) delivered to a target to perform the private MIB management item, and result identifier (privTransactionId) information after the execution of the private MIB management item target command Remote engineering system using SNMP standard entry containing one piece of information. The method of claim 5, The target IP (privTargetIP) information to perform the Private MIB management item is at least one of the local IP information and the remote IP information, the remote engineering system using an SNMP standard item. The method of claim 5, The transfer factor related table (privParamTable) information, A value (privCmdExtnIndex) corresponding to the instruction index (privCmdIndex) of the table for the network element (privInfoTable), transfer parameter index (privParamIndex) information, transfer factor type (privParamType) information, transfer factor length (privParamLength) information, Remote engineering system using an SNMP standard item that includes at least one of a parameter, privParamValue. Creating a template indicating a mapping relationship between a Standard MIB for at least one standard item and a Private MIB for a private item; Generating mapping table information between the standard MIB and the private MIB as XML information based on the created template; Receiving and analyzing the generated XML information when an SNMP agent is executed; Loading mapping table information into an internal memory according to the analyzed XML information; Recognizing a relationship structure between the standard MIB and the private MIB; And And changing the result information of the private item processed from the corresponding network element to the result information of the standard item according to the SNMP operation request designated as the standard item. The method of claim 8, The mapping table information, And mapping table information between a Standard MIB and a Private MIB defining at least one standard item and at least one table information among common interface table information. The method of claim 9, The common interface table information, Using an SNMP standard item including at least one of table (privInfoTable) information on a network element processing a management item for at least one SNMP operation and information on a transfer factor related table (privParamTable) transmitted to the network element. Remote engineering method. The method of claim 10, Table (privInfoTable) information for the network element, Command index (privCmdIndex) information of the at least one SNMP operation, target IP (privTargetIP) information to perform the private MIB management item, target port (privTargetPort) information to perform the private MIB management item, and the private MIB At least one of command identifier (privCmdIdentifier) information to perform a management item, information on the number of transfer factors (privNumberOfParameter) delivered to a target to perform the private MIB management item, and result identifier (privTransactionId) information after the execution of the private MIB management item target command Remote engineering method using SNMP standard item containing one information. The method of claim 11, The target IP (privTargetIP) information on which the Private MIB management item is to be performed is at least one of local IP information and remote IP information. The remote engineering method using the SNMP standard item. The method of claim 11, The transfer factor related table (privParamTable) information, A value (privCmdExtnIndex) corresponding to the instruction index (privCmdIndex) of the table for the network element (privInfoTable), transfer parameter index (privParamIndex) information, transfer factor type (privParamType) information, transfer factor length (privParamLength) information, Remote engineering method using an SNMP standard item including at least one of a transfer parameter value (privParamValue). Creating a template indicating a mapping relationship between a Standard MIB for at least one standard item and a Private MIB for a private item; Generating mapping table information between the standard MIB and the private MIB as XML information based on the created template; Receiving and analyzing the generated XML information when an SNMP agent is executed; Loading mapping table information into an internal memory according to the analyzed XML information; And Recognizing a relationship structure between the Standard MIB and Private MIB mapping method setting method using an SNMP standard item. The method of claim 14, The mapping table information, And mapping table information between the standard MIB and the private MIB defining at least one standard item, and at least one table information among the common interface table information. The method of claim 15, The common interface table information, Using an SNMP standard item including at least one of table (privInfoTable) information on a network element processing a management item for at least one SNMP operation and information on a transfer factor related table (privParamTable) transmitted to the network element. How to set up a mapping table. The method of claim 16, Table (privInfoTable) information for the network element, Command index (privCmdIndex) information of the at least one SNMP operation, target IP (privTargetIP) information to perform the private MIB management item, target port (privTargetPort) information to perform the private MIB management item, and the private MIB At least one of command identifier (privCmdIdentifier) information to perform a management item, information on the number of transfer factors (privNumberOfParameter) delivered to a target to perform the private MIB management item, and result identifier (privTransactionId) information after the execution of the private MIB management item target command How to set mapping table using SNMP standard item including one information. The method of claim 17, The target IP (privTargetIP) information on which the Private MIB management item is to be performed is at least one of local IP information and remote IP information. The method of claim 17, The transfer factor related table (privParamTable) information, A value (privCmdExtnIndex) corresponding to the instruction index (privCmdIndex) of the table for the network element (privInfoTable), transfer parameter index (privParamIndex) information, transfer factor type (privParamType) information, transfer factor length (privParamLength) information, The method of setting a mapping table using an SNMP standard item including at least one information of a propagation factor value (privParamValue). Transmitting mapping table information loaded in the internal memory according to an SNMP operation request designated as a standard item; Requesting an SNMP operation of a corresponding private MIB item from a corresponding network element according to the mapping table information; Converting a result value of a private MIB item processed and transmitted from the network element into a result value of a standard MIB item; And And returning a result value of the converted Standard MIB item. The method of claim 20, The mapping table information, And mapping table information between a Standard MIB and a Private MIB defining at least one standard item and at least one table information among common interface table information. The method of claim 21, The common interface table information, Using an SNMP standard item including at least one of table (privInfoTable) information on a network element processing a management item for at least one SNMP operation and information on a transfer factor related table (privParamTable) transmitted to the network element. How to convert mapping information. The method of claim 22, Table (privInfoTable) information for the network element, Command index (privCmdIndex) information of the at least one SNMP operation, target IP (privTargetIP) information to perform the private MIB management item, target port (privTargetPort) information to perform the private MIB management item, and the private MIB At least one of command identifier (privCmdIdentifier) information to perform a management item, information on the number of transfer factors (privNumberOfParameter) delivered to a target to perform the private MIB management item, and result identifier (privTransactionId) information after the execution of the private MIB management item target command Method of converting mapping information using SNMP standard item including one information. The method of claim 23, wherein Target IP (privTargetIP) information to perform the Private MIB management item is mapping information conversion method using the SNMP standard item, characterized in that at least one of the IP information of the local IP information and the remote IP information. The method of claim 23, wherein The transfer factor related table (privParamTable) information, A value (privCmdExtnIndex) corresponding to the instruction index (privCmdIndex) of the table for the network element (privInfoTable), transfer parameter index (privParamIndex) information, transfer factor type (privParamType) information, transfer factor length (privParamLength) information, Mapping information conversion method using an SNMP standard item including at least one information of a transfer parameter value (privParamValue).

Images