Vol. 8 No.

1, January 2017 ISSN 2079-8407

Journal of Emerging Trends in Computing and Information Sciences
©2009-2017 CIS Journal. All rights reserved.

http://www.cisjournal.org

Analysis of MPLS and IP Networks Performance to Improve the

Qos using Opnet Simulator
1
Alia Albdoor, 2Ghassan Kannan
1 a9l9i9a.99@gmail.com, 2 gkanaan@aau.edu.jo

ABSTRACT
To eliminate the problems related to the Internet Protocol (IP) network, Multi-Protocol Label Switching (MPLS) networks the
packets, they use label switching technology at the IP core routers to improve the routing mechanism and to make it more
efficient. The developed protocol configure the data packet with fixed labels at the start and the at the end of the MPLS domain,
it also allows a service provider to provide value added services like Virtual Private Network (VPNs), MPLS is faster than the
standard method of routing and switching packets of the data. MPLS traffic engineering (MPLS TE) provides better utilization
of network recourses, while MPLS offers VPN implementation and interconnected with other networks to gain secure and
reliable communication, MPLS was improved to support routing functionality on conventional service provider IP Network.
MPLS permit service providers to provide customer support services, and It naturally supports Quality of Service (QoS) by
providing classification and marked package, avoid congestion, congestion management, Improve traffic, and Signaling. MPLS
is not complex at all, and there is no need to any changed in the network structure because it uses one Unified Network
Infrastructure. Also, no need to run Border Gateway Protocol (BGP) in the core of MPLS network, this will increase the
efficiency of Internet Service Provider (ISP). Therefore MPLS provide the reliability of communication while reducing the
delays and supporting the speed of the packet transfer.
.
Keywords: Mpls network, ip network, traffic engineering, virtual private network, quality of services, label switching path, fe class.

1. INTRODUCTION There is a need to reach the quality standards while

In an accelerating world, that is overcrowded with
technological developments which made our world closer
despite the distance, and due to rapid progress in the Internet
and networks, we found growth in many of the services and
applications that depend on the network applications that have
appeared. All these developments took an important role in
people's lives, like The social networking revolution, E-
Learning, E- commerce, etc.
This massive use of networks has led to a significant
increase in the number of Internet users which causes high
pressure on networks and internet services. Moreover, it
affects the performance in a negative way, reduces the
available quality of service, and perhaps threaten its
performance seriously. With all that challenges, the real-time
applications such as voice and video showed a problem in the
performance while using traditional routers, due to challenges
in providing high bandwidth, fast routing, as well as the
quality of services (QoS).
Many studies have appeared attempts to solve this
problem. Mpls technology was one the most important
advanced techniques that have been used to address this
problem. This work will explain how MPLS technique is used
to improve the performance of networks, where MPLS
technology has a significant role in supporting the quality of
services for many applications like voice and video.
designing the network. To achieve the best result in the
services such as high bandwidth, fast routing, and the Quality
of Services (QoS), as well as to provide acceptable solutions
to avoid network errors or failure, also to protect data packets
from loss. Furthermore to reduce the delay and the cost of
building a network, and provide a better mechanism to
overcome Network defects and limitation.
2. IP AND MPLS CONTRADICTIONS AND
SIMILARITIES
With IP technology, routers forward the IP packets to
the destination IP address through looking at the IP header and
finding the precise match in the routing table. In the
beginning, the IP table lookup was so simple but with unicast
and multicast IP addresses the IP table lookup became
sophisticated and needed more time than before.
IP require multiple network checking while
forwarding packets, which is considered a time consuming
and causes congestion with a significant delay in forwarding
process.
Real-time applications like IP telephone need high
prediction and minimum End to End delay, so we need a new
smart IP network that supports sufficient real-time and
Interactive audio and video applications. (Sllame & Aljafar,
2015).

MPLS technology supports QoS and traffic
engineering, and it uses labels to transfer the packets in order
to improve packets forwarding speed, and it supports the
ability to control traffics and to override several boundaries
such as high packet loss and extreme delays in the network.
Growing demands to display packages need to be
fulfillment, Internet Service Providers (ISP) need suitable
high-performance equipments for switching and routing. Most
ISP inner cores use ATM (Asynchronous Transfer Mode).
ATM uses a complicated and expensive virtual circuit to carry
data packets. Furthermore, the links toward these ISP still use
frame relay that is slow and causes latency, time delay and

1
 Vol. 8 No. 1, January 2017
