System and method for providing feedback information

Abstract

In various arrangements, a user equipment (UE) receives at least one of a first scheduling indicator and a second scheduling indicator. Each of the first scheduling indicators schedules a transmission. The transmission scheduled by each of the first scheduling indicators is a first transmission type or a second transmission type. Each of the second scheduling indicators schedules two or more transmissions. Each transmission scheduled by the second scheduling indicator is a first transmission type or a second transmission type. The UE generates one or more subcodebooks according to one or more of the first scheduling indicator, the second scheduling indicator, the first transmission type, and the second transmission type. The UE generates a codebook by combining the one or more generated subcodebooks.

Description

Technical Field

[0001] The present disclosure relates to the field of telecommunications, and in particular, to generating a codebook when providing feedback information. Background Art

[0002] Downlink (DL) data scheduling features of new radio (NR) radio access technology (RAT) systems may include scheduling more than one DL data resources (e.g., more than one physical downlink shared channels (PDSCHs)) through one DL control resource (e.g., a single physical DL control channel (PDCCH)). Summary of the invention

[0003] The example embodiments disclosed herein are intended to solve problems associated with one or more problems presented in the prior art, as well as to provide additional features that will become apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and are not restrictive, and it will be apparent to those of ordinary skill in the art who read this disclosure that various modifications to the disclosed embodiments may be made while remaining within the scope of this disclosure.

[0004] In some arrangements, a wireless communication method includes: receiving, by a wireless communication device, at least one of (1) a first scheduling indicator and (2) a second scheduling indicator from a base station. Each of the first scheduling indicators schedules a transmission. Each of the second scheduling indicators schedules two or more transmissions. The wireless communication device generates at least one of a first subcodebook and a second subcodebook. The first subcodebook includes one or more first feedback bits, the one or more first feedback bits indicating a reception status of the transmission scheduled by each first scheduling indicator. The second subcodebook includes a second feedback bit, the second feedback bit indicating a reception status of the transmission scheduled by each second scheduling indicator. The wireless communication device generates a codebook by combining the first subcodebook and the second subcodebook.

[0005] In some arrangements, a wireless communication method includes: sending, by a base station, at least one of (1) a first scheduling indicator and (2) a second scheduling indicator to a wireless communication device. Each of the first scheduling indicators schedules one transmission. Each of the second scheduling indicators schedules two or more transmissions. The base station receives a codebook generated based on at least one of a first subcodebook and a second subcodebook from the wireless communication device. The first subcodebook includes a first feedback bit, the first feedback bit indicating a reception status of a transmission scheduled by each first scheduling indicator. The second subcodebook includes a second feedback bit, the second feedback bit indicating a reception status of a transmission scheduled by each second scheduling indicator. The base station determines, based on the codebook, a reception status of a transmission scheduled by each first scheduling indicator and a reception status of a transmission scheduled by each second scheduling indicator.

[0006] In some arrangements, a wireless communication method includes: receiving, by a wireless communication device, at least one of (1) a first scheduling indicator and (2) a second scheduling indicator from a base station. Each of the first scheduling indicators schedules a transmission. The transmission scheduled by each of the first scheduling indicators is a first transmission type or a second transmission type. Each of the second scheduling indicators schedules two or more transmissions. Each of the two or more transmissions scheduled by each of the second scheduling indicators is a first transmission type or a second transmission type. The wireless communication device generates one or more sub-codebooks based on one or more of the first scheduling indicator, the second scheduling indicator, the first transmission type, and the second transmission type. The wireless communication device generates a codebook by combining the generated one or more sub-codebooks.

[0007] In some arrangements, a wireless communication method includes: sending, by a base station, at least one of (1) a first scheduling indicator and (2) a second scheduling indicator to a wireless communication device. Each of the first scheduling indicators schedules a transmission. The transmission scheduled by each first scheduling indicator is a first transmission type or a second transmission type. Each second scheduling indicator schedules two or more transmissions. Each of the two or more transmissions scheduled by each second scheduling indicator is a first transmission type or a second transmission type. The base station receives, from the wireless communication device, a codebook generated based on one or more sub-codebooks generated by the wireless communication device according to the first scheduling indicator, the second scheduling indicator, the first transmission type, and the second transmission type. The base station determines, based on the codebook, a reception state of the transmission scheduled by each first scheduling indicator and a reception state of the transmission scheduled by each second scheduling indicator.

[0008] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Various example embodiments of the present solution are described in detail below with reference to the accompanying drawings or drawings. The drawings are provided for illustrative purposes only and depict only example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the breadth, scope or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

[0010] Figure 1 is a flow chart illustrating an example method for managing feedback according to various arrangements of the present disclosure.

[0011] Figure 2 is a diagram illustrating a feedback mechanism according to various arrangements of the present disclosure.

[0012] Figure 3 is a diagram illustrating a feedback mechanism according to various arrangements of the present disclosure.

[0013] Figure 4 is a table showing the number of feedback bits corresponding to each DAI count of different subcodebooks according to various arrangements of the present disclosure.

[0014] Figure 5 is a table showing the number of feedback bits corresponding to each DAI count of different subcodebooks according to various arrangements of the present disclosure.

[0015] Figure 6 is a flow chart illustrating an example method for managing feedback according to various arrangements of the present disclosure.

[0016] Fig. 7A A block diagram illustrating an example base station according to some embodiments of the present disclosure; and

[0017] Figure 7B A block diagram of an example UE according to some embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0018] Various example embodiments of the present solution are described below with reference to the accompanying drawings so that a person of ordinary skill in the art can make and use the present solution. As will be apparent to a person of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein may be made without departing from the scope of the present solution. Therefore, the present solution is not limited to the example embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be rearranged while still remaining within the scope of the present solution. Therefore, a person of ordinary skill in the art should understand that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.

[0019] In some conventional wireless communication systems, a base station may schedule a single PDSCH using downlink control information (DCI) of a PDCCH. Each PDSCH may be used by a base station to transmit at least one (e.g., one or two) transport blocks (TBs) or multiple code block groups (CBGs). A user equipment (UE) (e.g., a terminal) may provide feedback (e.g., feedback bits) for the reception status of at least one TB or CBG. For multiple feedback bits of a UE corresponding to the same uplink (UL) time slot, the UE aggregates the multiple feedback bits into a feedback codebook and sends the feedback codebook to the base station in the UL time slot, for example, on UL feedback resources such as, but not limited to, a physical UL control channel (PUCCH), a physical UL shared channel (PUSCH), etc. The UE may conventionally generate two types of feedback codebooks (semi-static codebooks and dynamic codebooks).

[0020] When generating a semi-static codebook, for a DL transmission resource corresponding to (mapped to or associated with) a UL feedback resource, feedback information is generated regardless of whether the base station has scheduled transmission on the DL transmission resource. Therefore, when generating a semi-static codebook, misalignment between the UE and the base station in "feedback codebook size" and "mapping relationship between feedback bits and downlink transmission" can be avoided. Feedback bits in a semi-static feedback codebook may be wasted because, in this codebook generation mode, some feedback bits corresponding to some DL transmission resources are useless because those DL transmission resources are not scheduled for DL ​​transmission of the UE.

[0021] In generating a dynamic codebook, a downlink allocation index (DAI) field is introduced into the scheduling DCI. DCI is carried on the PDCCH and is used to schedule DL or UL transmission. In some examples, DAI includes a counting DAI (e.g., a counter DAI (C-DAI)) and a total DAI (T-DAI). C-DAI indicates the index of the PDSCH that needs to be fed back in the same feedback codebook until the current DCI. The position of the feedback bit corresponding to the DL transmission scheduled by the DCI in the feedback codebook can be determined according to the C-DAI. T-DAI indicates the total number of PDSCHs that need to be fed back in the same feedback codebook until the current PDCCH monitoring time, which can be defined by the current monitoring opportunity (MO). In non-carrier aggregation mode, only the C-DAI domain or field can be included in the DCI. By counting the DL data on the same UL feedback resource, each bit in the dynamic feedback codebook corresponds to an actually scheduled DL data, thereby effectively saving feedback overhead. However, the introduction of the DAI indication domain also increases the overhead of the DCI.

[0022] In a conventional wireless communication system, one DCI carried on a PDCCH can only schedule one PDSCH. In self-scheduling, the PDSCH and DCI can be located in the same carrier (also known as component carrier (CC) or cell). In cross-carrier scheduling, the PDSCH and DCI can also be located on different carriers.

[0023] The following briefly describes the traditional dynamic codebook generation and feedback method for the context. Three DCIs (DCI1-3) are included in the first MO (e.g., MO1, starting from the starting point of time slot n), and two DCIs (DCI4, 5) are included in the second MO (e.g., MO2, starting from the starting point of time slot n+1). The feedback information of the PDSCH scheduled by these DCIs is provided in time slot n+7 according to the feedback timing indicated in the DCI. The UE multiplexes the feedback information into the feedback codebook. Specifically, DCI1 is located on CC3, and the scheduled PDSCH is located in time slot n+4 on CC3. DCI2 is located on CC4, and the scheduled PDSCH is located in time slot n+3 on CC4. DCI3 is located on CC5, and the scheduled PDSCH is located in time slot n+3 on CC2. DCI4 is located on CC3, and the scheduled PDSCH is located in time slot n+5 on CC3. DCI5 is on CC5 and the scheduled PDSCH is in slot n+4 on CC2.

