# US 10,873,425 B2 · Acknowledgement / negative acknowledgement feedback for TDD > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,873,425 B2 - Document ID: US10873425B2 - Status: Granted - Kind: B2 - Application number: 13/293,086 - Filed: 2011-11-09 - Published: 2012-11-15 - Granted: 2020-12-22 - Earliest claimed: 2010-11-12 - Assignees: QUALCOMM Incorporated - Applicants: Wanshi Chen; Juan Montojo; Xiliang Luo - Inventors: Wanshi Chen; Juan Montojo; Xiliang Luo - Web page: https://patentgrep.com/patent/US10873425B2 ## CPC - H04L 1/1861: {Physical mapping arrangements (for ACK signaling see also H04L5/0053)} - H04L 1/1614: {using bitmaps} - H04L 1/1864: {ARQ related signaling (H04L1/1607 takes precedence)} - H04L 5/0044: {Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Bits for acknowledgement (ACK) and/or negative acknowledgement (NAK) may be allocated based on whether a special subframe configuration in a TDD configuration permits downlink transmission. For carrier aggregation, ACK/NAK bits may be allocated only to special subframes in component carriers (CCs) which permit downlink transmission. Also, for example, ACK/NAK bits may be allocated to all CC special subframes if a single CC is configured to allow downlink transmission on one of its special subframes. ACK/NAK bits may also be allocated to all special subframes. ## Claims ### Claim 1 A method of wireless communication comprising: receiving, at a user equipment (UE), a configuration of an uplink control format supporting at least three payload bits for an acknowledgement/negative acknowledgement (ACK/NAK) payload; determining, at the UE, a special subframe configuration for a special subframe of each component carrier (CC) of a set of CCs scheduled for a downlink transmission; determining, at the UE, whether the scheduled special subframe of each CC of the set of CCs supports a downlink data transmission based on a length of a downlink pilot time slot of the special subframe configuration; determining, at the UE, a number of payload bits to allocate to the ACK/NAK payload based on a number of payload bits allocated for each CC of the set of CCs, a number of payload bits allocated for a given CC of the set of CCs is greater than zero when a scheduled special subframe for the given CC supports the downlink data transmission, and the number of payload bits allocated for the given CC is zero when the scheduled special subframe for the given CC does not support the downlink data transmission; determining, at the UE, a size of the ACK/NAK payload based at least in part on the determined number of payload bits; and transmitting, at the UE, ACK/NAK information for the set of CCs in an uplink subframe based on the determined size of the ACK/NAK payload. ### Claim 2 (depends on 1) The method of claim 1 in which the ACK/NAK information provides feedback for at least one downlink subframe associated with the uplink subframe, in a single carrier configuration. ### Claim 3 (depends on 1) The method of claim 1 in which the ACK/NAK information provides feedback for at least one downlink subframe of a primary component carrier and at least one downlink subframe of a secondary CC. ### Claim 4 (depends on 3) The method of claim 3 in which the ACK/NAK information comprises an uplink transmission in an uplink control channel on a primary carrier. ### Claim 5 (depends on 3) The method of claim 3 in which determining the size of the ACK/NAK payload and the number of payload bits to allocate are performed for each primary and secondary CC. ### Claim 6 (depends on 1) The method of claim 1 in which the ACK/NAK information comprises an uplink transmission in an uplink control channel. ### Claim 7 (depends on 1) The method of claim 1 in which the ACK/NAK information comprises an uplink transmission in an uplink data channel. ### Claim 8 (depends on 1) The method of claim 1, in which uplink control information comprises a DFT-S-OFDM (Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing) format, and further comprising determining an encoding scheme for the DFT-S-OFDM format based at least in part on the size of the ACK/NAK payload. ### Claim 9 (depends on 8) The method of claim 8, in which the encoding is further dependent on a number of downlink subframes associated with an uplink subframe transmitting a PUCCH (Physical Uplink Control Channel). ### Claim 10 (depends on 8) The method of claim 8, further comprising determining a transmission power of a PUCCH (Physical Uplink Control Channel) at least in part based on the allocated payload bits. ### Claim 11 An apparatus for wireless communication comprising: means for receiving, at a user equipment (UE), a configuration of an uplink control format supporting at least three payload bits for an acknowledgement/negative acknowledgement (ACK/NAK) payload; means for determining, at the UE, a special subframe of each component carrier (CC) of a set of CCs scheduled for a downlink transmission; means for determining, at the UE, whether the scheduled special subframe of each CC of the set of CCs supports a downlink data transmission based on a length of a downlink pilot time slot of the special subframe configuration; means for determining, at the UE, a number of payload bits to allocate to the ACK/NAK payload based on a number of payload bits allocated for each CC of the set of CCs, a number of payload bits allocated for a given CC of the set of CCs is greater than zero when a scheduled special subframe for the given CC supports the downlink data transmission, and the number of payload bits allocated for the given CC is zero when the scheduled special subframe for the given CC does not support the downlink data transmission; means for determining, at the UE, a size of the ACK/NAK payload based at least in part on the determined number of payload bits; and means for transmitting, at the UE, ACK/NAK information for the set of CCs in an uplink subframe based on the determined size of the ACK/NAK payload. ### Claim 12 A non-transitory computer-readable medium having non-transitory program code recorded thereon for wireless communication by a user equipment (UE), the non-transitory program code executable by at least one processor to: receive, at a user equipment (UE), a configuration of an uplink control format supporting at least three payload bits for an acknowledgement/negative acknowledgement (ACK/NAK) payload; determine, at the UE, a special subframe configuration for a special subframe of each component carrier (CC) of a set of CCs scheduled for a downlink transmission; determine, at the UE, whether the scheduled special subframe supports a downlink data transmission based on a length of a downlink pilot time slot of the special subframe configuration; determine, at the UE, a number of payload bits to allocate to the ACK/NAK payload based on a number of payload bits allocated for each CC of the set of CCs, a number of payload bits allocated for a given CC of the set of CCs is greater than zero when a scheduled special subframe for the given CC supports the downlink data transmission, and the number of payload bits allocated for the given CC is zero when the scheduled special subframe for the given CC does not support the downlink data transmission; determine, at the UE, a size of the ACK/NAK payload based at least in part on the determined number of payload bits; and transmit, at the UE, ACK/NAK information for the set of CCs in an uplink subframe based on the determined size of the ACK/NAK payload. ### Claim 13 A user equipment (UE) for wireless communication, comprising: a memory; and at least one processor coupled to the memory, the memory comprising program code executable by the at least one processor to cause the UE to: receive a configuration of an uplink control format supporting at least three payload bits for an acknowledgement/negative acknowledgement (ACK/NAK) payload; determine a special subframe configuration for a special subframe of each component carrier (CC) of a set of CCs scheduled for a downlink transmission; determine whether the scheduled special subframe of each CC of the set of CCs supports a downlink data transmission based on a length of a downlink pilot time slot of the special subframe configuration; determine a number of payload bits to allocate to the ACK/NAK payload based on a number of payload bits allocated for each CC of the set of CCs, a number of payload bits allocated for a given CC of the set of CCs is greater than zero when a scheduled special subframe for the given CC supports the downlink data transmission, and the number of payload bits allocated for the given CC is zero when the scheduled special subframe for the given CC does not support the downlink data transmission; determine a size of the ACK/NAK payload based at least in part on the determined number of payload bits; and transmit ACK/NAK information for the set of CCs in an uplink subframe based on the determined size of the ACK/NAK payload. ### Claim 14 (depends on 13) The UE of claim 13 in which the ACK/NAK information provides feedback for at least one downlink subframe associated with the uplink subframe, in a single carrier configuration. ### Claim 15 (depends on 13) The UE of claim 13 in which the ACK/NAK information provides feedback for at least one downlink subframe of a primary component carrier and at least one downlink subframe of a secondary CC. ### Claim 16 (depends on 15) The UE of claim 15 in which the ACK/NAK information comprises an uplink transmission in an uplink control channel on a primary carrier. ### Claim 17 (depends on 15) The UE of claim 15 in which the program code is further executable by the at least one processor to cause the UE to determine the size of the ACK/NAK payload and the number of payload bits to allocate for each primary and secondary CC. ### Claim 18 (depends on 13) The UE of claim 13 in which the ACK/NAK information comprises an uplink transmission in an uplink control channel. ### Claim 19 (depends on 13) The UE of claim 13 in which the ACK/NAK information comprises an uplink transmission in an uplink data channel. ### Claim 20 (depends on 13) The UE of claim 13, in which: uplink control information comprises a DFT-S-OFDM (Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing) format, and the program code is further executable by the at least one processor to cause the UE to determine an encoding scheme for the DFT-S-OFDM format based at least in part on the size of the ACK/NAK payload. ### Claim 21 (depends on 20) The UE of claim 20, in which the encoding is further dependent on a number of downlink subframes associated with an uplink subframe transmitting a PUCCH (Physical Uplink Control Channel). ### Claim 22 (depends on 20) The UE of claim 20, in which the program code is further executable by the at least one processor to cause the UE to determine a transmission power of a PUCCH (Physical Uplink Control Channel) at least in part based on the allocated payload bits. ### Claim 23 A method of wireless communication comprising: sending a configuration of an uplink control format supporting at least three payload bits for an acknowledgement/negative acknowledgement (ACK/NAK) payload; determining a special subframe configuration for a special subframe of each component carrier (CC) of a set of CCs scheduled for a downlink transmission; determining whether the scheduled special subframe of each CC of the set of CCs supports a downlink data transmission based on a length of a downlink pilot time slot of the special subframe configuration; determining a number of payload bits to allocate to the ACK/NAK payload based on a number of payload bits allocated for each CC of the set of CCs, a number of payload bits allocated for a given CC of the set of CCs is greater than zero when a scheduled special subframe for the given CC supports the downlink data transmission, and the number of payload bits allocated for the given CC is zero when the scheduled special subframe for the given CC does not support the downlink data transmission; determining a size of the ACK/NAK payload based at least in part on the determined number of payload bits; and receiving ACK/NAK information for the set of CCs in an uplink subframe based at least in part on the determined size of the ACK/NAK payload. ### Claim 24 (depends on 23) The method of claim 23 in which the ACK/NAK information provides feedback for at least one downlink subframe associated with the uplink subframe, in a single carrier configuration. ### Claim 25 (depends on 23) The method of claim 23 in which the ACK/NAK information provides feedback for at least one downlink subframe of a primary component carrier and at least one downlink subframe of a secondary CC. ### Claim 26 (depends on 25) The method of claim 25 in which the ACK/NAK information comprises an uplink transmission in an uplink control channel on a primary carrier. ### Claim 27 (depends on 25) The method of claim 25 in which determining the size of the ACK/NAK payload and the number of payload bits to allocate are performed for each primary and secondary CC. ### Claim 28 (depends on 23) The method of claim 23 in which the ACK/NAK information comprises an uplink transmission in an uplink control channel. ### Claim 29 (depends on 23) The method of claim 23 in which the ACK/NAK information comprises an uplink transmission in an uplink data channel. ### Claim 30 (depends on 23) The method of claim 23, in which uplink control information comprises a DFT-S-OFDM (Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing) format, and further comprising determining an encoding scheme for the DFT-S-OFDM format based at least in part on the size of the ACK/NAK payload. ### Claim 31 (depends on 30) The method of claim 30, in which the encoding is further dependent on a number of downlink subframes associated with an uplink subframe transmitting a PUCCH (Physical Uplink Control Channel). ### Claim 32 (depends on 30) The method of claim 30, further comprising determining a transmission power of a PUCCH (Physical Uplink Control Channel) at least in part based on the allocated payload bits. ### Claim 33 An apparatus for wireless communication comprising: means for sending a configuration of an uplink control format supporting at least three payload bits for an acknowledgement/negative acknowledgement (ACK/NAK) payload; means for determining a special subframe configuration for a special subframe of each component carrier (CC) of a set of CCs scheduled for a downlink transmission; means for determining whether the scheduled special subframe of each CC of the set of CCs supports a downlink data transmission based on a length of a downlink pilot time slot of the special subframe configuration; means for determining a number of payload bits to allocate to the ACK/NAK payload based on a number of payload bits allocated for each CC of the set of CCs, a number of payload bits allocated for a given CC of the set of CCs is greater than zero when a scheduled special subframe for the given CC supports the downlink data transmission, and the number of payload bits allocated the given CC is zero when the scheduled special subframe for the given CC does not support the downlink data transmission; means for determining a size of the ACK/NAK payload based at least in part on the determined number of payload bits; and means for receiving ACK/NAK information for the set of CCs in an uplink subframe based on the determined size of the ACK/NAK payload. ### Claim 34 A non-transitory computer-readable medium having non-transitory program code recorded thereon for wireless communication by an apparatus, the non-transitory program code executable by at least one processor to cause the apparatus to: send a configuration of an uplink control format supporting at least three payload bits for an acknowledgement/negative acknowledgement (ACK/NAK) payload; determine a special subframe configuration for a special subframe of each component carrier (CC) of a set of CCs scheduled for a downlink transmission; determine whether the scheduled special subframe of each CC of the set of CCs supports a downlink data transmission based on a length of a downlink pilot time slot of the special subframe configuration; determine a number of payload bits to allocate to the ACK/NAK payload based on a number of payload bits allocated for each CC of the set of CCs, a number of payload bits allocated for a given CC of the set of CCs is greater than zero when a scheduled special subframe for the given CC supports the downlink data transmission, and the number of payload bits allocated for the given CC is zero when the scheduled special subframe for the given CC does not support the downlink data transmission; determine a size of the ACK/NAK payload based at least in part on the determined number of payload bits; and receive ACK/NAK information for the set of CCs in an uplink subframe based on the determined size of the ACK/NAK payload. ### Claim 35 An apparatus for wireless communication, comprising: a memory; and at least one processor coupled to the memory, the memory comprising program code executable by the at least one processor to cause the apparatus to: send a configuration of an uplink control format supporting at least three payload bits for an acknowledgement/negative acknowledgement (ACK/NAK) payload; determine a special subframe configuration for a special subframe of each component carrier (CC) of a set of CCs scheduled for a downlink transmission; determine whether the scheduled special subframe of each CC of the set of CCs supports a downlink data transmission based on a length of a downlink pilot time slot of the special subframe configuration; determine a number of payload bits to allocate to the ACK/NAK payload based on a number of payload bits allocated for each CC of the set of CCs, a number of payload bits allocated for a given CC of the set of CCs is greater than zero when a scheduled special subframe for the given CC supports the downlink data transmission, and the number of payload bits allocated for the given CC is zero when the scheduled special subframe for the given CC does not support the downlink data transmission; determine a size of the ACK/NAK payload based at least in part on the determined number of payload bits; and receive ACK/NAK information for the set of CCs in an uplink subframe based on the determined size of the ACK/NAK payload. ### Claim 36 (depends on 35) The apparatus of claim 35 in which the ACK/NAK information provides feedback for at least one downlink subframe associated with the uplink subframe, in a single carrier configuration. ### Claim 37 (depends on 35) The apparatus of claim 35 in which the ACK/NAK information provides feedback for at least one downlink subframe of a primary component carrier and at least one downlink subframe of a secondary CC. ### Claim 38 (depends on 37) The apparatus of claim 37 in which the ACK/NAK information comprises an uplink transmission in an uplink control channel on a primary carrier. ### Claim 39 (depends on 37) The apparatus of claim 37 in which the program code is further executable by the at least one processor to cause the apparatus to determine the size of the ACK/NAK payload and the number of payload bits to allocate for each primary and secondary CC. ### Claim 40 (depends on 35) The apparatus of claim 35 in which the ACK/NAK information comprises an uplink transmission in an uplink control channel. ### Claim 41 (depends on 35) The apparatus of claim 35 in which the ACK/NAK information comprises an uplink transmission in an uplink data channel. ### Claim 42 (depends on 35) The apparatus of claim 35, in which: uplink control information comprises a DFT-S-OFDM (Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing) format, and the program code is further executable by the at least one processor to cause the apparatus to determine an encoding scheme for the DFT-S-OFDM format based at least in part on the size of the ACK/NAK payload. ### Claim 43 (depends on 42) The apparatus of claim 42, in which the encoding is further dependent on a number of downlink subframes associated with an uplink subframe transmitting a PUCCH (Physical Uplink Control Channel). ### Claim 44 (depends on 42) The apparatus of claim 42, in which the program code is further executable by the at least one processor to cause the apparatus to determine a transmission power of a PUCCH (Physical Uplink Control Channel) at least in part based on the allocated payload bits.