Wireless communication method, terminal device and network device

Abstract

A wireless communication method, terminal device and network device, the method comprising: the 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 terminal device determines whether to multiplex and transmit a first hybrid automatic repeat request acknowledgment HARQ‑ACK information on the first PUSCH according to the reception status of the first physical downlink channel, wherein the first HARQ‑ACK information corresponds to the reception status of the first physical downlink channel.

Description

[0001] This application is a divisional application of an application with a filing date of September 24, 2020, application number 2020801045959, and invention name “Method, terminal device and network device for wireless communication”. Technical Field

[0002] The embodiments of the present application relate to the field of communications, and specifically to a wireless communication method, terminal equipment, and network equipment. Background Art

[0003] In a non-terrestrial network (NTN) system, for downlink data transmission of a terminal device, a network device may indicate to the terminal device to enable a certain or certain downlink hybrid automatic repeat request (HARQ) process's hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback. In this case, 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 HARQ-ACK information corresponding to downlink data transmission on a first physical uplink control channel (PUCCH) resource, if the first PUCCH resource and the first 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 HARQ-ACK information included is an urgent problem to be solved. Summary of the invention

[0004] The embodiments of the present application provide a method, terminal device and network device for wireless communication, which are conducive to multiplexing PUSCH resources according to the reception status of the physical downlink channel associated with the PUSCH when the network device schedules PUSCH transmission and the PUSCH is associated with a physical downlink channel, thereby improving system performance.

[0005] In a first aspect, a method for wireless communication is provided, 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 terminal device determines, according to a reception status of the first physical downlink channel, whether to multiplex and transmit a first hybrid automatic repeat request acknowledgment HARQ-ACK information on the first PUSCH, wherein the first HARQ-ACK information corresponds to the reception status of the first physical downlink channel.

[0006] In a second aspect, a method for wireless communication is provided, including: a network device sends first downlink control information DCI to a terminal device, the first DCI is used to schedule the transmission of a first physical uplink shared channel PUSCH, the first DCI includes first downlink allocation indication DAI information, and the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH.

[0007] In a third aspect, a terminal device is provided, which is used to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the terminal device includes a unit for executing the method in the first aspect or any possible implementation of the first aspect.

[0008] In a fourth aspect, a network device is provided, which is used to execute the method in the second aspect or any possible implementation of the second aspect. Specifically, the network device includes a unit for executing the method in the second aspect or any possible implementation of the second aspect.

[0009] In a fifth aspect, a terminal device is provided, the terminal device comprising: a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its implementation manners.

[0010] In a sixth aspect, a network device is provided, the network device comprising: a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or its implementation manner.

[0011] In a seventh aspect, a chip is provided for implementing the method in any one of the first to second aspects or in each of their implementations.

[0012] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes a method as described in any one of the first to second aspects or in each of their implementations.

[0013] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to second aspects or any of their implementations.

[0014] In a ninth aspect, a computer program product is provided, comprising computer program instructions, which enable a computer to execute the method in any one of the first to second aspects or their respective implementations.

[0015] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects or in each of their implementations.

[0016] Based on the above technical solution, the network device can schedule the terminal device to transmit the first PUSCH. When the first PUSCH is associated with the first physical downlink channel, the terminal device can determine the multiplexing method of the first HARQ-ACK information corresponding to the first physical downlink channel on the first PUSCH according to the reception status of the first physical downlink channel, which is conducive to improving system performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1A-Figure 1C It is a schematic diagram of an application scenario provided by an embodiment of the present application.

[0018] Figure 2 It is a schematic diagram of the relationship between the number of HARQ processes and RTT.

[0019] Figure 3 It is a schematic diagram of a wireless communication method provided in an embodiment of the present application.

[0020] Figure 4 It is a schematic block diagram of a terminal device provided in an embodiment of the present application.

[0021] Figure 5 It is a schematic block diagram of a network device provided in an embodiment of the present application.

[0022] Figure 6 It is a schematic block diagram of a communication device provided in another embodiment of the present application.

[0023] Figure 7 It is a schematic block diagram of a chip provided in an embodiment of the present application.

[0024] Figure 8 It is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. For the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0026] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0027] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0028] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0029] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0030] Optionally, the embodiments of the present application may be applied to non-terrestrial communication networks (NTN) systems, and may also be applied to terrestrial communication networks (TN) systems.

[0031] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0032] The terminal device can be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0033] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).

[0034] In the embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, or a wireless terminal device in smart home, etc. The terminal device involved in the embodiment of the present application may also be referred to as a terminal, a user equipment (UE), an access terminal device, a vehicle terminal, an industrial control terminal, a UE unit, a UE station, a mobile station, a mobile station, a remote station, a remote terminal device, a mobile device, a UE terminal device, a wireless communication device, a UE agent, or a UE device, etc. The terminal device may also be fixed or mobile.

[0035] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, 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 clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0036] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.

[0037] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, 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. Optionally, the network device may also be a base station set up in a location such as land or water.

[0038] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0039] For example, Figure 1A The following is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. Figure 1A As shown, the communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices located in the coverage area.

[0040] Figure 1A One network device and two terminal devices are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0041] For example, Figure 1B This is a schematic diagram of another communication system architecture provided by an embodiment of the present application. Figure 1B , including a terminal device 1101 and a satellite 1102, the terminal device 1101 and the satellite 1102 can communicate wirelessly. The network formed between the terminal device 1101 and the satellite 1102 can also be called NTN. Figure 1B In the architecture of the communication system shown, the satellite 1102 may have the function of a base station, and the terminal device 1101 and the satellite 1102 may communicate directly. In the system architecture, the satellite 1102 may be referred to as a network device. Optionally, the communication system may include multiple network devices 1102, and each network device 1102 may include other number of terminal devices within its coverage area, which is not limited in the embodiment of the present application.

[0042] For example, Figure 1C This is a schematic diagram of another communication system architecture provided by an embodiment of the present application. Figure 1C, including terminal equipment 1201, satellite 1202 and base station 1203, terminal equipment 1201 and satellite 1202 can communicate wirelessly, and satellite 1202 and base station 1203 can communicate. The network formed by terminal equipment 1201, satellite 1202 and base station 1203 can also be called NTN. Figure 1C In the architecture of the communication system shown, the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be transferred through the satellite 1202. In this system architecture, the base station 1203 can be called a network device. Optionally, the communication system may include multiple network devices 1203, and each network device 1203 may include other number of terminal devices within its coverage area, which is not limited in the embodiment of the present application.

[0043] It should be noted that Figure 1A-Figure 1C The system to which the present application is applicable is only illustrated in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems, such as 5G communication system, LTE communication system, etc., and the embodiment of the present application does not make specific limitations on this.

[0044] Optionally, Figure 1A-Figure 1C The wireless communication system shown may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but this is not limited in the embodiments of the present application.

[0045] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1A Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0046] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0047] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0048] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0049] In the embodiments of the present application, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0050] In the embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0051] Optionally, the indication information in the embodiment of the present application includes at least one of physical layer signaling such as downlink control information (Downlink Control Information, DCI), radio resource control (Radio Resource Control, RRC) signaling and media access control element (Media Access Control Control Element, MAC CE).

[0052] Optionally, the high-level parameters or high-level signaling in the embodiment 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).

[0053] In order to better understand the embodiments of the present application, the HARQ mechanism and HARQ-ACK feedback mechanism related to the present application are first described.

[0054] HARQ mechanism in NR system

[0055] There are two levels of retransmission mechanisms in the NR system: the Hybrid Automatic Repeat reQuest (HARQ) mechanism of the Media Access Control (MAC) layer and the Automatic Repeat reQuest (ARQ) mechanism of the Radio Link Control (RLC) layer. The retransmission of lost or erroneous data is mainly handled by the HARQ mechanism of the MAC layer and 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.

[0056] HARQ uses a stop-and-wait protocol to send data. In the stop-and-wait protocol, after the sender sends a transport block (TB), it stops and waits for confirmation information. In this way, the sender stops and waits for confirmation after each transmission, which will result in very low user throughput. Therefore, NR uses multiple parallel HARQ processes. When a HARQ process is waiting for confirmation information, the sender can use another HARQ process to continue sending data. These HARQ processes together form a HARQ entity, which combines the stop-and-wait protocol to allow continuous data transmission. 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.

[0057] In some cases, the terminal device has its own HARQ entity for each service cell. Each HARQ entity maintains a set of parallel downlink HARQ processes and a set of parallel uplink HARQ processes. As an example, each uplink and downlink carrier supports a maximum of 16 HARQ processes. The network device can indicate the maximum number of HARQ processes to the terminal device through the semi-static configuration of the Radio Resource Control (RRC) signaling according to the deployment of the network device. Optionally, in some embodiments, if the network device does not provide the corresponding configuration parameters, the default number of HARQ processes for the 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. For the downlink, the Broadcast Control CHannel (BCCH) uses a dedicated broadcast HARQ process. For the uplink, the message 3 (Msg3) transmission in the random process uses HARQ ID 0.

[0058] In some embodiments, for a terminal device that does not support downlink spatial division multiplexing, each downlink HARQ process can only process 1 TB simultaneously; for a terminal device that supports downlink spatial division multiplexing, each downlink HARQ process can process 1 or 2 TB simultaneously. Each uplink HARQ process of the terminal device processes 1 TB simultaneously.

[0059] HARQ is divided into two categories: synchronous and asynchronous in the time domain, and non-adaptive and adaptive in the frequency domain. NR uses asynchronous adaptive HARQ mechanism for both uplink and downlink. 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.

