Dynamic Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) Codebook Decision

Abstract

Systems, apparatus, methods, and computer-readable media are provided for dynamic Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) feedback for multi-cell scheduling (e.g., downlink control information (DCI) for scheduling a Physical Downlink Shared Channel (PDSCH) and / or a Physical Uplink Shared Channel (PUSCH) on multiple cells). Embodiments may include techniques for determining a downlink assignment index (DAI) and / or a HARQ-ACK codebook, e.g., a type-1, type-2, and / or type-3 codebook, for multi-cell scheduling. Other embodiments may be described and claimed.

Description

[Technical field]

[0001] This application claims priority to International Patent Application No. PCT / CN2022 / 075311, filed on February 2, 2022, and International Patent Application No. PCT / CN2022 / 102278, filed on June 29, 2022.

[0002] Various embodiments may relate generally to the field of wireless communications. For example, some embodiments may relate to dynamic hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook determination. [Background technology]

[0003] New Radio (NR) supports a wide range of spectrum in different frequency ranges. It is expected that the availability of spectrum will increase in the 5G Advanced market, possibly due to refarming from bands originally used in previous cellular generation networks. Especially in Frequency Range 1 (FR1) bands, the available spectrum blocks tend to be more fragmented and scattered with narrower bandwidths. In Frequency Range 2 (FR2) bands and some FR1 bands, the available spectrum may be wider, such that intra-band multi-carrier operation is necessary. To meet different spectrum needs, it is important to ensure that these scattered spectrum bands or wider bandwidth spectrum can be utilized in a more spectrum / power efficient and flexible manner, thus providing higher throughput and adequate coverage in the network. [Brief description of the drawings]

[0004] [Figure 1A]1A and 1B illustrate an example of a Physical Downlink Control Channel (PDCCH)-based Downlink Allocation Index (DAI) and Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) mapping according to a reference cell, in accordance with various embodiments. [Figure 1B] 1A and 1B illustrate an example of a Physical Downlink Control Channel (PDCCH)-based Downlink Allocation Index (DAI) and Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) mapping according to a reference cell, in accordance with various embodiments. [Figure 2A] 2A and 2B show examples of separate HARQ-ACK mapping for each cell scheduled by multi-cell scheduling, according to various embodiments. [Figure 2B] 2A and 2B show examples of separate HARQ-ACK mapping for each cell scheduled by multi-cell scheduling, according to various embodiments. [Diagram 3] 1 illustrates an example of DAI and HARQ-ACK mapping for a Type 2 codebook in accordance with various embodiments. [Figure 4] 1 illustrates another example of DAI and HARQ-ACK mapping for a Type-2 codebook in accordance with various embodiments. [Figure 5A] 1 illustrates an example of one DAI and HARQ-ACK mapping in one DCI for different sub-codebooks according to various embodiments. [Figure 5B] 1 illustrates an example of two DAI and HARQ-ACK mappings in one DCI for different sub-codebooks according to various embodiments. [Figure 6] 1 illustrates a network in accordance with various embodiments. [Figure 7] 1 illustrates a schematic diagram of a wireless network in accordance with various embodiments. [Figure 8]FIG. 1 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods described herein, according to some example embodiments. [Figure 9] 1 illustrates an example procedure for implementing various embodiments described herein. [Figure 10] 1 illustrates another example of a procedure for implementing various embodiments described herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0005] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different figures to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to one of ordinary skill in the art having the benefit of this disclosure that various aspects of the various embodiments may be implemented in other examples that depart from those specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0006] Various embodiments herein may provide techniques for hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback for multi-cell scheduling. For example, embodiments may include techniques for determining a downlink assignment index (DAI) and / or a HARQ-ACK codebook, such as a type-1, type-2, and / or type-3 codebook, for multi-cell scheduling.

[0007] It is desirable to increase flexibility and spectrum / power efficiency in scheduling data across multiple cells, including intra-band and inter-band cells. Current scheduling mechanisms only allow scheduling of a single cell's Physical Uplink Shared Channel (PUSCH) / Physical Downlink Shared Channel (PDSCH) per scheduling downlink control information (DCI). With more available sparse spectrum bands or wider bandwidth spectrum, simultaneous scheduling of multiple cells is required. To reduce control overhead, it is beneficial to extend from single-cell scheduling to multi-cell PUSCH / PDSCH scheduling using a single scheduling DCI. More specifically, a DCI is used to schedule PDSCH or PUSCH transmissions in two or more cells or component carriers (CCs), with each PDSCH or PUSCH scheduled in one cell or CC.

[0008] Various embodiments herein provide a mechanism for dynamic HARQ-ACK codebook (type 2 HARQ-ACK codebook) determination for multi-cell scheduling (e.g., for PDSCH). For example, aspects of various embodiments include: · Downlink Allocation Index (DAI) determination for Type-2 HARQ-ACK feedback; · Sub-codebook decision for Type-2 HARQ-ACK feedback; Includes.

[0009] In NR systems, the DCI only schedules one PDSCH or multiple PDSCHs on the active downlink (DL) bandwidth portion (BWP) of a cell. For each scheduled PDSCH, the UE generates a HARQ-ACK codebook and reports the HARQ-ACK via the PUCCH.

[0010] There may be several different ways to generate the HARQ-ACK codebook. One example is to generate the HARQ-ACK codebook according to semi-statically configured parameters, such as HARQ-ACK feedback timing K1 set, time domain resource allocation (TDRA) for each serving cell, etc. Such a HARQ-ACK codebook is defined as a type-1 HARQ-ACK codebook. Another example is to generate the HARQ-ACK codebook according to dynamic scheduling, such as HARQ-ACK feedback according to the received K1 indication (PDSCH-to-HARQ_feedback timing indicator in DCI), Counter Downlink Assignment Index (C-DAI) and Total DAI (T-DAI) in DCI, etc. Such a HARQ-ACK codebook is defined as a type-2 HARQ-ACK codebook. Another example is to generate the HARQ-ACK codebook according to semi-statically configured HARQ processes and serving cells, which is also known as a type-3 HARQ-ACK codebook.

[0011] With DCI for multi-cell scheduling, DL transmissions on multiple cells can be scheduled by a single DCI. A transport block (TB) scheduled by DCI for multi-cell scheduling can only be mapped to time / frequency resources on one of the multiple cells. In other words, PDSCHs on different cells are considered as different PDSCHs carrying different TBs. For each PDSCH, one or two TBs can be scheduled.

[0012] For DCI scheduling PDSCH / PUSCH in multiple cells, the PDSCH / PUSCH scheduled by a single DCI can be divided into N PDSCH / PUSCH groups. For example, N=2. Within a PDSCH / PUSCH group, there may be PDSCH / PUSCH on one or multiple serving cells. One particular example is N=1. In one example, the gNB configures N. In another example, N=1 by default.

[0013] The multi-cell scheduling DCI format carrying DL allocation may indicate a single or N values ​​of K1 slot offset (PDSCH-to-HARQ_feedback timing indicator) and PUCCH resource indicator (PRI) for transmission of HARQ-ACK feedback corresponding to each of the scheduled PDSCH groups. To determine the PUCCH UL slot / sub-slot, the K1 slot offset indicates the slot or sub-slot offset from the slot carrying the corresponding reference PDSCH in the respective scheduled PDSCH group to the corresponding PUCCH carrying the HARQ-ACK feedback, or from the slot carrying the scheduling PDCCH for multi-cell scheduling to the corresponding PUCCH carrying the HARQ-ACK feedback.

[0014] For Type-2 HARQ-ACK codebook (Dynamic CB), the UE generates a HARQ-ACK for each PDSCH according to the K1 value indicated in each DCI that schedules the PDSCH and the Downlink Allocation Indicator (DAI) in the DCI. A DCI can schedule a single PDSCH or can schedule multiple PDSCHs on multiple cells.

[0015] In the following, for DAI determination and sub-codebook determination, in the case of a DCI format that supports multi-cell scheduling, if the DCI format schedules only a single cell, the DCI is considered to be single-cell scheduled. In the case of a DCI format that supports only single-cell scheduling (the DCI format does not support multi-cell scheduling), the DCI is considered to be single-cell scheduled.

[0016] DAI decision In one embodiment, for Type-2 HARQ-ACK CB, the multi-cell scheduling DCI format may indicate a single value of C-DAI and T-DAI to indicate the respective positions of the corresponding HARQ-ACK bits in the HARQ-ACK CB. The HARQ-ACK for PDSCH is mapped to the same HARQ-ACK codebook. The DAI in the DCI is determined by the reference serving cell index. In this case, the multi-cell scheduling DCI format carrying DL allocation may indicate a single K1 slot offset and PRI value for the transmission of HARQ-ACK feedback.

[0017] In one option, the value of the C-DAI field in the DCI format represents the cumulative number of {serving cell, PDCCH monitoring opportunity} pairs for which (one or more) PDSCH reception, SPS PDSCH release, or SCell dormancy indications associated with the DCI format exist for the current reference serving cell and up to the current PDCCH monitoring opportunity. For example, the C-DAI may be - first, when the UE supports two or more PDSCH receptions on a serving cell scheduled from the same PDCCH monitoring occasion, counted in ascending order of PDSCH reception start times for the same {reference serving cell, PDCCH monitoring occasion} pair; - secondly, counted in ascending order of reference serving cell index; - third, counting in ascending order of PDCCH monitoring opportunity index m, where 0 ≤ m <Mである。

[0018] For DCIs that do not schedule a PDSCH for any cell, such as an SPS release or SCell dormancy indication, the reference serving cell is the serving cell from which the PDCCH is received. In one example, the DCI format for multi-cell scheduling cannot be used without scheduling a PDSCH. In another example, the DCI format for multi-cell scheduling can be used without scheduling a PDSCH only if the multi-cell scheduling DCI format schedules a single cell, such as when the carrier indicator bit field indicates a single cell. In another example, the DCI format for multi-cell scheduling can be used without scheduling a PDSCH if the multi-cell scheduling DCI schedules a single or multiple cells.

[0019] In single cell scheduling DCI for PDSCH, the reference serving cell is the serving cell from which the PDSCH is received.

[0020] In a multi-cell scheduling DCI for PDSCH, the reference serving cell is one cell among the multiple cells scheduled by a single DCI. The reference serving cell is determined according to at least one of the following mechanisms: - the reference cell is a serving cell for a reference PDSCH for determining a UL slot for a PUCCH; · If there are two or more reference PDSCHs for determining the UL slot for the PUCCH, select one of the cells as the reference cell according to a specific cell index or according to a specific start or end position, as follows: - The reference cell is selected according to a specific cell index, e.g. The scheduled cell with the lowest cell index, or The scheduled cell with the lowest cell index in the PDSCH group, or The scheduled cell with the lowest cell index in the reference PDSCH group; The reference cells are selected according to a specific start or end position, e.g. The scheduled cell with the last to terminate PDSCH based on the Time Domain Resource Allocation (TDRA) bit field in the DCI and / or SCS; The scheduled cell with the PDSCH with the earliest start symbol based on the Time Domain Resource Allocation (TDRA) bit field in the DCI and / or SCS; · If two PDSCHs have aligned start and / or end symbols, the reference cell is selected according to a specific cell index as provided above; - The reference cell is set by the higher layer.

[0021] In multiple PDSCH scheduling by DCI, the PDSCHs are associated with the same C-DAI, and the HARQ-ACK bits for the multiple PDSCHs are arranged according to a predetermined rule, for example, according to the cell index order.

[0022] If the UE supports two or more PDSCH receptions on serving cells scheduled from the same PDCCH monitoring occasion, and at least one PDSCH reception is scheduled by a multi-cell scheduling DCI, and the serving cell is a reference serving cell for multi-cell scheduling, the DAI is counted in ascending order of the PDSCH reception start times for the same {reference serving cell, PDCCH monitoring occasion} pair.

[0023] FIG. 1A provides an example. In case of DCI, the reference cell is the cell of the reference PDSCH for determining the UL slot for PUCCH. If there are more than one reference PDSCH, the cell with the lowest cell index for the reference PDSCH is the reference cell. For PDCCH on serving cell 1, the reference serving cell is cell #3, and for PDCCH on serving cell 2, the reference serving cell is cell #1. Then, the DAI is counted for PDCCH in ascending order of reference serving cell index, so the DAI in PDCCH on serving cell 1 is 2, and the DAI in PDCCH on serving cell 2 is 1. If C-DAI=1, the HARQ-ACK for PDSCH on cell 1 is placed before the HARQ-ACK for PDSCH on cell 4. If C-DAI=2, the HARQ-ACK for PDSCH on cell 2 is placed before the HARQ-ACK for PDSCH on cell 3.

[0024] In one example, the reference cell is selected from the scheduled cells without considering an enabled or disabled PDSCH on the scheduled cells, while in another example, the reference cell is selected only among the scheduled cells that have a enabled PDSCH.

[0025] In another option, the value of the C-DAI field in the DCI format indicates that the cumulative number of (one or more) PDSCH reception, SPS PDSCH release, or SCell dormancy indications associated with the DCI format exists up to the current reference serving cell or the first cell scheduled on the current reference serving cell with the same DCI and current PDCCH monitoring opportunity.

[0026] In multiple PDSCH scheduling with DCI, the HARQ-ACK bits for the PDSCHs are ordered according to a predefined rule, for example according to the cell index order.

[0027] FIG. 1B provides an example. For DCI, the reference cell is the cell of the reference PDSCH for determining the UL slot for PUCCH. If there are more than one reference PDSCH, the cell with the lowest cell index for the reference PDSCH is the reference cell. For PDCCH on serving cell 1, the reference serving cell is cell #3, and for PDCCH on serving cell 2, the reference serving cell is cell #1. Then, the DAI is counted for PDSCH in ascending order of reference serving cell index, so the DAI in PDCCH on serving cell 1 is 3 (because there are two PDSCHs associated with PDCCH on serving cell 2), and the DAI in PDCCH on serving cell 2 is 1. If C-DAI=1, the HARQ-ACK for PDSCH on cell 1 is placed before the HARQ-ACK for PDSCH on cell 4. For C-DAI=3, the HARQ-ACK for the PDSCH on cell 2 is placed before the HARQ-ACK for the PDSCH on cell 3.

