Patent Description:
When a New Radio (NR) system is applied to an unlicensed frequency band, StandAlone may be supported, that is, it does not depend on a carrier on a licensed frequency band to provide an auxiliary service. After receiving a Physical Downlink Shared Channel (PDSCH) on an unauthorized carrier, a terminal device needs to send Hybrid Automatic Repeat reQuest Acknowledgement (HARQ-ACK) information, that is, an HARQ codebook, corresponding to the PDSCH on an unauthorized carrier. How to determine the HARQ codebook corresponding to the PDSCH is a problem worth studying.

The document "<NPL>), the document "<NPL>), and the document "<NPL>) disclose art related to the present application.

The invention is set out in independent claims <NUM>, <NUM>, <NUM> and <NUM>.

In the following, references to embodiments not failing within the scope of the claims do not form part of the invention but are to be understood as examples useful for understanding the invention.

Technical schemes in embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The technical solution of the embodiments of the present application may be applied to various communication systems, such as a Global System of Mobile Communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, an Advanced Long Term Evolution (LTE-A) system, a New Radio (NR) system, an evolution system of the NR system, an LTE-based access to unlicensed spectrum (LTE-U) system, an NR-based access to unlicensed spectrum (NR-U) system, a Universal Mobile Telecommunications System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), a future <NUM> system or other communication systems, etc..

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but also support, for example, device to device (D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), vehicle to vehicle (V2V) communication, etc., and the embodiments of the present application may also be applied to these communication systems.

Optionally, a communication system in the embodiments of the present application may also be applied to a Carrier Aggregation (CA) scenario, a Dual Connectivity (DC) scenario, or a Standalone (SA) scenario, etc..

<FIG> is a schematic diagram of a possible wireless communication system according to an embodiment of the present application. The wireless communication system <NUM> may include a network device <NUM>. The network device <NUM> may provide communication coverage for a specific geographical area, and may communicate with terminal devices located within the coverage area.

Optionally, the network device <NUM> may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a NodeB (NB) in a WCDMA system, an Evolutional Node B (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN). Or the network device may be a relay station, an access point, a vehicle-mounted device, a wearable device, a future network side device, or a network device in a future evolved Public Land Mobile Network (PLMN), etc..

The wireless communication system <NUM> further includes at least one terminal device <NUM> located within the coverage area of the network device <NUM>.

The terminal device <NUM> may be mobile or fixed.

Optionally, the terminal device <NUM> may refer to user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with a wireless communication function, a computing device, or other processing devices connected to wireless modems, a vehicle-mounted device, a wearable device, a terminal device in a <NUM> network, or a terminal device in a future evolved Public Land Mobile Network (PLMN), etc., and embodiments of the present application are not limited thereto. Optionally, device to device (D2D) communication may be established between the terminal devices <NUM>.

The network device <NUM> may provide services for a cell, and the terminal device <NUM> communicates with the network device <NUM> through transmission resources (e.g., frequency domain resources or spectrum resources) used by the cell. The cell may be a cell corresponding to the network device <NUM>. The cell may belong to a macro base station, or a base station corresponding to a small cell. The small cell herein may include, for example, a Metro cell, a Micro cell, a Pico cell, a Femto cell, etc., which have characteristics such as small coverage range and low transmission power, and are suitable for providing high-speed data transmission services.

<FIG> illustrates exemplarily one network device and two terminal devices, but the present application is not limited thereto. The wireless communication system <NUM> may include multiple network devices, and other numbers of terminal devices may be included within the coverage area of each network device. In addition, the wireless communication system <NUM> may further include other network entities, such as a network controller and a mobile management entity.

It should be understood that the system shown in <FIG> may be applied to a licensed spectrum or an unlicensed spectrum.

It should also be understood that the unlicensed spectrum is a spectrum divided by countries and regions that may be used for communication of radio devices. This spectrum is generally regarded as a shared spectrum, that is, communication devices in different communication systems can use this spectrum without applying for a proprietary spectrum license from the government, as long as they meet regulatory requirements set by countries or regions on this spectrum.

In order to enable various communication systems using unlicensed spectrum for wireless communication to coexist amicably on this spectrum, some countries or regions have stipulated the legal requirements that must be met for using unlicensed spectrum. For example, the communication devices follow the "Listen Before Talk (LBT)" principle, that is, before sending signals on a channel of the unlicensed spectrum, the communication devices need to performed channel listening first, and the communication devices can send signals only when the result of channel listening is that the channel is idle. If the result of channel listening performed by the communication devices on an unlicensed spectrum channel is that the channel is busy, the communication devices cannot send signals. In order to ensure fairness, in one transmission, a duration of signal transmission performed by a communication device using the channel on the unlicensed spectrum may not exceed a Maximum Channel Occupancy Time (MCOT).

An HARQ feedback process is described below.

An NR system supports dynamic determination of HARQ feedback timing. A base station schedules a terminal device to receive a PDSCH through Downlink Control Information (DCI), wherein the DCI includes indication information of a Physical Uplink Control Channel (PUCCH) resource for transmitting an HARQ codebook corresponding to the PDSCH. Specifically, the indication information includes: a PUCCH resource indicator, used for determining a PUCCH resource; and an HARQ timing indicator, used for dynamically determining a time domain position of the PUCCH resource. Herein, the HARQ timing indicator information is used for determining a value in a preconfigured HARQ timing set. For example, when the HARQ timing indicator information is <NUM>, k0 in the HARQ timing set is indicated, and when the HARQ timing indicator information is <NUM>, k1 in the HARQ timing set is indicated, etc..

If the feedback is dynamic codebook feedback, the DCI also includes following information: a Downlink assignment index (DAI), wherein the DAI includes counter DAI information and/or total DAI information, wherein the counter DAI information is used for indicating which PDSCH in a current HARQ feedback window a currently scheduled PDSCH is, and the DAI total information is used for indicating how many PDSCHs are totally scheduled in the current HARQ feedback window.

According to the above information, the terminal device can determine a PUCCH resource for feeding back the HARQ codebook and a position of the HARQ codebook in a codebook transmitted on the PUCCH resource.

Optionally, when using a dynamic codebook for HARQ codebook feedback, the terminal device may perform dynamic codebook feedback in single-carrier and multi-carrier scenarios.

