Systems and Methods for Sharing of Resources

This invention relates to systems and methods for sharing limited resources among a number of users and/or classes of users.

Resources are often shared by a number of users. For example, telecommunication service providers have a certain limited number of resources that are critical to serve their customers' requests. A fair and efficient system for allocating the resources is desirable to prevent heavy users from degrading the performance of the system while allowing unused resources to be fully utilized.

The issue of guaranteeing a fair share of resources in a shared resource setting pervades our current business environment. It is widely recognized that sharing can in principle lead to economies of scale, and that non-simultaneity of demand (e.g., business vs. residential traffic) can be exploited. There is no integrated framework that guarantees users real time access to their contracted "slices" of a resource even in the face of unanticipated large demands from other customers. Protection can be achieved by complete partitioning of the resources. Such partitioning is effective in that users are protected from each other but is not efficient in that resources assigned to and not used by a particular user are wasted.

In a typical resource sharing situation, as exemplified by communications and computer networks, there is a need to address three major problems; namely, the problem of controlling the access to a system or subsystem, the problem of scheduling a particular processor, and the problem of allocating discrete resources.

To help visualize the problems and solutions, we will refer to an AT&T, Inc. 5ESS.RTM. switch. FIG. 1 depicts a 5ESS.RTM. subject to the demand of multi-class traffic, represented by streams a to z. Typically, a stream bundles the requests of a particular service, which can include, for example, call setups. For instance, a stream associated with wireless service may include handover requests, location updates, etc. A given activity places demands on a number of resources such as links, processors, data bases, trunks, etc.

The 5ESS.RTM. is engineered and provisioned so that it can provide a certain grade of service subject to a certain sustained traffic mix. Basic access control mechanisms could be implemented to guarantee that no class exceeds its contractual value. Such an approach would be effective, but hardly efficient. After all, access to a class that exceeds its allocated rate should not be denied when the system is operating below capacity because other classes are below their contractual rates. Traffic variability makes this a common occurrence. It is not unlikely for a class to exceed its contractual rate, and this does not necessarily happen when all classes are demanding their full share.

The second problem, i.e., the sharing of a processor, is local in nature. It may be necessary to control the sharing of a processor in addition to the global access control. For example, a particular processor may play a critical role as a global resource. Second, different classes tax various resources differently. By its very nature, a global access mechanism has to be based on estimates of the demand of each class of every resource. Moreover, a single class may contain in itself a number of activities. Therefore, the estimate assumes a certain mix of activities, but there is no guarantee that, once a class has obtained access, it will have such a mix.

Finally, we face the problem of sharing discrete resources. An example is the contention for trunks in the 5ESS.RTM..

U.S. Pat. No. 5,274,644 (the "'644 patent"; incorporated herein by reference) discloses several examples of methods for controlling access to a common resource, including a scheme that utilizes "tokens" to regulate access to the common resource. The '644 patent system includes a "throttle" associated with each user that regulates that user's access to the resource based on that user's access to tokens, as described below.

FIG. 2 depicts a rate control throttle for a single stream. The system can provide a desirable grade of service as long as key parameters of the traffic (arrival rate, peakedness) are kept within certain bounds. The rate control throttle guarantees that, in the long run, the admission rate in the system does not exceed a predetermined value, and shapes the traffic by limiting its peakedness. This predetermined value is used to establish a contractual admission rate "r.sub.i " for each user (i=1 to N, N being the total number of users), and a peakedness related factor "L.sub.i ". The mechanism consists of a bank B.sub.i for each user, of finite capacity L.sub.i, and a source (not shown) that generates tokens at a predetermined rate r.sub.i. The admission mechanism works as follows:

i) Tokens are generated at rate r.sub.i.

ii) A freshly generated token is deposited in bank B.sub.i if the number of tokens already in the bank is less that L.sub.i. Otherwise, the token is destroyed.

iii) An arrival from user i that finds a token in bank B.sub.i is admitted into service (and the token destroyed). Otherwise, the arrival is either rejected or queued.

As shown above, the rate control throttle is an effective mechanism that can be generalized to the case of N classes of users by providing a separate bank for each class. This system is effective, but is not completely efficient. When several classes contend for a given resource, it is likely that some of them will be operating below their contractual levels. The rate at which tokens are destroyed for finding a full bank is an indication of resource underutilization (provided of course that the provisioning of resources, and the assigning of token rates is sound).

