HARQ codebook determination in wireless communications

Abstract

The invention relates to HARQ codebook determination in wireless communication. A user equipment (UE) and a network agree with the use of a hybrid automatic repeat request (HARQ) codebook. The UE: receives a plurality of downlink control information (DCI) transmissions from a base station during a corresponding plurality of physical downlink control channel (PDCCH) listening opportunities, wherein each DCI transmission schedules a plurality of physical downlink shared channel (PDSCH) transmissions on a corresponding CC of a plurality of component carriers (CCs); receiving a time domain resource allocation (TDRA) table configuration from the base station; determining a maximum number of PDSCH transmissions per CC based on the TDRA table configuration; grouping the plurality of CCs together; and determining a hybrid automatic repeat request (HARQ)-ACK codebook size based on the number of the plurality of PDSCH transmissions, a maximum number of the PDSCH transmissions, and a resulting acknowledgement (ACK) or negative acknowledgement (NACK) for each of the plurality of PDSCH transmissions.

Description

[0001] This application is a divisional application of the invention patent application with application date of October 15, 2020, application number 202080106215.5, and invention name “HARQ codebook determination in wireless communication”. Technical Field

[0002] The present application relates generally to wireless communications, and in particular to HARQ codebook determination in wireless communications. Background Art

[0003] In 5G New Radio (NR) wireless communications, the 5G NR network uses downlink channel information (DCI) to configure the physical downlink control channel (PDCCH) to schedule the physical downlink shared channel (PDSCH). The user equipment (UE) receives the PDCCH and decodes the DCI so that the UE can determine when to monitor the PDSCH. If the UE successfully decodes the PDSCH, the UE transmits an acknowledgment (ACK) to the network. If the UE does not successfully decode the PDSCH, the UE transmits a negative ACK (NACK) to the network. Summary of the invention

[0004] Some exemplary embodiments relate to a user equipment (UE) having: a transceiver configured to communicate with a network; and a processor communicatively coupled to the transceiver and configured to perform operations. The operations include: receiving multiple downlink control information (DCI) transmissions from the base station during corresponding multiple physical downlink control channel (PDCCH) listening opportunities, wherein each DCI transmission schedules multiple physical downlink shared channel (PDSCH) transmissions on a corresponding CC in multiple component carriers (CCs); receiving a time domain resource allocation (TDRA) table configuration from the base station; determining a maximum number of PDSCH transmissions per CC based on the TDRA table configuration; grouping the multiple CCs together; and determining a hybrid automatic repeat request (HARQ)-ACK codebook size based on the number of the multiple PDSCH transmissions, the maximum number of the PDSCH transmissions, and a resulting acknowledgement (ACK) or negative acknowledgement (NACK) for each of the multiple PDSCH transmissions.

[0005] Other exemplary embodiments relate to a processor configured to perform operations. The operations include: receiving multiple downlink control information (DCI) transmissions from a base station during corresponding multiple physical downlink control channel (PDCCH) listening opportunities, wherein each DCI transmission schedules multiple physical downlink shared channel (PDSCH) transmissions on a corresponding CC in multiple component carriers (CCs); receiving a time domain resource allocation (TDRA) table configuration from the base station; determining a maximum number of PDSCH transmissions per CC based on the TDRA table configuration; grouping the multiple CCs together; and determining a hybrid automatic repeat request (HARQ)-ACK codebook size based on the number of the multiple PDSCH transmissions, the maximum number of the PDSCH transmissions, and a resulting acknowledgement (ACK) or negative acknowledgement (NACK) for each of the multiple PDSCH transmissions.

[0006] Another exemplary embodiment relates to a base station having: a transceiver configured to communicate with a user equipment (UE); and a processor communicatively coupled to the transceiver and configured to perform operations. The operations include: transmitting a plurality of downlink control information (DCI) transmissions from the base station to the UE during corresponding plurality of physical downlink control channel (PDCCH) listening opportunities, wherein each DCI transmission schedules a plurality of physical downlink shared channel (PDSCH) transmissions on a corresponding CC in a plurality of component carriers (CCs); transmitting a time domain resource allocation (TDRA) table configuration to the UE; determining a maximum number of PDSCH transmissions per CC based on the TDRA table configuration; transmitting the plurality of PDSCH transmissions to the UE, wherein the UE determines a hybrid automatic repeat request (HARQ)-ACK codebook size based on the number of the plurality of PDSCH transmissions, the maximum number of the PDSCH transmissions, and a resulting acknowledgement (ACK) or negative acknowledgement (NACK) for each of the plurality of PDSCH transmissions. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0008] Figure 2 An exemplary UE according to various exemplary embodiments is shown.

