Terminal device and method for terminal device

Abstract

To provide a device, method of HARQ feedback for a plurality of data channels scheduled with single DCI and a computer-readable medium.SOLUTION: A method comprises: receiving, at a terminal device, control information from a network device; in accordance with a determination that transmissions of a plurality of transport blocks on a set of data channels are scheduled by the received control information, determining a control channel for transmitting Hybrid Automatic Repeat Request (HARQ) feedback information associated with the plurality of transport blocks; and transmitting the HARQ feedback information via the control channel to the network device. In this way, the enhancement on HARQ-ACK feedback mechanism in a case when multiple TBs / independent PDSCHs are scheduled by a single DCI can be reached, which may alleviate possible PUCCH collisions and provide more flexibility.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to an apparatus, method, device, and computer-readable storage medium for Hybrid Automatic Repeat reQuest (HARQ) feedback for multiple data channels scheduled by a single Downlink Control Information (DCI). [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) Release 17 (Rel-17) is considering scheduling multiple transport blocks (TBs) / physical downlink shared channels (PDSCHs) on a single DCI, due to the limited capacity of the physical downlink control channel (PDCCH) for reduced capability NR devices.

[0003] For Reduced Capability NR devices, it has been proposed that the user equipment (UE) bandwidth may be narrowed to 5 MHz or 10 MHz and that PDCCH monitoring may be reduced with less blind decoding and CCE restrictions, but this may lead to limited PDCCH capacity for narrow bandwidths.

[0004] Therefore, a HARQ feedback scheme is discussed for multiple TB / PDSCHs scheduled in a single DCI. Summary of the Invention [Problem to be solved by the invention]

[0005] Overall, the embodiments of the present disclosure provide a solution for HARQ for multiple data channels scheduled by a single DCI. [Means for solving the problem]

[0006] In a first aspect, a communication method is provided, the method including: receiving, in a terminal device, control information from a network device; determining, according to a determination that transmission of a plurality of transport blocks in a data channel set from the network device to the terminal device is scheduled by the control information, a control channel for transmitting HARQ feedback information of a hybrid automatic repeat request associated with the plurality of transport blocks; and transmitting the HARQ feedback information to the network device via the control channel.

[0007] In a second aspect, a communication method is provided, the method including: transmitting control information from a network device to a terminal device, the control information scheduling transmission of a plurality of transport blocks from the network device to the terminal device on a data channel set, and receiving, via a control channel, from the terminal device, hybrid automatic repeat request HARQ feedback information associated with the plurality of transport blocks.

[0008] In a third aspect, there is provided a terminal device, the terminal device comprising a processor and a memory having instructions stored thereon, the memory and the instructions being configured, together with the processor, to cause the terminal device to perform a method according to the first aspect.

[0009] In a fourth aspect, there is provided a network device comprising a processor and a memory having instructions stored thereon, the memory and the instructions being configured, together with the processor, to cause the network device to perform a method according to the second aspect.

[0010] In a fifth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor of an apparatus, cause the apparatus to perform a method according to the first aspect.

[0011] In a sixth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor of an apparatus, cause the apparatus to perform a method according to the second aspect.

[0012] Other features and advantages of the disclosed embodiments will become apparent from the following description of specific embodiments, taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the disclosed embodiments. [Brief description of the drawings]

[0013] BRIEF DESCRIPTION OF THE DRAWINGS Embodiments of the present disclosure are illustrated by way of example and advantages thereof will now be described in detail with reference to the accompanying drawings, in which: FIG.

[0014] [Figure 1] 1 illustrates an exemplary environment in which exemplary embodiments of the present disclosure may be implemented.

[0015] [Diagram 2] 1 illustrates an example signaling chart illustrating an example process of resource coordination in accordance with some embodiments of the present disclosure.

[0016] [Diagram 3]1 illustrates multiple PDSCHs scheduled by a single DCI and a PUCCH on which HARQ feedback associated with the multiple PDSCHs is transmitted, in accordance with some embodiments of the present disclosure.

[0017] [Figure 4A] 1 illustrates construction of a codebook for HARQ feedback in accordance with some embodiments of the present disclosure. [Figure 4B] 1 illustrates a codebook configuration for HARQ feedback in accordance with some embodiments of the present disclosure.

[0018] [Figure 5A] 1 illustrates construction of a codebook for HARQ feedback in accordance with some embodiments of the present disclosure. [Figure 5B] 1 illustrates a codebook configuration for HARQ feedback in accordance with some embodiments of the present disclosure.

[0019] [Figure 6A] 1 illustrates a codebook configuration for HARQ feedback in accordance with some embodiments of the present disclosure. [Figure 6B] 1 illustrates a codebook configuration for HARQ feedback in accordance with some embodiments of the present disclosure. [Figure 6C] 1 illustrates a codebook configuration for HARQ feedback in accordance with some embodiments of the present disclosure.

[0020] [Figure 7] 1 illustrates a flowchart of an example method for HARQ feedback for multiple data channels scheduled by a single DCI, in accordance with some example embodiments of the present disclosure.

[0021] [Figure 8]1 illustrates a flowchart of an example method for HARQ feedback for multiple data channels scheduled by a single DCI, in accordance with some example embodiments of the present disclosure.

[0022] [Figure 9] FIG. 1 shows a schematic block diagram of an apparatus suitable for practicing exemplary embodiments of the present disclosure.

[0023] Throughout the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] The principles of the present disclosure will be described with reference to some exemplary embodiments. It should be understood that these embodiments are merely described for illustrative purposes to aid those skilled in the art in understanding and implementing the present disclosure, and do not imply any limitations on the scope of the present disclosure. The present disclosure described herein can be implemented in a variety of ways other than those described below.

[0025] In the following description and claims, unless defined otherwise, all technical and scientific terms used have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0026] References in this disclosure to "one embodiment," "an embodiment," "an exemplary embodiment," and the like indicate that the embodiment being described may include a particular feature, structure, or characteristic, but not all embodiments need to include such a particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an exemplary embodiment, it is believed to be within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0027] In this specification, terms such as "first", "second", etc. may be used to describe various elements, but it should be understood that such elements should not be limited by these terms. These terms are used only to distinguish the function of the various elements. As used in this specification, the term "and / or" includes any one or more of the listed items, and all combinations thereof.

