WO2012065470A1 - Procédé et dispositif pour le traitement d'une défaillance de liaison - Google Patents

Procédé et dispositif pour le traitement d'une défaillance de liaison Download PDF

Info

Publication number
WO2012065470A1
WO2012065470A1 PCT/CN2011/078871 CN2011078871W WO2012065470A1 WO 2012065470 A1 WO2012065470 A1 WO 2012065470A1 CN 2011078871 W CN2011078871 W CN 2011078871W WO 2012065470 A1 WO2012065470 A1 WO 2012065470A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
channel
link
link layer
failure
Prior art date
Application number
PCT/CN2011/078871
Other languages
English (en)
Chinese (zh)
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 WO2012065470A1 publication Critical patent/WO2012065470A1/fr

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/07—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems
    • H04B10/075—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal
    • H04B10/079—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal using measurements of the data signal
    • H04B10/0791—Fault location on the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • 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/28—Routing or path finding of packets in data switching networks using route fault recovery

Definitions

  • the present invention relates to the field of communications, and in particular to a link fault processing method and apparatus.
  • ASON Automatic Switched Optical Network
  • AS0N's research focuses on three parts: service transmission, automatic switching control and network management. The functions are implemented by Transport Plane, Control Plane, and Management Plane.
  • ASON Based on the protection of the transport plane, ASON supports the network protection mode of the Synchronous Digital Hierarchy (SDH), such as the multiplex section shared guard ring (MS-SPRing, mainly in the form of two-fiber and four-fiber guard rings).
  • SDH Synchronous Digital Hierarchy
  • MS-SPRing multiplex section shared guard ring
  • ASON supports end-to-end (channel) protection, that is, the entire connection protection from the source node to the destination node.
  • channel channel
  • the transmission node network element When the actual transmission network transmits the service, some unpredictable abnormalities often occur, such as the power failure of the transmission node network element, the connection of the optical fiber, the failure of the service optical board, the failure of the cross-board, the insufficient resources of the SDH time slot, and the connection of the bearer service. There are alarms (external interference or internal generation) on the channel, which will affect the service creation and normal operation.
  • the method adopted by ASON is to detect the faults generated by the connection, and according to the layer of the connection, it can be divided into link layer fault detection and channel layer fault detection. Link layer fault detection needs to be performed in combination with the route of the connection itself and the actual link condition in the current network.
  • the link conditions in the network are often divided into two types: one is a ring protection link. (Two-fiber multiplex section shared protection ring or four-fiber multiplex section shared protection ring), another common link (including unprotected link, 1+1 multiplex section protection link, 1:1 multiplex section protection) The link and the 1: N multiplex section protection link.
  • the criterion for determining whether the connection is faulty is whether the hop-by-hop route of the connection is invalid on the ring or the normal link. If there is a failure condition, the service is triggered to recover.
  • Channel layer fault detection is often based on the Link Management Protocol (LMP). In the specific implementation, it is usually performed in a single direction.
  • LMP Link Management Protocol
  • the PAHT direction is detected by the source NE.
  • the RESV direction is detected by the destination NE.
  • the meta node sends the positioning result, and all service recovery or reply operations are controlled by the source network element node.
  • the PATH direction refers to the direction in which the head node initiates signaling to the tail node during the establishment of the connection, and vice versa.
  • link layer fault detection takes precedence over channel fault detection. Therefore, channel detection is not initiated normally.
  • a primary object of the present invention is to provide a link fault processing method and apparatus, to at least solve the above-mentioned situation that a link layer fault and a channel fault exist at the same time, and may only eliminate one type of fault instead of eliminating all, and further The problem that caused the subsequent business to respond incorrectly.
  • a link fault processing method including: determining, when a link layer fault and a channel fault exist on a network link connection, determining that the link layer fault and the channel fault occur Sequence; initiate link layer failure detection and/or channel failure detection according to the order.
  • the initiating the link layer detection and/or the channel fault detection according to the sequence includes: starting a link layer fault on the link connection, and then starting the link layer when a channel fault occurs Fault detection, repairing the link layer fault; and reporting that the link layer fault disappears when the link layer fault is repaired.
  • the method includes: when the service carried on the link connection has a recovery attribute, recovering the service; and when the link layer fault is When the service has a reply attribute, the channel fault detection is started by using the timer T1. If the channel fault is repaired, reporting the link connection failure of the link disappears, and notifying the service reply.
  • the fault includes: reporting that the link connecting the service fails.
  • the initiating the link layer detection and/or the channel fault detection according to the sequence includes: identifying a link connection when a link fault occurs first on the link connection, and then a link layer fault occurs If there is a channel fault, there is a link layer fault; the link layer fault detection is started to repair the link layer fault, and/or the channel fault detection is started to repair the channel fault; Reporting the link layer failure and/or the channel failure disappears according to the repair result reported by the link.
  • the method includes: when the service carried on the link connection has a recovery attribute, recovering the service; and when the link layer fault is repaired, When the service has a reply attribute, the channel fault detection is started by using the timer T2.
  • a link failure processing apparatus including: a determining unit configured to determine the link layer failure and when a link layer failure and a channel failure exist simultaneously on a network link connection The sequence in which the channel failures occur; the initiating unit is configured to initiate link layer failure detection and/or channel failure detection in accordance with the order.
  • the starting unit comprises: a first repairing subunit, configured to start the link layer fault detection when a link layer fault occurs first on the link connection, and then the link layer fault detection is started, The link layer fault is repaired.
  • the first reporting subunit is configured to report that the link layer fault disappears when the link layer fault is repaired.
  • the starting unit further includes: a first recovery subunit, configured to: when the service carried on the link connection has a recovery attribute, recover the service; the first activation subunit is set to be When the link layer fault is repaired and the service has a reply attribute, the channel fault detection is started by using the timer T1. If the channel fault is repaired, reporting the link connection failure of the link disappears, and the service reply is notified.
  • the first reporting sub-unit is further configured to report that the fault of the link connecting the service disappears after reporting that the link connection fails.
  • the activation unit includes: an identifier subunit, configured to: when a link failure occurs first on the link connection, and then a link layer fault occurs, the link is identified as: that is, there is a channel failure, and There is a link layer fault; a second repair subunit is configured to initiate the link layer fault detection to repair the link layer fault, and/or to initiate the channel fault detection to repair the channel fault; The second reporting subunit is configured to report the link layer failure according to the repair result and/or the channel failure disappears.
  • the starting unit further includes: a second recovery subunit, configured to: when the service carried on the link connection has a recovery attribute, recover the service; and the second activation subunit is configured to be When the link layer fault is repaired and the service has a reply attribute, the channel fault detection is started by using the timer T2. If the channel fault is repaired, the fault is reported to be reported by the link connection, and the service reply is notified; The unit is configured to notify the service reply when the channel failure is repaired and the service has a reply attribute.
  • the second report form sub-element is further configured to report that the fault of the link connecting the service disappears when the link layer fault and the channel fault disappear.
  • the order of link layer faults and channel faults is determined, and link layer fault detection is started according to the determined order and/or Channel fault detection, in the case of link layer faults and channel faults at the same time, it can confirm fault elimination and avoid subsequent business error recovery, which can effectively shorten development time and reduce project implementation cost.
  • FIG. 1 is a process flow diagram of a link failure processing method according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a scenario according to Embodiment 1 of the present invention
  • FIG. 3 is an implementation according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a scenario according to Embodiment 2 of the present invention;
  • FIG. 1 is a process flow diagram of a link failure processing method according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a scenario according to Embodiment 1 of the present invention
  • FIG. 3 is an implementation according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a scenario according to Embodiment 2 of the present invention;
  • FIG. 1 is a process flow diagram of a link failure processing method according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a scenario according to Embodiment 1 of the present invention
  • FIG. 3 is an implementation according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a process according to Embodiment 2 of the present invention
  • FIG. 6 is an implementation according to an embodiment of the present invention
  • FIG. 7 is a flowchart of a process according to Embodiment 3 of the embodiment of the present invention
  • FIG. 8 is a schematic structural diagram of a link failure processing apparatus according to an embodiment of the present invention
  • FIG. 9 is a first structural diagram of a startup unit according to an embodiment of the present invention
  • FIG. 10 is a second embodiment of a startup unit according to an embodiment of the present invention.
  • FIG. 11 is a schematic view showing a third structure of a starting unit according to an embodiment of the present invention
  • FIG. 12 is a fourth structural diagram of a starting unit according to an embodiment of the present invention.
  • the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
  • the priority of the link layer fault detection is higher than the priority of the channel fault detection. Therefore, the channel detection is not normally started, but in the case where the link layer fault and the channel fault exist simultaneously, it may be Only one of the faults is eliminated, not all eliminated, which leads to subsequent business mis-replies.
  • the embodiment of the present invention provides a link fault processing method. The processing flow is as shown in FIG.
  • Step 102 When a link layer fault and a channel fault exist on a network link connection, Determining the order in which link layer failures and channel failures occur; Step 104, initiating link layer failure detection and/or channel failure detection according to the order.
  • the order of link layer faults and channel faults is determined, and link layer fault detection is started according to the determined order and/or Channel fault detection, in the case of link layer faults and channel faults at the same time, it can confirm fault elimination and avoid subsequent business error recovery, which can effectively shorten development time and reduce project implementation cost.
  • Step 102 When a link layer fault and a channel fault exist on a network link connection, Determining the order in which link layer failures and channel failures occur; Step 104, initiating link layer failure detection and/or channel failure detection according to the order.
  • step 104 starts link layer detection and/or channel fault detection according to the sequence, which includes two situations, one is that a link layer fault occurs first on the link connection, and then A channel failure occurs. In another case, a channel failure occurs first on the link connection, and then a link layer failure occurs.
  • the analysis is performed separately.
  • the link layer fault detection is started to repair the link layer fault.
  • the link link layer fault is reported. disappear.
  • the channel fault detection is started by using the timer T1, and the channel fault is repaired.
  • the reported link connection channel failure disappears, and the service reply is notified.
  • the time of the timer T1 can be set to any time, depending on the specific situation, for example, it can be set to 0, or set to 5 seconds, and so on.
  • the channel fault detection is started, and after the channel fault disappears, the fault that the link connection service can be reported disappears. If only the link layer fault disappears or only the channel fault disappears, Only the link layer fault or channel fault is eliminated, and the service fault cannot be reported.
  • the link connection is identified as follows: there is a channel fault and a link layer fault exists; and the link layer fault detection pair chain is started.
  • the fault of the road layer is repaired, and/or the fault detection of the start channel is used to repair the fault of the channel; the link layer fault and/or the channel fault disappeared according to the repair result.
  • the timer T2 is started after the channel fault occurs on the link connection.
  • Channel fault detection if the channel fault is repaired, the reported link connection channel fault disappears, and the service reply is notified.
  • the timer T2 time can be set to any time, depending on the specific situation, for example, it can be set to 0, or Set for 5 seconds, and so on.
  • the timer T2 is only used to distinguish the timer T1 from the above.
  • the first timer, the second timer, or the timer A and the timer B can also be used for distinguishing.
  • the service reply is notified.
  • the link layer fault is detected, the channel fault detection is started, and after the channel fault disappears, the fault that the link connection service can be reported disappears. If only the link layer fault disappears or only the channel fault disappears, Only the link layer fault or channel fault is eliminated, and the service fault cannot be reported.
  • the embodiment of the invention provides a method for coordinating and processing faults when a link layer fault and a channel fault exist in a connection in an ASON network.
  • the scenario processing mechanism is as follows:
  • the link layer fault When a link layer fault is detected, if the service has a recovery attribute, the service should be restored.
  • the link layer fault can only be cleared by the link layer fault disappearing.
  • the channel fault can only be cleared by the channel fault disappearing. Only after receiving the two faults disappears, the service fault disappears. When only the link layer fault disappears, the channel fault may still exist because there is no trigger channel detection. For services with reply attributes, false responses may occur.
  • the timer ⁇ may be used. After the device times out, channel fault detection is performed to determine if a channel fault exists. Second, the first channel failure, the rear link layer failure.
  • connection When the connection first receives a channel failure and then receives a link layer failure, the connection needs to be clearly marked "that is, there is a channel failure and a link layer failure.” If the business has a recovery attribute, the business should be restored. If only the link layer fault that has received the connection disappears or the channel fault disappears, the connection cannot report the fault disappearing, and only the local link layer fault status or channel fault status is cleared. If the channel fault that has received this connection disappears or the link layer fault disappears, the connection needs to report that the channel fault disappears or the link layer fault disappears. The fault that the service receives the connection disappears.
  • the fault is handled in two cases: If the channel fault disappears, if the service has a reply attribute, the reply waiting timer does not need to be started, and the direct reply can be performed; if the link layer fault disappears, if the service has a reply Attribute, you need to start the reply wait timer ⁇ 2. When the timer ⁇ 2 times out, if there is no link layer fault or channel fault, the reply operation is performed.
  • the embodiments of the present invention focus on methods for coordinating link layer faults and channel layer faults. The methods for link layer fault detection and channel layer fault detection are only described in general, because in the industry, both detection mechanisms are sufficient.
  • connection refers to the link connection of the foregoing.
  • Embodiment 1 A link layer fault is generated first, and then a channel layer alarm scenario is generated.
  • Step 302 When a link layer alarm is generated between the two network elements, for example, between the network element A and the network element B, the link layer fault detection is performed.
  • Step 304 After the detection is completed and the link layer fault is reported, If the channel layer alarm is generated, the channel fault detection will not occur.
  • Step 306 The link layer alarm disappears. The link layer fault detection will notify the service link layer that the fault disappears. Because there is no trigger channel detection, the channel fault may still exist. The service with the reply attribute may cause a false reply.
  • Step 308 Start the timer, and after the timer expires, perform channel fault detection.
  • Step 310 Report the fault to the service. If the service has the recovery attribute, perform service recovery. .
  • Embodiment 2 A channel fault is generated first, and a link layer alarm scenario is generated. Referring to FIG. 4, the processing flow is as shown in FIG. 4, the processing flow is as shown in FIG.
  • Step 502 Connect the received channel alarm, perform channel alarm detection, and confirm that there is a channel fault; Step 504 If the link layer fault is received, the connection needs to be marked as "there is a channel fault and a link layer fault". However, when the connection reports to the bearer service, the channel layer fault reporting status needs to be determined. If the report has been reported, the report does not need to be reported, because the service of the channel fault has triggered the recovery of the service. Step 506: If the link layer fault disappears or the channel fault disappears, the connection cannot be forwarded to the bearer. The fault of the service report disappears, and only the local link layer fault state or the channel fault state is cleared.
  • Step 508 If the channel fault that subsequently receives the connection disappears or the link layer fault disappears, the connection needs to be carried to the bearer service. The escalation channel failure disappears.
  • Embodiment 3 In the process of channel detection, a link layer alarm scenario is generated. Referring to FIG. 6, the processing flow is as shown in FIG. 7. Step 702: Connect a channel alarm, perform a channel fault detection process, and receive the detection process. The link layer alarm is generated, and a link layer fault is generated. At this time, the link layer fault is reported.
  • Step 704 After the channel fault detection process ends, if a channel layer fault occurs, the connection needs to be marked with "existing channel.” Failure, there is a link layer failure"; Step 706: If the link layer fault disappears or the channel fault disappears, the connection fails to report the fault to the bearer service, and only the local link layer fault state or the channel fault state is cleared. Step 708: If subsequent If the channel fault that receives the connection disappears or the link layer fault disappears, the connection needs to report the channel fault to the bearer service. Based on the same inventive concept, an embodiment of the present invention further provides a link fault processing apparatus, and a schematic structural diagram thereof is shown in FIG. 8.
  • the method includes: determining unit 801, configured to have a link layer fault and a network link connection simultaneously In the event of a channel failure, the order in which the link layer failure and the channel failure occur is determined; the initiation unit 802 is configured to initiate link layer failure detection and/or channel failure detection in accordance with the sequence.
  • the starting unit 802 may include: a first repair subunit 901, configured to start a link layer fault when a link layer fault occurs first on a link connection, and then a channel fault occurs. Detecting, repairing the link layer fault; The first reporting sub-unit 902 is configured to report that the link link layer fault disappears when the link layer fault is repaired.
  • determining unit 801 configured to have a link layer fault and a network link connection simultaneously In the event of a channel failure, the order in which the link layer failure and the channel failure occur is determined
  • the initiation unit 802 is configured to initiate link layer failure detection and/or channel failure detection in accordance with the sequence.
  • the starting unit 802 may include: a first repair subunit
  • the initiating unit 802 may include: a first recovery subunit 1001 configured to restore a service when a service carried on the link connection has a recovery attribute; the first activation subunit 1002, When the link layer fault is repaired and the service has the reply attribute, the channel fault detection is started by using the timer T1. If the channel fault is repaired, the reported link connection channel fault disappears, and the service reply is notified.
  • the first reporting sub-unit 902 is further configured to report that the failure of reporting the link connection service disappears after the reported link connection channel failure disappears. In an embodiment, as shown in FIG.
  • the starting unit 802 includes: an identifying subunit 1101, configured to indicate that when a link fault occurs first on a link connection, and then a link layer fault occurs, the link connection is indicated as: The channel is faulty, and there is a link layer fault.
  • the second repair sub-unit 1102 is configured to initiate link layer fault detection to repair the link layer fault, and/or to initiate channel fault detection to repair the channel fault; and the second reporting sub-unit 1103 is configured to report the repair result according to the repair result.
  • the link connection link layer failure and/or channel failure disappears.
  • the initiating unit 802 may further include: a second recovery subunit 1201 configured to restore a service when a service carried on the link connection has a recovery attribute; the second activation subunit 1202 When the link layer fault is repaired and the service has a reply attribute, the channel fault detection is started by using the timer T2. If the channel fault is repaired, the reported link connection channel fault disappears, and the service reply is notified; the notification unit 1203, setting In order to notify the service reply when the channel failure is fixed and the service has a reply attribute.
  • the second reporting unit 1103 may further be configured to report that the link connection service fails when the link layer fault and the channel fault disappear.
  • the present invention achieves the following technical effects:
  • the link layer fault and the channel fault are determined.
  • the order of occurrence, and the link layer fault detection and/or channel fault detection are started according to the determined order.
  • the fault elimination can be confirmed, the subsequent service false reply can be avoided, and the fault can be effectively shortened. R&D time and reduce the cost of project implementation.
  • the technical solution of the present invention has industrial applicability, performs detection according to different fault occurrence sequences, can detect all faults, avoids omissions, and avoids subsequent business error recovery, can effectively shorten development time and reduce engineering implementation. cost.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
  • program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Maintenance And Management Of Digital Transmission (AREA)

