Uplink control information transmission method, receiving method, terminal and network equipment

Abstract

The present invention provides an uplink control information transmission method, a reception method, a terminal, and a network device. The method includes: a terminal receiving a first direct information communication (DCI), wherein a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second HARQ-ACK, whether the second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK; the terminal transmitting the HARQ-ACK based on the first indication field; wherein the first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK. This embodiment of the present invention can ensure that the terminal and the network device have a consistent understanding of the number of bits of the HARQ-ACK transmitted by the terminal.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to an uplink control information transmission method, a receiving method, a terminal and a network device. Background Art

[0002] In some communication systems (e.g., 5G systems), a terminal may need to transmit multiple Hybrid Automatic Repeat Request-ACK acknowledgements (HARQ-ACKs). When a terminal transmits multiple HARQ-ACK codebooks on the same channel, some HARQ-ACK codebooks (e.g., low-priority HARQ-ACK codebooks) may experience packet loss due to poor transmission performance, resulting in an unstable number of bits in the HARQ-ACK codebook. This may cause the terminal and the network device to have inconsistent understandings of the number of HARQ-ACK bits transmitted by the terminal. Summary of the Invention

[0003] Embodiments of the present invention provide an uplink control information transmission method, a receiving method, a terminal, and a network device to solve the problem of inconsistent understanding of the number of bits of HARQ-ACK transmitted by the terminal by the terminal and the network device.

[0004] An embodiment of the present invention provides a method for transmitting uplink control information, including:

[0005] The terminal receives first downlink control information (Downlink Control Information, DCI), where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0006] The terminal performs HARQ-ACK transmission according to the first indication field;

[0007] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0008] Optionally, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0009] Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or

[0010] The first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or

[0011] The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

[0012] Optionally, the information used to determine the total number of bits of the second HARQ-ACK includes:

[0013] The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

[0014] Optionally, when the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK:

[0015] In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

[0016] Optionally, when the second HARQ-ACK uses a semi-static HARQ-ACK codebook:

[0017] The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0018] The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0019] The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under the first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and under the second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size. the number of bits of the second HARQ-ACK; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or to indicate that the number of bits of the second HARQ-ACK is determined according to the fallback mode, the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that there is no second HARQ-ACK, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or

[0020] The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

[0021] Optionally, the first condition includes:

[0022] There is downlink transmission corresponding to the second HARQ-ACK; or

[0023] There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0024] The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK;

[0025] The second condition includes:

[0026] There is no downlink transmission corresponding to the second HARQ-ACK; or

[0027] There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0028] The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0029] Optionally, in the case where each indication status indication of the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

[0030] Optionally, when the first indication field includes the third indication state and the fourth indication state, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

[0031] Optionally, the terminal performing HARQ-ACK transmission according to the first indication field includes:

[0032] Determining, by the terminal, the number of bits of the second HARQ-ACK according to the first indication field;

[0033] The terminal performs HARQ-ACK transmission according to the number of bits of the second HARQ-ACK.

[0034] Optionally, the terminal performing HARQ-ACK transmission according to the number of bits of the second HARQ-ACK includes:

[0035] transmitting the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or,

[0036] When the number of bits of the second HARQ-ACK is greater than 0 or it is determined to transmit the second HARQ-ACK, simultaneously transmit the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or

[0037] When the number of bits of the second HARQ-ACK is 0 or it is determined not to transmit the second HARQ-ACK, the first HARQ-ACK is transmitted on the first uplink channel.

[0038] Optionally, the terminal determines, according to the first indication field, the number of bits of the second HARQ-ACK, including:

[0039] When a first uplink channel carrying the first HARQ-ACK overlaps with a second uplink channel carrying the second HARQ-ACK in the time domain, the terminal determines the number of bits of the second HARQ-ACK according to the first indication field.

[0040] Optionally, the priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK; or

[0041] The priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or

[0042] The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

[0043] Optionally, the first uplink channel is one of a physical uplink control channel (Physical Uplink Control Channel, PUCCH) and a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH), the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

[0044] Optionally, whether the first indication field exists in the first DCI is determined according to the configuration of high-layer signaling; or

[0045] By default, the first indication field always exists in the first DCI.

[0046] Optionally, when the first uplink channel is PUCCH, the first DCI is a PDSCH DCI for scheduling HARQ-ACK feedback required on the PUCCH, or the first DCI is a semi-persistent scheduling (Semi-Persistent Scheduling, SPS) physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) release DCI for indicating the need for HARQ-ACK feedback on the PUCCH; or

[0047] In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

[0048] Optionally, when there are multiple first DCIs, the values ​​of the first indication fields in the multiple first DCIs are the same, or the terminal performs HARQ-ACK transmission according to the first indication field in the last DCI.

[0049] An embodiment of the present invention further provides a method for receiving uplink control information, comprising:

[0050] The network device sends a first DCI, where the first indication field of the first DCI is used to determine at least one of the following: the number of bits of the second hybrid automatic repeat request confirmation HARQ-ACK, whether the second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0051] The network device performs HARQ-ACK reception according to the first indication field;

[0052] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0053] Optionally, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0054] Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or

[0055] The first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or

[0056] The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

[0057] Optionally, the information used to determine the total number of bits of the second HARQ-ACK includes:

[0058] The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

[0059] Optionally, when the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK:

[0060] In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

[0061] Optionally, when the second HARQ-ACK uses a semi-static HARQ-ACK codebook:

[0062] The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0063] The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0064] The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under the first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and under the second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size. the number of bits of the second HARQ-ACK; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or to indicate that the number of bits of the second HARQ-ACK is determined according to the fallback mode, the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that there is no second HARQ-ACK, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or

[0065] The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

[0066] Optionally, the first condition includes:

[0067] There is downlink transmission corresponding to the second HARQ-ACK; or

[0068] There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0069] The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK;

[0070] The second condition includes:

[0071] There is no downlink transmission corresponding to the second HARQ-ACK; or

[0072] There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0073] The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0074] Optionally, the network device performs HARQ-ACK reception according to the first indication field, including:

[0075] Determining, by the network device, the number of bits of the second HARQ-ACK according to the first indication field;

[0076] The network device receives HARQ-ACK according to the number of bits of the second HARQ-ACK.

[0077] Optionally, the network device performing HARQ-ACK reception according to the number of bits of the second HARQ-ACK includes:

[0078] receiving the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or,

[0079] When the number of bits of the second HARQ-ACK is greater than 0 or it is determined that the terminal transmits the second HARQ-ACK, simultaneously receiving the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or

[0080] When the number of bits of the second HARQ-ACK is 0 or it is determined that the terminal does not transmit the second HARQ-ACK, the first HARQ-ACK is received on the first uplink channel.

[0081] Optionally, the network device determines, according to the first indication field, the number of bits of the second HARQ-ACK, including:

[0082] When the first uplink channel carrying the first HARQ-ACK and the second uplink channel carrying the second HARQ-ACK overlap in the time domain, the network device determines the number of bits of the second HARQ-ACK according to the first indication field.

[0083] Optionally, the priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK; or

[0084] The priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or

[0085] The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

[0086] Optionally, the first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

[0087] Optionally, whether the first indication field exists in the first DCI is determined according to the configuration of high-layer signaling; or

[0088] By default, the first indication field always exists in the first DCI.

[0089] Optionally, when the first uplink channel is a PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or

[0090] In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

[0091] Optionally, when there are multiple first DCIs, the values ​​of the first indication fields in the multiple first DCIs are the same, or the terminal performs HARQ-ACK transmission according to the first indication field in the last DCI.

[0092] An embodiment of the present invention further provides a terminal, including a memory, a transceiver, and a processor:

[0093] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0094] receiving a first DCI, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0095] Performing HARQ-ACK transmission according to the first indication field;

[0096] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0097] Optionally, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0098] Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or

[0099] The first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or

[0100] The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

[0101] Optionally, the information used to determine the total number of bits of the second HARQ-ACK includes:

[0102] The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

[0103] Optionally, when the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK:

[0104] In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

[0105] Optionally, when the second HARQ-ACK uses a semi-static HARQ-ACK codebook:

[0106] The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0107] The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0108] The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under the first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and under the second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size. the number of bits of the second HARQ-ACK; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or to indicate that the number of bits of the second HARQ-ACK is determined according to the fallback mode, the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that there is no second HARQ-ACK, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or

[0109] The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

[0110] Optionally, the first condition includes:

[0111] There is downlink transmission corresponding to the second HARQ-ACK; or

[0112] There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0113] The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK;

[0114] The second condition includes:

[0115] There is no downlink transmission corresponding to the second HARQ-ACK; or

[0116] There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0117] The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0118] Optionally, in the case where each indication status indication of the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

[0119] Optionally, when the first indication field includes the third indication state and the fourth indication state, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

[0120] Optionally, the performing HARQ-ACK transmission according to the first indication field includes:

[0121] Determining, according to the first indication field, a number of bits of the second HARQ-ACK;

[0122] Perform HARQ-ACK transmission according to the number of bits of the second HARQ-ACK.

[0123] Optionally, the performing HARQ-ACK transmission according to the number of bits of the second HARQ-ACK includes:

[0124] transmitting the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or,

[0125] When the number of bits of the second HARQ-ACK is greater than 0 or it is determined to transmit the second HARQ-ACK, simultaneously transmit the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or

[0126] When the number of bits of the second HARQ-ACK is 0 or it is determined not to transmit the second HARQ-ACK, the first HARQ-ACK is transmitted on the first uplink channel.

[0127] Optionally, determining the number of bits of the second HARQ-ACK according to the first indication field includes:

[0128] When the first uplink channel carrying the first HARQ-ACK overlaps with the second uplink channel carrying the second HARQ-ACK in the time domain, the number of bits of the second HARQ-ACK is determined according to the first indication field.

[0129] Optionally, the priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK; or

[0130] The priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or

[0131] The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

[0132] Optionally, the first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

[0133] Optionally, whether the first indication field exists in the first DCI is determined according to the configuration of high-layer signaling; or

[0134] By default, the first indication field always exists in the first DCI.

[0135] Optionally, when the first uplink channel is a PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or

[0136] In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

[0137] Optionally, when there are multiple first DCIs, the values ​​of the first indication fields in the multiple first DCIs are the same, or the terminal performs HARQ-ACK transmission according to the first indication field in the last DCI.

[0138] An embodiment of the present invention further provides a network device, including a memory, a transceiver, and a processor:

[0139] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0140] Sending a first DCI, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0141] Receiving HARQ-ACK according to the first indication field;

[0142] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0143] Optionally, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0144] Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or

[0145] The first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or

[0146] The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

[0147] Optionally, the information used to determine the total number of bits of the second HARQ-ACK includes:

[0148] The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

[0149] Optionally, when the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK:

[0150] In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

[0151] Optionally, when the second HARQ-ACK uses a semi-static HARQ-ACK codebook:

[0152] The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0153] The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0154] The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under the first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and under the second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size. the number of bits of the second HARQ-ACK; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or to indicate that the number of bits of the second HARQ-ACK is determined according to the fallback mode, the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that there is no second HARQ-ACK, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or

[0155] The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

[0156] Optionally, the first condition includes:

[0157] There is downlink transmission corresponding to the second HARQ-ACK; or

[0158] There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0159] The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK;

[0160] The second condition includes:

[0161] There is no downlink transmission corresponding to the second HARQ-ACK; or

[0162] There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0163] The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0164] Optionally, the receiving HARQ-ACK according to the first indication field includes:

[0165] Determining, according to the first indication field, a number of bits of the second HARQ-ACK;

[0166] HARQ-ACK reception is performed according to the number of bits of the second HARQ-ACK.

[0167] Optionally, the performing HARQ-ACK reception according to the number of bits of the second HARQ-ACK includes:

[0168] receiving the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or,

[0169] When the number of bits of the second HARQ-ACK is greater than 0 or it is determined that the terminal transmits the second HARQ-ACK, simultaneously receiving the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or

[0170] When the number of bits of the second HARQ-ACK is 0 or it is determined that the terminal does not transmit the second HARQ-ACK, the first HARQ-ACK is received on the first uplink channel.

[0171] Optionally, determining the number of bits of the second HARQ-ACK according to the first indication field includes:

[0172] When the first uplink channel carrying the first HARQ-ACK overlaps with the second uplink channel carrying the second HARQ-ACK in the time domain, the number of bits of the second HARQ-ACK is determined according to the first indication field.

[0173] Optionally, the priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK; or

[0174] The priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or

[0175] The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

[0176] Optionally, the first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

[0177] Optionally, whether the first indication field exists in the first DCI is determined according to the configuration of high-layer signaling; or

[0178] By default, the first indication field always exists in the first DCI.

[0179] Optionally, when the first uplink channel is PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a semi-static SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or

[0180] In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

[0181] Optionally, when there are multiple first DCIs, the values ​​of the first indication fields in the multiple first DCIs are the same, or the terminal performs HARQ-ACK transmission according to the first indication field in the last DCI.

[0182] An embodiment of the present invention further provides a terminal, including:

[0183] A receiving unit, configured for a terminal to receive a first DCI, where the first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0184] a transmission unit, configured to perform HARQ-ACK transmission according to the first indication field;

[0185] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0186] An embodiment of the present invention further provides a network device, including:

[0187] A sending unit, configured for a network device to send a first DCI, where the first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0188] a receiving unit, configured to perform HARQ-ACK reception according to the first indication field;

[0189] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0190] An embodiment of the present invention also provides a processor-readable storage medium, which stores a computer program. The computer program is used to enable the processor to execute the uplink control information transmission method provided by the embodiment of the present invention, or the computer program is used to enable the processor to execute the uplink control information receiving method provided by the embodiment of the present invention.

[0191] In an embodiment of the present invention, a terminal receives a first DCI, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK; the terminal transmits HARQ-ACK based on the first indication field; wherein the first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK. In this way, since the terminal transmits HARQ-ACK based on the first indication field, it can ensure that the terminal and the network device have a consistent understanding of the number of bits of the HARQ-ACK transmitted by the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0192] Figure 1 is a schematic diagram of a network architecture applicable to embodiments of the present invention;

[0193] Figure 2 2 is a schematic diagram of a semi-static HARQ-ACK codebook provided by an embodiment of the present invention;

[0194] Figure 3 2 is a schematic diagram of a dynamic HARQ-ACK codebook provided by an embodiment of the present invention;

[0195] Figure 4 This is a flow chart of a method for transmitting uplink control information provided by an embodiment of the present invention;

[0196] Figure 5 This is a flow chart of a method for receiving uplink control information provided by an embodiment of the present invention;

[0197] Figure 6 is a schematic diagram of uplink control information transmission provided by an embodiment of the present invention;

[0198] Figure 7 is a schematic diagram of another uplink control information transmission provided by an embodiment of the present invention;

[0199] Figure 8 is a structural diagram of a terminal provided by an embodiment of the present invention;

[0200] Figure 9 is a structural diagram of a network device provided by an embodiment of the present invention;

[0201] Figure 10 is a structural diagram of another terminal provided by an embodiment of the present invention;