[0028] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise. Furthermore, it should be understood that the terms "comprise," "comprising," "having," "having," "including," and / or "including," when used herein, specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0029] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as a fifth generation (5G) system, Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrow Band Internet Of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in the communication network may be performed by any suitable generation of communication protocols, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) New Radio (NR) communication protocols, and / or other protocols now known or developed in the future. Embodiments of the present disclosure may be applied to various communication systems. Considering the rapid development of communication, there will naturally be future communication technologies and communication systems in which the present disclosure can be embodied, and the scope of the present disclosure should not be deemed to be limited only to the aforementioned systems.

[0030] As used herein, the term "network equipment" refers to a node in a communication network through which a terminal device accesses the network and receives services therefrom. Depending on the terminology and technology applied, the network equipment may refer to a base station (BS) or access point (AP), such as a Node B (Node B or NB), evolved Node B (eNode B or eNB), NR next generation Node B (gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a femto, a pico, or other low power node.

[0031] A "terminal" refers to any end device capable of wireless communication. By way of example and not limitation, a terminal may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber equipment, a mobile station (MS), or an access terminal (AT). Examples of end devices include, but are not limited to, mobile phones, cell phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable end devices, personal digital assistants (PDAs), portable computers, desktop computers, imaging end devices such as digital cameras, gaming end devices, music storage and playback devices, in-vehicle wireless end devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), Internet of Things (IoT) devices, wearables such as watches, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, and the like. A terminal device may also correspond to the Mobile Termination (MT) portion of an Integrated Access and Backhaul (IAB) node (also known as a relay node). In the following description, the terms "terminal device", "communication device", "terminal", "user equipment", and "UE" may be used interchangeably.

[0032] While the functions described herein may be performed in fixed and / or wireless network nodes in various exemplary embodiments, in other exemplary embodiments the functions may be implemented in a user terminal device (such as a mobile phone, tablet computer, laptop computer, desktop computer, mobile IoT device, or fixed IoT device). Such user terminal devices may include corresponding functions as described in connection with fixed and / or wireless network nodes, for example, as appropriate. The user terminal device may be a user terminal and / or a control device, such as a chipset or processor, configured to control the user terminal when attached to the user terminal. Examples of such functions include a bootstrap server function and / or a home subscriber server. Such functions may be implemented in the user terminal device by providing the user terminal device with software that is configured for the user terminal device to execute in terms of these functions / nodes.

[0033] FIG 1 illustrates an exemplary communications network 100 in which embodiments of the present disclosure may be implemented. As illustrated in FIG 1, communications network 100 includes a terminal device 110 and a network device 120. Terminal device 110 may communicate with network device 120. It should be understood that the number of network devices and terminal devices illustrated in FIG 1 is illustrated for illustrative purposes and is not intended to imply any limitation. Communications network 100 may include any suitable number of network devices and terminal devices.

[0034] Depending on the communication technology, the network 100 may be a Code Division Multiple Access (CDMA) network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) network, or others. The communications discussed in network 100 may conform to any suitable standard, including, but not limited to, New Radio Access (NR), Long Term Evolution (LTE), LTE Evolution (LTE-Evolution), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), cdma2000, Global System for Mobile Communications (GSM), and the like. Furthermore, communications may be performed according to any currently known or future developed generation of communications protocols. Examples of communications protocols include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, and fifth generation (5G) communications protocols. The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below with respect to LTE. LTE terminology is used extensively in the following description.

[0035] As mentioned above, the 3rd Generation Partnership Project (3GPP) Release 17 (Rel-17) considers scheduling multiple transport blocks (TBs) / physical downlink shared channels (PDSCHs) on a single DCI because of the limited capacity of the physical downlink control channel (PDCCH) for reduced capability NR devices.

[0036] In addition to Reduced Capability NR device scenarios, it is possible to consider scheduling of multiple transport blocks (TBs) / physical downlink shared channels (PDSCHs) over a single DCI in at least one of the following: New Radio (NR) Multiple-Input Multiple-Output (MIMO), NR Sidelink Enhancements, NR beyond 52.6 GHz, NR operation extension to 71 GHz, enhanced Ultra-Reliable and Low Latency Communications (eURLLC) / Enterprise Industrial Internet of Things (eIIoT), non-terrestrial network (NTN), Narrowband Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) in NTN, UE power saving enhancements, NR coverage enhancements, NB-IoT and LTE-MTC, integrated access backhauling (IAB). backhauling), NR multicast and broadcast services, and multi-radio dual connectivity enhancements.

[0037] For Reduced Capability NR devices, it is proposed that the user equipment (UE) bandwidth may be narrowed to 5 MHz or 10 MHz, and PDCCH monitoring may be reduced by fewer blind decoding and CCE restrictions, which may lead to limited PDCCH capacity for narrow bandwidths. The table below shows the number of PDCCHs with a bandwidth of 10 MHz and subcarrier spacing of 30 KHz / 15 KHz, and shows that the capacity of PDCCH is limited by bandwidth reduction. Table 1 PDCCH capacity limitations due to bandwidth reduction JPEG0007622883000001.jpg41162

[0038] "HARQ-ACK Timing K 1、k The term " may refer to a time window from downlink data reception to UL acknowledgment transmission. For example, the HARQ-ACK timing may be indicated by Radio Resource Control (RRC) signaling or control information, i.e., Downlink Control Information (DCI).

[0039] For example, a set of HARQ-ACK timing values ​​K1 is configured for the terminal device by an RRC parameter related to a DL DCI format. For a PDSCH scheduled by DCI format 1_0, an SPS PDSCH reception activated by DCI format 1_0, or an SPS PDSCH release indicated by DCI format 1_0, the set of timing values ​​between the PDSCH and the HARQ-ACK is defined in the specification K1={1,2,3,4,5,6,7,8}. For a PDSCH scheduled by DCI format 1_1, an SPS PDSCH reception activated by DCI format 1_1, or an SPS PDSCH release indicated by DCI format 1_1, the set of timing values ​​between the PDSCH and the HARQ-ACK is configured by the RRC parameter dl-DataToUL-ACK. For a PDSCH scheduled by DCI format 1_2, an SPS PDSCH reception activated by DCI format 1_2, or an SPS PDSCH release indicated by DCI format 1_2, the set of timing values ​​between the PDSCH and the HARQ-ACK is configured by the RRC parameter dl-DataToUL-ACKForDCIFormat1_2.