[0060] Combination Figure 2 , taking downlink transmission as an example, the relationship between the number of supported HARQ processes and RTT is explained. Figure 2 As shown, the maximum number of HARQ processes configured for the terminal device is 16. If the RTT is small, for example, less than 16ms, it does not affect the maximum throughput of the terminal device. In other words, if the RTT is less than 16ms, when there is a service to be transmitted, the terminal device can always have a parallel HARQ process for data transmission. Of course, if the RTT is large, for example, much larger than 16ms, then all the HARQ processes of the terminal device may be used for data transmission, and no feedback from the network device may be obtained, resulting in the situation that the terminal device has services to be transmitted but no HARQ process can be used, which in turn affects the data transmission throughput on the terminal device side.

[0061] HARQ-ACK feedback in NR systems

[0062] For terminal devices with downlink services, the network device can schedule the transmission of the physical downlink shared channel (PDSCH) for the terminal device through downlink control information (DCI). The DCI includes indication information of the physical uplink control channel (PUCCH) resources. After receiving the PDSCH, the terminal device feeds back the decoding result of the PDSCH (acknowledgement (ACK) information or negative acknowledgement (Negative Acknowledge, NACK) information) to the network device through the PUCCH resource. The NR system supports dynamic determination of HARQ feedback timing. The network device schedules the terminal device to receive PDSCH through DCI, wherein the DCI includes indication information of uplink feedback resources such as PUCCH resources for transmitting the HARQ-ACK corresponding to the PDSCH.

[0063] As an example, the indication information may include:

[0064] PUCCH resource indicator: used to determine PUCCH resources;

[0065] 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 the PUCCH resource used for HARQ feedback, usually denoted by K1.

[0066] The HARQ feedback timing indication information is used to indicate a value in a HARQ feedback timing set. The HARQ feedback timing set may be preset or configured by a network device. As an example, 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. When the HARQ feedback timing indication information is 001, it indicates the second value in the HARQ feedback timing set, and so on.

[0067] When performing HARQ-ACK feedback, the terminal device 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) HARQ-ACK codebook feedback.

[0068] If the terminal device is configured with Type-1 HARQ-ACK codebook feedback, the Type-1 HARQ-ACK codebook includes HARQ-ACK information corresponding to a candidate PDSCH transmission opportunity within a HARQ-ACK feedback window.

[0069] If the terminal device is configured with Type-2 HARQ-ACK codebook feedback, the Type-2 HARQ-ACK codebook includes HARQ-ACK information corresponding to the scheduled PDSCH within a HARQ-ACK feedback window. Among them, the DCI format for scheduling PDSCH includes a downlink assignment index (DAI) information field:

[0070] DAI count (counter DAI, C-DAI) information, the C-DAI information is used to determine the number of downlink transmissions scheduled by the current DCI in the HARQ feedback window, wherein the C-DAI information is sorted according to the detection opportunity order of the PDCCH.

[0071] If it is a carrier aggregation scenario, the DCI may also include:

[0072] 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.

[0073] If the terminal device is configured with eType-2 HARQ-ACK codebook feedback, the eType-2 HARQ-ACK codebook includes HARQ-ACK information corresponding to the PDSCH of the scheduled group within a HARQ-ACK feedback window. The base station can 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. In other words, the DCI that the base station schedules the UE to receive PDSCH includes indication information of the group index (PDSCH group index) and indication information of the new feedback indication NFI (Newfeedback indicator). This method can include up to 2 groups. When triggering the UE to perform HARQ-ACK feedback, the base station can trigger feedback for one group or trigger feedback for two groups at the same time. Specifically, the DCI information may include an information field for the number of feedback request groups (Number of requested PDSCH group(s)). If the terminal device receives DCI information sent by the network device, and the feedback request group number information field in the DCI information is a preset value, such as set to 1, then the terminal device needs to perform HARQ-ACK feedback for two groups. Alternatively, if the terminal device receives DCI information sent by the network device, and the feedback request group number information field in the DCI information is a preset value, such as set to 0, then the terminal device needs to perform HARQ-ACK feedback for the current scheduling group (i.e., the group to which the DCI-scheduled PDSCH belongs).

[0074] The HARQ feedback window may be determined according to the HARQ feedback timing set or the HARQ feedback timing indication information. With the evolution of the standard, the HARQ feedback timing indication information may indicate not only a valid value but also an invalid value. When the HARQ feedback timing indication information indicates an invalid value, it may indicate that the time domain position of the uplink feedback resource used to feedback the HARQ-ACK information is temporarily uncertain.

[0075] Based on the above information, the terminal device can determine the HARQ-ACK feedback codebook corresponding to the downlink transmission, the PUCCH resources used to feedback the HARQ-ACK information, the time slot for feedback of the HARQ-ACK information, and other information.

[0076] In the NTN system, since the communication distance between the terminal device and the satellite (or network device) is very long, the RTT of signal transmission is very large. In the GEO system, the RTT of signal transmission can be in the order of hundreds of milliseconds, for example, the maximum RTT of signal transmission can be about 600ms. In the LEO system, the RTT of signal transmission can be in 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.

[0077] As an implementation method, the network device can configure one or some downlink HARQ processes of the terminal device to be disabled. For the downlink HARQ process that is configured to be disabled, the network device does not need to receive the HARQ-ACK information fed back by the terminal device for the TB transmitted in the HARQ process, and can reuse the HARQ process for data transmission. 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.

[0078] In the NTN system, for downlink data transmission of a terminal device, the network device may instruct the terminal device to disable HARQ-ACK feedback of one or some downlink HARQ processes. In this case, 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 HARQ-ACK information corresponding to downlink data transmission on the first PUCCH resource, 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.

[0079] Figure 3 Schematic interaction diagram of a wireless communication method 300 provided in an embodiment of the present application. Figure 3 As shown, the method 300 may include at least part of the following:

[0080] S310, the network device schedules a first PUSCH transmission to the terminal device, and a first physical downlink channel is associated with the first PUSCH;

[0081] S320, the terminal device determines whether to multiplex and transmit first hybrid automatic repeat request acknowledgment HARQ-ACK information on the first PUSCH according to the reception status of the first physical downlink channel, wherein the first HARQ-ACK information corresponds to the reception status of the first physical downlink channel.

[0082] Optionally, in some embodiments, recorded as embodiment 1, the first PUSCH transmission may be scheduled by a first DCI, and S310 may include:

[0083] The network device sends a first DCI to the terminal device, where the first DCI is used to schedule a first PUSCH transmission, and the first 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;

[0084] Correspondingly, the terminal device receives the first DCI.

[0085] Further optionally, S320 can be replaced by: the terminal device determines whether to multiplex and transmit the first hybrid automatic repeat request acknowledgment HARQ-ACK information on the first PUSCH according to the reception status of the first DAI information and / or the first physical downlink channel, wherein the first HARQ-ACK information corresponds to the reception status of the first physical downlink channel.

[0086] Optionally, in some embodiments, 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 be other DCI formats including DAI information.

[0087] Optionally, in some embodiments, referred to as Embodiment 2, S310 may include:

[0088] The network device sends scheduling information to the terminal device, where the scheduling information is used to determine the transmission of the first PUSCH.

[0089] Optionally, the scheduling information does not include DCI, or the scheduling information includes a second DCI and the second DCI does not include DAI information.

[0090] That is, in the second embodiment, the first PUSCH may not be DCI-scheduled, 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.

[0091] Combining the first and second embodiments, the first PUSCH may be scheduled by the DCI including the DAI information, or may be scheduled by the DCI not including the DAI information, or may not be scheduled by the DCI.

[0092] Optionally, in some embodiments, the DCI format corresponding to the second DCI includes DCI format 0_0, or may be other DCI formats that do not include DAI information.

[0093] Optionally, in some embodiments, referred to as Embodiment 3, S310 may include:

[0094] The network device sends a first DCI to the terminal device, where the first DCI is used to schedule a first PUSCH transmission, where the first DCI includes first DAI information, where the first DAI information is used to indicate whether to multiplex and transmit first HARQ-ACK information on the first PUSCH, and where a first physical downlink channel is associated with the first PUSCH;

[0095] Correspondingly, the terminal device receives the first DCI.

[0096] Further, S320 can be replaced by: the terminal device determines whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH according to the reception status of the first DAI information and the first physical downlink channel, wherein the first HARQ-ACK information corresponds to the reception status of the first physical downlink channel.

[0097] Alternatively, S320 may be replaced by: the terminal device determines, based on the first DAI information, whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH, wherein the first HARQ-ACK information corresponds to the reception status of the first physical downlink channel.

[0098] Optionally, in this third embodiment, the terminal device is configured with Type-1 HARQ-ACK codebook feedback; or, the first DAI information includes 1 bit.

[0099] Optionally, in this third embodiment, 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 be other DCI formats including DAI information.

[0100] In the scheduling method of the first PUSCH in the above-mentioned Embodiment 2 and Embodiment 3, it can be considered that the number of first physical downlink channels is not associated with the first DAI, that is, the number of first physical downlink channels is not associated with the first DAI, which may include:

[0101] The first PUSCH is not scheduled by DCI or the DCI scheduling the first PUSCH does not include DAI information;

[0102] 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 first physical downlink channels.

