The present application is generally related to wireless communications systems and is more specifically related to hybrid Automatic Repeat Request (HARQ) transmission in systems where data transmissions are scheduled for durations of less than a subframe.
For error control, the fourth-generation (4G) wireless system known as “Long-Term Evolution (LTE), standardized by members of the 3rd-Generation Partnership Project (3GPP), uses hybrid-ARQ (HARQ). After receiving downlink data in a subframe, the mobile terminal attempts to decode it and report, via a Physical Uplink Control Channel (PUCCH), to the base station whether (ACK) or not (NACK) the decoding was successful. In the event of an unsuccessful decoding attempt, the base station (eNodeB or eNB) can retransmit the erroneous data. Similarly, the base station can indicate to the mobile terminal whether the decoding of the Physical Uplink Shared Channel (PUSCH) was successful (ACK) or not (NACK) via the Physical Hybrid ARQ Indicator Channel (PHICH).
In addition to the hybrid-ARQ ACK/NACK information transmitted from the mobile terminal to the base station, uplink control signaling from the mobile terminal to the base station also includes reports related to the downlink channel conditions, referred to generally as channel-state information (CSI) or channel-quality information (CQI). This CSI/CQI is used by the base station to assist in downlink resource scheduling decisions. Because LTE systems rely on dynamic scheduling of both downlink and uplink resources, uplink control-channel information also includes scheduling requests, which the mobile terminal sends to indicate that it needs uplink traffic-channel resources for uplink data transmissions.
Packet data latency is one of the performance metrics that vendors, operators and also end-users (via speed test applications) regularly measure. Latency measurements are done in all phases of a radio access network system lifetime, e.g., when verifying a new software release or system component, when deploying a system, and when the system is in commercial operation.
Improved latency compared to previous generations of 3GPP radio access technologies (RATs) was one performance metric that guided the design of LTE. LTE is also now recognized by its end users to be a system that provides faster access to internet and lower data latencies than previous generations of mobile radio technologies.
Packet data latency is important not only for the perceived responsiveness of the system, but is also a parameter that indirectly influences the throughput of the system. HTTP/TCP is the dominating application and transport layer protocol suite used on the Internet today. According to HTTP Archive (http://httparchive.org/trends.php), the typical size of HTTP based transactions over the Internet is in the range of a few tens of kilobytes up to 1 Mbyte. In this size range, the Transport Control Protocol (TCP) slow-start period is a significant part of the total transport period of the packet stream. During TCP slow start, the performance is latency limited. Hence, improved latency can rather easily be shown to improve the average throughput for this type of TCP based data transactions.
Radio resource efficiency can also be positively impacted by latency reductions. Lower packet data latency can increase the number of transmissions possible within a certain delay bound; hence, higher block-error rate (BLER) targets could be used for the data transmissions, freeing up radio resources and potentially improving the capacity of the system. It should also be noted that reduced latency of data transport may also indirectly give faster radio control plane procedures like call set-up/bearer set-up, due to the faster transport of higher layer control signaling.
There are several current applications that will be positively impacted by reduced latency, in terms of increased perceived quality of experience. Examples are gaming and real-time applications like Voice over LTE/Over-the-top voice over IP (VoLTE/OTT VoIP) and multi-party video conferencing. In the future, there will be a number of new applications that will be more delay critical. Examples may be remote control/driving of vehicles, augmented reality applications in, e.g., smart glasses, or specific machine communications requiring low latency.
LTE is a radio access technology based on radio access network control and scheduling. These facts impact the latency performance since a transmission of data need a round trip of lower layer control signaling. An example of this lower layer control signaling is shown in
When it comes to packet latency reductions, one area to address is the reduction of transport time of data and control signaling, e.g., by addressing the length of a transmit-time-interval (TTI), and the reduction of processing time of control signaling, e.g., by reducing the time it takes for a UE to process a grant signal.
One way to reduce the latency for terminal receiver processing is to allow for downlink transmissions, e.g., transmissions on the physical downlink shared channel (PDSCH) in LTE, that are shorter than the current transmit-time interval (TTI) of one subframe, e.g., that occupy fewer than all of the orthogonal frequency-division multiplexing (OFDM) symbols allocated to the PDSCH in an LTE subframe. These downlink transmissions may be referred to as sub-subframe (SSF) transmissions. Acknowledging these sub-subframe (SSF) downlink transmissions in a way that fully enables the latency benefits possible with SSF transmissions, however, requires modifications to uplink resource allocation and uplink control channels. For example, the LTE PUCCH needs to occupy less than the 1 ms uplink subframe. In addition to shorted uplink PUCCH formats, resource allocation and multiplexing can solve the issue of acknowledging downlink transmissions that use the sPDSCH, while keeping backwards compatibility with the current PUCCH structure in LTE. Taken together or separately, various embodiments described herein may be used in such a way that both legacy UEs and new UEs use PUCCH in the same way in a system that allows simultaneous use of subframes with 1-millisecond timing and SSFs with, e.g., 0.5-millisecond timing. This simplifies UE design and network design.
According to some embodiments, a method, in a wireless device that receives a data transmission in a first subframe and acknowledges that transmission with ACK/NACK feedback in a subsequent subframe, includes receiving a first data transmission from a second wireless device in a first subframe interval, and transmitting HARQ feedback and/or CSI to the second wireless device in a subsequent subframe interval, within a duration that is less than a maximum transmission duration that is possible within the subsequent subframe interval. For example, the HARQ feedback and/or CSI may be transmitted by an LTE UE using an SSF allocation of downlink resources that is less than a TTI of the subsequent subframe. This SSF allocation may be one of two slots in the subsequent subframe, for example.
According to some embodiments, a method, in a wireless device that transmits a data transmission in a first subframe and receives an acknowledgement of that transmission in ACK/NACK feedback received in a subsequent subframe, includes transmitting a first data transmission to a second wireless device in a first subframe interval, and receiving HARQ feedback and/CSI from the second wireless device in a subsequent subframe interval, within a duration that is less than a maximum transmission duration that is possible within the subsequent subframe interval. The wireless device may be an LTE eNodeB.
According to some embodiments, a wireless device has a transceiver circuit and a processing circuit configured to perform either of these methods. Variations of the above-described methods, as well as corresponding apparatuses, computer program products, computer readable medium and functional implementations are described in detail below. Thus, the disclosed techniques are not limited to the above-summarized features and advantages. Indeed, those skilled in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings.
As noted above, when it comes to reducing packet latency, one area to address is the reduction of transport time of data and control signaling, e.g., by addressing the length of a transmit-time-interval (TTI), and the reduction of processing time of control signaling, e.g., by reducing the time it takes for a UE to process a grant signal.
In a typical UE design, the UE receives an entire subframe before any processing of that subframe is started. For channel estimation purposes, there may be some look-ahead to obtain cell-specific reference symbols (CRS) from the following subframe, which will introduce a delay of one or a few symbols. Then, the demodulation of symbols in the received subframe and generation of soft values will take place, followed by turbo decoding. The time required for these operations is generally dependent on the size of the received transport block, and the processing chain of the UE is designed to allow for reception in the worst-case scenario, i.e., a scenario involving a maximum-size allocation and the most complex modulations and code rates, possibly on each of a number of aggregated component carriers. Further, the UE needs to complete processing on all of these blocks with an additional margin, as given by the maximum timing advance value. The timing advance is configured from the network to make the signals from different UEs arrive at the eNodeB at similar time instants—for large cell sizes, the timing advance may be specified to values up to 0.7 milliseconds, corresponding to the round-trip time of radio signals given a cell radius of about 100 kilometers.
One way to reduce the latency associated with decoding the data is to change the channel estimator and not employ any form of look ahead. The channel estimate is then available earlier, which allows demodulation and decoding to begin earlier. Similarly, since the time needed for turbo decoding depends on the code block size, latency can be further reduced by reducing the code block size. Hence, if the code block size (or equivalently the transport block size) is reduced, the decoding result will be available earlier (for a given decoding capability, in terms of number of parallel decoders). If instead of transmitting a single large code block of length 6000 bits once every millisecond, the system transmits two consecutives blocks of length 3000 bits every 0.5 milliseconds, the decoding latency for each block may be reduced by roughly one-half, while still sustaining the bit rate at roughly the same complexity. It should be noted that some performance degradations are expected from shorter block lengths and/or from eliminating look-aheads for channel estimation. In general, tradeoffs between latency and receiver performance can be expected. However, these tradeoffs need not necessarily diminish system or end user performance.
Given the discussion of receiver processing above, there is an opportunity to reduce the latency for terminal receiver processing by allowing for downlink transmissions, i.e., transmissions on the physical downlink shared channel (PDSCH), that are shorter than the current transmit-time interval (TTI) of one subframe in LTE systems, i.e., that occupy fewer than all of the orthogonal frequency-division multiplexing (OFDM) symbols allocated to the PDSCH in a subframe. These downlink transmissions may be referred to as sub-subframe (SSF) transmissions. In other words, the LTE system could be modified to not only allow PDSCH assignments covering all OFDM symbols in a 1 ms subframe, but also have PDSCH assignments with shorter durations, covering a lower number of consecutive OFDM symbols within a subframe. The duration of the assignment might vary from subframe to subframe.
An example of this approach is illustrated in
In future versions of the LTE standard, it is expected that terminals may have PDSCH assignments that, in the time domain, span a subset of the OFDM symbols in a subframe, rather than all of the OFDM symbols used for PDSCH (i.e., all symbols except symbols used by PDCCH and other good signals). Note that
There are several different ways in which such resource assignments, which might be referred to as “sub-subframe assignments,” can be conveyed to the terminal. One way is via a PDCCH control message transmitted every one millisecond, using a modified version of the Downlink Control Information (DCI) message formats standardized by the 3GPP as of Release 11 of the specifications for LTE. Another is to use an entirely new form of PDCCH, also referred to as “short PDCCH” (SPDCCH), one or more of which may be transmitted in any given subframe.
For illustrative purposes, several embodiments will be described in the context of an LTE system. Those skilled in the art will appreciate, however, that several embodiments of the disclosed techniques may be more generally applicable to other wireless communication systems, including, for example, WiMax (IEEE 802.16) systems. Further, while the following description of certain embodiments of the invention will focus on downlink resource assignments and the corresponding HARQ transmissions in the uplink, it should be appreciated that the described techniques may be applied in the reverse direction, i.e., for uplink resource assignments and data transmissions and corresponding HARQ transmissions in the downlink. Likewise, the same techniques may be adapted for peer-to-peer transmissions, in some embodiments, where there is no “uplink” or “downlink” per se.
The mobile communication network 10 comprises a plurality of geographic cell areas or sectors 12. Each geographic cell area or sector 12 is served by a base station 30, which is referred to in LTE as a NodeB or Evolved NodeB (eNodeB). One base station 30 may provide service in multiple geographic cell areas or sectors 12. The mobile terminals 50 receive signals from base station 30 on one or more downlink (DL) channels, and transmit signals to the base station 30 on one or more uplink (UL) channels.
LTE uses Orthogonal Frequency Division Multiplexing (OFDM) in the downlink and Discrete Fourier Transform (DFT)-spread OFDM in the uplink. The basic LTE downlink physical resource can be viewed as a time-frequency grid.
Resource elements are grouped into resource blocks, where each resource block in turn consists of twelve OFDM subcarriers, within one of two equal-length slots of a subframe.
Downlink transmissions are dynamically scheduled, in that in each subframe the base station transmits control information identifying the mobile terminals to which data is transmitted and the resource blocks in which that data is transmitted, for the current downlink subframe. This control signaling is typically transmitted in a control region, which occupies the first one, two, three, or four OFDM symbols in each subframe. A downlink system with a control region of three OFDM symbols is illustrated in
As shown in
For error control, LTE uses HARQ, where, after receiving downlink data in a subframe, the mobile terminal attempts to decode it and reports to the base station whether the decoding was successful (ACK) or not (NACK) via a Physical Uplink Control Channel (PUCCH). In the event of an unsuccessful decoding attempt, the base station (eNodeB) can retransmit the erroneous data. Similarly, the base station can indicate to the UE whether the decoding of the PUSCH was successful (ACK) or not (NACK) via the Physical Hybrid ARQ Indicator CHannel (PHICH).
In addition to the hybrid-ARQ ACK/NACK information transmitted from the mobile terminal to the base station, uplink control signaling from the mobile terminal to the base station also includes reports related to the downlink channel conditions, referred to generally as channel-state information (CSI) or channel-quality information (CQI). This CSI/CQI is used by the base station to assist in downlink resource scheduling decisions. Because LTE systems rely on dynamic scheduling of both downlink and uplink resources, uplink control-channel information also includes scheduling requests, which the mobile terminal sends to indicate that it needs uplink traffic-channel resources for uplink data transmissions.
In scenarios without downlink carrier aggregation, when a UE has data to transmit on PUSCH, it multiplexes the uplink control information with data on PUSCH. Thus, a UE only uses PUCCH for signaling this uplink control information when it does not have any data to transmit on PUSCH. Accordingly, if the mobile terminal has not been assigned an uplink resource for data transmission, Layer 1/Layer 2 (L1/L2) control information, including channel-status reports, hybrid-ARQ acknowledgments, and scheduling requests, is transmitted in uplink resources (resource blocks) specifically assigned for uplink L1/L2 control on the Physical Uplink Control CHannel (PUCCH), which was first defined in Release 8 of the 3GPP specifications (LTE Rel-8).
As illustrated in
The reasons for locating the PUCCH resources at the edges of the overall available spectrum are two-fold. First, together with the frequency hopping described above, this maximizes the frequency diversity experienced by the control signaling, which can be encoded so that it is spread across both resource blocks. Second, assigning uplink resources for the PUCCH at other positions within the spectrum, i.e., not at the edges, would fragment the uplink spectrum, making it difficult to assign very wide transmission bandwidths to a single mobile terminal while still retaining the single-carrier property of the uplink transmission.
When a UE has ACK/NACK to send in response to a downlink PDSCH transmission, it determines which PUCCH resource to use from the PDCCH transmission that assigned the PDSCH resources to the UE. More specifically, an index to the PUCCH resource for the UE is derived from the number of the first control channel element used to transmit the downlink resource assignment. When a UE has a scheduling request or CQI to send, it uses a specific PUCCH resource that has been pre-configured for the UE by higher layer signaling.
Depending on the different types of information that PUCCH is to carry, several different PUCCH formats may be used. The data-carrying capacity of a pair of resource blocks during one subframe is more than is generally needed for the short-term control signaling needs of one mobile terminal. Therefore, to efficiently exploit the resources set aside for control signaling, multiple mobile terminals can share the same physical control channel resource. This is done by assigning each of several mobile terminals different orthogonal phase-rotations of a cell-specific, length-12, frequency-domain sequence and/or different orthogonal time-domain cover codes. By applying these frequency-domain rotations and/or time-domain covering codes to the encoded control channel data, as many as 36 mobile terminals can share a given physical control channel resource, in some circumstances.
Several different encoding formats have been developed by 3GPP to encode different quantities and types of uplink control channel data, within the constraints of a single physical control channel resource. These several formats, known generally as PUCCH Format 1, PUCCH Format 2, and PUCCH Format 3, are described in detail at pages 226-242 of the text “4G LTE/LTE-Advanced for Mobile Broadband,” by Erik Dahlman, Stefan Parkvall, and Johan Sköld (Academic Press, Oxford UK, 2011), and are summarized briefly below.
PUCCH resources carry uplink control information (UCI) that includes scheduling requests (SR), hybrid-ARQ acknowledgements and channel state information (CSI reports). There exist 3 different PUCCH formats. PUCCH format 1, 1a and 1b carry SRs and one or two HARQ ACK/NACKs, respectively. Multiplexing of SR with HARQ feedback is also possible. PUCCH format 2 can carry up to 11 bits of information is used for CSI feedback. 2a and 2B may carry additionally one or two HARQ ACK/NACK bits, respectively. PUCCH format 3 was introduced in Release 11 and may carry up to 22 bits and may multiplex all three types of UCI.
PUCCH formats 1 and 2 use orthogonal phase rotations of a length-12 frequency domain sequence as the allocation is fixed to 12 subcarriers. PUCCH format 1 uses in addition orthogonal cover codes. This enables multiplexing multiple users to share uplink resources when same PUCCH format is used. It is also possible to multiplex PUCCH format 1 and 2 but some phase rotation need to be reserved as “guard period”.
PUCCH format 3 uses DFT-spread OFDM which is the same as used for UL data transmissions. Thus, with this PUCCH format 3 UL simultaneous transmission of PUCCH and PUSCH are possible as the DFTS-OFDM is a multicarrier transmission. For the format 3, length-5 orthogonal sequence is used to enable multiplexing up to five users on same resources. Due to different structures, PUCCH format 3 may not be multiplexed with formats 1 and 2.
The structure of PUCCH formats 1, 1a, and 1b, which are used to transmit scheduling requests and/or ACK/NACK, is based on cyclic shifts of a Zadoff-Chu sequence, and can be found in 3GPP TS 36.211, section 5.4.1. One or two bits are transmitted. First the bit(s) are converted to a complex-valued number d(0) according to Table 5.4.1.-1. The resulting modulated data symbol is multiplied with the cyclically Zadoff-Chu shifted sequence, which is a function of angle phi in Table 5.5.2.2-1, and where the cyclic shift is antenna port-specific. The cyclic shift varies from one symbol to another and from one slot to the next. Although twelve different shifts are available, higher-layer signaling may configure UEs in a given cell to use fewer than all of the shifts, to maintain orthogonality between PUCCH transmissions in cells that exhibit high frequency selectivity. After the modulated data symbol is multiplied with the Zadoff-Chu sequence, the result, which corresponds to a SC-FDMA symbol of 12 subcarriers is spread, using an orthogonal spreading sequence. PUCCH formats 1, 1a, and 1b carry three reference symbols per slot (when normal cyclic prefix is used), at SC-FDMA symbol numbers 2, 3, and 4. This leaves four SC-FDMA symbols for information transmission (three in the case of extended cyclic prefix). The SC-FDMA symbol of 12 subcarriers is thus spread over these four SC-FDMA symbols using orthogonal spreading codes from Table 5.4.1.-2. This set is then mapped onto both slots.
PUCCH Formats 1a and 1b refer to PUCCH transmissions that carry either one or two hybrid-ARQ acknowledgements, respectively. A PUCCH Format 1 transmission (carrying only a SR) is transmitted on a UE-specific physical control channel resource (defined by a particular time-frequency resource, a cyclic-shift, and an orthogonal spreading code) that has been pre-configured by RRC signaling. Likewise, PUCCH Format 1a or 1b transmissions carrying only hybrid-ARQ acknowledgements are transmitted on a different UE-specific physical control channel resource. PUCCH Format 1a or 1b transmissions that are intended to carry both ACK/NACK information and a scheduling request are transmitted on the assigned SR resource for positive SR transmission, and are encoded with the ACK/NACK information.
PUCCH Format 1/1a/1b transmissions carry only one or two bits of information (plus scheduling requests, depending on the physical control channel resource used for the transmission). Because channel-state information reports require more than two bits of data per subframe, PUCCH Format 2/2a/2b, as defined in section 5.4.2 of 3GPP TS 36.211, is used for these transmissions. As illustrated in
Formats 2a and 2b carry in addition one or two HARQ ACK/NACK bits, respectively. The bit(s) are converted to a complex number d(10) using the mapping described in Table 5.4.1.1, where 1a->2a and 1b->2b. The information in d(10) is carried such that the complex number is used in the generation of the DMRS sequence of the PUCCH.
For UEs operating in accordance with LTE Release 8 or LTE Release 9 (i.e., without carrier aggregation), it is possible to configure the UE in a mode where it reports ACK/NACK bits and CSI bits simultaneously. If the UE is using normal cyclic prefix, one or two ACK/NACK bits are modulated onto a QPSK symbol, using the mapping described in Table 5.4.1.1, where 1a->2a and 1b->2b, which is mapped onto the second reference signal (RS) resource element in each slot of the PUCCH format 2. If one ACK/NACK bit is modulated on the second RS in each slot, the PUCCH format used by the UE is referred to as PUCCH Format 2a. If two ACK/NACK bits are modulated on the second RS in each slot the PUCCH format used by the UE is referred to as PUCCH Format 2b. If the UE is configured with extended cyclic prefix, one or two ACK/NACK bits are jointly coded with CSI feedback and transmitted together within PUCCH format 2.
As with PUCCH Format 1 transmissions, a pair of resource blocks allocated to PUCCH can carry multiple PUCCH Format 2 transmissions from several UEs, with the separate transmissions separated by the cyclic shifting. As with PUCCH Format 1, each unique PUCCH Format 2 resource can be represented by an index from which the phase rotation and other quantities necessary are derived. The PUCCH format 2 resources are semi-statically configured. It should be noted that a pair of resource blocks can either be configured to support a mix of PUCCH formats 2/2a/2b and 1/1a/1b, or to support formats 2/2a/2b exclusively.
3GPP's Release 10 of the LTE standards (LTE Release 10) has been published and provides support for bandwidths larger than 20 MHz, through the use of carrier aggregation. One important requirement placed on the development of LTE Release 10 specifications was to assure backwards compatibility with LTE Release 8. The need for spectrum compatibility dictated that an LTE Release 10 carrier that is wider than 20 MHz should appear as a number of distinct, smaller bandwidth, LTE carriers to an LTE Release 8 mobile terminal. Each of these distinct carriers can be referred to as a component carrier.
For early LTE Release 10 system deployments in particular, it can be expected that there will be a relatively small number of LTE Release 10-capable mobile terminals, compared to many “legacy” mobile terminals that conform to earlier releases of the LTE specifications. Therefore, it is necessary to ensure the efficient use of wide carriers for legacy mobile terminals as well as Release 10 mobile terminals, i.e., that it is possible to implement carriers where legacy mobile terminals can be scheduled in all parts of the wideband LTE Release 10 carrier.
One straightforward way to obtain this is by means of a technique called carrier aggregation. With carrier aggregation, an LTE Release 10 mobile terminal can receive multiple component carriers, where each component carrier has (or at least may have) the same structure as a Release 8 carrier. Release 10 of the LTE standards specifies support of up to five aggregated carriers, where each carrier is limited to one of six radio-frequency (RF) bandwidths, namely 1.4, 3, 5, 10, 15, and 20 MHz.
The number of aggregated component carriers as well as the bandwidth for each individual component carrier may be different for uplink and downlink. In a symmetric configuration, the number of component carriers in downlink and uplink is the same, whereas the numbers of uplink and downlink carriers differ in an asymmetric configuration.
During initial access, an LTE Release 10 mobile terminal behaves similarly to an LTE Release 8 mobile terminal, requesting and obtaining access to a single carrier for the uplink and downlink. Upon successful connection to the network a mobile terminal may—depending on its own capabilities and the network—be configured with additional component carriers in the uplink and downlink.
Even if a mobile terminal is configured with additional component carriers, it need not necessarily monitor all of them, all of the time. This is because LTE Release 10 supports activation of component carriers, as distinct from configuration. The mobile terminal monitors for PDCCH and PDSCH only component carriers that are both configured and activated. Since activation is based on Medium Access Control (MAC) control elements—which are faster than radio resource control (RRC) signaling—the activation/de-activation process can dynamically follow the number of component carriers that is required to fulfill the current data rate needs. All but one component carrier—the downlink Primary component carrier (downlink PCC)—can be deactivated at any given time.
When carrier aggregation is used in LTE, one uplink carrier is designed to carry the HARQ-ACK/NACK bits for all downlink-carrier PDSCH transmissions. To enable the possibility to transmit more than four bits of A/N, PUCCH Format 3, which is defined in section 5.4.2A of 3GPP TS 36.211, can be used. In frequency-division duplex (FDD) scenarios, each downlink carrier can generate one or two HARQ ACK/NACK bits per scheduled subframe, depending on whether multiple-input multiple-output (MIMO) operation is enabled for that carrier. In time-division duplex (TDD) scenarios, the number of HARQ ACK/NACK bits also depends on how many downlink subframes a given uplink subframe should carry HARQ ACK/NACK bits for.
PUCCH Format 3, which is designed for scenarios when more than four bits of information must be transmitted, is based on DFT-spread OFDM. PUCCH Format 3 carries 48 channel coded bits, which are first QPSK modulated after scrambling using Table 7.1.2.1-1. The channel coded bits are formed from the (32, 0) code given in Table 5.2.2.6.4-1 by a circular repetition of the codewords. There are now 12 QPSK symbols per slot to be transmitted. The 12 QPSK symbols are input to DFT-precoder which outputs one OFDM symbols. There are five OFDM symbols available in a slot as two OFDM symbols are used for DMRS (normal cyclic prefix). Thus the one OFDM symbol may be spread over five OFDM symbols using orthogonal sequence from Table 5.4.2A-1. In addition to the orthogonal spreading, also a cyclic shift is applied to randomize interference between cells. In second slot, length four orthogonal sequence may be applied in case the last OFDM symbol is used for sounding reference signal. Note that when more than 11 ACK/NACK bits are encoded, the bits are split in two parts, separately encoded into 32 bit codewords which are then truncated to 24 bits and multiplexed together to form a 48 bit codeword.
For the reference signals (RS), cyclic-shifted constant-amplitude zero-autocorrelation (CAZAC) sequences can be used. For example, the computer optimized sequences in 3GPP TS 36.211, “Physical Channels and Modulation,” can be used. To improve orthogonality among reference signals even further, an orthogonal cover code of length two could be applied to the reference signals. However, this approach is not used in Releases 10 or 11 of the LTE specifications.
If the number of ACK/NACK bits exceeds eleven, then the bits are split into two parts and two RM encoders are used, one for each of the two parts. This is known as the dual-RM code. Up to twenty ACK/NACK bits (plus one SR bit) can be supported by PUCCH Format 3 in this manner Each encoder in the dual-RM code outputs twenty-four bits which are converted to twelve QPSK symbols, and the resulting two sets of twelve QPSK symbols are distributed across the slots and interleaved over the subcarriers so that the twelve symbols from the first encoder are mapped to odd subcarriers and the twelve symbols from the second encoder are mapped to even subcarriers, where six odd and six even sub-carriers are assumed per slot. (In this mapping operation, a cell-, slot-, and symbol-specific cyclic shift of the symbols in the time domain is included, to provide inter-cell interference randomization.) The twelve QPSK symbols per slot are then spread across the five DFTS-OFDM symbols, using one out of five orthogonal cover codes, as in the single-RM code case.
Some details of the encoding and multiplexing approach described above are shown in
The operation of the multiplexing scheme illustrated in 0,
1,
2, . . . ,
23 the output sequence from the second encoder. NscRB=12 is the number of subcarriers per resource block. The output bit sequence b0, b1, b2, . . . , bB-1, where B=4·NscRB, is obtained by the alternate concatenation of the bit sequences {tilde over (b)}0, {tilde over (b)}1, {tilde over (b)}2, . . . {tilde over (b)}23 and
0,
1,
2, . . . ,
23 as shown in the following pseudo-code:
j , bi+3 =
j+1
b
i
={tilde over (b)}
j
, b
i+1
={tilde over (b)}
j+1
b
i+2=j, bi+3=
j+1
i=i+4
j=j+2
end while.
The current PUCCH region is depicted in
The exact resource used for a particular UL subframe is determined by a variable m (in
The variable m is a function of higher layer configured or fixed parameters and a resource index. The resource index is also different for each format and is derived differently depending on for example how the DL assignment has been given [3GPP TS 36.213, section 10.1.2]. For example, if DL downlink control information (DCI) was given via PDCCH, for format 1, the resource index is a sum of the lowest CCE index used to construct the PDCCH and a higher layer configured parameter. This resource index also determines which of the multiplexing sequences are used for each format. Thus the uplink scheduling is dynamically controlled through the resource indexes within the higher layer configured resources.
In legacy LTE systems, i.e., those LTE systems operating according to Release 11 or earlier of the 3GPP specifications, DL scheduling is done on a 1-millisecond subframe basis. The scheduling messages are sent each subframe, and the granted resource occupies all of the OFDM symbols allocated to the PDSCH in the resource block pairs allocated to the UE in the resource grant. The processing time allowed to the terminal for completing all processing related to a transmission in a given subframe is 3 milliseconds, less the timing advance. The specifications for LTE thus specify that the ACK/NACK in response to a PDSCH transmission in subframe n should be transmitted in the UL in subframe n+4, no matter the size of the transport block or when the assignment ends. This is illustrated in
In a system in which sub-subframe assignments are possible, this rigid approach is wasteful, since the processing time required for the terminal depends on the duration of the PDSCH assignment, as well as the size of the transport block. This means that when a UE detects that the assignment is scheduled only on a consecutive subset of the OFDM symbols in a subframe, referred to as a “sub-subframe”, it is in principle able to transmit the ACK/NACK feedback earlier than what would be possible for the case when all symbols in the subframe are used.
The techniques detailed below are based on an assumption that an LTE terminal can receive PDSCH resource assignments on all or on only a subset of OFDM symbols within a 1-millisecond subframe and that the resource assignments can vary from one subframe to another. More generally, it will be appreciated that the techniques may be applied to communications between one wireless device and another, where transmissions of data from a first wireless device to a second wireless device in a given subframe can occupy a duration that is less than a maximum data transmission duration that is possible within the subframe, where the term “subframe” may be understood to refer to a default transmission-time interval (TTI) in a given wireless system.
There are three problems related to the concept of short downlink subframes. The first problem relates to latency reduction, and the second relates to multiplexing of UL resources for SSF and legacy users. The third problem is related to the use case of the sub-subframe (SSF) concept where the UL feedback channel allocation is longer than DL sub-subframe, such that one UL resource should carry ACK/NACK for multiple DL SSFs. That is a form of ACK/NACK bundling.
As can be seen in
The problem for resource allocations can be seen as follows. In
The 3GPP specification 3GPP TS 36.211 provides a rather complicated set of rules enables dynamic scheduling of UL PUCCH resources within an UL subframe n by controlling the DL scheduling of DL subframe n−4. Thus, the UL multiplexing (assuming it is possible), of SSF ACK/NACK and legacy UCI might bring in some scheduling complications or even restrictions.
A third problem is related to the use case where the UL feedback channel allocation is longer than DL sub-subframe, such that one UL resource needs to carry ACK/NACK for multiple DL SSFs. Similar situations may occur if a new RAT is introduced in one direction and combined with LTE in the other direction. For instance, a new radio-access technology in the downlink combined with legacy LTE in the uplink. Such a deployment would give a downlink performance boost with better uplink coverage than with same length UL and DL sub-subframes.
Accordingly, to acknowledge the sub-subframe DL transmissions in such a way that the latency benefits possible with SSF downlink transmissions are fully enabled, the uplink resource allocation and the UL control channels need modifications. In short, the PUCCH needs to occupy less than the 1 ms UL subframe. Thus, resource allocations and possible multiplexing, in addition to shorted UL PUCCH formats, are discussed. This solves the issue of acknowledging downlink transmissions that use the sPDSCH while keeping backwards compatibility with the current PUCCH structure in LTE. Taken together or separately, the techniques described herein may be used in such a way that both legacy UEs and new UEs use PUCCH in the same way in a system that allows simultaneous use of sub frames with 1-millisecond timing and SSFs with, e.g., 0.5-millisecond timing. This simplifies the UE design and the network design.
The short PUCCH, or “sPUCCH,” described herein may have a signal form similar to the legacy PUCCH formats 1, 2, which are single-carrier based, or format 3, which is DFTS-OFDM based. The key difference between the single carrier (SC) and multicarrier (MC) based sPUCCH solutions is that non-consecutive frequency domain allocations are possible only with the MC sPUCCH solution.
For both-single carrier and multicarrier sPUCCH solutions, the simplest solution, which can also be called the minimum impact solution, is a slot based UL.
For the MC based format on right side of the figure, one user may occupy a slot simultaneously from two sides of the spectrum. Here users m=2 and m=3 occupy two slots. It should be noted that it is not necessary to occupy non-consecutive frequency allocations with the MC-format. However, it is possible, and thus the feature allows more flexible design of the sPUCCH.
Both SC and MC based solutions may be generalized to an uplink allocation that may be any number of symbols from 1 to 14.
Depending on the exact design of the sPUCCH, length and cover code design, multiplexing with legacy PUCCH may be possible. For example, a slot-based SC sPUCCH may be multiplexed with legacy PUCCH format 1 or 2, and slot-based MC sPUCCH may be multiplexed with legacy PUCCH format 3.
In some cases, the multiplexing with legacy PUCCH formats is not preferred. For example, if the number of legacy users is high, it might be more efficient to multiplex only legacy users together as the length of the UL transmissions are the same. For this case, one possibility is to define a new sPUCCH region next to the existing PUCCH region in the frequency domain such that SSF-enabled UEs would be scheduled in that narrow frequency region. Within this region, different time and frequency domain multiplexing options are possible
In some embodiments of the techniques and apparatus described herein, the uplink allocation, that is sPUCCH, may be any number of symbols from 1 to 14. Different time and frequency multiplexing options with frequency hopping may be used. The signal format for the sPUCCH may be single carrier type similar to legacy sPUCCH format1/2 or DFTS-OFDM like legacy PUCCH format 3.
Single Carrier sPUCCH (Format1&2)
Slot Based—
A minimum impact UL would be a slot based UL where the existing PUCCH format 1 or 2 is used but only in one of the slots, i.e., skipping the frequency hopping aspect within a subframe. The left hand side of
For format 2, a new channel code is needed that maps information bits into 10 channel coded bits instead of 20. One such code can be formed by puncturing a sub code of the block code (20, A), given in Table 5.2.3.3-1. By taking the base sequences {Mi,0, Mi,1, Mi,2, Mi,3, Mi,4} for i=0, . . . , 9, we obtain a (10, 5) code with minimum distance 4. The resulting code is presented in Table 1. Then the same procedure for one slot may be used. That is, 5 CSI bits may be carried in addition to one to two HARQ ACK/NACK bits with the format 2 like slot base sPUCCH. These 5 bits may be also HARQ ACK/NACK bits.
Multiplexing with slot length UL and legacy format 1 and 2 should be possible by applying the existing Equation (1) and by mapping the slot number n_s to a corresponding downlink slot.
1-7 SC-FDMA Symbols—
A generalization of this case is to use 1-7 SC-FDMA symbol-length sPUCCH. Similar to the HARQ ACK/NACK indication for format 2a and 2b, the ACK/NACK indication could be carried in a phase shift of the DMRS sequence. Thus a simple 1-2 OFDM symbol length sPUCCH could consist of only one or two DMRS sequences.
In general, per SC-FDMA symbol, the length 12 sequence of Table 5.5.1.2.-1 gives multiplexing opportunities between the single carrier sPUCCH SC-FDMA symbol and an SC-FDMA symbol of legacy PUCCH of format 1 or 2. When format 2 is used for the 2-7 SC-FDMA symbol length sPUCCH, the constraining issue is the channel coding. Two channel coded bits (one complex symbol) can be sent within one SC-FDMA symbol of the sPUCCH.
Further, using similar structure as format 1a and 1b, any length between 2-7 is possible assuming one to two symbols are for the DMRS sequence. In this format, one complex symbols is first spread over 12 subcarriers using Table 5.5.1.2.-1 and then possibly spread over multiple SC-FDMA symbols. The number of SC-FDMA symbols define the robustness as a result of the length of the orthogonal cover code.
Multiplexing for SC sPUCCH—
The length of the cover code also defines the multiplexing capacity. For example, if there are two SC-FDMA symbols not carrying DMRS, the cover codes are for example [1 1] and [1 −1]. This means that two sPUCCH users using same length 12 cover codes may be multiplexed using the mentioned cover codes on the two SC-FDMA symbols. Multiplexing with a legacy user that has cover code [1 1 1 1] is possible such that one sPUCCH user is multiplexed on the first two SC-FDMA symbols and second user is multiplexed with the last two OFDM users. Both sPUCCH users use cover code [1 −1] and have one symbol for DMRS. Table 2 depicts this example. Note that same amount of information is carried with legacy PUCCH format 1 and this SC sPUCCH but the transmission of the legacy PUCCH is more robust.
Frequency Diversity for SC sPUCCH—
For SC sPUCCH, frequency domain diversity is possible by designing a slot length sPUCCH that consists of two parts, [1 −1 DMRS] and [DMRS 1 −1], and where the first part is sent over first three SC-FDMA symbols (symbols 0-2) on one end of the spectrum and the latter part is sent over last three SC-FDMA symbols of the slot (symbols 4-6).
Multicarrier Type sPUCCH (Format 3)
Slot Based—
DFTS-OFDM maybe a valid option for sPUCCH for two reasons. One is to enable simultaneous transmission with UL data (PUSCH) and other is to enable simultaneous transmission on non-contiguous frequency allocations as was depicted in
1-7 OFDM Symbols—
A modified version of PUCCH format 3 may be used, with as few as 1 OFDM symbols used to carry an ACK/NAK bit. One approach for 1 OFDM symbol long ACK/NAK is to use two different length-12 sequences, one for ACK and one for NAK (=orthogonal signal constellation instead of antipodal, comes at a cost in link budget). For >1 OFDM symbol long ACK/NAK, one can use 1 RS and up to 11 ACK/NAK bits can be transmitted by using a punctured length 24 code from the code given in Table 5.2.2.6.4-1. In particular, by puncturing the first 8 bits in the code, we obtain a length 24 code with minimum distance 7. The codewords from this code can then be used as in PUCCH format 3 in a single slot. The code is given in Table 3.
An alternative to this channel code is to use the current truncation of 32 bit codewords to 24 bit codewords that is used in legacy today when encoding more than 11 ACK/NACK bits in PUCCH format 3.
For the DFT based sPUCCH of length 2-7, the same channel coding approach can be used as was used for the slot-based approach described above. Differences come to the orthogonal sequence length and thus multiplexing capability.
Multiplexing for MC sPUCCH—
We can multiplex one legacy PUCCH format 3 user with three MC sPUCCH users, for example:
The only legacy UE: [w0,w1,w2,w3,w4]=[1 1 1 1 1]
UE1: [w3,w4]=[−1 1]
UE2: [w0,w1,w2]=[1e
UE3: [w0,w1,w2]=[1e
Table 4 depicts the multiplexing example with legacy user and Table 5 gives multiplexing example of only MC sPUCCH. Note that when multiplexing only MC sPUCCH users, that is, when there is separate frequency allocation for sPUCCH users, there is more freedom of selecting in which symbols the DMRS sequence is.
Frequency Diversity for MC sPUCCH—
For MC sPUCCH, frequency domain diversity is possible, similarly as for SC sPUCCH. In addition, as it is possible to send MC sPUCCH at multiple non-contiguous frequency allocations, the information bits may be scrambled over an MC sPUCCH that has multiple frequency allocations. Another option is to repeat the same channel coded bits in both slots, for example as shown for user m=2 in the right hand side of
In legacy LTE systems, if the transmission time of ACK/NACK coincides with a transmission time of CQI or SR, there exist different dropping rules in section 7.2 of 3GPP TS 36.213. With a short subframe (SSF), a couple of alternatives exist to handle this situation:
1. CQI or SR Transmitted on PUCCH, SSF ACK/NACK Transmitted on sPUCCH
2. CQI or SR and SSF ACK/NACK(s) are Transmitted on PUCCH
3. CQI or SR and SSF ACK/NACK on sPUCCH
4. CQI or SR and SSF ACK/NACK on sPUCCH with a Simultaneous PUSCH/sPUSCH Transmission
In one example, we have downlink granularity of half of the uplink granularity. In
In view of the detailed example embodiments described above, it will be appreciated that
As shown at block 1710, the method comprises receiving a first data transmission from a second wireless device in a first subframe interval. It will be appreciated that in some embodiments, the first data transmission is received within a duration that is less than a maximum data transmission duration that is possible within the first subframe interval, e.g., using a sub-subframe allocation of downlink resources. The method further includes, as shown at block 1720, transmitting HARQ feedback and/or CSI to the second wireless device in a subsequent subframe interval, within a duration that is less than a maximum transmission duration that is possible within the subsequent subframe interval.
In some embodiments, the length of the predetermined subframe interval is 1 millisecond and consists of 14 OFDM symbols.
In some embodiments, the transmission of the HARQ feedback and/or CSI occupies exactly one of two slots in the subsequent subframe interval. In some embodiments, transmitting the HARQ feedback and/or CSI comprises: converting one or two bits of HARQ data to a complex-valued number; spreading the complex-valued number over twelve subcarriers using a cyclically-shifted length-12 sequence, to form an array of twelve complex numbers; spreading the array of twelve complex numbers to four SC-FDMA symbols of twelve subcarriers, using a length-four orthogonal spreading code; and mapping the four SC-FDMA symbols to symbols of the one of two slots. In other embodiments, transmitting the HARQ feedback and/or CSI comprises: encoding a plurality of HARQ bits and/or CSI bits to 10 bits, using a channel code; scrambling the encoded bits; modulating the scrambled, encoded bits, using QPSK modulation, to form five QPSK symbols; multiplying each of the five QPSK symbols with a cyclically-shifted length-12 sequence, to obtain five arrays of twelve QPSK symbols; and mapping each of the five arrays of twelve QPSK symbols to a corresponding SC-FDMA symbol of the one of two slots. In some of these latter embodiments, the method further comprises: converting one or two HARQ bits to a complex number; using the complex number to generate a DMRS sequence; and mapping symbols from the generated DMRS symbol sequence to two SC-FDMA symbols of the one of two slots.
In some embodiments, DFT-spread OFDM is used, where the resulting sPUCCH occupies a single slot. In some of these embodiments, transmitting the HARQ feedback and/or CSI comprises: encoding a plurality of HARQ feedback bits and/or CSI bits to 24 bits, using a channel code; scrambling the encoded bits and modulating the scrambled, encoded bits, using QPSK modulation, to form twelve QPSK symbols; inputting the twelve QPSK symbols to a DFT precoder, to form a DFT-spread OFDM symbol (DFTS-OFDM); spreading the OFDM symbol, using a length-five orthogonal spreading sequence, to form five DFTS-OFDM symbols; and transmitting the five DFTS-OFDM symbols in OFDM symbols of the one of two slots.
In some embodiments, sPUCCH may occupy less than a single slot. In some embodiments, then, the subsequent subframe interval consists of a plurality of transmission symbols, and wherein the transmission of the HARQ feedback and/or CSI occupies fewer than all of the transmission symbols in the subsequent subframe interval. In some of these embodiments, the subsequent subframe interval consists of two slots, each slot comprising a plurality of transmission symbols, and wherein the transmission of the HARQ feedback and/or CSI is confined to one of the two slots and occupies fewer than all of the transmission symbols in the one of the two slots.
In some of these embodiments, transmitting the HARQ feedback and/or CSI comprises: converting one or two bits of HARQ data to a complex-valued number; spreading the complex-valued number over twelve subcarriers using a cyclically-shifted length-12 sequence, to form an array of twelve complex numbers; spreading the array of twelve complex numbers to two or more SC-FDMA symbols of twelve subcarriers, using an orthogonal spreading code; and mapping the two or more SC-FDMA symbols to symbols of the subsequent subframe interval. In other embodiments, transmitting the HARQ feedback and/or CSI comprises: converting one or two HARQ bits to a complex number; using the complex number to generate a DMRS sequence; and mapping symbols from the generated DMRS symbol sequence to one or more orthogonal SC-FDMA symbols of the subsequent subframe interval.
In still other embodiments, transmitting the HARQ feedback and/or CSI comprises: encoding a plurality of HARQ feedback bits and/or CSI bits to 24 bits, using a channel code; scrambling the encoded bits and modulating the scrambled, encoded bits, using QPSK modulation, to form twelve QPSK symbols; inputting the twelve QPSK symbols to a DFT precoder, to form an OFDM symbol; spreading the OFDM symbol, using an orthogonal spreading sequence, to form two or more spread OFDM symbols; and transmitting the two or more spread OFDM symbols in OFDM symbols of the subsequent subframe interval. In some of these and in some other embodiments where a multi-carrier sPUCCH is used, transmitting the HARQ feedback and/or CSI comprises transmitting HARQ feedback information and/or CSI information simultaneously using two disjoint frequency resource regions.
In some embodiments of the method 1700 shown in
As shown at block 1810, the method includes transmitting a first data transmission to a second wireless device in a first subframe interval. In some instances or in some embodiments, the first data transmission is transmitted within a duration that is less than a maximum data transmission duration that is possible within the first subframe interval. As shown at block 1820, the method further includes receiving HARQ feedback and/or CSI from the second wireless device in a subsequent subframe interval, within a duration that is less than a maximum transmission duration that is possible within the subsequent subframe interval.
In some embodiments, the length of the subsequent subframe interval corresponds to an interval at which scheduling information for transmissions to the second wireless device is exchanged between the first and second wireless devices.
In some embodiments, the received HARQ feedback and/or CSI occupies exactly one of two slots of the subsequent subframe interval. In some of these embodiments, receiving the HARQ feedback and/or CSI comprises: de-mapping four SC-FDMA symbols of twelve subcarriers from symbols of the one of two slots; de-spreading an array of twelve complex numbers from the four SC-FDMA symbols, using a length-four orthogonal spreading code; de-spreading a complex-valued number from the array of twelve complex numbers, using a cyclically-shifted length-12 sequence; and converting the complex-valued number to one or two bits of HARQ data. In others of these embodiments, transmitting the HARQ feedback and/or CSI comprises: de-mapping each of five arrays of twelve QPSK symbols from a corresponding SC-FDMA symbol of the one of two slots; dividing each of the five arrays of twelve QPSK symbols with a cyclically-shifted length-12 sequence, to obtain five QPSK symbols; de-modulating the five QPSK symbols to obtain a set of ten scrambled, encoded bits, using QPSK modulation; unscrambling the scrambled, encoded bits to obtain ten encoded bits; and decoding the ten encoded bits to obtain a plurality of HARQ bits and/or CSI bits. In some of these latter embodiments, the method further comprises de-mapping a sequence of DMRS symbols from two OFDM symbols of the one of two slots; and using the sequence of DMRS symbols to obtain a complex number; and converting the complex number to one or two HARQ bits.
In still other embodiments in which a single slot is used, transmitting the HARQ feedback and/or CSI comprises: receiving five spread OFDM symbols in OFDM symbols of the one of two slots; de-spreading the five spread OFDM symbols, using a length-five orthogonal spreading sequence, to obtain a de-spread OFDM symbol; using an IDFT to obtain twelve QPSK symbols from the OFDM symbol; de-modulating the twelve QPSK symbols to obtain 24 scrambled, encoded bits, and de-scrambling the scrambled, encoded bits to obtain 24 encoded bits; and decoding the 24 encoded bits to obtain a plurality of HARQ feedback bits and/or CSI bits.
In some embodiments, the subsequent subframe interval consists of a plurality of transmission symbols, and wherein the received HARQ feedback and/or CSI occupies fewer than all of the transmission symbols of the subsequent subframe interval. In some of these embodiments, the subsequent subframe interval consists of two slots, each slot comprising a plurality of transmission symbols, and wherein the transmission of the HARQ feedback and/or CSI is confined to one of the two slots and occupies fewer than all of the transmission symbols in the one of the two slots. In some of these embodiments, receiving the HARQ feedback and/or CSI comprises: de-mapping two or more SC-FDMA symbols of twelve subcarriers from symbols of the one of two slots; de-spreading an array of twelve complex numbers from the two or more SC-FDMA symbols, using an orthogonal spreading code; de-spreading a complex-valued number from the array of twelve complex numbers, using a cyclically-shifted length-12 sequence; and converting the complex-valued number to one or two bits of HARQ data. In others, receiving the HARQ feedback and/or CSI comprises: de-mapping a DMRS symbol sequence from one or more SC-FDMA symbols of the subsequent subframe interval; using the de-mapped DMRS symbol sequence to obtain a complex number; and converting the complex number to one or two HARQ bits. In still others, receiving the HARQ feedback and/or CSI comprises: receiving two or more spread OFDM symbols in OFDM symbols of the one of two slots; de-spreading the two or more spread OFDM symbols, using an orthogonal spreading sequence, to obtain a de-spread OFDM symbol; using an IDFT to obtain twelve QPSK symbols from the OFDM symbol; de-modulating the twelve QPSK symbols to obtain 24 scrambled, encoded bits, and de-scrambling the scrambled, encoded bits to obtain 24 encoded bits; and decoding the 24 encoded bits to obtain a plurality of HARQ feedback bits and/or CSI bits.
In some embodiments, receiving the HARQ feedback and/or CSI comprises simultaneously receiving HARQ feedback information and/or CSI information from each of two disjoint frequency resource regions. In some embodiments, the method further comprises unbundling, from the received HARQ feedback and/or CSI, one or more HARQ feedback bits for the first data transmission and one or more additional HARQ feedback bits for a second data transmission transmitted to the second wireless device. In some of these latter embodiments, the second data transmission is transmitted in a subframe interval other than the first subframe interval, or is transmitted in a different portion of the first subframe interval than the portion in which the first data transmission is received, or the second data transmission is transmitted to the second wireless device using a different RAT from that used for the first data transmission.
The functions in the various techniques and process flow diagrams discussed above may be implemented using electronic data processing circuitry provided in a mobile terminal and in a base station, or in multiple wireless devices. Each mobile terminal and base station, of course, also includes suitable radio circuitry for receiving and transmitting radio signals formatted in accordance with known formats and protocols, such as the LTE formats and protocols.
The base station 30 also includes one or more processing circuits 32 that are operatively associated with the communication interface circuit 38 and transceiver circuit 36. The processing circuit 32 comprises one or more digital processors 42, e.g., one or more microprocessors, microcontrollers, Digital Signal Processors or DSPs, Field Programmable Gate Arrays or FPGAs, Complex Programmable Logic Devices or CPLDs, Application Specific Integrated Circuits or ASICs, or any mix thereof. More generally, the processing circuit 32 may comprise fixed circuitry, or programmable circuitry that is specially configured via the execution of program instructions implementing the functionality taught herein, or may comprise some mix of fixed and programmed circuitry. The processor 32 may be multi-core.
The processing circuit 32 also includes a memory 44. The memory 44, in some embodiments, stores one or more computer programs 46 and, optionally, configuration data 48. The memory 44 provides non-transitory storage for the computer program 46 and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. By way of non-limiting example, the memory 44 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in the processing circuit 32 and/or separate from the processing circuit 32. In general, the memory 44 comprises one or more types of computer-readable storage media providing non-transitory storage of the computer program 46 and any configuration data 48 used by the base station 30.
The processor 42 may execute a computer program 46 stored in the memory 44 that configures the processor 42 to transmit a first data transmission to a wireless device in a first subframe interval, and to receive HARQ feedback and/or CSI from the wireless device in a subsequent subframe interval, within a duration that is less than a maximum transmission duration that is possible within the subsequent subframe interval. This functionality may be performed by Data Transmission and HARQ Processing Circuit 40 in the processing circuit 32. Of course, the processor circuit 32 may be configured to carry out any of the variants of the methods described above.
The user equipment 50 also includes one or more processing circuits 52 that are operatively associated with the radio transceiver circuit 56. The processing circuit 52 comprises one or more digital processing circuits, e.g., one or more microprocessors, microcontrollers, Digital Signal Processors or DSPs, Field Programmable Gate Arrays or FPGAs, Complex Programmable Logic Devices or CPLDs, Application Specific Integrated Circuits or ASICs, or any mix thereof. More generally, the processing circuit 52 may comprise fixed circuitry, or programmable circuitry that is specially adapted via the execution of program instructions implementing the functionality taught herein, or may comprise some mix of fixed and programmed circuitry. The processing circuit 52 may be multi-core.
The processing circuit 52 also includes a memory 64. The memory 64, in some embodiments, stores one or more computer programs 66 and, optionally, configuration data 68. The memory 64 provides non-transitory storage for the computer program 66 and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. By way of non-limiting example, the memory 64 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in the processing circuit 52 and/or separate from processing circuit 52. In general, the memory 64 comprises one or more types of computer-readable storage media providing non-transitory storage of the computer program 66 and any configuration data 68 used by the user equipment 50.
The processor 62 of the processor circuit 52 may execute a computer program 66 stored in the memory 64 that configures the processor 62 to receive a first data transmission from a second wireless device, such as base station 30, in a first subframe interval, and to transmit HARQ feedback and/or CSI to the second wireless device in a subsequent subframe interval, within a duration that is less than a maximum transmission duration that is possible within the subsequent subframe interval. This structure and functionality may be referred to as Data Reception and HARQ Feedback Circuitry 60 in processing circuit 52. Of course, the processor circuit 52 may be configured to carry out any of the variants of the methods described above.
It will be appreciated by the person of skill in the art that various modifications may be made to the above described embodiments without departing from the scope of the presently described techniques. For example, it will be readily appreciated that although the above embodiments are described with reference to parts of a 3GPP network, other embodiments will also be applicable to like networks, such as a successor of the 3GPP network, having like functional components. Therefore, in particular, the terms 3GPP and associated or related terms used in the above description and in the enclosed drawings and any appended claims now or in the future are to be interpreted accordingly.
In the above discussion, specific details of particular embodiments of the presently disclosed techniques are set forth for purposes of explanation and not limitation. It will be appreciated by those skilled in the art that other embodiments may be employed apart from these specific details. Furthermore, in some instances detailed descriptions of well-known methods, nodes, interfaces, circuits, and devices are omitted so as not obscure the description with unnecessary detail. Those skilled in the art will appreciate that the functions described may be implemented in one or in several nodes. Some or all of the functions described may be implemented using hardware circuitry, such as analog and/or discrete logic gates interconnected to perform a specialized function, ASICs, PLAs, etc. Likewise, some or all of the functions may be implemented using software programs and data in conjunction with one or more digital microprocessors or general purpose computers. Where nodes that communicate using the air interface are described, it will be appreciated that those nodes also have suitable radio communications circuitry. Moreover, the technology can additionally be considered to be embodied entirely within any form of computer-readable memory, including non-transitory embodiments such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.
Hardware implementations may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to ASIC and/or FPGAs, and (where appropriate) state machines capable of performing such functions.
In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer, processor, and controller may be employed interchangeably. When provided by a computer, processor, or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, the term “processor” or “controller” also refers to other hardware capable of performing such functions and/or executing software, such as the example hardware recited above.
Because it is not possible, of course, to describe every conceivable combination of components or techniques, those skilled in the art will appreciate that the techniques described above can be implemented in other ways than those specifically set forth herein, without departing from essential characteristics of the techniques. The present embodiments are thus to be considered in all respects as illustrative and not restrictive.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/SE2016/050183 | 3/9/2016 | WO | 00 |
Number | Date | Country | |
---|---|---|---|
62130331 | Mar 2015 | US |