Patent Description:
Considerations on UL inter-UE prioritization and multiplexing summarizes agreements made at the RAN1 #98bis meeting, and provides further elements for discussion, including the proposal to configure, if a serving cell is configured with NUL and SUL, each UL carrier with a different positionInDCI.

RAN1 agreements for Rel-<NUM> URLLC lists RAN1 agreements made for the Rel-<NUM> WI on "physical Layer Enhancements for NR URLLC" until and including RAN1 #<NUM>. In particular a summary is made of the above proposal.

<CIT> discloses a method and apparatus for uplink transmission in a communication system. An operation method of a terminal includes: receiving, from a base station, first SFI information indicating a flexible symbol(s); receiving, from the base station, second SFI information re-indicating m symbol(s); and transmitting an SRS to the base station through the m symbol(s) re-indicated as a UL symbol(s) among the n flexible symbol(s) indicated as a flexible symbol(s). Therefore, performance of the communication system can be improved.

After a base station schedules resources for a UE to use in transmission or reception, e.g., of enhanced mobile broadband (eMBB) data, the base station may become aware of a more urgent, higher priority transmission from another UE. For example, the other transmission may be from a latency sensitive device utilizing ultra-reliable, low latency communication (URLLC). In such circumstances, the base station may reclaim the resources previously scheduled to the first, lower priority UE for use by the second, higher priority UE. In particular, if the previously scheduled resources are for a downlink transmission, the base station may send a downlink cancellation indication (DLCI) (or downlink preemption indication) in a DLCI occasion to the first UE cancelling at least a portion of the downlink transmission to that UE. Similarly, if the previously scheduled resources are for an uplink transmission, the base station may send an uplink cancellation indication (ULCI) (or uplink preemption indication) in an ULCI occasion to the first UE to cancel at least a portion of the uplink transmission from that UE. The base station may then allocate those reclaimed resources to the higher priority, latency sensitive UE.

Additionally, a UE may be configured with two uplink carriers in the same uplink serving cell, namely a supplementary uplink (SUL) carrier and a non-supplementary uplink (NUL) carrier, and the base station may semi-statically or dynamically schedule uplink transmissions on either the NUL or SUL. When the base station sends ULCI to the UE to cancel a previously scheduled uplink transmission, the UE may determine whether to apply the ULCI to cancel uplink transmissions on NUL or SUL. For example, the base station may configure the UE to monitor separate blocks or fields in ULCI, where each block corresponds to either the SUL carrier and/or NUL carrier of a given cell where the uplink transmission to be punctured is carried. The portion of the uplink transmission to be canceled is based on various parameters (e.g., carrier, time domain resource granularity, symbols, etc.) configured for the UE.

Currently, a UE may receive a NUL configuration for ULCI in a serving cell, including a corresponding location of fields in the DCI for NUL (e.g., a NUL position parameter), a number of bits for applying the ULCI to NUL (e.g., a NUL size parameter), and an indication for time-frequency resources of the ULCI in NUL. The UE may also receive a corresponding location of fields in the DCI for SUL (e.g., a SUL position parameter) for ULCI in the serving cell. However, under the current configuration, the UE is not configured with a corresponding SUL CI payload size parameter and SUL time-frequency resources for ULCI. Thus, a UE monitoring for a block in ULCI corresponding to SUL may not be able to determine the subset of SUL resources in which to apply ULCI, in contrast to NUL. It would therefore be desirable to enable a UE to determine the subset of SUL resources for applying ULCI. Aspects presented herein enable the UE to determine a SUL configuration, including the SUL CI payload size parameter and time-frequency resources, to determine the subset of resources for cancelling uplink communications in SUL.

The invention is defined in the independent claims, and preferable features are set out in the dependent claims.

The base stations <NUM> 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 backhaul links <NUM> (e.g., S1 interface). The base stations <NUM> configured for <NUM> NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network <NUM> through backhaul links <NUM>. The base stations <NUM> may communicate directly or indirectly (e.g., through the EPC <NUM> or core network <NUM>) with each other over backhaul links <NUM> (e.g., X2 interface).

