WO2017092400A1 - 故障恢复方法及装置、控制器、软件定义网络 - Google Patents

故障恢复方法及装置、控制器、软件定义网络 Download PDF

Info

Publication number
WO2017092400A1
WO2017092400A1 PCT/CN2016/094675 CN2016094675W WO2017092400A1 WO 2017092400 A1 WO2017092400 A1 WO 2017092400A1 CN 2016094675 W CN2016094675 W CN 2016094675W WO 2017092400 A1 WO2017092400 A1 WO 2017092400A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
fault
network
service path
recovery
Prior art date
Application number
PCT/CN2016/094675
Other languages
English (en)
French (fr)
Inventor
孙德胜
赵福川
薄开涛
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP16869711.8A priority Critical patent/EP3386156B1/en
Publication of WO2017092400A1 publication Critical patent/WO2017092400A1/zh

Links

Images

Classifications

    • 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
    • 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
    • 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
    • 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/38—Flow based routing

Definitions

  • the present application relates to, but is not limited to, the field of communications, and in particular, to a fault recovery method and apparatus, a controller, and a software defined network.
  • SDN Software Defined Network
  • ONF Open Network Forum
  • ITU-T International Telecommunications Union-Telecommunications Standardization Sector
  • CCSA China Communications Standards Association
  • the controller generally includes a path management component, a service orchestration component, a topology management component, and a protocol adaptation component (ie, a protocol processing component).
  • the forwarding device generally includes a flow table component, an alarm detection component, a forwarding component, and a protocol adaptation component (ie, a protocol processing component).
  • Transport network (implementation includes Ethernet, Multi-Protocol Label Switching (MPLS), MPLS-TP, Optical Transport Network (OTN), and Wavelength Division Multiplexing (WDM) Technical network)
  • MPLS Multi-Protocol Label Switching
  • MPLS-TP MPLS-TP
  • OTN Optical Transport Network
  • WDM Wavelength Division Multiplexing
  • the alarm is sent to the controller through the SDN protocol processing component, where the protocol processing component is mainly responsible for the content.
  • the information is encapsulated into an SDN protocol packet, or the content information is parsed from the SDN protocol packet; the protocol processing component of the controller receives the alarm and forwards it to the topology management component, where the topology management component is mainly responsible for SDN resource management, including links, Node device, service path, etc., the topology management component updates the network topology, and notifies the path management component, the path
  • the management component creates a new path for the path that is affected by the fault, and the information generated by the service orchestration component is sent to the forwarding device related to the new path by the protocol processing component, where the path management component is mainly responsible for adding, modifying, and After the function is deleted, the service orchestration component generates the flow table and the group table entry required for forwarding the flow according to the logical path.
  • the protocol processing component of the forwarding device receives the configuration of the entry and forwards it to the flow table component. The component calls the relevant interface to write to the forwarding component, the new path is created successfully, and the service is restored.
  • the time from the network failure service interruption to the establishment of a new path recovery service is as short as possible, so as to reduce the impact on the user function and improve the user experience.
  • ASON Automatically Switched Optical Network
  • the relevant test standard specification has required the recovery time to be completed in 1 second or a few seconds.
  • the service scheduling process of the service path that is, according to the logical path output by the path management component, generating forwarding information such as a flow table and a group table required for forwarding the flow according to the forwarding hardware requirement takes a lot of time, thereby causing the recovery time of the SDN failure. Longer.
  • the embodiment of the invention provides a fault recovery method and device, a controller and a software defined network SDN.
  • a fault recovery method including: receiving network fault information sent by a forwarding device; and acquiring fault recovery information corresponding to network fault information pre-stored in the controller according to the network fault information, wherein the fault recovery is performed.
  • the information is used to recover the network fault corresponding to the network fault information; the fault recovery information is sent to each forwarding device corresponding to the fault recovery information.
  • the network fault information includes: link fault information.
  • the fault recovery information includes: a forwarding entry of each forwarding device corresponding to the standby service path; where the standby service path is a service path affected by the network fault information. Alternate business path.
  • the method further includes: deleting the service path affected by the network fault information.
  • the method after receiving the network fault information sent by the forwarding device, the method further includes: when detecting the newly added service path, creating an alternate service path corresponding to the newly added service path; wherein, the newly added service path is The alternate service path of the service path that is affected by the network fault information; the forwarding entry of each forwarding device required by the forwarding pipeline of the new service path corresponding to the new service path is stored in the controller.
  • a controller for use in an SDN, the controller comprising: a protocol processing component, a recovery management component, and an entry repository component; wherein the protocol processing component is configured to be a forwarding device in a software-defined network SDN
  • the received network failure information is sent to the recovery management component; the recovery management component is set to recover the network failure information according to the protocol processing component, retrieve the failure recovery information corresponding to the network failure information from the entry warehouse component, and recover the failure.
  • the information is sent to the forwarding device through the protocol processing component.
  • the entry warehouse component stores the network fault information, the fault recovery information, and the correspondence between the network fault information and the fault recovery information.
  • the network fault information further includes: link fault information.
  • the fault recovery information includes: a forwarding entry of each forwarding device corresponding to the standby service path; where the standby service path is an alternate service path of the service path affected by the network fault information.
  • the controller further includes: a path management component, configured to simulate various faults occurring in the SDN, and calculate an alternate service path corresponding to the service path for the service path affected by the fault; the service orchestration component is set according to The standby service path forwards the flow request, generates the fault recovery information, and stores the fault and the fault recovery information in the entry warehouse component.
  • the fault recovery information includes: a forwarding entry of each forwarding device related to the standby service path.
  • the controller further includes: a topology management component, configured to receive network fault information sent by the protocol processing component, and add the new service path to the network resource information of the SDN when the newly added service path is detected.
  • the new service path is an alternate service path of the service path affected by the network fault information.
  • the path management component is further configured to delete the service path affected by the network fault information.
  • an SDN comprising: a forwarding device and the controller described above.
  • a fault recovery apparatus which is applied to a software-defined network SDN, and includes: a receiving module configured to receive network fault information sent by the forwarding device; and an acquiring module configured to acquire the pre-stored control according to the network fault information.
  • the fault recovery information corresponding to the network fault information wherein the fault recovery information is used to recover the network fault corresponding to the network fault information; and the sending module is configured to send the fault recovery information to each of the fault recovery information Forward the device.
  • the network fault information includes: link fault information.
  • the fault recovery information includes: a forwarding entry of each forwarding device corresponding to the standby service path; where the standby service path is an alternate service path of the service path affected by the network fault information.
  • the method further includes: deleting the module, and setting to delete the service path affected by the network fault information.
  • the method further includes: creating a module, configured to create an alternate service path corresponding to the newly added service path when the newly added service path is detected; wherein the newly added service path is a service affected by the network fault information
  • the standby service path of the path is configured to store, in the controller, the forwarding entry of each forwarding device required by the forwarding pipeline of the alternate service path corresponding to the newly added service path.
  • an embodiment of the present invention further provides a storage medium configured to store program code for performing the following steps:
  • the fault recovery information corresponding to the network fault information pre-stored in the controller, where the fault recovery information is used to recover the network fault corresponding to the network fault information;
  • the failure recovery information is sent to each forwarding device corresponding to the failure recovery information.
  • the fault recovery information corresponding to the network fault information is obtained from the controller, and then sent to each forwarding device, instead of generating the fault recovery information after receiving the network fault, thereby solving the fault recovery after the SDN fault occurs.
  • the longer time problem saves recovery time and improves recovery efficiency.
  • FIG. 1 is an infrastructure diagram of an SDN controller and a forwarding device in the related art
  • FIG. 2 is a flowchart 1 of a fault recovery method according to an embodiment of the present invention.
  • FIG. 3 is a second flowchart of a fault recovery method according to an embodiment of the present invention.
  • FIG. 4 is a third flowchart of a fault recovery method according to an embodiment of the present invention.
  • FIG. 5 is a structural diagram 1 of a controller according to an embodiment of the present invention.
  • FIG. 6 is a second structural diagram of a controller according to an embodiment of the present invention.
  • FIG. 7 is a structural diagram 3 of a controller according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a software-defined network SDN according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram 1 of a fault recovery apparatus according to an embodiment of the present invention.
  • FIG. 10 is a structural block diagram 2 of a fault recovery apparatus according to an embodiment of the present invention.
  • FIG. 11 is a structural block diagram 3 of a fault recovery apparatus according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of an SDN according to a preferred embodiment of the present invention.
  • FIG. 13 is a schematic flowchart diagram of a method for maintaining validity of an item storage component storage information according to an embodiment of the present invention
  • FIG. 14 is a schematic diagram of a fault recovery scenario according to an embodiment of the present invention.
  • 15 is a flow diagram of implementing fast recovery in accordance with a network failure, in accordance with an embodiment of the present invention.
  • FIG. 2 is a flowchart 1 of a fault recovery method according to an embodiment of the present invention. As shown in FIG. 2, the flow may include the following steps:
  • Step S202 receiving network fault information sent by the forwarding device.
  • Step S204 Acquire, according to the network fault information, fault recovery information corresponding to the network fault information that is pre-stored in the controller, where the fault recovery information is used to recover the network fault corresponding to the network fault information;
  • Step S206 the fault recovery information is sent to a corresponding forwarding device.
  • the fault recovery information corresponding to the network fault information is obtained from the controller, and then sent to each forwarding device.
  • the fault recovery information is not generated, but the fault recovery information is pre-stored in the controller.
  • the controller receives the network fault information, directly from the controller. The fault recovery information is obtained, thereby solving the problem that the recovery fault time is long after the SDN fault occurs in the related technology, which saves recovery time and improves recovery efficiency.
  • the foregoing method may be applied to an SDN, where the SDN may include a network of related transmission technologies such as Ethernet, MPLS, MPLS-TP, OTN, and WDM, or may include a transmission network using a similar layer network transmission technology.
  • the above network fault information includes: link fault information.
  • the link fault information may be the alarm information of the link fault, the notification information of the link fault, and the like, but is not limited thereto.
  • the link fault can be a single fault. For example, there is only one link fault in the network, or multiple faults, that is, multiple link faults exist in the network. It should be noted that the interruption of the link itself or the power failure of the forwarding device may cause the above link failure, but is not limited thereto.
  • the fault recovery information may include a forwarding entry of each forwarding device corresponding to the standby service path, where the standby service path is an alternate service path of the service path affected by the network fault information.
  • the forwarding entry may include a flow table and a group table. At least one of the information. That is, the forwarding entry information corresponding to the alternate service path corresponding to each fault is stored in the controller in advance, and when a network fault occurs, such as a link fault occurs, the standby service corresponding to the network fault is retrieved through the network fault information. The forwarding entry of each forwarding device corresponding to the path is forwarded to the corresponding forwarding device to complete the fault recovery.
  • FIG. 3 is a second flowchart of a fault recovery method according to an embodiment of the present invention. As shown in FIG. 3, after the step S206, the method may further include:
  • Step S302 deleting the service path affected by the network fault information.
  • the number of service paths can be reduced, and the information of the backup path that needs to be stored in the controller can be reduced, thereby saving storage space.
  • step S302 may also be performed after step S204.
  • step S302 may not be performed, that is, the service path affected by the network failure information may also be reserved, and the service path affected by the network failure information may be an optimal service path, after the optimal service path is retained. If the network fault is eliminated, the alternate service path of the service path may not be adopted, but the optimal service path may be reselected. For the service path that is deleted or retained by the network fault information, it can be determined according to the actual needs of the user, but is not limited thereto.
  • FIG. 4 is a flowchart of a fault recovery method according to an embodiment of the present invention. As shown in FIG. 4, after the step S202, the method further includes:
  • step S402 when a new service path is detected, an alternate service path corresponding to the newly added service path is created; wherein the newly added service path is an alternate service path of the service path affected by the network failure information;
  • Step S404 The forwarding entry of each forwarding device required by the forwarding pipeline of the backup service path corresponding to the new service path is stored in the controller.
  • one or more forwarding entries form a forwarding pipeline
  • an alternate service path may correspond to one or more forwarding pipelines.
  • the new service path is corresponding.
  • the forwarding entry of each forwarding device in the standby service path is added to the controller to dynamically maintain the forwarding entry information in the controller, so that the service can be quickly restored when the new service path fails.
  • the current path is AB, AC, AD, BC, BD, CD as an example.
  • the link AB fails, the link AB is reserved.
  • the service path is ACB
  • the controller directly retrieves the forwarding entry information of A, C, and B corresponding to the ACB. If there is a new service path ACB, the ACB should be created in the controller.
  • the service path (assumed to be ADCB), and then the forwarding entries of the links A1, D, C, and B corresponding to ADCB and ADCB are stored in the controller, so that the next fault (such as AC or AC and AB occurs) When a failure occurs, it can be quickly recovered.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention in essence or the contribution to the related art can be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM).
  • the instructions include a number of instructions for causing a terminal device (which may be a cell phone, computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.
  • FIG. 5 is a structural diagram of the controller according to the embodiment of the present invention. As shown in FIG. 5, the controller includes: protocol processing. Component 52, recovery management component 54, entry repository component 56;
  • the protocol processing component 52 is configured to send network failure information received from the forwarding device in the SDN to the recovery management component;
  • the recovery management component 54 coupled with the protocol processing component 52 and the entry repository component 56, is configured to retrieve failure recovery information corresponding to the network failure information from the entry repository component 56 based on the network failure information sent by the protocol processing component 52, and The fault recovery information is sent to the forwarding device through the protocol processing component; wherein the entry warehouse component 56 stores the network fault information, the fault recovery information, and the correspondence between the network fault information and the fault recovery information.
  • the controller receives the network fault information, the fault recovery information, and the correspondence between the network fault information and the fault recovery information in advance in the entry warehouse component 56, when the recovery management component 54 receives
  • the fault recovery information corresponding to the network fault information can be obtained directly from the entry warehouse component 56, and the fault recovery information is not generated, and the recovery fault time after the SDN fault occurs in the related technology is solved.
  • the problem saves recovery time and improves recovery efficiency.
  • the foregoing SDN may include a network of related transmission technologies such as Ethernet, MPLS, MPLS-TP, OTN, and WDM, and may also include a transmission network using a similar layer network transmission technology.
  • the network fault information may include: link fault information.
  • the link fault information may be the alarm information of the link fault, the notification information of the link fault, and the like, but is not limited thereto.
  • the link fault can be a single fault. For example, there is only one link fault in the network, or multiple faults, that is, multiple link faults exist in the network. It should be noted that the interruption of the link itself or the power failure of the forwarding device may cause the above link failure, but is not limited thereto.
  • the fault recovery information may include a forwarding entry of each forwarding device corresponding to the standby service path, where the standby service path is an alternate service path of the service path affected by the network fault information.
  • the forwarding entry may include at least one of a flow table and a group table information.
  • FIG. 6 is a structural diagram of a controller according to an embodiment of the present invention. As shown in FIG. 6, the controller further includes:
  • the path management component 62 is configured to simulate various faults occurring in the SDN, and calculate an alternate service path corresponding to the service path for the service path affected by the fault;
  • the service orchestration component 64 is configured to be coupled to the path management component 62, configured to forward the flow requirements according to the alternate service path, generate failure recovery information, and store the failure and failure recovery information in the entry repository component 56, wherein the The fault recovery information includes: forwarding entries of each forwarding device related to the alternate service path.
  • the path management component 62 and the service orchestration component 64 are configured to calculate an alternate service path of the service path by simulating a fault in advance, and storing the simulated fault and the alternate service path information (ie, fault recovery information) corresponding to the fault in the entry.
  • the fault recovery information corresponding to the fault is directly obtained, and the calculation is not required, thereby saving the recovery time.
  • path management component 62 is further configured to delete the service path affected by the network failure information. To save storage space in the controller.
  • the path management component 62 can also be configured to retain traffic paths that are affected by network failure information.
  • the service path affected by the network failure information may be an optimal service path. Since the path management component 62 reserves the optimal service path, if the network failure is eliminated, the service path may not be used. The business path is re-selected to adopt the optimal business path.
  • whether to delete or retain the service path affected by the network failure information may be set according to actual needs of the user, but is not limited thereto.
  • FIG. 7 is a structural structural diagram of a controller according to an embodiment of the present invention. As shown in FIG. 7, the controller may further include:
  • the topology management component 72 is configured to receive network fault information sent by the protocol processing component, and add a new service path to the network resource information of the SDN when the newly added service path is detected, where the newly added service path is a network The alternate service path of the service path affected by the fault information.
  • the topology management component 72 adds the new service path to the network resource information of the SDN when the new service path is detected, and then the service orchestration component 64 turns the forwarding device of the standby service path corresponding to the new service path.
  • the publication item is added to the entry repository component 56 to dynamically maintain the entry repository component 56 to enable rapid recovery of the service when the new service path fails.
  • FIG. 8 is a schematic structural diagram of an SDN according to an embodiment of the present invention. As shown in FIG. 8, the SDN includes: a forwarding device 82 and any of the following FIG. 5 to FIG. The controller 84 is explained for the explanation of the controller in the embodiment shown in FIG. 5 to FIG. 7, and details are not described herein again.
  • forwarding device may be one or multiple, and is not limited thereto.
  • the SDN is based on an improvement to the controller, that is, by pre-storing the network failure information, the failure recovery information, and the correspondence between the network failure information and the failure recovery information in the entry warehouse component 56, when the recovery management component 54 receives the network failure information,
  • the fault recovery information corresponding to the network fault information can be obtained directly from the entry warehouse component 56, and the fault recovery information is not generated, which solves the problem that the recovery fault time is longer after the SDN fault occurs in the related technology, thereby saving Recovery time increases the efficiency of recovery.
  • a fault recovery device is further provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and has not been described again.
  • the term “module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 9 is a structural block diagram 1 of a fault recovery apparatus according to an embodiment of the present invention.
  • the apparatus is applied to an SDN.
  • the apparatus includes:
  • the receiving module 902 is configured to receive network fault information sent by the forwarding device.
  • the obtaining module 904 is configured to be connected to the receiving module 902, and configured to acquire, according to the network fault information, fault recovery information corresponding to the network fault information pre-stored in the controller, where the fault recovery information is used for the network fault information. Corresponding network failure to recover;
  • the sending module 906 is configured to be connected to the obtaining module 904, and configured to send the fault recovery information to each forwarding device corresponding to the fault recovery information.
  • the fault recovery information that is pre-stored in the network fault information is obtained from the controller, and then sent to each forwarding device.
  • the device After receiving the network fault, the device does not directly generate the fault recovery information, but stores the fault recovery information in the controller in advance. After receiving the network fault information, the fault recovery information is directly obtained from the controller. The problem of recovering the fault after the SDN fault occurs in the related art is solved, thereby saving the recovery time and improving the recovery efficiency.
  • the foregoing SDN may include a network of related transmission technologies such as Ethernet, MPLS, MPLS-TP, OTN, and WDM, and may also include a transmission network using a similar layer network transmission technology.
  • the above network fault information includes: link fault information.
  • the link fault information may be the alarm information of the link fault, the notification information of the link fault, and the like, but is not limited thereto.
  • the link fault can be a single fault. For example, there is only one link fault in the network, or multiple faults, that is, multiple link faults exist in the network. It should be noted that the interruption of the link itself or the power failure of the forwarding device may cause the above link failure, but is not limited thereto.
  • FIG. 10 is a structural block diagram 2 of a fault recovery apparatus according to an embodiment of the present invention. As shown in FIG. 10, the apparatus further includes:
  • the deleting module 1002 is configured to be connected to the sending module 906, and is configured to delete the service path affected by the network fault information.
  • deletion module 1002 may be configured to be connected to the acquisition module 904, and is not limited thereto.
  • the deletion of the original service path affected by the network fault information by the deletion module 1002 can reduce the number of service paths and reduce the information of the backup path that needs to be stored in the controller, thereby saving storage space.
  • the foregoing apparatus may not include the deleting module 1002, but may include a retaining module configured to retain a service path affected by the network fault information, and whether the foregoing apparatus includes the deleting module 1002 or the retaining module may be configured according to the user. The actual requirements are determined.
  • the above device may also include the deletion module 1002 and the reservation module, and is not limited thereto.
  • the above reserved module can retain the service path affected by the network failure information, if the device of the reserved module is used, if the service path affected by the network failure information is an optimal service path, if the network failure is eliminated, the network path may not be used.
  • FIG. 11 is a structural block diagram 3 of a fault recovery apparatus according to an embodiment of the present invention. As shown in FIG. 11, the apparatus further includes:
  • the creating module 1102 is configured to be connected to the receiving module 902, and is configured to create an alternate service path corresponding to the newly added service path when the newly added service path is detected; wherein the newly added service path is a service affected by the network fault information.
  • the storage module 1104 is configured to be connected to the creation module 1102, and is configured to store, in the controller, a forwarding entry of each forwarding device required by the forwarding pipeline of the alternate service path corresponding to the newly added service path.
  • the forwarding entry of each forwarding device of the standby service path corresponding to the newly added service path is added to the controller to dynamically maintain the controller.
  • the forwarding entry information is used to quickly recover the service when the new service path fails.
  • the current path has AB, AC, AD, BC, BD, CD, for example, when the link AB fails, the standby service path of the link AB is ACB, then the acquisition module 1004 directly goes to the controller to retrieve the A, C, and B corresponding to the ACB.
  • the forwarding entry information at this time, has a new service path ACB, then the creation module 1202 needs to create an alternate service path of the ACB in the controller (assumed to be ADCB), and then the link is ADCB and A corresponding to ADCB.
  • the forwarding entries of D, C, and B are stored in the controller, so that the next failure (such as AC or AC and AB failure) can be quickly recovered.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
  • the embodiment of the present invention introduces a recovery management component and an entry warehouse component based on the existing architecture of the controller, and proposes a method for implementing a fast recovery function, which solves the problem that the related technology recovery function takes a long time to meet the implementation including Ethernet, MPLS, and Network requirements for transport technologies such as MPLS-TP, OTN, and WDM.
  • the SDN includes a controller and a forwarding device, where the controller includes a protocol processing component, a topology management component, a path management component, and a service orchestration component. And the newly introduced entry warehouse component and the recovery management component; the forwarding device also includes a protocol processing component, an alarm detection component, a forwarding component, and a flow table component, and the foregoing components in the controller are in FIG. 5 to FIG. 7
  • the respective components of the illustrated embodiment function the same.
  • the core content of this embodiment is that after the network failure occurs, the protocol processing component quickly transmits the fault information to the recovery management component, and the recovery management component retrieves the entry warehouse component according to the fault information, and quickly sends the configuration information of the recovery path through the protocol processing component. It has the advantages of fast speed and good recovery effect.
  • the fast recovery function is implemented. Therefore, the method for the fast recovery function in the embodiment of the present invention includes:
  • Step 1 the alarm detection component of the forwarding device detects whether the related component is faulty. If yes, the fault information is reported to the controller through the protocol processing component of the forwarding device, and the process proceeds to the next step; otherwise, the content of this step is re-implemented.
  • Step 2 The protocol processing component of the controller receives the fault information (corresponding to step S302 in the embodiment shown in FIG. 1), passes it to the recovery management component, and passes it to the topology management component; the flow proceeds to the next step.
  • Step 3 The recovery management component of the controller retrieves the entry warehouse component according to the fault information (corresponding to step S204 of the embodiment shown in FIG. 1), and retrieves the expected information. If yes, the retrieved information is sent to the forwarding device through the protocol processing component (corresponding to step S206 of the embodiment shown in FIG. 1), and the process proceeds to step 1; otherwise, the content of the step is re-implemented.
  • the related elements in step 1 above may include units that affect the normal transmission of services, such as physical link interruption, label switching path detection failure, and the like.
  • the recovery management component in step 2 may also trigger the deletion operation of the original service path affected by the failure when the recovery information operation is performed to retrieve the desired information or the recovery service operation is implemented.
  • the alarm described in step 2 is passed to the topology management component, which triggers the update of the storage information of the entry warehouse component, that is, the storage table component storage component information validity.
  • FIG. 13 is a schematic flowchart of a method for maintaining validity of an item storage component storage information according to an embodiment of the present invention. As shown in FIG. 13, the method for maintaining validity of an item storage component of a table item includes the following steps:
  • Step S1302 According to the current SDN resource and the service path configuration, the path management component of the controller simulates various faults in the network, and calculates an alternate path for the service path affected by the fault (corresponding to the alternate service path in the foregoing embodiments) ;
  • Step S1304 Based on the alternate path output by the controller path management component, the service orchestration component performs service orchestration, that is, information such as a flow table and a group table entry required to generate flow water according to the path of each node device (corresponding to FIG. 1 )
  • the failure recovery information in the embodiment is stored in the entry warehouse component together with the network failure information;
  • Step S1306 The topology management component of the controller detects whether the SDN has a fault, and whether the network resource has been added, modified, or deleted. Or does the path management component detect whether there are new, modified, or deleted services and path operations? If yes, go to step S1308; otherwise, re-implement the contents of this step.
  • step S1308 the current network topology and resource status are updated, and the flow proceeds to step S1302.
  • fault or fault information including single fault (anytime, network There is only one failure, such as a single link interruption, multiple failures (multiple failures occur at the same time or in the network, such as multiple link interruptions, or node power failures, etc.).
  • the above method is applicable to SDN, including networks implementing existing transmission technologies such as Ethernet, MPLS, MPLS-TP, OTN, and WDM, and transmission networks employing similar layer network transmission technologies.
  • the foregoing technical solution of the embodiment of the present invention quickly retrieves the information of the alternate path according to the network fault reported by the forwarding device by introducing a recovery management component, an entry warehouse component, and an interaction interface between the controller and the existing components of the controller. Sending to the forwarding device to restore the service, with the advantages of fast, simple and reliable.
  • the embodiment of the present invention proposes another implementation method of the fast recovery function based on the SDN infrastructure.
  • the core of the preferred embodiment is the SDN controller import entry warehouse component, the recovery management component, and the The interface between the component and the component; the controller simulates the alternate path (or recovery path) of the fault calculation business path in advance, and saves the information of the alternate path in the table item warehouse component; when the failure occurs, the recovery management component quickly retrieves the table item warehouse The component also forwards the forwarding information to the forwarding device to resume the service.
  • FIG. 14 is a schematic diagram of a fault recovery scenario according to an embodiment of the present invention.
  • the fault recovery scenario described in FIG. 14 is taken as an example, that is, an SDN deployment controller and four SDN forwarding devices A, B, C, and D, device A and The bidirectional service between the Bs has been opened, the transmission path is A--B, and the optical fiber interruption in the link A ⁇ -B direction at the time T1 is taken as an example to illustrate the implementation of the fast recovery in the embodiment of the present invention, and FIG. 15 is implemented according to the present invention.
  • the embodiment of the fast recovery of the embodiment of the present invention includes the following steps:
  • Step S1502 The alarm detection component of the forwarding devices A, B, C, and D detects whether the local related component has a fault according to the current SDN resource and the service path configuration. If yes, step S1504 is performed, and if not, step S1602 is performed.
  • Step S1504 At time T1, the fiber in the direction of the link A ⁇ -B is interrupted, and the alarm detecting component of A detects the link failure, and reports the failure of the A-B link to the controller through the protocol processing component.
  • the alarm detection components of A, B, C, and D continue to detect local related component alarms online.
  • step S1506 the protocol processing component of the controller receives the A-B link failure alarm reported by A (corresponding to step S202 of the embodiment shown in FIG. 2), passes to the recovery management component, and simultaneously passes to the topology management component.
  • Step S1508 the recovery management component of the controller retrieves the entry warehouse component according to the alarm information of the A-B link failure (corresponding to step S204 of the embodiment shown in FIG. 2); if the desired information is retrieved, the recovery path A is restored. If the A, C, and B corresponding to the C-B forwarding entry information, step S1510 is performed. If the entry repository component does not have the recovery path information corresponding to the service path A-B, for example, the controller has not yet generated the recovery path information. The table item warehouse component (that is, the expected information is not retrieved), the recovery management component continues to re-retrieve. .
  • step S1510 the information of A, C, and B is respectively sent to the A, C, and B forwarding devices through the protocol processing component (corresponding to step S206 of the embodiment shown in FIG. 2), the service is restored, and then the flow proceeds to step S1502.
  • step S1508 after the recovery management component implements the recovery service operation or implements the recovery service operation, the path management component may also delete the original service path A-B affected by the failure.
  • the SDN deployment controller and the four SDN forwardings of A, B, C, and D are used.
  • the device, the two-way service between the devices A and B has been opened, and the transmission path is A--B.
  • the fiber break in the direction of the link A ⁇ -B at the time of the T1 is taken as an example, and the maintenance item storage component of the embodiment of the present invention is stored. Implementation of information effectiveness.
  • Step 1 According to the current SDN resources, including A-B, A-C, A-D, B-C, B-D and C-D links, A, B, C, D four forwarding devices and service path A —B.
  • the alarm detection component detects whether a local related component has a fault.
  • the controller path management component simulates that each link of the network is faulty, or each node fails, finds a service path affected by the fault, and calculates an alternate path (corresponding to the above-mentioned alternate service path).
  • the A-B link fails the A-B path of the bidirectional service is affected by the fault, and the alternate path A-C-B is calculated.
  • Step 2 Based on the controller path management component output, when the A-B link is faulty, the A-B path is affected by the forwarding flow requirement of the forwarding device, and the forwarding entries of the A, C, and B are generated, such as the flow table of each level. Group table and other information. This information, along with the A-B link failure information, is stored with the entry warehouse component to quickly retrieve the relevant alternate path forwarding information based on the failure.
  • Step 3 The topology management component of the controller detects the A-B link failure at time T1; the path management component detects the newly added A-C-B service path.
  • the topology management component updates SDN resource information, including A-C, A-D, B-C, B-D, and C-D links, four forwarding devices A, B, C, and D, and service path A-C-B. , AB. Perform the content described in step 1 of the technical solution.
  • the new alternate path of A-C-B will be created (such as A-D-C-B), and the service can be quickly restored again in the next failure (such as A-C link interruption).
  • A-C link interruption such as A-C link interruption
  • step 3 if the deleted fault path A-B is implemented as described in the fast recovery scheme, the third topology management component update SDN resource information no longer includes the service path A-B.
  • protocol processing component the entry warehouse component, the recovery management component, the topology management component, the path management component, and the service orchestration component of the controller in the foregoing embodiment are in the controllers in FIG. 6 to FIG.
  • the protocol processing component, the entry warehouse component, the recovery management component, the topology management component, the path management component, and the business orchestration component perform similar functions.
  • the embodiment of the invention further provides a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • modules or steps of the present application can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the application is not limited to any particular combination of hardware and software.
  • the embodiment of the invention provides a fault recovery method and device, a controller and a software defined network, so as to at least solve the problem that the recovery fault time is long after the SDN fault occurs in the related art.
  • the fault recovery method is applied to the SDN, and includes: receiving network fault information sent by the forwarding device, and acquiring, according to the network fault information, fault recovery information corresponding to the network fault information pre-stored in the controller, where The fault recovery information is used to recover the network fault corresponding to the network fault information, and the fault recovery information is sent to each forwarding device corresponding to the fault recovery information.
  • the embodiment of the invention not only saves recovery time but also improves recovery efficiency.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本文公布了一种故障恢复方法及装置、控制器、软件定义网络，其中，该方法包括：接收转发设备发送的网络故障信息；根据网络故障信息，获取预先存储在控制器中的与网络故障信息对应的故障恢复信息，其中，该故障恢复信息用于对网络故障信息对应的网络故障进行恢复；将故障恢复信息发送给与故障恢复信息对应的各个转发设备。通过本文，解决了相关技术中SDN故障发生后恢复故障时间较长的问题，进而节省了恢复时间，提高了恢复的效率。

Description

故障恢复方法及装置、控制器、软件定义网络 技术领域
本申请涉及但不限于通信领域，具体而言，涉及一种故障恢复方法及装置、控制器、软件定义网络。
背景技术
软件定义网络(Software defined network，SDN)是近年来通信领域的研究热点。开放网络论坛(Open networking forum，ONF)、国际电信联盟-电信标准部(International Telecommunications Union-Telecommunications standardization sector，ITU-T)、中国通讯标准化协会(China Communications Standards Association，CCSA)等国际国内标准组织拟定SDN相关标准建议，重点在于控制器(Controller)和转发设备(Forwarder)之间解耦，规范控制器与控制器、控制器与转发面之间的接口，方便不同厂家的控制器、转发设备联合组网。
图1是相关技术中的SDN控制器和转发设备的基础架构图，如图1所示，控制器一般包含路径管理组件、业务编排组件、拓扑管理组件以及协议适配组件(即协议处理组件)；转发设备一般包含流表组件、告警检测组件、转发组件以及协议适配组件(即协议处理组件)。
传送网(实施包括以太网、多协议标签交换(Multi-Protocol Label Switching，MPLS)、MPLS-TP、光传送网(Optical Transport Network，OTN)以及波分复用(Wavelength Division Multiplexing，WDM)等传送技术的网络)网络发生故障(比如链路断，元器件或者供电单元等故障)后，创建新路径恢复业务是传送网的重要功能。
传送网演进到SDN之后，如图1所示，故障相邻的转发设备的告警检测组件检测到故障后，通过SDN协议处理组件上送告警至控制器，其中，该协议处理组件主要负责将内容信息封装为SDN协议包，或者从SDN协议包中解析出内容信息；控制器的协议处理组件接收到告警后转发至拓扑管理组件，其中，该拓扑管理组件主要负责SDN资源管理，包括链路、节点设备、业务路径等，拓扑管理组件更新网络拓扑，并通知路径管理组件，路径 管理组件为故障影响了的路径创建新路径，并通过业务编排组件生成表项信息经协议处理组件下发至新路径相关的各转发设备，其中，路径管理组件主要负责路径的新增、修改和删除等功能，业务编排组件主要根据逻辑路径，按照转发硬件要求生成转发流水所需的流表、组表条目等；转发设备的协议处理组件接收到表项配置后转发至流表组件，流表组件调用相关接口写入转发组件，新路径创建成功，业务恢复。
一般，从网络发生故障业务中断，到建立新路径恢复业务这段时间要求越短越好，以便减轻对用户功能的影响，改善用户体验。例如，在自动交换光网络(Automatically Switched Optical Network，ASON)，相关测试标准规范曾要求所述恢复时间在1秒或几秒之内完成。另外，业务路径的业务编排过程，即根据路径管理组件输出的逻辑路径，按照转发硬件要求生成转发流水所需的流表、组表等转发信息会耗费很多的时间，进而使得SDN故障的恢复时间较长。
针对相关技术中SDN故障发生后恢复故障时间较长的问题，目前尚未提出有效的解决方案。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保围。
本发明实施例提供了一种故障恢复方法及装置、控制器、软件定义网络SDN。
一方面，提供了一种故障恢复方法，包括：接收转发设备发送的网络故障信息；根据网络故障信息，获取预先存储在控制器中的与网络故障信息对应的故障恢复信息，其中，该故障恢复信息用于对网络故障信息对应的网络故障进行恢复；将故障恢复信息发送给与故障恢复信息对应的各个转发设备。
在本发明实施例中，网络故障信息包括：链路故障信息。
在本发明实施例中，故障恢复信息包括：备用业务路径对应的各个转发设备的转发表项；其中，备用业务路径为受网络故障信息影响的业务路径的 备用业务路径。
在本发明实施例中，在将故障恢复信息发送给与恢复故障信息对应的各个转发设备之后，还包括：删除受网络故障信息影响的业务路径。
在本发明实施例中，在接收转发设备发送的网络故障信息之后，方法还包括：在检测到新增业务路径时，创建与新增业务路径对应的备用业务路径；其中，新增业务路径为受网络故障信息影响的业务路径的备用业务路径；将新增业务路径对应的备用业务路径的转发流水线要求的各个转发设备的转发表项存储在控制器中。
另一方面，提供了一种控制器，应用于SDN，控制器包括：协议处理组件，恢复管理组件，表项仓库组件；其中，协议处理组件，设置为将从软件定义网络SDN中的转发设备接收到的网络故障信息，发送给恢复管理组件；恢复管理组件，设置为根据协议处理组件发送的网络故障信息，从表项仓库组件中检索与网络故障信息对应的故障恢复信息，以及将故障恢复信息通过协议处理组件发送给转发设备；其中，表项仓库组件存储有网络故障信息、故障恢复信息和网络故障信息与故障恢复信息的对应关系。
在本发明实施例中，网络故障信息还包括：链路故障信息。
在本发明实施例中，故障恢复信息包括：备用业务路径对应的各个转发设备的转发表项；其中，备用业务路径为受网络故障信息影响的业务路径的备用业务路径。
在本发明实施例中，控制器还包括：路径管理组件，设置为模拟SDN出现的各种故障，对受故障影响的业务路径计算与业务路径对应的备用业务路径；业务编排组件，设置为根据备用业务路径转发流水要求，生成故障恢复信息，以及将故障和故障恢复信息存储于所述表项仓库组件中；其中，故障恢复信息包括：与备用业务路径相关的各个转发设备的转发表项。
在本发明实施例中，控制器还包括：拓扑管理组件，设置为接收协议处理组件发送的网络故障信息，以及在检测到新增业务路径时，将新增业务路径添加到SDN的网络资源信息中，其中，新增业务路径为受网络故障信息影响的业务路径的备用业务路径。
在本发明实施例中，路径管理组件，还设置为删除受网络故障信息影响的业务路径。
另一方面，提供了一种SDN，包括：转发设备和上述控制器。
另一方面，提供了一种故障恢复装置，应用于软件定义网络SDN，包括：接收模块，设置为接收转发设备发送的网络故障信息；获取模块，设置为根据网络故障信息，获取预先存储在控制器中的与网络故障信息对应的故障恢复信息，其中，该故障恢复信息用于对网络故障信息对应的网络故障进行恢复；发送模块，设置为将故障恢复信息发送给与故障恢复信息对应的各个转发设备。
在本发明实施例中，网络故障信息包括：链路故障信息。
在本发明实施例中，故障恢复信息包括：备用业务路径对应的各个转发设备的转发表项；其中，备用业务路径为受网络故障信息影响的业务路径的备用业务路径。
在本发明实施例中，还包括：删除模块，设置为删除受网络故障信息影响的业务路径。
在本发明实施例中，还包括：创建模块，设置为在检测到新增业务路径时，创建与新增业务路径对应的备用业务路径；其中，新增业务路径为受网络故障信息影响的业务路径的备用业务路径；存储模块，设置为将新增业务路径对应的备用业务路径的转发流水线要求的各个转发设备的转发表项存储在控制器中。
另一方面，本发明实施例还提供了一种存储介质，被设置为存储用于执行以下步骤的程序代码：
接收转发设备发送的网络故障信息；
根据网络故障信息，获取预先存储在控制器中的与网络故障信息对应的故障恢复信息，其中，该故障恢复信息用于对网络故障信息对应的网络故障进行恢复；
将故障恢复信息发送给与故障恢复信息对应的各个转发设备。
通过本发明实施例，采用当接收到转发设备上报的网络故障信息后，直 接从控制器中获取与该网络故障信息对应的故障恢复信息，再下发给各个转发设备，而不用当接收到网络故障后再去生成该故障恢复信息，进而解决了SDN故障发生后恢复故障时间较长的问题，节省了恢复时间，提高了恢复效率。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
在附图中：
图1是相关技术中的SDN控制器和转发设备的基础架构图；
图2是根据本发明实施例的故障恢复方法的流程图一；
图3是根据本发明实施例的故障恢复方法的流程图二；
图4是根据本发明实施例的故障恢复方法的流程图三；
图5是根据本发明实施例的控制器的结构框架图一；
图6是根据本发明实施例的控制器的结构框架图二；
图7是根据本发明实施例的控制器的结构框架图三；
图8是根据本发明实施例的软件定义网络SDN的结构示意图；
图9是根据本发明实施例的故障恢复装置的结构框图一；
图10是根据本发明实施例的故障恢复装置的结构框图二；
图11是根据本发明实施例的故障恢复装置的结构框图三；
图12是根据本发明优选例的SDN的架构示意图；
图13是根据本发明实施例的维护表项仓库组件存储信息有效性的方法的流程示意图；
图14是根据本发明实施例的故障恢复场景的示意图；
图15是根据本发明实施例的根据网络故障实施快速恢复的流程图。
本发明的实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在 不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种故障恢复方法，图2是根据本发明实施例的故障恢复方法的流程图一，如图2所示，该流程可以包括如下步骤：
步骤S202，接收转发设备发送的网络故障信息；
步骤S204，根据网络故障信息，获取预先存储在控制器中的与网络故障信息对应的故障恢复信息，其中，该故障恢复信息用于对网络故障信息对应的网络故障进行恢复；
步骤S206，将所述故障恢复信息发送给对应的个转发设备。
通过上述步骤，当接收到转发设备上报的网络故障信息后，直接从控制器中获取与该网络故障信息对应的故障恢复信息，再下发给各个转发设备。与相关技术相比，当接收到网络故障信息后不再去生成该故障恢复信息，而是该故障恢复信息预先存储在控制器中，当控制器接收到网络故障信息后，直接从控制器中获取该故障恢复信息，进而解决了相关技术中SDN故障发生后恢复故障时间较长的问题，节省了恢复时间，提高了恢复效率。
需要说明的是，上述方法可以应用于SDN中，该SDN可以包括以太网、MPLS、MPLS-TP、OTN、WDM等相关传送技术的网络，也可以包括采用相似层网络传送技术的传送网络。上述网络故障信息包括：链路故障信息。该链路故障信息可以是链路故障的告警信息，也可以是该链路故障的通知信息等，但并不限于此。该链路故障可以是单重故障，比如网络中只存在一处链路故障，也可以是多重故障，即网络中存在多出链路故障。需要说明的是，链路本身的中断或者转发设备的掉电都可以引起上述链路故障，但并不限于此。
在本发明实施例中，上述故障恢复信息可以包括备用业务路径对应的各个转发设备的转发表项；其中，所述备用业务路径为受网络故障信息影响的业务路径的备用业务路径。需要说明的是，该转发表项可以包括流表和组表 信息至少之一。即预先在控制器中存储有各个故障对应的备用业务路径对应的转发表项信息，当接收到网络故障发生时，比如链路故障发生，通过该网络故障信息检索与该网络故障对应的备用业务路径对应的各个转发设备的转发表项，然后将这些转发表项下发至相应的各个转发设备，进而完成故障的恢复。
图3是根据本发明实施例的故障恢复方法的流程图二，如图3所示，在步骤S206之后，上述方法还可包括：
步骤S302，删除受网络故障信息影响的业务路径。
通过该步骤，将受上述网络故障信息影响的原业务路径删除，可以减少业务路径的数量，同时减少控制器中需要存储的备用路径的信息，进而可以节省存储空间。
需要说明的是，步骤S302也可以在步骤S204之后执行。
另外，上述步骤S302也可以不执行，即也可以保留受网络故障信息影响的业务路径，由于这个受网络故障信息影响的业务路径可能是一个最优业务路径，在保留了该最优业务路径后，如果网络故障消除了，可以不采用该业务路径的备用业务路径，而是可以重新选择采用该最优业务路径。对于是删除还是保留受网络故障信息影响的业务路径，可以根据用户的实际需求来确定，但并不限于此。
在本发明实施例中，图4是根据本发明实施例的故障恢复方法的流程图三，如图4所示，在步骤S202之后，上述方法还包括：
步骤S402，在检测到新增业务路径时，创建与新增业务路径对应的备用业务路径；其中，新增业务路径为受网络故障信息影响的业务路径的备用业务路径；
步骤S404，将新增业务路径所对应备用业务路径的转发流水线所要求的各个转发设备的转发表项存储在所述控制器中。
需要说明的是，一个或者多个转发表项形成一个转发流水线，一个备用业务路径可以对应一个或者多个转发流水线。
通过上述步骤，通过检测到新增业务路径时，将该新增业务路径对应的 备用业务路径的各个转发设备的转发表项添加到控制器中，来动态的维护该控制器中的转发表项信息，以便当该新增业务路径发生故障时能够快速恢复业务。
以SDN中，包含转发设备A、B、C、D，以及一个控制器，当前路径有A-B，A-C，A-D，B-C，B-D，C-D为例，当链路A-B发生故障时，链路A-B的备用业务路径为A-C-B，那么控制器会直接到控制器检索A-C-B对应的A、C和B的转发表项信息，此时有了一个新的业务路径A-C-B，那么应当在该控制器中创建A-C-B的备用业务路径(假设为A-D-C-B)，再将链路为A-D-C-B以及A-D-C-B对应的A、D、C、B的转发表项存储于该控制器中，以使得下一次故障(比如A-C或者A-C和A-B都发生故障)发生时，能够快速恢复。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种控制器，该控制器应用于SDN，图5是根据本发明实施例的控制器的结构框架图一，如图5所示，上述控制器包括：协议处理组件52，恢复管理组件54，表项仓库组件56；
协议处理组件52，设置为将从SDN中的转发设备接收到的网络故障信息，发送给恢复管理组件；
恢复管理组件54，与协议处理组件52和表项仓库组件56连接，设置为根据协议处理组件52发送的网络故障信息，从表项仓库组件56中检索与网络故障信息对应的故障恢复信息，以及将故障恢复信息通过协议处理组件发送给转发设备；其中，表项仓库组件56存储有网络故障信息、故障恢复信息和网络故障信息与故障恢复信息的对应关系。
上述控制器通过在表项仓库组件56中预先存储网络故障信息、故障恢复信息和网络故障信息与故障恢复信息的对应关系，当恢复管理组件54接收到 网络故障信息时，可以直接从表项仓库组件56中获取与该网络故障信息对应的故障恢复信息，而不需要现生成该故障恢复信息，解决了相关技术中SDN故障发生后恢复故障时间较长的问题，节省了恢复时间，提高了恢复的效率。
需要说明的是，上述SDN可以包括以太网、MPLS、MPLS-TP、OTN、WDM等相关传送技术的网络，也可以包括采用相似层网络传送技术的传送网络。上述网络故障信息可以包括：链路故障信息。该链路故障信息可以是链路故障的告警信息，也可以是该链路故障的通知信息等，但并不限于此。该链路故障可以是单重故障，比如网络中只存在一处链路故障，也可以是多重故障，即网络中存在多出链路故障。需要说明的是，链路本身的中断或者转发设备的掉电都可以引起上述链路故障，但并不限于此。
在本发明实施例中，上述故障恢复信息可以包括备用业务路径对应的各个转发设备的转发表项；其中，所述备用业务路径为受网络故障信息影响的业务路径的备用业务路径。需要说明的是，该转发表项可以包括流表和组表信息至少之一。
图6是根据本发明实施例的控制器的结构框架图二，如图6所示，上述控制器还包括：
路径管理组件62，设置为模拟SDN出现的各种故障，对受故障影响的业务路径计算与业务路径对应的备用业务路径；
业务编排组件64，设置为与上述路径管理组件62连接，设置为根据备用业务路径转发流水要求，生成故障恢复信息，以及将故障和故障恢复信息存储于表项仓库组件56中，其中，所述故障恢复信息包括：与备用业务路径相关的各个转发设备的转发表项。
通过该路径管理组件62和业务编排组件64，使得提前模拟故障来计算业务路径的备用业务路径，将该模拟的故障和与该故障对应的备用业务路径信息(即故障恢复信息)存储于表项仓库组件56中，以当故障发生时，直接来获取与该故障对应的故障恢复信息，不用再去计算，节省了恢复的时间。
需要说明的是，上述路径管理组件62，还设置为删除受网络故障信息影响的业务路径。以节省控制器中的存储空间。
另外，该路径管理组件62还可以设置为保留受网络故障信息影响的业务路径。比如这个受网络故障信息影响的该业务路径可能是一个最优业务路径，由于该路径管理组件62对该最优业务路径进行了保留，如果网络故障消除了，则可以不采用该业务路径的备用业务路径，而是重新选择采用该最优业务路径。
需要说明的是，对于该路径管理组件62是删除还是保留受网络故障信息影响的业务路径，可以根据用户的实际需求进行设定，但并不限于此。
图7是根据本发明实施例的控制器的结构框架图三，如图7所示，上述控制器还可包括：
拓扑管理组件72，设置为接收协议处理组件发送的网络故障信息，以及在检测到新增业务路径时，将新增业务路径添加到SDN的网络资源信息中，其中，新增业务路径为受网络故障信息影响的业务路径的备用业务路径。
拓扑管理组件72，在检测到新增业务路径时，将新增业务路径添加到SDN的网络资源信息，然后该业务编排组件64将该新增业务路径对应的备用业务路径的各个转发设备的转发表项添加到表项仓库组件56中，来动态的维护该表项仓库组件56，以便当该新增业务路径发生故障时能够快速恢复业务。
在本实施例中还提供了一种SDN，图8是根据本发明实施例的SDN的结构示意图，如图8所示，该SDN包括：转发设备82和图5至图7任一图所示的控制器84，对于该控制器的解释图5至图7所示的实施例中对控制器的解释，此处不再赘述。
需要说明的是，上述转发设备可以是一个，也可以是多个，并不限于此。
SDN基于对控制器的改进，即通过在表项仓库组件56中预先存储网络故障信息、故障恢复信息和网络故障信息与故障恢复信息的对应关系，当恢复管理组件54接收到网络故障信息时，可以直接从表项仓库组件56中获取与该网络故障信息对应的故障恢复信息，而不需要现生成该故障恢复信息，解决了相关技术中SDN故障发生后恢复故障时间较长的问题，进而节省了恢复时间，提高了恢复的效率。
在本实施例中还提供了一种故障恢复装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图9是根据本发明实施例的故障恢复装置的结构框图一，该装置应用于SDN中，如图9所示，该装置包括：
接收模块902，设置为接收转发设备发送的网络故障信息；
获取模块904，设置为与上述接收模块902连接，设置为根据网络故障信息，获取预先存储在控制器中的与网络故障信息对应的故障恢复信息，其中，该故障恢复信息用于对网络故障信息对应的网络故障进行恢复；
发送模块906，设置为与上述获取模块904连接，设置为将故障恢复信息发送给与故障恢复信息对应的各个转发设备。
通过上述装置，采用当接收到转发设备上报的网络故障信息后，直接从控制器中获取预先存储在与该网络故障信息对应的故障恢复信息，再下发给各个转发设备。该装置当接收到网络故障后不再去直接生成该故障恢复信息，而是将该故障恢复信息预先存储在控制器中，当接收到网络故障信息后，直接从控制器中获取该故障恢复信息，进而解决了相关技术中SDN故障发生后恢复故障时间较长的问题，进而节省了恢复时间，提高了恢复的效率。
需要说明的是，上述SDN可以包括以太网、MPLS、MPLS-TP、OTN、WDM等相关传送技术的网络，也可以包括采用相似层网络传送技术的传送网络。上述网络故障信息包括：链路故障信息。该链路故障信息可以是链路故障的告警信息，也可以是该链路故障的通知信息等，但并不限于此。该链路故障可以是单重故障，比如网络中只存在一处链路故障，也可以是多重故障，即网络中存在多出链路故障。需要说明的是，链路本身的中断或者转发设备的掉电都可以引起上述链路故障，但并不限于此。
图10是根据本发明实施例的故障恢复装置的结构框图二，如图10所示，上述装置还包括：
删除模块1002，设置为与上述发送模块906连接，设置为删除受网络故障信息影响的业务路径。
需要说明的是，上述删除模块1002也可以设置为与上述获取模块904连接，并不限于此。
通过上述删除模块1002将受上述网络故障信息影响的原业务路径删除，可以减少业务路径的数量，同时减少控制器中需要存储的备用路径的信息，进而可以节省存储空间。
需要说明的是，上述装置也可以不包括删除模块1002，而是包括一个保留模块，设置为保留受网络故障信息影响的业务路径，对于上述装置是包括删除模块1002还是包括保留模块，可以根据用户的实际需求进行确定，当然，上述装置也可以同时包括删除模块1002和保留模块，并不限于此。
由于上述保留模块可以保留受网络故障信息影响的业务路径，在使用该保留模块的装置时，如果这个受网络故障信息影响的业务路径是一个最优业务路径，如果网络故障消除了，可以不采用该业务路径的备用业务路径，而是可以重新选择采用该保留模块保留的该最优业务路径。
图11是根据本发明实施例的故障恢复装置的结构框图三，如图11所示，上述装置还包括：
创建模块1102，设置为与上述接收模块902连接，设置为在检测到新增业务路径时，创建与新增业务路径对应的备用业务路径；其中，新增业务路径为受网络故障信息影响的业务路径的备用业务路径；
存储模块1104，设置为与上述创建模块1102连接，设置为将新增业务路径对应的备用业务路径的转发流水线要求的各个转发设备的转发表项存储在控制器中。
通过创建模块1102和存储模块1104，在检测到新增业务路径时，将该新增业务路径对应的备用业务路径的各个转发设备的转发表项添加到控制器中，来动态的维护该控制器中的转发表项信息，以便当该新增业务路径发生故障时能够快速恢复业务。
以SDN中，包含转发设备A、B、C、D，以及一个控制器，当前路径有 A-B，A-C，A-D，B-C，B-D，C-D为例，当链路A-B发生故障时，链路A-B的备用业务路径为A-C-B，那么获取模块1004会直接到控制器检索A-C-B对应的A、C和B的转发表项信息，此时有了一个新的业务路径A-C-B，那么创建模块1202需要在该控制器中创建A-C-B的备用业务路径(假设为A-D-C-B)，再将链路为A-D-C-B以及A-D-C-B对应的A、D、C、B的转发表项存储于该控制器中，以为下一次故障(比如A-C或者A-C和A-B都发生故障)时，能够快速恢复。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
为了更好的理解本发明，以下结合优选的实施例对本发明做进一步解释。
本发明实施例基于控制器现有架构，引入恢复管理组件和表项仓库组件，提出一种快速恢复功能的实施方法，解决相关技术恢复功能时间长的问题，以满足实施包括以太网、MPLS、MPLS-TP、OTN以及WDM等传送技术的网络要求。
图12是根据本发明实施例的SDN的架构示意图，如图12所述，该SDN包括控制器和转发设备，其中，该控制器包括协议处理组件，拓扑管理组件，路径管理组件，业务编排组件，以及新引入的表项仓库组件和恢复管理组件；该转发设备中也包括协议处理组件，告警检测组件，转发组件以及流表组件，该控制器中的上述各个组件与图5至图7中所示实施例的相应的各个组件的功能相同。本实施例的核心内容在于网络故障发生后，协议处理组件快速传递故障信息至恢复管理组件，恢复管理组件根据故障信息检索表项仓库组件，并通过协议处理组件快速下发创建恢复路径的配置信息，具备速度快，恢复效果好的优点。
对于控制器和多台转发设备组成的SDN传送网络，实施快速恢复的功能，因而本发明实施例的快速恢复功能的方法包括：
步骤1，根据当前SDN资源及业务路径配置，转发设备的告警检测组件检测相关元件是否有故障产生？是，则通过转发设备的协议处理组件将故障信息上报控制器，流程转入下一步；否，则重新实施本步骤内容。
步骤2、控制器的协议处理组件接收到故障信息(相当于图1所示实施例中的步骤S302)后，传递至恢复管理组件，同时传递至拓扑管理组件；流程转入下一步。
步骤3、控制器的恢复管理组件依据故障信息检索表项仓库组件(相当于图1所示实施例的步骤S204)，是否检索到期望信息？是，则将检索到的信息通过协议处理组件下发至转发设备(相当于图1所示实施例的步骤S206)，流程转入步骤1；否，则重新实施本步骤内容。
上述步骤1中的相关元件可以包括影响业务正常传送的单元，比如物理链路中断、标签交换路径检测失效等。步骤2中的恢复管理组件在检索到期望信息实施恢复业务操作时或实施恢复业务操作后，路径管理组件也可以触发受故障影响的原业务路径的删除操作。步骤2所述的告警传递至拓扑管理组件，将触发表项仓库组件存储信息的更新，即下文维护表项仓库组件存储信息有效性。
图13是根据本发明实施例的维护表项仓库组件存储信息有效性的方法的流程示意图，如图13所示，维护表项仓库组件存储信息有效性的方法主要包括如下步骤：
步骤S1302、根据当前SDN资源及业务路径配置，控制器的路径管理组件模拟网络出现各种故障，对受故障影响的业务路径，计算其备用路径(相当于上述各实施例中的备用业务路径)；
步骤S1304、基于控制器路径管理组件输出的备用路径，业务编排组件对其实施业务编排，即根据路径各节点设备转发流水生成所需的流表和组表条目等信息(相当于图1所示实施例中的故障恢复信息)，并与网络故障信息一起存储于表项仓库组件；
步骤S1306、控制器的拓扑管理组件检测SDN是否有故障发生，网络资源是否有新增、修改或删除发生？或者路径管理组件检测是否有新增、修改或删除业务及路径操作？是，执行步骤S1308；否，则重新实施本步骤内容。
步骤S1308，更新当前网络拓扑及资源状态，流程转入步骤S1302。
需要说明的是上述的故障或故障信息，包括单重故障(任何时候，网络 都只有一处故障，比如单条链路中断)，多重故障(网络同时或先后发生多个故障，比如多处链路中断，或者节点掉电等)等场景。
上述方法适用于SDN，包括实施以太网、MPLS、MPLS-TP、OTN以及WDM等现有传送技术的网络，也包括采用相似的层网络传送技术的传送网络。
本发明实施例的上述技术方案通过在控制器引入恢复管理组件、表项仓库组件、以及它们与控制器现有组件之间的交互接口，根据转发设备上报的网络故障快速检索备用路径的信息下发至转发设备恢复业务，具备快速、简洁、可靠的优点。
为了加速SDN业务路径的恢复效率，本发明实施例基于SDN基础架构提出了又一个快速恢复功能的实施方法，该优选实施例的核心是SDN控制器引入表项仓库组件、恢复管理组件，以及它们与组件之间的接口；控制器提前模拟故障计算业务路径的备用路径(或恢复路径)，并将备用路径的信息保存于表项仓库组件；当故障发生后，恢复管理组件快速检索表项仓库组件并下发转发信息至转发设备恢复业务。
图14是根据本发明实施例的故障恢复场景的示意图，以图14所述的故障恢复场景为例，即以SDN部署控制器以及A、B、C和D四台SDN转发设备，设备A和B之间的双向业务已经开通，传送路径为A--B，T1时刻链路A<—B方向的光纤中断为例，说明本发明实施例快速恢复的实施方案，图15是根据本发明实施例的根据网络故障实施快速恢复的流程图。
结合图12中的SDN的架构，图14中的故障恢复场景，以及图15的快速恢复的实施方案，本发明实施例快速恢复的实施方案包括以下步骤：
步骤S1502，根据当前SDN资源及业务路径配置，转发设备A、B、C和D的告警检测组件检测本地相关元件是否有故障产生，如果是，执行步骤S1504，如果否，执行本步骤S1602。
步骤S1504，T1时刻链路A<—B方向的光纤中断，A的告警检测组件检测到此链路故障，通过协议处理组件将A--B链路失效的告警上报控制器。A、B、C和D的告警检测组件继续在线检测本地相关元件告警。
步骤S1506，控制器的协议处理组件接收到A上报的A--B链路失效的告警(相当于图2所示实施例的步骤S202)，传递至恢复管理组件，同时传递至拓扑管理组件。
步骤S1508，控制器的恢复管理组件依据A--B链路失效的告警信息检索表项仓库组件(相当于图2所示实施例的步骤S204)；如果检索到期望的信息，即恢复路径A—C—B对应的A、C和B转发表项信息，则执行步骤S1510，如果表项仓库组件没有业务路径A—B对应的恢复路径信息，比如控制器还没有来得及生成恢复路径信息存入表项仓库组件(即没有检索到期望的信息)，则恢复管理组件持续重新检索。。
步骤S1510，分别将A、C、B的信息通过协议处理组件下发至A、C和B转发设备(相当于图2所示实施例的步骤S206)，业务恢复，然后流程转入步骤S1502。
步骤S1508，所述的恢复管理组件实施恢复业务操作时或实施恢复业务操作后，路径管理组件也可以删除受故障影响的原业务路径A-B。
结合图12中的SDN的架构，图14中的故障恢复场景，以及图13的维护表项仓库组件存储信息有效性的方法，以SDN部署控制器以及A、B、C和D四台SDN转发设备，设备A和B之间的双向业务已经开通，传送路径为A--B，T1时刻链路A<—B方向的光纤中断为例，说明本发明实施例的维护表项仓库组件所存储信息有效性的实施方案。
上述实施方案包括如下步骤：
步骤一、根据当前SDN资源，包括A—B、A—C、A—D、B—C、B—D和C—D链路，A、B、C、D四台转发设备以及业务路径A—B，告警检测组件检测本地相关元件是否有故障产生。控制器路径管理组件模拟网络所述各链路分别故障，或者各节点分别故障时，找到受故障影响的业务路径，计算备用路径(相当于上述的备用业务路径)。当A-B链路故障时，双向业务的A-B路径会受故障影响，计算出备用路径A-C-B。
步骤二、基于控制器路径管理组件输出的当A-B链路故障，A-B路径受影响转发设备的转发流水要求，生成A、C和B的转发表项，比如各级流表、 组表等信息。这些信息与A-B链路故障信息一起存储与表项仓库组件，以便根据故障来快速检索相关备用路径转发信息。
步骤三、控制器的拓扑管理组件在T1时刻检测到A-B链路故障；路径管理组件检测到新增A-C-B业务路径。拓扑管理组件更新SDN资源信息，包括A—C、A—D、B—C、B—D和C—D链路，A、B、C、D四台转发设备以及业务路径A—C—B，A-B。执行技术方案步骤一所述内容。
特别地，上述步骤三执行完毕，A-C-B新的备用路径将被创建(比如A-D-C-B)，可以在下一次故障(比如A-C链路中断)时，再次快速恢复业务。这是本发明实施例针对多重故障(A-B、A-C链路都故障)的应用，虽然没有在上述步骤一、二、三显示描述。
特别地，上述步骤三，如果实施了快速恢复方案所述的删除故障路径A-B，则步骤三拓扑管理组件更新SDN资源信息不再包括业务路径A-B。
需要说明的是，上述实施例中的控制器的协议处理组件，表项仓库组件，恢复管理组件，拓扑管理组件，路径管理组件以及业务编排组件，与图6至图8中的控制器中的协议处理组件，表项仓库组件，恢复管理组件，拓扑管理组件，路径管理组件以及业务编排组件完成的功能相似。
本发明实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，接收转发设备发送的网络故障信息；
S2，根据网络故障信息，获取预先存储在控制器中的与网络故障信息对应的故障恢复信息，其中，该故障恢复信息用于对网络故障信息对应的网络故障进行恢复；
S3，将故障恢复信息发送给与故障恢复信息对应的各个转发设备。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
工业实用性
本发明实施例提供了一种故障恢复方法及装置、控制器、软件定义网络，以至少解决相关技术中SDN故障发生后恢复故障时间较长的问题。其中，所述故障恢复方法，应用于SDN，包括：接收转发设备发送的网络故障信息；根据所述网络故障信息，获取预先存储在控制器中的与所述网络故障信息对应的故障恢复信息，其中，该故障恢复信息用于对所述网络故障信息对应的网络故障进行恢复；将所述故障恢复信息发送给与所述故障恢复信息对应的各个转发设备。
本发明实施例不仅节省了恢复时间，提高了恢复的效率。

Claims (18)

  1. 一种故障恢复方法，应用于软件定义网络SDN，包括：
    接收转发设备发送的网络故障信息；
    根据所述网络故障信息，获取预先存储在控制器中的与所述网络故障信息对应的故障恢复信息，其中，该故障恢复信息用于对所述网络故障信息对应的网络故障进行恢复；
    将所述故障恢复信息发送给与所述故障恢复信息对应的各个转发设备。
  2. 根据权利要求1所述的方法，其中，所述网络故障信息包括：链路故障信息。
  3. 根据权利要求1所述的方法，其中，所述故障恢复信息包括：备用业务路径对应的所述各个转发设备的转发表项；其中，所述备用业务路径为受所述网络故障信息影响的业务路径的备用业务路径。
  4. 根据权利要求1所述的方法，在将所述故障恢复信息发送给与所述恢复故障信息对应的各个转发设备之后，还包括：
    删除受所述网络故障信息影响的业务路径。
  5. 根据权利要求1至4中任一项所述的方法，在接收转发设备发送的网络故障信息之后，还包括：
    在检测到新增业务路径时，创建与所述新增业务路径对应的备用业务路径；其中，所述新增业务路径为受所述网络故障信息影响的业务路径的备用业务路径；
    将所述新增业务路径所对应备用业务路径的转发流水线所要求的各个所述转发设备的转发表项存储在所述控制器中。
  6. 一种控制器，应用于软件定义网络SDN，所述控制器包括：协议处理组件，恢复管理组件，表项仓库组件；其中，
    所述协议处理组件，设置为将从软件定义网络SDN中的转发设备接收到的网络故障信息，发送给所述恢复管理组件；
    所述恢复管理组件，设置为根据所述协议处理组件发送的所述网络故障 信息，从所述表项仓库组件中检索与所述网络故障信息对应的故障恢复信息，以及将所述故障恢复信息通过所述协议处理组件发送给所述转发设备；其中，所述表项仓库组件存储有所述网络故障信息、所述故障恢复信息和所述网络故障信息与所述故障恢复信息的对应关系。
  7. 根据权利要求6所述的控制器，其中，所述网络故障信息包括：链路故障信息。
  8. 根据权利要求6所述的控制器，其中，所述故障恢复信息包括：备用业务路径对应的各个所述转发设备的转发表项；其中，所述备用业务路径为受所述网络故障信息影响的业务路径的备用业务路径。
  9. 根据权利要求6所述的控制器，还包括：
    路径管理组件，设置为模拟所述SDN出现的各种故障，对受所述故障影响的业务路径计算与所述业务路径对应的备用业务路径；
    业务编排组件，设置为根据所述备用业务路径转发流水要求，生成所述故障恢复信息，以及将所述故障和所述故障恢复信息存储于所述表项仓库组件中，其中，所述故障恢复信息包括：与所述备用业务路径相关的各个转发设备的转发表项。
  10. 根据权利要求9所述的控制器，还包括：
    拓扑管理组件，设置为接收所述协议处理组件发送的所述网络故障信息，以及在检测到新增业务路径时，将所述新增业务路径添加到所述SDN的网络资源信息中，其中，所述新增业务路径为受所述网络故障信息影响的业务路径的备用业务路径。
  11. 根据权利要求9所述的控制器，
    所述路径管理组件，还设置为删除受所述网络故障信息影响的业务路径。
  12. 一种软件定义网络SDN，包括：转发设备和权利要求6至11中任一项所述的控制器。
  13. 一种故障恢复装置，应用于软件定义网络SDN，包括：
    接收模块，设置为接收转发设备发送的网络故障信息；
    获取模块，设置为根据所述网络故障信息，获取预先存储在控制器中的与所述网络故障信息对应的故障恢复信息，其中，该故障恢复信息设置为对所述网络故障信息对应的网络故障进行恢复；
    发送模块，设置为将所述故障恢复信息发送给与所述故障恢复信息对应的各个转发设备。
  14. 根据权利要求13所述的装置，其中，所述网络故障信息包括：链路故障信息。
  15. 根据权利要求14所述的装置，其中，所述故障恢复信息包括：备用业务路径对应的所述各个转发设备的转发表项；其中，所述备用业务路径为受所述网络故障信息影响的业务路径的备用业务路径。
  16. 根据权利要求13所述的装置，还包括：
    删除模块，设置为删除受所述网络故障信息影响的业务路径。
  17. 根据权利要求13至16中任一项所述的装置，还包括：
    创建模块，设置为在检测到新增业务路径时，创建与所述新增业务路径对应的备用业务路径；其中，所述新增业务路径为受所述网络故障信息影响的业务路径的备用业务路径；
    存储模块，设置为将所述新增业务路径所对应备用业务路径的转发流水线所要求的各个所述转发设备的转发表项存储在所述控制器中。
  18. 一种存储介质，被设置为存储用于执行以下步骤的程序代码：
    接收转发设备发送的网络故障信息；
    根据网络故障信息，获取预先存储在控制器中的与网络故障信息对应的故障恢复信息，其中，该故障恢复信息用于对网络故障信息对应的网络故障进行恢复；
    将故障恢复信息发送给与故障恢复信息对应的各个转发设备。
PCT/CN2016/094675 2015-11-30 2016-08-11 故障恢复方法及装置、控制器、软件定义网络 WO2017092400A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP16869711.8A EP3386156B1 (en) 2015-11-30 2016-08-11 Failure recovery method, device and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510863471.X 2015-11-30
CN201510863471.XA CN106817301A (zh) 2015-11-30 2015-11-30 故障恢复方法及装置、控制器、软件定义网络

Publications (1)

Publication Number Publication Date
WO2017092400A1 true WO2017092400A1 (zh) 2017-06-08

Family

ID=58796166

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/094675 WO2017092400A1 (zh) 2015-11-30 2016-08-11 故障恢复方法及装置、控制器、软件定义网络

Country Status (3)

Country Link
EP (1) EP3386156B1 (zh)
CN (1) CN106817301A (zh)
WO (1) WO2017092400A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10652084B2 (en) 2018-05-01 2020-05-12 At&T Intellectual Property I, L.P. Service recovery in a software defined network
US10880370B2 (en) 2018-11-27 2020-12-29 At&T Intellectual Property I, L.P. Virtual network manager system

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109818762B (zh) * 2017-11-20 2022-03-08 中国电信股份有限公司 用于实现sdn控制器自动注册的方法、适配器和***
CN109165141A (zh) * 2018-08-10 2019-01-08 武汉优品楚鼎科技有限公司 一种计算机***运维可视化监控方法、***及装置
CN109640195A (zh) * 2018-11-16 2019-04-16 中国电力科学研究院有限公司 一种面向电力通信光传输网大规模场景的仿真方法及***
CN111200506B (zh) * 2018-11-19 2023-08-29 中兴通讯股份有限公司 一种故障感知方法及装置和控制器
CN109756365B (zh) * 2018-12-12 2022-04-01 深圳供电局有限公司 一种电力通信网络的故障分析方法及***
CN111404734B (zh) * 2020-03-06 2021-03-19 北京邮电大学 一种基于配置迁移的跨层网络故障恢复***及方法
CN111782137A (zh) * 2020-06-17 2020-10-16 杭州宏杉科技股份有限公司 路径故障处理方法及装置
CN112671946B (zh) * 2020-12-25 2023-04-25 中盈优创资讯科技有限公司 一种基于sdn的地址转换实现方法
CN114866403B (zh) * 2021-01-18 2023-05-30 株洲中车时代电气股份有限公司 一种基于ttdp协议的列车骨干网节点故障恢复方法及装置
CN113055084B (zh) * 2021-03-19 2022-04-26 烽火通信科技股份有限公司 一种光网络业务故障恢复的方法和***
CN113727221B (zh) * 2021-08-13 2023-06-23 烽火通信科技股份有限公司 一种光网络智能控制方法、装置及***

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102946325A (zh) * 2012-11-14 2013-02-27 中兴通讯股份有限公司 一种基于软件定义网络的网络诊断方法、***及设备
CN103428031A (zh) * 2013-08-05 2013-12-04 浙江大学 一种基于软件定义网络的域间链路快速故障恢复方法
CN104184608A (zh) * 2013-05-22 2014-12-03 富士通株式会社 数据发送装置、方法和非易失性计算机可读存储介质
CN104426731A (zh) * 2013-08-23 2015-03-18 杭州华三通信技术有限公司 一种生成树计算的方法和装置
CN104753828A (zh) * 2013-12-31 2015-07-01 华为技术有限公司 一种sdn控制器、数据中心***和路由连接方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102118687B1 (ko) * 2013-11-15 2020-06-03 삼성전자주식회사 SDN(Software-defined networking)에서 네트워크 장애 해소를 위한 컨트롤러 및 스위치의 동작 방법과, 이를 위한 컨트롤러 및 스위치
US9253026B2 (en) * 2013-12-18 2016-02-02 International Business Machines Corporation Software-defined networking disaster recovery
CN106464589B (zh) * 2014-05-12 2020-04-14 华为技术有限公司 Ip网络中的部分软件定义网络交换机替换的方法和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102946325A (zh) * 2012-11-14 2013-02-27 中兴通讯股份有限公司 一种基于软件定义网络的网络诊断方法、***及设备
CN104184608A (zh) * 2013-05-22 2014-12-03 富士通株式会社 数据发送装置、方法和非易失性计算机可读存储介质
CN103428031A (zh) * 2013-08-05 2013-12-04 浙江大学 一种基于软件定义网络的域间链路快速故障恢复方法
CN104426731A (zh) * 2013-08-23 2015-03-18 杭州华三通信技术有限公司 一种生成树计算的方法和装置
CN104753828A (zh) * 2013-12-31 2015-07-01 华为技术有限公司 一种sdn控制器、数据中心***和路由连接方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3386156A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10652084B2 (en) 2018-05-01 2020-05-12 At&T Intellectual Property I, L.P. Service recovery in a software defined network
US11463304B2 (en) 2018-05-01 2022-10-04 At&T Intellectual Property I, L.P. Service recovery in a software defined network
US10880370B2 (en) 2018-11-27 2020-12-29 At&T Intellectual Property I, L.P. Virtual network manager system
US11451624B2 (en) 2018-11-27 2022-09-20 At&T Intellectual Property I, L.P. Virtual network manager system

Also Published As

Publication number Publication date
EP3386156A4 (en) 2018-12-12
EP3386156A1 (en) 2018-10-10
EP3386156B1 (en) 2022-07-13
CN106817301A (zh) 2017-06-09

Similar Documents

Publication Publication Date Title
WO2017092400A1 (zh) 故障恢复方法及装置、控制器、软件定义网络
US20200267069A1 (en) Link switching method, link switching device, network communication system, and computer-readable storage medium
CN104205748B (zh) 具有协调的业务方向的机架间冗余
US8856584B2 (en) Transport control server that modifies routing information
US10708184B2 (en) Switching primary/backup pseudowire
US20090201831A1 (en) Vpls n-pe redundancy using pseudo wire fast failover
CN103634423B (zh) 一种基于三层接口的mpls‑tp配置方法及装置
US10862735B2 (en) Method and apparatus for implementing operation, administration, and maintenance function
CN112218321B (zh) 主备链路切换方法、装置、通信设备和存储介质
US20150186202A1 (en) Method and Device for Sending Inter-Domain Fault Information
US20140050092A1 (en) Load sharing method and apparatus
CN102325080B (zh) 一种ospf协议平滑重启方法和装置
CN105634952A (zh) Lsp报文快速通告方法以及装置
WO2018107974A1 (zh) 一种路由回切方法、控制器及***
CN102055676B (zh) Mstp组网环境中实现负载分担的方法及装置
CN101340377B (zh) 一种用于二层网络数据传输的方法、装置及其***
CN104702498A (zh) 一种通过协调保护减少设备间光连接数量的方法及装置
JP6383232B2 (ja) 中継システムおよびスイッチ装置
WO2014029287A1 (zh) 隧道负荷分担方法及装置
WO2014101125A1 (zh) 聚合组链路协商方法、装置和***
CN103414642A (zh) 一种转发信息维护方法及设备
WO2012106914A1 (zh) 动态隧道故障诊断方法及设备和***
CN105790984B (zh) 一种操作维护管理功能的配置、实现方法及转发设备
JP6042838B2 (ja) 管理システム、管理サーバ、および管理方法
CN103607301A (zh) 一种ecmp方式下链路故障的保护切换方法和设备

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: 16869711

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016869711

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016869711

Country of ref document: EP

Effective date: 20180702