Communication device and method of communication device

Abstract

The present disclosure relates to a communication method, an apparatus, and a computer-readable medium. A network device generates downlink control information for scheduling a plurality of data channels grouped into a plurality of groups, and transmits the generated downlink control information to a terminal device. Upon receiving the downlink control information, the terminal device performs data transmission between the terminal device and the network device based on the grouped data channels. In this way, the payload of the downlink control information can be reduced, and the false detection rate can be reduced.

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) within a single downlink control channel.

Background Art

[0002] Currently, to support New Radio (NR) from 52.6 GHz to 71 GHz, multi-TTI-based scheduling has been proposed that uses a single physical downlink control channel (PDCCH) to schedule multiple physical uplink shared channels (PUSCH). Based on this mechanism, the implementation of the scheduler and the processing burden of the upper layer can be reduced while maintaining the same peak data rate.

[0003] When multi-TTI-based scheduling is extended to scheduling of multiple physical downlink shared channels (PDSCH) by DCI on a single PDCCH, there may be two transport blocks (TBs) within a single PDSCH, so the number of bits in the DCI should be further increased. This results in a larger DCI payload and a higher false detection rate.

Summary of the Invention

Problems 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 multi-TTIs within a single downlink control channel.

Means for Solving the Problems

[0005] In a first aspect, a communication method is provided. The method includes receiving, at a terminal device, downlink control information for scheduling a plurality of data channels grouped into a plurality of groups from a network device, and performing data transmission between the terminal device and the network device based on the grouped data channels.

[0006] In a second aspect, a communication method is provided. The method includes receiving, at a terminal device, downlink data on a plurality of downlink data channels scheduled by a single downlink control channel from a network device, and transmitting, to the network device, hybrid automatic repeat request (HARQ) feedback for the downlink data based on a countdown downlink assignment indicator (DAI) received from the single downlink control channel.

[0007] In a third aspect, a communication method is provided. The method includes generating, at a network device, downlink control information for scheduling a plurality of data channels grouped into a plurality of groups, and transmitting the downlink control information to a terminal device.

[0008] In a fourth aspect, a communication method is provided. The method includes transmitting, at a network device, downlink data on a plurality of downlink data channels scheduled by a single downlink control channel to a terminal device, and receiving, from the terminal device, HARQ feedback for the downlink data generated based on a counter DAI.

[0009] In a fifth aspect, a terminal device is provided. The terminal device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the terminal device to execute the method described in the first aspect of the present disclosure.

[0010] In a sixth aspect, a terminal device is provided. The terminal device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the terminal device to execute the method described in the second aspect of the present disclosure.

[0011] In a seventh aspect, a network device is provided. The network device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the network device to execute the method described in the third aspect of the present disclosure.

[0012] In an eighth aspect, a network device is provided. The network device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the network device to execute the method described in the fourth aspect of the present disclosure.

[0013] In a ninth aspect, a computer-readable medium storing instructions is provided. The instructions, when executed on at least one processor, cause the at least one processor to execute the methods described in the first and second aspects of the present disclosure.

[0014] In a tenth aspect, a computer-readable medium storing instructions is provided. The instructions, when executed on at least one processor, cause the at least one processor to execute the methods described in the third and fourth aspects of the present disclosure.

[0015] Other features of the present disclosure should be easily understood from the following description.

Brief Description of the Drawings

[0016] In the drawings, some embodiments of the present disclosure will be described in more detail to further clarify the above-mentioned and other objects, features, and advantages of the present disclosure.

[0017]

Figure 1

[0018]

Figure 2

[0019]

Figure 3

[0020]

Figure 4

[0021]

Figure 5

[0022]

Figure 6

[0023]

Figure 7

[0024]

Figure 8A

[0025]

Figure 8B

[0026]

Figure 9A

[0027]

Figure 9B

[0028]

Figure 10A

[0029]

Figure 10B

[0030]

Figure 11

[0031]

Figure 12

[0032]

Figure 13

[0033]

Figure 14

[0034]

Figure 15

[0035]

Figure 16

[0036]

Figure 17

[0037]

Figure 18

[0038]

Figure 19

[0039]

Figure 20

[0040] In the figure, the same or similar reference numerals represent the same or similar elements.

DETAILED DESCRIPTION OF THE INVENTION

[0041] Here, the principles of the present disclosure will be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and are intended to assist those skilled in the art in understanding and implementing 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 the methods described below.

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

[0043] As used herein, the term "terminal device" means any device having wireless or wired communication capabilities. 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, any Internet of Everything (IoE) devices, machine type communication (MTC) devices, in-vehicle devices for V2X communication, etc. Here, "X" in V2X represents a pedestrian, a vehicle, or infrastructure / network, or an image acquisition device such as a digital camera, a game device, a music storage and playback device, or an Internet appliance that enables wireless or wired Internet access and browsing. The term "terminal device" can be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. Also, the term "network device" means a device that can provide or host a cell or coverage with which a terminal device can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next-generation Node B (gNB), Transmission Reception Point (TRP), Remote Radio Unit (RRU), radio head (RH), remote radio head (RRH), femto node, pico node, and other low-power nodes.

[0044] In one embodiment, the terminal device can be connected to a first network device and a second network device. One of the first network device and the second network device may be used as a master node, and the other may be used as 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 regarding different RATs can be transmitted from at least one of the first network device or the second network device to the terminal 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 regarding the settings of the terminal device set by the second network device can be transmitted from the second network device via the first network device. Information regarding the resetting of the terminal device set by the second network device can be transmitted from the second network device directly or via the first network device to the terminal device.

[0045] As used herein, the singular forms "a / an" and "the" include the plural forms as well, unless the context clearly dictates otherwise. The term "comprising" and variations thereof should be understood as an open-ended term 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 "an embodiment" should be understood as "at least one embodiment." The term "another embodiment" should be understood as "at least one other embodiment." The terms "first," "second," etc. can refer to different or the same objects. There may be other explicit and implicit definitions below.

[0046] In some examples, a value, procedure, or device is referred to as "best," "lowest," "highest," "minimum," "maximum," etc. Such descriptions are intended to indicate that a selection can be made from among a number of available functional alternatives, and it will be understood that such a selection need not be better, smaller, higher, or otherwise more preferred than other selections.

[0047] As described above, when the scheduling of multiple PUSCHs within a single DCI is extended to the scheduling of multiple PDSCHs within a single DCI, since there may be two TBs in one PDSCH, it is necessary to further increase the bits in the DCI. Specifically, the DCI includes a new data indicator (NDI) field and a redundancy version (RV) field. The bits of the NDI field and the bits of the RV field are each mapped one-to-one to the scheduled PUSCH. When extended to the scheduling of multiple PDSCHs within a DCI and there are two TBs in one PDSCH, the bits of the NDI field and the RV field are doubled. In this case, since the payload of the DCI becomes larger, a higher false detection rate is brought about.

[0048] In view of this, embodiments of the present disclosure provide a solution for scheduling a plurality of data channels by DCI on a single downlink control channel. This solution may be applied to scheduling for uplink data channels and may also be applied to scheduling for downlink data channels. In this solution, a plurality of data channels are divided into a plurality of groups, and for each of the plurality of groups, the same bits in the NDI field and the RV field are allocated, that is, the NDI and RV values are shared in the DCI. Thus, fewer bits are used to indicate new data or retransmission data for each data channel group. Thereby, the payload of the DCI can be reduced and the false detection rate can be reduced.

[0049] Embodiments of the present disclosure also provide a solution for extending HARQ feedback for a plurality of downlink data channels scheduled by DCI on a single downlink control channel. In this solution, a counter DAI (also referred to as c-DAI here) is allocated to a plurality of downlink data channels scheduled by DCI, and for one CC and CA, HARQ feedback is provided based on the counter DAI. Thus, HARQ feedback extension can be realized for a plurality of downlink data channels scheduled by DCI.

