Method for dynamic harq-ack codebook with multiple sub-codebooks

Abstract

A system and method of handling acknowledgements in a wireless system. In some embodiments, the method includes receiving, by a user equipment (UE), one or more first transmissions; decoding, by the UE, the first transmissions to generate a first sub-codebook comprising one or more corresponding hybrid automatic repeat request acknowledgement (HARQ ACK) bit strings each having a first length; receiving, by the UE, one or more second transmissions; decoding, by the UE, the second transmissions to generate a second sub-codebook comprising one or more corresponding HARQ ACK bit strings each having a second length that is greater than the first length; receiving, by the UE, one or more third transmissions; and decoding, by the UE, the third transmissions to generate a third sub-codebook comprising one or more corresponding HARQ ACK bit strings each having a third length that is greater than the second length.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority and benefit to U.S. Provisional Application No. 63 / 156,504, filed March 4, 2021, entitled “HARQ CODEBOOK TYPE 2 ENHANCEMENT,” and U.S. Provisional Application No. 63 / 253874, filed October 8, 2021, entitled “DYNAMICHARQ-ACK CODEBOOK WITH MULTI-SUB CODEBOOKS,” the entire contents of the two provisional applications identified in this paragraph are incorporated herein by reference. Technical Field

[0003] One or more aspects of embodiments of this disclosure relate to wireless communication, and more specifically, to systems and methods for processing authentication in a wireless system. Background Technology

[0004] In wireless systems, acknowledgment bits for received data can be transmitted as a set of bits called a codebook. Each codebook can contain multiple bits, each indicating whether some data previously scheduled to be sent by the corresponding scheduling communication has been successfully received. Therefore, each such bit has a predictable position in the codebook. Given the uncertainty regarding whether all scheduled communications have been successfully received, the receiving device may populate the set of acknowledgment bits, potentially consuming system resources.

[0005] The aspects disclosed herein pertain to this general technological environment. Summary of the Invention

[0006] According to embodiments of this disclosure, a method is provided, comprising: receiving one or more first transmissions by a user equipment (UE); decoding the first transmissions by the UE to generate a first subcodebook including one or more corresponding Hybrid Automatic Repeat Request Acknowledgment (HARQ ACK) bit strings, each having a first length; receiving one or more second transmissions by the UE; decoding the second transmissions by the UE to generate a second subcodebook including one or more corresponding HARQ ACK bit strings, each having a second length greater than the first length; receiving one or more third transmissions by the UE; and decoding the third transmissions by the UE to generate a third subcodebook including one or more corresponding HARQ ACK bit strings, each having a third length greater than the second length.

[0007] In some embodiments, the first length is 1.

[0008] In some embodiments, each of the first length, the second length, and the third length is configured via Radio Resource Control (RRC).

[0009] In some embodiments, the generation of the third subcodebook includes: receiving a code block group (CBG) having a number of code blocks greater than the second length and less than or equal to the third length; generating a set of HARQ ACK bits, each corresponding to a corresponding code block group in the code block group; and filling the set of HARQ ACK bits to form a HARQ ACK bit string with the third length.

[0010] In some embodiments, the generation of the second subcodebook includes: receiving a code block group (CBG) having a number of code blocks greater than a first length and less than or equal to a second length; generating a set of HARQ ACK bits, each corresponding to a corresponding code block group in the code block group; and filling the set of HARQ ACK bits to form a HARQ ACK bit string of the second length.

[0011] In some embodiments, the method further includes: receiving a counted downlink allocation indicator (C-DAI) for the second transmission and a total downlink allocation indicator (T-DAI) for the second transmission; determining a transmission loss in the second transmission based on the C-DAI and T-DAI; and including a bit string with a second length of negative acknowledgment bits in a second subcodebook.

[0012] In some embodiments, the method further includes: receiving a third transmission C-DAI and a third transmission T-DAI, wherein the third transmission C-DAI is different from the second transmission C-DAI and the third transmission T-DAI is different from the second transmission T-DAI; determining a transmission loss in the third transmission based on the third transmission C-DAI and the third transmission T-DAI; and including a bit string with a third length of negative acknowledgment bits in a second subcodebook.

[0013] In some embodiments, the method further includes: receiving a third transmission T-DAI using the C-DAI of the second transmission and the T-DAI of the second transmission; determining a transmission loss in the third transmission based on the C-DAI and the T-DAI of the third transmission; and including a bit string with a negative acknowledgment bit of a third length in the second subcodebook.

[0014] In some embodiments, the method further includes: receiving one or more fourth transmissions by the UE; and decoding the fourth transmissions by the UE to generate a fourth subcodebook comprising one or more corresponding HARQ ACK bit strings, each having a fourth length greater than the third length.

[0015] According to embodiments of this disclosure, a user equipment (UE) is provided, including: a radio device; and a processing circuit configured to: receive one or more first transmissions; decode the first transmissions to generate a first subcodebook including one or more corresponding Hybrid Automatic Repeat Request Acknowledgment (HARQ ACK) bit strings, each having a first length; receive one or more second transmissions; decode the second transmissions to generate a second subcodebook including one or more corresponding HARQ ACK bit strings, each having a second length greater than the first length; receive one or more third transmissions; and decode the third transmissions to generate a third subcodebook including one or more corresponding HARQ ACK bit strings, each having a third length greater than the second length.

[0016] In some embodiments, the first length is 1.

[0017] In some embodiments, each of the first length, the second length, and the third length is configured via Radio Resource Control (RRC).

