System and method for feedback information transmission

Abstract

The present disclosure relates to systems, apparatus, non-transitory computer-readable media, and methods for transmitting, by a network, a downlink transmission to a wireless communication device, and receiving, by the network, feedback information for the downlink transmission from the wireless communication device in an uplink transmission scheduled by a first downlink control information (DCI). The feedback information corresponds to a codebook or comprises a codebook, and the codebook comprises at least one of a first sub-codebook and a second sub-codebook based on the receiving time of the first DCI.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more specifically, to Hybrid Automatic Repeat Request (HARQ). Background Technology

[0002] Current mobile networks provide users with virtually ubiquitous wireless access and data transmission services. As users continue to demand increasingly higher data rates, various technologies have been developed to improve data rates and the reliability of data transmission between the network and individual user equipment (UE). In fifth-generation mobile network systems (5GC), HARQ is a key technology in New Radio (NR) systems. HARQ functionality enhances the reliability of data transmission. Summary of the Invention

[0003] The exemplary arrangements disclosed herein are intended to address problems related to one or more issues presented in the prior art, and to provide additional features that will become apparent when taken in conjunction with the accompanying drawings and by referring to the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various arrangements. However, it should be understood that these arrangements are presented by way of example and are not limiting, and that various modifications can be made to the disclosed arrangements while remaining within the scope of this disclosure, as will be apparent to those skilled in the art who have read this disclosure.

[0004] The arrangements disclosed herein relate to systems, apparatuses, non-transient computer-readable media, and methods for transmitting downlink (DL) transmissions from a network (e.g., a base station) to a wireless communication device (user equipment (UE)) and for receiving from the wireless communication device feedback information for DL ​​transmissions in uplink (UL) transmissions scheduled by a first downlink control information (DCI) (e.g., UL DCI). The feedback information corresponds to or includes a codebook comprising at least one of a first sub-codebook and a second sub-codebook based on the reception time of the first DCI.

[0005] The arrangements disclosed herein relate to systems, apparatuses, non-transient computer-readable media, and methods for receiving DL transmissions from a network (e.g., a base station) by a wireless communication device (e.g., a UE). The wireless communication device transmits feedback information for the DL transmission to the network during a UL transmission scheduled by a first DCI. This feedback information corresponds to a codebook including a first sub-codebook and a second sub-codebook based on the reception time of the first DCI.

[0006] The above and other aspects and their embodiments are described in more detail in the accompanying drawings, specification and claims. Attached Figure Description

[0007] Various example arrangements of this solution are described in detail below with reference to the accompanying drawings. The drawings are provided for illustrative purposes only and merely depict example arrangements of this solution to aid the reader's understanding. Therefore, the drawings should not be considered as limitations on the breadth, scope, or applicability of this solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of explanation.

[0008] Figure 1 An example wireless communication system based on some arrangement is shown.

[0009] Figure 2 A block diagram of an example base station and an example UE device based on some arrangements is shown.

[0010] Figure 3 This is a diagram illustrating example wireless communication methods according to various arrangements.

[0011] Figure 4 This is a diagram illustrating example wireless communication methods for transmitting feedback information according to various arrangements.

[0012] Figure 5 This is a flowchart illustrating example wireless communication methods according to various arrangements.

[0013] Figure 5 This is a flowchart illustrating example wireless communication methods according to various arrangements.

[0014] Figure 6 This is a diagram illustrating example wireless communication methods for transmitting feedback information according to various arrangements.

[0015] Figure 7 This is a diagram illustrating example wireless communication methods for transmitting feedback information according to various arrangements.

[0016] Figure 8 This is a diagram illustrating example wireless communication methods for transmitting feedback information according to various arrangements. Detailed Implementation

[0017] Various example arrangements of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to manufacture and use this solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein after reading this disclosure without departing from the scope of this solution. Therefore, this solution is not limited to the example arrangements and applications described and shown herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely an example method. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art should understand that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0018] In a wireless communication system, a wireless communication device (e.g., a UE) can communicate with a network (e.g., a base station). As part of the communication process, the UE and the network can use feedback procedures (e.g., HARQ procedures) to improve data rate and data transmission reliability. For example, HARQ can be included in both the Media Access Control (MAC) and Physical Layer (PHY) layers to enhance data transmission reliability.

[0019] In some cases, the HARQ feedback codebook and UL data can be scheduled within the same UL time slot. Both the codebook and UL data can be transmitted by the UE to the network in the Physical Uplink Shared Channel (PUSCH). In some examples, UL data resources can be punctured by HARQ feedback codebook resources. In some examples, UL data resources can be transmitted by rate matching with resources in the HARQ feedback codebook. For a UE scheduled to provide feedback in the PUSCH, some DL transmissions, or some DL transmissions scheduled in the DL time slot by the DL DCI, may not be characterized (e.g., included) in the feedback codebook after UL authorization. The UE can determine the HARQ feedback codebook size based on the UL Total Downlink Allocation Index (DAI) value. For example, the UL Total DAI can be sent by the network to the UE along with the UL authorization in the DCI message. In some cases, the number of all DL transmissions to be included in the feedback codebook can be indicated (e.g., in a field of the DCI or via the UL Total DAI value). However, some wireless communication systems (e.g., NR systems) can support additional DL transmissions scheduled by DL DCI between UL grant and feedback slots carrying feedback codebooks. The configurations disclosed herein provide feedback support for such additional DL transmissions (e.g., support for both DL transmissions before and after the UL grant slot) to enhance the feedback process for DL ​​transmissions before and after the UL grant slot (e.g., the UL-granted slot). For example, the arrangements disclosed herein can support feedback information for the Physical Downlink Shared Channel (PDSCH) before and after the UL grant in a PUSCH scheduled by the UL grant. This feedback information allows DL scheduling after the UL DCI, which can result in improved system transmission efficiency and reduced feedback latency. In some cases, DL slots after the UL grant are referred to as post-UL-granted DL slots.

[0020] Figure 1 An example wireless communication system 100 according to an embodiment of this disclosure is illustrated, in which the techniques disclosed herein can be implemented. In the following discussion, the wireless communication system 100 can implement any wireless network such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as system 100. Such an example system 100 includes base stations (BS) 102 and UEs 104 that can communicate with each other via a communication link 110 (e.g., a wireless communication channel), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1In this context, BS102 and UE104 are located within the corresponding geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one BS that operates on its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0021] For example, BS102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS102 and UE 104 can communicate via DL radio frame 118 and UL radio frame 124, respectively. That is, BS102 can use DL radio frame 118 to send data, messages, signals, and information to UE 104, and UE 104 can use UL radio frame 124 to send data, information, signals, and messages to BS102. Each radio frame 118 or 124 can also be divided into subframes 120 or 127. Each subframe may include one or more time slots. Each subframe or time slot may include one or more data symbols 122 or 128. In this disclosure, BS102 and UE 104 are described herein as non-limiting examples of communication nodes that can generally practice the methods disclosed herein. According to various embodiments of this solution, such communication nodes are capable of wireless communication. In some embodiments, the wireless communication system 100 can support MIMO communication. For example, MIMO is a key technology in NR systems. MIMO can function in both frequency division duplex (FDD) and time division duplex (TDD) systems.

[0022] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to certain embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating characteristics that do not need to be described in detail herein. In one illustrative embodiment, as described above, system 200 can be used in applications such as... Figure 1 In a wireless communication environment such as 100, data symbols are transmitted (e.g., sent and received).

[0023] System 200 typically includes BS 202 and UE 204. BS 202 is an example of BS 102. UE 204 is an example of UE 104. BS 202 includes a BS transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with each other as needed via a data communication bus 220. UE 204 includes a UE transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for data transmission as described herein.

[0024] System 200 may also include Figure 2 Any number of modules other than those shown herein. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps are generally described according to their functionality. Whether this functionality is implemented as hardware, firmware, or software depends on the specific application and design constraints on the overall system. Those skilled in the art can implement this functionality appropriately for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0025] According to some embodiments, UE transceiver 230 may be referred to herein as UL transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to antenna 232. A duplex switch (not shown) may alternatively couple the UL transmitter or receiver to the UL antenna in a time-division duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred herein as “downlink” transceiver 210, which includes an RF transmitter and an RF receiver, each of which includes circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that while the downlink transmitter is coupled to downlink antenna 212, UL receiver circuitry is coupled to UL antenna 232 for receiving transmissions on radio transmission link 250. In some implementations, there is tight time synchronization with minimal protection time between changes in duplex direction.