[0103] It should be understood that the embodiments of the present application do not specifically limit the scheduling method of the first PUSCH. For example, in some other embodiments, S310 may include: the network device sends a preconfigured grant (Configured Grant, CG) information to the terminal device, and the preconfigured grant information is used to schedule the first PUSCH transmission, wherein the first PUSCH is a preconfigured grant PUSCH. Optionally, the preconfigured grant information may be preconfigured grant configuration information or preconfigured grant activation information.

[0104] When the first PUSCH transmission is scheduled based on any situation and the first PUSCH is associated with a physical downlink channel, it can be determined whether the HARQ-ACK corresponding to the physical downlink channel associated with the first PUSCH is multiplexed on the first PUSCH, and / or the number of bits included in the HARQ-ACK corresponding to the physical downlink channel multiplexed on the first PUSCH can be determined according to the method described in the embodiments of the present application. 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 are described in detail below. It should be understood that, unless otherwise specified, the features described below are applicable to any scheduling method of the first PUSCH, such as the scheduling methods in embodiments one to three.

[0105] Optionally, in some embodiments, the first physical downlink channel associated with the first PUSCH may refer to: a first PUSCH resource corresponding to the first PUSCH and an uplink HARQ-ACK feedback resource corresponding to the first physical downlink channel at least partially overlap in the time domain. Optionally, the uplink HARQ-ACK feedback resource of the first physical downlink channel may be, for example, a first PUCCH resource.

[0106] Below, in combination with specific embodiments, the specific meaning of the first DAI information in the embodiments of the present application is explained, and / or the specific implementation of the first physical downlink channel, and / or whether the terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH, and / or how the terminal device determines the size of the first HARQ-ACK information multiplexed and transmitted on the first PUSCH.

[0107] Implementation method 1:

[0108] The first physical downlink channel includes at least one of the following:

[0109] Associating a physical downlink control channel (PDCCH) with a physical downlink shared channel PDSCH of a first hybrid automatic repeat request HARQ process, wherein the first HARQ process includes a HARQ process corresponding to a first state;

[0110] PDCCH indicating the release of Semi-Persistent Scheduling (SPS) PDSCH;

[0111] PDCCH indicating SCell dormancy state;

[0112] Other PDCCHs corresponding to HARQ-ACK information, or PDCCHs associated with HARQ-ACK information.

[0113] That is, the first physical downlink channel may include a PDSCH that meets a specific condition, which is recorded as a first-type PDSCH. The first-type PDSCH is associated with a PDCCH and is transmitted through a HARQ process corresponding to a first state.

[0114] Optionally, the first HARQ process includes at least one HARQ process.

[0115] Optionally, the PDSCH associated with the PDCCH may include at least one of the following:

[0116] PDSCH scheduled by PDCCH;

[0117] SPS PDSCH scheduled by PDCCH for activating SPS PDSCH transmission.

[0118] Optionally, the first physical downlink channel does not include PDSCH transmission associated with PDCCH and a second HARQ process, wherein the second HARQ process includes a HARQ process corresponding to a second state.

[0119] Optionally, the second HARQ process includes at least one HARQ process.

[0120] Optionally, the first physical downlink channel may include at least one of a first type of PDSCH, a PDCCH indicating an SPS PDSCH release, a PDCCH indicating a secondary cell sleep state, and other PDCCHs corresponding to HARQ-ACK information, and does not include a second type of PDSCH, wherein the second type of PDSCH is associated with the PDCCH and is transmitted through a HARQ process corresponding to the second state.

[0121] Optionally, in the embodiment of the present application, the HARQ process corresponding to the first state includes at least one of the following situations:

[0122] The HARQ process corresponds to an enabled state;

[0123] The HARQ process is not configured with a disabling parameter;

[0124] The HARQ process corresponds to uplink HARQ-ACK feedback.

[0125] That is, it can be considered that the state of the HARQ process is enabled, or the PDSCH transmitted through the HARQ process needs to perform uplink HARQ-ACK feedback.

[0126] Optionally, in the embodiment of the present application, the HARQ process corresponding to the second state includes at least one of the following situations:

[0127] The HARQ process corresponds to a disabled state;

[0128] The HARQ process is configured with a disabling parameter.

[0129] It should be understood that the disabled state is also called the non-enabled state. Optionally, 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.

[0130] Optionally, in implementation method 1, the HARQ process corresponding to the second state does not correspond to uplink HARQ-ACK feedback, that is, HARQ-ACK feedback is not required.

[0131] Optionally, in some embodiments, the network device may configure whether the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback.

[0132] For example, the network device may send first indication information to the terminal device, wherein the first indication information is used to indicate whether the HARQ process corresponding to the second state performs uplink HARQ-ACK feedback. Specifically, in implementation method one, 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 is not necessary to feed back the HARQ-ACK information corresponding to the PDSCH to the network device.

[0133] Optionally, in some embodiments, 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 does not need to perform uplink HARQ-ACK feedback.

[0134] It should be understood that the embodiment of the present application does not specifically limit the number of bits of the first DAI information.

[0135] In some embodiments, the first DAI information is 1 bit, 2 bits, or another number of bits.

[0136] Optionally, in some embodiments, the first DAI information is used to indicate whether to multiplex the first HARQ-ACK information on the first PUSCH. For example, the first DAI information includes 1 bit, and 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 first HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.

[0137] Optionally, in some embodiments, the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH. When the first physical downlink channel is the case in implementation method one, the number of first physical downlink channels indicated by the first DAI information includes 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. Further optionally, the number of first physical downlink channels indicated by the first DAI information does not include the number of the second type of PDSCH. Table 1 shows the meaning of the value of the first DAI information when the first DAI information includes 2 bits in implementation method one, 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. Among them, LSB represents the least significant bit (LSB), and MSB represents the most significant bits (MSB).

[0138] Table 1

[0139]

[0140] Implementation method 2:

[0141] The first physical downlink channel includes at least one of the following situations:

[0142] Associating a PDCCH with a PDSCH transmission of the first HARQ process and associating a PDCCH with a PDSCH transmission of the second HARQ process, wherein the first HARQ process includes a HARQ process corresponding to the first state, and the second HARQ process includes a HARQ process corresponding to the second state;

[0143] PDCCH indicating the release of semi-persistent scheduling SPS PDSCH;

[0144] PDCCH indicating the dormant state of the secondary cell;

[0145] Other PDCCHs corresponding to HARQ-ACK information, or PDCCHs associated with HARQ-ACK information.

[0146] That is, in the second implementation, different from the first implementation, the first physical downlink channel may include a PDSCH transmission associated with the PDCCH and the second HARQ process, wherein the second HARQ process includes a HARQ process corresponding to the second state. In other words, the first physical downlink channel includes the second type of PDSCH.

[0147] Optionally, the first physical downlink channel includes at least one of the first type PDSCH, the second type PDSCH, a PDCCH indicating SPS PDSCH release, a PDCCH indicating a secondary cell sleep state, and other PDCCHs corresponding to HARQ-ACK information.

[0148] Optionally, in implementation mode 2, the HARQ process corresponding to the second state corresponds to uplink HARQ-ACK feedback.

[0149] Optionally, in some embodiments, the network device may configure whether the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback.

[0150] For example, the network device may send a first indication message to the terminal device, wherein the first indication message is used to indicate whether the HARQ process corresponding to the second state performs uplink HARQ-ACK feedback. Specifically, in implementation method 2, the first indication message indicates that the HARQ process corresponding to the second state needs 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 needs to feedback the HARQ-ACK information corresponding to the PDSCH to the network device.

[0151] Optionally, in some embodiments, 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.

[0152] Optionally, in some embodiments, the first DAI information is used to indicate whether to multiplex the transmission of the first HARQ-ACK information on the first PUSCH. For example, the first DAI information includes 1 bit, and 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 first HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.

[0153] Optionally, in some embodiments, the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH. When the first physical downlink channel is the case in implementation method two, the number of first physical downlink channels indicated by the first DAI information includes at least one of the first type of PDSCH, the second type of PDSCH, the PDCCH indicating the release of SPS PDSCH, the PDCCH indicating the sleep state of the secondary cell, and other PDCCHs corresponding to HARQ-ACK information.

[0154] Table 2 shows the meaning of the value of the first DAI information when the first DAI information includes 2 bits and 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 in the second implementation mode.

[0155] Table 2

[0156]

[0157] Optionally, in some embodiments of the present application, the terminal device may determine the meaning of the first DAI information based on the first indication information of the network device, wherein the first indication information is used to indicate whether the HARQ process corresponding to the second state 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 based on the first indication information of the network device, wherein the first indication information is used to indicate the meaning of the first DAI information.

[0158] For example, if the first indication information indicates that the HARQ process corresponding to the second state does not need uplink HARQ-ACK feedback, the meaning of the first DAI information may be the case in implementation method 1. In this case, 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.

[0159] For another example, if the first indication information indicates that the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback, the meaning of the first DAI information may be the case in implementation method 2. In this case, the terminal device may feedback the HARQ feedback information corresponding to the PDSCH transmitted by the HARQ process in the second state to the network device. That is, the HARQ feedback information corresponding to the PDSCH transmitted by the HARQ process in the first state and the second state is fed back to the network device.

[0160] 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 the number of bits included in the first HARQ-ACK information multiplexed on the first PUSCH, based on the aforementioned implementation method 1 and implementation method 2.

[0161] In some embodiments of the present application, the terminal device can determine whether to multiplex and transmit the first HARQ-ACK information corresponding to the first physical downlink channel on the first PUSCH based on the first DAI information, the reception status of the first physical downlink channel, and at least one of the feedback rules.

[0162] Optionally, 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.

[0163] Optionally, the feedback rule includes the first indication information.

