Patent Description:
However, as the demand for mobile broadband access continues to increase, further improvements in LTE and NR technologies remain useful.

3GPP document "<NPL>, summarizes views on intra-UE prioritization/multiplexing for IIoT. It discloses physical layer use of priorities for UCI multiplexing. 3GPP document "<NPL>, discusses the benefit of PHY based DG priority label to multiplexing vs prioritization decision.

In some aspects, a method of wireless communication, performed by a user equipment (UE), may include detecting a collision between a physical uplink control channel (PUCCH) and a plurality of physical uplink shared channels (PUSCHs) with a corresponding plurality of media access control (MAC) priorities, wherein the PUCCH is associated with uplink control information (UCI); selectively applying a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an effect of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing; and selectively transmitting at least one of the plurality of PUSCHs with the UCI based at least in part on a result of selectively applying the MAC prioritization rule.

In some aspects, a UE for wireless communication may include memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to detect a collision between a PUCCH and a plurality of PUSCHs with a corresponding plurality of MAC priorities, wherein the PUCCH is associated with UCI; selectively apply a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an effect of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing; and selectively transmit at least one of the plurality of PUSCHs with the UCI based at least in part on a result of selectively applying the MAC prioritization rule.

In some aspects, a method of wireless communication, performed by a base station (BS), may include determining a UCI multiplexing configuration in connection with a MAC prioritization rule for a scheduled collision between a PUCCH with UCI and a plurality of PUSCHs with a corresponding plurality of MAC priorities; and receiving at least one of the plurality of PUSCHs based at least in part on determining the UCI multiplexing configuration.

In some aspects, a BS for wireless communication may include memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to determine a UCI multiplexing configuration in connection with a MAC prioritization rule for a scheduled collision between a PUCCH with UCI and a plurality of PUSCHs with a corresponding plurality of MAC priorities; and receive at least one of the plurality of PUSCHs based at least in part on determining the UCI multiplexing configuration.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a BS, may cause the one or more processors to: detect a collision between a PUCCH and a plurality of PUSCHs with a corresponding plurality of MAC priorities, wherein the PUCCH is associated with UCI; selectively apply a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an effect of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing; and selectively transmit at least one of the plurality of PUSCHs with the UCI based at least in part on a result of selectively applying the MAC prioritization rule.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a BS, may cause the one or more processors to: determine a UCI multiplexing configuration in connection with a MAC prioritization rule for a scheduled collision between a PUCCH with UCI and a plurality of PUSCHs with a corresponding plurality of MAC priorities; and receive at least one of the plurality of PUSCHs based at least in part on determining the UCI multiplexing configuration.

In some aspects, an apparatus for wireless communication may include means for detecting a collision between a PUCCH and a plurality of PUSCHs with a corresponding plurality of MAC priorities, wherein the PUCCH is associated with UCI; means for selectively applying a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an effect of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing; and means for selectively transmitting at least one of the plurality of PUSCHs with the UCI based at least in part on a result of selectively applying the MAC prioritization rule.

In some aspects, an apparatus for wireless communication may include means for determining an UCI multiplexing configuration in connection with a MAC prioritization rule for a scheduled collision between a PUCCH with UCI and a plurality of PUSCHs with a corresponding plurality of MAC priorities; and means for receiving at least one of the plurality of PUSCHs based at least in part on determining the UCI multiplexing configuration.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

The wireless network <NUM> may include a number of BSs <NUM> (shown as BS 110a, BS 110b, BS 110c, and BS 11od) and other network entities.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with uplink channel collision resolution for conditional MAC layer based prioritization, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively.