Journal of Emerging Trends in Computing and Information Sciences
©2009-2017 CIS Journal. All rights reserved.
http://www.cisjournal.org
suffocation (bottleneck) in terminal access points. ( Murade,
Ingale & others, 2012).
Network core direction selectors (Routers) can cause
network delay because each one of them takes individual
decisions about the best direction or path to forward the
incoming packets.
IP routing was designed to calculate the shortest path
towards the destination. Routing is done in IP networks
specifically in the (Network layer) which is slower than the
switching. The links in the IP networks can be under-utilized
or over-utilized that are caused by the routing process, results
in congestion with over-utilized links also TE (Traffic
Engineering) is difficult to implement in the IP networks since
IP networks are not scalable. (Sharafali, Al-Quzwini & Fyath,
2015).
MPLS can deal with a different payload, recognize
layer 2, Ethernet encapsulation, and all dynamic routing
protocol, also it is capable of identifying and dealing with
IPV4, IPV6, ATM, Frame Relay... etc., this is why it is called
multi-protocol.
Additional label added to the packet that runs through
the MPLS technology, so forwarding the packet depends on
the label that was added which defined the source and
destination address. MPLS came as the better and most
supported technology for the IP, it has overcome the
limitations of other technology like ATM and FRAM
RELAY.
MPLS label is placed between the second layer and
the third one, and comes as a shim between them, as it is plain
in (Figure 1). It is a short fixed length identifier which is used
to identify FEC (forward error correction). Every label stack
entry is a 32-bit length, and it is divided into four fields. The
first is the labels' value 20-bits, next one is EXP 3-bits that
takes the role of QoS and used to show the service type, it's
ranged from 0 to 7 depending on the characteristic type of
service (CoS). Next is S 1-bit which give only two
possibilities either One means it's the last card or Zero which
refers otherwise, and finally TTL 8-bits that is used to prevent
the Loop, where it is decreased by one every time until it
reaches zero.
Figure 1: MPLS label stack.
MPLS has special devices that have the main role in
representing the MPLS network, with the following three
main components:
Provider router (P): is placed in the core of the MPLS
network, it can be more than on routers, router serial 7200 is
ISSN 2079-8407
mostly used in IOS (Internetwork Operating System) also
there are different types of routers that can be used.
Provider Edge (PE): a router that is on the edge of the
company between the internal ISP network that runs MPLS
and any other networks where MPLS has no control over
them. PE is located in the core centrals for MPLS network.
Customer Edge (CE): exists between the customer
network that he can controlled and any other external out of
customer administration network.
When PE receives the packet coming from CE, as
shown in (Figure 2), it adds a label to this packet by LDP or
UDP. Those labels are switched at each PE then the packets
are forwarded through MPLS router until they arrive their
destination, P and PE take the role of LSR (Label Switch
Router).
Figure 2: Forwarding equivalent class.
Incoming packets from CE router A are called FEC.
LSR received those packets and forwards them based on the
label and MPLS. PE1 take the decision about forwarding the
packet. The path that determined by the packets called LSP
which can pass through one or more MPLS routers until its
arrived to its destination.
In more details, when the packet is received from the
IP domain the label edge ingress router will check the
information in layer three in the packet and find a reference
for that particular packet type called FEC. Then the label for
that class pushed into the packet and then the packet is
forwarded to the MPLS domain. This label is held in a shim
header between layer 2 and layer 3. Inside the MPLS domain,
the packet arrives at the LSR where it checks the LIB (label
information base) which contains the previous label and the
next one. Then swaps the label (label swapping is responsible
for looking up the incoming label to determine the outgoing
label encapsulation and port) with a new one and forwards it
to the MPLS domain. Finally, the packet arrives at the egress
label edge router, and the LER (label edge router) remove or
popped the label and forwards the packet to the IP domain
according to the IP forwarding rules.
IOSXR is a new featured and flexible router that was
added by Cisco, which is different from the one we know, the
basic idea of this router is the capability of handling large and
essential operations to be suitable to put it in the core. Its
2
 Vol. 8 No. 1, January 2017