[0164] Optionally, in some embodiments, 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 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.

[0165] As an example but not limitation, the first physical downlink channel includes a first type of PDSCH, a PDCCH indicating the release of the SPS PDSCH, and a PDCCH indicating the sleep state of the secondary cell. If the total number of first physical downlink channels associated with the first PUSCH received by the terminal device 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, the terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH.

[0166] As an example but not limitation, the first physical downlink channel includes a first type of PDSCH, a second type of PDSCH, a PDCCH indicating the release of the SPS PDSCH, and a PDCCH indicating the sleep state of the secondary cell. If the total number of first physical downlink channels associated with the first PUSCH received by the terminal device 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, the terminal device multiplexes and transmits the first HARQ-ACK information on the first PUSCH.

[0167] Optionally, in some other embodiments, if the terminal device does not receive the first physical downlink channel, and the terminal device does not need to multiplex the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, and the first DAI information indicates a preset value, then the terminal device does not multiplex the first HARQ-ACK information on the first PUSCH. Optionally, this situation can be applied to the scheduling method of the first PUSCH in the aforementioned embodiment one.

[0168] Optionally, the preset value may be, for example, 4, etc., which is not limited in the present application.

[0169] As an example and not a limitation, the first physical downlink channel includes a first type of PDSCH, a PDCCH indicating the release of the SPS PDSCH, and a PDCCH indicating the sleep state of the secondary cell. If the total number of first physical downlink channels associated with the first PUSCH received by the terminal device is 0 (or, the terminal device has not received any first physical downlink channel), and the terminal device does not need to multiplex 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 the transmission of the first HARQ-ACK information on the first PUSCH.

[0170] As an example and not a limitation, the first physical downlink channel includes a first type of PDSCH, a second type of PDSCH, a PDCCH indicating the release of the SPS PDSCH, and a PDCCH indicating the sleep state of the secondary cell. If the total number of first physical downlink channels associated with the first PUSCH received by the terminal device is 0 (or the terminal device has not received any first physical downlink channel), and the terminal device does not need to multiplex 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 the transmission of the first HARQ-ACK information on the first PUSCH.

[0171] Optionally, in some embodiments, 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, and the first HARQ-ACK information includes the HARQ-ACK information corresponding to the SPS PDSCH.

[0172] Optionally, in some embodiments, if the terminal device does not receive the first physical downlink channel, and the terminal device does not need to multiplex the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, the terminal device does not multiplex the first HARQ-ACK information on the first PUSCH. Optionally, the first PUSCH is not associated with the first DAI information. For example, the first PUSCH is not DCI-scheduled or the DCI that schedules the first PUSCH does not include DAI information. Optionally, the first DAI information associated with the first PUSCH is not used to indicate the number of first physical downlink channels, for example, the first DAI information includes 1 bit.

[0173] As an example but not limitation, the first physical downlink channel includes a first type of PDSCH, a PDCCH indicating the release of the SPS PDSCH, and a PDCCH indicating the sleep state of the secondary cell. If the total number of first physical downlink channels associated with the first PUSCH received by the terminal device is 0 (or the terminal device has not received any first physical downlink channel), and the terminal device does not need to multiplex the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, the terminal device does not multiplex the first HARQ-ACK information on the first PUSCH.

[0174] As an example and not a limitation, the first physical downlink channel includes a first type of PDSCH, a second type of PDSCH, a PDCCH indicating the release of the SPS PDSCH, and a PDCCH indicating the sleep state of the secondary cell. If the total number of first physical downlink channels associated with the first PUSCH received by the terminal device is 0 (or the terminal device has not received any first physical downlink channel), and the terminal device does not need to multiplex the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, the terminal device does not multiplex the first HARQ-ACK information on the first PUSCH.

[0175] Optionally, in some embodiments, the first DAI information is used to indicate whether to multiplex the transmission of 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 the transmission of the first HARQ-ACK information on the first PUSCH, or, 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 the transmission of the first HARQ-ACK information on the first PUSCH, 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, the terminal device multiplexes the transmission of the first HARQ-ACK information on the first PUSCH. Optionally, the first DAI information associated with the first PUSCH is not used to indicate the number of first physical downlink channels, for example, the first DAI information includes 1 bit. Optionally, the terminal device is configured with Type-1 codebook feedback.

[0176] It should be understood that in some embodiments of the present application, since the first HARQ-ACK information includes HARQ-ACK information reflecting the reception status of the first physical downlink channel, when the terminal device does not receive the first physical downlink channel and the terminal device does not need to multiplex 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.

[0177] Optionally, in some embodiments, if the first indication information indicates that the HARQ process corresponding to the second state, such as the disabled state, does not need uplink HARQ-ACK feedback, the terminal device does not multiplex the HARQ-ACK information corresponding to the PDSCH of the HARQ process corresponding to the second state onto the first PUSCH, or the first HARQ-ACK information does not include the HARQ-ACK information corresponding to the PDSCH of the HARQ process corresponding to the second state.

[0178] It should be noted that, for the case in implementation method 1, the first physical downlink channel does not include the PDSCH associated with the PDCCH and the HARQ process corresponding to the second state. In other words, if the terminal device only receives the PDSCH associated with the PDCCH and the HARQ process corresponding to the second state, it is also considered that the first physical downlink channel is not received.

[0179] Optionally, the terminal device determines the bit size included in the first HARQ-ACK information according to the reception status of the first DAI information and / or the first physical downlink channel.

[0180] In some embodiments, when determining that the first HARQ-ACK information needs to be multiplexed in the first PUSCH, the terminal device may determine the bit size included in the first HARQ-ACK information according to the reception status of the first DAI information and / or the first physical downlink channel. As an implementation method, the terminal device may determine the bit size included in the first HARQ-ACK information based on the first DAI information, wherein the first DAI information is used to indicate the total number of first physical downlink channels associated with the first PUSCH. 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 SPS PDSCHs.

[0181] In some embodiments, the first DAI information associated with the first PUSCH includes 2 bits, as shown in Table 1, the value range of the first DAI information Y is 1 to 4, and assuming that the value indicated by the first DAI information received by the terminal device is Y, the terminal device determines the bit size included in the first HARQ-ACK information according to the reception status of the first DAI information and the first physical downlink channel, including: when the total number of first physical downlink channels received by the terminal device is less than or equal to Y, the total number X of first physical downlink channels that need to feedback HARQ-ACK information 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 first physical downlink channels that need to feedback HARQ-ACK information 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+4*2, the total number X of first physical downlink channels that need to feedback HARQ-ACK information is equal to Y+4*2, and so on. Accordingly, the first HARQ-ACK information includes HARQ-ACK information corresponding to X first physical downlink channels. In addition, if the terminal device needs to multiplex and transmit the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, then the first HARQ-ACK information also includes the HARQ-ACK information corresponding to the SPS PDSCH.

[0182] In another implementation, the terminal device may determine the bit size included in the first HARQ-ACK information according to the reception status of the first physical downlink channel, or in other words, the first HARQ-ACK information includes the HARQ-ACK information corresponding to the first physical downlink channel received by the terminal device. Optionally, the first PUSCH is not associated with the first DAI information. For example, the first PUSCH is not DCI-scheduled or the DCI that schedules the first PUSCH does not include DAI information. Optionally, the first DAI information associated with the first PUSCH is not used to indicate the number of the first physical downlink channels, for example, the first DAI information includes 1 bit.

[0183] In another implementation, the terminal device may determine the bit size included in the first HARQ-ACK information according to the reception status of the first DAI information and / or the first physical downlink channel, wherein the first DAI information is used to indicate whether to multiplex the transmission of 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 the transmission of the first HARQ-ACK information on the first PUSCH, and the number of bits included in the first HARQ-ACK information can be determined according to the number of candidate PDSCHs included in the HARQ feedback window. Alternatively, 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, the terminal device multiplexes the transmission of the first HARQ-ACK information on the first PUSCH, wherein the first HARQ-ACK information only includes the HARQ-ACK feedback information of the first physical downlink channel. Optionally, the terminal device is configured with Type-1 codebook feedback. Optionally, the DAI information associated with the first PUSCH includes 1 bit.

[0184] Optionally, if the terminal device needs to multiplex and transmit HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, then the first HARQ-ACK information also includes the HARQ-ACK information corresponding to the SPS PDSCH.

[0185] Optionally, in some other embodiments of the present application, the first PUSCH is associated with a second physical downlink channel, and the method 300 also includes: the terminal device determines whether to multiplex and transmit the second HARQ-ACK information on the first PUSCH and / or the number of bits included in the second HARQ-ACK information multiplexed on the first PUSCH according to the reception status of the second physical downlink channel, wherein the second HARQ-ACK information corresponds to the reception status of the second physical downlink channel.

[0186] Optionally, in some other embodiments of the present application, the first DCI also includes second DAI information, and the second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH.

[0187] Furthermore, the method 300 also includes: the terminal device determines whether to multiplex and transmit the second HARQ-ACK information on the first PUSCH and / or the number of bits included in the second HARQ-ACK information multiplexed on the first PUSCH according to the reception status of the second DAI information and / or the second physical downlink channel, wherein the second HARQ-ACK information corresponds to the reception status of the second physical downlink channel.

[0188] Optionally, the second physical downlink channel associated with the second PUSCH may mean that: a first PUSCH resource corresponding to the first PUSCH and an uplink HARQ-ACK feedback resource of the second physical downlink channel at least partially overlap in the time domain.

[0189] Optionally, 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 the HARQ-ACK feedback based on the TB.

