KR100441891B1 - Data structure of the configuration information for remote controlling the heterogeneous MPLS network and, apparatus, method thereof. - Google Patents

Abstract

The present invention defines multi-protocol label switching (MPLS) related information for setting, changing, and releasing configuration information of a device in a network composed of heterogeneous network devices that support multiprotocol label switching (MPLS). The present invention relates to defining a configuration information data structure to be stored and managed in a computer-readable recording medium, and to a management apparatus and a management method using the data structure.

According to the present invention, when a network is configured using a multi-protocol label switching (MPLS) network engineering technology using a multi-protocol label switching (MPLS) traffic engineering technology, the same configuration information may be used for heterogeneous network equipment. This enabled network administrators to deal with complex network equipment, which allowed them to establish and reflect consistent policies, reduce workload, and effectively manage networks.

Description

Data structure of the configuration information for remote controlling the heterogeneous MPLS network and, apparatus, method

The present invention defines multi-protocol label switching (MPLS) related information for setting, changing, and releasing configuration information of a device in a network composed of heterogeneous network devices that support multiprotocol label switching (MPLS). The present invention relates to defining a configuration information data structure to be stored and managed in a computer-readable recording medium, and to a management apparatus and a management method using the data structure.

In the conventional IP packet exchange method, a router that receives data repeats a process of retrieving a large number of IPs and transmitting data through a route calculation process for determining the next router, which is hop-by-hop. It is called a hop-by-hop method and is classified as a connectionless IP switching system in that it is stopped and transmitted for each router.

However, as Internet users surged, the number of IPs managed by one router and the amount of data waiting to process route calculations began to increase, resulting in congestion of Internet traffic. However, due to the increase in cost, the profitability of the customer increased. In addition, as the speed of communication depends on the speed of the entire network, demand for differentiated new products in speed, continuity, and price has begun to emerge, and consumers' dissatisfaction with using the same speed and price regardless of personal needs is high.

To solve this problem, multi-protocol label switching (MPLS) is a next-generation packet transmission method created by the Internet Engineering Task Force (IETF). This is a connection type IP (IP) exchange method in which a packet is labeled with a predetermined path and a packet is transmitted only by switching without a path calculation process.

By eliminating the route calculation process and reducing the burden of IP management on the router, speed can be increased and a quality of service (QoS) can be created by speed, continuity, and price.

The basic idea of multi-protocol label switching (MPLS) is to combine different control modules to perform label swapping and forward. The control module may be a basic unicast routing module, a traffic engineering module, or the like. The Label Switched Path (LSP), which is a connection in a multi-protocol Label Switching (MPLS) network, is based on a Label Distribution Protocol (LDP), a convergence-based protocol, which is a connection establishment protocol of Multi-Protocol Label Switching (MPLS). Constraint-based Routing LDP (LR-LDP) or Resource Reservation Protocol-set by Resource Reservation Protocol-Traffic Engineering (RSVP-TE), and packet forwarding in the Label Switching Path (LSP) Labels can transmit packets of three layers efficiently and quickly using short headers.

Common methods of using the Multiprotocol Label Switching (MPLS) feature provided by network devices include configuring configuration information using command line interface (CLI) commands via a console directly connected to the device, and Telnet. There is a way to set the configuration information by the remote control method through). The present invention supports a network management system or a configuration server to remotely control heterogeneous network equipment by providing a general information structure that is not dependent on specific equipment in using the latter method. In addition, by defining configuration information in consideration of scalability and interoperability, configuration information is defined to facilitate the addition of new functions and to share information among servers using the configuration information.

In addition, configuration information configuration, status monitoring, error reporting, and traffic state analysis of network equipment are essential functions of a network management system for operating and managing a network, and the multi-protocol label switching (MPLS) configuration information described in the present invention. The model defines the information necessary for the network management system to manage the configuration information of a specialized network, in particular a multiprotocol label switching (MPLS) network.

