Patent Description:
The following relates generally to wireless communications, and more specifically to uplink collision handling for a wireless communication system and service types such as ultra-reliable low-latency communications (URLLC) and enhanced mobile broadband (eMBB) communications.

These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g.,time, frequency, and power). These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform-spread-OFDM (DFT-S-OFDM).

In some cases, transmissions on channels may collide with one another. Although scheduling may mitigate some of the collisions, scheduling may introduce latency and decrease reliability of the transmissions, which may be problematic for higher-priority transmissions, such as URLLC. Accordingly, the existing techniques may be deficient for prioritizing channel transmissions that require low-latency or high reliability for multiple services. D1: <NPL>describes remaining issues on UL data transmission for URLLC.

D2: <NPL>describes handling UCI on PUSCH for URLLC.

D3: <NPL>describes handling UL multiplexing of transmissions with different reliability requirements.

Further examples are provided in the description to aid with understanding. The described techniques may provide methods for prioritizing transmissions in the event of overlapping transmissions and to decrease latency and improve reliability of transmissions for different types of communication services.

A method of wireless communication at a UE is described. The method comprising: identifying that the UE is scheduled to transmit on a first channel associated with a first service type; identifying that the UE is scheduled to transmit on a second channel associated with a second service type, and that the second channel is scheduled to at least partially overlap with the first channel; determining that one of the first channel or the second channel is a higher priority channel based at least in part on respective priorities of the first service type and the second service type; determining that the UE supports simultaneous transmission of partially overlapping channels and that the UE is power-limited; transmitting a message on the higher priority channel with a transmission power that is greater than other transmission powers used for other simultaneous transmission on channels that partially overlap with the higher priority channel, based at least in part on the UE being power-limited.

An apparatus for wireless communication at a UE is described wherein the apparatus comprising means configured to carry out the method indicated above.

A method of wireless communication at a base station is described. The method comprising: scheduling transmission on a first channel associated with a first service type; scheduling transmission on a second channel associated with a second service type, wherein the second channel is scheduled to at least partially overlap with the first channel and scheduling transmission on the second channel is based on a predetermined condition; and receiving a higher priority channel, wherein the higher priority channel is based at least in part on respective priorities of the first service type and the second service type determined by the UE, and wherein the higher priority channel is received with a transmission power that is greater than other transmission powers used for other simultaneous transmissions on channels that partially overlap with the higher priority channel based at least in part on the UE being power-limited.

An apparatus for wireless communication at a base station is described wherein the apparatus comprising means configured to carry out the method indicated above.

In some cases, wireless communication systems may schedule communication resources to support both uplink and downlink transmissions. For example, a wireless communication system may allocate a set of resources to uplink transmissions. In one example, a base station may schedule overlapping transmissions on multiple channels. Once the user equipment (UE) transmits or uplinks to the base station, a collision may result as a result of the transmissions and/or channels overlapping one another. Anticipating that collisions may sometimes occur, rules have been developed to provide guidance for how to handle certain transmissions in the event of a collision. One example set of rules includes a set of rules for handling the transmission of uplink control information (UCI), referred to herein as one or more UCI multiplexing rules. However, the UCI multiplexing rules generally only apply if certain conditions are first met. If the conditions are not met, the rules would normally not apply, and an error condition may result. For example, in the case that just one pair of overlapping channels does not meet timeline requirements of the UCI multiplexing rules, the UE may designate the uplink transmission as an error case for all uplink channels in the group of overlapping channels and the UE behavior may not be specified. This could result in additional latency or delay for transmissions associated with a service type that calls for low latency and/or high reliability, as these transmissions may also be dropped. Thus, even though the UCI multiplexing rule is intended to avoid collisions through scheduling, this method may actually increase latency for some channels.

In one solution, UCI multiplexing may be applied even when the Conditions of the UCI multiplexing rules are not met. UCI multiplexing may be applied on priority channels (for example, ultra-reliable, low-latency communications (URLLC) channels). Transmissions on lower priority channels may be dropped. Thus, a UE may determine a priority of the overlapping channels, and then communicate on the highest priority channel(s). The UE may do so outside of a UCI multiplexing context, and may apply prioritization rules, based on service type, for example, to various situations where uplink transmissions overlap. If the overlapping channels have the same priority, the timeline requirements must be met for UCI multiplexing, or the result is an error case. Across different priorities, however, the timeline does not need to be satisfied.

Aspects of the disclosure are initially described in the context of a wireless communications system. Aspects of the disclosure are further illustrated by timelines implemented by a communications system. Aspects of the disclosure are further illustrated by and described with reference to control channel configurations, apparatus diagrams, system diagrams, and flowcharts that relate to uplink collision handling for wireless communication systems.

<FIG> illustrates an example of a wireless communications system <NUM> that supports uplink collision handling for a wireless communication system in accordance with aspects of the present disclosure. The wireless communications system <NUM> includes base stations <NUM>, UEs <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, wireless communications system <NUM> may support enhanced broadband communications, ultra-reliable (e.g.,mission critical) communications, low latency communications, or communications with low-cost and low-complexity devices.