Abstract

L'invention concerne un procédé et un dispositif pour le traitement d'une défaillance de liaison. Le procédé comprend les étapes suivantes consistant à déterminer l'ordre d'apparition des défaillances dans la couche de liaison et dans le canal lorsque la défaillance de la couche de liaison et la défaillance du canal apparaissent simultanément dans la connexion de la liaison de réseau; et déclencher la détection de défaillance de la couche de liaison et/ou la détection de défaillance du canal selon ledit ordre. L'application de la présente invention permet d'assurer l'élimination des défaillances, évitant ainsi la réponse d'erreur du service suivant.
PCT/CN2011/078871 2010-11-17 2011-08-24 Procédé et dispositif pour le traitement d'une défaillance de liaison WO2012065470A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010548258.7 2010-11-17
CN2010105482587A CN102468885A (zh) 2010-11-17 2010-11-17 链路故障处理方法及装置

Publications (1)

Publication Number Publication Date
WO2012065470A1 true WO2012065470A1 (fr) 2012-05-24

Family

ID=46072118

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/078871 WO2012065470A1 (fr) 2010-11-17 2011-08-24 Procédé et dispositif pour le traitement d'une défaillance de liaison

Country Status (2)

Country Link
CN (1) CN102468885A (fr)
WO (1) WO2012065470A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002009698A (ja) * 2000-06-23 2002-01-11 Nippon Telegr & Teleph Corp <Ntt> 光伝達網の障害復旧方法
CN1885789A (zh) * 2005-06-23 2006-12-27 华为技术有限公司 自动交换光网络中通道故障的处理方法
CN101138256A (zh) * 2005-06-06 2008-03-05 中兴通讯股份有限公司 一种自动交换光网络中层网络之间保护恢复的协调方法
CN101197591A (zh) * 2008-01-02 2008-06-11 中兴通讯股份有限公司 用于ason的保护恢复方法和装置
CN101577585A (zh) * 2009-06-05 2009-11-11 中兴通讯股份有限公司 自动交换光网络中故障确定方法与装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7697455B2 (en) * 2004-02-17 2010-04-13 Dynamic Method Enterprises Limited Multiple redundancy schemes in an optical network
CN101159494A (zh) * 2007-10-26 2008-04-09 中兴通讯股份有限公司 用于自动交换光网络的业务保护方法
CN101534459B (zh) * 2009-04-22 2011-12-28 中兴通讯股份有限公司 一种自动交换光网络中实现保护与恢复的方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002009698A (ja) * 2000-06-23 2002-01-11 Nippon Telegr & Teleph Corp <Ntt> 光伝達網の障害復旧方法
CN101138256A (zh) * 2005-06-06 2008-03-05 中兴通讯股份有限公司 一种自动交换光网络中层网络之间保护恢复的协调方法
CN1885789A (zh) * 2005-06-23 2006-12-27 华为技术有限公司 自动交换光网络中通道故障的处理方法
CN101197591A (zh) * 2008-01-02 2008-06-11 中兴通讯股份有限公司 用于ason的保护恢复方法和装置
CN101577585A (zh) * 2009-06-05 2009-11-11 中兴通讯股份有限公司 自动交换光网络中故障确定方法与装置