[0009] Figure 3 An exemplary base station configured to establish a connection with a user equipment is shown according to various exemplary embodiments.

[0010] Figure 4 Methods of determining a hybrid automatic repeat request (HARQ) codebook size according to various exemplary embodiments are shown.

[0011] Figure 5 An exemplary table of a time domain resource allocation (TDRA) table is shown in accordance with various exemplary embodiments.

[0012] Figure 6 A diagram illustrating an exemplary multiple PDSCH reception scenario according to various exemplary embodiments is shown.

[0013] 7A to 7C A diagram illustrating an exemplary HARQ-ACK compression scheme according to various exemplary embodiments is shown.

[0014] Figure 8 A diagram illustrating an exemplary HARQ-ACK compression scheme according to various exemplary embodiments is shown.

[0015] Fig. 9A Pseudo code illustrating a Type I HARQ codebook determination process according to various exemplary embodiments is shown.

[0016] Fig. 9B A diagram illustrating a Type I HARQ codebook determination process according to various exemplary embodiments is shown. DETAILED DESCRIPTION

[0017] The exemplary embodiments may be further understood with reference to the following description and the related drawings, wherein similar elements have the same reference numerals. The exemplary embodiments describe devices, systems and methods for determining a hybrid automatic repeat request (HARQ) codebook size for multi-PDSCH scheduling by a user equipment (UE) for a 5G new radio (NR) network.

[0018] The exemplary embodiments are described with reference to a network including a 5G New Radio NR radio access technology (RAT). However, the exemplary embodiments may be implemented in other types of networks using the principles described herein.

[0019] The exemplary embodiments are also described with reference to a UE. However, the use of a UE is for illustrative purposes only. The exemplary embodiments can be utilized with any electronic component that can establish a connection with a network and is configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, the UE described herein is used to represent any electronic component.

[0020] 5G NR is currently needed to address the critical power capabilities of Reduced Capability (RedCap) UEs. One feature that has a significant impact on the power consumption of a RedCap UE is the large number of times it monitors the PDCCH.

[0021] According to some exemplary embodiments, a multi-PDSCH scheduling downlink control information (DCI) format may be used to expand a PDCCH monitoring period, thereby reducing power consumption at the UE. In addition, to avoid differences between the UE and the g-NodeB (gNB) regarding the payload size of the HARQ-ACK in response to the multi-PDSCH scheduling DCI, the UE is configured to determine the HARQ codebook size so that both the UE and the base station (e.g., the next generation Node B (gNB)) agree on the HARQ-ACK payload size, particularly when the UE does not successfully decode the DCI for the PDCCH monitoring opportunity.

[0022] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. It should be noted that any number of UEs may be used in the network arrangement 100. Those skilled in the art will appreciate that the UE 110 may alternatively be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a phablet, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. It should also be appreciated that an actual network arrangement may include any number of UEs used by any number of users. Therefore, for illustrative purposes, only an example with a single UE 110 is provided.

[0023] UE 110 may be configured to communicate with one or more networks. In the example of network configuration 100, the networks with which UE 110 may wirelessly communicate are 5G New Radio (NR) radio access network (5GNR-RAN) 120, LTE radio access network (LTE-RAN) 122, and wireless local area network (WLAN) 124. However, it should be understood that UE 110 may also communicate with other types of networks, and UE 110 may also communicate with the network through a wired connection. Therefore, UE 110 may include a 5G NR chipset that communicates with 5G NR-RAN 120, an LTE chipset that communicates with LTE-RAN 122, and an ISM chipset that communicates with WLAN 124.