Wireless communications system <NUM> may include base stations <NUM> of different types (e.g.,macro or small cell base stations).

The term "cell" refers to a logical communication entity used for communication with a base station <NUM> (e.g.,over a carrier), and may be associated with an identifier for distinguishing neighboring cells (e.g.,a physical cell identifier (PCID), a virtual cell identifier (VCID)) operating via the same or a different carrier. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g.,machine-type communication (MTC), narrowband Internet-of Things (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of devices. In some cases, the term "cell" may refer to a portion of a geographic coverage area <NUM> (e.g.,a sector) over which the logical entity operates.

Some UEs <NUM>, such as MTC or IoT devices, may be low cost or low complexity devices, and may provide for automated communication between machines (e.g.,via Machine-to-Machine (M2M) communication).

Some UEs <NUM> may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g.,a mode that supports one-way communication via transmission or reception, but not transmission and reception simultaneously). Other power conservation techniques for UEs <NUM> include entering a power saving "deep sleep" mode when not engaging in active communications, or operating over a limited bandwidth (e.g.,according to narrowband communications). In some cases, UEs <NUM> may be designed to support critical functions (e.g.,mission critical functions), and a wireless communications system <NUM> may be configured to provide ultra-reliable communications for these functions.

In some cases, a UE <NUM> may also be able to communicate directly with other UEs <NUM> (e.g.,using a peer-to-peer (P2P) or device-to-device (D2D) protocol).

For example, base stations <NUM> may interface with the core network <NUM> through backhaul links <NUM> (e.g.,via an S1, N2, N3, or other interface). Base stations <NUM> may communicate with one another over backhaul links <NUM> (e.g.,via an X2, Xn, or other interface) either directly (e.g.,directly between base stations <NUM>) or indirectly (e.g.,via core network <NUM>).

The MME may manage non-access stratum (e.g.,control plane) functions such as mobility, authentication, and bearer management for UEs <NUM> served by base stations <NUM> associated with the EPC.

In some configurations, various functions of each access network entity or base station <NUM> may 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 station <NUM>).

Transmission of UHF waves may be associated with smaller antennas and shorter range (e.g.,less than <NUM>) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below <NUM>.

Wireless communications system <NUM> may also operate in an extremely high frequency (EHF) region of the spectrum (e.g.,from <NUM> to <NUM>), also known as the millimeter band.

In some cases, operations in unlicensed bands may be based on a CA configuration in conjunction with CCs operating in a licensed band (e.g.,LAA).

For example, wireless communications system <NUM> may use a transmission scheme between a transmitting device (e.g.,a base station <NUM>) and a receiving device (e.g.,a UE <NUM>), where the transmitting device is equipped with multiple antennas and the receiving devices are equipped with one or more antennas. Each of the multiple signals may be referred to as a separate spatial stream, and may carry bits associated with the same data stream (e.g.,the same codeword) or different data streams.

Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g.,a base station <NUM> or a UE <NUM>) to shape or steer an antenna beam (e.g.,a transmit beam or receive beam) along a spatial path between the transmitting device and the receiving device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g.,with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

