WO2024031591A1

WO2024031591A1 - Method, device and computer storage medium of communication

Info

Publication number: WO2024031591A1
Application number: PCT/CN2022/111937
Authority: WO
Inventors: Xiaohong Zhang; Lin Liang; Gang Wang
Original assignee: Nec Corporation
Priority date: 2022-08-11
Filing date: 2022-08-11
Publication date: 2024-02-15

Abstract

Embodiments of the present disclosure relate to methods, devices and computer readable media of communication. A method of communication comprises: receiving, at a terminal device from a network device, initial transmission of a first set of transport blocks (TBs) each comprising one or more code block groups (CBGs) via a first number of physical downlink shared channels (PDSCHs); receiving, from the network device, a downlink control information (DCI) scheduling a second set of TBs comprising at least one retransmission of the first set of TBs via a second number of PDSCHs on multiple slots; and determining, at the terminal device, at least one CBG of the at least one retransmission of TB based on CBG transmission information (CBGTI) field in the DCI

Description

METHOD, DEVICE AND COMPUTER STORAGE MEDIUM OF COMMUNICATION

TECHNICAL FIELD

Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media of CBG-based transmission for multi-physical downlink shared channels (PDSCHs) on multiple cells or on multiple slots scheduled by a DCI.

BACKGROUND

A downlink control information (DCI) can be used by a network device (e.g., gNodeB) to schedule code block group (CBG) -based or transport-block (TB) -based single Physical Downlink Shared Channel (PDSCH) scheduling transmission. In NR Rel-17 B52.6GHz, single DCI scheduling multi-slot PDSCHs/PUSCHs by DCI format 1_1/0_1 is supported. In NR Rel-18 multi-carriers enhancements, single DCI scheduling multi-cell PDSCHs/PUSCHs by a new DCI format has been supported. A DCI may be also used by the network device to schedule CBG-based multiple PDSCHs transmission in multiple slots or multiple cells in NR Rel-18 or future NR release.

For XR traffic with large packet size, e.g., video traffic, supporting CBG based transmission for single DCI scheduling multiple PDSCH/PUSCHs is beneficial for capacity improvements. While whether and how to support CBG-based transmission for single DCI scheduling multi-slot PDSCHs/multi-cell PDSCHs is still for further study.

Upon receipt of the multiple CBG based transmissions via the PDSCHs scheduled by the DCI, a terminal device may transmit corresponding HARQ-acknowledgement (HARQ-ACK) feedbacks in a HARQ-ACK codebook. The HARQ-ACK codebook construction for CBG-based HARQ-ACK feedback for multiple CBG based PDSCHs scheduled by a DCI and the reduction of HARQ-ACK payload are still under discussion.

SUMMARY

In general, embodiments of the present disclosure provide methods, devices and computer storage media for communication during scheduling of multi-TTI in one downlink control channel.

In a first aspect, there is provided a method of communication. The method comprises: receiving, at a terminal device from a network device, initial transmission of a first set of transport blocks (TBs) each comprising one or more code block groups (CBGs) via a first number of physical downlink shared channels (PDSCHs) ; receiving, from the network device, a downlink control information (DCI) scheduling a second set of TBs comprising at least one retransmission of the first set of TBs via a second number of PDSCHs on multiple slots; and determining, at the terminal device, at least one CBG of the at least one retransmission of TB based on CBG transmission information (CBGTI) field in the DCI.

In a second aspect, there is provided a method of communication. The method comprises: transmitting, at a network device to a terminal device, a first set of transport blocks (TBs) each comprising one or more code block groups (CBGs) via a first number of physical downlink shared channels (PDSCHs) ; and transmitting, a second set of TBs comprising at least one retransmission of the first set of TBs via a second number of PDSCHs on multiple slots scheduled by a downlink control information (DCI) comprising a CBG transmission information (CBGTI) field.

In a third aspect, there is provided a method of communication. The method comprises: receiving, at a terminal device from a network device, data via a plurality of code block group (CBG) based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a first downlink control information (DCI) ; in accordance with determination that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, determining the HARQ-ACK codebook based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold configured by the network device, wherein the corresponding DCI is any one of the first DCI, the second DCI, the third DCI and the fourth DCI, and the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs; and transmitting the HARQ-ACK codebook on a PUCCH resource to the network device.

In a fourth aspect, there is provided a method of communication. The method comprises: transmitting, to a terminal device, data via a plurality of code block group (CBG) based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a first downlink control information (DCI) ; transmitting, to the terminal device, an indication that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based PDSCHs and PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook , wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs; and receiving the HARQ-ACK codebook on a PUCCH resource generated at the terminal device, wherein the HARQ-ACK codebook is determined based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold configured by the network device, and the corresponding DCI is any one of the first DCI, the second DCI, the third DCI and the fourth DCI.

In a fifth aspect, there is provided a method of communication. The method comprises: receiving, at a terminal device from a network device, data via a plurality of code block group (CBG) based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a downlink control information (DCI) ; generating a set of HARQ-acknowledgement (HARQ-ACK) positions in a HARQ-ACK codebook for HARQ-ACK information bits for each PDSCH of the plurality of CBG based PDSCHs scheduled by the DCI; and reporting HARQ-ACK information for the plurality of CBG based physical downlink shared channels (PDSCHs) in the HARQ-ACK codebook to the network device.

In a sixth aspect, there is provided a method of communication. The method comprises: transmitting, to a terminal device from a network device, data via a plurality of code block group (CBG) based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a downlink control information (DCI) ; and receiving HARQ-ACK information for the plurality of CBG based PDSCHs in a HARQ-ACK codebook from the terminal device.

In a seventh aspect, there is provided a method of communication. The method comprises: receiving, at a terminal device from a network device, data transmitted via a plurality of physical downlink shared channels (PDSCHs) on a plurality of cells scheduled by a first downlink control information (DCI) ; in accordance with determination that HARQ-acknowledgement (HARQ-ACK) information for the plurality of PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule code block groups (CBG) based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs, determining the HARQ-ACK codebook for the plurality of PDSCHs, wherein the HARQ-ACK codebook comprises TB-based sub-codebook and CBG-based sub-codebook; and transmitting the HARQ-ACK codebook to the network device.

In an eighth aspect, there is provided a method of communication. The method comprises: transmitting, to a terminal device from a network device, data transmitted via a plurality of physical downlink shared channels (PDSCHs) on a plurality of cells scheduled by a first downlink control information (DCI) ; transmitting, to the terminal device, an indication that HARQ-acknowledgement (HARQ-ACK) information for the plurality of PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule code block group (CBG) based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs, and receiving a HARQ-acknowledgement (HARQ-ACK) codebook for the plurality of PDSCHs generated at the terminal device, wherein the HARQ-ACK codebook comprises TB-based sub-codebook and CBG-based codebook.

Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Through the more detailed description of some embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:

FIG. 1 illustrates an example communication network in which some embodiments of the present disclosure can be implemented;

FIGs. 2A to 2D illustrate signaling charts illustrating process of communication according to some embodiments of the present disclosure.

FIG. 3A illustrates the initial transmission of a plurality of TBs via a first number of scheduled PDSCHs and HARQ-ACK feedback in accordance with some embodiments of the present disclosure.

FIG. 3B illustrates retransmission of one or more CBGs via a second number of scheduled PDSCHs in accordance with some embodiments of the present disclosure.

FIG. 4A illustrates the initial transmission of a plurality of TBs via a first number of scheduled PDSCHs according to one embodiment of the present discourse.

FIG. 4B illustrates retransmission of one or more CBGs via a second number of scheduled PDSCHs according to one embodiment of the present discourse.

FIG. 4C illustrates retransmission of one or more CBGs via a second number of scheduled PDSCHs and initial transmission of one or more new TBs via a plurality of scheduled PDSCHs according to one embodiment of the present discourse.

FIG. 5 illustrates the HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure.

FIG. 6 illustrates the HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure.

FIG. 7A illustrates a HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure, in which UE operates CBG-based HARQ-ACK bundling based on the No. of scheduled PDSCHs M by the DCI and a RRC configured value Q.

FIG. 7B illustrates a HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure, in which the first portion and the second portion are multiplexed on a HARQ-ACK codebook and transmitted to the network device via a same PUCCH.

FIG. 7C illustrates a HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure, in which first portion and the second portion are separately transmitted in two HARQ-ACK codebooks to the network device via two PUCCHs.

FIG. 8A illustrate a view of a single DCI scheduling multiple PDSCHs on multiple cells in accordance with some embodiments of the present disclosure.

FIG. 8B illustrates a view of a scheduling transmission when codeBlockGroupTransmissionDCI-1-X is provided for UE in accordance with some embodiments of the present disclosure.

FIG. 8C illustrates a view of a scheduling transmission when codeBlockGroupTransmissionDCI-1-X is not provided for UE in accordance with some embodiments of the present disclosure.

FIG. 9A illustrates the HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure, wherein the multi-cell scheduling DCI comprises one C-DAI or a pair of C-DAI and T-DAI.

FIG. 9B illustrates the HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure, wherein the multi-cell scheduling DCI comprises two C-DAIs or two pairs of C-DAI and T-DAI.

FIG. 10 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.

FIG. 11 illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure.

FIG. 12 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.

FIG. 13illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure.

FIG. 14 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.

FIG. 15 illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure.

FIG. 16 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.

FIG. 17 illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure.

FIG. 18 is a simplified block diagram of a device 1800 that is suitable for implementing embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principle of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitations as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.

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 skills in the art to which this disclosure belongs.

As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Small Data Transmission (SDT) , mobility, Multicast and Broadcast Services (MBS) , positioning, dynamic/flexible duplex in commercial networks, reduced capability (RedCap) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.

The term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , Network-controlled Repeaters, and the like.

The terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.

The terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz to 7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum. The terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.

The network device may have the function of network energy saving, Self-Organising Networks (SON) /Minimization of Drive Tests (MDT) . The terminal may have the function of power saving.

The embodiments of the present disclosure may be performed in test equipment, e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.

The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.

In one embodiment, the terminal device may be connected with 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 one may be 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 eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device. In one embodiment, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In one embodiment, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.

As used herein, the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’ The term ‘based on’ is to be read as ‘at least in part based on. ’ The term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’ The term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’ The terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.

In some examples, values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.

In NR Rel-17 B52.6GHz, single DCI scheduling multi-slot PDSCHs/PUSCHs by DCI format 1_1/0_1 is supported. In Rel-18 multi-carriers enhancements, single DCI scheduling multi-cell PDSCHs/PUSCHs by a new DCI format has been supported. For XR traffic with large packet size, e.g., video traffic, supporting CBG based transmission for single DCI scheduling multiple PDSCH/PUSCHs is beneficial for capacity improvements.

While whether and how to support CBG based transmission for single DCI scheduling multi-slot PDSCHs/multi-cell PDSCHs is still for further study. How to perform HARQ-ACK codebook construction for CBG based HARQ-ACK feedback needs to be solved. Further, HARQ-ACK payload for CBG based HARQ-ACK feedback should be reduced. The CBG indication information for retransmission reception with less indication bits should be design so as to indicate for UE which CBG (s) are scheduled to be retransmitted in the CBG based retransmission for single DCI scheduling multi-slot PDSCHs/multi-cell PDSCHs.

Example embodiments of the present disclosure provide a mechanism to solve the above discussed issues. The example embodiments of the present disclosure can enable CBG based retransmission for multi-slot PDSCHs scheduled by a single DCI for XR traffic, and design DCI field for CBG indication for multi-slot PDSCH retransmission scheduling. The example embodiments of the present disclosure further can construct Type 2 HARQ-ACK codebook for CBG-based multi-slot PDSCH (s) scheduled by a DCI and reduce the HARQ-ACK overhead or redundancy. The example embodiments of the present disclosure still further can enable CBG based retransmission for multi-cells PDSCHs scheduled by a single DCI for XR traffic, and construct Type 2 HARQ-ACK codebook for CBG-based multi-cell PDSCH (s) scheduled by a DCI. Principles and some example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

EXAMPLE OF COMMUNICATION NETWORK

FIG. 1 illustrates a schematic diagram of an example communication network 100 in which some embodiments of the present disclosure can be implemented. As shown in FIG. 1, the communication network 100 may 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 is to be understood that the number of devices in FIG. 1 is given for the purpose of illustration without suggesting any limitations to the present disclosure. The communication network 100 may include any suitable number of network devices and/or terminal devices adapted for implementing implementations of the present disclosure.

As shown in FIG. 1, the terminal device 110 may communicate with the network device 120 via a channel such as a wireless communication channel. The communications in the communication network 100 may conform to any suitable standards 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) and the like. Furthermore, the communications may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols.

The terminal device 110 may transmit uplink data to the 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 forms are also feasible. In some embodiments, the terminal device 110 may receive downlink data from the 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 forms are also feasible.

The terminal device 110 may receive a DCI, e.g., data transmission configuration from the 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 forms are also feasible.

The terminal device 110 may transmit uplink control information (UCI) , e.g., HARQ feedback information to the 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 forms are also feasible.

The network device 120 may provide a plurality of serving cells (not shown herein) for the terminal device 110, for example, a primary cell (PCell) , a primary secondary cell (PSCell) , a secondary cell (SCell) , a special cell (sPCell) or the like. Each of the serving cells may correspond to a CC. The terminal device 110 may perform transmission with the network device 120 via a CC. The terminal device 110 may also perform transmission with the network device 120 via multiple CCs, for example, in case of carrier aggregation (CA) .

The network device 120 may schedule downlink data transmissions via different CCs in various manners. For example, the network device 120 may schedule TB-based single PDSCH transmission by a DCI or TB-based multi-PDSCHs transmissions by a DCI on a CC that is configured with TB-based transmission. Additionally or alternatively, the network device 120 may schedule CBG-based single PDSCH transmission by a DCI or CBG-based multi-PDSCHs transmissions by a DCI on a CC that is configured with CBG-based transmission. The multi-PDSCH can be either on multiple cells or on multiple slots

The terminal device 110 may then generate a HARQ-ACK codebook comprising HARQ feedbacks of the downlink data transmissions.

FIG. 2A to FIG. 2D each illustrates a signaling flow for communications according to some embodiments of the present disclosure;

FIG. 2A shows a signaling chart illustrating process 200 of communication according to some embodiments of the present disclosure. For the purpose of discussion, the process 200 will be described with reference to FIG. 1. The process 200 may involve the terminal device 110 and the network device 120 in FIG. 1. It is to be understood that the steps and the order of the steps in FIG. 2A are merely for illustration, and not for limitation. For example, the order of the steps may be changed. Some of the steps may be omitted or any other suitable additional steps may be added.

As shown in FIG. 2A, the network device 120 transmits 208, to a terminal device 110, initial transmission of a first set of transport blocks (TBs) 210 each comprising one or more CBGs via a first number of PDSCHs scheduled by a single DCI.

As shown in FIG. 2A, the terminal device 110 receives 212 the initial transmission of a first set of transport blocks (TBs) 210 each comprising one or more CBGs via a first number of PDSCHs scheduled a single DCI.

As shown in FIG. 2A, the network device 120 transmits 220 a DCI 222 scheduling a second set of TBs comprising at least one retransmission of the first set of TBs via a second number of PDSCHs on multiple slots.

As shown in FIG. 2A, the terminal device 110 receives 224 the DCI 222 scheduling a second set of TBs comprising at least one retransmission of the first set of TBs via a second number of PDSCHs on multiple slots.

As shown in FIG. 2A, the network device 120 transmits 226 a second set of TBs 228 comprising at least one retransmission of the first set of TBs via a second number of PDSCHs on multiple slots scheduled by a DCI comprising a CBGTI field.

As shown in FIG. 2A, the terminal device 110 determines 230 at least one CBG of the at least one retransmission of the second set of TBs based on CBGTI field indication in the DCI.

By the process as shown in FIG. 2A, the scheme of CBG-based multi-cell PDSCHs scheduling retransmission can be supported.

FIG. 2B shows a signaling chart illustrating process 200 of communication according to some embodiments of the present disclosure. For the purpose of discussion, the process 200 will be described with reference to FIG. 1. The process 200 may involve the terminal device 110 and the network device 120 in FIG. 1. It is to be understood that the steps and the order of the steps in FIG. 2B are merely for illustration, and not for limitation. For example, the order of the steps may be changed. Some of the steps may be omitted or any other suitable additional steps may be added.

As shown in FIG. 2B, the network device 120 transmits 208, to terminal device 110, data 210 via a plurality of CBG based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a first DCI.

As shown in FIG. 2B, the terminal device 110 receives 212, from a network device 120, data 210 via a plurality of CBG based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a first DCI.

As shown in FIG. 2B, the network device 120 transmits to terminal device, indication that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a DCI and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook.

As shown in FIG. 2B, the terminal device 110 receives 218 the indication and in accordance with determination that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook: determine 218 the HARQ-ACK codebook based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold configured by the network device, wherein the corresponding DCI is any one of the first DCI, the second DCI, the third DCI and the fourth DCI, and the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs.

