HARQ-ACK Information Feedback Method and Device

Abstract

This application provides a HARQ-ACK information feedback method and apparatus. The DCI sent by the network device to the terminal device activates semi-static scheduling and also dynamically schedules downlink data. The timing offset value from the PDSCH to the HARQ feedback indicated by the DCI can simultaneously indicate the time-domain position of the PUCCH carrying the HARQ-ACK information corresponding to the semi-static scheduled data, as well as the time-domain position of the PUCCH carrying the HARQ-ACK information corresponding to the aforementioned downlink data. Through this scheme, the time-domain position of the PUCCH carrying the HARQ-ACK information corresponding to the semi-static scheduled data determined by the terminal device is valid, thereby ensuring timely feedback of the HARQ-ACK information corresponding to the semi-static scheduled data and guaranteeing the transmission performance of the semi-static scheduled data.

Description

Technical Field

[0001] This application relates to the field of wireless communication, and more specifically, to a HARQ-ACK information feedback method and apparatus. Background Technology

[0002] Normally, the physical uplink control channel (PUCCH), which carries uplink control information, is transmitted on a fixed cell by default. When the time domain position of this PUCCH overlaps with the downlink symbol, the PUCCH can only be postponed to the next slot, which increases the transmission delay of the uplink control information.

[0003] To address this issue, the 3rd Generation Partnership Project (3GPP) Release 17 (R17) Rel-17 standard introduced the PUCCH cell switching feature. In this feature, the downlink control information (DCI) can include a 1-bit PUCCH cell indication field. This field indicates whether the PUCCH carrying the hybrid automatic repeat request acknowledgment (HARQ-ACK) message is on the primary cell (PCell) or the secondary cell (SCell), also known as the PUCCH switching secondary cell. When the DCI indicates that the PUCCH is on the PCell, the value of K1 is determined based on the K1 set of the PCell; when it indicates that the PUCCH is on the SCell, the value of K1 is determined based on the K1 set of the SCell.

[0004] If the DCI activates semi-persistent scheduling (SPS) while dynamically scheduling downlink data, the terminal equipment needs to provide HARQ-ACK information not only for the dynamically scheduled downlink data but also for the semi-persistently scheduled physical downlink shared channel (PDSCH). Furthermore, due to the introduction of PUCCH cell handover features, the PUCCH carrying the HARQ-ACK information for dynamically scheduled downlink data and the PUCCH carrying the HARQ-ACK information for SPS may not be in the same cell. Therefore, the time-domain location of the PUCCH carrying the HARQ-ACK information for the PDSCH of SPS, determined by the user equipment (UE), may be invalid, thus affecting data transmission performance. Summary of the Invention

[0005] This application provides a HARQ-ACK information feedback method and apparatus to address the problem that the time-domain location of the PUCCH carrying the HARQ-ACK information of the PDSCH that is determined by the UE after the introduction of PUCCH cell handover features may be invalid.

[0006] Firstly, a HARQ-ACK information feedback method is provided. This method can be executed by a terminal device or by a component of the terminal device. The method includes: the terminal device receiving downlink control information from a network device. The downlink control information is used to schedule downlink data. The downlink control information includes first indication information, which instructs the terminal device to send first HARQ-ACK information via a first PUCCH in a first cell. The first HARQ-ACK information is the HARQ-ACK information corresponding to the downlink data. The downlink control information is also used to activate semi-static scheduling. The downlink control information also includes second indication information, which indicates a first value. The first value is a value in a first set, and the second set includes the first value. The terminal device determines the temporal location of a second PUCCH based on the first value. The terminal device sends second HARQ-ACK information via a second PUCCH in a second cell. The second HARQ-ACK information is the HARQ-ACK information corresponding to the semi-statically scheduled data. The values ​​in the first set indicate the time slot offset between the PDSCH carrying downlink data and the first PUCCH carrying the first HARQ-ACK information; the values ​​in the second set indicate the time slot offset between the PDSCH carrying semi-static scheduling data and the second PUCCH carrying the second HARQ-ACK information.

[0007] In one possible implementation, the first set belongs to the first cell, and the second set belongs to the second cell. This can also be understood as the first set being the K1 set of the first cell, and the second set being the K1 set of the second cell.

[0008] In one possible implementation, the first cell can be a PUCCH handover secondary cell, and the second cell can be either a primary cell or a PUCCH secondary cell.

[0009] Based on the above technical solution, the DCI sent by the network device to the terminal device is used to schedule downlink data while activating semi-static scheduling. The timing offset value from PDSCH to HARQ feedback indicated by the DCI can simultaneously indicate the time domain position of the PUCCH carrying the HARQ-ACK corresponding to the semi-static scheduled data and the time domain position of the PUCCH carrying the HARQ-ACK corresponding to the downlink data. Furthermore, this timing offset value belongs to both the K1 set in the first cell and the K1 set in the second cell. Through this scheme, the time domain position of the PUCCH carrying the HARQ-ACK information corresponding to the semi-static scheduled data determined by the terminal device is valid, thereby ensuring timely feedback of the HARQ-ACK information corresponding to the semi-static scheduled data and guaranteeing the transmission performance of the semi-static scheduled data.

[0010] The above scheme can also be understood as follows: the terminal device does not expect the first value in the first set indicated by the second indication information to be received, which is not included in the second set. Alternatively, it can be understood as follows: the terminal device does not expect the slot offset value between the PDSCH indicating the activation of SPS and the PUCCH carrying the HARQ-ACK information of the PDSCH to be a value not found in the intersection of the first set and the second set.

[0011] In one possible implementation, the terminal device can determine the time domain location of the first PUCCH based on the first value; and the terminal device can send the first HARQ-ACK information via the first PUCCH on the first cell.

[0012] Based on the above technical solution, if the second cell is in the downlink symbol position at this time, the first PUCCH can be sent in the first cell, thereby reducing the latency of HARQ-ACK transmission of downlink data.

[0013] Secondly, a HARQ-ACK information feedback method is provided. This method can be executed by a terminal device or by a component of the terminal device. The method includes: the terminal device receiving downlink control information from a network device. This downlink control information is used to schedule downlink data. The downlink control information includes first indication information, which instructs the terminal device to send first HARQ-ACK information via a first PUCCH in a first cell. The first HARQ-ACK information is the HARQ-ACK information corresponding to the downlink data. The downlink control information is also used to activate semi-static scheduling. The downlink control information further includes third indication information, which indicates values ​​in a first set and values ​​in a second set. The terminal device can determine the time-domain position of the first PUCCH and the time-domain position of the second PUCCH based on the third indication information. The terminal device sends the first HARQ-ACK information via the first PUCCH in the first cell; the terminal device sends the second HARQ-ACK information via the second PUCCH in the second cell. The second HARQ-ACK information is the HARQ-ACK information corresponding to the semi-statically scheduled data. The values ​​in the first set indicate the time slot offset between the PDSCH carrying the downlink data and the first PUCCH carrying the first HARQ-ACK information; the values ​​in the second set indicate the time slot offset between the PDSCH carrying the semi-statically scheduled data and the second PUCCH carrying the second HARQ-ACK information.

[0014] In one possible implementation, for the downlink data, the terminal device can determine the temporal location of the first PUCCH based on the third indication information and the first set.

[0015] Based on the above technical solution, if the second cell is in the downlink symbol position at this time, the first PUCCH can be sent in the first cell, thereby reducing the latency of HARQ-ACK transmission of downlink data.

[0016] In one possible implementation, for semi-statically scheduled data, the terminal device determines the temporal location of the second PUCCH based on the third indication information and the second set.

[0017] In other words, the PDSCH to HARQ-ACK feedback timing indication field in the downlink control information of this method indicates two K1 values: one is the K1 value in the K1 set of the first cell (i.e., the first set), and the other is the K1 value in the K1 set of the second cell (i.e., the second set). This allows the third indication information to also indicate a valid value in the second set. It can also be understood that in the above method, the terminal device does not expect the received third indication information to contain values ​​beyond those included in the second set.

[0018] Based on the above scheme, in this embodiment, the DCI sent by the network device to the terminal device is used to dynamically schedule downlink data while activating semi-static scheduling. The timing offset value from PDSCH to HARQ feedback indicated by the DCI can simultaneously indicate the time-domain position of the PUCCH carrying the HARQ-ACK information corresponding to the semi-static scheduled data in the K1 set of the second cell, and the time-domain position of the PUCCH carrying the HARQ-ACK information corresponding to the downlink data in the K1 set of the first cell. Through the above scheme, the time-domain position of the PUCCH carrying the HARQ-ACK information corresponding to the semi-static scheduled data determined by the terminal device is valid, thereby enabling the HARQ-ACK information corresponding to the semi-static scheduled data to be fed back in a timely manner, ensuring the transmission performance of the semi-static scheduled data.

[0019] Thirdly, a HARQ-ACK information feedback method is provided. This method can be executed by a terminal device or by a component of the terminal device. The method includes: the terminal device receiving configuration information from a network device, the configuration information being used to configure a third PUCCH carrying third information for a second cell, the third PUCCH overlapping with the physical uplink shared channel (PUSCH) in the time domain; the terminal device receiving downlink control information from the network device, the downlink control information being used to schedule downlink data, the downlink control information including first indication information, the first indication information instructing the terminal device to send first HARQ-ACK information via the first PUCCH in the first cell, the first HARQ-ACK information being the HARQ-ACK information corresponding to the downlink data; and the terminal device discarding the third PUCCH. In this application, the third information may include one or more of the following: HARQ-ACK information of semi-statically scheduled data, channel state information, and scheduling request information.

[0020] Based on the above technical solution, in this application, for scenarios where there are PUCCHs to be transmitted in two cells, if the third PUCCH carrying third information overlaps with the PUSCH in the time domain, the terminal device can discard the third PUCCH. This eliminates the need for the terminal device to multiplex the control channel in two cells (which can also be understood as "cross-cell") and then multiplex it into the corresponding PUSCH. At the same time, it can reduce the number of PUSCHs carrying uplink control information and simplify the multiplexing complexity of the terminal device.

[0021] In one possible implementation, the terminal device can discard the third PUCCH when the time domain position of the physical downlink control channel (PDCCH) carrying DCI precedes the time domain position of PUSCH, and the time domain position interval between PDCCH and PUSCH is greater than or equal to the first duration.