In one example, a base station <NUM> may use multiple antennas or antenna arrays to conduct beamforming operations for directional communications with a UE <NUM>. For instance, some signals (e.g. synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a base station <NUM> multiple times in different directions, which may include a signal being transmitted according to different beamforming weight sets associated with different directions of transmission. Transmissions in different beam directions may be used to identify (e.g.,by the base station <NUM> or a receiving device, such as a UE <NUM>) a beam direction for subsequent transmission and/or reception by the base station <NUM>. Some signals, such as data signals associated with a particular receiving device, may be transmitted by a base station <NUM> in a single beam direction (e.g.,a direction associated with the receiving device, such as a UE <NUM>). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based at least in in part on a signal that was transmitted in different beam directions. For example, a UE <NUM> may receive one or more of the signals transmitted by the base station <NUM> in different directions, and the UE <NUM> may report to the base station <NUM> an indication of the signal it received with a highest signal quality, or an otherwise acceptable signal quality. Although these techniques are described with reference to signals transmitted in one or more directions by a base station <NUM>, a UE <NUM> may employ similar techniques for transmitting signals multiple times in different directions (e.g.,for identifying a beam direction for subsequent transmission or reception by the UE <NUM>), or transmitting a signal in a single direction (e.g.,for transmitting data to a receiving device).

A receiving device (e.g.,a UE <NUM>, which may be an example of a mmW receiving device) may try multiple receive beams when receiving various signals from the base station <NUM>, such as synchronization signals, reference signals, beam selection signals, or other control signals. In some examples a receiving device may use a single receive beam to receive along a single beam direction (e.g.,when receiving a data signal). The single receive beam may be aligned in a beam direction determined based at least in part on listening according to different receive beam directions (e.g.,a beam direction determined to have a highest signal strength, highest signal-to-noise ratio, or otherwise acceptable signal quality based at least in part on listening according to multiple beam directions).

HARQ may include a combination of error detection (e.g.,using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g.,automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g.,signal-to-noise conditions).

A subframe may be further divided into <NUM> slots each having a duration of <NUM>, and each slot may contain <NUM> or <NUM> modulation symbol periods (e.g. depending on the length of the cyclic prefix prepended to each symbol period). In other cases, a smallest scheduling unit of the wireless communications system <NUM> may be shorter than a subframe or may be dynamically selected (e.g.,in bursts of shortened TTIs (sTTIs) or in selected component carriers using sTTIs).

A carrier may be associated with a pre-defined frequency channel (e.g.,an E-UTRA absolute radio frequency channel number (EARFCN)), and may be positioned according to a channel raster for discovery by UEs <NUM>. Carriers may be downlink or uplink (e.g.,in an FDD mode), or be configured to carry downlink and uplink communications (e.g.,in a TDD mode). In some examples, signal waveforms transmitted over a carrier may be made up of multiple sub-carriers (e.g.,using multi-carrier modulation (MCM) techniques such as orthogonal frequency-division multiplexing (OFDM) or discrete Fourier transform-spread OFDM (DFT-s-OFDM)).

The organizational structure of the carriers may be different for different radio access technologies (e.g.,LTE, LTE-A, LTE-A Pro, NR, etc.). A carrier may also include dedicated acquisition signaling (e.g.,synchronization signals or system information, etc.) and control signaling that coordinates operation for the carrier. In some examples (e.g.,in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.

In some examples, control information transmitted in a physical control channel may be distributed between different control regions in a cascaded manner (e.g.,between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

For example, the carrier bandwidth may be one of a number of predetermined bandwidths for carriers of a particular radio access technology (e.g.,<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM>). In other examples, some UEs <NUM> may be configured for operation using a narrowband protocol type that is associated with a predefined portion or range (e.g.,set of subcarriers or RBs) within a carrier (e.g.,"in-band" deployment of a narrowband protocol type).

In a system employing MCM techniques, a resource element may consist of one symbol period (e.g.,a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g.,the order of the modulation scheme). In MIMO systems, a wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g.,spatial layers), and the use of multiple spatial layers may further increase the data rate for communications with a UE <NUM>.

Devices of the wireless communications system <NUM> (e.g.,base stations <NUM> or UEs <NUM>) may have a hardware configuration that supports communications over a particular carrier bandwidth, or may be configurable to support communications over one of a set of carrier bandwidths. In some examples, the wireless communications system <NUM> may include base stations <NUM> and/or UEs <NUM> that can support simultaneous communications via carriers associated with more than one different carrier bandwidth.

In some cases, an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g.,when multiple serving cells have a suboptimal or non-ideal backhaul link). An eCC may also be configured for use in unlicensed spectrum or shared spectrum (e.g.,where more than one operator is allowed to use the spectrum). An eCC characterized by wide carrier bandwidth may include one or more segments that may be utilized by UEs <NUM> that are not capable of monitoring the whole carrier bandwidth or are otherwise configured to use a limited carrier bandwidth (e.g.,to conserve power).

A device, such as a UE <NUM> or base station <NUM>, utilizing eCCs may transmit wideband signals (e.g.,according to frequency channel or carrier bandwidths of <NUM>, <NUM>, <NUM>, <NUM>, etc.) at reduced symbol durations (e.g.,<NUM> microseconds).

Wireless communications systems such as an NR system may utilize any combination of licensed, shared, and unlicensed spectrum bands, among others. The flexibility of eCC symbol duration and subcarrier spacing may allow for the use of eCC across multiple spectrums. In some examples, NR shared spectrum may increase spectrum utilization and spectral efficiency, specifically through dynamic vertical (e.g.,across the frequency domain) and horizontal (e.g.,across the time domain) sharing of resources.

In some cases, wireless communication systems may schedule communication resources to support both uplink and downlink transmissions. For example, a wireless communication system may allocate a set of resources to uplink transmissions. In one example, a base station may schedule overlapping transmissions on multiple channels. Once the user equipment (UE) transmits or uplinks to the base station, a collision may result as a result of the transmissions and/or channels overlapping one another. Anticipating that collisions may sometimes occur, rules have been developed to provide guidance for how to handle certain transmissions in the event of a collision.

One example set of rules includes a set of rules for handling the transmission of uplink control information (UCI), referred to herein as one or more UCI multiplexing rules. However, the UCI multiplexing rules generally only apply if certain conditions are first met. If the conditions are not met, the rules would normally not apply, and an error condition may result. For example, in the case that just one pair of overlapping channels does not meet timeline requirements of the UCI multiplexing rules, the UE may designate the uplink transmission as an error case for all uplink channels in the group of overlapping channels and the UE behavior may not be specified. This could result in additional latency or delay for transmissions associated with a service type that calls for low latency and/or high reliability, as these transmissions may also be dropped. Thus, even though the UCI multiplexing rule is intended to avoid collisions through scheduling, this method may actually increase latency for some channels.

<FIG> illustrates an example of uplink collision handling for a wireless communication system in accordance with aspects of the present disclosure. In some examples, wireless communications system <NUM> may implement aspects of wireless communication system <NUM>. The wireless communications system <NUM> may include UE <NUM>-a and base station <NUM>-a, which may be examples of the UE <NUM> and base station <NUM> described with reference to <FIG>. As shown, UE <NUM>-a may communicate with base station <NUM>-a via uplinks <NUM>-a and <NUM>-b. Further, base station <NUM>-a may communicate with UE <NUM>-a via downlinks <NUM>-a and <NUM>-b.

In some cases, a base station <NUM> (e.g.,base station <NUM>-a) may transmit control information indicating the scheduled and allocated resources in a downlink transmission over downlinks <NUM>-a and <NUM>-b, to the UE <NUM>-a. For example, the base station <NUM> may transmit downlink control information (DCI) on a downlink control channel, such as a physical downlink control channel (PDCCH). In some examples, the base station <NUM> may transmit UE-specific scheduling assignments for downlink resource allocation, uplink grants, physical random access channel (PRACH) responses, uplink power control commands, and common scheduling assignments for signaling messages (e.g.,such as system information) on the PDCCH. The base station <NUM> may transmit the control information during one or more symbols within a given TTI (e.g.,a slot, a mini-slot, an sTTI).

In some cases, the base station <NUM> (e.g.,base station <NUM>-a) may transmit control information associated with a first scheduled uplink transmission. The control information may be transmitted via downlink <NUM>-a. Additionally, the base station <NUM> (e.g.,base station <NUM>-a) may also transmit different control information via downlink <NUM>-b. In some cases, the control information of downlink <NUM>-a may include scheduling information for uplink <NUM>-a, while the control information of downlink <NUM>-b may include scheduling information for uplink <NUM>-b. In one example, the uplinks <NUM>-a and <NUM>-b may be scheduled to include uplink control information. In many cases, uplinks <NUM>-a and <NUM>-b can be scheduled so as to not overlap. In those instances, the uplink control information that is scheduled for each uplink <NUM>-a, <NUM>-b may be transmitted. However, in some instances, uplinks <NUM>-a and <NUM>-b are scheduled so as to overlap. In such situations, a UCI multiplexing rule has been adopted to allow the UE <NUM>-a to determine when and how to multiplex the scheduled UCI.

In general, the UCI multiplexing rule may be applied when a single-slot PUCCH overlaps with a single-slot PUCCH or overlaps with a single-slot PUSCH in slot n for a PUCCH group. Under the UCI multiplexing rule and corresponding timeline conditions, the UE may multiplex all UCIs on either one PUCCH or one PUSCH so long as the timeline conditions for the UCI multiplexing rules are satisfied. In this case, the timeline conditions set forth that the first symbol of the earliest PUCCH(s)/PUSCH(s) among all the overlapping channels starts no earlier than symbol N1 + X after the last symbol of PDSCH(s) and additionally, that the first symbol of the earliest PUCCH(s)/PUSCH(s) among all the overlapping channels starts no earlier than N2+Y, in which N1 and N2 are time periods between channel transmissions and X and Y are non-negative integer values. <FIG> illustrates that uplink transmissions are multiplexed via a single uplink (uplink <NUM>-a), while the other uplink (uplink <NUM>-b) is dropped, pursuant to the UCI multiplexing rule.

In <FIG>, the downlinks <NUM>-a and <NUM>-b may schedule overlapping transmissions of different service types. In one example, the service types may be eMBB and URLLC. As discussed herein, prioritizing methods may be employed to determine a higher priority channel of uplink <NUM>-a and a lower priority channel of uplink <NUM>-b as depicted in <FIG>. Establishing which channel has a higher priority over another channel may be accomplished in a number of ways. For example, a priority may be determined explicitly and may be based on an indication in a DCI field corresponding to the service of a PDCCH.

Additionally or alternatively, a priority of a channel may be determined based on a search space or control resource set (CORESET) that may be associated with a specific service type. Additionally or alternatively, a priority may be determined based on a bandwidth part (BWP) of a channel, where the BWP may be associated with a specific service type. Additionally or alternatively, a priority may be determined based on a radio network temporary identifier (RNTI) masking associated with the service type. Additionally or alternatively, a priority may be determined based on a scrambling of a downlink control channel (e.g.,PDCCH) associated with the service type, or may even be based on a transmission reception point (TRP) identification (ID).

In some cases, a priority may be determined implicitly. For example, UE <NUM>-a may determine a block error rate (BLER) for a channel state calculation. UE <NUM>-a may determine a priority for the channel state calculation based on the determined BLER (e.g.,a lower BLER may correspond to a higher priority). In other cases, UE <NUM>-a may determine a priority based on whether a RNTI is configured for a service. For example, a new RNTI for a service may not be configured. In this example, UE <NUM>-a may determine a modulation and coding scheme (MCS) (e.g.,64QAM) based on a received MCS table. UE <NUM>-a may also detect DCI formats (formats 0_0, 1_0, 0_1, 1_1, etc.) from a UE-specific search space (USS). Based on the detected formats and determined MCS, UE <NUM>-a may determine a priority for a service. In another example, RNTI may be configured for a service. Channel state feedback requests (e.g.,DCI messaging) triggering channel state calculations may be scrambled by the configured RNTI. UE <NUM>-a may determine a priority for a service based on the configured RNTI. In yet another example, the priority may be determined based on whether a new channel quality indicator (CQI) table (associated with a higher priority service) is used in reporting channel state information (CSI) on one channel, whether one of the channels follows the cap#<NUM> N1/N2 values, while the other follows cap#<NUM> N1/N2 values, or any combination thereof.

Additionally, the base station <NUM> may configure a CORESET and search space for transmission of control information (e.g.,DCI) to the UE <NUM>-a on a downlink control channel (e.g.,downlink <NUM>-a or downlink <NUM>-b). The base station <NUM>-a may configure search space sets according to control channel candidates (e.g.,PDCCH candidates) at one or more aggregation levels to use for these DCI transmissions. When configuring a search space set, the base station <NUM>-a may determine a CORESET containing the search space set.

In each of these explicit and implicit differentiation cases, the PUCCH/PUSCH channel with a lower priority, including the corresponding UCI, may be dropped, or the UCI may be multiplexed onto the PUCCH/PUSCH channel with a higher priority. For example, UE <NUM>-a may drop channel state calculations based on the determined priorities.

Dropping may refer to either dropping scheduled channel state calculations, rescheduling channel state calculations (e.g.,to another uplink control channel transmission), or stopping the performing of channel state calculations that are in the process of being calculated. In some cases, UE <NUM>-a may drop all lower priority channel state calculations and may perform all higher priority channel state calculations. Additionally, the PUCCH/PUSCH channel with a higher priority will be transmitted by the UE <NUM>-a and specifically, the UE does not consider this case as an error case.

A prioritization of channels may be useful when multiple PUSCHs and/or PUCCHs overlap or collide. In one example, at least one pair of overlapping channels may not meet timeline requirements of the UCI multiplexing rules described above. Instead of simply declaring an error case, UE <NUM>-a may prioritize the channels to determine on which channel UCI is to be multiplexed, and which UCI is to be included.

The idea of prioritizing channels to determine which of overlapping channels is to be transmitted may be extended to more general cases. For example, a UE of multiple UEs may be scheduled across different component carriers (CCs) which may be partially overlapping. Additionally, the UE may not be able to support simultaneous transmission on partially overlapping channels. In this case, the channel with the higher priority should be transmitted and the other lower priority channel, even if transmission of the lower priority channel started earlier, may be dropped. The determination of priority may be determined using the methods discussed with respect to explicit and implicit differentiation, among other methods.

In another example, a UE of multiple UEs may be scheduled across different CCs which may be partially overlapping, but in this case, the UE may support simultaneous transmission of partially overlapping channels, but may be power limited. In this example, the higher priority channel may be transmitted and for all other lower priority channels, either the power may be scaled down, even if scaling down the power may introduce phase continuity, or the transmission of all the other lower priority channels may be stopped or dropped.

In another example, multiple eMBB channels may collide with one or more URLLC channels. In this example, if the timeline requirements are satisfied for all of the channels, then UCI from the eMBB channels may be transmitted on the URLLC channel. Further, to reduce overhead, some contents of the UCI may be piggybacked, for example, hybrid auto repeat request acknowledge (HARQ-ACK) bits. The rest of the contents may be dropped.

Continuing the discussion, in the case that the timeline requirements are satisfied between some of the eMBB channels and the URLLC channel, the eMBB channels that did not satisfy the timeline requirements may be dropped, including the corresponding UCI. The eMBB channels that satisfied the timeline requirements may piggyback the corresponding UCI or some contents of the UCI onto the URLLC channel. Should the timeline requirements not be satisfied between any of the eMBB channels and the URLLC channel, then all eMBB channels, including the corresponding UCI may be dropped and the URLLC channel may be transmitted. In another example, the timeline requirements are satisfied between the eMBB channels and the URLLC channel(s) and the eMBB channel may still be dropped. Additionally, in these examples, the configuration may include a preference for which channel may be dropped in which circumstance.

A further example may include a prioritization scheme in a wireless communication system that includes multiple URLLCs. In the case that all URLLC channels meet the timeline requirements, then the UCI multiplexing rules described above could be applied. However, in the case that the timelines requirements are not met, then an error case may be declared.

Continuing the discussion, in the case that a subset of colliding URLLC channels meet the timeline jointly, one URLLC channel may be a higher priority channel based on another priority rule. This priority rule may be based on which MCS/CQI is being used. For example, new CQI tables may be associated with a higher priority. The priority rule may also be based on making the shorter N1/N2 have a higher priority, the search space/CORESET/BWP index, TRP ID, the CCS index, new RNTI, UCI content on the channels and so forth as previously discussed. In this case, the UCI of other channels may be piggybacked on the higher priority channel.

As explained above, a priority determination for each channel may be based on or associated with a service type of each channel. eMBB and URLLC are two examples of different service types. However, URLLC may include a large spectrum of latency and reliability requirements. Generally, the previously discussed rules may be applied equally to URLLC channels with different requirements. For example, an eMBB service type may be associated with a priority that is less than that of a URLLC0 service type (with latency requirements of <NUM> and a BLER of <NUM>^-<NUM>), which may be associated with a priority that is less than that of a URLLC1 (with a latency requirement of. <NUM> and a BLER of <NUM>^-<NUM>).

<FIG> illustrates an example of a timeline <NUM> that supports uplink collision handling for a wireless communication system in accordance with aspects of the present disclosure. The wireless communication system timeline <NUM> may include an uplink (UL) timeline <NUM> and a downlink (DL) timeline <NUM>. The DL timeline <NUM> of <FIG> depicts an eMBB PDCCH, a first time period <NUM>, a PDSCH, and a second time period <NUM>. The first time period <NUM> may be time period N2 and a second time period <NUM> which may be time period N1. The first time period <NUM> or N2 may be a time period that occurs between the last symbol of eMBB PDCCH and the first symbol of the eMBB PUSCH scheduled by the eMBB PDCCH of UL timeline <NUM>, and the second time period <NUM> or N1 may be a time period that occurs between the last symbol of a physical downlink shared channel (PDSCH) of the DL timeline <NUM> and the first symbol of the eMBB PUSCH of the UL timeline <NUM>. N1 and N2 are timing parameters that are used in consideration of the UCI multiplexing rules described in connection with <FIG>.

DL timeline <NUM> also illustrates the transmission/receipt of a URLLC PDCCH, or other request for a priority response from the UE. The URLLC PDCCH is received during the scheduled eMBB PUSCH, thus resulting in an overlapping schedule. The URLLC PUSCH scheduled by the URLLC PDCCH overlaps with the eMBB PUSCH. As explained above, in these circumstances, where two different channels are scheduled with an overlap, a prioritization of transmissions may occur based at least in part on the service type associated with each channel. As explained above in connection with <FIG>, the channel on which UCI is multiplexed, and which UCI to include, may be governed by a determination of which PUSCH is of the highest priority. In some instances, when the UE is not capable of supporting simultaneous transmissions, only the highest priority transmission will be maintained, while other lower priority transmissions will be dropped. In other cases, when a UE is capable of simultaneous transmissions, lower priority transmissions may be transmitted with a lower transmission power than that used for higher priority transmissions. Priority of the channels and service types may be determined by any of the discussed methods or any appropriate combinations thereof.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports uplink collision handling for a wireless communication service in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a UE <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g.,via one or more buses).

The receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g.,control channels, data channels, and information related to uplink collision handling for a wireless communication system and service types such as URLLC and eMBB, etc.). Information may be passed on to other components of the device <NUM>. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The communications manager <NUM> may identify that the UE is scheduled to transmit on a first channel associated with a first service type, identify that the UE is scheduled to transmit on a second channel associated with a second service type, and that the second channel is scheduled to at least partially overlap with the first channel, determine that one of the first channel or the second channel is a higher priority channel based on respective priorities of the first service type and the second service type, and transmit a message on the higher priority channel. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The communications manager <NUM>, or its sub-components, may be implemented in hardware, code (e.g.,software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communications manager <NUM>, or its sub-components may be executed by a general-purpose processor, a DSP, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports uplink collision handling for a wireless communication service in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM> or a UE <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g.,via one or more buses).

The communications manager <NUM> may be an example of aspects of the communications manager <NUM> as described herein. The communications manager <NUM> may include a parameter identifier <NUM>, a priority manager <NUM>, and a transmission component <NUM>. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The parameter identifier <NUM> may identify that the UE is scheduled to transmit on a first channel associated with a first service type and identify that the UE is scheduled to transmit on a second channel associated with a second service type, and that the second channel is scheduled to at least partially overlap with the first channel.

The priority manager <NUM> may determine that one of the first channel or the second channel is a higher priority channel based on respective priorities of the first service type and the second service type.

