WO2022053843A1

WO2022053843A1 - Apparatus and method of communication

Info

Publication number: WO2022053843A1
Application number: PCT/IB2020/000761
Authority: WO
Inventors: Hao Lin
Original assignee: Orope France Sarl
Priority date: 2020-09-11
Filing date: 2020-09-11
Publication date: 2022-03-17

Abstract

An apparatus and a method of communication are provided. The method of communication of a user equipment (UE) includes receiving, by the UE, a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot from a base station; and transmitting, by the LIE, a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codehook in the first PUCCH transmission occasion to the base station, wherein the first HARQ-ACK codebook is relevant to the first HARQ process. This can increase a transmission throughput that can resolve a bottleneck due to a long round trip time.

Description

APPARATUS AND METHOD OF COMMUNICATION BACKGROUND OF DISCLOSURE 1. Field of the Disclosure [0001] The present disclosure relates to the field of communication systems, and more particularly, to an apparatus (such as a user equipment (UE) and/or a base station) and a method of communication in a non-terrestrial network (NTN), which can provide a good communication performance and/or provide high reliability. 2. Description of the Related Art [0002] Non-terrestrial networks (NTNs) refer to networks, or segments of networks, using a spaceborne vehicle or an airborne vehicle for transmission. Spaceborne vehicles include satellites including low earth orbiting (LEO) satellites, medium earth orbiting (MEO) satellites, geostationary earth orbiting (GEO) satellites, and highly elliptical orbiting (HEO) satellites. Airborne vehicles include high altitude platforms (HAPs) encompassing unmanned aircraft systems (UAS) including lighter than air (LTA) unmanned aerial systems (UAS) and heavier than air (HTA) UAS, all operating in altitudes typically between 8 and 50 km, quasi-stationary. [0003] Communication via a satellite is an interesting means thanks to its well-known coverage, which can bring the coverage to locations that normally cellular operators are not willing to deploy either due to non-stable crowd potential client, e.g. extreme rural, or due to high deployment cost, e.g. middle of ocean or mountain peak. Nowadays, the satellite communication is a separate technology to a 3rd generation partnership project (3GPP) cellular technology. Coming to 5G era, these two technologies can merge together, i.e. we can imagine having a 5G terminal that can access to a cellular network and a satellite network. The NTN can be good candidate technology for this purpose. It is to be designed based on 3GPP new radio (NR) with necessary enhancement. [0004] In NTN system, due to the very long round trip time (RTT) between the satellite and the user equipment, the transmission throughput is limited. The UE needs to wait long time to report the hybrid automatic repeat request acknowledgement (HARQ-ACK) information of a received physical downlink shared channel (PDSCH) in a physical uplink control channel (PUCCH) transmission. [0005] Therefore, there is a need for an apparatus (such as a user equipment (UE) and/or a base station) and a method of communication, which can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, provide a good communication performance and/or provide high reliability. SUMMARY [0006] An object of the present disclosure is to propose an apparatus (such as a user equipment (UE) and/or a base station) and a method of communication, which can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, provide a good communication performance and/or provide high reliability. [0007] In a first aspect of the present disclosure, a method of communication of a user equipment comprises receiving, by the UE, a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot from a base station; and transmitting, by the UE, a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission occasion to the base station, wherein the first HARQ-ACK codebook is relevant to the first HARQ process. [0008] In a second aspect of the present disclosure, a user equipment of communication comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver. The transceiver is configured to: receive a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot from a base station; and transmit a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission occasion to the base station, wherein the first HARQ-ACK codebook is relevant to the first HARQ process. [0009] In a third aspect of the present disclosure, a method of communication of a base station comprises configuring, by the base station, a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot to a user equipment (UE); and receiving, by the base station, a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission occasion from the UE, wherein the first HARQ-ACK codebook is relevant to the first HARQ process. [0010] In a fourth aspect of the present disclosure, a base station of communication comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to configure a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot to a user equipment (UE). The transceiver is configured to receive a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission occasion from the UE, wherein the first HARQ-ACK codebook is relevant to the first HARQ process. [0011] In a fifth aspect of the present disclosure, a method of communication of a user equipment comprises determining, by the UE, that physical downlink shared channels (PDSCHs) are divided into N groups, wherein N is an integer equal to or greater than 1; determining, by the UE, a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ processes are divided into N groups; and determining, by the UE, that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration. [0012] In a sixth aspect of the present disclosure, a user equipment of communication comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to: determine that physical downlink shared channels (PDSCHs) are divided into N groups, wherein N is an integer equal to or greater than 1; determine a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ processes are divided into N groups; and determine that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration. [0013] In a seventh aspect of the present disclosure, a method of communication of a base station comprises configuring, by the base station, physical downlink shared channels (PDSCHs) that are divided into N groups, wherein N is an integer equal to or greater than 1; configuring, by the base station, a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ processes are divided into N groups; and configuring, by the base station, that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration. [0014] In an eighth aspect of the present disclosure, a base station of communication comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to: configure physical downlink shared channels (PDSCHs) that are divided into N groups, wherein N is an integer equal to or greater than 1; configure a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ processes are divided into N groups; and configure that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration. [0015] In a ninth aspect of the present disclosure, a non-transitory machine-readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method. [0016] In a tenth aspect of the present disclosure, a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method. [0017] In an eleventh aspect of the present disclosure, a computer readable storage medium, in which a computer program is stored, causes a computer to execute the above method. [0018] In a twelfth aspect of the present disclosure, a computer program product includes a computer program, and the computer program causes a computer to execute the above method. [0019] In a thirteenth aspect of the present disclosure, a computer program causes a computer to execute the above method. BRIEF DESCRIPTION OF DRAWINGS [0020] In order to illustrate the embodiments of the present disclosure or related art more clearly, the following figures will be described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person having ordinary skill in this field can obtain other figures according to these figures without paying the premise. [0021] FIG.1 is a block diagram of one or more user equipments (UEs) and a base station (e.g., gNB) of communication in a communication network system (e.g., non-terrestrial network (NTN)) according to an embodiment of the present disclosure. [0022] FIG. 2 is a flowchart illustrating a method of communication of a user equipment in a non-terrestrial network (NTN) according to an embodiment of the present disclosure. [0023] FIG.3 is a flowchart illustrating a method of communication of a base station in a non-terrestrial network (NTN) according to an embodiment of the present disclosure. [0024] FIG. 4 is a flowchart illustrating a method of communication of a user equipment in a non-terrestrial network (NTN) according to an embodiment of the present disclosure. [0025] FIG.5 is a flowchart illustrating a method of communication of a base station in a non-terrestrial network (NTN) according to an embodiment of the present disclosure. [0026] FIG. 6 is a schematic diagram illustrating a communication system including a base station (BS) and a UE according to an embodiment of the present disclosure. [0027] FIG.7 is a schematic diagram illustrating that a BS transmits 3 beams to the ground forming 3 footprints according to an embodiment of the present disclosure. [0028] FIG.8 is a schematic diagram illustrating a method of a hybrid automatic repeat request (HARQ) process group configuration for an NTN system according to an embodiment of the present disclosure. [0029] FIG.9 is a schematic diagram illustrating a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI) applied for each HARQ process group for an NTN system according to an embodiment of the present disclosure. [0030] FIG.10 is a schematic diagram illustrating a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI) applied for each HARQ process group for an NTN system according to another embodiment of the present disclosure. [0031] FIG.11 is a schematic diagram illustrating a method of HARQ feedback for an NTN system according to another embodiment of the present disclosure. [0032] FIG.12 is a schematic diagram illustrating a method of HARQ feedback for an NTN system according to another embodiment of the present disclosure. [0033] FIG.13 is a schematic diagram illustrating a method of HARQ feedback for an NTN system according to another embodiment of the present disclosure. [0034] FIG.14 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF EMBODIMENTS [0035] Embodiments of the present disclosure are described in detail with the technical matters, structural features, achieved objects, and effects with reference to the accompanying drawings as follows. Specifically, the terminologies in the embodiments of the present disclosure are merely for describing the purpose of the certain embodiment, but not to limit the disclosure. [0036] FIG.1 illustrates that, in some embodiments, one or more user equipments (UEs) 10 and a base station (e.g., gNB) 20 for transmission adjustment in a communication network system 30 (e.g., non-terrestrial network (NTN)) according to an embodiment of the present disclosure are provided. The communication network system 30 includes the one or more UEs 10 and the base station 20. The one or more UEs 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12, the transceiver 13. The base station 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22, the transceiver 23. The processor 11 or 21 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of radio interface protocol may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively coupled with the processor 11 or 21 and stores a variety of information to operate the processor 11 or 21. The transceiver 13 or 23 is operatively coupled with the processor 11 or 21, and the transceiver 13 or 23 transmits and/or receives a radio signal. [0037] The processor 11 or 21 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and/or data processing device. The memory 12 or 22 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and/or other storage device. The transceiver 13 or 23 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the memory 12 or 22 and executed by the processor 11 or 21. The memory 12 or 22 can be implemented within the processor 11 or 21 or external to the processor 11 or 21 in which case those can be communicatively coupled to the processor 11 or 21 via various means as is known in the art. [0038] In some embodiments, the communication between the UE 10 and the BS 20 comprises non-terrestrial network (NTN) communication. In some embodiments, the base station 20 comprises spaceborne platform or airborne platform or high altitude platform station. [0039] In some embodiments, the transceiver 13 is configured to: receive a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot from the base station 20; and transmit a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission occasion to the base station 20, wherein the first HARQ-ACK codebook is relevant to the first HARQ process. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, provide a good communication performance and/or provide high reliability. This can also enable a HARQ disabling, which allows the base station to consecutively transmit PDSCHs that correspond to a same HARQ process number. Moreover, some methods are provided for the UE to feedback the HARQ-ACK information of the transmitted or received PDSCHs corresponding to the same HARQ process number. Further, this can solve an issue where HARQ disabling is configured. [0040] In some embodiments, the processor 21 is configured to configure a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot to the UE 10. The transceiver 23 is configured to receive a first hybrid automatic repeat request acknowledgement (HARQ- ACK) codebook in the first PUCCH transmission occasion from the UE 10, wherein the first HARQ-ACK codebook is relevant to the first HARQ process. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, provide a good communication performance and/or provide high reliability. This can also enable a HARQ disabling, which allows the base station to consecutively transmit PDSCHs that correspond to a same HARQ process number. Moreover, some methods are provided for the UE to feedback the HARQ-ACK information of the transmitted or received PDSCHs corresponding to the same HARQ process number. Further, this can solve an issue where HARQ disabling is configured. [0041] In some embodiments, the processor 11 is configured to: determine that physical downlink shared channels (PDSCHs) are divided into N groups, wherein N is an integer equal to or greater than 1; determine a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ processes are divided into N groups; and determine that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, provide a good communication performance and/or provide high reliability. This can also enable a HARQ disabling, which allows the base station to consecutively transmit PDSCHs that correspond to a same HARQ process number. Moreover, some methods are provided for the UE to feedback the HARQ-ACK information of the transmitted or received PDSCHs corresponding to the same HARQ process number. Further, this can solve an issue where HARQ disabling is configured. [0042] In some embodiments, the processor 21 is configured to: configure physical downlink shared channels (PDSCHs) that are divided into N groups, wherein N is an integer equal to or greater than 1; configure a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ processes are divided into N groups; and configure that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, provide a good communication performance and/or provide high reliability. This can also enable a HARQ disabling, which allows the base station to consecutively transmit PDSCHs that correspond to a same HARQ process number. Moreover, some methods are provided for the UE to feedback the HARQ-ACK information of the transmitted or received PDSCHs corresponding to the same HARQ process number. Further, this can solve an issue where HARQ disabling is configured. [0043] FIG. 2 illustrates a method 200 of communication of a UE in a communication network system (e.g., non- terrestrial network (NTN)) according to an embodiment of the present disclosure. In some embodiments, the method 200 includes: a block 202, receiving, by the UE, a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot from a base station; and a block 204, transmitting, by the UE, a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission occasion to the base station, wherein the first HARQ-ACK codebook is relevant to the first HARQ process. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, provide a good communication performance and/or provide high reliability. This can also enable a HARQ disabling, which allows the base station to consecutively transmit PDSCHs that correspond to a same HARQ process number. Moreover, some methods are provided for the UE to feedback the HARQ-ACK information of the transmitted or received PDSCHs corresponding to the same HARQ process number. Further, this can solve an issue where HARQ disabling is configured. [0044] FIG. 3 illustrates a method 300 of communication of a BS in a communication network system (e.g., non- terrestrial network (NTN)) according to an embodiment of the present disclosure. In some embodiments, the method 300 includes: a block 302, configuring, by the base station, a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot to a UE; and a block 304, receiving, by the base station, a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission occasion from the UE, wherein the first HARQ-ACK codebook is relevant to the first HARQ process. This can also enable a HARQ disabling, which allows the base station to consecutively transmit PDSCHs that correspond to a same HARQ process number. Moreover, some methods are provided for the UE to feedback the HARQ-ACK information of the transmitted or received PDSCHs corresponding to the same HARQ process number. Further, this can solve an issue where HARQ disabling is configured. [0045] In some embodiments, the first PDSCH is scheduled by a first downlink control information (DCI) format. In some embodiments, the first PDSCH is configured by the base station. In some embodiments, the first PDSCH comprises semi-persistent scheduling (SPS)-PDSCH. In some embodiments, the first DCI format comprises a first indication field, wherein the first HARQ process is indicated at least by the first indication field. In some embodiments, the first DCI format comprises a second indication field, wherein the second indication field indicates that the first PUCCH transmission occasion is in the first slot or in the first sub-slot . In some embodiments, the second indication field comprises PDSCH-to- HARQ_feedback timing indicator field. In some embodiments, the first HARQ process is configured by a base station to be associated with a first HARQ process group or a first HARQ process type or a first HARQ process function or a first HARQ process status. In some embodiments, the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status comprises at least one of the followings: HARQ feedback enabled or HARQ feedback disabled. In some embodiments, a first radio resource control (RRC) parameter is configured by the base station for the first HARQ process, and the first RRC parameter indicates HARQ feedback enabled or HARQ feedback disabled for the first HARQ process. In some embodiments, when the first RRC parameter is absent for the first HARQ process, the first HARQ process is associated with a default HARQ process group or a default HARQ process type or a default HARQ process function or a default HARQ process status. In some embodiments, the default process group or the default HARQ process type or the default HARQ process function or the default HARQ process status comprises HARQ feedback enabled or HARQ feedback disabled. [0046] In some embodiments, the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status is associated with one or more HARQ processes. In some embodiments, the first DCI format comprises a third indication field, wherein the third indication field comprises a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI). In some embodiments, a value of the C-DAI is counted within the first HARQ process group or within the first HARQ process type or within the first HARQ process function or within the first HARQ process status. In some embodiments, the C-DAI denotes that an accumulative number of {serving cell, physical downlink control channel (PDCCH) monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release, associated with one or more HARQ processes corresponding to the first HARQ process type or the first HARQ process function or the first HARQ process status, is present up to a current serving cell and a current PDCCH monitoring occasion. In some embodiments, the T-DAI is counted within the first HARQ process group or within the first HARQ process type or within the first HARQ process function or within the first HARQ process status. In some embodiments, the T-DAI denotes a total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release associated with one or more HARQ processes corresponding to the first HARQ process type or the first HARQ process function or the first HARQ process status, up to a current PDCCH monitoring occasion. In some embodiments, the first DCI format comprises: DCI format 1_0 and/or DCI format 1_1 and/or DCI format 1_2 and/or DCI format 1_3. In some embodiments, the first DCI format is used to schedule PDSCH in a serving cell. In some embodiments, the first DCI format is CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI. In some embodiments, the first HARQ-ACK codebook comprises at least one of the followings: a type 1 HARQ-ACK codebook, a type 2 HARQ-ACK codebook, a type 3 HARQ- ACK codebook, or a type 4 HARQ-ACK codebook. In some embodiments, the type 1 HARQ-ACK codebook contains a constant number of bits, which further comprises a first one or more bits and/or a second one or more bits. In some embodiments, the first one or more bits comprise one or more HARQ-ACK information corresponding to a first set of one or more received PDSCHs associated with one or more HARQ processes that are of the first HARQ process group, or the first HARQ process type or the first HARQ process function or the first HARQ process status, wherein the first set of one or more received PDSCHs comprise the first PDSCH. [0047] In some embodiments, the first set of one or more received PDSCHs are indicated with a same slot as the first slot or the first sub-slot for PUCCH transmission occasion. In some embodiments, the second one or more bits comprise one or more invalid HARQ-ACK information corresponding to a second set of one or more received PDSCHs associated with one or more HARQ processes that are of a second HARQ process group or a second HARQ process type or a second HARQ process function or a second HARQ process status. In some embodiments, the second one or more bits comprise one or more HARQ-ACK information corresponding to a second set of one or more received PDSCHs associated with one or more HARQ processes that are of a second HARQ process group or a second HARQ process type or a second HARQ process function or a second HARQ process status. In some embodiments, the PUCCH transmission occasion of the second set of one or more received PDSCHs is indicated to be a same slot as the first slot or the first sub-slot. In some embodiments, invalid HARQ-ACK information comprises HARQ-ACK value equal to negative acknowledgement (NACK). In some embodiments, when the first set of one or more PDSCHs only contain the first PDSCH, the UE only reports the HARQ- ACK information corresponding to the first PDSCH in the first PUCCH transmission occasion. In some embodiments, the C-DAI indicated by the first DCI format is equal to 1. In some embodiments, the type 2 HARQ-ACK codebook comprises a codebook size relevant to a T-DAI value, where the T-DAI value is corresponding to a last received PDSCH allocated with a PUCCH transmission occasion in the first slot or the first sub-slot. In some embodiments, the last received PDSCH is associated with a HARQ process of the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status. In some embodiments, the type 3 HARQ-ACK codebook comprises a number of HARQ-ACK bits which is relevant to a number of configured HARQ processes for a serving cell. In some embodiments, the type 3 HARQ-ACK codebook comprises a number of HARQ-ACK bits which is relevant to a number of configured HARQ processes associated with the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status for a serving cell. In some embodiments, the method further comprises reporting, by the UE, NACK corresponding to one or more HARQ processes associated with the second HARQ process group or the second HARQ process type or the second HARQ process function or the second HARQ process status. [0048] In some embodiments, the type 4 HARQ-ACK codebook does not contain an explicit HARQ-ACK information corresponding the first PDSCH. In some embodiments, the type 4 HARQ-ACK codebook comprises an information relevant to a decoding outcome of one or more PDSCHs associated with the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status. In some embodiments, the decoding outcome comprises at least one of the followings: a ratio between a number of successfully decoded PDSCHs and a total number of PDSCHs; or a number of successfully decoded PDSCHs. In some embodiments, the total number of PDSCHs is indicated by a T-DAI value, where the T-DAI value is corresponding to a last received PDSCH whose PUCCH transmission occasion is in the first slot or the first sub-slot. In some embodiments, the type 4 HARQ-ACK codebook comprises an amount of bits, wherein the amount is determined at least by one of the followings: configured by the base station, or predefined value, or indicated in the first DCI format, or by a T-DAI value, where the T-DAI value is corresponding to a last received PDSCH whose PUCCH transmission occasion is in the first slot or the first sub-slot. In some embodiments, the first codebook is configured by the base station to be associated with the first HARQ process or a first HARQ process group or a first HARQ process type or a first HARQ process function or a first HARQ process status. [0049] In some embodiments, the method further comprises receiving, by the UE, a second PDSCH associated with a second HARQ process, wherein the base station indicates a PUCCH transmission occasion for second PDSCH in the first slot or the first sub-slot; and transmitting, by the UE, the first HARQ-ACK codebook in the first PUCCH. In some embodiments, the method further comprises receiving, by the UE, a second PDSCH associated with a second HARQ process, wherein the base station indicates a PUCCH transmission occasion for second PDSCH in the first slot or the first sub-slot; and transmitting, by the UE, a second HARQ-ACK codebook in the first PUCCH, wherein the second HARQ process is associated with a second HARQ process group or a second process type or a second process function or a second process status. In some embodiments, the second HARQ-ACK codebook is appended after the first HARQ-ACK codebook. In some embodiments, the second HARQ-ACK codebook is configured by the base station to be associated with the second HARQ process or with the second HARQ process group or the second process type or the second process function or the second process status. In some embodiments, the second HARQ process group or the second process type or the second process function or the second process status comprises HARQ enabling or HARQ disabling. In some embodiments, the second HARQ-ACK codebook comprises at least one of the followings: the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, the type 3 HARQ-ACK codebook, or the type 4 HARQ-ACK codebook. [0050] FIG. 4 illustrates a method 400 of communication of a UE in a communication network system (e.g., non- terrestrial network (NTN)) according to an embodiment of the present disclosure. In some embodiments, the method 400 includes: a block 402,^determining, by the UE, that physical downlink shared channels (PDSCHs) are divided into N groups, wherein N is an integer equal to or greater than 1; a block 404, determining, by the UE, a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ processes are divided into N groups; and a block 406, determining, by the UE, that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, provide a good communication performance and/or provide high reliability. This can also enable a HARQ disabling, which allows the base station to consecutively transmit PDSCHs that correspond to a same HARQ process number. Moreover, some methods are provided for the UE to feedback the HARQ-ACK information of the transmitted or received PDSCHs corresponding to the same HARQ process number. Further, this can solve an issue where HARQ disabling is configured. [0051] FIG. 5 illustrates a method 500 of communication of a BS in a communication network system (e.g., non- terrestrial network (NTN)) according to an embodiment of the present disclosure. In some embodiments, the method 500 includes: a block 502, configuring, by the base station, physical downlink shared channels (PDSCHs) that are divided into N groups, wherein N is an integer equal to or greater than 1; a block 504, configuring, by the base station, a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ processes are divided into N groups; and a block 506, configuring, by the base station, that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, provide a good communication performance, and/or provide high reliability. This can also enable a HARQ disabling, which allows the base station to consecutively transmit PDSCHs that correspond to a same HARQ process number. Moreover, some methods are provided for the UE to feedback the HARQ-ACK information of the transmitted or received PDSCHs corresponding to the same HARQ process number. Further, this can solve an issue where HARQ disabling is configured. [0052] In some embodiments, when N is equal to 1, all the HARQ processes are of the same group, and all the PDSCHs are belong to the same HARQ process group. In some embodiments, when N is greater than 1, several of the HARQ processes are of different groups, and several of the PDSCHs are belong to different HARQ process groups. In some embodiments, the method further comprises determining downlink control information (DCI) format, wherein the DCI format contains one or more HARQ process numbers to indicate one or more PDSCHs are associated with the one or more HARQ process numbers. In some embodiments, the DCI format is used to schedule the PDSCHs. In some embodiments, a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI) is in the DCI format, and the C-DAI and/or the T-DAI is accumulated within each HARQ process group. In some embodiments, the DCI format comprises a DCI format 1_1, a DCI format 1_2, or a DCI format 1_3. In some embodiments, when the UE is configured with one serving cell, the DCI format scheduling the PDSCHs does not contain T-DAI. In some embodiments, when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group. [0053] In some embodiments, when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group; when another several of the PDSCHs are scheduled in another same HARQ process group, C-DAI values corresponding to the another several of the PDSCHs are continuously counted in the another same HARQ process group. In some embodiments, when the UE is configured with more than one serving cell, the HARQ process group configuration can be configured per serving cell. In some embodiments, cross different serving cells, HARQ process group configurations can be different. In some embodiments, the same HARQ process group configuration can be applied for all the serving cells. In some embodiments, when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values and T-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group. In some embodiments, when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values and T-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group; when another several of the PDSCHs are scheduled in another same HARQ process group, C-DAI values and T-DAI values corresponding to the another several of the PDSCHs are continuously counted in the another same HARQ process group. [0054] In some embodiments, the DCI format indicates a corresponding physical uplink control channel (PUCCH) resource for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback. In some embodiments, the method further comprises transmitting a corresponding HARQ-ACK codebook in the PUCCH resource according to an association between one or more HARQ process numbers and N HARQ process groups. In some embodiments, the HARQ-ACK codebook comprises a type 1 HARQ-ACK codebook, a type 2 HARQ-ACK codebook, a type 3 HARQ-ACK codebook, or a type 4 HARQ-ACK codebook. In some embodiments, in the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, or the type 3 HARQ-ACK codebook, HARQ-ACK information of the PDSCHs are reported. In some embodiments, the type 4 HARQ-ACK codebook comprises information relevant to a ratio of successful decoding of all the PDSCHs within N HARQ process groups. In some embodiments, the ratio is calculated by a number of the successfully decoded PDSCHs over total transmitted PDSCHs, where the PDSCHs are counted within a given HARQ process group. In some embodiments, a total number of the PDSCHs in a given HARQ process group is based on T-DAI. In some embodiments, the ratio can be quantized into M bits, where M is equal to 0 or an integer equal to or greater than 1. In some embodiments, the type 4 HARQ-ACK codebook has a constant codebook size. In some embodiments, the constant codebook size of the type 4 HARQ-ACK codebook is configured or pre-defined. [0055] In some embodiments, the constant codebook size of the type 4 HARQ-ACK codebook is zero or non-zero. In some embodiments, all the PDSCHs are belong to the same HARQ process group and one HARQ-ACK codebook is transmitted in the PUCCH resource. In some embodiments, all the PDSCHs are belong to different HARQ process groups and different HARQ-ACK codebooks are separately transmitted in different PUCCH resources. In some embodiments, all the PDSCHs are belong to different HARQ process groups and are allocated in the same slot, different HARQ-ACK codebooks are transmitted in the same PUCCH resource, and the different HARQ-ACK codebooks are concatenated codebooks. In some embodiments, when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 1 HARQ-ACK codebook is semi-static configured and comprises a bit location for one or more PDSCHs belong to the second HARQ-ACK group, the UE sets NACK for the bit location corresponding to the one or more PDSCHs belong to the second HARQ-ACK group, and/or the UE sets a valid ACK or NACK information for one or more PDSCHs belong to the first HARQ process group. In some embodiments, when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 1 HARQ-ACK codebook is semi-static configured and comprises a bit location for one or more PDSCHs belong to the second HARQ-ACK group, the UE is configured whether to set NACK for the bit location corresponding to the one or more PDSCHs belong to the second HARQ- ACK group and/or to set a valid ACK or NACK information for one or more PDSCHs belong to the first HARQ process group. [0056] In some embodiments, when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, if the UE receives a first PDSCH associated with the first HARQ process group and receives one or more PDSCHs associated with the second HARQ process group within a whole PDSCH reception window, and/or the first PDSCH is scheduled by a DCI with DCI format 1_0 and/or the DCI format 1_0 indicating a counter DAI field value of 1 on a primary cell (PCell), and/or the first PDSCH is a semi- persistent scheduling (SPS) PDSCH, the UE reports an HARQ-ACK information of the first PDSCH in the corresponding PUCCH resource. In some embodiments, when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, if the UE receives a SPS PDSCH release indicated by a DCI format 1_0 with a counter DAI field value of 1 on a PCell and receives one or more PDSCHs associated with the second HARQ process group within a whole PDSCH reception window, the UE reports an HARQ-ACK information of the SPS PDSCH release in the corresponding PUCCH resource. In some embodiments, the UE reports NACK of the one or more PDSCHs associated with the second HARQ process group. In some embodiments, the UE reports an HARQ-ACK information of the one or more PDSCHs associated with the second HARQ process group. In some embodiments, the UE is configured to report NACK or an HARQ-ACK information of the one or more PDSCHs associated with the second HARQ process group. In some embodiments, when the type 3 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 3 HARQ-ACK codebook comprises an HARQ-ACK information of a HARQ process associated with the first HARQ process group 1. In some embodiments, the type 3 HARQ-ACK codebook comprises the HARQ-ACK information corresponding to all the HARQ processes. In some embodiments, a selection of whether or not to comprises the HARQ-information for all the HARQ processes can depend on at least one of the followings: network configuration, or DCI indication, or PUCCH resource allocated for different HARQ process groups. [0057] FIG. 6 illustrates a communication system including a base station (BS) and a UE according to another embodiment of the present disclosure. Optionally, the communication system may include more than one base stations, and each of the base stations may connect to one or more UEs. In this disclosure, there is no limit. As an example, the base station illustrated in FIG.1 may be a moving base station, e.g. spaceborne vehicle (satellite) or airborne vehicle (drone). The UE can transmit transmissions to the base station and the UE can also receive the transmission from the base station. Optionally, not shown in FIG. 6, the moving base station can also serve as a relay which relays the received transmission from the UE to a ground base station or vice versa. [0058] Spaceborne platform includes satellite and the satellite includes LEO satellite, MEO satellite and GEO satellite. While the satellite is moving, the LEO and MEO satellite is moving with regards to a given location on earth. However, for GEO satellite, the GEO satellite is relatively static with regards to a given location on earth. A spaceborne or airborne base station (BS), e.g. in particular for LEO satellite or drone, communicates with a user equipment (UE) on the ground. The round trip time (RTT) between them is time varying due to the mobility of the base station. The RTT variation is related to the distance variation between the BS and the UE. The RTT variation rate is proportional to the BS motion velocity. To ensure a good uplink synchronization, the BS will adjust the uplink transmission timing and/or frequency for the UE. [0059] Optionally, as illustrated in FIG.7, where a base station is integrated in a satellite or a drone, and the base station transmits one or more beams to the ground forming one or more coverage areas called footprint. In FIG. 7, an example illustrates that the BS transmits three beams (beam 1, beam 2 and beam3) to form three footprints (footprint 1, 2 and 3), respectively. Optionally, 3 beams are transmitted at 3 different frequencies. In this example, the bit position is associated with a beam. FIG.7 illustrates that, in some embodiments, a moving base station, e.g. in particular for LEO satellite or drone, communicates with a user equipment (UE) on the ground. Due to long distance between the UE and the base station on satellite the beamformed transmission is needed to extend the coverage. As illustrated in FIG. 7, where a base station is transmitting three beams to the earth forming three coverage areas called footpoints. Moreover, each beam may be transmitted at dedicated frequencies so that the beams for footprint 1, 2 and 3 are non-overlapped in a frequency domain. [0060] In NTN system, due to very long round trip time between the satellite and the user equipment, for downlink transmissions, e.g. PDSCH transmission, in some embodiments, we consider a case where a network (such as a base station) may configure different types of PDSCHs, and separate these PDSCHs into different groups. Then HARQ-ACK feedbacks for different PDSCH groups are different. For example, a UE will report actual HARQ-ACK information of a PDSCH group 1 and report statistical status of a PDSCH group 2. The definition of HARQ process group can be in the form of grouping by the base station or can also be that the base station defines different HARQ process types/functions/states(status)/features, the same type is counted as one group, and different types are counted as different groups. In one embodiment, the base station defines two types: type 1: HARQ enabled and type 2: HARQ disabled. The type can be configured by the base station through a specific parameter. This parameter can configure different types of HARQ processes. [0061] Example: HARQ process group configuration [0062] FIG.8 illustrates a method of a hybrid automatic repeat request (HARQ) process group configuration for an NTN system according to an embodiment of the present disclosure. FIG.8 illustrates that, in some embodiments, a HARQ process group configuration is provided. A network such as a base station can separate scheduled PDSCHs into N groups, where N is an integer number and N can be 1 or more than 1. One example of group determination is via HARQ process configuration, e.g. the network divides a number of configured HARQ processes into N groups. [0063] In some embodiments, when N is equal to 1, all the configured HARQ processes are of the same group. It is to say that all the scheduled PDSCHs are belong to the same group. [0064] In some embodiments, when N is equal to 2, the network divides the configured HARQ processes into two groups (i.e. group 1 and group 2). Assuming there are in total 16 HARQ processes (HARQ processes 0 to 15^or can also be referred to as HARQ 0 to 15) configured for a UE for a given serving cell, and the network configures HARQ processes 0, 1, and 2 into HARQ process group 1 and HARQ processes 3, 4, 5, 6, 7, 8,9, 10, 11, 12, 13, 14, and 15 into HARQ process group 2, as illustrated in FIG.8. [0065] Further, for a PDSCH scheduled by a DCI, the DCI contains a HARQ process number to indicate the PDSCH is associated with the HARQ process number. Then, the UE can determine the PDSCH belongs to which HARQ process group. For example, if the scheduled PDSCH is associated with HARQ 0, then the PDSCH belongs to group 1. On the other hand, if the scheduled PDSCH is associated with HARQ 5, then the PDSCH belongs to group 2, as illustrated in FIG.8. [0066] In some examples, the HARQ process group is equivalent to HARQ process type or HARQ process status. A base station can configure two different HARQ process types or HARQ process status, e.g. HARQ enabling and HARQ disabling. Optionally, the HARQ process type or status is configured by a RRC parameter for each HARQ process, if the RRC parameter indicates HARQ enabling for a HARQ process, the HARQ process is associated with the HARQ process type or status of HARQ enabling; while if the RRC parameter indicates HARQ disabling for a HARQ process, the HARQ process is associated with the HARQ process type or status of HARQ disabling. The HARQ processes associated with the same HARQ process type or status are in the same HARQ process group. Optionally, for a HARQ process, if the RRC parameter is configured, the HARQ process is associated with a pre-defined HARQ process type or status, e.g. HARQ disabling; while if the RRC parameter is not configured for a HARQ process, the HARQ process is associated with a default HARQ process type or status, e.g. default HARQ process type or status is HARQ enabling. The HARQ processes associated with the same HARQ process type or status are in the same HARQ process group. [0067] Example: C-DAI and/or T-DAI applied for each HARQ process group [0068] FIG.9 illustrates a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI) applied for each HARQ process group for an NTN system according to an embodiment of the present disclosure. FIG.10 illustrates a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI) applied for each HARQ process group for an NTN system according to another embodiment of the present disclosure. FIG.9 and FIG.10 illustrate that, in some embodiments, C-DAI and/or T-DAI applied for each HARQ process group is provided. Some embodiments are provided that C-DAI and/or T-DAI are accumulated within a HARQ process group, where the HARQ process group is configured by a network (such as a base station) with regards to the HARQ process number. When a UE receives a DCI scheduling a PDSCH, the UE determines the HARQ process group based on the indicated HARQ process number. In some embodiments, the network schedules a PDSCH transmission by a DCI format, in which there is an indication field, C-DAI (For example, a current number of PDSCH in the corresponding group), when a UE is configured with more than one serving cell and when the PDSCH is scheduled with DCI format 1_1 or format 1_2 or format 1_3 and/or T-DAI (For example, the total number of PDSCHs in the corresponding group). [0069] In some embodiments, the C-DAI and/or the T-DAI are accumulated within each HARQ process group. This means that there is C-DAI and/or T-DAI for HARQ process group 1, e.g. C_DAI_g1/T-DAI_g1. Similarly, there is C-DAI and/or T-DAI for HARQ process group 2, e.g. C_DAI_g2/T-DAI_g2. When the network schedules a PDSCH1 using a HARQ process group 1, the network only updates the C_DAI_ g 1 and/or T-DAI_ g 1. It is to note that in a DCI scheduling a PDSCH1, the indication field C_DAI and/or T_DAI is to be read together with the indicated HARQ process number to determine if the indicated C_DAI and/or T_DAI belongs to group 1 or group 2. Following the above example, if the scheduled PDSCH is associated with HARQ 0, then the PDSCH belongs to group 1, and the C-DAI and/or T-DAI in the scheduled DCI represents C_DAI_g1/T-DAI_g1. On the other hand, if the scheduled PDSCH is associated with HARQ 5, then the PDSCH belongs to group 2, and the C-DAI and/or T-DAI in the scheduled DCI represents C_DAI_g2/T-DAI_g2. [0070] FIG.9 illustrates that, in some embodiments, a UE is configured with one serving cell, therefore the DCI format scheduling PDSCH does not contain T-DAI indication field. From an example of FIG.9, when the PDSCH is scheduled in the same HARQ process group, the C-DAI is counted within this group, for instance, the PDSCH 1, PDSCH 2, and PDSCH 4 are scheduled in the same HARQ process group 1, therefore C-DAI values corresponding to these PDSCHs are continuously counted. Similarly, the PDSCH3, PDSCH5, and PDSCH6 are scheduled within the same HARQ process group 2, thus their C-DAI values are continuously counted. [0071] FIG.10 illustrates that, in some embodiments, if a UE is configured with more than one serving cell, the HARQ process group configuration, as illustrated in FIG.8 can be configured per serving cell, i.e. for configured serving cell, there is a HARQ process group configuration, and cross different serving cells, the HARQ process group configuration can be different. Optionally, to reduce the configuration overhead, a same HARQ process group configuration can be applied for all the configured serving cells, i.e. for serving cell 1, cell 2, and cell 3, HARQ processes 0, 1, and 2 (or can also be referred to as HARQ 0, 1, and 2) belong to the same HARQ process group 1 according to configuration example in FIG.8, and the rest of the HARQ processes (HARQ 3, 3, and 5) are in the HARQ process group 2. Similar to FIG.9, in an example of FIG. 10, the C-DAI and T-DAI are continuously counted for group 1 and group 2 separately. When the UE receives PDSCH 1 associated with HARQ process 0 in slot n, the (C-DAI, T-DAI) in the scheduling DCI format indicates (1,2), it means that in HARQ group 1, up to slot n, there are two PDSCHs scheduled and the PDSCH 1 is the first PDSCH. When the UE receives a scheduling DCI for PDSCH3 associated with HARQ process 1, (C-DAI, T_DAI) = (2,2), means that in HARQ process group 1, up to slot n, there are two PDSCHs scheduled and the PDSCH 3 is the second PDSCH. When the UE receives PDSCH 6 associated with HARQ process 2 in slot n+3, the (C-DAI, T-DAI) in the scheduling DCI format indicates (3,3), it means that in HARQ group 1, up to slot n+3, there are three PDSCHs scheduled and the PDSCH 6 is the third PDSCH. Similar interpretation is applied for PDSCHs scheduled in the other HARQ process group (HARQ process group 2). In details, When the UE receives PDSCH 2 associated with HARQ process 3 in slot n, the (C-DAI, T-DAI) in the scheduling DCI format indicates (1,1), it means that in HARQ group 2, up to slot n, there is one PDSCH scheduled and the PDSCH 2 is the first PDSCH. When the UE receives PDSCH 4 associated with HARQ process 3 in slot n+2, the (C-DAI, T-DAI) in the scheduling DCI format indicates (2,3), it means that in HARQ group 2, up to slot n+2, there is three PDSCHs scheduled and the PDSCH 4 is the second PDSCH. When the UE receives PDSCH 5 associated with HARQ process 5 in slot n+2, the (C-DAI, T-DAI) in the scheduling DCI format indicates (3,3), it means that in HARQ group 2, up to slot n+2, there is three PDSCHs scheduled and the PDSCH 5 is the third PDSCH. [0072] To summary, the presented method in some embodiments is to restrict that C_DAI and/or T_DAI are accumulated within a HARQ process group, where the HARQ process group is configured by the network with regards to the HARQ process number. When the UE receives a DCI scheduling a PDSCH, the UE determine the HARQ process group based on the indicated HARQ process number. [0073] Example: Different HARQ-ACK codebooks for different HARQ process groups [0074] In an example, different HARQ-ACK codebooks for different HARQ process groups are provided. In some embodiments, when a PDSCH is scheduled by a DCI format and the PDSCH is associated with a HARQ process number, the DCI format indicates a corresponding PUCCH resource for HARQ-ACK feedback. According to the association between the HARQ process number and a HARQ process group, the UE will transmit a corresponding HARQ-ACK codebook in the PUCCH resource. It is to note that with respect to different HARQ process groups, the corresponding HARQ-ACK codebooks can be different. One example of the HARQ-ACK codebook is following TS 38.213 V16.2.0 section 9.1, which further includes type 1 HARQ-ACK codebook, and/or type 2 HARQ-ACK codebook, and/or type 3 HARQ-ACK codebook, in which explicit HARQ-ACK information (i.e. ACK or NACK) of the scheduled PDSCH is reported. Optionally, another type of codebook does not contain explicit HARQ-ACK information, i.e. ACK or NACK of the scheduled PDSCH. But instead, it contains an information relevant to a ratio of successful decoding of all the PDSCHs within the HARQ process group. One example of this ratio calculation is the following: The ratio is calculated by the number of the successfully decoded PDSCHs over the total transmitted PDSCHs, where the PDSCHs are counted within a given HARQ process group. Optionally, the total number of the PDSCHs in the given HARQ process group is based on T-DAI. Optionally, the ratio can be quantized into M bits, for instance M=2 as illustrated in table 1 or M=0. M can be configured by the network or pre- defined. [0075] Table 1: [0076] From th