[0026] UE transceiver 230 and BS transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 that are appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and BS transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G and 6G standards. However, it should be understood that the application of this disclosure is not necessarily limited to specific standards and related protocols. Rather, UE transceiver 230 and BS transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0027] According to various implementations, BS202 can be, for example, an evolved node B (eNB), gNB, serving eNB, target eNB, femtocell, transmit and receive point (TRP), picocell, or another UE. In some implementations, UE 204 can be various types of user equipment such as a mobile phone, smartphone, personal digital assistant (PDA), tablet computer, laptop computer, wearable computing device, terminal, etc. Processor modules 214 and 236 can be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this way, the processor can be implemented as a microprocessor, controller, microcontroller, state machine, etc. The processor can also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, a combination of one or more microprocessors with a digital signal processor core, or any other such configuration.

[0028] Furthermore, the methods described in conjunction with the embodiments disclosed herein can be implemented directly in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any practical combination thereof. Memory modules 216 and 234 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 210 and 230 respectively. Memory modules 216 and 234 may each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0029] Network communication module 218 typically represents the hardware, software, firmware, processing logic, and / or other components of BS 202 that enable bidirectional communication between BS transceiver 210 and other network components and communication nodes configured to communicate with BS 202. For example, network communication module 218 may be configured to support Internet or WiMAX services. In a typical, non-limiting deployment, network communication module 218 provides an 802.3 Ethernet interface, allowing BS transceiver 210 to communicate with traditional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and variations thereof, used herein for a specific operation or function, refer to devices, components, circuits, structures, machines, signals, etc., which are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0030] Figure 3This is a diagram illustrating an example wireless communication method 300 according to various arrangements. The frame structure shown with respect to wireless communication method 300 includes time slots 302, 304, 306, and 308 corresponding to different times. For example, time slot 302 may be referred to as time slot n, time slot 304 may be referred to as time slot n+1, time slot 306 may be referred to as time slot n+2, time slot 308 may be referred to as time slot n+k, and so on. Wireless communication method 300 may include various transmissions using various resources (e.g., time, frequency, space, code, etc.) of time slots 302, 304, 306, and 308 as transmission resources. For example, a network (e.g., BS102) may use time slot 302 to transmit DL DCI 310 (e.g., first DL DCI) and PDSCH 312 (e.g., first PDSCH) scheduled by DL DCI 310 to UE 104. Feedback information for PDSCH 312 is indicated by DL DCI 310 for transmission in the Physical Uplink Control Channel (PUCCH) 320 within time slot 308. The network can use time slot 304 to send UL DCI 314 to UE 104. The network can use time slot 306 to send DL DCI 316 (e.g., a second DL DCI) and PDSCH 318 (e.g., a second PDSCH) scheduled by DL DCI 316 to UE 104. UE 104 can use time slot 308 to send PUSCH 322 scheduled by UL DCI 314 to the network. Since PUCCH 320 is located in the same time slot as PUSCH 322, the feedback information initially carried on PUCCH 320 will be transmitted in PUSCH 322.

[0031] In some cases, the wireless communication method 300 can support UE-based HARQ feedback on a transport block (TB) basis. In some implementations using Time Domain Duplex (TDD) mode, a many-to-one mapping may exist between DL transmissions (or DL ​​time slots) and UL feedback resources (or UL time slots). For example, multiple DL time slots may correspond to one UL feedback time slot for the UE. Feedback for multiple DL transmissions can be aggregated into a HARQ feedback codebook and transmitted to the network (e.g., BS102) in UL transmission resources (e.g., within PUCCH or PUSCH). The feedback codebook may include the size of the number of bits in the codebook.

[0032] In certain situations, wireless communication 300 can support various conditions. For example, to provide feedback information in the PUSCH, HARQ feedback codebooks and UL data can be scheduled within the same UL time slot. Both the HARQ feedback codebook and UL data can be transmitted by UE 104 to BS102 in UL data resources (e.g., PUSCH). UL data resources can be punctured by HARQ feedback codebook resources, or UL data resources can be transmitted by rate matching with resources of the HARQ feedback codebook. In some examples, a DL time slot refers to a time slot with DL allocation (e.g., for DL ​​data transmission in the PDSCH). A UL time slot refers to a time slot with UL data transmission in the PUSCH, UL HARQ feedback in the PUCCH, or UL HARQ feedback in the PUSCH. The disclosure herein may refer to the HARQ feedback codebook as a feedback codebook or a HARQ-ACK feedback codebook, and HARQ feedback as feedback or HARQ-ACK feedback. In some cases, the feedback codebook may be one of two types of feedback codebooks, namely a type 1 codebook or a type 2 codebook.

[0033] The feedback codebook size of the Type 1 codebook can be configured based on the feedback timing (K1) value setting, the number of codewords per slot, and the time-domain resource allocation list, depending on the number of DL transmission slots corresponding to the UL feedback slot. In carrier aggregation (CA) use cases, the feedback codebook size of the Type 1 codebook can be related to the number of component carriers (CCs). BS102 and UE 104 can have a unified (e.g., mutual) understanding of the size and bit order of the Type 1 codebook feedback codebook (e.g., to avoid erroneous retransmissions). The bit order of the Type 1 feedback codebook can refer to the relationship between each bit in the codebook and the associated DL slot. The Type 1 codebook can include feedback information for all DL slots corresponding to the UL feedback slot transmitted by UE 104 with the Type 1 codebook. In some examples, a portion of a DL slot may not include DL data transmission. Due to the lack of DL data transmission, the feedback bits of the feedback codebook associated with that portion of the DL slot may provide junk information (e.g., useless information, information irrelevant to feedback, etc.).

[0034] For example, a Type 2 codebook may include a DAI mechanism for determining the codebook size and bit order. In the first example, feedback information may be carried on the PUCCH. For example, DAI indication fields (e.g., counter DAI and total DAI) may be included in the DCI used for scheduling DL transmissions. The counter DAI may indicate the bit order of the feedback information in the codebook. For example, the value of the counter DAI in the DLDCI may indicate the position of the feedback information for DL ​​transmissions scheduled by the DL DCI in the Type 2 codebook. The value of the total DAI in the last DL scheduling DCI may indicate the size of the feedback codebook. For example, the value of the total DAI may indicate the number of DL transmissions up to the current transmission (e.g., each transmission to be fed back in a Type 2 codebook). The value of the total DAI in the last DLDCI may indicate the size of the Type 2 feedback codebook.

[0035] In the second example, feedback information can be carried on the PUSCH. For example, a UL DAI field can be introduced into the ULDCI used for PUSCH scheduling. In some cases, the value of UL DAI can replace the value of the total DAI in the last DL DCI to determine the size of the Type 2 codebook. Due to this replacement, after the UL DCI, other DL DCIs may not schedule additional DL transmissions that feed back on the PUSCH scheduled by the ULDCI, which can lead to the avoidance of sending garbage feedback bits in the feedback codebook (e.g., because it can indicate the DL slot associated with the feedback codebook).

[0036] When a DAI field is added to the DL and / or UL DCI, the DAI may increase the overhead of the DCI. For example, PUSCH 322 in time slot 308 (e.g., time slot n+k) may be scheduled by UL DCI 314 in time slot 304 (e.g., time slot n+1). Because PUCCH 320 and PUSCH 322 overlap (e.g., overlap in time), PDSCH 312 in time slot 302 (e.g., time slot n), which is scheduled by DL DCI 310 in time slot 302 and starts earlier than UL DCI 314 (e.g., in time), can be instructed to be fed back on PUCCH 320 in time slot 308. Due to this instruction, the feedback information initially carried on PUCCH 320 can be included in PUSCH 322 (e.g., carried on PUSCH 322, associated with PUSCH 322, or related to PUCCH 322). In some cases, it may not be necessary to feed back PDSCH 318, which is scheduled by DL DCI 316 and starts later than or no earlier than ULDCI 314, in time slot 308. That is, time slot 308 may not include feedback information for PDSCH 318.

[0037] Some wireless communication systems can indicate UL HARQ feedback timing values. For example, in NR, a base station (BS) can indicate UL HARQ feedback timing values ​​(e.g., feedback slots for transmitting the feedback codebook) to the UE via semi-static Radio Resource Control (RRC) signaling, via dynamic DCI (e.g., via the relationship between a specific time slot and a feedback time slot used to transmit the feedback codebook), or both. Having both options allows for greater flexibility and complexity in feedback timing and associated feedback codebook size compared to other communication standards. For example, NR can include more DL allocations (e.g., DL slots) between UL grant and feedback slots carrying the feedback codebook than other communication standards. The arrangements described herein can support feedback for DL ​​allocations before and after the UL grant time slots, rather than only supporting feedback for DL ​​allocations before the UL grant time slots.

