WO2016134582A1 - 一种实现rsvp-te协议报文处理的方法及装置 - Google Patents

一种实现rsvp-te协议报文处理的方法及装置 Download PDF

Info

Publication number
WO2016134582A1
WO2016134582A1 PCT/CN2015/084972 CN2015084972W WO2016134582A1 WO 2016134582 A1 WO2016134582 A1 WO 2016134582A1 CN 2015084972 W CN2015084972 W CN 2015084972W WO 2016134582 A1 WO2016134582 A1 WO 2016134582A1
Authority
WO
WIPO (PCT)
Prior art keywords
path message
lsp
path
recovery
party
Prior art date
Application number
PCT/CN2015/084972
Other languages
English (en)
French (fr)
Inventor
付志涛
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016134582A1 publication Critical patent/WO2016134582A1/zh

Links

Images

Definitions

  • This document relates to data network communication technology, and in particular to a method and device for implementing resource engineering resource reservation protocol (RSVP-TE) protocol message processing.
  • RSVP-TE resource engineering resource reservation protocol
  • RSVP-TE Resource Reservation Protocol-Traffic Engineer
  • MPLS Multi-Protocol Label Switching
  • GR Graceful Restart
  • NSF Non-Stop Forwarding
  • FIG. 1 is a schematic diagram of a network structure of an elegantly restarted network. As shown in Figure 1, after detecting that an elegant restart occurs on a neighboring node, it is detected that the graceful restarting node needs to send a recovery packet to the restarting party.
  • the node of the text is called the auxiliary side; in Figure 1, if the node 2 (R2) gracefully restarts, both node 1 (R1) and node 3 (R3) are called the auxiliary side of R2.
  • the restarter When the auxiliary party helps the restarter to resume the control plane, it needs to send a recovery message to the restarter.
  • the restarter receives the recovery packet sent by the upstream device for recovery, the upstream sends a PATH message (here, the PATH message is a message type, which can be understood as the path) and carries the recovery.
  • the tag object after receiving the recovery message, the restarter determines that the message is a recovery message by parsing the recovery tag in the PATH message.
  • RSVP-TE is a soft state protocol
  • the neighbor nodes need to periodically send PATH messages and RESV messages (here, the RESV message is a proprietary message type, which can be understood as a reserved message) to be refreshed to maintain its Protocol status.
  • the refreshed PATH message sent periodically does not carry the recovery tag object.
  • FIG. 2 is a schematic diagram of the processing of the graceful restart before and after the related art; as shown in FIG. 2, it is assumed that the entry label entry corresponding to the node R2 before the graceful restart is (200, 3), that is, the incoming label is 200, and the outgoing label is 3.
  • R2 gracefully restarts.
  • the assistant R1 detects R2 restart at time T2 and starts sending the PATH message carrying the recovery label.
  • R1 periodically sends a PATH message to R2 according to the setting.
  • the PATH message at this time does not carry the recovery label. Therefore, the restarter receives the PATH without the recovery label.
  • the message is considered to be a PATH message of a newly created label switching path (LSP), so that a new reservation and a new inbound label application are possible, and the inbound label to be restored is 200 and the label is 3 is likely to be inconsistent. Causes recovery to fail.
  • LSP label switching path
  • the PATH message carries the recovery label to determine whether the packet is a recovery packet.
  • the packet sent between T1 and T2 cannot accurately determine the nature of the packet, and the recovery process cannot be accurately processed. .
  • the embodiment of the invention provides a method and a device for processing an RSVP-TE protocol packet, which can correctly determine a recovery message and perform an accurate recovery process.
  • An embodiment of the present invention provides a method for processing an RSVP-TE protocol packet, including:
  • the restarting party saves the label switching path LSP information of the path PATH message before gracefully restarting the GR;
  • the restarter When the restarter receives the PATH message from the secondary party without carrying the recovery label object, it determines whether the recovery process is performed according to whether the LSP information of the received PATH message is in the saved LSP information.
  • determining whether to perform the recovery process processing includes:
  • the PATH is discarded. After waiting for the auxiliary party to detect that the restarter restarts, the recovery process is performed on the regenerated PATH message carrying the recovery tag object;
  • the method further includes: the restarting party directly performs the recovery process.
  • the embodiment of the present invention further provides an apparatus for processing an RSVP-TE protocol packet, including: a saving unit and a first processing unit;
  • the saving unit is configured to save LSP information of a PATH message before the GR;
  • the first processing unit is configured to determine whether to perform recovery process processing according to whether the LSP information of the received PATH message is in the saved LSP information, when the PATH message from the secondary party does not carry the recovery label object.
  • the first processing unit is configured to
  • the PATH message is discarded, and after the auxiliary party detects that the restarting party restarts, the recovery process is performed on the regenerated PATH message carrying the recovery label object;
  • the apparatus further includes a second processing unit configured to perform a recovery process process when receiving the PATH message sent by the auxiliary party and the PATH message carrying the recovery tag object.
  • the embodiment of the invention further provides a computer readable storage medium storing program instructions, which can be implemented when the program instructions are executed.
  • the technical solution of the embodiment of the present application includes: the restarting party saves the LSP information of the PATH message before the GR; when the restarting party receives the PATH message from the auxiliary party, does not carry the recovery label object, according to the received PATH message. Whether the LSP information is in the saved LSP information determines whether the recovery process is performed.
  • the LSP information of the PATH message before the GR is saved, and it is determined whether the recovery process is performed, and whether the PATH message before the graceful restart is a recovery message is accurately determined, and the correct processing of the recovery process is implemented.
  • Figure 1 is a schematic diagram of the structure of an elegantly restarted network
  • FIG. 3 is a flowchart of a method for implementing RSVP-TE protocol packet processing according to an embodiment of the present invention
  • FIG. 4 is a structural block diagram of an apparatus for implementing RSVP-TE protocol packet processing according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for processing an RSVP-TE protocol packet according to an embodiment of the present invention. As shown in FIG. 3, the method includes:
  • Step 300 The restarter saves the LSP information of the PATH message before the GR.
  • the LSP information includes information such as an LSP key value, an inbound label, an inbound interface, an outgoing label, and an outgoing interface.
  • Step 301 When the received PATH message does not carry the recovery label object, determine whether the recovery process is performed according to whether the LSP information of the received PATH message is in the saved LSP information.
  • determining whether to perform the recovery process processing includes:
  • the PATH message is discarded, and after the auxiliary party detects that the restarting party restarts, the recovery process is performed on the regenerated PATH message carrying the recovery label object;
  • the foregoing method further includes: performing the recovery process directly.
  • FIG. 4 is a structural block diagram of an apparatus for processing an RSVP-TE protocol packet according to an embodiment of the present invention. As shown in FIG. 4, the method includes: a saving unit 401 and a first processing unit 402;
  • the saving unit 401 is configured to save the LSP information of the PATH message before the GR;
  • the first processing unit 402 is configured to determine whether to perform the recovery process according to whether the LSP information of the received PATH message is in the saved LSP information, when the PATH message from the secondary party does not carry the recovery label object.
  • the first processing unit 402 is configured to:
  • the PATH message is discarded, and after the auxiliary party detects that the restarting party restarts, the recovery process is performed on the regenerated PATH message carrying the recovery label object;
  • the foregoing apparatus further includes a second processing unit 403 configured to perform a recovery process process when receiving the PATH message sent by the auxiliary party and the PATH message carrying the recovery tag object.
  • a second processing unit 403 configured to perform a recovery process process when receiving the PATH message sent by the auxiliary party and the PATH message carrying the recovery tag object.
  • R1 When the secondary party R1 detects that the restarting party R2 is restarted through the hello packet, there is a path 1 between R1 and R2. R1 sends a PATH message to R2, and the PATH message carries the recovery label object.
  • the restarting party receives the packet of the PATH message sent by the auxiliary party, and determines that the PATH message has a recovery label object, and determines that the PATH message is a recovery packet, and performs a recovery process.
  • the secondary party R1 detects that the restarter R2 has been restarted. (It is generally considered that the restarter may have an graceful restart after receiving the hello packet from the peer for several cycles.) Since RSVP is a soft state protocol, it needs to be maintained by refreshing. Therefore, when the secondary party R1 does not detect that the restarting party R2 restarts, R1 will still send to R2. The path PATH is refreshed and the PATH message is not carried.
  • the restart method R2 After receiving the PATH packet that does not carry the recovery label object, the restart method R2 can find the LSP information of the path 1 in the LSP information saved before the R2 graceful restart because the recovery label is not carried. Therefore, the packet is considered to be an LSP that needs to be restored. However, since R1 has not detected the R2 restart, the packet does not carry the recovery label object. The packet is temporarily discarded. After R1 detects that R2 is restarted, it will continue to send the PATH message carrying the recovery label.
  • the restart method R2 receives the PATH message that the path 2 does not carry the recovery label after the restart, and the information of the path 2 cannot be found by querying the previously saved LSP information. Then, it is considered to be a newly created LSP, and the PATH information is processed according to the newly created LSP.
  • the LSP information of the PATH message before the GR is saved, and it is determined whether the recovery process is performed, and whether the PATH message before the graceful restart is a recovery message is accurately determined, and the correct processing of the recovery process is implemented.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种实现流量工程的资源预留协议(RSVP-TE)协议报文处理的方法及装置，包括：重启方保存优雅重启(GR)之前的路径(PATH)消息的标签交换路径(LSP)信息；当重启方接收到来自辅助方的PATH消息不携带恢复标签对象时，根据接收到的PATH消息的LSP信息是否在已保存的LSP信息中，确定是否进行恢复流程处理。