e above example, we can see that the codebook has a constant codebook size, where the size can be configured by the network or pre-defined. In what follows we call this codebook as type 4 HARQ-ACK codebook to differentiate it from the previous type 1, type 2, and type 3 codebooks. Optionally, the network can configure a special type 4 HARQ-ACK codebook size, which indicates the UE not to transmit the HARQ-ACK information corresponding to the scheduled PDSCH associated with a given HARQ process group. For example, the network can configure type 4 HARQ- ACK codebook size is zero bit, which means that the UE does not transmit any HARQ-ACK codebook corresponding to the associated HARQ process group. Optionally, the network can configure more than one type 4 codebook sizes, e.g. sizes={0, 2, 4, 8}, and in the scheduling DCI, the network selects the value of the type 4 codebook size. The advantage is that the network can control the UE to report the HARQ-ACK feedback or not by selecting the codebook size being zero or non-zero. Moreover, the network can dynamically adapt the HARQ-ACK feedback overhead, leading to different granularity of the reported ratio. Optionally, codebook sizes are related to T-DAI values. T-DAI values are related to PDSCHs. T-DAI values are related to the PDSCH closest to the PUCCH as illustrated in FIG.11. [0077] Example: HARQ-ACK codebook selection [0078] In some examples, a network can only configure one HARQ process group, and configure a codebook type 1 or type 2 or type 3 or type 4. In this case, all the scheduled PDSCHs are belong to a same HARQ process group and one HARQ- ACK codebook is transmitted in a PUCCH resource. In some examples, a network can configure two HARQ process groups (group 1 and group 2), and configures a type of HARQ-ACK codebook (e.g. type 1 or type 2 or type 3) for the PDSCHs scheduled in HARQ process group 1 and configures a different type of codebook, e.g. type 4 for the PDSCH scheduled in HARQ process group 2. [0079] FIG. 12 illustrates a method of HARQ feedback for an NTN system according to another embodiment of the present disclosure. As an example of FIG.12, where PDSCH 1 is scheduled associated with HARQ process group 1 and its corresponding HARQ-ACK information is generated based on type 1 or type 2 or type 3 codebook and is transmitted in PUCCH1; while PSDCH 2 is scheduled associated with HARQ process group 2, and its corresponding HARQ-ACK information is generated based on type 4 codebook and is transmitted in PUCCH2. [0080] FIG. 13 illustrates a method of HARQ feedback for an NTN system according to another embodiment of the present disclosure. In some examples, if the HARQ-ACK feedback of HARQ-ACK group 1 and group 2 are allocated in a same slot, as illustrated in FIG.13, the UE will transmit a concatenated codebook, which appends the HARQ-ACK codebook of the HARQ process group 2 (type 4 in our example) after the HARQ-ACK codebook of the HARQ process group 1 (type 1 or type 2 or type 3 in our example). Optionally, the UE should prioritize the HARQ-ACK codebook of one HARQ process group, e.g. the UE transmits only the HARQ-ACK codebook of the HARQ process group 1 and drops the HARQ-ACK codebook of the HARQ process group 2. Note that which HARQ process group is prioritized can be configured by the network or pre-defined. [0081] In some examples, when type 1 HARQ-ACK codebook is configured for one HARQ process group, e.g. group 1, and type 4 HARQ-ACK codebook is configured for the other HARQ process group, e.g. group 2, due to the semi-static configured type 1 HARQ-ACK codebook size, it will also contain a bit location for one or more scheduled PDSCHs belong to the HARQ-ACK group 2. In this case, the UE will only set NACK for the bit locations corresponding to the PDSCH associated with the other HARQ process group (group 2 in our example), and the UE will set a valid ACK or NACK information for the PDSCHs belong to the HARQ process group 1. Optionally, the network can configure if the UE sets NACK or sets a valid ACK/NACK information for the one or more PDSCHs of the other HARQ process group. [0082] Optionally, when type 1 HARQ-ACK codebook is configured for HARQ process group 1 and type 4 HARQ- ACK codebook is configured for the HARQ process group 2, if the UE receives only a first PDSCH associated with the HARQ process group 1 but receives one or more PDSCHs associated with the HARQ process group 2 within a whole PDSCH reception window according to TS 38.213 V16.2.0 section 9.1, and/or the first PDSCH is scheduled by a DCI with DCI format 1_0 and/or the DCI format 1_0 indicating a counter DAI field value of 1 on a PCell, and/or the first PDSCH is SPS PDSCH, the UE only reports an HARQ-ACK information of the first PDSCH in the corresponding PUCCH resource. [0083] Optionally, when type 1 HARQ-ACK codebook is configured for HARQ process group 1 and type 4 HARQ- ACK codebook is configured for the HARQ process group 2, if the UE receives only a SPS PDSCH release indicated by DCI format 1_0 with counter DAI field value of 1 on the PCell but receives one or more PDSCH associated with the HARQ process group 2 within a whole PDSCH reception window according to TS 38.213 V16.2.0 section 9.1, the UE only reports an HARQ-ACK information of the SPS PDSCH release in the corresponding PUCCH resource. [0084] In some examples, when type 3 HARQ-ACK codebook is configured for HARQ process group 1 and type 4 HARQ-ACK codebook is configured for the HARQ process group 2, the type 3 HARQ-ACK codebook only includes the HARQ-ACK information of the HARQ process associated with the HARQ process group 1. As an example of FIG.8, the type 3 HARQ-ACK codebook only contains HARQ-ACK information corresponding to HARQ processes 0, 1 and 2. Optionally, type 3 HARQ-ACK codebook includes HARQ-ACK information corresponding to all the configured HARQ processes, i.e. 16 HARQ processes as an example of FIG.8, where the selection of whether or not to include the HARQ- information for all the HARQ processes can depend on at least one of the followings: network configuration, or DCI indication, or PUCCH resource allocated for different HARQ process groups. [0085] Commercial interests for some embodiments are as follows. 1. Solving issues in the prior art. 2. Increasing a transmission throughput that can resolve a bottleneck due to a long round trip time. 3. Providing a good communication performance. 4. Providing a high reliability. 5. Some embodiments of the present disclosure are used by 5G-NR chipset vendors, V2X communication system development vendors, automakers including cars, trains, trucks, buses, bicycles, moto- bikes, helmets, and etc., drones (unmanned aerial vehicles), smartphone makers, communication devices for public safety use, AR/VR device maker for example gaming, conference/seminar, education purposes. Some embodiments of the present disclosure are a combination of “techniques/processes” that can be adopted in 3GPP specification to create an end product. Some embodiments of the present disclosure could be adopted in the 5G NR unlicensed band communications. Some embodiments of the present disclosure propose technical mechanisms. [0086] FIG.14 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and/or software. FIG. 14 illustrates the system 700 including a radio frequency (RF) circuitry 710, a baseband circuitry 720, an application circuitry 730, a memory/storage 740, a display 750, a camera 760, a sensor 770, and an input/output (I/O) interface 780, coupled with each other at least as illustrated. The application circuitry 730 may include a circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and dedicated processors, such as graphics processors, application processors. The processors may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system. [0087] The baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi- core processors. The processors may include a baseband processor. The baseband circuitry may handle various radio control functions that enables communication with one or more radio networks via the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry. [0088] In various embodiments, the baseband circuitry 720 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency. The RF circuitry 710 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In various embodiments, the RF circuitry 710 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency. [0089] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitry, the baseband circuitry, and/or the application circuitry. As used herein, “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, the application circuitry, and/or the memory/storage may be implemented together on a system on a chip (SOC). The memory/storage 740 may be used to load and store data and/or instructions, for example, for system. The memory/storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM)), and/or non-volatile memory, such as flash memory. [0090] In various embodiments, the I/O interface 780 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface. In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite. [0091] In various embodiments, the display 750 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, a AR/VR glasses, etc. In various embodiments, system may have more or less components, and/or different architectures. Where appropriate, methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium. [0092] A person having ordinary skill in the art understands that each of the units, algorithm, and steps described and disclosed in the embodiments of the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the condition of application and design requirement for a technical plan. A person having ordinary skill in the art can use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he/she can refer to the working processes of the system, device, and unit in the above-mentioned embodiment since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed. [0093] It is understood that the disclosed system, device, and method in the embodiments of the present disclosure can be realized with other ways. The above-mentioned embodiments are exemplary only. The division of the units is merely based on logical functions while other divisions exist in realization. It is possible that a plurality of units or components are combined or integrated in another system. It is also possible that some characteristics are omitted or skipped. On the other hand, the displayed or discussed mutual coupling, direct coupling, or communicative coupling operate through some ports, devices, or units whether indirectly or communicatively by ways of electrical, mechanical, or other kinds of forms. [0094] The units as separating components for explanation are or are not physically separated. The units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments. Moreover, each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units. [0095] If the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product. Or, one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other kinds of media capable of storing program codes. [0096] While the present disclosure has been described in connection with what is considered the most practical and preferred embodiments, it is understood that the present disclosure is not limited to the disclosed embodiments but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

