Patent Description:
NR (e.g., <NUM> NR) is an example of an emerging telecommunication standard.

<NPL>, discloses that gNB can send an indication to eMBB UEs to suspend transmissions during the scheduled URLLC PUSCH. This is referred to as upöink preemption inidcation (ULPI). Unlike downlink preemption indication that can take place after the completion of eMBB transmissions, the ULPI should be sent before the scheduled URLLC PUSCH to allow eMBB UEs to take actions.

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for uplink preemption indication (ULPI). Aspects provide ULPI with a power dimension indication. Aspects provide ULPI that indicates preemption for resources over duration longer than a ULPI monitoring periodicity, for ULPIs indicating overlapping resources, and for handling conflicting ULPIs. It is understood by a skilled reader that the features defined by the independent claims are not optional, even though the detailed description may disclose some such features using optional language (e.g., "may").

The following description provides examples of ULPI, and is not limiting of the scope, applicability, or examples set forth in the claims.

The techniques described herein may be used for various wireless networks and radio technologies. While aspects may be described herein using terminology commonly associated with <NUM>, <NUM>, and/or <NUM> wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, including later technologies.

A RAT may also be referred to as a radio technology, an air interface, etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.

New radio access (e.g., <NUM> NR) may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., <NUM> or beyond), millimeter wave (mmW) targeting high carrier frequency (e.g., <NUM> or beyond), massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC).

NR may utilize orthogonal frequency division multiplexing (OFDM) on the downlink and/or downlink, and/or may utilize single-carrier frequency division multiplexing (SC-FDM) on the uplink. NR may utilize a cyclic prefix (CP). OFDM and SC-FDM partition the system bandwidth into multiple orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. NR may support a base spacing of the subcarriers of <NUM> and other subcarrier spacing (SCS) may be defined with respect to the base SCS (e.g., <NUM>, <NUM>, <NUM>, <NUM>, etc). The minimum resource allocation (e.g., a resource block (RB)) may be <NUM> consecutive subcarriers. In NR, a subframe is <NUM>, but the basic TTI is referred to as a slot. slots) depending on the SCS. The symbol, slot, and CP lengths scale with the SCS.

As shown in <FIG>, the wireless communication network <NUM> may be in communication with a core network <NUM>. The core network <NUM> may in communication with one or more base station (BSs) <NUM> and/or user equipment (UE) <NUM> in the wireless communication network <NUM> via one or more interfaces.

As illustrated in <FIG>, the wireless communication network <NUM> may include a number of BSs 110a-z (each also individually referred to herein as BS <NUM> or collectively as BSs <NUM>) and other network entities. A BS <NUM> may be provide communication coverage for a particular geographic area, sometimes referred to as a cell, which may be stationary or may move according to the location of a mobile BS <NUM>. BSs <NUM> may be interconnected to one another and/or to one or more other BSs <NUM> or network nodes (not shown) in wireless communication network <NUM> through various types of backhaul interfaces (e.g., a direct physical connection, a wireless connection, a virtual network, or the like) using any suitable transport network.

The BSs <NUM> communicate with UEs 120a-y (each also individually referred to herein as UE <NUM> or collectively as UEs <NUM>) in the wireless communication network <NUM>. Each UE may be stationary or mobile. Wireless communication network <NUM> may also include relay stations (e.g., relay station 110r), also referred to as relays or the like, that receive a transmission of data and/or other information from an upstream station (e.g., a BS 110a or a UE 120r) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE <NUM> or a BS <NUM>), or that relays transmissions between UEs <NUM> to facilitate communication between devices.

