WO2012155667A1 - 一种双向工作路径故障消失后的处理方法及装置、系统 - Google Patents

一种双向工作路径故障消失后的处理方法及装置、系统 Download PDF

Info

Publication number
WO2012155667A1
WO2012155667A1 PCT/CN2012/072839 CN2012072839W WO2012155667A1 WO 2012155667 A1 WO2012155667 A1 WO 2012155667A1 CN 2012072839 W CN2012072839 W CN 2012072839W WO 2012155667 A1 WO2012155667 A1 WO 2012155667A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
local
dnr
remote
working path
Prior art date
Application number
PCT/CN2012/072839
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 WO2012155667A1 publication Critical patent/WO2012155667A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/03—Arrangements for fault recovery
    • H04B10/032—Arrangements for fault recovery using working and protection systems

Definitions

  • the present invention relates to an optical transport network (OTN) technology, and in particular, to a processing method, apparatus, and system after a bidirectional working path failure disappears.
  • OTN optical transport network
  • G.873.1 is the linear protection mechanism of the optical transport network at the optical channel data unit (ODUk) level, and the APS (Automatic Protection Switched) protocol and the protection switching operation procedure are determined. According to the standard operating procedure in G.873.1, if both the remote and the near working paths fail (SF), both ends will be switched, and each will send a work failure request (SF) to the peer end.
  • ODUk optical channel data unit
  • APS Automatic Protection Switched
  • both the far end and the near end send a reverse request (RR, Reverse Request) to its own peer, and according to G.873.1
  • RR reverse request
  • the near end will the signal Reverse, when the far end request has the highest priority, the near end will Request)
  • the remote end and the near end return a reverse request (RR, Reverse Request) to the opposite end, as described above.
  • the remote end and the near end enter a deadlock state after the working path failure disappears, and cannot be restored to the working state or the initial state.
  • the main object of the present invention is to provide a processing method, apparatus, and system for a two-way working path failure disappearing, so as to solve the problem that the remote end and the near end enter a deadlock state after the working path failure disappears and cannot be restored to the working state. Or an initial state issue.
  • the technical solution of the present invention is achieved as follows:
  • the present invention provides a processing method after a two-way working path failure disappears, and the method includes:
  • the local request is set to no request (NR) or no return request (DNR), and when the priority of the local request is lower than the remote request, the pair is The terminal sends a transmission request equal to NR or DNR.
  • the method further includes: after the working path fault of the opposite end disappears, the opposite end sets its local request as NR or DNR, The current remote request of the peer is the same as its local request, and the peer performs its local request and returns to the working state or the initial state.
  • the peer end performs its local request, and returns to the working state or the initial state, and further includes: the peer end sends a sending request equal to NR or DNR;
  • the method further includes: receiving a remote request from the peer, and when the remote request is the same as the local request, executing the local request, returning to an active state or an initial state.
  • the present invention also provides a node for processing after a two-way working path failure disappears, the node, configured to set a local request to NR or DNR after a bidirectional working path failure occurs and a local working path failure disappears, and When the local request has a lower priority than the remote request, a sending request equal to NR or DNR is sent to the opposite end.
  • the node is further configured to: after sending a sending request equal to NR or DNR to the opposite end, receiving a remote request from the opposite end, when the remote request is the same as the local request, performing the Local request, back to working state or initial state.
  • the present invention also provides a processing system after a two-way working path failure disappears, the system comprising: a node, configured to set a local request to NR or DNR after a bidirectional working path failure occurs and a local working path failure disappears, and When the priority of the local request is lower than the remote request, a sending request equal to NR or DNR is sent to the opposite end.
  • the system further includes: a peer end of the node, configured to set its own local request as NR or DNR after its own working path failure disappears, and request and itself in its own remote request When the local request is the same, execute its own local request and return to the working state or initial state.
  • the opposite end of the node is further configured to send a sending request equal to NR or DNR to the node;
  • the node is further configured to receive a remote request from the peer end, and when the remote request is the same as the local request, execute the local request, and return to an active state or an initial state.
  • the local request is set to NR or DNR, and when the priority of the local request is lower than the remote request, the opposite end is issued equal to NR or Send request for DNR.
  • the NR or DNR can be executed to return from the protection state to the working state or to the initial state, so as to avoid the deadlock state after the working path failure disappears, and the two-way protection structure is improved. Fault recovery efficiency and business processing efficiency.
  • FIG. 1 is a schematic diagram of an implementation of a processing method after a bidirectional working path fault disappears according to the present invention
  • FIG. 2 is a schematic diagram of an implementation process of a bidirectional fault disappearing in a bidirectional protection structure according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of the implementation process of the bidirectional fault disappearing in the bidirectional protection structure according to the non-return type in the second embodiment of the present invention. detailed description
  • the basic idea of the present invention is: after a bidirectional working path failure occurs in a bidirectional protection structure, a node that first disappears from a working path failure sets a local request to NR or DNR, and when the priority of the local request is lower than the remote request, Send a request to the peer to be equal to NR or DNR, so When the fault at the opposite end also disappears, the peer will set the local request to NR or DNR, and execute the local request and return to the working state. In this way, after the working channel is restored at both ends, it can return from the protected state to the working state. Or return to the initial state.
  • the method may include: after the bidirectional working path fault occurs and the local working path fault disappears, the local request is set to NR or DNR, and the local request is When the priority of the request is lower than the far-end request, a transmission request equal to NR or DNR is sent to the opposite end.
  • the local request is set to NR or DNR, even if the remote request has a higher priority than the local request (for example, when the current remote request is SF), the peer is sent equal to the peer.
  • the method may further include: after the working path fault of the opposite end disappears, the opposite end sets its local request as NR or DNR, then the pair The current remote request is the same as the local request of the peer, and the peer performs a local request and returns to the working state or the initial state.
  • the returning of the node or the peer to the initial state may be: the local request and the remote request on the node or the peer return to the initial value, but the service is still carried on the protection path, so if the fault occurs again, the path switching occurs.
  • the node or peer can restore the service to the original path.
  • the peer end performs a local request, and returns to the working state or the initial state, and also sends a sending request equal to the NR or the DNR.
  • the method further includes: receiving a remote request from the peer, and when the remote request is the same as the local request, executing the local request, returning to a working state or an initial state.
  • the present invention further provides a node for processing after a two-way working path failure disappears, wherein the node is configured to set a local request to an NR or a DNR after a bidirectional working path failure occurs and a local working path failure disappears. And when the priority of the local request is lower than the remote request, send a sending request equal to NR or DNR to the opposite end.
  • the node is further configured to: after sending a sending request equal to NR or DNR to the opposite end, receive a remote request from the opposite end, and execute the local request when the remote request is the same as the local request, Go back to work or initial state.
  • the present invention also provides a processing system after the two-way working path failure disappears.
  • the system includes the above-mentioned nodes.
  • the system may further include: a peer end of the node, configured to set its local request to be NR or DNR after its own working path failure disappears, and is in its current far When the end request is the same as the local request, the local request is executed and returned to the working state or the initial state.
  • the peer end of the node is further configured to send a sending request equal to NR or DNR to the node; the node is further configured to receive a remote request from the peer end, where the remote request and the remote end When the local request is the same, the local request is executed, and the working state or the initial state is returned.
  • the processing flow after the two-way fault disappears in the bidirectional protection structure, as shown in FIG. 2, may include the following steps:
  • Step 201 After detecting that the local working path fails, the near-end device performs switching, the local request (LReq) is set as the work failure request (SF), and the LReq is preferentially compared with the remote request (RReq) from the remote Z. After that, LReq is executed, and a transmission request equal to SF (SendReq) is sent to the remote Z through the APS channel (APS CHANEL);
  • the G.873.1 standard specifies that SF has a higher priority than NR and DNR. Therefore, LReq has a higher priority than RReq. Therefore, LReq is executed, that is, SF is executed.
  • Step 202 The remote end Z receives the RReq from the near end A. Since the current LReq is NR and the RReq is SF, and the RReq has a higher priority than the LReq, the RReq is executed, the conclusion of the switching is obtained, and the switching is performed, and the remote is performed. End A sends SendReq equal to RR;
  • Step 203 Near-end A receives RReq from remote Z, since RReq is RR, then End A stops sending the request to the remote Z for processing;
  • Step 204 After the remote Z detects that the local working path also fails, the LReq is set to SF, and the RReq received last time is also SF, the RReq and the LReq have the same priority, and the remote Z performs the action according to the LReq, End A sends SendReq equal to SF;
  • Step 205 The near end A receives the RReq from the remote end Z. Since the RReq is SF, and the current LReq is also SF, the RReq and the LReq have the same priority, and the near end A performs the action according to the LReq, and sends the same to the remote end Z equal to the SF. SendReq;
  • Step 206 The remote end Z receives the RReq. Since the currently received RReq is SF, which is the same as the RReq received by the remote Z last time, the remote end Z stops sending the request to the near-end A.
  • Step 207 After the working path failure of the near-end A disappears, the near-end A sets the current LReq to NR. Even if the current RReq is SF, the near-end A performs RReq, and sends a SendReq equal to NR to the remote Z according to a preset configuration.
  • the SendReq equal to NR or DNR is issued after the work path failure disappears, both in the near-end and the far-end Z, by the protocol or by the near-end and far-end negotiation.
  • Step 208 The remote end Z receives the RReq from the near end A. Since the RReq is NR and the current LReq is SF, and the LReq has a higher priority than the RReq, the remote end Z performs LReq, is still in the protection state, and Remote A sends a SendReq equal to SF;
  • Step 209 The near end A receives the RReq from the far end Z. Since the RReq is SF, and the current LReq is also NR, and the RReq has a higher priority than the LReq, the RReq is executed, still in the protection state, and is far to the remote Z. Issue SendReq equal to RR;
  • Step 210 The remote end Z receives the RReq from the near end A. Since the RReq is an RR, the remote end Z stops sending the request to the near end A.
  • Step 211 After the failure of the working path of the remote Z disappears, the current LReq is set to NR, since the current RReq is also NR, the RReq and LReq have the same priority, and the remote Z executes LReq, returns to the working state, and Sending SendReq equal to NR to the near end A;
  • Step 213 The remote end Z receives the RReq from the near end A, and the RReq is NR. The same as the last received RReq, the remote end Z stops sending the request to the near end A, and thus, the far end Z and the near end A After the work path fails, it returns to the working state and ends the current process.
  • the non-return type is taken as an example.
  • the processing flow after the two-way fault disappears in the bidirectional protection structure, as shown in FIG. 3, may include the following steps:
  • Steps 301-306 are exactly the same as steps 201-206;
  • Step 307 after the working path failure of the near-end A disappears, the near-end A sets the current LReq to DNR. Even if the current RReq is SF, the near-end A performs RReq, and sends a DNR equal to the DNR according to the preset configuration. SendReq;
  • the SendReq equal to NR or DNR is issued after the work path failure disappears, both in the near-end and the far-end Z, by the protocol or by the near-end and far-end negotiation.
  • Steps 308-310 which are basically the same as steps 208-210, except that DNR is used instead of NR;
  • Step 311 After the failure of the working path of the remote Z disappears, the current LReq is set to DNR. Since the current RReq is also DNR, the RReq and LReq have the same priority, and the remote Z executes LReq, returns to the initial state, and Sending SendReq equal to DNR to near end A;
  • the remote Z performs LReq
  • the RReq and LReq of the remote Z are restored to the initial values, but the service still carries the protection path.
  • Steps 312-313 are basically the same as steps 212-213 except that DNR is used instead of NR, and near-end A returns to the initial state.
  • the RReq and LReq of the near end A are restored to the initial value. But the service still carries the protection path.