That is, the dynamic codebook may be specifically classified into the following two cases.

The network device will send counter DAI (C-DAI) information to the terminal device while sending a PDSCH to the terminal device, wherein the counter DAI information is sent to the terminal device through a Physical Downlink Control Channel (PDCCH) for the terminal device to determine an HARQ feedback codebook. That is, the counter DAI is used for indicating which PDSCH in the HARQ feedback window a PDSCH currently scheduled by the PDCCH is, wherein a PDSCH sorting mode is sorted according to an order of PDCCH detection opportunities. In order to reduce a quantity of bits of the counter DAI information, counting may performed in a modular operation mode. For example, if a quantity of bits of the counter DAI is <NUM> bits, a value of the counter DAI is modulo <NUM>; if a quantity of bits of the counter DAI is <NUM> bits, a value of the counter DAI is modulo <NUM>. As shown in <FIG>, there are totally <NUM> time slots in an HARQ codebook feedback window, and each time slot is configured with a PDCCH detection opportunity. The network device schedules the terminal device to receive PDSCHs on a 1st, 3rd, 4th, 5th, and 7th PDCCH detection opportunities in the <NUM> PDCCH detection opportunities. Assuming that a quantity of bits of the counter DAI is <NUM> bits, correspondingly, counter DAIs corresponding to PDSCHs on the <NUM> time slots are <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>, respectively.

For each PDSCH, a corresponding quantity K of HARQ codebook feedback bits may be configured by a higher layer. For example, if at least one PDSCH in PDSCHs for which the terminal device is scheduled supports <NUM> codewords, a quantity of HARQ codebook bits corresponding to each of all PDSCHs is <NUM> bits (K=<NUM>). For another example, when feedback based on a Code block group (CBG) is supported, it is assumed that a maximum quantity of HARQ codebook bits corresponding to one PDSCH is <NUM> bits, and a quantity of HARQ codebook bits corresponding to each PDSCH in all PDSCHs is <NUM> bits (K=<NUM>).

In an example of <FIG>, it is assumed that K=<NUM>, which corresponds to two codewords. After the terminal device receives the <NUM> PDSCHs, the terminal device may determine that a codebook size in the HARQ codebook feedback window is <NUM> bits, as shown as table <NUM> below.

When the terminal device only receives part of the <NUM> PDSCHs, for example, the terminal device does not receive the PDSCH with the counter DAI of <NUM>, in this case, the PDSCH with the counter DAI of <NUM> is received after the PDSCH with the counter DAI of <NUM> is received. In this case, the terminal device may determine that it has lost the PDSCH with the counter DAI of <NUM>, so a Negative Acknowledgement (NACK) will be filled at a corresponding position, as shown as table <NUM> below.

It should be understood that if there is only one codeword in a PDSCH, an HARQ codebook corresponding to codeword <NUM> is NACK.

While sending a PDSCH to the terminal device, the network device will send two pieces of DAI information, i.e., a counter DAI and a total DAI (T-DAI), to the terminal device, wherein the two pieces of DAI information are sent to the terminal device through a PDCCH for the terminal device to determine an HARQ feedback codebook. Herein the counter DAI is used for indicating which PDSCH in the HARQ feedback window a PDSCH currently scheduled by the PDCCH is, and the total DAI is used for telling the terminal device how many HARQ codebooks there totally are in the HARQ feedback window so far. A PDSCH sorting mode is sorted according to an order of PDCCH detection opportunities, specifically, it may be in an order of the frequency domain first and then the time domain. In order to reduce a quantity of bits of the counter DAI (or total DAI) information, counting may be performed in a modular operation mode. For example, if a quantity of bits of the counter DAI (or the total DAI) is <NUM> bits, a value of the counter DAI (or the total DAI) is modulo <NUM>; if a quantity of bits of the counter DAI (or the total DAI) is <NUM> bits, a value of the counter DAI (or the total DAI) is modulo <NUM>.

As shown in <FIG>, a terminal device is configured with two carriers, a total of eight time slots are included in the HARQ codebook feedback window, and each time slot of each carrier is configured with a PDCCH detection opportunity, then the PDCCH detection opportunities are sorted as a first time slot of carrier #<NUM>, a first time slot of carrier #<NUM>, a second time slot of carrier #<NUM>, a second time slot of carrier #<NUM>,. , an eighth time slot of carrier #<NUM>, an eighth time slot of carrier #<NUM>. The network device schedules the terminal device to receive PDSCHs on the 1st, 2nd, 6th, 7th, 8th, 9th, 13th, and 14th time slots in the <NUM> PDCCH detection opportunities. Assuming that quantities of bits of the counter DAI and the total DAI are <NUM> bits respectively, accordingly, the counter DAIs and the total DAIs corresponding to PDSCHs on these <NUM> time slots are shown in <FIG>.

In an example of <FIG>, it is assumed that K=<NUM>, which corresponds to two codewords. Assuming that the terminal device does not receive a PDSCH on the fourth time slot, the terminal device may determine a codebook in the HARQ codebook feedback window as shown as table <NUM> below.

It should be understood that a PDSCH scheduled by a PDCCH may or may not be on a same time slot as the PDCCH, which is not limited by the embodiments of the present application.

When an NR system is applied to an unlicensed frequency band, a UE needs to send HARQ feedback corresponding to a PDSCH on an unlicensed carrier after receiving the PDSCH on an unlicensed carrier.

At present, on the unlicensed frequency band, the HARQ timing indicator information may be used not only to determine a PUCCH time domain resource for transmitting HARQ corresponding to the PDSCH, but also to indicate a state in which the HARQ corresponding to the PDSCH will not be fed back temporarily. For example, a preconfigured HARQ timing set includes a value kL indicating an invalid resource indicator, and when the HARQ timing indicator information is <NUM>, kL in the HARQ timing set is indicated, indicating that a corresponding PUCCH resource cannot be determined temporarily.