[0018] In some embodiments, the generation of the third subcodebook includes: receiving a code block group (CBG) having a number of code blocks greater than the second length and less than or equal to the third length; generating a set of HARQ ACK bits, each corresponding to a corresponding code block group in the code block group; and filling the set of HARQ ACK bits to form a HARQ ACK bit string with the third length.

[0019] In some embodiments, the generation of the second subcodebook includes: receiving a code block group (CBG) having a number of code blocks greater than a first length and less than or equal to a second length; generating a set of HARQ ACK bits, each corresponding to a corresponding code block group in the code block group; and filling the set of HARQ ACK bits to form a HARQ ACK bit string of the second length.

[0020] In some embodiments, the processing circuitry is further configured to: receive a counted downlink allocation indicator (C-DAI) for the second transmission and a total downlink allocation indicator (T-DAI) for the second transmission; determine a transmission loss in the second transmission based on the C-DAI and T-DAI; and include a bit string with a second length of negative acknowledgment bits in the second subcodebook.

[0021] In some embodiments, the processing circuit is further configured to: receive a third transmission C-DAI and a third transmission T-DAI, wherein the third transmission C-DAI is different from the second transmission C-DAI and the third transmission T-DAI is different from the second transmission T-DAI; determine a transmission loss in the third transmission based on the third transmission C-DAI and the third transmission T-DAI; and include a bit string with a third length of negative acknowledgment bits in the second subcodebook.

[0022] In some embodiments, the processing circuit is further configured to: receive a third transmission T-DAI using the C-DAI of the second transmission and the T-DAI of the second transmission; determine a transmission loss in the third transmission based on the C-DAI and the T-DAI of the third transmission; and include a bit string with a negative acknowledgment bit of a third length in the second subcodebook.

[0023] In some embodiments, the processing circuit is further configured to: receive one or more fourth transmissions by the UE; and decode the fourth transmissions by the UE to generate a fourth subcodebook comprising one or more corresponding HARQACK bit strings, each having a fourth length greater than the third length.

[0024] According to embodiments of this disclosure, a user equipment (UE) is provided, including: a radio device; and a processing component configured to: receive one or more first transmissions; decode the first transmissions to generate a first subcodebook including one or more corresponding Hybrid Automatic Repeat Request Acknowledgment (HARQ ACK) bit strings, each having a first length; receive one or more second transmissions; decode the second transmissions to generate a second subcodebook including one or more corresponding HARQ ACK bit strings, each having a second length greater than the first length; receive one or more third transmissions; and decode the third transmissions to generate a third subcodebook including one or more corresponding HARQ ACK bit strings, each having a third length greater than the second length.

[0025] In some embodiments, the first length is 1. Attached Figure Description

[0026] These and other features and advantages of this disclosure will be recognized and understood by referring to the specification, claims and drawings, wherein:

[0027] Figure 1A This is a data flow diagram according to an embodiment of the present disclosure;

[0028] Figure 1B This is a data flow diagram according to an embodiment of the present disclosure;

[0029] Figure 1C It is a subcodebook participation table according to an embodiment of this disclosure;

[0030] Figure 1D This is a data flow diagram according to an embodiment of the present disclosure;

[0031] Figure 2A This is a data flow diagram according to an embodiment of the present disclosure;

[0032] Figure 2B This is a data flow diagram according to an embodiment of the present disclosure;

[0033] Figure 3 This is a flowchart of an embodiment according to the present disclosure; and

[0034] Figure 4 This is a block diagram according to an embodiment of the present disclosure. Detailed Implementation

[0035] The detailed description set forth below with reference to the accompanying drawings is intended as a description of exemplary embodiments of systems and methods for processing authentication in a wireless system provided in accordance with this disclosure, and is not intended to represent the only form in which this disclosure may be constructed or utilized. This description illustrates features of the disclosure in conjunction with the illustrated embodiments. However, it should be understood that the same or equivalent functionality and structure may be implemented through different embodiments, which are also intended to be included within the scope of this disclosure. As shown elsewhere herein, similar element designations are intended to indicate similar elements or features.

[0036] In Release 16 (Rel-16) of the 3GPP 5G New Radio (NR) standard, when the uplink (UL) resources of the Physical Uplink Shared Channel (PUSCH) overlap with the Physical Uplink Control Channel (PUCCH) designed for delivering HARQ ACK information, the User Equipment (UE) has the capability to multiplex Hybrid Automatic Repeat Request Acknowledgment (HARQ ACK) information on the PUSCH. In this case, the UE can proceed to determine the HARQ codebook, which is subsequently used to deliver the HARQ ACK information multiplexed on the PUSCH via Uplink Control Information (UCI). If the UE uses a Type 2 HARQ ACK codebook, the UE responds with the values ​​of the Count Downlink Allocation Indicator (C-DAI) and the Total Downlink Allocation Indicator (T-DAI). C-DAI and T-DAI are provided to the UE via downlink (DL) scheduling downlink control information (DCI) and UL scheduling DCI, where these DCIs are used to schedule resource-overlapping PUCCH and PUSCH.

[0037] Rel-16 specifies the particular timing of the DL and UL DCIs involved in UCI multiplexing scenarios. Specifically, the UE expects to receive the UL DCI of the PUSCH that is scheduled for UCI multiplexing at a monitoring time (MO) after all other DL DCIs scheduled for PUCCHs that have overlapping resources with the PUSCH. While DL DCIs can carry the values ​​of the C-DAI and T-DAI counters, UL DCIs can also carry the value of the T-DAI counter (referred to as UL DAI, denoted as...). This value is used by the UE as an indication of the total number of DCIs scheduled up to the last MO during the process.

