Codebook feedback method, device, equipment and computer storage medium

Abstract

The present application discloses a method, apparatus, device, and computer storage medium for codebook feedback. The method includes: a terminal determining a target codebook for feedback based on one or more type-3 codebooks, or based on one or more type-3 codebooks and other HARQ-ACK codebooks that require feedback, wherein the one or more type-3 codebooks are triggered by the network side to require feedback by the terminal within a single time unit, or the one or more type-3 codebooks and other HARQ-ACK codebooks are triggered by the network side to require feedback by the terminal within a single time unit.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a codebook feedback method, apparatus, device, and computer storage medium. Background Art

[0002] When multiple enhanced Type-3 codebooks with different contents / ranges are triggered in a single slot / sub-slot, or when an enhanced Type-3 codebook is triggered in a single slot or sub-slot, and other hybrid automatic repeat request acknowledgement (HARQ-ACK) codebooks need to be fed back (the corresponding HARQ-ACK information may not be included in the triggered enhanced Type-3 codebook), how does the terminal (e.g., user equipment (UE)) feedback HARQ-ACK? There is currently no corresponding solution. Summary of the Invention

[0003] The embodiments of the present application provide a method, apparatus, device, and computer storage medium for codebook feedback, which can solve the problem of how a terminal determines a codebook that requires feedback.

[0004] According to a first aspect, a method for providing feedback of a codebook is provided, including:

[0005] The terminal determines a target codebook for feedback based on one or more type 3 codebooks, or based on one or more type 3 codebooks and other hybrid automatic repeat request response HARQ-ACK codebooks that require feedback;

[0006] The one or more type 3 codebooks are triggered by the network side to require feedback from the terminal within a single time unit, or the one or more type 3 codebooks and other HARQ-ACK codebooks are triggered by the network side to require feedback from the terminal within a single time unit.

[0007] In a second aspect, a method for providing feedback of a codebook is provided, including:

[0008] The network side device triggers the terminal to feedback one or more type 3 codebooks in a single time unit, or the network side device triggers the terminal to feedback one or more type 3 codebooks and other HARQ-ACK codebooks in a single time unit;

[0009] The network side device obtains a target codebook fed back by the terminal, wherein the target codebook is determined by the terminal according to one or more type 3 codebooks, or according to one or more type 3 codebooks and other HARQ-ACK codebooks.

[0010] According to a third aspect, a device for providing feedback of a codebook is provided, including:

[0011] A first determination module is configured to determine a target codebook for feedback based on one or more type 3 codebooks, or based on one or more type 3 codebooks and other HARQ-ACK codebooks that require feedback;

[0012] The one or more type 3 codebooks are triggered by the network side to require feedback from the terminal within a single time unit, or the one or more type 3 codebooks and the other HARQ-ACK codebooks are triggered by the network side to require feedback from the terminal within a single time unit.

[0013] In a fourth aspect, a device for feeding back a codebook is provided, including:

[0014] A triggering module, configured to trigger the terminal to feedback one or more type 3 codebooks in a single time unit, or to trigger the terminal to feedback one or more type 3 codebooks and other HARQ-ACK codebooks in a single time unit;

[0015] An acquisition module, configured to acquire a target codebook fed back by the terminal, wherein the target codebook is determined by the terminal according to one or more type 3 codebooks, or according to one or more type 3 codebooks and the other HARQ-ACK codebooks.

[0016] In a fifth aspect, a terminal is provided, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the first aspect.

[0017] In a sixth aspect, a network side device is provided, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the second aspect.

[0018] In a seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0019] In an eighth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a non-volatile storage medium, and the computer program / program product is executed by at least one processor to implement the steps of the processing method as described in the first aspect or the second aspect.

[0020] In the ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the processing method described in the first aspect or the second aspect.

[0021] In this embodiment of the present application, when the network side triggers one or more type 3 codebooks in a single time unit, or when the network side triggers one or more type 3 codebooks in a single time unit and needs to feedback other HARQ-ACK codebooks, the terminal can determine and feedback the target codebook according to one or more type 3 codebooks, or according to one or more type 3 codebooks and other HARQ-ACK codebooks that need to be fed back, thereby ensuring HARQ-ACK feedback performance and improving the reliability of the communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 is a schematic diagram of a wireless communication system to which embodiments of the present application may be applied;

[0023] Figure 2 This is one of the flow charts of the codebook feedback method provided in an embodiment of the present application;

[0024] Figure 3 This is the second flowchart of the codebook feedback method provided in an embodiment of the present application;

[0025] Figure 4 This is a schematic diagram of an embodiment of the present application providing that the network side triggers the terminal to feedback multiple type 3 codebooks within a single time unit;

[0026] Figure 5 This is a schematic diagram of an embodiment of the present application providing that the network side triggers the terminal to simultaneously feedback type 3 and other HARQ-ACK codebooks within a single time unit;

[0027] Figure 6 This is one of the schematic diagrams of the device for codebook feedback provided in an embodiment of the present application;

[0028] Figure 7 This is the second flow chart of the codebook feedback device provided in an embodiment of the present application;

[0029] Figure 8 is a schematic diagram of a terminal provided in an embodiment of the present application;

[0030] Figure 9is a schematic diagram of a network-side device provided in an embodiment of the present application;

[0031] Figure 10 It is a schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The following will be combined with the accompanying drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the embodiments described are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0033] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specified order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein, and that the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects; for example, the first object can be one or more. In addition, the character "and" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects connected are in an "or" relationship.

[0034] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to applications other than NR system applications, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0035] To facilitate understanding of the embodiments of the present application, the following technical points are first introduced below:

[0036] 1. Release 16 (Rel-16) Type-3 codebook:

[0037] In the New Radio-Unlicensed (NR-U) Rel-16 protocol, a Type-3 codebook is introduced to ensure that both the UE and the network have a consistent understanding of the number of HARQ-ACK codebook bits and to feedback HARQ-ACK information for all configured HARQ processes. This codebook feedbacks HARQ-ACK information for each configured codeword for all configured HARQ processes on all carriers currently configured for the UE. To ensure that both the UE and the evolved Node B (eNB) have a consistent understanding of the Physical Downlink Shared Channel (PDSCH) transmission corresponding to the feedback HARQ-ACK bits and to avoid ambiguity caused by missed detection of the Physical Downlink Control Information (DCI), the Type-3 codebook can further include a New Data Indicator (NDI) for each codeword (if a codeword for a HARQ process has never been scheduled, its corresponding NDI is assumed to be 0). Whether this codebook is included is configurable by the network through higher-layer parameters.

[0038] 2. Release 17 (Rel-17) HARQ-ACK Retransmission

[0039] In the Ultra-reliable and Low Latency Communications (URLLC) Rel-17 research, to ensure the performance of HARQ-ACK feedback, the retransmission of canceled HARQ-ACK was proposed and its corresponding solution was studied. The HARQ-ACKs that need to be retransmitted in this problem include:

[0040] (1) Based on the two physical layer priorities configured for a single UE (Intra-UE prioritization), HARQ-ACK carried in the lower physical layer priority uplink transmission (PUCCH / PUSCH) is deleted by the higher physical layer priority uplink transmission (Physical Uplink Control Channel (PUCCH) / Physical Uplink Shared Channel (PUSCH)).

[0041] (2) HARQ-ACK carried in uplink transmissions (e.g., PUSCH) that are cancelled by an uplink cancellation indication (UCI) based on inter-UE priority processing (Inter-UE cancellation).

[0042] (3) Semi-Persistent Scheduling (SPS) HARQ-ACK discarded due to conflict with the Time Division Duplexing (TDD) pattern (Semi-static downlink symbol (DL symbol) / Synchronization Signal and PBCH block (SSB) / control-resource set #0 (CORESET#0)) (can also be recovered through the SPS HARQ-ACK deferral mechanism).

[0043] After lengthy discussions at the RAN1#105-e meeting, vendors reached a compromise, resulting in the following Working Assumption, which supports HARQ-ACK retransmission based on an optimized Type-3 codebook and one-shot triggering.

[0044] Regarding Type-3 codebook optimization, the current focus is on triggering HARQ-ACK feedback only for certain HARQ processes (rather than for all configured HARQ processes on all carriers, as required by the Rel-16 Type-3 codebook). This reduces the codebook size and avoids the overhead of unnecessary HARQ-ACK feedback. For example, the network configures a state list, where each state corresponds to / indicates a different / unique HARQ process range (which may further indicate a serving cell range) and also corresponds to a Type-3 codebook (when the HARQ process range differs from the Rel-16 Type-3 codebook, it is called an enhanced Type-3 codebook). This Type-3 codebook contains the HARQ-ACKs for each HARQ process in the set of HARQ processes indicated by the corresponding state. Its codebook construction can follow all / part of the rules of the Rel-16 Type-3 codebook (for example, organizing the codebook based on HARQ process). The network triggers the corresponding Type-3 codebook by indicating the state index corresponding to a state in the state list in the triggering DCI. In addition, the indication field in the triggering DCI may also explicitly indicate the HARQ-ACK set / range corresponding to the triggered Type-3 codebook.

[0045] See also Figure 1 , the figure shows a block diagram of a wireless communication system that can be applied in an embodiment of the present application. The wireless communication system includes a terminal 11, a terminal 12 and a network side device 13. Among them, the terminal can also be called a terminal device or UE, and the terminal can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal-side devices, and wearable devices include: smart watches, bracelets, headphones, glasses, etc. It should be noted that the specific types of terminals 11 and 12 are not limited in the embodiments of the present application.

[0046] The network side device 13 can be a base station or a core network, where the base station can be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (gNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP), a radio access network node or other suitable terms in the field. As long as the same technical effect is achieved, the base station is not limited to the specified technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0047] See also Figure 2 , an embodiment of the present application provides a method for feeding back a codebook, and the specific steps include: step 201.

[0048] Step 201: The terminal determines a target codebook for feedback based on one or more type 3 codebooks, or based on one or more type 3 codebooks and other HARQ-ACK codebooks that require feedback.

[0049] The one or more type 3 codebooks are triggered by the network side to require feedback from the terminal within a single time unit, or the one or more type 3 codebooks and other HARQ-ACK codebooks requiring feedback are triggered by the network side to require feedback from the terminal within a single time unit.

[0050] It is understandable that the above time unit may be a time slot or a sub-time slot, or other time units of predefined duration. The above target codebook may also be described as a codebook to be transmitted or a codebook to be fed back.

[0051] The Type 3 codebook herein may include a basic Type 3 codebook and / or an enhanced Type 3 codebook. The basic Type 3 codebook refers to feedback of HARQ-ACK information for each configured codeword for all configured HARQ processes on all carriers currently configured for the UE. The enhanced Type 3 codebook refers to feedback of HARQ-ACK information for codewords for some HARQ processes currently configured for the UE.

[0052] Other HARQ-ACK codebooks herein may include: an initially transmitted HARQ-ACK codebook and / or a retransmitted HARQ-ACK codebook.

[0053] In one embodiment of the present application, the multiple type 3 codebooks correspond to the same physical layer priority. For a specific implementation, reference may be made to Example 1 (case 1) described below.

[0054] In another embodiment of the present application, the one or more type 3 codebooks and other HARQ-ACK codebooks requiring feedback correspond to the same physical layer priority. For a specific implementation, reference may be made to Example 2 (case 2) described below.

[0055] In another embodiment of the present application, at least one of the one or more type 3 codebooks and / or other HARQ-ACK codebooks requiring feedback corresponds to a different physical layer priority than the other codebooks. For a specific implementation, reference may be made to Example 3 (case 3) described below.

[0056] In one embodiment of the present application, the step of determining the target codebook for feedback based on one or more type 3 codebooks and other HARQ-ACK codebooks that require feedback includes the following method 1 or method 2:

[0057] Mode 1: The terminal determines the target HARQ-ACK to be fed back according to the first codebook determination mode, the one or more type 3 codebooks, and other HARQ-ACK codebooks that need to be fed back;

[0058] The first codebook determination method may include codebook feedback methods 2-4 and 2-5 in Example 2 described below.

[0059] Mode 2: The terminal determines the type of the target HARQ-ACK fed back according to the second codebook determination mode;

[0060] If the type of the target HARQ-ACK is a type 3 codebook, the terminal determines the target codebook to be fed back according to the one or more type 3 codebooks;

[0061] If the type of the target HARQ-ACK is the type corresponding to the other HARQ-ACK codebook, the terminal determines the target codebook to be fed back according to the other HARQ-ACK codebook.

[0062] The second codebook determination method may include: codebook feedback method 2-1, codebook feedback method 2-2, and codebook feedback method 2-3 in Example 2 described below.

