# US 11,121,824 B2 · Carrier aggregation with variable transmission durations > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,121,824 B2 - Document ID: US11121824B2 - Status: Granted - Kind: B2 - Application number: 16/723,917 - Filed: 2019-12-20 - Published: 2020-04-23 - Granted: 2021-09-14 - Earliest claimed: 2016-07-18 - Assignees: Samsung Electronics Co., Ltd. - Applicants: Samsung Electronics Co., Ltd. - Inventors: Aris Papasakellariou - Web page: https://patentgrep.com/patent/US11121824B2 ## CPC - H04L 1/1812: Hybrid protocols; Hybrid automatic repeat request [HARQ] - H04B 7/0413: MIMO systems - H04L 1/1822: involving configuration of automatic repeat request [ARQ] with parallel processes - H04L 1/1854: {Scheduling and prioritising arrangements} - H04L 1/1861: {Physical mapping arrangements (for ACK signaling see also H04L5/0053)} - H04L 1/1864: {ARQ related signaling (H04L1/1607 takes precedence)} - H04L 1/1896: {ARQ related signaling} - H04L 5/001: {the frequencies being arranged in component carriers} - H04L 5/0048: {Allocation of pilot signals, i.e. of signals known to the receiver (allocation of control signalling H04L5/0053; use of control signalling H04L5/0091)} - H04L 5/0053: {Allocation of signalling, i.e. of overhead other than pilot signals} - H04L 5/0055: {Physical resource allocation for ACK/NACK (for physical mapping arrangements in ARQ protocols H04L1/1861)} - H04L 5/0091: {Signalling for the administration of the divided path, e.g. signalling of configuration information} - H04W 72/20: Control channels or signalling for resource management - H04L 1/0061: {Error detection codes} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04B: TRANSMISSION - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A method of a user equipment (UE) for constructing a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook. The method comprises receiving physical downlink control channels (PDCCHs) that convey respective downlink control information (DCI) formats, wherein each DCI format includes a counter field and a slot offset field, receiving physical downlink data channels (PDSCHs) that convey data transport blocks, detecting the DCI formats configuring the received PDSCHs, determining locations for HARQ-ACK bits in a HARQ-ACK codebook based on a value of the slot offset field and a value of the counter field in each detected DCI format, determining a time unit for transmission of the HARQ-ACK codebook based on a value of the slot offset field in each detected DCI format, and transmitting the HARQ-ACK codebook. ## Claims ### Claim 1 A method for a user equipment (UE), the method comprising: receiving a first physical downlink control channel (PDCCH) that provides a first downlink control information (DCI) format, wherein the first DCI format includes a type field having a first value; receiving a second PDCCH that provides a second DCI format, wherein the second DCI format includes a type field having a second value; receiving a first physical downlink shared channel (PDSCH) scheduled by the first DCI format that provides a first transport block; receiving a second PDSCH scheduled by the second DCI format that provides a second transport block; generating first hybrid automatic response request acknowledgement (HARQ-ACK) information in response to reception of the first transport block and second HARQ-ACK information in response to reception of the second transport block; multiplexing the first HARQ-ACK information and the second HARQ-ACK information in: a physical uplink control channel (PUCCH) when the first and second values are the same, or a first PUCCH and a second PUCCH, respectively, when the first and second values are different; and transmitting: the PUCCH when the first and second values are the same, or the first PUCCH and the second PUCCH when the first and second values are different. ### Claim 2 (depends on 1) The method of claim 1, wherein reception of the first PDCCH is according to a first search space configuration and reception of the second PDCCH is according to a second search space configuration. ### Claim 3 (depends on 1) The method of claim 1, wherein the first DCI format and the second DCI format are a same DCI format. ### Claim 4 (depends on 1) The method of claim 1, wherein the first DCI format and the second DCI format are different DCI formats. ### Claim 5 (depends on 1) The method of claim 1, wherein: the first DCI format includes a counter downlink assignment index (DAI) field, and a value of the counter DAI field counts only DCI formats having a same value of the type field as the first value. ### Claim 6 (depends on 1) The method of claim 1, further comprising: receiving a first configuration indicating a zero or non-zero number of bits for a counter downlink assignment index (DAI) field in the first DCI format; and receiving a second configuration indicating a zero or non-zero number of bits for a counter DAI field in the second DCI format, wherein a value of the counter DAI field in the first DCI format counts only DCI formats with a same value of the type field as the first value, and wherein a value of the counter DAI field in the second DCI format counts only DCI formats with a same value of the type field as the second value. ### Claim 7 (depends on 1) The method of claim 1 further comprising: receiving a third PDCCH that provides a third DCI format that schedules a transmission of a physical uplink shared channel (PUSCH) and includes a type field having a third value, wherein a transmission of the PUSCH would overlap in time with a transmission of the first PUCCH; determining a transmission power for the PUSCH, a transmission power for the first PUCCH, and a total transmission power that exceeds a maximum transmission power; and reducing with priority, so that a total transmission power does not exceed the maximum transmission power, the transmission power for: the PUSCH, when the third value is equal to or smaller than the first value, or the first PUCCH, when the third value is larger than the first value. ### Claim 8 (depends on 7) The method of claim 7, wherein the PUSCH includes unlink control information (UCI). ### Claim 9 A user equipment (UE) comprising: a receiver configured to: receive a first physical downlink control channel (PDCCH) that provides a first downlink control information (DCI) format, wherein the first DCI format includes a type field having a first value; receive a second PDCCH that provides a second DCI format, wherein the second DCI format includes a type field having a second value; receive a first physical downlink shared channel (PDSCH) scheduled by the first DCI format that provides a first transport block; and receive a second PDSCH scheduled by the second DCI format that provides a second transport block; and a processor operably connected to the receiver, the processor configured to generate first hybrid automatic response request acknowledgement (HARQ-ACK) information in response to reception of the first transport block and second HARQ-ACK information in response to reception of the second transport block; a multiplexer operably connected to the processor, the multiplexer configured to multiplex the first HARQ-ACK information and the second HARQ-ACK information in: a physical uplink control channel (PUCCH) when the first and second values are the same, or a first PUCCH and a second PUCCH, respectively, when the first and second values are different; and a transmitter operably connected to the processor, the transmitter configured to transmit: the PUCCH when the first and second values are the same, or the first PUCCH and the second PUCCH when the first and second values are different. ### Claim 10 (depends on 9) The UE of claim 9, wherein reception of the first PDCCH is according to a first search space configuration and reception of the second PDCCH is according to a second search space configuration. ### Claim 11 (depends on 9) The UE of claim 9, wherein the first DCI format and the second DCI format are a same DCI format. ### Claim 12 (depends on 9) The UE of claim 9, wherein the first DCI format and the second DCI format are different DCI formats. ### Claim 13 (depends on 9) The UE of claim 9, wherein: the first DCI format includes a counter downlink assignment index (DAI) field, and a value of the counter DAI field counts only DCI formats having a same value of the type field as the first value. ### Claim 14 (depends on 9) The UE of claim 9, wherein: the receiver is further configured to: receive a first configuration indicating a zero or non-zero number of bits for a counter downlink assignment index (DAI) field in the first DCI format; and receive a second configuration indicating a zero or non-zero number of bits for a counter DAI field in the second DCI format, a value of the counter DAI field in the first DCI format counts only DCI formats with a same value of the type field as the first value, and a value of the counter DAI field in the second DCI format counts only DCI formats with a same value of the type field as the second value. ### Claim 15 (depends on 9) The UE of claim 9, wherein: the receiver is further configured to receive a third PDCCH that provides a third DCI format that schedules a transmission of a physical uplink shared channel (PUSCH) and includes a type field having a third value, wherein a transmission of the PUSCH would overlap in time with a transmission of the first PUCCH; the processor is further configured to determine a transmission power for the PUSCH, determine a transmission power for the first PUCCH, and determine a total transmission power that exceeds a maximum transmission power; and the transmitter is further configured to reduce with priority, so that a total transmission power does not exceed the maximum transmission power, the transmission power for: the PUSCH, when the third value is equal to or smaller than the first value, or the first PUCCH, when the third value is larger than the first value. ### Claim 16 (depends on 15) The UE of claim 15, wherein the PUSCH includes unlink control information (UCI). ### Claim 17 A base station comprising: a transmitter configured to: transmit a first physical downlink control channel (PDCCH) that provides a first downlink control information (DCI) format, the first DCI format includes a type field having a first value; transmit a second PDCCH that provides a second DCI format, the second DCI format includes a type field having a second value; transmit a first physical downlink shared channel (PDSCH) scheduled by the first DCI format that provides a first transport block; and transmit a second PDSCH scheduled by the second DCI format that provides a second transport block; and a receiver operably connected to the transmitter, the receiver configured to receive: a physical uplink control channel (PUCCH) with HARQ-ACK information corresponding to transmission of the first PDSCH and to transmission of the second PDSCH when the first and second values are the same, or a first PUCCH with HARQ-ACK information corresponding to transmission of the first PDSCH and a second PUCCH with HARQ-ACK information corresponding to transmission of the second PDSCH when the first and second values are different. ### Claim 18 (depends on 17) The base station of claim 17, wherein transmission of the first PDCCH is according to a first search space configuration and transmission of the second PDCCH is according to a second search space configuration. ### Claim 19 (depends on 17) The base station of claim 17, wherein: the first DCI format includes a counter downlink assignment index (DAI) field, and a value of the counter DAI field counts only DCI formats having a same value of the type field as the first value. ### Claim 20 (depends on 17) The base station of claim 17, wherein: the transmitter is further configured to: transmit a first configuration indicating a zero or non-zero number of bits for a counter downlink assignment index (DAI) field in the first DCI format; and transmit a second configuration indicating a zero or non-zero number of bits for a counter DAI field in the second DCI format, a value of the counter DAI field in the first DCI format counts only DCI formats with a same value of the type field as the first value, and a value of the counter DAI field in the second DCI format counts only DCI formats with a same value of the type field as the second value.