Signaling protocol for rerouting ATM connections in PNNI environments

• US 6,272,139 B1
• Filed: 01/21/2000
• Issued: 08/07/2001
• Est. Priority Date: 12/29/1997
• Status: Expired due to Term

• Current Assignee: Ericsson AB (Telefonaktiebolaget LM Ericsson)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Soncodi, Adrian C.
• Primary Examiner(s): Olms, Douglas
• Assistant Examiner(s): Pizarro, Ricardo M.
• Application Number:
  US09/488,528
• Time in Patent Office: 564 Days
• Field of Search: 370/395, 370/396, 370/397, 370/398, 370/399, 370/351, 370/254, 370/229, 370/356, 370/355, 370/410, 370/390, 370/408
• US Class Current: 370/241.1
• CPC Class Codes: H04L 2012/5621 Virtual private network [VPN]; Private-network - network-interface (P-NNI)
• CPC Class Codes: H04L 2012/5623 Network design, dimensioning, topology or optimisation
• CPC Class Codes: H04L 2012/5627 Fault tolerance and recovery
• CPC Class Codes: H04L 2012/5631 Resource management and allocation
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/10 Routing in connection-oriented networks, e.g. X.25 or ATM
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/26 Route discovery packet
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/302 Route determination based on requested QoS
• CPC Class Codes: H04L 45/48 Routing tree calculation
• CPC Class Codes: H04Q 11/0478 Provisions for broadband connections

Abstract

A method in a connection based communication network for rerouting a call connection path coupling a calling and a called party. Rerouting is done within a peer group and may be performed in any peer group level along the connection path. The method allows individual segments within peer groups to be rerouted for a number of different reasons such as fault recovery, route optimization, bandwidth adjustment, and load balancing. The reroutable call paths are implemented by inserting rerouting information elements in the standard setup and connect messages used to create call paths in PNNI environments. These information elements permit both nonpreemptive rerouting, establishing a new call path before the old one is terminated and preemptive rerouting, establishing a new path after the old one is terminated. Additional features such as, preserving QoS metrics during rerouting and separately identifying different incarnations of segments along the same call path are also provided.

Claims

1. In a network having at least one peer group including a plurality of nodes, a method for managing calls between a set of nodes, the method comprising:

establishing a reroutable call path connecting a source node to a destination node, the reroutable call path traversing the set of nodes;

detecting an event associated with the reroutable call path;

generating a reincarnate request upon an occurrence of the event by inserting a rendezvous node address in a called party identifier IE associated with the reincarnate request;

determining a new call path connecting a new set of nodes in a peer group; and

establishing the new call path connecting the new set of nodes wherein the source node and the destination node remain connected.

2. The method of claim 1, wherein the step of establishing the call path includes the substeps of

receiving a reroutable call request from the source node identifying the destination node;

transmitting the reroutable call request to the destination node;

receiving a connect message in response to the reroutable call request; and

establishing the reroutable call path in response to the connect message.

3. The method of claim 1, wherein the detecting step includes the substep of

generating a reincarnate request upon an occurrence of the event.

4. The method of claim 3, wherein the event specifies a rerouting reason, and wherein the generating step includes the substep of

inserting the rerouting reason into the reincarnate request.

5. The method of claim 4, wherein the rerouting reason specifies a nonpreemptive rerouting reason, the method further comprises the step of

releasing the call path after establishing the new call path.

6. The method of claim 4, wherein the rerouting reason specifies a preemptive rerouting reason, the method further comprises the step of

releasing the call path before establishing the new call path.

7. The method of claim 3, wherein the reincarnate request includes a rerouting type, and wherein the step of generating the reincarnate request further includes the substep of

specifying the rerouting type as peer group-based rerouting.

8. The method of claim 7, wherein each peer group includes at least one level, wherein each level includes a set of border nodes defining a peer group segment path, and wherein the determining step includes the substeps of

calculating a route to a rendezvous node via the peer group segment path, wherein the rendezvous node is a peer group exit border node;

and

transmitting the reincarnate request from a rerouting node in the peer group to the rendezvous node via the route, wherein the rerouting node is a peer group entry border node.

9. The method of claim 8, wherein the substep of calculating includes the substep of

inserting, into the reincarnate request, an address stack specifying a nodal address and a level number for each node in the route to the rendezvous node, wherein the level number identifies the peer group level on which the node resides.

10. The method of claim 9, wherein the reincarnate request includes a called party identifier IE, and wherein the step of generating further includes the substep of

inserting a rendezvous node address in the called party identifier IE.

11. A communication network comprising:

a plurality of peer groups, each peer group including;

a first border node switch configured to detect a rerouting event and transmit a rerouting message upon the occurrence of the rerouting event;

a second border node switch coupled to the first border node switch via a reroutable call path and configured to return a connect message upon receiving the rerouting message; and

means for connecting said first border node switch to the second border node switch via a rerouted call path upon receiving the connect message at the first border node switch, wherein the rerouting event specifies a nonpreemptive rerouting reason, and wherein the means for connecting includes means for disconnecting the first border node switch from the second border node switch after connecting the first border node switch to the second border node switch via the rerouted call path.

12. The communication network in claim 11, wherein the reroutable call path traverses more that one peer group, wherein the connect message includes a metric preservation value and wherein the network further comprises:

means for distributing the metric preservation value to each peer group traversed by the reroutable call path.

13. The communication network of claim 12, each peer group further including a number of internal node switches, wherein the reroutable call path includes a first set of internal node switches, and wherein the means for connecting further includes

means for connection the first border switch to the second border switch via a second set of internal node switches.

14. The communication network of claim 13, wherein the first border node switch is a first ATM switch.

15. The communication network of claim 14, wherein the second border node is a second ATM switch.

16. A communication network comprising:

a plurality of peer groups, each peer group including;

a first border node switch configured to detect a rerouting event and transmit a rerouting message upon the occurrence of the rerouting event;

a second border node switch coupled to the first border node switch vial a reroutable call path and configured to return a connect message upon receiving the rerouting message; and

means for connecting first border node switch to the second border node switch via a rerouted call path upon receiving the connect message at the first border node switch, wherein the rerouting event specifies a preemptive rerouting reason, and wherein the means for connecting includes means for disconnecting the first border node switch from the second border node switch, before connecting the first border node switch to the second border node switch via the rerouted call path.

17. The communication network in claim 16, wherein the reroutable call path traverses more that one peer group, wherein the connect message includes a metric preservation value and wherein the network further comprises:

means for distributing the metric preservation value to each peer group traversed by the reroutable call path.

18. The communication network of claim 17, wherein each peer group further includes a number of internal node switches, wherein the reroutable call path includes a first set of internal node switches, and wherein the means for connecting further includes;

means for connecting the first border switch to the second border switch via a second set of internal node switches.

19. The communication network of claim 18, wherein the first border node switch is a first ATM switch.

20. The communication network of claim 19, wherein the second border node is a second ATM switch.

21. A switching device comprising:

a plurality of peer groups, each peer group including;

a first border node switch configured to detect a rerouting event and transmit a rerouting message upon the occurrence of the rerouting event;

a second border node switch coupled to the first border node switch via a reroutable call path and configured to return a connect message upon receiving the rerouting message; and

means for connecting first border node switch to the second border node switch via a rerouted call path upon receiving the connect message at the first border node switch, wherein the rerouting event specifies a nonpreemptive rerouting reason, and wherein the means for connecting includes means for disconnecting the first border node switch from the second border node switch, after connecting the first border node switch to the second border node switch via the rerouted call path.

22. The switching device in claim 21, wherein the reroutable call path traverses more that one peer group, wherein the connect message includes a metric preservation value and wherein the network further comprises:

means for distributing the metric preservation value to each peer group traversed by the reroutable call path.

23. The switching device of claim 22, wherein each peer group further includes a number of internal node switches, wherein the reroutable call path includes a first set of internal node switches, and wherein the means for connecting further includes;

means for connecting the first border switch to the second border switch via a second set of internal node switches.

24. The switching device of claim 23, wherein the first border node switch is a first ATM switch.

25. The switching device of claim 24, wherein the second border node is a second ATM switch.

26. A switching device comprising:

a plurality of peer groups, each peer group including;

a first border node switch configured to detect a rerouting event and transmit a rerouting message upon the occurrence of the rerouting event;

a second border node switch coupled to the first border node switch via a reroutable call path and configured to return a connect message upon receiving the rerouting message; and

means for connecting first border node switch to the second border node switch via a rerouted call path upon receiving the connect message at the first border node switch, wherein the rerouting event specifies a preemptive rerouting reason, and wherein the means for connecting includes means for disconnecting the first border node switch from the second border node switch, before connecting the first border node switch to the second border node switch via the rerouted call path.

27. The switching device of claim 26, wherein the reroutable call path traverses more that one peer group, wherein the connect message includes a metric preservation value and wherein the network further comprises:

means for distributing the metric preservation value to each peer group traversed by the reroutable call path.

28. The switching device of claim 27, wherein each peer group further includes a number of internal node switches, wherein the reroutable call path includes a first set of internal node switches, and wherein the means for connecting further includes;

means for connecting the first border switch to the second border switch via a second set of internal node switches.

29. The switching device of claim 28, wherein the first border node switch is a first ATM switch.

30. The switching device of claim 29, wherein the second border node is a second ATM switch.