Harq reception status determination and transmission.

Description

BACKGROUND [0001] Long Term Evolution (LTE) and other wireless networks rely on transmission of messages across an unreliable medium between a mobile device (e.g., a User Equipment (UE)) and the Radio Access Network (RAN). In LTE the RAN consists of one or more eNodeBs. This unreliable communication medium can create problems for proper communication of data between the RAN and the UE as data may be lost or corrupted due to low signal quality, interference, or other problems with the wireless medium.

BRIEF DESCRIPTION OF THE DRAWINGS [0002] FIG. 1 is a table showing mappings from HARQ-ACK responses to resources, constellations and RM Code Input Bits for two cells with a bundling window of 3 according to some examples of the present disclosure.

[0003] FIG. 2 is a table showing mappings from HARQ-ACK responses to resources, constellations and RM Code Input Bits for two cells with a bundling window of 4 according to some examples of the present disclosure.

[0004] FIG. 2A is a continuation of the table of FIG. 2 according to some examples of the present disclosure.

[0005] FIG. 3 shows a diagram of an example resource allocation according to some examples of the present disclosure.

[0006] FIG. 4 shows a diagram of an example resource allocation according to some examples of the present disclosure.

[0007] FIG. 5A shows a flowchart of a method of generating a HARQ-ACK response according to some examples of the present disclosure.

[0008] FIG. 5B shows a flowchart of a method of processing a HARQ-ACK response according to some examples of the present disclosure.

[0009] FIG. 6 shows a block diagram of a wireless communication system according to some examples of the present disclosure.

[0010] FIG. 7 shows a block functional diagram showing certain functions of a

UE and an eNodeB according to some examples of the present disclosure.

[0011] FIG. 8 shows a block diagram of a machine according to some examples of the present disclosure.

DETAILED DESCRIPTION [0012] In order to deal with the unreliable wireless communication medium,

LTE and other cellular networks employ a mechanism called Hybrid Automatic Repeat Request (HARQ) to provide error correction and packet acknowledgements to ensure the safe delivery of data between the RAN and the UE. HARQ provides for error correction at the receiver side using forward error correction coding (FEC) as well as automatic feedback mechanisms (Automatic Repeat Request (ARQ)) to indicate to the sender whether or not the packets were successfully received. Upon receipt of a packet of data, the receiver uses an error detection code (e.g., a Cyclic Redundancy Check (CRC)) to determine if the packet was correctly received. If the packet was received successfully, the receiver acknowledges the sender using a feedback mechanism (e.g., ACK). If the packet was not received successfully, the receiver may attempt to repair the packet using the FEC information. If the receiver is successful in using the FEC information to repair the packet, it may ACK the sender, otherwise the receiver may respond to the sender with a Negative Acknowledgement (NACK). In yet other examples, the receiver (the UE) may respond that it was in Discontinuous Transmission Mode (DTX) mode. The DTX response may represent a case in which the UE is not able to properly detect information on a control channel (e.g., the Primary Downlink Control Channel - PDCCH) and thus was unable to determine if a packet was sent to the UE.

[0013] In a cellular network, these HARQ responses typically are transmitted on the control channels. Responses for downlink traffic sent from the RAN to the UE are typically sent in uplink control channels (e.g., the Physical Uplink Control Channel (PUCCH)). Responses for uplink traffic sent from the UE to the RAN are typically sent in downlink HARQ-ACK channels (e.g., the Physical hybrid HARQ indicator channel: PHICH). Packets that are not acknowledged (either NACKed or simply not acknowledged at all) may be retransmitted by the sender.

[0014] In some systems, uplink communications (from the UE to the RAN) are separated from downlink communications in the frequency domain. That is, the uplink and downlink wireless communications occur on different frequency bands. These systems are referred to as Frequency Duplex Division (FDD) systems. In other examples, the uplink and downlink wireless communications may share the same frequency bands, but may be divided in the time domain. That is, the frequency bands are reserved for the uplink wireless transmissions in some time instances (e.g. called time slots), and the downlink wireless communications in other time instances (e.g. time slots). This scheme is called Time Division Duplex (TDD). In still other examples, half-duplex FDD (H-FDD) systems feature the uplink and downlink wireless communications on different frequency bands but divided as well in the time domain. [0015] The very nature of the cellular network is that communications between the UE and the RAN is asymmetrical in favor of the downlink wireless link. That is, more data is usually sent from the RAN to the UE than from the UE to the RAN. In order to compensate for this, cell planners will often allocate more frequency or time resources (depending on whether the network is FDD or TDD) to the downlink wireless communications than are allocated to the uplink wireless communications. [0016] This resource asymmetry creates problems for the UE in trying to manage the necessary HARQ acknowledgements because there are often insufficient uplink resources on the uplink control channels to transmit these responses. This problem is only exasperated with the addition of multiple carriers and other uplink signaling such as Channel State Information.