[0063] In one embodiment of the present application, the step of determining the target codebook for feedback by the terminal according to one or more type 3 codebooks includes the following (1) or (2):

[0064] (1): When the network side triggers the terminal to feed back a type 3 codebook within a single time unit, the terminal determines to feed back the type 3 codebook;

[0065] That is, when only a single type 3 codebook is triggered, the single type 3 codebook is directly fed back.

[0066] (2): When the network side triggers the terminal to feed back multiple type 3 codebooks within a single time unit, the terminal determines the target codebook to be fed back according to the third codebook determination method.

[0067] The third codebook determination mode may include: codebook feedback mode 1-1, codebook feedback mode 1-2, codebook feedback mode 1-3, codebook feedback mode 1-4, and codebook feedback mode 1-5 in Example 1 described below.

[0068] In one embodiment of the present application, the third codebook determination method includes any one of the following (1) to (5):

[0069] (1) selecting a type 3 codebook from the multiple type 3 codebooks;

[0070] It can be understood that the one or more type 3 codebooks triggered by the network side to feedback the terminal can be described as one or more type 3 codebooks triggered, and the other HARQ-ACK codebooks triggered by the network side to feedback the terminal can be described as other HARQ-ACK codebooks triggered.

[0071] For related descriptions, please refer to codebook feedback method 1-1 in Example 1.

[0072] (2) constructing a new (corresponding) type 3 codebook according to the union of the HARQ process sets corresponding to the multiple type 3 codebooks;

[0073] For related descriptions, please refer to codebook feedback methods 1-2 in Example 1.

[0074] The union of the above HARQ process sets can be understood as each HARQ process appearing at most once in the union. Based on this union, a (new) type 3 codebook to be transmitted can be constructed according to the construction principle of the type 3 codebook, for example, based on a cyclic structure of a serving cell (Serving cell) or HARQ process or transport block (Transport Block, TB) index to construct a HARQ-ACK bit sequence, and the serving cell and HARQ process involved in the traversal only cover the HARQ processes in the union.

[0075] When one or more triggered DCIs are missed, the terminal and the network may have inconsistent understandings of the number of triggered type 3 codebooks, resulting in inconsistent understandings of the information / content of the (new) type 3 codebook that actually needs to be transmitted and the corresponding number of bits.

[0076] (3) performing end-to-end concatenation of the multiple type 3 codebooks in the first order to obtain a composite codebook;

[0077] It is understandable that a single HARQ process may correspond to multiple HARQ-ACK bits in the composite codebook, thereby resulting in redundant HARQ-ACK bits.

[0078] For related descriptions, please refer to codebook feedback methods 1-3 in Example 1.

[0079] (4) determining a first type 3 codebook that satisfies the first condition;

[0080] Optionally, the first type 3 codebook may be specified by a network configuration or a protocol. The first type 3 codebook may be a basic type 3 codebook or an enhanced type 3 codebook.

[0081] When the network side configures a state list for the terminal, each state in the state list can be traversed to find a type 3 codebook that meets the first condition and corresponds to a certain state.

[0082] For related descriptions, please refer to codebook feedback methods 1-4 in Example 1.

[0083] (5) Determine the type 3 codebook for direct feedback of Rel-16.

[0084] For related descriptions, please refer to codebook feedback methods 1-5 in Example 1.

[0085] It is understandable that as long as the network side triggers the terminal to feed back multiple type 3 codebooks within a single time unit, the terminal can directly feed back the Rel-16 type 3 codebook.

[0086] In one embodiment of the present application, the first condition includes one of the following (1) to (4):

[0087] (1) The first type-3 codebook satisfies a first requirement, and among all type-3 codebooks that meet the first requirement in a set of various types of type-3 codebooks, the first type-3 codebook has the least number of bits, wherein the first requirement is: HARQ-ACKs corresponding to all HARQ processes corresponding to any type-3 codebook among the multiple type-3 codebooks that are triggered;

[0088] The sets of various types of the above-mentioned type 3 codebooks may be configured by the network side or specified by the protocol.

[0089] (2) The first type-3 codebook satisfies a second requirement, and among all type-3 codebooks that meet the second requirement in a set of various types of type-3 codebooks, the first type-3 codebook has the least number of bits, wherein the second requirement is: HARQ-ACK corresponding to all HARQ processes corresponding to the one or more triggered type-3 codebooks and the other HARQ-ACK codebooks;

[0090] (3) The first type-3 codebook satisfies a third requirement, wherein the third requirement is that the number of HARQ processes corresponding to all type-3 codebooks in the set of various types of type-3 codebooks is the smallest compared to the number of HARQ processes in the first union, where the first union is the union of all HARQ processes corresponding to each of the multiple triggered type-3 codebooks.

[0091] (4) The first type-3 codebook satisfies a fourth requirement, where the number of HARQ processes corresponding to all type-3 codebooks in the set of various types of type-3 codebooks is the smallest compared to the number of HARQ processes in the second union, where the second union is the union of all HARQ processes corresponding to the one or more triggered type-3 codebooks and the other HARQ-ACK codebooks.

[0092] In one embodiment of the present application, determining the first type 3 codebook that satisfies the first condition includes:

[0093] If there are multiple type-3 codebooks that meet the first condition, a type-3 codebook is selected from the multiple type-3 codebooks as the first type-3 codebook.

[0094] When more than one Type 3 codebook meets the first condition, a single Type 3 codebook may be selected based on predefined rules. For example, the Type 3 codebook with the largest codebook index or state index may be selected, or the Type 3 codebook with the smallest codebook index or state index may be selected.

[0095] In one embodiment of the present application, selecting a type 3 codebook from the triggered multiple type 3 codebooks includes any one of the following (1)-(11):

[0096] (1) If the multiple type-3 codebooks include a (single) base type-3 codebook, selecting the base type-3 codebook;

[0097] For related descriptions, please refer to codebook feedback method 1-1-1 in Example 1.

[0098] (2) selecting the type 3 codebook with the earliest triggering time from the multiple type 3 codebooks;

[0099] The triggering time may be the time when the network side sends information or signaling that triggers the terminal to feedback the codebook.

[0100] (3) selecting a type 3 codebook with the latest triggering time from the multiple type 3 codebooks;

[0101] For the relevant descriptions of (2) and (3) above, please refer to the codebook feedback method 1-1-2 in Example 1.

[0102] When the transmission of the type 3 codebook is triggered by DCI, the triggering time here can be determined by the DCI sending time, wherein the time sequence of the DCI can follow the rules in Rel-15 or Rel-16, for example, based on the order of the PDCCH monitoring occasion (start time / end time) where the DCI is sent. When the time (e.g., start time or end time) of the PDCCH monitoring occasion where two DCIs are sent is equal, they can be further arranged in ascending order based on the index of the downlink serving cell (DL Serving cell).

[0103] The type 3 codebook with the earliest triggering time here can be understood as the type 3 codebook triggered by the first triggering DCI among multiple triggering DCIs (each triggering DCI corresponds to a single type 3 codebook).

[0104] The type 3 codebook with the latest triggering time here can be understood as the type 3 codebook triggered by the last triggering DCI among multiple triggering DCIs (each triggering DCI corresponds to a single type 3 codebook).

[0105] When multiple triggering DCIs trigger a single Type-3 codebook, for this Type-3 codebook, only the earliest / latest single triggering DCI, or the first / last triggering DCI among these triggering DCIs is considered; that is, when selecting the Type-3 codebook with the earliest / latest triggering time from multiple Type-3 codebooks, each triggered Type-3 codebook only corresponds to a single triggering DCI selected according to the above rules, and then a single Type-3 codebook is selected from them based on the triggering DCIs corresponding to each Type-3 codebook.

[0106] (4) selecting the type 3 codebook with the earliest or latest start time of the corresponding physical uplink control channel resource from the multiple type 3 codebooks;

[0107] (5) selecting the type 3 codebook with the earliest or latest end time of the corresponding physical uplink control channel resource from the multiple type 3 codebooks;

[0108] For the relevant descriptions of (4) and (5) above, please refer to codebook feedback method 1-1-3 in Example 1.

[0109] (6) selecting a type 3 codebook having the smallest identifier or index of a corresponding physical uplink control channel resource from the multiple type 3 codebooks;

[0110] (7) selecting a type 3 codebook having the largest identifier or index of the corresponding physical uplink control channel resource from the multiple type 3 codebooks;

[0111] For the relevant descriptions of (6) and (7) above, please refer to codebook feedback method 1-1-4 in Example 1.

[0112] (8) Selecting a type 3 codebook with the largest number of corresponding HARQ processes from the multiple type 3 codebooks;

[0113] (9) Selecting a type 3 codebook with the least number of corresponding HARQ processes from the multiple type 3 codebooks;

[0114] For the relevant descriptions of (8) and (9) above, please refer to codebook feedback method 1-1-5 in Example 1.

[0115] (10) Selecting a type 3 codebook with the largest codebook index or state index from the multiple triggered type 3 codebooks;

[0116] (11) Selecting a type 3 codebook having the smallest codebook index or state index from the multiple type 3 codebooks.

[0117] For the relevant descriptions of (10) and (11) above, please refer to codebook feedback method 1-1-6 in Example 1.

[0118] The above codebook index or state index can be configured by a higher layer. For example, for each enhanced type 3 codebook, it can correspond to a state in the state list configured by the higher layer. By indicating the state index corresponding to this state in the triggering DCI, the corresponding enhanced type 3 codebook can be triggered. The state index can be the index of a state in the state list, or it can be configured independently for each state.

[0119] It should be noted that the codebook index may directly use the state index here, or may be derived based on the state index here, for example, by conversion based on a predefined formula.

[0120] Optionally, the Rel-16 type 3 codebook may also correspond to a state in the above state list, or the Rel-16 type 3 codebook does not correspond to a state in the above state list, but its codebook index or state index is specified by the protocol or configured through high-layer signaling.

[0121] In one embodiment of the present application, the first order is determined according to any one of the following (1)-(4):

[0122] (1) The time sequence of the corresponding triggering downlink control information;

[0123] For example, the time sequence of triggering the downlink control information can refer to the above description according to the ascending time sequence of triggering the downlink control information. The relevant description of the above (1) can refer to the sequence 1-1 in Example 1.

[0124] (2) The temporal order of the physical uplink control channel resources carrying the type 3 codebook;

[0125] For example, in ascending order according to the start time or end time of the physical uplink control channel resource. The description of the above (2) can refer to the sequence 1-2 in Example 1;

[0126] (3) The size order of the identifiers or indexes of the physical uplink control channel resources carrying the type 3 codebook;

[0127] For example, in ascending order of identifier or index. The description of (3) above can refer to the order 1-3 in Example 1;

[0128] (4) The size order of the codebook index or state index corresponding to the type 3 codebook.

[0129] For example, in ascending order of codebook index or state index. For the description of (4) above, please refer to the order 1-4 in Example 1.

[0130] Optionally, the transmission of each triggered downlink control information and the corresponding triggered type 3 codebook needs to meet the timeline requirement of uplink control information (UCI) multiplexing.

[0131] In one embodiment of the present application, the first codebook determination method includes any one of the following (1) to (2):

[0132] (1) performing head-to-tail concatenation of at least part of one or more type 3 codebooks and other HARQ-ACK codebooks in the second order to obtain a composite codebook;

[0133] That is, the codebooks to be transmitted are concatenated head to tail in the second order to obtain a composite codebook.

[0134] Optionally, some codebooks may be selected from one or more type 3 codebooks and other HARQ-ACK codebooks requiring feedback for head-to-tail concatenation and transmission. For example, only the type 3 codebook with the largest or smallest codebook index or state index is selected and concatenated head-to-tail with other HARQ-ACK codebooks requiring feedback.

[0135] For the related description of (1) above, please refer to codebook feedback methods 2-4 in Example 2.

[0136] (2) Direct feedback of the basic type 3 codebook;

[0137] For the related description of (2) above, please refer to codebook feedback method 2-5 in Example 2.

[0138] In one embodiment of the present application, the second sequence includes one of the following (1) to (2):

[0139] (1) The other HARQ-ACK codebooks are concatenated after the bit sequences corresponding to the one or more type 3 codebooks;

[0140] (2) The bit sequences corresponding to the one or more type 3 codebooks are concatenated after the other HARQ-ACK codebooks.

[0141] When only one type 3 codebook needs to be transmitted, the type 3 codebook bit sequence here is the type 3 codebook; when more than one type 3 codebook needs to be transmitted, the type 3 codebook bit sequence here can be a composite codebook obtained by concatenating the more than one type 3 codebooks in a predefined order according to the operations described in codebook feedback modes 1-3.

