Patent Description:
In some examples, a wireless multiple-access communication system may include a number of base stations, each simultaneously supporting communication for multiple communication devices, otherwise known as user equipment (UEs). In LTE or LTE-A network, a set of one or more base stations may define an e NodeB (eNB). In other examples (e.g., in a next generation or <NUM> network), a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with a number of central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a set of one or more distributed units, in communication with a central unit, may define an access node (e.g., a new radio base station (NR BS), a new radio node-B (NR NB), a network node, <NUM> NB, gNB, etc.). A base station or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station or to a UE) and uplink channels (e.g., for transmissions from a UE to a base station or distributed unit).

Qualcomm Incorporated, R1-<NUM> relates to indication channels for dynamic multiplexing between URLLC and eMBB on the downlink. InterDigital Inc. , R1-<NUM> relates to dynamic multiplexing between eMBB and URLLC on the downlink and handling UL multiplexing with different reliability requirements. Qualcomm Incorporated, R1-<NUM> relates to DL indication channel design and indication schemes with different periodicities.

The methods, and devices of the disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes.

Certain aspects of the present disclosure provide a method for wireless communication that may be performed, for example, by a base station (BS), according to independent claim <NUM>.

Certain aspects of the present disclosure provide a method for wireless communication that may be performed, for example, by a user equipment (UE), according to independent claim <NUM>.

It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope.

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

Aspects of the present disclosure provide techniques and apparatus for dynamic switching between non-codebook and codebook based uplink transmission schemes.

<FIG> illustrates an example wireless network <NUM> in which aspects of the present disclosure may be performed. For example, the wireless network <NUM> may be a new radio (NR) or <NUM> network. In certain aspects, a BS <NUM> may signal an uplink preemption indication (ULPI) to a UE of a first type (e.g., eMBB UE) to reallocate uplink channel resources to a UE of a second type (e.g., URLLC UE) as further described herein with respect to <FIG>. In other aspects, the BS <NUM> may signal a downlink preemption indication (DLPI) to the UE of the first type (e.g., eMBB UE) to reallocate downlink channel resources to the UE of the second type (e.g., URLLC UE) as further described herein with respect to <FIG>.

As illustrated in <FIG>, the wireless network <NUM> may include a number of BSs <NUM> and other network entities. A BS may be a station that communicates with UEs. Each BS <NUM> may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a Node B and/or a Node B subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term "cell" and gNB, Node B, <NUM> NB, AP, NR BS, NR BS, or TRP may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station. In some examples, the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in the wireless network <NUM> through various types of backhaul interfaces such as a direct physical connection, a virtual network, or the like using any suitable transport network.

For example, a macro BS may have a high transmit power level (e.g., <NUM> Watts) whereas pico BS, femto BS, and relays may have a lower transmit power level (e.g., <NUM> Watt).

The BSs <NUM> may also communicate with one another, e.g., directly or indirectly via wireless or wireline backhaul.

A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE), a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered evolved or machine-type communication (MTC) devices or evolved MTC (eMTC) devices. Some UEs may be considered Internet-of Things (IoT) devices.

For example, the spacing of the subcarriers may be <NUM> and the minimum resource allocation (called a 'resource block') may be <NUM> subcarriers (or <NUM>). Consequently, the nominal FFT size may be equal to <NUM>, <NUM>, <NUM>, <NUM> or <NUM> for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM> or <NUM> megahertz (MHz), respectively. For example, a subband may cover <NUM> (i.e., <NUM> resource blocks), and there may be <NUM>, <NUM>, <NUM>, <NUM> or <NUM> subbands for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM> or <NUM>, respectively.

A single component carrier bandwidth of <NUM> may be supported. NR resource blocks may span <NUM> sub-carriers with a subcarrier bandwidth of <NUM> over a <NUM> duration. Each radio frame may consist of <NUM> subframes with a length of <NUM>. Consequently, each subframe may have a length of <NUM>. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. UL and DL subframes for NR may be as described in more detail below with respect to <FIG>. For certain NR networks, such as eMBB and/or URLLC, each subframe may include a subcarrier including up to <NUM> slots. A slot may be include to <NUM> minislots and up to <NUM> OFDM symbols. A minislot may include one or more OFDM symbols. OFDM symbols in a slot can be classified as downlink, flexible (i.e., downlink or uplink), or uplink. Alternatively, NR may support a different air interface, other than an OFDM-based. NR networks may include entities such CUs and/or DUs.

As noted above, a RAN may include a CU and DUs. A NR BS (e.g., gNB, <NUM> NB, NB, TRP, AP) may correspond to one or multiple BSs. NR cells can be configured as access cells (ACells) or data only cells (DCells). For example, the RAN (e.g., a central unit or distributed unit) can configure the cells. DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some cases DCells may not transmit synchronization signals-in some case cases DCells may transmit SS. NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.