[0017] In LTE, wireless transmissions are typically broken into discrete units called frames, which may then be broken down into sub-frames and the sub-frames into one or more code words. Each code word may have a mapping relationship with a particular transport block and herein are used interchangeably unless specified otherwise. With FDD systems, the HARQ response may be transmitted at a fixed number of sub-frames after the transmission is received (typically 4 sub-frames later). However, with TDD systems, a fixed delay is not possible as there often are a variable number of uplink and downlink timeslots in a radio frame due to the asymmetric wireless imbalance.

[0018] To solve these problems, for TDD systems, the 3^rd Generation

Partnership Project (3GPP) which promulgates the standards for 4G (LTE) wireless networks has developed several mechanisms. The first is ACK/NACK/DTX time domain bundling. For HARQ-ACK bundling, the ACK, NACK, or DTX result for each particular code word in each downlink sub frame for a particular number of sub frames (called a bundling window) received on the downlink channel (e.g., a Physical Downlink Shared Channel - PDSCH) are logically AND’ed to produce one or multiple composite result corresponding to each code word in all the sub frames of a bundling window. The number of composite ACK/NACK/DTX results produced then equals the number of code words in a sub-frame. For example, if the size of bundling window is four downlink sub-frames, and each sub-frame has two code words, the acknowledgements of the first code word of sub-frames 0-3 are logically AND’ed together, and the second code words of sub-frames 0-3 are also AND’ed together to produce two acknowledgement bits. The benefit of this technique is that it is very compact, using few bits so that the uplink coverage can be assured. The downside is that if any one of the code words of any one of the sub-frames is not received correctly, then the particular code word for all sub-frames will be retransmitted. Another technique is to use HARQ-ACK multiplexing which may logically AND code words across the code words (i.e. called spatial domain bundling) for each downlink sub-frame individually to produce one acknowledgement bit per each down link sub frame. The result is an ACK/NACK/DTX result for each associated downlink sub frame within a bundling window. For four down link sub-frames, with two code words per sub frame, a spatial domain bundling across two code words (if any) by logical AND operation is applied in the sub-frame and the multiple bundled ACK/NACKs in the sub-frames may result in one composite state within a bundling window. For a HARQ-ACK response sent on the Physical Uplink Control Channels (PUCCH), the composite state may be represented as a combination of a PUCCH resource and constellation points. This results in four acknowledgement results - one for each subframe. Notice that despite the fact that the name for this particular HARQ-ACK technique is “multiplexing,” throughout the specification the term “bundling window” is used.

[0019] A bundling window is a time unit (e.g., a number of sub-frames) specifying when HARQ-ACK feedback corresponding to down link traffic at a particular uplink sub frame is transmitted in the uplink. A UE transmits HARQ-ACK feedback using the PUCCH in a sub-frame n where the HARQ-ACK feedback for n-k_t, where k_t e/< (defined in Table 1) and 0 < z <M -1. The bundling window is generally defined as the down link sub-frames of n-k_i for an uplink HARQ-ACK feedback at sub-frame n.

Table 1. Downlink association set indexer; for TDD

<td rowspan="2"> UL-DL Configuration</td><td colspan="10"> Subframe n</td>

<td> 0</td><td> 1</td><td> 2</td><td> 3</td><td> 4</td><td> 5</td><td> 6</td><td> 7</td><td> 8</td><td> 9</td>

<td> 0</td><td> -</td><td> -</td><td> 6</td><td> -</td><td> 4</td><td> -</td><td> -</td><td> 6</td><td> -</td><td> 4</td>

<td> 1</td><td> -</td><td> -</td><td> 7,6</td><td> 4</td><td> -</td><td> -</td><td> -</td><td> 7,6</td><td> 4</td><td> -</td>

<td> 2</td><td> -</td><td></td><td> 8,7,4,6</td><td></td><td></td><td></td><td></td><td> 8, 7, 4,6</td><td></td><td></td>

<td> 3</td><td> -</td><td></td><td> 7,6,11</td><td> 6,5</td><td> 5, 4</td><td></td><td></td><td></td><td></td><td></td>