[0202] Figure 11 This is a structural diagram of another network device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0203] In order to make the technical problems, technical solutions and advantages to be solved by the present invention clearer, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0204] In embodiments of the present invention, the term "and / or" describes the association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "and / or" relationship.

[0205] In the embodiments of the present invention, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0206] The following will be combined with the accompanying drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0207] The embodiment of the present invention provides an uplink control information transmission method, a receiving method, a terminal and a network device to solve the problem that the terminal and the network device have inconsistent understanding of the number of bits of HARQ-ACK transmitted by the terminal

[0208] Among them, the method and the device are based on the same application concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0209] The technical solution provided by the embodiment of the present invention can be applicable to a variety of systems, especially 5G systems. For example, applicable systems may be global system of mobile communication (GSM) systems, code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, long term evolution advanced (LTE-A) systems, universal mobile telecommunication systems (UMTS), worldwide interoperability for microwave access (WiMAX) systems, 5G new radio (NR) systems, 6G systems, etc. These various systems include terminal devices and network devices. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0210] See Figure 1 , Figure 1 This is a schematic diagram of the network architecture applicable to the implementation of the present invention. Figure 1 As shown, it includes a terminal 11 and a network device 12.

[0211] The terminal involved in the embodiments of the present invention may refer to a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection capabilities, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called User Equipment (UE). A wireless terminal device can communicate with one or more core networks (CNs) via a radio access network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it can be a portable, pocket-sized, handheld, computer-built-in, or vehicle-mounted mobile device that exchanges voice and / or data with the radio access network. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, or a user device, but is not limited in the embodiments of the present invention.

[0212] The network device involved in the embodiments of the present invention may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application scenario, a base station may also be referred to as an access point, or may be a device in an access network that communicates with wireless terminal devices over the air interface through one or more sectors, or may be referred to by other names. The network device may be used to convert received air frames into Internet Protocol (IP) packets, and may serve as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management of the air interface. For example, the network device involved in the embodiments of the present invention may be a base transceiver station (BTS) in the Global System for Mobile communications (GSM) or code division multiple access (CDMA), a node in wide-band code division multiple access (WCDMA), an evolutionary node B (eNB or e-NodeB) in the long term evolution (LTE) system, a 5G base station (gNB) in the 5G next generation system, a home evolved node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of the present invention. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.

[0213] Network devices and terminals can each use one or more antennas for Multiple Input Multiple Output (MIMO) transmission. MIMO transmission can be either Single User MIMO (SU-MIMO) or Multi User MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or Massive-MIMO. It can also use diversity transmission, precoding, or beamforming.

[0214] In some communication systems (for example, the fifth generation new wireless system (5Generation New RAT, 5G NR)), uplink channel transmission with different physical layer priorities is supported. There may be resource conflicts between uplink channels with different physical layer priorities of the same terminal. For example, on the same carrier, there is overlap between the symbols occupied by uplink channels with different priorities. In order to avoid the problem of increased Peak to Average Power Ratio (PAPR) and power limitation caused by the parallel transmission of multiple uplink channels at the same time on the same carrier, only the channel with a higher physical layer priority in the conflicting channel can be transmitted, and the channel with a lower physical layer priority can be discarded. In an embodiment of the present invention, in order to avoid discarding the uplink control information (UCI) carried on the low-priority channel, it is possible to support the multiplexing of UCI on multiple PUCCHs with different physical layer priorities for transmission on the same channel.

[0215] Among them, channel transmission of different physical layer priorities can be as follows:

[0216] A terminal can support different service types, such as enhanced Mobile Broadband (eMBB) and Ultra-Reliable and Low Latency Communication (URLLC). Different service types have different requirements for reliability and transmission latency. URLLC service flows can occur sporadically and irregularly. Therefore, reserving separate system resources for different services results in significant system resource overhead, and in many cases, the resources reserved for URLLC may go unused. To improve system resource utilization, multiplexing different services on the same resources is supported. It is possible that an earlier scheduled data transmission may be interrupted or canceled by a later scheduled data transmission. For example, after a terminal is scheduled to transmit an eMBB service on Resource 1, a URLLC service arrives. To meet the latency requirements of the URLLC service, this service needs to be scheduled as soon as possible. This may occupy all or part of the resources (including time and / or frequency domain resources) in Resource 1 already allocated for the eMBB service for URLLC transmission. For another example, all or part of the symbols in the time domain resources (symbol set) scheduled for eMBB on the same carrier may be scheduled for URLLC transmission, regardless of whether the frequency domain resources overlap. Because two uplink channels cannot be transmitted simultaneously on the same carrier at the same time, the eMBB service will be interrupted or canceled by the URLLC service.

[0217] To avoid mutual impact between services, different priorities can be defined for different services. Thus, when resource conflicts occur, high-priority channels are selected for transmission, while low-priority channels are discarded. Therefore, to better support the transmission of different services with different requirements, physical layer priorities are introduced in some protocols. When channels with different physical layer priorities conflict, that is, when multiple PUCCHs overlap in the time domain on the same carrier, or when PUCCH and PUSCH overlap in the time domain on the same carrier, the low-priority channel is discarded and only the high-priority channel is transmitted.

[0218] Among them, the physical layer priority of PUCCH and PUSCH can be obtained by default, dynamic indication of DCI or semi-static configuration of Radio Resource Control (RRC). For example, when PUCCH carries a Scheduling Request (SR), its priority is determined by the priority corresponding to the SR it carries, and the priority corresponding to each SR configuration is configured by high-level signaling; when PUCCH carries the HARQ-ACK of SPS PDSCH or carries the HARQ-ACK of the PDCCH indicating the release of SPS resources (i.e., SPS PDSCH release), its priority is determined by the HARQ-ACK codebook number configured for SPS PDSCH by high-level signaling, and the HARQ-ACK codebook corresponding to number 0 is low priority, and the HARQ-ACK codebook corresponding to number 1 is high priority; when PUCCH carries CSI (including periodic CSI and semi-persistent channel state information (semi-persistent CSI)), its priority is determined by the HARQ-ACK codebook number configured for SPS PDSCH by high-level signaling. CSI, SP-CSI), its priority can be defaulted to low priority. When the DCI contains a priority indication field, the priority can be obtained through the priority indication field in the DCI corresponding to PUCCH and PUSCH (or PDCCH, in the embodiment of the present invention, PDCCH and DCI can be considered equivalent, DCI is the specific format used for PDCCH transmission, then having a corresponding DCI is equivalent to having a corresponding PDCCH). For example, the DCI used by PDCCH contains a priority indication field, then: when PDCCH schedules a PDSCH, the priority of the PUCCH carrying the HARQ-ACK of this PDSCH can be indicated through the priority indication field. When PDCCH schedules a PUSCH, the priority of the scheduled PUSCH can be indicated through the priority indication field, wherein the PUSCH includes a PUSCH that only carries a transport block (Transport Block, TB) or a PUSCH that only carries aperiodic channel state information (Aperiodic Channel State Information). For PUSCH carrying SP-CSI, A-CSI, or PUSCH carrying both TB and A-CSI; for PUSCH carrying SP-CSI, its priority can be obtained by activating the priority indication field in the DCI of the PUSCH carrying SP-CSI. If the DCI does not contain a priority indication field, or the higher-layer signaling does not configure the priority, the default priority is low.

[0219] Among them, UCI transmission in 5G NR can be as follows:

[0220] UCI can include information such as HARQ-ACK, CSI, SR, etc. UCI can be transmitted on PUCCH. Among them, HARQ-ACK is a general term for positive acknowledgment (ACK) and negative acknowledgment (NACK), which is used to provide feedback for PDSCH or PDCCH indicating SPS resource release (also known as SPS PDSCH release), informing the network device whether PDSCH or PDCCH indicating SPS PDSCH release is correctly received; CSI is used to feedback downlink channel quality, thereby helping network devices to better perform downlink scheduling, such as selecting the modulation and coding scheme (MCS) and configuring appropriate resource blocks (RB) resources based on CSI; SR is used to request transmission resources for PUSCH carrying uplink services from the network device when the terminal has uplink services to transmit.

[0221] 5G NR systems can support both semi-static and dynamic HARQ-ACK codebook generation methods. The HARQ-ACK codebook can be a HARQ-ACK feedback sequence generated for downlink transmissions (including PDSCH and SPS PDSCH releases) that perform HARQ-ACK feedback at the same time domain location or on the uplink channel.

[0222] The semi-static HARQ-ACK codebook can determine the position set Mc of the downlink transmission corresponding to the HARQ-ACK feedback in a time slot or sub-time slot n on each carrier c (specifically, the currently activated BWP on this carrier) according to each value in the K1 set representing the HARQ-ACK feedback timing, and then the HARQ-ACK codebook transmitted in the time slot or sub-time slot n can be determined according to Mc. Figure 2As shown, assuming that the K1 set is {2, 3, 4, 5, 6, 7, 8, 9}, where the time slots configured for uplink transmission are not included, then assuming that only a maximum of one PDSCH is transmitted in each time slot and the PDSCH only contains 1TB, it can be determined that the codebook size in time slot n+9 is 6 bits (if multiple PDSCHs can be transmitted in a time slot using time division multiplexing (TDM), multiple bits of HARQ-ACK positions can be reserved in each time slot. If a PDSCH contains multiple TBs or is configured for code block group (CBG) transmission, each PDSCH can correspond to more bits of HARQ-ACK, thereby changing the codebook size in time slot n+9). The advantage of a semi-static HARQ-ACK codebook is that it can relatively stably ensure that the terminal and network equipment have a consistent understanding of the codebook size. However, the overhead of the semi-static HARQ-ACK codebook is relatively large. Even if only a few transmissions are scheduled in the downlink transmission position set Mc, feedback needs to be based on the maximum range. In order to reduce the feedback overhead, a fallback method of a semi-static HARQ-ACK codebook is proposed. That is, if only one downlink transmission is scheduled using fallback DCI (such as DCI format 1-0) within the Mc range, and the downlink assignment index (DAI) field in the DCI is indicated as "1", when only one SPSPDSCH is received, only 1-bit HARQ-ACK is generated for the received downlink transmission for transmission, and there is no need to generate a fixed-size HARQ-ACK codebook determined by the K1 set.

[0223] The dynamic HARQ-ACK codebook can perform HARQ-ACK sorting according to the indication of the cumulative downlink assignment index (Counter-Downlink Assignment Index, C-DAI) field in the DCI for scheduling downlink transmission, and determine the total number of bits of the HARQ-ACK codebook according to the total downlink assignment index (Total-Downlink Assignment Index, T-DAI) field. Therefore, the size of the HARQ-ACK codebook can be dynamically adjusted according to the actual scheduling at different feedback times, thereby saving HARQ-ACK feedback overhead. Specifically, the PDCCH monitoring opportunity (MO) corresponding to the activated BWP on a carrier can be determined first according to K1, K0 (the time slot interval between the PDCCH and the PDSCH scheduled by it, that is, the scheduling timing) and the configured number of repeated transmissions (if configured). If there are multiple carriers, the PDCCH MOs on different carriers may not be aligned in time. The PDCCH MOs on multiple carriers are sorted in chronological order to form a large PDCCH MO set, one of which contains MOs with time domain overlap on multiple carriers; in this PDCCH MO set, C-DAI indicates the cumulative number of PDSCHs that have been transmitted by the current PDCCH MO on the current carrier or the PDCCHs released by the SPS PDSCH in the order of frequency domain first and time domain later, and T-DAI indicates the total number of PDSCHs transmitted by the current PDCCH MO on all carriers or the PDCCHs released by the SPS The number of PDCCHs released by PDSCH. When the network device sends DCI to schedule PDSCH transmission, it ensures that C-DAI is counted cumulatively in the DCI on different carriers in the same MO in the order of frequency domain. T-DAI has the same value in all DCIs in the same MO, indicating the total number of DCIs scheduled in all frequency domains in this MO. Figure 3 As shown, assuming that both C-DAI and T-DAI are 2 bits, one indication state of 2 bits can be multiplexed to indicate 1, 5, 9..., one state can be multiplexed to indicate 2, 6, 10..., one state can be multiplexed to indicate 3, 7, 11..., and one state can be multiplexed to indicate 4, 8, 12... The terminal detects the PDCCH using a certain DCI format (such as one or more of format 1-0, format 1-1, and format 1-2) in the determined PDCCH MO set, and generates a HARQ-ACK codebook based on the DAI information (including C-DAI and T-DAI) in the received PDCCH. The terminal generates a HARQ-ACK codebook based on the DAI information (including C-DAI and T-DAI) in the received PDCCH. Figure 3The scheduling of T-DAI in the last DCI can determine that the total number of bits is 6 (assuming that 1 PDSCH corresponding to each DAI count corresponds to only 1 bit HARQ-ACK, and if one PDSCH corresponds to A bits HARQ-ACK, then here is 6*A bits).

[0224] The overlap of PUCCH and PUCCH / PUSCH of the same priority can be as follows:

[0225] NR does not support the simultaneous transmission of PUCCH and PUSCH at the same time, whether on the same carrier or different carriers. When PUCCH and PUSCH (unless otherwise specified, PUCCH and PUSCH generally refer to PUCCH and PUSCH without repeated transmission) overlap in time domain resources, if the predetermined timeline is met, UCI (generally HARQ-ACK and CSI) can be transferred from PUCCH to a PUSCH for transmission. If an SR exists, it is not transmitted on the PUSCH and is discarded. If there are multiple PUSCHs overlapping with PUCCH, a PUSCH is selected according to the predetermined rules, among which the PUSCH carrying A-CSI is given priority. If there are PUSCHs with PDCCH scheduling (DG PUSCH) and PUSCHs without PDCCH scheduling (CG PUSCH, SP-CSI PUSCH, etc.), DG PUSCH is given priority. After selecting according to the above rules, if there are PUSCHs on multiple carriers, the PUSCH on the carrier with a lower carrier number can be given priority. If there are multiple PUSCHs that do not overlap in the time domain on the selected carrier and overlap with PUCCH, the earliest PUSCH can be given priority.

[0226] Among them, the definition of timeline can be: if PUCCH or PUSCH has a corresponding PDCCH (for example, the HARQ-ACK carried by PUCCH is the HARQ-ACK of PDSCH with PDCCH scheduling or the HARQ-ACK of PDCCH indicating the release of downlink SPS resources), then the PDCCH that schedules PDSCH or the PDCCH that indicates the release of downlink SPS resources is the PDCCH corresponding to PUCCH (or it can also be called the PDCCH that schedules PUCCH), and the PDCCH that schedules PUSCH is the PDCCH corresponding to PUSCH. The first symbol of the channel with the earliest starting time in the overlapping PUCCH and PUSCH is used as the target symbol. If there are multiple channels with the same starting time, one channel is randomly selected and its first symbol is used as the target symbol. The target symbol needs to meet the following timeline to be multiplexed and transmitted, otherwise it is considered to be incorrectly scheduled.

[0227] Timeline1: The target symbol is no earlier than the first symbol (including CP) after the T1mux time after the last symbol of any PDSCH or SPS PDSCH release that requires HARQ-ACK feedback on the PUCCH, that is, the time interval between the target symbol and the last symbol of any of the above PDSCH or SPS PDSCH releases is no less than T1mux time. Among them, T1mux is related to the processing delay of PDSCH and can be calculated according to a predetermined formula and related parameters. The purpose of this timeline is to ensure that the acquisition and preparation of HARQ-ACK can be completed before the transmission of the channel for finally transmitting HARQ-ACK begins.