[0024] 5G NR-RAN 120 and LTE-RAN 122 may be parts of cellular networks that may be deployed by cellular providers (e.g., Verizon, AT&T, T-Mobile, etc.). These networks 120, 122 may include, for example, cells or base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. WLAN 124 may include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.).

[0025] UE 110 may be connected to 5G NR-RAN 120 via gNB 120A and / or gNB 120B. During operation, UE 110 may be within range of multiple gNBs. Thus, simultaneously or alternatively, UE 110 may be connected to 5G NR-RAN 120 via gNBs 120A and 120B. In addition, UE 110 may communicate with eNB 122A of LTE-RAN 122 to transmit and receive control information for downlink and / or uplink synchronization with respect to 5G NR-RAN 120 connection.

[0026] Those skilled in the art will appreciate that any relevant process may be performed for the UE 110 to connect to the 5G NR-RAN 120. For example, as described above, the 5G NR-RAN 120 may be associated with a particular cellular provider, where the UE 110 and / or its user has a protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR-RAN 120, the UE 110 may transmit corresponding credential information in order to associate with the 5G NR-RAN 120. More specifically, the UE 110 may be associated with a particular base station (e.g., gNB 120A of the 5G NR-RAN 120).

[0027] In addition to networks 120, 122, and 124, network arrangement 100 includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. Cellular core network 130 (e.g., 5GC of NR) can be considered as an interconnected collection of components that manage the operation and traffic of a cellular network. Cellular core network 130 also manages traffic flowing between the cellular network and the Internet 140.

[0028] The IMS 150 may be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 may be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that may be used to extend the functionality of the UE 110 to communicate with various networks.

[0029] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 1 100 is used to describe the UE 110. The UE 110 may represent any electronic device and may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. The other components 230 may include, for example, an audio input device, an audio output device, a battery providing a limited power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, one or more antenna panels, etc. For example, the UE 110 may be coupled to industrial equipment via one or more ports.

[0030] The processor 205 may be configured to execute multiple engines of the UE 110. For example, the engine may include a HARQ management engine 235. The HARQ management engine 235 may perform various operations related to determining a HARQ codebook size for a multi-PDSCH scheduling scenario. An example of this process will be described in more detail below.

[0031] The above-described engine as an application (e.g., program) executed by the processor 205 is merely exemplary. The functions associated with the engine may also be represented as an independent combined component of the UE 110, or may be a modular component coupled to the UE 110, for example, an integrated circuit with or without firmware. For example, an integrated circuit may include an input circuit system for receiving a signal and a processing circuit system for processing signals and other information. The engine may also be embodied as an application or multiple separate applications. In addition, in some UEs, the functionality described for the processor 205 is shared between two or more processors such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0032] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, and the I / O device 220 may be a hardware component that enables user input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, LTE-RAN 122, WLAN 124, etc. Thus, the transceiver 225 may operate on multiple different frequencies or channels (e.g., a continuous set of frequencies).

[0033] Figure 3 An exemplary network cell, in this case gNB 120A, is shown according to various exemplary embodiments. gNB 120A may represent any access node of a 5G NR network that UE 110 may use to establish a connection. Figure 3 The gNB 120A shown may also represent gNB 120B.

[0034] The gNB 120A may include a processor 305, a memory arrangement 310, an input / output (I / O) device 320, a transceiver 325, and other components 330. The other components 330 may include, for example, a power supply, a data acquisition device, a port for electrically connecting the gNB 120A to other electronic devices, and the like.

[0035] Processor 305 may be configured to execute multiple engines of gNB 120A. For example, the engines may include a PDSCH management engine 335 for performing operations including configuring a multi-PDSCH scheduling DCI for UE 110. An example of this process is described in more detail below.

[0036] The engine described above as an application (e.g., program) executed by the processor 305 is merely exemplary. The functionality associated with the engine may also be represented as a stand-alone integrated component of the gNB 120A, or may be a modular component coupled to the gNB 120A, such as an integrated circuit with or without firmware. For example, an integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. In addition, in some gNBs, the functionality described for the processor 305 is split between multiple processors (e.g., a baseband processor, an application processor, etc.). The exemplary aspects may be implemented in any of these or other configurations of the gNB.