Also Published As

Publication number Publication date
CN102468885A (zh) 2012-05-23

Similar Documents

Publication Publication Date Title
EP2458797B1 (fr) Procédé, dispositif et système de mise à jour d&#39;informations de topologie de réseau en anneau
US8014300B2 (en) Resource state monitoring method, device and communication network
WO2010045832A1 (fr) Procédé et appareil destinés à protéger un groupe d&#39;agrégation de liaisons d&#39;un réseau en anneau ethernet
JP2010226393A (ja) 自律分散制御によるパス設定方法およびシステム並びに通信装置
US8630162B2 (en) Fast flooding based fast convergence architecture
JP2009303087A (ja) ノード及び通信システム
US20150186202A1 (en) Method and Device for Sending Inter-Domain Fault Information
WO2015196676A1 (fr) Procédé et dispositif de protection de réseau social et élément de réseau de convergence principal dans un réseau social
WO2013049981A1 (fr) Procédé et système de protection de réseau en anneau hybride fondés sur un chemin partagé
WO2008031352A1 (fr) Procédé et appareil de récupération d&#39;un effacement anormal survenu dans le lsp d&#39;un réseau optique
CN101155179B (zh) 一种多协议标签交换中环路拆除的方法
WO2010121459A1 (fr) Procédé et système pour mettre en oeuvre une protection et une reprise dans un réseau optique à commutation automatique
WO2011017941A1 (fr) Procédé et service de protection de réseau
WO2013040940A1 (fr) Procédé et dispositif de protection de réseau en anneau
WO2011091627A1 (fr) Procédé permettant de partager une protection du champ de protection d&#39;un réseau maillé et système associé
WO2015154423A1 (fr) Procédé, appareil et système de traitement de services inter-domaines
US10033573B2 (en) Protection switching method, network, and system
WO2013037248A1 (fr) Procédé et dispositif de commutation en retour de liaison de groupes de protection de réseau en anneau
US8868967B2 (en) Method and system for connection-error handling of service in an automatically switched optical network
WO2010133065A1 (fr) Système de protection et procédé basé sur un réseau optique passif
WO2009046652A1 (fr) Procédé de détection d&#39;état de liaison et dispositif de réseau
US8965199B2 (en) Method and apparatus for automatically restoring node resource state in WSON system
WO2015168892A1 (fr) Procédé de commutation de protection, nœud et dispositif de commande
JP6442847B2 (ja) 通信システム及びノード
WO2016149897A1 (fr) Procédé et appareil de calcul de route dans un ason

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

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

Country of ref document: EP

Kind code of ref document: A1