Skip to main content
Erschienen in: EURASIP Journal on Wireless Communications and Networking 1/2009

Open Access 01.12.2009 | Research Article

Fairness and QoS Guarantees of WiMAX OFDMA Scheduling with Fuzzy Controls

verfasst von: Chao-Lieh Chen, Jeng-Wei Lee, Chi-Yuan Wu, Yau-Hwang Kuo

Erschienen in: EURASIP Journal on Wireless Communications and Networking | Ausgabe 1/2009

Aktivieren Sie unsere intelligente Suche um passende Fachinhalte oder Patente zu finden.

search-config
loading …

Abstract

A fairness and QoS guaranteed scheduling approach with fuzzy controls (FQFCs) is proposed for WiMAX OFDMA systems. The controllers, respectively, adjust priority and transmission opportunity (TXOP) for each WiMAX connection according to QoS requirements and service classes. The FQFC provides intra- and interclass fairness guarantees by making connections within the same class achieve equal degree of QoS while at the same time making those without QoS requirements equally share the remaining resources. Even in dynamic environments such as mobile WiMAX networks with time-variant traffic specifications, the FQFC fairly guarantees delay, throughput, and jitter, which are seldom achieved at the same time by state-of-the-art solutions.

1. Introduction

IEEE 802.16 standard (WiMAX) [1, 2] is one of the most popular standards for fixed and mobile broadband wireless access systems to provide last mile access. Due to various users with diverse QoS requirements and wireless communication technologies, the resource scheduler plays an important role to provide fairness and QoS guarantees. As summarized in [3], a resource scheduler in wireless multimedia networks needs to possess the following features: efficient link utilization, delay bound, low implementation complexity, throughput, scalability, and fairness.
For WiMAX and OFDMA systems, various scheduling algorithms have been proposed for achieving QoS guarantees. For example, Liu et al. [4] proposed a priority-based scheduler which assigns each connection a priority updated according to QoS parameters and channel state and then assigns time slots to connections according to the order of priority values. The method has low implementation complexity because the scheduler simply updates the priority of each connection per frame and allocates time slots to the connection with the highest priority. However, it does not consider fairness and jitter issues which are important metrics for real-time applications. To maintain low implementation complexity under considering fairness and jitter, we use the priority-based scheduling scheme for initial priority assignment and afterward, the proposed a fairness and QoS guaranteed scheduling approach with fuzzy controls (FQFC) mechanism takes care of the scheduling job using fuzzy control approach. Many algorithms have been proposed to deal with the fairness problem, and can be briefly divided into two categories. The first category is to reduce the resource allocation problem into an optimization problem. Based on the optimization theory, for example, [5, 6] have good performance on spectrum efficiency and system utilization. They formulate the cross-layer optimization problem to maximize the average utility of all active users subject to certain constraints. However, in addition to implementation complexity, these methods still suffer some problems. To achieve optimal spectrum efficiency, the optimization approaches may, on the other hand, fail to provide QoS guarantees. Moreover, the relation between traffic specifications and network state is uncertain. Uncertainty and dynamics in mobile environment make exact modeling of objective function and constraints impossible when performing the optimization steps. In this paper, the FQFC adopts fuzzy control technique to deal with the modeling problem. The reason we use fuzzy control is to tackle uncertainty and dynamics in wireless communication environment. Among soft computing methods, inference based on probability theory is also widely used for modeling uncertainty and dynamics. However, the controller based on probability must rely on statistical observations to perform inference. Correctness of statistical information is based on the law of large number. In case that gathering large amount of statistic information in short time is difficult, it will be infeasible. Moreover, inference based on probability usually assumes some specific probability model for result of feedback observation to follow. As shown in [7], a single model usually fails to represent the behaviors of dynamic environments such as mobile wireless networks with sudden bursts or changes.
The second category is a utility-based scheduler. A utility function is a measure of relative satisfaction from users' requirements. The schemes in [8, 9] apply utility functions to maximize the total utility of all connections. Utility-based optimization approaches did guarantee QoS of some connections but also starve others. On the other hand, some approaches such as [10, 11] propose utility-fair bandwidth adaptation schemes for multiclass traffic in wireless networks. Rather than achieving resource fairness, the bandwidth adaptation schemes make sure that all connections can obtain similar utility values to achieve the so-called utility fairness. These schemes are effective in both achieving utility fairness and increasing network resource utilization. However, the utility-fair schemes may fail to provide QoS guarantees since it does not consider the priority of the connections.
In this paper, our objective is to provide efficient control for both QoS and fairness guarantees of WiMAX OFDMA scheduling. For QoS guarantees, we address the problem of head-of-line (HOL) delay and jitter control for real time applications and throughput control for nonreal-time applications. The FQFC scheduler assigns each connection a priority and TXOP, and adjusts them according to channel quality, QoS requirements, and service classes. Due to uncertainty and dynamics of the environment, it is difficult to find out the mapping between priority and QoS requirements. For fuzzy inference, it is the simplest way to model a complex system when there is few and uncertain information available. In the field of controller design, fuzzy controller is one of the most popular approaches. Moreover, fuzzy control has been widely used in researches on communication networks such as [7, 1217]. However, there are few articles talking about using fuzzy control for WiMAX. In this paper, the FQFC model is developed for WiMAX OFDMA systems and is proved that both fairness and QoS are guaranteed. Other fuzzy control methods [1417] may be proved to achieve certain degree of QoS. However, fairness is seldom assured in these and state-of-the-art approaches. Then, we define two types of fairness including intraclass and interclass fairness. To achieve intraclass fairness, we set up a reference goal to each connection according to the QoS requirements, and make the connections achieve the goal by priority scheduling and TXOP allocation. If each connection can achieve its QoS requirement, intraclass fairness is guaranteed. For achieving interclass fairness, the FQFC does not allocate superfluous resources out of what required. Compared to state-of-the-art methods, connections of high-priority classes release more resources to lower priority ones. Thus, the FQFC makes the connections without QoS requirements evenly share the remaining resources. Based on the priority scheduling and TXOP allocation methods, the FQFC provides both intraclass and interclass fairness with QoS guarantees and featuring low implementation complexity.
This paper is organized as follows. In Section 2, we introduce background including network configuration, MAC QoS, PHY resource allocation, and fairness descriptions. Section 3 describes the FQFC mechanism and depicts the design of the fuzzy controllers for each service class. In Section 4, we investigate the mechanism performance of QoS and fairness through simulations. Finally, we conclude the paper in Section 5.

2. Background

2.1. Network Configuration

WiMAX specifies two communication modes which form different topologies—point-to-multipoint (PMP) and mesh modes. In PMP mode, a base station (BS) centrally allocates downlink (from BS to SS) and uplink (from SS to BS) resources to subscriber stations (SSs). All SSs are only allowed to communicate with a BS. In mesh mode, SS can act as a router to assist its neighbor to relay data. In the 802.16 standard, this mode is optional and is not discussed in this paper. Hence, we focus on proposing a downlink scheduling algorithm to provide QoS guarantees in PMP mode.
IEEE 802.16 WiMAX PHY adopts the orthogonal frequency-division multiple access (OFDMA) technology based on OFDM modulation. The OFDMA technology allows multiple users transmitting packets at the same OFDMA symbol via different subchannels, such that wireless resources are utilized ultimately.

