Systems and methods for diverse connection signaling from disparate source nodes in distributed connection-oriented networks

1. A method in a network utilizing a distributed connection-oriented control plane, comprising:

signaling a first path for a first connection from a first source node;

storing call information for the first connection at any intermediate nodes in the first path;

signaling a second path for a second connection from a second source node, wherein the signaling comprises:

checking at any intermediate nodes in the second path if there is absolute route diversity between the first connection and the second connection responsive to a requirement therein; and

responsive to detecting a diversity violation at an intermediate node of the any intermediate nodes in the second path, signaling a crankback to the second source node with the call information for the first connection included therein;

failing to recompute the second path exclusive of the first path based on the call information responsive to the crankback due to no available diverse path;

recomputing the second path to be maximally diverse from the first path sharing as few nodes and/or links as possible with the first path; and

signaling the second path instructing the any intermediate nodes that it is not required to check for the node and/or link diversity.

2. The method of claim 1 , further comprising:

recomputing the second path exclusive of the first path based on the call information responsive to the crankback.

3. The method of claim 1 , further comprising:

checking at any intermediate nodes in the second path if there is nodal and/or link diversity based on the requirement, wherein the requirement is communicated in a setup message associated with the second connection.

4. The method of claim 1 , further comprising:

responsive to not detecting the diversity violation at the any intermediate nodes in the second path, establishing the second connection without requiring call coordination between the first connection and the second connection.

5. The method of claim 1 , wherein the first connection and the second connection comprise any of an Open-Open service, an Open-Close service, a Close-Open service, and a Close-Close service.

6. The method of claim 5 , wherein the first connection and the second connection comprise any of the Close-Open service and the Close-Close service, and the checking is not performed due to a lack of the requirement.

7. The method of claim 1 , wherein the distributed connection-oriented control plane comprises any of Automatically Switched Optical Network (ASON), Generalized Multi-Protocol Label Switching (GMPLS), Optical Signaling and Routing Protocol (OSRP), Private Network to Network Interface (PNNI).

8. The method of claim 1 , further comprising:

storing call information for the second connection at the any intermediate nodes in the second path, wherein the first connection and the second connection are part of N connections;

establishing the N connections as diverse therebetween with a maximum of N−1 crankbacks.

9. The method of claim 1 , wherein the call information comprises a Designated Transit List (DTL) or an Explicit Route Object (ERO).

10. The method of claim 1 , wherein the first connection and the second connection are part of a subnetwork connection protection (SNCP) with the first source node and the second source node being different.

11. The method of claim 1 , wherein the first connection and the second connection comprise any of a subnetwork connection (SNC), a subnetwork connection protection (SNCP), and a label switched path (LSP) computed by a source node and established by the distributed connection-oriented control plane.

12. The method of claim 1 , further comprising:

performing the signaling the first path or signaling the second path responsive to restoration from a failure or as part of connection maintenance.

13. A network utilizing a distributed connection-oriented control plane, comprising:

a plurality of nodes interconnected therebetween by a plurality of links, wherein the distributed connection-oriented control plane operates between the plurality of nodes;

wherein, responsive to control plane signaling for a new connection, any intermediate nodes of the plurality of nodes in a first path for the new connection store associated call information for the new connection;

wherein, responsive to control plane signaling for a subsequent connection after the new connection and a requirement for absolute route diversity with the new connection and any other connections, any intermediate nodes of the plurality of nodes in a second path for the subsequent connection check, during the control plane signaling for the subsequent connection, for the absolute route diversity based on stored call information;

wherein, responsive to a diversity violation at an intermediate node of the any intermediate nodes in the second path for the subsequent connection, during the check, a crankback is sent to a source node of the subsequent connection with relevant stored call information for the new connection included therein; and

wherein, responsive to failing to recompute the second path exclusive of the first path based on the call information responsive to the crankback due to no available diverse path, the second path is recomputed to be maximally diverse from the first path sharing as few nodes and/or links as possible with the first path; and the second path is signaled instructing the any intermediate nodes that it is not required to check for the node and/or link diversity.

14. The network of claim 13 , wherein the source node of the subsequent connection recomputes the second path for the subsequent connection exclusive of the relevant stored call information included therein responsive to the crankback.

15. The network of claim 13 , wherein, responsive to not detecting the diversity violation at the any intermediate nodes in the second path for the subsequent connection, the subsequent connection is established without requiring call coordination.

16. The network of claim 13 , wherein the new connection and the subsequent connection comprise any of an Open-Open service, an Open-Close service, a Close-Open service, and a Close-Close service.

17. The network of claim 16 , wherein the new connection and the subsequent connection comprise any of the Close-Open service and the Close-Close service, and the checking is not performed due to a lack of the requirement.

18. The network of claim 13 , wherein the distributed connection-oriented control plane comprises any of Automatically Switched Optical Network (ASON), Generalized Multi-Protocol Label Switching (GMPLS), Optical Signaling and Routing Protocol (OSRP), Private Network to Network Interface (PNNI);

wherein the call information comprises a Designated Transit List (DTL) or an Explicit Route Object (ERO); and

wherein the new connection and the subsequent connection comprise any of a subnetwork connection (SNC), a subnetwork connection protection (SNCP), and a label switched path (LSP) computed by a source node of the plurality of nodes and established by the distributed connection-oriented control plane.

19. A node, comprising:

a plurality of ports with switching therebetween; and

a controller operating a distributed connection-oriented control plane with a plurality of additional nodes in a network;

wherein if the node is a source node for a connection, the controller is configured to:

compute a path for the connection in the network;

signal the path with or without a requirement for absolute route diversity with another connection in the network;

receive a crankback with relevant call information of the another connection if an intermediate node detects a diversity violation responsive to the requirement for absolute route diversity; and

recompute the path exclusive the another connection based on the relevant call information;

wherein if the node is an intermediate node for the connection, the controller is configured to:

receive a setup message from a source node for the connection;

check if there is the requirement for absolute route diversity in the setup message; and

determine if there is the absolute route diversity by checking relevant stored call information, and responsive to a diversity violation, send a crankback to the source node with the relevant call information included therein, and responsive to no diversity violation, storing the relevant call information; and

wherein, responsive to failing to recompute the path exclusive of the first path based on the call information responsive to the crankback due to no available diverse path, the path is recomputed to be maximally diverse from the another connection sharing as few nodes and/or links as possible with the another connection; and the path is signaled instructing any intermediate nodes that it is not required to check for the node and/or link diversity.