WO2012100571A1 - Procédé et système de gestion centralisée pour une pluralité de tunnels ayant le même chemin - Google Patents

Procédé et système de gestion centralisée pour une pluralité de tunnels ayant le même chemin Download PDF

Info

Publication number
WO2012100571A1
WO2012100571A1 PCT/CN2011/081291 CN2011081291W WO2012100571A1 WO 2012100571 A1 WO2012100571 A1 WO 2012100571A1 CN 2011081291 W CN2011081291 W CN 2011081291W WO 2012100571 A1 WO2012100571 A1 WO 2012100571A1
Authority
WO
WIPO (PCT)
Prior art keywords
tunnel
cluster
tunnel cluster
management entity
detection
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/081291
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 WO2012100571A1 publication Critical patent/WO2012100571A1/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
    • 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/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
    • H04L41/0618—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time based on the physical or logical position
    • 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/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Definitions

  • the present invention relates to a multi-protocol label switching/Internet Protocol (MPLS/IP) technology in network communication, and more particularly to a method and system for centralized management of multiple tunnels of the same path.
  • MPLS/IP multi-protocol label switching/Internet Protocol
  • T-MPLS Transmission-Multi Protocol Label Switching
  • T-MPLS technology is a Packet Transport Network (PTN) transmission technology standardized by the International Telecommunication Union (ITU-T). It is characterized by a connection-oriented packet transmission technology, and its data forwarding plane is multi-protocol.
  • MPLS Multi Protocol Label Switching
  • MPLS Multi Protocol Label Switching
  • the function is to use the Automatically Switched Optical Network/Generalized Multiprotocol Label Switching (ASON/GMPLS) as its control plane.
  • ASON/GMPLS Automatically Switched Optical Network/Generalized Multiprotocol Label Switching
  • the "connection-oriented" feature means that T-MPLS technology can provide telecom carrier-grade services that require traditional delivery. Net equivalent OAM function. Therefore, OAM function becomes an indispensable key link of T-MPLS technology.
  • OAM is configured based on the Maintenance Entity Group (MEG), that is, a T-MPLS port is deployed on a tunnel.
  • MAG Maintenance Entity Group
  • Such a deployment can monitor the status of the tunnel, so that the user can be notified in time when the tunnel is abnormal, for example: printing an alarm on the user configuration interface and the network management interface; taking corresponding measures to detect, diagnose, and Positioning and fault recovery, etc., for example: Tunnel for protection switching or tunnel advertising upper layer application.
  • the T-MPLS mechanism has the following characteristics: 1. Each ⁇ detection management entity needs to specify T-MPLS connection support; 2. Support client layer/service layer ⁇ relationship, and need corresponding configuration mode at each level; The service provider shall be able to automatically detect and notify the faults related to the maintenance entity; 4. The corresponding measures must be taken when the fault occurs.
  • the main object of the present invention is to provide a method and system for centralized management of multiple tunnels of the same path, which can solve the same function of the MEG on the same path, and in the case of network failure, redundant message transmission avoids each The MEG prints the same warning.
  • the present invention provides a method for centralized management of multiple tunnels of the same path, and the method includes:
  • the management entity group When the physical link is abnormal, the management entity group notifies the tunnel cluster of the current detection status, and the tunnel group completes batch processing according to the detection status.
  • the method further includes: when a new tunnel is added to the tunnel cluster, determining whether the existing tunnel information in the tunnel cluster matches, and if yes, adding, otherwise the adding fails.
  • the tunnel cluster includes: a tunnel cluster number, a tunnel cluster type, a tunnel cluster management entity binding interface, a tunnel number statistics, a tunnel cluster state, and a tunnel information database.
  • the tunnel cluster type includes: a tunnel cluster detected by the layer, and a tunnel cluster detected by the lower layer.
  • the batch processing includes: the tunnel cluster notifies the tunnel included in the tunnel information database one by one, switches the tunnel with protection, and prints an alarm on the device.
  • the present invention also provides a system for centralized management of multiple tunnels of the same path, where the system includes: a tunnel endpoint, a detection management entity group;
  • the tunnel endpoint is configured to create a tunnel cluster for multiple tunnels of the same path, and the tunnel cluster on the tunnel endpoint completes batch processing according to the received detection state;
  • the detection management entity group is configured to bind the tunnel cluster. When the physical link is abnormal, the management entity group sends the current detection status to the tunnel endpoint.
  • the tunnel endpoint is further configured to: when the new tunnel needs to join the tunnel cluster, determine whether the existing tunnel information in the newly added tunnel and the tunnel cluster match, and if yes, join, otherwise add failed.
  • the tunnel cluster in the tunnel endpoint includes: a tunnel cluster number, a tunnel cluster type,
  • the tunnel cluster management entity binds the interface, the number of tunnels, the tunnel cluster status, and the tunnel information database.
  • the tunnel cluster type includes: a tunnel cluster detected by the layer, and a tunnel cluster detected by the lower layer.
  • the tunnel endpoint batch processing includes: the tunnel cluster notifying the tunnel included in the tunnel information database one by one, switching the tunnel with protection, and printing on the device the centralized management of multiple identical paths provided by the present invention
  • Method and system on the two endpoint devices of the tunnel, create a tunnel cluster for multiple tunnels of the same path; bind the tunnel cluster to the detection management entity group; when the physical link is abnormal, the management entity group will detect the current state
  • the tunnel cluster is notified, and the tunnel cluster completes batch processing according to the detection status. It can reduce the unnecessary T-MPLS OAM packets on the network.
  • the management layer is unified in the cluster mode. This prevents each MEG from printing the same warning and reduces the burden on the device.
  • FIG. 1 is a schematic structural diagram of an application scenario of a method for centralized management of multiple tunnels of the same path according to the present invention
  • FIG. 2 is a schematic flowchart of a method for centralized management of multiple tunnels of the same path according to the present invention
  • FIG. 3 is a schematic diagram of a current state of detection of a management entity group according to the present invention
  • Schematic diagram of the method of notifying the tunnel cluster
  • FIG. 4 is a schematic structural diagram of a system for centralized management of multiple tunnels of the same path according to the present invention. detailed description
  • FIG. 1 is a schematic structural diagram of an application scenario of a method for centralized management of multiple tunnels of the same path according to the present invention. As shown in FIG. 1, four tunnels between the device 101 and the device 108 are tunnel 1, tunnel 2, tunnel 3, and tunnel 4, respectively. Static tunnels pass through device 102, device 104, and device 106 at the same time.
  • tunnels are responsible for different services, such as: tunnel 1 is responsible for network telephony services, tunnel 2 is responsible for video data transmission services, tunnel 3 is responsible for fixed-line services, and tunnel 4 is responsible for point-to-point (BT) download services.
  • tunnel 1 is responsible for network telephony services
  • tunnel 2 is responsible for video data transmission services
  • tunnel 3 is responsible for fixed-line services
  • tunnel 4 is responsible for point-to-point (BT) download services.
  • the working paths of the four tunnels are identical and conform to the basic scenario of the present invention.
  • a tunnel cluster 1 can be created between device 101 and device 108.
  • the MEG deployment only generates a corresponding response at the head node of the tunnel. Therefore, the tunnel cluster only needs to be deployed on the two endpoints of the corresponding tunnel, and the device 101 and the device 108.
  • FIG. 2 is a schematic flowchart of a method for centralized management of multiple tunnels of the same path according to the present invention. As shown in FIG. 2, the method specifically includes:
  • Step 201 Create a tunnel cluster for multiple tunnels of the same path on the two endpoint devices of the tunnel.
  • the tunnel cluster includes: a tunnel cluster number, a tunnel cluster type, a tunnel cluster management entity binding interface, a tunnel number statistics, a tunnel cluster state, and a tunnel information database.
  • the tunnel cluster number is used as an index of the tunnel cluster, and the tunnel device assigns a tunnel cluster number to the cluster when the tunnel cluster is created; the tunnel cluster type is used to specify the type of the tunnel cluster.
  • TMPLS Detect which is the tunnel cluster detected by this layer, and the other is the TMS Detect for the tunnel cluster, which is the tunnel cluster of the lower layer detection; the tunnel cluster management entity binding interface is used as the tunnel cluster.
  • TMP Detect T-MPLS Path
  • T-MPLS segment layer
  • TMS Section, TMS
  • the corresponding TMS is bound to the specified tunnel cluster; the number of tunnels is used to record how many tunnels have been bound in the current tunnel cluster; the tunnel cluster state is used to record the state of the current tunnel cluster, and the tunnel cluster
  • the index of the tunnel information that has been bound in the current tunnel cluster is recorded, so that all the tunnels in the cluster are notified when the state of the tunnel cluster changes.
  • Step 202 Bind the tunnel cluster to the detection management entity group.
  • the binding is specifically performed by the tunnel cluster management entity binding interface, and the tunneling cluster and the management entity group of each tunnel in the tunnel cluster are bound. Further, you need to configure the tunnel cluster type as required. If you need to respond to the TMP tunnel cluster, configure the local layer detection. If you need to respond to the TMS tunnel cluster, configure the lower layer detection. In the present invention, the two tunnel clusters are mutually exclusive and therefore need to be separately configured.
  • the detection management entity group includes: a local layer detection module, configured to detect the current state of the connection path of the devices at both ends, and implement the OAM message transmission and reception between the devices through the protocol.
  • the protocol may be a detection protocol such as TMPLS OAM or BFD.
  • the detection status can be correctly reported.
  • the other is the lower layer detection module, which notifies the lower layer detection alarm for the lower layer detection alarm of the TMP.
  • the lower layer detection entity of the current tunnel cluster is the TMS, and the tunnel cluster needs to respond to the alarm state sent by the lower layer detection module.
  • the outbound interface of the TMS and the outbound interface corresponding to the tunnel are the same, and the TMS is registered through the tunnel cluster management entity binding interface. After the corresponding lower-layer notification relationship is established, the detection status of the lower layer can be correctly reported.
  • Step 203 When the physical link is abnormal, the management entity group notifies the tunnel cluster of the current detection state, and the tunnel cluster completes batch processing according to the detection state.
  • the detection status is specifically sent in the form of alarm information.
  • the tunnel cluster receives the detection status, that is, the alarm information, and then calculates the corresponding tunnel cluster alarm status, and then compares it with the existing alarm status. If the alarm status is the same as the current one, the tunnel cluster is not advertised. In the tunnel, the process ends. If the alarm status is different from the existing alarm status, the alarm status of the tunnel cluster is updated, and all tunnels in the tunnel cluster are advertised, the tunnel status is updated, and batch processing is completed.
  • the batch processing specifically includes: the tunnel cluster notifies the tunnel included in the tunnel information database one by one, switches the tunnel with protection, and prints an alarm on the device.
  • the method further includes: when a new tunnel needs to join the tunnel cluster, determine whether the existing tunnel information in the tunnel cluster matches, and if yes, add, otherwise the addition fails.
  • the tunnel joins the cluster, it first checks whether the tunnel cluster contains information about other tunnels. If there are no other tunnels in the cluster, directly join the tunnel to the cluster. If the tunnel already contains the tunnel, take the first tunnel and need it. The added tunnel compares the basic information of the two tunnels. If the mode (dynamic static), type (single bidirectional), outgoing interface, and next hop are the same, they are added to the tunnel cluster. For the dynamic tunnel, the tunnel is also required. Display route
  • the tunnel cluster does not need to care about the current state of the tunnel in the process of updating the tunnel.
  • the alarm state is directly updated to the current state of the tunnel cluster, and the tunnel is always maintained throughout the process.
  • the alarm status of the cluster is the same.
  • the tunnel cluster will cancel the current alarm state of the tunnel, and the initial value of the alarm state of the tunnel and the new alarm state will be re-notified by the MEG on the tunnel.
  • the tunnel obtains a new alarm status, the status is recorded. If the tunnel is not in the tunnel protection group and there is a corresponding upward advertised configuration, the tunnel advertises a new alarm state to the upper layer TMC.
  • the tunnel cluster Before the tunnel is added to the tunnel cluster, if the state of the tunnel is different from the tunnel cluster, the tunnel cluster advertises the tunnel update alarm status. If the tunnel exists in the tunnel protection group, the tunnel notifies the protection group of the new alarm state, and the protection group calculates the new protection group switching state according to the corresponding protection policy. The row corresponds to the operation. If there is a corresponding upward advertisement configuration on the tunnel, the tunnel will notify the upper TMC of the new alarm status. Before the tunnel is added to the tunnel cluster, if the state of the tunnel is different from the tunnel cluster, the tunnel cluster advertises the tunnel update alarm status.
  • FIG. 3 is a schematic flowchart of a method for a management entity group to notify a tunnel cluster of a current detection state according to the present invention. As shown in FIG. 3, the method includes:
  • Step 301 when the physical link is abnormal, the detecting module on the link calculates the corresponding alarm and reports it, if it is the layer detecting module, step 302 is performed; if it is the lower layer detecting module, step 304 is performed;
  • the abnormality may be a packet failure abnormality caused by fiber extraction, a closed port, or a lost route, or may be an abnormality caused by a packet signal degradation caused by other interferences and an error rate being too high.
  • Step 302 Determine whether the management entity group has a binding relationship with the tunnel cluster. If the binding is established, go to step 303. If there is no binding, process it according to the prior art.
  • Step 303 Determine whether the type of the tunnel cluster is detected by the layer. If yes, send the alarm information to the tunnel cluster, and end the process. If the tunnel cluster type is set to the lower layer detection, the tunnel cluster does not respond.
  • Step 304 The lower layer detecting module updates its own alarm state, and sends the alarm information to the tunnel cluster.
  • the TMS searches for the upward notification object of the TMS.
  • the TMS uplink notification interface is bound to the tunnel cluster management entity binding interface and the tunnel cluster type is the lower layer detection type
  • the alarm information is sent. Send to the tunnel cluster.
  • FIG. 4 is a schematic structural diagram of a system for centralized management of multiple tunnels of the same path according to the present invention. As shown in FIG. 4, the system includes: a tunnel endpoint 41, a detection management entity group 42;
  • the tunnel endpoint 41 is configured to create a tunnel cluster for multiple tunnels of the same path, and the tunnel cluster on the tunnel endpoint completes batch processing according to the received detection state; Specifically, the tunnel cluster includes: a tunnel cluster number, a tunnel cluster type, a tunnel cluster management entity binding interface, a tunnel number statistics, a tunnel cluster state, and a tunnel information database.
  • the tunnel cluster number is used as an index of the tunnel cluster.
  • the tunnel endpoint 41 assigns a tunnel cluster number to the cluster; the tunnel cluster type is used to specify the type of the tunnel cluster.
  • clusters There are two types of clusters, one for the layer detection of the tunnel cluster, that is, the tunnel cluster for the layer detection, and the other for the lower layer detection of the tunnel cluster, that is, the tunnel cluster for the lower layer detection;
  • An entity binding interface is used as an entry point for notification of a tunnel cluster state change.
  • the tunnel cluster type is for TMP
  • the specified detection mode needs to be bound in the cluster layer.
  • the tunnel cluster type is for TMS, Binding the specified tunnel cluster to the TMS corresponding to the lower layer of the cluster; the number of the tunnels is used to record the number of tunnels that have been bound in the current tunnel cluster; the tunnel cluster state is used to record the status of the current tunnel cluster.
  • SF signal failure alarm
  • SD signal degradation alarm
  • the detection status is specifically sent in the form of alarm information. After the tunnel cluster receives the detection status, that is, the alarm information, the corresponding tunnel cluster alarm status is calculated, and then compared with the existing alarm status. If the alarm status is the same as the current one, the tunnel in the tunnel cluster is not advertised. If the alarm status is different from the existing alarm status, update the alarm status of the tunnel cluster, and advertise all the tunnels in the tunnel cluster, update the tunnel status, and complete batch processing.
  • the batch processing specifically includes: the tunnel cluster notifies the tunnel included in the tunnel information database one by one, switches the tunnel with protection, and prints an alarm on the device.
  • the tunnel cluster does not need to care about the current state of the tunnel in the process of updating the tunnel.
  • the alarm state is directly updated to the current state of the tunnel cluster, and the tunnel is always maintained throughout the process.
  • the alarm status of the cluster is the same.
  • the tunnel cluster will cancel the current alarm state of the tunnel, and the initial value of the alarm state of the tunnel and the new alarm state will be re-notified by the MEG on the tunnel.
  • the tunnel obtains a new alarm status, the status is recorded. If the tunnel is not in the tunnel protection group and there is a corresponding upward advertised configuration, the tunnel advertises a new alarm state to the upper layer TMC.
  • the tunnel cluster Before the tunnel is added to the tunnel cluster, if the state of the tunnel is different from the tunnel cluster, the tunnel cluster advertises the tunnel update alarm status. If the tunnel exists in the tunnel protection group, the tunnel notifies the protection group of the new alarm state. The protection group calculates the new protection group switching state and performs corresponding operations according to the corresponding protection policy. If there is a corresponding upward advertisement configuration on the tunnel, the tunnel will notify the upper TMC of the new alarm status. Before the tunnel is added to the tunnel cluster, if the state of the tunnel is different from the tunnel cluster, the tunnel cluster advertises the tunnel update alarm status.
  • the detection management entity group 42 is configured to bind the tunnel cluster. When the physical link is abnormal, the management entity group 42 sends the current detection status to the tunnel endpoint 41.
  • the binding is specifically binding the management entity group of each tunnel in the tunnel cluster and the tunnel cluster by using the tunnel cluster management entity binding interface. Further, you need to configure the tunnel cluster type as required. If you need to respond to the TMP tunnel cluster, configure the local layer detection. If you need to respond to the TMS tunnel cluster, configure the lower layer detection. In the present invention, the two tunnel clusters are mutually exclusive and therefore need to be separately configured.
  • the detection management entity group includes: a layer detection module, configured to detect the current state of the connection path of the devices at both ends, and implement the OAM packet transmission and reception between the devices through the protocol.
  • the protocol may be a detection protocol such as TMPLS OAM or BFD.
  • the detection status can be correctly reported.
  • the other is the lower layer detection module, which notifies the lower layer detection alarm for the lower layer detection alarm of the TMP.
  • the lower layer detection entity of the current tunnel cluster is the TMS, and the tunnel cluster needs to respond to the alarm state sent by the lower layer detection module.
  • the outbound interface of the TMS and the outbound interface corresponding to the tunnel are the same, and the TMS is registered through the tunnel cluster management entity binding interface. After the corresponding lower-layer notification relationship is established, the detection status of the lower layer can be correctly reported.
  • the tunnel endpoint 41 is further configured to determine, when the new tunnel needs to join the tunnel cluster, whether the new tunnel joins the existing tunnel information in the tunnel cluster, and if yes, join, Otherwise the addition fails.
  • the tunnel when the tunnel joins the cluster, it first checks whether the tunnel cluster contains information about other tunnels. If there are no other tunnels in the cluster, directly join the tunnel to the cluster. If the tunnel already contains the tunnel, take the first tunnel and need it. The added tunnel compares the basic information of the two tunnels. If the mode (dynamic static), type (single bidirectional), outgoing interface, and next hop are the same, they are added to the tunnel cluster. For the dynamic tunnel, the tunnel is also required. The display route is checked. If it is not the same, the addition fails. The return user fails to be added. The above method can only determine whether the local end of the tunnel is consistent for a static tunnel, but cannot guarantee the same path. The specific topology needs to be guaranteed by the configurator.