In some aspects, UE <NUM> may include means for detecting (e.g., using controller/processor <NUM> and/or the like) a collision between a physical uplink control channel (PUCCH) and a plurality of physical uplink shared channels (PUSCHs) with a corresponding plurality of media access control (MAC) priorities, means for selectively applying (e.g., using controller/processor <NUM> and/or the like) a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an effect of the plurality of MAC priorities on an uplink control information (UCI) multiplexing configuration for UCI multiplexing, means for selectively transmitting (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) at least one of the plurality of PUSCHs with the UCI based at least in part on a result of selectively applying the MAC prioritization rule, and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>.

In some aspects, base station <NUM> may include means for determining (e.g., using controller/processor <NUM> and/or the like) a UCI multiplexing configuration in connection with a MAC prioritization rule for a scheduled collision between a PUCCH with UCI and a plurality of PUSCHs with a corresponding plurality of MAC priorities, means for receiving (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) at least one of the plurality of PUSCHs based at least in part on determining the UCI multiplexing configuration, and/or the like. In some aspects, such means may include one or more components of base station <NUM> described in connection with <FIG>.

In some communications systems, such as NR, a UE may be scheduled to transmit a plurality of channels concurrently. For example, a BS may schedule the UE for transmission of a PUCCH and one or more PUSCHs using the same orthogonal frequency multiplexing (OFDM) symbol. The UE may be unable to concurrently transmit the PUCCH and a PUSCH in a same PUCCH group or a plurality of PUSCHs using a single component carrier. However, the UE may be able to concurrently transmit a plurality of PUSCHs using a plurality of different component carriers.

Thus, the BS may define prioritizations for the different channels in order to enable the UE to resolve which channels to transmit when the UE is unable to transmit a plurality of channels concurrently. For example, the BS may define an ultra-reliable low latency communication (URLLC) channel as a high priority channel that may preempt other, lower priority channels. The BS may define channel priorities using physical (PHY) layer prioritization. For example, a BS may define a URLLC hybrid automatic repeat request acknowledgement (HARQ-ACK) with a first PHY priority, a URLLC PUSCH with a second PHY priority, an enhanced mobile broadband (eMBB) HARQ-ACK with a third PHY priority, an eMBB PUSCH with a fourth priority, and/or the like. In this case, the BS may explicitly or implicitly indicate a PHY priority of a particular channel using a downlink control information (DCI) of a scheduling grant that schedules the particular channel.

The UE may also define channel priorities using MAC layer prioritization. For example, the UE may determine a priority of a MAC payload that is to be conveyed via an uplink channel and may assign a corresponding MAC priority to the uplink channel based at least in part on the priority of the MAC payload. In some cases, the uplink channel may lack a PHY priority, and only the MAC priority may be assigned to the uplink channel. In other cases, the uplink channel may have a PHY priority and the MAC priority may override or alter the PHY priority.

When the UE is scheduled to transmit a PUCCH and one or more higher priority PUSCHs, the UE may multiplex the UCI of the PUCCH onto a PUSCH. In this case, the UE may drop the PUCCH and transmit the one or more higher priority PUSCHs. In this way, the UE ensures that both the UCI and the data of the one or more higher priority PUSCHs can both be conveyed to a BS. When using PHY layer prioritization, the UE may select a particular PUSCH of the one or more higher priority PUSCHs onto which to multiplex the UCI based at least in part on a set of fixed rules. For example, when a particular PUSCH includes an aperiodic channel state information (A-CSI) message, the UE may select the particular PUSCH onto which to multiplex the UCI. This may improve the probability that the A-CSI and the UCI are transmitted on the same PUSCH. Similarly, when a dynamic PUSCH and a configured PUSCH are available, the UE may select the dynamic PUSCH onto which to multiplex the UCI. Similarly, when selecting a PUSCH of a plurality of PUSCHs associated with a plurality of component carriers onto which to multiplex the UCI, the UE may select a PUSCH associated with a lowest indexed component carrier. Other PHY layer rules may be possible. In this way, the UE may multiplex UCI and the BS may determine onto which, of a plurality of PUSCHs, the UE multiplexed the UCI, thereby enabling the BS to decode the plurality of PUSCHs and the UCI thereof.