[0024] The C-DAI within the DCI is counted in the following order. First, the C-DAI is sorted according to the timing of the MO. The DCI within the same MO is further sorted from low to high according to the carrier index where the PDSCH is scheduled. Given that DCI can only schedule one PDSCH, C-DAI can be regarded as a count of DCI as well as a PDSCH count.

[0025] Specifically, the count of PDSCH scheduled by DCI in MO1 precedes the count of PDSCH scheduled by DCI in MO2. MO1 contains three DCIs. According to the carrier index of the PDSCH scheduled by each DCI, the PDSCH scheduled by DCI3 is counted first because it is located on the carrier with the lowest index (e.g. CC2), followed by DCI1 and DCI2. C-DAI adopts a counting method with a period of 4. That is, after counting to 4, the C-DAI of the next DL transmission is marked as 1. For T-DAI, the DCI within the same MO contains a T-DAI with the same value, which is used to indicate the total number of PDSCHs for which feedback needs to be provided in the same feedback codebook until the current MO. T-DAI also adopts a counting method with a period of 4. Therefore:

[0026] {c-DAI, T-DAI}={1, 3} in DCI3;

[0027] {c-DAI, T-DAI} in DCI1 = {2, 3}; and

[0028] {c-DAI, T-DAI}={3, 3} in DCI2.

[0029] Correspondingly, the first three bits in the feedback codebook correspond to the PDSCHs scheduled by DCI3, DCI1 and DCI2 in this order, respectively.

[0030] In addition, the PDSCH scheduled by DCI in the next MO (MO2) is counted in a similar manner:

[0031] {c-DAI, T-DAI}={4, 1} in DCI5; and

[0032] {c-DAI, T-DAI}={1, 1} in DCI4.

[0033] Correspondingly, the 4th bit and the 5th bit in the feedback codebook correspond to the PDSCH scheduled by DCI5 and DCI4 in this order, respectively.

[0034] It is worth noting that, since C-DAI uses a counting method with a period of 4, for the fifth PDSCH (that is, the PDSCH scheduled by DCI4), C-DAI = 1. Since T-DAI also uses a counting method with a period of 4, a total of 5 PDSCHs are scheduled until MO2. Therefore, T-DAI in the DCI within MO2 is 1.

[0035] In some examples, in response to determining that all PDSCHs are correctly received, the feedback codebook is "11111." When one or more DCIs are lost or the PDSCH is not correctly received, the corresponding bits in the feedback codebook are set to 0.

[0036] If some carriers are configured for CBG transmission (for example, using RRC signaling "maxCodeBlockGroupsPerTransportBlock" to indicate that the TB is split into up to M CBGs), the feedback information of the PDSCH scheduled on these carriers by DCI format other than DCI format 1_0 (for example, DCI format 1_1 or DCI format 1_2) forms a subcodebook, which can be called a CBG subcodebook.

[0037] In some examples, the UE may form another subcodebook for the PDSCH on a carrier that is not configured with CBG transmission and for the PDSCH on a carrier that is configured for CBG transmission but scheduled via DCI format 1_0. This subcodebook is called a "TB subcodebook". The CBG subcodebook and the TB subcodebook are counted separately to determine the order of the feedback bits and the size of the subcodebook. The UE uses the two subcodebooks to generate the final feedback codebook in a predefined order (which is specified in the specification or configured by signaling) by performing bit concatenation. For example, the bit in the TB subcodebook is the first bit, and the bit in the CBG subcodebook is the second bit.

[0038] Each bit in the TB subcodebook corresponds to one TB, and each DAI count corresponds to 1 bit. Each bit in the CBG subcodebook corresponds to one CBG, and each DAI count corresponds to the number of bits in the maximum number of CBGs (which can be configured via RRC signaling "maxCodeBlockGroupsPerTransportBlock").

[0039] Various arrangements disclosed herein relate to systems, methods, and non-transitory computer-readable media for constructing a DAI field in a DCI and generating a dynamic feedback codebook when more than one DL data resource (e.g., more than one PDSCH) is scheduled by one DL control resource (e.g., a single PDCCH). A DCI that can only schedule one PDSCH is referred to as a type 1 DCI (a first type of DCI), while a DCI that can schedule more than one PDSCH is referred to as a type 2 DCI (a second type of DCI). Although two PDSCHs scheduled by the same DCI are described in the examples herein for simplicity, similar mechanisms can be used for scenarios in which more than two PDSCHs are scheduled by the same DCI. The PDSCHs scheduled by the same DCI may be located in different carriers (CCs) or on different time domain resources of the same carrier (CC).

[0040] In some arrangements, the feedback mechanism described herein supports multiple PDSCHs scheduled by DCI by providing multiple PDSCHs to share the C-DAI / T-DAI indicator field within the DCI and generate a corresponding dynamic codebook. This feedback mechanism allows for improved consistency in the bit order and size of the feedback codebook in coordination between the UE and the base station, thereby saving the bit overhead of the DAI field in the DCI. In addition, the feedback mechanism described herein can minimize the impact of DCI loss on codebook reliability by independently counting PDSCHs scheduled by different DCI types.

[0041] Some arrangements involve indicating DAI in type 2 DCI and generating dynamic codebook generation. For example, the PDSCH scheduled by type 2 DCI and type 1 DCI are counted independently. The UE can generate sub-codebooks for type 2 DCI and type 1 DCI scheduled by PDSCH, respectively. Then, the UE generates the final feedback codebook by cascading the bits of the two sub-codebooks. At this time, regardless of the type of DCI, there is only one set of C-DAI and T-DAI in the DCI. In other words, one C-DAI and one T-DAI are in type 1 DCI, and one C-DA and one T-DAI are in type 2 DCI. The C-DAI and T-DAI in type 2 DCI can be counted according to the DCI, and the value of each DAI will correspond to the number of bits X in the feedback sub-codebook. In some arrangements, X is determined based on the number of PDSCHs scheduled by a type 2 DCI. In one example, X is equal to the number of PDSCHs scheduled in type 2 DCI. In another example, the number of PDSCHs scheduled by different Type-2DCIs is different, and X is equal to the maximum number of PDSCHs scheduled by different Type-2DCIs.

[0042] In some examples where the maximum number of PDSCHs scheduled by a type 2 DCI is 2 (e.g., which may be defined in the specification), the DAI value in the type 2 DCI corresponds to 2 bits in a subcodebook (e.g., a second subcodebook). The DAI value in each type 1 DCI corresponds to 1 bit in a subcodebook (e.g., a first subcodebook).

[0043] The UE may combine the first subcodebook and the second subcodebook by bit concatenation to form a feedback codebook. In one example, the feedback bits of the first subcodebook precede the feedback bits of the second subcodebook in the bit concatenation. In another example, the feedback bits of the second subcodebook precede the feedback bits of the first subcodebook in the bit concatenation.

[0044] Figure 1 is a flow chart illustrating example methods 100a and 100b for managing feedback according to various arrangements of the present disclosure. Figure 1 , method 100a is performed by a UE, and method 100b corresponds to method 100a and is performed by a base station.

[0045] At 102b, the base station sends at least one of (1) a first scheduling indicator (e.g., one or more type 1 DCIs) and (2) a second scheduling indicator (e.g., one or more type 2 DCIs) to the UE. Each first scheduling indicator schedules one transmission (e.g., one PDSCH). Each second scheduling indicator schedules two or more transmissions (e.g., multiple PDSCHs). At 102a, the UE receives at least one of the first scheduling indicator and the second scheduling indicator from the base station. Each first scheduling indicator schedules one transmission. Each second scheduling indicator schedules two or more transmissions.

[0046] At 104a, the UE generates at least one of a first subcodebook and a second subcodebook. The first subcodebook includes one or more first feedback bits, and the one or more first feedback bits indicate a reception status of a transmission scheduled by each first scheduling indicator. The second subcodebook includes a second feedback bit. The second feedback bit indicates a reception status of a transmission scheduled by each second scheduling indicator.

[0047] In some examples, each first scheduling indicator includes a first index that identifies a bit in the first subcodebook corresponding to a reception state of a transmission scheduled by each first scheduling indicator. Each second scheduling indicator includes a second index that identifies a bit in the second subcodebook corresponding to a reception state of a transmission scheduled by each second scheduling indicator. The first index of the first scheduling indicator is counted independently of the second index of the second scheduling indicator.

[0048] In some examples, the first scheduling indicator and each second scheduling indicator are DCI. Each transmission referred to is a PDSCH, which the UE uses to receive downlink data from the base station. Each of the first index and the second index is a DAI. The DAI in each second scheduling indicator includes a C-DAI and a T-DAI. Each count of a C-DAI or a T-DAI corresponds to the number of bits in the second subcodebook. The number of bits is based on the number of two or more transmissions scheduled by each second scheduling indicator.

