Patent Description:
<NPL>) discusses enhancements for multi-TRP/panel transmission, and related proposals.

Advantageous, but optional features of the invention are recited in the accompanying dependent claims.

The present disclosure relates to updating a downlink assignment index (DAI) and a corresponding codebook in the case of a downlink control information (DCI) scheduling multiple component carriers (CCs), which may also be referred to herein as cells. The techniques described herein enable a base station and UE to accurately identify control signaling messages and/or data messages and their receipt status, particularly in the case of cross-carrier scheduling. As such, the present solutions may improve efficiency in cross-carrier scheduling scenarios, e.g., carrier aggregation, as well as in dynamic spectrum sharing scenarios.

In an implementation, for example, the disclosed methods, apparatus, and computer-readable media are directed to updating a downlink assignment index (DAI) communicated to a UE for reporting feedback on downlink signaling in a case where a single downlink control information (DCI) transmitted on the control channels of multiple component carriers schedules transmissions on each of the multiple component carriers. The DAI may be used to track a number of scheduled transmissions to be acknowledged based on a hybrid automatic repeat request (HARQ) codebook. According to the present aspects, in a DCI that schedules a physical downlink shared channel (PDSCH) on multiple component carriers, the DCI may be updated based on the number of component carriers. More particularly, the base station transmitting the DCI may update the DAI based on one or any combination of an index of a scheduled component carrier, a DAI counter value, and/or a monitoring occasion. Correspondingly, the feedback information from the UE, e.g., the HARQ codebook for a physical uplink control channel (PUCCH) transmission may also be updated and/or formatted based on the number of component carriers on which the DCI is received. More specifically, for instance, when transmitting bundled feedback information, the UE may updated the HARQ codebook such that each component carrier per detected DCI is counted as one position for a HARQ acknowledgement bit of the scheduled PDSCH in the PUCCH transmission. In an implementation, the UE may format the HARQ acknowledgement positions to be first sorted/ordered based on ascending order of scheduled component carrier index in the same PDCCH monitoring occasion, then based on ascending order of PDCCH monitoring occasion index.

Accordingly, in one or more examples, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions of code on a computer-readable medium.

Referring to <FIG>, an example of a wireless communications system (also referred to as a wireless wide area network (WWAN)) defines an access network <NUM> including base stations <NUM>, UEs <NUM>, an Evolved Packet Core (EPC) <NUM>, and another core network <NUM> (e.g., a <NUM> Core (5GC)).

According to the present aspects, the base station <NUM> and the UE <NUM> may have established communications on multiple component carriers (CC), and the base station <NUM> may schedule the UE <NUM> on multiple CCs using a single DC. Specifically, the base station <NUM> includes a communication component <NUM> in communication with the UE <NUM> and having a downlink assignment index (DAI) indication component <NUM> configured to generate DAI information <NUM> for transmission with a single downlink control information (DCI) <NUM> that schedules resources for monitoring by the UE <NUM> on a plurality of CCs. For example, the plurality of CCs may be up to n CCs, where n is a positive integer, and where such DCI is indicated by the notation DCICC1-CCn. For instance, the DCI <NUM> may perform cross-carrier scheduling by indicating resources to the UE <NUM> for a first downlink (DL) signal on a first CC, e.g., DL signalCC1 <NUM>, and up to an nth DL signal on an nth CC, e.g., up to DL signalCCn <NUM>. Further, for instance, the DAI information <NUM> may be used to identify specific feedback, e.g., feedback <NUM> up to feedback <NUM>, with respect to each of the scheduled DL signals on each of the multiple CCs within a set of bundled feedback information <NUM>, such as a HARQ codebook. The feedback may include, for example, an acknowledgement (ACK) or a negative acknowledgement (NACK) of each respective DL signal.

