• No results found

QoS Strategy in DiffServ aware MPLS environment

N/A
N/A
Protected

Academic year: 2021

Share "QoS Strategy in DiffServ aware MPLS environment"

Copied!
15
0
0

Loading.... (view fulltext now)

Full text

(1)

QoS Strategy in DiffServ aware

MPLS environment

Teerapat Sanguankotchakorn, D.Eng.

Telecommunications Program,

School of Advanced Technologies

Asian Institute of Technology

(2)

Quality of service

• transparency

• throughput

• accessibility

Service model

• how capacity is shared

Traffic engineering

• how much capacity

• routing, ...

Network business model

•congestion pricing •volume pricing

Technology

(3)

Differentiated Services (DiffServ)

• Required Mechanisms for Service Differentiation

-

Classification:

To identify the aggregation (class) to which a packet belongs based on their different QoS requirements.

– Scheduling:

To determine which packet will be transmitted according to its priority specified by DS Code Point.

– Queue Management:

To decide which packets will be dropped, when the buffer overflows in the case of network congestions.

Marker Meter classifier Conditioner Incoming Packets Outgoing Packets

(4)

Multi Protocol Label Switching (MPLS)

– Fast routing

– Provide bandwidth management

– Less load on core routers

– Use of labels in packet headers

(short, fixed length and locally significant)

– Traffic engineering

(classification and identification of IP packets with a label and forwarding the packets to a switch or router that is modified to operate with such labels.

– Signaling protocols used in MPLS

(Label Distribution Protocol (LDP))

(5)

DiffServ + MPLS

• A scheme which is mutually beneficial for both…

– MPLS provides DiffServ with Path protection

and restoration.

– DiffServ acts as CoS architecture for MPLS

(6)

Domain Model

LSR

LSR

LSR

LSR

LER

LER

LER

LER

Diffserv aware

MPLS Domain

LSP

Some kind of mapping is required to convert IP header values to label

(7)

Mapping DiffServ to MPLS

Why:

•Label Switch Routers (LSRs), don’t see the IP header and DSCPs in ToS field of IPv4 header.

•LSR only reads the Label contents and decides the next hop

How:

•The contents of 6 bits DSCP is mapped into 3 bits EXP field of Label There are two options to map DSCP value into the Label…

E-LSP

EXP-inferred-PSC LSP

•PHB is determined from EXP bits •No additional signaling is required •EXP-PHB mapping is configured •Shim header is required

•Up to 8 PHBs per LSP

•With Bandwidth reservations, the bandwidth is shared by set of transported PSCs

L-LSP

Label-only-inferred-PSC

•PHB is determined from Label or from label and EXP/CLP bits

•PHB or PSC is signaled at LSP setup •Label-PHB mapping is signaled.

•EXP/CLP-PHB mapping is well known •Shim or link layer header may be used •One PHB per LSP except for AF and PSC per LSP for AF

(8)

Mapping Traffic to LSPs

Incoming Packets Ingress Node With both Diffserv and MPLS enable Premium Traffic High Priority Traffic Best Effort Traffic LSP 1 LSP 2 LSP 3 Problem:

Again the delay and jitter is

possible as all the premium traffic is following the same physical path.

• We can solve the above mentioned problem by splitting the traffic into different LSPs, even the destination is the same.

• We can allocate certain Bandwidth for each service class in a single LSP.

• A network may have multiple classes of traffic.

• For a same destination, there might be different classes. • Now, we can map different

(9)

Methodology

• Calculation of:

– Bandwidth Utilization per traffic flow

– Throughput

– Dropped packets

– Mean End-to-End Delay

1000

8

?

?

?

t

bits

P

N

r s ? ? ? t P N s

r Number of packets received at

destination router in bytes Packet size Time in second where;

1000

)