[0228] Timeline 2: The target symbol is no earlier than the first symbol (including the CP) after the T2mux time following the last symbol of any PDCCH (including the PDCCH indicating the SPS PDSCH release) scheduling the PDSCH (if any) and PUSCH (if any). That is, the time interval between the target symbol and the last symbol of any of the above PDCCHs is no less than T2mux time. T2mux is related to the PUSCH processing delay and can be calculated according to a predetermined formula and related parameters. The purpose of this timeline is to ensure that when UCI needs to be transferred to PUSCH for transmission, the PDCCH scheduling PUSCH can be obtained before PUCCH preparation begins, thereby determining that UCI transmission preparation on PUCCH is not required. In addition, transmission preparation including UCI can be completed before PUSCH transmission, that is, UCI acquisition and multiplexing processing are completed, and TB preparation (such as coding, modulation, scrambling, etc.) is completed. If multiple PUCCHs are multiplexed, this T2mux is used to simulate the preparation time for multiplexing CSI and SR with HARQ-ACK.

[0229] If the HARQ-ACK carried by the PUCCH does not have a corresponding PDCCH (i.e., the HARQ-ACK is the HARQ-ACK of the SPS PDSCH), there is no PDCCH scheduling the PDSCH. If there is no PUSCH or the PUSCH does not have a corresponding PDCCH, then only T1mux needs to be checked without T2mux. If CSI and / or SR are carried on the PUCCH, there is no need to check T1mux because there is no corresponding PDSCH. Furthermore, if there is no PUSCH or the PUSCH does not have a corresponding PDCCH, there is no need to check T2mux.

[0230] If PUCCH and PUSCH overlap, and at least one PUCCH is repeated (i.e., occupies multiple time slots and repeatedly transmits UCI in each time slot), only the overlapping repetitions are treated as having a higher priority, and the lower priority is discarded, without affecting the non-overlapping repetitions. If PUCCH and repeated PUSCH overlap, when PUSCH uses time slot-based repetition (R15 repetition, or protocol-defined repetition type A), the UCI carried by the PUCCH is transferred to one or more PUSCH time slots that overlap with the PUCCH for transmission; when PUSCH uses protocol-defined repetition type B, the UCI carried by the PUCCH is transferred to the earliest actual repetition PUSCH that overlaps with the PUCCH and contains more than one symbol (the actual repetition is the repetition PUSCH obtained by segmenting based on unavailable symbols, DL symbols, time slot boundaries, etc.); the one or more PUSCH repetitions that overlap with the PUCCH must meet the multiplexing timeline. If the multi-slot PUCCH overlaps with the single-slot or multi-slot PUSCH, the PUSCH that overlaps with the PUCCH is discarded to ensure that the repeated transmission of the PUCCH is not interrupted.

[0231] It should be noted that the above is merely an example of the features adopted in the embodiment of the present invention, and does not limit the solutions protected by the embodiment of the present invention.

[0232] See Figure 4 , Figure 4 This is a flow chart of a method for transmitting uplink control information provided by an embodiment of the present invention. Figure 4 As shown, the following steps are included:

[0233] Step 401: The terminal receives a first DCI, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK.

[0234] Step 402: The terminal performs HARQ-ACK transmission according to the first indication field;

[0235] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0236] The above-mentioned receiving the first DCI may be receiving DCI sent by a network device, and the network device may send one or more DCIs, and the terminal may receive one or more DCIs. In the case of receiving multiple first DCIs, the terminal may perform HARQ-ACK transmission based on the first indication field in some or all of the multiple first DCIs.

[0237] The first indication field of the first DCI may be one or more bit fields in the first DCI. In an optional embodiment, the first indication field is a reuse of existing bits in the first DCI, or the first indication field is a newly added bit in the first DCI. The existing bits in the first DCI may be bits in the first DCI already defined in the protocol, and the newly added bits in the first DCI are one or more bits added to the DCI already defined in the protocol.

[0238] The above-mentioned first indication field is used to determine the number of bits of the second HARQ-ACK. The first indication field may be information indicating the total number of bits of the second HARQ-ACK, such as the total number of bits of the second HARQ-ACK (for example, 0, 1, 2, 4, etc. bits), or indicating the total number of downlink transmissions corresponding to the second HARQ-ACK; wherein the downlink transmission corresponding to the second HARQ-ACK specifically includes a PDSCH or SPS PDSCH release for which second HARQ-ACK feedback is required.

[0239] Whether the second HARQ-ACK exists may refer to whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK.

[0240] It should be noted that, when the first indication field does not indicate whether the second HARQ-ACK exists, it can be determined whether the second HARQ-ACK exists based on the information of the number of bits of the second HARQ-ACK, such as 0 bits, it does not exist, and non-0 bits exist; when the first indication field does not indicate whether the second HARQ-ACK is multiplexed with the first HARQ-ACK, it can be determined whether the second HARQ-ACK is multiplexed with the first HARQ-ACK based on at least one of the information of the number of bits of the second HARQ-ACK and whether the second HARQ-ACK exists. If the second HARQ-ACK exists, it can be confirmed that the second HARQ-ACK is multiplexed with the first HARQ-ACK, otherwise it is confirmed that the second HARQ-ACK is not multiplexed with the first HARQ-ACK. If the number of bits of the second HARQ-ACK is 0, it can be confirmed that the second HARQ-ACK is not multiplexed with the first HARQ-ACK, otherwise it is confirmed that the second HARQ-ACK is multiplexed with the first HARQ-ACK.

[0241] The above-mentioned terminal may perform HARQ-ACK transmission according to the first indication field, which may be to transmit the first HARQ-ACK or transmit the first HARQ-ACK and the second HARQ-ACK according to at least one of the number of bits of the second HARQ-ACK, whether the second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed with the first HARQ-ACK.

[0242] In an embodiment of the present invention, the above steps can be used to determine the number of bits of the second HARQ-ACK transmitted simultaneously with the first HARQ-ACK based on the first indication field of the first DCI, thereby performing HARQ-ACK transmission. In this way, the network device can perform corresponding HARQ-ACK reception based on the first indication field of the first DCI, thereby ensuring that the terminal and the network device have a consistent understanding of the number of bits of the HARQ-ACK transmitted by the terminal.

[0243] As an optional implementation, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0244] Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or

[0245] The first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or

[0246] The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

[0247] The information for determining the total number of bits of the second HARQ-ACK may determine that the total number of bits of the second HARQ-ACK is 0 or a number of bits greater than 0.

[0248] Each indication state indication of the above-mentioned first indication field corresponds to a type of information for determining the total number of bits of the second HARQ-ACK, which may be that the first indication field can determine different total numbers of bits of the second HARQ-ACK through different indication states. Of course, some implementations allow a part of the indication states to correspond to the total number of bits of the same second HARQ-ACK. For example: the first indication field has 3 bits of indication information, which can indicate 8 indication states, but the possible total number of bits of the second HARQ-ACK is 1-7, then 2 of the 8 indication states may correspond to the total number of bits of the same second HARQ-ACK, or one of the indication states may be reserved. Some embodiments allow a certain indication state to correspond to the total number of bits of multiple second HARQ-ACKs. For example, the first indication field has 2 bits of indication information, which can indicate 4 indication states, but the possible value of the total number of bits of the second HARQ-ACK is 0-4. Then, among these 4 indication states, there can be 1 indication state corresponding to the two total bit numbers of 0 bits and 4 bits. The number of downlink transmissions corresponding to the second HARQ-ACK actually received can be used to determine whether the indication state actually indicates 0 bits or 4 bits. For example, if no downlink transmission corresponding to the second HARQ-ACK is received, it is determined that the indication is 0 bits. If at least 1 downlink transmission corresponding to the second HARQ-ACK is received, it is determined that the indication is 4 bits.

[0249] The above-mentioned first indication state may be an indication state defined by the protocol or configured on the network side, through which it may be indicated that there is no second HARQ-ACK, or that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or that the total number of bits of the second HARQ-ACK is 0, or that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. The other indication states each correspond to a type of information for determining the total number of bits of the second HARQ-ACK greater than 0.

[0250] The second indication state may be a protocol-defined or network-configured indication state, and the first and second conditions may be protocol-defined or network-configured. The second indication state may indicate different contents under different conditions, thereby reducing DCI overhead.

[0251] In addition, when the first indication field indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that there is no second HARQ-ACK, if there is actually a second HARQ-ACK and the second HARQ-ACK overlaps with the first HARQ-ACK in the time domain, the second HARQ-ACK can be discarded.

[0252] Optionally, the information used to determine the total number of bits of the second HARQ-ACK includes:

[0253] The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

[0254] The total number of bits of the second HARQ-ACK may be 0, or a number of bits greater than 0. The total number of downlink transmissions corresponding to the second HARQ-ACK may include the total number of PDSCH or SPS PDSCH release transmissions corresponding to the second HARQ-ACK, that is, the total number of PDCCHs that schedule PDSCH or PDCCHs that indicate SPS PDSCH release; or the total number of downlink transmissions corresponding to the second HARQ-ACK may include the total number of {serving cell, PDCCH monitoring occasion} pairs (i.e., {serving cell, PDCCH monitoring occasion}-pair(s)) in which PDSCH or SPS PDSCH release exists, where PDSCH and SPS PDSCH release correspond to the second HARQ-ACK. In addition, the total number of PDCCHs for scheduling PDSCH and PDCCHs indicating SPS PDSCH release can also be referred to as the number of downlink transmissions (including PDSCH, SPS PDSCH release) that require second HARQ-ACK (including both ACK and NACK feedback information) feedback. And the total number of downlink transmissions corresponding to the second HARQ-ACK can be used to determine the total number of bits of the second HARQ-ACK.

[0255] For example, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0256] Each indication status indication of the first indication field may respectively correspond to a total number of bits of a dynamic HARQ-ACK codebook of a second HARQ-ACK, where the total number of bits includes 0 or an integer greater than 0; or

[0257] The first indication state of the first indication field may be used to indicate that the second HARQ-ACK does not exist, or to indicate that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or to indicate that the total number of bits of the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field may indicate a total number of bits greater than 0 in a dynamic HARQ-ACK codebook of a respective corresponding second HARQ-ACK; or

[0258] The second indication state of the first indication field may indicate the total number of bits of a dynamic HARQ-ACK codebook of a second HARQ-ACK HARQ-ACK under the first condition, and under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, and each indication state in the first indication field except the second indication state may indicate a total number of bits greater than 0 of a dynamic HARQ-ACK codebook of a corresponding second HARQ-ACK; or

[0259] Each indication state of the first indication field may indicate a total number of downlink transmissions corresponding to a respective second HARQ-ACK, wherein the total number of downlink transmissions may be used to determine a total number of bits of a HARQ-ACK codebook corresponding to the second HARQ-ACK, where the total number includes 0 or is greater than 0; or

[0260] The first indication state of the first indication field may be used to indicate that the second HARQ-ACK does not exist, or to indicate that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or to indicate that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state in the first indication field other than the first indication state indicates a total number of downlink transmissions corresponding to a respective type of second HARQ-ACK that is greater than 0, wherein the total number of downlink transmissions may be used to determine the total number of bits of the HARQ-ACK codebook corresponding to the second HARQ-ACK; or

[0261] The second indication state of the first indication field may indicate a total number of downlink transmissions corresponding to a second HARQ-ACK greater than 0 under the first condition. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a total number of downlink transmissions corresponding to a respective second HARQ-ACK greater than 0, wherein the total number of downlink transmissions is used to determine the total number of bits of the HARQ-ACK codebook corresponding to the second HARQ-ACK.

[0262] As an optional implementation manner, when the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK:

[0263] In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

[0264] The information used to determine the total number of bits of the second HARQ-ACK may be the total number of bits of the subcodebook of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the subcodebook of the second HARQ-ACK.

[0265] In this embodiment, each sub-indicator field can indicate the information of the number of bits of a sub-codebook of a sub-codebook. For example, if the HARQ-ACK codebook of the second HARQ-ACK contains multiple sub-codebooks, the first indication field contains multiple T-DAI fields, which respectively indicate the information used to determine the total number of bits of each sub-codebook. For example, the first indication field is 4 bits, of which the first 2 bits are the T-DAI field corresponding to the first sub-codebook, which is used to indicate the information for determining the total number of bits of the first sub-codebook, and the last 2 bits are the T-DAI field corresponding to the second sub-codebook, which is used to indicate the information for determining the total number of bits of the second sub-codebook. In particular, in the case of a single carrier, there may be no T-DAI field, only a C-DAI field. At this time, because there is no accumulation of numbers between carriers, the physical meaning of the C-DAI field is equivalent to the T-DAI field, and can also be used to determine the total number of bits of a dynamic HARQ-ACK codebook or sub-codebook. In this case, the first indication field can be expressed as a C-DAI field. Among them, when the first HARQ-ACK also uses a dynamic HARQ-ACK codebook, the first DCI also contains T-DAI and C-DAI (or only C-DAI) for determining the dynamic HARQ-ACK codebook size of the first HARQ-ACK, and these fields are different from the first indication field in the first DCI (corresponding to the T-DAI and C-DAI (or only C-DAI) of the second HARQ-ACK). It is an indication field.

[0266] Optionally, the first condition includes:

[0267] There is downlink transmission corresponding to the second HARQ-ACK; or

[0268] There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0269] The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0270] The overlap between the first uplink channel and the second uplink channel in the time domain may be that the first uplink channel and the second uplink channel overlap completely or partially in the time domain.

[0271] Optionally, the second condition includes:

[0272] There is no downlink transmission corresponding to the second HARQ-ACK; or

[0273] There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0274] The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0275] The fact that the first uplink channel and the second uplink channel do not overlap in the time domain may mean that the first uplink channel and the second uplink channel do not have any overlapping time domain resources in the time domain.

[0276] As an optional implementation, when the second HARQ-ACK uses a semi-static HARQ-ACK codebook:

[0277] The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0278] The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0279] The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under the first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and under the second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size. the number of bits of the second HARQ-ACK; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or to indicate that the number of bits of the second HARQ-ACK is determined according to the fallback mode, the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that there is no second HARQ-ACK, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or

[0280] The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

[0281] The above-mentioned third to eleventh indication states can be protocol defined or network configured. In addition, in the above four implementation modes, the indication states can be reused, for example: the third indication state can be the same as the fifth indication state or the seventh indication state, and the fourth indication state can be the same as the sixth indication state or the eighth indication state.

[0282] The above-mentioned determination of the number of bits of the second HARQ-ACK according to the fallback mode may be to determine that the number of bits of the second HARQ-ACK is 1. For example, the fallback mode may be defined as feedback of only 1 bit of the second HARQ-ACK when the following conditions are met: when only one or more SPS PDSCHs are received, and if multiple SPS PDSCHs are received, only one SPS PDSCH requires HARQ-ACK feedback; or, when only one SPS PDSCH release transmitted using DCI format 1-0 is received, and the C-DAI value in the DCI is 1; or, when only one PDSCH scheduled using DCI format 1-0 is received, and the C-DAI value in the DCI is 1.