Landscapes

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

Abstract

La présente invention se rapporte à un procédé de gestion centralisée pour une pluralité de tunnels ayant le même chemin. Le procédé selon l'invention consiste à créer une grappe de tunnels pour une pluralité de tunnels ayant le même chemin aux deux dispositifs de point d'extrémité du tunnel. Le procédé selon l'invention consiste d'autre part à associer la grappe de tunnels à un groupe d'entités de maintenance (MEG, Maintenance Entity Group), le MEG informant la grappe de tunnels de l'état actuel détecté quand une panne se produit sur une liaison physique ; et la grappe de tunnels accomplissant un traitement par lots sur la base de l'état détecté. La présente invention se rapporte d'autre part à un système de gestion centralisée pour une pluralité de tunnels ayant le même chemin. Le procédé et le système selon la présente invention sont aptes : à réduire la transmission inutile d'un message de maintenance au sein du réseau ; à transmettre uniformément l'état d'une panne sur la liaison physique à une couche de gestion, de manière groupée ; et à supprimer la nécessité d'imprimer les mêmes alertes pour chaque MEG, ce qui permet ainsi de réduire la charge sur les dispositifs.
PCT/CN2011/081291 2011-01-24 2011-10-25 Procédé et système de gestion centralisée pour une pluralité de tunnels ayant le même chemin Ceased WO2012100571A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110025518.7A CN102611610B (zh) 2011-01-24 2011-01-24 一种多条相同路径隧道集中管理的方法和系统
CN201110025518.7 2011-01-24