[0038] Figure 4This is a diagram illustrating an example wireless communication method 400 for transmitting feedback information according to various arrangements. The frame structure in the wireless communication method 400 may include time slots 402, 404, 406, 408, 410, 412, 414, 416, 418, and 420. For example, time slot 402 may be time slot n, time slot 404 may be time slot n+1, time slot 406 may be time slot n+2, time slot 408 may be time slot n+3, time slot 410 may be time slot n+4, time slot 412 may be time slot n+5, time slot 414 may be time slot n+6, time slot 416 may be time slot n+7, time slot 418 may be time slot n+8, and time slot 420 may be time slot n+9. The frame structure may be a TDD frame structure with DDDSU configurations for time slots 402-420 respectively. Figure 4 As shown, time slots 402-410 include three DL time slots, one dedicated time slot, and one UL time slot, while time slots 412-420 include three DL time slots, one dedicated time slot, and one UL time slot. Time slots 402 to 420 can be associated with different types of transmissions; for example, time slots 402, 402, 406, 412, 414, and 416 can be DL time slots. Time slots 410 and 420 can be UL time slots. Time slots 408 and 418 are dedicated time slots.

[0039] In wireless communication method 400, various resources of time slots (e.g., time, frequency, space, code, etc.) can be used to send and receive various transmissions. For example, a network (e.g., BS102) can use time slots 402 and 404 to send UL DCI 422 (e.g., first UL DCI) and 424 (e.g., second UL DCI) to UE 104. The network can use time slots 406 and 410 to send DL DCI 426 (e.g., first DL DCI) and 434 (e.g., second DL DCI) as well as PDSCH 428 (e.g., first PDSCH) and PDSCH 436 (e.g., second PDSCH) to UE 104. UE 104 can use time slots 410 and 420 to send PUCCH 430 (e.g., first PUCCH) and PUCCH 438 (e.g., second PUCCH) and PUSCH 432 (e.g., first PUSCH) and PUSCH 440 (e.g., second PUSCH) to the network.

[0040] Wireless communication method 400 can support HARQ feedback. For example, feedback information for UL DCI 422 can be provided in PUSCH 432 in time slot 410, and feedback information for UL DCI 424 can be provided in PUSCH 440 in time slot 420. DL DCI 426 schedules PDSCH 428, and feedback information for PDSCH 428 cannot be provided in PUCCH 430 or PUCCH 438. DL DCI 434 schedules PDSCH 436, and feedback information for PDSCH 436 cannot be provided in PUCCH 438. Therefore, feedback information received from PDSCHs in time slots 406 to 416 (e.g., HARQ ACK or NACK) cannot be transmitted in UL time slots 410 or 420, resulting in HARQ delay.

[0041] In some examples, PUSCH repetitions can only be transmitted within available UL time slots. PUSCH repetitions may continue to occupy consecutive or directly adjacent UL time slots, thus denying the opportunity to send PUCCHs over extended periods. As the repetition factor increases (e.g., more repetitions), scheduling constraints become unacceptable for the user experience.

[0042] For Type 1 codebooks, in response to determining that the UL DAI for unicast is equal to zero or the UL DAI for multicast is equal to zero, UE 104 does not generate unicast or multicast HARQ-ACK information for multiplexing in PUSCH transmission, unless UE 104 receives the following at the M_c timing for candidate PDSCH reception (in which case UE 104 only generates the corresponding unicast or multicast HARQ-ACK information): 1) only unicast or multicast semi-persistent scheduling (SPS) PDSCH release, 2) only one or more unicast SPS PDSCHs or one or more multicast SPS PDSCHs have enabled associated HARQ-ACK information reporting, 3) only transmission of configuration indicator (TCI) status updates or PDSCHs scheduled by DCI format 1_0 with a counter DAI field value of 1 on the primary cell (PCell), or 4) only PDSCHs scheduled by DCI format 4_1 with associated HARQ-ACK information reporting enabled and a counter DAI field value of 1 on the PCell.

[0043] For Type 2 codebooks, in response to the determination that: 1) no code block group (CBG) configuration is provided to UE 104 (e.g., via PDSCH-CodeBlockGroupTransmission), 2) UE 104 is scheduled for PUSCH transmission using a DCI format including a UL DAI field with a value of 4, 3) UE 104 does not receive any PDCCH within the monitoring time of the DCI format used to schedule PDSCH reception, which provides the transport block with enabled HARQ-ACK information or with associated HARQ-ACK information, and does not schedule PDSCH reception on any serving cell c, and 4) UE 104 does not have HARQ-ACK information to be multiplexed in PUSCH in response to SPS PDSCH reception, UE 104 does not multiplex HARQ-ACK information in PUSCH transmission.

[0044] For Type 2 codebooks, in response to the determination that: 1) CBG configuration is provided to UE 104, 2) UE 104 is scheduled for PUSCH transmission using a DCI format including a UL DAI field with a first value of 4 or a second value of 4, 3) UE 104 does not receive any PDCCH within the monitoring time of the DCI format used to schedule PDSCH reception, which provides the transport block with enabled HARQ-ACK information or with associated HARQ-ACK information, and does not schedule PDSCH reception on any serving cell c, and 4) UE 104 does not have HARQ-ACK information to be multiplexed in PUSCH in response to SPS PDSCH reception, and UE 104 does not multiplex HARQ-ACK information for the first subcodebook or for the second subcodebook respectively in PUSCH transmission.

[0045] In some arrangements, feedback information transmission for DL ​​transmission and allocation after UL DCI includes dividing the codebook into multiple sub-codebooks. In some arrangements, the codebook (e.g., a Type 1 codebook or a Type 2 codebook) may be divided into two sub-codebooks.

[0046] In some examples, the first subcodebook corresponds to a first type of DL transmission that begins before or no later than the UL DCI, or a second type of DL transmission scheduled by the DL DCI that begins before or after the UL DCI. Feedback information for the aforementioned DL transmissions is instructed or configured to be transmitted in the same time slot of the PUSCH scheduled by the UL DCI. The first type of DL transmission can be at least one of SPS PDSCH, SPS PDSCH release, TCI state update, etc. The second type of DL transmission can be PDSCH.

[0047] In some examples, the second subcodebook corresponds to a first type of DL transmission that begins no earlier than or after the UL DCI, or a second type of DL transmission scheduled by the DL DCI that begins no earlier than or after the UL DCI. Feedback information for the aforementioned DL transmissions is instructed or configured to be transmitted in the same time slot as the PUSCH scheduled by the UL DCI. The first type of DL transmission can be at least one of SPS PDSCH, SPS PDSCH release, TCI state update, etc. The second type of DL transmission can be PDSCH.

[0048] Figure 5 This is a flowchart illustrating an example wireless communication method 500 according to various arrangements. Method 500 can be performed by a network (e.g., BS102) and a UE 104. At 510, the network transmits a DL transmission. At 520, the UE 104 receives the DL transmission. At 530, the UE 104 transmits feedback information for the DL transmission in a UL transmission scheduled by a first DCI. This feedback information corresponds to a codebook that includes at least one of a first sub-codebook and a second sub-codebook based on the reception time of the first DCI (e.g., UL DCI). At 540, the network receives the feedback information for the DL transmission in a UL transmission scheduled by the first DCI.

[0049] In some examples, a DL transmission includes at least one of the following: a first DL transmission (e.g., a first type of DL transmission for a first subcodebook) that begins before or no later than a first DCI for uplink transmission; a second DL transmission (e.g., a second type of DL transmission for a first subcodebook) scheduled by a second DCI (e.g., a DL DCI) that begins before or no later than the first DCI; a third DL transmission (e.g., a first type of DL transmission for a second subcodebook) that begins after or no earlier than the first DCI; or a fourth DL transmission (e.g., a second type of DL transmission for a second subcodebook) scheduled by a third DCI that begins after or no earlier than the first DCI. In some examples, the first subcodebook includes at least one of feedback information for the first DL transmission or feedback information for the second DL transmission. In some examples, the second subcodebook includes at least one of feedback information for the third DL transmission or feedback information for the fourth DL transmission.

[0050] In some arrangements, two subcodebooks can be concatenated to form a feedback codebook. The concatenated subcodebooks can be transmitted or multiplexed by UE 104 on the PUSCH. In some arrangements, UE 104 can independently transmit or multiplex two subcodebooks on the PUSCH. For example, the two subcodebooks are encoded independently, and the transmission resources for each subcodebook on the PUSCH are independently determined according to predefined rules. In some examples, in response to insufficient resources on the PUSCH for transmitting both subcodebooks, one subcodebook is discarded according to predefined rules, for example, the second subcodebook is always discarded, or a subcodebook with a relatively small number of bits is discarded.

[0051] Therefore, in some arrangements, a codebook is formed by cascading a first sub-codebook and a second sub-codebook. The cascaded first and second sub-codebooks are transmitted by UE 104 and received by the network. In some arrangements, the first and second sub-codebooks are transmitted independently by UE 104 and received by the network.

[0052] In some arrangements, each subcodebook contains at least one of unicast transmission feedback information and multicast transmission feedback information. A codebook is then generated by concatenating different types of subcodebooks in the following order: the unicast portion of the first subcodebook, the multicast portion of the first subcodebook, the unicast portion of the second subcodebook, and the multicast portion of the second codebook. In some arrangements, the codebook concatenation order may be the unicast portion of the first subcodebook, the unicast portion of the second subcodebook, the multicast portion of the first subcodebook, and the multicast portion of the second codebook.