[0028] In one embodiment, in case of Type-2 HARQ-ACK CB (Dynamic CB), the multi-cell scheduling DCI format may indicate N values ​​of C-DAI and T-DAI to indicate the respective positions of the corresponding HARQ-ACK bits in the HARQ-ACK CB. It is also noted that in this case, HARQ-ACKs for all PDSCHs in the same PDSCH group are associated with the same HARQ-ACK CB, but HARQ-ACK bits for different PDSCH groups are not necessarily mapped to the same HARQ-ACK CB. That is, HARQ-ACK bits may be carried on different PUCCHs depending on the K1 slot offset value, the relative numerology of DL serving cell and PUCCH cell, and the time domain resource allocation (TDRA) of each PDSCH group.

[0029] If the HARQ-ACKs of N PDSCH groups are associated with the same HARQ-ACK CB, the DAI counts the PDSCHs in the same codebook. The DAI for each PDSCH group is ordered according to the PDSCH group index or according to the reference cell within each PDSCH group index. For example, if the reference cell index of PDSCH group 1 is greater than the reference cell index of PDSCH group 2, the DAI for PDSCH group 2 is 1 and the DAI for PDSCH group 1 is 2.

[0030] If the HARQ-ACKs of the N PDSCH groups are associated with different HARQ-ACK CBs, the DAI counts the PDSCHs for each codebook respectively.

[0031] In one option, the C-DAI and T-DAI may be indicated separately for multiple PDSCH groups scheduled by the DCI. If the PDSCHs associated with each C-DAI are associated with different HARQ-ACK codebooks or different HARQ-ACK sub-codebooks, the C-DAI is counted separately within each codebook or sub-codebook.

[0032] For example, as shown in FIG. 2A, two cells with non-consecutive cell indexes #1 and #3 are scheduled by DCI for multi-cell scheduling, and these two cells are associated with the same PUCCH for HARQ-ACK feedback. Separate C-DAIs are indicated for PDSCHs on the two cells on the two PDSCH groups, otherwise the UE may not know that there is another PDSCH on cell #2 scheduled by another DCI. The two PDSCHs scheduled by DCI for multi-cell scheduling have C-DAIs equal to 1 and 3, and the PDSCH on cell #2 uses C-DAI equal to 2. The HARQ-ACK for the PDSCH on cell #1 is placed in the first position in the HARQ-ACK codebook, followed by the HARQ-ACK for the PDSCH on cell #2. The HARQ-ACK for the PDSCH on cell #3 is placed in the last position in the HARQ-ACK codebook.

[0033] For example, as shown in FIG. 2B, two cells with non-consecutive cell indexes #1 and #3 are scheduled by DCI for multi-cell scheduling, and these two cells are associated with different PUCCHs for HARQ-ACK feedback. Separate C-DAIs are shown for PDSCHs on two cells on two PDSCH groups. The two PDSCHs scheduled by DCI for multi-cell scheduling have C-DAIs equal to 1 and 1, and the PDSCH on cell #2 uses C-DAI equal to 2. The HARQ-ACK for the PDSCH on cell #1 is placed in the first position in the HARQ-ACK codebook in PUCCH1, followed by the HARQ-ACK for the PDSCH on cell #2. The HARQ-ACK for the PDSCH on cell #3 is placed in the first position in the HARQ-ACK codebook in PUCCH2.

[0034] In one option, the C-DAI may be indicated separately for multiple PDSCHs scheduled by the DCI, but a single T-DAI is signaled within the DCI for multi-cell scheduling. Corresponding to the transmission of the DCI, the T-DAI may be incremented by taking into account all PDSCHs associated with the same PUCCH.

[0035] Also, in one example, the earliest symbol of a PUCCH or PUSCH transmission carrying a corresponding HARQ-ACK feedback should not be earlier than T symbols from the end of the later-ending PDSCH, taking into account the impact from timing advance, where the duration of T symbols is determined based on the minimum UE processing time applicable for PDSCH processing according to the appropriate UE processing time capability. When different UE capabilities for PDSCH processing time are configured on multiple cells, the UE capability with the longer processing time may be applied.

[0036] CBG or TB based transmission for multi-cell scheduling In one embodiment, when a UE is configured with multi-cell scheduling and the UE is configured with a type 2 codebook, the UE does not expect to be configured with CBG-based transmission for all cells associated with the multi-cell scheduling. Alternatively, when a UE is configured with multi-cell scheduling and the UE is configured with a type 2 codebook, the UE does not expect to be configured with CBG-based transmission for any cell in the same PDSCH group or PUCCH group. Alternatively, when a UE is configured with multi-cell scheduling and the UE is configured with a type 2 codebook, the UE does not expect to be configured with CBG-based transmission for all any cell in the same PDSCH group. Alternatively, when a UE is configured with multi-cell scheduling, the UE does not expect to be configured with CBG-based transmission for any cell associated with the multi-cell scheduling. Alternatively, when a UE is configured with multi-cell scheduling, the UE does not expect to be configured with CBG-based transmission for any cell in the same PDSCH group or PUCCH group. Thus, for candidate PDSCH locations for cells that can be scheduled by multi-cell scheduling, HARQ-ACK is reported per TB, or per bundled TBs of the PDSCH, e.g. if spatial bundling is configured.

[0037] In another embodiment, the PDSCH on the cell scheduled by the DCI for multi-cell scheduling may use CBG-based transmission. For the candidate PDSCH positions, the number of HARQ-ACK bits Nc is determined by the maximum number of configured CBGs. HARQ-ACK is reported per CBG.

[0038] In another embodiment, the PDSCH on a cell scheduled by DCI for multi-cell scheduling may use only TB-based transmission, regardless of whether CBG-based transmission is configured for the cell or BWP. If CBG-based transmission is configured for BWP for single-cell scheduling, then for a candidate PDSCH position, the number of HARQ-ACK bits Nc is determined by the maximum configured number of CBGs. If the PDSCH is scheduled by TB-based transmission, then the HARQ-ACK is reported per TB, and the HARQ-ACK is repeated or the NACK is padded up to Nc bits. Alternatively, for a candidate PDSCH position that is an interplay of both single-cell and multi-cell scheduling, the number of HARQ-ACK bits Nc is determined by the maximum configured number of CBGs, and for a candidate PDSCH position with only multi-cell scheduling, the number of HARQ-ACK bits Nc is determined by the configured number of TBs for the PDSCH.

[0039] In another embodiment, whether CBG-based transmission is applied for a PDSCH on a cell scheduled by a DCI for multi-cell scheduling is configured by higher layer signaling. The configuration may be common to all cells that can be scheduled by a DCI for multi-cell scheduling. Alternatively, the configuration may be common to all cells in the same PDSCH group. Alternatively, the configuration may be configured separately for each cell that can be scheduled by a DCI for multi-cell scheduling, thus allowing one cell to have a CBG-based transmission and another cell to have a TB-based transmission. Also, the maximum number of CBGs for TBs scheduled by a DCI for multi-cell scheduling may be configured by higher layer signaling.

[0040] In one embodiment, a common configuration of the number of TBs (codewords) applies to both multi-cell and single-cell scheduling for DL ​​BWP of a cell. Alternatively, the number of TBs scheduled by DCI for multi-cell scheduling for DL ​​BWP of a cell may be configured separately from the number of TBs scheduled by DCI for single-cell scheduling for a cell. Alternatively, the number of TBs scheduled by DCI for multi-cell scheduling for a cell may be configured per UE or per serving cell.

[0041] Multi-PDSCH Scheduling for Multi-Cell Scheduling Multi-PDSCH scheduling means that one DCI schedules multiple PDSCHs in the same serving cell.

[0042] In one embodiment, if the UE is configured with multi-cell scheduling and the UE is configured with a type 2 codebook, the UE does not expect to be configured with multi-PDSCH scheduling for any cell associated with the multi-cell scheduling. Alternatively, if the UE is configured with multi-cell scheduling and the UE is configured with a type 2 codebook, the UE does not expect to be configured with multi-PDSCH scheduling for any cell in the same PDSCH group or PUCCH group. Alternatively, if the UE is configured with multi-cell scheduling, the UE does not expect to be configured with multi-PDSCH scheduling for any cell associated with the multi-cell scheduling. Alternatively, if the UE is configured with multi-cell scheduling, the UE does not expect to be configured with multi-PDSCH scheduling for any cell in the same PDSCH group or PUCCH group.

[0043] However, the above embodiment can also be applied to the case of multi-PUSCH scheduling and multi-cell scheduling. In other words, when the UE is configured with multi-cell scheduling, the UE does not expect to be configured with multi-PUSCH scheduling for any cell associated with the multi-cell scheduling or all cells in the PUCCH group or PUSCH group.

[0044] In another embodiment, when a UE is configured with multi-cell scheduling, the UE may be configured with multi-PDSCH / PUSCH scheduling, but the UE does not anticipate being scheduled for multi-cell scheduling and multi-PDSCH scheduling by the same DCI, e.g., the UE may be configured with DCI 1-1 for multi-PDSCH scheduling and DCI 1-3 for multi-cell scheduling.

[0045] Sub-codebook determination In one embodiment, for Type 2 HARQ-ACK CB, the HARQ-ACK for PDSCH scheduled by single-cell scheduling and the HARQ-ACK for PDSCH scheduled by multi-cell scheduling are in the same sub-codebook.

[0046] If at least one serving cell in a PUCCH group is configured with a CBG, there may be two or more HARQ-ACK sub-codebooks: one sub-codebook for HARQ-ACK for PDSCH scheduled by single-cell scheduling for TB transmission and HARQ-ACK for PDSCH scheduled by multi-cell scheduling for TB transmission, and another sub-codebook for HARQ-ACK for PDSCH scheduled by single-cell scheduling for CBG transmission and HARQ-ACK for PDSCH scheduled by multi-cell scheduling for CBG transmission.

[0047] If at least one serving cell in a PUCCH group is configured with multi-PDSCH scheduling, there may be two or more HARQ-ACK sub-codebooks: one sub-codebook for HARQ-ACK for PDSCH scheduled by multi-PDSCH scheduling, and another sub-codebook for HARQ-ACK for PDSCH not scheduled by multi-PDSCH scheduling, e.g., HARQ-ACK for PDSCH scheduled by single-cell scheduling without multi-PDSCH scheduling, and HARQ-ACK for PDSCH scheduled by multi-cell scheduling.

[0048] In one option, the DAI counts the number of PDCCHs in the same sub-codebook. For each PDCCH in the same sub-codebook, the number of HARQ-ACK bits is determined by the maximum number of HARQ-ACK bits for single-cell scheduling and multi-cell scheduling in the same sub-codebook: When TB-based HARQ-ACK feedback is used for multiple PDSCHs scheduled by DCI for multi-cell scheduling, N is the unit of the number of HARQ-ACK bits. TB max is the N among all cells. TB,2 tot,max and N TB,1 max where the total maximum configuration number of TBs for multiple PDSCHs scheduled by DCI for multi-cell scheduling is equal to N TB,2 tot,max and the maximum number of TBs of PDSCH scheduled by DCI for single cell scheduling is N TB,1 max Therefore, for a PDSCH scheduled by a DCI for single-cell scheduling or multiple PDSCHs scheduled by a DCI for multi-cell scheduling, the number of HARQ-ACK bits reported is N TB max bits. The total maximum configured number of TBs for multiple PDSCHs scheduled by a DCI for multi-cell scheduling is determined by the number of PDSCHs scheduled by the multi-cell scheduling DCI (e.g., the maximum number of PDSCHs in each row in the cell index table for multi-cell scheduling). Alternatively, the total maximum configured number of TBs for multiple PDSCHs scheduled by a DCI for multi-cell scheduling is determined by the total number of PDSCHs / serving cells configured for the multi-cell scheduling DCI (e.g., the union of all rows in the cell index table for multi-cell scheduling). The definition of the total maximum configured number of TBs for multiple PDSCHs scheduled by a DCI for multi-cell scheduling may be applicable to all embodiments in this document. If spatial bundling is configured (e.g., harq-ACK-SpatialBundling PUCCH is configured), the number of configured TBs per PDSCH is assumed to be 1.

[0049] If CBG-based HARQ-ACK feedback is used for at least one PDSCH among multiple PDSCHs scheduled by DCI for multi-cell scheduling, N is the unit of the number of HARQ-ACK bits for the sub-codebook for CBG. CBG max is the N among all cells CBG,2 tot,max and N CBG,1 max where the total maximum number of configurations of CBGs for multiple PDSCHs scheduled by DCI for multi-cell scheduling is equal to N CBG,2 tot,max and the maximum number of CBGs of PDSCH scheduled by DCI for single cell scheduling is N CBG,1 max Therefore, for a PDSCH scheduled by a DCI for single-cell scheduling or multiple PDSCHs scheduled by a DCI for multi-cell scheduling, the number of HARQ-ACK bits reported is N CBG max In multi-cell scheduling, if one PDSCH uses TB-based transmission, one CBG per TB can be effectively assumed for TB-based PDSCH transmission.

[0050] If at least one serving cell in the PUCCH group is configured with multi-PDSCH scheduling, the number of HARQ-ACK bits for each PDCCH in the sub-codebook for HARQ-ACK for PDSCHs not scheduled by multi-PDSCH scheduling is determined as provided above, and the number of HARQ-ACK bits for each PDCCH in the sub-codebook for HARQ-ACK for PDSCHs scheduled by multi-PDSCH scheduling is determined as follows: Unit N of HARQ-ACK bit number for sub-codebook for multi-PDSCH scheduling TBG max is equal to the maximum number of configured TBs of multiple PDSCHs or multiple PDSCH bundling groups scheduled by DCI for multi-PDSCH scheduling in all cells, e.g., N TBG max is the number of HARQ-BundlingGroups that the UE is configured with, and N when the UE is configured with multi-PDSCH but numberOfHARQ-BundlingGroups is not given. cells DL,TBG N across all serving cells TB,c DL N PDSCH,c max Given and, N cells DL,TBG N across all serving cells TB,c DL N PHARQ-ACK,c TBG,max is the maximum value between TB,c DL is the value of maxNrofCodeWordsScheduledByDCI for the serving cell c if harq-ACK-SpatialBundlingPUCCH is not given, otherwise N TB,c DL =1.