<FIG> illustrates example components of the BS <NUM> and UE <NUM> illustrated in <FIG>, which may be used to implement aspects of the present disclosure. One or more components of the BS <NUM> and UE <NUM> may be used to practice aspects of the present disclosure. For example, antennas <NUM>, Tx/Rx <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM> and/or antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the BS <NUM> may be used to perform the operations described herein and illustrated with reference to <FIG>.

At the base station <NUM>, a transmit processor <NUM> may receive data from a data source <NUM> and control information from a controller/processor <NUM>. The control information may be for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), etc. The data may be for the Physical Downlink Shared Channel (PDSCH), etc. The processor <NUM> may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor <NUM> may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal.

The processor <NUM> and/or other processors and modules at the BS <NUM> may perform or direct, e.g., the execution of the functional blocks illustrated in <FIG> and <FIG> and/or other processes for the techniques described herein. The processor <NUM> and/or other processors and modules at the UE <NUM> may also perform or direct, e.g., the execution of the functional blocks illustrated in <FIG> and <FIG> and/or other processes for the techniques described herein. The memories <NUM> and <NUM> may store data and program codes for the BS <NUM> and the UE <NUM>, respectively.

The DL-centric subframe may also include a common UL portion <NUM>. The common UL portion <NUM> may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL portion <NUM> may include feedback information corresponding to various other portions of the DL-centric subframe. For example, the common UL portion <NUM> may include feedback information corresponding to the control portion <NUM>. Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion <NUM> may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs), and various other suitable types of information. As illustrated in <FIG>, the end of the DL data portion <NUM> may be separated in time from the beginning of the common UL portion <NUM>. One of ordinary skill in the art will understand that the foregoing is merely one example of a DL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

<FIG> is a diagram <NUM> showing an example of an UL-centric subframe. The UL -centric subframe may include a control portion <NUM>. The control portion <NUM> may exist in the initial or beginning portion of the UL-centric subframe. The control portion <NUM> in <FIG> may be similar to the control portion <NUM> described above with reference to <FIG>. The UL-centric subframe may also include an UL data portion <NUM>. The UL data portion <NUM> may sometimes be referred to as the payload of the UL-centric subframe. The UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS). In some configurations, the control portion <NUM> may be a physical DL control channel (PDCCH).

As illustrated in <FIG>, the end of the control portion <NUM> may be separated in time from the beginning of the UL data portion <NUM>. The UL-centric subframe may also include a common UL portion <NUM>. The common UL portion <NUM> in <FIG> may be similar to the common UL portion <NUM> described above with reference to <FIG>. The common UL portion <NUM> may additional or alternative include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), and various other suitable types of information. One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein. In one example, a frame may include both UL centric subframes and DL centric subframes. In this example, the ratio of UL centric subframes to DL subframes in a frame may be dynamically adjusted based on the amount of UL data and the amount of DL data that are transmitted. For example, if there is more UL data, then the ratio of UL centric subframes to DL subframes may be increased. Conversely, if there is more DL data, then the ratio of UL centric subframes to DL subframes may be decreased.

Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet-of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications.

In wireless communications, channel state information (CSI) may refers to known channel properties of a communication link. The CSI may represent the combined effects of, for example, scattering, fading, and power decay with distance between a transmitter and receiver. Channel estimation may be performed to determine these effects on the channel. CSI may be used to adapt transmissions based on the current channel conditions, which is useful for achieving reliable communication, in particular, with high data rates in multi-antenna systems. CSI is typically estimated at the receiver, quantized, and fed back to the transmitter.

Certain communication systems (e.g., NR) maintain ultra-reliable low latency communication (URLLC) which provides requirements for latency and reliability. For example, URLLC may provide an end-to-end latency of <NUM> milliseconds and block error ratio (BLER) of <NUM>-<NUM> within <NUM> millisecond. In order to improve URLLC services, the RAN may signal to a UE to suspend or perform power control on ongoing transmissions when URLLC transmissions are scheduled. This preemption of resources may facilitate a reduction in interference with the URLLC transmissions. As further described herein, the RAN may transmit an indication to the eMBB UE to take one or more actions to reduce interference with a scheduled URLLC transmission.

Aspects presented herein provide techniques for signaling an uplink preemption indication (ULPI) to a UE of a first type (e.g., eMBB UE) to reallocate uplink channel resources to a UE of a second type (e.g., URLLC UE).

<FIG> is a flow diagram illustrating example operations <NUM> that may be performed, for example, by a base station and/or radio access network (e.g., BS <NUM> of <FIG>), for implementing an uplink preemption indication (ULPI), in accordance with certain aspects of the present disclosure. 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.

