Method and apparatus for sending and receiving HARQ-ACK codebook, storage medium, and computer program product

By using HARQ-ACK codebook multiplexing technology of different codebook types in the new 5G wireless system, the problem of resource waste when the terminal sends HARQ-ACK codebooks in multiple DCI formats is solved, and the efficient utilization of resources is achieved and The reliability of information transmission is improved.

WO2024240010A1PCT designated stage expired Publication Date: 2024-11-28HUAWEI TECH CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/092941
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-22
Filing Date
2024-05-13
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

In the new 5G wireless system, how the terminal efficiently sends HARQ-ACK codebooks to the base station, especially when the base station sends DCI in multiple formats, how to reduce the uplink channel resources occupied by feedback information and reduce the overhead of the control channel.

Method used

By sending HARQ-ACK feedback information corresponding to DCI scheduling data in multiple formats in the same uplink channel, using multiplexing technology of different codebook types, saving uplink channel resources, and configuring reasonable uplink channels according to the capabilities of the terminal, improving Reliability of information transmission.

Benefits of technology

It effectively saves resource overhead of uplink channels, improves the reliability and flexibility of information transmission, adapts to the capability configuration of different terminals, and improves the utilization rate of network resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024092941_28112024_PF_FP_ABST
    Figure CN2024092941_28112024_PF_FP_ABST
Patent Text Reader

Abstract

A method and apparatus for sending and receiving a HARQ-ACK codebook, a storage medium, and a computer program product, which are used for enabling a terminal to feed back two different types of HARQ-ACK codebooks by means of the same uplink channel when a base station sends DCI in various formats to the terminal. In the present application, the base station sends at least one first DCI and at least one second DCI to the terminal. The first DCI is traditional single-cell scheduling DCI, and the second DCI is multi-cell scheduling DCI. The codebook types of HARQ-ACK codebooks corresponding to the data scheduled by the first DCI and the second DCI are different. The terminal sends the HARQ-ACK codebooks corresponding to the data scheduled by the first DCI and the second DCI on the same uplink channel. The method enables feedback information to occupy fewer uplink channels and resources, thereby reducing resource consumption of the uplink channels.
Need to check novelty before this filing date? Find Prior Art

Description

Method, device, storage medium and computer program product for sending and receiving HARQ-ACK codebook

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to a Chinese patent application filed with the State Intellectual Property Office of China on May 22, 2023, with application number 202310584048.0 and application name “Method, device, storage medium and computer program product for sending and receiving HARQ-ACK codebook”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application relates to the field of wireless communication technologies, and in particular to a method, device, storage medium, and computer program product for sending and receiving a HARQ-ACK codebook. Background Art

[0004] In the 5G New Radio (NR) system, downlink physical layer data is carried by the physical downlink shared channel (PDSCH). A downlink control information (DCI) can schedule the PDSCH of a cell. This type of DCI is called "traditional DCI." When a terminal receives a PDSCH sent by a base station, it needs to send a hybrid automatic repeater request acknowledgment (HARQ-ACK) feedback message to the base station to inform the base station whether the transport block (TB) carried on the PDSCH has been successfully decoded. If the TB is successfully decoded, the terminal will feedback a positive acknowledgment (ACK); if the TB is not successfully decoded, the terminal will feedback a negative acknowledgment (NACK). The HARQ-ACK feedback information corresponding to one or more PDSCHs is concatenated to form a HARQ-ACK codebook. In other words, a HARQ-ACK codebook can include HARQ-ACK feedback information corresponding to one or more DCI-scheduled data.

[0005] To reduce the number of DCIs, the 3rd Generation Partnership Project (3GPP) Release (Rel)-18 work item (WI) has established the use of a new DCI to simultaneously schedule PDSCH reception in multiple cells. This new DCI can support scheduling data for one or more cells. This new DCI can reduce the number of DCIs and, in turn, reduce control channel overhead.

[0006] In the scenario where the base station schedules PDSCH through traditional DCI and this new DCI, how the terminal sends the HARQ-ACK codebook to the base station becomes a solution that needs to be solved urgently.

[0007] Summary of the Invention

[0008] The present application provides a HARQ-ACK codebook sending and receiving method, apparatus, storage medium, chip system, and computer program product, which are used to feedback the HARQ-ACK codebook corresponding to the DCI scheduled data in multiple formats through an uplink channel when a network device sends DCI in multiple formats, thereby saving the number and resources of uplink channels occupied by feedback information, thereby saving uplink channel resource overhead.

[0009] In a first aspect, the present application provides a method for transmitting a HARQ-ACK codebook. The method is performed by a first communication device, which may be a terminal, or a unit, module, or chip within the terminal. For ease of understanding, the following content is described using the first communication device as a terminal as an example.

[0010] In this method, a terminal receives at least one first DCI. The format of the first DCI is a DCI format for scheduling data for one cell. The first DCI is unicast DCI. The terminal receives at least one second DCI. The format of the second DCI is a DCI format that supports scheduling data for one or more cells. The terminal transmits a first HARQ-ACK codebook and a second HARQ-ACK codebook on a first uplink channel. The first HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to at least one data scheduled by the first DCI. The second HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to at least one data scheduled by the second DCI. The codebook type of the first HARQ-ACK codebook is different from the codebook type of the second HARQ-ACK codebook.

[0011] It can be seen that when the base station sends DCI in multiple formats and the codebook types corresponding to the feedback information of the data scheduled by the DCI in the multiple formats are different, the terminal can feedback the feedback information of the data scheduled by the DCI in the multiple formats in the same uplink channel. Compared with the solution that requires multiple uplink channels to respectively feedback the feedback information of the DCI in the multiple formats, this solution can save the number and resources of the uplink channels occupied by the feedback information, and thus save the resource overhead of the uplink channel.

[0012] When the codebook type of the second HARQ-ACK codebook is a dynamic codebook type, the second HARQ-ACK codebook may include multiple sub-codebooks, such as a first sub-codebook and a second sub-codebook, and each second DCI corresponding to the feedback information included in the first sub-codebook schedules data of one cell. Each second DCI corresponding to the feedback information included in the second sub-codebook schedules data of multiple cells.

[0013] In one possible implementation, when the codebook type of the second HARQ-ACK codebook is a dynamic codebook type: each second DCI in the at least one second DCI schedules data for one cell. In this way, the second HARQ-ACK codebook may include one subcodebook, that is, the second HARQ-ACK codebook includes the first subcodebook but does not include the second subcodebook. In this way, the size of the HARQ-ACK codebook reported by the terminal on the first uplink channel can be reduced, thereby improving the reliability of the reported information.

[0014] In another possible implementation, when the codebook type of the second HARQ-ACK codebook is a dynamic codebook type: each second DCI in the at least one second DCI schedules data of multiple cells. The number of cells scheduled by any two second DCIs may be the same or different, for example, the number of cells scheduled by one second DCI is two, and the number of cells scheduled by the other second DCI is two or three. In this way, the second HARQ-ACK codebook may include one subcodebook, that is, the second HARQ-ACK codebook includes the second subcodebook and does not include the first subcodebook. In this way, the size of the HARQ-ACK codebook reported by the terminal on the first uplink channel can be reduced, thereby improving the reliability of the reported information.

[0015] In one possible implementation, the terminal may further send first information. The first information indicates that the terminal supports multiplexing HARQ-ACK codebooks of different codebook types onto the same uplink channel. The terminal reporting the first information may also be understood as the terminal reporting the first capability of the terminal to the base station, where the first capability includes the terminal supporting multiplexing HARQ-ACK codebooks of different codebook types onto the same uplink channel.

[0016] Since the terminal can report the first capability, the base station can determine which terminals support the first capability and which do not support the first capability based on the information reported by the terminal, and then the HARQ-ACK codebooks of different codebook types for terminals supporting the first capability can be configured to be sent on the same uplink channel, and the HARQ-ACK codebooks of different codebook types for terminals that do not support the first capability are configured to be sent on multiple uplink channels. It can be seen that in this scheme, the base station can more reasonably and effectively configure uplink channels for multiple terminals with different capabilities in the network, thereby saving channel resource overhead.

[0017] In this application, “configure” can be replaced by “instruct”.

[0018] In one possible implementation, the terminal may further receive second information, where the second information enables the terminal to support the capability of multiplexing HARQ-ACK codebooks of different codebook types onto the same uplink channel. This may also be understood as the second information being used to enable the first capability of the terminal.

[0019] When uplink PUCCH or PUSCH resources are relatively tight, for UEs that support HARQ-ACK codebook multiplexing of different codebook types, the base station can enable this function and configure the UE to multiplex different types of HARQ-ACK codebooks on the same PUCCH or PUSCH for reporting, thereby improving uplink resource utilization. When uplink PUCCH or PUSCH resources are relatively abundant, this function can be disabled and the UE can be configured to feedback different types of HARQ-ACK codebooks in a time-division manner, thereby avoiding scheduling restrictions and increasing base station scheduling flexibility.

[0020] In a possible implementation, the second HARQ-ACK codebook is attached to the first HARQ-ACK codebook.

[0021] In the present application, the codebook type of the first HARQ-ACK codebook is different from the codebook type of the second HARQ-ACK codebook. For example, the codebook type of the first HARQ-ACK codebook is a semi-static codebook type, and the codebook type of the second HARQ-ACK codebook is a dynamic codebook type; or, the first HARQ-ACK codebook is a dynamic codebook type, and the codebook type of the second HARQ-ACK codebook is a semi-static codebook type.

