Method and apparatus for determining hybrid automatic repeat request acknowledgment codebook, and device thereof
View Patent ↗The present disclosure is related to a HARQ-ACK codebook determination method. The method includes receiving trigger information sent by a network device, wherein the trigger information is used to indicate the user equipment to perform One-Shot HARQ-ACK feedback; and according to data scheduling information corresponding to a target Transport Block (TB) in a target HARQ process, determining HARQ-ACK information for the target TB in the target HARQ process in a Type-3 HARQ-ACK codebook. The Type-3 HARQ-ACK codebook includes HARQ-ACK information corresponding to all HARQ processes on all configured carriers in a PUCCH group.
1. A Hybrid Automatic Repeat-reQuest-Acknowledge (HARQ-ACK) codebook determination method, applied to user equipment, wherein the method comprises:
receiving trigger information sent by a network device, wherein the trigger information is used to indicate the user equipment to perform One-Shot HARQ-ACK feedback; and
according to data scheduling information corresponding to a target Transport Block (TB) in a target HARQ process, determining HARQ-ACK information for the target TB in the target HARQ process in a Type-3 HARQ-ACK codebook, wherein the Type-3 HARQ-ACK codebook comprises HARQ-ACK information corresponding to all HARQ processes on all configured carriers in a Physical Uplink Control Channel (PUCCH) group;
wherein the data scheduling information corresponding to the target TB comprises one of first information, and third information, wherein:
the first information comprises: information that the target TB is currently scheduled for new transmission; and
the third information comprises: information that the target TB is not currently scheduled;
wherein determining the HARQ-ACK information for the target TB in the target HARQ process in the Type-3 HARQ-ACK codebook according to the data scheduling information corresponding to the target TB in the target HARQ process, comprises:
for the target TB in the target HARQ process, in response to the user equipment having reported ACK/NACK and the data scheduling information corresponding to the target TB being the third information, determining, by the user equipment, that the HARQ-ACK information for the target TB is NACK.
2. The method according to claim 1 , wherein the information that the target TB is not currently scheduled comprises that:
the user equipment has not received DCI comprises scheduling information for the target TB in the target HARQ process; or, the user equipment does not receive SPS PDSCH corresponding to the target TB in the target HARQ process.
3. The method according to claim 1 , wherein:
the information that the target TB is currently scheduled for new transmission comprises that: current NDI information for the target TB has a value different from last NDI information, or the target TB is a TB in Semi-Persistent Scheduling (SPS) PDSCH; and/or,
the information that the target TB is currently scheduled for retransmission comprises that: the current NDI information for the target TB has a value the same as the last NDI information, or the target TB is the TB in the SPS PDSCH and the value of the NDI information is 1; and/or,
the information that the target TB is not currently scheduled comprises that: the target TB does not currently correspond to NDI information, or the target TB does not currently correspond to NDI information and is not the TB in the SPS PDSCH.
4. The method according to claim 1 , wherein determining the HARQ-ACK information for the target TB in the target HARQ process in the Type-3 HARQ-ACK codebook according to the data scheduling information corresponding to the target TB in the target HARQ process, further comprises:
for the target TB in the target HARQ process, in response to the user equipment having reported ACK/NACK and the data scheduling information corresponding to the target TB being the first information, determining, by the user equipment, that the HARQ-ACK information for the target TB is a decoding result.
5. The method according to claim 1 , wherein determining the HARQ-ACK information for the target TB in the target HARQ process in the Type-3 HARQ-ACK codebook, comprises:
determining a bit length of the HARQ-ACK information for the target TB according to a Code Block Group (CBG) feedback length; or,
determining the bit length of the HARQ-ACK information for the target TB according to a TB feedback length.
6. The method according to claim 5 , wherein in response to the user equipment being configured to feed back One-Shot HARQ-ACK information based on CBG, and a target cell corresponding to the target HARQ process being configured with the CBG feedback length, the bit length of the HARQ-ACK information for the target TB is determined according to the CBG feedback length; otherwise, the bit length of the HARQ-ACK information for the target TB is determined according to the TB feedback length.
7. The method according to claim 1 , wherein the trigger information comprises Downlink Control Information (DCI) sent by the network device to the user equipment.
8. A user equipment, comprising a processor, a transceiver, memory and instructions stored in the memory that, when executed by the processor, cause the user equipment to:
receive trigger information sent by a network device, wherein the trigger information is used to indicate the user equipment to perform One-Shot HARQ-ACK feedback; and
according to data scheduling information corresponding to a target Transport Block (TB) in a target HARQ process, determine HARQ-ACK information for the target TB in the target HARQ process in a Type-3 HARQ-ACK codebook, wherein the Type-3 HARQ-ACK codebook comprises HARQ-ACK information corresponding to all HARQ processes on all configured carriers in a Physical Uplink Control Channel (PUCCH) group;
wherein the data scheduling information corresponding to the target TB comprises one of first information, and third information, wherein:
the first information comprises: information that the target TB is currently scheduled for new transmission; and
the third information comprises: information that the target TB is not currently scheduled;
wherein when the instructions are executed by the processor, the user equipment is caused to:
for the target TB in the target HARQ process, in response to the user equipment having reported ACK/NACK and the data scheduling information corresponding to the target TB being the third information, determine that the HARQ-ACK information for the target TB is NACK.
9. The user equipment according to claim 8 , wherein the information that the target TB is not currently scheduled comprises that:
the user equipment has not received DCI comprises scheduling information for the target TB in the target HARQ process; or, the user equipment does not receive SPS PDSCH corresponding to the target TB in the target HARQ process.
10. The user equipment according to claim 8 , wherein:
the information that the target TB is currently scheduled for new transmission comprises that: current NDI information for the target TB has a value different from last NDI information, or the target TB is a TB in Semi-Persistent Scheduling (SPS) PDSCH; or,
the information that the target TB is currently scheduled for retransmission comprises that: the current NDI information for the target TB has a value the same as the last NDI information, or the target TB is the TB in the SPS PDSCH and the value of the NDI information is 1; and
the information that the target TB is not currently scheduled comprises that: the target TB does not currently correspond to NDI information, or the target TB does not currently correspond to NDI information and is not the TB in the SPS PDSCH.
11. The user equipment according to claim 8 , wherein when the instructions stored in the memory are executed by the processor, the user equipment is further caused to:
for the target TB in the target HARQ process, in response to the user equipment having reported ACK/NACK and the data scheduling information corresponding to the target TB being the first information, determine that the HARQ-ACK information for the target TB is a decoding result.
12. The user equipment according to claim 8 , wherein when the instructions stored in the memory are executed by the processor, the user equipment is caused to:
determine a bit length of the HARQ-ACK information for the target TB according to a Code Block Group (CBG) feedback length; or,
determine the bit length of the HARQ-ACK information for the target TB according to a TB feedback length.
13. The user equipment according to claim 12 , wherein when the instructions stored in the memory are executed by the processor, the user equipment is caused to: in response to the user equipment being configured to feed back One-Shot HARQ-ACK information based on CBG, and a target cell corresponding to the target HARQ process being configured with the CBG feedback length, determine the bit length of the HARQ-ACK information for the target TB according to the CBG feedback length; otherwise, determine the bit length of the HARQ-ACK information for the target TB according to the TB feedback length.
14. The user equipment according to claim 8 , wherein the trigger information comprises Downlink Control Information (DCI) sent by the network device to the user equipment.
15. A network device, comprising a processor, a transceiver, memory and instructions stored in the memory that, when executed by the processor, cause the network device to:
send trigger information to user equipment, wherein the trigger information is used to indicate the user equipment to perform One-Shot HARQ-ACK feedback; and
receive a Type-3 HARQ-ACK codebook which is fed back by the user equipment, wherein the Type-3 HARQ-ACK codebook comprises HARQ-ACK information corresponding to all HARQ processes on all configured carriers in a Physical Uplink Control Channel (PUCCH) group, and HARQ-ACK information for a target Transport Block (TB) in a target HARQ process in the Type-3 HARQ-ACK codebook is determined by the user equipment according to data scheduling information corresponding to the target TB in the target HARQ process, wherein for the target TB in the target HARQ process, in response to the user equipment having reported ACK/NACK and the data scheduling information corresponding to the target TB being the third information, it is determined by the user equipment that the HARQ-ACK information for the target TB is NACK;
wherein the data scheduling information corresponding to the target TB comprises one of first information, and third information, wherein:
the first information comprises: information that the target TB is currently scheduled for new transmission; and
the third information comprises: information that the target TB is not currently scheduled.
16. The network device according to claim 15 , wherein the information that the target TB is not currently scheduled comprises that:
the user equipment has not received DCI comprises scheduling information for the target TB in the target HARQ process; or, the user equipment does not receive SPS PDSCH corresponding to the target TB in the target HARQ process.
17. The network device according to claim 15 , wherein:
the information that the target TB is currently scheduled for new transmission comprises that: current NDI information for the target TB has a value different from last NDI information, or the target TB is a TB in Semi-Persistent Scheduling (SPS) PDSCH; or,
the information that the target TB is currently scheduled for retransmission comprises that: the current NDI information for the target TB has a value the same as the last NDI information, or the target TB is the TB in the SPS PDSCH and the value of the NDI information is 1;
the information that the target TB is not currently scheduled comprises that: the target TB does not currently correspond to NDI information, or the target TB does not currently correspond to NDI information and is not the TB in the SPS PDSCH.
18. The network device according to claim 15 , wherein the trigger information comprises Downlink Control Information (DCI) sent by the network device to the user equipment.