[0037] The memory 310 may be a hardware component configured to store data related to operations performed by the UE 110, 112. The I / O device 320 may be a hardware component or port that enables a user to interact with the gNB 120A. The transceiver 325 may be a hardware component configured to exchange data with the UE 110 and any other UE in the system 100. The transceiver 325 may operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies). Thus, the transceiver 325 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.

[0038] Figure 4 A method 400 of determining a HARQ codebook size according to various exemplary embodiments is shown. At 405, UE 110 receives a DCI during a PDCCH listening occasion. In some embodiments, UE 110 receives multiple DCIs corresponding to multiple PDCCH listening occasions. Each DCI schedules multiple PDSCHs. At 410, UE 110 receives up to a maximum number of DCIs for a serving cell or component carrier (CC) index "i". The UE 110 determines the time domain resource allocation (TDRA) for the PDSCH or transport block (TB) of the UE 110 based on the TDRA table configured by the RRC signal for the UE's serving cell or CC index "i". In some embodiments, different CCs may be configured with different TDRA tables through RRC signaling. The time domain resource allocation for a given PDSCH reception on a CC is indicated by the received DCI based on the RRC_Configured TDRA.

[0039] Figure 5 An example of a TDRA table for four different serving cells or CCs (i.e., CC0, CC1, CC2, CC3) is shown. In some embodiments, the number of transport blocks (TBs) 504 actually scheduled by a single DCI is signaled by the selected row index 502 of the TDRA table configured by the RRC for the corresponding CC. In some embodiments, a different row index 502 may be selected on a per PDCCH opportunity basis and then signaled by the DCI. Based on each TDRA table, the maximum number of TBs per TDRA table per serving cell / CC is determined to be 506.

[0040] In some embodiments, gNB 120A may alternatively configure one or more serving cell groups for UE 110 via radio resource control (RRC) configuration. In some embodiments, each group is configured with a maximum number of single DCIs. In some embodiments, UE 110 alternatively determines based on the maximum number of TDRA / TB (e.g., 504) associated with a single TDRA row (e.g., 502) for multi-PDSCH scheduling.

[0041] return Figure 4 At 420, for HARQ-ACK bit determination, UE 110 may convert the In this scenario, the maximum number of PDSCHs in a given CC group is equal In some embodiments, CC grouping may alternatively be configured via RRC signaling from gNB 120A. In this scenario, the maximum number of PDSCHs in a given CC group is Equal to the maximum number of PDSCHs in any CC in the group's CCs

[0042] In some embodiments, the DCI received during the PDCCH listening opportunity includes two downlink allocation indicators (DAI) specific to each CC group: a count DAI (C-DAI) and a total DAI (T-DAI). The C-DAI indicates the cumulative number of PDCCH listening opportunities in the CC group up to the current CC and the current PDSCH listening opportunity. The C-DAI is first counted by incrementing the CC index number and then by incrementing the listening opportunity index number. The T-DAI indicates the total number of PDCCH listening opportunities in the CC group. In some embodiments, the T-DAI can be updated from one PDCCH listening opportunity to the next PDCCH listening opportunity. For example, although the DCI of a PDSCH listening opportunity may indicate that the T-DAI is 3, the T-DAI may be updated in a later PDCCH listening opportunity to reflect a different number (e.g., 4)), which includes all PDCCHs scheduled across CCs until the current time slot of the transmission T_DAI.

[0043] At 425, UE 110 determines the HARQ codebook size. In some embodiments, for each multi-PDSCH scheduling DCI received, UE 110 specifies a HARQ codebook size for the HARQ-ACK response. Then, UE 110 generates ACK or NACK based on the result of decoding each scheduled PDSCH. is greater than the number of PDSCHs actually scheduled, UE 110 generates a NACK for the difference to ensure that the codebook size used for each multi-PDSCH transmission is constant. For example, if the DCI schedules 2 PDSCHs and Then UE 110 will generate 4 information bits for the HARQ-ACK response for this multiple PDSCH scheduling opportunity. The first 2 bits are ACK / NACK, depending on the result of decoding each of the 2 scheduled PDSCHs. The second 2 bits are NACK because Greater than 2 scheduled PDSCHs. For example, if UE 110 successfully decodes two PDSCHs, the resulting HARQ-ACK response will be ACK, ACK, NACK, NACK.

