WO2016161802A1 - 一种快速倒换的dni-pw实现方法及系统 - Google Patents

一种快速倒换的dni-pw实现方法及系统 Download PDF

Info

Publication number
WO2016161802A1
WO2016161802A1 PCT/CN2015/093679 CN2015093679W WO2016161802A1 WO 2016161802 A1 WO2016161802 A1 WO 2016161802A1 CN 2015093679 W CN2015093679 W CN 2015093679W WO 2016161802 A1 WO2016161802 A1 WO 2016161802A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
dni
vpws
aggregation node
l2ve
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/CN2015/093679
Other languages
English (en)
French (fr)
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.)
Fiberhome Telecommunication Technologies Co Ltd
Original Assignee
Fiberhome Telecommunication Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fiberhome Telecommunication Technologies Co Ltd filed Critical Fiberhome Telecommunication Technologies Co Ltd
Publication of WO2016161802A1 publication Critical patent/WO2016161802A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability

Definitions

  • the present invention relates to the field of communication technologies, and in particular, to a DNI-PW (Dual Node Interconnection Pseudo Wire) implementation method and system.
  • DNI-PW Device Node Interconnection Pseudo Wire
  • the carrier network is generally divided into two layers: the backbone network and the metropolitan area network.
  • the backbone network can be divided into three layers: the core layer, the aggregation layer, and the access layer.
  • the DNI-PW is set up between the two aggregation devices to protect some or all of the N VPWSs with one VPWS (Virtual Pseudo Wire Service) (DNI-PW).
  • the downlink switchover needs to refresh the N host states in each VC (Virtual Circuit), resulting in a long switching time.
  • the control plane needs to sense the service switching state and increase the software complexity.
  • the uplink switching needs to refresh the service bridging status one by one.
  • the switching time is long.
  • the present invention aims to provide a fast switching DNI-PW implementation method and system, and the invention reduces the workload; at the forwarding layer, the control plane shields the signaling interaction before and after the switching. Difference, the protocol of the control plane does not need to sense the process of switching; the uplink switching speed is improved.
  • the technical solution adopted by the present invention is: a fast switching DNI-PW implementation method, which is applied to a virtual private line service VPWS network, where the VPWS network includes a primary VPWS, an alternate VPWS, a primary aggregation node, The standby aggregation node and the Layer 3 virtual private network L3VPN, and the dual node interconnection pseudowire DNI-PW is provided between the primary aggregation node and the standby aggregation node, including the following steps: Step S1. Add an intf_tbl table to the primary VPWS, The l2ve_bridge_tbl table is added to the standby VPWS.
  • the intf_tbl table is used to determine whether the service enters the primary VPWS, the standby VPWS, or the L3VPN.
  • the l2ve_bridge_tbl table is used to implement the Layer 2 virtual instance interface L2VE_Port and the 3 layer virtual instance on the exit of the Layer 2 virtual private network L2VPN.
  • the association of the interface L3VE_Port, the L2VE_Port includes L2VE0 and L2VE1, the L3VE_Port includes L3VE1; Step S2. Determine whether a fault occurs, and if yes, go to step S3; if not, go to step S5; Step S3.
  • step S4 Determine the fault type If the main path is broken, the process goes to step S4; if the main aggregation node is dialed, the process goes to step S7; if the main use is aggregated If the power is off, go to step S6; step S4. Determine whether the service has been broken, if yes, go to step S7; if not, go to step S5; step S5.
  • the uplink service is in the primary aggregation node L2VPN is connected to L3VPN through L2VE1 and L3VE1; the downlink service is connected to the active VPWS through L3VE1 and L2VE1 at the primary aggregation node; the process ends; Step S6.
  • the uplink service is bridged to the standby aggregation node through L2VE1 and L3VE1.
  • L3VPN the downlink service is connected to the standby VPWS through the L2VE1 and L3VE1 at the standby aggregation node; the process ends; Step S7.
  • the uplink service is connected to the DNI-PW through the L2VE1 and L2VE0 bridges at the standby aggregation node, and is bridged by the L2VE0 and L3VE1 at the primary aggregation node.
  • the downlink service is connected to the DNI-PW through the L3VE1 and L2VE0 bridges at the primary aggregation node, and the standby aggregation node is connected to the standby aggregation node through the L2VE0 and L2VE1 at the standby aggregation node;
  • the intf_tbl table includes dni_pw_ena, which is used as a DNI-PW enable flag; wherein the value "1" indicates that the DNI-PW is enabled; and the dni_pw_status indicates whether the occurrence occurs.
  • dni_pw_l2ve_port_id is used to indicate the L2VE_Port corresponding to the DNI-PW.
  • Step S41 In the uplink service, the primary VPWS searches for the intf_tbl table; and in step S42, determines whether the value of dni_pw_ena is "1", If yes, go to step S43; if no, go to step S5; step S43. Determine whether the value of dni_pw_status is "1", if yes, go to step S7; if no, go to step S5 .
  • the l2ve_bridge_tbl table includes flag_to_l2ve for indicating whether the L2VE_Port has been associated; wherein the value "1" indicates that the L2VE_Port has been associated; ve_port_id is used to indicate the corresponding L2VE_Port or L3VE_Port. .
  • step S31 In the downlink service, the standby VPWS searches for the l2ve_bridge_tbl table; step S32. determines whether the value of flag_to_l2ve is "1", and if so, jumps Go to step S33; if no, go to step S34; step S33. Search for the corresponding L2VE_Port according to ve_port_id, go to step S7; step S34. Find the corresponding ve_port_id L3VE_Port, go to step S6.
  • the L2VPN includes VPWS and DNI-PW.
  • the uplink service completes the pseudowire PW1:1 switching on the access device.
  • the primary VPWS and the standby VPWS each include a plurality of pseudowires.
  • the invention also provides a fast switching DNI-PW implementation system, which is applied to a virtual private line service VPWS network, the VPWS network includes a primary VPWS, an alternate VPWS, a primary aggregation node, an alternate aggregation node, and a 3-layer virtual private network.
  • L3VPN, and a dual-node interconnected pseudowire DNI-PW is provided between the primary aggregation node and the standby aggregation node.
  • the system includes an intf_tbl table addition module for adding an intf_tbl table to the primary VPWS, and the intf_tbl table is used to determine The service enters the primary VPWS, the standby VPWS or the L3VPN; the l2ve_bridge_tbl table adds a module for adding the l2ve_bridge_tbl table to the standby VPWS, and the l2ve_bridge_tbl table is used to implement the Layer 2 virtual instance interface L2VE_Port and the 3 layer virtual in the exit of the Layer 2 virtual private network L2VPN.
  • the fault type judging module is configured to determine whether a fault occurs, and if no fault occurs, the first service bridging indication signal is generated and sent to the first service.
  • Bridge indicator module if a fault occurs, determine the fault type, if the main aggregation node is powered off The second service bridging indication signal is generated and sent to the second service bridging indication module; if the main aggregation node is dialed, the third service bridging indication signal is generated and sent to the third service bridging indication module; If the path is broken, it is determined whether the service is broken.
  • a third service bridging indication signal is generated and sent to the third service bridging indication module; if not, the first service bridging indication signal is generated and sent to the a service bridging indication module;
  • a service bridging indication module is configured to: when receiving the first service bridging indication signal, indicate that the uplink service is connected to the L3VPN through the L2VE1 and the L3VE1 in the primary aggregation node; the downlink service is connected to the active VPWS through the L3VE1 and the L2VE1 in the primary aggregation node.
  • the second service bridging indication module is configured to: when receiving the second service bridging indication signal, indicate that the uplink service is bridged to the L3VPN by the L2VE1 and the L3VE1 at the standby aggregation node; the downlink service is connected to the standby VPWS by the L2VE1 and the L3VE1 bridge at the standby aggregation node;
  • the third service bridging indication module is configured to: when receiving the third service bridging indication signal, indicate that the uplink service is connected to the DNI-PW through the L2VE1 and L2VE0 bridges at the standby aggregation node, and the L3VPN is connected to the L3VPN through the L2VE0 and L3VE1 at the primary aggregation node;
  • the service is connected to the DNI-PW through the L3VE1 and L2VE0 at the primary aggregation node, and is connected to the standby aggregation node through the L2VE0 and L2VE
  • the second service bridging indication module when the second service bridging indication module receives the second service bridging indication signal, it first indicates that the uplink service completes the PW1:1 switching on the access device; the third service bridging indication module receives When the third service bridges the indication signal, it first instructs the uplink service to complete the pseudowire PW1:1 switching on the access device.
  • the present invention is based on VC switching of VPWS, and does not need to consider how many hosts are included in the VC service, that is, the workload is reduced by N times compared with the conventional method (N is the number of hosts in the VPWS service).
  • the switching operation is triggered by the BFD (Bidirectional Forwarding Detection)/OAM (Operation Administration and Maintenance) deployed on the forwarding plane, and no master participation is required. Therefore, although the path of the signaling interaction needs to be switched after the service switching, the master does not sense the process of the switching. Therefore, the present invention shields the control plane from the difference of the signaling interaction before and after the switching at the forwarding plane, and the control plane Agreement does not need to feel Know the process of switching.
  • BFD Bidirectional Forwarding Detection
  • OAM Operaation Administration and Maintenance
  • the l2ve_bridge_tbl table is provided in the present invention.
  • the L2Ve_port (L2Virtual Entity, Layer 2 virtual instance interface) of the standby VPWS is the same. Therefore, when the primary aggregation node loses power, the uplink service switching of the standby aggregation node only needs to be performed.
  • By refreshing the bridge state of the l2ve_bridge_tbl table multiple VPWSs can be associated with the DNI-PW, thereby improving the uplink switching speed.
  • Figure 1 is a schematic diagram of the DNI-PW internal implementation model
  • FIG. 2 is a flowchart of a method for implementing fast switching DNI-PW according to an embodiment of the present invention.
  • an embodiment of the present invention provides a fast switching DNI-PW implementation method, which is applied to a VPWS network, where the VPWS network includes a primary VPWS, an alternate VPWS, a primary aggregation node, and an alternate aggregation node.
  • the L3VPN L3Virtual Private Network
  • the primary VPWS and the standby VPWS each include a plurality of PWs (Pseudo Wires)
  • the DNI is provided between the primary aggregation node and the standby aggregation node.
  • PW including the following steps:
  • Step S1. Add the intf_tbl table in the primary VPWS, and add the l2ve_bridge_tbl table in the standby VPWS; wherein the intf_tbl table is used to determine that the service enters the primary VPWS, the alternate VPWS or the L3VPN, and the l2ve_bridge_tbl table is used in the L2VPN (L2Virtual Private Network, 2)
  • the L2VE_Port includes the VPWS and the DNI-PW, the L2VE_Port includes the L2VE0 and the L2VE1, and the L3VE_Port includes the L3VE1.
  • the L2VE_Port includes the VPWS and the DNI-PW.
  • the intf_tbl table includes dni_pw_ena, dni_pw_status, and dni_pw_l2ve_port_id, where dni_pw_ena is used as the DNI-PW enable flag; specifically, the value "1" indicates that the DNI-PW is enabled.
  • Dni_pw_status is used to indicate whether DNI-PW switching occurs. Specifically, the value "1" indicates that DNI-PW switching has occurred.
  • Dni_pw_l2ve_port_id is used to indicate the L2VE_Port corresponding to the DNI-PW.
  • each type of PORT (interface) + VLAN is called an interface, which is referred to as intf_tbl.
  • Each intf_tbl is associated with a VPWS or L3VPN, so the intf_tbl is determined, which determines the VPWS or L3VPN that the service is about to enter.
  • the aggregation node is configured with the bridging service. Since the VLAN is already planned when the carrier is connected to the network, the virtual interface (Ve_port) can be associated to bridge the L2VPN service and the L3VPN service.
  • the virtual interface connected to the primary VPWS is called vpws_l2ve_port_id
  • the virtual interface connected to the DNI-PW is called dni_pw_l2ve_port_id
  • the virtual interface connected to the L3VPN service is called l3ve_port_id.
  • the l2ve_bridge_tbl table includes flag_to_l2ve and ve_port_id, where flag_to_l2ve is used as a flag for whether L2VE_Port has been associated; wherein a value of "1" indicates that L2VE_Port has been associated.
  • Ve_port_id is used to indicate the corresponding L2VE_Port or L3VE_Port. Both VPWS and DNI-PW are L2VPN services, and their exits are l2ve_port_id.
  • the association between the active VPWS and the L3VPN is implemented in the working state of the active aggregation node, that is, the association between vpws_l2ve_port_id and l3ve_port_id is realized, and the association between the DNI-PW and the L3VPN is implemented in the switching state, that is, the implementation of the dni_pw_l2ve_port_id and the l3ve_port_id is implemented.
  • Association In general, the L2VPN exit is to achieve the association between l2ve_port_id and l3ve_port_id.
  • the association between the standby VPWS and the DNI-PW is implemented, that is, the association between the vpws_l2ve_port_id and the dni_pw_l2ve_port_id is implemented, and the association between the standby VPWS and the L3VPN is implemented in the switching state, that is, the vpws_l2ve_port_id and the vpws_l2ve_port_id are implemented.
  • the association of l3ve_port_id In general, it is necessary to implement l2ve_port_id and l3ve_port_id, or association with l2ve_port_id at the exit of L2VPN.
  • Step S2 It is judged whether a failure has occurred, and if so, the process goes to step S3; if not, the process goes to step S5.
  • Step S3 determining the fault type, if the main path is broken, the process goes to step S4; if the main use aggregation node is dialed, the process goes to step S7; if the main use aggregation node loses power, the jump Go to step S6; wherein the specific process of determining the fault type is:
  • Step S31 In the downlink service, the standby VPWS looks up the l2ve_bridge_tbl table.
  • Step S32 It is judged whether the value of flag_to_l2ve is "1", and if so, the process proceeds to step S33; if not, the process proceeds to step S34.
  • Step S33 Find the corresponding L2VE_Port according to ve_port_id, and jump to step S7.
  • Step S34 Find the corresponding L3VE_Port of ve_port_id, and go to step S6.
  • Step S4 determining whether the service has been broken, if not, then going to step S5; if yes, going to step S7; wherein, the specific process of determining whether the service has been broken is:
  • Step S41 In the uplink service, the primary VPWS searches for the intf_tbl table.
  • Step S42 It is judged whether the value of dni_pw_ena is "1", and if so, the process goes to step S43; if not, the process goes to step S5.
  • Step S43 It is judged whether the value of dni_pw_status is "1", and if so, the process proceeds to step S7; if not, the process proceeds to step S5.
  • Step S5. The uplink service is connected to the L3VPN through the L2VE1 and L3VE1 at the primary aggregation node; the downlink service is connected to the active VPWS through the L3VE1 and L2VE1 at the primary aggregation node; the process ends.
  • Step S6 The uplink service completes the PW1:1 switching on the access device, and is connected to the L3VPN through the L2VE1 and L3VE1 at the standby aggregation node; the downlink service is in the standby aggregation section. The point is bridged to the standby VPWS through L2VE1 and L3VE1; the process ends.
  • Step S7 The uplink service completes the PW1:1 switching on the access device, and connects to the DNI-PW through the L2VE1 and L2VE0 bridges at the standby aggregation node, and the L3VPN to the L3VPN through the L2VE0 and L3VE1 at the primary aggregation node; the downlink service is in the primary aggregation node.
  • the L3VE1 and L2VE0 bridges are connected to the DNI-PW, and the standby aggregation node is bridged to the standby aggregation node through L2VE0 and L2VE1; the process ends.
  • the embodiment of the present invention further provides a fast switching DNI-PW implementation system, which is applied to a virtual private line service VPWS network, where the VPWS network includes a primary VPWS, an alternate VPWS, a primary aggregation node, an alternate aggregation node, and a 3-layer virtual network.
  • the VPWS network includes a primary VPWS, an alternate VPWS, a primary aggregation node, an alternate aggregation node, and a 3-layer virtual network.
  • a dedicated network L3VPN, and a dual-node interconnected pseudowire DNI-PW is provided between the primary aggregation node and the standby aggregation node, and the system includes:
  • the intf_tbl table adds modules for adding the intf_tbl table to the primary VPWS.
  • the intf_tbl table is used to determine whether the service enters the primary VPWS, alternate VPWS, or L3VPN.
  • the l2ve_bridge_tbl table adds a module for adding a l2ve_bridge_tbl table to the standby VPWS, and the l2ve_bridge_tbl table is used to associate the Layer 2 virtual instance interface L2VE_Port with the Layer 3 virtual instance interface L3VE_Port at the exit of the Layer 2 virtual private network L2VPN, where the L2VE_Port includes L2VE0 And L2VE1, L3VE_Port includes L3VE1.
  • the fault type judging module is configured to determine whether a fault occurs. If no fault occurs, the first service bridging indication signal is generated and sent to the first service bridging indication module; if a fault occurs, the fault type is determined, if the fault is used for the main use. If the node is powered off, the second service bridging indication signal is generated and sent to the second service bridging indication module. If the main aggregation node is dialed, the third service bridging indication signal is generated and sent to the third service bridging indication module.
  • a third service bridging indication signal is generated and sent to the third service bridging indication module; if not, then A first service bridging indication signal is generated and sent to the first service bridging indication module.
  • the first service bridging indication module is configured to: when receiving the first service bridging indication signal, indicate that the uplink service is connected to the L3VPN through the L2VE1 and the L3VE1 in the primary aggregation node; the downlink service is connected to the main service through the L3VE1 and L2VE1 in the primary aggregation node. VPWS.
  • the second service bridging indication module is configured to: when receiving the second service bridging indication signal, first indicate that the uplink service completes the pseudowire PW1:1 switching on the access device, and then instructs the uplink service to be bridged to the L3VPN through the L2VE1 and L3VE1 at the standby aggregation node.
  • the downlink service is bridged to the standby VPWS through the L2VE1 and L3VE1 at the alternate aggregation node.
  • the third service bridging indication module is configured to: when receiving the third service bridging indication signal, first indicate that the uplink service completes the pseudowire PW1:1 switching on the access device, and then instructs the uplink service to connect to the DNI through the L2VE1 and L2VE0 bridges at the standby aggregation node.
  • the L3VPN is connected to the L3VPN through the L2VE0 and L3VE1 at the primary aggregation node;
  • the downlink service is connected to the DNI-PW through the L3VE1 and L2VE0 at the primary aggregation node, and the standby aggregation node is connected to the standby aggregation node through the L2VE0 and L2VE1 at the standby aggregation node.