What is claimed is: 1. A method of communication of a user equipment (UE), comprising: receiving, by the UE, a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot from a base station^^and transmitting, by the UE, a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission occasion to the base station, wherein the first HARQ-ACK codebook is relevant to the first HARQ process.

2. The method of claim 1, wherein the first PDSCH is scheduled by a first downlink control information (DCI) format.

3. The method of claim 1, wherein the first PDSCH is configured by the base station.

4. The method of claim 3, wherein the first PDSCH comprises semi-persistent scheduling (SPS)-PDSCH.

5. The method of any one of claims 1 to 4, wherein the first DCI format comprises a first indication field, wherein the first HARQ process is indicated at least by the first indication field.

6. The method of any one of claims 1 to 5, wherein the first DCI format comprises a second indication field, wherein the second indication field indicates the first PUCCH transmission occasion.

7. The method of claim 6, wherein the second indication field indicates the first PUCCH transmission occasion in the first slot or the first sub-slot.

8. The method of claim 6 or 7, wherein the second indication field comprises PDSCH-to-HARQ_feedback timing indicator field.

9. The method of any one of claims 1 to 8, wherein the first HARQ process is configured by a base station to be associated with a first HARQ process group or a first HARQ process type or a first HARQ process function or a first HARQ process status.

10. The method of claim 9, wherein the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status comprises at least one of the followings: HARQ feedback enabled or HARQ feedback disabled.

