WO2020057566A1 - 一种harq-ack的传输方法、终端设备及网络设备 - Google Patents

一种harq-ack的传输方法、终端设备及网络设备 Download PDF

Info

Publication number
WO2020057566A1
WO2020057566A1 PCT/CN2019/106511 CN2019106511W WO2020057566A1 WO 2020057566 A1 WO2020057566 A1 WO 2020057566A1 CN 2019106511 W CN2019106511 W CN 2019106511W WO 2020057566 A1 WO2020057566 A1 WO 2020057566A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
ack
pusch
transmission
downlink transmission
Prior art date
Application number
PCT/CN2019/106511
Other languages
English (en)
French (fr)
Inventor
高雪娟
Original Assignee
电信科学技术研究院有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 电信科学技术研究院有限公司 filed Critical 电信科学技术研究院有限公司
Priority to JP2021516465A priority Critical patent/JP7303291B2/ja
Priority to KR1020217011877A priority patent/KR102665094B1/ko
Priority to US17/278,332 priority patent/US11290217B2/en
Priority to EP19863862.9A priority patent/EP3855650A4/en
Publication of WO2020057566A1 publication Critical patent/WO2020057566A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1664—Details of the supervisory signal the supervisory signal being transmitted together with payload signals; piggybacking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a HARQ-ACK transmission method, a terminal device, and a network device.
  • the wireless air interface technology supports the repeated transmission of the Physical Uplink Shared Channel (PUSCH), and also supports the physical uplink control channel (Physical Uplink).
  • PUSCH Physical Uplink Shared Channel
  • Physical Uplink Physical Uplink control channel
  • UCI Uplink Control Information
  • PDCCH Physical Downlink Control Channel
  • the embodiments of the present application provide a HARQ-ACK transmission method, a terminal device, and a network device, which are used to provide a new mechanism for specifying how to transmit HARQ on a PUSCH configured with repeated transmissions or multiple PUSCHs scheduled by the same PDCCH. -ACK.
  • a HARQ-ACK transmission method includes: if the HARQ-ACK is transmitted on at least one PUSCH other than the first PUSCH among a plurality of PUSCHs corresponding to a PDCCH, When determining the HARQ-ACK, a downlink allocation index (DAI) in a downlink control information (DCI) format used by the PDCCH is ignored; and the determined HARQ-ACK is transmitted on the at least one PUSCH.
  • DCI downlink allocation index
  • DCI downlink control information
  • the terminal device may ignore the DAI in the DCI format used by the PDCCH and determine the bearer carried on the multiple PUSCHs.
  • HARQ-ACK That is, a new mechanism is provided to clarify how to transmit HARQ-ACK on a PUSCH configured with repeated transmission or multiple PUSCHs scheduled by the same PDCCH.
  • the multiple PUSCHs are repeated transmissions of the same PUSCH or transmission block (TB); or the multiple PUSCHs are multiple independent PUSCH transmissions scheduled by the same PDCCH.
  • multiple situations for multiple PUSCHs there may be multiple situations for multiple PUSCHs. For example, it may be repeated transmission of the same PUSCH, or repeated transmission of TB, or transmission of multiple independent PUSCHs scheduled by the same PDCCH. In any case, it applies, and the scope of application is wide.
  • the DCI format is DCI format 0_1.
  • ignoring the DAI in the DCI format used by the PDCCH when determining the HARQ-ACK includes: determining the HARQ- according to a determination manner in which the HARQ-ACK is transmitted on a PUSCH where there is no corresponding PDCCH. ACK; or, determining the HARQ-ACK according to the determination method of the HARQ-ACK transmission on the PUCCH, and replacing the configuration parameter of the HARQ-ACK corresponding to the PUCCH with the configuration parameter of the HARQ-ACK corresponding to the PUSCH, wherein the The configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • the HARQ-ACK is the HARQ-ACK of the one downlink transmission or the one SPS PDSCH; otherwise (i.e., only one downlink transmission requiring HARQ-ACK transmission on the PUSCH is received and the The downlink transmission is scheduled by the PDCCH using the DCI format 1_0 and the DAI in the DCI format 1_0 is not 1, or only one downlink transmission requiring HARQ-ACK transmission on the PUSCH is received and the downlink transmission is not performed by the PDCCH using the DCI format 1_0 Scheduled, or received more than one Downlink transmissions, or received a downlink transmission and an SPS PDSCH), the HARQ-ACK is a semi-static HARQ-ACK code determined according to a downlink transmission candidate time domain resource set and a feedback timing set between the downlink transmission and the HARQ-ACK this.
  • ignoring the DAI in the DCI format used by the PDCCH when determining the HARQ-ACK includes: when using a semi-static HARQ-ACK codebook, if no HARQ-ACK is received and transmitted on the PUSCH, ACK downlink transmission or SPS PDSCH, it is determined not to transmit HARQ-ACK on PUSCH; and / or, if at least one downlink transmission requiring HARQ-ACK transmission on PUSCH is received, the HARQ_ACK is based on the downlink transmission candidate time domain
  • a semi-static HARQ-ACK codebook determined by a resource set and a feedback timing set between downlink transmission and HARQ-ACK, or, according to a determination method of HARQ-ACK transmission on a PUCCH, determining the HARQ-ACK and corresponding to the PUCCH
  • the configuration parameters of the HARQ-ACK are replaced with the configuration parameters of the HARQ-ACK corresponding to the PUSCH, where the configuration parameters are used to indicate whether the HARQ-
  • ignoring the DAI in the DCI format used by the PDCCH when determining the HARQ-ACK includes: when using a dynamic HARQ-ACK codebook, if no HARQ-ACK needs to be transmitted on the PUSCH Downlink transmission or SPS PDSCH, it is determined that HARQ-ACK is not transmitted on the PUSCH; and / or, if at least one downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is received, the HARQ-ACK is based on the downlink A dynamic HARQ-ACK codebook determined by DAI in the corresponding PDCCH is transmitted.
  • the downlink transmission is at least one of PDSCH and semi-persistently scheduled SPS PDSCH release.
  • a HARQ-ACK transmission method includes: if the HARQ-ACK is transmitted on at least one PUSCH other than the first PUSCH among a plurality of PUSCHs corresponding to a PDCCH, When determining the number of feedback bits of the HARQ-ACK, the downlink allocation index (DAI) in the downlink control information DCI format used by the PDCCH is ignored; and received on the at least one PUSCH according to the number of feedback bits of the HARQ-ACK HARQ-ACK.
  • DAI downlink allocation index
  • the multiple PUSCHs are repeated transmissions of the same PUSCH or transport block TB; or, the multiple PUSCHs are multiple independent PUSCH transmissions scheduled by the same PDCCH.
  • the DCI format is DCI grid 0_1.
  • ignoring the DAI in the DCI format used by the PDCCH when determining the number of feedback bits of the HARQ-ACK includes: determining according to a determination manner of HARQ-ACK transmission on a PUSCH where there is no corresponding PDCCH. The number of feedback bits of the HARQ-ACK; or determining the number of feedback bits of the HARQ-ACK according to the determination method of the HARQ-ACK transmission on the PUCCH, and replacing the configuration parameter of the HARQ-ACK corresponding to the PUCCH with the PUSCH corresponding A configuration parameter of HARQ-ACK, wherein the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • ignoring the DAI in the DCI format used by the PDCCH when determining the number of feedback bits of the HARQ-ACK includes: when using a semi-static HARQ-ACK codebook, if there is no need to send anything on the PUSCH For downlink transmission of HARQ-ACK or SPS PDSCH, it is determined that HARQ-ACK is not received on the PUSCH;
  • the number of feedback bits of the HARQ-ACK is the number of feedback bits of HARQ-ACK of the one downlink transmission or the one SPS PDSCH; otherwise, the HARQ-ACK
  • the number of feedback bits is the number of feedback bits of the semi-static HARQ-ACK codebook determined according to the downlink transmission candidate time domain resource set and the feedback timing set between the downlink transmission and HARQ-ACK.
  • ignoring the DAI in the DCI format used by the PDCCH when determining the number of feedback bits of the HARQ-ACK includes: when using a semi-static HARQ-ACK codebook, if there is no need to send anything on the PUSCH Transmit HARQ-ACK downlink transmission or SPS PDSCH, determine that HARQ-ACK is not received on PUSCH; and / or, if at least one downlink transmission that requires HARQ-ACK transmission on PUSCH is sent, the HARQ-ACK feedback
  • the number of bits is the number of feedback bits of the semi-static HARQ-ACK codebook determined according to the downlink transmission candidate time domain resource set and the feedback timing set between the downlink transmission and HARQ-ACK, or the determination of transmission on the PUCCH based on HARQ-ACK Manner, determining the number of feedback bits of the HARQ-ACK, and replacing the configuration parameter of the HARQ-ACK corresponding to the PUCCH with the configuration parameter of the HARQ-ACK corresponding to the PU
  • ignoring the DAI in the DCI format used by the PDCCH when determining the number of feedback bits of the HARQ-ACK includes: when using a dynamic HARQ-ACK codebook, if no transmission is required, transmission on the PUSCH is required HARQ-ACK downlink transmission or SPS PDSCH, it is determined that HARQ-ACK is not received on the PUSCH; and / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is sent, the HARQ-ACK feedback bit The number is the number of feedback bits of the dynamic HARQ-ACK codebook determined according to the DAI in the PDCCH corresponding to the downlink transmission.
  • the downlink transmission is at least one of PDSCH and semi-persistent scheduling (SPS PDSCH) release.
  • SPS PDSCH semi-persistent scheduling
  • a terminal device includes: a memory for storing instructions; a processor for reading the instructions in the memory, and performs the following process: if HARQ-ACK Transmission on at least one PUSCH except the first PUSCH among the three PUSCHs, the downlink allocation index (DAI) in the downlink control information DCI format used by the PDCCH is ignored when determining the HARQ-ACK; The transmission of the determined HARQ-ACK on at least one PUSCH;
  • DAI downlink allocation index
  • a transceiver for receiving and sending data under the control of the processor.
  • the multiple PUSCHs are repeated transmissions of the same PUSCH or transport block TB; or, the multiple PUSCHs are multiple independent PUSCH transmissions scheduled by the same PDCCH.
  • the DCI format is DCI format 0_1.
  • the processor is specifically configured to: determine the HARQ-ACK according to a determination method of HARQ-ACK transmission on a PUSCH where there is no corresponding PDCCH; or, determine the transmission method of HARQ-ACK on PUCCH To determine the HARQ-ACK, and replace the configuration parameter of the HARQ-ACK corresponding to the PUCCH with the configuration parameter of the HARQ-ACK corresponding to the PUSCH, where the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • the HARQ-ACK is the HARQ-ACK of the one downlink transmission or the one SPS PDSCH; otherwise, the HARQ-ACK
  • a semi-static HARQ-ACK codebook is determined according to a downlink transmission candidate time domain resource set and a feedback timing set between downlink transmission and HARQ-ACK.
  • the processor is specifically configured to: when using a semi-static HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is received, determine not to transmit on the PUSCH HARQ-ACK; and / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is received, the HARQ-ACK is based on the downlink transmission candidate time domain resource set and the feedback between the downlink transmission and the HARQ-ACK
  • the semi-static HARQ-ACK codebook determined by the timing set, or the HARQ-ACK is determined according to the determination method of the HARQ-ACK transmission on the PUCCH, and the configuration parameter of the HARQ-ACK corresponding to the PUCCH is replaced with the HARQ corresponding to the PUSCH -An ACK configuration parameter, wherein the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • the processor is specifically configured to: when using a dynamic HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is received, determine that HARQ is not transmitted on the PUSCH -ACK; and / or, if at least one downlink transmission or SPS PDSCH requiring HARQ-ACK transmission on the PUSCH is received, the HARQ-ACK is a dynamic HARQ-ACK codebook determined according to DAI in the PDCCH corresponding to the downlink transmission .
  • the downlink transmission is at least one of PDSCH and semi-persistently scheduled SPS PDSCH release.
  • a network device includes: a memory for storing instructions; a processor for reading the instructions in the memory, and performing the following process: if HARQ-ACK Transmitting on at least one PUSCH other than the first PUSCH among the plurality of PUSCHs, ignoring the downlink allocation index DAI in the downlink control information DCI format used by the PDCCH when determining the number of HARQ-ACK feedback bits Receiving a HARQ-ACK according to the number of feedback bits of the HARQ-ACK on a PUSCH; a transceiver for receiving and sending data under the control of the processor.
  • the multiple PUSCHs are repeated transmissions of the same PUSCH or transport block TB; or, the multiple PUSCHs are multiple independent PUSCH transmissions scheduled by the same PDCCH.
  • the DCI format is DCI grid 0_1.
  • the processor is specifically configured to: determine the number of feedback bits of the HARQ-ACK according to a determination manner of HARQ-ACK transmission on a PUSCH where there is no corresponding PDCCH; or, on the PUCCH according to the HARQ-ACK A transmission determining manner, determining the number of feedback bits of the HARQ-ACK, and replacing the configuration parameter of the HARQ-ACK corresponding to PUCCH with the configuration parameter of the HARQ-ACK corresponding to PUSCH, wherein the configuration parameter is used to indicate the Whether HARQ-ACK is spatially merged.
  • the number of feedback bits of the HARQ-ACK is the number of feedback bits of the HARQ-ACK of the one downlink transmission or the one SPS PDSCH; otherwise, the The number of HARQ-ACK feedback bits is the number of feedback bits of the semi-static HARQ-ACK codebook determined according to the downlink transmission candidate time domain resource set and the feedback timing set between the downlink transmission and HARQ-
  • the processor is specifically configured to: when using a semi-static HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is sent, determine that HARQ is not received on the PUSCH -ACK; and / or, if at least one downlink transmission that requires HARQ-ACK to be transmitted on the PUSCH is sent, the number of feedback bits of the HARQ-ACK is based on the downlink transmission candidate time domain resource set and between the downlink transmission and the HARQ-ACK.
  • the ACK configuration parameter is replaced with a HARQ-ACK configuration parameter corresponding to the PUSCH, where the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • the processor is specifically configured to: when using a dynamic HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that needs to transmit HARQ-ACK on the PUSCH is sent, determine that HARQ- is not received on the PUSCH ACK; and / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is sent, the number of feedback bits of the HARQ-ACK is a dynamic HARQ-ACK codebook determined according to DAI in the PDCCH corresponding to the downlink transmission The number of feedback bits.
  • the downlink transmission is at least one of PDSCH and semi-persistently scheduled SPS PDSCH release.
  • a terminal device includes: a determining unit configured to: if HARQ-ACK is transmitted on at least one PUSCH other than a first PUSCH among a plurality of PUSCHs corresponding to a PDCCH, When determining the HARQ-ACK, a downlink allocation index (DAI) in a downlink control information DCI format used by the PDCCH is ignored; a transmission unit is configured to transmit the determined HARQ-ACK on the at least one PUSCH.
  • DAI downlink allocation index
  • the multiple PUSCHs are repeated transmissions of the same PUSCH or transport block TB; or, the multiple PUSCHs are multiple independent PUSCH transmissions scheduled by the same PDCCH.
  • the DCI format is DCI format 0_1.
  • the determining unit is specifically configured to: determine the HARQ-ACK according to a determination method of HARQ-ACK transmission on a PUSCH where there is no corresponding PDCCH; or determine the transmission method of HARQ-ACK on a PUCCH To determine the HARQ-ACK, and replace the configuration parameter of the HARQ-ACK corresponding to the PUCCH with the configuration parameter of the HARQ-ACK corresponding to the PUSCH, where the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • the determining unit is specifically configured to: when using a semi-static HARQ-ACK codebook, if no downlink transmission or semi-persistent scheduling SPS physical downlink shared channel PDSCH that needs to transmit HARQ-ACK on the PUSCH is received , It is determined that HARQ-ACK is not transmitted on the PUSCH; and / or, if only one downlink transmission requiring HARQ-ACK transmission on the PUSCH is received and the downlink transmission is scheduled by the PDCCH using the DCI format 1_0 and the DCI format 1_0
  • DAI 1, or when only one SPS PDSCH that needs to transmit HARQ-ACK on PUSCH is received, the HARQ-ACK is the HARQ-ACK of the one downlink transmission or the one SPS PDSCH; otherwise, all The HARQ-ACK is to determine a semi-static HARQ-ACK codebook according to a downlink transmission candidate time domain resource set and a feedback timing set between the downlink transmission and the HARQ-ACK.
  • the determining unit is specifically configured to: when using a semi-static HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is received, determine not to transmit on the PUSCH HARQ-ACK; and / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is received, the HARQ-ACK is based on the downlink transmission candidate time domain resource set and the feedback between the downlink transmission and the HARQ-ACK
  • the semi-static HARQ-ACK codebook determined by the timing set, or the HARQ-ACK is determined according to the determination method of the HARQ-ACK transmission on the PUCCH, and the configuration parameter of the HARQ-ACK corresponding to the PUCCH is replaced with the HARQ corresponding to the PUSCH -An ACK configuration parameter, wherein the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • the determining unit is specifically configured to: when using a dynamic HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is received, determine that HARQ is not transmitted on the PUSCH -ACK; and / or, if at least one downlink transmission or SPS PDSCH requiring HARQ-ACK transmission on the PUSCH is received, the HARQ-ACK is a dynamic HARQ-ACK codebook determined according to DAI in the PDCCH corresponding to the downlink transmission .
  • the downlink transmission is at least one of PDSCH and semi-persistently scheduled SPS PDSCH release.
  • a network device includes: a determining unit configured to: if a HARQ-ACK is transmitted on at least one PUSCH except a first PUSCH among a plurality of PUSCHs corresponding to a PDCCH, When determining the number of feedback bits of the HARQ-ACK, the downlink allocation index DAI in the downlink control information DCI format used by the PDCCH is ignored; and a receiving unit is configured to perform the HARQ-ACK on the at least one PUSCH according to the HARQ-ACK.
  • the number of feedback bits is HARQ-ACK.
  • the multiple PUSCHs are repeated transmissions of the same PUSCH or transport block TB; or, the multiple PUSCHs are multiple independent PUSCH transmissions scheduled by the same PDCCH.
  • the DCI format is DCI grid 0_1.
  • the determining unit is specifically configured to determine the number of feedback bits of the HARQ-ACK according to a determination method of HARQ-ACK transmission on a PUSCH where there is no corresponding PDCCH; or, on the PUCCH according to the HARQ-ACK A transmission determining manner, determining the number of feedback bits of the HARQ-ACK, and replacing the configuration parameter of the HARQ-ACK corresponding to PUCCH with the configuration parameter of the HARQ-ACK corresponding to PUSCH, wherein the configuration parameter is used to indicate the Whether HARQ-ACK is spatially merged.
  • the number of feedback bits of the HARQ-ACK is the number of feedback bits of the HARQ-ACK of the one downlink transmission or the one SPS PDSCH; otherwise, the The number of HARQ-ACK feedback bits is the number of feedback bits of the semi-static HARQ-ACK codebook determined according to the downlink transmission candidate time domain resource set and the feedback timing set between the downlink transmission and HAR
  • the determining unit is specifically configured to: when using a semi-static HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is sent, determine that HARQ is not received on the PUSCH -ACK; and / or, if at least one downlink transmission that requires HARQ-ACK to be transmitted on the PUSCH is sent, the number of feedback bits of the HARQ-ACK is based on the downlink transmission candidate time domain resource set and between the downlink transmission and the HARQ-ACK.
  • the ACK configuration parameter is replaced with a HARQ-ACK configuration parameter corresponding to the PUSCH, where the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • the determining unit is specifically configured to: when using a dynamic HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that needs to transmit HARQ-ACK on the PUSCH is sent, determine that HARQ- is not received on the PUSCH ACK; and / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is sent, the number of feedback bits of the HARQ-ACK is a dynamic HARQ-ACK codebook determined according to DAI in the PDCCH corresponding to the downlink transmission The number of feedback bits.
  • the downlink transmission is at least one of PDSCH and semi-persistently scheduled SPS PDSCH release.
  • a computer storage medium on which a computer program is stored, and when the computer program is executed by a processor, the method according to any one of the first aspect or the second aspect is implemented.
  • the terminal device may ignore the DAI in the DCI format used by the PDCCH and determine the HARQ-ACK. That is, a new mechanism is provided to clarify how to transmit HARQ-ACK on a PUSCH configured with repeated transmission or multiple PUSCHs scheduled by the same PDCCH.
  • FIG. 1 is a schematic flowchart of a HARQ-ACK transmission method according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of scheduling and feedback according to the first embodiment of the present application.
  • FIG. 3 is a schematic diagram of scheduling and feedback according to the second embodiment provided by the embodiment of this application.
  • FIG. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • LTE Long Term Evolution
  • terminal equipment such as user equipment (UE)
  • UE user equipment
  • the time domain of the PUCCH and PUSCH carrying the UCI There may be overlapping resources. If the UE supports simultaneous transmission of PUCCH and PUSCH and the high-level signaling configuration can perform simultaneous transmission of PUCCH and PUSCH, then PUCCH and PUSCH can be transmitted at the same time, such as transmitting UCI on PUCCH and transmitting data on PUSCH.
  • the UCI carried on PUCCH will be transferred to PUSCH and the information originally carried on PUSCH will be multiplexed and transmitted on PUSCH.
  • the UCI includes at least Hybrid Automatic Repeat Request (ARQ-ACK), Channel State Information (CSI), and Scheduling Request (SR).
  • DCI Downlink Control Information
  • UL DAI The Bit Downlink Assignment Index
  • the UE determines that there is no HARQ-ACK transmission on the PUSCH; when the UE receives the required When performing downlink transmission of HARQ-ACK feedback in the time domain location where the PUSCH is located, the UE determines that there is a HARQ-ACK transmission determined on the PUSCH according to the configured codebook.
  • DAI is included in DCI format 0_1 to indicate whether HARQ-ACK transmission exists on PUSCH, that is, to avoid packet loss due to downlink transmission As a result, the terminal and the base station have different understandings on whether there is HARQ-ACK transmission on the PUSCH.
  • DCI format 0_1 contains 2 or 4 bits of DAI, which is used to indicate the total number of bits of HARQ-ACK transmission on the PUSCH.
  • each sub-codebook corresponds to a 2-bit DAI for a total of 4-bit DAI.
  • the PDCCH in the PDCCH monitoring opportunity (Monitoring Occasion) set corresponding to the dynamic codebook (a PDCCH for scheduling PDSCH or indicating the release of downlink-persistent scheduling (Semi-Persistent Scheduling, SPS) resources)
  • the DCI used (for example, DCI format 1_0 or 1_1) also contains DAI, which is usually called DL DAI. When single carrier is used, it only contains 2 bit DAI, and when it is multi carrier, it includes 4 bit DAI. It is divided into 2 bits C-DAI and 2 Bit T-DAI is used to indicate the order and size of the codebook.
  • the 5G NR system supports the repeated transmission of the PUSCH, and also supports the transfer of UCI carried on the PUCCH to the PUSCH for transmission when the time domain resources of the PUCCH and the PUSCH overlap, thereby avoiding the simultaneous transmission of multiple channels.
  • the PDCCH in slot n simultaneously schedules N PUSCH transmissions in N slots starting from slot n + K2, or given N K2 values, Scheduling N PUSCH transmissions in N time slots determined based on N K2 values.
  • the scheduling information of the PUSCH in each time slot can be the same or different.
  • the PUSCH in each time slot carries an independent TB instead of one. Repeated transmission of TB, that is, one PDCCH carries scheduling information for scheduling multiple PUSCH transmissions in multiple time slots simultaneously.
  • an embodiment of the present application provides a new HARQ-ACK transmission method.
  • the terminal device can Ignore the DAI in the DCI format used by the PDCCH, and determine the HARQ-ACK carried on multiple PUSCHs. That is, a new mechanism is provided to clarify how to transmit HARQ-ACK on a PUSCH configured with repeated transmission or multiple PUSCHs scheduled by the same PDCCH.
  • an embodiment of the present application provides a HARQ-ACK transmission method, and a flow of the method is described as follows. Since the HARQ-ACK transmission method involves the interaction process between the network device and the terminal device, in the following flow description, the processes performed by the network device and the terminal device will be described together.
  • the manner of determining the HARQ-ACK carried on the PUSCH includes the following two cases: step S101 and step S102:
  • the HARQ-ACK is transmitted on the first PUSCH of multiple PUSCHs corresponding to a PDCCH, determine the HARQ-ACK carried on the first PUSCH according to the DAI in the DCI format used by the PDCCH.
  • the DAI in the DCI format used by the PDCCH is ignored when determining the HARQ-ACK.
  • the terminal device determines the HARQ-ACK carried on the PUSCH, and then S103, the determined HARQ-ACK is transmitted on the PUSCH. For example, if the terminal device determines the HARQ-ACK carried on the first PUSCH in the case of S101, it transmits the HARQ-ACK on the first PUSCH. If the terminal device determines the HARQ-ACK carried on the PUSCH other than the first PUSCH in the case of S102, it transmits the HARQ-ACK on the other PUSCH.
  • multiple PUSCHs may be repeated transmission of the same PUSCH or transmission block (TB). That is, when a PUSCH is configured to occupy multiple transmission time units for transmission, the PUSCH in each time unit carries the same TB, where the transmission time unit can be a time slot or a microslot, of course, it can also be other defined transmission time units; multiple PUSCHs can also be multiple independent PUSCH transmissions scheduled by the same PDCCH, that is, multiple uplink transmission times Unit joint scheduling means that one PDCCH simultaneously carries scheduling signaling corresponding to multiple PUSCHs, and each PUSCH carries independent TBs.
  • the DCI format may be a DCI format including DAI, for example, the DCI format 0_1.
  • the DAI in the DCI format used by the PDCCH is ignored, and the following methods exist:
  • First method Determine the HARQ-ACK according to the determination method of the HARQ-ACK transmission on a PUSCH (ie, a PUSCH without scheduling signaling, that is, a PUSCH without UL grant) corresponding to a PDCCH.
  • a PUSCH ie, a PUSCH without scheduling signaling, that is, a PUSCH without UL grant
  • the second method Determine the HARQ-ACK according to the determination method of the HARQ-ACK transmission on the PUCCH, and replace the configuration parameters of the HARQ-ACK corresponding to the PUCCH with the configuration parameters of the HARQ-ACK corresponding to the PUSCH.
  • HARQ-ACK is spatially merged. That is, it is assumed that the HARQ-ACK is transmitted on the PUCCH, and the HARQ-ACK sequence is determined in a corresponding manner.
  • the HARQ-ACK space combination configuration parameter for PUCCH in this manner needs to be replaced with the HARQ-ACK space combination configuration parameter for PUSCH.
  • the HARQ-ACK is a HARQ-ACK of a downlink transmission or an SPS PDSCH (that is, only a 1-bit HARQ-ACK is transmitted); otherwise, the HARQ-ACK is based on the downlink transmission candidate time domain resources
  • the set and the feedback timing set between downlink transmission and HARQ-ACK determine the semi-static HARQ-ACK codebook.
  • the fourth method when using a semi-static HARQ-ACK codebook:
  • HARQ_ACK is a semi-static HARQ-ACK code determined according to the downlink transmission candidate time domain resource set and the feedback timing set between the downlink transmission and HARQ-ACK. This, or, according to the determination method of the HARQ-ACK transmission on the PUCCH, determine the HARQ-ACK, and replace the configuration parameters of the HARQ-ACK corresponding to the PUCCH with the configuration parameters of the HARQ-ACK corresponding to the PUSCH, where the configuration parameters are used for Indicates whether HARQ-ACK is spatially merged.
  • HARQ-ACK is a dynamic HARQ-ACK codebook determined according to DAI in the PDCCH corresponding to the downlink transmission.
  • the downlink transmission from the first mode to the fifth mode may be at least one of PDSCH and SPS PDSCH release (that is, a PDCCH indicating release of downlink SPS resources).
  • HARQ-ACK is transmitted on PUSCH: for example, there is no configuration or ability to support simultaneous transmission of PUCCH and PUSCH, and the PUCCH carrying HARQ-ACK and the PUSCH time domain resources overlap, and it meets UCI multiplexing (that is UCI can be transferred from PUCCH to PUSCH, so that PUCCH is not transmitted.
  • UCI multiplexing that is UCI can be transferred from PUCCH to PUSCH, so that PUCCH is not transmitted.
  • the earliest channel in PUCCH and PUSCH if the starting symbols of PUCCH and PUSCH are the same, the channel with the longest transmission length is selected.
  • Start symbol and transmission length are the same, then the first symbol of any one) is selected no earlier than a specific time point, where time point 1 is the last PDSCH / SPS based on the HARQ-ACK feedback required on the PUCCH
  • time point 1 is the last PDSCH / SPS based on the HARQ-ACK feedback required on the PUCCH
  • the position obtained by a predetermined length of time after the last symbol of the PDSCH release, where time point 2 is obtained based on the predetermined time length of the last symbol of the PDCCH corresponding to the PDSCH / SPS PDSCH release that requires HARQ-ACK feedback on the PUCCH position.
  • Embodiment 1 Please refer to FIG. 2, which is a schematic diagram of scheduling and feedback, which is applied to the above scenario.
  • Figure 2 uses a Frequency Division Duplex (FDD) system as an example.
  • FDD Frequency Division Duplex
  • the HARQ-ACK feedback timing set K1 ⁇ 2,3,4,5,6 ⁇ , and K1 is a time slot unit, and is used according to the time slot of a PDSCH transmission. Determine the time slot where the PUCCH transmission of the HARQ-ACK carrying the PDSCH is located.
  • FDD Frequency Division Duplex
  • the configuration uses semi-static HARQ-ACK codebook, according to the K1 set and the PDSCH candidate time domain resource set (the PDSCH candidate time domain resource set can be represented as a pre-configured one)
  • the table contains multiple rows, each row corresponding to a time slot in which the PDSCH is located, and the time domain position in the time slot, such as the configuration information of the start symbol position and the symbol length.
  • the time slot in which the PDSCH is located is determined by the scheduling timing K0.
  • K0 represents the time slot interval between the PDCCH scheduling the PDSCH and the PDSCH. It can be determined that the semi-static codebook corresponding to each uplink slot shown in FIG.
  • each PDSCH has Corresponding to 1-bit HARQ-ACK, the size of the semi-static codebook corresponding to each time slot is 5 bits.
  • the base station sends a PDCCH (UL grant) using DCI format 0_1 in time slot n-1 to schedule the terminal device to perform repeated PUSCH transmission in time slots n to n + 3, that is, the PUSCH bearer in each time slot is the same.
  • TB and use the same time-frequency domain resources and MCS and other parameters.
  • HARQ-ACK feedback is required in slot n, then the network device will schedule the PUSCH in the DCI format 0_1
  • the 1-bit DAI is set to 0, indicating that there is no HARQ-ACK on the PUSCH.
  • the terminal device does not support or is not configured for simultaneous transmission of PUCCH and PUSCH, determine HARQ-ACK as follows:
  • the PDSCH needs to perform HARQ-ACK feedback in slot n, and according to the 1-bit DAI in the DCI format 0_1 of the scheduled PUSCH, it is determined that no HARQ-ACK is transmitted on PUSCH. It should be noted that no downlink transmission or SPS PDSCH is received in the downlink transmission opportunity set corresponding to the semi-static HARQ-ACK codebook (for example, the downlink corresponding to the semi-static HARQ-ACK codebook in time slot n in FIG. 2
  • the transmission opportunity set is that there is one downlink transmission opportunity in each slot from time slot n-6 to time slot n-2, and a total of 5 downlink transmission opportunities.
  • the downlink transmission opportunity set is based on the K1 set and the candidate time domain resources of the PDSCH.
  • the set is determined, the same applies hereinafter, and no further details are received)
  • No HARQ-ACK needs to be transmitted on the PUSCH that is, whether the HARQ-ACK feedback is performed in the time slot where the PUSCH is located is determined according to the corresponding K1 value of the downlink transmission.
  • the determination is yes In order to transmit downlink transmission of HARQ-ACK on PSUCH, the same applies hereinafter, and is not repeated here.
  • the PDSCH in slot n-5 needs to perform HARQ-ACK feedback in slot n + 1, and it is assumed that the PUCCH resource and slot n + carrying the HARQ-ACK
  • the terminal device does not support or is not configured for simultaneous transmission of PUCCH and PUSCH, when the UCI multiplexing time condition is met, the HARQ-ACK on PUCCH needs to be transferred to PUSCH for transmission and no longer transmitted. PUCCH.
  • it is not considered whether the 1-bit DAI value in the DCI format 0_1 for scheduling the repeated transmission of the PUSCH is 0, and there are the following further methods:
  • the HARQ-ACK is transmitted on the PUSCH, that is, the 5-bit HARQ-ACK is transmitted.
  • a NACK (as a placeholder) is generated for a location where the PDSCH is not received.
  • Method 2 Determine the HARQ-ACK according to the determination method of the HARQ-ACK transmission on the PUCCH. Specifically, according to the transmission mode of the HARQ-ACK on the PUCCH, the configuration parameter of whether the HARQ-ACK corresponding to the PUSCH is spatially merged is replaced with the configuration parameter of whether the HARQ-ACK corresponding to the PUCCH is spatially merged.
  • the first embodiment does not involve spatial merging. Therefore, determining the HARQ-ACK directly according to the transmission mode on the PUCCH specifically includes:
  • HARQ-ACK feedback is performed on the PUSCH only for the one downlink transmission, that is, only the transmission is performed according to the above assumption 1-bit HARQ-ACK (semi-static codebook fallback). If the downlink transmission is scheduled by DCI format 1_0 and the DCI in DCI format 1_0 is not 1, or if the downlink transmission is not scheduled by DCI format 1_0, or if more than one downlink transmission and / or SPS PDSCH is received, the time slot n + The size of the corresponding semi-static codebook is 1.
  • HARQ-ACK is transmitted on the PUSCH, that is, 5-bit HARQ-ACK is transmitted. Among them, a NACK (as a placeholder) is generated for a location where the PDSCH is not received.
  • Method 3 Determine HARQ-ACK according to whether only one downlink transmission is received, and the specific DCI format and DAI value. Since only one downlink transmission is received, it is determined according to whether the downlink transmission is scheduled by DCI format 1_0 and whether the DCI in DCI format 1_0 is 1. Whether to transmit only the HARQ-ACK of the one downlink transmission on the PUSCH, the specific steps are the same Mode 1 or Mode 2 will not be repeated here.
  • Method 4 The HARQ-ACK is always transmitted on the PUSCH according to the semi-static codebook corresponding to the time slot n + 1, that is, a 5-bit HARQ-ACK is transmitted, where a NACK is generated at a location where no PDSCH is received.
  • receiving one or more downlink transmissions is a downlink transmission that requires HARQ-ACK to be transmitted on the PUSCH in a set of downlink transmission opportunities corresponding to the semi-static HARQ-ACK codebook.
  • time slot n + 2 In time slot n + 2, according to the scheduling of the network equipment, PDSCH in time slots n-4 and n-3 needs to perform HARQ-ACK feedback in time slot n + 2, and it is assumed that the PUCCH resource carrying the HARQ-ACK and the The PUSCH resources in time slot n + 2 overlap. Because the terminal equipment does not support or is not configured for simultaneous transmission of PUCCH and PUSCH, it is necessary to transfer the HARQ-ACK on PUCCH to PUSCH when the time conditions for UCI multiplex transmission are met. Transmission, and no longer transmit PUCCH. At this time, regardless of whether the 1-bit DAI value in the DCI format 0_1 that schedules the PUSCH repeated transmission is 0, the HARQ-ACK is determined as follows.
  • Method 1 Determine the HARQ-ACK according to the determination method of the HARQ-ACK transmission on the PUSCH where the corresponding PDCCH does not exist. That is, the PUSCH is processed according to the case where there is no corresponding PDCCH. Since more than one downlink transmission is received, it is determined that the HARQ-ACK is transmitted on the PUSCH according to the semi-static codebook corresponding to the time slot n + 2, that is, a 5-bit HARQ-ACK is transmitted. Among them, a NACK is generated at a location where the PDSCH is not received.
  • Method 2 According to the transmission mode of the HARQ-ACK on the PUCCH, and replace the configuration parameter of whether the HARQ-ACK corresponding to the PUCCH is spatially merged with the configuration parameter of whether the HARQ-ACK corresponding to the PUSCH is spatially merged.
  • the first embodiment does not involve spatial merging. Therefore, determining the HARQ-ACK directly according to the transmission mode on the PUCCH specifically includes:
  • the HARQ-ACK is transmitted on the PUSCH according to the semi-static codebook corresponding to the time slot n + 1, that is, a 5-bit HARQ-ACK is transmitted. Among them, a NACK is generated at a location where the PDSCH is not received.
  • Method 3 Determine HARQ-ACK according to whether only one downlink transmission is received, and the specific DCI format and DAI value. Since more than one downlink transmission is received, the HARQ-ACK is transmitted on the PUSCH according to the semi-static codebook corresponding to the time slot n + 1, that is, a 5-bit HARQ-ACK is transmitted. Among them, a NACK is generated at a location where the PDSCH is not received.
  • Method 4 The HARQ-ACK is always transmitted on the PUSCH according to the semi-static codebook corresponding to the time slot n + 1, that is, a 5-bit HARQ-ACK is transmitted. Among them, a NACK is generated at a location where the PDSCH is not received.
  • receiving one or more than one downlink transmission is receiving the downlink transmission that requires the HARQ-ACK to be transmitted on the PUSCH in the downlink transmission opportunity set corresponding to the semi-static HARQ-ACK codebook.
  • the manner in the time slot n + 3 is the same as the manner in the time slot n + 1, and details are not described herein again.
  • the network device determines whether there is HARQ-ACK on the PUSCH and how many bits of HARQ-ACK exist in each slot in the same manner as described above, and then performs HARQ-ACK reception on the PUSCH.
  • the DAI value is not taken into consideration, and HARQ-ACK feedback is directly performed according to the actual downlink transmission requirements, which can avoid the above problems.
  • the HARQ-ACK is always determined according to the UL DAI in the UL grant, it will cause redundant HARQ-ACK transmission, that is, the terminal device needs to generate a NACK as a placeholder transmission according to the information indicated by the UL DAI, but it does not actually Corresponding to any downlink transmission, the uplink transmission efficiency and system efficiency are reduced.
  • the DAI value is not considered, and HARQ-ACK feedback is directly performed according to the actual downlink transmission requirements, which can avoid the above problems.
  • Embodiment 2 Please refer to FIG. 3, which is a schematic diagram of scheduling and feedback, which is applied to the scenario described above.
  • Figure 3 also uses a Frequency Division Duplex (FDD) system as an example.
  • FDD Frequency Division Duplex
  • FDD Frequency Division Duplex
  • This set contains 4 possible The position of the PDCCH is detected, and a PDCCH may be received at each position where the PDCCH is detected. It is further possible to determine one of the candidate PDSCH time domain resource sets according to the PDSCH time domain resource indicator field carried in the PDCCH.
  • the time slot is determined according to K0.
  • K0 the time domain location of the PDSCH and the time slot in which the PDSCH is transmitted.
  • each candidate PDSCH time domain resource in the PDSCH candidate time domain resource set it may have the same or different K0 value.
  • the PDCCH scheduled in the PDSCH transmission or the PDCCH indicating downlink SPS resource release received in the PDCCH monitoring set corresponding to each uplink slot may be carried in the PDCCH.
  • the DAI value determines the size of the dynamic codebook corresponding to an uplink time slot.
  • the above PDCCH only includes a 2-bit DAI, and the DAI accumulates in a time-domain scheduling order.
  • the DAI in the last PDCCH received it can be known that an uplink slot corresponds to the PDSCH and indicates the release of SPS resources
  • the number of PDCCHs, so that the size of the HARQ-ACK Codebook in the uplink slot can be known.
  • the network device sends a PDCCH (UL grant) using DCI format 0_1 in time slot n-1 to schedule the terminal device to perform repeated PUSCH transmission in time slots n to n + 3, that is, the PUSCH bearer in each time slot
  • the same TB uses the same time-frequency domain resources and MCS and other parameters.
  • there are 3 PDCCHs in the PDCCH monitoring set i.e., timeslot n-7 to timeslot n-4) corresponding to uplink timeslot n.
  • Each of the three PDSCH transmissions is scheduled to require HARQ-ACK feedback in uplink timeslot n.
  • the network device sets the 2-bit DAI in the DCI format 0_1 of the scheduling PUSCH sent in slot n-1 to 3 (depending on the codebook, different UL grants include UL DAI with different number of bits), indicating that there are 3 corresponding PUSCH HARQ-ACK feedback for PDSCH. Assuming that the terminal device does not support or is not configured for simultaneous transmission of PUCCH and PUSCH, determine HARQ-ACK as follows:
  • the terminal device receives HARQ-ACK feedback in time slot n after receiving three downlink transmissions, and the DL DAI (that is, the DAI in the PDCCH scheduling downlink transmission) in the last downlink transmission is indicated as 3.
  • the PUCCH resource carrying the HARQ-ACK overlaps with the PUSCH resource in slot n + 1. Since the terminal device does not support or is not configured for simultaneous transmission of PUCCH and PUSCH, it is necessary to transfer the HARQ-ACK on PUCCH to PUSCH. Transmit and no longer transmit PUCCH.
  • the terminal device schedules the DAI in the uplink transmission PDCCH according to the 2-bit UL in the DCI format 0_1 of the PUSCH scheduling schedule to be 3, which is consistent with the actual number of downlink transmissions received, and then determines to transmit 3 on the PUSCH according to the UL DAI.
  • Bit HARQ-ACK (assuming that each PDSCH corresponds to a 1-bit HARQ-ACK, of course, in other embodiments, each PDSCH may also correspond to a multi-bit HARQ-ACK according to the PDSCH transmission configuration).
  • the terminal device has lost the PDCCH in time slot n-5, it is determined that there are only 2 downlink transmissions according to the DL in the last received downlink transmission (in time slot n-6), and at this time the UL DAI (indicated as 3, it can be determined that there is a downlink transmission loss, according to UL, DAI needs to perform HARQ-ACK feedback on the PUSCH according to 3 downlink transmissions, that is, a 3-bit HARQ-ACK is still generated and transmitted on the PUSCH.
  • the last 1 bit generates a NACK as a HARQ-ACK for downlink transmission to determine packet loss.
  • Method 1 Determine the HARQ-ACK according to the determination method of the HARQ-ACK transmission on the PUSCH where the corresponding PDCCH does not exist. That is to say, the PUSCH is processed according to the absence of a corresponding PDCCH, that is, the number of downlink transmissions indicated by the DL and DAI in the last PDCCH received in the last PDCCH received in the occasion set corresponding to the time slot n + 1 is determined. The number of HARQ-ACK bits transmitted on the PUSCH in slot n + 1, that is, a 2-bit HARQ-ACK is generated at this time.
  • Method 2 According to the transmission mode of the HARQ-ACK on the PUCCH, and replace the configuration parameter of whether the HARQ-ACK corresponding to the PUCCH is spatially merged with the configuration parameter of whether the HARQ-ACK corresponding to the PUSCH is spatially merged.
  • the second embodiment does not involve spatial merging. Therefore, the terminal device may directly follow the PDCCH corresponding to the time slot n + 1 to monitor the number of downlink transmissions indicated by the DL DAI in the last PDCCH received in the occasion set. The number of HARQ-ACK bits transmitted on the PUSCH in slot n + 1, that is, a 2-bit HARQ-ACK is generated at this time.
  • Method 3 The codebook is always determined according to the DAI in the PDCCH using the downlink DCI format; that is, the number of downlink transmissions indicated by the DL in the last PDCCH received in the PDCCH monitoring set corresponding to the time slot n + 1 is directly received. Determine the number of HARQ-ACK bits that need to be transmitted on the PUSCH in slot n + 1, that is, a 2-bit HARQ-ACK is generated at this time.
  • the PDSCH in slot n-2 needs to perform HARQ-ACK feedback in slot n + 2. Assume that the PUCCH resource carrying the HARQ-ACK overlaps with the PUSCH resource in slot n + 2. Because the terminal device does not support or is not configured for simultaneous transmission of PUCCH and PUSCH, the terminal device needs to transfer the HARQ-ACK on the PUCCH to Transmitted on PUSCH, and no longer transmit PUCCH. At this time, regardless of the 2-bit DAI value in the DCI format 0_1 for scheduling the PUSCH repeated transmission, it is determined that the HARQ-ACK further exists in the following ways:
  • Method 1 Determine the HARQ-ACK according to the determination method of the HARQ-ACK transmission on the PUSCH where the corresponding PDCCH does not exist. That is to say, the PUSCH is scheduled according to the absence of a corresponding PDCCH, that is, the number of downlink transmissions indicated by the DL and DAI in the last PDCCH received in the PDCCH monitoring set in the occasion set corresponding to time slot n + 2 is determined. The number of HARQ-ACK bits transmitted on the PUSCH in slot n + 1, that is, a 1-bit HARQ-ACK is generated at this time.
  • Method 2 According to the transmission mode of the HARQ-ACK on the PUCCH, and replace the configuration parameter of whether the HARQ-ACK corresponding to the PUCCH is spatially merged with the configuration parameter of whether the HARQ-ACK corresponding to the PUSCH is spatially merged.
  • the second embodiment does not involve spatial merging. Therefore, the terminal device may directly follow the PDCCH corresponding to the time slot n + 2 to the number of downlink transmissions indicated by the DL and DAI in the last PDCCH received in the occasion set. The number of HARQ-ACK bits transmitted on the PUSCH in slot n + 1, that is, a 1-bit HARQ-ACK is generated at this time.
  • Method 3 The codebook is always determined according to the DAI in the PDCCH using the downlink DCI format; that is, the HARQ-ACK is determined directly according to the transmission mode on the PUCCH, that is, the last received in the PDCCH monitoring set corresponding to the time slot n + 2.
  • the number of downlink transmissions indicated by DL DAI in a PDCCH determines the number of HARQ-ACK bits that need to be transmitted on the PUSCH in slot n + 1, that is, a 1-bit HARQ-ACK is generated at this time.
  • the network device determines whether there is HARQ-ACK on the PUSCH and how many bits of HARQ-ACK exist in each slot in the same manner as described above, and then performs HARQ-ACK reception on the PUSCH.
  • the received one or more downlink transmissions are in the PDCCH detection opportunity set corresponding to the dynamic HARQ-ACK codebook (the PDCCH detection opportunity set is based on the K1 set and the PDSCH candidate time domain resource set
  • the K0 set is determined, for example, taking slot n as an example.
  • the PDSCH transmission opportunity can be determined to be n-K1, that is, time slots n-7 to n-4.
  • the PDSCH transmission opportunity is based on It is further determined that the PDCCH scheduled to be transmitted by these PDSCH transmission opportunities is n-K1-K0, that is, the time slots n-7 to n-4 are still as shown in FIG.
  • the PDCCH scheduling these downlink transmissions is received, and these downlink transmissions determine that HARQ-ACK feedback needs to be performed in the time slot where the PUSCH is located according to their corresponding K1, that is, these downlink transmissions need to transmit HARQ-ACK on the PUSCH.
  • the number of downlink transmissions indicated by the UL grant is less than The actual number of downlink transmissions received. If HARQ-ACK is determined according to the 2-bit UL DAI in the UL grant, some downlink transmissions cannot have HARQ-ACK feedback, which will affect downlink throughput and system efficiency. In the embodiments of the present application, the DAI value is not considered, and HARQ-ACK feedback is directly performed according to the actual downlink transmission requirements, which can avoid the above problems.
  • K1 the value of the dynamic indication of the indication domain in the PDCCH corresponding to the downlink transmission is taken as K1 as an example.
  • K1 can also be pre-defined or pre-configured by high-level signaling.
  • the downlink transmission is only based on the PDSCH as an example. It is also applicable to replace one or all of the PDSCHs with the PDCCH indicating the release of the downlink SPS resources.
  • the corresponding PDCCH for the downlink is the PDCCH indicating the release of the downlink SPS resources. itself.
  • the first embodiment and the second embodiment above only use FDD as an example. If TDD is also applicable, the only difference is that the PDSCH candidate set determined for the semi-static codebook may not be a continuous time slot. For the dynamic codebook, its PDCCH monitoring and occasion set It may not be in consecutive time slots, and these time slots may be excluded because there are no downlink transmission resources in some time slots or the downlink transmission resources are insufficient to support the candidate PDSCH time domain resource size.
  • the foregoing first and second embodiments only take a single carrier as an example, and the same applies to multiple carriers.
  • the PDCCH monitoring set on all carriers is determined based on the candidate PDSCH time domain resources (including K0) and the K1 set on each carrier, and the PDCCH scheduling downlink transmission includes a 4-bit DAI.
  • 2 bits are used for C-DAI, indicating the cumulative scheduling count of downlink transmissions in the frequency domain first and time domain
  • 2 bits are used for T-DAI, indicating the total number of downlink transmissions scheduled to the current moment, according to C-DAI and T- DAI can get the dynamic codebook corresponding to the final multi-carrier.
  • the PDCCH scheduling PUSCH includes 4-bit UL DAI, 2 bits corresponding to the TB-based subcodebook, and 2 bits corresponding Based on the CBG subcodebook, the total number of downlink transmissions in the corresponding subcodebook is indicated respectively.
  • the above-mentioned manner of generating HARQ-ACK transmitted on the PUSCH is also applicable.
  • the 4 PUSCHs correspond to the same scheduling information, but bear different TBs.
  • the DCI used in the UL grant contains multiple independent indication fields, corresponding to each of the 4 time slots. Time slots, the scheduling information in the four time slots may be different, and the above method is also applicable.
  • the HARQ-ACK transmission method provided in the embodiment of the present application is also applicable to a case where the same PDCCH jointly schedules N independent PUSCH transmissions. For example, if the PUCCH carrying HARQ-ACK overlaps with the first PUSCH, the HARQ-ACK carried on the PUSCH is determined according to the DAI in the DCI format used by the PDCCH; if the PUCCH carrying HARQ-ACK and its For PUSCHs other than the first PUSCH, there is overlap, the DAI in the DCI format used by the PDCCH is ignored, and the HARQ-ACK carried on the PUSCH is determined in the manner of transmitting the HARQ-ACK on the PUCCH.
  • the terminal device may ignore the DAI in the DCI format used by the PDCCH and determine the multiple PUSCHs.
  • HARQ-ACK That is, a new mechanism is provided to clarify how to transmit HARQ-ACK on a PUSCH configured with repeated transmission or multiple PUSCHs scheduled by the same PDCCH.
  • an embodiment of the present application provides a terminal device.
  • the terminal device includes: a memory 401, a processor 402, and a transceiver 403.
  • the memory 401 and the transceiver 403 may be connected to the processor 402 through a bus interface (as shown in FIG. 4 as an example), or may be connected to the processor 402 through a special connection line.
  • the memory 401 may be used to store a program.
  • the transceiver 403 is configured to transmit and receive data under the control of the processor.
  • the processor 402 may be used to read the program in the memory 401 and execute the following process: If HARQ-ACK is transmitted on at least one PUSCH except the first PUSCH among the plurality of PUSCHs corresponding to the PDCCH, determine the HARQ- In the ACK, the DAI in the DCI format used by the PDCCH is ignored; the determined HARQ-ACK is transmitted on at least one PUSCH.
  • multiple PUSCHs are repeated transmissions of the same PUSCH or transport block TB; or, multiple PUSCHs are multiple independent PUSCH transmissions scheduled by the same PDCCH.
  • the DCI format is DCI format 0_1.
  • the processor 402 is specifically configured to: determine the HARQ-ACK according to the determination method of the HARQ-ACK transmission on the PUSCH where the corresponding PDCCH does not exist; or determine the HARQ according to the determination method of the HARQ-ACK transmission on the PUCCH -ACK, and replace the HARQ-ACK configuration parameter corresponding to the PUCCH with the HARQ-ACK configuration parameter corresponding to the PUSCH, where the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • HARQ-ACK is HARQ-ACK for one downlink transmission or one SPS PDSCH; otherwise, HARQ-ACK is based on downlink transmission candidate time domain resource set and downlink The feedback timing set between transmission and HARQ-ACK determines the semi-static HARQ-ACK codebook.
  • the processor 402 is specifically configured to: when using a semi-static HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is received, determine that HARQ is not transmitted on the PUSCH -ACK; and / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is received, HARQ-ACK is determined according to a downlink transmission candidate time domain resource set and a feedback timing set between the downlink transmission and the HARQ-ACK Semi-static HARQ-ACK codebook, or, according to the determination method of HARQ-ACK transmission on PUCCH, determine HARQ-ACK, and replace the configuration parameter of HARQ-ACK corresponding to PUCCH with the configuration parameter of HARQ-ACK corresponding to PUSCH , Where the configuration parameter is used to indicate whether HARQ-ACK is spatially merged.
  • the processor 402 is specifically configured to: when using a dynamic HARQ-ACK codebook, if it does not receive any downlink transmission or SPS PDSCH that needs to transmit HARQ-ACK on the PUSCH, determine that HARQ- is not transmitted on the PUSCH ACK; and / or, if at least one downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is received, the HARQ-ACK is a dynamic HARQ-ACK codebook determined according to the DAI in the PDCCH corresponding to the downlink transmission.
  • the downlink transmission is at least one of PDSCH, semi-persistently scheduled SPS, and PDSCH release.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 402 and various circuits of the memory represented by the memory 401 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described further herein.
  • the bus interface provides an interface.
  • the transceiver 403 may be multiple elements, including a transmitter and a transceiver, providing a unit for communicating with various other devices on a transmission medium.
  • the processor 402 is responsible for managing the bus architecture and general processing, and the memory 401 can store data used by the processor 402 when performing operations.
  • the memory 401 may include a read-only memory (English: Read Only Memory, referred to as ROM), a random access memory (English: Random Access Memory, referred to as RAM), and a disk storage.
  • the memory 401 is used to store data required by the processor 402 during operation, that is, to store instructions that can be executed by at least one processor 402.
  • At least one processor 402 executes the instructions shown in FIG. 1-3 by executing the instructions stored in the memory 401.
  • the HARQ-ACK transmission method provided in the embodiment.
  • the number of the memories 401 is one or more.
  • the memory 401 is shown together in FIG. 4, but it needs to be known that the memory 401 is not a required functional module, so it is shown by a dotted line in FIG. 4.
  • the terminal device may include a determining unit 501 and a transmitting unit 502.
  • the determining unit 501 may be configured to ignore the DCI format used by the PDCCH when determining the HARQ-ACK if the HARQ-ACK is transmitted on at least one PUSCH except the first PUSCH among a plurality of PUSCHs corresponding to one PDCCH. DAI in.
  • the transmission unit 502 is configured to transmit the determined HARQ-ACK on at least one PUSCH.
  • multiple PUSCHs are repeated transmissions of the same PUSCH or transport block TB; or, multiple PUSCHs are multiple independent PUSCH transmissions scheduled by the same PDCCH.
  • the DCI format is DCI format 0_1.
  • the determining unit 501 is specifically configured to: determine the HARQ-ACK according to a determination method of HARQ-ACK transmission on a PUSCH where there is no corresponding PDCCH; or determine the HARQ according to a determination method of HARQ-ACK transmission on a PUCCH -ACK, and replace the HARQ-ACK configuration parameter corresponding to the PUCCH with the HARQ-ACK configuration parameter corresponding to the PUSCH, where the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • HARQ-ACK is HARQ-ACK for one downlink transmission or one SPS PDSCH; otherwise, HARQ-ACK is based on downlink transmission candidate time domain resource set and downlink The feedback timing set between transmission and HARQ-ACK determines the semi-static HARQ-ACK codebook.
  • the determining unit 501 is specifically configured to: when using a semi-static HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is received, determine that HARQ is not transmitted on the PUSCH -ACK; and / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is received, HARQ-ACK is determined according to a downlink transmission candidate time domain resource set and a feedback timing set between the downlink transmission and the HARQ-ACK Semi-static HARQ-ACK codebook, or, according to the determination method of HARQ-ACK transmission on PUCCH, determine HARQ-ACK, and replace the configuration parameter of HARQ-ACK corresponding to PUCCH with the configuration parameter of HARQ-ACK corresponding to PUSCH , Where the configuration parameter is used to indicate whether HARQ-ACK is spatially merged.
  • the determining unit 501 is specifically configured to: when using a dynamic HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that needs to transmit HARQ-ACK on the PUSCH is received, determine that HARQ- is not transmitted on the PUSCH ACK; and / or, if at least one downlink transmission or SPS PDSCH that requires HARQ-ACK transmission on the PUSCH is received, the HARQ-ACK is a dynamic HARQ-ACK codebook determined according to the DAI in the PDCCH corresponding to the downlink transmission.
  • the downlink transmission is at least one of PDSCH, semi-persistently scheduled SPS, and PDSCH release.
  • the physical device corresponding to the determining unit 501 and the transmitting unit 502 may be the aforementioned processor 402 or the transceiver 403.
  • the base station may be configured to execute the HARQ-ACK transmission method provided in the embodiment shown in FIG. 1-3. Therefore, regarding the functions that can be implemented by each functional module in the device, reference may be made to the corresponding description in the embodiment shown in FIGS. 1-3, and no further details are provided.
  • an embodiment of the present application provides a network device.
  • the network includes: a memory 601, a processor 602, and a transceiver 603.
  • the memory 601 and the transceiver 603 may be connected to the processor 602 through a bus interface (as an example in FIG. 6), or may be connected to the processor 602 through a special connection line.
  • the memory 601 may be used to store a program.
  • the transceiver 603 is configured to transmit and receive data under the control of the processor.
  • the processor 602 may be used to read a program in the memory 601 and execute the following process: if HARQ-ACK is transmitted on at least one PUSCH except for the first PUSCH among a plurality of PUSCHs corresponding to a PDCCH, determine the HARQ -When the number of feedback bits of the ACK is used, the DAI in the DCI format used by the PDCCH is ignored; the HARQ-ACK is received on the PUSCH according to the number of feedback bits of the HARQ-ACK.
  • multiple PUSCHs are repeated transmissions of the same PUSCH or transport block TB; or, multiple PUSCHs are multiple independent PUSCH transmissions scheduled by the same PDCCH.
  • the DCI format is DCI grid 0_1.
  • the processor 602 is specifically configured to: determine a HARQ-ACK feedback bit number according to a determination manner of HARQ-ACK transmission on a PUSCH where there is no corresponding PDCCH; or, determine a HARQ-ACK transmission on a PUCCH Method, determining the number of HARQ-ACK feedback bits, and replacing the HARQ-ACK configuration parameter corresponding to the PUCCH with the HARQ-ACK configuration parameter corresponding to the PUSCH, where the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • the HARQ-ACK feedback bit number is a downlink transmission or the SPS PDSCH HARQ-ACK feedback bit number; otherwise, the HARQ-ACK feedback bit number is based on the downlink transmission.
  • the number of feedback bits of the semi-static HARQ-ACK codebook determined by the candidate time domain resource set and the feedback timing set between downlink transmission and HARQ-ACK.
  • the processor 602 is specifically configured to: when using a semi-static HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that needs to transmit HARQ-ACK on the PUSCH is sent, determine that HARQ- is not received on the PUSCH ACK; and / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is sent, the number of HARQ-ACK feedback bits is based on the downlink transmission candidate time domain resource set and the feedback between downlink transmission and HARQ-ACK The number of feedback bits of the semi-static HARQ-ACK codebook determined by the timing set, or, according to the determination method of HARQ-ACK transmission on the PUCCH, the number of HARQ-ACK feedback bits is determined, and the configuration parameters of the HARQ-ACK corresponding to the PUCCH are determined. Replace the HARQ-ACK configuration parameter corresponding to the PUSCH, where the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • the processor 602 is specifically configured to: when using a dynamic HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that needs to transmit HARQ-ACK on the PUSCH is sent, determine that HARQ-ACK is not received on the PUSCH ; And / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is sent, the number of HARQ-ACK feedback bits is the feedback bits of the dynamic HARQ-ACK codebook determined according to the DAI in the PDCCH corresponding to the downlink transmission number.
  • the downlink transmission is at least one of PDSCH and SPS PDSCH release.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 602 and various circuits of the memory represented by the memory 601 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, so they are not described further herein.
  • the bus interface provides an interface.
  • the transceiver 603 may be multiple elements, including a transmitter and a transceiver, providing a unit for communicating with various other devices on a transmission medium.
  • the processor 602 is responsible for managing the bus architecture and general processing, and the memory 601 may store data used by the processor 602 when performing operations.
  • the memory 601 may include a read-only memory (English: Read Only Memory, referred to as ROM), a random access memory (English: Random Access Memory, referred to as RAM), and a disk storage.
  • the memory 601 is used to store data required by the processor 602 during operation, that is, to store instructions that can be executed by at least one processor 602.
  • At least one processor 602 executes the instructions shown in FIG. 1-3 by executing the instructions stored in the memory 601.
  • the HARQ-ACK transmission method provided in the embodiment.
  • the number of the memories 601 is one or more.
  • the memory 601 is shown together in FIG. 6, but it needs to be known that the memory 601 is not a required function module, so it is shown by a dotted line in FIG. 6.
  • the network device includes a determining unit 701 and a receiving unit 702.
  • the determining unit 701 may be configured to: if the HARQ-ACK is transmitted on at least one PUSCH other than the first PUSCH among multiple PUSCHs corresponding to one PDCCH, the PDCCH is ignored when determining the number of HARQ-ACK feedback bits. DAI in the DCI format used.
  • the receiving unit 702 is configured to receive HARQ-ACK according to the number of HARQ-ACK feedback bits on at least one PUSCH.
  • multiple PUSCHs are repeated transmissions of the same PUSCH or transport block TB; or, multiple PUSCHs are multiple independent PUSCH transmissions scheduled by the same PDCCH.
  • the DCI format is DCI grid 0_1.
  • the determining unit 701 is specifically configured to: determine a HARQ-ACK feedback bit number according to a determination manner of HARQ-ACK transmission on a PUSCH where there is no corresponding PDCCH; or, determine a HARQ-ACK transmission on a PUCCH Method, determining the number of HARQ-ACK feedback bits, and replacing the HARQ-ACK configuration parameter corresponding to the PUCCH with the HARQ-ACK configuration parameter corresponding to the PUSCH, where the configuration parameter is used to indicate whether the HARQ-ACK is spatially merged.
  • the HARQ-ACK feedback bit number is a downlink transmission or the SPS PDSCH HARQ-ACK feedback bit number; otherwise, the HARQ-ACK feedback bit number is based on the downlink transmission.
  • the number of feedback bits of the semi-static HARQ-ACK codebook determined by the candidate time domain resource set and the feedback timing set between downlink transmission and HARQ-ACK.
  • the determining unit 701 is specifically configured to: when using a semi-static HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that needs to transmit HARQ-ACK on the PUSCH is sent, determine that HARQ- is not received on the PUSCH ACK; and / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is sent, the number of HARQ-ACK feedback bits is based on the downlink transmission candidate time domain resource set and the feedback between downlink transmission and HARQ-ACK The number of feedback bits of the semi-static HARQ-ACK codebook determined by the timing set, or, according to the determination method of HARQ-ACK transmission on the PUCCH, the number of feedback bits of the HARQ-ACK is determined, and the configuration parameters of the HARQ-ACK corresponding to the PUCCH are determined. Replace the HARQ-ACK configuration parameter corresponding to the PUSCH, where the configuration parameter is used to indicate whether the HARQ-ACK is spatially
  • the determining unit 701 is specifically configured to: when using a dynamic HARQ-ACK codebook, if no downlink transmission or SPS PDSCH that needs to transmit HARQ-ACK on the PUSCH is sent, determine that HARQ-ACK is not received on the PUSCH ; And / or, if at least one downlink transmission requiring HARQ-ACK transmission on the PUSCH is sent, the number of HARQ-ACK feedback bits is the feedback bits of the dynamic HARQ-ACK codebook determined according to the DAI in the PDCCH corresponding to the downlink transmission number.
  • the downlink transmission is at least one of PDSCH, semi-persistently scheduled SPS, and PDSCH release.
  • the physical device corresponding to the determining unit 701 and the receiving unit 702 may be the foregoing processor 602 or transceiver 603.
  • the base station may be used to execute a method for setting a serving cell provided in the embodiment shown in FIG. 1. Therefore, regarding the functions that can be implemented by the functional modules in the device, reference may be made to the corresponding descriptions in the embodiments shown in FIG. 1 to FIG. 3, and details are not described repeatedly.
  • an embodiment of the present application further provides a computer storage medium, where the computer storage medium stores computer instructions, and when the computer instructions run on the computer, the HARQ-ACK provided in the embodiment shown in FIG. 1 is executed. Transmission method.
  • the HARQ-ACK transmission method, terminal device, and network device provided in the embodiments of the present application can be applied to a wireless communication system, such as a 5G system.
  • a wireless communication system such as a 5G system.
  • applicable communication systems include, but are not limited to, 5G systems or their evolved systems, other orthogonal frequency division multiplexing (OFDM) systems, and DFT-S-OFDM (DFT-Spread OFDM, DFT extended OFDM) ), Evolved Long Term Evolution (eLTE) systems, and new network equipment systems.
  • the connection between the foregoing devices may be a wireless connection or a wired connection.
  • the above communication system may include multiple terminal devices, and the network device may communicate (transmit signaling or transmit data) with multiple terminal devices.
  • the terminal device involved in this embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing device connected to a wireless modem.
  • a wireless user equipment can communicate with one or more core networks via a Radio Access Network (RAN).
  • the terminal equipment can be a mobile terminal, such as a mobile phone (or a "cellular" phone) and a mobile terminal with a mobile terminal.
  • Computers for example, may be portable, pocket-sized, handheld, computer-built or vehicle-mounted mobile devices that exchange languages and / or data with a wireless access network.
  • a terminal can also be called a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, and a remote station.
  • Terminal Remote Terminal
  • Access Terminal Access Terminal
  • User Terminal User Terminal
  • User Agent User Agent
  • User Equipment User Equipment
  • Wireless Device Wireless Device
  • the network device provided in this embodiment of the present application may be a base station or be used to convert received air frames and IP packets to each other and serve as a router between the wireless terminal device and the rest of the access network.
  • the rest may include Internet Protocol (IP) network equipment.
  • IP Internet Protocol
  • the network device may also be a device that coordinates attribute management of the air interface.
  • the network device may be a network device in a 5G system, such as a next-generation base station (Next Generation NodeB, gNB), or a Global System for Mobile Communications (GSM) or Code Division Multiple Access (Code Division) Multiple Access (CDMA) base stations (Base Transceiver Stations (BTS)) can also be Wideband Code Division Multiple Access (WCDMA) base stations (NodeB), or LTE evolved base stations ( (evolutional NodeB, eNB or e-NodeB), this embodiment of the present application is not limited.
  • a next-generation base station Next Generation NodeB, gNB
  • GSM Global System for Mobile Communications
  • CDMA Code Division Multiple Access
  • BTS Base Transceiver Stations
  • WCDMA Wideband Code Division Multiple Access
  • NodeB NodeB
  • LTE evolved base stations evolutional NodeB, eNB or e-NodeB
  • aspects of the HARQ-ACK transmission method, network device, and terminal device provided in the present application may also be implemented as a program product, which includes program code, and when the program product is in a computer, When running on a device, the program code is used to cause the computer device to execute the steps in the method for selecting configuration information according to various exemplary embodiments of the present application described above in this specification.
  • the computer device may execute The HARQ-ACK transmission method provided in the embodiment shown in FIG. 1.
  • the program product may employ any combination of one or more readable media.
  • the readable medium may be a readable signal medium or a readable storage medium.
  • the readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing.
  • the program product for the HARQ-ACK transmission method may adopt a portable compact disk read-only memory (CD-ROM) and include a program code, and may run on a computing device.
  • CD-ROM portable compact disk read-only memory
  • the program product of the present application is not limited thereto.
  • the readable storage medium may be any tangible medium containing or storing a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.
  • the readable signal medium may include a data signal that is borne in baseband or propagated as part of a carrier wave, in which readable program code is carried. Such a propagated data signal may take many forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the readable signal medium may also be any readable medium other than a readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device.
  • Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
  • the program code for performing the operations of this application may be written in any combination of one or more programming languages, which includes object-oriented programming languages—such as Java, C ++, etc., and also includes conventional procedural Programming language—such as "C" or a similar programming language.
  • the program code may be executed entirely on the user computing device, partly on the user device, as an independent software package, partly on the user computing device, partly on the remote computing device, or entirely on the remote computing device or server On.
  • the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it may be connected to an external computing device (e.g., using Internet services Provider to connect via the Internet).
  • LAN local area network
  • WAN wide area network
  • Internet services Provider to connect via the Internet
  • this application may be provided as a method, a system, or a computer program product. Therefore, this application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • the disclosed apparatus and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the modules or units is only a logical function division.
  • multiple units or components may be divided.
  • the combination can either be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit.
  • the integrated unit When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially a part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium. , Including a number of instructions to cause a computer device (which may be a personal computer, a server, or a network device) or a processor to perform all or part of the steps of the method described in the embodiments of the present application.
  • the foregoing storage medium includes: universal serial bus flash disk (Universal Serial Bus flash disk), mobile hard disk, read-only memory (Read-Only Memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or Various media such as optical discs that can store program codes.
  • universal serial bus flash disk Universal Serial Bus flash disk
  • mobile hard disk read-only memory
  • Read-Only Memory ROM
  • random access memory Random Access Memory, RAM
  • magnetic disk or Various media such as optical discs that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Abstract

本申请公开了一种HARQ-ACK的传输方法、终端设备及网络设备，以明确在配置了重复传输的PUSCH或者同一个PDCCH调度的多个PUSCH上如何传输HARQ-ACK。其中的HARQ-ACK的传输方法包括：若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定HARQ-ACK时忽略PDCCH所使用的DCI格式中的DAI；在所述至少一个PUSCH上传输所确定的HARQ-ACK。

Description

一种HARQ-ACK的传输方法、终端设备及网络设备
本申请要求在2018年9月21日提交中国专利局、申请号为201811106837.9、发明名称为“一种HARQ-ACK的传输方法、终端设备及网络设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别涉及一种HARQ-ACK的传输方法、终端设备及网络设备。
背景技术
在第五代移动通信技术(5 Generation，5G)网络的无线空中接口技术(简称NR)支持物理上行共享信道(Physical Uplink Shared Channel，PUSCH)的重复传输，也支持当物理上行控制信道(Physical Uplink Control Channel，PUCCH)与PUSCH的时域资源重叠时，将承载在PUCCH上的上行控制信息(Uplink Control Information，UCI)转移到PUSCH上传输，从而避免多种信道并行传输。但是，尚未明确在例如配置了重复传输的PUSCH或者同一个物理下行控制信道(Physical Downlink Control Channel，PDCCH)调度的多个PUSCH上如何传输UCI。
发明内容
本申请实施例提供一种HARQ-ACK的传输方法、终端设备及网络设备，用于提供一种新的机制，明确在配置了重复传输的PUSCH或者同一个PDCCH调度的多个PUSCH上如何传输HARQ-ACK。
第一方面，提供了一种HARQ-ACK的传输方法，该传输方法包括：若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK时忽略所述PDCCH所使用的下行控制信息(DCI)格式中的下行分配索引(DAI)；在所述至少一个PUSCH上传输所确定的HARQ-ACK。
本申请实施例中，如果承载HARQ-ACK的PUCCH与除了第一个PUSCH之外的多个PUSCH存在重叠，终端设备可以忽略PDCCH所使用的DCI格式中的DAI，确定在多个PUSCH上承载的HARQ-ACK。即提供了一种新的机制，明确在配置了重复传输的PUSCH或者同一个PDCCH调度的多个PUSCH上如何传输HARQ-ACK。
可选的，所述多个PUSCH为同一个PUSCH或传输块(TB)的重复传输；或者，所述多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
本申请实施例中，多个PUSCH可能有多种情况，例如可以是同一个PUSCH的重复传输，也可以是TB的重复传输，或者也可以是同一个PDCCH调度的多个独立的PUSCH的传输，不管是何种情况，都适用，适用范围较广。
可选的，所述DCI格式为DCI格式0_1。
可选的，在确定所述HARQ-ACK时忽略所述PDCCH所使用的DCI格式中的DAI，包括：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定所述HARQ-ACK；或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，在确定所述HARQ-ACK时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用半静态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或半持续性调度SPS物理下行共享信道PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若仅接收到一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅接收到一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时(即在PUSCH上仅存在对应一个SPS PDSCH的HARQ-ACK时)，则所述HARQ-ACK为所述一个下行传输或所述一个SPS PDSCH的HARQ-ACK；否则(即仅接收到一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI不为1，或仅接收到一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输不是由使用DCI格式1_0的PDCCH调度，或接收到超过一个下行传输，或接收到一个下行传输以及一个SPS PDSCH)，所述HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定半静态HARQ-ACK码本。
可选的，在确定所述HARQ-ACK时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用半静态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ_ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，在确定所述HARQ-ACK时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用动态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，所述HARQ-ACK为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本。
上述四种可选的方式列举了本申请实施例如何忽略PDCCH所使用的DCI格式中的DAI确定HARQ-ACK。
可选的，所述下行传输为PDSCH、半持续调度SPS PDSCH释放中的至少一种。
第二方面，提供了一种HARQ-ACK的传输方法，该传输方法包括：若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引(DAI)；在所述至少一个PUSCH上按照所述HARQ-ACK的反馈比特数接收HARQ-ACK。
可选的，所述多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，所述多 个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
可选的，所述DCI格式为DCI格0_1。
可选的，在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的DCI格式中的DAI，包括：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数；或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用半静态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；
和/或，若仅发送了一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅发送了一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则所述HARQ-ACK的反馈比特数为所述一个下行传输或所述一个SPS PDSCH的HARQ-ACK的反馈比特数；否则，所述HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数。
可选的，在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用半静态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用动态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK的反馈比特数为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本的反馈比特数。
可选的，所述下行传输为PDSCH、半持续调度(SPS PDSCH)释放中的至少一种。
第三方面，提供一种终端设备，该终端设备包括：存储器，用于存储指令；处理器，用于读取所述存储器中的指令，执行下列过程：若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引(DAI)；在所述至少一个PUSCH上传输所确定的HARQ-ACK；
收发机，用于在所述处理器的控制下收发数据。
可选的，所述多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，所述多 个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
可选的，所述DCI格式为DCI格式0_1。
可选的，所述处理器具体用于：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定所述HARQ-ACK；或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，所述处理器具体用于：当使用半静态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或半持续性调度SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若仅接收到一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅接收到一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则所述HARQ-ACK为所述一个下行传输或所述一个SPS PDSCH的HARQ-ACK；否则，所述HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定半静态HARQ-ACK码本。
可选的，所述处理器具体用于：当使用半静态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，所述处理器具体用于：当使用动态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，所述HARQ-ACK为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本。
可选的，所述下行传输为PDSCH、半持续调度SPS PDSCH释放中的至少一种。
第四方面，提供了一种网络设备，该网络设备包括：存储器，用于存储指令；处理器，用于读取所述存储器中的指令，执行下列过程：若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引DAI；在PUSCH上按照所述HARQ-ACK的反馈比特数接收HARQ-ACK；收发机，用于在所述处理器的控制下收发数据。
可选的，所述多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，所述多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
可选的，所述DCI格式为DCI格0_1。
可选的，所述处理器具体用于：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数；或者，根据HARQ-ACK在 PUCCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，所述处理器具体用于：当使用半静态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若仅发送了一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅发送了一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则所述HARQ-ACK的反馈比特数为所述一个下行传输或所述一个SPS PDSCH的HARQ-ACK的反馈比特数；否则，所述HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数。
可选的，所述处理器具体用于：当使用半静态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，所述处理器具体用于：当使用动态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK的反馈比特数为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本的反馈比特数。
可选的，所述下行传输为PDSCH、半持续调度SPS PDSCH释放中的至少一种。
第五方面，提供了一种终端设备，该终端设备包括：确定单元，用于若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引(DAI)；传输单元，用于在所述至少一个PUSCH上传输所确定的HARQ-ACK。
可选的，所述多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，所述多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
可选的，所述DCI格式为DCI格式0_1。
可选的，所述确定单元具体用于：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定所述HARQ-ACK；或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，所述确定单元具体用于：当使用半静态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或半持续性调度SPS物理下行共享信道PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若仅接收到一个需要在PUSCH 上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅接收到一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则所述HARQ-ACK为所述一个下行传输或所述一个SPS PDSCH的HARQ-ACK；否则，所述HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定半静态HARQ-ACK码本。
可选的，所述确定单元具体用于：当使用半静态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，所述确定单元具体用于：当使用动态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，所述HARQ-ACK为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本。
可选的，所述下行传输为PDSCH、半持续调度SPS PDSCH释放中的至少一种。
第六方面，提供了一种网络设备，该网络设备包括：确定单元，用于若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引DAI；接收单元，用于在所述至少一个PUSCH上按照所述HARQ-ACK的反馈比特数接收HARQ-ACK。
可选的，所述多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，所述多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
可选的，所述DCI格式为DCI格0_1。
可选的，所述确定单元具体用于：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数；或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，所述确定单元具体用于：当使用半静态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若仅发送了一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅发送了一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则所述HARQ-ACK的反馈比特数为所述一个下行传输或所述一个SPS PDSCH的HARQ-ACK的反馈比特数；否则，所述HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数。
可选的，所述确定单元具体用于：当使用半静态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
可选的，所述确定单元具体用于：当使用动态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK的反馈比特数为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本的反馈比特数。
可选的，所述下行传输为PDSCH、半持续调度SPS PDSCH释放中的至少一种。
第七方面，提供了一种计算机存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如第一方面或者第二方面任一项所述的方法。
本申请实施例中，如果承载HARQ-ACK的PUCCH与除了第一个PUSCH之外的多个PUSCH存在重叠，终端设备可以忽略PDCCH所使用的DCI格式中的DAI，确定在多个PUSCH上承载的HARQ-ACK。即提供了一种新的机制，明确在配置了重复传输的PUSCH或者同一个PDCCH调度的多个PUSCH上如何传输HARQ-ACK。
附图说明
图1是本申请实施例提供的HARQ-ACK的传输方法的流程示意图；
图2是本申请实施例提供的实施例一的一种调度和反馈示意图；
图3为本申请实施例提供的实施例二的一种调度和反馈示意图；
图4是本申请实施例提供的终端设备的一种结构示意图；
图5为本申请实施例提供的终端设备的一种结构示意图；
图6为本申请实施例提供的网络设备的一种结构示意图；
图7为本申请实施例提供的网络设备的一种结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚明白，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
下面介绍本申请实施例的背景技术。
在长期演进(Long Term Evolution，LTE)无线通信***中，当终端设备，例如用户设备(User Equipment，UE)在某个子帧中同时存在PUSCH和UCI传输时，承载UCI的PUCCH和PUSCH的时域资源可能存在重叠，如果UE支持PUCCH和PUSCH同时传输且高层信令配置可以进行PUCCH和PUSCH同时传输，则可以同时传输PUCCH和PUSCH，例如在PUCCH上传输UCI，在PUSCH上传输数据。如果UE不支持PUCCH和PUSCH 同时传输或高层信令配置不可以进行PUCCH和PUSCH同时传输，则承载在PUCCH上的UCI将转移到PUSCH上与PUSCH上原本承载的信息在PUSCH上进行复用传输。UCI至少包括混合自动重传请求确认(Hybrid Automatic Repeat reQuest ACKnowlegement，HARQ-ACK)、信道状态信息(Channel State Information，CSI)、调度请求(Scheduling Request，SR)。
特别的，对于不使用重复传输的PUSCH，当PUSCH具有对应的PDCCH(即由UL grant调度)且PDCCH使用下行控制信息(Downlink Control Information，DCI)格式0_1时，DCI格式0_1中包含1比特或2比特下行分配索引(Downlink Assignment Index，DAI)，通常称为UL DAI，用于指示HARQ-ACK在PUSCH上的传输情况。如果DCI格式0_1中没有DAI指示，当UE没有接收到任何需要在PUSCH所在的时域位置进行HARQ-ACK反馈的下行传输时，UE会确定PUSCH上不存在HARQ-ACK传输；当UE接收到需要在PUSCH所在的时域位置进行HARQ-ACK反馈的下行传输时，UE会确定PUSCH上存在按照配置的码本确定得到的HARQ-ACK传输。
当HARQ-ACK被配置使用半静态码本(Semi-Static Codebook)传输时，DCI格式0_1中包含1比特DAI，用于指示PUSCH上是否存在HARQ-ACK传输，即用于避免由于下行传输丢包导致的终端和基站对PUSCH上是否存在HARQ-ACK传输的理解不一致。当HARQ-ACK被配置使用动态码本(Dynamic Codebook)传输时，DCI格式0_1中包含2或4比特DAI，用于指示PUSCH上HARQ-ACK传输的总比特数，其中如果使用了子码本(针对基于传输块(Transport Block，TB)的下行传输和基于码块组(coding block Group，CBG)的下行传输分别的码本)，则每个子码本对应2比特DAI，共计为4比特DAI。对于动态码本(dynamic codebook)，该dynamic codebook对应的PDCCH检测机会(Monitoring occasion)集合中的PDCCH(用于调度PDSCH或指示下行伴持续性调度(Semi-Persistent Scheduling，SPS)资源释放的PDCCH)所使用的DCI(例如DCI格式1_0或1_1)中也包含DAI，通常称为DL DAI，单载波时，仅包含2比特DAI，多载波时包含4比特DAI，分为2比特C-DAI和2比特T-DAI，分别用于指示codebook的排序和大小。
目前，5G NR***支持PUSCH的重复传输，也支持PUCCH与PUSCH的时域资源重叠时，将承载在PUCCH上的UCI转移到PUSCH上传输，从而避免多种信道并行传输。
在5G NR中，当承载HARQ-ACK的PUCCH与一个配置了重复传输的PUSCH重叠且PUSCH由一个使用DCI格式0_1的PDCCH调度时，如何根据DCI格式0_1中的DAI确定HARQ-ACK在PUSCH上的codebook还没有明确的方法。
此外，对于由一个PDCCH同时调度多个PUSCH传输的情况，例如时隙n中的PDCCH同时调度时隙n+K2开始的N个时隙中进行N个PUSCH传输，或者给定N个K2值，调度在基于N个K2值确定的N个时隙中进行N个PUSCH传输，每个时隙中的PUSCH的调度信息可以相同或者不同，每个时隙中的PUSCH承载独立的TB，而不是一个TB的重复传输，即一个PDCCH中同时承载了用于调度多个时隙中的多个PUSCH传输的调度信息。此时，如何根据DCI格式0_1中的DAI确定HARQ-ACK在PUSCH上的码本(codebook)还没有明确的方法。即目前尚未明确在例如配置了重复传输的PUSCH或者同一个PDCCH调度的多个PUSCH上如何传输UCI。
鉴于此，本申请实施例提供了一种新的HARQ-ACK的传输方法，在该方法中，如果承载HARQ-ACK的PUCCH与除了第一个PUSCH之外的多个PUSCH存在重叠，终端设 备可以忽略PDCCH所使用的DCI格式中的DAI，确定在多个PUSCH上承载的HARQ-ACK。即提供了一种新的机制，明确在配置了重复传输的PUSCH或者同一个PDCCH调度的多个PUSCH上如何传输HARQ-ACK。
下面结合说明书附图介绍本申请实施例提供的技术方案。
请参见图1，本申请实施例提供一种HARQ-ACK的传输方法，该方法的流程描述如下。由于HARQ-ACK的传输方法中涉及到网络设备与终端设备之间的交互过程，因此在以下的流程描述中，网络设备与终端设备所执行的过程将一同进行描述。
对于由一个PDCCH调度的N个PUSCH传输，根据承载HARQ-ACK的PUCCH与多个PUSCH存在重叠的情况不同，确定PUSCH上承载的HARQ-ACK也有所不同。本申请实施例中，针对承载HARQ-ACK的PUCCH是否与第一个PUSCH重叠，确定PUSCH上承载的HARQ-ACK的方式包括以下步骤S101和步骤S102两种情况：
S101、若HARQ-ACK在对应一个PDCCH的多个PUSCH中的第一个PUSCH上传输，则根据PDCCH所使用的DCI格式中的DAI确定第一个PUSCH上承载的HARQ-ACK。
S102、若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定HARQ-ACK时忽略PDCCH所使用的DCI格式中的DAI。
本申请实施例中，终端设备确定了在PUSCH上承载的HARQ-ACK，则S103、在PUSCH上传输所确定的HARQ-ACK。例如，如果终端设备在S101的情况下确定了第一个PUSCH上承载的HARQ-ACK，则在第一个PUSCH上传输HARQ-ACK。如果终端设备在S102的情况下确定了除了第一个PUSCH的其他PUSCH上承载的HARQ-ACK，则在其他PUSCH上传输HARQ-ACK。
本申请实施例中，多个PUSCH可以为同一个PUSCH或传输块(TB)的重复传输，即当配置了一个PUSCH需要占用多个传输时间单元传输时，每个时间单元中的PUSCH承载相同的TB，其中传输时间单元可以为时隙或者微时隙当然也可以是其他定义的传输时间单元；多个PUSCH也可以为由同一个PDCCH调度的多个独立的PUSCH传输，即上行多个传输时间单元的联合调度，即一个PDCCH中同时承载对应多个PUSCH的调度信令，每个PUSCH承载独立的TB。DCI格式可以为包含DAI的DCI格式，例如DCI格式0_1。
本申请实施例中，在确定HARQ-ACK时忽略PDCCH所使用的DCI格式中的DAI，存在以下几种方式：
第一种方式：根据HARQ-ACK在不存在对应的PDCCH的PUSCH(即没有调度信令的PUSCH，即没有UL grant的PUSCH)上传输的确定方式，确定HARQ-ACK。
第二种方式：根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，配置参数用于指示HARQ-ACK是否空间合并。即假定HARQ-ACK在PUCCH上传输，按照对应的方式确定HARQ-ACK序列，其中需要将该方式中针对PUCCH的HARQ-ACK空间合并配置参数替换为针对PUSCH的HARQ-ACK空间合并配置参数。
第三种方式：当使用半静态HARQ-ACK码本时：
1)若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或
2)若仅接收到一个需要在PUSCH上传输HARQ-ACK的下行传输且下行传输由使用 DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或，若仅接收到一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则HARQ-ACK为一个下行传输或一个SPS PDSCH的HARQ-ACK(即仅传输1比特HARQ-ACK)；否则，HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定半静态HARQ-ACK码本。
第四种方式：当使用半静态HARQ-ACK码本时：
1)若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或
2)若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输，HARQ_ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，配置参数用于指示HARQ-ACK是否空间合并。
第五种方式：当使用动态HARQ-ACK码本时：
1)若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或
2)若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，HARQ-ACK为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本。
上述第一种方式到第五种方式的下行传输可以为PDSCH、SPS PDSCH释放(即指示下行SPS资源释放的PDCCH)中的至少一种。
为了便于理解，下面以具体实施例介绍本申请实施例提供的技术方案。
首先介绍HARQ-ACK在PUSCH上传输的一种场景：例如没有配置或者能力不支持PUCCH和PUSCH同时传输，且承载HARQ-ACK的PUCCH与PUSCH的时域资源存在重叠，且满足UCI复用(即UCI可以从PUCCH上转移到PUSCH，从而不传输PUCCH)的时间条件，例如PUCCH和PUSCH中的最早的信道(如果PUCCH和PUSCH的起始符号相同，则选择传输长度最长的一个信道，如果起始符号和传输长度都一致，则选择任何一个)的第一个符号的开始位置不早于特定的时间点，其中时间点1为基于需要在PUCCH上进行HARQ-ACK反馈的最后一个PDSCH/SPS PDSCH release的最后一个符号之后的预定时间长度得到的位置，其中时间点2为基于需要在PUCCH上进行HARQ-ACK反馈的PDSCH/SPS PDSCH release对应的PDCCH的最后一个符号之后的预定时间长度得到的位置。
实施例一、请参见图2，图2为一种调度与反馈示意图，应用于如上的场景。图2以频分双工(Frequency Division Duplex，FDD)***为例。每个时隙都存在上行资源和下行资源，假设HARQ-ACK反馈时序集合K1＝{2,3,4,5,6}，K1以时隙为单位，用于根据一个PDSCH的传输所在时隙确定承载该PDSCH的HARQ-ACK的PUCCH传输所在的时隙。假设每个下行时隙中最多存在一个PDSCH传输，配置使用semi-static HARQ-ACK codebook，则根据K1集合和PDSCH的候选时域资源集合(PDSCH的候选时域资源集合可以表现为预先配置的一个表格，包含多行，每行对应一个PDSCH所在的时隙，以及该时隙中的时域位置，如起始符号位置以及符号长度的配置信息，其中PDSCH所在的时隙由调度时序K0确定，K0表示调度该PDSCH的PDCCH与该PDSCH之间的时隙间隔)， 可以确定如图2所示每个上行时隙对应的semi-static codebook包含5个可能的PDSCH传输位置，假设每个PDSCH都对应1比特HARQ-ACK，则每个时隙对应的semi-static codebook的大小为5比特。假设基站在时隙n-1中发送了一个使用DCI格式0_1的PDCCH(UL grant)调度终端设备在时隙n到n+3中进行重复的PUSCH传输，即每个时隙中的PUSCH承载相同的TB且使用相同的时频域资源和MCS等参数。假设时隙n对应的候选PDSCH机会集合(即时隙n-6到时隙n-2)中不存在PDSCH传输需要在时隙n进行HARQ-ACK反馈，则网络设备将调度PUSCH的DCI格式0_1中的1比特DAI设置为0，表示在PUSCH上不存在HARQ-ACK。假设终端设备不支持或未配置PUCCH和PUSCH同时传输，按照如下方式确定HARQ-ACK：
在时隙n中，由于终端设备没有接收到任何下行传输或SPS PDSCH需要在时隙n中进行HARQ-ACK反馈，且根据调度PUSCH的DCI格式0_1中的1比特DAI为0，确定不需要在PUSCH上传输HARQ-ACK。需要说明的是，没有接收到任何下行传输或SPS PDSCH是在半静态HARQ-ACK码本对应的下行传输机会集合中(例如图2中时隙n中的半静态HARQ-ACK码本对应的下行传输机会集合为时隙n-6到时隙n-2中每个时隙中存在一个下行传输机会，共计5个下行传输机会，该下行传输机会集合是根据K1集合以及PDSCH的候选时域资源集合确定的，下同，不再赘述)没有接收到任何需要在PUSCH上传输HARQ-ACK(即根据下行传输对应K1值确定是否在PUSCH所在的时隙中进行HARQ-ACK反馈，当确定是时，为需要在PSUCH上传输HARQ-ACK的下行传输，下同，不再赘述)的下行传输。
在时隙n+1中，根据网络设备调度，时隙n-5中的PDSCH需要在时隙n+1中进行HARQ-ACK反馈，且假设承载该HARQ-ACK的PUCCH资源与时隙n+1中的PUSCH资源存在重叠，由于终端设备不支持或未配置PUCCH和PUSCH同时传输，因此在满足UCI复用时间条件时，需要将PUCCH上的HARQ-ACK转移到PUSCH上传输，并不再传输PUCCH。此时，不考虑调度该PUSCH重复传输的DCI格式0_1中的1比特DAI值是否为0，进一步存在如下几种方式：
方式1：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定HARQ-ACK。也就是按照不存在对应的PDCCH调度该PUSCH的情况处理。由于仅收到一个下行传输，如果该下行传输由DCI格式1_0调度且DCI格式1_0中的DAI＝1，则在PUSCH上仅针对该一个下行传输进行HARQ-ACK反馈，即按照上述假设仅传输1比特HARQ-ACK(semi-static codebook的fallback)。否则，即如果该下行传输由DCI格式1_0调度且DCI格式1_0中的DAI不为1，或者如果该下行传输不由DCI格式1_0调度，或者收到了超过一个下行传输和/或SPS PDSCH，则按照时隙n+1对应的semi-static codebook的大小，在PUSCH传输HARQ-ACK，即传输5比特HARQ-ACK。其中，对于没有接收到PDSCH的位置上产生NACK(作为占位)。
方式2：根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK。具体地，按照HARQ-ACK在PUCCH上的传输方式，并使用PUSCH对应的HARQ-ACK是否空间合并的配置参数替换PUCCH对应的HARQ-ACK是否空间合并的配置参数。在本实施例一中不涉及空间合并，因此，直接按照PUCCH上的传输方式确定HARQ-ACK，具体包括：
由于仅收到一个下行传输，如果该下行传输由DCI格式1_0调度，且DCI格式1_0中的DAI＝1，则在PUSCH上仅针对该一个下行传输进行HARQ-ACK反馈，即按照上述 假设仅传输1比特HARQ-ACK(semi-static codebook的fallback)。如果该下行传输由DCI格式1_0调度且DCI格式1_0中的DAI不为1，或者如果该下行传输不由DCI格式1_0调度，或者收到了超过一个下行传输和/或SPS PDSCH，则按照时隙n+1对应的semi-static codebook的大小，在PUSCH传输HARQ-ACK，即传输5比特HARQ-ACK。其中，对于没有接收到PDSCH的位置上产生NACK(作为占位)。
方式3：根据是否仅收到一个下行传输以及具体的DCI格式和DAI值确定HARQ-ACK。由于仅收到一个下行传输，则根据该下行传输是否由DCI格式1_0调度且DCI格式1_0中的DAI是否为1来判断，是否在PUSCH上仅传输该一个下行传输的HARQ-ACK，具体步骤同方式1或方式2，这里不再赘述。
方式4：总是按照时隙n+1对应的semi-static codebook，在PUSCH传输HARQ-ACK，即传输5比特HARQ-ACK，其中，对于没有接收到PDSCH的位置上产生NACK。
需要说明的是，接收到一个或超过一个下行传输是在半静态HARQ-ACK码本对应的下行传输机会集合中接收到需要在PUSCH上传输HARQ-ACK的下行传输。
在时隙n+2中，根据网络设备调度，时隙n-4和n-3中的PDSCH需要在时隙n+2中进行HARQ-ACK反馈，且假设承载该HARQ-ACK的PUCCH资源与时隙n+2中的PUSCH资源存在重叠，由于终端设备不支持或未配置PUCCH和PUSCH同时传输，因此，在满足UCI复用传输的时间条件时，需要将PUCCH上的HARQ-ACK转移到PUSCH上传输，并不再传输PUCCH。此时，不考虑调度该PUSCH重复传输的DCI格式0_1中的1比特DAI值是否为0，按照如下方式确定HARQ-ACK。
方式1：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定HARQ-ACK。也就是按照不存在对应的PDCCH调度该PUSCH的情况处理。由于收到超过一个下行传输，确定按照时隙n+2对应的semi-static codebook，在PUSCH传输HARQ-ACK，即传输5比特HARQ-ACK。其中，对于没有接收到PDSCH的位置上产生NACK。
方式2：按照HARQ-ACK在PUCCH上的传输方式，并使用PUSCH对应的HARQ-ACK是否空间合并的配置参数替换PUCCH对应的HARQ-ACK是否空间合并的配置参数。在本实施例一中不涉及空间合并，因此，直接按照PUCCH上的传输方式确定HARQ-ACK，具体包括：
由于收到超过一个下行传输，则按照时隙n+1对应的semi-static codebook，在PUSCH传输HARQ-ACK，即传输5比特HARQ-ACK。其中，对于没有接收到PDSCH的位置上产生NACK。
方式3：根据是否仅收到一个下行传输以及具体的DCI格式和DAI值确定HARQ-ACK。由于收到超过一个下行传输，则按照时隙n+1对应的semi-static codebook，在PUSCH传输HARQ-ACK，即传输5比特HARQ-ACK。其中，对于没有接收到PDSCH的位置上产生NACK。
方式4：总是按照时隙n+1对应的semi-static codebook，在PUSCH传输HARQ-ACK，即传输5比特HARQ-ACK。其中，对于没有接收到PDSCH的位置上产生NACK。
需要说明的是，接收到一个或超过一个下行传输是在半静态HARQ-ACK码本对应的下行传输机会集合中接收需要在PUSCH上传输HARQ-ACK的下行传输。
对于在时隙n+3中的方式同在时隙n+1的方式，这里不再赘述。
对于网络设备而言，网络设备在每个时隙中按照上述相同的方式确定PUSCH上是否存在HARQ-ACK以及存在多少比特HARQ-ACK，进而在PUSCH上进行HARQ-ACK接收。
在该实施例一中可知，如果每个PUSCH重复传输的时隙中都考虑调度PUSCH的DCI格式0_1(即UL grant)中的DAI＝0，则与实际存在下行传输需要在该时隙进行HARQ-ACK反馈相矛盾，如果参考UL grant中的DAI＝0，则意味着后续重复传输的每个PUSCH中都不能存在HARQ-ACK传输，这将严重影响下行调度和吞吐量，而本申请实施例中不考虑该DAI值，直接按照实际下行传输的需求进行HARQ-ACK反馈，可以避免上述问题。
此外，如果UL grant中的1比特DAI指示1，而在后续时隙n+1、n+2和n+3中存在没有收到任何对应的下行传输的时隙，则在该时隙中的PUSCH上，如果总是按照UL grant中的UL DAI确定HARQ-ACK，将造成冗余的HARQ-ACK传输，即终端设备需要按照UL DAI指示的信息产生NACK作为占位传输，但实际上却不对应任何下行传输，则降低了上行传输效率和***效率。而本申请实施例中不考虑该DAI值，直接按照实际下行传输的需求进行HARQ-ACK反馈，可以避免上述问题。
实施例二、请参见图3，图3为一种调度与反馈示意图，应用于如上述的场景。图3同样以频分双工(Frequency Division Duplex，FDD)***为例。假设仅配置了一个载波，HARQ-ACK反馈时序集合K1＝{4,5,6,7}，K1以时隙为单位，用于根据一个PDSCH的传输所在时隙确定承载该PDSCH的HARQ-ACK的PUCCH传输所在的时隙。假设每个下行时隙中最多存在一个PDSCH传输，配置使用dynamic HARQ-ACK Codebook，则根据K1集合、PDSCH的候选时域资源集合(即预先配置的资源表格中的信息，包含多种时域位置以及K0信息)，本实施例中出于简单假设K0＝0，则可以确定如图3所示每个上行时隙对应的dynamic codebook所对应的PDCCH monitoring occasion集合，该集合中包含4个可能的检测PDCCH的位置，在每个检测PDCCH的位置都可能收到一个PDCCH，进一步可以根据该PDCCH中携带的PDSCH时域资源指示域确定候选的PDSCH时域资源集合中的一个，该一个时域资源包含了PDSCH的时域位置以及PDSCH传输所在的时隙(根据K0确定时隙)。当然对于PDSCH候选时域资源集合中的每个候选的PDSCH时域资源，可以具有相同或者不同的K0值。假设每个PDSCH都对应1比特HARQ-ACK，则可以根据在每个上行时隙对应的PDCCH monitoring occasion集合中接收到的调度PDSCH传输的PDCCH或指示下行SPS资源释放的PDCCH、以及上述PDCCH中携带的DAI值，确定一个上行时隙对应的dynamic codebook的大小。具体的，对于单载波情况，上述PDCCH中仅包含2比特DAI，DAI以时域调度顺序累计递增，则根据接收到的最后一个PDCCH中的DAI可以知道一个上行时隙对应PDSCH和指示SPS资源释放的PDCCH个数，从而可以知道该上行时隙中的HARQ-ACK Codebook大小。假设网络设备在时隙n-1中发送了一个使用DCI格式0_1的PDCCH(UL grant)调度终端设备在时隙n到n+3中进行重复的PUSCH传输，即每个时隙中的PUSCH承载相同的TB且使用相同的时频域资源和MCS等参数。假设上行时隙n对应的PDCCH monitoring occasion集合(即时隙n-7到时隙n-4)中存在3个PDCCH分别调度了3个PDSCH传输需要在上行时隙n中进行HARQ-ACK反馈，则网络设备将在时隙n-1中发送的调度PUSCH的DCI格式0_1中的2比特DAI设置为3(根据codebook不同UL grant中包含不同比特数的UL DAI)，表示在PUSCH上存在对应3个PDSCH的HARQ-ACK反馈。假设终端设备不支持或未配置PUCCH和PUSCH同时传输， 按照如下方式确定HARQ-ACK：
在时隙n中，终端设备接收到3个下行传输需要在时隙n中进行HARQ-ACK反馈，最后一个下行传输中的DL DAI(即调度下行传输的PDCCH中的DAI)指示为3。假设承载该HARQ-ACK的PUCCH资源与时隙n+1中的PUSCH资源存在重叠，由于终端设备不支持或未配置PUCCH和PUSCH同时传输，因此，需要将PUCCH上的HARQ-ACK转移到PUSCH上传输，并不再传输PUCCH。且，终端设备根据调度PUSCH的DCI格式0_1中的2比特UL DAI调度上行传输的PDCCH中的DAI)为3，与实际接收到的下行传输个数吻合，则根据UL DAI确定在PUSCH上传输3比特HARQ-ACK(假设每个PDSCH都对应1比特HARQ-ACK，当然在其他实施例中，每个PDSCH还可以根据PDSCH的传输配置对应多比特HARQ-ACK)。特别的，如果终端设备丢失了时隙n-5中的PDCCH，则根据最后一个接收到的下行传输(时隙n-6中的)中的DL DAI确定只有2个下行传输，而此时UL DAI(指示为3，则可判断存在一个下行传输丢失，则根据UL DAI需要按照3个下行传输来在PUSCH上进行HARQ-ACK反馈，即依旧产生3比特HARQ-ACK在PUSCH上传输。其中，最后1比特产生NACK作为判断丢包的下行传输的HARQ-ACK。
在时隙n+1中，根据网络设备调度，时隙n-4和n-3中的PDSCH需要在时隙n+1中进行HARQ-ACK反馈，根据最后一个接收到的PDCCH中的DL DAI＝2，确定只有2个下行传输需要在时隙n+1中进行HARQ-ACK反馈。假设承载该HARQ-ACK的PUCCH资源与时隙n+1中的PUSCH资源存在重叠，由于终端设备不支持或未配置PUCCH和PUSCH同时传输，因此，终端设备需要将PUCCH上的HARQ-ACK转移到PUSCH上传输，并不再传输PUCCH。此时，不考虑调度该PUSCH重复传输的DCI格式0_1中的2比特DAI值，确定HARQ-ACK进一步存在如下几种方式：
方式1：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定HARQ-ACK。也就是按照不存在对应的PDCCH调度该PUSCH的情况处理，即直接按照时隙n+1对应的PDCCH monitoring occasion集合中接收到的最后一个PDCCH中的DL DAI指示的下行传输个数，确定需要在时隙n+1中的PUSCH上传输的HARQ-ACK比特数，即此时产生2比特HARQ-ACK。
方式2：按照HARQ-ACK在PUCCH上的传输方式，并使用PUSCH对应的HARQ-ACK是否空间合并的配置参数替换PUCCH对应的HARQ-ACK是否空间合并的配置参数。在本实施例二中不涉及空间合并，因此，终端设备可以直接按照时隙n+1对应的PDCCH monitoring occasion集合中接收到的最后一个PDCCH中的DL DAI指示的下行传输个数，确定需要在时隙n+1中的PUSCH上传输的HARQ-ACK比特数，即此时产生2比特HARQ-ACK。
方式3：总是按照使用下行DCI格式的PDCCH中的DAI确定codebook；即直接按照时隙n+1对应的PDCCH monitoring occasion集合中接收到的最后一个PDCCH中的DL DAI指示的下行传输个数，确定需要在时隙n+1中的PUSCH上传输的HARQ-ACK比特数，即此时产生2比特HARQ-ACK。
在时隙n+2中，根据网络设备调度，时隙n-2中的PDSCH需要在时隙n+2中进行HARQ-ACK反馈。假设承载该HARQ-ACK的PUCCH资源与时隙n+2中的PUSCH资源存在重叠，由于终端设备不支持或未配置PUCCH和PUSCH同时传输，因此，终端设备需要将PUCCH上的HARQ-ACK转移到PUSCH上传输，并不再传输PUCCH。此时，不 考虑调度该PUSCH重复传输的DCI格式0_1中的2比特DAI值，确定HARQ-ACK进一步存在如下几种方式：
方式1：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定HARQ-ACK。也就是按照不存在对应的PDCCH调度该PUSCH的情况处理，即按照时隙n+2对应的PDCCH monitoring occasion集合中接收到的最后一个PDCCH中的DL DAI指示的下行传输个数，确定需要在时隙n+1中的PUSCH上传输的HARQ-ACK比特数，即此时产生1比特HARQ-ACK。
方式2：按照HARQ-ACK在PUCCH上的传输方式，并使用PUSCH对应的HARQ-ACK是否空间合并的配置参数替换PUCCH对应的HARQ-ACK是否空间合并的配置参数。在本实施例二中不涉及空间合并，因此，终端设备可以直接按照时隙n+2对应的PDCCH monitoring occasion集合中接收到的最后一个PDCCH中的DL DAI指示的下行传输个数，确定需要在时隙n+1中的PUSCH上传输的HARQ-ACK比特数，即此时产生1比特HARQ-ACK。
方式3：总是按照使用下行DCI格式的PDCCH中的DAI确定codebook；即直接按照PUCCH上的传输方式确定HARQ-ACK，也就是按照时隙n+2对应的PDCCH monitoring occasion集合中接收到的最后一个PDCCH中的DL DAI指示的下行传输个数，确定需要在时隙n+1中的PUSCH上传输的HARQ-ACK比特数，即此时产生1比特HARQ-ACK。
情况四、在时隙n+3中，没有收到对应需要进行HARQ-ACK反馈的下行传输，则不存在PUCCH与PUSCH重叠传输，不考虑调度该PUSCH重复传输的DCI格式0_1中的2比特DAI值，则该PUSCH上无HARQ-ACK。此时不论是按照上述方式1或方式2或方式3都是确定PUSCH上无HARQ-ACK。
对于网络设备而言，网络设备在每个时隙中按照上述相同的方式确定PUSCH上是否存在HARQ-ACK以及存在多少比特HARQ-ACK，进而在PUSCH上进行HARQ-ACK接收。
需要说明的是，上述实施例二中，接收到一个或多个下行传输是在动态HARQ-ACK码本对应的PDCCH检测机会集合中(PDCCH检测机会集合是根据K1集合、PDSCH候选时域资源集合中的K0集合确定的，例如以时隙n为例，根据K1集合可以确定PDSCH传输机会为n-K1即时隙n-7到n-4，假设K0只有一个值为0，则基于PDSCH传输机会进一步确定调度这些PDSCH传输机会传输的PDCCH为n-K1-K0，即依旧是时隙n-7到n-4，如图3所示，而如果K0值可以有其他值，则确定的PDCCH检测机会集合会更大些，例如K0＝{0,1}，则基于时隙n-7到n-4的PDSCH传输机会进一步确定的PDCCH检测机会为时隙n-8到时隙n-4)接收到了调度这些下行传输的PDCCH，且这些下行传输根据其对应K1，确定需要在PUSCH所在的时隙中进行HARQ-ACK反馈，即这些下行传输需要在PUSCH上传输HARQ-ACK。
在该实施例二中可知，在后续的重复传输的时隙n+1、n+2和n+3中的PUSCH上，如果都考虑调度PUSCH的DCI格式0_1中的2比特DAI＝3，则总是需要传输3比特HARQ-ACK，但实际上与实际存在下行传输需要在该时隙进行HARQ-ACK反馈不一致。如果参考调度PUSCH的DCI格式0_1中DAI＝3，则意味着后续重复传输的每个PUSCH中都需要产生比实际下行需求更多的冗余HARQ-ACK比特进行传输，将降低上行传输效率和***效率，也增加了上行传输开销。而本申请实施例中不考虑该DAI值，直接按照实 际下行传输的需求进行HARQ-ACK反馈，可以避免上述问题。
此外，在该实施例二中，如果UL grant中的2比特DAI指示一个比较小的值，例如1，则在时隙n+1和n+2中，UL grant指示的下行传输个数少于实际接收到的下行传输个数，如果按照UL grant中的2比特UL DAI确定HARQ-ACK，则将导致部分下行传输不能具有HARQ-ACK反馈，将影响下行吞吐量和***效率。而本申请实施例中不考虑该DAI值，直接按照实际下行传输的需求进行HARQ-ACK反馈，可以避免上述问题。
需要说明的是，上述实施例一和实施例二中，仅以K1为下行传输所对应的PDCCH中的指示域动态指示的值为例。除此之外，K1还可以是预先定义或高层信令预先配置的，此时每个下行传输只有一个固定的反馈时序，但这个时序定义的改变不影响上述方案的执行。上述实施例一和实施例二中，下行传输仅以PDSCH为例，将其中的一个或所有PDSCH替换指示下行SPS资源释放的PDCCH同样适用，此时下行对应的PDCCH即指示下行SPS资源释放的PDCCH本身。上述实施例一和实施例二仅以FDD为例，如果为TDD同样适用，唯一不同的就是对于semi-static codebook确定的PDSCH候选集合不一定是连续的时隙，对于dynamic codebook其PDCCH monitoring occasion集合也可能不是在连续的时隙中，可能由于某些时隙不存在下行传输资源或者下行传输资源不足以支持候选的PDSCH时域资源大小，而将这些时隙排除。上述实施例一和实施例二仅以单载波为例，多载波时同样适用，对于实施例一，在使用semi-static codebook时，针对每个载波确定codebook，然后级联在一起得到最终的codebook；对于实施例二，在使用dynamic codebook时，基于每个载波上的候选PDSCH时域资源(包括K0)以及K1集合确定所有载波上的PDCCH monitoring occasion集合，调度下行传输的PDCCH中包含4比特DAI，2比特用作C-DAI，指示先频域后时域的下行传输的累计调度计数，2比特用于T-DAI，指示到当前时刻累计调度的下行传输总数，根据C-DAI和T-DAI可以得到最终多载波对应的dynamic codebook。如果使用了子码本(针对基于TB的下行传输和基于CBG的下行传输分别的码本)，则调度PUSCH的PDCCH中包含4比特UL DAI，2比特对应基于TB的子码本，2比特对应基于CBG的子码本，分别指示对应的子码本中的下行传输总数，此时，上述产生PUSCH上传输的HARQ-ACK的方式同样适用。上述实施例一和实施例二中，当一个UL grant同时调度4个PUSCH在时隙n到n+3中传输，且这4个PUSCH分别传输独立的TB(即并不是同一个TB的重复传输)时，例如，这4个PUSCH对应相同的调度信息，但承载的TB不同，又例如该一个UL grant中使用的DCI中包含多个独立的指示域，分别对应4个时隙中的每个时隙，则4个时隙中的调度信息可以不同，上述方法同样适用。
需要说明的，本申请实施例提供的HARQ-ACK的传输方法同样适用于当同一个PDCCH联合调度N个独立的PUSCH传输的情况。例如，如果承载HARQ-ACK的PUCCH与其中的第一个PUSCH存在重叠，则根据PDCCH所使用的DCI格式中的DAI确定该PUSCH上承载的HARQ-ACK；如果承载HARQ-ACK的PUCCH与其中的除了第一个PUSCH之外的PUSCH存在重叠，则忽略PDCCH所使用的DCI格式中的DAI，按照在PUCCH上传输HARQ-ACK的方式确定该PUSCH上承载的HARQ-ACK。
综上，本申请实施例中，如果承载HARQ-ACK的PUCCH与除了第一个PUSCH之外的多个PUSCH存在重叠，终端设备可以忽略PDCCH所使用的DCI格式中的DAI，确定在多个PUSCH上承载的HARQ-ACK。即提供了一种新的机制，明确在配置了重复传输的PUSCH或者同一个PDCCH调度的多个PUSCH上如何传输HARQ-ACK。
下面结合说明书附图介绍本申请实施例提供的设备。
请参见图4，基于同一发明构思，本申请实施例提供一种终端设备，该终端设备包括：存储器401、处理器402和收发机403。其中，存储器401和收发机403可以通过总线接口与处理器402相连接(图4以此为例)，或者也可以通过专门的连接线与处理器402连接。
其中，存储器401可以用于存储程序。收发机403，用于在所述处理器的控制下收发数据。处理器402可以用于读取存储器401中的程序，执行下列过程：若HARQ-ACK在对应PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定HARQ-ACK时忽略PDCCH所使用的DCI格式中的DAI；在至少一个PUSCH上传输所确定的HARQ-ACK。
可选的，多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
可选的，DCI格式为DCI格式0_1。
可选的，处理器402具体用于：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定HARQ-ACK；或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，配置参数用于指示HARQ-ACK是否空间合并。
可选的，处理器402具体用于：当使用半静态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或半持续性调度SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若仅接收到一个需要在PUSCH上传输HARQ-ACK的下行传输且下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅接收到一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则HARQ-ACK为一个下行传输或一个SPS PDSCH的HARQ-ACK；否则，HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定半静态HARQ-ACK码本。
可选的，处理器402具体用于：当使用半静态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输，HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，配置参数用于指示HARQ-ACK是否空间合并。
可选的，处理器402具体用于：当使用动态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，HARQ-ACK为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本。
可选的，下行传输为PDSCH、半持续调度SPS PDSCH释放中的至少一种。
其中，在图4中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器402代表的一个或多个处理器和存储器401代表的存储器的各种电路链接在一起。总线架构还 可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机403可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器402负责管理总线架构和通常的处理，存储器401可以存储处理器402在执行操作时所使用的数据。
可选的，存储器401可以包括只读存储器(英文：Read Only Memory，简称：ROM)、随机存取存储器(英文：Random Access Memory，简称：RAM)和磁盘存储器。存储器401用于存储处理器402运行时所需的数据，即存储有可被至少一个处理器402执行的指令，至少一个处理器402通过执行存储器401存储的指令，执行图1-3所示的实施例提供的HARQ-ACK的传输方法。其中，存储器401的数量为一个或多个。其中，存储器401在图4中一并示出，但需要知道的是存储器401不是必选的功能模块，因此在图4中以虚线示出。
请参见图5，基于同一发明构思，本申请实施例提供一种终端设备，该终端设备可以包括确定单元501和传输单元502。其中，确定单元501可以用于若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定HARQ-ACK时忽略PDCCH所使用的DCI格式中的DAI。传输单元502用于在至少一个PUSCH上传输所确定的HARQ-ACK。
可选的，多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
可选的，DCI格式为DCI格式0_1。
可选的，确定单元501具体用于：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定HARQ-ACK；或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，配置参数用于指示HARQ-ACK是否空间合并。
可选的，确定单元501具体用于：当使用半静态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或半持续性调度SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若仅接收到一个需要在PUSCH上传输HARQ-ACK的下行传输且下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅接收到一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则HARQ-ACK为一个下行传输或一个SPS PDSCH的HARQ-ACK；否则，HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定半静态HARQ-ACK码本。
可选的，确定单元501具体用于：当使用半静态HARQ-ACK码本时，若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输，HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，配置参数用于指示HARQ-ACK是否空间合并。
可选的，确定单元501具体用于：当使用动态HARQ-ACK码本时，若没有接收到任 何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，HARQ-ACK为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本。
可选的，下行传输为PDSCH、半持续调度SPS PDSCH释放中的至少一种。
其中，确定单元501和传输单元502所对应的实体设备均可以是前述的处理器402或收发机403。该基站可以用于执行图1-3所示的实施例提供的HARQ-ACK的传输方法。因此关于该设备中各功能模块所能够实现的功能，可参考图1-3所示的实施例中的相应描述，不多赘述。
请参见图6，基于同一发明构思，本申请实施例提供一种网络设备，该网络包括：存储器601、处理器602和收发机603。其中，存储器601和收发机603可以通过总线接口与处理器602相连接(图6以此为例)，或者也可以通过专门的连接线与处理器602连接。
其中，存储器601可以用于存储程序。收发机603，用于在所述处理器的控制下收发数据。处理器602可以用于读取存储器601中的程序，执行下列过程：若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定HARQ-ACK的反馈比特数时忽略PDCCH所使用的DCI格式中的DAI；在PUSCH上按照HARQ-ACK的反馈比特数接收HARQ-ACK。
可选的，多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
可选的，DCI格式为DCI格0_1。
可选的，处理器602具体用于：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定HARQ-ACK的反馈比特数；或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，配置参数用于指示HARQ-ACK是否空间合并。
可选的，处理器602具体用于：当使用半静态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若仅发送了一个需要在PUSCH上传输HARQ-ACK的下行传输且下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅发送了一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则HARQ-ACK的反馈比特数为一个下行传输或一个SPS PDSCH的HARQ-ACK的反馈比特数；否则，HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数。
可选的，处理器602具体用于：当使用半静态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，配置参数 用于指示HARQ-ACK是否空间合并。
可选的，处理器602具体用于：当使用动态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，HARQ-ACK的反馈比特数为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本的反馈比特数。
可选的，下行传输为PDSCH、SPS PDSCH释放中的至少一种。
其中，在图6中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器602代表的一个或多个处理器和存储器601代表的存储器的各种电路链接在一起。总线架构还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机603可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器602负责管理总线架构和通常的处理，存储器601可以存储处理器602在执行操作时所使用的数据。
可选的，存储器601可以包括只读存储器(英文：Read Only Memory，简称：ROM)、随机存取存储器(英文：Random Access Memory，简称：RAM)和磁盘存储器。存储器601用于存储处理器602运行时所需的数据，即存储有可被至少一个处理器602执行的指令，至少一个处理器602通过执行存储器601存储的指令，执行图1-3所示的实施例提供的HARQ-ACK的传输方法。其中，存储器601的数量为一个或多个。其中，存储器601在图6中一并示出，但需要知道的是存储器601不是必选的功能模块，因此在图6中以虚线示出。
请参见图7，基于同一发明构思，本申请实施例提供一种网络设备，该网络设备包括确定单元701和接收单元702。其中，确定单元701可以用于若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定HARQ-ACK的反馈比特数时忽略PDCCH所使用的DCI格式中的DAI。接收单元702用于在至少一个PUSCH上按照HARQ-ACK的反馈比特数接收HARQ-ACK。
可选的，多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
可选的，DCI格式为DCI格0_1。
可选的，确定单元701具体用于：根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定HARQ-ACK的反馈比特数；或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，配置参数用于指示HARQ-ACK是否空间合并。
可选的，确定单元701具体用于：当使用半静态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若仅发送了一个需要在PUSCH上传输HARQ-ACK的下行传输且下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅发送了一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则HARQ-ACK的反馈比特数为一个下行传输或一个SPS PDSCH的HARQ-ACK的反馈比特数；否则，HARQ-ACK 的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数。
可选的，确定单元701具体用于：当使用半静态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，配置参数用于指示HARQ-ACK是否空间合并。
可选的，确定单元701具体用于：当使用动态HARQ-ACK码本时，若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，HARQ-ACK的反馈比特数为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本的反馈比特数。
可选的，下行传输为PDSCH、半持续调度SPS PDSCH释放中的至少一种。
其中，确定单元701和接收单元702所对应的实体设备均可以是前述的处理器602或收发机603。该基站可以用于执行图1所示的实施例提供的服务小区的设置方法。因此关于该设备中各功能模块所能够实现的功能，可参考图1-图3所示的实施例中的相应描述，不多赘述。
基于同一发明构思，本申请实施例还提供一种计算机存储介质，其中，计算机存储介质存储有计算机指令，当计算机指令在计算机上运行时，执行图1所示的实施例提供的HARQ-ACK的传输方法。
本申请实施例提供的HARQ-ACK的传输方法、终端设备及网络设备可以应用于无线通信***，例如5G***中。但适用的通信***包括但不限于5G***或其演进***，其它的基于正交频分复用(orthogonal frequency division multiplexing，OFDM)***，基于DFT-S-OFDM(DFT-Spread OFDM，DFT扩展OFDM)，演进型长期演进(Evolved Long Term Evolution，eLTE)的***、以及新的网络设备***等。在实际应用中上述各个设备之间的连接可以为无线连接，也可以为有线连接。
需要说明的是，上述通信***可以包括多个终端设备，网络设备可以与多个终端设备通信(传输信令或传输数据)。本申请实施例涉及的终端设备，可以是指向用户提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线用户设备可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，终端设备可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication Service，PCS)电话、无绳电话、会话发起协议(SIP)话机、无线本地环路(Wireless Local Loop，WLL)站、个人数字助理(Personal Digital Assistant，PDA)等设备。终端也可以称为***、订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、接入点(Access Point)、 远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户代理(User Agent)、用户设备(User Device)，无线设备(wireless device)。
本申请实施例提供的网络设备可以为基站，或是用于将收到的空中帧与IP分组进行相互转换，作为无线终端设备与接入网的其余部分之间的路由器，其中接入网的其余部分可包括网际协议(IP)网络设备。该网络设备还可以是协调对空中接口的属性管理的设备。例如，网络设备可以是5G***中的网络设备，如下一代基站(Next generation Node B，gNB)，还可以是全球移动通信***(Global System for Mobile Communication，GSM)或码分多址(Code Division Multiple Access，CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)中的基站(NodeB)，还可以是LTE中的演进型基站(evolutional Node B，eNB或e-NodeB)，本申请实施例并不限定。
需要理解的是，在本申请实施例的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。在本申请实施例的描述中“多个”，是指两个或两个以上。
在一些可能的实施方式中，本申请提供的HARQ-ACK的传输方法、网络设备和终端设备的各个方面还可以实现为一种程序产品的形式，其包括程序代码，当所述程序产品在计算机设备上运行时，所述程序代码用于使所述计算机设备执行本说明书上述描述的根据本申请各种示例性实施方式的配置信息的选择方法中的步骤，例如，所述计算机设备可以执行如图1中所示的实施例提供的HARQ-ACK的传输方法。
所述程序产品可以采用一个或多个可读介质的任意组合。可读介质可以是可读信号介质或者可读存储介质。可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的***、装置或器件，或者任意以上的组合。可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑盘只读存储器(CD-ROM)、光存储器件、磁存储器件，或者上述的任意合适的组合。
本申请的实施方式的用于HARQ-ACK的传输方法的程序产品可以采用便携式紧凑盘只读存储器(CD-ROM)并包括程序代码，并可以在计算设备上运行。然而，本申请的程序产品不限于此，在本文件中，可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行***、装置或者器件使用或者与其结合使用。
可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了可读程序代码。这种传播的数据信号可以采用多种形式，包括——但不限于——电磁信号、光信号或上述的任意合适的组合。可读信号介质还可以是可读存储介质以外的任何可读介质，该可读介质可以发送、传播或者传输用于由指令执行***、装置或者器件使用或者与其结合使用的程序。
可读介质上包含的程序代码可以用任何适当的介质传输，包括——但不限于——无线、有线、光缆、RF等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言的任意组合来编写用于执行本申请操作的程序代码，所述程序设计语言包括面向对象的程序设计语言—诸如Java、C++等，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算 设备上执行、部分地在用户设备上执行、作为一个独立的软件包执行、部分在用户计算设备上部分在远程计算设备上执行、或者完全在远程计算设备或服务器上执行。在涉及远程计算设备的情形中，远程计算设备可以通过任意种类的网络——包括局域网(LAN)或广域网(WAN)—连接到用户计算设备，或者，可以连接到外部计算设备(例如利用因特网服务提供商来通过因特网连接)。
应当注意，尽管在上文详细描述中提及了装置的若干单元或子单元，但是这种划分仅仅是示例性的并非强制性的。实际上，根据本申请的实施方式，上文描述的两个或更多单元的特征和功能可以在一个单元中具体化。反之，上文描述的一个单元的特征和功能可以进一步划分为由多个单元来具体化。
此外，尽管在附图中以特定顺序描述了本申请方法的操作，但是，这并非要求或者暗示必须按照该特定顺序来执行这些操作，或是必须执行全部所示的操作才能实现期望的结果。附加地或备选地，可以省略某些步骤，将多个步骤合并为一个步骤执行，和/或将一个步骤分解为多个步骤执行。
本领域内的技术人员应明白，本申请的实施例可提供为方法、***、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。上述描述的***，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个 实施例所述方法的全部或部分步骤。而前述的存储介质包括：通用串行总线闪存盘(Universal Serial Busflash disk)、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (35)

  1. 一种混合自动重传请求确认HARQ-ACK的传输方法，其特征在于，包括：
    若HARQ-ACK在对应一个物理下行控制信道PDCCH的多个物理上行共享信道PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引DAI；
    在所述至少一个PUSCH上传输所确定的HARQ-ACK。
  2. 如权利要求1所述的传输方法，其特征在于，所述多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，所述多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
  3. 如权利要求1所述的传输方法，其特征在于，所述DCI格式为DCI格式0_1。
  4. 如权利要求1所述的传输方法，其特征在于，在确定所述HARQ-ACK时忽略所述PDCCH所使用的DCI格式中的DAI，包括：
    根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定所述HARQ-ACK；或者，
    根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
  5. 如权利要求1所述的传输方法，其特征在于，在确定所述HARQ-ACK时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用半静态HARQ-ACK码本时：
    若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或半持续性调度SPS物理下行共享信道PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，
    若仅接收到一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅接收到一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则所述HARQ-ACK为所述一个下行传输或所述一个SPS PDSCH的HARQ-ACK；否则，所述HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定半静态HARQ-ACK码本。
  6. 如权利要求1所述的传输方法，其特征在于，在确定所述HARQ-ACK时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用半静态HARQ-ACK码本时：
    若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，
    若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
  7. 如权利要求1所述的传输方法，其特征在于，在确定所述HARQ-ACK时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用动态HARQ-ACK码本时：
    若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，
    若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，所述HARQ-ACK为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本。
  8. 如权利要求5～7中任一项所述的传输方法，其特征在于，所述下行传输为PDSCH、SPS PDSCH释放中的至少一种。
  9. 一种混合自动重传请求确认HARQ-ACK的传输方法，其特征在于，包括：
    若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引DAI；
    在所述至少一个PUSCH上按照所述HARQ-ACK的反馈比特数接收HARQ-ACK。
  10. 如权利要求9所述的传输方法，其特征在于，所述多个PUSCH为同一个PUSCH或TB的重复传输；或者，所述多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
  11. 如权利要求9所述的传输方法，其特征在于，所述DCI格式为DCI格0_1。
  12. 如权利要求9所述的传输方法，其特征在于，在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的DCI格式中的DAI，包括：
    根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数；或者，
    根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
  13. 如权利要求9所述的传输方法，其特征在于，在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用半静态HARQ-ACK码本时：
    若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或半持续性调度SPS物理下行共享信道PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，
    若仅发送了一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅发送了一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则所述HARQ-ACK的反馈比特数为所述一个下行传输或所述一个SPS PDSCH的HARQ-ACK的反馈比特数；否则，所述HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数。
  14. 如权利要求9所述的传输方法，其特征在于，在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用半静态HARQ-ACK码本时：
    若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，
    若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈 定时集合确定的半静态HARQ-ACK码本的反馈比特数，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
  15. 如权利要求9所述的传输方法，其特征在于，在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的DCI格式中的DAI，包括：当使用动态HARQ-ACK码本时：
    若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，
    若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK的反馈比特数为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本的反馈比特数。
  16. 如权利要求13～15中任一项所述的传输方法，其特征在于，所述下行传输为PDSCH、SPS PDSCH释放中的至少一种。
  17. 一种终端设备，其特征在于，包括：
    存储器，用于存储指令；
    处理器，用于读取所述存储器中的指令，执行下列过程：
    若HARQ-ACK在对应一个物理下行控制信道PDCCH的多个物理上行共享信道PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引DAI；
    在所述至少一个PUSCH上传输所确定的HARQ-ACK；
    收发机，用于在所述处理器的控制下收发数据。
  18. 如权利要求17所述的终端设备，其特征在于，所述多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，所述多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
  19. 如权利要求17所述的终端设备，其特征在于，所述DCI格式为DCI格式0_1。
  20. 如权利要求17所述的终端设备，其特征在于，所述处理器具体用于：
    根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定所述HARQ-ACK；或者，
    根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
  21. 如权利要求17所述的终端设备，其特征在于，所述处理器具体用于：当使用半静态HARQ-ACK码本时：
    若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或半持续性调度SPS物理下行共享信道PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，
    若仅接收到一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅接收到一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则所述HARQ-ACK为所述一个下行传输或所述一个SPS PDSCH的HARQ-ACK；否则，所述HARQ-ACK为根据下行传输候选时 域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定半静态HARQ-ACK码本。
  22. 如权利要求17所述的终端设备，其特征在于，所述处理器具体用于：当使用半静态HARQ-ACK码本时：
    若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，
    若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
  23. 如权利要求17所述的终端设备，其特征在于，所述处理器具体用于：当使用动态HARQ-ACK码本时：
    若没有接收到任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不传输HARQ-ACK；和/或，
    若接收到至少一个需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，所述HARQ-ACK为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本。
  24. 如权利要求21～23中任一项所述的终端设备，其特征在于，所述下行传输为PDSCH、SPS PDSCH释放中的至少一种。
  25. 一种网络设备，其特征在于，包括：
    存储器，用于存储指令；
    处理器，用于读取所述存储器中的指令，执行下列过程：
    若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引DAI；
    在PUSCH上按照所述HARQ-ACK的反馈比特数接收HARQ-ACK；
    收发机，用于在所述处理器的控制下收发数据。
  26. 如权利要求25所述的网络设备，其特征在于，所述多个PUSCH为同一个PUSCH或传输块TB的重复传输；或者，所述多个PUSCH为由同一个PDCCH调度的多个独立的PUSCH传输。
  27. 如权利要求25所述的网络设备，其特征在于，所述DCI格式为DCI格0_1。
  28. 如权利要求25所述的网络设备，其特征在于，所述处理器具体用于：
    根据HARQ-ACK在不存在对应的PDCCH的PUSCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数；或者，
    根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
  29. 如权利要求25所述的网络设备，其特征在于，所述处理器具体用于：当使用半静态HARQ-ACK码本时：
    若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或半持续性调度SPS 物理下行共享信道PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，
    若仅发送了一个需要在PUSCH上传输HARQ-ACK的下行传输且所述下行传输由使用DCI格式1_0的PDCCH调度且DCI格式1_0中的DAI＝1时，或仅发送了一个需要在PUSCH上传输HARQ-ACK的SPS PDSCH时，则所述HARQ-ACK的反馈比特数为所述一个下行传输或所述一个SPS PDSCH的HARQ-ACK的反馈比特数；否则，所述HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数。
  30. 如权利要求25所述的网络设备，其特征在于，所述处理器具体用于：当使用半静态HARQ-ACK码本时：
    若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，
    若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK的反馈比特数为根据下行传输候选时域资源集合以及下行传输与HARQ-ACK之间的反馈定时集合确定的半静态HARQ-ACK码本的反馈比特数，或者，根据HARQ-ACK在PUCCH上传输的确定方式，确定所述HARQ-ACK的反馈比特数，并将PUCCH对应的HARQ-ACK的配置参数替换为PUSCH对应的HARQ-ACK的配置参数，其中，所述配置参数用于指示所述HARQ-ACK是否空间合并。
  31. 如权利要求25所述的网络设备，其特征在于，所述处理器具体用于：当使用动态HARQ-ACK码本时：
    若没有发送任何需要在PUSCH上传输HARQ-ACK的下行传输或SPS PDSCH，则确定在PUSCH上不接收HARQ-ACK；和/或，
    若发送了至少一个需要在PUSCH上传输HARQ-ACK的下行传输，所述HARQ-ACK的反馈比特数为根据下行传输对应的PDCCH中的DAI确定的动态HARQ-ACK码本的反馈比特数。
  32. 如权利要求29～31中任一项所述的网络设备，其特征在于，所述下行传输为PDSCH、SPS PDSCH释放中的至少一种。
  33. 一种终端设备，其特征在于，包括：
    确定单元，用于若HARQ-ACK在对应一个物理下行控制信道PDCCH的多个物理上行共享信道PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引DAI；
    传输单元，用于在所述至少一个PUSCH上传输所确定的HARQ-ACK。
  34. 一种网络设备，其特征在于，包括：
    确定单元，用于若HARQ-ACK在对应一个PDCCH的多个PUSCH中的除第一个PUSCH之外的至少一个PUSCH上传输，则在确定所述HARQ-ACK的反馈比特数时忽略所述PDCCH所使用的下行控制信息DCI格式中的下行分配索引DAI；
    接收单元，用于在所述至少一个PUSCH上按照所述HARQ-ACK的反馈比特数接收HARQ-ACK。
  35. 一种计算机存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现如权利要求1-8或者9-16任一项所述的传输方法。
