KR101726264B1 - Network Management System of inter-operation between multivendor packet transport networks and method thereof - Google Patents

Abstract

Disclosed is a technology for enabling heterogeneous packet transfer network interworking based on an integrated network management system. An embodiment according to one aspect of the present invention is a method for an integrated network management system to construct an overall network topology of a communication carrier network composed of a plurality of heterogeneous packet transmission network domains. The method includes receiving first topology information from a network management system of a first packet transport network domain, receiving second topology information from a network management system of a second packet transport network domain, The third topology information of the packet transfer network interworking interval is generated, and the first topology information, the second topology information, and the third topology information are integrated to construct the entire network topology information.

Description

[0001] The present invention relates to an integrated network management system for interworking between heterogeneous packet forwarding networks,

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a communication system, and more particularly, to a technology for enabling interworking between heterogeneous packet transfer networks based on an integrated network management system (NMS).

In general, the packet transmission network is a network technology that guarantees circuit-level high availability (recovery within 50ms) and operation and maintenance management functions used in existing voice-oriented SONET / SDH networks in network equipment implemented with packet technology. It is a technology spreading to network operators and enterprise customers based on standard technologies such as MPLS-TP (Multi-Protocol Label Switching-Transport Profile) or PBB-TE (Provider Backbone Bridge-Traffic Engineering)

However, if a network operator manages a SONET / SDH network with separate domains by region / customer, the interworking between domains is not possible. Packet link networks such as MPLS-TP and PBB-TE are interworked with the MPLS-TP label and the PBB-TE frame standard in the heterogeneous domain interworking section, while the interworking can be performed based on the SONET / Do not.
BACKGROUND ART [0002] The background art of the present invention is disclosed in Korean Patent Laid-Open Publication No. 2015-0013978.

Accordingly, it is an object of the present invention to provide a method of linking a heterogeneous packet transmission network based on MPLS-TP based on an integrated NMS.

An embodiment according to one aspect of the present invention is a method for an integrated network management system to construct an overall network topology of a communication carrier network composed of a plurality of heterogeneous packet transmission network domains. The method includes receiving first topology information from a network management system of a first packet transport network domain, receiving second topology information from a network management system of a second packet transport network domain, The third topology information of the packet transfer network interworking interval is generated, and the first topology information, the second topology information, and the third topology information are integrated to construct the entire network topology information.

Here, the third topology information of the interworking interval between the first packet transmission network domain and the second packet transmission network domain may include at least one of the first topology information and the second topology information using the first topology information and the second topology information, Identifying at least one border node belonging to the border node and the second packet transmission network domain, acquiring neighbor node information of the first border node and the second border node, and using the neighbor node information, May be obtained by identifying at least a pair of boundary nodes constituting the boundary node.

In one embodiment, the neighbor node information may be obtained using an adjacent node search protocol or MAC table matching.

Here, the MAC table matching may be performed such that the at least one boundary node belonging to the first packet transmission network domain and the at least one border node belonging to the second packet transmission network domain each transmit an Ethernet packet, A border node generates the MAC table including the MAC address and connection port information of the border node to which the Ethernet packet is transmitted, and transmits the generated MAC table to the integrated network management system, and the integrated network management system matches the MAC table, Node information can be obtained.

In one embodiment, the method may allocate a unified node ID to a node belonging to the first packet transfer network domain and the second packet transfer network domain. Here, the node may be a network device supporting Multi-Protocol Label Switching-Transport Profile (MPLS-TP).

An embodiment according to another aspect of the present invention is a method for interworking between heterogeneous packet transfer networks based on an integrated network management system. The method includes constructing an overall network topology of a carrier network that includes a first packet transmission network domain and a second packet transmission network domain, calculating at least one optimal path between end nodes using the overall network topology information, At least one optimal path is established. Here, the first packet transmission network domain and the second packet transmission network domain may be heterogeneous packet transmission networks.