[0050] Hereinafter, with reference to the accompanying drawings, the principles and embodiments of the present disclosure will be described in detail. Example of communication network

[0051] FIG. 1 is a schematic diagram showing an exemplary communication network 100 in which embodiments of the present disclosure can be implemented. As shown in FIG. 1, the communication network 100 can include a terminal device 110 and a network device 120. In some embodiments, the terminal device 110 may be served by the network device 120. It will be understood that the number of devices in FIG. 1 is provided for illustrative purposes and does not imply any limitation to the present disclosure. The communication network 100 can include any suitable number of network devices and / or terminal devices suitable for implementing the embodiments of the present disclosure.

[0052] As shown in FIG. 1, the terminal device 110 can communicate with the network device 120 via a channel such as a wireless communication channel. The communication in the communication network 100 can comply with 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. Further, the communication can be performed according to any generation of communication protocol known currently or developed in the future. Examples of communication protocols include, but are not limited to, the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols.

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

[0054] In some embodiments, the terminal device 110 may receive DCI, such as data transmission settings, from the network device 120 via downlink control channel transmission. For example, the downlink control channel transmission may be PDCCH transmission. Of course, any other appropriate format is also possible. In some embodiments, the terminal device 110 may transmit uplink control information (UCI), such as HARQ feedback information, to the network device 120 via uplink channel transmission. For example, the uplink channel transmission may be PUCCH or PUSCH transmission. Of course, any other appropriate format is also possible.

[0055] In some embodiments, the network device 120 may provide the terminal device 110 with a plurality of serving cells (not shown in this specification), 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 can communicate with the network device 120 via the CC. Of course, the terminal device 110 may communicate with the network device 120 via a plurality of CCs, for example, in the case of CA.

[0056] In the conventional solution, the network device may schedule one downlink data channel by DCI on one downlink control channel. FIG. 2 is a schematic diagram showing a process 200 for scheduling one downlink data channel by DCI according to the conventional solution. As shown in FIG. 2, one PDCCH schedules one PDSCH, and each PDSCH occupies one HARQ process number.

[0057] According to an embodiment of the present disclosure, the network device 120 may schedule a plurality of downlink data channels by DCI for the terminal device 110 on a single downlink control channel. FIG. 3 is a schematic diagram showing a process 300 for scheduling a plurality of downlink data channels by DCI according to an embodiment of the present disclosure. As shown in FIG. 3, one PDCCH 301 schedules five PDSCHs, namely PDSCH#0 to #4. It should be understood that the number of PDSCHs scheduled within one PDCCH is not limited to the above example, and any other integer greater than 1 is also possible. Although FIG. 3 shows one PDCCH scheduling a plurality of PDSCHs, the embodiment of the present disclosure is also applicable to one PDCCH scheduling a plurality of PUSCHs. For convenience, hereinafter, one PDCCH scheduling a plurality of PDSCHs will be described as an example. Example of realizing data channel scheduling in DCI

[0058] The embodiment of the present disclosure provides a solution for scheduling a plurality of data channels by DCI on a single downlink control channel. This will be described in detail with reference to FIGS. 4 to 6. FIG. 4 is a schematic diagram showing a process 400 for communication during scheduling of a plurality of data channels by DCI according to an embodiment of the present disclosure. For the sake of explanation, the process 400 will be described with reference to FIG. 1. As shown in FIG. 1, the terminal device 110 and the network device 120 may be involved in the process 400.

[0059] As shown in FIG. 4, the network device 120 may generate DCI for scheduling a plurality of data channels (410). In some embodiments, the DCI may include slot information for a plurality of data channels. In some embodiments, the DCI may include a new data indicator (NDI) field indicating a data transmission type. In some embodiments, the DCI may further include a redundancy version (RV) field. Of course, the DCI may further include any other appropriate information. For example, the DCI may further include modulation and coding scheme (MCS) information. As another example, the DCI may further include HARQ process information. In another example, the DCI may further include the total number of data channels scheduled by the DCI.

[0060] According to an embodiment of the present disclosure, the plurality of data channels are divided into a plurality of groups, and one of the bits in each of the NDI field and the RV field corresponds to one of the plurality of groups. In other words, the data channels within one group share the same NDI bit and RV bit. In this way, the number of bits in the DCI can be significantly reduced.

[0061] In some embodiments, the data channels within one group may share a HARQ process. In some embodiments, the data channels within one group may not share a HARQ process. For example, when the signal quality between the terminal device 110 and the network device 120 is below a threshold quality, the network device 120 may allocate different HARQ processes to each data channel within one group, and when the signal quality is above the threshold quality, the network device 120 may share the HARQ process among the data channels within one group. In some alternative or additional embodiments, the plurality of groups may share MCS values.

[0062] In some embodiments, the network device 120 may determine the number of data channels within each group. Thus, a plurality of data channels can be divided into groups. In some embodiments, the network device 120 may determine the number of data channels within each group based on the number of bits in the NDI field and the total number of data channels scheduled by the DCI.

[0063] In some embodiments, the network device 120 may determine the number of data channels by making the difference in the number of data channels between the plurality of groups less than or equal to a first predetermined value. For example, the first predetermined value may be 1. Of course, any other appropriate value is also possible.

[0064] Assume that C represents the number of scheduled PDSCHs signaled by the number of valid start and length indication values (SLIVs) indicated in the rows of the pdsch - TimeDomainAllocationList signaled within the DCI format 1_1, and M represents the NDI bits signaled within the DCI format 1_1. In some embodiments, the number of data channels within each group may be determined by the following equations (1) - (3). TIFF0007690987000001.tif43149M 1 If >0, m = 0, 1, … M 1 If = - 1, the PDSCH group m consists of PDSCHs (TTI) having K 1 and m = M 1 , M 1 If = + 1, … M - 1, the PDSCH group m consists of PDSCHs (TTI) having K 2 . Referring to FIG. 5, an example will be described.

[0065] FIG. 5 is a schematic diagram 500 showing an example of grouping of data channels scheduled by DCI according to an embodiment of the present disclosure. In this example, C = 8 and M = 3. That is, as shown by PDSCH#0 to #7 in FIG. 5, 8 PDSCHs are scheduled by one PDCCH, and there are 3 PDSCH groups in the DCI. According to the above formulas (1) to (3), as shown in FIG. 5, it is determined that PDSCH#0, PDSCH#1, and PDSCH#2 occupy group #0, PDSCH#3, PDSCH#4, and PDSCH#5 occupy group #1, and PDSCH#6 and PDSCH#7 occupy group #2.

[0066] In some alternative embodiments, the network device 120 may determine the number of data channels by making the number of groups having the same number of data channels among a plurality of groups greater than a second predetermined value. For example, the second predetermined value may be 2. Of course, any other appropriate value is also possible. In this way, most of the groups within the plurality of groups will have the same number of data channels.

[0067] Assume that C represents the number of scheduled PDSCHs signaled by the number of valid start and length indication values (SLIV: start and length indication value) shown in the rows of the pdsch - TimeDomainAllocationList signaled within DCI format 1_1, and M represents the NDI bit signaled within DCI format 1_1. In some embodiments, the number of data channels within each group may be determined by formula (1) and the following formulas (4) and (5). K 1 =(C - M 1 ) / M (4) K 2 =K 1 +M 1 (5) If m = 0, 1, … M - 2, then the PDSCH group m is K 1It consists of PDSCH (TTI). If m = M - 1, PDSCH group m has K 2 It consists of PDSCH (TTI) having

[0068] FIG. 6 is a schematic diagram 600 showing an example of grouping of data channels scheduled by DCI according to an embodiment of the present disclosure. In this example, C = 8 and M = 3. That is, as shown by PDSCH#0 to #7 in FIG. 6, eight PDSCHs are scheduled by one PDCCH, and there are three PDSCH groups in the DCI. According to the above formulas (1), (4), and (5), as shown in FIG. 6, it is determined that PDSCH#0 and PDSCH#1 occupy group #2, PDSCH#3 occupies group #1, and PDSCH#4, PDSCH#5, PDSCH#6, and PDSCH#7 occupy group #2.

