WO2005011302A1 - Procede de transformation entre une connexion permanente et une connexion commute dans un reseau optique - Google Patents

Procede de transformation entre une connexion permanente et une connexion commute dans un reseau optique Download PDF

Info

Publication number
WO2005011302A1
WO2005011302A1 PCT/CN2004/000325 CN2004000325W WO2005011302A1 WO 2005011302 A1 WO2005011302 A1 WO 2005011302A1 CN 2004000325 W CN2004000325 W CN 2004000325W WO 2005011302 A1 WO2005011302 A1 WO 2005011302A1
Authority
WO
WIPO (PCT)
Prior art keywords
connection
node
conversion
request message
information
Prior art date
Application number
PCT/CN2004/000325
Other languages
English (en)
French (fr)
Inventor
Yongliang Xu
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP04726412A priority Critical patent/EP1650986B1/en
Priority to US10/566,602 priority patent/US8068483B2/en
Priority to DE602004017185T priority patent/DE602004017185D1/de
Priority to JP2006521369A priority patent/JP2007500955A/ja
Priority to BRPI0413161-4A priority patent/BRPI0413161B1/pt
Publication of WO2005011302A1 publication Critical patent/WO2005011302A1/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
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/27—Arrangements for networking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • 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/0086—Network resource allocation, dimensioning or optimisation
    • 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 a conversion technology between a permanent connection and a switching connection in an optical network, and particularly to a method for implementing a damage-free conversion between a permanent connection and a switching connection in an optical network.
  • Optical networks include synchronous digital systems / Synchronous Optical Networks (SDH / Sonet), wavelength switching networks, and so on.
  • the traditional optical network is a system based on centralized management.
  • the nodes of the network communicate with each other in a permanent connection.
  • the connection path is calculated in advance by the management plane according to the connection requirements and the use of network resources, and then it passes the network management interface along the connection path. (NMI-T) sends a cross-connect command to the nodes, performs unified assignment, and finally completes the path establishment process.
  • NMI-T sends a cross-connect command to the nodes, performs unified assignment, and finally completes the path establishment process.
  • the permanent connection method achieved good results in the early stage of optical network development due to its simple design and low cost.
  • the creation, maintenance, and dismantling of the optical connection in the permanent connection method require manual or network management system intervention. With the continuous growth of data traffic, this connection method cannot meet the dynamic and flexible requirements of the optical network system
  • the International Telecommunication Union proposed the Automatic Switched Optical Network (ASON) architecture, which added a control plane to the traditional optical network and proposed switching. Connection concept.
  • ASON Automatic Switched Optical Network
  • a node of an optical network first obtains the connection relationship between this node and other optical nodes through the link local discovery technology, and then publishes its node and link status through the control plane, and receives the status release of other nodes in the network.
  • each optical node has a "network map" describing the precise topology of the network.
  • the "network map” includes various information such as nodes, links, and resources.
  • the node When a node is required to establish a connection by a client device or management system, the node first uses the information of the "network map" and a certain routing algorithm to obtain a feasible path, and then drives the nodes on the path through a signaling protocol. Establish a cross connection.
  • Switched Connection switched Connection
  • Soft Permanent Connection soft permanent connection
  • the control plane can dynamically re-establish the connection routing and restore services.
  • the optical network system adopting this switching method has the characteristics of dynamic and flexibility, and can meet the needs of data traffic growth.
  • the main object of the present invention is to provide a method for converting between a permanent connection and a switching connection in an optical network, so as to realize a damage-free conversion between the permanent connection and the switching connection without interrupting services, and make the conversion process more Convenient and safe, and promote the development of automatic switching optical network technology.
  • a conversion method between a permanent connection and a switched connection in an optical network according to the present invention includes the following steps:
  • the currently connected ingress node After receiving the connection conversion request message, the currently connected ingress node forwards the connection conversion request message from node to node along the currently connected service signal transmission direction until the currently connected egress node;
  • connection conversion request message After receiving the conversion request message, perform permanent connection and exchange connection conversion from node to node.
  • the forwarding and connection conversion process of the connection conversion request message in this method is performed by the control plane of the node, and the connection conversion request message is transmitted through the control link.
  • the permanent connection in the process of performing a permanent connection and a switching connection, is converted into a switching connection.
  • a switching connection state is established on a node's control plane, and the control plane takes over the cross connection of the node that is permanently connected to the node.
  • the method makes permanent connection as described
  • Changing to a permanent connection is to delete the current switching connection state in the control plane of the node, and the management plane takes over the cross-connection of the switching connection at the node.
  • control plane is based on the TCP / IP protocol, and the permanent connection and the switching connection are converted using a resource reservation protocol RSVP-TE signaling protocol with traffic engineering extension or a label distribution protocol CR-LDP with limited routing. Signaling protocol implementation.
  • step b) of the method the conversion between the permanent connection and the exchange connection is performed on a node-by-node basis. After the transfer request message arrives at the egress node, the egress node starts the permanent connection and the switch connection conversion from node to node in the opposite direction of the connection conversion request message forwarding path until the ingress node.
  • the method further includes: after the conversion of each node is completed, sending a conversion completion notification message to the next node that needs to be converted, until the ingress node sends the conversion completion notification message to the connection conversion request initiator.
  • step b) of the method the conversion of the permanent connection and the exchange connection from node to node is that each node performs the conversion of the permanent connection and the exchange connection after receiving the connection conversion request message.
  • the method further includes: after the conversion of all nodes is completed, starting from the egress node and forwarding the conversion completion notification message from node to node in the opposite direction of the request message forwarding path, until the ingress node sends the conversion completion notification message To connection conversion request initiator.
  • the conversion completion notification message includes routing information of the entire conversion connection link.
  • the conversion completion notification message includes an identifier of the current exchange connection.
  • the connection conversion request message received by the ingress node includes at least: the ingress node identification and ingress information on the ingress node of the connection that is currently requested to be converted, or the ingress node identification and egress information on the ingress node; Before forwarding the connection conversion request message, further add its own exit information to the connection conversion request message.
  • the connection conversion request message when each node forwards the connection conversion request message, if the connection conversion request message includes entry information, then the connection conversion request message adds the exit information of the node to the next node; if the connection conversion request The message includes exit information, and the connection conversion request message is added with the entry information of the node to the next node.
  • the ingress information is an ingress port identifier or an ingress channel identifier or a combination thereof
  • the egress information is an egress port identifier or an egress channel identifier or a combination thereof.
  • the exit information of the node itself is obtained by querying the cross-connection information stored in itself according to the entry information of the current node.
  • the method further includes: judging whether the ingress node identifier and the entry information included in the received connection conversion request message, or whether the ingress node identifier and the egress information are correct, and if so, then Perform conversion, otherwise, return a failure message and end this process.
  • the connection conversion request message received by the ingress node in the method further includes: the exit node identification of the egress node, or the egress node identification and the egress letter for the connection that is currently requested to be converted. Before the conversion, the method further includes: judging whether the received connection conversion request message contains an exit node identifier, or whether the exit node identifier and the exit information are correct. If yes, establish or delete an exchange connection on the node; otherwise, return a failure message and end. This process. For a permanent connection, the connection conversion request message received by the ingress node includes at least: the identifier of the current exchange connection.
  • connection is a one-way connection or a two-way connection.
  • the switching connection in this method is a soft permanent connection initiated by a network management system, or a switching connection initiated by a client device or an agent of a client device.
  • the optical network is a synchronous digital system, or a synchronous optical network, or a wavelength switching network.
  • the present invention implements a connection type conversion point by point at each node of the optical network, thereby achieving a smooth transition between a permanent connection and a switched connection, which effectively avoids The impairment of service terminal and service data transmission increases the flexibility of network service implementation.
  • FIG. 1 is a schematic diagram of an optical network and a network connection with a control plane according to an embodiment of the present invention
  • FIG. 2 is a flowchart of converting a permanent connection to a switched connection in the present invention
  • FIG. 3 is a flowchart of converting a switching connection into a permanent connection in the present invention. Mode of Carrying Out the Invention
  • optical networks such as SDH / Sonet and wavelength switching networks.
  • These optical networks include multiple network nodes and links connecting these nodes.
  • the network nodes that need to perform connection type conversion are equipped with transmission, control, and management.
  • the control plane controls the transmission plane and supports the establishment of a switching connection.
  • the management plane manages the control plane and the transmission plane and supports the establishment of a permanent connection.
  • the optical network shown in FIG. 1 is taken as an example to describe the solution of the present invention.
  • the optical network shown in FIG. 1 includes six nodes: node A-node F, and each node includes a transmission plane AT-FT and a control plane AC-FC, where the transmission plane and the control plane may be physically separated It can also be physically combined and logically separated.
  • each node includes a management plane.
  • the management plane enables the transmission plane and control plane to be managed by the network management system. It is not shown in Figure 1 for clarity.
  • the nodes are connected by optical links, and the optical links are indicated by solid lines in FIG. 1; the control plane entities of the nodes communicate with each other through control links, and the control links are indicated by dashed lines in FIG. 1. These control links
  • the channel is logical.
  • SDH / Sonet can use overhead bytes.
  • all nodes in the optical network have established normal optical link connections, and the control plane has established normal sessions with neighboring nodes through the control channel.
  • Each node obtains the node with the neighbor through the link management protocol.
  • Point-to-point optical link connection relationship the connection relationship between these adjacent optical link nodes is spread through the link state routing protocol, and finally a consistent "network map" is established at each node, including all network nodes, between them Link connection relationship and link resource information; in addition, each node has a cross-connection relationship table, which records the connection relationship of each port and channel on the node.
  • connection ABEF has been established, and their connection is indicated by a dashed line in FIG. 1.
  • the control plane is usually based on the TCP / IP protocol, and the permanent connection and the switch connection are converted by using a resource reservation protocol RSVP-TE signaling protocol with traffic engineering extension or a label distribution protocol CR-LDP with limited routing. Make the agreement come true.
  • Step 201 Network management in the case of a soft permanent connection
  • the client device in the case of a system or switched connection sends a connection conversion request message to the ingress node, that is, node A, to convert the permanent connection ABEF into a switched connection.
  • the message described in this article is usually a command if it is sent from a network management system, and it is usually a signal if it is sent from a client device.
  • the connection conversion request message includes a list of routing records. If the permanent connection ABEF to be converted starts from the ingress port or ingress channel of the ingress node A and ends at the egress port or egress channel of the egress node F, the connection conversion request The routing record list of the message should at least include: the ingress node address (ID) and the ingress information of the ingress node; if the permanent connection ABEF to be converted starts from ingress node A and ends at egress node F, the connection conversion request message
  • the list of routing records should include at least: the ID of the ingress node and the egress information of the ingress node. The ingress information here is the ingress port ID of the node.
  • the ingress information also needs to include the ingress channel ID of the in port; the egress information is the egress port ID.
  • the permanent connection includes a channel on the port, and the exit information also needs to include the channel on the out port. ID.
  • the identifiers of all the network devices in this embodiment are represented by the IDs of the network devices.
  • the list may further include: a connection direction of the current connection, that is, two-way or one-way information such as a connection load type.
  • an egress node ID can also be added to the request message, and if the permanent connection to be converted starts from the ingress port or ingress channel of the ingress node A to the egress At the end of the egress port or egress channel of node F, the egress information of the egress node should also be included in it.
  • step 202 after the ingress node A receives the connection conversion request message of step 201 from its ingress port, if the connection conversion request message includes the ingress node ID of the ingress node and the ingress node entry information, the information is passed through and cross-connected according to itself.
  • the cross-connection information stored in the relationship table is used to obtain the exit information of the permanent connection that currently needs to be converted at node A, and these exit information is added to the conversion request message; if the connection conversion request message contains the exit information, the exit information is directly added Translation request message in the routing record list.
  • the next hop node that is, the ID of Node B
  • the next hop node that is, the ID of Node B
  • node A after receiving the connection conversion request message, node A first verifies whether the information in the message is correct, which specifically includes: checking whether the ingress node ID included in the signaling exists, and if the message includes an entry Information, it should also check whether its entry information exists and whether a permanent connection already exists on the channel. If so, proceed to step 202, otherwise, return an error message to the initiator of the conversion request and end. In this way, interference from error messages can be avoided.
  • Step 203 After receiving the connection conversion request message from the node A, the node B can obtain the exit information of the previous station, that is, the node A's exit information, and combine it with the link management and maintenance link stored in its own cross-connection relationship table.
  • the connection relationship can get the permanent connection to be converted at node B.
  • Similar to the processing of node A that is, find the exit information through the entry information, add the exit information to the end of the routing record list in the conversion request message, and then obtain the next hop according to the "network map"
  • the ID of node E sends the conversion request message to node E through the control channel.
  • step 204 after receiving the connection conversion request message from node B, node E forwards the conversion request message to egress node F in the same way as node B.
  • Step 205 After receiving the connection conversion request message from node E, node F establishes the requested switching connection status in the control plane of node F, and the control plane takes over the ports, channels, and cross-resources occupied by the connection, and Generate a conversion completion notification message.
  • This message retains all the contents of the conversion request message routing record list and adds the node ID. If the connection conversion request message contains the entry information of the ingress node, the conversion completion notification message should also be included. Add the exit information of the egress node, that is, the outbound port ID or the outbound channel ID. In this way, the conversion completion notification message contains the complete link route of the permanent connection to be converted, and then the conversion completion notification message along the connection conversion request message Transmission in the opposite direction of the transmission path, that is, transmission along the FEBA path.
  • This step may preferably further verify whether the message is correct after the node F receives the connection conversion request message from the node E, and specifically includes: analyzing the exit node ID carried in the message, if the exit node is also included And then analyze the exit information at the same time, and compare whether the information is consistent with the ID and the exit information of this node. If they are the same, then accept the connection conversion request and continue to the next step of step 205, otherwise, follow the path of FEBA Return a failure message to the initiator, give the cause of the error, and end.
  • the egress information of the egress node F can obtain egress information such as the egress port ID and egress port ID on the node F through processing similar to the nodes B and E.
  • Step 206 After receiving the conversion completion notification message from node F, node E, similar to node F, establishes the requested switching connection status in its control plane, and is connected by the control plane. Manage the cross-connection status of this node, and take over the resources occupied by the connection, and then forward the conversion completion notification message to Node B.
  • Step 207 After receiving the conversion completion notification message from node E, node B uses the same method as that of node E to establish a switching connection, and then returns a conversion completion notification message to node A.
  • step 208 after receiving the conversion completion notification message from node B, node A establishes an exchange connection in node A by the same method as that of nodes £ and B. If the conversion is successful, the conversion completion notification message is returned to the message initiator. At this point, the permanent connection ABEF has been converted into an exchange connection, and the connection has functions such as dynamic recovery like other exchange connections; if the conversion fails, a failure message is returned to the message initiator, and the process ends.
  • the exchange conversion request message is forwarded in sequence along the downstream direction of the permanent connection to be converted, that is, along the service signal direction of the connection, and the final establishment process of the exchange connection is from the egress node. Established node by node in the upstream direction.
  • the connection direction is bidirectional, one of the service signal directions can be arbitrarily selected to perform the connection conversion process.
  • Step 301 A network management system in the case of a soft permanent connection
  • the client device in the case of a switched connection sends a conversion request message to the ingress node A for switching from a switched connection to a permanent connection.
  • this message is called a reverse conversion request message.
  • the identifier of the interactive connection includes information such as the first and last node identifiers of the exchange connection, the session identifier, the connection group identifier, and the connection instance identifier.
  • Each node of the current exchange connection can locally use the information contained in the exchange connection identifier to locally Find the corresponding routing information, and reverse A conversion request message is sent.
  • the reverse conversion request message may also carry a routing record list like the connection conversion request message, that is, if the currently-to-be-converted switching connection ABEF starts from the ingress port or ingress channel of the ingress node A and reaches the egress node The exit port or exit channel of F is ended, and the routing record list of the connection conversion request message should at least include: the address of the ingress node (ID) and the ingress information of the ingress node; if the switching connection ABEF to be converted is from the ingress node Starting from A and ending at egress node F, the routing record list of the connection conversion request message should at least include: the ingress node ID and the egress information of the ingress node.
  • ID the address of the ingress node
  • the routing record list of the connection conversion request message should at least include: the ingress node ID and the egress information of the ingress node.
  • the ingress information here is the ingress port ID of the node. If the switch connection to be converted is a channel of the port, the ingress information also needs to include the ingress channel ID of the ingress port; the egress information is the egress port ID.
  • the conversion switching connection includes a channel of the port, and the exit information also needs to include the ID of the channel in the egress port.
  • the identifiers of all network devices in this embodiment are represented by the IDs of the network devices.
  • the list may further include: a connection direction of the current connection, that is, two-way or one-way information such as a connection load type.
  • the egress node ID can also be added to the request message, and if the permanent connection to be exchanged starts from the ingress port or ingress channel of the ingress node A to the egress At the end of the egress port or egress channel of node F, the egress information of the egress node should also be included in it.
  • Step 302 After receiving the reverse conversion request message of step 301 from its ingress port, the ingress node A marks the connection as in progress from the control plane, but does not delete the cross connection. If the reverse conversion request message contains According to the identifier of the current switched connection, according to the identifier, the corresponding routing information to the next-hop node B is locally found, and the reverse conversion request message is sent out.
  • the inverse conversion request message includes the ingress node ingress ID and ingress node entry information, then use this information and according to the cross connection stored in its own cross connection relationship table To obtain the exit information of the exchange connection currently in need of conversion at node A, and add these exit information to the reverse conversion request message; if the reverse conversion request message contains the exit information, add these exit information directly to the reverse conversion
  • the request message is in the list of routing records. Then, according to the link connection relationship maintained and maintained by the adjacent links managed in the control plane, that is, the "network map" is used to obtain the ID of the next hop node, that is, the node B, and the reverse conversion request message is connected to the IP-based control channel. Node B sends.
  • node A may first verify whether the information in the message is correct, including: checking whether the ingress node ID included in the signaling exists, and if the message includes ingress information, it shall also Check whether its entry information exists, and whether a switching connection already exists on the channel. If so, proceed to step 302, otherwise, return an error message to the initiator of the conversion request and end. In this way, interference from error messages can be avoided.
  • Step 303 After receiving the reverse conversion request message from node A, the node B marks the connection as in progress from the control plane, but does not delete the cross connection. If the reverse conversion request message includes the current exchange, The identifier of the connection is used to find the corresponding routing information to the next hop node E locally, and send the reverse conversion request message.
  • the exit information of node A can be obtained, and the link connection relationship maintained by the link management maintained in the cross connection relationship table of itself can be used to obtain the to-be-transformed switching connection at the node.
  • Relevant entry information of B then, similar to the processing of node A, that is to find the exit information through the entry information, and add the exit information to the end of the routing record list in the conversion request message, and then get the next one according to the "network map"
  • the ID of the hop node E sends a reverse conversion request message to the node E through the control channel.
  • Step 304 After receiving the reverse conversion request message from node B, node E performs the same operation as node B, and forwards the reverse conversion request message to egress node F.
  • Step 305 After receiving the connection conversion request message from node E, node F deletes the message. The state of the switching connection in the control plane, but the cross connection of the connection is not deleted, and the resources occupied by the connection are managed by the management plane; and a conversion completion notification message is generated, if the reverse conversion request message contains the current switching connection identifier Then, the identifier of the exchange connection is extracted and put into a conversion completion notification message, and the conversion completion notification message is sent in the opposite direction of the connection conversion request message transmission path, that is, sent along the FEBA path.
  • the reverse conversion request message contains a routing list
  • all contents in the conversion request message routing record list are retained in the conversion completion notification message, and the node ID is added.
  • the connection conversion request message contains the entry information of the ingress node
  • the exit information of the egress node that is, the egress port ID or egress channel ID should be added to the conversion completion notification message.
  • the conversion completion notification message includes the complete link route of the converted connection, and then the conversion is completed.
  • the notification message is sent in the opposite direction of the connection conversion request message transmission path, that is, sent along the FEBA path.
  • This step may preferably further verify whether the information contained in the message is correct after the node F receives the reverse conversion request message from the node E, and specifically includes: analyzing the exit node ID carried in the message, if It also includes the exit information of the egress node, and then analyzes the egress information to compare whether the information is consistent with the ID of the node and the egress information. If they are the same, then accept the reverse connection conversion request, and continue with the subsequent steps of step 305. Otherwise, a failure message is returned to the initiator along the path of the FEBA, and an error reason is given, and the process ends.
  • the egress information of the egress node F can obtain egress information such as the egress port ID and egress channel ID on the node F through processing similar to the nodes B and E.
  • Step 306 After receiving the conversion completion notification message from node F, node E is similar to node F, and deletes the information of the exchange connection in the control plane, but does not delete the cross connection of the connection, and hands over the resources occupied by the connection. Management plane management; then forward the conversion completion notification message to Node B.
  • Step 307 After receiving the reverse conversion completion notification message from node E, node B uses After deleting the exchange connection in the same way as node E, the conversion completion notification cancellation step 308 is returned to node A.
  • node A After receiving the conversion completion notification message from node B, node A deletes the exchange connection in the same way as nodes 5, B, but The cross connection of the connection is not deleted, and the resources occupied by the connection are managed by the management plane. If the reverse conversion is successful, the conversion completion notification message is returned to the message initiator. At this time, the exchange connection ABEF has been converted to a permanent connection. The control plane no longer manages the resources occupied by the connection; if the conversion fails, a failure message is returned to the message initiator, and the process ends.
  • the reverse conversion request message is forwarded in turn along the downstream direction of the permanent connection to be converted, that is, along the connection service signal direction.
  • the cancellation process of the switching connection is It is established node by node from the egress node in the upstream direction.
  • the connection direction is bidirectional, one of them can be arbitrarily selected to perform the connection conversion process.
  • the conversion between the permanent connection and the switched connection in the optical network is performed after the connection conversion request message reaches the egress node, and the egress node starts the forwarding path along the connection conversion request message.
  • the connection between the permanent connection and the switching connection is performed node by node until the ingress node.
  • the conversion process between the permanent connection and the exchange connection in the present invention may also be performed along the path ABEF of the connection conversion request message, which is specifically: immediately after each node receives the connection conversion request message, the conversion between the permanent connection and the exchange connection is performed. After the connection conversion of the node is completed, the connection conversion request message is forwarded to the next node that needs to be converted.
  • the conversion is completed in the upstream direction, that is, in the direction of FEBA in the optical network of FIG. 1 Notification message until the initiator of the conversion request.
  • the content of the connection conversion request message and the conversion completion notification message in each node and the processing method of the message by the node are exactly the same as in the embodiment described above.
  • the node may first analyze the routing information included in the request message to determine the route of the next node included in the request message It is consistent with automatically discovering whether the route of the next node in the connection to be converted is consistent with the content in the cross-connection relationship table of itself and the "network map". If they are the same, the operation of the subsequent steps is continued; otherwise, the conversion request originator is included with The error message of the error node identification information ends the process.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Optical Communication System (AREA)
  • Mechanical Coupling Of Light Guides (AREA)
  • Eyeglasses (AREA)
  • Use Of Switch Circuits For Exchanges And Methods Of Control Of Multiplex Exchanges (AREA)