As shown in FIG. 2B, the terminal device 110 transmits 222 the HARQ-ACK codebook 220 on the PUCCH resource to the network device 120.

As shown in FIG. 2B, the network device 120 receives the HARQ-ACK codebook 220 on the PUCCH resource generated at the terminal device, wherein the HARQ-ACK codebook is determined based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold T generated by the network device.

By the process of FIG. 2B, the CBG-based Type 2 HARQ-ACK codebook can be determined for multi-slot PDSCHs scheduling.

FIG. 2C shows a signaling chart illustrating process 200 of communication according to some embodiments of the present disclosure. For the purpose of discussion, the process 200 will be described with reference to FIG. 1. The process 200 may involve the terminal device 110 and the network device 120 in FIG. 1. It is to be understood that the steps and the order of the steps in FIG. 2C are merely for illustration, and not for limitation. For example, the order of the steps may be changed. Some of the steps may be omitted or any other suitable additional steps may be added.

As shown in FIG. 2C, the network device 120 transmits 208 to terminal device 110 data 210 via a plurality of CBG based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a DCI.

As shown in FIG. 2C, the terminal device 110 receives 212 data via a plurality of CBG based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a DCI;

As shown in FIG. 2C, the terminal devices 110 generates 212 a set of HARQ-acknowledgement (HARQ-ACK) positions in a HARQ-ACK codebook for HARQ-ACK information bits for each PDSCH of the plurality of CBG based PDSCHs scheduled by the DCI.

As shown in FIG. 2C, the terminal device 110 reports 214 HARQ-ACK information 216 for the plurality of CBG based physical downlink shared channels (PDSCHs) in the HARQ-ACK codebook to the network device.

As shown in FIG. 2C, the network device 120 receives 218 HARQ-ACK information 216 for the plurality of CBG based PDSCHs in a HARQ-ACK codebook from the terminal device.

By the process of FIG. 2C, HARQ-acknowledgement (HARQ-ACK) positions in a HARQ-ACK codebook for HARQ-ACK information bits for each PDSCH of the plurality of CBG based PDSCHs scheduled by the DCI can support the CBG based multi-slot PDSCHs scheduling transmission.

FIG. 2D shows a signaling chart illustrating process 200 of communication according to some embodiments of the present disclosure. For the purpose of discussion, the process 200 will be described with reference to FIG. 1. The process 200 may involve the terminal device 110 and the network device 120 in FIG. 1. It is to be understood that the steps and the order of the steps in FIG. 2D are merely for illustration, and not for limitation. For example, the order of the steps may be changed. Some of the steps may be omitted or any other suitable additional steps may be added.

As shown in FIG. 2D, the network device 120 transmits 208 to terminal device 110 data 210 transmitted via a plurality of physical downlink shared channels (PDSCHs) on a plurality of cells scheduled by a first DCI.

As shown in FIG. 2D, the terminal device 110 receives 212 data 210 transmitted via a plurality of PDSCHs on a plurality of cells scheduled by first a DCI.

As shown in FIG. 2D, in accordance with determination that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs, the terminal device 110 determines a HARQ-ACK codebook for HARQ-ACK information for the plurality of CBG based PDSCHs, wherein the HARQ-ACK codebook comprises TB-based sub-codebook and CBG-based sub-codebook.

As shown in FIG. 2D, the terminal device 110 transmits HARQ-ACK codebook, to the network device.

As shown in FIG. 2D, the network device 120 receives HARQ-ACK codebook.

By the process of FIG. 2D, the HARQ-ACK codebook generated can support CBG-based multi-cell PDSCHs scheduling transmission scheduled by a single DCI.

EXAMPLE OF CBG BASED RETRANSMISSION FOR MULTI-SLOT PDSCHS SCHEDULING

In the current technology, a PDSCH transmission for a UE, configured by the gNB (for example, RRC signaling) , is based on each cell, that is to say, each serving cell can be configured with CBG-based transmission or TB-based transmission. When the UE receives a PDSCH on a cell configured with CBG-based transmission scheduled by DCI format 1_1, it means that this PDSCH transmission is based on CBG, whereas when the UE receives a PDSCH on a cell configured with CBG-based transmission scheduled by DCI format 1_0, it means that this PDSCH transmission is based on TB even this cell is configured with CBG-based PDSCH transmission.

In the current technology, the current DCI format 1_1 can be used to schedule one PDSCH in one cell configured with CBG-based transmission. When the current DCI format 1_1 is used to schedule one PDSCH in one cell configured with CBG-based transmission, the PDSCH transmission (especially, retransmission of the unsuccessfully decoded CBGs in a TB) can be based on CBG, whereas when the DCI format 1_1 is used to schedule multi-slot PDSCHs, the PDSCH transmission based on CBG is not supported.

In the current technology, a UE is only provided a PDSCH-CodeBlockGroupTransmission for a serving cell, if the UE receives one PDSCH transmission scheduled by current DCI format 1_1 on the cell, the PDSCH transmission is based on CBG, that includes CBGs of a transport block; and if the UE receives multi-slot PDSCHs transmission on a serving cell scheduled by current DCI format 1_1, each PDSCH transmission is based on TB and the serving cell is not expected to be configured with CBG-based PDSCH transmission.

In order to enable CBG based retransmission for multi-slot PDSCHs scheduled by a single DCI for XR traffic, the present disclosure introduce a new RRC parameter, MultiPDSCH-CodeBlockGroupTransmission.

In one embodiment of the present disclosure, CBG configuration for multi-slot PDSCH (s) scheduling and CBG configuration single PDSCH scheduling for UE are separated by introducing a new RRC parameter, MultiPDSCH-CodeBlockGroupTransmission. In this way, in contrary to provide a PDSCH-CodeBlockGroupTransmission for a serving cell to UE, when an RRC parameter MultiPDSCH-CodeBlockGroupTransmission for a serving cell is provided to UE, if the UE receives multi-slot PDSCHs scheduled by DCI format 1_1, each PDSCH transmission is based on CBG that includes CBGs of each TB. That is to say, the MultiPDSCH-CodeBlockGroupTransmission for a serving cell is functioned as a switch to enable/disable CBG-based transmission for scheduled multi-slot PDSCH (s) .

Further, the maxCodeBlockGroupsPerTransportBlock for single PDSCH transmission and the maxCodeBlockGroupsPerTransportBlock for multiple PDSCH transmission can be separately configured. For example, for the single PDSCH transmission, the maxCodeBlockGroupsPerTransportBlock can be configured to be a slightly large value, whereas for the multiple PDSCH transmission, the maxCodeBlockGroupsPerTransportBlock can be configured to be a slightly small value such that the DCI overhead and HARQ-ACK overhead can be reduced. Thus, it provides flexibility for CBG configuration of multi-PDSCH scheduling and helps gNB to control HARQ-ACK payload and DCI overhead.

In another embodiment of present disclosure, a UE also can be provided a PDSCH-CodeBlockGroupTransmission for a serving cell as provided in the current technology. However, relax the restriction in the current technology, in the new design, it can stipulate that allows UE receive a PDSCH or multi-slot PDSCHs scheduled by DCI format 1_1 on the cell, each PDSCH transmission is based on CBG that includes CBGs of a transport block.

EXAMPLE OF DCI FIELD DESIGN FOR CBG INDICATION FOR ONE OR MULTI-SLOT PDSCHS RETRANSMISSION SCHEDULING

When some CBGs in one TB are not successfully transmitted in initial transmission, the network device (e.g., gNB) can schedule the unsuccessfully transmitted CBGs, rather than the whole TB, to be retransmitted. The terminal device (e.g. UE) needs to know some information about the retransmitted CBGs. The network device needs to indicate the UE that which CBGs are retransmitted so as to facilitate the UE to receive the retransmitted CBGs and combine the retransmitted CBGs with the initially-received CBGs to decode them. In the DCI received from the network device, there is CBGTI indicating that which CBGs are retransmitted. For CBG-based retransmission for multi-slot PDSCHs scheduling, the CBGTI field will be very large, especially when the maximum of CBGs per TB and the maximum of TBs scheduled by a DCI are large, so it should be designed so as to reduce the DCI overhead, and how to reduce the DCI overhead is also under discussion.

In the current technology, when the DCI format 1_1 is used to schedule one PDSCH on one cell, the DCI is provided with the CBGTI so as to inform UE which CBGs are retransmitted, if the bit width of the CBGTI is 0, it means that higher layer parameter codeBlockGroupTransmission for PDSCH is not configured for it, otherwise the bit width of the CBGTI is , 2, 4, 6, or 8 bits as defined in Clause 5.1.7 of [6, TS38.214] , determined by the higher layer parameters maxCodeBlockGroupsPerTransportBlock and maxNrofCodeWordsScheduledByDCI for the PDSCH.

For initial transmission of a TB as indicated by the 'New Data Indicator' field of the scheduling DCI, the UE may assume that all the CBGs of the TB are present. For New data indicator, the bit width of it is 1 bit if the number of scheduled PDSCH indicated by the Time domain resource assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined based on the maximum number of schedulable PDSCH among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, where each bit corresponds to one scheduled PDSCH as defined in clause 5.1.3 in [6, TS 38.214] .

For a retransmission of a TB as indicated by the 'New Data Indicator' field of the scheduling DCI, the UE may assume that:

(i) the 'CBGTI' field of the scheduling DCI indicates which CBGs of the TB are present in the transmission, wherein a bit value of '0' in the CBGTI field indicates that the corresponding CBG is not transmitted and '1' indicates that it is transmitted;

(ii) if the 'CBG flushing out information' (CBGFI) field of the scheduling DCI is present, 'CBGFI' set to '0' indicates that the earlier received instances of the same CBGs being transmitted may be corrupted, and 'CBGFI' set to '1' indicates that the CBGs being retransmitted are combinable with the earlier received instances of the same CBGs; and

(iii) CBG contains the same CBs as in the initial transmission of the TB.

As discussed above, it can be seen that information bits in CBGTI field have an in-order one-to-one mapping with CBGs of a TB, the value 1 of CBGTI field means that the corresponding CBG is retransmitted, and value 0 of CBGTI field means that the corresponding CBG has been initially successfully transmitted and is not retransmitted, and thus, if bit-mapping indication for CBG of a TB in CBGTI field is still used for CBG based multi-slot PDSCHs scheduled by a DCI, the bit width of CBGTI in in the DCI will be quite large, and equal to the product of the higher layer parameters maxCodeBlockGroupsPerTransportBlock and the maximum number of schedulable PDSCH among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH . Therefore, the bit width of the CBGTI will be quite large, and the DCI overhead will be very large, especially when maxCodeBlockGroupsPerTransportBlock is large. It is desired to reduce the bit width of CBGTI and thus reduce the DCI overhead.

In the following, it will describe how to design the CBGTI so as to reduce DCI overhead with reference to FIG. 3A to FIG. 4C.

In one embodiment of the present disclosure, the ‘CBG transmission information’ (CBGTI) field of DCI format 1_1 is of length M·N bits, where M is is the value of the maximum number of schedulable PDSCH among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, i.e., the maximum number of scheduled PDSCH by single DCI, N is the maximum number of CBGs per TB configured by maxCodeBlockGroupsPerTransportBlock. If M>1, the CBGTI field bits are mapped such that the first set of N bits starting from the MSB corresponds to the first TB while the m ^th set of N bits corresponds to a m ^th TB, if scheduled. Each set of N bits in the CBGTI field have an in-order one-to-one mapping with the N CBGs of the TB, with the MSB mapped to CBG#0. When the actual number of CBGs of an initial TB n is smaller than N, bit value 0 will be padded in the last N-n positions.

FIG. 3A illustrates the initial transmission of a plurality of TBs via a first number of scheduled PDSCHs and HARQ-ACK feedback in accordance with some embodiments of the present disclosure, and FIG. 3B illustrates retransmission of one or more CBGs via a second number of scheduled PDSCHs in accordance with some embodiments of the present disclosure.

In the embodiment as shown in FIG. 3A and FIG. 3B the ‘CBG transmission information’ (CBGTI) field of DCI format 1_1 is of length M bits when PDSCH-CodeBlockGroupTransmission and pdsch-TimeDomainResourceAllocationListForMultiPDSCH are provided for UE, where M is the value of the maximum number of schedulable PDSCH among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH configured by the network device. If M>1, the CBGTI field bits are mapped such that the first bit starting from the MSB corresponds to the first TB transmitted in the first scheduled PDSCH while the m ^th bit corresponds to a m ^th TB transmitted in the m ^th scheduled PDSCH. That is to say, each of M bits corresponds to one PDSCH of the set of PDSCHs on multiple slots scheduled by the DCI. The number of actually scheduled PDSCHs can be M or less than M. The scheduled set of PDSCHs by the DCI can be used for retransmission of at least one TB, which is not successfully decoded by UE, and also can be used for transmitting new TBs which is newly scheduled by the network device. That is to say, a portion of the M bits correspond to the retransmission, and the other portion of M bits correspond to the new transmission.

In this embodiment, each bit of the bits, which correspond to the retransmissions, in M bits of the CBGTI field has a bit mapping relationship with one TB of the multiple retransmitted TBs in respective M multiple PDSCHs scheduled by a DCI. The value of a bit of the bits, which are corresponding to the at least one retransmission, in the CBGTI field indicates that whether retransmission of one TB via a corresponding PDSCH includes at least one unsuccessfully transmitted CBG or all CBGs. For example, the bit value 1 means that at least one unsuccessfully transmitted CBG of one retransmitted TB is scheduled to be retransmitted, and the bit value 0 means that all CBGs of one retransmitted TB, at least one CBG of which is unsuccessfully decoded, are scheduled to be retransmitted, i.e., all CBGs (regardless of the unsuccessfully decoded CBGs or the successfully decoded CBGs) of a TB are scheduled to be retransmitted.

When UE receives the initial transmitted TBs, the UE decodes the initial transmission of the first set of TBs, and stores each CBG decoding result of each TB, and reports the decoding result to the gNB. According to the decoding result, the gNB is configured to retransmit at least one TB, which is not successfully decoded by UE. When the number of the at least one TB is less than the number M, there is still some PDSCHs, which are free and can be used for new transmission of other TBs. The gNB may be configured to transmitted the unsuccessfully initially transmitted CBG or CBGs of one retransmitted TB in one TB in one respective scheduled PDSCH, and cannot retransmit the unsuccessfully initially transmitted CBGs of a TB in two or more different retransmitted TBs. In response to receive the at least one retransmitted TB, the UE decodes the at least one retransmitted CBG of the at least one retransmitted TB based on the stored decoding result and the value of each bit in the CBGTI field. UE determines the indexes of scheduled retransmitted CBGs of a TB-based on its decoding results/ACK&NACK feedback for the initial transmission for the corresponding TB. . In this way, the UE is configured to store CBG level decoding results (A/N) of the initial TB transmission until the retransmission is scheduled.

In this way, the value of each bit, in the portion corresponding to the retransmission, in the M bits CBGTI field indicates to UE only that the retransmission includes unsuccessfully decoded CBGs of one retransmitted TB or all CBGs of one retransmitted TB, rather than whether a specific CBG included in the TB is present or not as indicated in the current technology. Therefore, it reduces the needed CBG information bits in CBGTI field for CBG based multi-slot PDSCH scheduling. For example, for the legacy solution, if M=8, N=4, 32-bit CBGTI is needed, while with our solution, 8-bit CBGTI is enough.