11. The method of claim 9 or 10, wherein a first RRC parameter for the first HARQ process is configured by the base station, and the first RRC parameter indicates HARQ feedback enabled or HARQ feedback disabled.

12. The method of claim 11, wherein when the first RRC parameter is absent for the first HARQ process, the first HARQ process is associated with a default HARQ process group or a default HARQ process type or a default HARQ process function or a default HARQ process status.

13. The method of any one of claims 9 to 12, wherein the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status is associated with one or more HARQ processes.

14. The method of any one of claims 1 to 13, wherein the first DCI format comprises a third indication field, wherein the third indication field comprises a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI).

15. The method of claim 14, wherein the C-DAI is counted within the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

16. The method of claim 14 or 15, wherein the C-DAI denotes that an accumulative number of {serving cell, physical downlink control channel (PDCCH) monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release, associated with one or more HARQ processes that are associated with the first HARQ process type or the first HARQ process function or the first HARQ process status, is present up to a current serving cell and a current PDCCH monitoring occasion.

17. The method of any one of claims 14 to 16, wherein the T-DAI is counted within the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

18. The method of any one of claims 14 to 17, wherein the T-DAI denotes a total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release associated with one or more HARQ processes that are associated with the first HARQ process type or the first HARQ process function or the first HARQ process status, up to a current PDCCH monitoring occasion.

19. The method of any one of claims 1 to 18, wherein the first DCI format comprises: DCI format 1_0 and/or DCI format 1_1 and/or DCI format 1_2 and/or DCI format 1_3.

20. The method of any one of claims 1 to 19, wherein the first HARQ-ACK codebook comprises at least one of the followings: a type 1 HARQ-ACK codebook, a type 2 HARQ-ACK codebook, a type 3 HARQ-ACK codebook, or a type 4 HARQ-ACK codebook.

21. The method of claim 20, wherein the type 1 HARQ-ACK codebook contains a constant number of bits, which further comprises a first one or more bits and/or a second one or more bits.

22. The method of claim 21, wherein the first one or more bits comprise one or more HARQ-ACK information corresponding to a first set of one or more received PDSCHs associated with one or more HARQ processes that are of the first HARQ process group, or the first HARQ process type or the first HARQ process function or the first HARQ process status, wherein the first set of one or more received PDSCHs comprise the first PDSCH.

23. The method of claim 22, wherein the first set of one or more received PDSCHs are assigned by the second indication field for a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

24. The method of any one of claims 21 to 23, wherein the second one or more bits comprise one or more invalid HARQ- ACK information corresponding to a second set of one or more received PDSCHs associated with one or more HARQ processes that are of a second HARQ process group or a second HARQ process type or a second HARQ process function or a second HARQ process status.

25. The method of any one of claims 21 to 23, wherein the second one or more bits comprise one or more HARQ-ACK information corresponding to a second set of one or more received PDSCHs associated with one or more HARQ processes that are of a second HARQ process group or a second HARQ process type or a second HARQ process function or a second HARQ process status.

26. The method of claim 24 or 25, wherein the second set of one or more received PDSCHs are assigned by the second indication field for a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

27. The method of claim 24 or 25, wherein invalid HARQ-ACK information comprises HARQ-ACK value equal to negative acknowledgement (NACK).

28. The method of any one of claims 21 to 27, wherein when the first set of one or more PDSCHs only contain the first PDSCH, the UE only reports the HARQ-ACK information corresponding to the first PDSCH in the first PUCCH transmission occasion.

29. The method of claim 28, wherein the C-DAI indicated by the first DCI format is equal to 1.

30. The method of any one of claims 20 to 29, wherein the type 2 HARQ-ACK codebook comprises a codebook size relevant to a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

31. The method of claim 30, wherein the last received PDSCH is associated with a HARQ process of the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

32. The method of any one of claims 20 to 31, wherein the type 3 HARQ-ACK codebook comprises a number of HARQ- ACK bits which is relevant to a number of configured HARQ processes for a serving cell.

33. The method of any one of claims 20 to 31, wherein the type 3 HARQ-ACK codebook comprises a number of HARQ- ACK bits which is relevant to a number of configured HARQ processes associated with the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status for a serving cell.

34. The method of claim 32, further comprising reporting, by the UE, NACK corresponding to one or more HARQ processes associated with the second HARQ process group or the second HARQ process type or the second HARQ process function or the second HARQ process status.

35. The method of any one of claims 20 to 34, wherein the type 4 HARQ-ACK codebook does not contain an HARQ-ACK information for the first PDSCH.

36. The method of any one of claims 20 to 35, wherein the type 4 HARQ-ACK codebook comprises an information relevant to a decoding outcome of one or more PDSCHs associated with the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

37. The method of claim 36, wherein the decoding outcome comprises at least one of the followings: a ratio between a Number of successfully decoded PDSCHs and a total number of PDSCHs; or a number of successfully decoded PDSCHs.

38. The method of claim 37, wherein the total number of PDSCHs is indicated by a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

39. The method of any one of claims 20 to 38, wherein the type 4 HARQ-ACK codebook comprises an amount of bits, wherein the amount is determined at least by one of the followings: configured by the base station, or indicated in the first DCI format, or by a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

40. The method of any one of claims 1 to 39, wherein the first codebook is configured by a base station to be associated with the first HARQ process or a first HARQ process group or a first HARQ process type or a first HARQ process function or a first HARQ process status.

41. The method of any one of claims 1 to 40, further comprising receiving, by the UE, a second PDSCH associated with a second HARQ process, wherein the UE is assigned to report a second HARQ-ACK codebook in the first slot or the first sub-slot;and transmitting, by the UE, the first HARQ-ACK codebook in the first PUCCH transmission occasion.

42. The method of any one of claims 1 to 40, further comprising receiving, by the UE, a second PDSCH associated with a second HARQ process, and an indication indicating a PUCCH transmission occasion in the first slot or the first sub-slot; and transmitting, by the UE, a second HARQ-ACK codebook in the first PUCCH transmission occasion, wherein the second HARQ process is associated with a second HARQ process group or a second process type or a second process function or a second process status.

43. The method of claim 42, wherein the second HARQ process codebook is configured by the base station to be associated with the second HARQ process.

44. The method of claim 42 or 43, wherein the second HARQ process codebook is configured by the base station to be associated with the second HARQ process group or the second process type or the second process function or the second process status.

45. The method of any one of claims 42 to 44, wherein the second HARQ-ACK codebook is appended after the first HARQ- ACK codebook.

46. The method of any one of claims 41 to 45, wherein the second HARQ-ACK codebook comprises at least one of the followings: the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, the type 3 HARQ-ACK codebook, or the type 4 HARQ-ACK codebook.

47. The method of any one of claims 42 to 46, wherein the second HARQ process group or the second process type or the second process function or the second process status comprises HARQ enabling or HARQ disabling.

48. A user equipment (UE) of communication, comprising: a memory; a tranceiver, and a processor coupled to the memory and the transceiver; wherein the transceiver is configured to: receive a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot from a base station; and transmit a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission occasion to the base station, wherein the first HARQ-ACK codebook is relevant to the first HARQ process.

49. The UE of claim 48, wherein the first PDSCH is scheduled by a first downlink control information (DCI) format.

50. The UE of claim 48, wherein the first PDSCH is configured by the base station.

51. The UE of claim 50, wherein the first PDSCH comprises semi-persistent scheduling (SPS)-PDSCH.

52. The UE of any one of claims 48 to 51, wherein the first DCI format comprises a first indication field, wherein the first HARQ process is indicated at least by the first indication field.

53. The UE of any one of claims 48 to 52, wherein the first t DCI format comprises a second indication field, wherein the second indication field indicates the first PUCCH transmission occasion.

54. The UE of claim 53, wherein the second indication field indicates the first PUCCH transmission occasion in the first slot or the first sub-slot.

55. The UE of claim 53 or 54, wherein the second indication field comprises PDSCH-to-HARQ_feedback timing indicator field.

56. The UE of any one of claims 48 to 55, wherein the first HARQ process is configured by a base station to be associated with a first HARQ process group or a first HARQ process type or a first HARQ process function or a first HARQ process status.

57. The UE of claim 56, wherein the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status comprises at least one of the followings: HARQ feedback enabled or HARQ feedback disabled.

58. The UE of claim 56 or 57, wherein a first RRC parameter for the first HARQ process is configured by the base station, and the first RRC parameter indicates HARQ feedback enabled or HARQ feedback disabled.

59. The UE of claim 58, wherein when the first RRC parameter is absent for the first HARQ process, the first HARQ process is associated with a default HARQ process group or a default HARQ process type or a default HARQ process function or a default HARQ process status.

60. The UE of any one of claims 56 to 59, wherein the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status is associated with one or more HARQ processes.

61. The UE of any one of claims 48 to 60, wherein the first DCI format comprises a third indication field, wherein the third indication field comprises a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI).

