Study of Qos Efficiency in Deployment of Mpls and MPLS/ Diffserv
Study of Qos Efficiency in Deployment of Mpls and MPLS/ Diffserv
Study of Qos Efficiency in Deployment of Mpls and MPLS/ Diffserv
Abstract
The Multi-Protocol Label Switching (MPLS) protocol has contributed to the
Internet routing, traffic engineering and quality of service required for new services.
It would be interesting to compare the QoS performance of MPLS and MPLS /
DiffServ networks, taking into account their particular constraints.
In this article, we evaluated the QoS performance metrics such as delay variation,
delay, response time, throughput for different traffic types (voice, data and video) for
both platforms MPLS and MPLS / DiffServ.
The objective is to compare the performance of MPLS and MPLS / DiffServ using
"OPNET Modeler v14.5" using the latest simulation techniques, where different QoS
parameters can be measured to compare the performance of networks.
Our approach in this work is to design and build an operator network typebackbone
to simulate a real scenario that conveys different types of traffic (voice, data and
video).
The results of the work are presented according to the simulation time and the
network load. The results of the comparison demonstrate the advantage over the
performance of MPLS networks with diffserv compared to traditional MPLS networks.
1. Introduction
The objective of our research is to present first the characteristics of the architecture
of NGN networks, and to make a detailed study for the implementation of a core
network based on an IP / MPLS platform.
1.1. NGN
NGN or Next Generation Network in English (literally "New Generation
Network") is a phrase frequently used in the telecommunications industry,
especially since the early 1990s[1].
1171
International Journal of Pure and Applied Mathematics Special Issue
unique network core that enables it to provide subscribers with multiple services
(voice, data, audiovisual content, etc.)
MPLS allows to efficiently solve the tunneling functionality, since the routing
of the packets is not carried out on the destination address of the IP packet but
on the value of the label assigned to the packet.[4].
1172
International Journal of Pure and Applied Mathematics Special Issue
With MPLS technology, QoS [5-6] is a crucial element for an operator network.
Indeed, the operator must be able to guarantee to his customers the transport
of their flows by guaranteeing different constraints. The quality of service is
mainly divided into four parameters: throughput, delay, jitter and loss.
1173
International Journal of Pure and Applied Mathematics Special Issue
This application is closely related to the quality of service, since its immediate result
is the improvement of parameters such as delay or jitter in the network. It is still
regarded as an application in its own right by most manufacturers. This is because
MPLS TE[9] is not a simple resource reservation technique for network applications.
It is a more general concept that aims to be a solution that aims to increase the overall
performance of the network by playing on the balanced distribution of loads (traffics)
in the network so as to have a more optimal use of the links.
Figure 1 below shows the physical topology of the network of this simulation
1174
International Journal of Pure and Applied Mathematics Special Issue
a) Source of Trafic :
The traffic sources are generated by the client nodes of the objects (node) from which
we associate the application profile that presents the configuration of multiple
applications. We used Ftp, voice and video in our simulation.
The figures below show the chosen values and parameters of our traffic model.
Trafic Ftp :For Data traffic (FTP), the service type is AF11
Trafic Voice :For voice traffic, the encoder is GSM FR, the service type is AF31
Trafic Video:For video traffic, we use an average resolution of 15 frames / sec
(frame / sec) of 128x240 pixels, setting the DSCP field to AF41.
The network we have set up allows us to achieve a continuity of service between the
IP networks (representing the local networks) and the MPLS network (representing
the Operator network).To ensure this continuity, we use the DSCP to EXP mapping
table[10]
This principle consists in copying the value of the ToS field of IP in the EXP label of
MPLS. It is used by the LER routers (as input to the MPLS network). It ensures the
"translation" of the class values between IP and MPLS.
1175
International Journal of Pure and Applied Mathematics Special Issue
The ToS field [11] of an IP packet consists of 8 bits. The value of this field
can be configured according to the approach, as defined in the original IP
specification using four parameters [RFC 791].
These parameters are Delay, Throughput, Reliability and Precedence. The
Precedence parameter defining the importance of the datagram can take the following
8 values: (0) Best Effort, (1) Background, (2) Standard, (3) Excellent Effort, (4)
Streaming Multimedia, Multimedia, (6) Interactive Voice and (7) Reserved.
The ToS field of IP packets can also be configured using the Differenciated Services
Code Point (DSCP) approach [RFC 2474] used with IP networks supporting the
Diffserv quality of service architecture. In this case, the ToS field takes one of the
values defined for the different service classes of this architecture.
The value of this field can then be: Expedited Forwarding (EF), Assured Forwarding
(AF1, AF2, AF3, AF4). If the service class of the packet is AF1 to AF4, there is
added a value defining the priority to be deleted if necessary: AFx1 for packets
having priority not to be deleted, AFx2 for packets which can be deleted at need,
AFx3 for packets of class x to be deleted first.
A Traffic trunk [12] is not part of the foundation of MPLS technology. In an MPLS
network without traffic engineering, the packets characterized by a FEC follow the
corresponding LSP. Traffic Trunk is a concept related to traffic engineering. To move
traffic where there is bandwidth, the FEC associates traffic to another LSP, it is
Traffic Trunk that is associated with another LSP. When traffic engineering is used,
FEC associates traffic to a Trunk Traffic that is associated with one or more LSPs.
OPNET requires the use of Traffic Trunk. To configure those used in our simulation,
1176
International Journal of Pure and Applied Mathematics Special Issue
we must edit the Traffic Trunk Profiles attribute of the MPLS Configuration object.
For our simulation, we have configured a Trunk profile for voice traffic and another
for video and other for FTP. The Trunk profile associated with the voice is
characterized by any maximum and average bit rate. Indeed, its capacity will have to
vary according to the needs determined by the prediction of the bandwidth
requirements determined by the admission control function.
The excess traffic will not be deleted and the Trunk's service class is Expedited
Forwarding to ensure the desired bandwidth and minimize the delay and jitter of voice
packets.
For the video, a different Trunk will be used to mark this traffic with a different class
of service. This Trunk will have a maximum and average throughput of 64,000 bps.
Excess traffic will not be removed and the class of service will be Assured
Forwarding 41.
Each traffic type must be associated with the corresponding specific LSP [13] , and
which carries traffic to the destination PE router. The association of traffic to the LSP
is performed on the LER_1 (Traffic Mapping Configuration) device router (see figure
below)
FTP traffic will be routed through the LSP (in Green) (LER1 LSR_1
LSR_4LSR_7LSR_8LSR_9LER2)
1177
International Journal of Pure and Applied Mathematics Special Issue
Voice traffic will be routed through the LSP (in Red) (LER1 LSR_1
LSR_2LSR_3LSR_6LSR_9LER2)
The voice service does not have a backup LSP (in case of a break)
The video traffic will be routed through the LSP (in Blue) (LER1 LSR_1
LSR_5LSR_9LER2)
The activation of MPLS differs depending on the location of the router in the
backbone, in the 9 P routers we have enabled MPLS on all interfaces while in both PE
routers MPLS is enabled only on interfaces linking these routers to routers P We
chose the LDP protocol to distribute the MPLS labels.
Figure 4 : FTP response time with light load (Blue - MPLS, Red - MPLS /
DiffServ)
The MPLS response time is higher than the MPLS / DiffServ network. We notice that
1178
International Journal of Pure and Applied Mathematics Special Issue
the MPLS network with DiffServ provides better performance in response times for
FTP-based traffic.
Figure 5 : FTP traffic response time with heavy Load (Blue - MPLS / DiffServ; Red-
MPLS)
After increasing the load on the network (heavy load), the response time for MPLS
changes to a very high value, but DiffServ remains about the same as shown in Figure
5.
Then we pass on the study of network performance when traffic is the voice. We will
compare between the two scenarios MPLS and MPLS_ DiffServ. Figure 6 and Figure
7 illustrate the end-to-end delay parameters for light load and heavy load traffic.
Figure 6 : End-to-end traffic delay Voice with light load (Blue - MPLS; Red - MPLS /
DiffServ)
1179
International Journal of Pure and Applied Mathematics Special Issue
Figure 7 : Delayed end-to-end traffic Voice with heavy load (Blue - MPLS / DiffServ;
Red-MPLS)
Figures 8 and 9 show the delay (jitter) variations of voice traffic for light load and
heavy load traffic.
Figure 8: Variation of delay time (jitter) of traffic Voice with light load (Blue - MPLS;
Red - MPLS / DiffServ)
10
1180
International Journal of Pure and Applied Mathematics Special Issue
Figure 9: Variation of the Delay Delay (Jitter) of Voice heavy load traffic (Blue -
MPLS, Red-MPLS / DiffServ)
Figure 10 : Video End-to-End Delay with Light Load (Blue - MPLS; Red - MPLS /
DiffServ)
11
1181
International Journal of Pure and Applied Mathematics Special Issue
Figure 11 : Video End-to-End Delay with heavy Load (Blue - MPLS / DiffServ; Red-
MPLS)
The end-to-end delay for video stream is higher for MPLS than MPLS / DiffServ.
After the load increases, the end-to-end delay for MPLS becomes very high and keeps
increasing. While the MPLS / DiffServ delay remains at a low level. This shows that
MPLS / DiffServ offers better quality even in congested network with higher loads,
while in MPLS, the delay increases to a very high value.
Figure 12 : Variation of the delay time (jitter) of video traffic with light load (Blue -
MPLS; Red - MPLS / DiffServ)
The variation of the delay in FIG. 13 demonstrates the best quality of the MPLS /
DiffServ service.
12
1182
International Journal of Pure and Applied Mathematics Special Issue
Figure 13 : Variation of delay of video traffic with heavy Load (Blue - MPLS /
DiffServ; Red - MPLS)
After the increase in traffic load, the results of FIG 13 are evident that the delay
variation has increased to a very high value for MPLS, while the variation of the
MPLS_ DiffServ delay has remained at a very low value, keeping the quality of
service performance to the required level.
For all the parameters discussed above, MPLS with DiffServ demonstrates better
performance on both Heavy load and light compared to MPLS.
The response time of FTP traffic on MPLS_ DiffServ with Heavy Load was lower
than MPLS.
The delay of voice and video traffic as shown in Figures 6-13 demonstrates that
MPLS / DiffServ has a lower delay value than MPLS; the value of the delay on the
Heavy Load model becomes much more important.
13
1183
International Journal of Pure and Applied Mathematics Special Issue
The delay values for voice and video are less than 150 ms, according to the ITU-T
standard.
4. Conclusion
Consider in our simulations that the combination of DiffServ and MPLS presents a
very attractive strategy for the network service providers since it makes it possible to
ensure the load sharing and the quality of service demanded by the customers.
However, managing this type of network is not a simple function and can not be done
manually.
and it is in this sense that our perspective presents a new archetecture of automation
of MPLS management with diffServ based on the SDN.
5. References
5.1. Journal Article
1. Ito, A., & Fukuda, K. (2016). Next-generation Network Architecture Led by Information-
Centric Networking. FUJITSU Sci. Tech. J, 52(1), 53-60.
5. ADEWALE, Adeyinka A., MATTHEWS, Victor O., AGBOJE, O. E., et al. Performance
Enhancement of Quality of Service of IP Mobility for Real-Time Traffic. International Journal
of Computer Science and Telecommunications, 2017, vol. 8, no 3, p. 13-17.
5.2. Book
14
1184
International Journal of Pure and Applied Mathematics Special Issue
13. BERZIN, Oleg et MALIS, Andrew. Mobility support using MPLS and MP-BGP
signaling. 2008.
Authors
15
1185
1186