<td> 4</td><td> -</td><td></td><td> 12, 8, 7, 11</td><td> 6, 5, 4,7</td><td></td><td></td><td></td><td></td><td></td><td></td>

<td> 5</td><td> .</td><td></td><td> 13, 12, 9, 8, 7, 5, 4,11,6</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td> 6</td><td></td><td></td><td> 7</td><td> 7</td><td> 5</td><td></td><td> -</td><td> 7</td><td> 7</td><td> -</td>

TDD UL-DL configuration table is given as Table 2.

Table 2. TDD UL-DL configuration

<td> TDD</td><td> IIUDL</td><td rowspan="2"> Downlink to Uplink Switch Point Periodicity</td><td colspan="3"> Sub-frame</td><td colspan="7"> number</td>

<td colspan="2"> ucmiiyuimiuf!</td><td> 0</td><td> 1</td><td> 2</td><td> 3</td><td> 4</td><td> 5</td><td> 6</td><td> 7</td><td> 8</td><td> 9</td>

<td colspan="2"> 0</td><td> 5ms</td><td> D</td><td> S</td><td> U</td><td> U</td><td> U</td><td> D</td><td> S</td><td> U</td><td> U</td><td> U</td>

<td colspan="2"> 1</td><td> 5ms</td><td> D</td><td> s</td><td> U</td><td> U</td><td> D</td><td> D</td><td> S</td><td> U</td><td> U</td><td> D</td>

<td colspan="2"> 2</td><td> 5ms</td><td> D</td><td> s</td><td> U</td><td> D</td><td> D</td><td> D</td><td> S</td><td> u</td><td> D</td><td> D</td>

<td colspan="2"> 3</td><td> 10ms</td><td> D</td><td> s</td><td> u</td><td> U</td><td> U</td><td> D</td><td> D</td><td> D</td><td> D</td><td> D</td>

<td colspan="2"> 4</td><td> 10ms</td><td> D</td><td> s</td><td> u</td><td> U</td><td> D</td><td> D</td><td> D</td><td> D</td><td> D</td><td> D</td>

<td colspan="2"> 5</td><td> 10ms</td><td> D</td><td> s</td><td> u</td><td> D</td><td> D</td><td> D</td><td> D</td><td> D</td><td> D</td><td> D</td>

<td colspan="2"> 6</td><td> 5ms</td><td> D</td><td> s</td><td> u</td><td> U</td><td> U</td><td> D</td><td> 5</td><td> U</td><td> U</td><td> D</td>

TDD Uplink/Downlink Configurations (D=downlink, S=special sub-frame with the three fields DwPTS, GP and UpPTS which is used to give the UE time to switch from downlink to uplink, U=uplink).

[0020] LTE Advanced supports carrier aggregation in which multiple carriers may be utilized in the downlink. This means that multiple ACK/NACK information bits for multiple carriers need to be fed back in the uplink. For this, LTE defines a technique known as channel selection with time domain bundling. This technique utilizes a similar technique as the HARQ-ACK multiplexing except that time domain bundling of this technique is slightly different from the existing one. The time domain bundling for carrier aggregation may be for transmitting the number of consecutive ACKs for each component carrier while that for single carrier is for transmitting the logically bundled HARQ-ACK information. The resultant ACK/NACK information may be encoded by the joint selection of a channel and a QPSK constellation symbol. Essentially, the multiplexed acknowledgement results may then be indexed into a lookup table to select a two bit field (the QPSK constellation) and a PUCCH resource (the selected channel) for PUCCH transmission. A RM code input bit set is also provided in case the HARQ-ACK is piggybacked on PUSCH. The mapping tables are shown in FIGs. 1, and 2 (FIG. 2 is continued on FIG. 2A) for different bundling window sizes. The column labeled HARQ-ACK(0)-(2) for FIG. 1 and HARQ-ACK(0)-(3) for FIG. 2 and FIG. 2A represent the ACK, NACK, or DTX decision for that particular subframe for both the primary and secondary cells (PCell and SCell respectively). For example, in the case of a four sub frame bundling window, if sub-frame(O) was received successfully (ACK), sub-frame(l) was received unsuccessfully (NACK), subframe (2) was received successfully (ACK), and sub-frame (3) was received successfully (ACK) on the primary cell and a response of ACK, ACK, ACK, NACK, on the secondary cell, the UE would select a constellation of (0,1) with a feedback resource corresponding to a Physical Uplink Control Channel (PUCCH) 3 and using code input bits of 0,0,1,1. In short, the HARQ-ACK(j) column is the ACK/NACK/ or DTX response for each particular downlink sub frame for each of the primary and secondary cells (for multiple carriers) and the corresponding PUCCH resources, constellations, and RM code input bits to use depending on the HARQ-ACK(j) selected for each of the primary and secondary cells. This technique utilizes PUCCH format 1b when HARQ-ACK is transmitted using PUCCH.