[0069] It should be understood that the above formulas are only examples, and any other suitable method may be possible for grouping a plurality of data channels.

[0070] In some alternative embodiments, the network device 120 may set upper layer signaling parameters for the terminal device 110 to indicate the number of data channels in each group. In some embodiments, when a plurality of data channels scheduled by DCI on a single downlink control channel are enabled, the network device 120 may set a flag to enable or disable the grouping or bundling of the plurality of data channels. For example, this flag can be set as follows. TIFF0007690987000002.tif50142

[0071] In these embodiments, the network device 120 may introduce additional bits into the DCI to signal the number of data channels in each group (also referred to as the group size). The DCI payload may be designed as follows. DCI Payload: - Support for multi-PDSCH grouping - 0 or 1 bit. - 1 bit if the upper layer parameter multi-PDSCHs-Bundling-Flag is true. - Otherwise 0 bits. If multi-PDSCH grouping support is 0, the network device 120 may set the group size = 2, and if multi-PDSCH grouping support is 1, the network device 120 may set the group size = 4.

[0072] It should be understood that the above values and parameters for the group size are merely examples, and other suitable values and parameters are also possible.

[0073] Once the number of data channels within each group is determined, the network device 120 may allocate to each group a bit indicating whether the data transmission on each data channel within the group is a new data transmission. In this way, the network device 120 generates an NDI field including bits for a plurality of data channel groups. Accordingly, the network device 120 generates an RV field. In some embodiments, the number of bits in the RV field may be the same as the number of bits in the NDI field. In some embodiments, the number of bits in the RV field may be twice the number of bits in the NDI field. As a result, the network device 120 may generate a DCI including an NDI field and an RV field with fewer bits.

[0074] Returning to FIG. 4, once the DCI is generated, the network device 120 transmits the DCI to the terminal device 110 within a single downlink control channel (420). In this way, a plurality of data channels are scheduled by the DCI.

[0075] When the DCI is received, the terminal device 110 may determine the number of data channels in each group (430). In other words, the terminal device 110 may determine the grouping method adopted by the network device 120.

[0076] In some embodiments, the terminal device 110 may determine the number of data channels based on the number of bits in the NDI field and the total number of scheduled data channels included in the DCI. In some embodiments, the terminal device 110 may determine the number of data channels by making the difference in the number of data channels between the plurality of groups not exceed the first predetermined value. In some embodiments, the terminal device 110 may determine the number of data channels by making the number of groups having the same number of data channels among the plurality of groups greater than the second predetermined value. In some alternative embodiments, the terminal device 110 may determine the number of data channels based on upper layer signaling parameters from the network device 120.

[0077] It should be understood that the determination of the number of data channels in each group in the terminal device 110 is the same as the determination executed in the network device 120, and other details are not repeated here for the sake of brevity.

[0078] By determining the number of data channels in each group, the terminal device 110 determines which one bit among the bits the data channel group corresponds to. That is, the terminal device 110 determines the mapping relationship between the bits of the NDI field and the plurality of data channel groups.

[0079] In this case, the terminal device 110 can perform data transmission on a set of multiple data channels based on one corresponding bit among the bits. In some embodiments where the scheduled data channels are multiple downlink data channels, the terminal device 110 may receive downlink data on the multiple downlink data channels within the corresponding slot (440). In some embodiments where the scheduled data channels are multiple uplink data channels, the terminal device 110 may transmit uplink data on the multiple uplink data channels within the corresponding slot (450). In FIG. 4, three data channels are shown by dashed lines, but this is only an example, and it should be understood that the number of multiple data channels may be an integer of 2 or more.

[0080] As shown in Table 1, an exemplary comparison of the number of DCI bits between the conventional solution and this solution is shown. In this example, it is assumed that 8 PDSCHs are scheduled by DCI and a maximum of 2 TBs are supported. TIFF0007690987000003.tif79158

[0081] Grouping of data channels may occur when the signal-to-noise ratio (SNR) is good, the MCS is high, and the retransmission rate is low. An example of the relationship between MCS and the PDSCH group size is shown in Table 2. TIFF0007690987000004.tif43148

[0082] When scheduling multiple data channels by DCI on a single downlink control channel according to the process of FIG. 4, bundling multiple TTIs can use fewer bits to indicate new data or retransmission data for each group of data channels and can limit the RV bits. Further, by using the NDI bit in combination with the pdsch-TimeDomainAllocationList to implicitly indicate the number of TTIs within each group, it becomes more flexible for the network device to schedule HARQ processes according to performance.

[0083] For these embodiments, the 3GPP specification of 38.214 is changed as follows. Similar to the case where one PDCCH schedules multiple PUSCHs in R16, when multiple PDSCHs are scheduled for the UE by DCI, the HARQ process ID indicated by the DCI is applied to the first PDSCH group, and then, in the scheduled order, the HARQ process ID is incremented by 1 for each subsequent PDSCH, and a modulo 16 operation is applied. For any HARQ process ID within a given scheduled cell, it is not desirable for the UE to send a PDSCH group that temporally overlaps with another PDSCH group. When the pdsch-TimeDomainAllocationList in pdsch-Config includes rows indicating resource allocations for two to eight consecutive PDSCHs, K0 indicates the slot in which the DCI should schedule the first PDSCH among the multiple PDSCHs. Each PDSCH has its own SLIV and mapping type. The number of scheduled PDSCHs is signaled by the number of valid SLIVs indicated in the row of the pdsch-TimeDomainAllocationList signaled within DCI format 1_1. When multiple PDSCHs are scheduled for the UE by DCI, the bits of the rv field and the NDI field in the DCI are mapped one-to-one to the scheduled PDSCH group having the corresponding transport block in the scheduled order, and the LSB bits of the rv field and the NDI field respectively correspond to the last scheduled PDSCH group. When multiple PDSCHs are scheduled for the UE by DCI, the PDSCH-to-HARQ_feedback timing indicator, also referred to as K1, indicates the slot in which the DCI should schedule the first PDSCH among the multiple PDSCHs, and then is decremented by 1 for each subsequent PDSCH in the scheduled order, and the network should guarantee that K1 ≥ 0 for the last PDSCH. All of the multiple PDSCHs scheduled by DCI feedback HARQ within the same UL slot. Example of realizing HARQ feedback in data channel scheduling

[0084] Embodiments of the present disclosure also provide solutions for extending HARQ feedback for multiple downlink data channels scheduled by DCI on a single downlink control channel. According to embodiments of the present disclosure, based on different realizations of the counter DAI, embodiments of the present disclosure provide multiple solutions for HARQ feedback in the scheduling of multiple downlink data channels by a single DCI. This will be described in detail with reference to FIGS. 7-15.

[0085] FIG. 7 is a schematic diagram showing another process 700 for communication during the scheduling of multiple data channels by a single DCI according to an embodiment of the present disclosure. For the sake of explanation, process 700 will be described with reference to FIG. 1. As shown in FIG. 1, the terminal device 110 and the network device 120 may be involved in process 700.

[0086] As shown in FIG. 7, the network device 120 may generate DCI to schedule a downlink data channel group (710). According to an embodiment of the present disclosure, the downlink data channel group includes a plurality of downlink data channels. In some embodiments, the DCI may include slot information for a plurality of downlink data channels. In some embodiments, the DCI may include a counter DAI assigned for a plurality of downlink data channels. In some embodiments, the same counter DAI may be set for each downlink data channel within the group. In some embodiments, different counter DAIs may be set for each downlink data channel within the group based on the transmission order on a plurality of downlink data channels. It should be understood that the terminal device 110 and the network device 120 interpret the counter DAI in the same way.