Existing systems, especially those related to setting configuration information, provide functions for setting user authority, admission control, IP routing protocols, device interface configuration, and IP address filters. The present invention includes an information model for setting multi-protocol label switching (MPLS) configuration information for multi-protocol label switching (MPLS) network equipment.

Multiprotocol Label Switching (MPLS) configuration information includes Forward Error Correction (FEC), ReSerVation Protocol-Traffic Engineering (RSVP-TE), and Open Shortest Path First-Traffic Engineering (OSPF-TE). New configuration information such as Label Switching Protocol (LSP), Routes, and Resource Classes, as well as extended IP address filters, Routing Protocols, and Resource Reservation Protocols (RSVP) such as Open Shortest Path First-TE And the like.

The multi-protocol label switching (MPLS) configuration information model defined in the present invention is defined using an object-oriented modeling method, a database, a light-weight directory adaptation protocol (LDAP), and an extensible markup language (XML, eXtended). It is defined to be expressed in various schema formats such as Mark-up Language, CORBA Interface Description Language (IDL). In addition, a configuration information management apparatus for effectively managing instances of configuration information is defined.

In order to solve the above problems, the present invention enables to express the multi-protocol label switching (MPLS) configuration information of the multi-protocol label switching (MPLS) network equipment in various information schemes, and to a computer-readable storage medium. Provide an information model for storage and management. It provides a management device for managing this information.

This aims to support remote control of networks consisting of heterogeneous multiprotocol label switching (MPLS) network equipment through a single network management system.

1 is a block diagram of a multi-protocol label switching (MPLS) network management system applied to an embodiment of the present invention.

2 is a configuration diagram of a policy server PS.

3 illustrates the concept of a traffic trunk (TT).

4 illustrates a class present in a label switching path tunnel in a traffic trunk.

5 is a data structure diagram of multi-protocol label switching (MPLS) configuration information of the present invention;

6 is a block diagram of a management device for managing multi-protocol label switching (MPLS) configuration information classes of the present invention.

FIG. 7 is an embodiment configuration diagram of a reference and dependency relationship between a multi-protocol label switching (MPLS) configuration information class and a management device of the present invention. FIG.

8 is a flowchart of a management method for managing multi-protocol label switching (MPLS) configuration information classes of the present invention.

In order to achieve the above object, the present invention includes a forward error correction class used to identify IP packets transmitted through a specific label switching path; A resource reservation protocol traffic profile class that stores bandwidth resource information allocated to a label switching path; A traffic trunk class consisting of a set of label switching path tunnels for traffic sharing; A label switching path class that stores attribute information necessary for setting a label switching path; A label switching path tunnel class consisting of a set of primary label switching paths and backup label switching paths; A path class that stores path information designated by a network manager to set a label switching path; A setting path class that stores path information automatically set by a network manager or a network device; And it provides a data structure used in the system for managing the configuration information of the multi-protocol label switching network equipment including an interface class for storing the components of the network.

In order to achieve the above object, in the present invention, a forward direction having a function for creating or deleting a forward error correction (FEC) class instance and providing a list of forward error correction (FEC) and length information of the list is managed Error correction (FEC) manager; A resource reservation protocol (RSVP) traffic profile manager providing a function of maintaining and managing a list of resource reservation protocol (RSVP) traffic profile class instances; A path manager providing a function of maintaining and managing a list of path class instances defined by the network user; Provides the ability to create, modify, and delete Label Switching Path Tunnels (LSP Tunnel) and Label Switching Paths (LSP), and maintains a list of Label Switching Path Tunnel class instances and a list of Label Switching Path (LSP) class instances. A Label Switching Path Tunnel Manager (LSP Tunnel Manager) that provides the ability for client objects to retrieve it; And a traffic trunk (TT) manager for maintaining, managing a list of traffic trunk (TT) class instances, and providing a function of creating, modifying, and deleting a traffic trunk (TT). .