Operations <NUM> may begin, at <NUM>, by the BS determining that resources allocated for a scheduled transmission by a first user equipment (UE) of a first type (e.g., URLLC UE) overlap with uplink channel resources allocated to a second UE of a second type (e.g., eMBB UE). At <NUM>, the BS signals, based on the determination at <NUM>, an uplink preemption indication (ULPI), to the second UE, that identifies at least some of the overlapping resources.

<FIG> is a flow diagram illustrating example operations <NUM> that may be performed, for example, by a UE (e.g., UE <NUM>), for implementing the reception and processing of the ULPI, in accordance with certain aspects of the present disclosure. 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.

Operations <NUM> may begin, at <NUM>, by the UE signaling an uplink signal to a base station (BS) via uplink channel resources allocated to a first UE of a first type (e.g., eMBB UE). At <NUM>, the first UE receives an uplink preemption indication (ULPI) from the BS. At <NUM>, the first UE takes one or more actions, as further described herein, based on one or more resources identified in the ULPI, wherein the one or more resources overlap with resources allocated for a scheduled transmission by a second UE of a second type (e.g., URLLC UE).

In certain aspects, taking one or more actions may include various actions taken by the UE as further described herein. For example, taking one or more actions may include reducing a transmit power during the scheduled transmission. Taking one or more actions may also include suspending a transmission by the first UE during the scheduled transmission. Taking one or more actions may also include resuming a transmission by the first UE after the scheduled transmission. In certain aspects, taking one or more actions may depend on the identified resources being a physical uplink control channel (PUCCH) resources, semi-persistently scheduled (SPS) resources, sounding reference signal (SRS) resources, physical random access channel (PRACH) resources, physical broadcast channels (PBCH) resources, demodulation reference signal (DMRS) resources, synchronization signal block (SSB) resources, phase-track reference signal (PTRS) resources, channel state information reference signal (CSIRS) resources and the like as further described herein.

In certain aspects, the eMBB UE may receive the ULPI via downlink signaling and suspend any transmissions scheduled during the URLLC transmissions as indicated by the ULPI. For example, <FIG> illustrates a frequency-timing diagram of an example downlink channel <NUM> and uplink channel <NUM>, in accordance with aspects of the present disclosure. As shown, the downlink and uplink channels <NUM> and <NUM> span a slot <NUM>. The BS may transmit an URLLC DCI <NUM> and an ULPI <NUM> via the DL-channel <NUM>. As the eMBB UE is transmitting UL data <NUM> via the UL-channel <NUM>, the eMBB UE receives the ULPI and determines which of its allocated resources overlap with the scheduled URLLC transmission. The DCI <NUM> may provide an UL grant to the URLLC UE and the URLLC UE may transmit UL data <NUM> via the UL-channel <NUM>. At the same time the eMBB UE may suspend UL transmissions using the resources reallocated to the URLLC UE as indicated by the ULPI. This enables the URLLCs to avoid interference with eMBB transmissions and provide an optimal wireless environment for the URLLCs. In certain aspects, the BS may also periodically signal the ULPI to the eMBB UE every one or more OFDM symbols or slots as shown by the second ULPI <NUM>.

In certain aspects, the ULPI may be signaled via a different location of a search space and/or a control resource region than a downlink preemption indication (DLPI). The DLPI may also be signalled using a radio network temporary identifier (RNTI) distinct from an RNTIused to signal the DLPI. In certain aspects, the ULPI may be signaled using the same location of a search space and/or a control resource region and the same RNTI as the DLPI, but there is an additional indication to decide whether the signaling is for uplink or downlink preemption.

In certain aspects, the ULPI identifies one or more resources allocated to the eMBB UE relative to a reference uplink region (RUR). For example, <FIG> illustrates a frequency-timing diagram of example downlink and uplink channels <NUM> and <NUM>, respectively. As shown, the downlink and uplink channels <NUM> and <NUM> span three slots. In the second slot, ULPI <NUM> is transmitted via downlink signaling. The ULPI may indicate an offset time <NUM>, which is, for example, relative to the transmit time of the ULPI as shown in <FIG>. The offset time <NUM> indicates to the eMBB UE when a RUR (e.g., RUR <NUM>) begins within the UL-channel <NUM> and may be one or more minislots in length. The RUR is a resource map that includes a duration <NUM> and one or more resources <NUM> that are reallocated to the URLLC UE, which is granted UL resources <NUM>. The resources <NUM> reallocated to the scheduled URLLC transmission may also be referred to, herein, as a preemption gap.

In certain aspects, the BS may service UEs having various capabilities, such as latency capabilities, and provide information in the ULPI to take into account these different types of UEs. For example, the ULPI <NUM> may provide a second RUR <NUM> that has an offset time longer in length than the first RUR <NUM>. That is, the ULPI <NUM> may indicate to UEs, having a longer latency, an offset time that provides those UEs with enough time to respond to the ULPI <NUM>.