In addition, in order to flexibly feed back HARQ information corresponding to a PDSCH on the unlicensed frequency band, the base station may group scheduled PDSCHs and indicate grouping information of the PDSCHs through a displaying signaling, so that a UE performs corresponding HARQ feedback according to different groups after receiving the PDSCHs. If a certain group of HARQ information of the UE fails to be transmitted due to an LBT failure in a certain transmission, or the base station fails to detect a certain group of HARQ information expected to be transmitted by the UE on a certain PUCCH resource, the base station may trigger the UE to retransmit this group of HARQ information through DCI. The UE may keep a same codebook size as that of an initial transmission when retransmitting a certain group of HARQ information, and may also add new HARQ information when retransmitting.

<FIG> are schematic block diagrams of PDSCH groups and feedback groups when a UE needs to perform HARQ feedback according to grouping of a base station.

When the UE needs to perform HARQ feedback according to the grouping of the base station, specific feedback modes may include the following two modes.

After the base station performs grouping, when HARQ information included in the group is initially transmitted or retransmitted, an HARQ codebook size does not change. Or, if one valid uplink resource for transmission has been indicated to HARQ corresponding to a PDSCH in a certain group, no new PDSCH will be added into the group. In the first mode, HARQ information included in multiple groups may be fed back on one PUCCH resource. For example, referring to <FIG>, PUCCH <NUM> may feed back HARQ information included in group <NUM>, and HARQ information included in the group <NUM> and group <NUM> may be fed back on PUCCH <NUM>.

After the base station performs grouping, when HARQ information included in the group is initially transmitted or retransmitted, an HARQ codebook size may be different. Or, if one valid uplink resource for transmission has been indicated to HARQ corresponding to a PDSCH in a certain group, a new PDSCH may be added into the group. For example, referring to <FIG>, HARQ information included in group <NUM> may be fed back on PUCCH <NUM> and PUCCH <NUM>, respectively.

Optionally, DAIs corresponding to PDSCHs transmitted in multiple groups may be uniformly counted.

<FIG> is a schematic block diagram of a positional relationship among channel groups, DAIs, and feedback groups according to an embodiment of the present application.

It should be understood that in the embodiment of the present application, one carrier is taken as an example for description, and a similar method may be used for a case of multiple carriers.

With reference to <FIG>, a PDSCH group with group number #<NUM> includes PDSCH <NUM>, PDSCH <NUM>, PDSCH <NUM>, PDSCH <NUM>, and PDSCH <NUM>. A PDSCH group with group number #<NUM> includes PDSCH <NUM>, PDSCH <NUM>, PDSCH <NUM>, and PDSCH <NUM>. Herein, a DAI corresponding to PDSCH <NUM> to a DAI corresponding to PDSCH <NUM> are counted consecutively.

<FIG> is a schematic flowchart of a method <NUM> for transmitting an HARQ codebook according to an embodiment of the present application. The method <NUM> may be performed by interactions of a terminal device and a network device. The terminal device shown in <FIG> may be the terminal device as shown in <FIG>, and the network device shown in <FIG> may be the access network device as shown in <FIG>.

Referring to <FIG>, the method <NUM> may include part or all of the following contents.

In S210, a network device determines a first uplink resource.

In S220, a terminal device determines the first uplink resource.

In S230, the terminal device determines a first HARQ codebook corresponding to at least one of multiple channel groups for the first uplink resource.

In S240, the terminal device sends the first HARQ codebook to the network device.

The terminal device determines the first uplink resource, wherein the first uplink resource is used for feeding back a first HARQ codebook corresponding to at least one of multiple channel groups, wherein Downlink assignment indexes (DAIs) corresponding to Physical Downlink Shared Channels (PDSCHs) in the multiple channel groups are counted consecutively. The terminal device determines the first HARQ codebook for the first uplink resource.

The network device determines the first uplink resource, wherein the first uplink resource is used for feeding back a first HARQ codebook corresponding to at least one of multiple channel groups, wherein Downlink assignment indexes (DAIs) corresponding to Physical Downlink Shared Channels (PDSCHs) in the multiple channel groups are counted consecutively. The network device receives the first HARQ codebook on the first uplink resource.

The first uplink resource may be a resource for transmitting an uplink channel.

Optionally, the uplink channel includes, but is not limited to, a Physical Random Access Channel (PRACH), a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared channel (PUSCH), etc. It should be understood that embodiments of the present application may include an uplink channel with a same name as above and a different function from above, or may include an uplink channel with a different name from above and a same function as above, which is not limited by the present application.

It should be understood that the HARQ codebook may also be referred to as HARQ information, an HARQ-ACK codebook, or HARQ-ACK information.

The channel group may be a downlink channel group. For example, the channel group is a channel group corresponding to PDSCHs, or a channel group corresponding to PDCCHs.

The first uplink resource is used for feeding back a first HARQ codebook corresponding to at least one of multiple channel groups, wherein the first HARQ codebook includes an HARQ codebook corresponding to a channel in each of the at least one channel group. For example, the channel group is a PDSCH channel group, then the first HARQ codebook includes an HARQ codebook corresponding to a PDSCH in each of the at least one PDSCH channel group.

When a first DAI corresponding to a first PDSCH in a first channel group of the at least one channel group is not an initial value, information of the first HARQ codebook at a starting position is placeholder information.

When a first DAI corresponding to a first PDSCH in a first channel group of the at least one channel group is an initial value, information of the first HARQ codebook at a starting position is an HARQ codebook corresponding to the first PDSCH.

The first HARQ codebook between the starting position and a position corresponding to the first DAI is placeholder information, wherein the position corresponding to the first DAI is a position, determined based on a count of the first DAI, in the first HARQ codebook.

The at least one channel group includes at least two channel groups.

The at least two channel groups are channel groups with consecutively counted DAIs triggered for feeding back.

Optionally, the at least two channel groups include channel groups with disconsecutively counted DAIs triggered for feeding back, wherein the first HARQ codebook is an HARQ codebook generated based on a consecutively counted DAI, and a position corresponding to a channel group not triggered for feeding back in the first HARQ codebook is placeholder information.

Optionally, an arrangement order of channel groups in the multiple channel groups is a DAI counting order, or a scheduling order.

Optionally, an arrangement order of channel groups in the at least one channel group is an order of channel groups triggered for feeding back in the multiple channel groups; or, an arrangement order of channel groups in the at least one channel group is a DAI counting order; or, an arrangement order of channel groups in the at least one channel group is a scheduling order.

