Communication method, device and computer storage medium

Abstract

The embodiments of the present disclosure relate to a method, an apparatus, and a computer-readable medium for communication. A terminal device receives a plurality of first data transmissions scheduled by a first DCI and a second data transmission scheduled by a second DCI from a network device, and transmits to the network device a first HARQ feedback for the plurality of first data transmissions, the first HARQ feedback including a NACK for a first data transmission that collides with a configured uplink symbol among the plurality of first data transmissions, and a second HARQ feedback for the second data transmission. Thus, a rule for generating HARQ feedback for the plurality of data transmissions in the case of the collision is defined.

Description

[Technical Field]

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to a method, apparatus, and computer storage medium for communication during scheduling of multi-transmission time intervals (TTIs) with downlink control information (DCI) on a single downlink control channel. [Background technology]

[0002] Currently, to support New Radio (NR) from 52.6 GHz to 71 GHz, multi-TTI-based scheduling has been proposed, which schedules multiple physical uplink shared channels (PUSCHs) using one physical downlink control channel (PDCCH). This reduces control signaling overhead. Therefore, multi-TTI-based scheduling has been extended to scheduling multiple physical downlink shared channels (PDSCHs) with DCI on a single PDCCH.

[0003] It is now agreed to generate sub-codebooks for hybrid automatic repeat request (HARQ) feedback for multiple PDSCHs scheduled by a DCI and for a single PDSCH scheduled by another DCI, however, further details of the generation of the sub-codebooks are still incomplete. Summary of the Invention [Problem to be solved by the invention]

[0004] Generally, embodiments of the present disclosure provide a method, apparatus, and computer storage medium for communication during scheduling of multiple TTIs within a single downlink control channel. [Means for solving the problem]

[0005] In a first aspect, a method of communications is provided, the method including: receiving, in a terminal device, from a network device, a plurality of first data transmissions scheduled by a first DCI and a second data transmission scheduled by a second DCI; and transmitting, to the network device, first hybrid automatic repeat request (HARQ) feedback for the plurality of first data transmissions, the first HARQ feedback including negative acknowledgments (NACKs) for first data transmissions of the plurality of first data transmissions that collide with configured uplink symbols; and second HARQ feedback for the second data transmissions.

[0006] In a second aspect, a method of communication is provided, the method including: receiving, in a terminal device, a plurality of data transmissions scheduled by DCI from a network device; grouping the plurality of data transmissions based on a number of groups configured for the terminal device; and transmitting HARQ feedback generated for the grouped data transmissions to the network device.

[0007] In a third aspect, a method of communication is provided, the method including: receiving, in a terminal device, from a network device, DCI scheduling a plurality of data transmissions, the DCI indicating a plurality of parameters for the plurality of data transmissions, each of the plurality of parameters having a single value, the single value indicating a slot gap between a first slot of a corresponding data transmission and a second slot of a previous data transmission, the single value further indicating information regarding a starting position and a length of a time domain resource for the corresponding data transmission on the first slot; and determining the time domain resource for the corresponding data transmission based on each of the plurality of parameters.

[0008] In a fourth aspect, a method of communication is provided, the method including: transmitting, in a network device, a plurality of first data transmissions scheduled by a first DCI and a second data transmission scheduled by a second DCI to a terminal device; and receiving, from the terminal device, first HARQ feedback for the plurality of first data transmissions, the first HARQ feedback including a NACK for a first data transmission among the plurality of first data transmissions that collides with a configured uplink symbol, and second HARQ feedback for the second data transmission.

[0009] In a fifth aspect, a method of communication is provided, the method including: transmitting, in a network device, a plurality of data transmissions scheduled by a DCI to a terminal device; and receiving, from the terminal device, HARQ feedback for the plurality of data transmissions grouped based on a number of groups configured for the terminal device.

[0010] In a sixth aspect, a method of communication is provided, the method including: transmitting, in a network device, to a terminal device, DCI for scheduling a plurality of data transmissions, the DCI indicating a plurality of parameters for the plurality of data transmissions, each of the plurality of parameters having a single value, the single value indicating a slot gap between a first slot of a corresponding data transmission and a second slot of a previous data transmission, the single value further indicating information regarding a starting position and a length of a time domain resource of the corresponding data transmission on the first slot.

[0011] In a seventh aspect, a terminal device is provided, the terminal device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the terminal device to perform the method according to the first aspect of the present disclosure.

[0012] In an eighth aspect, a terminal device is provided, the terminal device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the terminal device to perform the method according to the second aspect of the present disclosure.

[0013] In a ninth aspect, there is provided a terminal device, the terminal device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the terminal device to perform the method according to the third aspect of the present disclosure.

[0014] In a tenth aspect, there is provided a network device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the network device to perform the method according to the fourth aspect of the present disclosure.

[0015] In an eleventh aspect, there is provided a network device, the network device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the network device to perform the method according to the fifth aspect of the present disclosure.

[0016] In a twelfth aspect, there is provided a network device, the network device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the network device to perform the method according to the sixth aspect of the present disclosure.

[0017] In a thirteenth aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to any one of the first, second and third aspects of the present disclosure.

[0018] In a fourteenth aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to any one of the fourth, fifth and sixth aspects of the present disclosure.

[0019] Other features of the present disclosure will be readily apparent from the following description. [Brief explanation of the drawings]

[0020] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description of several embodiments of the present disclosure in the accompanying drawings.

[0021] [Figure 1] FIG. 1 illustrates an exemplary communication network in which some embodiments of the present disclosure may be implemented.

[0022] [Figure 2A]FIG. 2 is a schematic diagram of a process for scheduling one downlink data channel with a single DCI according to an embodiment of the present disclosure.

[0023] [Figure 2B] FIG. 2 is a schematic diagram of a process for scheduling multiple data channels with a single DCI according to an embodiment of the present disclosure.

[0024] [Figure 2C] 1 is a schematic diagram of a process for scheduling multiple data channels with a single DCI in multiple serving cells according to an embodiment of the present disclosure.

[0025] [Figure 3] FIG. 10 is a schematic diagram illustrating a process for communication when one of multiple downlink data transmissions scheduled by a single DCI conflicts with a configured uplink symbol, according to an embodiment of the present disclosure.

[0026] [Figure 4] FIG. 10 is a schematic diagram illustrating a process for generating HARQ feedback for multiple downlink data transmissions scheduled by a single DCI when two of the transmissions collide with a configured uplink symbol, according to an embodiment of the present disclosure.

[0027] [Figure 5] 1 is a schematic diagram illustrating an exemplary scenario in which the uplink symbol configuration is such that only one of multiple downlink data transmissions is collision-free, according to an embodiment of the present disclosure; FIG.

[0028] [Figure 6] FIG. 1 is a schematic diagram illustrating an example time-domain bundling of HARQ feedback for multiple downlink data transmissions scheduled by a single DCI, according to an embodiment of the present disclosure.

[0029] [Figure 7] FIG. 10 is a schematic diagram illustrating another process for communication when time domain bundling is applied to multiple data transmissions scheduled by a single DCI, according to an embodiment of the present disclosure.

[0030] [Figure 8] FIG. 10 is a schematic diagram illustrating another process for communicating resources for multiple data transmissions scheduled by a single DCI, according to an embodiment of the present disclosure.

[0031] [Figure 9] FIG. 1 illustrates an exemplary communication method implemented in a terminal device, according to some embodiments of the present disclosure.

[0032] [Figure 10] FIG. 10 illustrates another exemplary communication method implemented in a terminal device, according to some embodiments of the present disclosure.

[0033] [Figure 11] FIG. 10 illustrates another exemplary communication method implemented in a terminal device, according to some embodiments of the present disclosure.

[0034] [Figure 12] FIG. 2 illustrates an exemplary communication method implemented in a network device, according to some embodiments of the present disclosure.

[0035] [Figure 13] FIG. 1 illustrates another exemplary communication method implemented in a network device, in accordance with some embodiments of the present disclosure.

[0036] [Figure 14] FIG. 1 illustrates another exemplary communication method implemented in a network device, in accordance with some embodiments of the present disclosure.

