You are presented with multiple paper abstracts, alongside the associated literature review and chapter titles. Given the provided information, you are going to do a literature review. Please generate a coherent literature review that synthesizes the content, draws connections between different works, highlights major findings, and identifies any gaps in the existing research.

Literature Review Title: A Survey of Mobile WiMAX IEEE 802.16m Standard 
Chapter Title:  IV. SCHEDULER 
1. Abstract of Cited Paper (BIB001):  In order to meet the requirements of 4G mobile networks targeted by the cellular layer of IMT-advanced, next generation mobile WiMAX devices based on IEEE 802.16m will incorporate sophisticated signal processing, seamless handover functionalities between heterogeneous technologies and advanced mobility mechanisms. This survey provides a description of key projected features of the physical (PHY) and medium access control (MAC) layers of 802.16m, as a major candidate for providing aggregate rates at the range of Gbps to high-speed mobile users. Moreover, a new unified method for simulation modeling, namely the evaluation methodology (EVM), introduced in 802.16m, is also presented. 
2. Abstract of Cited Paper (BIB002):  Multicast and broadcast services in WiMAX are downlink point-to-multipoint access services optimized for transmission of a common set of multimedia data packets to a group of users. This capability enables low-cost delivery of large volumes of popular contents (e.g., for video/audio streaming and file sharing) in a mobile network. The MCBCS framework in WiMAX allows multicast/broadcast of data in a radio channel that is time shared with unicast services. In a single-frequency network, where MCBCS transmissions are synchronized or coordinated across BSs in the designated service area, the mobile stations can use macro-space diversity to improve achievable data rates and also maintain service continuity and power saving across cells with minimal interaction with the network.

Literature Review:
Scheduling is the main component of the MAC layer that helps assure QoS to various service classes   BIB001 BIB002 . The scheduler works as a distributor to allocate the resources among MSs. The allocated resource can be defined as the number of slots and then these sots are mapped into a number of subchannels (each subchannel is a group of multiple physical subcarriers) and time duration (OFDM symbols). In OFDMA, the smallest logical unit for bandwidth allocation is a slot. The definition of slot depends upon the direction of traffic (downlink/uplink) and subchannelization modes. For example, in PUSC mode in downlink, one slot is equal to twenty four subcarriers (one subchannel) for three OFDM symbols duration. In the same mode for uplink, one slot is fourteen subcarriers (one uplink subchannel) for two OFDM symbols duration. The mapping process from logical subchannel to multiple physical subcarriers is called a permutation. PUSC, discussed above is one of the permutation modes. Others include Fully Used Subchannelization (FUSC) and Adaptive Modulation and Coding (band-AMC). The term band-AMC distinguishes the permutation from adaptive modulation and coding (AMC) MCS selection procedure. Basically there are two types of permutations: distributed and adjacent. The distributed subcarrier permutation is suitable for mobile users while adjacent permutation is for fixed (stationary) users. After the scheduler logically assigns the resource in terms of number of slots, it may also have to consider the physical allocation, e.g., the subcarrier allocation. In systems with Single Carrier PHY, the scheduler assigns the entire frequency channel to a MS. Therefore, the main task is to decide how to allocate the number of slots in a frame for each user. In systems with OFDM PHY, the scheduler considers the modulation schemes for various subcarriers and decides the number of slots allocated. In systems with OFDMA PHY, the scheduler needs to take into consideration the fact that a subset of subcarriers is assigned to each user. Scheduler designers need to consider the allocations logically and physically. Logically, the scheduler should calculate the number of slots based on QoS service classes. Physically, the scheduler needs to select which subchannels and time intervals are suitable for each user. The goal is to minimize power consumption, to minimize bit error rate and to maximize the total throughput. There are three distinct scheduling processes: two at the BS -one for downlink and the other for uplink and one at the MS for uplink as shown in Fig. 5 . At the BS, packets from the upper layer are put into different queues, which ideally is per-CID queue in order to prevent head of line (HOL) blocking. However, the optimization of queue can be done and the number of required queues can be reduced. Then, based on the QoS parameters and some extra information such as the channel state condition, the DL-BS scheduler decides which queue to service and how many service data units (SDUs) should be transmitted to the MSs. Since the BS controls the access to the medium, the second scheduler -the UL-BS scheduler -makes the allocation decision based on the bandwidth requests from the MSs and the associated QoS parameters. Several ways to send bandwidth requests were described earlier in Section I.F. Finally, the third scheduler is at the MS. Once the UL-BS grants the bandwidth for the MS, the MS scheduler decides which queues should use that allocation. Recall that while the requests are per connections, the grants are per subscriber and the subscriber is free to choose the appropriate queue to service. The MS scheduler needs a mechanism to allocate the bandwidth in an efficient way. Fig. 6 classification of scheduler is given. Table II presents a comparison of these classes BIB003 BIB002 . UGS: This service class provides a fixed periodic bandwidth allocation. Once the connection is setup, there is no need to send any other requests. This service is designed for constant bit rate (CBR) real-time traffic such as E1/T1 circuit emulation. The main QoS parameters are maximum sustained rate (MST), maximum latency and tolerated jitter (the maximum delay variation). ertPS: This service is designed to support VoIP with silence suppression. No traffic is sent during silent periods. ertPS service is similar to UGS in that the BS allocates the maximum sustained rate in active mode, but no bandwidth is allocated during the silent period. There is a need to have the BS poll the MS during the silent period to determine if the silent period has ended. The QoS parameters are the same as those in UGS. rtPS: This service class is for variable bit rate (VBR) realtime traffic such as MPEG compressed video. Unlike UGS, rtPS bandwidth requirements vary and so the BS needs to regularly poll each MS to determine what allocations need to be made. The QoS parameters are similar to the UGS but minimum reserved traffic rate and maximum sustained traffic rate need to be specified separately. For UGS and ertPS services, these two parameters are the same, if present. nrtPS: This service class is for non-real-time VBR traffic with no delay guarantee. Only minimum rate is guaranteed. File Transfer Protocol (FTP) traffic is an example of applications using this service class. Most of data traffic falls into this category. This service class guarantees neither delay nor throughput. The bandwidth will be granted to the MS if and only if there is a left-over bandwidth from other classes. In practice most implementations allow specifying minimum reserved traffic rate and maximum sustained traffic rate even for this class. Note that for non-real-time traffic, traffic priority is also one the QoS parameters that can differentiate among different connections or subscribers within the same service class. Consider bandwidth request mechanisms for uplink. UGS, ertPS and rtPS are real-time traffic. UGS has a static allocation. ertPS is a combination of UGS and rtPS. Both UGS and ertPS can reserve the bandwidth during setup. Unlike UGS, ertPS allows all kinds of bandwidth request including contention resolution. rtPS can not participate in contention resolution. For other traffic classes (non real-time traffic), nrtPS and BE, several types of bandwidth requests are allowed such as piggybacking, bandwidth stealing, unicast polling and contention resolution. These are further discussed in Section I.F. Thus mobile WiMAX brings potential benefits in terms of coverage, power consumption, self-installation, frequency reuse, and bandwidth efficiency. One of the key complications is that the incompatibility in the newly introduced scalable OFDM (SOFDM) in IEEE 802.11e with the original OFDM scheme forces equipment manufacturers to come up with mechanisms to ease the transition