62. The UE of claim 61, wherein the C-DAI is counted within the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

63. The UE of claim 61 or 62, wherein the C-DAI denotes that an accumulative number of {serving cell, physical downlink control channel (PDCCH) monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release, associated with one or more HARQ processes that are associated with the first HARQ process type or the first HARQ process function or the first HARQ process status, is present up to a current serving cell and a current PDCCH monitoring occasion.

64. The UE of any one of claims 61 to 63, wherein the T-DAI is counted within the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

65. The UE of any one of claims 61 to 64, wherein the T-DAI denotes a total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release associated with one or more HARQ processes that are associated with the first HARQ process type or the first HARQ process function or the first HARQ process status, up to a current PDCCH monitoring occasion.

66. The UE of any one of claims 48 to 65, wherein the first DCI format comprises: DCI format 1_0 and/or DCI format 1_1 and/or DCI format 1_2 and/or DCI format 1_3.

67. The UE of any one of claims 48 to 66, wherein the first HARQ-ACK codebook comprises at least one of the followings: a type 1 HARQ-ACK codebook, a type 2 HARQ-ACK codebook, a type 3 HARQ-ACK codebook, or a type 4 HARQ-ACK codebook.

68. The UE of claim 67, wherein the type 1 HARQ-ACK codebook contains a constant number of bits, which further comprises a first one or more bits and/or a second one or more bits.

69. The UE of claim 67, wherein the first one or more bits comprise one or more HARQ-ACK information corresponding to a first set of one or more received PDSCHs associated with one or more HARQ processes that are of the first HARQ process group, or the first HARQ process type or the first HARQ process function or the first HARQ process status, wherein the first set of one or more received PDSCHs comprise the first PDSCH.

70. The UE of claim 69, wherein the first set of one or more received PDSCHs are assigned by the second indication field for a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

71. The UE of any one of claims 68 to 70, wherein the second one or more bits comprise one or more invalid HARQ-ACK information corresponding to a second set of one or more received PDSCHs associated with one or more HARQ processes that are of a second HARQ process group or a second HARQ process type or a second HARQ process function or a second HARQ process status.

72. The UE of any one of claims 68 to 70, wherein the second one or more bits comprise one or more HARQ-ACK information corresponding to a second set of one or more received PDSCHs associated with one or more HARQ processes that are of a second HARQ process group or a second HARQ process type or a second HARQ process function or a second HARQ process status.

73. The UE of claim 71 or 72, wherein the second set of one or more received PDSCHs are assigned by the second indication field for a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

74. The UE of claim 71 or 72, wherein invalid HARQ-ACK information comprises HARQ-ACK value equal to negative acknowledgement (NACK).

75. The UE of any one of claims 68 to 74, wherein when the first set of one or more PDSCHs only contain the first PDSCH, the UE only reports the HARQ-ACK information corresponding to the first PDSCH in the first PUCCH transmission occasion.

76. The UE of claim 75, wherein the C-DAI indicated by the first DCI format is equal to 1.

77. The UE of any one of claims 67 to 76, wherein the type 2 HARQ-ACK codebook comprises a codebook size relevant to a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

78. The UE of claim 77, wherein the last received PDSCH is associated with a HARQ process of the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

79. The UE of any one of claims 67 to 78, wherein the type 3 HARQ-ACK codebook comprises a number of HARQ-ACK bits which is relevant to a number of configured HARQ processes for a serving cell.

80. The UE of any one of claims 67 to 78, wherein the type 3 HARQ-ACK codebook comprises a number of HARQ-ACK bits which is relevant to a number of configured HARQ processes associated with the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status for a serving cell.

81. The UE of claim 79, wherein the transceiver is configured to report NACK corresponding to one or more HARQ processes associated with the second HARQ process group or the second HARQ process type or the second HARQ process function or the second HARQ process status.

82. The UE of any one of claims 67 to 82, wherein the type 4 HARQ-ACK codebook does not contain an HARQ-ACK information for the first PDSCH.

83. The UE of any one of claims 67 to 82, wherein the type 4 HARQ-ACK codebook comprises an information relevant to a decoding outcome of one or more PDSCHs associated with the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

84. The UE of claim 83, wherein the decoding outcome comprises at least one of the followings: a ratio between a number of successfully decode PDSCHs and a total number of PDSCHs; or a number of successfully decoded PDSCHs .

85. The UE of claim 84, wherein the total number of PDSCHs is indicated by a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

86. The UE of any one of claims 67 to 85, wherein the type 4 HARQ-ACK codebook comprises an amount of bits, wherein the amount is determined at least by one of the followings: configured by the base station, or indicated in the first DCI format, or by a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

87. The UE of any one of claims 48 to 86, wherein the first codebook is configured by a base station to be associated with the first HARQ process or a first HARQ process group or a first HARQ process type or a first HARQ process function or a first HARQ process status.

88. The UE of any one of claims 48 to 87, wherein the transceiver is configured to receive a second PDSCH associated with a second HARQ process, the transceiver is assigned to report a second HARQ-ACK codebook in the first slot or the first sub-slot; and the transceiver is configured to transmit the first HARQ-ACK codebook in the first PUCCH transmission occasion.

89. The UE of any one of claims 48 to 87, wherein the transceiver is configured to receive a second PDSCH associated with a second HARQ process and an indication indicating a PUCCH transmission occasion in the first slot or the first sub-slot; and the transceiver is configured to transmit a second HARQ-ACK codebook in the first PUCCH transmission occasion, wherein the second HARQ process is associated with a second HARQ process group or a second process type or a second process function or a second process status.

90. The UE of claim 89, wherein the second HARQ process codebook is configured by the base station to be associated with the second HARQ process.

91. The UE of claim 89 or 90, wherein the second HARQ process codebook is configured by the base station to be associated with the second HARQ process group or the second process type or the second process function or the second process status.

92. The UE of any one of claims 89 to 91, wherein the second HARQ-ACK codebook is appended after the first HARQ- ACK codebook.

93. The UE of any one of claims 88 to 92, wherein the second HARQ-ACK codebook comprises at least one of the followings: the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, the type 3 HARQ-ACK codebook, or the type 4 HARQ-ACK codebook.

94. The UE of any one of claims 89 to 93, wherein the second HARQ process group or the second process type or the second process function or the second process status comprises HARQ enabling or HARQ disabling.

95. A method of communication of a base station, comprising: configuring, by the base station, a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot to a user equipment (UE); and receiving, by the base station, a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission occasion from the UE, wherein the first HARQ-ACK codebook is relevant to the first HARQ process.

96. The method of claim 95, wherein the first PDSCH is scheduled by a first downlink control information (DCI) format.

97. The method of claim 95, wherein the first PDSCH is configured by the base station.

98. The method of claim 97, wherein the first PDSCH comprises semi-persistent scheduling (SPS)-PDSCH.

99. The method of any one of claims 95 to 98, wherein the first DCI format comprises a first indication field, wherein the first HARQ process is indicated at least by the first indication field.

100. The method of any one of claims 95 to 99, wherein the DCI format comprises a second indication field, wherein the second indication field indicates the first PUCCH transmission occasion.

101. The method of claim 100, wherein the second indication field indicates the first PUCCH transmission occasion in the first slot or the first sub-slot.

102. The method of claim 100 or 101, wherein the second indication field comprises PDSCH-to-HARQ_feedback timing indicator field.

103. The method of any one of claims 95 to 102, wherein the first HARQ process is configured by the base station to be associated with a first HARQ process group or a first HARQ process type or a first HARQ process function or a first HARQ process status.

104. The method of claim 103, wherein the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status comprises at least one of the followings: HARQ feedback enabled or HARQ feedback disabled.

105. The method of claim 103 or 104, wherein a first RRC parameter for the first HARQ process is configured by the base station, and the first RRC parameter indicates HARQ feedback enabled or HARQ feedback disabled.

106. The method of claim 105, wherein when the first RRC parameter is absent for the first HARQ process, the first HARQ process is associated with a default HARQ process group or a default HARQ process type or a default HARQ process function or a default HARQ process status.

107. The method of any one of claims 103 to 106, wherein the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status is associated with one or more HARQ processes.

108. The method of any one of claims 95 to 107, wherein the first DCI format comprises a third indication field, wherein the third indication field comprises a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI).

109. The method of claim 108, wherein the C-DAI is counted within the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