[0051] For example, as shown in Figure 3, two cells with non-consecutive cell indexes #1 and #3 are scheduled by DCI for multi-cell scheduling. A single C-DAI, e.g., C-DAI=1, is indicated for two PDSCHs on the two cells. Meanwhile, another PDSCH on cell #2 is assigned a C-DAI equal to 2. To generate a HARQ-ACK codebook, HARQ-ACKs for multiple PDSCHs scheduled by DCI for multi-cell scheduling are concatenated and mapped to positions in the HARQ-ACK codebook according to the reference cell index, e.g., firstly map HARQ-ACKs for PDSCHs on cell #1 (reference cell) and cell #3, and then map HARQ-ACKs for PDSCHs on cell #2. Assuming the maximum number of HARQ-ACK bits per DAI is 2 bits, to ensure 2 bits per C-DAI, the HARQ-ACK for PDSCH on cell #1 is 2 bits, 1 bit is a valid HARQ-ACK for PDSCH and 1 bit is a NACK as a padding bit.

[0052] In one example, if the number of PDSCHs scheduled by a DCI is less than the maximum number of PDSCHs scheduled by a DCI, first, HARQ-ACKs for the scheduled PDSCHs are mapped consecutively, and NACKs are appended up to the maximum number of HARQ-ACK bits. For example, one row of the cell index table for multi-cell scheduling includes cells 2, 3, and 4, another row of the cell index table includes cells 1 and 3, and a single TB is configured without a CBG. The total maximum configuration number of TBs for multiple PDSCHs scheduled by a DCI for multi-cell scheduling is determined by the number of PDSCHs scheduled at one time by the multi-cell scheduling DCI, and N TB maxAssume that N = 3. If DCI schedules cell 1 and cell 3, HARQ-ACK for cell 1 and cell 3 are placed in the first and second bit positions, and one bit NACK is added in the third bit position. In another example, if the number of PDSCHs scheduled by DCI is less than the maximum number of PDSCHs scheduled by DCI, HARQ-ACK for scheduled PDSCH is mapped to the bit positions according to the serving cell index, and NACK is added in the remaining bit positions. For example, one row of cell index table for multi-cell scheduling includes cells 1, 2, 3, 4, another row of cell index table includes cells 1 and 3, and a single TB is configured without CBG. The total maximum configuration number of TBs for multiple PDSCHs scheduled by DCI for multi-cell scheduling is determined by the number of PDSCHs scheduled at one time by multi-cell scheduling DCI, N TB max Assume that =4, if DCI schedules cell 1 and cell 3, HARQ-ACK for cell 1 and cell 3 is placed in the 1st and 3rd bit positions, and NACK is added in the 2nd and 4th bit positions.

[0053] In another option, the DAI counts PDSCHs or the DAI counts serving cells in the same sub-codebook. For each PDCCH in the same sub-codebook, the number of HARQ-ACK bits varies with the number of PDSCHs actually scheduled or transmitted or valid PDSCHs. In this scheme, the DCI for multi-cell scheduling includes a single C-DAI value x, but the Np PDSCHs scheduled by the DCI effectively use C-DAI values ​​x...x+Np-1. The next DCI transmitted by the gNB may indicate a C-DAI value x+Np.

[0054] When TB-based HARQ-ACK feedback is used for multiple PDSCHs scheduled by DCI for multi-cell scheduling, N is the unit of the number of HARQ-ACK bits. TB max is the N among all cells. TB,2 max and N TB,1 max where the maximum number of TBs configured for PDSCH scheduled by DCI for multi-cell scheduling is N TB,2 max and the maximum number of TBs of PDSCH scheduled by DCI for single cell scheduling is N TB,1 max Therefore, for a PDSCH scheduled by DCI for single-cell scheduling, the number of HARQ-ACK bits reported is N TB max Meanwhile, for multiple PDSCHs scheduled by DCI for multi-cell scheduling, the total number of HARQ-ACK bits reported is N p N TB max It is a bit.

[0055] If CBG-based HARQ-ACK feedback is used for at least one of multiple PDSCHs scheduled by DCI for multi-cell scheduling, N is the unit of the number of HARQ-ACK bits. CBG max is the N among all cells CBG,2 max and N CBG,1 max where the maximum number of CBGs configured for PDSCH scheduled by DCI for multi-cell scheduling is N CBG,2 max and the maximum number of CBGs of PDSCH scheduled by DCI for single cell scheduling is N CBG,1 maxTherefore, for a PDSCH scheduled by DCI for single-cell scheduling, the number of HARQ-ACK bits reported is N CBG max Meanwhile, for multiple PDSCHs scheduled by DCI for multi-cell scheduling, the total number of HARQ-ACK bits reported is N p N CBG max In multi-cell scheduling, if one PDSCH uses TB-based transmission, one CBG per TB can be effectively assumed for TB-based PDSCH transmission.

[0056] For example, as shown in FIG. 4, two cells with non-consecutive cell indexes #1 and 3 are scheduled by DCI for multi-cell scheduling. A single C-DAI, e.g., C-DAI=1, is indicated in the DCI. C-DAI is applied to the PDSCH on cell #1, and effectively C-DAI=2 is applied to the PDSCH on cell #3. Thus, a C-DAI equal to 3 is assigned to another PDSCH on cell #2. To generate a HARQ-ACK codebook, the HARQ-ACKs for the two PDSCHs scheduled by DCI for multi-cell scheduling are concatenated and mapped to positions in the HARQ-ACK codebook according to the reference cell index, e.g., first, map the HARQ-ACKs for the PDSCHs on cell #0 (reference cell) and cell #3, and then map the HARQ-ACKs for the PDSCHs on cell #2.

[0057] In one embodiment, in type-2 HARQ-ACK CB, the HARQ-ACK for PDSCH scheduled by single-cell scheduling and the HARQ-ACK for PDSCH scheduled by multi-cell scheduling are in different sub-codebooks, i.e., one sub-codebook is for HARQ-ACK for PDSCH scheduled by single-cell scheduling, and another sub-codebook is for HARQ-ACK for PDSCH scheduled by multi-cell scheduling. Note that in the case of multi-cell scheduling, if the number of PDSCHs actually scheduled or transmitted is 1, the HARQ-ACK sub-codebook is based on the HARQ-ACK sub-codebook for PDSCH scheduled by single-cell scheduling.

[0058] In one option, if CBG based transmission is not configured, one sub-codebook is for HARQ-ACK for PDSCH scheduled by single-cell scheduling and another sub-codebook is for HARQ-ACK for PDSCH scheduled by multi-cell scheduling.

[0059] FIG. 5A provides an example. In one DCI, there is one C-DAI, which is applied to all PDSCHs scheduled by this DCI. Two cells with non-consecutive cell indexes #1 and #3 are scheduled by the DCI for multi-cell scheduling. A single C-DAI, e.g., C-DAI=1, is indicated in the DCI. The C-DAI is applied to the PDSCH on cell #1 and the PDSCH on cell #3. Meanwhile, a C-DAI equal to 1 is assigned to another PDSCH on cell #2. To generate the HARQ-ACK codebook, the first sub-codebook is for single-cell scheduling, e.g., for the PDSCH on cell #2, and the second sub-codebook is for multi-cell scheduling, and the HARQ-ACKs for the two PDSCHs scheduled by the DCI for multi-cell scheduling are concatenated and mapped to positions in the HARQ-ACK. Note that if the maximum number of HARQ-ACK bits per DAI for the second sub-codebook is greater than two, the UE should generate NACK up to the maximum number of HARQ-ACK bits.

[0060] Figure 5B provides an example. In one DCI, there are two C-DAIs for two PDSCH groups, and each C-DAI applies to all PDSCHs in one PDSCH group scheduled by this DCI. Three cells with non-consecutive cell indexes #1, #3, and #4 are scheduled by a DCI for multi-cell scheduling, where #1 and #3 are in PDSCH group 1, and #4 is in PDSCH group 2. Thus, DAI,1 applies to both #1 and #3, and DCI,2 applies to #2. One cell with cell index #2 is scheduled by a DCI for single-cell scheduling, and the DAI in the DCI applies to the PDSCH on #2.

[0061] The HARQ-ACK for PDSCH on cell #2 and cell #4 belongs to the first sub-codebook due to single-cell scheduling, and the HARQ-ACK for PDSCH on cell #1 and cell #3 belongs to the second sub-codebook due to multi-cell scheduling. Therefore, C-DAI,1 and C-DAI,2 are counted separately for the second and first sub-codebooks, but all PDSCHs are associated with the same PUCCH. C-DAI for #2 and C-DAI,2 for #4 are counted consecutively in the first sub-codebook with DAI=1 and DAI=2, respectively. Therefore, the HARQ-ACK codebook includes the first sub-codebook with HARQ-ACK for PDSCH on cell #1 and cell #3, and the second sub-codebook with HARQ-ACK for PDSCH on cell #2 and cell #4, respectively.

[0062] In another option, if CBG-based transmission is not configured for DCI for multi-cell scheduling, whether HARQ-ACK for PDSCH scheduled by multi-cell scheduling is in the same sub-codebook as HARQ-ACK for PDSCH scheduled by single-cell scheduling is determined by the number of TBs scheduled by DCI. For example, if only two TBs are carried by two PDSCHs, HARQ-ACK for PDSCH scheduled by multi-cell scheduling and HARQ-ACK for PDSCH scheduled by single-cell scheduling are in the same sub-codebook. Otherwise, different sub-codebooks are used. In another option, if CBG-based transmission is not configured for DCI for multi-cell scheduling, whether HARQ-ACK for PDSCH scheduled by multi-cell scheduling is in the same sub-codebook as HARQ-ACK for PDSCH scheduled by single-cell scheduling is configured by higher layer signaling.

[0063] In another option, if at least one serving cell in the PUCCH group is configured with a CBG, there may be more than one HARQ-ACK sub-codebook: one sub-codebook for HARQ-ACK for PDSCH scheduled by single-cell scheduling for TB transmission, and another sub-codebook for HARQ-ACK for PDSCH scheduled by multi-cell scheduling for TB transmission and HARQ-ACK for PDSCH with CBG transmission. Alternatively, one sub-codebook for HARQ-ACK for PDSCH scheduled by single-cell scheduling for TB transmission, another sub-codebook for HARQ-ACK for PDSCH scheduled by multi-cell scheduling for TB transmission, another sub-codebook for HARQ-ACK for PDSCH scheduled by single-cell scheduling for CBG transmission, and another sub-codebook for HARQ-ACK for PDSCH scheduled by multi-cell scheduling for CBG transmission. Alternatively, one sub-codebook is for HARQ-ACK for PDSCH scheduled by single-cell scheduling for TB transmission, another sub-codebook is for HARQ-ACK for PDSCH scheduled by multi-cell scheduling for TB transmission, and another sub-codebook is for HARQ-ACK for PDSCH with CBG transmission.

[0064] In another option, if multi-PDSCH scheduling is not configured for any cell in the PDSCH group or the PUCCH group, one sub-codebook is for HARQ-ACK for PDSCH scheduled by single-cell scheduling and another sub-codebook is for HARQ-ACK for PDSCH scheduled by multi-cell scheduling. If at least one cell in the PDSCH group or the PUCCH group is configured with multi-PDSCH scheduling, one sub-codebook is for HARQ-ACK for PDSCH scheduled by single-cell scheduling without multi-PDSCH scheduling and another sub-codebook is for HARQ-ACK for PDSCH scheduled by multi-cell scheduling and PDSCH scheduled by multi-PDSCH scheduling. Alternatively, one sub-codebook is for HARQ-ACK for a PDSCH scheduled by single-cell scheduling without multi-PDSCH scheduling, another sub-codebook is for HARQ-ACK for a PDSCH scheduled by multi-cell scheduling, and another sub-codebook is for HARQ-ACK for a PDSCH scheduled by multi-PDSCH scheduling.

[0065] The DAI counts the number of PDCCHs in the same sub-codebook. For each PDCCH in the same sub-codebook, the number of HARQ-ACK bits is determined by the maximum number of HARQ-ACK bits for PDCCHs in the same sub-codebook.

[0066] For example, if none of the serving cells in a PUCCH group is configured with a CBG, the first sub-codebook is for HARQ-ACK for PDSCHs scheduled by single-cell scheduling, and the second sub-codebook is for HARQ-ACK for PDSCHs scheduled by multi-cell scheduling. In the second sub-codebook, the number of HARQ-ACK bits per PDCCH is N TB max and N TB max is equal to the total maximum number of configured TBs of multiple PDSCHs scheduled by DCI for multi-cell scheduling. For example, N TB max =N cell max *N TB,2 max where N cell max is the maximum number of PDSCHs scheduled by DCI for multi-cell scheduling (e.g., the maximum number of PDSCHs for each row in the cell index table for multi-cell scheduling), or the total number of serving cells configured for multi-cell scheduling (e.g., the union of all rows in the cell index table for multi-cell scheduling), and N TB,2 max is the maximum number of TBs configured for PDSCH scheduled by DCI for multi-cell scheduling. If at least one serving cell in a PUCCH group is configured with two codewords for multi-cell scheduling, e.g., maxNrofCodeWordsScheduledByDCI=2, and spatial bundling is not configured, N TB,2 max = 2, otherwise N TB,2 max= 1. Assume that the UE is configured with four DL CCs and the gNB configures three sets of PDSCHs scheduled by a single DCI. The first set includes DL serving cell 1 and DL serving cell 2, the second set includes DL serving cell 3 and DL serving cell 4, and the third set includes DL serving cell 2, serving cell 3, and serving cell 4. DL serving cell 1 is configured with two codewords, and DL CCs 2, 3, and 4 are each configured with one codeword. Then, N cell max = 3, for example, N cell max is the maximum number of PDSCHs scheduled by DCI for multi-cell scheduling, and N TB,2 max = 2. Or, N cell max = 4, for example, N cell max is the total number of serving cells configured for multi-cell scheduling, and N TB,2 max = 2, or