However, when MAC layer prioritization is applied, the BS may be unable to determine a relative priority of each PUSCH without having already decoded the payload data of each PUSCH. As a result, the BS may be unable to determine onto which of the plurality of PUSCHs the UCI is multiplexed, which may prevent the BS from being able to decode the payload data of each PUSCH.

Some aspects described herein provide for uplink channel collision resolution for conditional MAC layer based prioritization. For example, a UE may determine an effect to a UCI multiplexing configuration of applying MAC priorities to a plurality of PUSCHs. If the UE determines that applying the MAC priorities results in an ambiguity in resolving which PUSCH includes UCI, the UE may determine not to apply the MAC priorities. In contrast, if the UE determines that using the MAC priorities does not result in ambiguity, the UE may determine to apply the MAC priorities. After determining whether to apply the MAC priorities, the UE may selectively transmit one or more PUSCHs with UCI. For example, in some cases the UE may transmit the one or more PUSCHs and may multiplex the UCI onto one of the one or more PUSCHs. In other cases, the UE may drop the one or more PUSCHs (i.e., the UE may not transmit the one or more PUSCHs) and may transmit a PUCCH to convey the UCI. In this way, the UE reduces a decoding processing complexity for the BS while enabling MAC layer prioritization to be used in some cases.

<FIG> and <FIG> are diagrams illustrating an example <NUM> of uplink channel collision resolution for conditional MAC layer based prioritization. As shown in <FIG> and <FIG>, example <NUM> includes a BS <NUM> and a UE <NUM>.

As shown in <FIG>, and by reference numbers <NUM> and <NUM>-<NUM> through <NUM>-N, UE <NUM> may receive scheduling information for transmitting an uplink channel. For example, BS <NUM> may provide, and UE <NUM> may receive, PUCCH scheduling information identifying a set of resources for transmitting a PUCCH with UCI. Additionally, or alternatively, BS <NUM> may provide, and UE <NUM> may receive, PUSCH scheduling information identifying a set of resources for transmitting a set of PUSCHs.

In some aspects, UE <NUM> may request the set of resources for transmitting an uplink channel. For example, UE <NUM> may transmit a scheduling request to request that BS <NUM> provide the PUSCH scheduling information to identify the set of resources. In some aspects, the uplink channels may be associated with a set of PHY priorities. For example, the scheduling information may include a set of DCIs identifying the set of PHY priorities of the set of PUSCHs. In this case, the set of DCIs may include explicit information (e.g., information explicitly indicating the set of PHY priorities) or implicit information (e.g., information identifying types of channels of the set of uplink channels from which UE <NUM> may implicitly derive the set of PHY priorities).

As further shown in <FIG>, and by reference number <NUM>, UE <NUM> may determine that the PUCCH collides with at least one PUSCH. For example, UE <NUM> may determine that the PUCCH is scheduled for a same OFDM symbol as a PUSCH. In some aspects, UE <NUM> may determine that a plurality of PUSCHs of the set of PUSCHs are scheduled for a common time. For example, UE <NUM> may determine that the plurality of PUSCHs are scheduled for transmission using different component carriers at a common time.

As shown in <FIG>, and by reference numbers <NUM> and <NUM>, UE <NUM> may determine an effect of MAC priorities of the PUSCHs on a UCI multiplexing configuration and may determine whether to apply the MAC priorities to the PUSCHs. For example, UE <NUM> may determine whether applying the MAC priorities to the PUSCHs results in a change to a PUSCH onto which a UCI is to be multiplexed relative to a set of PHY priority-based rules for multiplexing the UCI. In this case, UE <NUM> may determine whether applying the MAC priorities results in ambiguity for BS <NUM> in resolving which PUSCH includes the UCI, and may avoid the ambiguity by selecting to not apply the MAC priorities in such a case. Alternatively, UE <NUM> may apply the MAC priorities when an ambiguity is not a result of applying the MAC priorities.