110. The method of claim 108 or 109, wherein the C-DAI denotes that an accumulative number of {serving cell, physical downlink control channel (PDCCH) monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release, associated with one or more HARQ processes that are associated with the first HARQ process type or the first HARQ process function or the first HARQ process status, is present up to a current serving cell and a current PDCCH monitoring occasion.

111. The method of any one of claims 108 to 110, wherein the T-DAI is counted within the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

112. The method of any one of claims 108 to 111, wherein the T-DAI denotes a total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release associated with one or more HARQ processes that are associated with the first HARQ process type or the first HARQ process function or the first HARQ process status, up to a current PDCCH monitoring occasion.

113. The method of any one of claims 95 to 112, wherein the first DCI format comprises: DCI format 1_0 and/or DCI format 1_1 and/or DCI format 1_2 and/or DCI format 1_3.

114. The method of any one of claims 95 to 113, wherein the first HARQ-ACK codebook comprises at least one of the followings: a type 1 HARQ-ACK codebook, a type 2 HARQ-ACK codebook, a type 3 HARQ-ACK codebook, or a type 4 HARQ-ACK codebook.

115. The method of claim 114, wherein the type 1 HARQ-ACK codebook contains a constant number of bits, which further comprises a first one or more bits and/or a second one or more bits.

116. The method of claim 115, wherein the first one or more bits comprise one or more HARQ-ACK information corresponding to a first set of one or more configured PDSCHs associated with one or more HARQ processes that are of the first HARQ process group, or the first HARQ process type or the first HARQ process function or the first HARQ process status, wherein the first set of one or more configured PDSCHs comprise the first PDSCH.

117. The method of claim 116, wherein the first set of one or more configured PDSCHs are assigned by the second indication field for a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

118. The method of any one of claims 115 to 117, wherein the second one or more bits comprise one or more invalid HARQ- ACK information corresponding to a second set of one or more configured PDSCHs associated with one or more HARQ processes that are of a second HARQ process group or a second HARQ process type or a second HARQ process function or a second HARQ process status.

119. The method of any one of claims 115 to 117, wherein the second one or more bits comprise one or more HARQ-ACK information corresponding to a second set of one or more configured PDSCHs associated with one or more HARQ processes that are of a second HARQ process group or a second HARQ process type or a second HARQ process function or a second HARQ process status.

120. The method of claim 118 or 119, wherein the second set of one or more configured PDSCHs are assigned by the second indication field for a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

121. The method of claim 118 or 119, wherein invalid HARQ-ACK information comprises HARQ-ACK value equal to negative acknowledgement (NACK).

122. The method of any one of claims 115 to 121, wherein when the first set of one or more PDSCHs only contain the first PDSCH, the UE only reports the HARQ-ACK information corresponding to the first PDSCH in the first PUCCH transmission occasion.

123. The method of claim 122, wherein the C-DAI indicated by the first DCI format is equal to 1.

124. The method of any one of claims 114 to 123, wherein the type 2 HARQ-ACK codebook comprises a codebook size relevant to a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

125. The method of claim 124, wherein the last configured PDSCH is associated with a HARQ process of the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

126. The method of any one of claims 114 to 125, wherein the type 3 HARQ-ACK codebook comprises a number of HARQ- ACK bits which is relevant to a number of configured HARQ processes for a serving cell.

127. The method of any one of claims 114 to 125, wherein the type 3 HARQ-ACK codebook comprises a number of HARQ- ACK bits which is relevant to a number of configured HARQ processes associated with the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status for a serving cell.

128. The method of claim 126, further comprising receiving, by the base station, NACK corresponding to one or more HARQ processes associated with the second HARQ process group or the second HARQ process type or the second HARQ process function or the second HARQ process status.

129. The method of any one of claims 114 to 128, wherein the type 4 HARQ-ACK codebook does not contain an HARQ- ACK information for the first PDSCH.

130. The method of any one of claims 114 to 129, wherein the type 4 HARQ-ACK codebook comprises an information relevant to a decoding outcome of one or more PDSCHs associated with the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

131. The method of claim 130, wherein the decoding outcome comprises at least one of the followings: a ratio between a number of successfully decoded PDSCHs and a total number of PDSCHs; or a number of successfully decoded PDSCHs.

132. The method of claim 131, wherein the total number of PDSCHs is indicated by a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

133. The method of any one of claims 114 to 132, wherein the type 4 HARQ-ACK codebook comprises an amount of bits, wherein the amount is determined at least by one of the followings: configured by the base station, or indicated in the first DCI format, or by a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

134. The method of any one of claims 95 to 133, wherein the first codebook is configured by the base station to be associated with the first HARQ process or a first HARQ process group or a first HARQ process type or a first HARQ process function or a first HARQ process status.

135. The method of any one of claims 95 to 134, further comprising transmitting, by the base station, a second PDSCH associated with a second HARQ process, wherein the base station assigns a UE to report a second HARQ-ACK codebook in the first slot or the first sub-slot; and receiving, by the base station, the first HARQ-ACK codebook in the first PUCCH transmission occasion.

136. The method of any one of claims 95 to 134, further comprising transmitting, by the base station, a second PDSCH associated with a second HARQ process and an indication indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot; and receiving, by the base station, a second HARQ-ACK codebook in the first PUCCH transmission occasion, wherein the second HARQ process is associated with a second HARQ process group or a second process type or a second process function or a second process status.

137. The method of claim 136, wherein the second HARQ process codebook is configured by the base station to be associated with the second HARQ process.

138. The method of claim 136 or 137, wherein the second HARQ process codebook is configured by the base station to be associated with the second HARQ process group or the second process type or the second process function or the second process status.

139. The method of any one of claims 136 to 138, wherein the second HARQ-ACK codebook is appended after the first HARQ-ACK codebook.

140. The method of any one of claims 135 to 139, wherein the second HARQ-ACK codebook comprises at least one of the followings: the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, the type 3 HARQ-ACK codebook, or the type 4 HARQ-ACK codebook.

141. The method of any one of claims 136 to 140, wherein the second HARQ process group or the second process type or the second process function or the second process status comprises HARQ enabling or HARQ disabling.

142. A base station of communication, comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the processor is configured to configure a first physical downlink shared channel (PDSCH) associated with a first hybrid automatic repeat request (HARQ) process and an indication indicating a first physical uplink control channel (PUCCH) transmission occasion corresponding to the first PDSCH in a first slot or a first sub-slot to a user equipment (UE); and wherein the transceiver is configured to receive a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in the first PUCCH transmission from the UE, wherein the first HARQ-ACK codebook is relevant to the first HARQ process.

143. The base station of claim 142, wherein the first PDSCH is scheduled by a first downlink control information (DCI) format.

144. The base station of claim 142, wherein the first PDSCH is configured by the base station.

145. The base station of claim 144, wherein the first PDSCH comprises semi-persistent scheduling (SPS)-PDSCH.

146. The base station of any one of claims 142 to 145, wherein the first DCI format comprises a first indication field, wherein the first HARQ process is indicated at least by the first indication field.

147. The base station of any one of claims 142 to 146, wherein the first DCI format comprises a second indication field, wherein the second indication field indicates the first PUCCH transmission occasion.

148. The base station of claim 146 or 147, wherein the second indication field indicates the first PUCCH transmission occasion in the first slot or the first sub-slot. slot or the first sub-slot is indicated by the first DCI format with a second indication field.

149. The base station of claim 147, wherein the second indication field comprises PDSCH-to-HARQ_feedback timing indicator field.

150. The base station of any one of claims 142 to 149, wherein the first HARQ process is configured by the base station to be associated with a first HARQ process group or a first HARQ process type or a first HARQ process function or a first HARQ process status.

151. The base station of claim 150, wherein the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status comprises at least one of the followings: HARQ feedback enabled or HARQ feedback disabled.

152. The base station of claim 150 or 151, wherein a first RRC parameter for the first HARQ process is configured by the base station, and the first RRC parameter indicates HARQ feedback enabled or HARQ feedback disabled.

153. The base station of claim 152, wherein when the first RRC parameter is absent for the first HARQ process, the first HARQ process is associated with a default HARQ process group or a default HARQ process type or a default HARQ process function or a default HARQ process status.

154. The base station of any one of claims 150 to 153, wherein the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status is associated with one or more HARQ processes.

155. The base station of any one of claims 142 to 154, wherein the first DCI format comprises a third indication field, wherein the third indication field comprises a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI).

156. The base station of claim 155, wherein the C-DAI is counted within the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

157. The base station of claim 155 or 156, wherein the C-DAI denotes that an accumulative number of {serving cell, physical downlink control channel (PDCCH) monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release, associated with one or more HARQ processes that are associated with the first HARQ process type or the first HARQ process function or the first HARQ process status, is present up to a current serving cell and a current PDCCH monitoring occasion.

158. The base station of any one of claims 155 to 157, wherein the T-DAI is counted within the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

159. The base station of any one of claims 155 to 158, wherein the T-DAI denotes a total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release associated with one or more HARQ processes that are associated with the first HARQ process type or the first HARQ process function or the first HARQ process status, up to a current PDCCH monitoring occasion.

160. The base station of any one of claims 142 to 159, wherein the first DCI format comprises: DCI format 1_0 and/or DCI format 1_1 and/or DCI format 1_2 and/or DCI format 1_3.

161. The base station of any one of claims 142 to 160, wherein the first HARQ-ACK codebook comprises at least one of the followings: a type 1 HARQ-ACK codebook, a type 2 HARQ-ACK codebook, a type 3 HARQ-ACK codebook, or a type 4 HARQ-ACK codebook.

162. The base station of claim 161, wherein the type 1 HARQ-ACK codebook contains a constant number of bits, which further comprises a first one or more bits and/or a second one or more bits.

163. The base station of claim 162, wherein the first one or more bits comprise one or more HARQ-ACK information corresponding to a first set of one or more configured PDSCHs associated with one or more HARQ processes that are of the first HARQ process group, or the first HARQ process type or the first HARQ process function or the first HARQ process status, wherein the first set of one or more configured PDSCHs comprise the first PDSCH.

164. The base station of claim 163, wherein the first set of one or more configured PDSCHs are assigned by the second indication field for a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

165. The base station of any one of claims 162 to 164, wherein the second one or more bits comprise one or more invalid HARQ-ACK information corresponding to a second set of one or more configured PDSCHs associated with one or more HARQ processes that are of a second HARQ process group or a second HARQ process type or a second HARQ process function or a second HARQ process status.

166. The base station of any one of claims 162 to 164, wherein the second one or more bits comprise one or more HARQ- ACK information corresponding to a second set of one or more configured PDSCHs associated with one or more HARQ processes that are of a second HARQ process group or a second HARQ process type or a second HARQ process function or a second HARQ process status.

167. The base station of claim 165 or 166, wherein the second set of one or more configured PDSCHs are assigned by the second indication field for a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

168. The base station of claim 165 or 166, wherein invalid HARQ-ACK information comprises HARQ-ACK value equal to negative acknowledgement (NACK).

169. The base station of any one of claims 162 to 168, wherein when the first set of one or more PDSCHs only contain the first PDSCH, the UE only reports the HARQ-ACK information corresponding to the first PDSCH in the first PUCCH transmission occasion.

170. The base station of claim 169, wherein the C-DAI indicated by the first DCI format is equal to 1.

171. The base station of any one of claims 161 to 170, wherein the type 2 HARQ-ACK codebook comprises a codebook size relevant to a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

172. The base station of claim 171, wherein the last configured PDSCH is associated with a HARQ process of the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

173. The base station of any one of claims 161 to 172, wherein the type 3 HARQ-ACK codebook comprises a number of HARQ-ACK bits which is relevant to a number of configured HARQ processes for a serving cell.

174. The base station of any one of claims 161 to 172, wherein the type 3 HARQ-ACK codebook comprises a number of HARQ-ACK bits which is relevant to a number of configured HARQ processes associated with the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status for a serving cell.

175. The base station of claim 173, wherein the transceiver is configured to receive NACK corresponding to one or more HARQ processes associated with the second HARQ process group or the second HARQ process type or the second HARQ process function or the second HARQ process status.

176. The base station of any one of claims 161 to 175, wherein the type 4 HARQ-ACK codebook does not contain an HARQ-ACK information for the first PDSCH.

177. The base station of any one of claims 161 to 176, wherein the type 4 HARQ-ACK codebook comprises an information relevant to a decoding outcome of one or more PDSCHs associated with the first HARQ process group or the first HARQ process type or the first HARQ process function or the first HARQ process status.

178. The base station of claim 177, wherein the decoding outcome comprises at least one of the followings: a ratio between number of successfully decoded PDSCHs and a total number of PDSCHs; or a number of successfully decoded PDSCHs.

179. The base station of claim 178, wherein the total number of PDSCHs is indicated by a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

180. The base station of any one of claims 161 to 179, wherein the type 4 HARQ-ACK codebook comprises an amount of bits, wherein the amount is determined at least by one of the followings: configured by the base station, or indicated in the first DCI format, or by a T-DAI value, where the T-DAI value is indicated by the first DCI format that schedules a last PDSCH, indicating a PUCCH transmission occasion in a same slot as the first slot or the first sub-slot.

181. The base station of any one of claims 142 to 180, wherein the first codebook is configured by the base station to be associated with the first HARQ process or a first HARQ process group or a first HARQ process type or a first HARQ process function or a first HARQ process status.

182. The base station of any one of claims 142 to 181, wherein the transceiver is configured to transmit a second PDSCH associated with a second HARQ process, the processor assigns a UE to report a second HARQ-ACK codebook in the first slot or the first sub-slot; and the transceiver is configured to receive the first HARQ-ACK codebook in the first PUCCH transmission occasion.

183. The base station of any one of claims 142 to 181, wherein the transceiver is configured to transmit a second PDSCH associated with a second HARQ process and an indication indicating a PUCCH transmission occasion in the first slot or the first sub-slot; and the transceiver is configured to receive a second HARQ-ACK codebook in the first PUCCH transmission occasion, wherein the second HARQ process is associated with a second HARQ process group or a second process type or a second process function or a second process status.

184. The base station of claim 183, wherein the second HARQ process codebook is configured by the base station to be associated with the second HARQ process.

185. The base station of claim 183 or 185, wherein the second HARQ process codebook is configured by the base station to be associated with the second HARQ process group or the second process type or the second process function or the second process status.

186. The base station of any one of claims 183 to 185, wherein the second HARQ-ACK codebook is appended after the first HARQ-ACK codebook.

187. The base station of any one of claims 182 to 186, wherein the second HARQ-ACK codebook comprises at least one of the followings: the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, the type 3 HARQ-ACK codebook, or the type 4 HARQ-ACK codebook.

188. The base station of any one of claims 183 to 187, wherein the second HARQ process group or the second process type or the second process function or the second process status comprises HARQ enabling or HARQ disabling.

189. A method of communication of a user equipment (UE), comprising: determining, by the UE, that physical downlink shared channels (PDSCHs) are divided into N groups, wherein N is an integer equal to or greater than 1 determining, by the UE, a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ processes are divided into N groups; and determining, by the UE, that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration.

190. The method of claim 189, wherein when N is equal to 1, all the HARQ processes are of the same group, and all the PDSCHs are belong to the same HARQ process group.

191. The method of claim 189, wherein when N is greater than 1, several of the HARQ processes are of different groups, and several of the PDSCHs are belong to different HARQ process groups.

192. The method of any one of claims 189 to 191, further comprising determining downlink control information (DCI) format, wherein the DCI format contains one or more HARQ process numbers to indicate one or more PDSCHs are associated with the one or more HARQ process numbers.

193. The method of claim 192, wherein the DCI format is used to schedule the PDSCHs.

194. The method of claim 192 or 193, wherein a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI) is in the DCI format, and the C-DAI and/or the T-DAI is accumulated within each HARQ process group.

195. The method of any one of claims 192 to 194, wherein the DCI format comprises a DCI format 1_1, a DCI format 1_2, or a DCI format 1_3.

196. The method of any one of claims 192 to 195, wherein when the UE is configured with one serving cell, the DCI format scheduling the PDSCHs does not contain T-DAI.