[0022] In another possible implementation, if the time domain position of the PDCCH carrying DCI is before the time domain position of the third PUCCH, and the time domain position interval between the PDCCH and the third PUCCH is greater than or equal to the first duration, the terminal device can discard the third PUCCH.

[0023] This can also be understood as the success or failure of the terminal device in receiving downlink control information affecting whether the terminal device discards the third PUCCH on the second cell. Assuming that the terminal device needs three symbols to parse the DCI (in the case of the first duration), the terminal device needs to successfully parse the DCI before sending the PUSCH or before sending the third PUCCH.

[0024] Based on the above technical solution, this application provides a first duration, enabling the network device to determine that the terminal device will discard the third PUCCH; that is, the network device can also determine that the third information will not be reused on the PUSCH. Therefore, the network device does not need to perform blind detection when detecting the PUSCH, reducing the detection complexity of the network device. Alternatively, it can be understood that without providing the first duration, the network device cannot determine whether the terminal device will discard the third PUCCH, nor can it determine whether the third information has been reused on the PUSCH. Therefore, when detecting the PUSCH, the network device needs to perform blind detection to check whether the third information has been reused on the PUSCH, resulting in high detection complexity.

[0025] In one possible implementation, the time domain positions of the first PUCCH and PUSCH do not overlap. In this case, the terminal device can send the first HARQ-ACK information through the first PUCCH. This can also be understood as the first PUCCH not needing to be multiplexed with the PUSCH.

[0026] In one possible implementation, the time domain positions of the first PUCCH and PUSCH overlap. In this case, the terminal device can send the first HARQ-ACK information via the PUSCH. This can also be understood as the first PUCCH and PUSCH being multiplexed.

[0027] In one possible implementation, the third PUCCH overlaps with the downlink symbol configured by the network device in the time domain.

[0028] In one possible implementation, the time slot where the third PUCCH is located overlaps with the time slot where the first PUCCH is located in the time domain.

[0029] Fourthly, a HARQ-ACK information feedback method is provided. This method is a network-side method corresponding to the first aspect, and can be executed by a network device, or by a component of the network device. The beneficial effects achieved by this method are similar to those achieved by the HARQ-ACK information feedback method in the first aspect.

[0030] The method includes: a network device sending downlink control information to a terminal device. The downlink control information is used to schedule downlink data. The downlink control information includes first indication information, which instructs the terminal device to send first HARQ-ACK information via a first PUCCH in a first cell. The first HARQ-ACK information is the HARQ-ACK information corresponding to the downlink data. The downlink control information is also used to activate semi-static scheduling. The downlink control information further includes second indication information, which indicates a first value. The first value is a value in a first set, and the second set includes the first value. The network device receives second HARQ-ACK information via a second PUCCH in a second cell. The number of time slots between the time domain position of the second PUCCH and the PDSCH carrying the semi-statically scheduled data is the first value. The second HARQ-ACK information is the HARQ-ACK information corresponding to the semi-statically scheduled data. The values ​​in the first set indicate the time slot offset between the PDSCH carrying downlink data and the first PUCCH carrying the first HARQ-ACK information; the values ​​in the second set indicate the time slot offset between the PDSCH carrying semi-static scheduling data and the second PUCCH carrying the second HARQ-ACK information.

[0031] In one implementation, the network device receives first HARQ-ACK information via a first PUCCH in the first cell, wherein the number of time slots between the time domain position of the first PUCCH and the PDSCH carrying downlink data is a first value.

[0032] Fifthly, a HARQ-ACK information feedback method is provided. This method is a network-side method corresponding to the second aspect, and can be executed by a network device, or by a component of the network device. The beneficial effects achieved by this method are similar to those achieved by the HARQ-ACK information feedback method in the second aspect.

[0033] The method includes: a network device sending downlink control information to a terminal device. The downlink control information is used to schedule downlink data. The downlink control information includes first indication information, which instructs the terminal device to send first HARQ-ACK information via a first PUCCH in a first cell. The first HARQ-ACK information is the HARQ-ACK information corresponding to the downlink data. The downlink control information is also used to activate semi-static scheduling. The downlink control information further includes third indication information, which indicates values ​​in a first set and values ​​in a second set. In the first cell, the network device receives the first HARQ-ACK information via the first PUCCH, wherein the number of time slots between the time-domain position of the first PUCCH and the PDSCH carrying the downlink data is the value indicated by the third indication information. In the second cell, the network device receives second HARQ-ACK information via a second PUCCH, wherein the number of time slots between the time-domain position of the second PUCCH and the PDSCH carrying the semi-statically scheduled data is the value indicated by the third indication information. The second HARQ-ACK information is the HARQ-ACK information corresponding to the semi-statically scheduled data. The values ​​in the first set indicate the time slot offset between the PDSCH carrying downlink data and the first PUCCH carrying the first HARQ-ACK information; the values ​​in the second set indicate the time slot offset between the PDSCH carrying semi-static scheduling data and the second PUCCH carrying the second HARQ-ACK information.

[0034] In one possible implementation, for downlink data scheduled by DCI, the time slot offset between the time domain position of the first PUCCH and the PDSCH carrying the downlink data scheduled by DCI is a value in the first set indicated by the third indication information.

[0035] In one possible implementation, for semi-statically scheduled data, the time slot offset between the time domain location of the second PUCCH and the PDSCH carrying the semi-statically scheduled data is a value in the second set indicated by the third indication information.

[0036] Sixthly, a communication method is provided, which is a network-side method corresponding to the third aspect. This method can be executed by a network device, or by a component of the network device. The beneficial effects achieved by this method are comparable to those achieved by the HARQ-ACK information feedback method of the third aspect described above.

[0037] The method includes: a network device sending configuration information to a terminal device, the configuration information being used to configure a third PUCCH carrying third information for a second cell, the third PUCCH overlapping with the PUSCH in the time domain. The network device sending downlink control information to the terminal device, the downlink control information being used to schedule downlink data, the downlink control information including first indication information, the first indication information instructing the terminal device to send first HARQ-ACK information via the first PUCCH in the first cell, the first HARQ-ACK information being the HARQ-ACK information corresponding to the downlink data. The terminal device does not receive the third PUCCH in the second cell. The third information may include one or more of the following: HARQ-ACK information for semi-statically scheduled data, channel state information, and scheduling request information.

[0038] In one possible implementation, when the time domain position of the PDCCH carrying downlink control information is before the time domain position of the PUSCH, and the time domain position interval between the PDCCH and the PUSCH is greater than or equal to a first duration, the network device does not receive the third PUCCH.

[0039] In another possible implementation, if the time domain position of the PDCCH carrying physical downlink control information is before the time domain position of the third PUCCH, and the time domain position interval between the PDCCH and the third PUCCH is greater than or equal to the first duration, the terminal device can discard the third PUCCH.

[0040] In one possible implementation, the time domain positions of the first PUCCH and PUSCH do not overlap. In this case, the network device can receive the first HARQ-ACK information through the first PUCCH. Alternatively, it can be understood that the first PUCCH does not need to be multiplexed with the PUSCH.

[0041] In one possible implementation, the time domain positions of the first PUCCH and PUSCH overlap. In this case, the network device can receive the first HARQ-ACK information through the PUSCH. This can also be understood as the first PUCCH and PUSCH being multiplexed.

[0042] In one possible implementation, the third PUCCH overlaps with the downlink symbol configured by the network device in the time domain.

[0043] In one possible implementation, the time slot where the third PUCCH is located overlaps with the time slot where the first PUCCH is located in the time domain.

[0044] In a seventh aspect, a communication apparatus is provided for performing the method in any of the possible implementations of the first to third aspects described above. Specifically, the apparatus may include units and / or modules for performing the method in any of the possible implementations of the first to third aspects, such as transceiver units and / or processing units.

[0045] Eighthly, a communication apparatus is provided for performing the method in any of the possible implementations of the fourth to sixth aspects described above. Specifically, the apparatus may include units and / or modules for performing the method in any of the possible implementations of the fourth to sixth aspects, such as transceiver units and / or processing units.

[0046] In one possible implementation of the seventh or eighth aspect, the communication unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor, or processing circuitry. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0047] A ninth aspect provides a communication apparatus comprising: at least one processor for executing a computer program or instructions stored in a memory to perform the method in any of the possible implementations of the first to third aspects described above. Optionally, the apparatus further comprises a memory for storing the computer program or instructions.

[0048] In one implementation, the device is a terminal device.

[0049] In another implementation, the device is a chip, chip system, or circuit for a terminal device.

[0050] A tenth aspect provides a communication apparatus comprising: at least one processor for executing a computer program or instructions stored in a memory to perform the method in any of the possible implementations of the fourth to sixth aspects described above. Optionally, the apparatus further comprises a memory for storing the computer program or instructions.

[0051] In one implementation, the device is a network device.

[0052] In another implementation, the device is a chip, chip system, or circuit for use in network devices.

[0053] Eleventhly, a processing apparatus is provided, including a processor and a memory. The processor is used to read instructions stored in the memory and to receive signals via a transceiver and transmit signals via a transmitter to execute a method in any possible implementation of any of the first to sixth aspects.

[0054] In a twelfth aspect, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including methods for performing any of the possible implementations of the first to sixth aspects described above.

[0055] In a thirteenth aspect, a computer program product containing instructions is provided, which, when run on a communication device, causes the communication device to perform the method in any one of the possible implementations of the first to sixth aspects described above.

[0056] In a fourteenth aspect, a communication system is provided, the communication system comprising a terminal device and a network device, the terminal device being configured to execute a method according to any implementation of the first aspect, the network device being configured to execute a method according to any implementation of the fourth aspect; or, the terminal device being configured to execute a method according to any implementation of the second aspect, the network device being configured to execute a method according to any implementation of the fifth aspect; or the terminal device being configured to execute a method according to any implementation of the third aspect, the network device being configured to execute a method according to any implementation of the sixth aspect. Attached Figure Description

[0057] Figure 1 A schematic diagram of the architecture of a mobile communication system used in the embodiments of this application;

[0058] Figure 2 This is a schematic diagram provided in this application for determining the time-domain location of the PUCCH for the HARQ-ACK of the PDSCH carrying SPS;

[0059] Figure 3 This is a schematic diagram illustrating the determination of the typel codebook provided in this application;