In some aspects, UE <NUM> may determine that the MAC priorities do not alter which PUSCH is to include the UCI. For example, UE <NUM> may determine that, when using the MAC priorities, the UCI is to be multiplexed onto a same particular PUSCH as when using PHY priorities. In this case, UE <NUM> may select to use the MAC priorities (e.g., for the particular PUSCH and/or for assigning payload data to other PUSCHs). In some aspects, UE <NUM> may determine not to drop the particular PUSCH (e.g., in connection with the MAC priorities) when the particular PUSCH is selected for UCI multiplexing using the UCI multiplexing configuration and/or PHY priorities. For example, when there is not enough payload data for each of a plurality of PUSCHs, using MAC priorities may indicate that UE <NUM> is to drop a particular PUSCH. In this case, when the particular PUSCH is a PUSCH onto which UCI is to be multiplexed, UE <NUM> may determine not to drop the particular PUSCH. In this case, UE <NUM> may alter a distribution of data onto the plurality of PUSCHs and/or may drop one or more other PUSCHs of the plurality of PUSCHs. Similarly, when UE <NUM> determines (e.g., based at least in part on MAC priorities) that a first subset of PUSCHs are for transmitting high-priority data and a second subset of PUSCHs are for transmitting low-priority data and the UCI is to be multiplexed onto a particular PUSCH for transmitting low-priority data that is to be dropped, UE <NUM> may avoid dropping the particular PUSCH by selecting not to use MAC priorities.

In some aspects, UE <NUM> may determine that using the MAC priorities results in one or more candidate UCI multiplexing configurations that are based at least in part on which BS <NUM> may determine an actual UCI multiplexing configuration. For example, UE <NUM> may determine that using the MAC priorities results in less than or equal to a threshold quantity of candidate UCI multiplexing configurations (e.g., less than or equal to two candidate UCI multiplexing configurations). In this case, UE <NUM> may determine to use the MAC priorities, thereby enabling use of MAC priorities without creating excessive processing complexity for BS <NUM>. In some aspects, UE <NUM> may select from a plurality of different UCI multiplexing configurations. For example, UE <NUM> may select from two candidate UCI multiplexing configurations (e.g., to multiplex UCI in accordance with a PHY layer rule or to transmit the UCI on a PUCCH). In this case, UE <NUM> may select a MAC layer data assignment configuration (e.g., in accordance with MAC priorities) that is consistent with the selected UCI multiplexing configuration. As a result, UE <NUM> ensures that application of MAC priorities satisfies a selected UCI multiplexing scheme, which may enable BS <NUM> to receive the UCI in accordance with the UCI multiplexing scheme. When UE <NUM> multiplexes the UCI with a PUSCH based at least in part on a PHY layer rule, a MAC layer of UE <NUM> may not drop the PUSCH. In this case, the MAC layer of UE <NUM> may cause the PHY layer of UE <NUM> to transmit a zero transport block (e.g., a set of padding bits) to maintain a PHY structure of the PUSCH.

In some aspects, UE <NUM> may determine that using the MAC priorities changes a UCI multiplexing configuration relative to using the PHY priorities, but may nevertheless determine to use the MAC priorities. For example, when UE <NUM> determines that the MAC priorities result in dropping a PUSCH onto which the UCI is to be multiplexed (e.g., in connection with the PHY priorities), UE <NUM> may determine to drop the PUSCH and include the UCI in the PUCCH. In this case, UE <NUM> may transmit the PUCCH and may forgo transmitting any PUSCH that collides with the PUCCH. In this case, BS <NUM> may attempt to detect whether UCI is multiplexed onto a PUSCH in accordance with a PHY layer rule and without MAC priorities (e.g., which may be applied consistent with the PHY layer rule). If not, BS <NUM> may determine that the UCI is transmitted on a PUCCH. Additionally, or alternatively, UE <NUM> may transfer the UCI from the PUSCH that is to be dropped to another PUSCH with a next lowest index (e.g., of a component carrier on which the other PUSCH is to be transmitted). In this case, UE <NUM> may forgo transmitting the PUCCH, but may transmit the other PUSCH to convey the UCI.