197. The method of claim 196, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C- DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group.

198. The method of claim 197 or 197, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group; when another several of the PDSCHs are scheduled in another same HARQ process group, C-DAI values corresponding to the another several of the PDSCHs are continuously counted in the another same HARQ process group.

199. The method of any one of claims 192 to 195, wherein when the UE is configured with more than one serving cell, the HARQ process group configuration can be configured per serving cell.

200. The method of claim 199, wherein cross different serving cells, HARQ process group configurations can be different.

201. The method of claim 199, wherein the same HARQ process group configuration can be applied for all the serving cells.

202. The method of any one of claims 199 to 201, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values and T-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group.

203. The method of any one of claims 199 to 202, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values and T-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group; when another several of the PDSCHs are scheduled in another same HARQ process group, C-DAI values and T-DAI values corresponding to the another several of the PDSCHs are continuously counted in the another same HARQ process group.

204. The method of claim 192 or 193, wherein the DCI format indicates a corresponding physical uplink control channel (PUCCH) resource for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.

205. The method of claim 204, further comprising transmitting a corresponding HARQ-ACK codebook in the PUCCH resource according to an association between one or more HARQ process numbers and N HARQ process groups.

206. The method of claim 205, wherein the HARQ-ACK codebook comprises a type 1 HARQ-ACK codebook, a type 2 HARQ-ACK codebook, a type 3 HARQ-ACK codebook, or a type 4 HARQ-ACK codebook.

207. The method of claim 206, wherein in the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, or the type 3 HARQ-ACK codebook, HARQ-ACK information of the PDSCHs are reported.

208. The method of claim 206, wherein the type 4 HARQ-ACK codebook comprises information relevant to a ratio of successful decoding of all the PDSCHs within N HARQ process groups.

209. The method of claim 208, wherein the ratio is calculated by a number of the successfully decoded PDSCHs over total transmitted PDSCHs, where the PDSCHs are counted within a given HARQ process group.

210. The method of claim 208, wherein a total number of the PDSCHs in a given HARQ process group is based on T-DAI.

211. The method of claim 208, wherein the ratio can be quantized into M bits, where M is equal to 0 or an integer equal to or greater than 1.

212. The method of any one of claims 208 to 211, wherein the type 4 HARQ-ACK codebook has a constant codebook size.

213. The method of claim 212, wherein the constant codebook size of the type 4 HARQ-ACK codebook is configured or pre-defined.

214. The method of claim 212 or 213, wherein the constant codebook size of the type 4 HARQ-ACK codebook is zero or non-zero.

215. The method of any one of claims 205 to 214, wherein all the PDSCHs are belong to the same HARQ process group and one HARQ-ACK codebook is transmitted in the PUCCH resource.

216. The method of any one of claims 205 to 214, wherein all the PDSCHs are belong to different HARQ process groups and different HARQ-ACK codebooks are separately transmitted in different PUCCH resources.

217. The method of any one of claims 205 to 214, wherein all the PDSCHs are belong to different HARQ process groups and are allocated in the same slot, different HARQ-ACK codebooks are transmitted in the same PUCCH resource, and the different HARQ-ACK codebooks are concatenated codebooks.

218. The method of any one of claims 206 to 214, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 1 HARQ-ACK codebook is semi-static configured and comprises a bit location for one or more PDSCHs belong to the second HARQ-ACK group, the UE sets NACK for the bit location corresponding to the one or more PDSCHs belong to the second HARQ-ACK group, and/or the UE sets a valid ACK or NACK information for one or more PDSCHs belong to the first HARQ process group.

219. The method of any one of claims 206 to 214, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 1 HARQ-ACK codebook is semi-static configured and comprises a bit location for one or more PDSCHs belong to the second HARQ-ACK group, the UE is configured whether to set NACK for the bit location corresponding to the one or more PDSCHs belong to the second HARQ-ACK group and/or to set a valid ACK or NACK information for one or more PDSCHs belong to the first HARQ process group.

220. The method of any one of claims 206 to 214, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, if the UE receives a first PDSCH associated with the first HARQ process group and receives one or more PDSCHs associated with the second HARQ process group within a whole PDSCH reception window, and/or the first PDSCH is scheduled by a DCI with DCI format 1_0 and/or the DCI format 1_0 indicating a counter DAI field value of 1 on a primary cell (PCell), and/or the first PDSCH is a semi-persistent scheduling (SPS) PDSCH, the UE reports an HARQ-ACK information of the first PDSCH in the corresponding PUCCH resource.

221. The method of any one of claims 206 to 214, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, if the UE receives a SPS PDSCH release indicated by a DCI format 1_0 with a counter DAI field value of 1 on a PCell and receives one or more PDSCHs associated with the second HARQ process group within a whole PDSCH reception window, the UE reports an HARQ-ACK information of the SPS PDSCH release in the corresponding PUCCH resource.

222. The method of claim 221, wherein the UE reports NACK of the one or more PDSCHs associated with the second HARQ process group.

223. The method of claim 221, wherein the UE reports an HARQ-ACK information of the one or more PDSCHs associated with the second HARQ process group.

224. The method of claim 221, wherein the UE is configured to report NACK or an HARQ-ACK information of the one or more PDSCHs associated with the second HARQ process group.

225. The method of any one of claims 206 to 214, wherein when the type 3 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 3 HARQ-ACK codebook comprises an HARQ-ACK information of a HARQ process associated with the first HARQ process group 1.

226. The method of claim 225, wherein the type 3 HARQ-ACK codebook comprises the HARQ-ACK information corresponding to all the HARQ processes.

227. The method of claim 225 or 226, wherein a selection of whether or not to comprises the HARQ-information for all the HARQ processes can depend on at least one of the followings: network configuration, or DCI indication, or PUCCH resource allocated for different HARQ process groups.

228. A user equipment (UE) of communication, comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the processor is configured to: determine that physical downlink shared channels (PDSCHs) are divided into N groups, wherein N is an integer equal to or greater than 1; determine a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ a processes are divided into N groups; and determine that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration.

229. The UE of claim 228, wherein when N is equal to 1, all the HARQ processes are of the same group, and all the PDSCHs are belong to the same HARQ process group.

230. The UE of claim 228, wherein when N is greater than 1, several of the HARQ processes are of different groups, and several of the PDSCHs are belong to different HARQ process groups.

231. The UE of any one of claims 228 to 230, wherein the processor is further configured to determine downlink control information (DCI) format, wherein the DCI format contains one or more HARQ process numbers to indicate one or more PDSCHs are associated with the one or more HARQ process numbers.

232. The UE of claim 231, wherein the DCI format is used to schedule the PDSCHs.

233. The UE of claim 231 or 232, wherein a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI) is in the DCI format, and the C-DAI and/or the T-DAI is accumulated within each HARQ process group.

234. The UE of any one of claims 231 to 233, wherein the DCI format comprises a DCI format 1_1, a DCI format 1_2, or a DCI format 1_3.

235. The UE of any one of claims 231 to 234, wherein when the UE is configured with one serving cell, the DCI format scheduling the PDSCHs does not contain T-DAI.

236. The UE of claim 235, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group.

237. The UE of claim 235 or 236, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values corresponding to the several of the PDSCHs are continously counted in the same HARQ process group; when another several of the PDSCHs are scheduled in another same HARQ process group, C-DAI values corresponding to the another several of the PDSCHs are continuously counted in the another same HARQ process group.

238. The UE of any one of claims 231 to 234, wherein when the UE is configured with more than one serving cell, the HARQ process group configuration can be configured per serving cell.

239. The UE of claim 238, wherein cross different serving cells, HARQ process group configurations can be different.

240. The UE of claim 238, wherein the same HARQ process group configuration can be applied for all the serving cells.

241. The UE of any one of claims 238 to 240, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values and T-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group.

242. The UE of any one of claims 238 to 241, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values and T-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group; when another several of the PDSCHs are scheduled in another same HARQ process group, C-DAI values and T-DAI values corresponding to the another several of the PDSCHs are continuously counted in the another same HARQ process group.

243. The UE of claim 231 or 232, wherein the DCI format indicates a corresponding physical uplink control channel (PUCCH) resource for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.

244. The UE of claim 243, wherein the transceiver is configured to transmit a corresponding HARQ-ACK codebook in the PUCCH resource according to an association between one or more HARQ process numbers and N HARQ process groups.

245. The UE of claim 244, wherein the HARQ-ACK codebook comprises a type 1 HARQ-ACK codebook, a type 2 HARQ- ACK codebook, a type 3 HARQ-ACK codebook, or a type 4 HARQ-ACK codebook.

246. The UE of claim 245, wherein in the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, or the type 3 HARQ-ACK codebook, HARQ-ACK information of the PDSCHs are reported.

247. The UE of claim 245, wherein the type 4 HARQ-ACK codebook comprises information relevant to a ratio of successful decoding of all the PDSCHs within N HARQ process groups.

248. The UE of claim 247, wherein the ratio is calculated by a number of the successfully decoded PDSCHs over total transmitted PDSCHs, where the PDSCHs are counted within a given HARQ process group.

249. The UE of claim 247, wherein a total number of the PDSCHs in a given HARQ process group is based on T-DAI.

250. The UE of claim 247, wherein the ratio can be quantized into M bits, where M is equal to 0 or an integer equal to or greater than 1.

251. The UE of any one of claims 247 to 250, wherein the type 4 HARQ-ACK codebook has a constant codebook size.

252. The UE of claim 251, wherein the constant codebook size of the type 4 HARQ-ACK codebook is configured or pre- defined.

253. The UE of claim 251 or 252, wherein the constant codebook size of the type 4 HARQ-ACK codebook is zero or non- zero.

254. The UE of any one of claims 244 to 253, wherein all the PDSCHs are belong to the same HARQ process group and one HARQ-ACK codebook is transmitted in the PUCCH resource.

255. The UE of any one of claims 244 to 253, wherein all the PDSCHs are belong to different HARQ process groups and different HARQ-ACK codebooks are separately transmitted in different PUCCH resources.

256. The UE of any one of claims 244 to 253, wherein all the PDSCHs are belong to different HARQ process groups and are allocated in the same slot, different HARQ-ACK codebooks are transmitted in the same PUCCH resource, and the different HARQ-ACK codebooks are concatenated codebooks.

257. The UE of any one of claims 245 to 253, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 1 HARQ-ACK codebook is semi-static configured and comprises a bit location for one or more PDSCHs belong to the second HARQ-ACK group, the UE sets NACK for the bit location corresponding to the one or more PDSCHs belong to the second HARQ-ACK group, and/or the UE sets a valid ACK or NACK information for one or more PDSCHs belong to the first HARQ process group.

258. The UE of any one of claims 245 to 253, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 1 HARQ-ACK codebook is semi-static configured and comprises a bit location for one or more PDSCHs belong to the second HARQ-ACK group, the UE is configured whether to set NACK for the bit location corresponding to the one or more PDSCHs belong to the second HARQ-ACK group and/or to set a valid ACK or NACK information for one or more PDSCHs belong to the first HARQ process group.

259. The UE of any one of claims 245 to 253, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, if the UE receives a first PDSCH associated with the first HARQ process group and receives one or more PDSCHs associated with the second HARQ process group within a whole PDSCH reception window, and/or the first PDSCH is scheduled by a DCI with DCI format 1_0 and/or the DCI format 1_0 indicating a counter DAI field value of 1 on a primary cell (PCell), and/or the first PDSCH is a semi-persistent scheduling (SPS) PDSCH, the UE reports an HARQ-ACK information of the first PDSCH in the corresponding PUCCH resource.

260. The UE of any one of claims 245 to 253, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, if the UE receives a SPS PDSCH release indicated by a DCI format 1_0 with a counter DAI field value of 1 on a PCell and receives one or more PDSCHs associated with the second HARQ process group within a whole PDSCH reception window, the UE reports an HARQ-ACK information of the SPS PDSCH release in the corresponding PUCCH resource.

261. The UE of claim 260, wherein the transceiver reports NACK of the one or more PDSCHs associated with the second HARQ process group.

262. The UE of claim 260, wherein the transceiver reports an HARQ-ACK information of the one or more PDSCHs associated with the second HARQ process group.

263. The UE of claim 260, wherein the transceiver is configured to report NACK or an HARQ-ACK information of the one or more PDSCHs associated with the second HARQ process group.

264. The UE of any one of claims 245 to 253, wherein when the type 3 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 3 HARQ-ACK codebook comprises an HARQ-ACK information of a HARQ process associated with the first HARQ process group 1.

265. The UE of claim 264, wherein the type 3 HARQ-ACK codebook comprises the HARQ-ACK information corresponding to all the HARQ processes.

266. The UE of claim 264 or 265, wherein a selection of whether or not to comprises the HARQ-information for all the HARQ processes can depend on at least one of the followings: network configuration, or DCI indication, or PUCCH resource allocated for different HARQ process groups.

267. A method of communication of a base station, comprising: configuring, by the base station, physical downlink shared channels (PDSCHs) that are divided into N groups, wherein N is an integer equal to to greater than 1 configuring, by the base station, a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration comprising that HARQ processes are divided into N groups; and configuring, by the base station, that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration.

268. The method of claim 267, wherein when N is equal to 1, all the HARQ processes are of the same group, and all the PDSCHs are belong to the same HARQ process group.

269. The method of claim 267, wherein when N is greater than 1, several of the HARQ processes are of different groups, and several of the PDSCHs are belong to different HARQ process groups.

270. The method of any one of claims 267 to 269, further comprising configuring downlink control information (DCI) format, wherein the DCI format contains one or more HARQ process numbers to indicate one or more PDSCHs are associated with the one or more HARQ process numbers.

271. The method of claim 270, wherein the DCI format is used to schedule the PDSCHs.

272. The method of claim 270 or 271, wherein a counter downlink assignment indicator (C-DAI) and/or a total DAI (T-DAI) is in the DCI format, and the C-DAI and/or the T-DAI is accumulated within each HARQ process group.

273. The method of any one of claims 270 to 272, wherein the DCI format comprises a DCI format 1_1, a DCI format 1_2, or a DCI format 1_3.