With reference to <FIG>, the first HARQ codebook will be described in detail below when the at least two channel groups are channel groups with consecutively counted DAIs triggered for feeding back.

Please referring to <FIG>, if a UE needs to only feed back HARQ information included in group <NUM> on a PUCCH <NUM> resource, when the UE does not receive PDSCH <NUM> (or PDSCH <NUM>, here, not receiving the PDSCH <NUM> is taken as an example), the UE cannot determine whether the PDSCH <NUM> belongs to group <NUM> or the group <NUM>, then the UE may consider that numbers of PDSCHs included in the group <NUM> are <NUM>, <NUM>, <NUM>, or consider that numbers of PDSCHs included in the group <NUM> are <NUM>, <NUM>, <NUM>, <NUM>, that is, the UE will be unable to determine the starting PDSCH of the PDSCHs included in the group <NUM>, thereby unable to determine an HARQ codebook corresponding to the group <NUM> (A main problem when only HARQ information corresponding to one group is fed back on one uplink resource).

In a possible implementation, when the UE feeds back HARQ information on one uplink resource such as a PUCCH resource, a codebook is always prepared from <NUM> for the HARQ information fed back on the uplink resource. In this way, the base station and the UE can determine a size of an HARQ codebook fed back on one PUCCH resource.

With reference to <FIG>, if only one HARQ codebook of one group is fed back on one uplink resource, for example, group <NUM> is fed back on PUCCH <NUM>, and group <NUM> is fed back on PUCCH <NUM>, no matter what a DAI corresponding to a first PDSCH in this group received by the UE is, the UE will prepare an HARQ codebook from a DAI of <NUM>. In an embodiment of the present application, a feedback codebook of one PDSCH corresponding to two codewords is taken as an example.

An HARQ codebook corresponding to PDSCHs in group <NUM> included in an HARQ codebook transmitted on PUCCH <NUM> is shown as table <NUM>.

In feedback on PUCCH <NUM>, through preparing the HARQ codebook from a counter DAI of <NUM>, no matter whether the UE has received PDSCH <NUM> or PDSCH <NUM>, the base station and the UE have consistent understanding of codebook positions corresponding to PDSCHs correctly received by the UE, thus realizing transmission of the HARQ codebook.

If an HARQ codebook of at least two groups is fed back on one uplink resource, in one case, it may be limited that the base station can only trigger HARQ codebook feedback of continuous multiple groups, so as to avoid inconsistent understanding of HARQ codebooks between the base station and the UE caused by loss of a DAI. For example, group <NUM> and group <NUM> are fed back on PUCCH <NUM> (here, the group <NUM> and the group <NUM> are continuous, but it is limited here that sending groups are continuous, it is not necessary that group numbers are continuous), the group <NUM>, the group <NUM>, and group <NUM> are fed back on PUCCH <NUM>, and the UE may prepare a codebook according to a scheduling order of the base station. When the UE prepares an HARQ codebook transmitted on the PUCCH resource, no matter what a DAI corresponding to a first PDSCH in a first sorted group is, the UE prepares the HARQ codebook starting from a DAI of <NUM>. Since the feedback is for feedback triggering of a codebook of continuous groups, the UE prepares an HARQ codebook according to a DAI order, and does not need to supplement placeholder information.

An HARQ codebook corresponding to PDSCHs in group <NUM> and group <NUM> included in an HARQ codebook transmitted on PUCCH <NUM> is shown as table <NUM>.

An HARQ codebook corresponding to PDSCHs in group <NUM>, group <NUM>, and group <NUM> included in an HARQ codebook transmitted on PUCCH <NUM> may be shown as table <NUM>.

In continuous feedback of multiple groups on PUCCH <NUM>, through starting from a counter DAI of <NUM> and DAIs corresponding to multiple groups being consecutively counted, it can be ensured that the base station and the UE have consistent understanding of codebook positions corresponding to PDSCHs correctly received by the UE, thus realizing transmission of the HARQ codebook.

If an HARQ codebook of at least two groups is fed back on one uplink resource, in another case, it is not limited that the base station can only trigger HARQ codebook feedback of continuous multiple groups, which has an advantage that HARQ information corresponding to an HARQ process included in a middle group(s) may be released as soon as possible for downlink scheduling of the base station.

<FIG> is another schematic block diagram of a positional relationship among channel groups, DAIs, and feedback groups according to an embodiment of the present application.

In a case of multiple channel groups with consecutively counted DAIs and at least two of the multiple channel groups being channel groups with disconsecutively counted DAIs triggered for feeding back, the first HARQ codebook will be described in detail with reference to <FIG> below.

Please referring to <FIG>, groups <NUM> and <NUM> are fed back on PUCCH <NUM>, and groups <NUM> and <NUM> are fed back on PUCCH <NUM>, and the UE may prepare a codebook according to a scheduling order of the base station. When the UE prepares an HARQ codebook transmitted on the PUCCH resource, no matter what a DAI corresponding to a first PDSCH in a first sorted group is, the UE prepares the HARQ code starting from a DAI of <NUM>. Specifically, the UE prepares the HARQ codebook according to a DAI order, and needs to supplement placeholder information for a middle group(s) that is(are) not triggered to send HARQ information. The placeholder mode can ensure that, for codebook positions corresponding to PDSCHs correctly received by the UE, the base station and the UE have consistent understanding.

Optionally, the placeholder information is preset information.

Optionally, the placeholder information is NACK information.

Optionally, the placeholder information is not information with a specific meaning such as NACK information, etc., or a position corresponding to the placeholder information cannot normally place the codebook. For example, it may be understood that the position corresponding to the placeholder information is left a blank, that is, is not used for placing codebook information.

An HARQ codebook corresponding to PDSCHs in group <NUM> and group <NUM> included in an HARQ codebook transmitted on PUCCH <NUM> may be shown as table <NUM>.

The present application also provides a method for triggering a terminal device to perform feedback.

Optionally, it may be indicated through DCI indication information whether a channel group in the above multiple channel groups is triggered for feeding back.

In the embodiment of the present application, the terminal device can be simply and effectively triggered to feed back a codebook.

Herein, a quantity of groups may be configured by the base station or predefined. For example, a quantity of groups configured by the base station is <NUM>.