In certain aspects, the ULPI may be exclusive to one or more UEs having a specific capability, such as a ULPI that is specific to a particular UE (i.e., a UE-specific ULPI). That is, the RAN may generate a ULPI for a group of UEs that have a specific capability, e.g., latency. For example, <FIG> illustrates a diagram of example ULPI formats 1220A and B, in accordance aspects of the present disclosure. As shown, ULPI format 1220A has RUR information <NUM> that is exclusive to one or more UEs having a specific capability. Similarly, ULPI format 1220B has RUR information <NUM> that is exclusive to one or more UEs having another specific capability.

In certain aspects, the ULPI may apply to UEs having different capabilities (e.g., latency), such as a ULPI that is common among a group of UEs (i.e., a group-common ULPI). That is, the RAN generates a ULPI that has RUR information for UEs having different capabilities or a ULPI that is common among a group of UEs (i.e., a group-common ULPI). For example, <FIG> illustrates a diagram of an example ULPI format <NUM>, in accordance with certain aspects of the present disclosure. As shown, the ULPI format <NUM> includes RUR information <NUM> that applies to UEs having a specific capability and RUR information <NUM> that applies to UEs having a different capability. As further described herein, the RUR information is conveyed via a bitmap in the ULPI. When the ULPI applies to UEs having different capabilities, the UEs of one capability may use part of the bitmap, ignoring the rest of the RUR information in the bitmap used by the UEs of the other capability.

In certain aspects, the ULPI format may be determined based on the exchange of information between the RAN and the UE, such as exchanging RRC information. In some aspects, the ULPI format may be programmed in advance such that the RAN does not exchange information with a UE to determine the ULPI format compatible for that UE.

The ULPI includes a bitmap that identifies the one or more resources to be used during the scheduled URLLC transmission. The bitmap may define the duration of and resources included in the RUR. Each bit of the bitmap may represent various resource parameters. A bit of the bitmap corresponds to a wideband resource, a subband resource, or one or more OFDM symbols of the RUR. Wideband resources may refer to all frequency-domain resources in an active bandwidth part (BWP) of one component carrier, or in the active BWPs of component carriers in intra-band contiguous carrier aggregation. For instance, <FIG> illustrates a diagram of an example bitmap <NUM>, in accordance with certain aspects of the present disclosure. As shown, the ULPI <NUM> provides a bitmap <NUM> including <NUM> bits, where each bit represents a wideband uplink resource. The bitmap <NUM> identifies uplink resources that are reallocated for the URLLC transmission. As shown, a bit <NUM> having a value of "<NUM>" may indicate a resource not reallocated for URLLC transmission, and a bit <NUM> having a value of "<NUM>" may indicate the resource that is identified as being reallocated for the URLLC transmission. The bits in a ULPI may be evenly distributed across the time duration of a RUR that can be one or more slots. As a result, each bit in the ULPI represents one or multiple OFDM symbols.

<FIG> illustrates a diagram of an example bitmap <NUM> divided by subband, in accordance with aspects of the present disclosure. As shown, the ULPI <NUM> provides a bitmap <NUM> including <NUM> bits, where each bit represents a subband uplink resource by dividing the RUR region equally by the <NUM> bits. In <FIG>, the bit <NUM> identifies a subband uplink resource that is reallocated for the URLLC transmission. Also, the bitmap <NUM> may be formed by making bit <NUM> the most significant bit (MSB), going down from the MSB to make the next bit in the bitmap, and up to the subband adjacent to the MSB to make the next bit in the bitmap, and so on as indicated by the arrows. Whereas each bit of <FIG> spans a single OFDM symbol, each bit of <FIG> spans two OFDM symbols, providing a time duration of <NUM> OFDM symbols for the RURs shown in <FIG>.

In certain aspects, the ULPI may include a bitmap that represents UL resources in a time division duplex (TDD) configuration. For example, <FIG> illustrates a diagram of an example bitmap <NUM> for a TDD configuration, in accordance with certain aspects of the present disclosure. As shown, the ULPI <NUM> provides a bitmap <NUM> including <NUM> bits, where each bit represents one or more OFDM symbols of a wideband uplink resource by dividing the RUR region by the <NUM> bits as evenly as possible. The RUR represented by bitmap <NUM> spans two slots that have <NUM> OFDM symbols. The first two downlink symbols <NUM> in the subframe may be indicated as being omitted from the bitmap. That is, the UE may interpret the bitmap to indicate whether uplink or flexible resources are reallocated for URLLC transmission. The most significant bit of the bitmap is bit <NUM> including two flexible OFDM symbols. The next bit of the bitmap corresponds to the two uplink symbols after bit <NUM>. Bit <NUM> includes an uplink symbol, two downlink symbols, and a flexible symbol. The UE ignores any downlink resources associated with the bit or adjacent to the bit, such that the UE takes no action regarding the downlink resources that may be adjacent or within the bit. Similarly, the downlink resources <NUM> are ignored or omitted from the bitmap. Each bit of the last bits starting with the bit <NUM> covers a single uplink or flexible symbol.