[0060] Figure 4 This is a schematic diagram of PUCCH cell handover provided in this application;

[0061] Figure 5 This is a schematic diagram of the time-domain location of the PUCCH carrying the HARQ-ACK of the PDSCH under PUCCH cell handover provided in this application;

[0062] Figure 6 This is a schematic flowchart of the HARQ-ACK information feedback method provided in this application;

[0063] Figure 7 This is a schematic diagram showing the time-domain position of the PUCCH and the time slot offset between the PDSCH carrying downlink data when the subcarrier spacing is different, as provided in this application.

[0064] Figure 8This is another schematic diagram showing the time-domain location of the PUCCH carrying the HARQ-ACK of the PDSCH under the PUCCH cell handover provided in this application;

[0065] Figure 9 This is another schematic diagram showing the time-domain location of the PUCCH carrying the SPS PDSCH and the HARQ-ACK PUCCH under PUCCH cell handover provided in this application.

[0066] Figure 10 This is a schematic diagram showing that the HARQ-ACK bit position corresponding to the PDSCH of SPS is filled with "NACK" in the type 1 codebook of PUCCH-sSCell provided in this application.

[0067] Figure 11 This is a schematic flowchart of the HARQ-ACK information feedback method provided in this application;

[0068] Figure 12 This is a schematic diagram of discarding a third PUCCH provided in this application;

[0069] Figure 13 This is a schematic block diagram of a communication device provided in this application;

[0070] Figure 14 This is another schematic block diagram of the communication device provided in this application. Detailed Implementation

[0071] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0072] Figure 1 This is a schematic diagram of the architecture of the communication system 1000 used in an embodiment of this application. Figure 1 As shown, the communication system includes a wireless access network 100 and a core network 200. Optionally, the communication system 1000 may also include an Internet 300. The wireless access network 100 may include at least one wireless access network device (such as...). Figure 1 110a and 110b in the above), may also include at least one terminal (such as Figure 1 (Referring to 120a-120j in the original text). Terminals connect wirelessly to the wireless access network (WLAN) equipment, which in turn connects to the core network via wireless or wired connections. The core network equipment and the WLAN equipment can be independent physical devices, or they can integrate the functions of the core network equipment and the logical functions of the WLAN equipment onto the same physical device. Alternatively, a single physical device can integrate some of the functions of both the core network equipment and the WLAN equipment. Terminals and WLAN equipment can be interconnected via wired or wireless connections. Figure 1This is just an illustration; the communication system may also include other network devices, such as wireless repeaters and wireless backhaul devices. Figure 1 It is not shown in the middle.

[0073] Radio access network equipment (an example of network equipment) can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system; it can also be a module or unit that performs some of the functions of a base station, for example, it can be a central unit (CU) or a distributed unit (DU). Here, the CU performs the functions of the radio resource control protocol and packet data aggregation layer protocol of the base station, and can also perform the functions of the service data adaptation protocol (SDAP); the DU performs the functions of the radio link control layer and media access control layer of the base station, and can also perform some or all of the physical layer functions. For specific descriptions of the above protocol layers, please refer to the relevant technical specifications of 3GPP. Radio access network equipment can be a macro base station (such as... Figure 1 110a in the text), can also be a micro base station or an indoor station (such as... Figure 1 110b) in the text can also be a relay node or a donor node, etc. The embodiments of this application do not limit the specific technology or device form used in the wireless access network equipment. For ease of description, the following description uses a base station as an example of a wireless access network device.

[0074] A terminal can also be called a terminal device, user interface (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminals.

[0075] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0076] The roles of base stations and terminals can be relative, for example, Figure 1 The helicopter or drone 120i can be configured as a mobile base station. For terminals 120j accessing the wireless access network 100 via 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol; in this case, 120i is also a base station relative to 110a. Therefore, both base stations and terminals can be collectively referred to as communication devices. Figure 1 The 110a and 110b in the text can be referred to as communication devices with base station functions. Figure 1 The 120a-120j in the text can be referred to as communication devices with terminal functions.

[0077] Communication between base stations and terminals, between base stations, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0078] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0079] In the embodiments of this application, the time-domain symbol can be an orthogonal frequency division multiplexing (OFDM) symbol or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol. Unless otherwise specified, the symbols in the embodiments of this application refer to time-domain symbols.

[0080] In this application, the base station sends downlink signals or downlink information to the terminal, with the downlink information carried on the downlink channel; the terminal sends uplink signals or uplink information to the base station, with the uplink information carried on the uplink channel. In order to communicate with the base station, the terminal needs to establish a radio connection with a cell controlled by the base station. The cell with which the terminal has established a radio connection is called the terminal's serving cell. When the terminal communicates with this serving cell, it is also subject to interference from signals from neighboring cells.

[0081] It is understood that in the following embodiments of this application, PDSCH, PDCCH, PUCCH and PUSCH are only examples of downlink data channel, downlink control channel, uplink control channel and uplink data channel, respectively. In different systems and different scenarios, data channels and control channels may have different names, and the embodiments of this application do not limit this.

[0082] To facilitate understanding of the technical solution of this application, the following is a brief explanation of the technical terms involved in this application.

[0083] Primary cell (PCell): The primary cell is the cell that operates on the primary frequency. Terminal devices initiate the initial connection establishment process or the connection re-establishment process on the PCell. The PCell may also be specified during handover.

[0084] Secondary cell (SCell): For terminal devices configured with carrier aggregation (CA), a secondary cell is a cell that provides additional radio resources besides the primary cell.

[0085] Network devices (e.g., the aforementioned wireless access network devices) can activate and deactivate SCells via signaling. Activating a SCell indicates that the terminal device can transmit data on the SCell configured by the network device; deactivating a SCell indicates that the terminal device can no longer transmit data on that SCell.

[0086] PUCCH Secondary Cell (PUCCH SCell): A secondary cell configured with PUCCH. PUCCH can only be transmitted on a cell (e.g., PCell or SCell) after PUCCH parameters have been configured on that cell.

[0087] A PUCCH group is a group of cells in which the HARQ-ACK corresponding to the PDSCH on each cell can be transmitted on the same cell. A PUCCH group can include a primary PUCCH group and a secondary PUCCH group. Uplink control information such as HARQ-ACK in the primary PUCCH group can be transmitted on the PCell, while uplink control information such as HARQ-ACK in the secondary PUCCH group can be transmitted on the PUCCHSCell.

[0088] PUCCH switch secondary cell (PUCCH-sSCell): In a PUCCH group, this is another cell besides the one that can transmit PUCCHPCell or PUCCHSCell, which can also transmit PUCCH. PUCCH cell handover refers to the process where, within a PUCCH group (e.g., the primary PUCCH group), PUCCH can be transmitted on PCell or PUCCH-sSCell. Within a secondary PUCCH group, PUCCH can be transmitted on PUCCHSCell or PUCCH-sSCell. In a secondary PUCCH group, PUCCHSCell can be replaced by PCell for further description.

[0089] The K1 set: The DCI includes a timing indicator field for the PDSCH to the hybrid automatic repeat request (HARQ) feedback. This field indicates the slot offset between the PDSCH and the PUCCH carrying the corresponding HARQ-ACK feedback information. This slot offset is also called the K1 value. The DCI can use candidate K1 values ​​to form the K1 set. The K1 set can be predefined by the protocol or configured via RRC signaling. For example, the K1 set for DCI format 1_0 is {1, 2, 3, 4, 5, 6, 7, 8}, a total of 8 values, which can be indicated using 3 bits. For detailed information on the K1 set, please refer to the 3GPP technical specification (TS) 38.213.

[0090] Semi-static scheduling: During initial scheduling, network devices indicate the current scheduling information to terminal devices via PDCCH. When a terminal device identifies it as SPS, it saves the current scheduling information and transmits or receives data for that service at the same time-frequency resource location at fixed intervals. Using SPS transmission, with a single authorization, it can be used periodically, effectively saving PDCCH resources used for scheduling indication. Typically, the PUCCH carrying the HARQ-ACK for SPS data is transmitted on PCell or PUCCH SCell.

[0091] like Figure 2 As shown, the DCI on slot 0 schedules a PDSCH, which is also located in slot 0. Assuming K1 equals 1, the PUCCH carrying HARQ-ACK information bits is in slot 1 (slot 0 + K1). This PUCCH can be understood as a dynamically scheduled PUCCH because it is also indicated by the DCI. Simultaneously, the DCI on slot 0 can also activate SPS (in this case, the "DCI" can also be understood as "the DCI that activates SPS"). Once SPS is activated, there will be an SPS occasion (or "SPS PDSCH") every certain period of time (e.g., the SPS period). On this SPS occasion, the network device can send a PDSCH without sending another DCI for it. Then, for the time-domain location of the PUCCH carrying the HARQ-ACK of the SPS PDSCH, the terminal device can determine the time-domain location of the PUCCH carrying the HARQ-ACK using the same K1 value. Figure 2As shown, assume the terminal device receives the PDSCH of the SPS in slot 3. Since the value of K1 is 1, the terminal device determines that the time domain location of the PUCCH carrying the HARQ-ACK of the PDSCH of the SPS is slot 4 (slot 3+K1) on PCell.

[0092] HARQ-ACK codebook: Figure 2 The diagram illustrates a scenario where only 1 bit of HARQ-ACK information needs to be sent back within a single time slot. The terminal device needs to send a HARQ-ACK message for each received PDSCH, regardless of its cell or HARQ-ACK process, to inform the network device whether the PDSCH was correctly received. A 0 indicates NACK, and a 1 indicates ACK. This HARQ-ACK message can be sent to the network device via the PUCCH on the PCell.

[0093] When a terminal device needs to provide HARQ-ACK feedback for multiple received DCIs and / or PDSCHs within a single time slot, the number of HARQ-ACK information bits increases. Within a time slot, multiple HARQ-ACK information bits constitute a HARQ-ACK codebook. Each bit in the HARQ-ACK codebook indicates the HARQ-ACK information for the corresponding DCI or PDSCH, indicating whether the corresponding DCI or PDSCH has been correctly received by the terminal device. This HARQ-ACK codebook can be classified into three types: type 1, type 2, and type 3. The following mainly introduces type 1 codebook.