The transmission component <NUM> may transmit a message on the higher priority channel.

<FIG> shows a block diagram <NUM> of a communications manager <NUM> that supports uplink collision handling for a wireless communication service in accordance with aspects of the present disclosure. The communications manager <NUM> may be an example of aspects of a communications manager <NUM>, a communications manager <NUM>, or a communications manager <NUM> described herein. The communications manager <NUM> may include a parameter identifier <NUM>, a priority manager <NUM>, a transmission component <NUM>, and a process component <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g.,via one or more buses).

The parameter identifier <NUM> may identify that the UE is scheduled to transmit on a first channel associated with a first service type.

In some examples, the parameter identifier <NUM> may identify that the UE is scheduled to transmit on a second channel associated with a second service type, and that the second channel is scheduled to at least partially overlap with the first channel.

In some examples, the parameter identifier <NUM> may identify a set of uplink control information multiplexing rules that define conditions for multiplexing uplink control information on a single channel when multiple channels overlap.

In some examples, the parameter identifier <NUM> may identify that the UE is scheduled to transmit on a third channel that at least partially overlaps with both the first channel and the second channel, where the third channel is associated with a service type that is not the same as the service type of the higher priority channel.

In some examples, the parameter identifier <NUM> may identify that the UE is scheduled to transmit on a third channel that at least partially overlaps with both the first channel and the second channel, where the third channel is associated with a service type that is the same as the service type of the higher priority channel.