Journal of Emerging Trends in Computing and Information Sciences
©2009-2017 CIS Journal. All rights reserved.
http://www.cisjournal.org
distinctive characteristics distinguishing it from other routers
like preemptive, memory protected, multitasking and
microkernel based operating system. (Cisco, 2015).
IOSXR has different privileges like high availability,
scalability, package based software to remove and install
packages according to the need, also patching and updates
which allow making downtime while the system still running,
unlike old programs that make this during patching and
update.
QoS is aimed at addressing delay problem using a
different type of tools, in order to control and manages packet
transmission through different types of operation. Like
Classification: recognize the packet and what type of data it
holds, Marking: use a certain mark to Indicate packet content,
Policing: delete the excess packets (traffics), Shaping: take
excess packets and put them in the queue, when a shortage
occurs it covered this shortage and evaded congestion.
MPLS Naturally Supports QoS through Classification
and Marked Package: package classification allows traffic
movement to be split into several levels of priority or service
quality, Avoid congestion: congestion can be avoided through
the weighted random early detection (WRED) algorithms,
which is mounted on the network interfaces in order to gain
entry management, Congestion management: When the
network entry becomes congested it is necessary to use
stacking techniques to make sure that the critical applications
have the priority instead of non-critical application, some of
the stacking methods could be priority stacking, normal
stacking and potential stacking, Improve traffic: traffic
control and imaged can lead to improve the traffic within the
network, imaging traffic flowing with specified rate will
facilitates the use of entrances, and monitors that determine a
specified required rate, Signaling: RSVP is the main
mechanism to control traffic access through network.
The importance of QoS is not limited to transit or to
increase certain traffic but also to convey it as soon as possible
and for that better management of resources needed to be done
(Dhuri&Shaikh, 2014).
MPLS has the ability of traffic engineering, which is
the process to determine the paths for the flow of traffic and to
balance the traffic load through different links. Several parallel
paths are available and can provide fault tolerance within the
underlying network. It overcomes the problem of delays and
massive packet loss that can be found with traditional IP
networks by congestion control and scalability. (MPLS-TE)
create Label Switched-Paths (LSPs) along with links with
available resources, and this ensures that bandwidth will be
always available for specific flow and can avoid congestion
(Sabri, 2009).
The main important role of TE is the efficient use of
available network resources, and it can provide better service
quality of applications on the Internet. MPLS-TE utilizes
Constraint Based Routing that takes bandwidth, policies, and
network topology into account for establishing a path and
forwarding the packets.
ISSN 2079-8407
An encapsulation mechanism in the MPLS VPN can
simply describe that the PE router encapsulates IP packet
through pushing two MPLS labels. The label at the top of the
stack is called (outer label) is switched by P (provider) routers
in order to transited packet to specified router. Label at the
bottom of the stack is (inner label) is left untouched, it can be
used by the egress PE to recognize the right L3VPN. It is
noticeable that the inner label is so important because routers
could serve a different type of customer, and address spaces
that could be overlapping, where routers could be serving two
distinct VPNs for two customers with different addresses
(Cittadini, Di Battista, & Patrignani, 2012).
When PE router gets a packet from a CE router, it
catches the VPN identifier and the destination address while
depending on information contained in its MP-BGP (RIB),
and finds the next PE router that the packet should be sent to.
MP-BGP (RIB) also holds the inner label that must be used.
The egress PE router pushes the inner label and an outer
MPLS label that is guaranteed to carry out the packet to
specified router, the outer label maps specified router that is
distinguished by the Label Forwarding Information Base of
that router, which is also the forwarding table for MPLS.
With IP routing, every router should build routing
tables, and the network by using one of the different routing
protocols like OSPF, IS-IS, RIP or BGP. Each router in the
network must individually take routing decisions for every
incoming IP packet after building the routing tables, and this
will be time-consuming. Routing tables are checked by every
router at the arrival of a packet to figure out the following hop
for the packet depending on the destination address for the
packet given in the IP packet header (Akinsipe, Goodarzi&
others, 2012).
Every router within IP should compute the shortest
path from itself to the other one and store the identity for the
next router. IP cause random delay and also some packet loss
because of sequence number might drop when there is
congestion in network, and this means there is great need to
improve QoS (Murade, Ingale & others,2013).
Within MPLS every node forwards a labeled packet
without the need for any independent forwarding decision.
The IP routing in contrast, which is susceptible to any routing
changes, and independent forwarding decisions are performed
through determining the longest prefix match from the routing
table at every hop through the path. Diversely, the MPLS TE
path is calculated just one time by the head end, without any
care to any route changes through a network (Vadhwani and
Kulhare, 2013).
3. RELATED PREVIOUS STUDY
Through reading various previous studies in this area,
some notes were found. One of the most certain criticisms on
previous studies that they conducted their analytical study
based on the office network, and this is not close to reality
cause it does not give real results. The network must adopt a
way to expose the pressures that face real networks. Based on
that we decide to build a world network, so we chose global
network type world which is closer to the real life network.
3
 Vol. 8 No. 1, January 2017 ISSN 2079-8407
