A method and apparatus for feeding back HARQ-ACK information

By determining the HARQ-ACK codebook based on the number of cells scheduled by DCI, and adopting a sub-codebook structure, the problem of high complexity in generating HARQ-ACK codebooks in wireless communication systems is solved, enabling correct understanding and efficient transmission under various scheduling conditions.

CN118555672BActive Publication Date: 2025-10-31HUAWEI TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310231435.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-02-27
Publication Date
2025-10-31
Estimated Expiration
2043-02-27

AI Technical Summary

Technical Problem

In wireless communication systems, when a terminal device generates a HARQ-ACK codebook after receiving multiple downlink control messages, there is a problem that it cannot correctly understand the dynamic HARQ-ACK codebook under various scheduling conditions. This is especially true when multiple cells are scheduled with a single downlink control message (single DCI), which increases the complexity of codebook generation.

Method used

The HARQ-ACK codebook is determined based on the number of cells scheduled by different DCIs. A sub-codebook structure is used to generate and feed back HARQ-ACK information, including HARQ-ACK information of data scheduled by the first DCI and the second DCI. The HARQ-ACK information of SPS data of semi-persistent scheduling is appended to the end to reduce the generation complexity.

Benefits of technology

It effectively reduces the complexity of generating the HARQ-ACK codebook, ensuring that terminal devices and network devices can correctly understand the HARQ-ACK codebook under various scheduling conditions, thereby improving transmission efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118555672B_ABST
    Figure CN118555672B_ABST
Patent Text Reader

Abstract

This application provides a method and apparatus for feeding back HARQ-ACK information. The terminal device determines the position of the HARQ-ACK information of the data scheduled by the received Downlink Control Information (DCI) within the HARQ-ACK codebook based on the number of cells simultaneously scheduled by that DCI. For example, if the first and second DCIs each schedule data from only one cell, the HARQ-ACK information for the data scheduled by these two DCIs is in the first HARQ-ACK sub-codebook; if the third DCI schedules data from two or more cells, the HARQ-ACK information for the data scheduled by the third DCI is in the second HARQ-ACK sub-codebook; the second HARQ-ACK sub-codebook is positioned after the first HARQ-ACK sub-codebook. Therefore, the terminal device and network device can correctly understand the dynamic HARQ-ACK codebook generation method when multiple scheduling scenarios exist simultaneously, avoiding the problem of incorrect HARQ-ACK codebook reception.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] In a wireless system, after a terminal device receives multiple downlink control information (DCI) messages from a base station, it receives multiple physical downlink share channels (PDSCHs) based on these DCIs. For each PDSCH, the terminal device needs to provide a hybrid automatic repeat request acknowledgement (HARQ-ACK) response. When these multiple HARQ-ACKs need to be responded to on a physical uplink control channel (PUCCH), the multiple HARQ-ACK messages constitute a dynamic HARQ-ACK codebook. Current standard discussions have introduced single downlink control information (single DCI), which can schedule the PDSCHs of one or more cells.

[0003] For legacy DCI, its corresponding HARQ-ACK codebook consists of HARQ-ACK information from downlink semi-persistent scheduling (DL SPS) appended to the HARQ-ACK information from dynamic grant (DG). For single DCI, its corresponding HARQ-ACK codebook consists of a first sub-codebook including HARQ-ACK information for scheduling one cell, and a second sub-codebook including HARQ-ACK information for scheduling more than one cell. Summary of the Invention

[0004] This application provides a method for feeding back HARQ-ACK information. By determining the HARQ-ACK codebook based on the number of cells in two different DCI scheduling schemes, the terminal device and network device can correctly understand the generation method of the dynamic HARQ-ACK codebook when multiple scheduling schemes exist simultaneously, thereby avoiding the problem of HARQ-ACK codebook not being received correctly.

[0005] Firstly, a method for feeding back HARQ-ACK information is provided. This method can be executed by a terminal device, or by a component of the terminal device (such as a chip or circuit). There is no limitation on this. For ease of description, the following explanation will take execution by a terminal device as an example.

[0006] The method includes: receiving a first downlink control information (DCI) from a network device, wherein the first DCI schedules data from one cell; receiving a second DCI from the network device, wherein the second DCI has a DCI format that can schedule data from two or more cells or data from one cell; determining a HARQ-ACK codebook based on the number of cells scheduled by the first DCI and the second DCI, wherein the HARQ-ACK codebook includes HARQ-ACK information for data scheduled by the first DCI and the second DCI, as well as HARQ-ACK information for data scheduled by the first semi-persistent scheduling (SPS); and feeding back the HARQ-ACK codebook to the network device.

[0007] Based on the above scheme, the terminal device generates a HARQ-ACK codebook according to the number of cells scheduled by various DCIs and sends it to the network device. This enables the terminal device and the network device to correctly understand the generation method of the dynamic HARQ-ACK codebook when multiple scheduling conditions exist simultaneously, thereby avoiding the problem of HARQ-ACK codebook not being received correctly.

[0008] In one possible implementation, the first DCI has a DCI format that can only schedule data from one cell, the second DCI schedules data from only one cell, the HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, the first HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the first DCI and HARQ-ACK information of the data scheduled by the second DCI, and the HARQ-ACK information of the first SPS data is appended to the first HARQ-ACK sub-codebook.

[0009] Based on the above scheme, when the terminal device receives legacy DCI and single DCI that schedules data from one cell, the HARQ-ACK information of the data scheduled by these two DCIs is included in a sub-codebook of the HARQ-ACK codebook, and the HARQ-ACK information of the semi-persistent scheduling SPS data is placed at the end of the HARQ-ACK codebook. This reduces the number of times the corresponding HARQ-ACK information for semi-persistent scheduling is generated, eliminates the need to judge and distinguish the activation DCI format for semi-persistent scheduling, and reduces the complexity of generating the HARQ-ACK codebook.

[0010] In one possible implementation, the first DCI has a DCI format that can schedule data from two or more cells or data from one cell. The second DCI schedules data from two or more cells. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the first DCI, and the second HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the second DCI. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook, and the HARQ-ACK information of the first SPS data is appended to the second HARQ-ACK sub-codebook.

[0011] Based on the above scheme, when the terminal device receives a single DCI that schedules data from one cell and a single DCI that schedules data from two or more cells, the HARQ-ACK information of the data scheduled by these two DCIs is included in the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook, respectively. The HARQ-ACK information of the semi-persistent scheduling SPS data is placed at the end of the HARQ-ACK codebook. This reduces the number of times the HARQ-ACK information corresponding to the semi-persistent scheduling is generated, eliminates the need to judge and distinguish the activation DCI format for the semi-persistent scheduling, and reduces the complexity of generating the HARQ-ACK codebook.

[0012] In one possible implementation, the first DCI uses a DCI format that can only schedule data from one cell, while the second DCI schedules data from two or more cells. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information for the data scheduled by the first DCI, and the second HARQ-ACK sub-codebook includes HARQ-ACK information for the data scheduled by the second DCI. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook, and the HARQ-ACK information for the first SPS data is appended to the second HARQ-ACK sub-codebook.

[0013] Based on the above scheme, when the terminal device receives legacy DCI and single DCI that schedules data from two or more cells, the HARQ-ACK information of the data scheduled by these two DCIs is included in the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook, respectively. The HARQ-ACK information of the semi-persistent scheduling SPS data is placed at the end of the HARQ-ACK codebook. This reduces the number of times the corresponding HARQ-ACK information for semi-persistent scheduling is generated, eliminates the need to judge and distinguish the activation DCI format for semi-persistent scheduling, and reduces the complexity of generating the HARQ-ACK codebook.

[0014] In one possible implementation, the first DCI has a DCI format that can only schedule data from one cell, the second DCI schedules data from only one cell, the HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, the first HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the first DCI and HARQ-ACK information of the data scheduled by the second DCI, and the method further includes: receiving a third DCI from a network device, the third DCI having a DCI format that can schedule data from two or more cells or data from one cell, the third DCI scheduling data from two or more cells, the HARQ-ACK codebook also includes a second HARQ-ACK sub-codebook, the second HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the third DCI, the second HARQ-ACK sub-codebook is located after the first HARQ-ACK sub-codebook in the HARQ codebook, and the HARQ-ACK information of the first SPS data is appended after the second HARQ-ACK sub-codebook.

[0015] Based on the above scheme, when the terminal device receives legacy DCI (i.e., the first DCI), single DCI (i.e., the second DCI) that schedules data from one cell, and single DCI (i.e., the third DCI) that schedules data from two or more cells, the HARQ-ACK information of the data scheduled by the first DCI and the HARQ-ACK information of the data scheduled by the second DCI are included in the first HARQ-ACK sub-codebook, and the HARQ-ACK information of the data scheduled by the third DCI is included in the second HARQ-ACK sub-codebook. The HARQ-ACK information of the semi-persistent scheduling SPS data is placed at the end of the HARQ-ACK codebook. This reduces the number of times the HARQ-ACK information corresponding to the semi-persistent scheduling is generated, eliminates the need to judge and distinguish the activation DCI format for the semi-persistent scheduling, and reduces the generation complexity of the HARQ-ACK codebook.

[0016] In one possible implementation, the HARQ-ACK codebook further includes HARQ-ACK information for the second SPS data. The position of the HARQ-ACK information for the second SPS data in the HARQ-ACK codebook is after the position of the first HARQ-ACK sub-codebook and before the position of the second HARQ-ACK sub-codebook. The reception of the second SPS data is activated by a fourth DCI, the DCI format of which can only schedule data from one cell, or the DCI format of which can schedule data from two or more cells as well as data from one cell, and the fourth DCI simultaneously activates the reception of SPS data from only one cell. The reception of the first SPS data is activated by a fifth DCI, the DCI format of which can schedule data from two or more cells as well as data from one cell, and the fifth DCI simultaneously activates the reception of SPS data from two or more cells.