In one embodiment, the entire network topology of the communication service provider network including the first packet transmission network domain and the second packet transmission network domain includes receiving first topology information from the network management system of the first packet transmission network domain, The first topology information, the second topology information, the second topology information, and the second topology information, the first topology information, the second topology information, and the second topology information, 2 topology information, and the third topology information.

In one embodiment, a unified node ID may be assigned to a node belonging to the first packet transfer network domain and the second packet transfer network domain.

In one embodiment, the computed at least one optimal path computes an entire node set according to the computed at least one optimal path, calculates an entire set of Label values using the entire node set, A second domain node set including only the nodes belonging to the first packet transfer network domain and the second domain node set including only the nodes belonging to the second packet transfer network domain; Dividing the first set of domain labels into a set of domain nodes, dividing the entire set of Label values into a first domain Label value set and a second domain Label value set based on the first domain node set and the second domain node set, A first set of domain labels and a set of second domain nodes, And a second domain Label operation set.

The calculated at least one optimal path transmits the first domain node set, the first domain Label value set, and the first domain Label operation set to the network management system of the first packet transfer network domain, And transmitting the second domain node set, the second domain Label value set, and the second domain Label operation set to the network management system of the second packet transmission network domain.

In one embodiment, the method may test at least one or more optimal paths set.

In one embodiment, the set at least one optimal path may include a main path and a sub path.

Another embodiment of the present invention is an integrated network management system for interworking between heterogeneous packet transfer networks. Wherein the integrated management system comprises a topology building module for building an overall network topology of a communication carrier network including a first packet transmission network domain and a second packet transmission network domain and at least one optimal path between the end nodes using the overall network topology information, And a provisioning module for setting the calculated at least one optimal path, wherein the first packet transfer network domain and the second packet transfer network domain may be a heterogeneous packet transfer network.

In one embodiment, the provisioning module may include an OAM module that tests the at least one optimal path set.

In one embodiment, the provisioning module may include a protection switching module for performing protection switching between the main path and the auxiliary path.

As described above, according to the present invention, it is possible to interwork with a closed MPLS-TP packet transmission network composed of heterogeneous types, and it is possible to provide an end-to-end OAM and a protection switching function stably .

Further, according to the present invention, operators can quickly construct a line automatically through an integrated NMS without having to access individual NMSs or access individual devices and manually configure the tunnels.

Hereinafter, the present invention will be described with reference to the embodiments shown in the accompanying drawings. For the sake of clarity, throughout the accompanying drawings, like elements have been assigned the same reference numerals. It is to be understood that the present invention is not limited to the embodiments illustrated in the accompanying drawings, but may be embodied in many other specific forms without departing from the spirit or essential characteristics thereof.
1 illustrates an exemplary integrated network management system for interworking between heterogeneous packet transfer networks.
FIG. 2 exemplarily illustrates a heterogeneous packet transfer interworking method based on an integrated network management system.
FIG. 3 illustrates exemplary overall network topology information.
Figure 4 illustrates a bidirectional Label operation of the nodes in the computed path.

While the present invention has been described in connection with certain exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and similarities. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

The terms first, second, etc. are used to refer to elements described in the specification or drawings, but these terms are used for the purpose of distinguishing components from one another. That is, the reason why the structure or the function is substantially the same or similar is distinguished as the first, second, or the like is merely for explaining various cases in which the inventive idea can be embodied, This is not because multiple components are necessarily required. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used in this application is used only to describe a specific embodiment and is not intended to limit the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as either ideal or overly formal in the sense of the present application Do not.

1 illustrates an exemplary integrated network management system for interworking between heterogeneous packet transfer networks.

