Timeline for intra-user equipment (UE) channel multiplexing and cancellation

A method for wireless communications performed by a user equipment (UE) includes receiving a low priority (LP) grant for scheduling an LP uplink transmission in a slot. The LP uplink transmission may overlap a set of high priority (HP) uplink transmissions in the slot. The method also includes determining an uplink shared channel preparation time as a function of a subcarrier spacing (SCS) configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. The method further includes determining a time period until an expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on a corresponding HP grant, the time period being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. The method also includes canceling the LP uplink transmission before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communications, and more particularly to techniques and apparatuses for intra-user equipment (UE) channel multiplexing and cancellation.

BACKGROUND

A wireless communications network may include a number of base stations (BSs) that can support communications for a number of user equipment (UEs). A user equipment (UE) may communicate with a base station (BS) via the downlink and uplink. The downlink (or forward link) refers to the communications link from the BS to the UE, and the uplink (or reverse link) refers to the communications link from the UE to the BS. As will be described in more detail, a BS may be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit and receive point (TRP), a new radio (NR) BS, a 5G Node B, and/or the like.

SUMMARY

In one aspect of the present disclosure, a method for wireless communication by a user equipment (UE) includes receiving a low priority (LP) grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of high priority (HP) uplink transmissions in the slot. The method further includes determining an uplink shared channel preparation time as a function of a subcarrier spacing (SCS) configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. The method still further includes determining a time period until an expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on a corresponding HP grant, the time period being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. The method also includes canceling the LP uplink transmission before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

Another aspect of the present disclosure is directed to an apparatus for wireless communication at a UE. The apparatus includes means for receiving an LP grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of HP uplink transmissions in the slot. The apparatus further includes means for determining an uplink shared channel preparation time as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. The apparatus still further includes means for determining a time period until an expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on a corresponding HP grant, the time period being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. The apparatus also includes means for canceling the LP uplink transmission before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

In another aspect of the present disclosure, a non-transitory computer-readable medium with non-transitory program code recorded thereon for wireless communication at a UE is disclosed. The program code is executed by a processor and includes program code to receive an LP grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of HP uplink transmissions in the slot. The program code further includes program code to determine an uplink shared channel preparation time as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. The program code still further includes program code to determine a time period until an expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on a corresponding HP grant, the time period being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. The program code also includes program code to cancel the LP uplink transmission before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

Another aspect of the present disclosure is directed to an apparatus for wireless communication at a UE, the apparatus includes a processor, and a memory communicatively coupled with the processor and storing instructions that, when executed by the processor, cause the apparatus to receive an LP grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of HP uplink transmissions in the slot. Execution of the instructions also cause the apparatus to determine an uplink shared channel preparation time as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. Execution of the instructions further cause the apparatus to determine a time period until an expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on a corresponding HP grant, the time period being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. Execution of the instructions still further cause the apparatus to cancel the LP uplink transmission before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

In one aspect of the present disclosure, a method for wireless communication by a base station includes transmitting, to a user equipment UE, an LP grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of HP uplink transmissions in the slot. The method further includes determining an uplink shared channel preparation time of the UE as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. The method still further includes determining an earliest transmission time for scheduling each respective HP uplink transmission of the set of HP uplink transmissions based on a corresponding HP grant, the earliest transmission time being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. The method also includes receiving, from the UE, the LP uplink transmission based on the LP grant, the LP uplink transmission cancelled before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

Another aspect of the present disclosure is directed to an apparatus for wireless communication at a base station. The apparatus includes means for transmitting, to a user equipment UE, an LP grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of HP uplink transmissions in the slot. The apparatus further includes means for determining an uplink shared channel preparation time of the UE as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. The apparatus still further includes means for determining an earliest transmission time for scheduling each respective HP uplink transmission of the set of HP uplink transmissions based on a corresponding HP grant, the earliest transmission time being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. The apparatus also includes means for receiving, from the UE, the LP uplink transmission based on the LP grant, the LP uplink transmission cancelled before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

In another aspect of the present disclosure, a non-transitory computer-readable medium with non-transitory program code recorded thereon for wireless communication at a base station is disclosed. The program code is executed by a processor and includes program code to transmit, to a user equipment UE, an LP grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of HP uplink transmissions in the slot. The program code further includes program code to determine an uplink shared channel preparation time of the UE as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. The program code still further includes program code to determine an earliest transmission time for scheduling each respective HP uplink transmission of the set of HP uplink transmissions based on a corresponding HP grant, the earliest transmission time being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. The program code also includes program code to receive, from the UE, the LP uplink transmission based on the LP grant, the LP uplink transmission cancelled before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

Another aspect of the present disclosure is directed to an apparatus having a memory and one or more processors coupled to the memory. The processor(s) is configured to transmit, to a user equipment UE, an LP grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of HP uplink transmissions in the slot. The processor(s) is further configured to determine an uplink shared channel preparation time of the UE as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. The processor(s) is still further configured to determine an earliest transmission time for scheduling each respective HP uplink transmission of the set of HP uplink transmissions based on a corresponding HP grant, the earliest transmission time being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. The processor(s) is also configured to receive, from the UE, the LP uplink transmission based on the LP grant, the LP uplink transmission cancelled before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth. In addition, the scope of the disclosure is intended to cover such an apparatus or method, which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth. It should be understood that any aspect of the disclosure disclosed may be embodied by one or more elements of a claim.