Journal of Emerging Trends in Computing and Information Sciences
©2009-2017 CIS Journal. All rights reserved.

http://www.cisjournal.org
The study done by slime, member, et al, (2015)
characterizes performance estimation of multimedia data
streaming through IP and MPLS networks. An experimental
study was executed through VOIP and video streaming
applications in both networks with same performance metric
using different routing technique. The achieved results support
that the MPLS networks are the best alternative for real-time
applications than conventional IP networks. (Sllame, Member
and others, 2015).
The study done by dhuri and shaikh (2014) indicates
that the prescience of new uses confirms the need for a better
(QoS) not just for transmitting accurately or increasing
specific traffic, but also in order to convey traffic as quickly as
possible. So this leads to developing a technology known as
Multi-Protocol Label Switching (MPLS). According to MPLS
technique mechanisms QoS, TE and security become
reasonable for IP network like DiffServ, IntServ/RSVP to
earn end-to-end quality of service while MPLS is more
simple, scalable and best among them (Dhuri and Shaikh ,
2014).
In this paper they have simulated and approved that
MPLS TE is able to process incoming traffic efficiently
through classifying the traffic through many LSPs according
to FEC, which can't be implemented in conventional routing
protocol (Sulaiman and Alhafidh, 2014).
This paper explains and analyze the utilization of
merchant IP/MPLS and protection relay hardware to backing
power system protection tasks using multiple protocols,
(IP/MPLS) a certain and far distribute technology with service
providers worldwide. IP/MPLS has the potential to safely
develop the efficiency of power system communications
contrasted with legacy TDM solutions, without victimizing
performance or reliability (Coffele and others, 2014).
They explained that there are many algorithms that
work on QoS development in MPLS networks but until now
they didn't provide better results. They confirmed that they
could improve the QoS parameters by implementing enhanced
techniques, retain better survivability by employing advanced
algorithms for better efficiency. Then comparing their results
with the presence conventional techniques with the support of
simulation results (Kundu, Kumar and Wason, 2014).
them has the same precise configuration with an internet
connection between them. Thus, we have two scenarios with
the same topology. The first network use IP technology only
while the second use MPLS embedded to the IP network. We
added another scenario with MPLS configuration and
topology but we applied the MPLS VLAN to investigate and
evaluate its effect on the performance. After running each
scenario individually, we analyzed the results and compared
them in order to reach clear idea about what we had obtained
and draw our conclusion.
In this study, we have focused on the network
construction process, as we have noted previous studies and
researches did not take into account the network architecture
model, also one of the most important criticisms on the
networking models is that they measured the performance
only for local networks, like an office network.
These simple networks do not give a true measure of
possible outcomes because its capabilities are limited, as in
networks containing a limited number of components like
routers, switches, links and other nodes. So it will be not
enough to subject and expose the networks problems, and it
would express a limited time with a short distance. Therefore
they would not be exposed to real pressures such as
congestion, loss of data and delay.
From this point, we decided to test the network that
containing several components and works on a large scale
with more time and longer distance, so we chose global
network type world which is closer to the real life networks.
4.1. First Scenario (ALIA_Network Analysis: Scenario IP)
This Name: contains two subnets with Internet connection
between the that was built according to the IP technology
mechanism, so we established this network with respect to the
IP routing strategy applied in a traditional network as shown
in Figure (3).

4. NETWORK MODEL AND SCENARIOS

IMPLEMENTATION
After we run OPNET, we started the process of
building our network. We chose the name of our project
(Alia_ Network analysis), and we started with an empty
network topology because of the intention to create our
network using objects from objects palette.
Figure 3: IP network configuration and topology.
Our network scale will be the world and this is the
type of network we will represent, we choose a map that
would determine the geographical size of the network, and
then we select the type of technologies for our networks.

We establish a network with two subnets, which they

are between Amman_ subnet and Baghdad subnet. Each of

4
 Vol. 8 No. 1, January 2017
