WO2007079659A1 - Procédé et système de restauration de services ayant subi un problème - Google Patents

Procédé et système de restauration de services ayant subi un problème Download PDF

Info

Publication number
WO2007079659A1
WO2007079659A1 PCT/CN2006/003722 CN2006003722W WO2007079659A1 WO 2007079659 A1 WO2007079659 A1 WO 2007079659A1 CN 2006003722 W CN2006003722 W CN 2006003722W WO 2007079659 A1 WO2007079659 A1 WO 2007079659A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
domain
connection
cross
node
Prior art date
Application number
PCT/CN2006/003722
Other languages
English (en)
French (fr)
Inventor
Yu Yang
Original Assignee
Huawei 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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=38255977&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2007079659(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP06840752A priority Critical patent/EP1973267B1/en
Priority to DE602006016337T priority patent/DE602006016337D1/de
Priority to CNA2006800117358A priority patent/CN101156367A/zh
Priority to AT06840752T priority patent/ATE478492T1/de
Publication of WO2007079659A1 publication Critical patent/WO2007079659A1/zh
Priority to US12/102,421 priority patent/US8289843B2/en

Links

Classifications

    • 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
    • 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/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H04L47/762—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/783—Distributed allocation of resources, e.g. bandwidth brokers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • 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/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • 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/02—Topology update or discovery
    • H04L45/10—Routing in connection-oriented networks, e.g. X.25 or ATM
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0073—Provisions for forwarding or routing, e.g. lookup tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0079—Operation or maintenance aspects
    • H04Q2011/0081—Fault tolerance; Redundancy; Recovery; Reconfigurability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0088—Signalling aspects

Definitions

  • the present invention relates to the field of network and communication technologies, and in particular, to a cross-domain service failure recovery method and system. ' Background technique
  • the service scheduling of the traditional optical network adopts the static configuration of the network management system and does not support the dynamic provisioning mode.
  • the traditional optical network mostly adopts linear and ring networking.
  • the protection recovery adopts multiplex section protection and subnet connection protection, which is basically a static type. Recovery method, but with the rapid development of data services and leased line services, the bandwidth demand for the network is gradually increasing, and the dynamic allocation requirements for network bandwidth are becoming more and more urgent.
  • the network needs to be dynamically enabled, and needs to support the mesh network.
  • the structure, with flexible expansion capability and fast protection and recovery function, the Automatic Switch Optical Network (ASON) solves the above problem well. It uses general multi-protocol label switching (GMPLS, Generalized Multiprotocol) in the control plane.
  • GPLS Generalized Multiprotocol
  • the Label Switching protocol has become a core technology for the development of optical networks.
  • Two new connection types are provided in ASON: one is a soft permanent connection and the other is a switched connection.
  • the ITU-T of the International Telecommunication Union has basically completed the architecture and requirement definition of ASON.
  • the Internet Engineering Task Force IETF has completed the protocol extension and definition of signaling, automatic discovery and routing in a single domain.
  • the control plane needs to solve the management problem of large-scale networks.
  • the ITU-T, Optical Internet Forum OIF uses a hierarchical network model, and a lower control domain is represented by a proxy node in the upper layer.
  • a node can advertise an abstract topology representing an domain, an inter-domain link, a reachable address, etc., so that a layer-by-layer network is formed layer by layer. For example, in FIG.
  • layer 0 is an actual network, and is divided into multiple control domains, such as CD1, CD2, CD3 and CD4 are in layer 1, each domain is abstracted into one node, ie RC11, RC12, RC1 3 and RC14 in the figure, and so on, the whole network becomes a 3-layer network topology.
  • the connection recovery speed becomes a very important bottleneck. Because of the multi-domain case, the connection spans multiple domains, and the number of nodes passing is far more than that of a single domain. This becomes an urgent need after network expansion. The problem is solved.
  • the intra-domain tunnel is generally used for local recovery.
  • the inter-domain protection or fast recovery mechanism is usually used for recovery.
  • the intra-domain bandwidth resource is insufficient, the inter-domain fast recovery mode used in the domain cannot be restored, or the inter-domain link recovery fails, or there is no method for fast recovery between related domains, end-to-end connection recovery is required, but cross-domain connection is required.
  • the external network-interface (ENNI) signaling is required to establish a session process in the process of establishing a connection.
  • the entire end-to-end inter-domain connection service of the inter-domain connection service cannot be specifically determined.
  • the first node of the service fails to report the service information of the inter-domain connection.
  • the end-to-end connection recovery of the inter-domain connection service is difficult. P strives for the survivability of the inter-domain connection service. Summary of the invention
  • the embodiment of the invention provides a method and system for recovering service faults, which can implement end-to-end connection recovery of cross-domain connection services and improve the survivability of cross-domain connection services.
  • the embodiment of the present invention provides a service fault recovery method, which is used to implement end-to-end connection recovery of a cross-domain connection service, and the method includes:
  • the fault detection node of the inter-domain connection service sends the call identifier that identifies the inter-domain connection service and the failed link information in the inter-domain connection service to the first node of the inter-domain connection service;
  • the first node of the cross-domain connection service determines the faulty cross-domain connection service according to the call identifier
  • the embodiment of the invention provides a service fault recovery system, which is used for end-to-end connection recovery of an inter-domain connection service, including:
  • a fault detecting unit configured to detect a service fault, and send, to the head node of the cross-domain connection service, a call identifier that identifies the faulty cross-domain connection service and invalid link information in the cross-domain connection service;
  • the first node of the cross-domain connection service recalculates the route based on the failed link information and obtains a cross.
  • the fault recovery unit performs end-to-end connection recovery on the faulty cross-domain connection service according to the failed link information and the recovery connection path in the cross-domain connection service.
  • the embodiment of the present invention uniquely identifies a cross-domain connection service by using a call identifier object defined by a standard, and after detecting a service fault, the fault detection node of the cross-domain connection service is
  • the first node of the inter-domain connection service sends a call identifier that identifies the inter-domain connection service and the failed link information in the inter-domain connection service; the first node of the inter-domain connection service according to the call identifier and the failure chain in the cross-domain connection service
  • the end-to-end connection recovery of the cross-domain connection service is implemented, and the end-to-end connection recovery of the inter-domain connection service is improved, thereby improving the survivability of the inter-domain connection service.
  • FIG. 1 is a schematic diagram of a model of a prior art hierarchical network
  • FIG. 2 is a flowchart of implementing a service fault method according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of an end-to-end fault recovery in an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of fault recovery in a specific embodiment of a service failure recovery method according to the present invention. detailed description
  • the main processes for implementing the service fault recovery method in the embodiment of the present invention are as follows:
  • Step S11 the present invention uses a standard defined call identity object to uniquely identify an inter-domain connection service.
  • the fault detection node of the inter-domain connection service After detecting a service fault, the fault detection node of the inter-domain connection service sends the identifier to the first node of the inter-domain connection service.
  • Step S12 The first node of the inter-domain connection service determines the faulty cross-domain connection service according to the call identifier, and performs end-to-end connection recovery on the determined faulty cross-connection service according to the failed link information in the cross-domain connection service. .
  • the end-to-end connection service of the inter-domain connection service can greatly improve the survivability of the inter-domain connection service.
  • FIG. 3 is a schematic diagram of an end-to-end fault recovery according to an embodiment of the present invention.
  • the resource reservation protocol-traffic engineering RSVP-TE signaling may be used.
  • the first node Nil of the inter-AS connection label switching path (LSP, Label Switch Path) is restored in an end-to-end manner.
  • the call identifier CALL-ID object defined by the standard in the present invention uniquely identifies a cross-domain end-to-end service, for a case where there are multiple connections in a service, such as 1 + 1 service or cascading service, each connection
  • the call identifiers CALL_IDs are the same.
  • the present invention can use the index of the active/standby identifier field in the RSVP message of the extended resource reservation protocol to distinguish the connections in the service.
  • the index number is extended in the RSVP message.
  • the method of the field may be to use the Secondary field in the extended RSVP-PROTECTION object, and use the value of the extended field to distinguish different connections in a cross-domain connection service; for different connections in the 1+1 service or the cascade service Since the connection is distinguished by the call identification CALL_ID and the index number, each connection is independently restored in the event of a failure.
  • the node ID of the first node can be brought to each domain through the Notify Request object in RSVP, or can be converted by the Transmit Network Address (TNA) address.
  • TAA Transmit Network Address
  • the unique identifier of the cross-domain connection service that fails that is, the call identity CALL_ID and index number field information, and the failed link information, etc.
  • pass the RSVP message After obtaining the head node ID of the end-to-end connection, the unique identifier of the cross-domain connection service that fails, that is, the call identity CALL_ID and index number field information, and the failed link information, etc., pass the RSVP message.
  • the first node sent to the cross-domain connection service is restored.
  • the connection controller on the first node of the inter-domain connection service can re-calculate the route query to the cross-domain service according to the failed link information.
  • the protocol controller on the node initiates the establishment of the recovery connection path of the first node to the destination node; after the connection path is established, the service is bridged The faulty traffic on this link is bridged to the recovery connection path.
  • the end-to-end connection recovery of the cross-domain connection service is performed.
  • the call identity CALL-ID and index number of the cross-domain connection service are then unchanged.
  • an instance value field may be extended in the object of the RSVP message to distinguish, for example, a field is extended in the RSVP_PROTECTION object, and is carried downstream.
  • the service fault recovery method provided by the present invention can be applied when a failure occurs in a downstream domain of an end-to-end connection and a failure fails, or an intra-domain failure recovery failure or an inter-domain link failure does not use a fast recovery method or inter-domain between domains.
  • the fast recovery cannot be completed.
  • the end-to-end recovery of the inter-domain connection service can ensure the survivability of the inter-domain connection service. The following describes the specific implementation.
  • connection service across multiple domains. Because it is not a 1 + 1 service and a cascading service, there is only one connection for the inter-AS connection service.
  • the route of the connection is N11-> ⁇ 12-> ⁇ 13-> ⁇ 21-> ⁇ 22-> ⁇ 23-> ⁇ 31-> ⁇ 32-> ⁇ 33, the connection is established in 5 segments, Nil to N13 session, N13 to N21 session across ENNI interface, N21 to N23 session The 23 to N31 session across the ENNI interface and the last N31 to N33 session, through which the entire end-to-end connection is established.
  • the connection of the service is distinguished from other services by the call identifier CALL_ID. Since it is not 1+1 and the cascading service, the index number of the connection can be set to 1, and the instance value field before recovery can be 1 .
  • the call identity CALL_ID and index number fields of the connection service and the failed link N13->N21 information are searched on N13, and then N13 is sent.
  • the RSVP message notifies the first node Nil of the end-to-end connection of the cross-domain connection service, and re-initiates a connection identifier CALL_ID with the same value of the index value and the same instance value as the original cross-domain connection service on the Nil.
  • the intra-domain recovery may be performed first in N21, and when there is no resource in the domain and the recovery fails.
  • the N21 can find the call identifier CALL_ID and the index number Index information of the end-to-end cross-domain connection service, and send the information to the first node of the cross-domain connection service, and the first node of the cross-domain connection service initiates the end-to-end connection. restore.
  • the embodiment of the invention further provides a service fault recovery system, which is used for cross-domain connection service.
  • End-to-end connection recovery including:
  • a fault detecting unit configured to detect a service fault, and send, to the head node of the cross-domain connection service, a call identifier that identifies the faulty cross-domain connection service and the failed link information in the cross-domain connection service;
  • the first node of the inter-domain connection service recalculates the route according to the failed link information, and obtains the restoration connection path of the destination node of the inter-domain connection service;
  • the fault recovery unit performs end-to-end connection recovery on the faulty cross-domain connection service according to the failed link information and the recovery connection path in the cross-domain connection service.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Hardware Redundancy (AREA)
  • Vehicle Body Suspensions (AREA)

Description

业务故障恢复方法及系统
本申请要求于 2006 年 01 月 10 日提交中国专利局、 申请号为 200610032780.3、 发明名称为 "业务故障恢复方法，， 的中国专利申请的优 先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及网络及通信技术领域， 尤其涉及一种跨域的业务故障恢 复方法及系统。 ' 背景技术
传统光网络的业务调度采用网管静态配置的方式， 不支持动态开通 的方式， 同时传统光网络大多采用线性和环形组网， 保护恢复采用复用 段保护和子网连接保护， 基本是一种静态的恢复方法， 但随着数据业务 和专线业务的迅速发展， 对网络的带宽需求逐渐增强， 对网络带宽的动 态分配要求也越来越迫切， 需要网络提供动态开通的能力， 需要支持网 状网的结构， 同时具有灵活的扩展能力和快速的保护恢复功能， 自动交 换光网络（ ASON, Automatic Switch Optical Network )很好的解决了上述 问题， 它在控制平面使用通用多协议标记交换 ( GMPLS , Generalized Multiprotocol Label Switching )协议， 已成为光网给发展的一个核心技术， 在 ASON中提供了 2种新的连接类型： 一种是软永久连接方式， 另一种是 交换连接方式。 目前国际电信联盟 ITU - T已经基本完成了 ASON的架构 和需求定义， 因特网工程任务组 IETF则完成了单域内信令、 自动发现、 路由的协议扩展和定义。
随着 ASON网络的发展， 控制平面需要解决大规模网络的管理问题， 目前 ITU - T， 光互联网论坛 OIF中都采用层次网络的模型， 将下层的一个 控制域在上层用一个代理节点表示， 代理节点可以发布代表域的抽象拓 朴， 域间链路， 可达地址等， 这样逐层向上形成一个层次的网络， 例如 图 1中， 0层为实际的网络，划分为多个控制域，如 CD1， CD2, CD3和 CD4 在 1层， 每个域抽象为一个节点， 即图中 RC11 , RC12, RC13和 RC14依次 类推， 整个网络成为一个 3层的网络拓朴。 在多域的网络中， 连接恢复速度成为一个非常重要的瓶颈， 因为多 域情况下， 连接跨越多个域， 经过的节点数远远多于单域的情况， 这成 为网络扩展后的一个急需解决的问题， 通常对于跨域连接业务， 在域内 故障时， 一般采用域内隧道的方式进行局部恢复， 当域间链路故障时， 通常采用域间的保护或快速恢复机制进行恢复。 但如果域内带宽资源不 足导致域内无法恢复或者域间链路故障而使用的域间快速恢复方式失效 或者没有相关域间快速恢复的方法时就需要进行端到端连接的恢复， 但 跨域连接需要走外部网络接口 （ ENNI, External Node-Node Interface )信 令， 在连接的建立过程中需要分段建立会话过程， 由于不能具体确定跨 域连接业务的整个端到端跨域连接业务， 故障检测节点无法上报业务的 首节点故障跨域连接业务信息， 从而导致跨域连接业务的端到端连接恢 复难以进行， P争低了跨域连接业务的生存能力。 发明内容
本发明实施例提供一种业务故障恢复方法及系统， 可实现跨域连接 业务的端到端连接恢复， 提高跨域连接业务的生存能力。
本发明实施例提供一种业务故障恢复方法， 用于实现跨域连接业务 的端到端连接恢复， 该方法包括：
跨域连接业务的故障检测节点向跨域连接业务的首节点发送标识该 跨域连接业务的呼叫标识以及该跨域连接业务中失效链路信息；
跨域连接业务的首节点根据所述呼叫标识确定故障的跨域连接业 务；
根据该跨域连接业务中失效链路信息对所述确定的故障的跨域连接 业务进行端到端连接恢复。
本发明实施例提供一种业务故障恢复系统， 用于跨域连接业务的端 到端连接恢复， 包括：
故障检测单元， 用于检测业务故障， 并向跨域连接业务的首节点发 送标识所述故障的跨域连接业务的呼叫标识以及该跨域连接业务中失效 链路信息；
跨域连接业务的首节点， 根据失效链路信息重新计算路由， 得到跨 域连接业务的目的节点的恢复连接路径；
故障恢复单元， 根据该跨域连接业务中失效链路信息及恢复连接路 径对所述故障的跨域连接业务进行端到端连接恢复。
从上述本发明实施例的技术方案中可以看出， 本发明实施例通过采 用标准定义的呼叫标识对象唯一标识一条跨域连接业务， 在检测到业务 故障后， 跨域连接业务的故障检测节点向跨域连接业务的首节点发送标 识该跨域连接业务的呼叫标识以及该跨域连接业务中失效链路信息； 跨 域连接业务的首节点根据所述呼叫标识以及该跨域连接业务中失效链路 信息对相应跨域连接业务进行端到端连接恢复， 从而实现跨域连接业务 的端到端连接恢复， 提高了跨域连接业务的生存能力。 附图说明
图 1是现有技术层次网络的模型示意图；
图 2是本发明实施例中业务故障方法的实现流程图；
图 3是本发明实施例中一种端到端故障恢复示意图；
图 4是根据本发明提供的业务故障恢复方法的具体实施例中故障恢 复示意图。 具体实施方式
为使本发明的原理、 特性和优点更加清楚， 下面结合具体实施例对 本发明予以详细描述。
如图 2所示， 本发明实施例中业务故障恢复方法实现的主要流程如 下：
步骤 S11 ,本发明采用标准定义的呼叫标识对象唯一标识一条跨域连 接业务， 在检测到业务故障后， 由跨域连接业务的故障检测节点向跨域 连接业务的首节点发送标识该跨域连接业务的呼叫标识以及该跨域连接 业务中失效链路信息；
步骤 S12,跨域连接业务的首节点根据所述呼叫标识确定故障的跨域 连接业务， 根据该跨域连接业务中失效链路信息对所述确定的故障的跨 连接业务进行端到端连接恢复。 由于实现了跨域连接业务的端到端连接服务， 可以大大提高跨域连 接业务的生存能力， 下面详细进行说明。
图 3所示为本发明实施例中的一种端到端故障恢复示意图，参照图 3 , 当域间链路 N13-N21故障时， 可通过资源预留协议-流量工程 RSVP - TE 信令通知跨域连接业务标签交换路径 ( LSP, Label Switch Path ) 的首节 点 Nil , 采用端到端方式进行恢复。 为此， 本发明中采用标准定义的呼叫 标识 CALL— ID对象唯一标识一条跨域端到端的业务，对于一条业务里有 多条连接的情况， 例如 1 + 1 业务或级联业务， 每条连接的呼叫标识 CALL— ID 均相同，本发明可采用扩展资源预留协议 RSVP消息里主备标 识字段携带索引号加以区别该业务里的各条连接； 具体的， 所述在 RSVP 消息里扩展索引号字段的方法可以是采用扩展 RSVP— PROTECTION对 象中的 Secondary字段，利用扩展该字段取值来区别一条跨域连接业务里 的各条不同连接； 对于 1 + 1业务或者级联业务中不同连接来说， 由于采 用呼叫标识 CALL— ID和索引号已经将连接区别开来， 因此各个连接在出 现故障时独立 1复。
首节点的节点 ID可以通过 RSVP里的 Notify Request对象一直带到 各个域去 , 也可以通过传输网络地址（ TNA, Transmit Network Address ) 地址转换而成。 当发生故障需要进行端到端连接的恢复时， 需要由故障 检测点发消息给端到端连接的首节点进行恢复。
本发明中在获得端到端连接的首节点 ID后， 将发生故障的跨域连接 业务的唯一标识也就是所述的呼叫标识 CALL— ID和索引号字段信息以及 失效链路信息等通过 RSVP 消息发送给该条跨域连接业务的首节点进行 恢复， 具体实现时， 可由跨域连接业务的首节点上的连接控制器根据失 效链路信息排除故障链路重新计算路由查询到跨域业务的目的节点的恢 复连接路径； 在所述连接控制器获得恢复连接路径后， 由其上的协议控 制器启动所述首节点到目的节点的恢复连接路径的建立； 恢复连接路径 建立后， 进行业务的桥接， 将此链路上的故障业务桥接到所述的恢复连 接路径上。
需要说明的， 本发明实施例中， 在跨域连接业务的端到端连接恢复 之后该跨域连接业务的呼叫标识 CALL一 ID和索引号都不发生改变。为了 在该首节点区分恢复之前的跨域连接业务和恢复之后的跨域连接业务， 可在 RSVP 消息的对象里扩展一个实例值字段来区分， 例如在 RSVP_PROTECTION对象中扩展一个字段， 一直携带到下游的各个域。
本发明提供的业务故障恢复方法可以应用在端到端连接的下游域内 发生故障而恢复失败时， 或者域内故障恢复失效或者是域间链路故障而 域间没有釆用快速恢复方法或者域间的快速恢复无法完成， 通过跨域连 接业务的端到端恢复， 可以最大程度地保证跨域连接业务的生存性， 下 面以具体实施例进行说明。
如图 4所示网络中， 有一条跨多域的连接业务， 由于不是 1 + 1业务 和级联业务， 因此该跨域的连接业务只有一条连接， 该连接的路由为 N11->Ν12->Ν13->Ν21->Ν22->Ν23->Ν31->Ν32->Ν33 , 该连接是分 5段建 立会话的， 分别为 Nil至 N13会话、 跨 ENNI接口的 N13至 N21会话、 N21至 N23会话、 跨 ENNI接口的 23至 N31会话以及最后的 N31至 N33会话， 通过这 5段会话才建立起整条端到端的连接。 本实施例用呼 叫标识 CALL— ID将该业务的连接和其它业务区分， 由于不是 1 + 1和级 联业务， 因此该连接的索引号可设定为 1 ,恢复之前的实例值字段可为 1。
如图 4所示， 当域间链路 N13-N21出现故障时， 在 N13上查找出该 连接业务的呼叫标识 CALL— ID和索引号字段以及失效链路 N13->N21信 息， 然后 N13通过发 RSVP消息通知该跨域连接业务的端到端连接的首 节点 Nil , 在 Nil 上重新发起建立一条与原跨域连接业务的呼叫标识 CALL— ID和索引号值相同而实例值不同的连接， 具体为图 4中的连接： Nl 1->Ν16->Ν15->Ν14->N26->N25->N24->N35->N33。
需要说明的， 本发明实施例中， 如果在图 4 所示的域内链路失效后 如 N21和 N22之间的链路故障， 则可首先在 N21进行域内恢复， 当域内 没有资源而恢复失败时， N21 可找到该端到端跨域连接业务的呼叫标识 CALL— ID和索引号 Index信息， 发送给该跨域连接业务的首节点， 由该 跨域连接业务的首节点发起端到端连接的恢复。
本发明实施例中还提供一种业务故障恢复系统， 用于跨域连接业务 的端到端连接恢复， 包括：
故障检测单元， 用于检测业务故障， 并向跨域连接业务的首节点发 送标识所述故障的跨域连接业务的呼叫标识以及所述跨域连接业务中失 效链路信息；
跨域连接业务的首节点， 根据失效链路信息重新计算路由， 得到跨 域连接业务的目的节点的恢复连接路径；
故障恢复单元， 根据所述跨域连接业务中失效链路信息及恢复连接 路径对所述故障的跨域连接业务进行端到端连接恢复。
以上所述仅是本发明的优选实施方式， 本发明的实施方式不限于此， 可以理解， 对于本技术领域的普通技术人员来说， 在不脱离本发明原理 的前提下， 可进行各种修改和润饰， 这些改进和润饰涵盖在本发明的保 护范围内。