[0049] In some arrangements, such as reference Figure 2 In further detail, the C-DAI in each second scheduling indicator is determined based on a carrier index (CC) of each of the two or more transmissions scheduled by each second scheduling indicator. The second feedback bits are arranged according to the C-DAI of each second scheduling indicator. One of the two or more transmissions is a transmission on a carrier having a lower carrier index than any other of the two or more transmissions. Alternatively, one of the two or more transmissions is a transmission on a carrier having a higher carrier index than any other of the two or more transmissions.

[0050] In some arrangements, such as reference Figure 3 As described in further detail, the C-DAI of each second scheduling indicator is determined based on the carrier index of each second scheduling indicator. The second feedback bits are arranged according to the C-DAI of each second scheduling indicator.

[0051] In some arrangements, the second feedback bits corresponding to two or more transmissions scheduled by the second scheduling indicator are consecutive in the codebook.

[0052] In some examples, such as reference Figure 4Discussed in further detail, the first subcodebook includes at least one of two first subcodebooks. The first of the first subcodebooks includes feedback bits corresponding to a first type of transmission (e.g., CBG) scheduled by the first of the first scheduling indicators. The second of the first subcodebooks includes feedback bits corresponding to a second type of transmission (e.g., TB) scheduled by the second of the first scheduling indicators. The second subcodebook includes at least one of two second subcodebooks. The first of the second subcodebooks includes feedback bits corresponding to a first type of transmission (CBG) scheduled by the first of the second scheduling indicators. The second of the second subcodebooks includes feedback bits corresponding to a second type of transmission (TB) scheduled by the second of the second scheduling indicators. In some examples, generating the codebook includes merging the first subcodebook and the second subcodebook by bit-concatenating the first subcodebook and the second subcodebook according to the first transmission type, the second transmission type, the first scheduling indicator, and the second scheduling indicator.

[0053] In some examples, two or more of the first subcodebook and the second subcodebook (e.g., a total of 4 subcodebooks) may be merged to form a merged subcodebook. For example, the method further includes generating a merged subcodebook by merging feedback bits of two or more of the first subcodebook and the second subcodebook. The feedback bits of two or more of the first subcodebook and the second subcodebook are merged based on the scheduling mode. That is, the transmissions scheduled by the scheduling indicator in two or more scheduling modes are counted together. The merged subcodebook includes feedback bits from two or more scheduling modes. Each of the scheduling modes is one of the first scheduling indicators for scheduling a first type of transmission, one of the first scheduling indicators for scheduling a second type of transmission, one of the second scheduling indicators for scheduling a first type of transmission, or one of the second scheduling indicators for scheduling a second type of transmission.

[0054] In some examples, the number of feedback bits of the merged subcodebook corresponding to the DAI count is determined based on a first number of feedback bits used to provide feedback information to the first of two or more scheduling modes. The first number of feedback bits is greater than the second number of feedback bits used to provide feedback information to any other of the two or more scheduling modes. The DAI count in any other of the two or more scheduling modes corresponds to the first number of feedback bits in the merged subcodebook. The first number of feedback bits corresponding to any other of the two or more scheduling modes includes the second number of feedback bits and padding bits. The padding bits include zero or the first number of repeated feedback bits.

[0055] In some examples, such as reference Figure 5Discussed in further detail, the first subcodebook includes at least one of two first subcodebooks. The first of the first subcodebooks includes feedback bits corresponding to a first type of transmission scheduled by a first of the first scheduling indicators. The second of the first subcodebooks includes feedback bits corresponding to a second type of transmission scheduled by a second of the first scheduling indicators. The second subcodebook includes at least one of three subcodebooks. The first of the second subcodebooks includes feedback bits corresponding to a first type of transmission scheduled by a first of the second scheduling indicators. The second of the second subcodebooks includes feedback bits corresponding to a second type of transmission scheduled by a second of the second scheduling indicators. The third of the second subcodebooks includes feedback bits corresponding to a first type of transmission and a second type of transmission scheduled by a third of the second scheduling indicators. In some examples, generating the codebook includes merging the first subcodebook and the second subcodebook by concatenating bits of the first subcodebook and the second subcodebook according to the first transmission type, the second transmission type, the first scheduling indicator, and the second scheduling indicator.

[0056] In some examples, two or more of the first subcodebook and the second subcodebook (e.g., a total of 5 subcodebooks) may be merged to form a merged subcodebook. For example, the method further includes: generating a merged subcodebook by merging feedback bits of two or more of the first subcodebook and the second subcodebook. Merge two or more feedback bits of the first subcodebook and the second subcodebook based on the scheduling mode. That is, the transmissions scheduled by the scheduling indicator in two or more scheduling modes are counted together. The merged subcodebook includes feedback from two or more scheduling modes. Each of the scheduling modes is one of the first scheduling indicators for scheduling a first type of transmission, one of the first scheduling indicators for scheduling a second type of transmission, one of the second scheduling indicators for scheduling a first type of transmission, one of the second scheduling indicators for scheduling a second type of transmission, or one of the second scheduling indicators for scheduling a first type of transmission and a second type of transmission.

[0057] In some examples, the number of feedback bits of the merged subcodebook corresponding to the DAI count is determined according to a first number of feedback bits for providing feedback information to the first of two or more scheduling modes. The first number of feedback bits is greater than the second number of feedback bits for providing feedback information to any other of the two or more scheduling modes. Any other of the two or more scheduling modes corresponds to the first number of feedback bits in the merged subcodebook. The first number of feedback bits corresponding to any other of the two or more scheduling modes includes the second number of feedback bits and padding bits. The padding bits include zeros or repetitions of the first number of feedback bits.

[0058] At 106a, the UE generates a codebook by combining the first subcodebook and the second subcodebook. In some examples, the codebook is generated by concatenating or cascading bits in the first subcodebook and the second subcodebook (each of which may refer to multiple subcodebooks) in an appropriate order, as disclosed herein.

[0059] At 108a, the UE sends a codebook to the base station. At 104b, the base station receives a codebook generated based on at least one of the first subcodebook and the second subcodebook from the UE. As described, the first subcodebook includes a first feedback bit that indicates a reception status of a transmission scheduled by each first scheduling indicator. The second subcodebook includes a second feedback bit that indicates a reception status of a transmission scheduled by each second scheduling indicator.

[0060] At 106b, the base station determines a reception status of a transmission scheduled by each first scheduling indicator and a reception status of a transmission scheduled by each second scheduling indicator based on the codebook.

[0061] Figure 2 is a diagram illustrating a feedback mechanism 200 according to various arrangements. Figure 3 is a diagram illustrating a feedback mechanism 300 according to various arrangements. Figure 2 and Figure 3 A scenario in which type 2 DCI is introduced is shown. The UE can receive data from and send data to the base station via a CC group of 6 CCs (e.g., CC1-CC6). 9 time slots are shown for each CC, including time slot n, time slot n+1, time slot n+2, time slot n+3, time slot n+4, time slot n+5, time slot n+6, time slot n+7, and time slot n+8. The UE can monitor any DCI in MO (e.g., MO1) in time slot n. Although Figure 2 and Figure 3 An example is shown where DCIs 202, 204, 206, and 208 are all in the same MO in different CCs, but a similar feedback mechanism may be implemented for DCIs in different MOs.

[0062] As shown in the figure, the UE receives 4 DCIs (e.g., DCI 202, DCI 204, DCI 206, and DCI 208) from the base station in the same MO, which correspond to the starting point of time slot n. Two type 1 DCIs 202 and 208 are on CC6 and CC1, respectively. DCI 202 schedules PDSCH 211 in time slot n+3 of CC6 in self-scheduling. DCI 208 schedules PDSCH 216 in time slot n+3 of CC1 in self-scheduling. The UE can generate a subcodebook for providing feedback information on whether the data on PDSCH 211 (scheduled by DCI 202) and PDSCH 216 (scheduled by DCI 208) is correctly received. In other words, a subcodebook is generated for PDSCH 211 and 216 scheduled by all type 1 DCIs 202 and 208 corresponding to the same UL time slot n+7. In some examples, the C-DAI of the type 1 DCI 208 in CC1 is marked as 1, while the C-DAI of the type 1 DCI 202 in CC6 is marked as 2. In this MO, the T-DAI in the type 1 DCIs 202 and 208 is marked as 2.

[0063] As shown in the figure, two type 2 DCIs 204 and 206 are on CC5 and CC4, respectively. DCI 204 schedules PDSCH 212 in slot n+3 of CC5 in self-scheduling, and schedules PDSCH 215 in slot n+3 of CC2 in cross-carrier scheduling. DCI 206 schedules PDSCH 213 in slot n+3 of CC4 in self-scheduling, and schedules PDSCH 214 in slot n+3 of CC3 in cross-carrier scheduling. The UE may generate a subcodebook for providing feedback information on whether data on PDSCH 212 and 215 (scheduled by DCI 204) and PDSCH 213 and 214 (scheduled by DCI 206) is correctly received. In other words, one subcodebook is generated for all PDSCHs 212-215 scheduled by type 2 DCIs 204 and 206 corresponding to the same UL slot n+7.