Similar to <FIG>, the ULPI may include a TDD bitmap that covers subband resources. For example, <FIG> illustrates a diagram of an example bitmap <NUM> for a TDD configuration, in accordance with certain aspects of the present disclosure. As shown, the ULPI <NUM> provides a bitmap <NUM> including <NUM> bits, where each bit represents one or more OFDM symbols of a subband uplink resource by dividing the RUR region by the <NUM> bits as evenly as possible in the time and frequency domains. The first four downlink symbols <NUM> in the subframe may be indicated as being omitted from the bitmap. As shown, the most significant bit is bit <NUM>, which has to six symbols within a subband. The bitmap is formed from the MSB <NUM> similar to the progression indicated by the arrows in <FIG>.

In certain aspects, the RUR of the ULPI may include or exclude one or more resources in a physical uplink control channel (PUCCH). For example, <FIG> illustrates an example diagram of uplink channels 1800A and B, in accordance with certain aspects of the present disclosure. As shown, the RUR <NUM> includes physical uplink shared channel (PUSCH) resources <NUM> and PUCCH resources <NUM>, which may be short or long PUCCH resources. The long PUCCH resources may span an entire slot as illustrated in <FIG>. In cases where the RUR identifies PUCCH resources as being reallocated, the UE may continue to transmit control signaling using the PUCCH resources, suspend transmission of control signaling using the PUCCH resources, or reduce the power of transmissions using the PUCCH resources. Similarly, after transmitting the UPLI identifying PUCCH resources to be reallocated, the BS may receive uplink signals from the eMBB UE via the PUCCH resources during the scheduled transmission and decode the scheduled URLLC transmission based at least in part on the effect of the received uplink signals on the scheduled transmissions. For example, the BS may cancel out the received uplink signals to decode the scheduled URLLC transmission. In certain aspects, the scheduled URLLC transmissions may not use PUCCH resources of the eMBB UEs that are included in the RUR. That is, even though the RUR may include PUCCH resources, these resources may not be reallocated to URLLC transmissions.

<FIG> illustrates an example diagram of uplink channels 1900A and B where PUCCH resources <NUM> are included in the RUR <NUM>, in accordance with certain aspects of the present disclosure. As shown, the RUR <NUM> excludes PUCCH resources <NUM>, which may be short or long PUCCH resources, from being identified as reallocated resources.

In certain aspects, the RUR may include or exclude sounding reference signal (SRS) resources similar to the PUCCH resources as previously discussed. For example, <FIG> shows the RUR <NUM> including SRS resources <NUM>. In cases where the RUR identifies SRS resources as being reallocated, the UE may continue to transmit the SRS using the SRS resources, suspend transmission of the SRS, or reduce the power of transmissions using the PUCCH resources. Similarly, after transmitting the UPLI indicating SRS resources are to be reallocated the BS may receive the SRS from the eMBB UE and decode the scheduled URLLC transmission based at least in part on the effect of the received SRS on the scheduled URLLC transmission. For instance, the BS may cancel out the received SRS to decode the scheduled URLLC transmission. In certain aspects, the scheduled URLLC transmissions may not use the SRS resources of the eMBB UEs that are included in the RUR. That is, even though the RUR may include SRS resources, these resources may not be reallocated to URLLC transmissions.

In certain aspects, the RUR may include or exclude other reference signal resources such as demodulation reference signals (DMRS), channel state information reference signals (CSIRS), and phase-tracking reference signals (PTRS). The RUR may include or exclude other physical-layer channels such as physical random access channels (PRACH) and physical broadcast channels (PBCH). The RUR may include or exclude synchronization signal resource blocks (SSB). In certain aspects, the resources used by reference signals, physical channels, and synchronization signals of eMBB UEs as exemplified above may or may not be reallocated to the URLLC transmissions, even when the resources are included in the RUR.

In certain aspects, the RUR may include the resources of reference signals, physical channels, and synchronization signals as previously described with respect to <FIG>, but these resources are not to be reallocated to URLLC transmissions based on certain predefined rules or radio resource control (RRC) configurations. In this case, the resource allocation of URLLC transmissions may be rate-matched around those resources. In certain aspects, the resources of reference signals, physical channels, and synchronization signals may be possible to be reallocated to URLLC transmissions based on certain predefined rules or radio resource control (RRC) configurations. In this case, the URLLC transmissions may reuse those resources regardless of whether eMBB UEs continue, suspend, or power control transmissions on those resources.

