Communication method, terminal device and computer readable medium

Abstract

Embodiments of the present disclosure relate to devices, methods, and computer-readable storage media for HARQ feedback for multiple data channels scheduled by a single DCI. The method includes receiving control information from a network device at a terminal device; determining a control channel for sending hybrid automatic repeat request HARQ feedback information associated with the multiple transport blocks based on determining that the transmission of the multiple transport blocks from the network device to the terminal device on a set of data channels is scheduled by the control information; and sending the HARQ feedback information to the network device via the control channel. In this way, an enhancement of the HARQ‑ACK feedback mechanism for the terminal device can be achieved when multiple TBs / independent PDSCHs are scheduled by a single DCI, which can mitigate possible PUCCH conflicts and provide greater flexibility.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to methods, devices, and computer-readable storage media for hybrid automatic repeat request (HARQ) feedback for multiple data channels scheduled by a single downlink control information (DCI). Background Art

[0002] In the 3rd Generation Partnership Project (3GPP) Release 17 (Rel-17), due to the limited capacity of the Physical Downlink Control Channel (PDCCH) of Reduced Capability NR Devices, scheduling multiple Transport Blocks (TBs) / Physical Downlink Shared Channels (PDSCHs) through a single DCI has been considered.

[0003] For reduced capability NR devices, it has been proposed that the bandwidth of the user equipment (UE) can be reduced to 5 MHz or 10 MHz and PDCCH monitoring can be reduced through a smaller number of blind decoding and CCE restriction, which may result in PDCCH capacity being limited to the reduced bandwidth.

[0004] Therefore, a HARQ feedback scheme for multiple TB / PDSCHs scheduled by a single DCI can be discussed. Summary of the Invention

[0005] In general, example embodiments of the present disclosure provide a solution for HARQ feedback of multiple data channels scheduled by a single DCI.

[0006] In a first aspect, a communication method is provided. The method includes receiving control information at a terminal device from a network device; determining, based on determining that transmission of multiple transport blocks from the network device to the terminal device on a set of data channels is scheduled by the control information, a control channel for transmitting hybrid automatic repeat request (HARQ) feedback information associated with the multiple 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, comprising sending control information from a network device to a terminal device, wherein transmission of a plurality of transport blocks from the network device to the terminal device over a set of data channels is scheduled by the control information; and receiving hybrid automatic repeat request (HARQ) feedback information associated with the plurality of transport blocks from the terminal device via the control channel.

[0008] In a third aspect, a terminal device is provided. The terminal device includes a processor and a memory storing instructions. The memory and the instructions are configured to, together with the processor, cause the terminal device to execute the method according to the first aspect.

[0009] In a fourth aspect, a network device is provided. The network device includes a processor and a memory storing instructions. The memory and the instructions are configured to, together with the processor, cause the network device to execute the method according to the second aspect.

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

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

[0012] Other features and advantages of the embodiments of the present disclosure will also be apparent from the following description of the specific embodiments when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The embodiments of the present disclosure are given in an exemplary sense, and their advantages will be explained in more detail below with reference to the accompanying drawings, in which

[0014] Figure 1 shows an example environment in which example embodiments of the present disclosure may be implemented;

[0015] Figure 2 shows an example signaling diagram illustrating an example process for resource coordination according to some embodiments of the present disclosure;

[0016] Figure 3 shows multiple PDSCHs scheduled by a single DCI and a PUCCH on which HARQ feedback associated with the multiple PDSCHs is to be sent according to some embodiments of the present disclosure;

[0017] Figure 4A 、 Figure 4B The construction of a codebook for HARQ feedback according to some embodiments of the present disclosure is shown;

[0018] Figure 5A 、 Figure 5B The construction of a codebook for HARQ feedback according to some embodiments of the present disclosure is shown;

[0019] Figures 6A to 6C The construction of a codebook for HARQ feedback according to some embodiments of the present disclosure is shown;

[0020] Figure 7 A flowchart illustrating an example method for HARQ feedback for multiple data channels scheduled by a single DCI according to some example embodiments of the present disclosure is shown;

[0021] Figure 8 A flowchart illustrating an example method for HARQ feedback for multiple data channels scheduled by a single DCI according to some example embodiments of the present disclosure; and

[0022] Figure 9 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown.

[0023] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0024] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described only to illustrate and help those skilled in the art understand and implement the present disclosure, and do not represent any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various other ways in addition to the way described below.

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

[0026] In this disclosure, references to "one embodiment," "an embodiment," and "an example embodiment" indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an example embodiment, those skilled in the art believe that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0027] It should be understood that although the terms "first" and "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are merely used to distinguish the functions of the various elements. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0028] The terms used herein are for describing particular embodiments only and are not intended to limit the example embodiments. As used herein, the singular forms "a," "an," and "the" also include the plural forms, unless the context clearly indicates otherwise. It is further understood that the terms "comprises," "comprising," "has," "having," "includes," and / or "including" when used herein specify the presence of stated features, elements, and / or components, etc., but do not preclude 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 that complies with any suitable communication standard, such as a fifth generation (5G) system, long term evolution (LTE), advanced LTE (LTE-A), wideband code division multiple access (WCDMA), high speed packet access (HSPA), narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to any suitable generation communication protocol, 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 wireless (NR) communication protocol, and / or any other protocol currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communications, there will certainly be future types of communication technologies and systems that can implement the present disclosure. The scope of the present disclosure should not be limited to the above-mentioned systems.