When the MPLS-TP-based packet transmission network is supplied from different equipment suppliers, the SBI (southbound interface) between each packet transmission network NMS and the network equipment remains unchanged while the NBI (northbound interface) of each packet transmission network NMS and the integrated NMS is opened . Therefore, the information of the MPLS-TP network equipment necessary for the network operation is transferred to the integrated NMS, and the integrated NMS can link the heterogeneous packet transmission networks based on the MPLS-TP frame. MPLS-TP standard OAM and protection switching technology is based on ITU-T G.8113.1 OAM based on International Telecommunication Union Telecommunication (ITU-T) Y.1731 and ITU-T G.8113.2 OAM standard based on IETF (Internet Engineering Task Force) BFD Lt; / RTI > Therefore, interworking between packet-passing mangers conforming to the same OAM standard is required for interworking of heterogeneous packet-transport networks based on integrated NMS.

Referring to FIG. 1, the communication service provider network includes a packet transmission network domain A 210A and a packet transmission network domain B 210B, which are two heterogeneous packet transmission networks. An NMS A 200A) and NMS B (200B). Here, the heterogeneous packet transmission network uses the same MPLS-TP technology, but the packet transmission network is a device provided by a plurality of equipment suppliers, although the domain may be a separate packet transmission network or a domain may exist depending on the region or customer. And a packet transmission network that operates in the form of a sub-domain for each equipment supplier. The NMS A 200A and the NMS B 200B communicate with the integrated NMS 100 via the NBI and are controlled by the integrated NMS 100. Meanwhile, the NMS A 200A and the NMS B 200B communicate with the network equipment through the SBI to operate and maintain the packet transfer network domain A 210A and the domain B 210B.

Integrated NMS 100 is a functional entity that controls associated components (e.g., switches, routers, etc.) to control the flow of traffic or packets. The integrated NMS 100 is located at an upper position between the NMS A 200A and the NMS B 200B and uses the NBIs of the NMS A 200A and the NMS B 200B to transmit the NMS A 200A and the NMS B 200B, . In detail, the integrated NMS 100 integrates control over the network devices existing in the carrier network, and collects and integrates configuration information, topology, and resource information for the carrier network at the center. That is, the integrated NMS 100 centrally integrates distributed control functions for each domain or each network device, and transmits a command for controlling the network equipment to secure necessary network resources.

On the other hand, the integrated NMS 100 is not limited by the physical implementation form or the location of the implementation. That is, the integrated NMS 100 may be a transport SDN controller. For example, the integrated NMS 100 may refer to a controller functional entity defined in ONF (OpenFlow), IETF, European Telecommunication Standards Institute (ETSI), and / or ITU-T.

The integrated NMS 100 includes a topology provision module 110, a path computation module 120, and a provisioning module 120 that performs a provisioning function for the computed path, to perform provisioning of a subscriber line via more than one packet transport network domain. (130).

The topology building module 110 builds up the overall network topology information for the communication service provider network composed of a plurality of packet transmission network domains. The topology construction module 110 periodically collects topology information of the packet transfer network domain such as physical connection information and logical connection information between MPLS-TP based network devices belonging to each packet transmission network domain, and when the information is changed And keeps the entire network topology information in the latest state. The overall network topology information can be constructed by integrating the topology information of each of the plurality of packet transmission network domains and adding topology information for interworking intervals between the packet transmission network domains. Here, the topology information for interworking interval between packet transmission network domains can be constructed using the standardized neighbor search protocol or MAC table matching at the border node.

The path calculation module 120 calculates an optimal path between end nodes determined to provide the subscriber line. The path calculation module 120 calculates an optimal path based on the established overall network topology using the packet transmission network domain, the number of network hops, the availability of available network resources, and the like. Here, the path calculation can be provided by standard or various methods.

Provisioning module 130 provisions the customer service line according to the calculated path. Provisioning module 130 includes a Label module 131, an OAM module 132, and a protection switching module 133. The operation of the provisioning module 130 will be described below with reference to FIG. 2 and FIG.

FIG. 2 exemplarily shows a heterogeneous packet transfer network interworking method based on the integrated network management system, and FIG. 3 exemplarily shows the entire network topology information.

In steps 300 and 310, the integrated NMS 100 builds the overall network topology information. To this end, the integrated NMS 100 consolidates topology information for each of a plurality of packet transmission network domains, and integrates topology information for a plurality of packet transmission network inter-domain interworking periods. Thereafter, optionally, a unified node ID may be assigned to nodes belonging to each of a plurality of packet transport network domains.

