Fast rerouting apparatus and method for MPLS multicast

• US 20060159009A1
• Filed: 01/13/2006
• Published: 07/20/2006
• Est. Priority Date: 01/14/2005
• Status: Abandoned Application

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Kim, Jin-Hyoung, Park, Yong-Seok, Kang, Byung-Chang
• Application Number:
  US11/331,076
• Publication Number:
  US 20060159009A1
• Time in Patent Office: Days
• US Class Current: 370/216
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]

Abstract

Disclosed is a fast rerouting apparatus and method for multiprotocol label switching (MPLS) multicast. The fast rerouting apparatus and method is to rapidly cope with a failure occurring on an MPLS network. The fast rerouting method of redirecting a packet to be transmitted at the nearest location from a location where the failure occurs is applied to the MPLS multicast, so that it is possible to rapidly cope with the failure generated when an MPLS multicast packet is transmitted.

Claims

1. A fast rerouting apparatus for multiprotocol label switching (MPLS) multicast, comprising:

a message sender for sending and receiving a message to and from an upstream or downstream node;

a message processor for, when a path requested for routing through a routing request message from the upstream node is a path to perform fast rerouting, sending the routing request message for establishing a Next Hop database (NHDB) to the downstream node through the message sender, and establishing the Next Hop database (NHDB) using information included in a response message received from the downstream node; and

a storage for storing the established Next Hop database (NHDB).

2. The fast rerouting apparatus of claim 1, wherein checking whether the corresponding path is a path requested for the fast rerouting or not is performed using session information of the corresponding path requested for the fast rerouting.

3. The fast rerouting apparatus of claim 1, wherein the Next Hop database (NHDB) includes information on network addresses and labels of a next downstream node and a next-next downstream node.

4. The fast rerouting apparatus of claim 3, wherein the network address information is IPv4 address information.

5. The fast rerouting apparatus of claim 1, wherein information used for establishment of the Next Hop database (NHDB) is transmitted through a Next Hop object and a Next-Next Hop object of a resource reservation protocol-traffic engineering (RSVP-TE) protocol received from the downstream node.

6. The fast rerouting apparatus of claim 5, wherein the Next Hop object includes information on a network address and a label of the next downstream node.

7. The fast rerouting apparatus of claim 5, wherein the Next-Next Hop object includes information on a network address and a label of the next-next downstream node.

8. The fast rerouting apparatus of claim 1, further comprising a path computer for computing and determining a path with reference to the established Next Hop database (NHDB).

9. The fast rerouting apparatus of claim 8, wherein the path computer obtains information on a destination network address of a backup path from the Next Hop database (NHDB), and obtains routing information routed to the network address using a constraint-based shortest path first (CSPF).

10. A protocol for fast rerouting for multiprotocol label switching (MPLS) multicast, the protocol comprising:

a Next Hop object including information for establishing a Next Hop database (NHDB) used when a path for the fast rerouting of the MPLS multicast is established;

a Next-Next Hop object including information for establishing the Next Hop database (NHDB); and

a Unicast Backup LSP (Label Switched Path) Request object requesting another node of a corresponding multicast tree to set up a unicast backup path.

11. The protocol of claim 10, wherein the Next Hop object includes information on a network address and a label of a next downstream node.

12. The protocol of claim 10, wherein the Next-Next Hop object includes information on a network address and a label of a next-next downstream node.

13. The protocol of claim 10, wherein the Unicast Backup LSP Request object includes information on an end point network address of a tunnel used for setup of the unicast backup path, information on a label allocated to a corresponding multicast group address at the end point, information on a multicast source address to be transmitted to the tunnel, and information on a multicast group address to transmitted to the tunnel.

14. A fast rerouting apparatus for multiprotocol label switching (MPLS) multicast on a MPLS network where a replacement path for fast rerouting for the MPLS multicast, the fast rerouting apparatus comprising:

a message sender for sending and receiving a message to and from an upstream and downstream node;

a failure detector for determining whether a failure occurs between the downstream node and another node or not;

a path computer for searching the replacement node of the node where the failure occurs; and

a packet processor for determining whether a multicast packet received from the upstream node is a packet which must be transmitted through both the path where the failure occurs and the replacement path, and when the multicast packet must be transmitted through both of the paths, transmitting the multicast packet to a next branch node in a multicast packet format, and setting up a unicast backup path from the next branch node to a destination node of the packet.

15. The fast rerouting apparatus of claim 14, wherein the path computer sets up the unicast backup path from the next branch node to the destination node of the packet by transmitting a message requesting a Unicast Backup LSP (Label Switched Path) Request object to the branch node through the message sender.

16. The fast rerouting apparatus of claim 14, wherein the failure detector determines whether the failure occurs or not through exchange of a Hello message with a neighboring node.

17. The fast rerouting apparatus of claim 16, wherein the failure detector determines that the failure occurs between the neighboring node and a corresponding node when no message is received from the neighboring node in excess of a predetermined reference time.

18. The fast rerouting apparatus of claim 14, wherein the failure occurs at a link connecting with the downstream node or at the downstream node.

19. A fast rerouting method for multiprotocol label switching (MPLS) multicast, comprising:

a first step of receiving information for establishing a Next Hop database (NHDB) used for fast rerouting on a network from a downstream node;

a second step of establishing the Next Hop database (NHDB) using the received information; and

a third step of establishing a path for the fast rerouting for the MPLS multicast using the established Next Hop database (NHDB).

20. The fast rerouting method of claim 19, wherein information for establishment of the Next Hop database (NHDB) is received through a Next Hop object and a Next-Next Hop object received from the downstream node.

21. The fast rerouting method of claim 19, wherein the Next Hop database (NHDB) includes information on network addresses and labels of a next downstream node and a next-next downstream node.

22. The fast rerouting method of claim 19, wherein in the third step, the establishment of the path is performed using a constraint-based shortest path first (CSPF).

23. A fast rerouting method for multiprotocol label switching (MPLS) multicast on a network where a backup path for fast rerouting for the MPLS multicast used is established using a Next Hop database (NHDB), the fast rerouting method comprising:

a first step of detecting generation of a failure on a protected path;

a second step of searching the backup path of the protected path where the failure occurs;

a third step of determining whether the backup path belongs to existing transmission path of a multicast packet received from an upstream node or not; and

a fourth step of transmitting the multicast packet to a next branch node on the backup path belonging to the existing transmission path in a multicast packet format, and requesting the branch node to establish a unicast backup path from the branch node to an end node of the backup node.

24. The fast rerouting method of claim 23, wherein the established unicast backup path is a path selected by using an Unicast Backup LSP (Label Switched Path) Request object and a constraint-based shortest path first (CSPF).