Description

一种实现RSVP-TE协议报文处理的方法及装置 技术领域
本文涉及数据网络通信技术，尤指一种实现流量工程的资源预留协议(RSVP-TE)协议报文处理的方法及装置。
背景技术
基于流量工程的资源预留协议(RSVP-TE，Resource Reservation Protocol-Traffic Engineer)是一种基于多协议标签交换(MPLS)的流量工程技术。通过信息发布、路径计算、信令交互和流量转发四个部件实现业务流量在TE隧道中的转发。
基于RSVP-TE的优雅重启(GR，Graceful Restart)提供了一种业务流量的不间断转发(NSF，Non-Stop Forwarding)机制，在网络中节点的控制面发生故障时，可以通过该节点的邻居节点在优雅重启时发送的恢复控制面信息，使优雅重启涉及的转发信息在控制面的恢复阶段得到保持，确保重启后，与转发信息相关的流量的正常转发。
GR技术需要基于hello检测，检测的目的之一就是需要感知邻居节点发生了优雅重启，在RFC3209，RFC3473，RFC5063分别介绍了hello的扩展和使用规则。图1是优雅重启的网络组成结构示意图，如图1所示，在检测到邻居节点发生了优雅重启之后，检测到优雅重启的节点需要为重启方发送恢复报文，优雅重启时，发送恢复报文的节点被称为辅助方；图1中，如果节点2(R2)发生优雅重启，那么节点1(R1)和节点3(R3)都叫做R2的辅助方。
辅助方在帮助重启方恢复控制面时，需要向重启方发送恢复报文。对于RSVP-TE协议来说，在重启方作为下游接收到上游发送的恢复报文进行恢复时，上游发送PATH消息(这里，PATH消息是一种消息类型，可以理解为路径的意思)会携带恢复标签对象；重启方接收到恢复报文之后，通过解析到PATH消息中的恢复标签确定该报文是恢复报文。
由于RSVP-TE是一个软状态协议，邻居节点间需要周期性的发送PATH消息和RESV消息(这里，RESV消息是一种专有的消息类型，可以理解为预留消息)进行刷新，以维持其协议状态。周期性发送的刷新的PATH消息不携带恢复标签对象。
图2是相关技术中优雅重启前后处理示意图；如图2所示，假设节点R2在优雅重启前对应的入标签表项为(200，3)，即入标签为200，出标签为3。在T1时刻，R2发生优雅重启，辅助方R1在T2时刻检测到R2重启，开始发送携带恢复标签的PATH消息。在T1和T2时刻之间，由于协议的软状态性，R1根据设定周期性地向R2发送PATH消息，此时的PATH消息不携带恢复标签，因此，重启方接收到不带恢复标签的PATH消息，认为是一个新建标签交换路径(LSP，Lable Switch Path)的PATH消息，从而进行新的预留以及新的入标签申请，与需要恢复的入标签为200和出标签为3很可能不一致，导致恢复失败。
在相关协议标准中，通过PATH消息中携带恢复标签来判断该报文是否为恢复报文，存在T1和T2之间发送的报文无法准确的判断其报文性质，无法实现恢复流程的准确处理。
发明内容
本发明实施例提供一种实现RSVP-TE协议报文处理的方法及装置，能够正确判断恢复报文，进行准确的恢复流程处理。
本发明实施例提供了一种实现RSVP-TE协议报文处理的方法，包括：
重启方保存优雅重启GR之前的路径PATH消息的标签交换路径LSP信息；
当重启方接收到来自辅助方的PATH消息不携带恢复标签对象时，根据接收到的PATH消息的LSP信息是否在已保存的LSP信息中，确定是否进行恢复流程处理。
可选地，确定是否进行恢复流程处理包括：
当接收到的PATH消息的LSP在已保存的LSP中，则丢弃所述PATH消 息，等待辅助方检测到重启方重启后，对重新生成的携带恢复标签对象的PATH消息进行恢复流程处理；
当接收到的PATH消息的LSP不在已保存的LSP中，则确定所述PATH消息为刷新的PATH消息，进行刷新PATH消息的处理。
可选地，当重启方接收到辅助方发送的PATH消息且PATH消息携带恢复标签对象时，该方法还包括：重启方直接进行恢复流程处理。
本发明实施例还提供一种实现RSVP-TE协议报文处理的装置，包括：保存单元及第一处理单元；其中，
所述保存单元，设置为保存GR之前的PATH消息的LSP信息；
所述第一处理单元，设置为接收到来自辅助方的PATH消息不携带恢复标签对象时，根据接收到的PATH消息的LSP信息是否在已保存的LSP信息中，确定是否进行恢复流程处理。
可选地，第一处理单元是设置为，
当接收到的PATH消息的LSP在已保存的LSP中，则丢弃所述PATH消息，等待辅助方检测到重启方重启后，对重新生成的携带恢复标签对象的PATH消息进行恢复流程处理；
当接收到的PATH消息的LSP不在已保存的LSP中，则确定所述PATH消息为刷新的PATH消息，进行刷新PATH消息的处理。
可选地，该装置还包括第二处理单元，其设置为接收到辅助方发送的PATH消息且PATH消息携带恢复标签对象时，进行恢复流程处理。
本发明实施例还提供一种计算机可读存储介质，存储有程序指令，当该程序指令被执行时可实现上述方法。
与相关技术相比，本申请实施例技术方案包括：重启方保存GR之前的PATH消息的LSP信息；当重启方接收到来自辅助方的PATH消息不携带恢复标签对象时，根据接收到的PATH消息的LSP信息是否在已保存的LSP信息中，确定是否进行恢复流程处理。本发明实施例通过保存GR之前的PATH消息的LSP信息，判断是否进行恢复流程处理，准确判断出了优雅重启前的PATH消息是否是恢复报文，实现了恢复流程的正确处理。
附图概述
图1是优雅重启的网络组成结构示意图；
图2是相关技术中优雅重启前后处理示意图；
图3为本发明实施例实现RSVP-TE协议报文处理的方法的流程图；
图4为本发明实施例实现RSVP-TE协议报文处理的装置的结构框图。
本发明的实施方式
下文中将结合附图对本发明实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
图3为本发明实施例实现RSVP-TE协议报文处理的方法的流程图，如图3所示，包括：
步骤300、重启方保存GR之前的PATH消息的LSP信息；
需要说明的是，这里LSP信息包括LSP键值、入标签、入接口、出标签及出接口等信息。
步骤301、当接收到的PATH消息不携带恢复标签对象时，根据接收到的PATH消息的LSP信息是否在已保存的LSP信息中，确定是否进行恢复流程处理。
本步骤中，确定是否进行恢复流程处理包括：
当接收到的PATH消息的LSP在已保存的LSP中，则丢弃该PATH消息，等待辅助方检测到重启方重启后，对重新生成的携带恢复标签对象的PATH消息进行恢复流程处理；
当接收到的PATH消息的LSP不在已保存的LSP中，则确定该PATH消息为刷新的PATH消息，进行刷新PATH消息的处理。
当重启方接收到辅助方发送的PATH消息且PATH消息携带恢复标签对象时，上述方法还包括：直接进行恢复流程处理。
图4为本发明实施例实现RSVP-TE协议报文处理的装置的结构框图，如图4所示，包括：保存单元401及第一处理单元402；其中，
保存单元401，设置为保存GR之前的PATH消息的LSP信息；
第一处理单元402，设置为接收到来自辅助方的PATH消息不携带恢复标签对象时，根据接收到的PATH消息的LSP信息是否在已保存的LSP信息中，确定是否进行恢复流程处理。
可选地，第一处理单元402是设置为：
当接收到的PATH消息的LSP在已保存的LSP中，则丢弃该PATH消息，等待辅助方检测到重启方重启后，对重新生成的携带恢复标签对象的PATH消息进行恢复流程处理；
当接收到的PATH消息的LSP不在已保存的LSP中，则确定该发送的PATH消息为刷新的PATH消息，进行刷新PATH消息的处理。
可选地，上述装置还包括第二处理单元403，其设置为接收到辅助方发送的PATH消息且PATH消息携带恢复标签对象时，进行恢复流程处理。
以下通过应用示例对本发明实施例方法进行说明。
应用示例1
当辅助方R1通过hello报文检测到重启方R2发生重启，R1和R2之间有一条路径1，R1向R2发送PATH消息，PATH消息中会携带恢复标签对象。
重启方接收到辅助方发送的该PATH消息的报文，通过判断PATH消息中有恢复标签对象，断定该PATH消息的报文为恢复报文，执行恢复流程处理。
应用示例2
当重启方R2发生优雅重启后，辅助方R1要检测到重启方R2发生了重启，(一般需要几个周期未接收到对端的hello的报文之后，才会认为重启方可能出现优雅重启。)由于RSVP是软状态协议，需要通过刷新维持其状态。所以，在辅助方R1未检测到重启方R2发生重启的时候，R1还是会向R2发 送路径1的刷新PATH消息，不携带恢复标签对象。
重启方法R2接收到该不携带恢复标签对象的PATH报文后，由于不携带恢复标签，在R2优雅重启前保存的LSP信息中可以查找到路径1的LSP信息。从而认为该报文是需要恢复的LSP，但是由于R1还未感知到R2重启，所以报文中未携带恢复标签对象。该报文暂时做丢弃处理，等待R1感知到R2重启之后，会继续发送携带恢复标签的PATH消息。
应用示例3
重启方法R2在重启后，接收到了路径2不携带恢复标签的PATH消息，通过查询之前保存的LSP信息，找不到路径2的信息。那么认为这是一条新建的LSP，按照新建LSP的进行PATH信息的流程处理。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件完成，上述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本发明实施例不限制于任何特定形式的硬件和软件的结合。
工业实用性
本发明实施例通过保存GR之前的PATH消息的LSP信息，判断是否进行恢复流程处理，准确判断出了优雅重启前的PATH消息是否是恢复报文，实现了恢复流程的正确处理。