Optionally, the first DCI may include one piece of valid HARQ timing indicator information, which is used for determining the above first uplink resource.

Optionally, the terminal device receives first Downlink Control Information (DCI), wherein the first DCI is used for scheduling a first PDSCH, the first PDSCH belongs to a first channel group, the first DCI includes first indication information, and the first indication information is used for indicating whether feeding back is triggered for a channel group in the multiple channel groups. Optionally, feedback triggering information of the multiple channel groups included in the first indication information is arranged in an order of group numbers from small to large or group numbers from large to small. That is, if an HARQ codebook of at least two groups is fed back on one uplink resource, the base station may trigger feedback in an order of group numbers from small to large (or group numbers from large to small or in an order designated by the base station) when triggering the UE to feed back HARQ information of this group.

In an implementation, the first indication information is used for indicating whether feeding back is triggered for a channel group except the first channel group in the multiple channel groups. For example, HARQ timing indicator information in the first DCI is used for determining the first uplink resource, and the first indication information is used for indicating whether feeding back is triggered for a channel group except the first channel group in the multiple channel groups on the first uplink resource.

For example, assuming that a first PDSCH belongs to channel group #<NUM>, and the base station is configured with <NUM> groups including the channel group #<NUM>, then the following contents may be included.

Optionally, HARQ information corresponding to the channel group #<NUM> is fed back through a first uplink resource indicated by valid HARQ timing indicator information.

Optionally, HARQ information corresponding to another triggered channel group except the channel group #<NUM> is also fed back through the first uplink resource.

Optionally, the first indication information includes group triggering information of <NUM> bits, wherein the group triggering information of <NUM> bits is used for indicating whether other channel groups except the channel group #<NUM> are triggered to feed back HARQ information, respectively. Optionally, the group triggering information of <NUM> bits may be sorted from small to large according to numbers of other groups except a group to which the first PDSCH belongs (i.e., the channel group #<NUM>). For example, <NUM> indicates that group <NUM> is triggered, <NUM> indicates that group <NUM> is triggered, and <NUM> indicates that group <NUM> is triggered. For another example, <NUM> indicates that group <NUM> and group <NUM> are triggered.

Optionally, an HARQ codebook arrangement order corresponding to channel groups triggered for feeding back may be prepared according to a scheduling order. For example, the channel groups triggered for feeding back include groups #<NUM>, #<NUM>, and #<NUM>, and an order of groups scheduled by the base station (i.e., a DAI order) is group #<NUM>, group #<NUM>, and group #<NUM>, then the UE prepares an HARQ codebook according to an order of group #<NUM>, group #<NUM>, and group #<NUM>.

In another implementation, the first indication information is used for indicating whether each of the multiple channel groups is triggered for feeding back. For example, HARQ timing indicator information in the first DCI is used for determining the first uplink resource, and the first indication information is used for indicating whether each of the multiple channel groups is triggered for feeding back on the first uplink resource.

For example, assuming that a first PDSCH belongs to channel group #<NUM>, and the base station is configured with <NUM> groups including the channel group #<NUM>, then part or all of the following contents may be included.

The first first DCI includes one piece of valid HARQ timing indicator information, and the first DCI also includes group triggering information of <NUM> bits, wherein the <NUM> bits are used for indicating whether the <NUM> groups are triggered for HARQ information feedback.

Optionally, a value of the HARQ timing indicator information is meaningful only when the channel group #<NUM> is triggered.

The HARQ timing indicator information is used for indicating a first uplink resource used for HARQ information feedback corresponding to the triggered channel group.

Optionally, the channel group #<NUM> may or may not be triggered for feeding back.

Optionally, the HARQ timing indicator information in the first DCI is specifically used for indicating that HARQ information corresponding to the first PDSCH will not be fed back temporarily, the first indication information is invalid. For example, the terminal device ignores the first indication information. Optionally, when the HARQ timing indicator information in the first DCI is specifically used for indicating that the HARQ information corresponding to the first PDSCH will not be fed back temporarily, the first indication information may be used for another purpose, for example, used as other information.

Optionally, the terminal device receives second DCI, wherein the second DCI is used for scheduling a second PDSCH, HARQ timing indicator information in the second DCI is used for indicating that HARQ information corresponding to the second PDSCH will not be fed back temporarily, and the second DCI does not include indication information for indicating whether a channel group in the multiple channel groups is triggered for feeding back.

For example, assuming that a second PDSCH belongs to channel group #<NUM>, and the base station is configured with <NUM> groups including the channel group #<NUM>, then part or all of the following contents may be included.

Optionally, the second DCI may not include indication information (i.e., the aforementioned <NUM> bits or <NUM> bits) that triggers HARQ information feedback of the at least one group, or indication information that triggers HARQ information feedback of the at least one group, included in the second DCI, indicates that feedback is not triggered. Or, a value of indication information that triggers HARQ information feedback of the at least one group, included in the second DCI, is meaningless. Or, a value of indication information that triggers HARQ information feedback of the at least one group, included in the second DCI, may be used for another purpose, for example, used as other information.

The terminal device receives third DCI, wherein the third DCI is not used for scheduling a PDSCH, the third DCI includes second indication information, and the second indication information is used for indicating whether a channel group in the multiple channel groups is triggered for feeding back. Optionally, feedback triggering information of the multiple channel groups included in the second indication information is arranged in an order of group numbers from small to large or group numbers from large to small. Optionally, the third DCI further includes HARQ timing indicator information for determining the first uplink resource, and the second indication information is used for indicating whether feedback of each of the multiple channel groups is on the first uplink resource.

For example, assuming that the base station is configured with <NUM> groups, and the third DCI is not used for scheduling a PDSCH (for example, the third DCI is not used for scheduling PDSCHs within the <NUM> groups), then part or all of the following contents may be included.

The third DCI may include <NUM> bits, wherein the <NUM> bits are used for indicating whether the <NUM> groups are triggered for feeding back HARQ information.

The third DCI includes one piece of valid HARQ timing indicator information, wherein the valid HARQ timing indicator information is used for indicating an uplink resource used by HARQ information feedback corresponding to the triggered channel group. That is, the second indication information is used for indicating whether feedback of each of the multiple channel groups is on the first uplink resource.