[0021] HARQ-ACK bundling or HARQ-ACK multiplexing may not work properly if the UE does not correctly receive the scheduling information for any scheduled frames. For example, if the eNodeB schedules the terminal for two sub7 frames with a bundling window size 2, but the UE only received the last frame, but was unaware that it was scheduled in the first frame, the UE would reply with an ACK. The eNodeB would interpret this ACK as an acknowledgement of both sub-frames. In order to determine when a downlink grant for a UE is missed, the LTE specification provides a Downlink Assignment Index (DAI) sent to the UE from the RAN along with the downlink scheduling information on the PDCCH. The DAI conveyed in downlink grant demotes the accumulative number of PDCCH(s) with assigned PDSCH transmission(s) and PDCCH indicating Semi Persistent Scheduling (SPS) release up to the present sub-frame within the same bundling window of each configured serving cell. The UE then utilizes the DAI to generate the HARQ-ACK(j) within the bundling window.

[0022] Turning now to FIG. 3, an example response calculation is shown. In the example of FIG. 3, a bundling window of four sub-frames (M=4) is shown in two configured cells. The HARQ-ACK(/) response for the primary cell (PCell) is ACK, ACK, DTX, ACK and in the secondary cell (SCell) it is ACK, NACK, NACK, ACK, respectively. The DAIs received on the PDCCH for the PCell are 1 for sub-frame 0, 2 for sub-frame 1, and 4 for sub-frame 3. Note that the UE was not able to decode the PDCCH on sub-frame 2 (m=2) and thus did not update its DAI value. Even though the UE lost the updated DAI value it recovers it in sub-frame m=3 and thus knows that the DAI is 4 at the end of the bundling window. Because the DAI value is 4, the UE knows that it needs four HARQ-ACK(/) responses. For the SCell, the DAI’s received on the PDCCH are 1,2, 3, and 4 for sub-frames 0, 1,2, and 3 respectively.

[0023] Based on the mapping table in FIGs. 2 and 2A this produces a response of:

<td> Primary Cell</td><td> Secondary Cell</td><td> Resource</td><td> Constellation</td><td> RM Code Input Bds</td>

<td> HARQ-ACK(O), HARQ-ACK(I). HARG-ACK(2). HARQ-ACKP)</td><td> HARQ-ACK(O), HARO-ACK(I), HARO-ACKP), HARO-ACKP)</td><td> PUCCH RESOURCE</td><td> bfOS, b( 1)</td><td> o&lt;0), o(1), o&lt;2), op)</td>

<td> ACK, ACK, NACK DTX, any</td><td> (ACK, NACK / DTX, any, any), except for (ACK, DTX, DTX, DTX)</td><td> 1</td><td> 0,1</td><td> 1, o, 0, 0</td>

Note that there is a problem when all sub-frames of a particular bundling window are not scheduled by the RAN. Since certain frames are not scheduled, the DAI will not be incremented and will be less than the bundling window size at the end of the bundling window. The feedback tables of FIG. 1 and FIG. 2 assume that all frames are scheduled. FIG. 4 shows one example of this issue. In this example the first two downlink sub-frames in the PCell are not scheduled. Thus for sub-frame 2, DAI is 1 and for sub-frame 3, DAI is 2 (compared to FIG. 3, where DAI was 3 and 4 for sub frames 2 and 3 respectively). Since the HARQ-ACK (/) is determined in conjunction with the DAI value, HARQ-ACK(O) corresponds to sub-frame 2 and HARQ-ACK(1) corresponds to sub-frame 3. However, HARQ-ACK(2) and HARQ-ACK(3) are undefined because there are no corresponding DAI values of 3 and 4 within the bundling window according to the definition of DAI. This is because the DAI value is defined as the accumulative number of PDCCH(s) within an assigned PDSCH transmission(s) and PDCCH indicating downlink Semi-Persistent Scheduling (SPS) release up to the present sub-frame within a bundling window. Therefore, if there is no expected DL sub-frame to be monitored by a UE for HARQ-ACK(/) related to DAI value within a bundling window, a UE behavior is not specified.