[0087] In some embodiments regarding CA, the DCI may further include a total DAI (also referred to as t-DAI here) indicating the total number of a plurality of downlink data channels scheduled during a HARQ feedback window. Of course, the DCI may include any other appropriate information.

[0088] When the DCI is generated, the network device 120 may transmit the DCI to the terminal device 110 (720). When receiving the DCI, the terminal device 110 may determine a monitoring occasion for a plurality of downlink data channels based on the slot information in the DCI. Accordingly, the terminal device 110 receives downlink data transmitted from the network device 120 on a plurality of downlink data channels (730). Although three downlink data channels are shown by dashed lines in FIG. 7, this is only an example, and it should be understood that the number of a plurality of downlink data channels may be an integer greater than or equal to 2.

[0089] Then, the terminal device 110 may transmit HARQ feedback for the downlink data based on the counter DAI included in the DCI (740). According to an embodiment of the present disclosure, the terminal device 110 may receive downlink data from a plurality of downlink data channels scheduled by a single downlink control channel on at least one serving cell within at least one monitoring occasion for the downlink control channel. In this case, the HARQ feedback for the downlink data may be transmitted within the same uplink data or control channel. Embodiments of the present disclosure provide HARQ feedback solutions for CC (i.e., a single cell) and CA (i.e., a plurality of cells). In the case of CC, the terminal device 110 may receive downlink data from a plurality of downlink data channels scheduled by a single downlink control channel on the serving cell and within at least one monitoring occasion for the downlink control channel. 1. Example of HARQ feedback for CC

[0090] Embodiment 1

[0091] In this embodiment, the terminal device 110 may set the same counter DAI for each downlink data channel in the downlink data channel group, and generate a HARQ codebook based on the counter DAI and the number of downlink data channels in the downlink data channel group. This will be described in detail with reference to FIGS. 8A and 8B. According to an embodiment of the present disclosure, it is assumed that a Type-2 HARQ-ACK codebook is set for the terminal device 110. Of course, any other suitable codebook type is also possible.

[0092] FIG. 8A is a schematic diagram 800A showing an example of generating HARQ feedback during scheduling of a plurality of data channels by DCI in the CC according to an embodiment of the present disclosure. In this example, in the entire downlink data channel group scheduled by a single DCI, the counter DAI for each downlink data channel within the entire group maintains the same value as the value signaled within the DCI. The terminal device 110 may generate one or two HARQ bits for each downlink data channel based on the number of TBs supported in this cell. The HARQ codebook may be generated in ascending order of the counter DAI.

[0093] As shown in FIG. 8A, the PDCCH 810 schedules four PDSCHs of PDSCH#0 to #3, and the c-DAI in the PDCCH 810 of slot #0 is 1. The PDCCH 820 schedules two PDSCHs of PDSCH#4 and #5, and the c-DAI in the PDCCH 820 of slot #4 is 2. The PDCCH 830 schedules two PDSCHs of PDSCH#6 and #7, and the c-DAI in the PDCCH 830 of slot #6 is 3. Assume that downlink data is correctly received on PDSCH#0 to #7. When supporting one TB, the HARQ codebook 840 may be generated. When supporting two TBs, the HARQ codebook 850 may be generated.

[0094] It should be noted that the example of FIG. 8A is for illustration purposes only and does not limit the present disclosure. Any other suitable method is also possible.

[0095] In some embodiments, when it is determined that the counter DAI is missing within the HARQ feedback window, the terminal device 110 may generate a negative acknowledgement (NACK) feedback for the corresponding downlink data channel group. This will be described with reference to FIG. 8B. FIG. 8B is a schematic diagram 800B showing an example of generating HARQ feedback during scheduling of a plurality of data channels by DCI within a CC according to an embodiment of the present disclosure. In this example, within the entire downlink data channel group scheduled by DCI, the counter DAI for each downlink data channel within the entire group maintains the same value as the value signaled within the DCI. The terminal device 110 may generate one or two HARQ bits for each downlink data channel based on the number of TBs supported within this cell. The HARQ codebook may be generated in ascending order of the counter DAI. When any DCI within the PDCCHs 810 - 830 is missing, the terminal device 110 may generate one or two HARQ NACK bits based on the number of TBs supported for the missing DCI.

[0096] As shown in FIG. 8B, the DCI within the PDCCH 820 is missing. In this case, when one TB is supported, the terminal device 110 may generate one HARQ NACK bit for the missing DCI and generate a HARQ codebook 860 as shown by reference numeral 861. When two TBs are supported, a HARQ codebook 870 may be generated to have two HARQ NACK bits as shown by reference numeral 871.

[0097] Embodiment 2

[0098] In this embodiment, the terminal device 110 may generate N HARQ bits for each counter DAI. Here, N represents the maximum number of downlink data channels scheduled by DCI within the same HARQ feedback window (i.e., the same uplink data or control channel). This will be described in detail with reference to FIGS. 9A and 9B.

[0099] FIG. 9A is a schematic diagram 900A showing another generation example of HARQ feedback during scheduling of a plurality of data channels by DCI within a CC according to an embodiment of the present disclosure. In this example, within the entire group of downlink data channels scheduled by a single DCI, the counter DAI for each downlink data channel within the entire group maintains the same value as the value signaled within the DCI. The terminal device 110 may generate N HARQ bits for each counter DAI. The HARQ codebook may be generated in ascending order of the counter DAI. If M downlink data channels where M < N are scheduled by other DCI within the same feedback window, the terminal device 110 may fill the N HARQ bits with one or more NACK bits.

[0100] As shown in FIG. 9A, PDCCH 910 schedules four PDSCHs, namely PDSCH #0 to #3, and the c-DAI in PDCCH 910 of slot #0 is 1. PDCCH 920 schedules two PDSCHs, namely PDSCH #4 and #5, and the c-DAI in PDCCH 920 of slot #4 is 2. PDCCH 930 schedules two PDSCHs, namely PDSCH #6 and #7, and the c-DAI in PDCCH 930 of slot #6 is 3. Assume that downlink data is correctly received on PDSCHs #0 to #7. When one TB is supported, as shown by reference numeral 941, a HARQ codebook 940 filled with HARQ NACK bits may be generated. When two TBs are supported, as shown by reference numeral 951, a HARQ codebook 950 filled with HARQ NACK bits may be generated.

[0101] Note that the example of FIG. 9A is for illustration purposes only and does not limit the present disclosure. Any other suitable method is also possible.

[0102] In some embodiments, when it is determined that the counter DAI is missing, the terminal device 110 may generate N HARQ NACK bits for the corresponding downlink data channel group. This will be described with reference to FIG. 9B. FIG. 9B is a schematic diagram 900B showing another generation example of HARQ feedback during scheduling of a plurality of data channels by DCI within a CC according to an embodiment of the present disclosure. In this example, within the entire downlink data channel group scheduled by DCI, the counter DAI for each downlink data channel within the entire group maintains the same value as the value signaled within the DCI. The terminal device 110 may generate one or two HARQ bits for each downlink data channel based on the number of TBs supported within this cell. The HARQ codebook may be generated in ascending order of the counter DAI. When any DCI within PDCCHs 910 to 930 is missing, the terminal device 110 may generate N HARQ NACK bits based on the maximum scheduled PDSCH size within the feedback window. In this example, N = 4.

[0103] As shown in FIG. 9B, the DCI within PDCCH 920 is missing. In this case, when one TB is supported, the terminal device 110 may generate HARQ NACK bits for the missing DCI and may also generate HARQ codebook 960 as shown by reference numeral 961. When two TBs are supported, HARQ codebook 970 may be generated to have HARQ NACK bits as shown by reference numeral 971.

[0104] Embodiment 3