The base stations <NUM> / UEs <NUM> may use spectrum up to YMHz (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction.

Referring again to <FIG>, in certain aspects, the UE <NUM> may include a SUL determination component <NUM> configured to receive, from a base station, a first configuration associated with a first block of an uplink cancellation indication (ULCI), where the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cell; determine a second configuration associated with a second block of the ULCI, where the second configuration is associated with the SUL carrier in the cell; and monitor the ULCI based on the first configuration and the second configuration.

Referring again to <FIG>, in certain aspects, the base station <NUM> may include a SUL configuration component <NUM> configured to transmit, to a user equipment (UE), a first configuration associated with a first block of an uplink cancellation indication (ULCI), where the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cell; and configure the UE with a second configuration associated with a second block of the ULCI, where the second configuration is associated with the SUL carrier in the cell.

The symbols on DL may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. For slot configuration <NUM>, different numerologies µ <NUM> to <NUM> allow for <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> slots, respectively, per subframe. <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>. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see <FIG>) that are frequency division multiplexed. Each BWP may have a particular numerology.

The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> CCEs), each CCE including six RE groups (REGs), each REG including <NUM> consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also referred to as SS block (SSB)).

The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK / negative ACK (NACK)) feedback.

In some aspects of wireless communications, after a base station schedules resources for a UE to use in transmission or reception, e.g., of enhanced mobile broadband (eMBB) data, the base station may become aware of a more urgent, higher priority transmission from another UE. For example, the other transmission may be from a latency sensitive device utilizing ultra-reliable, low latency communication (URLLC). In such circumstances, the base station may reclaim the resources previously scheduled to the first, lower priority UE for use by the second, higher priority UE. In particular, if the previously scheduled resources are for a downlink transmission, the base station may send a downlink cancellation indication (DLCI) (or downlink preemption indication) in a DLCI occasion to the first UE cancelling at least a portion of the downlink transmission to that UE. Similarly, if the previously scheduled resources are for an uplink transmission, the base station may send an uplink cancellation indication (ULCI) (or uplink preemption indication) in an ULCI occasion to the first UE to cancel at least a portion of the uplink transmission from that UE. The base station may then allocate those reclaimed resources to the higher priority, latency sensitive UE.

For example, <FIG> illustrates an example of a diagram <NUM> illustrating the allocation of resources for an uplink transmission <NUM> of a UE based on an uplink grant <NUM> received from a base station. If the base station later becomes aware of a latency sensitive UE which utilizes at least a portion <NUM> of the allocated resources for the uplink transmission <NUM> for URLLC data or other higher priority data, the base station may transmit a ULCI <NUM> in a ULCI occasion <NUM> to the UE indicating that the portion <NUM> of the previously granted resources for the uplink transmission will be punctured for use by the latency sensitive UE. As a result, the UE may cancel its uplink transmission during portion <NUM> for use by the other UE.

Additionally, a UE may be configured with two uplink carriers in the same uplink serving cell, namely a supplementary uplink (SUL) carrier and a non-supplementary uplink (NUL) carrier, and the base station may semi-statically or dynamically schedule uplink transmissions on either the NUL or the SUL. <FIG> illustrates an example serving cell <NUM> in which a base station <NUM> may communicate with a UE <NUM> over a NUL carrier <NUM> and a SUL carrier <NUM>. The NUL carrier <NUM> and SUL carrier <NUM> may be located on different frequencies; for example, the NUL carrier <NUM> may be located at a higher frequency than SUL carrier <NUM>. The NUL carrier <NUM> and the SUL carrier <NUM> may have different ranges, as illustrated in <FIG>. The base station <NUM> may send an uplink grant to the UE <NUM> to communicate on either the NUL or the SUL; the UE may not simultaneously transmit uplink communications on the NUL and the SUL. For example, in a serving cell, the UE may be dynamically or semi-statically indicated by the base station to transmit PUSCH, SRS, PUCCH, or other uplink communications on either the NUL or the SUL.

When the base station sends ULCI to the UE to cancel a previously scheduled uplink transmission, the UE may determine whether to apply the ULCI to cancel uplink transmissions on NUL or SUL. For example, the base station may configure the UE to monitor separate blocks or fields in ULCI, where each block corresponds to either the SUL carrier and/or NUL carrier of a given cell where the uplink transmission to be punctured is carried. Also, ULCI may comprise multiple blocks. The UE may be configured in the DCI with the length of ULCI and may be configured to monitor a block corresponding to the SUL carrier, a block corresponding to the NUL carrier, or a block corresponding together to the SUL and NUL carriers. The UE may apply ULCI (e.g., cancel at least a portion of the uplink transmission) on the corresponding carrier (e.g., SUL or NUL) indicated in each configured block.