[0064] Various methods may be employed to determine the C-DAI in each of the Type 2 DCIs 204 and 206, including at least a first method and a second method.

[0065] In a first method corresponding to feedback mechanism 200, the UE selects one of the PDSCHs scheduled by each type 2 DCI as a reference to determine the C-DAI for each type 2 DCI. In some examples, the UE may select the PDSCH with the lowest CC index as a reference for each type 2 DCI. In some arrangements, the method of selecting a reference PDSCH for each type 2 DCI may be predefined by a specification or configured by radio resource control (RRC) signaling received from a base station.

[0066] Referring to the feedback mechanism 200, for example, among the PDSCHs 213 and 214 scheduled by the type 2 DCI 206, the PDSCH 214 on CC3 is selected as a reference because the PDSCH 214 has the lowest CC index. Among the PDSCHs 212 and 215 scheduled by the type 2 DCI 204, the PDSCH 215 on CC2 is selected as a reference because the PDSCH 215 has the lowest CC index. The reference PDSCHs 212 and 215 are then sorted according to an appropriate order (e.g., according to the index of the CC where the reference PDSCHs 214 and 215 are located, from low to high), and then the value of the C-DAI field in the type 2 DCIs 204 and 206 is determined based on the sorted order. For example, the C-DAI of the type 2 DCI of the PDSCH with the lowest CC index is set to a predetermined value (e.g., the lowest value such as 1), and the C-DAI of the type 2 DCI of the PDSCH with the second lowest CC index is set to another predetermined value (e.g., the second lowest value such as 2). As shown, the C-DAI in the type 2 DCI 204 and the C-DAI in the type 2 DCI 206 are 1 and 2, respectively. The value of the T-DAI in both type 2 DCIs is 2.

[0067] In some arrangements, after determining the values ​​of C-DAI and T-DAI in each type 2 DCI according to the first method, the codebook can be determined accordingly. As shown in the feedback mechanism 200, the codebook 220 contains the same number of bits (e.g., 6 bits) as the number of PDSCHs 211-216 scheduled by the DCIs 202, 204, 206, and 208, assuming that all are TB transmissions and two codewords are not configured. The first bit of codebook 220 corresponds to the reception status of PDSCH 216 in CC1, the second bit of codebook 220 corresponds to the reception status of PDSCH 211 in CC6, the third bit and the fourth bit of codebook 220 respectively correspond to the reception status of two PDSCHs 212 and 215 scheduled by type 2DCI 204 in CC5 (the reception status of PDSCH 215 in CC2 corresponds to the third bit, and the reception status of PDSCH 212 in CC5 corresponds to the fourth bit), and the 5th bit and the 6th bit of codebook 220 respectively correspond to the reception status of two PDSCHs 213 and 214 scheduled by type 2DCI 206 in CC4 (the reception status of PDSCH 214 in CC3 corresponds to the 5th bit, and the reception status of PDSCH 213 in CC4 corresponds to the 6th bit). In other words, the bits in the codebook 220 are determined by bit concatenation so that the feedback bits of type 1 DCI 202 and 208 (arranged according to their respective C-DAIs) are arranged before the feedback bits of type 2 DCI 204 and 206 (arranged according to their respective C-DAIs).

[0068] In the mapping relationship between the bits in the codebook 220 and the DL transmission, the multiple PDSCHs scheduled by the type 2 DCI occupy multiple consecutive bits of the codebook 220. That is, the PDSCHs 212 and 215 scheduled by the DCI 204 in type 2 occupy multiple consecutive bits in the codebook 210; and the PDSCHs 213 and 214 scheduled by the type 2 DCI 206 occupy multiple consecutive bits in the codebook 220. The two PDSCHs (e.g., 213 and 214) scheduled by the type 2 DCI (e.g., 206) correspond to the feedback bits in the order from low to high in the CC index, that is, among the two PDSCHs scheduled by the type 2 DCI, the PDSCH (e.g., 214) with the lower CC index occupies the earlier bits.

[0069] In a second method, the C-DAI of the type 2 DCI is determined by sorting the CC index of the type 2 DCI (e.g., from low to high). For example, in the feedback mechanism 300, the CC index of the type 2 DCI 204 is 5, and the CC index of the type 2 DCI 206 is 4. The CC index is sorted from low to high, with the type 2 DCI 206 being first and the type 2 DCI 204 being second. The C-DAI of the type 2 DCI with the lowest CC index is set to a predetermined value (e.g., the lowest value such as 1), and the C-DAI of the type 2 DCI with the second lowest CC index is set to another predetermined value (e.g., the second lowest value such as 2), and so on. For example, the C-DAI in the type 2 DCI 206 is 1, and the C-DAI in the type 2 DCI 204 is 2. The value of the T-DAI in both the type 2 DCI 204 and 206 is 2.

[0070] In some arrangements, after determining the values ​​of C-DAI and T-DAI in each type 2 DCI according to the second method, the codebook can be determined accordingly. As shown in the feedback mechanism 300, the codebook 320 contains the same number of bits (e.g., 6 bits) as the number of PDSCHs 211-216 scheduled by the DCIs 202, 204, 206, and 208, assuming that all are TB transmissions and two codewords are not configured. The first bit of codebook 320 corresponds to the reception status of PDSCH 216 in CC1, the second bit of codebook 320 corresponds to the reception status of PDSCH 211 in CC6, the third and fourth bits of codebook 320 respectively correspond to the reception status of two PDSCHs 213 and 214 scheduled by type 2DCI 206 in CC4 (the reception status of PDSCH 214 in CC3 corresponds to the third bit, and the reception status of PDSCH 213 in CC4 corresponds to the fourth bit), and the fifth and sixth bits of codebook 320 respectively correspond to the reception status of two PDSCHs 212 and 215 scheduled by type 2DCI 204 in CC5 (the reception status of PDSCH 215 in CC2 corresponds to the fifth bit, and the reception status of PDSCH 212 in CC5 corresponds to the sixth bit).

[0071] In the mapping relationship between the bits in the codebook 320 and the DL transmission, the multiple PDSCHs scheduled by the type 2 DCI occupy multiple consecutive bits in the codebook 220. That is, the PDSCHs 212 and 215 scheduled by the type 2 DCI 204 occupy multiple continuous bits in the codebook 220; and the PDSCHs 213 and 214 scheduled by the type 2 DCI 206 occupy multiple consecutive bits in the codebook 320. The multiple PDSCHs 212, 213, 214, and 215 scheduled by the type 2 DCIs 204 and 206 correspond to the feedback bits in the order from low to high according to the CC indexes of the type 2 DCIs 204 and 206. In the example where two PDSCHs are scheduled by the type 2 DCI, the two PDSCHs correspond to two consecutive bits in the codebook 320, and the PDSCH with the lower CC index corresponds to the preceding bit in the codebook 320.

[0072] Alternatively, a plurality of PDSCHs 212, 213, 214, and 215 scheduled by the type-2 DCI 204 and 206 correspond to feedback bits in descending order according to the CC indexes of the type-2 DCI 204 and 206. In an example in which two PDSCHs are scheduled by the type-2 DCI, the two PDSCHs correspond to two consecutive bits in the codebook 320, and the PDSCH with a higher CC index corresponds to a preceding bit in the codebook 320.

[0073] In some arrangements, the bits in the codebook 320 are determined by bit concatenation so that the feedback bits of type 1 DCI 202 and 208 (arranged according to their respective C-DAIs) are arranged before the feedback bits of type 2 DCI 204 and 206 (arranged according to their respective C-DAIs).

[0074] In some arrangements where type 2 DCI is implemented and some CCs are configured for CBG transmission, up to 4 subcodebooks may be supported. The feedback information (e.g., feedback bits) in each of those 4 subcodebooks may correspond to the reception status of the PDSCH, as described below.

[0075] For example, with respect to the first subcodebook, the feedback bits in the first subcodebook correspond to the reception status of two PDSCHs scheduled by type 2 DCI. Each of the PDSCHs is transmitted on a different CC. Both CCs are configured with CBG transmission. In other words, one or more CBGs are carried on each PDSCH.

[0076] Regarding the second subcodebook, the feedback bits in the second subcodebook correspond to the reception status of two PDSCHs scheduled by type 2 DCI. Each of the PDSCHs is transmitted on a different CC. Neither CC is configured with CBG transmission. In other words, a TB is carried on each PDSCH.

[0077] Regarding the third subcodebook, the feedback bits in the third subcodebook correspond to the reception status of the PDSCH on the CC configured for CBG transmission and not scheduled by DCI format 1_0. That is, the PDSCH is scheduled by a type 1 DCI with DCI format 1_1 or DCI format 1_2. In other words, one or more CBGs are carried on the PDSCH. Type 1 DCI can have one of various DCI formats (such as, but not limited to, DCI format 1_0, DCI format 1_1, and DCI format 1_2).