Landscapes

  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Description

一种双向工作路径故障消失后的处理方法及装置、 系统 技术领域
本发明涉及光传送网（OTN, Optical Transport Network )技术， 尤其涉 及一种双向工作路径故障消失后的处理方法及装置、 系统。 背景技术
在 OTN中， G.873.1为光信道数据单元（ODUk )层面的光传送网线性 保护机制， 确定了自动保护倒换（APS, Automatic Protection Switched )协 议和保护倒换操作程序。 按照 G.873.1中标准的操作流程， 如果远端和近端 的工作路径均发生故障（SF ), 两端均会发生倒换， 并且各自先后向对端发 送一个工作失效请求（SF ), 在远端和近端的工作路径故障消失后， 不管是 返回式还是非返回式， 远端和近端均先后向自身的对端发送一个反向请求 ( RR, Reverse Request ), 而按照在 G.873.1建议书中 8.3 节的规定 "在双 向倒换中， 在远端请求具有最高优先级时， 近端发出反向请求 （In bidirectional switching, when the far end request has the highest priority, the near end will signal Reverse Request )，，， 由于 SF具有最高优先级， 因此， 按 照上述规定远端和近端在接收到的远端请求为 SF时，会向对端返回反向请 求（RR, Reverse Request ), 如此， 使得远端和近端在工作路径故障消失后 进入一个死锁状态， 不能恢复到工作状态或初始状态。 发明内容
有鉴于此， 本发明的主要目的在于提供一种双向工作路径故障消失后 的处理方法及装置、 系统， 以解决远端和近端在工作路径故障消失后进入 死锁状态而不能恢复到工作状态或初始状态的问题。 为达到上述目的， 本发明的技术方案是这样实现的：
本发明提供了一种双向工作路径故障消失后的处理方法， 所述方法包 括：
在发生双向工作路径故障且本地工作路径故障消失后， 将本地请求置 为无请求 （NR )或不返回请求（DNR ), 并在所述本地请求的优先级低于 远端请求时， 向对端发出等于 NR或 DNR的发送请求。
在上述方案中， 向对端发出等于 NR或 DNR的发送请求后， 所述方法 还包括： 所述对端的工作路径故障消失后， 所述对端将自身的本地请求置 为 NR或 DNR, 则所述对端当前的远端请求与其本地请求相同， 所述对端 执行其本地请求， 回到工作态或初始状态。
在上述方案中， 所述对端执行其本地请求， 回到工作态或初始状态， 还包括： 所述对端发出等于 NR或 DNR的发送请求；
所述方法还包括： 接收来自所述对端的远端请求， 在所述远端请求与 所述本地请求相同时， 执行所述本地请求， 回到工作态或初始状态。
本发明还提供了一种用于双向工作路径故障消失后处理的节点， 所述 节点， 用于在发生双向工作路径故障且本地工作路径故障消失后， 将本地 请求置为 NR或 DNR, 并在所述本地请求的优先级低于远端请求时， 向对 端发出等于 NR或 DNR的发送请求。
在上述方案中， 所述节点还用于在向对端发出等于 NR或 DNR的发送 请求后， 接收来自对端的远端请求， 在所述远端请求与所述本地请求相同 时， 执行所述本地请求， 回到工作态或初始状态。
本发明还提供了一种双向工作路径故障消失后的处理系统， 所述系统 包括： 节点， 用于在发生双向工作路径故障且本地工作路径故障消失后， 将本地请求置为 NR或 DNR,并在所述本地请求的优先级低于远端请求时， 向对端发出等于 NR或 DNR的发送请求。 在上述方案中， 所述系统还包括： 所述节点的对端， 用于在自身的工 作路径故障消失后， 将自身的本地请求置为 NR或 DNR, 并在自身当前的 远端请求与自身的本地请求相同时， 执行自身的本地请求， 回到工作态或 初始状态。
在上述方案中， 所述节点的对端， 还用于向所述节点发出等于 NR或 DNR的发送请求；
所述节点， 还用于接收来自所述对端的远端请求， 在所述远端请求与 所述本地请求相同时， 执行所述本地请求， 回到工作态或初始状态。
本发明中， 在发生双向工作路径故障且本地工作路径故障消失后， 将 本地请求置为 NR或 DNR,并且在所述本地请求的优先级低于远端请求时， 向对端发出等于 NR或 DNR的发送请求。 如此， 使得两端先后恢复工作通 道后， 能够执行 NR或 DNR, 从而从保护态返回到工作态或恢复到初始状 态， 避免在工作路径故障消失后两端进入死锁状态， 提高了双向保护结构 的故障恢复效率和业务处理效率。 附图说明
图 1为本发明双向工作路径故障消失后的处理方法的实现示意图； 图 2 为本发明实施例一以返回式为例双向保护结构中双向故障消失后 处理过程的实现示意图；
图 3 为本发明实施例二以非返回式为例双向保护结构中双向故障消失 后处理过程的实现示意图。 具体实施方式
本发明的基本思想是： 在双向保护结构中发生双向工作路径故障后， 由工作路径故障先消失的节点将本地请求置为 NR或 DNR, 并在本地请求 的优先级低于远端请求时，向对端发出等于 NR或 DNR的发送请求，如此， 在对端的故障也消失时， 对端会将本地请求置为 NR或 DNR, 并执行本地 请求而返回到工作态， 这样， 在两端先后恢复工作通道后， 都能够从保护 态返回到工作态或恢复到初始状态。
本发明双向工作路径故障消失后的处理方法， 如图 1 所示， 主要可以 包括： 在发生双向工作路径故障且本地工作路径故障消失后， 将本地请求 置为 NR或 DNR, 并在所述本地请求的优先级低于远端请求时， 向对端发 出等于 NR或 DNR的发送请求。
具体地， 在本地工作路径故障消失后， 将本地请求置为 NR或 DNR, 即使远端请求的优先级高于本地请求（例如， 当前的远端请求为 SF时）， 仍向对端发出等于 NR或 DNR的发送请求。
在向对端发出等于 NR或 DNR的发送请求后， 所述方法还可以包括： 所述对端的工作路径故障消失后， 所述对端将自身的本地请求置为 NR或 DNR, 则所述对端当前的远端请求与所述对端的本地请求相同， 所述对端 执行本地请求， 回到工作态或初始状态。
这里， 节点或对端回到初始状态可以是： 节点或对端上的本地请求和 远端请求均回到初始值， 但业务仍然承载在保护路径上， 如此， 如果再发 生故障， 发生路径倒换， 节点或对端可以将业务恢复到原路径上。
其中， 所述对端执行本地请求， 回到工作态或初始状态后， 还发出等 于 NR或 DNR的发送请求。 所述方法还包括： 接收来自所述对端的远端请 求， 在所述远端请求与所述本地请求相同时， 执行所述本地请求， 回到工 作态或初始^ 态。
相应的， 本发明还提供了一种用于双向工作路径故障消失后处理的节 点， 所述节点， 用于在发生双向工作路径故障且本地工作路径故障消失后， 将本地请求置为 NR或 DNR,并在所述本地请求的优先级低于远端请求时， 向对端发出等于 NR或 DNR的发送请求。 其中， 所述节点还用于在向对端发出等于 NR或 DNR的发送请求后， 接收来自对端的远端请求， 在所述远端请求与所述本地请求相同时， 执行 所述本地请求， 回到工作态或初始状态。
此外， 本发明还提供了一种双向工作路径故障消失后的处理系统， 如 图 1所示， 所述系统包括上述的节点。 其中， 如图 1所示， 所述系统还可 以包括： 所述节点的对端， 用于在自身的工作路径故障消失后， 将自身的 本地请求置为 NR或 DNR, 并在自身当前的远端请求与本地请求相同时， 执行本地请求， 回到工作态或初始状态。
其中， 所述节点的对端， 还用于向所述节点发出等于 NR或 DNR的发 送请求； 所述节点， 还用于接收来自所述对端的远端请求， 在所述远端请 求与所述本地请求相同时， 执行所述本地请求， 回到工作态或初始状态。
实施例一
本实施例中， 以返回式为例双向保护结构中双向故障消失后的处理流 程， 如图 2所示， 可以包括以下步驟：
步驟 201 : 近端 Α检测到本地工作路径失效后， 进行倒换， 本地请求 ( LReq )置为工作失效请求（ SF ), 并将 LReq与来自远端 Z的远端请求 ( RReq )进行优先级比较后， 执行 LReq, 通过 APS信道（ APS CHANEL ) 向远端 Z发出等于 SF的发送请求（ SendReq );
这里， G.873.1标准中规定 SF与 NR、 DNR相比具有较高的优先级， 因此， 相对于 RReq, LReq都具有较高的优先级， 因此， 执行 LReq, 即执 行 SF。
步驟 202: 远端 Z接收来自近端 A的 RReq, 由于当前的 LReq为 NR, 而 RReq为 SF, RReq的优先级高于 LReq,则执行 RReq,得出倒换的结论， 进行倒换， 并向远端 A发出等于 RR的 SendReq;
步驟 203: 近端 A接收来自远端 Z的 RReq, 由于 RReq为 RR, 则近 端 A停止发送请求给远端 Z的处理；
步驟 204： 远端 Z检测到本地的工作路径也失效后， 将 LReq置为 SF , 而上次接收到的 RReq也为 SF , RReq与 LReq优先级相同，远端 Z按照 LReq 执行动作， 向远端 A发出等于 SF的 SendReq;
步驟 205, 近端 A接收来自远端 Z的 RReq, 由于该 RReq为 SF, 且当 前的 LReq也为 SF, RReq与 LReq优先级相同， 近端 A按照 LReq执行动 作， 向远端 Z发出等于 SF的 SendReq;
步驟 206, 远端 Z接收所述 RReq, 由于当前接收到的 RReq为 SF, 与 远端 Z上次接收到的 RReq相同，则远端 Z停止发送请求给近端 A的处理； 步驟 207 ,在近端 A的工作路径失效消失后，近端 A将当前的 LReq置 为 NR, 即使当前的 RReq为 SF, 近端 A执行 RReq, 并按照预设配置向远 端 Z发出等于 NR的 SendReq;
这里， 预先通过协议规定或由近端和远端协商的方式， 在近端 A和远 端 Z上均配置"在工作路径失效消失后仅发出等于 NR或 DNR的 SendReq"。
步驟 208, 远端 Z接收来自近端 A的 RReq, 由于该 RReq为 NR, 而 当前的 LReq为 SF, LReq的优先级高于 RReq, 则远端 Z执行 LReq, 仍在 保护态上， 并向远端 A发出等于 SF的 SendReq;
步驟 209: 近端 A接收来自远端 Z的 RReq, 由于该 RReq为 SF, 与当 前的 LReq也为 NR, RReq的优先级高于 LReq,则执行 RReq,仍在保护态， 并向远端 Z发出等于 RR的 SendReq;
步驟 210: 远端 Z接收来自近端 A的 RReq, 由于该 RReq为 RR, 则 远端 Z停止发送请求给近端 A的处理；
步驟 211 : 在远端 Z的工作路径的失效消失后， 将当前的 LReq置为 NR, 由于当前的 RReq也为 NR, RReq与 LReq优先级相同， 远端 Z执行 LReq , 返回到工作态， 并向近端 A发出等于 NR的 SendReq; 步驟 212: 近端 A接收来自远端 Z的 RReq, 由于当前的 LReq也为 NR, 则近端 A执行 LReq, 返回到工作态， 并向远端 Z发出等于 NR的 SendReq;
步驟 213: 远端 Z接收来自近端 A的 RReq, 该 RReq为 NR, 与上次 接收到的 RReq相同，远端 Z停止发送请求给近端 A的处理， 至此，远端 Z 和近端 A均在工作路径失效消失后， 恢复到工作态， 结束当前流程。
实施例二
本实施例中， 以非返回式为例双向保护结构中双向故障消失后的处理 流程， 如图 3所示， 可以包括以下步驟：
步驟 301-306, 与步驟 201-206完全相同；
步驟 307,在近端 A的工作路径失效消失后，近端 A将当前的 LReq置 为 DNR, 即使当前的 RReq为 SF, 近端 A执行 RReq, 并按照预设配置向 远端 Z发出等于 DNR的 SendReq;
这里， 预先通过协议规定或由近端和远端协商的方式， 在近端 A和远 端 Z上均配置"在工作路径失效消失后仅发出等于 NR或 DNR的 SendReq"。
步驟 308-310, 与步驟 208-210基本相同， 所不同的是， 用 DNR代替 了 NR;
步驟 311 : 在远端 Z的工作路径的失效消失后， 将当前的 LReq置为 DNR, 由于当前的 RReq也为 DNR, RReq与 LReq优先级相同， 远端 Z执 行 LReq, 返回到初始状态， 并向近端 A发出等于 DNR的 SendReq;
这里， 远端 Z执行 LReq后， 远端 Z的 RReq与 LReq恢复到初始值， 但业务仍承载保护路径上。
步驟 312-313 , 与步驟 212-213基本相同， 所不同的是， 用 DNR代替 了 NR, 近端 A返回到初始状态。
这里，近端 A执行 LReq后，近端 A的 RReq与 LReq均恢复到初始值， 但业务仍承载保护路径上。
其中， 上述实施例中， 图 2和图 3中所示的 （1, 1 ) 中， 前一个 "1" 表示当前业务承载在保护路径上， 后一个 "1" 表示永久桥接。 图 2所示的 (0, 1 ) 中， "0" 表示当前业务承载在原路径上， "1" 表示永久桥接。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种双向工作路径故障消失后的处理方法， 其特征在于， 所述方法 包括：
在发生双向工作路径故障且本地工作路径故障消失后， 将本地请求置 为无请求 NR或不返回请求 DNR, 并在所述本地请求的优先级低于远端请 求时， 向对端发出等于 NR或 DNR的发送请求。
2、 根据权利要求 1所述双向工作路径故障消失后的处理方法， 其特征 在于， 向对端发出等于 NR或 DNR的发送请求后， 所述方法还包括：
所述对端的工作路径故障消失后，所述对端将自身的本地请求置为 NR 或 DNR, 则所述对端当前的远端请求与其本地请求相同， 所述对端执行其 本地请求， 回到工作态或初始状态。
3、 根据权利要求 2所述双向工作路径故障消失后的处理方法， 其特征 在于， 所述对端执行其本地请求， 回到工作态或初始状态， 还包括： 所述 对端发出等于 NR或 DNR的发送请求；
所述方法还包括： 接收来自所述对端的远端请求， 在所述远端请求与 所述本地请求相同时， 执行所述本地请求， 回到工作态或初始状态。
4、 一种用于双向工作路径故障消失后处理的节点， 其特征在于， 所述 节点， 用于在发生双向工作路径故障且本地工作路径故障消失后， 将本地 请求置为 NR或 DNR, 并在所述本地请求的优先级低于远端请求时， 向对 端发出等于 NR或 DNR的发送请求。
5、 根据权利要求 4所述的节点， 其特征在于， 所述节点还用于在向对 端发出等于 NR或 DNR的发送请求后， 接收来自对端的远端请求， 在所述 远端请求与所述本地请求相同时， 执行所述本地请求， 回到工作态或初始 状态。
6、 一种双向工作路径故障消失后的处理系统， 其特征在于， 所述系统 包括： 节点， 用于在发生双向工作路径故障且本地工作路径故障消失后， 将本地请求置为 NR或 DNR,并在所述本地请求的优先级低于远端请求时， 向对端发出等于 NR或 DNR的发送请求。
7、 根据权利要求 6所述的系统， 其特征在于， 所述系统还包括： 所述 节点的对端， 用于在自身的工作路径故障消失后， 将自身的本地请求置为
NR或 DNR, 并在自身当前的远端请求与自身的本地请求相同时， 执行自 身的本地请求， 回到工作态或初始状态。
8、 根据权利要求 7所述的系统， 其特征在于，
所述节点的对端，还用于向所述节点发出等于 NR或 DNR的发送请求； 所述节点， 还用于接收来自所述对端的远端请求， 在所述远端请求与 所述本地请求相同时， 执行所述本地请求， 回到工作态或初始状态。
PCT/CN2012/072839 2011-07-15 2012-03-22 一种双向工作路径故障消失后的处理方法及装置、系统 WO2012155667A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110198396.1 2011-07-15
CN2011101983961A CN102882590A (zh) 2011-07-15 2011-07-15 一种双向工作路径故障消失后的处理方法及装置、系统