2.2. Scheduling Services in MAC Layer

IEEE 802.16 MAC protocol is connection-oriented; each connection is assigned a connection ID (CID) and a single scheduling service determined by a set of QoS parameters. Four scheduling services in the 802.16 standard are supported: unsolicited grant service (UGS), real-time polling service (rtPS), nonreal-time polling service (nrtPS), and best effort (BE). The UGS supports real-time constant bitrate data streams, such as voice over IP (VoIP) without silence suppression. The QoS parameters of UGS service are minimum reserved traffic rate, the tolerated jitter, maximum latency, and request/transmission policy. The rtPS supports real-time variable-rate data streams, such as MPEG video or VoIP with silence suppression. The QoS parameters of rtPS are maximum latency, request/transmission policy, minimum reserved traffic rate, and traffic priority. The nrtPS supports delay-tolerant variable-rate data streams, such as FTP. The QoS parameters of nrtPS are minimum reserved traffic rate, request/transmission policy, and traffic priority. The BE supports best-effort data streams. The QoS parameter is request/transmission policy. In IEEE 802.16e [2], an additional service class called extended real-time polling service (ertPS) has superior efficiency than both UGS and rtPS. It supports real-time variable-rate data streams, such as VoIP with silence suppression. The QoS parameters of ertPS are minimum reserved traffic rate, maximum latency, request/transmission policy, and the tolerated jitter. Hence, considering the QoS requirements of the four class services, we calculate the reference goal as traffic specification (TSPEC) according to these QoS parameters.

2.3. Resource Allocations in PHY Layer

IEEE 802.16 OFDMA system defines two types of subcarrier permutations, distributed subcarrier permutation and adjacent subcarrier permutation. The former permutation type includes partially and fully used subcarriers (PUSC and FUSC) which are pseudo-randomly selected and grouped into subchannels, while the later includes adaptive modulation and coding (AMC), and only adjacent subcarriers are clustered to form subchannels. Dispersing noise and interference in fast changing environment, the PUSC and FUSC modes are suitable for mobile networks. For AMC mode, the BS allocates appropriate subchannels for connections with larger SNR to enhance system performance, and it is suitable for fixed or low mobility environment. To support mobile WiMAX, the FQFC scheduling and allocation are based on distributed subcarrier permutation.
In OFDMA, the basic allocation unit is a slot that composes of one subchannel along with an OFDMA symbol, such that the resource allocation becomes a two-dimensional problem. By using the distributed subcarrier permutation, all subchannels are the so-called equally adequate for all SSs [18], and our resource allocation is based on Raster algorithm [18], in which the frame is filled row by row, from left to right and from top to bottom, and efficiently reduces the burst numbers.

2.4. Fairness

In wireless networks, the fairness definition is not straightforward. As described in [19], a fair resource allocation usually does not produce equal connection data rate because the diverse connections also suffer from diverse channel conditions, network states, and dynamics. The dynamics result from mobility and time-variant traffic specifications (TSPECs). Moreover, WiMAX needs to provide QoS guarantees for four classes of scheduling services. Therefore, for fairness, it is necessary to consider QoS guarantees for different class connections. We define two types of fairness described as follows.
(i)
Intraclass fairness: the connections within the same class achieve equal degree of QoS.
 
(ii)
Interclass fairness: the connections with QoS requirements achieve exactly their demands, and those without QoS requirements equally share the remaining resources.
 
Hence, our objective is to achieve both intraclass and interclass fairness.

2.5. Fuzzy Controller

Classical controller requires modeling of the physical reality. This is significant in control problems; however, it is difficult or even impossible to construct precise mathematical models. The difficulty may result from time-variant system behaviors, dynamics, and uncertainty in mobile wireless communication environment. Fuzzy controllers perform well under these circumstances. A general fuzzy controller consists of four components: a fuzzifier, a fuzzy rule base, a fuzzy inference engine, and a defuzzifier. The interconnections among these components and the controlled process are shown in Figure 1. The fuzzifier maps crisp input into appropriate fuzzy sets to express uncertainties. The fuzzy inference engine uses the fuzzified measurements to evaluate the fuzzy implication results. Finally, the defuzzifier deals with confliction of fuzzy implications and transforms the fuzzy implication results back to the crisp output. Two conditions are usually monitored by the controller: error https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq1_HTML.gif and the derivative of the error https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq2_HTML.gif . With https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq3_HTML.gif and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq4_HTML.gif , the fuzzy controller issues control actions.

3. Design of the Proposed Scheduling Mechanism

In this section, we describe the scheduling mechanism for multiple connections with various QoS requirements. The FQFC scheduler assigns two variables with fuzzy inference values for each connection with CID https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq5_HTML.gif , that is, the priority https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq6_HTML.gif and the maximum number of packets https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq7_HTML.gif that connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq8_HTML.gif can transmit in a frame duration. The FQFC scheduler first initializes the two variables based on the characteristics of connections and adjusts them, respectively, by two fuzzy controllers to adapt to the dynamics of system. As shown in Figure 2, the priority controller adjusts https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq9_HTML.gif according to channel quality, QoS requirements, and service classes. With the priority, the FQFC decides the transmission order of connections. The TXOP controller adapts https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq10_HTML.gif according to transmission rate and the queue length difference between two contiguous transmissions of the MAC layer.

3.1. Controller Design for ertPS & rtPS

Unlike the UGS class having the highest priority that constant bandwidth can be achieved by allocating fixed number of slots [1], the two service classes, rtPS and ertPS, that both support the real-time variable bit-rate data streaming require efficient and effective control to achieve QoS guarantees and fairness. A real-time connection of these two classes usually has two QoS specifications, maximum allowable latency (deadline) and jitter. The FQFC control for real-time connections comprises three steps: (1) set up goal delay and tolerable range, (2) adjust priority according to recent HOL delay, and (3) adjust TXOP according to the jitter requirement. The main idea is that the FQFC maintains the delay and jitter of each connection below the delay and jitter goals, respectively. First, we set the goal delay and the tolerable range. Figure 3 shows the control mechanism for real-time connections. Goal delay controller determines goal delay and tolerable range bounded by the lower and upper bounds. Then, the priority controller decides transmission order of connections, and the TXOP controller decides the number of transmitted packets to maintain the jitter. We describe the design of the three controllers as follows.

3.1.1. Goal Delay Controller