As shown in FIG. 3A, in the initial transmission, four TBs are transmitted in four scheduled PDSCH (i.e. PDSCH #0, PDSCH #1, PDSCH #2, PDSCH #3) in multi-slots on cell CC#1, and the maximum number of CBGs per TB is configured to be 2. The bits of CBGTI in DCI format 1_1 is of length 4 bits, where 4 is the value of the maximum number of schedulable PDSCH among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH. As shown in FIG. 3A, the UE generates a HARQ-ACK codebook comprising results/ACK&NACK feedback for the initial CBG based transmission for the corresponding TBs, and transmits the HARQ-ACK codebook via a PUCCH #0 to the gNB.

As shown in FIG. 3B, in the retransmission, CBG with index #1 transmitted in PDSCH #1 and CBG with index #0 transmitted in PDSCH #2 are not successfully transmitted, and the gNB then schedules two PDSCHs in multi-slots, i.e. PDSCH #4 and PDSCH #5 by a multi-slot scheduling DCI to perform retransmission, and in this illustrated embodiment, the number of scheduled two PDSCHs PDSCH #4 and PDSCH #5 is less than four and these two PDSCH #4 and PDSCH #5 are both used for retransmission. However, the person skilled in the art can understand that, when four PDSCHs are scheduled, the other two PDSCHs can be used for newt transmission, and the value of the bit of the CBGTI can be changed accordingly. As shown in FIG. 3B, in the retransmission, as shown in FIG. 3B, the CBGTI has four bits, wherein first two bits of value 1 indicates that only unsuccessfully transmitted CBG or CBGs of retransmitted TB is scheduled to be retransmitted, for example, in PDSCH #4, the CBG with index #1 initially transmitted in PDSCH #1 is scheduled to be retransmitted, and in PDSCH #5, the CBG with index #0 initially transmitted in PDSCH #2 is scheduled to be retransmitted; and two bits of value 0 of CBGTI means that the bits are padding value 0. When two other PDSCHs are used for new transmission, the two bits of value 0 in FIG. 3B can be changed to two bits of value 1 which mean that the new two TBs are scheduled to be transmitted, respectively.

In one embodiment of the present disclosure, the ‘CBG transmission information’ (CBGTI) field of DCI format 1_1 is of length a constant bit, preferably, 1 bit when higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH and PDSCH-CodeBlockGroupTransmission are provided. That is to say, the value of CBGTI field indicates that whether retransmissions via all PDSCHs scheduled by the DCI include a set of unsuccessfully transmitted CBGs of each retransmitted TB or all CBGs of each retransmitted TB. The person skilled in the art should be understood that the bith width of CBGTI field of DCI format 1_1 can be other constant, as long as the value can indicates that all retransmissions are TB-based (all CBGs of each TB) or CBG-based (a set of unsuccessfully transmitted CBGs of each retransmitted TB) .

The bit value 1 means that CBG-based transmissions for one or more TB retransmission are scheduled, UE determines the indexes of scheduled retransmitted CBGs of one or more TBs based on its decoding results/ACK&NACK feedback for the initial transmission for the corresponding TB (s) . In this way, the value 1 of CBGTI field of 1 bit indicates that all retransmissions via PDSCHs scheduled by the DCI include only a set of unsuccessfully transmitted CBGs of each retransmitted TB. That is to way, the PDSCH retransmissions scheduled by DCI are all CBG-based. The bit value 0 of CBGTI field of 1 bit indicates that all retransmissions via PDSCHs scheduled by the DCI include all CBGs of each retransmitted TB. That is to say, the PDSCH retransmissions scheduled by DCI are all whole initial TBs retransmissions.

In this embodiment, the UE is also configured to store the decoding result of each CBG in response to decode the initial transmitted one or more TBs, and in response to receive the retransmitted TB or TBs, the UE is further configured to decode the retransmitted CBG or CBGs based on the stored decoding result and the value of CBGTI field of 1 bit. In this way, the UE is configured to store decoding results (A/N) of the initial TB transmission until the retransmission is scheduled. In this embodiment, small bit width of CBGTI and DCI overhead can be achieved and UE needs to store decoding results (A/N) of the initial TB transmission until the retransmission is scheduled. In case, multiple retransmissions of a TB are scheduled, UE needs to update decoding results (A/N) of each CBG of the TB based on last retransmission reception until new data with the same HARQ process of the TB is scheduled.

FIG. 4A illustrates the initial transmission of a plurality of TBs via a first number of scheduled PDSCHs according to one embodiment of the present discourse, FIG. 4B illustrates retransmission of one or more CBGs via a second number of scheduled PDSCHs according to one embodiment of the present discourse, and FIG. 4C illustrates retransmission of one or more CBGs via a second number of scheduled PDSCHs and initial transmission of one or more new TBs via a plurality of scheduled PDSCHs according to one embodiment of the present discourse.

In one embodiment of the present disclosure, as shown in FIGs. 4A to 4C, the ‘CBG transmission information’ (CBGTI) field of DCI format 1_1 is of length H bits (H>N, where N is the maximum number of CBGs per TB configured by maxCodeBlockGroupsPerTransportBlock configured by the network device) , which is configured by RRC for DCI format 1_1.

If H≥N·L, where L is the number of scheduled CBG based PDSCHs by DCI format 1_1, the CBGTI field bits are mapped such that the first set of N bits starting from the MSB corresponds to the first TB in the first scheduled PDSCH while the m-th set of N bits corresponds to a m-th TB in the m-th scheduled PDSCH, that is to say, there are N bits configured for CBG information indication of each PDSCH for transmitting one TB (regardless the retransmitted TB or the newly transmitted TB) . For a retransmission of a TB as indicated by the 'New Data Indicator' field of the scheduling DCI, the UE may assume that a bit value of '0' in the CBGTI field indicates that the corresponding CBG is not transmitted or the bit is padded with value 0, and value '1' indicates that the corresponding CBG is transmitted. In this condition, the channel quality may be poor and the bit width of CBGTI can be configured to a large value, for example H≥N·L.

In this way, in accordance with determining that H≥N*L, where L is the number of PDSCHs for CBG-based transmission actually scheduled by the single DCI, and these PDSCHs can be used for the retransmission of unsuccessful transmitted TB or TBs and initial transmitted new TB or TBs (if any) . The bits in the CBGTI field has a first portion for indicating the retransmission of unsuccessful transmitted TB or TBs, a second portion for indicating the initial transmitted new TB or TBs, and a third portion for the padding value.

In the case that the actual number N1 of CBGs included in each TB is equal to N, in the first portion, the first set of N bits in the CBGTI field have an in-order one-to-one mapping with N CBGs of the first TB in the first scheduled PDSCH, and the m-th set of N bits in the CBGTI field have an in-order one-to-one mapping with N CBGs of the m-th TB in the m-th scheduled PDSCH.

In the case that the actual number N1 of CGBs included in one TB transmitted in one PDSCH is less than N, in the first portion, the N bits for this PDSCH comprise the bits corresponding to the actual number of CBGs for this PDSDCH and the padding bits corresponding to a (N-N1) paddling value.

The value of each bit of the bits for indicating the retransmission of unsuccessful transmitted TB or TBs can have different meanings, for example, the value 0 of each bit may indicate that the corresponding CBG is not transmitted in the corresponding PDSCH or the bit is padded with 0, and the value 1 of each bit may indicate that the corresponding CBG is transmitted in the corresponding PDSCH, and vice versa.

In this embodiment, for the third portion of the CBGTI field, it begins at the (N*L+1) -th bit and each bit of it is padded with a padding value, for example, 0.

If H<N·L, L is the number of PDSCHs for CBG-based transmission scheduled by the DCI. The bits of CBGTI field are divided into L groups, and the number of bits for group with index 0 to group with index mod (H, L) -1 is ceil (H/L) , the number of bits for group with index mod (H, L) to group with index L-1 is floor (H/L) . Each group of information bits Q is corresponding to a PDSCH, e.g., group index 0 is corresponding to the first scheduled PDSCH, and group index L-1 is corresponding to the last scheduled PDSCH. Each bit of a group in the CBGTI field corresponds to a CBG bundle of the TB in the corresponding PDSCH, and the number of CBGs for CBG bundle with index 0 to group index mod (N, Q) -1 is ceil (N/Q) , the number of CBGs P for CBG bundle with index mod (N, Q) to group index Q-1 is floor (N/Q) .

In an example, the CBGTI field bits are divided into L groups and mapped such that the first set or group of K bits starting from the MSB corresponds to the first TB, while the m-th set or group of K bits corresponds to a m-th TB, wherein

Each set of K bits in the CBGTI field have an in-order one-to-one mapping with K bundles of CBGs of one TB, with the MSB mapped to CBG bundle #0. Each CBG bundle includes

CBGs. For a retransmission of a TB as indicated by the 'New Data Indicator' field of the scheduling DCI, the UE may assume that a bit value of '0' in the CBGTI field indicates that the corresponding CBG bundle is not transmitted and '1' indicates that the corresponding CBG bundle is transmitted. For an initial transmission of a TB as indicated by the 'New Data Indicator' field of the scheduling DCI, the UE may assume that a bit value of '1' in the CBGTI field indicates that the all CBG bundles of the TB are transmitted. In this condition, the channel quality may be good and the bit width of CBGTI can be configured to a small value, for example H<N·L, and the CBGs can be transmitted in CBG bundles, so as to reduce the bit width of CBGTI.

In this way, in accordance with determining that H≤N*L, where L is the number of PDSCHs for CBG-based transmission actually scheduled by the DCI, the bits of CBGTI field is divided into L groups, and the number of information bits of each group is determined based on H and L; each bit of the CBGTI field of a group corresponds to a CBG bundle of the TB in the corresponding PDSCH, and the number of CBGs for each CBG bundle is determined based on the number information bits of each group and N.

The following table 1 shows several examples for the bit information of CBGTI. The bit width of CBGTI is 8 configured by RRC singling, and the maximum number of CBG per TB is 4, and the value of the maximum number of schedulable PDSCH among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH is 4. The actual number of PDSCH scheduled by DCI can be 1, 2 and 4 as shown in table 1, and the corresponding indication of CBGTI bits for different scheduling cases should be different.

Table 1

As shown in FIG. 4A, in the initial transmission, four TBs are transmitted in four scheduled PDSCH (i.e. PDSCH #0, PDSCH #1, PDSCH #2, PDSCH #3) in multi-slots on cell CC#1, and the maximum number of CBGs per TB is configured to be 4, and the bits of CBGTI in DCI format 1_1 is of length 8 bits configured by RRC signalling of DCI format1_1. As shown in FIG. 4A, the UE generates a HARQ-ACK codebook comprising CBG related results/ACK&NACK feedback for the initial transmission for the corresponding TB, and transmits the HARQ-ACK codebook via a PUCCH #0 to the gNB.

As shown in FIG. 4B, CBG with index #2 and #3 transmitted in PDSCH #2 and CBG with index #0 and #1 transmitted in PDSCH #3 are not successfully initially transmitted, and the gNB then schedules two PDSCHs, i.e. PDSCH #4 and PDSCH #5 by a DCI to perform retransmission. In the retransmission, as shown in FIG. 4B, two PDSCHs are scheduled for retransmission, and the CBGTI has 8 bits, and thus this situation corresponds to the second situation as shown in table 1, wherein the 1 ^st 4-bits have an in-order one-to-one mapping with the 4 CBGs of the 1 ^st TB, and the 4 LSB bits have an in-order one-to-one mapping with the 4 CBGs of the 2 ^nd TB. The two values 0 in 1 ^st 4 bits of the CBGTI of FIG. 4B indicate the corresponding CBGs with index #0 and #1 are not retransmitted, and the two values 1 in 1 ^st 4 bits of the CBGTI of FIG. 4B indicates that the corresponding CBGs with index #2 and #3 are retransmitted, respectively. The two values 1 in 2 ^nd 4 bits of the CBGTI of FIG. 4B indicates that the corresponding CBGs with index #0 and #1 are retransmitted, respectively, and the two values 0 in 2 ^nd 4 bits of the CBGTI of FIG. 4B indicate the corresponding CBGs with index #2 and #3 are not retransmitted.

In the retransmission and new initial transmission, as shown in FIG. 4C, four PDSCHs are scheduled, and two of them are scheduled to retransmit, and two of them are scheduled to perform a new initial transmission, and the CBGTI has 8 bits, and thus this situation corresponds to the third situation as shown in table 1, wherein the 1 ^st 2-bits of the CBGTI have an in-order one-to-one mapping with the 2 CBG bundles of the TB, each bundle includes 2 CBGs, and the m-th 2-bits of the CBGTI have an in-order one-to-one mapping with the 2 CBG bundles of the m-th TB, each bundle includes 2 CBGs.

The first value 0 of the CBGTI of FIG. 4C indicates that the first CBG bundle (including CBGs with index #0 and #1) of the first retransmitted TB is not retransmitted. The second value 1 of the CBGTI of FIG. 4C indicates that second CBG bundle (including CBGs with index #2 and #3) of the first retransmitted TB is retransmitted. The third value 1 of the CBGTI of FIG. 4C indicates that first CBG bundle (including CBGs with index #0 and #1) of the second retransmitted TB is retransmitted. The fourth value 0 of the CBGTI of FIG. 4C indicates that second CBG bundle (including CBGs with index #2 and #3) of the second retransmitted TB is not retransmitted. The fifth to eight value 1 of the CBGTI of FIG. 4C indicates that each of two CBG bundles of the first new TB is initially transmitted, and each of two CBG bundles of the second new TB is initially transmitted, respectively.

In this embodiment, the DCI overhead and the bit width of CBGTI can be controlled by network, which can achieve a trade-off between DCI overhead and spectrum efficiency. It is also helpful to align the HARQ-ACK overhead reduction (CBG bundling for HARQ-ACK report) .

EXAMPLE OF CBG-BASED TYPE-2 HARQ-ACK CODEBOOK DETERMINATION

A network device can assign a plurality of serving cells for serving a terminal device in a PUCCH cell group. Each of the plurality of serving cells corresponds to a different component carrier (CC) which in turns corresponds to a different PDSCH. Taking CC0 and CC1 as examples, CC0 is configured for CBG-based single PDSCH scheduling transmission and CBG-based multi-slot PDSCHs scheduling transmission. CC1 is configured for TB-based single PDSCH scheduling and TB-based multi-slot PDSCHs scheduling transmission.

When the downlink transmissions are received on a set of PDSCHs, the terminal device needs to feedback at least one HARQ-Acknowledgement/Negative-acknowledgement (ACK/NACK) in a PUCCH resource. To this end, the terminal device may generate the HARQ-ACK codebook comprising HARQ feedbacks of the downlink transmissions. However, the design of HARQ codebook in the current technology may not be adapted to reporting HARQ feedbacks when a single DCI is used for CBG-based multi-slot PDSCHs scheduling transmissions. Further, a reduced overhead of the HARQ-ACK feedback may be desirable, especially when the number of sub-codebooks contained in the HARQ-ACK codebook is getting larger.

FIG. 5 shows the HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure.

In some embodiments of the present disclosure provide solutions for solving the above and other potential issues. Generally, an enhanced HARQ-ACK codebook construction rule is provided to report HARQ feedbacks in a case where HARQ-ACK for CBG-based multi-slot PDSCHs transmission scheduling is multiplexed with HARQ-ACK for at least CBG-based single PDSCH transmission scheduling, TB-based single PDSCH transmission scheduling, and/or TB-based multi-slot PDSCHs transmission scheduling on a PUCCH resource configured by network device.

In one embodiment, when that HARQ-acknowledgement (HARQ-ACK) information for a plurality of CBG based PDSCHs scheduled by a first DCI and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs, the UE constructs HARQ-ACK codebook for HARQ-ACK information generated for CBG-based multi-slot PDSCHs and other PDSCHs scheduled by any one of the second DCI, the third DCI and the fourth DCI. In one embodiment, the UE determine the HARQ-ACK codebook based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold T indicated or preconfigured by the network device. The corresponding DCI can be any one of a DCI for scheduling CBG-based single PDSCH, a DCT for scheduling TB-based single PDSCH, a DCI for scheduling TB-based multi-slot PDSCHs and a DCI for scheduling CBG-based multi-slot PDSCHs.

The gNB configures a first threshold T for determining that HARQ-ACK information bit (s) associated with a DCI (i.e., associated with a K1 value on a cell) belongs to which sub-codebook.

The number of generated HARQ-ACK information bits for TB-based single scheduled PDSCH scheduled by the second DCI is 1 bit; the number of generated HARQ-ACK information bits for CBG-based single PDSCH scheduled by scheduled by the third DCI is based on the maximum number of CBGs per TB configured by RRC; the number of generated HARQ-ACK information bits for TB-based multi-slot PDSCHs scheduled by the fourth DCI is based on the maximum number of scheduled PDSCHs configured by RRC; and the number of generated HARQ-ACK information bits for CBG-based multi-slot PDSCHs scheduled by the first DCI is based on a product of the maximum number of CBGs per TB configured by RRC and the maximum number of scheduled PDSCHs of a DCI configured by RRC.

In one embodiment, as shown in FIG. 5, the HARQ-ACK codebook comprises two sub-codebooks, in response to that the number of generated HARQ-ACK information bits for PDSCH (s) scheduled by a DCI is equal to or less than the first threshold T, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the first sub-codebook; in response to that the number of generated HARQ-ACK information bits for PDSCH (s) scheduled by a DCI is larger than the first threshold T, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the second sub-codebook. In the first sub-codebook, the number of generated HARQ-ACK positions for a corresponding scheduling DCI is equal to T; and in the second sub-codebook, the number of generated HARQ-ACK positions for a corresponding scheduling DCI is equal to the product of the maximum number of CBGs of a TB configured by the network device and the maximum number of scheduled PDSCH by a DCI configured by network device. The first sub-codebook is placed before the second sub-codebook constructed as a codebook.

In this way, when the No. of generated HARQ-ACK information bits for PDSCH (s) associated with a DCI M ≤ M _{_threshold}, UE determines that HARQ-ACK information bits for PDSCH (s) associated with the DCI belongs to the first sub-codebook, M _{_threshold} HARQ-ACK positions are generated for the corresponding DCI, i.e., a DAI value (i.e. the number of HARQ-ACK positions generated when the C-DAI in the DCI is increased by 1) in the DCI corresponds to M _{_threshold} HARQ-ACK positions, if M< M _{_threshold}, 0 value will be padded for the last M _{_threshold} -M HARQ-ACK positions.

In this way, when the No. of generated HARQ-ACK information bits for PDSCH (s) associated with a DCI M > M _{_threshold}, UE determines that HARQ-ACK information bits for PDSCH (s) associated with the DCI belongs to the second sub-codebook, M _{_Max} HARQ-ACK positions are generated for the corresponding DCI, where M _{_Max} is determined based on the maximum No. of CBGs per TB and maximum No. of PDSCHs scheduled by single DCI or a value configured by RRC, i.e., a DAI value (i.e. the number of HARQ-ACK positions generated when the C-DAI in the DCI is increased by 1) in the DCI is corresponding to M _{_Max} HARQ-ACK positions, if M< M _{_Max}, 0 value will be padded for the last M _{_Max} -M HARQ-ACK positions.

In an example, the threshold is configured to be 1 by RRC signaling, the maximum number of CBGs per TB configured by RRC is 2, and maximum No. of PDSCHs scheduled by single DCI configured by RRC is also 2. For TB-based single scheduled PDSCH, the number “1” of generated HARQ-ACK information bits for TB-based single scheduled PDSCH is equal to the threshold 1, M _{_threshold} (i.e. 1) HARQ-ACK position is generated for this DCI for scheduling TB-based single PDSCH and belongs to the first sub-codebook. For CBG-based single scheduled PDSCH, the number “2” of generated HARQ-ACK information bits for CBG-based single scheduled PDSCH is larger than the threshold 1, and for this DCI for scheduling CBG-based single PDSCH, M _{_Max} HARQ-ACK positions (i.e. 4) are generated for this DCI and belongs to the second sub-codebook, where M _{_Max} is determined based on the product of the maximum No. of CBGs per TB and maximum No. of PDSCHs scheduled by single DCI or a value configured by RRC. UE reports 1-bit TB-level HARQ-ACK value for the single scheduling PDSCH in the first sub-codebook and UE reports 2-bits CBG-level HARQ-ACK values for two CBGs of the PDSCH in the first two HARQ-ACK positions in the second sub-codebook respectively, UE reports NACK value in the last two HARQ-ACK positions in the second sub-codebook .

In an example, the threshold is configured to be 4 by RRC signaling, the maximum number of CBGs per TB configured by RRC is 4, and maximum No. of PDSCHs scheduled by single DCI configured by RRC is also 4. For TB-based single scheduled PDSCH, the number “1” of generated HARQ-ACK information bits for TB-based single scheduled PDSCH is less than the threshold 4, 4 (i.e. the threshold) HARQ-ACK positions are generated for PDSCH scheduled by this DCI for scheduling TB-based single PDSCH and belongs to the first sub-codebook, wherein the first positon of 4 HARQ-ACK positions is the HARQ-ACK information (ACK/NACK) for this TB-based single PDSCH transmission scheduling, and the remaining three positons of 4 HARQ-ACK positions are padded with NACK or value 0. For CBG-based single scheduled PDSCH, the number “4” of generated HARQ-ACK information bits for CBG-based single scheduled PDSCH is equal than the threshold 4, and for this DCI for scheduling CBG-based single PDSCH, M _{_threshold} HARQ-ACK positions (i.e. 4) are generated for the PDSCH scheduled by this DCI and belongs to the first sub-codebook. For CBG-based multi-slot PDSCHs, the number “16” of generated HARQ-ACK information for CBG-based multi-slot scheduled PDSCH is larger than the threshold 4, and for this DCI for scheduling CBG-based multi-slot PDSCHs, M _{_Max} HARQ-ACK positions (i.e. 16) are generated for this DCI and belongs to the second sub-codebook, where M _{_Max} is determined based on the product of the maximum No. of CBGs per TB and maximum No. of PDSCHs scheduled by single DCI or a value configured by RRC.

The following table 2 shows two HARQ-ACK codebooks construction for CBG based multi-slot PDSCH scheduling, which are constructed for two different threshold values configured by network device, respectively, and each of which comprises two sub code-books.

Table 2

As shown in FIG. 5, the cell CC#1 is configured with CBG-based PDSCH transmission, and the cell CC#0 is configured with TB-based PDSCH transmission. The number of generated HARQ-ACK information bit for CBG-based single PDSCH #0 scheduled by DCI with C-DAI=1 (with dark color) is 4, which is equal to the maximum number of CBGs per TB configured by the network device or the RRC (as shown in FIG. 5, Maximum No. of CBGs=4) , and thus this number is equal to the threshold 4, and the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the first sub-codebook.

According to the same approach, as shown in FIG. 5, it can be determine that: (1) the generated HARQ-ACK information bit for TB-based multi-slot PDSCHs #1, #2, #3 and #4 scheduled by DCI with C-DAI=2 (with dark color) is determined to belong to the first sub-codebook; (2) the generated HARQ-ACK information bit for TB-based single PDSCH #9 scheduled by DCI with C-DAI=3 (with dark color) is determined to belong to the first sub-codebook; (3) the generated HARQ-ACK information bit for CBG-based multi-slot PDSCHs #5, #6, #7 and #8 scheduled by DCI with C-DAI=1 (with gray color) is determined to belong to the second sub-codebook.

As shown in FIG. 5, the HARQ-ACK positions generated for each DCI in the first sub-codebook is determined by the threshold, that is 4, and the HARQ-ACK positions generated for each DCI in the second sub-codebook is determined by the product of the maximum number of CBGs of a TB configured by RRC and the maximum number of scheduled PDSCHs of single DCI configured by RRC, and that is 16 (4*4) in the embodiment as shown in FIG. 5.

The C-DAI value of each DCI is accumulatively counted for the first or sub-codebook. Therefore, in the embodiment as shown in FIG. 5, in the first sub-codebook, there are HARQ-ACK positions generated for three DCIs, and in the second sub-codebook, there is only one DCI. As shown in FIG. 5, the HARQ-ACK positions generated for each of the three DCIs is 4. Since the number of generated HARQ-ACK information bit for TB-based single PDSCH #9 is 1 bit, there are three bits in the HARQ-ACK positions padded with N.

In the embodiment as shown in FIG. 5, the solution is flexible and has less HARQ-ACK redundancy; in addition, two sub-codebooks construction is aligned with legacy type-2 HARQ-ACK codebook construction rule.

FIG. 6 illustrates the HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure. As shown in FIG. 6, the first threshold is 1, the second threshold is 4, and the maximum number of CBGs per TB configured by RRC is 4, and maximum No. of PDSCHs scheduled by single DCI configured by RRC is also 4.

In one embodiment of the present disclosure, as shown in FIG. 6, the HARQ-ACK codebook comprises three sub-codebooks, and a first threshold value T1 and a second threshold value T2 are indicated by the network device. In response to that the number of generated HARQ-ACK information bits associated with a corresponding DCI is equal to or less than the first threshold value T1, the generated respective HARQ-ACK information is determined to belong to the first sub-codebook; in response to that the number of generated HARQ-ACK information bits associated with a corresponding DCI is larger than the first threshold value T1 and equal to or less than the second threshold value T2, the generated respective HARQ-ACK positions is determined to belong to the second sub-codebook; and in response to that the number of generated HARQ-ACK information bits is larger than the second threshold value T2, the generated respective HARQ-ACK positions is determined to belong to the third sub-codebook. In this embodiment, in the first sub-codebook, the number of generated HARQ-ACK positions for PDSCH (s) scheduled by the corresponding scheduling DCI is equal to T1; and in the second sub-codebook the number of generated HARQ-ACK positions for PDSCH (s) scheduled by the corresponding scheduling DCI is equal to T2, and in the third sub-codebook the number of generated HARQ-ACK positions is equal to the product of the maximum number of CBGs of a TB and the maximum number of scheduled PDSCHs by a DCI configured by network.

In an example, the first threshold is configured to be 1 by RRC signaling, and the second threshold is configured to be 4 by RRC signaling, and the maximum number of CBGs per TB configured by RRC is 4, and maximum No. of PDSCHs scheduled by single DCI configured by RRC is also 4. For TB-based single scheduled PDSCH, the number “1” of generated HARQ-ACK information for TB-based single scheduled PDSCH is equal to the first threshold 1, M _{_threshold} (i.e. 1) HARQ-ACK position is generated for this DCI for scheduling TB-based single PDSCH and belongs to the first sub-codebook. For CBG-based single scheduled PDSCH, the number “4” of generated HARQ-ACK information bits for CBG-based single scheduled PDSCH is larger than the first threshold 1 and equal to the second threshold 4, M _{_threshold} (i.e. 4) HARQ-ACK position is generated for this DCI for scheduling CBG-based single PDSCH and belongs to the second sub-codebook. For CBG-based multi-slot PDSCHs, the number “16” of generated HARQ-ACK information bits for TB-based single scheduled PDSCH is larger than the second threshold 4, and for this DCI for scheduling CBG-based multi-slot PDSCHs, M _{_Max} HARQ-ACK positions (i.e. 16) are generated for this DCI and belongs to the second sub-codebook, where M _{_Max} is determined based on the product of the maximum No. of CBGs per TB and maximum No. of PDSCHs scheduled by single DCI or a value configured by RRC.

The following table 3 shows one HARQ-ACK codebook, which is constructed for two thresholds and comprises three sub code-books.

Table 3

As shown in FIG. 6, the cell CC#1 is configured with CBG-based PDSCH transmission, and the cell CC#0 is configured with TB-based PDSCH transmission.

As shown in FIG. 6, the number of generated HARQ-ACK information bits for TB-based single PDSCH #9 scheduled by DCI with C-DAI=1 is 1, and thus this number is equal to the first threshold 1, and the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the first sub-codebook.

As shown in FIG. 6, the number of generated HARQ-ACK information bit for CBG-based single PDSCH #0 scheduled by DCI with C-DAI=1 is 4, which is equal to the maximum number of CBGs per TB configured by the network device or the RRC (as shown in FIG. 5, Maximum No. of CBGs=4) , and thus this number is larger than the first threshold 1 and equal to the second threshold 4, and the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the second sub-codebook.

According to the same approach, as shown in FIG. 6, it can be determine that: (1) the generated HARQ-ACK information bit for TB-based multi-slot PDSCHs #1, #2, #3 and #4 scheduled by DCI with C-DAI=2 (with dark color) is determined to belong to the second sub-codebook; and (2) the generated HARQ-ACK information bit for CBG-based multi-slot PDSCHs #5, #6, #7 and #8 scheduled by DCI with C-DAI=1is determined to belong to the third sub-codebook.

As shown in FIG. 6, the number of HARQ-ACK positions generated for each DCI in the first sub-codebook is determined by the first threshold, that is 1, and the number of HARQ-ACK positions generated for each DCI in the second sub-codebook is determined by the second threshold, that is 4, and the number of HARQ-ACK positions generated for each DCI in the third sub-codebook is determined by the product of the maximum number of CBGs of a TB configured by RRC and the maximum number of scheduled PDSCHs of a DCI configured by RRC, and that is 16 (4*4) in the embodiment as shown in FIG. 6.

The C-DAI value of each DCI is accumulatively counted for the first to third sub-codebook. Therefore, in the embodiment as shown in FIG. 6, in the first sub-codebook, there is one HARQ-ACK position generated for only one DCI for scheduling TB-based PDSCH #9. In the second sub-codebook, there are HARQ-ACK positions generated for the DCI for scheduling TB-based multi-slot PDSCHs #1, #2, #3 and #4 and the DCI for scheduling CBG-based single PDSCH #0, respectively. In the third sub-codebook, there are HARQ-ACK positions generated for one DCI for scheduling CBG-based multi-slot PDSCHs #5, #6, #7 and #8.

As shown in FIG. 6, the HARQ-ACK positions generated for the DCI in the first sub-codebook is 1. Since the number of generated HARQ-ACK information bit for TB-based single PDSCH #9 is 1 bit, there is no redundancy.

As compared with the embodiment as shown in FIG. 5, the HAR-ACK redundancy is further reduced by deleting the padding value in the HARQ-ACK position generated for a TB-based single PDSCH scheduling.

EXAMPLE OF HARQ-ACK REDUNDANCY REDUCTION

In case CBG-based HARQ-ACK feedback report for multi-slot PDSCH scheduling is configured, larger HARQ-ACK overhead will be generated, e.g., when Max No.of CBGs per TB is 4 and Max No. of scheduled PDSCH by a DCI is 8, then 32 bits HARQ-ACK position is needed for a DCI scheduling multi-PDSCH with CBGs, following methods can be considered to reduce HARQ-ACK redundancy.

In one embodiment, as shown in FIG. 7A, UE operates CBG-based HARQ-ACK bundling based on the No. of scheduled PDSCHs M by the DCI and a RRC configured value Q. That is to say, the number of HARQ-ACK positions for a plurality of CBG-based physical downlink shared channels (PDSCHs) transmission in multiple slots scheduled by each DCI is a constant Q. The number of the plurality of CBG-based PDSCHs actually scheduled by a DCI is M, and the value of M varies from one DCI to another DCI; and for each PDSCH of CBG-based multi-PDSCHs, the number of generated HARQ-ACK positions is determined based on Q and M.

Specifically, UE always generates Q HARQ-ACK positions for the CBG-based multi-PDSCHs scheduled by a DCI. Each HARQ-ACK position is corresponding to a CBG bundle of a scheduled PDSCH. For PDSCH i (i=0, …M-1) , UE generates corresponding H _i HARQ-ACK positions for H _i CBG bundles of the PDSCH i, H _i is obtained by dividing Q into M groups. In one embodiment, the number of bits for group with index 0 to group with index mod (Q, M) -1 is ceil (Q/M) , the number of bits for group with index mod (Q, M) to group with index M-1 is floor (Q/M) . Each group of information bits is corresponding to a PDSCH, e.g., group index 0 is corresponding to the first scheduled PDSCH, and group index M-1 is corresponding to the last scheduled PDSCH.

In one embodiment, as shown in FIG. 7A, the 1 ^st group corresponding to the CBG-based PDSCH #2 has

That is to say, for each PDSCH of CBG-based multi-PDSCHs, the number of generated HARQ-ACK positions is determined based on Q and M.

H _i CBG bundles of PDSCH i are obtained by dividing N CBGs of PDSCH i into H _i bundles. Each bit of a group of the HARQ-ACK positions corresponds to a CBG bundle in the corresponding PDSCH, and the number of CBGs for CBG bundle with index 0 to group index mod (Hi, N) -1 is ceil (N/Hi/) , the number of CBGs P for CBG bundle with index mod (Hi, N) to group index Hi-1 is floor (N/Hi) .

UE reports one A/N value in the corresponding HARQ-ACK position for one CBG bundle by do AND operation for CBG-based A/N value of the CBGs within the bundle. That is to say, the number of CBGs in each CBG bundle is determined based on N, Q and M, where N is the maximum number of CBGs per TB, for example, the number of CBGs in each CBG bundle is equal to N/H ₁.

In this embodiment, the solution provides flexibility for gNB to control the HARQ-ACK payload based on scheduling situation and can reduce the HARQ-ACK redundancy.

As shown in FIG. 7A, the DCI with C-DAI=1 is used for scheduling CBG-based two PDSCHs, and the DCI with C-DAI=2 is used for scheduling CBG-based four PDSCHs, and the DCI with C-DAI=3 is used for scheduling CBG-based eight PDSCHs. When HARQ-ACK information of these PDSCHs are indicated to be multiplexed in a PUCCH resource, 8 HARQ-ACK positions are generated for each of the DCI with C-DAI=1, the DCI with C-DAI=2 and the DCI with C-DAI=3, the total HARQ-ACK payload of the PUCCH is 24-bits. In the 8 HARQ-ACK positions generated for the DCI with C-DAI=1, UE generates corresponding

HARQ-ACK positions for

CBG bundles of the corresponding PDSCH, 4 is obtained by dividing Q (i.e. 8) into M (i.e. 2) groups, e.g., 1 ^st group has 4 HARQ-ACK positions, and the number of CBGs in each CBG bundle is equal to 1, i.e. N/H ₁=4/4. That is, each A/N value in the 8 HARQ-ACK positions is for corresponding to each CBG of two TBs in the two PDSCHs.

In the 8 HARQ-ACK positions generated for the DCI with C-DAI=2, UE generates corresponding

HARQ-ACK positions for

CBG bundles of the corresponding PDSCH, 2 is obtained by dividing Q (i.e. 8) into M (i.e. 4) groups, e.g., 1 ^st group has 2 HARQ-ACK positions, and the number of CBGs in each CBG bundle is equal to 2, i.e. N/H ₁=4/2=2. In the 8 HARQ-ACK positions generated for the DCI with C-DAI=2 , UE generates corresponding

HARQ-ACK position for

CBG bundle of the corresponding PDSCH, 1 is obtained by dividing Q (i.e. 8) into M (i.e. 8) groups, e.g., 1 ^st group has 1 HARQ-ACK positions, and the number of CBGs in each CBG bundle is equal to 2, i.e. N/H ₁=2/1=2. That is, each A/N value in the 8 HARQ-ACK positions is for corresponding to each CBG bundle (two CBGs) of fours TBs in the four PDSCHs.

The following table 4 illustrates table 3 the above comparison.

Table 4

Therefore, as can be seen from the table 5, the total generated HARQ-ACK positions for three DCI is 3*8=24 bits. Compared with the HARQ-ACK positions with 8*4*3=96 bits, wherein 4 is max No. of CBGs per TB, and 8 is Max No. of scheduled PDSCH by a DCI, and 3 is the number of DCIs, the HARQ-ACK overhead is reduced by 75%.

FIG. 7B illustrates a HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure, in which the first portion and the second portion are multiplexed on a HARQ-ACK codebook and transmitted to the network device via a same PUCCH. FIG. 7C illustrates a HARQ-ACK codebook construction in accordance with some embodiments of the present disclosure, in which first portion and the second portion are separately transmitted in two HARQ-ACK codebooks to the network device via two PUCCHs, wherein the first portion of TB-based HARQ-ACK information is transmitted via a first PUCCH of the two PUCCHs, and the second portion of CBG-based HARQ-ACK information is transmitted via a second PUCCH of the two PUCCHs.

In one embodiment, as shown in FIG. 7B and FIG. 7C, the HARQ-ACK information for the plurality of CBG-based PDSCHs transmission in multiple slots scheduled by a DCI comprises a first portion and a second portion, and the number of HARQ-ACK information of the second portion is determined based on the HARQ-ACK information in the first portion. The first portion comprises TB-based HARQ-ACK information for each PDSCH of the plurality of CBG-based PDSCHs, and the second portion comprises CBG-based HARQ-ACK information for a set of incorrectly decoded PDSCHs of the plurality of CBG-based PDSCHs. M HARQ-ACK positions is generated in the first portion for the plurality of CBG-based PDSCHs, where M is the value of the maximum number of schedulable PDSCH scheduled by a DCI configured by network. In response to that a PDSCH for a TB including CBGs is successfully decoded, 1 bit of TB ACK is generated in the first portion; and in response to that a PDSCH for a TB including CBGs is unsuccessfully decoded, 1 bit of TB NACK is generated in the first portion, and N bits of CBG-based ACK/NACK for each unsuccessfully decoded TB is generated in the second portion, where N is the maximum number of CBGs per TB, and N*P HARQ-ACK positions is generated for the second portion, where P is the total number of unsuccessfully decoded TBs of the plurality of CBG-based PDSCHs.

In this way, the first portion of HARQ-ACK information is TB-based HARQ-ACK information for all PDSCHs (regardless of TB-based or CBG-based for this PDSCHs, regardless of whether TB is correctly decoded or not) , the No. of HARQ-ACK information bits of the first portion HARQ-ACK information is determined based on the c-DAI/t-DAI value in scheduling DCI, while the second portion of HARQ-ACK information only includes CBG-based A/N bits of TB which is failed to be decoded.

That is, when a PDSCH for a TB including CBGs is successfully decoded by UE, UE will only generate 1-TB ACK bit in the first portion HARQ-ACK information and doesn’ t report CBG A/N bits for the TB. While when a PDSCH for a TB including CBGs is unsuccessfully decoded by UE, UE will generate 1-TB NACK bit in the first portion HARQ-ACK information and generates N CBG A/N bits for the TB in the second portion HARQ-ACK information, where N is the maximum CBGs of a TB.

The first portion and the second portion are multiplexed on a HARQ-ACK codebook and transmitted to the network device via a same PUCCH, and the network device is configured to decode the second portion of the HARQ-ACK codebook after successfully decoding the first portion of the HARQ-ACK codebook. When gNB receives a PUCCH for HARQ-ACK information report including multi-PDSCH scheduling with CBGs, gNB can only decode the second portion HARQ-ACK information after successfully decoding the first portion HARQ-ACK information and determine the size of the second portion HARQ-ACK information. The coding of the first portion of HARQ-ACK information and the second portion of HARQ-ACK information on a PUCCH can follow similar rule of CSI part 1 and CSI part 2. It should be understood by the skilled in the art that other methods for dividing the first portion and second portion information are not excluded, e.g., TB bundling A/N for the first portion of HARQ-ACK information.

In this embodiment, the solution can reduce the HARQ-ACK redundancy in most cases especially when configured maximum CBGs of a TB is large and channel condition is good, so it provides high efficient HARQ-ACK information report.

As shown in FIG. 7B, the DCI with C-DAI=1 is used for scheduling CBG-based two PDSCHs, and the DCI with C-DAI=2 is used for scheduling CBG-based four PDSCHs, and the DCI with C-DAI=3 is used for scheduling CBG-based eight PDSCHs. In the HARQ-ACK positons generated for the DCI with C-DAI=1, since two PDSCHs are both correctly decoded, there is no second portion of HARQ-ACK positons generated for it, and only the first portion of HARQ-ACK positons is generated, and in the first portion, 8 HARQ-ACK positons is generated, in which the bit information A means that the corresponding TB is correctly decoded, and the bit information N with gray color means that this bit is padded.

As shown in FIG. 7B, in the HARQ-ACK positons generated for the DCI with C-DAI=2, since PDSCH#3 is not correctly decoded, there is first portion of HARQ-ACK positons and second portion of HARQ-ACK positons generated for it, and in the first portion, 8 HARQ-ACK positons is generated, in which the bit information A means that the corresponding TB is correctly decoded, and the bit information N with diagonal lines means that the corresponding TB is not correctly decoded, and the bit information N with gray color means that this bit is padded, and in the second portion, 4 HARQ-ACK positons is generated for this unsuccessfully decoded TB on PDSCH #3. In the HARQ-ACK positons generated for the DCI with C-DAI=3, since

PDSCHs #

10, 11 and 13 are not correctly decoded, there is first portion of HARQ-ACK positons and second portion of HARQ-ACK positons generated for each of them, and in the first portion, 8 HARQ-ACK positons is generated, in which the bit information A means that the corresponding TB is correctly decoded, and the bit information N with diagonal lines means that the corresponding TB is not correctly decoded, and in the second portion, 4 HARQ-ACK positons is generated for this unsuccessfully decoded TB on each of

PDSCHs #

10, 11 and 13.

The following table 5 illustrates the above comparison.

Table 5

As can be seen from the table 5, the generated HARQ-ACK positions for first portion is 3*8=24 bits, and the generated HARQ-ACK positions for second portion is 4*4=16, and the total HARQ-ACK positions is 40 bits. Compared with the HARQ-ACK positions with 8*4*3=96 bits, wherein 4 is max No. of CBGs per TB, and 8 is Max No. of scheduled PDSCH by a DCI, and 3 is the number of DCIs, the HARQ-ACK overhead is reduced by 58.3%.

In one embodiment, as shown in FIG. 7C, the first portion and the second portion are separately transmitted in two HARQ-ACK codebooks to the network device via two PUCCHs, the first portion of TB-based HARQ-ACK information is transmitted via a first PUCCH of the two PUCCHs, and the second portion of CBG-based HARQ-ACK information is transmitted via a second PUCCH of the two PUCCHs. In response to that a PDSCH for a TB including CBGs is unsuccessfully decoded; the second portion of CBG-based HARQ-ACK information transmitted via the second PUCCH is triggered by the terminal device.

In this way, UE may report HARQ-ACK information bits for CBG-based multi-slot PDSCHs scheduled by a DCI on two PUCCHs. The first PUCCH is determined based on the scheduling DCI, the 1 ^st HARQ-ACK codebook on the 1 ^st PUCCH is for TB-based A/N bit for PDSCHs (regardless of PDSCH transmission is TB-based or CBG-based, regardless of whether TB is correctly decoded or not) , the CBS of codebook on 1 ^st PUCCH is determined based on the c-DAI/t-DAI value in scheduling DCI. In case a small part CBGs of some TBs are unsuccessfully decoded by UE, UE may trigger a second PUCCH transmission for a 2 ^nd HARQ-ACK codebook, which only includes CBG-based A/N bits for TBs which are failed to be decoded. UE determines the slots for 2 ^nd PUCCH transmission based on k1’ or K1+Δ, K1 is the time offset between the last PDSCH and the first PUCCH indicated by network, k1’ or Δ is indicated or configured by network, and UE determines the slots for 2 ^nd PUCCH resource based on same PRI on the DCI and HARQ-ACK payload of 2 ^nd HARQ-ACK CB. The gNB can only decode the 2 ^nd PUCCH after successfully decoding the 1 ^st PUCCH.

In this embodiment, the solution can reduce the HARQ-ACK redundancy in most cases especially when configured maximum CBGs of a TB is large and the channel condition is good, it will not complex the UCI multiplexing and channel coding, which has less specification impact, but it may increase scheduling latency.

As shown in FIG. 7C, the DCI with C-DAI=1 is used for scheduling CBG-based two PDSCHs, and the DCI with C-DAI=2 is used for scheduling CBG-based four PDSCHs, and the DCI with C-DAI=3 is used for scheduling CBG-based eight PDSCHs. In the HARQ-ACK positons generated for the DCI with C-DAI=1, since two PDSCHs are both correctly decoded, there is no second portion of HARQ-ACK positons generated for it, and only the first portion of HARQ-ACK positons is generated, and in the first portion, 8 HARQ-ACK positons is generated, in which the bit information A means that the corresponding TB is correctly decoded, and the bit information N with gray color means that this bit is padded.

As shown in FIG. 7C, in the HARQ-ACK positons generated for the DCI with C-DAI=2, since PDSCH#3 is not correctly decoded, there is first portion of HARQ-ACK positons and second portion of HARQ-ACK positons generated for it, and in the first portion, 8 HARQ-ACK positons is generated, in which the bit information A means that the corresponding TB is correctly decoded, and the bit information N with diagonal lines means that the corresponding TB is not correctly decoded, and the bit information N with gray color means that this bit is padded, and in the second portion, 4 HARQ-ACK positons is generated for this unsuccessfully decoded TB on PDSCH #3.

As shown in FIG. 7C, in the HARQ-ACK positons generated for the DCI with C-DAI=3, since

PDSCHs #

10, 11 and 13.

The following table 6 illustrates the above comparison.

Table 6

As can be seen from the table 6, the generated HARQ-ACK positions for first portion is 3*8=24 bits, and the generated HARQ-ACK positions for second portion is 4*4=16, and the total HARQ-ACK positions is 40 bits. Compared with the HARQ-ACK positions with 8*4*3=96 bits, wherein 4 is max No. of CBGs per TB, and 8 is Max No. of scheduled PDSCH by a DCI, and 3 is the number of DCIs, the HARQ-ACK overhead is reduced by 58.3%.

EXAMPLE OF CBG-BASED TRANSMISSION FOR SINGLE DCI SCHEDULING MULTI-CELL PDSCHS FOR XR TRAFFIC

In Rel-18 multi-carriers enhancements, single DCI scheduling multi-cell PDSCHs/PUSCHs by a new DCI format has been supported. However, there is no conclusion on whether and how to support CBG-based transmission for single DCI scheduling multi-cell PDSCHs.

In the following, referring to FIG. 8A to 9B, it will describe how to support CBG-based transmission for single DCI scheduling multi-cell PDSCHs and how to construct type 2 HARQ-ACK codebook for CBG-based transmission for single DCI scheduling multi-cell PDSCHs.

With reference to FIG. 8A, for a UE configured with a new DCI format for multi-cell scheduling, multiple PDSCHs on multiple cells (i.e., co-scheduled cells) are scheduled for UE by a DCI. As shown in FIG. 8A, a DCI format 1_X is used to schedule PDSCH #0 on CC #0, PDSCH #1 on CC #1 and PDSCH #2 on CC #2 for UE, and the HARQ-ACK feedback generated by UE are multiplexed on PUCCH #0 so as to be transmitted to network device, wherein CC #0 and CC #1 are configured with TB-based PDSCH transmission, and the CC #2 is configured with CBG-based PDSCH transmission.

In the following, it will describe how to support CBG-based multi-PDSCHs/PUSCHs transmission scheduled by multi-cell scheduling DCI.

For PDSCHs/PUSCHs on cells configured with CodeBlockGroupTransmission, which are scheduled by multi-cell scheduling DCI, whether or not the scheduled PDSCHs/PUSCHs support the CBG-based transmission depends on RRC configuration or DCI indication. The RRC configuration or DCI indication may comprise a new parameter codeBlockGroupTransmissionDCI 1-X/codeBlockGroupTransmissionDCI 0-X. If the parameter codeBlockGroupTransmissionDCI 1-X/codeBlockGroupTransmissionDCI 0-X is configured for UE by RRC configuration or DCI indication, the PDSCH/PUSCH on the cell configured with CBG transmission can be based on CBG-based transmission. That is to say, the parameter codeBlockGroupTransmissionDCI 1-X/codeBlockGroupTransmissionDCI 0-X configured by RRC signaling is functioned as a switch, and if this parameter is configured for UE by RRC signaling, the PDSCHs/PUSCHs (which are scheduled on cells configured with CodeBlockGroupTransmission) scheduled for this UE can support CBG-based transmission; otherwise, the PDSCHs/PUSCHs (which are scheduled on cells configured with CodeBlockGroupTransmission) scheduled for this UE cannot support CBG-based transmission, and the PDSCHs/PUSCHs (which are scheduled on cells configured with CodeBlockGroupTransmission) scheduled for UE is used for TB-based transmission, even the PDSCHs/PUSCHs are scheduled on cells configured with CodeBlockGroupTransmission.

In the following, it will describe how to design the CBGTI field of the new parameter codeBlockGroupTransmission DCI 1-X/DCI 0-X for scheduling multiple PDSCHs or PUSCHs on multiple cells each configured with CodeBlockGroupTransmission.

In one embodiment, for the CBGTI field of the new multi-cell scheduling DCI 1-X/DCI 0-X, it can be commonly configured for the co-scheduled cells configured with CBG transmission. In another embodiment, the CBGTI field of the multi-cell scheduling DCI 1_X/DCI 0_X can be separately configured for each of the co-scheduled cells configured with CBG transmission. Further, the bit width of the CBGTI field is determined based on the maximum No. of CBG-based cells in the co-scheduled cell lists and maximum No. of CBGs per TB.

Since whether or not the scheduled PDSCHs/PUSCHs support the CBG-based transmission depends on RRC configuration or DCI indication, and if the RRC configuration configures the new scheduling DCI 1-X/DCI 0-X for UE, the scheduled PDSCHs/PUSCHs for this UE support the CBG-based transmission; otherwise, the scheduled PDSCHs/PUSCHs for this UE cannot support the CBG-based transmission. It can provide scheduling flexibility for gNB and improve spectrum efficiency.

FIG. 8B illustrates a view of a scheduling transmission when codeBlockGroupTransmissionDCI-1-X is provided for UE in accordance with some embodiments of the present disclosure. FIG. 8C illustrates a view of a scheduling transmission when codeBlockGroupTransmissionDCI-1-X is not provided for UE in accordance with some embodiments of the present disclosure.

As shown in FIG. 8B and FIG. 8C, the cell CC#0 is configured with TB transmission, and the cell CC#1 is configured with CBG transmission. In FIG. 8B, the codeBlockGroupTransmissionDCI-1-X is configured by RRC signaling for UE, the scheduled PDSCH #1 on CC#1 configured with CBG transmission can support CBG-based transmission. On the contrary, in FIG. 8C, the codeBlockGroupTransmissionDCI-1-X is not configured by RRC signaling for UE, and even the cell CC#1 is configured with CBG transmission, the scheduled PDSCH #1 on this cell cannot support CBG-based transmission and is used for TB-based transmission.

EXAMPLE OF TYPE-2 HARQ-ACK CODEBOOK CONSTRUCTION FOR CBG-BASED PDSCHS ON MULTI-CELLS SCHEDULED BY DCI

In the following, it will describe how to determine the HARQ-ACK codebook when the HARQ-ACK feedback or information for PDSCH (s) scheduled by multi-cell scheduling DCI 1_X are multiplexed on a PUCCH resource.

In one embodiment, the DCI is configured to schedule PDSCHs either on cells configured with TB transmission or on cells configured with CBG transmission. In response to that all PDSCHs on multiple cells are configured for CBG-based transmission, HARQ-ACK information for all PDSCHs scheduled by a DCI belongs to the CBG-based sub-codebook, and in response to that all PDSCHs on multiple cells are configured for TB-based transmission, HARQ-ACK information for all PDSCHs scheduled by a DCI belongs to the TB-based sub-codebook.

In this way, the multi-cell scheduling DCI only contains one DAI value (c-DAI) or one pair of DAI values (c-DAI and t-DAI) . Only one of TB-based transmission and CBG-based transmissions is configured for co-scheduled cells scheduled by a DCI, e.g., if all PDSCHs in multiple cells are configured for CBG-based transmission, HARQ-ACK information bits for all PDSCHs scheduled by this DCI belongs to CBG-based sub-codebook; and if all PDSCHs in multiple cells are configured for TB-based transmission, HARQ-ACK information bits for all PDSCHs scheduled by this DCI belongs to TB-based sub-codebook. That is to say, the co-scheduled cells expect to have same CBG configuration, e.g., all scheduled cells of DCI are configured with CBG based PDSCH transmission, or all scheduled cells of DCI are not configured with CBG based PDSCH transmission.

In this embodiment, the DCI is configured to schedule PDSCHs either on cells configured with TB transmission or on cells configured with CBG transmission, and the DCI cannot be used to schedule multiple PDSCHs, some of which are on cells configured with TB transmission and, the other of which are on cells configured with CBG transmission. It is simple for UE implementation, but may restrict gNB scheudling.

In the following, with reference to FIG. 9A and 9B, it will describe when one DCI is configured to schedule multiple PDSCHs, some of which are on cells configured with TB transmission and, the other of which are on cells configured with CBG transmission, how to determine the HARQ-ACK codebook.

The UE determines the order of HARQ-ACK information for the TB-based PDSCH (s) and CBG-based PDSCH (s) scheduled by multi-cell scheduling DCI and other PDSCHs are multiplexed in the HARQ-ACK codebook, based on the DAI value indication in the DCI similar as Rel-17. When there are two sub-codebooks, one is TB-based sub-codebook, another one is CBG based sub-codebook, TB based HARQ-ACK bits and CBG based HARQ-ACK bits for PDSCHs scheduled on cells configured with and without CBG-based transmission by DCI 1_X are placed in one of the sub-codebook, e.g., the CBG based sub-codebook, DAI value in the multi-cell scheduling DCI is only counted in the sub-codebook, HARQ-ACK bits order of PDSCHs scheduled by multi-cell scheduling DCI are determined based on corresponding DAI values.

In an embodiment, as shown in FIG. 9A, the multi-cell scheduling DCI comprises one C-DAI or a pair of C-DAI and T-DAI, in response to that multi-PDSCHs scheduled by the DCI multi-cell scheduling DCI are transmitted on cells configured with CBG-based transmission and on cells configured with TB-based transmission, the C-DAI of this DCI is counted as for CBG-based sub-codebook; and HARQ-ACK information for the multi-cell PDSCHs scheduled by this DCI is placed in the CBG-based sub-codebook.

In this way, the multi-cell scheduling DCI only contains one DAI value (c-DAI) or one pair of DAI values (c-DAI and t-DAI) . When PDSCHs scheduled by multi-cell scheduling DCI 1_X are transmitted on TB-based cells and CBG-based cells, the DAI value is counted as for CBG-based sub-codebook, i.e., HARQ-ACK information bits for all PDSCHs scheduled by this DCI belongs to CBG-based sub-codebook.

As shown in FIG. 9A, PDSCH #0 on cell CC#0 configured with TB transmission is scheduled by DCI#1 with C-DAI-1, and thus the HARQ-ACK position (s) generated for this PDSCH #0 belongs to TB-based sub-codebook in the HARQ-ACK codebook.

Further, as shown in FIG. 9A, PDSCH #1 on cell CC#1 configured with TB transmission and PDSCH #2 on cell CC#2 configured with CBG transmission are scheduled by the DCI#0 with C-DAI-1, and thus the DCI#0 is a multi-cell scheduling DCI, and the C-DA-1 is counted for CBG-based sub-codebook. That is to say, the HARQ-ACK information bits generated for PDSCH #1 on cell CC#1 and PDSCH #2 on cell CC#2 are placed in CBG-based sub-codebook in the HARQ-ACK codebook, and HARQ-ACK positions for each PDSCH is determined based on maximum No. of CBGs of a TB configured for CBG based cell. Since only 1 bit of A/N feedback is generated for TB transmission on PDSCH #1 on cell CC#1 and the HARQ-ACK positions generated in CBG-based sub-codebook contains two positions for each PDSCH, there is 1 bit padded with N in the positons generated for PDSCH #1 on cell CC#1, rendering redundancy.

Further, as shown in FIG. 9A, PDSCH #3 on cell CC#2 configured with CBG transmission and PDSCH #4 on cell CC#3 configured with CBG transmission are scheduled by the DCI#2 with C-DAI-2, and thus the HARQ-ACK positions generated for this PDSCH #3 and PDSCH #4 belong to CBG-based sub-codebook in the HARQ-ACK codebook. Thus, the C-DAI count value for this DCI#2 for scheduling PDSCH #3 and PDSCH #4 on cells CC#2 and CC#3 both configured with CBG transmission should be increased by 1 to be C-DAI-2 with respect to the C-DAI-1 of DCI#0.

In an embodiment, as shown in FIG. 9B, the multi-cell scheduling DCI comprises two C-DAIs or two pairs of C-DAI and T-DAI, in response to that multi-PDSCHs scheduled by each DCI are transmitted on cells configured with CBG-based transmission and on cells configured with TB-based transmission, the first C-DAI of this DCI is counted as for the CBG-based sub-codebook, and the second C-DAI of this DCI is counted as for the TB-based sub-codebook or the vise, and HARQ-ACK information or positions for the multi-PDSCHs scheduled by this DCI is separately placed in the CBG-based sub-codebook and the TB-based sub-codebook.

In this way, the multi-cell scheduling DCI contains two DAI values (C-DAI) or two pair of DAI values (C-DAI and T-DAI) . One C-DAI is for TB-based HARQ-ACK feedback, the other C-DAI is for CBG-based HARQ-ACK feedback.

As shown in FIG. 9B, PDSCH #0 on cell CC#0 configured with TB transmission is scheduled by DCI#1 with C-DAI-1, and thus the HARQ-ACK position (s) generated for this PDSCH #0 belongs to TB-based sub-codebook in the HARQ-ACK codebook. Further, as shown in FIG. 9B, PDSCH #1 on cell CC#1 configured with TB transmission and PDSCH #2 on cell CC#2 configured with CBG transmission are scheduled by the DCI#0 with C-DAI-1 and C-DAI-2, and thus the multi-cell scheduling DCI #0 comprises two C-DAIs, i.e. C-DAI-1 and C-DAI-2, the C-DAI-1 is counted for CBG-based HARQ-ACK feedback, and the C-DAI-2 is counted for TB-based HARQ-ACK feedback.

That is to say, the HARQ-ACK positions (or HARQ-ACK information bits) generated for PDSCH #1 on cell CC#1 belong to the TB-based sub-codebook in the HARQ-ACK codebook, and the HARQ-ACK positions (or HARQ-ACK information bits) generated for PDSCH #2 on cell CC#2 belong to the CBG-based sub-codebook in the HARQ-ACK codebook. Since only 1 bit of A/N feedback is generated for TB transmission on PDSCH #1 on cell CC#1 and the HARQ-ACK positions generated in TB-based sub-codebook contains only one position for each PDSCH, there is no bits padded with N in the positons generated for PDSCH #1 on cell CC#1, which does not rendering redundancy with respect to the embodiment as shown in FIG. 9A.

Further, as shown in FIG. 9B, PDSCH #3 on cell CC#2 configured with CBG transmission and PDSCH #4 on cell CC#3 configured with CBG transmission are scheduled by the DCI#2 with C-DAI-2, and thus the HARQ-ACK positions generated for this PDSCH #3 and PDSCH #4 belong to CBG-based sub-codebook in the HARQ-ACK codebook. Thus, the C-DAI count value for this DCI#2 for scheduling PDSCH #3 and PDSCH #4 on cells CC#2 and CC#3 both configured with CBG transmission should be increased by 1 to be C-DAI-2 with respect to the C-DAI-1 of DCI#0.

In the embodiments as shown in FIGs. 9A and 9B, HARQ-ACK bits or positions or information for PDSCHs scheduled on cells configured with and without CBG-based transmission by DCI 1_X are separately placed in CBG-based sub-codebook and TB-based sub-codebook, the order of HARQ-ACK bits are determined based on corresponding DAI values.

EXAMPLE OF COMMUNICATION METHOD

Corresponding to the above processes, embodiments of the present disclosure provide methods of communication implemented at a terminal device and a network device. These methods will be described below with reference to FIGs. 10-17.

FIG. 10 illustrates an example method 1000 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. For example, the method 1000 may be performed at the terminal device 110 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1000 will be described with reference to FIG. 1. It is to be understood that the method 1000 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

At block 1010, the terminal device 110 receives initial transmission of a first set of TBs each comprising one or more CBGs via a first number of PDSCHs. At block 1020, the terminal device 110 receives a DCI scheduling a second set of TBs comprising at least one retransmitted TB of the first set of TBs via a second number of PDSCHs on multiple slots. At block 1030, the terminal device 110 determines at least one CBG of the at least one retransmission of TB based on CBGTI field in the DCI. By the method of FIG. 10, the scheme of scheduling CBG-based multi-slot PDSCHs retransmission by a single may be support, and the CBGTI indication in the DCI can be designed to support the CBG-based multi-slot PDSCHs retransmission and also reduce the DCI overhead.

In some embodiments, bit width of the CBGTI field may be of M bits, wherein M is maximum number of scheduled PDSCHs by single DCI configured by the network device; and the first number is equal to or less than M; and the second number is equal to or less than M.

In some embodiments, each of M bits may correspond to one PDSCH of the second number of PDSCHs on multiple slots scheduled by the DCI, value of a bit of bits corresponding to the at least one retransmission in the CBGTI field indicates that whether retransmission of one TB via a corresponding PDSCH includes at least one unsuccessfully transmitted CBG or all CBGs.

In some embodiments, the value 1 may indicate that at least one unsuccessfully transmitted CBG of one retransmitted TB is scheduled to be retransmitted, and the value 0 indicates that all CBGs of one retransmitted TB, at least one CBG of which is unsuccessfully decoded, are scheduled to be retransmitted.

In some embodiments, the method may further comprise: in response to decode the initial transmission of the first set of TBs, storing each CBG decoding result of each TB, and in response to receive at least one retransmitted TB of the second set of TBs, decoding the at least one retransmitted CBG of the at least one retransmitted TB based on the decoding result and the value of each bit in the CBGTI field.

In some embodiments, the value of one or more bits, corresponding to the at least one retransmission, in the CBGTI field may indicate that whether the at least one retransmission via the second number of PDSCHs include a set of unsuccessfully transmitted CBGs of each of the at least one retransmitted TB or all CBGs of each of the at least one retransmitted TB.

In some embodiments, the value 1 of CBGTI field of 1 bit may indicate that the at least one retransmissions via the second number of PDSCHs include only a set of unsuccessfully transmitted CBGs of each of the at least one retransmitted TB, and the value 0 of CBGTI field of 1 bit indicates that the at least one retransmissions via the second number of PDSCHs include all CBGs of each of the at least one retransmitted TB.

In some embodiments, the method may further comprise: in response to decode the initial transmission of one or more TBs, storing each CBG decoding result of each TB, and in response to receive at least one retransmitted TB of the second set of TBs, decoding at least one retransmitted CBG of the at least one retransmitted TB based on the decoding result and the value of CBGTI field of 1 bit.

In some embodiments, the method may further comprise: receiving, at the terminal device from the network device, an RRC configuration indicating bit width of the CBGTI field H, wherein H is equal to or larger than N, wherein N is maximum number of CBGs per TB configured by the network device.

In some embodiment, in response to H is equal to or larger than Q, wherein Q is the product of N and the second number: the first Q bits in the CBGTI filed may have a bit mapping relationship with Q1 CBGs of the second number of PDSCHs and Q2 padding bits, and Q=Q1+Q2.

In some embodiments, the value 0 of each bit may be indicate that the corresponding CBG is not retransmitted or the bit is padded with 0, and the value 1 of each bit indicates that the corresponding CBG is retransmitted.

In some embodiments, in response to that H is equal to or less than Q, wherein Q is the product of N and the second number: the H bits of CBGTI field may be divided into the second number of groups, and the number of bits of each group is determined based on H and the second number; and each bit of the CBGTI field corresponds to a CBG bundle of one of the second number of PDSCHs, and the number of CBGs for each CBG bundle is determined based on the number of bits of each group and N.

In some embodiments, the value 0 of each bit may indicate that the corresponding CBG bundle is not retransmitted, and the value 1 of each bit indicates that the corresponding CBG bundle is retransmitted.

In some embodiments, the second set of TBs may further comprise a third set of TBs that are initially transmitted, and a total number of the second set of TBs and the third set of TBs is equal to the second number.

FIG. 11 illustrates an example method 1100 of communication implemented at a network device in accordance with some embodiments of the present disclosure. For example, the method 1100 may be performed at the network device 120 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1100 will be described with reference to FIG. 1. It is to be understood that the method 1100 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

At block 1110, the network device 120 transmits transmitting, at a network device and to a terminal device, a first set of TBs each comprising one or more CBGs via a first number of PDSCHs. At block 1120, the network device 120 transmits a second set of TBs comprising at least one retransmission of the first set of TBs via a second number of PDSCHs on multiple slots scheduled by a DCI comprising a CBGTI field. By the method of FIG. 11, the scheme of scheduling CBG-based multi-slot PDSCHs retransmission by a single may be support, and the CBGTI indication in the DCI can be designed to support the CBG-based multi-slot PDSCHs retransmission and also reduce the DCI overhead.

FIG. 12 illustrates another example method 1200 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. For example, the method 1200 may be performed at the terminal device 110 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1200 will be described with reference to FIG. 1. It is to be understood that the method 1200 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

At block 1210, the terminal device 110 receives from a network device data via a plurality of CBG based PDSCHs on multiple slots scheduled by a first DCI. At block 1220, in accordance with determination that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, the terminal device 110 determines the HARQ-ACK codebook based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold configured by the network device. At block 1230, the terminal device 110 transmits the HARQ-ACK codebook on the PUCCH resource to the network device, wherein the corresponding DCI is any one of the first DCI, the second DCI, the third DCI and the fourth DCI, and the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs. By the method of FIG. 12, the Type 2 HARQ-ACK codebook for CBG-based multi-slot PDSCHs scheduling can be constructed, and can support the CBG-based multi-slot PDSCHs scheduling.

In some embodiments, the number of generated HARQ-ACK information bits associated with the second DCI may be 1 bit; the number of generated HARQ-ACK information bits associated with the third DCI may be based on the maximum number of CBGs per TB configured by the network device; the number of generated HARQ-ACK information bits associated with the fourth DCI may be based on the maximum number of scheduled PDSCHs by single DCI configured by the network device; and the number of generated HARQ-ACK information bits associated with the first DCI may be based on a product of the maximum number of CBGs per TB configured by the network device and the maximum number of scheduled PDSCHs by single DCI configured by the network device.

In some embodiments, the HARQ-ACK codebook may comprise a first sub-codebook and a second sub-codebook, in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is equal to or less than the first threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the first sub-codebook, and in the first sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the first threshold; or in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is larger than the first threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the second sub-codebook, and in the second sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the product of the maximum number of CBGs per TB configured by the network device and the maximum number of scheduled PDSCHs by single DCI configured by the network device.

In some embodiments, the HARQ-ACK codebook may comprise a first sub-codebook, a second sub-codebook and a third sub-codebook, the method further comprises: receiving, at the terminal device from a network device, an indication for a second threshold, in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is equal to or less than the first threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the first sub-codebook, and in the first sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the first threshold; or in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is larger than the first threshold and equal to or less than the second threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the second sub-codebook, and in the second sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the second threshold; or in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is larger than the second threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the third sub-codebook, and in the third sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the product of the maximum number of CBGs per TB configured by the network device and the maximum number of scheduled PDSCH by single DCI configured by the network device .

FIG. 13 illustrates an example method 1300 of communication implemented at a network device in accordance with some embodiments of the present disclosure. For example, the method 1300 may be performed at the network device 120 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1300 will be described with reference to FIG. 1. It is to be understood that the method 1300 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

At block 1310, the network device 120 transmits, to terminal device 110, data via a plurality of CBG based PDSCHs on multiple slots scheduled by a first DCI. At block 1320, the network device 120 transmits, to terminal device 110, an indication that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based PDSCHs and PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs. At block 1330, the network device 120 receives the HARQ-ACK codebook on a PUCCH resource generated at the terminal device, wherein the HARQ-ACK codebook is determined based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold configured by the network device, and the corresponding DCI is any one of the first DCI, the second DCI, the third DCI and the fourth DCI. By the method of FIG. 13, the Type 2 HARQ-ACK codebook for CBG-based multi-slot PDSCHs scheduling can be constructed, and can support the CBG-based multi-slot PDSCHs scheduling.

FIG. 14 illustrates an example method 1400 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. For example, the method 1400 may be performed at the terminal device 110 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1400 will be described with reference to FIG. 1. It is to be understood that the method 1400 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

At block 1410, the terminal device 110 receives from a network device 120, data via a plurality of CBG based PDSCHs on multiple slots scheduled by a DCI. At block 1420, the terminal device generates a set of HARQ-acknowledgement (HARQ-ACK) positions in a HARQ-ACK codebook for HARQ-ACK information bits for each PDSCH of the plurality of CBG based PDSCHs scheduled by the DCI. At block 1430, the terminal device 110 reports HARQ-ACK information for the plurality of CBG based PDSCHs in the HARQ-ACK codebook to the network device. By the method of FIG. 14, the HARQ-ACK codebook generated for CBG-based multi-slot PDSCHs scheduled by a single DCI can have a lower HARQ-ACK payload and have a reduced HARQ-ACK redundancy.

In some embodiments, the number of HARQ-ACK positions for the plurality of CBG based PDSCHs on multiple slots scheduled by the DCI may be a constant Q, and wherein Q is configured by RRC signaling.

In some embodiments, the method may further comprise: in response to that the number of the plurality of CBG based PDSCHs scheduled by a DCI is M, determining the number of generated HARQ-ACK positions for each PDSCH of the plurality of CBG based PDSCHs based on Q and M.

In some embodiments, in the generated HARQ-ACK positions for a corresponding PDSCH, each HARQ-ACK position may correspond to a CBG bundle of the corresponding PDSCH; and the number of CBGs in each CBG bundle is determined based on N, Q and M, where N is the number of CBGs for TB in the corresponding PDSCH.

In some embodiments, the HARQ-ACK information for the plurality of CBG based PDSCHs on multiple slots scheduled by a DCI may comprise a first portion and a second portion, and wherein the number of HARQ-ACK information bits of the second portion is determined on the HARQ-ACK information in the first portion.

In some embodiments, the first portion may comprise TB-based HARQ-ACK information for each PDSCH of the plurality of CBG based PDSCHs, and the second portion may comprise CBG-based HARQ-ACK information for a set of incorrectly decoded PDSCHs of the plurality of CBG based PDSCHs, M HARQ-ACK positions is generated in the first portion for the plurality of CBG based PDSCHs, where M is the value of the maximum number of scheduled PDSCHs by single DCI configured by the network device; and in response to that one of the plurality of CBG based PDSCHs is successfully decoded, 1 bit of TB ACK is generated in the first portion; in response to that one of the plurality of CBG based PDSCHs is unsuccessfully decoded, 1 bit of TB NACK is generated in the first portion, and N bits of CBG based ACK/NACK for the unsuccessfully decoded TB are generated in the second portion, wherein N is the maximum number of CBGs per TB configured by the network device, and N*P HARQ-ACK positions are generated for the second portion, wherein P is the total number of unsuccessfully decoded TBs of the plurality of CBG based PDSCHs.

In some embodiments, the first portion and the second portion may be multiplexed on a HARQ-ACK codebook and transmitted to the network device via a same PUCCH, and the network device is configured to decode the second portion of the HARQ-ACK codebook after successfully decoding the first portion of the HARQ-ACK codebook.

In some embodiments, the first portion and the second portion may be separately transmitted in two HARQ-ACK codebooks to the network device via two PUCCHs, the first portion of TB-based HARQ-ACK information is transmitted via a first PUCCH of the two PUCCHs, and the second portion of CBG-based HARQ-ACK information is transmitted via a second PUCCH of the two PUCCHs.

In some embodiments, in response to that one of the plurality of CBG based PDSCHs is unsuccessfully decoded, the second portion of CBG-based HARQ-ACK information transmitted via the second PUCCH may be triggered by the terminal device.

FIG. 15 illustrates an example method 1500 of communication implemented at a network device in accordance with some embodiments of the present disclosure. For example, the method 1500 may be performed at the network device 120 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1500 will be described with reference to FIG. 1. It is to be understood that the method 1500 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

At block 1510, the network device 120 transmits to a terminal device 110 data via a plurality of CBG based PDSCHs on multiple slots scheduled by a DCI. At block 1520, the network device 120 receives HARQ-ACK information for the plurality of CBG based PDSCHs in a HARQ-ACK codebook from the terminal device. By the method of FIG. 15, the HARQ-ACK codebook generated for CBG-based multi-slot PDSCHs scheduled by a single DCI can have a lower HARQ-ACK payload and have a reduced HARQ-ACK redundancy.

FIG. 16 illustrates another example method 1600 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. For example, the method 1600 may be performed at the terminal device 110 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1600 will be described with reference to FIG. 1. It is to be understood that the method 1600 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

At block 1610, the terminal device 110 receives from a network device 120, data transmitted via a plurality of PDSCHs on a plurality of cells scheduled by a first DCI. At block 1620, in accordance with determination that HARQ-acknowledgement (HARQ-ACK) information for the plurality of PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs, determining the HARQ-ACK codebook for the plurality of PDSCHs scheduled by the first DCI, wherein the HARQ-ACK codebook comprises TB-based sub-codebook and CBG-based sub-codebook. At block 1630, the terminal device 110 transmits the HARQ-ACK codebook to the network device. By method of FIG. 16, the scheme of CBG-based multi-cell PDSCHs scheduling transmission can be supported.

In some embodiments, in response to that all of the plurality of PDSCHs on the plurality of cells scheduled by the first DCI are CBG based transmission, HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI may belong to the CBG-based sub-codebook, and in response to that all of the plurality of PDSCHs on the plurality of cells scheduled by the first DCI are TB based transmission, HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI may belong to the TB-based sub-codebook.

In some embodiments, each cell may be configured with CBG based transmission or TB based transmission, each DCI may comprise one C-DAI or a pair of C-DAI and T-DAI, in response to that the plurality of PDSCHs scheduled by the first DCI are transmitted on both TB based cells and on CBG based cells, the C-DAI of the first DCI may be counted as for CBG-based sub-codebook; and HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI is placed in the CBG-based sub-codebook.

In some embodiments, each cell may be configured with CBG based transmission or TB based transmission, each DCI may comprise a first C-DAI and a second C-DAIs or a first pair of C-DAI and T-DAI and a second pair of C-DAI and T-DAI , in response to that the plurality of PDSCHs scheduled by the first DCI are transmitted on both TB based cells and CBG based cells, the first C-DAI or the first pair of C-DAI and T-DAI of the first DCI may be counted as for the CBG-based sub-codebook, and the second C-DAI or the second pair of C-DAI and T-DAI of the first DCI may be counted as for the TB-based sub-codebook, and HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI is separately placed in the CBG-based sub-codebook and the TB-based sub-codebook.

FIG. 17 illustrates an example method 1700 of communication implemented at a network device in accordance with some embodiments of the present disclosure. For example, the method 1700 may be performed at the network device 120 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1700 will be described with reference to FIG. 1. It is to be understood that the method 1700 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

At block 1710, the network device 120 transmits, to a terminal device, data transmitted via a plurality of PDSCHs on a plurality of cells scheduled by a first DCI. At block 1720, the network device 120 transmits to the terminal device, an indication that HARQ-acknowledgement (HARQ-ACK) information for the plurality of PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs. At block 1730, the network device 120 receives a HARQ-acknowledgement (HARQ-ACK) codebook generated at the terminal device, wherein the HARQ-ACK codebook comprises TB-based sub-codebook and CBG-based codebook. By method of FIG. 17, the scheme of CBG-based multi-cell PDSCHs scheduling transmission can be supported.

FIG. 18 is a simplified block diagram of a device 1800 that is suitable for implementing embodiments of the present disclosure. The device 1800 can be considered as a further example implementation of the terminal device 110 or the network device 120 as shown in FIG. 1. Accordingly, the device 1800 can be implemented at or as at least a part of the terminal device 110 or the network device 120.

As shown, the device 1800 includes a processor 1810, a memory 1820 coupled to the processor 1810, a suitable transmitter (TX) and receiver (RX) 1840 coupled to the processor 1810, and a communication interface coupled to the TX/RX 1840. The memory 1810 stores at least a part of a program 1830. The TX/RX 1840 is for bidirectional communications. The TX/RX 1840 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.

The program 1830 is assumed to include program instructions that, when executed by the associated processor 1810, enable the device 1800 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGs. 2 to 9. The embodiments herein may be implemented by computer software executable by the processor 1810 of the device 1800, or by hardware, or by a combination of software and hardware. The processor 1810 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1810 and memory 1820 may form processing means 1850 adapted to implement various embodiments of the present disclosure.

The memory 1820 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1820 is shown in the device 1800, there may be several physically distinct memory modules in the device 1800. The processor 1810 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

In some embodiments, a terminal device 110 comprises circuitry configured to perform any one of

methods

1000, 1200, 1400 and 1600. In some embodiments, a network device 120 comprises circuitry configured to perform any one of

methods

1100, 1300, 1500 and 1700.

The components included in the apparatuses and/or devices of the present disclosure may be implemented in various manners, including software, hardware, firmware, or any combination thereof. In one embodiment, one or more units may be implemented using software and/or firmware, for example, machine-executable instructions stored on the storage medium. In addition to or instead of machine-executable instructions, parts or all of the units in the apparatuses and/or devices may be implemented, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs) , Application-specific Integrated Circuits (ASICs) , Application-specific Standard Products (ASSPs) , System-on-a-chip systems (SOCs) , Complex Programmable Logic Devices (CPLDs) , and the like.

The term “circuitry” used herein may refer to hardware circuits and/or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.

Generally, 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 which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

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 those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGs. 10 to 17. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out 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, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection 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. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, 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 particular embodiments. Certain features that are described in the context of separate 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 sub-combination.

In summary, embodiments of the present disclosure may provide the following solutions.

A method of communication comprises: receiving, at a terminal device from a network device, initial transmission of a first set of TBs each comprising one or more CBGs via a first number of PDSCHs; receiving, from the network device, a DCI scheduling a second set of TBs comprising at least one retransmitted TB of the first set of TBs via a second number of PDSCHs on multiple slots; and determining, at a terminal device, at least one CBG of the at least one retransmission of TB based on CBGTI field in the DCI.

In some embodiments, bit width of the CBGTI field is of M bits, wherein M is maximum number of scheduled PDSCHs by single DCI configured by the network device; and the first number is equal to or less than M; and the second number is equal to or less than M.

In some embodiments, each of M bits corresponds to one PDSCH of the second number of PDSCHs on multiple slots scheduled by the DCI, value of a bit of bits corresponding to the at least one retransmission in the CBGTI field indicates that whether retransmission of one TB via a corresponding PDSCH includes at least one unsuccessfully transmitted CBG or all CBGs.

In some embodiments, the value 1 indicates that at least one unsuccessfully transmitted CBG of one retransmitted TB is scheduled to be retransmitted, and the value 0 indicates that all CBGs of one retransmitted TB, at least one CBG of which is unsuccessfully decoded, are scheduled to be retransmitted.

In some embodiments, the method further comprises: in response to decode the initial transmission of the first set of TBs, storing each CBG decoding result of each TB, and in response to receive at least one retransmitted TB of the second set of TBs, decoding the at least one retransmitted CBG of the at least one retransmitted TB based on the decoding result and the value of each bit in the CBGTI field.

In some embodiments, the value of one or more bits, corresponding to the at least one retransmission, in the CBGTI field indicates that whether the at least one retransmission via the second number of PDSCHs include a set of unsuccessfully transmitted CBGs of each of the at least one retransmitted TB or all CBGs of each of the at least one retransmitted TB.

In some embodiments, the value 1 of CBGTI field of 1 bit indicates that the at least one retransmissions via the second number of PDSCHs include only a set of unsuccessfully transmitted CBGs of each of the at least one retransmitted TB, and the value 0 of CBGTI field of 1 bit indicates that the at least one retransmissions via the second number of PDSCHs include all CBGs of each of the at least one retransmitted TB.

In some embodiments, the method further comprises: in response to decode the initial transmission of one or more TBs, storing each CBG decoding result of each TB, and in response to receive at least one retransmitted TB of the second set of TBs, decoding at least one retransmitted CBG of the at least one retransmitted TB based on the decoding result and the value of CBGTI field of 1 bit.

In some embodiments, the method further comprises: receiving, at the terminal device from the network device, an RRC configuration indicating bit width of the CBGTI field H, wherein H is equal to or larger than N, wherein N is maximum number of CBGs per TB configured by the network device.

In some embodiment, in response to H is equal to or larger than Q, wherein Q is the product of N and the second number: the first Q bits in the CBGTI filed have a bit mapping relationship with Q1 CBGs of the second number of PDSCHs and Q2 padding bits, and Q=Q1+Q2.

In some embodiments, the value 0 of each bit indicates that the corresponding CBG is not retransmitted or the bit is padded with 0, and the value 1 of each bit indicates that the corresponding CBG is retransmitted.

In some embodiments, in response to that H is equal to or less than Q, wherein Q is the product of N and the second number: the H bits of CBGTI field are divided into the second number of groups, and the number of bits of each group is determined based on H and the second number; and each bit of the CBGTI field corresponds to a CBG bundle of one of the second number of PDSCHs, and the number of CBGs for each CBG bundle is determined based on the number of bits of each group and N.

In some embodiments, the value 0 of each bit indicates that the corresponding CBG bundle is not retransmitted, and the value 1 of each bit indicates that the corresponding CBG bundle is retransmitted.

In some embodiments, the second set of TBs further comprise a third set of TBs that are initially transmitted, and a total number of the second set of TBs and the third set of TBs is equal to the second number.

A method of communication comprises: transmitting, at a network device and to a terminal device, a first set of TBs each comprising one or more CBGs via a first number of PDSCHs; and transmitting, a second set of TBs comprising at least one retransmission of the first set of TBs via a second number of PDSCHs on multiple slots scheduled by a DCI comprising a CBGTI field.

A method of communication comprises: receiving, at a terminal device from a network device, data via a plurality of CBG based PDSCHs on multiple slots scheduled by a first DCI; in accordance with determination that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook: determining the HARQ-ACK codebook based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold configured by the network device; and transmitting the HARQ-ACK codebook on the PUCCH resource to the network device, wherein the corresponding DCI is any one of the first DCI, the second DCI, the third DCI and the fourth DCI, and the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs.

In some embodiments, the number of generated HARQ-ACK information bits associated with the second DCI is 1 bit; the number of generated HARQ-ACK information bits associated with the third DCI is based on the maximum number of CBGs per TB configured by the network device; the number of generated HARQ-ACK information bits associated with the fourth DCI is based on the maximum number of scheduled PDSCHs by single DCI configured by the network device; and the number of generated HARQ-ACK information bits associated with the first DCI is based on a product of the maximum number of CBGs per TB configured by the network device and the maximum number of scheduled PDSCHs by single DCI configured by the network device.

In some embodiments, the HARQ-ACK codebook comprises a first sub-codebook and a second sub-codebook, in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is equal to or less than the first threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the first sub-codebook, and in the first sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the first threshold; or in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is larger than the first threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the second sub-codebook, and in the second sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the product of the maximum number of CBGs per TB configured by the network device and the maximum number of scheduled PDSCHs by single DCI configured by the network device.

In some embodiments, the HARQ-ACK codebook comprises a first sub-codebook, a second sub-codebook and a third sub-codebook, the method further comprises: receiving, at the terminal device from a network device, an indication for a second threshold, in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is equal to or less than the first threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the first sub-codebook, and in the first sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the first threshold; or in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is larger than the first threshold and equal to or less than the second threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the second sub-codebook, and in the second sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the second threshold; or in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is larger than the second threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the third sub-codebook, and in the third sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the product of the maximum number of CBGs per TB configured by the network device and the maximum number of scheduled PDSCH by single DCI configured by the network device .

. A method of communication, comprising: transmitting, to a terminal device, data via a plurality of CBG based PDSCHs on multiple slots scheduled by a first DCI; transmitting, to the terminal device, an indication that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based PDSCHs and PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs; and receiving the HARQ-ACK codebook on a PUCCH resource generated at the terminal device, wherein the HARQ-ACK codebook is determined based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold configured by the network device, and the corresponding DCI is any one of the first DCI, the second DCI, the third DCI and the fourth DCI.

A method of communication comprises receiving, at a terminal device from a network device, data via a plurality of CBG based PDSCHs on multiple slots scheduled by a DCI; generating a set of HARQ-acknowledgement (HARQ-ACK) positions in a HARQ-ACK codebook for HARQ-ACK information bits for each PDSCH of the plurality of CBG based PDSCHs scheduled by the DCI; and reporting HARQ-ACK information for the plurality of CBG based PDSCHs in the HARQ-ACK codebook to the network device.

In some embodiments, the number of HARQ-ACK positions for the plurality of CBG based PDSCHs on multiple slots scheduled by the DCI is a constant Q, and wherein Q is configured by RRC signaling.

In some embodiments, the method further comprises: in response to that the number of the plurality of CBG based PDSCHs scheduled by a DCI is M, determining the number of generated HARQ-ACK positions for each PDSCH of the plurality of CBG based PDSCHs based on Q and M.

In some embodiments, in the generated HARQ-ACK positions for a corresponding PDSCH, each HARQ-ACK position corresponds to a CBG bundle of the corresponding PDSCH; and the number of CBGs in each CBG bundle is determined based on N, Q and M, where N is the number of CBGs for TB in the corresponding PDSCH.

In some embodiments, the HARQ-ACK information for the plurality of CBG based PDSCHs on multiple slots scheduled by a DCI comprises a first portion and a second portion, and wherein the number of HARQ-ACK information bits of the second portion is determined on the HARQ-ACK information in the first portion.

In some embodiments, the first portion comprises TB-based HARQ-ACK information for each PDSCH of the plurality of CBG based PDSCHs, and the second portion comprises CBG-based HARQ-ACK information for a set of incorrectly decoded PDSCHs of the plurality of CBG based PDSCHs, M HARQ-ACK positions is generated in the first portion for the plurality of CBG based PDSCHs, where M is the value of the maximum number of scheduled PDSCHs by single DCI configured by the network device; and in response to that one of the plurality of CBG based PDSCHs is successfully decoded, 1 bit of TB ACK is generated in the first portion; in response to that one of the plurality of CBG based PDSCHs is unsuccessfully decoded, 1 bit of TB NACK is generated in the first portion, and N bits of CBG based ACK/NACK for the unsuccessfully decoded TB are generated in the second portion, wherein N is the maximum number of CBGs per TB configured by the network device, and N*P HARQ-ACK positions are generated for the second portion, wherein P is the total number of unsuccessfully decoded TBs of the plurality of CBG based PDSCHs.

In some embodiments, the first portion and the second portion are multiplexed on a HARQ-ACK codebook and transmitted to the network device via a same PUCCH, and the network device is configured to decode the second portion of the HARQ-ACK codebook after successfully decoding the first portion of the HARQ-ACK codebook.

In some embodiments, the first portion and the second portion are separately transmitted in two HARQ-ACK codebooks to the network device via two PUCCHs, the first portion of TB-based HARQ-ACK information is transmitted via a first PUCCH of the two PUCCHs, and the second portion of CBG-based HARQ-ACK information is transmitted via a second PUCCH of the two PUCCHs.

In some embodiments, in response to that one of the plurality of CBG based PDSCHs is unsuccessfully decoded, the second portion of CBG-based HARQ-ACK information transmitted via the second PUCCH is triggered by the terminal device.

A method of communication comprises: transmitting, to a terminal device from a network device, data via a plurality of CBG based PDSCHs on multiple slots scheduled by a DCI; and receiving HARQ-ACK information for the plurality of CBG based PDSCHs in a HARQ-ACK codebook from the terminal device.

A method of communication comprises: receiving, at a terminal device from a network device, data transmitted via a plurality of PDSCHs on a plurality of cells scheduled by a first DCI; in accordance with determination that HARQ-acknowledgement (HARQ-ACK) information for the plurality of PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBGs based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs, determining the HARQ-ACK codebook, wherein the HARQ-ACK codebook comprises TB-based sub-codebook and CBG-based sub-codebook; and transmitting the HARQ-ACK codebook to the network device.

In some embodiments, in response to that all of the plurality of PDSCHs on the plurality of cells scheduled by the first DCI are CBG based transmission, HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI belongs to the CBG-based sub-codebook, and in response to that all of the plurality of PDSCHs on the plurality of cells scheduled by the first DCI are TB based transmission, HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI belongs to the TB-based sub-codebook.

In some embodiments, each cell is configured with CBG based transmission or TB based transmission, each DCI comprises one C-DAI or a pair of C-DAI and T-DAI, in response to that the plurality of PDSCHs scheduled by the first DCI are transmitted on both TB based cells and on CBG based cells, that is to say, a set PDSCHs of the plurality of PDSCHs are TB based transmission, another set PDSCHs of the plurality of PDSCHs are CBG based transmission, the C-DAI of the first DCI is counted as for CBG-based sub-codebook; and HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI is placed in the CBG-based sub-codebook.

In some embodiments, each cell is configured with CBG based transmission or TB based transmission, each DCI comprises a first C-DAI and a second C-DAIs or a first pair of C-DAI and T-DAI and a second pair of C-DAI and T-DAI , in response to that the plurality of PDSCHs scheduled by the first DCI are transmitted on both TB based cells and CBG based cells, the first C-DAI or the first pair of C-DAI and T-DAI of the first DCI is counted as for the CBG-based sub-codebook, and the second C-DAI or the second pair of C-DAI and T-DAI of the first DCI is counted as for the TB-based sub-codebook, and HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI is separately placed in the CBG-based sub-codebook and the TB-based sub-codebook.

A method of communication comprises: transmitting, to a terminal device from a network device, data transmitted via a plurality of PDSCHs on a plurality of cells scheduled by a first DCI; transmitting, to the terminal device, an indication that HARQ-acknowledgement (HARQ-ACK) information for the plurality of PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs , and receiving a HARQ-acknowledgement (HARQ-ACK) codebook generated at the terminal device, wherein the HARQ-ACK codebook comprises TB-based sub-codebook and CBG-based codebook.

Although the present disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the present disclosure 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

A method of communication, comprising:

receiving, at a terminal device from a network device, initial transmission of a first set of transport blocks (TBs) each comprising one or more code block groups (CBGs) via a first number of physical downlink shared channels (PDSCHs) ;

receiving, from the network device, a downlink control information (DCI) scheduling a second set of TBs comprising at least one retransmission of the first set of TBs via a second number of PDSCHs on multiple slots; and

determining, at the terminal device, at least one CBG of the at least one retransmission of TB based on CBG transmission information (CBGTI) field in the DCI.
The method of claim 1, wherein bit width of the CBGTI field is of M bits, wherein M is maximum number of scheduled PDSCHs by single DCI configured by the network device;

the first number is equal to or less than M; and

the second number is equal to or less than M.
The method of claim 2, wherein each of M bits corresponds to one PDSCH of the second number of PDSCHs on multiple slots scheduled by the DCI,

value of a bit of bits corresponding to the at least one retransmission in the CBGTI field indicates that whether retransmission of one TB via a corresponding PDSCH includes at least one unsuccessfully transmitted CBG or all CBGs.
The method of claim 1, wherein value of one or more bits, corresponding to the at least one retransmission, in the CBGTI field indicates that whether the at least one retransmissions via the second number of PDSCHs includes a set of unsuccessfully transmitted CBGs or all CBGs.
The method of claim 1, further comprising:

receiving, at the terminal device from the network device, an RRC configuration indicating bit width of the CBGTI field H,

wherein H is equal to or larger than N, wherein N is maximum number of CBGs per TB configured by the network device.
The method of claim 5, wherein in response to that H is equal to or larger than Q, wherein Q is the product of N and the second number,

the first Q bits in the CBGTI filed have a bit mapping relationship with Q1 CBGs of the second number of PDSCHs and Q2 padding bits, and Q=Q1+Q2.
The method of claim 5, wherein in response to that H is equal to or less than Q, wherein Q is the product of N and the second number:

the H bits of CBGTI field are divided into the second number of groups, and the number of bits of each group is determined based on H and the second number; and

each bit of the CBGTI field corresponds to a CBG bundle of one of the second number of PDSCHs, and the number of CBGs for each CBG bundle is determined based on the number of bits of each group and N.
A method of communication, comprising:

transmitting, at a network device to a terminal device, a first set of transport blocks (TBs) each comprising one or more code block groups (CBGs) via a first number of physical downlink shared channels (PDSCHs) ; and

transmitting, a second set of TBs comprising at least one retransmission of the first set of TBs via a second number of PDSCHs on multiple slots scheduled by a downlink control information (DCI) comprising a CBG transmission information (CBGTI) field.
A method of communication, comprising:

receiving, at a terminal device from a network device, data via a plurality of code block group (CBG) based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a first downlink control information (DCI) ; in accordance with determination that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, determining the HARQ-ACK codebook based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold configured by the network device, wherein the corresponding DCI is any one of the first DCI, the second DCI, the third DCI and the fourth DCI, and the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs; and

transmitting the HARQ-ACK codebook on a PUCCH resource to the network device.
The method of claim 9, wherein the number of generated HARQ-ACK information bits associated with the second DCI is 1 bit;

the number of generated HARQ-ACK information bits associated with the third DCI is based on the maximum number of CBGs per TB configured by the network device;

the number of generated HARQ-ACK information bits associated with the fourth DCI is based on the maximum number of scheduled PDSCHs by single DCI configured by the network device; and

the number of generated HARQ-ACK information bits associated with the first DCI is based on a product of the maximum number of CBGs per TB configured by the network device and the maximum number of scheduled PDSCHs by single DCI configured by the network device.
The method of claim 10, wherein the HARQ-ACK codebook comprises a first sub-codebook and a second sub-codebook,

in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is equal to or less than the first threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the first sub-codebook, and in the first sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the first threshold; or

in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is larger than the first threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the second sub-codebook, and in the second sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the product of the maximum number of CBGs per TB configured by the network device and the maximum number of scheduled PDSCHs by single DCI configured by the network device.
The method of claim 10, wherein the HARQ-ACK codebook comprises a first sub-codebook, a second sub-codebook and a third sub-codebook,

the method further comprises:

receiving, at the terminal device from a network device, an indication for a second threshold,

in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is equal to or less than the first threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the first sub-codebook, and in the first sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the first threshold; or

in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is larger than the first threshold and equal to or less than the second threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the second sub-codebook, and in the second sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the second threshold; or

in response to that the number of generated HARQ-ACK information bits associated with the corresponding DCI is larger than the second threshold, the generated respective HARQ-ACK information bits associated with this DCI is determined to belong to the third sub-codebook, and in the third sub-codebook, the number of generated HARQ-ACK positions for this DCI is equal to the product of the maximum number of CBGs per TB configured by the network device and the maximum number of scheduled PDSCH by single DCI configured by the network device.
A method of communication, comprising:

transmitting, to a terminal device, data via a plurality of code block group (CBG) based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a first downlink control information (DCI) ;

transmitting, to the terminal device, an indication that HARQ-acknowledgement (HARQ-ACK) information for the plurality of CBG based PDSCHs and PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule CBG based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs; and

receiving the HARQ-ACK codebook on a PUCCH resource generated at the terminal device, wherein the HARQ-ACK codebook is determined based on the number of generated HARQ-ACK information bits associated with a corresponding DCI and a first threshold configured by the network device, and the corresponding DCI is any one of the first DCI, the second DCI, the third DCI and the fourth DCI.
A method of communication, comprising:

receiving, at a terminal device from a network device, data via a plurality of code block group (CBG) based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a downlink control information (DCI) ;

generating a set of HARQ-acknowledgement (HARQ-ACK) positions in a HARQ-ACK codebook for HARQ-ACK information bits for each PDSCH of the plurality of CBG based PDSCHs scheduled by the DCI; and

reporting HARQ-ACK information for the plurality of CBG based physical downlink shared channels (PDSCHs) in the HARQ-ACK codebook to the network device.
The method of claim 14, wherein the number of HARQ-ACK positions for the plurality of CBG based PDSCHs on multiple slots scheduled by the DCI is a constant Q, and

wherein Q is configured by RRC signaling.
The method of claim 15, further comprising:

in response to that the number of the plurality of CBG based PDSCHs scheduled by a DCI is M, determining the number of generated HARQ-ACK positions for each PDSCH of the plurality of CBG based PDSCHs based on Q and M;

wherein in the generated HARQ-ACK positions for a corresponding PDSCH, each HARQ-ACK position corresponds to a CBG bundle of the corresponding PDSCH; and

the number of CBGs in each CBG bundle is determined based on N, Q and M, where N is the number of CBGs for TB in the corresponding PDSCH.
The method of claim 14, wherein

the HARQ-ACK information for the plurality of CBG based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a DCI comprises a first portion and a second portion, and

wherein the number of HARQ-ACK information bits of the second portion is determined on the HARQ-ACK information in the first portion.
The method of claim 17, wherein the first portion comprises TB-based HARQ-ACK information for each PDSCH of the plurality of CBG based PDSCHs, and the second portion comprises CBG-based HARQ-ACK information for a set of incorrectly decoded PDSCHs of the plurality of CBG based PDSCHs,

M HARQ-ACK positions are generated in the first portion for the plurality of CBG based PDSCHs, where M is the value of the maximum number of scheduled PDSCH by single DCI configured by the network device; and

in response to that one of the plurality of CBG based PDSCHs is successfully decoded, 1 bit of TB ACK is generated in the first portion; or

in response to that one of the plurality of CBG based PDSCHs is unsuccessfully decoded, 1 bit of TB NACK is generated in the first portion, and N bits of CBG based ACK/NACK for the unsuccessfully decoded TB are generated in the second portion, where N is the maximum number of CBGs per TB configured by the network device; and

N*P HARQ-ACK positions are generated for the second portion, wherein P is the total number of unsuccessfully decoded TBs of the plurality of CBG based PDSCHs.
The method of claim 18, wherein the first portion and the second portion are multiplexed on a HARQ-ACK codebook and transmitted to the network device via a same PUCCH, and

the network device is configured to decode the second portion of the HARQ-ACK codebook after successfully decoding the first portion of the HARQ-ACK codebook.
The method of claim 18, wherein the first portion and the second portion are separately transmitted in two HARQ-ACK codebooks to the network device via two PUCCHs,

the first portion of TB-based HARQ-ACK information is transmitted via a first PUCCH of the two PUCCHs, and

the second portion of CBG-based HARQ-ACK information is transmitted via a second PUCCH of the two PUCCHs; and

in response to that one of the plurality of CBG based PDSCHs is unsuccessfully decoded, the second portion of CBG-based HARQ-ACK information transmitted via the second PUCCH is triggered by the terminal device.
A method of communication, comprising:

transmitting, to a terminal device from a network device, data via a plurality of code block group (CBG) based physical downlink shared channels (PDSCHs) on multiple slots scheduled by a downlink control information (DCI) ; and

receiving HARQ-ACK information for the plurality of CBG based PDSCHs in a HARQ-ACK codebook from the terminal device.
A method of communication, comprising:

receiving, at a terminal device from a network device, data transmitted via a plurality of physical downlink shared channels (PDSCHs) on a plurality of cells scheduled by a first downlink control information (DCI) ;

in accordance with determination that HARQ-acknowledgement (HARQ-ACK) information for the plurality of PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule code block groups (CBG) based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs, determining the HARQ-ACK codebook for the plurality of PDSCHs , wherein the HARQ-ACK codebook comprises TB-based sub-codebook and CBG-based sub-codebook; and

transmitting the HARQ-ACK codebook to the network device.
The method of claim 22, wherein in response to that all of the plurality of PDSCHs on the plurality of cells scheduled by the first DCI are CBG based transmission, HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI belongs to the CBG-based sub-codebook, and

in response to that all of the plurality of PDSCHs on the plurality of cells scheduled by the first DCI are TB based transmission, HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI belongs to the TB-based sub-codebook.
The method of claim 22, wherein each cell is configured with CBG based transmission or TB based transmission,

each DCI comprises one C-DAI or a pair of C-DAI and T-DAI,

in response to that the plurality of PDSCHs scheduled by the first DCI are transmitted on both TB based cells and on CBG based cells, the C-DAI of the first DCI is counted as for CBG-based sub-codebook; and

HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI is placed in the CBG-based sub-codebook.
The method of claim 22, wherein each cell is configured with CBG based transmission or TB based transmission,

each DCI comprises a first C-DAI and a second C-DAIs or a first pair of C-DAI and T-DAI and a second pair of C-DAI and T-DAI ,

in response to that the plurality of PDSCHs scheduled by the first DCI are transmitted on both TB based cells and CBG based cells, the first C-DAI or the first pair of C-DAI and T-DAI of the first DCI is counted as for the CBG-based sub-codebook, and the second C-DAI or the second pair of C-DAI and T-DAI of the first DCI is counted as for the TB-based sub-codebook, and

HARQ-ACK information for the plurality of PDSCHs scheduled by the first DCI is separately placed in the CBG-based sub-codebook and the TB-based sub-codebook.
A method of communication, comprising:

transmitting, to a terminal device from a network device, data transmitted via a plurality of physical downlink shared channels (PDSCHs) on a plurality of cells scheduled by a first downlink control information (DCI) ;

transmitting, to the terminal device, an indication that HARQ-acknowledgement (HARQ-ACK) information for the plurality of PDSCHs and HARQ-ACK information for PDSCHs scheduled by at least one of a second DCI, a third DCI and a fourth DCI are multiplexed on a HARQ-ACK codebook, wherein the second DCI is used to schedule TB based single PDSCH, the third DCI is used to schedule code block group (CBG) based single PDSCH and the fourth DCI is used to schedule TB based multi-slot PDSCHs , and

receiving a HARQ-acknowledgement (HARQ-ACK) codebook for the plurality of PDSCHs generated at the terminal device,

wherein the HARQ-ACK codebook comprises TB-based sub-codebook and CBG-based codebook.