[0094] like Figure 3 As shown, assuming the network device is configured with a K1 set of {1, 2}, the terminal device can generate a type 1 codebook based on this K1 set. For example, Figure 3 The dashed boxes in the diagram represent the locations of candidate PDSCHs, which can also be understood as locations where PDSCH transmission might occur (candidate PDSCHs could also be SPS PDSCHs). If the network device actually schedules a PDSCH at a candidate PDSCH location (e.g., the solid box at location B), the terminal device sends a HARQ-ACK bit feedback for that PDSCH (which can be understood as a real ACK or NACK); if the network device does not schedule a PDSCH at a candidate PDSCH location, then these candidate PDSCH locations are filled with NACKs. From the terminal device's perspective, if the PDSCH is successfully parsed, an ACK is sent; otherwise (including PDSCHs that fail to parse, and DCIs that are not detected), a NACK is sent.

[0095] like Figure 3 As shown, assuming a candidate PDSCH requires 1 bit of HARQ-ACK feedback (the exact number of bits depends on a rule in the protocol, such as whether dual codewords are configured, which is not covered in this application and therefore will not be described in detail), then the HARQ-ACK codebook size is 6 bits. For example, the bit order of the 6-bit HARQ-ACK codebook could be: first, sorted by cell index, for example, PCells first, SCells second, and then sorted according to the order of candidate PDSCHs, with earlier candidate PDSCHs listed first. For example, in... Figure 3 In this context, the code can be in the order {A, B, C, D, E, F}, i.e., the 6-bit codebook is {0, X, 0, Y, 0, 0}. X corresponds to the dynamically scheduled PDSCH within the solid-line box at position B, and Y corresponds to the SPS PDSCH within the solid-line box at position D. For example, if the terminal device successfully parses the scheduled PDSCH at position D but does not detect the DCI for the scheduled PDSCH at position B, the codebook is {0, 0, 0, 1, 0, 0}. Alternatively, if the terminal device successfully parses both the dynamically scheduled PDSCH at position B and the SPS PDSCH at position D, the codebook is {0, 1, 0, 1, 0, 0}.

[0096] like Figure 3 As shown, PUCCHs carrying HARQ-ACK are transmitted on a fixed cell (e.g., PCell) by default. However, when a PUCCH cannot be transmitted (e.g., when the time domain position of the PUCCH overlaps with the downlink symbol), the PUCCH can only be postponed to the next time slot, which increases latency. Therefore, to solve this problem, Rel-17 introduces the PUCCH cell handover feature. In this feature, there is a 1-bit PUCCH cell indication field in the DCI. This cell indication field is used to indicate whether the PUCCH carrying HARQ-ACK is transmitted on PCell or on another PUCCH-sSCell. When the cell indication field in the DCI indicates that the PUCCH is transmitted on PCell, the terminal device determines the value of K1 based on the K1 set of PCell; when the cell indication field in the DCI indicates that the PUCCH is transmitted on PUCCH-sSCell, the terminal device determines the value of K1 based on the K1 set of PUCCH-sSCell.

[0097] For example, such as Figure 4As shown, the DCI indication on slot 0 sends a HARQ-ACK on the PUCCH of PCell (i.e., the cell indication field indicates PCell), and the bit value of the feedback timing indication field from PDSCH to HARQ-ACK in the DCI is "00". Assuming the K1 set in PCell is {1, 2}, then the value of the K1 indication is "1". This can also be understood as sending a HARQ-ACK on the PUCCH of slot 1 (slot 0 + K1) on PCell. The DCI indication on slot 1 sends a HARQ-ACK on the PUCCH of PUCCH-sSCell (i.e., the cell indication field indicates PUCCH-sSCell), and the bit value of the feedback timing indication field from PDSCH to HARQ-ACK in the DCI is "01". Assuming the K1 set in PUCCH-sSCell is {2, 3, 4, 5}, then the value of the K1 indication is "3". This can also be understood as sending a HARQ-ACK on the PUCCH in slot 4 (slot 1+K1) of PUCCH-sSCell.

[0098] If the DCI activates SPS scheduling (i.e., the DCI is an "SPS-activated DCI"), and the cell indication field in the DCI indicates that the HARQ-ACK is carried on PUCCH-sSCell, the terminal device determines the value of K1 based on the K1 set configured on PUCCH-sSCell. As mentioned earlier, once SPS is activated, the time-domain position of the PUCCH carrying the HARQ-ACK of the SPS PDSCH will follow the value of K1 indicated in the SPS-activated DCI. Figure 5 As shown, if the DCI indicator K1 for activating SPS is 3, then the PUCCH carrying the HARQ-ACK of the dynamically scheduled PDSCH is in slot 3 of the SCell. Subsequently, when determining the time-domain location of the PUCCH carrying the HARQ-ACK of SPS for the PDSCH, the value of K1 will be used. For example, as... Figure 5 As shown, assuming the terminal device receives the PDSCH of SPS in slot 4, the terminal device determines that the PUCCH carrying the HARQ-ACK of the PDSCH of SPS is in slot 7 (slot 4+K1) of PCell.

[0099] However, according to the type 1 codebook generation rules introduced earlier, for semi-statically scheduled PDSCH, if the UE uses the K1 set in the SCell to determine the K1 value and then determines the time-domain position of the PUCCH carrying the HARQ-ACK of the semi-statically scheduled PDSCH on the PCell, it may result in the HARQ-ACK codebook not including the HARQ-ACK bit of the semi-statically scheduled PDSCH. In other words, the time-domain position of the PUCCH carrying the HARQ-ACK information of the semi-statically scheduled PDSCH determined by the terminal device may be invalid, thus affecting the performance of data transmission.

[0100] It should be noted that in this application, the first cell in the following embodiments can be PUCCH-sSCell, and the second cell can be PCell or PUCCH-SCell.

[0101] It should be noted that the SCell in the following embodiments of this application can be understood as the PUCCH-sSCell described above; the PCell mentioned in the following embodiments of this application can be understood as PCell if it is in the main PUCCH group, and as PUCCH-SCell if it is in the auxiliary PUCCH group.

[0102] In view of this, this application provides a hybrid automatic repeat request acknowledgment (HARQ-ACK) method and apparatus, which can ensure that the time domain position of the PUCCH carrying HARQ-ACK determined by the terminal device is valid, thereby guaranteeing the performance of data transmission.

[0103] Figure 6 This is a schematic flowchart of a hybrid automatic repeat request acknowledgment (HARQ-ACK) method 600 provided in this application, which includes:

[0104] Step 601: The network device sends a DCI to the terminal device. Correspondingly, the terminal device receives the DCI.

[0105] In one possible implementation, network devices can send DCI to terminal devices via PDCCH. This DCI can be used to schedule downlink data, which can be understood as dynamic scheduling. Dynamically scheduled downlink data can be carried via PDSCH.

[0106] The DCI may include first indication information, which instructs the terminal device to send first HARQ-ACK information via the first PUCCH on the first cell. The first HARQ-ACK information is the HARQ-ACK information corresponding to the downlink data scheduled by the DCI. This first indication information can also be referred to as the cell indication field.

[0107] This DCI can also be used to activate SPS, or it can be understood that this DCI is the DCI for activating SPS. This DCI may also include second indication information, which indicates a first value, which is a value in a first set, and the second set also includes the first value.

[0108] In this application, the first set belongs to the first cell, which can be a PUCCH-sSCell, and the first set can be the K1 set on the PUCCH-sSCell; the second set belongs to the second cell, which can be a PCell or a PUCCHSCell, and the second set can be the K1 set on the PCell or a PUCCH SCell. The values ​​in the first set indicate the slot offset between the PDSCH carrying downlink data and the first PUCCH carrying the first HARQ-ACK information; the values ​​in the second set indicate the slot offset between the PDSCH carrying SPS data and the second PUCCH carrying the second HARQ-ACK information. The second HARQ-ACK information is the HARQ-ACK information corresponding to the SPS data.

[0109] The length of a time slot in this application can be 14 symbols, 7 symbols, or 2 symbols. When the time slot length is 7 symbols or 2 symbols, the time slot can also be called a sub-time slot.