PCT/CN2019/106511 2018-09-21 2019-09-18 一种harq-ack的传输方法、终端设备及网络设备 WO2020057566A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2021516465A JP7303291B2 (ja) 2018-09-21 2019-09-18 Ｈａｒｑ－ａｃｋの伝送方法、端末装置およびネットワーク装置
KR1020217011877A KR102665094B1 (ko) 2018-09-21 2019-09-18 Harq-ack의 전송을 위한 방법, 단말 장치 및 네트워크 장치
US17/278,332 US11290217B2 (en) 2018-09-21 2019-09-18 HARQ-ACK transmission method, terminal device and network device
EP19863862.9A EP3855650A4 (en) 2018-09-21 2019-09-18 HARQ-ACK TRANSMISSION PROCESS, TERMINAL DEVICE AND NETWORK DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811106837.9A CN110943805B (zh) 2018-09-21 2018-09-21 一种harq-ack的传输方法、终端设备及网络设备
CN201811106837.9 2018-09-21

Publications (1)

Publication Number Publication Date
WO2020057566A1 true WO2020057566A1 (zh) 2020-03-26

Family

ID=69888370

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/106511 WO2020057566A1 (zh) 2018-09-21 2019-09-18 一种harq-ack的传输方法、终端设备及网络设备

Country Status (6)