[0022] In one possible implementation, the DCI (the first DCI or the second DCI mentioned above) includes a resource indication field of an uplink channel (such as PUCCH or PUSCH), and the resource indication field of the uplink channel can indicate the resources of the uplink channel used to feedback the HARQ-ACK code block. In another possible implementation, the DCI may include a priority indication field, and the priority indication field may indicate a priority index value, and the priority indication field may not directly indicate the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the DCI. The priority indication field can indicate the priority of the uplink channel corresponding to the DCI, and since the HARQ-ACK feedback information corresponding to the data scheduled by the DCI needs to be fed back on the uplink channel, it can be understood that: the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the DCI is the same as the priority of the uplink channel indicated by the resource indication field of the uplink channel in the DCI, and it can also be understood that: the priority indication field in the DCI indirectly indicates the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the DCI. In this application, the "priority of HARQ-ACK feedback information" and the "priority of the HARQ-ACK codebook" can be interchanged.

[0023] In another possible implementation, the HARQ-ACK feedback information corresponding to the first DCI scheduled data and the HARQ-ACK feedback information corresponding to the second DCI scheduled data have the same priority. In this way, the terminal can feedback the first HARQ-ACK codebook and the second HARQ-ACK codebook in the same uplink channel so that the transmission reliability of the feedback information corresponding to services with the same priority is the same.

[0024] In the present application, the first uplink channel may include PUCCH or PUSCH.

[0025] In a second aspect, the present application provides a method for receiving a HARQ-ACK codebook. The method is applicable to a second communication device. The second communication device may be a network device (such as a base station), or a unit, module, or chip within the network device (such as a base station). For ease of understanding, the following content is introduced using the second communication device as a base station as an example.

[0026] In this method, a base station sends at least one first downlink control information (DCI). The format of the first DCI is a DCI format used to schedule data for one cell. The first DCI is unicast DCI. The base station sends at least one second DCI. The format of the second DCI is a DCI format that supports scheduling data for one or more cells. The base station receives a first HARQ-ACK codebook and a second HARQ-ACK codebook on a first uplink channel. The first HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to at least one data scheduled by the first DCI. The second HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to at least one data scheduled by the second DCI. The codebook type of the first HARQ-ACK codebook is different from the codebook type of the second HARQ-ACK codebook.

[0027] In a possible implementation, when the codebook type of the second HARQ-ACK codebook is a dynamic codebook type: each second DCI in the at least one second DCI schedules data of one cell.

[0028] In a possible implementation, when the codebook type of the second HARQ-ACK codebook is a dynamic codebook type: each second DCI in the at least one second DCI schedules data of multiple cells.

[0029] In a possible implementation, when the codebook type of the second HARQ-ACK codebook is a dynamic codebook type: the second HARQ-ACK codebook includes a first subcodebook or a second subcodebook. Each second DCI corresponding to the feedback information included in the first subcodebook schedules data of one cell. Each second DCI corresponding to the feedback information included in the second subcodebook schedules data of multiple cells.

[0030] In a possible implementation, the base station receives first information, where the first information indicates that the terminal supports multiplexing HARQ-ACK codebooks of different codebook types onto the same uplink channel.

[0031] In a possible implementation, the base station sends second information, where the second information enables the terminal to support the capability of multiplexing HARQ-ACK codebooks of different codebook types onto the same uplink channel.

[0032] In a possible implementation, the second HARQ-ACK codebook is attached to the first HARQ-ACK codebook.

[0033] In a possible implementation, the codebook type of the first HARQ-ACK codebook is a semi-static codebook type, and the codebook type of the second HARQ-ACK codebook is a dynamic codebook type; or, the first HARQ-ACK codebook is a dynamic codebook type, and the codebook type of the second HARQ-ACK codebook is a semi-static codebook type.

[0034] In a possible implementation, the HARQ-ACK feedback information corresponding to the first DCI scheduled data is the same as the HARQ-ACK feedback information corresponding to the second DCI scheduled data.

[0035] In a possible implementation manner, the first uplink channel includes a PUCCH or a PUSCH.

[0036] For the relevant contents and beneficial effects involved in the second aspect and possible implementation methods of the second aspect, please refer to the relevant description of the first aspect and possible implementation methods of the first aspect, and no further details will be given.

[0037] In a third aspect, a communication device is provided, which may be the aforementioned first communication device or the second communication device. The communication device may include a communication unit and a processing unit to perform any aspect of the aforementioned first to second aspects, or to perform any possible implementation of the first to second aspects. The communication unit is used to perform functions related to sending and receiving. Optionally, the communication unit includes a receiving unit and a sending unit. In one design, the communication device is a communication chip, the processing unit may be one or more processors or processor cores, and the communication unit may be an input / output circuit or port of the communication chip.

[0038] In another design, the communication unit may be a transmitter and a receiver, or the communication unit may be a transmitter and a receiver.

[0039] Optionally, the communication device further includes modules that can be used to execute any one of the first to second aspects above, or execute any possible implementation of the first to second aspects.

[0040] In a fourth aspect, a communication device is provided, which may be the aforementioned first communication device or the second communication device. The communication device may include a processor and a memory to perform any aspect of the aforementioned first to second aspects, or to perform any possible implementation of the aforementioned first to second aspects. Optionally, a transceiver is further included, the memory is used to store a computer program or instruction, and the processor is used to call and run the computer program or instruction from the memory. When the processor executes the computer program or instruction in the memory, the communication device performs any aspect of the aforementioned first to second aspects, or to perform any possible implementation of the aforementioned first to second aspects.

[0041] Optionally, there are one or more processors and one or more memories.

[0042] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0043] Optionally, the transceiver may include a transmitter (transmitter) and a receiver (receiver).

[0044] In a fifth aspect, a communication device is provided. This communication device may be the aforementioned first or second communication device. The communication device may include a processor to perform any of the aforementioned first and second aspects, or any possible implementation of the first and second aspects. The processor is coupled to a memory. Optionally, the communication device also includes a memory. Optionally, the communication device also includes a communication interface, and the processor is coupled to the communication interface.

[0045] In one implementation, when the communication device is the first communication device or the second communication device, the communication interface may be a transceiver or an input / output interface. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0046] In another implementation, when the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0047] In a sixth aspect, a system is provided, which includes the above-mentioned first communication device.

[0048] In a possible implementation, the system may further include a second communication device.

[0049] In the seventh aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables the computer to execute any one of the above-mentioned first to second aspects, or any possible implementation of the first to second aspects.

[0050] In an eighth aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code, or instructions). When the computer program is run on a computer, the computer executes any one of the above-mentioned first to second aspects, or executes any possible implementation of the first to second aspects.

[0051] In a ninth aspect, a processing device is provided, comprising: an interface circuit and a processing circuit. The interface circuit may include an input circuit and an output circuit. The processing circuit is configured to receive signals via the input circuit and transmit signals via the output circuit, thereby implementing any of the first and second aspects above, or any possible implementation of the first and second aspects.

[0052] In a specific implementation, the processing device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter. The input circuit and the output circuit may be the same circuit, which functions as an input circuit and an output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0053] In one implementation, when the communication device is the first communication device or the second communication device, the interface circuit may be a radio frequency processing chip in the first communication device or the second communication device, and the processing circuit may be a baseband processing chip in the first communication device or the second communication device.

[0054] In another implementation, the communication device may be a component of the first communication device or the second communication device, such as an integrated circuit product such as a system-on-chip (SoC) or a communication chip. The interface circuit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processing circuit may be a logic circuit on the chip. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] FIG1 is a schematic diagram of a HARQ scenario applicable to an embodiment of the present application;

[0056] FIG2 is a schematic diagram of the architecture of a communication system applicable to an embodiment of the present application;

[0057] FIG3 is a schematic diagram of a method for sending and receiving a HARQ-ACK codebook provided in an embodiment of the present application;

[0058] FIG4A is a schematic diagram of the structure of a HARQ-ACK codebook fed back by a terminal according to an embodiment of the present application;

[0059] FIG4B is a schematic diagram of the structure of another HARQ-ACK codebook fed back by a terminal according to an embodiment of the present application;

[0060] FIG5 is a schematic diagram of the structure of another HARQ-ACK codebook fed back by a terminal according to an embodiment of the present application;

[0061] FIG6 is a schematic diagram of the structure of another HARQ-ACK codebook fed back by a terminal according to an embodiment of the present application;

[0062] FIG7 is a schematic structural diagram of another HARQ-ACK codebook fed back by a terminal according to an embodiment of the present application;

[0063] FIG8 is a schematic structural diagram of another HARQ-ACK codebook fed back by a terminal according to an embodiment of the present application;

[0064] FIG9 is a schematic structural diagram of another HARQ-ACK codebook fed back by a terminal according to an embodiment of the present application;

[0065] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0066] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0067] The following is an introduction to the nouns and terms involved in the embodiments of this application.

[0068] (1) Cell and carrier.

[0069] A cell can be an area of ​​wireless coverage identified by a base station identification code or a global cell identification code. A cell can be simply understood as an area where a base station provides wireless coverage.

[0070] In NR, in non-carrier aggregation (CA) scenarios, users are generally connected to only one cell, that is, this cell can be considered as the user's only serving cell. In carrier aggregation scenarios, users may be connected to multiple cells. The cell that initiates initial access can be called the primary cell (PCell), which is used to establish a radio resource control (RRC) connection between the user and the network. Based on the user's transmission requirements, the network can configure a secondary cell (SCell) for the user to provide additional uplink or downlink transmission resources. The secondary cell can be configured through the primary cell RRC signaling, and can be flexibly activated / deactivated through the medium access control control element (MAC CE) / DCI signaling.

[0071] A carrier is a radio signal (electromagnetic wave) with a specific frequency, bandwidth, and format, emitted by the main equipment of a base station. The carrier is the main body used to carry information, so it is called "carrier" or "carrier frequency", and can also be called component carrier (CC).