[0110] If the subcarrier spacing of the cell where the PDSCH is located (e.g., cell #a) and the cell where the PUCCH is located (e.g., cell #b) are different, the time slot offset between the PDSCH and the PUCCH can be determined based on the time slot length of cell #b.

[0111] For example, assuming the K1 set of cell #b is {2, 3, 4, 5}, taking the value "2" in the K1 set as an example, this value indicates that the time slot offset between the PDSCH carrying downlink data and the first PUCCH carrying the first HARQ-ACK information is 2 time slots. Figure 7 As shown in (a) of the diagram, in one implementation, the time slot offset value can be understood as: the time slot offset between the last time slot ("time slot 1") overlapping with the time slot containing the PDSCH in cell #b, and the time slot ("time slot 3") containing the PUCCH. In another implementation, as shown... Figure 7 As shown in (b), the time slot offset value can be understood as: the time slot offset value between the first time slot ("time slot 0") that overlaps with the PDSCH end symbol in cell #b and the time slot ("time slot 2") where PUCCH is located.

[0112] It should be noted that the embodiments in this application are all illustrated using the example of the cell where the PDSCH is located having the same subcarrier spacing as the cell where the PUCCH is located. However, the technical solutions involved in this application can all be applied to scenarios where the subcarrier spacing of the cell where the PDSCH is located is different from that of the cell where the PUCCH is located. Considering that the subcarrier spacing of the cell where the PDSCH is located is different from that of the cell where the PUCCH is located, the time slot offset determined by the K1 value can be determined according to the subcarrier spacing of the cell where the PUCCH is located. In other words, the time slot offset is determined according to the subcarrier spacing of the cell where the PUCCH is located.

[0113] As an example, suppose the first set is {2, 3, 4, 5}. For example, if the second instruction is "00", then the second instruction indicates the first value in the first set, that is, the first value is "2". For another example, if the second instruction is "11", then the second instruction indicates the fourth value in the second set, that is, the first value is "5".

[0114] In other words, in this embodiment, the first value in the first set indicated by the second indication information of the network device is not arbitrarily indicated, and the second set must also contain this first value. As an example, suppose the first set is {2, 3, 4, 5} and the second set is {1, 2}. In this case, the first value should be "2", and the second indication information is "00". At this time, the first value in the first set indicated by the second indication information is also contained in the second set. If the value in the first set indicated by the second indication information is not "2" (or the bit value of the second indication information is not "00"), for example, when the second indication information is "11", the first value is "5". When the terminal device receives this second indication information, it will recognize the indication information as erroneous (or "illegal value"). At this time, the terminal device will consider this an error case. The terminal can discard the second indication information, or discard the downlink control information, or not discard the downlink control information, but will not receive the semi-statically scheduled data.

[0115] Alternatively, in this embodiment, the terminal device does not expect the first value in the first set indicated by the second indication information to be included in the second set. Or, when the activation DCI indication sends HARQ-ACK via PUCCH on the SCell, the terminal device does not expect the K1 value indicated in the activation DCI to be a value that does not belong to the intersection of the first set and the second set.

[0116] This can also be understood as the terminal device not expecting the time slot timing value indicated by the SPS-activated DCI for transmitting HARQ-ACK information to be an intersection of the time slot timing value set of the Pcell's activated downlink (DL)-BWP and the time slot timing value set of the PUCCH-sSCell's activated DL-BWP.

[0117] In this embodiment, the DCI and the PDSCH scheduled by the DCI can be on any cell, without limitation. For example, the network device can send the DCI on the first cell or on the second cell; the first PDSCH scheduled by the DCI can be on the first cell or on the second cell; the second PDSCH of the SPS activated by the DCI can be on the first cell or on the second cell.

[0118] Optionally, step 602 is also included, whereby the network device may send a first PDSCH to the terminal device, which is a dynamically scheduled PDSCH of the DCI. Correspondingly, the terminal device receives the dynamically scheduled first PDSCH.

[0119] Optionally, the method also includes step 603, whereby the terminal device determines the temporal location of the first PUCCH carrying the first HARQ-ACK information based on the first value.

[0120] As an example, continue to refer to Figure 7 Assuming the terminal device receives the first PDSCH scheduled by DCI in slot 0, if the second indication information is "00" and the first value is "2", the terminal device determines that the time domain position of the first PUCCH carrying the first HARQ-ACK information is slot 2.

[0121] Optionally, step 604 is also included, in which the terminal device sends a first HARQ-ACK message via a first PUCCH on the first cell.

[0122] Optionally, the method further includes step 605, whereby the network device receives a first PUCCH carrying first HARQ-ACK information on the first cell. The number of time slots between the time-domain location of the second PUCCH and the PDSCH carrying SPS data is a first value.

[0123] This can also be understood as the first value being the time slot offset between the PDSCH carrying downlink data and the first PUCCH carrying the first HARQ-ACK information. Specifically, the network device can determine the time domain position of the first PUCCH by referring to the description of step 610 below.

[0124] Optionally, method 600 further includes step 606, whereby the network device sends a second PDSCH to the terminal device, which may be the PDSCH of the SPS. Correspondingly, the terminal device receives the second PDSCH of the SPS.

[0125] Step 607: The terminal device determines the temporal location of the second PUCCH carrying the second HARQ-ACK information based on the first value.

[0126] As an example, refer to Figure 5 As shown, assuming the terminal device receives the second PDSCH of SPS in slot 4, if the second indication information is "01" and the first value is "3", the terminal device determines that the time domain position of the second PUCCH carrying the second HARQ-ACK information is slot 7.

[0127] Specifically, the time slot in which the terminal device receives the SPS PDSCH can be pre-configured by the network device. In one implementation, before step 601, step 608 may be included, in which the network device sends configuration information to the terminal device. This configuration information is used to configure the SPS period (e.g., the interval between times the terminal device receives the second PDSCH of the SPS), configure the second PUCCH carrying the SPS HARQ-ACK (e.g., the format of the PUCCH, the number of symbols, etc.), and so on.

[0128] Step 609: The terminal device sends the second HARQ-ACK information via the second PUCCH on the second cell.

[0129] Step 610: The network device receives the second PUCCH carrying the second HARQ-ACK information on the second cell.

[0130] The first value is the time slot offset between the second PDSCH carrying SPS data and the second PUCCH carrying second HARQ-ACK information.

[0131] In one implementation, the network device can first determine a first value, and then determine the time domain location of the second PUCCH based on the first value. In another implementation, the network device can also first determine a time slot for receiving the second PUCCH based on service latency requirements, available resources, etc. (For example, for an urgent service, the network device can schedule resources in a certain time slot to receive the second PUCCH), and then determine whether the scheduled time slot meets the requirements of the first value. If the time slot meets the requirements of the first value, the network device can use the scheduled time slot to receive the second PUCCH; otherwise, the network device can reschedule resources in a certain time slot, thereby ultimately determining the time domain location for receiving the second PUCCH.

[0132] In this application, "sending DCI to the terminal device via PDCCH" can also be understood as the DCI being carried on PDCCH. Similarly, "sending first HARQ-ACK information via first PUCCH" can also be understood as the first HARQ-ACK information being carried on the first PUCCH; and "sending second HARQ-ACK information via second PUCCH" can also be understood as the second HARQ-ACK information being carried on the second PUCCH.

[0133] Based on the above technical solution, the DCI sent by the network device to the terminal device is used to schedule downlink data while activating semi-static scheduling. The timing offset value from PDSCH to HARQ feedback indicated by the DCI can simultaneously indicate the time domain position of the PUCCH carrying the HARQ-ACK corresponding to the semi-static scheduled data and the time domain position of the PUCCH carrying the HARQ-ACK corresponding to the downlink data. Furthermore, this timing offset value belongs to both the K1 set in the first cell and the K1 set in the second cell. Through this solution, the time domain position of the PUCCH carrying the HARQ-ACK information corresponding to the semi-static scheduled data determined by the terminal device is valid. That is, the HARQ-ACK codebook in the second cell can include the HARQ-ACK bits of the semi-static scheduled PDSCH, thereby ensuring timely feedback of the HARQ-ACK information corresponding to the semi-static scheduled data and guaranteeing the transmission performance of the semi-static scheduled data.

[0134] This application also provides a communication method 800, the schematic flowchart of which can be referred to. Figure 6 The same steps can be referred to the description in method 600, and will not be described in detail here. Specifically, compared with method 600, the DCI in this embodiment can be referred to the description of DCI in method 600. The difference is that the DCI in this embodiment does not include the second indication information, but the DCI may include the third indication information. The method includes:

[0135] Step 801: The network device sends the DCI to the terminal device. Correspondingly, the terminal device receives the DCI.

[0136] The DCI may include third indication information (e.g., a timing indication field between PDSCH and HARQ-ACK) that indicates values ​​in the first set and values ​​in the second set.

[0137] This can also be understood as follows: in this embodiment, the third indication information can indicate a value in the first set or a value in the second set. Assuming the first set is {2, 3, 4, 5} and the second set is {1, 2}, and assuming the bit value of the third indication information is "01", then in the first set, the third indication information indicates a value of "3"; and in the second set, the third indication information indicates a value of "2". In the above example, it can be seen that the second set contains fewer values ​​than the first set. For this scenario, this application proposes the following two implementation methods:

[0138] Method 1: It can be agreed upon through an agreement that, regardless of the bit value of the third indication information, a value can always be indicated in the second set. This ensures that the third indication information can indicate a valid value in the second set.

[0139] As an example, suppose the third indication bit value is "11". In the first set, the third indication bit indicates the value "5". In the second set, it can be agreed that "11" indicates the first value in the second set (e.g., "1"), or that "11" indicates the second value in the second set (e.g., "2"). Similarly, suppose the third indication bit value is "10". In the second set, it can also be agreed that "10" indicates the first value in the second set, or the second value in the second set. Alternatively, the values ​​in the second set can be repeated to obtain a second set of the same size as the first set. For example, the second set would then become {1, 1, 2, 2}, {1, 2, 1, 2}, or {1, 2, 1, 1}, etc.

[0140] Method 2: The network device can pre-determine the set containing fewer values ​​in the first and second sets. For example, the first set might be {2, 3, 4, 5}, and the second set might be {1, 2}. In this case, the second set contains fewer values. The network device can then determine that when sending the third indication information, the indicated value of that third indication information will not be invalid in the second set. In other words, those skilled in the art will design the bit values ​​of the third indication information to indicate two values, rather than four values.

[0141] As an example, the bit values ​​of the third indication information sent by the network device may include "00" and "01". The design of the third indication information bit values ​​indicating four values, such as "00", "01", "10", and "11", is not possible. That is, the network device guarantees that the third indication information will always indicate a value in the second set.

[0142] In other words, in this embodiment, the PDSCH to HARQ-ACK feedback timing indication field in the DCI indicates two K1 values: one is a value in the K1 set in PUCCH-sSCell, and the other is a value in the K1 set in PCell. This ensures that the third indication information can also indicate a valid value within the second set. Alternatively, in this embodiment, the terminal device does not expect the third indication information to contain values ​​exceeding those included in the second set. Or, the UE does not expect the third indication information to exceed the range of the second set.

[0143] In this embodiment, the DCI and the PDSCH scheduled by the DCI can be on any cell, without limitation. For example, the network device can send the DCI on the first cell or on the second cell; the PDSCH scheduled by the DCI can be on the first cell or on the second cell; the PDSCH of the SPS activated by the DCI can be on the first cell or on the second cell.

[0144] Optionally, the method further includes step 802, whereby the network device sends a first PDSCH to the terminal device, which may be a dynamically scheduled PDSCH of the DCI. Correspondingly, the terminal device receives the dynamically scheduled first PDSCH.

[0145] Optionally, the method also includes step 803, whereby the terminal device determines the temporal location of the first PUCCH carrying the first HARQ-ACK information based on the third instruction information.

[0146] Specifically, for downlink data, the terminal device can determine the temporal location of the first PUCCH based on the third indication information and the first set. As an example, such as... Figure 8 As shown, assuming the third indication information is "00", the first set is {2, 3, 4, 5}, and assuming the terminal device receives the DCI-scheduled PDSCH in slot 0, the terminal device can determine that the time domain position of the first PUCCH is slot 2.

[0147] Optionally, the method further includes step 804, whereby the terminal device sends a first HARQ-ACK message via a first PUCCH on the first cell. For example, the terminal device sends the first HARQ-ACK message via a first PUCCH on PUCCH-sSCell.

[0148] Optionally, the method further includes step 805, whereby the network device receives a first PUCCH carrying first HARQ-ACK information on the first cell. The number of time slots between the time-domain position of the first PUCCH and the PDSCH carrying downlink data is the value indicated by the third indication information.

[0149] Specifically, the time-domain position of the first PUCCH and the number of time slots between the time-domain position of the first PUCCH and the PDSCH carrying downlink data are values ​​in the first set indicated by the third indication information. The method by which the network device determines the time-domain position of the first PUCCH can be referred to step 609 in method 600, and will not be repeated here.

[0150] Step 806: The network device sends a second PDSCH to the terminal device. This second PDSCH can be the PDSCH of the SPS. Correspondingly, the terminal device receives the second PDSCH of the SPS.

[0151] Step 807: The terminal device determines the time domain location of the second PUCCH carrying the second HARQ-ACK information and the time domain location of the first PUCCH carrying the first HARQ-ACK information based on the third indication information.

[0152] Specifically, for SPS-scheduled data, the terminal device can determine the temporal location of the second PUCCH based on the third indication information and the second set. As an example, such as... Figure 8 As shown, assuming the third indication information is "00", the second set is {1, 2}, and assuming the terminal device receives the PDSCH of SPS in slot 4, the terminal device can determine the time domain position of the second PUCCH as slot 5.

[0153] Optionally, before step 801, step 808 may be included, in which the network device sends configuration information to the terminal device. Specifically, refer to step 608 in method 600.

[0154] Step 809: The terminal device sends the second HARQ-ACK information via the second PUCCH on the second cell.

[0155] For example, the terminal device on PCell sends a second HARQ-ACK message via a second PUCCH.

[0156] Step 810: The network device receives a second PUCCH carrying second HARQ-ACK information on the second cell. The number of time slots between the time-domain position of the second PUCCH and the PDSCH carrying SPS data is the value indicated by the third indication information.

[0157] Specifically, the number of time slots between the time domain position of the second PUCCH and the PDSCH carrying the SPS data is the value in the second set indicated by the third indication information.

[0158] Based on the above technical solution, in this embodiment, the DCI sent by the network device to the terminal device is used to schedule downlink data while activating semi-static scheduling. The timing offset value from PDSCH to HARQ feedback indicated by the DCI can simultaneously indicate the time-domain position of the PUCCH carrying the HARQ-ACK corresponding to the semi-static scheduled data in the K1 set of the second cell, and the time-domain position of the PUCCH carrying the HARQ-ACK corresponding to the downlink data in the K1 set of the first cell. Through the above solution, the time-domain position of the PUCCH carrying the HARQ-ACK information corresponding to the semi-static scheduled data determined by the terminal device is valid. That is, the HARQ-ACK codebook on the second cell can include the HARQ-ACK bits of the semi-static scheduled PDSCH, thereby enabling the HARQ-ACK information corresponding to the semi-static scheduled data to be fed back in a timely manner, ensuring the transmission performance of the semi-static scheduled data.

[0159] Methods 600 and 800 provided in this application can also be applied to the following scenarios. For example, the DCI for activating SPS instructs the transmission of a first PUCCH carrying downlink data HARQ-ACK on PUCCH-sSCell, and a second PUCCH carrying SPSHARQ-ACK is also transmitted on PUCCH-sSCell. That is, in this scenario, both the downlink data PUCCH and the SPS PUCCH can be transmitted on PUCCH-sSCell. Subsequently, the network device instructs to "deactivate" PUCCH-sSCell ("deactivating" PUCCH-sSCell can be understood as: the network device instructs the terminal device not to transmit data on this PUCCH-sSCell), at which time the second PUCCH carrying SPS HARQ-ACK will be on PCell. In this scenario, methods 600 and 800 are also applicable.

[0160] For example, in this scenario, after the network device sends the "deactivate" PUCCH-sSCell indication, it needs to determine the current K1 value, such as whether the current K1 value is the K1 value provided in method 600 or method 800. If the K1 value is the K1 value determined by method 600 or method 800 of this application, the network device can receive the PUCCH of SPSHARQ-ACK through method 600 or method 800 of this application. If the K1 value is not the K1 value determined by method 600 and method 800 of this application, the network device can resend the indication information indicating the value of K1 while sending the "deactivate" PUCCH-sSCell indication, in order to determine the time domain position of the PUCCH of SPSHARQ-ACK.

[0161] As an example, such as Figure 9As shown in Figure (a), assume the terminal device receives a DCI on slot 0 of PCell. This DCI is an SPS-activated DCI, indicating that a first PUCCH carrying downlink data and a second PUCCH carrying SPS HARQ-ACK are also being sent on PUCCH-sSCell. Assume the PDSCH-to-HARQ-ACK feedback timing indication field in this DCI is "00", and the value of K1 in the K1 set of PUCCH-sSCell is "2". At this time, the terminal device determines, based on the value of K1, to send the first PUCCH carrying downlink data and the first PUCCH carrying downlink data and the first PUCCH carrying downlink data and the first PUCCH carrying downlink data and the second PUCCH carrying SPS HARQ-ACK are also being sent on PUCCH-sSCell. Assume the terminal device receives an SPS PDSCH on slot 4 of PCell, then based on the value of K1, the terminal device determines, based on the value of K1, to send the first PUCCH carrying downlink data and the first PUCCH carrying downlink data and the first PUCCH carrying downlink data and the first PUCCH carrying downlink data and the second PUCCH carrying SPS HARQ-ACK are being sent on PUCCH-sSCell. Suppose that the network device instructs to activate PUCCH-sSCell in slot 7. Since the current K1 value is also included in the K1 set of PCell, the network device can receive the HARQ-ACK bit of SPS in slot 0 of PCell.

[0162] Or, as another example, such as Figure 9 As shown in Figure (b), assuming the PDSCH to HARQ-ACK feedback timing indication field in the DCI is "00", the value of K1 in the K1 set of PUCCH-sSCell is "2". According to the technical solution of method 800 of this application, in mode 1, the PDSCH to HARQ-ACK feedback timing indication field being "00" can always indicate a K1 value in the set of PCells. Therefore, after the network device sends the "deactivate" PUCCH-sSCell, it can receive the SPS HARQ-ACK bit on the PCell. According to the technical solution of method 800 of this application, in mode 2, since the PDSCH to HARQ-ACK feedback timing indication field being "00" can also indicate a K1 value in the set of PCells, for example, the K1 value is 1, after the network device sends the "deactivate" PUCCH-sSCell, it can receive the SPS HARQ-ACK bit on the PCell's time slot 9. However, assuming the PDSCH to HARQ-ACK feedback timing indication field is "11", according to method 2 in method 800, the value of K1 cannot be indicated in the PCell set. Therefore, the network device needs to retransmit the indication information indicating the value of K1 while sending the "deactivate" PUCCH-sSCell indication.

[0163] Furthermore, this application also considers that after the terminal device determines the time-domain position of transmitting the second PUCCH on the second cell according to the schemes of methods 600 and 800 of this application, if the time-domain position of the second PUCCH on the PCell overlaps with downlink symbols, or symbols used to transmit synchronization signal blocks (SSBs), or symbols of the control-resource set (CORESET) associated with the common search space of type 0 PDCCHs, and the second PUCCH cannot be transmitted, in this scenario, the terminal device can discard the PUCCH on the second cell (because it overlaps with downlink symbols). Specifically, the terminal device can discard the second PUCCH on the second cell in the following implementation.

[0164] Considering that although the SPS HARQ-ACK PUCCH is located in the second cell, the HARQ-ACK bit position corresponding to the candidate PDSCH of the SPS may or may not exist in the type 1 codebook of the first cell (specifically, whether the HARQ-ACK bit position corresponding to the candidate PDSCH of the SPS might exist in the type 1 codebook of the first cell depends at least on the subcarrier spacing of the first cell, the subcarrier spacing of the second cell, the K1 set on the first cell, and the current K1 value, which will not be described in detail in this application). In this scenario, discarding the second PUCCH can be implemented in the following way:

[0165] As an example: If there is no HARQ-ACK bit position corresponding to the candidate PDSCH of SPS in the type 1 codebook of PUCCH-sSCell, then the terminal device does not need to send the second PUCCH on PCell. The codebook to be sent on PUCCH-sSCell is unrelated to the candidate PDSCH of SPS on PCell and can be ignored.

[0166] As another example: If the HARQ-ACK bit position corresponding to the candidate PDSCH of SPS exists in the type 1 codebook of PUCCH-sSCell, then even if the terminal device does not send a second PUCCH on PCell, the HARQ-ACK bit position corresponding to the candidate PDSCH of SPS in the type 1 codebook of PUCCH-sSCell still needs to be considered. In this case, the HARQ-ACK bit position corresponding to the candidate PDSCH of SPS in the type 1 codebook of PUCCH-sSCell can be filled with "NACK".

[0167] For example, such as Figure 10As shown, assuming the subcarrier spacing of PCell is 30kHz, the subcarrier spacing of PUCCH-sSCell is 15kHz, the K1 set on PCell is {1, 3}, and the K1 set on PUCCH-sSCell is {1, 2, 3, 4}, and assuming the terminal device receives the PDSCH of SPS in slot 4 and the value of K1 is "3", according to the method of this application, the second PUCCH carrying the HARQ-ACK of the PDSCH of SPS should be discarded in slot 7. However, because the codebook to be transmitted on slot 3 of PUCCH-sSCell includes the HARQ-ACK bit positions corresponding to the PDSCH received from the SPS on slot 4 of PCell (this is because the codebook to be transmitted on slot 3 of PUCCH-sSCell includes the HARQ-ACK bit positions of the PDSCH in slots 0 (when the value of K1 in the K1 set of PUCCH-sSCell is "3"), 1 (when the value of K1 in the K1 set of PUCCH-sSCell is "2"), and 2 (when the value of K1 in the K1 set of PUCCH-sSCell is "1"), and also includes the HARQ-ACK bit positions of the PDSCH of the SPS on slot 4 of PCell (when the value of K1 in the K1 set of PCell is "1"). At this time, the slot 7 of the SCell overlapping with the slot of the SPSHARQ-ACK PUCCH on the PCell... In the type 1 codebook on 3, the HARQ-ACK bit position corresponding to the candidate PDSCH of SPS is filled with "NACK", and at this time, Kl corresponding to SPS PDSCH is equal to 1.

[0168] If the subcarrier spacing of the PCell is smaller than the subcarrier spacing of the PUCCH-sSCell, there will be multiple time slots on the PUCCH-sSCell that overlap with the time slot of the PUCCH carrying SPSHARQ-ACK on the PCell. In this case, a slot can be agreed upon by the protocol, and "NACK" can be padded to the HARQ-ACK bit position corresponding to the SPS candidate PDSCH in that slot. At this time, the K1 value on the PUCCH-sSCell corresponding to the SPSPDSCH is different from the K1 value on the PCell corresponding to the SPS PDSCH.

[0169] If the subcarrier spacing of PCell is the same as that of PUCCH-sSCell, then there is only one time slot on PUCCH-sSCell that overlaps with the time slot of PUCCH carrying SPSHARQ-ACK on PCell. In this case, "NACK" is also filled in the HARQ-ACK bit position corresponding to the SPS candidate PDSCH in that time slot. At this time, the K1 value on PUCCH-sSCell corresponding to SPS PDSCH is the same as the K1 value on PCell corresponding to SPS PDSCH.

[0170] Figure 11 This application provides a schematic flowchart of a communication method 900, which includes:

[0171] Step 901: The network device sends configuration information to the terminal device. Correspondingly, the terminal device receives the configuration information.

[0172] In this embodiment, the configuration information is used to configure a third PUCCH carrying third information for the second cell. The third PUCCH overlaps with the PUSCH in the time domain.

[0173] In this application, "overlapping in the time domain" can be understood as partial overlap in the time domain or complete overlap in the time domain.

[0174] In this embodiment, the third information may be, for example, SPS HARQ-ACK information, channel state information (CSI), or schedule request information (SR). That is, the third PUCCH can also be understood as a semi-static PUCCH.

[0175] Step 902: The network device sends the DCI to the terminal device. Correspondingly, the terminal device receives the DCI.

[0176] In one implementation, network devices can send DCI to terminal devices via PDCCH.

[0177] This DCI can be used to schedule downlink data; for example, it can be used to dynamically schedule PDSCH; and for another example, it can be used for BWP handover.

[0178] The DCI may include first indication information (e.g., cell indication field), which instructs the terminal device to send first HARQ-ACK information via the first PUCCH on the first cell. The first HARQ-ACK information is the HARQ-ACK information corresponding to the downlink data.

[0179] Optionally, in one implementation, the time-domain positions of the first PUCCH and PUSCH overlap.

[0180] Step 903: The network device sends a first PDSCH to the terminal device. This first PDSCH may be a dynamically scheduled PDSCH. Correspondingly, the terminal device receives the dynamically scheduled first PDSCH.

[0181] Step 904: The terminal device discards the third PUCCH.

[0182] Considering that although the SPS HARQ-ACK PUCCH is located in the second cell, the HARQ-ACK bit position corresponding to the candidate PDSCH of the SPS may or may not exist in the type 1 codebook of the first cell. In this scenario, discarding the third PUCCH can be implemented in the following way:

[0183] As an example: If there is no HARQ-ACK bit position corresponding to the candidate PDSCH of SPS in the type 1 codebook of PUCCH-sSCell, then the terminal device does not need to send the third PUCCH on PCell. The codebook to be sent on PUCCH-sSCell is unrelated to the candidate PDSCH of SPS on PCell and can be ignored.

[0184] As another example: If the HARQ-ACK bit position corresponding to the candidate PDSCH of SPS exists in the type 1 codebook of PUCCH-sSCell, then even if the terminal device does not send a third PUCCH on the PCell, the HARQ-ACK bit position corresponding to the candidate PDSCH of SPS on the type 1 codebook of PUCCH-sSCell still needs to be considered. In this case, the HARQ-ACK bit position corresponding to the candidate PDSCH of SPS can be filled with "NACK" in the type 1 codebook of PUCCH-sSCell. Then, in the type 1 codebook of the SCell where the slot of the SPS HARQ-ACK PUCCH is located overlaps with the slot of the PCell containing the PUCCH, the HARQ-ACK bit position corresponding to the candidate PDSCH of SPS can be filled with "NACK". If there are multiple overlapping slots, one slot can be selected, and the HARQ-ACK bit position corresponding to the candidate PDSCH of SPS in that slot can be filled with "NACK".

[0185] Based on the above technical solution, in this application, for scenarios where there are PUCCHs transmitting information in two cells respectively, if the third PUCCH carrying third information overlaps with the PUSCH in the time domain, the terminal device can discard the third PUCCH. This eliminates the need for the terminal device to multiplex the control channel in two cells (which can also be understood as "cross-cell") and then multiplex it into the corresponding PUSCH. At the same time, it can reduce the number of PUSCHs carrying uplink control information and simplify the multiplexing complexity of the terminal device.

[0186] In one implementation, if the time domain position of the PDCCH carrying DCI precedes the time domain position of the PUSCH, and the time domain position interval between the PDCCH and the PUSCH is greater than or equal to a first duration, the terminal device may discard the third PUCCH.

[0187] In another implementation, if the time domain position of the PDCCH carrying DCI is before the time domain position of the third PUCCH, and the time domain position interval between the PDCCH and the PUCCH is greater than or equal to the first duration, the terminal device can discard the third PUCCH.

[0188] This can also be understood as follows: in this application, whether the terminal device successfully receives the DCI will affect whether the terminal device discards the PUCCH on the PCell. Assuming that the terminal device needs 3 symbols to parse the DCI (in the case of the first duration), the terminal device needs to successfully parse the DCI before sending the PUSCH or before sending the third PUCCH.

[0189] In this embodiment, the first duration is at least X symbols. In one implementation, if the network device configures the UE with processing capability 2, X = 3 symbols when the subcarrier interval is 15kHz; X = 4.5 symbols when the subcarrier interval is 30kHz; and X = 9 symbols when the subcarrier interval is 60kHz. In another implementation, if the network device does not configure the UE with processing capability 2, X = 8 symbols when the subcarrier interval is 15kHz; X = 10 symbols when the subcarrier interval is 30kHz; X = 17 symbols when the subcarrier interval is 60kHz; and X = 20 symbols when the subcarrier interval is 120kHz. In yet another implementation, the first duration, i.e., X symbols, can be determined in seconds by the following formula: t = N³·(2048+144)·κ·2 -μ ·T c Where N3 represents the number of symbols (e.g., X above); κ is 64; μ represents the subcarrier spacing, T c = 1 / (4096×480kHz).

[0190] When the time domain positions of the first PUCCH and PUSCH do not overlap, the terminal device sends the first HARQ-ACK information through the first PUCCH. When the time domain positions of the first PUCCH and PUSCH overlap, the terminal device can send the first HARQ-ACK information through the PUSCH, which can also be understood as multiplexing the PUCCH onto the PUSCH. The PUSCH can be non-overlapping with the third PUCCH, that is, the network device guarantees that the PUSCH cannot overlap with both the first PUCCH and the third PUCCH simultaneously.

[0191] Step 905: On the second cell, the network device does not receive the third PUCCH.

[0192] Based on the above technical solution, in this embodiment, by providing a first duration, the network device can determine that the terminal device will discard the third PUCCH; that is, the network device can also determine that the third information will not be reused on the PUSCH. Therefore, the network device does not need to perform blind detection when detecting the PUSCH, reducing the detection complexity of the network device. Alternatively, it can be understood that if the first duration is not provided, the network device cannot determine whether the terminal device will discard the third PUCCH, nor can the network device determine whether the third information has been reused on the PUSCH. Therefore, when detecting the PUSCH, the network device needs to perform blind detection to check whether the third information has been reused on the PUSCH, resulting in high detection complexity.

[0193] For example, Figure 12 (a) shows that when the time domains of the third PUCCH and PUSCH carrying the third information of the PDSCH of SPS overlap, the terminal device will discard the third PUCCH after successfully parsing the DCI, provided that the subcarrier spacing is the same. Figure 12 (b) shows that when the time domains of the third PUCCH and PUSCH carrying the third information of the PDSCH of SPS overlap under different subcarrier spacings, the terminal device will discard the third PUCCH after successfully parsing the DCI.

[0194] Optionally, the third PUCCH may overlap in the time domain with downlink symbols configured by the network device, or symbols used to transmit SSBs, or symbols of the CORESET associated with the common search space of a type 0 PDCCH, such as... Figure 12 (a) and Figure 12 As shown in (b) of the diagram.

[0195] Optionally, the time slot where the third PUCCH is located overlaps with the time slot where the first PUCCH is located in the time domain.

[0196] In this embodiment, the PUSCH can be the PUSCH of the first cell, the PUSCH of the second cell, or the PUSCH of other cells besides the first and second cells, and is not limited thereto.

[0197] In the various embodiments of this application, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments are consistent and can be referenced mutually. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships, thereby ensuring that different embodiments can be combined with each other.

[0198] It is understood that in this application, "under certain circumstances" and "if" both refer to the device making a corresponding processing under certain objective circumstances, and are not limited to a time, nor do they require the device to make a judgment when it is implemented, nor do they mean that there are other limitations.

[0199] The above primarily describes the solutions provided in this application from the perspective of interactions between various nodes. It is understood that each node, such as a terminal device or network device, includes corresponding hardware structures and / or software modules to perform the aforementioned functions. Those skilled in the art should recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0200] It is understood that, in order to achieve the functions in the above embodiments, the network devices and terminals include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0201] Figure 13 and Figure 14 The diagram illustrates the possible communication devices provided in the embodiments of this application. These communication devices can be used to implement the functions of the terminal or network device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0202] In embodiments of this application, the communication device may be as follows: Figure 1One of the terminals 120a-120j shown can also be as follows: Figure 1 The network devices 110a or 110b shown can also be modules (such as chips) applied to terminals or network devices. Figure 13 As shown, the device 100 may include a transceiver unit 110 and a processing unit 120.