[0017] Based on the above scheme, when the terminal device receives the first DCI, the second DCI, and the third DCI, it includes the HARQ-ACK information of the data scheduled by the first DCI and the HARQ-ACK information of the data scheduled by the second DCI in the first HARQ-ACK sub-codebook, and the HARQ-ACK information of the data scheduled by the third DCI in the second HARQ-ACK sub-codebook. The HARQ-ACK information of SPS data that has activated one cell is placed between the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook, and the HARQ-ACK information of data that has activated two or more cells is placed at the end of the HARQ-ACK codebook. In this way, the existing scheme is reused as much as possible to generate the HARQ-ACK codebook, reducing protocol modifications and reducing the generation complexity of the HARQ-ACK codebook to a certain extent.

[0018] Secondly, a method for feeding back HARQ-ACK information is provided. This method can be executed by a network device, or by a component of the network device (such as a chip or circuit); there is no limitation on this. For ease of description, the following explanation uses execution by a network device as an example. This second aspect is a network device-side method corresponding to the first aspect, and therefore can also achieve the beneficial effects that the terminal device can achieve in the first aspect.

[0019] The method includes: sending a first downlink control information (DCI) to a terminal device, wherein the first DCI schedules data from one cell; sending a second DCI to the terminal device, wherein the second DCI has a DCI format that can schedule data from two or more cells or data from one cell; and receiving a HARQ-ACK codebook fed back from the terminal device, wherein the HARQ-ACK codebook is determined based on the number of cells scheduled by the first DCI and the second DCI, and the HARQ-ACK codebook includes HARQ-ACK information for data scheduled by the first DCI and the second DCI, as well as HARQ-ACK information for data scheduled by the first semi-persistent scheduling (SPS).

[0020] In one possible implementation, the first DCI has a DCI format that can only schedule data from one cell, the second DCI schedules data from only one cell, the HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, the first HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the first DCI and HARQ-ACK information of the data scheduled by the second DCI, and the HARQ-ACK information of the first SPS data is appended to the first HARQ-ACK sub-codebook.

[0021] In one possible implementation, the first DCI has a DCI format that can schedule data from two or more cells or data from one cell. The second DCI schedules data from two or more cells. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the first DCI, and the second HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the second DCI. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook, and the HARQ-ACK information of the first SPS data is appended to the second HARQ-ACK sub-codebook.

[0022] In one possible implementation, the first DCI uses a DCI format that can only schedule data from one cell, while the second DCI schedules data from two or more cells. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information for the data scheduled by the first DCI, and the second HARQ-ACK sub-codebook includes HARQ-ACK information for the data scheduled by the second DCI. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook, and the HARQ-ACK information for the first SPS data is appended to the second HARQ-ACK sub-codebook.

[0023] In one possible implementation, the first DCI has a DCI format that can only schedule data from one cell, the second DCI schedules data from only one cell, the HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, the first HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the first DCI and HARQ-ACK information of the data scheduled by the second DCI, and the method further includes: sending a third DCI to the terminal device, the third DCI having a DCI format that can schedule data from two or more cells or data from one cell, the third DCI scheduling data from two or more cells, the HARQ-ACK codebook also includes a second HARQ-ACK sub-codebook, the second HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the third DCI, the second HARQ-ACK sub-codebook is located after the first HARQ-ACK sub-codebook in the HARQ codebook, and the HARQ-ACK information of the first SPS data is appended after the second HARQ-ACK sub-codebook.

[0024] In one possible implementation, the HARQ-ACK codebook further includes HARQ-ACK information for the second SPS data. The position of the HARQ-ACK information for the second SPS data in the HARQ-ACK codebook is after the position of the first HARQ-ACK sub-codebook and before the position of the second HARQ-ACK sub-codebook. The transmission of the second SPS data is activated by a fourth DCI, the fourth DCI having a DCI format that can only schedule data from one cell, or a DCI format that can schedule data from two or more cells as well as data from one cell, and the fourth DCI simultaneously activates the transmission of SPS data from only one cell. The transmission of the first SPS data is activated by a fifth DCI, the fifth DCI having a DCI format that can schedule data from two or more cells as well as data from one cell, and the fifth DCI simultaneously activates the transmission of SPS data from two or more cells.

[0025] Thirdly, a method for feeding back HARQ-ACK information is provided. This method can be executed by the terminal device, or by a component of the terminal device (such as a chip or circuit). There is no limitation on this. For ease of description, the following explanation will take execution by the terminal device as an example.

[0026] The method may include: receiving a sixth DCI from a network device, wherein the DCI format of the sixth DCI is a DCI format that can schedule data from two or more cells or data from one cell, the sixth DCI includes indication information for K1 cells, where K1 is an integer greater than 1 and less than or equal to N, and N is the maximum number of cells that the sixth DCI can schedule, and the indication information for each of the K1 cells includes any one of the following: information indicating the release of SPS PDSCH, information indicating a transmission configuration information status update, and information indicating a secondary cell hibernation; and sending a HARQ-ACK codebook to the network device, wherein the HARQ-ACK codebook includes a first bit group, the first bit group indicating whether the sixth DCI has been correctly received, and the first bit group includes one or more bits.

[0027] Based on the above scheme, the terminal device can send back HARQ-ACK information corresponding to no data scheduling to the network device in a unified feedback manner, without having to send back the indication information for each cell independently. This can save feedback bits, reduce codebook size, and improve transmission efficiency.

[0028] In one possible implementation, the method further includes: receiving a first DCI from a network device, the first DCI scheduling data from a first cell; the HARQ-ACK codebook further includes a second bit group, the second bit group indicating whether the data from the first cell has been correctly decoded, the length of the second bit group being the same as the length of the first bit group. The aforementioned HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, the first HARQ-ACK sub-codebook including a first bit group and a second bit group.

[0029] One possible implementation further includes receiving a second DCI from a network device, wherein the second DCI schedules data from K2 cells, where K2 is an integer greater than 1 and less than or equal to N. The aforementioned HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes a first bit group and a second bit group. The second HARQ-ACK sub-codebook includes N third bit groups, where K2 of the N third bit groups respectively indicate whether the data from the K2 cells has been correctly decoded. The bit values ​​of N-K2 of the N third bit groups are predefined values.

[0030] One possible implementation further includes: receiving a third DCI from a network device, the third DCI scheduling data from M cells, the third DCI also including indication information for P cells, the M cells and P cells being different cells, M and P being positive integers less than N, and M+P being less than or equal to N; the second HARQ-ACK subcodebook also includes N fourth bit groups, M of the N fourth bit groups indicating whether the data of each of the M cells has been correctly decoded, P of the N fourth bit groups indicating whether the indication information of each of the P cells has been correctly received, and the bit values ​​of NMP of the N fourth bit groups being predefined values.

[0031] Fourthly, a method for feeding back HARQ-ACK information is provided. This method can be executed by a network device, or by a component of the network device (such as a chip or circuit); there is no limitation on this. For ease of description, the following explanation uses execution by a network device as an example. This fourth aspect is a network device-side method corresponding to the third aspect, and therefore can also achieve the beneficial effects that the terminal device can achieve in the first aspect.

[0032] The method includes: sending a sixth DCI to a terminal device, wherein the DCI format of the sixth DCI is a DCI format that can schedule data from two or more cells or data from one cell; the sixth DCI includes indication information for K1 cells, where K1 is an integer greater than 1 and less than or equal to N, and N is the maximum number of cells that the sixth DCI can schedule; the indication information for each of the K1 cells includes any one of the following: information indicating the release of SPS PDSCH, information indicating a transmission configuration information status update, or information indicating a secondary cell hibernation; and receiving a HARQ-ACK codebook from the terminal device, wherein the HARQ-ACK codebook includes a first bit group, the first bit group indicating whether the sixth DCI has been correctly received, and the first bit group includes one or more bits.

[0033] In one possible implementation, the method further includes: sending a first DCI to a terminal device, the first DCI scheduling data from a first cell; the HARQ-ACK codebook further includes a second bit group, the second bit group indicating whether the data from the first cell has been correctly decoded, the length of the second bit group being the same as the length of the first bit group. The aforementioned HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, the first HARQ-ACK sub-codebook including a first bit group and a second bit group.

[0034] One possible implementation further includes sending a second DCI to a terminal device, wherein the second DCI schedules data from K2 cells, where K2 is an integer greater than 1 and less than or equal to N. The aforementioned HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes a first bit group and a second bit group. The second HARQ-ACK sub-codebook includes N third bit groups, where K2 of the N third bit groups respectively indicate whether the data from the K2 cells has been correctly decoded. The bit values ​​of N-K2 of the N third bit groups are predefined values. One possible implementation further includes: sending a third DCI to a terminal device, the third DCI scheduling data from M cells, the third DCI also including indication information for P cells, the M cells and P cells being different cells, M and P being positive integers less than N, and M+P being less than or equal to N; the second HARQ-ACK subcodebook also includes N fourth bit groups, M of the N fourth bit groups indicating whether the data of each of the M cells has been correctly decoded, P of the N fourth bit groups indicating whether the indication information of each of the P cells has been correctly received, and the bit values ​​of NMP of the N fourth bit groups being predefined values.

[0035] Fifthly, a communication device is provided, including a unit for performing the method shown in the first or third aspect above. The communication device may be a terminal device, or a chip or module disposed in a terminal device.

[0036] In a sixth aspect, a communication device is provided, including a unit for performing the methods shown in the second or fourth aspect above. The communication device may be a network device, or a chip or module disposed in a network device.

[0037] A seventh aspect provides a communication apparatus, the apparatus comprising: a memory for storing a program; and at least one processor for executing the computer program or instructions stored in the memory to perform a method of any of the possible implementations of the first to fourth aspects described above.

[0038] Eighthly, this application provides a processor for performing the methods provided in the above aspects.

[0039] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0040] A ninth aspect provides a computer-readable storage medium storing program code for execution by a device, the program code being used to perform a method of any of the possible implementations of the first to fourth aspects described above.

