Comparison of SDN and GMPLS control techniques in

optical transport networks

by
Name: Muhammad Atif Yaqub
Reg #: MS(EE)-SP13-008

In Partial Fulfillment of Requirements

For the Award of Degree of

Master of Science in Electrical Engineering

School of Electrical Engineering

Faculty of Engineering Sciences

The University of Faisalabad

SIGNATURES

Title: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
............................................ ........... ........
Name of Student: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Registration No: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Supervisory Committee (Name & Signatures)

1.

.........................

(Supervisor) . . . . . . . . . . . . . . . . . . . . . . . . .

2.

.........................

(Member) . . . . . . . . . . . . . . . . . . . . . . . . .

3.

.........................

(Member) . . . . . . . . . . . . . . . . . . . . . . . . .

4.

____________________

Special member if any) _______________________

Certificate
This research work was neither submitted earlier nor will be submitted
elsewhere as a requirement of MPhil / MS degree. Moreover, no part of the
thesis is plagiarized / copied.

Name of Student: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signature: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Date: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Supervisor name: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signature: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Date: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Declaration Form
3

It is certified that MS(EE) thesis titled " Comparison of SDN and GMPLS control
techniques in optical transport network " prepared by Mr. Muhammad Atif Yaqub under
Reg # MS(EE)-SP13-008 has been approved for submission.

Thesis Supervisor

Abstract

GMPLS (Generalized multi-protocol label switching) is the control plane that is derived
from the IP/MPLS technique. The protocols used in GMPLS for routing (OSPF, IS-IS)
and signaling (RSVP) are same that are used in IP/MPLS network. In IP/MPLS the
Labels are used to distinguish between the LSPs but in GMPLS the LSPs are identified
based on TDM signal, wavelength and fiber.
On the other hand SDN (Software defined networking) serves the main purpose of
current requirements in optical transport network. It meets the requirement of dynamic,
smart and price operative services with more optimized solutions. SDN uses a common
control plane for all layers used in optical transport networks which make the control
plane less complicated as compared to GMPLS. There may be multiple switching layers
in SDN based on different vendors which may provide different services but the control
plane is centralized for the whole multi-layer network.
In this paper we will have comparison on the control techniques used in GMPLS and
SDN for the current requirements and the future trends in optical transport network. After
that the recommendations and conclusions will be made based on the advantages of SDN
control technique over GMPLS. Also the possible strengths of SDN will be discussed for
future optical networks. Control plane is not quite easy to implement in optical network
as we have to observe multiple parameters like optical power calculation, optical signal
bandwidth and path calculation.

First and foremost I would like to express my sincere gratitude to my thesis advisor, Dr.
Syed Ali Mohsin, for his guidance, encouragements and unreserved help during my two
years of study. He motivated me to start my master thesis during my third semester which

ACKNOWLEDGEMENT

allowed me to extend my research study this far. His office door was always opened for
me to discuss long hours even during after office hours. His pursuit of high standard in
research and his maturity in the field were the greatest source of my motivation.
My special thanks should go to the Mr. Muhammad Kashif for his in depth research
guidance especially in the area of Optical fiber Communication. In my daily work I have
been blessed with a friendly and supportive group of fellow students. I would like to
thank all my friends who have provided constant help and encouragement and I gratefully
acknowledge their support in many ways during two years of my study. Further my
immense gratitude should go to all my professional colleagues for their research
guidance, constructive criticisms and invaluable suggestions.
Finally I take this opportunity to embrace my beloved parents for everything they have
done for me and I thank my family for their prayers and emotional support throughout
my studies. I dedicate this thesis dissertation to my parents.

Abstract. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Table of contents

Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Chapter-1 Introduction to GMPLS and issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.

Introduction of

1.2.

GMPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
GMPLS protocols
............................................ .....3

1.3

GMPLS challenges and the way out . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.3.1

Division of Generalized

label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.2 Formation of Label switched path in GMPLS. . . . . . . . . . . . . . . . . . .
...7

1.3.3

Mechanism for data Transmission variety . . . . . . . . . . . . . . . . . . . 9

1.3.4

Structuring of GMPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.4.1 Proposed Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.4.2 Duplex Label switch path . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.3.5 Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

1.3.5.1 Forwarding Adjacency Label switch path . . . . . . . . . . . . . . .12
1.3.5.2 Categorized label switch path . . . . . . . . . . . . . . . . . . . . . . .13
1.3.5.3 Link Aggregations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3.6

Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.3.7

Efficient Use of available resources . . . . . . . . . . . . . . . . . . . . . . . 17

1.3.7.1 Numberless connections . . . . . . . . . . . . . . . . . . . . . . . . . . .18

1.4

GMPLS unresolved problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

1.4.1 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
1.4.2 Connectivity with other networks . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.4.3 Stability of network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

1.4.4 NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Chapter-2 Software defined networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.1 What is SDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2 SDN Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.1 Data plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.2 Control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.3 Data forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2.4 Data distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2.5 Network specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2.6 Advantages of Decoupling of control and data planes . . . . . . . . . . . . 24
2.2.7 Interaction of SDN layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.7.1 Software defined networking core controller . . . . . . . . . . . . . . 25
2.2.7.2 Use of vendor based Network Software . . . . . . . . . . . . . . . . . 25
2.2.7.3 Use of Network Management System . . . . . . . . . . . . . . . . . . 25
2.2.8 SDN layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.8.1 Infrastructure layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
2.2.8.2 Southbound interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2.8.3 Network hypervisors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.8.4 Network operating systems . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.8.5 Northbound interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.2.8.6 Language based virtualization . . . . . . . . . . . . . . . . . . . . . . . 30
2.2.8.7 Programming languages . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.2.8.8 Network applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3. Differences between GMPLS and SDN . . . . . . . . . . . . . . . . . . . . 31
3.1 Distributed and Centralized control . . . . . . . . . . . . . . . . . . . . . . 31
3.2 Complication of control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . 33

3.3

Non-Flexibility for new control plane . . . . . . . . . . . . . . .

. . . . . . . . . . . . . 33

3.4 Different services provisioning . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.5 Industrial application of SDN . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.5.1 Important benefits in Telecom industry . . . . . . . . . . . . .
. . . . . . . . . 35

3.5.1.1 Use of special software tools . . . . . . . . . . . . . . . . . . . . . . . . 36

3.5.1.2 Combined management . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
3.5.1.3 Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.5.1.4 Flexibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
3.5.2 ZTE SDN special features . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.5.2.1 Dynamic extension of services . . . . . . . . . . . . . . . . . . . . . . 37
3.5.2.2 Restoration of services using common controller . . . . . . . . . . 39
3.5.2.3 Possibility of availability . . . . . . . . . . . . . . . . . . . . . . . . . . .40

List of Figures

10

11

12

13

Chapter-1