One proposal to solve the problem of underutilization, described in the '644 patent, is to add an extra bank "B.sub.0 ", called the spare or overflow bank. As any regular bank, the overflow bank also has a limited capacity. The mechanism operates as follows (see FIG. 3):

i) Tokens corresponding to class i are generated at the contractual rate r.sub.i,

ii) A freshly generated class i token is deposited in bank B.sub.i, if the number of tokens already in B.sub.i is less than L.sub.i. Otherwise, the token is stored in the overflow bank B.sub.0. If the overflow bank happens to be full, the token is destroyed.

iii) A class i arrival that finds a token in bank B.sub.i is admitted into service (and the token destroyed). If no token is available in bank B.sub.i, but the overflow bank is not empty, the class i arrival is also admitted into service (and a token is destroyed in the overflow bank). Otherwise, the class i arrival is either rejected or queued.

An article authored by Berger and Whitt, entitled "A Multi-Class Input Regulation Throttle", (Proceedings Of The 29th IEEE Conference On Decision and Control, 1990, pp. 2106-2111), examines the case in which arrivals that are not admitted are lost from the system. This article discusses exact blocking and throughput for the case of two Poisson streams, and approximate models for N>2 classes. (This article is incorporated herein by reference.)

If arrivals that are not immediately admitted are queued and the number of classes exceeds two, access rules to the overflow bank by queued jobs need to be specified.

Yet another efficient multiclass admission control algorithm, homomorphic to the rate control throttle, is the leaky bucket mechanism, also described in the '644 patent. Instead of focusing on the availability of a certain amount of a material (e.g., a token) that flows in at a fixed rate, the leaky bucket mechanism considers the availability of space in a bucket that drains at a fixed rate.

In addition to N real buffers (queues Q.sub.1, Q.sub.2 . . . , Q.sub.N), the leaky bucket access mechanism consists of N+1 virtual buffers (leaky buckets LB.sub.0, LB.sub.1, . . . , LB.sub.N). Each class is assigned its own queue, and its own leaky bucket. While the size of the queues is infinite, the leaky buckets have finite capacity. We denote as L.sub.i the capacity of LB.sub.i, i=0, . . . N. The additional leaky bucket (LB.sub.0) is common to all classes. To be admitted into the system, a class i arrival has to deposit b.sub.i quanta of fluid in its own LB.sub.i or in the common LB.sub.0 if the former cannot contain the full quanta. Should the sum of the spare capacity in LB.sub.i and LB.sub.0 be less than b.sub.i the arrival waits in Q.sub.i. Fluid originated by class i traffic is continuously deposited in bucket LB.sub.i, and possibly in LB.sub.0, as space is made by the leaks as long as Q.sub.i is not empty. Access within a class is granted according to the FIFO (i.e., first in first out) discipline as soon as the required quanta for the head of the line arrival has been deposited. LB.sub.i, i.noteq.0 leaks at the contractual rate r.sub.i. When a bucket, say LB.sub.j, j.noteq.0 empties, its discharge capability at rate r.sub.j is immediately transferred to LB.sub.0. As soon as fluid is deposited in LB.sub.j the leak is returned to it. That is, LB.sub.0 does not have a leak of its own.

The disadvantages of the prior art have been overcome by the present invention which features an improved resource allocation system and method.

In one aspect, the invention features a method for allocating access to a shared limited resource among a plurality of users who require access to the resource, the allocation being made such that each user is granted access to the resource at a minimum guaranteed rate associated with each user and such that the resource is available for use by any user exceeding its minimum guaranteed rate only if the resource is available, the method comprising the steps of: assigning tokens to each user at a rate determined by the minimum guaranteed rate associated with each user; storing tokens assigned to each user in a bank associated with each user, each bank having a finite capacity associated with each user; storing tokens assigned to a user whose associated bank has reached its capacity in a bank assigned to another user whose bank is below its capacity; and allowing a user requesting access to the resource to have access to the resource if the user has a predetermined number of tokens in its associated bank and otherwise denying access to the resource.