[0030] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services from the network. A network device may refer to a base station (BS) or an access point (AP), for example, a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR next-generation NodeB (gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a repeater, a low-power node (such as a femto station, a pico station), etc., depending on the terminology and technology applied.

[0031] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, 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 the context of industrial and / or automated process chains), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminating (MT) portion of an integrated access 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 in various example embodiments, the functionality described herein may be performed in fixed and / or wireless network nodes, in other example embodiments, the functionality may be implemented in a user equipment device (such as a mobile phone or tablet or laptop or desktop computer or mobile IoT device or fixed IoT device). For example, the user equipment device may be appropriately equipped with corresponding capabilities as described in conjunction with fixed and / or wireless network nodes. The user equipment device may be a user device and / or a control device, such as a chipset or processor, that is configured to control the user device when installed in the user device. Examples of such functionality include boot server functionality and / or a home subscriber server, which may be implemented in the user equipment device by providing software to the user equipment device that is configured to cause the user equipment device to perform from the perspective of these functions / nodes.

[0033] Figure 1 1 shows an example communication network 100 in which embodiments of the present disclosure may be implemented. Figure 1 As shown, the communication network 100 includes a terminal device 110 and a network device 120. The terminal device 110 can communicate with the network device 120. It should be understood that Figure 1The number of network devices and terminal devices shown is given for illustrative purposes and does not imply any limitation. Communication network 100 may include any suitable number of network devices and terminal devices.

[0034] Depending on the communication technology, network 100 can 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 any other network. The communications discussed in network 100 can conform to any suitable standard, including but not limited to new radio access (NR), long term evolution (LTE), LTE evolution, advanced LTE (LTE-A), wideband code division multiple access (WCDMA), code division multiple access (CDMA), cdma2000, and global system for mobile communications (GSM). In addition, communications can be performed according to any generation of communication protocols currently known or to be developed in the future. Examples of communication 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) communication protocols. The technology described herein can be used for the above-mentioned wireless networks and radio technologies, as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below for LTE, and LTE terminology is used in much of the description below.

[0035] As mentioned above, in the 3rd Generation Partnership Project (3GPP) Release 17 (Rel-17), due to the limited capacity of the Physical Downlink Control Channel (PDCCH) of reduced-capability NR devices, scheduling multiple transport blocks (TBs) / physical downlink shared channels (PDSCHs) through a single DCI has been considered.

[0036] In addition to scenarios with reduced capability NR devices, scheduling of multiple transport blocks (TBs) / physical downlink shared channels (PDSCHs) via a single DCI may be considered in at least one of the following cases: NR multiple-input multiple-output (MIMO), NR sidelink enhancements; NR above 52.6 GHz; extending NR operation to 71 GHz; enhanced ultra-reliable low-latency communications (eURLLC) / eIIoT (enterprise industrial IoT); non-terrestrial networks (NTN); narrowband IoT (NB-IoT) over NTN / enhanced machine type communications (eMTC); UE energy saving enhancements; NR coverage enhancements; NB-IoT and LTE-MTC; integrated access backhaul (IAB); NR multicast and broadcast services, and enhancements to multi-radio dual connectivity.

[0037] For reduced-capability NR devices, it has been proposed that the bandwidth of the user equipment (UE) can be reduced to 5MHz or 10MHz and PDCCH monitoring can be reduced through a smaller number of blind decodes and CCE restrictions, which may result in PDCCH capacity being limited by the reduced bandwidth. The table below shows the number of PDCCHs for a 10MHz bandwidth and 30KHz / 15KHz subcarrier spacing, which may indicate that the PDCCH capacity is limited due to the bandwidth reduction.

[0038] Table 1: PDCCH capacity is limited due to bandwidth reduction

[0039]

[0040] The term "HARQ-ACK timing K 1，k " can be referred to as a time window from the reception of downlink data to the transmission of UL acknowledgment. For example, HARQ-ACK timing can be indicated via radio resource control (RRC) signaling or control information (i.e., downlink control information (DCI)).

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

[0042] It has been specified that bits 1 to 3 in the PDSCH-to-HARQ_feedback timing indicator field in the DL DCI are used to indicate one of the timing value set K1. The mapping of the PDSCH-to-HARQ_feedback timing indicator field value to the number of time slots can be as follows:

[0043] Table 2: Mapping of PDSCH-to-HARQ_feedback timing indicator field values ​​to slot numbers

[0044]

[0045]

[0046] There are two types of codebooks used for HARQ feedback in licensed spectrum: Type 1 HARQ-ACK codebook and Type 2 HARQ-ACK codebook. Type 1 HARQ-ACK codebook can be considered a semi-static codebook, while Type 2 HARQ-ACK codebook can be considered a dynamic codebook.

[0047] The Type 1 HARQ-ACK codebook is determined based on factors such as the PDSCH-to-HARQ_feedback timing value K1, the PDSCH time domain resource allocation (TDRA) table, the downlink SCS configuration μ if different numerologies are configured for DL ​​and UL. DL With uplink SCS configuration μ UL The ratio between and TDD configuration through TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated.