The purpose of the goal delay controller is to control delay and jitter within a tolerable range. If the delay exceeds the tolerable range, the FQFC increases the priority. If the delay is below the tolerable range, the FQFC decreases the priority. As shown in Figure 2, to avoid packet dropping, the goal delay is below the deadline. Since system load and transmission rate affect HOL delay obviously, we use them to decide the goal delay. Due to uncertainty and that the TSPEC changes rapidly in mobile WiMAX environment, we cannot use exact formulation to represent the goal delay. Therefore, we divide the delay space into three parts and use fuzzy sets S (small), M (medium), and L (large) to represent these three parts, respectively. Then, we decide which part that the goal delay belongs to according to the system load and transmission rate. The goal delay controller selects a goal delay and sets its upper and lower bounds to form a tolerable range for control. We denote https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq11_HTML.gif , https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq12_HTML.gif , and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq13_HTML.gif as the goal delay of connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq14_HTML.gif in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq15_HTML.gif th frame and its upper and lower bounds, respectively. The goal delay controller uses triangular and trapezoidal membership functions as shown in Figure 4. The fuzzy input variables are system load (SL) and transmission rate (TR), and the output function is the goal delay (GD). The fuzzy sets of SL, TR, and GD are defined as follows:
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq16_HTML.gif
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq17_HTML.gif
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq18_HTML.gif
According to system load, the controller decides the goal delay https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq19_HTML.gif by the following fuzzy rules.
(R1)
If system load is L, then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq20_HTML.gif is S.
 
(R2)
If system load is M, then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq21_HTML.gif is M.
 
(R3)
If system load is H, then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq22_HTML.gif is L.
 
The following controller uses normalized data rate with respect to the transmission rate in the highest modulation mode to decide the goal delay https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq23_HTML.gif .
(R1)
If transmission rate is F, then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq24_HTML.gif is S.
 
(R2)
If transmission rate is M, then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq25_HTML.gif is M.
 
(R3)
If transmission rate is S, then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq26_HTML.gif is L.
 
Using Mandamni implication and the centroid defuzzifier, we obtain the outputs, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq27_HTML.gif and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq28_HTML.gif . Considering system load and transmission rate, the final goal delay is
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ1_HTML.gif
(1)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq29_HTML.gif and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq30_HTML.gif are the weighting factors of system load and transmission rate, respectively.
With goal delay https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq31_HTML.gif and required jitter https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq32_HTML.gif , we define https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq33_HTML.gif and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq34_HTML.gif as the upper and lower bounds of the tolerable range, where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq35_HTML.gif and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq36_HTML.gif .

3.1.2. Priority Controller for Real Time Services

Figure 5 shows the control system including the priority controller, the WiMAX system plant, and the delay observer. The delay observer detects the HOL delay https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq37_HTML.gif . Then, the priority controller compares it with the delay requirement https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq38_HTML.gif , and adjusts priority https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq39_HTML.gif . If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq40_HTML.gif is around zero, the control system is stabilized around the requirement.
In our design, we denote negative, zero, and positive forces with fuzzy singletons S, M, and L. The control actions of these singletons at the conclusion parts of fuzzy rules are as follows:
S: https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq41_HTML.gif
M: https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq42_HTML.gif
L: https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq43_HTML.gif
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq44_HTML.gif is the priority influence of connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq45_HTML.gif in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq46_HTML.gif th frame. The priority controller must confirm that the HOL delay will not exceed the deadline. Hence, it adapts https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq47_HTML.gif according to the time duration between goal delay and the deadline. Let https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq48_HTML.gif be the deadline, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq49_HTML.gif be the guard time before the deadline, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq50_HTML.gif be the maximum priority of real-time connections, and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq51_HTML.gif be the frame duration. Then, we have
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ2_HTML.gif
(2)
As we can see in (2), when the goal delay is closer to the deadline, the adaptation force of the priority is larger. We depict the priority initialization and controlled direction as follows.
(a) Priority Setting. When the connection is in an initial stage or the HOL delay is below https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq52_HTML.gif , the priority controller assigns the connection a priority according to channel quality, QoS requirement, and service classes. For a real-time connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq53_HTML.gif , the priority https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq54_HTML.gif in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq55_HTML.gif th frame is assigned by (3) which was proposed in [4]:
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ3_HTML.gif
(3)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq56_HTML.gif is the maximum priority of real-time connections, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq57_HTML.gif is the data rate of connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq58_HTML.gif in the highest modulation mode, and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq59_HTML.gif is the data rate of connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq60_HTML.gif in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq61_HTML.gif th frame. https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq62_HTML.gif is the normalized data rate and the connection with high received SNR results in higher priority. https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq63_HTML.gif is the delay requirement indicator:
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ4_HTML.gif
(4)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq64_HTML.gif is the deadline, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq65_HTML.gif is the guard time before the deadline, and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq66_HTML.gif denotes the HOL delay. If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq67_HTML.gif , the larger https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq68_HTML.gif denotes the higher satisfaction of delay requirement, which causes lower priority. If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq69_HTML.gif , the HOL delay has been over the guard time of deadline. The connection should get resources immediately to avoid packet losses. Hence, the priority is set as https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq70_HTML.gif . When https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq71_HTML.gif is zero, the connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq72_HTML.gif is under deep fading and should not be scheduled.
(b) Priority Controller. Let the controller action be the priority https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq73_HTML.gif . One of the input https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq74_HTML.gif is the difference between the actual value of the observed HOL delay https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq75_HTML.gif and the desired value https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq76_HTML.gif , that is, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq77_HTML.gif . The universe of https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq78_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq79_HTML.gif . The variable https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq80_HTML.gif has three linguistic values N, E, and P which represent fuzzy concepts "Negative," "Equal," and "Positive," respectively. The fuzzy sets N, E, and P are characterized by the membership functions shown in Figure 6.
The other input of the controller is the difference between two errors, which is defined as https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq81_HTML.gif . Substituting https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq82_HTML.gif to https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq83_HTML.gif , we obtain https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq84_HTML.gif . The universe of https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq85_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq86_HTML.gif . The linguistic values of https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq87_HTML.gif , https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq88_HTML.gif , https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq89_HTML.gif , and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq90_HTML.gif also representing fuzzy concepts "Negative," "Equal," and "Positive," respectively, are characterized by the membership functions as shown in Figure 7, where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq91_HTML.gif and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq92_HTML.gif . Sign of these values constitutes four cases as shown in Figure 7. The membership functions are time-variant and change along with the variable https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq93_HTML.gif .
We consider four cases to design the fuzzy rule base as follows.
Case 1.
If HOL delay is too large, that is, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq96_HTML.gif , the priority should be increased with the large (L) step.
Case 2.
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq97_HTML.gif , maintaining priority at the median (M) level is fine.
Case 3.
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq98_HTML.gif , maintaining priority at the median (M) level is fine.
Case 4.
If HOL delay is too small, that is, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq99_HTML.gif , the priority should be decreased with negative decrement (S).
Therefore, expanding the above cases with changing rate https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq100_HTML.gif , we have the linguistic inference rules
(R1)
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq101_HTML.gif is P and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq102_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq103_HTML.gif , then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq104_HTML.gif is L,
 
(R2)
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq105_HTML.gif is P and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq106_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq107_HTML.gif , then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq108_HTML.gif is M,
 