[0037] [Figure 15] FIG. 1 is a schematic block diagram of an apparatus suitable for implementing embodiments of the present disclosure.

[0038] In the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0039] The principles of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are provided for illustrative purposes only to assist those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from those described below.

[0040] 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 pertains.

[0041] As used herein, the term "terminal device" refers to any device capable of wireless or wired communication. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, Internet of Everything (IoE) devices, machine-type communication (MTC) devices, and in-vehicle devices for V2X communications. Here, the "X" in V2X refers to pedestrians, vehicles, or infrastructure / networks, or image capture devices such as digital cameras, gaming devices, music storage and playback devices, or Internet appliances that enable wireless or wired Internet access and browsing. The term "terminal device" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. Additionally, the term "network device" refers to a device capable of providing or hosting a cell or coverage area through which terminal devices can communicate. Examples of network devices include, but are not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a next generation Node B (gNB), a Transmission Reception Point (TRP), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a femto node, a pico node, or other low power node.

[0042] In one embodiment, a terminal device can connect to a first network device and a second network device. One of the first network device and the second network device may be a master node and the other a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to the different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device directly or via the first network device to the terminal device. In one embodiment, information related to the terminal device configuration configured by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration of the terminal device configured by the second network device may be transmitted to the terminal device directly from the second network device or via the first network device.

[0043] As used herein, the singular forms "a / an" and "the" include the plural forms unless the context clearly indicates otherwise. The term "comprises" and variations thereof should be understood as open-ended, meaning "including, but not limited to." The term "based on" should be understood as "based at least in part on." The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment." The term "another embodiment" should be understood as "at least one other embodiment." Terms such as "first," "second," etc. may refer to different or the same object. The following may include other explicit and implicit definitions.

[0044] In some instances, values, procedures, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to illustrate that choices may be made from among many functional alternatives used, and that such choices are not necessarily better, smaller, higher, or otherwise more preferred than other choices.

[0045] As described above, a sub-codebook is generated for HARQ feedback for each of multiple PDSCHs scheduled by a DCI and a single PDSCH scheduled by another DCI. However, if one or more of the multiple PDSCHs collide with the configured uplink symbols, research should be conducted on how to generate HARQ feedback for the multiple PDSCHs in this situation. Furthermore, if grouping of the multiple PDSCHs is considered to reduce the codebook size of the HARQ feedback for the multiple PDSCHs, research should be conducted on how to indicate and apply the number of groups for grouping. Additionally, for time domain resource assignment (TDRA) within a DCI scheduling multiple PDSCHs or PUSCHs, research should be conducted on how to indicate slot gaps if slot gaps are introduced between PDSCHs or PUSCHs.

[0046]

[0013] Embodiments of the present disclosure provide solutions to solve the above and other potential problems. In one aspect, for multiple data transmissions scheduled by a DCI and a single data transmission scheduled by another DCI, a first HARQ feedback for the multiple data transmissions and a second HARQ feedback for the single data transmission are generated and transmitted. If one of the multiple data transmissions collides with a configured uplink symbol, the first HARQ feedback includes a NACK for the one of the multiple data transmissions. Thus, a rule is defined for generating HARQ feedback for the multiple data transmissions in the above-described collision event.

[0047] In another aspect, for multiple data transmissions scheduled by DCI, the multiple data transmissions are grouped based on the number of groups configured for the terminal device, and HARQ feedback is generated and transmitted for the grouped data transmissions. In this way, the number of groups for grouping may be flexibly changed according to the number of data transmissions to be scheduled.

[0048] In yet another aspect, for multiple data transmissions scheduled by a DCI, multiple parameters for the multiple data transmissions are indicated in the DCI to indicate time domain resources for the multiple data transmissions, each of the multiple parameters having a single value indicating a slot gap between a first slot of the corresponding data transmission and a second slot of the previous data transmission, and information about the start position and length of the time domain resource of the corresponding data transmission on the first slot. In this way, there is no need to add a slot gap field or a unique slot offset to each start and length indicator (SLIV) in the TDRA.

[0049] The principles and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Communication Network Example

[0050] FIG. 1 is a schematic diagram of an exemplary communications network 100 in which embodiments of the present disclosure may be implemented. As shown in FIG. 1, communications network 100 may include terminal devices 110 and network devices 120. In some embodiments, terminal devices 110 may be served by network devices 120. It should be understood that the number of devices in FIG. 1 is given for illustrative purposes and does not imply any limitations on the present disclosure. Communications network 100 may include any suitable number of network devices and / or terminal devices suitable for implementing embodiments of the present disclosure.

[0051] 1, terminal device 110 may communicate with network device 120 via a channel, such as a wireless communication channel. Communications in communication network 100 may conform to any suitable standard, including, but not limited to, Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. Furthermore, communications may be performed according to any generation of communication protocols now known or 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.

[0052] In some embodiments, terminal device 110 may transmit uplink data to network device 120 via an uplink data channel transmission. For example, the uplink data channel transmission may be a PUSCH transmission. Of course, any other suitable format is also possible. In some embodiments, terminal device 110 may receive downlink data from network device 120 via a downlink data channel transmission. For example, the downlink data channel transmission may be a PDSCH transmission. Of course, any other suitable format is also possible.

[0053] In some embodiments, terminal device 110 may receive DCI, e.g., data transmission configuration, from network device 120 via a downlink control channel transmission. For example, the downlink control channel transmission may be a PDCCH transmission. Of course, any other suitable format is also possible. In some embodiments, terminal device 110 may transmit uplink control information (UCI), e.g., HARQ feedback information, to network device 120 via an uplink channel transmission. For example, the uplink channel transmission may be a PUCCH or PUSCH transmission. Of course, any other suitable format is also possible.

[0054] In some embodiments, the network device 120 may provide the terminal device 110 with multiple serving cells (not shown herein), such as a primary cell (PCell), a primary secondary cell (PSCell), a secondary cell (SCell), a special cell (sPCell), etc. Each of the serving cells may correspond to a CC. The terminal device 110 may transmit with the network device 120 via a CC. Of course, the terminal device 110 may transmit with the network device 120 via multiple CCs, for example, in the case of CA.

[0055] In some embodiments, network device 120 may schedule one downlink data channel according to a DCI on a single downlink control channel for terminal device 110. Figure 2A is a schematic diagram of a process 200A for scheduling one downlink data channel according to a single DCI according to an embodiment of the present disclosure. As shown in Figure 2A, one PDCCH schedules one PDSCH, and each PDSCH occupies one HARQ process number.

[0056] In some embodiments, the network device 120 may schedule multiple downlink data channels for the terminal device 110 using DCI on a single downlink control channel. FIG. 2B is a schematic diagram of a process 200B for scheduling multiple downlink data channels using a single DCI according to an embodiment of the present disclosure. As shown in FIG. 2B, one PDCCH 201 schedules five PDSCHs, i.e., PDSCHs #0 to #4. It should be understood that the number of PDSCHs scheduled in one PDCCH is not limited to the above example and may be any other integer greater than one. Although FIG. 2B illustrates one PDCCH scheduling multiple PDSCHs, the embodiments of the present disclosure are also applicable to one PDCCH scheduling multiple PUSCHs. For convenience, the following description will be given taking one PDCCH scheduling multiple PDSCHs as an example.

[0057] In some embodiments, network device 120 may schedule multiple downlink data channels for terminal device 110 using a single DCI across multiple serving cells. FIG. 2C is a schematic diagram illustrating a process 200C for scheduling multiple downlink data channels using a DCI across multiple serving cells according to an embodiment of the present disclosure. As shown in FIG. 2C, there are two serving cells, CC1 and CC2. In a monitoring occasion in CC1, one PDCCH 210 schedules six PDSCHs, i.e., PDSCHs #0 to #5, and indicates that HARQ feedback for the six PDSCHs is transmitted on the PUCCH / PUSCH 230. In the same monitoring occasion in CC2, one PDCCH 220 schedules eight PDSCHs, i.e., PDSCHs #0 to #7, and indicates that HARQ feedback for the eight PDSCHs is also transmitted on the PUCCH / PUSCH 230.

