WO2012109912A1 - Procédé de reroutage et noeud de point de réparation locale - Google Patents

Procédé de reroutage et noeud de point de réparation locale Download PDF

Info

Publication number
WO2012109912A1
WO2012109912A1 PCT/CN2011/081175 CN2011081175W WO2012109912A1 WO 2012109912 A1 WO2012109912 A1 WO 2012109912A1 CN 2011081175 W CN2011081175 W CN 2011081175W WO 2012109912 A1 WO2012109912 A1 WO 2012109912A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
rerouting
downstream
path
tunnel
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.)
Ceased
Application number
PCT/CN2011/081175
Other languages
English (en)
Chinese (zh)
Inventor
付志涛
许浩
金昊
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.)
ZTE Corp
Original Assignee
ZTE Corp
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
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2012109912A1 publication Critical patent/WO2012109912A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities

Definitions

  • the present invention relates to the field of data network communication, and in particular, to a method for rerouting and a local repair point node.
  • Traffic Engineering-Fast Re-Route (TE-FRR) technology is a local protection technology that performs local repair when local links or nodes fail.
  • Two types of local protection, link protection and node protection, are defined in RFC4090.
  • Two special node types in the protection process are also defined: Point Local Repair (PLR) nodes and convergence points ( Merge Point, referred to as MP) node.
  • PLR Point Local Repair
  • MP Merge Point
  • Figure 1 shows the node protection topology of TE-FRR.
  • the topology diagram includes: nodes R1, R2, and R3 (R1 is a PLR node, and R3 is an MP node), and links are: L12, L23, and LI3, wherein the primary tunnel path (Primary lsp) is R1-R2-R3, the backup tunnel path (Backup lsp) is R1-R3.
  • the link L12 fails, the path is switched to L13 to form node protection.
  • Figure 2 shows the link protection topology of TE-FRR.
  • the topology map includes: nodes R1, R2, and R3 (R2 as a PLR node and R3 as an MP node), links: L12, L23, and L32, wherein the primary tunnel path (Primary lsp) is R1. -R2-R3, the backup tunnel path (Backup lsp) is R2-R3.
  • the MP node processes the protocol packets sent by the upstream, such as the PATH (Path) message and the PATH-TEAR (Path Removal) message sent from the backup tunnel.
  • the protocol packets of the original tunnel are not processed.
  • each of the other nodes is a potential PLR node.
  • PLR node As shown in Figure 3, a cross-node protection is formed, where Primary ls is R1-R2-R3-R4, Backup ls l is R1-R3 (via link L13) Backup lsp2 is R2-R4 (via link L24) .
  • Both nodes R1 and R2 act as PLR nodes, backup tunnel lspl protects R2 nodes, and backup tunnel Backup lsp2 protects R3 nodes.
  • node protection switching occurs as R2 of the PLR node at this time, and the upstream PATH signaling of the primary tunnel path reaches the R4 node (MP node) through L24.
  • R4 also refreshes RESV (Resource Reservation) signaling upstream through L24.
  • the R3 node is not refreshed.
  • the status of the primary tunnel path protocol of the R3 is aging. After the aging, if the link L12 also fails, the node protection switching occurs as the R1 of the PLR node.
  • the R3 becomes an MP node. However, the tunnel status information on the R3 is aged and cannot become an MP node. As a result, the switch is unsuccessful and the service of the tunnel is interrupted. Summary of the invention
  • the technical problem to be solved by the present invention is to provide a rerouting method and a local repair point node, so as to improve the protection relationship of the cross node protection and ensure continuous two-stage link failure, and the handover protection can take effect.
  • the present invention provides a method for rerouting, including: after receiving a resource reservation (RESV) message, the local repair point node determines a preset backup according to the information of the downstream node carried in the RESV message. If the tunnel destination node does not satisfy the rerouting condition, the downstream node information is searched for the downstream node that meets the rerouting condition, and if the tunnel path between the found downstream node and the local node does not coincide with the primary tunnel path, Then, the tunnel path between the downstream node and the local node is selected to form a rerouting relationship with the primary tunnel path.
  • the foregoing method further has the following features: before the step of determining, by the local repair point node, that the preset backup tunnel destination node does not satisfy the rerouting condition, the method further includes:
  • the local repair point node determines that the downstream path is switched.
  • the foregoing method further has the following features: after the step of determining, by the local repair point node, that the preset backup tunnel destination node does not satisfy the rerouting condition, the method further includes:
  • the local repair point node releases the original rerouting relationship.
  • the foregoing method further has the following features: the rerouting condition is:
  • the downstream node is the next hop router or the next next hop router of the local repair point node.
  • the foregoing method further has the following features: the downstream node information carried by the RESV message The information is achieved by:
  • the RESV message carries record routing object information, and the record routing object information includes at least interface information of the downstream node.
  • the present invention further provides a local repair point node, including: a first determining module, configured to: after receiving a resource reservation (RESV) message, determine a preset according to the downstream node information carried by the RESV message Whether the backup tunnel destination node meets the rerouting condition;
  • a first determining module configured to: after receiving a resource reservation (RESV) message, determine a preset according to the downstream node information carried by the RESV message Whether the backup tunnel destination node meets the rerouting condition;
  • RESV resource reservation
  • a locating module configured to: after the first determining module determines that the rerouting condition is not met, search for, from the downstream node information, a downstream node that meets a rerouting condition;
  • a second judging module configured to determine, when the search module finds a downstream node that satisfies the rerouting condition, whether the tunnel path between the found downstream node and the local node is coincident with the main tunnel path;
  • the selection module is configured to select a tunnel path between the downstream node and the local node to form a rerouting relationship with the primary tunnel path if the second determination module determines that the second determination module does not overlap.
  • the foregoing local repair point node further has the following features:
  • the third determining module is configured to: after receiving the RESV message, determine, according to the information of the downstream node that is carried by the RESV message, whether the downstream path is switched;
  • the first determining module determines whether the preset backup tunnel destination node satisfies the rerouting condition if the third determining module determines that the downstream path is switched.
  • the foregoing local repair point node further has the following features:
  • the local repair point node further has the following features:
  • the rerouting condition is: the downstream node is a next hop router or a next next hop router of the local repair point node.
  • the local repair point node has the following features:
  • the downstream node information carried by the RESV message is implemented in the following manner:
  • the RESV message carries record routing object information, and the record routing object information is at least Includes interface information for downstream nodes.
  • the above-mentioned method of rerouting and the local repair point node can improve the protection relationship of the cross-node protection, and can avoid the failure of the adjacent two links, causing the loss of the data service caused by the tunnel protection failure, and ensuring continuous If the two links fail, the switch protection can take effect.
  • Figure 1 is a topology diagram of TE-FRR node protection
  • Figure 2 is a topology diagram of TE-FRR link protection
  • Figure 3 is a topology diagram of TE-FRR cross node protection
  • FIG. 4 is a flowchart of a method for rerouting according to an embodiment of the present invention.
  • FIG. 5 is a topological diagram of TE-FRR cross node protection applied in an embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for rerouting according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a PLR node according to an embodiment of the present invention.
  • the embodiment of the present invention provides a rerouting method, as shown in FIG. , including the following steps:
  • the PLR node After receiving the RESV message, the PLR node determines, according to the downstream node information carried in the RESV message, that the preset backup tunnel destination node does not satisfy the rerouting condition, and searches for the rerouting from the downstream node information.
  • the downstream node of the condition
  • the PLR node determines that the discovered tunnel path between the downstream node and the local node does not coincide with the primary tunnel path, the tunnel path and the primary tunnel path shape between the downstream node and the local node are selected. Heavy routing relationship.
  • the rerouting condition is: the downstream node is a next hop router or a next hop router of the local repair point node.
  • FIG. 5 is a topological diagram of TE-FRR cross-node protection according to an embodiment of the present invention.
  • the primary tunnel has an FRR attribute
  • the RRO Record Route Object
  • the routing object information where the RRO information includes: interface information of the downstream node, Router1D (route identifier) information, and label information, where the interface information of the downstream node is necessarily carried.
  • the PLR node can check whether the preset backup tunnel destination node meets the NHOP (Next-hop Router, next hop router-and PLR one-hop router) or ⁇ ⁇ by the RRO information carried in the RESV message (Next- Next-hop Router, the relationship between the next router and the router with two hops from the PLR. If it is not satisfied, the original FRR relationship is removed, and other downstream nodes that satisfy the NHOP or N HOP relationship are selected to re-form the new FRR relationship. , so that the protection switch can take effect.
  • NHOP Next-hop Router, next hop router-and PLR one-hop router
  • RRO information carried in the RESV message Next- Next-hop Router, the relationship between the next router and the router with two hops from the PLR. If it is not satisfied, the original FRR relationship is removed, and other downstream nodes that satisfy the NHOP or N HOP relationship are selected to re-form the new FRR relationship. , so that the protection switch can take effect.
  • the sub-objects carried in the RRO in the RESV message are: the fei4/l interface address of R4 and the RouterlD address of R4 ( Optional), the inbound label of the primary tunnel path on R4, the fei3/2 interface address of R3, the RouterlD address of R3 (optional), the incoming label of the primary tunnel path on R3, the fei2/l interface address of R2, R2 RouterlD address (optional), the inbound label of the primary tunnel path on R2.
  • R1 determines that the preset backup tunnel destination R3 forms an N HOP relationship with R1, and determines that Backup lspl can form a node protection relationship with the primary tunnel path, that is, form an FRR relationship.
  • the sub-objects carried in the RESV message RRO of the R2 node are: fei4/l interface address of R4 , R4's RouterlD address (optional), and the primary tunnel path's inbound label on R4.
  • the RRO sub-objects carried are: fei4/l interface address of R4, RouterlD address of R4 (optional), incoming label of R2 on the primary tunnel path, fei2/l interface address of R2, R2 RouterlD address (optional), the inbound label of the primary tunnel path on R2.
  • R1 finds that the backup tunnel destination R3 is not in the RRO information. Therefore, it is determined that the destinations R3 and R1 of the backup tunnel do not satisfy the NHOP or N HOP relationship, and thus the corresponding FRR relationship is released.
  • R1 finds that R4 and R1 are NNHOP relations from the new RESV message, and the tunnel between R1 and R4 and the primary tunnel path satisfy the non-coincident condition.
  • Backup lsp3 can form a node protection relationship with the primary tunnel path, so Backup lsp3 and The main tunnel path forms a new FRR relationship.
  • link L12 fails, R1 switches, and the status of the primary tunnel path on R2 and R3 is aged and deleted.
  • the signaling of the primary tunnel is forwarded between L14.
  • the tunnel is not interrupted, ensuring service traffic.
  • Step 101 R1 receives the RESV message
  • Step 102 R1 determines whether the current primary tunnel path has an FRR relationship, if yes, then proceeds to step 103; otherwise, proceeds to step 107;
  • each node has state information.
  • Each tunnel forms an FRR relationship on a certain node, and it has a status flag in the status block.
  • Step 103 R1 determines whether the downstream path is switched according to the received RESV message, if yes, go to step 105; otherwise, go to step 104;
  • Step 104 Without processing, the old FRR relationship can be protected
  • Step 105 R1 determines whether the destination R3 and R1 of the preset backup tunnel meet the NHOP or NNHOP relationship. If yes, the process proceeds to step 104, and no processing is performed; otherwise, the process proceeds to step 106;
  • Step 106 the original FRR relationship is removed, and there is no FRR relationship with the main tunnel path in R1, and the process proceeds to step 102;
  • Step 107 R1 finds from the information carried in the RESV message whether there is a node that has a relationship with R1 that satisfies the NHOP or NNHOP relationship, and if yes, proceeds to step 108; otherwise, proceeds to step 109;
  • Step 108 R1 determines whether the tunnel between the node and the node searched in step 107 is related to the primary tunnel. If the paths are coincident, the tunnel between the node and the searched node is selected as the backup tunnel, and the FRR relationship is formed with the primary tunnel path; if they are coincident, the process proceeds to step 109;
  • Step 109 Cannot form protection and end.
  • the embodiment also provides a PLR node.
  • the PLR node in this embodiment includes: a first determining module, a searching module, a second determining module, and a selecting module, where
  • the first determining module is configured to: after receiving the RESV message, determine, according to the downstream node information carried in the RESV message, whether the preset backup tunnel destination node satisfies the rerouting condition;
  • a locating module configured to: after the first determining module determines that the rerouting condition is not met, search for, from the downstream node information, a downstream node that meets a rerouting condition;
  • a second judging module configured to determine, when the search module finds a downstream node that satisfies the rerouting condition, whether the tunnel path between the found downstream node and the local node is coincident with the main tunnel path;
  • the selection module is configured to select a tunnel path between the downstream node and the local node to form a rerouting relationship with the primary tunnel path if the second determination module determines that the second determination module does not overlap.
  • the PLR node may further include: a third determining module, configured to determine, according to the downstream node information carried in the RESV message, whether the downstream path is switched after receiving the RESV message.
  • the first determining module determines whether the preset backup tunnel destination node satisfies the rerouting condition if the third determining module determines that the downstream path is switched.
  • the PLR node may further include: a releasing module, configured to: after the first determining module determines that the preset backup tunnel destination node does not satisfy the rerouting condition, cancel the original Rerouting relationship.
  • the above technical solution provides a rerouting method and a local repair point node to improve the protection relationship of the cross node protection, ensure continuous two-stage link failure, and the switching protection can take effect, and the adjacent two links can be avoided.
  • the failure of the tunnel protection caused by the failure of the tunnel protection resulted in the loss of data services.

Landscapes

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

Abstract

L'invention concerne un procédé de reroutage et un noeud de point de réparation locale (PLR). Ce procédé consiste : lorsque le noeud PLR reçoit un message de réservation de ressources (RESV), si, en fonction d'informations de noeud aval jointes au message RESV, un noeud de destination tunnel de secours préconfiguré est estimé comme ne répondant pas à une exigence de reroutage, à rechercher dans les informations de noeud aval un noeud aval répondant à l'exigence de reroutage ; si un chemin à commutation d'étiquettes (LSP) ente le noeud aval trouvé et le noeud PLR est estimé comme ne coïncidant pas avec un LSP primaire, à sélectionner le LSP entre le noeud aval et le noeud PLR et le LSP primaire pour créer une relation de reroutage. Le procédé et le noeud PLR selon l'invention améliorent la relation de protection inter-noeuds et garantit que la protection de commutation entre en vigueur lors d'une défaillance de deux parties consécutives de la liaison.
PCT/CN2011/081175 2011-02-17 2011-10-24 Procédé de reroutage et noeud de point de réparation locale Ceased WO2012109912A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110039874.4 2011-02-17
CN201110039874.4A CN102158397B (zh) 2011-02-17 2011-02-17 一种重路由的方法和本地修复点节点

Publications (1)

Publication Number Publication Date
WO2012109912A1 true WO2012109912A1 (fr) 2012-08-23

Family

ID=44439594

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/081175 Ceased WO2012109912A1 (fr) 2011-02-17 2011-10-24 Procédé de reroutage et noeud de point de réparation locale

Country Status (2)

Country Link
CN (1) CN102158397B (fr)
WO (1) WO2012109912A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015149358A1 (fr) * 2014-04-04 2015-10-08 Telefonaktiebolaget L M Ericsson (Publ) Appareil et procede pour l'etablissement de chemin de reparation

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102158397B (zh) * 2011-02-17 2016-06-29 中兴通讯股份有限公司 一种重路由的方法和本地修复点节点
CN102281200B (zh) * 2011-08-24 2014-03-12 华为技术有限公司 选取当前备份路由的方法和路由器
CN104702501B (zh) * 2013-12-05 2019-02-15 中兴通讯股份有限公司 一种提高te frr保护可靠性的方法及装置
CN104168192A (zh) * 2014-08-08 2014-11-26 北京邮电大学 一种故障网络中的重路由方法和装置
CN107438026A (zh) * 2016-05-27 2017-12-05 任子行网络技术股份有限公司 域间路由系统的失效恢复方法和装置
CN107786385B (zh) * 2016-08-31 2020-10-09 中国电信股份有限公司 设备标签交换路径 lsp 隧道重路由能力检测方法和装置
US10476811B2 (en) * 2017-03-10 2019-11-12 Juniper Networks, Inc Apparatus, system, and method for providing node protection across label-switched paths that share labels
CN109510768B (zh) * 2017-09-14 2021-02-12 华为技术有限公司 链路状态通告lsa发送方法、装置和系统
CN110086712B (zh) * 2019-05-13 2021-04-23 何梓菁 一种基于sr-te隧道的链路保护方法和本地修复节点
CN110336743B (zh) * 2019-06-27 2021-12-14 烽火通信科技股份有限公司 一种保护隧道的合并方法及系统
CN110177044B (zh) * 2019-06-27 2021-08-24 烽火通信科技股份有限公司 一种保护隧道的创建方法及系统
CN114268579B (zh) * 2021-12-20 2023-03-24 烽火通信科技股份有限公司 一种对隧道进行快速重路由的方法、装置及计算机存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070008882A1 (en) * 2005-07-06 2007-01-11 Oran David R Method and apparatus for network-based admission control using path-coupled quality of service signaling
CN101431466A (zh) * 2007-11-09 2009-05-13 华为技术有限公司 快速重路由方法及标签交换路由器
CN101753342A (zh) * 2008-12-02 2010-06-23 华为技术有限公司 一种业务保护方法、节点和系统
CN102158397A (zh) * 2011-02-17 2011-08-17 中兴通讯股份有限公司 一种重路由的方法和本地修复点节点

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7782762B2 (en) * 2007-09-21 2010-08-24 Alcatel Lucent RSVP-TE enhancement for MPLS-FRR bandwidth optimization

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070008882A1 (en) * 2005-07-06 2007-01-11 Oran David R Method and apparatus for network-based admission control using path-coupled quality of service signaling
CN101431466A (zh) * 2007-11-09 2009-05-13 华为技术有限公司 快速重路由方法及标签交换路由器
CN101753342A (zh) * 2008-12-02 2010-06-23 华为技术有限公司 一种业务保护方法、节点和系统
CN102158397A (zh) * 2011-02-17 2011-08-17 中兴通讯股份有限公司 一种重路由的方法和本地修复点节点

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015149358A1 (fr) * 2014-04-04 2015-10-08 Telefonaktiebolaget L M Ericsson (Publ) Appareil et procede pour l'etablissement de chemin de reparation
US10075367B2 (en) 2014-04-04 2018-09-11 Telefonaktiebolaget Lm Ericsson (Publ) Apparatus and method for establishing a repair path
US10326692B2 (en) 2014-04-04 2019-06-18 Telefonaktiebolaget Lm Ericsson (Publ) Apparatus and method for establishing a repair path

Also Published As

Publication number Publication date
CN102158397B (zh) 2016-06-29
CN102158397A (zh) 2011-08-17

Similar Documents

Publication Publication Date Title
WO2012109912A1 (fr) Procédé de reroutage et noeud de point de réparation locale
US9350639B2 (en) Forwarding data in a data communications network
CN103368843B (zh) 受保护标签交换路径快速重路由的oam标签交换路径
KR100693052B1 (ko) Ｍｐｌｓ 멀티캐스트의 고속 재경로 설정 장치 및 방법
US7697417B2 (en) Methods and devices for re-routing MPLS traffic
EP2071768B1 (fr) Procédés de mise en oeuvre de réacheminement rapide multidiffusion et noeud
CN100518135C (zh) 一种多协议标签交换网络中重新路由的方法
CN104426763B (zh) 隧道切换方法、装置及交换机
CN102035681B (zh) 虚拟专用网络的链路保护方法和系统
JP5420547B2 (ja) Ｍｐｌｓ−ｆｒｒ帯域幅最適化のためのｒｓｖｐ−ｔｅ強化
CN101317405B (zh) 标签交换路径保护方法及装置
CN111698152A (zh) 一种故障保护方法、节点及存储介质
CN102315967B (zh) 一种组播标签交换路径的中间节点保护方法及装置
WO2012037820A1 (fr) Système de commutation multiprotocole par étiquette, dispositif de noeud et procédé pour établir un tunnel bidirectionnel
US11546252B2 (en) Fast flooding topology protection
CN105939273A (zh) 路由器方法、路由器以及路由器系统
CN100527683C (zh) 故障保护方法和系统
WO2008064612A1 (fr) Procédé, dispositif et système permettant d'effectuer un reroutage rapide dans un réseau mpls
US20040125745A9 (en) Two-stage reconnect system and method
CN105991388A (zh) 路由收敛方法、装置及虚拟专用网vpn系统
CN102790713A (zh) 一种双向路径的快速重路由保护方法及系统
WO2011147298A1 (fr) Procédé et appareil de réinitialisation de routes de réseau privé virtuel de couche 3
CN104283813B (zh) 一种处理rsvp-te信令的方法及系统
WO2016101492A1 (fr) Procédé et dispositif de réglage pour une table de transfert de service
CN109729006B (zh) 一种报文处理方法和装置、计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11858544

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11858544

Country of ref document: EP

Kind code of ref document: A1