(R3)
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq109_HTML.gif is P and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq110_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq111_HTML.gif , then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq112_HTML.gif is M,
 
(R4)
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq113_HTML.gif is E and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq114_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq115_HTML.gif , then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq116_HTML.gif is M,
 
(R5)
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq117_HTML.gif is E and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq118_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq119_HTML.gif , then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq120_HTML.gif is M,
 
(R6)
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq121_HTML.gif is E and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq122_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq123_HTML.gif , then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq124_HTML.gif is M,
 
(R7)
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq125_HTML.gif is N and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq126_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq127_HTML.gif , then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq128_HTML.gif is M,
 
(R8)
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq129_HTML.gif is N and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq130_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq131_HTML.gif , then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq132_HTML.gif is M,
 
(R9)
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq133_HTML.gif is N and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq134_HTML.gif is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq135_HTML.gif , then https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq136_HTML.gif is S.
 
Using Mandamni implication and the centroid defuzzifier, we obtain the control action responding each HOL delay https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq137_HTML.gif .
The priority controller makes the delay fall in the tolerable range which is below the deadline. Hence, each connection in the real-time class achieves the QoS specification, while intraclass fairness is guaranteed. When the delay is below the tolerable range, the controller decreases the priority for releasing the resources. This scheme guarantees the jitter and interclass fairness at the same time.
(c) Priority Adaptation for Fairness. For making the connections within the same class achieve equal degree of QoS, the priority controller adapts https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq138_HTML.gif by further considering the packet loss rate. All connections should receive the same packet loss rate. To compensate the packet losses in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq139_HTML.gif th frame, we define the loss rate as https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq140_HTML.gif and the scaling by
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ5_HTML.gif
(5)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq141_HTML.gif is a constant to normalize the loss rate according to the predefined precision. According to (5), if the connection drops packets due to out of the deadline, the priority controller allocates more resources by increasing the priority for achieving intraclass fairness. Even if all connections are in an extremely bad environment, they will suffer the same loss rate.

3.1.3. TXOP Controller

The TXOP controller initiates the TXOP based on frame duration https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq142_HTML.gif and packet interval of the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq143_HTML.gif th connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq144_HTML.gif as (6)
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ6_HTML.gif
(6)
According to deficit round robin [20], the TXOP increases as the number of packets in a queue increases. Let https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq145_HTML.gif denote the number of packets in queue https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq146_HTML.gif in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq147_HTML.gif th frame. The controller stores the bounded difference https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq148_HTML.gif in the deficit counter of connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq149_HTML.gif in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq150_HTML.gif th frame. Then, we add https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq151_HTML.gif to https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq152_HTML.gif as follows:
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ7_HTML.gif
(7)
To avoid burst transmission, TXOP has an upper bound in
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ8_HTML.gif
(8)

3.2. Controller Design for nrtPS

The nrtPS connection supports delay-tolerant variable-rate data streams and guarantees minimum reserved rate. The control mechanism for nrtPS connections can be divided into three steps: (1) setting up minimum reserved rate and an upper bound, (2) adjusting the priority according to average throughput of nrtPS connections and the required jitter of real-time connections, and (3) adjusting TXOP of nrtPS connections according to the required jitter. Figure 8 shows the control mechanism for nrtPS connection.
If the average throughput is lower than minimum reserved rate, the priority controller raises the priority to increase the throughput. Moreover, the controller needs to prevent large jitter from over-high priority. Besides, if the average throughput exceeds the upper bound, the controller decreases the priority to release the resource. We depict the controller design as follows.

3.2.1. Priority Controller

The priority controller in nrtPS class is easier than in the real-time class. The QoS requirement is only to guarantee the minimum reserved rate. Hence, we do not use fuzzy control and simply use the priority-based scheduler for nrtPS connections. Let https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq153_HTML.gif denote the average throughput of connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq154_HTML.gif in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq155_HTML.gif th frame, and let https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq156_HTML.gif denote the instantaneous data rate of connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq157_HTML.gif in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq158_HTML.gif th frame. The average throughput in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq159_HTML.gif th frame is usually estimated over a time constant https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq160_HTML.gif using moving average as
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ9_HTML.gif
(9)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq161_HTML.gif means connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq162_HTML.gif is scheduled in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq163_HTML.gif th frame.
For an nrtPS connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq164_HTML.gif , the priority https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq165_HTML.gif in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq166_HTML.gif th frame is defined as
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ10_HTML.gif
(10)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq167_HTML.gif is the priority decrement, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq168_HTML.gif is the maximum priority of nrtPS connection, and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq169_HTML.gif is the throughput requirement indicator which is the ratio of average throughput with respect to the minimum reserved rate https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq170_HTML.gif
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ11_HTML.gif
(11)
If https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq171_HTML.gif , the throughput requirement is satisfied, and the controller decreases the priority to release resource. When https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq172_HTML.gif implying that the average throughput is less than the minimum reserved rate, the connection should get more resources immediately to achieve the requirement. Hence, at this time, the priority is set to the maximum https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq173_HTML.gif . The priority decrement https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq174_HTML.gif is further defined as
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ12_HTML.gif
(12)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq175_HTML.gif is the packet length, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq176_HTML.gif is the upper bound of https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq177_HTML.gif which is the maximum sustained rate in the traffic specification, and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq178_HTML.gif is a constant representing system load.

3.2.2. TXOP Setting

For nrtPS, the FQFC sets https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq179_HTML.gif according to the throughput upper bound https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq180_HTML.gif as
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ13_HTML.gif
(13)

3.2.3. TXOP Adaptation for Fairness

For intraclass fairness, all nrtPS connections should have the same throughput ratio of average throughput with respect to minimum reserved rate. Via setting the upper bound https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq181_HTML.gif in (13), we control the average throughput within the range between the minimum reserved rate and the upper bound, and we make the throughput ratio of all nrtPS connections the same. For interclass fairness, the average throughput will not exceed the upper bound. Hence, we can release more resources to the connections without QoS requirements.

3.3. Controller Design for BE

3.3.1. Priority Setting

For a BE connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq182_HTML.gif , the priority https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq183_HTML.gif in the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq184_HTML.gif th frame is defined as
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ14_HTML.gif
(14)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq185_HTML.gif is the maximum priority of BE connection. All BE connections have the same priority. For intraclass fairness, we adopt the round robin scheduling for BE connections.

3.3.2. TXOP Setting

For fair resource allocation, the FQFC sets the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq186_HTML.gif according to the frame duration https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq187_HTML.gif and the packet interval of the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq188_HTML.gif th connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq189_HTML.gif as (14):
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ15_HTML.gif
(15)
In this paper, we also perform priority adaptation. Therefore, the overhead, especially the complexity, will be slightly higher than that of the priority-only method. Since in centralized PMP mode, all traffic flows are managed by base stations which have much more powerful computing ability than SSs, the additional computation overhead will not give any sensibly negative effect. Moreover, the proposed controllers do not use any control/management packets for fairness and QoS purposes. There is no additional network overhead caused by the proposed FQFC.

