WO2010028586A1 - 一种有阻边界节点及有阻边界节点间建立连接的方法 - Google Patents
一种有阻边界节点及有阻边界节点间建立连接的方法 Download PDFInfo
- Publication number
- WO2010028586A1 WO2010028586A1 PCT/CN2009/073795 CN2009073795W WO2010028586A1 WO 2010028586 A1 WO2010028586 A1 WO 2010028586A1 CN 2009073795 W CN2009073795 W CN 2009073795W WO 2010028586 A1 WO2010028586 A1 WO 2010028586A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- connection
- information
- boundary node
- node
- blocked
- Prior art date
- Legal status (The legal status 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 status listed.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/60—Router architectures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/62—Wavelength based
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/78—Architectures of resource allocation
- H04L47/783—Distributed allocation of resources, e.g. bandwidth brokers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0073—Provisions for forwarding or routing, e.g. lookup tables
Definitions
- the present invention relates to intelligent optical network technologies, and in particular, to a method for establishing a connection between a blocked boundary node and a blocked boundary node in an intelligent optical network.
- BACKGROUND With the large-scale application of intelligent optical network technology, the construction and development of a transmission network has evolved from a single hardware transmission technology to a comprehensive transmission technology combining network management technology, control technology, and hardware technology. With the help of the intelligent optical network control plane, the reliability of the network is improved, and new bandwidth services such as OVPN (Optical Virtual Private Network) and BoD (Bandwidth on demand) can be quickly provided. It brings efficiency and cost reduction to the operation and maintenance of the network.
- OVPN Optical Virtual Private Network
- BoD BoD
- WSS Widelength Selective Switch
- MEMS Micro Electromechanical System
- OEO Optical-Electrical-Optical
- OTN has advantages in the definition and end-to-end management of the WDM system, OTN has also begun to appear on commercial transmission equipment.
- the first method is to notify the various nodes by extending the route flooding information, and bring in the resistance information for calculation during the route calculation, so that the calculated route is exchangeable at each node.
- the calculated success rate of the route established by this method is high, but a large amount of flooding information needs to be added.
- the second method does not flood the blocked information, but does not reserve specific resources in the forward signaling process when the connection is established, but only gives a range of available resources, and finally only the target node.
- the last used range selects the last resource to be used. This method does not require additional flooding information, but the calculated route has a success rate of establishing a connection.
- the present invention provides a method for establishing a connection between a blocked boundary node and a blocked boundary node, by separately processing the obstructive information of the boundary subnet point of the boundary node of the routing domain from the obstructive information of the subnet point in the routing domain. Therefore, the flooding message of the blocked information is effectively reduced under the premise of ensuring the success rate of the connection establishment.
- the technical solution of the present invention is as follows: A blocked boundary node, comprising a connection controller, a link resource manager and a routing controller, and a connection controller, configured to connect to the link after receiving the connection request message
- the resource manager sends a blocked information query request, and verifies the blocked information of the local end that is queried.
- the blocked information of the exit boundary node is queried, and the resistance information of the local end and the exit boundary node are blocked.
- the information is used as a query parameter to send a routing query request to the routing controller;
- the link resource manager is configured to respond to the blocked information query request of the connected controller, and feed back the blocked information of the local end to the connection controller; Respond to the route query request, providing routing information for establishing a connection.
- the connection controller is further configured to: after receiving the blocked information update message of the local end, update the blocked information stored by the local end.
- the connection controller is further configured to: after receiving the blocked information update message of the remote border node, update the blocked information of the egress boundary node stored by the local end according to the message.
- the ingress border node After receiving the connection establishment request message, the ingress border node queries and verifies the obstructive information of the ingress subnet point in the ingress subnet, and sends a blocked information query request to the egress boundary node after the verification succeeds;
- the queried information of the subnet point of the risk certificate exit in the egress subnet is returned, and the blocked information is returned to the ingress boundary node after the verification succeeds;
- the ingress border node queries the route with the blocked information of the ingress subnet point and the egress subnet point as the query parameter, and sends a connection request message to the egress border node after the route is successfully queried;
- the connection establishment is completed.
- the ingress border node After receiving the connection establishment request message, the ingress border node performs a risk certificate on the message, and if the risk certificate passes, the query and the risk entry subnet point are in the ingress subnet. The blocked information, otherwise, the return connection request failed response, and the process ends.
- the egress border node opens the blocked information monitoring after receiving the connection request message; in the step D, the ingress border node opens the obstruction information monitoring after receiving the connection confirmation message.
- the ingress boundary node updates the blocked information of the locally stored local access subnet point.
- the connection is established.
- the exit boundary node detects that the resistance information of the local egress subnet point changes, sending a blocked information update message to the ingress border node, where the ingress border node stores the egress according to the message to the local storage.
- the obstructed information of the exit subnet point of the boundary node is updated.
- the ingress border node turns off the resistance information monitoring of the local end, and sends a connection release request to the egress boundary node; the egress border node closes the local end after receiving the connection release request.
- the blocked information monitoring sends a connection release confirmation message to the ingress border node after processing the connection release request.
- the present invention separates the obstructive information of the boundary subnet point of the boundary node of the routing domain from the obstructive information of the subnet point in the routing domain, so as to effectively reduce the success rate of the connection establishment. Flooding messages that have information.
- FIG. 1 is a schematic structural view of a blocked boundary node in the present invention
- FIG. 2 is a flowchart of a method for establishing a connection between blocked nodes in the present invention
- FIG. 3 is a schematic diagram of a network topology according to an example of the present invention
- 4 is a flowchart of establishing a connection in a case where a boundary node is in a resisted state according to the example of the present invention
- FIG. 1 is a schematic structural view of a blocked boundary node in the present invention
- FIG. 2 is a flowchart of a method for establishing a connection between blocked nodes in the present invention
- FIG. 3 is a schematic diagram of a network topology according to an example of the present invention
- 4 is a flowchart of establishing a connection in a case where a boundary node is in a resisted state according to the example of the present invention
- FIG. 1 is a schematic structural view of a blocked boundary node in the present invention
- FIG. 5 is a flow chart of releasing a connection of a blocked boundary node in the example of the present invention
- FIG. 6 is an example of the present invention.
- FIG. 7 is a flowchart of updating the blocked information stored by the node A when the C node has resistance information changes in the example of the present invention.
- DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention separates the obstructive information of a boundary subnet point of a boundary node of a routing domain from the obstructive information of a subnet point in a routing domain, thereby effectively reducing the resistance information under the premise of ensuring the success rate of connection establishment. Flooding news.
- the obstruction information of the boundary subnet point of the boundary node in the present invention can use the same data model, but different from the obstruction information of the subnet point in the routing domain, the boundary
- the blocked information of the node's boundary subnet point is only specified at the boundary.
- the boundary subnet point of a node is used in route calculation when it is used as the ingress/egress subnet point of the connection, and for other connections, this information is invalid.
- the obstructive information of the entry/exit subnet point of the boundary node is only related to the connection using the subnet point.
- the structure of the boundary nodes in the intelligent optical network mainly includes the connection controller (CC), the routing controller (RC) and the link resource manager (LRM).
- the functions of each component are as follows: Connection controller, responsible for coordinating link resources Managers, routing controllers, and peer-to-peer and slave connection controllers to manage and monitor connection establishment, release, and modification of connection parameters for existing connections.
- the routing controller is responsible for responding to the request from the connection controller, providing routing information for establishing a connection, which may be end-to-end (for example, source routing) or hop-by-hop; and responding to the network management extension Pak information (subnet points and their abstractions) requests.
- the Link Resource Manager is responsible for managing the Subnet Point Pool (SNPP) link, including assigning and de-assigning subnet point link connections, and providing topology and status information. Since the subnet point pool (SNPP) link can be public or private, the link resource manager can also be public or associated with a virtual private network (VPN).
- VPN virtual private network
- connection controller 20 After receiving the connection request message, sending a blocked information query request to the link resource manager 21, and verifying the blocked information of the local end, and querying the blocked information of the exit boundary node after the verification is passed, and Sending a route query request to the routing controller 22 by using the blocked information of the local end and the blocked information of the egress boundary node as the query parameter.
- the connection controller 20 is configured to: after receiving the blocked information update message of the local end, The blocked information stored in the local end is updated; and after receiving the blocked information update message of the remote border node, the blocked information of the egress boundary node stored at the local end is updated according to the message.
- the link resource manager 21 is configured to feed back the blocked information of the local end to the connection controller 20 in response to the blocked information query request of the connection controller 20.
- the routing controller 22 is configured to provide routing information for establishing a connection in response to the routing query request.
- FIG. 2 is a flowchart of a method for establishing a connection between a blocked boundary node according to the present invention. The main implementation process is as follows: Step 10: The connection controller of the ingress border node verifies the message after receiving the connection establishment request message.
- Step 11 After the verification is successful, the connection controller of the ingress border node queries and verifies the blocked information of the ingress subnet point in the ingress subnet to the local link resource manager; Step 12, when the risk certificate is successful, The connection controller of the ingress border node sends a connection information query request message to the connection controller of the egress boundary node; Step 13. The connection controller of the egress boundary node queries the local link resource manager after receiving the resistance information query request And the blocked information of the exit subnet point in the exit subnet; Step 14.
- connection controller of the exit boundary node After the verification is successful, the connection controller of the exit boundary node sends a resistive information query response to the connection controller of the ingress boundary node, where Obstructed information in the egress subnet through the verified egress subnet point; Step 15, connection controller of the ingress boundary node The local routing controller sends a route query request, and the query parameter is the blocked information of the ingress subnet point and the obstruction information of the egress subnet point. Step 16. After the query is successfully routed, the connection controller of the ingress border node sends a connection request to the downstream.
- Step 17 the connection controller of the egress boundary node receives and processes the connection request message, notifies the local link resource manager to open the blocked information detection, and then sends a connection confirmation message to the ingress border node;
- Step 18 After receiving the connection confirmation message returned by the downstream, the connection controller of the ingress boundary node opens the blocked information monitoring, and the connection establishment is completed.
- the link resource manager of the ingress border node detects that the blocked information of the local ingress subnet point changes, the local connection controller is notified, and the local controller stores the local end by the connection controller.
- the blocked information of the ingress subnet point is updated; when the link resource manager of the egress boundary node detects that the obstructive information of the local egress subnet point changes, the local connection controller is notified, and the connection control of the egress boundary node is Transmitting, by the connection controller of the ingress boundary node, a resistance information update message, where the connection controller of the ingress boundary node stores the information according to the message
- the blocked information of the exit subnet point of the stored exit boundary node is updated.
- connection release message After the connection is established, after the connection controller of the ingress border node receives the connection release message, the connection release message is verified, and if the verification is passed, the local link resource manager is notified to close the blocked information monitoring, and then Sending a connection release request to the connection controller of the egress boundary node, and the connection controller of the egress border node notifies the local link resource manager to close the damper information monitoring after receiving the connection release request, after processing the After the connection release request, a connection release confirmation message is sent to the connection controller of the ingress boundary node.
- FIG. 3 is a schematic diagram of a network topology according to an example of the present invention.
- FIG. 4 is a flowchart of establishing a connection in a case where a boundary node is in a resisted state according to the example of the present invention, which mainly includes the following steps: Step 301: A node connection controller receives a connection request message; Step 302, A node connection control The device verifies the connection request message, and mainly verifies whether the connection request condition is correct.
- step 303 If the verification fails, step 303 is performed, otherwise step 304 is performed; Step 303, the A node connection controller returns a connection request failure response, and the process ends; Step 304, A node connection The controller queries the A-node link resource manager for the obstructive information of the ingress subnet point, mainly the exchangeability of the ingress subnet point and the other subnet points of the A node in the routing domain.
- step 303 When the query fails, there is no entry subnet point or If there is no other subnet point in the routing domain that is exchangeable with the ingress subnet point, step 303 is performed, otherwise step 305 is performed; Step 305, the A node connection controller sends a blocked information query request message to the C node, which is used to query the C node export subroutine. The blocked information of the network point; Step 306, the C node is connected to the controller to receive and verify the blocked information query. News, queries is to verify the conditions are correct, if it fails to perform verification step 307, otherwise step Step 307: The C-node connection controller sends a resistance information query request failure response to the A-node connection controller.
- Step 308 the A-node connection controller receives the resistance information query request failure response, and then performs step 303; Step 309, C node connection The controller queries the C-node link resource manager for the obstruction information of the egress subnet point. When the query fails, step 307 is performed. Otherwise, step 310 is performed. Step 310: The C-node connection controller fills the obstruction information of the egress subnet point.
- Step 311 the A node receives the resistance information query response, the A node entry subnet point resistance information and the C node exit subnet point resistance information
- the routing controller is queried as the query condition, and when the query fails, step 303 is performed, otherwise step 312 is performed; step 312, the A node connection controller sends a connection request to the next hop B node, and the B node receives and processes the connection request.
- Step 313 the C node connection controller receives and processes the message
- the C-node link resource manager is notified to open the blocked information monitoring, and then the connection response message is sent to the Node B, the Node B receives and processes the connection response, and then forwards the connection response to the Node A;
- Step 314 the Node A connects to the controller.
- the A node link resource manager is notified to open the blocked information monitoring; Step 315, the A node sends a connection confirmation, and the process ends.
- Step 401 A node connection controller receives a connection release message; Step 402, A node connection control The device verifies the connection release message, and mainly verifies whether the connection release request condition is correct. If the verification fails, step 403 is performed, otherwise step 404 is performed; Step 403, the A node connection controller returns a connection release request failure response, and the process ends; Step 404: The A node connection controller notifies the A node link resource manager to close the blocked information monitoring.
- Step 405 The A node connection controller sends a connection release request to the next hop B node, and the B node receives and processes the connection release request.
- Step 406 the C node connection controller notifies the C node link resource manager to close the blocked information monitoring after receiving the connection release request, and processes the connection release request
- the Node B receives and processes the connection release response, and then forwards the connection release response to the A node
- Step 407 the A node connection controller receives and processes the connection release confirmation and sends the connection release confirmation. , the process ends. Please refer to FIG.
- Step 501 The A node link resource manager detects the local end When the entry subnet point has a resistance information change, such as a fiber connection failure of an exit subnet point and an entry subnet point, the A node link resource manager notifies the A node to connect to the controller A node entry subnet point to have resistance information update;
- Step 502 After receiving the information update of the A-node entry subnet point, the A-node connection controller updates the locally stored A-node entry sub-network point with resistance information, and the process ends. Please refer to FIG. 7.
- FIG. 7 The A node link resource manager detects the local end When the entry subnet point has a resistance information change, such as a fiber connection failure of an exit subnet point and an entry subnet point, the A node link resource manager notifies the A node to connect to the controller A node entry subnet point to have resistance information update;
- Step 502 After receiving the information update of the A-node entry subnet point, the A-node connection controller updates the locally stored
- Step 601 The C node link resource manager detects When the local egress subnet point has resistance information change, the C node link resource manager notifies the C node to connect to the controller C node entry subnet point to have resistance information update; Step 602, the C node connection controller sends the C node exit subnet point to block The information update message is sent to the A node.
- Step 603 After receiving the information update message of the C node egress subnet point, the A node connection controller updates the locally stored C node egress subnet point with resistance information, and the process ends.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
一种有阻边界节点及有阻边界节点间建立连接的方法 技术领域 本发明涉及智能光网络技术,特别涉及智能光网络中有阻边界节点及有 阻边界节点间建立连接的方法。 背景技术 随着智能光网络技术的大规模的应用 ,传送网络的建设和发展已经从单 一的硬件传送技术发展为网管技术、 控制技术和硬件技术结合的综合型传送 技术。 借助智能光网络控制平面, 网络的可靠性不但得到了提高, 同时也能 够快速提供新的带宽业务如 OVPN ( Optical Virtual Private Network, 光虚拟 专网), BoD ( Bandwidth on demand, 带宽点播) 等, 给网络的运维带来效 率的提升和成本的降低。 但是随着业务种类越来越丰富 ,特别是分组业务所消耗的带宽比重越来 越高, 业务颗粒也越来越大。 原本为话音承载而设计的 SDH ( Synchronous Digital Hierarchy, 同步数字体系) /SONET ( Synchronous Optical Network, 同步光纤网)设备已经不能很好的满足未来应用的发展, 因此智能光网络从 SDH网络向 OTN ( Optical Transport Network, 光传送网)的;寅进呈不可阻 4当 的趋势。 大颗粒业务的传送对 WDM ( wavelength division multiplexing, 波分复 用)节点的业务疏导能力提出挑战。近年来 , ROADM ( Reconfigurable Optical Add Drop Multiplexer,可重构型光分插复用器)技术已经获得了一定的突破, WSS ( Wavelength Selective Switch, 波长选择开关) 等基于 MEMS ( Micro Electromechanical System, 啟电子机械系统) 的技术解决了光波长的可重配 问题,从而在一定程度上,能够实现光波长的灵活上下和穿通。并且 ROADM 在将信号从一个 网 络向 另 一个 网 络传输时不需要经过 OEO ( Optical-Electrical-Optical, 光-电 -光) 转发, 可以消除光电光转换的成本。 业界多个厂家已推出具备光层可重配特性的 WDM 系统。 此外, 鉴于 OTN 对波分系统在节点的定义、 端到端管理方面均具备优势, 因而 OTN也开始 出现在商用传输设备上。随之而来的就是对波长 /子波长动态化的控制要求 —正: ¾口 ASON ( Automatically Switched Optical Network, 自动交换光网络 )
之于 SDH/SONET的 ADM ( Add/Drop Multiplexer, 分插复用器)。 但是正是因为 ROADM不需要经过 OEO转发, 因此只能重新指配波长 的方向, 而不能进行波长变换, 因此在波长交换时不是完全无阻塞的, 虽然 可以在 ROADM中引入 OEO转换的设备从而实现波长的变换, 但是受限于 OEO设备的成本和变换容量, 仍然无法实现完全无阻塞的波长交换。 对于上述的有阻信息, 当前主要有两种处理方法。 第一种方法是通过扩 展路由泛洪信息将有阻信息通知到各个节点, 在路由计算时带入有阻信息进 行计算, 这样保证计算出的路由在每个节点是可交换的。 这种方法计算出的 路由建立连接的成功率高, 但是需要增加大量的泛洪信息。 第二种方法不将 有阻信息进行泛洪,但是在连接建立时的正向信令过程中不预留具体的资源, 而是只给定一个可用的资源范围 , 最后在目的节点才艮据之前给定的范围选定 最后所要使用的资源。 这种方法不需要增加额外的泛洪信息, 但是计算出的 路由建立连接的成功率氐。 发明内容 本发明提供一种有阻边界节点及有阻边界节点间建立连接的方法,通过 将路由域的边界节点的边界子网点的有阻信息与路由域内的子网点的有阻信 息分开处理, 从而在保证连接建立的成功率的前提下有效的减少有阻信息的 泛洪消息。 本发明所述技术方案如下: 一种有阻边界节点, 包括连接控制器、 链路资源管理器及路由控制器, 其巾, 连接控制器 , 用于在收到连接请求消息后 , 向链路资源管理器发送有阻 信息查询请求, 并对查询到的本端的有阻信息进行验证, 在验证通过后查询 出口边界节点的有阻信息, 并以本端的有阻信息和出口边界节点的有阻信息 作为查询参数向路由控制器发送路由查询请求; 链路资源管理器, 用于响应连接控制器的有阻信息查询请求, 将本端的 有阻信息反馈给连接控制器; 路由控制器, 用于响应路由查询请求, 提供用于建立连接的路由信息。
优选地 , 所述连接控制器进一步用于在收到本端的有阻信息更新消息 后, 对本端存储的有阻信息予以更新。 优选地,所述连接控制器进一步用于在收到远端边界节点的有阻信息更 新消息后,按照该消息对本端存储的所述出口边界节点的有阻信息进行更新。 一种有阻边界节点间建立连接的方法, 包括步骤:
Α、 入口边界节点收到连接建立请求消息后查询并验证入口子网点在入 口子网内的有阻信息 ,当验证成功后发送有阻信息查询请求到出口边界节点;
B、 所述出口边界节点收到有阻信息查询请求后查询并-险证出口子网点 在出口子网内的有阻信息, 当验证成功后将该有阻信息返回给所述入口边界 节点;
C、 所述入口边界节点以入口子网点和出口子网点的有阻信息作为查询 参数查询路由,并在查询路由成功后向所述出口边界节点发送连接请求消息;
D、 所述入口边界节点收到所述出口边界节点返回的连接确认消息后连 接建立完成。 优选地, 所述步骤 A中, 所述入口边界节点收到连接建立请求消息后, 对该消息进行 -险证 , 若-险证通过 , 则查询并-险证入口子网点在入口子网内的 有阻信息, 否则, 返回连接请求失败响应, 流程结束。 优选地, 所述步骤 C 中, 所述出口边界节点收到连接请求消息后打开 有阻信息监测; 所述步骤 D中, 所述入口边界节点收到连接确认消息后打开 有阻信息监测。 优选地, 在连接建立后, 所述入口边界节点监测到本端入口子网点的有 阻信息发生变化时 , 对本地存储的本端入口子网点的有阻信息予以更新「 优选地, 在连接建立后, 所述出口边界节点监测到本端出口子网点的有 阻信息发生变化时, 向所述入口边界节点发送有阻信息更新消息, 所述入口 边界节点按照该消息对本地存储的所述出口边界节点的出口子网点的有阻信 息进行更新。
优选地 , 所述入口边界节点收到连接释放消息后, 关闭本端的有阻信息 监测, 向所述出口边界节点发送连接释放请求; 所述出口边界节点收到所述 连接释放请求后关闭本端的有阻信息监测 , 在处理完该连接释放请求后向所 述入口边界节点发送连接释放确认消息。 与现有技术相比较,本发明将路由域的边界节点的边界子网点的有阻信 息与路由域内的子网点的有阻信息分开处理, 这样在保证连接建立的成功率 的前提下有效的减少有阻信息的泛洪消息。 相对于现有技术所述的第一种方 法, 本发明能够有效的减少无效的泛洪信息, 并且有相同连接建立成功率, 而相对于现有技术所述的第二种方法 ,本发明能显著提高连接建立的成功率。 附图说明 图 1为本发明中有阻边界节点的结构示意图; 图 2为本发明中有阻边界节点间建立连接的方法的流程图; 图 3为本发明所述实例的网络拓朴示意图; 图 4为本发明所述实例中边界节点在有阻情况下建立连接的流程图; 图 5为本发明所述实例中有阻边界节点释放连接的流程图; 图 6为本发明所述实例中 Α节点有阻信息变化时更新本端有阻信息的 流程图; 图 7为本发明所述实例中 C节点有阻信息变化时更新 A节点存储的有 阻信息的流程图。 具体实施方式 本发明将路由域的边界节点的边界子网点的有阻信息与路由域内的子 网点的有阻信息分开处理, 这样在保证连接建立的成功率的前提下有效的减 少有阻信息的泛洪消息。 由于与路由域内的子网点的有阻信息相似,所以本发明中边界节点的边 界子网点的有阻信息可以使用相同的数据模型 , 但是和路由域内的子网点的 有阻信息不同的是, 边界节点的边界子网点的有阻信息只有在指定了该边界
节点的边界子网点作为连接的入口 /出口子网点时在路由计算中才会使用, 而 对于其它连接, 该信息无效。 并且在连接建立后, 边界节点的入口 /出口子网 点的有阻信息只与使用该子网点的连接有关。 下面将结合各个附图对本发明的具体实现予以说明。 智能光网络中的边界节点的结构主要包括连接控制器( CC )、 路由控制 器 (RC ) 和链路资源管理器 (LRM ), 各组成部分的作用如下: 连接控制器, 负责协调链路资源管理器、路由控制器以及对等和从属的 连接控制器, 来管理和监控连接的建立、释放以及修改现有连接的连接参数。 路由控制器, 负责响应来自连接控制器的请求, 提供用于建立连接的路 由信息, 该信息可以是端到端的(例如源路由), 也可以是逐跳的; 以及响应 用于网络管理的拓朴信息 (子网点及其抽象)请求。 链路资源管理器, 负责管理子网点池( SNPP ) 链路, 包括指配和去指 配子网点链路连接, 并提供拓朴和状态信息。 由于子网点池( SNPP )链路可 以是公共或私有的 , 所以链路资源管理器也可以是公共的或与某个虚拟专用 网络 ( VPN ) 目关联。 请参阅图 1 , 该图为本发明中有阻边界节点的结构示意图, 本发明所述 有阻边界节点包括连接控制器、 链路资源管理器及路由控制器, 其中, 连接控制器 20, 用于在收到连接请求消息后 , 向链路资源管理器 21发 送有阻信息查询请求, 并对查询到的本端的有阻信息进行验证, 在验证通过 后查询出口边界节点的有阻信息, 并以本端的有阻信息和出口边界节点的有 阻信息作为查询参数向路由控制器 22发送路由查询请求; 进一步地,所述连接控制器 20用于在收到本端的有阻信息更新消息后, 对本端存储的有阻信息予以更新; 以及在收到远端边界节点的有阻信息更新 消息后 , 按照该消息对本端存储的所述出口边界节点的有阻信息进行更新。 链路资源管理器 21 , 用于响应连接控制器 20的有阻信息查询请求, 将 本端的有阻信息反馈给连接控制器 20。 路由控制器 22, 用于响应路由查询请求, 提供用于建立连接的路由信 息。
请参阅图 2 , 该图为本发明中有阻边界节点间建立连接的方法的流程 图, 其主要实现过程为: 步骤 10、 入口边界节点的连接控制器收到连接建立请求消息后验证该 消息; 步骤 11、 当验证成功后, 入口边界节点的连接控制器向本地的链路资 源管理器查询并验证入口子网点在入口子网内的有阻信息; 步骤 12、 当-险证成功后, 入口边界节点的连接控制器发送有阻信息查 询请求消息到出口边界节点的连接控制器; 步骤 13、 出口边界节点的连接控制器收到有阻信息查询请求后向本地 的链路资源管理器查询并-险证出口子网点在出口子网内的有阻信息; 步骤 14、 当验证成功后, 出口边界节点的连接控制器向入口边界节点 的连接控制器发送有阻信息查询响应, 其中携带有通过验证的出口子网点在 出口子网内的有阻信息; 步骤 15、 入口边界节点的连接控制器向本地的路由控制器发送路由查 询请求 , 查询参数为入口子网点的有阻信息和出口子网点的有阻信息; 步骤 16、 当查询路由成功后, 入口边界节点的连接控制器向下游发送 连接请求消息继续连接建立的处理过程; 步骤 17、 出口边界节点的连接控制器接收并处理完连接请求消息后通 知本地的链路资源管理器打开有阻信息检测, 然后向入口边界节点发送连接 确认消息; 步骤 18、 入口边界节点的连接控制器收到下游返回的连接确认消息后 打开有阻信息监测, 连接建立完成。 在连接建立后,当所述入口边界节点的链路资源管理器监测到本端入口 子网点的有阻信息发生变化时会通知本地的连接控制器 , 由该连接控制器对 本地存储的本端入口子网点的有阻信息予以更新; 当所述出口边界节点的链 路资源管理器监测到本端出口子网点的有阻信息发生变化时会通知本地的连 接控制器, 出口边界节点的连接控制器向所述入口边界节点的连接控制器发 送有阻信息更新消息, 所述入口边界节点的连接控制器按照该消息对本地存
储的所述出口边界节点的出口子网点的有阻信息进行更新。 在连接建立后, 当所述入口边界节点的连接控制器收到连接释放消息 后, 对该连接释放消息进行验证, 若验证通过, 则通知本地的链路资源管理 器关闭有阻信息监测, 然后向所述出口边界节点的连接控制器发送连接释放 请求, 所述出口边界节点的连接控制器收到所述连接释放请求后通知本地的 链路资源管理器关闭有阻信息监测, 在处理完该连接释放请求后向所述入口 边界节点的连接控制器发送连接释放确认消息。 下面通过一具体实例对本发明的具体实现予以进一步详细的说明。 请参阅图 3 , 该图为本发明所述实例的网络拓朴示意图, 该图表示一个 路由域, 其中 A节点和 C节点为边界节点, 而 B节点为中间节点。 连接建 立方向为 A->B->C。 图 4 所示为本发明所述实例中边界节点在有阻情况下建立连接的流程 图, 主要包括以下步骤: 步骤 301、 A节点连接控制器收到连接请求消息; 步骤 302、 A节点连接控制器验证连接请求消息, 主要验证连接请求条 件是否正确, 如果验证失败执行步骤 303 , 否则执行步骤 304; 步骤 303、 A节点连接控制器返回连接请求失败响应, 本流程结束; 步骤 304、 A节点连接控制器向 A节点链路资源管理器查询入口子网点 的有阻信息 ,主要是入口子网点和 A节点在路由域内其它子网点的可交换性 , 当查询失败时, 即不存在入口子网点或没有与入口子网点可交换的路由域内 其它子网点时, 执行步骤 303 , 否则执行步骤 305; 步骤 305、 A节点连接控制器向 C节点发送有阻信息查询请求消息, 用 于查询 C节点出口子网点的有阻信息; 步骤 306、 C节点连接控制器接收并验证有阻信息查询请求消息 , 主要 是验证查询请求条件是否正确, 如果验证失败执行步骤 307, 否则执行步骤
步骤 307、 C节点连接控制器向 A节点连接控制器发送有阻信息查询请 求失败响应; 步骤 308、 A节点连接控制器接收有阻信息查询请求失败响应后执行步 骤 303; 步骤 309、 C节点连接控制器向 C节点链路资源管理器查询出口子网点 的有阻信息, 当查询失败时, 执行步骤 307, 否则执行步骤 310; 步骤 310、 C节点连接控制器将出口子网点的有阻信息填入有阻信息查 询响应中, 并返回给 A节点连接控制器; 步骤 311、 A节点收到有阻信息查询响应后将 A节点入口子网点的有阻 信息和 C节点出口子网点的有阻信息作为查询条件向路由控制器查询路由信 息, 当查询失败时, 执行步骤 303 , 否则执行步骤 312; 步骤 312、 A节点连接控制器发送连接请求到下一跳 B节点, B节点接 收并处理连接请求消息, 然后将连接请求消息转发到下一跳 C节点; 步骤 313、 C节点连接控制器接收并处理完连接请求后通知 C节点链路 资源管理器打开有阻信息监测, 然后向 B节点发送连接响应消息, B节点接 收并处理连接响应 , 然后转发连接响应到 A节点; 步骤 314、 A节点连接控制器接收并处理完连接响应后通知 A节点链路 资源管理器打开有阻信息监测; 步骤 315、 A节点发送连接确认, 本流程结束。 请参阅图 5 , 该图为本发明所述实例中有阻边界节点释放连接的流程 图, 主要包括以下步骤: 步骤 401、 A节点连接控制器收到连接释放消息; 步骤 402、 A节点连接控制器验证连接释放消息, 主要验证连接释放请 求条件是否正确 , 如果验证失败执行步骤 403 , 否则执行步骤 404; 步骤 403、 A节点连接控制器返回连接释放请求失败响应,本流程结束;
步骤 404、 A节点连接控制器向 A节点链路资源管理器通知关闭有阻信 息监测; 步骤 405、 A节点连接控制器发送连接释放请求到下一跳 B节点, B节 点接收并处理连接释放请求消息 , 然后将连接释放请求消息转发到连接下一 跳 C节点; 步骤 406、 C节点连接控制器收到连接释放请求后通知 C节点链路资源 管理器关闭有阻信息监测 , 并且处理连接释放请求 , 处理完发送连接释放响 应消息到 B节点, B节点接收并处理连接释放响应, 然后转发连接释放响应 到 A节点; 步骤 407、 A节点连接控制器接收并处理完连接释放确认后发送连接释 放确认, 本流程结束。 请参阅图 6,该图为本发明所述实例中 A节点有阻信息变化时更新本端 有阻信息的流程图, 主要包括以下步骤: 步骤 501、 A节点链路资源管理器检测到本端入口子网点有阻信息变化 时, 比如某个出口子网点与入口子网点的连纤故障, A节点链路资源管理器 通知 A节点连接控制器 A节点入口子网点有阻信息更新; 步骤 502、 A节点连接控制器收到 A节点入口子网点有阻信息更新后, 更新本地存储的 A节点入口子网点有阻信息, 本流程结束。 请参阅图 7 , 该图为本发明所述实例中 C 节点有阻信息变化时更新 A 节点存储的有阻信息的流程图, 主要包括以下步骤: 步骤 601、 C节点链路资源管理器检测到本端出口子网点有阻信息变化 时, C节点链路资源管理器通知 C节点连接控制器 C节点入口子网点有阻信 息更新; 步骤 602、 C节点连接控制器发送 C节点出口子网点有阻信息更新消息 到 A节点; 步骤 603、 A节点连接控制器收到 C节点出口子网点有阻信息更新消息 后, 更新本地存储的 C节点出口子网点有阻信息, 本流程结束。
显然,本领域的技术人员可以对本发明进行各种改动和变型而不脱离本 发明的精神和范围。 这样, 倘若本发明的这些修改和变型属于本发明权利要 求及其等同技术的范围之内, 则本发明也意图包含这些改动和变型在内。
Claims
1. 一种有阻边界节点, 其特征在于, 包括连接控制器、 链路资源管理器及 路由控制器, 其中, 连接控制器, 用于在收到连接请求消息后, 向所述链路资源管理 器发送有阻信息查询请求 , 并对查询到的本端的有阻信息进行验证, 在 -险证通过后查询出口边界节点的有阻信息 , 并以本端的有阻信息和 出口边界节点的有阻信息作为查询参数向所述路由控制器发送路由查 询请求;
链路资源管理器, 用于响应所述连接控制器的有阻信息查询请 求 , 将本端的有阻信息反馈给所述连接控制器;
路由控制器, 用于响应所述路由查询请求, 提供用于建立连接的 路由信息。
2. 如权利要求 1所述的有阻边界节点, 其特征在于, 所述连接控制器进一 步用于在收到本端的有阻信息更新消息后 , 对本端存储的有阻信息予以 更新。
3. 如权利要求 1所述的有阻边界节点, 其特征在于, 所述连接控制器进一 步用于在收到远端边界节点的有阻信息更新消息后, 按照该消息对本端 存储的所述出口边界节点的有阻信息进行更新。
4. 一种有阻边界节点间建立连接的方法, 其特征在于, 包括步骤:
A、 入口边界节点收到连接建立请求消息后查询并验证入口子网 点的有阻信息, 当验证成功后发送有阻信息查询请求到出口边界节点;
B、 所述出口边界节点收到所述有阻信息查询请求后查询并 -险证 出口子网点的有阻信息, 当验证成功后将该有阻信息返回给所述入口 边界节点;
C、 所述入口边界节点以入口子网点和出口子网点的有阻信息作 为查询参数查询路由, 并在查询路由成功后向所述出口边界节点发送 连接请求消息;
D、 所述入口边界节点收到所述出口边界节点返回的连接确认消 息后连接建立完成。 如权利要求 4所述的方法 , 其特征在于 , 所述步骤 A中 , 所述入口边界 节点收到连接建立请求消息后, 对该消息进行验证, 若验证通过, 则查 询并验证入口子网点的有阻信息, 否则, 返回连接请求失败响应, 流程 结束。 如权利要求 4所述的方法 , 其特征在于 , 所述步骤 C中,所述出口边界节点收到连接请求消息后打开有阻 信息监测;
所述步骤 D中,所述入口边界节点收到连接确认消息后打开有阻 信息监测。 如权利要求 6所述的方法 , 其特征在于 , 在连接建立后 , 所述入口边界 节点监测到本端入口子网点的有阻信息发生变化时 , 对本端存储的入口 子网点的有阻信息予以更新。 如权利要求 6所述的方法, 其特征在于, 在连接建立后, 所述出口边界 节点监测到本端出口子网点的有阻信息发生变化时, 向所述入口边界节 点发送有阻信息更新消息, 所述入口边界节点按照该消息对本端存储的 所述出口边界节点的出口子网点的有阻信息进行更新。 如权利要求 6所述的方法, 其特征在于, 所述入口边界节点收到连接释 放消息后, 关闭本端的有阻信息监测, 向所述出口边界节点发送连接释 放请求; 所述出口边界节点收到所述连接释放请求后关闭本端的有阻信 息监测, 在处理完该连接释放请求后向所述入口边界节点发送连接释 放确认消息。
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US13/063,591 US8832282B2 (en) | 2008-09-12 | 2009-09-07 | Barrier boundary node and method for establishing connection between barrier boundary nodes |
| ES09812652.7T ES2564526T3 (es) | 2008-09-12 | 2009-09-07 | Nodo frontera de barrera y procedimiento para establecer una conexión entre nodos frontera de barrera |
| EP09812652.7A EP2328307B1 (en) | 2008-09-12 | 2009-09-07 | Barrier boundary node and method for establishing connection between barrier bound ary nodes |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810211958XA CN101360349B (zh) | 2008-09-12 | 2008-09-12 | 一种有阻边界节点及有阻边界节点间建立连接的方法 |
| CN200810211958.X | 2008-09-12 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2010028586A1 true WO2010028586A1 (zh) | 2010-03-18 |
Family
ID=40332661
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2009/073795 Ceased WO2010028586A1 (zh) | 2008-09-12 | 2009-09-07 | 一种有阻边界节点及有阻边界节点间建立连接的方法 |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US8832282B2 (zh) |
| EP (1) | EP2328307B1 (zh) |
| CN (1) | CN101360349B (zh) |
| ES (1) | ES2564526T3 (zh) |
| WO (1) | WO2010028586A1 (zh) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101360349B (zh) * | 2008-09-12 | 2011-01-19 | 中兴通讯股份有限公司 | 一种有阻边界节点及有阻边界节点间建立连接的方法 |
| CN102801602B (zh) * | 2011-05-26 | 2017-09-22 | 中兴通讯股份有限公司 | 一种实现内部链路洪泛的方法及装置 |
| WO2014186986A1 (zh) * | 2013-05-24 | 2014-11-27 | 华为技术有限公司 | 流转发方法、设备及系统 |
| US10476545B2 (en) * | 2015-09-25 | 2019-11-12 | Intel Corporation | Communication between integrated circuit packages using a millimeter-wave wireless radio fabric |
| CN112583622B (zh) * | 2019-09-30 | 2023-09-26 | 中兴通讯股份有限公司 | 故障事件信息的上报方法及系统 |
| CN117472049B (zh) * | 2023-10-25 | 2024-05-07 | 山东大学 | 用于运动装置的控制方法、系统、存储介质及运动装置 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007019727A1 (en) * | 2005-08-15 | 2007-02-22 | Zte Corporation | A complex control node in the automatic switched transport networks and the control method thereof |
| CN101060420A (zh) * | 2006-04-21 | 2007-10-24 | 中兴通讯股份有限公司 | 自适应光传送网连接性能优化方法及设备 |
| CN101360349A (zh) * | 2008-09-12 | 2009-02-04 | 中兴通讯股份有限公司 | 一种有阻边界节点及有阻边界节点间建立连接的方法 |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6801496B1 (en) * | 1999-01-15 | 2004-10-05 | Cisco Technology, Inc. | Network addressing scheme for reducing protocol overhead in an optical network |
| US7215644B2 (en) * | 2003-03-19 | 2007-05-08 | Alcatel Lucent | Inter-domain constraint-based shortest path first technique for supporting hierarchical routing in interconnected multi-domain optical transport networks |
| CN1277375C (zh) * | 2003-07-31 | 2006-09-27 | 华为技术有限公司 | 一种光网络中永久连接和交换连接之间的转换方法 |
| CN100417117C (zh) | 2005-06-15 | 2008-09-03 | 华为技术有限公司 | 自动交换光网络中节点可达性的识别方法 |
| CN1859369B (zh) | 2005-10-09 | 2010-07-14 | 华为技术有限公司 | 实现网络连接服务建立的方法及装置 |
-
2008
- 2008-09-12 CN CN200810211958XA patent/CN101360349B/zh not_active Expired - Fee Related
-
2009
- 2009-09-07 WO PCT/CN2009/073795 patent/WO2010028586A1/zh not_active Ceased
- 2009-09-07 US US13/063,591 patent/US8832282B2/en not_active Expired - Fee Related
- 2009-09-07 ES ES09812652.7T patent/ES2564526T3/es active Active
- 2009-09-07 EP EP09812652.7A patent/EP2328307B1/en not_active Not-in-force
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007019727A1 (en) * | 2005-08-15 | 2007-02-22 | Zte Corporation | A complex control node in the automatic switched transport networks and the control method thereof |
| CN101060420A (zh) * | 2006-04-21 | 2007-10-24 | 中兴通讯股份有限公司 | 自适应光传送网连接性能优化方法及设备 |
| CN101360349A (zh) * | 2008-09-12 | 2009-02-04 | 中兴通讯股份有限公司 | 一种有阻边界节点及有阻边界节点间建立连接的方法 |
Non-Patent Citations (1)
| Title |
|---|
| See also references of EP2328307A4 * |
Also Published As
| Publication number | Publication date |
|---|---|
| EP2328307B1 (en) | 2016-01-06 |
| EP2328307A1 (en) | 2011-06-01 |
| EP2328307A4 (en) | 2014-05-07 |
| US8832282B2 (en) | 2014-09-09 |
| ES2564526T3 (es) | 2016-03-23 |
| CN101360349A (zh) | 2009-02-04 |
| US20110173336A1 (en) | 2011-07-14 |
| CN101360349B (zh) | 2011-01-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101447849B (zh) | 网络恢复 | |
| CA2311197C (en) | Enhanced dual counter rotating ring network control system | |
| US9800522B2 (en) | Make-before-break systems and methods decoupling a control plane from a data plane | |
| JP5163479B2 (ja) | パス切替え方法 | |
| US20070274224A1 (en) | Path setting method, node device, and monitoring/control device | |
| CN1866806B (zh) | 共享格状网恢复的实现方法 | |
| WO2004075494A1 (ja) | 通信ネットワークにおけるパスの故障救済を行うための装置及び方法 | |
| CN101360349B (zh) | 一种有阻边界节点及有阻边界节点间建立连接的方法 | |
| CN1833382A (zh) | 光网络网间互通结构及其连接配置方法 | |
| EP1887733B2 (en) | A method for processing network resource, a network unit in an intelligent optical network thereof | |
| US20080205262A1 (en) | Node controller and node system | |
| JP2008099295A (ja) | 接続変更要求を拒絶するシステム及び方法 | |
| CN1744479B (zh) | 传输网络中设置备份路径的方法以及用于传输网络的网元 | |
| CN101321115B (zh) | 一种业务路径建立的方法和系统以及节点设备 | |
| CN1981463A (zh) | 一种光网络中业务连接建立和业务恢复保护方法 | |
| CN100373866C (zh) | 跨越多域连接的网络故障恢复的方法 | |
| JP2004524784A5 (zh) | ||
| JP3967954B2 (ja) | 光クロスコネクト網の障害回復方法 | |
| WO2011134240A1 (zh) | 一种解决资源分配冲突的方法及装置 | |
| WO2020118505A1 (zh) | 一种业务路径建立的方法、网络设备和系统 | |
| US9451342B2 (en) | Method and apparatus for managing link on multi-layer networks | |
| US8218968B2 (en) | System and method for discovering neighboring nodes | |
| KR101726264B1 (ko) | 이기종 패킷전달망간 연동을 위한 통합 네트워크 관리 시스템 및 그 방법 | |
| EP2395773B1 (en) | Method and apparatus of sub-network connection protection (sncp) service migration | |
| CN101133601A (zh) | 自动交换传送网络中的复杂控制节点及其控制方法 |
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: 09812652 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 13063591 Country of ref document: US |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2009812652 Country of ref document: EP |