Claims

权 利 要 求
1、 一种业务故障恢复方法， 用于实现跨域连接业务的端到端连接 恢复， 其特征在于， 包括：
跨域连接业务的故障检测节点向跨域连接业务的首节点发送标识跨 域连接业务的呼叫标识以及所述跨域连接业务中失效链路信息；
跨域连接业务的首节点根据所述呼叫标识确定故障的跨域连接业 务；
根据所述跨域连接业务中失效链路信息对所述确定的故障的跨域连 接业务进行端到端连接恢复。
2、 根据权利要求 1所述的业务故障恢复方法， 其特征在于， 对同一 业务中的连接采用相同的呼叫标识。
3、 根据权利要求 1所述的业务故障恢复方法， 其特征在于， 所述跨 域连接业务包括多条连接， 各连接以不同的索引号标识， 跨域连接业务 的故障检测节点还向跨域连接业务的首节点发送标识所述跨域连接业务 中故障连接的索引号；
所述确定故障的跨域连接业务具体包括：
跨域连接业务的首节点根据标识所述跨域连接业务的呼叫标识和标 识所述跨域连接业务中故障连接的索引号确定跨域连接业务中故障的连 接。
4、 根据权利要求 3所述的业务故障恢复方法， 其特征在于， 所述呼 叫标识和索引号通过资源预留协议消息发送给跨域连接业务的首节点。
5、 根据权利要求 4所述的业务故障恢复方法， 其特征在于， 所述资 源预留协议消息为通知消息， 其中的对象中携带标识跨域连接业务中故 障连接的索引号。
6、 根据权利要求 2所述的业务故障恢复方法， 其特征在于， 对所述 确定的跨域连接业务中的故障连接进行端到端连接恢复具体包括：
跨域连接业务的首节点根据失效链路信息重新计算路由， 得到跨域 连接业务的目的节点的恢复连接路径；
所述首节点获得恢复连接路径后， 启动所述首节点到目的节点的恢 复连接路径的建立；
恢复连接路径建立后， 将此链路上的故障业务桥接到所述的恢复连 接路径上。
7、 根据权利要求 1所述的业务故障恢复方法， 其特征在于， 通过资源预留协议 RSVP的对象携带首节点的 ID到各个域， 或通过 传输网络地址 TNA转换得到首节点的 ID;
当发生故障需要进行端到端连接的恢复时 , 故障检测点根据所迷首 节点 ID发消息给端到端连接的首节点进行恢复。
8、 根据权利要求 1所述的业务故障恢复方法， 其特征在于， 当跨域连接业务的端到端连接恢复之后， 所述跨域连接业务的呼叫 标识 CALL— ID和索引号保持不变，在 RSVP消息的对象里扩展一个字段， 携带所述呼叫标识 CALL—ID和索引号到下游的各个域， 以区分恢复之前 和恢复之后的跨域连接业务。
9、 根据权利要求 1至 6中任一项所述的业务故障恢复方法， 其特征 在于， 所述业务为 1 + 1业务或级联业务。
10、 根据权利要求 1至 6中任一项所述的业务故障恢复方法， 其特 征在于， 进一步包括：
若域内链路故障， 则在相应节点进行或内恢复；
当域内恢复失败时， 找到所述端到端跨域连接业务的呼叫标识 CALL— ID和索引号 Index信息， 发送给所述跨域连接业务的首节点， 以 发起端到端连接的恢复。
11、 一种业务故障恢复系统， 用于跨域连接业务的端到端连接恢复， 其特征在于， 包括:
故障检测单元， 用于检测业务故障， 并向跨域连接业务的首节点发 送标识所述故障的跨域连接业务的呼叫标识以及所述跨域连接业务中失 效链路信息；
跨域连接业务的首节点， 根据失效链路信息重新计算路由， 得到跨 域连接业务的目的节点的恢复连接路径；
故障恢复单元， 根据所述跨域连接业务中失效链路信息及恢复连接 路径对所述故障的跨域连接业务进行端到端连接恢复。
12、 根据权利要求 11所述的业务故障恢复系统， 其特征在于， 当发生故障需要进行端到端连接的恢复时， 故障检测单元根据所述 首节点 ID发消息给端到端连接的首节点进行恢复。
PCT/CN2006/003722 2006-01-10 2006-12-30 Procédé et système de restauration de services ayant subi un problème WO2007079659A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP06840752A EP1973267B1 (en) 2006-01-10 2006-12-30 A service failure restoration method and system
DE602006016337T DE602006016337D1 (de) 2006-01-10 2006-12-30 Dienstausfall-wiederherstellungsverfahren und system
CNA2006800117358A CN101156367A (zh) 2006-01-10 2006-12-30 业务故障恢复方法及系统
AT06840752T ATE478492T1 (de) 2006-01-10 2006-12-30 Dienstausfall-wiederherstellungsverfahren und system
US12/102,421 US8289843B2 (en) 2006-01-10 2008-04-14 Service failure recovery method and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2006100327803A CN100490390C (zh) 2006-01-10 2006-01-10 业务故障恢复方法
CN200610032780.3 2006-01-10

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/102,421 Continuation US8289843B2 (en) 2006-01-10 2008-04-14 Service failure recovery method and system