It should be noted that while aspects may be described using terminology commonly associated with 5G and later wireless technologies, aspects of the present disclosure can be applied in other generation-based communications systems, such as and including 3G and/or 4G technologies.

Wireless communication systems, such as new radio (NR) access (e.g., 5G technology), may support various wireless communications services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or beyond), millimeter wave (mmWave) targeting high carrier frequency (e.g., 25 GHz or beyond), massive machine-type communications (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC). The described services may include quality of service (QoS) specifications, such as latency and reliability requirements. Different transmission time intervals (TTIs) may be specified to satisfy the respective QoS specifications. In addition, the described services may co-exist in the same subframe.

In some examples, a UE may dynamically multiplex different services, such as eMBB and URLLC, in a same time-frequency resource to improve spectrum use. Some wireless standards, such as NR Release-16 and beyond, may support intra-UE multiplexing and cancellation for uplink channels. In some examples, a UE may multiplex payloads of colliding uplink channels if the colliding uplink channels have a same priority. As an example, a physical uplink control channel (PUCCH) may collide with another PUCCH of a same priority. In this example, the UE may multiplex the uplink control information (UCI) payload of the two PUCCHs, and transmit the multiplexed UCIs in one PUCCH. As another example, a physical uplink shared channel (PUSCH) may collide with another transmission, such as a PUCCH, of a same priority. In this example, the UE may piggyback the UCI of the PUCCH on the PUSCH transmission. Piggybacking refers to transmitting control information, such as the UCI, together with data in a data area of an uplink shared channel, such as the PUSCH. Piggybacking may be an example of multiplexing. In some examples, a UE may multiplex (e.g., piggyback) eMBB services, such as multiplexing eMBB UCI on an eMBB PUSCH or multiplexing the eMBB UCI on eMBB PUSCH. Aspects of the present disclosure are not limited to multiplexing eMBB services, other services may be multiplexed.

In some examples, a UE may drop a channel with a lower priority if two uplink channels of different priorities collide. The priority may be defined in a physical layer. For example, if an eMBB uplink channel has a higher priority than a URLLC uplink channel, the UE may drop the URLLC uplink channel that collides with the eMBB uplink channel.

As described, a UE may mitigate collisions between a low priority uplink channel and a high priority uplink channel by dropping the low priority uplink channel. In some examples, a low priority uplink channel may collide with two or more high priority uplink channels. Aspects of the present disclosure are directed to cancelling a low priority (LP) channel colliding with two or more high priority (HP) uplink channels. Some aspects of the present disclose are also directed to multiplexing two or more HP uplink channels. Additionally, some aspects of the present disclosure are directed determining an expected transmission time for respective HP uplink channels based on an LP channel colliding with two or more HP uplink channels.

As an example, the BSs110(shown as BS110a, BS110b, BS110c, and BS110d) and the core network130may exchange communications via backhaul links132(e.g., S1, etc.). Base stations110may communicate with one another over other backhaul links (e.g., X2, etc.) either directly or indirectly (e.g., through core network130). The UEs120(e.g.,120a,120b,120c) may communicate with the core network130through a communications link135.

The core network130may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. One or more of the base stations110or access node controllers (ANCs) may interface with the core network130through backhaul links132(e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communications with the UEs120. In some configurations, various functions of each access network entity or base station110may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., a base station110).

One or more UEs120may establish a protocol data unit (PDU) session for a network slice. In some cases, the UE120may select a network slice based on an application or subscription service. By having different network slices serving different applications or subscriptions, the UE120may improve its resource utilization in the wireless network100, while also satisfying performance specifications of individual applications of the UE120. In some cases, the network slices used by UE120may be served by an AMF (not shown inFIG.1) associated with one or both of the base station110or core network130. In addition, session management of the network slices may be performed by a session management function (SMF).

The BSs110(e.g., BSs110a,110b,110c,110d) may include a UE timeline module138. For ease of explanation, only one BS110ais shown as including the UE timeline module138. The UE timeline module138may be a component of each BS110. The UE timeline module138may work in conjunction with one or more components of the BS110. The UE timeline module138may transmit, to a user equipment UE, an LP grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of HP uplink transmissions in the slot. The UE timeline module138may also determine an uplink shared channel preparation time of the UE as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. The UE timeline module138may further determine an earliest transmission time for scheduling each respective HP uplink transmission of the set of HP uplink transmissions based on a corresponding HP grant, the earliest transmission time being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. The UE timeline module138may still further receive, from the UE, the LP uplink transmission based on the LP grant, the LP uplink transmission cancelled before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

The UEs120(e.g., UEs120a,120b,120c,120d,120e) may include an uplink timeline module140. For ease of explanation, only one UE120dis shown as including the uplink timeline module140. The uplink timeline module140may be a component of each UE120. The uplink timeline module140may receive an LP grant for scheduling an LP uplink transmission in a slot. The uplink timeline module140may also determine an uplink shared channel preparation time as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. The uplink timeline module140may further determine a time period until an expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on a corresponding HP grant. The uplink timeline module140may further cancel the LP uplink transmission before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