[0072] In the embodiments of the present application, "cell" and "carrier" can be interchanged.

[0073] (2)DCI.

[0074] The embodiments of the present application involve DCIs of various formats, such as traditional DCIs used to schedule a single cell, and multi-cell scheduling DCIs that support scheduling one or more cells.

[0075] The multiple formats of DCI in the embodiments of the present application can be applied to multiple scenarios. In each scenario, traditional DCI and multi-cell scheduling DCI can have different names, for example: multi-cell scheduling DCI can also be called new (new) DCI, or single (single) DCI.

[0076] In the embodiment of the present application, the data scheduled by DCI (the above-mentioned traditional DCI and multi-cell scheduling DCI) can be carried on PDSCH or physical uplink shared channel (PUSCH). DCI is carried on physical downlink control channel (PDCCH).

[0077] The DCI discussed in this application may be unicast DCI. Unicast DCI may be understood as DCI that is scrambled with a cyclic redundancy check (CRC) using a cell-radio network temporary identifier (C-RNTI), a modulation coding scheme cell-radio network temporary identifier (MCS-C-RNTI), and a configured scheduling-radio network temporary identifier (CS-RNTI).

[0078] (2.1) Traditional DCI

[0079] Traditional DCI supports scheduling data for a single cell (or scheduling data transmission in a single cell), but does not support scheduling data for multiple cells. In the embodiments of the present application, "cell" can be replaced with "carrier," so it can also be said that traditional DCI supports scheduling data for a single carrier, but does not support scheduling data for multiple carriers.

[0080] The formats of conventional DCI may include, for example, DCI format 0_0, DCI format 1_0, DCI format 0_1, DCI format 1_1, DCI format 0_2, or DCI format 1_2. DCI format 0_0 and DCI format 1_0 may be configured in a common search space or a user-specific search space (USS).

[0081] (2.2) Multi-cell scheduling DCI.

[0082] Multi-cell scheduling DCI supports scheduling data transmission on multiple cells (any multiple cells in the primary cell and the secondary cell, or any multiple cells in the secondary cell), and also supports scheduling data transmission on a single cell (which can be either the primary cell or the secondary cell). In the embodiments of the present application, "cell" can be replaced with "carrier", so it can also be said that: Multi-cell scheduling DCI supports scheduling data on one or multiple carriers.

[0083] When multi-cell scheduling DCI is used to schedule uplink data carried on the PUSCH, the format of the multi-cell scheduling DCI may include, for example, DCI format 0_X or DCI format 0_3. When multi-cell scheduling DCI is used to schedule downlink data carried on the PDSCH, the format of the multi-cell scheduling DCI may include, for example, DCI format 1_X or DCI format 1_3. DCI format 0_3 can be used to schedule N PUSCHs in N cells. DCI format 1_3 can be used to schedule N PDSCHs in N cells, where N is a positive integer.

[0084] (3)HARQ-ACK codebook.

[0085] In wireless communication systems, the hybrid automatic repeat request (HARQ) technology is typically used between the sender and receiver to improve data transmission reliability. The sender sends a TB. The receiver then provides the sender with a HARQ-ACK codebook based on the reception status. Alternatively, the HARQ-ACK codebook is used to provide feedback on PDSCH reception, semi-persistent scheduling (SPS) PDSCH reception, or SPS PDSCH release reception.

[0086] In the embodiment of the present application, the HARQ-ACK codebook can be understood as a bit sequence, which is constructed using ACK / NACK feedback received for multiple PDSCHs in a configured time window.

[0087] The HARQ-ACK codebook, HARQ-ACK information, and HARQ-ACK feedback information in the embodiments of the present application can be replaced with each other if there is no logical conflict.

[0088] In another possible implementation, the HARQ-ACK codebook may be a data block obtained after the HARQ-ACK feedback information undergoes a series of physical layer processing (for example, including at least one of CRC addition, code block (CB) segmentation, CB CRC addition, channel coding, or rate matching).

[0089] The HARQ-ACK codebook includes an ACK for indicating correct decoding (the corresponding bit value can be 1) and a NACK for indicating abnormal decoding (the corresponding bit value can be 0). The sender sends a TB. If the receiver successfully receives the TB (that is, the TB is decoded normally), an ACK is fed back to the sender. If the receiver does not successfully receive the TB (that is, the TB is decoded abnormally), a NACK is fed back to the sender. After receiving the NACK, the sender can retransmit the TB. In the embodiment of the present application, the decoding abnormality may include not receiving the PDCCH, not receiving the PDSCH, or a PDSCH CRC check error.

[0090] The HARQ-ACK codebook may be carried on a physical uplink control channel (PUCCH) or a PUSCH.

[0091] FIG1 exemplarily illustrates a schematic diagram of a HARQ scenario applicable to an embodiment of the present application. As shown in FIG1 , a second communication device transmits a DCI in time slot n. The DCI instructs the terminal to receive the PDSCH in time slot n+K0 and to feed back the HARQ-ACK codebook on the PUCCH resource in time slot n+K0+K1. The K0 value, K1 value, and PUCCH resource information can be indicated by the DCI carried in time slot n.

[0092] (4) Codebook type of HARQ-ACK codebook.

[0093] The codebook type of the HARQ-ACK codebook includes a semi-static HARQ-ACK codebook type and a dynamic HARQ-ACK codebook type.

[0094] In the embodiment of the present application, the semi-static HARQ-ACK codebook type may also be referred to as a type (type) -1 HARQ-ACK codebook type. When the codebook type of the HARQ-ACK codebook is a semi-static HARQ-ACK codebook type, the HARQ-ACK codebook may also be referred to as a semi-static HARQ-ACK codebook or a type-1 HARQ-ACK codebook. The HARQ-ACK feedback information of one DCI-scheduled data corresponds to at least one bit on the type-1 HARQ-ACK codebook, for example, a bit value of 1 indicates ACK, and a bit value of 0 indicates NACK. The size of the type-1 HARQ-ACK codebook is fixed and has nothing to do with the number of PDSCHs actually scheduled by the DCI.

[0095] In the embodiment of the present application, the dynamic HARQ-ACK codebook type may also be referred to as a type-2 HARQ-ACK codebook type. When the codebook type of the HARQ-ACK codebook is a dynamic HARQ-ACK codebook type, the HARQ-ACK codebook may also be referred to as a dynamic HARQ-ACK codebook or a type-2 HARQ-ACK codebook. The HARQ-ACK feedback information of a DCI-scheduled data may correspond to one or more bits in the type-2 HARQ-ACK codebook. The size of the type-2 HARQ-ACK codebook is determined according to the number of DCIs or the number of PDSCHs scheduled by the DCI.

[0096] Figure 2 exemplarily shows an architectural diagram of a communication system 1000 applicable to an embodiment of the present application. As shown in Figure 2, Figure 2 is a schematic diagram of the architecture of the communication system 1000 applied to an embodiment of the present application. As shown in Figure 2, the communication system includes a radio access network (RAN) 100 and a core network 200. Optionally, the communication system 1000 may also include the Internet 300. The RAN 100 includes at least one RAN node (such as 110a and 110b in Figure 2, collectively referred to as 110), and may also include at least one terminal (such as 120a-120j in Figure 2, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in Figure 2). The terminal 120 is connected to the RAN node 110 via a wireless method, and the RAN node 110 is connected to the core network 200 via a wireless or wired method. The core network devices in the core network 200 and the RAN nodes 110 in the RAN 100 may be independent and distinct physical devices, or they may be a single physical device that integrates the logical functions of the core network devices and the logical functions of the RAN nodes. Terminals and RAN nodes may be connected to each other via wired or wireless means.

[0097] RAN100 may be an evolved universal terrestrial radio access (E-UTRA) system, a NR system, or a future radio access system defined in the 3rd Generation Partnership Project (3GPP). RAN100 may also include two or more of the aforementioned different radio access systems. RAN100 may also be an open RAN (O-RAN).

[0098] The network equipment involved in the embodiments of the present application may be a RAN node. A RAN node, also known as a radio access network device, a RAN entity or an access node, is used to help a terminal access a communication system wirelessly. In one application scenario, a RAN node may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation (5G) mobile communication system, a next generation base station in a sixth generation (6G) mobile communication system, or a base station in a future mobile communication system. A RAN node may be a macro base station (such as 110a in FIG2 ), a micro base station or an indoor station (such as 110b in FIG2 ), or a relay node or a donor node.

[0099] In another application scenario, multiple RAN nodes can collaborate to help terminals achieve wireless access, with different RAN nodes implementing portions of the base station's functions. For example, a RAN node can be a centralized unit (CU), a distributed unit (DU), or a radio unit (RU). The CU implements the base station's radio resource control protocol and packet data convergence protocol (PDCP) functions, as well as the service data adaptation protocol (SDAP) functions. The DU implements the base station's radio link control layer and medium access control (MAC) layer functions, as well as some or all of the physical layer functions. For detailed descriptions of each of the above protocol layers, please refer to the relevant 3GPP technical specifications. The RU can be used to implement the transmission and reception of radio frequency signals. The CU and DU can be two independent RAN nodes, or they can be integrated into the same RAN node, such as in a baseband unit (BBU). The RU can be included in radio frequency equipment, such as a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.

[0100] In different systems, RAN nodes may have different names. For example, in an O-RAN system, a CU may be called an open CU (O-CU), a DU may be called an open DU (O-DU), and a RU may be called an open RU (O-RU). The RAN node in the embodiments of the present application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module. For example, the RAN node may be a server loaded with the corresponding software module. The embodiments of the present application do not limit the specific technology and specific device form adopted by the RAN node. For ease of description, the following description takes a base station as an example of a RAN node.