[0040] It is specified that bits 1 to 3 of the PDSCH-toHARQ_feedback timing indicator field of the DL DCI are used to indicate one of the set of timing values ​​K1. The mapping between the value of the PDSCH-toHARQ_feedback timing indicator field and the slot number is as follows: Table 2: Mapping of PDSCH-toHARQ_feedback timing indicator field values ​​and slot numbers JPEG0007622883000002.jpg133165

[0041] There are two types of codebooks used for HARQ feedback in licensed spectrum: Type-1 HARQ-ACK codebook and Type-2 HARQ-ACK codebook. The Type-1 HARQ-ACK codebook can be regarded as a semi-static codebook, and the Type-2 HARQ-ACK codebook can be regarded as a dynamic codebook.

[0042] The Type-1 HARQ-ACK codebook is the PDSCH-toHARQ_feedback timing value K1, the PDSCH time domain resource allocation (TDRA) table, and the downlink SCS setting μ when different numerologies are set in DL and UL. DL and uplink SCS setting μ UL Ratio to 2 (μDL-μUL) The TDD configuration is determined based on factors such as TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated.

[0043] In the conventional method, the HARQ-ACK window size can be determined based on the HARQ-ACK timing value set K1. Then, for each HARQ-ACK timing value in the set K1, a PDSCH reception opportunity candidate in each slot can be determined based on the TDRA table and the TDD configuration. The PDSCH reception opportunity candidates in the time domain RA table that overlap with the UL configured by the TDD-UL-DL-ConfigurationCommon and the TDD-UL-DL-ConfigDedicated are excluded. Then, for the overlapping PDSCH reception opportunity candidates, only one HARQ-ACK bit is generated based on a specific rule. Once the PDSCH reception opportunity is determined, a Type-1 HARQ-ACK codebook can be determined based on the PDSCH reception opportunity.

[0044] The Type-2 HARQ-ACK codebook is determined based on the counter DAI and total DAI in the scheduling DCI, and the HARQ-ACK for the PDSCH scheduled by the DCI pointing to the same slot for PUCCH transmission is mapped to the same HARQ-ACK codebook. First, the DCI group for scheduling the PDSCH reception can be determined, and the terminal device transmits the corresponding HARQ-ACK information in the same PUCCH in slot n. Then, the codebook size and the bit order of the HARQ-ACK information can be determined based on parameters such as the counter DAI of the DL DCI format, the total DAI of the DCI format 1_1 / DCI format 1_2, maxNrofCodeWordsScheduledByDCI, Harq-ACK-SpatialBundlingPUCCH, and PDSCH-CodeBlockGroupTransmission.

[0045] The conventional HARQ-ACK feedback mechanism, which schedules a single TB or two TBs in the spatial domain for one PDCCH, cannot be directly reused when multiple TBs / PDSCHs are scheduled by a single DCI.

[0046] Therefore, the present disclosure proposes a HARQ-ACK feedback mechanism. When a terminal device receives multiple TBs scheduled by a single DCI on a data channel, the terminal device can determine a control channel for sending HARQ-ACK feedback and determine a corresponding codebook for carrying HARQ-ACK feedback information. Then, the terminal device can send the HARQ-ACK feedback information to a network device through a control channel based on the determined codebook.

[0047] The principles and implementations of the present disclosure are described in detail below with reference to Figure 2. For discussion purposes, a process 200 is described with reference to Figure 1. The process 200 involves the terminal device 110 and the network device 120 shown in Figure 1.

[0048] As shown in Figure 2, the network device 120 transmits (210) control information, i.e., downlink control information, to the terminal device 110. The control information may schedule the transmission of multiple TBs transmitted from the network device 120 to the terminal device 110 in different data channels, i.e., PDSCHs. It should be understood that the terminal device 110 does not expect these PDSCHs to be scheduled by DCIs of different cells. These PDSCHs should be scheduled by DCIs of one cell.

[0049] Next, the terminal device 110 first determines a control channel, i.e., PUCCH, for transmitting HARQ-ACK feedback information (220). The terminal device 110 determines the HARQ-ACK timing value K 1,k The slot / subslot for PUCCH transmission may be determined based on K 1,k is the time from the slot / subslot in which the last PDSCH is received in the time domain among the multiple PDSCHs to the slot / subslot in which the UL acknowledgment is transmitted.

[0050] FIG. 3 illustrates multiple PDSCHs scheduled by a single DCI and a PUCCH on which HARQ feedback associated with the multiple PDSCHs is transmitted in accordance with some embodiments of the present disclosure.

[0051] As shown in Fig. 3, a PDCCH 311 is transmitted in slot 301. A DCI can be received from the PDCCH 311. The DCI may schedule a first PDSCH 312 transmitted in slot 302 and a second PDSCH 313 transmitted in slot 303. To determine the slot for PUCCH transmission, the terminal device 110 receives a HARQ-ACK timing value K 1,k This value indicates the time in the time domain between PDSCHs until the transmission of the UL acknowledgment from the slot / sub-slot of the last PDSCH reception, i.e., slot 303 as shown in FIG. 3. K 1,k = 2, then slot 305 can be determined for transmitting PUCCH 314 .

[0052] In some embodiments, the range of values ​​for the set of HARQ-ACK timings K1 (also known as dl-DataToUL-ACK) is determined, e.g., the maximum K 1,k can be extended to 31 or 63. When the terminal device 110 receives N independent PDSCHs scheduled by the DCI format from slots n-N+1 to n, the terminal device 110 reports corresponding HARQ-ACK information for the PDSCHs in the PUCCH of slot n+k, where k is indicated by the value of the PDSCH-to-HARQ_feedback timing indicator field of the DCI format.