Publications (1)

Publication Number Publication Date
WO2007079659A1 true WO2007079659A1 (fr) 2007-07-19

Family

ID=38255977

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003722 WO2007079659A1 (fr) 2006-01-10 2006-12-30 Procédé et système de restauration de services ayant subi un problème

Country Status (7)

Country Link
US (1) US8289843B2 (zh)
EP (1) EP1973267B1 (zh)
CN (2) CN100490390C (zh)
AT (1) ATE478492T1 (zh)
DE (1) DE602006016337D1 (zh)
ES (1) ES2348362T3 (zh)
WO (1) WO2007079659A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8289843B2 (en) 2006-01-10 2012-10-16 Huawai Technologies Co., Ltd. Service failure recovery method and system
WO2013091170A1 (zh) * 2011-12-20 2013-06-27 华为技术有限公司 一种处理设备故障的方法、装置及系统

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7995914B2 (en) * 2008-03-28 2011-08-09 Mci Communications Services, Inc. Method and system for providing fault recovery using composite transport groups
CN101309525B (zh) * 2008-06-30 2011-03-16 中兴通讯股份有限公司 一种自动交换光网络中依据故障定位的路由恢复方法
CN101715149B (zh) * 2009-07-21 2013-01-23 北京邮电大学 一种多层多域分布式光网络并行跨域故障恢复方法和装置
CN101998181B (zh) * 2009-08-10 2013-09-11 中兴通讯股份有限公司 Sncp业务迁移方法及装置
CN101763321B (zh) * 2010-02-24 2013-01-02 华为技术有限公司 数据容灾的方法、装置及系统
EP2426858B1 (en) * 2010-09-01 2012-10-31 Alcatel Lucent Method and apparatus for restoring a connection through a provider network upon request
US8804485B2 (en) * 2011-05-06 2014-08-12 Tellabs Operations, Inc. Method and apparatus for coordinating fault recovery techniques among domains
CN102291255B (zh) * 2011-07-22 2014-09-10 中国电力科学研究院 一种电力系统广域保护的通信网络节点装置及其实现方法
CN104054283A (zh) * 2012-01-24 2014-09-17 瑞典爱立信有限公司 用于优化光网络的重新配置的设备和方法
CN103580904A (zh) * 2012-08-08 2014-02-12 中兴通讯股份有限公司 域间故障信息的发送方法及装置
CN104348720B (zh) * 2013-07-25 2018-05-04 中兴通讯股份有限公司 一种多域路径计算失败的处理方法及路径计算单元
US9608859B2 (en) * 2013-10-25 2017-03-28 Aruba Networks, Inc. System, apparatus and method for reducing failover time through redundancy using virtual access points
CN103731312A (zh) * 2014-01-26 2014-04-16 飞狐信息技术（天津）有限公司 对远程方法调用的服务进行故障检查的方法和装置
CN105005469B (zh) * 2015-06-03 2018-04-13 浙江大学 一种基于Zookeeper和RabbitMQ的非阻塞调用方法
CN106330294A (zh) * 2015-06-18 2017-01-11 中兴通讯股份有限公司 光通讯网络中的业务控制方法及装置
WO2018053747A1 (zh) * 2016-09-22 2018-03-29 华为技术有限公司 资源共享方法、网络节点及相关设备
CN110048944A (zh) * 2018-01-17 2019-07-23 中兴通讯股份有限公司 端到端重路由的方法及装置
CN112737937B (zh) * 2019-10-14 2022-09-16 中国电信股份有限公司 信息跨域通告方法、系统和边界路由器
CN111565145B (zh) * 2020-04-09 2022-07-01 烽火通信科技股份有限公司 一种跨域路径保护方法及系统
CN113286208B (zh) * 2021-06-15 2022-04-26 烽火通信科技股份有限公司 资源短缺时无源故障恢复方法和系统
CN114285602B (zh) * 2021-11-26 2024-02-02 成都安恒信息技术有限公司 一种分布式业务安全检测方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6111881A (en) 1997-12-29 2000-08-29 Nortel Networks Corporation Signaling protocol for rerouting ATM connections in PNNI environments
JP2001036587A (ja) * 1999-07-22 2001-02-09 Fujitsu Ltd ネットワーク管理システム
CN1674527A (zh) * 2005-04-15 2005-09-28 清华大学 一种增强自动交换光网络生存性的方法
CN1710868A (zh) * 2005-07-14 2005-12-21 广东省电信有限公司研究院 自动交换光网络中主备保护的跨域端到端连接的建立方法
CN1798051A (zh) * 2004-12-24 2006-07-05 中兴通讯股份有限公司 跨越多域连接的网络故障恢复的方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6292463B1 (en) * 1998-07-06 2001-09-18 Alcatel Canada Inc. Method and apparatus for recovering from a signalling failure in a switched connection data transmission network
US7426179B1 (en) 2000-03-17 2008-09-16 Lucent Technologies Inc. Method and apparatus for signaling path restoration information in a mesh network
US7471625B2 (en) 2001-10-31 2008-12-30 Nec Corporation Fault recovery system and method for a communications network
US20040107382A1 (en) * 2002-07-23 2004-06-03 Att Corp. Method for network layer restoration using spare interfaces connected to a reconfigurable transport network
CN100369419C (zh) 2005-07-14 2008-02-13 广东省电信有限公司研究院 自动交换光网络中连接的增强型主备保护的实现方法
CN100490390C (zh) 2006-01-10 2009-05-20 华为技术有限公司 业务故障恢复方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6111881A (en) 1997-12-29 2000-08-29 Nortel Networks Corporation Signaling protocol for rerouting ATM connections in PNNI environments
JP2001036587A (ja) * 1999-07-22 2001-02-09 Fujitsu Ltd ネットワーク管理システム
CN1798051A (zh) * 2004-12-24 2006-07-05 中兴通讯股份有限公司 跨越多域连接的网络故障恢复的方法
CN1674527A (zh) * 2005-04-15 2005-09-28 清华大学 一种增强自动交换光网络生存性的方法
CN1710868A (zh) * 2005-07-14 2005-12-21 广东省电信有限公司研究院 自动交换光网络中主备保护的跨域端到端连接的建立方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8289843B2 (en) 2006-01-10 2012-10-16 Huawai Technologies Co., Ltd. Service failure recovery method and system
WO2013091170A1 (zh) * 2011-12-20 2013-06-27 华为技术有限公司 一种处理设备故障的方法、装置及系统
US9219642B2 (en) 2011-12-20 2015-12-22 Huawei Technologies Co., Ltd. Method, apparatus and system for processing device faults