[0142] For the relevant descriptions of (1) and (2) above, please refer to sequence 2-1 in Example 2.

[0143] In one embodiment of the present application, the second order is determined according to any one of the following (1) to (4):

[0144] (1) a first time sequence, where the first time sequence is the time when the downlink control information is triggered corresponding to the one or more type 3 codebooks, and the time when the downlink control information is triggered corresponding to other HARQ-ACK codebooks that need to be fed back, for example, in ascending time order;

[0145] The time sequence of triggering DCI can be found in the previous description.

[0146] For the type 3 codebook, its corresponding (single) triggered DCI refers to the above description.

[0147] For the Type-1 codebook, Type-2 codebook, and enhanced Type-2 codebook, the last DCI carrying the corresponding HARQ-ACK can be taken as the corresponding (single) triggering DCI.

[0148] For the SPS HARQ-ACK codebook (SPS HARQ-ACK only), there is no corresponding triggering DCI, or, based on the carried SPS HARQ-ACK (when multiple SPS configurations (Config) are involved, the SPS HARQ-ACK corresponding to the SPS Config with the minimum or maximum index or a predefined value may be considered), the most recent activation / reactivation DCI, and the applied K1, a virtual DCI is determined for it.

[0149] For the related description of (1) above, please refer to sequence 2-2 in Example 2.

[0150] (2) a second time sequence, where the second time sequence is the time sequence of the physical uplink control channel resources carrying the one or more type 3 codebooks and the time sequence of the physical uplink control channel resources carrying other HARQ-ACK codebooks requiring feedback, for example, in ascending order of the start time or end time of the physical uplink control channel resources;

[0151] For the related description of (2) above, please refer to sequence 2-3 in Example 2.

[0152] (3) a first size order, where the first size order is the size order of the identifiers or indices of the physical uplink control channel resources carrying the one or more type 3 codebooks and the identifiers or indices of the physical uplink control channel resources carrying other HARQ-ACK codebooks requiring feedback, for example, in ascending order of the size of the identifiers or indices;

[0153] For the description of (2) above, please refer to the sequence 2-4 in Example 2;

[0154] (4) A second size order, where the second size order is the size order of the codebook indexes or state indexes corresponding to the one or more type 3 codebooks, and the codebook indexes or state indexes corresponding to other HARQ-ACK codebooks requiring feedback, for example, in ascending order of the size of the codebook index or state index.

[0155] The codebook index or state index corresponding to the type 3 codebook can be found in the above description.

[0156] For other HARQ-ACK codebooks, their corresponding codebook indexes or state indexes may be specified by the protocol or configured based on higher layer signaling.

[0157] It is understandable that a single HARQ process or PDSCH transmission may correspond to multiple HARQ-ACK bits in the composite codebook, thereby resulting in redundant HARQ-ACK bits.

[0158] Optionally, when the HARQ-ACK corresponding to a certain HARQ process is already included in other HARQ-ACK codebooks, the reporting information corresponding to the HARQ process is deleted in one or more cascaded type 3 codebooks, including HARQ-ACK, NDI, etc.

[0159] Optionally, each triggered DCI and the transmission corresponding to the corresponding codebook need to meet a predefined timeline requirement, where the timeline requirement can be the UCI multiplexing timeline requirement defined in Rel-15 or Rel 16, and / or, PUCCH overriding (modification) timeline requirement, and / or, other timeline requirements.

[0160] For the description of (2) above, please refer to the sequence 2-5 in Example 2;

[0161] In one embodiment of the present application, the second codebook determination method includes any one of the following (1) to (3):

[0162] (1) Only transmit type 3 codebook;

[0163] Optionally, when the network side triggers the UE to feedback a single type 3 codebook within the same time unit, and needs to feedback other HARQ-ACK codebooks, if the triggered single type 3 codebook is not a Rel-16 type 3 codebook (it can be understood that: when it is a Rel-16 type 3 codebook, based on the Rel-16 specification, only the Rel-16 type 3 codebook must be transmitted at this time, and no additional operation is required), then a method similar to the codebook feedback mode 1-4 in Example 1 can be used to search and determine a type 3 codebook of Rel-16 specified by a network configuration or protocol, so that this type 3 codebook can cover the triggered single type 3 codebook and all HARQ processes corresponding to other HARQ-ACK codebooks that need to be fed back, and the number of bits is minimized, and this type 3 codebook is transmitted.

[0164] Optionally, the HARQ process covered by the searched determined type 3 codebook is required to be closest to the union of all HARQ processes corresponding to the triggered single type 3 codebook and other HARQ-ACK codebooks that need feedback, for example, the number of HARQ processes that differ (extra or missing) is the smallest.

[0165] Optionally, when more than one Type 3 codebook meets the requirements, a single Type 3 codebook may be selected based on predefined rules. For example, the Type 3 codebook with the largest or smallest codebook index or state index may be selected. When the network side configures a state list for the UE, each state in the state list may be traversed to find a Type 3 codebook that meets the above requirements and corresponds to a particular state.

[0166] When the codebook feedback mode 1-4 in Example 1 is adopted, optionally, the searched and determined type 3 codebook can be further expanded so that this type 3 codebook can cover all HARQ processes corresponding to the triggered multiple type 3 codebooks and other HARQ-ACK codebooks that need feedback, and the number of bits is minimized, and this type 3 codebook is transmitted. Other processing is the same or similar to the corresponding processing of codebook feedback mode 1-4, and will not be repeated here.

[0167] It should be noted that when DCI is missed, the two sides may have inconsistent understandings of the HARQ processes that need to be reported in other HARQ-ACK codebooks (for missed DCI, the UE cannot accurately know the HARQ process occupied by the corresponding PDSCH transmission;

[0168] When the type 2 codebook or enhanced type 2 codebook is used, the UE can generally determine the DCI missed detection situation), which leads to inconsistent understanding of the type 3 codebook actually fed back (including the information / content contained in the codebook and the corresponding number of bits, etc.) between the two sides.

[0169] For the related description of (1) above, please refer to codebook feedback method 2-1 in Example 2.

[0170] (2) Feedback only the other HARQ-ACK codebooks;

[0171] Here, it is assumed that the Type 3 codebook can subsequently trigger further retransmissions as needed. Generally, other HARQ-ACK codebooks mainly contain the initial HARQ-ACK transmission; when it is an enhanced dynamic codebook, it may also contain retransmission HARQ-ACK.

[0172] For the related description of (2) above, please refer to codebook feedback method 2-2 in Example 2.

[0173] (3) Determine, according to the first rule, to feedback the type 3 codebook or to feedback the other HARQ-ACK codebook.

[0174] For the related description of (3) above, please refer to codebook feedback method 2-3 in Example 2.

[0175] In one embodiment of the present application, the first rule includes any one of the following (1) to (6):

[0176] (1) When the type 3 codebook contains all HARQ-ACK information in the other HARQ-ACK codebooks, only the type 3 codebook is fed back;

[0177] For example, when the type 3 codebook is a type 3 codebook of Rel-16, or contains HARQ-ACK information corresponding to all downlink HARQ processes configured by all Serving cells currently activated by the UE, assuming that the other HARQ-ACK codebook is an SPSHARQ-ACK codebook, the UE can only transmit the type 3 codebook. When a DCI miss occurs on the UE, it may not be possible to determine the DCI miss detection situation or the HARQ process scheduled by the missed DCI. Therefore, in some cases (for example, when the type 3 codebook only involves some HARQ processes for a certain DL Serving cell), the above-mentioned inclusion relationship may not be accurately determined.

[0178] For the relevant description of (1) above, please refer to Rule 1 in Example 2.

[0179] (2) Determined based on the triggering time of the type 3 codebook and / or other HARQ-ACK codebooks;

[0180] Optionally, the triggering time can be determined based on the order of triggering DCI, where the triggering DCI refers to the DCI used by the network side to trigger the terminal to feedback type 3 codebook and / or other HARQ-ACK codebook.

[0181] The triggering time of the type 3 codebook / the order of triggering DCI can refer to the previous description.

[0182] For other HARQ-ACK codebooks, when the corresponding DCI is involved (for example, a Type 1 codebook (Type-1 codebook), a Type-2 codebook, or an enhanced Type-2 codebook), the corresponding description of the triggering time of the Type 3 codebook or the order of triggering DCI may also be referred to or used;

[0183] When the corresponding DCI is not involved (for example, an SPS HARQ-ACK codebook), it is possible to directly assume the advance offset of the triggering time of other HARQ-ACK codebooks relative to the codebook transmission time, or based on the time domain feedback offset corresponding to the corresponding specified HARQ-ACK in other HARQ-ACK codebooks (for example, the minimum or maximum or specified index Serving cell index and / or the HARQ-ACK corresponding to the SPS Config corresponding to the SPS Configindex) (for example, the most recent activation or reactivation DCI indication or determined K1 of this SPS Config) to determine the time position of its virtual DCI, based on the virtual DCI, and refer to or follow the corresponding description of the triggering time of the type 3 codebook or the order of triggering DCI.

[0184] Whether to transmit the type 3 codebook or other HARQ-ACK codebook can be determined based on the order of triggering times corresponding to the type 3 codebook and other HARQ-ACK codebooks, for example, selecting a codebook type with an earlier or later transmission triggering time. The above only involves the selection between two codebook types. When determining to transmit the type 3 codebook, various methods corresponding to Example 1 can be further used to determine and transmit a type 3 codebook or a composite codebook.

[0185] Optionally, one or more type 3 codebooks and other HARQ-ACK codebooks may be uniformly configured based on the triggering time, and the codebook with the earliest / latest triggering time may be selected for transmission.

[0186] For the relevant description of (2) above, please refer to Rule 2 in Example 2.

[0187] (3) Determined based on the start time or end time of the PUCCH resource carrying the type 3 codebook and / or other HARQ-ACK codebook;

[0188] For example, based on the start time or end time of the PUCCH resources corresponding to the type 3 codebook and other HARQ-ACK codebooks, it can be determined whether to transmit the type 3 codebook or other HARQ-ACK codebooks, for example, the codebook type corresponding to the codebook with the earliest or latest start time or end time of the PUCCH resource carrying the codebook is selected.

[0189] The above only involves the selection between two codebook types. When it is determined to transmit a type 3 codebook, various methods corresponding to Example 1 may be further adopted to determine and transmit a type 3 codebook or a composite codebook.

[0190] Optionally, one or more type 3 codebooks and other HARQ-ACK codebooks may be unified based on the start time / end time of the PUCCH resource carrying the codebook, and the codebook with the earliest or latest start time or end time of the PUCCH resource carrying the codebook may be selected for transmission.

[0191] For the relevant description of (2) above, please refer to Rule 3 in Example 2.

[0192] (4) Determined based on the identifier or index of the PUCCH resource carrying the type 3 codebook and / or other HARQ-ACK codebook;

[0193] For example, based on the ID or index of the PUCCH resource corresponding to the type 3 codebook and other HARQ-ACK codebooks, it can be determined whether to transmit the type 3 codebook or other HARQ-ACK codebook, for example, the codebook type corresponding to the codebook with the smallest or largest ID or index of the PUCCH resource carrying the codebook is selected.

[0194] The above only involves the selection between two codebook types. When it is determined to transmit a type 3 codebook, various methods corresponding to Example 1 may be further adopted to determine and transmit a type 3 codebook or a composite codebook.

[0195] Optionally, one or more type 3 codebooks and other HARQ-ACK codebooks may be unified based on the ID or index of the PUCCH resource carrying the codebook, and the codebook with the smallest or largest ID or index of the PUCCH resource carrying the codebook may be selected for transmission.

[0196] For the relevant description of (2) above, please refer to Rule 4 in Example 2.

[0197] (5) Determined based on the number of HARQ processes in the type 3 codebook and / or other HARQ-ACK codebooks;

[0198] For example, based on the number of HARQ processes corresponding to the type 3 codebook and other HARQ-ACK codebooks, it can be determined whether to transmit the type 3 codebook or other HARQ-ACK codebooks, for example, the codebook type corresponding to the codebook with the most or least corresponding HARQ processes is selected.

[0199] The above only involves the selection between two codebook types. When it is determined to transmit a type 3 codebook, various methods corresponding to Example 1 may be further adopted to determine and transmit a type 3 codebook or a composite codebook.

[0200] Optionally, one or more type 3 codebooks and other HARQ-ACK codebooks may be uniformly selected based on the corresponding number of HARQ processes, and the codebook with the most or least HARQ processes corresponding to the transmission may be selected.

[0201] For the relevant description of (2) above, please refer to Rule 5 in Example 2.