[0024] Disclosed in some examples are systems, methods, UEs, and machine-readable media which solve the issue of generating an acknowledgement for the situation in which a last received DAI (LDAI) value is less than a size of a bundling window. In some examples, a predetermined state is utilized for HARQ-ACK(/) for the case LDAI&lt;=j^&lt;M-'\, where M is the multiplexing or bundling window size. For example, the DTX state may be padded into these HARQ-ACK responses. So for example, in FIG. 4, the HARQ-ACK(/) for the PCell to use to determine the proper response parameters would be: ACK, ACK, DTX, DTX.

[0025] Since the last two states for the PCell are padded by DTX, the UE will know the exact mapping from the table to use. In addition, on the network side, since the eNodeB already knows the last two states are padded with DTX, the irrelevant states other than DTX can be excluded during PUCCH detection hypothesis tests which may improve HARQ-ACK detection performances. For example in Figure 3, since the HARQ-ACK response in PCell is {ACK, ACK, DTX, DTX}, {ACK, NACK, DTX, DTX}, {NACK, ACK, DTX, DTX}, or {NACK, NACK, DTX, DTX}, the states of {any, any, ACK/NACK, ACK/NACK} can be excluded in eNB detection. By decreasing the detection hypothesis tests, the PUCCH detection performance may be enhanced. [0026] Applying this method to the example shown in FIG. 4 produces:

<td> Primary Cell</td><td> Secondary Cel</td><td> Resource</td><td> Constellation</td><td> RM Code Input Bits</td>

<td> HARG-ACK(O). HARG-ACK(I). HARG-ACK(2). HARQ-ACK(3)</td><td> HARQ-ACK(Oj, HARÖ-ACK(t), HARO-ACKP), HARQ-ACKpj</td><td> PUCCH RESOURCE</td><td> b(0), b&lt;1)</td><td> o(0), o(1), o&lt;2), op)</td>

<td> ACK, ACK, NACK ! DTX, any</td><td> (ACK. NACK / DTX, any, any), except for (ACK, DTX, DTX, DTX)</td><td> 1</td><td> 0,1</td><td> 1, 0, 0, 0</td>

[0027] While in some examples the HARQ-ACK(/) may be filled with DTX for the case in which all downlink sub-frames within a bundling window were not scheduled, in other examples, other values may be used, such as an ACK, NACK, or another defined value. This is because the eNodeB has enough system knowledge to ignore these values. In fact, in some examples, the UE may arbitrarily choose any ACK/NACK/DTX value.

[0028] Turning now to FIG. 5A, a method 5000 of acknowledging a transmission when not all the downlink frames in a particular bundling window have been scheduled is shown. At operation 5010, the UE receives scheduling information on the PDCCH indicating downlink frames which are scheduled. At operation 5020, the UE determines that it has received the last downlink assignment for a particular bundling window and at operation 5030 determines that the last DAI value (LDAI) is less than the bundling window size. At operation 5040 the UE determines the ACK/NACK/DTX responses for the frames for which the UE was aware it was scheduled. At operation 5050, the remaining HARQ-ACK(/) that do not have corresponding DAI values are filled in with a predetermined value (e.g., DTX).

[0029] Turning now to FIG. 5B, a method 5100 of processing an acknowledgement at an eNodeB of a transmission in which not all the downlink frames in a particular bundling window have been scheduled is shown. At operation

5110 the base station (e.g., an eNodeB) may schedule one or more downlink transmissions for a particular acknowledgement period (e.g., a bundling window) and notify the UE through a downlink control channel such as a Physical Downlink Control Channel (PDCCH). At operation 5120, the eNodeB may transmit the scheduled frames. At operation 5130 the eNodeB may receive the response from the UE. At operation 5140, the eNodeB may determine that the last DAI value sent on the PDCCH is less than a bundling window size. At operation 5150, the eNodeB may use the resource (e.g., the PUCCH resource) that the response was received on along with the received constellation and RM code bits to determine the response, factoring in that the HARQ-ACK(/) where j is LDAI&lt;=j&lt;M-'\, where M is the multiplexing or bundling window size, are padded values. The eNodeB may then transmit any necessary retransmissions.

