WO2009146652A1 - 一种自动交换光网络中连接迁移方法和系统 - Google Patents

一种自动交换光网络中连接迁移方法和系统 Download PDF

Info

Publication number
WO2009146652A1
WO2009146652A1 PCT/CN2009/072115 CN2009072115W WO2009146652A1 WO 2009146652 A1 WO2009146652 A1 WO 2009146652A1 CN 2009072115 W CN2009072115 W CN 2009072115W WO 2009146652 A1 WO2009146652 A1 WO 2009146652A1
Authority
WO
WIPO (PCT)
Prior art keywords
migration
signaling
spc
node
value
Prior art date
Application number
PCT/CN2009/072115
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 中兴通讯股份有限公司
Publication of WO2009146652A1 publication Critical patent/WO2009146652A1/zh

Links

Classifications

    • 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
    • H04Q11/0071—Provisions for the electrical-optical layer interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0088—Signalling aspects

Definitions

  • the present invention relates to the field of service migration technologies in an optical communication network, and in particular to an ASON (Automatically Switched Optical Network) between a PC (Permanent Connection, Permanent Connection) and an SPC (Soft Permanent Connection). Methods and systems for mutual migration.
  • ASON Automatically Switched Optical Network
  • PC Permanent Connection, Permanent Connection
  • SPC Soft Permanent Connection
  • PC In ASON, three types of connections are provided depending on the connection needs and the request objects of the service: PC, Permanent Connection, Soft Permanent Connection (SPC), and Switched Connection.
  • SPC Soft Permanent Connection
  • Switched Connection In ASON, three types of connections are provided depending on the connection needs and the request objects of the service: PC, Permanent Connection, Soft Permanent Connection (SPC), and Switched Connection.
  • the PC is migrated to the SPC.
  • the signaling plane of the control plane needs to be introduced into the PC.
  • the label (the label here refers to the SDH universal label described in RFC3946) and the cross management rights are migrated to the control plane.
  • the SPC is migrated to the PC.
  • the general principle is that when the PC is migrated to an abnormal SPC, and the SPC is migrated to the PC, the final result needs to be guaranteed as the PC (that is, the management rights of the label and the cross-connection are on the management plane), that is, the label is only Cross-rights are migrated to the management plane, and tags and cross-connects are not allowed to be deleted.
  • the hop-by-hop implementation performs the mutual migration between the PC and the SPC, mainly by using the signaling from the ingress node to hop by hop by other nodes, and the signaling can use CR- LDP (based on route-restricted label distribution protocol) or RSVP-TE (based on stream) Volume engineering extended resource reservation protocol).
  • CR- LDP based on route-restricted label distribution protocol
  • RSVP-TE based on stream
  • LSP Label Switched Path
  • the RSVP-TE signaling hop-by-hop notification procedure can be found in RFC3209, RFC3473.
  • the prior art only the normal migration process (PC migration to SPC, SPC migration to PC) is considered, and the migration processing under abnormal conditions is not considered.
  • the signaling of the migration is the same as the signaling for establishing the deletion of the connection, and the current method does not consider the use of ordinary establishment and deletion signaling (RSVP-TE or CR-LDP).
  • RSVP-TE or CR-LDP ordinary establishment and deletion signaling
  • RSVP-TE signaling extensions supporting GMPLS are described in RFC3209 and RFC3473.
  • Pathr Pathtear.
  • ResvErr and ResvTear signaling resvErr and ResvTear signaling are not commonly used
  • the above signaling needs to release the label and the cross-connection.
  • migration only the management rights of the label and the cross-connection need to be migrated to the management plane. Therefore, if an error occurs in processing signaling, or if there is confusion in processing signaling, the label and cross-connection will be released, so that the service is interrupted and the robustness cannot be ensured.
  • the technical problem to be solved by the present invention is to provide a connection migration method and system in an automatic switched optical network, and to smoothly synchronize the connection establishment deletion signaling, to ensure that the distinction is a resource release or a rights migration, and the PC migration SPC fails or the SPC migrates the PC.
  • the connection establishment deletion signaling to ensure that the distinction is a resource release or a rights migration
  • the PC migration SPC fails or the SPC migrates the PC.
  • the present invention provides an automatic switching optical network connection migration method, in which a node and a related node exchange standard signaling for connection migration, wherein: a migration status bit field for identifying a migration operation state is set in the connection information,
  • the standard signaling carries the information of the signaling scenario, and the node performs state transition of the signaling scenario according to the information of the signaling scenario carried in the standard signaling and the value of the current migration status bit, and completes the permanent connection of the PC and the Soft permanent connection between phases of SPC Mutual migration.
  • the above method may also have the following features.
  • the node After the node is converted in the signaling scenario state, the node resets the value of the migration status bit.
  • the above method may also have the following features.
  • the information of the signaling scenario includes a type of a current signaling scenario
  • the type of the signaling scenario is connection deletion, connection establishment, PC migration to SPC, or migration from SPC to PC.
  • the above method may also have the following features.
  • the value of the migration status bit refers to:
  • the value of this field is: Non-migration status;
  • SPC to PC migration the value of this field is: Start SPC migration PC or SPC migration to PC success;
  • the above method may also have the following features.
  • the type of the signaling scenario is that when the SPC migrates to the PC, the node receives standard signaling from the upstream node or sends standard signaling to the downstream node, and the standard signaling is abnormal signaling, and the value of the migration status bit is PC migration.
  • the SPC operation succeeds or is not in the migration state, the value of the migration status bit is converted to start the SPC migration PC; when the node receives the standard signaling from the downstream node or sends standard signaling to the upstream node, and the standard signaling is abnormal signaling.
  • the value of the migration status bit is the value of the migration status bit when starting the SPC migration PC.
  • the SPC migration PC starts.
  • the above method may also have the following features.
  • the type of the signaling scenario is when the PC migrates to the SPC, when the node receives standard signaling from the downstream node or sends standard signaling to the upstream node, and the standard signaling is abnormal signaling, and the value of the migration status bit is PC migration.
  • the SPC label succeeds or the PC is migrated to SPC failure
  • the value of the migration status bit is converted to start the SPC migration PC; when the node receives standard signaling from the upstream node or sends standard signaling to the downstream node, and the standard signaling is Abnormal signaling, and the value of the migration status bit is PC
  • the migration SPC tag is successful or the PC migration SPC operation is successful
  • the value of the migration status bit is converted to start the SPC migration PC.
  • the above method may also have the following features.
  • the migration label and the cross-connection are connected to the management plane.
  • the present invention also provides an automatic switched optical network connection migration system, including a plurality of nodes composed of a head node and related nodes, where
  • the node is configured to exchange standard signaling with the related node, where the standard signaling carries information of the signaling scenario, and according to the value and standard signaling of the migration status bit field used to identify the migration operation state set in the connection information.
  • the information of the signaling scenario carried in the signaling scenario state transitions to complete the mutual migration between the permanently connected PC and the soft permanent connection SPC.
  • the above system may also have the following features.
  • the node is further configured to reset the value of the migration status bit after the signaling scenario state transition. Further, the above system may also have the following features.
  • the node is further configured to include a type of the current signaling scenario in the information of the signaling scenario; the type of the signaling scenario is connection deletion, connection establishment, PC migration to SPC, or migration from SPC to PC.
  • the above system may also have the following features.
  • the node is further configured to set a value of the migration status bit
  • the value of this field is: Non-migration status;
  • SPC to PC migration the value of this field is: Start SPC migration PC or SPC migration to PC success;
  • the above system may also have the following features.
  • the node is further configured to: when the node receives the standard signaling from the upstream node or sends the standard signaling to the downstream node, when the type of the signaling scenario is SPC to migrate to the PC, and the standard signaling is abnormal signaling, And the value of the migration status bit is converted to the SPC migration PC when the PC migration SPC operation is successful or not, and is also used to receive standard signaling from the downstream node or send standard signaling to the upstream node.
  • the type of the signaling scenario is that the SPC migrates to the PC, and the standard signaling is abnormal signaling
  • the value of the migration status bit is the value of the SPC migration PC
  • the value of the migration status bit is kept to start the SPC migration.
  • the above system may also have the following features.
  • the node is further configured to receive standard signaling from a downstream node or send standard signaling to an upstream node.
  • the standard signaling is abnormal signaling
  • the migration status bit is The value of the value of the migration status bit is converted to the start SPC migration PC when the PC migrates the SPC label successfully or the PC is migrated to the SPC. It is also used to receive standard signaling from the upstream node or to send standard signaling to the downstream node.
  • the type of the signaling scenario is when the PC migrates to the SPC, and the standard signaling is abnormal signaling, and the value of the migration status bit is converted to the value of the migration status bit when the PC migrates the SPC label successfully or the PC migration SPC operation succeeds. Start SPC migration of the PC.
  • the above system may also have the following features.
  • the node is further configured to receive standard signaling, determine that the standard signaling is abnormal signaling, and the value of the transition status bit after the conversion is started.
  • the SPC migrates the PC, the migration label and the cross-connection are connected to the management plane.
  • the present invention also provides an automatic switching optical network connection processing method, in which a migration status bit field for identifying a migration operation state is set in the connection information, and standard signaling carries information of a signaling scenario, and the node is configured according to the standard signaling.
  • the information of the carried signaling scenario and the value of the current migration status bit are used to perform signaling scenario state transition, and the connection establishment, deletion, and migration are completed.
  • connection migration status bit is set to be non-migrated when the connection is established or deleted.
  • the value of the migration status bit is set according to the migration operation status, where the value is in the SPC migration process to the PC. For: Start SPC migration PC, or SPC migration to PC success;
  • the signaling scenario type is connection establishment or connection deletion, and when the converted migration status bit is non-migrated, the label and cross-connection are deleted.
  • the application of the present invention is smooth and compatible with common connection establishment and deletion signaling, and does not change any signaling flow.
  • standard RSVP-TE or CR-LDP signaling it is carried according to the self-destination node.
  • the signaling scenario value of the downstream node distinguishes whether the deletion is established, or whether the SPC is migrated to the PC, and the PC is migrated to the SPC.
  • the strict state control determines whether the resource is migrated or released, ensuring that the deletion signaling is received. After that, the resources will not be deleted by mistake, and the PC will be migrated to PC or PC.
  • FIG. 1 is a flowchart of a state transition based migration method in an automatic switched optical network according to the present invention
  • FIG. 2 is a RSVP-TE signaling diagram when an SPC is migrated to a PC in a specific example of the present invention
  • FIG. 3 is a specific example of the present invention.
  • An abnormal RSVP-TE signaling diagram that times out when the SPC is migrated to the PC;
  • FIG. 4 is a RSVP-TE signaling diagram of an intermediate node failure when a PC migrates to an SPC in a specific example of the present invention
  • FIG. 5 is a RSVP-TE signaling diagram of a downstream PathErr received when a PC migrates to SPC according to a specific example of the present invention.
  • Figure 3 4 ⁇ 4 ''''''
  • Figure 7 is a flow chart showing the process of receiving signaling in a specific example of the present invention. Preferred embodiment of the invention
  • CR-LDP may also be selected (which is described in detail in RFC3212 and RFC3472).
  • RSVP-TE signaling such as Path (R&D), PathErr, and Pathtear; it corresponds to CR-LDP Notification, Label Withdraw, and Label Release signaling. Therefore, the method of the present invention supports RSVP-TE signaling or CR-LDP signaling.
  • the main idea of the present invention is to carry out the signaling scenario in the standard signaling, in order to improve the robustness of the mutual migration between the PC and the SPC.
  • the information of the signaling scenario includes the type of the signaling scenario, and the type of the signaling scenario includes connection deletion, connection establishment, PC to SPC migration, and SPC migration to the PC), and is set in the connection information to identify the operation state related to the migration.
  • the migration status bit field performs state transition of the signaling scenario according to the information of the signaling scenario and the value of the migration status bit in the standard signaling, and completes the mutual migration between the PC and the SPC.
  • the first node When the SPC is migrated to a PC, if the signaling process of graceful deletion in RSVP is used, the first node sends Path (R&D) signaling to the tail node, and the tail node sends PathErr to the upstream node (Path_state_remove, path). State deletion) Signaling, Pathtear signaling will occur in abnormal conditions; while PC is migrated to SPC, the first node sends Path signaling to the tail node, and the tail node sends Resv signaling to the first node. When it fails, Pathtear signaling will occur. And PathErr signaling.
  • R&D Path
  • PathErr the upstream node
  • the state transition based migration method in the automatic switched optical network of the present invention includes the following steps:
  • Step 100 The node receives the standard signaling of the upstream node or the downstream node, where the standard signaling carries the information of the signaling scenario.
  • the standard signaling of the node receiving the upstream node or the downstream node specifically means that the node receives the abnormal signaling from the upstream node, or the node receives the abnormal signaling from the downstream node.
  • Step 200 The node acquires information about a corresponding signaling scenario from standard signaling.
  • the information of the signaling scenario includes a type of a current signaling scenario.
  • the types of signaling scenarios include connection deletion, connection establishment, PC migration to SPC, and migration from SPC to PC.
  • Step 300 The node combines the information of the signaling scenario and the value of the current migration status bit to perform state transition on the signaling scenario, determine the value of the converted migration status bit, and complete mutual migration between the PC and the SPC, where the migration status bit Used to identify the operational status of the migration.
  • the node performs state transition on the signaling scenario according to the value of the migration status bit and the information of the signaling scenario, determines the value of the converted migration status bit, determines whether to implement the rollback according to the value of the converted migration status bit, and distinguishes Resource release or permission migration.
  • the label and cross-connection are deleted; if the value of the migration status bit after the conversion starts the SPC migration, the label and cross-connection are migrated, where if the conversion
  • the value of the post-migration status bit is the value of the SPC migration PC and the value of the migration status bit before the conversion is successful. Only the label migration is performed.
  • the value of the migration status bit is as follows:
  • the value of this field is: Non-migration status;
  • SPC to PC migration the value of this field is: Start SPC migration PC, or SPC migration to PC success;
  • the present invention is capable of migrating between a PC and an SPC of an automatic switching optical network.
  • the signaling flow for implementing SPC migration to a PC is not unique due to network failures, etc.
  • the following is an example of RSVP-TE (and CR-LDP can also be used).
  • the main signaling scenarios in which the SPC is migrated to the PC will be listed.
  • the present invention will be further described in conjunction with the drawings and specific examples. As described in the technical solution, the present invention sets a migration status bit field in the connection information, and the value is described as follows:
  • the value of this field is: 1) Non-migration status;
  • SPC migration to PC the value of this field is: 1) Start SPC migration PC; 2) SPC migration to PC success;
  • Example 1 The normal signaling flow of SPC migration to PC. As shown in Figure 2, the normal signaling flow of the SPC migration to the PC is consistent with the signaling flow of the graceful deletion of the connection described in RFC3473.
  • the first node A sends Path (R&D) signaling to the intermediate node B, and the intermediate node B sends Path (R&D) signaling to the tail node C.
  • the tail node C sends PathErr signaling to the intermediate node B, and the intermediate node B sends the path to the head node.
  • A sends PathErr signaling.
  • the node for example, the intermediate node B or the tail node C
  • the corresponding signaling scenario is taken out from the private data of the Path (R&D) signaling, and the signaling scenario should be
  • the SPC is migrated to the PC; the value of the migration status bit is determined, and the corresponding conversion is performed in combination with the signaling scenario.
  • the value of the migration status bit is PC migration.
  • the SPC operation is successful. At this time, the SPC is successfully migrated from the PC, and it is converted to start SPC migration to the PC.
  • ⁇ 2> The value of the migration status bit is non-migrated. At this time, the SPC is normally established, and it is converted to start SPC migration to the PC.
  • the migration status bit takes the value other, which is the error status.
  • the corresponding signaling scenario is taken out from the private data of the PathErr signaling according to the interface provided by the protocol stack.
  • the signaling scenario should be the SPC migration to the PC.
  • the value of the bit is combined with the signaling scenario to perform the corresponding conversion.
  • the value of the migration status bit is to start the SPC migration of the PC. At this time, the node has received the Path (R&D) signaling in the migration scenario. The value of the migration status bit is not changed, and the label and cross-connection are migrated to the management. Plane, delete database information and local connection information.
  • R&D Path
  • the value of the migration status bit is other, which is the error status.
  • the migration status bit value at the node is modified to start the SPC migration to the PC.
  • Example 2 SPC migration to PC abnormal signaling process.
  • the abnormal signaling flow of the SPC migration to the PC is consistent with the signaling flow of the forced deletion of the connection described in RFC3473.
  • Figure 3 shows that the first node does not receive the PathErr of the downstream node after the Path (R&D) is issued. The timeout may be because the downstream signaling control channel is invalid or the downstream node is faulty.
  • the Pathtear is sent to the downstream node to implement SPC forced migration.
  • the intermediate node is taken as an example to describe the implementation of SPC migration to PC under this signaling flow. The operation steps are as follows:
  • Step 201 The node receives the Pathtear signaling from the upstream node, and extracts the corresponding signaling scenario from the private data of the Pathtear signaling according to the interface provided by the protocol stack.
  • the signaling scenario should be the SPC migration to the PC.
  • Step 202 Determine the value of the migration status bit, and perform corresponding conversion according to the signaling scenario. At this point, the different values are converted as follows:
  • the value of the migration status bit is successful.
  • the SPC is successfully migrated from the PC.
  • the SPC is successfully migrated from the PC.
  • the path is not received by the path (R&D) signaling. Signaling, converts the migration state to start SPC migration to the PC, implements migration tags and cross-connects to the management plane, and deletes database connection information and local connection information.
  • ⁇ 2> The value of the migration status bit is non-migrated. In this case, the SPC is established normally. If the Path (R&D) signaling is not received, the Pathtear signaling is directly received and converted to start SPC migration. , Implement migration labels and cross-connects to the management plane, and delete database connection information and local connection information.
  • the migration status bit takes the value other, which is the error status.
  • Example 3 When the PC migrates to SPC, it receives the PathErr signaling of the downstream node.
  • the specific signaling procedure is that the first node sends Path signaling to the tail node, and the tail node sends Resv signaling to the first node.
  • the migration status bit is changed to start the PC migration SPC, and the node starts to apply for label migration to the control plane.
  • the migration status bit is converted to PC migration SPC.
  • the tag is successful; the node receives the Resv of the downstream node During signaling, the node starts to apply for cross-connection migration to the control plane.
  • the migration status bit is converted to PC migration SPC operation succeeded.
  • the intermediate node B when the PC is migrated to SPC, the intermediate node B fails to transmit the cross-connection after receiving the Resv signaling from the downstream node C. After the failure, the intermediate node B fails the response protocol stack, thereby moving to the downstream node. C sends Pathtear signaling and sends PathErr signaling to the upstream node A.
  • the intermediate node B receives the PathErr signaling sent by the tail node C due to the migration of the tail node C.
  • the intermediate node is taken as an example to describe the implementation of the SPC migration to the PC in the signaling flow of FIG. 4 and FIG. 5, and the operation steps are as follows:
  • Step 301 The node receives the PathErr signaling advertised by the protocol stack (for Figure 4, the intermediate node is
  • the signaling point of PathErr signaling for Figure 5, the intermediate node is the receiver of PathErr signaling, but the processing is the same), and the corresponding signaling scenario is taken out from the private data of PathErr signaling.
  • the signaling scenario should be PC migration. For SPC;
  • Step 302 Determine the value of the migration status bit, and perform corresponding conversion according to the signaling scenario. At this point, the different values are converted as follows:
  • the migration status bit value is the PC migration to SPC failure.
  • the label is successfully migrated to the control plane when the Path signaling is received.
  • the path to the upstream node is sent to the upstream node because the cross-connection fails.
  • the cross-migration fails.
  • the migration status bit fails for the PC to migrate to SPC.
  • this point converts the migration state to start SPC migration to the PC, implements the migration label to the management plane (previously, the cross-connection fails, so there is no cross-rollback here), and the database connection information and local connection information are deleted. .
  • the value of the migration status bit is successful.
  • the SIP label is successfully migrated.
  • the device successfully migrates the label to the control plane when receiving the Path signaling. It directly receives the PathErr signaling from the downstream node and converts the migration status to the start SPC. Migrate to the PC, implement the migration label to the management plane (the cross-connection has not been migrated at this time, so there is no cross-rollback here), delete the database connection information and local connection information.
  • the migration status bit takes a value of other status, which is an error status.
  • Example 4 The PC migrates to the SPC timeout, and the first node sends Pathtear signaling to the downstream node.
  • the head node starts a timer for the PC to be migrated to the SPC. If the Resv signaling is not received within the timer time, the first node sends Pathtear signaling to the downstream node to implement SPC migration to PC rollback.
  • the intermediate node is taken as an example to describe the implementation of the PC migration to SPC in the signaling flow of Figure 6. The operation steps are as follows:
  • Step 401 Receive the Pathtear signaling of the upstream node, and take out the corresponding signaling scenario from the private data of the Pathtear signaling.
  • the signaling scenario should be the PC migration to the SPC.
  • Step 402 Determine the value of the migration status bit, and perform corresponding conversion according to the signaling scenario. Referring to Figure 7, the different values are converted as follows:
  • the value of the migration status bit is set to PC.
  • the SPC label is successfully transmitted.
  • the label is successfully migrated to the management plane when the Path signaling is received.
  • the Pathtear signaling of the upstream node is received.
  • the migration status is converted to start SPC migration to the PC, and the migration label is implemented to the management plane (the cross-connection is not migrated at this time, so there is no cross-rollback here), and the database connection information and local connection information are deleted.
  • the value of the migration status bit is set to be successful.
  • the migration of the node to the SPC is successful.
  • the first node timer expires due to the upstream signaling channel failure.
  • the migration status is changed to start the SPC migration to the PC.
  • the migration status bit takes a value of other status, which is an error status.
  • Example 5 Handling of migration status bits when Path (R&D), PathErr, and Pathtear signaling are received during connection establishment deletion.
  • the value of the migration status bit is PC migration.
  • the SPC operation is successful.
  • the SPC is obtained by the PC migration, and the value of the migration status bit is converted to the non-migration state.
  • the value of the migration status bit is non-migrated.
  • the SPC is established by the normal connection and does not change the migration status. That is, the value of the migration status bit is non-migrated.
  • the migration status bit takes a value of other status, which is an error status.
  • the migration status bit is in the non-migration state. In this case, the normal process of the SPC deletion is not changed. Implement the removal of tags and cross-connects, and delete database connection information and local connection information.
  • the migration status bit takes values as other statuses. This is the error status.
  • the value of the migration status bit is PC migration.
  • the SPC operation is successful.
  • the SPC is obtained by PC migration.
  • R&D Path
  • ⁇ 2> The value of the migration status bit is non-migrated.
  • the SPC is established by the normal connection.
  • the Path (R&D) signaling is not received before, and the Pathtear signaling is directly received.
  • the migration status bit takes a value of other status, which is an error status.
  • the intermediate node is taken as an example, and when the remaining nodes receive the same signaling as the intermediate node, the processing is similar.
  • the node acts as the sender of the signaling, and the processing flow of the signaling received by the receiver of the signaling is consistent. Because the node handles the signaling, it processes the signaling advertised by the protocol stack. Regardless of whether the node is the receiver of the signaling or the sender, it is the protocol stack. The advertised signaling is processed and sent to other nodes after processing.
  • the tail node as the sender of the PathErr signaling, receives the advertised PathErr signaling from the protocol stack before issuing the PathErr signaling.
  • the intermediate node acts as the receiver of the PathErr signaling and also receives the advertised PathErr letter from the protocol stack. Therefore, the two methods are consistent with the processing method of the PathErr signaling, and the corresponding migration state transition is performed according to the information of the migration status bit and the signaling scenario.
  • the migration state is converted to the start SPC migration to the PC, and the migration label is implemented to the management plane.
  • the method of the invention controls the process and the specific operation through strict state control (first checking the previous state when assigning the migration state), and performs corresponding actions under the flow, thereby eliminating the pair of signaling confusion and process inconsistency. Label and cross-connect operations are incorrect.
  • the invention is smooth and compatible with the signaling process of the common connection establishment and deletion, and does not make any change to the existing signaling flow.
  • the standard RSVP-TE or CR-LDP signaling according to the signaling scenario information carried by the self-destination node to the downstream.
  • the distinction is whether the connection is established and deleted, or the SPC is migrated to the PC, and the PC is migrated to the SPC.
  • the strict state control is used to determine whether the resource is migrated or released, ensuring that the deletion signaling (ie, the abnormal signaling PathErr, After Pathtear, etc., the resources will not be deleted by mistake, and the PC will be migrated to PC or PC.

Landscapes

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

Description

一种自动交换光网络中连接迁移方法和系统
技术领域
本发明涉及光通信网络中业务迁移技术领域， 尤其涉及一种自动交换光 网络 ( ASON: Automatically Switched Optical Network ) 中 PC (永久连接， Permanent Connection)与 SPC (軟永久连接, Soft Permanent Connection)之间相 互迁移的方法和系统。
背景技术
随着网络技术的发展， 网络通信容量的大幅增长， 人们对传送网的性能 提出了更高的要求： 通过在光域增加自动控制的协议手段赋予光网络智能属 性， 希望网络的构架更加灵活， 网络的管理灵活统一， 带宽利用率更高， 生 存性和扩展性更好， 能够提供动态的连接和智能的调度方式。 于是， 自动交 换光网络应运而生。
在 ASON中， 根据不同的连接需要以及业务的请求对象不同， 提供了三 种连接： 永久连接 ( PC, Permanent Connection ) 、 软永久连接 ( SPC, Soft Permanent Connection )和交换连接 (Switched Connection)。
在实际网络运维中， 运营商需要在网络内根据需要作 PC与 SPC业务之 间的迁移。 PC迁移为 SPC, 需要在 PC中引入控制平面的信令状态， 将标签 (此处的标签指 RFC3946所述的 SDH通用标签）和交叉管理权限迁移至控 制平面。 SPC迁移为 PC, 要删除 SPC的信令状态， 将标签与交叉管理权限 迁移至管理平面。 通常原则为， 网元在实施 PC迁移为 SPC发生异常时， 及 实施 SPC迁移 PC时， 最终结果都需要保证为 PC (即标签与交叉连接的管理 权限在管理平面）， 即仅仅是将标签与交叉权限迁移至管理平面， 而不允许删 除标签与交叉连接。
当前光网络中永久连接和交换连接之间的转换， 通过逐跳实施进行 PC 与 SPC的相互迁移， 主要是自入口节点利用信令向其他节点逐跳通告进行迁 移， 信令可釆用 CR-LDP (基于路由受限标签分发协议)或者 RSVP-TE (基于流 量工程扩展的资源预留协议)。 由于 PC与 SPC之间的迁移涉及到 LSP ( Label Switched Path, 标签交换路径)信令的增加与删除， 因此， 当前的逐跳通告流 程为公用的标准协议流程。 釆用 CR-LDP 的信令逐跳通告流程可参见 RFC3212, RFC3472。 釆用 RSVP-TE的信令逐跳通告流程可参见 RFC3209, RFC3473。 现有技术中只考虑了正常的迁移流程 (PC迁移为 SPC, SPC迁移 为 PC) , 未考虑异常情况下迁移的处理。 此外， 无论釆用 CR-LDP还是 RSVP-TE, 由于迁移的信令与连接建立删除的信令相同， 而当前方法中并未 考虑釆用普通的建立删除信令 (RSVP-TE或 CR-LDP)时的兼容操作， 即如何 确保在相同信令流程下对标签与交叉连接进行删除还是迁移。 RFC3209 与 RFC3473中描述了支持 GMPLS (通用多协议标志交换协议)的 RSVP-TE信令 扩展。 参照 RFC3473 , 无论是在连接建立、 删除还是 PC与 SPC间的迁移， 可能出现 Patherr. Pathtear. ResvErr和 ResvTear信令 ( ResvErr和 ResvTear 信令不常用）。 在业务建立删除时接收到以上信令需要释放标签与交叉连接， 而在迁移时只需要将标签与交叉连接的管理权限迁移至管理平面。 因此， 如 果在处理信令时出错， 或者在处理信令时出现混乱， 将导致标签与交叉连接 被释放， 以至于业务中断， 无法确保其健壮性。
综上所述， 当前需要一种新的技术方案解决 PC与 SPC之间相互迁移的 健壮性的问题。
发明内容
本发明所要解决的技术问题是提供一种自动交换光网络中连接迁移方法 和系统， 平滑兼容连接建立删除的信令， 确保区分是资源的释放还是权限迁 移， 对于 PC迁移 SPC失败或者 SPC迁移 PC时， 确保了在接收到相应的信 令时不会误删资源， 而只作权限改变， 确保异常后最终一定为 PC。
为了解决上述问题， 本发明提供了一种自动交换光网络连接迁移方法， 节点与相关节点交互标准信令进行连接迁移， 其中： 在连接信息中设置用于 标识迁移操作状态的迁移状态位字段，所述标准信令中携带信令场景的信息， 所述节点根据所述标准信令中携带的信令场景的信息和当前迁移状态位的 值， 进行信令场景状态转换， 完成永久连接 PC与软永久连接 SPC之间的相 互迁移。
进一步地， 上述方法还可具有以下特点，
所述节点在信令场景状态转换后， 重新设置迁移状态位的值。
进一步地， 上述方法还可具有以下特点，
所述信令场景的信息中包括当前信令场景的类型；
所述信令场景的类型为连接删除、 连接建立、 PC向 SPC迁移或 SPC向 PC迁移。
进一步地， 上述方法还可具有以下特点，
所述迁移状态位的值， 是指：
对于普通的连接删除或连接建立， 该字段取值为： 非迁移状态； 对于 SPC向 PC迁移， 该字段取值为： 开始 SPC迁移 PC或 SPC迁移为 PC成功；
对于 PC向 SPC迁移， 该字段取值为： 开始 PC迁移 SPC、 PC迁移 SPC 标签成功、 PC迁移 SPC操作成功或 PC迁移为 SPC失败。
进一步地， 上述方法还可具有以下特点，
信令场景的类型为 SPC向 PC迁移时， 当节点从上游节点接收到标准信 令或者向下游节点发出标准信令， 且该标准信令为异常信令， 且迁移状态位 取值为 PC迁移 SPC操作成功或非迁移状态时， 将迁移状态位的值转换为开 始 SPC迁移 PC; 当节点从下游节点接收到标准信令或者向上游节点发出标 准信令， 且该标准信令为异常信令， 且迁移状态位取值为开始 SPC迁移 PC 时， 保持迁移状态位的值为开始 SPC迁移 PC。
进一步地， 上述方法还可具有以下特点，
信令场景的类型为 PC向 SPC迁移时， 当节点从下游节点接收到标准信 令或者向上游节点发出标准信令， 且该标准信令为异常信令， 且迁移状态位 的值为 PC迁移 SPC标签成功或者为 PC迁移为 SPC失败时， 将迁移状态位 的值转换为开始 SPC迁移 PC; 当节点从上游节点接收到标准信令或者向下 游节点发出标准信令， 且该标准信令为异常信令， 且迁移状态位的值为 PC 迁移 SPC标签成功或 PC迁移 SPC操作成功时， 将迁移状态位的值转换为开 始 SPC迁移 PC。
进一步地， 上述方法还可具有以下特点，
当节点接收到标准信令， 且该标准信令为异常信令且转换后迁移状态位 的值为开始 SPC迁移 PC时， 迁移标签和交叉连接至管理平面。
本发明还提供一种自动交换光网络连接迁移系统， 包括由首节点和相关 节点组成的若干个节点， 其中，
所述节点， 用于和相关节点交换标准信令， 所述标准信令中携带信令场 景的信息， 根据连接信息中设置的用于标识迁移操作状态的迁移状态位字段 的值和标准信令中携带的信令场景的信息， 进行信令场景状态转换， 完成永 久连接 PC与软永久连接 SPC之间的相互迁移。
进一步地， 上述系统还可具有以下特点，
所述节点， 还用于在信令场景状态转换后， 重新设置迁移状态位的值。 进一步地， 上述系统还可具有以下特点，
所述节点， 还用于在信令场景的信息中包括当前信令场景的类型； 所述 信令场景的类型为连接删除、 连接建立、 PC向 SPC迁移或 SPC向 PC迁移。
进一步地， 上述系统还可具有以下特点，
所述节点， 还用于设置所述迁移状态位的值，
对于普通的连接删除或连接建立， 该字段取值为： 非迁移状态； 对于 SPC向 PC迁移， 该字段取值为： 开始 SPC迁移 PC或 SPC迁移为 PC成功；
对于 PC向 SPC迁移， 该字段取值为： 开始 PC迁移 SPC、 PC迁移 SPC 标签成功、 PC迁移 SPC操作成功或 PC迁移为 SPC失败。
进一步地， 上述系统还可具有以下特点，
所述节点， 还用于当节点从上游节点接收标准信令或者向下游节点发出 标准信令， 当信令场景的类型为 SPC向 PC迁移， 且该标准信令为异常信令， 且迁移状态位取值为 PC迁移 SPC操作成功或非迁移状态时， 将迁移状态位 的值转换为开始 SPC迁移 PC; 还用于从下游节点接收标准信令或者向上游 节点发出标准信令， 当信令场景的类型为 SPC向 PC迁移， 且该标准信令为 异常信令， 且迁移状态位取值为开始 SPC迁移 PC时， 保持迁移状态位的值 为开始 SPC迁移 PC。
进一步地， 上述系统还可具有以下特点，
所述节点， 还用于从下游节点接收标准信令或者向上游节点发出标准信 令， 当信令场景的类型为 PC向 SPC迁移时， 且该标准信令为异常信令， 且 迁移状态位的值为 PC迁移 SPC标签成功或者为 PC迁移为 SPC失败时， 将 迁移状态位的值转换为开始 SPC迁移 PC; 还用于从上游节点接收标准信令 或者向下游节点发出标准信令， 当信令场景的类型为 PC向 SPC迁移时， 且 该标准信令为异常信令， 且迁移状态位的值为 PC迁移 SPC标签成功或 PC 迁移 SPC操作成功时， 将迁移状态位的值转换为开始 SPC迁移 PC。
进一步地， 上述系统还可具有以下特点，
所述节点， 还用于接收标准信令， 判断标准信令为异常信令且转换后迁 移状态位的值为开始 SPC迁移 PC时， 迁移标签和交叉连接至管理平面。
本发明还提供一种自动交换光网络连接处理方法， 在连接信息中设置用 于标识迁移操作状态的迁移状态位字段， 标准信令中携带信令场景的信息， 节点根据所述标准信令中携带的信令场景的信息和当前迁移状态位的值， 进 行信令场景状态转换， 完成连接的建立、 删除和迁移。
其中， 在连接建立、 删除时设置连接迁移状态位的值为非迁移状态； 在连接迁移时， 根据迁移操作状态设置迁移状态位的值， 其中， 在 SPC向 PC迁移过程中， 该字段取值为： 开始 SPC迁移 PC, 或 SPC 迁移为 PC成功；
在 PC向 SPC迁移过程中， 该字段取值为： 开始 PC迁移 SPC、 PC迁移
SPC标签成功、 PC迁移 SPC操作成功或者 PC迁移为 SPC失败。
节点接收到异常信令时， 信令场景类型为连接建立或连接删除， 且转换 后的迁移状态位为非迁移状态时， 进行标签和交叉连接的删除。 与现有技术相比， 应用本发明， 平滑兼容普通的连接建立删除的信令， 未对其信令流程作任何改变，对于标准 RSVP-TE或 CR-LDP的信令，根据自 首节点携带至下游节点的信令场景值来区分是建立删除， 还是 SPC 迁移为 PC, 及 PC迁移为 SPC; 通过严格的状态控制来判定是对资源实施权限迁移， 还是释放， 确保了在收到删除信令后不会误删资源， 进一步保证 SPC迁移为 PC或者 PC迁移为 SPC失败后一定是 PC。 附图概述
图 1 是本发明的自动交换光网络中基于状态转换的迁移方法的流程图； 图 2 是本发明具体实例中 SPC迁移为 PC时的 RSVP-TE信令图； 图 3 是本发明具体实例中 SPC迁移为 PC时超时的异常的 RSVP-TE信 令图；
图 4 是本发明具体实例中 PC迁移为 SPC时中间节点失败的 RSVP-TE 信令图；
图 5 是本发明具体实例中 PC 迁移为 SPC 时接收到下游 PathErr 的 RSVP-TE信令图； 图； ¾ ' ' ' ' ' '
图 7是本发明具体实例中接收到信令的处理流程图。 本发明的较佳实施方式
下面结合附图和具体实施方式对本发明作进一步说明。
对于本发明迁移的信令实现， 除上文描述的 RSVP-TE 外， 也可选择 CR-LDP (其中 RFC3212与 RFC3472中对此作了详尽描述） 。 在 RSVP-TE 信令中，如 Path(R&D)、 PathErr和 Pathtear;其与 CR-LDP的 Notification, Label Withdraw和 Label Release信令相对应。 因此， 本发明的方法支持 RSVP-TE 信令或 CR-LDP信令。 由于迁移与普通的连接建立删除的信令流程相同， 因此为了提高 PC 与 SPC之间相互迁移的健壮性， 本发明的主要构思是： 为了区分信令， 在标准 信令中携带信令场景的信息 （信令场景的信息中包括信令场景的类型， 信令 场景类型包括连接删除、 连接建立、 PC向 SPC迁移和 SPC向 PC迁移）， 并 在连接信息中设置用于标识迁移相关操作状态的迁移状态位字段， 根据标准 信令中信令场景的信息和迁移状态位的值， 进行信令场景状态转换， 完成 PC 与 SPC之间的相互迁移。
在 SPC迁移为 PC时， 如釆用的是 RSVP中优雅删除的信令流程， 则首 节点发送 Path(R&D)信令至尾节点 ， 尾节点向上游节点回送 PathErr(Path— state— remove, 路径状态删除)信令， 异常情况将出现 Pathtear信 令； 而 PC迁移为 SPC则是首节点发送 Path信令至尾节点， 尾节点回送 Resv 信令至首节点， 在失败时将会出现 Pathtear信令和 PathErr信令。
对于节点在接收到异常信令 (如 RSVP的 PathErr、 Pathtear或 CR-LDP的 Label Withdraw, Label Release)时， 需要考虑 PC与 SPC之间相互迁移的健壮 性： 对于已申请的资源， 需要释放， 对于已迁移到控制平面的资源， 需要回 滚其管理权限， 而不允许发生释放。 对于以上情况， 本发明的自动交换光网 络中基于状态转换的迁移方法， 如图 1所示， 包括以下步骤：
步骤 100、 节点接收上游节点或下游节点的标准信令， 其中该标准信令 中携带信令场景的信息；
节点接收上游节点或下游节点的标准信令具体是指， 节点接收来自上游 节点的异常信令， 或者节点接收来自下游节点的异常信令。
步骤 200、 节点从标准信令中获取相应的信令场景的信息；
其中， 所述信令场景的信息中包括当前信令场景的类型。
信令场景的类型包括， 连接删除、 连接建立、 PC向 SPC迁移、 SPC向 PC迁移。
步骤 300、 节点结合信令场景的信息和当前迁移状态位的值， 对信令场 景进行状态转换， 判断转换后的迁移状态位的值， 完成 PC与 SPC之间的相 互迁移， 其中迁移状态位用于标识迁移相关操作状态。 节点根据迁移状态位的值和信令场景的信息，对信令场景进行状态转换， 判断转换后的迁移状态位的值， 根据转换后的迁移状态位的值决定是否实施 回滚， 并且区分是资源释放还是权限迁移。
如果转换后迁移状态位的值为非迁移状态， 则进行标签和交叉连接的删 除操作； 如果转换后迁移状态位的值为开始 SPC迁移 PC, 则进行标签和交 叉连接的迁移， 其中， 如果转换后迁移状态位的值为开始 SPC迁移 PC而转 换前迁移状态位的值为 PC迁移 SPC标签成功， 则只进行标签迁移。
所述迁移状态位的值， 具体如下：
对于普通的连接删除或连接建立， 该字段取值为： 非迁移状态； 对于 SPC向 PC迁移， 该字段取值为： 开始 SPC迁移 PC, 或 SPC迁移 为 PC成功；
对于 PC向 SPC迁移， 该字段取值为： 开始 PC迁移 SPC、 PC迁移 SPC 标签成功、 PC迁移 SPC操作成功或者 PC迁移为 SPC失败。
本发明^^于自动交换光网络的 PC与 SPC迁移，由于网络故障等原因， 实施 SPC迁移为 PC的信令流程并不唯一， 以下以 RSVP-TE为例（亦可釆用 CR-LDP), 将列出 SPC迁移为 PC的主要信令场景， 对不同场景结合附图和 具体实例对本发明作进一步的描述。 如技术方案所述， 本发明在连接信息中设置了一个迁移状态位字段， 取 值描述如下：
对于普通的连接删除或连接建立， 该字段取值为： 1)非迁移状态； 对于 SPC迁移为 PC, 该字段取值为： 1)开始 SPC迁移 PC; 2)SPC迁移 为 PC成功；
对于 PC迁移为 SPC, 该字段取值为： 1)开始 PC迁移 SPC; 2) PC迁移 SPC标签成功； 3) PC迁移 SPC操作成功； 4) PC迁移为 SPC失败。
实例 1: SPC迁移为 PC的正常信令流程。 如图 2所示， SPC迁移为 PC的正常信令流程与 RFC3473中描述的连接 优雅删除的信令流程一致。 其中， 首节点 A向中间节点 B发送 Path(R&D)信 令， 中间节点 B向尾节点 C发送 Path(R&D)信令； 尾节点 C向中间节点 B发 送 PathErr信令， 中间节点 B向首节点 A发送 PathErr信令。
结合图 7 , 描述在此信令流程下处理， 操作步骤如下：
如果节点（例如中间节点 B或尾节点 C )接收到来自上游节点的 Path(R&D) 信令， 则从 Path ( R&D )信令的私有数据中取出对应的信令场景， 此时信令 场景应为 SPC迁移为 PC; 判断其迁移状态位取值， 结合信令场景， 作相应 的转换。
此时， 不同取值处理如下：
<1>迁移状态位取值为 PC迁移 SPC操作成功，此时该 SPC是由 PC成功 迁移而成的， 将其转换为开始 SPC向 PC迁移。
<2>迁移状态位取值为非迁移状态， 此时该 SPC是普通建立而成的， 将 其转换为开始 SPC向 PC迁移。
<3>迁移状态位取值为其他， 此时是错误状态。
如果节点接收到来自下游节点的 PathErr信令， 根据协议栈提供的接口， 从 PathErr信令的私有数据中取出对应的信令场景， 此时信令场景应为 SPC 迁移为 PC; 判断其迁移状态位的取值， 结合信令场景， 作相应的转换。
此时， 不同取值处理如下：
<1>迁移状态位取值为开始 SPC迁移 PC, 此时该节点之前已收到过迁移 场景下的 Path(R&D)信令， 不改变迁移状态位的值， 将标签和交叉连接迁移 至管理平面， 删除数据库信息和本地连接信息。
<2>迁移状态位取值为其他， 此时是错误状态。
另外， 首节点发起 SPC迁移至 PC时， 修改该节点处的迁移状态位值为 开始 SPC向 PC迁移。 实例 2: SPC迁移为 PC的异常信令流程。
如图 3所示， SPC迁移为 PC的异常信令流程与 RFC3473中描述的连接 强制删除的信令流程一致。 图 3 中表示首节点在发出 Path(R&D)后， 超时未 收到下游节点的 PathErr (超时原因可能是因为下游信令控制通道失效， 或者 下游节点故障）， 向下游节点发送 Pathtear实施 SPC强制迁移为 PC。 结合图 7, 以中间节点为例描述在此信令流程下 SPC迁移为 PC的实现， 操作步骤如 下：
步骤 201 : 节点接收到来自上游节点的 Pathtear信令， 根据协议栈提供的 接口， 从 Pathtear信令的私有数据中取出对应的信令场景， 此时信令场景应 为 SPC迁移为 PC;
步骤 202: 判断其迁移状态位取值， 结合所述信令场景， 作相应的转换。 此时， 不同取值转换如下：
<1>迁移状态位取值为 PC迁移 SPC操作成功，此时该 SPC是由 PC成功 迁移而成的， 并且之前由于信令通道故障未接收到 Path(R&D)信令导致超时 直接收到 Pathtear信令， 将迁移状态转换为开始 SPC迁移 PC, 实施迁移标签 和交叉连接至管理平面， 删除数据库连接信息和本地连接信息。
<2>迁移状态位取值为非迁移状态， 此时该 SPC是普通建立而成的， 未 收到过 Path(R&D)信令而直接收到 Pathtear信令， 将其转换为开始 SPC迁移 PC, 实施迁移标签和交叉连接至管理平面， 删除数据库连接信息和本地连接 信息。
<3>迁移状态位取值为其他， 此时是错误状态。
实例 3: PC迁移为 SPC时收到下游节点的 PathErr信令。
首先简要说明一下 PC迁移为 SPC的正常信令流程。具体的信令流程为， 首节点发送 Path信令至尾节点， 尾节点回送 Resv信令至首节点。
其中， 节点接收到来自上游节点的 Path信令时， 迁移状态位转换为开始 PC迁移 SPC, 节点开始申请标签迁移至控制平面， 当标签成功迁移至控制平 面时，迁移状态位转换为 PC迁移 SPC标签成功；节点接收到下游节点的 Resv 信令时， 节点开始申请交叉连接迁移至控制平面， 当标签和交叉连接均成功 迁移至控制平面时， 迁移状态位转换为 PC迁移 SPC操作成功。
如图 4所示， PC迁移为 SPC时， 中间节点 B在收到下游节点 C的 Resv 信令后，在迁移交叉连接的时候失败， 失败后中间节点 B将应答协议栈失败， 从而向下游节点 C发送 Pathtear信令， 向上游节点 A发送 PathErr信令。
如图 5所示， PC迁移为 SPC时， 中间节点 B在发出 Path信令后， 由于 尾节点 C迁移出错， 中间节点 B接收到尾节点 C回送的 PathErr信令。
结合图 7, 以中间节点为例， 描述在图 4、 图 5信令流程下 SPC迁移为 PC的实现， 操作步骤如下：
步骤 301 : 节点接收到协议栈通告的 PathErr信令 (对于图 4, 中间节点是
PathErr信令的发出点， 对于图 5, 中间节点是 PathErr信令的接收者， 但处理 相同）， 从 PathErr信令的私有数据中取出对应的信令场景， 此时信令场景应 为 PC迁移为 SPC;
步骤 302: 判断其迁移状态位取值， 结合信令场景， 作相应的转换。 此时， 不同取值转换如下：
<1> 迁移状态位取值为 PC迁移为 SPC失败。 此场景是在收到 Path信令 时已成功迁移标签至控制平面， 由于本节点迁移交叉连接失败， 导致向上游 节点发送 PathErr信令， 由于交叉迁移失败， 在接收到交叉迁移失败应答后将 置迁移状态位为 PC迁移为 SPC失败。此时本点在处理 PathErr信令时将迁移 状态转换为开始 SPC迁移 PC, 实施迁移标签至管理平面 （之前迁移交叉连 接失败， 因此在此不作交叉回滚） ， 删除数据库连接信息和本地连接信息。
<2>迁移状态位取值为 PC迁移 SPC标签成功， 此时是在收到 Path信令 时已成功迁移标签至控制平面， 直接收到下游节点的 PathErr信令， 将迁移状 态转换为开始 SPC向 PC迁移， 实施迁移标签至管理平面 （此时尚未迁移交 叉连接， 因此在此不作交叉回滚） ， 删除数据库连接信息和本地连接信息。
<3>迁移状态位取值为其他状态， 此时是错误状态。
实例 4: PC迁移为 SPC超时， 首节点向下游节点发送 Pathtear信令。 如图 6所示， 首节点在发送 Path信令后， 会启动一个 PC迁移为 SPC的 定时器。 在定时器定时时间内如果未收到 Resv信令， 首节点会向下游节点发 送 Pathtear信令实施 SPC迁移为 PC的回滚。 结合图 7 , 以中间节点为例， 描 述在图 6信令流程下 PC迁移为 SPC的实现， 操作步骤如下：
步骤 401 : 接收到上游节点的 Pathtear信令， 从 Pathtear信令的私有数据 中取出对应的信令场景， 此时信令场景应为 PC迁移为 SPC;
步骤 402: 判断其迁移状态位取值， 结合信令场景， 作相应的转换。 参见图 7 , 不同取值转换如下：
<1>迁移状态位取值为 PC迁移 SPC标签成功， 此时是在收到 Path信令 时已成功迁移标签至管理平面， 此后超时收到上游节点的 Pathtear信令。 将 迁移状态转换为开始 SPC向 PC迁移， 实施迁移标签至管理平面 （此时尚未 迁移交叉连接， 因此在此不作交叉回滚） ， 删除数据库连接信息和本地连接 信息。
<2>迁移状态位取值为 PC迁移 SPC操作成功， 此时本节点迁移至 SPC 成功， 但由于上游信令通道故障导致首节点定时器超时， 将迁移状态转换为 开始 SPC向 PC迁移， 实施迁移标签和交叉连接至管理平面， 删除数据库连 接信息和本地连接信息。
<3>迁移状态位取值为其他状态， 此时是错误状态。
其中实例 3中尾节点收到中间节点发送的 Pathtear信令时其处理流程和 实例 4中的处理一致。
实例 5: 连接建立删除时接收到 Path(R&D)， PathErr和 Pathtear信令 时， 对迁移状态位的处理。
对于 SPC连接建立而言， 无论是正常还是异常信令流程， 均不会出现迁 移状态的转换。 在所有流程中， 迁移状态位只可能是非迁移状态。 因此， 在 此不作描述。
对于 SPC连接删除而言， 由于将删除的 SPC可能是普通建立而成， 也可 能是由 PC 迁移而成。 因此， 将涉及到迁移状态位的转换。 下文描述连接删 除信令场景下在接收到 Path(R&D), PathErr和 Pathtear信令的状态转换。 情形一： 对于 Path(R&D)信令， 判断迁移状态， 作相应的转换：
<1>迁移状态位取值为 PC迁移 SPC操作成功，此时该 SPC是由 PC迁移 而得到， 将迁移状态位的值转换为非迁移状态。
<2>迁移状态位取值为非迁移状态，此时该 SPC是由普通连接建立得到， 不作迁移状态的改变， 即保持迁移状态位的值为非迁移状态。
<3>迁移状态位取值为其他状态， 此时是错误状态。
情形二： 对于 PathErr信令， 判断迁移状态， 作相应的转换。
<1>迁移状态位取值为非迁移状态， 此时为该 SPC删除的正常流程， 不 作迁移状态的改变。 实施标签和交叉连接的删除， 删除数据库连接信息和本 地连接信息。
<2>迁移状态位取值为其他状态。 此时是错误状态。
情形三： 对于 Pathtear信令， 判断迁移状态， 作相应的转换。
<1>迁移状态位取值为 PC迁移 SPC操作成功，此时该 SPC是由 PC迁移 而得到。之前未收到 Path(R&D)信令而直接收到 Pathtear信令， 迁移状态转换 为非迁移状态， 实施标签和交叉连接的删除， 删除数据库连接信息和本地连 接信息。
<2>迁移状态位取值为非迁移状态，此时该 SPC是由普通连接建立得到， 之前未收到 Path(R&D)信令而直接收到 Pathtear信令， 不作迁移状态转换。 实 施标签和交叉连接的删除， 删除数据库连接信息和本地连接信息。
<3>迁移状态位取值为其他状态， 此时是错误状态。
上述实例中以中间节点作为示例， 其余节点收到和该中间节点相同的信 令时， 其处理类似。
另外， 需要指出的是， 节点作为信令的发出者， 和该信令的接收者收到 该信令的处理流程一致。 因为， 节点对信令的处理， 是通过对协议栈通告的 信令进行处理。 不管节点是作为信令的接收者， 还是发送者， 均是对协议栈 通告的信令进行处理， 处理完毕后， 才向其他节点发送。
例如， 尾节点作为 PathErr信令的发出者， 在发出 PathErr信令前， 从协 议栈接收到通告的 PathErr信令， 中间节点作为 PathErr信令的接收者， 也是 从协议栈接收到通告的 PathErr信令， 二者对对该 PathErr信令的处理方法一 致， 根据迁移状态位和信令场景的信息进行相应的迁移状态转换。
又例如， 实例 3中， 中间节点作为 Pathtear信令的发出者时， 和中间节 点作为 Pathtear信令的接收者时， 均是将迁移状态转换为开始 SPC向 PC迁 移， 实施迁移标签至管理平面。
本发明方法通过严格的状态控制 （对迁移状态赋值时先校验前一状态 ) 来控制流程及具体操作， 在此流程下作相应的动作， 消除了发生信令混乱和 流程不统一导致的对标签和交叉连接的操作错误。
以上所述， 仅为本发明较佳的具体实施方式， 但本发明的保护范围并不 局限于此， 任何熟悉该技术的人在本发明所公开的技术范围内， 可轻易想到 的变化或替换， 都应涵盖在本发明的保护范围之内。 因此， 本发明的保护范 围应该以权利要求的保护范围为准。
工业实用性
本发明平滑兼容普通的连接建立删除的信令流程， 未对现有信令流程作 任何改变，对于标准 RSVP-TE或 CR-LDP的信令，根据自首节点携带至下游 的信令场景信息来区分是连接建立删除， 还是 SPC迁移为 PC, 及 PC迁移为 SPC; 通过严格的状态控制来判定是对资源实施权限迁移， 还是释放， 确保 了在收到删除信令（即异常信令 PathErr, Pathtear等）后不会误删资源， 进 一步保证 SPC迁移为 PC或者 PC迁移为 SPC失败后一定是 PC。

Claims

权 利 要 求 书
1、 一种自动交换光网络连接迁移方法，节点与相关节点交互标准信令 进行连接迁移， 其中： 在连接信息中设置用于标识迁移操作状态的迁移状态 位字段， 所述标准信令中携带信令场景的信息， 所述节点根据所述标准信令 中携带的信令场景的信息和当前迁移状态位的值， 进行信令场景状态转换， 完成永久连接 PC与软永久连接 SPC之间的相互迁移。
2、 如权利要求 1所述的方法， 其中：
所述节点在信令场景状态转换后， 重新设置迁移状态位的值。
3、 如权利要求 2所述的方法， 其中：
所述信令场景的信息中包括当前信令场景的类型；
所述信令场景的类型为连接删除、 连接建立、 PC向 SPC迁移或 SPC向 PC迁移。
4、 如权利要求 3所述的方法， 其中：
所述迁移状态位的值， 是指：
对于普通的连接删除或连接建立， 该字段取值为： 非迁移状态； 对于 SPC向 PC迁移， 该字段取值为： 开始 SPC迁移 PC或 SPC迁移为 PC成功；
对于 PC向 SPC迁移， 该字段取值为： 开始 PC迁移 SPC、 PC迁移 SPC 标签成功、 PC迁移 SPC操作成功或 PC迁移为 SPC失败。
5、 如权利要求 4所述的方法， 其中：
信令场景的类型为 SPC向 PC迁移时， 当节点从上游节点接收到标准信 令或者向下游节点发出标准信令， 且该标准信令为异常信令， 且迁移状态位 取值为 PC迁移 SPC操作成功或非迁移状态时， 将迁移状态位的值转换为开 始 SPC迁移 PC; 当节点从下游节点接收到标准信令或者向上游节点发出标 准信令， 且该标准信令为异常信令， 且迁移状态位取值为开始 SPC迁移 PC 时， 保持迁移状态位的值为开始 SPC迁移 PC。
6、 如权利要求 4所述的方法， 其中：
信令场景的类型为 PC向 SPC迁移时， 当节点从下游节点接收到标准信 令或者向上游节点发出标准信令， 且该标准信令为异常信令， 且迁移状态位 的值为 PC迁移 SPC标签成功或者为 PC迁移为 SPC失败时， 将迁移状态位 的值转换为开始 SPC迁移 PC; 当节点从上游节点接收到标准信令或者向下 游节点发出标准信令， 且该标准信令为异常信令， 且迁移状态位的值为 PC 迁移 SPC标签成功或 PC迁移 SPC操作成功时， 将迁移状态位的值转换为开 始 SPC迁移 PC。
7、 如权利要求 4或 5或 6所述的方法， 其中：
当节点接收到标准信令， 且该标准信令为异常信令且转换后迁移状态位 的值为开始 SPC迁移 PC时， 迁移标签和交叉连接至管理平面。
8、 一种自动交换光网络连接迁移系统， 包括节点， 其中，
所述节点， 用于和相关节点交换标准信令， 所述标准信令中携带信令场 景的信息， 根据连接信息中设置的用于标识迁移操作状态的迁移状态位字段 的值和标准信令中携带的信令场景的信息， 进行信令场景状态转换， 完成永 久连接 PC与软永久连接 SPC之间的相互迁移。
9、 如权利要求 8所述的系统， 其中，
所述节点， 还用于在信令场景状态转换后重新设置迁移状态位的值。
10、 如权利要求 9所述的系统， 其中，
所述节点， 还用于在信令场景的信息中包括当前信令场景的类型； 所述 信令场景的类型为连接删除、 连接建立、 PC向 SPC迁移或 SPC向 PC迁移。
11、 如权利要求 10所述的系统， 其中，
所述节点， 还用于设置所述迁移状态位的值，
对于普通的连接删除或连接建立， 该字段取值为： 非迁移状态； 对于 SPC向 PC迁移， 该字段取值为： 开始 SPC迁移 PC或 SPC迁移为 PC成功；
对于 PC向 SPC迁移， 该字段取值为： 开始 PC迁移 SPC、 PC迁移 SPC 标签成功、 PC迁移 SPC操作成功或 PC迁移为 SPC失败。
12、 如权利要求 11所述的系统， 其中，
所述节点， 还用于当节点从上游节点接收标准信令或者向下游节点发出 标准信令， 当信令场景的类型为 SPC向 PC迁移， 且该标准信令为异常信令， 且迁移状态位取值为 PC迁移 SPC操作成功或非迁移状态时， 将迁移状态位 的值转换为开始 SPC迁移 PC; 还用于从下游节点接收标准信令或者向上游 节点发出标准信令， 当信令场景的类型为 SPC向 PC迁移， 且该标准信令为 异常信令， 且迁移状态位取值为开始 SPC迁移 PC时， 保持迁移状态位的值 为开始 SPC迁移 PC。
13、 如权利要求 11所述的系统， 其中， 所述节点， 还用于从下游节点 接收标准信令或者向上游节点发出标准信令，当信令场景的类型为 PC向 SPC 迁移时， 且该标准信令为异常信令， 且迁移状态位的值为 PC迁移 SPC标签 成功或者为 PC迁移为 SPC失败时， 将迁移状态位的值转换为开始 SPC迁移 PC; 还用于从上游节点接收标准信令或者向下游节点发出标准信令， 当信令 场景的类型为 PC向 SPC迁移时， 且该标准信令为异常信令， 且迁移状态位 的值为 PC迁移 SPC标签成功或 PC迁移 SPC操作成功时， 将迁移状态位的 值转换为开始 SPC迁移 PC。
14、 如权利要求 11或 12或 13所述的系统， 其中，
所述节点， 还用于接收标准信令， 判断标准信令为异常信令且转换后迁 移状态位的值为开始 SPC迁移 PC时， 迁移标签和交叉连接至管理平面。
PCT/CN2009/072115 2008-06-03 2009-06-03 一种自动交换光网络中连接迁移方法和系统 WO2009146652A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810098298.9 2008-06-03
CN2008100982989A CN101299893B (zh) 2008-06-03 2008-06-03 一种自动交换光网络中基于状态转换的迁移方法

Publications (1)

Publication Number Publication Date
WO2009146652A1 true WO2009146652A1 (zh) 2009-12-10

Family

ID=40079544

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/072115 WO2009146652A1 (zh) 2008-06-03 2009-06-03 一种自动交换光网络中连接迁移方法和系统

Country Status (2)

Country Link
CN (1) CN101299893B (zh)
WO (1) WO2009146652A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101299893B (zh) * 2008-06-03 2011-05-11 中兴通讯股份有限公司 一种自动交换光网络中基于状态转换的迁移方法
CN101945308B (zh) 2009-07-07 2013-05-08 中兴通讯股份有限公司 一种自动交换光网络中业务迁移的方法和装置
CN101998181B (zh) * 2009-08-10 2013-09-11 中兴通讯股份有限公司 Sncp业务迁移方法及装置
CN101854257B (zh) * 2010-05-25 2014-02-19 中兴通讯股份有限公司南京分公司 一种自动交换光网络中连接管理的迁移方法及系统
CN102594652B (zh) 2011-01-13 2015-04-08 华为技术有限公司 一种虚拟机迁移方法、交换机、虚拟机系统
WO2012129988A1 (zh) * 2011-03-30 2012-10-04 中兴通讯股份有限公司 一种节点加入对等网络的方法及系统
CN102325045B (zh) * 2011-09-08 2017-07-18 中兴通讯股份有限公司 一种实现控制平面交叉倒换的方法及系统
CN103139665B (zh) * 2011-11-30 2015-06-17 大唐联诚信息系统技术有限公司 一种基于7号信令的信息传输方法及系统

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1431833A (zh) * 2003-01-16 2003-07-23 上海交通大学 自动交换光/传送网络中交换连接的信令级联方法
US6813276B2 (en) * 2001-01-30 2004-11-02 The Regents Of The University Of California Optical layer multicasting using a single sub-carrier header with active header detection, deletion, and re-insertion via a circulating optical path
JP2005242662A (ja) * 2004-02-26 2005-09-08 Japan Telecom Co Ltd 通信システム
US6947669B2 (en) * 2001-03-07 2005-09-20 Meriton Networks Inc. Generic optical routing information base support
CN1764322A (zh) * 2005-11-10 2006-04-26 中兴通讯股份有限公司 自动交换光网络中资源冲突后连接资源再分配的一种方法
CN101170482A (zh) * 2006-10-26 2008-04-30 中兴通讯股份有限公司 Ason网络中通过控制平面实现spc激活/去激活的方法
CN101299893A (zh) * 2008-06-03 2008-11-05 中兴通讯股份有限公司 一种自动交换光网络中基于状态转换的迁移方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1277375C (zh) * 2003-07-31 2006-09-27 华为技术有限公司 一种光网络中永久连接和交换连接之间的转换方法
CN100531079C (zh) * 2005-05-09 2009-08-19 中兴通讯股份有限公司 自动交换光网络中sc/spc连接控制的方法

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6813276B2 (en) * 2001-01-30 2004-11-02 The Regents Of The University Of California Optical layer multicasting using a single sub-carrier header with active header detection, deletion, and re-insertion via a circulating optical path
US6947669B2 (en) * 2001-03-07 2005-09-20 Meriton Networks Inc. Generic optical routing information base support
CN1431833A (zh) * 2003-01-16 2003-07-23 上海交通大学 自动交换光/传送网络中交换连接的信令级联方法
JP2005242662A (ja) * 2004-02-26 2005-09-08 Japan Telecom Co Ltd 通信システム
CN1764322A (zh) * 2005-11-10 2006-04-26 中兴通讯股份有限公司 自动交换光网络中资源冲突后连接资源再分配的一种方法
CN101170482A (zh) * 2006-10-26 2008-04-30 中兴通讯股份有限公司 Ason网络中通过控制平面实现spc激活/去激活的方法
CN101299893A (zh) * 2008-06-03 2008-11-05 中兴通讯股份有限公司 一种自动交换光网络中基于状态转换的迁移方法

Also Published As

Publication number Publication date
CN101299893B (zh) 2011-05-11
CN101299893A (zh) 2008-11-05

Similar Documents

Publication Publication Date Title
US8289843B2 (en) Service failure recovery method and system
WO2009146652A1 (zh) 一种自动交换光网络中连接迁移方法和系统
EP2028774B1 (en) Method, system and node device for realizing service protection in the automatically switched optical network
US8068483B2 (en) Method for migration between a permanent connection and a switched connection in a transmission network
US7652983B1 (en) Method for restoration and normalization in a mesh network
US20070274224A1 (en) Path setting method, node device, and monitoring/control device
EP1942604A1 (en) A service switching method and the network node thereof
US8149693B2 (en) Method of implementing association in automatic switched optical network (ASON)
WO2006069523A1 (fr) Procede de recuperation de redemarrage de noeud dans un trajet de commutation multiprotocole par etiquette
EP1959609B1 (en) A method for service management in an intelligent optical network
US8868967B2 (en) Method and system for connection-error handling of service in an automatically switched optical network
WO2010133065A1 (zh) 基于无源光网络的保护系统和方法
US20130301402A1 (en) Message passing to assure deletion of label switched path
US9380359B2 (en) Method and a device of service migration in an automatically switched optical network
EP2395773B1 (en) Method and apparatus of sub-network connection protection (sncp) service migration
WO2009062354A1 (fr) Tap, lrm et système et procédé de contrôle de l&#39;état des ressources
WO2013033997A1 (zh) 一种实现控制平面交叉倒换的方法及系统
US8055131B2 (en) Route query method in ASON
WO2020118505A1 (zh) 一种业务路径建立的方法、网络设备和系统
US20210218668A1 (en) Tearing Down a Label Switched Path through a Communications Network
JP2006157709A (ja) パス設定方法およびパス開放方法

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09757086

Country of ref document: EP

Kind code of ref document: A1