Patent Application
20120230211
The present disclosure pertains to telecommunications, and more particularly to methods and apparatuses for controlling communications through a control channel.
In a typical cellular radio system, wireless terminals (also known as mobile stations and/or user equipment units (UEs)) communicate via a radio access network (RAN) to one or more core networks. User equipment units (UEs) may be, for example, mobile telephones (“cellular” telephones), desktop computers, laptop computers, and tablet computers with wireless communication capability to communicate voice and/or data with a radio access network.
The radio access network covers a geographical area which is divided into cell areas, with each cell area being served by a base station, e.g., a radio base station (RBS), which in some networks is also called “NodeB” or (in Long Term Evolution) eNodeB. A cell is a geographical area where radio coverage is provided by the radio base station equipment at a base station site. Each cell is identified by an identity within the local radio area, which is broadcast in the cell. The base stations communicate over the air interface operating on radio frequencies with the UEs within range of the base stations.
Specifications for an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) are ongoing within the 3rd Generation Partnership Project (3GPP). Another name used for E-UTRAN is the Long Term Evolution (LTE) Radio Access Network (RAN). Long Term Evolution (LTE) is a variant of a 3GPP radio access technology wherein the radio base station nodes are connected directly to a core network rather than to radio network controller (RNC) nodes. In general, in LTE the functions of a radio network controller node are performed by the radio base stations nodes. As such, the radio access network of an LTE system has an essentially “flat” architecture comprising radio base station nodes without reporting to radio network controller nodes.
The evolved UTRAN comprises evolved base station nodes, e.g., evolved NodeBs or eNBs, providing user-plane and control-plane protocol terminations toward the UEs. The eNB hosts the PHYsical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Control Protocol (PDCP) layers that include the functionality of user-plane header-compression and encryption. The eNodeB also offers Radio Resource Control (RRC) functionality corresponding to the control plane. The eNodeB performs many functions including radio resource management, admission control, scheduling, enforcement of negotiated UL QoS, cell information broadcast, ciphering/deciphering of user and control plane data, and compression/decompression of DL/UL user plane packet headers.
The LTE standard is based on multi-carrier based radio access schemes, Orthogonal Frequency-Division Multiplexing (OFDM) in the downlink and SC-FDMA in the uplink. Orthogonal FDM's (OFDM) spread spectrum technique distributes the data over a large number of carriers that are spaced apart at precise frequencies. This spacing provides the “orthogonality” in this technique which prevents the demodulators from seeing frequencies other than their own. The benefits of OFDM are high spectral efficiency, resiliency to RF interference, and lower multi-path distortion.
In the time domain, one subframe, Transmission Time Interval (TTI), of 1 ms duration is divided into 12 or 14 OFDM (or SC-FDMA) symbols, depending on the configuration. One OFDM (or SC-FDMA) symbol includes a number of sub-carriers in the frequency domain, depending on the channel bandwidth and configuration. One OFDM (or SC-FDMA) symbol on one sub-carrier is referred to as a resource element (RE). See, e.g., 3GPP Technical Specification 36.211.
In LTE no dedicated data channels are used; instead, shared channel resources are used in both downlink and uplink. These shared resources, the Physical Downlink Shared Channel (PDSCH) and the Physical Uplink Shared Channel (PUSCH), are each controlled by one or more schedulers that assign(s) different parts of the downlink and uplink shared channels to different UEs for reception and transmission, respectively.
The downlink assignments for the Physical Downlink Shared Channel (PDSCH) and uplink grants for the Physical Uplink Shared Channel (PUSCH) are transmitted to UEs in a control region covering a few OFDM symbols in the beginning of each downlink subframe. The Physical Downlink Shared Channel (PDSCH) is transmitted in a data region covering all or a subset of the OFDM symbols in each downlink subframe. The size of the control region may be either, one, two, three or four OFDM symbols, and is set dynamically per subframe, sometimes within semistatically configured restrictions (e.g., R-PDCCH, cross-scheduled UEs in carrier aggregation).
Each assignment PDSCH or PUSCH is transmitted as a message on a physical channel named the Physical Downlink Control Channel (PDCCH) in the control region. There are typically multiple Physical Downlink Control Channels (PDCCHs) in each subframe. Downlink assignments and uplink grants are defined for only one transmission time interval (TTI). Thus, a new downlink assignment or uplink grant is sent for each TTI where the UE is expected to receive transmission, except for semipersistent scheduling where scheduling is performed for a defined number of TTIs by identifying that a downlink assignment or uplink grant is valid for a one TTI at a time, reoccurring with a configured periodicity until it is released by a defined PDCCH message or by RRC signalling.
A PDCCH is mapped to (e.g., comprises) a number of control channel elements (CCEs). Each CCE consists of thirty six Resource Elements (REs). A PDCCH can be transmitted with quadrature phase-sift keying (QPSK) modulation and channel coding, and can include an aggregation level of 1, 2, 4 or 8 CCEs, See, e.g., 3GPP Technical Specification 36.213, which is incorporated herein by reference in its entirety. These four different alternatives are herein referred to as aggregation level 1, 2, 4, and 8, respectively. Each control channel element (CCE) may only be utilized on one aggregation level at the time. The total number of available control channel element (CCEs) in a subframe will vary depending on several parameters like number of OFDM symbols used for PDCCH, number of antennas used for transmission/reception, system bandwidth, Physical HARQ Indicator Channel (PHICH) size, etc.
The number of CCEs, and thereby the coderate, used for transmission of a PDCCH message from a network node to a UE can be controlled based on channel state information (CSI) that is reported by the UE. The CSI can include a Channel-Quality Indication (CQI), a rank indication, and a precoder matrix indication. A UE generates the CSI based on measurements performed on CSI reference signals (RS) transmitted by the network node. The interference measured on these references signals, from RSs or data traffic, might be correlated with the interference experienced by a PDCCH. Moreover, data traffic and its resulting interference dynamically changes over time, and these changes may not be correlated with PDCCH interference changes.
Consequently, controlling CCE allocation for PDCCH messages solely based on CSI may lead to inefficient allocation of CCEs. Inefficient allocation of CCEs may be particularly problematic when handling low-bandwidth services and/or uplink communications (which are typically limited to more narrowband allocation than downlink due to UE transmission power limitations) where a lack of available CCEs can limit how many UEs can be scheduled in the same TTI on different frequency segments to utilize the available bandwidth. Improvements in how CCEs can be allocated for PDCCH messages are therefore desired.
Some embodiments of the present invention are a method of operating a node of a telecommunications system. The method controls how many Control Channel Elements (CCEs) of a frequency or time division multiplexing radio interface are used to transmit a Physical Downlink Control Channel (PDCCH) message to a User Equipment unit (UE) based on a rate of expected responses that the node does not receive from the UE for previously transmitted PDCCH messages to the UE.
In some further embodiments, the method of controlling how many CCEs are used to transmit the PDCCH message to the UE may include comparing the rate of expected responses that the node does not receive to a threshold value to determine when to increase the number of CCEs that are used to communicate the PDCCH message, and controlling the threshold value of the comparison based on uplink channel quality from the UE to the node so that as uplink channel quality decreases a higher rate of expected responses that the node does not receive is needed to trigger an increase in the number of CCEs.
In some further embodiments, the method of controlling how many CCEs are used to transmit the PDCCH message to the UE can include communicating a PDCCH message containing a DownLink (DL) assignment to the UE. In response to receipt of an ACKnowledgement (ACK) or Negative-ACKnowledgement (NACK) from the UE, how many CCEs are used to communicate a PDCCH message to the UE can be decreased. Conversely, in response to absence of receipt of the ACK or NACK from the UE, how many CCEs are used to communicate a PDCCH message to the UE can be increased.
In some further embodiments, the method of controlling how many CCEs are used to transmit the PDCCH message to the UE can include communicating a PDCCH message containing an UpLink (UL) grant PDCCH message to the UE. In response to receipt of an UL transmission on a Physical Uplink Shared Channel (PUSCH) from the UE, how many CCEs are used to communicate a PDCCH message to the UE can be decreased. Conversely, in response to absence of receipt of an UL transmission on the PUSCH from the UE, how many CCEs are used to communicate a PDCCH message to the UE can be increased.
Some other embodiments of the present invention are directed to a corresponding node of a telecommunications system.
Other methods, network nodes, and/or telecommunication systems according to embodiments of the invention will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional methods, network nodes, and/or telecommunication systems be included within this description, be within the scope of the present invention, and be protected by the accompanying claims. Moreover, it is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate certain embodiment(s) of the invention. In the drawings:
a-b illustrate example operations and methods by a network node to control CCE allocation based on a rate of expected responses that the network node does not receive from a UE for previously transmitted PDCCH messages to the UE;
In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. That is, those skilled in the art will be able to devise various arrangements which, although not explicitly described or shown herein, embody the principles of the invention and are included within its spirit and scope. In some instances, detailed descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail. All statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.
The eNodeB 28 includes one or more transceiver(s) 34 which is/are configured to transmit a subframe of information over the radio interface 32. For downlink transmission to the UEs 30, the transceiver(s) 34 feed one or more antennae 35 which function to provide plural sub-carriers. The transceiver(s) 34 thereby transmit symbols of the subframe on plural sub-carriers in a frequency domain.
The eNodeB 28 also includes a handler 36 of subframes that is configured to prepare or format subframes of information for transmission by transceiver(s) 34 on a downlink to one or more of the UEs 30. A representative, sample depiction of a subframe S is shown in
Details of the subframe S and the resource grid are provided in 3GPP Technical Specification 36.211, which is incorporated herein by reference. The subframe S includes downlink physical channels, each of which corresponds to a set of resource elements which carry information originating from layer one or higher layers. The downlink physical channels of subframe S can include the Physical Downlink Control Channel (PDCCH), the Physical Downlink Share Channel (PDSCH), the Physical Broadcast Channel (PBCH), the Physical Multicast Channel (PMCH), the Physical Control Format Indicator channel (PCFICH), the Physical Hybrid ARQ Indicator Channel (PHICH), a reference signal (RS), and a synchronization signal.
As explained above, each subframe S includes a control region. Depending on implementation, the size of the control region can be either one, two, three, or four OFDM symbols. The example subframe S of
The subframe handler 36 of the eNodeB 28 formats and processes information for transmission through a subframe S, such as that depicted in
As explained above, the PDCCH messages carry downlink assignments for the Physical Downlink Shared Channel (PDSCH) and uplink grants for the Physical Uplink Shared Channel (PUSCH). There are typically multiple PDCCHs in the control region of each subframe, and the UEs 30 detect the assignments/grants directed to them through the PDCCHs.
The number of CCEs that are needed to be able to reliably transmit a single PDCCH message from the eNodeB 28 to a particular UE 30 depends on the present channel quality from the eNodeB 28 to the UE 30. Accordingly, PDCCH messages may be more reliably and efficiently transmitted by providing a mechanism for the eNobeB 28 to determine how many CCEs to select for use in transmitting each PDCCH to the UE 30 based on the present quality of the channel through which the PDCCH is transmitted.
In accordance with various embodiments of the present invention, the PDCCH processor 38 controls how many CCEs of a frequency or time division multiplexing radio interface are used to transmit a PDCCH message to a UE 30 based on a rate of expected responses that the eNodeB 28 does not receive from the UE 30 for previously transmitted PDCCH messages to the UE 30.
The PDCCH processor 38 may control how many CCEs are used to transmit the PDCCH message to the UE 30 by comparing the rate of expected responses that the eNodeB 28 does not receive to a threshold value to determine when to increase the number of CCEs that are used to communicate the PDCCH message. The PDCCH processor 38 may control the threshold value of the comparison based on uplink channel quality from the UE 30 to the eNodeB 28 so that as uplink channel quality decreases a higher rate of expected responses that the node does not receive is needed to trigger an increase in the number of CCEs.
Although various embodiments are described herein the context of the CCEs of a frequency division multiplexed radio interface, in some other embodiments the CCEs may alternatively or additionally relate to resource elements of a time division multiplexed radio interface. The receipt or absence of a response from a particular UE 30 to a PDCCH message can provide a more accurate indication of the present channel conditions affecting communication of a message through the PDCCH to a particular UE 30. Accordingly, more efficient allocation of CCEs to PDCCH transmissions to a particular UE 30 may be accomplished compared to using channel state information (CSI) alone.
Example operations that may be carried out by the PDCCH processor 38 to control the number of CCEs that are used to transmit a PDCCH to a particular UE 30 are explained below with regard to the following three embodiments:
1) whether the eNodeB 28 receives from the UE 30 an ACK/NACK response to a DownLink (DL) assignment message that the eNodeB 28 transmitted to the UE 30;
2) whether the eNodeB 28 receives from the UE 30 an uplink (UL) transmission responsive to an uplink (UL) grant message that the eNodeB 28 transmitted to the UE 30; and
3) whether the eNodeB 28 receives from the UE 30 both an ACK/NACK response and an UL transmission responsive to a corresponding DL assignment message and UL grant message that the eNodeB 28 transmitted to the UE 30.
Although operation of the PDCCH processor 38 is described in the context of these three separate embodiments, the invention is not limited thereto. Moreover, the three example embodiments are described in the context of using a step (jump) algorithm to adjust a PDCCH link adaptation offset value, however the adjustments may instead be made by other algorithms, such as by a moving average filter and/or an exponential filter.
Before discussing these three embodiments, reference is made to
Regarding
a and 4b illustrate example operations and methods of the PDCCH processor 38 within the eNodeB 28 or another network node for controlling allocation of CCEs of a frequency or time division multiplexing radio interface for transmission of a PDCCH message based on a rate of expected responses that the eNodeB 28 does not receive from the UE 30 for (in response to) previously transmitted PDCCH messages to the UE 30.
Referring to
b illustrates further operations that may be carried out by the PDCCH processor 38 to control CCE allocation for a PDCCH message. Referring to
As will be explained in further detail below with regard to, for example,
When the PDCCH processor 38 allocates more CCEs for use in transmitting a PDCCH message due to allowed aggregation levels but which is much greater than the number of CCEs determined by the CCE allocation algorithm, the PDCCH processor 38 may respond to another occurrence of absence of receipt of an expected response by causing a larger adjustment in allocation of CCEs to adapt to the effects of channel quality. For example, when the CCE allocation algorithm determined that 4.2 CCEs were to be used for the PDCCH message but, due to allowed aggregation levels being limited to 1, 2, 4, or 8, 8 CCEs were used, the PDCCH processor 38 may respond to another occurrence of absence of receipt of an expected response by causing a larger adjustment in allocation of CCEs to adapt to the effects of channel quality. In contrast, in the above example, if the PDCCH processor 38 allocated 4 CCEs (less aggressive channel adaptation) for a PDCCH message in expectation that 4 CCEs would be just enough, not receiving a response is not as unexpected as in the previous example and, therefore, a relatively smaller adjustment may be made in the allocation of CCEs to adapt to the effects of channel quality.
Accordingly, although some of
Adaptation of CCE Allocation Responsive to DL Assignments:
a-b and 6 illustrate example operations and methods of the PDCCH processor 38 within the eNodeB 28 or another network node for controlling CCE allocation for transmission of a PDCCH message based on estimation of PDCCH quality using a downlink DL assignment message.
Referring to
In some further embodiments, the PDCCH processor 38 may decrease (block 504) the number of CCEs using the optional operations and methods of blocks 506-512. The eNodeB 28 receives (block 506) a Channel Status Report (CSR) from the UE 30. The PDCCH processor 38 estimates (block 508) a Signal-to-Interference-and-Noise Ratio (SINR) value for communications from the UE 30. The SINR value may be estimated based on a previously received Channel Status Report from the UE 30, that can include a rank indication that provides information about the channel rank, a precoding matrix indicator, and/or a channel-quality indication (CQI) representing a recommended modulation scheme, coding rate and precoder matrix for downlink transmission on PDSCH. The PDCCH processor 38 determines (block 510) an adjustment value responsive to probability that: 1) the DL assignment message was successfully decoded by the UE 30; or 2) the DL assignment message not successfully by the UE 30 and a false ACK or false NACK was received by the eNodeB 28. The PDCCH processor 38 then decreases (block 512) how many CCEs are used to communicate a PDCCH message to the UE 30 responsive to the adjustment value and to the CSR.
The PDCCH processor 38 may increase (block 514) the number of CCEs using the optional operations and methods of blocks 516-522. The eNodeB 28 receives (block 516) a Channel Status Report (CSR) from the UE 30. The PDCCH processor 38 estimates (block 518) a Signal-to-Interference-and-Noise Ratio (SINR) value for communications from the UE 30. The PDCCH processor 38 determines (block 520) an adjustment value responsive to probability that: 1) the DL assignment message was not successfully decoded by the UE 30; or 2) the DL assignment message successfully decoded by the UE 30 and the eNodeB 28 failed to detect an ACK or NACK from the UE 30. The PDCCH processor 38 then increases (block 522) how many CCEs are used to communicate a PDCCH message to the UE 30 responsive to the adjustment value and to the CSR.
When an ACK or NACK is received, an adjustment step size x1(n) is calculated (block 604) responsive to an estimated SINR and a probability determination that corresponds to the operations of block 510 of
y(n)=y(n−1)+x1(n)/k1.
In contrast, when an ACK or NACK is not received, an adjustment step size x2(n) is calculated (block 616) responsive to an estimated SINR and a probability determination that corresponds to the operations of block 520 of
A Channel Status Report (CSR) is received (block 610) from the UE 30. The CSR is adjusted to generate (block 612) a PDCCH-adapted-CSRLA value as follows: CSRLA(n)=CSR(n)+y(n). The CSR reported by a UE may be preprocessed before being adjusted to generate the CSRLA. The PDCCH processor 38 then controls (block 614) how many CCEs are used to communicate a PDCCH message to the UE 30 responsive to the CSRLA value.
Accordingly, a first increase can be provided in the number of CCEs based on a defined rate of expected responses not being received from the UE while uplink channel quality from the UE is at a first level. A second increase can be provided in the number of CCEs based on the defined rate of expected responses not being received from the UE while uplink channel quality from the UE is at a second level. When the first level of uplink channel quality is better than the second level of uplink channel quality, then the first increase in the number of CCEs can be greater than the second increase in the number of CCEs.
Adaptation of CCE Allocation Responsive to UL Grants:
Referring to
In some further embodiments, the PDCCH processor 38 may decrease (block 804) the number of CCEs using the optional operations and methods of blocks 806-812. The eNodeB 28 receives (block 806) a Channel Status Report (CSR) from the UE 30. The PDCCH processor 38 estimates (block 808) a SINR value for communications from the UE 30. The PDCCH processor 38 determines (block 810) an adjustment value responsive to probability that: 1) the UL grant PDCCH message was successfully decoded by the UE 30; or 2) the UL grant PDCCH message was not successfully decoded by the UE 30 and a false UL transmission on the PUSCH was detected by the eNodeB 28 while subject to the estimated SINR value. The PDCCH processor 38 then decreases (block 812) how many CCEs are used to communicate a PDCCH message to the UE 30 responsive to the adjustment value and to the CSR.
The PDCCH processor 38 may increase (block 814) the number of CCEs using the optional operations and methods of blocks 816-822. The eNodeB 28 receives (block 816) a Channel Status Report (CSR) from the UE 30. The PDCCH processor 38 estimates (block 818) a Signal-to-Interference-and-Noise Ratio (SINR) value for communications from the UE 30. The PDCCH processor 38 determines (block 820) an adjustment value responsive to probability that: 1) the UL grant PDCCH message was not successfully decoded by the UE 30; or 2) the UL grant PDCCH message was successfully decoded by the UE 30 and the eNodeB 28 failed to detect an UL transmission on the PUSCH from the UE 30 while subject to the estimated SINR value. The PDCCH processor 38 then increases (block 822) how many CCEs are used to communicate a PDCCH message to the UE 30 responsive to the adjustment value and to the CSR.
When an UL transmission is received, an adjustment step size x1(n) is calculated (block 904) responsive to an estimated SINR and a probability determination that corresponds to the operations of block 810 of
In contrast, when an UL transmission is not received, an adjustment step size x2(n) is calculated (block 916) responsive to an estimated SINR and a probability determination that corresponds to the operations of block 820 of
A Channel Status Report (CSR) is received (block 910) from the UE 30. The CSR is adjusted to generate (block 912) a PDCCH-adapted-CSRLA value as follows: CSRLA(n)=CSR(n)+y(n). The PDCCH processor 38 then controls (block 914) how many CCEs are used to communicate a PDCCH message to the UE 30 responsive to the CSRLA value.
Adaptation of CCE Allocation Responsive to DL Assignments and UL Grants:
Referring to
The PDCCH processor 38 determines (block 1104) whether it received a UL transmission (corresponding to the UL grant) on the PUSCH from the UE 30 and received a ACK/NACK (corresponding to the DL assignment) from the UE 30. In response to receiving both, the PDCCH processor 38 determines (block 1106) an adjustment value responsive to a probability that: 1) the DL assignment PDCCH message was successfully decoded by the UE; or 2) the DL assignment PDCCH message was not successfully decoded by the UE and a false ACK or false NACK was received by the node while subject to the estimated SINR value, and responsive to a probability that: 1) the UL grant PDCCH message was successfully decoded by the UE; or 2) the UL grant PDCCH message was not successfully decoded by the UE and a false UL transmission on the PUSCH was detected by the node while subject to the estimated SINR value. The PDCCH processor 38 then controls (block 1108) how many CCEs are used to communicate a PDCCH message to the UE in response to the adjustment value and to the CSR.
In response to determining (block 1110) that the eNodeB 28 received a UL transmission (corresponding to the UL grant) but did not receive an ACK/NACK (corresponding to the DL assignment) from the UE 30, the PDCCH processor 38 determines (block 1112) an adjustment value responsive to a probability that: 1) the DL assignment PDCCH message was not successfully decoded by the UE; or 2) the DL assignment PDCCH message was successfully decoded by the UE and the node failed to detect an ACK or NACK from the UE while subject to the estimated SINR value, and responsive to a probability that: 1) the UL grant PDCCH message was successfully decoded by the UE; or 2) the UL grant PDCCH message was not successfully decoded by the UE and a false UL transmission on the PUSCH was detected by the node while subject to the estimated SINR value. The PDCCH processor 38 then controls (block 1108) how many CCEs are used to communicate a PDCCH message to the UE in response to the adjustment value and to the CSR.
In response to determining (block 1114) that the eNodeB 28 did not receive a UL transmission (corresponding to the UL grant) but did receive an ACK/NACK (corresponding to the DL assignment) from the UE 30, the PDCCH processor 38 determines (block 1116) an adjustment value responsive to a probability that: 1) the DL assignment PDCCH message was successfully decoded by the UE; or 2) the DL assignment PDCCH message was not successfully decoded by the UE and a false ACK or false NACK was received by the node while subject to the estimated SINR value, and responsive to a probability that: 1) the UL grant PDCCH message was not successfully decoded by the UE; or 2) the UL grant PDCCH message was successfully decoded by the UE and the node failed to detect an UL transmission on the PUSCH from the UE while subject to the estimated SINR value. The PDCCH processor 38 then controls (block 1108) how many CCEs are used to communicate a PDCCH message to the UE in response to the adjustment value and to the CSR.
In response to determining (block 1118) that the eNodeB 28 did not receive a UL transmission (corresponding to the UL grant) and did not receive an ACK/NACK (corresponding to the DL assignment) from the UE 30, the PDCCH processor 38 determines (block 1120) an adjustment value responsive to a probability that: 1) the DL assignment PDCCH message was not successfully decoded by the UE; or 2) the DL assignment PDCCH message was successfully decoded by the UE and the node failed to detect an ACK or NACK from the UE while subject to the estimated SINR value, and responsive to a probability that: 1) the UL grant PDCCH message was not successfully decoded by the UE; or 2) the UL grant PDCCH message was successfully decoded by the UE and the node failed to detect an UL transmission on the PUSCH from the UE while subject to the estimated SINR value. The PDCCH processor 38 then controls (block 1108) how many CCEs are used to communicate a PDCCH message to the UE in response to the adjustment value and to the CSR.
a-b illustrate further operations and methods that may be carried-out by the PDCCH processor 38 to control CCE allocation for transmission of a PDCCH message using both a DL assignment message and an UL grant message according to some embodiments. Referring to
The PDCCH processor 38 determines (block 1202) whether it received a UL transmission (corresponding to the UL grant) on the PUSCH from the UE 30 and received an ACK/NACK (corresponding to the DL assignment) from the UE 30. In response to receiving both, the PDCCH processor 38 calculates (block 1204) an adjustment step size x1(n) responsive to an estimated SINR and a probability determination that can correspond to the operations of block 1106 of
In contrast, in response to determining (block 1216) that a UL transmission (corresponding to the UL grant) was received but an ACK/NACK (corresponding to the DL assignment) was not received, an adjustment step size x2(n) is calculated (block 1218) responsive to an estimated SINR and a probability determination that can correspond to the operations of block 1112 of
In contrast, in response to determining (block 1224) that a UL transmission (corresponding to the UL grant) was not received but an ACK/NACK (corresponding to the DL assignment) was received, an adjustment step size x3(n) is calculated (block 1226) responsive to an estimated SINR and a probability determination that can correspond to the operations of block 1116 of
In contrast, in response to determining (block 1232) that a UL transmission (corresponding to the UL grant) was not received and an ACK/NACK (corresponding to the DL assignment) was not received, an adjustment step size x3(n) is calculated (block 1234) responsive to an estimated SINR and a probability determination that can correspond to the operations of block 1120 of
A Channel Status Report (CSR) is received (block 1210) from the UE 30. The CSR is adjusted to generate (block 1212) a PDCCH-adapted-CSRLA value as follows: CSRLA(n)=CSR(n)+y(n). The PDCCH processor 38 then controls (block 1214) how many CCEs are used to communicate a PDCCH message to the UE 30 responsive to the CSRLA value.
In the above-description of various embodiments of the present invention, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense expressly so defined herein.
When an element is referred to as being “connected”, “coupled”, “responsive”, or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected”, “directly coupled”, “directly responsive”, or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, “coupled”, “connected”, “responsive”, or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term “and/or” includes any and all combinations of one or more of the associated listed items.
As used herein, the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia,” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.
Exemplary embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).
These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks.
A tangible, non-transitory computer-readable medium may include an electronic, magnetic, optical, electromagnetic, or semiconductor data storage system, apparatus, or device. More specific examples of the computer-readable medium would include the following: a portable computer diskette, a random access memory (RAM) circuit, a read-only memory (ROM) circuit, an erasable programmable read-only memory (EPROM or Flash memory) circuit, a portable compact disc read-only memory (CD-ROM), and a portable digital video disc read-only memory (DVD/BlueRay).
The computer program instructions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks.
Accordingly, embodiments of the present invention may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as “circuitry,” “a module” or variants thereof.
It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, the present specification, including the drawings, shall be construed to constitute a complete written description of various exemplary combinations and subcombinations of embodiments and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.
Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present invention. All such variations and modifications are intended to be included herein within the scope of the present invention.