[0038] In the 3GPP standard for New Radio (NR), User Equipment (UE) is designed to receive various downlink (DL) signals from a base station (gNB). In NR, the UE receives DL transmissions to retrieve various information from the gNB. For example, the UE receives user data from the gNB, such as the configuration of time and frequency resources known as the Physical Downlink Shared Channel (PDSCH). Specifically, the Media Access Control (MAC) layer provides user data intended to be delivered to the corresponding layer on the UE side. The UE's physical (PHY) layer takes the physical signals received on the PDSCH as input to the PDSCH processing chain, the output of which is fed as input to the MAC layer. Similarly, the UE receives control data from the gNB in ​​a channel known as the Physical Downlink Control Channel (PDCCH). The control data is called Downlink Control Information (DCI) and is converted into PDCCH signals by the PDCCH processing chain on the gNB side. Conversely, the UE transmits uplink (UL) signals to deliver user data or control information, referred to as the Physical Uplink Shared Channel (PUSCH) and Physical Uplink Control Channel (PUCCH), respectively. Specifically, the PUSCH is used by the UE MAC layer to deliver data to the gNB. Furthermore, the PUCCH is used to transmit control data known as Uplink Control Information (UCI), which is converted into PUCCH signals through the PUCCH processing chain on the UE side.

[0039] For the PDSCH channel, the Rel-16 standard of NR allows the use of code blocks (CBs) and code block groups (CBGs). The use of CBs helps reduce the processing complexity of PDSCH, and by grouping the CBs of a transport block (TB) into a maximum of N CBGs per TB, the use of CBGs helps reduce the Hybrid Automatic Repeat Request (HARQ) feedback overhead, where the value of N is configured for each cell. Specifically, the process of transmitting and receiving PDSCH signals on an active cell is as follows.

[0040] On the transmitter side (gNB):

[0041] 1. The gNB decides to schedule PDSCH transmissions to the UE. Transmissions occur on specific resource allocations and have specific PDSCH configurations. Based on the PDSCH allocation, the gNB determines the TB size (TBS).

[0042] 2. Then, the amount of data equal to TBS is allocated as the TB to be sent in PDSCH. The TB is modified using Cyclic Redundancy Check (CRC).

[0043] 3. Then, gNB divides the combination of TB and CRC into smaller data blocks called CBs, where the size of each CB is based on the low-density parity-check (LDPC) code used. The set of CBs is virtually grouped into a set of N non-overlapping CBs, called CBG.

[0044] 4. Modify each CB with an additional CRC, and encode the combination of CB and CRC using the determined LDPC code.

[0045] 5. All CB encoded outputs are rate-matched on available resources for PDSCH transmission.

[0046] On the receiver side (UE):

[0047] 1. The UE extracts the received encoded output of all CBs included in the PDSCH.

[0048] 2. Then, the UE attempts to decode each CB individually.

[0049] 3. For each CBG, if any CB within the CBG fails its corresponding CRC check, a HARQ negative acknowledgment (NACK) is prepared for the UE's feedback transmission. Otherwise, a HARQ acknowledgment (ACK) is prepared.

[0050] 4. Then, the UE transmits a set of HARQ ACK / NACK bits in the UCI sent in the PUCCH signal corresponding to the PDSCH.

[0051] In Rel-16, for each cell, the UE is configured with a maximum number of CBGs per TB via Radio Resource Control (RRC). For a given TB, the set of C CBs is then grouped into M CBGs, where M is at most equal to the maximum number of CBGs per TB per cell. Regarding the transmission of PUCCH containing HARQ feedback, the UE is provided with a timing value k (in timeslots) indicating that PUCCH transmission occurs in timeslot n+k, where n is the timeslot at which PDSCH reception ends. This value k can be configured by RRC or dynamically provided by the scheduling DCI via the PDSCH-to-HARQ_feedback field. The PDSCH-to-HARQ_feedback field can assume any value in the set {1,2,3,4,5,6,7,8}. Alternatively, the value of this field can be mapped to a set of eight values ​​configured by RRC.

[0052] For a given slot n in which a UCI is scheduled to be transmitted by the UE on a PUCCH or PUSCH, multiple candidate locations for PDCCH reception can have corresponding HARQ feedback transmissions in the given slot; these candidate locations are called watch times (MOs). The set of MOs corresponds to all possible MOs that may have already scheduled HARQ ACK information in slot n. Counting the number of possible MOs may include: 1) counting all slots in which a DCI schedules a PDSCH, where the PUCCH corresponding to the PDSCH falls in slot n, and 2) considering the necessary processing time for the PUCCH; for example, a slot with a potential DCI scheduling a PDSCH that does not allow the UE sufficient time to process the PUCCH may not be considered an MO in the set of MOs, where the PUCCH corresponding to the PDSCH is in slot n. When preparing a UCI to be transmitted in a PUCCH or PUSCH, the UE considers all HARQ information bits corresponding to these MOs. The UE prepares the HARQ feedback in the HARQ codebook and then maps it onto the UCI.

[0053] In Rel-16, there are two mechanisms for determining the HARQ codebook: Type I and Type II (also referred to as "Type 1" and "Type 2"). In the Type I HARQ codebook (semi-static), the UE allocates HARQ feedback bits for all possible PDSCH instances that may be transmitted within slot n, including all MOs and active cells, regardless of whether they are actually transmitted. In the Type II HARQ codebook (dynamic), the UE allocates HARQ feedback bits for the MOs and active cells that actually transmit PDSCH.