In order to achieve the above object, the present invention provides a method for managing a forward error correction class instance used to identify IP packets transmitted through a specific label switching path; Managing a traffic trunk class instance consisting of a set of label switching path tunnels for traffic sharing; Managing a label switching path tunnel class comprising a primary label switching path and a backup label switching path and a label switching path class defining attribute information necessary for setting the label switching path; Managing a traffic trunk class managed by the traffic trunk manager, a label switching path tunnel class and a label switching path class managed by the label switching path tunnel manager, and maintaining and managing a list of resource reservation protocol traffic profile class instances step; And maintaining and managing a list of the label switching path class and the path class instance defined by the network user.

The data structure of the above-described multi-protocol label switching (MPLS) configuration information model, a management apparatus and a management method using the data structure will be more clearly defined through the accompanying drawings and the following detailed description. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of a multi-protocol label switching (MPLS) network management system applied to an embodiment of the present invention.

Communication between system modules is performed using a CORBA interface, and each module is implemented using a C ++ language, a C language, or JAVA. Telnet through Common Open Policy Service (COPS) protocol, Simple Network Management Protocol (SNMP) and Proxy Agent for control and monitoring between network equipment and development system Based Command Line Interface (CLI) technology is implemented, overall data management is based on Relational Database (RDB) based on Open Database Connectivity (ODBC) technology, and lightweight directory access. Protocol (LDAP, Lightweight Directory Access Protocol) technology was used together. The development of the system was done on Sun Solaris OS systems and can be done on Sun, Linux, and FreeBSD.

The multi-protocol label switching (MPLS) network management system includes a common service interface (CSI) 101, a graphical user interface (GUI) 102, a policy server (PS) 103 Resource Monitoring Server (RMS) 104, Traffic Measurement Analysis Server (TMS) 105, Routing Advisor for Traffic Engineering (RATE) 106 And a proxy agent (PA) 107.

2 is a configuration diagram of the policy server PS.

The Policy Server (PS) is designed and implemented according to the structure defined by the Internet Framework Task Force's Policy Framework Working Group (IETF), which is a multi-protocol label switching (MPLS) traffic engineering (TE) network-wide network. ) It is responsible for determining the VPN and VPN policy, creating, modifying, deleting, and checking policy rules, policy rule enforcement, and admission control.

The functions of these Policy Servers (PS) are responsible for automatically applying complex multiprotocol label switching-traffic engineering (MPLS-TE) and virtual private network (VPN) configurations across the network. This feature can be an essential element for operators who have manually managed complex configuration information by router and can contribute to maximum efficiency in terms of time and cost of management. Particularly, the virtual private network (VPN) configuration management product has been developed in part, but the multi-protocol label switching-traffic engineering (MPLS-TE) and the virtual private network (VPN) configuration management based on the same are important in the present invention. It can be said.

3 is a diagram illustrating the concept of a traffic trunk (TT).

The traffic trunk (TT) is composed of a set of label switching path tunnels (LSP tunnels) composed of one primary label switching path (Primary LSP) and a secondary label switching path (Secondary LSP). The Secondary Label Switching Path (Secondary LSP) may be zero or more since it may not exist.

4 is a diagram illustrating a class present in a label switching path tunnel in a traffic trunk.

The traffic trunk (TT) is composed of a set of LSP tunnels, which consist of a primary label switching path and a secondary label switching path. The primary label switching path or secondary label switching path is composed of resource reservation protocol traffic profile class (RSVP TP), affinity class (Affinity), forward error correction class (FEC), and path class (Path).

5 is a data structure diagram of multi-protocol label switching (MPLS) configuration information according to the present invention.

In FIG. 5, the common class 501 among the multi-protocol label switching (MPLS) configuration information is an Internet address in IP version 4 (IPv4) format such as a network address, node address, node name, subnet mask, and the like. Define the information. It also includes time information and node location information defined for recording the scheduling time and traffic data storage time.

In FIG. 5, the global configuration class 502 does not belong to a specific node or interface, an LSP tunnel, etc., and defines configuration information that can be used globally. Resource class Class 503 defines the information needed to group nodes or links with similar characteristics.