[0283] It should be noted that, in the embodiment of the present invention, the first indication field may include other indication states in addition to the first to eleventh indication states, which may be specifically defined according to requirements.

[0284] Optionally, in a case where each indication status indication of the first indication field corresponds to a type of information for determining the total number of bits of the second HARQ-ACK, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored. That is, at this time, the terminal may not parse or read the indication information of the first indication field, or regardless of the content of the indication information of the first indication field, the terminal will not perform HARQ-ACK transmission according to the first indication field, and always assumes that there is no second HARQ-ACK and only transmits the first HARQ-ACK.

[0285] The second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain may mean that for the terminal, there is currently no uplink channel carrying the second HARQ-ACK that overlaps with the first uplink channel in the time domain.

[0286] Optionally, when the first indication field includes the third indication state and the fourth indication state, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored. That is, at this time, the terminal may not parse or read the indication information of the first indication field, or regardless of the content of the indication information of the first indication field, the terminal will not perform HARQ-ACK transmission according to the first indication field, and always assumes that there is no second HARQ-ACK and only transmits the first HARQ-ACK.

[0287] As an optional implementation manner, the terminal performing HARQ-ACK transmission according to the first indication field includes:

[0288] Determining, by the terminal, the number of bits of the second HARQ-ACK according to the first indication field;

[0289] The terminal performs HARQ-ACK transmission according to the number of bits of the second HARQ-ACK.

[0290] The terminal determines the number of bits of the second HARQ-ACK according to the first indication field, which may be determined by determining the number of bits of the second HARQ-ACK according to the indication state of the first indication field, for example, determining the number of bits of the second HARQ-ACK according to the information indicated by the indication state of the indication field for determining the total number of bits of the second HARQ-ACK. Or, it determines whether the number of bits of the second HARQ-ACK is 0 according to whether the second HARQ-ACK indicated by the first indication field exists, or whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK.

[0291] As an optional implementation manner, the terminal determining the number of bits of the second HARQ-ACK based on the first indication field may be performed only when it is determined that the first HARQ-ACK and the second HARQ-ACK need to be transmitted simultaneously on the same channel. For example, the terminal determining the number of bits of the second HARQ-ACK based on the first indication field includes:

[0292] When a first uplink channel carrying the first HARQ-ACK overlaps with a second uplink channel carrying the second HARQ-ACK in the time domain, the terminal determines the number of bits of the second HARQ-ACK according to the first indication field.

[0293] In this embodiment, since the terminal transmits HARQ-ACK according to the number of bits of the second HARQ-ACK determined according to the first indication field, the network device can receive HARQ-ACK according to the same number of bits of the second HARQ-ACK, thereby ensuring that the terminal and the network device have a consistent understanding of the number of bits of the second HARQ-ACK.

[0294] Optionally, the terminal performing HARQ-ACK transmission according to the number of bits of the second HARQ-ACK includes:

[0295] transmitting the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or,

[0296] When the number of bits of the second HARQ-ACK is greater than 0 or it is determined to transmit the second HARQ-ACK, the first HARQ-ACK and the second HARQ-ACK are transmitted simultaneously on the same channel according to the number of bits of the second HARQ-ACK; when the number of bits of the second HARQ-ACK is 0 or it is determined not to transmit the second HARQ-ACK, the first HARQ-ACK is transmitted on the first uplink channel.

[0297] The above-mentioned determination to transmit the second HARQ-ACK may be, according to the first indication field, determining that the number of bits of the second HARQ-ACK is greater than 0, or determining that there is a second HARQ-ACK, or determining that the second HARQ-ACK is allowed to be multiplexed and transmitted with the first HARQ-ACK; the above-mentioned determination not to transmit the second HARQ-ACK may be, according to the first indication field, determining that the number of bits of the second HARQ-ACK is 0, or determining that there is no second HARQ-ACK, or determining that the second HARQ-ACK is not multiplexed and transmitted with the first HARQ-ACK.

[0298] The above-mentioned simultaneous transmission of the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK determined according to the first indication field may be that the number of bits of the second HARQ-ACK transmitted on the channel is the number of bits of the second HARQ-ACK determined according to the first indication field, and the number of bits of the first HARQ-ACK may be determined in accordance with the prior art according to the HARQ-ACK codebook type configured by the network side, the actual reception situation, the relevant configuration parameters, etc. in accordance with the protocol provisions, or the number of bits determined by pre-negotiation between the terminal and the network side device, etc. In this embodiment of the present invention, the number of bits of the first HARQ-ACK is not limited, and it is assumed that the network side and the terminal always have the same understanding of the number of bits of the first HARQ-ACK.

[0299] The simultaneous transmission of the first HARQ-ACK and the second HARQ-ACK on the same channel may be simultaneous transmission of the first HARQ-ACK and the second HARQ-ACK on a first uplink channel or a second uplink channel, wherein the second channel may be a channel different from the first uplink channel, and may be a PUCCH corresponding to the first HARQ-ACK or an uplink channel with the same priority as the first uplink channel or the first HARQ-ACK.

[0300] The simultaneous transmission of the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK determined according to the first indication field may be, using the number of bits of the second HARQ-ACK determined according to the first indication field as a reference number of bits, and transmitting the second HARQ-ACK and the first HARQ-ACK simultaneously on the same uplink channel according to the reference number of bits; specifically including:

[0301] When the uplink channel for simultaneously transmitting the first HARQ-ACK and the second HARQ-ACK is a PUCCH, determining a PUCCH resource based at least on the reference number of bits, and simultaneously transmitting the first HARQ-ACK and the second HARQ-ACK on the PUCCH resource; or

[0302] When the uplink channel for simultaneously transmitting the first HARQ-ACK and the second HARQ-ACK is the PUSCH, the target resource for carrying the HARQ-ACK on the PUSCH is determined based at least on the reference number of bits, and the first HARQ-ACK and the second HARQ-ACK are simultaneously transmitted on the target resource.

[0303] The determining of the PUCCH resource includes at least one of the following:

[0304] Determine a PUCCH resource set;

[0305] Determine a minimum number of resource blocks (RBs) for PUCCH resources carrying the first HARQ-ACK and the second HARQ-ACK;

[0306] A PUCCH resource among at least one PUCCH resource for carrying channel state information CSI is determined, wherein the PUCCH resource for carrying CSI is a PUCCH resource for carrying multiple CSIs.

[0307] Determining the PUCCH resource set includes:

[0308] The PUCCH resource set is determined according to the sum of the number of bits of the first HARQ-ACK and the reference number of bits of the second HARQ-ACK.

[0309] Determining the minimum number of RBs of PUCCH resources carrying the first HARQ-ACK and the second HARQ-ACK includes:

[0310] determining, according to the sum of the number of bits of the first HARQ-ACK and the reference number of bits of the second HARQ-ACK, the minimum number of RBs of PUCCH resources carrying the first HARQ-ACK and the second HARQ-ACK; or

[0311] Determine the first minimum number of RBs for carrying the first HARQ-ACK according to the number of bits of the first HARQ-ACK, determine the second minimum number of RBs for carrying the second HARQ-ACK according to the reference number of bits of the second HARQ-ACK, and use the sum of the first minimum number of RBs and the second minimum number of RBs as the minimum number of RBs for PUCCH resources carrying the first HARQ-ACK and the second HARQ-ACK.

[0312] The determining of one PUCCH resource among at least one PUCCH resource for carrying CSI includes:

[0313] Select a PUCCH resource from at least one PUCCH resource for carrying CSI according to the sum of the number of bits of the first HARQ-ACK, the reference number of bits of the second HARQ-ACK, and the number of bits of CSI transmitted simultaneously with the first HARQ-ACK and the second HARQ-ACK.

[0314] The method further includes transmitting the second HARQ-ACK and the first HARQ-ACK simultaneously on the same uplink channel according to the reference bit number:

[0315] In the case where CSI and HARQ-ACK are transmitted simultaneously, whether to perform CSI discard and / or discard part of the CSI is determined based at least on the reference number of bits of the second HARQ-ACK.

[0316] Specifically, based on the reference number of bits of the first HARQ-ACK and the second HARQ-ACK, it is determined whether to perform CSI discard and / or discard part of the CSI.

[0317] Specifically, if it is determined not to be discarded, the CSI is directly transmitted simultaneously with the second HARQ-ACK and the first HARQ-ACK on the same uplink channel; if it is determined to be discarded, it is further determined which part of the CSI to retain and which part of the CSI to discard, and the retained CSI is transmitted simultaneously with the second HARQ-ACK and the first HARQ-ACK on the same uplink channel.

[0318] Determining a target resource for carrying HARQ-ACK on the PUSCH based on the reference number of bits includes:

[0319] determining, according to the sum of the number of bits of the first HARQ-ACK and the reference number of bits of the second HARQ-ACK, the target resources on the PUSCH for carrying the first HARQ-ACK and the second HARQ-ACK; or

[0320] Determine a first resource on the PUSCH for carrying the first HARQ-ACK according to the number of bits of the first HARQ-ACK, and determine a second resource on the PUSCH for carrying the second HARQ-ACK according to the reference number of bits of the second HARQ-ACK, where the target resources include the first resource and the second resource.

[0321] The step of simultaneously transmitting the second HARQ-ACK and the first HARQ-ACK on the same uplink channel according to the reference number of bits includes:

[0322] When the first HARQ-ACK and the second HARQ-ACK are transmitted using joint coding, transmitting the second HARQ-ACK according to the reference number of bits; or

[0323] When the first HARQ-ACK and the second HARQ-ACK are transmitted using independent coding, the second HARQ-ACK is transmitted according to the reference number of bits, or the second HARQ-ACK is transmitted according to the actual number of bits (i.e., the number of bits determined according to the downlink reception situation and HARQ-ACK corresponding to the second HARQ-ACK).

[0324] In which, when the second HARQ-ACK is transmitted according to the reference number of bits, a negative acknowledgement NACK bit is added after the actual bit sequence of the second HARQ-ACK to obtain a target bit sequence, and the number of bits of the target bit sequence is the reference number of bits.

[0325] As an optional implementation manner, the priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK.

[0326] In this implementation, the second HARQ-ACK with a low priority may be multiplexed and transmitted with the first HARQ-ACK with a high priority.

[0327] As an optional implementation, the first uplink channel is one of PUCCH and PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

[0328] In this embodiment, since the first uplink channel and the second uplink channel can be PUCCH or PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different, HARQ-ACK carried by uplink channels of the same or different types can be multiplexed and transmitted.

[0329] As an optional implementation manner, whether the first indication field exists in the first DCI is determined according to the configuration of high-layer signaling; or

[0330] By default, the first indication field always exists in the first DCI.

[0331] In this implementation, the terminal can determine whether the first indication field is in the first DCI based on the high-level signaling, so that when it is determined that it exists, the DCI is detected according to the DCI size of the first indication field. The high-level signaling can explicitly or implicitly indicate whether the first indication field exists in the first DCI. For example: the high-level signaling directly notifies whether the first indication field exists in the first DCI; or the high-level signaling can notify whether the multiplexing transmission of channels of different priorities is supported. If supported, it means that the first indication field is included in the first DCI; or the high-level signaling can notify whether the multiplexing transmission of the first HARQ-ACK and the second HARQ-ACK is supported. When the configuration supports it, it is determined that the first DCI has the first indication field.

[0332] The above-mentioned default that the first indication field always exists in the first DCI may be that the terminal and the network device believe that the first indication field always exists in the first DCI. And the first indication field can indicate a state to dynamically determine whether the multiplexing transmission of the first HARQ-ACK and the second HARQ-ACK is supported, for example: the indication state of the first indication field indicates that there is no second HARQ-ACK transmission or the second HARQ-ACK is not multiplexed with the first HARQ-ACK, which means that the multiplexing transmission of the first HARQ-ACK and the second HARQ-ACK is not supported, or that the second HARQ-ACK is scheduled or, or that the second uplink channel does not overlap with the first uplink channel.

[0333] As an optional implementation manner, when the first uplink channel is a PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating an SPS PDSCH release requiring HARQ-ACK feedback on the PUCCH; or

[0334] In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

[0335] The above-mentioned first DCI is a DCI for scheduling a PDSCH that requires HARQ-ACK feedback on the PUCCH, which can be understood as follows: the first DCI is used to schedule a PDSCH, and the PDSCH is a PDSCH that requires HARQ-ACK feedback on the PUCCH. The above-mentioned first DCI is a DCI for indicating an SPS PDSCH release that requires HARQ-ACK feedback on the PUCCH, which can be understood as follows: the first DCI is used to indicate an SPS PDSCH release, and the SPS PDSCH release is an SPS PDSCH release that requires HARQ-ACK feedback on the PUCCH.

[0336] As an optional implementation, when there are multiple first DCIs, the values ​​of the first indication fields in the multiple first DCIs are the same, or the terminal performs HARQ-ACK transmission according to the first indication field in the last DCI.

[0337] For example, when there are multiple DCIs corresponding to the first uplink channel, the values ​​of the first indicator fields of the multiple DCIs are the same, and the terminal can perform HARQ-ACK transmission according to the first indicator field of any DCI.

[0338] For example, when there are multiple DCIs corresponding to the first uplink channel, the terminal only performs HARQ-ACK transmission according to the first indication field in the last DCI.

[0339] As an optional implementation manner, the priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or

[0340] The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

[0341] In this implementation, HARQ-ACKs of different priorities can be multiplexed and transmitted, and HARQ-ACKs for unicast services and HARQ-ACKs for multicast services can be multiplexed and transmitted.

[0342] It should be noted that the overlap in the time domain mentioned in the present invention generally refers to overlap in the time domain in the same carrier group, for example, in the case of carrier aggregation (CA), in the same PUCCH carrier group, or in the case of dual link (DC), in the same main carrier group (MCG) or the same secondary carrier group (SCG), or in the case of CA and DC combined, in the same PUCCH carrier group in a certain carrier group (MCG or SCG); the above-mentioned carriers can be replaced by cells, which are equivalent.

[0343] In an embodiment of the present invention, a terminal receives first downlink control information DCI, where the first indication field of the first DCI is used to determine at least one of the following: the number of bits of the second HARQ-ACK, whether the second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed with the first HARQ-ACK for transmission; the terminal performs HARQ-ACK transmission according to the first indication field; wherein the first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed with the first HARQ-ACK for transmission. In this way, since the terminal performs HARQ-ACK transmission according to the first indication field, it can avoid that when multiple HARQ-ACKs are transmitted simultaneously, the terminal and the network device have inconsistent understandings of the number of bits of the HARQ-ACK transmitted by the terminal.

[0344] See Figure 5 , Figure 5 This is a flow chart of a method for receiving uplink control information provided by an embodiment of the present invention. Figure 5 As shown, the following steps are included:

[0345] Step 501: The network device sends first downlink control information (DCI), where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation (HARQ-ACK), whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed with the first HARQ-ACK for transmission.

[0346] Step 502: The network device receives HARQ-ACK according to the first indication field.

[0347] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0348] Optionally, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0349] Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or

