EP3841690A1 - Vorrichtung, verfahren und netzwerksystem zur bereitstellung von fehlerabhängigem schutz und wiederherstellung der betroffenen dienste - Google Patents
Vorrichtung, verfahren und netzwerksystem zur bereitstellung von fehlerabhängigem schutz und wiederherstellung der betroffenen diensteInfo
- Publication number
- EP3841690A1 EP3841690A1 EP18766237.4A EP18766237A EP3841690A1 EP 3841690 A1 EP3841690 A1 EP 3841690A1 EP 18766237 A EP18766237 A EP 18766237A EP 3841690 A1 EP3841690 A1 EP 3841690A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- failure
- network system
- services
- specific backup
- potential failure
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 230000001419 dependent effect Effects 0.000 title claims abstract description 43
- 238000000034 method Methods 0.000 title claims description 65
- 238000005457 optimization Methods 0.000 claims abstract description 18
- 238000011084 recovery Methods 0.000 claims description 48
- 230000003287 optical effect Effects 0.000 claims description 17
- 238000001514 detection method Methods 0.000 claims description 12
- 238000012544 monitoring process Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 4
- 230000008569 process Effects 0.000 description 12
- 230000009286 beneficial effect Effects 0.000 description 6
- 238000004364 calculation method Methods 0.000 description 6
- 238000013461 design Methods 0.000 description 5
- 230000011664 signaling Effects 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000008929 regeneration Effects 0.000 description 2
- 238000011069 regeneration method Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 230000006735 deficit Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000004064 dysfunction Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/14—Monitoring arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
- H04J3/1605—Fixed allocated frame structures
- H04J3/1652—Optical Transport Network [OTN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- 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/22—Alternate routing
Definitions
- the present invention relates generally to the field of failure-dependent protection in a network system. More particularly, the present invention relates to a device, a method, and a network system for providing failure dependent protection and recovering the failing services in the network system.
- OTN Optical Transport Networks
- failures may be caused by various factors such as fiber cuts, amplifier dysfunctions, failures of electronic components, etc.
- various recovery schemes have been proposed.
- restoration (a.k.a. dynamic rerouting) is a reactive approach.
- protection is a proactive approach, and hence the necessary resources for recovery have to be reserved in advance.
- the network controller may be the Path Computation Element (PCE) in the Generalized Multiprotocol Label Switching (GMPLS) networks or the transport software defined network (T-SDN) (T-SDN) controller in the Automatically Switched Optical Networks (ASON).
- PCE Path Computation Element
- GPLS Generalized Multiprotocol Label Switching
- T-SDN transport software defined network
- ASON Automatically Switched Optical Networks
- Restoration is a best-effort process, and hence a successful recovery cannot be guaranteed.
- restoration may be a slow process since it requires on- the-fly path calculation.
- the conventional devices and methods which support protection, enable fast and guaranteed recovery, and they come in two different varieties including a link protection and a path protection scheme.
- the end nodes of the failing link detect the failure, and may further detour the affected traffic from the failed link to another path.
- any failure occurring along the path of a service causes the head-end node to move the traffic to a pre-computed new route called backup path.
- backup path since the backup paths are established in advance, recovery is fast, however, the backup paths should be carefully designed so that the overall network resource reservation is minimized.
- the path protection is the most efficient of the conventional schemes.
- the conventional protection schemes e.g., in ASON or MPLS networks, which rely on pre-planned recovery paths, have a disadvantage of only considering the failure- independent paths, and consequently, any failure affecting the working path may cause traffic to move to a new backup path, which usually does not share any critical resources with the original path.
- SRG Shared Risk Groups
- MPLS Multiprotocol Label Switching
- IP Internet Protocol
- SRG Shared Risk Link Groups
- SRLG Shared Risk Link Groups
- a conventional protection method namely 1+1 is known, in which two signals are simultaneously sent over two SRG-disjoint paths. This ensures immediate recovery, since neither failure detection nor any reconfiguration is needed.
- the 1+1 protection method has the disadvantage that it significantly incurs a larger resource reservation (e.g., increases the cost of protection), since it actually doubles the traffic in the network system.
- a second conventional protection method namely 1: 1 (or shared backups), is also known.
- the 1: 1 method is a failure-independent protection scheme that uses shared backup paths.
- the 1: 1 protection method reserves bandwidth for backup paths in such a way that if two paths do not fail together, they can possibly share the same backup reservation.
- the 1: 1 protection method ensures a fast recovery, since only the intermediate switches need to be reconfigured.
- the 1: 1 protection method has the disadvantage that it supports only partial resource sharing, since the reaction is the same to any failure in the network system.
- FD Failure-Dependent
- the FD recovery is more economical than the 1+1 and 1:1 methods, since it achieves the reuse of primary and backup resources. Moreover, the FD recovery has the characteristics that it enables re-using of released resources of primary paths (Stub release). Moreover, the backup paths do not have to be SRG-disjoint to the primary paths, and it further enables more sharing opportunities. From the above discussed benefits, it becomes evident that the failure-dependent (FD) recovery is a better option than 1+1 and 1: 1 in terms of resource efficiency.
- the FD recovery method has the disadvantage that it is a slow method, since SRG failure detection and backup establishment is a time-consuming process.
- SMP Shared Mesh Protection
- the conventional existing failure-dependent protection mechanisms suffer from slow recovery, since they heavily rely on a centralized control plane (e.g., PCE).
- PCE centralized control plane
- SMP Shared Mesh Protection
- the conventional SMP systems use multiple shared backups (e.g., Pl, PU, P2) for each working service (Wl).
- Wl multiple shared backups
- Using multiple shared backups for each working service may introduce contention for resources among different services, and priorities among services may be defined. For example, if Pl is available, then Wl switches to Pl, otherwise W 1 switches to P 1’ . However, if P2 is of higher priority, it will interrupt P 1 , thus W 1 switches to P2.
- the conventional SMP system supports multiple backups per each service, and hence enables the creation of efficient protection mechanisms.
- it since it is a distributed recovery scheme, it introduces contention for resources, and consequently it delays the recovery process.
- the backup of each service to be used is independently selected by the head-end node of the service.
- the exact configuration of the network system after a failure and the incurred delay are non-deterministic. For that reason, if the backup paths are not carefully designed, SMP could eventually lead to recovery failure.
- a monitoring mechanism is needed that constantly monitors the availability of backup resources.
- the conventional SMP systems have an additional disadvantage that they require an extensive signalling to monitor all the network resources.
- the conventional method based on the SRLG Failure-dependent reaction have a disadvantage that the recovery is slow.
- the present invention aims to improve the conventional devices, methods and systems.
- the present invention has the objective to provide a device, a method and a system for providing a failure dependent protection for rapid recovery of a failing system.
- the present invention proposes a device for providing a failure dependent protection in a network system, and a fast recovery with a minimum resource reservation may be obtained.
- a first aspect of the present invention provides a device for providing failure dependent protection in a network system comprising a plurality of nodes, the device being configured to identify at least one potential failure in the network system; calculate and assign a specific backup path for each of one or more services in the network system and for each of the at least one potential failure, wherein the specific backup paths for each of the one or more services are jointly determined for the at least one potential failure based on an offline optimization of a configuration of the network system; and output a signal to the head-end node of a given service, indicating the at least one potential failure paired with the specific backup path calculated for the given service, in order to fill a forwarding table at the head-end node.
- the first aspect of the present invention has the advantages that it enables design and establishment of the failure-dependent resilient networks. Moreover, the offline calculation of failure-dependent protection may minimize the overall resource reservation, since the reaction to each failure is carefully designed in an offline manner. In addition, prefetching failure-dependent specific backup paths at network nodes enables a faster failure recovery. Therefore, an immediate recovery from network failures may be guaranteed.
- the device is further configured to react to link failures, and upon detection of a link failure caused by Shared Risk Link Groups, provide a notification signal to the head-end node indicating the failing link.
- the notification signal may be provided, and the network may recover rapidly from the link failure.
- the link failure is detected based on a high order optical channel data unit, ODU, tandem connection monitoring, TCM, of adjacent nodes.
- the working paths of the services and the specific backup paths are jointly determined such that the overall network cost is minimized with respect to a predefined criterion.
- a reservation of the resources can be implemented.
- Such a reservation of the required resources may enable overall network cost to be minimized. Therefore, a faster and deterministic recovery with a minimum cost can be achieved.
- prefetching centrally-de signed failure- dependent (FD) backup paths at the nodes of the network system ensures a fast and guaranteed recovery at minimum cost.
- the working paths of the services and the specific backup paths are jointly determined based on maximizing sharing of resources in the network system.
- the device is further configured to calculate a network configuration and output an additional signal Sl for filling the forwarding table to each of the plurality of nodes (A, B, C, D, E, F) before recovery of the network system from the detected failure, wherein the additional signal comprises a new specific backup path being calculated for a subsequent potential failure.
- the network system may be able to recover from the sequential failures. For example, initially when there is no failure, the offline calculation of reaction to potential failures (i.e. optimization of the configuration of the network system) can be performed along with prefetching the specific backup paths via signal Sl, as discussed before. Then, when the failure is detected, the network system may reconfigure to a new network configuration. Afterward, the device may perform the offline calculation once again in order to protect the second potential failure, etc.
- the potential failure comprises at least one of a node failure, a link failure, and a shared risk link group failure.
- the device is based on an optical network device.
- the device may be based on an optical network, and the signal may be encoded onto light to transmit information among the plurality of nodes of the network system.
- the output signal may be a notification message including the potential failure paired with corresponding specific backup path, etc.
- the failure notification signal (S2) is based on an in-band signal.
- failure can be quickly detected and the network system may be able to recover from the detected failure, for example, in a fast and deterministic way.
- a second of the present invention provides a method for providing a failure dependent protection in a network system comprising a plurality of nodes, the method comprises the steps of identifying at least one potential failure in the network system; calculating and assigning a specific backup path for each of one or more services in the network system and for each of the at least one potential failure, wherein the specific backup paths for each of the one or more services are jointly determined for the at least one potential failure based on an offline optimization of a configuration of the network system; and outputting a signal to the head-end node of a given service, indicating the at least one potential failure paired with the specific backup path calculated for the given service, in order to fill a forwarding table at the head-end node.
- the method further comprises reacting to link failures, and upon detection of a link failure caused by Shared Risk Link Groups, providing a notification signal to the head-end node indicating the failing link.
- the method further comprises detecting the link failure based on a high order optical channel data unit, ODU, tandem connection monitoring, TCM, of adjacent nodes.
- the working paths of the services and the specific backup paths are jointly determined such that the overall network cost is minimized with respect to a predefined criterion.
- the working paths of the services and the specific backup paths are jointly determined based on maximizing sharing of resources in the network system.
- the method further comprises calculating a network configuration and outputting an additional signal for filling the forwarding table to each of the plurality of nodes before recovery of the network system from the detected failure, wherein the additional signal comprises a new specific backup path being calculated for a subsequent potential failure.
- the potential failure comprises at least one of a node failure, a link failure, and a shared risk link group failure.
- the method is performed in an optical network device.
- the failure notification signal is based on an in-band signal.
- a third aspect of the present invention provides a node for recovering a failing service in a network system comprising a plurality of nodes, the node being configured to maintain a forwarding table for indicating one or more services associated to the node, and a specific backup path for each of the one or more services to be used under a potential failure; obtain a signal from a device, indicating at least one potential failure paired with a specific backup path for a given service, in order to fill the forwarding table, and apply, when a failure is detected in the network system, the specific backup path of the detected failure according to the forwarding table to the given service.
- a fourth aspect of the present invention provides a network system, comprising a device for providing a failure dependent protection configured to identify at least one potential failure in the network system; calculate and assign a specific backup path for each of one or more services in the network system and for each of the at least one potential failure, wherein the specific backup paths for each of the one or more services are jointly determined for the at least one potential failure based on an offline optimization of a configuration of the network system; and output a signal to the head-end node of a given service, indicating the at least one potential failure paired with the specific backup path calculated for the given service, in order to fill a forwarding table at the head-end node; and the network system further comprising a plurality of nodes for recovering a failing service, the nodes being interconnected by a plurality of links, and each node being configured to maintain a forwarding table for indicating at least one or more services associated to the node, and a specific backup path for each of the one or more services to be used under a potential failure obtain, if being the
- system is further configured to react to link failures, and upon detection of a link failure caused by Shared Risk Link Groups, provide a notification signal to the head-end node indicating the failing link.
- system is further configured to detect the link failure based on a high order optical channel data unit, ODU, tandem connection monitoring, TCM, of adjacent nodes.
- the working paths of the services and the specific backup paths are jointly determined such that the overall network cost is minimized with respect to a predefined criterion.
- the working paths of the services and the specific backup paths are jointly determined based on maximizing sharing of resources in the network system.
- the system is further configured to calculate a network configuration and output an additional signal for filling the forwarding table to each of the plurality of nodes before recovery of the network system from the detected failure, wherein the additional signal comprises a new specific backup path being calculated for a subsequent potential failure.
- the potential failure comprises at least one of a node failure, a link failure, and a shared risk link group failure.
- a fifth aspect of the present invention provides a computer program comprising program code causing a computer to perform the method according to the second aspect, when being carried out on a computer.
- FIG. 1 shows a schematic view of a device for providing a failure dependent protection in a network system according to an embodiment of the present invention.
- FIG. 2 shows a schematic view of a device for providing a failure dependent protection in a network system according to an embodiment of the present invention in more detail.
- FIG. 3 shows a schematic view of a method for providing a failure dependent protection in a network system according to an embodiment of the present invention.
- FIG. 4 shows a schematic view of a method for network slicing with failure-dependent protection according to an embodiment of the present invention.
- FIG. 5 shows a schematic view of a flow chart of an algorithm implemented according to an embodiment of the present invention.
- FIG. 1 shows a schematic view of a device 100 for providing a failure dependent protection in a network system 1 according to an embodiment of the present invention.
- the device 100 is in particular suited to identify at least one potential failure fl in the network system 1.
- the network system 1 comprises a plurality of nodes A, B, C, D, E, and F.
- the plurality of nodes A, B, C, D, E, and F are interconnected to each other by a plurality of links.
- the device 100 is further configured to calculate and assign a specific backup path pl for each of one or more services wl in the network system 1, and for each of the at least one potential failure fl, wherein the specific backup paths for each of the one or more services are jointly determined for the at least one potential failure based on an offline optimization of a configuration of the network system 1.
- the device 100 may provide a fast and deterministic recovery at minimum cost and/or resource reservation. For example, the device 100 may ensure the resource efficiency by jointly designing all the backup paths (with and/or without the primary paths) that should be used under each possible failure.
- the device 100 is further configured to output a signal Sl to the head-end node of a given service, indicating the at least one potential failure paired with the specific backup path calculated for the given service, in order to fill a forwarding table 101 at the head-end node.
- the forwarding table 101 may be located in anyone of the device 100, the plurality of nodes A, B, C, D, E, and F, the head-end node, the system 1, etc., without limiting the present invention to the location of the forwarding table 101.
- the fast reaction in the network system 1 may be ensured by prefetching the failure-dependent backup paths at the head-end node of the given service, and thus, upon failure detection, a communication with the central network controller may not be required.
- the device 100 is able to provide a failure dependent protection in the network system 1.
- FIG. 2 shows a schematic view of a device 100 for providing a failure dependent protection in a network system 1 according to an embodiment of the present invention in more detail.
- the device 100 is configured to obtain as an input the resources and services 201 of the network system 1.
- the device 100 further comprises a control plane 202, which has a path computation element. For example, the device 100 calculates and assigns a specific backup path pl for each of one or more services wl in the network system 1, and for each of the at least one potential failure fl. Moreover, the device 100 performs an offline optimization of a configuration of the network system 1, and it further jointly determines the specific backup paths for each of the one or more services for the at least one potential failure f 1.
- the device 100 e.g., the path computation element of its control plane
- the device 100 centrally implement a planning phase for the calculation and prefetching of the specific backup paths to network nodes.
- the device 100 and/or its path computation element jointly designs the working and the failure dependent backup paths of all running services according to their requirements and the state of the network so that overall resource reservation is minimized.
- the device 100 optionally comprises a storage unit 203, which is configured to store the calculated and assigned the specific backup path pl for each of the one or more services wl in the network system 1, and for each of the at least one potential failure fl, which may be pre-fetched to the nodes.
- the potential failure may be a node failure, a link failure, and a shared risk link group failure, without limiting the present disclosure to a specific failure.
- each node i.e. from the plurality of nodes A, B, C, D, E, and F
- the forwarding table 101 may be stored in each node, the system, etc., as discussed above.
- the device 100 optionally comprises a signal generator 204, which is configured to output a signal Sl to the head-end node of a given service, indicating the at least one potential failure paired with the specific backup path calculated for the given service, in order to fill the forwarding table at the head-end node.
- a signal generator 204 which is configured to output a signal Sl to the head-end node of a given service, indicating the at least one potential failure paired with the specific backup path calculated for the given service, in order to fill the forwarding table at the head-end node.
- the head-end node of the given service may obtain the signal Sl from the device 100, indicating the at least one potential failure fl paired with the specific backup path pl for the given service wl, and may fill the forwarding table.
- the device 100 further optionally comprises a look-up function 205, which is configured to detect a link failure in the network system 1. Moreover, a link failure may be detected in the network system 1, for example, based on a high order optical channel data unit, ODU, tandem connection monitoring, TCM, of adjacent nodes. For example, the device 100 may further be configured to react to the link failures, and upon detection of a link failure caused by Shared Risk Link Groups, the device 100 (e.g. its signal generator unit 204) may provide a notification signal S2 to the head-end node indicating the failing link.
- a link failure may be detected in the network system 1, for example, based on a high order optical channel data unit, ODU, tandem connection monitoring, TCM, of adjacent nodes.
- the device 100 may further be configured to react to the link failures, and upon detection of a link failure caused by Shared Risk Link Groups, the device 100 (e.g. its signal generator unit 204) may provide a notification signal S2 to the head-end node indicating
- the plurality of the nodes in the network system may detect a failure and notify the affected head-end nodes.
- the head-end node may further apply the specific backup path of the detected failure according to the forwarding table to the given service.
- the device 100 is able to provide a failure dependent protection in the network system 1 comprising the plurality of nodes A, B, C, D, E, and F, and the plurality of nodes A, B, C, D, E, and F, if being the head-end node, are able to recover the failing service.
- FIG. 3 shows a schematic view of a method 300 for providing a failure dependent protection in a network system 1 comprising a plurality of nodes A, B, C, D, E, and F, according to an embodiment of the present invention.
- the method 300 comprises a first step of identifying 301 at least one potential failure fl in the network system 1.
- the method 300 comprises a second step of calculating 302 and assigning 302 a specific backup path pl for each of one or more services wl in the network system 1 and for each of the at least one potential failure fl, wherein the specific backup paths for each of the one or more services are jointly determined for the at least one potential failure based on an offline optimization of a configuration of the network system 1.
- the method 300 comprises a third step of outputting 303 a signal Sl to the head-end node of a given service, indicating the at least one potential failure paired with the specific backup path calculated for the given service, in order to fill a forwarding table 101 at the head-end node.
- FIG. 4 shows a schematic view of a method 400 for network slicing with failure-dependent protection according to an embodiment of the present invention.
- the present invention is illustrated over Transport SDN for providing Network Slices (NS) with fast recovery in a guaranteed, and minimum resource footprint.
- NS Network Slices
- the device 100 obtains the state of the network system as an input.
- the centralized SDN controller is constantly aware of the network status, network resources, and ongoing services.
- the method further comprises a NS planning M.l which invokes so as to calculate the necessary resource reservations.
- the NS planning module (M. l) comprises four steps of 401, 402, 403, and 404.
- the device 100 jointly designs the primary and the backup paths, for example, by computing the 1+1 solution.
- the device 100 uses the 1+1 type of solution for all active services. By jointly designing all the primary and backup paths, the device 100 ensures that all the services may be served.
- the device 100 names the primary and the backup paths towards maximizing disjointness.
- the device 100 names each one of the 1+1 paths as primary or backup such that disjointness, and hence sharing opportunities are maximized.
- the device 100 calculates more efficient link-failure backup x l, f that is SRLG-disjoint to /.
- the device 100 derives a failure-dependent backup path for each service, such that the overall reservation is minimized, e.g. using a method as it is generally known to the skilled person.
- the device 100 reserves the backup resources according to worst SRLG failure, but for each SRLG failure, the device 100 protects against the worst sequence of detected failures according to the following equation (1):
- S corresponds to a specific SRLG failure of the set SRLG
- d corresponds to the bandwidth requirement of service 1
- f corresponds to any link failure caused by SRLG failure S.
- the necessary resources are calculated and reserved according to the worst SRLG failure and according to the worst link failure detection sequence.
- the device 100 fills failure-dependent look-up tables (M2) via signaling Sl.
- the calculated primary paths are established and the calculated backup paths are pre fetched to the network nodes via signaling Sl of the form ⁇ failure, path ⁇ for each active service.
- All the network nodes are configured so that they can react to failures in a distributed manner.
- a failure may be detected in the network system 1.
- the nodes detect a failure and notify the affected head-end nodes.
- the head-end node Upon failure, the head-end node receives a notification regarding the failing link. This detection can happen by monitoring the links of the working path links similarly to the OTN SMP approach for protection resources, i.e. via high order ODU TCM monitoring between adjacent nodes
- the head-end retrieves the corresponding backup entry of the Look-up table.
- the head-end node establishes the backup path indicated by the look-up table
- the head-end node initiates the establishment of the backup path for the specific failure.
- the method and/or the device may ensure a fast recovery from a failure at minimum cost, but the slice now may not be protected against a subsequent failure.
- the method may further initiate the NS planning module M. l, so as to ensure protection against any subsequent failure.
- the method 400 may guarantee protection against multiple failures.
- the module M.1 may be executed periodically, even if no failure has occurred, but some other aspects of the network have changed.
- the steps 402, 403, 404, and 405 may be representative of a first module Ml and the step 406 may be representative of a second module M2, without limiting the present invention to a specific number of steps, modules, etc.
- the network recovery may be based on two main phases, an offline phase that calculates the network configuration for each detected failure, and a real-time reaction.
- the failure-dependent network planning method executed centrally, e.g. at PCE, it jointly designs the working and the FD backup paths of all running services according to their requirements and the state of the network so that overall resource reservation is minimized. Then, in M2 it performs a per service failure-dependent Forwarding table at each network node. Each network node stores a forwarding table indicating for its ongoing services the backup path that should be used under each failure.
- the signal the signal Sl is sent from PCE to Network devices to fill the FD look-up tables, for example, for each failure a signal of the form ⁇ failure, backup path ⁇ is sent to the head-end node of the affected service.
- a signal of the form ⁇ failure, backup path ⁇ is sent to the head-end node of the affected service.
- An immediate recovery based on Table look-up may be performed.
- a standard notification of the head-end about the detected failure affecting the primary/working path is sent.
- the reaction to detected failure may be applied, and since the reaction to each failure is deterministic and sufficient resources have been reserved, no resource contention exists.
- Each service eventually switches to the corresponding backup path.
- the network system may recover, and once recovery from the failure is completed, it may apply once again the NS planning method M.1, based on the new network state. Thus, a protection against any subsequent failure may be ensured.
- FIG. 5 shows a schematic view of a flow chart of an algorithm implemented according to an embodiment of the present invention.
- the device 100 obtains the network resource and demands, as an input for the offline optimization.
- the device 100 for example, its centralized controller is able to retrieve the network system status, the network system resources, and the active services in the network system.
- the optical signal can only be transmitted over certain distance before regeneration is needed.
- the device 100 creates physical reachability graph.
- the device 100 creates the physical reachability graph in order to plan failure-dependent backup paths for each service, and further minimize the necessary network resources such as regenerators and wavelengths.
- the physical reachability graph can be created such that the graph nodes are network nodes, a graph edge is created between two nodes if there is a physical path with available capacity, and the optical signal is reachable without regeneration.
- a shortest path on the reachability graph is a path with minimal number of regenerators.
- the device 100 identifies the key physical links and the nodes.
- the device 100 may identifies key physical links to reserve resource, and key nodes for regenerator placement in order to, for example, maintain the load balanced over the network during the optimization process.
- the device 100 loops all failures.
- the device 100 may consider all possible failures during the offline optimization process.
- the device 100 identifies failed demands.
- the device 100 may identify for each failure the affected services.
- the device 100 finds recovery paths.
- the device 100 For example, for each affected service under a certain failure, the device 100 performs the optimization process, and may find a recovery path with minimal resources required.
- the device 100 refreshes reachability graph. For instance, once the new recovery paths have consumed some network resources, the original reachability graph may not be valid anymore. Thus, the device 100 may refresh the reachability graph with new network resource status.
- the device 100 finds cost least recovery paths.
- the loop process in step 504 continues and for each failure and each failed service, the device 100. Moreover, the device 100 may always find the least cost recovery path.
- the device 100 balances the wavelength and regenerators.
- both of the wavelengths and regenerators are network resources, and they should be used according to operator’s objectives. For example, more regenerators could reduce the wavelengths required; and fewer regenerators may result in more wavelengths being used. Accordingly, the device 100 performs the optimization process and may provide a knob in order to control the balance between these two resources.
- the device 100 performs a global optimization.
- the required number of regenerators and link wavelengths may strongly depend on the order of consideration of failures and affected services.
- the optimization process may include a global adjustment phase to improve the backup resource sharing.
- the device 100 may further reduce overall network resources reserved or may further increase the number of services recovered under some failures.
- the device 100 for example, its centralized controller finds the specific backup paths for each service under different failures, it will push the recovery paths to the end nodes of each demand through Signal Sl to fill the recovery look-up table.
- the head-end node of the failed service will be notified about the failure, and it will select the correct backup path for the network recovery.
- the device 100 e.g., its centralized controller may retrieve the new network status as well as the working demands. The whole process may start again in an iterative procedure in order to fully make use of the available network resources.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/EP2018/074147 WO2020048611A1 (en) | 2018-09-07 | 2018-09-07 | Device, method and network system for providing failure dependent protection and recovering the affected services |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| EP3841690A1 true EP3841690A1 (de) | 2021-06-30 |
Family
ID=63528793
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP18766237.4A Pending EP3841690A1 (de) | 2018-09-07 | 2018-09-07 | Vorrichtung, verfahren und netzwerksystem zur bereitstellung von fehlerabhängigem schutz und wiederherstellung der betroffenen dienste |
Country Status (2)
| Country | Link |
|---|---|
| EP (1) | EP3841690A1 (de) |
| WO (1) | WO2020048611A1 (de) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114070783A (zh) * | 2020-07-27 | 2022-02-18 | 中兴通讯股份有限公司 | 预置路径信息获取方法、实体、业务控制单元及存储介质 |
| CN115915041B (zh) * | 2021-09-30 | 2025-04-25 | 中国移动通信集团北京有限公司 | 语音问题定位方法、装置、电子设备及存储介质 |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080130489A1 (en) * | 2006-11-02 | 2008-06-05 | Hung-Hsiang Jonathan Chao | Rerouting for double-link failure recovery in an internet protocol network |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1633068B1 (de) * | 2004-09-01 | 2007-06-06 | Alcatel Lucent | Verfahren zur Herstellung eines Back-up Pfades in einem Transportnetz |
-
2018
- 2018-09-07 EP EP18766237.4A patent/EP3841690A1/de active Pending
- 2018-09-07 WO PCT/EP2018/074147 patent/WO2020048611A1/en not_active Ceased
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080130489A1 (en) * | 2006-11-02 | 2008-06-05 | Hung-Hsiang Jonathan Chao | Rerouting for double-link failure recovery in an internet protocol network |
Non-Patent Citations (2)
| Title |
|---|
| KANG XI ET AL: "IP Fast Reroute for Double-Link Failure Recovery", GLOBAL TELECOMMUNICATIONS CONFERENCE, 2009. GLOBECOM 2009. IEEE, IEEE, PISCATAWAY, NJ, USA, 30 November 2009 (2009-11-30), pages 1 - 8, XP031645611, ISBN: 978-1-4244-4148-8 * |
| See also references of WO2020048611A1 * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020048611A1 (en) | 2020-03-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9559947B2 (en) | Recovery in connection-oriented network | |
| EP2464036B1 (de) | Routenauswahlvorrichtung und routenauswahlverfahren zur mehrfach-dienstwiederherstellung | |
| EP2159957B1 (de) | Verfahren zum schutz eines gemeinsam benutztes vernetztes netzwerk | |
| JP4661892B2 (ja) | 通信ネットワークシステム、通信装置、経路設計装置及び障害回復方法 | |
| JP5596149B2 (ja) | 伝送ネットワークにおけるサービス復元速度向上方法及びパス計算エレメント | |
| US9124522B2 (en) | Multi-level recovery in transport networks | |
| US9372753B2 (en) | Protection against a failure in a computer network | |
| US10805209B2 (en) | Virtual network protection method and apparatus | |
| US20100080119A1 (en) | Method for restoring connections in a network | |
| US9088486B2 (en) | Retention of a sub-network connection home path | |
| US8565116B2 (en) | Communication apparatus and protocol processing method | |
| CN106664214B (zh) | 一种虚拟网络的故障恢复方法和装置 | |
| US20060250948A1 (en) | Dynamic path protection in an optical network | |
| EP3244580B1 (de) | Netzwerkdienstherstellungsverfahren, kooperationssteuerzentrale und netzwerksystem | |
| US9391694B2 (en) | Protection path providing method and transmission device | |
| EP1845656A1 (de) | Verfahren zur implementierung eines master- und backup-übertragungsweges | |
| US20150016815A1 (en) | Adding new alternative paths for restoration in wson network | |
| US9356870B2 (en) | Contention handling in SMP based networks | |
| KR20150002474A (ko) | 통신 네트워크에서 장애 복구 방법 | |
| EP3841690A1 (de) | Vorrichtung, verfahren und netzwerksystem zur bereitstellung von fehlerabhängigem schutz und wiederherstellung der betroffenen dienste | |
| EP1746762B1 (de) | Rückgewinnung von Netzelementenkonfiguration | |
| KR101727782B1 (ko) | 전송망의 자원 관리 방법 및 장치 | |
| CN106464524B (zh) | Ason的路由计算方法和装置 | |
| Ruan et al. | A hybrid protection/restoration scheme for two-link failure in WDM mesh networks | |
| WO2011035804A1 (en) | Method and device for processing data in a network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
| PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
| 17P | Request for examination filed |
Effective date: 20210323 |
|
| AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
| DAV | Request for validation of the european patent (deleted) | ||
| DAX | Request for extension of the european patent (deleted) | ||
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
| 17Q | First examination report despatched |
Effective date: 20240328 |