As further shown in <FIG>, and by reference number <NUM>, UE <NUM> may selectively transmit (e.g., transmit in some circumstances and not transmit in other circumstances) one or more PUSCHs in accordance with determining whether to use the MAC priorities. For example, UE <NUM> may transmit a PUSCH that includes UCI multiplexed into the PUSCH. In some aspects, UE <NUM> may transmit a plurality of PUSCHs. For example, UE <NUM> may transmit a first PUSCH that includes UCI multiplexed into the PUSCH on a first component carrier, a second PUSCH on a second component carrier, and/or the like.

In some aspects, UE <NUM> may drop a PUSCH. For example, based at least in part on a MAC priority and based at least in part on determining to apply the MAC priority, UE <NUM> may drop a PUSCH that is scheduled for transmission. Additionally, or alternatively, UE <NUM> may select not to transmit any PUSCH. For example, when UE <NUM> determines to drop a PUSCH onto which a UCI is to be multiplexed based at least in part on the MAC priority, UE <NUM> may transfer the UCI onto a PUCCH, and may transmit the PUCCH rather than the PUSCH. In this case, UE <NUM> may forgo transmitting any PUSCHs concurrently with the PUCCH.

In some aspects, UE <NUM> may determine data to convey via one or more PUSCHs when transmitting the one or more PUSCHs. For example, UE <NUM> may multiplex UCI onto a first PUSCH based at least in part on a PHY priority and may use the MAC priorities to determine what data to assign to each of a set of second PUSCHs. In this way, UE <NUM> may avoid ambiguity in BS <NUM> resolving which PUSCH includes the UCI (e.g., BS <NUM> may determine which PUSCH includes the UCI based at least in part on the PHY priority) and may use the MAC priority to assign data, thereby improving network utilization. In some aspects, UE <NUM> may include one or more padding bits in a PUSCH transmission. For example, when UE <NUM> lacks data to include in a particular PUSCH onto which UCI is to be multiplexed, UE <NUM> may generate all-zero transport blocks as padding bits to be conveyed via the particular PUSCH to maintain a PHY layer structure of the particular PUSCH and avoid dropping the particular PUSCH.

As further shown in <FIG>, and by reference numbers <NUM> and <NUM>, BS <NUM> may determine whether UE <NUM> is to use the MAC priorities based at least in part on the effect of the MAC priorities on the UCI multiplexing configuration and may receive the UCI. For example, BS <NUM> may determine that UE <NUM> dropped a PUSCH onto which UCI was to be multiplexed (e.g., based at least in part on a MAC priority) and may determine to receive a PUCCH onto which UE <NUM> transferred the UCI.

Additionally, or alternatively, BS <NUM> may determine that UE <NUM> dropped a PUSCH onto which UCI was to be multiplexed and may determine that a next lowest indexed PUSCH includes the UCI. In this case, BS <NUM> may decode the next lowest indexed PUSCH to receive the UCI and may decode one or more other PUSCHs that do not include UCI. Additionally, or alternatively, BS <NUM> may determine that UCI is to be multiplexed onto a particular PUSCH based at least in part on PHY priorities, and may determine that UE <NUM> is not applying a MAC priority to the particular PUSCH (and that UE <NUM> is applying MAC priorities to other PUSCHs, as described above). In this case, BS <NUM> may receive the particular PUSCH with the UCI and one or more other PUSCHs without UCI.

Other examples may differ from what is described with respect to <FIG> and <FIG>.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a UE (e.g., UE <NUM> and/or the like) performs operations associated with uplink channel collision resolution for conditional MAC layer based prioritization.