number

number

number

number

number

number

[0067] In the first sub-codebook, the number of HARQ-ACK bits per PDCCH is N TB,1 max N TB,1 max is the maximum number of TBs of PDSCH scheduled by DCI for single-cell scheduling among all cells. If two codewords are configured for at least one serving cell in a PUCCH group, e.g., maxNrofCodeWordsScheduledByDCI=2, and spatial bundling is not configured, then N TB,1 max = 2, otherwise N TB,1 max =1.

[0068] In another example, when at least one serving cell in a PUCCH group is configured with a CBG, the first sub-codebook is for HARQ-ACK for PDSCH scheduled by single-cell scheduling, and the second sub-codebook is for HARQ-ACK for PDSCH scheduled by multi-cell scheduling and HARQ-ACK for PDSCH with CBG transmission. And in the second sub-codebook, the number of HARQ-ACK bits per PDCCH is N CBG max N CBG max is the N among all cells. CBG,2 tot,max and N CBG,1 max where N CBG,1max is the maximum number of CBGs for PDSCH scheduled by DCI for single cell scheduling, and N CBG,2 tot,max is the total maximum number of CBGs configured for multiple PDSCHs scheduled by DCI for multi-cell scheduling when CBG is supported for multi-cell scheduling (when some cells of the multi-cell are configured with TBs and some cells of the multi-cell are configured with CBGs, the number of TBs for cells configured with TBs is N CBG,2 tot,max (treated as the number of CBGs for CBG,2 tot,max is the total maximum number N of configured TBs for multiple PDSCHs scheduled by DCI for multi-cell scheduling when CBG is not supported for multi-cell scheduling. TB max It is.

[0069] In another example, when at least one serving cell in a PUCCH group is configured with multi-PDSCH scheduling, the first sub-codebook is for HARQ-ACK for PDSCH scheduled by single-cell scheduling without multi-PDSCH scheduling, and the second sub-codebook is for HARQ-ACK for PDSCH scheduled by multi-cell scheduling and HARQ-ACK for PDSCH with multi-PDSCH scheduling. And, in the second sub-codebook, the number of HARQ-ACK bits per PDCCH is N TBG&TB max and N TBG&TB max is the N among all cells. TB max and N TBG max where N TB maxis equal to the total maximum number of configured TBs of multiple PDSCHs scheduled by DCI for multi-cell scheduling among all cells given above, and N TBG max is equal to the maximum number of configured TBs of multiple PDSCHs or multiple PDSCH bundling groups scheduled by DCI for multi-PDSCH scheduling among all cells. This may apply when a single TB or two TBs are configured and scheduled for a PDSCH with multi-cell scheduling or multi-PDSCH scheduling.

[0070] In another example, when at least one serving cell in a PUCCH group is configured with multi-PDSCH scheduling, the first sub-codebook is for HARQ-ACK for PDSCH scheduled by single-cell scheduling without multi-PDSCH scheduling, the second sub-codebook is for HARQ-ACK for PDSCH scheduled by multi-cell scheduling, and the third sub-codebook is for HARQ-ACK for PDSCH with multi-PDSCH scheduling. And in the second sub-codebook, the number of HARQ-ACK bits per PDCCH is N given above. TB max and in the third sub-codebook, the number of HARQ-ACK bits per PDCCH is N given above. TBG max It is.

[0071] If the expected number of HARQ-ACK bits per PDCCH determined according to any of the above methods is greater than the number of HARQ-ACK bits with valid HARQ-ACK values ​​per PDCCH, the UE transmits valid HARQ-ACK bits and padding bits. The bit order of the valid HARQ-ACK bits and padding bits is determined according to at least one of the following methods: - First, map the valid HARQ-ACK bits consecutively (e.g. from smaller serving cell index to larger serving cell index), then add padding bits up to the expected number of HARQ-ACK bits per PDCCH; - First map the valid HARQ-ACK bits to the bit positions associated with the corresponding serving cell index, and then add padding bits to the unmapped bit positions up to the expected number of HARQ-ACK bits per PDCCH.

[0072] A valid HARQ-ACK is associated with a valid PDSCH, or a valid HARQ-ACK is associated with a scheduled PDSCH according to the received DCI.

[0073] System and Implementation 6-8 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments.

[0074] 6 illustrates a network 600 in accordance with various embodiments. Network 600 may operate in a manner consistent with 3GPP® technical specifications for LTE or 5G / NR systems. However, example embodiments are not limited in this respect, and the described embodiments may be applied to other networks that would benefit from the principles described herein, such as future 3GPP® systems or the like.

[0075] The network 600 may include a UE 602, which may include any mobile or non-mobile computing device designed to communicate with a RAN 604 via an over-the-air connection. The UE 602 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, a heads-up display device, an in-vehicle diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, etc.

[0076] In some embodiments, the network 600 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0077] In some embodiments, the UE 602 may further communicate with the AP 606 via an over-the-air connection. The AP 606 may manage a WLAN connection that may serve to offload some / all network traffic from the RAN 604. The connection between the UE 602 and the AP 606 may conform to any IEEE 802.11 protocol, and the AP 606 may be a Wireless Fidelity (Wi-Fi) router. In some embodiments, the UE 602, RAN 604, and AP 606 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve the UE 602 being configured by the RAN 604 to utilize both cellular radio resources and WLAN resources.

[0078] The RAN 604 may include one or more access nodes, such as the AN 608. The AN 608 may terminate air interface protocols for the UE 602 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. Thus, the AN 608 may enable data / voice connectivity between the CN 620 and the UE 602. In some embodiments, the AN 608 may be implemented in a separate device or as one or more software entities running on a server computer as part of a virtual network, such as what may be referred to as a CRAN or virtual baseband unit pool. The AN 608 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 608 may be a macrocell base station or a low power base station to provide a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0079] In embodiments where the RAN 604 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 604 is an LTE RAN) or an Xn interface (if the RAN 604 is a 5G RAN). The X2 / Xn interface may be separated into a control / user plane interface in some embodiments and may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0080] Each of the ANs of the RAN 604 may manage one or more cells, cell groups, component carriers, etc., to provide the UE 602 with an air interface for network access. The UE 602 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 604. For example, the UE 602 and the RAN 604 may use carrier aggregation to enable the UE 602 to connect with multiple component carriers, each corresponding to a Pcell or Scell. In a dual connection scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0081] The RAN 604 may provide an air interface over licensed or unlicensed spectrum. To operate in the unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA techniques using PCell / SCell. Prior to accessing the unlicensed spectrum, the node may perform medium / carrier sensing operations based on, for example, a Listen-Before-Talk (LBT) protocol.

[0082] In a V2X scenario, the UE 602 or AN 608 may be or act as an RSU, which may refer to any transportation infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-based RSU", an eNB may be referred to as an "eNB-based RSU", a gNB may be referred to as a "gNB-based RSU", and so on. In one example, the RSU is a computing device coupled with radio frequency circuitry located at the roadside that provides connectivity support to passing vehicular UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communication required for high speed events such as collision avoidance and traffic warnings. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components can be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

[0083] In some embodiments, the RAN 604 may be an LTE RAN 610 having an eNB, such as eNB 612. The LTE RAN 610 may provide an LTE air interface with characteristics such as a 15 kHz SCS, a CP-OFDM waveform for DL ​​and an SC-FDMA waveform for UL, turbo codes for data and TBCC for control. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management, PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on sub-6 GHz bands.

[0084] In some embodiments, the RAN 604 may be an NG-RAN 614 having a gNB, e.g., gNB 616, or an ng-eNB, e.g., ng-eNB 618. The gNB 616 may connect to a 5G-capable UE using a 5G NR interface. The gNB 616 may connect to a 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 618 may also connect to a 5G core via an NG interface, but may connect to a UE via an LTE air interface. The gNB 616 and the ng-eNB 618 may connect to each other via an Xn interface.

[0085] In some embodiments, the NG interface may be divided into two parts: an NG User Plane (NG-U) interface (e.g., an N3 interface), which carries traffic data between the nodes of the NG-RAN 614 and the UPF 648, and an NG Control Plane (NG-C) interface (e.g., an N2 interface), which is a signaling interface between the nodes of the NG-RAN 614 and the AMF 644.

[0086] The NG-RAN 614 may provide a 5G-NR air interface with the following characteristics: variable SCS, CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL, polar, repetitive, simplex and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH, and tracking reference signal for time tracking. The 5G-NR air interface may operate on the FR1 band, which includes sub-6 GHz bands, or the FR2 band, which includes bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid that includes PSS / SSS / PBCH.

[0087] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs may be used for dynamic adaptation of SCS. For example, the UE 602 may be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to the UE 602, the SCS of the transmission is changed as well. Another use case example of BWPs relates to power savings. In particular, multiple BWPs with different amounts of frequency resources (e.g., PRBs) may be configured for the UE 602 to support data transmissions under different traffic load scenarios. This may enable power savings at the UE 602 and in some cases at the gNB 616, while a BWP with a smaller number of PRBs may be used for data transmissions with a smaller traffic load. A BWP with a larger number of PRBs may be used for scenarios with a higher traffic load.

[0088] The RAN 604 is communicatively coupled to the CN 620, which includes network elements for providing various functions to customers / subscribers (e.g., users of UEs 602) to support data and telecommunication services. The components of the CN 620 may be implemented in one physical node or in multiple separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 620 onto physical computation / storage resources in servers, switches, etc. A logical instantiation of the CN 620 may be referred to as a network slice, and a portion of the logical instantiation of the CN 620 may be referred to as a network sub-slice.

[0089] In some embodiments, the CN 620 may be an LTE CN 622, which may also be referred to as an EPC. The LTE CN 622 may include an MME 624, an SGW 626, an SGSN 628, an HSS 630, a PGW 632, and a PCRF 634 coupled together via interfaces (or "reference points") as shown. A brief introduction to the functionality of these elements of the LTE CN 622 may be as follows:

[0090] The MME 624 may implement mobility management functions to track the current location of the UE 602 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0091] The SGW 626 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 622. The SGW 626 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0092] The SGSN 628 may track the location of the UE 602 and perform security functions and access control. In addition, the SGSN 628 may perform EPC inter-node signaling for mobility between different RAT networks, PDN and S-GW selection specified by the MME 624, MME selection for handover, etc. An S3 reference point between the MME 624 and the SGSN 628 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active state.

[0093] The HSS 630 may include a database for network users containing subscription related information to support network entity handling of communication sessions. The HSS 630 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS 630 and the MME 624 may enable transfer of subscription and authentication data to authenticate / authorize user access to the LTE CN 620.

[0094] The PGW 632 may terminate an SGi interface towards a data network (DN) 636, which may include an application / content server 638. The PGW 632 may route data packets between the LTE CN 622 and the data network 636. The PGW 632 may be coupled to the SGW 626 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 632 may further include a node (e.g., PCEF) for policy enforcement and charging data collection. The SGi reference point between the PGW 632 and the data network 636 may also be an operator external public, private PDN, or intra-operator packet data network, for example, for the provision of IMS services. The PGW 632 may be coupled to the PCRF 634 via a Gx reference point.

[0095] The PCRF 634 is the policy and charging control element of the LTE CN 622. The PCRF 634 may be communicatively coupled to an app / content server 638 to determine appropriate QoS and charging parameters for a service flow. The PCRF 634 may provision the PCEF with the relevant rules (via the Gx reference point) with the appropriate TFT and QCI.

[0096] In some embodiments, the CN 620 may be a 5GC 640. The 5GC 640 may include an AUSF 642, an AMF 644, an SMF 646, a UPF 648, an NSSF 650, an NEF 652, an NRF 654, a PCF 656, a UDM 658, and an AF 660 coupled together via interfaces (or "reference points") as shown. A brief introduction to the functionality of these elements of the 5GC 640 may be as follows:

[0097] The AUSF 642 may store data and handle authentication related functions for authentication of the UE 602. The AUSF 642 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 640 via the reference points shown, the AUSF 642 may exhibit a Nausf service-based interface.

[0098] The AMF 644 may enable other functions of the 5GC 640 to communicate with the UE 602 and the RAN 604 and subscribe to notifications about mobility events for the UE 602. The AMF 644 may be responsible for registration management (e.g., to register the UE 602), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 644 may provide transport for SM messages between the UE 602 and the SMF 646 and may act as a transparent proxy for routing SM messages. The AMF 644 may also provide transport for SMS messages between the UE 602 and the SMSF. The AMF 644 may interact with the AUSF 642 and the UE 602 to perform various security anchor and context management functions. Additionally, the AMF 644 may be the termination point of the RAN CP interface, which may include or be an N2 reference point between the RAN 604 and the AMF 644, and the AMF 644 may be the termination point of the NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 644 may also support NAS signaling with the UE 602 over an N3 IWF interface.

[0099] The SMF 646 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 648 and the AN 608), UE IP address allocation and management (including optional authorization), selection and control of UP functions, configuration of traffic steering in the UPF 648 to route traffic to the appropriate destination, termination of the interface towards the policy control function, control of the policy enforcement, charging, and QoS portions, lawful interception (for SM events and the interface towards the L1 system), termination of the SM portion of NAS messages, downlink data notification, initiation of AN-specific SM information sent over N2 to the AN 608 via the AMF 644, and determination of the SSC mode of the session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between the UE 602 and the data network 636.