[0202] (6) Determined according to the codebook index or state index corresponding to the type 3 codebook and / or other HARQ-ACK codebooks.

[0203] The above-mentioned type 3 codebook may include an enhanced type 3 codebook and / or a Rel-16 type 3 codebook. For the codebook index or state index corresponding to the enhanced type 3 codebook and / or the Rel-16 type 3 codebook, refer to the above description.

[0204] For other HARQ-ACK codebooks, the corresponding codebook index or state index may be configured by a higher layer or specified by a protocol.

[0205] Whether to transmit the type 3 codebook or other HARQ-ACK codebook can be determined based on the codebook indexes or state indexes corresponding to the type 3 codebook and other HARQ-ACK codebooks. For example, the codebook type corresponding to the codebook with the largest or smallest codebook index or state index is selected. The above only involves the selection between two codebook types. When determining to transmit the type 3 codebook, various methods corresponding to Example 1 can be further used to determine and transmit a type 3 codebook or a composite codebook.

[0206] Optionally, one or more type 3 codebooks and other HARQ-ACK codebooks may be uniformly selected based on corresponding codebook indexes or state indexes, and a codebook with the largest or smallest corresponding codebook index or state index may be transmitted.

[0207] For the relevant description of (2) above, please refer to Rule 6 in Example 2.

[0208] In one embodiment of the present application, the triggering time of the type 3 codebook and / or other HARQ-ACK codebooks is determined according to the order of triggering DCI.

[0209] In one embodiment of the present application, the method further includes:

[0210] The terminal determines the physical layer priority corresponding to the target codebook;

[0211] The terminal feeds back the target codebook according to the first codebook feedback mode and the physical layer priority corresponding to the target codebook.

[0212] For the description of the first codebook feedback mode, reference may be made to codebook feedback mode 3-1 and codebook feedback mode 3-2 in Example 3.

[0213] In one embodiment of the present application, the first codebook feedback mode includes any one of the following (1) to (3):

[0214] (1) The codebook corresponding to each physical layer priority is processed separately. When there is time domain overlap in the transmission (such as PUCCH transmission or PUSCH transmission) carrying codebooks corresponding to different physical layer priorities, only the target codebook with the higher physical layer priority is fed back;

[0215] For the processing of cross-physical layer priorities, the corresponding rules of Rel-16 priority processing (Prioritization) can be followed or continued, such as only feeding back the codebook determined for the higher physical layer priority; for a certain physical layer priority codebook, the corresponding processing methods in Example 1 and Example 2 are used.

[0216] For the description of (1), please refer to the codebook feedback method 3-1 in Example 3.

[0217] (2) Allow codebook multiplexing across physical layer priorities, or allow codebooks with different physical layer priorities to be transmitted in parallel;

[0218] For the description of (2), please refer to codebook feedback method 3-2 in Example 3.

[0219] (3) Direct feedback based type 3 codebook.

[0220] Optionally, the type 3 codebook based on the feedback corresponds to a higher physical layer priority.

[0221] For the description of (3), please refer to the codebook feedback method 3-2-4 in Example 3.

[0222] In one embodiment of the present application, HARQ-ACK codebooks of different physical layer priorities are allowed to be transmitted in parallel, including one of the following (1) to (3):

[0223] (1) When the UE supports transmitting PUCCHs carrying HARQ-ACKs corresponding to different physical layer priorities in a single time unit, the terminal transmits a target codebook corresponding to a higher physical layer priority and a target codebook corresponding to a lower physical layer priority on PUCCHs (without overlapping time domains);

[0224] The codebook corresponding to each physical layer priority can be determined using the corresponding processing methods in Example 1 and Example 2.

[0225] For any physical layer priority, when the PUCCH and PUSCH for transmitting the corresponding codebook overlap in the time domain, the corresponding codebook may be further multiplexed and transmitted on the PUSCH without transmitting the PUCCH.

[0226] For the description of (1), please refer to the codebook feedback method 3-2-1 in Example 3.

[0227] (2) When the UE supports parallel transmission of PUCCH and PUSCH, the terminal transmits a target codebook corresponding to a high physical layer priority on the PUCCH, and the terminal transmits a target codebook corresponding to a low physical layer priority on the PUSCH;

[0228] (3) When the UE supports parallel transmission of PUCCH and PUSCH, the terminal transmits a target codebook corresponding to a low physical layer priority on the PUCCH, and the terminal transmits a target codebook corresponding to a high physical layer priority on the PUSCH.

[0229] Here, the PUCCH transmission and the PUSCH transmission may overlap in the time domain. When there is a time domain overlap, they are located on different Serving cells. When there is no time domain overlap, they may be located on the same or different Serving cells.

[0230] The codebook corresponding to each physical layer priority can be determined using the corresponding processing methods in Example 1 and Example 2.

[0231] For the description of (2) and (3), please refer to the codebook feedback method 3-2-2 in Example 3.

[0232] In one embodiment of the present application, codebook multiplexing across physical layer priorities is allowed, including:

[0233] The terminal multiplexes target codebooks corresponding to different physical layer priorities, and carries the multiplexed codebook on one PUCCH for transmission.

[0234] The codebook corresponding to each physical layer priority can be determined using the corresponding processing methods in Example 1 and Example 2.

[0235] During multiplexing, the codebooks corresponding to different physical layer priorities can be cascaded head to tail (for example, the codebook with higher physical layer priority is cascaded after the codebook with lower physical layer priority, or the codebook with lower physical layer priority is cascaded after the codebook with higher physical layer priority), or the codebook corresponding to each physical layer priority is independently coded, rate matched, and resource element (RE) mapped.

[0236] When the PUCCH and PUSCH transmitting the multiplexed codebook overlap in the time domain, the multiplexed codebook may be further multiplexed and transmitted on the PUSCH without transmitting the PUCCH.

[0237] For a description of this part, please refer to codebook feedback method 3-2-3 in Example 3.

[0238] In one embodiment of the present application, the method further includes one of the following (1) to (2):

[0239] (1) The terminal does not expect the network to trigger the terminal to feed back multiple type 3 codebooks within a single time unit;

[0240] For the related description of (1) above, please refer to codebook feedback methods 1-6 in Example 1.

[0241] The network side needs to ensure that the number of Type-3 codebooks triggered in a single time unit does not exceed 1 through implementation.

[0242] Optionally, the UE expects that when the network side triggers the terminal to feedback the number of type 3 codebooks greater than 1 within a single time unit, the HARQ-ACK range corresponding to the later triggered type 3 codebook is larger, that is, it must cover all HARQ processes corresponding to the previously triggered type 3 codebook. At this time, the UE can use codebook feedback mode 1-1-1, codebook feedback mode 1-1-2 (latest triggering time), and codebook feedback mode 1-1-5 (most HARQ processes) to perform corresponding operations.

[0243] It should be noted that, in the case of the above optional UE expectation, there are some other methods with the same operation results but more complicated operations, such as codebook feedback method 1-2 and codebook feedback method 1-4.

[0244] (2) The terminal does not expect the network side to trigger the terminal to feedback the one or more type 3 codebooks and the other HARQ-ACK codebooks that need to be fed back within a single time unit;

[0245] For the related description of (2) above, please refer to codebook feedback mode 2-6 in Example 2.

[0246] Optionally, the UE expects that when the network triggers the terminal to feedback a type 3 codebook within a single time unit and needs to feedback other HARQ-ACK codebooks, the triggered type 3 codebook (or the type 3 codebook triggered after the DCI or PDSCH transmission corresponding to part or all of the HARQ-ACKs that have been triggered in other HARQ-ACK codebooks) corresponds to the HARQ process must cover all HARQ processes corresponding to other HARQ-ACK codebooks (or all HARQ processes corresponding to part or all of the HARQ-ACKs that have been triggered in other HARQ-ACK codebooks).

[0247] In this embodiment of the present application, when the network side triggers one or more type 3 codebooks in a single time unit, or when the network side triggers one or more type 3 codebooks in a single time unit and needs to feedback other HARQ-ACK codebooks, the terminal can determine and feedback the target codebook according to one or more type 3 codebooks, or according to one or more type 3 codebooks and other HARQ-ACK codebooks that need to be fed back, thereby ensuring HARQ-ACK feedback performance and improving the reliability of the communication system.

[0248] See also Figure 3 , an embodiment of the present application provides a method for feeding back a codebook, and the specific steps include: step 301 and step 302.

[0249] Step 301: The network side device triggers the terminal to feedback one or more type 3 codebooks in a single time unit, or the network side device triggers the terminal to feedback one or more type 3 codebooks and other HARQ-ACK codebooks in a single time unit;

[0250] Step 302: The network side device obtains a target codebook fed back by the terminal, where the target codebook is determined by the terminal based on one or more type 3 codebooks, or based on one or more type 3 codebooks and other HARQ-ACK codebooks that need to be fed back.

[0251] In one embodiment of the present application, the multiple type 3 codebooks correspond to the same physical layer priority;

[0252] or,

[0253] The one or more type 3 codebooks and other HARQ-ACK codebooks requiring feedback correspond to the same physical layer priority;

[0254] or,

[0255] At least one of the one or more type 3 codebooks and / or other HARQ-ACK codebooks requiring feedback corresponds to a different physical layer priority than the other codebooks.

[0256] In one embodiment of the present application, when the terminal does not expect the network to trigger the terminal to feed back multiple type 3 codebooks within a single time unit, the method further includes:

[0257] The network-side device determines that the number of type 3 codebooks fed back by the terminal in a single time unit is one.

[0258] In one embodiment of the present application, the method further includes:

[0259] The network side device determines that the HARQ process corresponding to the type 3 codebook fed back by the terminal within a single time unit covers all HARQ processes corresponding to the other HARQ-ACK codebooks.

[0260] In an embodiment of the present application, when the network side triggers one or more type 3 codebooks in a single time unit, or when the network side triggers one or more type 3 codebooks in a single time unit and needs to feedback other HARQ-ACK codebooks, the network side device can obtain the terminal according to one or more type 3 codebooks, or according to one or more type 3 codebooks and other HARQ-ACK codebooks that need to be fed back, determine and feedback the target codebook, thereby ensuring the HARQ-ACK feedback performance and improving the reliability of the communication system.

[0261] The following describes the implementation of the present application in conjunction with Example 1, Example 2, and Example 3.

[0262] It should be noted that the time unit in Example 1, Example 2 and Example 3 is described using Slot or Sub-slot as an example. Other cases are similar and will not be described in detail here.

[0263] Example 1: The UE triggers one or more Type-3 codebooks in a single (or described as the same) slot or sub-slot, where the triggered one or more Type-3 codebooks correspond to the same physical layer priority.

[0264] The aforementioned Type-3 codebook may include: the Rel-16 Type-3 codebook and the enhanced Type-3 codebook. The enhanced Type-3 codebook may be the enhanced Type-3 codebook considered in Rel-17, or any one of multiple enhanced Type-3 codebooks. Different enhanced Type-3 codebooks may correspond to different codebook sizes and / or different reported information or content.

[0265] When the information or content of two or more Type-3 codebooks triggered are completely consistent, they can be considered to be triggered by a single (or the same) Type-3 codebook.

[0266] Example 1 includes: Example 1-1 or Example 1-2, wherein,

[0267] Example 1-1: When the network side triggers the terminal to feedback only one (or single) Type-3 codebook, this Type-3 codebook is directly transmitted.

[0268] Example 1-2: See Figure 4 When the network triggers the terminal to feedback multiple Type-3 codebooks (type-3CB1 and type-3CB2), any of the codebook feedback modes 1-1 to 1-6 can be used:

[0269] Codebook feedback mode 1-1: Select one of the Type-3 codebooks for transmission, such as type-3CB1 or type-3CB2.

[0270] Optionally, the codebook feedback mode 1-1 may include: any one of codebook feedback modes 1-1-1 to 1-1-6:

[0271] Codebook feedback mode 1-1-1: When the network side triggers the terminal to feedback multiple Type-3 codebooks including one Rel-16 Type-3 codebook, this Rel-16 Type-3 codebook is selected.

[0272] Codebook feedback mode 1-1-2: Select the Type-3 codebook with the earliest trigger time, or select the Type-3 codebook with the latest trigger time.

[0273] When the transmission of the Type-3 codebook is triggered by DCI, the triggering time may use the DCI delivery time, wherein the order of the DCI delivery time may follow the rules in Rel-15 or Rel-16, for example, based on the order of the PDCCH monitoring occasions (start time or end time) where the DCI is delivered. When the times (e.g., start time or end time) of the PDCCH monitoring occasions where two DCIs are delivered are equal, they may be further arranged in ascending order based on the index of the DL Serving cell.