Country Link
US (1) US11290217B2 (zh)
EP (1) EP3855650A4 (zh)
JP (1) JP7303291B2 (zh)
KR (1) KR102665094B1 (zh)
CN (1) CN110943805B (zh)
WO (1) WO2020057566A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111884770A (zh) * 2020-04-10 2020-11-03 中兴通讯股份有限公司 Harq-ack码本产生方法
WO2021109465A1 (en) * 2020-05-15 2021-06-10 Zte Corporation Methods and devices for constructing harq-ack codebook for semi-persistent scheduling
CN114258115A (zh) * 2020-09-24 2022-03-29 ***通信有限公司研究院 一种确定方法、发送方法、终端设备及网络设备
WO2022075728A1 (en) * 2020-10-08 2022-04-14 Samsung Electronics Co., Ltd. Method and apparatus for transmission of harq-ack in wireless communication system
CN114726478A (zh) * 2021-01-05 2022-07-08 大唐移动通信设备有限公司 传输上行控制信息的方法、装置以及存储介质
EP4152852A4 (en) * 2020-05-15 2023-07-26 Datang Mobile Communications Equipment Co., Ltd. METHOD OF DETERMINING THE TRANSMISSION LOCATION OF FEEDBACK INFORMATION AND DEVICE

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11824811B2 (en) * 2018-02-13 2023-11-21 Lenovo (Beijing) Limited Method and apparatus for fallback operation for semi-static HARQ-ACK codebook determination
US11831571B2 (en) * 2018-10-31 2023-11-28 Qualcomm Incorporated Transport block transmission using different spatial parameters
CN111770572B (zh) * 2019-03-30 2023-08-04 华为技术有限公司 确定反馈信息的方法和通信装置
EP3965332A4 (en) * 2019-04-30 2022-04-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. FEEDBACK METHOD FOR SEMI-STATIC TRANSMISSION, NETWORK DEVICE, AND TERMINAL DEVICE
US11483099B2 (en) * 2019-08-16 2022-10-25 Samsung Electronics Co., Ltd. Apparatus and method for transmission of uplink control information in network cooperative communication
US11736933B2 (en) * 2019-08-26 2023-08-22 Qualcomm Incorporated Capability signaling for physical uplink shared channel repetition
US20240048289A1 (en) * 2019-10-03 2024-02-08 Ntt Docomo, Inc. Terminal and radio communication method
CN116155468A (zh) * 2020-04-20 2023-05-23 大唐移动通信设备有限公司 一种码本反馈处理方法、设备、装置及介质
CN113595697B (zh) * 2020-04-30 2022-09-27 维沃移动通信有限公司 Dai计数方法、dai计数控制方法、终端及网络设备
CN113677011A (zh) * 2020-05-15 2021-11-19 华为技术有限公司 一种通信方法及相关设备
WO2022000498A1 (en) * 2020-07-03 2022-01-06 Nec Corporation Methods, devices, and computer readable medium for communication
US11956777B2 (en) * 2020-08-07 2024-04-09 Qualcomm Incorporated Management of overlapping semi-persistent scheduling (SPS) configured physical downlink shared channel (PDSCH) transmission occasions
CN114696968B (zh) * 2020-12-31 2024-07-02 维沃移动通信有限公司 控制信道的配置方法、装置、通信设备
CN115333681B (zh) * 2021-05-11 2024-05-07 大唐移动通信设备有限公司 信息传输方法、装置及存储介质
EP4381644A1 (en) * 2021-08-06 2024-06-12 Apple Inc. Scheduling for multiple pdsch/pusch operations

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103516496A (zh) * 2012-06-27 2014-01-15 北京三星通信技术研究有限公司 一种发送harq-ack反馈信息的方法
CN104427550A (zh) * 2013-08-23 2015-03-18 北京三星通信技术研究有限公司 业务流量自适应***中上行数据传输的方法及设备
WO2017078454A1 (ko) * 2015-11-06 2017-05-11 주식회사 아이티엘 반송파 집성을 지원하는 무선통신 시스템에서 harq 동작을 수행하는 장치 및 방법
CN108271262A (zh) * 2017-01-03 2018-07-10 北京三星通信技术研究有限公司 分配上行控制信道的方法及设备

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5199223B2 (ja) * 2008-12-30 2013-05-15 創新音▲速▼股▲ふん▼有限公司 Ａｃｋ／ｎａｃｋバンドリングを改善する方法及び通信装置
CN103370970B (zh) * 2010-11-03 2016-11-09 三星电子株式会社 具有载波聚合的下行链路的tdd***中的harq-ack信息生成及harq-ack信号功率控制
KR101497850B1 (ko) 2010-12-02 2015-03-02 엘지전자 주식회사 Tdd 기반 무선 통신 시스템에서 ack/nack 전송 방법 및 장치
KR101727793B1 (ko) * 2010-12-15 2017-04-17 엘지전자 주식회사 Tdd 기반 무선 통신 시스템에서 ａｃｋ/ｎａｃｋ 전송 방법 및 장치
JP5933753B2 (ja) * 2012-01-15 2016-06-15 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおいて制御情報の送信方法及び装置
CN103220795A (zh) * 2012-01-21 2013-07-24 中兴通讯股份有限公司 下行控制信息的发送方法和基站
WO2015147591A1 (ko) * 2014-03-27 2015-10-01 엘지전자 주식회사 무선 통신 시스템에서 하향링크 신호 송수신 방법 및 이를 위한 장치
US9686064B2 (en) * 2015-01-21 2017-06-20 Intel IP Corporation Devices and methods for HARQ-ACK feedback scheme on PUSCH in wireless communication systems
US10965407B2 (en) * 2017-02-02 2021-03-30 Sharp Kabushiki Kaisha User equipments, base stations and communication methods
EP3468081A4 (en) 2017-02-05 2020-02-19 LG Electronics Inc. -1- METHOD FOR TRANSMITTING UPLINK CONTROL INFORMATION IN A WIRELESS COMMUNICATION SYSTEM AND APPARATUS THEREFOR
US20210067275A1 (en) * 2017-12-27 2021-03-04 Ntt Docomo, Inc. Base station and radio communication method
CN111587548B (zh) * 2018-01-12 2023-05-26 瑞典爱立信有限公司 具有混合自动重传请求确认的物理上行链路共享信道
US10834711B2 (en) * 2018-04-17 2020-11-10 Qualcomm Incorporated Selectively multiplexing physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH) communications
US11838907B2 (en) * 2020-02-04 2023-12-05 Qualcomm Incorporated Simultaneous feedback information and uplink shared channel transmissions

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103516496A (zh) * 2012-06-27 2014-01-15 北京三星通信技术研究有限公司 一种发送harq-ack反馈信息的方法
CN104427550A (zh) * 2013-08-23 2015-03-18 北京三星通信技术研究有限公司 业务流量自适应***中上行数据传输的方法及设备
WO2017078454A1 (ko) * 2015-11-06 2017-05-11 주식회사 아이티엘 반송파 집성을 지원하는 무선통신 시스템에서 harq 동작을 수행하는 장치 및 방법
CN108271262A (zh) * 2017-01-03 2018-07-10 北京三星通信技术研究有限公司 分配上行控制信道的方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3855650A4

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111884770A (zh) * 2020-04-10 2020-11-03 中兴通讯股份有限公司 Harq-ack码本产生方法
EP4135238A4 (en) * 2020-04-10 2024-07-10 Zte Corp METHOD FOR GENERATING A HARQ-ACK CODEBOOK, METHOD FOR TRANSMITTING A HARQ-ACK CODEBOOK AND PDSCH RECEIVING METHOD
WO2021109465A1 (en) * 2020-05-15 2021-06-10 Zte Corporation Methods and devices for constructing harq-ack codebook for semi-persistent scheduling
EP4152852A4 (en) * 2020-05-15 2023-07-26 Datang Mobile Communications Equipment Co., Ltd. METHOD OF DETERMINING THE TRANSMISSION LOCATION OF FEEDBACK INFORMATION AND DEVICE
CN114258115A (zh) * 2020-09-24 2022-03-29 ***通信有限公司研究院 一种确定方法、发送方法、终端设备及网络设备
WO2022075728A1 (en) * 2020-10-08 2022-04-14 Samsung Electronics Co., Ltd. Method and apparatus for transmission of harq-ack in wireless communication system
CN114726478A (zh) * 2021-01-05 2022-07-08 大唐移动通信设备有限公司 传输上行控制信息的方法、装置以及存储介质
CN114726478B (zh) * 2021-01-05 2023-09-01 大唐移动通信设备有限公司 传输上行控制信息的方法、装置以及存储介质