[0190] Optionally, 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 HARQ-ACK feedback based on CBG.

[0191] Optionally, when the first DCI includes first DAI information and second DAI information, the corresponding HARQ-ACK feedback codebook may include two HARQ-ACK feedback sub-codebooks, wherein the first HARQ-ACK feedback sub-codebook includes TB-based feedback, and 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 sizes of the two HARQ-ACK sub-codebooks, respectively.

[0192] Optionally, when at least one of the following conditions is met, the first DCI includes the second DAI information:

[0193] The terminal device is configured to feed back two HARQ-ACK subcodebooks;

[0194] The terminal device is configured with code block group CBG transmission;

[0195] The terminal device is configured with CBG feedback.

[0196] Below, in combination with specific embodiments, 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 HARQ-ACK information on the first PUSCH and / or how the terminal device determines the size of the second HARQ-ACK information multiplexed and transmitted on the first PUSCH are explained.

[0197] Implementation method three:

[0198] Optionally, in some embodiments, the second physical downlink channel includes at least one of the following situations:

[0199] Associating a PDCCH with a PDSCH transmission of a third HARQ process, wherein the third HARQ process includes a HARQ process corresponding to the first state;

[0200] PDCCH indicating SPS PDSCH release;

[0201] PDCCH indicating the dormant state of the secondary cell;

[0202] Other PDCCHs corresponding to HARQ-ACK information, or PDCCHs associated with HARQ-ACK information.

[0203] That is, the second physical downlink channel includes a first type PDSCH, the first type PDSCH is associated with the PDCCH and is transmitted through the third HARQ process corresponding to the first state.

[0204] Optionally, the second physical downlink channel includes a first type PDSCH corresponding to CBG feedback.

[0205] Optionally, the third HARQ process includes at least one HARQ process.

[0206] Optionally, the second physical downlink channel does not include a 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.

[0207] Optionally, the second physical downlink channel does not include a second type of PDSCH corresponding to CBG feedback.

[0208] Optionally, the fourth HARQ process includes at least one HARQ process.

[0209] Optionally, the second physical downlink channel may include at least one of a first type PDSCH, a PDCCH indicating an SPS PDSCH release, a PDCCH indicating a secondary cell sleep state, and other PDCCHs corresponding to HARQ-ACK information, and does not include a second type PDSCH, wherein the second type PDSCH is associated with the PDCCH and is transmitted through a HARQ process corresponding to the second state.

[0210] Optionally, in implementation method three, the HARQ process corresponding to the second state does not correspond to uplink HARQ-ACK feedback.

[0211] It should be understood that the present application does not specifically limit the number of bits of the second DAI information.

[0212] In some embodiments, the second DAI information is 0 bits (ie, does not include the second DAI information), 1 bit, or 2 bits or another number of bits.

[0213] Optionally, in some embodiments, the second DAI information is used to indicate whether to multiplex the second HARQ-ACK information on the first PUSCH. For example, the second DAI information includes 1 bit, and 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 second HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.

[0214] Optionally, in some embodiments, the second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH. When the second physical downlink channel is implemented in the third embodiment, the number of second physical downlink channels indicated by the second DAI information includes 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. Further, optionally, the number of second physical downlink channels indicated by the second DAI information does not include the number of the second type of PDSCH.

[0215] Implementation method 4:

[0216] The second physical downlink channel includes at least one of the following situations:

[0217] Associating a PDCCH with a PDSCH transmission of the third HARQ process and associating a PDCCH with a PDSCH transmission of the fourth HARQ process, wherein 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;

[0218] PDCCH indicating the release of semi-persistent scheduling SPS PDSCH;

[0219] PDCCH indicating the dormant state of the secondary cell;

[0220] Other PDCCHs corresponding to HARQ-ACK information, or PDCCHs associated with HARQ-ACK information.

[0221] That is, in the fourth implementation, unlike the third implementation, the second physical downlink channel may include a PDSCH transmission associated with the PDCCH and the second HARQ process, wherein the second HARQ process includes a HARQ process corresponding to the second state. In other words, the second physical downlink channel includes the second type of PDSCH.

[0222] Optionally, the second physical downlink channel includes at least one of the first type PDSCH, the second type PDSCH, a PDCCH indicating SPS PDSCH release, a PDCCH indicating a secondary cell sleep state, and other PDCCHs corresponding to HARQ-ACK information.

[0223] Optionally, in implementation method four, the HARQ process corresponding to the second state corresponds to uplink HARQ-ACK feedback.

[0224] Optionally, in some embodiments of the present application, the terminal device may determine the meaning of the second DAI information based on the first indication information of the network device, wherein the first indication information is used to indicate whether the HARQ process corresponding to the second state 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 based on the first indication information of the network device, wherein the first indication information is used to indicate the meaning of the second DAI information.

[0225] For example, if the first indication information indicates that the HARQ process corresponding to the second state does not perform uplink HARQ-ACK feedback, the meaning of the second DAI information may be the case in implementation method 3. In this case, 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.

[0226] For another example, if the first indication information indicates that the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback, the meaning of the second DAI information may be the case in implementation method 4. In this case, the terminal device may feedback the HARQ feedback information corresponding to the PDSCH transmitted by the HARQ process in the second state to the network device. That is, the HARQ feedback information corresponding to the PDSCH transmitted by the HARQ process in the first state and the second state is fed back to the network device.

[0227] Furthermore, in some embodiments of the present application, the terminal device may also determine whether to multiplex the second HARQ-ACK information corresponding to the second physical downlink channel on the first PUSCH, and / or determine the number of bits included in the second HARQ-ACK information multiplexed on the first PUSCH.

[0228] It should be understood that in the embodiment of the present application, the specific implementation of the terminal device determining whether to multiplex and transmit the second HARQ-ACK information corresponding to the second physical downlink channel on the first PUSCH can refer to 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 in the aforementioned embodiment. For the sake of brevity, it will not be repeated here.

[0229] It should also be understood that in an embodiment of the present application, the specific implementation of the terminal device determining the number of bits included in the second HARQ-ACK information multiplexed on the first PUSCH can refer to the relevant implementation of the terminal device determining the number of bits included in the first HARQ-ACK information multiplexed on the first PUSCH in the aforementioned embodiment. For the sake of brevity, it will not be repeated here.

[0230] In some other embodiments of the present application, 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 second HARQ-ACK information on the first PUSCH; 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.

[0231] In some other embodiments of the present application, 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 second HARQ-ACK information on the first PUSCH according to the second DAI information; 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 does not multiplex and transmit the second HARQ-ACK information on the first PUSCH.

[0232] In some other embodiments of the present application, if the terminal device is configured with Type-1 codebook feedback, the first DCI does not include the second DAI information.

[0233] In the following, in combination with several typical HARQ-ACK codebook feedback methods, taking the use of the first DCI corresponding to DCI format 0_1 ​​to schedule the first PUSCH transmission as an example, the role of the first DAI information and / or the second DAI information in the first DCI and the specific multiplexing method are explained.

[0234] 1. If the terminal device is configured with Type-1 HARQ-ACK codebook feedback, the first DAI information includes 1 bit, and the second DAI information includes 0 bits (or, the second DAI information is not included).

[0235] The first DAI information is used to indicate whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH.

[0236] For example, 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. When the bit indicates 0, it is used to indicate that the first HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.

[0237] For example, when the first DAI information indicates 1, the terminal device can 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. Alternatively, 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 information only includes the HARQ-ACK feedback information of the first physical downlink channel.

[0238] For example, if the total number of first physical downlink channels associated with the first PUSCH sent by the network device is greater than 1, the network device sets the bit to 1; or, if the network device does not send the first physical downlink channel associated with the first PUSCH or only sends one first physical downlink channel associated with the first PUSCH, the network device sets the bit to 0.

[0239] 2. If the terminal device is configured with Type-2 HARQ-ACK codebook feedback, then:

[0240] Case 1: If a HARQ-ACK codebook is included, or the terminal device is not configured with CBG transmission or 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).

[0241] The first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH.

[0242] 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.

[0243] Case 2: If two HARQ-ACK subcodebooks are included, or the terminal device is configured with CBG transmission or CBG feedback, the first DAI information includes 2 bits for determining the size of the first HARQ-ACK subcodebook, and the second DAI information includes 2 bits for determining the size of the second HARQ-ACK subcodebook.

[0244] The first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH, wherein 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.

[0245] The second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH, wherein 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.

[0246] 3. If the terminal device is configured with eType-2 HARQ-ACK codebook feedback, then:

[0247] Case 1: the first DAI information includes 2 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).

[0248] If HARQ-ACK information of two groups is to be fed back on the first PUSCH, the first DAI information is used to indicate the number of first physical downlink channels of the corresponding first group (or group 0) associated with the first PUSCH.

[0249] If HARQ-ACK information of a group is to be fed back on the first PUSCH, the first DAI information is used to indicate the number of first physical downlink channels of the corresponding scheduling group (eg, group 0 or group 1) associated with the first PUSCH.

[0250] Case 2: The first DAI information includes 2 DAI information, 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).

[0251] The first DAI information in the first DAI information is used to indicate the number of first physical downlink channels of the first group associated with the first PUSCH. The second DAI information in the first DAI information is used to indicate the number of first physical downlink channels of the second group associated with the first PUSCH.

[0252] Case 3: CBG feedback is configured, the first DAI information includes 2 bits, and the second DAI information includes 2 bits.

[0253] If HARQ-ACK information of two groups is to be fed back on the first PUSCH, the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH and corresponding to the first group and corresponding to 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.