[0105] In this embodiment, the terminal device 110 may set the counter DAI for the downlink data channels within the downlink data channel group by incrementing the counter DAI by 1 for each subsequent downlink data channel in the DCI based on the order of reception on the downlink data channel, in other words, based on the index of the downlink data channel. Therefore, the terminal device 110 may generate the HARQ codebook based on the counter DAI and the number of downlink data channels within the downlink data channel group. This will be described in detail with reference to FIGS. 10A and 10B.

[0106] FIG. 10A is a schematic diagram 1000A showing another generation example of HARQ feedback during scheduling of a plurality of data channels by DCI in a CC according to an embodiment of the present disclosure. In this example, only the initial c-DAI signaled in the DCI is present, and the initial c-DAI means the c-DAI value of the first PDSCH. In some embodiments, the c-DAI value is incremented by 1 for each subsequent PDSCH in the scheduled order, and a modulo 16 operation is applied. In this case, since 8 PDSCHs can be scheduled at once by the DCI, the c-DAI needs to have a bit length of 4. The terminal device 110 may generate one or two HARQ bits for each PDSCH based on the number of TBs supported in the cell. The HARQ codebook may be generated in ascending order of c-DAI.

[0107] As shown in FIG. 10A, PDCCH 1010 schedules four PDSCHs of PDSCH#0 to #3, and the c-DAI in PDCCH 1010 of slot #0 is 1. PDCCH 1020 schedules five PDSCHs of PDSCH#4 and #5, and the c-DAI in PDCCH 1020 of slot #4 is 5. PDCCH 1030 schedules two PDSCHs of PDSCH#6 and #7, and the c-DAI in PDCCH 1030 of slot #6 is 7. Assume that downlink data is correctly received on PDSCH#0 to #7. When supporting one TB, the HARQ codebook 1040 may be generated. When supporting two TBs, the HARQ codebook 1050 may be generated.

[0108] Note that the example of FIG. 10A is for illustrative purposes only and does not limit the present disclosure. Any other suitable method is also possible.

[0109] In some embodiments, when it is determined that the counter DAI is missing, the terminal device 110 may generate NACK feedback for the corresponding downlink data channel group. This will be described with reference to FIG. 10B. FIG. 10B is a schematic diagram 1000B showing an example of generating HARQ feedback during scheduling of a plurality of data channels by DCI in a CC according to an embodiment of the present disclosure. In this example, only the initial c-DAI signaled in the DCI is present, and the initial c-DAI means the c-DAI value of the first PDSCH. The c-DAI values of the remaining PDSCHs in the scheduling group should be incremented by 1 continuously. In this case, since 8 PDSCHs can be scheduled at once by the DCI, it is necessary to extend the c-DAI. In some embodiments, the c-DAI may have a bit length greater than 2. For example, the c-DAI may have a bit length of 3 or 4. The terminal device 110 may generate one or two HARQ bits for each PDSCH based on the number of TBs supported in the cell. The HARQ codebook may be generated in ascending order of c-DAI.

[0110] As shown in FIG. 10B, since the DCI in the PDCCH 1020 is missing, the PDSCH #4 and PDSCH #5 are missing. In this case, when one TB is supported, the terminal device 110 may generate two HARQ NACK bits for the missing PDSCH as shown by reference numeral 1061, and may also generate a HARQ codebook 1060. When two TBs are supported, as shown by reference numeral 1071, a HARQ codebook 1070 may be generated to have four HARQ NACK bits.

[0111] Embodiment 4

[0112] In this embodiment, the downlink data channel group is divided into a set of a plurality of downlink data channels. The terminal device 110 may generate HARQ bits (also referred to as crc results) for each set of downlink data channels. Within a set of downlink data channels, a "BIT AND" operation (also referred to as an AND operation in this specification) is performed among the HARQ bits for the set of downlink data channels. That is, when the downlink data on a downlink data channel within one set of the set of downlink data channels is received inaccurately, the terminal device 110 may generate NACK feedback for the one set. When the downlink data on each downlink data channel within one set of the set of downlink data channels is received accurately, the terminal device may generate ACK feedback for the one set. In this way, the number of bits used for HARQ feedback can be reduced.

[0113] FIG. 11 is a schematic diagram 1100 showing another generation example of HARQ feedback during scheduling of a plurality of data channels by DCI in a CC according to an embodiment of the present disclosure. In this example, the terminal device 110 may generate one or two HARQ bits based on the number of TBs supported within the cell. The HARQ codebook may be generated in ascending order of c-DAI.

[0114] As shown in FIG. 11, PDCCH 1110 schedules four PDSCHs of PDSCH#0 to #3, and the c-DAI in PDCCH 1110 in slot #0 is 1. PDCCH 1120 schedules four PDSCHs of PDSCH#4 to #7, and the c-DAI in PDCCH 1120 in slot #4 is 2. PDSCH#0 to #3 are divided into two groups, group #0 and group #1. PDSCH#4 to #7 are divided into two groups, group #2 and group #3. Group #0 and group #1 are scheduled within slot #0 by PDCCH 1110, and group #2 and group #3 are scheduled within time slot #4 by PDCCH 1120.

[0115] Assume that downlink data is correctly received on PDSCH#0 to #7. The HARQ codebook may be summarized in Table 3. TIFF0007690987000005.tif171158 Here, crc0 is the crc result of PDSCH#0 (supporting only one TB), crc0(TB1) is the crc result of TB1 (PDSCH#0), and crc0(TB2) is the crc result of TB2 (PDSCH#0) (supporting two TBs).

[0116] Therefore, when supporting one TB, the HARQ codebook 1130 may be generated. When supporting two TBs, the HARQ codebook 1140 may be generated.

[0117] It should be noted that the example of FIG. 11 is for illustrative purposes only and does not limit the present disclosure. Any other suitable method is also possible. Although FIG. 11 shows the same c-DAI for each PDSCH within a group, this solution for the "AND" operation can also be applied to the c-DAI incremented for the PDSCHs in the scheduled order. 2. Example of HARQ feedback for CA

[0118] According to an embodiment of the present disclosure, in the case of CA, the terminal device 110 may receive downlink data from a plurality of downlink data channels scheduled by a single downlink control channel on a plurality of serving cells and within a plurality of monitoring occasions for the downlink control channel. In this case, the HARQ codebook may be generated in the order of reception on the downlink data channels scheduled within a single downlink control channel, the index of the serving cell, and the order of the PDCCH monitoring occasions for the downlink data channels. This will be described in detail with reference to FIGS. 12 to 15.

[0119] Embodiment 5

[0120] In this embodiment, the number of downlink data channels scheduled by a single DCI within a PDCCH monitoring occasion is the same for each serving cell. The HARQ codebook may be generated first in ascending order of the plurality of received PDSCHs, then in ascending order of the serving cell indexes, and finally in ascending order of the PDCCH monitoring occasions. This will be described in detail with reference to FIG. 12.

[0121] FIG. 12 is a schematic diagram 1200 showing an example of generation of HARQ feedback during scheduling of a plurality of data channels by DCI in a CA according to an embodiment of the present disclosure. In this example, for the entire downlink data channel group scheduled by DCI, the c-DAI for each downlink data channel within the group maintains the same value as the value signaled within the DCI, and the t-DAI is used to determine whether any detection is missing within several PDCCH monitoring occasions. The terminal device 110 may generate one or two HARQ bits for each downlink data channel based on the number of TBs supported within this cell.

[0122] As shown in FIG. 12, within PDCCH monitoring occasion #0, that is, within slot #0, each of PDCCH 1210 in the Pcell, PDCCH 1220 in Scell1, and PDCCH 1230 in Scell2 schedules four PDSCHs. The HARQ codebook may be compiled based on Table 4. TIFF0007690987000006.tif114156 Therefore, when supporting one TB, the HARQ codebook 1240 may be generated. When supporting two TBs, the number of HARQ bits should be doubled.

[0123] It should be noted that the example in FIG. 12 is for illustrative purposes only and does not limit the present disclosure. Any other suitable method is also possible.