[0041] In a tenth aspect, a computer program product comprising instructions is provided, which, when run on a computer, causes the computer to perform any of the possible implementations of the first to fourth aspects described above.

[0042] Eleventhly, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions stored in a memory through the communication interface and executing a method of any one of the possible implementations of the first to fourth aspects described above.

[0043] Optionally, as one implementation, the chip also includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is used to perform the method of any of the possible implementations of the first to fourth aspects described above.

[0044] In a twelfth aspect, a communication system is provided, including one or more of the terminal equipment and network equipment mentioned above. Attached Figure Description

[0045] Figure 1 A schematic diagram of the architecture of a communication system 1000 applicable to embodiments of this application is shown.

[0046] Figure 2 A schematic flowchart of a method 400 for feeding back HARQ-ACK information according to an embodiment of this application is shown.

[0047] Figure 3 A schematic flowchart of a method 500 for feeding back HARQ-ACK information according to an embodiment of this application is shown.

[0048] Figure 4 A schematic block diagram of a communication device 600 provided in an embodiment of this application is shown.

[0049] Figure 5 A schematic block diagram of another communication device 700 provided in an embodiment of this application is shown. Detailed Implementation

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

[0051] 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 1 This 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.

[0052] It should be understood that the communication system architecture shown above is merely an illustrative example, and the communication system architecture applicable to the embodiments of this application is not limited thereto. Any communication system architecture capable of realizing the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0053] Wireless access network equipment is an access device that enables terminals to access a communication system wirelessly. Wireless access network equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in 5G mobile communication systems, a next-generation base station in 6G mobile communication systems, 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). The CU here performs the functions of the radio resource control protocol and packet data convergence protocol (PDCP) 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 medium access control (MAC) 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 the 3rd Generation Partnership Project (3GPP). The 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 The node in 110b) 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, network equipment is used as a shorthand for wireless access network equipment, and base station is used as an example of wireless access network equipment.

[0054] A terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminals can also be called terminal equipment, user equipment (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 technology or device form used in the terminal.

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

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

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

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

[0059] 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 the serving cell, it is also subject to interference from signals from neighboring cells.

[0060] The following explanations or introductions of some technical terms or concepts used in this application are provided for ease of reading.

[0061] 1. Dynamic grant (DG):

[0062] In dynamic scheduling, a DCI indicates the scheduling information of a PDSCH or Physical Uplink Shared Channel (PUSCH). The DCI includes time-domain resources, frequency-domain resources, modulation and coding scheme, HARQ-related information, etc. After detecting a DCI, the terminal device receives the PDSCH or sends the PUSCH according to the DCI's indication information, and then detects the next DCI, further receiving or sending the PDSCH according to the DCI's indication information, and so on. Dynamic scheduling also includes the data retransmission scheduling of the PDSCH corresponding to a specific HARQ process in semi-persistent scheduling. Dynamically scheduled DCIs include: DCIs that schedule PDSCH reception, and DCIs that do not schedule PDSCH reception (DCIs without PDSCH scheduling).

[0063] 2. Semi-persistent scheduling (SPS):

[0064] In semi-persistent scheduling, a DCI can indicate scheduling information for several (persistent) PDSCHs or PUSCHs. Once the terminal device receives the DCI, it begins periodically receiving PDSCHs or sending PUSCHs until it detects a DCI deactivating this persistent scheduling. Only then does the terminal device stop receiving PDSCHs or sending PUSCHs for semi-persistent scheduling. SPS PDSCHs consist of two parts: the first PDSCH scheduled with the SPS-activated DCI, and the SPSPDSCH reception without a corresponding PDCCH. During this persistent scheduling period, the terminal device does not need to detect DCIs again; it only needs to periodically receive PDSCHs on the time-frequency resources indicated by the PDCCH corresponding to the activated SPS, according to the period corresponding to each SPS configuration. When a PDSCH corresponding to a HARQ process is decoded incorrectly, and the base station performs retransmission scheduling, the UE needs to listen to the DCI to retransmit the corresponding HARQ process's PDSCH. The method for generating the corresponding HARQ-ACK information for SPS PDSCH reception can be found in the description in 3GPP communication protocol 38.213, and will not be repeated here.

[0065] 3. No PDSCH scheduling:

[0066] When a base station sends a DCI to a terminal device, if the DCI does not contain PDSCH scheduling information (such as time-domain information, frequency-domain information, etc.), but the terminal device still needs to provide HARQ-ACK information feedback to the DCI, then the DCI is called a DCI without PDSCH scheduling (or a DCI without data scheduling). The HARQ-ACK information that provides scheduling feedback without PDSCH can also be called the DCI corresponding to the HARQ-ACK information that does not contain scheduling (associated HARQ-ACK information without scheduling PDSCH reception).

[0067] Specifically, there are three types of PDSCH-less scheduling that require HARQ-ACK feedback:

[0068] 1) DCI indicates that DL SPS is deactivated or released (SPS PDSCH release);

[0069] 2) The DCI indicated that the secondary cell was entering dormancy but did not schedule a PDSCH reception;

[0070] 3) The DCI indicates an update to the Transmission Configuration Information state (TCI state) and no PDSCH is scheduled for reception.

[0071] 4) DCI indicates that the terminal device sends HARQ-ACK information for all processes in all cells without PDSCH scheduling. DCI includes a one-shot HARQ-ACK request field.

[0072] 4. Dynamic HARQ-ACK codebook:

[0073] In the 3rd generation partnership project (3GPP), the dynamic HARQ-ACK codebook is also called the Type-2 HARQ-ACK codebook. The terminal device receives DCIs that indicate the scheduling of PDSCH (DCIs may not schedule PDSCH, for example, DCIs indicating the release of SPS do not schedule PDSCH) and PUCCH. The UE receives the PDSCH based on the DCIs and then sends HARQ-ACKs back to the base station via PUCCH. A HARQ-ACK information bit of 0 indicates a negative acknowledgement (NACK), and a HARQ-ACK information bit of 1 indicates a positive acknowledgement (ACK). When the UE receives multiple DCIs, it needs to send a HARQ-ACK for each downlink data. The information bits of multiple HARQ-ACKs constitute a HARQ-ACK codebook. The number of HARQ-ACK information bits is related to the number of DCIs scheduling downlink data; that is, the number of HARQ-ACK information bits is dynamically variable, hence the codebook is called a dynamic HARQ-ACK codebook. The method for generating the Type-2 HARQ-ACK codebook can be found in the description in 3GPP communication protocol 38.213, and will not be repeated here.

[0074] 5. Downlink assignment index (DAI) mechanism:

[0075] The DAI field is divided into counter DAI (C-DAI) and total DAI (T-DAI) in carrier aggregation cases. C-DAI counts the number of PDCCH schedulings up to the currently scheduled PDCCH. T-DAI counts the total number of PDCCH schedulings across all carriers in a given PDCCH monitoring occasion, and is updated only when the PDCCH monitoring occasion is updated. The counting rules for DAI can be found in 3GPP communication protocol 38.213, and will not be repeated here.

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

[0077] The terminology used in this application has been briefly explained above, and will not be repeated in the following embodiments. The communication method provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided in this application can be applied to the above... Figure 1 The network architecture shown is not limited.

[0078] Based on the above Figure 1 In the architecture shown, when both DG and SPS PDSCH reception exist, and the HARQ-ACK information corresponding to DG and SPS PDSCH are transmitted on the same PUCCH or PUSCH in the same time slot, the dynamic HARQ-ACK codebook is generated by appending the HARQ-ACK information corresponding to SPS PDSCH to the HARQ-ACK information corresponding to DG. For the single DCI introduced in R18, since one single DCI can simultaneously schedule the PDSCH of one or more cells, when a single DCI exists, the dynamic HARQ-ACK codebook is defined as a first sub-codebook and a second sub-codebook. The first sub-codebook contains HARQ-ACK information for scheduling the PDSCH of one cell, and the second sub-codebook contains HARQ-ACK information for scheduling the PDSCH of more than one cell. The first and second sub-codebooks are concatenated to form the dynamic HARQ-ACK codebook.

[0079] However, when the scheduling of a single DCI includes at least one of DG, SPS PDSCH activation, SPS PDSCH deactivation, and SPS PDSCH retransmission, and the HARQ-ACK information corresponding to these scheduled PDSCHs is sent on the PUCCH or PUSCH in the same time slot, multiple dynamic HARQ-ACK codebooks will appear. This can easily lead to inconsistencies in the understanding of dynamic HARQ-ACK codebooks between terminal devices and base stations, resulting in the problem that the HARQ-ACK codebook cannot be received correctly.

[0080] On the other hand, for DCIs without PDSCH scheduling, such as semi-persistent scheduling of the physical downlink shared channel (SPS PDSCH release), transmission configuration information state update (TCI state update), and secondary cell dormancy indication, each DCI requires a corresponding 1-bit HARQ-ACK information bit feedback. When a single DCI includes PDSCH-free scheduling indications for all cells, generally the number of cells indicated corresponds to the number of HARQ-ACK information bits fed back. However, since a single DCI can provide PDSCH-free scheduling indications for multiple cells through a single DCI, feeding back multiple HARQ-ACK information bits causes bit redundancy. A large HARQ-ACK codebook size may lead to a decrease in reception performance. Furthermore, when a single DCI contains no PDSCH scheduling indication for all cells or contains no PDSCH scheduling indication for at least one cell and dynamic PDSCH scheduling for at least one cell, the number of HARQ-ACK information bits corresponding to this single DCI in the HARQ-ACK codebook, and whether it belongs to the first or second sub-codebook, can easily lead to inconsistencies in the understanding of the dynamic HARQ-ACK codebook between the terminal equipment and the base station, resulting in the problem of the HARQ-ACK codebook not being received correctly.

[0081] This application provides a method for feeding back HARQ-ACK information. By generating a dynamic HARQ-ACK codebook based on the number of cells scheduled by DCI and the scheduling type, the terminal device and the base station can correctly understand the dynamic HARQ-ACK codebook when multiple scheduling conditions exist simultaneously, thereby avoiding the problem of HARQ-ACK codebook not being received correctly.

