WO2011017861A1 - Sncp业务迁移方法及装置 - Google Patents

Sncp业务迁移方法及装置 Download PDF

Info

Publication number
WO2011017861A1
WO2011017861A1 PCT/CN2009/075010 CN2009075010W WO2011017861A1 WO 2011017861 A1 WO2011017861 A1 WO 2011017861A1 CN 2009075010 W CN2009075010 W CN 2009075010W WO 2011017861 A1 WO2011017861 A1 WO 2011017861A1
Authority
WO
WIPO (PCT)
Prior art keywords
connection
migration
cross
spc
current
Prior art date
Application number
PCT/CN2009/075010
Other languages
English (en)
French (fr)
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 中兴通讯股份有限公司
Priority to BRPI0924924-9A priority Critical patent/BRPI0924924A2/pt
Priority to RU2011137322/07A priority patent/RU2479943C1/ru
Priority to EP09848191.4A priority patent/EP2395773B1/en
Priority to US13/258,886 priority patent/US8554073B2/en
Publication of WO2011017861A1 publication Critical patent/WO2011017861A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0029—Provisions for intelligent networking
    • H04Q3/0054—Service creation techniques
    • 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
    • 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

Definitions

  • the present invention relates to an automatic switched optical network technology, and in particular, to a SNCP (Sub-network Connection Protection) service migration method and apparatus.
  • SNCP Sub-network Connection Protection
  • ASON Automatically Switched Optical Network
  • PC In ASON, three types of connections are provided depending on different connection needs and service request objects: PC, Permanent Connection, Soft Permanent Connection (SPC), and Switched Connection (SC). .
  • PC In actual network operation and maintenance, operators need to migrate between SPC and PC services as needed within the network.
  • the label the label here refers to the SDH universal label described in RFC3946
  • the cross management authority are migrated to the control plane.
  • the SPC When the SPC is migrated to the PC, the SPC resource reservation protocol (RSVP) signaling status needs to be deleted, and the label and cross management rights are migrated to the control plane.
  • RSVP SPC resource reservation protocol
  • the 1+1 Sub-network Connection Protection (SNCP) service is a common type of service in the transport network. It is characterized in that it provides 1+1 backup for the bearer connection of the service, that is, there is a working connection and Protect the connection. For the first and last nodes, the cross-connection is concurrent and acceptable. Therefore, for the SNCP service, whether it is implementing SPC migration to PC or PC migration to SPC, it is necessary to ensure the consistency of the working connection label and the protection connection label and the cross management authority under normal processes and abnormal processes. In addition, for the migration of SNCP services, The serial mode can be used, that is, the working connection is migrated first, and the migration of the protection connection is implemented after the working connection is successfully migrated.
  • the parallel mode can also be used, that is, the migration of the working connection and the protection connection are simultaneously issued. Regardless of which method is used, in the normal or abnormal migration, the management rights of the two connections under the SNCP service are not allowed to be the management plane and the control plane. If the cross-administration rights of the working connection and the protection connection are inconsistent, the management plane cannot operate at the intersection of the control plane, and the control plane cannot operate the intersection of the management plane. Therefore, the management plane cannot directly implement the management plane.
  • the deletion of services does not enable service recovery, optimization, deletion, and modification in the control plane.
  • the main purpose of the present invention is to provide an SNCP service migration method and apparatus, which can ensure the consistency of the working connection and the protection connection cross management authority when performing the cross-over migration of the protection relationship between the first and last nodes of the SNCP service.
  • Another object of the present invention is to provide an SNCP service migration apparatus, which can ensure the consistency of the working connection and the protection connection cross management authority when performing the cross-over migration of the protection relationship between the first and last nodes of the SNCP service.
  • an SNCP service migration method is provided.
  • a subnet connection protection SNCP service migration method is applied to an automatic switched optical network ASON, and the method includes:
  • Receiving a migration request of the SNCP service respectively, setting a cross-state control bit of the current operation connection and its associated connection according to the received migration request, and implementing the current operation connection and the association according to the set cross-state control bit Common migration of connections;
  • the migration request includes: migrating to a soft permanent link SPC with a persistent link PC, and migrating the SPC to one of the PCs.
  • the cross state control bits include: a cross setup status bit for timing the decision to cross connect migration under a serial or parallel migration mechanism, and an actual cross status bit for identifying the actual state of the current cross.
  • the cross setting status bit value is a crossover to be migrated, or the cross setting is successful, or the cross setting fails;
  • the actual cross status bit takes the value of the output direction to be closed, or the closing direction to be closed, or the transceiver is to be disconnected, or the transceiver is closed.
  • the migration request is a migration request for the PC to be migrated to the SPC, and the common migration of the current operation connection and its associated connection according to the set of the cross state control bits is:
  • the migration request is a migration request for the SPC to be migrated to the PC, and the common migration of the current operation connection and its associated connection according to the set cross state control bit is:
  • the current operation connection is a working connection, and the associated connection is a protection connection; or the current operation connection is a protection connection, and the associated connection is a working connection.
  • An SNCP service migration device includes:
  • a receiving module configured to receive a migration request of the subnet connection to protect the SNCP service, where the migration request includes: the PC is migrated to the SPC, and the SPC is migrated to the PC;
  • a setting module configured to separately set a cross state control bit of the current operation connection and its associated connection according to the received migration request
  • An implementation module configured to implement the current operation connection according to the set cross state control bit Joint migration of their associated connections
  • a modification module configured to respectively modify a cross state control bit of the current connection and its associated connection according to the result of the migration.
  • the cross state control bit set by the setting module and/or modified by the modifying module includes: a cross setting status bit and an actual cross status bit, wherein the timing of the shift includes: crossover to be migrated, crossover setting The success of the crossover fails.
  • the actual crossover status bit is used to identify the actual status of the current crossover. The values include: the send direction is closed, the close direction is closed, the transceiver is disconnected, and the transceiver is closed.
  • the implementation module includes:
  • a first implementation module configured to: when the receiving module receives a migration request that the PC migrates to the SPC, if the current operation connection and the associated connection thereof receive the migration request, the current operation connection and the current operation connection Associate the connection to implement a common migration;
  • a second implementation module configured to: when the receiving module receives a migration request for the SPC to be migrated to the PC, if the one of the current operation connection and one of the associated connections receives the migration request, Its associated connections implement a common migration.
  • the timing and specific actions of the cross-migration are determined by setting the cross-set status bit and the actual cross-state bit, and the cross-implementation of the protection relationship between the first and last nodes of the SNCP service can be implemented.
  • One-time migration ensures consistency of cross-administration permissions for work connections and protection connections.
  • FIG. 1 is a flowchart of a method for SNCP service migration according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a normal RSVP-TE signaling of a PC based on a parallel mechanism being migrated to an SPC according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a parallel mechanism based SPC migration to a PC according to an embodiment of the present invention. RSVP-TE signaling diagram;
  • FIG. 4 is a diagram showing an RSVP-TE signaling diagram in which a PC based on a serial mechanism is migrated to an SPC and a first node cross-transition fails;
  • FIG. 5 is a schematic diagram of connection of a tail node according to an embodiment of the present invention.
  • FIG. 6 is a block diagram of an SNCP service migration apparatus according to an embodiment of the present invention.
  • FIG. 7 is a block diagram showing a preferred structure of an SNCP service migration apparatus according to an embodiment of the present invention. detailed description
  • the main idea of the present invention is mainly to implement a one-time migration (possibly when operating a working connection or protecting a connection) for tags and intersections with protection relationships, rather than two migrations when operating a working connection and protecting a connection.
  • the present invention sets the cross-setting status bit and the actual cross-state bit in the connection information, and decides the timing and specific action of the cross-migration based on the cross-setting status bit and the actual cross-state bit.
  • the invention is smooth and compatible with the parallel and serial migration schemes of the SNCP service, and implements a one-time migration of the protection relationship between the first and the last nodes of the SNCP service, thereby ensuring the consistency of work and protection cross management rights.
  • FIG. 1 is a flowchart of a method for migrating an SNCP service according to an embodiment of the present invention. As shown in FIG. 1, the method of the present invention includes:
  • Step 102 Receive a migration request of the SNCP service, where the migration request includes one of the following: the PC is migrated to the SPC, and the SPC is migrated to the PC.
  • Step 104 According to the received migration request, respectively set a cross-state control bit of the current operation connection and its associated connection, and implement a common migration of the current operation connection and its associated connection according to the set cross-state control bit.
  • This step specifically includes: in the case that the migration request is for the PC to be migrated to the SPC, and when In the case where the pre-operation connection and its associated connection receive the migration request, a common migration is performed on the current operation connection and its associated connection; and, in the case where the migration request is SPC migration to the PC, and the current operation connection and In the case where one of the associated connections receives the migration request, a common migration is performed on the current operational connection and its associated connection.
  • the cross status control bits include: a cross setting status bit and an actual cross status bit, wherein the cross setting status bit is used to determine the timing of the cross-connection migration under the serial or parallel migration mechanism, and the values include: The crossover setting succeeds and the crossover setting fails.
  • the actual crossover status bit is used to identify the actual status of the current crossover.
  • the values include: the send direction is closed, the close direction is closed, the transceiver is disconnected, and the transceiver is closed.
  • Step 106 Modify the cross state control bits of the current connection and its associated connection according to the result of the migration.
  • the associated connection when the current operation connection is a working connection, the associated connection is a protection connection; or, when the current operation connection is a protection connection, the associated connection is a working connection.
  • the timing and action of the cross-migration are discriminated by the cross-setting status bit and the actual cross-state bit, and the crossover of the protection relationship between the first and last nodes of the SNCP service is implemented.
  • the secondary migration ensures the consistency of the cross-administration permissions of the working connection and the protection connection.
  • the present invention is used for migration between a PC and an SPC of an ASON network (PC migration to SPC, hereinafter referred to as PC-SPC migration, SPC migration to PC, hereinafter abbreviated as SPC-PC migration).
  • PC-SPC migration SPC migration to PC
  • SPC-PC migration Due to network failures and other reasons, the signaling process for implementing PC-SPC migration is not unique.
  • the following example uses RSVP-TE (also CR-LDP).
  • RSVP-TE also CR-LDP
  • There are two main signaling protocols to implement connection management: Constraint-based Routed Label Distribution Protocol (CR-LDP) and Resource Reservation Protocol based on Traffic Engineering Extension (RSVP-TE, Resource) Reservation Protocol Traffic Engineering ) will be ⁇ 1 J out
  • the main signaling scenario for the migration between the PC and the SPC of the SNCP service will be ⁇ 1 J out.
  • RSVP-TE For SPC migration to PC, RSVP-TE's elegant deletion signaling process is used, but it is not limited to using elegant deletion.
  • the mode of the crossover is set in the Resv mode when the PC is migrated to the SPC, indicating that the node performs the cross-connection migration after receiving the Resv signaling, and therefore, the method involved in the embodiment of the present invention is involved.
  • the migration between the PC and the SPC is described by taking the Resv setting cross as an example, but is not limited to the way of cross setting.
  • the embodiments of the present invention are all two-way SNCP services. Since the cross-protection relationship between the first and the last nodes of the two-way SNCP service is the same, the embodiments of the present invention are described by taking the tail node as an example in the following embodiments. It should be noted that in Fig. 2 to Fig. 5, A is the head node, B and C are the intermediate nodes, and D is the tail node.
  • Example 1 is the normal flow of PC migration to SPC based on parallel mechanism.
  • FIG. 2 is a schematic diagram of normal RSVP-TE signaling of a PC based on a parallel mechanism being migrated to SPC according to an embodiment of the present invention.
  • the normal signaling flow for PC migration to SPC is consistent with the connection creation process described in IETF RFC3473.
  • Figure 2 depicts the PC-SPC migration of the SNCP service based on the parallel mechanism.
  • the so-called parallel is the Path signaling indicating that the first node sends out the working connection and the protection connection in parallel. For the tail node, it is impossible to determine the working connection before the first node.
  • the Path signaling of the connection is also protected, so the connection arriving after the migration request is cross-connected. This embodiment is described by taking the path signaling of the protection connection first.
  • the tail node receives the Path signaling of the protection connection, indicating that the PC_SPC migration request from the upstream node arrives.
  • a local protection connection control block is created according to the PC-SPC migration request from the upstream node.
  • the cross-setting status bit of the protection connection control block is initialized, that is, the cross setting is successful, and the actual cross status bit is closed for transmission and reception.
  • the search for the working connection control block failed. Since the Path signaling of the working connection has not yet reached the tail node, its connection control block is also not created.
  • the tail node considers that the migration request for the protection connection is received first, therefore, the cross setting of the protection connection is set.
  • the status bit is the cross-to-migrate state. The cross-connection migration is not implemented, and the Resv signaling of the protection connection is directly sent back to the upstream node, and the PC-SPC migration of the protection connection is completed.
  • the tail node receives the Path signaling of the working connection and creates a local working connection control block.
  • the protection connection cross status bit is viewed. Since the protection connection cross setting status bit is cross-to-migrate, the tail node considers that the migration request of the working connection is later than the protection connection, so the working connection is implemented and protected at this time. Cross-migration of the sending and receiving directions, migrating permissions from the management plane to the control plane.
  • the tail node sends back the Resv signaling of the working connection to the upstream node, and the work of the tail node SNCP service and the protection PC-SPC migration are completed.
  • Example 2 is a normal flow of SPC migration to PC based on parallel mechanism.
  • FIG. 3 is a schematic diagram of normal RSVP-TE signaling of a SPC based on a parallel mechanism being migrated to a PC according to an embodiment of the present invention.
  • the normal signaling flow for SPC migration to PC is consistent with the connection creation process described in IETF RFC3473.
  • Figure 3 depicts the SPC-PC migration of the SNCP service based on the parallel mechanism, that is, the Path (R&D) message indicating that the first node sends out the working connection and the protection connection in parallel.
  • the Path signaling arrives first, and cross-migration is performed on the connection that the migration request arrives first.
  • the Path (R&D) signaling of the working connection is first arrived as an example.
  • the tail node receives the Path (R&D) signaling of the working connection, indicating that the SPC-PC migration request from the upstream node has arrived.
  • R&D Path
  • the tail node implements the work and protects the cross-transfer of the transmit and receive directions (migrated by the control plane) To the management plane), and modify the cross-setting status bit of the working connection and the protection connection to the cross setting successfully. Modifying the actual cross state of the working connection and the protection connection is that the transceiver is disconnected, and the tail node sends back the PathErr signaling of the working connection.
  • tail node sends back the PathErr signaling of the protection connection, and the SPC-PC migration of the tail node SNCP connection is completed.
  • Example 3 is a serial mechanism based PC migration to SPC, the first node cross migration failed.
  • FIG. 4 is a schematic diagram of RSVP-TE signaling in which a PC based on a serial mechanism is migrated to an SPC and a cross-connection of a first node fails.
  • Figure 4 depicts the PC_SPC migration of the SNCP service based on the serial mechanism, that is, the PC-SPC migration that indicates that the first node sends the working connection's Path signaling to implement the working connection. After the working connection is successfully migrated, the Path signaling of the protection connection is sent. Implementing a protected connection for PC-SPC migration; During the implementation of the protection connection migration, the first node cross migration failed. Therefore, the SPC-PC migration is rolled back for the tail node that has successfully executed the PC-SPC migration.
  • the working connection is successfully migrated, so the first node will automatically deliver the SPC-PC migration implementation rollback of the working connection.
  • the SPC migration to the PC uses the elegant deletion signaling process of RSVP-TE.
  • the head node shall issue Path (R&D) signaling downstream.
  • R&D Path
  • the cross-connection setting for the first node fails, so the first node will send the Pathtear delete signaling implementation signaling state deletion.
  • the tail node it is impossible to determine whether the Path (R&D) signaling of the working connection or the Pathtear signaling of the protection connection arrives first, and the tail node will first reach the connection to the migration request. Implement cross-migration.
  • the Path (R&D) signaling of the working connection is first arrived as an example.
  • the tail node receives the Path signaling that receives the working connection, indicating that the PC-SPC migration request from the upstream node arrives.
  • the working connection PC—SPC requests to arrive first.
  • the tail node does not perform the cross-migration action at this time, but directly returns the working connection Resv signaling to the upstream node, and the PC-SPC migration of the working connection is completed.
  • the tail node receives the Path signaling of the protection connection, as described in Example 1, at which point the cross-migration of the work and protection direction is implemented.
  • modify the cross-setting status bit of the working connection and the protection connection to successfully set the crossover. Modify the actual cross state of the working connection and the protection connection to close the transceiver.
  • the tail node sends back the Resv signaling of the protection connection, and the tail node completes the SNCP service work and protects the connected PC-SPC migration.
  • the first node fails to implement PC-SPC cross-migration.
  • the working connection SPC-PC migration implementation rollback will be initiated, and the first node will issue Path (R&D) signaling to the downstream node to implement the rollback of the working connection.
  • R&D Path
  • the protection connection sends a Pathtear signaling downstream to implement a rollback of the protection connection due to the failure of the migration crossover after receiving the Resv signaling.
  • the tail node receives the Path (R&D) signaling of the working connection, and checks that the cross-setting status bit of the working connection is successful for the cross setting, and the actual cross status bit of the working connection is closed for the transceiving (set in step 404). At this point, work and protection of the SPC-PC crossover is implemented. And modify the cross-setting status bit of the working connection and the protection connection to the cross setting successfully, and modify the actual cross status bit of the working connection and the protection connection to be disconnected. The tail node sends back the PathErr signaling of the working connection to the upstream node.
  • R&D Path
  • the tail node receives the Pathtear signaling of the protection connection, and checks that the cross-setting status bit of the protection connection is successfully set, and the actual cross-state status bit is disconnected. Therefore, the migration of the SPC-PC migration connection that protects the connection cross is no longer implemented.
  • the tail node completes the work of the SNCP service and protects the rollback of the SPC-PC migration.
  • the case where the Pathtear signaling of the protection connection first arrives at the tail node is similar to the foregoing processing, and is not described here.
  • an SNCP service migration apparatus is further provided, and the apparatus may be used to implement the SNCP service migration method provided by the foregoing method embodiment.
  • FIG. 6 is a block diagram of an SNCP service migration apparatus according to an embodiment of the present invention
  • FIG. 7 is a block diagram showing a preferred structure of an SNCP service migration apparatus according to an embodiment of the present invention.
  • the SNCP service migration apparatus includes: a receiving module 10, a setting module 20, an implementing module 30, and a modifying module 40.
  • a receiving module 10 receives a setting module 10
  • a setting module 20 receives a setting module 20
  • a modifying module 40 receives a setting module 20
  • a setting module 20 receives a setting value from a setting module 20
  • a modifying module 40 modify the modifying module 40.
  • the receiving module 10 is configured to receive a migration request of the SNCP service, where the migration request includes one of the following: a PC-SPC migration, an SPC-PC migration.
  • the setting module 20 is connected to the receiving module 10, and is configured to respectively set a cross state control bit of the current operating connection and its associated connection according to the migration request received by the receiving module 10.
  • the implementation module 30 is connected to the setting module 20, and is configured to implement a common migration of the current operation connection and its associated connection according to the cross state control bit set by the setting module 20; wherein the cross state control bit includes: a cross setting status bit, an actual crossover Status bit.
  • the cross-setting status bit is used to determine the timing of the cross-connection migration under the serial or parallel migration mechanism.
  • the values are: cross-to-migrate, cross-setting success, cross-setting failure; actual cross-status bit, used to identify the current crossover
  • the actual state its value is: the direction of the direction is closed, the direction of closure is closed, the transceiver is disconnected, and the transceiver is closed.
  • the modification module 40 is connected to the implementation module 30 for implementing the migration according to the implementation module 30.
  • the result modifies the cross state control bits of the current connection and its associated connections, respectively.
  • the implementation module 30 further includes: a first implementation module 310, configured to receive, by the receiving module 10, a migration request for the PC to be migrated to the SPC, and connect the current operation. And in the case that the association connection receives the migration request, the common operation connection and the associated connection are jointly migrated; the second implementation module 320 is configured to receive the migration request that the SPC is migrated to the PC, and the current operation is connected. In the case where one of its associated connections receives a migration request, a common migration is performed on the current operational connection and its associated connection.
  • the associated connection when the current operation connection is a working connection, the associated connection is a protection connection; or, when the current operation connection is a protection connection, the associated connection is an active connection.
  • FIG. 1 to FIG. 5 For a specific implementation process of the SNCP service migration apparatus according to the embodiment of the present invention, reference may be made to FIG. 1 to FIG. 5 , and details are not described herein.
  • the present invention can smoothly conform to the parallel and serial migration modes of the SNCP service, and set the status bit and the actual cross status bit through the cross in the connection information.

