Source: https://patents.google.com/patent/US8885459B2/en
Timestamp: 2019-09-19 15:57:42
Document Index: 386234342

Matched Legal Cases: ['Application No. 61', 'Application No. 201080003837', 'Application No. 201080003837', 'Application No. 10700352', 'Application No. 10700352', 'Application No. 10700352', 'Application No. 11746859', 'Application No. 13170910', 'Application No. 2011', 'Application No. 2011', 'Application No. 2012', 'Application No. 2012', 'Application No. 2011523222', 'Application No. 2011523222']

US8885459B2 - System and method for computing a backup ingress of a point-to-multipoint label switched path - Google Patents
US8885459B2
US8885459B2 US13/033,125 US201113033125A US8885459B2 US 8885459 B2 US8885459 B2 US 8885459B2 US 201113033125 A US201113033125 A US 201113033125A US 8885459 B2 US8885459 B2 US 8885459B2
backup ingress
US13/033,125
US20110211445A1 (en
2011-02-23 Application filed by FutureWei Technologies Inc filed Critical FutureWei Technologies Inc
2011-02-23 Assigned to FUTUREWEI TECHNOLOGIES, INC. reassignment FUTUREWEI TECHNOLOGIES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHEN, HUAIMO
2011-09-01 Publication of US20110211445A1 publication Critical patent/US20110211445A1/en
2014-11-11 Publication of US8885459B2 publication Critical patent/US8885459B2/en
Disclosed is an apparatus that includes a path computation element (PCE) configured to communicate with a path computation client (PCC) and compute a backup ingress node for a Point-to-Multipoint (P2MP) Label Switched Path (LSP) in a network associated with the PCC. The backup ingress node is coupled to an ingress node of the P2MP LSP and to a plurality of next-hop nodes of the ingress node of the P2MP LSP via a backup tree.
The present application claims the benefit of U.S. Provisional Patent Application No. 61/308,835 filed Feb. 26, 2010 by Huaimo Chen and entitled “System and Method for Computing A Backup Ingress of A P2MP LSP,” which is incorporated herein by reference as if reproduced in its entirety.
In one embodiment, the disclosure includes an apparatus. The apparatus includes a path computation element (PCE) configured to communicate with a path computation client (PCC) and compute a backup ingress node for a Point-to-Multipoint (P2MP) Label Switched Path (LSP) in a network associated with the PCC. The backup ingress node is coupled to an ingress node of the P2MP LSP and to a plurality of next-hop nodes of the ingress node of the P2MP LSP via a backup tree.
In another embodiment, the disclosure includes a network component. The network component includes a receiver, circuit logic, and a transmitter. The receiver is configured to receive a request message for computing a backup ingress node of a Point-to-Multipoint (P2MP) Label Switched Path (LSP) in a network. The circuit logic is configured to attempt computing a backup ingress node for the P2MP LSP based on the network's topology and a set of constraints in the request message. The transmitter is configured to send a reply message comprising the computed backup ingress node if the backup ingress node is computed successfully.
In a third aspect, the disclosure includes a method. The method includes exchanging capability information between a path computation element (PCE) and a path computation client (PCC) during a session establishment between the PCE and the PCC. The capability information are related to computing a backup ingress node for a Point-to-Multipoint (P2MP) Label Switched Path (LSP) in a network.
The Internet Engineering Task Force (IETF) request for comment (RFC) 4655 publication dated August 2006 entitled “A Path Computation Element-(PCE) Based Architecture”, which is incorporated herein by reference, describes components for computing P2P TE LSPs across multiple areas or Autonomous System (AS) domains. The components may comprise a PCE, which may comprise or may be coupled to one or more path computation servers and traffic engineering databases (TEDs), and one or more PCCs coupled to the PCE. A PCC may send a P2P TE LSP computation request to the PCE, which may use a TED to compute a path and respond to the PCC with the computed path. The TED may be constructed using TE information that may be exchanged using a network routing protocol. The communications between the PCE and the PCC for P2P LSP path computations may be based on a PCE communication protocol (PCEP).
An IETF RFC 4875 publication dated May 2007 entitled “Extensions to Resource Reservation Protocol—Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)”, which is incorporated herein by reference, describes a mechanism for setting up P2MP TE LSPs. A P2MP LSP may comprise a plurality of Source-to-Leaf (S2L) sub LSPs that may be configured between an ingress node or LSR and a plurality of egress nodes or LSRs. The S2L sub LSPs may be appropriately combined to one another by a plurality of branch nodes or LSRs using a RSVP to obtain a P2MP TE LSP. Additionally, an IETF RFC 6006 publication dated September 2010 entitled “Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths”, which is incorporated herein by reference, describes extensions to the PCEP for handling requests and responses for P2MP TE LSPs path computations.
However, the documents above do not include a mechanism to allow a PCC to send a request to a PCE for computing a backup ingress node for a P2MP LSP and to allow a PCE to compute the backup ingress node and reply to the PCC with a computation result for the backup ingress node. Disclosed herein is a system and method for computing a backup ingress node for a P2MP LSP, which may transport traffic across multiple areas or AS domains. The system and method may also allow the PCE and the PCC to exchange information related to the computed backup ingress node of the P2MP LSP.
FIG. 5 illustrates one embodiment of a RP object 500, which may be part of a request message transmitted from a PCC to a PCE or a part of a reply message transmitted from a PCE to a PCC. For instance, the RP object may indicate a backup ingress of a P2MP LSP related request message. The RP object 500 may comprise a reserved field 510, a flags field 520, and a request identification (ID) number 550. The flags field comprises flag 521, 523, 525, 527, 529, 531, 533, and 535. Additionally, the RP object 500 may optionally comprise one or more optional TLVs 560. The reserved field 510 may be reserved or may not be used. The reserved field 510 may have a length of about eight bits. The flags field 520 may comprise a backup ingress bit (I) flag 521, a fragmentation bit (F) flag 523, a P2MP bit (N) flag 525, an ERO compression bit (E) flag 527, a strict/loose bit (0) flag 529, a bi-directional bit (B) flag 531, a re-optimization (R) flag 533, and a plurality of priority bit (P) flags 535. The flags 520 may also comprise additional bits, which may be unassigned or reserved. For instance, the remaining bits in the flags field 520 may be set to about zero and ignored. The I flag 521 may be set, e.g., to about one, to indicate a backup ingress computation for a P2MP LSP. The I flag 521 may be set to indicate whether a request message or reply message is related to a backup ingress computation for a P2MP LSP.
Alternatively, a plurality of error values may be defined under an existing error type value, e.g., of about two, that indicates that a capability is not supported. The defined errors value may indicate errors associated with a backup ingress computation request. In one embodiment, an error value of about three may be used with an existing error type value of about two in the PCEP Error object 600. The error value of about three may indicate that the PCE received a backup ingress computation request and is not capable of computing the backup ingress. Alternatively, an error value of about four may be used with the existing error type value of about two to indicate that the PCE received a backup ingress computation request and is not able to satisfy the request due to some reason, such as insufficient memory. In some embodiments, an error value may be defined under an existing error type value, e.g., of about five, that indicates a policy violation. The defined error value may indicate an error associated with a backup ingress computation policy violation. For instance, an error value of about six may be used with an existing error type value of about five in the PCEP Error object 600 to indicate that the PCE received a backup ingress computation request that is not compliant with administrative privileges (e.g., “The PCE policy does not support backup ingress computation”).
receive a request message from a path computation client (PCC) that requests to compute a backup ingress node for an ingress node associated with a Point-to-Multipoint (P2MP) Label Switched Path (LSP);
compute the backup ingress node for the ingress node associated with the P2MP LSP using information within the request; and
transmit a reply message that indicates the backup ingress node has been computed,
wherein the backup ingress node is coupled to the ingress node of the P2MP LSP and to a plurality of next-hop nodes from the ingress node along the P2MP LSP,
wherein the request message comprises a plurality of constraints and a plurality of flags, and
wherein one of the flags is a backup ingress bit flag.
2. The apparatus of claim 1, wherein the backup ingress node and the ingress node are both coupled to an external node, wherein the backup node is configured to transport data received from the external node via a backup sub tree when the ingress node fails, wherein the backup sub tree merges with the P2MP LSP on at least one of the next hop-nodes, and wherein the sub tree does not extend across a network.
3. The apparatus of claim 1, wherein the PCE is further configured to obtain a list of candidate backup ingress nodes, wherein each of the candidate backup ingress nodes satisfies the plurality of constraints from an external node to one of the candidate backup ingress nodes, and wherein the PCE is not located along the P2MP LSP.
4. The apparatus of claim 3, wherein the one of the candidate backup ingress nodes is a node in the same network as the ingress node of the P2MP LSP.
5. The apparatus of claim 3, wherein the constraints comprise a hop limit, bandwidth and metric constraints on the path from the external node to the one of the backup ingress node.
6. The apparatus of claim 3, wherein the PCE is configured to receive the list of the candidate backup ingress nodes from a second PCE and select the backup ingress node from the list that satisfies the plurality of constraints.
7. The apparatus of claim 3, wherein the plurality of constraints comprise exclusive constraints, a hop limit, and bandwidth and metric constraints for a backup sub tree that has end points that extend from the backup ingress node to the next-hop nodes of the ingress node of the P2MP LSP.
8. The apparatus of claim 3, wherein one of the plurality of constraints is a hop limit constraint for the path between the backup ingress node and the ingress node of the P2MP LSP.
9. The apparatus of claim 1, wherein the reply message comprises the backup ingress node and a backup sub tree path, wherein the backup sub tree path extends from the backup ingress node to at least one of the next-hop nodes of the ingress node of the P2MP LSP.
10. The apparatus of claim 1, wherein the PCE is configured to exchange a capability information that indicates supporting one or more functions related to computing the backup ingress node for the ingress node associated with the P2MP LSP, and wherein the capability information is exchanged using a plurality of session establishment messages.
a receiver configured to receive a request message from a path computation client (PCC) to select a backup ingress node for a Point-to-Multipoint (P2MP) Label Switched Path (LSP) in a network to protect an ingress node of the P2MP LSP;
a circuit logic configured to select the backup ingress node for the P2MP LSP based on the network's topology and a set of constraints that are located in the request message; and
a transmitter configured to send a reply message comprising the computed backup ingress node when the backup ingress node is selected successfully,
wherein the backup ingress node is a root node of a backup sub tree,
wherein the request message comprises a plurality of flags,
wherein one of the flags is a backup ingress bit flag, and
wherein the backup sub tree extends from the backup ingress node to one or more next-hop nodes from the ingress node along the P2MP LSP.
12. The network component of claim 11, wherein the set of constraints comprise bandwidth limitation and information about an external node that transmits traffic to the ingress node of the P2MP LSP, and wherein the network component is not located along the P2MP LSP.
13. The network component of claim 11, wherein the transmitter is configured to send a reply message that indicates a reason for failure to select the backup ingress node when the backup ingress node is not selected successfully.
14. The network component of claim 13, wherein the reply message comprises a NO-PATH object that indicates a reason of failure to compute the backup ingress node, wherein the NO-PATH object comprises a nature of issue field, a flags field that comprises a capability (C) flag, a first optional type-length-value (TLV), and one or more second optional TLVs, and wherein the first optional TLV comprises a type field, a length field, and a second flags field that comprises a reachability (R) flag.
15. The network component of claim 14, wherein the R flag is set to indicate a reachability issue with one or more next-hops of the ingress node of the P2MP LSP from a candidate backup ingress node, and wherein the NO-PATH object comprises a plurality of unreachable Internet Protocol (IP) version four (IPv4) or IP version six (IPv6) next-hops TLVs that list IP addresses of the next-hops of the ingress node of the P2MP LSP that are not reachable from the candidate backup ingress node.
16. The network component of claim 11, wherein the reply message comprises a PCE Protocol (PCEP) Error object that indicates an error related to the backup ingress node computation, and wherein the PCEP Error object comprises a flags field, an error-type field, an error-value field, and one or more optional type-length-values (TLVs).
a receiver configured to receive a request message for computing a backup ingress node of a Point-to-Multipoint (P2MP) Label Switched Path (LSP) in a network to protect the ingress of the P2MP LSP, wherein the backup ingress node is an ingress node of a backup P2MP sub tree, and wherein the backup P2MP sub tree does not extend across the network;
a circuit logic configured to attempt computing the backup ingress node for the P2MP LSP based on the network's topology and a set of constraints in the request message; and
a transmitter configured to send a reply message comprising the computed backup ingress node if the backup ingress node is computed successfully,
wherein the request message, the reply message, or both comprise a request parameter (RP) object that comprises a reserved field, a plurality of flags, a request identification (ID) number, and one or more optional type-length-values (TLVs), and
wherein the flags comprise a backup ingress bit (I) flag, a fragmentation bit (F) flag, a P2MP bit (N) flag, an Explicit Route Object (ERO) compression bit (E) flag, a strict/loose bit (O) flag, a bi-directional bit (B) flag, a re-optimization (R) flag, and a plurality of priority bit (P) flags.
exchanging a capability information with a path computation client (PCC) during a session establishment that signals a path computation element (PCE) is capable to compute a backup ingress node;
receiving a request message for computing the backup ingress node for an ingress node along a Point-to-Multipoint (P2MP) Label Switched Path (LSP);
computing the backup ingress node; and
sending a reply message to the PCC in response to the request message for computing the backup ingress node,
wherein the reply message comprises the backup ingress node information,
wherein the backup ingress node is a root node of a backup path,
wherein the request message comprises a plurality of constraints and a plurality of flags,
wherein the backup path is a path from the backup ingress node to one or more next-hop nodes of the ingress node along the P2MP LSP.
19. The method of claim 18, wherein the capability information is exchanged using a PCE capability sub type-length-value (TLV) in a PCE Discovery (PCED) TLV, wherein the PCE capability sub TLV comprises a type field, a length field, and a value field that comprises a first flag and a second flag, and wherein the first flag is set to indicate that the PCE is capable of computing the backup ingress node for the P2MP LSP and the second flag is set to indicate that the PCE is capable of computing a backup ingress node for a Point-to-Point (P2P) LSP.
20. The method of claim 18, wherein the capability information is exchanged using a PCE capability TLV in an open message to discover the capability information, and wherein the PCE capability TLV comprises a type field, a length field, and a value field that indicates a capability to compute the backup ingress node for the ingress node along the P2MP LSP.
US13/033,125 2010-02-26 2011-02-23 System and method for computing a backup ingress of a point-to-multipoint label switched path Active 2032-03-07 US8885459B2 (en)
CN201180008368.7A CN102771096B (en) 2010-02-26 2011-02-28 The backup ingress point to multipoint system and a method for calculating the label switched path
JP2012554211A JP5596182B2 (en) 2010-02-26 2011-02-28 System and method for calculating a backup ingress point-to-multipoint label switch path
EP11746859.5A EP2540041B1 (en) 2010-02-26 2011-02-28 System and method for computing a backup ingress of a point-to-multipoint label switched path
ES11746859.5T ES2523574T3 (en) 2010-02-26 2011-02-28 System and method for calculating input route backup label switch point to multipoint
US14/516,909 US9172637B2 (en) 2010-02-26 2014-10-17 System and method for computing a backup ingress of a point-to-multipoint label switched path
US14/846,022 US9860161B2 (en) 2010-02-26 2015-09-04 System and method for computing a backup ingress of a point-to-multipoint label switched path
US14/516,909 Continuation US9172637B2 (en) 2010-02-26 2014-10-17 System and method for computing a backup ingress of a point-to-multipoint label switched path
US20110211445A1 US20110211445A1 (en) 2011-09-01
US8885459B2 true US8885459B2 (en) 2014-11-11
US13/033,125 Active 2032-03-07 US8885459B2 (en) 2010-02-26 2011-02-23 System and method for computing a backup ingress of a point-to-multipoint label switched path
US14/516,909 Active US9172637B2 (en) 2010-02-26 2014-10-17 System and method for computing a backup ingress of a point-to-multipoint label switched path
US14/846,022 Active US9860161B2 (en) 2010-02-26 2015-09-04 System and method for computing a backup ingress of a point-to-multipoint label switched path
CN106130901A (en) * 2016-06-03 2016-11-16 华为技术有限公司 Data transmission method, device and system
US10230618B2 (en) * 2013-06-26 2019-03-12 Huawei Technologies Co., Ltd. Path acquisition method, path computation element, path computation client and system
CN103503376B (en) 2011-12-29 2018-05-01 华为技术有限公司 The method of managing a cloud computing system, a cloud computing system and storage resources
US9219614B2 (en) 2012-06-14 2015-12-22 Futurewei Technologies, Inc. mRSVP-TE based fast reroute in detour (1:1) protection mode
EP2804352B1 (en) * 2012-11-28 2017-07-19 Huawei Technologies Co., Ltd. Method and apparatus for processing residual information
CN108243105A (en) * 2016-12-23 2018-07-03 中兴通讯股份有限公司 Path computation method and device, PCC, PCE and path computation system
US20030117952A1 (en) 2001-12-26 2003-06-26 Kyoko Ueno Method of transmitting data with redundant structure, and device for transmitting data by said method
US20070019954A1 (en) 2005-06-30 2007-01-25 Infinera Corporation Discovery Of An Adjacent Network Element Within A Network Data Plane
US20070019558A1 (en) 2005-07-19 2007-01-25 Jean-Philippe Vasseur Dynamic enforcement of MPLS-TE inter-domain policy and QoS
US20070047556A1 (en) 2005-08-29 2007-03-01 Alcatel Resiliency in minimum cost tree-based VPLS architecture
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
US20070091792A1 (en) 2005-10-21 2007-04-26 Alcatel Multiple endpoint paths for point-to-multipoint (P2MP) SPVC
US20070133406A1 (en) 2005-12-14 2007-06-14 Jean-Philippe Vasseur Technique for enabling traffic engineering on CE-CE paths across a provider network
US20080076720A1 (en) 2003-03-04 2008-03-27 Sancai Xie Personal care compositions having kinetin or zeatin
WO2008037917A1 (en) 2006-09-25 2008-04-03 France Telecom Routing method in a label switching network
CN101163105A (en) 2007-11-26 2008-04-16 华为技术有限公司 Method of obtaining path information and path computing node
WO2008043374A1 (en) 2006-10-09 2008-04-17 Telefonaktiebolaget Lm Ericsson (Publ) Resiliency schemes in communications networks
US20080205282A1 (en) 2005-11-02 2008-08-28 Huawei Technologies Co., Ltd. Method for protecting the service flow and a network device
WO2009054032A1 (en) 2007-10-25 2009-04-30 Fujitsu Limited Communication device in label switching network
US20100146149A1 (en) 2008-01-11 2010-06-10 Cisco Technology, Inc. Dynamic path computation element load balancing with backup path computation elements
US20100323000A1 (en) 2006-02-24 2010-12-23 Neopharm, Inc. Method and process for preparing cardiolipin
US20120044801A1 (en) 2006-02-03 2012-02-23 Cisco Technology, Inc. Technique for determining whether to reestablish fast rerouted primary tunnels based on backup tunnel path quality feedback
CN101228739A (en) 2005-07-19 2008-07-23 思科技术公司 Dynamic enforcement of MPLS-TE inter-domain policy and QoS
US20100008222A1 (en) 2006-09-25 2010-01-14 Jean-Louis Le Roux Routing Method in a Label Switching Network
US8331220B2 (en) 2007-03-28 2012-12-11 Fujitsu Limited Edge node redundant system
US20100189115A1 (en) 2007-10-25 2010-07-29 Fujitsu Limited Edge node redundant system in label switching network
US20100039939A1 (en) 2007-11-26 2010-02-18 Huawei Technologies Co., Ltd. Method and system for obtaining path information, path computation element
Aggarwal, R., Papadimitriou, D., and S. Yasukawa,"Extensions to Resource Reservation Protocol-Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)", RFC 4875, May 2007.
Aggarwal, R., Papadimitriou, D., and S. Yasukawa,"Extensions to Resource Reservation Protocol—Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)", RFC 4875, May 2007.
Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, Dec. 2001.
Awduche, D., et al., "Requirements for Traffic Engineering Over MPLS," RFC 2702, Sep. 1999, 29 pages.
Berger, Ed., L, et al., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions," RFC 3473, Jan. 2003, 43 pages.
Braden, Ed., R., et al., "Resource Reservation Protocol (RSVP)-Version 1 Functional Specification," RFC 2205, Sep. 1997, 112 pages.
Braden, Ed., R., et al., "Resource Reservation Protocol (RSVP)—Version 1 Functional Specification," RFC 2205, Sep. 1997, 112 pages.
Cao, et al. "Head Node Protection Extensions to RSVP-TE for LSP Tunnels," draft-cao-mpls-te-p2mp-head protection-01.txt, Nov. 17, 2007, 18 pages.
Cao, et al. "Head Node Protection Extensions to RSVP-TE for LSP Tunnels," draft-cao-mpls-te-p2mp-head-protection-01.txt, Nov. 17, 2007, 18 pages.
Chen, "Extensions to the Path Computation Element Communication Protocol (PCEP) for Backup Ingress of a Traffic Engineering Label Switched Path," draft-chen-pce-compute-backup-ingress-00.txt; Oct. 18 2010.
Chen, "Extensions to the Path Computation Element Communication Protocol (PCEP) for Backup Ingress of a Traffic Engineering Label Switched Path," draft-chen-pce-compute-backup-ingress-01.txt; Mar. 12, 2011.
Chen, H., "Extensions to Path Computation Element Communication Protocol (PCEP) for Backup Ingress of a Traffic Engineering Label Switched Path," draft-chen-pce-compute-backup-ingress-05.txt, Feb. 25, 2013, 14 pages.
Farrel, A., Vasseur, J., and J. Ash, "A Path Computation Element (PCE)-Based Architecture", RFC 4655, Aug. 2006.
Foreign Communication From a Counterpart Application, Chinese Application No. 201080003837.1, Chinese Office Action dated Feb. 27, 2013, 5 pages.
Foreign Communication From a Counterpart Application, Chinese Application No. 201080003837.1, Partial English Translation of Chinese Office Action dated Feb. 27, 2013, 7 pages.
Foreign Communication From a Counterpart Application, European Application No. 10700352.7, European Office Action dated Aug. 29, 2012, 3 pages.
Foreign Communication From a Counterpart Application, European Application No. 10700352.7, European Office Action dated Jun. 10, 2011, 6 pages.
Foreign Communication From a Counterpart Application, European Application No. 10700352.7, European Office Action dated Mar. 9, 2012, 5 pages.
Foreign Communication From a Counterpart Application, European Application No. 11746859.5, Extended European Search Report dated Feb. 8, 2013, 8 pages.
Foreign Communication From a Counterpart Application, European Application No. 13170910.7, Extended European Search Report dated Aug. 29, 2013, 9 pages.
Foreign Communication From a Counterpart Application, Japanese Application No. 2011-523222, Japanese Notice of Allowance dated Jan. 29, 2013, 3 pages.
Foreign Communication From a Counterpart Application, Japanese Application No. 2011-523222, Partial English Translation of Japanese Notice of Allowance dated Jan. 29, 2013, 1 page.
Foreign Communication From a Counterpart Application, Japanese Application No. 2012-554211, English Translation of Japanese Office Action dated Dec. 3, 2013, 2 pages.
Foreign Communication From a Counterpart Application, Japanese Application No. 2012-554211, Japanese Office Action dated Dec. 3, 2013, 2 pages.
Foreign Communication From a Counterpart Application, PCT Application PCT/US2010/020462, International Search Report dated Aug. 4, 2010, 7 pages.
Foreign Communication From a Counterpart Application, PCT Application PCT/US2010/020462, Written Opinion dated Aug. 4, 2010, 6 pages.
Foreign Communication From a Related Counterpart Application, Japanese Application No. 2011523222, Japanese Office Action dated Sep. 14, 2012, 3 pages.
Foreign Communication From a Related Counterpart Application, Japanese Application No. 2011523222, Partial Translation of Japanese Office Action dated Sep. 14, 2012, 2 pages.
Foreign Communication From a Related Counterpart Application, PCT Application PCT/CN2011/071358, International Search Report dated Jun. 9, 2011, 3 pages.
Foreign Communication From a Related Counterpart Application, PCT Application PCT/CN2011/071358, Written Opinion dated Jun. 9, 2011, 3 pages.
Foreign Communication From a Related Counterpart Application,International Search Report and Written Opinion, PCT/CN2011/071358 dated Feb. 8, 2013, 8 pages.
Le Roux, J.L., et al., "P2MP MPLS-TE Fast Reoute with P2MP Bypass Tunnels," draft-leroux-mpls-p2mp-te-bypass-01.txt, Mar. 2007, 12 pages.
Narten, T., "Assigning Experimental and Testing Numbers Considered Useful," RFC 3692, Jan. 2004, 8 pages.
Office Action dated Aug. 1, 2012, 39 pages, U.S. Appl. No. 12/683,968, filed Jan. 7, 2010.
Office Action dated Feb. 13, 2013, 40 pages, U.S. Appl. No. 12/683,968, filed Jan. 7, 2010.
Office Action dated Jun. 15, 2012, 6 pages, U.S. Appl. No. 12/683,968, filed Jan. 7, 2010.
Pan, P., Swallow, G., and A. Atlas, "Fast Reroute Extensions to RSVP-TE for LSP Tunnels", RFC 4090, May 2005.
Rosen, E., et al., "MPLS Label Stack Encoding," RFC 3032, Jan. 2001, 22 pages.
Rosen, E., et al., "Multiprotocol Label Switching Architecture," RFC 3031, Jan. 2001, 57 pages.
Vasseur et al, path computation element communication protocol dratft-ietf-pce-pcep-03, Oct. 2006. *
Vasseur, JP. And JL. Le Roux, "Path Computation Element (PCE) Communication Protocol (PCEP)", RFC 5440, Mar. 2009.
Yasukawa, Ed., S., "Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)," RFC 4461, 30 pages.
Yasukawa, S. and A. Farrel, "Path Computation Clients (PCC)-Path Computation Element (PCE) Requirements for Point-to-Multipoint MPLS-TE", RFC 5862, Jun. 2010.
Yasukawa, S. and A. Farrel, "Path Computation Clients (PCC)—Path Computation Element (PCE) Requirements for Point-to-Multipoint MPLS-TE", RFC 5862, Jun. 2010.
Zhao, (Ed.) et al., "Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths," draft-ietf-pce-pcep-p2mp-extensions-06.txt, Dec. 30, 2009.
Zhao, Q., Ed., et al., "Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths," draft-ietf-pce-pcep-p2mp-extensions-04.txt, Internet Draft, Aug. 18, 2009, 29 pages.
Zhao, Q., King, D., Verhaeghe, F., Takeda, T., Ali, Z., and J. Meuric, "Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths", RFC 6006, Sep. 2010.
EP2540041B1 (en) 2014-09-03
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CHEN, HUAIMO;REEL/FRAME:025851/0031