An approach to service provisioning with quality of service requirements in ATM networks

  • Authors:
  • Panagiotis Thomas;Demosthenis Teneketzis

  • Affiliations:
  • (Correspd.) Department of Electrical Engineering and Computer Science, University of Michigan, Ann Arbor, MI 48109-2122, USA Tel.&colon/ +1313 764 7568&semi/ E-mail&colon/ grthomas@umich.edu;Department of Electrical Engineering and Computer Science, University of Michigan, Ann Arbor, MI 48109-2122, USA E-mail&colon/ teneket@umich.edu

  • Venue:
  • Journal of High Speed Networks
  • Year:
  • 1997

Quantified Score

Hi-index 0.01

Visualization

Abstract

We present an approach to Service Provisioning with Quality ofService (QoS) requirements in ATM networks. The ATM networkprovides services to users every \widehat{T} units of time. Eachservice is characterized by its one way route, its input trafficconstraints and its provided QoS. The input traffic constraintsconsist of the maximum input rate and an upper bound on theburstiness curve. The QoS provided is defined by the maximumpercentage of cell loss along the route and the maximum end-to-endcell delay. The service provisioning problem is defined asfollows: determine the amount, price and requiredresources (bandwidth and buffers) for each type of service, thatmaximize a social welfare function that consists of the networksrevenue and the users surplus. This problem is solved every\widehat{T} units of time and the allocation is made only over theavailable resources, that is, those that are not used byconnections that are still active. We prove the existence of asolution to the Service Provisioning Problem and we also suggest aniterative procedure that interprets the solution. The networkadjusts the prices to maximize the welfare function and also toguarantee that the allocated resources do not exceed the availableresources. Based on these prices, users request a new allocationthat minimizes their cost and the network adjusts again the pricesbased on the new allocation. The above procedure has the followingfeatures: (i) the network needs to know only the average requestrate for each type of service, their route and the resourcesrequested by the users; (ii) users need to know only their privateinformation (input traffic constraints and QoS requirements), theirroute, and the prices for resources announced by the network.