Claims (7)

  1. 一种实现流量工程的资源预留协议RSVP-TE协议报文处理的方法，包括：
    重启方保存优雅重启GR之前的路径PATH消息的标签交换路径LSP信息；
    当重启方接收到来自辅助方的PATH消息不携带恢复标签对象时，根据接收到的PATH消息的LSP信息是否在已保存的LSP信息中，确定是否进行恢复流程处理。
  2. 根据权利要求1所述的方法，其中，所述确定是否进行恢复流程处理包括：
    当接收到的PATH消息的LSP在已保存的LSP中，则丢弃所述PATH消息，等待辅助方检测到重启方重启后，对重新生成的携带恢复标签对象的PATH消息进行恢复流程处理；
    当接收到的PATH消息的LSP不在已保存的LSP中，则确定所述PATH消息为刷新的PATH消息，进行刷新PATH消息的处理。
  3. 根据权利要求1或2所述的方法，当重启方接收到辅助方发送的PATH消息且PATH消息携带恢复标签对象时，该方法还包括：重启方直接进行恢复流程处理。
  4. 一种实现流量工程的资源预留协议RSVP-TE协议报文处理的装置，包括：保存单元及第一处理单元；其中，
    所述保存单元，设置为保存优雅重启GR之前的路径PATH消息的标签交换路径LSP信息；
    所述第一处理单元，设置为接收到来自辅助方的PATH消息不携带恢复标签对象时，根据接收到的PATH消息的LSP信息是否在已保存的LSP信息中，确定是否进行恢复流程处理。
  5. 根据权利要求4所述的装置，所述第一处理单元是设置为：
    当接收到的PATH消息的LSP在已保存的LSP中，则丢弃所述PATH消 息，等待辅助方检测到重启方重启后，对重新生成的携带恢复标签对象的PATH消息进行恢复流程处理；
    当接收到的PATH消息的LSP不在已保存的LSP中，则确定所述PATH消息为刷新的PATH消息，进行刷新PATH消息的处理。
  6. 根据权利要求4或5所述的装置，所述装置还包括第二处理单元，
    所述第二处理单元，设置为接收到辅助方发送的PATH消息且PATH消息携带恢复标签对象时，进行恢复流程处理。
  7. 一种计算机可读存储介质，存储有程序指令，当该程序指令被执行时可实现权利要求1-3任一项所述的方法。