In some examples, the priority manager <NUM> may determine that the set of uplink control information multiplexing rules are not satisfied.

In some examples, the priority manager <NUM> may determine that a timeline for each of the first channel, the second channel, and the third channel satisfies a set of uplink control information multiplexing rules that define conditions for multiplexing uplink control information on a single channel when multiple channels overlap.

In some examples, transmitting the message on the higher priority channel may include transmitting the message using a transmission power that is greater than other transmission powers used for other simultaneous transmissions on channels that partially overlap with the higher priority channel, based on the UE being power-limited.

In some examples, the transmission component <NUM> may determine that the UE is to transmit uplink control information for each of the first channel, the second channel, and the third channel on the higher priority channel.

The process component <NUM> may determine that the UE is to transmit on only one of the first channel or the second channel based on the second channel being scheduled to at least partially overlap with the first channel and based on a predetermined condition.

In some examples, the process component <NUM> may determine that the UE supports simultaneous transmission of partially overlapping channels.

In some examples, the process component <NUM> may determine that the UE is power-limited.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports uplink collision handling a wireless communication service in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, or a UE <NUM> as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager <NUM>, an I/O controller <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, and a processor <NUM>. These components may be in electronic communication via one or more buses (e.g.,bus <NUM>).

The communications manager <NUM> may identify that the UE is scheduled to transmit on a first channel associated with a first service type, identify that the UE is scheduled to transmit on a second channel associated with a second service type, and that the second channel is scheduled to at least partially overlap with the first channel, determine that one of the first channel or the second channel is a higher priority channel based on respective priorities of the first service type and the second service type, and transmit a message on the higher priority channel.

