requency from the first one, resulting in inter-slot hopping. This mechanism is especially useful for small resource block allocations. The UE decodes the resource allocation field depending on the PDCCH DCI format. A resource allocation field in each PDCCH includes two parts: a resource allocation header field; and information consisting of the actual resource block assignment. The PDCCH DCI formats 1, 2, 2A, and 2B with type 0, and PDCCH DCI formats 1, 2, 2A, and 2B with type 1 resource allocation have the same 9.15 3GPP LTE physical layer protocols format and are distinguished from each other via the single bit resource allocation header field which exists depending on the downlink system bandwidth. The PDCCH with DCI format 1A, 1B, 1C, and 1D have a type 2 resource allocation while PDCCH with DCI format 1, 2, 2A, and 2B have a type 0 or type 1 resource allocation. The PDCCH DCI formats with a type 2 resource allocation do not have a resource allocation header field. The UE would discard the PDSCH resource allocation in the corresponding PDCCH, if consistent control information is not detected (see Figures 9-75 and 9-76). In 3GPP LTE, several downlink control channels are scheduled in one subframe and a UE is expected to monitor a number of those control channels in two search spaces (blind detection): (1) common search space; and (2) UE-specific search space. Each channel carries information associated with an RNTI (UE identifier). The minimum code rate R = 1/3 with constraint length K = 7 tail-biting convolution code is used with QPSK modulation for the control channel. Higher and lower code rates are generated through rate matching. The control and data regions are time-division multiplexed. Each scheduling grant is defined based on fixed-size Control Channel Elements (CCEs), which are combined in a predetermined manner to achieve different coding rates. Each CCE consists of multiple mini-Ces, also known as Resource Element Groups (REGs), that are distributed across time and frequency control resource. Inte