WO2019134572A1 - Procédé et dispositif de récupération de protection de réseau de transport optique à base de sdn et support de stockage - Google Patents

Procédé et dispositif de récupération de protection de réseau de transport optique à base de sdn et support de stockage Download PDF

Info

Publication number
WO2019134572A1
WO2019134572A1 PCT/CN2018/124045 CN2018124045W WO2019134572A1 WO 2019134572 A1 WO2019134572 A1 WO 2019134572A1 CN 2018124045 W CN2018124045 W CN 2018124045W WO 2019134572 A1 WO2019134572 A1 WO 2019134572A1
Authority
WO
WIPO (PCT)
Prior art keywords
recovery
protection
path
domain
route calculation
Prior art date
Application number
PCT/CN2018/124045
Other languages
English (en)
Chinese (zh)
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 中国移动通信有限公司研究院
Publication of WO2019134572A1 publication Critical patent/WO2019134572A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/03—Arrangements for fault recovery
    • H04B10/032—Arrangements for fault recovery using working and protection systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0005—Switch and router aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0079—Operation or maintenance aspects
    • H04Q2011/0081—Fault tolerance; Redundancy; Recovery; Reconfigurability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0086—Network resource allocation, dimensioning or optimisation

Definitions

  • the present invention relates to the field of optical fiber communication technologies, but is not limited to the field of optical fiber communication technologies, and in particular, to an optical transmission network protection recovery method, device, and storage medium based on a Software Defined Network (SDN).
  • SDN Software Defined Network
  • Optical transport networks based on SDN centralized control architecture have been widely used.
  • the Open Networking Foundation defines an information interaction model for optical transport networks that can be used to describe all network resources.
  • the embodiments of the present application are expected to provide an SDN-based optical transport network protection recovery method, device, and storage medium.
  • the first aspect of the embodiments of the present application provides an SDN-based optical transport network protection and recovery method, which is applied to a controller, and includes:
  • a protection path or a recovery path is configured.
  • a second aspect of the embodiments of the present application provides a controller, including:
  • An obtaining unit configured to obtain information of a recovery constraint object in an Open Network Foundation ONF model, where the recovery constraint object includes at least: a protection recovery scope field;
  • a route calculation unit configured to perform route calculation according to the information of the recovery constraint object
  • a configuration unit configured to configure a protection path or a recovery path according to the result of the route calculation.
  • a third aspect of the embodiments of the present application provides a controller, including: a network interface, a memory, a processor, and a computer program stored on the memory and executed by the processor;
  • the processor is connected to the network interface and the memory, respectively, for implementing the SDN-based optical transport network protection recovery method provided by the foregoing one or more technical solutions by executing the computer program.
  • a fourth aspect of the embodiments of the present application provides a computer storage medium, where the computer storage medium stores a computer program; after the computer program is executed, the SDN-based optical transport network protection and recovery provided by the foregoing one or more technical solutions can be implemented. method.
  • the embodiment of the present invention provides an SDN-based optical transport network protection and recovery method, device, and storage medium.
  • the controller can obtain at least a recovery constraint object including a protection recovery range field from the ONF recovery constraint object, and perform route calculation, so triggering
  • the information calculated by the route is carried in the ONF message transmitted between the controllers, and the ONF message is a message transmission supported by devices of different vendors, thereby solving the problem of poor interoperability in the prior art.
  • the problem of poor interoperability is solved and it is determined that the calculation is based on the ONF message.
  • the controller that is most suitable for the current protection path or the recovery path calculation may be selected according to the protection recovery range field, thereby optimizing the route calculation of the protection path or the restoration path, thereby realizing Resource configuration optimization and effect optimization for protection of working paths.
  • FIG. 1 is a schematic flowchart of a first SDN-based optical transport network protection and recovery method according to an embodiment of the present application
  • FIG. 2 is a system architecture diagram provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a controller according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart of a second SDN-based optical transport network protection and recovery method according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a third SDN-based optical transport network protection and recovery method according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart diagram of a fourth SDN-based optical transport network protection and recovery method according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of a fifth SDN-based optical transport network protection and recovery method according to an embodiment of the present disclosure
  • FIG. 8 is a schematic flowchart of a sixth SDN-based optical transport network protection and recovery method according to an embodiment of the present disclosure
  • FIG. 9 is a schematic flowchart of a seventh SDN-based optical transport network protection and recovery method according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic flowchart of an eighth SDN-based optical transport network protection and recovery method according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic flowchart diagram of a DC SDN-based optical transport network protection and recovery method according to an embodiment of the present disclosure.
  • the embodiment provides an SDN-based optical transport network protection recovery method, which is applied to a controller, and includes:
  • Step S110 Acquire information of a recovery constraint object in an Open Network Foundation ONF model, where the recovery constraint object includes at least: a protection recovery scope field;
  • Step S120 Perform route calculation according to the information of the recovery constraint object.
  • Step S130 Configure a protection path or a recovery path according to the result of the route calculation.
  • the controller may be an SC or a DC.
  • the one DC controls one domain; the SC is connected to multiple DCs and controls multiple domains at the same time.
  • FIG. 2 is a schematic structural diagram of an SDN network provided by an embodiment of the present application.
  • the A domain DC controls the A domain
  • the B domain DC controls the B domain.
  • the DC connects to the SC through the northbound borrowing.
  • the SC can control the A domain and the B domain at the same time, and can uniformly schedule network resources in the A domain and the B domain.
  • the A domain and the B domain may be metropolitan area networks of different cities, or one may be a miniaturized domain within a group based on an enterprise or a government, and the other is a metropolitan area network.
  • the SC may receive information of the recovery constraint object from a management device connected thereto or from a human-machine interaction interface, or query information of the recovery constraint object from an ONF model database.
  • the information of the recovery constraint object includes one or more fields, and the field defines various parameters for eliminating the service failure by switching the protection path or the recovery path when the working path of the service data is faulty.
  • the information of the recovery constraint object includes at least a protection recovery scope field, and the field is one field or multiple fields. If a field can be used to indicate the range, specifically the scope of protection or the range of responses can be determined by combining the type field.
  • the protection recovery range field may be two fields, one is a protection scope field for indicating a range in which the protection path is located, and the other is a recovery scope field for indicating a range of the restoration path.
  • the range may be single domain or cross domain. For example, if the end-to-end protection is used, the protection scope is cross-domain, and all the domains that the working path corresponding to the protection path passes through.
  • the single-domain only the protection of the domain through which the working path passes is required.
  • Multiple domains coordinate for protection.
  • the working path is in the A domain, the B domain, and the C domain.
  • the protection path is configured in the A domain, the B domain, and the C domain.
  • the fault point of the current working path is located in the A domain
  • the service data is switched
  • the traffic data on the working path in the A domain is switched to the protection path of the A domain, and the B domain is transmitted.
  • the C domain still uses the original working path for transmission, and there is no need to switch between the working path and the protection path.
  • the protection path is a pre-configured reserved path. For example, after calculating the route of the protection path, according to the result of the route calculation, the transmission resource of the protection path is reserved, for example, the transmission bandwidth, etc. Once the fault is detected, you can switch directly to the protection path.
  • the recovery path may be that the route is calculated first, but the network resource is not allocated in advance to configure the path.
  • the network resource is allocated based on the pre-calculated route to implement the configuration of the recovery path. After the configuration of the recovery path is completed, the service data transmitted on the failed working path is switched to the recovery for transmission.
  • the route of the restoration path is not necessarily calculated in advance, but the route calculation is performed when the fault is detected, and the network resource allocation is implemented based on the route calculation to implement the restoration path configuration, and after the restoration path configuration is completed, the route is performed. Switching transmission of business data.
  • the calculated route may include: a domain through which the two ends of the service transmission pass, a forwarding node in the domain, a port of the transit node, and the like.
  • the SC and the DC in the step S130 acquire the protection recovery range field, it may be determined whether the route calculation is required. For example, if the global end-to-end protection is performed, the SC itself needs to perform route calculation. If the SC is only based on the single-domain protection, the SC only needs to send the ONF message carrying the protection recovery range field to the corresponding DC.
  • the route calculation in the domain can be performed by the DC. Therefore, first, the protection recovery range word can be used to indicate an execution subject that performs routing calculation, and the execution subject can be an SC or a DC. In this case, even if the devices of different manufacturers receive the ONF message, they know whether they need to participate in the calculation of the route, so that the calculation can be avoided and the calculation can be performed preferentially.
  • the devices of different vendors support the interaction and identification of ONF messages in the ONF model. Therefore, the problem of poor interoperability is solved.
  • the ONF message is directly equivalent to indicating whether the corresponding controller performs route calculation. If it needs to be executed, it is equivalent to the implementation. Coordination between devices from different vendors avoids double counting and can select the best execution subject for route calculation to optimize the protection recovery.
  • the information of the recovery constraint object is carried by the ONF message between the controllers for transmission, so the compatibility with the prior art is strong, and the interaction between the SC and the DC can be easily performed; Unnecessary calculation and waste of resources, the optimal configuration of protection recovery in the entire network is realized, and the optimization of protection and recovery of fault cancellation is realized.
  • the protection recovery range field is used to determine the scope of protection recovery and/or the execution subject of the route calculation.
  • the step S120 may include: when the protection recovery range field indicates end-to-end protection recovery, the inter-domain controller SC performs a route calculation;
  • the step S130 may include: performing resource configuration of the pre-configured protection path or the recovery path according to the route calculation performed by the SC, and sending the configuration information of the resource configuration to the domain controller DC of each domain. .
  • the route calculated by the SC is superior to the route calculated by a single DC.
  • the SC may consider different The load of the domain, select the domain through which the protection path or recovery path passes, select the port to be transmitted between the domain and the domain according to the load between the different domain ports, avoid the domain with high load or disconnect, and thus obtain the protection path or recovery.
  • the path can reduce the congestion of the service data transmission process, and avoid further increasing the busyness of the busy domain or forwarding device or port, thereby reducing the delay of the service data, thereby optimizing the configuration of the protection path or the recovery path.
  • the configuration information of the resource configuration of the protection path or the recovery path is sent to the DC of the domain that the protection path or the recovery path needs to pass, and is determined by the DC according to the The configuration information is used for resource configuration, thereby completing the configuration of the protection path or the recovery path.
  • the route calculation is performed as DC, and the resource configuration of the protection path or the restoration path is also performed.
  • DC Because the domain-by-domain protection is complete, the domain and the domain can be completely independent. In this case, unnecessary information interaction between the SC and the DC can be reduced, and the delay caused by the information interaction is reduced.
  • the DC performs route calculation of the local domain, and performs configuration of the protection path or the recovery path based on the result of the route calculation.
  • the step S120 may include: when the protection recovery range field is the domain-by-domain protection recovery, the DC calculates the route calculation of the local domain; the step S130 may include: according to the result of the route calculation performed by the DC, Configure the protection path or recovery path in this domain.
  • the step S110 may include: receiving an ONF message carrying information of the recovery constraint object from the SC.
  • the protection constraint object further includes: a protection recovery type field; wherein the protection recovery type field is used to determine a route calculation mode of the protection path or the restoration path.
  • the protection recovery type field substantially indicates the type of protection recovery, for example, may include: 1+1 protection, dynamic reroute recovery, or preset route recovery.
  • the 1+1 protection is pre-configured with a protection path, and the protection path and the working path are 1:1 configured, that is, one protection path is configured with one protection path.
  • the execution subject of the route calculation is SC.
  • the protection recovery type field is to indicate dynamic reroute recovery, the DC of each domain that the work path passes may be performed by performing the route calculation.
  • the protection recovery type field indicates that the recovery type is the preset configuration, the route is pre-calculated by the SC, and the configuration information for performing the restoration path configuration is sent to the DC.
  • the protection recovery type field is also used to indicate when protection and recovery are taking place.
  • the step S120 may include one or more of the following alternatives.
  • the step S120 may include:
  • the path of the protection path or the recovery path of the working path is calculated after detecting the working path failure. If you want to save network resources and avoid waste of resources by pre-configuring routing resources, you can use dynamic rerouting for route calculation of recovery path of service data with large transmission delay. Therefore, in order to reduce unnecessary calculation, you can appear in the working path.
  • the route calculation of the recovery path is performed only when the fault occurs. Generally, if the probability of occurrence of the fault is small, the calculation amount and the computational resources consumed by the route calculation can be greatly reduced.
  • the route calculation by the SC requires further delay caused by the information exchange with the DC for routing calculation, in this implementation.
  • DC is preferred for route calculation, and in the case of failure due to dynamic rerouting,
  • the step S120 may include:
  • the route of the protection path or the recovery path of the working path is calculated before the calculation of the working path failure.
  • the protection recovery type field indicates that the recovery type is a preset re-routing, that is, the route of the restoration path is pre-configured, that is, the calculation is performed before the failure of the working path occurs, so the pre-computation recovery is required in the implementation force.
  • the route of the path Normally, when the route of the working path is calculated, the route of the recovery path can be calculated synchronously. Alternatively, after completing the route calculation of the working path, when the service data is transmitted by using the working path, the route calculation of the recovery path is started.
  • the step S130 may include:
  • the route of the protection path is calculated in advance.
  • the protection type is a permanent 1+1 protection mode, which indicates that a protection path always exists in a working path. Therefore, before the working path starts to transmit service data, it is necessary to pre-calculate the route of the protection path and complete the protection path. Configuration. If the data transmission on the working path is switched to the currently available protection path for transmission, the protection path of the path of the current transmission service data needs to be calculated immediately to ensure a highly reliable path.
  • the current working path is to use the recovery path for service guarantee or the protection path for service guarantee, and may be determined according to the quality of service (QoS) of the service data and the transmission delay requirement.
  • QoS quality of service
  • the reliability of the protection path is the highest and the delay of the service switching is small, and the reliability of the recovery path is slightly lower and the delay is larger.
  • the recovery path is used, it is divided into dynamic re-routing and pre-re-routing. The reliability of dynamic routing is lower than that of domain-to-reroute, and the delay of dynamic re-routing is greater than the delay of preset re-routing. Therefore, when determining the protection recovery type field in the information of the recovery constraint object, comprehensive configuration may be performed according to parameters such as QoS of service data and/or allowed transmission delay.
  • this embodiment provides a controller, including:
  • the obtaining unit 110 is configured to acquire information of a recovery constraint object in an Open Network Foundation ONF model, where the recovery constraint object includes at least: a protection recovery scope field;
  • the route calculation unit 120 is configured to perform route calculation according to the information of the recovery constraint object
  • the configuration unit 130 is configured to configure a protection path or a recovery path according to the result of the route calculation.
  • the controller may be the foregoing SC or DC
  • the obtaining unit 110 may include information that the network interface may receive the recovery constraint object from other devices, or may include a human-computer interaction interface receiving management input. The information of the recovery constraint object.
  • the route calculation unit 120 may correspond to a processor and may be configured to perform route calculation according to a network topology condition.
  • the configuration unit 130 can also be corresponding to the processor, and can be used to continue the configuration of the protection path or the recovery path through the configuration of the network resource, for example, the port configuration and/or the port configuration, so that the service data is paired through the protection path.
  • the working path is protected, and the recovery of the service data is resumed when the working path fails, thereby realizing the protection and recovery of the service data transmission.
  • the protection recovery range field is used to determine the scope of protection recovery and/or the execution subject of the route calculation.
  • the controller may be an inter-domain controller; the route calculation unit 120 is configured to perform route calculation when the protection recovery range field indicates end-to-end protection recovery; the configuration unit 130 is configured to use, according to the SC The route calculation is performed, and the resource configuration of the pre-configured protection path or the recovery path is performed, and the configuration information of the resource configuration is sent to the domain controller DC of each domain.
  • the controller may be a DC
  • the route calculation unit 120 is configured to calculate a route calculation of the local domain when the protection recovery range field is a domain-by-domain protection recovery; the configuration unit 130. Specifically, configured to configure a protection path or a recovery path in the local area according to a result of the route calculation performed by the DC.
  • the acquiring unit 110 is specifically configured to receive, from the SC, an ONF message carrying information of the recovery constraint object.
  • the protection constraint object further includes: a protection recovery type field; wherein the protection recovery type field is used to perform an execution entity of the route calculation.
  • the controller when the protection recovery type field indicates that the recovery type is dynamic reroute recovery, the controller is a DC, and the route of the restoration path is calculated by the route calculation unit 120 of the DC.
  • the controller when the protection recovery type field indicates that the recovery type is preset reroute recovery, the controller is an SC, and the route of the restoration path is calculated by the route calculation unit 120 of the SC;
  • the controller when the protection recovery type field indicates that the protection type is a permanent 1+1 protection mode, the controller is an SC, and the route of the protection path is calculated by the route calculation unit 120 of the SC.
  • the protection recovery type field is further configured to determine a route calculation mode of the protection path or the restoration path;
  • the route calculation unit 120 is specifically configured to: when the protection recovery type field indicates that the recovery type is dynamic reroute recovery, calculate a route of the recovery path after detecting a working path failure; and/or, when The protection recovery type field indicates that when the recovery type is preset reroute recovery, the route of the restoration path is calculated before calculating the working path failure; and/or, when the protection recovery type field indicates that the protection type is permanent 1+1 protection mode At the time, the route of the protection path is calculated in advance.
  • the protection recovery range field includes a protection scope field for indicating a range of the protection path, and a recovery range field for indicating a range of the restoration path.
  • the embodiment of the present application further provides a controller, which may include: a network interface 210, a memory 220, a processor 230, and a computer program stored on the memory 220 and executed by the processor 230;
  • the processor 230 is connected to the network interface 210 and the memory 220, respectively, for implementing the SDN-based optical transport network protection recovery method by implementing the computer program to implement the foregoing one or more technical solutions.
  • the network interface 210 in this embodiment may correspond to various types of interfaces, such as cable interfaces or fiber optic cable interfaces.
  • the memory 220 can include devices that store various information.
  • the processor 230 may include: a central processing unit, a microprocessor, a digital signal processor, an application processor, a programmable array or an application specific integrated circuit, etc., and may be applied to the execution by computer executable instructions such as a computer program. In a power control method for a beam in a communication device.
  • the processor 230 can be coupled to the transceiver 310 and the memory via a communication bus (e.g., an integrated circuit bus).
  • a communication bus e.g., an integrated circuit bus
  • the embodiment provides a computer storage medium, where the computer storage medium stores a computer program, and the computer program is executed to execute the SDN-based optical transport network protection and recovery method provided by the foregoing one or more technical solutions.
  • the ResilienceType object in the ResilienceConstraint object in the ONF model contains a ResilienceType type object. Specify the protection/recovery type and policy for a specific service by resilienceType.
  • the current ResilienceType is defined as follows:
  • the current field definition is insufficient to meet the requirements of the multi-domain protection recovery strategy.
  • This proposal extends the resilienceType and adds a protectionRange field and a restoreRange field to indicate the scope of execution protection and the scope of execution recovery, that is, the scope of the protection path and the scope of the recovery path. Is an end-to-end cross-domain or single-domain scope.
  • the ResilienceType is as follows, and the protection recovery type of the service is identified by three fields: resilienceType, protectionRange, and restoreRange.
  • SC-related field is as follows (end-to-end protection service needs to occupy 3 Service End Point (SEP) ports in the domain):
  • the protection/recovery types usually have permanent 1+1, dynamic reroute recovery, and 1+1 reroute recovery.
  • This proposal mainly defines the interaction mechanism between DC and SC for the above three protection types.
  • the scheme of protection type for permanent 1+1 protection can be as follows:
  • the service identifiers of the DC and SC are E2E.
  • this example uses the cross-domain end-to-end protection scheme in which the protection path is calculated by the SC in the permanent 1+1 protection mode. This solution not only ensures the global optimization of the path, but also does not affect the service switching time.
  • the device uses a dual-issue selection mechanism, that is, the device sends data signals on both the working and protection paths, and the receiver selects the signal with better quality. In this mode, after the device detects an alarm, the receiver directly switches to the protection port, and the sender does not need to switch.
  • the permanent 1+1 protection mode is performed by the device after the fault occurs, and the alarm of the fault is reported to the DC, and then reported to the SC by the DC. Since it is a hardware direct handover, there is no need to wait for a signaling response, so the service interruption time can be guaranteed to be less than 50 ms.
  • the DC and the SC receive the fault alarm and do not need to send any signaling for service switching. However, for the permanent 1+1 mode, the SC needs to recalculate a protection path after the working path fails.
  • the parameters of the DC side are configured as follows:
  • the scheme for recovery type reroute recovery can be as follows:
  • Reroute recovery includes dynamic rerouting and pre-reroute.
  • the controller calculates the rerouting in real time after detecting the fault; in the preset rerouting mode, the controller calculates the rerouting while the service is being sent, and saves it in the system database, and does not occupy the actual device resources. After the fault occurs, the service is directly switched to the pre-calculated re-routing.
  • this example adopts a domain-by-domain recovery scheme of re-routing by DC calculation.
  • the device detects a fault, the device does not switch because the dual-issue selection is not configured.
  • the alarm is directly submitted to the DC.
  • the DC of the fault domain calculates the intra-domain rerouting scheme according to the restoreType field, and the other domains do not take any action. Since per-domain rerouting is configured, the SC does not calculate rerouting after receiving an alert.
  • the corresponding parameters of the SC end are configured as follows:
  • the configuration parameters of the DC side are as follows:
  • this example uses the SC to calculate the re-routing, and then delivers and stores the scheme in the DC database.
  • the parameter configuration perform configuration according to DC execution recovery, and the corresponding parameters are configured as follows:
  • the parameters of the SC side are as follows:
  • the interaction between the pre-rerouted SC and the DC and the device is as shown in the figure (assuming a fault occurs in the A domain). Since the re-routing calculated by the SC is the globally optimal end-to-end route, not only the fault occurs when the fault occurs. The domain needs to be rerouted, and domains that have not failed may also need to be rerouted.
  • this example provides a 1+1 protection method based on an example, including:
  • the SC performs route calculation of the protection path
  • the SC sends the configuration information of the network resource for the reserved protection path to the controllers DC A and DC B of the A domain and the B domain respectively.
  • DC A detects the fault and switches the service to the protection path, that is, the transmission of the service data is switched from the working path to the protection path;
  • DC A sends a fault report to the SC
  • the SC re-calculates the route of the current working path
  • the SC reserves the network resources of the protection path again, and sends the information of the network resources that reserve the protection path to DC A and DC B respectively.
  • this example provides a recovery method for dynamic rerouting, including:
  • the SC performs resource configuration, and sends configuration information of the resource configuration to the DC A.
  • DC A detects the fault and then calculates the route of the recovery path.
  • DC A can report the fault of the working path to the SC, or it can not report the fault of the working path.
  • this example provides a 1+1 protection recovery method, including:
  • the SC performs route calculation of the protection path
  • the SC sends a notification of the network resource that reserves the protection path to the DC A and the DC B;
  • DC A detects the fault and directly switches the service to the configured protection path.
  • the SC indicates that the service has been switched to dynamic rerouting
  • DC A detects the route of the fault calculation recovery path
  • the service fault can be eliminated based on the protection path or the recovery path according to the protection path and the recovery path.
  • this example provides a recovery method for dynamic rerouting, including:
  • the A-domain DC configures the resources of the A-domain device according to the configuration information sent by the SC.
  • the B-domain DC configures the resources of the B-domain device according to the configuration information sent by the SC.
  • the B domain device detects the fault and reports it to the B domain DC.
  • the processing here is fault recovery processing.
  • the A domain device detects the fault and reports it to the A domain DC.
  • the A domain device calculates the intra-domain rerouting, configures the resources of the recovery path calculated by the route, and switches the service to the recovery path.
  • the A domain DC reports a fault.
  • this example provides a 1+1 protection method, including:
  • the A-domain DC configures the resources of the A-domain device according to the configuration information sent by the SC.
  • the B-domain DC configures the resources of the B-domain device according to the configuration information sent by the SC.
  • the B domain device detects the fault and reports the B domain DC and switches the service to the protection path.
  • the device here is the device in the B domain and reports the fault to the SC.
  • the A domain device detects the fault and reports it to the A domain DC and switches the service to the protection path.
  • the device here is the device in the A domain and reports the fault to the SC.
  • this example provides a preset route recovery method, including:
  • This E2E represents end-to-end recovery within a single domain, rather than cross-domain recovery of the entire path.
  • the A-domain DC and the B-domain DC save the re-routing of the recovery path to the database according to the field sent by the SC, and configure the resources of the devices in the respective domain, but the resource configuration here is not the resource configuration of the recovery path.
  • the B domain device detects the fault and reports it to the B domain DC.
  • the B domain device After receiving the configuration resource allocation command of the B domain DC, the B domain device configures the recovery path and switches the service to the recovery path.
  • the A domain device detects the fault and reports it to the A domain DC.
  • the A domain device After receiving the configuration resource allocation command of the A domain DC, the A domain device configures the recovery path and switches the service to the recovery path.
  • the example provides a DC protection recovery method, including:
  • the process After determining the preset route, it is determined whether the domain is faulty; if the domain is faulty, the configuration is sent to the device to configure the recovery path; if not, whether the domain needs to be modified, for example, the threshold re-routing port is determined. If the configuration of the recovery path is delivered by the device, the process is terminated.
  • the disclosed apparatus and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed.
  • coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.
  • the units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing module, or each unit may be separately used as one unit, or two or more units may be integrated into one unit;
  • the unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing storage device includes the following steps: the foregoing storage medium includes: a mobile storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • ROM read-only memory
  • RAM random access memory
  • magnetic disk or an optical disk.
  • optical disk A medium that can store program code.