In order to integrate topology information for each of a plurality of packet transmission network domains, the topology construction module 110 of the integrated NMS 100 shown in FIG. 1 includes an NMS A 200A operating a packet transmission network domain A and a packet transmission network domain B To the NMS B (200B) that operates the packet forwarding network domain A and the topology information of the packet transfer network A (B). In order for the topology construction module 110 to construct the overall network topology information for the packet transfer network domains A and B, the NMS A 200A and the NMS B 200B transmit topology information in a form recognizable by the topology building module 110 Conversion. Here, the NMS A 200A transmits topology information indicating that A3 and A6 are boundary nodes to the topology construction module 110, and the NMS B 200B transmits topology information indicating that B1 and B3 are boundary nodes, To the module 110. The topology building module 110 aggregates topology information for the packet transport network domains A and B.

In order to integrate topology information for interworking intervals between a plurality of packet transmission network domains, the topology construction module 110 requests neighbor node information of the border node by the NMS A 200A and the NMS B 200B. That is, the topology construction module 110 calls neighbor node information providing APIs of the NMS A 200A and the NMS B 200B to acquire neighbor node information. Accordingly, the topology construction module 110 can construct the topology information for the two boundary nodes that are matched with each other, thereby completing the entire network topology information.

In the API call for retrieving information of the neighbor node, the NMS of the packet transfer network domain can use either (1) a method using a standardized adjacent node search protocol, and (2) a method using MAC table matching at a border node .

The standardized neighbor node search protocol can utilize, for example, standard Ethernet protocol based on Link Layer Discovery Protocol (LLDP). When using the LLDP protocol between adjacent nodes, the network equipment can receive node ID, port information, and MAC information from neighboring nodes. To this end, the integrated NMS 100 identifies the boundary nodes from the topology information collected from the NMS A 200A and the NMS B 200B. Then, the integrated NMS 100 calls an API for activating the neighboring node search protocol such as LLDP for the identified border node from the NMS A 200A and the NMS B 200B. Accordingly, the NMS A 200A collects neighbor node information collected through the LLDP for the nodes A3 and A6 and the neighbor node information collected through the LLDP for the nodes B1 and B3 of the NMS B 200B To the topology building module 110. In the example below, the information in parentheses is the port ID information for the device.

A3 neighbor node information: A2 (p2), B1 (p1)

A6 neighbor node information: A5 (p1), B3 (p2)

B1 neighbor node information: A3 (p1) , B2 (p2)

B3 neighbor node information: A6 (p3) , B4 (p1)

The topology construction module 110 searches for a neighboring node matching based on neighbor node information received from the NMS A 200A and the NMS B 200B. Accordingly, the topology construction module 110 knows that A3-B1 and A6-B3 are connected in the interworking section.

In the method using MAC table matching in a border node, a MAC table is acquired by allowing two boundary nodes constituting an interworking section to transmit arbitrary Ethernet packets, and the topology building module 110 matches the acquired MAC table To find the neighboring node.

In detail, the topology construction module 110 transmits a command to the boundary nodes A3, A6, B1, and B3 of the packet transmission network domains A 210A and B 210B to direct an arbitrary Ethernet packet for neighboring node search to an NMS A (200A) and NMS B (200B), respectively. Here, the destination address of the arbitrarily transmitted packet may be a multicast or broadcast address, and the Ethernet packet received from the neighboring node must be immediately discarded from the corresponding port without being forwarded to the next node.

The NMS A 200A transfers arbitrary Ethernet packets through the ports connected to the external packet transmission network among the ports of the boundary nodes A3 and A6. Accordingly, the border nodes A3 and A6 of the packet transfer network domain A 210A transmit the Ethernet frames having the source MAC addresses a3p1 and a6p3 to the external packet transmission network through the ports p1 and p3, respectively. In the same manner, the border nodes B1 and B3 of the packet transfer network domain B 210B transmit the Ethernet frames having the source MAC addresses b1p1 and b3p2 to the external packet transmission network through the ports p1 and p2, respectively.