According to certain aspects, the BSs <NUM> and UEs <NUM> may be configured for uplink preemption. The wireless communication network <NUM> may be a <NUM> NR network. As shown in <FIG>, the BS 110a includes a ULPI manager <NUM> and the UE 120a includes a ULPI manager <NUM>. The ULPI manager <NUM> may be configured to send, and the ULPI manager <NUM> to receive, at least one ULPI. The ULPI indicates, for each of a plurality of sets of uplink resources, a power level the UE 120a can use for one or more uplink transmissions, such as eMBB. The ULPI manager <NUM> may be configured to send or drop, and the ULPI manager <NUM> to monitor or not monitor, the one or more uplink transmissions according to the ULPI.

<FIG> illustrates example components of BS 110a and UE 120a (as depicted in <FIG>), which may be used to implement aspects of the present disclosure.

At the BS 110a, a transmit processor <NUM> may receive data from a data source <NUM> and control information from a controller/processor <NUM>. The processor <NUM> may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), and channel state information reference signal (CSI-RS). A transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 232a through 232t. Downlink signals from modulators 232a through 232t may be transmitted via the antennas 234a through 234t, respectively.

At the UE 120a, the antennas 252a through 252r may receive the downlink signals from the BS 110a and may provide received signals to the demodulators (DEMODs) in transceivers 254a through 254r, respectively. A MIMO detector <NUM> may obtain received symbols from all the demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120a to a data sink <NUM>, and provide decoded control information to a controller/processor <NUM>.

On the uplink, at UE 120a, a transmit processor <NUM> may receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source <NUM> and control information (e.g., for the physical uplink control channel (PUCCH) from the controller/processor <NUM>. The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the modulators in transceivers 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At the BS 110a, the uplink signals from the UE 120a may be received by the antennas <NUM>, processed by the modulators <NUM>, detected by a MIMO detector <NUM> if applicable, and further processed by a receive processor <NUM> to obtain decoded data and control information sent by the UE 120a.

Antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE 120a and/or antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the BS 110a and/or other modules may be used to perform the various techniques and methods described herein for the ULPI. As shown in <FIG>, the controller/processor <NUM> has an ULPI manager <NUM> and the controller/processor <NUM> has an ULPI manager <NUM>.

Aspects of the disclosure relate generally to uplink preemption. As mentioned above, <NUM> NR can support services with different and/or varying reliability and latency requirements (e. g, such as eMBB and URLLC). The ULPI features discussed herein can help bring about such features. ULPI may also be referred to as an uplink cancellation indication (or ULCI).

In some cases, the network (e.g., the BS 110a) multiplexes users (e.g., UEs <NUM>) with different services (e.g., eMBB and URLLC) in the same time-frequency resources, such as to improve efficiency (e.g., better spectrum utilization). URLLC, having stricter latency targets, may be more urgent and may, therefore, be scheduled over resources allocated to eMBB.

The BS can transmit a downlink preemption indication (DLPI) to the UEs to indicate that downlink resources allocated for one service (e.g., eMBB) are preempted for transmissions for another service (e.g., URLLC). For example, the BS may signal a DLPI to a UE, scheduled to receive an eMBB transmission, to indicate that the downlink resources for the eMBB transmission are reallocated for a URLLC transmission, by that UE or a different UE.

In order to improve URLLC services, the BS may signal to a UE to suspend ongoing uplink transmissions of a first service (e.g., eMBB) when a second service (e.g., URLLC) transmissions are scheduled. This preemption of resources may help to reduce interference with the URLLC transmissions, for example, to help achieve the strict reliability targets for URLLC. For example, the BS may transmit an indication to a UE, scheduled to send an eMBB transmission, that the uplink resources for the eMBB transmission are reallocated for a URLLC transmission by a different UE. That is, the eMBB UE is indicated to preempt (e.g., cancel or drop) its uplink transmission on the corresponding resources indicated as "preempt" in the indication. This may be referred to as an uplink preemption indication (ULPI) or uplink cancellation indication.

<FIG> is an example ULPI. An ULPI may indicate preemption for a set of resources. In the example shown in <FIG>, time and frequency resources are divided into <NUM> parts, <NUM> parts in frequency and <NUM> parts in time. In this example, <NUM> bits can be used to indicate whether a corresponding frequency-time part is pre-empted or not (e.g., <NUM> may indicate not preempted and a <NUM> may indicate preempted). The numbers of bits and the granualarity if the resources indicated by each bit may vary. In the example shown in <FIG>, the total time-domain resources indicated by the ULPI is equal to the ULPI monitoring periodicity. Thus, if the ULPI monitoring periodicity is <NUM> slots (e.g., <NUM> symbols), then using the <NUM> bits, and with two frequency parts, each bit corresponds to a <NUM> symbol time part.

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for uplink preemption indication (ULPI). According to certain aspects, the ULPI can indicate a power dimension indication. According to certain aspects, the ULPI indicates preemption for resources over a duration longer than a ULPI monitoring periodicity and/or multiple ULPIs in different ULPI monitoring occasions may indicate preemption information for overlapping resources. Aspects provide techniques and apparatus for handling conflicting ULPI indications.

According to certain aspects, instead of, or in addition to, indicating whether resources are preempted or not preempted, the ULPI may include a power dimension to indicate a power level or power back-off the UE can use for the indicated resources. For example, the ULPI may indicate a power back-off for a user equipment (UE) to apply to an uplink transmission for a first service (e.g., enhanced mobile broadband (eMBB)), for example, in order to reduce interference to an uplink transmission by another UE for a second service (e.g., ultra-reliable low-latency communication (URLLC)).

<FIG> is a flow diagram illustrating operations <NUM> for wireless communication, in accordance with the present invention. The operations <NUM> are performed, by a UE (e.g., such as a UE 120a in the wireless communication network <NUM>). Operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., processor <NUM> of <FIG>). Further, the transmission and reception of signals by the UE in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the transmission and/or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., processor <NUM>) obtaining and/or outputting signals.