Landscapes

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

Abstract

本发明公开了一种SNCP业务迁移方法及装置，其中，该方法包括：接收SNCP业务的迁移请求，其中，迁移请求包括以下之一：PC迁移为SPC、SPC迁移为PC；根据接收到的迁移请求，分别设置当前操作连接及其关联连接的交叉状态控制位，并根据设置的交叉状态控制位实施当前操作连接及其关联连接的共同迁移；根据迁移的结果分别修改当前连接及其关联连接的交叉状态控制位。通过本发明，能够保证SNCP业务迁移的工作连接和保护连接交叉管理权限的一致性。

Description

SNCP业务迁移方法及装置 技术领域
本发明涉及自动交换光网络技术，尤其涉及一种子网连接保护（ SNCP, Sub-network Connection Protection ) 业务迁移方法及装置。 背景技术
自动交换光网络 ( ASON, Automatically Switched Optical Network )是 在传统光网络基础上发展的一种新技术。 ASON通过其完备的路由、 信令、 自动发现等协议机制的动作， 为用户业务提供了智能、 灵活、 高效的配置。
在 ASON中， 根据不同的连接需要以及业务的请求对象不同， 提供了 三种连接： 永久连接 ( PC, Permanent Connection ) 、 软永久连接 ( SPC, Soft Permanent Connection )和交换连接 ( SC, Switched Connection )。 在实 际网络运维中， 运营商需要在网络内根据需要作 SPC与 PC业务之间的迁 移。 当 PC迁移为 SPC时， 需要在 PC中引入控制平面的信令状态， 将标签 (此处的标签指 RFC3946所述的 SDH通用标签）和交叉管理权限迁移至控 制平面。 当 SPC迁移为 PC时， 需要删除 SPC的资源预留协议（RSVP, Resource Reservation Protocol )信令状态， 将标签与交叉管理权限迁移至控 制平面。
1+1子网连接保护 ( SNCP, Sub-network Connection Protection )业务为 传送网络中的一种常见业务类型， 其特点是在对业务的承载连接提供 1+1 备份， 即： 同时存在工作连接和保护连接。 对于首、 尾节点而言， 交叉连 接是并发优收的。 因此， 对于 SNCP业务， 无论是实施 SPC迁移为 PC, 还 是 PC迁移为 SPC,在正常流程与异常流程下均需要确保工作连接标签和保 护连接标签与交叉管理权限的一致性。 此外， 对于 SNCP业务的迁移， 可 能釆用串行方式， 即先迁移工作连接， 工作连接迁移成功后实施保护连接 的迁移； 也可能釆用并行方式， 即同时下发工作连接和保护连接的迁移。 无论釆用哪种方式， 在迁移正常或者异常中， 均不允许出现 SNCP业务下 两条连接的管理权限分别为管理平面和控制平面。 如果出现工作连接与保 护连接的交叉管理权限不一致， 由于管理平面无法操作权限在控制平面的 交叉， 而控制平面也无法操作权限在管理平面的交叉， 因此， 将直接导致 无法在管理平面内实施该业务的删除， 也无法在控制平面内实施业务恢复， 优化， 删除， 修改等操作。
因此， 现有 SNCP业务在迁移过程中出现的具备保护关系的交叉权限 不一致的问题， 影响了后续的业务操作。 发明内容
本发明的主要目的在于提供一种 SNCP 业务迁移方法及装置， 在对 SNCP业务首、尾节点具备保护关系的交叉实施迁移时， 能够保证工作连接 和保护连接交叉管理权限的一致性。
本发明的另一目的在于提供一种 SNCP业务迁移装置， 在对 SNCP业 务首、 尾节点具备保护关系的交叉实施迁移时， 能够保证工作连接和保护 连接交叉管理权限的一致性。
为了解决上述问题， 根据本发明的一个方面， 提供了一种 SNCP业务 迁移方法。
一种子网连接保护 SNCP 业务迁移方法， 应用于自动交换光网络 ASON, 所述方法包括：
接收 SNCP业务的迁移请求； 根据接收到的所述迁移请求， 分别设置 当前操作连接及其关联连接的交叉状态控制位， 并根据设置的所述交叉状 态控制位实施所述当前操作连接及其关联连接的共同迁移；
根据迁移结果分别修改所述当前连接及其关联连接的交叉状态控制位； 所述迁移请求包括： 以永久链接 PC迁移为软永久链接 SPC、 SPC迁移 为 PC之一。
所述交叉状态控制位包括： 用于在串行或并行迁移机制下决策交叉连 接迁移的时机的交叉设置状态位、 以及用于标识当前交叉的实际状态的实 际交叉状态位。
所述交叉设置状态位取值为交叉待迁移、 或交叉设置成功、 或交叉设 置失败；
所述实际交叉状态位取值为发方向闭合、 或收方向闭合、 或收发均断 开、 或收发均闭合。
所述迁移请求为 PC迁移为 SPC的迁移请求， 所述根据设置的所述交 叉状态控制位实施所述当前操作连接及其关联连接的共同迁移为：
在所述当前操作连接及其关联连接都接收到迁移请求的情况下， 对所 述当前操作连接及其关联连接实施共同迁移。
所述迁移请求为 SPC迁移为 PC的迁移请求， 所述根据设置的所述交 叉状态控制位实施所述当前操作连接及其关联连接的共同迁移为：
在所述当前操作连接及其关联连接之一接收到迁移请求的情况下， 对 所述当前操作连接及其关联连接实施共同迁移。
所述当前操作连接为工作连接， 其关联连接为保护连接； 或者， 所述当前操作连接为保护连接， 其关联连接为工作连接。
一种 SNCP业务迁移装置， 包括：
接收模块， 用于接收子网连接保护 SNCP业务的迁移请求， 其中， 所 述迁移请求包括 PC迁移为 SPC、 SPC迁移为 PC之一；
设置模块， 用于根据接收到的所述迁移请求， 分别设置当前操作连接 及其关联连接的交叉状态控制位；
实施模块， 用于根据设置的所述交叉状态控制位实施所述当前操作连 接及其关联连接的共同迁移；
修改模块， 用于根据迁移的结果分别修改所述当前连接及其关联连接 的交叉状态控制位。
所述设置模块设置的和 /或所述修改模块修改的所述交叉状态控制位包 括： 交叉设置状态位、 实际交叉状态位， 其中， 移的时机， 其取值包括： 交叉待迁移、 交叉设置成功、 交叉设置失败； 所述实际交叉状态位， 用于标识当前交叉的实际状态， 其取值包括： 发方向闭合、 收方向闭合、 收发均断开、 收发均闭合。
所述实施模块包括：
第一实施模块， 用于在所述接收模块接收到 PC迁移为 SPC的迁移请 求时， 在所述当前操作连接及其关联连接都接收到迁移请求的情况下， 对 所述当前操作连接及其关联连接实施共同迁移；
第二实施模块， 用于在所述接收模块接收到 SPC迁移为 PC的迁移请 求时， 在所述当前操作连接及其关联连接之一接收到迁移请求的情况下， 对所述当前操作连接及其关联连接实施共同迁移。
与现有技术相比， 根据本发明的上述技术方案， 通过设置交叉设置状 态位和实际交叉状态位来判别交叉迁移的时机和具体动作， 能够对 SNCP 业务首、 尾节点具备保护关系的交叉实施一次性迁移， 保证了工作连接和 保护连接交叉管理权限的一致性。 附图说明
图 1为本发明实施例的 SNCP业务迁移方法的流程图；
图 2 为本发明实施例的基于并行机制的 PC 迁移为 SPC 的正常 RSVP-TE信令图；
图 3 为本发明实施例的基于并行机制的 SPC 迁移为 PC 的正常 RSVP-TE信令图；
图 4为本发明实施例的基于串行机制的 PC迁移为 SPC,首节点交叉迁 移失败的 RSVP-TE信令图；
图 5为本发明实施例的尾节点的连接示意图；
图 6为本发明实施例的 SNCP业务迁移装置的框图；
图 7为本发明实施例的 SNCP业务迁移装置的优选结构的框图。 具体实施方式
为使本发明的目的、 技术方案和优点更加清楚， 以下结合附图及具体 实施例， 对本发明作进一步地详细说明。
本发明的主要思想主要在于， 对于具有保护关系的标签和交叉， 实施 一次性迁移 （可能是在操作工作连接或者保护连接的时候） ， 而非在操作 工作连接和保护连接时分两次迁移。 本发明通过在连接信息中设置交叉设 置状态位和实际交叉状态位， 并根据交叉设置状态位和实际交叉状态位决 策交叉迁移的时机及具体的动作。 本发明平滑兼容 SNCP业务并行和串行 两种迁移方案， 对于 SNCP业务首、 尾节点具备保护关系的交叉实施一性 次迁移， 确保了工作和保护交叉管理权限的一致性。
根据本发明的实施例， 提出了一种 SNCP业务迁移方法， 该方法能够 应用于 ASON网络。图 1为本发明实施例的 SNCP业务迁移方法的流程图， 如图 1所示， 本发明方法包括：
步骤 102: 接收 SNCP业务的迁移请求， 其中， 该迁移请求包括以下之 一： PC迁移为 SPC、 SPC迁移为 PC。
步骤 104: 根据接收到的迁移请求， 分别设置当前操作连接及其关联连 接的交叉状态控制位， 并根据设置的交叉状态控制位实施当前操作连接及 其关联连接的共同迁移。
本步骤具体包括： 在迁移请求为 PC迁移为 SPC的情况下， 并且在当 前操作连接及其关联连接都接收到该迁移请求的情况下， 对当前操作连接 及其关联连接实施共同迁移； 以及， 在迁移请求为 SPC迁移为 PC的情况 下， 并且在当前操作连接及其关联连接其中之一接收到该迁移请求的情况 下， 对当前操作连接及其关联连接实施共同迁移。
其中， 交叉状态控制位包括： 交叉设置状态位和实际交叉状态位， 其 中， 交叉设置状态位， 用于在串行或并行迁移机制下决策交叉连接迁移的 时机， 其取值包括： 交叉待迁移、 交叉设置成功、 交叉设置失败； 实际交 叉状态位， 用于标识当前交叉的实际状态， 其取值包括： 发方向闭合、 收 方向闭合、 收发均断开、 收发均闭合。
步骤 106:根据迁移的结果分别修改当前连接及其关联连接的交叉状态 控制位。
其中， 上述的当前操作连接为工作连接时， 其关联连接为保护连接； 或者， 上述的当前操作连接为保护连接时， 其关联连接为工作连接。
与现有技术相比， 根据本发明的上述技术方案， 通过交叉设置状态位 和实际交叉状态位来判别交叉迁移的时机和动作， 对 SNCP业务首、 尾节 点具备保护关系的交叉实施了一性次迁移， 保证了工作连接和保护连接交 叉管理权限的一致性。
下面结合附图及具体实施方式对本发明作进一步说明。
本发明用于 ASON网络的 PC与 SPC之间迁移（ PC迁移为 SPC, 下文 简写为 PC— SPC迁移， SPC迁移为 PC, 下文简写为 SPC— PC迁移） 。 由于 网络故障等原因，实施 PC— SPC迁移的信令流程并不唯一，以下以 RSVP-TE 为例（亦可釆用 CR-LDP )说明。 目前存在两种主要的信令协议来实现连接 管理： 基于约束路由的标记分发协议 （CR-LDP, Constraint-based Routed Label Distribution Protocol ) 和基于流量工程扩展的资源预留协议 ( RSVP-TE, Resource Reservation Protocol Traffic Engineering ) , 将歹1 J出 SNCP业务的 PC与 SPC之间迁移的主要信令场景。 对于 SPC迁移为 PC, 釆用的是 RSVP-TE的优雅删除信令流程， 但不限于使用优雅删除。 为了简 化失败过程中的回滚， 通常在作 PC迁移为 SPC时釆用 Resv设置交叉的模 式， 表示节点在接收到 Resv信令后才实施交叉连接的迁移， 因此， 本发明 实施例中涉及的 PC与 SPC之间的迁移是以 Resv设置交叉为例描述， 但不 限于交叉设置的方式。
本发明中的实施例均为双向 SNCP业务， 由于双向 SNCP业务的首、 尾节点交叉保护关系相同， 因此， 以下实施例中均以尾节点为例来描述本 发明实施例。 需要说明， 在图 2至图 5中， A为首节点， B和 C为中间节 点， D为尾节点。
实例 1为基于并行机制的 PC迁移为 SPC的正常流程。
图 2 为本发明实施例的基于并行机制的 PC 迁移为 SPC 的正常 RSVP-TE信令图。 如图 2所示， PC迁移为 SPC的正常信令流程与 IETF RFC3473 中描述的连接创建流程一致。 图 2 中描述的是基于并行机制的 SNCP业务的 PC— SPC迁移， 所谓并行， 是表示首节点并行发出工作连接和 保护连接的 Path信令， 对于尾节点， 则无法确定先行到达的是工作连接还 是保护连接的 Path信令， 因此， 将对迁移请求后到达的连接实施交叉连接。 本实施例以保护连接的 Path信令先到达为例进行说明。
首先， 尾节点接收到保护连接的 Path信令， 则表示来自上游节点的 PC_SPC迁移请求到达。
接着， 根据来自上游节点的 PC— SPC 迁移请求创建本地的保护连接控 制块， 此时保护连接控制块的交叉设置状态位为初始化， 即， 交叉设置成 功， 实际交叉状态位为收发均闭合。 查找工作连接控制块失败， 由于此时 工作连接的 Path信令还未到达尾节点， 因此其连接控制块也未创建。此时， 尾节点认为先接收到保护连接的迁移请求， 因此， 置保护连接的交叉设置 状态位为交叉待迁移状态， 不实施交叉连接迁移， 而直接向上游节点回送 保护连接的 Resv信令， 保护连接的 PC— SPC迁移完成。
然后，尾节点接收到工作连接的 Path信令，创建本地工作连接控制块。 此时查看保护连接交叉状态位， 由于保护连接交叉设置状态位为交叉待迁 移， 则此时尾节点认为工作连接的迁移请求晚于保护连接到达， 因此， 此 时工作连接一并实施工作和保护的收发方向的交叉迁移， 将权限由管理平 面迁移至控制平面。
之后， 接收到交叉迁移成功请求后， 修改工作连接和保护连接的交叉 设置状态位为交叉设置成功， 修改工作连接和保护连接的实际交叉状态为 收发均闭合。
最后， 尾节点向上游节点回送工作连接的 Resv信令， 尾节点 SNCP业 务的工作和保护 PC— SPC迁移完成。
通过该实例， 减少了交叉连接迁移的回滚。 在具体实施过程中， 工作 连接 Path信令先到达尾节点的情况与上述处理类似， 此处不赘述。
实例 2为基于并行机制的 SPC迁移为 PC的正常流程。
图 3 为本发明实施例的基于并行机制的 SPC 迁移为 PC 的正常 RSVP-TE信令图。 如图 3所示， SPC迁移为 PC的正常信令流程与 IETF RFC3473 中描述的连接创建流程一致。 图 3 中描述的是基于并行机制的 SNCP业务的 SPC— PC迁移，即表示首节点并行发出工作连接和保护连接的 Path ( R&D ) 消息， 对于尾节点， 则无法确定是工作连接还是保护连接的 Path信令先行到达， 将对迁移请求先到达的连接实施交叉迁移。 此处以工 作连接的 Path ( R&D )信令先到达为例说明。
首先， 尾节点接收到工作连接的 Path ( R&D )信令， 则表示来自上游 节点的 SPC— PC迁移请求到达。
接着， 尾节点实施工作和保护收发方向的交叉迁移 （由控制平面迁移 至管理平面） ， 并修改工作连接和保护连接的交叉设置状态位为交叉设置 成功。 修改工作连接和保护连接的实际交叉状态为收发均断开， 尾节点回 送工作连接的 PathErr信令。
然后， 保护连接的 Path ( R&D )信令到达后， 查看保护连接控制块的 交叉设置状态位和实际交叉状态位。 此时， 保护连接的交叉设置状态位为 交叉设置成功， 实际交叉状态为收发均断开 （在步骤 302修改） 。 因此， 不再实施保护连接交叉的 SPC— PC迁移连接的迁移。
最后， 尾节点回送保护连接的 PathErr信令， 尾节点 SNCP 连接的 SPC— PC迁移完成。
通过该实例， 快速完成了对首、 尾节点存在保护关系交叉的迁移。 在 具体实施过程中， 保护连接 Path ( R&D )先到达尾节点的情况与上述处理 类似， 此处不赘述。
实例 3为基于串行机制的 PC迁移为 SPC, 首节点交叉迁移失败。
图 4为本发明实施例的基于串行机制的 PC迁移为 SPC,首节点交叉迁 移失败的 RSVP-TE信令图。 图 4描述的是基于串行机制的 SNCP业务的 PC_SPC迁移， 即表示首节点先发送工作连接的 Path信令实施工作连接的 PC— SPC迁移， 工作连接迁移成功后， 发送保护连接的 Path信令实施保护 连接的 PC— SPC迁移； 在实施保护连接迁移过程中， 首节点交叉迁移失败。 因此， 对于已成功执行 PC— SPC迁移的尾节点将实施 SPC— PC迁移进行回 滚。 对于首节点， 工作连接迁移成功， 因此首节点将自动下发工作连接的 SPC— PC迁移实施回滚， 如上所述， SPC迁移为 PC釆用的是 RSVP-TE的 优雅删除信令流程， 即首节点须向下流发出 Path ( R&D )信令。 对于保护 连接，对于首节点交叉设置失败， 因此首节点将发送 Pathtear的删除信令实 施信令状态删除。 对于尾节点， 无法确定是工作连接的 Path ( R&D )信令 还是保护连接的 Pathtear信令先行到达，尾节点将对迁移请求先到达的连接 实施交叉迁移。 此处以工作连接的 Path ( R&D )信令先到达为例说明。 首先， 尾节点接收接收到工作连接的 Path信令， 此时表示来自上游节 点的 PC— SPC迁移请求到达。 工作连接的 PC— SPC请求先行到达， 如实例 1 中所述， 尾节点此时不作交叉迁移动作， 而直接回送工作连接 Resv信令至 上游节点， 工作连接的 PC— SPC迁移完成。 尾节点接收到保护连接的 Path 信令， 如实例 1 中所述， 此时实施工作和保护收发方向的交叉迁移。 接收 到交叉迁移成功请求后， 修改工作连接和保护连接的交叉设置状态位为交 叉设置成功。 修改工作连接和保护连接的实际交叉状态为收发均闭合。 尾 节点回送保护连接的 Resv信令， 尾节点完成 SNCP业务工作和保护连接的 PC— SPC迁移。
接着， 首节点在接收到保护连接的 Resv信令后， 实施 PC— SPC交叉迁 移失败。 此时将发起工作连接 SPC— PC 迁移实施回滚， 首节点将向下游节 点发出 Path ( R&D )信令实施工作连接的回滚。 此外， 保护连接由于在接 收到 Resv信令后迁移交叉失败， 将向下游发出 Pathtear信令实施保护连接 的回滚。
然后， 尾节点接收到工作连接的 Path ( R&D )信令， 查看工作连接的 交叉设置状态位为交叉设置成功， 查看工作连接的实际交叉状态位为收发 均闭合 (步骤 404中设置） 。 此时一并实施工作和保护的 SPC— PC交叉迁 移。 并修改工作连接和保护连接的交叉设置状态位为交叉设置成功， 修改 工作连接和保护连接的实际交叉状态位为收发均断开。 尾节点回送工作连 接的 PathErr信令至上游节点。
之后，尾节点接收到保护连接的 Pathtear信令， 查看保护连接的交叉设 置状态位为交叉设置成功， 实际交叉状态位为收发均断开。 因此， 不再实 施保护连接交叉的 SPC— PC迁移连接的迁移
最后， 尾节点完成 SNCP业务的工作和保护 SPC— PC迁移的回滚。 在具体实施过程中，保护连接的 Pathtear信令先行到达尾节点的情况与 上述处理类似， 此处不赘述。
上述实例 1至 3均以尾节点为例进行描述， 但是， 本发明实施例不仅 限于此， 以首节点为例的处理过程与此类似， 此处不赘述。 并且， 结合图 5 理解上述实例 1至 3中的处理过程， 图 5是根据本发明实施例的尾节点的 连接示意图。
根据本发明实施例， 还提供了一种 SNCP业务迁移装置， 该装置可以 用于实现上述方法实施例所提供的 SNCP业务迁移方法。
图 6为本发明实施例的 SNCP业务迁移装置的框图， 图 7为本发明实 施例的 SNCP业务迁移装置的优选结构的框图。
如图 6所示， 根据本发明实施例的 SNCP业务迁移装置包括： 接收模 块 10、 设置模块 20、 实施模块 30、 修改模块 40, 下面结合附图详细描述 该装置的具体结构。
接收模块 10, 用于接收 SNCP业务的迁移请求， 其中， 该迁移请求包 括以下之一： PC— SPC迁移、 SPC— PC迁移。
设置模块 20, 与接收模块 10相连接， 用于根据接收模块 10接收到的 迁移请求， 分别设置当前操作连接及其关联连接的交叉状态控制位。
实施模块 30, 与设置模块 20相连接， 用于根据设置模块 20设置的交 叉状态控制位实施当前操作连接及其关联连接的共同迁移； 其中， 交叉状 态控制位包括： 交叉设置状态位、 实际交叉状态位。 交叉设置状态位， 用 于在串行或并行迁移机制下决策交叉连接迁移的时机， 其取值为： 交叉待 迁移、 交叉设置成功、 交叉设置失败； 实际交叉状态位， 用于标识当前交 叉的实际状态， 其取值为： 发方向闭合、 收方向闭合、 收发均断开、 收发 均闭合。
修改模块 40, 与实施模块 30相连接， 用于根据实施模块 30实施迁移 的结果分别修改当前连接及其关联连接的交叉状态控制位。
如图 7所示， 在图 6所示结构的基础上， 优选地， 实施模块 30进一步 包括： 第一实施模块 310 , 用于接收模块 10接收到 PC迁移为 SPC的迁移 请求， 在当前操作连接及其关联连接都接收到迁移请求的情况下， 对当前 操作连接及其关联连接实施共同迁移； 第二实施模块 320 , 用于接收模块 10接收到 SPC迁移为 PC的迁移请求， 在当前操作连接及其关联连接之一 接收到迁移请求的情况下， 对当前操作连接及其关联连接实施共同迁移。
在处理过程中， 上述的当前操作连接为工作连接时， 其关联连接为保 护连接； 或者， 上述的当前操作连接为保护连接时， 其关联连接为工作连 接。
在具体实施过程中， 根据本发明实施例提供的 SNCP业务迁移装置的 具体工作流程， 可以参考图 1至图 5 , 此处不赘述。
综上所示， 根据本发明上述技术方案， 与现有技术相比， 本发明能够 平滑兼容 SNCP业务并行和串行两种迁移方式， 通过对连接信息中的交叉 设置状态位和实际交叉状态位来判别交叉迁移的时机和动作， 无论对于 PC— SPC迁移还是 SPC— PC迁移，对其正常或异常流程， 都能够对 SNCP业 务首、 尾节点具备保护关系的交叉实施一性次迁移， 保证了工作连接和保 护连接交叉管理权限的一致性。
以上所述仅为本发明的实施例而已， 并不用于限制本发明， 对于本领 域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的权 利要求范围之内。

Claims

权利要求书
1、 一种子网连接保护 SNCP 业务迁移方法， 应用于自动交换光网络 ASON, 其特征在于， 所述方法包括：
接收 SNCP业务的迁移请求； 根据接收到的所述迁移请求， 分别设置 当前操作连接及其关联连接的交叉状态控制位， 并根据设置的所述交叉状 态控制位实施所述当前操作连接及其关联连接的共同迁移；
根据迁移结果分别修改所述当前连接及其关联连接的交叉状态控制位； 所述迁移请求包括： 以永久链接 PC迁移为软永久链接 SPC、 SPC迁移 为 PC之一。
2、 根据权利要求 1所述的方法， 其特征在于， 所述交叉状态控制位包 括： 用于在串行或并行迁移机制下决策交叉连接迁移的时机的交叉设置状 态位、 以及用于标识当前交叉的实际状态的实际交叉状态位。
3、 根据权利要求 2所述的方法， 其特征在于， 所述交叉设置状态位取 值为交叉待迁移、 或交叉设置成功、 或交叉设置失败；
所述实际交叉状态位取值为发方向闭合、 或收方向闭合、 或收发均断 开、 或收发均闭合。
4、 根据权利要求 2所述的方法， 其特征在于， 所述迁移请求为 PC迁 移为 SPC的迁移请求， 所述根据设置的所述交叉状态控制位实施所述当前 操作连接及其关联连接的共同迁移为：
在所述当前操作连接及其关联连接都接收到迁移请求的情况下， 对所 述当前操作连接及其关联连接实施共同迁移。
5、 根据权利要求 2所述的方法， 其特征在于， 所述迁移请求为 SPC迁 移为 PC的迁移请求，所述根据设置的所述交叉状态控制位实施所述当前操 作连接及其关联连接的共同迁移为：
在所述当前操作连接及其关联连接之一接收到迁移请求的情况下， 对 所述当前操作连接及其关联连接实施共同迁移。
6、 根据权利要求 1至 5任一项所述的方法， 其特征在于， 所述当前操 作连接为工作连接， 其关联连接为保护连接； 或者，
所述当前操作连接为保护连接， 其关联连接为工作连接。
7、 一种 SNCP业务迁移装置， 其特征在于， 包括：
接收模块， 用于接收子网连接保护 SNCP业务的迁移请求， 其中， 所 述迁移请求包括 PC迁移为 SPC、 SPC迁移为 PC之一；
设置模块， 用于根据接收到的所述迁移请求， 分别设置当前操作连接 及其关联连接的交叉状态控制位；
实施模块， 用于根据设置的所述交叉状态控制位实施所述当前操作连 接及其关联连接的共同迁移；
修改模块， 用于根据迁移的结果分别修改所述当前连接及其关联连接 的交叉状态控制位。
8、 根据权利要求 7所述的装置， 其特征在于， 所述设置模块设置的和 /或所述修改模块修改的所述交叉状态控制位包括： 交叉设置状态位、 实际 交叉状态位， 其中， 移的时机， 其取值包括： 交叉待迁移、 交叉设置成功、 交叉设置失败； 所述实际交叉状态位， 用于标识当前交叉的实际状态， 其取值包括： 发方向闭合、 收方向闭合、 收发均断开、 收发均闭合。
9、 根据权利要求 8所述的装置， 其特征在于， 所述实施模块包括： 第一实施模块， 用于在所述接收模块接收到 PC迁移为 SPC的迁移请 求时， 在所述当前操作连接及其关联连接都接收到迁移请求的情况下， 对 所述当前操作连接及其关联连接实施共同迁移；
第二实施模块， 用于在所述接收模块接收到 SPC迁移为 PC的迁移请 求时， 在所述当前操作连接及其关联连接之一接收到迁移请求的情况下 , 对所述当前操作连接及其关联连接实施共同迁移。
PCT/CN2009/075010 2009-08-10 2009-11-18 Sncp业务迁移方法及装置 WO2011017861A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
BRPI0924924-9A BRPI0924924A2 (pt) 2009-08-10 2009-11-18 Método e aparelho para migração de serviço de proteção de conexão de sub-rede (sncp).
RU2011137322/07A RU2479943C1 (ru) 2009-08-10 2009-11-18 Способ и устройство миграции услуг защиты соединений подсетей
EP09848191.4A EP2395773B1 (en) 2009-08-10 2009-11-18 Method and apparatus of sub-network connection protection (sncp) service migration
US13/258,886 US8554073B2 (en) 2009-08-10 2009-11-18 Method and apparatus for migrating sub-network connection protection (SNCP) service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910161358.1 2009-08-10
CN2009101613581A CN101998181B (zh) 2009-08-10 2009-08-10 Sncp业务迁移方法及装置

Publications (1)

Publication Number Publication Date
WO2011017861A1 true WO2011017861A1 (zh) 2011-02-17

Family

ID=43585862

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/075010 WO2011017861A1 (zh) 2009-08-10 2009-11-18 Sncp业务迁移方法及装置

Country Status (6)

Country Link
US (1) US8554073B2 (zh)
EP (1) EP2395773B1 (zh)
CN (1) CN101998181B (zh)
BR (1) BRPI0924924A2 (zh)
RU (1) RU2479943C1 (zh)
WO (1) WO2011017861A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931471B (zh) * 2009-06-23 2013-08-07 华为海洋网络有限公司 一种监控光纤线路状态的方法、中继器和海缆系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005060521A2 (en) * 2003-12-15 2005-07-07 Ciena Corporation 1+1 mesh protection
CN101047541A (zh) * 2006-05-27 2007-10-03 华为技术有限公司 1+1单向子网连接保护的方法和采用该方法的通信网络
CN101047440A (zh) * 2006-05-10 2007-10-03 华为技术有限公司 一种业务路径返回的方法
CN101299893A (zh) * 2008-06-03 2008-11-05 中兴通讯股份有限公司 一种自动交换光网络中基于状态转换的迁移方法
CN101321172A (zh) * 2008-07-22 2008-12-10 中兴通讯股份有限公司 链路两端管理权限一致性的校验装置及方法

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1277375C (zh) * 2003-07-31 2006-09-27 华为技术有限公司 一种光网络中永久连接和交换连接之间的转换方法
CN1816217B (zh) * 2005-02-06 2010-06-02 华为技术有限公司 基于节点地址更换的路径建立方法
WO2006116839A1 (en) * 2005-04-29 2006-11-09 Nortel Networks Limited Method and apparatus for non-disruptive call modification
CN1859369B (zh) * 2005-10-09 2010-07-14 华为技术有限公司 实现网络连接服务建立的方法及装置
CN100561962C (zh) * 2005-11-24 2009-11-18 华为技术有限公司 基于目录服务来实现网络连接服务建立的方法及系统
CN1866806B (zh) * 2005-12-22 2011-11-02 华为技术有限公司 共享格状网恢复的实现方法
CN100490390C (zh) * 2006-01-10 2009-05-20 华为技术有限公司 业务故障恢复方法
CN100563354C (zh) * 2006-07-03 2009-11-25 华为技术有限公司 一种自动交换光网络中实现业务保护的方法
CN101170482B (zh) 2006-10-26 2010-07-07 中兴通讯股份有限公司 Ason网络中通过控制平面实现spc激活/去激活的方法
CN100508469C (zh) * 2006-12-21 2009-07-01 华为技术有限公司 一种在带宽按需分配业务中调整带宽的方法
US8787170B2 (en) * 2007-01-24 2014-07-22 Ciena Corporation Methods and systems for existential provisioning of flexible line modules using distributed control
CN101304340B (zh) * 2007-05-09 2011-09-21 华为技术有限公司 一种资源状态监控方法及装置以及通信网络
CN101170494B (zh) 2007-11-21 2010-06-02 中兴通讯股份有限公司 自动交换光网络中的软重路由方法
US7852863B2 (en) * 2007-12-20 2010-12-14 Ciena Corporation System and methods for connections using automatically switched optical network control planes
US8559812B2 (en) * 2008-09-02 2013-10-15 Ciena Corporation Methods and systems for the hierarchical mesh restoration of connections in an automatically switched optical network
CN101394310B (zh) 2008-11-04 2011-05-04 烽火通信科技股份有限公司 一种构建管理通信网和信令通信网的装置和方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005060521A2 (en) * 2003-12-15 2005-07-07 Ciena Corporation 1+1 mesh protection
CN101047440A (zh) * 2006-05-10 2007-10-03 华为技术有限公司 一种业务路径返回的方法
CN101047541A (zh) * 2006-05-27 2007-10-03 华为技术有限公司 1+1单向子网连接保护的方法和采用该方法的通信网络
CN101299893A (zh) * 2008-06-03 2008-11-05 中兴通讯股份有限公司 一种自动交换光网络中基于状态转换的迁移方法
CN101321172A (zh) * 2008-07-22 2008-12-10 中兴通讯股份有限公司 链路两端管理权限一致性的校验装置及方法

Also Published As

Publication number Publication date
EP2395773A1 (en) 2011-12-14
CN101998181B (zh) 2013-09-11
RU2479943C1 (ru) 2013-04-20
EP2395773B1 (en) 2019-05-01
BRPI0924924A2 (pt) 2015-07-07
EP2395773A4 (en) 2017-06-21
CN101998181A (zh) 2011-03-30
US20120128353A1 (en) 2012-05-24
US8554073B2 (en) 2013-10-08
RU2011137322A (ru) 2013-03-20

Similar Documents

Publication Publication Date Title
EP1973267B1 (en) A service failure restoration method and system
Lang et al. RSVP-TE extensions in support of end-to-end generalized multi-protocol label switching (GMPLS) recovery
EP1758298B1 (en) Method and system for realizing the reliability guarantee of end-to-end quality of service
EP1953958B1 (en) Management of protection path bandwidth and changing of path bandwidth
US8068483B2 (en) Method for migration between a permanent connection and a switched connection in a transmission network
US8149693B2 (en) Method of implementing association in automatic switched optical network (ASON)
JP4199514B2 (ja) ネットワークを相互に接続する方法、及びそのための装置
WO2009146652A1 (zh) 一种自动交换光网络中连接迁移方法和系统
WO2008064612A1 (fr) Procédé, dispositif et système permettant d'effectuer un reroutage rapide dans un réseau mpls
WO2008037162A1 (fr) Procédé de gestion de services dans un réseau optique intelligent
JP4316822B2 (ja) パスの経路を変更する方法及びこれを用いるスイッチ装置
WO2011017861A1 (zh) Sncp业务迁移方法及装置
WO2013000384A1 (zh) 一种网络配置方法、环形网络系统和一种节点
JP4680151B2 (ja) データ伝送方法及び装置
WO2007071114A1 (fr) Procede pour le reacheminement sans interruption en reseau optique
US11323365B2 (en) Tearing down a label switched path through a communications network
KR101050881B1 (ko) Ｍｐｌｓ 망관리시스템에서 ｃｒ－ｌｓｐ 관리시스템 및그 방법
JP3777185B2 (ja) Ｇｍｐｌｓ＋ｉｐ／ｍｐｌｓネットワークおよびノード
WO2011015142A1 (zh) 自动交换光网络中交换连接的建立系统及方法
JP2003134148A (ja) Ｍｐｌｓ迂回方式
JP2001285356A (ja) ラベルスイッチパス接続装置、その方法、及び記録媒体
Li et al. Description of the Resource Reservation Protocol-Traffic-Engineered (RSVP-TE) Graceful Restart Procedures
Bardalai et al. Network Working Group D. Li Request for Comments: 5495 J. Gao Category: Informational Huawei A. Satyanarayana Cisco
Huang et al. IETF Draft Vishal Sharma Multi-Protocol Label Switching Ben-Mack Crane Expires: May 2001 Srinivas Makam Ken Owens Tellabs Operations, Inc.
Lang et al. RFC 4872: RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2009848191

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2011137322

Country of ref document: RU

WWE Wipo information: entry into national phase

Ref document number: 3817/KOLNP/2011

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 13258886

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: PI0924924

Country of ref document: BR

ENP Entry into the national phase

Ref document number: PI0924924

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20110926