[0053] Therefore, the first subcodebook includes at least one of feedback information for a first unicast transmission sent from the network to the wireless communication device or feedback information for a first multicast transmission sent from the network to the wireless communication device. The second subcodebook includes at least one of feedback information for a second unicast transmission sent from the network to the wireless communication device or feedback information for a second multicast transmission sent from the network to the wireless communication device.

[0054] In some configurations, UE capabilities are defined. UE capabilities indicate whether UE 104 supports providing feedback HARQ-ACK information on DL transmissions scheduled by UL authorization for transmissions no earlier than or after UL authorization. Therefore, in some configurations, UE 104 sends an indication to the network, and the network receives an indication from UE 104, indicating that UE 104 supports providing feedback information on DL transmissions scheduled by uplink DCI for transmissions in DCI formats no earlier than or after the uplink DCI. In other configurations, UE 104 sends an indication to the network, and the network receives an indication from UE 104, indicating that UE 104 supports providing feedback information on DL transmissions scheduled by uplink DCI for transmissions no earlier than or after the start of the uplink DCI.

[0055] In some arrangements, if UE 104 reports the UE capability, UE 104 may divide the codebook into two sub-codebooks as described herein. If UE 104 does not report the UE capability, the codebook carried on the PUSCH (e.g., the feedback information contained therein) contains feedback information only for DL ​​transmissions that begin no later than or earlier than the UL grant, or the codebook carried on the PUSCH contains feedback information only for DL ​​transmissions scheduled in the DCI format that begin no later than or earlier than the UL grant.

[0056] In some arrangements, BS102 may send RRC signaling to UE104 to indicate whether BS102 can begin transmitting DL transmissions no earlier than or after UL authorization, and / or to indicate or configure UE104 to 1) provide feedback in a PUSCH scheduled by UL authorization, 2) indicate whether BS102 can begin transmitting DL transmissions scheduled by DL DCI no earlier than or after UL authorization; and / or 3) indicate or configure UE104 to provide feedback in a PUSHH scheduled by UL authorization. In some arrangements, if feedback for DL ​​transmissions is indicated or configured to be provided in a PUSCH scheduled by UL authorization, BS102 may send RRC signaling to UE104 to indicate whether UE104 can provide feedback information for DL ​​transmissions after UL authorization. In response to receiving RRC signaling, UE 104 generates a codebook by including a first sub-codebook and a second sub-codebook, for example by including feedback information for both DL transmissions before or no later than the UL DCI and DL transmissions no earlier than or after the UL DCI.

[0057] In some arrangements, the sizes of the first and second sub-codebooks are determined based on the value of UL DAI in the UL DCI. For example, assuming the value of UL DAI is 2, the sizes of the first and second sub-codebooks can be 4*a+2 and 4*b+2, respectively, where a and b are non-zero integers. In some examples, a equals b. In some examples, a is different from b.

[0058] In other words, a separate subcodebook is defined for feedback corresponding to DL transmissions following UL DCI, and feedback can be provided in the PUSCH scheduled by UL DCI. UL DCI removes the restriction on downlink scheduling, thereby improving system transmission efficiency.

[0059] In some arrangements, the transmission of feedback information for DL ​​transmissions or allocations following the UL DCI includes the generation of a Type 1 codebook. In some arrangements, as described herein, the Type 1 codebook to be transmitted in a PUSCH scheduled by the UL DCI can be divided into two sub-codebooks, corresponding respectively to feedback information for DL ​​transmissions that begin before or no later than the UL DCI, and to feedback information for DL ​​transmissions that begin no earlier than or after the UL DCI.

[0060] In some arrangements, the size of the first subcodebook is determined based on the value of UL DAI in the UL DCI. In some examples, in response to determining that the UL DAI for unicast is equal to zero or the UL DAI for multicast is equal to zero, UE 104 does not generate a first subcodebook for multiplexing in PUSCH transmission unless UE 104 receives 1) a unicast or multicast SPS PDSCH release only, 2) one or more unicast SPS PDSCHs or one or more multicast SPS PDSCHs have enabled associated HARQ-ACK information reporting, 3) a PDSCH only updated by TCI or scheduled by DCI format 1_0 with a counter DAI field value of 1 on the PCell, or 4) a PDSCH only scheduled by DCI format 4_1 with associated HARQ-ACK information reporting enabled and a counter DAI field value of 1 on the PCell. In this case, UE 104 only generates the corresponding unicast or multicast HARQ-ACK information.

[0061] In some arrangements, the size of the codebook (including both the first and second sub-codebooks) is determined based on the value of ULDAI in the UL DCI. In some examples, in response to determining that the unicast UL DAI is equal to zero or the multicast UL DAI is equal to zero, UE 104 does not generate a codebook for multiplexing in PUSCH transmission unless UE 104 receives 1) a unicast or multicast SPS PDSCH release only, 2) one or more unicast SPS PDSCHs or one or more multicast SPS PDSCHs have enabled associated HARQ-ACK information reporting, 3) a PDSCH with only TCI state updates or scheduled by DCI format 1_0 with a counter DAI field value of 1 on the PCell, or 4) a PDSCH scheduled by DCI format 4_1 with associated HARQ-ACK information reporting enabled and a counter DAI field value of 1 on the PCell. In this case, UE 104 only generates the corresponding unicast or multicast HARQ-ACK information.

[0062] In some arrangements, the codebook size (including both the first and second sub-codebooks) or the size of the first codebook is determined based on the value of UL DAI in the UL DCI. More specifically, in response to determining that the unicast UL DAI is equal to zero or the multicast UL DAI is equal to zero, UE 104 does not generate a codebook or first sub-codebook for multiplexing in PUSCH transmissions unless the UL scheduling timing indicated in the UL DCI (e.g., the slot offset between the UL DCI and PUSCH) is greater than at least one value in the set of DL scheduling timing values ​​(e.g., the slot offset between the DL DCI and PDSCH).

[0063] In some arrangements, the size of at least one of the first sub-codebook or the second sub-codebook is determined based on the uplink DAI value in the first DCI. In some arrangements, in response to determining that the uplink scheduling timing indicated in the first DCI is greater than at least one value in the set of values ​​for the DL scheduling timing, UE 104 generates a first sub-codebook to be multiplexed in uplink transmission.

[0064] Figure 6 This is a diagram illustrating an example wireless communication method 600 for transmitting feedback information according to various arrangements. The frame structure in the wireless communication method 600 may include time slots 602, 604, 606, 608, 610, 612, and other time slots. PDCCHs 614, 618, 620, and 622 are repeated. Figure 6As shown, assume that the UL scheduling timing k2 is indicated as m (e.g., 3) by the UL DCI. If the UL DCI transmits in slot n (e.g., slot 608, PDCCH 622), then PUSCH 628 scheduled by the UL DCI is transmitted in slot n+m (e.g., slot 612). Then, if at least one value of the DL scheduling timing value set (k1 set) is less than m, then regardless of the value of UL DAI in the UL DCI, UE 104 generates a codebook or first sub-codebook for multiplexing in the PUSCH transmission. In the example where the k1 set is {2, 3, 4, 5}, there is a potential DL transmission in slot 610 (e.g., PDSCH 626 scheduled by PDCCH 624). Feedback for PDSCH 626 is indicated in slot 612 (e.g., setting k1 = 2). A second sub-codebook is then generated to provide this feedback. On the other hand, in response to the determination that there is no value less than m in the set of DL scheduling timing values ​​(k1 set), if the value of UL DAI in UL DCI is zero, then UE 104 does not generate a codebook or first sub-codebook for multiplexing in PUSCH transmission. In the example where the k1 set is {4, 5, 6, 7}, there is no additional DL transmission between PDCCH4 and PUSCH, which means that there is no need to generate a second sub-codebook.

[0065] In other words, feedback corresponding to the DL transmission following UL DCI can be provided in the PUSCH scheduled by UL DCI. After UL DCI removes the restriction on downlink scheduling, the system transmission efficiency is improved accordingly.

[0066] In some arrangements, the transmission of feedback information for DL ​​transmissions or allocations following the UL DCI includes the generation of a Type 2 codebook. In some arrangements, as described herein, the Type 2 codebook to be transmitted in a PUSCH scheduled by the UL DCI can be divided into two sub-codebooks, corresponding respectively to feedback information for DL ​​transmissions that begin before or no later than the UL DCI, and to feedback information for DL ​​transmissions that begin no earlier than or after the UL DCI.