Correspondingly, the UE <NUM> may include a communication component <NUM> in communication with the base station <NUM> and having an ACK/NACK feedback indication component <NUM> configured to generate the bundled feedback information <NUM> based on the DAI information <NUM> from the DCI <NUM> and in response to receipt of the plurality of DL signals, e.g., DL signalCC1 <NUM> up to DL signalCCn <NUM>, on the multiple CCs.

As such, implementation of the present solution a base station and UE to accurately identify control signaling messages and/or data messages and their receipt status, particularly in the case of cross-carrier scheduling. As such, the present solutions may improve efficiency in cross-carrier scheduling scenarios, e g. , carrier aggregation, as well as in dynamic spectrum sharing scenarios. Further details of the present solution are described in detail in the subsequent figures.

The base stations <NUM> may include macrocells (e.g., a relatively higher power cellular base station) and/or small cells (e.g., relatively lower power cellular base station). Some of the base stations <NUM> may be configured for <NUM> LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through first backhaul links <NUM> (e.g., S1 interface). Some of the base stations <NUM> may be configured for <NUM> NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network <NUM> through second backhaul links <NUM>. The third backhaul links <NUM> may be wired or wireless.

The small cell <NUM>' may operate in a licensed and/or an unlicensed frequency spectrum When operating in an unlicensed frequency spectrum, the small cell <NUM>' may employ NR and use the same <NUM> unlicensed frequency spectrum as used by the Wi-Fi AP <NUM>.

The MME <NUM> may be in communication with a Home Subscriber Server (HSS) <NUM><NUM>. The PDN Gateway <NUM> and the BM-SC <NUM> are connected to the IF Services <NUM>.

The IP Services <NUM> may include the Internet, an intranet, an IP Multimedia Subsystems (IMS), a PS Streaming Service, and/or other IP services.

Although the present description may be focused on <NUM> NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

Referring to <FIG>, the base station <NUM> and UE <NUM> described herein may utilize one or more examples <NUM>, <NUM>, <NUM>, and/or <NUM> of frame structures, resources, and communication channels for exchanging communications as described herein.

<FIG> provide an example of slot configuration <NUM> with <NUM> symbols per slot and numerology µ=<NUM> with <NUM> slots per subframe. The slot duration is <NUM>, the subcarrier spacing is <NUM>, and the symbol duration is approximately <NUM>,.

Each time slot includes a resource block (R13) (also referred to as physical R13s (PRBs)) that extends <NUM> consecutive subcarriers.

Referring to <FIG>, some of the REs carry reference (pilot) signals (RS) for the UE.

Referring to <FIG>, diagram <NUM> includes an example of various DL channels within a subframe of a frame.

Referring to <FIG>, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH), The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH.

Referring to <FIG>, diagram <NUM> includes an example of various UL channels within a subframe of a frame. The PDSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI.