Journal of Emerging Trends in Computing and Information Sciences
©2009-2017 CIS Journal. All rights reserved.
http://www.cisjournal.org
Figure 4: IP Amman subnet.
The configuration was set to start, see (Figure 4),
with these devices for Amman subnet, Device Name:
eth16_ethch16_fddi16_tr16_switch (two switches). This
device was set up using the device creator utility and it
contains these technologies: IF/Port Count, Ethernet 16 and
Ether Channel 16.
Device Name: The ethernet_wkstn node model (16
nodes for each subnet) It performs a workstation with client-
server implementation running through TCP/IP and UDP/IP.
The workstation backs one underlying Ethernet connection at
10 Mbps, 100 Mbps, or 1000 Mbps.
This wkstn needs a fixed amount of time to route
every packet, as specified by "IP Forwarding Rate" node
attribute. Packets are routed based on a first-come-first-serve
basis and might encounter queuing at the lower protocol
layers, and relying on the transmission rates of corresponding
output interfaces.
Device Name the 100BaseT duplex link & 1000
BaseT duplex link: Symbolized an Ethernet connection
operating at 100 Mbps, It could connect any combination of
the next nodes, Station, Hub, Bridge, Switch and LAN nodes.
Device Name: (The ethernet4_slip8_gtwy node
model) The ethernet4_slip8_gtwy node model expresses an
IP-based gateway supporting four Ethernet hub interfaces, and
eight serial line interfaces. IP packets arriving on any interface
are routed to the appropriate output interface based on their
destination IP address. The Routing Information Protocol
(RIP) or the Open Shortest Path First (OSPF) protocol may be
used to dynamically and automatically create the gateway's
routing tables and select routes in an adaptive manner. This
gateway depend upon a fixed amount of time to route each
packet as resolved by the "IP Routing Speed" attribute of the
node. Depending on a first-come-first-serve basis packets are
routed and may face queuing at the lower protocol layers.
Depending on the transmission rate of the corresponding
output interface the model represents a particular
configuration of IP-based router Model, where IP packets
arriving on any IP interface are routed to the suitable output
interface based on their destination IP address.
ISSN 2079-8407
Device Name: The ethernet2_slip8_firewall node
model, symbolized an IP-based gateway with firewall features
and server assistant. So it can be also called as a multihued-
server firewall node. It back two Ethernet and eight serial line
interfaces at selectable data rates. IP packets arriving on any
interface are routed to the suitable output interface depend on
their destination IP address.
Device Name: ethernet_server model (we use five of
them to perform our selected application). This represents a
server node with server applications running through TCP/IP
and UDP/IP. This node enhances one underlying Ethernet
connection at 10 Mbps, 100 Mbps, or 1Gbps. The operational
speed is specified by the connected link's data rate.
We use six Ethernet server model to performed six
application investigations, which are as follow: voice (IP
telephony), video (high resolution), HTTP (heavy browsing),
Database (high load) and Email (high load).
Figure 5: IP Baghdad subnet.
This subnet (Figure 5) contains the same type of
nods, ethernet2_slip8_firewall node model, the
ethernet4_slip8_gtwy node model (nine of them), The
100BaseTduplex link & 1000 BaseT duplex link,
eth16_ethch16_fddi16_tr16_switch, The ethernet_wkstn node
model and eth16_ethch16_fddi16_tr16_switch. For parent
subnet, we should add two main components that are needed
for each network, the Application configuration node and
Profile configuration.
Device Name: Application configuration node
Specifies applications using obtainable kinds, we can specify a
name and the corresponding specification in the process of
setting up new applications.
Device Name: the Profile Configuration node It is
used to create user profiles, and these user profiles can then be
specified on various nodes in the network to create an
application layer traffic. The application is defined in the
"Application Configuration" and objects are used by this
object to configure profiles, so you should create applications
using the "Application Configuration" object before using this
object.
5
 Vol. 8 No. 1, January 2017