[0048] In a conventional manner, the HARQ-ACK window size may be determined based on a set of HARQ-ACK timing values, K1. Then, for each HARQ-ACK timing value in the set K1, the candidate PDSCH reception timing in each time slot may be determined based on the TDRA table and the TDD configuration. The candidate PDSCH reception timings in the time domain RA table that overlap with the UL configured by TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated are excluded, and for the overlapping candidate PDSCH reception timings, only one HARQ-ACK bit is generated based on a specific rule. When the PDSCH reception timing is determined, the type 1 HARQ-ACK codebook may be determined based on the PDSCH reception timing.

[0049] The type 2 HARQ-ACK codebook is determined based on the counter DAI and the total DAI in the scheduling DCI, where the HARQ-ACK for the PDSCH scheduled by the DCI pointing to the same time slot for PUCCH transmission is mapped to the same HARQ-ACK codebook. First, a set of DCIs for scheduling PDSCH reception can be determined, and the terminal device sends this set of DCIs based on the HARQ-ACK information in the same PUCCH in time slot n. Then, the codebook size and the HARQ-ACK information bit order can be determined based on parameters such as the counter DAI in the DL DCI format, the total DAI in DCI format 1_1 / DCI format 1_2, maxNrofCodeWordsScheduledByDCI, harq-ACK-SpatialBundlingPUCCH and PDSCH-CodeBlockGroupTransmission.

[0050] In the case where multiple TBs / PDSCHs are scheduled by a single DCI, the conventional HARQ-ACK feedback mechanism of one PDCCH for scheduling a single TB / or two TBs in the spatial domain cannot be directly reused.

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

[0052] The following will refer to Figure 2 The principles and implementations of the present disclosure are described in detail. For the purpose of discussion, reference will be made to Figure 1 Describe process 200. Process 200 may involve Figure 1 The terminal device 110 and the network device 120 are shown.

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

[0054] Then, the terminal device 120 may first determine 220 a control channel for sending HARQ-ACK feedback information, i.e., PUCCH. The terminal device 110 may determine 220 a control channel for sending HARQ-ACK feedback information based on the HARQ-ACK timing value K indicated by the scheduling DCI. 1，k To determine the time slot / sub-time slot for PUCCH transmission. 1，k It is the time from the slot / subslot of the last PDSCH reception in the time domain among multiple PDSCHs to the slot / subslot of UL acknowledgement transmission.

[0055] Figure 3 Multiple PDSCHs scheduled by a single DCI and a PUCCH on which HARQ feedback associated with the multiple PDSCHs is to be sent are shown according to some embodiments of the present disclosure.