[0053] In addition, to report HARQ-ACK feedback information for each PDSCH, the terminal device 110 may determine a feedback pattern for indicating the HARQ-ACK feedback information. The determination of the feedback pattern may depend on the reporting mode of the HARQ-ACK feedback information and the adopted type of the HARQ HARQ-ACK codebook.

[0054] In some embodiments, the terminal device 110 may generate only one HARQ-ACK bit for multiple independent PDSCHs by bundling HARQ-ACK values ​​for multiple PDSCHs. The terminal device 110 may generate a bundling HARQ feedback value by determining respective HARQ feedback values ​​for multiple TBs in different PDSCHs and performing a logical operation, such as an AND operation, on the respective HARQ feedback values. An example of an AND operation for multiple independent PDSCHs can be shown as follows: Table 3: AND operation for multiple independent PDSCHs JPEG0007622883000003.jpg35162

[0055] 3, the HARQ-ACK value for the first PDSCH 312 and the HARQ-ACK value for the second PDSCH 313 may be bundled into a 1-bit HARQ-ACK value and reported on the PUCCH 314. For example, in the case of an ACK for the first PDSCH 312 and a NACK for the second PDSCH 313, the 1-bit HARQ-ACK value may be ACK(1)&NACK(0)=NACK(0).

[0056] In some embodiments, the terminal device 110 may also generate HARQ-ACK bits for each PDSCH among the multiple PDSCHs separately and report these HARQ-ACK bits in one PUCCH, i.e., the terminal device 110 may determine respective HARQ feedback values ​​for multiple TBs in different PDSCHs and report these HARQ feedback values ​​in the PUCCH.

[0057] Next, the selection and use of a codebook for carrying HARQ-ACK feedback information, including a bundled 1-bit HARQ-ACK value or separate HARQ-ACK bits for each PDSCH, may be further discussed as follows: As mentioned above, there are two types of codebooks for HARQ feedback: Type-1 codebook and Type-2 codebook.

[0058] In the case where the terminal device 110 generates one HARQ-ACK bit for multiple independent PDSCHs, if a Type-1 HARQ-ACK codebook is configured in the terminal device 110, in some embodiments, the terminal device 110 does not assume that multiple PDSCHs are scheduled by DCIs with different time domain resource allocations. That is, one HARQ-ACK position is generated in the HARQ-ACK codebook for each reception opportunity of a TB in different PDSCHs. The terminal device 110 may report one HARQ-ACK bit for multiple PDSCHs at the corresponding HARQ-ACK position in the Type-1 HARQ-ACK codebook.

[0059] 4A illustrates a codebook configuration for HARQ feedback according to some embodiments of the present disclosure. As shown in FIG. 4A, the reception opportunity for TB in PDSCH 411 of slot 401 starts from the second symbol and has a symbol length of 5, and the reception opportunity for TB in PDSCH 412 of slot 402 starts from the second symbol and has a symbol length of 5. Therefore, the reception opportunities of PDSCH 411 and PDSCH 412 can be considered to be the same.

[0060] As described above, the Type-1 HARQ-ACK codebook for multiple PDSCHs is a single HARQ-ACK timing value K 1,kA codebook pattern may then be determined to indicate the size of the codebook, e.g., the number of reporting positions contained in the codebook. As shown in FIG. 4A, the codebook may include reporting positions 421-426. For example, in the case of an ACK for the first PDSCH 411 and a NACK for the second PDSCH 412, a 1-bit HARQ-ACK value may be ACK(1)&NACK(0)=NACK(0). Then, the value NACK(0) may be reported at position 423.

[0061] In some embodiments, the multiple PDSCHs according to the DCI may have different SLIV allocations, and multiple HARQ-ACK positions are associated with the multiple PDSCHs in the HARQ-ACK codebook. In this case, if the terminal device reports only one HARQ-ACK bit for the multiple PDSCHs at one of the HARQ-ACK positions associated with the multiple PDSCHs in the HARQ-ACK codebook, the HARQ-ACK position may be determined based on a reception opportunity associated with one of the PDSCHs, such as the first PDSCH or the last PDSCH, among the multiple PDSCHs in the time domain.

[0062] Alternatively, the HARQ-ACK position may be determined based on receiving a PDSCH with the smallest starting symbol, receiving a PDSCH with the longest duration, or receiving a PDSCH with the smallest / largest HARQ-ACK process ID.

[0063] That is, the terminal device 110 may select a reference TB from among multiple TBs. The reference TB may be transmitted in the first / last PDSCH in the time domain, a reception opportunity for a reference TB having a minimum start symbol, a reception opportunity for a reference TB having a maximum duration, or reception with a minimum / maximum HARQ-ACK process ID.

[0064] Figure 4B illustrates a codebook configuration for HARQ feedback according to some embodiments of the present disclosure. As shown in Figure 4B, the TB reception opportunity in PDSCH 411 of slot 401 starts from the second symbol and has a symbol length of 5, and the TB reception opportunity in PDSCH 412 of slot 402 starts from the 9th symbol and has a symbol length of 5. Therefore, the reception opportunities of PDSCH 411 and PDSCH 412 can be considered as different. Two HARQ-ACK positions 423 and 425 are generated for PDSCH 411 and PDSCH 412, respectively.

[0065] In this case, when the terminal device 110 receives an ACK for PDSCH 411 and an ACK for PDSCH 412, it reports only the valid HARQ-ACK value ACK(1)&ACK(1)=ACK(1) at the HARQ-ACK position of the last PDSCH reception, i.e., PDSCH 412. Therefore, the terminal device 110 reports only ACK(1) at the reporting position 425.

[0066] For the remaining HARQ-ACK positions in the HARQ-ACK codebook associated with multiple PDSCHs, the terminal device 110 reports a fixed ACK or NACK value, or the UE reports a valid HARQ-ACK value for other PDSCHs scheduled by the network device. For example, in FIG. 4B, the terminal device 110 may report a NACK(0) at position 423.