As shown in <FIG>, in some aspects, process <NUM> may include detecting a collision between a PUCCH and a plurality of PUSCHs with a corresponding plurality of MAC priorities wherein the PUCCH is associated with UCI (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may detect a collision between a PUCCH and a plurality of PUSCHs with a corresponding plurality of MAC priorities and wherein the PUCCH is associated with UCI, as described above, for example, with reference to <FIG> and <FIG>. In some aspects, the PUCCH is associated with UCI.

As further shown in <FIG>, in some aspects, process <NUM> may include selectively applying a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an effect of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may selectively apply a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an effect of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing, as described above, for example, with reference to <FIG> and <FIG>.

As further shown in <FIG>, in some aspects, process <NUM> may include selectively transmitting at least one of the plurality of PUSCHs with the UCI based at least in part on a result of selectively applying the MAC prioritization rule (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may selectively transmit at least one of the plurality of PUSCHs with the UCI based at least in part on a result of selectively applying the MAC prioritization rule, as described above, for example, with reference to <FIG> and <FIG>.

In a first aspect, the plurality of PUSCHs are scheduled on a corresponding plurality of different uplink component carriers.

In a second aspect, alone or in combination with the first aspect, selectively applying the MAC prioritization rule for processing the plurality of PUSCHs includes determining to use the corresponding plurality of MAC priorities for processing the plurality of PUSCHs based at least in part on the plurality of MAC priorities not altering a PHY layer rule for the UCI multiplexing configuration.

In a third aspect, alone or in combination with one or more of the first and second aspects, selectively applying the MAC prioritization rule for processing the plurality of PUSCHs includes multiplexing the UCI to a first PUSCH, of the plurality of PUSCHs, based at least in part on the UCI multiplexing configuration; and using the corresponding plurality of MAC priorities for assignment of data to one or more second PUSCHs, of the plurality of PUSCHs, onto which the UCI is not multiplexed.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, process <NUM> may include applying a PHY layer priority to data assignment for a particular PUSCH onto which the UCI is multiplexed.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, selectively applying the MAC prioritization rule for processing the plurality of PUSCHs includes multiplexing the UCI to a particular PUSCH, of the plurality of PUSCHs, based at least in part on the UCI multiplexing configuration; and determining not to drop the particular PUSCH in accordance with the corresponding plurality of MAC priorities.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, and according to the invention, process <NUM> may include adding one or more padding bits to the particular PUSCH in order to maintain a PHY layer structure of the particular PUSCH.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, selectively applying the MAC prioritization rule for processing the plurality of PUSCHs includes processing the plurality of PUSCHs in accordance with the corresponding plurality of MAC priorities based at least in part on the UCI multiplexing being associated with less than or equal to a threshold quantity of UCI multiplexing options.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, selectively applying the MAC prioritization rule for processing the plurality of PUSCHs includes processing the plurality of PUSCHs in accordance with the corresponding plurality of MAC priorities based at least in part on the UCI multiplexing being associated with less than or equal to two UCI multiplexing options.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, selectively applying the MAC prioritization rule for processing the plurality of PUSCHs includes determining that the corresponding plurality of MAC priorities alters the UCI multiplexing configuration; and processing the plurality of PUSCHs without using the corresponding plurality of MAC priorities based at least in part on determining that the corresponding plurality of MAC priorities alters the UCI multiplexing configuration.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, selectively applying the MAC prioritization rule for processing the plurality of PUSCHs includes dropping, based at least in part on the corresponding plurality of MAC priorities, a particular PUSCH, of the plurality of PUSCHs, onto which the UCI is to be multiplexed; transferring the UCI to the PUCCH based at least in part on dropping the particular PUSCH; and processing the plurality of PUSCHs in accordance with the corresponding plurality of MAC priorities based at least in part on determining to drop the particular PUSCH and transferring the UCI to the PUCCH.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process <NUM> may include transmitting the PUCCH based at least in part on transferring the UCI to the PUCCH; and dropping the plurality of PUSCHs based at least in part on transferring the UCI to the PUCCH.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, selectively applying the MAC prioritization rule for processing the plurality of PUSCHs includes dropping, based at least in part on the corresponding plurality of MAC priorities, a particular PUSCH onto which the UCI is to be multiplexed; moving, based at least in part on dropping the particular PUSCH, the UCI to a next lowest indexed PUSCH after the particular PUSCH; and processing the plurality of PUSCHs in accordance with the corresponding plurality of MAC priorities based at least in part on determining to drop the particular PUSCH and moving the UCI to the next lowest indexed PUSCH.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, an index of the next lowest indexed PUSCH is a component carrier index for a component carrier for which the next lowest indexed PUSCH is scheduled.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process <NUM> may include dropping the plurality of PUSCHs based at least in part on a PHY layer priority rule.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a BS, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a BS (e.g., BS <NUM> and/or the like) performs operations associated with uplink channel collision resolution for conditional MAC layer based prioritization.

As shown in <FIG>, in some aspects, process <NUM> may include determining a UCI multiplexing configuration in connection with a MAC prioritization rule for a scheduled collision between a PUCCH with UCI and a plurality of PUSCHs with a corresponding plurality of MAC priorities (block <NUM>). For example, the BS (e.g., using transmit processor <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may determine a UCI multiplexing configuration in connection with a MAC prioritization rule for a scheduled collision between a PUCCH with UCI and a plurality of PUSCHs with a corresponding plurality of MAC priorities, as described above, for example, with reference to <FIG> and <FIG>.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving the UCI via at least one of the plurality of PUSCHs or via the PUCCH in accordance with the UCI multiplexing configuration (block <NUM>). For example, the BS (e.g., using transmit processor <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive at least one of the plurality of PUSCHs based at least in part on determining the UCI multiplexing configuration, as described above, for example, with reference to <FIG> and <FIG>.

In a first aspect, determining the UCI multiplexing configuration includes deterministically resolving a UCI multiplexing configuration. For example, the BS may resolve the UCI multiplexing configuration based at least in part on a set of rules for selecting which uplink channel to use for the UCI.

In a second aspect, alone or in combination with the first aspect, determining the UCI multiplexing configuration includes processing the plurality of PUSCHs in accordance with a plurality of candidate UCI multiplexing configurations.

In a third aspect, alone or in combination with any one or more of the first and second aspects, process <NUM> may include determining the UCI multiplexing configuration based at least in part on a PHY layer priority rule.

In a fourth aspect, alone or in combination with any one or more of the first through third aspects, process <NUM> may include determining that the UCI is multiplexed to a particular PUSCH of the plurality of PUSCHs, wherein the particular PUSCH is not dropped based at least in part on the UCI being multiplexed to the particular PUSCH; and demultiplexing the UCI from the particular PUSCH.

In a fifth aspect, alone or in combination with any one or more of the first through fourth aspects, and according to the invention, the particular PUSCH includes one or more padding bits in order to maintain a PHY layer structure of the at least one PUSCH.

Claim 1:
A method of wireless communication performed by a user equipment, UE, comprising:
detecting (<NUM>) a collision between a physical uplink control channel, PUCCH, and a plurality of physical uplink shared channels, PUSCHs, with a corresponding plurality of media access control, MAC, priorities,
wherein the PUCCH is associated with uplink control information, UCI;
selectively applying (<NUM>) a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an effect of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing, comprising
multiplexing the UCI to a particular PUSCH, of the plurality of PUSCHs, based at least in part on the UCI multiplexing configuration;
adding one or more padding bits to the particular PUSCH in order to maintain a PHY layer structure of the particular PUSCH; and
selectively transmitting (<NUM>) at least one of the plurality of PUSCHs with the UCI based at least in part on a result of selectively applying the MAC prioritization rule.