[0350] The first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or

[0351] The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

[0352] Optionally, the information used to determine the total number of bits of the second HARQ-ACK includes:

[0353] The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

[0354] Optionally, when the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK:

[0355] In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

[0356] Optionally, when the second HARQ-ACK uses a semi-static HARQ-ACK codebook:

[0357] The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0358] The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0359] The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under the first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and under the second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size. the number of bits of the second HARQ-ACK; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or to indicate that the number of bits of the second HARQ-ACK is determined according to the fallback mode, the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that there is no second HARQ-ACK, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or

[0360] The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

[0361] Optionally, the first condition includes:

[0362] There is downlink transmission corresponding to the second HARQ-ACK; or

[0363] There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0364] The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK;

[0365] The second condition includes:

[0366] There is no downlink transmission corresponding to the second HARQ-ACK; or

[0367] There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0368] The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0369] Optionally, in the case where each indication status indication of the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field can be set arbitrarily.

[0370] Optionally, when the first indication field includes the third indication state and the fourth indication state, if it is determined that the second uplink channel carrying the second HARQ-ACK does not overlap with the first uplink channel in the time domain, the indication information of the first indication field can be set arbitrarily.

[0371] Optionally, the network device performs HARQ-ACK reception according to the first indication field, including:

[0372] Determining, by the network device, the number of bits of the second HARQ-ACK according to the first indication field;

[0373] The network device receives HARQ-ACK according to the number of bits of the second HARQ-ACK.

[0374] Optionally, the network device performing HARQ-ACK reception according to the number of bits of the second HARQ-ACK includes:

[0375] receiving the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or,

[0376] When the number of bits of the second HARQ-ACK is greater than 0 or it is determined that the terminal transmits the second HARQ-ACK, simultaneously receiving the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or

[0377] When the number of bits of the second HARQ-ACK is 0 or it is determined that the terminal does not transmit the second HARQ-ACK, the first HARQ-ACK is received on the first uplink channel.

[0378] Optionally, the network device determines, according to the first indication field, the number of bits of the second HARQ-ACK, including:

[0379] When the first uplink channel carrying the first HARQ-ACK and the second uplink channel carrying the second HARQ-ACK overlap in the time domain, the network device determines the number of bits of the second HARQ-ACK according to the first indication field.

[0380] Optionally, the priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK.

[0381] Optionally, the first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

[0382] Optionally, whether the first indication field exists in the first DCI is determined according to the configuration of high-layer signaling; or

[0383] By default, the first indication field always exists in the first DCI.

[0384] Optionally, when the first uplink channel is PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a semi-persistent scheduling SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or

[0385] In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

[0386] Optionally, when there are multiple first DCIs, the first indication fields in the multiple first DCIs are set to indicate the same value, or HARQ-ACK reception is performed according to the first indication field in the last DCI.

[0387] Optionally, the priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or

[0388] The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

[0389] Optionally, the first indication field is a reused existing bit in the first DCI, or the first indication field is a newly added bit in the first DCI.

[0390] It should be noted that this embodiment is Figure 4 The embodiment shown in the embodiment corresponds to the embodiment. This embodiment describes the implementation of the network device. The specific implementation can be found in Figure 4 In order to avoid duplication, the relevant descriptions of the embodiment shown will not be repeated in this embodiment, and the same beneficial effects can still be achieved.

[0391] The method provided by the embodiment of the present invention is illustrated below through multiple embodiments:

[0392] Example 1:

[0393] Assume that the low-priority HARQ-ACK (i.e., the second HARQ-ACK) codebook uses a dynamic codebook and CBG transmission is not configured, that is, at least 2 bits of T-DAI are required to indicate the total number of bits of the low-priority dynamic codebook (if CBG is configured, 4 bits of T-DAI are required, the first 2 bits indicate the T-DAI of the first sub-codebook, and the last 2 bits indicate the T-DAI of the second sub-codebook. The bit size of each sub-codebook is determined in a similar manner to the process in this embodiment and will not be repeated here); the high-priority HARQ-ACK (i.e., the first HARQ-ACK) can use the method in this embodiment regardless of the codebook used (for example, the high-priority HARQ-ACK only needs to be pressed Similar to the codebook used, a high-priority HARQ-ACK feedback sequence is determined according to the protocol definition); assuming that the terminal is configured to support multiplexing transmission when low-priority and high-priority channels overlap, or the terminal is configured to support HARQ-ACK multiplexing transmission of different priorities, it is determined that the DCI corresponding to the high-priority PUCCH (for example, the DCI of the PDSCH that schedules HARQ-ACK transmission on the PUCCH, or the DCI that indicates the release of SPS resources and this DCI indicating the release of SPS resources needs to transmit HARQ-ACK on the PUCCH) includes a first indication field (the first indication field can be 2 bits or 3 bits according to the mapping table in different ways). The network device sends DCI according to the case where the first indication field is included, and the terminal receives DCI according to the case where the first indication field is included; assuming that according to the scheduling of the network device, on an activated BWP on the main carrier, low-priority PUCCH (LP PUCCH) transmission and high-priority PUCCH (HP PUCCH) transmission overlap in the time domain, and both PUCCHs are used to carry HARQ-ACK. The priority of the two PUCCHs is determined according to the priority of the HARQ-ACK codebook they carry, and the priority of the HARQ-ACK codebook can be dynamically indicated by the priority indication field in the DCI that schedules the PDSCH.

[0394] Specific as Figure 6 As shown, the network devices can be as follows:

[0395] Assume that the network device schedules 6 downlink transmissions corresponding to low-priority HARQ-ACK (such as PDSCH or SPSPDSCH release), and each downlink transmission corresponds to 1-bit HARQ-ACK, that is, the network device determines that the low-priority PUCCH carries 6 bits of low-priority HARQ-ACK, such as Figure 3As shown; the network device determines that the A-bit high-priority HARQ-ACK is transmitted in the high-priority PUCCH according to the number of downlink transmissions corresponding to the high-priority HARQ-ACK scheduled, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the high-priority HARQ-ACK codebook (dynamic or semi-static);