[0054] The process for determining the Type II HARQ codebook relies on the values ​​of two counters, which are indicated in the DL DCIs received in the MOs within the MO set. These two counters are called the Count Downlink Allocation Indicator (C-DAI) and the Total Downlink Allocation Indicator (T-DAI). The C-DAI value indicated in the DL DCIs received in a MOm within the MO set and in a given serving cell c is used to indicate the total number of increments of the DL DCIs sent by the gNB up to the transmission in that MOm and serving cell c. The C-DAI value is expressed as... The T-DAI value indicated in the DL DCI received in one MOm within the MO set is used to indicate the total number of DLDCIs transmitted by the gNB across all serving cells up to that MOm. The T-DAI value is expressed as...

[0055] For type II HARQ codebooks, in Figure 1A The image shows an example of a Rel-16-based HARQ codebook determination mechanism, illustrating the maximum number of CBGs per TB configured for three serving cells. The scenario involves specific values. The HARQ codebook determination based on Rel-16 is based on the count DAI and the total DAI increasing based on the number of TBs sent. In the scenario shown, the resulting HARQ codebook comprises 56 bits, which is significantly larger than the 19 ACK / NACK feedback bits required to provide feedback for 19 sent CBGs.

[0056] The process of determining the Type II HARQ codebook in Rel-16 is described in section 9.1.3.1 of Rel-16 technical specification 38.213.

[0057] When UCI is multiplexed on PUSCH, the scheduling UL DCI can also carry the T-DAI value (called UL DAI, determined by...). This value (represented by the UL DAI value) is used by the UE during the HARQ codebook determination process. This process replaces the T-DAI value indicated by the DL DCI with the UL DAI value described in section 9.1.3.2 of Rel-16 technical specification 38.213. In Rel-16, the UE interprets the C-DAI and T-DAI values ​​in the DL DCI according to Tables 9.1.3-1 and 9.1.3-1A of Rel-16 technical specification 38.213, and interprets the UL DAI value according to Table 9.1.3-2 of Rel-16 technical specification 38.213.

[0058] However, there is an exception for UL DAI. That is, when When this instruction is received, the UE interprets it as meaning that (i) if the UE receives at least one PDCCH carrying DL DCI or has semi-persistent scheduling (SPS) ACK / NACK bits up to the last MO, the total number of DCIs is 4; and (ii) if the UE does not receive any PDCCH carrying DL DCI up to the last MO and does not have any ACK / NACK bits corresponding to the SPS PDCCH reception, the total number of DCIs is 0. From the UE's perspective, the following two cases are indistinguishable: if the UE does not receive any PDCCH and is instructed to... Then (i) the UE may have lost all scheduled DCIs, in which case, in addition to the SPS ACK / NACK bits (if any), the UE should have also indicated 4 NACKs for the dynamically authorized DG PDSCH; or (ii) there may be no scheduled DCIs, in which case, in addition to the SPS A / N bits (if any), the UE should not send any HARQ feedback bits for those DCIs for the DG PDSCH. (UE) for This interpretation assumes case (ii), which could lead to errors if the actual scheduling is similar to case (i). However, case (i) is likely less likely than case (ii).

[0059] As described above, in Rel-15, for a given PDSCH reception, the UE generates a 1 or 1 PDCCH for either the detected Dynamic Grant (DG) PDSCH or the lost Scheduled DG PDSCH. bits, of which

[0060]

[0061] In the above text, The maximum number of codewords for serving cell c is indicated by the Radio Resource Control (RRC) Information Element (IE) `maxNrofCodeWordsScheduledByDCI`, and... Indicates the number of HARQ-ACK bits per codeword or per transport block (TB) for serving cell c, given by RRC IE maxCodeBlockGroupsPerTransportBlock. A fixed number of HARQ-ACK bits are generated for detected or lost PDCCHs. The reason for this is that the UE may not know how many CBGs have been scheduled in the lost DCI. (Reference) Figure 1BFor illustrative purposes, assume (i) the UE is configured with four serving cells, (ii) for each cell, the maximum number of codewords is equal to 1, and (iii) for component carriers (CC)#1 to CC#4, the maximum number of receiveable CBGs is 2, 3, 4, and 5, respectively. If the UE loses a DCI on CC#3 and detects two other DCIs, the UE will know from the indicated DAI value that it has lost one DCI. However, the UE cannot know on which cell the lost DCI was transmitted. If the lost DCI was transmitted on CC#2, the UE should include 3 NACK bits, and if the lost DCI was transmitted on CC#3, it should include 4 NACK bits. To avoid any mismatch between the UE and gNB in ​​the number of included NACK bits, for each detected or lost PDCCH, the UE can simply include the maximum number of possible CBGs across all cells. Considering the number of codewords in each cell, the UE generates a DCI for each scheduled DCI. One ACK / NACK bit. If the actual number of scheduled CBGs is less than this maximum number, the UE appends zeros.

[0062] Although for each PDSCH including While a single bit can address the payload size mismatch issue, it can become inefficient due to the added zero padding. This inefficiency becomes more pronounced when the maximum number of CBGs configured across different cells varies significantly. For example, if two cells are configured with only one CBG (or TB-based transmission), while two other cells are configured with eight CBGs, each ACK / NACK bit in the first two cells will be appended with seven zero bits. This significantly increases the payload size and negatively impacts PUCCH reliability. To mitigate the zero-padding problem, Rel-15 employs two subcodebooks, such as... Figure 1C As shown in the table, the first subcodebook (subcodebook 1) includes all 1-bit HARQ-ACK bit strings (e.g., concatenated together), while the second subcodebook (subcodebook 2) includes all... A string of HARQ-ACK bits (e.g., concatenated together). For example, if for If a UE is provided with PDSCH-CodeBlockGroupTransmission for a serving cell, it can use subcodebook 2 for those serving cells, and if for If a UE is not provided with PDSCH-CodeBlockGroupTransmission in a serving cell, it can use subcodebook 1 for those serving cells (where...). ).

