second. As wavelength routing and all-optical
switching paves the way for network throughput of
such scales, network survivability assumes critical
importance. A single loss of or damage to a fiber is a
common means of a greater loss. A short network
outage can lead to huge data loss, particularly in the
backbone core. Thus, a connection being carried in
the network also needs high protection and
resilience. Survivability refers to the ability of the
network to reconfigure and re-establish
communication upon node and/or link failures.
Such network survivability can be classified into
two general categories: pre planned protection and
dynamic restoration. In pre-planned protection-based
techniques resources are already planned, typically
at the time of establishing a lightpath connection, to
recover from network failures and hence recovery is
faster.
During the normal operation phase these
reserved resources remain idle. Upon the occurrence
of failure, reserved resources are used to recover
from the failure according to protection protocols. In
contrast, in dynamic restoration, the resources used
for recovery from failure are not reserved at the time
of connection establishment, but are discovered
dynamically using link state algorithms when a
failure occurs. As it is obvious, dynamic restoration
uses resources efficiently, but the restoration time is
usually longer, because it requires the establishment
of a new functional backup path. Moreover, 100%
service recovery cannot be guaranteed as it is not
guaranteed that the spare capacity is available at the
time of failure (Dutta, 2008).
2.1 Problems with Conventional
GMPLS Restoration Mechanisms
One of the most common problems of the existing
fault recovery schemes in GMPLS networks is that
they do not consider the already existing link load of
a backup path when it has to be configured. A
typical bad case scenario is when selecting an
optical link which is a critical segment, or cut-edge,
for many connections. It has been shown that a
failure on this link has more overall impact on the
network traffic (Changwoo, 2007). Figure 1 shows a
related network situation where more connections
cross through a particular optical link, which
therefore acts as a bridge, than other links. As the
number of connections increases in a particular link,
so does the overall impact of a potential failure of
the link.
It is well known that some links have higher
failure probabilities, and this can be attributed to
their physical situation and conditions. This Link
Failure Probability Factor (LFP) is based on the type
of physical link, the node characteristics and
geographical distribution of the network segments.
Since these parameters are outside of our control, we
consider the LFP values for the network topology as
given, and our purpose is to route backup paths so
that traffic distribution across the network becomes
as even as possible. Thus we can try to decrease the
impact of new potential network faults in terms of
affected connections.
Figure 1: Link Failure in a Path with many connections
(Changwoo, 2007).
3 LINK DELAY-CONSTRAINED
ALGORITHM
IMPLEMENTATION
Due to the previous problems that occur from
traditional unconstrained Restoration Schemes in
GMPLS networks, our proposed algorithm
configures a backup path by searching for the
optimal path through the link state algorithm, based
on the delay parameter. The key concept of this
improved algorithm is that the path selection
procedure typically prefers links that carry fewer
connections, and thus, given the Link Failure
Probability Factors, distributes the impact of links
failures on LSP more evenly.
3.1 Constraint-based Algorithm
The implementation of our mechanism, from now on
called LDC (Link Delay-Constrained), is separated
in two phases: The Link Searching for Delay
Constraint Procedure and the Modified Dijkstra
Algorithm which takes into account the filtered link
information, with newer cost values, from the
previous phase according to the least delay
constraint. The delay metric can be calculated using
DCNET 2011 - International Conference on Data Communication Networking
46