SYSTEMS AND METHODS FOR SELECTION OF OPTIMAL ROUTING PARAMETERS FOR DWDM NETWORK SERVICES IN A CONTROL PLANE NETWORK

• US 20160037239A1
• Filed: 09/10/2014
• Published: 02/04/2016
• Est. Priority Date: 07/30/2014
• Status: Active Grant

• Current Assignee: Ciena Corporation
• Original Assignee: Ciena Corporation
• Inventors: CHHILLAR, Mohit, PRAKASH, Anurag, BISHT, Seemant, SRINIVASAN, Hari
• Granted Patent: US 9,485,550 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04J 14/0227 Operation, administration, maintenance or provisioning [OAMP] of WDM networks, e.g. media access, routing or wavelength allocation
• CPC Class Codes: H04J 14/0257 Wavelength assignment algorithms
• CPC Class Codes: H04J 14/0271 Impairment aware routing
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/12 Shortest path evaluation
• CPC Class Codes: H04L 45/26 Route discovery packet
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/64 using an overlay routing layer
• CPC Class Codes: H04Q 11/0003 Details
• CPC Class Codes: H04Q 11/0005 Switch and router aspects
• CPC Class Codes: H04Q 11/0062 Network aspects
• CPC Class Codes: H04Q 2011/0073 Provisions for forwarding or routing, e.g. lookup tables

Abstract

A method, in an intermediate node in a control plane network, includes receiving a setup message from an originating node, wherein the setup message is sent towards a terminating node on a computed path in the control plane network, and the setup message indicates associated Layer 0 attributes; validating the associated attributes/constraints based on locally available resources; and performing one of: forwarding the setup message on the path towards the terminating node when validation is successful; forwarding the setup message on the path towards the terminating node with updated information indicating a rejection cause and additional information when the validation is unsuccessful, but a modification of the Layer 0 attributes/constraints is possible; and forwarding a release message on the path back to the originating node with updated information indicating a rejection cause and additional information when the validation is unsuccessful and no modifications of the Layer 0 attributes/constraints are possible.

Claims

1. A method, in an intermediate node in a control plane network, for selecting optimal routing parameters for Dense Wave Division Multiplexing (DWDM) network services, the method comprising:

receiving a setup message from an originating node, wherein the setup message is sent towards a terminating node on a computed path in the control plane network, and the setup message indicates associated Layer 0 attributes/constraints;

validating the associated Layer 0 attributes/constraints based on locally available resources; and

performing one of;

forwarding the setup message on the path towards the terminating node when validation is successful;

forwarding the setup message on the path towards the terminating node with updated information indicating a rejection cause and additional information, when the validation is unsuccessful but a modification of the Layer 0 attributes/constraints is possible; and

transmitting a release message on the path back to the originating node with updated information indicating a rejection cause and additional information when the validation is unsuccessful and no modifications of the Layer 0 attributes/constraints are possible.

2. The method of claim 1, wherein the setup message is received at the terminating node after the intermediate node, and wherein the terminating node is configured to perform one of:

establishing a connection if the setup message was successfully validated at all nodes in the path; and

transmitting the release message on the path back to the originating node with rejection causes and additional information from all intermediate nodes included therein.

3. The method of claim 2, further comprising:

receiving the release message from the terminating node;

updating the additional information in the release message if required at the intermediate node; and

forwarding the release message on the path back to the originating node.

4. The method of claim 2, wherein the originating node is configured to receive the release message from the terminating node, extract and review the rejection causes and additional information included therein, and determine a retry on the path with revisions to the Layer 0 attributes/constraints based on the reviewing or a retry on an alternate path.

5. The method of claim 2, wherein the setup message is determined at the terminating node as successfully validated at all nodes in the path, based on an absence of information elements with the updated information in the setup message received at the terminating node.

6. The method of claim 1, wherein Layer 0 information is not flooded in the control plane network.

7. The method of claim 1, wherein the updated information, in the setup message or the release message, indicating the rejection cause and the additional information is a new information element.

8. The method of claim 1, wherein the Layer 0 attributes/constraints are any one or more of:

regenerator port assignments;

regenerator port assignments for a specific wavelength;

modem type;

drop port type being either colored or colorless; and