Referring to <FIG>, the base station <NUM> in communication with the UE <NUM> in the access network <NUM> may include a variety of hardware components for performing the communications described herein. The controller/processor <NUM> provides RRC layer functionality associated with broadcasting of system information (e. g, MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions, RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDDs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Similar to the functionality described in connection with the DL transmission by the base station <NUM>, the controller/processor <NUM> provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting, PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

At least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM> may be configured to perform aspects in connection with communication component <NUM> (<FIG>) as described herein.

Referring to <FIG>, an example cross-carrier scheduling scenario <NUM> includes the base station <NUM> and the UE <NUM> having established communications on multiple component carriers (CCs) <NUM> and utilizing one or more DAI / codebook updating rules <NUM> to enable the base station <NUM> to transmit the single DCI <NUM> to schedule DL signals <NUM>, <NUM> for receipt by the UE <NUM> on each of the multiple CCs <NUM>. Notably, the DCI <NUM> includes DAI information <NUM> that is updated according to one or more DAI / codebook updating rules <NUM> to enable the UE <NUM> to identify specific feedback relative the status of the receipt of the DL signals <NUM>, <NUM>, e.g., PDSCH<NUM> and PDSCH<NUM>, scheduled by the single DCI <NUM> on each of the multiple CCs <NUM>.

The DAI information <NUM> includes, but is not limited to, a counter-DAI (C-DAI) value or index and/or a total-DAI counter or index, which may be respective fields in the DAI information <NUM>. The C-DAI value indicates the accumulative number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release is present, up to the current serving cell and current PDCCH monitoring occasion. The T-DAI value, when present, indicates the total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release is present, up to the current PDCCH monitoring occasion and is updated from PDCCH monitoring occasion to the PDCCH monitoring occasion. The C-DAI value and/or T-DAI value may be explicitly signaled, or in some cases one of more of the C-DAI values and/or T-DAI values may be implicitly signaled, as is explained below.

Correspondingly, the cross-carrier scheduling scenario <NUM> includes the UE <NUM> transmitting bundled feedback information <NUM>, configured according to one or more DAI / codebook updating rules <NUM>, to the base station <NUM> in response to receiving the DL signals <NUM>, <NUM> scheduled by the single DCI <NUM> on each of the multiple CCs <NUM>. The base station <NUM> may then re-transmit unsuccessfully received or unsuccessfully decoded ones of the signals <NUM>, <NUM> based on the indications provided by the bundled feedback information <NUM>.

It should be noted that current DAI and codebook updating rules are not configured to account for a case of a single DCI scheduling PDSCH for multiple CCs. For example, current solutions cannot properly account for the scheduling of multiple CCs by a single DCI, thereby leading to inaccurate feedback or an inability to efficiently perform cross-carrier scheduling and/or dynamic spectrum sharing.

In contrast, the one or more DAI / codebook updating rules <NUM> are configured to enable this cross-carrier scheduling and/or dynamic spectrum sharing by providing a mechanism for accurate feedback reporting in an simple and efficient manner.

For example, for the base station <NUM>, in a case where the cross-carrier scheduling scenario <NUM> includes the DCI <NUM> scheduling multiple DL signals <NUM>, <NUM>, e.g. ,PDSCHs, on the plurality of CCs <NUM>, the one or more DAI / codebook updating rules <NUM> may instruct the base station <NUM> to update the DAI information <NUM> in the DCI <NUM> based on the following options:.

Option <NUM>: C-DAI and/or T-DAI values signaled in the DCI are increased by one per CC, e.g., n (number of the multiple CCs) in total; or.

Option <NUM>: C-DAI and/or T-DAI values signaled in the DCI are increased by one.

Alternatively, or in addition, for the UE <NUM>, in the case where the DCI <NUM> is scheduling multiple DL signals <NUM>, <NUM>, e.g. ,PDSCH, on the plurality of CCs <NUM>, the one or more DAI / codebook updating rules <NUM> may instruct the UE <NUM> to update the bundled feedback information <NUM>, e.g., the HARQ-ACK in the PUCCH codebook, based on the following option:.

Option <NUM>: Each scheduled CC per detected DCI is counted by UE as one position for the HARQ-ACK bit(s) of the corresponding scheduled PDSCH in the PUCCH codebook. In this case, the HARQ-ACK positions are first sorted based on ascending order of scheduled CC index (e.g., CC1 then CC2 and so on) in the same PDCCH monitoring occasion, then based on ascending order of PDCCH monitoring occasion index.

More specifically, continuing to refer to <FIG>, in scenario <NUM>, the multiple component carriers (CCs) <NUM> may be any plurality of CCs, e.g., up to n where n is a positive integer. To establish the multiple CCs <NUM>, the base station <NUM> and UE <NUM> may operate their respective communication components <NUM>, <NUM>, according to one or more communication protocols <NUM> that may instantiate, for example, one or more protocols stacks on each of the base station <NUM> and the UE <NUM> configured to initiate or define one or more of the components described herein and/or perform the functionality described herein, and to communicate with each other over a wireless and/or wired network.

Further, the base station <NUM> and/or the communication component <NUM> may execute a DL signal generator <NUM> configured to generate one or more single DCIs <NUM> that each schedule a respective set of the multiple CCs <NUM>. For example, each single DCI <NUM> may include a plurality of control information <NUM> (e.g., in <FIG>, Control Info CC1 up to Control Info CCn, wherein n is a positive integer), where the control information identifies the scheduled resources, e.g., one or more time/frequency resource blocks, for the UE <NUM> to monitor to receive a DL signal. The single DCI <NUM> may be triggered, for example, by a scheduler component <NUM> that receives data packets for delivery to the UE <NUM> and/or that generates control signaling identify, for example, reserved UL or DL resources, to configure the UE <NUM>. For instance, the DL signal generator <NUM> may additionally be configured to generate the DL signals <NUM>, <NUM>, such as one or more PDSCHs, to convey the data packets the UE <NUM>. Alternatively, or in addition, the generation of the single DCI <NUM> may be triggered by other events, such as but not limited to new radio resource configurations, and/or retransmission of DL signals such as may be indicated by re-transmission controller <NUM>. For instance, the re-transmission controller <NUM> may include an ACK/NACK manager component <NUM> that keeps track of the status of receipt of DL signals, as is explained below.

Also, the base station <NUM> and/or the communication component <NUM> may execute a DAI generator <NUM>, associated with the DAI indication component <NUM>, configured to generate the DAI information <NUM> to be included in each single DCI <NUM> that schedules multiple CCs <NUM>. In an implementation, the DAI generator <NUM> is configured to operate an indexer component <NUM> to update the C-DAI value <NUM> and/or the T-DAI value <NUM> according to the one or more DAI / codebook updating rules <NUM>, and provide such values to the DL signal generator <NUM> for including in the corresponding single DCI <NUM>.

Further, the base station <NUM> and/or the communication component <NUM> and/or the re-transmission controller <NUM> may execute a decoder/sorter component <NUM> on the received bundled feedback information <NUM> or PUCCH codebook to parse the data and identify the specific feedback indications. For instance, re-transmission controller <NUM> is configured to receive an UL signal including the bundled feedback information <NUM> or PUCCH codebook, such as on a PUCCH, and decode the bundled feedback information <NUM> based on the one or more DAI / codebook updating rules <NUM> in order to interpret HARQ ACKS/NACKS for specific DL signals, and thereby determine whether or not to call for a re-transmission of a DL signal. For instance, re-transmission controller <NUM> may execute the decoder/sorter component <NUM> to decode and parse the bundled feedback information <NUM> to identify the specific feedback values. The ACK/NACK manager component <NUM> may then keep track of the status of receipt of UL signals, for instance, using one or more HARQ processes <NUM>, which based on HARQ processing rules may be configured to generate a request for a re-transmission of a DL signal Alternatively, the information in the received UL signal(s) may be further processed by the communication component <NUM> and/or the base station <NUM>, for example, to clear a DL queue, or inform the scheduler component <NUM>.

Moreover, the base station <NUM> and/or the communication component <NUM> may execute a receiver component <NUM> to receive the communications described herein, and a transmitter component <NUM> to transmit the communications described herein. In an implementation, the receiver component <NUM> and the transmitter component <NUM> may be interfaces to/from the communications component <NUM> and/or they may be associated with a transmitter or receiver, respectively, or a transceiver.

Additionally, as noted above, the communication component <NUM> of the base station <NUM> as described herein may be implemented by at least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM> of <FIG>.

Correspondingly, the UE <NUM> operates the communication component <NUM> in communication with the base station <NUM>, executing the ACK/NACK feedback indication component <NUM> according to the one or more DAI / codebook updating rules <NUM>, to generate the bundled feedback information <NUM> based on the DAI information <NUM> from the DCI <NUM> and in response to receipt of the plurality of DL signals, e.g., DL signalCC1 <NUM> up to DL signalCCn <NUM>, on the multiple CCs <NUM>. The feedback may include, for example, an acknowledgement (ACK) or a negative acknowledgement (NACK) of each respective DL signal.

For example, in an implementation, the UE <NUM> and/or the communication component <NUM> and/or the ACK/NACK feedback indication component <NUM> may execute a DL signal processor <NUM> to receive and process the DCI <NUM> and the multiple DL signals <NUM>, <NUM>. Further, the DL signal processor <NUM> may execute a decoder/index identifier component <NUM> to attempt to parse the corresponding DAI information <NUM> from the DCI <NUM> and attempt to decode the received DL signals <NUM>, <NUM> and track a successful or unsuccessful decoding result based on the DAI information <NUM> and the one or more DAI / codebook updating rules <NUM>. The DL signal processor <NUM> may then communicate with a feedback generator component <NUM>, and in particular with one or more HARQ processes <NUM>, to track the status of the received DL signals <NUM>, <NUM>. The feedback generator <NUM> operates a feedback value determiner <NUM> in combination with a sorting component <NUM> to utilize the results of the processing by the DL signal processor <NUM> and HARQ processes <NUM>, in combination with the one or more DAI / codebook updating rules <NUM>, to determine an order and/or position of the specific feedback values <NUM> indicated in the bundled feedback information <NUM>. For example, each specific feedback value <NUM> may be indicated by a bit or bits, where one value indicates successful receipt and decoding, e.g., an ACK, whereas a different value indicates unsuccessful receipt and/or decoding, e.g., a NACK. For example, this particular formatting and/or positioning of the feedback enables the base station <NUM> to accurately identify and correlate the specific feedback contained in the bundled feedback information <NUM> for each of the plurality of transmitted DL signals <NUM>, <NUM> scheduled by the single DCI <NUM> on each of the multiple CCs <NUM>.

Further, in an implementation, the UE <NUM> and/or communication component <NUM> includes an UL signal generator <NUM> configured to generate one or more UL signals, including the bundled feedback information <NUM> as generated by the feedback generator <NUM>. The UL signal generator <NUM> may also generate other UL control and/or data signals, such as a PDSCH to carry data generated by the UE <NUM> for transmission to the base station <NUM> or another device directly or indirectly in communication with the UE <NUM> over a wired or wireless network. For instance, the UL signal generator <NUM> may receive data packets from one or more applications <NUM> executing on the UE <NUM>.

Moreover, the UE <NUM> and/or the communication component <NUM> may execute a receiver component <NUM> to receive the communications described herein, and a transmitter component <NUM> to transmit the communications described herein. In an implementation, the receiver component <NUM> and the transmitter component <NUM> may be interfaces to/from the communications component <NUM> and/or they may be associated with a transmitter or receiver, respectively, or a transceiver,.

Moreover, as noted above, the communication component <NUM> of the UE <NUM> as described herein may be implemented by at least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM> of <FIG>.

Referring to <FIG>, examples of signaling scenarios <NUM>, <NUM>, and <NUM>, respectively, represent cases where different variations in the DAI / codebook updating rules <NUM> are used, and all include updating at least one of the counter DAI or the total DAI in the DCI by a value that is incremented by at least <NUM> or by a number of the multiple component carriers scheduled by a previous DCI. In these examples, the base station <NUM> is indicated as gNB and the multiple component carriers are indicated as Cell <NUM> and Cell <NUM>.

For example, in scenario <NUM>, both of the counter DAI and the total DAI in the DCI have respective values that are incremented by a number of the at least two component carriers from a previous DCI. For instance, since DCI1 is the first DCI and it schedules both the first component carrier (CC1, or, Cell <NUM> as illustrated), the counter DAI is initially set with a value of <NUM> and the total DAI value is set to include the number of scheduled PDSCHs, e.g., <NUM> in this case. The subsequent DCI2 therefore increments the counter DAI by <NUM> based on the number of PDSCHs previously scheduled, and the total DAI value is incremented add the number of previously scheduled PDSCHs, e.g., PDSCH1 and PDSCH2, to the number of currently scheduled PDSCHs, e.g., PDSCH3 and PDSCH4, and thus is incremented from <NUM> to <NUM> in this case.

In the variation of scenario <NUM>, the counter DAI in each subsequent DCI is incremented by <NUM>, whereas the total DAI is incremented by the number of component carriers scheduled by the previous DCI.

Further, for example, in scenario <NUM>, both the counter DAI and the total DAI are incremented by at least <NUM> from a previous DCI. Specifically, in this variation, the total DAI is initially set at a value of <NUM> since the incrementing is only by <NUM> and not by the number of component carriers scheduled.

Referring to <FIG>, examples of signaling scenarios <NUM>, <NUM>, and <NUM>, respectively, represent cases where different variations in the DAI / codebook updating rules <NUM> are used, and all include using multiple values for one or both of the counter DAI and the total DAI, as well as updating at least one of the multiple values of the counter DAI or the total DAI in the DCI by a value that is incremented by at least <NUM> or by a number of the multiple component carriers scheduled by a previous DCI. In these examples, the base station <NUM> is indicated as gNB and the multiple component carriers are indicated as Cell <NUM> and Cell <NUM>.

In scenario <NUM>, the counter DAI includes a value for each of the at least two component carriers and the total DAI is incremented by a number of the at least two component carriers from a previous DCI. For example, for DC1, the counter DAI is initially set as (<NUM>,<NUM>) to correspond to scheduled PDSCH1 and PDSCH2, and the total DAI is set to <NUM> to correspond to the total number of PDSCHs scheduled Subsequent DCI2 has the counter DAI incremented to (<NUM>,<NUM>) to correspond to scheduled PDSCH3 and PDSCH4, respectively, and the total DAI is set to <NUM> to correspond to the total number of PDSCHs scheduled.

In the variation of scenario <NUM>, the DAI includes paired counter DAI and total DAI values for each of the multiple component carriers scheduled, where each counter DAI includes a value for each of the multiple component carriers and the total DAI includes a value for each of the multiple component carriers, wherein the paired counter DAI and total DAI values for a corresponding component carrier are each incremented by <NUM> when a subsequent DCI schedules a subsequent PDSCH for the corresponding component carrier.

Further, in scenario <NUM>, the counter DAI includes a value for a single component carrier of the multiple component carriers selected by a rule, and the total DAI is incremented by a number of the multiple component carriers scheduled, where the counter DAI value for one or more remaining ones of the multiple component carriers is implicitly indicated or determined based on the rule and the number of the multiple component carriers. For instance, in this example, the rule dictates that the component carrier having the highest index, e.g., component carrier <NUM> (or Cell <NUM>) in this case, receives the explicit DAI information. Based on this information and the number of component carriers scheduled, the UE <NUM> can determine the DAI information for the remaining component carriers, e.g., component carrier <NUM> (or Cell <NUM>) in this case, by further applying the portion of the rule that dictates that the counter DAI and the total DAI are each incremented by a number of the multiple component carriers scheduled.

Referring to <FIG>, examples of signaling scenarios <NUM> and <NUM>, respectively, represent cases where different variations in the DAI / codebook updating rules <NUM> are used, and each include multiple PDCCH monitoring occasions in which one or more DCIs may be transmitted by the base station <NUM> and received by the UE <NUM>. Correspondingly, these scenarios include updating at least one of the counter DAI or the total DAI in the DCI by a value that is incremented by a number of the multiple component carriers scheduled by a previous DCI. Further, these scenarios include transmitting the bundled feedback information <NUM> in the form of a physical uplink control channel (PUCCH) including a position for hybrid automatic repeat request (HARQ)-Acknowledgement (ACK) bits corresponding to the PDSCH for each of the multiple component carriers. In these examples, the base station <NUM> is indicated as gNB and the multiple component carriers are indicated as Cell <NUM> and Cell <NUM>.

In scenario <NUM>, a single DCI is received in each monitoring occasion, and the feedback is ordered based on the component carrier index per monitoring occasion. In other words, the UE <NUM> generates and transmits the PUCCH by sorting the HARQ-ACK bits corresponding to the PDSCH for each of the multiple component carriers first in ascending order of scheduled component carrier index within each PDCCH monitoring occasion, then in ascending order of PDCCH monitoring occasion index.

In scenario <NUM>, two DCIs are received in a first monitoring occasion, and a single DCI is received in a second monitoring occasion, but two of the scheduled PDSCHs are not received by the UE <NUM>. Specifically, PDSCH3 and PDSCH4 scheduled by DCI3 are not received by the UE <NUM>. In this case, to generate the bundled feedback information <NUM> or PUCCH codeword, the UE <NUM> sorts the HARQ-ACK bits corresponding to the PDSCHs for each of the multiple component carriers in ascending order of scheduled component carrier index, including sorting the HARQ-ACK bits in ascending order of a corresponding counter DAI value.

Referring to <FIG>, an example of a method <NUM> of wireless communication performed by the UE <NUM> may be used in a scenario where a single DCI schedules multiple component carriers. The UE <NUM> may perform method <NUM> by executing communication component <NUM> or one or more subcomponents thereof, and/or via execution of at least one of the TX processor <NUM>, the RX processor <NUM>, and/or the controller/processor <NUM>, as discussed above. Specifics of the actions or features of each portion of the method <NUM> are described above in detail.

At <NUM>, the method <NUM> includes receiving on a physical downlink control channel (PDCCH) during a first PDCCH monitoring occasion a first downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH) for each of at least two component carriers, wherein the DCI includes a counter downlink assignment index (DAI) that indicates a number of scheduled PDSCHs up to a point that the first DCI was received and a total DAI indicating a number of scheduled PDSCHs across the at least two component carriers. Alternatively, or more specifically, the C-DAI value indicates the accumulative number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release is present, up to the current serving cell and current PDCCH monitoring occasion. The T-DAI value, when present, indicates the total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release is present, up to the current PDCCH monitoring occasion and is updated from PDCCH monitoring occasion to the PDCCH monitoring occasion.