The operations <NUM> begin, at <NUM>, by receiving at least one ULPI from a BS indicating, for one or more of a plurality of sets of uplink resources, a power level the UE can use for one or more uplink transmissions. In some scenarios, the ULPI can indicate a power level for each of a plurality of sets of uplink resources. The one or more set of resources may include a plurality of RBs in one or more symbols.

As mentioned above, the ULPI may indicate the power level to preempt a first uplink transmission for a second uplink transmissions. The power level comprises a power back-off. As shown in <FIG>, the ULPI includes at least <NUM> bits for each resource set, the values of the at least <NUM> bits at least indicating no back-off (e.g., 'not preempted'), a first non-zero power back-off amount (e.g., <NUM> dB), a second non-zero power back-off amount (e.g., <NUM> dB, or full power back-off (e.g., 'preempted' and the UE does not transmit on those resources). The non-zero backoff amounts may be configured by the network, for example, via radio resource control (RRC) signaling.

At <NUM>, the UE sends or drops the one or more uplink transmissions according to the ULPI. For example, the eMBB UE may receive the ULPI via downlink signaling and suspend or reduce any transmissions scheduled during the URLLC transmissions as indicated by the ULPI. This enables the URLLCs to avoid interference with eMBB transmissions and provide an optimal wireless environment for the URLLCs.

According to certain aspects, a UE determines one or more power levels indicated by the ULPI for resources allocated for the UE for uplink transmission. Allocated resources include multiple sets of uplink resources. For example, as shown in <FIG>, the ULPI provides preemption information for the resource sets <NUM>, <NUM>,. <NUM>, and the UE uplink resource allocation <NUM> overlaps four of the resource sets <NUM>, <NUM>, <NUM>, and <NUM> indicated by the ULPI. As shown in <FIG>, the ULPI indicates <NUM> dB power back-off for resource sets <NUM>, <NUM>, and <NUM>, and indicates preemption (full power back-off) for the resource set <NUM>. Thus, the UE selects the power level to use for uplink transmission using the allocated resources based, at least in part, on the determination. The UE may select the power level to use based on various approaches, for example, according to a rule.

According to certain aspects, a UE can apply one or more respective power back-off indicated by the ULPI for sets of uplink resources in the uplink resource allocation (e.g., according to a first rule). For the example shown in <FIG>, according to this rule, the UE applies the <NUM> dB power back-off for the RBs of the uplink resource allocation <NUM> included in the resource sets <NUM>, <NUM>, and <NUM>, and the UE applies the full power back-off for the RBs of the uplink resource allocation <NUM> included in the resource set <NUM>. As used herein, full power back-off may refer to canceling or dropping uplink transmission on the indicated resources.

According to certain aspects, the UE applies the worst case power back-off on a per symbol (e.g., OFDM symbol) basis (e.g., according to a second rule). For example, in each symbol, the UE can select the lowest power level indicted by the ULPI for the sets of uplink resources in the symbol. For example, if for a symbol k, the UE receives backoff power of -<NUM> dB on one set of RBs, and a backoff power of -<NUM> dB on another set of RBs, then UE may apply the backoff power -<NUM> dB on all RBs on that symbol. For the example shown in <FIG>, according to this rule, the UE applies the worst case, full power back-off, for the RBs of the uplink resource allocation <NUM> included in the resource sets <NUM> and <NUM> (which are in the same symbol(s)) and applies the worst case, <NUM> dB power back-off, for the RBs of the uplink resource allocation <NUM> included in the resource sets <NUM> and <NUM> (which are in the same symbol(s)).

According to certain aspects, the UE applies the worst case power back-off for the entire resource allocation (e.g., according to a third rule). For example, the UE selects, for all of the sets of uplink resources included in the allocated resources, a lowest power level indicated by the ULPI for those sets of uplink resources. For the example shown in <FIG>, according to this rule, the UE applies the worst case, full power back-off (e.g., cancels or drops uplink transmission), for the all RBs of the uplink resource allocation <NUM> included in the resource sets <NUM>, <NUM>, <NUM>, and <NUM>.

According to certain aspects, the UE selects the rule to apply (e.g., one of the rules described above). In examples, the UE may determine the rule for selecting the power level based on a capability of the UE. For example, the UE may report its capability to apply independent power back-off on different RBs, to apply per-symbol worst case power back-off, and/or to apply worst case power back-off for all of the resource sets. In some examples, the UE may determine the rule for selecting the power level based on a transmission waveform configured for the uplink transmission. For example, the UE may use the first rule (respective power back offs), for cyclic prefix OFDM (CP-OFDM), and the UE may use the second rule (per symbol worst case power backoff) or the third rule (worst case power backoff for the entire allocation) for discrete Fourier transform spreaded OFDM (DFT-S-OFDM).

According to certain aspects, multiple component carriers (CCs) are configured with carrier aggregation (CA). In this case, the ULPI may contain preemption and/or power level information for one or more uplink CCs. For example, as shown in <FIG>, the frequency domain may be divided in to two CCs (UL CC1 and UL CC2). Thus, the plurality of sets of uplink resources can include a plurality of uplink CCs and each set of resources comprises one or more uplink CCs. The rules described above for selecting the power level for the RBs of the uplink resource allocation may be used for selecting the power levels for the CCs. For example, the UE can apply the power level indicated for each set of CCs independently, the UE can apply per-symbol worst case power level, and/or worst case power level for all of the resource sets.

According to certain aspects, the UE can determine one or more rules for selecting power levels further based on whether the CCs are in a same frequency band. For example, if some CCs are in the same frequency band, the UE may apply the worst-case power-backoff/pre-emption from among those CCs in the same frequency band to those CCs. In some examples, the UE may pre-empt transmissions on all CCs in the same frequency band on the symbols indicated in ULPI, even if the ULPI indicates only preemption in a particular CC in the frequency band. If two CCs are not in the same frequency band, then UE may always perform independent power-backoff/pre-emption to those CCs.

The UE may also support downlink CA. The ULPI may be sent from different downlink CCs. Thus, the UE may monitor a plurality of downlink CCs for the ULPI. According to certain aspects, a ULPI is transmitted on each DL CC with the preemption information for the corresponding UL CC. For example, in the example shown in <FIG>, the ULPI1 is sent on DL CC1 for the UL CC1 and the ULPI2 is sent on the DL CC2 for the UL CC2. According to certain aspects, a ULPI may be transmitted on a DL CC for multiple UL CCs. Thus, the UE may apply the ULPI information for the corresponding CC(s). In some cases, the ULPI monitored on the different downlink CCs may contain preemption information for overlapping resources. For example, the UE may monitor/receive ULPI for the UL CC1 on both DL CC1 and DL CC2, as shown in <FIG>. In this case, the UE may assume/expect that the two ULPI received on the DL CC1 and the DL CC2 indicate consistent (e.g., the same) power and/or preemption information. Multiple ULPI with the same information may improve reliability of the ULPI reception (e.g., because the same ULPI is transmitted form the BS on multiple DL CCs which provides frequency diversity). Thus, in some examples, if the information in the ULPIs conflicts, the UE may treat the information as an error case (e.g., the UE disregards the information).

According to certain aspects, even if a ULPI provides information for some uplink CCs (e.g., in <FIG>, ULPI1 on DL CC1 and ULPI2 on DL CC2 each provide information for UL CC1 and UL CC2), if the UE has simultaneous uplink transmission on another CC (e.g., CC3 in <FIG>), the UE may apply the power level indicated by the ULPI on the other CC (e.g., based on UE capability) as shown in <FIG>. For example, the UE selects a power level for uplink transmission on one or more CCs not indicated by the at least one ULPI based on the power level selected for one or more CCs that are indicated by the at least one ULPI.

<FIG> is a flow diagram illustrating example operations <NUM> for wireless communication, in accordance with certain aspects of the present disclosure. The operations <NUM> may be performed, for example, by a BS (e.g., such as the BS 11a0 in the wireless communication network <NUM>). The operations <NUM> may be complimentary operations by the BS to the operations <NUM> performed by the UE. Operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., processor <NUM> of <FIG>). Further, the transmission and reception of signals by the BS in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the transmission and/or reception of signals by the BS may be implemented via a bus interface of one or more processors (e.g., processor <NUM>) obtaining and/or outputting signals.