[0078] Regarding the fourth subcodebook, the feedback bits in the fourth subcodebook correspond to the following reception states: 1) PDSCH scheduled by type 1 DCI on a CC not configured for CBG transmission; and 2) PDSCH scheduled by type 1 DCI with DCI format 1_0 on a CC configured for CBG transmission. In other words, a TB is carried on each PDSCH, and its reception state corresponds to the feedback bit in the fourth subcodebook.

[0079] Figure 4 4 is a table 400 showing the number of feedback bits corresponding to each DAI count of 4 different subcodebooks according to various arrangements of the present disclosure. The maximum number of CBGs carried on the PDSCH can be configured to N by the base station via RRC signaling "maxCodeBlockGroupsPerTransportBlock". As shown, the first subcodebook (which includes feedback bits corresponding to type 2 DCI configured for CBG transmission on two CCs) has 2*N feedback bits. The second subcodebook (which includes feedback bits corresponding to type 2 DCI configured for TBs on two CCs) has 2 feedback bits (one for each TB). The third subcodebook (which includes feedback bits corresponding to type 1 DCI configured for CBG transmission) has N feedback bits. The fourth subcodebook (which includes feedback bits corresponding to type 1 DCI configured for TB transmission) has 1 feedback bit.

[0080] Given that type 2 DCI scheduling two PDSCHs is described herein for illustrative purposes, in an example where type 2 DCI schedules two TB PDSCH transmissions, the number of feedback bits corresponding to one DAI count is 2 (e.g., Q=2). In an example where the number of PDSCHs scheduled by type 2 DCI is Q, if Q PDSCHs are transmitted by CBG, then for the first subcodebook, the number of feedback bits corresponding to the DAI count is Q*N. If Q PDSCHs are transmitted by TB, then for the second subcodebook, the number of feedback bits corresponding to the DAI count is Q.

[0081] For each of the four sub-codebooks, the order (by which the DAI is counted) may be determined using the methods described herein (including at least feedback mechanisms 200 and 300).

[0082] In some arrangements, the UE may form a final feedback codebook by concatenating or cascading four subcodebooks (rather than two subcodebooks). The concatenation order of the four subcodebooks in the final feedback codebook may be predefined in the protocol or configured to the UE by the base station through RRC signaling.

[0083] In one example, the TB-level subcodebook is concatenated before the CBG-level subcodebook. For the TB-level subcodebook or the CBG-level subcodebook, the subcodebook corresponding to the type 1 DCI is concatenated before the subcodebook corresponding to the type 2 DCI. According to this concatenation order, the order in which the four feedback codebooks are concatenated is: the fourth subcodebook, the second subcodebook, the third subcodebook, and the first subcodebook.

[0084] In another example, the subcodebook corresponding to type 1 DCI is concatenated before the subcodebook corresponding to type 2 DCI. For two subcodebooks corresponding to type 1 DCI or two subcodebooks corresponding to type 2 DCI, the TB-level subcodebook is concatenated before the CBG-level subcodebook. According to this concatenation order, the order in which the four feedback codebooks are concatenated is: the fourth subcodebook, the third subcodebook, the second subcodebook, and the first subcodebook. Other predefined or configured concatenation orders may be implemented.

[0085] In some arrangements, the final feedback codebook may be generated based on some but not all of the 4 subcodebooks. In one example, for PDSCH scheduled by type 2 DCI, CBG transmission does not exist. In this example, the first subcodebook is not used to generate the final feedback codebook, and the final feedback codebook is generated by concatenating the fourth, third, and second subcodebooks in that order.

[0086] In addition, the occurrence of a specific type of scheduling can be restricted according to the requirements of the specification. Therefore, when generating the final codebook, one of the 4 subcodebooks corresponding to the restricted type of scheduling is not considered. For example, the PDSCH scheduled by the type 2 DCI is regarded as a TB, regardless of whether the CC where the PDSCH is located is configured for CBG transmission. In this example, the first subcodebook is restricted and only 3 of the 4 subcodebooks are defined. The final feedback codebook is generated using a maximum of 3 subcodebooks.

[0087] In the embodiments described herein with respect to 4 subcodebooks, it is assumed that two PDSCHs scheduled by the same type 2DCI are transmitted with the same attributes. That is, both PDSCHs are TB transmissions (CC is not configured with CBG transmission), or both PDSCHs are CBG transmissions (CC is configured with CBG transmission). In other embodiments (one involving 5 subcodebooks), two PDSCHs are allowed to be scheduled by type 2DCI with different transmission attributes. For example, one of the two PDSCHs is a TB transmission (CC is not configured with CBG transmission), and the other of the two PDSCHs is a CBG transmission (CC is configured with CBG transmission). In this regard, an additional subcodebook is added to contain feedback information (feedback bits) for PDSCHs scheduled by the same type 2DCI with different transmission attributes.

[0088] In the example of two PDSCHs scheduled by type 2 DCI, the CC of one of the two PDSCHs is configured with CBG transmission (one or more CBGs are carried on the PDSCH), and the CC of the other of the two PDSCHs is not configured with CBG transmission (TB is carried on the PDSCH). The fifth subcodebook may be implemented to include feedback bits for such a PDSCH scheduled by type 2 DCI.

[0089] Figure 55 is a table 500 showing the number of feedback bits corresponding to each DAI count of 5 different subcodebooks according to various arrangements of the present disclosure. As described, the maximum number of CBGs carried on the PDSCH can be configured to N by the base station via RRC signaling "maxCodeBlockGroupsPerTransportBlock". As shown, the first subcodebook (which includes feedback bits corresponding to type 2DCI configured for CBG transmission on two CCs) has 2*N feedback bits. The second subcodebook (which includes feedback bits corresponding to type 2DCI configured for TBs on two CCs) has 2 feedback bits (one for each TB). The third subcodebook (which includes feedback bits corresponding to type 1DCI configured for CBG transmission) has N feedback bits. The fourth subcodebook (which includes feedback bits corresponding to type 1DCI configured for TB transmission) has 1 feedback bit. The fifth subcodebook (which includes feedback bits corresponding to type 2DCI configured for both CBG and TB transmission) has N+1 feedback bits.

[0090] Given that type 2 DCI scheduling two PDSCHs is described herein for illustrative purposes, in an example where type 2 DCI schedules two TB PDSCH transmissions, the number of feedback bits corresponding to one DAI count is 2 (e.g., Q=2). In an example where the number of PDSCHs scheduled by type 2 DCI is Q, if Q PDSCHs are transmitted by CBG, then for the first subcodebook, the number of feedback bits corresponding to the DAI count is Q*N. If Q PDSCHs are transmitted by TB, then for the second subcodebook, the number of feedback bits corresponding to the DAI count is Q.

[0091] For each of the five sub-codebooks, the order (by which the DAI is counted) may be determined using the methods described herein (including at least feedback mechanisms 200 and 300).

[0092] In some arrangements, the UE may form a final feedback codebook by concatenating 5 subcodebooks (instead of 2 or 4). The concatenation order of the 5 subcodebooks in the final feedback codebook may be predefined in the protocol or configured to the UE by the base station through RRC signaling.

[0093] In one example, the subcodebook corresponding to type 1 DCI is concatenated before the subcodebook corresponding to type 2 DCI. For the two subcodebooks corresponding to type 1 DCI, the TB-level subcodebook is concatenated before the CBG-level subcodebook. For the three subcodebooks corresponding to type 2 DCI, the subcodebook containing feedback bits for TB and CBG transmissions is concatenated before the TB-level subcodebook, and the TB-level subcodebook is concatenated before the CBG-level subcodebook. According to this concatenation order, the order in which the five feedback codebooks are concatenated is: the fourth subcodebook, the third subcodebook, the fifth subcodebook, the second subcodebook, and the first subcodebook. Other predefined or configured concatenation orders may be implemented.

[0094] As described in reference tables 400 and 500, there may be more than one subcodebook for each of type 1 and type 2 DCIs. In some arrangements, the feedback bits of the subcodebooks may be merged into one subcodebook. As used herein, different scheduling modes include, but are not limited to, type 1 DCI for scheduling TB transmissions, type 1 DCI for scheduling CBG transmissions, type 2 DCI for scheduling two TB transmissions, type 2 DCI for scheduling two CBG transmissions, and type 2 DCI for scheduling TB transmissions and CBG transmissions. PDSCHs scheduled by DCI in different scheduling modes are counted together. Feedback bits corresponding to PDSCHs received in different scheduling modes may be merged into the subcodebook. As used herein, merging two subcodebooks into a merged subcodebook refers to generating a merged subcodebook that includes the subcodebooks that would otherwise be included in reference tables 400 and 500. Figure 4 or Figure 5 The number of feedback bits corresponding to the DAI count is determined according to the scheduling mode that requires more feedback bits corresponding to the DAI count.