[0067] In some arrangements, the size of the first subcodebook can be determined based on the value of the UL DAI in the UL DCI. For example, if UE 104 is not provided with CBG configuration, and UE 104 is scheduled for PUSCH transmission in a DCI format that includes a UL DAI field with a value of 4, and UE 104 does not receive a DL transmission that it is instructed or configured to provide feedback in the PUSCH (before or no later than receiving the UL DCI), then UE 104 does not generate a first subcodebook for multiplexing in the PUSCH transmission. This DL transmission can be at least one of the following: 1) any PDCCH in a monitoring timing of a DCI format used to schedule PDSCH reception that provides enabled feedback information to the transport block or has associated feedback information, without scheduling PDSCH reception; or 2) an SPS PDSCH. In some arrangements, the first DCI schedules uplink transmissions, and the first DCI includes a DAI with a first value (e.g., 4). UE 104 does not receive a DL transmission before or after receiving the first DCI. Feedback for this DL transmission is configured to be transmitted within the same time interval (e.g., the same time slot) as the uplink transmission. The UE does not multiplex the first subcodebook in the uplink transmission.

[0068] In some arrangements, the size of the codebook (including both the first and second sub-codebooks) is determined based on the value of ULDAI in the UL DCI. For example, if UE 104 is not provided with CBG configuration, and UE 104 is scheduled for PUSCH transmission using a UL DCI that includes a UL DAI field with a value of 4, and UE 104 does not receive a DL transmission that it is instructed or configured to provide feedback in the PUSCH (before or after receiving the UL DCI), then UE 104 does not generate a codebook for multiplexing in the PUSCH transmission. This DL transmission can be at least one of the following: 1) any PDCCH in a monitoring timing of a DCI format used to schedule PDSCH reception that provides enabled feedback information to the transport block or has associated feedback information, without scheduling PDSCH reception; or 2) an SPS PDSCH. In some arrangements, a first DCI schedules uplink transmissions, and the first DCI includes a DAI with a first value (e.g., 4). UE 104 did not receive a DL transmission before or after receiving the first DCI. Feedback for this DL transmission is configured to be transmitted within the same time interval (e.g., the same time slot) as the uplink transmission. The UE does not multiplex the codebook in the uplink transmission.

[0069] In some arrangements, the size of the codebook (including both the first and second sub-codebooks) is determined based on the value of ULDAI in the UL DCI. For example, if UE 104 is not provided with CBG configuration, and UE 104 is scheduled for PUSCH transmission by a UL DCI including a UL DAI field with a value of 4, and UE 104 does not receive any DL transmissions that it is instructed or configured to provide feedback in the PUSCH (including both before (no later than) the UL DCI) and after (no earlier than) the UL DCI), then UE 104 does not generate a codebook for multiplexing in the PUSCH transmission. This DL transmission can be at least one of the following: 1) any PDCCH within the monitoring time of a DCI format used to schedule PDSCH reception, which provides enabled feedback information to the transport block or has associated feedback information, without scheduling PDSCH reception; or 2) an SPS PDSCH.

[0070] In some arrangements, if UE 104 is scheduled for PUSCH transmission by a UL DCI including a UL DAI field with a value other than 4, or if UE 104 has received at least one DL transmission that is indicated or configured to be fed back in the PUSCH (including both before (or no later than) the UL DCI) and after (no earlier than) the UL DCI), UE 104 generates a codebook for multiplexing in the PUSCH transmission. In some arrangements, a first DCI schedules an uplink transmission, which includes a DAI with a second value (e.g., a value other than 4), or the UE receives a DL transmission before (or no later than) receiving the first DCI or after (or no earlier than) receiving the first DCI, configuring feedback for the DL transmission in the uplink transmission. The wireless communication device does not generate a codebook for multiplexing in the uplink transmission.

[0071] In some arrangements, if UE 104 is scheduled for PUSCH transmission by a UL DCI including a UL DAI field with a value of 4, and UE 104 does not receive a DL transmission that is indicated or configured to be fed back in the PUSCH before or no later than receiving the UL DCI, then UE 104 does not generate a codebook (including both the first and second sub-codebooks) for multiplexing in the PUSCH transmission. In some arrangements, a first DCI schedules uplink transmissions, and the first DCI includes a DAI with a first value (e.g., 4). UE 104 does not receive a DL transmission that is configured to be fed back in the same time interval of the uplink transmission before or after receiving the first DCI. The UE does not multiplex the codebook (including both the first and second sub-codebooks) in the uplink transmission.

[0072] In some arrangements, the first subcodebook is generated based on the value of UL DAI in UL DCI, and the second subcodebook is generated based on the rules used to generate the type 1 codebook.

[0073] In some arrangements, if UE 104 is scheduled for a PUSCH transmission by a UL DCI that includes a UL DAI field with a value other than 4, or if UE 104 has received a DL transmission that is indicated or configured to be fed back in the PUSCH before or after receiving the UL DCI, UE 104 generates a first sub-codebook based on the value of the UL DAI in the UL DCI. A second sub-codebook is generated according to rules used for generating a Type 1 codebook. In some arrangements, the first DCI schedules an uplink transmission, the first DCI including a DAI with a second value (e.g., other than 4), or UE 104 receives at least one DL transmission before or after receiving the first DCI. Feedback for the DL transmission is configured to be transmitted in the same time interval as the uplink transmission. UE 104 generates a codebook, including generating a first sub-codebook based on the value of the uplink DAI in the first DCI, and generating a second sub-codebook according to rules for a Type 1 codebook.

[0074] In some arrangements, if UE 104 is scheduled for PUSCH transmissions by a UL DCI that includes a UL DAI field with a value other than 4, or if UE 104 receives a DL transmission that is indicated or configured to be fed back in the PUSCH only before or no later than receiving the UL DCI, then UE 104 generates a first subcodebook based solely on the value of the UL DAI in the UL DCI. No second subcodebook is generated. In some arrangements, the first DCI schedules uplink transmissions, the first DCI includes a DAI with a second value (e.g., other than 4), or the UE receives a DL transmission before or after receiving the first DCI. Feedback for the DL transmission is configured to be transmitted in the same time interval as the uplink transmission. UE 104 generates the first subcodebook based solely on the value of the uplink DAI in the first DCI.

[0075] In some arrangements, if UE 104 is scheduled for a PUSCH transmission by a UL DCI including a UL DAI field with a value not equal to 4, or if UE 104 receives a DL transmission that is indicated or configured to provide feedback in the PUSCH only before or no later than receiving the UL DCI, UE 104 generates both a first subcodebook and a second subcodebook. In some arrangements, UE 104 receives at least one DL transmission only before or after receiving the first DCI. Feedback for this at least one DL transmission is configured to be transmitted within the same time interval (e.g., a timeslot) as the uplink transmission. UE 104 generates both a first subcodebook and a second subcodebook.

[0076] In some arrangements, if UE 104 receives a DL transmission that is instructed or configured to provide feedback in the PUSCH only after receiving the UL DCI, then UE 104 generates only a second sub-codebook. For example, the second sub-codebook is generated according to rules used for generating a Type 1 codebook. In some arrangements, UE 104 receives at least one DL transmission only after receiving the first DCI, or no earlier than receiving the first DCI. Feedback for this at least one DL transmission is configured to be transmitted in the same time interval as the uplink transmission. UE 104 generates a second sub-codebook instead of a first codebook.

[0077] In some arrangements, whether a second subcodebook is generated depends on whether UE 104 receives the DL transmission, which is instructed or configured to provide feedback in the PUSCH, after or no earlier than receiving the UL DCI. In some arrangements, UE 104 generates the second subcodebook based on whether UE 104 receives the DL transmission after or no earlier than receiving the first DCI. Feedback for this DL transmission is configured to be transmitted within the same time interval as the uplink transmission.

[0078] In some arrangements, if UE 104 is scheduled for PUSCH transmission using a UL DCI that includes a UL DAI field with a value of 4, and UE 104 receives the DL transmission that it is instructed or configured to provide feedback in the PUSCH only after receiving the UL DCI or no earlier than receiving the UL DCI, then UE 104 generates only a second sub-codebook. For example, the second sub-codebook is generated according to the rules used to generate a Type 1 codebook.

[0079] In some arrangements, if a CBG configuration is provided to UE 104, UE 104 generates a TB subcodebook and a CBG subcodebook based on a first value of the UL DAI for TB and a second value of the UL DAI for CBG, respectively. The TB subcodebook and CBG subcodebook can be generated independently using the methods described herein. More specifically, the TB subcodebook includes at least one of a first TB subcodebook and a second TB subcodebook. And the CBG subcodebook includes at least one of a first CBG subcodebook and a second CBG subcodebook.

[0080] In other words, feedback corresponding to the DL transmission following UL DCI can be provided in the PUSCH scheduled by UL DCI. After UL DCI removes the restriction on downlink scheduling, the system transmission efficiency is improved accordingly.

[0081] In some arrangements, feedback information transmission for DL ​​transmission and allocation after the UL DCI includes a codebook as shown in the example where repeating PUSCH transmissions are scheduled by UL authorization. In some arrangements, the codebook to be transmitted in a PUSCH scheduled by the ULDCI (e.g., a Type 1 codebook or a Type 2 codebook) can be divided into two sub-codebooks, corresponding to feedback information for DL ​​transmissions that begin before (or no later than) the UL DCI and feedback information for DL ​​transmissions that begin after (no earlier than) the UL DCI, respectively.