[0100] The UPF 648 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 636, and a branching point for supporting multi-homed PDU sessions. The UPF 648 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF-to-QoS flow mapping), perform transport level packet marking in the uplink and downlink, perform downlink packet buffering, and downlink data notification triggering. The UPF 648 may include an uplink classifier that supports routing traffic flows to the data network.

[0101] The NSSF 650 may select a set of network slice instances to serve the UE 602. The NSSF 650 may also determine the allowed NSSAIs and mapping to subscribed S-NSSAIs, if necessary. The NSSF 650 may also determine the AMF set to be used to serve the UE 602, or a list of candidate AMFs, based on a preferred configuration and possibly by querying the NRF 654. The selection of a set of network slice instances for the UE 602 may be triggered by the AMF 644 to which the UE 602 is registered, by interacting with the NSSF 650, which may lead to a change of the AMF. The NSSF 650 may interact with the AMF 644 via the N22 reference point and may also communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, the NSSF 650 may exhibit an Nnssf service-based interface.

[0102] The NEF 652 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal publication / republication, AFs (e.g., AF 660), edge computing systems, or fog computing systems. In such an embodiment, the NEF 652 may authenticate, authorize, or throttle the AF. The NEF 652 may also translate information exchanged with the AF 660 and with internal network functions. For example, the NEF 652 may translate between AF service identifiers and internal 5GC information. The NEF 652 may also receive information from other NFs based on the published capabilities of the other NFs. This information may be stored in the NEF 652 as structured data or in a data storage NF using a standardized interface. The stored information may then be republished by the NEF 652 to other NFs and AFs or used for other purposes, such as analytics. Additionally, the NEF 652 may present an Nnef service-based interface.

[0103] The NRF 654 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to the NF instances. The NRF 654 also maintains information of available NF instances and their supported services. As used herein, the terms "instantiate," "instance," and the like may refer to the creation of an instance, and an "instance" may refer to a concrete occurrence of an object, such as may occur during the execution of program code. Additionally, the NRF 654 may expose an Nnrf service-based interface.

[0104] The PCF 656 can provide policy rules to the control plane functions to enforce them and can also support a unified policy framework to manage network behavior. The PCF 656 can also implement a front end to access subscription information related to policy decisions within the UDRs of the UDM 658. In addition to communicating with functions via the reference points shown, the PCF 656 exhibits an Npcf service-based interface.

[0105] The UDM 658 may process subscription related information to support network entity processing of communication sessions and may store subscription data of the UE 602. For example, the subscription data may be communicated via the N8 reference point between the UDM 658 and the AMF 644. The UDM 658 may include two parts: an application front end and a UDR. The UDR may store subscription and policy data for the UDM 658 and the PCF 656, and / or structured data for publishing and application data for the NEF 652 (including PFD for application discovery, application requirement information for multiple UEs 602). Nudr service-based interfaces may be exposed by the UDR to allow the UDM 658, the PCF 656, and the NEF 652 to access a particular set of stored data and to read, update (e.g., add, modify), delete, and register for notifications of relevant data changes in the UDR. The UDM may include a UDM-FE, which is responsible for credential processing, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via the reference points shown, the UDM 658 may expose a Nudm service-based interface.

[0106] The AF660 provides application influence over traffic routing, provides access to the NEF, and can interact with the policy framework for policy control.

[0107] In some embodiments, the 5GC 640 may enable edge computing by selecting an operator / third-party service to be geographically close to the point where the UE 602 attaches to the network. This may reduce latency and load on the network. To provide edge computing implementation, the 5GC 640 may select a UPF 648 close to the UE 602 and perform traffic steering from the UPF 648 to the data network 636 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 660. Thus, the AF 660 may influence UPF (re)selection and traffic routing. Based on operator deployment, when the AF 660 is considered a trusted entity, the network operator may allow the AF 660 to directly interact with the associated NFs. In addition, the AF 660 may exhibit a Naf service-based interface.

[0108] Data network 636 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers, including, for example, application / content server 638 .

[0109] 7 illustrates a schematic of a wireless network 700 in accordance with various embodiments. The wireless network 700 may include a UE 702 in wireless communication with an AN 704. The UE 702 and the AN 704 may be similar to similarly named components described elsewhere herein and may be substantially interchangeable.

[0110] The UE 702 may be communicatively coupled to the AN 704 via a connection 706. The connection 706 is shown as an air interface for enabling the communicative coupling and may correspond to a cellular communication protocol, such as, for example, an LTE protocol or a 5G NR protocol operating at mm-wave or sub-6 GHz frequencies.

[0111] The UE 702 may include a host platform 708 coupled to a modem platform 710. The host platform 708 may include an application processing circuit 712, which may be coupled to the protocol processing circuit 78 of the modem platform 710. The application processing circuit 712 may execute various applications for the UE 702 that source / sink application data. The application processing circuit 712 may further implement one or more layer operations for sending / receiving application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0112] The protocol processing circuitry 714 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 706. The layer operations implemented by the protocol processing circuitry 714 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0113] The modem platform 710 may further include digital baseband circuitry 716 that may implement one or more layer operations "below" the layer operations performed by the protocol processing circuitry 714 in a network protocol stack. These operations may include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding which may include one or more of space-time, space-frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0114] The modem platform 710 may further include transmit circuitry 718, receive circuitry 720, RF circuitry 722, and an RF front end (RFFE) 724 that may include or connect to one or more antenna panels 726. Briefly, the transmit circuitry 718 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc., the receive circuitry 720 may include analog-to-digital converters, mixers, IF components, etc., the RF circuitry 722 may include low noise amplifiers, power amplifiers, power tracking components, etc., and the RFFE 724 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of components of the transmit circuitry 718, receive circuitry 720, RF circuitry 722, RFFE 724, and antenna panel 726 (collectively referred to as the "transmit / receive components") may be specific to the details of a particular implementation, such as, for example, whether communications are TDM or FDM, in mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be configured in multiple parallel transmit / receive chains and may be located on the same or different chips / modules, etc.

[0115] In some embodiments, the protocol processing circuit 714 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.

[0116] UE reception may be established by and through the antenna panel 726, the RFFE 724, the RF circuitry 722, the receive circuitry 720, the digital baseband circuitry 716, and the protocol processing circuitry 714. In some embodiments, the antenna panel 726 may receive transmissions from the AN 704 by receive beamforming signals received by multiple antennas / antenna elements of one or more of the antenna panels 726.

[0117] UE transmissions may be established by and through the protocol processing circuitry 714, the digital baseband circuitry 716, the transmit circuitry 718, the RF circuitry 722, the RFFE 724, and the antenna panel 726. In some embodiments, the transmit components of the UE 702 may apply spatial filters to data to be transmitted to form transmit beams that are radiated by the antenna elements of the antenna panel 726.

[0118] Similar to the UE 702, the AN 704 may include a host platform 728 coupled to a modem platform 730. The host platform 728 may include an application processing circuit 732 coupled to a protocol processing circuit 734 of the modem platform 730. The modem platform may further include a digital baseband circuit 736, a transmit circuit 738, a receive circuit 740, an RF circuit 742, an RFFE circuit 744, and an antenna panel 746. These components of the AN 704 may be similar to, and substantially interchangeable with, similarly named components of the UE 702. In addition to performing data transmission / reception as described above, the components of the AN 704 may perform various logical functions including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0119] 8 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) to perform any one or more of the methods described herein, according to some example embodiments. Specifically, FIG. 8 illustrates a schematic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory / storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840 or other interface circuitry. In embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 802 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 800.

[0120] Processor 810 may include, for example, processor 812 and processor 814. Processor 810 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), other processors (including those described herein), or any suitable combination thereof.

[0121] The memory / storage device 820 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 820 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0122] Communications resources 830 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 804 or one or more databases 806 or other network elements over network 808. For example, communications resources 830 may include a wired communications component (e.g., for coupling via USB, Ethernet, etc.), a cellular communications component, an NFC component, a Bluetooth® (or Bluetooth® Low Energy) component, a Wi-Fi® component, and other communications components.

[0123] The instructions 850 may comprise software, programs, applications, applets, apps, or other executable code for causing at least one of the processors 810 to perform any one or more of the methods described herein. The instructions 850 may reside, completely or partially, in at least one of the processors 810 (e.g., in a cache memory of the processor), in the memory / storage device 820, or any suitable combination thereof. Also, any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral device 804 or the database 806. Thus, the memory of the processor 810, the memory / storage device 820, the peripheral device 804, and the database 806 are examples of computer-readable and machine-readable media.

[0124] Step-by-step example In some embodiments, the electronic device(s), network(s), system(s), chip(s), or component(s) of FIG. 6-FIG. 8 or some other figures herein, or portions or implementations thereof, may be configured to perform one or more processes, techniques, or methods described herein, or portions thereof. One such process 900 is shown in FIG. 9. In some embodiments, the process 900 may be performed by a UE or a portion thereof. At 902, the process 900 may include detecting downlink control information (DCI) that schedules multiple physical downlink shared channels (PDSCHs) in multiple cells. At 904, the process 900 may further include decoding a counter downlink allocation index (C-DAI) of the DCI based on the reference cell. At 906, the process 900 may further include encoding a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback for the PDSCH based on the C-DAI.

[0125] Configure one or more NTCRMs.

[0126] 10 illustrates another example process 1000 in accordance with various embodiments. In some embodiments, the process 1000 may be performed by a gNB or a portion thereof. At 1002, the process 1000 may include encoding downlink control information (DCI) that schedules a plurality of physical downlink shared channels (PDSCHs) in a plurality of cells for transmission to a user equipment (UE), the DCI including a reference cell-based counter downlink allocation index (C-DAI). At 1004, the process 1000 may further include receiving a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback for the PDSCH based on the C-DAI.

[0127] In one or more embodiments, at least one of the components described in one or more of the above figures may be configured to perform one or more of the operations, techniques, processes, and / or methods as described in the Examples section below. For example, the baseband circuitry described above in connection with one or more of the above figures may be configured to operate according to one or more of the examples described below. In another example, circuitry associated with a UE, base station, network element, etc. described above in connection with one or more of the above figures may be configured to operate according to one or more of the examples described below in the Examples section.

[0128] example Example A1 may include one or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors of a user equipment (UE), configure the UE to: detect downlink control information (DCI) scheduling multiple physical downlink shared channels (PDSCHs) in multiple cells; decode a counter downlink allocation index (C-DAI) of the DCI based on a reference cell; and encode a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback for the PDSCHs based on the C-DAI.

[0129] Example A2 may include one or more NTCRMs of Example A1, wherein the HARQ-ACK feedback is encoded based on a second sub-codebook different from the first sub-codebook used for single-cell PDSCH scheduling.

[0130] Example A3 may include one or more NTCRMs of example A2, wherein the C-DAI counts the number of physical downlink control channels (PDCCHs) that use the second sub-codebook.

[0131] Example A4 may include one or more NTCRMs of any one of Examples A2 to A3, where the instructions when executed further configure the UE to determine a number of HARQ-ACK bits for the C-DAI in the HARQ-ACK feedback based on a maximum number of HARQ-ACK bits for a PDSCH that can be scheduled by a physical downlink control channel (PDCCH) in the second sub-codebook.

[0132] Example A5 may include one or more NTCRMs of any one of Examples A2 to A4, wherein HARQ-ACK information bits for the PDSCHs in the HARQ-ACK feedback in the second sub-codebook are ordered based on serving cell indexes of each of the cells.

[0133] Example A6 may include one or more NTCRMs of Example A5, where the HARQ-ACK information bits are mapped to bit positions first, and the instructions, when executed, further configure the UE to add one or more padding bits after the HARQ-ACK information bits if a number of expected bits per physical downlink control channel (PDCCH) exceeds the number of the HARQ-ACK information bits for the multiple PDSCHs.

[0134] Example A7 can include one or more NTCRMs of example A1, wherein the reference cell is selected from the plurality of cells based on a cell index.

[0135] Example A8 can include one or more NTCRMs of example A7, where the reference cell is selected as the cell having the lowest cell index among the plurality of cells.

[0136] Example A9 may include one or more NTCRMs of Example A1, wherein the reference cell is a serving cell for a reference PDSCH among the plurality of PDSCHs, or is selected according to a start or end position of the reference cell among the plurality of cells, or is configured for the UE by a next generation Node B (gNB).

[0137] Example A10 may include one or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors of a next generation Node B (gNB), configure the gNB to: encode downlink control information (DCI) that schedules a plurality of physical downlink shared channels (PDSCHs) in a plurality of cells for transmission to a user equipment (UE), the DCI including a counter downlink allocation index (C-DAI) based on a reference cell; and receive hybrid automatic repeat request delivery acknowledgement (HARQ-ACK) feedback for the PDSCHs based on the C-DAI.

[0138] Example A11 may include one or more NTCRMs of example A10, wherein the HARQ-ACK feedback is encoded based on a second sub-codebook different from a first sub-codebook used for single-cell PDSCH scheduling.

[0139] Example A12 may include one or more NTCRMs of example A11, wherein the C-DAI counts the number of physical downlink control channels (PDCCHs) that use the second sub-codebook.

[0140] Example A13 may include one or more NTCRMs of any one of Examples A11 to A12, wherein the number of HARQ-ACK bits for the C-DAI in the HARQ-ACK feedback is based on a maximum number of HARQ-ACK bits for a PDSCH that can be scheduled by a physical downlink control channel (PDCCH) in the second sub-codebook.

[0141] Example A14 may include one or more NTCRMs of any one of Examples A11 to A13, wherein HARQ-ACK information bits for the PDSCHs in the HARQ-ACK feedback in the second sub-codebook are ordered based on serving cell indexes of each of the cells.

[0142] Example A15 may include one or more NTCRMs of Example A14, wherein the HARQ-ACK information bits are mapped to bit positions first, and the HARQ-ACK feedback further includes one or more padding bits after the HARQ-ACK information bits if a number of expected bits per physical downlink control channel (PDCCH) exceeds the number of the HARQ-ACK information bits for the multiple PDSCHs.