[0101] A terminal is a device with wireless transceiver capabilities that can send signals to a base station or receive signals from a base station. A terminal may also be referred to as a terminal device, 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 grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. A terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the terminal.

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

[0103] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 2 can be configured as a mobile base station. To terminals 120j accessing the wireless access network 100 via 120i, terminal 120i is a base station. However, to base station 110a, 120i is a terminal, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via a base station-to-base station interface protocol. In this case, 120i is also a base station relative to 110a. Therefore, base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 2 can be referred to as communication devices with base station functionality, while 120a-120j in Figure 2 can be referred to as communication devices with terminal functionality.

[0104] Communication between base stations and terminals, between base stations, and between terminals can be carried out through authorized spectrum, unauthorized spectrum, or both; communication can be carried out through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

[0105] In the embodiments of the present application, the functions of the base station may also be performed by a module (such as a chip) in the base station, or by a control subsystem that includes the base station functions. The control subsystem that includes the base station functions here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal may also be performed by a module (such as a chip or modem) in the terminal, or by a device that includes the terminal functions.

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

[0107] It can be understood that in the embodiments of the present application, PDSCH, PDCCH and PUSCH are merely examples of downlink data channels, downlink control channels and uplink data channels, respectively. In different systems and different scenarios, data channels and control channels may have different names, and the embodiments of the present application do not limit this.

[0108] Based on the embodiments shown in Figures 1 and 2, Figure 3 exemplarily shows a schematic diagram of a method for sending and receiving a HARQ-ACK codebook provided in an embodiment of the present application. The terminal in Figure 3 may be the terminal shown in Figure 2 above, and the base station in Figure 3 may be the RAN node in Figure 2 above. It is understandable that the method performed by the terminal in the method shown in Figure 3 may also be performed by a module (such as a chip) applied to the terminal, and the method performed by the base station may also be performed by a RAN node (such as a CU or DU) or by a module (such as a chip) applied to the base station.

[0109] As shown in FIG3 , the method includes:

[0110] Step 301: The terminal sends first information to the base station.

[0111] The first information indicates that the terminal supports multiplexing HARQ-ACK codebooks of different codebook types into the same uplink channel.

[0112] Reporting of the first information by the terminal may also be understood as reporting of the first capability of the terminal to the base station by the terminal, where the first capability includes support for multiplexing of HARQ-ACK codebooks of different codebook types onto the same uplink channel by the terminal.

[0113] Since the terminal can report the first capability, the base station can determine which terminals support the first capability and which do not support the first capability based on the information reported by the terminal, and then the HARQ-ACK codebooks of different codebook types for terminals supporting the first capability can be configured to be sent on the same uplink channel, and the HARQ-ACK codebooks of different codebook types for terminals that do not support the first capability are configured to be sent on multiple uplink channels. It can be seen that in this scheme, the base station can more reasonably and effectively configure uplink channels for multiple terminals with different capabilities in the network, thereby saving channel resource overhead.

[0114] Step 302: The base station sends second information to the terminal.

[0115] The second information enables the first capability. For example, the base station can enable (or activate) the first capability of the terminal through parameters (such as parameters carried in an RRC message). The terminal can use the first capability only after the base station enables the first capability of the terminal.

[0116] In another possible implementation, the base station may enable (or deactivate) the first capability of the terminal through parameters (such as parameters carried in an RRC message). After the base station deactivates the first capability of the terminal, the terminal cannot use the first capability.

[0117] When uplink PUCCH or PUSCH resources are limited, the network device can enable the first capability of the terminal and configure HARQ-ACK codebooks of different codebook types to be transmitted on the same uplink channel, thereby improving the utilization of uplink resources. When uplink PUCCH or PUSCH resources are sufficient, the network device can disable the first capability of the terminal and configure HARQ-ACK codebooks of different codebook types to be sent on different uplink channels, thereby avoiding scheduling restrictions and increasing the flexibility of base station scheduling.

[0118] Step 303: The base station sends at least one first DCI.

[0119] Correspondingly, the terminal receives at least one first DCI.

[0120] For the sake of distinction, in the embodiments of the present application, a portion (one or more) of the DCI sent by the base station is referred to as the first DCI. The format of the first DCI is the DCI format used to schedule data for a single cell. The first DCI is a unicast DCI. The first DCI may be a traditional DCI. For details about the traditional DCI, refer to the previous description and are not repeated here.

[0121] In the embodiment of the present application, each first DCI schedules data of one cell.

[0122] The cell scheduling method of the first DCI can be a self-cell (or self-carrier) scheduling method, or a cross-cell (or cross-carrier) scheduling method. For example, the base station sends the first DCI: DCI#1 on CC#1 (or cell#1). DCI#1 is used to schedule data of CC#1 (or cell#1) (self-carrier scheduling scheduling method), or DCI#1 is used to schedule data of CC#2 (or cell#2) (cross-carrier scheduling method). In the embodiment of the present application, the cell scheduling methods of any two first DCIs may be the same or different.

[0123] Step 302 is an optional step and may not be performed in the embodiment shown in Figure 3. For example, if the terminal has the first capability, the first capability may be enabled when the first capability is needed, without the base station enabling (or activating) it through signaling.

[0124] Step 304: The base station sends at least one second DCI.

[0125] Correspondingly, the terminal receives at least one second DCI.

[0126] For the sake of distinction, in the embodiments of the present application, a portion (one or more) of the DCI sent by the base station is referred to as the second DCI. The format of the second DCI is a DCI format that supports scheduling data for one or more cells. The second DCI is unicast DCI. The second DCI can be multi-cell scheduling DCI. For the relevant content of multi-cell scheduling DCI, please refer to the previous description and will not be repeated here.

[0127] In the embodiment of the present application, the base station can schedule data of one (or more) cells through a second DCI. The number of cells scheduled by any two second DCIs can be the same or different. In this way, the flexibility of the solution can be increased.

[0128] For example, the base station sends a second DCI: DCI#2 on cell #1 (or CC#1). DCI#2 is used to schedule data for cell #1 (or CC#1); or DCI#2 is used to schedule data for cell #2 (or CC#2); or DCI#2 is used to schedule data for cell #1 (or CC#1) and cell #2 (or CC#2); or DCI#2 is used to schedule data for cell #2 (or CC#2) and cell #3 (or CC#3).

[0129] In the above example, the base station may also send other second DCIs. For example, the base station sends a second DCI: DCI#3 in cell #2 (or CC#2). The number of cells scheduled by DCI#3 may be the same as or different from the number of cells scheduled by DCI#2. For example, DCI#2 is used to schedule data for cell #1 (or CC#1), and DCI#3 is used to schedule data for cell #2 (or CC#2). For another example, DCI#2 is used to schedule data for cell #1 (or CC#1) and cell #3 (or CC#3), and DCI#3 is used to schedule data for cell #2 (or CC#2).

[0130] It can be seen that one second DCI can schedule data for one or more cells, thereby saving the number of DCIs, reducing the overhead of the control channel, releasing more resources for data transmission, improving downlink capacity, and thus approaching the performance of a continuous broadband carrier.

[0131] Step 305: The terminal sends a first HARQ-ACK codebook and a second HARQ-ACK codebook on a first uplink channel.

[0132] Correspondingly, the base station receives the first HARQ-ACK codebook and the second HARQ-ACK codebook.

[0133] In this embodiment of the present application, the terminal may feedback multiple HARQ-ACK codebooks. For the purpose of distinction, in this embodiment of the present application, the codebooks among the multiple HARQ-ACK codebooks fed back by the terminal are exemplarily referred to as the first HARQ-ACK codebook and the second HARQ-ACK codebook.

[0134] The first HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to at least one first DCI-scheduled data. The second HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to at least one second DCI-scheduled data.

[0135] The base station can independently configure the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook. For example, the base station can configure the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook respectively through two independent high-layer parameters. The codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook may be different or the same. In this way, the base station can configure the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook according to actual needs, thereby making the configured codebook type more reasonable.

[0136] In one possible implementation, the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook are different. For example, the codebook type of the first HARQ-ACK codebook is a type-1 HARQ-ACK codebook type (or a semi-static HARQ-ACK codebook type, or the first HARQ-ACK codebook is referred to as a type-1 HARQ-ACK codebook, and the relevant content is referred to as the above description and will not be repeated). The codebook type of the second HARQ-ACK codebook is a type-2 HARQ-ACK codebook type (or a dynamic HARQ-ACK codebook type, or the second HARQ-ACK codebook is referred to as a type-2 HARQ-ACK codebook, and the relevant content is referred to as the above description and will not be repeated). For another example, the codebook type of the first HARQ-ACK codebook is a type-2 HARQ-ACK codebook type (the first HARQ-ACK codebook may also be referred to as a type-2 HARQ-ACK codebook), and the codebook type of the second HARQ-ACK codebook is a type-1 HARQ-ACK codebook type (the second HARQ-ACK codebook may also be referred to as a type-1 HARQ-ACK codebook).

[0137] In the embodiment of the present application, the first uplink channel may be, for example, a PUCCH or a PUSCH. On the first uplink channel, the positions of the first HARQ-ACK codebook and the second HARQ-ACK codebook may be flexibly set, for example, the second HARQ-ACK codebook may be attached to the first HARQ-ACK codebook.

[0138] Figures 4A and 4B illustrate schematic diagrams of the structures of several terminals according to embodiments of the present application feeding back the first HARQ-ACK codebook and the second HARQ-ACK codebook via the first channel. In Figures 4A and 4B, the first DCI is a traditional DCI, the second DCI is a multi-cell scheduling DCI, and the second HARQ-ACK codebook is attached to the first HARQ-ACK codebook.

