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 ...
# Feedback RTT Duty Period (p) Max Switch Delay(ms) (ms) Cycle (d) (ms) Q (cells) 1. 1ms 3 ms 0.8 10 ms 4176 (0.4 RTT) 2. 5ms 15 ms 0.8 10 ms DIVERGES 3. 10 ms 30 ms 0.8 10 ms DIVERGES Table 8.8: E ect of Feedback Delay with VBR delay. Hence, in any VBR OFF time, the switch cannot allocate high rates to sources long enough to cause queue backlogs. The new load is quickly felt at the switch and feedback is given to the sources. Rows 2 and 3 in Table 8.8 have a feedback delay longer than the OFF time. This is one of the factors causing the divergence in the queues of these rows. E ect of Switch Scheme with VBR The TCP tra c makes the ABR demand variable. The VBR background makes the ABR capacity variable. In the presence of TCP and VBR, the measurements used by switchschemes are a ected by thevariation. The errors in the metrics are re ected in the feedback. The errors in the feedback result in queues. Switch schemes need to be robust to perform under such error-prone conditions. Another e ect of errors is that the boundary conditions of the scheme are encountered often. The scheme must be designed to handle such conditions gracefully. We study the robustness issues in ERICA and make adjustments needed to reduce the e ect of the variation. As an example, consider the case when the VBR ON-OFF periods are very small (1 ms ON, 1 ms OFF). The resulting variation can be controlled by aswitch scheme 307
like ERICA+ which uses the queueing delay to calculate feedback (in addition to input rate etc). The basic ERICA algorithm without queue control cannot handle this level of variation. The ERICA+ algorithm uses the queue length as a secondary metric to reduce the high allocation of rates. However, ERICA+ has a limit on how much it can reduce the allocation. Given su cient variation, the limit can be reached. This means that even the minimum rate allocation by ERICA+ causes the queues to diverge. This reason, along with the discussion on ON-OFF times and feedback delays explains the divergent cases in Tables 8.7 and 8.8. Reducing the E ects of Variation In ERICA+ We tackle these problems by reducing the e ect of variation on the scheme mea- surements in three ways (described in detail in chapter 6): 1. First, we observethatoneway to reduce variation in measurements is to measure quantities over longer intervals. Longer intervals yield averages which have less variance. However, making the intervals too long increases the response time, and queues may build up in the interim. 2. Second, we average the measurements over several successive intervals. The ERICA scheme uses two important measurements: the overload factor (z)which is the ratio of the input rate and the target ABR rate, and the numberofactive sources (Na). We re-examine how the scheme depends on these metrics and design an appropriate averaging technique for each of them. The overload factor (z) is used to divide the current cell rate of the source to give what we call the \VC share". The VC share is one of the rates 308
- Page 283 and 284: CHAPTER 8 SUPPORTING INTERNET APPLI
- Page 285 and 286: u ering which does not depend upon
- Page 287 and 288: 4 make it to the destination are ar
- Page 289 and 290: Figure 8.3: At the ATM layer, the T
- Page 291 and 292: issues and e ect of bursty applicat
- Page 293 and 294: from the loss and they trigger the
- Page 295 and 296: 8.8 Performance Metrics We measure
- Page 297 and 298: the performance is fair. Also, the
- Page 299 and 300: Figure 8.7(b) shows the rates (ACRs
- Page 301 and 302: Window Size in bytes vfive-tcp/opti
- Page 303 and 304: The e ect of large bu ers on CLR is
- Page 305 and 306: 8.13 Summary of TCP/IP performance
- Page 307 and 308: Feedback delay: Twice the delay fro
- Page 309 and 310: on a link, two cells are expected a
- Page 311 and 312: state only after the switch algorit
- Page 313 and 314: queue length is less susceptible to
- Page 315 and 316: to equalize rates for fairness, and
- Page 317 and 318: QB = Link bandwidth (RT T ; T ) and
- Page 319 and 320: u ered at the end-system, and not i
- Page 321 and 322: Part b): When ABR load goes away, t
- Page 323 and 324: All our simulations presented use t
- Page 325 and 326: Averaging RTT(ms) Feedback Max Q Th
- Page 327 and 328: a modi ed version of the ERICA algo
- Page 329 and 330: ABR is better than UBR in these (en
- Page 331 and 332: problems. During the ON time, the V
- Page 333: hand, the frequency of the VBR is h
- Page 337 and 338: minimum fairshare is low. This may
- Page 339 and 340: 8.17 E ect of Long-Range Dependent
- Page 341 and 342: terminology) are called \Presentati
- Page 343 and 344: The key point is that the MPEG-2 ra
- Page 345 and 346: the MPEG-2 Transport Stream, and st
- Page 347 and 348: 8.17.4 Observations on the Long-Ran
- Page 349 and 350: For the video sources, we choose me
- Page 351 and 352: Video Sources ABR Metrics # Mean St
- Page 353 and 354: However, with modi cations to ERICA
- Page 355 and 356: Video Sources ABR Metrics # Avg Src
- Page 357 and 358: Video Sources ABR Metrics # Avg Src
- Page 359 and 360: On the other hand, if the applicati
- Page 361 and 362: of managing bu ers, queueing, sched
- Page 363 and 364: hence control the total load on the
- Page 365 and 366: call such a switch a \VS/VD switch"
- Page 367 and 368: Figure 9.2: Per-class queues in a n
- Page 369 and 370: which arises is where the rate calc
- Page 371 and 372: 9.2 The ERICA Switch Scheme: Renota
- Page 373 and 374: The unknowns in the above equations
- Page 375 and 376: Figure 9.9: Two methods to measure
- Page 377 and 378: 9.4 VS/VD Switch Design Options 9.4
- Page 379 and 380: # VC Rate VC Input Rate Input Rate
- Page 381 and 382: 8 uses source rate measurement, we
- Page 383 and 384: The allocated rate update and the e
# Feedback RTT Duty Period (p) Max Switch<br />
Delay(ms) (ms) Cycle (d) (ms) Q (cells)<br />
1. 1ms 3 ms 0.8 10 ms 4176 (0.4 RTT)<br />
2. 5ms 15 ms 0.8 10 ms DIVERGES<br />
3. 10 ms 30 ms 0.8 10 ms DIVERGES<br />
Table 8.8: E ect of Feedback Delay with VBR<br />
delay. Hence, <strong>in</strong> any VBR OFF time, <strong>the</strong> switch cannot allocate high rates to sources<br />
long enough to cause queue backlogs. The new load is quickly felt at <strong>the</strong> switch and<br />
feedback is given to <strong>the</strong> sources.<br />
Rows 2 and 3 <strong>in</strong> Table 8.8 have a feedback delay longer than <strong>the</strong> OFF time. This<br />
is one of <strong>the</strong> factors caus<strong>in</strong>g <strong>the</strong> divergence <strong>in</strong> <strong>the</strong> queues of <strong>the</strong>se rows.<br />
E ect of Switch Scheme with VBR<br />
The TCP tra c makes <strong>the</strong> <strong>ABR</strong> demand variable. The VBR background makes<br />
<strong>the</strong> <strong>ABR</strong> capacity variable. In <strong>the</strong> presence of TCP and VBR, <strong>the</strong> measurements used<br />
by switchschemes are a ected by <strong>the</strong>variation. The errors <strong>in</strong> <strong>the</strong> metrics are re ected<br />
<strong>in</strong> <strong>the</strong> feedback. The errors <strong>in</strong> <strong>the</strong> feedback result <strong>in</strong> queues. Switch schemes need to<br />
be robust to per<strong>for</strong>m under such error-prone conditions. Ano<strong>the</strong>r e ect of errors is<br />
that <strong>the</strong> boundary conditions of <strong>the</strong> scheme are encountered often. The scheme must<br />
be designed to handle such conditions gracefully. We study <strong>the</strong> robustness issues <strong>in</strong><br />
ERICA and make adjustments needed to reduce <strong>the</strong> e ect of <strong>the</strong> variation.<br />
As an example, consider <strong>the</strong> case when <strong>the</strong> VBR ON-OFF periods are very small<br />
(1 ms ON, 1 ms OFF). The result<strong>in</strong>g variation can be controlled by aswitch scheme<br />
307