Landscapes

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

Abstract

本发明公开了一种快速倒换的DNI-PW实现方法及系统，涉及通信领域，该方法包括：在主用VPWS中添加intf_tbl表，在备用VPWS中添加l2ve_bridge_tbl表。若无故障：则上行业务在主用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE1桥接到主用VPWS。若为掉电故障：则上行业务在备用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在备用汇聚节点通过L2VE1和L3VE1桥接到备用VPWS。若为拔盘或业务断纤故障，则上行业务在备用汇聚节点通过L2VE1和L2VE0桥接到DNI-PW；下行业务在在主用汇聚节点通过L3VE1和L2VE0桥接到DNI-PW，在备用汇聚节点通过L2VE0和L2VE1桥接到备用VPWS。本发明减少了倒换发生时软件刷新的工作量，提高了业务上下行倒换速度。

Description

一种快速倒换的DNI-PW实现方法及系统 技术领域
本发明涉及通信技术领域，具体来讲是一种快速倒换的DNI-PW(Dual Node Interconnection Pseudo Wire，双节点互联伪线)实现方法及系统。
背景技术
随着互联网的兴起和应用走向多元化，互联网越来越深刻地改变着人们的学习、工作以及生活方式。为支持互联网的发展，电信运营商的网络规模越来越大，结构也越来越复杂，同时对网络的稳定性提出了更高的要求。
运营商网络一般分为骨干网和城域网两层结构，骨干网又可分为三个层次：核心层、汇聚层、接入层。两端汇聚设备之间会设置DNI-PW，以实现用1条VPWS(Virtual Pseudo Wire Service，虚拟专用线路业务)(DNI-PW)保护N条VPWS的某几条或者全部。
当运营商网络出现接入环主用路径断纤、主用汇聚节点拔盘、主用汇聚节点掉电等故障时，必须及时对故障进行检测，快速完成流量的切换，从而保证业务能够快速得到修复，然而传统的方法存在几下几点缺陷：
1、下行倒换需要刷新每条VC(Virtual Circuit，虚拟电路)中的N个主机状态导致倒换时间长。
2、控制平面需要感知业务倒换状态而增加软件复杂度。
3、主用节点掉电时，上行倒换需要逐条刷新业务桥接状态导致 倒换时间长。
因此亟需一种实现DNI-PW快速倒换的方法。
发明内容
针对现有技术中存在的缺陷，本发明的目的在于提供一种快速倒换的DNI-PW实现方法及系统，本发明减少了工作量；在转发层面为控制平面屏蔽了信令交互在倒换前后的差异，控制平面的协议不需要感知倒换的过程；提高了上行倒换速度。
为达到以上目的，本发明采取的技术方案是：一种快速倒换的DNI-PW实现方法，应用于虚拟专用线路业务VPWS网络，所述VPWS网络包括主用VPWS、备用VPWS、主用汇聚节点、备用汇聚节点以及3层虚拟专用网络L3VPN，且主用汇聚节点与备用汇聚节点之间设有双节点互联伪线DNI-PW，包括以下步骤：步骤S1.在主用VPWS中添加intf_tbl表，在备用VPWS中添加l2ve_bridge_tbl表；其中，intf_tbl表用于确定业务进入主用VPWS、备用VPWS或者L3VPN，l2ve_bridge_tbl表用于在2层虚拟专用网络L2VPN的出口实现2层虚实例接口L2VE_Port与3层虚实例接口L3VE_Port的关联，所述L2VE_Port包括L2VE0和L2VE1，L3VE_Port包括L3VE1；步骤S2.判断是否出现故障，若是，则跳转至步骤S3；若否，则跳转至步骤S5；步骤S3.判断故障类型，若为主用路径断纤，则跳转至步骤S4；若为主用汇聚节点拔盘，则跳转至步骤S7；若为主用汇聚节点掉电，则跳转至步骤S6；步骤S4.判断业务是否经过断纤，若是，则跳转至步骤S7；若否，则跳转至步骤S5；步骤S5.上行业务在主用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE1桥接到主用VPWS；结束流程；步骤S6.上行业务在备用汇聚节点通过L2VE1和L3VE1桥接到 L3VPN；下行业务在备用汇聚节点通过L2VE1和L3VE1桥接到备用VPWS；结束流程；步骤S7.上行业务在备用汇聚节点通过L2VE1和L2VE0桥接到DNI-PW，在主用汇聚节点通过L2VE0和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE0桥接到DNI-PW，在备用汇聚节点通过L2VE0和L2VE1桥接到备用汇聚节点；结束流程。
在上述技术方案的基础上，步骤S1中，所述intf_tbl表包括dni_pw_ena，用于作为DNI-PW使能标志；其中，数值“1”表示DNI-PW已使能；dni_pw_status，用于指示是否发生DNI-PW倒换；其中，数值“1”表示DNI-PW倒换已发生；dni_pw_l2ve_port_id，用于指示DNI-PW对应的L2VE_Port。
在上述技术方案的基础上，步骤S4中判断业务是否经过断纤的具体流程为：步骤S41.在上行业务中，主用VPWS查找intf_tbl表；步骤S42.判断dni_pw_ena的值是否为“1”，若是，则跳转至步骤S43；若否，则跳转至步骤S5；步骤S43.判断dni_pw_status的值是否为“1”，若是，则跳转至步骤S7；若否，则跳转至步骤S5。
在上述技术方案的基础上，步骤S1中，所述l2ve_bridge_tbl表包括flag_to_l2ve，用于作为是否已关联L2VE_Port的标志；其中，数值“1”表示已关联L2VE_Port；ve_port_id，用于指示相应的L2VE_Port或者L3VE_Port。
在上述技术方案的基础上，步骤S3中判断故障类型的具体流程为：步骤S31.在下行业务中，备用VPWS查找l2ve_bridge_tbl表；步骤S32.判断flag_to_l2ve的值是否为“1”，若是，则跳转至步骤S33；若否，则跳转至步骤S34；步骤S33.根据ve_port_id查找相应的L2VE_Port，跳转至步骤S7；步骤S34.查找ve_port_id相应的 L3VE_Port，跳转至步骤S6。
在上述技术方案的基础上，步骤S1中，所述L2VPN包括VPWS和DNI-PW。
在上述技术方案的基础上，在步骤S6和步骤S7中首先执行以下步骤：上行业务在接入设备完成伪线PW1:1倒换。
在上述技术方案的基础上，所述主用VPWS和备用VPWS均包括多条伪线。
本发明还提供一种快速倒换的DNI-PW实现系统，应用于虚拟专用线路业务VPWS网络，所述VPWS网络包括主用VPWS、备用VPWS、主用汇聚节点、备用汇聚节点以及3层虚拟专用网络L3VPN，且主用汇聚节点与备用汇聚节点之间设有双节点互联伪线DNI-PW，所述系统包括：intf_tbl表添加模块，用于在主用VPWS中添加intf_tbl表，intf_tbl表用于确定业务进入主用VPWS、备用VPWS或者L3VPN；l2ve_bridge_tbl表添加模块，用于在备用VPWS中添加l2ve_bridge_tbl表，l2ve_bridge_tbl表用于在2层虚拟专用网络L2VPN的出口实现2层虚实例接口L2VE_Port与3层虚实例接口L3VE_Port的关联，所述L2VE_Port包括L2VE0和L2VE1，L3VE_Port包括L3VE1；故障类型判断模块，用于判断是否出现故障，若没有出现故障，则生成第一业务桥接指示信号，并发送到第一业务桥接指示模块；若出现故障，则判断故障类型，若为主用汇聚节点掉电，则生成第二业务桥接指示信号，并发送到第二业务桥接指示模块；若为主用汇聚节点拔盘，则生成第三业务桥接指示信号，并发送到第三业务桥接指示模块；若为主用路径断纤，则判断业务是否经过断纤，若是，则生成第三业务桥接指示信号，并发送到第三业务桥接指示模块；若否，则生成第一业务桥接指示信号，并发送到第一业务桥接指示模块；第 一业务桥接指示模块，用于收到第一业务桥接指示信号时，指示上行业务在主用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE1桥接到主用VPWS；第二业务桥接指示模块，用于收到第二业务桥接指示信号时，指示上行业务在备用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在备用汇聚节点通过L2VE1和L3VE1桥接到备用VPWS；第三业务桥接指示模块，用于收到第三业务桥接指示信号时，指示上行业务在备用汇聚节点通过L2VE1和L2VE0桥接到DNI-PW，在主用汇聚节点通过L2VE0和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE0桥接到DNI-PW，在备用汇聚节点通过L2VE0和L2VE1桥接到备用汇聚节点。
在上述技术方案的基础上，所述第二业务桥接指示模块收到第二业务桥接指示信号时，首先指示上行业务在接入设备完成PW1:1倒换；所述第三业务桥接指示模块收到第三业务桥接指示信号时，首先指示上行业务在接入设备完成伪线PW1:1倒换。
本发明的有益效果在于：
1、本发明是基于VPWS的VC来倒换，不需要考虑该VC业务中包含多少个主机，即工作量相对于传统方法减少了N倍(N是该VPWS业务中的主机数)。
2、本发明中由于倒换动作通过部署在转发面的BFD(Bidirectional Forwarding Detection，双向转发检测机制)/OAM(Operation Administration and Maintenance，操作管理维护)来触发，并不需要主控参与。因此，尽管业务倒换后信令交互的路径也需要随之倒换，但主控并不感知倒换的过程，因此，本发明在转发层面为控制平面屏蔽了信令交互在倒换前后的差异，控制平面的协议不需要感 知倒换的过程。
3、本发明中设置有l2ve_bridge_tbl表，由于多个备用VPWS的出口L2Ve_port(L2Virtual Entity，2层虚实例接口)相同，因此，当主用汇聚节点掉电故障时，备用汇聚节点的上行业务倒换只需刷新l2ve_bridge_tbl表的桥接状态即可实现多条VPWS与DNI-PW的关联，从而提高了上行倒换速度。
附图说明
图1为DNI-PW内部实现模型示意图；
图2为本发明实施例中快速倒换的DNI-PW实现方法的流程图。
具体实施方式
以下结合附图及实施例对本发明作进一步详细说明。
参见图1及图2所示，本发明实施例提供一种快速倒换的DNI-PW实现方法，应用于VPWS网络，所述VPWS网络包括主用VPWS、备用VPWS、主用汇聚节点、备用汇聚节点以及L3VPN(L3Virtual Private Network，3层虚拟专用网络)，所述主用VPWS和备用VPWS均包括多条PW(Pseudo Wire，伪线)，且主用汇聚节点与备用汇聚节点之间设有DNI-PW，包括以下步骤：
步骤S1.在主用VPWS中添加intf_tbl表，在备用VPWS中添加l2ve_bridge_tbl表；其中，intf_tbl表用于确定业务进入主用VPWS、备用VPWS或者L3VPN，l2ve_bridge_tbl表用于在L2VPN(L2Virtual Private Network，2层虚拟专用网络)的出口实现L2VE_Port与L3VE_Port(L3Virtual Entity，3层虚实例接口)的关联，其中，所述L2VPN包括VPWS和DNI-PW，所述L2VE_Port包括L2VE0和L2VE1，L3VE_Port包括L3VE1。
优选的，所述intf_tbl表包括dni_pw_ena、dni_pw_status和dni_pw_l2ve_port_id，其中dni_pw_ena用于作为DNI-PW使能标志；具体的，通过数值“1”表示DNI-PW已使能。dni_pw_status用于指示是否发生DNI-PW倒换；具体的，通过数值“1”表示DNI-PW倒换已发生。dni_pw_l2ve_port_id用于指示DNI-PW对应的L2VE_Port。每一种PORT(接口)+VLAN(Virtual Local Area Network，虚拟局域网)的组合称为一条interface，本文简称为intf_tbl。每一条intf_tbl关联一个VPWS或者L3VPN，所以确定了intf_tbl，也就确定了业务即将进入的VPWS或者L3VPN。汇聚节点配置桥接业务，由于VLAN在运营商组网时已经规划好了，所以只需关联虚接口(Ve_port)即可完成L2VPN业务与L3VPN业务的桥接。其中与主用VPWS相连的虚接口称为vpws_l2ve_port_id，与DNI-PW相连的虚接口称为dni_pw_l2ve_port_id，与L3VPN业务相连的虚接口称为l3ve_port_id。
所述l2ve_bridge_tbl表包括flag_to_l2ve和ve_port_id，其中flag_to_l2ve用于作为是否已关联L2VE_Port的标志；其中，数值“1”表示已关联L2VE_Port。ve_port_id用于指示相应的L2VE_Port或者L3VE_Port。VPWS和DNI-PW都是L2VPN业务，其出口都是l2ve_port_id。在上行业务中，在主用汇聚节点的工作状态要实现主用VPWS与L3VPN的关联，即实现vpws_l2ve_port_id和l3ve_port_id的关联，在倒换状态要实现DNI-PW与L3VPN的关联，即实现dni_pw_l2ve_port_id和l3ve_port_id的关联。总的来说，就是在L2VPN的出口要实现l2ve_port_id与l3ve_port_id的关联。在备用汇聚节点的工作状态要实现备用VPWS与DNI-PW的关联，即实现vpws_l2ve_port_id和dni_pw_l2ve_port_id的关联，在倒换状态要实现备用VPWS与L3VPN的关联，即实现vpws_l2ve_port_id和 l3ve_port_id的关联。总的来说，就是在L2VPN的出口要实现l2ve_port_id与l3ve_port_id、或者与l2ve_port_id的关联。
步骤S2.判断是否出现故障，若是，则跳转至步骤S3；若否，则跳转至步骤S5。
步骤S3.判断故障类型，若为主用路径断纤，则跳转至步骤S4；若为主用汇聚节点拔盘，则跳转至步骤S7；若为主用汇聚节点掉电，则跳转至步骤S6；其中，判断故障类型的具体流程为：
步骤S31.在下行业务中，备用VPWS查找l2ve_bridge_tbl表。
步骤S32.判断flag_to_l2ve的值是否为“1”，若是，则跳转至步骤S33；若否，则跳转至步骤S34。
步骤S33.根据ve_port_id查找相应的L2VE_Port，跳转至步骤S7。
步骤S34.查找ve_port_id相应的L3VE_Port，跳转至步骤S6。
步骤S4.判断业务是否经过断纤，若否，则跳转至步骤S5；若是，则跳转至步骤S7；其中，判断业务是否经过断纤的具体流程为：
步骤S41.在上行业务中，主用VPWS查找intf_tbl表。
步骤S42.判断dni_pw_ena的值是否为“1”，若是，则跳转至步骤S43；若否，则跳转至步骤S5。
步骤S43.判断dni_pw_status的值是否为“1”，若是，则跳转至步骤S7；若否，则跳转至步骤S5。
步骤S5.上行业务在主用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE1桥接到主用VPWS；结束流程。
步骤S6.上行业务在接入设备完成PW1:1倒换，并在备用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在备用汇聚节 点通过L2VE1和L3VE1桥接到备用VPWS；结束流程。
步骤S7.上行业务在接入设备完成PW1:1倒换，并在备用汇聚节点通过L2VE1和L2VE0桥接到DNI-PW，在主用汇聚节点通过L2VE0和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE0桥接到DNI-PW，在备用汇聚节点通过L2VE0和L2VE1桥接到备用汇聚节点；结束流程。
本发明实施例还提供一种快速倒换的DNI-PW实现系统，应用于虚拟专用线路业务VPWS网络，所述VPWS网络包括主用VPWS、备用VPWS、主用汇聚节点、备用汇聚节点以及3层虚拟专用网络L3VPN，且主用汇聚节点与备用汇聚节点之间设有双节点互联伪线DNI-PW，所述系统包括：
intf_tbl表添加模块，用于在主用VPWS中添加intf_tbl表，intf_tbl表用于确定业务进入主用VPWS、备用VPWS或者L3VPN。
l2ve_bridge_tbl表添加模块，用于在备用VPWS中添加l2ve_bridge_tbl表，l2ve_bridge_tbl表用于在2层虚拟专用网络L2VPN的出口实现2层虚实例接口L2VE_Port与3层虚实例接口L3VE_Port的关联，所述L2VE_Port包括L2VE0和L2VE1，L3VE_Port包括L3VE1。
故障类型判断模块，用于判断是否出现故障，若没有出现故障，则生成第一业务桥接指示信号，并发送到第一业务桥接指示模块；若出现故障，则判断故障类型，若为主用汇聚节点掉电，则生成第二业务桥接指示信号，并发送到第二业务桥接指示模块；若为主用汇聚节点拔盘，则生成第三业务桥接指示信号，并发送到第三业务桥接指示模块；若为主用路径断纤，则判断业务是否经过断纤，若是，则生成第三业务桥接指示信号，并发送到第三业务桥接指示模块；若否，则 生成第一业务桥接指示信号，并发送到第一业务桥接指示模块。
第一业务桥接指示模块，用于收到第一业务桥接指示信号时，指示上行业务在主用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE1桥接到主用VPWS。
第二业务桥接指示模块，用于收到第二业务桥接指示信号时，首先指示上行业务在接入设备完成伪线PW1:1倒换，然后指示上行业务在备用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在备用汇聚节点通过L2VE1和L3VE1桥接到备用VPWS。
第三业务桥接指示模块，用于收到第三业务桥接指示信号时，首先指示上行业务在接入设备完成伪线PW1:1倒换，然后指示上行业务在备用汇聚节点通过L2VE1和L2VE0桥接到DNI-PW，在主用汇聚节点通过L2VE0和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE0桥接到DNI-PW，在备用汇聚节点通过L2VE0和L2VE1桥接到备用汇聚节点。
本发明不局限于上述实施方式，对于本技术领域的普通技术人员来说，在不脱离本发明原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也视为本发明的保护范围之内。本说明书中未作详细描述的内容属于本领域专业技术人员公知的现有技术。