[0056] like Figure 3 As shown, PDCCH 311 may be transmitted in time slot 301, from which DCI may be received. DCI may schedule a first PDSCH 312 to be transmitted in time slot 302 and a second PDSCH 313 to be transmitted in time slot 303. To determine the time slot for PUCCH transmission, terminal device 110 may obtain the HARQ-ACK timing value K from the DCI. 1，k , which indicates the slot / subslot received from the last PDSCH in the time domain among multiple PDSCHs (i.e., Figure 3 The time from the time slot 303 shown in FIG1 to the time of transmission of the UL confirmation. 1， If k=2, the time slot 305 may be determined for transmission of the PUCCH 314 .

[0057] In some embodiments, the value range of the HARQ-ACK timing set K1 (also called d1-DataToUL-ACK) (e.g., the maximum K 1，k ) can be extended to 31 or 63. If the terminal device 110 receives N independent PDSCHs scheduled by the DCI format from time slots n-N+1 to N, the terminal device 110 shall report the corresponding HARQ-ACK information of the PDSCH in the PUCCH in time slot n+k, where k is indicated by the value of the PDSCH-to-HARQ_feedback timing indicator field in the DCI format.

[0058] To report HARQ-ACK feedback information for each PDSCH, the terminal device 110 may also determine a feedback mode for indicating the HARQ-ACK information. The determination of the feedback mode may depend on the reporting mode of the HARQ-ACK feedback information and the type of HARQ-ACK codebook used.

[0059] 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 determine corresponding HARQ feedback values ​​for multiple TBs on different PDSCHs and generate bundled HARQ feedback by performing a logical operation (such as an AND operation) on the corresponding HARQ feedback values. An example of an AND operation for multiple independent PDSCHs may be as follows:

[0060] Table 3: AND operation for multiple independent PDSCHs

[0061]

[0062]

[0063] For example, returning a reference Figure 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 one-bit HARQ-ACK value and reported in the PUCCH 314. For example, if the first PDSCH 312 is ACK and the second PDSCH 313 is NACK, the one-bit HARQ-ACK value may be ACK(1)&NACK(0)=NACK(0).

[0064] In some embodiments, the terminal device 110 may also generate HARQ-ACK bits separately for each of the multiple PDSCHs and report these HARQ-ACK bits in the PUCCH. That is, the terminal device 110 may determine corresponding HARQ feedback values ​​for multiple TBs on different PDSCHs and report these HARQ feedback values ​​in the PUCCH.

[0065] A codebook for carrying HARQ-ACK feedback information, including a bundled one-bit HARQ-ACK value or a separate HARQ-ACK bit for each PDSCH, may then be selected and used as discussed further below. As described above, there are two types of HARQ-ACK feedback codebooks, namely, type 1 codebooks and type 2 codebooks.

[0066] In the case where the terminal device 110 generates one HARQ-ACK bit for multiple independent PDSCHs, if the terminal device 110 is configured with a type 1 HARQ-ACK codebook, then in some embodiments, the terminal device 110 does not expect to schedule multiple PDSCHs via DCI with different time domain resource allocations. That is, one HARQ-ACK position in the HARQ-ACK codebook is generated for the corresponding reception timings of TBs on different PDSCHs. The terminal device 110 may report one HARQ-ACK bit for multiple PDSCHs in the corresponding HARQ-ACK position in the type 1 HARQ-ACK codebook.

[0067] Figure 4A FIG. 4 shows the construction of a codebook for HARQ feedback according to some embodiments of the present disclosure. Figure 4A As shown, the reception timing of the TB on the PDSCH 411 in the time slot 401 starts from the 2nd symbol and the symbol length is 5, while the reception timing of the TB on the PDSCH 412 in the time slot 402 starts from the 2nd symbol and the symbol length is 5. Therefore, the reception timings of the PDSCH 411 and the PDSCH 412 can be considered to be the same.

[0068] As mentioned above, the type 1 HARQ-ACK codebook for multiple PDSCHs can be based on a HARQ-ACK timing value K 1，k The codebook mode can then be determined to indicate the codebook size, for example, how many reporting positions are involved in the codebook. Figure 4A As shown, the codebook may include reporting positions 421 to 426. For example, if the first PDSCH 411 is ACK and the second PDSCH 412 is NACK, the one-bit HARQ-ACK value may be ACK(1) & NACK(0) = NACK(0). Then, the value NACK(0) may be reported in position 423.

[0069] In some embodiments, multiple PDSCHs scheduled by DCI may have different SLIV allocations, then more than one HARQ-ACK position is associated with multiple PDSCHs in the HARQ-ACK codebook. In this case, if the terminal device reports only one HARQ-ACK bit for multiple PDSCHs in one of the HARQ-ACK positions associated with multiple PDSCHs in the HARQ-ACK codebook, the HARQ-ACK position may be determined, for example, based on a reception timing associated with one of the PDSCHs (e.g., the first PDSCH or the last PDSCH in the multiple PDSCHs in the time domain).

[0070] As another option, the HARQ-ACK position may also be determined based on the PDSCH reception with the smallest starting symbol / or the PDSCH with the longest duration or the PDSCH reception with the lowest / highest HARQ-ACK process ID.

[0071] That is, the terminal device 110 can select a reference TB from multiple TBs. The reference TB can be transmitted on the first / last PDSCH in the time domain, or at the reception timing of the reference TB with the smallest starting symbol, or at the reception timing of the reference TB with the longest duration, or at the reception timing with the lowest / highest HARQ-ACK process ID.

[0072] Figure 4B FIG. 4 shows the construction of a codebook for HARQ feedback according to some embodiments of the present disclosure. Figure 4B As shown, the reception timing of the TB on PDSCH 411 in time slot 401 starts from the 2nd symbol and the symbol length is 5, while the reception timing of the TB on PDSCH 412 in time slot 402 starts from the 9th symbol and the symbol length is 5. Therefore, it can be considered that the reception timings of PDSCH 411 and PDSCH 412 are different. Two HARQ-ACK positions 423 and 425 are generated for PDSCH 411 and PDSCH 412, respectively.

[0073] In this case, if terminal device 110 reports only a valid HARQ-ACK value in the HARQ-ACK position of the last PDSCH reception (i.e., PDSCH 412), then when ACK for PDSCH 411 and ACK for PDSCH 412, the valid HARQ-ACK value is ACK(1)&ACK(1)=ACK(1). Terminal device 110 then reports only ACK(1) in reporting position 425.

[0074] 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. Figure 4B In the example, the terminal device 110 may report NACK(0) in position 423.

[0075] In the case where the terminal device 110 generates HARQ-ACK bits separately for each of the multiple PDSCHs and reports these HARQ-ACK bits in the PUCCH, if the terminal device 110 is configured with a type 1 HARQ-ACK codebook, the type 1 HARQ-ACK codebook for the multiple PDSCHs determines the HARQ-ACK timing value K based on one HARQ-ACK timing value K.1，k , the reception timing of multiple TBs on multiple PDSCHs scheduled by DCI is the same.

[0076] However, if the current Type 1 HARQ-ACK codebook construction rule is followed, only one HARQ-ACK position is generated and the terminal device 110 cannot report all valid HARQ-ACK bits for multiple PDSCHs scheduled by the DCI.

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

[0078] Figure 5A FIG5 shows the construction of a codebook for HARQ feedback according to some embodiments of the present disclosure. As shown in FIG5, the reception timing on PDSCH 511 and PDSCH 512 is the same, and the type 1 HARQ-ACK codebook for PDSCH 511 and PDSCH 512 can be based on a HARQ-ACK timing value K having positions 521 to 527. 1，k To determine, two HARQ-ACK positions, namely, positions 523 and 524, can be generated for PDSCH 511 and PDSCH 512.

[0079] In some embodiments, the N HARQ-ACK positions for PDSCH in the codebook are arranged in ascending / descending order of HARQ-ACK process ID. As another option, the N HARQ-ACK positions for PDSCH in the codebook are arranged in order of earlier PDSCH reception priority.

[0080] If the terminal device 110 is configured with a Type 1 HARQ-ACK codebook, the Type 1 HARQ-ACK codebook determination for multiple PDSCHs may also be based on multiple virtual HARQ-ACK timing values. The virtual HARQ-ACK timing value for each PDSCH may be based on one HARQ-ACK timing value K indicated by the DCI. 1，k The time offset Δt is determined by the time gap between the current PDSCH reception and the last or first PDSCH reception.

[0081] Figure 5B FIG5 shows the construction of a codebook for HARQ feedback according to some embodiments of the present disclosure. As shown in FIG5 , the reception timings on PDSCH 511 and PDSCH 512 are the same. If the HARQ-ACK timing value K for PDSCH 512 is 1，k=2 and time offset Δt=1, then the virtual HARQ-ACK timing value for PDSCH 511 is K 1，k +Δt=3. For the determined type 1 HARQ-ACK codebook having positions 521 to 526 , a HARQ-ACK value for PDSCH 511 may be reported in position 521 , and the HARQ-ACK value may be reported in position 524 .

[0082] In the case where the terminal device 110 generates HARQ-ACK bits separately for each of multiple PDSCHs and reports these HARQ-ACK bits in the PUCCH, if the terminal device is configured with a type 2 HARQ-ACK codebook and the terminal device is configured with only one CC, then the HARQ-ACK information for multiple PDSCHs scheduled by DCI and the HARQ-ACK information for a single PDSCH scheduled by DCI / or two SDM-based PDSCHs are allowed to be multiplexed in the PUCCH.

[0083] In this case, for multiple PDSCHs scheduled by a single DCI, the counter DAI is accumulated. The bit width of the counter DAI field can be extended to x bits by the network device 120, for example, x=4, and the maximum value of c-DAI is 16. The HARQ-ACK positions in the type 2 codebook for these PDSCHs scheduled by the DCI can be the same as in the type 1 codebook in

[0070] .

[0084] Figure 6A The construction of a codebook for HARQ feedback according to some embodiments of the present disclosure is shown.

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

[0086] Therefore, in Figure 6A, HARQ-ACK values ​​for PDSCHs 621 , 622 , 623 , and 624 may be reported in positions 641 to 644 , respectively, and HARQ-ACK values ​​for PDSCH 625 and PDSCH 626 may be reported in positions 645 and 646 .

[0087] In some embodiments, if the terminal device is configured with a type 2 HARQ-ACK codebook and the terminal device is configured with only one CC, the HARQ-ACK information for multiple PDSCHs scheduled by DCI and the HARQ-ACK information for a single PDSCH scheduled by DCI / or two SDM-based PDSCHs are allowed to be multiplexed in the PUCCH. In this case, two sub-codebooks are constructed for the multiple PDSCHs scheduled by DCI and the single PDSCH scheduled 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.

[0088] Figure 6B The construction of a codebook for HARQ feedback according to some embodiments of the present disclosure is shown.

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

[0090] In some embodiments, if the terminal device is configured with a Type 2 HARQ-ACK codebook and the terminal device is configured with only one component carrier (CC), the HARQ-ACK information for multiple PDSCHs scheduled by DCI and the HARQ-ACK information for a single PDSCH / s or two SDM-based PDSCHs scheduled by DCI are allowed to be multiplexed in the PUCCH. In this case, the terminal device 110 may receive N HARQ-ACK positions generated for the PDSCH for each DL scheduling DCI. N is the maximum number of TBs scheduled by a single DCI, and N may be configured by RRC. For example, for a single PDSCH scheduled by DCI, the terminal device may report its valid HARQ-ACK value only in the first position among the N corresponding HARQ-ACK positions and report NACK in the other N-1 positions. For multiple PDSCHs scheduled by DCI, if M PDSCHs are scheduled (M < N), the terminal device may report M valid HARQ-ACK values only in the first M positions among the N corresponding HARQ-ACK positions, and report NACK in the other N-M positions.

[0091] Figure 6C The construction of a codebook for HARQ feedback according to some embodiments of the present disclosure is shown.

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

[0093] Therefore, 4 HARQ-ACK positions 641 to 644 may be generated to report the HARQ-ACK values of PDSCHs 621, 622, 623, and 624. 4 HARQ-ACK candidate positions 651 to 654 may be generated to report the HARQ-ACK value of PDSCH 625, and 4 HARQ-ACK candidate positions 661 to 664 may be generated to report the HARQ-ACK value of PDSCH 626.

[0094] As described above, the terminal device may report its valid HARQ-ACK value only in the first of the N corresponding HARQ-ACK positions and report NACK 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.

[0095] In this way, if the terminal device 110 determines the feedback mode for the HARQ-ACK feedback information, the reference Figure 2 , the terminal device 110 can send 230 HARQ-ACK information to the network device via the control channel based on the feedback mode.

[0096] Furthermore, regarding the processing timeline of HARQ feedback, the terminal device 110 does not expect the start symbol of PUCCH Tx for HARQ-ACK for multiple PDSCHs to be earlier than the end symbol of the last PDSCH received in the time domain in the multiple PDSCHs. As an option, the terminal device may only report HARQ-ACK information for PDSCHs that meet the processing timeline.

[0097] Whether the terminal device 110 is able to support / decode / receive unicast multiple TBs / individual TBs (also called multiple independent PDSCHs) scheduled by the PDCCH depends on the capabilities of the terminal device 110 .

[0098] If the terminal device 110 indicates the ability to receive / decode unicast multiple TBs scheduled by PDCCH, the maximum number of unicast TBs scheduled by PDCCH depends on the UE capability. For example, for separate capabilities of different maximum numbers of unicast TBs scheduled by PDCCH, a maximum of two unicast TBs can be scheduled by PDCCH, or a maximum of four unicast TBs can be scheduled by PDCCH.

[0099] The actual number of unicast TBs scheduled by PDCCH depends on the configuration of the network equipment. The terminal device can obtain this information in the following ways. For example, the information can be implicitly indicated by RRC or DCI. Alternatively, the information can be implicitly indicated by RRC and DCI. For example, the number of time domain resource allocations for each entry in the TDRA table. As another option, the information can be explicitly indicated by RRC or DCI. For example, an RRC parameter in the PDSCH configuration can be introduced, such as NrofTbsScheduledBySingleDCI, or a new indicator field can be used, or the current indicator field in the scheduling DCI can be reinterpreted, for example, 2 bits are used to indicate the number of unicast TBs, bit 00 can correspond to 1TB; bit 01 can correspond to 2TB; bit 10 can correspond to 3TB, and bit 11 can correspond to 4TB.

[0100] In this way, an enhancement of the HARQ-ACK feedback mechanism for the terminal device can be achieved when multiple TBs / independent PDSCHs are scheduled by a single DCI, which can alleviate possible PUCCH conflicts and provide more flexibility.

[0101] Figure 7 A flow chart illustrating an example method 700 for HARQ feedback of multiple data channels scheduled by a single DCI according to some example embodiments of the present disclosure is shown. The method 700 may be implemented in a manner such as Figure 1 For the purpose of discussion, reference will be made to the terminal device 110. Figure 1 Method 700 is described.

[0102] like Figure 7 As shown, at 710, the terminal device 110 receives control information from the network device.

[0103] At 720 , if the terminal device 110 determines that transmission of multiple transport blocks from the network device to the terminal device on a set of data channels is scheduled by the control information, the terminal device 110 determines a control channel for sending hybrid automatic repeat request HARQ feedback information associated with the multiple transport blocks.

[0104] In some example embodiments, 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 set of data channels. Terminal device 110 may also obtain a time window of HARQ feedback associated with the reference transport block from the control information, and determine the control channel based on the reference position and the time window.

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

[0106] In some example embodiments, the terminal device 110 may determine corresponding HARQ feedback values ​​of a plurality of transport blocks as the HARQ feedback information.

[0107] At 730 , the terminal device 110 sends HARQ feedback information to the network device via the control channel.

[0108] In some example embodiments, if terminal device 110 determines that a Type 1 HARQ-ACK codebook will be used to carry HARQ feedback information, terminal device 110 may determine the corresponding start (Start) and length indicator values ​​SLIV (Length Indicator Value) of multiple transport blocks on the group of data channels. If terminal device 110 determines that the corresponding SLIVs are the same, terminal device 110 may determine the feedback position in the Type 1 HARQ-ACK codebook based on the SLIVs and send the HARQ feedback information based on the feedback position.

[0109] In some example embodiments, if terminal device 110 determines that a Type 1 HARQ-ACK codebook is to be employed to carry HARQ feedback information, terminal device 110 may determine corresponding start and length indicator values ​​SLIV for a plurality of transport blocks on the group of data channels. If terminal device 110 determines that the corresponding SLIVs are different, terminal device 110 may determine a reference SLIV in the time domain corresponding to reception of a reference transport block among the plurality of transport blocks, and determine a feedback position in the Type 1 HARQ-ACK codebook based on the reference SLIV. Terminal device 110 may send HARQ feedback information based on the feedback position.

[0110] In some example embodiments, the terminal device 110 may determine a reference SLIV corresponding to the reception of the reference transport block based on at least one of: an index of a reference data channel used to send 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 the reception of the reference transport block.

[0111] In some example embodiments, if terminal device 110 determines that a type 1 HARQ-ACK codebook is to be adopted to carry HARQ feedback information, terminal device 110 may determine start and length indicator values ​​SLIV for a plurality of transport blocks on the set of data channels. If terminal device 110 determines that the corresponding SLIVs are the same, terminal device 110 may determine a plurality of feedback positions in the type 1 HARQ-ACK codebook for indicating corresponding HARQ feedback values ​​based on the corresponding SLIVs. Terminal device 110 may determine an order for reporting corresponding HARQ feedback values ​​at the plurality of feedback positions based on an index of a HARQ process associated with the plurality of transport blocks or an order in which the plurality of transport blocks on the set of data channels are received, and send the HARQ feedback information based on the plurality of feedback positions and the order.

[0112] In some example embodiments, if terminal device 110 determines that a type 1 HARQ-ACK codebook is to be used to carry HARQ feedback information, terminal device 110 may obtain from the control information a set of time offsets for a plurality of transport blocks associated with a time window for HARQ feedback associated with a reference transport block in the plurality of transport blocks. Terminal device 110 may determine, based on the time window and the set of time offsets, a plurality of feedback positions in the type 1 HARQ-ACK codebook for indicating corresponding HARQ feedback values, and send the HARQ feedback information based on the plurality of feedback information.

[0113] In some example embodiments, if the terminal device 110 determines that a type 2 HARQ-ACK codebook is to be adopted to carry the HARQ feedback information, the terminal device 110 may determine a codebook size of the type 2 HARQ-ACK codebook and a plurality of feedback positions in the type 2 HARQ-ACK codebook for indicating the corresponding HARQ feedback value and the additional HARQ feedback value (for the additional transport block sent from the network device to the terminal device on the additional data channel scheduled by the additional control information) based on the number of the group of data channels and the number of the additional data channels. The terminal device may determine an order for reporting the corresponding HARQ feedback value and the additional HARQ feedback value at the plurality of feedback positions based on an index of a HARQ process associated with the plurality of transport blocks and the additional transport blocks, or an order of reception of the plurality of transport blocks and the additional transport blocks on the group of data channels and the additional data channels, and send the HARQ feedback information based on the codebook size, the plurality of feedback positions, and the order.

[0114] In some example embodiments, if terminal device 110 determines that a type 2 HARQ-ACK codebook is to be adopted to carry HARQ feedback information, terminal device 110 may determine a codebook size for the type 2 HARQ-ACK codebook based on a threshold number of data channels that are allowed to be scheduled by the control information. The terminal device may determine, based on the threshold number, a first number of the group of data channels, and a second number of additional data channels, a plurality of feedback positions for indicating a corresponding HARQ feedback value and additional HARQ feedback values ​​for additional transport blocks, the additional transport blocks being sent from the network device to the terminal device on additional data channels scheduled by the additional control information, and send the HARQ feedback information based on the codebook size and the plurality of feedback positions and the additional feedback positions.

[0115] In some example embodiments, terminal device 110 may determine, based on a threshold number, a corresponding set of candidate feedback positions in a type-2 HARQ-ACK codebook that are allowed to report the corresponding HARQ feedback value and the additional HARQ feedback value. The terminal device may also determine, based on the threshold number and the first number, a first partial feedback position for reporting the corresponding HARQ feedback value on the corresponding set of candidate feedback positions, and determine, based on the threshold number and the second number, a second partial feedback position for reporting the additional HARQ feedback value, and determine a plurality of feedback positions based on the first partial feedback position and the second partial feedback position.

[0116] Figure 8 8. A flow chart illustrating an example method 800 for HARQ feedback of multiple data channels scheduled by a single DCI according to some example embodiments of the present disclosure is shown. The method 800 may be implemented in a manner such as Figure 1 For the purpose of discussion, reference will be made to the network device 120. Figure 1 Method 800 is described.

[0117] like Figure 8 As shown, at 810 , the network device 120 sends control information from the network device to the terminal device, and transmission of multiple transmission blocks from the network device to the terminal device on a group of data channels is scheduled by the control information.

[0118] At 820 , the network device 120 receives hybrid automatic repeat request (HARQ) feedback information associated with a plurality of transport blocks from the terminal device via the control channel.

[0119] Figure 9 is a simplified block diagram of a device 900 suitable for implementing embodiments of the present disclosure. The device 900 may be provided to implement a communication device, such as Figure 1The terminal device 110 and the network device 120 are shown. As shown, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processor 910, and one or more transmitters and / or receivers (TX / RX) 940 coupled to the processor 910.

[0120] The TX / RX 940 is used for bidirectional communication. The TX / RX 940 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.

[0121] Processor 910 can be of any type suitable for the local technology network and, as non-limiting examples, can include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 900 can have multiple processors, such as application-specific integrated circuit chips that are time-slave to a clock synchronized with a main processor.

[0122] 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) 924, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 922 and other volatile memories that do not persist during power outages.