[0139] In FIG4A , the first HARQ-ACK codebook is a type-2 HARQ-ACK codebook, and the second HARQ-ACK codebook is a type-1 HARQ-ACK codebook. As shown in FIG4A , when the first HARQ-ACK codebook is a type-2 HARQ-ACK codebook, since one first DCI can only schedule one cell (or carrier), the first HARQ-ACK codebook includes only one sub-codebook, thereby reducing the size of the HARQ-ACK codebook and improving transmission reliability.

[0140] FIG4B illustrates an example in which the first HARQ-ACK codebook is a type-1 HARQ-ACK codebook and the second HARQ-ACK codebook is a type-2 HARQ-ACK codebook. As shown in FIG4B , when the second HARQ-ACK codebook is a type-2 HARQ-ACK codebook, the second HARQ-ACK codebook may include two sub-codebooks, namely a first sub-codebook and a second sub-codebook.

[0141] The first subcodebook may carry HARQ-ACK feedback information corresponding to the data scheduled by at least one second DCI for scheduling one cell. In this embodiment of the present application, the first subcodebook in the second HARQ-ACK codebook (type-2 HARQ-ACK codebook) may also be referred to as a first type-2 HARQ-ACK subcodebook, and the second DCI (e.g., DCI format 1_3) corresponding to the first type-2 HARQ-ACK subcodebook does not schedule PDSCH reception of multiple (or more than one) cells in a cell set.

[0142] The second subcodebook may carry HARQ-ACK feedback information corresponding to at least one second DCI-scheduled data for scheduling more than one (or multiple) cells. The second subcodebook in the second HARQ-ACK codebook (type-2 HARQ-ACK codebook) in this embodiment of the present application may also be referred to as a second type-2 HARQ-ACK subcodebook, and the second DCI corresponding to the second type-2 HARQ-ACK subcodebook (e.g., DCI format 1_3) schedules PDSCH reception of multiple (or more than one) cells in a cell set.

[0143] From the above content, it can be seen that when the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook are different, the terminal can also feedback the two codebooks in the same uplink channel (ie, the first uplink channel), thereby saving the number and resources of uplink channels occupied by feedback information, and thus saving the resource overhead of the uplink channel.

[0144] Some steps in FIG. 3 of the embodiment of the present application are optional, such as step 301 and step 302. Step 301 and / or step 302 may not be performed. The order of the steps in the embodiment shown in FIG. 3 can also be flexibly set, such as step 301 can be after step 302, step 303, step 304, and / or step 305, etc. For another example, step 302 can be before step 301, or step 302 can be after step 303, step 304, and / or step 305, etc.

[0145] It can be seen from the example shown in FIG. 4B above that in an embodiment of the present application, the terminal may multiplex the codebooks corresponding to the HARQ-ACK feedback information of different codebook types by concatenation. When the second HARQ-ACK codebook is a type-2 HARQ-ACK codebook, it is likely that three sub-codebooks need to be transmitted on the first channel, resulting in the HARQ-ACK codebook transmitted on the first channel (the HARQ-ACK codebook includes the first HARQ-ACK codebook and the second HARQ-ACK codebook) being too large, which brings difficulties to decoding.

[0146] In the embodiment of the present application, the size of the HARQ-ACK codebook may also be referred to as the payload size. The size of the HARQ-ACK codebook may refer to the number of information bits of the HARQ-ACK codebook, or may be understood as the number of bits occupied by the payload in the HARQ-ACK codebook.

[0147] In order to further reduce the size of the HARQ-ACK codebook transmitted on the first channel, in one possible implementation, the base station may control the number of cells scheduled by the second DCI. For example, a constraint condition is set, and the constraint condition includes: each second DCI in at least one second DCI schedules data for one cell. Or the constraint condition includes: each second DCI in at least one second DCI schedules data for multiple cells. When the base station determines that the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook are different, the base station may use the above constraint condition to configure the number of cells scheduled by the second DCI, so that the HARQ-ACK codebook sent by the terminal includes a sub-codebook, thereby reducing the size of the HARQ-ACK codebook and improving transmission reliability.

[0148] For example, each second DCI in the at least one second DCI schedules data for one cell. In this way, the second HARQ-ACK codebook includes the first subcodebook but does not include the second subcodebook. Each second DCI corresponding to the feedback information included in the first subcodebook schedules data for one cell.

[0149] For another example, each second DCI in at least one second DCI schedules data for multiple cells. The number of cells scheduled by any two second DCIs is the same or different. In this case, the second HARQ-ACK codebook may include the second subcodebook but not the first subcodebook. Each second DCI corresponding to the feedback information included in the second subcodebook schedules data for multiple cells.

[0150] Figures 5 and 6 illustrate schematic diagrams of structures in which several terminals feed back the first HARQ-ACK codebook and the second HARQ-ACK codebook on the first channel. The contents shown in Figures 5 and 6 can refer to the relevant contents of Figure 4B above, with the difference that the second HARQ-ACK codebook in Figure 5 does not include the second subcodebook, and the second HARQ-ACK codebook in Figure 6 does not include the first subcodebook.

[0151] Through the above implementation and the contents shown in Figures 5 and 6, it can be seen that in this implementation, since the base station controls the number of cells scheduled by the second DCI in at least one second DCI, the second HARQ-ACK codebook can include only one sub-codebook, thereby reducing the size of the HARQ-ACK codebook fed back on the first uplink channel, thereby improving the reliability of uplink control information (UCI) transmission.

[0152] In the embodiment of the present application, the terminal can execute the scheme shown in Figure 3 on multiple uplink channels. For the schemes on other uplink channels, please refer to the content shown in Figure 3 and will not be repeated here. The codebook types of the two first HARQ-ACK codebooks transmitted on any two uplink channels may be the same or different. The codebook types of the two second HARQ-ACK codebooks transmitted on any two uplink channels may be the same or different. The two subcodebooks included in the two second HARQ-ACK codebooks transmitted on any two uplink channels may both be the first subcodebook (or the second subcodebook), or the first subcodebook and the second subcodebook, respectively. It can also be understood that the codebook type of the HARQ-ACK codebooks transmitted on the two uplink channels and the form of the included subcodebooks are not necessarily the same and may also be different. A possible example is introduced below through Figure 7.

[0153] Figure 7 exemplarily shows a schematic diagram of the structure of another HARQ-ACK codebook fed back by a terminal. As shown in Figure 7 , the terminal can send PUCCH#1 in time slot n+1 and PUCCH#2 in time slot n+T1.

[0154] The terminal feeds back HARQ-ACK codebook #1 (which can be regarded as the first HARQ-ACK codebook in PUCCH #1) and HARQ-ACK codebook #2 (which can be regarded as the second HARQ-ACK codebook in PUCCH #1) in PUCCH #1. HARQ-ACK codebook #1 carries feedback information corresponding to the data scheduled by traditional DCI. HARQ-ACK codebook #1 is a type-1 HARQ-ACK codebook. HARQ-ACK codebook #2 carries feedback information corresponding to the data scheduled by multi-cell DCI. HARQ-ACK codebook #2 is a type-2 HARQ-ACK codebook. Figure 7 illustrates an example in which HARQ-ACK codebook #2 includes the first sub-codebook but does not include the second sub-codebook.

[0155] The terminal feeds back HARQ-ACK codebook #3 (which can be regarded as the first HARQ-ACK codebook in PUCCH #2) and HARQ-ACK codebook #4 (which can be regarded as the second HARQ-ACK codebook in PUCCH #2) in PUCCH #2. HARQ-ACK codebook #3 carries feedback information corresponding to the data scheduled by traditional DCI. HARQ-ACK codebook #3 is a type-1 HARQ-ACK codebook. HARQ-ACK codebook #4 carries feedback information corresponding to the data scheduled by multi-cell DCI. HARQ-ACK codebook #4 is a type-2 HARQ-ACK codebook. Figure 7 illustrates an example in which HARQ-ACK codebook #4 includes the second sub-codebook but does not include the first sub-codebook.

[0156] In one possible implementation, in the implementation shown in FIG3 , the base station may configure some parameters for the terminal, such as at least one of the codebook type, priority, or channel information of the first HARQ-ACK codebook and / or the second HARQ-ACK codebook. Several possible parameters configured by the base station are introduced below using parameters A, B, and C.

[0157] Parameter A: codebook type of the first HARQ-ACK codebook and / or the second HARQ-ACK codebook.

[0158] In the embodiment of the present application, the base station may configure the codebook type of the first HARQ-ACK codebook and / or the second HARQ-ACK codebook for the terminal. The base station may configure the codebook type of the first HARQ-ACK codebook and / or the second HARQ-ACK codebook through at least one signaling.

[0159] Parameter B: priority of the HARQ-ACK feedback information corresponding to the first DCI scheduled data and / or the HARQ-ACK feedback information corresponding to the second DCI scheduled data.

[0160] In one possible implementation, the DCI (the first DCI or the second DCI mentioned above) includes a resource indication field of an uplink channel (such as PUCCH or PUSCH), and the resource indication field of the uplink channel can indicate the resources of the uplink channel used to feedback the HARQ-ACK code block.

[0161] In another possible implementation, the DCI may include a priority indicator field, and the information in the priority indicator field (such as a priority index) may indicate a priority (for example, a priority index of 0 may be understood as a low priority, and a priority index of 1 may be understood as a high priority).

[0162] The priority indication field in the DCI may not directly indicate the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the DCI, and the information carried in the priority indication field may be understood as indicating the priority of the uplink channel indicated by the resource indication field of the uplink channel in the DCI. Since the HARQ-ACK feedback information corresponding to the data scheduled by the DCI needs to be fed back on the uplink channel, it can be understood that: the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the DCI is the same as the priority of the uplink channel indicated by the resource indication field of the uplink channel in the DCI, and it can also be understood that: the information carried by the priority indication field in the DCI indirectly indicates the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the DCI.