Claims (10)

  1. 一种快速倒换的DNI-PW实现方法，应用于虚拟专用线路业务VPWS网络，所述VPWS网络包括主用VPWS、备用VPWS、主用汇聚节点、备用汇聚节点以及3层虚拟专用网络L3VPN，且主用汇聚节点与备用汇聚节点之间设有双节点互联伪线DNI-PW，其特征在于，包括以下步骤：
    步骤S1.在主用VPWS中添加intf_tbl表，在备用VPWS中添加l2ve_bridge_tbl表；其中，intf_tbl表用于确定业务进入主用VPWS、备用VPWS或者L3VPN，l2ve_bridge_tbl表用于在2层虚拟专用网络L2VPN的出口实现2层虚实例接口L2VE_Port与3层虚实例接口L3VE_Port的关联，所述L2VE_Port包括L2VE0和L2VE1，L3VE_Port包括L3VE1；
    步骤S2.判断是否出现故障，若是，则跳转至步骤S3；若否，则跳转至步骤S5；
    步骤S3.判断故障类型，若为主用路径断纤，则跳转至步骤S4；若为主用汇聚节点拔盘，则跳转至步骤S7；若为主用汇聚节点掉电，则跳转至步骤S6；
    步骤S4.判断业务是否经过断纤，若是，则跳转至步骤S7；若否，则跳转至步骤S5；
    步骤S5.上行业务在主用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE1桥接到主用VPWS；结束流程；
    步骤S6.上行业务在备用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在备用汇聚节点通过L2VE1和L3VE1桥接到备用VPWS；结束流程；
    步骤S7.上行业务在备用汇聚节点通过L2VE1和L2VE0桥接到DNI-PW，在主用汇聚节点通过L2VE0和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE0桥接到DNI-PW，在备用汇聚节点通过L2VE0和L2VE1桥接到备用汇聚节点；结束流程。
  2. 如权利要求1所述的快速倒换的DNI-PW实现方法，其特征在于：步骤S1中，所述intf_tbl表包括
    dni_pw_ena，用于作为DNI-PW使能标志；其中，数值“1”表示DNI-PW已使能；
    dni_pw_status，用于指示是否发生DNI-PW倒换；其中，数值“1”表示DNI-PW倒换已发生；
    dni_pw_l2ve_port_id，用于指示DNI-PW对应的L2VE_Port。
  3. 如权利要求2所述的快速倒换的DNI-PW实现方法，其特征在于：步骤S4中判断业务是否经过断纤的具体流程为：
    步骤S41.在上行业务中，主用VPWS查找intf_tbl表；
    步骤S42.判断dni_pw_ena的值是否为“1”，若是，则跳转至步骤S43；若否，则跳转至步骤S5；
    步骤S43.判断dni_pw_status的值是否为“1”，若是，则跳转至步骤S7；若否，则跳转至步骤S5。
  4. 如权利要求1所述的快速倒换的DNI-PW实现方法，其特征在于：步骤S1中，所述l2ve_bridge_tbl表包括
    flag_to_l2ve，用于作为是否已关联L2VE_Port的标志；其中，数值“1”表示已关联L2VE_Port；
    ve_port_id，用于指示相应的L2VE_Port或者L3VE_Port。
  5. 如权利要求4所述的快速倒换的DNI-PW实现方法，其特征在于：步骤S3中判断故障类型的具体流程为：
    步骤S31.在下行业务中，备用VPWS查找l2ve_bridge_tbl表；
    步骤S32.判断flag_to_l2ve的值是否为“1”，若是，则跳转至步骤S33；若否，则跳转至步骤S34；
    步骤S33.根据ve_port_id查找相应的L2VE_Port，跳转至步骤S7；
    步骤S34.查找ve_port_id相应的L3VE_Port，跳转至步骤S6。
  6. 如权利要求1至5中任一项所述的快速倒换的DNI-PW实现方法，其特征在于：步骤S1中，所述L2VPN包括VPWS和DNI-PW。
  7. 如权利要求1至5中任一项所述的快速倒换的DNI-PW实现方法，其特征在于，在步骤S6和步骤S7中首先执行以下步骤：上行业务在接入设备完成伪线PW1:1倒换。
  8. 如权利要求1至5中任一项所述的快速倒换的DNI-PW实现方法，其特征在于：所述主用VPWS和备用VPWS均包括多条伪线。
  9. 一种快速倒换的DNI-PW实现系统，应用于虚拟专用线路业务VPWS网络，所述VPWS网络包括主用VPWS、备用VPWS、主用汇聚节点、备用汇聚节点以及3层虚拟专用网络L3VPN，且主用汇聚节点与备用汇聚节点之间设有双节点互联伪线DNI-PW，其特征在于，所述系统包括：
    intf_tbl表添加模块，用于在主用VPWS中添加intf_tbl表，intf_tbl表用于确定业务进入主用VPWS、备用VPWS或者L3VPN；
    l2ve_bridge_tbl表添加模块，用于在备用VPWS中添加l2ve_bridge_tbl表，l2ve_bridge_tbl表用于在2层虚拟专用网络L2VPN的出口实现2层虚实例接口L2VE_Port与3层虚实例接口L3VE_Port的关联，所述L2VE_Port包括L2VE0和L2VE1，L3VE_Port包括L3VE1；
    故障类型判断模块，用于判断是否出现故障，若没有出现故障，则生成第一业务桥接指示信号，并发送到第一业务桥接指示模块；
    若出现故障，则判断故障类型，若为主用汇聚节点掉电，则生成第二业务桥接指示信号，并发送到第二业务桥接指示模块；
    若为主用汇聚节点拔盘，则生成第三业务桥接指示信号，并发送到第三业务桥接指示模块；
    若为主用路径断纤，则判断业务是否经过断纤，若是，则生成第三业务桥接指示信号，并发送到第三业务桥接指示模块；若否，则生成第一业务桥接指示信号，并发送到第一业务桥接指示模块；
    第一业务桥接指示模块，用于收到第一业务桥接指示信号时，指示上行业务在主用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE1桥接到主用VPWS；
    第二业务桥接指示模块，用于收到第二业务桥接指示信号时，指示上行业务在备用汇聚节点通过L2VE1和L3VE1桥接到L3VPN；下行业务在备用汇聚节点通过L2VE1和L3VE1桥接到备用VPWS；
    第三业务桥接指示模块，用于收到第三业务桥接指示信号时，指示上行业务在备用汇聚节点通过L2VE1和L2VE0桥接到DNI-PW，在主用汇聚节点通过L2VE0和L3VE1桥接到L3VPN；下行业务在主用汇聚节点通过L3VE1和L2VE0桥接到DNI-PW，在备用汇聚节点通过L2VE0和L2VE1桥接到备用汇聚节点。
  10. 如权利要求9所述的快速倒换的DNI-PW实现系统，其特征在于，所述第二业务桥接指示模块收到第二业务桥接指示信号时，首先指示上行业务在接入设备完成PW1:1倒换；所述第三业务桥接指示模块收到第三业务桥接指示信号时，首先指示上行业务在接入设备完成伪线PW1:1倒换。