In preferred embodiments, the users are assigned different priorities and selected based on the assigned priorities.

The method further comprises the step of deleting a predetermined number of tokens from a bank associated with a user that is granted access to the resource. The predetermined number of tokens can be one token. Each bank can either have the same predetermined finite capacity, or at least two of the banks can have different capacities.

In another aspect, the invention features a method for allocating access to a shared resource, comprising the steps of: (a) establishing an incrementable counter for each of a plurality of users of the resource, the incrementable counter having a count; (b) incrementing the count in each counter established for each user at a rate associated with each user if the count is below a predefined maximum count associated with each user; (c) permitting a user requesting access to the resource to have access if the count in the counter established for the user requesting access is non-zero; and (d) incrementing the count in a counter associated with a user whose counter is below the predefined maximum count at a rate higher than its associated rate if the count in any other counter incremented in step (b) is at its predefined maximum count.

In still another aspect, the invention features a method for sharing access to a common resource among N users, where N is an integer greater than 1, comprising the steps of: assigning a rate "R.sub.i " to each of the N users, the rate indicating the minimum desired access rate for the i.sup.th user, where 1.ltoreq.i.ltoreq.N; storing an indicia "B.sub.i " of the eligibility of the i.sup.th user to access the common resource for each of the N users; incrementing each B.sub.i at its associated rate R.sub.i up to a predetermined limit L.sub.i assigned to each of the N users; incrementing a selected B.sub.i at a rate greater than its associated R.sub.i in the event that any other B.sub.i is at its associated limit L.sub.i, and the selected B.sub.i is not at its limit L.sub.i ; and allowing the i.sup.th user to access the common resource if its associated B.sub.i is not zero. The method preferably further includes the step of decrementing B.sub.i upon the granting of access to the ith user of the resource.

FIG. 1 is a block diagram of an AT&T 5ESS.RTM. switch with multiple classes seeking access.

FIG. 2 is a diagram illustrating a prior art throttle control technique.

FIG. 3 is a block diagram illustrating a second prior art throttle control technique.

FIG. 4 is a block diagram illustrating a third prior art throttle control technique.

FIG. 5 is a block diagram illustrating an access control technique of the invention.

FIG. 6 is a block diagram illustrating a system according to the invention for controlling both access to a service among a number of segments and access to a resource among a number of services.

A first embodiment of the invention features a variant of the token and leaky bucket schemes discussed above, where certain classes are able to withdraw a token from the common bank B.sub.0 (or are allowed to deposit their quanta of fluid in LB.sub.0) first, and use their own banks (or buckets) only when the common bank (or bucket) is full. This scheme allows the system to give priority to certain classes and allow those classes to "save" their own access to the resources for future use if there are some overflow resources that can be utilized first.

In a second embodiment, the system can eliminate the overflow bank or bucket completely and, instead, redistribute the excess tokens generated by (or leak capacity of) users operating below their contacted capacity, to certain selected users. This scheme is explained next and, for ease of explanation, it is explained only in the context of the leaky bucket analogy.

Consider the scheme illustrated in FIG. 4, where the size of the common bucket LB.sub.0 is be made arbitrarily small, which means that the impact of the common bucket on the burstiness of the admitted stream is negligible. FIG. 4 captures a particular situation in which bucket LB.sub.2 is empty. Therefore, its drainage capability is currently exercised on the common bucket LB.sub.0. Also note that there are class 1 arrivals waiting in the real queue Q.sub.1. As shown in FIG. 4 this implies that there is no room in buckets LB.sub.0 and LB.sub.1 to deposit the needed quanta to allow access to the system for the Class 1 arrival (thus, the class 1 arrival is waiting on Q.sub.1).

Let the auxiliary variables Z.sub.n.sup.(i), i=1, 2 denote the sum of the workload in LB.sub.0, LB.sub.i, and Q.sub.i at arrival epoch n without counting the arrival. We will also denote Q.sub.i, LB.sub.i, and LB.sub.0 as the amount of work in the queue and the leaky buckets. In the particular state shown in FIG. 4 Z.sub.1 =LB.sub.0 +LB.sub.1 +Q.sub.1, and Z.sub.n.sup.(2) =LB.sub.0. An arrival has to wait in Q.sub.i until the deposit of b.sub.i quanta of fluid is completed, but fluid is leaked from buckets as long as Q.sub.i >0 and LB.sub.i +LB.sub.0 -L.sub.i -L.sub.0 <0. Also note LB.sub.i >0=>LB.sub.0 =L.sub.0. We use the index n to denote the epoch of the n.sup.th arrival to the system, .DELTA..sub.n+1 for the time between epochs n and n+1, and introduce the random variables ##EQU1##