[0067] When the terminal device 110 generates a HARQ-ACK bit for each PDSCH among a plurality of PDSCHs separately and reports these HARQ-ACK bits in one PUCCH, if a Type-1 HARQ-ACK codebook is configured in the terminal device 110, the determination of the Type-1 HARQ-ACK codebook for the plurality of PDSCHs is performed according to one HARQ-ACK timing value K 1,k The reception opportunities for multiple TBs in multiple PDSCHs scheduled by one DCI are equal.

[0068] However, if only one HARQ-ACK position is generated according to the current Type-1 HARQ-ACK codebook configuration rules, the terminal device 110 cannot report all valid HARQ-ACK bits for multiple PDSCHs scheduled by DCI.

[0069] In this case, for multiple TBs in multiple PDSCHs with the same reception opportunity, N HARQ-ACK positions are generated, where N is the maximum number of TBs or the actual number of TBs scheduled by DCI for the terminal device.

[0070] 5A illustrates a codebook configuration for HARQ feedback according to some embodiments of the present disclosure. As shown in FIG. 5, PDSCH 511 and PDSCH 512 have the same reception opportunity. In addition, the Type-1 HARQ-ACK codebook for PDSCH 511 and PDSCH 512 has one HARQ-ACK timing value K 1,k For PDSCH 511 and PDSCH 512, two HARQ-ACK positions, namely 523 and 524, can be generated.

[0071] In some embodiments, the N HARQ-ACK positions in the codebook for the PDSCH are in ascending / descending order of the HARQ-ACK process ID. Alternatively, the N HARQ-ACK positions in the codebook for the PDSCH are in the reception order of the PDSCH.

[0072] In addition, when a Type-1 HARQ-ACK codebook is configured in the terminal device 110, it is also possible to determine a Type-1 HARQ-ACK codebook for multiple PDSCHs based on multiple virtual HARQ-ACK timing values. The virtual HARQ-ACK timing value for each PDSCH is one HARQ-ACK timing value K indicated by the DCI. 1,kand a time offset Δt, which is the time difference between the current PDSCH reception and the last or first PDSCH reception.

[0073] 5B illustrates the configuration of a codebook for HARQ feedback according to some embodiments of the present disclosure. As shown in FIG. 5, PDSCH 511 and PDSCH 512 have the same reception opportunity. The HARQ-ACK timing value K 1,k = 2 and the time offset Δt = 1, the virtual HARQ-ACK timing value for PDSCH 511 is K 1,k +Δt=3. In the determined Type-1 HARQ-ACK codebook having positions 521 to 526, the HARQ-ACK value for PDSCH 511 can be reported at position 521, and the HARQ-ACK value can be reported at position 524.

[0074] When the terminal device 110 generates a HARQ-ACK bit separately for each PDSCH among multiple PDSCHs and reports these HARQ-ACK bits in one PUCCH, if a Type-2 HARQ-ACK codebook is configured in the terminal device and only one CC is configured in the terminal device, HARQ-ACK information for multiple PDSCHs scheduled by DCI and HARQ-ACK information for a single PDSCH scheduled by DCI / or two SDM-based PDSCHs are allowed to be multiplexed in the PUCCH.

[0075] In this case, the counter DAI is calculated cumulatively for multiple PDSCHs scheduled by a single DCI. The bit width of the counter DAI field can be extended by the network device 120 up to x bits, for example, when x=4, the maximum value of c-DAI is 16. The HARQ-ACK position in the Type-2 codebook for these PDSCHs scheduled by the DCI can be the same as that of the Type-1 codebook in paragraph 0070.

[0076] FIG. 6A illustrates a codebook configuration for HARQ feedback in accordance with some embodiments of the present disclosure.

[0077] 6A, a first DCI 611 with a counter DAI=1 may schedule PDSCHs 621, 622, 623, and 624 in slots 601, 602, 603, and 604, respectively. A second DCI 612 with a counter DAI=5 may schedule a PDSCH 625 on slot 605, and a third DCI 613 with a counter DAI=6 may schedule a PDSCH 626 on slot 607. If the terminal device 110 determines that HARQ-ACK feedback information associated with PDSCHs 621 to 626 is transmitted on PUCCH 631 on slot 608, then the first four HARQ-ACK positions are generated for the four PDSCHs scheduled by DCI 611, a fifth HARQ-ACK position is generated for the PDSCH scheduled by DCI format 612, and a sixth HARQ-ACK position is generated for the PDSCH scheduled by DCI format 613.

[0078] Thus, in FIG. 6A, HARQ-ACK values ​​for PDSCHs 621, 622, 623, 624 may be reported in positions 641 through 644, and HARQ-ACK values ​​for PDSCHs 625 and 626 may be reported in positions 645 and 646, respectively.

[0079] In some possible embodiments, if a Type-2 HARQ-ACK codebook is configured in the terminal device and only one CC is configured in the terminal device, HARQ-ACK information for multiple PDSCHs scheduled by DCI and HARQ-ACK information for a single PDSCH scheduled by DCI / or two SDM-based PDSCHs are allowed to be multiplexed in PUCCH. In this case, two sub-codebooks are configured separately for multiple PDSCHs by DCI and a single PDSCH by DCI. The counter DAI is calculated separately for each sub-codebook. The sub-codebook containing only HARQ-ACK bits for multiple PDSCHs is placed after the sub-codebook containing only HARQ-ACK bits for a single PDSCH.

[0080] FIG. 6B illustrates a codebook configuration for HARQ feedback in accordance with some embodiments of the present disclosure.

[0081] Similar to Figure 6A, in Figure 6B a first DCI 611 with counter DAI=1 may schedule PDSCHs 621, 622, 623, 624 in slots 601, 602, 603, 604, respectively. A second DCI 612 with counter DAI=1 may schedule a PDSCH 625 on slot 605, and a third DCI 613 with counter DAI=2 may schedule a PDSCH 626 on slot 607. If the terminal device 110 determines that HARQ-ACK feedback information associated with PDSCHs 621 to 626 is transmitted on PUCCH 631 in slot 608, then two HARQ-ACK positions 641, 642 can be generated for reporting the HARQ-ACK values ​​of PDSCHs 625 and 626, and four HARQ-ACK positions 643 to 646 can be generated for reporting the HARQ-ACK values ​​of PDSCHs 621, 622, 623, and 624.