[0254] If the HARQ-ACK information of a group is to be fed back on the first PUSCH, the first DAI information is used to indicate the number of first physical downlink channels of the corresponding scheduling group (e.g., group 0 or group 1) associated with the first PUSCH and corresponding to the feedback of the TB. The second DAI information is used to indicate the number of second physical downlink channels of the corresponding scheduling group (e.g., group 0 or group 1) associated with the first PUSCH and corresponding to the feedback of the CBG.

[0255] Case 4: CBG feedback is configured, the first DAI information includes 2 DAI information, each DAI information includes 2 bits, and the second DAI information includes 2 DAI information, each DAI information includes 2 bits.

[0256] The first DAI information in the first DAI information is used to indicate the number of first physical downlink channels corresponding to the first group and corresponding to TB feedback associated with the first PUSCH.

[0257] The second DAI information in the first DAI information is used to indicate the number of first physical downlink channels corresponding to the second group and corresponding to TB feedback associated with the first PUSCH.

[0258] The first DAI information in the second DAI information is used to indicate the number of second physical downlink channels corresponding to the first group and corresponding to CBG feedback associated with the first PUSCH.

[0259] 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 CBG feedback associated with the first PUSCH.

[0260] As an example but not limitation, when the terminal device is configured with eType-2 HARQ-ACK codebook feedback, the size of the DAI information in DCI format 0_1 ​​includes one of the cases shown in Table 3:

[0261] Table 3

[0262]

[0263] In the example of Table 3, a0 or b0 represents the least significant bit (LSB) in the DAI information, and a3 or b3 represents the most significant bits (MSB) in the DAI information.

[0264] Optionally, if the first DCI includes the first DAI information, and the meaning of the first DAI information is the case in the aforementioned implementation method 1, S320 may include:

[0265] If the terminal device is not configured with CBG transmission (for example, the terminal device is not provided with the high-level parameter PDSCH-CodeBlockGroupTransmission), and the terminal device receives a first DCI in a first DCI format that schedules a first PUSCH transmission and includes first DAI information, and the value of the first DAI information is a preset value, and the terminal device does not receive a PDCCH received by the PDSCH of the corresponding enabled HARQ process scheduled by DCI format 1_0 or DCI format 1_1 in the PDCCH detection opportunity corresponding to the HARQ feedback window, or does not receive a PDCCH indicating the release of the SPS PDSCH on any serving cell, and the terminal device does not have the HARQ-ACK information received by the corresponding SPS PDSCH multiplexed on the first PUSCH, then the terminal device does not multiplex the first HARQ-ACK information on the first PUSCH; and / or

[0266] If a terminal device receives a first DCI in a first DCI format scheduled for a first PUSCH transmission and including first DAI information corresponding to a group number, and the value of the first DAI information is a preset value, and the terminal device has not received a PDCCH received by a PDSCH corresponding to the group number and an enabled HARQ process scheduled by any DCI format, and the terminal device has not received a request for feedback of HARQ-ACK information corresponding to the group number indicated by any DCI format, then the terminal device does not multiplex the HARQ-ACK information corresponding to the group number on the first PUSCH.

[0267] Optionally, if the first DCI includes the first DAI information, and the meaning of the first DAI information is the case in the aforementioned implementation method 2, S320 may include:

[0268] If the terminal device is not configured with CBG transmission (for example, the terminal device is not provided with the high-level parameter PDSCH-CodeBlockGroupTransmission), and the terminal device receives a first DCI in a first DCI format scheduled for a first PUSCH transmission and including first DAI information, and the value of the first DAI information is a preset value, and the terminal device does not receive a PDCCH for PDSCH reception of the corresponding enabled and disabled HARQ processes scheduled by DCI format 1_0 or DCI format 1_1 in the PDCCH detection opportunity corresponding to the HARQ feedback window, or does not receive a PDCCH indicating the release of the SPS PDSCH on any serving cell, and the terminal device does not have HARQ-ACK information received corresponding to the SPS PDSCH multiplexed on the first PUSCH, then the terminal device does not multiplex the first HARQ-ACK information on the first PUSCH; and / or

[0269] If a terminal device receives a first DCI in a first DCI format scheduled for a first PUSCH transmission and includes first DAI information corresponding to a group number, and the value of the first DAI information is a preset value, and the terminal device has not received any PDSCH reception of a HARQ process in an enabled and disabled state scheduled by any DCI format corresponding to the group number, and the terminal device has not received any DCI format indicated request for feedback of HARQ-ACK information corresponding to the group number, then the terminal device does not multiplex the HARQ-ACK information corresponding to the group number on the first PUSCH.

[0270] Optionally, if the first DCI includes the first DAI information and the second DAI information, and the meaning of the first DAI information and the meaning of the second DAI information are respectively the cases in the aforementioned implementation method one and implementation method three, in some specific embodiments, S320 may include:

[0271] If the terminal device is configured with CBG transmission (for example, the terminal device is provided with a high-level parameter PDSCH-CodeBlockGroupTransmission), and the terminal device schedules the first PUSCH transmission and receives the first DCI in the first DCI format including the first DAI information and the second DAI information, and the first DAI information value is a preset value or the second DAI information value is a preset value, and the terminal device does not receive the corresponding DCI format 1_0 or DCI format 1_1 scheduled corresponding enabled HARQ process in the PDCCH detection opportunity corresponding to the HARQ feedback window. The PDCCH received, or the PDCCH indicating the release of the SPS PDSCH on any service cell, or the PDCCH of the DCI format 1_1 indicating SCell dormancy, and the terminal device does not have the corresponding SPS PDSCH received HARQ-ACK information multiplexed on the first PUSCH, then the terminal device does not multiplex the corresponding HARQ-ACK information in the first subcodebook or the second subcodebook on the first PUSCH.

[0272] Optionally, if the first DCI includes the first DAI information and the second DAI information, and the meaning of the first DAI information and the meaning of the second DAI information are respectively the cases in the aforementioned implementation method 2 and implementation method 4, in some specific embodiments, S320 may include:

[0273] If the terminal device is configured with CBG transmission (for example, the terminal device is provided with a high-level parameter PDSCH-CodeBlockGroupTransmission), and the terminal device receives a first DCI in a first DCI format that is scheduled for a first PUSCH transmission and includes first DAI information and second DAI information, and the first DAI information takes a preset value or the second DAI information takes a preset value, and the terminal device does not receive the corresponding DCI format 1_0 or DCI format 1_1 scheduled corresponding to the enabled and disabled HARQ processes in the PDCCH detection opportunity corresponding to the HARQ feedback window. The PDCCH received, or the PDCCH indicating the release of the SPS PDSCH on any service cell, or the PDCCH of the DCI format 1_1 indicating SCelldormancy, and the terminal device does not have the HARQ-ACK information received by the corresponding SPS PDSCH multiplexed on the first PUSCH, then the terminal device does not multiplex the HARQ-ACK information in the corresponding first subcodebook or second subcodebook on the first PUSCH.

[0274] Therefore, in some embodiments of the present application, when a terminal device is configured with a certain HARQ process 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 determine whether it is necessary to multiplex the transmission of HARQ-ACK information on the PUSCH or determine the size of the HARQ-ACK information multiplexed on the PUSCH according to the value of the DAI field in the DCI that schedules the PUSCH resource and / or the reception status of the physical downlink channel. The number of downlink transmissions indicated by the DAI field may not include the number of PDSCHs transmitted using a non-enabled HARQ process, thereby reducing the overhead on the PUSCH for transmitting uplink control information.

[0275] Combination of the above Figure 3 , describes in detail the method embodiment of the present application, and the following is combined with Figures 4 to 8 , the device embodiments of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and similar descriptions can refer to the method embodiments.

[0276] Figure 4 FIG. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. Figure 4 As shown, the terminal device 400 includes:

[0277] The processing unit 410 is used to determine whether to transmit a first physical uplink shared channel PUSCH, wherein the first PUSCH is associated with a first physical downlink channel; and determine whether to multiplex and transmit a first hybrid automatic repeat request acknowledgment HARQ-ACK information on the first PUSCH according to the reception status of the first physical downlink channel, wherein the first HARQ-ACK information corresponds to the reception status of the first physical downlink channel.

[0278] Optionally, in some embodiments, the first physical downlink channel includes at least one of the following:

[0279] Associating a physical downlink control channel PDCCH with a physical downlink shared channel PDSCH transmission of a first hybrid automatic repeat request HARQ process, wherein the first HARQ process includes a HARQ process corresponding to a first state;

[0280] PDCCH indicating the release of semi-persistent scheduling SPS PDSCH;

[0281] PDCCH indicating the dormant state of the secondary cell;

[0282] PDCCH associated with HARQ-ACK information.

[0283] Optionally, in some embodiments, the first physical downlink channel does not include a PDSCH transmission associated with a PDCCH and a second HARQ process, wherein the second HARQ process includes a HARQ process corresponding to a second state.

[0284] Optionally, in some embodiments, the first physical downlink channel includes at least one of the following situations:

[0285] Associating a PDCCH with a PDSCH transmission of the first HARQ process and associating a PDCCH with a PDSCH transmission of the second HARQ process, wherein the first HARQ process includes a HARQ process corresponding to the first state, and the second HARQ process includes a HARQ process corresponding to the second state;

[0286] PDCCH indicating the release of semi-persistent scheduling SPS PDSCH;

[0287] PDCCH indicating the dormant state of the secondary cell;

[0288] PDCCH associated with HARQ-ACK information.

