WO2022061661A1 - 无线通信的方法、终端设备和网络设备 - Google Patents

无线通信的方法、终端设备和网络设备 Download PDF

Info

Publication number
WO2022061661A1
WO2022061661A1 PCT/CN2020/117491 CN2020117491W WO2022061661A1 WO 2022061661 A1 WO2022061661 A1 WO 2022061661A1 CN 2020117491 W CN2020117491 W CN 2020117491W WO 2022061661 A1 WO2022061661 A1 WO 2022061661A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
pusch
physical downlink
terminal device
information
Prior art date
Application number
PCT/CN2020/117491
Other languages
English (en)
French (fr)
Inventor
吴作敏
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to EP20954513.6A priority Critical patent/EP4216628A4/en
Priority to PCT/CN2020/117491 priority patent/WO2022061661A1/zh
Priority to CN202311368176.8A priority patent/CN117499002A/zh
Priority to CN202080104595.9A priority patent/CN116235444A/zh
Publication of WO2022061661A1 publication Critical patent/WO2022061661A1/zh
Priority to US18/171,232 priority patent/US20230199799A1/en

Links

Images

Classifications

    • 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
    • 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
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • 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/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/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/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • 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/1825—Adaptation of specific ARQ protocol parameters according to transmission conditions
    • 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/1864—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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • 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
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a wireless communication method, a terminal device, and a network device.
  • Non-Terrestrial Networks for the downlink data transmission of a terminal device, the network device can instruct the terminal device to enable one or some downlink hybrid automatic repeat requests (Hybrid Automatic Repeat).
  • HARQ-ACK Hybrid Automatic Repeat request Acknowledgement
  • the terminal device when the terminal device is configured with Type-1 or Type-2 or eType-2 HARQ-ACK codebook feedback, when the terminal device should be on the first Physical Uplink Control Channel (Physical Uplink Control Channel, When the HARQ-ACK information corresponding to downlink data transmission is transmitted on the PUCCH) resource, if the first PUCCH resource and the first physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) resource of the terminal device at least partially overlap in the time domain, How to determine whether to multiplex the HARQ-ACK information corresponding to the downlink data transmission on the first PUSCH resource or the size of the included HARQ-ACK information is an urgent problem to be solved.
  • Physical Uplink Control Channel Physical Uplink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • Embodiments of the present application provide a wireless communication method, terminal device, and network device, which are helpful for scheduling PUSCH transmission according to the network device, and when the PUSCH is associated with a physical downlink channel, according to the reception of the physical downlink channel associated with the PUSCH.
  • multiplexing of PUSCH resources is beneficial to improve system performance.
  • a method for wireless communication including: a terminal device determines to transmit a first physical uplink shared channel PUSCH, wherein the first PUSCH is associated with a first physical downlink channel; The reception of the physical downlink channel, to determine whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH, where the first HARQ-ACK information corresponds to the first physical downlink channel reception.
  • a wireless communication method including: a network device sending first downlink control information DCI to a terminal device, where the first DCI is used to schedule first physical uplink shared channel PUSCH transmission, the first The DCI includes first downlink allocation indication DAI information, where the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH.
  • a terminal device for executing the method in the first aspect or any possible implementation manner of the first aspect.
  • the terminal device includes a unit for executing the method in the first aspect or any possible implementation manner of the first aspect.
  • a network device for executing the method in the second aspect or any possible implementation manner of the second aspect.
  • the network device includes a unit for executing the method in the second aspect or any possible implementation manner of the second aspect.
  • a terminal device in a fifth aspect, includes: a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory to execute the method in the above-mentioned first aspect or each implementation manner thereof.
  • a network device in a sixth aspect, includes: a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or each of its implementations.
  • a chip is provided for implementing any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • the chip includes: a processor for invoking and running a computer program from a memory, so that a device on which the chip is installed executes any one of the above-mentioned first to second aspects or each of its implementations method.
  • a computer-readable storage medium for storing a computer program, the computer program causing a computer to execute the method in any one of the above-mentioned first aspect to the second aspect or each of its implementations.
  • a computer program product comprising computer program instructions, the computer program instructions causing a computer to execute the method in any one of the above-mentioned first to second aspects or the respective implementations thereof.
  • a computer program which, when run on a computer, causes the computer to perform the method in any one of the above-mentioned first to second aspects or the respective implementations thereof.
  • the network device can schedule the terminal device to transmit the first PUSCH.
  • the terminal device can determine the first physical downlink channel corresponding to the first physical downlink channel according to the reception of the first physical downlink channel.
  • a multiplexing manner of HARQ-ACK information on the first PUSCH is beneficial to improve system performance.
  • FIGS. 1A-1C are schematic diagrams of an application scenario provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a relationship between the number of HARQ processes and RTT.
  • FIG. 3 is a schematic diagram of a wireless communication method provided by an embodiment of the present application.
  • FIG. 4 is a schematic block diagram of a terminal device provided by an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of a network device provided by an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a communication device provided by another embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a chip provided by an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • CDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • NTN Non-Terrestrial Networks
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • WiFi fifth-generation communication
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • V2X Vehicle to everything
  • the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.
  • Carrier Aggregation, CA Carrier Aggregation, CA
  • DC Dual Connectivity
  • SA standalone
  • the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.
  • the embodiments of the present application may be applied to a non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, and may also be applied to a terrestrial communication network (Terrestrial Networks, TN) system.
  • NTN non-terrestrial communication network
  • TN terrestrial communication network
  • the embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • user equipment User Equipment, UE
  • access terminal subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device may be a station (STATION, ST) in the WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a Wireless Local Loop (WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
  • PLMN Public Land Mobile Network
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • a mobile phone Mobile Phone
  • a tablet computer Pad
  • a computer with a wireless transceiver function a virtual reality (Virtual Reality, VR) terminal device
  • augmented reality (Augmented Reality, AR) terminal Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • the terminal equipment involved in the embodiments of this application may also be referred to as terminal, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, and remote station , remote terminal equipment, mobile equipment, UE terminal equipment, wireless communication equipment, UE proxy or UE device, etc.
  • Terminal devices can also be stationary or mobile.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network device may be a satellite or a balloon station.
  • the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a High Elliptical Orbit (HEO) ) satellite etc.
  • the network device may also be a base station set in a location such as land or water.
  • a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device (
  • the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell).
  • Pico cell Femto cell (Femto cell), etc.
  • These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • FIG. 1A is a schematic structural diagram of a communication system provided by an embodiment of the present application.
  • the communication system 100 may include a network device 110 , and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal).
  • the network device 110 may provide communication coverage for a particular geographic area, and may communicate with terminal devices located within the coverage area.
  • FIG. 1A exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices.
  • the present application The embodiment does not limit this.
  • FIG. 1B is a schematic structural diagram of another communication system provided by an embodiment of the present application.
  • a terminal device 1101 and a satellite 1102 are included, and wireless communication can be performed between the terminal device 1101 and the satellite 1102 .
  • the network formed between the terminal device 1101 and the satellite 1102 may also be referred to as NTN.
  • the satellite 1102 can function as a base station, and the terminal device 1101 and the satellite 1102 can communicate directly. Under the system architecture, satellite 1102 may be referred to as a network device.
  • the communication system may include multiple network devices 1102, and the coverage of each network device 1102 may include other numbers of terminal devices, which are not limited in this embodiment of the present application.
  • FIG. 1C is a schematic structural diagram of another communication system provided by an embodiment of the present application.
  • a terminal device 1201 including a terminal device 1201 , a satellite 1202 and a base station 1203 , the terminal device 1201 and the satellite 1202 can communicate wirelessly, and the satellite 1202 and the base station 1203 can communicate.
  • the network formed between the terminal device 1201, the satellite 1202 and the base station 1203 may also be referred to as NTN.
  • the satellite 1202 may not have the function of the base station, and the communication between the terminal device 1201 and the base station 1203 needs to be relayed through the satellite 1202 .
  • the base station 1203 may be referred to as a network device.
  • the communication system may include multiple network devices 1203, and the coverage of each network device 1203 may include other numbers of terminal devices, which are not limited in this embodiment of the present application.
  • FIG. 1A-FIG. 1C merely illustrate the system to which the present application applies.
  • the methods shown in the embodiments of the present application may also be applied to other systems, such as a 5G communication system, an LTE communication system, etc. , which is not specifically limited in the embodiments of the present application.
  • the wireless communication system shown in FIG. 1A-FIG. 1C may further include other network entities such as a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF). , which is not limited in the embodiments of the present application.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • a device having a communication function in the network/system may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal device 120 with a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here.
  • the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobility management entity, etc., which are not limited in this embodiment of the present application.
  • the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship.
  • a indicates B it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • corresponding may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.
  • predefinition may be implemented by pre-saving corresponding codes, forms, or other means that can be used to indicate relevant information in devices (for example, including terminal devices and network devices).
  • the implementation method is not limited.
  • predefined may refer to the definition in the protocol.
  • the "protocol” may refer to a standard protocol in the communication field, for example, may include the LTE protocol, the NR protocol, and related protocols applied in future communication systems, which are not limited in this application.
  • the indication information in this embodiment of the present application includes physical layer signaling such as downlink control information (Downlink Control Information, DCI), radio resource control (Radio Resource Control, RRC) signaling, and a media access control unit (Media Access Control Unit).
  • DCI Downlink Control Information
  • RRC Radio Resource Control
  • Media Access Control Unit Media Access Control Unit
  • MAC CE Access Control Control Element
  • the high-level parameters or high-level signaling in the embodiments of the present application include at least one of radio resource control (Radio Resource Control, RRC) signaling and media access control element (Media Access Control Control Element, MAC CE). kind.
  • RRC Radio Resource Control
  • MAC CE Media Access Control Control Element
  • the HARQ mechanism and the HARQ-ACK feedback mechanism related to the present application are first described.
  • HARQ Hybrid Automatic Repeat reQuest
  • RLC Radio Link Control
  • ARQ Layer's Automatic Repeat ReQuest
  • the retransmission of lost or erroneous data is mainly handled by the HARQ mechanism of the MAC layer, supplemented by the retransmission function of the RLC layer.
  • the HARQ mechanism of the MAC layer can provide fast retransmission, and the ARQ mechanism of the RLC layer can provide reliable data transmission.
  • HARQ uses the Stop-and-Wait Protocol (Stop-and-Wait Protocol) to send data.
  • Stop-and-wait Protocol After the sender sends a Transport Block (TB) once, it stops and waits for confirmation. In this way, the sender stops and waits for an acknowledgment after each transmission, resulting in low user throughput. Therefore, NR uses multiple parallel HARQ processes. When one HARQ process is waiting for acknowledgment information, the sender can use another HARQ process to continue sending data.
  • These HARQ processes collectively form a HARQ entity, which incorporates a stop-and-wait protocol, allowing data to be transmitted continuously.
  • HARQ is divided into uplink HARQ and downlink HARQ. Uplink HARQ is for uplink data transmission, and downlink HARQ is for downlink data transmission. The two are independent of each other.
  • the terminal device has its own HARQ entity for each serving cell.
  • Each HARQ entity maintains a set of parallel downlink HARQ processes and a set of parallel uplink HARQ processes.
  • each uplink and downlink carrier supports a maximum of 16 HARQ processes.
  • the network device may indicate the maximum number of HARQ processes to the terminal device through a radio resource control (Radio Resource Control, RRC) signaling semi-static configuration according to the deployment situation of the network device.
  • RRC Radio Resource Control
  • the default number of HARQ processes in downlink is 8, and the maximum number of HARQ processes supported by each uplink carrier is always 16.
  • Each HARQ process corresponds to a HARQ process ID.
  • a broadcast control channel Broadcast Control CHannel, BCCH
  • HARQ ID 0 is used for message 3 (Msg3) transmission in the random process.
  • each downlink HARQ process can only process one TB at the same time; for terminal equipment that supports downlink space division multiplexing, each downlink HARQ process can simultaneously process 1 or 2 TB. Each uplink HARQ process of the terminal device simultaneously processes 1 TB.
  • HARQ is divided into two categories: synchronous and asynchronous in the time domain, and non-adaptive and adaptive in the frequency domain. Both the NR uplink and downlink use the asynchronous adaptive HARQ mechanism. For asynchronous HARQ, the time interval between the retransmission of the same TB and the last transmission is not fixed. Adaptive HARQ can change the frequency domain resources and MCS used for retransmission.
  • the relationship between the number of supported HARQ processes and RTT is described by taking downlink transmission as an example.
  • the maximum number of HARQ processes configured on a terminal device is 16, then if the RTT is small, for example, less than 16ms, the maximum throughput of the terminal device will not be affected. In other words, if the RTT is less than 16ms, the When there is a service to be transmitted, the terminal device can always have a parallel HARQ process for data transmission.
  • the RTT is relatively large, for example, much larger than 16ms
  • the RTT is relatively large, for example, much larger than 16ms
  • the network equipment can schedule the transmission of the Physical Downlink Shared Channel (PDSCH) for the terminal equipment through downlink control information (Downlink Control Information, DCI).
  • DCI Downlink Control Information
  • the DCI includes indication information of a physical uplink control channel (Physical Uplink Control Channel, PUCCH) resource, and after receiving the PDSCH, the terminal device will decode the PDSCH result (Acknowledge, ACK) information or negative acknowledgement (Negative Acknowledge, NACK) information) is fed back to the network device through the PUCCH resource.
  • PUCCH Physical Uplink Control Channel
  • the terminal device will decode the PDSCH result (Acknowledge, ACK) information or negative acknowledgement (Negative Acknowledge, NACK) information) is fed back to the network device through the PUCCH resource.
  • Acknowledge, ACK Physical Uplink Control Channel
  • NACK negative acknowledgement
  • dynamic determination of HARQ feedback timing is supported in the NR system.
  • the network device schedules the terminal device to receive
  • the indication information may include:
  • PUCCH resource indicator used to determine PUCCH resources
  • HARQ feedback timing indication information (eg PDSCH-to-HARQ_feedback timing indicator): used to dynamically determine the time domain position of uplink feedback resources, such as the time slot of PUCCH resources used for HARQ feedback, usually denoted by K1.
  • the HARQ feedback timing indication information is used to indicate the value in the HARQ feedback timing set.
  • the HARQ feedback timing set may be preset or configured by the network device.
  • the HARQ feedback timing indication information includes 3 bits. When the HARQ feedback timing indication information is 000, it indicates the first value in the HARQ feedback timing set, and when the HARQ feedback timing indication information is 001, it indicates that the HARQ feedback timing set is in the HARQ feedback timing set. the second value of , and so on.
  • the terminal equipment includes semi-static codebook feedback such as type 1 (Type-1) HARQ-ACK codebook feedback and dynamic codebook feedback such as type 2 (Type-2) or enhanced type 2 (eType-2) when performing HARQ-ACK feedback. 2) HARQ-ACK codebook feedback.
  • the Type-1 HARQ-ACK codebook includes HARQ-ACK information corresponding to candidate PDSCH transmission opportunities within a HARQ-ACK feedback window.
  • the Type-2 HARQ-ACK codebook includes HARQ-ACK information corresponding to the scheduled PDSCH within a HARQ-ACK feedback window.
  • the DCI format for scheduling PDSCH includes a downlink assignment indicator (Downlink assignment index, DAI) information field:
  • the C-DAI information is used to determine the downlink transmission scheduled by the current DCI is the number of downlink transmissions in the HARQ feedback window, where the C-DAI information is sorted according to the PDCCH The detection opportunities are sorted in order.
  • the DCI can also include:
  • Total DAI (total DAI, T-DAI) information where the T-DAI information is used to determine how many downlink transmissions are included in the HARQ feedback window up to the current DCI scheduling.
  • the eType-2 HARQ-ACK codebook includes HARQ-ACK information corresponding to the PDSCH of a scheduled packet within a HARQ-ACK feedback window.
  • the base station may group the scheduled PDSCH, and indicate the grouping information of the PDSCH through the DCI display signaling of the scheduled PDSCH, so that the UE performs corresponding HARQ-ACK feedback according to different groups after receiving the PDSCH.
  • the DCI in which the base station schedules the UE for PDSCH reception includes indication information of a group index (PDSCH group index) and indication information of a new feedback indication NFI (New feedback indicator).
  • the base station may trigger the feedback of one group when triggering the UE to perform HARQ-ACK feedback, or may trigger the feedback of two groups at the same time.
  • the DCI information may include an information field (Number of requested PDSCH group(s)) for the number of feedback request groups. If the terminal device receives the DCI information sent by the network device, and the number of feedback request groups information field in the DCI information is a preset value, for example, set to 1, the terminal device needs to perform HARQ-ACK feedback of two groups.
  • the terminal device receives the DCI information sent by the network device, and the information field of the number of feedback request groups in the DCI information is a preset value, for example, set to 0, then the terminal device needs to perform the current scheduling group (that is, the PDSCH scheduled by the DCI). the HARQ-ACK feedback of the group to which it belongs).
  • the HARQ feedback window may be determined according to the HARQ feedback timing set or HARQ feedback timing indication information.
  • the HARQ feedback timing indication information can indicate not only valid values but also invalid values.
  • the HARQ feedback timing indication information indicates an invalid value, it may indicate that the time domain position of the uplink feedback resource for feeding back the HARQ-ACK information is temporarily uncertain.
  • the terminal device can determine information such as the HARQ-ACK feedback codebook corresponding to downlink transmission, the PUCCH resource for feeding back HARQ-ACK information, and the time slot for feeding back HARQ-ACK information, according to the above information.
  • the RTT of the signal transmission is very large.
  • the RTT of signal transmission may be in the order of hundreds of milliseconds, for example, the RTT of signal transmission may be about 600 ms at most.
  • the RTT of signal transmission can be on the order of tens of milliseconds. Since the RTT of the NTN system is much larger than the RTT of the terrestrial communication system, the HARQ mechanism in the NR system is no longer applicable to the NTN system.
  • the network device may configure and disable one or some downlink HARQ processes of the terminal device.
  • the network device can reuse the HARQ process for data transmission without receiving the HARQ-ACK information fed back by the terminal device for the TB transmitted in the HARQ process. Therefore, the network device can use the disabled HARQ process to schedule multiple data packets for the terminal device, thereby reducing the impact of RTT.
  • the network device may instruct the terminal device to disable HARQ-ACK feedback of one or some downlink HARQ processes.
  • the terminal device when the terminal device is configured with Type-1 or Type-2 or eType-2 HARQ-ACK codebook feedback, when the terminal device should transmit the HARQ corresponding to the downlink data transmission on the first PUCCH resource -In the case of ACK information, if the first PUCCH resource and the first PUSCH resource of the terminal device at least partially overlap in the time domain, how to determine whether to multiplex the HARQ-ACK information corresponding to the downlink data transmission on the first PUSCH or How to determine the number of bits included in the HARQ-ACK information multiplexed on the first PUSCH is an urgent problem to be solved.
  • FIG. 3 is a schematic interaction diagram of a method 300 for wireless communication provided by an embodiment of the present application. As shown in FIG. 3 , the method 300 may include at least some of the following contents:
  • the network device schedules the first PUSCH transmission to the terminal device, and the first physical downlink channel is associated with the first PUSCH;
  • the terminal device determines whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH according to the reception of the first physical downlink channel, wherein the first HARQ - The ACK information corresponds to the reception situation of the first physical downlink channel.
  • the first PUSCH transmission may be scheduled by the first DCI, and S310 may include:
  • the network device sends the first DCI to the terminal device, where the first DCI is used to schedule the first PUSCH transmission, and the first DCI includes the first downlink assignment indication DAI information, and the first DAI information is used to schedule the first PUSCH transmission. for indicating the number of first physical downlink channels associated with the first PUSCH;
  • the terminal device receives the first DCI.
  • S320 may be replaced by: the terminal device determines whether to multiplex and transmit the first hybrid on the first PUSCH according to the first DAI information and/or the reception condition of the first physical downlink channel Automatically request retransmission and acknowledge HARQ-ACK information, wherein the first HARQ-ACK information corresponds to the reception condition of the first physical downlink channel.
  • the DCI format corresponding to the first DCI includes at least one of the following: DCI format 0_1 and DCI format 0_2, or other DCI formats including DAI information.
  • S310 may include:
  • the network device sends scheduling information to the terminal device, where the scheduling information is used to determine to transmit the first PUSCH.
  • the scheduling information does not include DCI, or the scheduling information includes a second DCI and the second DCI does not include DAI information.
  • the first PUSCH may not be scheduled by DCI, for example, the resource location corresponding to the first PUSCH is semi-statically configured, or may be scheduled by DCI that does not include DAI information.
  • the first PUSCH may be scheduled by DCI including DAI information, or may be scheduled by DCI not including DAI information, or may not be scheduled by DCI.
  • the DCI format corresponding to the second DCI includes DCI format 0_0, or may also be other DCI formats that do not include DAI information.
  • S310 may include:
  • the network device sends the first DCI to the terminal device, where the first DCI is used to schedule the first PUSCH transmission, the first DCI includes first DAI information, and the first DAI information is used to indicate whether the first DCI is in the first Multiplexing and transmitting the first HARQ-ACK information on the PUSCH, and the first physical downlink channel is associated with the first PUSCH;
  • the terminal device receives the first DCI.
  • S320 may be replaced by: the terminal device determines whether to multiplex and transmit the first HARQ-ACK on the first PUSCH according to the first DAI information and the reception condition of the first physical downlink channel information, wherein the first HARQ-ACK information corresponds to the reception situation of the first physical downlink channel.
  • S320 may be replaced by: the terminal device determines, according to the first DAI information, whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH, wherein the first HARQ-ACK information Corresponding to the reception situation of the first physical downlink channel.
  • the terminal device is configured with Type-1 HARQ-ACK codebook feedback; or, the first DAI information includes 1 bit.
  • the DCI format corresponding to the first DCI includes at least one of the following: DCI format 0_1 and DCI format 0_2, or may also be other DCI formats including DAI information.
  • associations can include:
  • the first PUSCH is not scheduled by DCI or the DCI scheduling the first PUSCH does not include DAI information;
  • the first DAI information associated with the first PUSCH includes 1 bit, and the first DAI information is not used to indicate the number of the first physical downlink channels.
  • S310 may include: the network device sends pre-configured grant (Configured Grant, CG) information to the terminal device,
  • the preconfigured grant information is used to schedule first PUSCH transmission, where the first PUSCH is a preconfigured grant PUSCH.
  • the preconfigured authorization information may be preconfigured authorization configuration information or preconfigured authorization activation information.
  • the HARQ-ACK corresponding to the physical downlink channel associated with the first PUSCH can be determined according to the manner described in the embodiments of the present application Whether to multiplex on the first PUSCH, and/or determine the number of bits included in the HARQ-ACK corresponding to the physical downlink channel multiplexed on the first PUSCH.
  • the specific implementation of the first physical downlink channel and the multiplexing method of the HARQ-ACK information corresponding to the first physical downlink channel will be described in detail. It should be understood that the features described below are applicable to the first PUSCH unless otherwise specified. Any scheduling method, such as the scheduling methods in Embodiment 1 to Embodiment 3.
  • the first physical downlink channel associated with the first PUSCH may refer to: the first PUSCH resource corresponding to the first PUSCH and the uplink HARQ-ACK feedback corresponding to the first physical downlink channel The resources overlap at least partially in the time domain.
  • the uplink HARQ-ACK feedback resource of the first physical downlink channel may be, for example, the first PUCCH resource.
  • the specific meaning of the first DAI information in the embodiments of the present application, and/or the specific implementation of the first physical downlink channel, and/or, whether the terminal device is on the first PUSCH is described
  • a method for multiplexing and transmitting the first HARQ-ACK information, and/or a method for how the terminal device determines the size of the first HARQ-ACK information multiplexing and transmitting on the first PUSCH is described.
  • the first physical downlink channel includes at least one of the following:
  • the physical downlink control channel Physical Downlink Control Channel, PDCCH
  • PDCCH Physical Downlink Control Channel
  • PDCCHs corresponding to HARQ-ACK information or in other words, PDCCHs associated with HARQ-ACK information.
  • the first physical downlink channel may include a PDSCH that satisfies a specific condition, denoted as the first type of PDSCH, and the first type of PDSCH is associated with the PDCCH and transmitted through the HARQ process corresponding to the first state.
  • the first HARQ process includes at least one HARQ process.
  • the PDSCH associated with the PDCCH may include at least one of the following:
  • PDCCH scheduled SPS PDSCH for activating SPS PDSCH transmission PDCCH scheduled SPS PDSCH for activating SPS PDSCH transmission.
  • the first physical downlink channel does not include PDSCH transmission associated with the PDCCH and the second HARQ process, where the second HARQ process includes a HARQ process corresponding to the second state.
  • the second HARQ process includes at least one HARQ process.
  • the first physical downlink channel may include at least one of the first type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, the PDCCH indicating the sleep state of the secondary cell, and other PDCCHs corresponding to HARQ-ACK information, and does not include the first type of PDSCH.
  • the second type of PDSCH wherein the second type of PDSCH is associated with the PDCCH and transmitted through the HARQ process corresponding to the second state.
  • the HARQ process corresponding to the first state includes at least one of the following situations:
  • the HARQ process corresponds to an enabled state
  • the HARQ process is not configured with a disable parameter
  • the HARQ process corresponds to uplink HARQ-ACK feedback.
  • the state of the HARQ process is an enabled state, or the PDSCH transmitted through the HARQ process needs to be fed back with uplink HARQ-ACK.
  • the HARQ process corresponding to the second state includes at least one of the following situations:
  • the HARQ process corresponds to a disabled state
  • the HARQ process is configured with a disable parameter.
  • the disabled state is also referred to as the disabled state.
  • the disabling parameter is configured by the network device to the terminal device through at least one of RRC signaling, MAC CE and physical layer signaling such as DCI.
  • the HARQ process corresponding to the second state does not correspond to uplink HARQ-ACK feedback, that is, no HARQ-ACK feedback is required.
  • the network device may configure whether the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback.
  • the network device may send first indication information to the terminal device, where the first indication information is used to indicate whether the HARQ process corresponding to the second state performs uplink HARQ-ACK feedback.
  • the first indication information indicates that the HARQ process corresponding to the second state does not need to perform uplink HARQ-ACK feedback, and when the terminal device receives the PDSCH transmitted by the HARQ process corresponding to the second state, it does not need to send The network device feeds back HARQ-ACK information corresponding to the PDSCH.
  • whether the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback may be predefined. For example, it is pre-defined that the HARQ process corresponding to the second state does not need to perform uplink HARQ-ACK feedback.
  • the first DAI information is 1 bit, 2 bits, or other bit numbers.
  • the first DAI information is used to indicate whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH.
  • the first DAI information includes 1 bit, when the 1 bit indicates 1, it is used to indicate that the first HARQ-ACK information is multiplexed and transmitted on the first PUSCH, and when the 1 bit indicates 0, it is used to indicate that the The first HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.
  • the first DAI information is used to indicate the number of the first physical downlink channels associated with the first PUSCH, then when the first physical downlink channel is the case in the first implementation , the number of the first physical downlink channels indicated by the first DAI information includes the first type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, the PDCCH indicating the sleep state of the secondary cell, and other PDCCHs corresponding to the HARQ-ACK information. at least one number. Further optionally, the number of the second type of PDSCH is not included in the number of the first physical downlink channels indicated by the first DAI information.
  • Table 1 shows that when the first DAI information includes 2 bits and the first physical downlink channel includes the first type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, and the PDCCH indicating the sleep state of the secondary cell, the first DAI information is obtained in Table 1. the meaning of the value.
  • LSB represents a low-order bit (Least Significant Bit, LSB)
  • MSB represents a high-order bit (most significant bits, MSB).
  • the first physical downlink channel includes at least one of the following situations:
  • the first HARQ process includes a HARQ process corresponding to the first state
  • the second HARQ process the process includes a HARQ process corresponding to the second state
  • PDCCHs corresponding to HARQ-ACK information or in other words, PDCCHs associated with HARQ-ACK information.
  • the first physical downlink channel may include PDSCH transmission associated with the PDCCH and the second HARQ process, wherein the second HARQ process includes the HARQ process corresponding to the second state .
  • the first physical downlink channel includes the second type of PDSCH.
  • the first physical downlink channel includes the PDSCH of the first type, the PDSCH of the second type, the PDCCH indicating the release of the SPS PDSCH, the PDCCH indicating the sleep state of the secondary cell, and other PDCCHs corresponding to HARQ-ACK information. at least one of.
  • the HARQ process corresponding to the second state corresponds to uplink HARQ-ACK feedback.
  • the network device may configure whether the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback.
  • the network device may send first indication information to the terminal device, where the first indication information is used to indicate whether the HARQ process corresponding to the second state performs uplink HARQ-ACK feedback.
  • the first indication information indicates that the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback.
  • the terminal device receives the PDSCH transmitted by the HARQ process corresponding to the second state, it needs to report to the network device. Feedback HARQ-ACK information corresponding to the PDSCH.
  • whether the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback may be predefined. For example, it is predefined that the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback.
  • the first DAI information is used to indicate whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH.
  • the first DAI information includes 1 bit, when the bit indicates 1, it is used to indicate that the first HARQ-ACK information is multiplexed and transmitted on the first PUSCH, and when the bit indicates 0, it is used to indicate that the The first HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.
  • the first DAI information is used to indicate the number of the first physical downlink channels associated with the first PUSCH, when the first physical downlink channel is the situation in the second implementation manner , the number of the first physical downlink channels indicated by the first DAI information includes the first type PDSCH, the second type PDSCH, the PDCCH indicating the release of the SPS PDSCH, the PDCCH indicating the sleep state of the secondary cell, and other corresponding HARQ-ACK information The number of at least one of the PDCCHs.
  • Table 2 shows that in the second implementation, when the first DAI information includes 2 bits, the first physical downlink channel includes the first type PDSCH, the second type PDSCH, the PDCCH indicating the release of the SPS PDSCH, and the PDCCH indicating the sleep state of the secondary cell, The meaning of the value of the first DAI information.
  • the terminal device may determine the meaning of the first DAI information according to first indication information of the network device, where the first indication information is used to indicate that the first indication information corresponds to the first DAI information. Whether the two-state HARQ process performs uplink HARQ-ACK feedback. Alternatively, the terminal device may determine whether the HARQ process corresponding to the second state performs uplink HARQ-ACK feedback according to the first indication information of the network device, where the first indication information is used to indicate the first DAI information meaning.
  • the meaning of the first DAI information may be the situation in the first implementation.
  • the terminal device may not feed back the HARQ feedback information corresponding to the PDSCH transmitted through the HARQ process in the second state to the network device. That is, only the HARQ feedback information corresponding to the PDSCH transmitted through the HARQ process in the first state is fed back to the network device.
  • the meaning of the first DAI information may be the situation in the second implementation.
  • the terminal device may feed back HARQ feedback information corresponding to the PDSCH transmitted through the HARQ process in the second state to the network device. That is, the HARQ feedback information corresponding to the PDSCH transmitted through the HARQ process in the first state and the second state is fed back to the network device.
  • the following describes how to determine whether to multiplex and transmit the first HARQ-ACK information corresponding to the first physical downlink channel on the first PUSCH, or how to determine whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH based on the foregoing implementation manners 1 and 2 The number of bits included in the first HARQ-ACK message used.
  • the terminal device may determine whether to perform multiplexing on the first PUSCH according to at least one of the first DAI information, the reception situation of the first physical downlink channel, and a feedback rule. Use to transmit the first HARQ-ACK information corresponding to the first physical downlink channel.
  • the feedback rule includes whether the terminal device needs to multiplex and transmit HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH.
  • the feedback rule includes the first indication information.
  • the terminal device if the number of the first physical downlink channels received by the terminal device is greater than or equal to 1, or the terminal device needs to multiplex and transmit SPS on the first PUSCH HARQ-ACK information corresponding to the PDSCH, the terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH.
  • the first physical downlink channel includes the first type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, and the PDCCH indicating the sleep state of the secondary cell. If the terminal device receives the first physical downlink channel associated with the first PUSCH The total number is greater than or equal to 1, or the terminal device needs to multiplex and transmit HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, then the terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH.
  • the first physical downlink channel includes the first type of PDSCH, the second type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, and the PDCCH indicating the sleep state of the secondary cell.
  • the total number of the first physical downlink channels is greater than or equal to 1, or the terminal device needs to multiplex and transmit the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, then the terminal device multiplexes and transmits on the first PUSCH The first HARQ-ACK information.
  • the terminal device if the terminal device does not receive the first physical downlink channel, and the terminal device does not need to multiplex and transmit the HARQ- corresponding to the SPS PDSCH on the first PUSCH ACK information, and the first DAI information indicates a preset value, the terminal device does not multiplex and transmit the first HARQ-ACK information on the first PUSCH.
  • this situation may be applicable to the scheduling method of the first PUSCH in the foregoing Embodiment 1.
  • the preset value may be, for example, 4, etc., which is not limited in this application.
  • the first physical downlink channel includes the first type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, and the PDCCH indicating the sleep state of the secondary cell. If the terminal device receives the first physical downlink channel associated with the first PUSCH The total number is 0 (in other words, the terminal device has not received any first physical downlink channel), and the terminal device does not need to multiplex and transmit the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, and the first The value indicated by the DAI information is 4, then the terminal device does not multiplex and transmit the first HARQ-ACK information on the first PUSCH.
  • the first physical downlink channel includes the first type of PDSCH, the second type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, and the PDCCH indicating the sleep state of the secondary cell.
  • the total number of a physical downlink channel is 0 (or the terminal device does not receive any first physical downlink channel), and the terminal device does not need to multiplex and transmit the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH , and the value indicated by the first DAI information is 4, then the terminal device does not multiplex and transmit the first HARQ-ACK information on the first PUSCH.
  • the terminal device if the terminal device does not receive the first physical downlink channel, and the terminal device needs to multiplex and transmit the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH , the terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH, where the first HARQ-ACK information includes the HARQ-ACK information corresponding to the SPS PDSCH.
  • the terminal device if the terminal device does not receive the first physical downlink channel, and the terminal device does not need to multiplex and transmit the HARQ-ACK corresponding to the SPS PDSCH on the first PUSCH information, the terminal device does not multiplex and transmit the first HARQ-ACK information on the first PUSCH.
  • the first PUSCH is not associated with the first DAI information.
  • the first PUSCH is not scheduled by DCI or the DCI scheduling the first PUSCH does not include DAI information.
  • the first DAI information associated with the first PUSCH is not used to indicate the number of the first physical downlink channels.
  • the first DAI information includes 1 bit.
  • the first physical downlink channel includes the first type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, and the PDCCH indicating the sleep state of the secondary cell. If the terminal device receives the first physical downlink channel associated with the first PUSCH The total number is 0 (or the terminal device has not received any first physical downlink channel), and the terminal device does not need to multiplex and transmit the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, then the terminal device The first HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.
  • the first physical downlink channel includes the first type of PDSCH, the second type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, and the PDCCH indicating the sleep state of the secondary cell.
  • the total number of a physical downlink channel is 0 (or the terminal device does not receive any first physical downlink channel), and the terminal device does not need to multiplex and transmit the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH , the terminal device does not multiplex and transmit the first HARQ-ACK information on the first PUSCH.
  • the first DAI information is used to indicate whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH. If the first DAI information associated with the first PUSCH received by the terminal device indicates a preset value such as 1, the terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH, Alternatively, if the first DAI information associated with the first PUSCH received by the terminal device indicates another preset value such as 0, the terminal device does not multiplex and transmit the first HARQ- ACK information, or, if the first DAI information associated with the first PUSCH received by the terminal device indicates another preset value such as 0, and the terminal device only receives one first physical downlink channel, then The terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH.
  • the first DAI information associated with the first PUSCH is not used to indicate the number of the first physical downlink channels.
  • the first DAI information includes 1 bit.
  • the terminal device since the first HARQ-ACK information includes HARQ-ACK information reflecting the reception of the first physical downlink channel, when the terminal device does not receive the first physical downlink channel, and the When the terminal device does not need to multiplex and transmit the HARQ-ACK information corresponding to the SPS PDSCH, the terminal device does not need to multiplex the first HARQ-ACK information on the first PUSCH.
  • the terminal device if the first indication information indicates that the HARQ process corresponding to the second state, for example, the disabled state, does not need to perform uplink HARQ-ACK feedback, the terminal device does not correspond to the HARQ-ACK feedback.
  • the HARQ-ACK information corresponding to the PDSCH of the HARQ process in the second state is multiplexed onto the first PUSCH, or the first HARQ-ACK information does not include the HARQ-ACK corresponding to the PDSCH of the HARQ process in the second state information.
  • the first physical downlink channel does not include the PDSCH associated with the PDCCH and the HARQ process corresponding to the second state. That is to say, if the terminal device only receives the PDSCH associated with the PDCCH and the HARQ process corresponding to the second state, it is considered that it has not received the first physical downlink channel.
  • the terminal device determines the bit size included in the first HARQ-ACK information according to the first DAI information and/or the reception situation of the first physical downlink channel.
  • the terminal device may determine the first HARQ-ACK information according to the reception situation of the first DAI information and/or the first physical downlink channel.
  • the bit size included in the first HARQ-ACK information may be determined according to the first DAI information, where the first DAI information is used to indicate the total number of first physical downlink channels associated with the first PUSCH number. It should be noted here that since the SPS PDSCH is not dynamically scheduled by the PDCCH, the number indicated by the first DAI information does not include the number of the SPS PDSCH.
  • the first DAI information associated with the first PUSCH includes 2 bits.
  • the value range of the first DAI information Y is 1 to 4, and it is assumed that the first DAI received by the terminal device
  • the value of the information indication is Y
  • the terminal device determines the bit size included in the first HARQ-ACK information according to the first DAI information and the reception of the first physical downlink channel, including: when the terminal device receives the first If the total number of physical downlink channels is less than or equal to Y, the total number X of the first physical downlink channels for which HARQ-ACK information needs to be fed back is equal to Y; when the total number of first physical downlink channels received by the terminal device is greater than Y and less than or equal to Y+4, the total number X of the first physical downlink channels for which HARQ-ACK information needs to be fed back is equal to Y+4; when the total number of first physical downlink channels received by the terminal device is greater than Y +4 and less than or equal to Y+
  • the first HARQ-ACK information includes HARQ-ACK information corresponding to the X first physical downlink channels.
  • the terminal device needs to multiplex and transmit HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, the first HARQ-ACK information also includes the HARQ-ACK information corresponding to the SPS PDSCH.
  • the terminal device may determine the bit size included in the first HARQ-ACK information according to the reception situation of the first physical downlink channel, or in other words, the first HARQ-ACK information includes the bit size received by the terminal device HARQ-ACK information corresponding to the first physical downlink channel.
  • the first PUSCH is not associated with the first DAI information.
  • the first PUSCH is not scheduled by DCI or the DCI scheduling the first PUSCH does not include DAI information.
  • the first DAI information associated with the first PUSCH is not used to indicate the number of the first physical downlink channels.
  • the first DAI information includes 1 bit.
  • the terminal device may determine the bit size included in the first HARQ-ACK information according to the first DAI information and/or the reception condition of the first physical downlink channel, where the first DAI information is used for Indicates whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH. If the first DAI information associated with the first PUSCH received by the terminal device indicates a preset value such as 1, the terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH, And the number of bits included in the first HARQ-ACK information may be determined according to the number of PDSCH candidates included in the HARQ feedback window.
  • the terminal device may multiplexes and transmits the first HARQ-ACK information on the first PUSCH, where the first HARQ-ACK information only includes the HARQ-ACK feedback information of the first physical downlink channel.
  • the terminal device is configured with Type-1 codebook feedback.
  • the DAI information associated with the first PUSCH includes 1 bit.
  • the first HARQ-ACK information also includes the HARQ-ACK information corresponding to the SPS PDSCH.
  • the first PUSCH is associated with a second physical downlink channel
  • the method 300 further includes: the terminal device, according to the reception of the second physical downlink channel, determines whether to The number of bits included in the multiplexed transmission of the second HARQ-ACK information on the first PUSCH and/or the second HARQ-ACK information multiplexed on the first PUSCH, where the second HARQ-ACK information corresponds to The reception situation of the second physical downlink channel.
  • the first DCI further includes second DAI information, where the second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH .
  • the method 300 further includes: the terminal device determines whether to multiplex and transmit the second HARQ on the first PUSCH according to the second DAI information and/or the reception condition of the second physical downlink channel - the number of bits included in the ACK information and/or the second HARQ-ACK information multiplexed on the first PUSCH, where the second HARQ-ACK information corresponds to the reception situation of the second physical downlink channel.
  • the second physical downlink channel associated with the second PUSCH may refer to: the first PUSCH resource corresponding to the first PUSCH and the uplink HARQ-ACK feedback resource of the second physical downlink channel are at least partially in the time domain overlapping.
  • the first physical downlink channel includes a downlink channel corresponding to TB feedback, or the HARQ-ACK feedback of the first physical downlink channel corresponds to TB-based HARQ-ACK feedback.
  • the second physical downlink channel includes a downlink channel corresponding to CBG feedback, or the HARQ-ACK feedback of the second physical downlink channel corresponds to CBG-based HARQ-ACK feedback.
  • the corresponding HARQ-ACK feedback codebook may include two HARQ-ACK feedback subcodebooks, wherein the first HARQ-ACK feedback subcodebook The codebook includes TB-based feedback, the second HARQ-ACK feedback sub-codebook includes code block group (Code Block Group, CBG)-based feedback, and the first DAI information and the second DAI information are used to determine the two The size of the HARQ-ACK subcodebook.
  • the codebook includes TB-based feedback
  • the second HARQ-ACK feedback sub-codebook includes code block group (Code Block Group, CBG)-based feedback
  • the first DAI information and the second DAI information are used to determine the two The size of the HARQ-ACK subcodebook.
  • the first DCI includes the second DAI information:
  • the terminal device is configured to feed back two HARQ-ACK subcodebooks
  • the terminal equipment is configured with code block group CBG transmission;
  • the end device is configured with CBG feedback.
  • the specific meaning of the second DAI information, and/or the specific implementation of the second physical downlink channel, and/or whether the terminal device multiplexes and transmits the second physical downlink channel on the first PUSCH will be described.
  • the second physical downlink channel includes at least one of the following situations:
  • the third HARQ process includes the HARQ process corresponding to the first state
  • PDCCHs corresponding to HARQ-ACK information or in other words, PDCCHs associated with HARQ-ACK information.
  • the second physical downlink channel includes the first type of PDSCH, and the first type of PDSCH is associated with the PDCCH and transmitted through the third HARQ process corresponding to the first state.
  • the second physical downlink channel includes the first type of PDSCH feedback corresponding to the CBG.
  • the third HARQ process includes at least one HARQ process.
  • the second physical downlink channel does not include PDSCH transmission associated with a PDCCH and a fourth HARQ process, where the fourth HARQ process includes a HARQ process corresponding to the second state.
  • the second physical downlink channel does not include the second type of PDSCH feedback corresponding to the CBG.
  • the fourth HARQ process includes at least one HARQ process.
  • the second physical downlink channel may include at least one of the first type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, the PDCCH indicating the sleep state of the secondary cell, and other PDCCHs corresponding to HARQ-ACK information, and does not include the first type of PDSCH.
  • the second type of PDSCH wherein the second type of PDSCH is associated with the PDCCH and transmitted through the HARQ process corresponding to the second state.
  • the HARQ process corresponding to the second state does not correspond to uplink HARQ-ACK feedback.
  • the second DAI information is 0 bits (that is, does not include the second DAI information), 1 bit, or 2 bits or other bits and the like.
  • the second DAI information is used to indicate whether to multiplex and transmit the second HARQ-ACK information on the first PUSCH.
  • the second DAI information includes 1 bit, when the 1 bit indicates 1, it is used to indicate that the second HARQ-ACK information is multiplexed and transmitted on the first PUSCH, and when the 1 bit indicates 0, it is used to indicate that the The second HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.
  • the second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH, then when the second physical downlink channel is the situation in the third implementation
  • the number of the second physical downlink channels indicated by the second DAI information includes the first type PDSCH, the PDCCH indicating the release of the SPS PDSCH, the PDCCH indicating the sleep state of the secondary cell, and other PDCCHs corresponding to the HARQ-ACK information. at least one number.
  • the number of the second type of PDSCH is not included in the number of the second physical downlink channels indicated by the second DAI information.
  • the second physical downlink channel includes at least one of the following situations:
  • the third HARQ process includes a HARQ process corresponding to the first state
  • the fourth HARQ process includes a HARQ process corresponding to the second state
  • PDCCHs corresponding to HARQ-ACK information or PDCCHs associated with HARQ-ACK information.
  • the second physical downlink channel may include PDSCH transmission associated with the PDCCH and the second HARQ process, where the second HARQ process includes the HARQ process corresponding to the second state .
  • the second physical downlink channel includes the second type of PDSCH.
  • the second physical downlink channel includes the first type of PDSCH, the second type of PDSCH, the PDCCH indicating the release of the SPS PDSCH, the PDCCH indicating the sleep state of the secondary cell, and other PDCCHs corresponding to HARQ-ACK information. at least one of.
  • the HARQ process corresponding to the second state corresponds to uplink HARQ-ACK feedback.
  • the terminal device may determine the meaning of the second DAI information according to first indication information of the network device, where the first indication information is used to indicate that the first indication information corresponds to the first indication information. Whether the two-state HARQ process performs uplink HARQ-ACK feedback. Alternatively, the terminal device may determine whether the HARQ process corresponding to the second state performs uplink HARQ-ACK feedback according to the first indication information of the network device, where the first indication information is used to indicate the second DAI information meaning.
  • the meaning of the second DAI information may be the situation in the third implementation.
  • the terminal device may not feed back the HARQ feedback information corresponding to the PDSCH transmitted through the HARQ process in the second state to the network device. That is, only the HARQ feedback information corresponding to the PDSCH transmitted through the HARQ process in the first state is fed back to the network device.
  • the meaning of the second DAI information may be the situation in the fourth implementation.
  • the terminal device may feed back HARQ feedback information corresponding to the PDSCH transmitted through the HARQ process in the second state to the network device. That is, the HARQ feedback information corresponding to the PDSCH transmitted through the HARQ process in the first state and the second state is fed back to the network device.
  • the terminal device may further determine whether to multiplex and transmit the second HARQ-ACK information corresponding to the second physical downlink channel on the first PUSCH, and/or determine the first HARQ-ACK information corresponding to the second physical downlink channel. The number of bits included in the second HARQ-ACK information multiplexed on the PUSCH.
  • the specific implementation of determining by the terminal device whether to multiplex and transmit the second HARQ-ACK information corresponding to the second physical downlink channel on the first PUSCH may refer to the foregoing embodiments.
  • the relevant implementation of the terminal device determining whether to multiplex and transmit the first HARQ-ACK information corresponding to the first physical downlink channel on the first PUSCH is not repeated here for brevity.
  • the terminal device if the number of the second physical downlink channels received by the terminal device is greater than or equal to 1, the terminal device multiplexes and transmits the first PUSCH on the first PUSCH. 2 HARQ-ACK information; or, if the terminal device does not receive the second physical downlink channel, the terminal device does not multiplex and transmit the second HARQ-ACK information on the first PUSCH.
  • the terminal device if the number of the second physical downlink channels received by the terminal device is greater than or equal to 1, the terminal device, according to the second DAI information, The second HARQ-ACK information is multiplexed and transmitted on the PUSCH; or, if the terminal device does not receive the second physical downlink channel, and the second DAI information indicates the preset value, the terminal device The device transmits the second HARQ-ACK information without multiplexing on the first PUSCH.
  • the first DCI does not include the second DAI information.
  • the first DAI information and/or the second DAI in the first DCI will be described by using the first DCI corresponding to DCI format 0_1 to schedule the first PUSCH transmission in combination with several typical HARQ-ACK codebook feedback methods.
  • the role of information and the specific reuse method will be described by using the first DCI corresponding to DCI format 0_1 to schedule the first PUSCH transmission in combination with several typical HARQ-ACK codebook feedback methods. The role of information and the specific reuse method.
  • the terminal device is configured with Type-1 HARQ-ACK codebook feedback
  • the first DAI information includes 1 bit
  • the second DAI information includes 0 bits (or, in other words, does not include the second DAI information).
  • the first DAI information is used to indicate whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH.
  • the first DAI information includes 1 bit, when the bit indicates 1, it is used to indicate that the first HARQ-ACK information is multiplexed and transmitted on the first PUSCH, and when the bit indicates 0, it is used to indicate that the The first HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.
  • the terminal device may determine the number of bits included in the first HARQ-ACK information according to the number of candidate PDSCHs included in the HARQ feedback window. Or, when the first DAI information indicates 0, and the terminal device only receives one first physical downlink channel, the terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH, wherein the first HARQ-ACK The information only includes the HARQ-ACK feedback information of the first physical downlink channel.
  • the network device sets this bit to 1; or, if the network device does not send the first physical downlink channel associated with the first PUSCH When the physical downlink channel or only one first physical downlink channel associated with the first PUSCH is sent, the network device sets this bit to 0.
  • the terminal device is configured with Type-2 HARQ-ACK codebook feedback, then,
  • Case 1 If a HARQ-ACK codebook is included, or the terminal device is not configured for CBG transmission or CBG feedback, the first DAI information includes 2 bits to determine the size of the HARQ-ACK codebook, and the second DAI information includes 0 bits (or not including the second DAI information).
  • the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH.
  • the network device may set the value of the first DAI information according to the total number of scheduled first physical downlink channels associated with the first PUSCH.
  • the first DAI information includes 2 bits, which are used to determine the size of the first HARQ-ACK subcodebook.
  • the 2DAI information includes 2 bits and is used to determine the size of the second HARQ-ACK subcodebook.
  • the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH.
  • the first physical downlink channel corresponds to TB feedback, that is, the first physical downlink channel includes a physical downlink channel that needs to be based on TB feedback.
  • the first DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH.
  • the second physical downlink channel corresponds to CBG feedback, that is, the second physical downlink channel includes a physical downlink channel that needs to be based on CBG feedback.
  • the first DAI information includes 2 bits for determining the size of the HARQ-ACK codebook, and the second DAI information includes 0 bits (or does not include the second DAI information).
  • the first DAI information is used to indicate the first physical downlink channel corresponding to the first group (or group 0) associated with the first PUSCH number of.
  • the first DAI information is used to indicate the first physical downlink channel of the corresponding scheduling group (eg, group 0 or group 1) associated with the first PUSCH. number.
  • the first DAI information includes 2 DAI information, and each DAI information includes 2 bits, that is, the first DAI information includes 4 bits, which are used to determine the size of the HARQ-ACK codebook, and the second DAI information includes 0 bits ( Or does not include the second DAI information).
  • the first DAI information in the first DAI information is used to indicate the number of the first physical downlink channels corresponding to the first group associated with the first PUSCH.
  • the second DAI information in the first DAI information is used to indicate the number of the first physical downlink channels corresponding to the second group associated with the first PUSCH.
  • Case 3 CBG feedback is configured, the first DAI information includes 2 bits, and the second DAI information includes 2 bits.
  • the first DAI information is used to indicate the number of the first physical downlink channels associated with the first PUSCH corresponding to the first group and corresponding to the TB feedback .
  • the second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH and corresponding to the first group and corresponding to CBG feedback.
  • the first DAI information is used to indicate the corresponding scheduling group (eg, group 0 or group 1) associated with the first PUSCH and the first corresponding TB feedback Number of physical downlink channels.
  • the second DAI information is used to indicate the corresponding scheduling group (eg, group 0 or group 1) associated with the first PUSCH and the number of second physical downlink channels fed back by the corresponding CBG.
  • Case 4 CBG feedback is configured, the first DAI information includes 2 DAI information, each DAI information includes 2 bits, the second DAI information includes 2 DAI information, and each DAI information includes 2 bits.
  • the first DAI information in the first DAI information is used to indicate the number of the first physical downlink channels corresponding to the first group and corresponding to the TB feedback associated with the first PUSCH.
  • the second DAI information in the first DAI information is used to indicate the number of the first physical downlink channels corresponding to the second group and corresponding to the TB feedback associated with the first PUSCH.
  • the first DAI information in the second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH and corresponding to the first group and corresponding to CBG feedback.
  • the second DAI information in the second DAI information is used to indicate the number of second physical downlink channels corresponding to the second group and corresponding to the CBG feedback associated with the first PUSCH.
  • the size of the DAI information in DCI format 0_1 includes one of the situations shown in Table 3:
  • a0 or b0 represents the Least Significant Bit (LSB) in the DAI information
  • a3 or b3 represents the MSB (most significant bits, MSB) in the DAI information.
  • S320 may include:
  • the terminal device If the terminal device is not configured for CBG transmission (for example, the terminal device is not provided with the high-level parameter PDSCH-CodeBlockGroupTransmission), and the terminal device receives the first PUSCH transmission scheduled in the first DCI format including the first DAI information, and the first DAI
  • the value of the information is a preset value, and the terminal device has not received the PDCCH received by the PDSCH of the HARQ process corresponding to the enabled state scheduled by DCI format 1_0 or DCI format 1_1 in the PDCCH detection opportunity corresponding to the HARQ feedback window, or has not received the PDCCH received.
  • the terminal device does not multiplex the HARQ-ACK information received by the corresponding SPS PDSCH on the first PUSCH, then the terminal device does not multiplex the first HARQ-ACK information on the first PUSCH;
  • the terminal device receives the first PUSCH transmission scheduled in the first DCI format including the first DAI information corresponding to a certain group label, and the first DAI information is a preset value, and the terminal device does not receive any DCI
  • the format schedule corresponds to the PDCCH received by the PDSCH of the HARQ process of the group label and corresponding to the enabled state, and the terminal device does not receive any DCI format indication to feedback the HARQ-ACK information request corresponding to the group label, then the terminal equipment The device does not multiplex the HARQ-ACK information corresponding to the group number on the first PUSCH.
  • S320 may include:
  • the terminal device is not configured for CBG transmission (for example, the terminal device is not provided with the high-level parameter PDSCH-CodeBlockGroupTransmission), and the terminal device receives the first PUSCH transmission scheduled in the first DCI format including the first DAI information, and the first DAI
  • the value of the information is a preset value, and the terminal device has not received the PDSCH reception of the HARQ process corresponding to the enabled and disabled states scheduled by DCI format 1_0 or DCI format 1_1 in the PDCCH detection opportunity corresponding to the HARQ feedback window.
  • the terminal device does not multiplex the HARQ-ACK information received corresponding to the SPS PDSCH on the first PUSCH, then the terminal device does not use the first HARQ - ACK information is multiplexed on the first PUSCH;
  • the terminal device receives the first PUSCH transmission scheduled in the first DCI format including the first DAI information corresponding to a certain group label, and the first DAI information is a preset value, and the terminal device does not receive any DCI
  • S320 may include:
  • the terminal device is configured for CBG transmission (for example, the terminal device is provided with the high-level parameter PDSCH-CodeBlockGroupTransmission), and the terminal device receives the first PUSCH transmission scheduled in the first DCI format including the first DAI information and the second DAI information, and the The first DAI information is a preset value or the second DAI information is a preset value, and the terminal device does not receive the corresponding DCI format 1_0 or DCI format 1_1 scheduling in the PDCCH detection opportunity corresponding to the HARQ feedback window
  • the PDCCH received by the PDSCH corresponding to the HARQ process in the enabled state, or the PDCCH indicating the release of the SPS PDSCH on any serving cell is not received, or the PDCCH indicating the DCI format 1_1 of the SCell dormancy is not received, and the terminal device does not correspond to
  • the HARQ-ACK information received on the SPS PDSCH is multiplexed on the first PUSCH, and the terminal device does not multiplex the
  • S320 may include:
  • the terminal device is configured for CBG transmission (for example, the terminal device is provided with the high-level parameter PDSCH-CodeBlockGroupTransmission), and the terminal device receives the first PUSCH transmission scheduled in the first DCI format including the first DAI information and the second DAI information, and the The first DAI information is a preset value or the second DAI information is a preset value, and the terminal device does not receive the corresponding DCI format 1_0 or DCI format 1_1 scheduling in the PDCCH detection opportunity corresponding to the HARQ feedback window
  • the PDCCH received by the PDSCH of the HARQ process corresponding to the enabled state and the disabled state, or the PDCCH that indicates the release of the SPS PDSCH on any serving cell is not received, or the PDCCH that indicates the DCI format 1_1 of the SCell dormancy is not received, and
  • the terminal device does not multiplex the HARQ-ACK information received corresponding to the SPS PDSCH on the first PUSCH, then the terminal device does not multiplex
  • the terminal device when a terminal device is configured with a certain or some HARQ processes corresponding to a non-enabled state, if the PUSCH resources and PUCCH resources of the terminal device overlap in the time domain, the terminal device can Schedule the value of the DAI field in the DCI of the PUSCH resource and/or the reception of the physical downlink channel to determine whether the HARQ-ACK information needs to be multiplexed and transmitted on the PUSCH or the HARQ-ACK multiplexed and transmitted on the PUSCH. size of the message.
  • the number of downlink transmissions indicated by the DAI field may not include the number of PDSCHs that are transmitted using the HARQ process in the disabled state, thereby reducing the overhead for transmitting uplink control information on the PUSCH.
  • FIG. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application.
  • the terminal device 400 includes:
  • the processing unit 410 is configured to determine to transmit a first physical uplink shared channel PUSCH, wherein the first PUSCH is associated with a first physical downlink channel; and according to the reception of the first physical downlink channel, determine whether to The first hybrid automatic request retransmission response HARQ-ACK information is multiplexed and transmitted on the PUSCH, wherein the first HARQ-ACK information corresponds to the reception condition of the first physical downlink channel.
  • the first physical downlink channel includes at least one of the following:
  • the first HARQ process includes a HARQ process corresponding to the first state
  • the first physical downlink channel does not include PDSCH transmission associated with a PDCCH and a second HARQ process, wherein the second HARQ process includes a HARQ process corresponding to the second state.
  • the first physical downlink channel includes at least one of the following situations:
  • the first HARQ process includes a HARQ process corresponding to the first state
  • the second HARQ process the process includes a HARQ process corresponding to the second state
  • the first PUSCH is associated with a first physical downlink channel, including:
  • the first PUSCH resource corresponding to the first PUSCH and the uplink HARQ-ACK feedback resource corresponding to the first physical downlink channel at least partially overlap in the time domain.
  • the first physical downlink channel corresponds to a transport block TB-based HARQ-ACK feedback manner.
  • the first PUSCH is associated with a second physical downlink channel
  • the processing unit 410 is further configured to: determine whether the first PUSCH is in the first physical downlink channel according to the reception situation of the second physical downlink channel
  • the second HARQ-ACK information is multiplexed and transmitted on the PUSCH, wherein the second HARQ-ACK information corresponds to the reception condition of the second physical downlink channel.
  • the second physical downlink channel includes: PDSCH transmission associated with a PDCCH and a third HARQ process, wherein the third HARQ process includes a HARQ process corresponding to the first state.
  • the second physical downlink channel does not include PDSCH transmission associated with a PDCCH and a fourth HARQ process, wherein the fourth HARQ process includes a HARQ process corresponding to the second state.
  • the second physical downlink channel includes: PDSCH transmission associated with the PDCCH and the third HARQ process and PDSCH transmission associated with the PDCCH and the fourth HARQ process, wherein the first The third HARQ process includes a HARQ process corresponding to the first state, and the fourth HARQ process includes a HARQ process corresponding to the second state.
  • the first PUSCH is associated with a second physical downlink channel, including:
  • the first PUSCH resource corresponding to the first PUSCH and the uplink HARQ-ACK feedback resource corresponding to the second physical downlink channel at least partially overlap in the time domain.
  • the second physical downlink channel corresponds to a HARQ-ACK feedback manner based on a code block group CBG.
  • the terminal device 400 further includes:
  • a communication unit 420 configured to receive first downlink control information DCI sent by a network device, where the first DCI is used to schedule the first PUSCH transmission, wherein the first DCI includes a first downlink allocation indication DAI information, the first DAI information is used to indicate the number of the first physical downlink channels associated with the first PUSCH;
  • the processing unit 410 is further configured to: determine whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH according to the first DAI information and the reception situation of the first physical downlink channel.
  • the DCI format corresponding to the first DCI includes at least one of the following: DCI format 0_1 and DCI format 0_2.
  • the processing unit 410 is further configured to:
  • the terminal device When the number of the first physical downlink channels received by the terminal device is greater than or equal to 1, or the terminal device needs to multiplex and transmit HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH , the terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH according to the first DAI information.
  • the processing unit 410 is further configured to: when the terminal device does not receive the first physical downlink channel, and the terminal device does not need to replay on the first PUSCH When the HARQ-ACK information corresponding to the SPS PDSCH is transmitted, and the first DAI information indicates a preset value, the first HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.
  • the first PUSCH is further associated with a second physical downlink channel
  • the first DCI further includes second DAI information
  • the second DAI information is used to indicate that the first PUSCH is related to the first physical downlink channel.
  • the number of the second physical downlink channels associated with the PUSCH, the processing unit 410 is further configured to:
  • the processing unit 410 is further configured to: in the case that the number of the second physical downlink channels received by the terminal device is greater than or equal to 1, according to the second DAI information, the second HARQ-ACK information is multiplexed and transmitted on the first PUSCH.
  • the processing unit 410 is further configured to: when the terminal device does not receive the second physical downlink channel, and the second DAI information indicates the preset value Next, the second HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.
  • the preset value is 0 or 4.
  • the processing unit 410 is further configured to:
  • the DCI format corresponding to the second DCI includes DCI format 0_0.
  • the processing unit 410 is further configured to:
  • the terminal device When the number of the first physical downlink channels received by the terminal device is greater than or equal to 1, or the terminal device needs to multiplex and transmit HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH , multiplexing and transmitting the first HARQ-ACK information on the first PUSCH.
  • the processing unit 410 is further configured to:
  • the terminal device does not receive the first physical downlink channel, and the terminal device does not need to multiplex and transmit the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, the first The first HARQ-ACK information is not multiplexed and transmitted on the PUSCH.
  • the processing unit 410 is further configured to:
  • the second HARQ-ACK information is multiplexed and transmitted on the first PUSCH.
  • the processing unit 410 is further configured to:
  • the second HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.
  • the HARQ process corresponding to the first state includes at least one of the following situations:
  • the HARQ process corresponds to an enabled state
  • the HARQ process is not configured with a disable parameter
  • the HARQ process corresponds to uplink HARQ-ACK feedback.
  • the HARQ process corresponding to the second state includes at least one of the following situations:
  • the HARQ process corresponds to a disabled state
  • the HARQ process is configured with a disable parameter.
  • the processing unit 410 is further configured to:
  • the first indication information is used to indicate whether the HARQ process corresponding to the second state is Perform uplink HARQ-ACK feedback.
  • the processing unit 410 is further configured to:
  • the first indication information sent by the network device it is determined that the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback, where the first indication information is used to indicate the HARQ process corresponding to the second state Whether the process performs uplink HARQ-ACK feedback.
  • the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
  • the aforementioned processing unit may be one or more processors.
  • terminal device 400 may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of the various units in the terminal device 400 are respectively for realizing the method shown in FIG. 2 .
  • the corresponding process of the terminal device in 300 is not repeated here for brevity.
  • FIG. 5 is a schematic block diagram of a network device according to an embodiment of the present application.
  • the network device 500 of FIG. 5 includes:
  • the communication unit 510 is configured to send the first downlink control information DCI to the terminal device, where the first DCI is used to schedule the first physical uplink shared channel PUSCH transmission, and the first DCI includes the first downlink allocation indication DAI information , the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH.
  • the first physical downlink channel includes at least one of the following:
  • the first HARQ process includes a HARQ process corresponding to the first state
  • the first physical downlink channel does not include PDSCH transmission associated with a PDCCH and a second HARQ process, wherein the second HARQ process includes a HARQ process corresponding to the second state.
  • the first physical downlink channel includes at least one of the following situations:
  • the first HARQ process includes a HARQ process corresponding to the first state
  • the second HARQ process the process includes a HARQ process corresponding to the second state
  • the first DCI further includes second DAI information, where the second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH.
  • the second physical downlink channel includes: PDSCH transmission associated with a PDCCH and a third HARQ process, wherein the third HARQ process includes a HARQ process corresponding to the first state.
  • the second physical downlink channel does not include PDSCH transmission associated with a PDCCH and a fourth HARQ process, wherein the fourth HARQ process includes a HARQ process corresponding to the second state.
  • the second physical downlink channel includes: PDSCH transmission associated with the PDCCH and the third HARQ process and PDSCH transmission associated with the PDCCH and the fourth HARQ process, wherein the first The third HARQ process includes a HARQ process corresponding to the first state, and the fourth HARQ process includes a HARQ process corresponding to the second state.
  • the terminal device is configured to feed back two HARQ-ACK subcodebooks; or,
  • the terminal device is configured for code block group CBG transmission; or,
  • the end device is configured with CBG feedback.
  • the HARQ process corresponding to the first state includes at least one of the following situations:
  • the HARQ process corresponds to an enabled state
  • the HARQ process is not configured with a disable parameter
  • the HARQ process corresponds to uplink HARQ-ACK feedback.
  • the HARQ process corresponding to the second state includes at least one of the following situations:
  • the HARQ process corresponds to a disabled state
  • the HARQ process is configured with a disable parameter.
  • the communication unit 510 is further configured to:
  • the communication unit 510 is further configured to:
  • the second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH, wherein the first PUSCH resource corresponding to the first PUSCH and The uplink HARQ-ACK feedback resources corresponding to the second physical downlink channel at least partially overlap in the time domain.
  • the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH, where the first PUSCH corresponding to the first PUSCH The resource and the uplink HARQ-ACK feedback resource corresponding to the first physical downlink channel at least partially overlap in the time domain.
  • the DCI format corresponding to the first DCI includes at least one of the following: DCI format 0_1 and DCI format 0_2.
  • the network device 500 further includes:
  • a processing unit configured to determine the value of the first DAI information and/or the value of the second DAI information according to the conditions of the scheduled first physical downlink channel and/or the second physical downlink channel.
  • the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
  • the aforementioned processing unit may be one or more processors.
  • the network device 500 may correspond to the network device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the network device 500 are for realizing the method shown in FIG. 3 respectively.
  • the corresponding process of the network device in 300 is not repeated here for brevity.
  • FIG. 6 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application.
  • the communication device 600 shown in FIG. 6 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the communication device 600 may further include a memory 620 .
  • the processor 610 may call and run a computer program from the memory 620 to implement the methods in the embodiments of the present application.
  • the memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive other devices Information or data sent by a device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of the antennas may be one or more.
  • the communication device 600 may specifically be the network device in this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • the communication device 600 may specifically be the mobile terminal/terminal device of the embodiments of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, for the sake of brevity. , and will not be repeated here.
  • FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 700 shown in FIG. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in this embodiment of the present application.
  • the chip 700 may further include a memory 720 .
  • the processor 710 may call and run a computer program from the memory 720 to implement the methods in the embodiments of the present application.
  • the memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .
  • the chip 700 may further include an input interface 730 .
  • the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740 .
  • the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • FIG. 8 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 8 , the communication system 900 includes a terminal device 910 and a network device 920 .
  • the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application.
  • the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.
  • Embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.
  • the embodiments of the present application also provide a computer program.
  • the computer program can be applied to the network device in the embodiments of the present application.
  • the computer program When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.
  • the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application.
  • the corresponding process for the sake of brevity, will not be repeated here.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种无线通信的方法、终端设备和网络设备，该方法包括：终端设备确定传输第一物理上行共享信道PUSCH，其中，所述第一PUSCH关联第一物理下行信道；所述终端设备根据所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第一混合自动请求重传应答HARQ-ACK信息，其中，所述第一HARQ-ACK信息对应所述第一物理下行信道的接收情况。