Publications (1)

Publication Number Publication Date
WO2012155667A1 true WO2012155667A1 (zh) 2012-11-22

Family

ID=47176256

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/072839 WO2012155667A1 (zh) 2011-07-15 2012-03-22 一种双向工作路径故障消失后的处理方法及装置、系统

Country Status (2)

Country Link
CN (1) CN102882590A (zh)
WO (1) WO2012155667A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9806939B2 (en) 2013-10-17 2017-10-31 Electronics And Telecommunications Research Institute Method and apparatus for linear protection switching
KR20150044801A (ko) * 2013-10-17 2015-04-27 한국전자통신연구원 선형 보호 절체 방법 및 장치

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101662329A (zh) * 2008-08-29 2010-03-03 华为技术有限公司 倒换方法、网络节点和网络系统
CN101911595A (zh) * 2007-11-16 2010-12-08 韩国电子通信研究院 以太环网的非反向模式中的故障恢复方法
CN102006188A (zh) * 2010-11-19 2011-04-06 中兴通讯股份有限公司 一种传送网中的路径回切方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100401688C (zh) * 2005-09-30 2008-07-09 华为技术有限公司 光通信系统的自动恢复检测方法、自动恢复方法及装置
CN100505574C (zh) * 2005-12-23 2009-06-24 中兴通讯股份有限公司 一种通讯链路的主备倒换方法
CN1972142B (zh) * 2006-12-08 2010-12-08 中兴通讯股份有限公司 通讯设备单板主备倒换装置及实现方法
CN101626272B (zh) * 2008-07-10 2013-03-20 中兴通讯股份有限公司 一种光网络中错连阻错的实现方法
CN101790110B (zh) * 2009-01-22 2012-12-19 中兴通讯股份有限公司 一种协调自动保护倒换操作与恢复操作的装置及方法
CN101951303B (zh) * 2010-09-26 2016-03-30 中兴通讯股份有限公司 一种实现复用段双向线性保护倒换的方法及节点设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101911595A (zh) * 2007-11-16 2010-12-08 韩国电子通信研究院 以太环网的非反向模式中的故障恢复方法
CN101662329A (zh) * 2008-08-29 2010-03-03 华为技术有限公司 倒换方法、网络节点和网络系统
CN102006188A (zh) * 2010-11-19 2011-04-06 中兴通讯股份有限公司 一种传送网中的路径回切方法及装置