Optionally, at <NUM>, the BS may determine uplink resources, of a plurality of sets of uplink resources, configured for at least a first UE for a first type of uplink service.

At <NUM>, the BS transmits at least one ULPI to a UE (e.g., a second UE) indicating, for one or more of a plurality of sets of uplink resources, a power level (e.g., a backoff power level) the UE can use for transmission on that set of uplink resources (e.g., for a second type of uplink service). In some scenarios, the ULPI can indicate a power level for each of a plurality of sets of uplink resources.

In certain systems, the UE monitors PI (e.g., ULPI and/or DLPI) at a monitoring periodicity. For example, the UE may monitor every <NUM> slots within one PI monitoring period. In some examples, the PI indicates preemption information of the resources in <NUM> slots. According to certain aspects, ULPIs may point to overlapping resources. Aspects provide for which ULPI the UE should follow when the ULPIs pointing to overlapping resources provide conflicting preemption information. In some cases, the later ULPI may override the earlier ULPI only when certain conditions are met.

In some cases, the monitoring periodicity for ULPI may be much smaller (e.g., <NUM> OFDM symbols), for example, to meet the stringent URLLC latency. In this case, it may be in-effective for ULPI to indicate only resources for a time duration equal to the monitoring periodicity, for example, because the ULPI may need to be padded, such that the size of the ULPI is a certain number of bits (e.g., <NUM> bits). Instead of adding dummy zero padding bits, the ULPI could indicate resources for a time duration equal to multiple monitoring periods as shown in <FIG>. As shown in <FIG>, the UE may receive a first ULPI <NUM> in the monitoring period in a monitoring period <NUM> and a second ULPI <NUM> in a second monitoring period <NUM>. In this example, the preemption information does not change in the monitoring period <NUM> and, thus, a third ULPI is not received during that monitoring period. The first ULPI <NUM> and the second ULPI <NUM> can provide preemption information on overlapping resource sets. As shown in <FIG>, the first ULPI <NUM> provides preemption information for time frequency resources <NUM>, <NUM>, and <NUM> and the second ULPI <NUM> provides preemption information for the time frequency resources <NUM>, <NUM>, and <NUM>. As shown in <FIG>, the first ULPI <NUM> indicates 'no preemption' for the time frequency resource <NUM>; however, the second ULPI <NUM> indicates 'preemption' for the time frequency resource <NUM>, which overlaps the time frequency resource <NUM>. For example, after sending the first ULPI <NUM>, the BS may schedule some more urgent URLLC service in the time frequency resource <NUM>. Thus, as shown in <FIG>, the ULPIs may provide conflicting information for the overlapping resources. Aspects provide techniques and apparatus for handling of conflicting ULPIs, such as for determining which ULPI to apply.