Description

无线通信的方法、终端设备和网络设备 技术领域
本申请实施例涉及通信领域，具体涉及一种无线通信的方法、终端设备和网络设备。
背景技术
在非地面通信网络(Non-Terrestrial Networks，NTN)系统中，对于终端设备的下行数据传输，网络设备可以为该终端设备指示去使能某个或某些下行混合自动请求重传(Hybrid Automatic Repeat reQuest，HARQ)进程的混合自动请求重传-应答(Hybrid Automatic Repeat request Acknowledgement，HARQ-ACK)反馈。在这种情况下，在终端设备被配置Type-1或Type-2或eType-2 HARQ-ACK码本反馈的情况下，当终端设备本应在第一物理上行控制信道(Physical Uplink Control Channel，PUCCH)资源上传输下行数据传输对应的HARQ-ACK信息时，如果该第一PUCCH资源和该终端设备的第一物理上行共享信道(Physical Uplink Shared Channel，PUSCH)资源在时域上至少部分重叠，如何确定是否将下行数据传输对应的HARQ-ACK信息复用在该第一PUSCH资源上或包括的HARQ-ACK信息的大小是一项急需解决的问题。
发明内容
本申请实施例提供一种无线通信的方法、终端设备和网络设备，有利于根据在网络设备调度PUSCH传输，并且该PUSCH关联物理下行信道的情况下，根据与该PUSCH关联的物理下行信道的接收情况，进行PUSCH资源的复用，有利于提升系统性能。
第一方面，提供了一种无线通信的方法，包括：终端设备确定传输第一物理上行共享信道PUSCH，其中，所述第一PUSCH关联第一物理下行信道；所述终端设备根据所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第一混合自动请求重传应答HARQ-ACK信息，其中，所述第一HARQ-ACK信息对应所述第一物理下行信道的接收情况。
第二方面，提供了一种无线通信的方法，包括：网络设备向终端设备发送第一下行控制信息DCI，所述第一DCI用于调度第一物理上行共享信道PUSCH传输，所述第一DCI中包括第一下行分配指示DAI信息，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数。
第三方面，提供了一种终端设备，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该终端设备包括用于执行上述第一方面或第一方面的任一可能的实现方式中的方法的单元。
第四方面，提供了一种网络设备，用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第二方面或第二方面的任一可能的实现方式中的方法的单元。
第五方面，提供了一种终端设备，该终端设备包括：包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面或其各实现方式中的方法。
第六方面，提供了一种网络设备，该网络设备包括：包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第二方面或其各实现方式中的方法。
第七方面，提供了一种芯片，用于实现上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行如上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第八方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第九方面，提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第十方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
基于上述技术方案，网络设备可以调度终端设备传输第一PUSCH，在第一PUSCH关联第一物理下行信道时，终端设备可以根据该第一物理下行信道的接收情况确定第一物理下行信道对应的第一HARQ-ACK信息在第一PUSCH上的复用方式，有利于提升系统性能。
附图说明
图1A-图1C是本申请实施例提供的一种应用场景的示意性图。
图2是HARQ进程数和RTT之间的一种关系的示意性图。
图3是本申请实施例提供的一种无线通信的方法的示意性图。
图4是本申请实施例提供的一种终端设备的示意性框图。
图5是本申请实施例提供的一种网络设备的示意性框图。
图6是本申请另一实施例提供的一种通信设备的示意性框图。
图7是本申请实施例提供的一种芯片的示意性框图。
图8是本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。针对本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、非地面通信网络(Non-Terrestrial Networks，NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、第五代通信(5th-Generation，5G)系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信，或车联网(Vehicle to everything，V2X)通信等，本申请实施例也可以应用于这些通信系统。
可选地，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
可选地，本申请实施例中的通信系统可以应用于非授权频谱，其中，非授权频谱也可以认为是共享频谱；或者，本申请实施例中的通信系统也可以应用于授权频谱，其中，授权频谱也可以认为是非共享频谱。
可选地，本申请实施例可应用于非地面通信网络(Non-Terrestrial Networks，NTN)系统，也可应用于地面通信网络(Terrestrial Networks，TN)系统。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中，终端设备也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是WLAN中的站点(STATION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字助理(Personal Digital Assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信系统例如NR网络中的终端设备，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。
在本申请实施例中，终端设备可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中，终端设备可以是手机(Mobile Phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。本申请实施例所涉及的终端设备还可以称为终端、用户设备(user  equipment，UE)、接入终端设备、车载终端、工业控制终端、UE单元、UE站、移动站、移动台、远方站、远程终端设备、移动设备、UE终端设备、无线通信设备、UE代理或UE装置等。终端设备也可以是固定的或者移动的。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中，网络设备可以是用于与移动设备通信的设备，网络设备可以是WLAN中的接入点(Access Point，AP)，GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及NR网络中的网络设备(gNB)或者未来演进的PLMN网络中的网络设备或者NTN网络中的网络设备等。
作为示例而非限定，在本申请实施例中，网络设备可以具有移动特性，例如网络设备可以为移动的设备。可选地，网络设备可以为卫星、气球站。例如，卫星可以为低地球轨道(low earth orbit，LEO)卫星、中地球轨道(medium earth orbit，MEO)卫星、地球同步轨道(geostationary earth orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等。可选地，网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中，网络设备可以为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
示例性的，图1A为本申请实施例提供的一种通信系统的架构示意图。如图1A所示，通信系统100可以包括网络设备110，网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。
图1A示例性地示出了一个网络设备和两个终端设备，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
示例性的，图1B为本申请实施例提供的另一种通信系统的架构示意图。请参见图1B，包括终端设备1101和卫星1102，终端设备1101和卫星1102之间可以进行无线通信。终端设备1101和卫星1102之间所形成的网络还可以称为NTN。在图1B所示的通信系统的架构中，卫星1102可以具有基站的功能，终端设备1101和卫星1102之间可以直接通信。在系统架构下，可以将卫星1102称为网络设备。可选地，通信系统中可以包括多个网络设备1102，并且每个网络设备1102的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
示例性的，图1C为本申请实施例提供的另一种通信系统的架构示意图。请参见图1C，包括终端设备1201、卫星1202和基站1203，终端设备1201和卫星1202之间可以进行无线通信，卫星1202与基站1203之间可以通信。终端设备1201、卫星1202和基站1203之间所形成的网络还可以称为NTN。在图1C所示的通信系统的架构中，卫星1202可以不具有基站的功能，终端设备1201和基站1203之间的通信需要通过卫星1202的中转。在该种系统架构下，可以将基站1203称为网络设备。可选地，通信系统中可以包括多个网络设备1203，并且每个网络设备1203的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
需要说明的是，图1A-图1C只是以示例的形式示意本申请所适用的系统，当然，本申请实施例所示的方法还可以适用于其它系统，例如，5G通信系统、LTE通信系统等，本申请实施例对此不作具体限定。
可选地，图1A-图1C所示的无线通信系统还可以包括移动性管理实体(Mobility Management Entity，MME)、接入与移动性管理功能(Access and Mobility Management Function，AMF)等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1A示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端设备120，网络设备110和终端 设备120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
本申请实施例中，"预定义"可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。比如预定义可以是指协议中定义的。
本申请实施例中，所述"协议"可以指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
可选地，在本申请实施例中的指示信息包括物理层信令例如下行控制信息(Downlink Control Information，DCI)、无线资源控制(Radio Resource Control，RRC)信令和媒体接入控制单元(Media Access Control Control Element，MAC CE)中的至少一种。
可选地，在本申请实施例中的高层参数或高层信令包括无线资源控制(Radio Resource Control，RRC)信令和媒体接入控制单元(Media Access Control Control Element，MAC CE)中的至少一种。
为便于更好的理解本申请实施例，首先对本申请相关的HARQ机制和HARQ-ACK反馈机制进行说明。
NR系统中的HARQ机制
NR系统中有两级重传机制：媒体接入控制(Media Access Control，MAC)层的混合自动请求重传(Hybrid Automatic Repeat reQuest，HARQ)机制和无线链路控制协议(Radio Link Control，RLC)层的自动请求重传(Automatic Repeat reQuest，ARQ)机制。丢失或出错的数据的重传主要是由MAC层的HARQ机制处理的，并由RLC层的重传功能进行补充。MAC层的HARQ机制能够提供快速重传，RLC层的ARQ机制能够提供可靠的数据传输。
HARQ使用停等协议(Stop-and-Wait Protocol)来发送数据。在停等协议中，发送端发送一次传输块(Transport Block，TB)后，就停下来等待确认信息。这样，每次传输后发送端就停下来等待确认，会导致用户吞吐量很低。因此，NR使用多个并行的HARQ进程，当一个HARQ进程在等待确认信息时，发送端可以使用另一个HARQ进程来继续发送数据。这些HARQ进程共同组成了一个HARQ实体，这个实体结合了停等协议，允许数据连续传输。HARQ有上行HARQ和下行HARQ之分。上行HARQ针对上行数据传输，下行HARQ针对下行数据传输。两者相互独立。
在一些情况中，终端设备对应每个服务小区都有各自的HARQ实体。每个HARQ实体维护一组并行的下行HARQ进程和一组并行的上行HARQ进程。作为一个示例，每个上下行载波均支持最大16个HARQ进程。网络设备可以根据网络设备部署情况通过无线资源控制(Radio Resource Control，RRC)信令半静态配置向终端设备指示最大的HARQ进程数。可选地，在一些实施例中，如果网络设备没有提供相应的配置参数，则下行缺省的HARQ进程数为8，上行每个载波支持的最大HARQ进程数始终为16。每个HARQ进程对应一个HARQ进程ID。对于下行，广播控制信道(Broadcast Control CHannel，BCCH)使用一个专用的广播HARQ进程。对于上行，随机过程中的消息3(Msg3)传输使用HARQ ID 0。
在一些实施例中，对于不支持下行空分复用的终端设备，每个下行HARQ进程只能同时处理1个TB；对于支持下行空分复用的终端设备，每个下行HARQ进程可以同时处理1个或者2个TB。终端设备的每个上行HARQ进程同时处理1个TB。
HARQ在时域上分为同步和异步两类，在频域上分为非自适应和自适应两类。NR上下行均使用异步自适应HARQ机制。对于异步HARQ，同一个TB的重传与上一次传输的时间间隔是不固定的。自适应HARQ即可以改变重传所使用的频域资源和MCS。
结合图2，以下行传输为例，对支持的HARQ进程数和RTT之间的关系进行说明。如图2所示，终端设备被配置的最大HARQ进程数为16，那么在RTT较小，例如小于16ms的情况下，不影响该终端设备的最大吞吐量，或者说，如果RTT小于16ms，在有业务要传输时，该终端设备总是可以有 并行的HARQ进程来进行数据传输。当然，如果RTT较大，例如远大于16ms，那么可能存在终端设备的所有HARQ进程都被用于数据传输，且并未获得网络设备的反馈，从而导致终端设备有业务待传输却没有HARQ进程可以被使用的情况，进而会影响终端设备侧数据传输的吞吐量。
NR系统中的HARQ-ACK反馈
对于有下行业务的终端设备，网络设备可以通过下行控制信息(Downlink Control Information，DCI)为终端设备调度物理下行共享信道(Physical Downlink Shared Channel，PDSCH)的传输。其中，该DCI中包括物理上行控制信道(Physical Uplink Control Channel，PUCCH)资源的指示信息，终端设备在收到PDSCH后，将该PDSCH的译码结果(肯定确认(Acknowledge，ACK)信息或否定确认(Negative Acknowledge，NACK)信息)通过该PUCCH资源反馈给网络设备。其中，在NR系统中支持动态确定HARQ反馈时序。网络设备通过DCI调度终端设备进行PDSCH接收，其中，该DCI中包括用于传输该PDSCH对应的HARQ-ACK的上行反馈资源例如PUCCH资源的指示信息。
作为示例，该指示信息可以包括：
PUCCH资源指示(PUCCH resource indicator)：用于确定PUCCH资源；
HARQ反馈时序指示信息(例如PDSCH-to-HARQ_feedback timing indicator)：用于动态确定上行反馈资源的时域位置例如用于HARQ反馈的PUCCH资源的时隙，通常用K1表示。
其中，该HARQ反馈时序指示信息用于指示HARQ反馈时序集合中的取值。HARQ反馈时序集合可以是预设的或网络设备配置的。作为示例，HARQ反馈时序指示信息包括3比特，该HARQ反馈时序指示信息为000时，指示HARQ反馈时序集合中的第一个值，该HARQ反馈时序指示信息为001时，指示HARQ反馈时序集合中的第二个值，等等。
终端设备在进行HARQ-ACK反馈时包括半静态码本反馈例如类型1(Type-1)HARQ-ACK码本反馈和动态码本反馈例如类型2(Type-2)或增强的类型2(eType-2)HARQ-ACK码本反馈。
如果终端设备被配置了Type-1 HARQ-ACK码本反馈，Type-1 HARQ-ACK码本中包括一个HARQ-ACK反馈窗口内的候选PDSCH传输机会对应的HARQ-ACK信息。
如果终端设备被配置了Type-2 HARQ-ACK码本反馈，Type-2 HARQ-ACK码本中包括一个HARQ-ACK反馈窗口内的被调度的PDSCH对应的HARQ-ACK信息。其中，调度PDSCH的DCI格式中包括下行分配指示(Downlink assignment index，DAI)信息域：
DAI计数(counter DAI，C-DAI)信息，该C-DAI信息用于确定当前DCI调度的下行传输是HARQ反馈窗口内的第几个下行传输，其中，C-DAI信息的排序方式是根据PDCCH的检测机会顺序排序的。
如果是载波聚合的场景，那么DCI中还可以包括：
DAI总数(total DAI，T-DAI)信息，该T-DAI信息用于确定HARQ反馈窗口内截止到当前DCI调度为止一共包括多少个下行传输。
如果终端设备被配置了eType-2 HARQ-ACK码本反馈，eType-2 HARQ-ACK码本中包括一个HARQ-ACK反馈窗口内的被调度的分组的PDSCH对应的HARQ-ACK信息。基站可以对调度的PDSCH进行分组，并通过调度PDSCH的DCI显示信令指示该PDSCH的分组信息，以使UE在接收到该PDSCH后根据不同的分组进行对应的HARQ-ACK反馈。或者说，基站调度UE进行PDSCH接收的DCI中包括组标号(PDSCH group index)的指示信息和新反馈指示NFI(New feedback indicator)的指示信息。该方式下最多可以包括2个组，基站在触发UE进行HARQ-ACK反馈时可以触发一个组的反馈，也可以同时触发两个组的反馈。具体地，DCI信息中可以包括反馈请求组个数的信息域(Number of requested PDSCH group(s))。如果终端设备接收到网络设备发送的DCI信息，并且该DCI信息中的反馈请求组个数信息域为预设值例如设置为1，那么终端设备需要进行两个组的HARQ-ACK反馈。或者，如果终端设备接收到网络设备发送的DCI信息，并且该DCI信息中的反馈请求组个数信息域为预设值例如设置为0，那么终端设备需要进行当前调度组(即DCI调度的PDSCH所属的组)的HARQ-ACK反馈。
其中，HARQ反馈窗口可以根据HARQ反馈时序集合或HARQ反馈时序指示信息确定。随着标准的演进，HARQ反馈时序指示信息除了可以指示有效值，还可以指示无效值。当HARQ反馈时序指示信息指示无效值时，可以表示该用于反馈HARQ-ACK信息的上行反馈资源的时域位置暂时不确定。
终端设备根据上述信息可以确定下行传输对应的HARQ-ACK反馈码本、用于反馈HARQ-ACK信息的PUCCH资源和反馈HARQ-ACK信息的时隙等信息。
在NTN系统中，由于终端设备和卫星(或者说网络设备)之间的通信距离很远，信号传输的RTT很大。在GEO系统中，信号传输的RTT可以为百毫秒量级，例如信号传输的RTT最大可以为约600ms。在LEO系统中，信号传输的RTT可以为几十毫秒量级。由于NTN系统的RTT远大于地面通信系统 的RTT，因此，NR系统中的HARQ机制不再适用于NTN系统。
作为一种实现方式，网络设备可以为终端设备的某个或某些下行HARQ进程配置去使能。对于被配置去使能的下行HARQ进程，网络设备不需要接收到终端设备为该HARQ进程中传输的TB反馈的HARQ-ACK信息，即可重用该HARQ进程进行数据传输。因此，网络设备可以使用去使能的HARQ进程为终端设备进行多个数据包的调度，从而可以减少RTT带来的影响。
在NTN系统中，对于终端设备的下行数据传输，网络设备可以为该终端设备指示去使能某个或某些下行HARQ进程的HARQ-ACK反馈。在这种情况下，在终端设备被配置Type-1或Type-2或eType-2 HARQ-ACK码本反馈的情况下，当终端设备本应在第一PUCCH资源上传输下行数据传输对应的HARQ-ACK信息时，如果该第一PUCCH资源和该终端设备的第一PUSCH资源在时域上至少部分重叠，如何确定是否将下行数据传输对应的HARQ-ACK信息复用在该第一PUSCH上或如何确定该第一PUSCH上复用的HARQ-ACK信息包括的比特数是一项急需解决的问题。
图3为本申请实施例提供的一种无线通信的方法300的示意性交互图。如图3所示，该方法300可以包括如下至少部分内容：
S310，网络设备向终端设备调度第一PUSCH传输，第一物理下行信道与所述第一PUSCH关联；
S320，所述终端设备根据所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第一混合自动请求重传应答HARQ-ACK信息，其中，所述第一HARQ-ACK信息对应所述第一物理下行信道的接收情况。
可选地，在一些实施例中，记为实施例一，所述第一PUSCH传输可以是第一DCI调度的，S310可以包括：
所述网络设备向所述终端设备发送第一DCI，所述第一DCI用于调度第一PUSCH传输，所述第一DCI中包括第一下行分配指示DAI信息，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数；
对应地，终端设备接收该第一DCI。
进一步可选地，S320可以替换为：所述终端设备根据所述第一DAI信息和/或所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第一混合自动请求重传应答HARQ-ACK信息，其中，所述第一HARQ-ACK信息对应所述第一物理下行信道的接收情况。
可选地，在一些实施例中，所述第一DCI对应的DCI格式包括以下至少一种：DCI格式0_1和DCI格式0_2，或者也可以为其他包括DAI信息的DCI格式。
可选地，在一些实施例中，记为实施例二，S310可以包括：
网络设备向终端设备发送调度信息，所述调度信息用于确定传输所述第一PUSCH。
可选地，所述调度信息不包括DCI，或所述调度信息包括第二DCI且所述第二DCI中不包括DAI信息。
即在该实施例二中，第一PUSCH可以不是DCI调度的例如第一PUSCH对应的资源位置是半静态配置的，或者可以是由不包括DAI信息的DCI调度的。
综合实施例一和实施例二，第一PUSCH可以是由包括DAI信息的DCI调度的，或者是由不包括DAI信息的DCI调度，或者也可以不是由DCI调度的。
可选地，在一些实施例中，所述第二DCI对应的DCI格式包括DCI格式0_0，或者也可以为其他不包括DAI信息的DCI格式。
可选地，在一些实施例中，记为实施例三，S310可以包括：
网络设备向终端设备发送第一DCI，所述第一DCI用于调度第一PUSCH传输，所述第一DCI中包括第一DAI信息，所述第一DAI信息用于指示是否在所述第一PUSCH上复用传输第一HARQ-ACK信息，第一物理下行信道与所述第一PUSCH关联；
对应地，终端设备接收该第一DCI。
进一步地，S320可以替换为：所述终端设备根据所述第一DAI信息和所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输所述第一HARQ-ACK信息，其中，所述第一HARQ-ACK信息对应所述第一物理下行信道的接收情况。
或者，S320可以替换为：所述终端设备根据所述第一DAI信息，确定是否在所述第一PUSCH上复用传输所述第一HARQ-ACK信息，其中，所述第一HARQ-ACK信息对应所述第一物理下行信道的接收情况。
可选地，在该实施例三中，所述终端设备被配置了Type-1 HARQ-ACK码本反馈；或者，所述第一DAI信息包括1比特。
可选地，在该实施例三中，所述第一DCI对应的DCI格式包括以下至少一种：DCI格式0_1和 DCI格式0_2，或者也可以为其他包括DAI信息的DCI格式。
在上述实施例二和实施例三中的第一PUSCH的调度方式中，可以认为第一物理下行信道的个数和第一DAI不关联，即第一物理下行信道的个数和第一DAI不关联可以包括：
第一PUSCH不是DCI调度的或调度第一PUSCH的DCI中不包括DAI信息；
所述第一PUSCH关联的第一DAI信息包括1比特，且该第一DAI信息不用于指示第一物理下行信道的个数。
应理解，本申请实施例并不具体限定所述第一PUSCH的调度方式，例如，在又一些实施例中，S310可以包括：网络设备向终端设备发送预配置授权(Configured Grant，CG)信息，所述预配置授权信息用于调度第一PUSCH传输，其中，所述第一PUSCH为预配置授权PUSCH。可选地，所述预配置授权信息可以为预配置授权配置信息或预配置授权激活信息。
当第一PUSCH传输基于任一情况被调度，并且第一PUSCH关联物理下行信道时，都可以根据本申请实施例中所述的方式确定所述第一PUSCH关联的物理下行信道对应的HARQ-ACK是否复用在该第一PUSCH上，和/或确定在所述第一PUSCH上复用的该物理下行信道对应的HARQ-ACK包括的比特数。以下，具体说明所述第一物理下行信道的具体实现以及所述第一物理下行信道对应的HARQ-ACK信息的复用方式，应理解，除非特别说明，以下所描述的特征适用于第一PUSCH的任一调度方式，例如实施例一至实施例三中的调度方式。
可选地，在一些实施例中，与所述第一PUSCH关联的第一物理下行信道可以指：所述第一PUSCH对应的第一PUSCH资源和第一物理下行信道对应的上行HARQ-ACK反馈资源在时域上至少部分重叠。可选地，所述第一物理下行信道的上行HARQ-ACK反馈资源例如可以为第一PUCCH资源。
以下，结合具体实施例，说明本申请实施例中所述第一DAI信息的具体含义，和/或，所述第一物理下行信道的具体实现，和/或，终端设备是否在第一PUSCH上复用传输第一HARQ-ACK信息的方法，和/或，终端设备如何确定在第一PUSCH上复用传输的第一HARQ-ACK信息大小的方法。
实现方式一：
所述第一物理下行信道包括以下中的至少一种：
关联物理下行控制信道(Physical Downlink Control Channel，PDCCH)和第一混合自动请求重传HARQ进程的物理下行共享信道PDSCH，其中，所述第一HARQ进程包括对应第一状态的HARQ进程；
指示半持续调度(Semi-Persistent Scheduling，SPS)PDSCH释放的PDCCH；
指示辅小区休眠(SCell dormancy)状态的PDCCH；
其他对应HARQ-ACK信息的PDCCH，或者说，关联HARQ-ACK信息的PDCCH。
即所述第一物理下行信道可以包括满足特定条件的PDSCH，记为第一类PDSCH，该第一类PDSCH关联PDCCH并且是通过对应第一状态的HARQ进程传输的。
可选地，第一HARQ进程包括至少一个HARQ进程。
可选地，关联PDCCH的PDSCH可以包括以下中的至少一种：
PDCCH调度的PDSCH；
用于激活SPS PDSCH传输的PDCCH调度的SPS PDSCH。
可选地，所述第一物理下行信道不包括关联PDCCH和第二HARQ进程的PDSCH传输，其中，所述第二HARQ进程包括对应第二状态的HARQ进程。
可选地，第二HARQ进程包括至少一个HARQ进程。
可选地，所述第一物理下行信道可以包括第一类PDSCH、指示SPS PDSCH释放的PDCCH、指示辅小区休眠状态的PDCCH和其他对应HARQ-ACK信息的PDCCH中的至少一个，并且不包括第二类PDSCH，其中，该第二类PDSCH关联PDCCH并且是通过对应第二状态的HARQ进程传输的。
可选地，在本申请实施例中，所述对应第一状态的HARQ进程，包括以下情况中的至少一种：
所述HARQ进程对应使能态；
所述HARQ进程未被配置去使能参数；
所述HARQ进程对应上行HARQ-ACK反馈。
即可以认为该HARQ进程的状态是使能态，或通过该HARQ进程传输的PDSCH需要进行上行HARQ-ACK反馈。
可选地，在本申请实施例中，所述对应第二状态的HARQ进程，包括以下情况中的至少一种：
所述HARQ进程对应去使能态；
所述HARQ进程被配置去使能参数。
应理解，去使能(disabled)态或称为非使能态。可选地，所述去使能参数是网络设备通过RRC 信令、MAC CE和物理层信令例如DCI中的至少一种配置给终端设备的。
可选地，在实现方式一中，所述对应第二状态的HARQ进程不对应上行HARQ-ACK反馈，即不需要进行HARQ-ACK反馈。
可选地，在一些实施例中，网络设备可以配置对应第二状态的HARQ进程是否需要进行上行HARQ-ACK反馈。
例如，网络设备可以向终端设备发送第一指示信息，其中，所述第一指示信息用于指示对应所述第二状态的HARQ进程是否进行上行HARQ-ACK反馈。具体地，在实现方式一中，第一指示信息指示对应第二状态的HARQ进程不需要进行上行HARQ-ACK反馈，当终端设备收到对应第二状态的HARQ进程传输的PDSCH时，不需要向网络设备反馈该PDSCH对应的HARQ-ACK信息。
可选地，在一些实施例中，对应第二状态的HARQ进程是否需要进行上行HARQ-ACK反馈可以是预定义的。例如预定义对应所述第二状态的HARQ进程不需要进行上行HARQ-ACK反馈。
应理解，本申请实施例对于第一DAI信息的比特数不作具体限定。
在一些实施例中，所述第一DAI信息为1比特，2比特或其他的比特数等。
可选地，在一些实施例中，所述第一DAI信息用于指示是否在所述第一PUSCH上复用传输第一HARQ-ACK信息。例如，第一DAI信息包括1比特，当该1比特指示1时，用于指示在所述第一PUSCH上复用传输第一HARQ-ACK信息，当该1比特指示0时，用于指示在所述第一PUSCH上不复用传输第一HARQ-ACK信息。
可选地，在一些实施例中，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数，则当第一物理下行信道为实现方式一中的情况时，所述第一DAI信息指示的第一物理下行信道的个数中包括第一类PDSCH、指示SPS PDSCH释放的PDCCH、指示辅小区休眠状态的PDCCH和其他对应HARQ-ACK信息的PDCCH中的至少一个的个数。进一步可选地，所述第一DAI信息指示的第一物理下行信道的个数中不包括所述第二类PDSCH的个数。表1示出了实现方式一中当第一DAI信息包括2比特，第一物理下行信道包括第一类PDSCH、指示SPS PDSCH释放的PDCCH和指示辅小区休眠状态的PDCCH时，第一DAI信息取值的含义。其中，LSB表示低位比特(Least Significant Bit，LSB)，MSB表示高位比特(most significant bits，MSB)。
表1
Figure PCTCN2020117491-appb-000001
实现方式二：
所述第一物理下行信道包括以下情况中的至少一种：
关联PDCCH和所述第一HARQ进程的PDSCH传输以及关联PDCCH和所述第二HARQ进程的PDSCH传输，其中，所述第一HARQ进程包括对应所述第一状态的HARQ进程，所述第二HARQ进程包括对应所述第二状态的HARQ进程；
指示半持续调度SPS PDSCH释放的PDCCH；
指示辅小区休眠状态的PDCCH；
其他对应HARQ-ACK信息的PDCCH，或者说，关联HARQ-ACK信息的PDCCH。
即在该实现方式二中，和实现方式一不同，所述第一物理下行信道可以包括关联PDCCH和第二HARQ进程的PDSCH传输，其中，所述第二HARQ进程包括对应第二状态的HARQ进程。或者说，所述第一物理下行信道包括所述第二类PDSCH。
可选地，所述第一物理下行信道包括所述第一类PDSCH、所述第二类PDSCH、指示SPS PDSCH释放的PDCCH、指示辅小区休眠状态的PDCCH和其他对应HARQ-ACK信息的PDCCH中的至少一个。
可选地，在实现方式二中，所述对应第二状态的HARQ进程对应上行HARQ-ACK反馈。
可选地，在一些实施例中，网络设备可以配置对应第二状态的HARQ进程是否需要进行上行HARQ-ACK反馈。
例如，网络设备可以向终端设备发送第一指示信息，其中，所述第一指示信息用于指示对应所述 第二状态的HARQ进程是否进行上行HARQ-ACK反馈。具体地，在实现方式二中，第一指示信息指示对应第二状态的HARQ进程需要进行上行HARQ-ACK反馈，当终端设备收到对应第二状态的HARQ进程传输的PDSCH时，需要向网络设备反馈该PDSCH对应的HARQ-ACK信息。
可选地，在一些实施例中，对应第二状态的HARQ进程是否需要进行上行HARQ-ACK反馈可以是预定义的。例如预定义对应所述第二状态的HARQ进程需要进行上行HARQ-ACK反馈。
可选地，在一些实施例中，所述第一DAI信息用于指示是否在所述第一PUSCH上复用传输第一HARQ-ACK信息。例如，第一DAI信息包括1比特，当该比特指示1时，用于指示在所述第一PUSCH上复用传输第一HARQ-ACK信息，当该比特指示0时，用于指示在所述第一PUSCH上不复用传输第一HARQ-ACK信息。
可选地，在一些实施例中，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数，当第一物理下行信道为实现方式二中的情况时，所述第一DAI信息指示的第一物理下行信道的个数中包括第一类PDSCH、第二类PDSCH、指示SPS PDSCH释放的PDCCH、指示辅小区休眠状态的PDCCH和其他对应HARQ-ACK信息的PDCCH中的至少一个的个数。
表2示出了实现方式二中当第一DAI信息包括2比特，第一物理下行信道包括第一类PDSCH、第二类PDSCH、指示SPS PDSCH释放的PDCCH和指示辅小区休眠状态的PDCCH时，第一DAI信息的取值的含义。
表2
Figure PCTCN2020117491-appb-000002
可选地，在本申请一些实施例中，所述终端设备可以根据网络设备的第一指示信息确定所述第一DAI信息的含义，其中，所述第一指示信息用于指示对应所述第二状态的HARQ进程是否进行上行HARQ-ACK反馈。或者，所述终端设备可以根据网络设备的第一指示信息确定对应所述第二状态的HARQ进程是否进行上行HARQ-ACK反馈，其中，所述第一指示信息用于指示所述第一DAI信息的含义。
例如，若所述第一指示信息指示对应所述第二状态的HARQ进程不需要进行上行HARQ-ACK反馈，则第一DAI信息的含义可以为实现方式一中的情况。此情况下，所述终端设备可以不向网络设备反馈通过第二状态的HARQ进程传输的PDSCH对应的HARQ反馈信息。即只向网络设备反馈通过第一状态的HARQ进程传输的PDSCH对应的HARQ反馈信息。
又例如，若所述第一指示信息指示对应所述第二状态的HARQ进程需要进行上行HARQ-ACK反馈，则第一DAI信息的含义可以为实现方式二中的情况。此情况下，所述终端设备可以向网络设备反馈通过第二状态的HARQ进程传输的PDSCH对应的HARQ反馈信息。即向网络设备反馈通过第一状态和第二状态的HARQ进程传输的PDSCH对应的HARQ反馈信息。
以下，介绍基于前述的实现方式一和实现方式二，如何确定是否在所述第一PUSCH上复用传输第一物理下行信道对应的第一HARQ-ACK信息，或如何确定该第一PUSCH上复用的第一HARQ-ACK信息包括的比特数。
在本申请一些实施例中，所述终端设备可以根据所述第一DAI信息，所述第一物理下行信道的接收情况和反馈规则中的至少一项，确定是否在所述第一PUSCH上复用传输第一物理下行信道对应的第一HARQ-ACK信息。
可选地，所述反馈规则包括所述终端设备是否需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息。
可选地，所述反馈规则包括所述第一指示信息。
可选地，在一些实施例中，若所述终端设备收到的所述第一物理下行信道的个数大于或等于1，或所述终端设备需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，则所述终端设备在所述第一PUSCH上复用传输所述第一HARQ-ACK信息。
作为示例而非限定，第一物理下行信道包括第一类PDSCH、指示SPS PDSCH释放的PDCCH和指示辅小区休眠状态的PDCCH，若终端设备收到的与第一PUSCH关联的第一物理下行信道的总个数大于或等于1，或该终端设备需要在第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息， 则该终端设备在该第一PUSCH上复用传输第一HARQ-ACK信息。
作为示例而非限定，所述第一物理下行信道包括第一类PDSCH、第二类PDSCH、指示SPS PDSCH释放的PDCCH和指示辅小区休眠状态的PDCCH，若终端设备收到的与第一PUSCH关联的第一物理下行信道的总个数大于或等于1，或该终端设备需要在第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，则该终端设备在该第一PUSCH上复用传输第一HARQ-ACK信息。
可选地，在另一些实施例中，若所述终端设备没有收到所述第一物理下行信道，且所述终端设备不需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，且所述第一DAI信息指示预设值，则所述终端设备在所述第一PUSCH上不复用传输所述第一HARQ-ACK信息。可选地，此情况可以适用于前述实施例一中的第一PUSCH的调度方式。
可选地，所述预设值例如可以为4等，本申请对此不作限定。
作为示例而非限定，第一物理下行信道包括第一类PDSCH、指示SPS PDSCH释放的PDCCH和指示辅小区休眠状态的PDCCH，若终端设备收到的与第一PUSCH关联的第一物理下行信道的总个数为0(或者说，该终端设备没有收到任意一个第一物理下行信道)，且该终端设备不需要在第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，且第一DAI信息指示的取值为4，则该终端设备在该第一PUSCH上不复用传输第一HARQ-ACK信息。
作为示例而非限定，第一物理下行信道包括第一类PDSCH、第二类PDSCH、指示SPS PDSCH释放的PDCCH和指示辅小区休眠状态的PDCCH，若终端设备收到的与第一PUSCH关联的第一物理下行信道的总个数为0(或者说该终端设备没有收到任意一个第一物理下行信道)，且该终端设备不需要在第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，且第一DAI信息指示的取值为4，则该终端设备在该第一PUSCH上不复用传输第一HARQ-ACK信息。
可选地，在一些实施例中，若所述终端设备没有收到所述第一物理下行信道，且所述终端设备需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，则所述终端设备在所述第一PUSCH上复用传输所述第一HARQ-ACK信息，所述第一HARQ-ACK信息包括所述SPS PDSCH对应的HARQ-ACK信息。
可选地，在一些实施例中，若所述终端设备没有收到所述第一物理下行信道，且所述终端设备不需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，则所述终端设备在所述第一PUSCH上不复用传输所述第一HARQ-ACK信息。可选地，所述第一PUSCH不关联第一DAI信息。例如，第一PUSCH不是DCI调度的或调度第一PUSCH的DCI中不包括DAI信息。可选地，所述第一PUSCH关联的第一DAI信息不用于指示第一物理下行信道的个数例如第一DAI信息包括1比特。
作为示例而非限定，第一物理下行信道包括第一类PDSCH、指示SPS PDSCH释放的PDCCH和指示辅小区休眠状态的PDCCH，若终端设备收到的与第一PUSCH关联的第一物理下行信道的总个数为0(或者说该终端设备没有收到任意一个第一物理下行信道)，且该终端设备不需要在第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，则该终端设备在该第一PUSCH上不复用传输第一HARQ-ACK信息。
作为示例而非限定，第一物理下行信道包括第一类PDSCH、第二类PDSCH、指示SPS PDSCH释放的PDCCH和指示辅小区休眠状态的PDCCH，若终端设备收到的与第一PUSCH关联的第一物理下行信道的总个数为0(或者说该终端设备没有收到任意一个第一物理下行信道)，且该终端设备不需要在第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，则该终端设备在该第一PUSCH上不复用传输第一HARQ-ACK信息。
可选地，在一些实施例中，所述第一DAI信息用于指示是否在所述第一PUSCH上复用传输第一HARQ-ACK信息。若所述终端设备收到的与所述第一PUSCH关联的第一DAI信息指示一预设值例如1，则所述终端设备在所述第一PUSCH上复用传输第一HARQ-ACK信息，或者，若所述终端设备收到的与所述第一PUSCH关联的第一DAI信息指示另一预设值例如0，则所述终端设备不在所述第一PUSCH上复用传输第一HARQ-ACK信息，或者，若所述终端设备收到的与所述第一PUSCH关联的第一DAI信息指示另一预设值例如0，且所述终端设备仅收到一个第一物理下行信道，则所述终端设备在所述第一PUSCH上复用传输第一HARQ-ACK信息。可选地，所述第一PUSCH关联的第一DAI信息不用于指示第一物理下行信道的个数例如第一DAI信息包括1比特。可选地，该终端设备被配置Type-1码本反馈。
应理解，在本申请的一些实施例中，由于第一HARQ-ACK信息中包括反映第一物理下行信道的接收情况的HARQ-ACK信息，当终端设备没有收到第一物理下行信道，且该终端设备也不需要复用传输SPS PDSCH对应的HARQ-ACK信息时，该终端设备不需要在第一PUSCH复用第一HARQ-ACK 信息。
可选地，在一些实施例中，若所述第一指示信息指示对应所述第二状态例如去使能态的HARQ进程不需要进行上行HARQ-ACK反馈，所述终端设备不将对应所述第二状态的HARQ进程的PDSCH所对应的HARQ-ACK信息复用到第一PUSCH上，或者，第一HARQ-ACK信息不包括对应所述第二状态的HARQ进程的PDSCH所对应的HARQ-ACK信息。
需要说明的是，对于实现方式一中的情况，所述第一物理下行信道中不包括关联PDCCH和对应第二状态的HARQ进程的PDSCH。也就是说，如果终端设备只接收到关联PDCCH和对应第二状态的HARQ进程的PDSCH，也认为没有收到第一物理下行信道。
可选地，所述终端设备根据所述第一DAI信息和/或所述第一物理下行信道的接收情况确定所述第一HARQ-ACK信息包括的比特大小。
在一些实施例中，所述终端设备可以在确定需要在第一PUSCH复用第一HARQ-ACK信息时，根据所述第一DAI信息和/或所述第一物理下行信道的接收情况确定所述第一HARQ-ACK信息包括的比特大小。作为一个实现方式，该终端设备可以根据第一DAI信息确定该第一HARQ-ACK信息包括的比特大小，其中，第一DAI信息用于指示与第一PUSCH关联的第一物理下行信道的总个数。这里需要说明的是，由于SPS PDSCH不是PDCCH动态调度的，因此第一DAI信息指示的个数中不包括SPS PDSCH的个数。
在一些实施例中，第一PUSCH关联的第一DAI信息包括2比特，如表1所示，第一DAI信息Y的取值范围为1到4，并假设该终端设备收到的第一DAI信息指示的取值为Y，该终端设备根据该第一DAI信息和第一物理下行信道的接收情况确定该第一HARQ-ACK信息包括的比特大小，包括：当该终端设备收到的第一物理下行信道的总个数小于或等于Y，则需要反馈HARQ-ACK信息的第一物理下行信道的总个数X等于Y；当该终端设备收到的第一物理下行信道的总个数大于Y且小于或等于Y+4，则需要反馈HARQ-ACK信息的第一物理下行信道的总个数X等于Y+4；当该终端设备收到的第一物理下行信道的总个数大于Y+4且小于或等于Y+4*2，则需要反馈HARQ-ACK信息的第一物理下行信道的总个数X等于Y+4*2，等等，以此类推。相应地，第一HARQ-ACK信息包括X个第一物理下行信道对应的HARQ-ACK信息。另外，如果该终端设备需要在第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，那么第一HARQ-ACK信息还包括该SPS PDSCH对应的HARQ-ACK信息。
在另一种实现方式中，该终端设备可以根据第一物理下行信道的接收情况确定该第一HARQ-ACK信息包括的比特大小，或者说，第一HARQ-ACK信息包括该终端设备接收到的第一物理下行信道对应的HARQ-ACK信息。可选地，所述第一PUSCH不关联第一DAI信息。例如，第一PUSCH不是DCI调度的或调度第一PUSCH的DCI中不包括DAI信息。可选地，所述第一PUSCH关联的第一DAI信息不用于指示第一物理下行信道的个数例如第一DAI信息包括1比特。
在又一种实现方式中，该终端设备可以根据第一DAI信息和/或第一物理下行信道的接收情况确定该第一HARQ-ACK信息包括的比特大小，其中，该第一DAI信息用于指示是否在所述第一PUSCH上复用传输第一HARQ-ACK信息。若所述终端设备收到的与所述第一PUSCH关联的第一DAI信息指示一预设值例如1，则所述终端设备在所述第一PUSCH上复用传输第一HARQ-ACK信息，且第一HARQ-ACK信息包括的比特数可以根据HARQ反馈窗口中包括的候选PDSCH的个数来确定。或者，若所述终端设备收到的与所述第一PUSCH关联的第一DAI信息指示另一预设值例如0，且所述终端设备仅收到一个第一物理下行信道，则所述终端设备在所述第一PUSCH上复用传输第一HARQ-ACK信息，其中，第一HARQ-ACK信息中仅包括该个第一物理下行信道的HARQ-ACK反馈信息。可选地，该终端设备被配置Type-1码本反馈。可选地，所述第一PUSCH关联的DAI信息包括1比特。
可选地，如果该终端设备需要在第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，那么第一HARQ-ACK信息还包括该SPS PDSCH对应的HARQ-ACK信息。
可选地，在本申请另一些实施例中，所述第一PUSCH关联第二物理下行信道，所述方法300还包括：所述终端设备根据所述第二物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第二HARQ-ACK信息和/或所述第一PUSCH上复用的第二HARQ-ACK信息包括的比特数，其中，所述第二HARQ-ACK信息对应所述第二物理下行信道的接收情况。
可选地，在本申请另一些实施例中，所述第一DCI还包括第二DAI信息，所述第二DAI信息用于指示与所述第一PUSCH关联的第二物理下行信道的个数。
进一步地，所述方法300还包括：所述终端设备根据所述第二DAI信息和/或所述第二物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第二HARQ-ACK信息和/或所述第一 PUSCH上复用的第二HARQ-ACK信息包括的比特数，其中，所述第二HARQ-ACK信息对应所述第二物理下行信道的接收情况。
可选地，与所述第二PUSCH关联的第二物理下行信道可以指：所述第一PUSCH对应的第一PUSCH资源和第二物理下行信道的上行HARQ-ACK反馈资源在时域上至少部分重叠。
可选地，第一物理下行信道包括对应TB反馈的下行信道，或者，第一物理下行信道的HARQ-ACK反馈对应基于TB的HARQ-ACK反馈。
可选地，第二物理下行信道包括对应CBG反馈的下行信道，或者，第二物理下行信道的HARQ-ACK反馈对应基于CBG的HARQ-ACK反馈。
可选地，当第一DCI包括第一DAI信息和第二DAI信息时，对应的HARQ-ACK反馈码本可以包括两个HARQ-ACK反馈子码本，其中，第一个HARQ-ACK反馈子码本包括基于TB的反馈，第二个HARQ-ACK反馈子码本包括基于码块组(Code Block Group，CBG)的反馈，所述第一DAI信息和第二DAI信息分别用于确定这两个HARQ-ACK子码本的大小。
可选地，在满足以下条件中的至少一个时，所述第一DCI包括所述第二DAI信息：
所述终端设备被配置反馈两个HARQ-ACK子码本；
所述终端设备被配置码块组CBG传输；
所述终端设备被配置CBG反馈。
以下，结合具体实施例，说明所述第二DAI信息的具体含义，和/或，所述第二物理下行信道的具体实现，和/或，终端设备是否在第一PUSCH上复用传输第二HARQ-ACK信息的方法，和/或，终端设备如何确定在第一PUSCH上复用传输的第二HARQ-ACK信息大小的方法。
实现方式三：
可选地，在一些实施例中，所述第二物理下行信道包括以下情况中的至少一种：
关联PDCCH和第三HARQ进程的PDSCH传输，其中，所述第三HARQ进程包括对应所述第一状态的HARQ进程；
指示SPS PDSCH释放的PDCCH；
指示辅小区休眠状态的PDCCH；
其他对应HARQ-ACK信息的PDCCH，或者说，关联HARQ-ACK信息的PDCCH。
即所述第二物理下行信道包括第一类PDSCH，该第一类PDSCH关联PDCCH并且是通过对应第一状态的第三HARQ进程传输的。
可选地，所述第二物理下行信道包括对应CBG反馈的第一类PDSCH。
可选地，第三HARQ进程包括至少一个HARQ进程。
可选地，所述第二物理下行信道不包括关联PDCCH和第四HARQ进程的PDSCH传输，其中，所述第四HARQ进程包括对应所述第二状态的HARQ进程。
可选地，所述第二物理下行信道不包括对应CBG反馈的第二类PDSCH。
可选地，第四HARQ进程包括至少一个HARQ进程。
可选地，所述第二物理下行信道可以包括第一类PDSCH、指示SPS PDSCH释放的PDCCH、指示辅小区休眠状态的PDCCH和其他对应HARQ-ACK信息的PDCCH中的至少一个，并且不包括第二类PDSCH，其中，该第二类PDSCH关联PDCCH并且是通过对应第二状态的HARQ进程传输的。
可选地，在实现方式三中，所述对应第二状态的HARQ进程不对应上行HARQ-ACK反馈。
应理解，本申请对于第二DAI信息的比特数不作具体限定。
在一些实施例中，所述第二DAI信息为0比特(即不包括该第二DAI信息)，1比特，或2比特或其他的比特数等。
可选地，在一些实施例中，所述第二DAI信息用于指示是否在所述第一PUSCH上复用传输第二HARQ-ACK信息。例如，第二DAI信息包括1比特，当该1比特指示1时，用于指示在所述第一PUSCH上复用传输第二HARQ-ACK信息，当该1比特指示0时，用于指示在所述第一PUSCH上不复用传输第二HARQ-ACK信息。
可选地，在一些实施例中，所述第二DAI信息用于指示与所述第一PUSCH关联的第二物理下行信道的个数，则当第二物理下行信道为实现方式三中的情况时，所述第二DAI信息指示的第二物理下行信道的个数中包括第一类PDSCH、指示SPS PDSCH释放的PDCCH、指示辅小区休眠状态的PDCCH和其他对应HARQ-ACK信息的PDCCH中的至少一个的个数。进一步可选地，所述第二DAI信息指示的第二物理下行信道的个数中不包括所述第二类PDSCH的个数。
实现方式四：
所述第二物理下行信道包括以下情况中的至少一种：
关联PDCCH和所述第三HARQ进程的PDSCH传输以及关联PDCCH和所述第四HARQ进程的PDSCH传输，其中，所述第三HARQ进程包括对应所述第一状态的HARQ进程，所述第四HARQ进程包括对应所述第二状态的HARQ进程；
指示半持续调度SPS PDSCH释放的PDCCH；
指示辅小区休眠状态的PDCCH；
其他对应HARQ-ACK信息的PDCCH，或者说关联HARQ-ACK信息的PDCCH。
即在该实现方式四中，和实现方式三不同，所述第二物理下行信道可以包括关联PDCCH和第二HARQ进程的PDSCH传输，其中，所述第二HARQ进程包括对应第二状态的HARQ进程。或者说，所述第二物理下行信道包括所述第二类PDSCH。
可选地，所述第二物理下行信道包括所述第一类PDSCH、所述第二类PDSCH、指示SPS PDSCH释放的PDCCH、指示辅小区休眠状态的PDCCH和其他对应HARQ-ACK信息的PDCCH中的至少一个。
可选地，在实现方式四中，所述对应第二状态的HARQ进程对应上行HARQ-ACK反馈。
可选地，在本申请一些实施例中，所述终端设备可以根据网络设备的第一指示信息确定所述第二DAI信息的含义，其中，所述第一指示信息用于指示对应所述第二状态的HARQ进程是否进行上行HARQ-ACK反馈。或者，所述终端设备可以根据网络设备的第一指示信息确定对应所述第二状态的HARQ进程是否进行上行HARQ-ACK反馈，其中，所述第一指示信息用于指示所述第二DAI信息的含义。
例如，若所述第一指示信息指示对应所述第二状态的HARQ进程不进行上行HARQ-ACK反馈，则第二DAI信息的含义可以为实现方式三中的情况。此情况下，所述终端设备可以不向网络设备反馈通过第二状态的HARQ进程传输的PDSCH对应的HARQ反馈信息。即只向网络设备反馈通过第一状态的HARQ进程传输的PDSCH对应的HARQ反馈信息。
又例如，若所述第一指示信息指示对应所述第二状态的HARQ进程需要进行上行HARQ-ACK反馈，则第二DAI信息的含义可以为实现方式四中的情况。此情况下，所述终端设备可以向网络设备反馈通过第二状态的HARQ进程传输的PDSCH对应的HARQ反馈信息。即向网络设备反馈通过第一状态和第二状态的HARQ进程传输的PDSCH对应的HARQ反馈信息。
进一步地，在本申请一些实施例中，所述终端设备还可以确定是否在所述第一PUSCH上复用传输第二物理下行信道对应的第二HARQ-ACK信息，和/或确定该第一PUSCH上复用的第二HARQ-ACK信息包括的比特数。
应理解，在本申请实施例中，所述终端设备确定是否在所述第一PUSCH上复用传输所述第二物理下行信道对应的第二HARQ-ACK信息的具体实现可以参考前述实施例中所述终端设备确定是否在所述第一PUSCH上复用传输第一物理下行信道对应的第一HARQ-ACK信息的相关实现，为了简洁，这里不再赘述。
还应理解，在本申请实施例中，所述终端设备确定在该第一PUSCH上复用的第二HARQ-ACK信息包括的比特数的具体实现可以参考前述实施例中所述终端设备确定在该第一PUSCH上复用的第一HARQ-ACK信息包括的比特数的相关实现，为了简洁，这里不再赘述。
在本申请另一些实施例中，若所述终端设备收到的所述第二物理下行信道的个数大于或等于1，则所述终端设备在所述第一PUSCH上复用传输所述第二HARQ-ACK信息；或者，若所述终端设备没有收到所述第二物理下行信道，则所述终端设备在所述第一PUSCH上不复用传输所述第二HARQ-ACK信息。
在本申请又一些实施例中，若所述终端设备收到的所述第二物理下行信道的个数大于或等于1，则所述终端设备根据所述第二DAI信息，在所述第一PUSCH上复用传输所述第二HARQ-ACK信息；或者，若所述终端设备没有收到所述第二物理下行信道，且所述第二DAI信息指示所述预设值，则所述终端设备在所述第一PUSCH上不复用传输所述第二HARQ-ACK信息。
在本申请又一些实施例中，若终端设备被配置Type-1码本反馈，则第一DCI中不包括第二DAI信息。
以下，结合几种典型的HARQ-ACK码本反馈方式，以使用对应DCI格式0_1的第一DCI调度第一PUSCH传输为例，说明该第一DCI中的第一DAI信息和/或第二DAI信息的作用以及具体的复用方式。
一、如果终端设备被配置了Type-1 HARQ-ACK码本反馈，那么该第一DAI信息包括1比特，第二DAI信息包括0比特(或者说，不包括第二DAI信息)。
第一DAI信息用于指示是否在第一PUSCH上复用传输第一HARQ-ACK信息。
例如，第一DAI信息包括1比特，当该比特指示1时，用于指示在所述第一PUSCH上复用传输第一HARQ-ACK信息，当该比特指示0时，用于指示在所述第一PUSCH上不复用传输第一HARQ-ACK信息。
例如，当第一DAI信息指示1时，则终端设备可以根据HARQ反馈窗口中包括的候选PDSCH的个数来确定第一HARQ-ACK信息包括的比特数。或者，当第一DAI信息指示0，且终端设备仅收到一个第一物理下行信道时，则该终端设备在第一PUSCH上复用传输第一HARQ-ACK信息，其中，第一HARQ-ACK信息中仅包括该个第一物理下行信道的HARQ-ACK反馈信息。
例如，若网络设备发送的与第一PUSCH关联的第一物理下行信道的总个数大于1时，网络设备将该比特设置为1；或者，若网络设备没有发送与第一PUSCH关联的第一物理下行信道或仅发送一个与第一PUSCH关联的第一物理下行信道时，网络设备将该比特设置为0。
二、如果终端设备被配置了Type-2 HARQ-ACK码本反馈，那么，
情况1：如果包括一个HARQ-ACK码本，或者终端设备未被配置CBG传输或CBG反馈，那么第一DAI信息包括2比特，用于确定HARQ-ACK码本的大小，第二DAI信息包括0比特(或者说不包括第二DAI信息)。
所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数。
网络设备可以根据调度的与第一PUSCH关联的第一物理下行信道的总个数设置所述第一DAI信息的取值。
情况2：如果包括两个HARQ-ACK子码本，或者终端设备被配置CBG传输或CBG反馈，那么第一DAI信息包括2比特，用于确定第一个HARQ-ACK子码本的大小，第二DAI信息包括2比特，用于确定第二个HARQ-ACK子码本的大小。
所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数。其中，该第一物理下行信道对应TB反馈，即第一物理下行信道包括需要基于TB反馈的物理下行信道。
所述第一DAI信息用于指示与所述第一PUSCH关联的第二物理下行信道的个数。其中，该第二物理下行信道对应CBG反馈，即第二物理下行信道包括需要基于CBG反馈的物理下行信道。
三、如果终端设备被配置了eType-2 HARQ-ACK码本反馈，那么，
情况1：第一DAI信息包括2比特，用于确定HARQ-ACK码本的大小，第二DAI信息包括0比特(或者说不包括第二DAI信息)。
如果第一PUSCH上要反馈两个组的HARQ-ACK信息，所述第一DAI信息用于指示与所述第一PUSCH关联的对应第一组(或者说，组0)的第一物理下行信道的个数。
如果第一PUSCH上要反馈一个组的HARQ-ACK信息，所述第一DAI信息用于指示与所述第一PUSCH关联的对应调度组(例如组0或组1)的第一物理下行信道的个数。
情况2：第一DAI信息包括2个DAI信息，每个DAI信息包括2比特，即第一DAI信息包括4个比特，用于确定HARQ-ACK码本的大小，第二DAI信息包括0比特(或者说不包括第二DAI信息)。
所述第一DAI信息中的第一个DAI信息用于指示与所述第一PUSCH关联的对应第一组的第一物理下行信道的个数。所述第一DAI信息中的第二个DAI信息用于指示与所述第一PUSCH关联的对应第二组的第一物理下行信道的个数。
情况3：被配置CBG反馈，第一DAI信息包括2比特，第二DAI信息包括2比特。
如果第一PUSCH上要反馈两个组的HARQ-ACK信息，所述第一DAI信息用于指示与所述第一PUSCH关联的对应第一组且对应TB反馈的第一物理下行信道的个数。所述第二DAI信息用于指示与所述第一PUSCH关联的对应第一组且对应CBG反馈的第二物理下行信道的个数。
如果第一PUSCH上要反馈一个组的HARQ-ACK信息，所述第一DAI信息用于指示与所述第一PUSCH关联的对应调度组(例如组0或组1)且对应TB反馈的第一物理下行信道的个数。所述第二DAI信息用于指示与所述第一PUSCH关联的对应调度组(例如组0或组1)且对应CBG反馈的第二物理下行信道的个数。
情况4：被配置CBG反馈，第一DAI信息包括2个DAI信息，每个DAI信息包括2比特，第二DAI信息包括2个DAI信息，每个DAI信息包括2比特。
所述第一DAI信息中的第一个DAI信息用于指示与所述第一PUSCH关联的对应第一组且对应TB反馈的第一物理下行信道的个数。
所述第一DAI信息中的第二个DAI信息用于指示与所述第一PUSCH关联的对应第二组且对应TB反馈的第一物理下行信道的个数。
所述第二DAI信息中的第一个DAI信息用于指示与所述第一PUSCH关联的对应第一组且对应 CBG反馈的第二物理下行信道的个数。
所述第二DAI信息中的第二个DAI信息用于指示与所述第一PUSCH关联的对应第二组且对应CBG反馈的第二物理下行信道的个数。
作为示例而非限定，在终端设备被配置了eType-2 HARQ-ACK码本反馈情况下，DCI格式0_1中的DAI信息的大小包括表3所示的情况中的一种：
表3
Figure PCTCN2020117491-appb-000003
在表3的示例中，a0或b0表示DAI信息中的低位比特(Least Significant Bit，LSB)，a3或b3表示DAI信息中的高位比特MSB(most significant bits，MSB)。
可选地，若所述第一DCI包括所述第一DAI信息，并且第一DAI信息的含义为前述的实现方式一中的情况时，S320可以包括：
如果终端设备没有被配置CBG传输(例如终端设备没有被提供高层参数PDSCH-CodeBlockGroupTransmission)，且该终端设备收到包括第一DAI信息的第一DCI格式调度的第一PUSCH传输，且该第一DAI信息取值为预设值，且该终端设备在HARQ反馈窗口对应的PDCCH检测机会中没有收到DCI格式1_0或DCI格式1_1调度的对应使能态的HARQ进程的PDSCH接收的PDCCH，或没有收到指示任意服务小区上的SPS PDSCH释放的PDCCH，且该终端设备没有对应SPS PDSCH接收的HARQ-ACK信息复用在该第一PUSCH上，则该终端设备不将第一HARQ-ACK信息复用在该第一PUSCH上；和/或
如果终端设备收到包括对应某个组标号的第一DAI信息的第一DCI格式调度的第一PUSCH传输，且该第一DAI信息取值为预设值，且该终端设备没有收到任意DCI格式调度的对应该组标号的且对应使能态的HARQ进程的PDSCH接收的PDCCH，且该终端设备没有收到任意DCI格式指示的反馈对应该组标号的HARQ-ACK信息的请求，则该终端设备不将对应该组标号的HARQ-ACK信息复用在该第一PUSCH上。
可选地，若所述第一DCI包括所述第一DAI信息，并且第一DAI信息的含义为前述的实现方式二中的情况，S320可以包括：
如果终端设备没有被配置CBG传输(例如终端设备没有被提供高层参数PDSCH-CodeBlockGroupTransmission)，且该终端设备收到包括第一DAI信息的第一DCI格式调度的第一PUSCH传输，且该第一DAI信息取值为预设值，且该终端设备在HARQ反馈窗口对应的PDCCH检测机会中没有收到DCI格式1_0或DCI格式1_1调度的对应使能态和去使能态的HARQ进程的PDSCH接收的PDCCH，或没有收到指示任意服务小区上的SPS PDSCH释放的PDCCH，且该终端设备没有对应SPS PDSCH接收的HARQ-ACK信息复用在该第一PUSCH上，则该终端设备不将第一HARQ-ACK信息复用在该第一PUSCH上；和/或
如果终端设备收到包括对应某个组标号的第一DAI信息的第一DCI格式调度的第一PUSCH传输，且该第一DAI信息取值为预设值，且该终端设备没有收到任意DCI格式调度的对应该组标号的且对应使能态和非使能态的HARQ进程的PDSCH接收，且该终端设备没有收到任意DCI格式指示的反馈对应该组标号的HARQ-ACK信息的请求，则该终端设备不将对应该组标号的HARQ-ACK信息复用在该第一PUSCH上。
可选地，若所述第一DCI包括所述第一DAI信息和第二DAI信息，并且第一DAI信息的含义和第二DAI信息的含义分别为前述的实现方式一和实现方式三中的情况，在一些具体实施例中，S320 可以包括：
如果终端设备被配置CBG传输(例如终端设备被提供高层参数PDSCH-CodeBlockGroupTransmission)，且该终端设备收到包括第一DAI信息和第二DAI信息的第一DCI格式调度的第一PUSCH传输，且该第一DAI信息取值为预设值或该第二DAI信息取值为预设值，且该终端设备在HARQ反馈窗口对应的PDCCH检测机会中没有收到对应的DCI格式1_0或DCI格式1_1调度的对应使能态的HARQ进程的PDSCH接收的PDCCH、或没有收到指示任意服务小区上的SPS PDSCH释放的PDCCH、或没有收到指示SCell dormancy的DCI格式1_1的PDCCH，且该终端设备没有对应SPS PDSCH接收的HARQ-ACK信息复用在该第一PUSCH上，则该终端设备在该第一PUSCH上不复用对应的第一子码本或第二子码本中的HARQ-ACK信息。
可选地，若所述第一DCI包括所述第一DAI信息和第二DAI信息，并且第一DAI信息的含义和第二DAI信息的含义分别为前述的实现方式二和实现方式四中的情况，在一些具体实施例中，S320可以包括：
如果终端设备被配置CBG传输(例如终端设备被提供高层参数PDSCH-CodeBlockGroupTransmission)，且该终端设备收到包括第一DAI信息和第二DAI信息的第一DCI格式调度的第一PUSCH传输，且该第一DAI信息取值为预设值或该第二DAI信息取值为预设值，且该终端设备在HARQ反馈窗口对应的PDCCH检测机会中没有收到对应的DCI格式1_0或DCI格式1_1调度的对应使能态和去使能态的HARQ进程的PDSCH接收的PDCCH、或没有收到指示任意服务小区上的SPS PDSCH释放的PDCCH、或没有收到指示SCell dormancy的DCI格式1_1的PDCCH，且该终端设备没有对应SPS PDSCH接收的HARQ-ACK信息复用在该第一PUSCH上，则该终端设备在该第一PUSCH上不复用对应的第一子码本或第二子码本中的HARQ-ACK信息。
因此，在本申请一些实施例中，当终端设备被配置某个或某些HARQ进程对应非使能态时，如果该终端设备的PUSCH资源和PUCCH资源在时域上存在重叠，终端设备可以根据调度该PUSCH资源的DCI中的DAI域的取值和/或物理下行信道的接收情况来确定是否需要在该PUSCH上复用传输HARQ-ACK信息或确定在该PUSCH上复用传输的HARQ-ACK信息的大小。其中，该DAI域指示的下行传输的个数中可以不包括使用非使能态的HARQ进程来进行传输的PDSCH的个数，从而减少了PUSCH上用于传输上行控制信息的开销。
上文结合图3，详细描述了本申请的方法实施例，下文结合图4至图8，详细描述本申请的装置实施例，应理解，装置实施例与方法实施例相互对应，类似的描述可以参照方法实施例。
图4示出了根据本申请实施例的终端设备400的示意性框图。如图4所示，该终端设备400包括：
处理单元410，用于确定传输第一物理上行共享信道PUSCH，其中，所述第一PUSCH关联第一物理下行信道；以及根据所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第一混合自动请求重传应答HARQ-ACK信息，其中，所述第一HARQ-ACK信息对应所述第一物理下行信道的接收情况。
可选地，在一些实施例中，所述第一物理下行信道包括以下中的至少一种：
关联物理下行控制信道PDCCH和第一混合自动请求重传HARQ进程的物理下行共享信道PDSCH传输，其中，所述第一HARQ进程包括对应第一状态的HARQ进程；
指示半持续调度SPS PDSCH释放的PDCCH；
指示辅小区休眠状态的PDCCH；
关联HARQ-ACK信息的PDCCH。
可选地，在一些实施例中，所述第一物理下行信道不包括关联PDCCH和第二HARQ进程的PDSCH传输，其中，所述第二HARQ进程包括对应第二状态的HARQ进程。
可选地，在一些实施例中，所述第一物理下行信道包括以下情况中的至少一种：
关联PDCCH和所述第一HARQ进程的PDSCH传输以及关联PDCCH和所述第二HARQ进程的PDSCH传输，其中，所述第一HARQ进程包括对应所述第一状态的HARQ进程，所述第二HARQ进程包括对应所述第二状态的HARQ进程；
指示半持续调度SPS PDSCH释放的PDCCH；
指示辅小区休眠状态的PDCCH；
关联HARQ-ACK信息的PDCCH。
可选地，在一些实施例中，所述第一PUSCH关联第一物理下行信道，包括：
所述第一PUSCH对应的第一PUSCH资源和所述第一物理下行信道对应的上行HARQ-ACK反馈资源在时域上至少部分重叠。
可选地，在一些实施例中，所述第一物理下行信道对应基于传输块TB的HARQ-ACK反馈方式。
可选地，在一些实施例中，所述第一PUSCH关联第二物理下行信道，所述处理单元410还用于：根据所述第二物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第二混合自动请求重传应答HARQ-ACK信息，其中，所述第二HARQ-ACK信息对应所述第二物理下行信道的接收情况。
可选地，在一些实施例中，所述第二物理下行信道包括：关联PDCCH和第三HARQ进程的PDSCH传输，其中，所述第三HARQ进程包括对应所述第一状态的HARQ进程。
可选地，在一些实施例中，所述第二物理下行信道不包括关联PDCCH和第四HARQ进程的PDSCH传输，其中，所述第四HARQ进程包括对应所述第二状态的HARQ进程。
可选地，在一些实施例中，所述第二物理下行信道包括：关联PDCCH和所述第三HARQ进程的PDSCH传输以及关联PDCCH和所述第四HARQ进程的PDSCH传输，其中，所述第三HARQ进程包括对应所述第一状态的HARQ进程，所述第四HARQ进程包括对应所述第二状态的HARQ进程。
可选地，在一些实施例中，所述第一PUSCH关联第二物理下行信道，包括：
所述第一PUSCH对应的第一PUSCH资源和所述第二物理下行信道对应的上行HARQ-ACK反馈资源在时域上至少部分重叠。
可选地，在一些实施例中，所述第二物理下行信道对应基于码块组CBG的HARQ-ACK反馈方式。
可选地，在一些实施例中，所述终端设备400还包括：
通信单元420，用于接收网络设备发送的第一下行控制信息DCI，所述第一DCI用于调度所述第一PUSCH传输，其中，所述第一DCI中包括第一下行分配指示DAI信息，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数；
所述处理单元410还用于：根据所述第一DAI信息和所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输所述第一HARQ-ACK信息。
可选地，在一些实施例中，所述第一DCI对应的DCI格式包括以下至少一种：DCI格式0_1和DCI格式0_2。
可选地，在一些实施例中，所述处理单元410还用于：
在所述终端设备收到的所述第一物理下行信道的个数大于或等于1，或所述终端设备需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息的情况下，所述终端设备根据所述第一DAI信息，在所述第一PUSCH上复用传输所述第一HARQ-ACK信息。
可选地，在一些实施例中，所述处理单元410还用于：在所述终端设备没有收到所述第一物理下行信道，且所述终端设备不需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，且所述第一DAI信息指示预设值的情况下，在所述第一PUSCH上不复用传输所述第一HARQ-ACK信息。
可选地，在一些实施例中，所述第一PUSCH还关联第二物理下行信道，所述第一DCI中还包括第二DAI信息，所述第二DAI信息用于指示与所述第一PUSCH关联的所述第二物理下行信道的个数，所述处理单元410还用于：
根据所述第二DAI信息和所述第二物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第二HARQ-ACK信息，其中，所述第二HARQ-ACK信息对应所述第二物理下行信道的接收情况。
可选地，在一些实施例中，所述处理单元410还用于：在所述终端设备收到的所述第二物理下行信道的个数大于或等于1的情况下，根据所述第二DAI信息，在所述第一PUSCH上复用传输所述第二HARQ-ACK信息。
可选地，在一些实施例中，所述处理单元410还用于：在所述终端设备没有收到所述第二物理下行信道，且所述第二DAI信息指示所述预设值的情况下，在所述第一PUSCH上不复用传输所述第二HARQ-ACK信息。
可选地，在一些实施例中，所述预设值为0或4。
可选地，在一些实施例中，所述处理单元410还用于：
根据网络设备发送的调度信息确定传输所述第一PUSCH，其中，所述调度信息不包括DCI，或所述调度信息包括第二DCI且所述第二DCI中不包括DAI信息。
可选地，在一些实施例中，所述第二DCI对应的DCI格式包括DCI格式0_0。
可选地，在一些实施例中，所述处理单元410还用于：
在所述终端设备收到的所述第一物理下行信道的个数大于或等于1，或所述终端设备需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息的情况下，在所述第一PUSCH上复用 传输所述第一HARQ-ACK信息。
可选地，在一些实施例中，所述处理单元410还用于：
在所述终端设备没有收到所述第一物理下行信道，且所述终端设备不需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息的情况下，在所述第一PUSCH上不复用传输所述第一HARQ-ACK信息。
可选地，在一些实施例中，所述处理单元410还用于：
若所述终端设备收到的所述第二物理下行信道的个数大于或等于1，在所述第一PUSCH上复用传输所述第二HARQ-ACK信息。
可选地，在一些实施例中，所述处理单元410还用于：
若所述终端设备没有收到所述第二物理下行信道，在所述第一PUSCH上不复用传输所述第二HARQ-ACK信息。
可选地，在一些实施例中，所述对应第一状态的HARQ进程包括以下情况中的至少一种：
所述HARQ进程对应使能态；
所述HARQ进程未被配置去使能参数；
所述HARQ进程对应上行HARQ-ACK反馈。
可选地，在一些实施例中，所述对应第二状态的HARQ进程包括以下情况中的至少一种：
所述HARQ进程对应去使能态；
所述HARQ进程被配置去使能参数。
可选地，在一些实施例中，所述处理单元410还用于：
根据所述网络设备发送的第一指示信息确定对应所述第二状态的HARQ进程不进行上行HARQ-ACK反馈，其中，所述第一指示信息用于指示对应所述第二状态的HARQ进程是否进行上行HARQ-ACK反馈。
可选地，在一些实施例中，所述处理单元410还用于：
根据所述网络设备发送的所述第一指示信息确定对应所述第二状态的HARQ进程需要进行上行HARQ-ACK反馈，其中，所述第一指示信息用于指示对应所述第二状态的HARQ进程是否进行上行HARQ-ACK反馈。
可选地，在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的终端设备400可对应于本申请方法实施例中的终端设备，并且终端设备400中的各个单元的上述和其它操作和/或功能分别为了实现图2所示方法300中终端设备的相应流程，为了简洁，在此不再赘述。
图5是根据本申请实施例的网络设备的示意性框图。图5的网络设备500包括：
通信单元510，用于向终端设备发送第一下行控制信息DCI，所述第一DCI用于调度第一物理上行共享信道PUSCH传输，所述第一DCI中包括第一下行分配指示DAI信息，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数。
可选地，在一些实施例中，所述第一物理下行信道包括以下中的至少一种：
关联物理下行控制信道PDCCH和第一混合自动请求重传HARQ进程的物理下行共享信道PDSCH传输，其中，所述第一HARQ进程包括对应第一状态的HARQ进程；
指示半持续调度SPS PDSCH释放的PDCCH；
指示辅小区休眠状态的PDCCH；
关联HARQ-ACK信息的PDCCH。
可选地，在一些实施例中，所述第一物理下行信道不包括关联PDCCH和第二HARQ进程的PDSCH传输，其中，所述第二HARQ进程包括对应第二状态的HARQ进程。
可选地，在一些实施例中，所述第一物理下行信道包括以下情况中的至少一种：
关联PDCCH和所述第一HARQ进程的PDSCH传输以及关联PDCCH和所述第二HARQ进程的PDSCH传输，其中，所述第一HARQ进程包括对应所述第一状态的HARQ进程，所述第二HARQ进程包括对应所述第二状态的HARQ进程；
指示半持续调度SPS PDSCH释放的PDCCH；
指示辅小区休眠状态的PDCCH；
关联HARQ-ACK信息的PDCCH。
可选地，在一些实施例中，所述第一DCI中还包括第二DAI信息，所述第二DAI信息用于指示与所述第一PUSCH关联的第二物理下行信道的个数。
可选地，在一些实施例中，所述第二物理下行信道包括：关联PDCCH和第三HARQ进程的PDSCH传输，其中，所述第三HARQ进程包括对应所述第一状态的HARQ进程。
可选地，在一些实施例中，所述第二物理下行信道不包括关联PDCCH和第四HARQ进程的PDSCH传输，其中，所述第四HARQ进程包括对应所述第二状态的HARQ进程。
可选地，在一些实施例中，所述第二物理下行信道包括：关联PDCCH和所述第三HARQ进程的PDSCH传输以及关联PDCCH和所述第四HARQ进程的PDSCH传输，其中，所述第三HARQ进程包括对应所述第一状态的HARQ进程，所述第四HARQ进程包括对应所述第二状态的HARQ进程。
可选地，在一些实施例中，所述终端设备被配置反馈两个HARQ-ACK子码本；或，
所述终端设备被配置码块组CBG传输；或，
所述终端设备被配置CBG反馈。
可选地，在一些实施例中，所述对应第一状态的HARQ进程，包括以下情况中的至少一种：
所述HARQ进程对应使能态；
所述HARQ进程未被配置去使能参数；
所述HARQ进程对应上行HARQ-ACK反馈。
可选地，在一些实施例中，所述对应第二状态的HARQ进程，包括以下情况中的至少一种：
所述HARQ进程对应去使能态；
所述HARQ进程被配置去使能参数。
可选地，在一些实施例中，所述通信单元510还用于：
向所述终端设备发送第一指示信息，其中，所述第一指示信息指示对应所述第二状态的HARQ进程不进行上行HARQ-ACK反馈。
可选地，在一些实施例中，所述通信单元510还用于：
向所述终端设备发送第一指示信息，其中，所述第一指示信息指示对应所述第二状态的HARQ进程需要进行上行HARQ-ACK反馈。
可选地，在一些实施例中，所述第二DAI信息用于指示与所述第一PUSCH关联的第二物理下行信道的个数，其中，所述第一PUSCH对应的第一PUSCH资源和所述第二物理下行信道对应的上行HARQ-ACK反馈资源在时域上至少部分重叠。
可选地，在一些实施例中，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数，其中，所述第一PUSCH对应的所述第一PUSCH资源和所述第一物理下行信道对应的上行HARQ-ACK反馈资源在时域上至少部分重叠。
可选地，在一些实施例中，所述第一DCI对应的DCI格式包括以下至少一种：DCI格式0_1和DCI格式0_2。
可选地，在一些实施例中，所述网络设备500还包括：
处理单元，用于根据调度的第一物理下行信道和/或第二物理下行信道的情况，确定所述第一DAI信息的取值和/或所述第二DAI信息的取值。
可选地，在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的网络设备500可对应于本申请方法实施例中的网络设备，并且网络设备500中的各个单元的上述和其它操作和/或功能分别为了实现图3所示方法300中网络设备的相应流程，为了简洁，在此不再赘述。
图6是本申请实施例提供的一种通信设备600示意性结构图。图6所示的通信设备600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图6所示，通信设备600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，如图6所示，通信设备600还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备600具体可为本申请实施例的网络设备，并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备600具体可为本申请实施例的移动终端/终端设备，并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
图7是本申请实施例的芯片的示意性结构图。图7所示的芯片700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图7所示，芯片700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该芯片700还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片700还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端设备，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图8是本申请实施例提供的一种通信系统900的示意性框图。如图8所示，该通信系统900包括终端设备910和网络设备920。
其中，该终端设备910可以用于实现上述方法中由终端设备实现的相应的功能，以及该网络设备920可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁， 在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (60)

  1. 一种无线通信的方法，其特征在于，包括：
    终端设备确定传输第一物理上行共享信道PUSCH，其中，所述第一PUSCH关联第一物理下行信道；
    所述终端设备根据所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第一混合自动请求重传应答HARQ-ACK信息，其中，所述第一HARQ-ACK信息对应所述第一物理下行信道的接收情况。
  2. 根据权利要求1所述的方法，其特征在于，所述第一物理下行信道包括以下中的至少一种：
    关联物理下行控制信道PDCCH和第一混合自动请求重传HARQ进程的物理下行共享信道PDSCH传输，其中，所述第一HARQ进程包括对应第一状态的HARQ进程；
    指示半持续调度SPS PDSCH释放的PDCCH；
    指示辅小区休眠状态的PDCCH；
    关联HARQ-ACK信息的PDCCH。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一物理下行信道不包括关联PDCCH和第二HARQ进程的PDSCH传输，其中，所述第二HARQ进程包括对应第二状态的HARQ进程。
  4. 根据权利要求1所述的方法，其特征在于，所述第一物理下行信道包括以下情况中的至少一种：
    关联PDCCH和所述第一HARQ进程的PDSCH传输以及关联PDCCH和所述第二HARQ进程的PDSCH传输，其中，所述第一HARQ进程包括对应所述第一状态的HARQ进程，所述第二HARQ进程包括对应所述第二状态的HARQ进程；
    指示半持续调度SPS PDSCH释放的PDCCH；
    指示辅小区休眠状态的PDCCH；
    关联HARQ-ACK信息的PDCCH。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一PUSCH关联第一物理下行信道，包括：
    所述第一PUSCH对应的第一PUSCH资源和所述第一物理下行信道对应的上行HARQ-ACK反馈资源在时域上至少部分重叠。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一物理下行信道对应基于传输块TB的HARQ-ACK反馈方式。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述第一PUSCH关联第二物理下行信道，所述方法还包括：
    所述终端设备根据所述第二物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第二混合自动请求重传应答HARQ-ACK信息，其中，所述第二HARQ-ACK信息对应所述第二物理下行信道的接收情况。
  8. 根据权利要求7所述的方法，其特征在于，所述第二物理下行信道包括：
    关联PDCCH和第三HARQ进程的PDSCH传输，其中，所述第三HARQ进程包括对应所述第一状态的HARQ进程。
  9. 根据权利要求7或8所述的方法，其特征在于，所述第二物理下行信道不包括关联PDCCH和第四HARQ进程的PDSCH传输，其中，所述第四HARQ进程包括对应所述第二状态的HARQ进程。
  10. 根据权利要求7所述的方法，其特征在于，所述第二物理下行信道包括：
    关联PDCCH和所述第三HARQ进程的PDSCH传输以及关联PDCCH和所述第四HARQ进程的PDSCH传输，其中，所述第三HARQ进程包括对应所述第一状态的HARQ进程，所述第四HARQ进程包括对应所述第二状态的HARQ进程。
  11. 根据权利要求7至10中任一项所述的方法，其特征在于，所述第一PUSCH关联第二物理下行信道，包括：
    所述第一PUSCH对应的第一PUSCH资源和所述第二物理下行信道对应的上行HARQ-ACK反馈资源在时域上至少部分重叠。
  12. 根据权利要求7至11中任一项所述的方法，其特征在于，所述第二物理下行信道对应基于码块组CBG的HARQ-ACK反馈方式。
  13. 根据权利要求1至12中任一项所述的方法，其特征在于，所述终端设备确定传输第一PUSCH，包括：
    所述终端设备接收网络设备发送的第一下行控制信息DCI，所述第一DCI用于调度所述第一PUSCH传输，其中，所述第一DCI中包括第一下行分配指示DAI信息，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数；
    所述终端设备根据所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第一混合自动请求重传应答HARQ-ACK信息，包括：
    所述终端设备根据所述第一DAI信息和所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输所述第一HARQ-ACK信息。
  14. 根据权利要求13所述的方法，其特征在于，所述第一DCI对应的DCI格式包括以下至少一种：DCI格式0_1和DCI格式0_2。
  15. 根据权利要求13或14所述的方法，其特征在于，所述终端设备根据所述第一DAI信息和所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输所述第一HARQ-ACK信息，包括：
    在所述终端设备收到的所述第一物理下行信道的个数大于或等于1，或所述终端设备需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息的情况下，所述终端设备根据所述第一DAI信息，在所述第一PUSCH上复用传输所述第一HARQ-ACK信息。
  16. 根据权利要求13或14所述的方法，其特征在于，所述终端设备根据所述第一DAI信息和所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输所述第一HARQ-ACK信息，包括：
    在所述终端设备没有收到所述第一物理下行信道，且所述终端设备不需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息，且所述第一DAI信息指示预设值的情况下，所述终端设备在所述第一PUSCH上不复用传输所述第一HARQ-ACK信息。
  17. 根据权利要求13至16中任一项所述的方法，其特征在于，所述第一PUSCH还关联第二物理下行信道，所述第一DCI中还包括第二DAI信息，所述第二DAI信息用于指示与所述第一PUSCH关联的所述第二物理下行信道的个数，所述方法还包括：
    所述终端设备根据所述第二DAI信息和所述第二物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第二HARQ-ACK信息，其中，所述第二HARQ-ACK信息对应所述第二物理下行信道的接收情况。
  18. 根据权利要求17所述的方法，其特征在于，所述终端设备根据所述第二DAI信息和所述第二物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第二HARQ-ACK信息，包括：
    在所述终端设备收到的所述第二物理下行信道的个数大于或等于1的情况下，所述终端设备根据所述第二DAI信息，在所述第一PUSCH上复用传输所述第二HARQ-ACK信息。
  19. 根据权利要求17所述的方法，其特征在于，所述终端设备根据所述第二DAI信息和所述第二物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第二HARQ-ACK信息，包括：
    在所述终端设备没有收到所述第二物理下行信道，且所述第二DAI信息指示所述预设值的情况下，所述终端设备在所述第一PUSCH上不复用传输所述第二HARQ-ACK信息。
  20. 根据权利要求16或19所述的方法，其特征在于，所述预设值为0或4。
  21. 根据权利要求1至12中任一项所述的方法，其特征在于，所述终端设备确定传输第一PUSCH，包括：
    所述终端设备根据网络设备发送的调度信息确定传输所述第一PUSCH，其中，所述调度信息不包括DCI，或所述调度信息包括第二DCI且所述第二DCI中不包括DAI信息。
  22. 根据权利要求21所述的方法，其特征在于，所述第二DCI对应的DCI格式包括DCI格式0_0。
  23. 根据权利要求1至12、21、22中任一项所述的方法，其特征在于，所述终端设备根据所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输所述第一HARQ-ACK信息，包括：
    在所述终端设备收到的所述第一物理下行信道的个数大于或等于1，或所述终端设备需要在所述第一PUSCH上复用传输SPS PDSCH对应的HARQ-ACK信息的情况下，所述终端设备在所述第一PUSCH上复用传输所述第一HARQ-ACK信息。
  24. 根据权利要求1至12、21、22中任一项所述的方法，其特征在于，所述终端设备根据所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输所述第一HARQ-ACK信息，包括：
    在所述终端设备没有收到所述第一物理下行信道，且所述终端设备不需要在所述第一PUSCH上 复用传输SPS PDSCH对应的HARQ-ACK信息的情况下，所述终端设备在所述第一PUSCH上不复用传输所述第一HARQ-ACK信息。
  25. 根据权利要求7至12中任一项所述的方法，其特征在于，所述终端设备根据所述第二物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第二HARQ-ACK信息，包括：
    若所述终端设备收到的所述第二物理下行信道的个数大于或等于1，所述终端设备在所述第一PUSCH上复用传输所述第二HARQ-ACK信息。
  26. 根据权利要求7至12中任一项所述的方法，其特征在于，所述终端设备根据所述第二物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第二HARQ-ACK信息，包括：
    若所述终端设备没有收到所述第二物理下行信道，所述终端设备在所述第一PUSCH上不复用传输所述第二HARQ-ACK信息。
  27. 根据权利要求2、4、8、10中任一项所述的方法，其特征在于，所述对应第一状态的HARQ进程，包括以下情况中的至少一种：
    所述HARQ进程对应使能态；
    所述HARQ进程未被配置去使能参数；
    所述HARQ进程对应上行HARQ-ACK反馈。
  28. 根据权利要求3、4、9、10中任一项所述的方法，其特征在于，所述对应第二状态的HARQ进程，包括以下情况中的至少一种：
    所述HARQ进程对应去使能态；
    所述HARQ进程被配置去使能参数。
  29. 根据权利要求3、9、28中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备根据所述网络设备发送的第一指示信息确定对应所述第二状态的HARQ进程不进行上行HARQ-ACK反馈，其中，所述第一指示信息用于指示对应所述第二状态的HARQ进程是否进行上行HARQ-ACK反馈。
  30. 根据权利要求4、10、28中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备根据所述网络设备发送的所述第一指示信息确定对应所述第二状态的HARQ进程需要进行上行HARQ-ACK反馈，其中，所述第一指示信息用于指示对应所述第二状态的HARQ进程是否进行上行HARQ-ACK反馈。
  31. 一种无线通信的方法，其特征在于，包括：
    网络设备向终端设备发送第一下行控制信息DCI，所述第一DCI用于调度第一物理上行共享信道PUSCH传输，所述第一DCI中包括第一下行分配指示DAI信息，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数。
  32. 根据权利要求31所述的方法，其特征在于，所述第一物理下行信道包括以下中的至少一种：
    关联物理下行控制信道PDCCH和第一混合自动请求重传HARQ进程的物理下行共享信道PDSCH传输，其中，所述第一HARQ进程包括对应第一状态的HARQ进程；
    指示半持续调度SPS PDSCH释放的PDCCH；
    指示辅小区休眠状态的PDCCH；
    关联HARQ-ACK信息的PDCCH。
  33. 根据权利要求31或32所述的方法，其特征在于，所述第一物理下行信道不包括关联PDCCH和第二HARQ进程的PDSCH传输，其中，所述第二HARQ进程包括对应第二状态的HARQ进程。
  34. 根据权利要求31所述的方法，其特征在于，所述第一物理下行信道包括以下情况中的至少一种：
    关联PDCCH和所述第一HARQ进程的PDSCH传输以及关联PDCCH和所述第二HARQ进程的PDSCH传输，其中，所述第一HARQ进程包括对应所述第一状态的HARQ进程，所述第二HARQ进程包括对应所述第二状态的HARQ进程；
    指示半持续调度SPS PDSCH释放的PDCCH；
    指示辅小区休眠状态的PDCCH；
    关联HARQ-ACK信息的PDCCH。
  35. 根据权利要求31至34中任一项所述的方法，其特征在于，所述第一DCI中还包括第二DAI信息，所述第二DAI信息用于指示与所述第一PUSCH关联的第二物理下行信道的个数。
  36. 根据权利要求35所述的方法，其特征在于，所述第二物理下行信道包括以下情况中的至少一种：
    关联PDCCH和第三HARQ进程的PDSCH传输，其中，所述第三HARQ进程包括对应所述第一 状态的HARQ进程。
  37. 根据权利要求35或36所述的方法，其特征在于，所述第二物理下行信道不包括关联PDCCH和第四HARQ进程的PDSCH传输，其中，所述第四HARQ进程包括对应所述第二状态的HARQ进程。
  38. 根据权利要求35所述的方法，其特征在于，所述第二物理下行信道包括以下情况中的至少一种：
    关联PDCCH和所述第三HARQ进程的PDSCH传输以及关联PDCCH和所述第四HARQ进程的PDSCH传输，其中，所述第三HARQ进程包括对应所述第一状态的HARQ进程，所述第四HARQ进程包括对应所述第二状态的HARQ进程。
  39. 根据权利要求35至38中任一项所述的方法，其特征在于，所述终端设备被配置反馈两个HARQ-ACK子码本；或，
    所述终端设备被配置码块组CBG传输；或，
    所述终端设备被配置CBG反馈；或，
    所述第二物理下行信道对应基于码块组CBG的HARQ-ACK反馈方式。
  40. 根据权利要求32、34、36、38中任一项所述的方法，其特征在于，所述对应第一状态的HARQ进程，包括以下情况中的至少一种：
    所述HARQ进程对应使能态；
    所述HARQ进程未被配置去使能参数；
    所述HARQ进程对应上行HARQ-ACK反馈。
  41. 根据权利要求33、34、37、38中任一项所述的方法，其特征在于，所述对应第二状态的HARQ进程，包括以下情况中的至少一种：
    所述HARQ进程对应去使能态；
    所述HARQ进程被配置去使能参数。
  42. 根据权利要求33、37、41中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端设备发送第一指示信息，其中，所述第一指示信息指示对应所述第二状态的HARQ进程不进行上行HARQ-ACK反馈。
  43. 根据权利要求34、38、41中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端设备发送第一指示信息，其中，所述第一指示信息指示对应所述第二状态的HARQ进程需要进行上行HARQ-ACK反馈。
  44. 根据权利要求35至39中任一项所述的方法，其特征在于，所述第二DAI信息用于指示与所述第一PUSCH关联的第二物理下行信道的个数，其中，所述第一PUSCH对应的第一PUSCH资源和所述第二物理下行信道对应的上行HARQ-ACK反馈资源在时域上至少部分重叠。
  45. 根据权利要求31至44中任一项所述的方法，其特征在于，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数，其中，所述第一PUSCH对应的所述第一PUSCH资源和所述第一物理下行信道对应的上行HARQ-ACK反馈资源在时域上至少部分重叠。
  46. 根据权利要求31至45中任一项所述的方法，其特征在于，所述第一DCI对应的DCI格式包括以下至少一种：DCI格式0_1和DCI格式0_2。
  47. 根据权利要求31至46中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备根据调度的所述第一物理下行信道的情况，确定所述第一DAI的取值。
  48. 根据权利要求35至39中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备根据调度的所述第二物理下行信道的情况，确定所述第二DAI的取值。
  49. 一种终端设备，其特征在于，包括：
    处理单元，用于确定传输第一物理上行共享信道PUSCH，其中，所述第一PUSCH关联第一物理下行信道；以及
    根据所述第一物理下行信道的接收情况，确定是否在所述第一PUSCH上复用传输第一混合自动请求重传应答HARQ-ACK信息，其中，所述第一HARQ-ACK信息对应所述第一物理下行信道的接收情况。
  50. 一种网络设备，其特征在于，包括：
    通信单元，用于向终端设备发送第一下行控制信息DCI，所述第一DCI用于调度第一物理上行共享信道PUSCH传输，所述第一DCI中包括第一下行分配指示DAI信息，所述第一DAI信息用于指示与所述第一PUSCH关联的第一物理下行信道的个数。
  51. 一种终端设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述 处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至30中任一项所述的方法。
  52. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至30中任一项所述的方法。
  53. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至30中任一项所述的方法。
  54. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至30中任一项所述的方法。
  55. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至30中任一项所述的方法。
  56. 一种网络设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求18至20中任一项所述的方法。
  57. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求31至48中任一项所述的方法。
  58. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求31至48中任一项所述的方法。
  59. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求31至48中任一项所述的方法。
  60. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求31至48中任一项所述的方法。
PCT/CN2020/117491 2020-09-24 2020-09-24 无线通信的方法、终端设备和网络设备 WO2022061661A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP20954513.6A EP4216628A4 (en) 2020-09-24 2020-09-24 WIRELESS COMMUNICATION METHOD, TERMINAL DEVICE AND NETWORK DEVICE
PCT/CN2020/117491 WO2022061661A1 (zh) 2020-09-24 2020-09-24 无线通信的方法、终端设备和网络设备
CN202311368176.8A CN117499002A (zh) 2020-09-24 2020-09-24 无线通信的方法、终端设备和网络设备
CN202080104595.9A CN116235444A (zh) 2020-09-24 2020-09-24 无线通信的方法、终端设备和网络设备
US18/171,232 US20230199799A1 (en) 2020-09-24 2023-02-17 Wireless communication method, terminal device and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/117491 WO2022061661A1 (zh) 2020-09-24 2020-09-24 无线通信的方法、终端设备和网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/171,232 Continuation US20230199799A1 (en) 2020-09-24 2023-02-17 Wireless communication method, terminal device and network device

Publications (1)

Publication Number Publication Date
WO2022061661A1 true WO2022061661A1 (zh) 2022-03-31

Family

ID=80846032

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/117491 WO2022061661A1 (zh) 2020-09-24 2020-09-24 无线通信的方法、终端设备和网络设备

Country Status (4)

Country Link
US (1) US20230199799A1 (zh)
EP (1) EP4216628A4 (zh)
CN (2) CN116235444A (zh)
WO (1) WO2022061661A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024055319A1 (zh) * 2022-09-16 2024-03-21 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200137695A1 (en) * 2017-04-21 2020-04-30 Samsung Electronics Co., Ltd. Information type multiplexing and power control

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019216729A1 (ko) * 2018-05-11 2019-11-14 주식회사 윌러스표준기술연구소 무선 통신 시스템의 상향 링크 제어 정보 멀티플렉싱 방법 및 이를 이용하는 장치

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200137695A1 (en) * 2017-04-21 2020-04-30 Samsung Electronics Co., Ltd. Information type multiplexing and power control

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Solutions for NR to support non-terrestrial networks (NTN) (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 38.821, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. V1.0.0, 2 December 2019 (2019-12-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 143, XP051840691 *
HUAWEI, HISILICON: "Summary of MAC remaining issues for eURLLC", 3GPP DRAFT; R2-2004147, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200420 - 20200430, 1 May 2020 (2020-05-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051879384 *
OPPO: "Remaining issues on HARQ enhancements for NR-U", 3GPP DRAFT; R1-2000472, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Athens, Greece; 20200224 - 20200228, 15 February 2020 (2020-02-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051853323 *
See also references of EP4216628A4 *
VIVO: "Remaining issues on HARQ operation for NR-U", 3GPP DRAFT; R1-2000311, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200224 - 20200306, 14 February 2020 (2020-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051852800 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024055319A1 (zh) * 2022-09-16 2024-03-21 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备

Also Published As

Publication number Publication date
EP4216628A1 (en) 2023-07-26
US20230199799A1 (en) 2023-06-22
CN116235444A (zh) 2023-06-06
CN117499002A (zh) 2024-02-02
EP4216628A4 (en) 2023-11-15

Similar Documents

Publication Publication Date Title
US20220407629A1 (en) Data transmission method and device
WO2021168834A1 (zh) 数据传输方法、装置及设备
WO2020248258A1 (zh) 无线通信方法、收端设备和发端设备
WO2021237721A1 (zh) Harq-ack码本的反馈方法和终端设备
US20230231665A1 (en) Method for feeding back hybrid automatic repeat request acknowledgement (harq-ack) and terminal device
WO2021237702A1 (zh) Harq-ack码本的反馈方法和终端设备
CN114788204B (zh) Harq进程的状态确定方法、装置及设备
WO2020034223A1 (zh) Harq信息的传输方法、网络设备和终端设备
WO2022021007A1 (zh) 无线通信方法、终端设备和网络设备
WO2021217378A1 (zh) 无线通信方法、终端设备和网络设备
US20230199799A1 (en) Wireless communication method, terminal device and network device
WO2022099555A1 (zh) 无线通信的方法、终端设备和网络设备
WO2021226850A1 (zh) Harq-ack码本的反馈方法、终端设备和网络设备
WO2021227142A1 (zh) Harq-ack码本的反馈方法、终端设备和网络设备
CN116114197B (zh) 无线通信的方法、终端设备和网络设备
WO2022061548A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022021032A1 (zh) 信息处理方法、终端设备和网络设备
WO2022141652A1 (zh) 无线通信的方法和设备
WO2023039811A1 (zh) 通信方法及通信装置
WO2022110071A1 (zh) 无线通信的方法和终端设备
WO2024055319A1 (zh) 无线通信的方法、终端设备和网络设备
WO2021174557A1 (zh) 生成混合自动重传请求应答码本的方法和终端设备
WO2023004584A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022077481A1 (zh) 一种信道传输方法及其装置
WO2023004789A1 (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: 20954513

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020954513

Country of ref document: EP

Effective date: 20230419