[0203] When the device 100 is used to implement the function of the terminal device in the method 600 of this application embodiment, the transceiver unit 110 is used to receive downlink control information, the downlink control information includes second indication information, the second indication information indicates a first value, the first value is a value in a first set, and the second set includes the first value; the processing unit 120 is used to determine the time domain position of the second PUCCH according to the first value; the transceiver unit 110 is used to send second HARQ-ACK information through the second PUCCH.

[0204] The processing unit 120 is used to determine the time domain position of the first PUCCH based on the first value. The transceiver unit 110 is used to send the first HARQ-ACK information through the first PUCCH.

[0205] When the device 100 is used to implement the functions of the terminal device in the method 800 of this application embodiment, the transceiver unit 110 is used to send downlink control information, which includes third indication information indicating values ​​in a first set and values ​​in a second set. The processing unit 120 is used to determine the time-domain location of the first PUCCH and the time-domain location of the second PUCCH according to the third indication information; the transceiver unit 110 is used to send the first HARQ-ACK information through the first PUCCH; the transceiver unit 110 is used to send the second HARQ-ACK information through the second PUCCH on the second cell. The processing unit 120 is used to determine the time-domain location of the first PUCCH according to the third indication information and the first set.

[0206] When the device 100 is used to implement the function of the terminal device in the method 900 of this application embodiment: the transceiver unit 110 is used to receive configuration information, the configuration information is used to configure a third PUCCH carrying third information for the second cell, the third PUCCH and PUSCH overlap in the time domain; the transceiver unit 110 is used to receive downlink control information, the downlink control information is used to schedule downlink data, the downlink control information includes first indication information, the first indication information instructs the terminal device to send a first HARQ-ACK information through the first PUCCH in the first cell, the first HARQ-ACK information is the HARQ-ACK information corresponding to the downlink data; the processing unit 120 is used to discard the third PUCCH.