274. The method of any one of claims 270 to 273, wherein when the UE is configured with one serving cell, the DCI format scheduling the PDSCHs does not contain T-DAI.

275. The method of claim 274, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C- DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group.

276. The method of claim 274 or 275, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group; when another several of the PDSCHs are scheduled in another same HARQ process group, C-DAI values corresponding to the another several of the PDSCHs are continuously counted in the another same HARQ process group.

277. The method of any one of claims 270 to 273, wherein when the UE is configured with more than one serving cell, the HARQ process group configuration can be configured per serving cell.

278. The method of claim 277, wherein cross different serving cells, HARQ process group configurations can be different.

279. The method of claim 277, wherein the same HARQ process group configuration can be applied for all the serving cells.

280. The method of any one of claims 277 to 279, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values and T-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group.

281. The method of any one of claims 277 to 280, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values and T-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group; when another several of the PDSCHs are scheduled in another same HARQ process group, C-DAI values and T-DAI values corresponding to the another several of the PDSCHs are continuously counted in the another same HARQ process group.

282. The method of claim 270 or 271, wherein the DCI format indicates a corresponding physical uplink control channel (PUCCH) resource for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.

283. The method of claim 282, further comprising configuring a corresponding HARQ-ACK codebook in the PUCCH resource according to an association between one or more HARQ process numbers and N HARQ process groups.

284. The method of claim 283, wherein the HARQ-ACK codebook comprises a type 1 HARQ-ACK codebook, a type 2 HARQ-ACK codebook, a type 3 HARQ-ACK codebook, or a type 4 HARQ-ACK codebook.

285. The method of claim 284, wherein in the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, or the type 3 HARQ-ACK codebook, HARQ-ACK information of the PDSCHs are reported.

286. The method of claim 284, wherein the type 4 HARQ-ACK codebook comprises information relevant to a ratio of successful decoding of all the PDSCHs within N HARQ process groups.

287. The method of claim 286, wherein the ratio is calculated by a number of the successfully decoded PDSCHs over total transmitted PDSCHs, where the PDSCHs are counted within a given HARQ process group.

288. The method of claim 286, wherein a total number of the PDSCHs in a given HARQ process group is based on T-DAI.

289. The method of claim 286, wherein the ratio can be quantized into M bits, where M is equal to 0 or an integer equal to or greater than 1.

290. The method of any one of claims 286 to 289, wherein the type 4 HARQ-ACK codebook has a constant codebook size.

291. The method of claim 290, wherein the constant codebook size of the type 4 HARQ-ACK codebook is configured or pre-defined.

292. The method of claim 290 or 291, wherein the constant codebook size of the type 4 HARQ-ACK codebook is zero or non-zero.

293. The method of any one of claims 283 to 292, wherein all the PDSCHs are belong to the same HARQ process group and one HARQ-ACK codebook is transmitted in the PUCCH resource.

294. The method of any one of claims 283 to 292, wherein all the PDSCHs are belong to different HARQ process groups and different HARQ-ACK codebooks are separately transmitted in different PUCCH resources.

295. The method of any one of claims 283 to 292, wherein all the PDSCHs are belong to different HARQ process groups and are allocated in the same slot, different HARQ-ACK codebooks are transmitted in the same PUCCH resource, and the different HARQ-ACK codebooks are concatenated codebooks.

296. The method of any one of claims 284 to 292, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 1 HARQ-ACK codebook is semi-static configured and comprises a bit location for one or more PDSCHs belong to the second HARQ-ACK group, the UE sets NACK for the bit location corresponding to the one or more PDSCHs belong to the second HARQ-ACK group, and/or the UE sets a valid ACK or NACK information for one or more PDSCHs belong to the first HARQ process group.

297. The method of any one of claims 284 to 292, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 1 HARQ-ACK codebook is semi-static configured and comprises a bit location for one or more PDSCHs belong to the second HARQ-ACK group, the UE is configured whether to set NACK for the bit location corresponding to the one or more PDSCHs belong to the second HARQ-ACK group and/or to set a valid ACK or NACK information for one or more PDSCHs belong to the first HARQ process group.

298. The method of any one of claims 284 to 292, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, if the UE receives a first PDSCH associated with the first HARQ process group and receives one or more PDSCHs associated with the second HARQ process group within a whole PDSCH reception window, and/or the first PDSCH is scheduled by a DCI with DCI format 1_0 and/or the DCI format 1_0 indicating a counter DAI field value of 1 on a primary cell (PCell), and/or the first PDSCH is a semi-persistent scheduling (SPS) PDSCH, the UE reports an HARQ-ACK information of the first PDSCH in the corresponding PUCCH resource.

299. The method of any one of claims 284 to 292, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, if the UE receives a SPS PDSCH release indicated by a DCI format 1_0 with a counter DAI field value of 1 on a PCell and receives one or more PDSCHs associated with the second HARQ process group within a whole PDSCH reception window, the UE reports an HARQ-ACK information of the SPS PDSCH release in the corresponding PUCCH resource.

300. The method of claim 299, wherein the base station receives NACK of the one or more PDSCHs associated with the second HARQ process group.

301. The method of claim 299, wherein the base station receives an HARQ-ACK information of the one or more PDSCHs associated with the second HARQ process group.

302. The method of claim 299, wherein the base station configures the UE to report NACK or an HARQ-ACK information of the one or more PDSCHs associated with the second HARQ process group.

303. The method of any one of claims 284 to 292, wherein when the type 3 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 3 HARQ-ACK codebook comprises an HARQ-ACK information of a HARQ process associated with the first HARQ process group 1.

304. The method of claim 303, wherein the type 3 HARQ-ACK codebook comprises the HARQ-ACK information corresponding to all the HARQ processes.

305. The method of claim 303 or 304, wherein a selection of whether or not to comprises the HARQ-information for all the HARQ processes can depend on at least one of the followings: network configuration, or DCI indication, or PUCCH resource allocated for different HARQ process groups.

306. A base station of communication, comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the processor is configured to: configure physical downlink shared channels (PDSCHs) that are divided into N groups, wherein N is an integer equal to or greater than 1; configure a hybrid automatic repeat request (HARQ) process group configuration, wherein the HARQ process group configuration conmprising that HARQ processes are divided into N groups; and configure that each PDSCH belongs to which HARQ process group according to the HARQ process group configuration.

307. The base station of claim 306, wherein when N is equal to 1, all the HARQ processes are of the same group, and all the PDSCHs are belong to the same HARQ process group.

308. The base station of claim 306, wherein when N is greater than 1, several of the HARQ processes are of different groups, and several of the PDSCHs are belong to different HARQ process groups.

309. The base station of any one of claims 306 to 308, wherein the processer is configured to configure downlink control information (DCI) format, wherein the DCI format contains one or more HARQ process numbers to indicate one or more PDSCHs are associated with the one or more HARQ process numbers.

310. The base station of claim 309, wherein the DCI format is used to schedule the PDSCHs.

311. The base station of claim 309 or 310, wherein a counter downlink assignment indicator (C-DAI) and/or a total DAI (T- DAI) is in the DCI format, and the C-DAI and/or the T-DAI is accumulated within each HARQ process group.

312. The base station of any one of claims 309 to 311, wherein the DCI format comprises a DCI format 1_1, a DCI format 1_2, or a DCI format 1_3.

313. The base station of any one of claims 309 to 312, wherein when the UE is configured with one serving cell, the DCI format scheduling the PDSCHs does not contain T-DAI.

314. The base station of claim 303, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group.

315. The base station of claim 303 or 304, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group; when another several of the PDSCHs are scheduled in another same HARQ process groups, C-DAI values corresponding to the another several of the PDSCHs are continuously counted in the another same HARQ process group.

316. The base station of any one of claims 309 to 312, wherein when the UE is configured with more than one serving cell, the HARQ process group configuration can be configured per serving cell.

317. The base station of claim 316, wherein cross different serving cells, HARQ process group configurations can be different.

318. The base station of claim 316, wherein the same HARQ process group configuration can be applied for all the serving cells.

319. The base station of any one of claims 316 to 318, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values and T-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group.

320. The base station of any one of claims 316 to 319, wherein when several of the PDSCHs are scheduled in the same HARQ process group, C-DAI values and T-DAI values corresponding to the several of the PDSCHs are continuously counted in the same HARQ process group; when another several of the PDSCHs are scheduled in another same HARQ process group, C-DAI values and T-DAI values corresponding to the another several of the PDSCHs are continuously counted in the another same HARQ process group.

321. The base station of claim 309 or 310, wherein the DCI format indicates a corresponding physical uplink control channel (PUCCH) resource for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.

322. The base station of claim 321, the processer is configured to configure a corresponding HARQ-ACK codebook in the PUCCH resource according to an association between one or more HARQ process numbers and N HARQ process groups.

323. The base station of claim 322, wherein the HARQ-ACK codebook comprises a type 1 HARQ-ACK codebook, a type 2 HARQ-ACK codebook, a type 3 HARQ-ACK codebook, or a type 4 HARQ-ACK codebook.

324. The base station of claim 323, wherein in the type 1 HARQ-ACK codebook, the type 2 HARQ-ACK codebook, or the type 3 HARQ-ACK codebook, HARQ-ACK information of the PDSCHs are reported.

325. The base station of claim 323, wherein the type 4 HARQ-ACK codebook comprises information relevant to a ratio of successful decoding of all the PDSCHs within N HARQ process groups.

326. The base station of claim 325, wherein the ratio is calculated by a number of the successfully decoded PDSCHs over total transmitted PDSCHs, where the PDSCHs are counted within a given HARQ process group.

327. The base station of claim 325, wherein a total number of the PDSCHs in a given HARQ process group is based on T- DAI.

328. The base station of claim 325, wherein the ratio can be quantized into M bits, where M is equal to 0 or an integer equal to or greater than 1.

329. The base station of any one of claims 325 to 328, wherein the type 4 HARQ-ACK codebook has a constant codebook size.

330. The base station of claim 329, wherein the constant codebook size of the type 4 HARQ-ACK codebook is configured or pre-defined.

331. The base station of claim 329 or 330, wherein the constant codebook size of the type 4 HARQ-ACK codebook is zero or non-zero.

332. The base station of any one of claims 322 to 331, wherein all the PDSCHs are belong to the same HARQ process group and one HARQ-ACK codebook is transmitted in the PUCCH resource.

333. The base station of any one of claims 322 to 331, wherein all the PDSCHs are belong to different HARQ process groups and different HARQ-ACK codebooks are separately transmitted in different PUCCH resources.

334. The base station of any one of claims 322 to 331, wherein all the PDSCHs are belong to different HARQ process groups and are allocated in the same slot, different HARQ-ACK codebooks are transmitted in the same PUCCH resource, and the different HARQ-ACK codebooks are concatenated codebooks.

335. The base station of any one of claims 323 to 331, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 1 HARQ-ACK codebook is semi-static configured and comprises a bit location for one or more PDSCHs belong to the second HARQ-ACK group, the UE sets NACK for the bit location corresponding to the one or more PDSCHs belong to the second HARQ-ACK group, and/or the UE sets a valid ACK or NACK information for one or more PDSCHs belong to the first HARQ process group.

336. The base station of any one of claims 323 to 331, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 1 HARQ-ACK codebook is semi-static configured and comprises a bit location for one or more PDSCHs belong to the second HARQ-ACK group, the UE is configured whether to set NACK for the bit location corresponding to the one or more PDSCHs belong to the second HARQ-ACK group and/or to set a valid ACK or NACK information for one or more PDSCHs belong to the first HARQ process group.

337. The base station of any one of claims 323 to 331, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, if the UE receives a first PDSCH associated with the first HARQ process group and receives one or more PDSCHs associated with the second HARQ process group within a whole PDSCH reception window, and/or the first PDSCH is scheduled by a DCI with DCI format 1_0 and/or the DCI format 1_0 indicating a counter DAI field value of 1 on a primary cell (PCell), and/or the first PDSCH is a semi-persistent scheduling (SPS) PDSCH, the UE reports an HARQ-ACK information of the first PDSCH in the corresponding PUCCH resource.

338. The base station of any one of claims 323 to 331, wherein when the type 1 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, if the UE receives a SPS PDSCH release indicated by a DCI format 1_0 with a counter DAI field value of 1 on a PCell and receives one or more PDSCHs associated with the second HARQ process group within a whole PDSCH reception window, the UE reports an HARQ-ACK information of the SPS PDSCH release in the corresponding PUCCH resource.

339. The base station of claim 338, wherein the transceiver is configured to receive NACK of the one or more PDSCHs associated with the second HARQ process group.

340. The base station of claim 338, wherein the transceiver is configured to receive an HARQ-ACK information of the one or more PDSCHs associated with the second HARQ process group.

341. The base station of claim 338, wherein the processor configures the UE to report NACK or an HARQ-ACK information of the one or more PDSCHs associated with the second HARQ process group.

342. The base station of any one of claims 323 to 331, wherein when the type 3 HARQ-ACK codebook is configured for a first HARQ process group and the type 4 HARQ-ACK codebook is configured for a second HARQ process group, the type 3 HARQ-ACK codebook comprises an HARQ-ACK information of a HARQ process associated with the first HARQ process group 1.

343. The base station of claim 342, wherein the type 3 HARQ-ACK codebook comprises the HARQ-ACK information corresponding to all the HARQ processes.

344. The base station of claim 342 or 343, wherein a selection of whether or not to comprises the HARQ-information for all the HARQ processes can depend on at least one of the followings: network configuration, or DCI indication, or PUCCH resource allocated for different HARQ process groups.

345. A non-transitory machine-readable storage medium having stored thereon instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 47, 95 to 141, 189 to 227, and 267 to 305.

346. A chip, comprising: a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the method of any one of claims 1 to 47, 95 to 141, 189 to 227, and 267 to 305.

347. A computer readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to execute the method of any one of claims 1 to 47, 95 to 141, 189 to 227, and 267 to 305.

348. A computer program product, comprising a computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 47, 95 to 141, 189 to 227, and 267 to 305.

349. A computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 47, 95 to 141, 189 to 227, and 267 to 305.