When preparing the HARQ codebook, the UE may prepare if according to a DAI order or a scheduling order of the base station or an order of scheduled groups. Therefore, it can be ensured that, for codebook positions corresponding to PDSCHs correctly received by the UE, the base station and the UE have consistent understanding.

With reference to <FIG>, assuming that the base station is configured with four groups, when HARQ feedback is triggered, if a triggering signaling does not schedule a PDSCH, then a signaling for triggering to feed back HARQ of groups on PUCCH2 is <NUM> (i.e. triggering to feed back group <NUM> and group <NUM> on PUCCH2), and a signaling of for triggering to feed back HARQ of groups on PUCCH3 is <NUM> (i.e. triggering to feed back group <NUM>, group <NUM>, and group <NUM> on PUCCH2).

If a signaling for triggering to feed back HARQ on PUCCH2 is indicated by DCI scheduling PDSCH <NUM>, then a triggering signaling is <NUM> (that is, group <NUM> to which PDSCH <NUM> belongs is triggered by default); if a signaling for triggering to feed back HARQ on PUCCH3 is indicated by a DCI scheduling PDSCH <NUM>, then a triggering signaling is <NUM> (that is, group <NUM> to which PDSCH <NUM> belongs is triggered by default).

Herein, a UE prepares an HARQ codebook on PUCCH <NUM> according to an order of group #<NUM> and group #<NUM>; and the UE prepares an HARQ codebook on PUCCH <NUM> according to an order of groups #<NUM>, #<NUM>, and #<NUM>.

The preferred embodiments of the present application have been described in detail above with reference to the accompanying drawings.

It should be understood that sequence numbers of the foregoing processes do not mean execution sequences in various method embodiments of the present application. The execution sequences of the processes should be determined according to functions and internal logics of the processes, and should not be construed as any limitation on the implementation processes of the embodiments of the present application.

Method embodiments of the present application are described in detail above in combination with <FIG>. Device embodiments of the present application are described in detail below in combination with <FIG>.

<FIG> is a schematic block diagram of a terminal device <NUM> according to an embodiment of the present application.

Please referring to <FIG>, the terminal device <NUM> may include: a processing unit <NUM>, configured to: determine a first uplink resource, wherein the first uplink resource is used for feeding back a first HARQ codebook corresponding to at least one of multiple channel groups, wherein Downlink assignment indexes (DAIs) corresponding to Physical Downlink Shared Channels (PDSCHs) in the multiple channel groups are counted consecutively; and determine the first HARQ codebook for the first uplink resource.

Optionally, the at least one channel group includes at least two channel groups.

Optionally, the at least two channel groups are channel groups with consecutively counted DAIs triggered for feeding back.

Optionally, an arrangement order of channel groups in the multiple channel groups is a DAI counting order; or an arrangement order of channel groups in the multiple channel groups is a scheduling order.

The terminal device <NUM> further includes: a communication unit, configured to receive first Downlink Control Information (DCI), wherein the first DCI is used for scheduling a first PDSCH, the first PDSCH belongs to a first channel group, the first DCI includes first indication information, and the first indication information is used for indicating whether a channel group in the multiple channel groups is triggered for feeding back.

The first indication information is used for indicating whether a channel group except the first channel group in the multiple channel groups is triggered for feeding back; or, the first indication information is used for indicating whether each of the multiple channel groups is triggered for feeding back.

Optionally, feedback triggering information of the multiple channel groups included in the first indication information is arranged in an order of group numbers from small to large or group numbers from large to small.

Optionally, HARQ timing indicator information in the first DCI is used for determining the first uplink resource, and the first indication information is used for indicating whether a channel group except the first channel group in the multiple channel groups is triggered for feeding back on the first uplink resource; or, the first indication information is used for indicating whether each of the multiple channel groups is triggered for feeding back on the first uplink resource.

Optionally, the HARQ timing indicator information in the first DCI is specifically used for indicating that HARQ information corresponding to the first PDSCH will not be fed back temporarily, and the first indication information is invalid.

Optionally, the terminal device <NUM> may further include: a communication unit, configured to receive second DCI, wherein the second DCI is used for scheduling a second PDSCH, HARQ timing indicator information in the second DCI is used for indicating that HARQ information corresponding to the second PDSCH will not be fed back temporarily, and the second DCI does not include indication information for indicating whether a channel group in the multiple channel groups is triggered for feeding back.

The terminal device <NUM> further includes: a communication unit, configured to receive third DCI, wherein the third DCI is not used for scheduling a PDSCH, the third DCI includes second indication information, and the second indication information is used for indicating whether a channel group in the multiple channel groups is triggered for feeding back.

Optionally, feedback triggering information of the multiple channel groups included in the second indication information is arranged in an order of group numbers from small to large or group numbers from large to small.

The third DCI further includes HARQ timing indicator information for determining the first uplink resource, and the second indication information is used for indicating whether each of the multiple channel groups is fed back on the first uplink resource.

Optionally, the first uplink resource includes a Physical Uplink Control Channel (PUCCH) resource and/or a Physical Uplink Shared channel (PUSCH) resource.

It should be understood that the device embodiments may correspond to the method embodiments with each other, and description of the method embodiments may be referred to for similar description of the device embodiments. Specifically, the terminal device <NUM> shown in <FIG> may correspond to a corresponding subject performing the method <NUM> in the embodiment of the present application, and the above and other operations and/or functions of various units in the terminal device <NUM> are respectively for realizing corresponding flows of various methods in <FIG>, which will not be repeated here for the sake of brevity.

<FIG> is a schematic block diagram of a network device <NUM> according to an embodiment of the present application.

Please referring to <FIG>, the network device <NUM> may include: a processing unit <NUM>, configured to determine a first uplink resource, wherein the first uplink resource is used for feeding back a first HARQ codebook corresponding to at least one of multiple channel groups, wherein Downlink assignment indexes (DAIs) corresponding to Physical Downlink Shared Channels (PDSCHs) in the multiple channel groups are counted consecutively; and a communication unit <NUM>, configured to receive the first HARQ codebook on the first uplink resource.

Optionally, an arrangement order of channel groups in the at least one channel group is an order of channel groups triggered for feeding back in the multiple channel groups; or an arrangement order of channel groups in the at least one channel group is a DAI counting order; or, an arrangement order of channel groups in the at least one channel group is a scheduling order.