The MAC table information constructed for each node after each border node transmits the Ethernet frame to the external packet transmission network is as follows. The MAC address is the source MAC address of the Ethernet frame received by the border node, and the port number indicates the port number at which the Ethernet frame is received.

MAC Table of Node A3 Serial Number MAC address Port number One b1p1 p1

MAC Table of Node A6 Serial Number MAC address Port number One b3p3 p2

MAC Table of Node B1 Serial Number MAC address Port number One a3p1 p1

MAC Table of Node B3 Serial Number MAC address Port number One a6p2 p3

The NMS A 200A and the NMS B 200B collect the constructed MAC table information from each border node and transmit the collected MAC table information to the topology building module 110. The topology construction module 110 can find neighbor nodes and connected ports of each boundary node based on the MAC table information. For example, in the MAC table information constructed by the border node A3, it can be seen that the neighboring node matching the MAC address b1p1 is B1, and the connection is made through the port p1 of A3. The topology building module 110 may find neighbor nodes in the same way for the remaining nodes. On the other hand, when the boundary nodes have the same time synchronization, the MAC table may further include packet transmission / reception time information. Accordingly, the topology construction module 110 can measure the propagation delay time between adjacent nodes.

An integrated node ID may be assigned to nodes belonging to each of a plurality of packet transmission network domains. 1 and 3, nodes A1 to A6 are nodes belonging to the packet transfer network domain A, and nodes B1 to B5 are nodes belonging to the packet transfer network domain B. A 1 to A 6, and B 1 to B 5 are the source node ID of each node, and are identifiable only in the packet transfer network domain to which each node belongs. a to k are the integrated node IDs of the same format assigned by the topology building module 110 to the nodes A1 to A6 and the nodes B1 to B5. The integrated node ID is used when processing sub-modules in the integrated NMS 100, such as the path calculation module 120 and the provisioning module 130. [

Referring to FIG. 3, nodes i, e, j, and f are boundary nodes, and their neighboring nodes and connection port information are known. On the other hand, the delay time represents the propagation delay time of the interlocking section.

In step 320, the integrated NMS 100 performs path computation to create an MPLS-TP tunnel that accepts the requested subscriber line based on the established overall network topology. The integrated NMS 100 may calculate the optimal path in consideration of constraints (bandwidth, delay, redundancy, etc.) of the subscriber line based on the entire network topology constructed in steps 300 to 310. Referring to FIG. 1, the requested subscriber line is connected through node S1 and node S2, S1 is connected to node a, and S2 is connected to node k. Therefore, the path calculation module 120 calculates an optimal path having the node a and the node k as the end nodes. A plurality of routes can be calculated, and the calculated plurality of routes can be output in the form of a list. Two optimal path results are illustrated at the center top of FIG.

The integrated NMS 100 establishes an MPLS-TP tunnel between end nodes according to the calculated path. The MPLS-TP tunnel can be set by the label value calculation (step 330) and the node-specific operation decision (step 340). In this case, each packet forwarding network domain NMS provides a UNI-to-UNI tunnel setting function for nodes managed by the corresponding NMS, a UNI-to-NNI or an NNI-to-NNI MPLS- TP setting function can be provided.

In step 330, the Label module 131 calculates a Label value for all nodes included in the calculated path.

The label module 131 may be calculated randomly considering redundancy with the already assigned Label value, or may be calculated in consideration of the subscriber identification information. Packet delivery network domain NMSs can set Label values individually. However, when the packet transfer network domain NMS sets the Label value separately, the packet transfer network domain NMSs must know the Label value between adjacent nodes so that the label values between the adjacent nodes can be matched. On the contrary, when the Label module 131 collectively sets the Label value to all the nodes included in the path calculated by the path calculation module 120, it is possible to avoid the risk of duplication of the Label value, The MPLS-TP tunnel can be established quickly because there is no need to exchange label information with each other.

Since the Label value must be set in both directions, the Label module 131 individually calculates Label values in the downward direction and the upward direction. For example, referring to FIG. 1, based on the calculated path information (a) - (b) - (i) - (j) - (k) ) -> (i) -> (j) -> (k) direction and a) <- (b) <- (i) <- . When the calculated Label value is set to the actual node through the MPLS-TP tunnel configuration process, which will be described later, the Label values are managed for each link to prevent duplication of labels when setting the label for the next subscriber line.