[0082] Figure 7 This is a diagram illustrating an example wireless communication method 700 for transmitting feedback information according to various arrangements. The frame structure in the wireless communication method 700 may include time slots 702, 704, 706, 708, 710, and other time slots shown. The frame structure may be a TDD frame structure with a DDDSU configuration for the time slots shown. In some examples, repeating PUSCH transmissions (e.g., PUSCH 714, 716, 718, and 720) may be scheduled by UL DCI 712. In this example, the repetition factor is 4. The four PUSCH transmissions 714, 716, 718, and 720 are then located within four UL time slots 702, 704, 706, and 708, respectively.

[0083] In some arrangements, the first subcodebook is transmitted only in the initial PUSCH transmission (e.g., the first PUSCH transmission or PUSCH rep#1, denoted as PUSCH 714). The second subcodebook is transmitted in subsequent PUSCH transmissions (i.e., non-initial PUSCH transmissions such as PUSCH 716, 718, or 720). In some arrangements, the network (e.g., BS102) receives the first subcodebook from UE 104 in the first PUSCH transmission (e.g., 714). The network receives the second subcodebook from UE 104 in subsequent PUSCH transmissions (e.g., PUSCH 716, 718, or 720). This subsequent PUSCH transmission is a repetition of the first PUSCH transmission and is later than the first PUSCH transmission.

[0084] In some arrangements, if a DL transmission is indicated or configured to be fed back in a time slot of a PUSCH transmission, the feedback information for that DL transmission is transmitted in the PUSCH transmission. For example, feedback information for a DL transmission indicated or configured to be provided in time slot PUSCH rep#1 (e.g., PUSCH 714) is transmitted in PUSCH rep#1. Feedback information for another DL transmission indicated or configured to be provided in time slot PUSCH rep#2 (e.g., PUSCH 716) is transmitted in PUSCH rep#2, and so on. In some arrangements, the network indicates or configures feedback for a DL transmission in a DL transmission to UE 104 corresponding to a time interval (e.g., time slot) of the PUSCH transmission. The network receives feedback for the DL transmission from UE 104 in the PUSCH transmission.

[0085] In some arrangements, the size of the codebook or sub-codebook transmitted in each repetition of the PUSCH transmission is determined based on the value of UL DAI in the UL DCI that schedules the PUSCH repetition. In an example where the UL DAI value is 2, the size of the codebook or sub-codebook transmitted in the first PUSCH repetition could be 4*n+2. The size of the codebook or sub-codebook transmitted in the second PUSCH repetition could be 4*m+2, and so on. The parameters n and m are non-zero integers. In some examples, n equals m. In some examples, n is different from m.

[0086] In some arrangements, the first subcodebook is transmitted only in the initial PUSCH transmission (e.g., the first PUSCH transmission or PUSCHrep#1, denoted as PUSCH 714). The second subcodebook is transmitted in the last PUSCH transmission (e.g., PUSCH rep#4 or PUSCH 720). The second subcodebook contains feedback information indicating or configured to provide DL transmissions in any slot of each PUSCH repeat. These DL transmissions are neither earlier nor later than the start of the UL authorization used to schedule the PUSCH repeat. In some arrangements, the network receives the first subcodebook from UE 104 in the first PUSCH transmission (e.g., PUSCH 714), which is the first transmission of the PUSCH repeat. The network receives the second subcodebook from UE 104 in the second PUSCH transmission (e.g., PUSCH 720), which is the last transmission of the PUSCH repeat.

[0087] In some arrangements, the size of the codebook or sub-codebook transmitted in the first and last PUSCH transmissions is determined based on the value of UL DAI in the UL DCI that schedules the PUSCH repetitions. In an example where the UL DAI value is 2, the size of the codebook or sub-codebook transmitted in the first PUSCH repetition could be 4*x+2. The size of the codebook or sub-codebook transmitted in the last PUSCH repetition could be 4*y+2, and so on. Parameters x and y are non-zero integers. In some examples, x equals y. In some examples, x is different from y.

[0088] In some arrangements, feedback information for DL ​​transmissions, which is instructed or configured to be fed back in the time slot of the initial PUSCH transmission (e.g., the first PUSCH transmission or PUSCHrep#1, denoted as PUSCH 714), is transmitted in PUSCH rep#1. In some arrangements, the network indicates to UE 104 that the feedback for the DL transmission in the DL transmission corresponds to the time interval of the first PUSCH transmission (e.g., PUSCH 714). The network receives the feedback for the DL transmission from UE 104 during the first PUSCH transmission.

[0089] Feedback information for a DL transmission provided in any slot of a non-initial PUSCH transmission (e.g., PUSCH rep#2(716), PUSCH rep#3(718), or PUSCH rep#4(720)) is transmitted in the final PUSCH transmission (e.g., PUSCH rep#4(720)). In some arrangements, the network indicates to UE 104 that the feedback for the DL transmission in the DL transmission corresponds to a time interval (e.g., a slot) of subsequent PUSCH transmissions (e.g., PUSCH 716, 718, 720). Subsequent PUSCH transmissions are PUSCH transmissions other than the first transmission of a PUSCH repetition. The network receives feedback for the DL transmission from UE 104 in the final PUSCH transmission (e.g., PUSCH 714). This final PUSCH transmission is the last transmission of a PUSCH repetition.

[0090] In other words, feedback corresponding to the DL transmission following UL DCI can be provided in the PUSCH scheduled by UL DCI. After UL DCI removes the restriction on downlink scheduling, the system transmission efficiency is improved accordingly.

[0091] In some examples, in a TB (TBoMS) schedule across multiple time slots, a PUSCH transmission or TB can occupy two or more time slots. For example... Figure 7 As shown, PUSCH or TB is scheduled to be transmitted in four UL time slots 702, 704, 706 and 708 respectively. PUSCH 714 can be PUSCH part 1, PUSCH 716 can be PUSCH part 2, PUSCH 718 can be PUSCH part 3, and PUSCH 720 can be PUSCH part 4.

[0092] In some arrangements, the first subcodebook is transmitted only in PUSCH section 1 (e.g., PUSCH 714). The second subcodebook is transmitted in one or more subsequent PUSCH sections 2, 3, and 4.

[0093] In some arrangements where feedback information for a DL transmission is indicated or configured to be provided in a time slot of a specific PUSCH section, the feedback information for the DL transmission can be transmitted within that PUSCH section. In an example where feedback information for a DL transmission is indicated or configured to be provided in a time slot of PUSCH section 1, the feedback information will be transmitted in PUSCH section 1. Feedback information for another DL transmission indicated or configured to be provided in a time slot of PUSCH section 2 will be transmitted in PUSCH section 2, and so on (e.g., PUSCH 716).

[0094] In some arrangements, the first subcodebook is transmitted only in PUSCH section 1. The second subcodebook is transmitted in the final PUSCH section, PUSCH section 4 (e.g., PUSCH 720). The second subcodebook contains feedback information that is indicated or configured to be provided in any time slot of the PUSCH section other than PUSCH section 1. This DL transmission is no earlier or later than the start of the UL authorization (e.g., UL DCI 712) used to schedule PUSCH 714, 716, 718, and 720.

[0095] In some arrangements where feedback information is indicated or configured to provide DL transmission in a time slot of PUSCH section 1, the feedback information is transmitted in PUSCH section 1. Feedback information for DL ​​transmissions that are indicated or configured to be provided in any time slot of a PUSCH section other than PUSCH section 1 (e.g., PUSCH section 2, PUSCH section 3, or PUSCH section 4) is transmitted in the final PUSCH section (e.g., PUSCH section 4).

[0096] In some arrangements, the size of the codebook or sub-codebook transmitted in each PUSCH section is determined based on the value of UL DAI in the UL DCI of the scheduled PUSCH. For example, assuming the value of UL DAI is 2, the size of the codebook or sub-codebook transmitted in PUSCH section 1 could be 4*p+2; the size of the codebook or sub-codebook transmitted in PUSCH section 2 could be 4*q+2, and so on. Here, p and q are non-zero integers. In some examples, p equals q. In some examples, p is different from q.

[0097] In some arrangements, feedback information transmission includes generating a Type 2 codebook for DL ​​transmission or allocation after the UL DCI. In some arrangements, the size of the Type 2 codebook is determined based on at least one of the UL DAI in the UL DCI and the total DAI in the final DL DCI. In some arrangements, the codebook includes a Type 2 codebook. The size of the codebook is determined based on at least one of the uplink DAI in the first DCI or the DAI in the final DL DCI, which will be fed back within the same time interval of the uplink transmission scheduled by the first DCI.

[0098] In some arrangements, if the UL DCI begins before or is no later than the last DL DCI, the size of the Type 2 codebook is determined based on the total DAI in the last DL DCI. If the UL DCI does not begin before the last DL DCI or begins after the last DL DCI, the size of the Type 2 codebook is determined based on the UL DAI in the UL DCI. In some examples, at least one of the counted DAI in a DL DCI that does not begin before or after the UL DCI, and the total DAI, is counted starting from the value of the UL DAI in the UL DCI.

[0099] In some arrangements, the first DCI begins before or no later than the last DL DCI, and the codebook size is determined based on the DAI in the last DL DCI. In some arrangements, the first DCI begins after or no earlier than the last DL DCI, and the codebook size is determined based on the uplink DAI in the first DCI. In some arrangements, the last DCI begins after or no earlier than the first DCI, and the DAI in the DL DCI begins after or no earlier than the first start, counting from the value of the uplink DAI in the first DCI.

[0100] Figure 8 This is a diagram illustrating an example wireless communication method 800 for transmitting feedback information according to various arrangements. The frame structure in the wireless communication method 800 may include time slots 802, 804, 806, 808, and 810. For example, time slot 802 may be time slot n, time slot 804 may be time slot n+1, time slot 806 may be time slot n+2, time slot 808 may be time slot n+3, and time slot 810 may be time slot n+4. This frame structure may be a TDD frame structure having DDDSU configurations for time slots 402-410 respectively. Figure 8 As shown, time slots 802-810 include three DL time slots, one dedicated time slot, and one UL time slot. Time slots 802 to 810 can be associated with different types of transmissions; for example, time slots 802, 802, and 806 are DL time slots. Time slot 810 is a UL time slot. Time slot 818 is a dedicated time slot.

[0101] In wireless communication method 800, various resources of time slots (e.g., time, frequency, space, code, etc.) can be used to send and receive various transmissions. For example, a network (e.g., BS102) can use time slot 802 to send ULDCI 810 to UE 104. The network can use time slots 804 and 806 to send DL DCI 812 (e.g., first DL DCI) and DL DCI 816 (e.g., second DL DCI) as well as PDSCH 814 (e.g., first PDSCH) and PDSCH 818 (e.g., second PDSCH) to UE 104. UE 104 can use time slot 810 to send PUCCH 820 and PUSCH 822 to the network.

[0102] The wireless communication method 800 can support HARQ feedback. For example, feedback information for UL DCI 810 can be provided in PUSCH 822 within time slot 810. DL DCI 812 schedules PDSCH 814 and provides feedback information for PDSCH 814 in PUCCH 820. DL DCI 816 schedules PDSCH 818 and provides feedback information for PDSCH 818 in PUCCH 820.

[0103] As Figure 8 In the example shown, there are two DL DCIs, 812 and 816, which do not begin earlier than UL DCI 820 or after UL DCI 810. Feedback for PDSCH 814 and PDSCH 818, scheduled by DL DCI 812 and DL DCI 816 respectively, is instructed to be provided in slot 810 of PUSCH 822, scheduled by UL DCI 810. UE 104 generates a codebook based on the total DAI value in the last DL DCI (e.g., DL DCI 916) (e.g., total DAI2 = 4). The codebook size can be determined as 4*p+4. Since DAI is cyclically counted in units of 4, a total DAI of 4 indicates that the number of bits requiring feedback is 4*p+4, and the value of p is determined by the number of DL transmissions received by UE 104.

[0104] In some arrangements, the Type 2 codebook to be transmitted in the PUSCH scheduled by the UL DCI can be divided into two sub-codebooks, corresponding respectively to feedback information for DL ​​transmissions that begin before or no later than the UL DCI and for feedback information for DL ​​transmissions that begin no earlier than or after the UL DCI. The size of the first sub-codebook is determined based on the UL DAI in the UL DCI. The size of the second sub-codebook is determined based on the total DAI in the last DL DCI. In some examples, at least one of the counted DAI in the DL DCI corresponding to the second sub-codebook and the total DAI is counted starting from 1. In some arrangements, the size of the first sub-codebook is determined based on the uplink DAI in the first DCI. The size of the second sub-codebook is determined based on the DAI in the last DL DCI used for DL ​​transmissions. The DAI in the DL DCI used for DL ​​transmissions corresponding to the second sub-codebook is counted starting from 1.

[0105] As Figure 8 In the example shown, there are two DL DCIs, 812 and 816, which begin no earlier or later than UL DCI 810 and PDSCH 814 and PDSCH 818, respectively, scheduled by DL DCI 812 and DL DCI 816. Feedback from PDSCH 814 and PDSCH 818, scheduled by DL DCI 812 and DL DCI 816, is instructed to be provided in slot 810 of PUSCH 822, scheduled by UL DCI 810. UE 104 generates a second codebook by including feedback information for these DL transmissions (e.g., PDSCH 814 and PDSCH 818) and transmits it in PUSCH 822. The size of the first sub-codebook is determined to be 4*n+2 based on the value of UL DAI in UL DCI 810 (e.g., 2). Based on the total DAI value in the final DL DCI 816 (e.g., total DAI2), the size of the second subcodebook is determined to be 4*m+2. Since DAI is cyclically counted in units of 4, a UL DAI of 2 indicates that the number of bits requiring feedback is 4*n+2 or 4*m+2, and the value of n or m is determined by the number of DL transmissions received by the UE 104. The codebook size is then determined to be 4*n+2+4*m+2=4*(n+m)+4.

[0106] In some arrangements, the Type 2 codebook to be transmitted in a PUSCH scheduled by the UL DCI can be divided into two sub-codebooks (a first sub-codebook and a second sub-codebook), corresponding respectively to feedback information for DL ​​transmissions that begin before or no later than the UL DCI and for feedback information for DL ​​transmissions that begin no earlier than or after the UL DCI. The size of the first sub-codebook is determined based on the total DAI in the penultimate DL DCI, which is the last DL DCI among those that begin before or no later than the UL DCI. The size of the second sub-codebook is determined based on the total DAI in its penultimate DL DCI, which is no earlier than or after the UL DCI. In some examples, at least one of the counted DAI and the total DAI in the DL DCI corresponding to the second sub-codebook starts from 1.

[0107] Therefore, the arrangement described herein allows for the provision of feedback information for DL ​​transmissions received by the UE within the PUSCH scheduled by the UL DCI, following the UL DCI. System transmission efficiency can be improved after the UL DCI removes the restriction on downlink scheduling.

[0108] While various arrangements of this solution have been described above, it should be understood that they are presented by way of example only, and not by way of limitation. Similarly, various diagrams may depict example architectures or configurations, provided to enable those skilled in the art to understand the exemplary features and functionality of this solution. However, such individuals should understand that the solution is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art should understand, one or more features of some arrangements may be combined with one or more features of another arrangement described herein. Therefore, the breadth and scope of this disclosure should not be limited by any of the illustrative arrangements described above.

[0109] It should also be understood that any reference to elements in this document using names such as "first," "second," etc., does not generally restrict the number or order of these elements. Rather, these names serve as a convenient means of distinguishing two or more elements or instances of elements. Therefore, the reference to "first" and "second" elements does not imply that only two elements can be used, or that the first element must precede the second element in some way.

[0110] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0111] Those skilled in the art will also understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of programs or design code containing instructions (for convenience, these may be referred to herein as "software" or "software module"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been generally described above in accordance with their functions. Whether such a function is implemented as hardware, firmware, software, or a combination of these technologies depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure.

[0112] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but in alternatives, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein.

[0113] If implemented as software, the functionality can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, including any medium capable of transmitting computer programs or code from one place to another. Storage media can be any available medium that is accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer.

[0114] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements used to perform the relevant functions described herein. Furthermore, for the purposes of discussion, various modules are described as discrete modules; however, as will be apparent to those skilled in the art, two or more modules may be combined to form a single module that performs the relevant functions according to the arrangement of this solution.

[0115] Furthermore, memory or other storage devices and communication components may be incorporated into the arrangement of this solution. It should be understood that, for clarity, the above description has referenced different functional units and processors in the arrangement of this solution. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains may be used without departing from this solution. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic unit or controller. Therefore, references to specific functional units are merely references to appropriate methods for providing said functions and not indications of strict logical or physical structures or organization.

[0116] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but should be given the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method, comprising: The network sends downlink transmissions to the wireless communication device; as well as The network receives feedback information from the wireless communication device in an uplink transmission scheduled by a first downlink control information (DCI) for the downlink transmission, wherein the feedback information corresponds to a codebook, the codebook including at least one of a first sub-codebook and a second sub-codebook based on the reception time of the first DCI.

2. The method according to claim 1, wherein The downlink transmission includes at least one of the following: The first downlink transmission begins before or no later than the first DCI corresponding to the uplink transmission; A second downlink transmission scheduled by a second DCI, wherein the second DCI begins before or no later than the first DCI; The third downlink transmission begins after or no earlier than the first DCI; or A fourth downlink transmission scheduled by a third DCI, wherein the third DCI begins after or no earlier than the first DCI; and The first subcodebook includes at least one of the following: Feedback information transmitted in the first downlink; or Feedback information regarding the second downlink transmission; and The second subcodebook includes at least one of the following: Feedback information transmitted in the third downlink; or Feedback information regarding the fourth downlink transmission.

3. The method according to claim 1, wherein The codebook is formed by concatenating the first sub-codebook and the second sub-codebook, and the concatenated first and second sub-codebooks are transmitted by the wireless communication device and received by the network; or The first subcodebook and the second subcodebook are independently transmitted by the wireless communication device and received by the network.

4. The method according to claim 1, wherein The first subcodebook includes at least one of the following: Feedback information regarding the first unicast transmission sent from the network to the wireless communication device; or Feedback information regarding the first multicast transmission sent from the network to the wireless communication device; and The second subcodebook includes at least one of the following: Feedback information regarding the second unicast transmission sent from the network to the wireless communication device; or Feedback information regarding the second multicast transmission sent from the network to the wireless communication device.

5. The method of claim 1, further comprising receiving from the wireless communication device by the network: The wireless communication device supports providing indications on uplink resources scheduled by the uplink DCI for downlink transmissions scheduled by a DCI format that begins no earlier than or after the uplink DCI; or The wireless communication device supports providing indications of feedback information for downlink transmissions no earlier than or after the uplink DCI on uplink resources scheduled by the uplink DCI.

6. The method according to claim 1, wherein, The size of at least one of the first or second subcodebooks is determined based on the value of the uplink-downlink allocation index (DAI) in the first DCI.

7. The method according to claim 1, wherein, In response to determining that the uplink scheduling timing indicated in the first DCI is greater than at least one value in a set of values, the wireless communication device generates a first subcodebook to be multiplexed in the uplink transmission.

8. The method according to claim 1, wherein The first DCI schedules uplink transmissions, and the first DCI includes a downlink allocation index (DAI) with a first value; The wireless communication device does not receive downlink transmissions before or no later than receiving the first DCI, and feedback regarding the downlink transmissions is configured to be transmitted within the same time interval as the uplink transmissions; and The wireless communication device does not reuse the first subcodebook in the uplink transmission.

9. The method according to claim 1, wherein The first DCI schedules uplink transmissions, and the first DCI includes a downlink allocation index (DAI) with a first value; The wireless communication device did not receive a downlink transmission configured to provide feedback within the same time interval as the uplink transmission; and The wireless communication device does not reuse the codebook during the uplink transmission.

10. The method of claim 1, wherein The first DCI schedules uplink transmissions, the first DCI including a downlink allocation index (DAI) with a second value, or the wireless communication device receives downlink transmissions before or after receiving the first DCI, and feedback for the downlink transmissions is configured in the uplink transmissions; and The wireless communication device multiplexes the first subcodebook and the second subcodebook during the uplink transmission.

11. The method of claim 1, wherein The first DCI schedules uplink transmissions, and the first DCI includes a downlink allocation index (DAI) with a first value; The wireless communication device did not receive a downlink transmission configured to provide feedback within the same time interval as the uplink transmission; and The wireless communication device does not reuse the first subcodebook in the uplink transmission.

12. The method according to claim 1, wherein The first DCI schedules the uplink transmission, the first DCI includes a downlink allocation index (DAI) with a second value, or the wireless communication device receives the downlink transmission before or no later than receiving the first DCI, and feedback for the downlink transmission is configured to be transmitted in the same time interval as the uplink transmission. The wireless communication device generates a codebook, including: The first subcodebook is generated based on the value of the uplink downlink allocation index (DAI) of the first DCI; as well as The second subcodebook is generated according to the rules used for type 1 codebooks.

13. The method of claim 1, wherein The first DCI schedules the uplink transmission, the first DCI includes a downlink allocation index (DAI) with a second value, or the wireless communication device receives the downlink transmission before or no later than receiving the first DCI, and feedback for the downlink transmission is configured to be transmitted in the same time interval as the uplink transmission. The wireless communication device generates a first subcodebook based on the value of the uplink-downlink allocation index (DAI) of the first DCI.

14. The method of claim 1, wherein The wireless communication device receives at least one downlink transmission only after receiving the first DCI or no earlier than receiving the first DCI, and the feedback for the at least one downlink transmission is configured to be transmitted in the same time interval as the uplink transmission. The wireless communication device generates the second sub-codebook instead of the first codebook.

15. The method according to claim 1, wherein, The wireless communication device generates the second subcodebook based on whether it receives downlink transmissions after or no earlier than receiving the first DCI, and the feedback for the downlink transmissions is configured to be transmitted in the same time interval as the uplink transmissions.

16. The method of claim 1, wherein The network receives the first subcodebook from the wireless communication device during a first Physical Uplink Shared Channel (PUSCH) transmission; and The network receives the second subcodebook from the wireless communication device in a subsequent PUSCH transmission, the subsequent PUSCH transmission being a repetition of the first PUSCH transmission.

17. The method of claim 1, comprising: The network instructs the wireless communication device to provide feedback on the downlink transmission in the downlink transmission, corresponding to the time interval of the Physical Uplink Shared Channel (PUSCH) transmission; as well as The network receives feedback from the wireless communication device regarding the downlink transmission during the PUSCH transmission.

18. The method of claim 1, wherein The network receives the first subcodebook from the wireless communication device during a first Physical Uplink Shared Channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission of a PUSCH repetition; and The network receives the second subcodebook from the wireless communication device in the second PUSCH transmission, which is the last transmission of the PUSCH repetition.

19. The method according to claim 1, comprising: The network instructs the wireless communication device to provide feedback on the downlink transmission in the downlink transmission, corresponding to the time interval of the first Physical Uplink Shared Channel (PUSCH) transmission; as well as The network receives feedback from the wireless communication device regarding the downlink transmission during the first PUSCH transmission.

20. The method of claim 1, comprising: The network instructs the wireless communication device that the feedback for the downlink transmission in the downlink transmission corresponds to the time interval of the subsequent Physical Uplink Shared Channel (PUSCH) transmission, which is a PUSCH transmission other than the first transmission of PUSCH repetition; and The network receives feedback from the wireless communication device regarding the downlink transmission in the final PUSCH, which is the last transmission of the PUSCH repetition.

21. The method of claim 1, wherein The codebook includes a type 2 codebook; and The size of the codebook is determined based on at least one of the uplink downlink allocation index (DAI) in the first DCI used for downlink transmission or the DAI in the last DL DCI, wherein the downlink transmission will be fed back in the same time interval as the uplink transmission scheduled by the first DCI.

22. The method of claim 21, wherein at least one of the following is satisfied: The first DCI begins before or no later than the last downlink DCI, and the size of the codebook is determined based on the DAI in the last downlink DCI. The first DCI begins after or no earlier than the last downlink DCI, and the codebook size is determined based on the uplink DAI in the first DCI; or The last DCI begins after or no earlier than the first DCI, and the DAI in the downlink DCI that begins after or no earlier than the first DCI starts counting from the value of the uplink DAI in the first DCI.

23. The method of claim 1, wherein The size of the first subcodebook is determined based on the uplink-downlink allocation index (DAI) in the first DCI; The size of the second subcodebook is determined based on the DAI in the last downlink DCI used for downlink transmission; and The DAI in the downlink DCI corresponding to the second subcodebook is counted starting from 1.

24. The method of claim 1, wherein The size of the first subcodebook is determined based on the first downlink allocation index (DAI) in the penultimate DL DCI among a plurality of DCIs used for downlink transmission, the penultimate DL DCI being either before or no later than the first DCI; The size of the second subcodebook is determined based on the second DAI in the penultimate DL DCI used for downlink transmission, wherein the penultimate downlink DL DCI is after or no earlier than the first DCI; and The DAI in the downlink DCI corresponding to the second subcodebook is counted starting from 1.

25. A wireless communication device, the wireless communication device comprising at least one processor and a memory, wherein, The at least one processor is configured to read code from the memory and implement the method according to claim 1.

26. A computer program product comprising computer-readable program medium code stored thereon, the code, when executed by at least one processor, causing the at least one processor to perform the method according to claim 1.

27. A wireless communication method, comprising: The wireless communication device receives downlink transmissions from the network. The wireless communication device sends feedback information for the downlink transmission to the network during an uplink transmission scheduled by a first downlink control information (DCI), wherein the feedback information corresponds to a codebook, the codebook including a first sub-codebook and a second sub-codebook based on the reception time of the first DCI.

28. A wireless communication device, the wireless communication device comprising at least one processor and a memory, wherein, The at least one processor is configured to read code from the memory and implement the method according to claim 27.

29. A computer program product comprising computer-readable program medium code stored thereon, the code, when executed by at least one processor, causing the at least one processor to perform the method according to claim 27.

Images