Journal of Emerging Trends in Computing and Information Sciences
©2009-2017 CIS Journal. All rights reserved.
http://www.cisjournal.org
Device Name: IP Attribute configuration this Defines
the attribute configuration specification for protocols
enhanced at the IP layer. These specifications can be
referenced by the individual nodes using symbolic names.
Device Name: the ip32_cloud node model This is an IP cloud
supporting up to 32 serial line interfaces at a selectable data
rate through which an IP traffic can be modeled. IP packets
arriving on any cloud interface are routed to the appropriate
output interface based on their destination IP address.
Device Name: PPP_DS1
Connects two nodes running IP, DS1 (1.544 Mbps).
Device Name: PPP_DS3
Connects two nodes running IP, DS3 (44.736 Mbps).
4.2. Second Scenario (ALIA_ Network Analysis: Scenario
MPLS)
This MPLS scenario is the same as the first one
except that we have changed the type of links used to connect
nodes and changed the type of the main router and added
MPLS Label Edge Routers and Label Switch Routers as you
can see in Figure (6). MPLS configuration determines the FEC
paths and other attributes configuration.
Figure 6: MPLS Amman subnet.
Device Name: ethernet2_slip8_ler node model (LER)
This model represents an IP-based gateway running MPLS
and supporting up to two interfaces and up to eight serial line
interfaces at a selectable data rate. IP packets that reach any
interface are routed to the suitable output interface based on
destination IP address.
Device Name: The ethernet2_slip8_lsr node model
(LSR) an IP-based gateway running MPLS and supporting up
to two Ethernet interfaces and up to eight serial line interfaces
at a selectable data rate. IP packets arriving at any interface
are routed to the appropriate output interface based on
destination IP address.
Device Name: PPP_SONET_OC3, type of link that
Connects two nodes running IP OC3148.61 Mbps, This is the
data rate available to the user after accounting for the SONET
overhead.
Device Name: MPLS configuration objects through this model
we will define the paths and setup FEC names for MPLS
scenario, so we determined the name of forwarding
ISSN 2079-8407
equivalence classes (FEC) that we created with static
mappings and traffic trunks, which are used to define different
types of traffic, see (Figure 7).
We have placed an MPLS configuration object in the
project workspace and open its attributes dialog box, then
Double-clicked on the value for FEC Specifications. The FEC
Specifications table appears, we replaced the rows value to the
number of FECs we want to create. For each FEC, we assign a
name, and then double-click on the details column to describe
the FEC.
Then the model requires that we set up at least one
default traffic trunk. Additional trunks can be used to handle
prioritized flows to create a Traffic Trunk. After place with
MPLS configuration object in the project workspace and open
its Attributes dialog box then Double-click on the value for
Traffic Trunk Profiles, the Traffic Trunk Profiles Table
appears, and we change the rows value to one then Specify a
name for the trunk after that Configure the Trunk Details
attribute.
After we create the LSPs, FECs, and traffic trunks,
we can create the static mappings or TE bindings that decide
which packets are sent to which LSPs, we do this in the LER's
MPLS >MPLS Parameters > Traffic Map Sending Traffic
over LSPs
Figure 7: MPLS configuration objects.
Before we can transit traffic through an LSP, we need
to configure the traffic mappings that support traffic with a
specific LSP. We have two ways to connect traffic with an
LSP, static mappings and IGP shortcuts.
In static mappings we make forwarding equivalence
classes (FECs) and traffic trunks (which is the total of traffic
flows that are forwarded through a shared path and share a
common (QoS) requirement), that are used to relies on
various kinds of traffic.
After we create the LSPs, FECs, and traffic trunks,
we could make the static mappings or the TE bindings which
decide which packets are sent to which LSPs. We do this in
the LER's MPLS > MPLS Parameters > Traffic Mapping
Configuration attribute. Device Name: ethernet_server model
(we use five of them to perform our selected application)
6
 Vol. 8 No. 1, January 2017