[0058] It should be understood that the number of PDSCHs scheduled within one PDCCH is not limited to the above example, but can be any other integer greater than 1 and less than 9.

[0059] In some embodiments, a Type-2 HARQ-acknowledgement (HARQ-ACK) codebook may be generated for HARQ feedback for one or more data transmissions scheduled by a single DCI. In some embodiments in which a counter-downlink assignment index (c-DAI) or a total DAI (t-DAI) is counted for each DCI during generation of the Type-2 HARQ-ACK codebook, a sub-codebook (also referred to as a first codebook for convenience) may be generated for the multiple data transmissions scheduled by the single DCI, and another sub-codebook (also referred to as a second codebook for convenience) may be generated for the one data transmission scheduled by another single DCI. Example implementation of HARQ feedback for data transmissions scheduled within DCI

[0060] In some scenarios, one or more of the PDSCHs scheduled by a single DCI may collide with one or more configured uplink symbols indicated by, for example, a time division duplexing (TDD) configuration, in which case it is unclear how to place the HARQ-ACK bits in the first codebook.

[0061] In view of this, embodiments of the present disclosure provide a solution for generating HARQ feedback for one or more data channels via a single DCI, which will be described in detail with reference to FIGS. 3 to 5. FIG. 3 is a schematic diagram illustrating a process 300 for communication when one of multiple downlink data transmissions scheduled by a single DCI conflicts with a configured uplink symbol according to an embodiment of the present disclosure. For illustrative purposes, the process 300 will be described with reference to FIG. 1. The process 300 may involve the terminal device 110 and the network device 120 shown in FIG. 1.

[0062] 3, network device 120 may transmit one or more data transmissions to terminal device 110 (310). In some embodiments, network device 120 may transmit multiple data transmissions (also referred to herein as first data transmissions for convenience) scheduled by a single DCI (also referred to herein as first DCI for convenience) to terminal device 110. In some embodiments, network device 120 may transmit a data transmission (also referred to herein as second data transmissions for convenience) scheduled by a single DCI (also referred to herein as second DCI for convenience) to terminal device 110.

[0063] Upon receiving the one or more data transmissions, terminal device 110 may generate HARQ feedback for the one or more data transmissions (320). In some embodiments in which the plurality of first data transmissions and the second data transmission are received by terminal device 110, terminal device 110 may generate first HARQ feedback for the plurality of first data transmissions and second HARQ feedback for the second data transmission. If a configured uplink symbol indicates that a first data transmission of the plurality of first data transmissions collides (i.e., the first data transmission is unavailable), terminal device 110 may generate first HARQ feedback including a NACK for the first data transmission. In other words, if a configured uplink symbol indicates that at least one data transmission of the plurality of first data transmissions collides, terminal device 110 may generate first HARQ feedback including at least one NACK for the at least one colliding data transmission. In relation to the first and second embodiments, an example of the arrangement of NACK in the first HARQ feedback will be described. Embodiment 1

[0064] In this embodiment, the terminal device 110 may generate a first codebook for the first HARQ feedback, the first codebook including a NACK in an HARQ-ACK bit position corresponding to a scheduled position for the first colliding data transmission. In other words, the first codebook may include at least one NACK in at least one HARQ-ACK bit position corresponding to at least one scheduled position for the at least one colliding data transmission.

[0065] For example, when generating a Type-2 HARQ-ACK codebook corresponding to a DCI that can schedule multiple PDSCHs, terminal device 110 may need to report a fixed number of HARQ-ACK bits for each DCI that schedules multiple PDSCHs in the first codebook. If a collision exists between any of the scheduled PDSCHs of a single DCI and one or more uplink symbols indicated by the TDD configuration, when generating a fixed number of HARQ-ACK payloads, terminal device 110 simply pads NACKs for invalid collision slots without changing their positions in the TDRA table. For clarity, an example will be described in detail with reference to FIG. 4.

[0066] FIG. 4 is a schematic diagram illustrating a process 400 for generating HARQ feedback for multiple downlink data transmissions scheduled by a single DCI when two of the transmissions collide with a configured uplink symbol, according to an embodiment of the present disclosure.

[0067] As shown in Figure 4, there are two serving cells CC1 and CC2 (also referred to herein as cell 0 and cell 1). In PDCCH monitoring occasion #0, PDCCH 410 in CC1 schedules six PDSCHs, i.e., PDSCHs #0 to #5, and indicates that HARQ feedback for the six PDSCHs is transmitted on PUCCH / PUSCH 430. In the same monitoring occasion, PDCCH 420 in CC2 schedules eight PDSCHs, i.e., PDSCHs #0 to #7, and indicates that HARQ feedback for the eight PDSCHs is also transmitted on PUCCH / PUSCH 430.

[0068] 4, PDSCH#3 and PDSCH#4 in CC1 and CC2 collide with uplink symbols 441 and 442 indicated in TDD configuration 440 for terminal device 110. The HARQ codebook may be compiled based on the table represented by 450. In this example, CC1 is configured to have a TDRA table in which the maximum number of SLIVs in any row is equal to 6, and CC2 is configured to have a TDRA table in which the maximum number of SLIVs in any row is equal to 8. In this case, the fixed number of HARQ-ACK bits across all serving cells corresponding to DAI is max(6,8).

[0069] In some embodiments, terminal device 110 pads NACKs for invalid collision slots. That is, terminal device 110 may pad HARQ-ACK bit positions corresponding to the scheduled positions of PDSCH #3 and PDSCH #4 with NACKs. Additionally, to avoid codebook size mismatch, terminal device 110 may pad the last two HARQ-ACK bit positions for CC1 with NACKs. Thus, terminal device 110 may generate HARQ codebook 460 including HARQ-ACK bit 461 for CC1 and HARQ-ACK bit 462 for CC2. Embodiment 2

[0070] In this embodiment, the terminal device 110 may generate a first codebook for the first HARQ feedback, the first codebook including a NACK after HARQ-ACK bits for actual data transmissions excluding colliding first data transmissions (i.e., one or more colliding data transmissions) among the plurality of first data transmissions. In other words, when generating a fixed number of HARQ-ACK payloads, the terminal device 110 pads NACKs for invalid collision slots, and actual PDSCHs scheduled by a single DCI are counted first, followed by invalid (omitted) slots.

[0071] 4, the fixed number of HARQ-ACK bits across all serving cells corresponding to DAI is max(6,8). Then, terminal device 110 may pad NACKs for invalid collision slots and place them after valid slots. Thus, terminal device 110 may generate HARQ codebook 470 including HARQ-ACK bits 471 for CC1 and HARQ-ACK bits 472 for CC2.

[0072] Thus, rules for NACK placement for colliding data transmissions may be defined.

[0073] In some scenarios, only one of the multiple data transmissions scheduled by a single DCI does not collide with the configured uplink symbol, i.e., other data transmissions among the multiple data transmissions collide with the configured uplink symbol. The generation of HARQ feedback in this case will be described in detail in relation to embodiment 3 and embodiment 4. Embodiment 3

[0074] FIG. 5 is a diagram illustrating an example scenario 500 in which only one of multiple downlink data transmissions does not collide with a configured uplink symbol, according to an embodiment of the present disclosure.

[0075] For example, assume the TDRA table is shown in Table 1. TIFF0007775903000001.tif37150

[0076] For example, the terminal device 110 is scheduled with index 1 or index 2. However, one or more PDSCHs among the multiple PDSCHs scheduled by one DCI collide with the uplink symbol indicated by tdd-UL-DL-Configuration Common or tdd-UL-DL-Configuration Dedicated, and only one PDSCH is actually scheduled within that DCI. As shown in FIG. 5, PDSCHs #1 to #3 within CC1 collide with the configured uplink symbols. In this case, only one PDSCH #0 is actually scheduled within the corresponding DCI.