[0123] Computer program 930 includes computer-executable instructions executed by associated processor 910. Program 930 may be stored in ROM 920. Processor 910 may perform any suitable actions and processes by loading program 930 into RAM 920.

[0124] The embodiment of the present disclosure can be implemented by the program 930 so that the device 900 can execute the reference Figures 2 to 8 The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

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

[0126] In general, various embodiments of the present disclosure may be implemented using hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented using hardware, while other aspects may be implemented using 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 are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented using hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0127] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as instructions included in a program module, which are executed in a device on a target real processor or a target virtual processor to perform the above-referenced Figure 7 Method 700 described, and reference Figure 8 Method 800 is described. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or split between program modules as needed. The machine-executable instructions of program modules can be executed on local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0128] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code causes the function / operation specified in the flow chart and / or block diagram to be realized when executed by the processor or controller. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0130] The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems or devices, or any suitable combination of the foregoing. More specific examples of computer readable storage media will include an electrical connection with one or more wires, a portable computer floppy disk, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0131] In addition, although operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in sequence or performing all of the operations shown to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details have been included in the above discussion, these should not be interpreted as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0132] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in 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 terminal device that communicates with a network device, the terminal device comprising: a receiver configured to receive a plurality of physical downlink shared channel (PDSCH) transmissions, the plurality of PDSCH transmissions being scheduled by downlink control information (DCI); a processor configured to determine a time slot for a physical uplink control channel (PUCCH) transmission for transmitting hybrid automatic repeat request (HARQ) feedback information associated with the plurality of PDSCH transmissions based on a first position and first information included in the DCI, the first information indicating a HARQ feedback timing value, the first position indicating a time slot for a last PDSCH transmission of the plurality of PDSCH transmissions; and A transmitter is configured to send the HARQ feedback information in the PUCCH transmission within the determined time slot.