Also Published As

Publication number Publication date
EP3855650A1 (en) 2021-07-28
EP3855650A4 (en) 2021-12-08
CN110943805B (zh) 2021-06-04
KR102665094B1 (ko) 2024-05-09
US11290217B2 (en) 2022-03-29
CN110943805A (zh) 2020-03-31
US20210314094A1 (en) 2021-10-07
KR20210054000A (ko) 2021-05-12
JP2022500959A (ja) 2022-01-04
JP7303291B2 (ja) 2023-07-04

Similar Documents

Publication Publication Date Title
WO2020057566A1 (zh) 一种harq-ack的传输方法、终端设备及网络设备
JP7119100B2 (ja) 通信方法およびデバイス
WO2019096060A1 (zh) 上行控制信息传输方法和设备
CN111435878B (zh) 一种信息传输方法、终端及网络设备
WO2020057565A1 (zh) 一种harq-ack的传输方法、终端设备及网络设备
RU2604808C2 (ru) Способ и устройство
WO2020089875A1 (en) Method and apparatus for transmitting harq-ack information
US20140211767A1 (en) Scheduling Communications
JP2022500961A (ja) ハイブリッド自動再送要求確認コードブックの伝送方法及び機器
WO2021023011A1 (zh) Harq-ack反馈方法、终端及网络侧设备
JP2022520589A (ja) 送信動作および受信動作を実行するユーザ機器およびシステム
TWI757651B (zh) 行動通訊中harq過程以及pucch資源選擇的方法和裝置
WO2010133043A1 (zh) 多子帧调度方法、***及终端、基站
WO2021238545A1 (zh) 信息传输方法及装置
WO2019029287A1 (zh) Pucch传输方法、用户设备和装置
EP3723314A1 (en) Transmission method and device
WO2021227624A1 (zh) 一种确定反馈信息传输位置的方法及设备
US20240121785A1 (en) Dynamic resource scheduling in wireless communications
WO2020228588A1 (zh) Pucch资源确定方法和通信设备
US20200322959A1 (en) Method for transmitting uplink control information, and related product
US20230155737A1 (en) Information communication method and apparatus
EP4319396A1 (en) Method transmitting uci on pusch, terminal, and device
WO2022206218A1 (zh) 一种通信方法、装置及***

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19863862

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021516465

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217011877

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019863862

Country of ref document: EP

Effective date: 20210421