Alternatively or in addition, in some implementations, at least one of the counter DAI or the total DAI in the DCI has a value that is incremented by a number of the at least two component carriers from a previous DCI.

Alternatively or in addition, in some implementations, both of counter DAI and the total DAI in the DCI have respective values that are incremented by a number of the at least two component carriers from a previous DCI.

Alternatively or in addition, in some implementations, both the counter DAI and the total DAI are incremented by <NUM> from a previous DCI.

Alternatively or in addition, in some implementations, the counter DAI includes a value for each of the at least two component carriers and the total DAI is incremented by a number of the at least two component carriers from a previous DCI.

Alternatively or in addition, in some implementations, the counter DAI includes a value for each of the at least two component carriers and the total DAI includes a value for each of the at least two component carriers, wherein a DAI for a means for corresponding component carrier is incremented by <NUM> when the DCI schedules a PDSCH for the corresponding component carrier.

Alternatively or in addition, in some implementations, the counter DAI includes a value for a single component carrier of the at least two component carriers selected by a rule and the total DAI is incremented by a number of the at least two component carriers, further comprising means for determining a counter DAI value for another of the at least two component carriers based on the rule and the number of the at least two component carriers.

At <NUM>, the method <NUM> includes transmitting a physical uplink control channel (PUCCH) including a position for hybrid automatic repeat request (HARQ)-Acknowledgement (ACK) bits corresponding to the PDSCH for each of the at least two component carriers.

