24.11.2012 Views

Traffic Management for the Available Bit Rate (ABR) Service in ...

Traffic Management for the Available Bit Rate (ABR) Service in ...

Traffic Management for the Available Bit Rate (ABR) Service in ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

We observe that <strong>the</strong>re is a drastic reduction of TCP throughput which is not<br />

proportional to <strong>the</strong> <strong>in</strong>crease <strong>in</strong> CLR. The throughput drops by 36% while <strong>the</strong> CLR<br />

is only 0.18%.<br />

Figure 8.7 shows graphs of w<strong>in</strong>dow size, sequence numbers, and ACR <strong>for</strong> <strong>the</strong><br />

two sources. Figure 8.7(a) shows that <strong>the</strong>re is one loss around t=200 ms. No acks<br />

are received <strong>for</strong> <strong>the</strong> next 300 ms and <strong>the</strong>re<strong>for</strong>e, <strong>the</strong> w<strong>in</strong>dow rema<strong>in</strong>s constant and<br />

nally drops to 1 at t=500 ms. The packets are retransmitted and w<strong>in</strong>dow rises ex-<br />

ponentially upto <strong>the</strong> half of <strong>the</strong> value be<strong>for</strong>e <strong>the</strong> drop. Subsequently, <strong>the</strong> w<strong>in</strong>dow rise<br />

l<strong>in</strong>early. Note that <strong>the</strong> l<strong>in</strong>ear rise is very slow. The source w<strong>in</strong>dow is much below its<br />

maximum. In o<strong>the</strong>r words, <strong>the</strong> sources are w<strong>in</strong>dow limited. The congestion w<strong>in</strong>dows<br />

of both sources are approximately equal, and so <strong>the</strong> operation is fair. However, <strong>the</strong><br />

throughput <strong>in</strong> this experiment is only 64% of <strong>the</strong> maximum throughput. The mea-<br />

sured cell loss ratio <strong>in</strong> this case was only 0.18%. Note that <strong>the</strong> CLR and throughput<br />

loss are one order of magnitude apart.<br />

W<strong>in</strong>dow Size <strong>in</strong> bytes<br />

two-tcp/option=1/optionb=295/optiont=6/sw_qsize=2048/tbe=512/granularity=100/wnd_scale_factor=4/epd_thresh=2045/icr=10.0/air=1/xdf=0.5/tdf=0/headroom=1.0<br />

t_threshold=900000.0/maxsrcrate=10.0/ontime=100000/offtime=100000/vbrrate=124.41/t0v=120/a=1.15/b=1.05/qlt=0.8/time_<strong>in</strong>t=1000.0/sw_<strong>in</strong>t=100/dist=1000 / Date:02/03/96<br />

300000<br />

250000<br />

200000<br />

150000<br />

100000<br />

50000<br />

ICR: 10.00 10.00 10.00 10.00 / XRM: 16.00 16.00 16.00 16.00 / Graph: 1<br />

Two TCP : Cwnds<br />

Cwnd Size <strong>for</strong> S1<br />

Cwnd Size <strong>for</strong> S2<br />

0<br />

0 500 1000 1500 2000 2500 3000 3500 4000 4500 5000<br />

Time <strong>in</strong> milliseconds<br />

(a) Congestion W<strong>in</strong>dow<br />

<strong>Rate</strong>s<br />

two-tcp/option=1/optionb=295/optiont=6/sw_qsize=2048/tbe=512/granularity=100/wnd_scale_factor=4/epd_thresh=2045/icr=10.0/air=1/xdf=0.5/tdf=0/headroom=1.0<br />

t_threshold=900000.0/maxsrcrate=10.0/ontime=100000/offtime=100000/vbrrate=124.41/t0v=120/a=1.15/b=1.05/qlt=0.8/time_<strong>in</strong>t=1000.0/sw_<strong>in</strong>t=100/dist=1000 / Date:02/03/96<br />

180<br />

160<br />

140<br />

120<br />

100<br />

80<br />

60<br />

40<br />

20<br />

ICR: 10.00 10.00 10.00 10.00 / XRM: 16.00 16.00 16.00 16.00 / Graph: 1<br />

Two TCP : ACRs<br />

ACR <strong>for</strong> S1<br />

ACR <strong>for</strong> S2<br />

0<br />

0 500 1000 1500 2000 2500 3000 3500 4000 4500 5000<br />

Time <strong>in</strong> milliseconds<br />

(b) ACR<br />

Figure 8.7: Two TCP Source Con guration, Bu er=2048 cells, TBE=512<br />

271

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!