4. Evaluations and Simulation Results

We first introduce intraclass and interclass fairness criteria and then according to these criteria, we evaluate the performances of the fairness.

4.1. Fairness Criteria

The descriptions of fairness indices are as follows.

4.1.1. Intraclass Fairness Index

Intraclass fairness means that the connections within the same class achieve equal QoS guarantees. Because the connections in different service classes have different QoS requirements, we define respective intraclass fairness indices for real-time, nrtPS, and BE classes.
(a) Real-Time Connection. A connection belonging to the real-time class requires strict maximum allowable latency (deadline) and the tolerated jitter. Packet loss occurs when packet delay is out of the deadline. Hence, we use loss rate and jitter to evaluate the intraclass fairness of real-time connections. We define a real-time indicator https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq190_HTML.gif as
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ16_HTML.gif
(16)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq191_HTML.gif , https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq192_HTML.gif , and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq193_HTML.gif are the loss rate, jitter, and the tolerated jitter of connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq194_HTML.gif , respectively. If the jitter is larger than the tolerated jitter, the connection does not achieve QoS guarantees and we set the real-time indicator to one. Otherwise, we set the real-time indicator as the loss rate. Then, we utilize the real-time indicator to compute the real time fairness index. If the real-time indicators of all connections are closer to each other, the better intraclass fairness is achieved. We define the real-time fairness index https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq195_HTML.gif as the standard deviation of the real-time indicators of all rtPS connections as follows:
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ17_HTML.gif
(17)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq196_HTML.gif is the number of connections in the real time class, and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq197_HTML.gif is the average real-time indicator. Thus, a smaller value of https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq198_HTML.gif represents better intraclass fairness of the real-time class.
(b) nrtPS Connection. A connection belonging to the nrtPS class requires minimum reserved rate. Hence, we use the average throughput to evaluate the intraclass class fairness of nrtPS connections. We define a nrtPS indicator https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq199_HTML.gif as
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ18_HTML.gif
(18)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq200_HTML.gif and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq201_HTML.gif are the average throughput and minimum reserved rate of connection https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq202_HTML.gif , respectively. Then, we introduce the throughput indicator to compute the nrtPS fairness index. The nrtPS fairness index https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq203_HTML.gif is defined as the standard deviation of the throughput indicator of connections in the same nrtPS class as follows:
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ19_HTML.gif
(19)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq204_HTML.gif is the number of connections in nrtPS class, and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq205_HTML.gif is the average nrtPS indicator. Similar to the https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq206_HTML.gif , a smaller https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq207_HTML.gif value represents better intraclass fairness of the nrtPS class.
(c) BE Connection. A connection belonging to BE requires no QoS metrics. We introduce the average throughput to compute the BE fairness index. The BE fairness index is defined as the standard deviation of the average throughput of connections in the same BE class https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq208_HTML.gif as follows:
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ20_HTML.gif
(20)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq209_HTML.gif is the number of connections in BE class, and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq210_HTML.gif is the average throughput in the BE class. Smaller https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq211_HTML.gif represents better intraclass fairness of the BE class.

4.1.2. Interclass Fairness Index

According to the definition of interclass fairness, the interclass fairness has two folds: (1) the connections with QoS requirements achieve the demands; (2) the connections without QoS requirements equally share the remaining resources.
For the first fold, we introduce a requirement indicator https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq212_HTML.gif to show the degree of the connection close to the demands as
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ21_HTML.gif
(21)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq213_HTML.gif is a tunable parameter which determines the tolerable range. https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq214_HTML.gif and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq215_HTML.gif are the average state and the QoS goal of class https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq216_HTML.gif , respectively. In the real-time class, the average state is the mean loss rate, and its goal loss rate is zero. In the nrtPS class, the QoS parameter is the average throughput, and the goal is the minimum reserved rate. The smaller the difference between the average state and the QoS goal is, the larger requirement indicator is. When the mean allocated resources for a class are away from the requirement, no matter above or below the goal, the requirement indicator decreases. When the allocated resources reach the requirements exactly, not only the QoS is guaranteed but also the remaining resources are most preserved at the same time.
The BE class has no QoS requirement. For the second part, we introduce Jain's fairness index [21] as the BE fairness index:
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ22_HTML.gif
(22)
where https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq217_HTML.gif is the number of connections without QoS requirements. The index equals to one indicates perfect fairness in the class without QoS requirements. Then, we utilize the requirement indicator https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq218_HTML.gif and the BE fairness index https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq219_HTML.gif to define the interclass fairness index as follows:
https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_Equ23_HTML.gif
(23)
In (23), https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq220_HTML.gif is the number of classes with QoS requirements, and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq221_HTML.gif is the weighting factor of class https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq222_HTML.gif , which determines the importance of the class. https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq223_HTML.gif and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq224_HTML.gif are the weighting factors of the classes with and without QoS requirements, respectively. In contrast to the indices of intraclass fairness, a larger https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq225_HTML.gif value indicates better interclass fairness.

4.2. Simulation Configuration

The parameters used in this simulation are listed in Table 1, where OFDM FFT size represents the number of subcarriers an OFDMA symbol composes. The packet length is 1024 bits, and the maximum priority of each service class is https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq226_HTML.gif and https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq227_HTML.gif , and for best effort, https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq228_HTML.gif . The weighting factors https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq229_HTML.gif , https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq230_HTML.gif , https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq231_HTML.gif in (23) are all 0.5. Each connection uses a fixed modulation. The FQFC allocates fixed number of time slots to UGS connections. The FQFC adopts persistent resource allocation [1, 22, 23] for UGS service because it has the highest priority. We focus on the performance of real-time, nrtPS, and BE connections. Besides, in our survey, the priority-based scheduler was proposed only for WiMAX OFDM PHY [4]. FQFC outperforms many state-of-the art schedulers for WiMAX OFDM PHY. To present the improvement by FQFC, we modify the priority-based scheduler in [4] to work with WiMAX OFDMA PHY by using the Raster algorithm and regard it as the priority-only scheduler. Then, FQFC fuzzy controllers further improve the fairness and QoS performance of the priority-only scheduler. There are four simulation scenarios as follows.
Table 1
Simulation parameters.
Parameter
Value
System bandwidth
10 MHz
Frame duration
5 ms
OFDMA FFT size
1024
Number of subchannels
30
Number of OFDMA symbols for DL
28
(i)
Scenario 1. We set 20 real-time connections. The QoS requirements of real-time connection are the loss rate, deadline, and required jitter. The traffic rates of connections are 8 connections in 1 Mbps, 10 connections in 500 kbps, and 2 connections in 250 kbps. This scenario is to verify the guarantees of maximum latency, the tolerated jitter, and the intraclass fairness in real-time class. It is difficult to find out the mapping between priority and QoS requirements. We prove that the FQFC can efficiently control the delay.
 