PCT/CN2015/093679 2015-04-08 2015-11-03 一种快速倒换的dni-pw实现方法及系统 Ceased WO2016161802A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510161616.1 2015-04-08
CN201510161616.1A CN104753722B (zh) 2015-04-08 2015-04-08 一种快速倒换的dni‑pw实现方法及系统

Publications (1)

Publication Number Publication Date
WO2016161802A1 true WO2016161802A1 (zh) 2016-10-13

Family

ID=53592870

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/093679 Ceased WO2016161802A1 (zh) 2015-04-08 2015-11-03 一种快速倒换的dni-pw实现方法及系统

Country Status (2)

Country Link
CN (1) CN104753722B (zh)
WO (1) WO2016161802A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111683307A (zh) * 2020-05-22 2020-09-18 烽火通信科技股份有限公司 一种olt多级交换下业务接入的方法及系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104753722B (zh) * 2015-04-08 2018-01-02 烽火通信科技股份有限公司 一种快速倒换的dni‑pw实现方法及系统
CN110166286A (zh) * 2019-04-30 2019-08-23 中时讯通信建设有限公司 一种ip ran网络系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100118711A1 (en) * 2008-11-07 2010-05-13 Alcatel Lucent Tools that facilitate diagnostics for mobile backhaul networks
CN102710523A (zh) * 2012-06-14 2012-10-03 中兴通讯股份有限公司 路径的切换方法及系统
CN104270231A (zh) * 2014-09-05 2015-01-07 烽火通信科技股份有限公司 一种实现双节点互联伪线的系统及方法
CN104753722A (zh) * 2015-04-08 2015-07-01 烽火通信科技股份有限公司 一种快速倒换的dni-pw实现方法及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100696196B1 (ko) * 2005-12-09 2007-03-20 한국전자통신연구원 Ｓｄｈ／ｓｏｎｅｔ를 이용한 ｖｐｗｓ망에서의유지보수신호 전파 방법
CN102035681B (zh) * 2010-12-17 2015-07-22 中兴通讯股份有限公司 虚拟专用网络的链路保护方法和系统
CN102148713B (zh) * 2011-05-11 2013-12-11 烽火通信科技股份有限公司 一种适用于大容量ptn设备的线性保护倒换方法
CN102325037B (zh) * 2011-05-25 2016-01-20 中兴通讯股份有限公司 一种伪线双归网络的切换方法、系统和双归属运营商设备
CN103490969B (zh) * 2013-09-17 2016-07-06 烽火通信科技股份有限公司 实现vpws冗余保护快速收敛的系统及方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100118711A1 (en) * 2008-11-07 2010-05-13 Alcatel Lucent Tools that facilitate diagnostics for mobile backhaul networks
CN102710523A (zh) * 2012-06-14 2012-10-03 中兴通讯股份有限公司 路径的切换方法及系统
CN104270231A (zh) * 2014-09-05 2015-01-07 烽火通信科技股份有限公司 一种实现双节点互联伪线的系统及方法
CN104753722A (zh) * 2015-04-08 2015-07-01 烽火通信科技股份有限公司 一种快速倒换的dni-pw实现方法及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111683307A (zh) * 2020-05-22 2020-09-18 烽火通信科技股份有限公司 一种olt多级交换下业务接入的方法及系统
CN111683307B (zh) * 2020-05-22 2022-05-20 烽火通信科技股份有限公司 一种olt多级交换下业务接入的方法及系统

