Title of Invention: METHODS AND DEVICES FOR CONTROL CHANNEL DECODING Abstract: A circuit arrangement includes a control circuit configured to identify a candidate message in received control data that indicates a potential location of an encoded message in the received control data, the candidate message having a predefined message bit length, a measurement circuit configured to perform a radio measurement, the control circuit further configured to compare the radio measurement to a predefined threshold, and a decoding circuit further configured to, if the radio measurement satisfies the predefined threshold, search for the encoded message in the received control data by decoding the candidate message from the received control data with a reduced message bit length less than the predefined bit length. Detailed Description: TECHNICAL FIELD Various embodiments relate generally to methods and devices for control channel decoding. BACKGROUND Long Term Evolution (LTE) networks may transmit control information at the beginning of each downlink transmission period. As specified by the 3rd Generation Partnership Project (3GPP), LTE cells may transmit with a 1 ms Transmission Time Interval (TTI), where each 1 ms TTI is a subframe and groups of 10 consecutive subframes are grouped into radio frames. The first several (e.g. between one and four) symbol periods of each subframe may then be allocated for control information, which may be transmitted on the Physical Downlink Control Channel (PDCCH). Mobile terminals connected to a given LTE cell may then need to read the PDCCH symbols at the beginning of each subframe in order to obtain essential control information, which may include uplink transmission grants, downlink scheduling messages, transmit power control messages, etc. BRIEF DESCRIPTION OF THE DRAWINGS In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention. In the following description, various embodiments of the invention are described with reference to the following drawings, in which: FIG. 1 shows an LTE resource grid; FIG. 2 shows CCEs of a PDCCH search space; FIG. 3 shows downlink encoding circuitry for an LTE cell; FIG. 4 shows an internal configuration of a mobile terminal; FIG. 5 shows a decoding structure of a mobile terminal; FIG. 6 shows a method of performing PDCCH searches; FIG. 7 shows an SNR vs. BLER plot; FIG. 8 shows a first exemplary PDCCH search procedure with a reduced decoding aggregation level; FIG. 9 shows a second exemplary PDCCH search procedure with a reduced decoding aggregation level; FIG. 10 shows a first method of decoding control data for radio communications; and FIG. 11 shows a second method of decoding control data for radio communications. DESCRIPTION The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and embodiments in which the invention may be practiced. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration”. Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. The words “plurality” and “multiple” in the description and the claims expressly refer to a quantity greater than one. The terms “group (of)”, “set [of]”, “collection (of)”, “series (of)”, “sequence (of)”, “grouping (of)”, etc., and the like in the description and in the claims, if any, refer to a quantity equal to or greater than one, i.e. one or more. Any term expressed in plural form that does not expressly state “plurality” or “multiple” refers to a quantity equal to or greater than one. The terms “proper subset”, “reduced subset”, and “lesser subset” refer to a subset of a set that is not equal to the set, i.e. a subset of a set that contains less elements than the set. It is appreciated that any vector and/or matrix notation utilized herein is exemplary in nature and is employed solely for purposes of explanation. Accordingly, it is understood that the approaches detailed in this disclosure are not limited to being implemented solely using vectors and/or matrices, and that the associated processes and computations may be equivalently performed with respect to sets, sequences, groups, etc., of data, observations, information, signals, samples, symbols, elements, etc. Furthermore, it is appreciated that references to a “vector” may refer to a vector of any size or orientation, e.g. including a 1×1 vector (e.g. a scalar), a 1×M vector (e.g. a row vector), and an M×1 vector (e.g. a column vector). Similarly, it is appreciated that references to a “matrix” may refer to matrix of any size or orientation, e.g. including a 1×1 matrix (e.g. a scalar), a 1×M matrix (e.g. a row vector), and an M×1 matrix (e.g. a column vector). A “circuit” as used herein is understood as any kind of logic-implementing entity, which may include special-purpose hardware or a processor executing software. A circuit may thus be an analog circuit, digital circuit, mixed-signal circuit, logic circuit, processor, microprocessor, Central Processing Unit (CPU), Graphics Processing Unit (GPU), Digital Signal Processor (DSP), Field Programmable Gate Array (FPGA), integrated circuit, Application Specific Integrated Circuit (ASIC), etc., or any combination thereof. Any other kind of implementation of the respective functions which will be described below in further detail may also be understood as a “circuit”. It is understood that any two (or more) of the circuits detailed herein may be realized as a single circuit with substantially equivalent functionality, and conversely that any single circuit detailed herein may be realized as two (or more) separate circuits with substantially equivalent functionality. Additionally, references to a “circuit” may refer to two or more circuits that collectively form a single circuit. The term “circuit arrangement” may refer to a single circuit, a collection of circuits, and/or an electronic device composed of one or more circuits. As used herein, “memory” may be understood as a non-transitory computer-readable medium in which data or information can be stored for retrieval. References to “memory” included herein may thus be understood as referring to volatile or non-volatile memory, including random access memory (RAM), read-only memory (ROM), flash memory, solid-state storage, magnetic tape, hard disk drive, optical drive, etc., or any combination thereof. Furthermore, it is appreciated that registers, shift registers, processor registers, data buffers, etc., are also embraced herein by the term memory. It is appreciated that a single component referred to as “memory” or “a memory” may be composed of more than one different type of memory, and thus may refer to a collective component comprising one or more types of memory. It is readily understood that any single memory component may be separated into multiple collectively equivalent memory components, and vice versa. Furthermore, while memory may be depicted as separate from one or more other components (such as in the drawings), it is understood that memory may be integrated within another component, such as on a common integrated chip. The term “base station” used in reference to an access point of a mobile communication network may be understood as a macro base station, micro base station, Node B, evolved NodeB (eNB), Home eNodeB, Remote Radio Head (RRH), relay point, etc. As used herein, a “cell” in the context of telecommunications may be understood as a sector served by a base station. Accordingly, a cell may be a set of geographically co-located antennas that correspond to a particular sectorization of a base station. A base station may thus serve one or more cells (or sectors), where each cell is characterized by a distinct communication channel. Furthermore, the term “cell” may be utilized to refer to any of a macrocell, microcell, femtocell, picocell, etc. For purposes of this disclosure, radio communication technologies may be classified as one of a Short Range radio communication technology, Metropolitan Area System radio communication technology, or Cellular Wide Area radio communication technology. Short Range radio communication technologies include Bluetooth, WLAN (e.g. according to any IEEE 802.11 standard), and other similar radio communication technologies. Metropolitan Area System radio communication technologies include Worldwide Interoperability for Microwave Access (WiMax) (e.g. according to an IEEE 802.16 radio communication standard, e.g. WiMax fixed or WiMax mobile) and other similar radio communication technologies. Cellular Wide Area radio communication technologies include Global System for Mobile Communications (GSM), Code Division Multiple Access 2000 (CDMA2000), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), General Packet Radio Service (GPRS), Evolution-Data Optimized (EV-DO), Enhanced Data Rates for GSM Evolution (EDGE), High Speed Packet Access (HSPA), etc., and other similar radio communication technologies. Cellular Wide Area radio communication technologies also include “small cells” of such technologies, such as microcells, femtocells, and picocells. Cellular Wide Area radio communication technologies may be generally referred to herein as “cellular” communication technologies. It is understood that exemplary scenarios detailed herein are demonstrative in nature, and accordingly may be similarly applied to various other mobile communication technologies, both existing and not yet formulated, particularly in cases where such mobile communication technologies share similar features as disclosed regarding the following examples. The term “network” as utilized herein, e.g. in reference to a communication network such as a mobile communication network, encompasses both an access section of a network (e.g. a radio access network (RAN) section) and a core section of a network (e.g. a core network section). The term “radio idle mode” or “radio idle state” used herein in reference to a mobile terminal refers to a radio control state in which the mobile terminal is not allocated at least one dedicated communication channel of a mobile communication network. The term “radio connected mode” or “radio connected state” used in reference to a mobile terminal refers to a radio control state in which the mobile terminal is allocated at least one dedicated uplink communication channel of a mobile communication network. Unless explicitly specified, the term “transmit” encompasses both direct (point-to-point) and indirect transmission (via one or more intermediary points). Similarly, the term “receive” encompasses both direct and indirect reception. The term “communicate” encompasses one or both of transmitting and receiving, i.e. unidirectional or bidirectional communication in one or both of the incoming and outgoing directions. The term “calculate” encompass both ‘direct’ calculations via a mathematical expression/formula/relationship and ‘indirect’ calculations via lookup tables and other array indexing or searching operations. As specified by the 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE) cells may perform downlink transmissions according to 10 ms radio frames that are each divided into 10 subframes of 1 ms duration each, i.e. 10 Transmission Time Intervals (TTI). Each subframe may be further divided into two slots (each of 0.5 ms duration) of either 6 or 7 symbol periods each (depending on the Cyclic Prefix (CP) length), where each symbol period may contain one Orthogonal Frequency Division Multiplexing (OFDM) symbol per subcarrier. The LTE system bandwidth may be distributed across a set of evenly-spaced subcarriers, which as noted above may each carry a single OFDM symbol per symbol period. As defined by the 3GPP, the subcarriers may be uniformly positioned on a 15 kHz grid and include a central DC subcarrier; accordingly, the number of subcarriers may vary between 73 and 1201 according to the variable 1.4 to 20 MHz system bandwidth. Each symbol period per subcarrier may be defined as a Resource Element (RE), and accordingly each RE (per antenna port) may hold a single OFDM symbol. REs may be further grouped into RE Groups (REG), which is a group of 4 consecutive REs (not including reference signal REs), and Resource Blocks (RB), which is a time-frequency block spanning one slot (6 or 7 symbols) and 12 subcarriers (180 kHz), e.g. a block of 84 REs for normal CP. FIG. 1 shows an exemplary downlink LTE resource grid 100 depicting 12 subcarriers over a single subframe with a normal CP length. Each LTE cell may need to transmit both control and user data traffic during each subframe; accordingly, as shown in FIG. 1 each subframe may be divided into a control region and a data region, where the control region occurs in the first several symbols of each subframe and the data region occupies the remaining symbols. The control region may contain symbols allocated for the Physical Control Format Indicator Channel (PCFICH), Physical Hybrid Automatic Repeat Request (HARM) Indicator Channel (PHICH), and Physical Downlink Control Channel (PDCCH) (where certain other REs in the control region may be allocated for reference signals or are left vacant). LTE mobile terminals (also known as User Equipment (UE)) may need to receive control information contained in the control region in order to support both downlink and uplink communications. As previously noted, the control region may vary in size between 1 and 4 symbols at the beginning of each subframe. LTE cells may broadcast the size of the control region for each subframe on the PCFICH, which may be mapped to 16 REs in the first symbol period of each subframe and may specify the Control Format Indicator (CFI). Mobile terminals may thus receive the PCFICH during the first symbol of each subframe and utilize the CFI specified thereon to establish the size of the control region for the current subframe. For example, the CFI in the exemplary scenario of resource grid 100 may specify that the control region is three symbols in length, i.e. the first three symbols of the subframe. Identification of the CFI from PCFICH data may then allow mobile terminals to read the PDCCH data of the subframe, which may be essential to both uplink and downlink communications. In particular, PDCCH data may include uplink and downlink scheduling messages in addition to transmit power control (TPC) instructions. Each PDCCH message may be in a particular format known as a Downlink Control Information (DCI) Format, where different DCI formats may be utilized for different types of PDCCH messages. For example, DCI Formats 0 and 4 may be used for uplink scheduling grants and assignments, which an LTE cell may utilize in order to instruct a mobile terminal of transmission and scheduling parameters for uplink transmissions in the current subframe, while DCI Formats 1 and 2 may be utilized for downlink scheduling assignments and DCI Format 3 may be utilized for TPC commands. The 3GPP has also defined additional DCI formats, such as e.g. DCI Format 1A, 2A, etc., in order to handle the various single- and multi-antenna LTE transmission modes. Mobile terminals may thus need to reliably receive the relevant DCIs in order to support uplink and downlink communications in each subframe. Depending on the specific format, certain DCI formats may need to contain more information (e.g. to schedule more complex transmissions such as Multiple Input Multiple Output (MIMO) transmissions); accordingly, LTE cells may need to transmit more payload data for some DCI formats than others. As an LTE cell will conventionally serve multiple mobile terminals during each subframe, LTE cells may need to allocate PDCCH messages for multiple mobile terminals during each control region. Accordingly, an LTE cell may need to select control symbols to apportion for each PDCCH message; as a result, mobile terminals will need to search through the control region in order to identify which PDCCH data are of interest. LTE cells may perform the resource mapping for PDCCH messages according to Control Channel Elements (CCE), which may each be composed of 9 REGs (each composed of four consecutive non-reference signal REs) in the control region that are allocated to the PDCCH. More specifically, LTE cells may map each PDCCH message (each DCI Format message) to any of 1, 2, 4, or 8 CCEs, where the number of CCEs utilized for a given PDCCH message corresponds to the aggregation level of the PDCCH message. As specified by the 3GPP, PDCCH employ utilize Quadrature Phase-Shift Keying (QPSK) as the modulation scheme, which may be able to transmit 2 bits per QPSK symbol. Given the 4 REs (one symbol each) per REG and 9 REGs per CCE, each CCE may thus have capacity for 72 total bits. As the control region may be shared between all mobile terminals being serviced by a given LTE cell, the PDCCH messages intended for multiple different mobile terminals may all be placed close to one another in the control symbols; accordingly, there may be many different locations where the PDCCH message addressed to a given mobile terminal may be placed in the control region. The placement of the PDCCH message for each mobile terminal within the control region may switch every subframe, and as a result a given mobile terminal may therefore need to ‘search’ through the CCEs in each subframe in order to identify which PDCCH messages are intended for the mobile terminal. As previously noted, some PDCCH messages may be addressed to groups of mobile terminals while other PDCCH messages may be addressed to specific mobile terminals. Accordingly, the CCEs of each control region may be divided into a common search space and UE-specific search spaces, where the CCEs in the common search space may contain PDCCH messages addressed to groups of mobile terminals and CCEs in each UE-specific search space (one per UE) may contain PDCCH messages addressed to a particular UE. The CCEs of each control region thus each be assigned a CCE index to differentiate between the CCEs, where the specific mapping between CCE index and the physical REs of each subframe may depend on the number of reference symbols, CFI, etc. FIG. 2 shows an exemplary depiction of the common and UE-specific search spaces for a set of NCCE CCEs in a given subframe. As shown in FIG. 2, the common search space may start at logical CCE n=0, i.e. the first logical CCE of the control region (where the exact REs may depend on the mapping of the particular subframe), and may occupy CCEs n=0, . . . , 15. The CCEs may additionally contain one or more UE-specific search spaces (one per mobile terminal), where an LTE cell may select the starting CCE index for the UE-specific search space for each mobile terminal based on a random hash function; accordingly, each UE-specific search space may occupy a contiguous block of CCEs beginning with the respective starting CCE index. As shown in FIG. 2, a UE-specific search space may overlap with the common search space, as the depicted UE-specific search space also has a starting CCE index of n=0; additionally, UE-specific search spaces may overlap with one another. Accordingly, depending on which type(s) of PDCCH messages a mobile terminal is expecting, the mobile terminal may search through the CCEs one or both of the search spaces in order to identify and read any PDCCH messages that are addressed to the mobile terminal. The transmitting LTE cell may consequently need to address each of the PDCCH messages in order to allow the receiving mobile terminals to establish whether a given PDCCH message is intended for it or not. As specified by the 3GPP, LTE cells may append a Cyclic Redundancy Check (CRC) to each PDCCH message that depends on an identification value, where each identification value specifies an individual or group of mobile terminals. More specifically, each mobile terminal may be assigned one or more network identifiers known as Radio Network Temporary Identifiers (RNTI). RNTIs of particular importance include Cell-RNTIs (C-RNTI), which a cell may individually assign to each connected mobile terminal in order to uniquely identify each connected mobile terminal, Paging-RNTIs (P-RNTIs), which a cell may utilize to page mobile terminals, System Information-RNTIs (SI-RNTIs), which a cell may use to schedule system information messages, etc. Accordingly, depending on the type and intended recipients of each PDCCH message, an LTE cell may append an appropriate CRC to each PDCCH message that corresponds to the RNTI of the intended recipients. Depending on its current operating status, a given mobile terminal may be assigned multiple different RNTIs and accordingly may need to check the search spaces for PDCCH messages addressed with more than one RNTI. During search of the common and/or UE-specific search spaces, a mobile terminal may thus need to identify each possible block of CCEs that could contain a PDCCH message addressed to the mobile terminal and attempt to decode each possible CCE block. Upon completing the decode of a given CCE block, the mobile terminal may compare the CRC with the RNTIs associated with the mobile terminal and determine whether the CCE block contains a PDCCH message addressed to the mobile terminal based on whether the CRC matches any of the associated RNTIs. Mobile terminals may proceed to check each possible block of CCEs in the search space and thus identify all relevant PDCCH messages. Each possible block of CCEs that could contain a PDCCH message for a given mobile terminal may thus be referred to as a PDCCH candidate. FIG. 2 depicts various PDCCH candidates in both the common and UE-specific search space, which may have varying aggregation levels L; in other words, each PDCCH candidate may be composed of L logically consecutive CCEs where L may vary. The exact CCE locations of each PDCCH candidate may be specified by the 3GPP; accordingly, upon identifying the common search space (CCE index n=0) and the UE-specific search space (with a starting CCE index dependent on the random hash function), a mobile terminal may need to search through each PDCCH candidate and determine which (if any) PDCCH candidates are addressed to the mobile terminal by comparing the CRC of each decoded PDCCH candidate to the associated RNTIs. As L and the starting CCE position of each PDCCH candidate may vary, a mobile terminal may have to search across multiple different blocks of CCEs in order to reliably detect PDCCH messages. The aggregation level used by an LTE cell for each PDCCH message may vary depending on several factors. As noted above, certain DCI formats may need to contain more data in order to detail control information for complex transmissions such as MIMO. While most of the DCI formats specified by the 3GPP will fit into the 72 bit capacity of a single CCE, some DCI formats, such as for the aforementioned case of MIMO, may contain over 72 payload bits and thus may require more than one CCE. Additionally, LTE cells may select aggregation levels based on the current radio conditions of the target mobile terminals. As PDCCH messages are essential to maintaining both uplink and downlink communications, LTE cells may need to ensure that target mobile terminals are able to reliably receive and decode PDCCH messages. In order to ensure decoding, LTE cells may utilize higher aggregation levels for mobile terminals in poor radio conditions and accordingly may transmit these PDCCH messages with more coding bits. As a result, the target mobile terminals may enjoy coding and/or energy gains in decoding and be able to accurately decode PDCCH messages despite poor radio conditions. As other mobile terminals in superior radio conditions may be able to decode the PDCCH messages without such coding and energy gains, LTE cells may utilize lower aggregation levels for PDCCH messages addressed to these mobile terminals. Furthermore, LTE cells may select to utilize higher aggregation levels when only a small number of mobile terminals are being serviced, as such may allow for more CCEs to be allocated per user and thus provide improved decoding performance. Conversely, when a large number of mobile terminals are being served by a cell, the limited per-user control resources may result in the cell needing to utilize smaller aggregation levels. When searching through the search space for PDCCH messages, a mobile terminal may not know specifically which aggregation level the cell used to transmit a PDCCH message of interest. As a result, mobile terminals may need to search PDCCH candidates of all possible aggregation levels in order to detect PDCCH messages, where some of the PDCCH candidates overlap in CCEs with one another due to the varying lengths. As specified by the 3GPP, PDCCH messages in the common search space may utilize an aggregation level of either L=4 or L=8 while PDCCH messages in UE-specific search spaces may use any of the possible L=1,2,4,8 aggregation levels. Accordingly, a mobile terminal may need to search L=4 and L=8 PDCCH candidates in the common search space and L=1,2,4,8 candidates in the UE-specific search space (as shown in FIG. 2). While the 3GPP has also specified certain CCE indices that PDCCH messages of specific aggregation levels can be located (e.g., L=1 PDCCH messages may only be located at certain CCE indices and so forth for L=2,4,8), as shown in FIG. 2 the PDCCH candidates may overlap in CCE index. Mobile terminals may therefore need to perform blind decodes over a number of PDCCH candidates of varying aggregation levels in order to search for PDCCH messages. Furthermore, in many cases a mobile terminal may not know specifically which DCI Format an expected PDCCH message will be. For example, as specified by the 3GPP in Table 7.1-5 of TS 36.213 “Evolved Universal Terrestrial Radio Access (E-UTRA) Physical layer procedures”, V13.1.1 (Release 13), each mobile terminal configured with a given Transmission Mode (TM) may be eligible to receive two different DCI Formats. More specifically, the LTE cell may configure each mobile terminal according to a particular transmission mode, where each transmission mode may call for a different transmission configuration such as standard single antenna communication, transmit diversity, cyclic delay diversity, single/multi-user MIMO, beamforming, coordinated multi-point, etc. As shown in Table 7.1-5, each transmission mode may allow for two different DCI Formats; as a result, a mobile terminal that has been configured to a particular transmission mode may be eligible to receive either of the two corresponding DCI Formats as the PDCCH message. As each DCI Format requires a different amount of payload data, and thus is encoded differently depending on the payload data size, a mobile terminal that is expecting a PDCCH message may need to decode each PDCCH candidate according to both eligible DCI Formats. As opposed to decoding each PDCCH candidate a single time, a mobile terminal may thus need to perform two separate decodes where each decode utilizes a different decoding assumption on account of the different possible DCI Formats. In other words, a mobile terminal may decode a given PDCCH candidate a first time assuming the PDCCH candidate is the first eligible DCI Format and, if this decode fails, may decode the same PDCCH candidate a second time assuming the PDCCH candidate is the second eligible DCI Format. The extensive blind decoding over a large number of PDCCH candidates combined with the need to perform multiple decodes of each PDCCH candidate may thus require considerable time and high power consumption. In an advantageous solution of this disclosure, a mobile terminal may take exploit the rate-matching procedure used by LTE cells to encode PDCCH messages in order to substantially reduce the amount of decoding in the blind decode process to both save time and power. In particular, a mobile terminal may determine whether the mobile terminal is currently in strong radio conditions and, if so, perform blind decoding of PDCCH candidates assuming a reduced aggregation level and may thus perform blind decoding on smaller blocks of data for each PDCCH candidate. Accordingly, as opposed to decoding each PDCCH candidate over the corresponding full aggregation level (i.e. over all of the CCEs assigned to the PDCCH candidate), the mobile terminal may decode certain PDCCH candidates with a reduced aggregation level by only decoding part of the encoded data of the PDCCH candidate (i.e. only decoding some of the CCEs assigned to the PDCCH candidate). As LTE cells may encoded PDCCH with redundancy (to provide coding and/or energy gains at higher aggregation levels), the mobile terminal may be able to reliably decode the PDCCH candidates with lower aggregation levels and thus conserve time and power in the decoding process. While the mobile terminal may sacrifice coding and/or energy gain by ignoring some of the CCEs during decoding, given strong radio conditions the mobile terminal may still enjoy sufficient decoder performance. As noted above, the possibility of this solution may stem from the rate-matching scheme employed by LTE cells during PDCCH encoding. FIG. 3 shows an exemplary encoding circuitry 300 for PDCCH data which may be included in an LTE cell (e.g. at a Baseband Unit (BBU) of an LTE eNodeB) As shown in FIG. 3, an LTE cell may start with the PDCCH payload data of A bits at 302, which as detailed in Section 5.3.3 of 3GPP TS 36.212 “Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding” V13.1.0 (Release 13), may vary depending on the DCI format, e.g. low complexity DCI formats such as single-antenna transmission have less payload data than complex DCI formats such as MIMO transmission, and on system bandwidth (with larger system bandwidth settings needing larger payload size). The LTE cell may then append a 16-bit CRC to the payload data to obtain a B=A+16 bit unencoded sequence with CRC circuit 304, where as previously detailed the LTE cell may derive the CRC based on the RNTI of the destination mobile terminal. The LTE cell may then encode the B bit unencoded sequence at encoder 306, which may be a 1/3 rate convolutional encoder as specified by the 3GPP. Accordingly, given the 1/3 rate encoder 306 may produce 3B bits in the form of three separate bitstreams each of length B, where each bitstream corresponds to a respective encoded bit position. Due to the bit capacity constraints placed by the aggregation level L, the LTE cell may then need to perform rate matching at rate matching circuit 308 to obtain an E=72L bit sequence (where each CCE contains 72 bits) from the 3B bits of the encoded bit sequence. The advantageous solution of this disclosure may exploit the rate-matching procedure employed by LTE cells to obtain the E bit encoded sequence. In order to ensure that the encoded sequence can be completely decoded by a destination mobile terminal, rate matching circuit 308 may need to ensure that each of the original B bits (of which A are payload data and 16 are CRC bits) is represented by at least one bit of the E-bit encoded sequence; otherwise, the mobile terminal will not have enough information to decode all of the bits. Accordingly, E must be at least B, i.e. E≧B, which may require the LTE cell to utilize an aggregation level L sufficient to fit at least B bits into the E=72L bits of the rate-matched sequence. As previously noted, most DCI formats will be able to fit into a single CCE, i.e. B≦72; however, some DCI formats may be larger and thus may require a minimum aggregation level of L=2. Depending on the aggregation level L and original sequence length B, rate matching circuit 308 may either need to employ puncturing or bit replication in order to produce an E length sequence. For example, if not all of the 3B bits encoded bits will fit into the E total bits of the L aggregated CCEs, rate matching circuit 308 may need to discard, or ‘puncture’ some of the encoded bits to arrive at E bits that will fit into the L aggregated CCEs; conversely, if more than the 3B bits will fit into the E total bits of the L aggregated CCEs, rate matching circuit 308 may duplicate some of the encoded bits to produce E bits to place into the L aggregated CCEs. As specified by the 3GPP, encoder 306 may generate the 3B bit sequence by generating the aforementioned three bitstreams each of length 3: b0 (k), b1(k), and b2(k) for k=0, 1, . . . , B−1. Encoder 306 may then generate the 3B bit encoded sequence benc(k), k=0, 1, . . . , 3B−1 by placing b0(k) as the first B bits of benc(k), b1(k) as next B bits of benc(k), and b2(k) for the remaining B bits of benc(k), i.e. benc(k)=[b0(0) . . . b0(B−1)b1(0) . . . b1(B−1)b2(0) . . . b2(B−1)] (1) As previously noted, there must be at least one encoded bit of benc(k) that corresponds to each unencoded bit of the original B bit sequence in order to allow a mobile terminal to fully recover the original sequence, i.e. one coding bit corresponding to each of the original B bits. The presence of multiple coding bits, e.g. if two or more of b0 (0), b1(0), and b2 (0) are present for bit position k=0 of the original sequence, may offer coding gains for bit k=0 during decoding by a mobile terminal; additionally, the presence of duplicated bits, e.g. if b0(0) is duplicated in the encoded sequence, such may offer energy gains during decoding as a mobile terminal may combine the received bits. While only the first B bits of benc(k) are theoretically needed to decode, multiple coding bits and duplicated bits may be needed for mobile terminals in poor radio conditions to reliably decode the encoded sequence. Rate matching circuit 308 may need to puncture or replicate encoded bit sequence benc(k) to arrive at a rate matched sequence brm(k), k=0, 1, . . . , E−1 (where some puncturing may be required in every case that E is not an integer multiple of 3B). Accordingly, if 3B>E, i.e. not all of the 3B bits of benc(k) will fit into the E total bits of the L aggregated CCEs, rate matching circuit 308 may simply perform burst puncturing and drop the 3B−E last bits of benc(k), thus producing the rate-matched sequence brm(k) as the first E bits of benc(k), i.e. brm(k)=benc(k), k=0, 1, . . . E−1 (2) Rate matching circuit 308 may then pass the resulting E bit rate-matched sequence brm(k) to modulator 310 for modulation and transmission. Accordingly, brm(k) may contain multiple encoded bits corresponding to certain bit positions of the unencoded sequence (assuming E≠3B) and may thus offer a coding gain for certain bit positions; however, as less than the 3B bits were transmitted there may only be coding gains at some bit positions and no energy gain (as no encoded bits were replicated). The condition 3B>E may only be feasible if the destination mobile terminal is in strong radio conditions, as it may be difficult for mobile terminals to reliably decode the rate-matched sequence brm(k) with only partial coding gains and no energy gains in the face of noise and interference. Accordingly, for mobile terminals experiencing poor radio conditions, the LTE cell may select a larger aggregation level L which may as a result allow for more of the 3B encoded bits of benc(k) to be passed by rate matching circuit 308 to brm(k). For example, if E≧3B, i.e. if at least the 3B bits of benc(k) will fit in the L total aggregated CCEs, rate matching circuit 308 may be able to pass the complete 3B bits of benc(k) to brm(k), thus offering coding gains for every bit. Furthermore, if E>3B, i.e. if more than the 3B bits of benc(k) will fit into the L aggregated CCEs, rate matching circuit 308 may additionally be able to duplicate some of the 3B bits to fill the remaining E−3B bit positions of the L aggregated CCEs, thus offering an energy gain at the duplicated bit positions as a decoder may be able to combine multiple bits together. If brm(k) is e.g. double or triple the size of benc(k), i.e. if benc(k) fits multiple times within brm(k), rating matching circuit 308 may be able to duplicate benc(k) several times over, thus offering substantial energy gain. As specified by the 3GPP, depending on the payload size A and aggregation level L, it may be possible for rate matching circuit 308 to produce e.g. an 18B bit encoded sequence, thus replicating benc(k) six times over in the rate-matched sequence brm(k). In all such cases, rate matching circuit 308 may still need to perform burst puncturing (unless E is an exact multiple of 3B) in order to produce an rate-matched sequence brm(k) of exactly E bits. Accordingly, the LTE cell may be able to select aggregation levels to provide coding and energy gains to ensure that destination mobile terminals are able to reliably decode each PDCCH message. Nevertheless, as rate matching circuit 308 will always include b0(k) as the first B bits the rate-matched bit sequence brm (k) (as b0(k) will occupy the first B bits of benc(k)), mobile terminals may still have enough information to decode a given PDCCH message from only the first B bits of the encoded output sequence. For example, if e.g. B=70 and L=2, rate matching circuit 308 may produce an E=144 bit rate-matched sequence brm(k) in which the first 70 bits of brm(k) are b0(k) and the remaining 74 bits are the 70 bits of b(k) and the first 4 bits of b2(k). If radio conditions are strong enough, a mobile terminal may theoretically not need the coding gain offered by the final 74 bits and may be able to recover the original 70 bit sequence by only decoding b0(k), i.e. the first 70 bits of rate-matched sequence brm(k). Accordingly, even though two CCEs were used to transmit brm (k), the mobile terminal may only need to decode the first CCE, i.e. the first 72 bits of brm (k) in order to recover the original B bit sequence. Alternatively, the mobile terminal may determine that SNR conditions are good enough that e.g. two CCEs of data (e.g. 144 bits of the rate-matched sequence brm (k)) would be sufficient to reliably decode the original PDCCH message. Accordingly, the mobile terminal may decode each L=2,4,8 PDCCH candidate with only two CCEs, i.e. may input only two CCEs of each PDCCH candidate to the decoder for decoding. While explained here with an integer multiple of CCEs, the mobile terminal may instead input only partial CCEs to the decoder, such as e.g. only inputting the first B bits of the first CCE (if E>B) into the decoder. Such examples may be similarly extended to any number of scenarios with B, L, and E. Accordingly, in order to conserve time and power, a mobile terminal may determine when radio conditions are strong and subsequently decode PDCCH candidates with a lower assumed aggregation level, i.e. by decoding less than all of the CCEs assigned to the PDCCH candidates. For example, the mobile terminal may perform a Signal to Noise Ratio (SNR) measurement and determine that radio conditions are strong enough that only one CCE is needed to decode PDCCH messages. Accordingly, the mobile terminal may decode each PDCCH candidate, regardless of aggregation level, with only one CCE. Accordingly, as decoding of further CCEs will produce coding and energy gains but are not absolutely necessary if radio conditions are sufficient, the mobile terminal may conserve time and power by decoding less information than in the conventional case. FIG. 4 shows an internal configuration of mobile terminal 400, which may include antenna system 402, radio frequency (RF) transceiver 404, baseband modem 406 (including physical layer processing circuit 408 and controller 410), data source 412, memory 414, and data sink 416. As will be detailed, mobile terminal 400 may be configured to perform PDCCH decoding by determining if a reduced decoding aggregation level is acceptable based on radio measurements and, if yes, decode the PDCCH candidates with the reduced decoding aggregation level, i.e. decode less than all of the CCEs assigned to the PDCCH candidates. As certain encoded bits will be redundant, mobile terminal 400 may theoretically not need to decode all of the CCEs and may conserve time and power at the expense of coding and/or energy gains by decoding only part of the CCEs of the PDCCH candidates. Although not explicitly shown in FIG. 4, mobile terminal 400 may include one or more additional hardware, software, and/or firmware components (such as processors/microprocessors, controllers/microcontrollers, other specialty or generic hardware/processors/circuits, etc.), peripheral device(s), memory, power supply, external device interface(s), subscriber identify module(s) (SIMs), user input/output devices (display(s), keypad(s), touchscreen(s), speaker(s), external button(s), camera(s), microphone(s), etc.), etc. In an abridged operational overview, mobile terminal 400 may transmit and receive radio signals on one or more radio access networks. Baseband modem 406 may direct such communication functionality of mobile terminal 400 according to the communication protocols associated with each radio access network, and may execute control over antenna system 402 and RF transceiver 404 in order to transmit and receive radio signals according to the formatting and scheduling parameters defined by each communication protocol. Mobile terminal 400 may transmit and receive radio signals with antenna system 400, which may be a single antenna or an antenna array composed of multiple antennas and may additionally include analog antenna combination and/or beamforming circuitry. In the receive path (RX), RF transceiver 404 may receive analog radio frequency signals from antenna system 402 and perform analog and digital RF front-end processing on the analog radio frequency signals to produce digital baseband samples (e.g. In-Phase/Quadrature (IQ) samples) to provide to baseband modem 404. RF transceiver 404 may accordingly include analog and digital reception circuitry including amplifiers (e.g. a Low Noise Amplifier (LNA), filters, RF demodulators (e.g. an RF IQ demodulator)), and analog-to-digital converters (ADCs) to convert the received radio frequency signals to digital baseband samples. In the transmit path (TX), RF transceiver 404 may receive digital baseband samples from baseband modem 206 and perform analog and digital RF front-end processing on the digital baseband samples to produce analog radio frequency signals to provide to antenna system 402 for wireless transmission. RF transceiver 404 may thus include analog and digital transmission circuitry including amplifiers (e.g. a Power Amplifier (PA), filters, RF modulators (e.g. an RF IQ modulator), and digital-to-analog converters (DACs) to mix the digital baseband samples received from baseband modem 406 to produce the analog radio frequency signals for wireless transmission by antenna system 402. Baseband circuit 406 may control the RF transmission and reception of RF transceiver 404, including specifying the transmit and receive radio frequencies for operation of RF transceiver 404. As shown in FIG. 4, baseband modem 406 may include physical layer processing circuit 408, which may perform physical layer (Layer 1) transmission and reception processing to prepare outgoing transmit data provided by controller 410 for transmission via RF transceiver 404 and prepare incoming received data provided by RF transceiver 404 for processing by controller 410. Physical layer processing circuit 410 may accordingly perform one or more of error detection, forward error correction encoding/decoding, channel coding and interleaving, physical channel modulation/demodulation, physical channel mapping, radio measurement and search, frequency and time synchronization, antenna diversity processing, power control and weighting, rate matching, retransmission processing, etc. Physical layer processing circuit 408 may be structurally realized as hardware logic, e.g. as an integrated circuit or FPGA, as software logic, e.g. as program code defining arithmetic, control, and I/O instructions stored in a non-transitory computer-readable storage medium and executed on a processor, or as a combination of hardware and software logic. Although not explicitly shown in FIG. 4, physical layer processing circuit 408 may include a control circuit such as a processor configured to control the various hardware and software processing components of physical layer processing circuit 408 in accordance with physical layer control logic defined by the communications protocol for the relevant radio access technologies. Furthermore, while physical layer processing circuit 408 is depicted as a single component in FIG. 4, physical layer processing circuit 408 may be collectively composed separate sections of physical layer processing circuitry where each respective section is dedicated to the physical layer processing of a particular radio access technology. Mobile terminal 400 may be configured to operate according to one or more radio access technologies, which may be directed by controller 410. Controller 410 may thus be responsible for controlling the radio communication components of mobile terminal 400 (antenna system 402, RF transceiver 404, and physical layer processing circuit 408) in accordance with the communication protocols of each supported radio access technology, and accordingly may represent the Access Stratum and Non-Access Stratum (NAS) (also encompassing Layer 2 and Layer 3) of each supported radio access technology. Controller 410 may be structurally embodied as a protocol processor configured to execute protocol software (retrieved from controller memory MEM as shown in FIG. 4) and subsequently control the radio communication components of mobile terminal 400 in order to transmit and receive communication signals in accordance with the corresponding protocol control logic defined in the protocol software. Controller 410 may therefore be configured to manage the radio communication functionality of mobile terminal 400 in order to communicate with the various radio and core network components of radio communication network 100, and accordingly may be configured according to the communication protocols for both the LTE network and the GSM/UMTS legacy network. Controller 410 may either be a unified controller that is collectively responsible for all supported radio access technologies (e.g. LTE and GSM/UMTS) or may be composed of multiple separate controllers where each controller is a dedicated controller for a particular radio access technology, such as e.g. a dedicated LTE controller and a dedicated legacy controller (or alternatively a dedicated LTE controller, dedicated GSM controller, and a dedicated UMTS controller). Regardless, controller 410 may be responsible for directing radio communication activity of mobile terminal 400 according to the communication protocols of the LTE and legacy networks. As previously noted regarding physical layer processing circuit 408, one or both of antenna system 402 and RF transceiver 404 may similarly be partitioned into multiple dedicated components that each respectively correspond to one or more of the supported radio access technologies. Depending on the specifics of each such configuration and the number of supported radio access technologies, controller 410 may be configured to control the radio communication operations of mobile terminal 400 in accordance with a master/slave RAT hierarchical or multi-SIM scheme. Mobile terminal 400 may further comprise data source 412, memory 414, and data sink 416, where data source 412 may include sources of communication data above controller 410 (i.e. above the NAS/Layer 3) and data sink 412 may include destinations of communication data above controller 410 (i.e. above the NAS/Layer 3). Such may include, for example, an application processor of mobile terminal 400, which may be configured to execute various applications and/or programs of mobile terminal 400 at an application layer of mobile terminal 400, such as e.g. an Operating System (OS), a User Interface (UI) for supporting user interaction with mobile terminal 400, and/or various user applications. The application processor may interface with baseband modem 406 (as data source 412/data sink 416) as an application layer to transmit and receive user data such as voice data, audio/video/image data, messaging data, application data, basic Internet/web access data, etc., over a the radio network connection(s) provided by baseband modem 406. Data source 412 and data sink 416 may additionally represent various user input/output devices of communication device 400, such as display(s), keypad(s), touchscreen(s), speaker(s), external button(s), camera(s), microphone(s), etc., which may allow a user of mobile terminal 400 to control various communication functions of mobile terminal 400 associated with user data. Memory 414 may embody a memory component of mobile terminal 400, such as e.g. a hard drive or another such permanent memory device. Although not explicitly depicted in FIG. 4, the various other components of mobile terminal 400 shown in FIG. 4 may additionally each include integrated permanent and non-permanent memory components, such as for storing software program code, buffering data, etc. As introduced above, mobile terminal 400 may perform PDCCH decoding by, if radio conditions are determined to be strong, assuming a reduced aggregation level during decoding and thus decoding PDCCH candidates with less CCEs the PDCCH candidates actually include (either as an integer number of CCEs or partial CCEs, i.e. inputting an integer number of CCEs into the decoder or inputting partial bits of CCEs into the decoder). Accordingly, if mobile terminal 400 determines that radio conditions are strong enough that one CCE is sufficient to reliably decode PDCCH data, mobile terminal 400 may only decode one CCE worth of data for each PDCCH candidate, thus conserving time and power while sacrificing coding and energy gains that may be available if all CCEs of the PDCCH candidates are decode. Similarly, if mobile terminal 400 determines that radio conditions are strong enough that two CCEs are sufficient to reliably decode PDCCH data, mobile terminal 400 may decode two CCEs worth of data for each L=2,4,8 PDCCH candidate. As the LTE cell may nevertheless have transmitted a PDCCH message with L=1, mobile terminal 400 may still need to decode only one CCE for each L=1 candidate. FIG. 5 shows the internal structure of mobile terminal 400 related to the PDCCH decoding procedure of this disclosure, where other internal components of mobile terminal 400 in addition to control, clock, and power lines are not explicitly shown in order to preserve drawing clarity. FIG. 6 shows method 600, which details the PDCCH decoding process performed by decoding structure 500 of baseband modem 406 as shown in FIG. 5. The functionality of each component of decoding structure 500 may be structurally realized/embodied as hardware logic, e.g. as one or more integrated circuits or FPGAs, as software logic, e.g. as one or more processors executing program code
{'app_number': None, 'application_number': '<application-reference appl-type="utility">\n<document-id>\n<country>US</country>\n<doc-number>15200077</doc-number>\n<date>20160701</date>\n</document-id>\n</application-reference>', 'doc_number': None, 'publication_number': '<publication-reference>\n<document-id>\n<country>US</country>\n<doc-number>20180007664</doc-number>\n<kind>A1</kind>\n<date>20180104</date>\n</document-id>\n</publication-reference>', 'source_file': './application/2018/ipa180104.xml', 'source_data': 'USPTO-Application'}