The forward error correction class (FEC) 504 of FIG. 5 includes an IP protocol version, a source IP and a destination IP address of traffic, type of service (ToS) information, 4 Defines information such as layer protocol type.

Resource reservation protocol traffic profile (RSVP Traffic Profile) class 505 of Figure 5 defines the resources, in particular bandwidth information required when using the resource reservation protocol (RSVP).

The traffic trunk (TT) class 506 of FIG. 5 is an operational state indicating whether a unique identifier for the traffic trunk (TT), the traffic trunk (TT) name, and the traffic trunk (TT) are being reflected to the equipment. It defines the types of ingress network equipment, IP addresses of ingress and egress network equipment, and priorities for establishing and maintaining traffic trunks (TT).

In addition, if a traffic trunk failure occurs, error recovery is allowed, optimization is allowed, the role of the traffic trunk (TT) includes a list of resource classes to be included, a list of resource classes to be excluded, and a traffic trunk (TT). In the list of the Label Switching Path Tunnels (LSPTunnel), the load sharing rate assigned by the included Label Switching Path Tunnels (LSP Tunnel), the reference list of the Forward Error Correction (FEC) class, and the reference of the Resource Reservation Protocol (RSVP) traffic profile class. Defines information about

Label Switching Path Tunnel (LSP Tunnel) class 507 of FIG. 5 is an identifier for uniquely identifying a Label Switching Path Tunnel (LSP Tunnel), a name of the Label Switching Path Tunnel (LSP Tunnel), and is automatically generated by the device. Creation type to indicate whether it was created by the network manager, type of incoming network device, operating status to indicate whether or not the Label Switching Path Tunnel is operating on the network device, and IP address of the incoming and outgoing network device. Defines information about references to the node IP (IP) configuration class of incoming, outgoing and outgoing nodes.

In addition, the label switching path tunnel (LSP Tunnel establishment and maintenance priority), whether to record the label switching path (LSP) generated by the resource reservation protocol-traffic engineering (RSVP-TE) protocol, resource reservation protocol traffic profile (RSVP Traffic Profile) class reference, reference list of forward error correction (FEC) class, reference to primary label switching path (LSP) class, reference list to secondary label switching path (LSP) class, resource class to include Defines a list of references to resources, a list of references to resource classes to be excluded, and information about the roles assigned to the Label Switching Path Tunnel.

The label switching path (LSP) class 508 of FIG. 5 is a class constituting the label switching path tunnel (LSP Tunnel), and is used as a primary label switching path (LSP) and an auxiliary label switching path (LSP) according to a purpose.

The Label Switching Path (LSP) class is an identifier for uniquely identifying a Label Switching Path (LSP), a Label Switching Path (LSP) name, a generation type that indicates whether it was automatically generated by the device or generated by the network manager, and a label. Operational status indicating whether the switching path (LSP) is operating on the network equipment, setting and maintenance priority of the label switching path (LSP), class of service (CoS), metric value, absolute value and relative Value metric type, preference between secondary label switching paths (LSPs) to be used if the primary label switching path (LSP) fails, the maximum number of nodes that can pass when the label switching path (LSP) is created, and wait for actual operation. Defines whether or not to indicate standby.

In addition, it includes whether the path indicating whether to store the label switching path (LSP) information determined by the network equipment, whether or not to use the Constrained Shortest Path First (CSPF) routing algorithm, reference to the path class, itself Defines information about the label-switching route tunnel (LSP Tunnel), the resource reservation protocol (RSVP Traffic Profile) class reference, and the type of route that indicates whether the neighboring node described when establishing the route is a direct or indirect connection. do.

The route class 509 of FIG. 5 includes information on which route the label switching route (LSP) is set to, a reference list of interface classes constituting the route, and an IP address list of interfaces constituting the route. It defines information about the path type, path name, etc., which indicates whether it has been explicitly selected by the network administrator or automatically by the network device.

In the configuration path class 510 of FIG. 5, when the network manager inputs only information on inflow and outflow nodes and the remaining paths are selected by the network equipment, a reference list of all interface classes constituting the path including inflow and outflow interface classes Define.