No simultaneous arrivals are allowed i.e., a.sub.n.sup.(i) a.sub.n.sup.(2) =0. To describe the evolution of the system between arrival epochs we include the workload contributed by the previous arrival, and then account for the drainage during the interval .DELTA..sub.n+1.

Equations 1-4 highlight the impact of having the common bucket LB.sub.0. Consider the evolution of a particular bucket, say LB.sub.1. The negative term in equation 3 represents the contribution to the common drainage by LB.sub.2. The latter contributes to the common drainage when .DELTA..sub.n+1 r.sup.(2), its drainage capability during the interval, exceeds its own exclusive workload Z.sub.n+1.sup.(2) -L.sub.0. This common drainage capability is the distinctive feature of having L.sub.0. On the other hand, Z.sub.n+1.sup.(1) is somewhat impacted by a class 2 arrival, as shown by the third term on the right side of equation 3. However, as this term shows, that impact cannot exceed L.sub.0. Our interest is to find the cumulative distribution function (CDF) of the workload D.sub.n.sup.(i) in Q.sub.i, i=1,2 at arrival epoch n. Accordingly:

Equations 1 and 2 are coupled. That is, getting the CDF of Z.sub.n.sup.(i), i=1,2 requires finding the joint distribution of (Z.sub.n.sup.(1) Z.sub.n.sup.(2)). Note that the dimension of the state space is 2, rather than 3, as would be if we reversed the order in making deposits to the common bucket and the own bucket. This represents a substantial simplification in the numerical procedure to compute the CDF of D.sub.n.sup.(i), i=1,2.

Considerable insight into the access method can be gained by comparing it to a multiclass access without a common bucket. As noted above, such a scheme is effective in terms of protection, but lacks in efficiency. We now prove the point for the particular case of two classes. To this goal consider a separate access mechanism without a common bucket subject to the same arrivals as our original system, and use bars to differentiate its variables. In particular, equations 1 and 2 reduce to

and equation 5 translates into

Choose L.sub.i =L.sub.i, i=1,2, L.sub.0 =.epsilon., and write Z.sub.n.sup.(i) (.epsilon.) to emphasize the dependence of the workload on the size of the common bucket. Let ##EQU2## Set W.sub.0.sup.(i) =Z.sub.0.sup.(i), i=1,2. Then, for any integer n>0 the random variable W.sub.n.sup.(i) is

n stochastically smaller than Z.sub.n.sup.(i), i.e., Pr{W.sub.n.sup.(i) >x}.ltoreq.Pr{Z.sub.n.sup.(i) >x} for all x.gtoreq.0.

Note that as L.sub.0 .fwdarw.0 the contribution of the other class to the workload of class i (equations 3 and 4) reduces to zero. However, even for L.sub.0 32 0 the other class contributes to the drainage of Z.sub.n.sup.(i) (equations 3 and 4). Therefore, in the limit, the evolution of Z.sub.n.sup.(i) (.epsilon.) matches that of Z.sub.n.sup.(i) with the addition of a non positive term.

The following corollary shows that the multi-class access controller with a common bucket outperforms the classical access controller from the point of view of access delay.

Under the conditions described above the random variable D.sub.n.sup.(i) is stochastically smaller than D.sub.n.sup.(i), i.e., Pr{D.sub.n.sup.(i) >x}.ltoreq.Pr{D.sub.n.sup.(i) >x} for all x.gtoreq.0.

The inequality can be rewritten Pr{W.sub.n.sup.(i) >L.sub.i +x}.ltoreq.Pr{Z.sub.n.sup.(i) >L.sub.i +x}, which holds according to the above proposition.