Publications (1)

Publication Number Publication Date
WO2012100571A1 true WO2012100571A1 (fr) 2012-08-02

Family

ID=46528776

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/081291 Ceased WO2012100571A1 (fr) 2011-01-24 2011-10-25 Procédé et système de gestion centralisée pour une pluralité de tunnels ayant le même chemin

Country Status (2)

Country Link
CN (1) CN102611610B (fr)
WO (1) WO2012100571A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107104837A (zh) * 2017-05-09 2017-08-29 华为技术有限公司 路径检测的方法和控制设备
CN113472642A (zh) * 2021-06-10 2021-10-01 新华三信息安全技术有限公司 一种保护切换方法及装置
CN115314365A (zh) * 2022-07-05 2022-11-08 杭州云合智网技术有限公司 单保护组集合的快速切换方法

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102970219B (zh) * 2012-11-30 2016-03-30 华为技术有限公司 绑定保护环的方法和装置
CN106656606A (zh) * 2016-12-27 2017-05-10 北京奇虎科技有限公司 数据通路的测试方法、测试服务器及测试系统
CN109495286B (zh) * 2017-09-13 2021-11-12 中兴通讯股份有限公司 相交环复用段告警检测方法及装置、计算机可读存储介质
CN107769964B (zh) * 2017-09-29 2021-06-04 北京天元创新科技有限公司 专线核查方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101106486A (zh) * 2007-08-13 2008-01-16 杭州华三通信技术有限公司 虚链路故障的检测处理方法及组件
CN101425971A (zh) * 2008-12-02 2009-05-06 中兴通讯股份有限公司 一种t-mpls通路层隧道切换的方法
CN101483560A (zh) * 2009-02-20 2009-07-15 华为技术有限公司 一种实现隧道检测的方法、装置和系统
CN101877677A (zh) * 2010-06-25 2010-11-03 中兴通讯股份有限公司 一种多协议标签交换业务隧道切换的方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101106486A (zh) * 2007-08-13 2008-01-16 杭州华三通信技术有限公司 虚链路故障的检测处理方法及组件
CN101425971A (zh) * 2008-12-02 2009-05-06 中兴通讯股份有限公司 一种t-mpls通路层隧道切换的方法
CN101483560A (zh) * 2009-02-20 2009-07-15 华为技术有限公司 一种实现隧道检测的方法、装置和系统
CN101877677A (zh) * 2010-06-25 2010-11-03 中兴通讯股份有限公司 一种多协议标签交换业务隧道切换的方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
H.OHTA ET AL.: "Assignment of the 'OAM Alert Label' for Multiprotocol Label Switching Architecture(MPLS) Operation and Maintenance(OAM) Functions.", IETF, November 2002 (2002-11-01) *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107104837A (zh) * 2017-05-09 2017-08-29 华为技术有限公司 路径检测的方法和控制设备
CN113472642A (zh) * 2021-06-10 2021-10-01 新华三信息安全技术有限公司 一种保护切换方法及装置
CN115314365A (zh) * 2022-07-05 2022-11-08 杭州云合智网技术有限公司 单保护组集合的快速切换方法