The node class 511 of FIG. 5 is a class that defines general information about network equipment, and includes a node IP configuration class 512, a node multiprotocol label switching (MPLS) configuration class 513, and a node boundary gateway protocol ( It includes a list of references to the Border Gateway Protocol (BGP) configuration class 514 and the Open Shortest Path First configuration class (OSPF) 515.

It also provides functions to create, search, and delete four types of configuration classes. It defines node identifier information that can uniquely identify a node and a reference list of interface classes that belong to a node.

The interface class 516 of FIG. 5 includes four lower configuration classes: interface IP (IP) configuration class 517, interface multiprotocol label switching (MPLS) configuration class 518, and interface boundary gateway protocol (BGP). The configuration class 519 and the interface Open Shortest Path First (OSPF) configuration class 520 include a list of references, an identifier that can uniquely identify the interface, and reference information for the node class that contains it. Create, search, and delete the configuration class.

FIG. 6 is a diagram illustrating a configuration of a management apparatus for managing multi-protocol label switching (MPLS) configuration information classes.

The management apparatus of FIG. 6 includes a forward error correction (FEC) class, a resource class, a resource reservation protocol (RSVP Traffic Profile) class, a path class, a node class, a label switching path (LSP) class, and a label switching path tunnel (LSP Tunnel). ), Create, modify, delete, and retrieve instances of class and traffic trunk (TT) classes.

Looking at the function of each component constituting the management device in detail as follows.

The forward error correction manager (FEC) 610 provides a function for creating or deleting a forward error correction (FEC) class instance. The forward error correction manager (FEC) 610 provides a list of the forward error correction (FEC) and the length information of the list. Client) Performs the function provided to the object. In addition, a Forward Error Correction (FEC) Manager includes a Forward Error Correction (FEC) class instance included in the traffic trunk (TT) class, the Label Switching Path Tunnel (LSP Tunnel) class, and the Label Switching Path (LSP) class described above with reference to FIG. 5. Managed by classes ensures reusability and consistency of forward error correction (FEC) class instances.

The resource class manager 620 provides a function of collectively managing resource class instances included in the traffic trunk (TT) class, the label switching path tunnel (LSP Tunnel) class, and the label switching path (LSP) class described above with reference to FIG. 1. This ensures the reusability and consistency of class instances of resource classes.

Resource reservation protocol traffic profile (RSVP Traffic Profile) Class manager 630 performs a function of maintaining and managing a list of resource reservation protocol traffic profile class instances.

The path manager 640 maintains and manages a list of path class instances defined by the network user.

The node manager 650 provides functions of creating, changing, and deleting node and interface class instances, and maintains and manages a list of each.

The Label Switching Path Tunnel Manager (660) provides the ability to create, modify, and delete Label Switching Path Tunnels (LSP Tunnels) and Label Switching Paths (LSPs), and lists the Label Switching Path Tunnels (LSP Tunnel) class instances. It maintains a list of Label Switching Path (LSP) class instances and allows client objects to retrieve them.

The traffic trunk (TT) manager 670 maintains and manages a list of traffic trunk (TT) class instances and performs the function of creating, modifying, and deleting a traffic trunk (TT).

7 is a diagram illustrating an embodiment of a reference and dependency relationship between a multi-protocol label switching (MPLS) configuration information class and a management apparatus according to the present invention.

FIG. 7 illustrates a reference relationship between a configuration class and an administrator and between configuration classes. The relationship between the traffic trunk (TT) class and the Label Switching Path Tunnel (LSP Tunnel) class 701 is formed for traffic load sharing, and the Label Switching Path Tunnel (LSPTunnel) class is used for zero or one traffic trunk (TT) class. While having a reference, a traffic trunk (TT) class may contain a reference to one or more Label Switching Path Tunnel (LSP Tunnel) classes.

