On Survivability of Dynamically Provisioned Wavelength-Routed Networks
On Survivability of Dynamically Provisioned Wavelength-Routed Networks
net/publication/272792217
CITATIONS READS
0 1,028
3 authors, including:
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Partha Goswami on 26 February 2015.
I. Introduction
Control
OXC3
OXC1
Control
Working
OXC1 OXC2 Lightpath Control
Data
OXC4
OXC5
Optical Network Optical Network
Node 1 Node 2 Protection
Lightpath
Figure 11 Optical node model Figure 12 Dedicated (1:1) link protection (control plane exchanges
GMPLS-based realization of protection and restoration shown in the above include all the relevant messages, viz., RSVP
schemes: The development of a common control plane for path refresh message, Resv message, LMP messages etc.)
both optical and electronic networks will need the relevant
functionalities realized through appropriate signaling, As shown in Fig.12, in order to provide dedicated (1:1) link
routing, and link management protocols to enable protection, failures are localized before the switchover can
intelligent fault management. At the connection level, occur. Once a failure has been localized between the two
GMPLS-based fault management would consist of four adjacent nodes, the upstream node can initiate local span
primary steps: detection, localization, notification and protection by sending an RSVP path refresh message. Use
mitigation. Fault detection should be handled at the layer of path refresh messages is a distinct feature of RSVP that
closest to the failure; for optical networks this is the allows intermediate nodes to refresh the state of an LSP.
physical (optical) layer. One measure of fault detection at This feature allows for a switchover from the primary to the
the physical layer is detecting loss of light (LOL); other backup channel. Note that the benefit of exchanging the
techniques based on optical signal-to-noise ratio (OSNR), shared-protection configuration in advance (using LMP) is
bit-error rate (BER), dispersion, crosstalk, and attenuation that it minimizes the potential backup channel (label)
are still being developed. conflict when protection switching takes place. When the
Fault localization requires communication between nodes downstream node receives the path message, it verifies the
to determine where the failure has occurred (e.g., parameters, updates the signaling state, and either responds
SDH/SONET alarm indication signal (AIS) is used to with a Resv message with a new label or generates an error
localize failures between spans). One interesting message.
consequence of using LOL to detect failures is that, LOL Link Restoration: As mentioned earlier, link restoration
propagates downstream along the connection path, and is designed to react to failures quickly in an exploratory
therefore all downstream nodes may detect the failure. The mode. This in turn involves dynamic resource allocation
LMP protocol includes a fault localization procedure and route calculation, and therefore takes more time to
designed to localize failures in both transparent (all-optical) switch to an alternate path than protection techniques.
and opaque (optoelectrical) networks. This is done by Similar to protection techniques described previously,
sending LMP channel fail messages between adjacent restoration can be implemented at the source or an
nodes over a control channel (maintained separately from intermediate node, once the responsible node has been
the data-bearing channels, as mentioned earlier). Once a notified. In case of link restoration, where traffic is
failure has been detected and localized, failure information switched via an alternate route around a failure, a new path
is notified to all concerned and protection and/or restoration is selected at an intermediate node, as illustrated in Figures
are used to mitigate the failure. Some example of such 13a & 13b. This involves passing the traffic through
failure recovery (for dedicated protection) procedure would additional transit nodes. Link restoration may be beneficial
be worthwhile to discuss as follows. for connections that span multiple hops and/or large
Link protection: As mentioned earlier, link protection is distances because the latency incurred for failure
carried out between two adjacent nodes and involves notification may be significantly reduced. In this case only
switching to a backup channel or link when a failure occurs segments of the connection are rerouted instead of the
(Fig.12). As a part of the GMPLS-routing extensions [21] entire path. Link restoration, however, may break traffic
the link protection type (LPT) is advertised so that span engineering requirements if a strict-hop explicit route is
protection can be used in route calculation. Once a route is defined for the connection. Furthermore, the constraints
selected, the connection is signaled using RSVP-TE or CR- used for routing the connection must be forwarded so that
LDP, which includes a protection bit vector indicating an intermediate node doing link restoration is able to
which LPTs are acceptable for the connection. calculate an appropriate alternate route.
discovered (from the spare capacity in the network) upon
OXC2
the occurrence of a failure. The studies reported in the
literature indicate that shared protection schemes provide
Notify
significant savings in capacity utilization over dedicated
OXC1
OXC3 protection schemes. Furthermore, the restoration schemes
Control
are in general more capacity-efficient as compared to the
Working protection schemes, however with slower recovery process.
Lightpath Control
It is also important to note that, if two fiber links fail in the
Notify
OXC4 network at the same time, then the number of connections
OXC5 that are dropped under shared-path or dedicated-path
protection schemes would be more than the number of
connections dropped under shared-link protection. Thus,
with a given network setting, one needs to choose
Figure 13a Failure of working lightpath judiciously a specific scheme or a combination, governed
by the available resources, needed speed of service
recovery, and the number of possible link failures occurring
OXC2 concurrently in the network. Finally, it may be worthwhile
to indicate that, in a realistic network setting, different users
may have different needs, and also different parts of a
network may have different failure characteristics, thereby
OXC1
OXC3 necessitating adequate investigations on the differentiated
Control survivability methods. Moreover, traditionally the notion of
network service has been binary, i.e., it is either available
Control (as contracted) or not. But the notion of degraded service
also needs to be addressed, so that even if some parts of the
OXC4
network are down, service can still be provided at a reduced
OXC5 quality, if possible. Investigations on multiple and large-
Working scale correlated failures (or attacks) are also going to be of
Lightpath future interest [25].