As noted above, a variant to the classical leaky bucket mechanism was proposed where users probe the extra bucket LB.sub.0 first, and deposit fluid in their own bucket if Lb.sub.0 is full. The behavior of the proposed scheme was then compared to the standard multi-access approach. To make a consistent comparison, the size of the bucket LB.sub.0 was set to zero. The process of doing that illuminated that the mechanism to redistribute extra capacity relies primarily on the redistribution of the leak capability, not on the extra bucket LB.sub.0. Hence, the extra bucket is eliminated altogether, and the algorithm is modified in the following way: whenever bucket LB.sub.i is empty, its capability to drain at rate r.sub.i is distributed among the non-empty buckets. Two algorithms can be used to redistribute the leaks:

i) Redistribution of the excess capacity in proportion to the contractual rate. Say that LB.sub.z is empty. Let A={LB.sub.i :LB.sub.i >0}. Then, increment the leak rate of bucket LB.sub.i, i.epsilon.A by ##EQU3## ii) Redistribution of the excess capacity according to a priority table. Have the buckets ordered in decreasing priority order. Idle leaks go first to the head of the priority list. Only when this bucket is empty, they move to the second in the list, and so on.

These two schemes are extremes of a range that goes from a particular interpretation of fairness all the way to a discriminatory arrangement. Other possibilities include allocating the excess to the most needy bucket.

There are at least two compelling advantages to this embodiment of the invention. First, while rates relate to mean arrival rate to the system, bucket sizes are associated with the burst the system can endure. It is advantageous to have a mechanism whose worst burst equals that of assigning a standard leaky bucket per class. Second, a cleaner implementation, focused on the distribution of the excess capacity, is achieved.

System malfunctions, or external traffic not controlled by the throttle may still result in occasional system overload scenarios. While the rate control throttle is an open-loop controller, it is possible to provide a slow time-scale adaptation loop by making the set of rates {r.sub.i } dependent on the status of the system.

The access controller without an extra bucket proposed above has a built-in upward adaptation mechanism of the rates to distribute extra capacity that contrasts with the closed-loop, slow time-scale downward adaptation under overload. Actually, it is quite possible that while the overall rate is decreased due to congestion caused by uncontrolled traffic the actual rates associated with some classes are increased due to the contribution of inactive users.

The preceding access control schemes can be used to control access to a group of resources at multiple levels. For example, it may be desirable to use one system to control access to a service (e.g. wireless) among a number of customers and then to use another scheme to control access among a number of different services to the resources. FIG. 5 illustrates such a system, wherein a number of segments a-z first compete for access to one of services 1-N under the control of priority segments access controllers ("PSAC") 20. Thereafter, the services compete for access to the resources 40 under the control of a multi-service access controller ("MSAC") 30. MSAC 30 preferably uses one of the access control schemes discussed above (described, for convenience, using the "token" analogy, although the leaky bucket analogy could also be used).

Each PSAC 20 controls access to its corresponding service according to the following preferred method. Referring to FIG. 6, a number of banks B.sub.1 -B.sub.N are shown, each corresponding to one of N classes of users of a system (each class corresponding to a user segment a-z). Each class's bank B.sub.i receives a stream of tokens at a contractual rate of r.sub.i. Also associated with each class is an overflow bank O.sub.i. If a token generated for a particular class finds a full bank B.sub.i, the token is not immediately deposited in that class's overflow bank O.sub.i. Instead, the system first attempts to deposit the extra token in bank O.sub.i, representing the overflow bank of class 1, a higher priority class in this system. If overflow bank O.sub.1 is full then the token is deposited in overflow bank O.sub.2, and so on.

Thus, while each class is guaranteed its contractual rate, excess capacity is distributed on a priority scheme that favors certain classes.

Modifications to this scheme can be made as appropriate for the desired priority scheme to be implemented. For example, a single high priority class can be designated with each class first attempting to deposit overflow tokens to this class's overflow bank and if this overflow bank is full, then depositing excess tokens in their own overflow bank. The sizes of the overflow banks can also be modified to reflect the preferred priorities of the system.

A multi-class polling algorithm for processor sharing will now be described. Consider a processor to be shared by N users. Say that fraction f.sup.(0) of the processor real time is allocated to overhead (typically, f.sup.(O) .apprxeq.0.1 to 0.15). Overhead will be considered user 0, for a total of N+1 users.