<FIG> is a flow diagram illustrating example operations <NUM> for wireless communication, in accordance with certain aspects of the present disclosure. The operations <NUM> may be performed, for example, by a UE (e.g., such as the UE 120a in the wireless communication network <NUM>). Operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., processor <NUM> of <FIG>). Further, the transmission and reception of signals by the UE in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the transmission and/or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., processor <NUM>) obtaining and/or outputting signals.

The operations <NUM> may begin, at <NUM> receiving a first ULPI in a first ULPI monitoring period from a BS indicating, for a first plurality of sets of uplink resources, whether the resources are preempted (e.g., eMBB preempted for URLLC). A time duration of the plurality of sets of uplink resources is longer than a configured ULPI monitoring periodicity for the UE. One or more set of resources may include a plurality of RBs in one or more symbols. The monitoring periodicity may be less than <NUM> slots.

At <NUM>, the UE sends or drops one or more uplink transmissions according to the ULPI.

According to certain aspects, the UE receives a second ULPI from the BS in a second ULPI monitoring period indicating, for a second plurality of sets of uplink resources, whether the resources are preempted. The UE determines whether the first and second plurality of sets of uplink resources overlap and, for the overlapping resources, the UE determines whether the first and second ULPIs conflict. Then, the UE determines whether to apply the first ULPI or to apply the second ULPI for the overlapping sets of uplink resources.