Also Published As

Publication number Publication date
CN101001170A (zh) 2007-07-18
EP1973267B1 (en) 2010-08-18
EP1973267A4 (en) 2009-01-28
ATE478492T1 (de) 2010-09-15
CN100490390C (zh) 2009-05-20
DE602006016337D1 (de) 2010-09-30
US8289843B2 (en) 2012-10-16
ES2348362T3 (es) 2010-12-03
US20080192626A1 (en) 2008-08-14
EP1973267A1 (en) 2008-09-24
CN101156367A (zh) 2008-04-02

Similar Documents

Publication Publication Date Title
WO2007079659A1 (fr) Procédé et système de restauration de services ayant subi un problème
Huang et al. Building reliable MPLS networks using a path protection mechanism
US7180866B1 (en) Rerouting in connection-oriented communication networks and communication systems
CN101160761B (zh) 链路故障的恢复方法及装置
WO2007128176A1 (fr) Procédé de commutation de service et noeud de réseau associé
US8149693B2 (en) Method of implementing association in automatic switched optical network (ASON)
EP1953958B1 (en) Management of protection path bandwidth and changing of path bandwidth
WO2006099784A1 (fr) Procédé de détection d’un défaut de liaison entre des noeuds d’une extrémité à l’autre dans un réseau hybride
WO2007054032A1 (en) Communication network system and leaf-node network element of the multicasting tree signal transmission method and node network element thereof
WO2008037198A1 (fr) Procédés de mise en oeuvre de réacheminement rapide multidiffusion et noeud
WO2006069523A1 (fr) Procede de recuperation de redemarrage de noeud dans un trajet de commutation multiprotocole par etiquette
WO2011157130A2 (zh) 路径建立方法和装置
WO2008119294A1 (fr) Procédé et matériel de restauration du commerce en réseau
WO2009146652A1 (zh) 一种自动交换光网络中连接迁移方法和系统
WO2010028560A1 (zh) 在mesh网络中实现永久环网保护的方法
WO2012071909A1 (zh) 业务恢复方法及装置
WO2007036101A1 (fr) Systeme et procede de protection de voie de service multidiffusion
WO2008037162A1 (fr) Procédé de gestion de services dans un réseau optique intelligent
WO2015024440A1 (zh) 一种获取ip链路的链路开销值的方法及系统
US20030043427A1 (en) Method of fast circuit recovery using local restoration
WO2012075914A1 (zh) 一种实现点到多点标签交换路径保护的方法及系统
KR100842256B1 (ko) 지.엠.피.엘.에스 기반 네트워크에서 물리계층의 레이블 스위칭 경로에 대한 연결성 검사 방법 및 그 시스템
WO2018053747A1 (zh) 资源共享方法、网络节点及相关设备
WO2014059570A1 (zh) 建立标签交换路径的方法、设备和系统
Austin et al. Fast, scalable, and distributed restoration in general mesh optical networks

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 200680011735.8

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2006840752

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 2006840752

Country of ref document: EP