In some aspects, two or more UEs120(e.g., shown as UE120aand UE120e) may communicate directly using one or more sidelink channels (e.g., without using a base station110as an intermediary to communicate with one another). For example, the UEs120may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, and/or the like), a mesh network, and/or the like. In this case, the UE120may perform scheduling operations, resource selection operations, and/or other operations described elsewhere as being performed by the base station110. For example, the base station110may configure a UE120via downlink control information (DCI), radio resource control (RRC) signaling, a media access control-control element (MAC-CE) or via system information (e.g., a system information block (SIB).

As indicated above,FIG.1is provided merely as an example. Other examples may differ from what is described with regard toFIG.1.

FIG.2shows a block diagram of a design200of the base station110and UE120, which may be one of the base stations and one of the UEs inFIG.1. The base station110may be equipped with T antennas234athrough234t, and UE120may be equipped with R antennas252athrough252r, where in general T≥1 and R≥1.

At the UE120, antennas252athrough252rmay receive the downlink signals from the base station110and/or other base stations and may provide received signals to demodulators (DEMODs)254athrough254r, respectively. Each demodulator254may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator254may further process the input samples (e.g., for OFDM and/or the like) to obtain received symbols. A MIMO detector256may obtain received symbols from all R demodulators254athrough254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor258may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE120to a data sink260, and provide decoded control information and system information to a controller/processor280. A channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), and/or the like. In some aspects, one or more components of the UE120may be included in a housing.

On the uplink, at the UE120, a transmit processor264may receive and process data from a data source262and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) from the controller/processor280. Transmit processor264may also generate reference symbols for one or more reference signals. The symbols from the transmit processor264may be precoded by a TX MIMO processor266if applicable, further processed by modulators254athrough254r(e.g., for DFT-s-OFDM, CP-OFDM, and/or the like), and transmitted to the base station110. At the base station110, the uplink signals from the UE120and other UEs may be received by the antennas234, processed by the demodulators254, detected by a MIMO detector236if applicable, and further processed by a receive processor238to obtain decoded data and control information sent by the UE120. The receive processor238may provide the decoded data to a data sink239and the decoded control information to a controller/processor240. The base station110may include communications unit244and communicate to the core network130via the communications unit244. The core network130may include a communications unit294, a controller/processor290, and a memory292.

The controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform one or more techniques associated with canceling an LP uplink transmission before an initial symbol of an HP uplink transmission overlaps the LP uplink transmission, as described in more detail elsewhere. For example, the controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform or direct operations of, for example, the processes ofFIGS.6-7and/or other processes as described. Memories242and282may store data and program codes for the base station110and UE120, respectively. A scheduler246may schedule UEs for data transmission on the downlink and/or uplink.

In some aspects, the UEs120may include means for receiving an LP grant for scheduling an LP uplink transmission in a slot; means for determining an uplink shared channel preparation time as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions; means for determining a time period until an expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on a corresponding HP grant; and means for canceling the LP uplink transmission before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

In some aspects, a BSs110may include means for transmitting, to a user equipment UE, an LP grant for scheduling an LP uplink transmission in a slot; means for determining an uplink shared channel preparation time of the UE as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions; means for determining an earliest transmission time for scheduling each respective HP uplink transmission of the set of HP uplink transmissions based on a corresponding HP grant; means for receiving, from the UE, the LP uplink transmission based on the LP grant.

As indicated above,FIG.2is provided merely as an example. Other examples may differ from what is described with regard toFIG.2.

Wireless communication systems, such as new radio (NR) access (e.g., 5G technology), may support various wireless communications services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or beyond), millimeter wave (mmWave) targeting high carrier frequency (e.g., 25 GHz or beyond), massive machine-type communications (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC). The described services may include quality of service (QoS) specifications, such as latency and reliability requirements. Different transmission time intervals (TTIs) may be specified to satisfy the respective QoS specifications. In addition, the described services may co-exist in the same subframe.

In some examples, a UE may dynamically multiplex different services, such as eMBB and URLLC, in a same time-frequency resource to improve spectrum use. Some wireless standards, such as NR Release-16 and beyond, may support intra-UE multiplexing and cancellation for uplink channels. In some examples, a UE may multiplex payloads of colliding uplink channels if the colliding uplink channels have a same priority. As an example, a physical uplink control channel (PUCCH) may collide with another PUCCH of a same priority. In this example, the UE may multiplex the uplink control information (UCI) payload of the two PUCCHs, and transmit the multiplexed UCIs in one PUCCH. As another example, a physical uplink shared channel (PUSCH) may collide with another PUSCH of a same priority. In this example, the UE may piggyback the UCI of the PUCCH on the PUSCH transmission. Piggybacking refers to transmitting control information, such as the UCI, together with data in a data area of an uplink shared channel, such as the PUSCH. Piggybacking may be an example of multiplexing. In some examples, a UE may multiplex (e.g., piggyback) eMBB services, such as multiplexing eMBB UCI on an eMBB PUSCH or multiplexing the eMBB UCI on eMBB PUSCH. Aspects of the present disclosure are not limited to multiplexing eMBB services, other services may be multiplexed.