Journal of Emerging Trends in Computing and Information Sciences
©2009-2017 CIS Journal. All rights reserved.
http://www.cisjournal.org
Device Name: The ethernet2_slip8_firewall node
model Device Name:The ethernet_wkstn node model (16
nodes of them for each subnet)
Device Name: eth16_ethch16_fddi16_tr16_switch (two
switches)
Device Name The 100BaseT duplex link & 1000 BaseT
duplex link.
Baghdad subnet has this configuration with these devices as
you can see in ( Figure 8).
These two components for each network must hold
the Device Name: Application configuration node This
specified applications using obtainable application kinds, and
we can specify a name and the corresponding specification
during the process of setting up new applications.
Figure 8: Application configuration node.
Device Name: the Profile Configuration node this is
used to create user profiles, and these user profiles can be then
specified on various nodes in the network to create an
application layer traffic. The application defined in the
"Application Configuration" objects are used by this object to
configure profiles, so we should create applications using the
"Application Configuration" object before using this object.
Device Name: the ip32_cloud node model
Device Name: PPP_DS1
Device Name: PPP_DS3
5. NETWORK MODEL AND SCENARIOS
IMPLEMENTATION
We study the parameters that affecting the
performance of MPLS network and IP network and earn ways
for obtaining optimal performance, which will give the
specification of MPLS network routing technique with the
functionalities and their design metrics. This research is
ultimately concentrated on the performance evaluation of
packet receive and sent for different applications. Also
measure the delay, respond time, download respond time,
Packet End to End Delay, Jitter and packet delay variation
over IP network and MPLS network by employing the
application of traffic engineering and other implementation of
ISSN 2079-8407
QoS by using DiffServ architecture. Also in order to decide
which of the scheduling algorithms must be used to implement
QoS in order to execute better, it went through details and
basic of the MPLS network operation and compare them with
IP ones. We have examined six applications with specific
performance parameter, which are:
(a) Email (High load): Traffic Received (Packet/sec), Traffic
Sent (Packet/sec), Download respond time(sec), Upload
respond time/sec,
(b) HTTP (Heavy browsing): Traffic Received (Packet/sec),
Traffic Sent (Packet/sec)
(c) Voice real time application: Jitter (bytes/sec), Traffic
Received (Packet/sec), Traffic Sent (Packet/sec)
(d) Video (High resolution video):Video Packet Delay
variation, Video Packet End -To- End Delay(sec), Traffic
Received(Packet/sec), Traffic Sent (Packet/sec)
(e) Ethernet: Delay
(f) DB Query: Traffic Received (Packet/sec), Traffic Sent
(Packet/sec)
5.1 Measuring Traffic Sent and Received Over Internet
MPLS Network Scenario and IP Network Scenario
This parameter indicates total packets that are sent (in
transmitting table) or received (in Received table) on that
interfaces in a specific period. Traffic flow determines the
number of packets within each network scenarios, which
indicates the type of QoS that explains the performance
quality through its ability to convey more packets via the two
scenarios over various applications.
Figures 9 and 10: Voice and video traffic received
(packets/sec) over MPLS and IP network.
From Figure (9) it is clear that there are more number
of packets received through MPLS TE scenario than IP
scenario. MPLS TE conveys 3000 packets of data in 10
minutes while IP conveys about 2600 packets in the same
amount of time, which means that MPLS TE gives us better
throughput and reliability in packets transmission.
In Figure (10) MPLS-TE network more than 4500
packets can be sent in ten minutes while in IP network 4200
packets can be sent at the same time.
7
 Vol. 8 No. 1, January 2017
Journal of Emerging Trends in Computing and Information Sciences
©2009-2017 CIS Journal. All rights reserved.
http://www.cisjournal.org
Figure 11, 12: HTTP and DB query traffic sent packet/sec
over MPLS and IP network.
HTTP traffic can be received and sent better in
MPLS network than IP network, as shown in (Figure 11).
More packets can be delivered and give better throughput by
applying MPLS network. DB Query traffic received and sent
better in MPLS
(Figure 12) network than IP network and delivers
more packets and gives better throughput by applying MPLS
network.
Measuring Delay/sec
Delay in the network is a serious sign of performance
prosperity of a computer network and telecommunications
network. The delay for the network determines how long it
needs a bit of data to be transported over the network from one
node or endpoint to another. It is usually measured in
multiples or fractions of the seconds. Delay can be differed
based on the location of specific two communicating nodes.
The users just care about the total delay of a network, while
engineers report the maximum and average delay.
There is a minimum level of delay that can be
experienced according to the time it takes to convey a packet
through a link. There are different variable levels of delay
according to network congestion, and delays in the IP network
can differ from a few milliseconds to many hundreds of
milliseconds.
As delay is a critical factor in network performance,
we take it in to account to investigate and analyze our network
performance, so we checked it through this application.
Ethernet Delay /sec over MPLS and IP Networks
The delay in MPLS Ethernet starts with 0,0004 part
of the second while the IP Ethernet start to increase to 0.0006
part of the second then increase more and more to be at the
end of simulation up to 0.0029 while the MPLS Ethernet still
less than 0.0028. This indicates that it introduce more delay in
the IP network and MPLS still better in reducing network
delay.
Packet delay variation for video conferencing is
begin to decline in MPLS network after the fourth minute and
keep dropping down until the end of the simulation. While in
IP network its keeps moving up until the end of simulation to
have about 7000 packets while just 6000 packets for MPLS
network, with a difference of about 1000 packets for MPLS
benefit.
ISSN 2079-8407
Video conferencing packet End_To_End Delay/sec
End To End delay for MPLS network is less than IP
network, which provides us a clear view of the effectiveness
of MPLS TE network in real time application.
MPLS network requires an email download services
less than 0.03 part of the second when the download is
beginning. It then begins declines until the end of the
simulation, while in the IP network its start download at 0.10
and declines near more than 0.03 but still is near 0.02 until the
end of the simulation as seen in (Figure 13).
Figure 13: Email upload response time/sec.
MPLS network requires an email upload services less
than 0.03 part of the second at upload beginning, then begin to
declines until the end of the simulation, while in the IP
network it starts upload at 0.10 and declines near more than
0.03 but is still near 0.02 until the end of the simulation.
6. CONCLUSION AND FUTURE WORK
MPLS has proved to be faster than the standard
method of routing and switching packets of the data. It's not
complex at all and no need to any changed in the network
structure because of the use of one Unified Network
Infrastructure. There is no need to run BGP in the core of
MPLS network, so that will increase the efficient of ISP,
MPLS provide a combination of a high-performance
forwarding mechanism connection establishment. While
mapping into various lower layer technology, data path
protection, operation, administration and also maintenance
functions (OAM functions).
The importance of MPLS is represented in
performing TE, it has the capability to monitoring where and
how traffic is routed on our network, to administrate capacity,
prioritize several services, and stop congestion. It performs
Multi-Service Networks and has the capability to convey data
transport services like IP routing services.
MPLS provide combination of a high-performance
forwarding mechanism connection establishment, mapping
into various lower layer technology, data path protection,
operation, administration and also maintenance functions.
We can see from the analysis results that MPLS with
TE mechanism provide greater performance in real time
application in traffic sent and received and provide less delay
in End To End packet delay. Also it provides highly respond
time in downloading and uploading application services.
8
 Vol. 8 No. 1, January 2017 ISSN 2079-8407