(ii)
Scenario 2. We set 10 real-time connections and 10 nrtPS connections. The QoS parameter of nrtPS connection is the minimum reserved rate. The traffic rates are 2 real-time connections in 1 Mbps, 8 real-time connections in 500 kbps, 5 nrtPS connections in 1 Mbps, and 5 nrtPS connections in 500 kbps. This scenario is to verify the guarantees of minimum reserved rate and fair resource allocation of the FQFC scheme.
 
(iii)
Scenario 3. We set 10 real-time connections, 10 nrtPS connections, and 10 BE connections. BE connection has no QoS requirement. The traffic rates are 1 real-time connection in 1 Mbps, 9 real-time connections in 500 kbps, 3 nrtPS connections in 750 kbps, 2 nrtPS connections in 500 kbps, 5 nrtPS connections in 1 Mbps, and 10 BE connections in 100 kbps. This scenario is to verify the fair resource allocation of FQFC.
 
(iv)
Scenario 4. In this scenario, we simulate the wireless link degrades. This will cause the modulation to change. The experiment is designed to test the robustness of the FQFC whether it can efficiently track the goal delay when the channel quality degrades. The simulated network consists of 1 BS and 10 SS (numbered from 1 to 10). In the downlink, each SS with number https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq232_HTML.gif has 1 real-time, 1 nrtPS, and 1 BE connection with CID https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq233_HTML.gif , https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq234_HTML.gif , https://static-content.springer.com/image/art%3A10.1155%2F2009%2F512507/MediaObjects/13638_2008_Article_1684_IEq235_HTML.gif , respectively. The connections from SS1 to SS5 apply with QPSK modulation, and connections from SS6 to SS7 apply with 16-QAM modulation. All the other connections initially adopt 64-QAM modulation. This is for simulating the different channel conditions.
 

4.3. Performance Evaluation for Fairness and QoS Guarantees

4.3.1. Scenario 1: Intraclass Fairness and QoS Guarantees of Real Time Connections

We compare the FQFC with the priority-only scheduler [4]. The QoS is in terms of average delay, delay jitter, and packet loss rate. As illustrated in Figure 9, although the priority-only scheduler controls delay of connection to be below the deadline, it cannot guarantee tolerant jitter. Under the same simulation conditions, FQFC guarantees both delay and jitter requirements as shown in Figure 10. The average delay is close to the goal delay. The result also shows that it is useful by controlling the HOL delay in the tolerable range to guarantee the required jitter.
For intraclass fairness evaluation, from Figure 10, we can see that the jitter of the connections using FQFC is still smaller than the tolerated jitter in Figure 9. Figure 11 shows the delay outage probabilities of the FQFC and the priority-only scheduler. The FQFC disperses the outage probability for intraclass fairness. Moreover, as summarized in Table 2, the intraclass fairness index of the FQFC is much lower than the one of the priority-only scheduler and is almost near to zero. Hence, the FQFC guarantees the intraclass fairness for real-time connections.
Table 2
Intraclass fairness index.
  
FQFC
Priority-only
Scenario 1
Real-time
0.000131
0.504639
Scenario 2
Real-time
0
0.489360
 
nrtPS
0.012748
0.081995
Scenario 3
Real-time
0
0.502625
 
nrtPS
0.003088
0.107002
 
BE
6.686637
84.312975

4.3.2. Scenario 2: Intraclass Fairness and QoS Guarantees of Real-Time and nrtPS Connections

For QoS evaluation, we introduce the throughput indicator defined as the ratio of the average throughput with respect to the minimum reserved rate. In Figures 12 and 13, even adding nrtPS connections, the FQFC still guarantees the delay and jitter specifications of real-time connections. Then, we evaluate nrtPS connections by throughput indicators. Figure 14 shows that all nrtPS connections with FQFC control keep their throughput indicators almost the same about 1.15. The result means that the FQFC guarantees minimum reserved rate. For the connections with priority-only-based scheduler [4], the throughput indicators of the last four nrtPS connections are higher than the others since priority-only-based scheduler provides more resources to the connections using high-bitrate modulation. The FQFC focuses on making the connections of the same class achieve the equal degree of QoS. As illustrated in Table 2, for nrtPS, the intraclass fairness index of the FQFC is close to zero which is much lower than the one of the priority-only scheduler. Hence, the FQFC also guarantees the intraclass fairness for the connections of the nrtPS class.

4.3.3. Scenario 3: Intra-and Interclass Fairness and QoS Guarantees of All Classes

For QoS evaluation, Figures 15, 16, and 17 show that the FQFC guarantees the delay and jitter of real-time connections as well as guarantees the throughput of nrtPS connections. Even for users with diverse QoS requirements, the FQFC still provides QoS guarantees. For BE connections, although they have no QoS requirement, the remnant resources should be fairly allocated to all BE connections. In Figure 18, BE connections under FQFC control obtain throughputs and are not starved.
For intraclass fairness evaluation of the BE class, we compare the FQFC with the priority-only scheduler regarding average throughput. Figure 18 shows that the average throughputs of all BE connections under the FQFC control are nearly the same. The priority-only scheduler provides more resource to the last four BE connections since they employ higher rate modulation. Table 2 shows that the intraclass fairness index of the FQFC is close to zero, which is much lower than the one of the priority-only scheduler. For every real-time connection, FQFC sets the goal delay below the deadline for a certain distance in terms of the tolerable jitter. Since the goal is for priority and TXOP controllers to follow, intraclass fairness is achieved when real-time connections have almost the same loss rate and jitter performances based on the intraclass fairness criteria. For nrtPS connections, the FQFC control algorithm maintains their ratios of throughput achievement over minimum reserved rate as close to 1 as possible. Again, as long as BE connections can evenly share the remained resources from real-time and nrtPS connections, intraclass fairness of BE connections is achieved. Hence, the FQFC guarantees the intraclass fairness for the BE classes.
For interclass fairness evaluation, in Figure 17, the throughput indicator of the FQFC is lower than the one of the priority-only scheduler since the FQFC always preserves resources for lower priority classes. This causes the BE connections get more resources. For interclass fairness comparison, the FQFC outperforms priority-only scheduler as shown in Figure 18. Table 3 shows that the interclass fairness index of the FQFC is close to one. Hence, in addition to intraclass fairness, the FQFC also guarantees the interclass fairness. For priority-only scheduler, every real-time connection grabs as many channel resources as possible. Though delays can be lower than the deadlines, delay and jitter differences among connections are not maintained. For nrtPS connections, the differences of throughput ratios are not controlled in priority-only scheduler. The differences of channel resources grasped by the BE connections are, therefore, obvious.
Table 3
Interclass fairness index.
 