[0063] Figure 1D An example of a Type 2 HARQ codebook in Rel-15 is shown. Four MOs participate in subcodebook 1, and seven MOs participate in subcodebook 2. The UE generates four HARQ-ACK bits (a1, a2, a3, a4) for the four MOs, corresponding to ordered pairs (formatted as (m = MO index, c = serving cell index)) (0, 2), (1, 1), (2, 0), and (2, 3), respectively. For the remaining MOs, eight bits are generated to obtain the ACK / NACK bit string (b1, b2, b3, b4, b5), where each bit string b... i The length is 8 bits. All four cells participate in the first subcodebook, while only CC#0, CC#2, and CC#3 participate in the second subcodebook. Figure 1D middle, and

[0064] As mentioned above, if the maximum number of CBGs configured per serving cell varies significantly among serving cells, having a fixed HARQ-ACK bit width per serving cell may incur significant overhead on the payload size because the UE may need to append a large number of zero bits. For example, if all serving cells except one are configured with a maximum... One CBG, and the serving cell is configured with If there are CBGs, the UE can generate 8 bits for all MOs and serving cells, including a large number of padding bits. To solve this problem, two sub-codebooks are used in Rel-15, where the first sub-codebook and the second sub-codebook generate 1 or 2 respectively. 1 bit. The subcode is determined by the UE based on... Figure 1C The table is used to determine this.

[0065] In some embodiments, using N subcodebooks allows for more efficient reporting of ACK / NACK bits. Each DCI that schedules DGPDSCH, instructs the SPS to release PDCCH, instructs the secondary cell (Scell) to sleep, or otherwise requires only one ACK / NACK bit for HARQ feedback can be mapped to one of the subcodebooks. Mapping can be accomplished using one or a combination of the following methods: (i) determining the maximum number of RRC configurations for each serving cell's CBG, (ii) searching the space set configuration, (iii) configuring the control resource set (CORESET), (iv) the detected DCI format, (v) DCIs that instruct the SPS to release or the Scell ​​to sleep, or any DCIs that do not schedule PDSCH when the UE is configured to report the HARQ_ACK bit for the PDCCH carrying the DCI, are mapped to the first subcodebook, and (vi) the SPS PDSCH is mapped to the first subcodebook.

[0066] Codebook construction can be performed as follows. The UE can be configured with N sub-codebooks via RRC; namely, sub-codebook 0, sub-codebook 1, ..., sub-codebook N-1, and corresponding maximum number of A / N bits L0, L1, ..., L... N-1 The UE constructs the CB as follows, if for For each serving cell, the UE was provided with PDSCH-CodeBlockGroup Transmission; and for... The service cell was not provided with PDSCH-CodeBlockGroupTransmission (of which... ).

[0067] for In a cell, subcodebook 0 can be constructed for (i) SPS PDSCH release of PDCCH, (ii) SPSPDSCH reception, (iii) any DCI format indicating Scell ​​sleep, and (iv) in Any TB-based PDSCH reception on a cell or Any PDSCH received on a cell, or (v) any DCI format that transmits UE unicast control information without scheduling PDSCH. For each of the above categories (i) to (v), the UE generates L0 ACK / NACK bits.

[0068] For a subcodebook n∈{1,…,N-1}, (i) Replaced with in yes The maximum number of CBGs configured in each cell Make The number of cells, and (ii) the ACK / NACK bits of the PDSCH scheduled by the UE, which are padded (e.g., with zero bits) to generate the L for each DG PDSCH, including (e.g., composed of) these bits. n A bit string of ACK / NACK bits. As used in this article, “padded” a set of m bits to form a bit string of length n means (i) if m is less than n, then add nm padding bits to the set of m bits, or (ii) if m equals n, then do not add padding bits (i.e., keep the set of m bits unchanged).

[0069] For each subcodebook, the C-DAI and T-DAI values ​​are calculated separately. For subcodebook 0, the ACK / NACK bits of the SPS PDSCH are appended to the other ACK / NACK bits. The UE generates the final CB payload by appending the ACK / NACK bits of the subcodebooks to each other, starting from subcodebook 0. In some embodiments, L0 = 1, which means that only one ACK / NACK bit is generated for the PDSCH and PDCCH.

[0070] Figure 2A An example of a 4-subcodebook, i.e., N=4, dynamic HARQ-ACK codebook, is described. The subcodebook is determined by RRC parameters that determine the maximum number of codewords per serving cell and the maximum number of CBGs per serving cell, or based on DCI format, etc. Figure 2A This corresponds to a configuration with four subcodebooks, (L0, L1, L2, L3) = (2, 4, 6, 8). Using this configuration, the quantity... All DCIs of cells with 2 or fewer cells, as well as all DCIs for scheduling based on TB such as PDSCH, SPS releasing PDCCH, and Scell ​​hibernation, are mapped to subcodebook 1. DCIs of cells with more than 2 cells and less than or equal to 4 cells are mapped to subcodebook 2. DCIs of cells with more than 4 cells and less than or equal to 6 cells are mapped to subcodebook 3, and DCIs of cells with more than 6 cells and less than or equal to 8 cells are mapped to subcodebook 4. This mapping is not only based on… The value is also based on the DCI format and the type of information carried by the DCI. Specifically, on cells CC#3 and CC#5, only the DCI format of TB-based PDSCH (or SPS release) has been detected, which is mapped to subcodebook 1.