In some examples, a UE may drop a channel with a lower priority if two uplink channels of different priorities collide. The priority may be defined in a physical layer. For example, if an eMBB uplink channel has a higher priority than a URLLC uplink channel, the UE may drop the URLLC uplink channel that collides with the eMBB uplink channel.

As described, a UE may mitigate collisions between a low priority uplink channel and a high priority uplink channel by dropping the low priority uplink channel. In some examples, a low priority uplink channel may collide with two or more high priority uplink channels. Aspects of the present disclosure are directed to cancelling a low priority (LP) channel colliding with two or more high priority (HP) uplink channels. Some aspects of the present discloser are also directed to multiplexing two or more HP uplink channels. Additionally, some aspects of the present disclosure are directed determining an expected transmission time for respective HP uplink channels based on an LP channel colliding with two or more HP uplink channels.

In some wireless communication systems, such as NR, a base station may provide time for a UE to process an uplink transmission. A PUSCH preparation time (N2) may be an example of an uplink transmission processing time. The PUSCH preparation time may be defined as a number of OFDM symbols specified for a UE from an end of a downlink transmission, such as a physical downlink control channel (PDCCH) transmission, including a grant to an earliest possible start of an uplink transmission, such as a PUSCH transmission, scheduled based on the grant. In some examples, the PUSCH preparation time (N2) described above may be represented as an absolute time (e.g., seconds). In such examples, the PUSCH preparation time may be referred to as Tproc,2. In some examples, the PUSCH preparation time (Tproc,2) may correspond to a UE's processing capability. In general, the UE is not expected to perform an uplink transmission if the UE is not provided sufficient time for processing (e.g., as indicated by the Tproc,2value for the UE, based on the UE's processing capability).

As described, the PUSCH preparation time (Tproc,2) may be a minimum time for a UE to prepare an uplink transmission, such as a PUSCH transmission, in a wireless communication system, such as an NR system. In some examples, the PUSCH preparation time (Tproc,2) may be determined based on a subcarrier spacing (SCS) configuration (μ) and also a PUSCH preparation time (N2) of the uplink carrier on which the uplink transmission is scheduled. The SCS configuration (μ) may be determined based on an SCS configuration (μDL) of a downlink channel, such as a physical downlink control channel (PDCCH), including a grant and an SCS configuration (μUL) of an uplink transmission scheduled based on the grant.

In some wireless communication standards, such as NR communication standards, different UE processing capabilities may be defined. In some examples, the UE may have a first processing capability, referred to as Cap 1, and a second processing capability, referred to as Cap 2. Cap 2 corresponds to higher UE processing capability (e.g., faster processing time) and, thus, shorter times for the PUSCH preparation time (Tproc,2). For example, TABLES 1 and 2 provide example values for the SCS configuration (μ) and the PUSCH preparation time (N2) used for determining the PUSCH preparation time (Tproc,2) for Cap 1 and Cap 2, respectively. In TABLES 1 and 2, the values for the PUSCH preparation time (N2) represent a minimum number of symbols required for processing an uplink transmission. For example, as shown in TABLE 1, for Cap 1, if the SCS configuration (μ) is zero, then the PUSCH preparation time (N2) is ten.

A UE may be limited to performing one uplink transmission per slot. Therefore, when two or more uplink transmissions are scheduled for a same slot, the UE may multiplex two or more transmissions and/or cancel one or more transmissions. As described, an HP uplink transmission may collide with an LP uplink transmission in the same slot. The collision refers to a scenario where one uplink transmission overlaps another uplink transmission in the same slot. In some examples, the UE may mitigate a collision between the HP uplink transmission and the LP uplink transmission in the slot by cancelling the LP uplink transmission.

In some examples, an exact cancellation time may be specified for a UE to cancel an LP uplink transmission.FIG.3is a timing diagram illustrating an exemplary timeline300for a UE cancelling an LP uplink transmission304colliding with an HP uplink transmission308, in accordance with various aspects of the present disclosure. The UE (not shown inFIG.3) may be an example of a UE120as described with reference toFIGS.1and2. As shown inFIG.3, at time t1, the UE receives a first grant302scheduling an LP uplink transmission304at time t3. The first grant302may be LP downlink control information (DCI) received in a downlink control channel, such as a PDCCH. Additionally, at time t2, the UE receives a second grant306scheduling an HP uplink transmission308at time t4. The second grant306may be an example of HP DCI received in the downlink control channel.

In the example ofFIG.3, an expected transmission time for the HP uplink transmission308may be based on the PUSCH preparation time (Tproc,2) and a reported UE capability (d1). In such examples, the reported UE capability (d1) may be a time duration corresponding to 0, 1, or 2 symbols reported by the UE capability. In the example ofFIG.3, the UE expects the transmission of the HP uplink transmission308will not start before Tproc,2+d1after a last symbol of the second grant306scheduling the HP uplink transmission308. In the example ofFIG.3, Tproc,2is determined based on an assumption that a first symbol of a PUSCH allocation only includes a demodulation reference signal (DM-RS) (e.g., the DM-RS is front-loaded), such that d2,1=0.