[0274] The Type-3 codebook with the earliest triggering time can be understood as the Type-3 codebook triggered by the first triggering DCI among multiple triggering DCIs (each triggering DCI corresponds to a Type-3 codebook).

[0275] The Type-3 codebook with the latest triggering time can be understood as the Type-3 codebook triggered by the last triggering DCI among multiple triggering DCIs (each triggering DCI corresponds to a Type-3 codebook).

[0276] When multiple triggering DCIs trigger a single (or the same) Type-3 codebook, only the earliest or latest triggering DCI, or the first or last triggering DCI, among these triggering DCIs is considered for that Type-3 codebook. That is, when selecting the Type-3 codebook with the earliest or latest triggering time from multiple Type-3 codebooks, each triggering Type-3 codebook corresponds to only one triggering DCI selected according to the aforementioned rules. A Type-3 codebook is then selected based on the triggering DCIs corresponding to each Type-3 codebook.

[0277] Codebook feedback mode 1-1-3: Select the Type-3 codebook with the earliest or latest start time of the PUCCH resources of the Type-3 codebook triggered by the carrier, or select the Type-3 codebook with the earliest or latest end time of the PUCCH resources of the Type-3 codebook triggered by the carrier;

[0278] Codebook feedback mode 1-1-4: Select the Type-3 codebook with the smallest ID or index of the PUCCH resource of the Type-3 codebook that carries the trigger, or select the Type-3 codebook with the largest ID or index of the PUCCH resource of the Type-3 codebook that carries the trigger;

[0279] Codebook feedback mode 1-1-5: Select the Type-3 codebook with the most corresponding HARQ processes, or select the Type-3 codebook with the least corresponding HARQ processes;

[0280] Codebook feedback mode 1-1-6: Select the Type-3 codebook with the largest codebook index or state index, or select the Type-3 codebook with the smallest codebook index or state index;

[0281] The Codebook index or State index can be configured by higher layers. For example, for each enhanced Type-3 codebook, it can correspond to a State in the State list configured by the higher layers. By indicating the State index corresponding to this State in the triggering DCI, the corresponding enhanced Type-3 codebook can be triggered. The State index can be the index of a State in the State list, or it can be configured independently for each State. The Codebook index can directly use the State index here, or it can be derived based on the State index, for example, by converting it based on a predefined formula.

[0282] Optionally, the Rel-16 Type-3 codebook may also correspond to a State in the above State list, or the Rel-16 Type-3 codebook may not correspond to a State in the above State list, but the Codebook index or State index of the Rel-16 Type-3 codebook is specified by the protocol or configured through high-layer signaling.

[0283] Codebook feedback mode 1-2: Based on the union of the HARQ process sets corresponding to the triggered multiple Type-3 codebooks, a corresponding (new (or described as to be transmitted)) Type-3 codebook is constructed and transmitted;

[0284] The union of the HARQ process sets can be understood as each HARQ process appearing at most once in the union. Based on this union, a new Type-3 codebook can be constructed according to the construction principles of the Type-3 codebook. For example, the HARQ-ACK bit sequence is constructed based on a cyclic structure of the serving cell, HARQ process, and / or transport block (TB) index. When traversing, the corresponding serving cell and HARQ process only covers the HARQ processes in the union.

[0285] When one or more triggered DCIs are missed, the UE and the network may have different understandings of the number of triggered Type-3 codebooks, resulting in inconsistent understanding of the information or content of the (new) Type-3 codebook to be transmitted and the corresponding number of bits.

[0286] Codebook feedback mode 1-3: Concatenate multiple triggered Type-3 codebooks in a predefined order to obtain a composite codebook and transmit it

[0287] The predefined order can be any of the following:

[0288] Sequence 1-1: based on the time sequence of the corresponding DCI triggering, for example, in ascending order of time. The time sequence of the DCI triggering can be referred to the previous description;

[0289] Sequence 1-2: Time sequence of PUCCH resources based on the bearer-triggered Type-3 codebook, for example, in ascending order of the start time or end time of the PUCCH resources;

[0290] Sequence 1-3: based on the order of the ID or index of the PUCCH resource in the Type-3 codebook triggered by the bearer, for example, in ascending order of the ID or index of the PUCCH resource;

[0291] Sequence 1-4: based on the size of the Codebook index or State index corresponding to the triggered Type-3 codebook, for example, in ascending order of the Codebook index or State index.

[0292] It is understandable that a single HARQ process may correspond to multiple (ie, more than one) HARQ-ACK bits in the composite codebook, thereby resulting in redundant HARQ-ACK bits.

[0293] Optionally, the transmission between each triggered DCI and the corresponding triggered Type-3 codebook needs to meet the Timeline requirements of UCI multiplexing.

[0294] Codebook feedback mode 1-4: Search and determine a Type-3 codebook specified by the network configuration or protocol, so that this Type-3 codebook can cover at least some of the HARQ processes corresponding to all the triggered Type-3 codebooks, and the Type-3 codebook determined by the search has the smallest number of bits, and transmit this Type-3 codebook

[0295] Optionally, the HARQ processes covered by the searched and determined Type-3 codebook are required to be closest to the union of all HARQ processes corresponding to the triggered multiple Type-3 codebooks, for example, the number of HARQ processes with the difference (extra or missing) is the smallest.

[0296] When more than one Type-3 codebook meets the requirements, a Type-3 codebook can be selected based on predefined rules. For example, the Type-3 codebook with the largest or smallest Codebook index or State index can be selected.

[0297] The Type-3 codebook determined by the search may be either the Rel-16 Type-3 codebook or the enhanced Type-3 codebook.

[0298] When the network side configures a State list for the UE, it can traverse each State in the State list to find a Type-3 codebook that meets the above requirements and corresponds to a certain State.

[0299] Codebook feedback methods 1-5: Direct feedback of Rel-16 Type-3 codebook;

[0300] It should be noted that codebook feedback mode 1-5 is slightly different from codebook feedback mode 1-1-1.

[0301] Codebook feedback mode 1-5 directly feeds back the Rel-16 Type-3 codebook as long as multiple Type-3 codebooks are triggered in a single slot or sub-slot. Codebook feedback mode 1-1-1 only feeds back the Rel-16 Type-3 codebook when the multiple Type-3 codebooks triggered include the Rel-16 Type-3 codebook.

[0302] Codebook feedback mode 1-6: The UE does not expect the network to trigger multiple Type-3 codebooks in a single slot or sub-slot;

[0303] The network side needs to ensure that the number of Type-3 codebooks triggered in a single slot or sub-slot does not exceed 1 through implementation.

[0304] Optionally, the UE expects that when the network side triggers more than 1 Type-3 codebook in a single Slot or Sub-slot, the HARQ-ACK range corresponding to the later triggered Type-3 codebook is larger, that is, it must cover all HARQ processes corresponding to the previously triggered Type-3 codebook (it should be noted that, based on the previous description, when the Type-3 codebook information or content triggered twice or more is exactly the same, it can be considered as a single Type-3 codebook triggered). At this time, any of the codebook feedback modes 1-1-1, 1-1-2 (latest triggering time), and 1-1-5 (most HARQ processes) can be used to perform the corresponding operation.

[0305] It should be noted that there are some other methods with the same operation results but more complicated operations, such as codebook feedback method 1-2 and codebook feedback method 1-4.

[0306] Example 2: When the UE triggers one or more Type-3 codebooks (Type-3 CB) in a single slot or sub-slot and needs to feedback other HARQ-ACK codebooks (other CB), the one or more Type-3 codebooks triggered and the other HARQ-ACK codebooks that need to be fed back correspond to the same physical layer priority. For a schematic diagram, see Figure 5 .

[0307] The other HARQ-ACK codebook that requires feedback can be one of the SPS HARQ-ACK codebook (SPS HARQ-ACK only), Type-1 codebook, Type-2 codebook, and enhanced Type-2 codebook. Based on the Rel-15 or Rel-16 protocol specifications, it is currently understood that there is at most one other HARQ-ACK codebook that requires feedback in a single slot or sub-slot.

[0308] The codebook feedback mode in Example 2 includes: any one of codebook feedback mode 2-1 to codebook feedback mode 2-6:

[0309] Codebook feedback mode 2-1: only transmits Type-3 codebook.

[0310] Specifically, various methods corresponding to Example 1 may be adopted, including the operation corresponding to Example 1-1 and any method corresponding to Example 1-2.

[0311] Optionally, when the UE triggers a Type-3 codebook within a single slot or sub-slot and needs to feedback other HARQ-ACK codebooks, if the triggered Type-3 codebook is not a Rel-16 Type-3 codebook (it should be noted that if a triggered Type-3 codebook is a Rel-16 Type-3 codebook, based on the Rel-16 specification, only the Rel-16 Type-3 codebook must be transmitted at this time, and no additional operation is required), then a method similar to codebook feedback mode 1-4 can be used to search and determine a Type-3 codebook specified by a network configuration or protocol, so that the Type-3 codebook determined by the search can cover the triggered Type-3 codebook and all HARQ processes corresponding to other HARQ-ACK codebooks that need to be fed back, and the number of bits of the Type-3 codebook determined by the search is the smallest, and the Type-3 codebook determined by the search is transmitted.

[0312] Optionally, the HARQ process covered by the searched Type-3 codebook is closest to the union of all HARQ processes corresponding to the triggered single Type-3 codebook and other HARQ-ACK codebooks that need feedback, for example, the number of HARQ processes that differ (extra or missing) is the smallest.

[0313] When more than one Type-3 codebook is identified through the search, a Type-3 codebook can be selected based on predefined rules. For example, the Type-3 codebook with the largest Codebook index or State index can be selected, or the Type-3 codebook with the smallest Codebook index or State index can be selected. When the network configures a State list for the UE, each State in the State list can be traversed to find a Type-3 codebook that meets the above requirements and corresponds to a particular State.

[0314] When codebook feedback mode 1-4 is adopted, optionally, the Type-3 codebook determined by the search can be further expanded so that the Type-3 codebook determined by the search can cover multiple triggered Type-3 codebooks and all HARQ processes corresponding to other HARQ-ACK codebooks that need feedback, and the number of bits of the Type-3 codebook determined by the search is the smallest, and the Type-3 codebook determined by the search is transmitted. The other processing is the same or similar to the corresponding processing of codebook feedback mode 1-4, and will not be repeated here.

[0315] It should be noted that when DCI is missed, the two sides may have inconsistent understandings of the HARQ processes that need to be reported in other HARQ-ACK codebooks (for missed DCI, the UE cannot accurately know the HARQ process occupied by the corresponding PDSCH transmission;

[0316] It should be noted that when using Type-2 codebook or enhanced Type-2 codebook, the UE can generally determine the DCI missed detection situation), which leads to inconsistent understanding of the actual feedback Type-3 codebook (including the information or content contained in the codebook, and the corresponding number of bits, etc.) on both sides.

[0317] Codebook feedback mode 2-2: Only other HARQ-ACK codebooks are transmitted;

[0318] Here, it is assumed that the Type-3 codebook can be further retransmitted as needed. In general, other HARQ-ACK codebooks can include the initially transmitted HARQ-ACK codebook; when using an enhanced dynamic codebook, they may also include the retransmitted HARQ-ACK codebook.

[0319] Codebook feedback mode 2-3: Determine the transmission of Type-3 codebook or other HARQ-ACK codebook based on predefined rules

[0320] The predefined rules may include any one of Rule 1 to Rule 6:

[0321] Rule 1: When a Type-3 codebook contains all HARQ-ACK information in other HARQ-ACK codebooks, only this Type-3 codebook is transmitted.

[0322] For example, when the Type-3 codebook is a Rel-16 Type-3 codebook, or contains the HARQ-ACK information corresponding to all downlink HARQ processes configured by all Serving cells currently activated by the UE, assuming that the other HARQ-ACK codebook is an SPS HARQ-ACK codebook, the UE can only transmit the Type-3 codebook. When a DCI miss occurs on the UE, it may not be possible to determine the DCI miss detection situation or the HARQ process scheduled by the missed DCI. Therefore, in some cases (for example, when the Type-3 codebook only involves some HARQ processes for a certain DL Serving cell), it may not be possible to accurately determine the above-mentioned inclusion relationship.

[0323] Rule 2: Determined based on trigger time.

[0324] Optionally, the triggering time may be determined based on the order in which the DCI is triggered.

[0325] For the triggering time of the Type-3 codebook or the order of triggering DCI, please refer to the previous description.