Optionally, the communication unit <NUM> is further configured to send first Downlink Control Information (DCI), wherein the first DCI is used for scheduling a first PDSCH, the first PDSCH belongs to a first channel group, the first DCI includes first indication information, and the first indication information is used for indicating whether a channel group in the multiple channel groups is triggered for feeding back.

Optionally, the first indication information is used for indicating whether a channel group except the first channel group in the multiple channel groups is triggered for feeding back; or, the first indication information is used for indicating whether each of the multiple channel groups is triggered for feeding back.

Optionally, the communication unit <NUM> is further configured to send second DCI, wherein the second DCI is used for scheduling a second PDSCH, HARQ timing indicator information in the second DCI is used for indicating that HARQ information corresponding to the second PDSCH will not be fed back temporarily, and the second DCI does not include indication information for indicating whether a channel group in the multiple channel groups is triggered for feeding back.

The communication unit <NUM> is further configured to send third DCI, wherein the third DCI is not used for scheduling a PDSCH, the third DCI includes second indication information, and the second indication information is used for indicating whether a channel group in the multiple channel groups is triggered for feeding back.

It should be understood that the device embodiments may correspond to the method embodiments with each other, and description of the method embodiments may be referred to for similar description of the device embodiments. It should be understood that the network device <NUM> shown in <FIG> may correspond to a corresponding subject performing the method <NUM> in the embodiment of the present application, and the above and other operations and/or functions of various units in the network device <NUM> are respectively for realizing corresponding flows of various methods in <FIG>, which will not be repeated here for the sake of brevity.

In the above, the communication device according to an embodiment of the present application is described from a perspective of a functional module. It should be understood that the functional module may be realized in form of hardware, or through instructions in form of software, or through a combination of hardware and software modules.

Specifically, various acts of the method embodiments in the embodiments of the present application can be implemented by hardware integrated logic circuits and/or instructions in the form of software in a processor, and the acts of methods disclosed with reference to the embodiments of the present application may be directly executed and implemented by a hardware decoding processor, or may be implemented by a combination of hardware and software modules in the decoding processor.

Optionally, the software modules may be located in a storage medium commonly used in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register, etc. The storage medium is located in the memory, and the processor reads information in the memory and completes the acts of the above method embodiments in combination with its hardware.

For example, in an embodiment of the present application, the processing unit <NUM> shown in <FIG> and the processing unit <NUM> shown in <FIG> may be implemented by a processor, and the communication unit <NUM> shown in <FIG> may be implemented by a transceiver.

<FIG> is a schematic diagram of a structure of a communication device <NUM> according to an embodiment of the present application.

Please referring to <FIG>, the communication device <NUM> may include a processor <NUM>, wherein the processor <NUM> may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

Optionally, the communications device <NUM> may further include a memory <NUM>.

The memory <NUM> may be configured to store indication information, or may be configured to store codes, instructions, etc., executed by the processor <NUM>. The processor <NUM> may call and run the computer program from the memory <NUM> to implement the methods in the embodiments of the present application.

Optionally, the communication device <NUM> may further include a transceiver <NUM>, and the processor <NUM> may control the transceiver <NUM> to communicate with another device. Specifically, information or data may be sent to another device, or information or data sent by another device may be received.

The transceiver <NUM> may further include antennas, and the quantity of which may be one or more.

Optionally, the communication device <NUM> may be a terminal device according to the embodiments of the present application, and the communication device <NUM> may implement corresponding processes implemented by the terminal device in various methods in the embodiments of the present application, that is to say, the communication device <NUM> according to the embodiments of the present application may correspond to the terminal device <NUM> in the embodiments of the present application, and may correspond to a corresponding subject that executes the method <NUM> according to the embodiments of the present application, which will not be described here for brevity.

Optionally, the communication device <NUM> may be a network device according to an embodiment of the present application, and the communication device <NUM> may implement corresponding processes implemented by the network device in various methods of embodiments of the present application. That is to say, the communication device <NUM> in the embodiments of the present application may correspond to the network device <NUM> in the embodiments of the present application, and may correspond to a corresponding subject that executes the method <NUM> according to the embodiments of the present application, which will not be described here for brevity.

It should be understood that the various components in the communication device <NUM> are connected through a bus system. In addition to a data bus, the bus system further includes a power bus, a control bus, a status signal bus, etc..

In addition, an embodiment of the present application further provides a chip, which may be an integrated circuit chip with a signal processing capability, and can implement or execute the methods, acts and logic block diagrams disclosed in the embodiments of the present application.

Optionally, the chip may be applied to various communication devices, so that the communication devices with the chip installed therein can perform the methods, acts and logic block diagrams disclosed in the embodiments of the present application.

<FIG> is a schematic diagram of a structure of a chip according to an embodiment of the present application.

A chip <NUM> shown in <FIG> includes a processor <NUM>.

The processor <NUM> may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, the chip <NUM> may further include a memory <NUM>.

The processor <NUM> may call and run the computer program from the memory <NUM> to implement the methods in the embodiments of the present application. The memory <NUM> may be configured to store indication information, or may be configured to store codes, instructions, etc., executed by the processor <NUM>.

Optionally, the chip <NUM> may further include an input interface <NUM>.

The processor <NUM> may control the input interface <NUM> to communicate with other devices or chips. Specifically, the processor <NUM> may acquire information or data sent by other devices or chips.

The processor <NUM> may control the output interface <NUM> to communicate with other devices or chips. Specifically, the processor <NUM> may output information or data to other devices or chips.

Optionally, the chip may be applied to the network device in the embodiments of the present application, and the chip may implement the corresponding processes implemented by the network device in various methods in accordance with the embodiments of the present application, which will not be repeated herein for brevity. Optionally, the chip may be applied to the terminal device in the embodiments of the present application, and the chip may implement the corresponding processes implemented by the terminal device in various methods in accordance with the embodiments of the present application, which will not be repeated herein for brevity.

It should be understood that the chip mentioned in the embodiments of the present application may be referred to as a system-level chip, a system chip, a chip system or a system-on-chip, etc. It should also be understood that, various components in the chip <NUM> are connected through a bus system, herein, in addition to a data bus, the bus system further includes a power bus, a control bus and a state signal bus.