[0163] For example, the priority indicated by the information carried by the priority indication field in the first DCI can be understood as the priority of the uplink channel (such as the first uplink channel) indicated by the resource indication field of the uplink channel in the first DCI; it can also be understood as the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the first DCI. In this embodiment of the present application, the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the first DCI can also be referred to as the priority of the uplink channel resources indicated by the first DCI.

[0164] Similarly, the priority indicated by the information carried by the priority indication field in the second DCI can be understood as the priority of the uplink channel (such as the first uplink channel) indicated by the resource indication field of the uplink channel in the second DCI; it can also be understood as the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the second DCI. In this embodiment of the present application, the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the second DCI can also be referred to as the priority of the resources of the uplink channel indicated by the second DCI.

[0165] In another possible implementation, the DCI may not include a priority indication field. In this case, the priority information indicated by the DCI can be considered to be a default priority, and the default priority can be a preset priority, such as a low priority. For example, if the first DCI does not include a priority indication field, the priority indicated by the first DCI can be considered to be the default priority (such as a low priority). It can also be understood that: the priority of the uplink channel indicated by the resource indication field of the uplink channel in the first DCI is the default priority (such as a low priority), and the priority of the HARQ-ACK feedback information corresponding to the data scheduled by the first DCI is the default priority (such as a low priority). If the second DCI does not include a priority indication field, the solution is similar to it and will not be repeated.

[0166] In one possible implementation, the HARQ-ACK feedback information corresponding to the first DCI scheduled data is the same as the HARQ-ACK feedback information corresponding to the second DCI scheduled data. In one possible implementation, the terminal may process the HARQ-ACK feedback information corresponding to the at least one first DCI scheduled data (for example, including at least one of CRC addition, CB segmentation, CB CRC addition, channel coding, or rate matching) to obtain a first HARQ-ACK codebook; the terminal processes the HARQ-ACK feedback information corresponding to the at least one second DCI scheduled data to obtain a second HARQ-ACK codebook, and then transmits the first HARQ-ACK codebook and the second HARQ-ACK codebook on the first uplink channel. In this way, the terminal can feedback the first HARQ-ACK codebook and the second HARQ-ACK codebook on the same uplink channel, so that the transmission reliability of the feedback information corresponding to services with the same priority is the same.

[0167] In the present application, the HARQ-ACK codebook can also be understood as HARQ-ACK information (information). In this way, the terminal can feedback HARQ-ACK feedback information corresponding to at least one first DCI-scheduled data and HARQ-ACK feedback information corresponding to at least one second DCI-scheduled data in the same uplink channel. The priorities of the HARQ-ACK feedback information corresponding to the at least one first DCI-scheduled data and the HARQ-ACK feedback information corresponding to the at least one second DCI-scheduled data can be the same. In a possible example, the terminal device can process the HARQ-ACK feedback information corresponding to the at least one first DCI-scheduled data and the HARQ-ACK feedback information corresponding to the at least one second DCI-scheduled data (for example, it may include at least one of CRC addition, CB segmentation, CB CRC addition, channel coding or rate matching) to obtain a HARQ-ACK codebook, and then send the HARQ-ACK codebook on the first uplink channel.

[0168] Parameter C: channel information of the first HARQ-ACK codebook and / or the second HARQ-ACK codebook.

[0169] In one possible implementation, when the resources (such as time domain resources) of the uplink channel where the HARQ-ACK feedback information corresponding to the data scheduled by multiple DCIs (including the above-mentioned at least one first DCI and / or at least one second DCI) are located are the same (or the time slots where the uplink channels are located are the same), the HARQ-ACK feedback information of the data scheduled by the multiple DCIs can be transmitted through the same uplink channel.

[0170] For the DCI in the first DCI and the second DCI, the information carried by the PDSCH-HARQ feedback timing indicator field (PDSCH-to-HARQ_feedback timing indicator) in the DCI can be used to indicate the offset between the resources of the uplink channel (e.g., time domain resources (e.g., time slot)) where the HARQ-ACK feedback information corresponding to the scheduled data (e.g., PDSCH) in the DCI is located and the uplink channel (e.g., time domain resources (e.g., time slot)) where the scheduled data (e.g., PDSCH) in the DCI is located.