[0030] Turning now to FIG. 6 a system 6000 for acknowledging transmissions is shown. User Equipment (UE) 6010 communicates with a Radio Access Network (RAN) 6020 which may include one or more base stations (e.g., an eNodeB) 6030, 6035 over one or more radio links 6040. RAN 6020 may be connected to a core network 6045, such as an enhanced Packet Core. EPC 6045 may be connected to a network 6050, such as the internet, a Plain Old Telephone Service network (POTS), or the like. In the system of FIG. 6, the radio links 6040 may operate in a Time Division Duplex mode (TDD) mode.

[0031] FIG. 7 shows a partial functional diagram of a UE 7000 (more components not shown may be included). UE 7000 may include a transmission module 7010. The transmission module 7010 may transmit control and user traffic to the RAN over one or more uplink channels such as a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH) or the like. Transmission module 7010 may transmit the acknowledgements of user traffic and control traffic sent from the RAN to the UE 7000 on the downlink channels (e.g., the Physical Downlink Shared Channel (PDSCH) - and the Physical Dedicated Control Channel (PDCCH)).

[0032] Reception module 7020 may receive information sent by the RAN on the downlink channels such as the Physical Downlink Shared Channel (PDSCH) and Physical Downlink Control Channel (PDCCH) and inform the response module 7030 of the reception status of that information. For example, received sub-frames may be decoded at the reception module (and any FEC correction may be done here as well) and an indication of whether the sub-frame should be ACK’ed, NACK’ed, or DTX’ed may be sent to the response module 7030. Reception module 7020 may also pass various communication parameters to the response module 7030 such as the size of the bundling window and the last received DAI for that window.

[0033] Response module 7030 may inform the transmission module 7010 of the appropriate response parameters (e.g., PUCCH resource, RM code bits, constellation) according to the tables in FIG. 1 and FIG. 2 (continued on FIG. 2A) based upon the LDAI, the bundling window size and the like. For example, the response module 7030 may make a determination that a number of received downlink assignments is less than a response bundling window size and based upon that determination, set the reception status of each received downlink assignment based on whether a frame associated with the particular received downlink assignment was successfully received and setting the reception status of a frame in the bundling window that did not have a corresponding downlink assignment to a predetermined value. For example, the response module may determine for each index j for a plurality of downlink sub-frames in a response bundling window if one or more received downlink assignment index (DAI) values is equal to j + p. Determining a reception status (ACK/NACK/DTX) of the sub-frame corresponding to j responsive to determining that one of the one or more DAI values is equal to j + p. Setting the reception status of the sub-frame corresponding to j to a predetermined value responsive to determining that none of the one or more DAI values is equal to j+p. Where p is a constant (e.g., 0 or 1), where the one or more DAI values is received over the Physical Downlink Control Channel (PDCCH), where j &lt; M - 1, and where M is a number of sub-frames in a HARQ bundling window. The response module 7030 may also be called a HARQ module and may then instruct the transmission module 7010 to transmit the appropriately determined response. In some examples, the variable p may be equal to zero if there is a Physical Downlink Shared Channel (PDSCH) transmission on the primary cell without a corresponding PDCCH detected within the bundling window, otherwise p may be one. Therefore, the value p can represent whether a semi-persistent scheduling (SPS) PDSCH without the corresponding PDCCH exists within a bundling window or not. Note that while the specification describes a PDCCH with a DAI value for a scheduled downlink frame, the disclosure may also be used when the UE receives a PDCCH indicating a downlink Semi-Persistent Scheduling (SPS) release message which also includes a DAI value.

[0034] FIG. 7 also shows a partial functional diagram of an eNodeB 7100 (more components not shown may be included). eNodeB 7100 includes a transmission module 7110 which transmits user data and control data on one or more channels. For example, user data or control data may be transmitted on a Physical Dedicated Control Channel (PDCCH) or a Physical Dedicated Shared Channel (PDSCH). The transmission module 7110 may schedule frames for transmission and signal the UE on the PDCCH. The transmission module 7110 may also transmit the DAI in the PDCCH. The reception module 7120 may receive control and user data on the uplink communication channels such as the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH). Reception module 7120 may receive the HARQ responses from the UE to the downlink sub-frames (e.g., the ACK-NACK-DTX responses). In response to this information, the reception module may indicate to the transmission module that certain data may need to be retransmitted. The reception module 7120 may decode the response based on determining which PUCCH resource the response was received upon, the received constellation bits, and the received RM codes. The reception module 7120 may also determine that the last DAI value in the bundling window was less than the number of sub-frames in the bundling window and that one or more of the ACK/NACK/DTX of the sub-frames should be ignored as not representing an actual transmission.