(

8

?

?

?

?

start stop s r

T

T

bits

P

N

? ? stop start T T where;

Start time of each traffic flow in second Stop time of each traffic flow in second

%

100

?

?

g r g

N

N

N

where; ? ? r g N

N Number of packets generated at source

Number of packets received at source

r N i i

N

D

?

?1 where;

End-to-End delay of packet ‘i’=

Time of packet ‘i’en-queue at source router Time of packet ‘i’receive at destination

(10)

Application Scenario

• DiffServ + MPLS

Incoming Packets

Ingress Node

With both DiffServ and MPLS enable

Premium Traffic

High Priority Traffic

Best Effort Traffic

LSP 1

LSP 2

(11)

Network Topology: (Simple)

For Simple Network

? Traffic sources are CBR sources on UDP agents.

? All packets follows the same smallest path e1-c1-e2 for simple case.

? For each case we will keep constant all the above 3 sources and will vary only last source from 500kbps to 5000kbps.

? Other constant rates are:

? Rate1: 1.9 Mbps (Real Time 1---RT1)

? Rate2: 1.1 Mbps (Real Time 2---RT2)

? Rate3: 1.0 Mbps (High Priority Best Effort---HPBE)

? Rate4: 500kbps? 5Mbps (Simple Best Effort— SBE) ? Simulation time is 30.0 seconds

2Mbit/s 5 msec c5 c4 e2 c1 e1 c2 c3 SRC 1 SRC 2 SRC 3 SRC 4 DEST 1 DEST 2 DEST 3 DEST 4 Domain 2Mbit/s 2Mbit/s 2Mbit/s 2Mbit/s 5Mbit/s 5Mbit/s 3Mbit/s 3Mbit/s 3Mbit/s 5 msec 5 msec 5 msec 5 msec 5 msec 5 msec 5 msec 5 msec 5 msec

Overall Packet Loss in %age

-10 0 10 20 30 40 50 0 1 2 3 4 5 6 rate 4 in Mbps

%age Packet Loss

Average End to End Delay

0 0.005 0.01 0.015 0.02 0.025 0 1 2 3 4 5 6 rate4 in Mbps delay in msec

Overall Link Utilization of Network

(12)

Average End to End Delay 0 0.005 0.01 0.015 0.02 0 1 2 3 4 5 6 rate4 in Mbps delay in msec

Overall Packet Loss in %age

-10 0 10 20 30 40 50 0 1 2 3 4 5 6 rate 4 in Mbps

%age Packet Loss

Overall Link Utilization of Network

0 5 10 15 20 25 0 2 4 6 rate4 in Mbps Link Utilization in %age

Network Topology: (DiffServ)

For Diffserv Network

?? Traffic sources are CBR sources on UDP agents

?? For each case we will keep constant all the above 3 sources and will vary only last source from 500kbps to 5000kbps.

?? Other constant rates are:

?? Rate1: 1.9 Mbps (Real Time 1---RT1)

?? Rate2: 1.1 Mbps (Real Time 2---RT2)

?? Rate3: 1.0 Mbps (High Priority Best Effort---HPBE)

?? Rate4: 500kbps? 5Mbps (Simple Best Effort— SBE) ??Simulation time is 30.0 seconds

(13)

Overall Packet Loss in %age -1 0 1 2 3 4 0 1 2 3 4 5 6 rate 4 in Mbps

%age Packet Loss

Average End to End Delay

0 0.005 0.01 0.015 0.02 0 1 2 3 4 5 6 rate4 in Mbps delay in msec

Overall Link Utilization of Network

0 20 40 60 80 0 5 10 15 rate4 in Mbps Link Utilization in %age Network Topology: (MPLS) For MPLS Network

?? If no ER-LSP is defined, all packets follow the same smallest path LSR4-LSR5-LSR6. In our case, we establish ER-LSP as soon as simulation starts.

?? Traffic sources are CBR sources on UDP agents

?? For each case we will keep constant all the above 3 sources and will vary only last source from 500kbps to 5000kbps.

?? Other constant rates are:

?? Rate1: 1.9 Mbps (Real Time 1---RT1) ?? Rate2: 1.1 Mbps (Real Time 2---RT2)

?? Rate3: 1.0 Mbps (High Priority Best Effort---HPBE) ?? Rate4: 500kbps? 5Mbps (Simple Best Effort— SBE) ??Simulation time is 30.0 sec

(14)

Conclusions

From our “Dumbbell” network topology,

• The overall performance (packet Loss, End-to-End elay, Link

utilization) of DiffServ is quite similar to the Simple scheme, but

MPLS is superior than DiffServ.

• In Simple case, there is no mechanism to classify the packets, so

packets are randomly dropped from all 4 sources.

• In DiffServ, the low priority packets (Best effort packets) are

discarded. Since RED queue has been used, some early dropping of

high priority traffic can also be predicted in the network.

(15)

References

Related documents

*The search included the National Institutes of Health clinical trial registry and the fourteen registries included in the World Health Organisation trials registry

For the typology of land uses we applied the CORINE land cover classification (European Environmental Agency 2000). CORINE includes all the major land cover types in Europe and

The PPA was implemented in the MPLS network to support DiffServ-aware traffic engineering and all the LSPs are established by using RSVP-TE signaling from ingress router to

Using the MPLS Diff-Serv model, an MPLS service provider can offer differentiated services to customers sending IP traffic or MPLS traffic. DiffServ Aware

• MPLS QoS uses Differentiated Services (DiffServ) architecture defined for IP QoS (RFC 2475). • MPLS DiffServ is defined

Furthermore, when an MPLS network supports DiffServ, traffic flows can receive class- based admission, differentiated queue servicing in the network nodes, preemption priority,

This study is the first to distinguish the differences between prokaryotic microbial communities associated with sinking and suspended marine particles – as opposed to all

19 DELA CRUZ MARIZ SABACAN NUEVA ECIJA UNIVERSITY OF SCIENCE & TECHNOLOGY-CABANATUAN). 20 DELA CRUZ MARK JAYSON BAUTISTA