[0082] It should be understood that the following description is for ease of understanding and explanation only, using the interaction between a terminal device and a network device as an example to illustrate the methods provided in the embodiments of this application. However, this should not constitute any limitation on the subject executing the methods provided in this application. For example, the terminal device shown in the embodiments below can be replaced by components (such as chips or chip systems) configured in the terminal device. The network device shown in the embodiments below can also be replaced by components (such as chips or chip systems) configured in the network device.

[0083] The embodiments shown below do not specifically limit the structure of the execution subject of the method provided in the embodiments of this application. As long as it is possible to communicate according to the method provided in the embodiments of this application by running a program that records the code of the method provided in the embodiments of this application, for example, the execution subject of the method provided in the embodiments of this application can be a terminal device or a network device, or a functional module in a terminal device or network device that can call and execute a program.

[0084] Figure 2 This is a schematic diagram of a method 400 for feeding back HARQ-ACK information according to an embodiment of this application. Method 400 may include the following steps.

[0085] S410, the network device sends the first DCI to the terminal device. Correspondingly, the terminal device receives the first DCI from the network device. The first DCI schedules data for one cell.

[0086] One possible implementation is that the first DCI is legacy downlink control information (legacy DCI). The legacy DCI can only schedule data from one cell, and the DCI format of the legacy DCI is a DCI format that can only schedule data from one cell.

[0087] For example, the DCI format corresponding to legacy DCI is DCI format 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2.

[0088] One possible implementation is that the first DCI is a single downlink control information (single DCI). The DCI format of the single DCI can schedule data from two or more cells or data from one cell, and the first DCI only schedules data from one cell.

[0089] For example, the DCI format corresponding to single DCI is format 0_X / 1_X, where X may be greater than or equal to 3. For example, when X is 5, the uplink single DCI format is DCI format 0_5, and the downlink single DCI format is DCI format 1_5. This application does not limit the value of X.

[0090] It should be understood that in this application, the data of the scheduling cell can be understood as the PDSCH of the scheduling cell, that is, "data" and "PDSCH" can be used interchangeably. In this application, the data of the scheduling cell is used as an example for explanation.

[0091] S420, the network device sends a second DCI to the terminal device. Correspondingly, the terminal device receives the second DCI from the network device. The second DCI has a DCI format that allows scheduling data from two or more cells, or data from one cell.

[0092] One possible implementation is that the second DCI is a single DCI, and the second DCI only schedules data from one cell.

[0093] One possible implementation is that the second DCI is a single DCI, and the second DCI schedules data from two or more cells.

[0094] S430, the terminal device determines the HARQ-ACK codebook based on the number of cells scheduled by the first DCI and the second DCI.

[0095] The HARQ-ACK codebook includes HARQ-ACK information for the data scheduled by the first DCI and the data scheduled by the second DCI, as well as HARQ-ACK information for the data scheduled by the first semi-persistent scheduling (SPS).

[0096] The HARQ-ACK information of the data scheduled by the first DCI can be understood as the HARQ-ACK information corresponding to the data of a cell dynamically scheduled by the network device according to the first DCI received by the terminal device.

[0097] The HARQ-ACK information of the data scheduled by the second DCI can be understood as the HARQ-ACK information corresponding to the data of one or more cells dynamically scheduled by the network device according to the second DCI.

[0098] The HARQ-ACK information for the first half of the continuous scheduling of SPS data is the HARQ-ACK information corresponding to the terminal device activating DCI to receive SPS data from one or more cells based on the SPS data sent by the network device.

[0099] Dynamic scheduling includes any of the following scheduling methods:

[0100] The cell-radio network temporary identifier (C-RNTI) or modulation and coding scheme-cell-radionetwork temporary identifier (MCS-C-RNTI) scrambled cyclic redundancy check (CRC) DCI PDSCH scheduling, semi-persistent scheduling physical downlink shared channel deactivation (SPS PDSCH release), and SPS PDSCH retransmission.

[0101] In this case, the PDSCH scheduling of the DCI scrambled by C-RNTI / MCS-C-RNTI CRC involves the network device sending a DCI scrambled by C-RNTI or MCS-C-RNTI CRC to the terminal device. The DCI contains PDSCH scheduling information. The terminal device receives the PDSCH based on the DCI, which is scheduled by the network device through the DCI. The new data indicator (NDI) contained in the DCI can be equal to 0 or 1.

[0102] SPS PDSCH deactivation occurs when the terminal device detects a DCI indicating SPS PDSCH deactivation. A valid release of a DLSPS requires information verification, specifically determining whether certain field values ​​in the DCI meet predefined protocol values. If they do, the terminal device identifies the DCI as an SPS PDSCH activated DCI and periodically receives PDSCHs based on the scheduling information and higher-layer parameter configuration information contained in the DCI. Specific verification methods can be found in 3GPP communication protocol 38.213, and will not be elaborated here.

[0103] SPS PDSCH retransmission involves the network device sending a DCI (Distributed Control Information) with a CS-RNTI-scrambled CRC to the terminal device. This DCI contains scheduling information for a PDSCH. The terminal device receives the PDSCH based on the DCI, which is scheduled by the network device using the DCI. The new data indicator in the DCI is equal to 1. SPS PDSCH retransmission is also a retransmission scheduling mechanism performed by the network device based on a previous SPS PDSCH HARQ-ACK message from the terminal device. This HARQ-ACK message indicates a PDSCH decoding error in a specific HARQ-ACK process within a specific SPS.

[0104] Semi-persistent scheduling can be understood as the terminal device receiving an SPS PDSCH associated with an SPS PDSCH configuration based on the DCI sent by the network device. It includes two parts: SPS PDSCH activation scheduling and SPS PDSCH transmission without a corresponding PDCCH. These two parts can be understood as the reception of an SPS PDSCH corresponding to one SPS PDSCH configuration. The SPS PDSCH configuration is activated by a DCI with CS-RNTI scrambled CRC. The new data indicator in the DCI is 0.

[0105] It should be noted that in this application, SPS PDSCH can be interchanged with DL SPS.

[0106] In this process, SPS PDSCH activation scheduling involves the network device sending a DCI (Distributed Control Information) with a CS-RNTI-scrambled CRC to the terminal device. The DCI contains scheduling information for a PDSCH. The terminal device receives the PDSCH based on the DCI. The PDSCH is scheduled by the network device through the DCI, and can be understood as the first PDSCH in the activation SPS PDSCH reception. The new data indicator in the DCI is equal to 0. Valid activation of a DL SPS PDSCH requires information verification, specifically determining whether certain fields in the DCI are set to predefined special values. The specific method is described in 3GPP communication protocol 38.213 and will not be elaborated here.

[0107] An SPS PDSCH without a corresponding PDCCH transmission refers to a situation where, once an SPS PDSCH configuration is activated by a DCI, the terminal device periodically receives PDSCHs based on the higher-layer parameter configuration and the indication information contained in the DCI. During periodic PDSCH reception, it is not necessary to receive / detect the PDCCH corresponding to this SPS PDSCH configuration, unless a PDSCH decoding error occurs in a process and retransmission is required. An SPS PDSCH without a corresponding PDCCH transmission can also be understood as activating all SPS PDSCHs except the first PDSCH in the SPS PDSCH reception.

[0108] The scheduling of SPS data for one cell by one DCI can be understood as the activation of SPS data for one cell by the DCI. The SPS data for one cell can be the first PDSCH received by the DCI-activated SPS PDSCH, or it can be any SPS PDSCH other than the first PDSCH that is activated by the DCI.

[0109] Specifically, depending on the different formats of the first DCI and the second DCI, and the different number of cells scheduled by the first DCI and the second DCI, the HARQ-ACK codebook determined by the terminal equipment has the following situations.