The processor <NUM> may include an intelligent hardware device, (e.g.,a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory (e.g.,the memory <NUM>) to cause the device <NUM> to perform various functions (e.g.,functions or tasks supporting uplink collision handling for a wireless communication system and service types such as URLLC and eMBB).

In some cases, the code <NUM> may not be directly executable by the processor <NUM> but may cause a computer (e.g.,when compiled and executed) to perform functions described herein.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports uplink collision handling for a wireless communication service in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a base station <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g.,via one or more buses).

The receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g.,control channels, data channels, and information related to uplink collision handling for a wireless communication system, and a service type such as URLLC and eMBB, etc.). Information may be passed on to other components of the device <NUM>. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The communications manager <NUM> may schedule transmission on a first channel associated with a first service type, schedule transmission on a second channel associated with a second service type, where the second channel is scheduled to at least partially overlap with the first channel and scheduling transmission on the second channel is based on a predetermined condition, and receive a higher priority channel, where the higher priority channel is based on respective priorities of the first service type and the second service type determined by the UE. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The communications manager <NUM>, or its sub-components, may be implemented in hardware, code (e.g.,software or firmware) executed by a processor, or any combination thereof.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports uplink collision handling for a wireless communication service in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM> or a base station <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g.,via one or more buses).

The communications manager <NUM> may be an example of aspects of the communications manager <NUM> as described herein. The communications manager <NUM> may include a scheduling component <NUM> and a priority manager <NUM>. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The scheduling component <NUM> may schedule transmission on a first channel associated with a first service type and schedule transmission on a second channel associated with a second service type, where the second channel is scheduled to at least partially overlap with the first channel and scheduling transmission on the second channel is based on a predetermined condition.

The priority manager <NUM> may receive a higher priority channel, where the higher priority channel is based on respective priorities of the first service type and the second service type determined by the UE.

<FIG> shows a block diagram <NUM> of a communications manager <NUM> that supports uplink collision handling for a wireless communication service in accordance with aspects of the present disclosure. The communications manager <NUM> may be an example of aspects of a communications manager <NUM>, a communications manager <NUM>, or a communications manager <NUM> described herein. The communications manager <NUM> may include a scheduling component <NUM>, a priority manager <NUM>, a parameter identifier <NUM>, and a receiving component <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g.,via one or more buses).

The scheduling component <NUM> may schedule transmission on a first channel associated with a first service type.

In some examples, the scheduling component <NUM> may schedule transmission on a second channel associated with a second service type, where the second channel is scheduled to at least partially overlap with the first channel and scheduling transmission on the second channel is based on a predetermined condition.

The parameter identifier <NUM> may identify a set of uplink control information multiplexing rules that define conditions for multiplexing uplink control information on a single channel when multiple channels overlap.

In some cases, the first service type and the second service type are one of an enhanced mobile broadband (eMBB) service or an ultra-reliable low-latency communications (URLLC) service.

In some cases, the first channel and the second channel are one of a PUCCH channel or a PUSCH channel.

The receiving component <NUM> may receive uplink control information on the higher priority channel for a set of the channels that satisfy the set of uplink control information multiplexing rules.

In some examples, the receiving component <NUM> may receive a transmission on a channel with reduced power.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports uplink collision handling for a wireless communication service in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, or a base station <NUM> as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager <NUM>, a network communications manager <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, a processor <NUM>, and an inter-station communications manager <NUM>. These components may be in electronic communication via one or more buses (e.g.,bus <NUM>).