The processor may include, but is not limited to, a general purpose processor, a Digital Signal Processing (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or another programmable logic device, a discrete gate or a transistor logic device, or a discrete hardware component, etc..

The processor may be configured to implement or perform methods, acts and logical block diagrams disclosed in the embodiments of the present application. The acts of the methods disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or may be implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium commonly used in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads information in the memory and completes the acts of the foregoing methods in combination with its hardware.

The memory includes but is not limited to, a volatile memory and/or nonvolatile memory. The non-volatile memory may be a Read-Only Memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. Through an exemplary but not limitative description, many forms of RAMs may be used, for example, a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDRSDRAM), an Enhanced SDRAM (ESDRAM), a Synchlink DRAM (SLDRAM), and a Direct Rambus RAM (DRRAM).

It should be noted that the memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memories.

An embodiment of the present application further provides a computer readable storage medium, configured to store a computer program. The computer readable storage medium stores one or more programs including instructions that, when executed by a portable electronic device including multiple application programs, enable the portable electronic device to perform the method of an embodiment shown for the method <NUM>.

Optionally, the computer readable storage medium may be applied to a network device in an embodiment of the present application, and the computer program enables a computer to perform the corresponding processes implemented by the network device in various methods of the embodiments of the present application, which will not be repeated here for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in an embodiment of the present application, and the computer program enables a computer to perform the corresponding processes implemented by the mobile terminal/terminal device in various methods of the embodiments of the present application, which will not be repeated here for brevity.

An embodiment of the present application further provides a computer program product, including a computer program.

Optionally, the computer program product may be applied in the network device of the embodiment of the present application, and the computer program enables the computer to perform the corresponding processes implemented by the network device in various methods of embodiments of the present application, which is not repeated here again for the sake of brevity.

Optionally, the computer program product may be applied in the mobile terminal/terminal device of the embodiment of the present application, and the computer program enables the computer to perform the corresponding processes implemented by the mobile terminal/terminal device in various methods of embodiments of the present application, which is not repeated here again for the sake of brevity.

An embodiment of the present application further provides a computer program. When the computer program is executed by a computer, the computer is enabled to execute the method of an embodiment shown for the method <NUM>.

Optionally, the computer program may be applied to the network device in the embodiments of the present application, and the computer program, when running on a computer, enables the computer to perform the corresponding processes implemented by the network device in various methods of the embodiments of the present application, which will not be repeated herein for brevity.

An embodiment of the present application also provides a communication system, which may include the terminal device <NUM> as shown in <FIG> and the network device <NUM> as shown in <FIG>. Herein, the terminal device <NUM> may be configured to implement the corresponding functions implemented by the terminal device in the above-mentioned method <NUM>, and the network device <NUM> may be configured to implement the corresponding functions implemented by the network device in the above-mentioned method <NUM>, and this will not be repeated here for brevity.

For example, the singular forms "a", "said", "the above" and "the" used in the embodiments of the present application and the appended claims are also intended to include the plural forms unless the context clearly indicates other meanings.

Those skilled in the art may recognize that the exemplary elements and algorithm acts described in combination with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions in respect to each particular application, but such realization should not be considered to be beyond the scope of embodiments of the present application.

The function units may be stored in a computer readable storage medium if realized in a form of software functional units and sold or used as a separate product. Based on this understanding, the technical solution of embodiments of the present application, in essence, or the part contributing to the existing art, or a part of the technical solution, may be embodied in a form of a software product. The computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which may be a personal computer, a server, or a network device, or the like. ) to perform all or part of the acts of the methods described in various embodiments of the present application. And the aforementioned storage medium includes various kinds of media that may store program codes, such as a USB flash disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, etc..

Those skilled in the art may clearly understand that for the sake of convenience and conciseness of description, the specific working processes of the systems, devices and units described above may refer to the corresponding processes in the above method embodiments, and will not be repeated herein.

In several embodiments provided by the present application, it should be understood that the disclosed systems, devices and methods may be implemented in another mode.

For example, the division of the units, modules or components in the above-mentioned device embodiments is only a logical function division, and there may be another division mode in an actual realization. For example, multiple units, modules or components may be combined or integrated into another system, or some units or components may be ignored or not executed.

For another example, the units/modules/components described above as separate/display components may or may not be physically separated, i.e., they may be located in one place or may be distributed over multiple network units. Part or all of the units/modules/components therein may be selected according to an actual requirement to achieve a purpose of the embodiments of the present application.

Finally, it should be noted that the mutual coupling or direct coupling or communication connection shown or discussed in the above may be indirect coupling or communication connection through some interfaces, apparatuses or units, and may be in electrical, mechanical or other forms.

Claim 1:
A method for determining a Hybrid Automatic Repeat reQuest, HARQ, codebook, configured to operate in a New Radio, NR, system, comprising:
receiving, by a terminal device from a network device, first Downlink Control Information, DCI, wherein the first DCI is used for scheduling a first Physical Downlink Shared Channel, PDSCH, the first PDSCH belongs to a first channel group in a plurality of channel groups, the first DCI comprises first indication information and valid HARQ timing indicator information, wherein the first indication information is used for indicating whether feeding back is triggered for a channel group except the first channel group in the plurality of channel groups; wherein the channel groups are PDSCH channel groups;
determining (S220), by the terminal device, first uplink resource based on the valid HARQ timing indicator information;
determining (S230), by the terminal device, a first HARQ codebook corresponding to the plurality of channel groups for the first uplink resource; and
sending (S240), by the terminal device, the first HARQ codebook to the network device;
wherein the quantity of the plurality of channel groups is predefined;
wherein Downlink assignment indexes, DAIs, that correspond to the PDSCHs in the plurality of channel groups are counted consecutively;
wherein when a first DAI corresponding to the first PDSCH in the first channel group is not an initial value, information of a starting position of the first HARQ codebook is placeholder information; wherein the placeholder information is NACK information, or a position corresponding to the placeholder information is not used for placing the codebook; wherein the information of the first HARQ codebook between the starting position and a position corresponding to the first DAI is the placeholder information, wherein the position corresponding to the first DAI is a position, determined based on a count of the first DAI, in the first HARQ codebook.