Let f.sup.(i) denote the fraction of real time usage contracted by user i. Assume that ##EQU4## Normalization takes care of the case in which the sum of the contracted fractions plus the needed overhead f.sup.(0) is less than one. Job requests of user i are stored in buffer B.sub.i. Buffer B.sub.0 is reserved for overhead work. Time is divided into slots of duration .tau.. The granularity is processor dependent, and the trade-offs are easy to identify: too course of a granularity gives poor control, too fine a granularity may result in unacceptable overhead.

Every .tau. seconds the processor has to pick up .tau. seconds worth of work from one of the set of buffers B={B.sub.i, 0.ltoreq..sub.i .ltoreq.N}. The processor is scheduled in a way that: a) guarantees that every user that operates within its contractual limits receives the service it expects; b) guarantees that every user that operates above its contractual limits receives at least its contractual share; and c) the processor does not refuse service in any visit if there is work in any buffer. Note that the service discipline is not truly work conserving in that the processor may serve a buffer with less than .tau. seconds worth of work. Also note that as .tau..fwdarw.0 the discipline approaches a work conserving one.

At epoch n, the control variable u.sub.n.sup.(i) denotes the decision in relation to buffer B.sub.i : ##EQU5##

Consider a scenario in which no buffer (including B.sub.0) ever empties. Note that ##EQU6## denotes the number of times the processor has chosen a segment from the buffer B.sub.i, up to, and including, epoch n. To meet the contractual fractions {f.sup.(i) } we demand that ##EQU7##

This long run average measure is a necessary but hardly a sufficient condition to meet users' expectations. We seek then to minimize the maximum deviation of the real time allocation to user i from the target as measured by ##EQU8## which can be updated recursively as

Let b.sub.n.sup.* denote the buffer served at epoch n, and consider the following algorithm:

i) Initialization:

ii) Polling instant.

a. Polling decision: ##EQU9## (break ties with lexicographic ordering) ##EQU10## b. State update:

Accordingly, in the preferred embodiment, the polling decision at epoch n is made by selecting the largest e.sup.(i) at epoch n-1. Thus, access to the processor is granted to the user that exhibits the largest difference between its contracted share and its actual use over time. This is the most equitable method for processor sharing when all users are continuously seeking access to the processor (i.e., when user buffers never empty).

In most realistic scenarios, however, the server utilization is below 1, and buffers do empty. Also, jobs are normally sliced in segments. The length of a segment indicates the time it takes the CPU to perform the task, and it is therefore unrealistic to assume that all segments have the same duration. We now consider an alternative embodiment which takes these realistic problems into account.

Denote S.sub.n.sup.(i) the segment length at the head of buffer Bi at polling epoch n, and assume that there is a certain upper bound S.sub.max for the length of the segments. It is illustrative to focus on two particular cases, namely, the heterogeneous overloaded, and the homogeneous not overloaded scenarios. The overloaded, heterogeneous case can easily be handled by the following simple modification of equation 15:

That is, the modification is to weigh both the credit f.sup.(i) and the unit debit u.sub.n.sup.(i) by the amount of time spent by the processor serving the segment at the head of the polled buffer.

Considering the homogeneous, non-overloaded case, it is assumed that each class i is assigned the same fraction ##EQU11## of the CPU, and the segment length distribution is the same for all classes. In this scenario, a natural, fair, and indeed optimal policy according to most reasonable criteria, is the round robin algorithm, in which the server skips empty buffers.

The system proceeds when the polling buffer is empty as follows. It would be wasteful for the processor to wait for a segment to arrive, so we determine that empty buffers be skipped. The question is then how to account for the "virtual" visit to the empty buffer. One could consider not charging the empty buffer for the virtual visit, and continue giving it credit for the elapsed time. The problem with this approach is that credits accumulated by an inactive source could allow it to hog the CPU when it wakes up. A reasonable solution would be to introduce exponential smoothing in the recursion, so that more weight is put on the present than in the past. Another alternative is to distribute credit at each stage only among the active buffers. A different approach is based on the concept that the selected buffer is charged a "lost opportunity" fee for the virtual circuit.