[0396] The network device follows the following mapping table 1 according to mode 1 (each indication state indication of the first indication field corresponds to a type of information for determining the total number of bits of the second HARQ-ACK), or according to mode 3 (i.e. Figure 4 In the embodiment shown in FIG2 , the second indication state is implemented as follows: According to the mapping table 4 below, the 2-bit first indication field in the DCI corresponding to the HP PUCCH (i.e., the DCI for scheduling the PDSCH that needs to transmit a high-priority HARQ-ACK on the high-priority PUCCH) is set to "01" corresponding to The value is "2", or, according to method 2 (i.e. Figure 4 In the embodiment shown in FIG1 , the first indication state is implemented as follows: According to the following mapping table 2, the 2-bit first indication field in the DCI corresponding to the HP PUCCH is set to "10" corresponding to The value is "2", or, according to method 2 (i.e. Figure 4 In the embodiment shown in FIG1 , the first indication state is implemented as follows: According to the following mapping table 3, the 3-bit first indication field in the DCI corresponding to the HP PUCCH is set to "011" corresponding to The value is "3", indicating that there are 6 DCI transmissions corresponding to low priority, scheduling 6 PDSCH or SPSPDSCH releases corresponding to low priority HARQ-ACK, thereby helping the terminal determine that the number of bits of low priority HARQ-ACK is 6 bits (that is, the number of bits of the second HARQ-ACK is 6);

[0397] The network device receives HARQ-ACK according to A-bit high-priority HARQ-ACK and 6-bit low-priority HARQ-ACK on a PUCCH resource determined according to a high-priority and low-priority HARQ-ACK multiplexing transmission scheme (the specific multiplexing transmission scheme is not limited, for example, it can be a method defined in the protocol or newly defined in a subsequent protocol version), and obtains A-bit high-priority HARQ-ACK and 6-bit low-priority HARQ-ACK respectively;

[0398] The terminal side can be as follows:

[0399] For low priority cases, based on Figure 3Scheduling situation, assuming that the terminal loses the DCI in the last time slot (time slot n+3), then in the traditional system, if the terminal determines the low-priority HARQ-ACK according to T-DAI=1 in the last received DCI, it is determined to be 5 bits, which is inconsistent with the determination of the network device; in the embodiment of the present invention, regardless of the T-DAI in the last received DCI corresponding to the low-priority HARQ-ACK, the terminal determines the number of bits of the low-priority HARQ-ACK according to the first indicator field in the DCI corresponding to the HPPUCCH (that is, the indication of the first indicator field is used as the final T-DAI value, and if it is a single carrier, it is used as the final C-DAI value). Specifically, according to the mapping table corresponding to the same method adopted by the network device, the 2-bit first indicator field indicated can be obtained. The value is "2", or the 3-bit first indication field indicates The value is "3", and because more than 2 DCIs are received, it is judged that The total number of DCIs transmitted indicated by the value is 6 (which value of 2, 6, or 10 corresponds to the same indication state can be determined in combination with the number of DCIs received. Assuming that there is no continuous loss of 4 DCIs in the modulo 4 multiplexing counting mode, if the received DCI exceeds 2 but does not exceed 6, it can be determined that the current first indication field indicates 6 DCIs), and based on the number of downlink transmissions scheduled by the DCI and the number of HARQ-ACK feedback bits corresponding to each downlink transmission, it is determined that the low-priority HARQ-ACK is 6 bits in total (because there is packet loss in the last DCI, a 1-bit NACK is added to the 5-bit HARQ-ACK generated according to the DAI value corresponding to the received DCI to obtain 6-bit feedback information); for the high-priority case, based on the number of downlink transmissions corresponding to the received high-priority HARQ-ACK, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the high-priority HARQ-ACK codebook (dynamic or semi-static), it is determined that the A-bit high-priority HARQ-ACK is transmitted in the high-priority PUCCH;

[0400] The terminal simultaneously sends an A-bit high-priority HARQ-ACK and a 6-bit low-priority HARQ-ACK on a PUCCH resource determined according to the high-priority and low-priority HARQ-ACK multiplexing transmission scheme;

[0401] Table 1: Correspondence between the indication states of the 2-bit first indication field (corresponding to the above method 1, where T D =2 2 =4)

[0402]

[0403] Table 2: Correspondence of indication status of the 2-bit first indication field (corresponding to the above method 2, where T D =2 2 -1=3)

[0404]

[0405] Table 3: Correspondence of indication status of the 3-bit first indication field (corresponding to the above method 2, where T D =4)

[0406]

[0407] Table 4: Correspondence between the indication states of the 2-bit first indication field (corresponding to the above method 3, where T D =2 2 =4)

[0408]

[0409]

[0410] Example 2:

[0411] Assume that on an activated BWP on the primary carrier, there is no time domain overlap between the high priority PUCCH (HP PUCCH) carrying the high priority HARQ-ACK (i.e., the first HARQ-ACK mentioned above) and the low priority PUCCH (LP PUCCH) carrying the low priority HARQ-ACK (i.e., the second HARQ-ACK mentioned above) at the current moment (Case 1: the network device schedules the low priority transmission, but the LP PUCCH carrying the low priority HARQ-ACK does not overlap with the HP PUCCH in the time domain; Case 2: the network device does not schedule the low priority transmission, so there is no LP PUCCH). PUCCH); the rest of the assumptions are the same as in Example 1, that is, the assumptions about the high priority and low priority HARQ-ACK codebooks are the same as in Example 1, and assuming that the terminal is configured to support multiplexing transmission when low priority and high priority channels overlap, or the terminal is configured to support HARQ-ACK multiplexing transmission of different priorities, then it is determined that the DCI corresponding to the high priority PUCCH (that is, the DCI of the PDSCH for scheduling HARQ-ACK transmission on the PUCCH, or the DCI indicating the release of SPS resources and the DCI indicating the release of SPS resources needs to transmit HARQ-ACK on the PUCCH) contains a first indication field (the first indication field can be 2 bits or 3 bits according to the mapping table in different ways), the network device sends the DCI according to the case of including the first indication field, and the terminal receives the DCI according to the case of including the first indication field.

[0412] Specific as Figure 7 As shown, the network device side can be as follows:

[0413] For the above situation 1: assuming that the network device schedules B downlink transmissions corresponding to low-priority HARQ-ACK (such as PDSCH or SPS PDSCH release), each downlink transmission corresponds to 1-bit HARQ-ACK, that is, the network device determines that the low-priority PUCCH carries B bits of low-priority HARQ-ACK, or, for the above situation 2: assuming that the network device does not schedule low-priority transmission, there is no low-priority PUCCH transmission carrying low-priority HARQ-ACK; for cases 1 and 2, the network device determines that the A-bit high-priority HARQ-ACK is transmitted in the high-priority PUCCH according to the number of downlink transmissions corresponding to the high-priority HARQ-ACK scheduled by it, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the high-priority HARQ-ACK codebook (dynamic or semi-static);

[0414] For the above situation 1 and the above situation 2, there is no overlap between LP PUCCH and HP PUCCH; when using mode 1 (each indication state indication of the first indication field corresponds to a type of information for determining the total number of bits of the second HARQ-ACK), it is considered that the first indication field in the DCI corresponding to the HP PUCCH does not work, that is, the network device can set the first indication field to a fixed value or an arbitrary value, and the terminal will not read this value or determine the number of bits of the low-priority HARQ-ACK according to this value; when using mode 2 ( Figure 4 In the embodiment shown in the second indication state embodiment) according to mapping table 2, or in the use mode 3 ( Figure 4 In the embodiment shown in the third indication state embodiment), according to mapping table 4, the 2-bit first indication field in the DCI corresponding to the HP PUCCH is set to "00" corresponding to The value is "0", or, when using mode 2, according to mapping table 3, the 3-bit first indication field in the DCI corresponding to HP PUCCH is set to "000" A value of "0" indicates that there is no overlap between LP PUCCH and HP PUCCH, that is, no low-priority HARQ-ACK needs to be transmitted together with the high-priority HARQ-ACK. This helps the terminal determine that the number of bits of the low-priority HARQ-ACK transmitted together with the high-priority HARQ-ACK is 0, that is, no low-priority HARQ-ACK needs to be transmitted together with the high-priority HARQ-ACK;

[0415] For the above situation 1: the network device receives A-bit high-priority HARQ-ACK on HP PUCCH and B-bit low-priority HARQ-ACK on LP PUCCH; for the above situation 2: the network device receives A-bit high-priority HARQ-ACK only on HP PUCCH.

[0416] The terminal side can be as follows:

[0417] For the above situation 1: because it is determined based on the low priority and high priority scheduling conditions respectively that there is no time domain overlap between the LP PUCCH and the HP PUCCH, there is no need to perform multiplexing transmission between the low priority HARQ-ACK and the high priority HARQ-ACK; for the above situation 2: because no downlink transmission corresponding to the low priority is received, it is determined that there is no LP PUCCH carrying the low priority HARQ-ACK, and therefore there is no need to perform multiplexing transmission between the low priority HARQ-ACK and the high priority HARQ-ACK;

[0418] When the above-mentioned method 1 is used, it is determined according to the above judgment that the first indication field in the DCI corresponding to the HP PUCCH is ineffective, and the terminal may not read this indication field or not care about the indication state of this indication field. When the above-mentioned method 2 or the above-mentioned method 3 is used, the terminal may determine the indication state of the DCI corresponding to the HP PUCCH according to the 2-bit or 3-bit first indication field in the received DCI. If the value is "0", it can be determined according to the corresponding mapping table that there is no low-priority HARQ-ACK multiplexing transmission with the high-priority HARQ-ACK at this time. Then: for the above situation 1, the terminal directly determines that the B-bit low-priority HARQ-ACK is transmitted in the LP PUCCH based on the number of downlink transmissions of the corresponding low-priority HARQ-ACK received, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the low-priority HARQ-ACK codebook (dynamic or semi-static), and determines that the A-bit high-priority HARQ-ACK is transmitted in the HP PUCCH based on the number of downlink transmissions of the corresponding high-priority HARQ-ACK received, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the high-priority HARQ-ACK codebook (dynamic or semi-static), and transmits the B-bit low-priority HARQ-ACK on the LP PUCCH and the A-bit high-priority HARQ-ACK on the HP PUCCH respectively. For the above situation 2, the terminal determines that the A-bit high-priority HARQ-ACK is transmitted in the HP PUCCH (i.e., there is no low-priority HARQ-ACK transmission at this time) based on the number of downlink transmissions of the corresponding high-priority HARQ-ACK received, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the high-priority HARQ-ACK codebook (dynamic or semi-static), and transmits the A-bit high-priority HARQ-ACK only on the HP PUCCH.

[0419] Example 3:

[0420] Assuming that the low-priority HARQ-ACK uses a semi-static codebook type, the first indication field included in the DCI corresponding to the HP PUCCH (i.e., the above-mentioned first DCI) is 1 or 2 bits, and the other assumptions are the same as in Example 1, as follows:

[0421] The first indication field can be 1 bit, corresponding to mode 4 (i.e. Figure 4 The third indication state and the fourth indication state in the embodiment shown in FIG5 are implemented); or the 2-bit corresponding mode 5 (ie Figure 4 The fifth indication state and the sixth indication state in the embodiment shown) and mode 6 (ie Figure 4 Implementation of the seventh indication state and the eighth indication state in the embodiment shown).

[0422] For the semi-static codebook, the network device sends 3 bits, the terminal receives 1 bit, and multiplexes and transmits it according to the A1 bit; in the above methods 4-6, if the instruction is generated according to the semi-static codebook, the 3 bits are transmitted together with the AN.

[0423] The network device side can be as follows:

[0424] Assume that the network device schedules 3 downlink transmissions (such as PDSCH or SPS PDSCH release) corresponding to low-priority HARQ-ACK (i.e., the second HARQ-ACK mentioned above), and each downlink transmission corresponds to 1-bit HARQ-ACK, such as Figure 2 As shown, because the fallback condition of the semi-static codebook is not satisfied (the case of 1-bit HARQ-ACK transmission), the network device determines that the low priority HARQ-ACK carried in the LP PUCCH is determined according to the semi-static codebook, that is, based on the K1 set, as shown Figure 2 The figure shows a 6-bit HARQ-ACK. The network device determines that the A-bit high-priority HARQ-ACK is transmitted in the high-priority PUCCH based on the number of downlink transmissions of the corresponding high-priority HARQ-ACK (i.e., the first HARQ-ACK) scheduled, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the high-priority HARQ-ACK codebook (dynamic or semi-static).

[0425] The network device sets the 1-bit first indication field in the DCI corresponding to the HP PUCCH to "1" according to the following mapping table 5 according to the above method 4, or according to the following mapping table 6 according to the above method 5, or, according to the above method 6 according to the following mapping table 7, sets the 1-bit first indication field in the DCI corresponding to the HP PUCCH to "0", or, according to the above method 7 (i.e. Figure 4 In the illustrated embodiment, the ninth indication state, the tenth indication state, and the eleventh indication state are implemented according to the following mapping table 8. The 2-bit first indication field in the DCI corresponding to the HP PUCCH is set to "10", indicating that the number of bits of the low-priority HARQ-ACK is determined according to the size of the semi-static codebook, thereby helping the terminal determine that the number of bits of the low-priority HARQ-ACK is 6 bits.

[0426] The network device receives HARQ-ACK according to A-bit high-priority HARQ-ACK and 6-bit low-priority HARQ-ACK on a PUCCH resource determined according to the high-priority and low-priority HARQ-ACK multiplexing transmission scheme, and obtains A-bit high-priority HARQ-ACK and 6-bit low-priority HARQ-ACK respectively.

[0427] Table 5: Correspondence of indication status of 1-bit first indication field (corresponding to above method 4)

[0428]

[0429] Table 6: Correspondence of indication status of 1-bit first indication field (corresponding to above method 5)

[0430]

[0431]

[0432] Table 7: Correspondence of indication status of 1-bit first indication field (corresponding to above method 6)

[0433]

[0434] Table 8: Correspondence of indication status of the 2-bit first indication field (corresponding to the above method 7)

[0435]

[0436] The terminal side can be as follows:

[0437] For low priority cases, based on Figure 2 Scheduling situation, assuming that the terminal only receives the first DCI, and the first DCI is fallback DCI and the DAI therein is 1, then in the traditional system, the terminal will consider it as a fallback mode of the semi-static codebook, and consider that the low-priority 1-bit HARQ-ACK is transmitted on the LP PUCCH determined according to the first DCI, which is inconsistent with the determination of the network device; In the embodiment of the present invention, regardless of how many DCIs corresponding to the low-priority HARQ-ACK are received by the terminal, the number of bits of the low-priority HARQ-ACK is determined according to the first indication field in the DCI corresponding to the HP PUCCH. Specifically, according to the mapping table corresponding to the same method adopted by the network device, it can be determined according to the 1-bit first indication field or the 2-bit first indication field that the number of bits of the low-priority HARQ-ACK is determined according to the size of the semi-static codebook. In particular, for the above-mentioned method 6, because both 0 bits and the number of bits determined according to the size of the semi-static codebook correspond to the first indication field being in state "0", the terminal determines that the first indication field is "0" based on the actual received DCI corresponding to the low-priority HARQ-ACK, indicating that the number of bits of the low-priority HARQ-ACK is determined according to the size of the semi-static codebook; furthermore, the terminal determines that the low-priority HARQ-ACK is 6 bits in total; for the high-priority case, the A-bit high-priority HARQ-ACK is determined to be transmitted in the high-priority PUCCH according to the number of downlink transmissions corresponding to the high-priority HARQ-ACK received and the number of HARQ-ACK bits corresponding to each downlink transmission and the type of the high-priority HARQ-ACK codebook (dynamic or semi-static).

[0438] The terminal simultaneously sends an A-bit high-priority HARQ-ACK and a 6-bit low-priority HARQ-ACK on a PUCCH resource determined according to a high-priority and low-priority HARQ-ACK multiplexing transmission scheme.

[0439] Example 4:

[0440] Assuming that the low-priority HARQ-ACK uses a semi-static codebook type, the first indication field included in the DCI corresponding to the HP PUCCH is 1 or 2 bits, and other assumptions are the same as those in Example 2, as follows:

[0441] For a semi-static codebook, if the network device does not send an LP AN and indicates that there is no LP AN multiplexing through a specific status in the DCI, only the HP AN is transmitted. Using the above-mentioned method 5 or method 6, the absence of an LP AN can be determined based on the first indication field. Using the above-mentioned method 4, if the terminal does not receive any LP transmission, it is determined to ignore the first indication field and only transmit the HP AN, or if it is determined that there is no overlap, the first indication field is not needed to determine the number of LP AN bits.

[0442] The network device side can be as follows:

[0443] Case 1: Assuming that the network device schedules more than one downlink transmission corresponding to a low-priority HARQ-ACK (such as PDSCH or SPS PDSCH release), each downlink transmission corresponds to 1-bit HARQ-ACK, that is, the network device determines the low-priority PUCCH to carry B bits of low-priority HARQ-ACK (that is, the above-mentioned second HARQ-ACK) according to the determination method of the semi-static codebook. Or, Case 2: Assuming that the network device does not schedule low-priority transmission, there is no low-priority PUCCH transmission carrying low-priority HARQ-ACK; for Cases 1 and 2, the network device determines that the A-bit high-priority HARQ-ACK is transmitted in the high-priority PUCCH according to the number of downlink transmissions corresponding to the high-priority HARQ-ACK (that is, the above-mentioned first HARQ-ACK) scheduled by it, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the high-priority HARQ-ACK codebook (dynamic or semi-static);

[0444] For the above cases 1 and 2, there is no overlap between LP PUCCH and HP PUCCH; when using the above method 4, it is considered that the first indicator field in the DCI corresponding to HP PUCCH is ineffective, that is, the network device can set the first indicator field to a fixed value or an arbitrary value, and the terminal will not read this value or determine the number of bits of the low-priority HARQ-ACK according to this value; when using the above method 5, according to mapping table 6, or according to mapping table 7 when using the above method 6, the 1-bit first indicator field in the DCI corresponding to HP PUCCH is set to "0", or, when using the above method 7, according to mapping table 8, the 2-bit first indicator field in the DCI corresponding to HP PUCCH is set to "00", indicating that there is no overlap between LP PUCCH and HP PUCCH, that is, no low-priority HARQ-ACK needs to be transmitted together with the high-priority HARQ-ACK. This helps the terminal determine that the number of bits of the low-priority HARQ-ACK transmitted together with the high-priority HARQ-ACK is 0, that is, no low-priority HARQ-ACK needs to be transmitted together with the high-priority HARQ-ACK;

[0445] For the above situation 1: the network device receives A-bit high-priority HARQ-ACK on HP PUCCH and B-bit low-priority HARQ-ACK on LP PUCCH; for the above situation 2: the network device receives A-bit high-priority HARQ-ACK only on HP PUCCH.

[0446] The terminal side can be as follows:

[0447] For the above situation 1: because it is determined based on the low priority and high priority scheduling conditions respectively that there is no time domain overlap between the LP PUCCH and the HP PUCCH, there is no need to perform multiplexing transmission between the low priority HARQ-ACK and the high priority HARQ-ACK; for the above situation 2: because no downlink transmission corresponding to the low priority is received, it is determined that there is no LP PUCCH carrying the low priority HARQ-ACK, and therefore there is no need to perform multiplexing transmission between the low priority HARQ-ACK and the high priority HARQ-ACK;

[0448] When the above-mentioned method 4 is used, it is determined according to the above judgment that the first indication field in the DCI corresponding to the HP PUCCH is ineffective, and the terminal may not read this indication field or care about the indication status of this indication field. When the above-mentioned method 5, method 6, or method 7 is used, according to the value of the 1-bit or 2-bit first indication field in the received DCI corresponding to the HP PUCCH, it can be determined according to the corresponding mapping table that there is no low-priority HARQ-ACK and high-priority HARQ-ACK multiplexing transmission at this time. In particular, for method 6, in the above-mentioned case 1, because the terminal receives multiple downlink transmissions corresponding to the low-priority HARQ-ACK and the determined LP PUCCH resources do not overlap with the HP PUCCH, it is determined that the "0" indicated by the first indication field at this time indicates that there is no low-priority HARQ-ACK and high-priority HARQ-ACK multiplexing transmission; in the above-mentioned case 2, because the terminal does not receive any downlink transmission corresponding to the low-priority HARQ-ACK, it is determined that the "0" indicated by the first indication field at this time indicates that there is no low-priority HARQ-ACK and high-priority HARQ-ACK multiplexing transmission. Furthermore, for the above situation 1, the terminal directly determines that the B-bit low-priority HARQ-ACK is transmitted in the LP PUCCH according to the number of downlink transmissions of the corresponding low-priority HARQ-ACK received, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the low-priority HARQ-ACK codebook (dynamic or semi-static), and determines that the A-bit high-priority HARQ-ACK is transmitted in the HP PUCCH according to the number of downlink transmissions of the corresponding high-priority HARQ-ACK received, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the high-priority HARQ-ACK codebook (dynamic or semi-static), and transmits the B-bit low-priority HARQ-ACK on the LP PUCCH and the A-bit high-priority HARQ-ACK on the HP PUCCH respectively; for situation 2, the terminal determines that the A-bit high-priority HARQ-ACK is transmitted in the HP PUCCH according to the number of downlink transmissions of the corresponding high-priority HARQ-ACK received, the number of HARQ-ACK bits corresponding to each downlink transmission, and the type of the high-priority HARQ-ACK codebook (dynamic or semi-static). The A-bit high-priority HARQ-ACK is transmitted on the HP PUCCH (i.e., there is no low-priority HARQ-ACK transmission at this time), and only the A-bit high-priority HARQ-ACK is transmitted on the HP PUCCH;

[0449] It should be noted that, in the above-mentioned multiple embodiments, the above-mentioned terminals and network devices execute the steps in no particular order, and are only for the purpose of illustrating specific behaviors. In the above-mentioned multiple embodiments, only one DCI schedules one PDSCH, and one PDSCH corresponds to 1-bit feedback as an example. If one DCI schedules multiple PDSCHs or one PDSCH corresponds to multi-bit feedback (for example, multiple TBs or CBG configuration), it only affects the result of the total number of bits determined according to T-DAI, and does not affect the above-mentioned process of determining the number of bits according to the first indication field. The above-mentioned method can be reused after making corresponding replacements for the determined number of bits.

[0450] In addition, in the above multiple embodiments, if one or both PUCCHs are replaced with PUSCH, the same applies, wherein if the high priority PUCCH is replaced with a high priority PUSCH, the first indication field exists in the DCI that schedules the high priority PUSCH.

[0451] The 2-bit and 3-bit first indication fields are merely examples. Alternatively, a single bit may be used to indicate different cumulative DCI numbers in a modulo-2 manner. Alternatively, the number of bits may be greater than 2 or 3. The correspondence between different indication states and corresponding DCI numbers may also vary, all of which are included in the embodiments of the present invention.

[0452] Furthermore, the HARQ-ACKs of different priorities in the above embodiment are replaced by unicast and multicast HARQ-ACKs, or replaced by other two different UCI transmissions, which is also applicable.

[0453] In an embodiment of the present invention, when there is a conflict in transmission between two different types of HARQ-ACK, the number of bits of the second type of HARQ-ACK can be determined based on the first indication field in the DCI corresponding to the first type of HARQ-ACK or the uplink channel corresponding to the carrying of the first type of HARQ-ACK, thereby avoiding the change in the number of bits of the second type of HARQ-ACK due to packet loss affecting the transmission of the first type of HARQ-ACK.

[0454] See Figure 8 , Figure 8 This is a structural diagram of a terminal provided by an embodiment of the present invention, such as Figure 8 As shown, it includes a memory 820, a transceiver 800 and a processor 810:

[0455] The memory 820 is used to store computer programs; the transceiver 800 is used to send and receive data under the control of the processor 810; the processor 810 is used to read the computer program in the memory 820 and perform the following operations:

[0456] receiving first downlink control information (DCI), where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation (HARQ-ACK), whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0457] Performing HARQ-ACK transmission according to the first indication field;

[0458] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0459] The transceiver 800 is configured to receive and send data under the control of the processor 810 .

[0460] Among them, Figure 8 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 810 and memory represented by memory 820. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be further described herein. The bus interface provides an interface. The transceiver 800 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. For different user devices, the user interface 830 may also be an interface capable of connecting external or internal devices as required, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0461] The processor 810 is responsible for managing the bus architecture and general processing, and the memory 820 can store data used by the processor 800 when performing operations.