In some examples, the UE cancels the LP uplink transmission304at Tproc,2+d1. In some other examples, the UE cancels the LP uplink transmission304before a first symbol of the HP uplink transmission308overlaps the LP uplink transmission304. In the example ofFIG.3, for exemplary purposes, the first symbol of the HP uplink transmission308overlaps the LP uplink transmission304at time t4. Therefore, in the example ofFIG.3, the UE may cancel the LP uplink transmission304any time before time t4. Additionally, in the current example, a base station (e.g., gNB) maintains at least a threshold time (Tproc,2+d1) between an ending symbol of the second grant306and a starting symbol of the HP uplink transmission308. That is, the HP uplink transmission308is not scheduled before Tproc,2+d1. The base station (not shown inFIG.3) may be an example of a base station110as described with reference toFIGS.1and2.

In some examples, two or more HP uplink transmissions may overlap an LP uplink transmission. In some implementations, an expected transmission time may be determined for one or more of the multiple HP uplink transmissions.FIG.4is a timing diagram illustrating an exemplary timeline400for a UE cancelling an LP uplink transmission406colliding with a first HP uplink transmission410and a second HP uplink transmission414, in accordance with various aspects of the present disclosure. The UE (not shown inFIG.4) may be an example of a UE120as described with reference toFIGS.1and2. As shown inFIG.4, at time t1, the UE receives an LP grant404scheduling an LP uplink transmission406at time t4. The LP grant404may be LP DCI received in a downlink control channel, such as a PDCCH. Additionally, at time t2a, the UE receives a first HP grant408scheduling a first HP uplink transmission410at time t5. Furthermore, at time t3a, the UE receives a second HP grant412scheduling a second HP uplink transmission414at time t6. The first HP grant408and the second HP grant412may be HP DCIs, respectively, and each HP grant408,412may be received in a downlink control channel, such as the PDCCH.

In the example ofFIG.4, the UE expects the base station will not schedule a transmission of an earliest scheduled HP uplink transmission, such as the first HP uplink transmission410, to start before a time period, such as Tproc,2+d1, after a last symbol of latest received HP grant, such as the second HP grant412. That is, Tproc,2+d1may be an example of a time period until an expected transmission time of an HP uplink transmission. As an example, as shown inFIG.4, the UE expects the base station will not schedule a transmission of the first HP uplink transmission410to start before Tproc,2+d1(e.g., time t5) after a last symbol of the second HP grant412. As shown inFIG.4, the last symbol of the second HP grant412occurs at time t3b. The base station (not shown inFIG.4) may be an example of a base station110as described with reference toFIGS.1and2.FIG.4is provided as an example and is not drawn to scale. In the example ofFIG.4, the UE may cancel the LP uplink transmission406before a first symbol of the first HP uplink transmission410overlaps the LP uplink transmission406. For exemplary purposes, as shown inFIG.4, the first symbol of the first HP uplink transmission410overlaps the LP uplink transmission406at time t5. Therefore, the UE may cancel the LP uplink transmission406any time before time t5.

In another implementation, the UE expects a transmission of one or more of the HP uplink transmissions410,414will not start before a time period, such as Tproc,2+d1, after a last symbol of a corresponding HP grant408,412. That is, Tproc,2+d1may be an example of a time period until an expected transmission time of an HP uplink transmission. As an example, the UE expects the transmission of the first HP uplink transmission410will not start before Tproc,2+d1after a last symbol of the first HP grant408. For exemplary purposes, the last symbol of the first HP grant408occurs at time t2b. Thus, although not shown inFIG.4, in this example, time t5corresponds to Tproc,2+d1after a last symbol of the first HP grant408. Additionally, or alternatively, the UE may expect that transmission of the second HP uplink transmission414will not start before Tproc,2+d1after a last symbol of the second HP grant412. For exemplary purposes, the last symbol of the second HP grant412occurs at time t3a. Thus, although not shown inFIG.4, in this example, time t6corresponds to Tproc,2+d1after a last symbol of the second HP grant412. As described above, the example ofFIG.4, the UE may cancel the LP uplink transmission406before a first symbol of the first HP uplink transmission410overlaps the LP uplink transmission406. In some implementations, such as the example ofFIG.4, Tproc,2may be determined based on an assumption that a first symbol of a PUSCH allocation consists of DM-RS only, such that d2,1=0.

In the example ofFIG.4, the LP uplink transmission406may be a PUSCH transmission, the first HP uplink transmission410may be a PUCCH transmission, and the second HP uplink transmission414may be a PUSCH transmission. According to aspects of the present disclosure, the UE may piggyback the UCI of the first HP uplink transmission410on the second HP uplink transmission414.FIG.4illustrates examples of two HP uplink channels overlapping an LP uplink channel. Aspects of the present disclosure are not limited to two HP uplink channels overlapping an LP uplink channel. Aspects of the present disclosure, such as the expected transmission time, as described with respect toFIG.4, and determining the processing time (e.g., Tproc,2), as described below. Aspects of the present disclosure may also contemplate scenarios in which one of the multiple HP channels overlaps the LP channel and two or more HP channels overlap each other.