The general process can now be stated. Recall that S.sub.n.sup.(i) is the segment length at the head of the buffer B.sub.i at polling epoch n. Should buffer B.sub.i be empty, set it to S.sub.i, where S.sub.i is, e.g., the mean segment length of user i, and call it a virtual segment.

i. Initialization:

ii. Polling instant.

a. Polling decision: ##EQU12##

(break ties with lexicographic ordering) ##EQU13##

(i can be a virtual segment, on which the processor spends no time)

b. State update:

As noted above, even though access to the resources is regulated, it may nevertheless be desirable to regulate access to one or more particular discrete resources. A Multi-class recirculating token scheme to access discrete resources in next described.

Trunks, 3-port conference circuits and UTDs (universal tone decoders) are among the discrete resources that may need to be shared between different classes of users. By its very nature, these resources are either busy or idle. Normally, the holding time of the resource far exceeds the time needed to communicate its status. And of course, the discrete nature of the resource maps naturally into the positive integers. The following is a recirculating token scheme with a common pool.

Say that there are M units of the resource for which N users compete.

Provisioning:

i. Assign n.sub.i tokens to class i bank, i=1,2, . . . N.

ii. Assign n.sub.0 tokens to the common bank b.sub.0, such that ##EQU14##

Each token gives access to one unit of the resource. Tokens are recirculated, not destroyed. That is, tokens are returned to the bank(s) (own bank, or common bank) they were taken from once the unit to which they granted access becomes free.

For example, assume that class i needs m.gtoreq.1 units of the resource. There are three possibilities: i) it has m idle tokens of its own, in which case it gets access to the desired units in exchange for the tokens, ii) it has less than m tokens of its own, but the tokens in the common bank suffice to complete the demand, and class i proceeds as in (i), and iii) the sum of its own available tokens and the available tokens in the common bank is less than m, in which case the demand is either rejected or queued, depending on the specific design of the system.

This scheme covers a wide range of solutions, from complete partition to total sharing of the resources. It reduces to complete resource partitioning when no tokens are assigned to the common bank (n.sub.0 =0). On the other extreme, if n.sub.0 =N and consequently n.sub.i =0, i=0), we have complete resource sharing. Complete partitioning is effective: class i is always guaranteed the simultaneous access to n.sub.i units of the resource. It is not efficient, in that it can never get access to more than n.sub.i, even if all the remaining N-n.sub.i units are idle. Complete sharing, on the other hand, handles this last scenario beautifully, but does not guarantee class i to n.sub.i units at every epoch. The intermediate situation 0<n.sub.0 <N represents a trade-off between guarantee and flexibility. To contribute to the common pool, class i will be allocated n.sub.i <n.sub.i. The maximum number of units it can simultaneously use will vary between n.sub.i and n.sub.i +n.sub.0, depending on the aggregate load on the system.

One variant of the scheme consists of giving a subset of users (high priority classes) access to the common bank before searching for tokens in their own banks. To get an exact correspondence a modification of the rule to return tokens is needed. According to this modification, tokens are always returned to the high priority bank, which overflows into the common bank. These variants indicate that in general a token recirculation policy is determined by:

a. Assignment of tokens, and token banks to the different classes.

b. Assignment of tokens to one or more shared banks.

c. A rule that grants access to the banks.

d. A rule that determines to which banks the used tokens should be returned.

There are some similarities between multi-class rate access control and the recirculating token scheme. Both approaches are explained in terms of the concept of tokens, and that of a common as well as class-specific devices (banks or pools). But there are also important differences that illuminate the distinctions between the problems they address. The closed loop nature of recirculating tokens contrasts with the open loop nature of the multi-class access control. Also, wile tokens in the former are inherently discrete, the latter admits real-valued tokens. The attributes of the token recirculating scheme stem from the crispy nature of discrete resources: a unit is either in use or idle, and this status is in most cases available in real time. On the other hand, an arrival admitted into a global system such as the one depicted in FIG. 1 is bound to consume a number of different resources in more subtle ways: it will increase the utilization of a certain processor, augment the delay in certain queues, etc. Also, its impact on these internal resources (processors, links, etc.) will take place at different points in time during the holding time of the activity associated with the arrival.

The preceding description includes illustrations of the preferred embodiments that are intended only as examples, and various other embodiments are within the scope of the appended claims.