In certain aspects, the UE may assume the preemption gap applies to adjacent resources in the RUR. That is, taking one or more actions at <NUM> may include applying the one or more actions as described herein to a resource that is adjacent to one or more resources identified in the ULPI. For example, <FIG> illustrates a diagram of an example bitmap <NUM>, in accordance with certain aspects of the present disclosure. As shown, the ULPI <NUM> provides a bitmap <NUM> that identifies resources <NUM> as being preempted by the reallocated resources. The UE may assume that the lower subband <NUM> adjacent to one of the identified resources <NUM> is also preempted and take one or more actions based on this assumption as described herein.

In certain cases, the ULPI may trigger a preemption gap in a UE's PUSCH transmission, for example, as the UE takes one or more actions based on the identified resources by suspending transmissions as indicated by the RUR. If the UE can preserve the phase continuity across the preemption gap, the BS may decode the received uplink signals having the preemption gap between. That is, the BS decodes the received signals if the UE is capable of preserving phase continuity across the preemption gap.

In cases where the UE is not capable of maintaining the phase continuity, the UE may transmit a demodulation reference signal (DMRS) before and after the preemption gap. For example, <FIG> depicts a diagram of an example PUSCH transmission, in accordance with certain aspects of the present disclosure. As shown, the PUSCH transmission <NUM> has a preemption gap splitting the transmission into two blocks of data. Not yet aware of the URLLC reallocation, the UE may initially transmit a DMRS <NUM> to enable the BS to decode the PUSCH transmission based on the received DMRS. As the UE is transmitting, the UE may receive the ULPI, which triggers a preemption gap <NUM> in the transmission as described herein with respect to operations <NUM>. As the UE is incapable of maintaining phase continuity, the UE may or may not resume the PUSCH transmission partly based on whether a second DMRS <NUM> is to be transmitted after the preemption gap.

In certain aspects, the ULPI may puncture the DMRS. That is, the ULPI may identify resources to be reallocated that coincide with the UE's transmission of the DMRS. In such a situation, the BS may determine not to decode at least a portion of the received signals based on a determination that the preemption gap punctures an expected DMRS. In cases where the preemption gap punctures the first DMRS (e.g., DMRS <NUM>), the BS may determine to drop the entire slot of uplink data. In cases where the preemption gap punctures the second DMRS (e.g., DMRS <NUM>), the BS may determine to drop the second block of data after the expected DMRS. A DMRS may be punctured if one or more symbols of the DMRS are punctured.

In certain aspects, the ULPI may identify semi-persistently scheduled (SPS) resources to be reallocated for URLLC. The SPS resources are periodic and may be hopped in the frequency domain. <FIG> illustrates a diagram of an example uplink channel <NUM> having SPS resources, in accordance with certain aspects of the present disclosure. As shown, the uplink channel <NUM> includes deactivated SPS resources <NUM> and activated SPS resources <NUM>. In the first slot, a UE is dynamically scheduled with PUSCH resources <NUM> that use the deactivated SPS resources. In the second slot, the PUSCH resources <NUM> overlap with activated SPS resources <NUM> triggering a preemption gap <NUM>. The BS may transmit a ULPI that identifies the SPS resources to be activated and reallocated for URLLCs. The UE may then rate match around the activated SPS resources. In certain aspects, the BS may signal an uplink grant of the PUSCH resources to the UE that excludes the SPS resources (e.g., PUSCH resources <NUM>). The ULPI for SPS resources may be a bitmap that identifies one or more activated SPS resources, a status of the SPS resources (e.g., activated or deactivated), or a change of status of the SPS resources (e.g., from activated to deactivated and vice versa).

In certain aspects, the ULPI may include cross-carrier information. That is, the ULPI identifies resources corresponding to more than one component carrier. This enables the RAN to reduce the payload size of ULPIs and have a more compact ULPI format that service more than one component carrier. For example, up to <NUM> component carriers are supported in certain systems, resulting in a maximum payload size of <NUM> bits if <NUM> bits are provided in each ULPI representing each of the <NUM> component carriers. A ULPI payload of <NUM> bits may be too large to be included as part of a DCI message. Cross-carrier ULPIs can reduce the payload to indicate uplink preemption across more than one component carrier.

As an example of a cross-carrier ULPI, <FIG> illustrates a diagram of a bitmap <NUM> having cross-carrier information, in accordance with certain aspects of the present disclosure. As shown, the ULPI <NUM> provides a bitmap <NUM> having <NUM> bits that correspond to more than one component carrier. The seven most significant bits may correspond to component carrier <NUM>, and the seven least significant bits may correspond to the other component carrier <NUM>. That is, the bitmap has two (<NUM>, <NUM>) bitmaps for the (M, N) notation, where M provides the number of columns, i.e., symbols, of the RUR, and N provides the number of rows of the RUR, i.e., N indicates whether the bitmaps is wideband or subband. Each bit may correspond to one or more OFDM symbols and a wideband resource. In this example, the bitmap <NUM> identifies bits <NUM> and <NUM> as being reallocated in the different component carriers <NUM> and <NUM>.