[0326] For other HARQ-ACK codebooks, when the corresponding DCI is involved (for example, Type-1 codebook, Type-2 codebook, or enhanced Type-2 codebook), the corresponding description of the triggering time or the order of triggering DCI of the Type-3 codebook may also be referred to or used;

[0327] When the corresponding DCI is not involved (for example, an SPS HARQ-ACK codebook), it is possible to directly assume the advance offset of the triggering time of other HARQ-ACK codebooks relative to the codebook transmission time, or based on the time domain feedback offset corresponding to the corresponding specified HARQ-ACK in other HARQ-ACK codebooks (for example, the HARQ-ACK corresponding to the SPS Config corresponding to the minimum, maximum or specified index Serving cell index and / or SPS Config index) (for example, the most recent activation or reactivation DCI indication or determined K1 of this SPS Config) to determine the time position of its virtual DCI, based on the virtual DCI, and refer to or follow the corresponding description of the triggering time of the Type-3 codebook or the order of triggering the DCI.

[0328] For example, based on the order of triggering times corresponding to the Type-3 codebook and other HARQ-ACK codebooks, it is determined whether to transmit the Type-3 codebook or other HARQ-ACK codebook, for example, selecting a codebook type with an earlier or later transmission triggering time. The above only involves the selection between two codebook types. When it is determined to transmit the Type-3 codebook, various methods corresponding to Example 1 can be further used to determine and transmit a Type-3 codebook or composite codebook.

[0329] Optionally, one or more Type-3 codebooks and other HARQ-ACK codebooks may be unified based on the triggering time, and the codebook with the earliest or latest triggering time may be selected for transmission.

[0330] Rule 3: Determined based on the start time or end time of the PUCCH resource carrying the codebook.

[0331] For example, based on the start time or end time of the PUCCH resources corresponding to the Type-3 codebook and other HARQ-ACK codebooks, determine whether to transmit the Type-3 codebook or other HARQ-ACK codebook, for example, select the codebook type corresponding to the codebook with the earliest or latest start time or end time of the PUCCH resource carrying the codebook.

[0332] The above only involves the selection between two codebook types. When it is determined to transmit a Type-3 codebook, various methods corresponding to Example 1 can be further adopted to determine and transmit a Type-3 codebook or a composite codebook.

[0333] Optionally, one or more Type-3 codebooks and other HARQ-ACK codebooks can be unified based on the start time or end time of the PUCCH resource carrying the codebook, and the codebook with the earliest or latest start time or end time of the PUCCH resource carrying the codebook is selected for transmission.

[0334] Rule 4: Determined based on the ID or index of the PUCCH resource carrying the codebook.

[0335] Whether to transmit the Type-3 codebook or other HARQ-ACK codebook can be determined based on the ID or index of the PUCCH resource corresponding to the Type-3 codebook and other HARQ-ACK codebooks, for example, the codebook type corresponding to the codebook with the smallest or largest ID or index of the PUCCH resource carrying the codebook is selected.

[0336] The above only involves the selection between two codebook types. When it is determined to transmit a Type-3 codebook, various methods corresponding to Example 1 can be further adopted to determine and transmit a Type-3 codebook or a composite codebook.

[0337] Optionally, one or more Type-3 codebooks, as well as other HARQ-ACK codebooks, can be unified based on the ID or index of the PUCCH resource carrying the codebook, and the codebook with the ID of the PUCCH resource carrying the codebook, the smallest index, or the largest index can be selected for transmission.

[0338] Rule 5: Determined based on the corresponding number of HARQ processes.

[0339] Based on the number of HARQ processes corresponding to the Type-3 codebook and other HARQ-ACK codebooks, it can be determined whether to transmit the Type-3 codebook or other HARQ-ACK codebooks. For example, the codebook type corresponding to the codebook with the most corresponding HARQ processes is selected, or the codebook type corresponding to the codebook with the least corresponding HARQ processes is selected.

[0340] The above only involves the selection between two codebook types. When it is determined to transmit a Type-3 codebook, various methods corresponding to Example 1 can be further adopted to determine and transmit a Type-3 codebook or a composite codebook.

[0341] Optionally, one or more Type-3 codebooks and other HARQ-ACK codebooks can be unified based on the corresponding number of HARQ processes, and the codebook with the most corresponding HARQ processes can be selected for transmission, or the codebook with the least corresponding HARQ processes can be selected for transmission.

[0342] Rule 6: Determined based on Codebook index or State index.

[0343] For the Codebook index or State index corresponding to the enhanced Type-3 codebook and / or Rel-16 Type-3 codebook, see the above description.

[0344] For other HARQ-ACK codebooks, the corresponding Codebook index or State index may be configured by a higher layer or specified by a protocol.

[0345] Whether to transmit the Type-3 codebook or other HARQ-ACK codebook can be determined based on the Codebook index or State index corresponding to the Type-3 codebook and other HARQ-ACK codebooks, for example, the codebook type corresponding to the codebook with the largest or smallest Codebook index or State index is selected. The above only involves the selection between two codebook types. When it is determined to transmit the Type-3 codebook, various methods corresponding to Example 1 can be further used to determine and transmit a Type-3 codebook or composite codebook.

[0346] Optionally, one or more Type-3 codebooks and other HARQ-ACK codebooks may be unified based on the corresponding Codebook index or State index, and the codebook with the largest or smallest corresponding Codebook index or State index may be selected for transmission.

[0347] Codebook feedback method 2-4: The codebooks to be transmitted are concatenated head to tail in a predefined order to obtain a composite codebook and transmit it

[0348] The codebooks that need to be transmitted here include one or more triggered Type-3 codebooks and other HARQ-ACK codebooks that need feedback.

[0349] Optionally, some codebooks may be selected for head-to-tail concatenation and transmission, for example, only the Type-3 codebook with the largest or smallest Codebook index or State index is selected and concatenated head-to-tail with other HARQ-ACK codebooks that require feedback.

[0350] The predefined order in codebook feedback mode 2-4 may include any of sequences 2-1 to 2-5:

[0351] Sequence 2-1: concatenate other HARQ-ACK codebooks after the Type-3 codebook bit sequence, or concatenate the Type-3 codebook bit sequence after other HARQ-ACK codebooks.

[0352] When only one Type-3 codebook needs to be transmitted, the Type-3 codebook bit sequence here is this Type-3 codebook. When more than one Type-3 codebook needs to be transmitted, the Type-3 codebook bit sequence here can be a composite codebook obtained by concatenating these more than one Type-3 codebooks in a predefined order according to the operations described in codebook feedback methods 1-3.

[0353] Sequence 2-2: based on the time sequence of the corresponding DCI triggering;

[0354] For example, according to the ascending order of the time of triggering the corresponding DCI, the time sequence of triggering the DCI can refer to the previous description.

[0355] For the Type-3 codebook, its corresponding (single) triggering DCI refers to the above description.

[0356] For Type-1 codebook, Type-2 codebook, and enhanced Type-2 codebook, the last DCI carrying the corresponding HARQ-ACK can be taken as the corresponding (single) triggering DCI.

[0357] For the SPS HARQ-ACK codebook (only SPS HARQ-ACK), there is no corresponding triggering DCI, or, based on the carried SPS HARQ-ACK (when multiple SPS configurations (Config) are involved, the SPS HARQ-ACK corresponding to the SPS Config with the smallest index, the largest index, or a predefined value may be considered), the most recent activation or reactivation DCI, and the applied K1, a virtual DCI is determined for it.

[0358] Sequence 2-3: based on the time sequence of the PUCCH resources carrying each codebook;

[0359] For example, in ascending order according to the start time or end time of the PUCCH resources carrying each codebook.

[0360] Sequence 2-4: based on the order of the ID or index of the PUCCH resource carrying each codebook, for example, in ascending order of ID or index;

[0361] Sequence 2-5: based on the size of the codebook index or state index corresponding to each codebook, for example, in ascending order of codebook index or state index;

[0362] For the Codebook index or State index corresponding to the Type-3 codebook, see the previous description.

[0363] For other HARQ-ACK codebooks, the corresponding Codebook index or State index may be specified by the protocol or configured based on high-layer signaling.

[0364] It is understandable that a single HARQ process or PDSCH transmission may correspond to more than one HARQ-ACK bit in the composite codebook, thereby resulting in redundant HARQ-ACK bits.

[0365] Optionally, when the HARQ-ACK corresponding to a certain HARQ process is already included in other HARQ-ACK codebooks, the reporting information corresponding to this HARQ process is deleted in one or more cascaded Type-3 codebooks, including HARQ-ACK, NDI, etc.

[0366] Optionally, each triggered DCI and the transmission corresponding to the corresponding codebook need to meet a predefined timeline requirement, where the timeline requirement can be the UCI multiplexing timeline requirement defined in Rel-15 or Rel-16, and / or the PUCCH overriding timeline requirement, and / or other timeline requirements.

[0367] Codebook feedback methods 2-5: Direct feedback of Rel-16 Type-3 codebook;

[0368] Codebook feedback mode 2-6: The UE does not expect the network to trigger the Type-3 codebook within a single slot or sub-slot and needs to feedback other HARQ-ACK codebooks;

[0369] The network side needs to avoid this situation through implementation.

[0370] Optionally, the UE expects that when the network triggers the Type-3 codebook within a single Slot or Sub-slot and needs to feedback other HARQ-ACK codebooks, the HARQ process corresponding to the triggered Type-3 codebook (or the Type-3 codebook triggered after the DCI or PDSCH transmission corresponding to part or all HARQ-ACKs that have been triggered in other HARQ-ACK codebooks) must cover all HARQ processes corresponding to other HARQ-ACK codebooks (or all HARQ processes corresponding to part or all HARQ-ACKs that have been triggered in other HARQ-ACK codebooks).

[0371] Example 3: When the UE triggers one or more Type-3 codebooks in a single slot or sub-slot, and optionally needs to feedback other HARQ-ACK codebooks (one or two; when there are two, each corresponding to a different physical layer priority), at least one of the one or more Type-3 codebooks and / or other HARQ-ACK codebooks corresponds to a different physical layer priority from the other codebooks.

[0372] Example 3 may include: any one of codebook feedback modes 3-1 to 3-2:

[0373] Codebook feedback method 3-1: For the processing of cross-physical layer priorities, the corresponding priority (Prioritization) rules of Rel-16 can be followed / continued (only the codebook determined for the higher physical layer priority is fed back); for a certain priority, the corresponding processing methods in Example 1 and Example 2 are followed.

[0374] Codebook feedback mode 3-2: allows HARQ-ACK multiplexing across physical layer priorities, or allows HARQ-ACK of different physical layer priorities to be transmitted in parallel.

[0375] Codebook feedback mode 3-2 may include: any one of codebook feedback modes 3-2-1 to 3-2-4:

[0376] Codebook feedback mode 3-2-1: When the UE supports the transmission of PUCCH carrying HARQ-ACK corresponding to different physical layer priorities in a single slot or sub-slot, the UE transmits the codebook corresponding to the higher physical layer priority and the codebook corresponding to the lower physical layer priority on the PUCCH (without overlapping time domain)

[0377] The codebook corresponding to each physical layer priority can be determined using the corresponding processing methods in Example 1 and Example 2.

[0378] For any physical layer priority, when the PUCCH and PUSCH for transmitting the corresponding codebook overlap in the time domain, the corresponding codebook may be further multiplexed and transmitted on the PUSCH without transmitting the PUCCH.

[0379] Codebook feedback mode 3-2-2: When the UE supports parallel transmission of PUCCH and PUSCH, the UE transmits the codebook corresponding to the higher / lower physical layer priority on PUCCH and the codebook corresponding to the lower / higher physical layer priority on PUSCH

[0380] Here, the PUCCH transmission and the PUSCH transmission may overlap in the time domain. When there is a time domain overlap, they are located on different Serving cells. When there is no time domain overlap, they may be located on the same or different Serving cells.

[0381] The codebook corresponding to each physical layer priority can be determined using the corresponding processing methods in Example 1 and Example 2.

[0382] Codebook feedback mode 3-2-3: The UE multiplexes the codebooks corresponding to different physical layer priorities and transmits the multiplexed codebooks on a single PUCCH.

[0383] The codebook corresponding to each physical layer priority can be determined using the corresponding processing methods in Example 1 and Example 2.

[0384] During multiplexing, the codebooks corresponding to different physical layer priorities can be cascaded head to tail (for example, the codebook with higher physical layer priority is cascaded after the codebook with lower physical layer priority, or the codebook with lower physical layer priority is cascaded after the codebook with higher physical layer priority), or the codebook corresponding to each physical layer priority is independently encoded, rate matched, and RE mapped.