According to aspects of the present disclosure, such as the aspects described with reference toFIG.4, the PUSCH preparation time (Tproc,2) may be based on a value of an SCS configuration (μ) corresponding to a smallest SCS configuration of each PDCCH (μDL) carrying a grant (e.g., DCI), such as the first HP grant408, the second HP grant412, and the LP grant404ofFIG.4, and each PUSCH or PUCCH (μUL) scheduled by a received grant, such as the LP uplink transmission406, the first HP uplink transmission410, and the second HP uplink transmission414ofFIG.4. For example, if the SCS configurations are zero, one, and two, a value of the SCS configuration (μ) for the PUSCH preparation time (Tproc,2) may be zero (e.g., the smallest SCS configuration).

Additionally, in some aspects, such as the aspects described with reference toFIG.4, the UE may consider a processing timing capability (e.g., Cap 1 or Cap 2) of all uplink transmissions, such as all HP uplink transmissions, and use a lowest capability. In some implementations, a second processing timing capability (Cap 2) may be enabled on all uplink carriers for scheduled HP uplink transmissions and scheduled LP uplink transmissions. As an example, a processing Type 2 parameter, such as processingType2Enabled parameter, may be enabled for all serving cells corresponding to the scheduled HP uplink transmissions. In such implementations, a PUSCH preparation time (N2) may correspond to a Cap 2 value. Additionally, based on the PUSCH preparation time (N2) corresponding to a Cap 2 value, a value of the SCS configuration (μ) may also correspond to a Cap 2 value. Alternatively, a first processing timing capability (Cap 1) may be enabled on one or more uplink carriers for the scheduled HP uplink transmissions. In such implementations, the PUSCH preparation time (N2) may be correspond to a Cap 1 value. In some examples, based on the PUSCH preparation time (N2) corresponding to a Cap 1 value, a value of the SCS configuration (μ) may also correspond to a Cap 1 value.

In some examples, an HP uplink transmission may be scheduled without a corresponding grant.FIG.5is a timing diagram illustrating an exemplary timeline500for a UE cancelling an LP uplink transmission506colliding with a first HP uplink transmission510and a second HP uplink transmission514, in accordance with various aspects of the present disclosure. The UE (not shown inFIG.5) may be an example of a UE120as described with reference toFIGS.1and2. As shown inFIG.5, at time t1, the UE receives, from a base station, an LP grant504scheduling an LP uplink transmission506at time t4. The LP grant504may be LP DCI received in a downlink control channel, such as a PDCCH. Additionally, at time t2a, the UE receives an HP grant512scheduling a second HP uplink transmission514at time t5. The HP grant512may be HP DCI received in a downlink control channel, such as the PDCCH. The base station (not shown inFIG.5) may be an example of a base station110as described with reference toFIGS.1and2.

In the example ofFIG.5, a first HP uplink transmission510scheduled at time t4may be an example of an uplink transmission that is scheduled without a corresponding dynamic grant, such as the HP grant512. Examples of an uplink transmission that is scheduled without a corresponding dynamic grant include, but are not limited to, type 1 or type 2 uplink configured grants, scheduling request (SR) transmissions, or hybrid automatic repeat request (HARD)-acknowledgement (ACK) reports for semi-persistent (SPS) physical downlink shared channel (PDSCH). A HARQ-ACK report for an SPS PDSCH may be an example of a HARQ-ACK report transmitted in response to a received PDSCH without a corresponding PDCCH. In one example, the first HP uplink transmission510may be a HARQ-ACK report for an SPS PDSCH.

In some examples, such as the example ofFIG.5, due to the absence of the dynamic grant, a base station may not the dynamic grant when determining an expected transmission time for the first HP uplink transmission510. Additionally, the SCS (μDL) value for the grant (μDL) of the grantless HP uplink transmission may not be considered when determining the SCS value (μ) for the Tproc,2, as described with reference toFIG.4. For ease of explanation, an HP uplink transmission that does not correspond to a grant (e.g., PDCCH) may be referred to as a grantless HP uplink transmission. In such examples, the UE may cancel the LP uplink transmission before a first symbol of a grantless HP uplink transmission overlaps the LP uplink transmission if the grantless HP uplink transmission is an earliest HP uplink transmission from a set of HP uplink transmissions scheduled in a slot. In the example ofFIG.5, the the first HP uplink transmission510is the earliest HP uplink transmission from the set of HP uplink transmissions510,514scheduled in a slot. Therefore, the UE may cancel the LP uplink transmission506before the first symbol of the first HP uplink transmission510overlaps the LP uplink transmission506at time t4. Additionally, as shown inFIG.5, the UE may expect a transmission of the second HP uplink transmission514will not start before Tproc,2+d1(e.g., before time t5) after a last symbol of the HP grant512. In the example ofFIG.5, the last symbol of the HP grant512occurs at time t2b.

As indicated above,FIGS.3,4, and5are provided as examples. Other examples may differ from what is described with respect toFIGS.3,4, and5.

FIG.6is a diagram illustrating an example process performed at a UE that supports canceling an LP uplink transmission before an initial symbol of an HP uplink transmission overlaps the LP uplink transmission, in accordance with various aspects of the present disclosure. The operations of the process600may be implemented by a UE, such as a UE120, or its components, as described with reference toFIGS.1,2,3,4, and5, respectively. For example, operations of the process600may be performed by an uplink (UL) timeline module140as described with reference toFIG.1. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the operations or functions described below. Additionally, or alternatively, a UE may perform aspects of the operations or functions described below using special-purpose hardware.

