Share Email Print
cover

Proceedings Paper

Improvement of CBQ for bandwidth reclamation of RPR
Author(s): Benxiong Huang; Xiaoling Wang; Ming Xu; Lili Shi
Format Member Price Non-Member Price
PDF $17.00 $21.00

Paper Abstract

The Resilient Packet Ring (RPR) IEEE 802.17 standard is under development as a new high-speed backbone technology for metropolitan area networks (MAN) [1]. Bandwidth reclamation has been concerned in RPR specifications from draft 0.1 to draft 2.4. According to specifications, allocated bandwidth can be reused, or reclaimed, by a lower priority service class whenever the reclamation does not effect the service guarantees of any equal or higher priority classes on the local station or on any other station on the ring [2]. The class-based queuing (CBQ) algorithm is proposed to implement link-sharing [3]. A hierarchical link-sharing structure can be used to specify guidelines for the distribution of 'excess’ bandwidth [4] and it can rate-limit all classes to their allocated bandwidth. There is some sameness between the link-sharing of CBQ and bandwidth reclamation of RPR. The CBQ is a mature technology while RPR is a new technology. Given CBQ improvement and full use so as to make its thought suitable for bandwidth reclamation of RPR is the focus of our work. In this paper, we present the solution that can solve the reclamation problem, which proves to be effective by simulation.

Paper Details

Date Published: 15 April 2004
PDF: 8 pages
Proc. SPIE 5282, Network Architectures, Management, and Applications, (15 April 2004); doi: 10.1117/12.523872
Show Author Affiliations
Benxiong Huang, Huazhong Univ. of Science and Technology (China)
Xiaoling Wang, Huazhong Univ. of Science and Technology (China)
Ming Xu, Huazhong Univ. of Science and Technology (China)
Lili Shi, Huazhong Univ. of Science and Technology (China)


Published in SPIE Proceedings Vol. 5282:
Network Architectures, Management, and Applications
S. J. Ben Yoo; Kwok-wai Cheung; Yun-Chur Chung; Guangcheng Li, Editor(s)

© SPIE. Terms of Use
Back to Top