[0124] Embodiment 6

[0125] In this embodiment, the time intervals scheduled by DCI within a monitoring occasion are the same for each serving cell. The HARQ codebook may be generated first in ascending order of the received plurality of PDSCHs, then in ascending order of the serving cell index, and finally in ascending order of the PDCCH monitoring occasion. This will be described in detail with reference to FIG. 13.

[0126] FIG. 13 is a schematic diagram 1300 showing another generation example of HARQ feedback during scheduling of a plurality of data channels by DCI in a CA according to an embodiment of the present disclosure. In this example, in the entire downlink data channel group scheduled by DCI, the c-DAI for each downlink data channel within the entire group maintains the same value as the value signaled within the DCI, and the t-DAI is used to determine whether any detection is missing within several PDCCH monitoring occasions. The terminal device 110 may generate one or two HARQ bits for each downlink data channel based on the number of TBs supported in this cell.

[0127] As shown in FIG. 13, within PDCCH monitoring occasion #0, that is, within slot #0, PDCCH 1310 in the Pcell schedules 4 PDSCHs when the subcarrier spacing (SCS) = 30 kHz, and PDCCH 1320 in Scell1 and PDCCH 1330 in Scell2 schedule 2 PDSCHs when SCS = 15 kHz. The HARQ codebook may be compiled based on Table 5. TIFF0007690987000007.tif131155 Therefore, when supporting one TB, a HARQ codebook 1340 may be generated. When supporting two TBs, the number of HARQ bits should be doubled.

[0128] Note that the example in FIG. 13 is for illustration purposes only and does not limit the present disclosure. Any other suitable method is also possible.

[0129] Embodiment 7

[0130] In this embodiment, the terminal device 110 may generate N HARQ bits for each c-DAI of each cell within the same PDCCH monitoring occasion. Here, N represents the maximum number of downlink data channels scheduled by a single DCI within the same monitoring occasion. When M downlink data channels by a DCI with M < N exist in other cells within the same monitoring occasion, the terminal device 110 may fill the N HARQ bits with one or more NACK bits. The HARQ codebook may be generated first in ascending order of the received plurality of PDSCHs, then in ascending order of the serving cell index, and finally in ascending order of the PDCCH monitoring occasion. This will be described in detail with reference to FIG. 14.

[0131] FIG. 14 is a schematic diagram 1400 showing another example of generating HARQ feedback during scheduling of a plurality of data channels by a single DCI within CA according to an embodiment of the present disclosure. In this example, within the entire downlink data channel group scheduled by a single DCI, the c-DAI for each downlink data channel within the entire group maintains the same value as the value signaled within the DCI, and the t-DAI is used to determine whether any detection is missing within several PDCCH monitoring occasions. The terminal device 110 may generate one or two HARQ bits for each downlink data channel based on the number of TBs supported within this cell.

[0132] As shown in FIG. 14, within the same PDCCH monitoring occasion #0, that is, within slot #0, PDCCH 1410 in the Pcell schedules 6 PDSCHs, PDCCH 1420 in Scell1 schedules 4 PDSCHs, and PDCCH 1430 in Scell2 also schedules 4 PDSCHs. The HARQ codebook may be compiled based on Table 6. TIFF0007690987000008.tif202157Therefore, when supporting one TB, the HARQ codebook 1440 may be generated. When supporting two TBs, the number of HARQ bits should be doubled.

[0133] It should be noted that the example in FIG. 14 is for illustrative purposes only and does not limit the present disclosure. Any other suitable method is also possible.

[0134] Embodiment 8

[0135] In this embodiment, the terminal device 110 may set the c-DAI for the downlink data channels in the downlink data channel group by incrementing the c-DAI by 1 for each subsequent downlink data channel in the DCI based on the order of reception on the downlink data channel, that is, based on the index of the downlink data channel. Therefore, the terminal device 110 may generate the HARQ codebook based on the c-DAI, the t-DAI, and the number of downlink data channels in the downlink data channel group. This will be described in detail with reference to FIG. 15.

[0136] FIG. 15 is a schematic diagram 1500 showing another generation example of HARQ feedback during scheduling of a plurality of data channels by DCI in a CA according to an embodiment of the present disclosure. In this example, only the initial c-DAI signaled within the DCI is present, and the initial c-DAI means the c-DAI value of the first PDSCH. In some embodiments, in the scheduled order, the c-DAI value is incremented by 1 for each subsequent PDSCH, and a modulo 16 operation is applied. In this case, since 8 PDSCHs may be scheduled by the DCI at a time, it is necessary to extend each of the c-DAI and the t-DAI. In some embodiments, each of the c-DAI and the t-DAI may have a bit length greater than 2. For example, each of the c-DAI and the t-DAI may have a bit length of 3 or 4. The HARQ codebook may be generated first in ascending order of the plurality of received PDSCHs, then in ascending order of the serving cell index, and finally in ascending order of the PDCCH monitoring occasion.

[0137] As shown in FIG. 15, within the same PDCCH monitoring occasion #0, that is, within slot #0, PDCCH 1510 in the Pcell schedules 8 PDSCHs, PDCCH 1520 in Scell1 schedules 4 PDSCHs, and PDCCH 1530 in Scell2 also schedules 4 PDSCHs. The HARQ codebook may be compiled based on Table 7. TIFF0007690987000009.tif202168 Therefore, when supporting one TB, the HARQ codebook 1540 may be generated. When supporting two TBs, the number of HARQ bits should be doubled.

[0138] Note that the example in FIG. 15 is for illustrative purposes only and does not limit the present disclosure. Any other suitable method is also possible.

[0139] In this way, for multiple downlink data channels scheduled by a single DCI, HARQ feedback extension can be realized. Example of method

[0140] Embodiments of the present disclosure provide communication methods implemented in a terminal device and a network device. Referring to FIGS. 16 to 19, these methods will be described below.

[0141] FIG. 16 is a diagram showing an exemplary communication method 1600 implemented in a terminal device according to some embodiments of the present disclosure. For example, method 1600 can be executed in a terminal device 110 as shown in FIG. 1. Hereinafter, for the sake of explanation, method 1600 will be described with reference to FIG. 1. Method 1600 can include additional blocks not shown and / or can omit some of the blocks shown, and it should be understood that the scope of the present disclosure is not limited in this regard.

[0142] In block 1610, the terminal device 110 receives from the network device 120 a DCI that schedules a plurality of data channels grouped into a plurality of groups. In some embodiments, the DCI includes an NDI field, and one of the bits in the NDI field corresponds to one of the data channel groups among the plurality of groups. In some embodiments, the MCS value may be shared among the plurality of groups. In some embodiments, the HARQ process may be shared among the data channels within each of the plurality of groups. In some alternative embodiments, the data channels within each of the plurality of groups may be associated with different HARQ processes. That is, depending on the signal quality, the HARQ process may or may not be shared among the data channels within each of the plurality of groups.

[0143] In block 1620, the terminal device 110 executes data transmission between the terminal device 110 and the network device 120 on a data channel based on DCI. In some embodiments, the terminal device 110 determines the number of data channels in each data channel group among the plurality of groups, determines the data channel group to which one of the bits corresponds based on the number of the data channels, and may perform data transmission on the data channel group based on the one of the bits.

[0144] In some embodiments, the terminal device 110 may determine the number of data channels based on the number of bits in the NDI field and the total number of scheduled data channels included in the DCI. In some embodiments, the terminal device 110 may determine the number of data channels by making the difference in the number of data channels between the plurality of groups not more than a first predetermined value. In some embodiments, the terminal device 110 may determine the number of data channels by making the number of groups having the same number of data channels among the plurality of groups more than a second predetermined value. In some embodiments, the terminal device 110 may determine the number of data channels based on upper layer signaling parameters from the network device 120.