Abstract

L'invention concerne un procédé et un dispositif de récupération de protection de réseau de transport optique à base de SDN et un support de stockage. Le procédé consiste à : acquérir des informations d'un objet de contrainte de récupération dans un modèle de fondation de réseautage ouvert (ONF), l'objet de contrainte de récupération comprenant au moins : un champ d'étendue de récupération de protection ; réaliser un calcul d'itinéraire selon les informations de l'objet de contrainte de récupération ; et configurer un trajet de protection ou un trajet de récupération en fonction du résultat du calcul d'itinéraire.
PCT/CN2018/124045 2018-01-02 2018-12-26 Procédé et dispositif de récupération de protection de réseau de transport optique à base de sdn et support de stockage WO2019134572A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810003049.0A CN109996130A (zh) 2018-01-02 2018-01-02 基于sdn的光传送网保护恢复方法、设备及存储介质
CN201810003049.0 2018-01-02

Publications (1)

Publication Number Publication Date
WO2019134572A1 true WO2019134572A1 (fr) 2019-07-11

Family

ID=67128895

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/124045 WO2019134572A1 (fr) 2018-01-02 2018-12-26 Procédé et dispositif de récupération de protection de réseau de transport optique à base de sdn et support de stockage

Country Status (2)

Country Link
CN (1) CN109996130A (fr)
WO (1) WO2019134572A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113691464A (zh) * 2021-08-16 2021-11-23 中国电子科技集团公司第五十四研究所 一种基于同步资源权衡优化的星地协同网络资源分配方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113067659B (zh) * 2020-01-02 2022-08-23 中国移动通信有限公司研究院 一种信息处理方法、装置、设备及计算机可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106301541A (zh) * 2015-06-05 2017-01-04 中兴通讯股份有限公司 设置业务保护的方法、控制器和光网络设备
CN106330698A (zh) * 2015-06-24 2017-01-11 中兴通讯股份有限公司 一种局部路由的恢复方法及装置
CN106664248A (zh) * 2014-08-28 2017-05-10 华为技术有限公司 在软件定义网络中路由数据包的方法和控制器
CN107196854A (zh) * 2017-06-20 2017-09-22 西安交通大学 一种软件定义网络中数据平面异常处理方法
US9848049B2 (en) * 2015-10-06 2017-12-19 Ciena Corporation Service preemption selection systems and methods in networks

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105656654A (zh) * 2014-11-14 2016-06-08 中兴通讯股份有限公司 路径获取方法和多域控制器、跨域业务保护方法和系统
CN106302153B (zh) * 2015-05-11 2020-02-07 中兴通讯股份有限公司 多域控制器、单域控制器、软件定义光网络系统及方法
CN106453077B (zh) * 2015-08-10 2019-07-02 中国电信股份有限公司 层次化路由的管理方法、主控制器、子域控制器及sdn
CN106452817B (zh) * 2015-08-12 2019-05-31 中国电信股份有限公司 保护配置管理方法和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106664248A (zh) * 2014-08-28 2017-05-10 华为技术有限公司 在软件定义网络中路由数据包的方法和控制器
CN106301541A (zh) * 2015-06-05 2017-01-04 中兴通讯股份有限公司 设置业务保护的方法、控制器和光网络设备
CN106330698A (zh) * 2015-06-24 2017-01-11 中兴通讯股份有限公司 一种局部路由的恢复方法及装置
US9848049B2 (en) * 2015-10-06 2017-12-19 Ciena Corporation Service preemption selection systems and methods in networks
CN107196854A (zh) * 2017-06-20 2017-09-22 西安交通大学 一种软件定义网络中数据平面异常处理方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113691464A (zh) * 2021-08-16 2021-11-23 中国电子科技集团公司第五十四研究所 一种基于同步资源权衡优化的星地协同网络资源分配方法