Optionally, at <NUM>, any of the preceding aspects of the method <NUM> may include receiving a second DCI in a second PDCCH monitoring occasion, wherein transmitting the PUCCH comprises sorting the HARQ-ACK bits corresponding to the PDSCH for each of the at least two component carriers first in ascending order of scheduled component carrier index within each PDCCH monitoring occasion, then in ascending order of PDCCH monitoring occasion index.

In this optional case, in some aspects, sorting the HARQ-ACK bits corresponding to the PDSCH for each of the at least two component carriers in ascending order of scheduled component carrier index comprises sorting the HARQ-ACK bits in ascending order of a corresponding counter DAI value.

<FIG> is a flowchart <NUM> of a method of wireless communication at the base station <NUM> may be used in a scenario where a single DCI schedules multiple component carriers. The base station <NUM> may perform the method <NUM> by executing communication component <NUM> or one or more subcomponents thereof, and/or via execution of at least one of the TX processor <NUM>, the RX processor <NUM>, and/or the controller/processor <NUM>, as discussed above. Specifics of the actions or features of each portion of the method <NUM> are described above in detail.

At <NUM>, the method <NUM> includes transmitting on a physical downlink control channel (PDCCH) during a first PDCCH monitoring occasion a first downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH) for each of at least two component carriers, wherein the DCI includes a counter downlink assignment index (DAI) that indicates a number of scheduled PDSCHs up to a point that the first DCI was received and a total DAI indicating a number of scheduled PDSCHs across the at least two component carriers. Alternatively, or more specifically, the C-DAI value indicates the accumulative number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH receptioti(s) or SPS PDSCH release is present, up to the current serving cell and current PDCCH monitoring occasion. The T-DAI value, when present, indicates the total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release is present, up to the current PDCCH monitoring occasion and is updated from PDCCH monitoring occasion to the PDCCH monitoring occasion.