[0143] Example A16 may include one or more NTCRMs of example A10, wherein the reference cell is selected from the plurality of cells based on a cell index.

[0144] Example A17 may include one or more NTCRMs of example A16, where the reference cell is selected as the cell having the lowest cell index among the plurality of cells.

[0145] Example A18 may include one or more NTCRMs of Example A10, wherein the reference cell is a serving cell for a reference PDSCH among the plurality of PDSCHs, or is selected according to a start or end position of the reference cell among the plurality of cells, or is configured for the UE by the gNB.

[0146] Example A19 may include one or more NTCRMs of Example A10, where the instructions, when executed, further configure the gNB to: identify a restriction that the UE should not be configured with code block group (CBG) based transmission on a cell in a PDSCH group configured for multi-cell scheduling; and schedule one or more additional PDSCHs based on the restriction.

[0147] Example A20 may include one or more NTCRMs of Example A10, where the instructions, when executed, further configure the gNB to: identify a restriction that the UE should not be configured with multi-PDSCH scheduling on cells in a PDSCH group configured for multi-cell scheduling; and schedule one or more additional PDSCHs based on the restriction.

[0148] Example B1 may include a method of wireless communication, the method including: a UE receiving a configuration of a search space set of a DCI format for multi-cell scheduling; and the UE detecting a DCI format for multi-cell scheduling, and receiving one or more PDSCHs or transmitting one or more PUSCHs according to a downlink (DL) assignment or an uplink (UL) grant in the detected DCI format.

[0149] Example B2 may include the method of example B1 or some other example herein, where multiple PDSCHs scheduled by the DCI for multi-cell scheduling are associated with different TBs.

[0150] Example B3 may include the method of Example B2 or some other examples herein, where for a type 2 codebook, the DAI is counted according to a serving cell index of a reference PDSCH among multiple PDSCHs scheduled by a DCI for multi-cell scheduling.

[0151] Example B4 may include the method of Example B2 or some other example herein, where for a Type-2 codebook, the HARQ-ACK for PDSCH scheduled by DCI for multi-cell scheduling and the HARQ-ACK for PDSCH scheduled by DCI for single-cell scheduling are in different sub-codebooks.

[0152] Example B5 may include the method of Example B2 or some other example herein, where for a Type-2 codebook, the HARQ-ACK for PDSCH scheduled by DCI for multi-cell scheduling and the HARQ-ACK for PDSCH scheduled by DCI for single-cell scheduling are in the same sub-codebook.

[0153] Example B6 may include the method of example B4 or example B5 or some other example herein, where for a type-2 codebook, the DAI counts PDCCHs in the same sub-codebook.

[0154] Example B7 may include the method of example B5 or some other example herein, where for a type-2 codebook, the DAI counts PDSCHs in the same sub-codebook.

[0155] Example B8 may include a method for a user equipment (UE), the method including receiving a configuration of a search space set for a downlink control information (DCI) format for multi-cell scheduling, detecting DCI having the DCI format based on the configuration, the DCI including a downlink (DL) assignment or an uplink (UL) grant, and receiving a plurality of physical downlink shared channels (PDSCHs) according to the DL assignment or transmitting a plurality of physical uplink shared channels (PUSCHs) according to the UL grant.

[0156] Example B9 may include the method of example B8 or some other example herein, wherein the multiple PDSCHs are associated with different transport blocks (TBs).

[0157] Example B10 may include the method of example B9 or some other examples herein, wherein the DAI is counted according to a serving cell index of a reference PDSCH of the multiple PDSCHs.

[0158] Example B11 may include the method of Example B9 or some other example herein, wherein a Hybrid Automatic Repeat Request (HARQ)-acknowledgement (ACK) for the multiple PDSCHs scheduled by the DCI uses a different sub-codebook than a HARQ-ACK for a single PDSCH scheduled for single-cell scheduling.

[0159] Example B12 may include the method of Example B9 or some other example herein, wherein Hybrid Automatic Repeat Request (HARQ)-acknowledgement (ACK) for the multiple PDSCHs scheduled by the DCI uses the same sub-codebook as a HARQ-ACK for a single PDSCH scheduled for single-cell scheduling.

[0160] Example B13 may include the method of Example B11, Example B12, or some other example herein, where the DAI counts one or more PDCCHs in a same sub-codebook used for multi-cell scheduling.

[0161] Example B14 may include the method of example B12 or some other example herein, where the DAI counts PDSCHs in the same sub-codebook used for multi-cell scheduling.

[0162] Example B15 may include the method of any of Examples B8 to B14 or some other examples herein, wherein the PDSCH or PUSCH is associated with a Type 2 codebook.

[0163] Example B16 may include a method for a next generation Node B (gNB), the method including: configuring, for a user equipment (UE), a search space set for downlink control information (DCI) formats for multi-cell scheduling; transmitting DCI having the DCI format to the UE based on the search space set, the DCI including a downlink (DL) assignment for a plurality of physical uplink shared channels (PUSCHs) or an uplink (UL) grant for a plurality of physical uplink shared channels (PUSCHs); and transmitting one or more of the PDSCHs in accordance with the DL assignments or receiving one or more of the PUSCHs in accordance with the UL grants.

[0164] Example B17 may include the method of example B16 or some other example herein, wherein the multiple PDSCHs are associated with different transport blocks (TBs).

[0165] Example B18 may include the method of example B17 or some other example herein, wherein the DAI is counted according to a serving cell index of a reference PDSCH among the multiple PDSCHs.

[0166] Example B19 may include the method of Example B17 or some other example herein, wherein a Hybrid Automatic Repeat Request (HARQ)-acknowledgement (ACK) for the multiple PDSCHs scheduled by the DCI uses a different sub-codebook than a HARQ-ACK for a single PDSCH scheduled for single-cell scheduling.

[0167] Example B20 may include the method of Example B17 or some other example herein, wherein Hybrid Automatic Repeat Request (HARQ)-acknowledgement (ACK) for the multiple PDSCHs scheduled by the DCI uses the same sub-codebook as a HARQ-ACK for a single PDSCH scheduled for single-cell scheduling.

[0168] Example B21 may include the method of Example B19, Example B20, or some other example herein, where the DAI counts one or more PDCCHs in a same sub-codebook used for multi-cell scheduling.

[0169] Example B22 may include the method of example B20 or some other example herein, where the DAI counts PDSCHs in the same sub-codebook used for multi-cell scheduling.

[0170] Example B23 may include the method of any of Examples B16 to B22 or some other examples herein, wherein the PDSCH or PUSCH is associated with a Type 2 codebook.

[0171] Example Z01 may include an apparatus having means for performing one or more elements of the method described or related to any of Examples A1-A20, Examples B1-B23, or any other method or process described herein.

[0172] Example Z02 may include one or more non-transitory computer-readable media having instructions that, upon execution of the instructions by one or more processors of the electronic device, cause an electronic device to perform one or more elements of a method described or related to any of Examples A1-A20, Examples B1-B23, or any other method or process described herein.

[0173] Example Z03 may include an apparatus having logic, modules, or circuitry that performs one or more elements of the methods described or related to any of Examples A1-A20, Examples B1-B23, or any other methods or processes described herein.

[0174] Example Z04 may include any method, technique, or process described or related to any of Examples A1-A20, B1-B23, or any part or portion thereof.

[0175] Example Z05 may include an apparatus having one or more processors and one or more computer-readable media having instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any of Examples A1-A20, Examples B1-B23, or portions thereof.

[0176] Example Z06 may include signals described or related to any of Examples A1-A20, Examples B1-B23, or any part or portion thereof.

[0177] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples A1-A20, Examples B1-B23, or any part or portion thereof, or otherwise described in this disclosure.

[0178] Example Z08 may include a signal encoded with data described or related to any of Examples A1-A20, Examples B1-B23, or any part or portion thereof, or as otherwise described in this disclosure.

[0179] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples A1-A20, Examples B1-B23, or any part or portion thereof, or otherwise described in this disclosure.

[0180] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any or any portion of Examples A1-A20, Examples B1-B23.

[0181] Example Z11 may include a computer program having instructions, the execution of which by a processing element causes the processing element to perform a method, technique, or process described in or related to any of Examples A1-A20, Examples B1-B23, or any portion thereof.

[0182] Example Z12 may include signals in a wireless network as shown and described herein.

[0183] Example Z13 may include a method of communicating within a wireless network as shown and described herein.

[0184] Example Z14 may include a system for providing wireless communication as shown and described herein.

[0185] Example Z15 may include devices that provide wireless communication as shown and described herein.