[0035] FIG. 8 illustrates a block diagram of an example machine 8000 upon which any one or more of the techniques (e.g., methodologies) discussed herein can be performed. The UE, the RAN (including the eNodeBs) or the EPC may be or include parts of, machine 8000. In alternative embodiments, the machine 8000 can operate as a standalone device or can be connected (e.g., networked) to other machines. In a networked deployment, the machine 8000 can operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 8000 can act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine 8000 can be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a mobile telephone (such as a UE), a web appliance, a wireless base station, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations. For example, the functions of the machine 8000 can be distributed across multiple other machines in a network.

[0036] Examples, as described herein, can include, or can operate on, logic or a number of components, modules, or mechanisms. Modules are tangible entities capable of performing specified operations and can be configured or arranged in a certain manner. In an example, circuits can be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors can be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software can reside (1) on a non-transitory machine-readable medium or (2) in a transmission signal. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0037] Accordingly, the term “module” is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor can be configured as one or more modules that can change over time. Software can accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0038] Machine (e.g., computer system) 8000 can include a hardware processor 8002 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 8004 and a static memory 8006, some or all of which can communicate with each other via a bus 8008. The machine 8000 can further include a display unit 8010, an alphanumeric input device 8012 (e.g., a keyboard), a user interface (Ul) control device 8014, and/or other input devices. In an example, the display unit 8010 and Ul control device 8014 can be a touch screen display. The machine 8000 can additionally include a storage device (e.g., drive unit) 8016, a signal generation device 8018 (e.g., a speaker), and a network interface device 8020.

[0039] The storage device 8016 can include a machine-readable medium

8022 on which is stored one or more sets of data structures or instructions 8024 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 8024 can also reside, completely or at least partially, within the main memory 8004, within static memory 8006, or within the hardware processor 8002 during execution thereof by the machine 8000. In an example, one or any combination of the hardware processor 8002, the main memory 8004, the static memory 8006, or the storage device 8016 can constitute machine readable media.

[0040] While the machine-readable medium 8022 is illustrated as a single medium, the term machine readable medium can include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that configured to store the one or more instructions 8024.

[0041] The term “machine-readable medium” can include any tangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 8000 and that cause the machine 8000 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machinereadable medium examples can include solid-state memories, and optical and magnetic media. Specific examples of machine-readable media can include: nonvolatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

[0042] The instructions 8024 can further be transmitted or received over a communications network 8026 using a transmission medium via the network interface device 8020. Network interface device 8020 may connect the machine 8000 to a network of other machines in order to communicate with the other machines in the network by utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks can include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as WiFi®, IEEE 802.16 family of standards known as WiMax®), peer-to-peer (P2P) networks, among others. In an example, the network interface device 8020 can include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 8026. In an example, and as shown in FIG. 8, the network interface device 8020 can include a plurality of antennas (not shown) to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (ΜΙΜΟ), or multiple-input singleoutput (MISO) techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 8000, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

OTHER NOTES AND EXAMPLES [0043] Example 1: Disclosed is a User Equipment (UE) comprising a response module arranged to receive one or more downlink assignments of a bundling window over a wireless downlink control channel; set a reception status for each sub-frame of a downlink data channel in the bundling window based on whether the sub-frame on the downlink data channel was associated with a particular one of the downlink assignments and based upon whether the sub-frame was successfully received; and set a reception status of sub-frames of the downlink data channel in the bundling window that did not have a corresponding downlink assignment to a predetermined value; and a transmission module arranged to transmit a response, the response based upon the reception statuses set by the response module.

[0044] Example 2: The UE of example 1, wherein the reception status is one of: acknowledgement (ACK), negative acknowledgement (NACK), and Discontinuous Reception (DTX).

[0045] Example 3: The UE of any one of examples 1-2, wherein the predetermined value is a value indicating a discontinuous transmission (DTX).

[0046] Example 4: The UE of any one of examples 1-3, wherein the UE is arranged to operate in a Time Division Duplex (TDD) mode and wherein the transmission module is arranged to transmit the response using a Physical Uplink Control Channel (PUCCH) format 1b.

[0047] Example 5: The UE of any one of examples 1-4, wherein the bundling window is greater than 2 sub-frames.