[0145] In this way, fewer bits are used to indicate new data or retransmitted data for each data channel group. Thereby, the payload of the DCI can be reduced and the false detection rate can be reduced.

[0146] FIG. 17 shows another exemplary communication method 1700 implemented in a terminal device according to some embodiments of the present disclosure. For example, the method 1700 can be executed in the terminal device 110 as shown in FIG. 1. Hereinafter, for the sake of explanation, the method 1700 will be described with reference to FIG. 1. It should be understood that the method 1700 can include additional blocks not shown and / or some of the blocks shown can be omitted, and the scope of the present disclosure is not limited in this regard.

[0147] In block 1710, the terminal device 110 receives downlink data from the network device 120 on a plurality of downlink data channels scheduled by a single downlink control channel. In other words, the plurality of downlink data channels are scheduled by DCI within a single downlink control channel. In some embodiments, the terminal device 110 may receive downlink data from the network device 120 on at least one serving cell within at least one monitoring occasion for the downlink control channel.

[0148] In block 1720, the terminal device 110 transmits HARQ feedback regarding the downlink data to the network device 120 based on the counter DAI included in the DCI.

[0149] In some embodiments, the terminal device 110 may generate a HARQ codebook in the order of reception on a plurality of downlink data channels, the index of the serving cell, and the monitoring occasion for the downlink control channel. In some embodiments, the number of downlink data channels scheduled by a single downlink control channel within a monitoring occasion for the downlink control channel is the same for each serving cell. In some embodiments, the time interval scheduled by a single downlink control channel within a monitoring occasion for the downlink control channel is the same for each serving cell.

[0150] In some embodiments, the terminal device 110 may determine the number of HARQ bits based on the maximum number of downlink data channels scheduled by a single downlink control channel among serving cells within a monitoring occasion for the downlink control channel, and generate the HARQ codebook based on the number of HARQ bits. In some embodiments, the terminal device 110 may fill spare HARQ bits for the serving cell with NACK feedback according to a determination that the number of downlink data channels in the serving cell is less than the number of HARQ bits within the monitoring occasion for the downlink control channel.

[0151] In some embodiments, the terminal device 110 may determine the counter DAI for a plurality of downlink data channels by incrementing the counter DAI by 1 for each subsequent downlink data channel based on the order of reception on the plurality of downlink data channels, and generate the HARQ codebook based on the counter DAI, the number of downlink data channels received from the single downlink control channel, and the total DAI. In some embodiments, each of the counter DAI and the total DAI may have a bit length greater than 2.

[0152] In some embodiments, the terminal device 110 may set the same counter DAI for each of the downlink data in a plurality of downlink data channels, and generate a HARQ codebook based on the counter DAI and the number of the plurality of downlink data channels included in the DCI. In some embodiments where the HARQ feedback window is associated with a plurality of downlink data channel groups scheduled by a plurality of downlink control channels, if one of the plurality of downlink control channels is missing, the terminal device 110 may generate a NACK feedback for one of the plurality of groups scheduled by the one of the plurality of downlink control channels. In this specification, each downlink data channel group among the plurality of groups is scheduled by a single downlink control channel.

[0153] In some embodiments where the HARQ feedback window is associated with a plurality of downlink data channel groups scheduled by a plurality of downlink control channels, the terminal device 110 may determine the number of HARQ bits based on the maximum number of downlink data channels scheduled by a single downlink control channel within the HARQ feedback window, and generate the HARQ codebook based on the number of HARQ bits. In this specification, each downlink data channel group among the plurality of groups is scheduled by a single downlink control channel. In some embodiments, if the number of downlink data channels in the serving cell is less than the number of HARQ bits in the monitoring occasion for the downlink control channel, the terminal device 110 may fill the spare HARQ bits for the serving cell with NACK feedback.

[0154] In some embodiments, the terminal device 110 may determine the counter DAI for a plurality of downlink data channels by incrementing the counter DAI by 1 for each subsequent downlink data channel based on the order of reception on the plurality of downlink data channels, and generate a HARQ codebook based on the counter DAI and the number of the plurality of downlink data channels included in the DCI. In some embodiments, the counter DAI may have a bit length greater than 2.

[0155] In some embodiments where the plurality of downlink data channels include a plurality of groups of downlink data channels, the terminal device 110 may generate one or two HARQ bits for each group among the plurality of groups. In some embodiments, the terminal device 110 may obtain HARQ information bits by determining the HARQ information bits for each downlink data channel within one of the plurality of groups, and perform an AND operation on the HARQ information bits. Thereby, HARQ bits for HARQ feedback can be generated.

[0156] In this way, HARQ feedback extension can be realized for the plurality of downlink data channels scheduled by the DCI.

[0157] FIG. 18 shows an exemplary communication method 1800 implemented in a network device according to some embodiments of the present disclosure. For example, the method 1800 may be implemented in the network device 120 as shown in FIG. 1. Hereinafter, for the sake of explanation, the method 1800 will be described with reference to FIG. 1. It should be understood that the method 1800 may include additional blocks not shown and / or some of the blocks shown may be omitted, and the scope of the present disclosure is not limited in this regard.

[0158] As shown in FIG. 18, in block 1810, network device 120 generates DCI for scheduling a plurality of data channels grouped into a plurality of groups. In some embodiments, the DCI includes an NDI field, and one of the bits in the NDI field corresponds to one of the data channel groups of the plurality of groups. In some embodiments, the MCS value may be shared among the plurality of groups. In some embodiments, the HARQ process may be shared among the data channels within each of the plurality of groups. In some alternative embodiments, the data channels within each of the plurality of groups may be associated with different HARQ processes.

[0159] In some embodiments, network device 120 may determine the number of data channels within each of the plurality of groups and generate the NDI field by allocating bits to each of the data channel groups of the plurality of groups.

[0160] In some embodiments, network device 120 may determine the number of data channels based on the number of bits in the NDI field and the total number of scheduled data channels included in the DCI. In some embodiments, network device 120 may determine the number of data channels by making the difference in the number of data channels among the plurality of groups not exceed a first predetermined value. In some embodiments, network device 120 may determine the number of data channels by making the number of groups having the same number of data channels among the plurality of groups greater than a second predetermined value.

[0161] In some embodiments, network device 120 may transmit to terminal device 110 a higher layer signaling parameter indicating the number of data channels within each of the plurality of groups.

[0162] In block 1820, the network device 120 transmits DCI to the terminal device 110.

[0163] In this way, fewer bits are used to indicate new data or retransmitted data for each data channel group. As a result, the payload of the DCI can be reduced and the false detection rate can be reduced.

[0164] FIG. 19 shows an exemplary communication method 1900 implemented in a network device according to some embodiments of the present disclosure. For example, method 1900 may be implemented in network device 120 as shown in FIG. 1. Hereinafter, for the sake of explanation, method 1900 will be described with reference to FIG. 1. It should be understood that method 1900 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0165] As shown in FIG. 19, in block 1910, the network device 120 transmits downlink data to the terminal device 110 on a plurality of downlink data channels scheduled by DCI transmitted on a single downlink control channel.

[0166] In block 1920, the network device 120 receives HARQ feedback for the downlink data from the terminal device 110 based on the counter DAI included in the DCI.

[0167] In some embodiments, the network device 120 may receive a HARQ codebook generated in the order of reception on a plurality of downlink data channels, an index of a serving cell, and a monitoring occasion for a downlink control channel. In some embodiments, the number of downlink data channels scheduled by a single downlink control channel within a monitoring occasion for the downlink control channel may be the same for each serving cell. In some embodiments, the time interval scheduled by a single downlink control channel within a monitoring occasion for the downlink control channel may be the same for each serving cell.

[0168] In some embodiments, the network device 120 may receive HARQ bits, and the number of the HARQ bits is the maximum number of downlink data channels scheduled by a single downlink control channel within a monitoring occasion for the downlink control channel. In some embodiments where the number of downlink data channels is less than the number of HARQ bits, the network device 120 may receive spare HARQ bits filled with NACK feedback.