[0095] For scheduling modes that require fewer feedback bits corresponding to the DAI count, in addition to containing valid feedback information, the remaining bits are filled with zeros or repetitions of valid feedback bits.

[0096] For example, in the first merge mode 1, the final codebook is generated according to the CBG codebook and the TB subcodebook. The UE is configured to generate a first subcodebook, the first subcodebook comprising feedback bits corresponding to a PDSCH scheduled by one or more type 1 DCIs and one or more type 2 DCIs, wherein the CC is configured for the CBG. The UE is also configured to generate a second subcodebook, the second subcodebook comprising feedback bits corresponding to a PDSCH scheduled by one or more type 1 DCIs and one or more type 2 DCIs, wherein the CC is configured for the TB.

[0097] The C-DAI count of the first subcodebook corresponds to 2*N bits, where N is the maximum number of CBGs. The number of CBGs can be configured by the base station via RRC parameters (such as "maxCodeBlockGroupsPerTransportBlock") (received from the base station). The number of feedback bits for the PDSCH scheduled by type 1 DCI is also 2*N. The 2*N feedback bits contain M valid bits, which are valid feedback information. The valid bits correspond to the M CBGs scheduled by type 1 DCI, where M≤N. The remaining (2*NM) bits can be filled with filler bits (e.g., zeros or repetitions of valid feedback bits). The M bits of valid feedback information can occupy the first M bits of a total of 2*N feedback bits. For example, the first M bits can be referred to as the M most significant bits (MSBs).

[0098] In an alternative example, the number of CBGs scheduled by type 2 DCI may be limited to half of N, and the C-DAI count of the first subcodebook represents N bits.

[0099] The C-DAI count of the second subcodebook corresponds to 2 bits. The PDSCH scheduled by the type 1 DCI corresponds to 2 feedback bits in the second subcodebook. Of the 2 feedback bits, 1 bit is valid feedback information corresponding to 1TB scheduled by the type 1 DCI, and the other 1 bit is filled with padding bits (e.g., zero or repetition of valid feedback bits). In some examples, the valid feedback information occupies the first 1 bit of the 2 bits.

[0100] In the second merge mode, the feedback bits corresponding to the PDSCH carrying the CBG transmission scheduled by type 1 DCI (CBG+type 1 DCI) and the feedback bits corresponding to the PDSCH carrying the TB transmission scheduled by type 2 DCI (TB+type 2 DCI) are merged into a subcodebook (referred to as subcodebook x).

[0101] The number of bits in the subcodebook x corresponding to the C-DAI count is equal to Max{N,Q}. N is the maximum number of CBGs, which can be configured by the base station RRC parameter "maxCodeBlockGroupsPerTransportBlock". Q is the number of PDSCHs scheduled by Type 2 DCI.

[0102] In the example of N>Q, the Q PDSCHs scheduled by the type 2 DCI also occupy N bits in the feedback codebook x, where the Q valid bits correspond to the reception status of the Q PDSCHs. The Q valid bits are valid feedback information, which can be the first Q bits of the total N bits. The remaining (NQ) bits are filled with padding bits (e.g., zeros or repetitions of valid feedback bits). The Q bits of valid feedback information can occupy the first Q bits of the total N feedback bits. For example, the first Q bits can be referred to as the Q most significant bits (MSBs).

[0103] In the example of N < Q, the reception status of the N CBGs included in the PDSCH scheduled by the type 1 DCI also occupies Q bits in the feedback codebook x, where the N valid bits correspond to the N CBGs. The N valid bits are valid feedback information, which can be the first N bits of the total Q bits. The remaining (QN) bits are filled with padding bits (e.g., zero or repetition of valid feedback bits). The N bits of valid feedback information can occupy the first N bits of the total Q feedback bits.

[0104] As described with reference to Table 500, the PDSCH scheduled by type 2 DCI may have two different attributes, namely, TB transmission and CBG transmission. In the third merge mode, feedback bits corresponding to the reception status of CBG transmission (CBG+type 1 DCI) scheduled by type 1 DCI are merged with feedback bits corresponding to the reception status of one TB transmission and one CBG transmission (TB+CBG+type 2 DCI) scheduled by type 2 DCI to form a subcodebook referred to as subcodebook y.

[0105] The C-DAI count corresponds to (N+1) bits in the subcodebook y, where N is the maximum number of CBGs, which can be configured by the base station via the RRC parameter "maxCodeBlockGroupsPerTransportBlock". The (N+1) bits correspond to the TBs and N CBGs scheduled by type 2 DCI, respectively. For PDSCH scheduled by type 1 DCI, N bits correspond to N CBGs, and the remaining 1 bit can be filled with padding bits (e.g., zeros).

[0106] Alternatively, the subcodebook may be determined based on the RRC configuration received from the base station. In an example where no CC in the CC group is configured with CBG, the UE forms two subcodebooks, a type 1 DCI subcodebook (including feedback bits corresponding to the PDSCH scheduled by type 1 DCI) and a type 2 DCI subcodebook (including feedback bits corresponding to the PDSCH scheduled by type 2 DCI). In an example where at least one CC in the CC group is configured with CBG, the UE forms two subcodebooks, a CBG subcodebook (including feedback bits corresponding to the PDSCH carrying CBG transmissions scheduled by type 1 and type 2 DCI) and a TB subcodebook (including feedback bits corresponding to the PDSCH carrying TB transmissions scheduled by type 1 and type 2 DCI).

[0107] In some examples, the merged sub-codebooks may be bit-concatenated in any suitable order to form a final codebook.

[0108] Figure 6 is a flow chart illustrating example methods 600a and 600b for managing feedback according to various arrangements of the present disclosure. Figure 6 , method 600a is performed by a UE, and method 600b corresponds to method 600a and is performed by a base station.

[0109] At 602b, the base station sends at least one of (1) a first scheduling indicator (e.g., one or more type 1 DCIs) and (2) a second scheduling indicator (e.g., one or more type 2 DCIs) to the UE. At 602a, the UE receives at least one of (1) the first scheduling indicator and (2) the second scheduling indicator from the base station. Each of the first scheduling indicators schedules one transmission. The transmission scheduled by each of the first scheduling indicators is a first transmission type or a second transmission type. Each of the second scheduling indicators schedules two or more transmissions. Each of the two or more transmissions scheduled by each of the second scheduling indicators is a first transmission type or a second transmission type.

[0110] At 604a, the UE generates one or more sub-codebooks according to one or more of the first scheduling indicator, the second scheduling indicator, the first transmission type, and the second transmission type.

[0111] In some examples, each of the one or more sub-codebooks is generated based on one or more scheduling modes. Each of the scheduling modes is one of a first scheduling indicator for scheduling a first type of transmission, one of a first scheduling indicator for scheduling a second type of transmission, one of a second scheduling indicator for scheduling a first type of transmission, one of a second scheduling indicator for scheduling a second type of transmission, or one of a second scheduling indicator for scheduling a first type of transmission and a second type of transmission.

[0112] In some examples, the one or more sub-codebooks include a first sub-codebook, a second sub-codebook, a third sub-codebook, and a fourth sub-codebook, as shown in FIG. Figure 4 In a further example, one or more sub-codebooks further include Figure 5 The fifth subcodebook. Generating one or more subcodebooks based on the first scheduling indicator, the second scheduling indicator, the first transmission type, and the second transmission type includes at least one of the following: generating a first subcodebook based on one of the second scheduling indicators for scheduling the first type of transmission, generating a second subcodebook based on one of the second scheduling indicators for scheduling the second type of transmission, generating a third subcodebook based on one of the first scheduling indicators for scheduling the first type of transmission, generating a fourth subcodebook based on one of the first scheduling indicators for scheduling the second type of transmission, or generating a fifth subcodebook based on one of the second scheduling indicators for scheduling the first type of transmission and the second type of transmission.

[0113] In some examples, the UE may generate a merged subcodebook by merging two or more subcodebooks. The number of feedback bits of the merged subcodebook corresponding to the DAI count is determined according to the first number of feedback bits used to provide feedback information to the first of the two or more subcodebooks. The first number of feedback bits is greater than the second number of feedback bits used to provide feedback information to any other of the two or more subcodebooks. The DAI count in any other of the two or more subcodebooks corresponds to the first number of feedback bits within the merged subcodebook. The first number of feedback bits corresponding to any other of the two or more subcodebooks includes a second number of feedback bits and padding bits. The padding bits include zeros or repetitions of the first number of feedback bits.

[0114] At 606a, the UE generates a codebook by combining the generated one or more subcodebooks. In some examples, the codebook is generated by bit concatenating or serializing bits in subcodebooks (e.g., 4 subcodebooks, 5 subcodebooks, etc.). In some examples, the codebook is generated by bit concatenating or serializing bits in a merged subcodebook (obtained by merging two subcodebooks) with bits in other merged subcodebooks or with subcodebooks.