PCT/CN2015/084972 2015-02-27 2015-07-23 一种实现rsvp-te协议报文处理的方法及装置 WO2016134582A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510091434.1A CN105991480A (zh) 2015-02-27 2015-02-27 一种实现rsvp-te协议报文处理的方法及装置
CN201510091434.1 2015-02-27

Publications (1)

Publication Number Publication Date
WO2016134582A1 true WO2016134582A1 (zh) 2016-09-01

Family

ID=56787841

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/084972 WO2016134582A1 (zh) 2015-02-27 2015-07-23 一种实现rsvp-te协议报文处理的方法及装置

Country Status (2)

Country Link
CN (1) CN105991480A (zh)
WO (1) WO2016134582A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108881340A (zh) * 2017-05-11 2018-11-23 中兴通讯股份有限公司 一种时延收集的方法及装置
US10680941B2 (en) * 2018-06-13 2020-06-09 Juniper Networks, Inc. Graceful restart procedures for label switched paths with label stacks

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101087207A (zh) * 2006-06-09 2007-12-12 华为技术有限公司 一种多节点通信故障的处理方法
CN101296239A (zh) * 2008-06-18 2008-10-29 杭州华三通信技术有限公司 刷新标签交换路径的方法及标签交换路由器
CN102571576A (zh) * 2011-12-29 2012-07-11 中兴通讯股份有限公司 一种多协议标签交换网络中优雅重启的方法及路由设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101087207A (zh) * 2006-06-09 2007-12-12 华为技术有限公司 一种多节点通信故障的处理方法
CN101296239A (zh) * 2008-06-18 2008-10-29 杭州华三通信技术有限公司 刷新标签交换路径的方法及标签交换路由器
CN102571576A (zh) * 2011-12-29 2012-07-11 中兴通讯股份有限公司 一种多协议标签交换网络中优雅重启的方法及路由设备