degree connectivity at each node.

9. The method of claim 1, wherein the validating comprises comparing the locally available resources, at the intermediate node, with the Layer 0 attributes/constraints in the setup message and any of the rejection causes and additional information;

and the method further comprises;

modifying the setup message based thereon or generating the release message based thereon.

10. The method of claim 1, wherein the validating comprises determining that a regenerator port is unavailable per the Layer 0 attributes/constraints at the intermediate node;

and the method further comprises;

updating the setup message with the rejection cause and the additional information indicates which regenerator ports are available at the intermediate node.

11. The method of claim 1, wherein the validating comprises determining that a regenerator port is unavailable per the Layer 0 attributes/constraints at the intermediate node based on wavelength contention for a specific wavelength;

and the method further comprises;

updating the setup message with the rejection cause and the additional information indicates which alternate wavelengths are available at the intermediate node.

12. The method of claim 1, wherein the validating comprises determining that a regenerator port is unavailable per the Layer 0 attributes/constraints at the intermediate node based on unavailability of a specific wavelength;

and the method further comprises;

updating the setup message with the rejection cause and the additional information indicates which alternate wavelengths are available at the intermediate node.

13. The method of claim 1, wherein the validating comprises determining a modem type mismatch per the Layer 0 attributes/constraints at the intermediate node;

and the method further comprises;

generating the release message based on the modem type mismatch with the updated information based thereon.

14. The method of claim 1, wherein the terminating node is configured to determine a mismatch between drop port type with the originating node;

and the terminating node is configured to transmit the release message based on available drop port types at the terminating node.

15. The method of claim 1, further comprising:

determining a partial connectivity block at the intermediate node; and

generating the release message based on the partial connectivity block with the updated information based thereon.

16. An intermediate node in a control plane network, for selecting optimal routing parameters for Dense Wave Division Multiplexing (DWDM) network services, the intermediate node comprising:

one or more ports communicatively coupled to one or more adjacent nodes; and

a controller communicatively coupled to the one or more ports, wherein the controller is configured to;

receive, via the one or more ports, a setup message from an originating node, wherein the setup message is sent towards a terminating node on a computed path in the control plane network, and the setup message indicates associated Layer 0 attributes/constraints;

validate the associated Layer 0 attributes/constraints based on locally available resources; and

perform one of;

forward the setup message on the path towards the terminating node when validation is successful;

forward the setup message on the path towards the terminating node with updated information indicating a rejection cause and additional information when the validation is unsuccessful, but a modification of the Layer 0 attributes/constraints is possible; and

transmit a release message on the path back to the originating node with updated information indicating a rejection cause and additional information when the validation is unsuccessful and no modifications of the Layer 0 attributes/constraints are possible.

17. The intermediate node of claim 16, wherein Layer 0 information is not flooded in the control plane network.

18. The intermediate node of claim 16, wherein the terminating node is configured to receive the setup message, and perform one of:

establish a connection if the setup message was successfully validated at all nodes in the path, and transmit the release message on the path back to the originating node with rejection causes and additional information from all intermediate nodes included therein.

19. The intermediate node of claim 18, wherein the controller is further configured to:

receive the release message from the terminating node;

update the additional information in the release message if required; and

forward the release message on the path back to the originating node.

20. A network, comprising:

a plurality of nodes interconnected by a plurality of links;

an originating node of the plurality of nodes configured to send a setup message to a terminating node of the plurality of nodes with associated Layer 0 attributes/constraints in the setup message; and

one or more intermediate nodes of the plurality of nodes, wherein the one or more intermediate nodes are in a path between the originating node and the terminating node, wherein the one or more intermediate nodes are configured to validate the associated Layer 0 attributes/constraints sequentially;

wherein, each of the one or more intermediate nodes is configured to perform one of;

forward the setup message on the path towards the terminating node when validation is successful;

forward the setup message on the path towards the terminating node with updated information indicating a rejection cause and additional information when the validation is unsuccessful, but a modification of the Layer 0 attributes/constraints is possible; and

transmit a release message on the path back to the originating node with updated information indicating a rejection cause and additional information when the validation is unsuccessful and no modifications of the Layer 0 attributes/constraints are possible.