We consider multirate loss models of random arriving calls with elastic bandwidth requirements and fixed bandwidth allocation during service. Calls may retry several times upon arrival (requiring less bandwidth each time) in order to be accepted for service. Alternatively, calls may request less bandwidth upon arrival, according to the occupied link bandwidth indicated by threshold(s).
In the single‐retry model (SRM), a link of capacity b.u. accommodates Poisson arriving calls of service‐classes, under the CS policy. A new call of service‐class has a peak‐bandwidth requirement of b.u. and an exponentially distributed service time with mean . If the initially required b.u. are not available in the link, the call is blocked, but immediately retries to be connected with bandwidth requirement b.u., while the mean of the new (exponentially distributed) service time increases to , so that the product bandwidth requirement by service time remains constant [1,2]. If the b.u. are not available, the call is blocked and lost (Figure 2.1). The CAC mechanism of a call of service‐class is depicted in Figure 2.2. A new call of service‐class is blocked with b.u. if and is accepted with b.u., if , where and are the in‐service calls of service‐class (in the steady state of the system) accepted with b.u., respectively. The comparison of the SRM with the EMLM reveals the following basic differences:
To describe the analytical model in the steady state, let us concentrate on a single link of capacity b.u. that accommodates two service‐classes with the following traffic characteristics: . Blocked calls of service‐class 2 can retry with parameters , while blocked calls of service‐class 1 are not allowed to retry. Although the SRM does not have a PFS, we assume that the LB equation (1.51) proposed in the EMLM does hold, that is:
This assumption (approximation) is important for the derivation of an approximate but recursive formula for the calculation of . The aforementioned equation expresses the fact that no call blocking occurs in state , if there are available b.u. . If , when a new call of service‐class 2 arrives in the system, then this call is blocked and retries to be connected with b.u. If , then, the retry call will be accepted in the system. To describe the latter case, we need an additional LB equation [ 2]:
where is the mean number of service‐class calls accepted in the system with in state .
Dividing (2.2) by and multiplying by , we obtain [ 2]:
where is the offered traffic‐load of service‐class 2 calls with .
Equation (2.1) can be written as . Then, by multiplying both sides with and summing up for , we have:
Adding (2.3) to (2.4), and since , we have:
Apart from the assumption of the LB equation ( 2.1), another approximation is necessary for the recursive calculation of [ 2]:
Equation (2.6) expresses the so‐called migration approximation [ 1, 2,4], according to which the number of calls accepted in the system with other than the maximum bandwidth requirement is negligible within a state space, called the migration space. In this space, the value of is negligible compared to when . For service‐class (with ):
Equation ( 2.4) due to ( 2.6) is written as:
The combination of (2.5) and (2.8) is achieved through the use of a binary parameter (), and gives an approximate but recursive formula for the determination of in the SRM, considering two service‐classes where only calls of service‐class 2 can retry [ 1, 2]:
where , and when (otherwise ).
The symbol is used to distinguish retry models, where only the migration approximation exists, from other models (e.g., thresholds models presented in Section 2.5) where the symbol is used and additional approximations are considered.
The generalization of (2.9) for service‐classes, where all service‐classes may retry, is as follows [ 2]:
where and when (otherwise ).
Note that the variable in (2.10) expresses the migration approximation, i.e., (2.7).
Having determined the unnormalized values of , we can calculate the following performance measures:
In the system of Example 2.1 ():
The normalization constant is
. |
Thus:
(compare with the exact 0.20692) | ||
(compare with the exact 0.55226) | ||
(compare with the exact 0.37764) | ||
(compare with the exact 0.68380) |
It is apparent that even in small SRM examples the error introduced by the assumption of LB and the migration approximation is not significant.
In the SRM under the BR policy (SRM/BR), b.u. are reserved to benefit calls of all other service‐classes apart from service‐class . The application of the BR policy in the SRM is similar to that of the EMLM/BR, as the following example shows.
Consider Example 2.1 () and apply the BR parameters b.u. and b.u. to the first and second service‐class, respectively.
By replacing one GB equation, say (1,0,0), with the equation of the normalization condition , the solution of the resultant linear system is:
Based on the values of , we have:
The of service‐class 2 calls is given by:
Finally, the CBP of service‐class 2 (calls with ), is given by:
We see that the BR policy has substantially increased (from 0.206923 in the SRM to 0.548536 in the SRM/BR) and as a result there is a decrease in (from 0.377639 in the SRM to 0.301968 in the SRM/BR).
To calculate the link occupancy distribution in the steady state of the SRM/BR, we prefer the Roberts method to the Stasiak–Glabowski method. The latter is more complex compared to the Roberts method and does not provide more accurate results (compared to simulation) in retry loss models and threshold loss models (see Section 2.6, below) [5].
Based on the Roberts method, ( 2.10) takes the form [ 4]:
where , , when (otherwise ), is given by (1.65) and, similarly, by:
Based on (2.18) and (2.19), we can calculate the following performance measures:
In the system of Example 2.3 ():
The normalization constant is . Thus:
(compare with the exact 0.548536) | |
(due to the values of the BR parameters) | |
(compare with the exact 0.301968) |
Consider a single link of capacity b.u. that accommodates calls of four different service‐classes with the following traffic characteristics:
That is, only calls of service‐class 4 have the ability to retry.
In Figure 2.6, we present the link utilization results for the EMLM and SRM; both models give almost the same results, a fact that is explained by the fact that the CBP decrease in service‐class 4 is accompanied by the CBP increase of the other service‐classes.
Table 2.1 CBP of Example 2.5 (SRM, b.u. and b.u.).
b.u. | b.u. | |||
CBP | Analytical results | Simulation results | Analytical results | Simulation results |
0.0479 | 0.0493 1.2745e‐4 | 0.0004 | 0.0004 9.0281e‐6 | |
0.2997 | 0.2986 5.1219e‐4 | 0.0031 | 0.0029 5.6690e‐5 | |
0.5089 | 0.5077 4.7558e‐4 | 0.0063 | 0.0060 6.8768e‐5 | |
0.7360 | 0.7430 4.8105e‐4 | 0.0128 | 0.0125 1.0325e‐4 | |
0.5089 | 0.5081 6.3207e‐4 | 0.0063 | 0.0060 8.0577e‐5 | |
0.6914 | 0.6844 1.4349e‐3 | 0.4955 | 0.4871 4.6728e‐3 |
Table 2.2 CBP of Example 2.5 (SRM/BR, b.u. and b.u.).
b.u. | b.u. | |||
CBP | Analytical results | Simulation results | Analytical results | Simulation results |
0.3804 | 0.3825 3.3290e‐4 | 0.00485 | 0.00485 1.1740e‐4 | |
0.3804 | 0.3826 4.2058e‐4 | 0.00485 | 0.00486 1.6266e‐4 | |
0.3804 | 0.3824 4.2857e‐4 | 0.00485 | 0.00485 1.3816e‐4 | |
0.3804 | 0.3825 6.0689e‐4 | 0.00485 | 0.00487 1.0434e‐4 |
In the multi‐retry model (MRM), calls of service‐class can retry not only once, but several times, in order to be accepted in the system [ 1, 2]. Let be the number of retrials for calls of service‐class , and assume that , where is the required bandwidth of a service‐class call in the retry, . Then a service‐class call is accepted in the system with b.u. if . By definition, and .
Consider a link of b.u. The link accommodates Poisson arriving calls of two service‐classes. Calls of service‐class 1 require b.u., while calls of service‐class 2 require . Blocked calls of service‐class 2, in order to be accepted in the system, can immediately retry two times with b.u. and b.u. Let calls/sec, sec, sec, and sec (in this example we do not assume that ).
By replacing the GB equation of (1,0,0,0) with the normalization condition , the solution of this linear system is:
Based on the values of , we have:
The of service‐class 2 is given by:
The of service‐class 2, is given by:
The CBP of service‐class 2 is given by:
The link utilization is determined by: b.u.
Compare these results with the corresponding CBP and link utilization results in the case of the EMLM: b.u.
Following the analysis of Section 2.1.2.1, we have to assume in the MRM the existence of both LB and the migration approximation. According to the migration approximation, the mean number of service‐class k calls in state , , accepted with b.u., is negligible when , where . This means that service‐class k calls with are limited in the area . Based on [1, 2], the unnormalized values of can be determined by the following recursive formula:
where when (otherwise ).
Having determined the unnormalized values of , we can determine the following performance measures:
In the system of Example 2.6 ():
The normalization constant is . Thus:
(compare with the exact 0.545687) | ||
(compare with the exact 0.876443) | ||
(compare with the exact 0.725882) | ||
(compare with the exact 0.545687) | ||
(compare with the exact 0.62262) |
In this very small example, the recursive formula ( 2.22) does not provide very good results compared to the exact results of Example 2.6. For an explanation, consider the effect of the migration approximation to the calculation of . The migration approximation assumes that service‐class 2 calls with and exist only when . However, we have already seen in Example 2.6 that , when (states : and ), while , when (states , ).
The normalization constant is . Thus:
(compare with the exact 0.416381) | |
(compare with the exact 0.72426) | |
(compare with the exact 0.59663) | |
(compare with the exact 0.416381) | |
(compare with the exact 0.57491) |
It is worth mentioning that the exact values require the knowledge of 25 steady state probabilities of the form . Of course, the increase of results in a larger system (25 states vs 14 states when ) in which the migration approximation introduces less error in the calculation of .
Obviously, in the MRM under the BR policy (MRM/BR), unlike the SRM/BR, blocked calls of service‐class can retry more than once to be connected in the system.
Consider the system of Example 2.6 () under the BR policy with BR parameters b.u. and b.u. for the two service‐classes, respectively, so that . In that case, CBP of service‐class 1 calls is equalized with the of calls of service‐class 2:
By replacing the GB equation of with , the solution of this linear system is:
Based on the values of , we have:
(compare with 0.545687 in the MRM) |
The of service‐class 2 is given by:
(compare with 0.876443 in the MRM) |
The of service‐class 2 is given by:
(compare with 0.725882 in the MRM) |
The CBP of service‐class 2 is given by:
(compare with 0.545687 in the MRM) |
The link utilization is determined by:
b.u. | (compare with 2.148 b.u. in the MRM) |
Based on the Roberts method, we calculate the unnormalized link occupancy distribution in the steady state of the MRM/BR by modifying ( 2.22) as follows [ 4]:
where when (otherwise ), and is given by (1.65) and, similarly, by:
Based on (2.27) and (2.28), we can determine the following performance measures:
In the system of Example 2.8 ():
(due to the BR parameter ) |
The normalization constant is . Thus,
CBP of service‐class 1 |
CBP of service‐class 2 |
(compare with the exact 0.819672) | |
(compare with the exact 0.606557) | |
(compare with the exact 0.514754) |
In this very small example, ( 2.27) does not provide good results compared to the exact values of Example 2.8. This is because, the Roberts approximation (BR policy) and the migration approximation have additively introduced errors on the results. Fortunately, in larger examples (i.e., more realistic scenarios) the results provided by ( 2.27) are quite good compared to simulation [ 4]. To be more specific, in this example, the Roberts approximation ignores the transition from state to for . On the other hand, migration approximation ignores the existence of states and , since and when .
Consider a single link of capacity b.u. that accommodates calls of four different service‐classes with the following traffic characteristics: , , and That is, only calls of service‐class 4 have the ability to retry four times; note that the product bandwidth by service time for service‐class 4 remains constant.
Table 2.3 CBP of Example 2.10 (MRM, b.u.).
CBP | Analytical results | Simulation results |
0.0049 | 0.0049 8.3970e‐5 | |
0.0202 | 0.0202 5.3021e‐4 | |
0.0273 | 0.0286 4.9654e‐4 | |
0.1161 | 0.1142 1.6558e‐3 | |
0.0349 | 0.0374 3.0918e‐4 |
In the single‐threshold model (STM), the requested b.u. and the corresponding service time of a new call are related to the value of the occupied link bandwidth (upon the new call arrival). More precisely, the following CAC is applied. When the value of is lower or equal to a threshold , then a new call of service‐class is accepted in the system with its initial requirements . Otherwise, if , the call tries to be connected in the system with , where and , so that the product bandwidth requirement by service time remains constant [ 1]. This means that, contrary to the SRM, a call does not have to be blocked in order to retry with lower bandwidth requirement. If the b.u. are not available the call is blocked and lost.
The comparison of the STM with the SRM reveals the following basic similarities and differences:
Consider again Example 2.1 () and let b.u.
By replacing the GB equation of with the equation , the solution of this linear system is:
Based on the values of we have:
(compare with 0.206923 in the SRM) |
The CBP of service‐class 2 is given by:
(compare with 0.377639 in the SRM) |
The link utilization is determined by:
b.u. | (compare with 2.66 b.u. in the SRM) |
Aiming at deriving a recursive formula for the calculation of (the unnormalized link occupancy distribution), we consider a link of capacity b.u. that accommodates calls of two service‐classes, whose initial bandwidth requirements are and b.u., respectively. Calls of each service‐class arrive in the link according to a Poisson process with means and , and have exponentially distributed service times with means and , respectively. If upon the arrival of a service‐class 2 call, then this call requests from the system and . No such option is considered for calls of service‐class 1.
Although the STM does not have a PFS, we assume that the LB equation (1.51) does hold for calls of service‐class 1, for :
For calls of service‐class 2, we assume the existence of LB between adjacent states that can be expressed as follows [ 2]:
where is the mean number of service‐class 2 calls with in state .
Equations (2.31)–(2.33) lead to the following system of equations [ 2]:
For (2.34), the following approximation is adopted: the value of in state is negligible when . This approximation is similar to the migration approximation used in the SRM. For (2.36), the following approximation is applied: the value of in state is negligible when . This approximation is named the upward migration approximation and is different from the migration approximation since it considers negligible the population of calls with their initial bandwidth requirement [ 2]. The error introduced by the upward migration approximation in the calculation of can be higher than the corresponding error introduced by the migration approximation of the SRM, especially when the offered traffic‐load is light. In that case, it is highly probable that calls are accepted in the system with their initial bandwidth requirement [2].
Based on the above‐mentioned approximations, we have (for ):
where , , and .
Note that in (2.37), expresses the upward migration approximation and expresses the migration approximation.
In the general case of service‐classes, the approximate but recursive formula for is the following [ 2]:
where , and .
Having determined the unnormalized values of , we can calculate the following performance measures:
Note that if , then (2.40) is identical to ( 2.13) of the SRM.
In the system of Example 2.11 ():
The normalization constant is . Thus:
(compare with the exact 0.165955) |
(compare with the exact 0.382997) |
(compare with the exact 0.53779) |
It is apparent that the error of the results in this small STM example is higher compared to the corresponding SRM example. This is due to the fact that in addition to the LB assumption and the migration approximation, which hold in the SRM, the upward migration approximation is introduced to the STM.
In the STM under the BR policy (STM/BR), b.u. are reserved to benefit calls of all other service‐classes apart from service‐class . The application of the BR policy in the STM is similar to that of the SRM/BR as the following example shows.
Consider Example 2.3 () and let b.u. This means that calls of service‐class 2 are accepted in the system with b.u. whenever .
By replacing the GB equation of (1,0,0) with the equation , the solution of this linear system is:
Based on the values of , we have:
(compare with 0.548536 in the SRM/BR) |
Finally, the CBP of service‐class 2 is given by:
(compare with 0.301968 in the SRM/BR) |
Similar to the SRM/BR, we adopt the Roberts method for the calculation of in the STM/BR.
Based on the Roberts method, ( 2.38) takes the form [ 4]:
where , , , is given by (1.65), and
Based on (2.44) and (2.45), we can determine the following performance measures:
In the system of Example 2.13 ():
The normalization constant is . Thus:
(compare with the exact 0.545538) |
(compare with the exact 0.31399) |
(compare with the exact 0.44617) |
It is apparent that in this small STM/BR example the error introduced by the assumption of LB, the migration approximation, the upward migration approximation, and the introduction of the BR policy via the Roberts method is high, especially for .
Consider a single link of capacity b.u. that accommodates calls of four different service‐classes with the following traffic characteristics: , , , , , and .
Based on Figure 2.15, we see that the increase of results in the substantial decrease of and a minor decrease in the CBP of the first three service‐classes. This was anticipated since calls of service‐class 4 use the requirement more frequently compared to the SRM.
Table 2.4 CBP of Example 2.15 (STM, or b.u., and ).
b.u. | b.u. | |||
CBP | Analytical results | Simulation results | Analytical results | Simulation results |
0.0474 | 0.0479 2.9368e‐4 | 0.0003 | 0.00026 1.6765e‐5 | |
0.2953 | 0.2948 3.3213e‐4 | 0.0025 | 0.0019 3.3650e‐5 | |
0.5086 | 0.5074 3.6020e‐4 | 0.0054 | 0.0042 3.0290e‐5 | |
0.5361 | 0.5302 3.2453e‐4 | 0.1579 | 0.1363 2.3964e‐3 |
Table 2.5 CBP of Example 2.15 (STM, or b.u., and ).
b.u. | b.u. | |||
CBP | Analytical results | Simulation results | Analytical results | Simulation results |
0.0475 | 0.0480 1.4185e‐4 | 0.0003 | 0.00017 1.2923e‐5 | |
0.2949 | 0.2948 5.6484e‐4 | 0.0021 | 0.00137 2.9135e‐5 | |
0.5082 | 0.5074 6.7936e‐4 | 0.0047 | 0.00297 6.4709e‐5 | |
0.5124 | 0.5113 7.5074e‐4 | 0.0702 | 0.0511 8.6489e‐4 |
Table 2.6 CBP of Example 2.15 (STM/BR, or b.u., and ).
b.u. | b.u. | |||
CBP | Analytical results | Simulation results | Analytical results | Simulation results |
0.3783 | 0.3799 5.0062e‐4 | 0.00410 | 0.00332 2.6103e‐5 | |
0.3783 | 0.3799 4.6590e‐4 | 0.00410 | 0.00333 4.1082e‐5 | |
0.3783 | 0.3799 7.1394e‐4 | 0.00410 | 0.00332 3.8769e‐5 | |
0.3783 | 0.3799 6.9529e‐4 | 0.00410 | 0.00333 3.6205e‐5 |
In the multi‐threshold model (MTM), there exist different thresholds which are common to all service‐classes [ 1, 2]. A call of service‐class with initial requirements can use, depending on the occupied link bandwidth, one of the requirements , where the pair is used when (where . The maximum possible threshold is , while . As far as the bandwidth requirements of a service‐class call are concerned, we assume that they decrease as increases, i.e., , while by definition (see Figure 2.17).
To describe the MTM in steady state, the following LB equations are considered:
and
where denotes the mean number of service‐class calls, with , in state .
Similar to the analysis of the STM and based on (2.49) and (2.50), we have the following recursive formula for the calculation of [ 1, 2]:
where and .
Note that in (2.51), expresses the upward migration approximation, while expresses the migration approximation.
Based on ( 2.51), we can determine the following performance measures:
In the MTM under the BR policy (MTM/BR), b.u. are reserved to benefit calls of all other service‐classes apart from service‐class . The application of the BR policy in the MTM is similar to that of the MRM/BR.
Similar to the MRM/BR, we adopt the Roberts method for the calculation of the unnormalized link occupancy distribution in the MTM/ BR.
Based on the Roberts method, ( 2.51) takes the form [ 4]:
where , , and
Based on (2.57) and (2.58), we can determine the following performance measures:
Consider again Example 2.10 ( , and ). Calls of service‐class 4 reduce their bandwidth four times according to the following 12 sets of thresholds:
Set 1: | |
Set 2: | |
Set 3: | |
Set 12: |
In the case of Set 1 the same CBP results are anticipated by the MRM and the MTM.
In the connection dependent threshold model (CDTM), bandwidth and service time requests depend on the total number of occupied b.u. of a link of capacity , as in the MTM. The only difference with the MTM is that different service‐classes may have different sets of thresholds. Specifically, we consider service‐classes of Poisson arriving calls with mean arrival rates that require b.u. per call and a mean service time , exponentially distributed. Calls compete for the available bandwidth under the CS policy. The offered traffic‐load of calls of service‐class is . Let , and . Each arriving call of a service‐class may have bandwidth and service‐time requirements, that is, one initial requirement with values and more requirements with values , where and , and . The pair is used when , where and are two successive thresholds of service‐class , while ; the highest possible threshold (other than ) is (see Figure 2.20). By convention, and , while the pair is used when .
As an application example of the CDTM, imagine a CPU (server in a LAN) exclusively devoted to video file format conversion (e.g., from AVI to DVD). The CPU collaborates with a CAC, which either accepts or denies conversion requests, depending on the current status and the processing capacity of the CPU (let it be 60 video frames/sec). We consider conversion requests for movies (service‐class 1), video clips (service‐class 2), and advertisements (short video clips, service‐class 3). Requests for movies are processed with a conversion rate of either 40 or 30 frames/sec, while requests for video clips are processed with a conversion rate of either 20 or 10 frames/sec, depending on the current CPU status, as Figure 2.21 shows. In Figure 2.21, the CPU together with the CAC is equivalent to a link of capacity b.u., considering that 1 b.u.= 10 frames/sec. Requests for advertisements are processed with a fixed conversion rate of 10 frames/sec. In order to determine the percentage of denied conversion requests per service‐class, we apply the CDTM with the following traffic and bandwidth requirements for each service‐class: , and , respectively. Furthermore, b.u., , and , so that and .
Similar to the MTM, the CDTM has no PFS. To describe the CDTM in steady state, the following LB equations are assumed:
where denotes the mean number of service‐class calls, with , in state .
Formulas (2.63) and (2.64) are graphically presented in Figure 2.22.
Similar to the analysis of the MTM and based on ( 2.63) and ( 2.64), we have the following recursive formula for the calculation of [ 4]:
where and .
As a summary, in order to derive (2.65), the following assumptions (approximations) are necessary:
Note that in both (ii) and (iii), the values of and may not be negligible in the corresponding migration and upward migration spaces, respectively (see Example 2.18). The determination of these values can improve the accuracy of the CDTM, compared to simulation, but is beyond the scope of this book. The reader may refer to [7,8].
Consider again Example 2.17 (). Calls of service‐class 1 behave as in the SRM due to the associated threshold parameter . Calls of service‐class 2 behave as in the STM due to the associated threshold parameter . A migration space exists for calls of service‐class 1, while both migration and upward migration spaces exist for calls of service‐class 2. More precisely:
In reality, however, the values of and may not be negligible. To illustrate this statement as well as the migration and upward migration spaces for Example 2.17, we present in Figure 2.23 an excerpt from the state transition diagram. In Figure 2.23, we give only the following specific state transitions. Assume that the system is in state , servicing a call of service‐class 2 with bandwidth , when a new call of service‐class 1 arrives. This call is accepted with its initial bandwidth and the system passes to state , transferring to that state the call of service‐class 2 which is still in service. It is therefore apparent to expect that the average number of service‐class 2 calls in state (which belongs to the upward migration space of service‐class 2), denoted as , will not be zero. On the other hand, if the system is in state and a call of service‐class 3 (with ) leaves the system, then the system passes to state and the population of service‐class 1 calls with (if any) is transferred to . Thus, we also expect that the average number of service‐class 1 calls with in state (which belongs to the migration space of service‐class 1), denoted as , will not be zero.
Based on ( 2.65), we can determine the following performance measures:
Consider a link of capacity b.u. in which calls of four service‐classes are accommodated. Calls of service‐classes 2, 3, and 4 can reduce their bandwidth requirements one, two, and three times, respectively. The traffic and bandwidth requirements of all service‐classes are the following:
where and are the vectors of the reduced bandwidth and increased service‐time of service‐class , respectively.
Use the following three sets of threshold parameters for service‐classes 2, 3, and 4:
Set 1: | ||||||
Set 2: | ||||||
Set 3: |
By using Set 1, service‐classes 2, 3, and 4 behave according to the MRM. By using Set 2, service‐classes 2 and 3 behave according to the MRM, while service‐class 4 behaves according to the CDTM. By using Set 3, all service‐classes behave as in the CDTM. Provide CBP results of all service‐classes and compare them to the corresponding simulation results. Comment on the results.
In Tables 2.7–2.9 we present the analytical and the simulation CBP results for Sets 1–3, respectively, and for seven values of . Needless to say that the CBP of service‐classes 2, 3, and 4 are determined based on their last bandwidth requirement. Simulation results are mean values of 12 runs with 95% confidence interval.
Each point P in the first column of Tables 2.7–2.9 corresponds to a vector . Point corresponds to . In the successive points the values of and are increased by 5 and 3, respectively, while and remain constant. That is, point corresponds to and point to . The analytical CBP results of service‐classes 2 and 3 coincide since both service‐classes have the same last bandwidth requirement (i.e., 4). This is validated from the simulation results. Based on Tables 2.7– 2.9, we see that:
Table 2.7 Analytical and simulation CBP results for Set 1 (Example 2.19).
Analytical CBP (%) | Simulation CBP (%) | |||||||
P | ||||||||
1 | 1.89 | 7.43 | 7.43 | 9.98 | 1.89 0.06 | 6.73 0.17 | 6.79 0.15 | 9.03 0.22 |
2 | 2.41 | 9.35 | 9.35 | 12.54 | 2.47 0.07 | 8.63 0.11 | 8.67 0.14 | 11.62 0.19 |
3 | 2.98 | 11.40 | 11.40 | 15.28 | 3.06 0.07 | 10.68 0.27 | 10.69 0.24 | 14.53 0.36 |
4 | 3.58 | 13.54 | 13.54 | 18.12 | 3.73 0.07 | 12.78 0.16 | 12.75 0.18 | 17.32 0.33 |
5 | 4.21 | 15.74 | 15.74 | 21.03 | 4.37 0.07 | 14.94 0.18 | 14.89 0.19 | 20.22 0.25 |
6 | 4.86 | 17.96 | 17.96 | 23.95 | 5.06 0.07 | 17.08 0.22 | 17.05 0.18 | 23.36 0.33 |
7 | 5.52 | 20.16 | 20.16 | 26.85 | 5.71 0.08 | 19.40 0.25 | 19.32 0.31 | 26.38 0.42 |
Table 2.8 Analytical and simulation CBP results for Set 2 (Example 2.19).
Analytical CBP (%) | Simulation CBP (%) | |||||||
P | ||||||||
1 | 1.68 | 6.53 | 6.53 | 9.49 | 1.56 0.007 | 5.69 0.01 | 5.70 0.006 | 7.90 0.04 |
2 | 2.19 | 8.42 | 8.42 | 12.17 | 2.13 0.01 | 7.62 0.03 | 7.62 0.03 | 10.68 0.04 |
3 | 2.76 | 10.47 | 10.47 | 15.07 | 2.75 0.02 | 9.70 0.04 | 9.72 0.03 | 13.68 0.06 |
4 | 3.38 | 12.63 | 12.63 | 18.10 | 3.44 0.02 | 11.95 0.03 | 11.96 0.03 | 16.91 0.02 |
5 | 4.03 | 14.86 | 14.86 | 21.20 | 4.14 0.02 | 14.23 0.04 | 14.23 0.03 | 20.20 0.05 |
6 | 4.70 | 17.12 | 17.12 | 24.31 | 4.90 0.02 | 16.56 0.05 | 16.55 0.03 | 23.47 0.06 |
7 | 5.39 | 19.37 | 19.37 | 27.39 | 5.64 0.01 | 18.85 0.04 | 18.86 0.04 | 26.79 0.07 |
Table 2.9 Analytical and simulation CBP results for Set 3 (Example 2.19).
Analytical CBP (%) | Simulation CBP (%) | |||||||
P | ||||||||
1 | 0.95 | 4.01 | 4.01 | 8.21 | 0.51 0.05 | 2.15 0.13 | 2.12 0.12 | 4.28 0.24 |
2 | 1.35 | 5.70 | 5.70 | 11.47 | 1.00 0.05 | 4.11 0.15 | 4.10 0.14 | 8.15 0.34 |
3 | 1.82 | 7.66 | 7.66 | 15.15 | 1.61 0.07 | 6.41 0.24 | 6.47 0.17 | 12.64 0.40 |
4 | 2.35 | 9.80 | 9.80 | 19.07 | 2.23 0.04 | 8.79 0.16 | 8.87 0.18 | 17.34 0.21 |
5 | 2.91 | 12.06 | 12.06 | 23.11 | 2.90 0.07 | 11.49 0.18 | 11.42 0.17 | 21.71 0.42 |
6 | 3.50 | 14.39 | 14.39 | 27.14 | 3.42 0.06 | 13.78 0.21 | 13.73 0.22 | 26.00 0.46 |
7 | 4.12 | 16.73 | 16.73 | 31.08 | 4.19 0.10 | 16.18 0.24 | 16.13 0.27 | 30.34 0.51 |
In the CDTM under the BR policy (CDTM/BR), b.u. are reserved to benefit calls of all other service‐classes apart from service‐class . The application of the BR policy in the CDTM is similar to that of the MTM/BR.
Similar to the MTM/BR, we adopt the Roberts method for the calculation of in the CDTM/BR. Based on the Roberts method, ( 2.65) takes the form [ 4]:
where and .
Based on (2.70), we can determine the following performance measures:
Consider four service‐classes of Poisson arriving calls with the following traffic characteristics: , and . Calls are accommodated by a link of capacity b.u. under the BR policy. Calls of service‐classes 3 and 4 may reduce their bandwidth, upon their arrival, according to the thresholds of Figure 2.24. Choose the BR parameters so that CBP are equalized among all service‐classes. Calculate the equalized CBP and compare them to the corresponding simulation results when the offered traffic‐load increases from the initial value to , and in six equal steps.
Since , and b.u., we choose the BR parameters that achieve CBP equalization as follows: , and . Then, . Table 2.10 shows the analytical and simulation CBPs for the seven different sets of offered traffic‐load. Simulation CBP results are very close to the analytical equalized CBP results and validate the CTDM.
Table 2.10 Equalized CBP for Example 2.20.
Equalized | Simulation CBP (%) | ||||
(erl) | CBP (%) | ||||
(100, 12.0, 12.0, 1.0) | 4.19 | 3.36 0.11 | 3.36 0.11 | 3.35 0.13 | 3.32 0.20 |
(110, 13.2, 13.2, 1.1) | 8.64 | 7.61 0.15 | 7.60 0.15 | 7.61 0.21 | 7.63 0.21 |
(120, 14.4, 14.4, 1.2) | 13.85 | 13.11 0.22 | 13.11 0.17 | 13.08 0.23 | 13.10 0.25 |
(130, 15.6, 15.6, 1.3) | 19.11 | 18.57 0.26 | 18.54 0.24 | 18.56 0.27 | 18.52 0.22 |
(140, 16.8, 16.8, 1.4) | 24.07 | 23.68 0.23 | 23.70 0.22 | 23.70 0.24 | 23.71 0.30 |
(150, 18.0, 18.0, 1.5) | 28.62 | 28.43 0.20 | 28.43 0.25 | 28.44 0.21 | 28.45 0.32 |
(160, 19.2, 19.2, 1.6) | 32.75 | 32.58 0.31 | 32.60 0.27 | 32.57 0.17 | 32.59 0.40 |
We concentrate only on the CDTM since it comprises the retry and threshold models. The initial motivation for the CDTM was the available bit rate (ABR) service of asynchronous transfer mode (ATM) networks. The ABR service is a purely elastic service in which the notion of equivalent bandwidth is not well applicable (i.e., the ABR service cannot be considered a stream service having its average bandwidth per call, as constant rate). Therefore, a different model to the EMLM is needed, and this is the CDTM because it sufficiently models an elastic call at its set‐up phase (but not during the entire call duration) by adequately setting the threshold parameters. Thus, the CDTM is applicable to any elastic service at the call set‐up phase, as long as it is not a bandwidth hungry application wasting all the available bandwidth. For this reason, a threshold scheme must be applied (e.g., Figure 2.20). The logic behind the threshold scheme is that even if the available bandwidth of a link is large enough, a CAC does not always waste it on one call only, but saves a part of it for sharing with the next calls.
The minimum and the maximum bandwidth requirements of an elastic call are important CDTM parameters for the CBP calculation no matter what the thresholds are. The minimum bandwidth requirement is critical for the CBP value. If the minimum required bandwidth is zero, an elastic call should wait for any available bandwidth to start servicing. If the network (CAC) ignores the details of bandwidth requirements (i.e., the threshold scheme) of an elastic call, the assigned bandwidth will not meet the real needs of the call and the CBP calculation will not be accurate. Suppose, for instance, that an elastic call has the following thresholds scheme in a transmission link with bandwidth capacity of 19.2 Mbps: maximum rate of 1.536 Mbps for available link bandwidth at least 6.4 Mbps (first threshold at Mbps), rate of 768 kbps for available link bandwidth at least 3.2 Mbps at least (second threshold at Mbps), and minimum rate of 384 kbps for available link bandwidth less than 3.2 Mbps (third threshold at 19.2 Mbps, or at Mbps). Assume that the CAC knows only the minimum and maximum resource requirements of this elastic call, and offers to it (a) 700 kbps or (b) 1.536 Mbps when the available bandwidth is 4.0 Mbps at least in both cases. In the first case, the holding time will be estimated incorrectly (by taking into account 768 kbps instead of 700 kbps), while in the second case, although the holding time will be estimated correctly, the threshold scheme has been violated, therefore the CBP through the CDTM cannot be accurate. As far as the number of thresholds between the minimum and the maximum bandwidth requirements is concerned, several values exist since bandwidth is quantized and provided as a group of b.u. (trunks). So, in a realistic network environment the number of thresholds is manageable.
In what follows, we concentrate on the applicability of the CDTM to WCDMA networks. We have skipped straightforward applications, albeit some of them are very interesting, such as the application of the CDTM on smart grid, for a fine control of energy consumption [9].
The CDTM can be applied to WCDMA networks (in the uplink) in a similar way to the EMLM. A single BS controlling a cell can be modeled as a system of certain bandwidth capacity. The b.u. can be an equivalent bandwidth defined by the load factor introduced, for instance, by a lower rate service‐class (e.g., voice). The load factor is determined by the signal‐to‐noise ratio (SNR), data rate, and activity factor (probability that a call is active – transmits) of the associated service‐class. As far as the inter‐cell interference is concerned, it is assumed log‐normally distributed1 and independent of the cell load. A call is accepted for service as long as there are enough resources available in the cell. The CAC policy is based on the estimation of the increase in the total interference (intra‐ and inter‐cell interference plus thermal noise) caused by the acceptance of new calls. After call acceptance, the SNR of all in‐service calls deteriorates; because of this, WCDMA systems usually have no hard limits on call capacity. A call should not be accepted if it increases the noise of all in‐service calls above a tolerable level. Poisson arriving calls to a cell may have several contingency resource/QoS requirements.
Let us consider that the QoS offered to each service‐class belongs to one out of alternative QoS levels, which depend on the occupied cell resources. In what follows, a service‐class call of QoS level is referred to as service‐class call. A service‐class call is characterized by the following QoS parameters: (i) , transmission bit rate, (ii) , mean service time (exponentially distributed), and (iii) , BER parameter.
The application of the CDTM for the call‐level performance evaluation of WCDMA networks is necessary when assuming that a WCDMA cell accommodates not only stream service‐classes but also elastic service‐classes, which are associated with individual sets of thresholds (indicating the occupied cell resources). A variation of an elastic service‐class is an adaptive service‐class, in which calls may reduce their resources/bandwidth, but their service time is kept fixed. We can therefore consider three types of service‐classes:
Upon their arrival, elastic or adaptive calls select one resource requirement according to an associated threshold scheme; a resource requirement is not altered during the service‐time. For example, a QoS level can be assigned to an elastic service‐class call at the arrival time and is based on the occupied system resources (cell load ), which is indicated through thresholds. The thresholds of an elastic service‐class are denoted by . The QoS level assignment is performed as follows. If , then the elastic call is assigned the first QoS level and occupies system resources for an exponentially distributed service time with mean . The symbol comes from the load factor (see 2.78). If , then the call is assigned to the second QoS level and occupies resources for an exponentially distributed service‐time with mean , and so on. Finally, if , then the call is assigned to the QoS level and occupies resources for an exponentially distributed service time with mean . We assume that an elastic call has a certain amount of data to transmit. Therefore, a call's service time should be conversely proportional to the allocated resources. For this reason, the mean call service times, , are chosen so that the product remains constant for every QoS level . As far as the offered traffic‐load of service‐class calls is concerned, it is defined as .
We assume perfect power control, i.e., at the BS, the same amount of power, , is received from each service‐class call. Since in WCDMA systems all users transmit within the same frequency band, a single user sees the signals generated by all other users as interference. Intra‐cell interference, , is caused by users of the cell and inter‐cell interference, , is caused by users of the neighbouring cells. An amount of power is due to thermal noise in the cell and corresponds to the intra‐cell interference when the cell is empty.
The CAC is performed by measuring the noise rise, , which is defined as the ratio of the total received power at the BS, , to the thermal noise power, :
When a new call arrives, the CAC estimates the noise rise and if it exceeds a maximum value, , the new call is blocked and lost.
The cell load, , is defined as the ratio of the received power from all active users to the total received power:
From (2.75) and (2.76), the relation between the noise rise and the cell load is:
The maximum value of the cell load, , is the cell load which corresponds to the maximum noise rise, 2: .
The resource/bandwidth requirement of a service‐class call is expressed by the load factor, [10]:
where is the chip rate of the WCDMA carrier.
The cell load can be written as the sum of the intra‐cell load, (cell load derived from the active users of the reference cell), and the inter‐cell load, (cell load derived from the active users of the neighbouring cells), i.e., . The values of and are given by 2.79 and 2.80, respectively:
where is the number of active users of service‐class , while
For a new service‐class call acceptance, the following condition must hold in the BS:
That is, an arriving call with resource requirement is accepted in the cell if and only if, after its acceptance, the cell load remains below .
Due to (2.81), the probability that a new service‐class call is blocked when arriving at an instant with intra‐cell load, , is called the local blocking probability (LBP), , and can be calculated by (based on ( 2.78)–( 2.80)):
In ( 2.80), the can be modelled as a lognormal random variable (with parameters mean and variance ), which is independent of the intra‐cell interference. Hence, the mean, , and the variance, , of are calculated by:
Consequently, because of ( 2.80), the inter‐cell load, , will also be a lognormal random variable. Its mean, , and variance, , are calculated as follows:
where the parameters and can be determined by solving (2.85) and (2.86):
where is the coefficient of variation.
Thus, (2.82) can be rewritten as:
The RHS of (2.89), is the cumulative distribution function (CDF) of . It is denoted by and can be calculated from:
where is the well‐known error function.
Hence, if we substitute into (2.90), from ( 2.89) we can calculate the LBP of service‐class calls as follows:
To apply the CDTM in WCDMA systems, parameters' discretization is required. It is achieved by the introduction of a basic cell load unit (e.g., granularity of , used in Example 2.23). The CDTM parameters of system capacity, the total number of occupied b.u. in the system, the assigned number of b.u. to an in‐service call, and a bandwidth threshold are obtained by discretizing the cell load, the maximum cell load, the load factor, and the resource threshold, respectively:
The user activity is described by the activity factor, , which represents the fraction of the active period of a service‐class call/user over the entire service time (). In the CDTM, we consider that calls are active during the entire service time and we do not distinguish active users from passive users. However, in WCDMA systems it is essential to consider such a distinction because passive users do not consume any system resources. Hence, a system state does not represent the total number of occupied b.u. Instead, it represents the total number of b.u. that would be occupied if all (mobile) users were active. Let denote the total number of occupied b.u. at an instant. In the CDTM, is always equal to , while in WCDMA networks we have . When all users are passive, , while when all users are active.
The bandwidth occupancy, , is defined as the conditional probability that b.u. are occupied in state and, for user activity , it can be calculated recursively by:
where is the highest reachable system state, for , and is called resource/bandwidth share and denotes the proportion of the total occupied resources, , from service‐class calls (see (2.95)).
In WCDMA systems, due to the intra‐/inter‐cell interference, blocking of a service‐class call may occur at any state with a probability . This probability, called the local blocking factor (LBF), is calculated by summing over the LBP multiplied by the corresponding bandwidth occupancies:
where for use (2.91) with . Note that when , (since in this case and ).
The service‐class bandwidth share in state (requiring b.u.) is derived assuming LB between adjacent systems states, while incorporating the LBF and the parameter delta (indicating the upward migration and migration approximations):
where , while for :
In Figure 2.25 we show how we can recursively determine the bandwidth occupancy (2.93). Consider a system with service‐classes and a single QoS level per service‐class (i.e., ), while b.u. A dashed line shows the arrival of a passive user, while a solid line represents the arrival of an active user. Starting from state , four possibilities exist:
Then, is determined from and :
.
Thanks to discretization, we can continue presenting a WCDMA cell in terms of the CDTM. Let us consider a link of capacity b.u. accommodating service‐classes. Calls of service‐class 1 require 1 b.u. without any threshold. Service‐class 2 has one threshold, , and two contingency bandwidth requirements, and , while service‐class 3 has two thresholds, and , and three contingency bandwidth requirements, , and . In this specific example, a call is blocked and lost whenever the link bandwidth is fully occupied because the minimum bandwidth per call requirement of all three service‐classes is 1. If we apply this threshold scheme to a WCDMA system, due to the existence of local blocking, there are no pure blocking and non‐blocking states, but blocking of a service‐class call may occur in any state with probability (LBF). In Figure 2.26 we show the (macro‐) state transition diagram of this example for service‐class 2. Observe that in the Markov chain of this system, due to the local blocking, the transition rates from lower states to higher are reduced by the factor . A more important difference is that the system state can exceed . The maximum value of is denoted by and is the state at which approach 1. In other words, the higher states are unreachable due to severe local blocking. This fact shows that WCDMA systems may have no hard limit on the system capacity and therefore we talk about soft capacity. The Markov chain of Figure 2.26 does not have a PFS (all arrows are valid, ignore the Xs on the arrows for the moment) due to the existence of different contingency bandwidth requirements (as in the CDTM) and the local blocking; they both destroy the local balance between adjacent system states.
For LB, the Markov chain must be transformed to a reversible Markov chain (represented in Figure 2.26 when ignoring the arrows bearing an X) by taking into account the migration and upward migration approximation (Figure 2.27).
The state probabilities are given by:
for and for , with .
The CBP of service‐class can be calculated by adding all the state probabilities multiplied by the corresponding LBFs:
Due to the contingency bandwidth requirements, , we need also to sum over in specific areas defined by thresholds. This is done with the aid of the parameter gamma:
A WCDMA cell of , with mW, suffering mW and , supports elastic service‐classes having kbps, and or erl. Table 2.11 contains the CBP results.
Table 2.11 Various parameters and CBP results of Example 2.23.
Service‐class 1 | Service‐class 2 | |||
Activity factor | 1 | 0.7 | ||
4 dB | 3 dB | |||
Traffic load | 4 erl | 8 erl | 1 erl | 2 erl |
CBP (EMLM) | 0.9052% | 5.1663% | 1.1131% | 6.8848% |
CBP (CDTM) | 0.9% | 4.5441% | 1.0978% | 5.9980% |
Extensions of the retry or thresholds models are categorized in wired [11–18], wireless [19–21], and optical networks [22]. In [ 11], the threshold models are extended to include BPP traffic. The CBP calculations are based either on recursive formulas or on convolution algorithms. In [12] and [13], the single threshold of the STM is replaced by two thresholds. When a new call finds the occupied link bandwidth above a threshold, it can be accepted in the link with its lower bandwidth requirement (similar to the STM). When the occupied link bandwidth becomes less than the second threshold then an in‐service call (accepted with its lower bandwidth requirement) can increase its bandwidth to its peak‐bandwidth requirement. In [14] and [15], the CDTM is extended to allow call bandwidth compression/expansion of in‐service calls with [ 15] or without [ 14] the existence of the BR policy (more on the subject of bandwidth compression/expansion and Poisson arriving calls can be found in Chapters and ). In [16– 18], a variant of the SRM/STM is proposed. Specifically, some service‐classes are characterized cooperative and the rest non‐cooperative. Users from a cooperative service‐class can retry with a certain probability to be connected in the system with reduced bandwidth when blocked with their initial peak‐bandwidth and the total occupied bandwidth of the system is below a threshold. This behavior increases the QoS perceived by other users. In [ 19], the threshold models are extended to include the CBP calculation in the uplink of a UMTS network. To this end, the notion of local (soft) blocking is incorporated in the model. The latter means that a call may be blocked in any state of the system if its acceptance violates the QoS, in terms of noise, of all in‐service calls (see also [23–26]). In [20], the threshold models are extended for the call‐level analysis of the Iub interface in UMTS networks. In [ 21], a multi‐threshold teletraffic model for heterogeneous CDMA networks is proposed. The model enables QoS differentiation of handover traffic when elastic and adaptive service‐classes are present. Furthermore, an applicability framework is proposed that takes into account advances in Cloud‐RAN and self‐organizing network (SON) technologies. In [ 22], the CDTM is extended for the calculation of connection failure probabilities (due to unavailability of a wavelength) and CBP (due to the restricted bandwidth capacity of a wavelength) in hybrid TDM‐WDM PONs with DWA.