[0207] When the time domain position of the PDCCH carrying downlink control information received by the transceiver unit 110 is before the time domain position of the PUSCH, and the time domain position interval between the PDCCH and the PUSCH is greater than or equal to the first duration, the processing unit 120 discards the third PUCCH.

[0208] When the communication device 100 is used to implement the function of the network device in the embodiment of method 600: the transceiver unit 110 is used to send downlink control information, the downlink control information includes second indication information, the second indication information indicates a first value, the first value is a value in a first set, and the second set includes the first value; the processing unit 120 is used to determine the time domain position of the second PUCCH according to the first value; the transceiver unit 110 is used to receive the second HARQ-ACK information through the second PUCCH.

[0209] The processing unit 120 is used to receive the first HARQ-ACK information via the first PUCCH.

[0210] When the communication device 100 is used to implement the functions of the network device in the embodiment of method 800: the transceiver unit 110 is used to send downlink control information, which includes third indication information indicating values ​​in a first set and values ​​in a second set. The processing unit 120 is used to receive first HARQ-ACK information through the first PUCCH; the transceiver unit 110 is used to receive second HARQ-ACK information through the second PUCCH.

[0211] When the communication device 100 is used to implement the function of the network device in the embodiment of method 900: the transceiver unit 110 is used to send configuration information, which is used to configure a third PUCCH carrying third information for the second cell, and the third PUCCH and PUSCH overlap in the time domain; the transceiver unit 110 is used to send downlink control information, which is used to schedule downlink data, and the downlink control information includes first indication information, which instructs the terminal device to send first HARQ-ACK information through the first PUCCH in the first cell, and the first HARQ-ACK information is the HARQ-ACK information corresponding to the downlink data; the processing unit is used to discard the third PUCCH.