In certain aspects, each bit of the cross-carrier ULPI may correspond to more than one component carrier. For example, <FIG> depicts a diagram of a bitmap <NUM> having cross-carrier information, in accordance with certain aspects of the present disclosure. As shown, the ULPI <NUM> provides a bitmap <NUM> having <NUM> bits (M=<NUM>, N=<NUM>), where each bit corresponds to more than one component carrier. In this example, the UE may treat bit <NUM> as identifying both respective resources in component carriers <NUM> and <NUM> as being reallocated, even if only the resource of component carrier <NUM> is being reallocated for bit <NUM>. That is, the UE may assume both resources in the component carriers <NUM> and <NUM> are being reallocated regardless of whether the resources are actually reallocated.

In certain aspects, the RAN may signal to an eMBB UE that downlink resources were reallocated to URLLC transmissions via a downlink preemption indication (DLPI). The DLPI may identify downlink resources that were reallocated in the past. That is, the DLPI may indicate to the UE to discard signals received via the identified resources in the reference downlink region (RDR). Similar to the ULPI previously discussed, the DLPI may also include cross-carrier information, which enables the RAN to service multiple component carriers or bandwidth parts for downlink preemption with a reduced payload.

Aspects presented herein provide techniques for signaling a downlink preemption indication (DLPI) to a UE of a first type (e.g., eMBB UE) to reallocate downlink channel resources to a UE of a second type (e.g., URLLC UE).

<FIG> is a flow diagram illustrating example operations <NUM> that may be performed, for example, by a base station and/or radio access network (e.g., BS <NUM> of <FIG>), for implementing a downlink preemption indication (DLPI), in accordance with certain aspects of the present disclosure. 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.

Operations <NUM> may begin, at <NUM>, by the BS determining that resources allocated for a transmission to a first UE (e.g., URLLC UE) of a first type overlap with downlink channel resources allocated to a second UE of a second type (e.g., eMBB UE). At <NUM>, the BS signals, based on the determination at <NUM>, a downlink preemption indication (DLPI), to the second UE, that comprises cross-carrier information and identifies at least some of the overlapping resources.

Operations <NUM> may begin, at <NUM>, by the UE receiving a downlink signal from a base station (BS) using one or more downlink channel resources allocated to the a UE of a first type (e.g., eMBB UE). At <NUM>, the first UE receives a downlink preemption indication (DLPI) comprising cross-carrier information from the BS. At <NUM>, the first UE takes one or more actions based on one or more resources identified in the DLPI, wherein the one or more resources overlap with resources allocated for a scheduled transmission to a second UE of a second type (e.g., URLLC UE). For example, the UE may discard signals received by the identified resources during the scheduled transmission as those signals may be contaminated with URLLC interference.

In certain aspects, the DLPI may include cross-carrier information, which may be formed similar to the cross-carrier information previously discussed for the DLPI of <FIG>. For example, <FIG> illustrates a diagram of a bitmap <NUM> having cross-carrier information, in accordance with certain aspects of the present disclosure. As shown, the DLPI <NUM> provides a bitmap <NUM> having <NUM> bits that correspond to more than one component carrier. The seven most significant bits may correspond to component carrier <NUM>, and the seven least significant bits may correspond to the other component carrier <NUM>. That is, the bitmap includes two (M=<NUM>, N=<NUM>) bitmaps as described herein with respect to <FIG>. Each bit may correspond to one or more OFDM symbols and a wideband resource. In this example, the bitmap <NUM> identifies bits <NUM> and <NUM> as being reallocated in the different component carriers <NUM> and <NUM>.

In certain aspects, each bit of the cross-carrier DLPI may correspond to more than one component carrier similar to the bitmap of <FIG>. For example, <FIG> depicts a diagram of a bitmap <NUM> having cross-carrier information, in accordance with certain aspects of the present disclosure. As shown, the DLPI <NUM> provides a bitmap <NUM> having <NUM> bits (M=<NUM>, N=<NUM>), where each bit corresponds to more than one component carrier. In this example, the UE may treat bit <NUM> as identifying the respective resources in component carriers <NUM> and <NUM> as being reallocated, regardless of whether the resources are actually reallocated.

In certain aspects, the DLPI may be broadcast to more than UE having the same carrier indicator field (CIF). That is, the DLPI may be exclusive to a specific value of the CIF assigned to one or more UEs. The CIF may provide a basis for identifying the reference downlink region in the DLPI. That is, the RDR may be relative to the CIF assigned to a UE. In certain aspects, the DLPI may be exclusive to a UE having a specific value of the CIF. That is, the DLPI may be applicable to a single UE and its CIF.