In block602, the process600may receive an LP grant for scheduling an LP uplink transmission in a slot. In some examples, such as the examples described in reference toFIGS.3-6, the LP uplink transmission overlaps a set of HP uplink transmissions in the slot. The HP uplink transmissions may include one or both of control channel (e.g., PUCCH) or data channel (e.g., PUSCH) transmissions. At block604, the process600may determine an uplink shared channel preparation time as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. As described, the uplink shared channel (e.g., PUSCH) preparation time (Tproc,2) may be a minimum time for a UE to prepare an uplink transmission, such as a PUSCH transmission, in a wireless communication system, such as an NR system. In some examples, the PUSCH preparation time (Tproc,2) may be determined based on a subcarrier spacing (SCS) configuration (μ) and also a PUSCH preparation time (N2) of the uplink carrier on which the uplink transmission is scheduled. The SCS configuration (μ) may be determined based on an SCS configuration (μDL) of a downlink channel, such as a physical downlink control channel (PDCCH), including a grant and an SCS configuration (μUL) of an uplink transmission scheduled based on the grant.

As shown inFIG.6, at block606, the process600determines a time period until an expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on a corresponding HP grant. The time period may be a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. As shown inFIG.6, at block606, the process600determines a time period until an expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on a corresponding HP grant. The time period may be a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. For example, as described with reference toFIG.3, an expected transmission time for an HP uplink transmission may be based on the PUSCH preparation time (Tproc,2) and a reported UE capability (d1). In some examples, the reported UE capability (d1) may be a time duration corresponding to 0, 1, or 2 symbols reported by the UE capability. In some implementations, the UE expects the transmission of the HP uplink transmission will not start before Tproc,2+d1after a last symbol of a grant scheduling the HP uplink transmission. In such implementations, the PUSCH preparation time (Tproc,2) may be determined based on an assumption that a first symbol of a PUSCH allocation only includes a demodulation reference signal (DM-RS) (e.g., the DM-RS is front-loaded), such that d2,1=0.

Additionally, as shown inFIG.6, at block608, the process600may cancel the LP uplink transmission before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions. For example, as described in reference toFIG.4, the LP uplink transmission406is cancelled at a time before time t5, where time t5corresponds to a time when a symbol of the LP uplink transmission overlaps the first HP uplink transmission410. In the example ofFIG.4, the first HP uplink transmission410is an earliest HP uplink transmission of the set of HP uplink transmissions410,414.

FIG.7is a diagram illustrating an example process performed at a base station that supports an LP uplink transmission being cancelled before an initial symbol of an HP uplink transmission overlaps the LP uplink transmission, in accordance with various aspects of the present disclosure. The operations of the process700may be implemented by a base station, such as a base station110, or its components, as described with reference toFIGS.1,2,3,4, and5, respectively. For example, operations of the process700may be performed by a UE timeline module138as described with reference toFIG.1. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the operations or functions described below. Additionally, or alternatively, a base station may perform aspects of the operations or functions described below using special-purpose hardware.

In block702, the process700may transmit, to a UE, an LP grant for scheduling an LP uplink transmission in a slot. The LP uplink transmission may overlap a set of HP uplink transmissions in the slot. At block704, the process700determines an uplink shared channel preparation time of the UE as a function of an SCS configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions. In some examples, the PUSCH preparation time (Tproc,2) may be determined based on a subcarrier spacing (SCS) configuration (μ) and also a PUSCH preparation time (N2) of the uplink carrier on which the uplink transmission is scheduled. The SCS configuration (μ) may be determined based on an SCS configuration (μDL) of a downlink channel, such as a physical downlink control channel (PDCCH), including a grant and an SCS configuration (μUL) of an uplink transmission scheduled based on the grant.

At block706, the process700may determine an earliest transmission time for scheduling each respective HP uplink transmission of the set of HP uplink transmissions based on a corresponding HP grant. The earliest transmission time may be a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability. For example, as described with reference toFIG.3, the earliest transmission time for an HP uplink transmission may be based on the PUSCH preparation time (Tproc,2) and a reported UE capability (d1). At block708, the process receives, from the UE, the LP uplink transmission based on the LP grant, the LP uplink transmission cancelled before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.