[0044] Figure 6 A diagram illustrating an exemplary multiple PDSCH reception scenario according to various exemplary embodiments is shown. Figure 6 Assume four CCs, and Figure 5 The TDRA tables are applicable to these four CCs. is 4, then Therefore, for each successfully received DCI, UE 110 will generate 4 HARQ-ACK bits. Figure 6 As shown, UE110 successfully receives / decodes the multi-PDSCH scheduling DCI of PDCCH monitoring opportunities 602a, 604a, 606a, 608a and 612a. As described above, due to The UE will then generate 4 HARQ-ACK bits regardless of how many PDSCHs are actually scheduled to ensure that there is no mismatch between UE 110 and gNB 120A regarding the number of HARQ-ACK bits in the event of a missed DCI detection at the UE side. The difference between the actual scheduled PDSCH and the actual scheduled PDSCH will generate a NACK for each additional HARQ-ACK bit. Thus, UE 110 will generate ACK, ACK, NACK, NACK for PDSCH 602b and 602c, ACK, ACK, ACK, ACK for PDSCH 604b-604e; ACK, ACK, ACK, NACK for PDSCH 606b-606d, ACK, ACK, ACK, NACK for PDSCH 608b-608e, and ACK, ACK, ACK, NACK for PDSCH 612b and 612c.

[0045] Although UE 110 successfully processes multiple PDSCH transmissions 602, 604, 606, 608, and 612, UE 110 does not successfully receive / process / detect PDCCH 610a. Because each PDCCH monitoring opportunity includes C-DAI and T-DAI, UE 110 understands that it has not received DCI. Figure 6 As shown, the C-DAI and T-DAI of the PDCCH monitoring opportunities 602a-606a are (1,3), (2,3) and (3,3), respectively. Therefore, when UE 110 receives DCI at PDCCH monitoring opportunity 602a, UE 110 knows that this is the first monitoring opportunity of a total of three monitoring opportunities. Similarly, the second PDCCH monitoring opportunity 604a is the second monitoring opportunity of a total of three monitoring opportunities. The T-DAI of the PDCCH monitoring opportunity 608a is updated to 4. Therefore, the C-DAI and T-DAI of the PDCCH monitoring opportunity 608a are (4,4). As described above, the C-DAI is counted first by CC index (C0-C3) and then by PSCCH monitoring opportunity. In other words, reference Figure 6 , the C-DAI is counted first from top to bottom (by CC index) and then from left to right (by PDCCH monitoring opportunity).

[0046] When UE 110 receives the DCI of PDCCH monitoring opportunity 612a, UE 110 similarly knows that this PDCCH monitoring opportunity is the second monitoring opportunity of the total two monitoring opportunities. Since UE 110 has not received the DCI of the PDCCH monitoring opportunity with C-DAI and T-DAI (1, 2) (the first monitoring opportunity of the total two monitoring opportunities indicated in PDCCH monitoring opportunity 612a), UE 110 knows that it has missed the DCI.

[0047] The HARQ-ACK codebook size may be determined based on the following items: the T-DAI of the last detected PDCCH monitoring opportunity and Specifically, the product of these two parameters. Figure 6 In the scenario depicted in FIG, the last T-DAI of the last detected PDCCH listening opportunity 612a is 2. However, because UE 110 previously detected a T-DAI value of 4 in CC1, UE 110 determines that it has missed the DCI and the T-DAI used to determine the HARQ-ACK codebook size is actually 6 (4+2). As previously described, Therefore, the codebook size is 24 bits. As a result of this process, both UE 110 and gNB 120A agree on a 24-bit HARQ-ACK codebook size. gNB 120A configures 6 PDCCH monitoring opportunities. is 4, gNB 120A will expect a 24-bit HARQ-ACK payload. Although UE 110 misses the DCI of one of the PDCCH listening occasions, the C-DAI and T-DAI inform UE 110 of this failure, and UE 110 is still able to determine the correct 24-bit HARQ-ACK payload size.