2. The terminal device according to claim 1, wherein Type 1 HARQ-ACK codebook will be used to carry the HARQ feedback information.

3. The terminal device according to claim 2, wherein Based on the first feedback mode: In response to receiving a last PDSCH transmission associated with a last start and length indicator value SLIV, The processor is configured to determine bundled HARQ feedback values ​​for the plurality of PDSCH transmissions by using a binary AND operation, and The transmitter is configured to send the bundled HARQ feedback value as the HARQ feedback information in the PUCCH transmission within the determined time slot.

4. The terminal device according to claim 3, wherein The processor is configured to: determine corresponding start and length indicator values ​​SLIV for a plurality of transport blocks on the plurality of PDSCH transmissions; and Based on determining that the corresponding SLIVs are different, The processor is configured to: determine, in a time domain, a reference SLIV corresponding to reception of a reference transport block among the plurality of transport blocks; The processor is configured to: determine a feedback position in the type 1 HARQ-ACK codebook based on the reference SLIV; and The transmitter is configured to send the HARQ feedback information based on the feedback position.

5. The terminal device according to claim 4, wherein The processor is configured to determine a last SLIV corresponding to the last PDSCH transmission based on at least one of: an index of the reference data channel used to send the last PDSCH transmission; the value of the start symbol indicated in said last SLIV; the value of the symbol length indicated in the last SLIV; and An index of a HARQ process associated with said reception of said last PDSCH transmission. The terminal device according to claim 1 , wherein Based on the second feedback mode: The processor is configured to: determine corresponding HARQ feedback values ​​for the plurality of PDSCH transmissions, and The transmitter is configured to: send the corresponding HARQ feedback value as the HARQ feedback information in the PUCCH transmission within the determined time slot based on a first offset.