[0212] When the time domain position of the PDCCH carrying downlink control information sent by the transceiver unit 110 is before the time domain position of the PUSCH, and the time domain position interval between the PDCCH and the PUSCH is greater than or equal to the first duration, the processing unit 120 does not receive the third PUCCH.

[0213] For a more detailed description of the processing unit 120 and the transceiver unit 110, please refer to [link / reference needed]. Figure 6 , Figure 11 The relevant descriptions in the method embodiments shown are directly obtained and will not be repeated here.

[0214] Figure 14 This is a schematic block diagram of a communication device 200 provided in an embodiment of this application. As shown, the device 200 includes at least one processor 220. The processor 220 is coupled to a memory and is used to execute instructions stored in the memory to transmit and / or receive signals. Optionally, the device 200 also includes a memory 230 for storing instructions. Optionally, the device 200 also includes a transceiver 210, and the processor 220 controls the transceiver 210 to transmit and / or receive signals.

[0215] It should be understood that the processor 220 and memory 230 described above can be combined into a single processing device, with the processor 220 executing the program code stored in the memory 230 to achieve the aforementioned functions. In specific implementations, the memory 230 can be integrated into the processor 220 or independent of the processor 220.

[0216] It should also be understood that transceiver 210 may include a transceiver (or receiver) and a transmitter (or transmitter). The transceiver may further include an antenna, and the number of antennas may be one or more. Transceiver 210 may be a communication interface or interface circuitry.

[0217] Specifically, the transceiver 210 in the device 200 can correspond to the transceiver unit 110 in the device 100, and the processor 220 in the device 200 can correspond to the processing unit 120 in the device 100.

[0218] It should be understood that the specific process by which each transceiver processor performs the corresponding steps described above has been explained in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0219] When the communication device 200 is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from other modules (such as radio frequency modules or antennas) in the terminal, which is sent to the terminal by the network device; or, the terminal chip sends information to other modules (such as radio frequency modules or antennas) in the terminal, which is sent to the network device by the terminal.

[0220] When the aforementioned communication device is a module applied to a network device, the network device module implements the functions of the network device in the above method embodiments. The network device module receives information from other modules (such as a radio frequency module or antenna) in the network device, which is information sent by the terminal to the network device; or, the network device module sends information to other modules (such as a radio frequency module or antenna) in the network device, which is information sent by the network device to the terminal. Here, the network device module can be the baseband chip of the network device, or a DU (Digital Unit) or other modules. The DU can be a DU under an Open Radio Access Network (O-RAN) architecture.

[0221] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0222] According to the method provided in the embodiments of this application, this application also provides a computer program product, which stores computer program code. When the computer program code is run on a computer, it causes the computer to execute the method executed by the terminal device in any one of the embodiments of method 600, method 800, and method 900; or, it causes the computer to execute the method executed by the network device in any one of the embodiments of method 600, method 800, and method 900.

[0223] According to the method provided in the embodiments of this application, this application also provides a computer-readable medium storing program code, which, when run on a computer, causes the computer to execute the method executed by the terminal device in any one of the embodiments of method 600, method 800, and method 900; or causes the computer to execute the method executed by the network device in any one of the embodiments of method 600, method 800, and method 900.

[0224] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes a terminal device and a network device. The terminal device is used to execute method 600 and the network is used to execute method 600; or, the terminal device is used to execute method 800 and the network is used to execute method 800; or, the terminal device is used to execute method 900 and the network is used to execute method 900.

[0225] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0226] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a network device or terminal. The processor and storage medium can also exist as discrete components in a network device or terminal.

[0227] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0228] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0229] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A hybrid automatic repeat request acknowledgment (HARQ-ACK) information feedback method, executed by a terminal device or a module within the terminal device, characterized in that, include: The terminal device receives downlink control information from a network device. This downlink control information is used to schedule downlink data. The downlink control information includes first indication information, which instructs the terminal device to send first HARQ-ACK information via a first physical uplink control channel in a first cell. The first HARQ-ACK information is the HARQ-ACK information corresponding to the downlink data. The downlink control information is also used to activate semi-static scheduling. The downlink control information further includes second indication information, which indicates a first value. The first value is a value in a first set, and the second set includes the first value. The values ​​in the first set indicate the time slot offset between the physical downlink shared channel carrying the downlink data and the first physical uplink control channel carrying the first HARQ-ACK information. The values ​​in the second set indicate the time slot offset between the physical downlink shared channel carrying the semi-static scheduled data and the second physical uplink control channel carrying the second HARQ-ACK information, where the second HARQ-ACK information is the HARQ-ACK information corresponding to the semi-static scheduled data. Based on the first value, determine the time domain location of the second physical uplink control channel; On the second cell, the second HARQ-ACK information is sent through the second physical uplink control channel.

2. The method according to claim 1, characterized in that, The method further includes: Based on the first value, determine the time domain location of the first physical uplink control channel; On the first cell, the first HARQ-ACK information is sent through the first physical uplink control channel.

3. The method according to claim 1 or 2, characterized in that, The first cell is a secondary cell for physical uplink control channel handover, and the second cell is either the primary cell or a secondary cell for physical uplink control channel handover.

4. A hybrid automatic repeat request acknowledgment (HARQ-ACK) information feedback method, executed by a network device or a module within a network device, characterized in that, include: Downlink control information is sent to the terminal device. This downlink control information is used to schedule downlink data. The downlink control information includes first indication information, which instructs the terminal device to send first HARQ-ACK information on the first cell via a first physical uplink control channel. This first HARQ-ACK information is the HARQ-ACK information corresponding to the downlink data. The downlink control information is also used to activate semi-static scheduling. The downlink control information further includes second indication information, which indicates a first value. The first value is a value in a first set, and the second set includes the first value. The values ​​in the first set indicate a time slot offset between the physical downlink shared channel carrying the downlink data and the first physical uplink control channel carrying the first HARQ-ACK information. The values ​​in the second set indicate a time slot offset between the physical downlink shared channel carrying the semi-statically scheduled data and the second physical uplink control channel carrying the second HARQ-ACK information, where the second HARQ-ACK information is the HARQ-ACK information corresponding to the semi-statically scheduled data. In the second cell, the second HARQ-ACK information is received through the second physical uplink control channel, wherein the number of time slots between the time domain location of the second physical uplink control channel and the physical downlink shared channel carrying the semi-static scheduling data is the first value.

5. The method according to claim 4, characterized in that, The method further includes: In the first cell, the first HARQ-ACK information is received through the first physical uplink control channel, wherein the time domain position of the first physical uplink control channel is the number of time slots between it and the physical downlink shared channel carrying the downlink data, which is the first value.

6. The method according to claim 4 or 5, characterized in that, The first cell is a secondary cell for physical uplink control channel handover, and the second cell is either the primary cell or a secondary cell for physical uplink control channel handover.

7. A communication device, characterized in that, It includes a unit or module for performing the method as described in any one of claims 1 to 3, or includes a unit or module for performing the method as described in any one of claims 4 to 6.

8. A communication device, characterized in that, The device includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor is used to implement the method as described in any one of claims 1 to 3, or to implement the method as described in any one of claims 4 to 6, through logic circuits or execution code instructions.

9. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes instructions for performing the method as described in any one of claims 1 to 6.

Images