Fair and Stable Resource Allocation Methods for Guaranteed Service

Kazumasa OIDA

Fair and Stable Resource Allocation Methods for Guaranteed Service

Kazumasa OIDA

Full Text Views

0

Cite this

Summary :

This paper deals with deadlock and fairness issues that may arise when network users request resources for guaranteed service with the resource reservation protocol (RSVP). A deadlock occurs when a request can only be satisfied if the resources reserved for another request are released, but the reserved resources are never released. The fairness issue occurs when some reservation requests may be satisfied but only after a very long wait. Our approach to these issues is based on our belief that a network should provide stable throughput and fairness whatever the behavior of the user. Our methods are unique in two respects. First, during the session setup phase, a node directly connected to the requesting users terminates the users' behavior and makes reservations fairly and efficiently in place of the users. Second, our three admission control methods allocate resources for each reservation request by considering not only the current residual bandwidth but also the properties of the requesting session; e.g., its weight (the number of resources it requires) or its age (how long it has been waiting for session setup). Our methods do not maximize the throughput since they always keep a certain amount of resources unreserved for fairness. From simulation results, however, they do provide quite fair behavior, and their throughput is stable regardless of the network size and the session holding time.

Publication: IEICE TRANSACTIONS on Communications Vol.E84-B No.1 pp.71-80

Publication Date: 2001/01/01

Publicized

Online ISSN

DOI

Type of Manuscript: PAPER

Category: Internet

Cite this

Copy

Kazumasa OIDA, "Fair and Stable Resource Allocation Methods for Guaranteed Service" in IEICE TRANSACTIONS on Communications, vol. E84-B, no. 1, pp. 71-80, January 2001, doi: .
Abstract: This paper deals with deadlock and fairness issues that may arise when network users request resources for guaranteed service with the resource reservation protocol (RSVP). A deadlock occurs when a request can only be satisfied if the resources reserved for another request are released, but the reserved resources are never released. The fairness issue occurs when some reservation requests may be satisfied but only after a very long wait. Our approach to these issues is based on our belief that a network should provide stable throughput and fairness whatever the behavior of the user. Our methods are unique in two respects. First, during the session setup phase, a node directly connected to the requesting users terminates the users' behavior and makes reservations fairly and efficiently in place of the users. Second, our three admission control methods allocate resources for each reservation request by considering not only the current residual bandwidth but also the properties of the requesting session; e.g., its weight (the number of resources it requires) or its age (how long it has been waiting for session setup). Our methods do not maximize the throughput since they always keep a certain amount of resources unreserved for fairness. From simulation results, however, they do provide quite fair behavior, and their throughput is stable regardless of the network size and the session holding time.
URL: https://global.ieice.org/en_transactions/communications/10.1587/e84-b_1_71/_p

Copy

@ARTICLE{e84-b_1_71,
author={Kazumasa OIDA, },
journal={IEICE TRANSACTIONS on Communications},
title={Fair and Stable Resource Allocation Methods for Guaranteed Service},
year={2001},
volume={E84-B},
number={1},
pages={71-80},
abstract={This paper deals with deadlock and fairness issues that may arise when network users request resources for guaranteed service with the resource reservation protocol (RSVP). A deadlock occurs when a request can only be satisfied if the resources reserved for another request are released, but the reserved resources are never released. The fairness issue occurs when some reservation requests may be satisfied but only after a very long wait. Our approach to these issues is based on our belief that a network should provide stable throughput and fairness whatever the behavior of the user. Our methods are unique in two respects. First, during the session setup phase, a node directly connected to the requesting users terminates the users' behavior and makes reservations fairly and efficiently in place of the users. Second, our three admission control methods allocate resources for each reservation request by considering not only the current residual bandwidth but also the properties of the requesting session; e.g., its weight (the number of resources it requires) or its age (how long it has been waiting for session setup). Our methods do not maximize the throughput since they always keep a certain amount of resources unreserved for fairness. From simulation results, however, they do provide quite fair behavior, and their throughput is stable regardless of the network size and the session holding time.},
keywords={},
doi={},
ISSN={},
month={January},}

Copy

TY - JOUR
TI - Fair and Stable Resource Allocation Methods for Guaranteed Service
T2 - IEICE TRANSACTIONS on Communications
SP - 71
EP - 80
AU - Kazumasa OIDA
PY - 2001
DO -
JO - IEICE TRANSACTIONS on Communications
SN -
VL - E84-B
IS - 1
JA - IEICE TRANSACTIONS on Communications
Y1 - January 2001
AB - This paper deals with deadlock and fairness issues that may arise when network users request resources for guaranteed service with the resource reservation protocol (RSVP). A deadlock occurs when a request can only be satisfied if the resources reserved for another request are released, but the reserved resources are never released. The fairness issue occurs when some reservation requests may be satisfied but only after a very long wait. Our approach to these issues is based on our belief that a network should provide stable throughput and fairness whatever the behavior of the user. Our methods are unique in two respects. First, during the session setup phase, a node directly connected to the requesting users terminates the users' behavior and makes reservations fairly and efficiently in place of the users. Second, our three admission control methods allocate resources for each reservation request by considering not only the current residual bandwidth but also the properties of the requesting session; e.g., its weight (the number of resources it requires) or its age (how long it has been waiting for session setup). Our methods do not maximize the throughput since they always keep a certain amount of resources unreserved for fairness. From simulation results, however, they do provide quite fair behavior, and their throughput is stable regardless of the network size and the session holding time.
ER -