GMPLS
1.1 Introduction of GMPLS
This is the time of high speed internet that is requirement of each and every individual.
Also the high definition and high quality video streaming has become quite important for
use. All these services required high bandwidth allocations. For this purpose the transport
network is very important which needs to have high bandwidth in it to fulfill the future
and current requirements. The DWDM is the type of optical transport networks which
covers the requirements in a better way. Also it is very important that the control on these
DWDM systems should be well optimized for better use.

Internet Engineering Task Force (IETF) started working on the control planes of optical
transport networks and developed Generalized Multi-protocol Label switching
( GMPLS). GMPLS works as a control technique in the optical transport networks to
calculate the path between source and destination. The GMPLS control plane is for the
old TDM type transport networks like SDH, PDH, wavelength and fiber switching
techniques similar to MPLS that is used for IP traffic between switches and routers.
GMPLS control plane works in such a way that it dynamically allocates the resources as
per demand. Whenever there is demand for resource allocation, then the media resources
are allocated and remain spare when no requirements. This dynamic approach of GMPLS
has selected it as a better choice of control technique in the future transport networks.

14

MPLS has the benefit of being used for fast data transmission in data networks
comprising of switches and routers. Since Internet protocol technique is a not connection
oriented technique but when the MPLS is used it has information of both source and
destination. This path in determined before the packets are transmitted from one station to
the other. In order to further enhance the pace of data transmission in this type of system,
a label is used to identify the forward path of the packet. It not used the IP addresses to
check for the destination IP for path calculation. We can also provide the Quality of
service to the traffic using MPLS with the tables. The combination of both the label and
tables makes the LSP.
GMPLS uses the qualities of MPLS as a control plane. The protocols used in MPLS like
routing and signaling protocols are used in GMPLS as well for different TDM,
wavelength and fiber switched systems. The main purpose of using the MPLS techniques
in GMPLS is to provide automatic service provisioning methods that require fewer loads
on the management and dynamically uses the available network resources.
MPLS has good features for efficient routing and transmission of data in data networks
and with other TDM switches and wavelength multiplexed systems also had the
requirements to have a generalized control plane that can control the data transport
dynamically through these old systems. For this purpose the GMPLS idea was used that
is also using the LSPs that were used in MPLS network. The LSP not having labels in
GMPLS as were in MPLS, but for TDM it is having time slots, for WDM it is having
wavelength and also for fiber switching it is having fiber port in place of labels.
Very important feature that is quite new in optical transport networks and used in GMPLS
is dynamic and automated network management. As we see in SDH all kinds of services
are configured manuallay from one station to the other and we have to manullay create
the path traversing all the systems in the path. Such process is too lengthy and creates a
lot of load on the management system operations teams. If one ring is fully used and no
more resource is available in the ring then it is essential to upgrade the ring. After that the

15

wholebetwork will be informed manullay about this upgradation so that the resources are
further used.

1.2 GMPLS protocols

All the routing protocols like OSPF, IS-IS and signaling protocols like RSVP, CR-LDP
that were used in MPLS are now also used in GMPLS control plane. All these protocols
cover the TDM like SDH and WDM for wavelength networks.
Another very important protocol for signaling puposes in link management protocol
(LMP). It is used to have better conditions of control and data planes between the two
nearby stations.
Below table-1 summarizes these protocols and the extensions for GMPLS.

Table-1. GMPLS protocols

Description

Protocols

16

Routing

OSPF-TE,
IS-IS-TE

Signaling

RSVP-TE,
CR-LDP

Link
Management

LMP

These protocols are used for dynamic/auto discovery

of the network, all the necessary information like the
available bandwidth in the network is also shared
with all network elements.
Also works to check for the protection paths
availability. It shares some very important
information which is as under.
It shares what kind of protection to the traffic is
available (e.g 1 +1, 1 :1 or no protection)
In order to improve the quality it uses these new links
It broadcasts the information of links that are not
having IP addresses but the IDs of the link NEs and
the interface IDs of both ends.
It is also important to have calculated/identified the
protection path in case of failure (which is shared risk
link group).
These protocols are very important, used for making
the Label switched paths.
The important aspects are as below.
Since TDM, wavelength networks are used in
GMPLS so generalized labels are required instead of
labels in packer transport.
The generalized labels are always bi-directional.
Like routing protocols the signaling protocols also
use protection path for backup recovery.
After that the labels are assigned using the
Expediting label assignment via proposed labels.
These protocols have following aspects.
Link management with control-channel:
It shares link parameters, for example the frequency
sends the information to other end to check the link
status and also link strength using hello protocol.
PING-test verification: The PING test is used to
check the physical connectivity of the two joining
systems so that link management is verified.
Correlation of link possessions: It will identify the
properties of the link of all nodes connected together.
The properties may be of protection scheme used by
the nodes.
Fault Separation: It will separate a single or many
faults of the optical domain.

All these protocols can be seen in below Fig-1.

17

GMPLS protocols.

1.3 GMPLS challenges and the way out

Since GMPLS has to cover different types of equipments with different switching types
to provide a unified control plane, teherfore folliwng important issues are observed.
1. Forwarding of the data is as not just related to packet. The
GMPLS control plane should be able to provide the facility to
forward the data of TDM, wavelength and fiber switching also as
works with packets traffic.
2. The data carried by packets has the facility that it cab be
observed by the network NEs who carry this traffic. The packets
receive the header of packet, check for label and then the
output port having the forward path is determined and the
packet moves to this direction. But when we talk about time and
wavelength division systems then the packets are not identified
in these systems as these systems are not made for this
purpose.
3. As we know in TDM, DWDM and frequency switching the
bandwidth reservation of a label switched path is done as per
fixed units. But when we see in packet networks the bandwidth
of label switched path can be from 1 Mb/s to 100 Mb/s. Like is

18

TDM we have optical data rates of STM-1, STM-4, STM-16,

teherfeore the bandwidth allocation will be only as per earlier
mentioned data rates. If we have a packet network that has LSP
bandwidth requirement of 50 Mbps, so a fixed bandwidth pipe of
STM-4 is more than the requirements. Therefore the
requirements should be as per actual.
4. It is essential that the network should be made such that is can
cover all the network modification easily and quickly. Since the
TDM and optical networks are very large networks as compared
to those of packet switched systems, therefore it is required that
the proper network change adaptability be ensured. The
wavelength and fiber switched systems will have to use hundrds
of wavelengths in it.
5. It is not time saving job to have electronic and optical switches
as takes more time when there are hundreds of output ports
available for switching from input to output ports. All these types
of networks create too much delay in setting up label switched
path as mane input ports will be checked for switching to many
output ports.
6. Since in TDM networks like SDH we observe that the automatic
protection is observed in these systsems in case of failure of any
link. The restoration time is 50 ms. The GMPLS ssystems should
also ensure that the fast recovery mechanism is also adopted in
this system with dynamic/auto recovery process. The protection
mechanism may be fixed or automatic/dynamic.
All these challenges are discussed in detail is the below section.

1.3.1 Division of Generalized label