[0385] When the PUCCH and PUSCH transmitting the multiplexed codebook overlap in the time domain, the multiplexed codebook may be further multiplexed and transmitted on the PUSCH without transmitting the PUCCH.

[0386] Codebook Feedback Method 3-2-4: Direct Feedback Rel-16 Type-3 Codebook

[0387] Optionally, the fed-back Rel-16 Type-3 codebook corresponds to a higher physical layer priority.

[0388] See also Figure 6 , an embodiment of the present application provides a device for feeding back a codebook, the device 600 including:

[0389] A first determining module 601 is configured to determine a target codebook for feedback based on one or more type 3 codebooks, or based on one or more type 3 codebooks and other hybrid automatic repeat request response HARQ-ACK codebooks requiring feedback;

[0390] The one or more type 3 codebooks are triggered by the network side to require feedback from the terminal within a single time unit, or the one or more type 3 codebooks and other HARQ-ACK codebooks requiring feedback are triggered by the network side to require feedback from the terminal within a single time unit.

[0391] In one embodiment of the present application, the multiple type 3 codebooks correspond to the same physical layer priority;

[0392] or,

[0393] The one or more type 3 codebooks and other HARQ-ACK codebooks requiring feedback correspond to the same physical layer priority;

[0394] or,

[0395] At least one of the one or more type 3 codebooks and / or other HARQ-ACK codebooks requiring feedback corresponds to a different physical layer priority than the other codebooks.

[0396] In one embodiment of the present application, the first determining module 501 is further configured to:

[0397] Determine the target HARQ-ACK to be fed back according to the first codebook determination method, the one or more type 3 codebooks, and other HARQ-ACK codebooks that require feedback;

[0398] or,

[0399] Determining a target HARQ-ACK type for feedback according to the second codebook determination method;

[0400] If the type of the target HARQ-ACK is a type 3 codebook, the terminal determines the target codebook to be fed back according to the one or more type 3 codebooks;

[0401] If the type of the target HARQ-ACK is the type corresponding to the other HARQ-ACK codebook, the terminal determines the target codebook to be fed back according to the other HARQ-ACK codebook.

[0402] In one embodiment of the present application, the first determining module 501 is further configured to:

[0403] When the network side triggers the terminal to feed back a type 3 codebook within a single time unit, determining to feed back the type 3 codebook;

[0404] or,

[0405] In the case where the network side triggers the terminal to feed back multiple type 3 codebooks within a single time unit, the target codebook to be fed back is determined according to the third codebook determination method.

[0406] In one embodiment of the present application, the third codebook determination method includes any one of the following:

[0407] Selecting a type 3 codebook from the triggered multiple type 3 codebooks;

[0408] Constructing a new type 3 codebook according to a union of the HARQ process sets corresponding to the multiple type 3 codebooks triggered;

[0409] Performing end-to-end concatenation on the triggered multiple type 3 codebooks in the first order to obtain a composite codebook;

[0410] Determining a first type 3 codebook that satisfies a first condition;

[0411] Determine the direct feedback basic type 3 codebook.

[0412] In one embodiment of the present application, the first condition includes:

[0413] The first type-3 codebook satisfies a first requirement, and among all type-3 codebooks that meet the first requirement in a set of various types of type-3 codebooks, the first type-3 codebook has the least number of bits, wherein the first requirement is: HARQ-ACK corresponding to all HARQ processes corresponding to any one type-3 codebook in the multiple type-3 codebooks that are triggered;

[0414] or,

[0415] The first type-3 codebook satisfies the second requirement, and among all type-3 codebooks that meet the second requirement in a set of various types of type-3 codebooks, the first type-3 codebook has the least number of bits, wherein the second requirement is: HARQ-ACK corresponding to all HARQ processes corresponding to one or more triggered type-3 codebooks and other HARQ-ACK codebooks;

[0416] or,

[0417] The first type-3 codebook satisfies a third requirement, where the third requirement is that the number of HARQ processes corresponding to all type-3 codebooks in the set of various types of type-3 codebooks differs from the number of HARQ processes in a first union set at a minimum, where the first union set is the union of all HARQ processes corresponding to each of the multiple triggered type-3 codebooks;

[0418] or,

[0419] The first type-3 codebook satisfies the fourth requirement, where the fourth requirement is that all HARQ processes corresponding to the type-3 codebooks in the set of various types of type-3 codebooks have the least number of HARQ processes compared with the second union, and the second union is the union of all HARQ processes corresponding to each of the one or more triggered type-3 codebooks and the other HARQ-ACK codebooks.

[0420] In one embodiment of the present application, the HARQ processes covered by the first type-3 codebook are compared with the union of all HARQ processes corresponding to the multiple type-3 codebooks triggered, and the number of HARQ processes is the smallest;

[0421] or,

[0422] The HARQ process covered by the first type 3 codebook has the least difference in the number of HARQ processes compared to the union of all HARQ processes corresponding to the one or more triggered type 3 codebooks and other HARQ-ACK codebooks that require feedback.

[0423] In one embodiment of the present application, determining the first type 3 codebook that satisfies the first condition includes:

[0424] If there are multiple type-3 codebooks that meet the first condition, a type-3 codebook is selected from the multiple type-3 codebooks as the first type-3 codebook.

[0425] In one embodiment of the present application, the state corresponding to the first type 3 codebook is included in a state list configured on the network side.

[0426] In one embodiment of the present application, the first type-3 codebook includes: a basic type-3 codebook and / or an enhanced type-3 codebook.

[0427] In one embodiment of the present application, the selecting a type 3 codebook from the triggered multiple type 3 codebooks includes any one of the following:

[0428] If the multiple type-3 codebooks include a base type-3 codebook, selecting the base type-3 codebook;

[0429] Selecting a type 3 codebook with the earliest triggering time from the multiple type 3 codebooks;

[0430] Selecting a type 3 codebook with the latest triggering time from the multiple type 3 codebooks;

[0431] Selecting a type 3 codebook having the earliest or latest start time of corresponding physical uplink control channel resources from the multiple type 3 codebooks;

[0432] Selecting a type 3 codebook having the earliest or latest end time of corresponding physical uplink control channel resources from the multiple type 3 codebooks;

[0433] Selecting a type 3 codebook having a minimum identifier or index of a corresponding physical uplink control channel resource from the multiple type 3 codebooks;

[0434] Selecting a type 3 codebook having a largest identifier or index of a corresponding physical uplink control channel resource from the multiple type 3 codebooks;

[0435] Selecting a type 3 codebook with the largest number of corresponding HARQ processes from the multiple type 3 codebooks;

[0436] Selecting a type 3 codebook with the least number of corresponding HARQ processes from the multiple type 3 codebooks;

[0437] Selecting a type 3 codebook with a largest codebook index or state index from the multiple type 3 codebooks;

[0438] A type 3 codebook with a smallest codebook index or state index is selected from the multiple type 3 codebooks.

[0439] In one embodiment of the present application, the first order is determined according to any one of the following:

[0440] The corresponding time sequence of triggering downlink control information;

[0441] The time sequence of physical uplink control channel resources carrying type 3 codebooks;

[0442] The size order of the identifiers or indexes of the physical uplink control channel resources carrying the type 3 codebook;

[0443] The size order of the codebook index or state index corresponding to the type 3 codebook.

[0444] In one embodiment of the present application, the first codebook determination method includes any one of the following:

[0445] Concatenate at least part of the one or more type 3 codebooks and other HARQ-ACK codebooks that require feedback end-to-end in the second order to obtain a composite codebook;

[0446] Direct feedback of the basic type 3 codebook.

[0447] In one embodiment of the present application, the second sequence includes:

[0448] The other HARQ-ACK codebooks are concatenated after the bit sequences corresponding to the one or more type 3 codebooks,

[0449] or,

[0450] The bit sequences corresponding to the one or more type 3 codebooks are concatenated after the other HARQ-ACK codebooks.

[0451] In one embodiment of the present application, the second order is determined according to any one of the following:

[0452] A first time sequence, where the first time sequence is the time when the downlink control information is triggered corresponding to the one or more type 3 codebooks, and the time when the downlink control information is triggered corresponding to other HARQ-ACK codebooks that need to be fed back;

[0453] A second time sequence, where the second time sequence is a time sequence of physical uplink control channel resources carrying the one or more type 3 codebooks and a time sequence of physical uplink control channel resources carrying other HARQ-ACK codebooks requiring feedback;

[0454] A first size order, where the first size order is the size order of identifiers or indexes of physical uplink control channel resources carrying the one or more type 3 codebooks, and identifiers or indexes of physical uplink control channel resources carrying other HARQ-ACK codebooks requiring feedback;

[0455] The second size order is the size order of the codebook index or state index corresponding to the one or more type 3 codebooks, and the codebook index or state index corresponding to other HARQ-ACK codebooks that need feedback.

[0456] In one embodiment of the present application, the second codebook determination method includes any one of the following:

[0457] Only type 3 codebook is transmitted;

[0458] Feedback only the other HARQ-ACK codebook;

[0459] Determine, according to the first rule, whether to feedback the type 3 codebook or to feedback the other HARQ-ACK codebook.

[0460] In one embodiment of the present application, the first rule includes any one of the following:

[0461] When the type 3 codebook includes all HARQ-ACK information in the other HARQ-ACK codebooks, only the type 3 codebook is fed back;

[0462] Determined according to the triggering time of the type 3 codebook and / or other HARQ-ACK codebooks;

[0463] Determined according to the start time or end time of the PUCCH resource carrying the type 3 codebook and / or other HARQ-ACK codebook;

[0464] Determined according to the identifier or index of the PUCCH resource carrying the type 3 codebook and / or other HARQ-ACK codebook;

[0465] Determined according to the number of HARQ processes of the type 3 codebook and / or other HARQ-ACK codebooks;

[0466] Determined according to the codebook index or state index corresponding to the type 3 codebook and / or other HARQ-ACK codebooks.

[0467] In one embodiment of the present application, the triggering time of the type 3 codebook and / or other HARQ-ACK codebooks is determined according to the order of triggering DCI.

[0468] In one embodiment of the present application, the device further comprises:

[0469] A second determining module is used to determine the physical layer priority corresponding to the target codebook;

[0470] A transmission module is configured to feed back the target codebook according to a first codebook feedback mode and a physical layer priority corresponding to the target codebook.

[0471] In one embodiment of the present application, the first codebook feedback mode includes any one of the following:

[0472] The codebook corresponding to each physical layer priority is processed separately. When there is time domain overlap in the transmission of codebooks corresponding to different physical layer priorities, only the target codebook with the higher physical layer priority is fed back.

[0473] Allow codebook multiplexing across physical layer priorities, or allow codebooks of different physical layer priorities to be transmitted in parallel;

[0474] Direct feedback based type 3 codebook.

[0475] In one embodiment of the present application, codebooks with different physical layer priorities are allowed to be transmitted in parallel, including:

[0476] The terminal transmits a target codebook corresponding to a high physical layer priority and a target codebook corresponding to a low physical layer priority on the PUCCH respectively;

[0477] or,

[0478] The terminal transmits a target codebook corresponding to a high physical layer priority on a PUCCH, and the terminal transmits a target codebook corresponding to a low physical layer priority on a PUSCH;

[0479] or,

[0480] The terminal transmits a target codebook corresponding to a low physical layer priority on a PUCCH, and the terminal transmits a target codebook corresponding to a high physical layer priority on a PUSCH.

[0481] In one embodiment of the present application, codebook multiplexing across physical layer priorities is allowed, including:

[0482] The terminal multiplexes target codebooks corresponding to different physical layer priorities, and carries the multiplexed codebook on one PUCCH for transmission.

[0483] In one embodiment of the present application, the device further comprises:

[0484] A processing module, configured to not expect the network side to trigger the terminal to feedback multiple type 3 codebooks within a single time unit; or not expect the network side to trigger the terminal to feedback the one or more type 3 codebooks and the other HARQ-ACK codebooks that need to be fed back within a single time unit;

[0485] The device provided in the embodiment of the present application can achieve Figure 2 The various processes implemented in the method embodiment shown achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0486] See also Figure 7 The embodiment of the present application provides a device for feeding back a codebook, which is applied to a network-side device. The device 700 includes:

[0487] A triggering module 701 is configured to trigger the terminal to feedback one or more type 3 codebooks in a single time unit, or a network-side device to trigger the terminal to feedback one or more type 3 codebooks and other HARQ-ACK codebooks that need to be fed back in a single time unit;

[0488] An acquisition module 702 is configured to acquire a target codebook fed back by the terminal, where the target codebook is determined by the terminal according to one or more type 3 codebooks, or according to one or more type 3 codebooks and other HARQ-ACK codebooks that need to be fed back.