Implementation examples are described in the following numbered clauses:1. A method for wireless communications performed by a user equipment (UE), comprising: receiving a low priority (LP) grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of high priority (HP) uplink transmissions in the slot; determining an uplink shared channel preparation time as a function of a subcarrier spacing (SCS) configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions; determining a time period until an expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on a corresponding HP grant, the time period being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability; and canceling the LP uplink transmission before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.2. The method of Clause 1, further comprising receiving a set of high priority (HP) grants for scheduling the set of HP uplink transmissions in the slot, each respective HP grant of the set of HP grants corresponding to different HP uplink transmission of the set of HP uplink transmissions.3. The method of any of Clauses 1-2, in which the time period until the expected transmission time for each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on the corresponding HP grant is initiated after a last symbol of the corresponding HP grant.4. The method of any of Clauses 1-3, further comprising transmitting each respective HP uplink transmission of the set of HP uplink transmissions scheduled based on the corresponding HP grant no earlier than the expected transmission time.5. The method of any of Clauses 1-4, in which the SCS configuration corresponds to a smallest SCS configuration selected from one of a set of first SCS configurations, a set of second SCS configurations, a third SCS configuration, and a fourth SCS configuration.6. The method of Clause 5, in which: each first SCS configuration of the set of first SCS configurations is associated with a different HP uplink grant of a set of HP uplink grants corresponding to a set of HP uplink transmissions; and each second SCS configuration of the second SCS configurations is associated with a different HP uplink transmission of the set of HP uplink transmissions.7. The method of Clause 5, in which: the third SCS configuration is associated with the LP grant; and the fourth SCS configuration is associated with the LP uplink transmission.8. The method of any of Clauses 1-7, in which the UE processing time capability is processing time capability 2 when each HP uplink transmission of the set of HP uplink transmissions corresponds to processing time capability 2, a value of the uplink shared channel preparation time for processing time capability 2 being less than a value of the uplink shared channel preparation time for processing time capability 1.9. The method of any of Clauses 1-7, in which the UE processing time capability is processing time capability 1 when one HP uplink transmission of the set of HP uplink transmissions corresponds to processing time capability 1.10. The method of any of Clauses 1-9, in which the earliest HP uplink transmission is a grantless HP uplink transmission comprising HARQ-ACK information generated based on a downlink shared channel received without a corresponding downlink control channel.11. The method of any of Clauses 1-9, in which the earliest HP uplink transmission is a grantless HP uplink transmission comprising a scheduling request (SR).12. The method of any of Clauses 1-9, in which the earliest HP uplink transmission is a grantless HP uplink transmission generated based on a configured grant.13. The method of any of Clauses 1-12, in which the UE assumes a first symbol of the LP uplink transmission is limited to including demodulation reference signals (DM-RS).14. A method for wireless communications performed by a base station, comprising: transmitting, to a user equipment (UE), a low priority (LP) grant for scheduling an LP uplink transmission in a slot, the LP uplink transmission overlapping a set of high priority (HP) uplink transmissions in the slot; determining an uplink shared channel preparation time of the UE as a function of a subcarrier spacing (SCS) configuration and a UE processing time capability based on the LP uplink transmission overlapping the set of HP uplink transmissions; determining an earliest transmission time for scheduling each respective HP uplink transmission of the set of HP uplink transmissions based on a corresponding HP grant, the earliest transmission time being a function of the uplink shared channel preparation time and a time duration corresponding to a reported UE capability; and receiving, from the UE, the LP uplink transmission based on the LP grant, the LP uplink transmission cancelled before a symbol of the LP uplink transmission overlaps an earliest HP uplink transmission of the set of HP uplink transmissions.15. The method of Clause 14, further comprising transmitting a set of high priority (HP) grants for scheduling the set of HP uplink transmissions in the slot, each respective HP grant of the set of HP grants corresponding to different HP uplink transmission of the set of HP uplink transmissions.16. The method of any of Clauses 14-15, in which the earliest transmission time for each respective HP uplink transmission of the set of HP uplink transmissions is an end of a time period initiated after a last symbol of the corresponding HP grant.17. The method of any of Clauses 14-16, further comprising receiving each respective HP uplink transmission of the set of HP uplink transmissions no earlier than the earliest transmission time.18. The method of any of Clauses 14-17, in which the SCS configuration is a smallest SCS configuration corresponding to one of a set of first SCS configurations, a set of second SCS configurations, a third SCS configuration, and a fourth SCS configuration.19. The method of Clause 18, in which: each first SCS configuration of the set of first SCS configurations is associated with a different HP uplink grant of a set of HP uplink grants corresponding to a set of HP uplink transmissions; and each second SCS configuration of the second SCS configurations is associated with a different HP uplink transmission of the set of HP uplink transmissions.20. The method of Clause 18, in which: the third SCS configuration is associated with the LP uplink grant; and the fourth SCS configuration is associated with the LP uplink transmission.21. The method of any of Clauses 14-20, in which the UE processing time capability is processing time capability 2 when each HP uplink transmission of the set of HP uplink transmissions corresponds to processing time capability 2, a value of the uplink shared channel preparation time for processing time capability 2 being less than a value of the uplink shared channel preparation time for processing time capability 1.22. The method of any of Clauses 14-20, in which the UE processing time capability is processing time capability 1 when one HP uplink transmission of the set of HP uplink transmissions corresponds to processing time capability 1.23. The method of any of Clauses 14-22, in which the earliest HP uplink transmission is a grantless HP uplink transmission comprising HARQ-ACK information generated based on a downlink shared channel transmitted without a corresponding downlink control channel.24. The method of any of Clauses 14-22, in which the earliest HP uplink transmission is a grantless HP uplink transmission comprising a scheduling request (SR).25. The method of any of Clauses 14-22, in which the earliest HP uplink transmission is a grantless HP uplink transmission generated based on a configured grant.

As used, the term “component” is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software. As used, a processor is implemented in hardware, firmware, and/or a combination of hardware and software.