[0082] In some possible embodiments, if a Type-2 HARQ-ACK codebook is configured for the terminal device and only one component carrier (CC) is configured for the terminal device, the HARQ-ACK information for a plurality of PDSCHs scheduled by DCI and the HARQ-ACK information for a single PDSCH or two PDSCHs based on SDM scheduled by DCI are permitted to be multiplexed on the PUCCH. In this case, the terminal device 110 may generate N HARQ-ACK positions for the PDSCH each time it receives DL scheduling DCI. N is the maximum number of TBs scheduled by a single DCI, and N can be set by RRC. For example, in the case of a single PDSCH scheduled by DCI, the terminal device may report a valid HARQ-ACK value only at the first position among the N corresponding HARQ-ACK positions, and report NACK at the other N-1 positions. In the case of a plurality of PDSCHs scheduled by DCI, if M PDSCHs are scheduled and M < N, the terminal device may report M valid HARQ-ACK values only at the first M positions among the N corresponding HARQ-ACK positions, and report NACK at the other N-M positions.

[0083] FIG. 6C shows a configuration of a codebook for HARQ feedback according to some embodiments of the present disclosure.

[0084] 6A and 6B, the first DCI 611 may schedule PDSCHs 621, 622, 623, and 624 in slots 601, 602, 603, and 604, respectively. The second DCI 612 may schedule PDSCHs 625 in slot 605, and the third DCI 613 may schedule PDSCHs 626 in slot 607. If the terminal device 110 determines that HARQ-ACK feedback information associated with PDSCHs 621 to 626 is transmitted on a PUCCH 631 in slot 608, the terminal device 110 may determine a codebook size based on the maximum number of PDSCHs scheduled by the DCI.

[0085] Thus, four HARQ-ACK positions 641-644 may be generated for reporting the HARQ-ACK values ​​of PDSCH 621, 622, 623, 624, four HARQ-ACK candidate positions 651-654 may be generated for reporting the HARQ-ACK value of PDSCH 625, and four HARQ-ACK candidate positions 661-664 may be generated for reporting the HARQ-ACK value of PDSCH 626.

[0086] As mentioned above, the terminal device may report a valid HARQ-ACK value only in the first of N corresponding HARQ-ACK positions and may report NACKs in the other N-1 positions. Thus, the HARQ-ACK value for PDSCH 625 may be reported in position 651 and the HARQ-ACK value for PDSCH 626 may be reported in position 661.

[0087] Thus, when the terminal device 110 determines the feedback pattern of the HARQ-ACK feedback information, referring to FIG. 2, the terminal device 110 may transmit the HARQ-ACK feedback information to the network device via a control channel based on the feedback pattern (230).

[0088] Furthermore, with regard to the processing timeline of the HARQ feedback, the terminal device 110 determines whether the start symbol of the PUCCH Tx for the HARQ-ACK for the multiple PDSCHs is equal to or smaller than the end symbol of the last PDSCH reception in the time domain among the multiple PDSCHs, as shown in the following equation: Do not assume it will be faster than TIFF0007622883000004.tif510. TIFF0007622883000005.tif684. As an option, the terminal device may report only HARQ-ACK information for PDSCH that meets the processing timeline.

[0089] Whether terminal device 110 can support / decode / receive multiple unicast / individual TBs (also known as multiple independent PDSCHs) scheduled by the PDCCH depends on the capabilities of terminal device 110.

[0090] If the terminal device 110 indicates the capability to receive / decode multiple unicast TBs scheduled by the PDCCH, the maximum number of unicast TBs scheduled by the PDCCH depends on the UE capability, for example, up to two unicast TBs can be scheduled by the PDCCH or up to four unicast TBs can be scheduled by the PDCCH depending on the individual capability for different maximum number of unicast TBs scheduled by the PDCCH.

[0091] The actual number of unicast TBs scheduled by the PDCCH depends on the configuration of the network device. The terminal device can obtain the information in the following ways: For example, the information can be indicated implicitly by RRC or DCI. Alternatively, the information can be indicated implicitly by RRC and DCI, for example, the number of time domain resources allocated for each entry in the TDRA table. As another option, the information can be indicated explicitly by RRC or DCI. For example, an RRC parameter of PDSCH-Config such as NrofTbSchduledBySingleDCI can be introduced. Alternatively, a new indicator field can be provided in the scheduling DCI or the current indicator field can be reinterpreted, for example, to use 2 bits to indicate the number of unicast TBs, with bit 00 corresponding to 1 TB, bit 01 corresponding to 2 TB, bit 10 corresponding to 3 TB, and bit 11 corresponding to 4 TB.

[0092] In this way, an enhanced HARQ-ACK feedback mechanism of the terminal device can be realized when multiple TBs / independent PDSCHs are scheduled by a single DCI, reducing the possibility of PUCCH collisions and providing further flexibility.

[0093] 7 illustrates a flowchart of an example method 700 of HARQ feedback for multiple data channels scheduled by a single DCI, in accordance with some example embodiments of the present disclosure. Method 700 may be implemented in terminal device 110, such as that shown in FIG. 1. For discussion purposes, method 700 will be described with reference to FIG. 1.

[0094] As shown in FIG. 7, at 710, the terminal device 110 receives control information from a network device.

[0095] In 720, if the terminal device 110 determines that the transmission of multiple transport blocks from the network device to the terminal device 110 in the data channel set is scheduled by control information, it determines a control channel for transmitting HARQ feedback information of a hybrid automatic repeat request associated with the multiple transport blocks.

[0096] In some example embodiments, the terminal device 110 may determine a reference position of a reference transport block in the time domain, where the reference transport block is transmitted on a reference data channel in the data channel set, and may obtain a time window of HARQ feedback associated with the reference transport block from the control information, and determine a control channel based on the reference position and the time window.

[0097] In some example embodiments, the terminal device 110 may generate a HARQ feedback value by performing an operation on each HARQ feedback value for a plurality of transport blocks, and determine the HARQ feedback value as the HARQ feedback information.

[0098] In some example embodiments, the terminal device 110 may determine respective HARQ feedback values ​​for multiple transport blocks as HARQ feedback information.