Description

一种光网络中永久连接和交换连接之间的转换方法
技术领域
本发明涉及光网络中永久连接和交换连接之间的转换技术， 特别是 指一种实现光网络中永久连接和交换连接之间无损伤转换的方法。 发明背景
光网络包括同步数字体系 /同步光网络（ SDH/Sonet )、 波长交换网络 等。 传统的光网络是一种基于集中管理的系统， 网络的节点之间采用永 久连接方式实现通信， 连接路径由管理平面根据连接要求以及网络资源 利用情况预先计算， 然后沿着连接路径通过网络管理接口 （NMI-T ) 向 节点发送交叉连接命令， 进行统一指配， 最终完成通路的建立过程。 永 久连接方式在光网络发展初期因其设计简单、 成本较低等取得了较好效 果。 但是， 永久连接方式中光连接的创建、 维护和拆除都需要人工或网 管系统进行干预， 随着数据业务量的不断增长， 这种连接方式已不能满 足对光网络系统动态、 灵活的要求。
解决这个问题的关键是实现动态光交换， 因此， 国际电联（ITU-T ) 提出了自动交换光网络（ASON ) 架构， 该架构给传统上的光网络增加 了一个控制平面， 并提出了交换连接的概念。 根据这一思想， 光网络的 节点首先通过链路局部的发现技术获得本节点与其他光节点的连接关 系， 再通过控制平面发布其节点和链路状态， 并接收网络中其他节点的 状态发布， 最终每个光节点都有一份描述网络精确拓朴的 "网络地图"， "网络地图" 中包括节点、 链路、 资源等多种信息。 当节点被客户设备 或管理系统要求建立连接时， 节点先利用 "网络地图" 的信息， 结合一 定的路由算法得到一条可行的路径， 再通过信令协议驱动路径上的节点 建立交叉连接。 在网络连接动态建立、 拆除、 或者故障引起链路资源变 化时， 相应节点将及时发布更新的节点、 链路状态信息， 实现 "网络地 图" 的再同步。 在 ASON中， 如果节点接收的连接请求来自客户设备或 者代理， 则这时建立的连接称交换连接（Switched Connection ); 如果来 自 网管系统， 这时建立的连接称软永久连接 （ Soft Permanent Connection ), 在本文中如果没有特别指出， 交换连接和软永久连接将统 一称为交换连接。 在网络故障， 如： 链路中断或节点失效发生时， 如果 交换连接或软永久连接被中断， 则控制平面能动态地重建连接路由并恢 复业务。 采用这种交换方式的光网络系统具有动态、 灵活的特点， 可以 满足数据业务量增长的需要。
虽然交换连接方式会带来很多好处， 但是从传统基于供给的光网络 升级到自动交换光网络是一个庞大的系统工程， 涉及到网络设备、 网络 管理系统、 操作支持系统和其他方面的升级换代， 需要一个长期的演进 过程。 在目前的过渡过程中， 控制平面只是在一部分的节点上实现， 即 使在这些实现了控制平面的 "智能" 节点上基于供给的业务也不会立刻 消失， 永久连接和交换连接还会在网络中共存。 当永久连接和交换连接 共存于一个网络中时， 通常通过管理平面分配各自控制的网络资源， 网 络资源分配之后就不易更改， 但是， 资源的静态分割往往不能满足不断 变化光网络业务的开展， 运营商可能经常需要进行永久连接和交换连接 之间的转换， 以重新分配两种连接各自占用的网络资源， 和利用两种连 接不同的特性。
然而现有技术中，并没有制定永久连接和交换连接之间转换的方法， 如果需要进行连接类型的转换， 则需拆除已有连接后， 再建立所需类型 的连接。 这样做将会引起业务的中断， 造成业务数据网络传输损伤， 从 而会给业务运营带来问题， 给运营商的使用带来不便， 并进而会影响自 动交换光网络这项新技术的推广。 发明内容
有鉴于此， 本发明的主要目的在于提供一种光网络中永久连接和交 换连接之间转换的方法， 实现永久连接和交换连接之间在不中断业务情 况下的无损伤转换， 使转换过程更加方便、 安全， 推动自动交换光网络 技术的发展。
本发明的一种光网络中永久连接和交换连接之间的转换方法， 包括 以下步骤：
a )当前连接的入口节点在接收到连接转换请求消息后，从入口节点 开始沿当前连接的业务信号传输方向逐节点转发连接转换请求消息， 直 到当前连接的出口节点；
b )收到转换请求消息后， 逐节点进行永久连接和交换连接的转换。 该方法所述连接转换请求消息的转发和连接转换过程由节点的控 制平面执行， 并通过控制链路传递连接转换请求消息。
该方法在所述进行永久连接和交换连接的转换过程中永久连接转 换为交换连接是在节点的控制平面建立交换连接状态， 并由控制平面接 管永久连接在该节点的交叉连接。
该方法在所述进行永久连接
换为永久连接是在所述节点的控制平面中删除当前交换连接状态， 并由 管理平面接管所述交换连接在该节点的交叉连接。
该方法所述控制平面为基于 TCP/IP协议， 所述永久连接和交换连 接的转换釆用带流量工程扩展的资源预留协议 RSVP-TE信令协议或路 由受限的标签分布协议 CR-LDP信令协议实现。
该方法步骤 b )所述逐节点进行永久连接和交换连接的转换是在连 接转换请求消息到达所述出口节点后， 从出口节点开始沿所述连接转换 请求消息转发路径的相反方向逐节点进行永久连接和交换连接的转换， 直到入口节点。
该方法进一步包括： 所述每个节点转换完成后向下一个需要转换的 节点发送转换完成通知消息， 直到入口节点， 入口节点将所述转换完成 通知消息发送至连接转换请求发起者。
该方法步骤 b )所述逐节点进行永久连接和交换连接的转换是每个 节点在接收到连接转换请求消息后， 即进行永久连接和交换连接的转 换。
该方法进一步包括： 在所述所有节点转换完成后， 从出口节点开始 沿所述请求消息转发路径的相反方向逐节点转发转换完成通知消息， 直 到入口节点， 入口节点将所述转换完成通知消息发送至连接转换请求发 起者。
该方法所述转换完成通知消息中包括整个转换连接链路的路由信 息。 为永久连接， 则所述转换完成通知消息中包括当前交换连接的标识。
该方法所述入口节点收到的连接转换请求消息中至少包括： 当前请 求转换的连接在入口节点上的入口节点标识和入口信息， 或入口节点上 的入口节点标识和出口信息； 每个节点在转发连接转换请求消息以前， 在该连接转换请求消息中进一步加入自身的出口信息。
该方法每个节点在转发所述连接转换请求消息过程中， 如果连接转 换请求消息中包括有入口信息， 则在该连接转换请求消息中加入本节点 到达下一节点的出口信息； 如果连接转换请求消息中包括有出口信息， 则在该连接转换请求消息中加入本节点到达下一节点的入口信息。 该方法所述入口信息是入口端口标识或入口通道标识或其组合， 所 述出口信息是出口端口标识或出口通道标识或其组合。
该方法所述节点自身的出口信息是根据当前节点的入口信息通过 查询自身中保存的交叉连接信息获得的。
该方法所述入口节点进行永久连接和交换连接的转换前进一步包 括： 判断收到的连接转换请求消息中包含的入口节点标识和入口信息， 或入口节点标识和出口信息是否正确， 如果是， 则进行转换， 否则， 返 回失败消息， 结束本流程。
该方法所述入口节点收到的连接转换请求消息中进一步包括： 当前 请求转换的连接在出口节点的出口节点标识， 或出口节点标识和出口信 该方法所述出口节点进行永久连接和交换连接的转换前进一步包 括： 判断收到的连接转换请求消息包含的出口节点标识， 或出口节点标 识和出口信息是否正确， 如果是， 则在该节点上建立或删除交换连接， 否则， 返回失败消息， 结束本流程。 为永久连接， 则所述入口节点收到的连接转换请求消息中至少包括： 当 前交换连接的标识。
该方法所述连接是单向连接或双向连接。
该方法所述交换连接是由网络管理系统发起的软永久连接， 或是由 客户设备或客户设备的代理发起的交换连接。
该方法所述光网络为同步数字体系、 或同步光网络、 或波长交换网 络。
从上述方案可以看出， 本发明通过在光网络的每个节点逐点进行连 接类型转换， 实现了永久连接和交换连接之间的平滑过渡， 有效避免了 业务终端和业务数据的传输损伤， 增加了网络业务实施的灵活性。 附图简要说明
图 1为本发明实施例中带控制平面的光网络和网络连接示意图； 图 2为本发明中永久连接转换为交换连接的流程图；
图 3为本发明中交换连接转换为永久连接的流程图。 实施本发明的方式
下面结合附图对本发明进行详细描述。
本发明方案可应用于 SDH/Sonet、 波长交换网络等光网络， 在这些 光网络中包括多个网络节点和连接这些节点的链路， 需要进行连接类型 转换的网络节点具备传送、 控制、 管理三个平面， 控制平面控制传送平 面并支持交换连接的建立， 管理平面管理控制平面和传送平面并支持永 久连接的建立。
下面以图 1所示的光网络为例对本发明方案进行说明。 图 1所示的 光网络中包括六个节点： 节点 A -节点 F， 每个节点中都包括有传送平 面 AT - FT和控制平面 AC - FC, 其中， 传送平面和控制平面可以是物 理分离的， 也可以物理上合在一起， 逻辑上分离。 并且每个节点都包含 管理平面， 管理平面使得传送平面和控制平面可以被网络管理系统所管 理， 在图 1 中为清楚起见没有示出。 节点之间通过光链路连接， 光链 路在图 1中用实线表示； 节点的控制平面实体之间通过控制链路相互通 信， 控制链路在图 1中用虚线表示， 这些控制链路通道是逻辑的， 具体 实现上有多种方式， 如 SDH/Sonet 可以利用开销字节。 这里光网络中 所有节点间已经建立了正常的光链路连接， 控制平面已经通过控制通道 与相邻节点建立正常的会话； 通过链路管理协议每个节点得到与邻居节 点的光链路连接关系； 这些相邻光链路节点的连接关系通过链路状态路 由协议扩散， 最终在每个节点建立起一致的 "网络地图"， 其中包括所 有的网络节点、 它们之间的链路连接关系和链路资源信息； 另外每个节 点中都有一份交叉连接关系表，记录该节点上各端口、通道的连接关系。 并且在该网络中已经建立一条连接 A-B-E-F, 它们的连接在图 1中用点 划线表示。 其中， 所述控制平面通常为基于 TCP/IP协议的， 永久连接 和交换连接的转换采用带流量工程扩展的资源预留协议 RSVP-TE信令 协议或路由受限的标签分布协议 CR-LDP信令协议实现。
当图 1中所建立的连接 A-B-E-F是永久连接， 并需要将该永久连接 A-B-E-F转换为交换连接时， 转换过程参见图 2所示， 包括以下步骤： 步骤 201， 由软永久连接情况下的网络管理系统或交换连接情况下 的客户设备向入口节点，即节点 A发送将永久连接 A-B-E-F转换为交换 连接的连接转换请求消息。
其中，在本文中所述消息如果是从网络管理系统发出的通常是命令， 如果是从客户设备发出的通常是信令。
所述连接转换请求消息中包含路由记录列表， 如果当前待转换的永 久连接 A-B-E-F是从入口节点 A的入端口或入口通道开始，到出口节点 F的出端口或出口通道结束， 则在连接转换请求消息的路由记录列表中 应至少包括： 入口节点地址（ID )和该入口节点的入口信息； 如果当前 待转换的永久连接 A-B-E-F是从入口节点 A开始， 到出口节点 F结束， 则连接转换请求消息的路由记录列表中应至少包括： 入口节点 ID和该 入口节点的出口信息。 这里所述入口信息是该节点的入端口 ID, 如果待 转换永久连接包括所在端口的某个通道， 则入口信息中还需要包括入端 口中所在入口通道 ID; 出口信息是出端口 ID， 如果待转换永久连接包 括所在端口的某个通道， 则出口信息中还需要包括出端口中所在通道 ID。 本实施例中所有网络设备的标识都用网络设备的 ID表示。 另外， 在所述列表中还可以进一步包括： 当前连接的连接方向， 即指双向或者 单向， 连接负荷类型等信息。 并进而为了方便后续的步骤 205中出口节 点对连接转换请求消息进行验证， 还可在请求消息中加入出口节点 ID, 并且如果待转换永久连接从入口节点 A的入端口或入口通道开始，到出 口节点 F的出端口或出口通道结束， 则还应在其中包括出口节点的出口 信息。
步骤 202， 入口节点 A从其入端口接收到步骤 201的连接转换请求 消息后， 如果该连接转换请求消息中包含入口节点入端口 ID、 入口节 点入口信息， 则通过这些信息， 并根据自身交叉连接关系表中保存的交 叉连接信息得到当前需要转换的永久连接在 A节点的出口信息，将这些 出口信息加入该转换请求消息中； 如果连接转换请求消息中包含出口信 息， 则将这些出口信息直接加入转换请求消息的路由记录列表中。 再根 据控制平面中保存的相邻链路管理维护的链路连接关系， 即 "网络地图" 得到下一跳节点， 即节点 B的 ID， 将转换请求消息通过基于 IP的控制 通道连接向节点 B发送。
本步骤较佳的方式还可以在节点 A接收到连接转换请求消息后， 先 验证该消息中的信息是否正确， 具体包括： 检查信令中包含的入端口节 点 ID是否存在， 如果消息中包括入口信息， 则还应检查其入口信息是 否存在， 并且在该通道上是否已经存在永久连接， 如果是， 则进入步骤 202 的后续步骤， 否则， 向转换请求的发起者返回错误消息， 结束。 这 样， 可以避免错误消息的干扰。
步骤 203 , 节点 B收到从节点 A发来的连接转换请求消息后， 从中 可得到前一站， 即节点 A的出口信息， 再结合自身交叉连接关系表中保 存的链路管理维护的链路连接关系可以得到该待转换永久连接在节点 B 的相关入口信息； 然后， 与节点 A的处理类似， 即通过入口信息找出出 口信息， 并将出口信息添加到转换请求消息中的路由记录列表的末尾， 再根据 "网络地图"得到下一跳节点 E的 ID, 将转换请求消息通过控制 通道向节点 E发送。
步骤 204， 节点 E收到从节点 B发来的连接转换请求消息后， 用与 节点 B同样的方法将转换请求消息转发给出口节点 F。
步骤 205， 节点 F收到从节点 E发来的连接转换请求消息后， 在节 点 F的控制平面中建立起请求的交换连接状态， 由控制平面接管该连接 占用的端口、 通道和交叉资源， 并生成转换完成通知消息， 该消息中保 留有转换请求消息路由记录列表中的所有内容， 并加入了本节点 ID， 如果连接转换请求消息中包含入口节点的入口信息， 则还应在转换完成 通知消息中加入出口节点的出口信息，即出端口 ID或出通道 ID,这样， 在转换完成通知消息中包含有完整的待转换永久连接的链路路由， 然后 将该转换完成通知消息沿连接转换请求消息传送路径的相反方向发送， 即沿 F-E-B-A的路径发送。
本步骤较佳地可以在节点 F收到从节点 E发来的连接转换请求消息 后， 进一步验证该消息是否正确， 具体包括： 对消息中所携带的出口节 点 ID进行分析， 如果还包含出口节点的出口信息， 则同时对该出口信 息进行分析， 比较这些信息与本节点的 ID 以及出口信息是否一致， 如 果一致， 则接受该连接转换请求， 继续步骤 205的后续步骤， 否则， 沿 F-E-B-A的路径向发起者返回失败消息， 并给出错误原因， 结束。 其中 的出口节点 F 自身的出口信息可以通过类似节点 B、 E的处理得到节点 F上出端口 ID和出端口通道 ID等出口信息。
步骤 206, 节点 E收到节点 F发来的转换完成通知消息后， 与节点 F类似， 在其控制平面中建立起请求的交换连接状态， 并由控制平面接 管本节点的交叉连接状态， 并接管连接占用的资源， 然后将转换完成通 知消息向节点 B转发。
步骤 207, 节点 B收到节点 E发来的转换完成通知消息后， 用与节 点 E做同样的方法建立起交换连接后，向节点 A返回转换完成通知消息。
步骤 208,节点 A 收到节点 B的转换完成通知消息后，用与节点£、 B同样的方法在节点 A中建立起交换连接， 如果转换成功， 则将转换完 成通知消息返回至消息发起者， 此时， 永久连接 A-B-E-F 已经被转换 为交换连接， 该连接与其他的交换连接一样具备像动态恢复等功能； 如 果转换失败， 则向消息发起者返回失败消息， 结束。
从上述中可以看出， 本实施例中交换转换请求消息是沿待转换永久 连接的下游方向， 即沿该连接的业务信号走向逐节点依次转发的， 而交 换连接的最终建立过程是从出口节点沿上游方向逐节点建立的。 对于连 接方向是双向的情况， 可以任意选择其中的一个业务信号走向进行连接 转换过程。
当图 1 中所建立的连接 A-B-E-F是交换连接， 并需要将交换连接 A-B-E-F转换为永久连接时， 转换过程参见图 3所示， 包括以下步骤： 步骤 301， 由软永久连接情况下的网络管理系统或交换连接情况下 的客户设备向入口节点 A发送由交换连接转换为永久连接的转换请求 消息， 这里为了区分前面的过程， 将该消息称之为反向转换请求消息。
其中， 在该从交换连接到永久连接的反向转换过程中， 由于通常在 控制平面，每个节点本地已保存有其它交换连接节点的路由信息， 因此， 较佳的方案是在反向转换请求消息中只需提供当前交换连接的标识。 通 常， 在交互连接的标识中包含有交换连接的首末节点标识、 会话标识、 连接组标识和连接实例标识等信息， 当前交换连接的每个节点可以通过 交换连接标识中包含的这些信息在本地查找到相应的路由信息， 将反向 转换请求消息发送出去。
当然， 也可以在所述反向转换请求消息中像连接转换请求消息那样 携带有路由记录列表， 即如果当前待转换的交换连接 A-B-E-F是从入口 节点 A的入端口或入口通道开始，到出口节点 F的出端口或出口通道结 束， 则在连接转换请求消息的路由记录列表中应至少包括： 入口节点地 址（ ID )和该入口节点的入口信息；如果当前待转换的交换连接 A-B-E-F 是从入口节点 A开始， 到出口节点 F结束， 则连接转换请求消息的路由 记录列表中应至少包括： 入口节点 ID和该入口节点的出口信息。 这里 所述入口信息是该节点的入端口 ID，如果待转换交换连接是所在端口的 某个通道， 则入口信息中还需要包括入端口中所在入口通道 ID; 出口 信息是出端口 ID, 如果待转换交换连接包括所在端口的某个通道， 则出 口信息中还需要包括出端口中所在通道 ID。本实施例中所有网络设备的 标识都用网络设备的 ID表示。 另外， 在所述列表中还可以进一步包括： 当前连接的连接方向， 即指双向或者单向， 连接负荷类型等信息。 并进 而为了方便后续的步骤 305中出口节点对连接转换请求消息进行验证， 还可在请求消息中加入出口节点 ID,并且如果待交换永久连接从入口节 点 A的入端口或入口通道开始，到出口节点 F的出端口或出口通道结束， 则还应在其中包括出口节点的出口信息。
步骤 302, 入口节点 A从其入端口接收到步骤 301的反向转换请求 消息后， 从控制平面将该连接标记为删除进行中状态， 但不删除交叉连 接； 如果该反向转换请求消息中包含当前交换连接的标识， 则根据该标 识在本地查找相应的到达下一跳节点 B的路由信息，将该反向转换请求 消息发送出去。
如果该反向转换请求消息中包含入口节点入端口 ID、 入口节点入 口信息， 则通过这些信息， 并根据自身交叉连接关系表中保存的交叉连 接信息得到当前需要转换的交换连接在 A节点的出口信息，将这些出口 信息加入该反向转换请求消息中； 如果反向转换请求消息中包含出口信 息， 则将这些出口信息直接加入反向转换请求消息的路由记录列表中。 再根据控制平面中保存的相邻链路管理维护的链路连接关系， 即 "网络 地图" 得到下一跳节点， 即节点 B的 ID, 将反向转换请求消息通过基 于 IP的控制通道连接向节点 B发送。
另外还可以在节点 A接收到连接转换请求消息后， 先验证该消息中 的信息是否正确， 具体包括： 检查信令中包含的入端口节点 ID是否存 在， 如果消息中包括入口信息， 则还应检查其入口信息是否存在， 并且 在该通道上是否已经存在交换连接， 如果是， 则进入步骤 302的后续步 骤， 否则， 向转换请求的发起者返回错误消息， 结束。 这样， 可以避免 错误消息的干扰。
步骤 303， 节点 B收到从节点 A发来的反向转换请求消息后， 从控 制平面将该连接标记为删除进行中状态， 但不删除交叉连接； 如果该反 向转换请求消息中包含当前交换连接的标识， 则才 M居该标识在本地查找 相应的到达下一跳节点 E的路由信息，将该反向转换请求消息发送出去。
如果该反向转换请求消息中包含有路由列表， 则可得到节点 A的出 口信息， 再结合自身交叉连接关系表中保存的链路管理维护的链路连接 关系可以得到该待转换交换连接在节点 B的相关入口信息； 然后， 与节 点 A ό 处理类似， 即通过入口信息找出出口信息， 并将出口信息添加到 转换请求消息中的路由记录列表的末尾， 再根据 "网络地图" 得到下一 跳节点 Ε的 ID, 将反向转换请求消息通过控制通道向节点 E发送。
步骤 304， 节点 E收到从节点 B发来的反向转换请求消息后， 执行 与节点 B同样的操作， 并将反向转换请求消息转发给出口节点 F。
步骤 305 , 节点 F收到从节点 E发来的连接转换请求消息后， 删除 控制平面中该交换连接的状态， 但不删除该连接的交叉连接， 将该连接 占用的资源交由管理平面管理； 并生成转换完成通知消息， 如果反向转 换请求消息中包含当前交换连接的标识， 则提取该交换连接的标识放入 转换完成通知消息， 将该转换完成通知消息沿连接转换请求消息传送路 径的相反方向发送， 即沿 F-E-B-A的路径发送。
如果反向转换请求消息中包含路由列表， 在该转换完成通知消息中 保留转换请求消息路由记录列表中的所有内容， 并加入了本节点 ID, 如果连接转换请求消息中包含入口节点的入口信息， 则还应在转换完成 通知消息中加入出口节点的出口信息，即出端口 ID或出通道 ID，这样， 在转换完成通知消息中包含有完整的已转换连接的链路路由， 然后将该 转换完成通知消息沿连接转换请求消息传送路径的相反方向发送， 即沿 F-E-B-A的路径发送。
本步骤较佳地可以在节点 F收到从节点 E发来的反向转换请求消息 后， 进一步验证该消息包含的信息是否正确， 具体包括： 对消息中所携 带的出口节点 ID进行分析， 如果还包含出口节点的出口信息， 则同时 对该出口信息进行分析， 比较这些信息与本节点的 ID 以及出口信息是 否一致， 如果一致， 则接受该反向连接转换请求， 继续步骤 305的后续 步骤， 否则， 沿 F-E-B-A的路径向发起者返回失败消息， 并给出错误原 因， 结束。 其中的出口节点 F 自身的出口信息可以通过类似节点 B、 E 的处理得到节点 F上出端口 ID和出端口通道 ID等出口信息。
步骤 306, 节点 E收到节点 F发来的转换完成通知消息后， 与节点 F类似， 删除控制平面中该交换连接的信息， 但不删除该连接的交叉连 接， 将该连接占用的资源交由管理平面管理； 然后将转换完成通知消息 向节点 B转发。
步骤 307， 节点 B收到节点 E发来的反向转换完成通知消息后， 用 与节点 E做同样的方法删除交换连接后，向节点 A返回转换完成通知消 步骤 308,节点 A收到节点 B的转换完成通知消息后，用与节点5、 B同样的方法删除交换连接， 但不删除该连接的交叉连接， 将该连接占 用的资源交由管理平面管理， 如果反向转换成功， 则将转换完成通知消 息返回至消息发起者， 此时， 交换连接 A-B-E-F 已经被转换为永久连 接， 控制平面不再管理该连接占用的资源； 如果转换失败， 则向消息发 起者返回失败消息， 结束。
与永久连接到交换连接的转换过程相同， 本实施例中反向转换请求 消息是沿待转换永久连接的下游方向， 即沿该连接业务信号走向逐节点 依次转发的， 而交换连接的取消过程是从出口节点沿上游方向逐节点建 立的。 对于连接方向是双向的情况， 可以任意选择其中的一个方向进行 连接转换过程。
上面所述的较佳实施例中， 光网络中永久连接和交换连接之间的转 换都是在连接转换请求消息到达所述出口节点后， 从出口节点开始沿所 述连接转换请求消息转发路径的相反方向逐节点进行永久连接和交换 连接的转换， 直到入口节点。 另外， 本发明中永久连接和交换连接之间 的转换过程也可以沿连接转换请求消息的路径 A-B-E-F进行， 具体为： 在每个节点接收到连接转换请求消息后即刻进行永久连接和交换连接 的转换， 在该节点连接转换完成后向下一个需要转换的节点转发连接转 换请求消息， 当最后一个节点即出口节点连接转换完成后，沿上游方向， 即沿图 1光网络中的 F-E-B-A方向转发转换完成通知消息， 直至转换请 求的发起者。 其中， 这里连接转换请求消息和转换完成通知消息在每个 节点中的内容和节点对消息的处理方式与上面所述实施例中完全相同。
在上述方案中， 如果转换请求发起者发出的连接转换请求消息中事 先包括有待转换链路的整个或部分路由信息， 则在连接转换请求消息到 达节点后， 节点可先对请求消息中包括的路由信息进行分析， 判断该请 求消息中包含的关于下一节点的路由与根据自身交叉连接关系表中的 内容和 "网络地图" 自动发现待转换连接中下一个节点的路由是否一致， 如果一致， 则继续进行后续步骤的操作， 否则， 向转换请求发起者返回 包含有出错节点标识信息的错误消息， 结束流程。
以上所述仅为本发明的较佳实施例而已， 并不用以限制本发明， 凡 在本发明的精神和原则之内， 所作的任何修改、 等同替换、 改进等， 均 应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种光网络中永久连接和交换连接之间的转换方法， 其特征在 于， 包括以下步骤：
a )当前连接的入口节点在接收到连接转换请求消息后，从入口节点 开始沿当前连接的业务信号传输方向逐节点转发连接转换请求消息， 直 到当前连接的出口节点；
b )收到转换请求消息后， 逐节点进行永久连接和交换连接的转换。
2、 根据权利要求 1 所述的方法， 其特征在于， 所述连接转换请求 消息的转发和连接转换过程由节点的控制平面执行， 并通过控制链路传 递连接转换请求消息。
3、 根据权利要求 2 所述的方法， 其特征在于， 在所述进行永久连 接和交换连接的转换过程中永久连接转换为交换连接是在节点的控制 平面建立交换连接状态， 并由控制平面接管永久连接在该节点的交叉连 接。
4、 根据权利要求 2所述的方法， 其特征在于， 在所述进行永久连 控制平面中删除当前交换连接状态， 并由管理平面接管所述交换连接在 该节点的交叉连接。
5、 根据权利要求 2、 3、 4 中任意一项所述的方法， 其特征在于， 所述控制平面为基于 TCP/IP协议， 所述永久连接和交换连接的转换采 用带流量工程扩展的资源预留协议 RSVP-TE信令协议或路由受限的标 签分布协议 CR-LDP信令协议实现。
6、 根据权利要求 1所述的方法， 其特征在于， 步骤 b )所述逐节点 进行永久连接和交换连接的转换是在连接转换请求消息到达所述出口 节点后， 从出口节点开始沿所述连接转换请求消息转发路径的相反方向 逐节点进行永久连接和交换连接的转换， 直到入口节点。
7、 根据权利要求 6 所述的方法， 其特征在于， 进一步包括： 所述 每个节点转换完成后向下一个需要转换的节点发送转换完成通知消息， 直到入口节点， 入口节点将所述转换完成通知消息发送至连接转换请求 发起者。
8、 根据权利要求 1所述的方法， 其特征在于， 步骤 b )所述逐节点 进行永久连接和交换连接的转换是每个节点在接收到连接转换请求消 息后， 即进行永久连接和交换连接的转换。
9、 根据权利要求 8 所述的方法， 其特征在于， 进一步包括： 在所 述所有节点转换完成后， 从出口节点开始沿所述请求消息转发路径的相 反方向逐节点转发转换完成通知消息， 直到入口节点， 入口节点将所述 转换完成通知消息发送至连接转换请求发起者。
10、 根据权利要求 7或 9所述的方法， 其特征在于， 所述转换完成 通知消息中包括整个转换连接链路的路由信息。
11、 根据权利要求 7或 9所述的方法， 其特征在于， 如果所述永久 连接和交互连接之间的转换为交换连接转换为永久连接， 则所述转换完 成通知消息中包括当前交换连接的标识。
12、 根据权利要求 1所述的方法， 其特征在于， 所述入口节点收到 的连接转换请求消息中至少包括： 当前请求转换的连接在入口节点上的 入口节点标识和入口信息， 或入口节点上的入口节点标识和出口信息； 每个节点在转发连接转换请求消息以前， 在该连接转换请求消息中进一 步加入自身的出口信息。
13、 根据权利要求 12 所述的方法， 其特征在于， 每个节点在转发 所述连接转换请求消息过程中， 如果连接转换请求消息中包括有入口信 息， 则在该连接转换请求消息中加入本节点到达下一节点的出口信息； 如果连接转换请求消息中包括有出口信息， 则在该连接转换请求消息中 加入本节点到达下一节点的入口信息。
14、 根据权利要求 12 所述的方法， 其特征在于， 所述入口信息是 入口端口标识或入口通道标识或其组合 , 所述出口信息是出口端口标识 或出口通道标识或其组合。
15、 根据权利要求 12 所述的方法， 其特征在于， 所述节点自身的 出口信息是根据当前节点的入口信息通过查询自身中保存的交叉连接 信息获得的。
16、 根据权利要求 12 所述的方法， 其特征在于， 所述入口节点进 行永久连接和交换连接的转换前进一步包括： 判断收到的连接转换请求 消息中包含的入口节点标识和入口信息， 或入口节点标识和出口信息是 否正确， 如果是， 则进行转换， 否则， 返回失败消息， 结束本流程。
17、 根据权利要求 12 所述的方法， 其特征在于， 所述入口节点收 到的连接转换请求消息中进一步包括： 当前请求转换的连接在出口节点 的出口节点标识， 或出口节点标识和出口信息。
18、 根据权利要求 17 所述的方法， 其特征在于， 所述出口节点进 行永久连接和交换连接的转换前进一步包括： 判断收到的连接转换请求 消息包含的出口节点标识， 或出口节点标识和出口信息是否正确， 如果 是， 则在该节点上建立或删除交换连接， 否则， 返回失败消息， 结束本 流程。
19、 根据权利要求 1所述的方法， 其特征在于， 如果所述永久连接 和交互连接之间的转换为交换连接转换为永久连接， 则所述入口节点收 到的连接转换请求消息中至少包括： 当前交换连接的标识。
20、 根据权利要求 1所述的方法， 其特征在于， 所述连接是单向连 接或双向连接。
21、 根据权利要求 1所述的方法， 其特征在于， 所述交换连接是由 网络管理系统发起的软永久连接， 或是由客户设备或客户设备的代理发 起的交换连接。
22、 根据权利要求 1所述的方法， 其特征在于， 所述光网络为同步 数字体系、 或同步光网络、 或波长交换网络。
PCT/CN2004/000325 2003-07-31 2004-04-08 Procede de transformation entre une connexion permanente et une connexion commute dans un reseau optique WO2005011302A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP04726412A EP1650986B1 (en) 2003-07-31 2004-04-08 A method of transformation between permanent connection and switched connection in optical network
US10/566,602 US8068483B2 (en) 2003-07-31 2004-04-08 Method for migration between a permanent connection and a switched connection in a transmission network
DE602004017185T DE602004017185D1 (de) 2003-07-31 2004-04-08 Verfahren zur transformation zwischen einer permanenten verbindung und einer vermittelten verbindung in einem optischen netzwerk
JP2006521369A JP2007500955A (ja) 2003-07-31 2004-04-08 伝送ネットワークにおける固定接続及び相手先選択接続間の移行のための方法
BRPI0413161-4A BRPI0413161B1 (pt) 2003-07-31 2004-04-08 "método para migração entre uma conexão permanente e uma conexão comutada em uma rede de transmissão"

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN03149955.4A CN1277375C (zh) 2003-07-31 2003-07-31 一种光网络中永久连接和交换连接之间的转换方法
CN03149955.4 2003-07-31