The Label Switching Path (LSP) class for the Label Switching Path Tunnel (LSP Tunnel) may have a relationship 702 of the Primary Label Switching Path (LSP) or a Relationship 703 of the Secondary Label Switching Path (LSP). When a Label Switching Path Tunnel (LSP Tunnel) and a Label Switching Path (LSP) class have a main Label Switching Path (LSP) relationship, both may contain only one reference. On the other hand, when it has a secondary label switching (LSP) path relationship, the Label Switching Path Tunnel class can contain references to one or more Label Switching Path (LSP) classes, and the Label Switching Path (LSP) class. Contains a reference to one Label Switching Path Tunnel (LSP Tunnel) class.

In FIG. 7, the label switching path (LSP) class and the path class have a 1-n relationship, and an instance of the configuration path class is generated after the label switching path (LSP) is reflected in the network device. At this time, if the path is explicitly selected by the network manager, the path class instance and the configuration path class instance have the same information. If the path is automatically selected by the network device, the label switching path (LSP) class refers to the configuration path class instance. It includes.

8 is a flowchart illustrating a management method of managing multi-protocol label switching (MPLS) configuration information classes of the present invention.

First, a forward error correction (FEC) manager manages a forward error correction (FEC) class instance used to identify IP packets delivered over a specific label switching path (LSP) (810). That is, the Forward Error Correction (FEC) Manager creates a Forward Error Correction (FEC) class instance, and if the generated Forward Error Correction (FEC) class is unnecessary, the Forward Error Correction (FEC) Manager creates a Forward Error Correction (FEC) class instance. Deletes and forwards the list of generated forward error correction (FEC) classes and the length information of the list to the traffic trunk (TT) manager and the label switching path (LSP) tunnel manager.

The traffic trunk (TT) manager manages a traffic trunk (TT) class instance consisting of a set of label switching path tunnels for traffic sharing (820). That is, the traffic trunk (TT) manager creates a traffic trunk (TT) class instance, and if the value of the generated traffic trunk (TT) class instance is changed or unnecessary, changes or deletes the value of the traffic trunk (TT) class instance.

The Label Switching Path (LSP) Tunnel Manager defines the Label Switching Path (LSP) tunnel class, which consists of a set of Primary Label Switching Path (LSP) and Backup Label Switching Path (LSP), and the attribute information required to set up the Label Switching Path (LSP). The label switching path (LSP) class is managed (830).

That is, the Label Switching Path (LSP) Tunnel Manager creates a Label Switching Path (LSP) tunnel class and a Label Switching Path (LSP) class, and generates a Label Switching Path (LSP) tunnel class and a Label Switching Path (LSP) class. If the value changes or is unnecessary, change or delete it to maintain a list of Label Switching Path (LSP) tunnel class instances and a list of Label Switching Path (LSP) class instances.

The resource reservation protocol (RSVP) traffic profile manager includes a traffic trunk (TT) class managed by the traffic trunk (TT) manager and a label switching path (LSP) tunnel class managed by the label switching path (LSP) tunnel manager; A label switching path (LSP) class is managed, and a list of resource reservation protocol (RSVP) traffic profile class instances is maintained and managed (840).

The path manager maintains and manages the list of path class instances defined by the label switching path (LSP) class and the network user (850).

Meanwhile, the above-described embodiments of the present invention can be written as a program that can be executed in a computer, and can be implemented in a general-purpose digital computer that operates the program using a computer-readable recording medium.

In addition, the structure of the data used in the above-described embodiment of the present invention can be recorded on the computer-readable recording medium through various means.

The computer-readable recording medium may be a magnetic storage medium (for example, a ROM, a floppy disk, a hard disk, etc.), an optical reading medium (for example, a CD-ROM, DVD, etc.) and a carrier wave (for example, the Internet). Storage medium).

So far I looked at the center of the preferred embodiment for the present invention. Those skilled in the art will appreciate that the present invention can be implemented in a modified form without departing from the essential features of the present invention. Therefore, the disclosed embodiments should be considered in descriptive sense only and not for purposes of limitation. The scope of the present invention is shown in the claims rather than the foregoing description, and all differences within the scope will be construed as being included in the present invention.

