WO2007071189A1 - Procede et dispositif de restauration d'un reseau maille partage - Google Patents

Procede et dispositif de restauration d'un reseau maille partage Download PDF

Info

Publication number
WO2007071189A1
WO2007071189A1 PCT/CN2006/003503 CN2006003503W WO2007071189A1 WO 2007071189 A1 WO2007071189 A1 WO 2007071189A1 CN 2006003503 W CN2006003503 W CN 2006003503W WO 2007071189 A1 WO2007071189 A1 WO 2007071189A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
recovery path
network
routing information
recovery
Prior art date
Application number
PCT/CN2006/003503
Other languages
English (en)
French (fr)
Inventor
Yongliang Xu
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
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to AT06828409T priority Critical patent/ATE458320T1/de
Priority to DE602006012318T priority patent/DE602006012318D1/de
Priority to CNA2006800122036A priority patent/CN101160901A/zh
Priority to EP06828409A priority patent/EP1898584B1/en
Publication of WO2007071189A1 publication Critical patent/WO2007071189A1/zh
Priority to US12/019,025 priority patent/US7787362B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/14—Monitoring arrangements
    • 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
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby 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
    • 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
    • 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
    • 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
    • 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]
    • 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/62—Wavelength based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/15—Flow control; Congestion control in relation to multipoint traffic
    • 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/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]
    • 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/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/726—Reserving resources in multiple paths to be used simultaneously
    • H04L47/728—Reserving resources in multiple paths to be used simultaneously for backup paths
    • 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/74—Admission control; Resource allocation measures in reaction to resource unavailability
    • H04L47/746—Reaction triggered by a failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • 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
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0057—Operations, administration and maintenance [OAM]
    • H04J2203/006—Fault tolerance and recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0064—Admission Control
    • H04J2203/0067—Resource management and allocation
    • 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/009—Topology aspects
    • H04Q2011/0098—Mesh

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a method and an apparatus for implementing shared grid network recovery. Background of the invention
  • Optical transport networks including SDH (Synchronous Digital Hierarchy), SONET (Synchronous Optical Network), and OT (Optical Transport Network), are traditionally designed to transmit voice services.
  • SDH Serial Digital Hierarchy
  • SONET Synchronous Optical Network
  • OT Optical Transport Network
  • This new type of optical transmission network is called the ASON (Automatic Switched Optical Network) by the ITU-T (ITU-Standardization Department).
  • the ASON is introduced into the control plane for establishing, modifying, and maintaining network connections, and implementing connection recovery in the event of a network failure.
  • GMPLS Generalized Multi-Protocol Label Switching
  • Recovery path pre-establishment It is to establish a fault-independent recovery path for the working path before the network failure occurs. (The two paths are irrelevant. It means that the two paths will not be interrupted at the same time due to the same network failure. It is irrelevant that the two paths do not pass through the same link and do not pass through the same SRLG (Shared-Risk Link Group).
  • SRLG Shared-Risk Link Group
  • the path is pre-computed, and the network resources are reserved according to the sharing mode. After the network failure occurs, the recovery path is dynamically established.
  • This protection mode is usually called “shared grid recovery”.
  • the advantage of this protection mode is that resource reservation is performed by reasonably planning the work and recovery paths of each network connection requirement.
  • the recovery path can improve resource utilization through resource sharing, but the recovery time is longer than the recovery path pre-establishment mode, usually at 200 ms. Left or right or longer.
  • the protection path is established as needed, that is, after a network failure occurs, a recovery path is calculated and an attempt is made to restore the connection.
  • the advantage of this protection method is that it can support network failure conditions that cannot be predicted in advance, such as multiple network failures.
  • the disadvantage is that there is no pre-requisite resource reservation, which cannot ensure the connection is restored, the reliability is poor, and the recovery time is longer. It takes a few seconds.
  • the protection mode of shared grid recovery has the reliability of connection recovery and high resource utilization, it is a kind of service protection and recovery method that the industry considers to be very effective.
  • the work and recovery paths are all established using the RSVP-TE protocol of the RPC3743 specification.
  • the extension of the protocol adds a "PROTECTION" object, among which One bit (hereinafter referred to as "S bit") is used to indicate the recovery path of the shared grid. If the S bit is set to 1, the control plane only reserves resources and does not establish a cross-connection. If the network fails, the bit is set to 0 after the working path is interrupted.
  • the control plane initiates a cross-connection and uses the reserved resources to establish a recovery path.
  • the process of establishing resource reservation and cross-connection requires signaling interaction to complete. Specifically, the following steps are included:
  • the network ingress node of the network connection service (referred to as the ingress node) first determines the source routing information of the working path, and establishes a working path through the signaling protocol;
  • the ingress node determines the source routing information of the recovery path, and "establishes" the recovery path by signaling.
  • the difference from the establishment of the working path is that the S bit of the establishment of the recovery path is set to 1, and the nodes on the recovery path are restored. Only the link resources are reserved, and no cross-connection is established. Therefore, the recovery path is not connected when the working path is normal.
  • the signaling session of the recovery path in the life cycle of the entire network connection service needs to be maintained as well as the signaling session of the working path;
  • the S bit position of the path signaling will be restored to 0.
  • the modification is transmitted by the signaling message refresh along the node on the recovery path, and the used nodes are reserved.
  • the resources establish a cross-connection of the recovery path, and the ingress node and the egress node also switch the network connection service from the working path to the recovery path for transmission.
  • the embodiment of the invention provides a method and a device for implementing the recovery of the shared grid network.
  • the technical solution is simple and easy to implement, and can be implemented by using an existing protocol, and can be well compatible with existing devices. .
  • An embodiment of the present invention provides a method for implementing shared lattice network recovery, including the following steps:
  • the network ingress node of the network connection server determines the routing information of the recovery path and saves; after the working path is successfully established, the network management system controls the resource reservation processing of the recovery path;
  • the network ingress node of the network connection server initiates a recovery path establishment process by using the reserved resources according to the saved routing information of the recovery path;
  • the embodiment of the invention provides an implementation device for restoring a grid network recovery, comprising: a routing information saving module, a resource reservation control module, a path establishing module and a path switching module,
  • the routing information saving module is configured to determine and save routing information of the recovery path
  • the resource reservation control module is configured to control, according to the routing information of the recovery path saved by the routing information saving module, a resource reserved for the recovery path;
  • the path establishing module is configured to establish a recovery path according to the routing information of the recovery path saved by the routing information saving module and the resource reserved by the resource reservation control module for the restoration path;
  • the path switching module is configured to switch the service on the working path of the fault to the recovery path corresponding to the working path that the path establishing module has established.
  • the existing protocol such as RSVP-TE
  • RSVP-TE can be used to implement shared grid recovery without the need to extend the protocol, so the technical solution is simple and easy to implement, and can be well compatible with existing devices;
  • the signaling process is started as needed after the network failure occurs, causing the control channel to maintain the connection state and reduce the data communication.
  • the communication traffic of the network saves network resources
  • the network management system centrally maintains the relationship between the recovery path resource and the recovery path and the network connection service, and the control plane only needs to maintain the number of resources reserved for use in the recovery path, thereby simplifying the implementation of the control plane. .
  • FIG. 2 is a schematic structural diagram of a shared lattice network according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a device module according to an embodiment of the present invention.
  • the network ingress node of the network connection service determines the routing information of the restoration path and saves; after the working path is successfully established, the network management system controls the resource reservation processing of the recovery path; when the working path is interrupted, The network ingress node of the network connection server initiates a process of establishing a recovery path according to the saved routing information of the recovery path, and uses the reserved resource, and switches the service of the working path to the recovery path for transmission. .
  • FIG. 1 is a working flow diagram of a method according to an embodiment of the present invention. and the following steps are included:
  • Step 11 Determine the routing of the working and recovery paths.
  • the network management system sends a connection establishment request to a network ingress node (hereinafter referred to as an entry node) of the network connection server;
  • the ingress node parses the request after receiving the connection establishment request message. If the request message carries the routing information of the working path and the recovery path of the strict explicit route, the routing information is used as the routing information of the working path and the recovery path and will be restored. The routing information of the path is saved;
  • the ingress node calculates the route of the working path and/or the recovery path, and saves the recovery path. Routing information.
  • the strict explicit routing information includes: a sequence of links through which the path passes in sequence, and the link is usually composed of a node identifier and a port identifier, and is called a link identifier.
  • the loose explicit routing information refers to missing part or all of the routing information of the link.
  • Step 12 Establish a working path.
  • the ingress node determines the route of the working path and the recovery path, the establishment process of the working path is initiated.
  • the working path can be established as follows:
  • the ingress node sends a connection establishment request of the working path to each node in turn according to the routing information of the working path through the GMPLS extended signaling protocol (such as RSVP-TE protocol) until the last node where the working path is located [below Referred to as the egress node), in this process each node receives a connection establishment request and then reserves resources;
  • GMPLS extended signaling protocol such as RSVP-TE protocol
  • each node of the working path from the egress node sequentially establishes a corresponding cross-connection in the opposite direction of the connection establishment request of the working path and returns the connection to the next node after the cross-connection is established. Establish a response until the entry node;
  • Step 13 After receiving the working path establishment success message, the network management system obtains the routing information of the recovery path. If the connection establishment request message sent by the network management system to the ingress node carries the routing information of the recovery path of the strict explicit route, the network management system uses the routing information of the recovery path carried in the request message as the routing information of the restoration path;
  • connection establishment request message sent by the network management system to the ingress node does not carry the routing information of the recovery path, or the carried routing information is loose explicit routing information, the network management system needs to query the ingress node and obtain the routing information of the recovery path. .
  • Step 14 The network management system controls the resource reservation processing of the recovery path.
  • the network management system determines the link through which the recovery path passes according to the obtained routing information of the restoration path, determines whether the reserved resource needs to be allocated to the corresponding link, and controls the resource reservation processing according to the judgment result.
  • the network management system determines that a reserved resource needs to be allocated to the link.
  • the network management system determines that there is no need to allocate reserved resources on the link for establishing the recovery path; when one link of the recovery path already has one or more reserved resources, and the recovery The path cannot share any one of the reserved resources, that is, when the other working path of the reserved resource protection is related to the working path of the connection request, the network management system determines that the recovery path needs to be allocated on the link. Reserve resources.
  • FIG. 2 is a schematic structural diagram of a shared trellis network according to an embodiment of the present invention; in the network shown in FIG. 2, there are six nodes of A-F and seven links connecting A-B, A-C, CD, and DB. , EC, DF and EF, there are two working paths AB and EF.
  • the working path AB passes through link A-B, its recovery path passes through links A-C, C-D and D-B; the working path EF passes through link E-F, and its recovery path passes through links E-C, C-D and D-F.
  • the network management system In the process of the network management system reserving resources for the recovery path of the working path AB, if the link CD already has the reserved resources allocated for the recovery path of the working path EF, the network management system does not need to allocate the recovery path of the working path AB. Reserve resources. After determining that a resource needs to be allocated for establishing a link of the recovery path, the network management system sends a resource reservation command to the two nodes of the corresponding link, and the corresponding link node reserves the corresponding resource after receiving the resource reservation command. These resources can only be used for recovery paths for related connections and cannot be used for working paths for new connections.
  • the specific process of resource reservation can be implemented according to the RSVP-TE protocol extension supporting the end-to-end recovery draft ( draft-ietf-ccamp-gmpls-recoveiy-e2e-signaling).
  • Step 15 After the ingress node determines that the working path has failed, the establishment process of the recovery path is initiated by signaling. After the network fault causes the working path to be interrupted, the ingress node of the working path can determine the working path fault through the alarm detection or the fault notification of the control plane, and then initiate the recovery path establishment process according to the saved routing information of the recovery path.
  • the signaling process for establishing a recovery path is similar to the signaling process for establishing a working path, and the recovery path is established using pre-reserved link resources.
  • the recovery path can be established in the following ways:
  • the ingress node sends a connection establishment request of the restoration path to each node in turn according to the routing information of the GMPLS extended signaling protocol (such as the RSVP-TE protocol), until the egress node of the recovery path is in the process.
  • Each node confirms the reserved resources;
  • each section of the recovery path from the egress node sequentially establishes a corresponding cross-connection in the opposite direction of the connection establishment request of the restoration path and returns a connection establishment response to the upper node after the cross-connection is established, until the entry node;
  • the ingress node After the recovery path is successfully established, the ingress node returns a connection establishment success message to the recovery path to the network management system.
  • the user signal After the recovery path is successfully established, the user signal needs to be transferred to the recovery path for transmission, and the service is restored.
  • the advantage of this method is that the status of the working path can be monitored at any time, and the business can be switched to the working path in time when the working path is restored.
  • Another way is to remove the cross-connection of the user signal to the working path and switch the user signal to the recovery path for transmission.
  • Step 16 When the working path is restored, remove the recovery path and release the resources.
  • the user signal needs to be returned to the working path for transmission, and then the recovery path is removed, and the resources occupied by the recovery path are released. These resources can be used to establish other working paths or Restore the path.
  • the connection setup request received by the ingress node comes from the user equipment (such as a router or switch, etc.) or its agent.
  • the network management system may not only send a resource reservation command to the two nodes of the corresponding link, but also perform resources by the corresponding node. For reservation, the network management system may also perform resource reservation processing and save the resource reservation information in a centralized manner.
  • Occupied state that is, used by an already established path
  • Idle state resources of this state can be used to establish various paths, no restrictions.
  • the nodes in the network should be timed or The resource reservation is queried to the network management system as needed.
  • the node in the network can query the network management system for resource reservation after receiving the new connection establishment request, and can only use the idle state resource to establish a new working path. .
  • the node can query the network management system for the resource reservation.
  • the network management system can be used as the directory server.
  • the resource reservation of each node is saved in the directory.
  • the node can check the network management system through the directory service protocol. Ask for the corresponding resource reservation.
  • the resources used to establish the recovery path may be reserved resources or resources in an idle state.
  • the network management system generally represents a system composed of one or more mutually communicating software supporting a network operator to perform optical transport network management operations, and the system supports various nodes by using a management interface provided by a network node.
  • network management functions (such as initiating soft permanent connections), including network resource management functions, which are responsible for tracking the use of network link resources, including the use of link resources by the working path, and the resources of the recovery path. Reservations.
  • the resource management function can be embedded in the network management software or as a separate software that communicates with the network management software, thus forming part of the network management system.
  • the automatic switched optical network includes: SDH, SONET, OTN or OXC (Optical) Cross-connect, light cross) and so on. '
  • An embodiment of the present invention provides a device for implementing a shared mesh network recovery.
  • a schematic diagram of an embodiment of the device is shown in FIG. 3, including: a routing information saving module 1 configured to determine and save routing information of a recovery path;
  • a resource reservation control module 2 configured to control, according to the recovery path routing information saved by the routing information saving module 1, a resource reserved for the recovery path;
  • the path establishing module 3 is configured to: according to the routing information, save the routing information of the recovery path saved by the module 1 and the resource reservation control module 2 to establish a recovery path for the resources reserved for the recovery path;
  • the path switching module 4 is configured to switch the service on the working path of the fault to the recovery path corresponding to the working path that has been established by the path establishing module 3;
  • the path removal module 5 is configured to remove the recovery path and release the path resource occupied by the recovery path.
  • the technical solution described in the embodiment of the present invention can use the existing RSVP-TE protocol to implement the shared lattice network recovery without extending the protocol, so the technical solution is simple and easy, and can be well implemented.
  • the signaling process does not need to be started during the resource reservation process of the recovery path, but the signaling process is started as needed after the network failure occurs, causing the control plane to maintain the connection state. The burden is reduced, and the communication traffic of the data communication network is reduced, which saves network resources.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Input Circuits Of Receivers And Coupling Of Receivers And Audio Equipment (AREA)