Also Published As

Publication number Publication date
CN109996130A (zh) 2019-07-09

Similar Documents

Publication Publication Date Title
US9705735B2 (en) System and method using RSVP hello suppression for graceful restart capable neighbors
KR102118687B1 (ko) SDN(Software-defined networking)에서 네트워크 장애 해소를 위한 컨트롤러 및 스위치의 동작 방법과, 이를 위한 컨트롤러 및 스위치
JP5039639B2 (ja) パスプロテクション機能を有する通信装置及びその通信装置を使用するネットワークシステム
EP2288079B1 (fr) Système et procédé de surveillance de la connectivité d'un chemin entre des noeds dans un réseau
US8730814B2 (en) Communication network connection failure protection methods and systems
CN112868206A (zh) 在使用基于服务的体系架构的电信网络核心中提供服务代理功能的方法、系统和计算机可读介质
US9385944B2 (en) Communication system, path switching method and communication device
US10805209B2 (en) Virtual network protection method and apparatus
CN103051565A (zh) 一种等级软件定义网络控制器的架构系统及实现方法
EP2608459A2 (fr) Routeur, système de routeur de grappes virtuel et procédé d'établissement associé
KR102157711B1 (ko) 통신 네트워크에서 장애 복구 방법
US10237124B2 (en) Network operation, administration, and maintenance (OAM) method, apparatus, and system
WO2019134572A1 (fr) Procédé et dispositif de récupération de protection de réseau de transport optique à base de sdn et support de stockage
US20160352636A1 (en) Network path computation method, apparatus, and system
CN114157715B (zh) 一种骨干网络控制器的网络信息管理方法及系统
US10033573B2 (en) Protection switching method, network, and system
CN103081406B (zh) 用于应请求通过提供商网络来恢复连接的方法和设备
JP2006135945A (ja) パス設定装置、パス設定システム、及び、それらのパス設定方法
CN112803995B (zh) 资源共享方法、网络节点及相关设备
WO2015024163A1 (fr) Procédé de commutation bidirectionnelle de bout en bout de type 1:1, système et nœud
US8676947B2 (en) Resource reservation apparatus and method
WO2014094575A1 (fr) Procédé de négociation d'état de chemin interdomaine et dispositif de nœud
CN114531393B (zh) 分段路由策略下发方法、装置、设备及介质
US9806939B2 (en) Method and apparatus for linear protection switching
US20210306724A1 (en) Method for establishing service path, network device, and system

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 15/10/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18898717

Country of ref document: EP

Kind code of ref document: A1