Generalized switching is required in the GMPLS based systems that have time
slots, wavelengths and fiver ports for switching. The generalized approach is used
in it in which the data is forwarded to the next node without considering what
kind of data it is and what kind of switching is involved. When we talk about

19

generalized switch it can have a time slot, wavelength or fiber as a generalized

label. GMPLS also carries the packet MPLS labels as well to carry packet traffic
as well.
Following important data regarding lables is available in GMPLS.
a) Label switched path need to be identified that what kind of label is used,
for example packet, TDM or wavelength.
b) Switching capability needs to be verified that what kind of switching
ability (packet, wavelength of TDM) the NE possesses.
c) It is important to know what kind of data/payload will be with the Label
switched path (data may be of Ethernet, SDH, ATM etc).
Label switching router of the main upstream node send the lables to the last
downstream node. The upstream node suggest labels for the downstream and
ultimately it covers the whole path.

1.3.2 Formation of Label switched path in GMPLS

Now we have an example to create LSP path from source to destination that has
packet switching at start. The TDM network used having SONET systems and
after that DWDM system used network two networks. Each layer has its different
Labels. The source is LSR1 and destination is LSR4. In the initial layer from
source we have OC-12 link between packet switching layer to TDM network.
After that It is network of TDM WITH OC-48 capacity. Then multiple OC-48
lines combine in the OXC1.

20

Formation of LSP in GMPLS network Fig.2