[0099] At 730, the terminal device 110 transmits the HARQ feedback information to the network device over the control channel.

[0100] In some example embodiments, when terminal device 110 determines that a Type-1 HARQ-ACK codebook is employed to convey HARQ feedback information, terminal device 110 may determine start and length indicator values, SLIVs, of each of a plurality of transport blocks in a data channel set. Terminal device 110 may determine a feedback position in the Type-1 HARQ-ACK codebook based on the SLIVs if the respective SLIVs are the same, and transmit the HARQ feedback information based on the feedback position.

[0101] In some example embodiments, if the terminal device 110 determines that a Type-1 HARQ-ACK codebook is employed to convey the HARQ feedback information, the terminal device 110 may determine a start and length indicator value, SLIV, for each of the multiple transport blocks in the data channel set. If the terminal device 110 determines that the respective SLIVs are different, the terminal device 110 may determine a reference SLIV corresponding to reception of a reference transport block in the multiple transport blocks in the time domain and determine a feedback position in the Type-1 HARQ-ACK codebook based on the reference SLIV. The terminal device 110 may transmit the HARQ feedback information based on the feedback position.

[0102] In some exemplary embodiments, the terminal device 110 may determine a reference SLIV corresponding to reception of the reference transport block based on at least one of an index of a reference data channel for transmitting the reference transport block, a value of a start symbol indicated in the reference SLIV, a value of a symbol length indicated in the reference SLIV, and an index of a HARQ process associated with reception of the reference transport block.

[0103] In some example embodiments, if the terminal device 110 determines that a Type-1 HARQ-ACK codebook is employed to convey the HARQ feedback information, the terminal device 110 may determine start and length indicator values, SLIVs, of multiple transport blocks in the data channel set. If the terminal device 110 determines that the respective SLIVs are the same, the terminal device 110 may determine multiple feedback positions for indicating the respective HARQ feedback values ​​in the Type-1 HARQ-ACK codebook based on the respective SLIVs. The terminal device 110 may determine an order of reporting the respective HARQ feedback values ​​in the multiple feedback positions based on indices of HARQ processes associated with the multiple transport blocks or a reception order of the multiple transport blocks in the data channel set, and transmit the HARQ feedback information based on the multiple feedback positions and the order.

[0104] In some example embodiments, when the terminal device 110 determines that a Type-1 HARQ-ACK codebook is employed to convey the HARQ feedback information, the terminal device 110 may obtain from the control information a set of time offsets of multiple transport blocks associated with a time window of the multiple transport blocks, the time window of the multiple transport blocks being associated with a time window of the HARQ feedback associated with a reference transport block in the multiple transport blocks. The terminal device 110 may determine multiple feedback positions for indicating respective HARQ feedback values ​​in the Type-1 HARQ-ACK codebook based on the time window and the set of time offsets, and transmit the HARQ feedback information based on the multiple feedback positions.

[0105] In some example embodiments, when the terminal device 110 determines that a Type-2 HARQ-ACK codebook is adopted to carry HARQ feedback information, the terminal device 110 may determine a codebook size of the Type-2 HARQ-ACK codebook and multiple feedback positions for indicating the respective HARQ feedback values ​​and the further HARQ feedback values ​​in the Type-2 HARQ-ACK codebook based on the number of data channel sets and the number of further data channels, the further HARQ feedback values ​​being for further transport blocks transmitted from the network device to the terminal device in the further data channel scheduled by the further control information. The terminal device may determine an order of reporting the respective HARQ feedback values ​​and the further HARQ feedback values ​​in the multiple feedback positions based on indices of HARQ processes associated with the multiple transport blocks and the further transport blocks or a reception order of the multiple transport blocks and the further transport blocks in the data channel set and the further data channel, and transmit the HARQ feedback information based on the codebook size, the multiple feedback positions, and the order.

[0106] In some example embodiments, if the terminal device 110 determines that a Type-2 HARQ-ACK codebook is employed to carry the HARQ feedback information, the terminal device 110 may determine a codebook size of the Type-2 HARQ-ACK codebook based on a threshold number of data channels allowed to be scheduled by the control information. The terminal device may determine multiple feedback positions for indicating respective HARQ feedback values ​​and further HARQ feedback values ​​for further transport blocks transmitted from the network device to the terminal device in the further data channels scheduled by the further control information based on the threshold number, the first number of data channel sets, and the second number of further data channels. The terminal device may then transmit the HARQ feedback information based on the codebook size, the multiple feedback positions, and the further feedback positions.

[0107] In some example embodiments, the terminal device 110 may determine a set of respective candidate feedback positions at which the respective HARQ feedback values ​​and the further HARQ feedback values ​​are allowed to be reported in the Type-2 HARQ-ACK codebook based on the threshold number. The terminal device may further determine a first portion of feedback positions for reporting the respective HARQ feedback values ​​in the respective set of candidate feedback positions based on the threshold number and the first number, and may determine a second portion of feedback positions for reporting the further HARQ feedback values ​​based on the threshold number and the second number. The terminal device may then determine the plurality of feedback positions based on the first portion of feedback positions and the second portion of feedback positions.

[0108] 8 illustrates a flowchart of an example method 800 of HARQ feedback for multiple data channels scheduled by a single DCI, in accordance with some example embodiments of the present disclosure. The method 800 may be implemented in a network device 120 as shown in FIG. 1. For discussion purposes, the method 800 will be described with reference to FIG. 1.

[0109] 8, the network device 120 transmits control information from the network device to the terminal device at 810. The control information schedules transmission of multiple transport blocks from the network device to the terminal device on a data channel set.

[0110] At 820, the network device 120 receives HARQ feedback information for hybrid automatic repeat requests associated with a plurality of transport blocks from the terminal device over a control channel.

[0111] 9 is a schematic block diagram of an apparatus 900 suitable for implementing embodiments of the present disclosure. The apparatus 900 may be provided to realize a communication apparatus, such as the terminal device 110 and the network device 120 shown in FIG. 1. As shown, the apparatus 900 includes one or more processors 910, one or more memories 920 coupled to the processor 910, and one or more communication modules 990 coupled to the processor 910.