Journal of Emerging Trends in Computing and Information Sciences
©2009-2017 CIS Journal. All rights reserved.

http://www.cisjournal.org
REFERENCES
[1] Akinsipe, O., Goodarzi, F., and Li, M. (2012).
Comparison of IP, MPLS and MPLS RSVP-TE
Networks using OPNET. International Journal of
Computer Applications, p58(2)
[2] Blair, M., Coffele, F., Booth, C., De Valck, B., &
Verhulst, D. (2014). Demonstration and analysis of
IP/MPLS communications for delivering power system
protection solutions using IEEE C37. 94, IEC 61850
Sampled Values, and IEC 61850 GOOSE protocols.
[3] Cittadini, L., Di Battista, G., and Patrignani, M. (2012).
MPLS virtual private networks. Recent Advances in
Networking, 1, pp: 275-304
[4] (Cisco,2015),availableat:http://docwiki.cisco.com/wiki/F
ile:CT842801.jg
[5] Kanchan, D.,and Alam, S.(2014).Review on QoS
Improvement with MPLS Mechanism in NGN.
International Journal of Innovative Research in
Science,Engineering and Technology, Vol. 3.
[6] Murade, R., Ingale, P., Kale, R., and Sayyad, S. (2012).
Comparative analysis of IP, ATM and MPLS With their
QoS. International Journal of Innovative Technology and
Exploring Engineering (IJITEE) ISSN: Pp, 2278-
3075,Volume 2.
[7] Sabri, H. (2009). QoS in MPLS and IP
Networks (Doctoral dissertation, Blekinge Institute of
Technology).
[8] Sharafali, S. A., Al-Quzwini, M. M., & Fyath, R. S.
(2015). Performance Evaluation of MPLS TE Signal
Protocols for Voice Applications with QoS
Implementation. International Journal of Networks and
Communications, 5(1), 1-9.
[9] Sllame, M., and Aljafari, M. (2015). Performance
Evaluation of Multimedia over IP/MPLS
Networks. International Journal of Computer Theory and
Engineering, 7(4), 283.
[10] Sulaiman, A., and Alhafidh, O. (2014). Performance
Analysis of Multimedia Traffic over MPLS
Communication Networks with Traffic
Engineering.International Journal of Computer Networks
and Communications Securitik,2(3), pp: 93-101.
[11] Vadhwani, N., and Kulhare, D. (2013).traffic analysis of
DSR, AODV and OLSR using TCP and
UDP. International Journal on Computer Science and
Engineering, 5(4), p 221.
[12] Wason, A., Kumar, A., and Kundu, R.
(2014).Performance analysis and improvement in QOS
of MPLS networks, Ambala College of Engineering &
Applied Research, 1(2).
AUTHOR PROFILES
Alia Ali Albdoor received the B.S. from Arab Open
University in Amman at 2013, and M.S degree in Computer
Science from Amman Arab University (AAU) in 2016.