[0186] Any of the above examples may be combined with any other example (or combination of examples) unless expressly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0187] Abbreviation Unless used differently herein, the terms, definitions, and abbreviations may be consistent with those defined in 3GPP® TR 21.905 v16.0.0(2019-06). For purposes of this document, the following abbreviations may apply to the examples and embodiments described herein: 3GPP(registered trademark) Third Generation Partnership Project 4G Fourth Generation 5G Fifth Generation 5GC 5G Core network AC Application Client ACR Application Context Relocation ACK Acknowledgement Delivery confirmation ACID Application Client Identification AF Application Function AM Acknowledged Mode AMBR Aggregate Maximum Bit Rate AMF Access and Mobility Management Function AN Access Network ANR Automatic Neighbour Relation AOA Angle of Arrival AP Application Protocol Antenna Port Access Point API Application Programming Interface APN Access Point Name Access Point Name ARP Allocation and Retention Priority ARQ Automatic Repeat Request Automatic repeat request AS Access Stratum Access stratum ASP Application Service Provider ASN.1 Abstract Syntax Notation One AUSF Authentication Server Function Authentication server function AWGN Additive White Gaussian Noise Additive White Gaussian Noise BAP Backhaul Adaptation Protocol BCH Broadcast Channel BER Bit Error Ratio Bit Error Rate BFD Beam Failure Detection BLER Block Error Rate BPSK Binary Phase Shift Keying BRAS Broadband Remote Access Server BSS Business Support System BS Base Station BSR Buffer Status Report BW Bandwidth BWP Bandwidth Part C-RNTI Cell Radio Network Temporary Identity Cell Radio Network Temporary Identity CA Carrier Aggregation Certification Authority CAPEX CAPital EXpenditure Capital Expenditure CBRA Contention Based Random Access CC Component Carrier Country Code Cryptographic Checksum CCA Clear Channel Assessment CCE Control Channel Element CCCH Common Control Channel CE Coverage Enhancement CDM Content Delivery Network CDMA Code-Division Multiple Access CDR Charging Data Request CDR Charging Data Response CFRA Contention Free Random Access CG Cell Group CGF Charging Gateway Function CHF Charging Function CI Cell Identity Cell Identifier CID Cell-ID Cell ID (e.g. positioning method) CIM Common Information Model CIR Carrier to Interference Ratio CK Cipher Key CM Connection Management Conditional Mandatory CMAS Commercial Mobile Alert Service CMD Command CMS Cloud Management System Cloud Management System CO Conditional Optional CoMP Coordinated Multi-Point CORESET Control Resource Set COTS Commercial Off-The-Shelf CP Control Plane Cyclic Prefix Connection Point CPD Connection Point Descriptor CPE Customer Premise Equipment CPICH Common Pilot Channel CQI Channel Quality Indicator CPU CSI processing unit Central Processing Unit C / R Command / Response field bit CRAN Cloud Radio Access Network Cloud RAN CRB Common Resource Block CRC Cyclic Redundancy Check Cyclic Redundancy Check CRI Channel-State Information Resource Indicator Channel state information resource indicator, CSI-RS resource indicator C-RNTI Cell RNTI Cell RNTI CS Circuit Switched CSCF call session control function CSAR Cloud Service Archive Cloud Service Archive CSI Channel-State Information CSI-IM CSI Interference Measurement CSI Interference Measurement CSI-RS CSI Reference Signal CSI reference signal CSI-RSRP CSI reference signal received power CSI reference signal received power CSI-RSRQ CSI reference signal received quality CSI reference signal received quality CSI-SINR CSI signal-to-noise and interference ratio CSMA Carrier Sense Multiple Access CSMA / CA CSMA with collision avoidance CSMA / Collision avoidance CSS Common Search Space Cell-specific Search Space CTF Charging Trigger Function CTS Clear-to-Send Clear-to-Send CW Codeword CWS Contention Window Size D2D Device-to-Device DC Dual Connectivity Direct Current DCI Downlink Control Information DF Deployment Flavour DL Downlink DMTF Distributed Management Task Force DPDK Data Plane Development Kit DM-RS, DMRS Demodulation Reference Signal DN Data network DNN Data Network Name Data Network Name DNAI Data Network Access Identifier DRB Data Radio Bearer DRS Discovery Reference Signal DRX Discontinuous Reception DSL Domain Specific Language Digital Subscriber Line DSLAM DSL Access Multiplexer DSL Access Multiplexer DwPTS Downlink Pilot Time Slot Downlink Pilot Time Slot E-LAN ​​Ethernet Local Area Network Ethernet (registered trademark) local area network E2E End-to-End EAS Edge Application Server Edge Application Server ECCA extended clear channel assessment, extended CCA ECCE Enhanced Control Channel Element Enhanced CCE ED Energy Detection EDGE Enhanced Datarates for GSM Evolution Enhanced Datarates for GSM Evolution (GSM Evolution) EAS Edge Application Server Edge Application Server EASID Edge Application Server Identification ECS Edge Configuration Server Edge Configuration Server ECSP Edge Computing Service Provider Edge Computing Service Provider EDN Edge Data Network EEC Edge Enabler Client EECID Edge Enabler Client Identification Edge Enabler Client Identification EES Edge Enabler Server EESID Edge Enabler Server Identification Edge Enabler Server Identification EHE Edge Hosting Environment EGMF Exposure Governance Management Function EGPRS Enhanced GPRS EIR Equipment Identity Register ELaA enhanced Licensed Assisted Access Enhanced Licensed Assisted Access, Enhanced LAA EM Element Manager eMBB Enhanced Mobile Broadband EMS Element Management System eNB evolved NodeB Evolved Node B, E-UTRAN Node B EN-DC E-UTRA-NR Dual Connectivity E-UTRA-NR Dual Connectivity EPC Evolved Packet Core EPDCCH enhanced PDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel EPRE Energy per resource element EPS Evolved Packet System EREG enhanced REG, Enhanced Resource Element Group ETSI European Telecommunications Standards Institute ETWS Earthquake and Tsunami Warning System eUICC embedded UICC embedded universal integrated circuit card E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN EV2X Enhanced V2X F1AP F1 Application Protocol F1 Application Protocol F1-C F1 Control plane interface F1-U F1 User plane interface F1 User plane interface FACCH Fast Associated Control CHannel FACCH / F Fast Associated Control Channel / Full rate FACCH / H Fast Associated Control Channel / Half rate FACH Forward Access Channel FAUSCH Fast Uplink Signalling Channel FB Functional Block FBI Feedback Information FCC Federal Communications Commission FCCH Frequency Correction Channel FDD Frequency Division Duplex FDM Frequency Division Multiplex FDMA Frequency Division Multiple Access FE Front End FEC Forward Error Correction FFS For Further Study FFT Fast Fourier Transformation feLAA further enhanced Licensed Assisted Access Further enhanced licensed assisted access, further enhanced LAA FN Frame Number FPGA Field-Programmable Gate Array FR Frequency Range FQDN Fully Qualified Domain Name G-RNTI GERAN Radio Network Temporary Identity GERAN Radio Network Temporary Identity GERAN GSM EDGE RAN GSM Edge RAN, GSM Edge Radio Access Network GGSN Gateway GPRS Support Node GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English name: Global Navigation Satellite System) Global Navigation Satellite System gNB Next Generation NodeB Next Generation NodeB gNB-CU gNB-centralized unit, Next Generation NodeB centralized unit gNB centralized unit, Next Generation NodeB centralized unit gNB-DU gNB-distributed unit, Next Generation NodeB distributed unit gNB distributed unit, Next Generation NodeB distributed unit GNSS Global Navigation Satellite System GPRS General Packet Radio Service GPSI Generic Public Subscription Identifier GSM Global System for Mobile Communication GTP GPRS Tunneling Protocol GTP-U GPRS Tunnelling Protocol for User Plane GPRS Tunnelling Protocol for User Plane GTS Go To Sleep Signal (WUS related) GUMMEI Globally Unique MME Identifier Globally Unique MME Identifier GUTI Globally Unique Temporary UE Identity Globally Unique Temporary UE Identity HARQ Hybrid ARQ, Hybrid Automatic Repeat Request HANDO Handover HFN HyperFrame Number HyperFrame Number HHO Hard Handover HLR Home Location Register HN Home Network HO Handover HPLMN Home Public Land Mobile Network HSDPA High Speed ​​Downlink Packet Access HSN Hopping Sequence Number Hopping sequence number HSPA High Speed ​​Packet Access HSS Home Subscriber Server HSUPA High Speed ​​Uplink Packet Access HTTP Hyper Text Transfer Protocol HTTPS Hyper Text Transfer Protocol Secure (https is http / 1.1 over SSL, i.e. port 443) I-Block Information Block ICCID Integrated Circuit Card Identification IAB Integrated Access and Backhaul ICIC Inter-Cell Interference Coordination ID Identity, identifier IDFT Inverse Discrete Fourier Transform IE Information element IBE In-Band Emission In-band emission IEEE Institute of Electrical and Electronics Engineers IEI Information Element Identifier IEIDL Information Element Identifier Data Length IETF Internet Engineering Task Force IF Infrastructure IIOT Industrial Internet of Things IM Interference Measurement Intermodulation IP Multimedia IMC IMS Credentials IMS Credentials IMEI International Mobile Equipment Identity IMGI International mobile group identity IMPI IP Multimedia Private Identity IMPU IP Multimedia PUblic identity IP Multimedia Public Identifier IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IoT Internet of Things IP Internet Protocol Ipsec IP Security, Internet Protocol Security IP Security, Internet Protocol Security IP-CAN IP-Connectivity Access Network IP Connectivity Access Network IP-M IP Multicast IP Multicast IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 IR Infrared IS In Sync IRP Integration Reference Point ISDN Integrated Services Digital Network ISIM IM Services Identity Module ISO International Organisation for Standardisation ISP Internet Service Provider IWF Interworking-Function I-WLAN Interworking WLAN kB Kilobyte Kilobyte (1000 bytes). kbps kilo-bits per second Kc Ciphering key Ki Individual subscriber authentication key KPI Key Performance Indicator KQI Key Quality Indicator KSI Key Set Identifier ksps kilo-symbols per second KVM Kernel Virtual Machine L1 Layer 1 Layer 1 (physical layer) L1-RSRP Layer 1 reference signal received power L2 Layer 2 (Data Link Layer) L3 Layer 3 (Network Layer) LAA Licensed Assisted Access LAN Local Area Network LADN Local Area Data Network Local Area Data Network LBT Listen Before Talk LCM LifeCycle Management LCR Low Chip Rate LCS Location Services LCID Logical Channel ID Logical Channel ID LI Layer Indicator LLC Logical Link Control Low Layer Compatibility LMF Location Management Function LOS Line of Sight LPLMN Local PLMN LPP LTE Positioning Protocol LSB Least Significant Bit LTE Long Term Evolution LWA LTE-WLAN aggregation LTE-WLAN aggregation LWIP LTE / WLAN Radio Level Integration with IPsec Tunnel LTE Long Term Evolution M2M Machine-to-Machine MAC Medium Access Control (Protocol Layer Context) MAC Message authentication code (security / cryptography context) MAC-A MAC used for authentication and key agreement (TSG T WG3 context) MAC-I MAC used for data integrity of signalling messages (TSG T WG3 context) MANO Management and Orchestration Management and Orchestration MBMS Multimedia Broadcast and Multicast Service MBSFN Multimedia Broadcast multicast service Single Frequency Network MCC Mobile Country Code MCG Master Cell Group MCOT Maximum Channel Occupancy Time MCS Modulation and coding scheme MDAF Management Data Analytics Function MDAS Management Data Analytics Service Management Data Analytics Service MDT Minimization of Drive Tests ME Mobile Equipment MeNB master eNB MER Message Error Ratio Message Error Ratio MGL Measurement Gap Length MGRP Measurement Gap Repetition Period Measurement gap repetition period MIB Master Information Block Management Information Base MIMO Multiple Input Multiple Output MLC Mobile Location Centre MM Mobility Management Mobility Management MME Mobility Management Entity MN Master Node MNO Mobile Network Operator MO Measurement Object Mobile Originated MPBCH MTC Physical Broadcast CHannel MPDCCH MTC Physical Downlink Control CHannel MPDSCH MTC Physical Downlink Shared CHannel MPRACH MTC Physical Random Access CHannel MPUSCH MTC Physical Uplink Shared Channel MPLS MultiProtocol Label Switching MS Mobile Station Mobile station MSB Most Significant Bit MSC Mobile Switching Centre MSI Minimum System Information MCH Scheduling Information MSID Mobile Station Identifier MSIN Mobile Station Identification Number MSISDN Mobile Subscriber ISDN Number MT Mobile Terminated, Mobile Termination MTC Machine-Type Communications mMTC massive MTC, massive Machine-Type Communications MU-MIMO Multi User MIMO Multi User MIMO MWUS MTC wake-up signal, MTC WUS MTC wake-up signal NACK Negative Acknowledgement NAI Network Access Identifier NAS Non-Access Stratum, Non-Access Stratum layer NCT Network Connectivity Topology NC-JT Non-Coherent Joint Transmission NEC Network Capability Exposure NE-DC NR-E-UTRA Dual Connectivity NR-E-UTRA Dual Connectivity NEF Network Exposure Function NF Network Function NFP Network Forwarding Path NFPD Network Forwarding Path Descriptor NFV Network Functions Virtualization NFVI NFV Infrastructure NFV Infrastructure NFVO NFV Orchestrator NFV Orchestrator NG Next Generation, Next Gen Next Generation NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NG-RAN E-UTRA-NR Dual Connectivity NM Network Manager NMS Network Management System N-PoP Network Point of Presence NMIB, N-MIB Narrowband MIB NPBCH Narrowband Physical Broadcast CHannel NPDCCH Narrowband Physical Downlink Control CHannel NPDSCH Narrowband Physical Downlink Shared CHannel NPRACH Narrowband Physical Random Access CHannel NPUSCH Narrowband Physical Uplink Shared CHannel NPSS Narrowband Primary Synchronization Signal NSSS Narrowband Secondary Synchronization Signal NR New Radio New Radio Neighbor Relation NRF NF Repository Function NRS Narrowband Reference Signal NS Network Service NSA Non-Standalone operation mode NSD Network Service Descriptor NSR Network Service Record NSSAI Network Slice Selection Assistance Information S-NNSAI Single-NSSAI Single NSSAI NSSF Network Slice Selection Function NW Network NWUS Narrowband wake-up signal, Narrowband WUS NZP Non-Zero Power O&M Operation and Maintenance ODU2 Optical channel Data Unit - type 2 OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OOB Out-of-band OOS Out of Sync OPEX OPErating EXpense operating expenses OSI Other System Information OSS Operations Support System OTA over-the-air PAPR Peak-to-Average Power Ratio Peak-to-Average Power Ratio PAR Peak to Average Ratio PBCH Physical Broadcast Channel PC Power Control Personal Computer PCC Primary Component Carrier, Primary CC P-CSCF Proxy CSCF PCell Primary Cell PCI Physical Cell ID, Physical Cell Identity PCEF Policy and Charging Enforcement Function PCF Policy Control Function PCRF Policy Control and Charging Rules Function PDCP Packet Data Convergence Protocol Packet Data Convergence Protocol layer PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDN Packet Data Network Public Data Network PDSCH Physical Downlink Shared Channel Physical Downlink Shared Channel PDU Protocol Data Unit PEI Permanent Equipment Identifiers PFD Packet Flow Description P-GW PDN Gateway PDN Gateway PHICH Physical hybrid-ARQ indicator channel PHY Physical layer PLMN Public Land Mobile Network PIN Personal Identification Number PM Performance Measurement Performance measurement PMI Precoding Matrix Indicator PNF Physical Network Function PNFD Physical Network Function Descriptor PNFR Physical Network Function Record POC PTT over Cellular PTT over Cellular PP, PTP Point-to-Point PPP Point-to-Point Protocol PRACH Physical RACH Physical RACH PRB Physical resource block PRG Physical resource block group ProSe Proximity Service, Proximity-Based Service PRS Positioning Reference Signal PRR Packet Reception Radio PS Packet Services PSBCH Physical Sidelink Broadcast Channel PSDCH Physical Sidelink Downlink Channel PSCCH Physical Sidelink Control Channel PSSCH Physical Sidelink Shared Channel PSCell Primary SCell Primary SCell PSS Primary Synchronization Signal PSTN Public Switched Telephone Network PT-RS Phase-tracking reference signal Phase-tracking reference signal PTT Push-to-Talk PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel Physical Uplink Shared Channel QAM Quadrature Amplitude Modulation QCI QoS class of identifier QoS class of identifier QCL Quasi co-location QFI QoS Flow ID, QoS Flow Identifier QoS flow ID, QoS flow identifier QoS Quality of Service QPSK Quadrature (Quaternary) Phase Shift Keying QZSS Quasi-Zenith Satellite System RA-RNTI Random Access RNTI Random Access RNTI RAB Radio Access Bearer Random Access Burst RACH Random Access Channel RADIUS Remote Authentication Dial In User Service RAN Radio Access Network RAND RANDom number Random number (used for authentication) RAR Random Access Response RAT Radio Access Technology RAU Routing Area Update RB Resource block Radio Bearer RBG Resource block group REG Resource Element Group Resource Element Group Release REQ REQuest Request RF Radio Frequency RI Rank Indicator RIV Resource indicator value RL Radio Link RLC Radio Link Control Radio Link Control layer RLC AM RLC Acknowledged Mode RLC acknowledged mode RLC UM RLC Unacknowledged Mode RLC Unacknowledged Mode RLF Radio Link Failure Radio Link Failure RLM Radio Link Monitoring RLM-RS Reference Signal for RLM Reference signal for RLM RM Registration Management RMC Reference Measurement Channel RMSI Remaining MSI Remaining Minimum System Information Remaining Minimum System Information RN Relay Node RNC Radio Network Controller RNL Radio Network Layer RNTI Radio Network Temporary Identifier ROHC RObust Header Compression RRC Radio Resource Control Radio Resource Control layer RRM Radio Resource Management RS Reference Signal Reference signal RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality RSSI Received Signal Strength Indicator RSU Road Side Unit RSTD Reference Signal Time Difference RTP Real Time Protocol RTS Ready-To-Send RTT Round Trip Time Rx Reception, Receiving Receiver S1AP S1 Application Protocol S1-MME S1 for the control plane S1-U S1 for the user plane S-CSCF serving CSCF S-GW Serving Gateway S-RNTI SRNC Radio Network Temporary Identity SRNC Radio Network Temporary Identity S-TMSI SAE Temporary Mobile Station Identifier SAE Temporary Mobile Station Identifier SA Standalone operation mode SAE System Architecture Evolution SAP Service Access Point SAPD Service Access Point Descriptor SAPI Service Access Point Identifier SCC Secondary Component Carrier, Secondary CC Secondary component carrier, secondary CC SCell Secondary Cell Secondary Cell SCEF Service Capability Exposure Function SC-FDMA Single Carrier Frequency Division Multiple Access SCG Secondary Cell Group SCM Security Context Management SCS Subcarrier Spacing SCTP Stream Control Transmission Protocol SDAP Service Data Adaptation Protocol Service Data Adaptation Protocol layer SDL Supplementary Downlink SDNF Structured Data Storage Network Function SDP Session Description Protocol SDSF Structured Data Storage Function SDT Small Data Transmission SDU Service Data Unit SEAF Security Anchor Function SeNB secondary eNB SEPP Security Edge Protection Proxy SFI Slot format indication SFTD Space-Frequency Time Diversity SFN and frame timing difference SFN System Frame Number SGnB Secondary gNB Secondary gNB SGSN Serving GPRS Support Node S-GW Serving Gateway SI System Information SI-RNTI System Information RNTI System Information RNTI SIB System Information Block SIM Subscriber Identity Module SIP Session Initiated Protocol SiP System in Package SL Sidelink SLA Service Level Agreement SM Session Management SMF Session Management Function SMS Short Message Service SMSF SMS Function SMTC SSB-based Measurement Timing Configuration SN Secondary Node Secondary Node Sequence Number SoC System on Chip SON Self-Organizing Network SPCell Special Cell Special Cell SP-CSI-RNTI Semi-Persistent CSI RNTI Semi-Persistent CSI RNTI SPS Semi-Persistent Scheduling SQN Sequence number SR Scheduling Request SRB Signalling Radio Bearer SRS Sounding Reference Signal SS Synchronization Signal Synchronization signal SSB Synchronization Signal Block SSID Service Set Identifier SS / PBCH Block SSBRI SS / PBCH Block SSBRI SS / PBCH Block Resource Indicator Synchronization Signal Block Resource Indicator SSC Session and Service Continuity SS-RSRP Synchronization Signal based Reference Signal Received Power SS-RSRQ Synchronization Signal based Reference Signal Received Quality SS-SINR Synchronization Signal based Signal to Noise and Interference Ratio SSS Secondary Synchronization Signal SSSG Search Space Set Group SSSIF Search Space Set Indicator SST Slice / Service Types SU-MIMO Single User MIMO SUL Supplementary Uplink TA Timing Advance Tracking Area TAC Tracking Area Code TAG Timing Advance Group TAI Tracking Area Identity Tracking Area Identifier TAU Tracking Area Update TB Transport Block TBS Transport Block Size TBD To Be Defined TCI Transmission Configuration Indicator TCP Transmission Communication Protocol TDD Time Division Duplex Time Division Duplex TDM Time Division Multiplexing TDMA Time Division Multiple Access TE Terminal Equipment TEID Tunnel End Point Identifier TFT Traffic Flow Template TMSI Temporary Mobile Subscriber Identity TNL Transport Network Layer TPC Transmit Power Control TPMI Transmitted Precoding Matrix Indicator TR Technical Report TRP, TRxP Transmission Reception Point TRS Tracking Reference Signal TRx Transceiver TS Technical Specifications Technical Standard TTI Transmission Time Interval Tx Transmission, Transmitting Transmitter U-RNTI UTRAN Radio Network Temporary Identity UTRAN Radio Network Temporary Identity UART Universal Asynchronous Receiver and Transmitter Universal Asynchronous Receiver and Transmitter UCI Uplink Control Information UE User Equipment UDM Unified Data Management UDP User Datagram Protocol UDSF Unstructured Data Storage Network Function Unstructured Data Storage Network Function UICC Universal Integrated Circuit Card UL Uplink UM Unacknowledged Mode UML Unified Modelling Language UMTS Universal Mobile Telecommunications System UP User Plane UPF User Plane Function URI Uniform Resource Identifier URL Uniform Resource Locator URLLC Ultra-Reliable and Low Latency USB Universal Serial Bus USIM Universal Subscriber Identity Module USS UE-specific search space UTRA UMTS Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access UwPTS Uplink Pilot Time Slot V2I Vehicle-to-Infrastruction V2P Vehicle-to-Pedestrian V2V Vehicle-to-Vehicle V2X Vehicle-to-everything VIM Virtualized Infrastructure Manager VL Virtual Link Virtual Link. VLAN Virtual LAN, Virtual Local Area Network VM Virtual Machine VNF Virtualized Network Function VNFFG VNF Forwarding Graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNF Manager VNF Manager VoIP Voice-over-IP, Voice-over-Internet Protocol VPLMN Visited Public Land Mobile Network VPN Virtual Private Network VRB Virtual Resource Block WiMAX Worldwide Interoperability for Microwave Access WLAN Wireless Local Area Network WMAN Wireless Metropolitan Area Network WPAN Wireless Personal Area Network X2-C X2-Control plane X2-Control plane X2-U X2-User plane X2-User plane XML eXtensible Markup Language XRES EXpected user RESponse Expected user response XOR eXclusive OR exclusive OR ZC Zadoff-Chu ZP Zero Power