[0071] In some embodiments, a significant reduction in payload size is possible. A properly designed m-subcode HARQ-ACK codebook ensures that the payload size decreases as the number of subcodebooks m increases. Compared to a HARQ codebook with only one subcodebook, in Figure 2A In the described scheduling scenario, a 1-subcodebook HARQ-ACK codebook generates 31×8=248 bits, while a 4-subcodebook HARQ-ACK codebook generates 10×2+6×4+7×6+8×8=150 bits, which results in a reduction of the payload size by approximately 40%.

[0072] Generally, the reliability of the method using each subcodebook is likely related to the bit width of the DAI field and the number of scheduled PDSCHs whose HARQ-ACK bits will be multiplexed in a time slot. Roughly speaking, if the scheduling conditions of each subcodebook make the total number of scheduled PDSCHs or PDCCHs in the subcodebook too small, then losing all DCIs will result in a HARQ_ACK payload size mismatch, regardless of the bit width. However, in a heavy CA framework with a large number of scheduled PDSCHs within each subcodebook, increasing the bit width of the DAI field can increase the reliability of the subcodebook. However, even with an increased bit width, if the number of PDCCHs is too large, the probability of losing a certain number of PDCCHs in a row also increases, so the gNB should ensure that the number of PDCCHs within each subcodebook is not too large. This condition can be ensured by the gNB by configuring a sufficiently large number of subcodebooks for the UE.

[0073] In some embodiments, the network can send an additional DAI field in the DCI, which can improve reliability. In the basic form of multi-subcodebook CB, the DCI only provides C-DAI and T-DAI for the indicated subcodebook. That is, there is only one DAI field in the DCI, regardless of the number of subcodebooks configured. For this form, there may be no protection across subcodebooks. As mentioned above, the reliability of each subcodebook may be reduced, especially when the number of scheduled PDSCHs is small. To mitigate reliability issues, the gNB can configure an additional DAI field in the DCI to provide protection for other unscheduled subcodebooks. For example, the gNB can set the DAI value of other subcodebooks to be equal to the latest DAI value corresponding to the subcodebook. Generally, either of the following two options can be implemented.

[0074] In the first option, N subcodebooks are used, and the DCI includes N distinct DAI fields. The DAI used for the scheduled subcodebook is incremented starting from the latest PDCCH of the participating subcodebook based on the MO and serving cell index in the type 2 HARQ-ACK CB pseudocode. Based on the MO and cell index, each DAI value of an unscheduled subcodebook is equal to the latest DAI value corresponding to that subcodebook.

[0075] In the second option, with N codebooks utilized, DCI includes two DAI fields. One field is associated with the scheduled codebook i, while the other field is associated with another codebook j, wherein j is a function of i, and the function may be (i) configured for the UE via RRC, or (ii) a specific fixed formula. More generally, DCI may include M<N fields, wherein one DAI corresponds to the scheduled codebook, and the other M-1 fields are associated with certain unscheduled codebooks, and the association is given by a specific rule such as RRC configuration or a fixed formula.

[0076] In some embodiments, the pseudocode for Type 2 HARQ-ACK CB (included in Section 9.1.3.1 of Technical Specification 38.213 of Rel-16) may be modified to accommodate the transmission of an additional DAI. In one approach, only the T-DAI corresponding to the last MO index of the unscheduled codebook can be included in DCI, and the UE uses this T-DAI to override the latest T-DAI directly indicated by DCI for the codebook.

[0077] Figure 2B An example of how including an additional T-DAI can help the UE determine the correct payload size is shown. It can be seen that when no additional T-DAI is included, if the UE misses two DCIs of the first codebook, the payload size of the first codebook is incorrect. However, the gNB may be configured to include an additional T-DAI in the scheduling DCI of the codebook, such that in any MO, the value of the additional T-DAI ( Figure 2B the third element of each triplet shown therein) indicates the value of the T-DAI of another codebook. In the case of including an additional T-DAI, if the UE misses two DCIs of the first codebook in the last MO, it can determine the correct payload size of the first codebook as long as it detects at least one of the two DCIs of the second codebook in the last MO, because each of these DCIs contains the value of the T-DAI of the first codebook (i.e., the value 4) as the last element of the triplet.

[0078] Figure 3A flowchart of the method is shown. In some embodiments, at 305, the UE receives one or more first transmissions; at 310, the UE decodes the first transmissions to generate a first subcodebook including one or more corresponding Hybrid Automatic Repeat Request Acknowledgment (HARQ ACK) bit strings, each having a first length; at 315, the UE receives one or more second transmissions; at 320, the UE decodes the second transmissions to generate a second subcodebook including one or more corresponding HARQ ACK bit strings, each having a second length greater than the first length; at 325, the UE receives one or more third transmissions; and at 330, the UE decodes the third transmissions to generate a third subcodebook including one or more corresponding HARQ ACK bit strings, each having a third length greater than the second length. For ease of illustration, in Figure 3 In this context, the reception of the first, second, and third transmissions is described as occurring in sequence; however, in general, transmissions can be received in any order, for example, some of the third transmissions can be received after some of the first transmissions and before some of the first transmissions. Figure 4 A system including a UE 405 and a gNB 410 communicating with each other is illustrated. The UE may include a radio device 415 and processing circuitry (or components for processing) 420, which can perform various methods disclosed herein, such as Figure 3 The method is illustrated. For example, the processing circuit 420 can receive transmissions from the network node (gNB) 410 via the radio device 415, and the processing circuit 420 can send signals to the gNB 410 via the radio device 415.