[0115] At 608, the UE sends a codebook to the base station. At 604b, the base station receives a codebook generated based on one or more sub-codebooks from the UE. The one or more sub-codebooks are generated by the UE according to the first scheduling indicator, the second scheduling indicator, the first transmission type, and the second transmission type. At 606b, the base station determines the reception status of the transmission scheduled by each first scheduling indicator and the reception status of the transmission scheduled by each second scheduling indicator based on the codebook.

[0116] Fig. 7AA block diagram of an example BS 702 is shown in accordance with some embodiments of the present disclosure. Figure 7B FIG. 7 is a block diagram of an example UE 701 according to some embodiments of the present disclosure. Figure 1-7B , UE 701 (eg, wireless communication device, terminal, mobile device, mobile user, etc.) is an example implementation of a UE described herein, and BS 702 is an example implementation of a BS described herein.

[0117] BS 702 and UE 701 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In an illustrative embodiment, BS 702 and UE 701 may be used to transmit (e.g., send and receive) data symbols in a wireless communication environment, as described above. For example, BS 702 may be a BS (e.g., gNB, eNB, etc.), a server, a node, or any suitable computing device for implementing various network functions.

[0118] BS 702 includes a transceiver module 710, an antenna 712, a processor module 714, a memory module 716, and a network communication module 718. Modules 710, 712, 714, 716, and 718 are operably coupled to and interconnected with each other via a data communication bus 720. UE 701 includes a UE transceiver module 730, a UE antenna 732, a UE memory module 734, and a UE processor module 736. Modules 730, 732, 734, and 736 are operably coupled to and interconnected with each other via a data communication bus 740. BS 702 communicates with UE 701 or another BS via a communication channel, which may be any wireless channel or other medium suitable for transmitting data as described herein.

[0119] As will be understood by those skilled in the art, BS 702 and UE 701 may also include other components besides Fig. 7A and Figure 7B Any number of modules other than the modules shown in . The various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any actual combination thereof. In order to illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described according to their functions. Whether such functions are implemented as hardware, firmware, or software may depend on the specific application and the design constraints imposed on the entire system. The embodiments described herein can be implemented in a suitable manner for each specific application, but the decision of any implementation method should not be interpreted as limiting the scope of the present disclosure.

[0120] According to some embodiments, the UE transceiver 730 includes a radio frequency (RF) transmitter and an RF receiver, each of which includes a circuit coupled to an antenna 732. A duplex switch (not shown) may alternatively couple the RF transmitter or receiver to the antenna in a time duplex manner. Similarly, according to some embodiments, the transceiver 710 includes an RF transmitter and an RF receiver, each of which has a circuit coupled to an antenna 712 or an antenna of another BS. The duplex switch may alternatively couple the RF transmitter or receiver to the antenna 712 in a time duplex manner. The operation of the two transceiver modules 710 and 730 may be coordinated in time so that while the transmitter is coupled to the antenna 712, the receiver circuit is coupled to the antenna 732 for receiving transmissions via a wireless transmission link. In some embodiments, there is tight time synchronization with a minimum guard time between changes in duplex direction.

[0121] The UE transceiver 730 and the transceiver 710 are configured to communicate via a wireless data communication link and cooperate with an appropriately configured RF antenna arrangement 712 / 732 capable of supporting a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 730 and the transceiver 710 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to application to specific standards and associated protocols. Instead, the UE transceiver 730 and the BS transceiver 710 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0122] The transceiver 710 and the transceiver of another BS (such as but not limited to the transceiver 710) are configured to communicate via a wireless data communication link and cooperate with an appropriately configured RF antenna arrangement capable of supporting a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the transceiver 710 and the transceiver of another BS are configured to support industry standards such as LTE and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to the application of specific standards and related protocols. On the contrary, the transceiver 710 and the transceiver of another BS can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0123] According to various embodiments, for example, BS 702 may be a BS such as, but not limited to, an eNB, a serving eNB, a target eNB, a femtocell or a microcell. BS 702 may be a RN, a DeNB or a gNB. In some embodiments, UE 701 may be embodied in various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. Processor module 714 and processor module 736 may be implemented or implemented with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, a discrete gate or transistor logic, a discrete hardware component or any combination thereof designed to perform the functions described herein. In this manner, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0124] In addition, the methods or algorithms disclosed herein may be directly embodied in hardware, firmware, software modules executed by the processor module 714 and the processor module 736, respectively, or any practical combination thereof. The memory module 716 and the memory module 734 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, the memory module 716 and the memory module 734 may be coupled to the processor module 714 and the processor module 736, respectively, so that the processor module 714 and the processor module 736 can read information from the memory module 716 and the memory module 734, respectively, and write information to the memory module 716 and the memory module 734. The memory module 716 and the memory module 734 may also be integrated into their respective processor modules 714 and processor modules 736. In some embodiments, the memory module 716 and the memory module 734 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by the processor module 714 and the processor module 736, respectively. The memory module 716 and the memory module 734 may also each include a non-volatile memory for storing instructions to be executed by the processor module 714 and the processor module 736, respectively.

[0125] The network communication module 718 generally represents the hardware, software, firmware, processing logic and / or other components of the BS 702, which can enable bidirectional communication between the transceiver 710 and other network components and communication nodes communicating with the BS 702. For example, the network communication module 718 can be configured to support Internet or WiMAX traffic. In deployment, but not limited to, the network communication module 718 provides an 802.3 Ethernet interface so that the transceiver 710 can communicate with a traditional Ethernet-based computer network. In this way, the network communication module 718 can include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). In some embodiments, the network communication module 718 includes a fiber optic transmission connection configured to connect the BS 702 to the core network. The terms "configured for", "configured to" and their variants used herein with respect to a specified operation or function refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted and / or arranged to perform a specified operation or function.

[0126] Although various embodiments of the present solution have been described above, it should be understood that they are presented only by way of example rather than by way of limitation. Similarly, various figures may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the example features and functions of the present solution. However, these personnel will understand that the present solution is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. In addition, as those of ordinary skill in the art will appreciate, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-mentioned illustrative embodiments.

[0127] It should also be understood that any reference to an element using names such as "first", "second" etc. herein does not generally limit the quantity or order of these elements. On the contrary, these names can be used as a convenient means of distinguishing two or more elements or element instances in this article. Therefore, reference to a first element and a second element does not mean that only two elements can be used, or that the first element must be located before the second element in some way.

[0128] In addition, it should be understood by those skilled in the art that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0129] It will also be understood by those of ordinary skill in the art that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design codes containing instructions (which may be referred to herein as "software" or "software modules" for convenience), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functions. Whether such functionality is implemented as hardware, firmware, or as software, or as a combination of these technologies, depends on the specific application and the design constraints imposed on the entire system. Those skilled in the art may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of this disclosure.

[0130] In addition, it will be appreciated by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or performed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. The general-purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein.

[0131] If implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, and communication media include any media that can enable a computer program or code to be transferred from one place to another. The storage medium can be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to store desired program codes in the form of instructions or data structures and can be accessed by a computer.

[0132] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. In addition, for the purpose of discussion, various modules are described as discrete modules; however, it will be apparent to one of ordinary skill in the art that two or more modules can be combined to form a single module that performs the associated functions according to an embodiment of the present solution.

[0133] In addition, memory or other storage and communication components can be used in the embodiments of the present solution. It should be understood that, for the purpose of clarity, the above description has described the embodiments of the present solution with reference to different functional units and processors. However, it is apparent that any appropriate functional distribution between different functional units, processing logic elements or domains can be used without departing from the present solution. For example, the functions shown as being performed by a separate processing logic element or controller can be performed by the same processing logic element or controller. Therefore, reference to a specific functional unit is only a reference to a suitable device for providing the described function, rather than an indication of a strict logical or physical structure or organization.

[0134] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the broadest scope consistent with the novel features and principles disclosed herein, as described in the following claims.

Claims

1. A wireless communication method, comprising: receiving, by a wireless communication device from a base station, a first scheduling indicator and a second scheduling indicator, wherein each of the first scheduling indicators schedules one transmission and each of the second scheduling indicators schedules two or more transmissions; The wireless communication device generates a first sub-codebook and a second sub-codebook, wherein The first subcodebook comprises one or more first feedback bits, the one or more first feedback bits indicating a reception status of a transmission scheduled by each of the first scheduling indicators; as well as The second subcodebook includes second feedback bits indicating a reception status of two or more transmissions scheduled by each of the second scheduling indicators; as well as A codebook is generated by the wireless communication device by merging the first sub-codebook and the second sub-codebook.

2. The method according to claim 1, wherein each of the first scheduling indicators comprises a first index identifying a bit in the first subcodebook corresponding to a reception status of a transmission scheduled by each of the first scheduling indicators; each of the second scheduling indicators comprises a second index identifying a bit in the second subcodebook corresponding to a reception status of two or more transmissions scheduled by each of the second scheduling indicators; and The first index of the first scheduling indicator and the second index of the second scheduling indicator are counted independently.