[0462] Optionally, the processor 810 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0463] The processor calls the computer program stored in the memory to execute any of the methods provided by the embodiments of the present invention according to the obtained executable instructions. The processor and the memory can also be physically separated.

[0464] Optionally, first downlink control information DCI is received, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0465] Performing HARQ-ACK transmission according to the first indication field;

[0466] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0467] Optionally, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0468] Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or

[0469] The first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or

[0470] The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

[0471] Optionally, the information used to determine the total number of bits of the second HARQ-ACK includes:

[0472] The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

[0473] Optionally, when the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK:

[0474] In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

[0475] Optionally, when the second HARQ-ACK uses a semi-static HARQ-ACK codebook:

[0476] The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0477] The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0478] The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under the first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and under the second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size. the number of bits of the second HARQ-ACK; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or to indicate that the number of bits of the second HARQ-ACK is determined according to the fallback mode, the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that there is no second HARQ-ACK, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or

[0479] The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

[0480] Optionally, the first condition includes:

[0481] There is downlink transmission corresponding to the second HARQ-ACK; or

[0482] There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0483] The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK;

[0484] The second condition includes:

[0485] There is no downlink transmission corresponding to the second HARQ-ACK; or

[0486] There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0487] The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0488] Optionally, in the case where each indication status indication of the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

[0489] Optionally, when the first indication field includes the third indication state and the fourth indication state, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

[0490] Optionally, the performing HARQ-ACK transmission according to the first indication field includes:

[0491] Determining, according to the first indication field, a number of bits of the second HARQ-ACK;

[0492] Perform HARQ-ACK transmission according to the number of bits of the second HARQ-ACK.

[0493] Optionally, the performing HARQ-ACK transmission according to the number of bits of the second HARQ-ACK includes:

[0494] transmitting the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or,

[0495] When the number of bits of the second HARQ-ACK is greater than 0 or it is determined to transmit the second HARQ-ACK, simultaneously transmit the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or

[0496] When the number of bits of the second HARQ-ACK is 0 or it is determined not to transmit the second HARQ-ACK, the first HARQ-ACK is transmitted on the first uplink channel.

[0497] Optionally, determining the number of bits of the second HARQ-ACK according to the first indication field includes:

[0498] When the first uplink channel carrying the first HARQ-ACK overlaps with the second uplink channel carrying the second HARQ-ACK in the time domain, the number of bits of the second HARQ-ACK is determined according to the first indication field.

[0499] Optionally, the priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK.

[0500] Optionally, the first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

[0501] Optionally, whether the first indication field exists in the first DCI is determined according to the configuration of high-layer signaling; or

[0502] By default, the first indication field always exists in the first DCI.

[0503] Optionally, when the first uplink channel is PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a semi-persistent scheduling SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or

[0504] In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

[0505] Optionally, when there are multiple first DCIs, the values ​​of the first indication fields in the multiple first DCIs are the same, or the terminal performs HARQ-ACK transmission according to the first indication field in the last DCI.

[0506] Optionally, the priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or

[0507] The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

[0508] Optionally, the first indication field is a reused existing bit in the first DCI, or the first indication field is a newly added bit in the first DCI.

[0509] It should be noted here that the above-mentioned terminal provided in the embodiment of the present invention can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effects. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0510] See Figure 9 , Figure 9 This is a structural diagram of a network device provided by an embodiment of the present invention, such as Figure 9 As shown, it includes a memory 920, a transceiver 900 and a processor 910:

[0511] The memory 920 is used to store computer programs; the transceiver 900 is used to send and receive data under the control of the processor 910; the processor 910 is used to read the computer program in the memory 920 and perform the following operations:

[0512] Sending a first DCI, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0513] Receiving HARQ-ACK according to the first indication field;

[0514] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0515] The transceiver 900 is configured to receive and send data under the control of the processor 910 .

[0516] Among them, Figure 9In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by one or more processors represented by processor 910 and memory represented by memory 920. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 900 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 910 is responsible for managing the bus architecture and general processing, and the memory 920 may store data used by the processor 910 when performing operations.

[0517] The processor 910 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0518] The processor calls the computer program stored in the memory to execute any of the methods provided by the embodiments of the present invention according to the obtained executable instructions. The processor and the memory can also be physically separated.

[0519] Optional,

[0520] Optionally, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0521] Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or

[0522] The first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or

[0523] The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

[0524] Optionally, the information used to determine the total number of bits of the second HARQ-ACK includes:

[0525] The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

[0526] Optionally, when the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK:

[0527] In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

[0528] Optionally, when the second HARQ-ACK uses a semi-static HARQ-ACK codebook:

[0529] The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0530] The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0531] The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under the first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and under the second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size. the number of bits of the second HARQ-ACK; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or to indicate that the number of bits of the second HARQ-ACK is determined according to the fallback mode, the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that there is no second HARQ-ACK, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or

[0532] The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

[0533] Optionally, the first condition includes:

[0534] There is downlink transmission corresponding to the second HARQ-ACK; or

[0535] There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0536] The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK;

[0537] The second condition includes:

[0538] There is no downlink transmission corresponding to the second HARQ-ACK; or

[0539] There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0540] The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0541] Optionally, in the case where each indication status indication of the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is set arbitrarily.

[0542] Optionally, when the first indication field includes the third indication state and the fourth indication state, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is arbitrarily set.

[0543] Optionally, the receiving HARQ-ACK according to the first indication field includes:

[0544] Determining, according to the first indication field, a number of bits of the second HARQ-ACK;

[0545] HARQ-ACK reception is performed according to the number of bits of the second HARQ-ACK.

[0546] Optionally, the performing HARQ-ACK reception according to the number of bits of the second HARQ-ACK includes:

[0547] receiving the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or,

[0548] When the number of bits of the second HARQ-ACK is greater than 0 or it is determined that the terminal transmits the second HARQ-ACK, simultaneously receiving the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or

[0549] When the number of bits of the second HARQ-ACK is 0 or it is determined that the terminal does not transmit the second HARQ-ACK, the first HARQ-ACK is received on the first uplink channel.

[0550] Optionally, determining the number of bits of the second HARQ-ACK according to the first indication field includes:

[0551] When the first uplink channel carrying the first HARQ-ACK overlaps with the second uplink channel carrying the second HARQ-ACK in the time domain, the number of bits of the second HARQ-ACK is determined according to the first indication field.

[0552] Optionally, the priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK.

[0553] Optionally, the first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

[0554] Optionally, whether the first indication field exists in the first DCI is determined according to the configuration of high-layer signaling; or

[0555] By default, the first indication field always exists in the first DCI.

[0556] Optionally, when the first uplink channel is PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a semi-static SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or

[0557] In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

[0558] Optionally, when there are multiple first DCIs, the first indication fields in the multiple first DCIs are set to indicate the same value, or HARQ-ACK reception is performed according to the first indication field in the last DCI.

[0559] Optionally, the priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or

[0560] The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

[0561] Optionally, the first indication field is a reused existing bit in the first DCI, or the first indication field is a newly added bit in the first DCI.

[0562] It should be noted here that the above-mentioned network device provided in the embodiment of the present invention can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0563] See Figure 10 , Figure 10 This is a structural diagram of a terminal provided by an embodiment of the present invention, such as Figure 10 As shown, terminal 1000 includes:

[0564] A receiving unit 1001 is configured to receive a first DCI at a terminal, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0565] A transmitting unit 1002 is configured to perform HARQ-ACK transmission according to the first indication field;

[0566] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0567] Optionally, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0568] Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or

[0569] The first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or

[0570] The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

[0571] Optionally, the information used to determine the total number of bits of the second HARQ-ACK includes:

[0572] The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

[0573] Optionally, when the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK:

[0574] In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

[0575] Optionally, when the second HARQ-ACK uses a semi-static HARQ-ACK codebook:

[0576] The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0577] The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0578] The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under the first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and under the second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size. the number of bits of the second HARQ-ACK; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or to indicate that the number of bits of the second HARQ-ACK is determined according to the fallback mode, the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that there is no second HARQ-ACK, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or

[0579] The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

[0580] Optionally, the first condition includes:

[0581] There is downlink transmission corresponding to the second HARQ-ACK; or

[0582] There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0583] The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK;

[0584] The second condition includes:

[0585] There is no downlink transmission corresponding to the second HARQ-ACK; or

[0586] There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0587] The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0588] Optionally, in the case where each indication status indication of the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

[0589] Optionally, when the first indication field includes the third indication state and the fourth indication state, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

[0590] Optionally, the transmission unit 1002 includes:

[0591] a determining subunit, configured to determine the number of bits of the second HARQ-ACK according to the first indication field;

[0592] The transmission subunit is used to perform HARQ-ACK transmission according to the number of bits of the second HARQ-ACK.

[0593] Optionally, the transmission subunit is used to:

[0594] transmitting the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or,

[0595] When the number of bits of the second HARQ-ACK is greater than 0 or it is determined to transmit the second HARQ-ACK, simultaneously transmit the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or

[0596] When the number of bits of the second HARQ-ACK is 0 or it is determined not to transmit the second HARQ-ACK, the first HARQ-ACK is transmitted on the first uplink channel.

[0597] Optionally, determine the subunit for:

[0598] When the first uplink channel carrying the first HARQ-ACK overlaps with the second uplink channel carrying the second HARQ-ACK in the time domain, the number of bits of the second HARQ-ACK is determined according to the first indication field.

[0599] Optionally, the priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK.

[0600] Optionally, the first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

[0601] Optionally, whether the first indication field exists in the first DCI is determined according to the configuration of high-layer signaling; or

[0602] By default, the first indication field always exists in the first DCI.

[0603] Optionally, when the first uplink channel is a PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or

[0604] In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

[0605] Optionally, when there are multiple first DCIs, the values ​​of the first indication fields in the multiple first DCIs are the same, or the terminal performs HARQ-ACK transmission according to the first indication field in the last DCI.

[0606] Optionally, the priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or

[0607] The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

[0608] Optionally, the first indication field is a reused existing bit in the first DCI, or the first indication field is a newly added bit in the first DCI.

[0609] It should be noted here that the above-mentioned terminal provided in the embodiment of the present invention can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effects. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0610] See Figure 11 , Figure 11 This is a structural diagram of a network device provided by an embodiment of the present invention, such as Figure 11 As shown, the network device 1100 includes:

[0611] A sending unit 1101 is configured to send a first DCI through a network device, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK, whether a second HARQ-ACK exists, and whether the second HARQ-ACK is multiplexed and transmitted with the first HARQ-ACK;

[0612] A receiving unit 1102 is configured to receive HARQ-ACK according to the first indication field;

[0613] The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

[0614] Optionally, when the second HARQ-ACK uses a dynamic HARQ-ACK codebook:

[0615] Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or

[0616] The first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or

[0617] The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

[0618] Optionally, the information used to determine the total number of bits of the second HARQ-ACK includes:

[0619] The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

[0620] Optionally, when the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK:

[0621] In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

[0622] Optionally, when the second HARQ-ACK uses a semi-static HARQ-ACK codebook:

[0623] The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0624] The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or

[0625] The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under the first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and under the second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size. the number of bits of the second HARQ-ACK; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or to indicate that the number of bits of the second HARQ-ACK is determined according to the fallback mode, the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that there is no second HARQ-ACK, or indicates that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or

[0626] The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the second HARQ-ACK is not multiplexed with the first HARQ-ACK for transmission, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

[0627] Optionally, the first condition includes:

[0628] There is downlink transmission corresponding to the second HARQ-ACK; or

[0629] There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0630] The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK;

[0631] The second condition includes:

[0632] There is no downlink transmission corresponding to the second HARQ-ACK; or

[0633] There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or

[0634] The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

[0635] Optionally, in the case where each indication status indication of the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is set arbitrarily.

[0636] Optionally, when the first indication field includes the third indication state and the fourth indication state, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is arbitrarily set.

[0637] Optionally, the receiving unit 1102 includes:

[0638] a determining subunit, configured to determine the number of bits of the second HARQ-ACK according to the first indication field;

[0639] The receiving subunit is configured to perform HARQ-ACK reception according to the number of bits of the second HARQ-ACK.

[0640] Optionally, the receiving subunit is used to:

[0641] receiving the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or,

[0642] When the number of bits of the second HARQ-ACK is greater than 0 or it is determined that the terminal transmits the second HARQ-ACK, simultaneously receiving the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or

[0643] When the number of bits of the second HARQ-ACK is 0 or it is determined that the terminal does not transmit the second HARQ-ACK, the first HARQ-ACK is received on the first uplink channel.

[0644] Optionally, determine the subunit for:

[0645] When the first uplink channel carrying the first HARQ-ACK overlaps with the second uplink channel carrying the second HARQ-ACK in the time domain, the number of bits of the second HARQ-ACK is determined according to the first indication field.

[0646] Optionally, the priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK.

[0647] Optionally, the first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

[0648] Optionally, whether the first indication field exists in the first DCI is determined according to the configuration of high-layer signaling; or

[0649] By default, the first indication field always exists in the first DCI.

[0650] Optionally, when the first uplink channel is PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a semi-static SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or

[0651] In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

[0652] Optionally, when there are multiple first DCIs, the first indication fields in the multiple first DCIs are set to indicate the same value, or HARQ-ACK reception is performed according to the first indication field in the last DCI.

[0653] Optionally, the priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or

[0654] The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

[0655] Optionally, the first indication field is a reused existing bit in the first DCI, or the first indication field is a newly added bit in the first DCI.

[0656] It should be noted here that the above-mentioned network device provided in the embodiment of the present invention can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0657] It should be noted that the division of units in the embodiments of the present invention is schematic and is only a logical functional division. In actual implementation, other division methods may be used. In addition, the functional units in the various embodiments of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into a single unit. The above-mentioned integrated units can be implemented in the form of hardware or software functional units.

[0658] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0659] An embodiment of the present invention also provides a processor-readable storage medium, which stores a computer program. The computer program is used to enable the processor to execute the uplink control information transmission method provided by the embodiment of the present invention, or the computer program is used to enable the processor to execute the uplink control information receiving method provided by the embodiment of the present invention.

[0660] The processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NANDFLASH), solid-state drives (SSDs)), etc.

[0661] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) that contain computer-usable program code.

[0662] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0663] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce an article of manufacture comprising an instruction device that implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0664] These processor-executable instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0665] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A method for transmitting uplink control information, characterized in that: include: The terminal receives first downlink control information DCI, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of the second hybrid automatic repeat request confirmation HARQ-ACK and whether the second HARQ-ACK exists; The terminal performs HARQ-ACK transmission according to the first indication field; The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

2. The method according to claim 1, wherein When the second HARQ-ACK uses a dynamic HARQ-ACK codebook: Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or A first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

3. The method according to claim 2, wherein The information used to determine the total number of bits of the second HARQ-ACK includes: The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