FQFC
Priority-only
Scenario 3
0.994669
0.677405
In this scenario, we evaluate the robustness of the FQFC against wireless link degradation. At the 4.0th second, the wireless link from BS to SS3 degrades, and the PHY layer adaptation mechanism changes the modulation over this link from 64-QAM to QPSK. At the 6.0th second, this link recovers to 64-QAM. Figures 19 and 20, respectively, show the PDU delay of real-time connection 3 and the average throughput of nrtPS connections 13 in SS3, where the link degradation occurs at the 4.0th second. Figure 20 also shows the average throughput of nrtPS connection 13 which is an external connection out of SS3. Figure 21 shows the average throughput of BE connections 23 and 25. The simulation shows that
(i)
when the link degradation occurs, the FQFC adjusts the goal delay and the tolerable range according to the updated modulation. The FQFC continues to make the delay of real-time connection 3 fall in the tolerable range as shown in Figure 19. Hence, the FQFC can efficiently control the delay according to the goal delay and the tolerable range;
 
(ii)
the service curves of nrtPS connections 11 and 13 in Figure 20 distinguish a throughput drop from the 4.0th second to the 6.0th second, whereas FQFC still maintains the throughput to meet the QoS requirements. The service curves of BE connections 23 and 25 in Figure 21 also distinguish a throughput drop from the 4.0th second to the 6.0th second. The resources are released to guarantee the QoS of real-time connection 7 as shown in Figure 19. For intraclass fairness in nrtPS connections and BE connections, all nrtPS connections keep almost the same resource usage ratio. For interclass fairness, nrtPS and BE connections release resources to guarantee the QoS of real-time connections. Hence, the FQFC guarantees both QoS and fairness even in case that wireless link degrades.
 

5. Conclusions