[0110] Scenario 1: When the DCI format of the first DCI is a DCI format that can only schedule data from one cell, and the first DCI schedules data from one cell (hereinafter referred to as legacy DCI#1), and the DCI format of the second DCI is a DCI format that can schedule data from two or more cells or data from one cell, and the second DCI only schedules data from one cell (hereinafter referred to as single DCI#1), the HARQ-ACK codebook determined by the terminal device includes the first HARQ-ACK sub-codebook.

[0111] The first HARQ-ACK subcodebook includes HARQ-ACK information for data scheduled by the first DCI (legacy DCI#1) and HARQ-ACK information for data scheduled by the second DCI (single DCI#1). The HARQ-ACK information for the first SPS data is appended to the first HARQ-ACK subcodebook.

[0112] It should be understood that the HARQ-ACK information of the first SPS data is appended to the first HARQ-ACK sub-codebook, which can be interpreted as the HARQ-ACK information of the SPS data being located after the position of the first HARQ-ACK sub-codebook in the HARQ-ACK codebook. Similarly, it should be understood that in this application, A is appended to B, which can be interpreted as A being located after the position of B.

[0113] The reception of the first SPS data is activated through the fourth DCI.

[0114] For example, the DCI format of the fourth DCI is a DCI format that can only schedule data from one cell, and the fourth DCI simultaneously activates the reception of SPS data from only one cell, for example, the fourth DCI is a legacy DCI (hereinafter referred to as legacyDCI#2); or the DCI format of the fourth DCI is a DCI format that can schedule data from two or more cells as well as data from one cell, and the fourth DCI simultaneously activates the reception of SPS data from only one cell, for example, the fourth DCI is a single DCI (hereinafter referred to as single DCI#2) that only activates the reception of SPS data from only one cell.

[0115] One possible implementation is that the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of the legacy DCI#2 scheduling cell.

[0116] One possible implementation is that the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of a single DCI#2 scheduling cell.

[0117] One possible implementation is that the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of the legacy DCI#2 scheduling one cell, and the HARQ-ACK information of the SPS data of the single DCI#2 scheduling one cell.

[0118] For example, the HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, which includes HARQ-ACK information for data scheduled by legacy DCI#1 and HARQ-ACK information for data dynamically scheduled by single DCI#1. The HARQ-ACK information for the first SPS data is appended to the first HARQ-ACK sub-codebook. The HARQ-ACK information for the first SPS data includes HARQ-ACK information for SPS data of one cell scheduled by legacy DCI#2 and HARQ-ACK information for SPS data of one cell scheduled by single DCI#2.

[0119] Scenario 2: When the DCI format of the first DCI is a DCI format that can schedule data from two or more cells or data from one cell, and the first DCI schedules data from only one cell (hereinafter referred to as single DCI#1), and the DCI format of the second DCI is a DCI format that can schedule data from two or more cells or data from one cell, and the second DCI schedules data from two or more cells (hereinafter referred to as single DCI#3), the HARQ-ACK codebook determined by the terminal device includes the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook.

[0120] The first HARQ-ACK subcodebook includes HARQ-ACK information for data scheduled by the first DCI (single DCI#1), the second HARQ-ACK subcodebook includes HARQ-ACK information for data scheduled by the second DCI (single DCI#3), the second HARQ-ACK subcodebook is appended to the first HARQ-ACK subcodebook, and the HARQ-ACK information for the first SPS data is appended to the second HARQ-ACK subcodebook.

[0121] The reception of the first SPS data is activated via the fourth or fifth DCI.

[0122] For example, the DCI format of the fourth DCI is a DCI format that can schedule data from two or more cells or data from one cell, and the fourth DCI activates the reception of SPS data from only one cell at the same time. For example, the fourth DCI is a single DCI (single DCI#2) that activates the reception of SPS data from only one cell.

[0123] For example, the DCI format of the fifth DCI is a DCI format that can schedule data from two or more cells or data from one cell, and the fifth DCI simultaneously activates the reception of SPS data from two or more cells. For example, the fifth DCI is a single DCI that activates the reception of SPS data from two or more cells (hereinafter referred to as singleDCI#4).

[0124] One possible implementation is that the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of a single DCI#2 scheduling cell.

[0125] One possible implementation is that the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of two or more cells scheduled by single DCI#4.

[0126] In one possible implementation, the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of SPS data scheduled by single DCI#2 for one cell, and the HARQ-ACK information of SPS data scheduled by single DCI#4 for two or more cells.

[0127] For example, the HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information for data scheduled by single DCI#1, and the second HARQ-ACK sub-codebook includes HARQ-ACK information for data scheduled by single DCI#3. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook. The HARQ-ACK information for the first SPS data is appended to the second HARQ-ACK sub-codebook. The HARQ-ACK information for the first SPS data includes HARQ-ACK information for SPS data scheduled by single DCI#2 for one cell, and HARQ-ACK information for data scheduled by single DCI#4 for two or more cells.

[0128] Scenario 3: When the DCI format of the first DCI is a DCI format that can only schedule data from one cell, and the first DCI schedules data from one cell (legacy DCI#1), and the DCI format of the second DCI is a DCI format that can schedule data from two or more cells or data from one cell, and the second DCI schedules data from two or more cells (single DCI#3), the HARQ-ACK codebook determined by the terminal device includes the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook.

[0129] The first HARQ-ACK subcodebook includes HARQ-ACK information for data scheduled by the first DCI (legacy DCI#1), the second HARQ-ACK subcodebook includes HARQ-ACK information for data scheduled by the second DCI (single DCI#3), the second HARQ-ACK subcodebook is appended to the first HARQ-ACK subcodebook, and the HARQ-ACK information for the first SPS data is appended to the second HARQ-ACK subcodebook.

[0130] The reception of the first SPS data is activated via the fourth or fifth DCI.

[0131] For example, the DCI format of the fourth DCI is a DCI format that can only schedule data from one cell, and the fourth DCI only activates the reception of SPS data from one cell at a time, for example, the fourth DCI is legacy DCI#2.

[0132] For example, the DCI format of the fifth DCI is a DCI format that can schedule data from two or more cells or data from one cell, and the fifth DCI simultaneously activates the reception of SPS data from two or more cells. For example, the fifth DCI is a single DCI (single DCI#4) that activates the reception of SPS data from two or more cells.

[0133] One possible implementation is that the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of the legacy DCI#2 scheduling cell.

[0134] One possible implementation is that the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of two or more cells scheduled by single DCI#4.

[0135] One possible implementation is that the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of one cell scheduled by legacy DCI#2, and the HARQ-ACK information of the SPS data of two or more cells scheduled by single DCI#4.

[0136] For example, the HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information for data scheduled by legacy DCI#1, and the second HARQ-ACK sub-codebook includes HARQ-ACK information for data scheduled by single DCI#3. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook. The HARQ-ACK information for the first SPS data is appended to the second HARQ-ACK sub-codebook. The HARQ-ACK information for the first SPS data includes HARQ-ACK information for SPS data scheduled by legacy DCI#2 for one cell, and HARQ-ACK information for SPS data scheduled by single DCI#4 for two or more cells.

[0137] Case 4: When the DCI format of the first DCI is a DCI format that can only schedule data from one cell, and the first DCI schedules data from one cell (legacy DCI#1), and the DCI format of the second DCI is a DCI format that can schedule data from two or more cells or data from one cell, and the second DCI only schedules data from one cell (single DCI#1), the terminal device, based on the HARQ-ACK codebook determined by the received first DCI and second DCI, including the first HARQ-ACK sub-codebook, the first HARQ-ACK sub-codebook includes the HARQ-ACK information of the data scheduled by the first DCI (legacy DCI#1) and the HARQ-ACK information of the data scheduled by the second DCI (single DCI#1), method 400 may further include:

[0138] S421, the network device sends a third DCI to the terminal device.

[0139] Accordingly, the terminal device receives a third DCI from the network device.

[0140] Among them, the DCI format of the third DCI is a DCI format that can schedule data from two or more cells or data from one cell, and the third DCI schedules data from two or more cells.

[0141] It should be understood that the third DCI may schedule data from two or more cells, or it may schedule data from one cell while simultaneously indicating the activation or deactivation of SPS in at least one other cell. This application does not limit this.

[0142] For example, the third DCI is a single DCI that schedules data from two or more cells (hereinafter referred to as single DCI#3).

[0143] Specifically, when the terminal device also receives the third DCI, the HARQ-ACK codebook determined by the terminal device also includes the second HARQ-ACK sub-codebook.

[0144] The second HARQ-ACK subcodebook includes the HARQ-ACK information of the data scheduled by the third DCI (single DCI#3). The second HARQ-ACK subcodebook is located after the first HARQ-ACK subcodebook in the HARQ codebook. The HARQ-ACK information of the first SPS data is appended after the second HARQ-ACK subcodebook.

[0145] In one possible implementation, the reception of the first SPS data is activated via a fourth or fifth DCI.

[0146] For example, the fourth DCI has a DCI format that can only schedule data from one cell, and the fourth DCI simultaneously activates the reception of SPS data from only one cell, such as legacy DCI (legacy DCI#2); or the fourth DCI has a DCI format that can schedule data from two or more cells as well as data from one cell, and the fourth DCI simultaneously activates the reception of SPS data from only one cell, such as single DCI#2. For example, the fifth DCI has a DCI format that can schedule data from two or more cells as well as data from one cell, and the fifth DCI simultaneously activates the reception of SPS data from two or more cells, such as single DCI#4. Method 1: The HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of one cell scheduled by legacy DCI#2, or the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of one cell scheduled by single DCI#2, or the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of two or more cells scheduled by single DCI#4.

[0147] Method 2: The HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of one cell scheduled by legacy DCI#2 and the HARQ-ACK information of the SPS data of one cell scheduled by single DCI#2; or the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of one cell scheduled by legacy DCI#2 and the HARQ-ACK information of the SPS data of two or more cells scheduled by single DCI#4; or the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of one cell scheduled by single DCI#2 and the HARQ-ACK information of the SPS data of two or more cells scheduled by single DCI#4.

[0148] Method 3: The HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of one cell scheduled by legacy DCI#2, the HARQ-ACK information of the SPS data of one cell scheduled by single DCI#2, and the HARQ-ACK information of the SPS data of two or more cells scheduled by single DCI#4.

[0149] In one possible implementation, the HARQ-ACK codebook further includes HARQ-ACK information for the second SPS data. This HARQ-ACK information is located in the HARQ-ACK codebook after the position of the first HARQ-ACK sub-codebook and before the position of the second HARQ-ACK sub-codebook. The reception of the first SPS data is activated via a fifth DCI, and the reception of the second SPS data is activated via a fourth DCI.

[0150] In other words, the HARQ-ACK codebook at this time includes, in sequence, the first HARQ-ACK sub-codebook, the HARQ-ACK information of the second SPS data, the second HARQ-ACK sub-codebook, and the HARQ-ACK information of the first SPS data.

[0151] For example, the DCI format of the fifth DCI is a DCI format that can schedule data from two or more cells or data from one cell, and the fifth DCI simultaneously activates the reception of SPS data from two or more cells. For example, the fifth DCI is single DCI#4.

[0152] Optionally, the HARQ-ACK information of the first SPS data includes the HARQ-ACK information of the SPS data of two or more cells scheduled by single DCI#4.

[0153] For example, the DCI format of the fourth DCI is a DCI format that can only schedule data from one cell, such as legacy DCI#2, or the DCI format of the fourth DCI is a DCI format that can schedule data from two or more cells as well as data from one cell, and the fourth DCI only activates the reception of SPS data from one cell at the same time, such as single DCI#2.

[0154] Optionally, the HARQ-ACK information of the second SPS data includes the HARQ-ACK information of the SPS data of the legacy DCI#2 scheduling one cell, or the HARQ-ACK information of the second SPS data includes the HARQ-ACK information of the SPS data of the single DCI#2 scheduling one cell, or the HARQ-ACK information of the second SPS data includes the HARQ-ACK information of the SPS data of the legacy DCI#2 scheduling one cell, and the HARQ-ACK information of the SPS data of the single DCI#2 scheduling one cell.

[0155] For example, the HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information for data scheduled by legacy DCI#1 and HARQ-ACK information for data scheduled by single DCI#1. The second HARQ-ACK sub-codebook includes HARQ-ACK information for data scheduled by single DCI#3. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook. The HARQ-ACK information for the first SPS data is appended to the second HARQ-ACK sub-codebook. The HARQ-ACK information for the first SPS data includes HARQ-ACK information for SPS data scheduled by single DCI#4 from two or more cells. The position of the HARQ-ACK information for the second SPS data in the HARQ-ACK codebook is after the position of the first HARQ-ACK sub-codebook and before the position of the second HARQ-ACK sub-codebook. The HARQ-ACK information for the second SPS data includes legacy... HARQ-ACK information for SPS data of one cell scheduled by DCI#2, and HARQ-ACK information for SPS data of one cell scheduled by singleDCI#2.

[0156] It should be noted that when the second DCI has a DCI format that can schedule data from two or more cells or data from one cell, and the second DCI only schedules data from one cell, and the fourth DCI has a DCI format that can schedule data from two or more cells or data from one cell, and the fourth DCI simultaneously activates the reception of SPS data from only one cell, the fourth DCI and the second DCI can still be the same DCI. In other words, when the fourth DCI and the second DCI are the same DCI, and the DCI format can schedule data from two or more cells or data from one cell, and the DCI only schedules data from one cell and activates the reception of SPS data from only one cell, that is, single DCI#1 and single DCI#2 can be the same single DCI.

[0157] It should be noted that when the second DCI has a DCI format that can schedule data from two or more cells or data from one cell, and the second DCI only schedules data from one cell, and the fifth DCI has a DCI format that can schedule data from two or more cells or data from one cell, and the fifth DCI simultaneously activates the reception of SPS data from two or more cells, the fifth DCI and the second DCI can still be the same DCI. In other words, when the fifth DCI and the second DCI are the same DCI, and the DCI format can schedule data from two or more cells or data from one cell, and the DCI only schedules data from one cell and activates the reception of SPS data from two or more cells, that is, single DCI#1 and single DCI#4 can be the same single DCI.

[0158] It should be noted that when the fourth DCI's DCI format can schedule data from two or more cells or data from one cell, and the fourth DCI simultaneously activates only the reception of SPS data from one cell, and the third DCI's DCI format can schedule data from two or more cells or data from one cell, and the third DCI schedules data from two or more cells, the third DCI and the fourth DCI can also be the same DCI. In other words, when the third DCI and the fourth DCI are the same DCI, and the DCI format can schedule data from two or more cells or data from one cell, and the DCI schedules data from two or more cells and only activates the reception of SPS data from one cell, that is, single DCI#2 and single DCI#3 can be the same single DCI.

[0159] It should be noted that when the fifth DCI's DCI format can schedule data from two or more cells or data from one cell, and the fifth DCI simultaneously activates the reception of SPS data from two or more cells, and the third DCI's DCI format can also schedule data from two or more cells or data from one cell, and the third DCI schedules data from two or more cells, the third DCI and the fifth DCI can be the same DCI. In other words, when the third DCI and the fifth DCI are the same DCI, and the DCI format can schedule data from two or more cells or data from one cell, and the DCI schedules data from two or more cells and activates the reception of SPS data from two or more cells, that is, single DCI#3 and single DCI#4 can be the same single DCI.

[0160] S440, the terminal device sends the HARQ-ACK codebook back to the network device.

[0161] Accordingly, the network device receives the HARQ-ACK codebook from the terminal device.

[0162] One possible implementation is that the terminal device sends a HARQ-ACK codebook to the network device on the PUCCH or PUSCH.

[0163] Based on the above scheme, the terminal device generates a HARQ-ACK codebook according to the number of cells scheduled by various DCIs. This enables the terminal device and network device to correctly understand the generation method of the dynamic HARQ-ACK codebook when multiple scheduling conditions exist simultaneously, thereby avoiding the problem of HARQ-ACK codebook not being received correctly.

[0164] Figure 3 This is a schematic diagram of a method 500 for feeding back HARQ-ACK information according to an embodiment of this application. Method 400 may include the following steps.

[0165] S510, the network device sends the sixth DCI to the terminal device. Correspondingly, the terminal device receives the sixth DCI from the network device. The sixth DCI has a DCI format that allows scheduling data from two or more cells, or data from one cell.

[0166] For example, the sixth DCI is a single DCI. Specifically, the sixth DCI includes indication information for K1 cells, where K1 is an integer greater than 1 and less than or equal to N, and N is the maximum number of cells that the sixth DCI can schedule. This sixth DCI is not used to schedule data from other cells. The indication information for each of the K1 cells includes any one of the following: information indicating the release of the SPS PDSCH, information indicating a transmission configuration information status update, or information indicating a secondary cell hibernation.

[0167] The information used to indicate the release of an SPS PDSCH is a DCI (Digital Information Chaining) sent by the network device to the terminal device, scrambled by a CS-RNTI CRC. The DCI contains deactivation or release information configured for the SPS PDSCH. The new data indication in the DCI is equal to 0. The DCI either does not contain any PDSCH scheduling information or contains invalid information related to PDSCH scheduling. The terminal device releases SPS PDSCH reception based on the DCI, meaning it no longer receives the indicated activated SPS PDSCH. Valid deactivation or release of a DL SPS PDSCH requires information verification, specifically determining whether certain fields in the DCI are set to predefined special values. The specific method can be found in 3GPP communication protocol 38.213, and will not be elaborated here.

[0168] The information used to indicate a Transmission Configuration Information (TCI) state update is a Data Interchange (DCI) sent by the network device to the terminal device to indicate the updated TCI state of received data. The DCI does not contain any PDSCH scheduling information, or if it does, the information containing PDSCH scheduling-related information is invalid. The terminal device updates the TCI state of received data based on the DCI. Whether a DCI indicates a TCI state update and has no PDSCH scheduling requires information verification, i.e., determining whether certain fields in the DCI are set to predefined special values. Specific methods can be found in 3GPP communication protocol 38.214, and will not be elaborated here.

[0169] The information used to indicate secondary cell dormancy is a DCI sent by the network device to the terminal device, which contains a secondary cell dormancy indication field. The DCI indicates that one or more cells have entered a dormant state. The DCI does not contain any PDSCH scheduling information or contains invalid information related to PDSCH scheduling.

[0170] It should be understood that the indication information used by the sixth DCI to indicate the K1 cells can be interpreted as the sixth DCI being used to indicate the status of the K1 cells without including data scheduling (e.g., no PDSCH scheduling).

[0171] Optionally, in step S520, the network device sends a first DCI to the terminal device. Correspondingly, the terminal device receives the first DCI from the network device. The first DCI schedules data from the first cell.

[0172] One possible implementation is that the first DCI's DCI format is a DCI format that can only schedule data from one cell.

[0173] For example, the first DCI is a legacy DCI.

[0174] One possible implementation is that the DCI format of the first DCI is a DCI format that can schedule data from two or more cells or data from one cell.

[0175] For example, the first DCI is a single DCI.

[0176] Optionally, in S530, the network device sends a second DCI to the terminal device.

[0177] Accordingly, the terminal device receives a second DCI from the network device.

[0178] In this process, the second DCI schedules data from K2 cells, where K2 is an integer greater than 1 and less than or equal to N.

[0179] Specifically, the second DCI's DCI format is a DCI format that can schedule data from two or more cells or data from one cell.

[0180] For example, the second DCI is a single DCI.

[0181] Optionally, in S540, the network device sends a third DCI to the terminal device.

[0182] Accordingly, the terminal device receives a third DCI from the network device.

[0183] The third DCI schedules data from M cells and also includes indication information for P cells. The M cells and P cells are different cells, M and P are positive integers less than N, and M+P is less than or equal to N.

[0184] Specifically, the third DCI format is a DCI format that can schedule data from two or more cells or data from one cell.

[0185] For example, the third DCI is a single DCI.

[0186] It should be understood that the third DCI schedules data from M cells, including indication information from P cells. This can be understood as the third DCI being used to indicate the state of no-data scheduling for P cells and to perform PDSCH scheduling for M cells.

[0187] The data for scheduling M cells may include C-RNTI / MCS-C-RNTI initial retransmission or SPS PDSCH retransmission.

[0188] In S550, the terminal device sends a HARQ-ACK codebook to the network device. Correspondingly, the network device receives the HARQ-ACK codebook from the terminal device.

[0189] One possible implementation is that the terminal device sends a HARQ-ACK codebook to the network device on the PUCCH or PUSCH.

[0190] The HARQ-ACK codebook includes a first bit group, which indicates whether the sixth DCI was correctly received. The first bit group includes one or more bits.

[0191] Specifically, the value of the C-DAI field and / or the value of the T-DAI field corresponding to the sixth DCI are both 1. The first bit group indicates whether the sixth DCI has been correctly received, which can be understood as indicating the HARQ-ACK information corresponding to the indication information of N cells through the first bit group.

[0192] For example, the sixth DCI is used to indicate the indication information of the four cells. In other words, the sixth DCI is used to perform no-data scheduling on the four cells. At this time, the HARQ-ACK information corresponding to the indication information of the four cells is indicated by the first bit group.

[0193] It should be understood that the first bit group can be equal to 1 bit, 2 bits, or more bits. When at least one cell in the network device is configured with dual codeword scheduling (configured with the higher-layer parameter maxNrofCodeWordsScheduledByDCI equal to n2), the HARQ-ACK information corresponding to the data of one cell scheduled by the first DCI is 2 bits, that is, the length of the second bit group is 2. Then, the length of the first bit group corresponding to the indication information of K1 cells in the sixth DCI is equal to the length of the second bit group, that is, the length of the first bit group is equal to 2. When at least one cell in the network device is configured with code-block-group based transmission (CBG-based transmission), the HARQ-ACK information corresponding to the data of one cell scheduled by the first DCI is N2 bits, that is, the length of the second bit group is N2, where N2 is equal to the maximum number of CBGs contained in one TB configured by the higher-layer parameter maxCodeBlockGroupsPerTransportBlock, such as 4 or 6, etc. Then, the length of the first bit group corresponding to the indication information of the sixth DCI, including K1 cells, is equal to the length of the second bit group, that is, the length of the first bit group is equal to N2. If at least one cell among the multiple cells configured by the network device is configured with dual codeword scheduling and at least one cell is configured with code block group-based transmission, then the length of the first bit group is equal to the length of the second bit group, which is equal to 2*N2.

[0194] It should be understood that, currently, for single DCIs, DAI counting is performed separately for single DCIs scheduling a single cell, and separately for single DCIs scheduling more than one cell. For both types of single DCIs, the C-DAI field value and / or T-DAI field value corresponding to a single DCI is 1. However, for single DCIs scheduling more than one cell, the single DCI needs to correspond to N HARQ-ACK information bits in the HARQ-ACK codebook. N depends on the number of configured cells in the co-scheduled cell set, the maximum number of configured cells, or the maximum number of configurable cells. In this application, the single DCI that performs data-free scheduling for more than one cell requires corresponding HARQ-ACK information in the HARQ-ACK codebook to be indicated by a single bit group. In other words, the feedback of data-free scheduling for more than one cell based on the single DCI is fed back to the network device through a single bit group, which can effectively save the number of feedback bits, reduce the codebook size, and improve transmission efficiency.

[0195] It should be noted that the method for counting DAI for DCI can be found in the specific descriptions of DAI-related technologies in existing 3GPP protocols.

[0196] It should be understood that, depending on whether the terminal device receives the first DCI, the second DCI, or the third DCI, the HARQ-ACK codebook sent by the terminal device to the network device can have the following variations.

[0197] Scenario 1: When the terminal device receives the first DCI from the network device, i.e., when S520 is executed, the HARQ-ACK codebook sent by the terminal device to the network device also includes a second bit group. That is, at this time, the HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, and the first HARQ-ACK sub-codebook includes a first bit group and a second bit group.

[0198] The second bit group indicates whether the data in the first cell has been correctly decoded, and the length of the second bit group is the same as the length of the first bit group.

[0199] Specifically, the value of the C-DAI field and / or the value of the T-DAI field corresponding to the first DCI are both 1, and the second bit group indicates whether the data of the first cell has been correctly decoded. This can be understood as indicating the HARQ-ACK information corresponding to the data of the first cell through the second bit group.

[0200] It should be understood that when scheduling single codewords, the PDSCH of one cell scheduled by one DCI corresponds to 1 bit of HARQ-ACK information. When scheduling two codewords, the PDSCH of one cell scheduled by one DCI corresponds to 2 bits of HARQ-ACK information. Network devices configure whether a bandwidth part (BWP) of a cell is scheduled using single codewords or two codewords through higher-layer parameters. Therefore, in carrier aggregation (CA) scenarios, some cells are scheduled using single codewords while others are scheduled using two codewords. When HARQ-ACK information corresponding to PDSCHs from different cells needs to be fed back on the same PUCCH or PUSCH in the same time slot within the same bandwidth of the same cell, in order to standardize the length of the HARQ-ACK information bits corresponding to one PDSCH in each cell, the protocol stipulates that each cell generates HARQ-ACK information according to the configured maximum number of codeword feedback bits. That is, the HARQ-ACK information bits of one PDSCH in a cell configured with single codeword scheduling must be aligned with the HARQ-ACK information bits of one PDSCH in a cell configured with dual codeword scheduling, i.e., feeding back 2 bits of HARQ-ACK information. Therefore, it can be understood that the size of the first bit group is equal to the size of the second bit group.

[0201] It should be noted that the positions of the first bit group and the second bit group in the HARQ-ACK codebook can be determined by existing DAI mechanisms, and this application does not restrict the method of determining the positions of the first bit group and the second bit group in the HARQ-ACK codebook.

[0202] Scenario 2: When the terminal device receives the second DCI from the network device, i.e. when S530 is executed, the HARQ-ACK codebook sent by the terminal device to the network device includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes a first bit group and a second bit group, and the second HARQ-ACK sub-codebook includes N third bit groups.

[0203] Among them, K2 third bit groups out of N third bit groups indicate whether the data of K2 cells have been correctly decoded, and the bit values ​​of N-K2 third bit groups out of N third bit groups are predefined values.

[0204] Specifically, the value of the C-DAI field and / or the value of the T-DAI field corresponding to the second DCI are both 1. The K2 third bit groups in the N third bit groups indicate whether the data of the K2 cells have been correctly decoded. This can be understood as indicating the HARQ-ACK information corresponding to the data of one of the K2 cells through one of the K2 third bit groups.

[0205] Scenario 3: When the terminal device receives the third DCI from the network device, i.e., when S540 is executed, the HARQ-ACK codebook sent by the terminal device to the network device includes the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook. The second HARQ-ACK sub-codebook also includes N fourth bit groups.

[0206] Among them, M fourth bit groups out of N fourth bit groups indicate whether the data of each cell in M ​​cells has been correctly decoded, P fourth bit groups out of N fourth bit groups indicate whether the indication information of each cell in P cells has been correctly received, and the bit values ​​of NMP fourth bit groups out of N fourth bit groups are predefined values.

[0207] Specifically, the values ​​of the C-DAI field and / or T-DAI field corresponding to the third DCI are both 1. M of the N fourth bit groups indicate whether the data of each of the M cells has been correctly decoded; this can be understood as indicating the HARQ-ACK information corresponding to the data of each of the M cells through a single fourth bit group. P of the N fourth bit groups indicate whether the indication information of each of the P cells has been correctly received; this can be understood as indicating the HARQ-ACK information corresponding to the indication information of each of the P cells through a single fourth bit group. NMP of the N fourth bit groups have predefined bit values; this can be understood as NMP cells out of the N cells not being indicated and / or not being scheduled, and indicating the HARQ-ACK information corresponding to each of the NMP cells through a single fourth bit group, with the bit values ​​of the NMP fourth bit groups set to the predefined values. For example, a single DCI can schedule a maximum of 4 cells (N equals 4). Network devices are configured to transmit dual codewords in at least one of the four cells via higher-layer parameters. Therefore, the fourth bit group contains 2 bits (predefined as 2). When a terminal device receives a third DCI (Data Information Coding), which includes data scheduling information for one cell (M = 1) and indication information for two cells without PDSCH scheduling (P = 2), the HARQ-ACK information corresponding to the third DCI is 6 bits, i.e., (M + P) * 2 = 6. The remaining cell is neither scheduled nor indicated (NMP = 1), so the fourth bit group corresponding to this cell has a predefined value of 2 bits.

[0208] It should be noted that scenarios one through three can exist simultaneously, individually, or in combination. For example, when only S520 is executed (i.e., only scenario one exists), the HARQ-ACK codebook includes the first bit group and the second bit group; when only S530 is executed (i.e., only scenario two exists), the HARQ-ACK codebook includes the first bit group, the second bit group, and N third bit groups; when only S540 is executed (i.e., only scenario three exists), the HARQ-ACK codebook includes the first bit group and N fourth bit groups; when both S520 and S530 are executed (i.e., both scenario one and scenario two exist simultaneously), the HARQ-ACK codebook includes the first bit group, the second bit group, and N third bit groups; when executing... When executing S520 and S540, i.e., when both Case 1 and Case 3 exist simultaneously, the HARQ-ACK codebook includes a first bit group, a second bit group, and N fourth bit groups; when executing S530 and S540, i.e., when both Case 2 and Case 3 exist simultaneously, the HARQ-ACK codebook includes a first bit group, a second bit group, N third bit groups, and N fourth bit groups; when executing S520, S530, and S540, i.e., when both Case 1, Case 2, and Case 3 exist simultaneously, the HARQ-ACK codebook includes a first bit group, a second bit group, N third bit groups, and N fourth bit groups.

[0209] Based on the above scheme, the terminal device can send back HARQ-ACK information corresponding to no data scheduling to the network device in a unified feedback manner, without having to send back the indication information for each cell independently. This can save feedback bits, reduce codebook size, and improve transmission efficiency.

[0210] It is understood that, in order to achieve the functions in the above embodiments, the base station and terminal 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 of the various examples 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 in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0211] Figure 4 and Figure 5 This is a schematic diagram illustrating the structure of possible devices for feeding back HARQ-ACK information, provided for embodiments of this application. These devices can be used to implement the functions of terminal devices or network devices in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments. In embodiments of this application, the device for feeding back HARQ-ACK information can be as follows: Figure 1 One of the terminals 120a-120j shown can also be as follows: Figure 1The network devices 110a or 110b shown can also be modules (such as chips) applied to terminals or network devices.

[0212] like Figure 4 As shown, the device 600 includes a processing unit 610 and a transceiver unit 620. The device 600 is used to implement the above-described... Figure 2 or Figure 3 The methods illustrated in this embodiment demonstrate the functions of the terminal device or network device.

[0213] When device 600 is used to achieve Figure 2 In the method embodiment shown, the terminal device functions as follows: transceiver unit 620 is used to receive a first DCI from network device; transceiver unit 620 is also used to receive a second DCI from network device; transceiver unit 620 is also used to receive a third DCI from network device; processing unit 610 is used to determine the HARQ-ACK codebook based on the number of cells scheduled by the first DCI and the second DCI; transceiver unit 620 is also used to send the HARQ-ACK codebook to network device.

[0214] When device 600 is used to achieve Figure 2 In the method embodiment shown, the network device functions as follows: the transceiver unit 620 is used to send a first DCI to the terminal device; the transceiver unit 620 is also used to send a second DCI to the terminal device; the transceiver unit 620 is also used to send a third DCI to the terminal device; the transceiver unit 620 is also used to receive a HARQ-ACK codebook from the terminal device.

[0215] When device 600 is used to achieve Figure 3 In the method embodiment shown, the terminal device functions as follows: the transceiver unit 620 is used to receive a sixth DCI from the network device; the transceiver unit 620 is also used to receive a first DCI from the network device; the transceiver unit 620 is also used to receive a second DCI from the network device; the transceiver unit 620 is also used to receive a third DCI from the network device; and the transceiver unit 620 is also used to send a HARQ-ACK codebook to the network device.

[0216] When device 600 is used to achieve Figure 3 In the method embodiment shown, the network device functions as follows: the transceiver unit 620 is used to send a sixth DCI to the terminal device; the transceiver unit 620 is also used to send a first DCI to the terminal device; the transceiver unit 620 is also used to send a second DCI to the terminal device; the transceiver unit 620 is also used to send a third DCI to the terminal device; and the transceiver unit 620 is also used to receive a HARQ-ACK codebook from the terminal device.

[0217] For a more detailed description of the processing unit 610 and the transceiver unit 620, please refer to [reference needed]. Figure 2 or Figure 3 The relevant descriptions in the method embodiments shown.

[0218] like Figure 5 As shown, device 700 includes a processor 710 and interface circuitry 720. The processor 710 and interface circuitry 720 are coupled to each other. It is understood that interface circuitry 720 can be a transceiver or an input / output interface. Optionally, device 700 may further include a memory 730 for storing instructions executed by the processor 710, or storing input data required by the processor 710 to execute instructions, or storing data generated after the processor 710 executes instructions.

[0219] When device 700 is used to achieve Figure 2 In the method shown, the processor 710 is used to implement the functions of the processing unit 610, and the interface circuit 720 is used to implement the functions of the transceiver unit 620.

[0220] When the aforementioned device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiments. The terminal device chip receives information sent to the terminal device by the network device through other modules (such as an RF module or antenna) in the terminal device; or, the terminal device chip sends information to other modules (such as an RF module or antenna) in the terminal device, the information being sent by the terminal device to the network device.

[0221] When the aforementioned 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 radio frequency modules or antennas) within the network device; this information is sent from the terminal device to the network device. Alternatively, the network device module sends information to other modules (such as radio frequency modules or antennas) within the network device; this information is sent from the network device to the terminal device. Here, the network device module can be the baseband chip of the network device, or a CU, DU, or other module, or a device under an open radioaccess network (O-RAN) architecture, such as an open CU, open DU, etc.

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

[0223] 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 well 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 base station or terminal. The processor and storage medium can also exist as discrete components in a base station or terminal.

[0224] 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. Computer-readable storage media can be volatile or non-volatile, or may include both types of storage media.

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

[0226] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0227] 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 method for feeding back HARQ-ACK information, characterized in that, include: Receive first downlink control information (DCI) from network equipment; the first DCI schedules data for one cell. Receive a second DCI from the network device, wherein the DCI format of the second DCI is a DCI format that can schedule data from two or more cells or data from one cell; The HARQ-ACK codebook is determined based on the number of cells scheduled by the first DCI and the second DCI. The HARQ-ACK codebook includes HARQ-ACK information of data scheduled by the first DCI, HARQ-ACK information of data scheduled by the second DCI, and HARQ-ACK information of data scheduled by the first semi-persistent scheduling (SPS). The HARQ-ACK codebook is fed back to the network device.

2. The method according to claim 1, characterized in that, The first DCI uses a DCI format that can only schedule data from one cell. The second DCI schedules data from only one cell. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, which includes HARQ-ACK information for the data scheduled by the first DCI and HARQ-ACK information for the data scheduled by the second DCI. The HARQ-ACK information for the first SPS data is appended to the first HARQ-ACK sub-codebook.

3. The method according to claim 1, characterized in that, The first DCI has a DCI format that can schedule data from two or more cells or data from one cell. The second DCI schedules data from two or more cells. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the first DCI. The second HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the second DCI. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook. The HARQ-ACK information of the first SPS data is appended to the second HARQ-ACK sub-codebook.

4. The method according to claim 1, characterized in that, The first DCI uses a DCI format that can only schedule data from one cell. The second DCI schedules data from two or more cells. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information for the data scheduled by the first DCI. The second HARQ-ACK sub-codebook includes HARQ-ACK information for the data scheduled by the second DCI. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook. The HARQ-ACK information for the first SPS data is appended to the second HARQ-ACK sub-codebook.

5. The method according to claim 1, characterized in that, The first DCI uses a DCI format that can only schedule data from one cell. The second DCI schedules data from only one cell. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, which includes HARQ-ACK information for the data scheduled by the first DCI and HARQ-ACK information for the data scheduled by the second DCI. The method further includes: The network device receives a third DCI, the third DCI having a format that can schedule data from two or more cells or data from one cell. The third DCI schedules data from two or more cells. The HARQ-ACK codebook also includes a second HARQ-ACK sub-codebook, which includes HARQ-ACK information for the data scheduled by the third DCI. The second HARQ-ACK sub-codebook is located after the first HARQ-ACK sub-codebook in the HARQ codebook. The HARQ-ACK information for the first SPS data is appended to the second HARQ-ACK sub-codebook.

6. The method according to claim 5, characterized in that, The HARQ-ACK codebook also includes HARQ-ACK information of the second SPS data, wherein the position of the HARQ-ACK information of the second SPS data in the HARQ-ACK codebook is after the position of the first HARQ-ACK sub-codebook and before the position of the second HARQ-ACK sub-codebook. The reception of the second SPS data is activated by the fourth DCI. The DCI format of the fourth DCI is either a DCI format that can only schedule data from one cell, or a DCI format that can schedule data from two or more cells as well as data from one cell. The fourth DCI also activates the reception of SPS data from only one cell at a time. The reception of the first SPS data is activated by the fifth DCI. The DCI format of the fifth DCI is a DCI format that can schedule data from two or more cells or data from one cell. The fifth DCI simultaneously activates the reception of SPS data from two or more cells.

7. A method for feeding back HARQ-ACK information, characterized in that, include: Send a first downlink control information (DCI) to the terminal device; the first DCI schedules data from one cell. Send a second DCI to the terminal device. The DCI format of the second DCI is a DCI format that can schedule data from two or more cells or data from one cell. The terminal device receives a HARQ-ACK codebook, which is determined based on the number of cells scheduled by the first DCI and the second DCI. The HARQ-ACK codebook includes HARQ-ACK information for data scheduled by the first DCI, HARQ-ACK information for data scheduled by the second DCI, and HARQ-ACK information for data scheduled by the first semi-persistent scheduling (SPS).

8. The method according to claim 7, characterized in that, The first DCI uses a DCI format that can only schedule data from one cell. The second DCI schedules data from only one cell. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, which includes HARQ-ACK information for the data scheduled by the first DCI and HARQ-ACK information for the data scheduled by the second DCI. The HARQ-ACK information for the first SPS data is appended to the first HARQ-ACK sub-codebook.

9. The method according to claim 7, characterized in that, The first DCI has a DCI format that can schedule data from two or more cells or data from one cell. The second DCI schedules data from two or more cells. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the first DCI. The second HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the second DCI. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook. The HARQ-ACK information of the first SPS data is appended to the second HARQ-ACK sub-codebook.

10. The method according to claim 7, characterized in that, The first DCI uses a DCI format that can only schedule data from one cell. The second DCI schedules data from two or more cells. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook includes HARQ-ACK information for the data scheduled by the first DCI. The second HARQ-ACK sub-codebook includes HARQ-ACK information for the data scheduled by the second DCI. The second HARQ-ACK sub-codebook is appended to the first HARQ-ACK sub-codebook. The HARQ-ACK information for the first SPS data is appended to the second HARQ-ACK sub-codebook.

11. The method according to claim 7, characterized in that, The first DCI uses a DCI format that can only schedule data from one cell. The second DCI schedules data from only one cell. The HARQ-ACK codebook includes a first HARQ-ACK sub-codebook, which includes HARQ-ACK information for the data scheduled by the first DCI and HARQ-ACK information for the data scheduled by the second DCI. The method further includes: A third DCI is sent to the terminal device. The DCI format of the third DCI is a DCI format that can schedule data from two or more cells or data from one cell. The third DCI schedules data from two or more cells. The HARQ-ACK codebook also includes a second HARQ-ACK sub-codebook. The second HARQ-ACK sub-codebook includes HARQ-ACK information of the data scheduled by the third DCI. The second HARQ-ACK sub-codebook is located after the first HARQ-ACK sub-codebook in the HARQ codebook. The HARQ-ACK information of the first SPS data is appended to the second HARQ-ACK sub-codebook.

12. The method according to claim 11, characterized in that, The HARQ-ACK codebook also includes HARQ-ACK information of the second SPS data, wherein the position of the HARQ-ACK information of the second SPS data in the HARQ-ACK codebook is after the position of the first HARQ-ACK sub-codebook and before the position of the second HARQ-ACK sub-codebook. The transmission of the second SPS data is activated by the fourth DCI. The DCI format of the fourth DCI is either a DCI format that can only schedule data from one cell, or a DCI format that can schedule data from two or more cells as well as data from one cell. The fourth DCI also activates the transmission of SPS data from only one cell at a time. The transmission of the first SPS data is activated by the fifth DCI. The DCI format of the fifth DCI is a DCI format that can schedule data from two or more cells or data from one cell. The fifth DCI simultaneously activates the transmission of SPS data from two or more cells.

13. A communication device, characterized in that, include: A processor for executing a computer program stored in a memory to cause the communication device to perform the method of any one of claims 1 to 12.

14. A computer-readable storage medium, characterized in that, It stores a computer program or instructions thereon, characterized in that, when the computer program or instructions are executed by a processor, the method as described in any one of claims 1 to 12 is performed.

15. A computer program product comprising instructions which, when executed on a computer, cause the method of any one of claims 1 to 12 to be performed.

Citation Information

Patent Citations

  • HARQ-ACK codebook feedback method and communication device

    CN114793360A

  • User equipments, base stations and methods

    US20190074929A1