7. The terminal device according to claim 6, wherein The processor is configured to: obtain, from control information, a set of time offsets for a plurality of transport blocks, the set of time offsets being associated with a time window for HARQ feedback associated with a reference transport block among the plurality of transport blocks; The processor is configured to: determine, based on the time window and the set of time offsets, a plurality of feedback positions in a type 1 HARQ-ACK codebook for indicating the corresponding HARQ feedback values; and The transmitter is configured to send the HARQ feedback information based on the multiple feedback positions.

8. The terminal device according to claim 6, wherein The first offset indicates a duration between a current PDSCH transmission and a last PDSCH transmission.

9. A method for a terminal device to communicate with a network device, the method comprising: receiving a plurality of physical downlink shared channel (PDSCH) transmissions, the plurality of PDSCH transmissions being scheduled by downlink control information (DCI); determining, based on a first position and first information included in the DCI, a time slot for a physical uplink control channel (PUCCH) transmission for transmitting hybrid automatic repeat request (HARQ) feedback information associated with the plurality of PDSCH transmissions, wherein the first information indicates a HARQ feedback timing value and the first position indicates a time slot for a last PDSCH transmission in the plurality of PDSCH transmissions; and The HARQ feedback information is sent in the PUCCH transmission within the determined time slot.

10. The method according to claim 9, wherein Type 1 HARQ-ACK codebook will be used to carry the HARQ feedback information.

