
Queueing System Models 25-3
Similarly, we associate to the event d a stochastic sequence {Z
1
, Z
2
, ...},whereZ
k
is the kth service time,
i.e., the time required for the kth customer to be served, k =1, 2, .... If we assume that the stochastic
sequence {Z
k
}is also iid, then we define
B(t) = P[Z ≤ t] (25.3)
where Z is a generic service time. Similar to Eq. (25.2), we use the following notation for the mean
of B(t):
E[Z] ≡
1
µ
(25.4)
so that µ is the service rate of the server in our model.
Structural Parameters. The most common structural parameters of interest in a queueing system are (i)
The storage capacity of the queue, usually denoted by K =1, 2, ....By convention, we normally agree to
include in this storage capacity the space provided for customers in service. (ii) The number of servers,
usually denoted by m =1, 2, ....In the simple system of Figure 25.1, we have K =∞and m =1.
Operating Policies. Even for the simple system of Figure 25.1, there are various schemes one can adopt in
handling the queueing process. Here are just some of the natural questions that arise about the operation
of the system: (i) Is the service time distribution the same for all arriving customers? (ii) Are customers
differentiated on the basis of belonging to different“classes,” some of which may have a higher priority than
others in requesting service? (iii) Are all customers admitted to the system? (iv) Are customers allowed to
leave the queue before they get served, and, if so, under what conditions? (v) How does the server decide
which customer to serve next (if there are more than one in the queue); for example, the first one in queue,
anyone at random, and so forth? (vi) Is the server allowed to preempt a customer in service to serve a
higher-priority customer that just arrived?
Clearly, operatingpoliciescan cover a widerange of possibilities. In categorizing them, the most common
issues we consider are the following: (i) Number of customer classes. In the case of a single-class system, all
customers have the same service requirements and the server treats them all equally. This means that the
service time distribution is the same for all customers. In the case of a multiple-class system, customers
are distinguished according to their service requirements and/or the way in which the server treats them.
(ii) Scheduling policies. In a multiple-class system, the server must decide upon a service completion which
class to process next. For example, the server may always give priority to a particular class, or it may
preempt a customer in process because a higher priority customer just arrived. (iii) Queueing disciplines.
A queueing discipline describes the order in which the server selects customers to be processed, even if
there is only a single class. For example, first-come-first-served (FCFS), last-come-last-served (LCFS), and
random order. (iv) Admission policies. Even if a queue has infinite storage capacity, it may be desirable
to deny admission to some arriving customers. In the case of two arriving classes, for instance, higher
priority customers may always be admitted, but lower priority customers may only be admitted if the
queue is empty or if some amount of time has elapsed since such a customer was admitted. (v) Batching.
It is possible that arrivals occur in “batches,” i.e., customers may arrive one at a time or in groups of size
n > 1. Similarly, it is possible that service occurs in batches of size n > 1 customers processed at a time.
In the simple case of Figure 25.1, we assume a single-class system with all arriving customers admitted
and served one at a time and the queueing discipline is FCFS.
Notation. It is customary in queueing theory to employ a particular type of notation to succinctly
describe a system. This notation (attributed to Kendall) is A/B/m/K,whereA is the interarrival time
distribution, B the service time distribution, m the number of servers present, m =1, 2, ..., and K the
storage capacity of the queue, K =1, 2, .... Thus, the infinite queueing capacity single-server system of
Figure 25.1 is described by A/
B/1/∞. To simplify the notation, if the K position is omitted it is understood
that K =∞. Therefore, in our case, we have A/B/1. Furthermore, there is some common notation used
to represent the distributions A and B. In particular, G stands for a General distribution when nothing
else is known about the arrival/service process, GI for a General distribution in a renewal arrival/service
process (i.e., all interarrival/service times in that process are iid), D for the Deterministic case, (i.e., the