[0171] For multiple DCIs in the first DCI and the second DCI, the resources of the uplink channels where the HARQ-ACK feedback information corresponding to the multiple DCI-scheduled data indicated by the multiple DCIs are located are the same (or the same time slots), which can be: determined jointly according to the PDSCH-related indication information in the multiple DCIs (for example, K0, that is, the offset of the time domain resources between the DCI and the PDSCH scheduled by the DCI (such as the time slot offset) and the information carried by the PDSCH-HARQ feedback timing indication field.

[0172] For example, the resources (such as time domain resources) of the uplink channel where the HARQ-ACK feedback information corresponding to the multiple first DCI scheduled data is located are the same (or the time slot where the uplink channel is located is the same), so the terminal can carry the feedback information of the multiple first DCI scheduled data in the same first HARQ-ACK codebook.

[0173] For another example, the resources (such as time domain resources) of the uplink channel where the HARQ-ACK feedback information corresponding to the multiple second DCI scheduled data is located are the same (or the time slot where the uplink channel is located is the same), so the terminal can carry the feedback information of the multiple second DCI scheduled data in the same second HARQ-ACK codebook or the same second HARQ-ACK subcodebook.

[0174] For another example, the resources (such as time domain resources) of the uplink channel where the HARQ-ACK feedback information corresponding to at least one first DCI-scheduled data and at least one second DCI-scheduled data are located are the same (or the time slot where the uplink channel is located is the same). Therefore, the terminal can transmit the feedback information corresponding to the at least one first DCI-scheduled data (carried in the first HARQ-ACK codebook) and the feedback information corresponding to the at least one second DCI-scheduled data (carried in the second HARQ-ACK codebook) through one uplink channel. In this way, the number and resources of the uplink channels occupied by the feedback information can be saved, and the resource overhead of the uplink channel can be saved.

[0175] In one possible implementation, the resources (such as time domain resources) of the uplink channel where the HARQ-ACK feedback information corresponding to the data scheduled by at least one first DCI and at least one second DCI are located are the same, which can be regarded as a preconfigured rule. For example, when the base station determines that the feedback information corresponding to the at least one first DCI and the at least one second DCI scheduled data needs to be fed back through an uplink channel (such as a first uplink channel), the base station can, according to the preconfigured rule, make the resources (such as time domain resources) of the uplink channel where the HARQ-ACK feedback information corresponding to the at least one first DCI and the at least one second DCI scheduled data the same, so that the terminal subsequently carries the codebook of the feedback information corresponding to the at least one first DCI scheduled data (i.e., the first HARQ-ACK codebook) and the codebook of the feedback information corresponding to the at least one second DCI scheduled data (i.e., the second HARQ-ACK codebook) on the same uplink channel.

[0176] The base station can configure the channel information (such as PUCCH or PUSCH information) where the first HARQ-ACK codebook and / or the second HARQ-ACK codebook are located through parameters (such as parameters in the RRC message) (and / or through the resource indication field of the uplink channel (such as PUCCH or PUSCH) in the DCI). The channel information includes resource information of the channel (such as time domain resources and / or frequency domain resources, etc.). The channel information indicates the first channel, so that the terminal transmits the first HARQ-ACK codebook and the second HARQ-ACK codebook through the first channel, thereby achieving the effect of saving channel resources.

[0177] In one possible implementation, the resources (such as time domain resources) of the uplink channel where the HARQ-ACK feedback information corresponding to at least one first DCI-scheduled data and at least one second DCI-scheduled data are located are the same, which can be regarded as a preconfigured rule. For example, when the base station determines that the feedback information corresponding to the at least one first DCI and the at least one second DCI-scheduled data needs to be fed back through an uplink channel (such as a first uplink channel), the base station can configure the resources (such as time domain resources) of the uplink channel where the HARQ-ACK feedback information corresponding to the at least one first DCI and the at least one second DCI-scheduled data are located to be the same according to the preconfigured rule, so that the terminal subsequently carries the codebook of the feedback information corresponding to the at least one first DCI-scheduled data (i.e., the first HARQ-ACK codebook) and the codebook of the feedback information corresponding to the at least one second DCI-scheduled data (i.e., the second HARQ-ACK codebook) on the same uplink channel.

[0178] In another possible implementation, the base station determines that the feedback information corresponding to the data scheduled by at least one first DCI and at least one second DCI needs to be multiplexed into one uplink channel (for example, the resources (for example, time domain resources) of the uplink channel where the HARQ-ACK feedback information corresponding to the data scheduled by at least one first DCI and at least one second DCI are located are the same). The base station may configure the codebook type of the first HARQ-ACK codebook and the second HARQ-ACK codebook to be the same. In this way, the codebook type of the two HARQ-ACK codebooks transmitted by the terminal through the first uplink channel is the same, thereby avoiding the problem of high decoding complexity and excessive load of the HARQ-ACK codebook caused by multiplexing different codebook types on one uplink channel.

[0179] In another possible implementation, the base station may configure the codebook types of the HARQ-ACK feedback information of the DCI scheduled data in the multiple formats to be the same when at least one of the following first conditions is met.

[0180] The first condition includes:

[0181] The terminal does not have the first capability;

[0182] The terminal does not report the first capability (or the terminal does not send the first information); for example, the base station does not enable the first capability (or the base station does not send the second information);

[0183] The base station disables the first capability;

[0184] The standard does not support multiplexing of HARQ-ACK codebooks of different codebook types into the same uplink channel.

[0185] In another possible implementation, when the base station does not meet the conditions in the first condition, the base station can be flexibly set as needed, for example, the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook can be configured to be different (the implementation of Figure 3 can be used).

[0186] In another possible implementation, the base station configures the codebook type of the HARQ-ACK feedback information of the DCI scheduled data in multiple formats to be the same, which can be understood as a constraint on the base station configuration behavior or scheduling behavior, which can be referred to as predefined condition #1. The predefined condition #1 can also be understood as: the terminal expects (expects) that the codebook type of the HARQ-ACK feedback information of the DCI scheduled data in multiple formats (or all formats) is configured to be the same, and the base station configures the codebook type of the HARQ-ACK feedback information of the DCI scheduled data in the multiple formats to be the same according to the predefined condition #1.

[0187] In another possible implementation, the base station may perform configuration based on other predefined conditions. For example, predefined condition #2 may include: the terminal does not expect (does not expect) that the codebook type of the HARQ-ACK feedback information of the DCI scheduled data of multiple formats (or all formats) is configured to be different. In this case, the base station may configure the codebook type of the HARQ-ACK feedback information of the DCI scheduled data of the multiple formats to be different according to the predefined condition #2.

[0188] Figure 8 exemplarily shows a structural diagram of another HARQ-ACK codebook fed back by the terminal. As shown in Figure 8, the base station sends traditional DCI, multi-cell scheduling DCI#1 and multi-cell scheduling DCI#2. Among them, multi-cell scheduling DCI#2 is used to schedule PDSCH#1, multi-cell scheduling DCI#1 is used to schedule PDSCH#2, PDSCH#3 and PDSCH#4, and traditional DCI is used to schedule PDSCH#5. The codebook type of the feedback information corresponding to the data scheduled by traditional DCI, multi-cell scheduling DCI#1 and multi-cell scheduling DCI#2 is all type-2 HARQ-ACK codebook type. As shown in Figure 8, the terminal feeds back the first HARQ-ACK codebook and the second HARQ-ACK codebook through PUCCH. The first HARQ-ACK codebook includes feedback information corresponding to PDSCH#5 scheduled by traditional DCI. The second HARQ-ACK codebook can be attached to the first HARQ-ACK codebook. The feedback information corresponding to PDSCH#5 and PDSCH#1 is feedback information corresponding to DCI-scheduled data for scheduling one cell, and can also be regarded as the first subcodebook. The feedback information corresponding to PDSCH#2, PDSCH#3, and PDSCH#4 is feedback information corresponding to DCI-scheduled data for scheduling multiple cells, and can also be regarded as the second subcodebook.

[0189] Continuing with Figure 8, in the first subcodebook, the feedback information corresponding to PDSCH#1 is appended after the feedback information corresponding to PDSCH#5. Conversely, the feedback information corresponding to PDSCH#5 can also be appended after the feedback information corresponding to PDSCH#1. The corresponding feedback information can be arranged in the order of the feedback information corresponding to the traditional DCI-scheduled PDSCH first, and the feedback information corresponding to the multi-cell DCI-scheduled PDSCH after the feedback information corresponding to the traditional DCI-scheduled PDSCH. Alternatively, the feedback information can be arranged in ascending order based on the cell index of the scheduled PDSCH, without distinguishing between traditional DCI and multi-cell DCI.

[0190] In another possible implementation, when the base station determines that the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook are different (for example, the codebook type of the HARQ-ACK codebook corresponding to the at least one first DCI scheduled data is configured as semi-static, and the codebook type of the HARQ-ACK codebook corresponding to the at least one second DCI scheduled data is configured as dynamic; for example, the codebook type of the HARQ-ACK codebook corresponding to the at least one first DCI scheduled data is configured as dynamic, and the codebook type of the HARQ-ACK codebook corresponding to the at least one second DCI scheduled data is configured as semi-static), the base station may configure the first HARQ-ACK codebook and the second HARQ-ACK codebook for time division multiplexing. In this way, the terminal can respectively feedback the first HARQ-ACK codebook and the second HARQ-ACK codebook in a time division multiplexing manner. For example, the first HARQ-ACK codebook can be fed back through the second uplink channel and the second HARQ-ACK codebook can be fed back through the third uplink channel. The time domain resources of the second uplink channel and the third uplink channel are different, and the time domain resources may also include time slots, sub-time slots, time domain symbols, frames, or subframes. In an embodiment of the present application, the time domain symbols may be orthogonal frequency division multiplexing (OFDM) symbols or discrete Fourier transform spread OFDM (DFT-s-OFDM) symbols.

[0191] In another possible implementation, when the base station determines that the codebook type of the first HARQ-ACK codebook and the second HARQ-ACK codebook is the same (for example, the resources (for example, time domain resources) of the uplink channel where the HARQ-ACK feedback information corresponding to the at least one first DCI and the at least one second DCI scheduled data is located are the same), the base station may configure the first HARQ-ACK codebook and the second HARQ-ACK codebook to be fed back through one uplink channel. For example, the terminal may feed back the first HARQ-ACK codebook and the second HARQ-ACK codebook through the first uplink channel.

[0192] It can be seen from the above example that in this embodiment, the codebook type of the HARQ-ACK codebook fed back by the terminal through an uplink channel is the same, thereby avoiding the problem of HARQ-ACK codebooks of different codebook types being multiplexed into one uplink channel, thereby reducing the complexity of implementation.

[0193] In another possible implementation, when at least one of the first conditions is met and the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook need to be configured as different, the base station may configure the first HARQ-ACK codebook and the second HARQ-ACK codebook as time division multiplexing. For the relevant content of the first condition, refer to the above description and will not be repeated here.

[0194] In another possible implementation, when the base station does not meet the conditions in the first condition, and the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook need to be configured as different, the base station may configure the first HARQ-ACK codebook and the second HARQ-ACK codebook to be transmitted through one uplink channel (the implementation shown in FIG. 3 may be used).

[0195] In another possible implementation, the base station configures the first HARQ-ACK codebook and the second HARQ-ACK codebook as time division multiplexing, which can be understood as a constraint on the base station configuration behavior or scheduling behavior, which can be referred to as predefined condition #3. Predefined condition #3 can also be understood as: when the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook are configured to be different, the terminal expects (expects) to send the uplink channel of the first HARQ-ACK codebook and the uplink channel of the second HARQ-ACK codebook on different time slots or sub-time slots. According to the predefined condition #3, when the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook are configured to be different, the base station sends the uplink channel of the first HARQ-ACK codebook and the uplink channel of the second HARQ-ACK codebook on different time slots or sub-time slots.

[0196] In another possible implementation, the base station may perform configuration according to other predefined conditions. For example, predefined condition #4 may include: when the codebook types of the first HARQ-ACK codebook and the second HARQ-ACK codebook are configured to be different, the terminal does not expect (does not expect) that the uplink channel for sending the first HARQ-ACK codebook and the uplink channel for sending the second HARQ-ACK codebook are on the same time slot or sub-time slot. In this case, according to the predefined condition #4, the base station does not need to configure the first HARQ-ACK codebook and the second HARQ-ACK codebook with different codebook types as time division multiplexing.

[0197] Figure 9 exemplifies a structural diagram of another HARQ-ACK codebook for terminal feedback. As shown in Figure 9, the base station sends traditional DCI, multi-cell scheduling DCI#3, and multi-cell scheduling DCI#4. Among them, multi-cell scheduling DCI#4 is used to schedule PDSCH#6, multi-cell scheduling DCI#3 is used to schedule PDSCH#7, PDSCH#8, and PDSCH#9, and traditional DCI is used to schedule PDSCH#10. The codebook type of the feedback information corresponding to the data scheduled by multi-cell scheduling DCI#3 and multi-cell scheduling DCI#4 is both type-2 HARQ-ACK codebook type. The codebook type of the feedback information corresponding to the data scheduled by traditional DCI is type-1 HARQ-ACK codebook type.

[0198] As shown in Figure 9, the terminal feeds back the first HARQ-ACK codebook and the second HARQ-ACK codebook through two PUCCHs respectively. The terminal feeds back the second HARQ-ACK codebook through PUCCH #1. The second HARQ-ACK codebook includes feedback information corresponding to PDSCH #6, PDSCH #7, PDSCH #8, and PDSCH #9. The second HARQ-ACK codebook includes a first sub-codebook and a second sub-codebook. The first sub-codebook includes a codebook of feedback information corresponding to PDSCH #1, and the second sub-codebook includes a codebook of feedback information corresponding to PDSCH #2, PDSCH #3, and PDSCH #4.

[0199] As shown in Figure 9, the terminal feeds back the first HARQ-ACK codebook via PUCCH#2. The first HARQ-ACK codebook includes feedback information corresponding to the legacy DCI-scheduled PDSCH#5.

[0200] FIG9 is an example of introducing the codebook type of the feedback information corresponding to the multi-cell DCI scheduled data as the type-2 HARQ-ACK codebook type, and the codebook type of the feedback information corresponding to the traditional DCI scheduled data as the type-1 HARQ-ACK codebook type. In actual applications, the codebook type of the feedback information corresponding to the multi-cell DCI scheduled data can be the type-1 HARQ-ACK codebook type, and the codebook type of the feedback information corresponding to the traditional DCI scheduled data can be the type-2 HARQ-ACK codebook type. The relevant content is similar and will not be repeated here.

[0201] It is understood that, in order to implement the functions in the above embodiments, the base station and the terminal include hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily appreciate that, in conjunction with the units and method steps of the various examples described in the embodiments disclosed in this application, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application scenario and design constraints of the technical solution.

[0202] Based on the same concept, Figures 10 and 11 are schematic diagrams of the structures of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of the terminal or base station in the above-mentioned method embodiments, thereby also achieving the beneficial effects of the above-mentioned method embodiments. In the embodiments of the present application, the communication device can be the terminal 120 shown in Figure 2, or the RAN node 110 shown in Figure 2, or a module (such as a chip) applied to the terminal 120 or the RAN node 110.

[0203] As shown in Figure 10, the communication device 1300 includes a processing unit 1310 and a transceiver unit 1320. The communication device 1300 is used to implement the functions of the terminal or base station in the method embodiment shown in Figure 3 above.

[0204] When the communication device 1300 is used to implement the function of the terminal in the method embodiment shown in Figure 3: the processing unit 1310 is used to receive at least one first DCI through the transceiver unit 1320; receive at least one second DCI; and send a first HARQ-ACK codebook and a second HARQ-ACK codebook on the first uplink channel.

[0205] In a possible implementation, when the communication device 1300 is used to implement the function of the terminal in the method embodiment shown in FIG. 3 , the processing unit 1310 is further used to send the first information through the transceiver unit 1320 .

[0206] In a possible implementation, when the communication device 1300 is used to implement the function of the terminal in the method embodiment shown in FIG. 3 , the processing unit 1310 is further used to receive the second information through the transceiver unit 1320 .

[0207] When the communication device 1300 is used to implement the function of the base station in the method embodiment shown in Figure 3: the processing unit 1310 is used to send at least one first DCI through the transceiver unit 1320; send at least one second DCI; and receive a first HARQ-ACK codebook and a second HARQ-ACK codebook on the first uplink channel.

[0208] In a possible implementation, when the communication device 1300 is used to implement the function of the base station in the method embodiment shown in Figure 3: the processing unit 1310 is further used to receive first information through the transceiver unit 1320, where the first information indicates that the terminal supports multiplexing HARQ-ACK codebooks of different codebook types into the same uplink channel.

[0209] In a possible implementation, when the communication device 1300 is used to implement the function of the base station in the method embodiment shown in Figure 3: the processing unit 1310 is further used to send second information through the transceiver unit 1320, and the second information enables the terminal to support the ability to multiplex HARQ-ACK codebooks of different codebook types into the same uplink channel.

[0210] For a more detailed description of the processing unit 1310 and the transceiver unit 1320 , reference may be made to the relevant description in the method embodiment shown in FIG. 3 .

[0211] As shown in Figure 11, communication device 1400 includes a processor 1410 and an interface circuit 1420. Processor 1410 and interface circuit 1420 are coupled to each other. It is understood that interface circuit 1420 can be a transceiver or an input / output interface. Optionally, communication device 1400 may also include a memory 1430 for storing instructions executed by processor 1410, input data required by processor 1410 to execute instructions, or data generated after processor 1410 executes instructions.

[0212] When the communication device 1400 is used to implement the method shown in FIG. 3 , the processor 1410 is used to implement the functions of the processing unit 1310 , and the interface circuit 1420 is used to implement the functions of the transceiver unit 1320 .

[0213] When the above-mentioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal device in the above-mentioned method embodiment. When the terminal chip receives information from the base station, it can be understood that the information is first received by other modules in the terminal (such as a radio frequency module or antenna) and then sent to the terminal chip by these modules. When the terminal chip sends information to the base station, it can be understood that the information is first sent to other modules in the terminal (such as a radio frequency module or antenna) and then sent to the base station by these modules.

[0214] When the above-mentioned communication device is a chip applied to a base station, the base station chip implements the functions of the network device in the above-mentioned method embodiment. When the base station chip receives information from the terminal, it can be understood that the information is first received by other modules in the base station (such as a radio frequency module or antenna) and then sent to the base station chip by these modules. When the base station chip sends information to the terminal, it can be understood that the information is sent to other modules in the base station (such as a radio frequency module or antenna) and then sent to the terminal by these modules.

[0215] In this application, when entity A sends information to entity B, it can be done directly from A or indirectly through another entity. Similarly, when entity B receives information from entity A, it can be done directly from entity A or indirectly through another entity. Entities A and B herein can be RAN nodes or terminals, or modules within a RAN node or terminal. The sending and receiving of information can be information exchange between a RAN node and a terminal, for example, between a base station and a terminal; between two RAN nodes, for example, between a CU and a DU; or between different modules within a device, for example, between a terminal chip and other modules in the terminal, or between a base station chip and other modules within the base station.

[0216] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0217] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules 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 disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. The processor and storage medium can also exist in a base station or a terminal as discrete components.