[0048] Figure 6 Also shown in FIG. 6 is a PUCCH transmission 614. Figure 6 In the example shown, it is assumed that UE 110 is configured with a set of K1 values ​​for HARQ-ACK feedback, where K1 can be 2, 3, 4, 6, 7, 8. The K1 value indicates how many TBs from the last TB of the multi-PDSCH transmission the PUCCH 614 is sent (e.g., for multi-PDSCH transmission 602, K1=8).

[0049] In some implementations, in addition to CC grouping 420, UE 110 may also perform HARQ-ACK compression. 7A to 7C A diagram illustrating an exemplary HARQ-ACK compression scheme according to various exemplary embodiments is shown. In some embodiments, UE 110 may utilize a compression window having a size W, where And α group,k is the compression factor (1 / 4,1 / 2,1). Compression factor α group,k =1 means there is no compression. In some embodiments, the value α group,k May be configured by gNB 120A on a per-UE basis via RRC signaling. In the following description, Will represent the number of TB / PDSCHs scheduled by gNB 120A at PDCCH monitoring occasion “m”.

[0050] if is less than or equal to W, the HARQ-ACK bit sequence generated by UE 110 will include the decoding result based on the PDSCH HARQ-ACK bit plus Each bit in the bit has a NACK value. Fig. 7A As shown, there are two scheduled PDSCHs 704a and 704b The PDCCH listening opportunity 702 of W=4 is scheduled for UE 110. Assuming that window 710 has a size of W=4, HARQ-ACK bit sequence 706 includes ACK, ACK (assuming both PDSCH 704a, 704b are successfully decoded), and two NACKs (W- ) is filled 708.

[0051] However, if is greater than W, then UE 110 may Divided into S= bits of size for the first subwindow and have values ​​corresponding to the rest The second sub-window of the scheduled PDSCH bits. Figure 7B As shown, there are 5 The PDCCH listening opportunities 712 of the scheduled PDSCHs 714a-714e are scheduled for the UE 110. Assuming the window has a size of W=2, the sub-window size S will be (5 / 2=3) (rounded to the nearest integer). As a result, the first sub-window 720a includes 3 bits corresponding to the scheduled PDSCHs 714a-714c, and the second sub-window 720b includes 2 bits corresponding to the remaining scheduled PDSCHs 714d and 714e. Figure 7B Assume that PDSCH 714d is not decoded correctly. Therefore, the HARQ-ACK bit sequence 716 is ACK, ACK, ACK, NACK, ACK. The compression scheme in this example generates an ACK for the first sub-window 720a and a NACK for the second sub-window 720b (due to the presence of a NACK in sub-window 720b). Therefore, gNB 120a will retransmit both PDSCH 714d and 714e associated with the second sub-window 720b.

[0052] In some embodiments, UE 110 may alternatively group j PDSCHs together in a first subgroup, where j is less than W, and group the remaining (Wj) PDSCHs together in a second subgroup. The motivation behind this grouping is that due to the channel correlation characteristics in time, there is a close correlation in the decoding of PDSCHs in the time domain. For example, Figure 7C As shown, there are 5 PDCCH listening opportunities 722 for scheduled PDSCHs 724a-724e are scheduled for UE 110. Assuming the window has a size of W=2, a first sub-window 730a includes 1 bit corresponding to scheduled PDSCH 724a, and a second sub-window 730b includes 4 bits corresponding to scheduled PDSCHs 724b-724e. Figure 7C It is also assumed that PDSCH 724d is not decoded correctly. Therefore, the HARQ-ACK bit sequence 726 is ACK, ACK, ACK, NACK, ACK. The compression scheme in this example generates an ACK for the first sub-window 730a and a NACK for the second sub-window 730b (due to the presence of a NACK in sub-window 730b). Therefore, gNB 120a will retransmit PDSCH 714b, 714c, 714d, and 714e associated with the second sub-window 730b.