In step 340, the Label module 131 determines an operation for each node by using the calculated Label value. The Label module 131 includes a total node set (a, b, i, j, k) in a direction (a) -> (b) -> (i) -> (j) (PUSH 10, SWAP 10-> 20, SWAP 20-> 30, SWAP 30-> 40) indicating the operation to be performed by each node included in the entire node set, , POP 40). The Label module 131 also includes a set of all nodes a, b, i, j, and j in the direction (a) <- (b) <- (i) <- (j) <- (POP 11, SWAP 21-> 11, SWAP 31-> 21, SWAP 41-> 31, PUSH 41) is calculated for the entire label operation set. Here, the operation is composed of POP, PUSH, and SWAP. POP is an operation for removing a label value from a packet or a frame entering or leaving the network equipment, PUSH is an operation for adding a label value to a packet or a frame, Or to change the Label value set in the frame to another Label value.

In step 350, the Label module 131 transmits a domain node set, a domain Label value set, and a domain Label operation set to each packet transfer network domain NMS. Here, the domain node set is generated by dividing the entire node set, and a plurality of domain node sets do not include the same element in duplicate. For example, for a total node set (a, b, i, j, k) in direction (a) -> (b) -> (i) -> (A, b, i), and the domain node set transmitted to the packet transfer network domain B is (j, k). Accordingly, the entire label operation set (POP 11, SWAP 21-> 11, SWAP 31-> 21, SWAP 41) in the direction of (a) -> (b) -> (i) -> -> 31, PUSH 41), the domain label operation set (POP 11, SWAP 21-> 11, SWAP 31-> 21) transmitted to the packet transfer network domain A and the domain label operation set (SWAP 41- > 31, PUSH 41).

Meanwhile, the Label module 131 may convert the integrated node ID, which is an element of the domain node set and the domain label operation set, into the source node ID, and then transmit the source node ID to each packet transfer network domain NMS.

At step 360, each packet forwarding network domain NMS provisions network devices with the received domain node set, domain Label value set, and domain Label operation set. That is, using the domain node set, domain label value set, and domain label operation set, the packet delivery network domain NMS determines the bidirectional label value and bidirectional label operation of each network equipment. Each network device thus establishes a bi-directional path between end nodes.

In steps 370 and 380, the OAM module 132 performs tests on the set path. The OAM module 132 calls the OAM test API of each packet transfer network domain NMS to perform a loopback test through the MPLS-TP OAM function at an arbitrary end node. In detail, the OAM module 132 activates the MPLS-TP OAM function using the API of each packet transfer network domain NMS and performs an end-to-end loopback test from each packet transfer network domain A and B. For example, when the node B 2 normally receives an arbitrary LoopBack Request message transmitted by the node A 1, the node B 2 transmits a LoopBack Response message to the node A 1. This result is transmitted to the OAM module 132, and the OAM module 132 can confirm that the end-to-end MPLS-TP tunnel is normally configured. Likewise, the node B2 performs a LoopBack test on the node A1 and informs the OAM module 132 of the result, thereby confirming that the MPLS-TP tunnel can be normally generated in both directions. Here, the LoopBack test may be a Ping test between the end nodes of the subscriber. When the test is successfully performed, the integrated NMS 100 transmits the traffic to the subscriber line, and ends the provisioning process.