Also Published As

Publication number Publication date
CN104753722A (zh) 2015-07-01
CN104753722B (zh) 2018-01-02

Similar Documents

Publication Publication Date Title
CN101902353B (zh) 分组网络的保护方法
US8681605B2 (en) Method and apparatus for using G.8031 extensions to enable coexistence of G.8031-based protection and LAG-like loadsharing for ethernet paths
EP2528272A1 (en) Dual-attached protection switching method based on vpls and system thereof
WO2011120301A1 (zh) 双归保护倒换方法、装置和系统
EP2204947A1 (en) Method and node device of ethernet failure detecting and converging
JP2011518506A5 (zh)
CN102377607B (zh) 用于二层虚拟专用网络的数据传输方法和装置
CN102264088B (zh) 伪线保护倒换实现方法及装置
EP2633649A1 (en) Dual-homing for ethernet line services
CN103607317A (zh) 二层环路检测方法和装置及通信系统
CN103581025B (zh) 路由信息处理方法、设备及系统
CN104618150B (zh) 一种ptn二层转三层业务场景下的业务配置方法及系统
CN101834773A (zh) 一种虚拟专用局域网业务的保护方法和系统
CN101789879B (zh) 一种关联链路的动态维护方法及装置
CN103457817B (zh) 一种pw+l3vpn的保护方法和系统
EP3182645B1 (en) Network protection switching method, network device and storage medium
WO2016034127A1 (zh) 一种实现双节点互联伪线的系统及方法
CN102468977B (zh) 分组传送网的保护方法和装置
CN102932247A (zh) 一种vpn快速重路由方法、装置及提供商边缘设备
WO2016086548A1 (zh) 一种伪线双归保护切换系统、方法和装置
WO2016161802A1 (zh) 一种快速倒换的dni-pw实现方法及系统
WO2015039456A1 (zh) 网络数据自环回的控制方法及装置
CN103916270B (zh) 基于ptn的实现链路状态穿通功能的系统、方法及装置
CN101237343A (zh) 故障时快速切换的方法及快速切换系统
CN102025561A (zh) 一种以太环网中刷新mac的方法及系统

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: DZP2017000041

Country of ref document: DZ

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15888352

Country of ref document: EP

Kind code of ref document: A1

WWG Wipo information: grant in national office

Ref document number: DZP2017000041

Country of ref document: DZ