The communications manager <NUM> may schedule transmission on a first channel associated with a first service type, schedule transmission on a second channel associated with a second service type, where the second channel is scheduled to at least partially overlap with the first channel and scheduling transmission on the second channel is based on a predetermined condition, and receive a higher priority channel, where the higher priority channel is based on respective priorities of the first service type and the second service type determined by the UE.

The network communications manager <NUM> may manage communications with the core network (e.g.,via one or more wired backhaul links).

The memory <NUM> may store computer-readable code <NUM> including instructions that, when executed by a processor (e.g.,the processor <NUM>) cause the device to perform various functions described herein.

The processor <NUM> may include an intelligent hardware device, (e.g.,a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor <NUM> may be configured to operate a memory array using a memory controller. In some cases, a memory controller may be integrated into processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory (e.g.,the memory <NUM>) to cause the device to perform various functions (e.g.,functions or tasks supporting uplink collision handling for a wireless communication system and service types, including URLLC and eMBB).

The inter-station communications manager <NUM> may manage communications with other base station <NUM> and may include a controller or scheduler for controlling communications with UEs <NUM> in cooperation with other base stations <NUM>.

<FIG> shows a flowchart illustrating a method <NUM> that supports uplink collision handling for a wireless communication service in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a UE <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.

At <NUM>, the UE may identify that the UE is scheduled to transmit on a first channel associated with a first service type having a first priority (e.g., first priority channel). The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a parameter identifier as described with reference to <FIG>.

At <NUM>, the UE may identify that the UE is scheduled to transmit on a second channel associated with a second service type having a second priority (e.g., second priority channel), and that the second channel is scheduled to at least partially overlap with the first channel. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a parameter identifier as described with reference to <FIG>.

At <NUM>, the UE may determine that one of the first channel or the second channel is a higher priority channel based on respective priorities of the first service type and the second service type. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a priority manager as described with reference to <FIG>.

At <NUM>, the UE may transmit a message on the higher priority channel. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a transmission component as described with reference to <FIG>.

At <NUM>, the UE may identify that the UE is scheduled to transmit on a first channel associated with a first service type. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a parameter identifier as described with reference to <FIG>.

At <NUM>, the UE may identify that the UE is scheduled to transmit on a second channel associated with a second service type, and that the second channel is scheduled to at least partially overlap with the first channel. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a parameter identifier as described with reference to <FIG>.

At <NUM>, the UE may identify that the UE is scheduled to transmit on a third channel that at least partially overlaps with both the first channel and the second channel, where the third channel is associated with a service type that is the same as the service type of the higher priority channel. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a parameter identifier as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> that supports uplink collision handling for a wireless communication service in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a base station <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.

At <NUM>, the base station may schedule transmission on a first channel associated with a first service type. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a scheduling component as described with reference to <FIG>.

At <NUM>, the base station may schedule transmission on a second channel associated with a second service type, where the second channel is scheduled to at least partially overlap with the first channel and scheduling transmission on the second channel is based on a predetermined condition. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a scheduling component as described with reference to <FIG>.

At <NUM>, the base station may identify a set of uplink control information multiplexing rules that define conditions for multiplexing uplink control information on a single channel when multiple channels overlap. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a parameter identifier as described with reference to <FIG>.

At <NUM>, the base station may receive a higher priority channel, where the higher priority channel is based on respective priorities of the first service type and the second service type determined by the UE. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a priority manager as described with reference to <FIG>.

At <NUM>, the base station may receive uplink control information on the higher priority channel for a set of the channels that satisfy the set of uplink control information multiplexing rules. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a receiving component as described with reference to <FIG>.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by UEs <NUM> with service subscriptions with the network provider. A small cell may be associated with a lower-powered base station <NUM>, as compared with a macro cell, and a small cell may operate in the same or different (e.g.,licensed, unlicensed, etc.) frequency bands as macro cells. A femto cell may also cover a small geographic area (e.g.,a home) and may provide restricted access by UEs <NUM> having an association with the femto cell (e.g.,UEs <NUM> in a closed subscriber group (CSG), UEs <NUM> for users in the home, and the like). An eNB may support one or multiple (e.g.,two, three, four, and the like) cells, and may also support communications using one or multiple component carriers.

A processor may also be implemented as a combination of computing devices (e.g.,a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

By way of example, and not limitation, non-transitory computer-readable media may include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

As used herein, including in the claims, "or" as used in a list of items (e.g.,a list of items prefaced by a phrase such as "at least one of" or "one or more of") indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

Claim 1:
A method for wireless communication at a user equipment, UE, comprising:
identifying (<NUM>) that the UE is scheduled to transmit on a first channel associated with a first service type;
identifying (<NUM>) that the UE is scheduled to transmit on a second channel associated with a second service type, and that the second channel is scheduled to at least partially overlap with the first channel;
determining (<NUM>) that one of the first channel or the second channel is a higher priority channel based at least in part on respective priorities of the first service type and the second service type;
determining that the UE supports simultaneous transmission of partially overlapping channels and that the UE is power-limited;
transmitting (<NUM>) a message on the higher priority channel with a transmission power that is greater than other transmission powers used for other simultaneous transmission on channels that partially overlap with the higher priority channel, based at least in part on the UE being power-limited.