+

US8248917B2 - Method and system for implementing protection switching in multi-protocol label switching network - Google Patents

Method and system for implementing protection switching in multi-protocol label switching network Download PDF

Info

Publication number
US8248917B2
US8248917B2 US11/688,972 US68897207A US8248917B2 US 8248917 B2 US8248917 B2 US 8248917B2 US 68897207 A US68897207 A US 68897207A US 8248917 B2 US8248917 B2 US 8248917B2
Authority
US
United States
Prior art keywords
lsr
egress
lsp
ingress
probe packets
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US11/688,972
Other versions
US20070242605A1 (en
Inventor
Wenyang LEI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=36118579&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=US8248917(B2) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Assigned to HUAWEI TECHNOLOGIES CO., LTD. reassignment HUAWEI TECHNOLOGIES CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LEI, WENYANG
Publication of US20070242605A1 publication Critical patent/US20070242605A1/en
Application granted granted Critical
Publication of US8248917B2 publication Critical patent/US8248917B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Definitions

  • the present invention relates to the Multi-protocol Label Switching (MPLS) technique, and more particularly, to a method and a system for implementing protection switching in an MPLS network.
  • MPLS Multi-protocol Label Switching
  • the MPLS technique as a key technique in Next Generation Network, has been playing a more and more important role in IP networks.
  • the MPLS technique was put forward to increase the forwarding speed of routers; however, it has been widely applied in the fields of traffic engineering, Virtual Private network (VPN) and Quality of Service (QoS) because of its inherent advantages and is becoming an important standard in large scale IP networks.
  • VPN Virtual Private network
  • QoS Quality of Service
  • LSP Label Switched Path
  • LSR Label Switching Routers
  • protection switching enhances the reliability and availability performance of MPLS networks.
  • the protection switching implies that both routing and resources are pre-calculated and allocated to a dedicated protection LSP prior to failures of a working LSP. The protection switching therefore offers a strong assurance of being able to re-obtain the required network resources when the LSP connectivity is defected or interrupted.
  • FIG. 1 is a flow chart illustrating the protection switching in MPLS network in an existing art. As shown in FIG. 1 , the method includes the following steps of:
  • Step 101 an Ingress LSR transmitting periodically probe packets via an LSP to an Egress LSR.
  • Step 102 if the Egress LSR does not receive the probe packets within pre-determined times, determining that the LSP is failed; the Egress LSR then transmitting a Backward Defect Indication (BDI) message to the Ingress LSR via a reverse path, to notify the Ingress LSR the failure of the LSP.
  • BDI Backward Defect Indication
  • Step 103 upon receiving the BDI message, the Ingress LSR switching the working traffic to a protection LSP.
  • FIG. 2 is a schematic diagram illustrating the protection switching in the MPLS network in the existing art.
  • the working traffic is distributed to the working LSP.
  • the Egress LSR if not receiving the probe packets within pre-determined times, transmits the BDI message to the Ingress LSR via a reverse path.
  • the Ingress LSR switches the working traffic to the protection LSP.
  • the Ingress LSR determines that the LSP has been failed while receiving the BDI message, and correspondingly switches the working traffic.
  • the Egress LSR is likely unable to transmit the BDI message to the Ingress LSR.
  • the Ingress LSR thus may not switch the working traffic, as it may not learn that a failure of the working LSP occurs.
  • the Ingress LSR may not switch the working traffic when a failure of the Egress LSR occurs in the existing art, since the failed Egress LSR could't notify the Ingress LSR the failure in time. Consequently, the working LSP and protection LSP may only be terminated at the same Egress LSR limitedly. That is, the Ingress LSR is failed to terminate the working LSP and protection LSP at different Egress LSRs, as the Ingress LSR can not learn the working status of the Egress LSR, thereby reducing the security of the MPLS network.
  • the embodiments of the present invention provide a method and a system for implementing protection switching in MPLS network, to enable an Ingress LSR to switch working traffic when a failure of an Egress LSR occurs.
  • a method for implementing protection switching in MPLS network includes:
  • a system for implementing protection switching in Multi-protocol Label Switching (MPLS) network includes:
  • an Ingress LSR configured to receive first probe packets from the first Egress LSR through a first LSP, and switch working traffic to a third LSP terminated at the second Egress LSR if the Ingress LSR does not receive the first probe packets.
  • the first LSP between the Ingress LSR and the first Egress LSR is established, and the first Egress LSR transmits probe packets to the Ingress LSR via the first LSP.
  • the Ingress LSR performs working traffic switching.
  • the Ingress LSR may learn the failure of the Egress LSR according to the result of receiving the probe packets when a failure of the Egress LSR occurs, and switches the working traffic correspondingly.
  • the working traffic may be switched from the working LSP to a protection LSP connected to other Egress LSR working normally when the working traffic needs to be switched, since the Ingress LSR may learn the failure of the Egress LSR.
  • the Ingress LSR may not learn the failure of the Egress LSR, thus may not switch the working LSP to a protection LSP connected to other Egress LSR working normally when a failure of the Egress LSR occurs. Therefore, the working LSP and protection LSP are not limited to be terminated at a same Egress LSR, but correspond to different Egress LSRs after the embodiment of the present invention is applied, which greatly improves the security of the MPLS network.
  • FIG. 1 is a flow chart illustrating the protection switching in MPLS network in an existing art.
  • FIG. 2 is a schematic diagram illustrating the protection switching in MPLS network in the existing art.
  • FIG. 3 is a flow chart illustrating the protection switching in MPLS network according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram illustrating the protection switching in MPLS network according to another embodiment of the present invention.
  • a first LSP is firstly established between an Ingress LSR and a first Egress LSR, and the first Egress LSR transmits first probe packets to the Ingress LSR via the first LSP.
  • the Ingress LSR determines whether to switch working traffic according to the result of receiving the probe packets transmitted by the first Egress LSR.
  • FIG. 3 is a schematic flow chart illustrating the protection switching in MPLS network according to an embodiment of the present invention. As shown in FIG. 3 , the method includes the following steps.
  • Step 301 establishing a first LSP from a first Egress LSR to an Ingress LSR, and a second LSP from the Ingress LSR to the first Egress LSR.
  • the traffic of various services in the MPLS network are generally bidirectional, and these bidirectional traffics are implemented via two LSPs. Firstly, establish the first LSP and the second LSP between the Ingress LSR and the first Egress LSR, wherein the first LSP may or may not correspond to the second LSP. The first LSP and second LSP may be further bounded after being established, by which a bidirectional LSP is established actually.
  • Step 302 the first Egress LSR transmitting first probe packets to the Ingress LSR via the first LSP; and the Ingress LSR transmitting second probe packets to the first Egress LSR via the second LSP.
  • the first probe packets transmitted by the first Egress LSR to the Ingress LSR, as well as the second probe packets transmitted by the Ingress LSR to the first Egress LSR, may be Connectivity Verification (CV) packets or Fast Failure Detection (FFD) packets. Both the CV packets and FFD packets are used to verify the connectivity of LSP in the MPLS network. Moreover, both the formats and contents of the CV packets and FFD packets are the same, while the only difference between the CV packets and FFD packets is the different transmitting frequency.
  • CV Connectivity Verification
  • FFD Fast Failure Detection
  • the first Egress LSR transmits the first probe packets periodically to the Ingress LSR.
  • the Ingress LSR periodically transmits the second probe packets to the first Egress LSR.
  • the transmitting speed of the CV packets is one packet per second, that is, the first Egress LSR periodically transmits to the Ingress LSR the CV packets of which the transmission interval is one second, or the Ingress LSR periodically transmits to the first Egress LSR the CV packets of which the transmission interval is one second.
  • the transmitting speed of the FFD packets is one packet per fifty milliseconds, that is, the first Egress LSR periodically transmits to the Ingress LSR the FFD packets of which the transmission interval is fifty milliseconds, or the Ingress LSR periodically transmits to the first Egress LSR the FFD packets of which the transmission interval is fifty milliseconds.
  • the transmitting cycles of the CV packets and FFD packets may be modified according to real requirements.
  • Step 303 the Ingress LSR switching the working traffic to a protection LSP, when the Ingress LSR does not receive the first probe packets transmitted by the first Egress LSR, or the first Egress LSR does not receive the second probe packets transmitted by the Ingress LSR.
  • the Ingress LSR when not receiving the first probe packets transmitted by the first Egress LSR, the Ingress LSR determines that a failure of the first LSP or the first Egress LSR has occurred, and switches the working traffic. Similarly, the Ingress LSR, when the first Egress LSR does not receive the second probe packets transmitted by the Ingress LSR, also starts to switch the working traffic.
  • a receiving threshold N 1 for the first probe packets may be preset. If the Ingress LSR does not receive the first probe packets for consecutive N 1 times, the Ingress LSR switches the working traffic. More preferably, the N 1 mentioned herein equals to 3.
  • a receiving threshold N 2 for the second probe packets may be preset. If the first Egress LSR does not receive the second probe packets for consecutive N 2 times, the Ingress LSR switches the working traffic. For example, the first Egress LSR transmits a BDI message to the Ingress LSR via a reverse path, i.e. the first LSP, when not receiving the second probe packets for consecutive N 2 times. The Ingress LSR implements switching upon receiving the BDI message. More preferably, the N 2 mentioned herein equals to 3.
  • the working traffic may be switched to the protection LSP.
  • the working traffic may be switched to the protection LSP connected to the first Egress LSR.
  • a third LSP from the Ingress LSR to a second Egress LSR may be firstly established, which is used as a protection LSP.
  • the working traffic may be switched to the third LSP.
  • a fourth LSP from the second Egress LSR to the Ingress LSR may be further established.
  • the second Egress LSR transmits third probe packets to the Ingress LSR via the fourth LSP.
  • the Ingress LSR again switches the working traffic to a next protection LSP which may be a protection LSP connected to the second Egress LSR.
  • the Ingress LSR may further connect to a third Egress LSR, to switch the working traffic to the protection LSP between the Ingress LSR and the third Egress LSR when a failure of the second Egress LSR occurs.
  • the Ingress LSR is granted to switch the working traffic successfully again when a failure of the second Egress LSR occurs. It is easy to be appreciated that the Ingress LSR may further connect to more Egress LSRs to improve the security of the MPLS network.
  • FIG. 4 is a schematic diagram illustrating the protection switching in MPLS network according to another embodiment of the present invention.
  • a bidirectional LSP serving as the working LSP, between the Ingress LSR and the first Egress LSR.
  • the bidirectional LSP includes two unidirectional LSPs.
  • the Ingress LSR and the first Egress LSR respectively transmits a CV/FFD packet in the transmitting direction of the two unidirectional LSPs, and detect and receive the CV/FFD packet transmitted to them.
  • another bidirectional LSP serving as the protection LSP, between the Ingress LSR and the second Egress LSR, and the another bidirectional LSP includes two unidirectional LSPs as well.
  • the working traffic is distributed to the working LSP connected to the first Egress LSR. If the first Egress LSR does not receive the CV/FED packets from the Ingress LSR, the first Egress LSR determines that a failure of the working LSP occurs, and transmits the BDI message to the Ingress LSR via the reverse path. The Ingress LSR thus determines that a failure of the working LSP occurs. When receiving the BDI message or not receiving the probe packets transmitted by the first Egress LSR, the Ingress LSR switches the working traffic to the protection LSP connected to the second Egress LSR.
  • the Ingress LSR connects to the second Egress LSR to serve as a protection of the working LSP.
  • the embodiment of the present invention is not limited to this.
  • the Ingress LSR may also connect to multiple other Egress LSRs to serve as farther protections according to the embodiment of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiments of the present invention provide a method and a system for implementing protection switching in Multi-protocol Label Switching (MPLS) network, the method includes: transmitting by a first Egress Label Switched Router (LSR) first probe packets to an Ingress LSR via a first Label Switching Path (LSP); switching by the Ingress LSR working traffic to a third LSP terminated at a second Egress LSR when the Ingress LSR does not receive the first probe packets. According to the embodiments of the present invention, the Ingress LSR may learn the failure of the Egress LSR according to the result of receiving the probe packets when a failure of the Egress LSR occurs, and switches the working traffic correspondingly. Moreover, the working LSP and protection LSP are not terminated at a same Egress LSR, but correspond to different Egress LSRs which greatly improves the security of the MPLS network.

Description

FIELD OF THE INVENTION
The present invention relates to the Multi-protocol Label Switching (MPLS) technique, and more particularly, to a method and a system for implementing protection switching in an MPLS network.
BACKGROUND OF THE INVENTION
The MPLS technique, as a key technique in Next Generation Network, has been playing a more and more important role in IP networks. At the beginning, the MPLS technique was put forward to increase the forwarding speed of routers; however, it has been widely applied in the fields of traffic engineering, Virtual Private network (VPN) and Quality of Service (QoS) because of its inherent advantages and is becoming an important standard in large scale IP networks.
In the MPLS network, a label switching is used to forward data packets, and thus the routing of network may be controlled flexibly. The Forwarding path of data packet, in the MPLS network, is called Label Switched Path (LSP). The LSP is defined by the switching of label value, and the label value of data packet is switched at Label Switching Routers (LSRs) which may include an Ingress LSR and an Egress LSR.
In the MPLS network, it has become a pressing issue to detect failures and implement protection switching, as the MPLS technique has become a key technique for IP network multi-service bearer. Protection switching enhances the reliability and availability performance of MPLS networks. The protection switching implies that both routing and resources are pre-calculated and allocated to a dedicated protection LSP prior to failures of a working LSP. The protection switching therefore offers a strong assurance of being able to re-obtain the required network resources when the LSP connectivity is defected or interrupted.
FIG. 1 is a flow chart illustrating the protection switching in MPLS network in an existing art. As shown in FIG. 1, the method includes the following steps of:
Step 101: an Ingress LSR transmitting periodically probe packets via an LSP to an Egress LSR.
Step 102: if the Egress LSR does not receive the probe packets within pre-determined times, determining that the LSP is failed; the Egress LSR then transmitting a Backward Defect Indication (BDI) message to the Ingress LSR via a reverse path, to notify the Ingress LSR the failure of the LSP.
Step 103: upon receiving the BDI message, the Ingress LSR switching the working traffic to a protection LSP.
FIG. 2 is a schematic diagram illustrating the protection switching in the MPLS network in the existing art. As shown in FIG. 2, in a normal condition, the working traffic is distributed to the working LSP. The Egress LSR, if not receiving the probe packets within pre-determined times, transmits the BDI message to the Ingress LSR via a reverse path. Upon receiving the BDI message, the Ingress LSR switches the working traffic to the protection LSP.
In the existing art, the Ingress LSR determines that the LSP has been failed while receiving the BDI message, and correspondingly switches the working traffic. However, when a failure of the Egress LSR occurs, if a failure of the working LSP occurs, the Egress LSR is likely unable to transmit the BDI message to the Ingress LSR. The Ingress LSR thus may not switch the working traffic, as it may not learn that a failure of the working LSP occurs.
Furthermore, the Ingress LSR may not switch the working traffic when a failure of the Egress LSR occurs in the existing art, since the failed Egress LSR couldn't notify the Ingress LSR the failure in time. Consequently, the working LSP and protection LSP may only be terminated at the same Egress LSR limitedly. That is, the Ingress LSR is failed to terminate the working LSP and protection LSP at different Egress LSRs, as the Ingress LSR can not learn the working status of the Egress LSR, thereby reducing the security of the MPLS network.
SUMMARY OF THE INVENTION
The embodiments of the present invention provide a method and a system for implementing protection switching in MPLS network, to enable an Ingress LSR to switch working traffic when a failure of an Egress LSR occurs.
A method for implementing protection switching in MPLS network, includes:
transmitting, by a first Egress LSR, first probe packets to an Ingress LSR via a first LSP;
switching, by the Ingress LSR, working traffic to a third LSP terminated at a second Egress LSR when the Ingress LSR does not receive the first probe packets.
A system for implementing protection switching in Multi-protocol Label Switching (MPLS) network, includes:
a first Egress LSR;
a second Egress LSR;
an Ingress LSR, configured to receive first probe packets from the first Egress LSR through a first LSP, and switch working traffic to a third LSP terminated at the second Egress LSR if the Ingress LSR does not receive the first probe packets.
It can be seen from the above technical solution that, according to the embodiments of the present invention, the first LSP between the Ingress LSR and the first Egress LSR is established, and the first Egress LSR transmits probe packets to the Ingress LSR via the first LSP. When not receiving the probe packets, the Ingress LSR performs working traffic switching. Accordingly, in the application of the embodiments of the present invention, the Ingress LSR may learn the failure of the Egress LSR according to the result of receiving the probe packets when a failure of the Egress LSR occurs, and switches the working traffic correspondingly.
Furthermore, in the application of the embodiments of the present invention, the working traffic may be switched from the working LSP to a protection LSP connected to other Egress LSR working normally when the working traffic needs to be switched, since the Ingress LSR may learn the failure of the Egress LSR. In the existing art, however, the Ingress LSR may not learn the failure of the Egress LSR, thus may not switch the working LSP to a protection LSP connected to other Egress LSR working normally when a failure of the Egress LSR occurs. Therefore, the working LSP and protection LSP are not limited to be terminated at a same Egress LSR, but correspond to different Egress LSRs after the embodiment of the present invention is applied, which greatly improves the security of the MPLS network.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a flow chart illustrating the protection switching in MPLS network in an existing art.
FIG. 2 is a schematic diagram illustrating the protection switching in MPLS network in the existing art.
FIG. 3 is a flow chart illustrating the protection switching in MPLS network according to an embodiment of the present invention.
FIG. 4 is a schematic diagram illustrating the protection switching in MPLS network according to another embodiment of the present invention.
 DETAILED DESCRIPTION OF THE INVENTION
The present invention will be described in detail hereinafter with reference to the accompanying drawings and embodiments, so as to make the technical solution and merits of the present invention more apparent.
According to the embodiments of the present invention, a first LSP is firstly established between an Ingress LSR and a first Egress LSR, and the first Egress LSR transmits first probe packets to the Ingress LSR via the first LSP. The Ingress LSR then determines whether to switch working traffic according to the result of receiving the probe packets transmitted by the first Egress LSR.
FIG. 3 is a schematic flow chart illustrating the protection switching in MPLS network according to an embodiment of the present invention. As shown in FIG. 3, the method includes the following steps.
Step 301: establishing a first LSP from a first Egress LSR to an Ingress LSR, and a second LSP from the Ingress LSR to the first Egress LSR.
The traffic of various services in the MPLS network are generally bidirectional, and these bidirectional traffics are implemented via two LSPs. Firstly, establish the first LSP and the second LSP between the Ingress LSR and the first Egress LSR, wherein the first LSP may or may not correspond to the second LSP. The first LSP and second LSP may be further bounded after being established, by which a bidirectional LSP is established actually.
Step 302: the first Egress LSR transmitting first probe packets to the Ingress LSR via the first LSP; and the Ingress LSR transmitting second probe packets to the first Egress LSR via the second LSP.
The first probe packets transmitted by the first Egress LSR to the Ingress LSR, as well as the second probe packets transmitted by the Ingress LSR to the first Egress LSR, may be Connectivity Verification (CV) packets or Fast Failure Detection (FFD) packets. Both the CV packets and FFD packets are used to verify the connectivity of LSP in the MPLS network. Moreover, both the formats and contents of the CV packets and FFD packets are the same, while the only difference between the CV packets and FFD packets is the different transmitting frequency.
Preferably, the first Egress LSR transmits the first probe packets periodically to the Ingress LSR. And the Ingress LSR periodically transmits the second probe packets to the first Egress LSR. More preferably, when the CV packets are used as the first probe packets and/or the second probe packets, the transmitting speed of the CV packets is one packet per second, that is, the first Egress LSR periodically transmits to the Ingress LSR the CV packets of which the transmission interval is one second, or the Ingress LSR periodically transmits to the first Egress LSR the CV packets of which the transmission interval is one second. More preferably, when the FFD packets are used as the first probe packets and/or the second probe packets, the transmitting speed of the FFD packets is one packet per fifty milliseconds, that is, the first Egress LSR periodically transmits to the Ingress LSR the FFD packets of which the transmission interval is fifty milliseconds, or the Ingress LSR periodically transmits to the first Egress LSR the FFD packets of which the transmission interval is fifty milliseconds. Correspondingly, the transmitting cycles of the CV packets and FFD packets may be modified according to real requirements.
Step 303: the Ingress LSR switching the working traffic to a protection LSP, when the Ingress LSR does not receive the first probe packets transmitted by the first Egress LSR, or the first Egress LSR does not receive the second probe packets transmitted by the Ingress LSR.
Herein, when not receiving the first probe packets transmitted by the first Egress LSR, the Ingress LSR determines that a failure of the first LSP or the first Egress LSR has occurred, and switches the working traffic. Similarly, the Ingress LSR, when the first Egress LSR does not receive the second probe packets transmitted by the Ingress LSR, also starts to switch the working traffic.
Preferably, a receiving threshold N1 for the first probe packets may be preset. If the Ingress LSR does not receive the first probe packets for consecutive N1 times, the Ingress LSR switches the working traffic. More preferably, the N1 mentioned herein equals to 3.
Similarly, a receiving threshold N2 for the second probe packets may be preset. If the first Egress LSR does not receive the second probe packets for consecutive N2 times, the Ingress LSR switches the working traffic. For example, the first Egress LSR transmits a BDI message to the Ingress LSR via a reverse path, i.e. the first LSP, when not receiving the second probe packets for consecutive N2 times. The Ingress LSR implements switching upon receiving the BDI message. More preferably, the N2 mentioned herein equals to 3.
When switched, the working traffic may be switched to the protection LSP. For instance, the working traffic may be switched to the protection LSP connected to the first Egress LSR.
Preferably, a third LSP from the Ingress LSR to a second Egress LSR may be firstly established, which is used as a protection LSP. When switched, the working traffic may be switched to the third LSP. More preferably, a fourth LSP from the second Egress LSR to the Ingress LSR may be further established. After the Ingress LSR switches the working traffic to the third LSP, the second Egress LSR transmits third probe packets to the Ingress LSR via the fourth LSP. When not receiving the third probe packets, the Ingress LSR again switches the working traffic to a next protection LSP which may be a protection LSP connected to the second Egress LSR. Correspondingly, the Ingress LSR may further connect to a third Egress LSR, to switch the working traffic to the protection LSP between the Ingress LSR and the third Egress LSR when a failure of the second Egress LSR occurs. Thus, the Ingress LSR is granted to switch the working traffic successfully again when a failure of the second Egress LSR occurs. It is easy to be appreciated that the Ingress LSR may further connect to more Egress LSRs to improve the security of the MPLS network.
FIG. 4 is a schematic diagram illustrating the protection switching in MPLS network according to another embodiment of the present invention. As shown in FIG. 4, there is a bidirectional LSP, serving as the working LSP, between the Ingress LSR and the first Egress LSR. The bidirectional LSP includes two unidirectional LSPs. The Ingress LSR and the first Egress LSR respectively transmits a CV/FFD packet in the transmitting direction of the two unidirectional LSPs, and detect and receive the CV/FFD packet transmitted to them. Additionally, there is another bidirectional LSP serving as the protection LSP, between the Ingress LSR and the second Egress LSR, and the another bidirectional LSP includes two unidirectional LSPs as well.
In normal condition, the working traffic is distributed to the working LSP connected to the first Egress LSR. If the first Egress LSR does not receive the CV/FED packets from the Ingress LSR, the first Egress LSR determines that a failure of the working LSP occurs, and transmits the BDI message to the Ingress LSR via the reverse path. The Ingress LSR thus determines that a failure of the working LSP occurs. When receiving the BDI message or not receiving the probe packets transmitted by the first Egress LSR, the Ingress LSR switches the working traffic to the protection LSP connected to the second Egress LSR.
In the above embodiments, the Ingress LSR connects to the second Egress LSR to serve as a protection of the working LSP. However, the embodiment of the present invention is not limited to this. The Ingress LSR may also connect to multiple other Egress LSRs to serve as farther protections according to the embodiment of the present invention.
To sum up, the foregoing descriptions are only preferred embodiments of the present invention and are not for use in limiting the protection scope thereof. Any modification, equivalent replacement or improvement made under the spirit and principles of the present invention is included in the protection scope of the claims of the present invention.

Claims (14)

1. A method for implementing protection switching in Multi-protocol Label Switching “MPLS” network, comprising:
transmitting, by a first Egress Label Switching Router “LSR,” first probe packets to an Ingress LSR via a first Label Switched Path “LSP”;
switching, by the Ingress LSR, working traffic to a third LSP terminated at a second Egress LSR when the Ingress LSR does not receive the first probe packets, wherein the second Egress LSR is different from the first Egress LSR.
2. The method of claim 1, further comprising:
transmitting, by the Ingress LSR, second probe packets to the first Egress LSR via a second LSP;
switching, by the Ingress LSR, the working traffic upon receiving a Backward Defect Indication “BDI” message from the first Egress LSR.
3. The method of claim 2, wherein the process of switching by the Ingress LSR the working traffic upon receiving the BDI message comprises:
switching, by the Ingress LSR, the working traffic to the third LSP upon receiving the BDI message.
4. The method of claim 2, wherein the process of switching by the Ingress LSR the working traffic upon receiving the BDI message comprises:
switching, by the Ingress LSR, the working traffic to a protection LSP between the Ingress LSR and the first Egress LSR upon receiving the BDI message.
5. The method of claim 2, wherein the second probe packets comprise one of CV packets and FFD packets.
6. The method of claim 2, wherein the process of transmitting the second probe packets to the first Egress LSR comprises:
transmitting periodically, by the Ingress LSR, the second probe packets to the first Egress LSR.
7. The method of claim 2, further comprising:
setting a receiving threshold N2 for the second probe packets;
when the first Egress LSR does not receive the second probe packets for consecutive N2 times, sending the BDI message to the Ingress LSR.
8. The method of claim 1, wherein the first probe packets comprise one of Connectivity Verification “CV” packets and Fast Failure Detection “FFD” packets.
9. The method of claim 1, further comprising:
after switching by the Ingress LSR the working traffic to the third LSP, transmitting, by the second Egress LSR, third probe packets to the Ingress LSR via a fourth LSP;
switching, by the Ingress LSR, the working traffic to an LSP terminated at a third Egress LSR when the Ingress LSR does not receive the third probe packets.
10. The method of claim 1, wherein the process of transmitting the first probe packets to the Ingress LSR comprises:
transmitting periodically, by the first Egress LSR, the first probe packets to the Ingress LSR.
11. The method of claim 1, further comprising:
setting a receiving threshold N1 for the first probe packets;
the Ingress LSR does not receive the first probe packets comprises:
the Ingress LSR does not receive the first probe packets for consecutive N1 times.
12. A system for implementing protection switching in Multi-protocol Label Switching “MPLS” network, comprising:
a first Egress Label Switching Router “LSR”;
a second Egress LSR;
an Ingress LSR, configured to receive first probe packets from the first Egress LSR through a first Label Switched Path “LSP,” and to switch working traffic to a third LSP terminated at the second Egress LSR if the Ingress LSR does not receive the first probe packets;
wherein the second Egress LSR is different from the first Egress LSR.
13. The system of claim 12, wherein the Ingress LSR is further configured to transmit second probe packets to the first Egress LSR through a second LSP, and switch the working traffic to a protection LSP between the Ingress LSR and the first Egress LSR or the third LSP upon receiving a Backward Defect Indication “BDI” message from the first Egress LSR.
14. The system of claim 12, further comprising:
a third Egress LSR;
the Ingress LSR is further configured to receive third probe packets from the second Egress LSR through a fourth LSP, and switch the working traffic to an LSP terminated at the third Egress LSR when the Ingress LSR does not receive the third probe packets.
US11/688,972 2004-09-27 2007-03-21 Method and system for implementing protection switching in multi-protocol label switching network Active 2028-02-24 US8248917B2 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CNB2004100809366A CN100359860C (en) 2004-09-27 2004-09-27 A protection switching method for a multi-protocol label switching network
CN200410080936.6 2004-09-27
CN200410080936 2004-09-27
PCT/CN2005/001568 WO2006034639A1 (en) 2004-09-27 2005-09-26 A protection switching method of a multi-protocol label switching network

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001568 Continuation WO2006034639A1 (en) 2004-09-27 2005-09-26 A protection switching method of a multi-protocol label switching network

Publications (2)

Publication Number Publication Date
US20070242605A1 US20070242605A1 (en) 2007-10-18
US8248917B2 true US8248917B2 (en) 2012-08-21

Family

ID=36118579

Family Applications (1)

Application Number Title Priority Date Filing Date
US11/688,972 Active 2028-02-24 US8248917B2 (en) 2004-09-27 2007-03-21 Method and system for implementing protection switching in multi-protocol label switching network

Country Status (7)

Country Link
US (1) US8248917B2 (en)
EP (1) EP1793530B1 (en)
CN (1) CN100359860C (en)
ES (1) ES2386900T3 (en)
PL (1) PL1793530T3 (en)
PT (1) PT1793530E (en)
WO (1) WO2006034639A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160112349A1 (en) * 2014-10-16 2016-04-21 Electronics And Telecommunications Research Institute Method for providing protection switching service in virtual tenant network and controller therefor

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100696176B1 (en) * 2005-12-09 2007-03-20 한국전자통신연구원 MPS LSP Protection Alternating Device and Method
GB0702508D0 (en) * 2007-02-09 2007-03-21 Ericsson Telefon Ab L M Label switched path networking
CN100558082C (en) * 2007-03-20 2009-11-04 华为技术有限公司 A communication system, a label switching router, and a routing switching method
CN100583827C (en) 2007-05-17 2010-01-20 华为技术有限公司 Method and equipment for multiple protocol label switching network flow switchover
CN101316225B (en) * 2007-05-30 2012-12-12 华为技术有限公司 Fault detection method, communication system and label exchange router
CN101094175B (en) * 2007-06-14 2011-06-01 华为技术有限公司 Method, device and system for multicast traffic protection
CN101364926B (en) * 2007-08-08 2011-06-01 华为技术有限公司 Method and apparatus for network protection
WO2009040244A1 (en) * 2007-09-28 2009-04-02 Telefonaktiebolaget Lm Ericsson (Publ) Telecommunication network
CN101369922B (en) 2008-09-28 2011-04-06 华为技术有限公司 Connectivity detection method and maintenance field terminal and system
CN101431459B (en) * 2008-12-17 2011-05-04 烽火通信科技股份有限公司 Looped network protection method for transmitting multiprotocol label switching network
CN101826989B (en) * 2009-03-02 2013-11-06 华为技术有限公司 Method and device for treating fault
CN101505250B (en) * 2009-04-10 2011-08-24 杭州华三通信技术有限公司 Detection method, detection system and VPN for public network LSP
CN102025585A (en) * 2009-09-09 2011-04-20 中兴通讯股份有限公司 Method and device for protecting Ethernet tunnel
CN101777997A (en) * 2010-01-21 2010-07-14 中兴通讯股份有限公司 Method and system for switching flow of network link
CN101888339B (en) * 2010-07-19 2012-04-11 南京邮电大学 MPLS-TP-based looped network steering protection method
CN101977141B (en) * 2010-09-27 2012-05-23 南京邮电大学 MPLS-TP-based multicast protection method
CN102130829B (en) * 2010-12-28 2013-06-05 华为技术有限公司 Method and device for establishing label switch paths (LSP)
ES2400434B1 (en) * 2011-01-20 2014-04-29 Telefónica, S.A. PROCEDURE AND SYSTEM FOR THE SURVIVAL OF AN OPTICAL NETWORK AGAINST MULTIPLE FAILURES
CN102123097B (en) 2011-03-14 2015-05-20 杭州华三通信技术有限公司 Method and device for protecting router
CN102201985B (en) 2011-05-06 2014-02-05 杭州华三通信技术有限公司 Ring protection switching method adopting multi-protocol label switching transport profile (MPLS TP) and node
CN102185773B (en) * 2011-05-09 2013-08-21 杭州华三通信技术有限公司 Multi-protocol label switching transport profile ring protection switching method and node
CN102316032B (en) * 2011-09-05 2017-03-29 中兴通讯股份有限公司 A kind of method and the network switch of protection link exchange safety
JP2016001847A (en) * 2014-06-12 2016-01-07 富士通株式会社 Transmission device and transmission method

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020060985A1 (en) 2000-11-22 2002-05-23 Lee Jae Yong Method for high speed rerouting in multi protocol label switching network
WO2002065607A1 (en) 2001-02-12 2002-08-22 Maple Optical Systems, Inc. Multiple level fault protection in a communications network
KR20030001635A (en) 2001-06-25 2003-01-08 에스케이 텔레콤주식회사 Method for determining traffic paths for Protection Switching in MPLS based data telecommunication network
CN1394053A (en) 2001-06-27 2003-01-29 华为技术有限公司 Fast protecting switching method for multi-protocol label exchange
JP2003124978A (en) 2001-10-10 2003-04-25 Hitachi Ltd Failure notification method and relay device
US20030126287A1 (en) 2002-01-02 2003-07-03 Cisco Technology, Inc. Implicit shared bandwidth protection for fast reroute
US20030147346A1 (en) * 2002-02-01 2003-08-07 Nec Corporation Label switching router, label switching network and label switched path setting method
EP1422870A1 (en) 2002-10-24 2004-05-26 Tellabs Oy Method and system for detecting a connection fault
CN1501644A (en) 2002-11-19 2004-06-02 ��Ϊ�������޹�˾ Reachability detection method between IP network devices and its application in access backup of public dial-up network platform
US20040193724A1 (en) 2003-03-31 2004-09-30 Dziong Zbigniew M. Sharing restoration path bandwidth in mesh networks
US7106729B1 (en) * 2001-10-29 2006-09-12 Ciena Corporation Switching control mechanism based upon the logical partitioning of a switch element
US20060233137A1 (en) * 2000-02-25 2006-10-19 Cisco Technology, Inc. Wireless Router and Method for Processing Traffic in a Wireless Communications Network
US20070076720A1 (en) * 2004-09-30 2007-04-05 Huawei Technologies Co., Ltd. Method for handling fault between an egress label switching router and a data device connected therewith
US7269132B1 (en) * 2002-02-22 2007-09-11 Nortel Networks, Ltd. Method and apparatus for achieving transparent redundancy at a hierarchical boundary
US7336615B1 (en) * 2001-06-25 2008-02-26 Juniper Networks, Inc. Detecting data plane livelines in connections such as label-switched paths
US7345991B1 (en) * 2003-05-28 2008-03-18 Atrica Israel Ltd. Connection protection mechanism for dual homed access, aggregation and customer edge devices

Patent Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060233137A1 (en) * 2000-02-25 2006-10-19 Cisco Technology, Inc. Wireless Router and Method for Processing Traffic in a Wireless Communications Network
US20020060985A1 (en) 2000-11-22 2002-05-23 Lee Jae Yong Method for high speed rerouting in multi protocol label switching network
WO2002065607A1 (en) 2001-02-12 2002-08-22 Maple Optical Systems, Inc. Multiple level fault protection in a communications network
KR20030001635A (en) 2001-06-25 2003-01-08 에스케이 텔레콤주식회사 Method for determining traffic paths for Protection Switching in MPLS based data telecommunication network
US7336615B1 (en) * 2001-06-25 2008-02-26 Juniper Networks, Inc. Detecting data plane livelines in connections such as label-switched paths
CN1394053A (en) 2001-06-27 2003-01-29 华为技术有限公司 Fast protecting switching method for multi-protocol label exchange
JP2003124978A (en) 2001-10-10 2003-04-25 Hitachi Ltd Failure notification method and relay device
US7106729B1 (en) * 2001-10-29 2006-09-12 Ciena Corporation Switching control mechanism based upon the logical partitioning of a switch element
CN1466832A (en) 2002-01-02 2004-01-07 ƽ Implicit shared bandwidth protection for fast rerouting
WO2003060745A1 (en) 2002-01-02 2003-07-24 Cisco Technology, Inc. Implicit shared bandwidth protection for fast reroute
US20030126287A1 (en) 2002-01-02 2003-07-03 Cisco Technology, Inc. Implicit shared bandwidth protection for fast reroute
US20030147346A1 (en) * 2002-02-01 2003-08-07 Nec Corporation Label switching router, label switching network and label switched path setting method
US7269132B1 (en) * 2002-02-22 2007-09-11 Nortel Networks, Ltd. Method and apparatus for achieving transparent redundancy at a hierarchical boundary
EP1422870A1 (en) 2002-10-24 2004-05-26 Tellabs Oy Method and system for detecting a connection fault
CN1501644A (en) 2002-11-19 2004-06-02 ��Ϊ�������޹�˾ Reachability detection method between IP network devices and its application in access backup of public dial-up network platform
US20040193724A1 (en) 2003-03-31 2004-09-30 Dziong Zbigniew M. Sharing restoration path bandwidth in mesh networks
US7345991B1 (en) * 2003-05-28 2008-03-18 Atrica Israel Ltd. Connection protection mechanism for dual homed access, aggregation and customer edge devices
US20070076720A1 (en) * 2004-09-30 2007-04-05 Huawei Technologies Co., Ltd. Method for handling fault between an egress label switching router and a data device connected therewith

Non-Patent Citations (8)

* Cited by examiner, † Cited by third party
Title
"Protection switching for MPLS networks;" ITU-T Standard in Force (I), International Telecommunications Union, Geneva, CH, No. Y1720 9/3, Sep. 13, 2003 pp. 1-34 XP01740438.
Changcheng Huang, et al; "Building Reliable MPLS Networks Using a Path Protection Mechanism;" IEEE Communications Magazine, IEEE Service Center, Piscataway, US , vol. 40, No. 3, Mar. 2002 pp. 156-162 XP011092802.
Chinese Office Action, Application No. 200410080936.6, Dated Mar. 9, 2007, 15 pages.
International Telecommunication Union, "ITU-T Recommendation Y.1710; Requirements for Operation & Maintenance Functionality for MPLS Networks," ITU-T Y-Series Recommendations: Global Information Infrastructure and Internet Protocol Aspects, Nov. 2002, 12 pages.
International Telecommunication Union, "ITU-T Recommendation Y.1711; Operation & Maintenance Mechanism for MPLS Networks," ITU-T Y-Series Recommendations: Global Information Infrastructure, Internet Protocol Aspects and Next Generation Networks, Feb. 2004, 36 pages.
International Telecommunication Union, "ITU-T Recommendation Y.1720; Protection Switching for MPLS Networks," ITU-T Y-Series Recommendations: Global Information Infrastructure and Internet Protocol Aspects, Apr. 2003, 20 pages.
Mao, Yongua et al; "MPLS OAM Technology" Information Network, Jun. 30, 2003.
Neil Harrison, et al; "OAM Functionality for MPLS Networks;" IETF Standard-Working-Draft, Internet Engineering Task Force, IETF, CH, Feb. 2001 XP015014105.

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160112349A1 (en) * 2014-10-16 2016-04-21 Electronics And Telecommunications Research Institute Method for providing protection switching service in virtual tenant network and controller therefor
US9935900B2 (en) * 2014-10-16 2018-04-03 Electronics And Telecommunications Research Institute Method for providing protection switching service in virtual tenant network and controller therefor

Also Published As

Publication number Publication date
PT1793530E (en) 2012-08-02
CN1756184A (en) 2006-04-05
EP1793530A4 (en) 2008-01-02
WO2006034639A1 (en) 2006-04-06
EP1793530B1 (en) 2012-06-13
PL1793530T3 (en) 2012-10-31
CN100359860C (en) 2008-01-02
US20070242605A1 (en) 2007-10-18
ES2386900T3 (en) 2012-09-05
EP1793530A1 (en) 2007-06-06

Similar Documents

Publication Publication Date Title
US8248917B2 (en) Method and system for implementing protection switching in multi-protocol label switching network
EP1777897B1 (en) A method for implementing management and protection by dividing domain in the label switching network
EP2238721B1 (en) Gmpls based oam provisioning
EP2190150B1 (en) A method, device and system of multi-protocol label exchange traffic engineering flow capacity switch
CN101316225B (en) Fault detection method, communication system and label exchange router
CA2570333C (en) Method for implementing bidirectional protection switching in multiple protocol label switching network
US7948900B2 (en) Method and system for verifying connectivity of multi-segment pseudo-wires
US8521896B2 (en) Method and system for negotiating the bidirectional forwarding detection session discriminator of pseudo wire
CN101945049B (en) The method for building up of multiprotocol label switching system, node device and bidirectional tunnel
US8045452B2 (en) Method for handling fault between an egress label switching router and a data device connected therewith
US7801049B2 (en) Method, system and node for implementing subnetwork connection protection in multi-protocol label switching network
US20020110087A1 (en) Efficient setup of label-switched connections
WO2008047332A2 (en) A method and system for verifying connectivity of multi- segment pseudo-wires by tracing
EP1826961A1 (en) A method for creating the path for the return label in the multi-protocol label switching system
WO2006081731A1 (en) A protection switching method for multi-protocol label switching network
EP1786158B1 (en) Methods and systems for informing and negotiating the monitor ability of the label switching capability
EP1942609B1 (en) A system and method for protecting multicast service path
EP2129042B1 (en) A multicast network system, node and a method for detecting a fault of a multicast network link
WO2011020257A1 (en) Method and apparatus for notifying failure lsp information
EP1798912B1 (en) A method for transmitting control message in mpls ring network
Agarwal et al. Ingress failure recovery mechanisms in MPLS network

Legal Events

Date Code Title Description
AS Assignment

Owner name: HUAWEI TECHNOLOGIES CO., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LEI, WENYANG;REEL/FRAME:019480/0975

Effective date: 20070616

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载