4. The method according to claim 2, wherein When the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK: In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

5. The method according to claim 1, wherein When the second HARQ-ACK uses a semi-static HARQ-ACK codebook: The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under a first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and under a second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

6. The method according to claim 2 or 5, wherein: The first condition includes: There is downlink transmission corresponding to the second HARQ-ACK; or There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK; The second condition includes: There is no downlink transmission corresponding to the second HARQ-ACK; or There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

7. The method according to claim 2, wherein In the case where each indication status indication of the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

8. The method according to claim 5, wherein In the case where the first indication field includes the third indication state and the fourth indication state, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

9. The method according to claim 1, wherein The terminal performing HARQ-ACK transmission according to the first indication field, including: Determining, by the terminal, the number of bits of the second HARQ-ACK according to the first indication field; The terminal performs HARQ-ACK transmission according to the number of bits of the second HARQ-ACK.

10. The method according to claim 9, wherein The terminal performs HARQ-ACK transmission according to the number of bits of the second HARQ-ACK, including: transmitting the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or, When the number of bits of the second HARQ-ACK is greater than 0 or it is determined to transmit the second HARQ-ACK, simultaneously transmit the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or When the number of bits of the second HARQ-ACK is 0 or it is determined not to transmit the second HARQ-ACK, the first HARQ-ACK is transmitted on the first uplink channel.

11. The method according to claim 9, wherein The terminal determining, according to the first indication field, the number of bits of the second HARQ-ACK, including: When a first uplink channel carrying the first HARQ-ACK overlaps with a second uplink channel carrying the second HARQ-ACK in the time domain, the terminal determines the number of bits of the second HARQ-ACK according to the first indication field.

12. The method according to claim 1, wherein The priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK; or, The priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or, The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

13. The method according to claim 1, wherein The first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

14. The method according to claim 1, wherein Whether the first indication field exists in the first DCI is determined according to the configuration of higher layer signaling; or By default, the first indication field always exists in the first DCI.

15. The method according to claim 1, wherein In a case where the first uplink channel is a PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a semi-persistent scheduling SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

16. The method according to claim 1, wherein When there are multiple first DCIs, the values ​​of the first indication fields in the multiple first DCIs are the same, or the terminal performs HARQ-ACK transmission according to the first indication field in the last DCI.

17. A method for receiving uplink control information, characterized in that: include: The network device sends first downlink control information DCI, where the first indication field of the first DCI is used to determine at least one of the following: the number of bits of the second hybrid automatic repeat request confirmation HARQ-ACK and whether the second HARQ-ACK exists; The network device performs HARQ-ACK reception according to the first indication field; The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

18. The method according to claim 17, wherein When the second HARQ-ACK uses a dynamic HARQ-ACK codebook: Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or A first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

19. The method according to claim 18, wherein The information used to determine the total number of bits of the second HARQ-ACK includes: The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

20. The method of claim 18, wherein: When the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK: In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

21. The method according to claim 17, wherein When the second HARQ-ACK uses a semi-static HARQ-ACK codebook: The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under a first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and under a second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

22. The method according to claim 18 or 21, wherein The first condition includes: There is downlink transmission corresponding to the second HARQ-ACK; or There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK; The second condition includes: There is no downlink transmission corresponding to the second HARQ-ACK; or There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

23. The method of claim 17, wherein: The network device performing HARQ-ACK reception according to the first indication field includes: Determining, by the network device, the number of bits of the second HARQ-ACK according to the first indication field; The network device receives HARQ-ACK according to the number of bits of the second HARQ-ACK.

24. The method according to claim 23, wherein The network device performs HARQ-ACK reception according to the number of bits of the second HARQ-ACK, including: receiving the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or, When the number of bits of the second HARQ-ACK is greater than 0 or it is determined that the terminal transmits the second HARQ-ACK, simultaneously receiving the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or When the number of bits of the second HARQ-ACK is 0 or it is determined that the terminal does not transmit the second HARQ-ACK, the first HARQ-ACK is received on the first uplink channel.

25. The method of claim 23, wherein: The network device determining, according to the first indication field, the number of bits of the second HARQ-ACK, including: When the first uplink channel carrying the first HARQ-ACK and the second uplink channel carrying the second HARQ-ACK overlap in the time domain, the network device determines the number of bits of the second HARQ-ACK according to the first indication field.

26. The method of claim 17, wherein: The priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK; or The priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

27. The method of claim 17, wherein: The first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

28. The method of claim 17, wherein: Whether the first indication field exists in the first DCI is determined according to the configuration of higher layer signaling; or By default, the first indication field always exists in the first DCI.

29. The method of claim 17, wherein: In a case where the first uplink channel is a PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a semi-persistent scheduling SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

30. The method of claim 17, wherein: When there are multiple first DCIs, the first indication fields in the multiple first DCIs are set to indicate the same value, or HARQ-ACK reception is performed according to the first indication field in the last DCI.

31. A terminal, characterized in that: Includes memory, transceiver and processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: receiving first downlink control information (DCI), where a first indication field of the first DCI is used to determine at least one of the following: a number of bits of a second hybrid automatic repeat request confirmation (HARQ-ACK) and whether a second HARQ-ACK exists; Performing HARQ-ACK transmission according to the first indication field; The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

32. The terminal according to claim 31, wherein When the second HARQ-ACK uses a dynamic HARQ-ACK codebook: Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or A first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

33. The terminal according to claim 32, wherein: The information used to determine the total number of bits of the second HARQ-ACK includes: The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

34. The terminal according to claim 32, wherein: When the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK: In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

35. The terminal according to claim 31, wherein When the second HARQ-ACK uses a semi-static HARQ-ACK codebook: The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under a first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and under a second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

36. The terminal according to claim 32 or 35, characterized in that The first condition includes: There is downlink transmission corresponding to the second HARQ-ACK; or There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK; The second condition includes: There is no downlink transmission corresponding to the second HARQ-ACK; or There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

37. The terminal according to claim 32, wherein: In the case where each indication status indication of the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

38. The terminal according to claim 35, wherein: In the case where the first indication field includes the third indication state and the fourth indication state, if it is determined that the second uplink channel that does not carry the second HARQ-ACK overlaps with the first uplink channel in the time domain, the indication information of the first indication field is ignored.

39. The terminal according to claim 31, wherein The performing HARQ-ACK transmission according to the first indication field includes: Determining, according to the first indication field, a number of bits of the second HARQ-ACK; Perform HARQ-ACK transmission according to the number of bits of the second HARQ-ACK.

40. The terminal according to claim 39, wherein The performing HARQ-ACK transmission according to the number of bits of the second HARQ-ACK includes: transmitting the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or, When the number of bits of the second HARQ-ACK is greater than 0 or it is determined to transmit the second HARQ-ACK, simultaneously transmit the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or When the number of bits of the second HARQ-ACK is 0 or it is determined not to transmit the second HARQ-ACK, the first HARQ-ACK is transmitted on the first uplink channel.

41. The terminal according to claim 39, wherein: The determining, according to the first indication field, the number of bits of the second HARQ-ACK includes: When the first uplink channel carrying the first HARQ-ACK overlaps with the second uplink channel carrying the second HARQ-ACK in the time domain, the number of bits of the second HARQ-ACK is determined according to the first indication field.

42. The terminal according to claim 31, wherein The priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK; or, The priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or, The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

43. The terminal according to claim 31, wherein The first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

44. The terminal according to claim 31, wherein Whether the first indication field exists in the first DCI is determined according to the configuration of higher layer signaling; or By default, the first indication field always exists in the first DCI.

45. The terminal according to claim 31, wherein In a case where the first uplink channel is a PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a semi-persistent scheduling SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

46. ​​The terminal according to claim 31, wherein When there are multiple first DCIs, the values ​​of the first indication fields in the multiple first DCIs are the same, or the terminal performs HARQ-ACK transmission according to the first indication field in the last DCI.

47. A network device, characterized in that: Includes memory, transceiver and processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Sending first downlink control information DCI, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK and whether a second HARQ-ACK exists; Receiving HARQ-ACK according to the first indication field; The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

48. The network device according to claim 47, wherein: When the second HARQ-ACK uses a dynamic HARQ-ACK codebook: Each indication status indication in the first indication field corresponds to a type of information used to determine the total number of bits of the second HARQ-ACK; or A first indication state of the first indication field is used to indicate that the second HARQ-ACK does not exist, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0, and each indication state other than the first indication state in the first indication field indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0; or The second indication state of the first indication field indicates, under the first condition, information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0. Under the second condition, the second indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the total number of bits of the second HARQ-ACK is 0, or indicates that the total number of downlink transmissions corresponding to the second HARQ-ACK is 0. Each indication state in the first indication field except the second indication state indicates a corresponding type of information for determining the total number of bits of the second HARQ-ACK, and the total number of bits is greater than 0.

49. The network device according to claim 48, wherein The information used to determine the total number of bits of the second HARQ-ACK includes: The total number of bits of the second HARQ-ACK, or the total number of downlink transmissions corresponding to the second HARQ-ACK.

50. The network device according to claim 48, wherein When the first indication field indicates information used to determine the total number of bits of the second HARQ-ACK: In the case where the dynamic HARQ-ACK codebook of the second HARQ-ACK includes multiple sub-codebooks, the first indication field includes multiple sub-indication fields, each sub-indication field being used to indicate the corresponding information for determining the number of bits of the sub-codebook of the second HARQ-ACK.

51. The network device according to claim 47, wherein When the second HARQ-ACK uses a semi-static HARQ-ACK codebook: The first indication field includes at least: a third indication state and a fourth indication state, the third indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the fourth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or The first indication field includes at least: a fifth indication state and a sixth indication state, the fifth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the sixth indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or The first indication field includes at least: a seventh indication state and an eighth indication state, wherein the seventh indication state indicates, under a first condition, that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and under a second condition, the seventh indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, and the eighth indication state is used to indicate that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size; or, the seventh indication state is used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicates that the number of bits of the second HARQ-ACK is determined according to a fallback mode, and the eighth indication state indicates that the number of bits of the second HARQ-ACK is determined according to a semi-static HARQ-ACK codebook size under the first condition, and under the second condition, the eighth indication state is used to indicate that the second HARQ-ACK does not exist, or indicates that the number of bits of the second HARQ-ACK is 0, or indicates that the number of downlink transmissions corresponding to the second HARQ-ACK is 0; or The first indication field includes at least: a ninth indication state, a tenth indication state, and an eleventh indication state, the ninth indication state being used to indicate that the second HARQ-ACK does not exist, or indicating that the number of bits of the second HARQ-ACK is 0, or indicating that the number of downlink transmissions corresponding to the second HARQ-ACK is 0, the tenth indication state being used to indicate that the number of bits of the second HARQ-ACK is 1 bit or indicating that the number of bits of the second HARQ-ACK is determined according to the fallback mode, and the eleventh indication state being used to indicate that the number of bits of the second HARQ-ACK is determined according to the semi-static HARQ-ACK codebook size.

52. The network device according to claim 48 or 51, wherein: The first condition includes: There is downlink transmission corresponding to the second HARQ-ACK; or There is a downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or The first uplink channel and the second uplink channel overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK; The second condition includes: There is no downlink transmission corresponding to the second HARQ-ACK; or There is no downlink transmission corresponding to the second HARQ-ACK scheduled by DCI; or The first uplink channel and the second uplink channel do not overlap in the time domain, wherein the second uplink channel is a channel carrying a second HARQ-ACK.

53. The network device according to claim 47, wherein: The receiving HARQ-ACK according to the first indication field includes: Determining, according to the first indication field, a number of bits of the second HARQ-ACK; HARQ-ACK reception is performed according to the number of bits of the second HARQ-ACK.

54. The network device according to claim 53, wherein: The receiving the HARQ-ACK according to the number of bits of the second HARQ-ACK includes: receiving the first HARQ-ACK and the second HARQ-ACK simultaneously on the same channel according to the number of bits of the second HARQ-ACK; or, When the number of bits of the second HARQ-ACK is greater than 0 or it is determined that the terminal transmits the second HARQ-ACK, simultaneously receiving the first HARQ-ACK and the second HARQ-ACK on the same channel according to the number of bits of the second HARQ-ACK; or When the number of bits of the second HARQ-ACK is 0 or it is determined that the terminal does not transmit the second HARQ-ACK, the first HARQ-ACK is received on the first uplink channel.

55. The network device according to claim 53, wherein: The determining, according to the first indication field, the number of bits of the second HARQ-ACK includes: When the first uplink channel carrying the first HARQ-ACK overlaps with the second uplink channel carrying the second HARQ-ACK in the time domain, the number of bits of the second HARQ-ACK is determined according to the first indication field.

56. The network device according to claim 47, wherein The priority of the first uplink channel is higher than the priority of the second uplink channel carrying the second HARQ-ACK; or The priority of the first HARQ-ACK is higher than the priority of the second HARQ-ACK; or The first HARQ-ACK is a HARQ-ACK for a unicast service, and the second HARQ-ACK is a HARQ-ACK for a multicast service.

57. The network device according to claim 47, wherein: The first uplink channel is one of a physical uplink control channel PUCCH and a physical uplink shared channel PUSCH, the second uplink channel carrying the second HARQ-ACK is one of PUCCH and PUSCH, and the channel types of the first uplink channel and the second uplink channel are the same or different.

58. The network device according to claim 47, wherein: Whether the first indication field exists in the first DCI is determined according to the configuration of higher layer signaling; or By default, the first indication field always exists in the first DCI.

59. The network device according to claim 47, wherein In a case where the first uplink channel is a PUCCH, the first DCI is a DCI for scheduling a PDSCH requiring HARQ-ACK feedback on the PUCCH, or the first DCI is a DCI for indicating a semi-persistent scheduling SPS physical downlink shared channel PDSCH release requiring HARQ-ACK feedback on the PUCCH; or In a case where the first uplink channel is a PUSCH, the first DCI is a DCI for scheduling the PUSCH.

60. The network device according to claim 47, wherein: When there are multiple first DCIs, the first indication fields in the multiple first DCIs are set to indicate the same value, or HARQ-ACK reception is performed according to the first indication field in the last DCI.

61. A terminal, characterized in that: include: A receiving unit, configured for a terminal to receive first downlink control information DCI, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK and whether a second HARQ-ACK exists; a transmission unit, configured to perform HARQ-ACK transmission according to the first indication field; The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

62. A network device, characterized in that include: A sending unit, configured for a network device to send first downlink control information DCI, where a first indication field of the first DCI is used to determine at least one of the following: the number of bits of a second hybrid automatic repeat request confirmation HARQ-ACK and whether a second HARQ-ACK exists; a receiving unit, configured to perform HARQ-ACK reception according to the first indication field; The first DCI is the DCI corresponding to the first uplink channel carrying the first HARQ-ACK, and the second HARQ-ACK is the HARQ-ACK multiplexed and transmitted with the first HARQ-ACK.

63. A processor-readable storage medium, characterized in that The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the uplink control information transmission method described in any one of claims 1 to 16, or the computer program is used to enable the processor to execute the uplink control information receiving method described in any one of claims 17 to 30.

Images