11. The method according to claim 10, further comprising: Based on the first feedback mode: In response to receiving a last PDSCH transmission associated with a last start and length indicator value SLIV, The method comprises: determining bundled HARQ feedback values ​​for the plurality of PDSCH transmissions by using a binary AND operation, and The bundled HARQ feedback value is sent as the HARQ feedback information in the PUCCH transmission within the determined time slot.

12. The method according to claim 11, wherein the sending the HARQ feedback information comprises: determining corresponding start and length indicator values ​​SLIV for a plurality of transport blocks on the plurality of PDSCH transmissions; as well as determining, in the time domain, a reference SLIV corresponding to reception of a reference transport block among the plurality of transport blocks based on determining that the corresponding SLIVs are different; determining, based on the reference SLIV, a feedback position in the type 1 HARQ-ACK codebook; as well as The HARQ feedback information is sent based on the feedback position.

13. The method of claim 12, wherein determining a reference SLIV comprises: Determining a last SLIV corresponding to the last PDSCH transmission based on at least one of: an index of the reference data channel used to send the last PDSCH transmission; the value of the start symbol indicated in said last SLIV; the value of the symbol length indicated in the last SLIV; and An index of a HARQ process associated with said reception of said last PDSCH transmission.

14. The method according to claim 9, wherein Based on the second feedback mode: The method comprises: determining corresponding HARQ feedback values ​​for the plurality of PDSCH transmissions, and Based on a first offset, the corresponding HARQ feedback value is sent in the PUCCH transmission within the determined time slot as the HARQ feedback information.

15. The method according to claim 14, wherein the sending the HARQ feedback information comprises: obtaining, from control information, a set of time offsets for a plurality of transport blocks, the set of time offsets being associated with a time window for HARQ feedback associated with a reference transport block among the plurality of transport blocks; determining, based on the time window and the set of time offsets, a plurality of feedback positions in a type 1 HARQ-ACK codebook for indicating the corresponding HARQ feedback values; and The HARQ feedback information is sent based on the multiple feedback positions.

16. The method according to claim 14, wherein The first offset indicates a duration between a current PDSCH transmission and a last PDSCH transmission.

Images