[0077] In this embodiment, one PDSCH #0 may still belong to the first codebook for multiple PDSCHs scheduled in a single DCI. In this case, the terminal device 110 may generate a first codebook for the multiple PDSCHs scheduled by the first DCI and a second codebook for the single PDSCH scheduled by the second DCI, and the first HARQ feedback includes HARQ feedback for PDSCH #0 and NACKs for the other data transmissions PDSCHs #1 to #3.

[0078] It should be noted that the example in Figure 4 is for illustrative purposes only and is not intended to limit the present disclosure, any other suitable method is also possible. Embodiment 4

[0079] As an alternative to embodiment 3, if only one of the multiple first data transmissions (e.g., PDSCH#0 in FIG. 5 ) does not collide with the configured uplink symbol, the PDSCH#0 may be changed to belong to a second codebook for a single PDSCH scheduled within a single DCI. In this case, for the multiple PDSCHs scheduled within the first DCI, terminal device 110 may generate first HARQ feedback including only HARQ feedback for PDSCH#0. For the single PDSCH scheduled within the second DCI, terminal device 110 may generate second HARQ feedback for the single PDSCH. Terminal device 110 may then generate a codebook having a set of c-DAI and t-DAI for the first HARQ feedback and the second HARQ feedback. In this way, the codebook size can be reduced and the corresponding overhead can be saved.

[0080] In some scenarios, time-domain bundling may be supported during generation of the first HARQ feedback for multiple PDSCHs scheduled by a single DCI. The size of the first codebook may be reduced by introducing grouping among the multiple PDSCHs. In some cases, the first codebook and the second codebook may be combined into one codebook. The generation of the first HARQ feedback and the second HARQ feedback in these cases will be described in detail in relation to embodiments 5 and 6. Embodiment 5

[0081] In this embodiment, terminal device 110 may generate the first HARQ feedback by grouping the plurality of first data transmissions (e.g., PDSCHs) into a plurality of groups, and may generate the second HARQ feedback by padding HARQ-ACK bits with NACKs so that the number of HARQ-ACK bits for the second HARQ feedback is equal to the number of HARQ-ACK bits for the first HARQ feedback. Terminal device 110 may then generate codebooks for the first feedback and the second feedback.

[0082] For example, the number of groups (also referred to herein as the grouping number) may be 2. For illustrative purposes, an example will be described with reference to FIG. 6. FIG. 6 is a schematic diagram illustrating exemplary time-domain bundling 600 of HARQ feedback for multiple downlink data transmissions scheduled by a single DCI according to an embodiment of the present disclosure. As shown in FIG. 6, PDCCH 610 schedules eight PDSCHs, namely, PDSCHs #0 to #7. PDSCHs #0 to #3 occupy group #0, and PDSCHs #4 to #7 occupy group #1. In this case, terminal device 110 may generate first feedback having two HARQ-ACK bits.

[0083] Assume that 1TB is supported by the serving cell of terminal device 110. In this case, terminal device 110 may generate second feedback having two HARQ-ACK bits, one of which is padded with a NACK. Thus, terminal device 110 may generate one codebook having a set of c-DAI and t-DAI for the first feedback and the second feedback.

[0084] It should be understood that any other suitable number is possible as the grouping number and the disclosure is not limited in this respect. Embodiment 6

[0085] In this embodiment, terminal device 110 may generate the first HARQ feedback by grouping the plurality of first data transmissions (e.g., PDSCHs) into a plurality of groups. The maximum number of transport blocks (TBs) supported by the serving cell of terminal device 110 is equal to the number of the plurality of groups. Terminal device 110 may then generate second HARQ feedback having the same number of HARQ-ACK bits as the first HARQ feedback. Terminal device 110 may then generate a codebook having sets of c-DAIs and t-DAIs for the first feedback and the second feedback.

[0086] For example, the number of groups may be 2. If any of the serving cells of terminal device 110 supports 2TB, terminal device 110 may generate a codebook having a set of c-DAIs and t-DAIs for the first feedback and the second feedback. It should be understood that any other suitable number is also possible as the number of groups, and the present disclosure is not limited in this respect.

[0087] 3, once the HARQ feedback for the one or more data transmissions is generated, the terminal device 110 transmits the HARQ feedback to the network device 120. Thus, the details of HARQ feedback in some special cases have been clarified, and the trade-off between UCI payload and HARQ feedback efficiency has been discovered. Implementation of HARQ feedback for grouped data transmissions

[0088] In some scenarios, if the c-DAI or t-DAI is counted for each DCI when generating the Type-2 HARQ-ACK codebook, it is assumed that the c-DAI or t-DAI design in Rel-16 is reused. To solve the codebook size mismatch problem, the terminal device 110 may report a fixed number of HARQ-ACK bits for each DCI that schedules multiple PDSCHs in the first codebook. If the fixed number is larger than the number of scheduled PDSCHs, redundancy is introduced in the codebook. Therefore, it is expected that the codebook size can be reduced by introducing PDSCH grouping among multiple scheduled PDSCHs. However, how to indicate and apply the grouping number needs to be discussed.

[0089] The embodiments of the present disclosure provide a solution for enhancing HARQ feedback for multiple downlink data channels scheduled by DCI on a single downlink control channel. According to the embodiments of the present disclosure, the multiple PDSCHs are grouped based on a configured number of groups, and HARQ feedback is generated for the grouped PDSCHs. This will be described in detail with reference to FIG. 7.

[0090] 7 is a schematic diagram illustrating another process 700 for communication when time domain bundling is applied to multiple data transmissions scheduled by a single DCI, according to an embodiment of the present disclosure. For illustrative purposes, process 700 will be described with reference to FIG. 1. Process 700 may involve terminal device 110 and network device 120 shown in FIG. 1.

[0091] 7, the network device 120 transmits multiple data transmissions scheduled by a single DCI to the terminal device 110 (710). Upon receiving the multiple data transmissions, the terminal device 110 groups the multiple data transmissions based on the number of groups configured for the terminal device 110 (720). Below, several examples of grouping will be described in relation to embodiments 7 to 9. Embodiment 7

[0092] In this embodiment, the number of groups may be commonly set for the serving cell of the terminal device 110. In this case, the network device 120 may set a common grouping number for the terminal device 110, and if the common grouping number is available, the terminal device 110 may apply the common grouping number across all serving cells that schedule multiple PDSCHs.

[0093] In some embodiments, the network device 120 may configure the number of groups to the terminal device 110 via an RRC message. For example, a set of group sizes may be configured as follows: TIFF0007775903000002.tif42137

[0094] It should be understood that the number of groups may be set via any other suitable method, and the present disclosure is not limited in this respect. Embodiment 8

[0095] In this embodiment, the number of groups may be set differently for each serving cell of the terminal device 110. In this case, the network device 120 may set a unique grouping number for each serving cell of the terminal device 110, and the grouping number is updated when a new cell capable of scheduling multiple PDSCHs is added.

[0096] In some embodiments, terminal device 110 may determine the maximum number of configured group numbers for serving cells that establish a connection with terminal device 110, and group the multiple data transmissions based on the maximum number. In other words, terminal device 110 may always use the maximum configured grouping number among all serving cells that establish a connection with terminal device 110. In this way, network device 120 may flexibly change the grouping number according to the TDRA table.

[0097] For example, serving cell #1 is configured to have a grouping number equal to 2, and serving cell #2 is configured to have another grouping number equal to 3. In this case, the grouping number across serving cells #1 and #2 corresponding to the DAI may be max(2,3). Then, serving cell #3 is added, i.e., terminal device 110 establishes a connection with serving cell #3. Since serving cell #3 is configured to have a new grouping number equal to 4, the grouping number across serving cells #1, #2, #3 corresponding to the DAI may be max(2,3,4).

[0098] In some embodiments, the network device 120 may configure the number of groups to the terminal device 110 via an RRC message. For example, a set of group sizes may be configured as follows: TIFF0007775903000003.tif42137

[0099] It should be understood that the number of groups may be set via any other suitable method, and the present disclosure is not limited in this respect. Embodiment 9

[0100] In this embodiment, the number of groups may be configured for each of the serving cells of the terminal device 110 (e.g., via an RRC message), and the terminal device 110 will not apply the group number to group the multiple data transmissions until an instruction to enable grouping is received.

[0101] In some embodiments, network device 120 may send an indication to terminal device 110 regarding whether grouping is enabled. Based on the indication, terminal device 110 may determine whether the group number applies to grouping. In some embodiments, network device 120 may send the indication via a medium access control (MAC) control element (CE). Of course, any other suitable method for sending the indication is possible, and the disclosure is not limited in this respect.

[0102] In some embodiments, network device 120 may transmit a first indication to enable grouping as the indication. In this case, terminal device 110 may group the multiple data transmissions in response to receiving the first indication. In some embodiments, if the configured number of groups is available, terminal device 110 may apply the configured number of groups across all serving cells that schedule multiple PDSCHs. In some embodiments, terminal device 110 may employ grouping enablement after time a, e.g., slot n+N, where n represents the slot index in which an ACK for the first indication is transmitted to network device 120 and N represents a fixed processing delay for processing the ACK in network device 120.

[0103] In some embodiments, network device 120 may transmit the second instruction to disable grouping as the instruction. For example, if network device 120 wants to stop PDSCH grouping for a HARQ codebook for multi-PDSCH scheduling, network device 120 may transmit the second instruction to terminal device 110. In response to receiving the second instruction, terminal device 110 may generate HARQ feedback for the multiple data transmissions without grouping the multiple data transmissions.

[0104] In this way, the network device 120 may adjust the codebook size according to variations in the uplink channel without adding any additional bits in the DCI.

[0105] 7, when the multiple data transmissions are grouped, terminal device 110 generates and transmits HARQ feedback for the grouped data transmissions (730), thereby reducing HARQ feedback overhead. Example of implementation of indication of slot gap between data transmissions

[0106] For operation at 480 KHz or 960 KHz sub-carrier spacing (SCS), the maximum number of scheduled data transmissions (e.g., PDSCS or PUSCH) may be up to 8. Rows of the TDRA table in the DCI may indicate scheduled data transmissions in contiguous or non-contiguous slots. It is unclear how to indicate non-contiguous slots in the TDRA table.

[0107] Table 1 below shows an exemplary TDRA table in the DCI that schedules one data transmission. TIFF0007775903000004.tif48150

[0108] The parameter K0 in Table 1 represents the offset between the scheduling slot corresponding to the scheduling PDCCH and the scheduled slot corresponding to the scheduled data transmission. The parameter SLIV in Table 1 represents the start position and length of the time domain resource for the scheduled data transmission within the scheduled slot.

[0109] For a TDRA table in a DCI that schedules multiple data transmissions, it is expected to introduce slot gaps between the data transmissions. Table 2 shows an exemplary TDRA table in a DCI that schedules multiple data transmissions according to a conventional solution. TIFF0007775903000005.tif49155

[0110] The row index in Table 2 is associated with the number of scheduled transmissions. For example, row index 0 represents resources for scheduled data transmissions when the number of scheduled data transmissions is 2. Row index 1 represents resources for scheduled data transmissions when the number of scheduled data transmissions is 4. Row index 2 represents resources for scheduled data transmissions when the number of scheduled data transmissions is 8.

[0111] For each row index in the TDRA table, there is a common parameter K0. Parameter K0 in Table 2 represents the offset between the slot of the scheduling PDCCH and the slot of the first scheduled PDSCH. Each of parameters SLIV1 to SLIV8 in Table 2 includes two fields (e.g., (0, 40) in row index 0), one field indicating the slot gap between the scheduled slot of the corresponding data transmission and the scheduled slot of the previous data transmission, and the other field indicating the starting position and length of the time domain resource for the corresponding data transmission.

[0112]

[0013] Embodiments of the present disclosure provide an improved solution for indicating resources for scheduled data transmissions within a DCI. Instead of using two fields for each parameter SLIV1-SLIV8 in Table 2, in the present solution, one field is used to indicate both the slot gap between the first slot of the corresponding data transmission and the second slot of the previous data transmission, and information about the starting position and length of the time domain resource for the corresponding data transmission on the first slot. Table 3 shows an example TDRA table within a DCI for scheduling multiple data transmissions according to an embodiment of the present disclosure. TIFF0007775903000006.tif53166

[0113] Parameter K0 in Table 3 represents the slot offset between the scheduling PDCCH and the first scheduled PDSCH. Parameters SLIV1-SLIV2 in Table 2 each include a single field (hereinafter referred to as SLIV1 for convenience) with a single value. The single value indicates the slot gap between the scheduled slot of the corresponding data transmission and the scheduled slot of the previous data transmission, as well as information about the start position and length of the time domain resource of the corresponding data transmission. In other words, the slot gap between the scheduled slot of the corresponding data transmission and the scheduled slot of the previous data transmission, as well as information about the start position and length, may be determined from the single value. This will be described in detail with reference to FIG. 8.

[0114] 8 is a schematic diagram illustrating another process 800 for communicating indicating resources for multiple data transmissions scheduled by a single DCI according to an embodiment of the present disclosure. For illustrative purposes, process 800 will be described with reference to FIG. 1. Process 800 may involve terminal device 110 and network device 120 shown in FIG. 1.

[0115] 8, network device 120 may generate 810 a DCI for scheduling multiple data transmissions. The DCI indicates multiple parameters (e.g., SLIV1 through SLIV8 in Table 3) for the multiple data transmissions, each of which has a single value (SLIV1) indicating a slot gap between a first slot of the corresponding data transmission and a second slot of the previous data transmission (hereinafter referred to as SLIV2), and information regarding the starting position and length of the time domain resource for the corresponding data transmission on the first slot (hereinafter referred to as SLIV3).

[0116] Network device 120 transmits 820 DCI indicating the plurality of parameters to terminal device 110. Based on each of the plurality of parameters, terminal device 110 determines 830 time domain resources for the corresponding data transmission. In some embodiments, terminal device 110 may determine slot gap SLIV2 according to equation (1) below. TIFF0007775903000007.tif474Here, SLIV2 represents the slot gap between the first slot of the corresponding data transmission and the second slot of the previous data transmission, and SLIV1 represents a single value of the parameter for the corresponding data transmission in the DCI.

[0117] In some embodiments, the terminal device 110 may determine the information SLIV3 according to the following equation (2): TIFF0007775903000008.tif473Here, SLIV3 represents information about the starting position and length of the time domain resource for the corresponding data transmission on the first slot, and SLIV1 represents a single value of the parameter for the corresponding data transmission in the DCI.

[0118] It should be noted that the above Table 3 is merely an example and does not limit the present disclosure. Furthermore, the above formula is merely an example, and any other suitable form of formula is also possible.

[0119] 8, in some embodiments where the multiple data transmissions are PDSCHs, terminal device 110 may receive the multiple data transmissions on the determined time domain resources 840. In some embodiments where the multiple data transmissions are PUSCHs, terminal device 110 may transmit the multiple data transmissions on the determined time domain resources 850.

[0120] Thus, there is no need to add a slot gap field or a unique slot offset to each SLIV in the TDRA table. Example of the method

[0121] The embodiments of the present disclosure provide communication methods implemented in a terminal device and a network device, which will be described below with reference to Figures 9 to 14.

[0122] 9 illustrates an exemplary communication method 900 implemented in a terminal device, according to some embodiments of the present disclosure. For example, method 900 may be performed in terminal device 110 shown in FIG. 1. For purposes of explanation, method 900 will be described below with reference to FIG. 1. It should be understood that method 900 may include additional blocks not shown and / or omit some blocks shown, and that the scope of the present disclosure is not limited in this respect.

[0123] At block 910, terminal device 110 receives from network device 120 a plurality of first data transmissions scheduled by a first DCI and a second data transmission scheduled by a second DCI.

[0124] In block 920, the terminal device 110 transmits to the network device 120 first HARQ feedback for a plurality of first data transmissions, the first HARQ feedback including a NACK for a first data transmission among the plurality of first data transmissions that collides with the configured uplink symbol, and second HARQ feedback for a second data transmission.

[0125] In some embodiments, terminal device 110 may transmit a first codebook for first HARQ feedback, the first codebook including a NACK in an HARQ-ACK bit position corresponding to a scheduled position for a colliding first data transmission. In some embodiments, terminal device 110 may transmit a first codebook for first HARQ feedback, the first codebook including a NACK after an HARQ-ACK bit for data transmissions of the plurality of first data transmissions excluding the colliding first data transmission.

[0126] In some embodiments, if only one of the multiple first data transmissions does not collide with the configured uplink symbol, terminal device 110 may generate a codebook for the first HARQ feedback and the second HARQ feedback for only that one of the multiple first data transmissions and transmit the codebook to network device 120.

[0127] In some embodiments, if only one of the plurality of first data transmissions does not collide with the set uplink symbol, terminal device 110 may generate a first codebook for the first HARQ feedback including HARQ feedback for the one of the plurality of first data transmissions and NACKs for the other data transmissions of the plurality of first data transmissions, and a second codebook for the second HARQ feedback, and transmit the codebooks to network device 120.

[0128] In some embodiments, terminal device 110 may generate the first HARQ feedback by grouping the plurality of first data transmissions into a plurality of groups, generate the second HARQ feedback by padding HARQ-ACK bits with NACKs such that the number of HARQ-ACK bits for the second HARQ feedback is equal to the number of HARQ-ACK bits for the first HARQ feedback, generate a codebook for the first feedback and the second feedback, and transmit the codebook to network device 120.

[0129] In some embodiments, terminal device 110 may generate the first HARQ feedback by grouping the plurality of first data transmissions into a plurality of groups, generate second HARQ feedback, generate a codebook for the first feedback and the second feedback, and transmit the codebook to network device 120. A maximum number of transport blocks supported by the terminal device's serving cell is equal to the number of the plurality of groups.

[0130] Thus, rules are defined for generating HARQ feedback for the multiple data transmissions in the event of such a collision.

[0131] 10 illustrates another exemplary communication method 1000 implemented in a terminal device, according to some embodiments of the present disclosure. For example, method 1000 may be performed in terminal device 110 shown in FIG. 1. For purposes of explanation, method 1000 will be described below with reference to FIG. 1. It should be understood that method 1000 may include additional blocks not shown and / or omit some blocks shown, and that the scope of the present disclosure is not limited in this respect.

[0132] At block 1010, terminal device 110 receives from network device 120 multiple data transmissions scheduled by the DCI.

[0133] At block 1020, terminal device 110 groups the multiple data transmissions based on a number of groups configured for terminal device 110. In some embodiments, the number of groups is commonly configured for terminal device 110's serving cell.

[0134] In some embodiments, the number of groups is set differently for each serving cell of terminal device 110. In these embodiments, terminal device 110 may group the multiple data transmissions by determining the largest number of the group numbers set for serving cells that establish a connection with terminal device 110 and grouping the multiple data transmissions based on the largest number.

[0135] In some embodiments, terminal device 110 may group the plurality of data transmissions by receiving a first instruction to enable grouping from network device 120 and grouping the plurality of data transmissions in accordance with the first instruction.

[0136] At block 1030, terminal device 110 transmits the HARQ feedback generated for the grouped data transmissions to network device 120. In some embodiments, terminal device 110 receives a second instruction from network device 120 to disable grouping and transmits to network device 120 another HARQ feedback generated for the multiple data transmissions without grouping the multiple data transmissions.

[0137] In this way, the number of groups for grouping may be flexibly changed depending on the number of data transmissions to be scheduled.

[0138] 11 illustrates another exemplary communication method 1100 implemented in a terminal device, according to some embodiments of the present disclosure. For example, method 1100 may be performed in terminal device 110 shown in FIG. 1. For purposes of explanation, method 1100 will be described below with reference to FIG. 1. It should be understood that method 1100 may include additional blocks not shown and / or omit some blocks shown, and that the scope of the present disclosure is not limited in this respect.

[0139] 11 , in block 1110, terminal device 110 receives, from network device 120, DCI scheduling multiple data transmissions, the DCI indicating multiple parameters for the multiple data transmissions, each of the multiple parameters having a single value indicating a slot gap between a first slot of the corresponding data transmission and a second slot of a previous data transmission, and further indicating information regarding a starting position and a length of a time domain resource for the corresponding data transmission on the first slot, i.e., the single value indicating both the slot gap and the information.

[0140] At block 1120, terminal device 110 determines a time domain resource for a corresponding data transmission based on each of the parameters. TIFF0007775903000009.tif434 may determine the slot gap between the first slot and the second slot, and mod(SLIV1,128) may determine information regarding the start position and length of the time domain on the first slot, where SLIV1 indicates a single value of each of the multiple parameters.

[0141] In this way, there is no need to add a slot gap field or a unique slot offset to each SLIV in the TDRA table.

[0142] 12 illustrates an exemplary communication method 1200 implemented in a network device according to some embodiments of the present disclosure. For example, method 1200 may be performed in network device 120 shown in FIG. 1. For purposes of explanation, method 1200 will be described below with reference to FIG. 1. It should be understood that method 1200 may include additional blocks not shown and / or omit some blocks that are shown, and that the scope of the present disclosure is not limited in this respect.

[0143] As shown in FIG. 12, in block 1210, the network device 120 transmits to the terminal device 110 a plurality of first data transmissions scheduled by a first DCI and a second data transmission scheduled by a second DCI.

[0144] In block 1220, the network device 120 receives, from the terminal device 110, first HARQ feedback for a plurality of first data transmissions, the first HARQ feedback including a NACK for a first data transmission among the plurality of first data transmissions that collides with a configured uplink symbol, and second HARQ feedback for a second data transmission.

[0145] In some embodiments, the network device 120 may receive a first codebook for the first HARQ feedback, the first codebook including a negative acknowledgment at a HARQ-ACK bit position corresponding to the scheduled position for the colliding first data transmission.

[0146] In some embodiments, the network device 120 may receive a first codebook for a first HARQ feedback, the first codebook including negative acknowledgments after HARQ-ACK bits for data transmissions of the plurality of first data transmissions excluding a colliding first data transmission.

[0147] In some embodiments, the network device 120 may receive a codebook for the first HARQ feedback and the second HARQ feedback for only one data transmission of the plurality of first data transmissions that does not collide with the configured uplink symbol.

[0148] In some embodiments, the network device 120 may receive a first codebook for the first HARQ feedback that includes a NACK or an ACK for only one data transmission of the plurality of first data transmissions that does not collide with the configured uplink symbol, and a second codebook for the second HARQ feedback.

[0149] In some embodiments, network device 120 may receive a codebook for first feedback generated by grouping the plurality of first data transmissions into a plurality of groups and second HARQ feedback generated by padding HARQ-ACK bits for the second HARQ feedback with a NACK such that the number of HARQ-ACK bits for the second HARQ feedback is equal to the number of HARQ-ACK bits for the first HARQ feedback.

[0150] In some embodiments, the network device 120 may receive a codebook for the first feedback and the second feedback, and the first HARQ feedback is generated by grouping the plurality of first data transmissions into a plurality of groups, and the maximum number of transport blocks supported by the terminal device's serving cell is equal to the number of the plurality of groups.

[0151] In this way, rules are defined for generating HARQ feedback for the multiple data transmissions in the event of such a collision.

[0152] 13 illustrates another exemplary communication method 1300 implemented in a network device, according to some embodiments of the present disclosure. For example, method 1300 may be performed in network device 120 shown in FIG. 1. For purposes of explanation, method 1300 will be described below with reference to FIG. 1. It should be understood that method 1300 may include additional blocks not shown and / or omit some blocks that are shown, and that the scope of the present disclosure is not limited in this respect.

[0153] As shown in FIG. 13, in block 1310, network device 120 transmits multiple data transmissions to terminal device 110, which are scheduled by the DCI.

[0154] At block 1320, network device 120 receives, from terminal device 110, HARQ feedback for multiple data transmissions grouped based on a number of groups configured for terminal device 110. In some embodiments, the number of groups may be commonly configured for the serving cell of terminal device 110.

[0155] In some embodiments, the number of groups may be configured differently for each of the terminal device's serving cells, and the multiple data transmissions are grouped based on the largest number of groups configured for the serving cells that establish a connection with terminal device 110.

[0156] In some embodiments, network device 120 may send a first instruction to enable grouping to terminal device 110. In some embodiments, network device 120 may send a second instruction to disable grouping to terminal device 110 and receive another HARQ feedback generated for the multiple data transmissions from terminal device 110.

[0157] In this way, the number of groups for grouping may be flexibly changed depending on the number of data transmissions to be scheduled.

[0158] 14 illustrates another exemplary communication method 1400 implemented in a network device, according to some embodiments of the present disclosure. For example, method 1400 may be performed in network device 120 shown in FIG. 1. For purposes of explanation, method 1400 will be described below with reference to FIG. 1. It should be understood that method 1400 may include additional blocks not shown and / or omit some blocks that are shown, and that the scope of the present disclosure is not limited in this respect.

[0159] As shown in FIG. 14, in block 1410, the network device 120 transmits to the terminal device 110 a DCI scheduling multiple data transmissions, the DCI indicating multiple parameters for the multiple data transmissions, each parameter having a single value indicating a slot gap between a first slot of a corresponding data transmission and a second slot of a previous data transmission, and further indicating information regarding the starting position and length of the time domain resource of the corresponding data transmission on the first slot.

[0160] In some embodiments, the slot gap between the first slot and the second slot is: TIFF0007775903000010.tif434, where SLIV1 indicates a single value of each of the multiple parameters. Information about the starting position and length of the time domain resource on the first slot may be determined by mod(SLIV1,128).

[0161] In this way, the overhead of DCI transmission is reduced. Device implementation example

[0162] Figure 15 is a schematic block diagram of an apparatus 1500 suitable for implementing embodiments of the present disclosure. Apparatus 1500 may be considered another exemplary implementation of terminal device 110 or network device 120 shown in Figure 1. Thus, apparatus 1500 may be implemented in, or as at least a part of, terminal device 110 or network device 120.

[0163] As shown, the apparatus 1500 comprises a processor 1510, a memory 1520 coupled to the processor 1510, a suitable transmitter (TX) and receiver (RX) 1540 coupled to the processor 1510, and a communication interface coupled to the TX / RX 1540. The memory 1510 stores at least a portion of a program 1530. The TX / RX 1540 is used for bidirectional communication. The TX / RX 1540 has at least one antenna to facilitate communication, although the access nodes referred to herein may in practice have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 / Xn interface for bidirectional communication between eNBs / gNBs, an S1 / NG interface for communication between a Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and an eNB / gNB, an Un interface for communication between an eNB / gNB and a relay node (RN), or a Uu interface for communication between an eNB / gNB and a terminal device.

[0164] The program 1530 is envisioned to include program instructions that, when executed by an associated processor 1510, enable the device 1500 to operate in accordance with embodiments of the present disclosure, as described herein with reference to Figures 3-14. The embodiments herein may be implemented by computer software executable by the processor 1510 of the device 1500, by hardware, or by a combination of software and hardware. The processor 1510 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 1510 and the memory 1520 may form a processing means 1550 suitable for implementing various embodiments of the present disclosure.

[0165] Memory 1520 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, including, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. While only one memory 1520 is shown in device 1500, several physically distinct memory modules may be present within device 1500. Processor 1510 may be of any type suitable for a local technology network and may include, by way of non-limiting example, 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 architecture. Device 1500 may have multiple processors, e.g., application-specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

[0166] In some embodiments, a terminal device comprises a circuit configured to receive from a network device a plurality of first data transmissions scheduled by a first DCI and a second data transmission scheduled by a second DCI, and to transmit to the network device a first HARQ feedback for the plurality of first data transmissions, the first HARQ feedback including a NACK for a first data transmission among the plurality of first data transmissions that collides with a configured uplink symbol, and a second HARQ feedback for the second data transmission.

[0167] In some embodiments, the circuitry may be configured to transmit the first HARQ feedback by transmitting a first codebook for the first HARQ feedback, the first codebook including a negative acknowledgment at a HARQ-ACK bit position corresponding to a scheduled position for the colliding first data transmission.

[0168] In some embodiments, the circuitry may be configured to transmit the first HARQ feedback by transmitting a first codebook for the first HARQ feedback, the first codebook including negative acknowledgments after HARQ-ACK bits for data transmissions of the plurality of first data transmissions excluding a colliding first data transmission.

[0169] In some embodiments, the circuitry may be further configured to: generate a codebook for a first HARQ feedback and a second HARQ feedback for only one of the plurality of first data transmissions according to a determination that only the one of the plurality of first data transmissions does not collide with the set uplink symbol; and transmit the codebook to network device 120.

[0170] In some embodiments, the circuitry may be further configured to generate a first codebook for first HARQ feedback including a NACK or ACK for the one of the plurality of first data transmissions and NACKs for other data transmissions of the plurality of first data transmissions according to a determination that the set uplink symbols are non-colliding, and a second codebook for second HARQ feedback, and transmit the codebooks to network device 120.

[0171] In some embodiments, the circuitry may be configured to generate the first HARQ feedback by grouping the plurality of first data transmissions into a plurality of groups, generate the second HARQ feedback by padding HARQ-ACK bits with NACKs such that a number of HARQ-ACK bits for the second HARQ feedback is equal to a number of HARQ-ACK bits for the first HARQ feedback, generate a codebook for the first feedback and the second feedback, and transmit the first HARQ feedback and the second HARQ feedback by transmitting the codebook to the network device.

[0172] In some embodiments, the circuitry may be configured to generate the first HARQ feedback by grouping the plurality of first data transmissions into a plurality of groups, generate second HARQ feedback, generate a codebook for the first feedback and the second feedback, and transmit the first HARQ feedback and the second HARQ feedback by transmitting the codebook to the network device, wherein a maximum number of transport blocks supported by a serving cell of a terminal device is equal to the number of the plurality of groups.

[0173] In some embodiments, a terminal device comprises circuitry configured to receive, from a network device, a plurality of data transmissions scheduled by a DCI, group the plurality of data transmissions based on a number of groups configured for the terminal device, and transmit, to the network device, HARQ feedback generated for the grouped data transmissions.

[0174] In some embodiments, the number of groups may be commonly configured for the terminal device's serving cells. In some embodiments, the number of groups may be configured differently for each of the terminal device's serving cells. In these embodiments, the circuitry may be configured to group the multiple data transmissions by determining a maximum number of group numbers configured for serving cells that establish a connection with terminal device 110 and grouping the multiple data transmissions based on the maximum number.

[0175] In some embodiments, the circuitry may be configured to group the plurality of data transmissions by receiving a first instruction from a network device to enable grouping, and grouping the plurality of data transmissions in response to the first instruction.

[0176] In some embodiments, the circuitry may be further configured to receive, from the network device, a second instruction to disable grouping and to transmit, to the network device, another HARQ feedback generated for the plurality of data transmissions.

[0177] In some embodiments, a terminal device comprises circuitry configured to receive from a network device a DCI scheduling a plurality of data transmissions, the DCI indicating a plurality of parameters for the plurality of data transmissions, each parameter having a single value indicating a slot gap between a first slot of a corresponding data transmission and a second slot of a previous data transmission, and further indicating information regarding a starting position and a length of a time domain resource for the corresponding data transmission on the first slot, and to determine a time domain resource for the corresponding data transmission based on each of the plurality of parameters.

[0178] In some embodiments, the circuitry comprises: TIFF0007775903000011.tif434 may be set to determine the slot gap between the first slot and the second slot, where SLIV1 indicates a single value of each of the multiple parameters, and mod(SLIV1,128) may be set to determine the time domain resource by determining information regarding the starting position and length of the time domain resource on the first slot.

[0179] In some embodiments, the network device comprises a circuit configured to transmit to a terminal device a plurality of first data transmissions scheduled by a first DCI and a second data transmission scheduled by a second DCI, and to receive from the terminal device a first HARQ feedback for the plurality of first data transmissions, the first HARQ feedback including a NACK for a first data transmission among the plurality of first data transmissions that collides with a configured uplink symbol, and a second HARQ feedback for the second data transmission.

[0180] In some embodiments, the circuitry may be configured to receive the first HARQ feedback by transmitting a first codebook for the first HARQ feedback, the first codebook including a negative acknowledgment at a HARQ-ACK bit position corresponding to a scheduled position for the colliding first data transmission.

[0181] In some embodiments, the circuitry may be configured to receive the first HARQ feedback by receiving a first codebook for the first HARQ feedback, the first codebook including negative acknowledgments after HARQ-ACK bits for data transmissions of the plurality of first data transmissions excluding a colliding first data transmission.

[0182] In some embodiments, the circuitry may be further configured to receive a codebook for a first HARQ feedback and a second HARQ feedback for only one data transmission of the plurality of first data transmissions that does not collide with the configured uplink symbol.

[0183] In some embodiments, the circuitry may be further configured to receive a first codebook for first HARQ feedback including a NACK or an ACK for only one data transmission of the plurality of first data transmissions that does not collide with a configured uplink symbol and a NACK for other data transmissions of the plurality of first data transmissions, and a second codebook for second HARQ feedback.

[0184] In some embodiments, the circuitry may be configured to receive the first HARQ feedback and the second HARQ feedback by receiving a codebook for the first feedback generated by grouping the plurality of first data transmissions into a plurality of groups and the second HARQ feedback generated by padding HARQ-ACK bits for the second HARQ feedback with a NACK such that a number of HARQ-ACK bits for the second HARQ feedback equals the number of HARQ-ACK bits for the first HARQ feedback.

[0185] In some embodiments, the circuitry may be configured to receive the first HARQ feedback and the second HARQ feedback by receiving a codebook for the first HARQ feedback and the second HARQ feedback. The first HARQ feedback is generated by grouping a plurality of first data transmissions into a plurality of groups. A maximum number of transport blocks supported by a serving cell of the terminal device is equal to the number of the plurality of groups.

[0186] In some embodiments, the network device comprises circuitry configured to transmit, to a terminal device, a plurality of data transmissions scheduled by the DCI, and receive, from the terminal device, HARQ feedback for the plurality of data transmissions grouped based on a number of groups configured for the terminal device. In some embodiments, the number of groups may be commonly configured for a serving cell of the terminal device.

[0187] In some embodiments, the number of groups may be configured differently for each of the terminal device's serving cells, and the multiple data transmissions are grouped based on the largest number of groups configured for the serving cells that establish a connection with the terminal device.

[0188] In some embodiments, the circuitry may be further configured to send, to the terminal device, a first instruction to enable grouping.

[0189] In some embodiments, the circuitry may be further configured to send a second instruction to the terminal device to disable grouping and receive another HARQ feedback generated for the plurality of data transmissions from the terminal device.

[0190] In some embodiments, the network device comprises circuitry configured to transmit from a terminal device a DCI scheduling a plurality of data transmissions, the DCI indicating a plurality of parameters for the plurality of data transmissions, each parameter having a single value indicating a slot gap between a first slot of a corresponding data transmission and a second slot of a previous data transmission, and further indicating information regarding a starting position and a length of a time domain resource for the corresponding data transmission on the first slot.

[0191] In some embodiments, the slot gap between the first slot and the second slot is: TIFF0007775903000012.tif434, where SLIV1 indicates a single value of each of the multiple parameters, and information regarding the starting position and length of the time domain resource on the first slot may be determined by mod(SLIV1,128).

[0192] As used herein, the term "circuitry" can refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuitry and software / firmware. As yet another example, a circuit may be any portion of a hardware processor with software, including a digital signal processor, software, and one or more memories, that cooperate to cause a device, such as a terminal device or a network device, to perform various functions. In yet another example, a circuit may be a hardware circuit and / or a processor, such as a microprocessor or portion thereof, that requires software / firmware for operation, although the software may not be present if not necessary for operation. As used herein, the term "circuitry" also includes implementations of a hardware circuit or one or more processors only, or a hardware circuit or portion of one or more processors and its (or their) accompanying software and / or firmware.

[0193] Overall, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. While various aspects of embodiments of the present disclosure have been illustrated and described using block diagrams, flowcharts, or other pictorial representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented, by way of non-limiting example, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or any combination thereof.

[0194] 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 program modules, that execute within a device on a target real or virtual processor to perform the processes or methods described above with reference to FIGS. 3-14. Generally, 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 between program modules as desired. The machine-executable instructions of the program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote storage media.

[0195] Program code 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 device, and when executed by the processor or controller, cause the program code to implement the functions / acts specified in the flowcharts and / or block diagrams. The program code 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.

[0196] The above-described program code may be embodied on a machine-readable medium, which may be any tangible medium that can contain or store a program used by or associated with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the aforementioned media. More specific examples of a machine-readable storage medium may include an electrical connection having one or more wires, a portable computer 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 above.

[0197] Although operations have been described in a particular order, it should not be understood that performing these operations in the particular order shown, or in any sequential order, or performing all of the operations described, is required to achieve desirable results. In some cases, multitasking or parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Some features that are described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0198] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure, as 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. 1. A method implemented by a terminal device, comprising: receiving downlink control information (DCI) from a network device scheduling a plurality of data transmissions; transmitting to the network device a codebook for hybrid automatic repeat request (HARQ) feedback for the plurality of data transmissions, the HARQ feedback including negative acknowledgements (NACKs) for data transmissions of the plurality of data transmissions that collide with configured uplink symbols; the codebook includes the negative acknowledgement in a HARQ-ACK bit position corresponding to a scheduled position for the data transmission. method.