<FIG> illustrates an example frame structure <NUM> of DCI comprising ULCI <NUM>. The ULCI comprises multiple blocks <NUM> that may be configured for a particular cell. Each block <NUM> may correspond to at least one bit associated with a time domain resource granularity (e.g., a number of symbols), where '<NUM>' may indicate not to cancel an uplink transmission and <NUM>' may indicate to cancel an uplink transmission (e.g., apply the ULCI), or vice-versa. The blocks <NUM> may be configured to indicate which carrier (SUL or NUL) and resources/symbols the portion of the uplink transmission are to be punctured or canceled. In one example as shown in <FIG>, the base station may configure UE with at least one block of the ULCI. In <FIG>, the UE may be configured to receive ULCI in block two <NUM> and block six <NUM> of the ULCI <NUM> structure, where block two <NUM> may be configured to correspond to NUL and block six <NUM> may be configured to correspond to SUL (or vice-versa). <FIG> merely illustrates a single example; any block of ULCI <NUM> may be configured (e.g., with <NUM>'s or <NUM>'s), and any of the blocks may be configured to correspond to a NUL carrier or a SUL carrier of a given cell. For example, the UE may apply ULCI to either the NUL carrier or SUL carrier based on which of blocks <NUM>, <NUM> the ULCI instruction to cancel the transmission was received. In another example, the UE may apply ULCI received in a single block to both the NUL carrier and the SUL carrier.

When the UE receives instructions to cancel an uplink transmission in blocks <NUM> and/or <NUM>, the UE may apply the ULCI to cancel at least a portion of the uplink transmission on the carrier(s) (SUL and/or NUL) and resources indicated in the blocks. The portion of the uplink transmission to be canceled is based on the various parameters (e.g., carrier, time domain resource granularity, symbols, etc.) configured for the UE. For instance, if the UE is configured based on the various parameters to receive ULCI for the NUL carrier in block <NUM> and for the SUL carrier in block <NUM>, the UE may cancel the transmission on the NUL carrier when the ULCI instructions are received in block <NUM>. The UE may cancel the transmission on the SUL carrier when the ULCI instructions are received in block <NUM>.

As indicated above, for each serving cell, the UE may be configured with various parameters for applying the ULCI. In one example, the UE may be configured with a corresponding location of fields in the DCI for NUL. For instance, this parameter may be a NUL position parameter (e.g., positioninDCI or another name) in DCI format 2_4. The UE may also be configured with a corresponding location of fields in the DCI for SUL. For instance, this parameter may be a SUL position parameter (e.g., positioninDCI-forSUL or another name). Thus, in the example of <FIG>, the NUL position parameter may correspond to block two <NUM>, while the SUL position parameter may correspond to block six <NUM>. In another example, the UE may be configured with a number of bits for applying the ULCI. For instance, this parameter may be a NUL size parameter (e.g., Cl-PayloadSize or another name). Referring to <FIG>, for example, the NUL size parameter of block two <NUM> may be nine bits (or another number). In a further example, the UE may be configured with an indication for time-frequency resources of the ULCI. For instance, this parameter may be a NUL indication of time and frequency domain resources (e.g., timeFrequencyRegion or another name). The NUL indication may include, for example, a set of frequency domain resources on the serving cell, a number of consecutive symbols (excluding symbols for reception of SS/PBCH blocks and DL symbols indicated by a timedivision-duplex configuration [e.g., tdd-UL-DL-ConfigurationCommon or another name]), and a time domain granularity of each bit in the field (e.g., timeGranularityforCl or another name). Referring to <FIG> and assuming an NUL size parameter of nine bits in this example, the NUL indication may indicate for example that block two <NUM> has a NUL time domain granularity of three bits, a NUL duration in time of three symbols, and a NUL duration in frequency of three subcarriers. In some aspects, an uplink cancelation priority field or parameter (e.g., uplinkCancellationPriority or another name) may configure uplink cancelation behavior if both ULCI and intra-UE priority indicators are configured for a given UE. If the field or parameter is present, then ULCI may be applicable to the UL transmissions indicated/configured as a low priority level. If the field or parameter is absent, ULCI may be applicable to an UL transmission irrespective of its priority level. In some instances, this parameter may be configured for the NUL. That is, a separate parameter (e.g., uplinkCancellationPriority-For-SUL or another name) may be configured for the SUL to indicate the uplink cancelation priority on the SUL. If this parameter is not configured for the SUL, the UE may follow the same behavior as the NUL (i.e., based on the existing RRC parameter uplinkCancellationPriority).