In certain aspects, the cross-carrier DLPI may include multiple distinct DLPI bitmaps, each of which applies to one or more UEs having the same CIF, i.e., the same cross-carrier configuration. UEs having a specific value of CIF may be provided and/or preconfigured with an indication that allows the UEs to locate its DLPI bitmap in the cross-carrier DLPI.

Each bit of the DLPI bitmap may represent various resource parameters. A bit of the bitmap may correspond to a wideband resource, a subband resource, or one or more OFDM symbols of a RDR as described herein with respect to <FIG>. The DLPI may also employ the same TDD techniques described herein with respect to <FIG>.

<FIG> illustrates a wireless 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 one or more of <FIG>, <FIG>. The transceiver <NUM> is configured to transmit and receive signals for the communications device <NUM> via an antenna <NUM>, such as the various signals described herein.

The processing system <NUM> includes one or more processors <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 computer-executable instructions that when executed by processor <NUM>, cause the processor <NUM> to perform the operations illustrated in one or more of <FIG>, <FIG>, or other operations for performing the various techniques discussed herein.

In certain aspects, the processing system <NUM> further includes a receive component <NUM> for performing the receiving operations illustrated in one or more of <FIG>, <FIG>. Additionally, the processing system <NUM> includes a transmit component <NUM> for performing the transmitting operations illustrated in one or more of <FIG>, <FIG>. Further, the processing system <NUM> includes a performing component <NUM> for performing the performing operations illustrated in one or more of <FIG>, <FIG>. Also, the processing system <NUM> includes a determining component <NUM> for performing the determining operations illustrated in one or more of <FIG>, <FIG>. The receive component <NUM>, transmit component <NUM>, performing component <NUM>, and determining component <NUM> may be coupled to the processor <NUM> via bus <NUM>. The processor <NUM> may obtain or output signals via the bus <NUM> for performing the operations illustrated in one or more of <FIG>, <FIG>. In certain aspects, the receive component <NUM>, transmit component <NUM>, performing component <NUM>, and determining component <NUM> may be hardware circuits. In certain aspects, the receive component <NUM>, transmit component <NUM>, performing component <NUM>, and determining component <NUM> may be software components that are executed and run on processor <NUM>.

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 carrier component, reducing the signaling overhead to preempt resources as described herein.

Unless specifically stated otherwise, the term "some" refers to one or more.

For example, means for transmitting (or means for outputting for transmission) or means for signaling may comprise an antenna(s) <NUM> of the base station <NUM> or the antenna(s) <NUM> of the user equipment <NUM> illustrated in <FIG>. Means for receiving (or means for obtaining) may comprise an antenna(s) <NUM> of the base station <NUM> or antenna(s) <NUM> of the user equipment <NUM> illustrated in <FIG>. Means for processing, means for obtaining, means for determining, means for taking one or more actions, or means for identifying may comprise a processing system, which may include one or more processors, such as the MIMO detector <NUM>, the TX MIMO processor <NUM>, the TX processor <NUM>, and/or the controller <NUM> of the base station <NUM> or the MIMO detector <NUM>, the TX MIMO processor <NUM>, the TX processor <NUM>, and/or the controller <NUM> of the user equipment <NUM> illustrated in <FIG>.

In some cases, rather than actually transmitting a signal, a device may have an interface to output a signal for transmission (a means for outputting). For example, a processor may output a signal, via a bus interface, to a radio frequency (RF) front end for transmission. Similarly, rather than actually receiving a signal, a device may have an interface to obtain a signal received from another device (a means for obtaining). For example, a processor may obtain (or receive) a signal, via a bus interface, from an RF front end for reception. In some cases, an interface to output a signal for transmission and an interface for obtaining a signal may be integrated as a single interface.

As used herein, the terms "transmitting" and "receiving" encompass a wide variety of actions. For example, "transmitting" may include outputting (e.g., outputting a signal to be transmitted), signaling, and the like. Also, "receiving" may include obtaining (e.g., obtaining a signal), accessing (e.g., accessing data in a memory), sampling (e.g., sampling a signal), and the like.

In the case of a user equipement <NUM> (see <FIG>), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus.

Claim 1:
A method for wireless communication by a first user equipment, UE (<NUM>), comprising:
signaling (<NUM>) an uplink signal to a base station, BS (<NUM>), via uplink channel resources allocated to the first UE of a first type;
receiving (<NUM>) an uplink preemption indication, ULPI, from the BS,
wherein the ULPI comprises a bitmap identifying one or more resources to be used during a scheduled transmission,
wherein a bit of the bitmap corresponds to at least one of a wideband resource of a reference uplink region, RUR, a subband resource of the RUR, or one or more symbols of the RUR, the RUR being part of scheduled resources; and
taking (<NUM>) one or more actions based on the one or more resources identified in the ULPI, wherein the one or more resources overlap with resources allocated for a scheduled transmission by a second UE of a second type.