[0169] In some embodiments, the network device 120 may receive a HARQ codebook generated based on a counter DAI and the total DAI received from a single downlink control channel and the number of downlink data channels, where the counter DAI is determined for the plurality of downlink data channels by incrementing the counter DAI by 1 for each subsequent downlink data channel based on the order of reception on the plurality of downlink data channels. In some embodiments, each of the counter DAI and the total DAI has a bit length greater than 2.

[0170] In some embodiments, the network device 120 may receive a HARQ codebook generated based on a counter DAI and the number of downlink data channels included in the DCI, and the same counter DAI is set for the downlink data channels in the plurality of downlink data channels. In some embodiments where the HARQ feedback window is associated with a plurality of downlink data channel groups scheduled by a plurality of downlink control channels, the network device 120 may receive a NACK feedback for one of the plurality of groups scheduled by one of the plurality of downlink control channels according to a determination that one of the plurality of downlink control channels is missing.

[0171] In some embodiments where the HARQ feedback window is associated with a plurality of downlink data channel groups scheduled by a plurality of downlink control channels, the network device 120 may receive HARQ bits, and the number of the HARQ bits is the maximum number of downlink data channels scheduled by a single downlink control channel. In some embodiments, the network device 120 may receive spare HARQ bits filled with NACK feedback according to a determination that the number of downlink data channels is less than the number of HARQ bits.

[0172] In some embodiments, the network device 120 may receive a HARQ codebook generated based on a counter DAI and the number of a plurality of downlink data channels included in the DCI, and the counter DAI is determined for the plurality of downlink data channels by incrementing the counter DAI by 1 for each subsequent downlink data channel based on the order of reception on the plurality of downlink data channels. In some embodiments, the counter DAI has a bit length greater than 2.

[0173] In some embodiments where a plurality of downlink data channels include a plurality of groups of downlink data channels, the network device 120 may receive one or two HARQ bits generated for each group among the plurality of groups. In some embodiments, the network device 120 may receive one or two HARQ bits generated by performing an AND operation on HARQ information bits for a downlink data channel within one of the plurality of groups.

[0174] In this way, HARQ feedback extension can be realized for a plurality of downlink data channels scheduled by DCI. Example of device

[0175] FIG. 20 is a schematic block diagram of an apparatus 2000 suitable for implementing an embodiment of the present disclosure. The apparatus 2000 can be considered as another exemplary embodiment of the terminal device 110 or the network device 120 shown in FIG. 1. Therefore, the apparatus 2000 can be implemented in the terminal device 110 or the network device 120, or as at least a part thereof.

[0176] As shown, apparatus 2000 includes a processor 2010, a memory 2020 coupled to the processor 2010, a suitable transmitter (TX) and receiver (RX) 2040 coupled to the processor 2010, and a communication interface coupled to the TX / RX 2040. The memory 2010 stores at least a portion of a program 2030. The TX / RX 2040 is used for bidirectional communication. The TX / RX 2040 has at least one antenna to facilitate communication, although the access nodes referred to herein can actually have multiple antennas. The communication interface may represent any interface necessary for communication with other network elements, such as an X2 / Xn interface for bidirectional communication between eNB / gNB, an S1 / NG interface for communication between a Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and an eNB / gNB, a 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.

[0177] Assume that the program 2030 includes program instructions that, when executed by the relevant processor 2010 as described herein with reference to FIGS. 4 - 19, enable the apparatus 2000 to operate in accordance with embodiments of the present disclosure. The embodiments herein can be realized by computer software executable by the processor 2010 of the apparatus 2000, or by hardware, or by a combination of software and hardware. The processor 2010 can be configured to implement various embodiments of the present disclosure. Further, the combination of the processor 2010 and the memory 2020 can form a processing means 2050 suitable for implementing various embodiments of the present disclosure.

[0178] Memory 2020 may be of any type suitable for a local technology network and, by way of non-limiting example, may be implemented using any suitable data storage technology such as a non-transitory computer-readable storage medium, a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, a fixed memory, and a removable memory. Although only one memory 2020 is shown within device 2000, there may be several physically different memory modules within device 2000. Processor 2010 may be of any type suitable for a local technology network and, by way of non-limiting example, may include one or more of a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 2000 may have a plurality of processors, for example, an application-specific integrated circuit chip that is temporally dependent on a clock that synchronizes a main processor.

[0179] In general, the various embodiments of the present disclosure can be implemented in hardware or dedicated circuitry, 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, a microprocessor, or other computing device. Although the various aspects of the embodiments of the present disclosure are 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 can be implemented, by way of non-limiting example, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0180] 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 are executed within a device on a target physical processor or virtual processor to perform the processes or methods described above with reference to FIGS. 4 to 19. 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 functions of the program modules can be combined or divided among the program modules as needed. The machine-executable instructions of the program modules can be executed within a local or distributed device. In a distributed device, the program modules may be located in both local and remote storage media.

[0181] The program code for executing the method of the present disclosure may be described in any combination of one or more programming languages. These program codes are provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing equipment, and when executed by the processor or controller, the program codes implement the functions / operations specified in the flowchart and / or block diagram. The program code may 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.

[0182] The above program code can be implemented on a machine-readable medium, and the machine-readable medium may be any tangible medium that can be used by or associated with an instruction execution system, apparatus, or device, or that can contain or store a program. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing media. More specific examples of machine-readable storage media may include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0183] Note that although the operations have been described in a particular order for purposes of illustration, it should be understood that such operations need not be performed in the particular order shown or in sequential order, nor is it required that all of the operations described be performed, to obtain the desired result. In some cases, multitasking or parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Some features described in the context of individual embodiments may be combined in a single embodiment to be realized. Conversely, various features described in the context of a single embodiment may be implemented separately in multiple embodiments or in any suitable sub-combination.

[0184] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to 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 illustrative forms of implementing the claims.

Claims

1. Receive a single downlink control information (DCI) for scheduling a plurality of physical downlink shared channels (PDSCH) from a base station device, The single DCI includes a receiving unit that includes first information indicating values related to each of the plurality of PDSCHs, The receiving unit receives second information indicating the number of groups from the base station device, Based on the first information and the second information, a processing unit generates hybrid automatic repeat request (HARQ) information for each group of the plurality of PDSCHs scheduled by the single DCI grouped thereby A communication device.

2. The value includes a Start and Length Indicator Value (SLIV), The number of the plurality of PDSCHs scheduled by the DCI is transmitted according to the number of SLIVs indicated by the first information included in the single DCI The communication device according to claim 1.

3. The processing unit divides the groups into a first type and a second type, The number of PDSCHs included in each group belonging to the first type and the number of PDSCHs included in each group belonging to the second type are determined based on the following formula, M １ If M is 0 or greater, C is given by the first information, M is given by the second information, M １ indicates the number of groups belonging to the first type, M ２ indicates the number of groups belonging to the second type, K １ indicates the number of PDSCHs included in each group belonging to the first type, K ２ indicates the number of PDSCHs included in each group belonging to the second type The communication device according to claim 1.

4. When all the PDSCHs included in the group are accurately received, the processing unit generates an acknowledgement (ACK) as the HARQ information bit of the group, When at least one of the PDSCHs included in the group is inaccurately received, the processing unit generates a non-acknowledgement (NACK) as the HARQ information bit of the group The communication device according to claim 1.

5. Receive a single downlink control information (DCI) for scheduling a plurality of physical downlink shared channels (PDSCH) from a base station device, The single DCI includes first information indicating values related to each of the plurality of PDSCHs, receives second information indicating the number of groups from the base station apparatus, generates hybrid automatic repeat request (HARQ) information for each group for the plurality of PDSCHs scheduled by the single DCI grouped based on the first information and the second information A method for a communication device.

Images