[0079] As used herein, “a part” of something means “at least some” of that thing, and can also mean less than or all of that thing. Similarly, “a part” of something, as a special case, includes the whole thing, that is, an example where the whole thing is a part of that thing. As used herein, the term “or” should be interpreted as “and / or”, such that, for example, “A or B” means either “A” or “B” or “A and B”.

[0080] The terms “processing circuitry” and “components for processing” are used herein to refer to any combination of hardware, firmware, and software used for processing data or digital signals. Processing circuitry hardware may include, for example, application-specific integrated circuits (ASICs), general-purpose or special-purpose central processing units (CPUs), digital signal processors (DSPs), graphics processing units (GPUs), and programmable logic devices such as field-programmable gate arrays (FPGAs). As used herein, in processing circuitry, each function is either performed by hardware configured to (i.e., hardwired) perform that function or by more general-purpose hardware (such as a CPU) configured to execute instructions stored in a non-transitory storage medium. Processing circuitry may be fabricated on a single printed circuit board (PCB) or distributed across several interconnected PCBs. Processing circuitry may include other processing circuitry; for example, processing circuitry may include two processing circuits, an FPGA and a CPU, interconnected on a PCB.

[0081] As used herein, when a method (e.g., adjustment) or a first quantity (e.g., a first variable) is referred to as “based on” a second quantity (e.g., a second variable), it means that the second quantity is an input to the method or affects the first quantity. For example, the second quantity may be an input to a function that computes the first quantity (e.g., a unique input or one of several inputs), or the first quantity may be equal to the second quantity, or the first quantity may be the same as the second quantity (e.g., the first quantity and the second quantity are stored in one or more locations in memory).

[0082] It should be understood that although the terms "first," "second," "third," etc., may be used herein to describe various elements, components, regions, layers, and / or portions, these elements, components, regions, layers, and / or portions should not be limited by these terms. These terms are used only to distinguish one element, component, region, layer, or portion from another element, component, region, layer, or portion. Therefore, without departing from the spirit and scope of the inventive concept, the first element, component, region, layer, or portion discussed herein may be referred to as the second element, component, region, layer, or portion.

[0083] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of the invention. As used herein, the terms “substantially,” “approximately,” and similar terms are used as approximate terms rather than terms of degree and are intended to account for the inherent biases of measurements or calculations that would be recognized by one of ordinary skill in the art.

[0084] As used herein, the singular forms “a” and “an” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “including” are used in this specification, they specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more associated items. When expressions such as “at least one of…” are used after a list of elements, the entire list of elements is modified, not individual elements in the list. Furthermore, when describing embodiments of the inventive concept, the use of “may” means “one or more embodiments of this disclosure.” Additionally, the term “exemplary” is intended to refer to an example or illustration. As used herein, the terms “use,” “with,” and “being used” may be considered synonymous with the terms “utilize,” “using,” and “being exploited,” respectively.

[0085] It should be understood that when a component or layer is referred to as "on another component or layer," "connected to," "coupled to," or "adjacent to" another component or layer, it can be directly on, directly connected to, coupled to, or adjacent to another component or layer, or one or more intermediate components or layers may exist. Conversely, when a component or layer is referred to as "directly on another component or layer," "directly connected to," "directly coupled to," or "immediately adjacent to" another component or layer, no intermediate components or layers exist.

[0086] Although exemplary embodiments of systems and methods for processing authentication in wireless systems have been specifically described and illustrated herein, various modifications and variations will be apparent to those skilled in the art. Therefore, it should be understood that systems and methods for processing authentication in wireless systems constructed in accordance with the principles of this disclosure can be implemented in ways other than those specifically described herein. The invention is also defined in the appended claims and their equivalents.

Claims

1. A method for processing acknowledgments in a wireless system, comprising: The user equipment (UE) receives one or more first transmissions; The UE decodes the first transmission to generate a first subcodebook comprising one or more corresponding HARQ ACK bit strings, wherein each of the one or more corresponding HARQ ACK bit strings of the first subcodebook has a first length based on a first maximum number of code block groups (CBG) per transport block (TB). The UE receives one or more second transmissions; The UE decodes the second transmission to generate a second subcodebook comprising one or more corresponding HARQ ACK bit strings, wherein each of the one or more corresponding HARQ ACK bit strings of the second subcodebook has a second length, the second length being based on a second maximum number of code block groups CBG per transport block TB and greater than the first length; The UE receives one or more third transmissions; and The UE decodes the third transmission to generate a third subcodebook comprising one or more corresponding HARQ ACK bit strings, wherein each of the one or more corresponding HARQ ACK bit strings of the third subcodebook has a third length, the third length being based on a third maximum number of code block groups (CBG) per transport block (TB) and greater than the second length.

2. The method according to claim 1, wherein, The first length is 1.

3. The method according to claim 1, wherein, Each of the first length, the second length, and the third length is configured via Radio Resource Control (RRC).

4. The method according to claim 1, wherein, The generation of the third subcodebook includes: Receive a code block group (CBG) having a number of code blocks greater than the second length and less than or equal to the third length; Generate a set of HARQ ACK bits corresponding to a specific code block group within the code block group; and The set of HARQ ACK bits is padded to form a HARQ ACK bit string with a third length.

5. The method according to claim 1, wherein, The generation of the second subcodebook includes: Receive a code block group (CBG) having a number of code blocks greater than a first length and less than or equal to a second length; Generate a set of HARQ ACK bits corresponding to a specific code block group within the code block group; and The set of HARQ ACK bits is padded to form a HARQ ACK bit string with a second length.