2. The plurality of data transmissions includes several groups, and the number of groups is determined based on a maximum number of a plurality of group numbers for a plurality of serving cells. The method of claim 1.

3. 1. A method implemented by a network device, comprising: transmitting downlink control information (DCI) to the terminal device scheduling the plurality of data transmissions; receiving, from the terminal device, a codebook for hybrid automatic repeat request (HARQ) feedback for the plurality of data transmissions, the HARQ feedback including negative acknowledgements (NACKs) for data transmissions among the plurality of data transmissions that collide with configured uplink symbols; the codebook includes the negative acknowledgement in a HARQ-ACK bit position corresponding to a scheduled position for the data transmission. method.

4. The plurality of data transmissions includes several groups, and the number of groups is determined based on a maximum number of a plurality of group numbers for a plurality of serving cells. The method of claim 3.

5. A terminal device, means for receiving downlink control information (DCI) from a network device that schedules a plurality of data transmissions; means for transmitting to the network device a codebook for hybrid automatic repeat request (HARQ) feedback for the plurality of data transmissions, the HARQ feedback including negative acknowledgements (NACKs) for data transmissions of the plurality of data transmissions that collide with configured uplink symbols; the codebook includes the negative acknowledgement in a HARQ-ACK bit position corresponding to a scheduled position for the data transmission. Terminal device.

6. The method of claim 1, wherein the plurality of data transmissions includes a number of groups, and the number of groups is determined based on a maximum number of a plurality of groups for a plurality of serving cells. The terminal device according to claim 5.

7. A network device, means for transmitting to the terminal device downlink control information (DCI) scheduling a plurality of data transmissions; means for receiving from the terminal device a codebook for hybrid automatic repeat request (HARQ) feedback for the plurality of data transmissions, the HARQ feedback including negative acknowledgements (NACKs) for data transmissions of the plurality of data transmissions that collide with configured uplink symbols; the codebook includes the negative acknowledgement in a HARQ-ACK bit position corresponding to a scheduled position for the data transmission. Network equipment.

8. The method of claim 7, wherein the plurality of data transmissions includes a number of groups, and the number of groups is determined based on a maximum number of a plurality of groups for a plurality of serving cells. The network device according to claim 7.

Images