If the test between the end nodes fails, the configuration information is internally reconfirmed, and if there is an abnormality next, it is possible to attempt provisioning by selecting the next preferred path among the calculated path lists.

If duplication of the subscriber line is required, it is checked whether there is a section in which paths are overlapped with respect to the calculated plurality of paths. If there is no overlapping section, the provisioning is performed through steps 320 to 360. Thereafter, the protection switching module 133 calls the API for assigning two paths to the protection node group to the end node via each packet transmission network domain NMS. At this time, a shortest path (a path with fewer hops or less delay) is set as a main path, and information including the remaining path as a sub path is transmitted.

After the OAM module 132 performs the LoopBack test for both MPLS-TP tunnels after the primary path / secondary path is established at both end nodes, if there is no abnormality in both MPLS-TP tunnels, the protection switching module 133 performs protection Perform a transfer test. The MPLS-TP protection switching standard supports a manual switching command that allows the operator to intervene directly to force a protection switch. Therefore, the protection switching module 133 instructs the arbitrary end node to perform manual switching, and then confirms switching from the main path to the auxiliary path. If there is no abnormality, manual switching to the main path is performed again.

Figure 4 illustrates a bidirectional Label operation of the nodes in the computed path.

In the downward directional path, node A1 receives a first packet containing a header and data from source S1. The header contains the MAC address of destination S2. Node A1 performs a Label operation that PUSHs the Label value 10 and forwards the second packet to node A2. The second packet is a first packet having a Label value of 10 and information 50 indicating the path PW.