Based on the above, a UE may receive the NUL configuration (e.g., the NUL position, size, and time-frequency resources) for ULCI in a serving cell, and the SUL position for ULCI in the serving cell. For instance, a UE configured with the aforementioned example parameters may monitor for block two <NUM> and, when block two <NUM> is received, may apply ULCI across a subset of NUL resources spanning a number of symbols, e.g., three symbols, and a number of subcarriers, e.g., three subcarriers, in the serving cell. However, under the current configuration, the UE may not be configured with the cancellation indication (CI) payload size for SUL (e.g., field bit width) and SUL time-frequency resources. Thus, a UE monitoring for block six <NUM>, for example, may not be able to determine which subset of SUL resources to apply ULCI when block six <NUM> is received, in contrast to NUL. The UE may also not be able to determine how many bits are contained in the block in the ULCI corresponding to SUL. It would therefore be desirable to enable a UE to determine the subset of SUL resources for applying ULCI.

Aspects presented herein enable a UE to determine a SUL configuration, including the SUL CI payload size parameter and time-frequency resources, to determine the subset of resources for cancelling uplink communications in SUL. For example, if a UE is configured with and receives the SUL position parameter described above from a base station, the UE may apply one or more of the various aspects described infra to determine the SUL configuration for ULCI. Otherwise, if the UE is not configured with the SUL position parameter, the UE may refrain from determining the SUL configuration and monitoring ULCI for the SUL.

The UE may determine the SUL configuration according to various aspects. In a first aspect, the base station may configure a separate time/frequency region and a number of bits for the SUL in a separate configuration from those of the NUL. For example, the base station may provide to the UE a SUL CI payload size parameter (e.g., Cl-PayloadSize-forSUL or another name) and a SUL indication of time-frequency resources (e.g., timefrequencyRegion-forSUL or another name) as additional RRC parameters for SUL configuration. Thus, referring to <FIG>, the UE may determine the SUL CI payload size parameter corresponding to block six <NUM> from an RRC parameter received from the base station, in addition to the NUL size parameter corresponding to block two <NUM> received from the base station. Similarly, the UE may determine the SUL time-frequency resources corresponding to block six <NUM> from one or more RRC parameters received from the base station in addition to the RRC parameters corresponding to the NUL (e.g., block two <NUM>).

In this first aspect, the additional RRC parameters for the SUL configuration may be configured under the same parent RRC parameter (e.g., ci-ConfigurationPerServingCell or another name) for NUL configuration. For example, the NUL configuration parameters (e.g., the NUL position, size, and time-frequency resources) and SUL configuration parameters (e.g., the SUL position as well as SUL CI payload size and time-frequency resources) may be provided to the UE under a common, parent RRC parameter.

In a second aspect, the UE may not receive additional RRC parameters from the base station for SUL. Instead, the UE may determine the SUL configuration parameters based at least in part on the NUL configuration parameters. In one example, the SUL and NUL may share the same number of bits. For instance, the fields of NUL and SUL in the ULCI may be configured to have the same bit-width, which both may follow from the existing NUL size parameter (e.g., Cl-PayloadSize or another name). Thus, referring to <FIG>, the UE may determine that the SUL CI payload size parameter (e.g., number of bits) corresponding to block six <NUM> is the same as the NUL size parameter configured for block two <NUM>.

In another example, the frequency domain resources covered by ULCI for SUL may be configured to correspond to the whole, active uplink bandwidth part (BWP) configured for the UE in SUL. Alternatively, the frequency domain resources for SUL may be configured to correspond to the entire SUL bandwidth. Thus, referring to <FIG>, the UE may determine that the set of frequency domain resources associated with block six <NUM> for SUL corresponds to a configured BWP (e.g., the active BWP) for SUL, or the configured SUL bandwidth. In contrast, the frequency domain resources configured for NUL (e.g., as provided by the parameter timeFrequencyRegion or another name) may not be used for SUL, as NUL and SUL occupy different frequencies.

In a further example, the time domain resources covered by the SUL may be configured to have a duration equal in time to that of the NUL. Thus, referring to <FIG>, the UE may determine that the SUL time domain resources configured for block six <NUM> have a duration equal to that of the NUL time domain resources configured for block two <NUM>. Additionally, the UE may determine the SUL time domain resources based on the UE's monitoring periodicity of ULCI. For example, when the UE's monitoring periodicity of ULCI is greater than or equal to one slot (e.g., the UE monitors for ULCI in SUL every one or more slots), the duration of the SUL time domain resources may be equal to the monitoring periodicity. Thus, in the example of <FIG>, if the UE monitors for block six <NUM> every two slots, the duration of the SUL time domain resources may be configured to also be two slots. However, when the UE's monitoring periodicity of ULCI is less than one slot, a number of symbols configured for the ULCI (e.g., as provided by the parameter timeFrequencyRegion or another name) may apply both to NUL and SUL when NUL and SUL overlap in time. For instance, in the example of <FIG>, if the UE monitors for block six <NUM> every five symbols, the duration of the SUL time domain resources (and NUL time domain resources) may configured to also be five symbols. The number of symbols may be based on (e.g., in a unit of) the subcarrier spacing (SCS) for downlink transmissions.