Publications (1)

Publication Number Publication Date
WO2005011302A1 true WO2005011302A1 (fr) 2005-02-03

Family

ID=34085338

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2004/000325 WO2005011302A1 (fr) 2003-07-31 2004-04-08 Procede de transformation entre une connexion permanente et une connexion commute dans un reseau optique

Country Status (9)

Country Link
US (1) US8068483B2 (zh)
EP (1) EP1650986B1 (zh)
JP (1) JP2007500955A (zh)
CN (1) CN1277375C (zh)
AT (1) ATE411724T1 (zh)
BR (1) BRPI0413161B1 (zh)
DE (1) DE602004017185D1 (zh)
RU (1) RU2310279C2 (zh)
WO (1) WO2005011302A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2642473C1 (ru) * 2014-02-25 2018-01-25 Файберхоум Телекоммьюникейшн Текнолоджиз Ко., Лтд. Система otn и способ поддержки двусторонней передачи света от оптического контрольного канала по одному волокну

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE69931393T2 (de) * 1998-12-23 2007-03-29 Eli Lilly And Co., Indianapolis Antithrombotische amide
CN1277375C (zh) * 2003-07-31 2006-09-27 华为技术有限公司 一种光网络中永久连接和交换连接之间的转换方法
US20060248194A1 (en) * 2005-03-18 2006-11-02 Riverbed Technology, Inc. Connection forwarding
EP1878210B1 (en) * 2005-04-29 2016-01-13 Ciena Luxembourg S.a.r.l. Method and apparatus for non-disruptive call modification
CN1859369B (zh) * 2005-10-09 2010-07-14 华为技术有限公司 实现网络连接服务建立的方法及装置
CN101401483A (zh) * 2006-03-08 2009-04-01 日本电气株式会社 无线控制装置及其动作控制方法
CN101064675B (zh) * 2006-04-26 2011-07-06 华为技术有限公司 分组业务连接的切换方法及装置
CN101304340B (zh) 2007-05-09 2011-09-21 华为技术有限公司 一种资源状态监控方法及装置以及通信网络
CN101365230B (zh) 2007-08-07 2010-08-11 华为技术有限公司 异构网络切换/改变时的用户分离方法、系统及装置
CN101299893B (zh) * 2008-06-03 2011-05-11 中兴通讯股份有限公司 一种自动交换光网络中基于状态转换的迁移方法
CN101615967B (zh) 2008-06-26 2011-04-20 华为技术有限公司 一种业务数据的发送、接收方法、装置和系统
CN101626312B (zh) * 2008-07-11 2013-11-06 中兴通讯股份有限公司 永久连接与软永久连接迁移的管理平面实现方法
CN101360349B (zh) * 2008-09-12 2011-01-19 中兴通讯股份有限公司 一种有阻边界节点及有阻边界节点间建立连接的方法
US9071500B2 (en) * 2009-05-29 2015-06-30 Telefonaktiebolaget L M Ericsson (Publ) Ownership transfer of a label switched path
CN101594558B (zh) * 2009-06-23 2011-12-28 中兴通讯股份有限公司 一种链路资源碎片整理方法及系统
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 中兴通讯股份有限公司南京分公司 一种自动交换光网络中连接管理的迁移方法及系统
US9628356B2 (en) * 2013-10-10 2017-04-18 Ixia Methods, systems, and computer readable media for providing user interfaces for specification of system under test (SUT) and network tap topology and for presenting topology specific test results
US9356855B2 (en) * 2013-10-10 2016-05-31 Ixia Methods, systems, and computer readable media for providing for specification or autodiscovery of device under test (DUT) topology information
US9906403B2 (en) * 2014-08-26 2018-02-27 Mitsubishi Electric Corporation Slave station device, master station device, optical communication system, and malfunction detection method
US10587515B2 (en) * 2017-02-07 2020-03-10 Futurewei Technologies, Inc. Stateless information centric forwarding using dynamic filters
US10958560B2 (en) * 2019-07-16 2021-03-23 At&T Intellectual Property I, L.P. Common abstraction for network traffic migration
US10917326B1 (en) 2019-08-23 2021-02-09 Keysight Technologies, Inc. Methods, systems, and computer readable media for debugging test traffic generation

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1384618A (zh) * 2002-06-07 2002-12-11 清华大学 自动交换光网络中的光通道建立方法
JP2003204351A (ja) * 2003-01-24 2003-07-18 Oki Electric Ind Co Ltd 交換システム

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3612105B2 (ja) * 1995-03-13 2005-01-19 株式会社東芝 Ａｔｍ通信システムとａｔｍ通信システムにおけるプロセスマイグレーション方法
US5761193A (en) * 1996-05-31 1998-06-02 Derango; Mario F. Method for pre-establishing communications in a wireless communication network
US6775288B1 (en) * 1998-03-13 2004-08-10 Alcatel Canada Inc. Identifying soft permanent virtual circuits
US7106698B1 (en) * 1998-09-16 2006-09-12 Cisco Technology, Inc. System for triggering the control plane in an asynchronous connection-oriented transmission network
JP3223898B2 (ja) * 1999-01-06 2001-10-29 日本電気株式会社 集中型通信網観測制御装置
WO2001010083A1 (fr) 1999-07-29 2001-02-08 Fujitsu Limited Procede et dispositif de conversion de donnees de connexion, et standard a cet effet
JP2001156798A (ja) * 1999-11-29 2001-06-08 Hitachi Ltd Ｖｃ切替え方法およびａｔｍ交換機
US20010033561A1 (en) * 2000-01-25 2001-10-25 Telefonaktiebolaget L M Ericsson ( Publ). Combination switch and routing-switching radio base station
JP3871538B2 (ja) 2001-10-03 2007-01-24 沖電気工業株式会社 ネットワークリソース予約制御方法及びノード
US7093160B2 (en) * 2001-05-03 2006-08-15 Nokia Corporation Method and system for implementing MPLS redundancy
US7706383B2 (en) 2001-07-31 2010-04-27 Alcatel-Lucent Usa Inc. Minimum contention distributed wavelength assignment in optical transport networks
US6999681B2 (en) * 2002-01-23 2006-02-14 Pts Corporation Method of seamless migration from static to agile optical networking
US7436817B2 (en) * 2002-03-08 2008-10-14 Nortel Networks Limited Call clearing for legacy mobile circuit switched domain wireless systems
US7085554B2 (en) * 2003-01-24 2006-08-01 Common Voices Llc Subscriber migration system
CN1277375C (zh) * 2003-07-31 2006-09-27 华为技术有限公司 一种光网络中永久连接和交换连接之间的转换方法
US20050083862A1 (en) * 2003-10-20 2005-04-21 Kongalath George P. Data migration method, system and node

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1384618A (zh) * 2002-06-07 2002-12-11 清华大学 自动交换光网络中的光通道建立方法
JP2003204351A (ja) * 2003-01-24 2003-07-18 Oki Electric Ind Co Ltd 交換システム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Study on optical communications", ATM SWITCHED VIRTUAL CIRCUIT SIGNALING, vol. 6, 1998, pages 16 - 20, XP008077738 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2642473C1 (ru) * 2014-02-25 2018-01-25 Файберхоум Телекоммьюникейшн Текнолоджиз Ко., Лтд. Система otn и способ поддержки двусторонней передачи света от оптического контрольного канала по одному волокну