6. The method according to claim 1, further comprising: Receive the count downlink allocation indicator C-DAI for the second transmission and the total downlink allocation indicator T-DAI for the second transmission; Based on C-DAI and T-DAI, the transmission loss in the second transmission is determined; as well as The second subcodebook includes a bit string with a second length of negative acknowledgment bits.

7. The method according to claim 6, further comprising: Receive a third transmission of C-DAI and a third transmission of T-DAI, wherein the third transmission of C-DAI is different from the second transmission of C-DAI, and the third transmission of T-DAI is different from the second transmission of T-DAI; Based on the C-DAI and T-DAI of the third transmission, determine the transmission loss in the third transmission; as well as The second subcodebook includes a bit string with a third negative acknowledgment bit.

8. The method according to claim 6, further comprising: Receive the third transmission of T-DAI using the second transmission of C-DAI and the second transmission of T-DAI; Based on the C-DAI and T-DAI of the third transmission, determine the transmission loss in the third transmission; as well as The second subcodebook includes a bit string with a third negative acknowledgment bit.

9. The method according to claim 1, further comprising: The UE receives one or more fourth transmissions; as well as The UE decodes the fourth transmission to generate a fourth subcodebook, which includes one or more corresponding HARQ ACK bit strings, each having a fourth length greater than the third length.

10. A user equipment (UE), comprising: Radio equipment; as well as Processing circuit, The processing circuit is configured as follows: Receive one or more first transmissions; Decode the first transmission to generate a first subcodebook comprising one or more corresponding HARQ ACK bit strings, wherein each of the one or more corresponding HARQ ACK bit strings of the first subcodebook has a first length, the first length being based on a first maximum number of code block groups (CBG) per transport block (TB). Receive one or more second transmissions; Decode the second transmission to generate a second subcodebook comprising one or more corresponding HARQ ACK bit strings, wherein each of the one or more corresponding HARQ ACK bit strings of the second subcodebook has a second length, the second length being based on a second maximum number of code block groups CBG per transport block TB and greater than the first length; Receive one or more third transmissions; and The third transmission is decoded to generate a third subcodebook comprising one or more corresponding HARQ ACK bit strings, wherein each of the one or more corresponding HARQ ACK bit strings of the third subcodebook has a third length, the third length being based on a third maximum number of code block groups (CBG) per transport block (TB) and greater than the second length.

11. The UE according to claim 10, wherein, The first length is 1.

12. The UE according to claim 10, wherein, Each of the first length, the second length, and the third length is configured via Radio Resource Control (RRC).

13. The UE according to claim 10, wherein, The generation of the third subcodebook includes: Receive a code block group (CBG) having a number of code blocks greater than the second length and less than or equal to the third length; Generate a set of HARQ ACK bits corresponding to a specific code block group within the code block group; and The set of HARQ ACK bits is padded to form a HARQ ACK bit string with a third length.

14. The UE according to claim 10, wherein, The generation of the second subcodebook includes: Receive a code block group (CBG) having a number of code blocks greater than a first length and less than or equal to a second length; Generate a set of HARQ ACK bits corresponding to a specific code block group within the code block group; and The set of HARQ ACK bits is padded to form a HARQ ACK bit string with a second length.

15. The UE according to claim 10, wherein, The processing circuit is further configured to: Receive the count downlink allocation indicator C-DAI for the second transmission and the total downlink allocation indicator T-DAI for the second transmission; Based on C-DAI and T-DAI, the transmission loss in the second transmission is determined; as well as The second subcodebook includes a bit string with a second length of negative acknowledgment bits.

16. The UE according to claim 15, wherein, The processing circuit is further configured to: Receive a third transmission of C-DAI and a third transmission of T-DAI, wherein the third transmission of C-DAI is different from the second transmission of C-DAI, and the third transmission of T-DAI is different from the second transmission of T-DAI; Based on the C-DAI and T-DAI of the third transmission, determine the transmission loss in the third transmission; as well as The second subcodebook includes a bit string with a third negative acknowledgment bit.

17. The UE according to claim 15, wherein, The processing circuit is further configured to: Receive the third transmission of T-DAI using the second transmission of C-DAI and the second transmission of T-DAI; Based on the C-DAI and T-DAI of the third transmission, determine the transmission loss in the third transmission; as well as The second subcodebook includes a bit string with a third negative acknowledgment bit.

18. The UE according to claim 10, wherein, The processing circuit is further configured to: The UE receives one or more fourth transmissions; and The UE decodes the fourth transmission to generate a fourth subcodebook, which includes one or more corresponding HARQ ACK bit strings, each having a fourth length greater than the third length.

19. A user equipment (UE), comprising: Radio equipment; as well as Components used for processing The component for processing is configured as follows: Receive one or more first transmissions; Decode the first transmission to generate a first subcodebook comprising one or more corresponding HARQ ACK bit strings, wherein each of the one or more corresponding HARQ ACK bit strings of the first subcodebook has a first length, the first length being based on a first maximum number of code block groups (CBG) per transport block (TB). Receive one or more second transmissions; Decode the second transmission to generate a second subcodebook comprising one or more corresponding HARQ ACK bit strings, wherein each of the one or more corresponding HARQ ACK bit strings of the second subcodebook has a second length, the second length being based on a second maximum number of code block groups CBG per transport block TB and greater than the first length; Receive one or more third transmissions; and The third transmission is decoded to generate a third subcodebook comprising one or more corresponding HARQ ACK bit strings, wherein each of the one or more corresponding HARQ ACK bit strings of the third subcodebook has a third length, the third length being based on a third maximum number of code block groups (CBG) per transport block (TB) and greater than the second length.

20. The UE according to claim 19, wherein, The first length is 1.

Images