Node A2 receives the second packet from node A1. The node A2 performs a Label operation of SWAP of the Label value 10 to 20 and transmits the third packet to the node A3. The third packet is a second packet having a label value of 20. [

Node A3 receives the third packet from node A2. The node A3 performs the Label operation of SWAPing the Label value 20 to 30 and transmits the fourth packet to the node B1. The fourth packet is a second packet having a Label value of 30. [

Node B1 receives the fourth packet from node A3. The node B1 performs the label operation of SWAP 40 of the label value 30 to transmit the fifth packet to the node B2. The fifth packet is a second packet with a Label value of 40.

Node B2 receives the fifth packet from node B1. Node B2 performs a Label operation that pops a Label value, deletes the path PW, and then transmits the first packet to the destination S2.

Since the Label operation is performed in the same way also in the upward direction route, a description thereof will be omitted.

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

It is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents. .

100: Integrated NMS
110: Topology building module
120: Path calculation module
130: Provisioning module
200A, 200B: Packet transmission network domain NMS
210A, 210B: Packet delivery network domain

Claims (19)

A method for establishing an overall network topology of a telecommunications carrier network in which an integrated network management system is composed of a plurality of heterogeneous packet delivery network domains,
Receiving first topology information from a network management system of a first packet transfer network domain;
Receiving second topology information from a network management system of a second packet transfer network domain;
Generating third topology information of an interworking interval between the first packet transmission network domain and the second packet transmission network domain; And
And constructing the overall network topology information by integrating the first topology information, the second topology information, and the third topology information. 2. The method of claim 1, wherein generating third topology information of an interworking interval between the first packet transfer network domain and the second packet transfer network domain comprises:
Identifying at least one border node belonging to the first packet transport network domain and at least one border node belonging to the second packet transport network domain using the first topology information and the second topology information;
Acquiring neighbor node information of at least one border node belonging to the first packet transfer network domain and at least one border node belonging to the second packet transfer network domain; And
And identifying at least one pair of boundary nodes constituting the interworking section using the neighbor node information. 3. The method of claim 2, wherein the neighbor node information is acquired using an adjacent node discovery protocol. 3. The method of claim 2, wherein the neighbor node information is acquired using MAC table matching. 5. The method of claim 4, wherein the MAC table matching comprises:
The at least one border node belonging to the first packet transfer network domain and the at least one border node belonging to the second packet transfer network domain each carry an Ethernet packet,
The boundary node receiving the Ethernet packet generates the MAC table including the MAC address and the connection port information of the border node that has transmitted the Ethernet packet, and transmits the generated MAC table to the integrated network management system,
And the integrated network management system obtains the neighbor node information by matching the MAC table. 2. The method of claim 1, wherein the step of merging the first topology information, the second topology information, and the third topology information to construct the entire network topology information comprises:
And allocating an aggregation node ID to a node belonging to the first packet transfer network domain and the second packet transfer network domain. 7. The method of claim 6, wherein the node is a network device supporting a Multi-Protocol Label Switching-Transport Profile (MPLS-TP). Constructing an overall network topology of a telecommunications carrier network comprising a first packet transport network domain and a second packet transport network domain, wherein the first packet transport network domain and the second packet transport network domain are heterogeneous packet transport networks;
Calculating at least one optimal path between end nodes using the overall network topology information; And
And setting at least one calculated optimal path,
Wherein the step of establishing the overall network topology of the communication service provider network including the first packet transmission network domain and the second packet transmission network domain comprises:
Receiving first topology information from a network management system of the first packet transfer network domain;
Receiving second topology information from a network management system of the second packet transfer network domain;
Generating third topology information of an interworking interval between the first packet transmission network domain and the second packet transmission network domain; And
And constructing the overall network topology information by integrating the first topology information, the second topology information, and the third topology information. delete The method of claim 8, wherein the step of constructing the overall network topology information by combining the first topology information, the second topology information, and the third topology information comprises:
And assigning an integrated node ID to a node belonging to the first packet transfer network domain and the second packet transfer network domain. 9. The method of claim 8, wherein setting the calculated at least one optimal path comprises:
Calculating a total node set according to the calculated at least one optimal path;
Calculating an entire set of Label values using the entire node set;
Determining an entire Label operation set using the entire set of Label values;
Dividing the entire node set into a first domain node set including only nodes belonging to the first packet transfer network domain and a second domain node set including only nodes belonging to the second packet transfer network domain;
Dividing the entire Label value set into a first domain Label value set and a second domain Label value set based on the first domain node set and the second domain node set; And
Dividing the entire Label operation set into a first domain Label operation set and a second domain Label operation set based on the first domain node set and the second domain node set, Manganese interlocking method. 12. The method of claim 11,
Transmitting the first domain node set, the first domain Label value set, and the first domain Label operation set to the network management system of the first packet transfer network domain; And
Further comprising transmitting the second domain node set, the second domain Label value set, and the second domain Label operation set to a network management system of the second packet forwarding network domain, Manganese interlocking method. 9. The method of claim 8,
And testing at least one or more optimal paths that have been set. The method as claimed in claim 8, wherein the at least one optimal path includes a primary path and a secondary path. A topology building module for establishing an overall network topology of a communication service provider network including a first packet transmission network domain and a second packet transmission network domain, wherein the first packet transmission network domain and the second packet transmission network domain are heterogeneous packet transmission networks;
A path calculation module for calculating at least one optimal path between the end nodes using the overall network topology information; And
And a provisioning module for setting the calculated at least one optimal path,
Wherein the topology building module is configured to receive first topology information from a network management system of the first packet delivery network domain, receive second topology information from a network management system of the second packet transfer network domain, And the second topology information and the third topology information to generate the third topology information of the interworking interval between the second packet transmission network and the second packet transmission network domain and to construct the entire network topology information by integrating the first topology information, the second topology information, Integrated Network Management System for Interworking Networks. delete 16. The system of claim 15, wherein the provisioning module comprises:
Calculating a total node set according to the calculated at least one optimal path,
The entire set of label values is calculated using the entire node set,
And the entire Label operation set is determined using the entire set of Label values. 16. The system of claim 15, wherein the provisioning module comprises:
And an OAM module for testing at least one optimal path set. 16. The method of claim 15, wherein the set at least one optimal path includes a primary path and a secondary path,
Wherein the provisioning module comprises:
And a protection switching module for performing protection switching between the main path and the auxiliary path.

Images