[0048] Example 6: The UE of any one of examples 1-5, wherein the transmission module is arranged to transmit the response by selecting a PUCCH uplink resource, a constellation, and a set of code input bits based upon the reception statuses.

[0049] Example 7: The UE of any one of examples 1-6, wherein the UE is arranged to communicate with a wireless network using a Long Term Evolution (LTE) family of standards.

[0050] Example 8: The UE of any one of examples 1-7, wherein the UE is arranged to utilize carrier aggregation with two serving cell configurations.

[0051] Example 9: Disclosed is a method comprising determining for each index j for a plurality of downlink sub-frames if one or more received downlink assignment index (DAI) values are equal to j+p, the one or more DAI values received over a Physical Downlink Control Channel (PDCCH), where j &lt; M - 1, M being a number of sub-frames in a HARQ bundling window, wherein p is a constant; setting the reception status of the sub-frame corresponding to j to a predetermined value responsive to determining that none of the one or more DAI values is equal to j+1; and transmitting the reception status of each of the plurality of downlink sub-frames j in the bundling window M.

[0052] Example 10: The method of example 9, wherein the predetermined value is a value indicating a discontinuous transmission (DTX).

[0053] Example 11: The method of any one of examples 9-10, comprising:

determining if there is a Primary Downlink Shared Channel (PDSCH) transmission on a primary cell without a corresponding PDCCH detected within the bundling window; responsive to determining that there is a PDSCH without a corresponding PDCCH, setting p to 0; responsive to determining that there are no PDSCH without a corresponding PDCCH, setting p to 1.

[0054] Example 12: The method of any one of examples 9-11, wherein the reception statuses are transmitted using a Physical Uplink Control Channel (PUCCH) format 1 b.

[0055] Example 13: The method of any one of examples 9-12, comprising transmit the reception statuses by at least selecting a PUCCH uplink resource, a constellation, and a set of code input bits based upon the reception statuses.

[0056] Example 14: Disclosed is a User Equipment (UE) comprising: a Hybrid

Automatic Repeat Request (HARQ) module arranged to: for each index j for a plurality of downlink sub-frames: determine if one or more received downlink assignment index (DAI) values is equal to j + p, where p is a constant, the one or more DAI values received over a Physical Downlink Control Channel (PDCCH), where j &lt; M - 1, and where M is a number of sub-frames in a HARQ bundling window, determine a reception status of the sub-frame corresponding to j responsive to determining that one of the one or more DAI values is equal to j + p, and setting the reception status of the sub-frame corresponding to j to a predetermined value responsive to determining that none of the one or more DAI values is equal to j+p; and a transmission module arranged to transmit the reception status of each of the plurality of downlink subframes j in the bundling window M.

[0057] Example 15: The UE of example 14, wherein the reception status is one of: acknowledgement (ACK), negative acknowledgement (NACK), and Discontinuous Reception (DTX).

[0058] Example 16: The UE of any one of examples 14-15, wherein the predetermined value is a value indicating a discontinuous transmission (DTX).

[0059] Example 17: The UE of any one of examples 14-16, wherein the predetermined value is a value different from a value indicating an ACK, a NACK, and a DTX.

[0060] Example 18: The UE of any one of examples 14-17, wherein the predetermined value is a value chosen at random from one of a value indicating an ACK, a NACK, and a DTX.

[0061] Example 19: The UE of any one of examples 14-18, wherein the UE is arranged to operate in a Time Division Duplex (TDD) mode.

[0062] Example 20: The UE of any one of examples 14-19, wherein the UE is arranged to multiplex HARQ reception statuses.

[0063] Example 21: The UE of any one of examples 14-20, wherein the transmission module is arranged to transmit the reception statuses using a Physical Uplink Control Channel (PUCCH) format 1b.

[0064] Example 22: The UE of any one of examples 14-21, wherein the

HARQ module is further arranged to: determine if there is a Primary Downlink Shared Channel (PDSCH) transmission on a primary cell without a corresponding PDCCH detected within the bundling window; responsive to determining that there is a PDSCH without a corresponding PDCCH, setting p to 0; responsive to determining that there are no PDSCH without a corresponding PDCCH, setting p to 1.

[0065] Example 23: The UE of any one of examples 14-22, wherein the transmission module is arranged to transmit the reception status by selecting a PUCCH uplink resource, a constellation, and a set of code input bits based upon the reception statuses.

[0066] Example 24: The UE of any one of examples 14-23, wherein the UE is arranged to communicate with a wireless network using a Long Term Evolution (LTE) family of standards.