A fairness and QoS guaranteed scheduling approach with fuzzy controls FQFC algorithm is proposed for WiMAX OFDMA systems. Different from the utility-fairness, new fairness and QoS evaluation criteria in terms of loss rate, jitter, and throughput are proposed for different classes. The proposed FQFC scheme controls the delay, jitter, and throughput QoS parameters efficiently providing both fairness and QoS guarantees. Rather than using hard computation approaches such as utility-based optimizations, we use fuzzy controller to perform scheduling and resource allocations to resolve mapping among priority, transmission opportunity, and QoS requirements. The proposed FQFC scheme provides both intra- and interclass fairness guarantees in addition to QoS guarantees while implementation is with low complexity.
Open AccessThis article is distributed under the terms of the Creative Commons Attribution 2.0 International License (https://​creativecommons.​org/​licenses/​by/​2.​0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.
Literatur
1.
Zurück zum Zitat IEEE Std. 802.16-2004 (Revision of IEEE Std. 802.16-2001) : IEEE standard for local and metropolitan area networks—part 16: air interface for fixed broadband wireless access systems. Revision of IEEE Std. 802.16-2001, October 2004 IEEE Std. 802.16-2004 (Revision of IEEE Std. 802.16-2001) : IEEE standard for local and metropolitan area networks—part 16: air interface for fixed broadband wireless access systems. Revision of IEEE Std. 802.16-2001, October 2004
2.
Zurück zum Zitat IEEE 802.16e-2005 : IEEE Standard for Local and metropolitan area networks—part 16: air interface for fixed and mobile broadband wireless access systems amendment 2: physical and medium access control layers for combined fixed and mobile operation in licensed bands and corrigendum. February 2006 IEEE 802.16e-2005 : IEEE Standard for Local and metropolitan area networks—part 16: air interface for fixed and mobile broadband wireless access systems amendment 2: physical and medium access control layers for combined fixed and mobile operation in licensed bands and corrigendum. February 2006
3.
Zurück zum Zitat Fattah H, Leung C: An overview of scheduling algorithms in wireless multimedia networks. IEEE Wireless Communications 2002, 9(5):76-83. 10.1109/MWC.2002.1043857CrossRef Fattah H, Leung C: An overview of scheduling algorithms in wireless multimedia networks. IEEE Wireless Communications 2002, 9(5):76-83. 10.1109/MWC.2002.1043857CrossRef
4.
Zurück zum Zitat Liu Q, Wang X, Giannakis GB: A cross-layer scheduling algorithm with QoS support in wireless networks. IEEE Transactions on Vehicular Technology 2006, 55(3):839-847. 10.1109/TVT.2006.873832CrossRef Liu Q, Wang X, Giannakis GB: A cross-layer scheduling algorithm with QoS support in wireless networks. IEEE Transactions on Vehicular Technology 2006, 55(3):839-847. 10.1109/TVT.2006.873832CrossRef
5.
Zurück zum Zitat Song G, Li Y: Cross-layer optimization for OFDM wireless networks—part I: theoretical framework. IEEE Transactions on Wireless Communications 2005, 4(2):614-624.MathSciNetCrossRef Song G, Li Y: Cross-layer optimization for OFDM wireless networks—part I: theoretical framework. IEEE Transactions on Wireless Communications 2005, 4(2):614-624.MathSciNetCrossRef
6.
Zurück zum Zitat Ergen M, Coleri S, Varaiya P: QoS aware adaptive resource allocation techniques for fair scheduling in OFDMA based broadband wireless access systems. IEEE Transactions on Broadcasting 2003, 49(4):362-370. 10.1109/TBC.2003.819051CrossRef Ergen M, Coleri S, Varaiya P: QoS aware adaptive resource allocation techniques for fair scheduling in OFDMA based broadband wireless access systems. IEEE Transactions on Broadcasting 2003, 49(4):362-370. 10.1109/TBC.2003.819051CrossRef
7.
Zurück zum Zitat Chen C-L, Lee J-W, Chen S-Y, Kuo Y-H: Hierarchical cross-layer fuzzy control for compromise of multiple objectives in wireless mobile networks. Proceedings of the International Conference on Mobile Technology, Applications, and Systems (Mobility '08), September 2008, Yilan, Taiwan 1-7. Chen C-L, Lee J-W, Chen S-Y, Kuo Y-H: Hierarchical cross-layer fuzzy control for compromise of multiple objectives in wireless mobile networks. Proceedings of the International Conference on Mobile Technology, Applications, and Systems (Mobility '08), September 2008, Yilan, Taiwan 1-7.
8.
Zurück zum Zitat Zheng D, Zhang J: A two-phase utility maximization framework for wireless medium access control. IEEE Transactions on Wireless Communications 2007, 6(12):4299-4307.CrossRef Zheng D, Zhang J: A two-phase utility maximization framework for wireless medium access control. IEEE Transactions on Wireless Communications 2007, 6(12):4299-4307.CrossRef
9.
Zurück zum Zitat Liu K-H, Cai L, Shen X: Multiclass utility-based scheduling for UWB networks. IEEE Transactions on Vehicular Technology 2008, 57(2):1176-1187.CrossRef Liu K-H, Cai L, Shen X: Multiclass utility-based scheduling for UWB networks. IEEE Transactions on Vehicular Technology 2008, 57(2):1176-1187.CrossRef
10.
Zurück zum Zitat Lu N, Bigham J, Nasser N: An intra-class and inter-class utility-fair bandwidth adaptation algorithm for multi-class traffic in wireless networks. Proceedings of the Asia-Pacific Conference on Communications (APCC '06), August-September 2006, Busan, Korea 1-5. Lu N, Bigham J, Nasser N: An intra-class and inter-class utility-fair bandwidth adaptation algorithm for multi-class traffic in wireless networks. Proceedings of the Asia-Pacific Conference on Communications (APCC '06), August-September 2006, Busan, Korea 1-5.
11.
Zurück zum Zitat Lu N, Bigham J: On utility-fair bandwidth adaptation for multi-class traffic QoS provisioning in wireless networks. Computer Networks 2007, 51(10):2554-2564. 10.1016/j.comnet.2006.11.012MATHCrossRef Lu N, Bigham J: On utility-fair bandwidth adaptation for multi-class traffic QoS provisioning in wireless networks. Computer Networks 2007, 51(10):2554-2564. 10.1016/j.comnet.2006.11.012MATHCrossRef
12.
Zurück zum Zitat Chen C-L: IEEE 802.11e EDCA QoS provisioning with dynamic fuzzy control and cross-layer interface. Proceedings of the 16th International Conference on Computer Communications and Networks (ICCCN '07), August 2007, Honolulu, Hawaii, USA 766-771. Chen C-L: IEEE 802.11e EDCA QoS provisioning with dynamic fuzzy control and cross-layer interface. Proceedings of the 16th International Conference on Computer Communications and Networks (ICCCN '07), August 2007, Honolulu, Hawaii, USA 766-771.
13.
Zurück zum Zitat Chen C-L: Morphisms from IEEE 802.11 DCF specifications to its EDCA QoS practice with cross-layer interface. Proceedings of the 13th International Conference on Parallel and Distributed Systems (ICPADS '07), December 2007, Hsinchu, Taiwan 2: 1-8. Chen C-L: Morphisms from IEEE 802.11 DCF specifications to its EDCA QoS practice with cross-layer interface. Proceedings of the 13th International Conference on Parallel and Distributed Systems (ICPADS '07), December 2007, Hsinchu, Taiwan 2: 1-8.
14.
Zurück zum Zitat Douligeris C, Develekos G: Neuro-fuzzy control in ATM networks. IEEE Communications Magazine 1997, 35(5):154-162. 10.1109/35.592110CrossRef Douligeris C, Develekos G: Neuro-fuzzy control in ATM networks. IEEE Communications Magazine 1997, 35(5):154-162. 10.1109/35.592110CrossRef
15.
Zurück zum Zitat Habib IW: Applications of neurocomputing in traffic management of ATM networks. Proceedings of the IEEE 1996, 84(10):1430-1441. 10.1109/5.537109CrossRef Habib IW: Applications of neurocomputing in traffic management of ATM networks. Proceedings of the IEEE 1996, 84(10):1430-1441. 10.1109/5.537109CrossRef
16.
Zurück zum Zitat Yang K, Zhang J, Chen H-H: A flexible QoS-aware service gateway for heterogeneous wireless networks. IEEE Network 2007, 21(2):6-12.CrossRef Yang K, Zhang J, Chen H-H: A flexible QoS-aware service gateway for heterogeneous wireless networks. IEEE Network 2007, 21(2):6-12.CrossRef
17.
Zurück zum Zitat Kazemian HB, Meng L: Neuro-fuzzy control for MPEG video transmission over bluetooth. IEEE Transactions on Systems, Man and Cybernetics, Part C 2006, 36(6):761-771.CrossRef Kazemian HB, Meng L: Neuro-fuzzy control for MPEG video transmission over bluetooth. IEEE Transactions on Systems, Man and Cybernetics, Part C 2006, 36(6):761-771.CrossRef
18.
Zurück zum Zitat Ben-Shimol Y, Kitroser I, Dinitz Y: Two-dimensional mapping for wireless OFDMA systems. IEEE Transactions on Broadcasting 2006, 52(3):388-396. 10.1109/TBC.2006.879937CrossRef Ben-Shimol Y, Kitroser I, Dinitz Y: Two-dimensional mapping for wireless OFDMA systems. IEEE Transactions on Broadcasting 2006, 52(3):388-396. 10.1109/TBC.2006.879937CrossRef
19.
Zurück zum Zitat Wengerter C, Ohlhorst J, von Elbwart AGE: Fairness and throughput analysis for generalized proportional fair frequency scheduling in OFDMA. Proceedings of the 61st IEEE Vehicular Technology Conference (VTC '05), May-June 2005, Stockholm, Sweden 3: 1903-1907. Wengerter C, Ohlhorst J, von Elbwart AGE: Fairness and throughput analysis for generalized proportional fair frequency scheduling in OFDMA. Proceedings of the 61st IEEE Vehicular Technology Conference (VTC '05), May-June 2005, Stockholm, Sweden 3: 1903-1907.
20.
Zurück zum Zitat Shreedhar M, Varghese G: Efficient fair queuing using deficit round-robin. IEEE/ACM Transactions on Networking 1996, 4(3):375-385. 10.1109/90.502236CrossRef Shreedhar M, Varghese G: Efficient fair queuing using deficit round-robin. IEEE/ACM Transactions on Networking 1996, 4(3):375-385. 10.1109/90.502236CrossRef
21.
Zurück zum Zitat Jain R, Chiu D, Hawe W: A quantitative measure of fairness and discrimination for resource allocation in shared computer systems. In DEC Research Report. Digital Equipment, Littleton, Mass, USA; September 1984. Jain R, Chiu D, Hawe W: A quantitative measure of fairness and discrimination for resource allocation in shared computer systems. In DEC Research Report. Digital Equipment, Littleton, Mass, USA; September 1984.
22.
Zurück zum Zitat Freitag J, da Fonseca NLS: Uplink scheduling with quality of service in IEEE 802.16 networks. Proceedings of the 50th Annual IEEE Global Telecommunications Conference (GLOBECOM '07), November 2007, Washington, DC, USA 2503-2508. Freitag J, da Fonseca NLS: Uplink scheduling with quality of service in IEEE 802.16 networks. Proceedings of the 50th Annual IEEE Global Telecommunications Conference (GLOBECOM '07), November 2007, Washington, DC, USA 2503-2508.
23.
Zurück zum Zitat Fong M-H, Novak R, McBeath S, Srinivasan R: Improved VoIP capacity in mobile WiMAX systems using persistent resource allocation. IEEE Communications Magazine 2008, 46(10):50-57.CrossRef Fong M-H, Novak R, McBeath S, Srinivasan R: Improved VoIP capacity in mobile WiMAX systems using persistent resource allocation. IEEE Communications Magazine 2008, 46(10):50-57.CrossRef
Metadaten
Titel
Fairness and QoS Guarantees of WiMAX OFDMA Scheduling with Fuzzy Controls
verfasst von
Chao-Lieh Chen
Jeng-Wei Lee
Chi-Yuan Wu
Yau-Hwang Kuo
Publikationsdatum
01.12.2009
Verlag
Springer International Publishing
DOI
https://doi.org/10.1155/2009/512507

Weitere Artikel der Ausgabe 1/2009

EURASIP Journal on Wireless Communications and Networking 1/2009 Zur Ausgabe