In some examples, the later ULPI overwrites the earlier ULPI. The UE may determine to always apply the second ULPI on overlapping uplink resources. In some examples, the overwriting may only happen in one direction. For example, if the earlier ULPI indicates 'no-preempt' for a resource set (e.g., the ULPI <NUM> as shown in <FIG>), a later ULPI indicating 'preempt' for the resource set (the ULPI <NUM> as shown in <FIG>) overwrites the earlier indication; however, a later ULPI indicating 'no-preempt' for a resource set does not overwrite an earlier ULPI indicating 'preempt' for the resource set. That is to say, in some examples, the later ULPI only overwrites the earlier ULPI when the later ULPI indicates preemption and the earlier ULPI does not indicate preemption, but a later ULPI indicating not to preempt would not override an earlier ULPI indicate to preempt. This may save DCI overhead. For example, if the eMBB transmission is much longer than the ULPI monitoring periodicity, then one ULPI could preempt multiple portions of an eMBB transmission. For example, an earlier indication of no preemption resources in a first ULPI may be overridden by a later indication of preempt for the resources in a second ULPI to schedule an urgent URLLC transmission in the resources after sending the first ULPI.

<FIG> is a flow diagram illustrating example operations <NUM> for wireless communication, in accordance with certain aspects of the present disclosure. The operations <NUM> may be performed, for example, by BS (e.g., such as a BS 110a in the wireless communication network <NUM>). The operations <NUM> may be complimentary operations by the BS to the operations <NUM> performed by the UE.