Also Published As

Publication number Publication date
CN105991480A (zh) 2016-10-05

Similar Documents

Publication Publication Date Title
US8218432B2 (en) Routing method in a label switching network
US20190132234A1 (en) Method and network device for computing forwarding path
US9590895B2 (en) Refresh interval independent fast reroute facility protection tear down messaging
US8027247B2 (en) Method and router for controlling graceful restart status
EP2978176B1 (en) Packet processing method and router
US8565071B2 (en) Protection method, system, and device in packet transport network
US8462805B2 (en) Graceful restart method of router, router and communication network thereof
WO2012037820A1 (zh) 多协议标签交换系统、节点设备及双向隧道的建立方法
WO2018121284A1 (zh) 一种处理路由的方法及网络设备
US20150085639A1 (en) Protecting a Label Switched Path Egress Without Using Downstream Labels
US9699073B2 (en) System and method for reducing traffic loss while using loop free alternate routes for multicast only fast reroute (MoFRR)
EP2360872B1 (en) Fast LSP alert mechanism
WO2006102851A1 (fr) Procede d'information et de negociation de l'aptitude a surveiller propre a la commutation de label
WO2010003323A1 (zh) 一种链路故障恢复的方法、系统和装置
WO2016033870A1 (zh) 隧道信号劣化通知及切换方法、装置和计算机存储介质
CN110601979B (zh) 具有标签栈的标签交换路径的平滑重启过程
WO2016134582A1 (zh) 一种实现rsvp-te协议报文处理的方法及装置
WO2016169214A1 (zh) 一种隧道保护切换的方法和装置
US7680028B1 (en) Method and apparatus for restarting RSVP processes in multiple network devices
US20190379596A1 (en) Methods and Systems preventing Make Before Break failures during soft preemption in MPLS
US10601611B1 (en) Method and apparatus for providing resiliency for delay sensitive services
WO2017152595A1 (zh) 一种响应网络拓扑变化的方法和装置
US9258221B2 (en) System and method for rapid protection of RSVP based LSP
WO2016101492A1 (zh) 一种业务转发表的设置方法及装置
WO2016061920A1 (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: 15883019

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: 15883019

Country of ref document: EP

Kind code of ref document: A1