Also Published As

Publication number Publication date
CN102882590A (zh) 2013-01-16

Similar Documents

Publication Publication Date Title
KR101385377B1 (ko) 데이터를 포워딩하기 위한 방법, 장치 및 시스템
WO2008046358A1 (fr) Procédé et dispositif destinés à réaliser une pénétration d'un statut de liaison de réseau point à multipoint
EP3217608B1 (en) Switchback delay methods and devices
WO2014166065A1 (zh) 保护业务可靠性的方法、设备及网络虚拟化系统
WO2011095101A1 (zh) 一种分组传送网络的线性1：n保护方法、装置和系统
WO2009124499A1 (zh) 信令传送的保护方法、装置及通信系统
WO2012065435A1 (zh) 一种传送网中的路径回切方法及装置
JP2007258926A (ja) 故障復旧方法およびノードならびにネットワーク
GB2444170A (en) Ethernet protection using a redundant link, with link up of a remote port being triggered using a "link status control mechanism".
CN102264088A (zh) 伪线保护倒换实现方法及装置
WO2015196676A1 (zh) 组网保护方法、装置及组网中的汇聚主用网元
US8908506B2 (en) Method and system for switching APS service channel and automatic protection switching device
CN105790965A (zh) 链路切换方法、装置及线卡
WO2012171164A1 (zh) 一种网络安全保护方法、装置及系统
JP5208051B2 (ja) 通信装置
CN106330699B (zh) 一种组播链路的切换方法、装置及路由设备
CN106161232B (zh) 一种隧道保护切换的方法和装置
CN104468168A (zh) 网络故障恢复方法、控制服务器及交换机
WO2013091576A1 (zh) 一种环网保护的实现方法及系统
WO2010034147A1 (zh) 一种实现中继网关容灾不断话的方法、系统及媒体网关
WO2012155667A1 (zh) 一种双向工作路径故障消失后的处理方法及装置、系统
WO2012037754A1 (zh) 一种实现复用段双向线性保护倒换的方法及节点设备
WO2010133157A1 (zh) 一种通信方法、设备及系统
EP2451116B1 (en) Automatic recovering method and device for node resource state in dense wavelength division multiplexing based automatic switched optical network system
WO2012000329A1 (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: 12786385

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

Country of ref document: EP

Kind code of ref document: A1