[0053] In some embodiments, the HARQ-ACK codebook may indicate the number of consecutive PDSCH receptions scheduled by a single multi-PDSCH DCI format and successfully decoded at the UE side. An example of a 2-bit HARQ-ACK code state is provided in the following table. This codebook advantageously indicates to the gNB 120A how many PDSCHs the UE has successfully decoded (starting with the first scheduled PDSCH with DAI=1) and therefore how many failed PDSCHs should be retransmitted.

[0054]

[0055] Figure 8 A diagram illustrating an exemplary HARQ-ACK compression scheme according to various exemplary embodiments is shown. Figure 8 As shown, there are 5 The PDCCH monitoring occasions 802 of the scheduled PDSCHs 804a-804e are scheduled for the UE 110. Assuming the window has a size of W=2, the sub-window size S will be (5 / 2=3) (rounded to the nearest integer). Figure 8 Assume that PDSCH 804c and 804d are not decoded correctly. As a result, HARQ-ACK bit sequence 806 is ACK, ACK, NACK, NACK, ACK. Compressed HARQ-ACK bit sequence 810 is based on the above with respect to Figure 7B As a result of the compression scheme 810, gNB 120a will retransmit all five PDSCHs 804a-804e. The compressed HARQ-ACK bit sequence 820 is based on the above description with respect to Figure 7C As a result of the compression scheme 820, gNB 120a will retransmit the last four PDSCHs 804b-804e.

[0056] Based on the above table, UE 110 uses compression scheme 830 to group the first two PDSCHs in a first subwindow with 2 bits (which corresponds to 2 consecutive ACKs for PDSCH 804a and 804b), and groups the last three PDSCHs in a second subwindow with 3 bits (which corresponds to the remaining scheduled PDSCH 804c-804e). Compression scheme 830 generates an ACK for the first subwindow and a NACK for the second subwindow (due to the presence of two NACKs in the second subwindow). As a result of compression scheme 830, gNB 120a will retransmit PDSCH 804c-804e. It should be noted that although one scheme may appear to produce better results than another, the results discussed above are based primarily on the above variables ( α group,k, W, S, etc.), and therefore the results are determined by the values ​​of these variables.

[0057] Fig. 9A Pseudo code illustrating a Type I HARQ codebook determination process according to various exemplary embodiments is shown. Fig. 9B A diagram illustrating a Type I HARQ codebook determination process according to various exemplary embodiments is shown. In some embodiments, UE 110 is configured with multiple K1 values. The UE then uses the configured K1 values ​​and Fig. 9A The pseudo code shown in FIG. 1 determines the PDCCH monitoring timing and the maximum number of scheduled TBs corresponding to different multiple PDSCH transmissions. Fig. 9B As shown, UE 110 may be configured with K1 values ​​(8, 6, 5, 3, 2) corresponding to PUCCH transmissions 908. Based on these K1 values, the UE determines a first multiple PDSCH transmission 902 corresponding to K1=8, a second multiple PDSCH transmission 904 corresponding to K1=6, and a third multiple PDSCH transmission 906 corresponding to K1=3. Fig. 9B Assume that there is no valid TDRA for K1=5 and K1=2. The Type I HARQ codebook excludes overlap between scheduled multiple PDSCHs. Fig. 9B As shown, only 2 TBs after the end of the first multi-PDSCH transmission 902 are shown. Similarly, only 2 TBs after K1=5 are shown. Therefore, the resulting HARQ-ACK payload size (codebook size) is 12 bits (8 bits from the first multi-PDSCH transmission 902, 2 bits from the second multi-PDSCH transmission 904, and 2 bits from the third multi-PDSCH transmission 906).

[0058] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. In other examples, the exemplary embodiments of the above methods may be embodied as a program including lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0059] Although this patent application describes various combinations of various aspects, each with different features, those skilled in the art will understand that any feature of one aspect may be combined with features of other aspects or features that are not functionally or logically inconsistent with the operation or function of the device of the aspects disclosed in the present invention in any manner not publicly denied.