In an additional example, the same time domain granularity may apply to both the SUL and the NUL. For instance, the SUL time domain granularity may be configured to be the same as the configured NUL time domain granularity (e.g., timeGranularityforCl or another name). Thus, referring to <FIG>, the UE may determine that the SUL time domain granularity associated with block six <NUM> is the same as the NUL time domain granularity associated with block two <NUM>.

In a third aspect, the UE may determine the SUL configuration parameters based on whether or not additional RRC parameters are received from the base station for ULCI in SUL. For example, if each of the SUL CI payload size parameter (e.g., Cl-PayloadSize-forSUL or another name) and SUL indication of time-frequency resources (e.g., timeFrequencyRegion-forSUL or another name) are configured by the base station and received by the UE, then the UE may determine the SUL configuration parameters from the received RRC parameters as described above (with respect to the first aspect). Otherwise, if the UE does not receive certain RRC parameters, the UE may determine the corresponding SUL configuration parameters from the NUL configuration parameters as described above (with respect to the second aspect). The RRC parameters may include, for example, the frequency domain resources, the number of bits, the total time duration, the time domain granularity, and/or an uplink cancelation priority.

<FIG> illustrates an example call flow diagram <NUM> between a UE <NUM> and a base station <NUM>. At block <NUM>, the base station may configure the rules for the UE to determine the SUL configuration parameters for ULCI, in accordance with the third aspect described above with respect to <FIG>. For example, the base station may configure the UE to determine the SUL configuration from separate RRC parameters configured for the SUL carrier and transmitted to the UE, in accordance with the first aspect described above with respect to <FIG>. Alternatively, the base station may configure the UE to determine the SUL configuration parameters based on the NUL configuration parameters, without configuring separate RRC parameters for ULCI in SUL, in accordance with the second aspect described above with respect to <FIG>. After configuring these rules, the base station may transmit the configuration rules <NUM> for the UE to determine the SUL configuration. Alternatively, the UE may be preconfigured with these rules.

At block <NUM>, the base station may configure NUL configuration parameters associated with a block of ULCI. For example, the base station may configure the UE with a corresponding location of fields in the DCI for NUL (e.g., a NUL position parameter), a number of bits for applying the ULCI (e.g., a NUL size parameter), and an indication for time-frequency resources of the ULCI (e.g., a NUL indication of time and frequency domain resources), including a set of frequency domain resources on the serving cell, a number of consecutive symbols, and a time domain granularity of each bit in the field. The base station may then transmit to the UE <NUM> the NUL configuration parameters <NUM>.

At block <NUM>, the base station may configure SUL configuration parameters associated with another block of ULCI. For example, the base station may configure a separate time/frequency region (e.g., a SUL indication of time-frequency resources) and a number of bits for the SUL (e.g., a SUL CI payload size parameter) as additional RRC parameters separate from those of the NUL. The base station may transmit the SUL configuration <NUM> including the additional RRC parameters to the UE <NUM>.

Alternatively, the base station may not configure additional RRC parameters for SUL. Instead, at block <NUM>, the base station may configure one or more SUL configuration parameters based on the NUL configuration parameters. In one example, the fields of NUL and SUL in the ULCI may be configured to have the same bit width. In another example, the frequency domain resources covered by ULCI for SUL may be configured to correspond to the whole, active uplink bandwidth part (BWP) configured for the UE in SUL, or to correspond to the entire SUL bandwidth. In a further example, the time domain resources covered by the SUL may be configured to have a duration equal in time to that of the NUL. In an additional example, the SUL time domain granularity may be configured to be the same as the configured NUL time domain granularity.

At block <NUM>, after the UE <NUM> receives the NUL configuration <NUM> associated with one block of the ULCI, the UE may determine the SUL configuration associated with another block of the ULCI. At block <NUM>, the UE may monitor the ULCI based on the NUL configuration <NUM> and the SUL configuration. The UE <NUM> may determine the SUL configuration based on the configuration rules <NUM> (e.g., preconfigured or provided by the base station <NUM>) in accordance with either the first aspect or the second aspect described above. For example, if the UE receives SUL configuration <NUM> including additional RRC parameters associated with SUL, the UE may monitor for and apply ULCI to SUL based on those separate RRC parameters (e.g., the SUL indication of time-frequency resources and the SUL CI payload size parameter). Alternatively, if the UE does not receive SUL configuration <NUM>, or does not receive some parameters in SUL configuration <NUM>, the UE may monitor for and apply ULCI to SUL based on the corresponding parameters in the NUL configuration <NUM>. For example, the UE may determine that the SUL CI payload size parameter is the same as the NUL size parameter, determine that the set of frequency domain resources corresponds to a configured BWP for SUL or the configured SUL bandwidth, determine that the SUL time domain resources have a duration equal to that of the NUL time domain resources, or determine that the SUL time domain granularity is the same as the NUL time domain granularity.