[0289] Optionally, in some embodiments, the first PUSCH is associated with a first physical downlink channel, including:

[0290] 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.

[0291] Optionally, in some embodiments, the first physical downlink channel corresponds to a HARQ-ACK feedback method based on a transport block TB.

[0292] Optionally, in some embodiments, the first PUSCH is associated with a second physical downlink channel, and the processing unit 410 is further used to determine whether to multiplex and transmit second hybrid automatic repeat request acknowledgment HARQ-ACK information on the first PUSCH according to the reception status of the second physical downlink channel, wherein the second HARQ-ACK information corresponds to the reception status of the second physical downlink channel.

[0293] Optionally, in some embodiments, the second physical downlink channel includes: a 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.

[0294] Optionally, in some embodiments, the second physical downlink channel does not include a 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.

[0295] Optionally, in some embodiments, the second physical downlink channel includes: a PDSCH transmission associated with the PDCCH and the third HARQ process and a PDSCH transmission associated with the PDCCH and the fourth HARQ process, wherein 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.

[0296] Optionally, in some embodiments, the first PUSCH is associated with a second physical downlink channel, including:

[0297] 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.

[0298] Optionally, in some embodiments, the second physical downlink channel corresponds to a HARQ-ACK feedback method based on code block group CBG.

[0299] Optionally, in some embodiments, the terminal device 400 further includes:

[0300] A communication unit 420 is 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 first downlink allocation indication DAI information, and the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH;

[0301] 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 reception status of the first DAI information and the first physical downlink channel.

[0302] Optionally, in some embodiments, the DCI format corresponding to the first DCI includes at least one of the following: DCI format 0_1 ​​and DCI format 0_2.

[0303] Optionally, in some embodiments, the processing unit 410 is further configured to:

[0304] 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 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 according to the first DAI information.

[0305] Optionally, in some embodiments, the processing unit 410 is also used for: when the terminal device does not receive the first physical downlink channel, and the terminal device does not need to multiplex the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, and the first DAI information indicates a preset value, the first HARQ-ACK information is not multiplexed on the first PUSCH.

[0306] Optionally, in some embodiments, the first PUSCH is also associated with a second physical downlink channel, the first DCI also includes second DAI information, the second DAI information is used to indicate the number of the second physical downlink channels associated with the first PUSCH, and the processing unit 410 is further used to:

[0307] According to the reception status of the second DAI information and the second physical downlink channel, determine whether to multiplex and transmit second HARQ-ACK information on the first PUSCH, wherein the second HARQ-ACK information corresponds to the reception status of the second physical downlink channel.

[0308] Optionally, in some embodiments, the processing unit 410 is further used to: when the number of the second physical downlink channels received by the terminal device is greater than or equal to 1, multiplex and transmit the second HARQ-ACK information on the first PUSCH according to the second DAI information.

[0309] Optionally, in some embodiments, the processing unit 410 is further used to: when the terminal device does not receive the second physical downlink channel and the second DAI information indicates the preset value, non-multiplexed transmission of the second HARQ-ACK information on the first PUSCH.

[0310] Optionally, in some embodiments, the preset value is 0 or 4.

[0311] Optionally, in some embodiments, the processing unit 410 is further configured to:

[0312] The transmission of the first PUSCH is determined according to scheduling information sent by a network device, wherein the scheduling information does not include DCI, or the scheduling information includes a second DCI and the second DCI does not include DAI information.

[0313] Optionally, in some embodiments, the DCI format corresponding to the second DCI includes DCI format 0_0.

[0314] Optionally, in some embodiments, the processing unit 410 is further configured to:

[0315] 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 the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, the first HARQ-ACK information is multiplexed and transmitted on the first PUSCH.

[0316] Optionally, in some embodiments, the processing unit 410 is further configured to:

[0317] When 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 HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.

[0318] Optionally, in some embodiments, the processing unit 410 is further configured to:

[0319] If the number of the second physical downlink channels received by the terminal device is greater than or equal to 1, the second HARQ-ACK information is multiplexed and transmitted on the first PUSCH.

[0320] Optionally, in some embodiments, the processing unit 410 is further configured to:

[0321] If the terminal device does not receive the second physical downlink channel, the second HARQ-ACK information is not multiplexed and transmitted on the first PUSCH.

[0322] Optionally, in some embodiments, the HARQ process corresponding to the first state includes at least one of the following situations:

[0323] The HARQ process corresponds to an enabled state;

[0324] The HARQ process is not configured with a disabling parameter;

[0325] The HARQ process corresponds to uplink HARQ-ACK feedback.

[0326] Optionally, in some embodiments, the HARQ process corresponding to the second state includes at least one of the following situations:

[0327] The HARQ process corresponds to a disabled state;

[0328] The HARQ process is configured with a disabling parameter.

[0329] Optionally, in some embodiments, the processing unit 410 is further configured to:

[0330] Determine, according to the first indication information sent by the network device, that the HARQ process corresponding to the second state does not perform uplink HARQ-ACK feedback, wherein the first indication information is used to indicate whether the HARQ process corresponding to the second state performs uplink HARQ-ACK feedback.

[0331] Optionally, in some embodiments, the processing unit 410 is further configured to:

[0332] Determine, according to the first indication information sent by the network device, that the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback, wherein the first indication information is used to indicate whether the HARQ process corresponding to the second state performs uplink HARQ-ACK feedback.

[0333] Optionally, in some embodiments, the 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 processing unit may be one or more processors.

[0334] It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 400 are respectively to implement Figure 3 For the sake of brevity, the corresponding process of the terminal device in the method 300 is not repeated here.

[0335] Figure 5 It is a schematic block diagram of a network device according to an embodiment of the present application. Figure 5 The network device 500 includes:

[0336] The communication unit 510 is used to send first downlink control information DCI to the terminal device, where the first DCI is used to schedule the transmission of the first physical uplink shared channel PUSCH. The first 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.

[0337] Optionally, in some embodiments, the first physical downlink channel includes at least one of the following:

[0338] Associating a physical downlink control channel PDCCH with a physical downlink shared channel PDSCH transmission of a first hybrid automatic repeat request HARQ process, wherein the first HARQ process includes a HARQ process corresponding to a first state;

[0339] PDCCH indicating the release of semi-persistent scheduling SPS PDSCH;

[0340] PDCCH indicating the dormant state of the secondary cell;

[0341] PDCCH associated with HARQ-ACK information.

[0342] Optionally, in some embodiments, the first physical downlink channel does not include a PDSCH transmission associated with a PDCCH and a second HARQ process, wherein the second HARQ process includes a HARQ process corresponding to a second state.

[0343] Optionally, in some embodiments, the first physical downlink channel includes at least one of the following situations:

[0344] Associating a PDCCH with a PDSCH transmission of the first HARQ process and associating a PDCCH with a PDSCH transmission of the second HARQ process, wherein the first HARQ process includes a HARQ process corresponding to the first state, and the second HARQ process includes a HARQ process corresponding to the second state;

[0345] PDCCH indicating the release of semi-persistent scheduling SPS PDSCH;

[0346] PDCCH indicating the dormant state of the secondary cell;

[0347] PDCCH associated with HARQ-ACK information.

[0348] Optionally, in some embodiments, the first DCI also includes second DAI information, and the second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH.

[0349] Optionally, in some embodiments, the second physical downlink channel includes: a 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.

[0350] Optionally, in some embodiments, the second physical downlink channel does not include a 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.

[0351] Optionally, in some embodiments, the second physical downlink channel includes: a PDSCH transmission associated with the PDCCH and the third HARQ process and a PDSCH transmission associated with the PDCCH and the fourth HARQ process, wherein 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.

[0352] Optionally, in some embodiments, the terminal device is configured to feed back two HARQ-ACK subcodebooks; or,

[0353] The terminal device is configured with code block group CBG transmission; or,

[0354] The terminal device is configured with CBG feedback.

[0355] Optionally, in some embodiments, the HARQ process corresponding to the first state includes at least one of the following situations:

[0356] The HARQ process corresponds to an enabled state;

[0357] The HARQ process is not configured with a disabling parameter;

[0358] The HARQ process corresponds to uplink HARQ-ACK feedback.

[0359] Optionally, in some embodiments, the HARQ process corresponding to the second state includes at least one of the following situations:

[0360] The HARQ process corresponds to a disabled state;

[0361] The HARQ process is configured with a disabling parameter.

[0362] Optionally, in some embodiments, the communication unit 510 is further configured to:

[0363] Send first indication information to the terminal device, wherein the first indication information indicates that the HARQ process corresponding to the second state does not perform uplink HARQ-ACK feedback.

[0364] Optionally, in some embodiments, the communication unit 510 is further configured to:

[0365] Send first indication information to the terminal device, wherein the first indication information indicates that the HARQ process corresponding to the second state needs to perform uplink HARQ-ACK feedback.

[0366] Optionally, in some embodiments, the second DAI information is used to indicate the number of second physical downlink channels associated with the first PUSCH, wherein the first PUSCH resources 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.

[0367] Optionally, in some embodiments, the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH, wherein the first PUSCH resources corresponding to the first PUSCH and the uplink HARQ-ACK feedback resources corresponding to the first physical downlink channel at least partially overlap in the time domain.

[0368] Optionally, in some embodiments, the DCI format corresponding to the first DCI includes at least one of the following: DCI format 0_1 ​​and DCI format 0_2.

[0369] Optionally, in some embodiments, the network device 500 further includes:

[0370] A processing unit is used to determine a value of the first DAI information and / or a value of the second DAI information according to the conditions of the scheduled first physical downlink channel and / or the second physical downlink channel.

[0371] Optionally, in some embodiments, the 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 processing unit may be one or more processors.

[0372] It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the network device 500 are respectively to implement Figure 3 For the sake of brevity, the corresponding processes of the network device in the method 300 are not repeated here.

[0373] Figure 6 It is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. Figure 6 The communication device 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0374] Alternatively, if Figure 6 As shown, 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 method in the embodiment of the present application.

[0375] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0376] Alternatively, if Figure 6 As shown, 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 information or data sent by other devices.

[0377] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of the antennas may be one or more.

[0378] Optionally, the communication device 600 may specifically be a network device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0379] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device of an embodiment 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 embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0380] Figure 7 It is a schematic structural diagram of the chip of an embodiment of the present application. Figure 7 The chip 700 shown includes a processor 710, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0381] Alternatively, if Figure 7 As shown, 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 method in the embodiment of the present application.

[0382] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0383] Optionally, 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 obtain information or data sent by other devices or chips.

[0384] Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0385] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0386] Optionally, 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 the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0387] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0388] Figure 8 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. Figure 8 As shown, the communication system 900 includes a terminal device 910 and a network device 920 .

[0389] Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0390] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media 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.

[0391] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0392] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), 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 link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, 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.

[0393] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0394] Optionally, 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. For the sake of brevity, they are not repeated here.

[0395] Optionally, 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 the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0396] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0397] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0398] Optionally, 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 enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0399] The embodiment of the present application also provides a computer program.

[0400] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0401] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0402] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0403] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0404] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0405] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0406] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

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

[0408] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method of wireless communication, It is characterized in that include: The 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 terminal device determines, according to a reception condition of the first physical downlink channel, whether to multiplex and transmit first hybrid automatic repeat request acknowledgment HARQ-ACK information on the first PUSCH, wherein the first HARQ-ACK information corresponds to a reception condition of the first physical downlink channel; The first physical downlink channel includes at least one of the following: Associating a physical downlink control channel PDCCH with a physical downlink shared channel PDSCH transmission of a first hybrid automatic repeat request HARQ process, wherein the first HARQ process includes a HARQ process corresponding to a first state; PDCCH associated with HARQ-ACK information; The first physical downlink channel does not include PDSCH transmission associated with the PDCCH and the second HARQ process, and the second HARQ process includes a HARQ process corresponding to the second state; The HARQ process corresponding to the first state includes: the HARQ process corresponding to the enabled state; The HARQ process corresponding to the second state includes: the HARQ process corresponds to a disabled state.

2. The method according to claim 1, It is characterized in that The first PUSCH is associated with a second physical downlink channel, and the method further includes: The terminal device determines, according to the reception status of the second physical downlink channel, whether to multiplex and transmit second hybrid automatic repeat request acknowledgment HARQ-ACK information on the first PUSCH, wherein the second HARQ-ACK information corresponds to the reception status of the second physical downlink channel; The second physical downlink channel includes a PDSCH transmission associated with a PDCCH and a third HARQ process, and 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 the PDCCH and the fourth HARQ process, and the fourth HARQ process includes the HARQ process corresponding to the second state.

3. The method according to claim 1 or 2, It is characterized in that The terminal device determines to transmit a first PUSCH, including: The terminal device receives 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 first downlink allocation indication DAI information, and the first DAI information is used to indicate the number of first physical downlink channels associated with the first PUSCH; The terminal device determines, according to a reception condition of the first physical downlink channel, whether to multiplex and transmit first hybrid automatic repeat request acknowledgment HARQ-ACK information on the first PUSCH, including: The terminal device determines whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH according to the reception status of the first DAI information and the first physical downlink channel.

4. The method according to claim 3, It is characterized in that The terminal device determines, according to the first DAI information and the reception status of the first physical downlink channel, whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH, including: 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; or, When the terminal device does not receive the first physical downlink channel, and the terminal device does not need to multiplex the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, and the first DAI information indicates a preset value, the terminal device does not multiplex the first HARQ-ACK information on the first PUSCH; wherein the preset value is 0 or 4.

5. The method according to claim 3, It is characterized in that The first PUSCH is also associated with a second physical downlink channel, the first DCI also includes second DAI information, and the second DAI information is used to indicate the number of the second physical downlink channels associated with the first PUSCH, and the method further includes: The terminal device determines whether to multiplex and transmit second HARQ-ACK information on the first PUSCH according to the second DAI information and the reception status of the second physical downlink channel, wherein the second HARQ-ACK information corresponds to the reception status of the second physical downlink channel.

6. The method according to claim 5, It is characterized in that The terminal device determines, according to the reception status of the second DAI information and the second physical downlink channel, whether to multiplex and transmit the second HARQ-ACK information on the first PUSCH, including: When 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 second HARQ-ACK information on the first PUSCH according to the second DAI information; or, When the terminal device does not receive the second physical downlink channel and the second DAI information indicates the preset value, the terminal device does not multiplex the second HARQ-ACK information on the first PUSCH; wherein the preset value is 0 or 4.

7. The method according to claim 1 or 2, It is characterized in that The terminal device determines to transmit a first PUSCH, including: The terminal device determines to transmit the first PUSCH according to scheduling information sent by a network device, wherein the scheduling information does not include DCI, or the scheduling information includes a second DCI and the second DCI does not include DAI information.

8. The method according to claim 1, It is characterized in that The terminal device determines, according to a reception condition of the first physical downlink channel, whether to multiplex and transmit the first HARQ-ACK information on the first PUSCH, including: 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 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; or, When the terminal device does not receive the first physical downlink channel and the terminal device does not need to multiplex transmit the HARQ-ACK information corresponding to the SPS PDSCH on the first PUSCH, the terminal device does not multiplex transmit the first HARQ-ACK information on the first PUSCH.

9. The method according to claim 2, It is characterized in that The terminal device determines, according to a reception condition of the second physical downlink channel, whether to multiplex and transmit second HARQ-ACK information on the first PUSCH, including: 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 second HARQ-ACK information on the first PUSCH; or, If the terminal device does not receive the second physical downlink channel, the terminal device does not multiplex the second HARQ-ACK information on the first PUSCH.

10. A method of wireless communication, It is characterized in that include: The network device sends first downlink control information DCI to the terminal device, where the first DCI is used to schedule the transmission of a first physical uplink shared channel PUSCH, and the first 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; The first physical downlink channel includes at least one of the following: Associating a physical downlink control channel PDCCH with a physical downlink shared channel PDSCH transmission of a first hybrid automatic repeat request HARQ process, wherein the first HARQ process includes a HARQ process corresponding to a first state; PDCCH associated with HARQ-ACK information; The first physical downlink channel does not include a PDSCH transmission associated with a PDCCH and a second HARQ process, and the second HARQ process includes a HARQ process corresponding to a second state; The HARQ process corresponding to the first state includes: the HARQ process corresponding to the enabled state; The HARQ process corresponding to the second state includes: the HARQ process corresponds to a disabled state.

11. The method according to claim 10, It is characterized in that The first DCI also 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 a PDSCH transmission associated with a PDCCH and a third HARQ process, and the third HARQ process includes a HARQ process corresponding to the first state; The second physical downlink channel does not include a PDSCH transmission associated with a PDCCH and a fourth HARQ process, 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 with code block group CBG transmission; or, The terminal device is configured with CBG feedback; or, The second physical downlink channel corresponds to a HARQ-ACK feedback method based on a code block group CBG.

12. The method according to claim 10 or 11, It is characterized in that The method further comprises: The network device sends first indication information to the terminal device, wherein the first indication information indicates that the HARQ process corresponding to the second state does not perform uplink HARQ-ACK feedback.

13. A terminal device, It is characterized in that include: A processing unit, 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 Determine, according to a reception condition of the first physical downlink channel, whether to multiplex and transmit first hybrid automatic repeat request acknowledgment HARQ-ACK information on the first PUSCH, wherein the first HARQ-ACK information corresponds to a reception condition of the first physical downlink channel; The first physical downlink channel includes at least one of the following: Associating a physical downlink control channel PDCCH with a physical downlink shared channel PDSCH transmission of a first hybrid automatic repeat request HARQ process, wherein the first HARQ process includes a HARQ process corresponding to a first state; PDCCH associated with HARQ-ACK information; The first physical downlink channel does not include PDSCH transmission associated with the PDCCH and the second HARQ process, and the second HARQ process includes a HARQ process corresponding to the second state; The HARQ process corresponding to the first state includes: the HARQ process corresponding to the enabled state; The HARQ process corresponding to the second state includes: the HARQ process corresponds to a disabled state.

14. A network device, It is characterized in that include: A communication unit, configured to send first downlink control information DCI to a terminal device, where the first DCI is used to schedule transmission of a first physical uplink shared channel PUSCH, where the first 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; The first physical downlink channel includes at least one of the following: Associating a physical downlink control channel PDCCH with a physical downlink shared channel PDSCH transmission of a first hybrid automatic repeat request HARQ process, wherein the first HARQ process includes a HARQ process corresponding to a first state; PDCCH associated with HARQ-ACK information; The first physical downlink channel does not include a PDSCH transmission associated with a PDCCH and a second HARQ process, and the second HARQ process includes a HARQ process corresponding to a second state; The HARQ process corresponding to the first state includes: the HARQ process corresponding to the enabled state; The HARQ process corresponding to the second state includes: the HARQ process corresponds to a disabled state.

Images