As described above, the present invention is the same for heterogeneous network equipment when a network is configured by using multi-protocol label switching (MPLS) traffic engineering (TE) technology in a network composed of multi-protocol label switching (MPLS) network equipment. Configuration information can be used, which enables the establishment and reflection of consistent policies for network administrators who have to deal with complex network equipment, and has the effect of reducing the workload and efficiently managing the network.

In addition, by using object-oriented modeling method considering scalability and interoperability, it is easy to cope with the need to add or change functions.

Claims (7)

A forward error correction class used to identify IP packets carried over a particular label switching path; A resource reservation protocol traffic profile class storing bandwidth resource information allocated to the label switching path; A traffic trunk class consisting of the set of label switching path tunnels for traffic sharing; A label switching path class for storing attribute information necessary for setting the label switching path; A label switching path tunnel class consisting of a set of primary label switching paths and backup label switching paths; A path class that stores path information designated by a network manager to set the label switching path; A setting path class that stores path information automatically set by a network manager or a network device; And A data structure used in a system that manages configuration information for multiprotocol label switching network equipment, including interface classes that store network components. The method of claim 1, wherein the traffic trunk class, A data structure used in a system for managing configuration information of a multi-protocol label switching network device, characterized by one or more label switching path tunnels, each label switching path tunnel consisting of a set of label switching paths. A forward error correction manager that creates or deletes a forward error correction class instance used to identify IP packets transmitted through a specific label switching path, and provides a list of forward error correction classes and length information of the list; A traffic trunk manager for creating, modifying, and deleting a traffic trunk class instance consisting of a set of label switching path tunnels for traffic sharing, and maintaining and managing a list of traffic trunk instances; Create, modify, and delete a label switching path tunnel class, which consists of a set of primary label switching paths and backup label switching paths, and the label switching path classes that define the attribute information required to set the label switching path, and list and label instances of the label switching path tunnel classes. A label switching path tunnel manager that maintains a list of switching path class instances and allows client objects to retrieve them; Managing a traffic trunk class managed by the traffic trunk manager, a label switching path tunnel class and a label switching path class managed by the label switching path tunnel manager, and maintaining and managing a list of resource reservation protocol traffic profile class instances Resource reservation protocol traffic profile manager; And And a path manager for maintaining and managing a list of path class instances defining path information specified by a network manager to set the label switching path class and the label switching path. (a) managing a forward error correction class instance used to identify IP packets carried over a particular label switching path; (b) managing a traffic trunk class instance consisting of a set of label switching path tunnels for traffic sharing; (c) managing a label switching path tunnel class consisting of a set of primary label switching paths and backup label switching paths and a label switching path class defining attribute information necessary for setting the label switching path; (d) manage a traffic trunk class managed by the traffic trunk manager, a label switching path tunnel class and a label switching path class managed by the label switching path tunnel manager, and maintain a list of resource reservation protocol traffic profile class instances Managing; And (e) maintaining and managing a list of the label switching path class and the path class instance defined by the network user. The method of claim 4, wherein step (a) comprises: (a1) the forward error correction manager creating a forward error correction class instance; (a2) if the forward error correction class generated in step (a1) is unnecessary, the forward error correction manager deletes the forward error correction class instance; And (a3) multi-protocol label switching configuration information management, comprising: forwarding the list of forward error correction classes and the list length information generated in step (a1) to the traffic trunk manager and the label switching path tunnel manager. Way. The method of claim 4, wherein step (b) comprises: (b1) the traffic trunk manager creating a traffic trunk class instance; And and (b2) changing or deleting the value of the traffic trunk class instance when the value of the traffic trunk class instance created or changed in step (b1) is unnecessary. The method of claim 4, wherein step (c) comprises: (c1) the label switching path tunnel manager generating a label switching path tunnel class and a label switching path class; And (c2) If the values of the label switching path tunnel class and the label switching path class created in step (c1) are changed or unnecessary, change or delete the list of the label switching path tunnel class instance and the list of label switching path class instance. And maintaining the multi-protocol label switching configuration information.