<FIG> is a flowchart <NUM> of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., the UE <NUM>, <NUM>, <NUM>, <NUM>; the apparatus <NUM>). Optional aspects are illustrated in dashed lines. The method allows a UE to determine a SUL configuration to determine the subset of resources for cancelling uplink communications in SUL. The methods described herein can provide a number of benefits, such as improving communication signaling, resource utilization, and/or power savings.

At <NUM>, the UE receives, from a base station, a first configuration associated with a first block of an ULCI, where the first configuration is associated with at least one of a SUL carrier or a NUL carrier in a cell. For example, referring to <FIG>, the UE <NUM> may receive the NUL configuration <NUM> associated with one block of the ULCI. Further, <NUM> may be performed by <NUM> in <FIG>.

At <NUM>, the UE determines a second configuration associated with a second block of the ULCI, where the second configuration is associated with a SUL carrier in the cell. For example, referring to <FIG>, at block <NUM>, after the UE <NUM> receives the NUL configuration <NUM> associated with one block of the ULCI, the UE may determine the SUL configuration associated with another block of the ULCI. Further, <NUM> may be performed by <NUM> in <FIG>.

In the first aspect, the second configuration may be determined from RRC parameters received from the base station and associated with the SUL carrier. The first configuration may include a NUL size parameter indicating a first number of bits associated with the first block, and a NUL indication of time-frequency resources associated with the first block. The second configuration may include a SUL CI payload size parameter indicating a second number of bits associated with the second block, and a SUL indication of time-frequency resources associated with the second block. The SUL CI payload size parameter and the SUL indication may be separate RRC parameters from the NUL size parameter and the NUL indication. The first configuration and the second configuration may be configured under a same (parent) RRC parameter.

In the second aspect, and according to the invention, the second configuration is determined based on the first configuration received from the base station. In one example, the first configuration may include a NUL size parameter indicating a first number of bits associated with the first block, the second configuration may include a SUL CI payload size parameter indicating a second number of bits associated with the second block, and the SUL CI payload size parameter may be the same as the NUL size parameter. In another example, the second configuration may include a set of SUL frequency resources, and the SUL frequency resources may include one of a BWP on the SUL or a bandwidth of the SUL. In a further example, the first configuration may include a first indication of NUL time domain resources associated with the first block, the second configuration may include a second indication of SUL time domain resources associated with the second block, and a NUL duration of the NUL time domain resources may be the same as a SUL duration of the SUL time domain resources. The SUL duration may be equal to a ULCI monitoring periodicity of the UE when the ULCI monitoring periodicity is at least one slot, and the SUL duration may be equal to a configured number of symbols when the ULCI monitoring periodicity is less than one slot. In an additional example, the first configuration may include a NUL time domain granularity associated with the first block, the second configuration may include a SUL time domain granularity associated with the second block, and the NUL time domain granularity may be the same as the SUL time domain granularity. In another example, the first configuration may include a first indication of uplink cancelation priority on the NUL associated with the first block, the second configuration may include a second indication of uplink cancelation priority on the SUL associated with the second block, and the uplink cancelation priority on the NUL may be the same as the uplink cancelation priority on the SUL.

In the third aspect, the second configuration may be determined from RRC parameters associated with the SUL carrier when the RRC parameters are configured by the base station, and the second configuration may be determined based on the first configuration when the RRC parameters are not configured. The RRC parameters associated with the SUL carrier may comprise at least one of a set of frequency domain resources, a number of bits, a total duration of time domain resources, or a time domain granularity.

At <NUM>, the UE monitors the ULCI based on the first configuration and the second configuration. The ULCI may be monitored based on the second configuration based on a radio resource control (RRC) parameter received from the base station. For example, referring to <FIG>, at block <NUM>, the UE may monitor the ULCI based on the NUL configuration <NUM> and the SUL configuration. For example, referring to the example of <FIG>, a UE may monitor for block two <NUM> based on the NUL position parameter received in NUL configuration <NUM>, and, when block two <NUM> is received, apply ULCI across a subset of NUL resources based on the other NUL configuration parameters. Similarly, a UE may monitor for block six <NUM> based on the SUL position parameter received in SUL configuration <NUM>, and when block six <NUM> is received, apply ULCI across a subset of SUL resources based on the determined SUL configuration parameters. Alternatively, if the UE does not receive the SUL position parameter, the UE may refrain from determining the SUL parameters and monitoring the ULCI for SUL. Further, <NUM> may be performed by <NUM> in <FIG>.

