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 ...
i) at least Mrm in-rate cells have been sent and at least Trm time has elapsed, or ii) Nrm -1 in-rate cells have been sent. b) The next in-rate cell shall be a backward RM-cell if condition (a) above is not met, if a backward RM cell is waiting for transmission, and if either: i) no in-rate backward RM-cell has been sent since the last in-rate forward RM-cell, or ii) no data cell is waiting for transmission. c) The next in-rate cell sent shall be a data cell if neither condition (a) nor condition (b) is met, and if a data cell is waiting for transmission. 4. Cells sent in accordance with source behaviors #1,#2, and #3 shall have CLP=0. 5. Before sending a forward in-rate RM cell, if ACR > ICR and the time T that has elapsed since the last in-rate forward RM-cell was sent is greater than ADTF, then ACR shall be reduced to ICR. 6. Before sending an in-rate forward RM cell, and following behavior #5 above, if at least CRM in-rate forward RM-cells have been sent since the last backward RM-cell with BN=0 was received, then ACR shall be reduced by at least ACR CDF, unless that reduction would result in a rate below MCR, in which case ACR shall be set to MCR. 381
7. After following behaviors #5 and #6 above, the ACR value shall be placed in the CCR eld of the outgoing forward RM-cell, but only in-rate cells sent after the outgoing forward RM-cell need to follow the new rate. 8. When a backward RM-cell (in-rate or out-of-rate) is received with CI=1, then ACR shall be reduced by at least ACR RDF, unless that reduction would result in a rate below MCR, in which case ACR shall be set to MCR. If the backward RM-cell has both CI=0 and NI=0, then the ACR may be increased by no more than RIF PCR, to a rate not greater than PCR. If the backward RM-cell has NI=1, the ACR shall not be increased. 9. When a backward RM-cell (in-rate or out-of-rate) is received, and after ACR is adjusted according to source behavior #8, ACR is set to at most the minimum of ACR as computed in source behavior #8, and the ER eld, but no lower than MCR. 10. When generating a forward RM-cell, the source shall assign values to the various RM-cell elds as speci ed for source-generated cells in Table 5-4. 11. Forward RM-cells may be sent out-of-rate (i.e., not conforming to the current ACR). Out-of-rate forward RM-cells shall not be sent at a rate greater than TCR. 12. A source shall reset EFCI on every data cell it sends. 13. The source may implement a use-it-or-lose-it policy to reduce its ACR to a value which approximated the actual cell transmission rate. Use-it-or-lose-it policies are discussed in Appendix I.8. 382
- 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
- Page 385 and 386: sources in chapter 6. We expect the
- Page 387 and 388: con guration mentioned in the table
- Page 389 and 390: can be very di erent for di erent V
- Page 391 and 392: CHAPTER 10 IMPLEMENTATION ISSUES At
- Page 393 and 394: With an enhanced UBR service, appli
- Page 395 and 396: 2. Some switch schemes have a proce
- Page 397 and 398: 4. Large legacy switches have a pro
- Page 399 and 400: section 9. Further, WAN switches wo
- Page 401 and 402: CHAPTER 11 SUMMARY AND FUTURE WORK
- Page 403 and 404: good transient performance. Since r
- Page 405 and 406: variant background tra c conditions
- Page 407: APPENDIX A SOURCE, DESTINATION AND
- Page 411 and 412: set the QL and SN elds to zero, pre
- Page 413 and 414: d) VS/VD Control: The switch may se
- Page 415 and 416: 5. Setting of other parameters at V
- Page 417 and 418: 4. The averaging interval timer exp
- Page 419 and 420: 1. Initialization: Target Cell Rate
- Page 421 and 422: THEN IF (OCR In Cell Fair Share Rat
- Page 423 and 424: APPENDIX C ERICA SWITCH ALGORITHM:
- Page 425 and 426: Number Active VCs In Last Interval
- Page 427 and 428: IF (NOT(Averaging VCs Option)) THEN
- Page 429 and 430: IF (Load Factor = In nity) THEN Loa
- Page 431 and 432: ; (Contribution[VC] = Decay Factor)
- Page 433 and 434: Name Explanation Flow Chart (FC) or
- Page 435 and 436: Figure C.2: Flow Chart for Achievin
- Page 437 and 438: Figure C.4: Flow Chart of averaging
- Page 439 and 440: Figure C.6: Flow chart of averaging
- Page 441 and 442: C.3 Pseudocode for VS/VD Design Opt
- Page 443 and 444: (* | Bottleneck rate of next loop |
- Page 445 and 446: Follow SESRules 1-4 (see appendix A
- Page 447 and 448: CRM - Missing RM-cell Count DIR bit
- Page 449 and 450: TUB -Target Utilization Band Trm -
- Page 451 and 452: [12] J. Bennett and G. Tom Des Jard
- Page 453 and 454: [38] M. Grossglauser, S.Keshav, and
- Page 455 and 456: [64] H. T. Kung. Flow Controlled Vi
7. After follow<strong>in</strong>g behaviors #5 and #6 above, <strong>the</strong> ACR value shall be placed <strong>in</strong><br />
<strong>the</strong> CCR eld of <strong>the</strong> outgo<strong>in</strong>g <strong>for</strong>ward RM-cell, but only <strong>in</strong>-rate cells sent after<br />
<strong>the</strong> outgo<strong>in</strong>g <strong>for</strong>ward RM-cell need to follow <strong>the</strong> new rate.<br />
8. When a backward RM-cell (<strong>in</strong>-rate or out-of-rate) is received with CI=1, <strong>the</strong>n<br />
ACR shall be reduced by at least ACR RDF, unless that reduction would<br />
result <strong>in</strong> a rate below MCR, <strong>in</strong> which case ACR shall be set to MCR. If <strong>the</strong><br />
backward RM-cell has both CI=0 and NI=0, <strong>the</strong>n <strong>the</strong> ACR may be <strong>in</strong>creased<br />
by no more than RIF PCR, to a rate not greater than PCR. If <strong>the</strong> backward<br />
RM-cell has NI=1, <strong>the</strong> ACR shall not be <strong>in</strong>creased.<br />
9. When a backward RM-cell (<strong>in</strong>-rate or out-of-rate) is received, and after ACR is<br />
adjusted accord<strong>in</strong>g to source behavior #8, ACR is set to at most <strong>the</strong> m<strong>in</strong>imum<br />
of ACR as computed <strong>in</strong> source behavior #8, and <strong>the</strong> ER eld, but no lower<br />
than MCR.<br />
10. When generat<strong>in</strong>g a <strong>for</strong>ward RM-cell, <strong>the</strong> source shall assign values to <strong>the</strong> various<br />
RM-cell elds as speci ed <strong>for</strong> source-generated cells <strong>in</strong> Table 5-4.<br />
11. Forward RM-cells may be sent out-of-rate (i.e., not con<strong>for</strong>m<strong>in</strong>g to <strong>the</strong> current<br />
ACR). Out-of-rate <strong>for</strong>ward RM-cells shall not be sent at a rate greater than<br />
TCR.<br />
12. A source shall reset EFCI on every data cell it sends.<br />
13. The source may implement a use-it-or-lose-it policy to reduce its ACR to a value<br />
which approximated <strong>the</strong> actual cell transmission rate. Use-it-or-lose-it policies<br />
are discussed <strong>in</strong> Appendix I.8.<br />
382