[0112] The communication module 990 is for bidirectional communication. The communication module 990 has at least one antenna to facilitate communication. The communication interface may represent any interface necessary for communication with other network elements.

[0113] The processor 910 may be of any type suitable for a local technology network, including, by way of example and without limitation, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor configuration. The device 900 may have multiple processors, for example application specific integrated circuit chips time-slaved to a clock that is synchronized with a master processor.

[0114] The memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, Read Only Memory (ROM) 929, Electrically Programmable Read Only Memory (EPROM), flash memory, hard disks, compact discs (CDs), digital video disks (DVDs), and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, Random Access Memory (RAM) 922 and other volatile memories that do not retain information while powered off.

[0115] The computer program 930 includes computer executable instructions that are executed by the associated processor 910. The program 930 may be stored in the ROM 929. The processor 910 may load the program 930 into the RAM 922 to perform any suitable operation or process.

[0116] The embodiment of the present disclosure may be implemented by the program 930 such that the device 900 can execute any of the processes of the present disclosure discussed with reference to Figures 2 to 8. The embodiment of the present disclosure may be implemented by hardware or a combination of software and hardware.

[0117] In some embodiments, the program 930 may be tangibly included in a computer readable medium, which may be included in the device 900 (such as in memory 920) or in other storage accessible by the device 900. The device 900 may load the program 930 from the computer readable medium into RAM 922 for execution. The computer readable medium may include any type of non-volatile tangible storage device, such as a ROM, an EPROM, a flash memory, a hard disk, a CD, a DVD, etc.

[0118] In general, various embodiments of the present disclosure may be implemented by hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented by hardware, and other aspects may be implemented by firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure have been shown and described as block diagrams, flow charts, or illustrated by some other pictorial representation, it should be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented by, for example, but not limited to, hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controller or other computing device, or combinations thereof.

[0119] The present disclosure further provides at least one computer program product tangibly stored in a computer readable non-transitory storage medium. The computer program product includes computer executable instructions, such as instructions included in program modules. The instructions execute on a target real or virtual processor device to perform the methods 700, 800 described above with reference to Figures 7-8. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split among program modules as desired. The machine readable instructions of the program modules may be executed in local or distributed devices. In distributed devices, the program modules may be located in both local and remote storage media.

[0120] The program codes for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, a special purpose computer or other programmable data processing apparatus, and when the program codes are executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are performed. The program codes may run entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0121] In the context of the present disclosure, computer program code or associated data may be carried by any suitable carrier to enable an apparatus, device or processor to perform the various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0122] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Even more specific examples of computer-readable storage media include one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable-programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0123] It should be understood that although operations have been described in a particular order, it is not required that such operations be performed in the particular order or sequence shown, or that all of the operations shown be performed, in order to achieve desired results. In some situations, multitasking and parallel processing may be advantageous. Similarly, although the above discussion includes some specific implementation details, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to certain embodiments. Some features described in the context of individual embodiments may be implemented in combination in an embodiment. Conversely, various features described in the context of an embodiment may be implemented in multiple embodiments separately or in any suitable subcombination.

[0124] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure, as defined by the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. a processing unit for communicating with the network device; a receiver configured to receive a plurality of Physical Downlink Control Channel (PDSCH) transmissions scheduled by a first Downlink Control Information (DCI); Equipped with The receiver is configured to receive the single PDSCH transmission scheduled by a second DCI; When a Type-2 HARQ-ACK codebook is configured, the processing unit is configured to multiplex Hybrid Automatic Repeat Request (HARQ) feedback information for the plurality of PDSCH transmissions and HARQ feedback information for the single PDSCH transmission. Terminal device.

2. the processing unit is configured to determine, based on a number of the plurality of PDSCH transmissions, a first sub-codebook and a plurality of feedback positions in the first sub-codebook for indicating respective HARQ feedback values ​​for the plurality of PDSCH transmissions. The terminal device according to claim 1 .

3. A transmitter is further provided, the processing unit is configured to determine a second sub-codebook and a further feedback location in the second sub-codebook to indicate a further HARQ feedback value for the single PDSCH transmission; the transmitting unit is configured to transmit the HARQ feedback information based on the first sub-codebook, the second sub-codebook, the plurality of feedback positions, and the further feedback position. The terminal device according to claim 2.

4. A transmitter is further provided, the processing unit is configured to determine a codebook size of the Type-2 HARQ-ACK codebook based on a threshold number of the plurality of PDSCH transmissions that should be allowed to be scheduled by the first DCI; the processing unit is configured to determine a plurality of feedback positions for indicating the respective HARQ feedback values ​​and a further HARQ feedback value for a further transport block based on the threshold number, a first number of the plurality of PDSCH transmissions, and a second number of the two or more single PDSCH transmissions, the further transport block being transmitted from the network device to the terminal device on the single PDSCH transmission; the transmitting unit is configured to transmit the HARQ feedback information based on the codebook size, the plurality of feedback positions, and the further feedback position. The terminal device according to claim 1 .

5. the processing unit is configured to determine a set of respective candidate feedback positions in the Type-2 HARQ-ACK codebook at which the respective HARQ feedback values ​​and the further HARQ feedback values ​​are allowed to be reported based on the threshold number; the processing unit is configured to determine, in the respective set of candidate feedback locations, a first portion of feedback locations for reporting the respective HARQ feedback value based on the threshold number and the first number, and to determine a second portion of feedback locations for reporting the further HARQ feedback value based on the threshold number and the second number; the processor is configured to determine the plurality of feedback positions based on the first portion of the feedback positions and the second portion of the feedback positions. The terminal device according to claim 4.

6. 1. A method for a terminal device communicating with a network device, comprising: receiving a plurality of physical downlink shared channel (PDSCH) transmissions scheduled by a first downlink control information (DCI); receiving the single PDSCH transmission scheduled by a second DCI; Including, When a Type-2 HARQ-ACK codebook is configured, and multiplexing Hybrid Automatic Repeat Request (HARQ) feedback information for the plurality of PDSCH transmissions and HARQ feedback information for the single PDSCH transmission. method.

Images