Description

共享格状网恢复的实现方法及装置
技术领域
本发明涉及网络通信技术领域， 尤其涉及一种共享格状网恢复的实现方法及装置。 发明背景
光传送网络， 包括 SDH (Synchronous Digital Hierarchy, 同步数字体系）、 SONET (Synchronous Optical Network, 同步光网络）和 OT ( Optical Transport Network, 光传 送网）， 传统上是被设计用于传送话音业务的， 数据业务的快速发展使得其占现有光网 络传送流量的比例不断提高， 对传送网络的带宽需求不断提髙， 服务提供时间的要求越 来越短。 这使得现有的网络架构和组网形式受到冲击， 为应对数据业务传送的需求， 网 络拓扑需要从传统的以环网为主演进到以格状网为主， 网络连接服务的提供方式要从以 静态供给的永久连接过渡到以基于信令的软永久连接和交换连接为主。这种新型的光传 送网络被 ITU-T (国际电联 -标准化部） 称为 ASON ( Automatically Switched Optical Network, 自动交换光网络）。 所述 ASON引入控制平面， 用于网络连接的建立、 修改和 维护， 并在网络故障情况下实现连接的恢复。 ASON的信令实现的方式之一是应用 IETF ( Internet Engineering Task Force , 互联网工程任务组） 开发的 GMPLS ( Generalized Multi-Protocol Label Switching,通用多协议标签交换）。
在格状网中， 为保证网络连接服务能在网络故障情况下得到恢复，需要为连接的工 作路径建立备用的恢复路径。 恢复路径的建立存在以下几种策略：
1、 恢复路径预建立： 就是在网络故障发生前预先为工作路径建立一条故障无关的 恢复路径 （两条路径故障无关是指这两条路径不会因为同一处网络故障而同时被中断， 路径故障无关要求这两条路径不经过相同的链路， 也不经过相同的 SRLG (Shared-Risk Link Group,共享风险链路组））。这种保护方式的优点是恢复时间短，通常在 50ms以下， 缺点是带宽占用多， 资源利用率低。
2、 恢复路径预计算， 并按共享方式预留网络资源， 网络故障发生后再动态建立恢 复路径， 这种保护方式通常称为 "共享格状网恢复"。 这种保护方式的优点是通过合理 规划各网络连接需求的工作和恢复路径进行资源预留，恢复路径通过资源共享可以提高 资源利用率， 但是恢复时间比恢复路径预建立方式长， 通常在 200 ms左右或更长。
3、保护路径按需建立， 即在网络故障发生后再计算一条恢复路径并试图恢复连接。 这种保护方式的优点是可以支持无法事先预测的网络故障情况， 如多重网络故障， 缺点 是由于没有预先进行资源预留无法确保恢复连接， 可靠性差， 而且恢复时间更长， 通常 需要数秒。
由于共享格状网恢复的保护方式同时具备连接恢复的可靠性和高资源利用率，因此 是一种业界认为很有效的业务保护和恢复方法。
目前， 业界提出了一种共享格状网恢复的技术方案， 该方案是： 工作和恢复路径都 使用 RPC3743 规范的 RSVP-TE协议来建立，扩展该协议增加" PROTECTION (保护）" 对象， 其中的一个比特位 （以下称 "S比特位"） 被用于指示共享格状网的恢复路径。 S 比特位如果被置 1， 控制平面只预留资源不建立交叉连接， 网络发生故障导致工作路径 中断后则将该比特位置 0， 控制平面则启动交叉连接， 利用预留的资源建立恢复路径， 而且资源预留和交叉连接的建立过程都需要信令交互来完成。 具体包括如下步骤：
1、 网络连接服务的网络入口节点 （简称入口节点） 首先确定工作路径的源路由信 息， 通过信令协议建立工作路径；
2、 入口节点确定恢复路径的源路由信息， 并通过信令 "建立"该恢复路径， 与建 立工作路径不同的是恢复路径的建立信令的 S比特位被置 1， 恢复路径上的各节点只预 留链路资源， 不建立交叉连接， 因此恢复路径在工作路径正常情况下并不连通。 在整个 网络连接服务的生命周期中恢复路径的信令会话和工作路径的信令会话一样需要被维 持着；
3、 入口节点发现工作路径因网络故障而中断后， 将恢复路径信令的 S比特位置 0， 该修改通过信令消息刷新沿恢复路径上的节点逐站传递，所经过的各节点利用预留的资 源建立恢复路径的交叉连接，入口节点和出口节点还将网络连接服务从工作路径切换到 恢复路径进行传送。
发明人在发明过程中发现- 上述的技术方案需要扩展现有的 RSVP-TE协议， 因此在实现上比较复杂； 该技术方案需要在对恢复路径进行资源预留时预先启动信令过程，而且该信令过程 自建立工作路径启动后一直持续到该工作路径上的业务结束。因此增加了控制平面信令 维护连接状态的负担， 加大了数据通信网的通信流量， 需要耗费大量网络资源。
发明内容
本发明实施例提供一种共享格状网恢复的实现方法及装置， 技术方案简单易行， 利 用现有协议即可实现， 能够很好地兼容现有设备。 .
本发明实施例是通过以下技术方案实现的：
本发明实施例提供一种共享格状网恢复的实现方法， 包括如下步骤： 网络连接服务器的网络入口节点确定恢复路径的路由信息并保存； 当工作路径建立成功后， 网管系统控制恢复路径的资源预留处理；
当工作路径中断后，所述网络连接服务器的网络入口节点根据保存的恢复路径的路 由信息， 利用预留的资源发起恢复路径的建立过程；
将工作路径的业务切换到恢复路径进行传送。、 本发明实施例提供一种共享格状网恢复的实现装置， 包括： 路由信息保存模块、 资 源预留控制模块、 路径建立模块及路径切换模块，
所述路由信息保存模块， 用于确定并保存恢复路径的路由信息；
所述资源预留控制模块，用于根据所述路由信息保存模块保存的恢复路径的路由信 息， 控制为所述恢复路径预留资源；
所述路径建立模块，用于根据所述路由信息保存模块保存的恢复路径的路由信息及 所述资源预留控制模块为恢复路径预留的资源建立恢复路径；
所述路径切换模块，用于将故障的工作路径上的业务切换到所述路径建立模块已经 建立的该工作路径对应的恢复路径上。
由上述本发明实施例提供的技术方案可以看出：本发明实施例所述的方法具有如下 优点：
可以利用现有协议， 如 RSVP-TE等协议来实现共享格状网恢复， 而无需扩展协议， 因此技术方案简单易行， 能够很好地兼容现有设备；
在恢复路径的资源预留过程中无需启动信令流程，而是当网络发生故障导致工作路 径中断后按需启动信令流程， 因此降低了控制平面信令维护连接状态的负担， 减少了数 据通信网的通信流量， 节约了网络资源；
另外， 在本发明技术方案中， 网管系统集中维护恢复路径资源与恢复路径和网络连 接服务的关系， 控制平面只需要维护 "预留给恢复路径使用"的资源数目， 因此简化了 控制平面的实现。
附图简要说明
图 1为本发明实施例所述方法的工作流程图；
图 2为本发明实施例所述的共享格状网结构示意图；
图 3为本发明实施例所述装置模块示意图。
实施本发明的方式 本发明实施例在自动交换光网络中， 网络连接服务的网络入口节点确定恢复路径的 路由信息并保存； 当工作路径建立成功后网管系统控制恢复路径的资源预留处理； 当工 作路径中断后， 所述网络连接服务器的网络入口节点根据保存的恢复路径的路由信息、 利用预留的资源发起恢复路径的建立过程，并将工作路径的业务切换到恢复路径进行传 送。 .
为了对本发明实施例有进一步的了解，下面将结合附图对本发明实施例进行详细的 说明， 但并不作为对本发明的限定。
本发明实施例的具体实施方式如图 1所示， 图 1为本发明实施例所述方法的工作流 程图； 包括如下步骤：
步骤 11： 确定工作路径和恢复路径的路由。
自动交换光网络中， 网管系 向网络连接服务器的网络入口节点（以下简称入口节 点） 发送连接建立请求；
入口节点收到连接建立请求消息后解析该请求，如果请求消息中携带有严格显式路 由的工作路径和恢复路径的路由信息，则将该路由信息作为工作路径和恢复路径的路由 信息并将恢复路径的路由信息进行保存；
如果连接建立请求消息中没有携带工作路径和 /或恢复路径的路由信息，或者携带的 路由信息为松散显式路由信息，则入口节点计算工作路径和 /或恢复路径的路由，并保存 恢复路径的路由信息。
所述严格显式路由信息， 包括： 路径依次经过的链路的序列， 链路通常由节点标识 和端口标识组成， 称链路标识。
所述松散显式路由信息， 指缺少部分或者所有的经过链路的路由信息。
步骤 12: 建立工作路径。
入口节点确定工作路径和恢复路径的路由后， 发起工作路径的建立过程。
工作路径的建立可以采用如下的工作方式：
入口节点根据工作路径的路由信息通过 GMPLS 扩展的信令协议 （如 RSVP-TE 协议等）的数据报文依次向各个节点发送工作路径的连接建立请求， 直到该工作路径所 在的最后一个节点 〔以下简称出口节点）， 在这个过程中每个节点接到连接建立请求后 进行资源预留； '
工作路径的资源预留后，从出口节点起工作路径的各个节点沿工作路径的连接建立 请求的反方向依次建立相应的交叉连接并且在交叉连接建立后向上一个节点返回连接 建立响应， 直到入口节点；
工作路径建立成功后， 入口节点向网管系统返回工作路径的连接建立成功消息。 步骤 13 : 网管系统收到工作路径建立成功消息后， 获取恢复路径的路由信息。 如果网管系统向入口节点下发的连接建立请求消息中携带有严格显式路由的恢复 路径的路由信息， 网管系统将该请求消息中携带的恢复路径的路由信息作为恢复路径的 路由信息；
如果网管系统向入口节点下发的连接建立请求消息中没有携带恢复路径的路由信 息， 或者携带的路由信息为松散显式路由信息， 那么网管系统需要向入口节点査询并获 取恢复路径的路由信息。
步骤 14: 网管系统控制恢复路径的资源预留处理。
网管系统根据获取的恢复路径的路由信息确定恢复路径所经过的链路并判断是否 需要向相应链路分配预留资源， 并根据判断结果控制资源预留处理。
当恢复路径的某条链路不存在预留资源时， 网管系统确定需要向该链路分配预留资 源。
当恢复路径的某条链路已经存在一份或多份预留资源，并且该恢复路径可以共享其 中的一份或几份预留资源， 即该预留资源保护的其他工作路径与本连接请求的工作路径 故障无关时， 则网管系统确定不需要为建立恢复路径而在该链路上分配预留资源； 当恢复路径的某条链路已经存在一份或多份预留资源，并且该恢复路径不可以共享 其中任何一份预留资源， 即该预留资源保护的其他工作路径与本连接请求的工作路径敌 障相关时， 则网管系统确定需要为建立恢复路径而在该链路上分配预留资源。
图 2为本发明实施例所述的共享格状网结构示意图；如图 2所示的网络中，共有 A - F六个节点以及七个链路连接 A- B、 A- C、 C-D、 D-B、 E-C、 D-F和 E-F， 有两条工 作路径 AB和 EF。
工作路径 AB经过链路 A-B， 它的恢复路径经过连路 A-C、 C-D和 D-B; 工作路径 EF经过链路 E-F, 它的恢复路径经过连路 E-C、 C-D和 D-F。
因为工作路径 AB和工作路径 EF没有经过相同的链路或者 SRLG, 所以这两条工 作路径故障无关， 因此它们的恢复路径在 路 C-D上可以共享恢复资源。
在网管系统为工作路径 AB的恢复路径预留资源过程中，如果链路 C-D已经存在了 为工作路径 EF的恢复路径而分配的预留资源， 则网管系统无需再为工作路径 AB的恢 复路径分配预留资源。 当确定需要为建立恢复路径的某条链路分配预留资源后， 网管系统向相应链路的两 端节点发送资源预留命令， 相应链路节点收到资源预留命令后预留相应资源。这些资源 仅能用于相关连接的恢复路径， 不能被用于新建连接的工作路径。
资源预留的具体过程可以按照 RSVP- TE 协议扩展支持端到端的恢复的草案 ( draft-ietf-ccamp-gmpls-recoveiy-e2e-signaling ) 中关于资源预留的技术方案执行。
步骤 15 :当入口节点确定工作路径发生故障后，通过信令发起恢复路径的建立过程。 当网络故障引起工作路径中断后，工作路径的入口节点可以通过告警检测或者控制 平面的故障通知确定工作路径故障，进而根据保存的恢复路径的路由信息发起恢复路径 的建立过程。
建立恢复路径的信令过程与建立工作路径的信令过程类似，并且使用预先预留的链 路资源进行恢复路径的建立。 恢复路径的建立可以采用如下的方式：
入口节点根据恢复路径的路由信息通过 GMPLS 扩展的信令协议 （如 RSVP-TE 协议等）的数据报文依次向各个节点发送恢复路径的连接建立请求， 直到恢复路径的出 口节点， 在这个过程中每个节点确认预留的资源；
然后，从出口节点起恢复路径的各个节'点沿恢复路径的连接建立请求的反方向依次 建立相应的交叉连接并且在交叉连接建立后向上一个节点返回连接建立响应，直到入口 节点；
最后， 恢复路径建立成功后， 入口节点向网管系统返回恢复路径的连接建立成功消 息。
恢复路径成功建立后， 需要将用户信号转移到恢复路径传送， 业务得到恢复。 将用户信号转移到恢复路径的具体方式有多种- 一种方式是： 可以在源端将用户信号桥接到工作路径和恢复路径， 宿端则从恢复路 径接收信号。
这种方式的优点在于可以随时监测工作路径的状态， 当工作路径恢复后可以及时将 业务切换到工作路径上。
另外一种方式是：拆除用户信号与工作路径的交叉连接并将用户信号切换到恢复路 径上传送。
步骤 16: 当工作路径恢复后， 拆除恢复路径， 释放资源。
如果网络故障被修复， 工作路径恢复后， 则需要将用户信号返回到工作路径传送， 然后拆除恢复路径， 释放恢复路径占用的资源， 这些资源可以用于建立其他工作路径或 者恢复路径。
上述技术方案是针对 SPC ( Soft Permanent Connection, 软永久连接）的， 也适用于 SC (Switched Connection, 交换连接）。
对于交换连接， 入口节点收到的连接建立请求则来自用户设备（比如路由器或者交 换机等）或其代理。
在上述网管系统进行恢复路径的资源预留处理过程中，如果需要为建立恢复路径而 分配预留资源， 网管系统不但可以向相应链路的两端节点发送资源预留命令， 由相应节 点进行资源预留， 也可以由网管系统自行进行资源预留处理并集中保存资源预留信息。
网络中建立链路所需资源的状态通常有三种， 分别是：
占用状态， 即被已经建立的路径所使用；
预留状态， 这种状态的资源仅能用于建立共享格状网恢复情况下的恢复路径使用， 不能用于建立其他路径， 如工作路径；
空闲状态， 这种状态的资源可以用于建立各种路径， 没有限制。
因此，如果采用网管系统集中进行资源预留处理并保存恢复路径的资源预留信息的 资源预留方式， 为了确保为恢复路径预留的资源不被其他连接占用， 网络中的节点应该 定时的或者按需向网管系统査询资源预留情况， 比如网络中的节点可以在收到新的连接 建立请求后向网管系统査询资源预留情况，并只能利用空闲状态的资源建立新的工作路 径。
节点向网管系统查询资源预留情况可以通过目录服务来实现，这时网管系统可以作 为目录服务器， 在其中的目录下保存有各节点的资源预留情况， 节点可以通过目录服务 协议向网管系统査询相应的资源预留情况。
另外，不论采用何种资源预留方式，建立恢复路径所使用的资源既可以是预留资源， 也可以是处于空闲状态的资源。
本发明实施例所述的网管系统通常表现为支持网络操作者进行光传送网络管理操 作的一个或多个相互通信的软件组成的系统，该系统支持通过网络节点提供的管理接口 来实现各种节点和网络的管理功能（如发起软永久连接）， 其中包括网络资源管理功能， 该功能负责跟踪网络链路资源的使用情况， 既包括链路资源被工作路径的使用情况， 也 包括恢复路径的资源预留情况。具体实现上，资源管理功能既可以内嵌在网管软件内部， 也可以作为一个与网管软件有通讯关系的独立的软件， 从而构成网管系统的一部分。
本发明实施例所述的自动交换光网络包括： SDH、 SONET, OTN或 OXC (Optical Cross-connect, 光交叉)等。 '
本发明实施例提供一种共享格状网恢复的实现装置，所述装置一种实施例模块示意 图如图 3所示， 包括- 路由信息保存模块 1， 用于确定并保存恢复路径的路由信息；
资源预留控制模块 2, 用于根据所述路由信息保存模块 1保存的恢复路径路由信息 控制为恢复路径预留的资源；
路径建立模块 3， 用于根据路由信息保存模块 1保存的恢复路径的路由信息及资源 预留控制模块 2为恢复路径预留的资源建立恢复路径；
路径切换模块 4， 用于将故障的工作路径上的业务切换到所述路径建立模块 3已经 建立的该工作路径对应的恢复路径上；
路径拆除模块 5， 用于拆除恢复路径， 释放恢复路径占用的路径资源。
综上所述， 本发明实施例所述的技术方案， 可以利用现有的 RSVP-TE等协议来实 现共享格状网恢复， 而无需扩展该协议， 因此技术方案简单易行， 能够很好地兼容现有 设备； 另外在恢复路径的资源预留过程中无需启动信令流程， 而是当网络发生故障导致 工作路径中断后按需启动信令流程， 因此降低了控制平面信令维护连接状态的负担， 减 少了数据通信网的通信流量， 节约了网络资源。
以上所述，仅为本发明实施例的具体实施方式，但本发明的保护范围并不局限于此， 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可轻易想到的变化或替 换， 都应涵盖在本发明的保护范围之内。 因此， 本发明的保护范围应该以权利要求的保 护范围为准。

Claims

权利要求
1、 一种共享格状网恢复的实现方法， 其特征在于， 包括如下步骤：
网络连接服务器的网络入口节点确定恢复路径的路由信息并保存；
当工作路径建立成功后， 网管系统控制恢复路径的资源预留处理；
当工作路径中断后，所述网络连接服务器的网络入口节点根据保存的恢复路径的路 由信息， 利用预留的资源发起恢复路径的建立过程；
将工作路径的业务切换到恢复路径进行传送。
2、 根据权利要求 1所述的方法， 其特征在于， 所述确定并保存恢复路径的路由信 息的方法步骤具体包括：
所述网络连接服务器的网络入口节点收到连接建立请求后解析该请求消息； 若所述请求消息中承载有严格显式路由的工作路径和恢复路径的路由信息，则所述 网络连接服务器的网络入口节点将所述请求消息中承载的路由信息作为工作路径和恢 复路径的路由信息， 并将所述请求消息中承载的恢复路径的路由信息进行保存；
若所述请求消息中没有承载工作路径和 /或恢复路径的路由信息，或者承载的路由信 息为松散显式路由信息，则所述网络连接服务器的网络入口节点计算工作路径和 /或恢复 路径的路由，并保存所述请求消息承载的或者所述网络入口节点计算出的恢复路径的路 由信息；
所述网络连接服务器的网络入口节点根据确定的工作路径的路由信息发起所述工 作路径的建立过程。
3、 根据权利要求 2所述的方法， 其特征在于： 当所述连接为软永久连接时， 所述 连接建立请求来自于网管系统；
当所述连接为交换连接时， 所述连接建立请求来自于用户设备或其代理。
4、 根据权利要求 1所述的方法， 其特征在于， 所述网管系统控制恢复路径的资源 预留处理的方法步骤具体包括- 当网管系统收到所述网络连接服务器的网络入口节点发送的所述工作路径建立成 功的消息后， 获取所述恢复路径的路由信息；
网管系统根据获取的所述恢复路径的路由信息确定该恢复路径所经过的链路，并判 断是否需要为该链路预留资源；
网管系统根据判断结果控制资源预留处理。
5、 根据权利要求 4所述的方法， 其特征在于， 所述网管系统获取所述恢复路径的 路由信息的方式包括：
当所述连接建立请求来自于网管系统且 ά请求消息中承载有严格显式路由的恢复 路径的路由信息时， 网管系统将所述请求消息中承载的路由信息作为恢复路径的路由信 息； 或者，
当所述连接建立请求来自于网管系统且该请求消息中没有承载恢复路径的路由信 息， 或者承载的恢复路径的路由信息为松散显式路由信息， 或者所述连接建立请求来自 于用户设备或其代理时， 网管系统向所述网络连接服务器的网络入口节点査询并获取恢 复路径的路由信息。
6、 根据权利要求 4所述的方法， 其特征在于， 所述网管系统确定恢复路径所经过 的链路并判断是否需要为该链路预留资源的方法步骤包括：
当所述恢复路径经过的链路存在可用的共享预留资源时， 网管系统确定无需向该链 路分配预留资源；
当所述恢复路径经过的链路不存在预留资源， 或者不存在可用的共享预留资源时， 网管系统确定向该链路分配预留资源。
7、 根据权利要求 4、 5或 6所述的方法， 其特征在于， 所述网管系统根据判断结果 控制资源预留处理的方法步骤进一步包括- 当网管系统确定需要向所述恢复路径经过的链路分配预留资源后， 向该链路的两端 节点发送资源预留命令；
所述两端节点收到资源预留命令后进行资源预留处理。
8、 根据权利要求 4、 5或 6所述的方法， 其特征在于， 所述网管系统根据判断结果 控制资源预留处理的方法步骤进一步包括- ,
当网管系统确定需要向所述恢复路径经过的链路分配预留资源时， 网管系统自行进 行资源预留处理并保存相应的资源预留信息。
9、 根据权利要求 8所述的方法， 其特征在于， 该方法还包括- 当网络中的节点收到新的连接建立请求后向网管系统查询所述资源预留信息，利用 空闲状态的资源建立新的工作路径。
10、 根据权利要求 1至 6任一项所述的方法， 其特征在于， 该方法还包括 - 当工作路径中断后，所述网络连接服务器的网络入口节点根据保存的恢复路径的路 由信息， 利用空闲状态的资源发起恢复路径的建立过程， 并将工作路径的业务切换到恢 复路径进行传送。
11、根据权利要求 1所述的方法， 其特征在于， 所述将工作路径的业务切换到恢复 路径的方法包括步骤：
将用户信号桥接到工作路径和恢复路径， 从所述恢复路径接收信号； 或
拆除用户信号与所述工作路径的交叉连接，并将所述用户信号切换到所述恢复路径 上进行传送。
12、根据权利要求 1所述的方法，其特征在于，该方法还包括： 当工作路径恢复后， 拆除恢复路径， 释放恢复路径占用的资源。
13、 一种共享格状网恢复的实现装置， 其特征在于， 包括： 路由信息保存模块、 资 源预留控制模块、 路径建立模块及路径切^模块，
所述路由信息保存模块， 用于确定并保存恢复路径的路由信息；
所述资源预留控制模块，用于根据所述路由信息保存模块保存的恢复路径的路由信 息， 控制为所述恢复路径预留资源；
所述路径建立模块，用于根据所述路由信息保存模块保存的恢复路径的路由信息及 所述资源预留控制模块为恢复路径预留的资源建立恢复路径；
所述路径切换模块，用于将故障的工作路径上的业务切换到所述路径建立模块已经 建立的该工作路径对应的恢复路径上。
14、 根据权利要求 13所述的装置， 其特征在于， 所述装置进一步包括： 路径拆除模块， 用于拆除恢复路径， 释放该恢复路径占用的路径资源。
PCT/CN2006/003503 2005-12-22 2006-12-20 Procede et dispositif de restauration d'un reseau maille partage WO2007071189A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
AT06828409T ATE458320T1 (de) 2005-12-22 2006-12-20 Verfahren und vorrichtung zur wiederherstellung eines gemeinsam genutzten vermaschten netzes
DE602006012318T DE602006012318D1 (de) 2005-12-22 2006-12-20 Verfahren und vorrichtung zur wiederherstellung eines gemeinsam genutzten vermaschten netzes
CNA2006800122036A CN101160901A (zh) 2005-12-22 2006-12-20 共享格状网恢复的实现方法及装置
EP06828409A EP1898584B1 (en) 2005-12-22 2006-12-20 A method and device for recovering the share mesh network
US12/019,025 US7787362B2 (en) 2005-12-22 2008-01-24 Method and device for recovering a shared mesh network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2005101322018A CN1866806B (zh) 2005-12-22 2005-12-22 共享格状网恢复的实现方法
CN200510132201.8 2005-12-22

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/019,025 Continuation US7787362B2 (en) 2005-12-22 2008-01-24 Method and device for recovering a shared mesh network

Publications (1)

Publication Number Publication Date
WO2007071189A1 true WO2007071189A1 (fr) 2007-06-28

Family

ID=37425699

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003503 WO2007071189A1 (fr) 2005-12-22 2006-12-20 Procede et dispositif de restauration d'un reseau maille partage

Country Status (7)

Country Link
US (1) US7787362B2 (zh)
EP (1) EP1898584B1 (zh)
CN (2) CN1866806B (zh)
AT (1) ATE458320T1 (zh)
DE (1) DE602006012318D1 (zh)
ES (1) ES2340719T3 (zh)
WO (1) WO2007071189A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103595626A (zh) * 2013-10-15 2014-02-19 苏州拓康自动化技术有限公司 一种环形网络中实现动态路径规划的方法
CN113727220A (zh) * 2020-05-26 2021-11-30 华为技术有限公司 业务资源预配置方法、设备和系统

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080008102A1 (en) * 2006-07-07 2008-01-10 Fujitsu Limited Tracing an optical path of a communication network
CN101163030A (zh) * 2006-10-09 2008-04-16 华为技术有限公司 一种建立区分器映射表的方法
CN101170494B (zh) * 2007-11-21 2010-06-02 中兴通讯股份有限公司 自动交换光网络中的软重路由方法
JP5062845B2 (ja) * 2008-06-30 2012-10-31 日本電信電話株式会社 経路切替方法、サーバ装置、境界ノード装置、経路切替システム及び経路切替プログラム
CN101646105B (zh) * 2008-08-07 2013-08-07 华为技术有限公司 业务恢复的方法、系统和设备
US8848538B2 (en) * 2009-06-09 2014-09-30 Telefonaktiebolaget Lm Ericsson (Publ) Power-saving functions in communications networks
EP2441218B1 (en) * 2009-06-09 2013-03-27 Telefonaktiebolaget LM Ericsson (publ) A communications network and a method in a communications network
WO2011006541A1 (en) * 2009-07-16 2011-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Recovery mechanism for point-to-multipoint traffic
CN101998181B (zh) * 2009-08-10 2013-09-11 中兴通讯股份有限公司 Sncp业务迁移方法及装置
CN101998186A (zh) * 2009-08-13 2011-03-30 中兴通讯股份有限公司 网络保护方法及装置
US9800495B2 (en) * 2009-09-30 2017-10-24 Infinera Corporation Fast protection path activation using control plane messages
CN102104495B (zh) 2009-12-18 2014-07-09 华为技术有限公司 共享Mesh保护的实现方法和设备及光网络系统
MY165724A (en) 2010-01-04 2018-04-20 Ericsson Telefon Ab L M Shared path recovery scheme
US8670302B2 (en) * 2010-06-10 2014-03-11 Infinera Corporation Activation signaling in transport networks
US8908533B2 (en) 2010-06-10 2014-12-09 Infinera Corporation Supporting OAM on protecting connections in shared mesh protection environment
EP3223158B1 (en) * 2016-02-01 2020-04-22 Huawei Technologies Co., Ltd. Data recovery method and storage system
US10362631B2 (en) * 2017-04-03 2019-07-23 Level 3 Communications, Llc Last resource disaster routing in a telecommunications network
US10970152B2 (en) * 2017-11-21 2021-04-06 International Business Machines Corporation Notification of network connection errors between connected software systems
CN110858820A (zh) 2018-08-22 2020-03-03 中兴通讯股份有限公司 业务运行方法、装置、存储介质及电子装置
US11076348B2 (en) 2019-01-03 2021-07-27 Samsung Electronics Co., Ltd. Method of neighbor discovery and wireless inter-connection for cellular mesh network
US10849179B1 (en) 2019-05-29 2020-11-24 Bank Of America Corporation Mobile network tool

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020114031A1 (en) * 2001-02-21 2002-08-22 Ryo Yamada Ring configuration method, failure recovery method, and node address assignment method when configuring ring in network
CN1392686A (zh) * 2002-07-11 2003-01-22 北京邮电大学 一种自动交换光网络可恢复路径选择建立方法
CN1556637A (zh) * 2003-12-30 2004-12-22 ���ͨ�ſƼ��ɷ����޹�˾ 一种在格状网中利用共享备用通道进行故障恢复的方法
EP1737145A1 (en) 2004-09-10 2006-12-27 Huawei Technologies Co., Ltd. A method for optical meshwork service restoration

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6882765B1 (en) * 1999-11-02 2005-04-19 Xros, Inc. Connection protection between clients and optical cross-connect switches
US6934248B1 (en) * 2000-07-20 2005-08-23 Nortel Networks Limited Apparatus and method for optical communication protection
JP4145025B2 (ja) * 2001-05-17 2008-09-03 富士通株式会社 予備パスの設定方法および装置
KR100420956B1 (ko) * 2002-02-09 2004-03-02 주식회사 케이티 Ｍｐｌｓ 망에서 대체 경로를 공유하는 방법, 대체 경로를설정하는 레이블 스위칭 라우터 및 그 시스템
TWI323101B (en) * 2003-01-21 2010-04-01 Panasonic Corp Communication system and its terminal
JP4691372B2 (ja) * 2005-03-09 2011-06-01 富士通株式会社 データ中継装置およびデータ中継方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020114031A1 (en) * 2001-02-21 2002-08-22 Ryo Yamada Ring configuration method, failure recovery method, and node address assignment method when configuring ring in network
CN1392686A (zh) * 2002-07-11 2003-01-22 北京邮电大学 一种自动交换光网络可恢复路径选择建立方法
CN1556637A (zh) * 2003-12-30 2004-12-22 ���ͨ�ſƼ��ɷ����޹�˾ 一种在格状网中利用共享备用通道进行故障恢复的方法
EP1737145A1 (en) 2004-09-10 2006-12-27 Huawei Technologies Co., Ltd. A method for optical meshwork service restoration

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Fast Recovery Mechanism in Optical Networks", 2005 PROCEEDINGS, 6TH ASIA-PACIFIC SYMPOSIUM ON YANGON, MYANMAR 09-10 NOV. 2005, PISCATAWAY, NJ, USA, IEEE, 25 November 2003 (2003-11-25), pages 435 - 440
"Shared segment recovery mechanism in optical networks", INFORMATION AND TELECOMMUNICATION TECHNOLOGIES, 2005, APSITT 2005 PROCEEDINGS, 6TH ASIA-PACIFIC SYMPOSIUM ON YANGON, MYANMAR 09-10 NOV. 2005, PISCATAWAY, NJ, USA, IEEE, 9 November 2005 (2005-11-09), pages 415 - 420

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103595626A (zh) * 2013-10-15 2014-02-19 苏州拓康自动化技术有限公司 一种环形网络中实现动态路径规划的方法
CN113727220A (zh) * 2020-05-26 2021-11-30 华为技术有限公司 业务资源预配置方法、设备和系统

Also Published As

Publication number Publication date
CN101160901A (zh) 2008-04-09
ES2340719T3 (es) 2010-06-08
EP1898584B1 (en) 2010-02-17
EP1898584A1 (en) 2008-03-12
US7787362B2 (en) 2010-08-31
DE602006012318D1 (de) 2010-04-01
CN1866806A (zh) 2006-11-22
EP1898584A4 (en) 2008-11-26
US20080117806A1 (en) 2008-05-22
CN1866806B (zh) 2011-11-02
ATE458320T1 (de) 2010-03-15

Similar Documents

Publication Publication Date Title
WO2007071189A1 (fr) Procede et dispositif de restauration d'un reseau maille partage
EP1942604B1 (en) A service switching method and the network node thereof
JP3972664B2 (ja) パス障害回復方式及び障害復旧後の切戻方式並びにそれらを用いるノード
JP3900194B2 (ja) 通信ネットワークにおけるパスの故障救済を行うための装置及び方法
US7974183B2 (en) Method for restoration and normalization in a mesh network
WO2006026930A1 (fr) Procede de restauration d'un service de maillage optique
JP5163479B2 (ja) パス切替え方法
US20080056159A1 (en) Method for setting path and node apparatus
US20070274224A1 (en) Path setting method, node device, and monitoring/control device
WO2008006268A1 (en) Method system and node device for realizing service protection in the automatically switched optical network
WO2010109802A1 (ja) 自律分散制御によるパス設定方法およびシステム並びに通信装置
WO2005022782A1 (fr) Structure d'echange et procede de configuration de connexion entre reseaux optiques
JP2007500955A (ja) 伝送ネットワークにおける固定接続及び相手先選択接続間の移行のための方法
US8165016B2 (en) Method and apparatus for setting communication paths in a network
WO2008119294A1 (fr) Procédé et matériel de restauration du commerce en réseau
JP2007053793A (ja) 通信ネットワークにおけるパスの故障救済を行うための装置及び方法
US20080205262A1 (en) Node controller and node system
WO2008037162A1 (fr) Procédé de gestion de services dans un réseau optique intelligent
US20110173336A1 (en) Barrier boundary node and method for establishing connection between barrier boundary nodes
JP2003143183A (ja) ネットワークのソースノードと宛先ノードとの間の接続設定の際にノードで用いられる方法。
JP4704311B2 (ja) 通信システムおよび故障復旧方法
JP2007129782A (ja) 通信ネットワークにおけるパスの故障救済を行うための装置及び方法
EP2395773B1 (en) Method and apparatus of sub-network connection protection (sncp) service migration
WO2013033997A1 (zh) 一种实现控制平面交叉倒换的方法及系统
JP2007014031A (ja) 通信ネットワークにおけるパスの故障救済を行うための装置及び方法

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

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2006828409

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 12019025

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 2006828409

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 12019025

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE