Transport control server, transport control system, and backup path setting method

Patent metadata

Field	Value
Publication number	US-9325607-B2
Application number	US-201414462613-A
Country	US
Kind code	B2
Filing date	Aug 19, 2014
Priority date	Aug 14, 2009
Publication date	Apr 26, 2016
Grant date	Apr 26, 2016

Abstract

Transport control server (TCS) in a network system including a first backup path (FBP) with predetermined first bandwidth (PFB) secured or reserved between any node pair, second backup path (SBP) with predetermined second bandwidth (PSB) secured or reserved between any node pair, the FBP and SBP sharing a link, each node forwards data according to path setting information. The TCS including: a storage section storing, for each path, an identifier for each node through which the path passes; and a control processing section performing: upon switchover of first active path to FBP, judging whether PSB of SBP can be secured or reserved by the bandwidth of the shared link through which the FBP passes, by referring to the storage section; if not, identifying nodes through which the SBP passes, by referring to the storage section; and transmitting a setting change notification to delete the SBP to the identified nodes.

First claim

What is claimed is:

1. A path control server for controlling a plurality of nodes in communication with the path control server, the path control server comprising one or more processors programmed with logic configured to:
receive a notification from a first node of the plurality of nodes,
determine from the notification whether any of the plurality nodes in a third path are affected by the notification resulting in a path switch from a first path to a second path,
identify one or more of the plurality of nodes in the third path to be notified of a setting change to delete the third path resulting from the path switch, the third path being different from the first and second paths and sharing at least one link with the second path, and
notify the one or more of the plurality of nodes on the third path to perform the setting change to delete the third path.

2. The path control server of claim 1 , wherein the one or more nodes on the third path is joined to the at least one link shared with the second path, and wherein the third path and the second path share a bandwidth on the at least one link.

3. The path control server of claim 1 , wherein the path control server receives the notification from any of the plurality of nodes.

4. The path control server of claim 1 , wherein the notification comprises a notification of an occurrence of a failure in the first path.

5. The path control server of claim 4 , wherein the failure comprises a link failure or a node failure in the first path.

6. The path control server of claim 1 , wherein the first path is an active path, the second path is an alternative path for the active path, and the third path is another alternative path for another active path.

7. The path control server of claim 1 , further configured to determine whether the third path has a sufficient bandwidth.

8. The path control server of claim 1 , further configured to identify the first path and the second path based on the notification.

9. The path control server of claim 1 , wherein the notification comprises at least one of a label of an active path, a label of an alternative path, tag information of the active path, tag information of the alternative path, and an identifier of a node that switched the active path to the alternative path.

Assignees

• Hitachi Ltd

Inventors

• Yabusaki Hitoshi
• Matsubara Daisuke

Classifications

• H04L45/22 Primary

  Alternate routing · CPC title

• H04L45/02 Primary

  Topology update or discovery · CPC title

• H04L41/0654

  using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437) · CPC title

• H04L45/125

  based on throughput or bandwidth · CPC title

• H04L45/42

  Centralised routing · CPC title