This cross connect is connecting multiple wavelengths of OC-192 data rate. Now
we want to create LSP from LSR1 to last LSR4.
Now it is very important that the LSPs should be established such that 1st of all the
downstream path LSPs should be established. These LSPs should be tunneled
with the higher level LSPs to have complete path between source to destication.
As per Fig.2 the LSP between LSR1 and LSR4 will have to carry all the labels of
in between network (TDM + WDM).
First of all a Request for label is forwarded downwards to the network from
upstream node as the downward nodes will share the LSP first. In this Fig.2, the
TDM system DSCi will forward the request to OXC1 mentioning the receiver
which is DSCe. This message received by OXC1 causes an action of one label
switch path creation between OXC1 and OXC2. With creation of this LSP, the
main LSP between DSCi and DSCe is made which is called LSPtDi.
What information is carried in this request for label creation is demand for
creation of generalized label for the label switch path. It carries the type of label
switch path (protocol of the layer and the what kind of payload it will carry for
example VC-4, VC-3. Some special properties like type of signal, automatic
protection mechanism, duplex Label switch path and the proposed labels are also
available in this label request. The downward system sends RESV/label mapping
message which has one generalized label and can also have many generalized
labels.
As the source LSR gets these generalized labels from downward systems then it
makes a label switch path to the destination LSR with RSVP/PATH message.
The actions performed in our case are as under.
1. Since a label switch path is established between OXC1 and OXC2
so with this a complete wavelength of 10 G is available for use.
2. Label switch path is made between DSCi and DSCe.

21

3. The TDM nodes at corners of the 02 TDM networks are also

having label switch path. Before that the label switch paths intra
networks must be made.
4. The end systems of LSR2 and LSR3 also make a label switch path.
5. At last the label switch path established between source and
destination.

1.3.3 Mechanism for data Transmission variety

As we know that Multi-protocol label switching systems have the intelligence of
identifying the packet headers and then performing required actions of data forwarding as
per the information carried by the headers including labels and the destination system
information. The data and control planes are separated when the labels are exchanges
between systems.
Generalized multi-protocol label switching uses the same kind of approach that
mentioned above. In it the control and data planes are separated physically or logically.
We can have the option to have different path for the control messages other than the data
path. We may have separate SDH signal for control. Generalized multi-protocol label
switching will not give orders that the control messages should be transmitted in this way.
The cost is involved in choosing any one option for transmission of the control
information. It is also not feasible to have just one SDH link to transport the control
information in a scenario when the systems are far apart in a SDH ring. A good idea for
use of the control messages in the existing network without involving any cost is to
transmit the control information through DCC channel of the SDH signal. These
overhead bytes will be used in each SDH link of joining nodes in the ring, so we will
have no single point of failure. This arrangement does not cause any bandwidth wastage
as it may happen if the control channel uses the space of data plane.

1.3.4 Structuring of GMPLS

22

In GMPLS the label switch paths are created from the last access side. These paths may
also require the LSP formation of intermediate systems that may have different structures
upto the destination node. Each of the intermediate devices has unique qualities which
GMPLS has to address so that LSP creation is fast and efficient.
In order to have insight about these differences following methods needs to be clear.

1.3.4.1 Proposed Label

There is one possibility available that we discussed earlier that there is an option with the
upstream system that it can propose a label to the next downward system to speed up the
process of LSP paths formation. But the downward system can reject this label and can
create its own made LSP. This is a lengthy process which may take too much time. If the
switching capacity of TDM system is e.g 622 Mbps then it will become long process to
allocate labels for multiple traffic. Proposed labels are used to speed up the process of
making LSP between source to destination. The SDH system is our example does not
wait for the labels from downward OXC layers and has its own label. It reduces the time
consumption if making the LSP end to end. But if the downward system not willing to
use the proposed label then it can use its own chosen label instead of proposed one.

1.3.4.2 Duplex Label switch path

As we know that SDH TDM systems use ring topology for provisioning of the protection
path in case of fiber cut conditions. Like TDM protection we have to protect the label
switch path to have the same protection of the path in case of any path failure. It can be
done by having two simplex LSPs. One LSP works as protection to the other.
Generalized multi-protocol label switching has the option for use of duplex LSPs with the
signaling protocols like RSVP/PATH. It becomes useful to avoid unnecessary sharing of
control information, route formation in optical networks.

23

1.3.5 Scaling
1.3.5.1 Forwarding Adjacency Label switch path
Forwarding Adjacency label switch path is used in GMPLS to get data of other LSPs. It
os contructed among 02 GMPLS systems as has its own characteristics and may be added
in routing protocols like OSPF and IS-IS. It can be used in the link state algorithm of
routing protocols to transport information of other label switch paths. It will ultimately
lower the load on database and time consumption in label search from the table is
reduced. These Forwarding adjacency label switch paths can be a number of unnumbered
data which may be attached with the other links information.
Figure 3. Forwarding Adjacency

In above Fig.3, we observe that the LSPtdm is the PSP which is connecting 02packet
switched networks. It makes the sense of just one LSP path between two packet networks
instead of combination of different networks.

1.3.5.2 Categorized label switch path

24

As we know the network categorization in access, METRO and WDM to carry the traffic
from source to destination, therefore the LSP hierarchy should be used for better us eof
the network. The data from source to destination will pass through different LSPs of
different networks. The TDM systems have fixed bandwidth for each LSP.
Fig.4 Hierarchy of network

Therefore it is not feasible to use a complete 10 G wavelength for just a data of 10 Mbps.
For this purpose it is better to aggregate the lower rate signals into higher rate for better
use of resources.
In Generalized multi-protocol label switching the LSPs are grouped together to aggregate
the traffic in main LSP having large capacity. The below Figure shows the architecture.
Figure 5. Hierarchical LSPs

1.3.5.3 Link Aggregations

25

Since the optical networks are supposed to have hundreds of the optical fiber lines
between 02 adjacent nodes and each fiber may also have many wavelengths in it. This
will give huge bandwidth availability for the Generalized Multi-protocol label switching
network. In order to efficiently use the network resources it is better to use bundling of
the network resources.
With this approach of bundling all this information is shared with routing protocols. With
this bundling we may have lost some data. But this method has great advantage that the
load on routing and signaling protocols is reduced too much extent. This bundle carrying
heavy data has only one control channel for exchange between systems.
The bundling can be done of point to point as well as label switch paths, which are shared
with the routing protocols.
We have some limitations for the use of bundling the links. All these mentioned below.
1. It is compulsory that bundling can be done only when the both
end source and destination are the same.
2. It is also essential that the links added in a bundle will be having
same type of the link for example point to point or point to multi
point.
3. It is also bound on the link that the link which is bundled will
have similar traffic characteristics like type of protection and the
band pipe used.

26

4. It is also essential that the switching type should be same for all
the members of the bundle for example Time switching,
wavelength switching or fiber switching.

1.3.6 Consistency
This is very important feature of this control plane is its capability for dynamic
restoration of faults in the network. It is important that whenever a fault occurs in the
network it must be separated from the network and restoration must be done after
separating from network. The label switch paths that are already tunneled with other label
switch paths must have such kind of consistency.
The process of the faults resolution is shown in below Figure.6

Figure 6. Fault-Management Process in GMPLS

Generalized multi-protocol label switching gives protection of the faulty channels among
both joining systems which is called span protection while source to destination
protection is path protection. Routing protocols broadcast all the information of this kind
of protection with the whole network and the protection route is calculated. After its
calculation a signaling is used with the RSVP and CR-LDP protocols. The secondary path
is calculated and when the fault occurs the signaling protocols switch the signals to
protection paths.

27

Whenever a fault occurs the dynamic fault recovery is achieved with shifting traffic to
protection path. The 02 dynamic procedures of restoration are line and path. In line
protection alternate path is selected at the system in between source and destination,
while in path receiver the restoration is started from the source system.
The below mentioned Figure.7 shows that system 1 starts for new path. Since much large
time taken for switching to protection path but it is bandwidth efficient as no media is
already allocated for this protected path.

Figure 7. Protection techniques used in GMPLS

1.3.7 Efficient Use of available resources

It needs some kind of optimization when we talk about use of TDM network with IPbased control plane. It needs to be discussed the major tendency of TDM network to use
IP addresses of packet network.

28

1.3.7.1 Numberless connections

In the time division and wavelength switching systems we do not use the IP addresses for
each such traffic. It is called numberless connectivity technique. The reasons behind this
technique are as below.
1. Since the time division and wavelength channels are quite large
in number for which IP address will be assigned. It takes too
much time to assign IP addresses for all these channels.
2. We do not have enough IP addresses and these are shot for use.
These links which are not having any numbers are identified by the router number and
some information of the link number. The other necessary information is carried by the
signaling protocols as done with the links having identified by IP addresses.

1.4 GMPLS unresolved problems

The GMPLS protocols are not standardized and there are many issues which need
solution, which are mentioned below.

1.4.1 Safety
As we know that the already used packet based systems use the IP address to identify the
traffic and the packet header has the complete information about originator and the final
end node IP addresses. These IP addresses are exclusive in the whole world and have
better security phenomena. But the labels which are used in GMPLS and MPLS are just
limited to the internal network and have nothing to do with the external network.
Therefore these labels cannot be used for security policy to give access control to the
systems. In order to have security in these networks it is required to use techniques like
that used in ATM and X.25.

29

1.4.2 Connectivity with other networks

GMPLS success is due to its property for connectivity and working with other network
techniques like ATM and Frame relay. Such connectivity with other networks results in
sharing of data and control information of 02 ATM networks when GMPLS used in
between 02 ATM networks.
Following issues are observed in making such connectivity.
1. It is very difficult for connectivity of 02 different control protocols.
For example the routing network used in ATM is private network
to network interface while for GMPLS it is open shortest path
first.
2. It is quite important to manage the quality of service when data
moves in 02 different networks.
3. As we know we can have TDM, packet switched, wavelength
switched and fiber switched networks. This makes very few
combinations of GMPLS with ATM and frame relay. The ATM and
frame relay have cells and frames of data.

1.4.3 Stability of network

Whenever a new network element id placed in network or someone removed, the much
large control data is shared by NEs with each other than that of old packet based systems.
Generic multi-protocol label switching performs TE which has information about traffic
parameters and using important protocols like Link Management Protocol. As per my
study this kind of network consumes large time to have stability than those old type
packet-based systems.

30

1.4.4 NMS
Old Internet protocol based systems use only the IP address to have reachability to that
systems, but when we talk about Generalized MPLS it has to deal with thousands of
Label switch paths to check for traffic monitoring and quality of services. It makes the
NMS more difficult to use in such networks.

Chapter-2

Software defined networking

2.1 What is SDN?
Software defined networking is a technique that is required to
be used in the latest computer networking centers in the world.
This technique performs separation of data and control planes
which provide common control scenario in the network. The
control plane is found in the software defined networking
controller. The path for the packet movement is determined with
this controller and then shares this information with all network
elements. It all special applications that run with the application
layer. These applications can run dynamically or through the
management system. This dynamic nature of control processes
enables the SDN network to provide fast service extensions. This
control plane minimizes the hardware cost of the optical
equipment with the use of control information in software that
runs over common hardware instead of working on optical chips.

31

2.2

SDN Architecture

2.2.1 Data plane

Data plane is the movement of data between the routers and switches through the
interface ports. The switches and routers can be connected with high data rate lines like in
Gbps. Two important information databases are available in every equipment in the
network. The 1st is the database to differentiate the packets and the other forwards the
packet to its destination through interface ports.

2.2.2 Control plane

It contains special procedures and methods that are used to find the path to route the
packets from source to destination. In the switches the control plane checks if the packet
MAC addresses matches the database then it forwards to the destination, otherwise if the
database not contains the information of packet then it sends the packet to all switches.
Routers use their own routing protocols for calculating the path.
Fig-8 SDN Architecture

32

Following are four important parts of this architecture.

The last two planes of data and control planes are not connected
with each other in a single network element. Control plane will

just send packet to next systems.

What and where to forward the packets are only dependent of
flow of packets. The forwarding is done at each network element
between A-end and Z-end elements. All kinds of equipment in the
network like layer-2, layer3 devices receive the same procedure

to send the packets from one end to the other.

There is a separate system available for control of the whole
network. It has software in it to perform these control functions.
All required programming of other network elements is done with

this control system.

There is important software running above the network operating
system which is the main control system. The software works
with the plane of data flow of the devices.

The common control nature has many benefits like it is very easy to change network
structure with high level software versions. It becomes quite difficult with system

33

dependent software. The common control works immediately whenever new network
changes are observed. The control plane has complete information of the network
changes and then acts accordingly.

2.2.3 Data forwarding

Data forwarding is very important and unique feature in SDN. The forwarding
information does not carry any information of the source hardware and hides its
information.

2.2.4 Data distribution

In SDN the data distribution control is also common. The network operating system
carried this distribution plane. It performs downloading network distribution information
of the network elements and gets all necessary information about the network elements
and connectivity between them for proper distribution.

2.2.5 Network specification

Network specification is done in network operating system with a required behavior of
network, which is supposed to be not done by control plane. It is a virtual technique in
which the specific configurations are mapped on physical network setup basis.
Below Fig-9 show the detail.
Fig.9 SDN architecture with abstraction

34

2.2.6 Advantages of Decoupling of control and data planes

Following are important benefits of using the separate control and data planes.

It is quite easy for running new applications as the

applications are shared due to common control plane.

It is seen that the applications run on the same network
for which this this control plane is used, so the other

parts of control plane are free for other services.

The control plane takes the actions for any network
element. In this way no need to have accurate
procedure for new network requirements for data

transmission.
All kinds of applications can be interconnected. We can
add different applications but the priorities are given to
certain applications.

35

2.2.7 Interaction of SDN layers

2.2.7.1 Software defined networking core controller
It is the main part in the operation and maintenance layers of the SDN and keeps all the
network related information with it. It performs main operations to provide required
actions in the network.

2.2.7.2 Use of vendor based Network Software

This is software which is made by the equipment manufacturer. It is installed in the
system which manages the network. The user gets it accessed from another computer and
works on it through some commands. The specific vendor based touch of this software
asks user to use specific commands which are only based on the vendor equipment. This
software is responsible to manage the whole network either single layered or multi
layered.

2.2.7.3 Use of Network Management System

Network Management system is used for some low level configurations of the transport
systems. It is used for making the arrangement so that the network elements are online
and accessible for further operations. This software makes configurations of transport
nodes regarding their ID, IP and the link establishment between the network elements.
This software is also vendor based and each vendor used its own specific network
management software. Like one vendor uses U31 software for this purpose. This is GUI
based software which enables users to have performed all operations efficiently.

2.2.8 SDN layers

2.2.8.1 Infrastructure layer

36

This is the layer which is related to hardware equipment installed in the network. These
equipment are not having any control information in them as SDN has the centralized
control plane. The data plane is not having any intelligence in it and all is available in
control plane.

Fig-10 SDN in (a) planes (b) layers (c) architecture

The intelligence is completely available in the network control and application plane. It is
seen that these networks are established along with Open Flow standards so that different
kinds of networks elements can be used together for data forwarding. The old
transmission equipment like SDH are not having this flexibility as many built-in
hardware requirements must be fulfilled in these equipment.
The below Fig-11 shows the SDN control and data devices.

37

Fig-11 Open flow enabled SDN devices

In the above Fig-11 the SDN elements are shown. One is the control element and other is
forwarding one. The control plane has a match table which has parts of rules, actions and
statistics of these data packets.
The table shows the process through which the packets have to move. We have the option
to choose one of the rule out of these mentioned for a packet to distinguish. The actions
with the packet may be sending to the out ports, send to control plane, discard, forward to
old forwarding line which is not open flow.

2.2.8.2 Southbound interface

These interfaces are in between control and forwarding planes, which clearly separate
these two important fields. Open flow field has made it very easy for the investors to help
them invest in the new technologies that can integrate multiple different types of
equipment.
Southbound interface performs some important actions. It shares the information with
control plane when the data port of forwarding device is changed, other is the traffic
information is also shared with the controller and the third is that it share the information
of data for which the data plane has no information about its forwarding.

38

2.2.8.3 Network hypervisors

The new latest computer networks are using a new technique of simulations. It has been
made effective in last few years. The resources are used based on simulated hardware not
the physical hardware resources.
This layer asks for the use of these simulated resources instead of asking for the physical
resources. The user demands for resources only when there is the requirement. It is great
benefit regarding revenue as the resources are always shared between users. This
technology has the important benefit that these shared resources can be shifted from any
physical machine to any other physical hardware which provides flexible network nature.
But still right now it is not freely used and the old physical fixed resources are used in
networks.
The capacity of any network can be calculated with its structure and the available place to
have network information. The network layers of different type require different types of
network resources. The layers can be Layer-2, Layer-3 etc. One network structure cannot
provide all kinds of requirements. The simulated networks are used to have best use of
the resources. The IPv6 will have limitations for use as machines may be using IPv4
scheme.

2.2.8.4 Network operating systems

It is observed that the old types of networks have the operating systems with them which
can only work with basic level of equipment and operate them with vendor specific
software. In addition to that some special commands with different programming
techniques are used to further better use these devices.
Different vendors have developed their own network operating systems which are very
well in the use and are fulfilling the requirements in better way as per service demand.
The research is there to have common control of the whole diverse networks with the
routing protocols which work with different kinds of network equipment.
Software defined networking has provided a common network operating system which
gives protocols that are used by all kinds of network. There is no requirement to see for
the details of data that is forwarded between devices in this operating system.

39

The control plane is run by this network operating system. The major classification of the
control planes is done in 02 categories. The one is the common and other is divided.
The common control software is a one source to manage all the network entities. It has
one software source and there may be any resource limitations in this kind of network.
The common resources have very high limit for data forwarding and thousands of data
forwarding can be managed with these controllers in one second.
The other one which is dispersed software is made as to handle a short or big network. It
may be centrally managed or physically distributed. The first one which is centralized can
be used for condensed data networks. The other is much hard to the different kinds of
failures. The separated control planes have the advantage that when a system is failed,
then the other system takes load of this faulty one. In a single control system, we have
only one system to perform control actions and all control function will be affected when
there is fault to this controller.
The controller performs important functions. It performs running of a program, activities
based on commands, service safety in case of any network failure. In addition to that the
network structure, control of devices in the network, data sending on smaller path and
data safety is also managed by controllers.

2.2.8.5 Northbound interfaces

The north bound interfaces are performing the operations of abstraction and implement
languages to program. There are different programming languages available for this
purpose. One program used Linux language which used Virtual file system application. It
is helpful for systems that are working on layer-1&2. The programming is different for
each operation as the applications like data forwarding, routing and protection and
different for each other.
Some applications are based on involvement of the applications in the systems. There are
certain rules which work for these applications. The network resources are allocated
automatically when there is demand for a particular service. When there is a requirement
of voice and data services then it is possible that unique bandwidth is allocated to that
service as per service requirement. There is also check to verify that the bandwidth
allocated does not surpass the set one by the network manager.

40

2.2.8.6 Language based virtualization

Virtualization has the ability to provide the service thought and also ensures the qualities
like protection. It shows the idea of one large switch which shows adding many
forwarding equipment which forward the data. Such centralized approach reduces the
complexity in data forwarding as becomes easy to make the network.
One such kind of language has the idea of objects. Each object has its own requirements
of data forwarding. The objects do not share the information with each other for any
particular service.

2.2.8.7 Programming languages

The research based on moveable program is quite latest in the latest computer networks.
The High level codes are helpful to resolve many issues faced on low levels. The high
level has following important aspects.

The codes required to program the devices (which forward the

data) are more simplified.

The programming is much problem resolution oriented which

becomes quite easy for the peoples involved in coding.

It enables to reuse the code as per requirement.
Makes the network virtualization possible

In software defined networking it will become very difficult that one application jobs do
not affect each other. It is found that every application has its own principles for data
forwarding which may be different for other application. In this way the systems that are
required to send the data to next end with face some clashes. This issue can only be
resolved with the languages used to program the applications.
The important benefit of this programming is its ability to build for virtual structure. The
idea of object oriented is also the same. It enables the programmers to consider only the
requirements and not think about the type of data used and how to manage this data.
High level languages serve the purpose of software defined networking with qualities like
its modular approach, composition covering whole network and data verifications. The
low level design has many challenges and to cover these challenges the high level is used
with approach as mentioned below.

41

1. This does not manage the service configuration on each

system and focuses on the whole network. Such issues
also observed in old systems.
2. Management work is made easy with the network
structure.
3. Different jobs for data forwarding are not connected with
each other.
4. Resolves issues which avoid data forwarding with dynamic
approach.
5. Reducing the time for data forwarding.
6. Immediate addressing of any kind of fault.

2.2.8.8 Network applications

It is taken as the network core. Particular control information is changed into the form of
instructions that further driver the devices which are used to send the traffic from one end
to the other. The idea in it is that the path is defined between the source and destination.
For this purpose a special instruction if followed by all systems from source to
destination.
SDN is used for any type of network which may be small or large. These old systems can
perform the other applications of the networks like the Laye-2 and Layer-3 protocols. But
special features can be performed with the SDN network only. Software defined
networking has important features like Optimization of data forwarding, data protection
and interconnectivity about devices.
Very important application of Software defined networking is to balance the load in
network. It combines the multiple requests from different users and does not need control
function for every request. It is quite useful to balance the load as per network
requirements. It avoids exerting load on a single network element or link.
In software defined networking it is possible to have routers configured dynamically. It
helps routers to have less data base of routing tables and routers are configured when
there is some data transmission required.

42

Chapter-3

3. Differences between GMPLS and SDN

3.1

Distributed and Centralized control

In SDN we enjoy the benefit of centralized control plane while GMPLS has the
distributed control plane. In GMPLS each node has to perform the control functions
regarding identification of link capacity, available bandwidth and service security as per
requirement of service. All nodes have the complete information about the mechanism to
select a link route in case when any service is required to be routed from Source to
destination in a network. In the distributed control scenario the 1 st node also has the
complete information about the destination and the path required to be used for the
packet. Each network element has to make the links in such a way that the service path is
completed and all this is done at the same time. In such scenarios it becomes very
difficult for the network to have optimum utilization of the network resources. All nodes
work together to make the connections established and the network becomes inefficient
for the traffic.
While the centralized one has the facility to use the network in more optimized way. The
distributed control cannot manage the efficiency of the routes from source to destination
and the same is possible with Software defined networking. In this control technique all
the network related information like paths, connectivity of nodes and bandwidth available
is stored in common software. It computes the path for the services centrally and can
manage in a better way as it has full picture of the network. The bandwidth requirement if
also fulfilled as the service path changing is done as per demand. With this the network is
used in efficient manner. Since it has complete information of the network so centralized
control plane provides opportunity to control the issue of delay in data transmission due
to long path usage. With this technique we can use the optimum path to avoid delay in
data transmission.
Software defined networking has 02 important interfaces. One is for the demand of
network resources from the network and other is for connectivity to Network
management systems which has full authority to use the network. One disadvantage of

43

the centralized control plane is that it is not as fast as GMPLS control plane when the
changes in network are observed. When any node is down or any connectivity between
nodes is disturbed the same cannot be instantly conveyed to the centralized control plane.
GMPLS has distributed control and is efficient in this scenario.
In Software defined networking, control domain is not placed at the same location as it
may be apart from each other for protection of the services. Each separate control domain
needs to be in close connectivity with all other control domains so that all information
between these controllers is shared and no ambiguity observed in the network. It is alos
possible that each separate control domain may be of different brand and company. The
control systems should be able to arrange communication between them even if they are
not of same type.
The difference in these two control techniques is as under.

Fig-12 (a) SDN control plane with centralized control (b) GMPLS control plane with
distributed control

44

3.2

Complication of control plane

The control plane becomes much complicated with the use of GMPLS. The routing
protocols used in it like Open Shortest Path First are not beneficial for the network that is
altering its condition quite frequently. It makes the network less reliable. Similarly the
Reservation protocol that was initially used for the end user to get the network resources
has now been used in Multi-Protocol Label switching. It helps the network to get the
Label switching path resources. With the same idea this protocol used in Generalized
Multi-Protocol Label Switching. All these advancements in this protocol made it more
and more complicated and reduced its efficiency. GMPLS always tries to have
information related to different types of equipment in the network. The independence of
these equipment and retaining the identity makes the network quite more complicated.
Network complication is reduced with the use of Software defined networking. In it there
are no Open shortest path first and Reservation protocols and the unified interface of
Open Flow is used along with many operating systems which are interconnected with
each other.

3.3 Non-Flexibility for new control plane

In GMPLS there is no option available for resilience to the use of control plane that is
new in the network. The people who are to operate the network do not find it easy to us
the new control plane with the existing. It takes a long time when the new control plane
can synchronize with the needs of the network. Therefore it is the continuous process that
the network operators should be looking for the new plane that is very much close in
process to the existing.
In SDN we use to add the control plane with a new technique in which the new control
plane is placed among the already working control planes. This control plane then divides
the circuit plane into many parts. Each part is then controlled by a different control plane.
The network operator has only control over the data plane that has not been divided,
while all the other divided data planes are controlled by the separate control planes. With
this division there is also benefir that the control plane does not take packet and circuit

45

switching separately and only one data plane is considered if controlled by a single
control plane.

3.4 Different services provisioning

Generalized multi-protocol label switching provides different services for the users
which make differentiated from the Software defined networking.
GMPLS provides services of optical virtual private network. In this network each
user is sharing the optical fiber resources between the nodes. Each user is allocated
separate media resources in the GMPLS network which make them independent in
service provisioning as well as operation and maintenance.

Fig-13 Connectivity of OVPN users in a network

46

As per above mentioned diagram, the different optical virtual private network users are
connected to one management server. Both the users have different links for operation
and maintenance of the network. These users can manage their GMPLS services from the
network. Each network management user first allocates resources in form of bandwidth
to the customer. After that it monitors the traffic associated with that customer and
performs necessary operations when there is further requirement of media resources for
that particular customer.
Another important GMPLS service is user network interface (UNI) service which is
provided through the GMPLS network. When a user connect to the GMPLS systems
through this interface then it automatically send the GMPLS request to the network to get
the services. In this service each user who is asking for connectivity to the other user
sends all information regarding the source node address and sink node address. The nodes
on receiving this information change the node addresses into their identification numbers.
After that the path is calculated and the end to end trail is made. The service level is also
available in the message information generated by the user. After that the path is
identified as per service level.

3.5

Industrial application of SDN

SDN in transport network is a new idea for the generalization of the networks. It is
separate planes for transport and control. It is used in core networks to have new
applications. The use of SDN in Telecommunication industry has high importance
regarding its new features.
Software defined networking is providing following important features to Telecom
industry which were not provided by GMPLS and old Transport technologies.

3.5.1 Important benefits in Telecom industry

The important benefits gained by SDN over GMPLS is telecom industry as below.

47

3.5.1.1Use of special software tools

The old transport technologies like SDH, DWDM, ASON and GMPLS in transport
network were not having any features to use special software tools to properly plan the
telecom network. The planning was done only using the manual approach. Software
defined networking has given the good features to plan the network using a software tool.
Also all the planning was done prior to commissioning of the network. So it did not
provide the real time application. When there was some abnormality in the real time
working of the systems then it was not handled by old systems. SDN gives real time
solution to the problems using proper coordination between the tools.

3.5.1.2 Combined management

This is the important feature available in SDN that it provides a simple and easy
management of the tools to manage the equipments. It helps to lower the expenses to
maintain the equipment and also can work to improve the equipment as per the
requirements.

3.5.1.3 Synchronization
SDN provides an important feature that it provides the synchronization between transport
equipments of different vendors, which was not possible in legacy transport technologies.
Along with this SDN provides the synchronization between the core network and the
transmission network to have a single control plane. It gives a simple understanding that
managing a single control plane is easy other than to work on different control planes of
different vendors.

3.5.1.4 Flexibility
The flexibility of the SDN planes makes it possible for interconnection of devices that are
using multi-layer services. The Multi-layer devices make it possible to work together
with a common control plane of SDN.

48

3.5.1.5 Directness
This is the important feature available in SDN that it gives direction that any vendor
equipment can be connected to any other vendor equipment using the unified control
architecture.
All these important features are available in one of the top vendor in Telecommunication
vendors in the world. This is ZTE Technologies which has this important feature.
ZTE is the now the leading company to provide the transport equipments in different
parts of the world.
ZTE has developed the important features of SDN which are well beyond the scope of
legacy transport networks. The important features used by ZTE are shown below in
detail.

3.5.2 ZTE SDN special features

ZTE provides following special features with the use of SDN.

3.5.2.1 Dynamic extension of services

Since SDN is using the important feature of centralized controller, therefore it is possible
that a common centralized controller can well manage the network to provide services
from one end to the other. Since all type of the systems are controlled by this common
controller, so this controller has the database of all the available resources of the network.
It cannot be possible to provide such dynamic services using the distributed control plane
of the old transport technologies.
The distributed control system of GMPLS gives following drawbacks which reduce
efficiency of the transport equipments.

The distributed control system is used to cover only the faults of

specific areas and is unable to cover the whole network. Since
the whole network comprises of multiple vendors or multiple
technologies,

therefore

proper

synchronization

distributed control planes is not possible.

49

of

different

When a new network is going to be established or existing

networking is expanded then it can be done using the
information to plan the network for service configurations. After
using a planning tool the available data is exported to the
network management system. After that configuration is done.

All this long process reduces the system efficiency.

When the new routes are discovered for new service provisioning
and the data is shared with the NMS, then the services can be
created on the network. This also reduces the efficiency of the
network as consumes too much time from network planning to
service provisioning.

The SDN provides a common controller. Whenever there is the requirement of new
services. The controller automatically searches for the new service routes. In this way
the SDN feature makes the network to give complete management. Resultantly the
efficiency is improved, which is the main feature of SDN.

50

Fig. Dynamic extension of services

3.5.2.2 Restoration of services using common controller
When any fault is observed on working or protection label switched path of any trail
service then the corresponding network elements ask centralized control plane for the
restoration of the services. The centralized controller finds the most feasible route for the
new path. The new path is then forwarded to the specific network elements. The NEs get
this information and then configure the services.
This restoration of the services is makes the network more efficient. The controller has all
the information about the network. Therefore the rerouting of the services becomes quite
fast.
The service rerouting can be done based on the priority as well. It gives the planning
information based on the priorities.

Fig. Restoration of services through centralized controller

51

3.5.2.3 Possibility of availability

Transport SDN has the option to prompt about the chance of any fault occurrence in the
network. It gives analysis about any fault occurrence. It uses simulation to check for the
network status during any fault occurrence. Through simulation the SDN control plane
gives real time warning about the network survival.
The user performs the simulation to check the result of fault. When the fault is created
then SDN control plane checks the available resources and calculates that which services
will be interrupted. It computes the path of the services which will be rerouted and
highlights those services which will not be restored.

Fig. Analysis to check survival of resources

52

References
[1] A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic
Engineering (TE) Label Switched Paths, IETF RFC 5152, February 2008.
[2] A Backward-Recursive PCE-Based Computation (BRPC) Procedure to Compute
Shortest Constrained Inter-Domain Traffic Engineering Label Switched Paths, IETF
RFC 5441, August 2009
[3] The Application of the Path Computation Element Architecture to the Determination
of a Sequence of Domains in MPLS and GMPLS, IETF RFC 6805, November 2012
[4] P. Iovanna, A. Germoni, F. Testa, G. Cossu, V. Lopez, R. Sabella, " Multi-layer
Control for Packet-Optical Networks," in Journal of Optical Communications and
Networking, Vol.5, Issue 10 pp.A86-A99.
[5] Thomas A. Limoncelli. Openflow: a radical new idea in networking.
Commun. ACM, 55(8):4247, August 2012.

53

[6] A.T. Campbell, I. Katzela, K. Miki, and J. Vicente. Open signaling

for atm, internet and mobile networks (opensig98). ACM SIGCOMM
Computer Communication Review, 29(1):97108, 1999.
[7] A. Doria, F. Hellstrand, K. Sundell, and T. Worster. General Switch
Management Protocol (GSMP) V3. RFC 3292 (Proposed Standard),
June 2002.
[8] D.L. Tennenhouse, J.M. Smith, W.D. Sincoskie, D.J. Wetherall, and
G.J. Minden. A survey of active network research. Communications
Magazine, IEEE, 35(1):8086, 1997.
[9] D.L. Tennenhouse and D.J. Wetherall. Towards an active network
architecture. In DARPA Active NEtworks Conference and Exposition,
2002. Proceedings, pages 215. IEEE, 2002.
[10] J.T. Moore and S.M. Nettles. Towards practical programmable
packets.
In Proceedings of the 20th Conference on Computer Communications
(INFOCOM). Citeseer, 2001.
[11] Devolved Control of ATM Networks.
http://www.cl.cam.ac.uk/research/srg/netos/old-projects/dcan/#pub.
[12] J. E. Van Der Merwe and I. M. Leslie. Switchlets and dynamic
virtual
atm networks. In Proc Integrated Network Management V, pages 355
368. Chapman and Hall, 1997.
[13] J.E. Van der Merwe, S. Rooney, I. Leslie, and S. Crosby. The
tempesta
practical framework for network programmability. Network, IEEE,
12(3):2028, 1998.
[14] J. Rexford, A. Greenberg, G. Hjalmtysson, D.A. Maltz, A. Myers,
G. Xie, J. Zhan, and H. Zhang. Network-wide decision making: Toward
a wafer-thin control plane. In Proc. HotNets, pages 5964. Citeseer,
2004.
[15] A. Greenberg, G. Hjalmtysson, D.A. Maltz, A. Myers, J. Rexford,
G. Xie, H. Yan, J. Zhan, and H. Zhang. A clean slate 4d approach
to network control and management. ACM SIGCOMM Computer
Communication Review, 35(5):4154, 2005.
[16] Y. Jarraya, T. Madi, and M. Debbabi, A survey and a layered
taxonomy
of software-defined networking, Communications Surveys Tutorials,

54

IEEE, vol. PP, no. 99, pp. 11, 2014.

[17] N. Feamster, J. Rexford, and E. Zegura, The road to SDN, Queue,
vol. 11, no. 12, pp. 20:2020:40, Dec. 2013.
[18] R. Presuhn, Version 2 of the Protocol Operations for the Simple
Network Management Protocol (SNMP), RFC 3416 (INTERNET
STANDARD), Internet Engineering Task Force, Dec. 2002. [Online].
Available: http://www.ietf.org/rfc/rfc3416.txt
[19] J. Pan, S. Paul, and R. Jain, A survey of the research on future
internet
architectures, Communications Magazine, IEEE, vol. 49, no. 7, pp.
2636, July 2011.
[20] N. Feamster and H. Balakrishnan, Detecting BGP configuration
faults
with static analysis, in Proceedings of the 2nd conference on
Symposium
on Networked Systems Design & Implementation - Volume 2, ser.
NSDI05. Berkeley, CA, USA: USENIX Association, 2005, pp. 43
56.
[21] R. Barrett, S. Haar, and R. Whitestone, Routing snafu causes
internet
outage, Interactive Week, 1997.
[22] K. Butler, T. Farley, P. McDaniel, and J. Rexford, A survey of BGP
security issues and solutions, Proceedings of the IEEE, vol. 98, no. 1,
pp. 100122, Jan 2010.
[23] J. Sherry and S. Ratnasamy, A survey of enterprise middlebox
deployments, EECS Department, University of California, Berkeley,
Tech. Rep. UCB/EECS-2012-24, Feb 2012.
[24] K. Greene, MIT Tech Review 10 Breakthrough Technologies:
Software-defined Networking, http://www2.technologyreview.com/
article/412194/tr10-software-defined-networking/, 2009.
[25] P. Newman, G. Minshall, and T. L. Lyon, Ip switching—atm
under ip, IEEE/ACM Trans. Netw., vol. 6, no. 2, pp. 117129, Apr.
1998.
[26] N. Gude, T. Koponen, J. Pettit, B. Pfaff, M. Casado, N. McKeown,
and
S. Shenker, NOX: towards an operating system for networks, Comp.
Comm. Rev., 2008.

55

[27] H. Jamjoom, D. Williams, and U. Sharma, Dont call them

middleboxes,
call them middlepipes, in Proceedings of the Third Workshop
on Hot Topics in Software Defined Networking, ser. HotSDN 14. New
York, NY, USA: ACM, 2014, pp. 1924.
[28] H. Alkhatib, P. Faraboschi, E. Frachtenberg, H. Kasahara, D. Lange,
P. Laplante, A. Merchant, D. Milojicic, and K. Schwan, IEEE CS 2022
report (draft), IEEE Computer Society, Tech. Rep., February 2014.
[29] M. Casado, N. Foster, and A. Guha, Abstractions for softwaredefined
networks, Commun. ACM, vol. 57, no. 10, pp. 8695, Sep. 2014.
[30] A. Doria, J. H. Salim, R. Haas, H. Khosravi, W. Wang, L. Dong,
R. Gopal, and J. Halpern, Forwarding and Control Element Separation
(ForCES) Protocol Specification, Internet Engineering Task Force,
Mar. 2010. [Online]. Available: http://www.ietf.org/rfc/rfc5810.txt
[31] H. Song, Protocol-oblivious Forwarding: Unleash the power of SDN
through a future-proof forwarding plane, in Proceedings of the Second
ACM SIGCOMM Workshop on Hot Topics in Software Defined
Networking, ser. HotSDN 13. New York, NY, USA: ACM, 2013, pp.
127132.
[32] T. D. Nadeau and K. Gray, SDN: software defined networks, 1st ed.
OReilly, 2013, vol. 1.
[33] N. M. K. Chowdhury and R. Boutaba, A survey of network
virtualization,
Computer Networks, vol. 54, no. 5, pp. 862 876, 2010.
[34] B. Davie and J. Gross, A Stateless Transport Tunneling Protocol for
Network Virtualization (STT), Internet Engineering Task Force, April
2014. [Online]. Available: http://tools.ietf.org/html/draft-davie-stt-06
[35] M. Mahalingam, D. Dutt, K. Duda, P. Agarwal, L. Kreeger, T.
Sridhar,
M. Bursell, and C. Wright, VXLAN: A Framework for Overlaying
Virtualized Layer 2 Networks over Layer 3 Networks, Internet Draft,
Internet Engineering Task Force, November 2013. [Online]. Available:
http://www.ietf.org/id/draft-mahalingam-dutt-dcops-vxlan-06.txt
[36] M. Sridharan, A. Greenberg, Y. Wang, P. Garg, N. Venkataramiah,
K. Duda, I. Ganga, G. Lin, M. Pearson, P. Thaler, and

56

C. Tumuluri, NVGRE: Network Virtualization using Generic

Routing Encapsulation, Internet Draft, Internet Engineering Task
Force,
August
2013.
[Online].
Available:
http://tools.ietf.org/id/draftsridharanvirtualization-nvgre-03.txt
[37] F. Maino, V. Ermagan, Y. Hertoghs, D. Farinacci, and M. Smith,
LISP Control Plane for Network Virtualization Overlays, Internet
Engineering Task Force, Oct 2013. [Online]. Available: http:
//tools.ietf.org/html/draft-maino-nvo3-lisp-cp-03

57