[0188] Terminology For purposes of this document, the following terms and definitions are applicable to the rays and embodiments described herein.

[0189] The term "circuitry" as used herein refers to, is a part of, or includes hardware components, such as electronic circuits, logic circuits, processors (shared, dedicated, or groups) and / or memories (shared, dedicated, or groups), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high performance PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc., configured to provide a described functionality. In some embodiments, a circuitry may provide at least a portion of the described functionality by executing one or more software or firmware programs. The term "circuitry" may also refer to a combination of one or more hardware elements with program code (or a combination of circuitry used in an electrical or electronic system) that is used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0190] The term "processor circuitry" as used herein refers to, is a part of, or includes circuitry capable of automatically performing a series of arithmetic or logical operations in sequence, or recording, storing, and / or transferring digital data. The processing circuitry may include one or more processing cores for executing instructions, and one or more memory structures for storing program and data information. The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single-core processors, dual-core processors, triple-core processors, quad-core processors, and / or any other device capable of executing or otherwise processing computer-executable instructions, e.g., program code, software modules, and / or functional processes. The processing circuitry may include more hardware accelerators, which may be microprocessors or programmable processing devices, etc. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with, and may be referred to as, "processor circuitry."

[0191] As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as, for example, a bus, an I / O interface, a peripheral component interface, a network interface card, and / or the like.

[0192] The term "user equipment" or "UE" as used herein refers to a device having wireless communication capabilities and may represent a remote user of network resources in a communications network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless device, reconfigurable wireless device, reconfigurable mobile device, etc.

[0193] The term "network element" as used herein refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or may be referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN equipment, RAN node, gateway, server, virtualized VNF, NFVI, and / or the like.

[0194] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computing equipment, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. Additionally, the terms "computer system" and / or "system" may refer to multiple computing equipment and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.

[0195] As used herein, the terms "appliance," "computer appliance," or the like, refer to a computing device or system having program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computing appliance or is otherwise dedicated to providing specific computing resources.

[0196] The term "resource" as used herein refers to physical or virtual devices, physical or virtual components in a computing environment, and / or physical or virtual components in a particular device, such as, for example, computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, workload units, and / or the like. The term "hardware resources" may refer to computational, storage, and / or network resources provided by (one or more) physical hardware elements. "Virtualized resources" may refer to computational, storage, and / or network resources provided by a virtualization infrastructure to an application, device, system, etc. The term "network resources" or "communication resources" may refer to resources accessible by a computer device / system via a communication network. The term "system resources" may refer to any type of shared entity for providing services and may include computing resources and / or network resources. A system resource may be viewed as a set of coherent functions, network data objects, or services accessible via a server, where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0197] The term "channel," as used herein, refers to any transmission medium, either tangible or intangible, used to communicate data or data streams. The term "channel" may be synonymous and / or equivalent to "communications channel," "data communications channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar term describing the path or medium over which data is communicated.

[0198] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" may also refer to a specific occurrence of an object that may occur, for example, during the execution of program code.

[0199] The terms "coupled" and "communicatively coupled," along with their derivatives, are used herein. The term "coupled" can mean that two or more elements are in direct physical or electrical contact with each other, can mean that two or more elements are in only indirect contact with each other but still cooperate or interact with each other, and / or can mean that one or more other elements are coupled or connected between the elements that are said to be coupled to each other. The term "directly coupled" can mean that two or more elements are in direct contact with each other. The term "communicatively coupled" can mean that two or more elements may be in contact with each other by any means of communication, including via a wire or other interconnection, via a wireless communication channel or link, and / or the like.

[0200] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of the information element or the data element that contains the contents.

[0201] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0202] The term "SSB" refers to SS / PBCH block.

[0203] The term "primary cell" refers to an MCG cell operating on a primary frequency in which a UE either performs an initial connection establishment procedure or initiates a connection reestablishment procedure.

[0204] The term "primary SCG cell" refers to the SCG cell in which the UE performs random access when reconfiguring using the synchronization procedure for DC operation.

[0205] The term "secondary cell" refers to a cell that provides additional radio resources to a UE configured with CA in addition to a special cell.

[0206] The term "secondary cell group" refers to a subset of serving cells that includes a PSCell and zero or more secondary cells for a UE configured with a DC.

[0207] The term "Serving Cell" refers to a primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and only one serving cell is included in the primary cells.

[0208] The term “serving cell” or “serving cells” refers to a set of cells including the special cell(s) and all secondary cells for a UE that is in RRC_CONNECTED and configured with CA / .

[0209] The term "special cell" refers to a PCell of an MCG or a PSCell of an SCG for DC operation, otherwise the term "special cell" refers to a Pcell.

Claims

1. An apparatus for use in a user equipment (UE), comprising: a memory for storing received downlink control information (DCI) scheduling a plurality of physical downlink shared channels (PDSCHs) in a plurality of cells; one or more processors; Decoding a counter-downlink allocation index (C-DAI) of the DCI based on a reference cell; encoding a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback for the PDSCH based on the C-DAI; one or more processors configured to An apparatus having the above configuration.

2. The apparatus of claim 1 , wherein the HARQ-ACK feedback is encoded based on a second sub-codebook that is different from a first sub-codebook used for single-cell PDSCH scheduling.

3. The apparatus of claim 2 , wherein the C-DAI counts the number of physical downlink control channels (PDCCHs) that use the second sub-codebook.

4. 4. The apparatus of claim 2, wherein the one or more processors are further configured to determine a number of HARQ-ACK bits for the C-DAI in the HARQ-ACK feedback based on a maximum number of HARQ-ACK bits for a PDSCH that can be scheduled by a physical downlink control channel (PDCCH) in the second sub-codebook.

5. 4. The apparatus of claim 2, wherein HARQ-ACK information bits for the plurality of PDSCHs in the HARQ-ACK feedback in the second sub-codebook are ordered based on serving cell indexes of each of the plurality of cells.

6. 6. The apparatus of claim 5, wherein the HARQ-ACK information bits are mapped to bit positions first, and the one or more processors are further configured to add one or more padding bits after the HARQ-ACK information bits if a number of expected bits per physical downlink control channel (PDCCH) exceeds a number of the HARQ-ACK information bits for the multiple PDSCHs.

7. The apparatus of claim 1 , wherein the reference cell is selected from the plurality of cells based on a cell index.

8. The apparatus of claim 7 , wherein the reference cell is selected as the cell having the lowest cell index among the plurality of cells.

9. The reference cell is A serving cell for a reference PDSCH among the plurality of PDSCHs; or selected according to a start or end position of the reference cell among the plurality of cells; or Configured for the UE by a next generation Node B (gNB); 2. The apparatus of claim 1.

10. One or more non-transitory computer readable media (NTCRMs) having instructions stored thereon, the instructions, when executed by one or more processors of a next generation Node B (gNB), cause the gNB to: encoding downlink control information (DCI) that schedules a plurality of physical downlink shared channels (PDSCHs) in a plurality of cells for transmission to a user equipment (UE), the DCI including a reference cell-based counter-downlink allocation index (C-DAI); receiving a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback for the PDSCH based on the C-DAI; One or more NTCRMs configured to:

11. The one or more NTCRMs of claim 10, wherein the HARQ-ACK feedback is encoded based on a second sub-codebook that is different from a first sub-codebook used for single-cell PDSCH scheduling.

12. The one or more NTCRMs of claim 11, wherein the C-DAI counts the number of physical downlink control channels (PDCCHs) that used the second sub-codebook.

13. 13. The one or more NTCRMs of claim 11, wherein a number of HARQ-ACK bits for the C-DAI in the HARQ-ACK feedback is based on a maximum number of HARQ-ACK bits for a PDSCH that can be scheduled by a physical downlink control channel (PDCCH) in the second sub-codebook.

14. 13. The one or more NTCRMs of claim 11, wherein HARQ-ACK information bits for the multiple PDSCHs in the HARQ-ACK feedback in the second sub-codebook are ordered based on serving cell indexes of each of the multiple cells.

15. 15. The one or more NTCRMs of claim 14, wherein the HARQ-ACK information bits are mapped to bit positions first, and the HARQ-ACK feedback further includes one or more padding bits after the HARQ-ACK information bits if a number of expected bits per physical downlink control channel (PDCCH) exceeds the number of the HARQ-ACK information bits for the multiple PDSCHs.

16. The one or more NTCRMs of claim 10 , wherein the reference cell is selected from the plurality of cells based on a cell index.

17. The one or more NTCRMs of claim 16 , wherein the reference cell is selected as the cell having the lowest cell index among the plurality of cells.

18. The reference cell is A serving cell for a reference PDSCH among the plurality of PDSCHs; or selected according to a start or end position of the reference cell among the plurality of cells; or Configured by the gNB for the UE; One or more NTCRMs according to claim 10.

19. The instructions, when executed, further cause the gNB to: Identifying a restriction that the UE should not be configured with Code Block Group (CBG) based transmission on a cell in a PDSCH group configured for multi-cell scheduling; scheduling one or more additional PDSCHs based on said constraints; 11. One or more NTCRMs according to claim 10, configured to:

20. The instructions, when executed, further cause the gNB to: Identifying a restriction that the UE should not be configured with multi-PDSCH scheduling on cells in a PDSCH group configured for multi-cell scheduling; scheduling one or more additional PDSCHs based on said constraints; 11. One or more NTCRMs according to claim 10, configured to:

Images