Also Published As

Publication number Publication date
CN102611610A (zh) 2012-07-25
CN102611610B (zh) 2016-03-30

Similar Documents

Publication Publication Date Title
EP2680510B1 (fr) Protection de réacheminement rapide déclenchée par un plan de service
US8325611B2 (en) Scaling OAM for point-to-point trunking
US11388041B2 (en) Service-based loss forwarding in communication networks
US9755957B2 (en) Pseudowire control channel for signaling events
US8335154B2 (en) Method and system for providing fault detection and notification for composite transport groups
US9203732B2 (en) Recovery of traffic in a connection-oriented network
CN101523803B (zh) 通信网络中的弹性方案
KR20110090905A (ko) 라우팅된 백업을 갖는 준비된 ｐｌｓｂ
CN102684973B (zh) 一种环网保护的方法及系统
US20090161533A1 (en) Active fault management for metro ethernet service over mpls network
US10862706B2 (en) Detection of node isolation in subtended ethernet ring topologies
WO2012100571A1 (fr) Procédé et système de gestion centralisée pour une pluralité de tunnels ayant le même chemin
WO2011079441A1 (fr) Procédé et système de mise à jour de topologie de réseau dans un système de commutation multiprotocole par étiquette
JP2014064252A (ja) ネットワークシステム、伝送装置、及び障害情報通知方法
US20080263615A1 (en) Integrated operation management system of video transmission network and operation management method
CN105264836B (zh) 一种多域网络保护方法、系统和节点
CN102291310B (zh) 一种提高t‑mpls链路环网保护切换性能的方法及装置
JP5518771B2 (ja) 冗長ネットワークシステム、終端装置及び中継点隣接装置
CN101645840B (zh) 一种转发报文的方法、系统及路由设备
CN102487327B (zh) 业务切换方法及装置
Kim et al. OAM and protection mechanisms for MPLS-TP packet transport networks
US20150188803A1 (en) Systems, apparatuses, and methods for rerouting network traffic
CN114598596A (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: 11857162

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

Country of ref document: EP

Kind code of ref document: A1