<FIG> is a flowchart <NUM> of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., the base station <NUM>/<NUM>, <NUM>, <NUM>, <NUM>; the apparatus <NUM>). Optional aspects are illustrated in dashed lines. The method allows a base station to configure a UE to determine a SUL configuration to determine the subset of resources for cancelling uplink communications in SUL. The methods described herein can provide a number of benefits, such as improving communication signaling, resource utilization, and/or power savings.

At <NUM>, the base station transmits, to the UE, a first configuration associated with a first block of an ULCI, where the first configuration is associated with at least one of a SUL carrier or a NUL carrier in a cell. For example, referring to <FIG>, the base station <NUM> may transmit the NUL configuration <NUM> associated with one block of the ULCI to the UE <NUM>. Further, <NUM> may be performed by <NUM> in <FIG>.

At <NUM>, the base station configures the UE with a second configuration associated with a second block of the ULCI, where the second configuration is associated with a SUL carrier in the cell. For example, referring to <FIG>, at block <NUM>, the base station configures SUL configuration parameters associated with another block of ULCI. Further, <NUM> may be performed by <NUM> in <FIG>.

In the first aspect, the second configuration includes RRC transmitted to the UE and associated with the SUL carrier. The first configuration may include a NUL size parameter indicating a first number of bits associated with the first block, and a NUL indication of time-frequency resources associated with the first block. The second configuration may include a SUL CI payload size parameter indicating a second number of bits associated with the second block, and a SUL indication of time-frequency resources associated with the second block. The SUL CI payload size parameter and the SUL indication may be separate RRC parameters from the NUL size parameter and the NUL indication. The first configuration and the second configuration may be configured under a same (parent) RRC parameter.

In the second aspect, and according to the invention, the second configuration is configured based on the first configuration transmitted to the UE. In one example, the first configuration may include a NUL size parameter indicating a first number of bits associated with the first block, the second configuration may include a SUL CI payload size parameter indicating a second number of bits associated with the second block, and the SUL CI payload size parameter may be the same as the NUL size parameter. In another example, the second configuration may include a set of SUL frequency resources, and the SUL frequency resources may include one of a BWP on the SUL or a bandwidth of the SUL. In a further example, the first configuration may include a first indication of NUL time domain resources associated with the first block, the second configuration may include a second indication of SUL time domain resources associated with the second block, and a NUL duration of the NUL time domain resources may be the same as a SUL duration of the SUL time domain resources. The SUL duration may be equal to a ULCI monitoring periodicity of the UE when the ULCI monitoring periodicity is at least one slot, and the SUL duration may be equal to a configured number of symbols when the ULCI monitoring periodicity is less than one slot. In an additional example, the first configuration may include a NUL time domain granularity associated with the first block, the second configuration may include a SUL time domain granularity associated with the second block, and the NUL time domain granularity may be the same as the SUL time domain granularity. In another example, the first configuration may include a first indication of uplink cancelation priority on the NUL associated with the first block, the second configuration may include a second indication of uplink cancelation priority on the SUL associated with the second block, and the uplink cancelation priority on the NUL may be the same as the uplink cancelation priority on the SUL.

In the third aspect, at <NUM>, the base station may configure the UE to determine the second configuration from RRC parameters associated with the SUL carrier when the RRC parameters are configured by the base station. At <NUM>, the base station may configure the UE to determine the second configuration based on the first configuration when the RRC parameters are not configured. The RRC parameters associated with the SUL carrier may comprise at least one of a set of frequency domain resources, a number of bits, a total duration of time domain resources, or a time domain granularity. For example, referring to <FIG>, at block <NUM>, the base station may configure the rules for the UE to determine the SUL configuration parameters for ULCI. After configuring these rules, the base station may transmit the configuration rules <NUM> for the UE to determine the SUL configuration. Alternatively, the UE may be preconfigured with these rules. Further, <NUM> may be performed by <NUM> in <FIG>. <NUM> may also be performed by <NUM> in <FIG>.