Also Published As

Publication number Publication date
DE602004017185D1 (de) 2008-11-27
CN1581796A (zh) 2005-02-16
US8068483B2 (en) 2011-11-29
EP1650986A1 (en) 2006-04-26
RU2310279C2 (ru) 2007-11-10
CN1277375C (zh) 2006-09-27
ATE411724T1 (de) 2008-10-15
EP1650986A4 (en) 2007-03-14
RU2006106235A (ru) 2006-06-27
US20060268944A1 (en) 2006-11-30
BRPI0413161B1 (pt) 2018-01-16
EP1650986B1 (en) 2008-10-15
JP2007500955A (ja) 2007-01-18
BRPI0413161A (pt) 2006-10-03

Similar Documents

Publication Publication Date Title
WO2005011302A1 (fr) Procede de transformation entre une connexion permanente et une connexion commute dans un reseau optique
EP0752795B1 (en) Link reservation in communications networks
JP4199514B2 (ja) ネットワークを相互に接続する方法、及びそのための装置
US20090103533A1 (en) Method, system and node apparatus for establishing identifier mapping relationship
JP5739960B2 (ja) パケット光ネットワークの宛先ノードに外部の光データパケットを提供する方法及びシステム
WO2009146652A1 (zh) 一种自动交换光网络中连接迁移方法和系统
WO2007079649A1 (fr) Procede et dispositif de decouverte automatique pour liaison de couche client
CN101860769B (zh) 一种ip与光融合的方法、装置和系统
KR100842256B1 (ko) 지.엠.피.엘.에스 기반 네트워크에서 물리계층의 레이블 스위칭 경로에 대한 연결성 검사 방법 및 그 시스템
CN109005473B (zh) 一种协同选择路径的方法、装置及系统
WO2014059570A1 (zh) 建立标签交换路径的方法、设备和系统
US7898938B2 (en) Transmitting apparatus and transmitting method
WO2020118505A1 (zh) 一种业务路径建立的方法、网络设备和系统
CN101753450A (zh) 三层网络联合资源优化方法
WO2009062354A1 (fr) Tap, lrm et système et procédé de contrôle de l'état des ressources
WO2007071114A1 (fr) Procede pour le reacheminement sans interruption en reseau optique
US7512130B2 (en) Optical communication network system
EP2395773B1 (en) Method and apparatus of sub-network connection protection (sncp) service migration
EP4109821A1 (en) Restoration path configuration method and apparatus
KR100890341B1 (ko) 파장 분할 다중화 전달망에서 파장 경로의 변환 방법
JP4425201B2 (ja) 仮想大容量パス制御方法およびパス通信装置
JP3938708B2 (ja) 光パス通信網およびノードおよび光パス設定波長検索方法
WO2007084597A2 (en) System, network and methods for provisioning optical circuits in a multi-network, multi vendor environment
JP3778138B2 (ja) ネットワークパス設定方法及びシステム
KR101034915B1 (ko) 비동기식 전송 모드 초고속 통신망에서의 메트로이더넷-다중 프로토콜 라벨 스위칭 복합 연결 관리 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

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

Ref document number: 2004726412

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2006521369

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 1037/DELNP/2006

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2006106235

Country of ref document: RU

WWP Wipo information: published in national office

Ref document number: 2004726412

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2006268944

Country of ref document: US

Ref document number: 10566602

Country of ref document: US

ENP Entry into the national phase

Ref document number: PI0413161

Country of ref document: BR

WWP Wipo information: published in national office

Ref document number: 10566602

Country of ref document: US