Optionally, at <NUM>, the BS may determine uplink resources, of a plurality of sets of uplink resources, configured for at least a first UE for a first type of uplink service. At <NUM>, the BS transmits a first ULPI to a UE in a first ULPI monitoring period indicating, for a first plurality of sets of uplink resources, whether the resources are preempted. A time duration of the plurality of sets of uplink resources is longer than a configured ULPI monitoring periodicity for the UE.

Techniques described herein provide advantages to URLLC systems. To improve the latency and reliability of URLLC systems, the RAN may signal to one or more UEs, via the ULPI, to suspend transmissions or reduce the transmit power of transmissions during scheduled URLLC transmissions. This may reduce the interference encountered at the BS and enhance the signal to noise ratio of URLLC signals. Also, cross-carrier information enables the RAN to service more than one CC, reducing the signaling overhead to preempt resources as described herein.

<FIG> illustrates a communications device <NUM> that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in <FIG> and/or <FIG>.

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that when executed by the processor <NUM>, cause the processor <NUM> to perform the operations illustrated in <FIG> and/or <FIG>, or other operations for performing the various techniques discussed herein for ULPI. In certain aspects, computer-readable medium/memory <NUM> stores code <NUM> for receiving ULPI;; and code <NUM> for sending or dropping uplink transmissions based on the ULPI, in accordance with aspects of the disclosure. In certain aspects, the processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>. The processor <NUM> includes circuitry <NUM> for receiving ULPI; and circuitry <NUM> for sending or dropping uplink transmissions based on the ULPI, in accordance with aspects of the disclosure.

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that when executed by the processor <NUM>, cause the processor <NUM> to perform the operations illustrated in <FIG> and/or <FIG>, or other operations for performing the various techniques discussed herein for ULPI. In certain aspects, computer-readable medium/memory <NUM> stores code <NUM> for determining uplink resources configured for a first UE for a first type of service; code <NUM> for sending ULPI to second UE configured for a second type of service, indicating power levels; and code <NUM> for sending ULPI to second UE configured for a second type of service, indicating whether resource are preempted for a duration longer than a configured ULPI monitoring periodicity, in accordance with aspects of the disclosure. In certain aspects, the processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>. The processor <NUM> includes circuitry <NUM> for determining uplink resources configured for a first UE for a first type of service; circuitry <NUM> for sending ULPI to second UE configured for a second type of service, indicating power levels; and circuitry <NUM> for sending ULPI to second UE configured for a second type of service, indicating whether resource are preempted for a duration longer than a configured ULPI monitoring periodicity.

In NR systems, the term "cell" and next generation NodeB (gNB or gNodeB), NR BS, <NUM> NB, access point (AP), or transmission reception point (TRP) may be interchangeable.

For example, instructions for performing the operations described herein and illustrated in <FIG>, <FIG>, <FIG>, and/or <FIG>.

Claim 1:
A method (<NUM>) for wireless communication by a user equipment, UE, comprising:
receiving (<NUM>) at least one uplink preemption indication, ULPI, from a base station, BS, indicating, for one or more of a plurality of sets of uplink resources, a power level the UE can use for one or more uplink transmissions;
wherein the indication of the power level comprises a power back off value for the one or more of the plurality of sets of uplink resources; and
sending (<NUM>) or dropping the one or more uplink transmissions according to the ULPI; characterized in that the ULPI comprises at least <NUM> bits for each resource set; and values of the at least <NUM> bits at least indicate one of no power back-off, a first non-zero power back-off value, a second non-zero power back-off value, or full power back-off, full power-back off indicating the resource set is preempted and the UE does not transmit on the resource set; further comprising receiving radio resource control, RRC, signaling configuring the first and second non-zero power back-off values.