3. The method according to claim 2, wherein Each of the first scheduling indicators and each of the second scheduling indicators is downlink control information DCI; The transmission is a physical downlink shared channel (PDSCH), and the wireless communication device receives downlink data from the base station using the PDSCH; and Each of the first index and the second index is a downlink allocation index DAI.

4. The method according to claim 3, wherein The DAI in each of the second scheduling indicators comprises a counter DAI C-DAI and a total DAI T-DAI; Each count in the C-DAI or the T-DAI corresponds to a number of bits in the second sub-codebook, the number of bits being based on a number of two or more transmissions scheduled by each of the second scheduling indicators.

5. The method according to claim 4, wherein The C-DAI in each of the second scheduling indicators is determined based on a carrier index of each of the two or more transmissions; and The second feedback bits are arranged according to the C-DAI in each of the second scheduling indicators.

6. The method according to claim 5, wherein One of the two or more transmissions is a transmission on a carrier having a lower carrier index than any other of the two or more transmissions; or One of the two or more transmissions is a transmission on a carrier having a higher carrier index than any other one of the two or more transmissions.

7. The method according to claim 4, wherein The C-DAI in each of the second scheduling indicators is determined based on a carrier index of each of the second scheduling indicators; and The second feedback bits are arranged according to the C-DAI in each of the second scheduling indicators.

8. The method according to claim 1, wherein: Second feedback bits corresponding to two or more transmissions scheduled by the second scheduling indicator are consecutive in the codebook.

9. The method according to claim 1, wherein The first sub-codebook comprises at least one of two first sub-codebooks, a first one of the first sub-codebooks comprising feedback bits corresponding to a first transmission type scheduled by a first one of the first scheduling indicators, the first transmission type comprising a code block group CBG, and a second one of the first sub-codebooks comprising feedback bits corresponding to a second transmission type scheduled by a second one of the first scheduling indicators, the second transmission type comprising a transport block TB; and The second sub-codebook includes at least one of two second sub-codebooks, a first one of the second sub-codebooks including feedback bits corresponding to the first transmission type scheduled by a first one of the second scheduling indicators, and a second one of the second sub-codebooks including feedback bits corresponding to a second transmission type scheduled by a second one of the second scheduling indicators.

10. The method according to claim 9, wherein: Generating the codebook includes: merging the first sub-codebook and the second sub-codebook by bit-concatenating the first sub-codebook and the second sub-codebook according to the first transmission type, the second transmission type, the first scheduling indicator, and the second scheduling indicator.

11. The method according to claim 1, wherein The first sub-codebook comprises at least one of two first sub-codebooks, a first one of the first sub-codebooks comprising feedback bits corresponding to a first transmission type scheduled by a first one of the first scheduling indicators, the first transmission type comprising a code block group CBG, and a second one of the first sub-codebooks comprising feedback bits corresponding to a second transmission type scheduled by a second one of the first scheduling indicators, the second transmission type comprising a transport block TB; and The second sub-codebook includes at least one of three second sub-codebooks, a first one of the second sub-codebooks includes feedback bits corresponding to the first transmission type scheduled by the first one of the second scheduling indicators, a second one of the second sub-codebooks includes feedback bits corresponding to the second transmission type scheduled by the second one of the second scheduling indicators, and a third one of the second sub-codebooks includes feedback bits corresponding to the first transmission type and the second transmission type scheduled by the third one of the second scheduling indicators.

12. The method according to claim 11, wherein: Generating the codebook includes merging the first sub-codebook and the second sub-codebook by bit-concatenating the first sub-codebook and the second sub-codebook according to the first transmission type, the second transmission type, the first scheduling indicator, and the second scheduling indicator.

13. A wireless communication device, comprising at least one processor and a memory, wherein: The at least one processor is configured to read code from the memory and implement the method according to claim 1.

14. A computer program product comprising computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement the method according to claim 1.

15. A wireless communication method, comprising: sending, by a base station, a first scheduling indicator and a second scheduling indicator to a wireless communication device, wherein each of the first scheduling indicators schedules one transmission and each of the second scheduling indicators schedules two or more transmissions; The base station receives, from the wireless communication device, a codebook generated by combining a first subcodebook and a second subcodebook, wherein The first subcodebook includes a first feedback bit, the first feedback bit indicating a reception status of a transmission scheduled by each of the first scheduling indicators; as well as The second subcodebook includes second feedback bits indicating a reception status of two or more transmissions scheduled by each of the second scheduling indicators; as well as The reception status of the transmission scheduled by each of the first scheduling indicators and the reception status of the transmission scheduled by each of the second scheduling indicators are determined by the base station based on the codebook.

16. A wireless communication device comprising at least one processor and a memory, wherein: The at least one processor is configured to read code from the memory and implement the method according to claim 15 .

17. A computer program product comprising computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement the method according to claim 15.

18. A wireless communication method, comprising: Receiving, by a wireless communication device, a first scheduling indicator and a second scheduling indicator from a base station, wherein each of the first scheduling indicators schedules one transmission, the transmission scheduled by each of the first scheduling indicators being of a first transmission type or a second transmission type, and each of the second scheduling indicators schedules two or more transmissions, each of the two or more transmissions scheduled by each of the second scheduling indicators being of the first transmission type or the second transmission type; The wireless communication device generates a first subcodebook according to the first transmission type scheduled by the first scheduling indicator or generates a second subcodebook according to the second transmission type scheduled by the first scheduling indicator, and generates a third subcodebook according to the first transmission type scheduled by the second scheduling indicator, generates a fourth subcodebook according to the second transmission type scheduled by the second scheduling indicator, or generates a fifth subcodebook according to the first transmission type and the second transmission type scheduled by the second scheduling indicator, wherein The first subcodebook or the second subcodebook comprises one or more first feedback bits, wherein the one or more first feedback bits indicate a reception status of a transmission scheduled by each of the first scheduling indicators; as well as The third subcodebook, the fourth subcodebook or the fifth subcodebook comprises a second feedback bit, wherein the second feedback bit indicates a reception status of two or more transmissions scheduled by each of the second scheduling indicators; as well as A codebook is generated by the wireless communication device by merging at least one of the generated first and second sub-codebooks and at least one of the third, fourth, and fifth sub-codebooks.

19. The method according to claim 18, wherein The first sub-codebook is generated based on a scheduling mode for scheduling the first scheduling indicator of the first transmission type, the second sub-codebook is generated based on a scheduling mode for scheduling the first scheduling indicator of the second transmission type, the third sub-codebook is generated based on a scheduling mode for scheduling the second scheduling indicator of the first transmission type, the fourth sub-codebook is generated based on a scheduling mode for scheduling the second scheduling indicator of the second transmission type, and the fifth sub-codebook is generated based on a scheduling mode for scheduling the second scheduling indicator of the first transmission type and the second transmission type.

20. The method of claim 18, further comprising generating a merged sub-codebook by merging two or more of the sub-codebooks.

21. The method according to claim 20, wherein: The number of feedback bits of the merged sub-codebook corresponding to the downlink allocation index DAI count is determined according to a first number of feedback bits for providing feedback information to a first one of the two or more sub-codebooks, the first number of feedback bits being greater than a second number of feedback bits for providing feedback information to any other one of the two or more sub-codebooks.

22. The method according to claim 21, wherein: The DAI count in any other one of the two or more subcodebooks corresponds to a first number of the feedback bits of the merged subcodebook, and the first number of feedback bits corresponding to any other one of the two or more subcodebooks includes the second number of feedback bits and padding bits, wherein the padding bits include zeros or repetitions of the first number of feedback bits.

23. A wireless communication device, comprising at least one processor and a memory, wherein: The at least one processor is configured to read code from the memory and implement the method according to claim 18.

24. A computer program product comprising computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement the method according to claim 18.

25. A wireless communication method, comprising: Sending, by a base station, a first scheduling indicator and a second scheduling indicator to a wireless communication device, wherein each of the first scheduling indicators schedules one transmission, the transmission scheduled by each of the first scheduling indicators being of a first transmission type or a second transmission type, and each of the second scheduling indicators schedules two or more transmissions, each of the two or more transmissions scheduled by each of the second scheduling indicators being of the first transmission type or the second transmission type; receiving, by the base station, from the wireless communication device, a codebook generated by combining at least one of a first sub-codebook generated by the wireless communication device according to a first transmission type scheduled by the first scheduling indicator and a second sub-codebook generated according to a second transmission type scheduled by the first scheduling indicator, and a third sub-codebook generated according to the first transmission type scheduled by the second scheduling indicator, a fourth sub-codebook generated according to the second transmission type scheduled by the second scheduling indicator, and a fifth sub-codebook generated according to the first transmission type and the second transmission type scheduled by the second scheduling indicator; as well as A reception status of a transmission scheduled by each of the first scheduling indicators and a reception status of a transmission scheduled by each of the second scheduling indicators are determined by the base station based on the codebook.

26. A wireless communication device comprising at least one processor and a memory, wherein: The at least one processor is configured to read code from the memory and implement the method according to claim 25.

27. A computer program product comprising computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement the method according to claim 25.

Images