[0489] In one embodiment of the present application, the multiple type 3 codebooks correspond to the same physical layer priority;

[0490] or,

[0491] The one or more type 3 codebooks and other HARQ-ACK codebooks requiring feedback correspond to the same physical layer priority;

[0492] or,

[0493] At least one of the one or more type 3 codebooks and / or other HARQ-ACK codebooks requiring feedback corresponds to a different physical layer priority than the other codebooks.

[0494] In one embodiment of the present application, the device further comprises:

[0495] The third determining module is configured to determine that the number of type 3 codebooks fed back by the terminal in a single time unit is one.

[0496] In one embodiment of the present application, the device further comprises:

[0497] The fourth determining module is configured to determine that the HARQ process corresponding to the type 3 codebook fed back by the terminal within a single time unit covers all HARQ processes corresponding to the other HARQ-ACK codebooks.

[0498] The device provided in the embodiment of the present application can achieve Figure 3 The various processes implemented in the method embodiment shown achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0499] An embodiment of the present application further provides a terminal, including a processor and a communication interface, wherein the processor is configured to determine a target codebook for feedback based on one or more type 3 codebooks, or based on one or more type 3 codebooks and other HARQ-ACK codebooks requiring feedback; wherein the one or more type 3 codebooks are triggered by the network side to require feedback from the terminal within a single time unit, or the one or more type 3 codebooks and other HARQ-ACK codebooks are triggered by the network side to require feedback from the terminal within a single time unit. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment are applicable to this terminal embodiment and can achieve the same technical effect.

[0500] Specifically, Figure 8To implement a hardware structure diagram of a terminal in an embodiment of the present application, the terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, and at least some of the components of the processor 810.

[0501] Those skilled in the art will understand that the terminal 800 may also include a power supply (such as a battery) to power each component, and the power supply may be logically connected to the processor 810 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. Figure 8 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0502] It should be understood that in an embodiment of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042, and the graphics processing unit 8041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 807 includes a touch panel 8061 and other input devices 8072. The touch panel 8061 is also called a touch screen. The touch panel 8061 may include two parts: a touch detection device and a touch controller. Other input devices 8072 may include but are not limited to a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0503] In this embodiment of the present application, the radio frequency unit 801 receives downlink data from the network-side device and transmits it to the processor 810 for processing. Furthermore, the radio frequency unit 801 transmits uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0504] The memory 809 can be used to store software programs or instructions and various data. The memory 809 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, at least one application program or instruction required for a function (such as a sound playback function, an image playback function, etc.). In addition, the memory 809 may include a high-speed random access memory and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0505] Processor 810 may include one or more processing units. Optionally, processor 810 may integrate an application processor and a modem processor. The application processor primarily processes the operating system, user interface, and application programs or instructions, while the modem processor primarily processes wireless communications, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 810.

[0506] In this embodiment of the present application, the processor 810 is configured to determine a target codebook for feedback according to one or more type 3 codebooks, or according to one or more type 3 codebooks and other HARQ-ACK codebooks that require feedback, wherein the one or more type 3 codebooks are triggered by the network side to require feedback by the terminal within a single time unit, or the one or more type 3 codebooks and other HARQ-ACK codebooks that require feedback are triggered by the network side to require feedback by the terminal within a single time unit.

[0507] The terminal provided in the embodiment of the present application can achieve Figure 2 The various processes implemented in the method embodiment shown achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0508] See also Figure 9 , the embodiment of the present application also provides a network side device. Figure 9As shown, network-side device 900 includes an antenna 901, a radio frequency device 902, and a baseband device 903. Antenna 901 is connected to radio frequency device 902. In the uplink direction, radio frequency device 902 receives information via antenna 901 and sends the received information to baseband device 903 for processing. In the downlink direction, baseband device 903 processes the information to be transmitted and sends it to radio frequency device 902. Radio frequency device 902 processes the received information and then sends it through antenna 901.

[0509] The frequency band processing device may be located in the baseband device 903 . The method performed by the network-side device in the above embodiment may be implemented in the baseband device 903 . The baseband device 903 includes a processor 904 and a memory 905 .

[0510] The baseband device 903 may include, for example, at least one baseband board on which a plurality of chips are arranged, such as Figure 8 As shown, one of the chips is, for example, a processor 904, which is connected to a memory 905 to call a program in the memory 905 and execute the network device operations shown in the above method embodiment.

[0511] The baseband device 903 may further include a network interface 906 for exchanging information with the radio frequency device 902 . The interface may be, for example, a common public radio interface (CPRI).

[0512] Specifically, the network side device in the embodiment of the present application also includes: instructions or programs stored in the memory 905 and executable on the processor 904 .

[0513] In one embodiment of the present application, the processor 904 is configured to trigger the terminal to feedback one or more type 3 codebooks in a single time unit, or the network side device triggers the terminal to feedback one or more type 3 codebooks and other HARQ-ACK codebooks that need to be fed back in a single time unit; obtain the target codebook fed back by the terminal, wherein the target codebook is determined by the terminal according to one or more type 3 codebooks, or according to one or more type 3 codebooks and other HARQ-ACK codebooks that need to be fed back.

[0514] It is understood that the processor 904 calls the instructions or programs in the memory 905 to execute Figure 7 The methods executed by the modules shown achieve the same technical effects, so they will not be described here to avoid repetition.

[0515] Optional, such as Figure 10As shown, the embodiment of the present application further provides a communication device 1000, including a processor 1001, a memory 1002, and a program or instruction stored in the memory 1002 and executable on the processor 1001. For example, when the communication device 1000 is a terminal, the program or instruction is executed by the processor 1001 to implement the above Figure 2 When the communication device 1000 is a network side device, the program or instruction is executed by the processor 1001 to implement the above Figure 3 The various processes of the method embodiments can achieve the same technical effects, and to avoid repetition, they will not be described here.

[0516] The embodiment of the present application further provides a computer program / program product, which is stored in a non-volatile storage medium and is executed by at least one processor to implement the following Figure 2 or Figure 3 The steps of the processing method.

[0517] The embodiment of the present application also provides a readable storage medium on which a program or instruction is stored, and when the program or instruction is executed by the processor, the above Figure 2 or Figure 3 The various processes of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described here.

[0518] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0519] The embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the above Figure 2 The various processes of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described here.

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

[0521] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device comprising a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0522] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0523] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A method for feeding back a codebook, characterized in that: include: When the network side triggers the terminal to feedback a type 3 codebook and other hybrid automatic repeat request response HARQ-ACK codebooks within a single time unit, the terminal determines that the type of the target HARQ-ACK to be fed back is the type 3 codebook according to the codebook determination mode for feeding back only the type 3 codebook; If the type of the target HARQ-ACK is a type 3 codebook, the terminal determines a target codebook for feedback according to the type 3 codebook and the other HARQ-ACK codebooks; The HARQ process corresponding to the type 3 codebook covers the HARQ processes corresponding to the other HARQ-ACK codebooks.

2. The method according to claim 1, characterized in that The type 3 codebook and the other HARQ-ACK codebooks correspond to the same physical layer priority; or, At least one of the type 3 codebook and the other HARQ-ACK codebooks corresponds to a different physical layer priority than the other codebooks.

3. The method according to claim 1, characterized in that The state corresponding to the type 3 codebook is included in the state list configured on the network side.

4. The method according to claim 1, wherein The type 3 codebook includes: a basic type 3 codebook and / or an enhanced type 3 codebook.

5. The method according to claim 1, wherein The method further comprises: The terminal determines the physical layer priority corresponding to the target codebook; The terminal feeds back the target codebook according to the first codebook feedback mode and the physical layer priority corresponding to the target codebook.

6. The method according to claim 5, characterized in that The first codebook feedback mode includes any one of the following: The codebook corresponding to each physical layer priority is processed separately. When there is time domain overlap in the transmission of codebooks corresponding to different physical layer priorities, only the target codebook with the higher physical layer priority is fed back. Allow codebook multiplexing across physical layer priorities, or allow codebooks corresponding to different physical layer priorities to be transmitted in parallel; Direct feedback of the basic type 3 codebook.

7. The method according to claim 6, characterized in that Allows parallel transmission of HARQ-ACK codebooks with different physical layer priorities, including: The terminal transmits a target codebook corresponding to a high physical layer priority and a target codebook corresponding to a low physical layer priority on the PUCCH respectively; or, The terminal transmits a target codebook corresponding to a high physical layer priority on a PUCCH, and the terminal transmits a target codebook corresponding to a low physical layer priority on a PUSCH; or, The terminal transmits a target codebook corresponding to a low physical layer priority on a PUCCH, and the terminal transmits a target codebook corresponding to a high physical layer priority on a PUSCH.

8. The method according to claim 6, characterized in that Allows codebook reuse across physical layer priorities, including: The terminal multiplexes target codebooks corresponding to different physical layer priorities, and carries the multiplexed codebook on one PUCCH for transmission.

9. The method according to claim 1, characterized in that The method further comprises: The terminal does not expect the network side to trigger the terminal to feed back multiple type 3 codebooks within a single time unit.

10. A method for feeding back a codebook, characterized in that: include: The network-side device triggers the terminal to feedback a type 3 codebook and other HARQ-ACK codebooks in a single time unit; The network-side device obtains a target codebook fed back by the terminal, wherein the target codebook is a type 3 codebook; The HARQ process corresponding to the type 3 codebook covers the HARQ processes corresponding to the other HARQ-ACK codebooks.

11. The method according to claim 10, characterized in that The type 3 codebook and the other HARQ-ACK codebooks correspond to the same physical layer priority; or, At least one of the type 3 codebook and the other HARQ-ACK codebooks corresponds to a different physical layer priority than the other codebooks.

12. A device for feeding back a codebook, characterized in that: include: A first determining module is configured to, when the network side triggers the terminal to feedback a type 3 codebook and other hybrid automatic repeat request answer HARQ-ACK codebooks within a single time unit, determine, by the terminal, according to a codebook determination mode for feeding back only the type 3 codebook, that the type of the target HARQ-ACK to be fed back is a type 3 codebook; if the type of the target HARQ-ACK is a type 3 codebook, determine the target codebook to be fed back according to the type 3 codebook and the other HARQ-ACK codebooks that need to be fed back; The HARQ process corresponding to the type 3 codebook covers the HARQ processes corresponding to the other HARQ-ACK codebooks.

13. The device according to claim 12, characterized in that The first determining module is further configured to: Determine the target HARQ-ACK to be fed back according to the first codebook determination method, the one or more type 3 codebooks, and other HARQ-ACK codebooks that require feedback; or, Determining a target HARQ-ACK type for feedback according to the second codebook determination method; If the type of the target HARQ-ACK is a type 3 codebook, determining the target codebook to be fed back according to the one or more type 3 codebooks; If the type of the target HARQ-ACK is the type corresponding to the other HARQ-ACK codebook, determining the target codebook to be fed back according to the other HARQ-ACK codebook.

14. The device according to claim 13, characterized in that The first determining module is further configured to: When the network side triggers the terminal to feedback a type 3 codebook within a single time unit, determining to feedback the type 3 codebook; or, When the network side triggers the terminal to feed back multiple type 3 codebooks within a single time unit, the target codebook to be fed back is determined according to the third codebook determination method.

15. The device according to claim 12, characterized in that The device further comprises: A second determining module is used to determine the physical layer priority corresponding to the target codebook; A transmission module is configured to feed back the target codebook according to a first codebook feedback mode and a physical layer priority corresponding to the target codebook.

16. The device according to claim 12, characterized in that The device further comprises: The processing module is configured to not expect the network side to trigger the terminal to feed back multiple type 3 codebooks within a single time unit.

17. A device for feeding back a codebook, characterized in that: include: A triggering module, configured to trigger the terminal to feed back a type 3 codebook and other HARQ-ACK codebooks in a single time unit; an acquisition module, configured to acquire a target codebook fed back by the terminal, wherein the target codebook is a type 3 codebook; The HARQ process corresponding to the type 3 codebook covers the HARQ processes corresponding to the other HARQ-ACK codebooks.

18. The device according to claim 17, characterized in that The device further comprises: A third determining module is configured to determine that the number of type 3 codebooks fed back by the terminal in a single time unit is one; or, The fourth determining module is configured to determine that the HARQ process corresponding to the type 3 codebook fed back by the terminal within a single time unit includes all HARQ processes of the other HARQ-ACK codebooks.

19. A terminal, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program implements the steps of the method according to any one of claims 1 to 9 when executed by the processor.

20. A network side device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the method according to any one of claims 10 to 11 are implemented.

21. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.

Images