WO2014077313A1 - 通信システム、制御装置、その制御方法及びプログラム - Google Patents
通信システム、制御装置、その制御方法及びプログラム Download PDFInfo
- Publication number
- WO2014077313A1 WO2014077313A1 PCT/JP2013/080778 JP2013080778W WO2014077313A1 WO 2014077313 A1 WO2014077313 A1 WO 2014077313A1 JP 2013080778 W JP2013080778 W JP 2013080778W WO 2014077313 A1 WO2014077313 A1 WO 2014077313A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- path
- control
- network
- nodes
- failure
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 65
- 238000000034 method Methods 0.000 title claims description 49
- 230000008859 change Effects 0.000 claims description 43
- 238000012545 processing Methods 0.000 claims description 35
- 230000008569 process Effects 0.000 claims description 23
- 238000012423 maintenance Methods 0.000 claims description 9
- 230000004044 response Effects 0.000 claims description 6
- 238000011084 recovery Methods 0.000 abstract description 55
- 238000010586 diagram Methods 0.000 description 26
- 230000009471 action Effects 0.000 description 16
- 238000012546 transfer Methods 0.000 description 7
- 238000006243 chemical reaction Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000004083 survival effect Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000004308 accommodation Effects 0.000 description 1
- 230000001174 ascending effect Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
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/28—Routing or path finding of packets in data switching networks using route fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
- H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/34—Signalling channels for network management communication
- H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
-
- 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/24—Multipath
-
- 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/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L41/065—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving logical or physical relationship, e.g. grouping and hierarchies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
Definitions
- the present invention is based on the priority claim of Japanese patent application: Japanese Patent Application No. 2012-252425 (filed on November 16, 2012), the entire contents of which are incorporated herein by reference. Shall.
- the present invention relates to a communication system, a control device, a control method thereof, and a program.
- the present invention relates to a communication system including a control device that centrally controls a network, a control device, a control method thereof, and a program.
- Patent Document 1 when GMPLS (Generalized Multi-Protocol Label Switching) is adopted as a control plane and the failure can be recovered only by the optical switch (data plane in Patent Document 1), the failure is recovered by switching the optical switch. Technology is disclosed. On the other hand, when the failure cannot be recovered only by the optical switch, the failure is recovered by controlling the GMPLS control plane.
- GMPLS Generalized Multi-Protocol Label Switching
- Patent Document 2 discloses a technique for preventing path disconnection of a data plane during data transfer when a failure occurs only in the control plane in a network in which the data plane and the control plane are configured by different media.
- Patent Document 3 discloses a technique for efficiently performing failure recovery at the time of multiple failures by distributed control.
- Patent Document 4 discloses a technique for acquiring highly reliable path state information by synchronizing a data plane and a control plane, and managing the data plane and the control plane in cooperation with each other.
- Acceleration of failure can be expected by performing failure recovery only on the data plane without depending on the control plane.
- control route control
- control route control
- control plane in Patent Document 1 is distributed control using GMPLS. Therefore, it takes time to identify the fault location as compared to the control plane by centralized control. Furthermore, even if a single failure can be handled, if the control plane is distributed control, the response to multiple failures becomes complicated, and as a result, reliable failure recovery may not be possible. Further, with the technology disclosed in Patent Document 1, since it is determined that failure recovery by the data plane is impossible, failure information is notified to the control plane, so failure recovery on the control plane is delayed.
- Patent Document 2 is a technology for preventing path disconnection in the data plane when a failure occurs in the control plane, and is irrelevant to failure recovery using the data plane and the control plane. Furthermore, since the technique disclosed in Patent Document 3 is a failure recovery method using distributed control as in Patent Document 1, it is complicated to deal with multiple failures. Furthermore, the technique disclosed in Patent Literature 4 links the data plane and the control plane to achieve highly reliable acquisition of route state information. That is, the technique disclosed in Patent Document 4 does not have a main purpose of failure recovery.
- the present invention provides a communication system, a control device, a control method thereof, and a communication system that contributes to properly using failure recovery by a plurality of nodes and failure recovery by a control device that controls the plurality of nodes.
- the purpose is to provide a program.
- a plurality of nodes each having an OAM (Operation Administration and Maintenance) function and a control device that controls the plurality of nodes are included, and each of the plurality of nodes includes the plurality of nodes.
- a state change notification including information related to a port affected by a failure occurring in a network including the nodes, and the control device transmits the state change notification and information regarding the configuration of the network; Based on the above, a communication system for determining whether or not to perform route control in the network is provided.
- a port affected by a failure that has occurred in a network composed of a plurality of nodes from at least one of a plurality of nodes having an OAM (Operation Administration and Maintenance) function a communication unit that receives a state change notification including information, a route control determination unit that determines whether or not to perform route control in the network, based on the state change notification and information on the configuration of the network; are provided.
- OAM Operaation Administration and Maintenance
- a port affected by a failure that has occurred in a network composed of a plurality of nodes from at least one of a plurality of nodes having an OAM (Operation Administration and Maintenance) function including: receiving a state change notification including information; and determining whether or not to perform route control in the network based on the state change notification and information on a configuration of the network.
- OAM Operaation Administration and Maintenance
- An apparatus control method is provided. This method is linked to a specific machine called a control device for controlling the network.
- At least one of nodes configuring a plurality of networks having an OAM (Operation Administration and Maintenance) function is affected by a failure occurring in the network configured by the plurality of nodes.
- OAM Operaation Administration and Maintenance
- a program for causing a computer that controls the control device to execute the process of determining the above can be recorded on a computer-readable storage medium.
- the storage medium may be non-transient such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, or the like.
- the present invention can also be embodied as a computer program product.
- a communication system a control device, a control method, and a program that contribute to properly using failure recovery by a plurality of nodes and failure recovery by a control device that controls the plurality of nodes.
- FIG. 6 is a diagram for explaining an operation when both an active path and a backup path are affected by a failure.
- FIG. 10 is a diagram for explaining an operation when a plurality of working paths are affected by a failure but a protection path is not shared. It is a figure which shows an example of the internal structure of the control apparatus 20a which concerns on 2nd Embodiment. It is a flowchart for demonstrating operation
- FIG. 10 is a diagram for explaining an operation when a plurality of working paths are affected by a failure but a protection path is not shared. It is a figure which shows an example of the internal structure of the control apparatus 20a which concerns on 2nd Embodiment. It is a flowchart for demonstrating operation
- FIG. 2 is a diagram illustrating an example of an internal configuration of an open flow switch 40.
- FIG. It is a flowchart for demonstrating operation
- the failure recovery by the data plane is, for example, failure recovery by a plurality of nodes having an OAM function.
- the failure recovery by the control plane is, for example, failure recovery in which the control device executes path control of a network constituted by a plurality of nodes.
- the data plane is composed of a plurality of nodes.
- a control plane is comprised with a control apparatus.
- the data plane may be regarded as a lower layer, and the control plane may be regarded as an upper layer with respect to the data plane (lower layer).
- the communication system shown in FIG. 1 includes a plurality of nodes 100 having an OAM function, and a control device 101 that controls the plurality of nodes 100.
- Each of the plurality of nodes 100 transmits, to the control device 101, a state change notification including information related to a port that has been affected by a failure that has occurred in a network including the plurality of nodes 100.
- the control device 101 determines whether or not to execute route control in the network based on the state change notification and information related to the network configuration.
- control device 101 determines that the route control by the control plane is not executed, the control device 101 does not perform any special operation. Rely on the data plane to recover from network failures. In other words, the control device 101 does not participate in the failure recovery operation when recovery from a failure by a data plane such as a single failure can be expected. As a result, the communication system shown in FIG. 1 can achieve quick failure recovery by the data plane.
- the control apparatus 101 determines that the path control by the control plane is to be executed, the failure recovery by the data plane such as multiple faults is expected by performing appropriate path control for the plurality of nodes 100. A failure that cannot be recovered can be reliably recovered.
- FIG. 2 is a diagram illustrating an example of a configuration in the communication system according to the first embodiment.
- a configuration including nodes 10-1 to 10-4 and a control device 20 that centrally controls the nodes 10-1 to 10-4 is shown.
- the data plane is a network composed of a plurality of nodes 10-1 to 10-4.
- the control plane is configured by the control device 20.
- the data plane may be regarded as a lower layer and the control plane as an upper layer with respect to the data plane (lower layer).
- the control device 20 sets a processing rule that defines processing of the received packet for the nodes 10-1 to 10-4.
- the nodes 10-1 to 10-4 perform packet processing (packet transfer) according to the processing rules set by the control device 20.
- a path is set between the nodes 10-1 to 10-4. More specifically, in FIG. 2, paths P01 and P02 are set, the path P01 is an active path (solid line in FIG. 2), and the path P02 is a standby path (dotted line in FIG. 2).
- the backup path P02 is used as a backup path when a failure occurs in the active path P01.
- the nodes 10-1 to 10-4 are referred to as “node 10” when it is not necessary to distinguish them.
- the node 10 When the node 10 detects a signal disconnection of communication, the node 10 transmits a state change notification to the control device 20.
- the control device 20 determines whether or not route control for recovering from a failure occurring in the network should be performed based on the state change notification transmitted by the node 10 and the topology information and path information held therein. Route control is performed according to Details of the status change notification, topology information, and path information will be described later.
- FIG. 3 is a diagram illustrating an example of the internal configuration of the control device 20.
- the control device 20 includes a network configuration management unit 21, a network configuration database (network configuration DB) 22, a path control determination unit 23, and a communication unit 24 that communicates with devices such as the node 10. .
- network configuration management unit 21 a network configuration management unit 21, a network configuration database (network configuration DB) 22, a path control determination unit 23, and a communication unit 24 that communicates with devices such as the node 10.
- the network configuration management unit 21 receives topology information and path information input from the network administrator via the communication unit 24.
- the network configuration management unit 21 registers the received topology information and path information in the network configuration DB 22.
- the control device 20 may communicate with the node 10 to collect topology information and path information, and register the collected topology information and path information in the network configuration DB 22.
- the route control determination unit 23 receives a state change notification from the node 10 via the communication unit 24. When receiving the state change notification, the route control determination unit 23 refers to the topology information and path information stored in the network configuration DB 22. The route control determination unit 23 determines whether route control for recovering from a failure is necessary (whether route control is executed) based on the state change notification, topology information, and path information.
- the path control determination unit 23 determines whether the detour path is determined by a component (not shown) or the like. Instructs the determination of a detour route.
- the route control determination unit 23 notifies the network administrator that the route control for recovering the failure is necessary using the communication unit 24 or the like. Upon receiving the notification, the network administrator sets a path necessary for recovering the failure in the node 10.
- the control device 20 may communicate with the node 10 to collect topology information and path information, and register the collected topology information and path information in the network configuration DB 22.
- each unit (processing means) of the control device 20 shown in FIG. 3 can be realized by a computer program that causes a computer constituting these devices to execute each process described later using its hardware.
- the state change notification includes information regarding the port where the state change has occurred in the node 10. For example, when a link failure occurs in the node 10, information regarding the port corresponding to the link where the failure has occurred is included in the state change notification.
- the topology information is information related to the topology (connection form) of the network to be controlled by the control device 20.
- the topology information includes information regarding the ports connecting the nodes 10.
- FIG. 4 is a diagram showing an example of topology information.
- the description of the control device 20 is omitted when illustrating the topology of the network.
- the topology of the network to be controlled by the control device 20 is as shown in FIG.
- FIG. 4A the numbers given in the vicinity of the solid lines connecting the nodes 10-1 to 10-4 clearly indicate the connection ports at the nodes.
- Information that summarizes the topology shown in FIG. 4A is topology information
- FIG. 4B is an example of topology information.
- the path information is information relating to a network path that is controlled by the control device 20.
- the path information includes information on the working path and the backup path. More specifically, information such as a node through which each path passes and to which working path the backup path is associated is included.
- FIG. 5 is a diagram illustrating an example of path information.
- the path P01 is an active path that passes through the node 10-1 and the node 10-4.
- the path P02 is a backup path that passes through the nodes 10-1, 10-2, and 10-4. Information obtained by collecting these pieces of information is path information, and FIG. 5B is an example of path information.
- the backup path of the path P01 which is the active path is recognized as the path P02.
- FIG. 6 is an exemplification, and the operation of the communication system according to the present embodiment is not limited to the flowchart of FIG.
- FIG. 6 is a flowchart for explaining the operation of the communication system according to the first embodiment.
- step S01 the path control determination unit 23 of the control device 20 receives the state change notification via the communication unit 24.
- step S02 the route control determination unit 23 determines which path has an influence from the failure that has occurred in the network based on the information about the port that has undergone the state change obtained from the received state change notification, the topology information, and the path information. Identify if you received it.
- step S03 the path control determination unit 23 identifies the affected path, and then confirms the number of affected paths. If the number of affected paths is one or less, the processing in FIG. (Step S03, Yes branch). If the number of affected paths is one or less, the control device 20 does not take any special action regardless of whether the path is an active path or a backup path. In other words, if there is one affected path and that path is a working path, the OAM function of the node 10 works to use the backup path, and the node 10 itself recovers from the failure. I do. On the other hand, if there is one affected path and the path is a backup path, the working path is not affected, and the link is maintained.
- FIG. 7 is a diagram for explaining the operation when there is one path affected by the failure.
- the nodes 10-1 and 10-4 transmit a state change notification to the control device 20.
- the route control determination unit 23 recognizes from the state change notification that a state change has occurred in the port 2 of the node 10-1 and the port 2 of the node 10-4.
- the path control determination unit 23 refers to the information related to the port 2 of the node 10-1 and the port 2 of the node 10-4 in the topology information, so that a failure occurs in the link between the nodes 10-1 and 10-4. Recognize that Further, the route control determination unit 23 identifies the affected path from the link failure position (nodes 10-1 and 10-4 in the example of FIG. 7) and the path information.
- the path P01 which is the active path is a path affected by the failure. Since only the working path is affected by the failure, the failure can be recovered by the OAM function in the data plane. That is, in the case of a single failure, rapid failure recovery independent of the control plane is achieved.
- step S03 When there are two or more paths affected by the failure (step S03, No branch), the processes of steps S04 to S07 are executed. That is, when multiple failures occur in the network, the processes of steps S04 to S07 may be executed.
- step S04 in FIG. 6 the route control determination unit 23 determines whether or not both the active path and the backup path associated with the active path are affected by the failure. If both the active path and the backup path are affected by the failure (step S04, Yes branch), the path control determination unit 23 determines that the path control is necessary (determines that the path control is to be executed). ), Path control is performed (step S06).
- FIG. 8 is a diagram for explaining the operation when both the active path and the backup path are affected by the failure. In FIG. 8, it is assumed that a failure has occurred not only in the link between the nodes 10-1 and 10-4 but also in the link between the nodes 10-2 and 10-4.
- the path control determination unit 23 determines that the port 10 of the node 10-1, the port 2 of the node 10-2, the node 10- Recognize that a state change has occurred for each of the four ports 1 and 2.
- the path control determining unit 23 refers to the information regarding each port in the topology information, and a failure occurs in the link between the nodes 10-1 and 10-4 and between the nodes 10-2 and 10-4. Recognize that Further, the route control determination unit 23 identifies the affected path from the link failure position (nodes 10-1, 10-2, and 10-4 in the example of FIG. 8) and the path information.
- the path P01 that is the active path and the path P02 that is the backup path associated with the path P01 are the paths affected by the failure. Since both the active path and the backup path prepared as a backup path for the active path are affected by the failure, the failure can be recovered even if the OAM function on the data plane is used. Absent. Therefore, the failure recovery by the control plane using the control device 20 is performed (step S06).
- step S05 If neither the active path nor the backup path is affected by the failure (step S04, No branch), the process of step S05 is executed.
- step S05 the route control determination unit 23 determines whether or not a plurality of working paths sharing the protection path have been affected by the failure. When a plurality of working paths are affected by a failure (step S05, Yes branch), the route control determination unit 23 determines that route control is necessary (determines that route control is to be executed), and performs route control. (Step S07).
- FIG. 9 is a diagram for explaining an operation when a plurality of working paths are affected by a failure.
- the path information shown in FIG. 9B is set for the topology shown in FIG.
- three paths (paths P01 to P03) are formed.
- the path P01 is an active path that passes through the node 10-1 and the node 10-4.
- the path P03 is an active path that passes through the nodes 10-1, 10-3, and 10-4.
- the path P02 is a backup path that passes through the nodes 10-1, 10-2, and 10-4.
- the path P02 is a backup path for the active paths P01 and P03.
- FIG. 9B shows path information obtained by collecting these pieces of information. Further, in FIG. 9A, it is assumed that a failure has occurred in the links between the nodes 10-1 and 10-4 and between the nodes 10-3 and 10-4.
- Each of the nodes 10-1, 10-3, and 10-4 transmits a state change notification to the control device 20.
- the control device 20 recognizes the occurrence of a state change in each of the port 2 of the node 10-1, the port 2 of the node 10-3, the port 2 of the node 10-4, and the port 3 from the received state change notification.
- the path control determination unit 23 refers to the information regarding each port in the topology information, and a failure has occurred in the link between the nodes 10-1 and 10-4 and between the nodes 10-3 and 10-4. Recognize that. Further, the route control determination unit 23 identifies the affected path from the link failure position (nodes 10-1, 10-3, and 10-4 in the example of FIG. 9) and the path information. In the example of FIG. 9, it is specified that the paths P01 and P03, which are active paths, are paths affected by the failure.
- the path control determination unit 23 can recognize that these two working paths (paths P01 and P03) share the path P02 which is the backup path by referring to the path information.
- paths P01 and P03 share the path P02 which is the backup path by referring to the path information.
- the failure cannot be recovered for either of the active paths even if the OAM function of the data plane is used. Therefore, it is determined that the failure is recovered by the control plane using the control device 20 (step S07).
- FIG. 10 is a diagram for explaining the operation when a plurality of working paths are affected by a failure, but the protection path is not shared.
- a node 10-5 is added to the network shown in FIG.
- FIG. 10B is a diagram summarizing the topology information of FIG.
- the path P01 is an active path that passes through the node 10-1 and the node 10-4.
- the path P03 is an active path that passes through the nodes 10-1, 10-3, and 10-4.
- the path P02 is a backup path that passes through the nodes 10-1, 10-2, and 10-4, and is set as a backup path of the path P01.
- the path P04 is a backup path that passes through the nodes 10-1, 10-5, and 10-4, and is set as a backup path of the path P03.
- each of the nodes 10-1, 10-3, and 10-4 transmits a state change notification to the control device 20. From the received state change notification, the control device 20 recognizes the occurrence of the state change in each of the port 2 of the node 10-1, the port 2 of the node 10-3, the port 2 and the port 3 of the node 10-4.
- the path control determination unit 23 refers to the information regarding each port in the topology information, and a failure has occurred in the link between the nodes 10-1 and 10-4 and between the nodes 10-3 and 10-4. Recognize that. Furthermore, the route control determination unit 23 identifies the affected path from the link failure position (nodes 10-1, 10-3, and 10-4 in the example of FIG. 8) and the path information. In the example of FIG. 10, the paths P01 and P03 that are working paths are identified as paths that are affected by the failure. When the path control determining unit 23 refers to the path information, it can recognize that these two working paths (paths P01 and P03) do not share the protection path. Therefore, each of the working paths P01 and P03 is recovered from a failure by the OAM function of the data plane.
- the control device 20 since the failure can be recovered without depending on the control plane, the control device 20 does not take any special measures. That is, when a plurality of working paths sharing the protection path are not affected by the failure (step S05, No branch), the processing shown in FIG. 6 is terminated. As described above, even when there are two or more paths affected by the failure, there is a case where failure recovery by the control plane is not performed.
- the control device 20 determines whether or not failure recovery by the data plane is possible or failure recovery by the control plane is necessary based on the state change notification transmitted by each node. As a result of the determination, if it is determined that the failure recovery by the data plane is possible, the control device 20 does not take any special measures and leaves the failure recovery to the data plane.
- the control device 20 performs a measure for recovering the failure. That is, when the communication system according to the present embodiment receives a failure occurrence notification (state change notification) from a node and the failure recovery can be recovered only by the data plane, the failure recovery response is handled by the data plane. To quickly recover from failures. On the other hand, when it is determined that the failure cannot be recovered by handling only the data plane as in the case of multiple failures, the control device 20 takes appropriate measures to achieve reliable failure recovery by the control plane. To do.
- FIG. 11 is a diagram illustrating an example of an internal configuration of the control device 20a according to the present embodiment. 11, the same components as those in FIG. 3 are denoted by the same reference numerals, and the description thereof is omitted.
- the difference between the control device 20a and the control device 20 is that the operation of the route control determination unit 23a is different and a route search unit 25 is added.
- the route control determination unit 23a performs route control on the route search unit 25 when performing the processing according to the flowchart shown in FIG. 6 and determining that failure recovery by the control plane is necessary (steps S06 and S07 in FIG. 6). Output the path information necessary for this.
- the route search unit 25 determines a detour route necessary for failure recovery based on the received path information and information stored in the network configuration DB 22. Further, the route search unit 25 sets a processing rule for realizing the determined path in the node 10 via the communication unit 24. That is, the control device 20a according to the present embodiment determines a detour route necessary for recovering from a failure when failure recovery by the control plane is necessary. Thereafter, a processing rule for realizing the determined path is set in the node 10.
- FIG. 12 is an example, and the operation of the communication system according to the present embodiment is not limited to the flowchart of FIG.
- FIG. 12 is a flowchart illustrating an example of operations in steps S06 and S07 of FIG. 6 described in the first embodiment.
- the control device 20a performs an operation according to the flowchart shown in FIG. 12 when the determinations in steps S04 and S05 in FIG. 6 are true.
- step S101 the route control determination unit 23a determines that route control by the control device 20a is necessary (determines that route control by the control device 20a is to be executed).
- step S102 the route search unit 25 searches for a detour route from the path subject to route control and the topology information. If the determination in step S04 of FIG. 6 is true (step S04, Yes branch), both the active path and the backup path are affected by the failure. Therefore, in step S102 corresponding to step S06, the working path affected by the failure is a path to be searched for a detour route. In other words, the backup path is not a search target for a detour route.
- step S05 when the determination in step S05 in FIG. 6 is true (step S05, Yes branch), there are a plurality of working paths affected by the failure. Therefore, one working path among a plurality of working paths is switched to a backup path. Therefore, the working path that cannot be switched to the backup path becomes a search target for the detour path.
- priority is set in advance for the active path based on the network operation policy and the like. . The priority is held by the control device 20a and is determined in advance by, for example, a network administrator. Alternatively, the control device 20a can automatically determine which of the plurality of working paths is to be recovered by the backup path (the control device 20a determines the priority of the working path). Can also be determined).
- step S103 the route search unit 25 determines a detour route and updates the processing rule held by the node 10.
- FIG. 13 is a diagram for explaining an operation related to determination of a detour route. With reference to FIG. 13, a description will be given of the setting of a detour route when both the active path and the backup path as shown in FIG. 8 are affected by the failure.
- FIG. 13B shows path information before a failure occurs.
- the route search unit 25 searches for a detour route related to the active path P01.
- the route search unit 25 recognizes that the nodes that terminate the active path P01 are the nodes 10-1 and 10-4 by referring to the path information. Further, based on the state change notification received from each of the nodes 10-1, 10-2, and 10-4, a link failure has occurred in the nodes 10-1 and 10-4 and the nodes 10-2 and 10-4. Recognize that it has occurred.
- the route search unit 25 refers to the topology information (see FIG. 4) and determines a detour route while avoiding the port of the node where the link failure has occurred. For example, in FIG. 13A, the route search unit 25 determines the path P03 that terminates the nodes 10-1 and 10-4 as a bypass route. That is, the route search unit 25 sets the path P03 as a detour route of the working path P01 by referring to the topology information. After determining the detour route, the route search unit 25 sets a processing rule for realizing the detour route in the node 10 via the communication unit 24. Further, the route search unit 25 updates the path information. An example of the updated path information is shown in FIG.
- the control device 20a determines a bypass route for recovering the failure, and sets a processing rule for realizing the bypass route in the node 10. As a result, it is possible to reliably and promptly cope with multiple failures that cannot be handled only by the data plane.
- an open flow switch having an OAM function constitutes a data plane and an open flow is applied as a control plane.
- FIG. 14 is a diagram illustrating an example of a configuration in the communication system according to the present embodiment.
- the communication system shown in FIG. 14 includes an open flow controller (OFC) 30 and open flow switches (OFS) 40-1 to 40-4.
- the open flow switches 40-1 to 40-4 have an OAM function.
- a flow is set between the open flow switches 40-1 to 40-4. More specifically, in FIG. 14, flows F01 and F02 are set, the flow F01 is an active flow (solid line in FIG. 14), and the flow F02 is a standby flow (dotted line in FIG. 14).
- the backup flow F02 is used as a backup when a failure occurs in the active flow F01. Note that the OpenFlow switches 40-1 to 40-4 are described as “OpenFlow switch 40” when it is not necessary to distinguish them.
- the OpenFlow switch 40 sends a Port_status message to the OpenFlow controller 30 when it detects a broken link between the OpenFlow switches.
- the OpenFlow controller 30 determines whether or not path control for failure recovery is necessary based on the Port_status message transmitted from the OpenFlow switch 40 and the topology information and flow information held in the OpenFlow controller 30. (Determining whether or not to execute path control). Further, when the OpenFlow controller 30 determines that route control is necessary, the OpenFlow controller 30 searches for a bypass route and determines a bypass route. Furthermore, the OpenFlow controller 30 sends a Flow_mod message to the OpenFlow switch 40 on the detour path. The open flow switch 40 updates the flow table based on the received Flow_mod message. The open flow switch 40 processes the received packet according to the updated flow table, thereby realizing a detour path (accommodating the flow in the detour path).
- FIG. 15 is a diagram illustrating an example of an internal configuration of the OpenFlow controller 30 according to the present embodiment.
- the OpenFlow controller 30 includes a network configuration management unit 31, a network configuration database (network configuration DB) 32, a route control determination unit 33, a route search unit 34, and an OpenFlow message conversion unit 35. And a communication unit 36 that communicates with a device such as the OpenFlow switch 40.
- the network configuration DB 32 is a database that stores topology information and flow information. Note that there is no difference between the topology information and the topology information described in the first embodiment, and further description is omitted.
- the flow information corresponds to the path information described in the first embodiment. That is, the flow attribute defines a flow attribute.
- the flow information defines the type of flow (active system or standby system) and information related to the standby system flow with respect to the active system flow (presence / absence of standby system flow, specification of standby system flow).
- the communication unit 36 When the Port_status message is received from the OpenFlow switch 40 and the Port_status message includes link-down information, the communication unit 36 notifies the path control determination unit 33 of the link-down port information. . Specifically, the communication unit 36 notifies the path control determination unit 33 of port information when the link down flag included in the Port_status message is set.
- the path control determination unit 33 refers to the topology information stored in the network configuration DB 32 and identifies the fault location. Further, the path control determination unit 33 refers to the flow information stored in the network configuration DB 32 to identify the flow in which the failure has occurred and determines whether it is necessary to set a detour path for the flow. When the route control determination unit 33 determines that the setting of a bypass route is necessary, the route control determination unit 33 notifies the route search unit 34 of information on a flow that requires a bypass.
- the route search unit 34 searches for a detour route that avoids the failure that has occurred, based on the flow information that is generated by the route control determination unit 33 and needs to be detoured. Information regarding the searched detour route is notified to the OpenFlow message conversion unit 35.
- the OpenFlow message conversion unit 35 converts the information on the detour route notified from the route search unit 34 into a Flow_mod message, and uses the communication unit 36 to send the Flow_mod message to the OpenFlow switch 40 on the detour route. Send it out.
- FIG. 16 is a diagram illustrating an example of an internal configuration of the open flow switch 40.
- the OpenFlow switch 40 includes a communication unit 41, a table management unit 42, a table database (table DB) 43, and a transfer processing unit 44.
- the communication unit 41 is means for realizing communication with the OpenFlow controller 30 that controls the OpenFlow switch 40. It is assumed that the communication unit 41 communicates with the OpenFlow controller 30 using the OpenFlow protocol.
- the table management unit 42 is a means for managing the tables held in the table DB 43. More specifically, the table management unit 42 registers the flow table set from the OpenFlow controller 30 in the table DB 43. The table management unit 42 manages a group table described later.
- the table DB 43 is configured by a database capable of storing a flow table and a group table that are referred to when the transfer processing unit 44 processes a received packet.
- the transfer processing unit 44 includes a table search unit 141 and an action execution unit 142.
- the table search unit 141 is a means for searching a rule (action) having a match field that matches the received packet from the flow table stored in the table DB 43.
- the action execution unit 142 is a unit that performs packet processing according to the processing specified in the instruction field of the rule searched by the table search unit 141.
- the OpenFlow switch 40 recovers a failure that has occurred between the OpenFlow switches 40 by processing the received packet in accordance with the processing defined in the flow table and the group table.
- FIG. 17 is an exemplification, and the operation of the communication system according to the present embodiment is not limited to the flowchart of FIG.
- step S11 the communication unit 36 of the OpenFlow controller 30 receives the Port_status message from the OpenFlow switch 40.
- step S12 the path control determination unit 33 grasps the link-down port information included in the Port_status message.
- FIG. 18 is a diagram illustrating an example of the Port_status message.
- FIG. 18A shows the port configuration of the OpenFlow switch 40.
- description of the open flow controller 30 is abbreviate
- a data path identifier managed by the OpenFlow controller 30 is assigned to each OpenFlow switch 40.
- the open flow switch 40-1 shown in FIG. 18 is given 0x0a as the data path identifier
- the open flow switch 40-2 is given 0x0b as the data path identifier (see FIG. 18 (b)). ).
- FIG. 18C is a diagram illustrating an example of a Port_status message transmitted by each of the open flow switches 40-1 and 40-4. Referring to FIG. 18A, since the ports 2 of the OpenFlow switches 40-1 and 40-4 are linked down, the information is notified to the OpenFlow controller 30.
- the OpenFlow controller 30 grasps which port of the OpenFlow switch 40 is linked down based on the data path identifier managed by itself and the Port_status message.
- step S ⁇ b> 13 the path control determination unit 33 of the OpenFlow controller 30 grasps the failure location based on the information related to the link-down port transmitted from the OpenFlow switch 40 and the topology information stored in the network configuration DB 32. .
- FIG. 19 is a diagram for explaining an operation of grasping the failure point in the route control determination unit 33.
- the path control determination unit 33 when receiving the Port_status message shown in FIG. 18C, the path control determination unit 33 is given port 2 of the OpenFlow switch 40-1 given 0x0a as the data path identifier and 0x0c as the data path identifier. That the port 2 of the open flow switch 40-4 is linked down is mapped to the topology information (the topology information in the network configuration DB 32 is updated). As a result, it is understood that a failure has occurred between the open flow switches 40-1 and 40-4.
- step S14 the path control determination unit 33 identifies the flow affected by the failure that has occurred based on the updated topology information and flow information. Note that the flow affected by the failure corresponds to a flow that passes through the failure location (in the above example, the open flow switches 40-1 and 40-4).
- step S15 the path control determination unit 33 confirms whether or not the number of flows affected by the failure is one or less. If the number of flows affected by the failure is one or less (step S15, Yes branch), the open flow controller 30 ends the process shown in FIG. In this case, the OAM function included in each OpenFlow switch 40 can recover from a failure without depending on the control plane. Therefore, the OpenFlow controller 30 is not involved in the failure recovery operation.
- FIG. 20 is a diagram for explaining the operation when the OpenFlow controller 30 is not involved in failure recovery.
- the flow F01 set in the active flow is a flow affected by the failure.
- the flow F02 is a standby flow of the flow F01.
- the OpenFlow switches 40-1 and 40-4 can perform failure recovery in the data plane (failure recovery independent of the control plane) by using the group table.
- FIG. 21 is a diagram illustrating an example of a flow table and a group table.
- FIGS. 21A and 21C are examples of flow tables provided in the open flow switches 40-1 and 40-4, respectively.
- FIGS. 21B and 21D are examples of group tables provided in the open flow switches 40-1 and 40-4, respectively.
- description of fields for describing revocation conditions and statistical information is omitted.
- FIG. 21A it is described that the processing for the received packet at port 4 of the OpenFlow switch 40-1 follows the group table. Further, referring to FIG. 21B, an action and a type are specified in the group table. In the example shown in FIGS. 21B and 21D, “Failover” is specified as the type, and a monitoring port (port for monitoring survival confirmation) is set in the action. For example, the action 1 shown in FIG. 21B describes that the existence of the port 2 is confirmed and if the existence of the port 2 can be confirmed, the received packet is transferred from the port 2. It should be noted that an OAM signal or the like is used for the port existence confirmation.
- “Fast Failover” is specified for the OpenFlow switches 40-1 and 40-4.
- the OpenFlow switches 40-1 and 40-4 search for actions in ascending order (action 1, action 2,%), And execute the action for which the existence of the port is first confirmed.
- action 1, action 2, the existence of port 2
- action 2 the existence of port 1 is confirmed, so action 2 is executed.
- the OpenFlow switch 40 detects the link down of the port, the OpenFlow switch 40 transfers the received packet to the port whose existence is confirmed according to the flow table and the group table that define the processing of the received packet.
- the group table type in the OpenFlow switch 40-1 on the transmission side is set to ALL. In that case, the operation on the receiving side is not changed.
- ALL is set as the group table type, the actions set in the group table are executed simultaneously. For example, in the example shown in FIG. 21B, actions 1 and 2 are executed, and flows are transmitted to ports 1 and 2 at the same time. As a result, the active and standby flows are transmitted simultaneously, and an operation equivalent to 1 + 1 protection for selecting one of the two flows on the receiving side can be performed.
- the path control determination unit 33 causes both the active flow and the standby flow corresponding to the active flow to fail. It is confirmed whether or not it is received (step S16).
- the route search unit 34 searches for and determines the detour route of the flow (step S17).
- step S18 the OpenFlow message conversion unit 35 converts the detour route determined by the route search unit 34 into a Flow_mod message.
- step S19 the OpenFlow message conversion unit 35 sends a Flow_mod message to the OpenFlow switch 40 on the detour path via the communication unit 36.
- FIG. 22 is a diagram for explaining setting of a detour route by the OpenFlow controller 30.
- the flows F01 and F02 shown in FIG. 22 are assumed to be affected by the failure.
- the route search unit 34 determines the flow F03 as a detour route for the active flow F01.
- the OpenFlow controller 30 sends a Flow_mod message to the OpenFlow switches 40-1, 40-3, and 40-4 in order to realize the flow F03, and updates the flow table included in each OpenFlow switch.
- FIG. 23 is a diagram illustrating an example of a table updated by the Flow_mod message.
- the open flow switch 40-1 is a transmission side switch. Therefore, the OpenFlow controller 30 sends a Flow_mod message for correcting the accommodation destination of the flow received at the port 4 of the OpenFlow switch 40-1 to the port 3 (see FIG. 23A). In this case, no action referring to the group table is set in the flow table of the open flow switch 40-1. This is because ports 1 and 2 are ports whose survival cannot be confirmed (see FIG. 23B).
- the open flow switch 40-3 is a relay switch. For this reason, the OpenFlow controller 30 sends a Flow_mod message in which the destination of the flow received at the port 1 of the OpenFlow switch 40-3 is port 2 (see FIG. 23C). That is, since a new flow passes through the open flow switch 40-3, a Flow_mod message for adding a new rule to the flow table is transmitted.
- the open flow switch 40-4 is a switch on the receiving side. Therefore, the OpenFlow controller 30 sends a Flow_mod message in which the destination of the flow received at the port 3 of the OpenFlow switch 40-4 is the port 4 (see FIG. 23 (d)). More specifically, a new condition is added to the flow table provided in the open flow switch 40-4.
- a Group_mod message for updating the group table is opened.
- the controller 30 may send it out.
- step S16 When both the active flow and the standby flow are not affected by the failure (step S16 in FIG. 17, No branch), the open flow controller 30 has a plurality of active flows sharing the standby flow. It is confirmed whether or not has been affected by the failure (step S20).
- step S20, Yes branch When a plurality of working flows are affected by a failure (step S20, Yes branch), if it is possible to transmit a backup path for only one flow, search for a detour route for other flows. There is a need to. Accordingly, when a plurality of active flows sharing the standby flow are affected by the failure (step S20, Yes branch), the open flow controller 30 performs the operation described in steps S17 to S19.
- step S20 when a plurality of active flows are not affected by the failure (step S20, No branch), the open flow controller 30 ends the operation. That is, in such a case, similarly to step S15, the OAM function of the data plane can recover the failure independent of the control plane, so the OpenFlow controller 30 is not involved in the failure recovery operation.
- the communication system according to the present embodiment employs OpenFlow as the control plane, and quickly determines whether or not failure recovery is necessary based on the message from the OpenFlow switch 40. Therefore, it is possible to reliably cope with multiple failures by open flow while supporting high-speed failure recovery on the data plane using the OAM function.
- the control device includes: The communication system according to mode 1, wherein the network topology information and path information are used as information relating to the network configuration to determine whether or not the path control is necessary to recover from a failure occurring in the network.
- the control device includes: The communication system according to mode 1 or 2, wherein the path control is determined not to be executed when the number of paths formed by the plurality of nodes is one or less affected by a failure occurring in the network.
- the control device includes: If the path is formed by the plurality of nodes and the active path and the backup path corresponding to the active path are affected by a failure occurring in the network, the path control is performed.
- the control device includes: When a plurality of working paths sharing a backup path that are formed by the plurality of nodes are affected by a failure that has occurred in the network, it is determined to execute the path control.
- the control device includes: The communication system according to any one of Embodiments 1 to 5, wherein when it is determined that the route control is necessary, a path that avoids a failure that has occurred in the network is searched based on information about the network.
- Each of the plurality of nodes requests a processing rule for processing the packet;
- the control device creates a processing rule for processing the received packet in response to the request, and notifies the created processing rule to at least one of the plurality of nodes.
- Each of the plurality of nodes forwards the received packet to a port other than the link-down port in accordance with a flow table and a group table that define processing of the received packet in response to detecting a link down of the port.
- the communication system according to any one of Forms 1 to 7.
- Form 9 It is as the control apparatus which concerns on the above-mentioned 2nd viewpoint.
- the route control determination unit The control device according to mode 9, wherein the network topology information and path information are used as information relating to the network configuration to determine whether or not to execute the path control in order to recover from a failure occurring in the network.
- the route control determination unit The control device according to mode 9 or 10 that determines that the route control is not executed when a path formed by a plurality of the nodes and less than one path is affected by a failure occurring in the network.
- the route control determination unit If the path is formed by a plurality of the nodes, and the working path and the backup path corresponding to the working path are affected by a failure occurring in the network, the path control is performed.
- the control device according to any one of Embodiments 9 to 11, which is determined to be executed.
- the route control determination unit If a plurality of working paths sharing a backup path that are formed by a plurality of nodes are affected by a failure that has occurred in the network, it is determined that the path control is to be executed.
- the control device according to any one of Forms 9 to 12.
- the route control determination unit includes a route search unit that searches for a path that avoids a failure that has occurred in the network based on information about the network when the route control determination unit determines to execute the route control The control device according to any one of the above.
- the step of determining whether or not the route control is necessary includes Control of the control device according to mode 15 for determining whether or not to execute the path control to recover from a failure occurring in the network, using the topology information and path information of the network as information relating to the network configuration Method.
- the step of determining whether or not the route control is necessary includes The control device according to mode 15 or 16 that determines that the route control is not executed when the number of paths formed by the plurality of nodes is one or less affected by a failure occurring in the network. Control method.
- the step of determining whether or not the route control is necessary includes If the path is formed by a plurality of the nodes, and the working path and the backup path corresponding to the working path are affected by a failure occurring in the network, the path control is performed.
- the step of determining whether or not the route control is necessary includes If a plurality of working paths sharing a backup path that are formed by a plurality of nodes are affected by a failure that has occurred in the network, it is determined that the path control is to be executed.
- the control method of the control apparatus as described in any one of form 15 thru
- a form 15 including a step of searching for a path that avoids a failure that has occurred in the network based on information about the network when it is determined that the route control is to be executed by the step of determining whether or not the route control is necessary.
- the control method of the control apparatus as described in any one of thru
- [Form 21] It is as the program which concerns on the above-mentioned 4th viewpoint.
- the process of determining whether the route control is necessary is as follows: The program of the form 21 which judges whether the said route control is performed in order to recover the failure which arose in the said network, using the topology information and path information of the said network as information regarding the structure of the said network.
- the process of determining whether the route control is necessary is as follows: The program of the form 21 or 22 which judges not to perform the said route control, when it is a path
- the process of determining whether the route control is necessary is as follows: If a plurality of working paths sharing a backup path that are formed by a plurality of nodes are affected by a failure that has occurred in the network, it is determined that the path control is to be executed. The program according to any one of forms 21 to 24. [Form 26] A mode of executing a process of searching for a path that avoids a failure occurring in the network based on information on the network when it is determined that the path control is to be executed by the process of determining whether the path control is necessary. The program according to any one of 21 to 25.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
本発明は、日本国特許出願:特願2012-252425号(2012年11月16日出願)の優先権主張に基づくものであり、同出願の全記載内容は引用をもって本書に組み込み記載されているものとする。
本発明は、通信システム、制御装置、その制御方法及びプログラムに関する。特に、ネットワークを集中制御する制御装置を含む通信システム、制御装置、その制御方法及びプログラムに関する。
なお、本方法は、ネットワークを制御する制御装置という、特定の機械に結びつけられている。
なお、このプログラムは、コンピュータが読み取り可能な記憶媒体に記録することができる。記憶媒体は、半導体メモリ、ハードディスク、磁気記録媒体、光記録媒体等の非トランジェント(non-transient)なものとすることができる。本発明は、コンピュータプログラム製品として具現することも可能である。
第1の実施形態について図面を参照して説明する。
・パスP01は、ノード10-1とノード10-4を経由する現用系パスである。
・パスP02は、ノード10-1、10-2及び10-4を経由する予備系パスである。
これらの情報をまとめた情報がパス情報であり、図5(b)がパス情報の一例である。図5(b)を参照することで、現用系パスであるパスP01の予備系パスは、パスP02であると認識される。
・パスP01は、ノード10-1とノード10-4を経由する現用系パスである。
・パスP03は、ノード10-1、10-3及び10-4を経由する現用系パスである。
・パスP02は、ノード10-1、10-2及び10-4を経由する予備系パスである。
・パスP02は、現用系パスP01及びP03の予備系パスである。
これらの情報をまとめたパス情報が、図9(b)である。さらに、図9(a)では、ノード10-1と10-4の間と、ノード10-3と10-4の間のリンクに障害が発生したものとする。
・パスP01は、ノード10-1とノード10-4を経由する現用系パスである。
・パスP03は、ノード10-1、10-3及び10-4を経由する現用系パスである。
・パスP02は、ノード10-1、10-2及び10-4を経由する予備系パスであって、パスP01の予備系パスに設定されている。
・パスP04は、ノード10-1、10-5及び10-4を経由する予備系パスであって、パスP03の予備系パスに設定されている。
これらの情報をまとめると、図10(c)となる。
続いて、第2の実施形態について図面を参照して詳細に説明する。
続いて、第3の実施形態について図面を参照して詳細に説明する。
上述の第1の視点に係る通信システムのとおりである。
[形態2]
前記制御装置は、
前記ネットワークの構成に関する情報として、前記ネットワークのトポロジ情報とパス情報を用いて、前記ネットワークに生じた障害を回復するために前記経路制御が必要か否かを判断する形態1の通信システム。
[形態3]
前記制御装置は、
前記複数のノードにより形成されるパスであって、前記ネットワークに生じた障害により影響を受けるパスが1本以下の場合には、前記経路制御を実行しないと判断する形態1又は2の通信システム。
[形態4]
前記制御装置は、
前記複数のノードにより形成されるパスであって、現用系パスと現用系パスに対応する予備系パスとが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する形態1乃至3のいずれか一に記載の通信システム。
[形態5]
前記制御装置は、
前記複数のノードにより形成されるパスであって、予備系パスを共有する複数の現用系パスが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する形態1乃至4のいずれか一に記載の通信システム。
[形態6]
前記制御装置は、
前記経路制御が必要と判断した場合に、前記ネットワークに関する情報に基づいて、前記ネットワークに生じた障害を回避するパスを探索する形態1乃至5のいずれか一に記載の通信システム。
[形態7]
前記複数のノードのそれぞれは、パケットを処理するための処理規則を要求し、
前記制御装置は、前記要求に応じて、受信したパケットを処理するための処理規則を作成し、作成した処理規則を前記複数のノードの少なくとも1つに通知する形態1乃至6のいずれか一に記載の通信システム。
[形態8]
前記複数のノードのそれぞれは、ポートのリンクダウンを検出したことに応じて、受信したパケットの処理を規定するフローテーブル及びグループテーブルに従い、前記受信したパケットを前記リンクダウンしたポート以外のポートに転送する形態1乃至7のいずれか一に記載の通信システム。
[形態9]
上述の第2の視点に係る制御装置のとおりである。
[形態10]
前記経路制御判断部は、
前記ネットワークの構成に関する情報として、前記ネットワークのトポロジ情報とパス情報を用いて、前記ネットワークに生じた障害を回復するために前記経路制御を実行するか否かを判断する形態9の制御装置。
[形態11]
前記経路制御判断部は、
複数の前記ノードにより形成されるパスであって、前記ネットワークに生じた障害により影響を受けるパスが1本以下の場合には、前記経路制御を実行しないと判断する形態9又は10の制御装置。
[形態12]
前記経路制御判断部は、
複数の前記ノードにより形成されるパスであって、現用系パスと現用系パスに対応する予備系パスとが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する形態9乃至11のいずれか一に記載の制御装置。
[形態13]
前記経路制御判断部は、
複数の前記ノードにより形成されるパスであって、予備系パスを共有する複数の現用系パスが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する形態9乃至12のいずれか一に記載の制御装置。
[形態14]
前記経路制御判断部により、前記経路制御を実行すると判断された場合に、前記ネットワークに関する情報に基づいて、前記ネットワークに生じた障害を回避するパスを探索する経路探索部を備える形態9乃至13のいずれか一に記載の制御装置。
[形態15]
上述の第3の視点に係る制御装置の制御方法のとおりである。
[形態16]
前記経路制御の要否を判断する工程は、
前記ネットワークの構成に関する情報として、前記ネットワークのトポロジ情報とパス情報を用いて、前記ネットワークに生じた障害を回復するために前記経路制御を実行するか否かを判断する形態15の制御装置の制御方法。
[形態17]
前記経路制御の要否を判断する工程は、
複数の前記ノードにより形成されるパスであって、前記ネットワークに生じた障害により影響を受けるパスが1本以下の場合には、前記経路制御を実行しないと判断する形態15又は16の制御装置の制御方法。
[形態18]
前記経路制御の要否を判断する工程は、
複数の前記ノードにより形成されるパスであって、現用系パスと現用系パスに対応する予備系パスとが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する形態15乃至17のいずれか一に記載の制御装置の制御方法。
[形態19]
前記経路制御の要否を判断する工程は、
複数の前記ノードにより形成されるパスであって、予備系パスを共有する複数の現用系パスが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する形態15乃至18のいずれか一に記載の制御装置の制御方法。
[形態20]
前記経路制御の要否を判断する工程により、前記経路制御を実行すると判断された場合に、前記ネットワークに関する情報に基づいて、前記ネットワークに生じた障害を回避するパスを探索する工程を含む形態15乃至19のいずれか一に記載の制御装置の制御方法。
[形態21]
上述の第4の視点に係るプログラムのとおりである。
[形態22]
前記経路制御の要否を判断する処理は、
前記ネットワークの構成に関する情報として、前記ネットワークのトポロジ情報とパス情報を用いて、前記ネットワークに生じた障害を回復するために前記経路制御を実行するか否かを判断する形態21のプログラム。
[形態23]
前記経路制御の要否を判断する処理は、
複数の前記ノードにより形成されるパスであって、前記ネットワークに生じた障害により影響を受けるパスが1本以下の場合には、前記経路制御を実行しないと判断する形態21又は22のプログラム。
[形態24]
前記経路制御の要否を判断する処理は、
複数の前記ノードにより形成されるパスであって、現用系パスと現用系パスに対応する予備系パスとが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する形態21乃至23のいずれか一に記載のプログラム。
[形態25]
前記経路制御の要否を判断する処理は、
複数の前記ノードにより形成されるパスであって、予備系パスを共有する複数の現用系パスが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する形態21乃至24のいずれか一に記載のプログラム。
[形態26]
前記経路制御の要否を判断する処理により、前記経路制御を実行すると判断された場合に、前記ネットワークに関する情報に基づいて、前記ネットワークに生じた障害を回避するパスを探索する処理を実行させる形態21乃至25のいずれか一に記載のプログラム。
20、20a、101 制御装置
21、31 ネットワーク構成管理部
22、32 ネットワーク構成データベース(ネットワーク構成DB)
23、23a、33 経路制御判断部
24、36、41 通信部
25、34 経路探索部
30 オープンフローコントローラ
35 オープンフローメッセージ変換部
40、40-1~40-4 オープンフロースイッチ
42 テーブル管理部
43 テーブルデータベース(テーブルDB)
44 転送処理部
141 テーブル検索部
142 アクション実行部
Claims (26)
- OAM(Operation Administration and Maintenance)機能を備える複数のノードと、
前記複数のノードを制御する制御装置と、
を含み、
前記複数のノードのそれぞれは、前記複数のノードにより構成されるネットワークに生じた障害により影響を受けたポートに関する情報を含む状態変更通知を前記制御装置に送信し、
前記制御装置は、前記状態変更通知と、前記ネットワークの構成に関する情報と、に基づいて、前記ネットワークにおける経路制御を実行するか否かを判断する、通信システム。 - 前記制御装置は、
前記ネットワークの構成に関する情報として、前記ネットワークのトポロジ情報とパス情報を用いて、前記ネットワークに生じた障害を回復するために前記経路制御が必要か否かを判断する請求項1の通信システム。 - 前記制御装置は、
前記複数のノードにより形成されるパスであって、前記ネットワークに生じた障害により影響を受けるパスが1本以下の場合には、前記経路制御を実行しないと判断する請求項1又は2の通信システム。 - 前記制御装置は、
前記複数のノードにより形成されるパスであって、現用系パスと現用系パスに対応する予備系パスとが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する請求項1乃至3のいずれか一項に記載の通信システム。 - 前記制御装置は、
前記複数のノードにより形成されるパスであって、予備系パスを共有する複数の現用系パスが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する請求項1乃至4のいずれか一項に記載の通信システム。 - 前記制御装置は、
前記経路制御が必要と判断した場合に、前記ネットワークに関する情報に基づいて、前記ネットワークに生じた障害を回避するパスを探索する請求項1乃至5のいずれか一項に記載の通信システム。 - 前記複数のノードのそれぞれは、パケットを処理するための処理規則を要求し、
前記制御装置は、前記要求に応じて、受信したパケットを処理するための処理規則を作成し、作成した処理規則を前記複数のノードの少なくとも1つに通知する請求項1乃至6のいずれか一項に記載の通信システム。 - 前記複数のノードのそれぞれは、ポートのリンクダウンを検出したことに応じて、受信したパケットの処理を規定するフローテーブル及びグループテーブルに従い、前記受信したパケットを前記リンクダウンしたポート以外のポートに転送する請求項1乃至7のいずれか一項に記載の通信システム。
- OAM(Operation Administration and Maintenance)機能を備える複数のノードの少なくとも1つから、前記複数のノードにより構成されるネットワークに生じた障害により影響を受けたポートに関する情報を含む状態変更通知を受信する通信部と、
前記状態変更通知と、前記ネットワークの構成に関する情報と、に基づいて、前記ネットワークにおける経路制御を実行するか否かを判断する経路制御判断部と、
を備える制御装置。 - 前記経路制御判断部は、
前記ネットワークの構成に関する情報として、前記ネットワークのトポロジ情報とパス情報を用いて、前記ネットワークに生じた障害を回復するために前記経路制御を実行するか否かを判断する請求項9の制御装置。 - 前記経路制御判断部は、
複数の前記ノードにより形成されるパスであって、前記ネットワークに生じた障害により影響を受けるパスが1本以下の場合には、前記経路制御を実行しないと判断する請求項9又は10の制御装置。 - 前記経路制御判断部は、
複数の前記ノードにより形成されるパスであって、現用系パスと現用系パスに対応する予備系パスとが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する請求項9乃至11のいずれか一項に記載の制御装置。 - 前記経路制御判断部は、
複数の前記ノードにより形成されるパスであって、予備系パスを共有する複数の現用系パスが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する請求項9乃至12のいずれか一項に記載の制御装置。 - 前記経路制御判断部により、前記経路制御を実行すると判断された場合に、前記ネットワークに関する情報に基づいて、前記ネットワークに生じた障害を回避するパスを探索する経路探索部を備える請求項9乃至13のいずれか一項に記載の制御装置。
- OAM(Operation Administration and Maintenance)機能を備える複数のノードの少なくとも1つから、前記複数のノードにより構成されるネットワークに生じた障害により影響を受けたポートに関する情報を含む状態変更通知を受信する工程と、
前記状態変更通知と、前記ネットワークの構成に関する情報と、に基づいて、前記ネットワークにおける経路制御を実行するか否かを判断する工程と、
を含む制御装置の制御方法。 - 前記経路制御の要否を判断する工程は、
前記ネットワークの構成に関する情報として、前記ネットワークのトポロジ情報とパス情報を用いて、前記ネットワークに生じた障害を回復するために前記経路制御を実行するか否かを判断する請求項15の制御装置の制御方法。 - 前記経路制御の要否を判断する工程は、
複数の前記ノードにより形成されるパスであって、前記ネットワークに生じた障害により影響を受けるパスが1本以下の場合には、前記経路制御を実行しないと判断する請求項15又は16の制御装置の制御方法。 - 前記経路制御の要否を判断する工程は、
複数の前記ノードにより形成されるパスであって、現用系パスと現用系パスに対応する予備系パスとが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する請求項15乃至17のいずれか一項に記載の制御装置の制御方法。 - 前記経路制御の要否を判断する工程は、
複数の前記ノードにより形成されるパスであって、予備系パスを共有する複数の現用系パスが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する請求項15乃至18のいずれか一項に記載の制御装置の制御方法。 - 前記経路制御の要否を判断する工程により、前記経路制御を実行すると判断された場合に、前記ネットワークに関する情報に基づいて、前記ネットワークに生じた障害を回避するパスを探索する工程を含む請求項15乃至19のいずれか一項に記載の制御装置の制御方法。
- OAM(Operation Administration and Maintenance)機能を備える複数のノードの少なくとも1つから、前記複数のノードにより構成されるネットワークに生じた障害により影響を受けたポートに関する情報を含む状態変更通知を受信する処理と、
前記状態変更通知と、前記ネットワークの構成に関する情報と、に基づいて、前記ネットワークにおける経路制御を実行するか否かを判断する処理と、
を制御装置を制御するコンピュータに実行させるプログラム。 - 前記経路制御の要否を判断する処理は、
前記ネットワークの構成に関する情報として、前記ネットワークのトポロジ情報とパス情報を用いて、前記ネットワークに生じた障害を回復するために前記経路制御を実行するか否かを判断する請求項21のプログラム。 - 前記経路制御の要否を判断する処理は、
複数の前記ノードにより形成されるパスであって、前記ネットワークに生じた障害により影響を受けるパスが1本以下の場合には、前記経路制御を実行しないと判断する請求項21又は22のプログラム。 - 前記経路制御の要否を判断する処理は、
複数の前記ノードにより形成されるパスであって、現用系パスと現用系パスに対応する予備系パスとが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する請求項21乃至23のいずれか一項に記載のプログラム。 - 前記経路制御の要否を判断する処理は、
複数の前記ノードにより形成されるパスであって、予備系パスを共有する複数の現用系パスが、前記ネットワークに生じた障害により影響を受けるパスである場合には、前記経路制御を実行すると判断する請求項21乃至24のいずれか一項に記載のプログラム。 - 前記経路制御の要否を判断する処理により、前記経路制御を実行すると判断された場合に、前記ネットワークに関する情報に基づいて、前記ネットワークに生じた障害を回避するパスを探索する処理を実行させる請求項21乃至25のいずれか一項に記載のプログラム。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/439,208 US9544223B2 (en) | 2012-11-16 | 2013-11-14 | Communication system, control apparatus, method for controlling same, and program |
EP13856009.9A EP2922248B1 (en) | 2012-11-16 | 2013-11-14 | Communication system, control device, method for controlling same, and program |
JP2014547027A JP6311612B2 (ja) | 2012-11-16 | 2013-11-14 | 通信システム、制御装置、その制御方法及びプログラム |
ES13856009T ES2745637T3 (es) | 2012-11-16 | 2013-11-14 | Sistema de comunicación, dispositivo de control, método de control del mismo, y programa |
CN201380060175.5A CN104798348A (zh) | 2012-11-16 | 2013-11-14 | 通信系统、控制装置、用于控制控制装置的方法以及程序 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012252425 | 2012-11-16 | ||
JP2012-252425 | 2012-11-16 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014077313A1 true WO2014077313A1 (ja) | 2014-05-22 |
Family
ID=50731222
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2013/080778 WO2014077313A1 (ja) | 2012-11-16 | 2013-11-14 | 通信システム、制御装置、その制御方法及びプログラム |
Country Status (6)
Country | Link |
---|---|
US (1) | US9544223B2 (ja) |
EP (1) | EP2922248B1 (ja) |
JP (1) | JP6311612B2 (ja) |
CN (1) | CN104798348A (ja) |
ES (1) | ES2745637T3 (ja) |
WO (1) | WO2014077313A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017000243A1 (zh) * | 2015-06-30 | 2017-01-05 | 华为技术有限公司 | 一种路由的方法、相关设备及系统 |
JP2020522925A (ja) * | 2017-05-31 | 2020-07-30 | アファームド ネットワークス,インク. | Ipsecの地理的冗長性のための分離した制御プレーンおよびデータプレーンの同期 |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103929334B (zh) * | 2013-01-11 | 2018-02-23 | 华为技术有限公司 | 网络异常通知方法和装置 |
CN103782552B (zh) * | 2013-09-03 | 2016-10-12 | 华为技术有限公司 | 一种业务路径的保护方法、控制器、设备及系统 |
JP2017103519A (ja) * | 2015-11-30 | 2017-06-08 | 日本電気株式会社 | 制御装置、通信システム、制御方法及びプログラム |
US11271870B2 (en) | 2016-01-27 | 2022-03-08 | Oracle International Corporation | System and method for supporting scalable bit map based P_Key table in a high performance computing environment |
US10594627B2 (en) * | 2016-01-27 | 2020-03-17 | Oracle International Corporation | System and method for supporting scalable representation of switch port status in a high performance computing environment |
US10313231B1 (en) | 2016-02-08 | 2019-06-04 | Barefoot Networks, Inc. | Resilient hashing for forwarding packets |
US10063407B1 (en) * | 2016-02-08 | 2018-08-28 | Barefoot Networks, Inc. | Identifying and marking failed egress links in data plane |
US10404619B1 (en) | 2017-03-05 | 2019-09-03 | Barefoot Networks, Inc. | Link aggregation group failover for multicast |
US10237206B1 (en) | 2017-03-05 | 2019-03-19 | Barefoot Networks, Inc. | Equal cost multiple path group failover for multicast |
US10362631B2 (en) * | 2017-04-03 | 2019-07-23 | Level 3 Communications, Llc | Last resource disaster routing in a telecommunications network |
US20190334808A1 (en) * | 2018-04-28 | 2019-10-31 | Hewlett Packard Enterprise Development Lp | Data plane forwarding table downed link updating |
CN109194592B (zh) * | 2018-09-25 | 2021-06-25 | 盛科网络(苏州)有限公司 | 一种解决multi-link网络中孤岛问题的方法和系统 |
CN115460125B (zh) * | 2022-09-05 | 2024-07-12 | 苏州盛科通信股份有限公司 | 一种解决Multi-Link网络中孤岛问题的方法和装置 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003318983A (ja) | 2002-04-26 | 2003-11-07 | Hitachi Ltd | 光クロスコネクト網の障害回復方法 |
JP2007053793A (ja) | 2003-02-21 | 2007-03-01 | Nippon Telegr & Teleph Corp <Ntt> | 通信ネットワークにおけるパスの故障救済を行うための装置及び方法 |
JP2008066989A (ja) | 2006-09-06 | 2008-03-21 | Ntt Communications Kk | 経路状態管理システム、制御装置、ネットワーク管理装置、通信装置および経路状態管理方法 |
JP2012090058A (ja) * | 2010-10-19 | 2012-05-10 | Nec Corp | 通信システム、制御装置、処理規則の設定方法およびプログラム |
JP2012170161A (ja) | 2012-06-13 | 2012-09-06 | Hitachi Ltd | ノード、制御装置及び通信システム |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5995485A (en) * | 1996-11-26 | 1999-11-30 | Mci Communications Corporation | Method and apparatus for isolating network failures by correlating paths issuing alarms with failure spans |
US6347074B1 (en) * | 1997-08-13 | 2002-02-12 | Mci Communications Corporation | Centralized method and system for excluding components from a restoral route in a communications network |
DE19737359C2 (de) * | 1997-08-27 | 1999-08-19 | Siemens Ag | Kommunikationseinrichtung für die Übertragung von Nachrichtensignalen |
JP3467681B2 (ja) * | 1998-11-04 | 2003-11-17 | 日本電信電話株式会社 | 二重化構成を有するパスの故障管理方法 |
JP3871467B2 (ja) * | 1999-03-25 | 2007-01-24 | 富士通株式会社 | 通信パスの障害復旧装置 |
US7085224B1 (en) * | 2001-06-14 | 2006-08-01 | Cisco Technology, Inc. | Method and apparatus for fast failure detection in switched LAN networks |
US20030005095A1 (en) * | 2001-06-29 | 2003-01-02 | Fee John A. | Method and system for programmable submarine network configuration plans to enable diverse service level agreements in telecommunication networks |
JP4437984B2 (ja) * | 2005-08-24 | 2010-03-24 | アラクサラネットワークス株式会社 | ネットワーク中継装置及びその制御方法 |
JP2008269462A (ja) * | 2007-04-24 | 2008-11-06 | Hitachi Ltd | ノードの管理装置及び方法 |
CN101990133B (zh) * | 2009-07-31 | 2014-02-19 | 中兴通讯股份有限公司 | 一种自动交换光网络业务降级告警状态的维护方法及系统 |
JP5621781B2 (ja) * | 2009-10-06 | 2014-11-12 | 日本電気株式会社 | ネットワークシステムとコントローラと方法とプログラム |
EP2526652B1 (en) * | 2010-01-22 | 2019-04-10 | Telefonaktiebolaget LM Ericsson (publ) | Method, apparatus and communication network for providing restoration survivability |
EP2572473B1 (en) * | 2010-05-19 | 2014-02-26 | Telefonaktiebolaget L M Ericsson (PUBL) | Methods and apparatus for use in an openflow network |
-
2013
- 2013-11-14 ES ES13856009T patent/ES2745637T3/es active Active
- 2013-11-14 CN CN201380060175.5A patent/CN104798348A/zh active Pending
- 2013-11-14 WO PCT/JP2013/080778 patent/WO2014077313A1/ja active Application Filing
- 2013-11-14 JP JP2014547027A patent/JP6311612B2/ja active Active
- 2013-11-14 US US14/439,208 patent/US9544223B2/en active Active
- 2013-11-14 EP EP13856009.9A patent/EP2922248B1/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003318983A (ja) | 2002-04-26 | 2003-11-07 | Hitachi Ltd | 光クロスコネクト網の障害回復方法 |
JP2007053793A (ja) | 2003-02-21 | 2007-03-01 | Nippon Telegr & Teleph Corp <Ntt> | 通信ネットワークにおけるパスの故障救済を行うための装置及び方法 |
JP2008066989A (ja) | 2006-09-06 | 2008-03-21 | Ntt Communications Kk | 経路状態管理システム、制御装置、ネットワーク管理装置、通信装置および経路状態管理方法 |
JP2012090058A (ja) * | 2010-10-19 | 2012-05-10 | Nec Corp | 通信システム、制御装置、処理規則の設定方法およびプログラム |
JP2012170161A (ja) | 2012-06-13 | 2012-09-06 | Hitachi Ltd | ノード、制御装置及び通信システム |
Non-Patent Citations (2)
Title |
---|
KENJI FUJIHIRA: "PROPOSAL OF SERVICE RECOVERY METHOD AGAINST WIDE AREA DISASTER", PROCEEDINGS OF COMMUNICATIONS SOCIETY IEICE, vol. 2, 28 August 2012 (2012-08-28), pages 57, XP008179437 * |
See also references of EP2922248A4 |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017000243A1 (zh) * | 2015-06-30 | 2017-01-05 | 华为技术有限公司 | 一种路由的方法、相关设备及系统 |
EP3306873A4 (en) * | 2015-06-30 | 2018-05-30 | Huawei Technologies Co., Ltd. | Routing method, and relevant device and system |
US10630592B2 (en) | 2015-06-30 | 2020-04-21 | Huawei Technologies Co., Ltd. | Routing method, related device, and system |
US11509584B2 (en) | 2015-06-30 | 2022-11-22 | Huawei Technologies Co., Ltd. | Routing method, related device, and system |
JP2020522925A (ja) * | 2017-05-31 | 2020-07-30 | アファームド ネットワークス,インク. | Ipsecの地理的冗長性のための分離した制御プレーンおよびデータプレーンの同期 |
JP7234141B2 (ja) | 2017-05-31 | 2023-03-07 | マイクロソフト テクノロジー ライセンシング,エルエルシー | Ipsecの地理的冗長性のための分離した制御プレーンおよびデータプレーンの同期 |
Also Published As
Publication number | Publication date |
---|---|
US20150295818A1 (en) | 2015-10-15 |
ES2745637T3 (es) | 2020-03-03 |
EP2922248A1 (en) | 2015-09-23 |
EP2922248B1 (en) | 2019-06-26 |
US9544223B2 (en) | 2017-01-10 |
CN104798348A (zh) | 2015-07-22 |
EP2922248A4 (en) | 2016-07-13 |
JPWO2014077313A1 (ja) | 2017-01-05 |
JP6311612B2 (ja) | 2018-04-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6311612B2 (ja) | 通信システム、制御装置、その制御方法及びプログラム | |
JP5941404B2 (ja) | 通信システム、経路切替方法及び通信装置 | |
JP5033856B2 (ja) | ネットワーク構成の想定のための装置、システム | |
CN103155497B (zh) | 通信系统、控制设备、节点、处理规则设置方法以及程序 | |
JP5546461B2 (ja) | チェーン及びリングネットワークにおける透過的なオートリカバリのための方法及びシステム | |
JP6095583B2 (ja) | データ転送装置システム及びネットワークシステム | |
JP5743809B2 (ja) | 網管理システムおよび網管理方法 | |
RU2612599C1 (ru) | Устройство управления, система связи, способ управления коммутаторами и программа | |
Chen et al. | When software defined networks meet fault tolerance: a survey | |
JP2008167315A (ja) | 回線冗長接続方法および広域通信網ノード装置 | |
JP4895972B2 (ja) | リングプロトコル高速切替方法およびその装置 | |
JP5822236B2 (ja) | 通信装置、通信装置を制御する方法及び通信システム | |
Liao et al. | Fast failover with hierarchical disjoint paths in SDN | |
EP2479926B1 (en) | Method and device for backing up user information | |
WO2014175423A1 (ja) | 通信ノード、通信システム、パケット処理方法及びプログラム | |
JP6781288B2 (ja) | マルチノード装置及びその予備通信方法 | |
WO2013185583A1 (zh) | 智能光网络中保护业务的恢复方法和装置 | |
CN102045259B (zh) | 分组交换设备以及管理用户业务的方法 | |
JP4541367B2 (ja) | 故障救済方法およびパケット通信装置 | |
EP2180636B1 (en) | Method for signaling a unidirectional failure of a packet-switched link | |
WO2017010078A1 (ja) | 制御装置、障害通知方法及び記録媒体 | |
JP6282222B2 (ja) | 通信装置 | |
JP2007088866A (ja) | 通信システム | |
CN102946321A (zh) | 一种基于irf网络的故障处理方法和设备 | |
WO2016045276A1 (zh) | 报文转发方法、装置、sdn及系统 |
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: 13856009 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14439208 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2014547027 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2013856009 Country of ref document: EP |