[0218] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. A computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, all or part of the processes or functions of the embodiments of the present application are performed. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may 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 may 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 may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media, such as floppy disks, hard disks, or magnetic tapes; optical media, such as digital video disks; or semiconductor media, such as solid-state drives. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0219] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0220] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next associated objects are in an "or" relationship; in the formula of this application, the character " / " indicates that the previous and next associated objects are in a "division" relationship. "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. "Including at least one of A, B or 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.

[0221] It is understood that the various numbers involved in the embodiments of this application (such as the numerical numbers "first" and "second", and the letter numbers "parameter A", "parameter B", "parameter C", etc.) are only for the convenience of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic.

Claims

1. A method for sending a hybrid automatic repeat request response HARQ-ACK codebook, the method being performed by a communication device, characterized in that: The method comprises: receiving at least one first downlink control information DCI, where the format of the first DCI is a DCI format used for scheduling data of a cell, and the first DCI is a unicast DCI; receiving at least one second DCI, wherein the format of the second DCI is a DCI format supporting scheduling of data of one or more cells; A first HARQ-ACK codebook and a second HARQ-ACK codebook are sent on a first uplink channel, where the first HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to the at least one first DCI scheduled data, and the second HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to the at least one second DCI scheduled data, and the codebook type of the first HARQ-ACK codebook is different from the codebook type of the second HARQ-ACK codebook.

2. The method according to claim 1, characterized in that In the case where the codebook type of the second HARQ-ACK codebook is a dynamic codebook type: Each second DCI in the at least one second DCI schedules data of one cell; or, Each second DCI in the at least one second DCI schedules data of multiple cells.

3. The method according to claim 1, characterized in that In a case where the codebook type of the second HARQ-ACK codebook is a dynamic codebook type: the second HARQ-ACK codebook includes a first subcodebook or a second subcodebook; Wherein, each second DCI corresponding to the feedback information included in the first subcodebook schedules data of one cell; Each second DCI corresponding to the feedback information included in the second subcodebook schedules data of multiple cells.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Sending first information, where the first information indicates that the communication device supports multiplexing HARQ-ACK codebooks of different codebook types onto the same uplink channel.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Second information is received, where the second information enables the communication device to multiplex HARQ-ACK codebooks of different codebook types onto the same uplink channel.

6. The method according to any one of claims 1 to 5, characterized in that: The second HARQ-ACK codebook is attached to the first HARQ-ACK codebook.

7. A method for receiving a hybrid automatic repeat request response HARQ-ACK codebook, the method being performed by a communication device, characterized in that: The method comprises: Send at least one first downlink control information DCI, where the format of the first DCI is a DCI format used for scheduling data of a cell, and the first DCI is a unicast DCI; Send at least one second DCI, where the format of the second DCI is a DCI format that supports scheduling data of one or more cells; A first HARQ-ACK codebook and a second HARQ-ACK codebook are received on a first uplink channel, where the first HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to the at least one first DCI scheduled data, and the second HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to the at least one second DCI scheduled data, and the codebook type of the first HARQ-ACK codebook is different from the codebook type of the second HARQ-ACK codebook.

8. The method according to claim 7, characterized in that In the case where the codebook type of the second HARQ-ACK codebook is a dynamic codebook type: Each second DCI in the at least one second DCI schedules data of one cell; or, Each second DCI in the at least one second DCI schedules data of multiple cells.

9. The method according to claim 7, characterized in that In a case where the codebook type of the second HARQ-ACK codebook is a dynamic codebook type: the second HARQ-ACK codebook includes a first subcodebook or a second subcodebook; Wherein, each second DCI corresponding to the feedback information included in the first subcodebook schedules data of one cell; Each second DCI corresponding to the feedback information included in the second subcodebook schedules data of multiple cells.

10. The method according to any one of claims 7 to 9, characterized in that: The method further comprises: First information is received, where the first information indicates that the terminal supports multiplexing HARQ-ACK codebooks of different codebook types onto the same uplink channel.

11. The method according to any one of claims 7 to 10, characterized in that: The method further comprises: Sending second information, where the second information enables the terminal to multiplex HARQ-ACK codebooks of different codebook types onto the same uplink channel.

12. The method according to any one of claims 7 to 11, characterized in that: The second HARQ-ACK codebook is attached to the first HARQ-ACK codebook.

13. A communication device, characterized in that: The method comprises a module for executing the method as claimed in any one of claims 1 to 6, or comprises a module for executing the method as claimed in any one of claims 7 to 12.

14. A communication device, characterized in that: The method comprises a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1 to 6 or the method as described in any one of claims 7 to 12 through a logic circuit or executing code instructions.

15. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or an instruction. When the computer program or the instruction is executed by the communication device, the method according to any one of claims 1 to 6 or the method according to any one of claims 7 to 12 is implemented.

16. A computer program product, characterized in that The computer program product stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the method according to any one of claims 1 to 6 or the method according to any one of claims 7 to 12.

Citation Information

Patent Citations

  • Uplink control information transmission method, uplink control information receiving method, terminal and network equipment

    CN114599093A

  • HARQ-ACK codebook feedback method, terminal device and network device

    CN115336215A

  • Hybrid automatic repeat request feedback with multi-cell downlink control information

    WO2022086888A1