At <NUM>, the method <NUM> includes receiving a physical uplink control channel (PUCCH) including a position for hybrid automatic repeat request (HARQ)-Acknowledgement (ACK) bits corresponding to the PDSCH for each of the at least two component carriers.

Alternatively or in addition, in some implementations, both the counter DAI and the total DAI are incremented by <NUM> from a previous DCI.

Alternatively or in addition, in some implementations, the counter DAI includes a value for a single component carrier of the at least two component carriers selected by a rule and the total DAI is incremented by a number of the at least two component carriers, further comprising means for determining a counter DAI value for another of the at least two component carriers based on the rule and the number of the at least two component carriers.

Optionally, at <NUM>, any of the preceding aspects of the method <NUM> may include transmitting a second DCI in a second PDCCH monitoring occasion, wherein receiving the PDCCH comprises sorting the HARQ-ACK bits corresponding to the PDSCH for each of the at least two component carriers first in ascending order of scheduled component carrier index within each PDCCH monitoring occasion, then in ascending order of PDCCH monitoring occasion index.

In this case, sorting the HARQ-ACK bits corresponding to the PDSCH for each of the at least two component carriers in ascending order of scheduled component carrier index comprises sorting the HARQ-ACK bits in ascending order of a corresponding counter DAI value.

The UE <NUM> and/or the base station <NUM> may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts. As such, each block in the aforementioned flowcharts may be performed by a component and the UE <NUM> and/or the base station <NUM> may include one or more of those components.

The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order of hierarchy presented.

Claim 1:
A method (<NUM>) of wireless communication at a user equipment, UE, (<NUM>), comprising:
receiving (<NUM>), from a base station, on a physical downlink control channel, PDCCH, during a first PDCCH monitoring occasion, a first downlink control information, DCI, that schedules a physical downlink shared channel, PDSCH, for each of at least two component carriers, wherein the first DCI includes a counter downlink assignment index, DAI, that indicates a number of scheduled PDSCHs across the at least two component carriers up to a point that the first DCI was received, and a total DAI indicating a number of scheduled PDSCHs across the at least two component carriers;
updating, with reference to rules configured in a codebook, bundled feedback information, based on the counter DAI and the total DAI in the received first DCI, and in response to receipt of the scheduled PDSCHs by the UE; and
transmitting (<NUM>), to the base station, the bundled feedback information included in a physical uplink control channel, PUCCH, wherein the bundled feedback information is configured to include a position for hybrid automatic repeat request, HARQ,-Acknowledgement, ACK, bits corresponding to the PDSCH for each of the at least two component carriers.