[0060] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0061] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. An apparatus comprising a processing circuit, the processing circuit being configured to: processing a plurality of downlink control information (DCI) transmissions during a corresponding plurality of physical downlink control channel (PDCCH) monitoring opportunities based on signaling from a base station, wherein each DCI transmission schedules a plurality of physical downlink shared channel (PDSCH) transmissions on a corresponding one of a plurality of component carriers (CCs); Determine the maximum number of PDSCH transmissions per CC; grouping the CCs into one or more CC groups; Determining a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook size; as well as A plurality of HARQ bits is generated for each of the plurality of PDSCH transmissions, wherein the plurality of HARQ bits is equal to a maximum number of the PDSCH transmissions per CC group.

2. The apparatus of claim 1, wherein each HARQ bit corresponds to an acknowledgement (ACK) or a negative acknowledgement (NACK) based on decoding of each of the plurality of PDSCH transmissions.

3. The apparatus of claim 1 , wherein the plurality of HARQ bits include a decoding acknowledgement (ACK) for each of the plurality of PDSCH transmissions and one or more negative acknowledgement (NACK) bits corresponding to a difference between the plurality of multi-PDSCH transmissions and a maximum number of the PDSCH transmissions per CC group.

4. The apparatus of claim 3, wherein the HARQ-ACK codebook size is based on a total downlink allocation indicator (T-DAI) of a last PDCCH listening occasion and a maximum number of the PDSCH transmissions per CC group.

5. A user equipment (UE), comprising: a transceiver circuit configured to communicate with a base station; and a processor circuit communicatively coupled to the transceiver circuit and configured to: processing a plurality of downlink control information (DCI) transmissions during a corresponding plurality of physical downlink control channel (PDCCH) monitoring opportunities based on signaling from the base station, wherein each DCI transmission schedules a plurality of physical downlink shared channel (PDSCH) transmissions on a corresponding one of a plurality of component carriers (CCs); Determine the maximum number of PDSCH transmissions per CC; grouping the CCs into one or more CC groups; Determining a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook size; as well as A plurality of HARQ bits is generated for each of the plurality of PDSCH transmissions, wherein the plurality of HARQ bits is equal to a maximum number of the PDSCH transmissions per CC group.

6. The UE of claim 5, wherein each HARQ bit corresponds to an acknowledgement (ACK) or a negative acknowledgement (NACK) based on decoding of each of the plurality of PDSCH transmissions.

7. The UE of claim 5, wherein the plurality of HARQ bits include a decoding acknowledgement (ACK) for each of the plurality of PDSCH transmissions and one or more negative acknowledgement (NACK) bits corresponding to a difference between the plurality of multi-PDSCH transmissions and a maximum number of the PDSCH transmissions for each CC group.

8. The UE of claim 7, wherein the HARQ-ACK codebook size is based on a total downlink allocation indicator (T-DAI) of a last PDCCH listening occasion and a maximum number of the PDSCH transmissions per CC group.

9. A method comprising: processing a plurality of downlink control information (DCI) transmissions during a corresponding plurality of physical downlink control channel (PDCCH) monitoring opportunities based on signaling from a base station, wherein each DCI transmission schedules a plurality of physical downlink shared channel (PDSCH) transmissions on a corresponding one of a plurality of component carriers (CCs); Determine the maximum number of PDSCH transmissions per CC; grouping the CCs into one or more CC groups; Determining a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook size; as well as A plurality of HARQ bits is generated for each of the plurality of PDSCH transmissions, wherein the plurality of HARQ bits is equal to a maximum number of the PDSCH transmissions per CC group.

10. The method of claim 9, wherein each HARQ bit corresponds to an acknowledgement (ACK) or a negative acknowledgement (NACK) based on decoding each of the plurality of PDSCH transmissions.

11. The method of claim 9, wherein the plurality of HARQ bits include a decoding acknowledgement (ACK) for each of the plurality of PDSCH transmissions and one or more negative acknowledgement (NACK) bits corresponding to a difference between the plurality of multi-PDSCH transmissions and a maximum number of the PDSCH transmissions per CC group.

12. The method of claim 11, wherein the HARQ-ACK codebook size is based on a total downlink allocation indicator (T-DAI) of a last PDCCH listening occasion and a maximum number of the PDSCH transmissions per CC group.

Images