The communication manager <NUM> includes a determination component <NUM> that is configured to receive, from a base station, a first configuration associated with a first block of an uplink cancellation indication (ULCI), where the first configuration is associated with at least one of a supplementary uplink (SUL) or a non-supplementary uplink (NUL) carrier in a cell, e.g., as described in connection with <NUM> in <FIG>. Determination component <NUM> is also configured to determine a second configuration associated with a second block of the ULCI, where the second configuration is associated with the SUL carrier in the cell, e.g., as described in connection with <NUM> in <FIG>. Determination component <NUM> is also configured to monitor the ULCI based on the first configuration and the second configuration, e.g., as described in connection with <NUM> in <FIG>.

In one configuration, the apparatus <NUM>, and in particular the cellular baseband processor <NUM>, includes means for receiving, from a base station, a first configuration associated with a first block of an uplink cancellation indication (ULCI), where the first configuration is associated with at least one of a supplementary uplink (SUL) or a non-supplementary uplink (NUL) carrier in a cell; means for determining a second configuration associated with a second block of the ULCI, where the second configuration is associated with the SUL carrier in the cell; and means for monitoring the ULCI based on the first configuration and the second configuration. The aforementioned means may be one or more of the aforementioned components of the apparatus <NUM> configured to perform the functions recited by the aforementioned means. As described supra, the apparatus <NUM> may include the TX Processor <NUM>, the RX Processor <NUM>, and the controller/processor <NUM>.

The apparatus <NUM> is a base station (BS) and includes a baseband unit <NUM>. The baseband unit <NUM> may communicate through a cellular RF transceiver <NUM> with the UE <NUM>. The baseband unit <NUM> may include a computer-readable medium / memory. The baseband unit <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the baseband unit <NUM>, causes the baseband unit <NUM> to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the baseband unit <NUM> when executing software. The baseband unit <NUM> further includes a reception component <NUM>, a communication manager <NUM>, and a transmission component <NUM>. The components within the communication manager <NUM> may be stored in the computer-readable medium / memory and/or configured as hardware within the baseband unit <NUM>. The baseband unit <NUM> may be a component of the BS <NUM> and may include the memory <NUM> and/or at least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM>.

The communication manager <NUM> includes a determination component <NUM> that is configured to transmit, to a user equipment (UE), a first configuration associated with a first block of an uplink cancellation indication (ULCI), where the first configuration is associated with at least one of a supplementary uplink (SUL) or a non-supplementary uplink (NUL) carrier in a cell, e.g., as described in connection with as described in connection with <NUM> in <FIG>. Determination component <NUM> is also configured to configure the UE with a second configuration associated with a second block of the ULCI, where the second configuration is associated with the SUL carrier in the cell, e.g., as described in connection with <NUM> in <FIG>. Determination component <NUM> is also configured to configure the UE to determine the second configuration from radio resource control (RRC) parameters associated with the SUL carrier when the RRC parameters are configured by the base station, e.g., as described in connection with <NUM> in <FIG>. Determination component <NUM> is also configured to configure the UE to determine the second configuration based on the first configuration when the RRC parameters are not configured, e.g., as described in connection with <NUM> in <FIG>.

In one configuration, the apparatus <NUM>, and in particular the baseband unit <NUM>, includes means for transmitting, to a user equipment (UE), a first configuration associated with a first block of an uplink cancellation indication (ULCI), where the first configuration is associated with at least one of a supplementary uplink (SUL) or a non-supplementary uplink (NUL) carrier in a cell; means for configuring the UE with a second configuration associated with a second block of the ULCI, where the second configuration is associated with the SUL carrier in the cell; means for configuring the UE to determine the second configuration from radio resource control (RRC) parameters associated with the SUL carrier when the RRC parameters are configured by the base station; and means for configuring the UE to determine the second configuration based on the first configuration when the RRC parameters are not configured. The aforementioned means may be one or more of the aforementioned components of the apparatus <NUM> configured to perform the functions recited by the aforementioned means. As described supra, the apparatus <NUM> may include the TX Processor <NUM>, the RX Processor <NUM>, and the controller/processor <NUM>.

Claim 1:
A method (<NUM>) of wireless communication of a user equipment, UE, (<NUM>) comprising:
receiving (<NUM>), from a base station (<NUM>), a first configuration associated with a first block (<NUM>) of an uplink cancellation indication, ULCI,, wherein the first configuration is associated with at least one of a supplementary uplink, SUL, carrier or a non-supplementary uplink, NUL, carrier in a cell;
determining (<NUM>) a second configuration associated with a second block (<NUM>) of the ULCI, wherein the second configuration is associated with the SUL carrier in the cell and is determined based on the first configuration received from the base station; and
monitoring (<NUM>) the ULCI based on the first configuration and the second configuration.