Managing overlap between repeated uplink control channel transmissions and uplink data transmissions - Patents.com

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may perform a multi-stage overlap (e.g., contention) resolution procedure based on a scheduling overlap between one or more repeated transmissions of a first uplink control information (UCI) and one or more overlapping uplink transmissions having a different priority from the first UCI. The procedure may include a first stage based on different starting slot indexes or UCI types between the overlapping UCIs having the same priority, a second stage based on overlap resolution between the first UCI and additional UCIs, and a third stage based on overlap resolution between the first UCI and uplink data transmissions. The UE may selectively drop one or more of the overlapping UCIs or uplink transmissions and transmit at least a portion of the first UCI or one or more overlapping uplink transmissions according to the procedure.

Description

[Technical field]

[0001] cross reference This application claims the benefit of U.S. Provisional Patent Application No. 63 / 309,455, filed February 11, 2022, by YANG et al., entitled "MANAGING OVERLAP BETWEEN UPLINK CONTROL CHANNEL REPETITIONS AND UPLINK DATA TRANSMISSIONS," and U.S. Patent Application No. 18 / 069,955, filed December 21, 2022, by YANG et al., entitled "MANAGING OVERLAP BETWEEN UPLINK CONTROL CHANNEL REPETITIONS AND UPLINK DATA TRANSMISSIONS," each of which is assigned to the assignee of the present application.

[0002] The following relates to wireless communications, including managing overlap between uplink control channel repetition and uplink data transmissions. [Background technology]

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems, such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems, sometimes referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM), etc. A wireless multiple-access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).

[0004] In some examples, a network entity may schedule multiple uplink channels for transmission by a UE on overlapping resources. Techniques for resolving scheduling overlaps between uplink transmissions may be improved. Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses that support managing overlap between repeated transmissions of an uplink control channel carrying uplink control information (UCI) and uplink data transmissions. For example, the described techniques provide for managing overlap collisions between repeated transmissions of an uplink control channel and uplink data transmissions. In some examples, multiple repeated transmissions of a first UCI and one or more overlapping uplink transmissions may be scheduled with overlap, and the first UCI and one or more overlapping uplink transmissions may be associated with different priority indices. To resolve the overlapping channels, a user equipment (UE) may perform one or more stages of a multi-stage contention resolution procedure, which may include a prioritization procedure, an intra-UE multiplexing procedure, or a combination thereof. The multi-stage contention resolution procedure may alternatively be referred to as a multi-stage overlap resolution procedure because it addresses conflicts resulting from scheduling overlaps.

[0006] In a first stage of the multi-stage contention resolution procedure, the UE may resolve any overlap between two or more overlapping UCIs that share the same priority index, and the resolution may be based on the difference in the starting slot index or UCI type. In a second stage of the multi-stage contention resolution procedure, the UE may resolve any overlap between any overlapping UCIs with different priority indexes. In a third stage of the multi-stage contention resolution procedure, the UE may resolve any overlap between any UCIs and uplink data transmissions remaining after the first two stages based on the respective priority indexes of the UCIs and uplink data transmissions. Based on the multi-stage contention resolution procedure, the UE may selectively drop or transmit the first UCI or at least a portion of one or more overlapping uplink transmissions.

[0007] A method is described. The method may include performing one or more stages of a multi-stage overlap resolution procedure based on a scheduling overlap between one or more repeated transmissions of a first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI. The one or more stages of the multi-stage overlap resolution procedure may include a first stage, a second stage, and a third stage. The first stage may be based on overlap resolution between overlapping UCIs of the same priority index, where the overlapping UCIs include one or more of the first UCI, a second UCI associated with a priority index of the first UCI, or at least a portion of the one or more overlapping uplink transmissions. The second stage may be based on overlap resolution between the first UCI and a third UCI associated with a priority index different from the priority index of the first UCI, where the first UCI and the third UCI are associated with one or more overlapping uplink transmissions. The third stage may be based on overlap resolution between the first UCI and an uplink data transmission associated with a priority index different from a priority index of the first UCI, where the first UCI and the uplink data transmission are associated with one or more overlapping uplink transmissions. The method may include transmitting at least a portion of the first UCI or the one or more overlapping uplink transmissions according to one or more stages of a multi-stage overlap resolution procedure.

[0008] An apparatus is described. The apparatus may include at least one processor and a memory coupled to the at least one processor, where the memory stores instructions for causing the at least one processor to cause a UE to perform (e.g., directly, indirectly, after pre-processing, or without pre-processing) one or more stages of a multi-stage overlap resolution procedure based on a scheduling overlap between one or more repeated transmissions of a first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI. The one or more stages of the multi-stage overlap resolution procedure may include a first stage, a second stage, and a third stage. The first stage may be based on a difference between overlapping UCIs of the same priority index, where the overlapping UCIs include one or more of the first UCI, a second UCI associated with a priority index of the first UCI, or at least a portion of the one or more overlapping uplink transmissions. The second stage may be based on overlap resolution between the first UCI and a third UCI associated with a priority index different from the priority index of the first UCI, where the first UCI and the third UCI are associated with one or more overlapping uplink transmissions. The third stage may be based on overlap resolution between the first UCI and an uplink data transmission associated with a priority index different from the priority index of the first UCI, where the first UCI and the uplink data transmission are associated with one or more overlapping uplink transmissions. The memory may store instructions for causing the at least one processor to cause the UE to transmit at least a portion of the first UCI or the one or more overlapping uplink transmissions according to one or more stages of a multi-stage overlap resolution procedure.

[0009] Another apparatus is described. The apparatus may include means for performing one or more stages of a multi-stage overlap resolution procedure based on a scheduling overlap between one or more repeated transmissions of a first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI. The one or more stages of the multi-stage overlap resolution procedure may include a first stage, a second stage, and a third stage. The first stage may be based on a difference between the overlapping UCIs of the same priority index, where the overlapping UCIs include one or more of the first UCI, a second UCI associated with a priority index of the first UCI, or at least a portion of the one or more overlapping uplink transmissions. The second stage may be based on overlap resolution between the first UCI and a third UCI associated with a priority index different from the priority index of the first UCI, where the first UCI and the third UCI are associated with the one or more overlapping uplink transmissions. The third stage may be based on overlap resolution between the first UCI and an uplink data transmission associated with a priority index different from a priority index of the first UCI, where the first UCI and the uplink data transmission are associated with one or more overlapping uplink transmissions. The apparatus may include means for transmitting at least a portion of the first UCI or the one or more overlapping uplink transmissions according to one or more stages of a multi-stage overlap resolution procedure.

[0010] A non-transitory computer-readable medium storing code is described. The code may include instructions for at least one processor to perform one or more stages of a multi-stage overlap resolution procedure based on a scheduling overlap between one or more repeated transmissions of a first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI. The one or more stages of the multi-stage overlap resolution procedure may include a first stage, a second stage, and a third stage. The first stage may be based on a difference between the overlapping UCIs of the same priority index, where the overlapping UCIs include one or more of the first UCI, a second UCI associated with a priority index of the first UCI, or at least a portion of the one or more overlapping uplink transmissions. The second stage may be based on overlap resolution between the first UCI and a third UCI associated with a priority index different from the priority index of the first UCI, where the first UCI and the third UCI are associated with one or more overlapping uplink transmissions. The third stage may be based on overlap resolution between the first UCI and an uplink data transmission associated with a priority index different from a priority index of the first UCI, the first UCI and the uplink data transmission being associated with one or more overlapping uplink transmissions. The code may include instructions for the at least one processor to transmit at least a portion of the first UCI or the one or more overlapping uplink transmissions according to one or more stages of a multi-stage overlap resolution procedure.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing one or more stages of a multi-stage duplicate resolution procedure may include acts, features, means, or instructions for performing a first stage separately for each priority index of a set of multiple priority indexes.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing one or more stages of a multi-stage overlap resolution procedure may include acts, features, means, or instructions for selectively dropping either one repeat transmission of the one or more repeat transmissions of the first UCI or the third UCI during the second stage, where the dropping may be based on a priority index of the first UCI and a priority index of the third UCI.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing one or more stages of the multi-stage overlap resolution procedure may include acts, features, means, or instructions for selectively dropping either one of the repeat transmissions of the one or more repeat transmissions of the first UCI or the uplink data transmission during the third stage, where the dropping may be based on a priority index of the first UCI and a priority index of the uplink data transmission.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, transmitting at least a portion of the first UCI may include acts, features, means, or instructions for selectively dropping one repeat transmission of the one or more repeat transmissions of the first UCI and transmitting a remaining portion of the one or more repeat transmissions of the first UCI.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving an uplink grant for an uplink data transmission within a first processing time defined for the UE, and receiving a downlink transmission that triggers one or more of the first UCI, the second UCI, or the third UCI within a second processing time defined for the UE.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or both of the second UCI or the third UCI may not have a repeat transmission.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing one or more stages of a multi-stage overlap resolution procedure may include acts, features, means, or instructions for dropping, during the second stage, the set of multiple repeat transmissions of the one or more repeat transmissions of the first UCI when the third UCI may be scheduled to overlap with a set of multiple repeat transmissions of the one or more repeat transmissions of the first UCI and a priority index of the first UCI indicates a lower priority than the priority index of the third UCI.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing one or more stages of a multi-stage overlap resolution procedure may include acts, features, means, or instructions for dropping the third UCI during the second stage when the third UCI may be scheduled to overlap with a set of multiple repeat transmissions of the one or more repeat transmissions of the first UCI and a priority index of the first UCI indicates a higher priority than a priority index of the second UCI.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing one or more stages of a multi-stage overlap resolution procedure may include acts, features, means, or instructions for dropping, during a third stage, the set of multiple repeat transmissions of the one or more repeat transmissions of the first UCI when an uplink data transmission may be scheduled to overlap with a set of multiple repeat transmissions of the one or more repeat transmissions of the first UCI and a priority index of the first UCI indicates a lower priority than a priority index of the uplink data transmission.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing one or more stages of the multi-stage overlap resolution procedure may include acts, features, means, or instructions for dropping the uplink data transmission during the third stage when the uplink data transmission may be scheduled to overlap with a set of multiple repeat transmissions of the one or more repeat transmissions of the first UCI and a priority index of the first UCI indicates a higher priority than a priority index of the uplink data transmission.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or more of the first UCI, the second UCI, the third UCI, or the uplink data transmission may be scheduled using a first time unit that may be longer than the second time unit, and another of the first UCI, the second UCI, or the uplink data transmission may be scheduled using the second time unit.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for allocating one or more of the first UCI, the second UCI, the third UCI, or an uplink data transmission to a time period corresponding to the second time unit prior to performing the first stage of the multi-stage overlap resolution procedure.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for allocating one or more of the first UCI, the second UCI, the third UCI, or the uplink data transmission to a time period corresponding to a second time unit between performing the first stage and performing the second stage of the multi-stage overlap resolution procedure.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first stage is based on the difference in starting slot index or UCI type between overlapping UCIs of the same priority index. [Brief description of the drawings]

[0025] [Figure 1] 1 illustrates an example wireless communication system that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Diagram 2] 1 illustrates an example wireless communication system that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Diagram 3] 1 illustrates an example of a multi-stage contention resolution procedure that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Figure 4] 1 illustrates an example of a multi-stage contention resolution procedure that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Diagram 5] 1 illustrates an example of a multi-stage contention resolution procedure that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Figure 6] 1 illustrates an example of a multi-stage contention resolution procedure that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Figure 7] 1 illustrates an example process flow that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Figure 8]1 illustrates a block diagram of a device that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Figure 9] 1 illustrates a block diagram of a device that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Figure 10] 1 illustrates a block diagram of a communications manager that supports managing overlap between repeated uplink control channel transmissions and uplink data transmissions in accordance with one or more aspects of the present disclosure. [Figure 11] 1 illustrates a diagram of a system including a device that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. [Figure 12] 1 illustrates a flowchart illustrating a method for supporting managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Figure 13] 1 illustrates a flowchart illustrating a method for supporting managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. [Figure 14] 1 illustrates a flowchart illustrating a method for supporting managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0026] In some examples, a network entity may schedule multiple overlapping physical uplink control channel (PUCCH) transmissions carrying uplink control information (UCI) for a user equipment (UE), or physical uplink shared channel transmissions (PUSCHs) carrying uplink data, and the scheduling overlap between the channels may cause collisions or scheduling conflicts. If the UE does not have the capability to simultaneously transmit the overlapping channels, the UE may follow a prioritization procedure or an intra-UE multiplexing procedure to resolve the overlapping channels. For example, if two PUCCHs overlap, the UE may multiplex the UCI of the PUCCHs into one PUCCH to resolve the overlapping channels. In another example, if the overlapping channels are associated with different priority indexes, the UE may at least partially cancel or drop the relatively lower priority channel and transmit the relatively higher priority channel to resolve the overlapping channels.

[0027] In addition, if two overlapping channels share the same priority index, the UE may resolve the overlapping channels based on the UCI type priority associated with the UCI carried in the channel. For example, the UE may at least partially cancel or drop a channel carrying UCI (e.g., channel state information (CSI)) with a relatively lower UCI type priority and transmit a channel carrying UCI (e.g., hybrid automatic repeat request (HARQ) acknowledgment (ACK)) with a relatively higher UCI type priority. If the UCI in both channels is the same, the UE may at least partially cancel or drop a channel scheduled in a later slot and transmit a channel scheduled in an earlier slot. However, such prioritization rules may fail to resolve overlapping channels when at least one of the overlapping channels includes a PUCCH scheduled with repeated transmission.

[0028] Techniques described herein provide for managing overlap collisions between repeated transmissions of a PUCCH and uplink data transmissions. In some examples, multiple repeated transmissions of a first UCI may conflict with one or more overlapping uplink transmissions, and the first UCI and the one or more overlapping uplink transmissions may be associated with different priority indices. This scenario may trigger one or more stages of a multi-stage contention resolution procedure, which may include a prioritization procedure, an intra-UE multiplexing procedure, or a combination thereof. The multi-stage contention resolution procedure may alternatively be referred to as a multi-stage overlap resolution procedure because it addresses conflicts resulting from scheduling overlaps. In a first stage of the multi-stage contention resolution procedure, the UE may resolve overlaps between two or more overlapping UCIs that share the same priority index, and the resolution may be based on a difference in starting slot index or UCI type.

[0029] In a second stage of the multi-stage contention resolution procedure, the UE may resolve any overlap between any overlapping UCIs with different priority indexes. In a third stage of the multi-stage contention resolution procedure, the UE may resolve any overlap between any UCIs and uplink transmissions remaining after the first two stages based on the respective priority indexes of the UCIs and uplink data transmissions. Based on the multi-stage contention resolution procedure, the UE may selectively drop or transmit the first UCI or at least a portion of one or more overlapping uplink transmissions.

[0030] In some examples, a prioritized UCI from one or more stages may not overlap with other UCIs or uplink transmissions of the same priority index. That is, a resolved conflict between overlapping uplink transmissions may fail to overlap with a different uplink transmission. In addition, the multi-stage contention resolution procedure may vary based on the time unit in which the UE is performing one or more stages. For example, if a network entity schedules a repeat transmission of a first UCI in a subslot (e.g., instead of a slot), the UE may selectively drop a lower priority uplink transmission that overlaps with a UCI that includes a high priority HARQ-ACK in favor of transmitting the high priority HARQ-ACK. Additionally or alternatively, the UE may associate a low priority UCI with a time unit (e.g., slot, subslot) corresponding to a high priority UCI at different times during the multi-stage contention resolution procedure, which may affect the outcome of one or more stages of the multi-stage contention resolution procedure.

[0031] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are then described in the context of multi-stage contention resolution procedures and process flows. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow charts related to managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions.

[0032] 1 illustrates an example of a wireless communication system 100 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a network operating according to a Long Term Evolution (LTE) network, a LTE-Advanced (LTE-A) network, a LTE-A Pro network, a New Radio (NR) network, or other systems and radio technologies, including future systems and radio technologies not expressly mentioned herein.

[0033] The network entities 105 may be distributed throughout a geographic area to form the wireless communication system 100 and may include devices of different forms or with different capabilities. In some examples, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entities 105 and the UEs 115 may support communication of signals via one or more radio access technologies (RATs).

[0034] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both at different times. The UEs 115 may be devices of different forms or with different capabilities. Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.

[0035] As described herein, a node of the wireless communication system 100, which may be referred to as a network node or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, reference to a UE 115, a network entity 105, an apparatus, a device, a computing system, etc. may include disclosure of the UE 115, the network entity 105, the apparatus, the device, the computing system, etc. being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0036] In some examples, the network entities 105 may communicate with the core network 130, with each other, or with both. For example, the network entities 105 may communicate with the core network 130 through one or more backhaul communication links 120 (e.g., via S1, N2, N3, or other interface protocols). The network entities 105 may communicate with each other either through the backhaul communication links 120 (e.g., via X2, Xn, or other interface protocols), directly (e.g., directly between the network entities 105), or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), among other examples or various combinations thereof. The UE 115 may communicate with the core network 130 through the communication link 155.

[0037] One or more of the network entities 105 described herein may include a base station (e.g., a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a Next Generation NodeB or a giga NodeB (any of which may be referred to as a gNB), a Next Generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology) or may be referred to as a base station 140. The network entities 105 (e.g., the base stations 140) may be implemented in an aggregated or monolithic base station architecture, or alternatively, in a non-aggregated base station architecture. For example, the network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a Radio Access Network (RAN) Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof). The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission / reception point (TRP). One or more components of the network entity 105 of a disaggregated RAN may be co-located, or one or more components of the network entity 105 may be located in distributed locations.

[0038] The division of functions among the CU 160, the DU 165, and the RU 175 is flexible and may support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are executed in the CU 160, the DU 165, or the RU 175. For example, a functional division of a protocol stack may be adopted between the CU 160 and the DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, which may host lower protocol layers such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, each of which may be at least partially controlled by the CU 160. Additionally or alternatively, a functional division of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170).In some cases, the functional division between the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within a protocol layer (e.g., some functions for the protocol layer may be performed by one of the CU 160, the DU 165, or the RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). The CU 160 may be further functionally divided into a CU control plane (CU-CP) function and a CU user plane (CU-UP) function. The CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u), and the DUs 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., an open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by the respective network entities 105 communicating over such communication link.

[0039] In a wireless communication system (e.g., the wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an integrated access backhaul (IAB) network architecture (e.g., to the core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 (e.g., one or more RUs 170) may be partially controlled by a CU 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB Mobile Termination (IAB-MT) that is controlled (e.g., scheduled) by the DU 165 of the associated IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115 or may share the same antennas (e.g., of the RU 170) of the IAB node 104 that are used for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., the IAB node 104, the UE 115) in a relay chain or configuration of an access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate in accordance with the techniques described herein.

[0040] For the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions as described herein. For example, some operations described as being performed by the UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 170, the SMO 180).

[0041] The UE 115 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or any other suitable terminology, and a "device" may be referred to as a unit, a station, a terminal, or a client, among various examples. The UE 115 may be a mobile phone, a personal digital assistant (PDA), a multimedia / entertainment device (e.g., a radio, an MP3 player, or a video device), a camera, a gaming device, a navigation / positioning device (e.g., based on global positioning system (GPS), Beidou, GLONASS, or Galileo, or a ground-based device, e.g., global navigation satellite (GNSS) The electronic devices may also include or may be referred to as personal electronic devices such as a wireless or wired system (Global Navigation Satellite System) device), tablet computer, laptop computer, netbook, smartbook, personal computer, smart device, wearable device (e.g., smart watch, smart clothing, smart glasses, virtual reality goggles, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), drone, robot / robotic device, vehicle, vehicle device, meter (e.g., parking meter, electric meter, gas meter, water meter), monitor, gas pump, appliance (e.g., kitchen appliance, washer, dryer), location tag, medical / healthcare device, implant, sensor / actuator, display, or any other suitable device configured to communicate over a wireless or wired medium.In some examples, the UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various items such as an appliance, or a vehicle, a meter, among other examples.

[0042] The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may act as relays, as shown in FIG. 1, as well as network entities 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among various examples.

[0043] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for the communication links 125 may include a portion (e.g., a bandwidth part, BWP) of a radio frequency spectrum band that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry collection signaling (e.g., synchronization signals, system information), control signaling to coordinate operation on the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communications between the network entity 105 and other devices may refer to communications between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, when referring to the network entity 105, the terms "transmitting," "receiving," or "communicating" may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN that communicates with another device (e.g., directly or via one or more other network entities 105).

[0044] A signal waveform transmitted on a carrier may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., the time length of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing are inversely proportional. The amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate for the device may be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase data rates or data integrity for communications with UE 115.

[0045] One or more numerologies for a carrier may be supported, and the numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communication for the UE 115 may be limited to one or more active BWPs.

[0046] The time interval for the network entity 105 or the UE 115 may be, for example, T s =1 / ((Δf max N f )) seconds, and Δf maxmay represent the maximum supported subcarrier spacing, and N f may represent the maximum discrete Fourier transform (DFT) size supported. The communication resource time intervals may be organized according to radio frames, each having a specified time length (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0047] Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same time length. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain amount of slots. Alternatively, each frame may include a variable amount of slots, and the amount of slots may depend on the subcarrier spacing. Each slot may include a certain amount of symbol periods (e.g., depending on the length of a cyclic prefix prepended to each symbol period). In some wireless communications systems 100, a slot may be further divided into multiple minislots that include one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the frequency band of operation.

[0048] A subframe, slot, minislot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI length (e.g., the amount of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., among a burst of shortened TTIs (sTTIs)).

[0049] The physical channels may be multiplexed on the carriers according to various techniques. The physical control channels and the physical data channels may be multiplexed on the downlink carriers using, for example, one or more of a time division multiplexing (TDM), a frequency division multiplexing (FDM), or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for the physical control channels may be defined by a set of symbol periods and may extend across the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates at one or more aggregation levels configured in a cascaded manner. The aggregation level for a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0050] The network entity 105 may provide communication coverage via one or more cells, e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with the network entity 105 (e.g., on a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) to distinguish neighboring cells. In some examples, a cell may also refer to a coverage area 110 or a portion (e.g., a sector) of a coverage area 110 in which the logical communication entity operates. Such a cell may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include, among others, a building, a subset of a building, or an outside space between or overlapping with the coverage area 110.

[0051] A macro cell generally covers a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs 115 that subscribe to the service of a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) compared to a macro cell, and the small cell may operate in the same or a different (e.g., licensed, unlicensed, etc.) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that subscribe to the service of the network provider, or may provide restricted access to UEs 115 that have an association with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with a user in a home or office). A network entity 105 may support one or more cells and may also support communication on one or more cells using one or more component carriers.

[0052] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0053] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for moving geographic coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include heterogeneous networks, for example, where different types of network entities 105 provide coverage to various coverage areas 110 using the same or different radio access technologies.

[0054] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and transmissions from different network entities 105 may not be aligned in time, in some examples. The techniques described herein may be used for either synchronous or asynchronous operation.

[0055] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception, but not simultaneous transmission and reception). In some examples, the half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the UE 115 include entering a power saving deep sleep mode when not engaged in active communication, operating over a limited bandwidth (e.g., in accordance with narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of the carrier, or outside of a carrier.

[0056] The wireless communication system 100 may be configured to support ultra-reliable or low latency communications, or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low latency, or critical functionality. Ultra-reliable communications may include private or group communications and may be supported by one or more services such as push-to-talk, video, data, etc. Support for ultra-reliable, low latency functionality may include service prioritization, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low latency, and ultra-reliable low latency may be used interchangeably herein.

[0057] In some examples, the UEs 115 may be able to communicate directly with other UEs 115 via device-to-device (D2D) communication links 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UEs 115 of a group performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, the D2D communication may be performed between the UEs 115 without the involvement of the network entity 105.

[0058] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnects to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be forwarded through a user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0059] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). The 300 MHz to 3 GHz region is commonly known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range in length from approximately 1 decimeter to 1 meter. Although UHF waves may be blocked or redirected by buildings and environmental features, which may be called clusters, the waves may penetrate structures sufficiently for a macrocell to serve UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmissions using lower frequencies and longer waves in the shortwave (high frequency (HF)) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0060] The wireless communication system 100 may also operate in the super high frequency (SHF) region, also known as the centimeter band, using a frequency band from 3 GHz to 30 GHz, or in the extremely high frequency (EHF) region of the spectrum, also known as the millimeter band (e.g., from 30 GHz to 300 GHz). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105 (e.g., base station 140, RU 170), where the EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate the use of antenna arrays within the devices. However, propagation of EHF transmissions may experience more atmospheric attenuation and may be shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed over transmissions using one or more different frequency regions, and the designated use of the bands over these frequency regions may vary by country or regulatory body.

[0061] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation in an unlicensed band may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA). Operation in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0062] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be collocated in an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at various geographic locations. The network entity 105 may have an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted through the antenna ports.

[0063] Beamforming, sometimes referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting and receiving devices. Beamforming may be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array are subject to constructive interference, while other signals are subject to destructive interference. Adjustment of signals communicated through antenna elements may include the transmitting or receiving device applying an amplitude offset, a phase offset, or both to signals conveyed through the antenna element associated with the device. The adjustment associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device, or to some other orientation).

[0064] The UE 115 and the network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. HARQ feedback is one technique for increasing the likelihood that data is correctly received over a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using 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., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which the device may provide HARQ feedback in a particular slot for data received in a previous symbol in that slot. In some other examples, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0065] In some wireless communication systems 100 (e.g., NR communication systems), the network entity 105 may schedule the UE 115 with multiple overlapping channels for transmission. For example, the UE 115 may be scheduled with multiple PUCCHs or PUSCHs that overlap in time, which may cause collisions. If the UE 115 does not have the capability to simultaneously transmit the overlapping channels, the UE 115 may follow some intra-UE multiplexing procedures to resolve the overlapping channels and determine which channel to prioritize for transmission. In some examples, when the overlapping PUCCHs are associated with the same priority index, the UE 115 may multiplex the UCI of the PUCCHs into one PUCCH for transmission. In some other examples, when the PUCCH overlaps with the PUSCH, the UE may piggyback the UCI onto the PUSCH for transmission. However, if any of the PUCCHs includes a repeat transmission (e.g., if the PUCCH is scheduled across multiple slots with multiple opportunities), the UE 115 may refrain from multiplexing UCI onto the repeat transmission of the PUCCH or multiplexing the repeated UCI onto any PUSCH. Instead, the UE 115 may follow some prioritization rules (e.g., dropping rules) in a multi-stage contention resolution procedure to resolve the overlapping channels by dropping the overlapping channels that may be deprioritized (e.g., lower priority compared to other channels) and transmitting the channels that may be prioritized. Thus, if the PUCCH is scheduled as an independent transmission without a repeat transmission, the UE 115 may use an intra-UE multiplexing procedure to resolve the overlapping channels, and if the PUCCH includes a repeat transmission, the UE 115 may use the prioritization rules in the multi-stage contention resolution procedure to resolve the overlapping channels.

[0066] In some cases, two or more prioritization levels may be used to establish a priority hierarchy among the multiple overlapping channels. In one example, two prioritization levels may be defined, corresponding to a priority index of 0 indicating low priority and a priority index of 1 indicating high priority. If a collision occurs between two channel transmissions of different priority indexes (e.g., when two overlapping PUCCHs have different priorities), the UE 115 may at least partially cancel the lower priority channel and transmit the higher priority channel during the overlapping time period based on the priority index associated with each channel. Furthermore, the UE 115 may perform an intra-UE multiplexing procedure for channels with the same priority index. When two overlapping channels have the same priority index, the UE 115 may use the prioritization rules of the intra-UE multiplexing procedure or the multi-stage contention resolution procedure based on the presence of repeated transmissions of the PUCCH. As described herein, canceling a channel is different from dropping a channel. That is, channel cancellation may include partial cancellation (e.g., canceling a portion of an overlapping channel while transmitting the remaining portion of the non-overlapping channel), while dropping may apply to the entire transmission and have stricter time requirements.

[0067] Some wireless communication systems 100 may support UE 115 multiplexing UCI across different priorities within the same transmission, so that UE 115 may avoid canceling or dropping low priority channels as much as possible. To support intra-UE multiplexing when none of the overlapping PUCCHs are scheduled with repetitive transmissions, UE 115 may perform a multi-stage contention resolution procedure to resolve any contention between PUCCHs carrying UCI or PUSCHs carrying uplink data. In the first stage of the multi-state contention resolution procedure, UE 115 may first resolve any overlapping channels with the same priority index. That is, any overlapping PUCCHs remaining after resolution may have different priorities.

[0068] After resolving channels with the same priority index, the UE 115 may perform a second stage of a multi-stage contention resolution procedure to resolve any overlap between channels with different priority indexes (e.g., overlapping high and low priority channels). For example, the UE 115 may resolve any overlap between overlapping UCI with different priority indexes (e.g., overlapping low and high priority PUCCHs). If the UE 115 may simultaneously transmit a PUSCH with a PUCCH (e.g., if the PUSCH and PUCCH are scheduled on different bands and are of different priorities), the PUSCH may be excluded from the set of overlapping channels for multiplexing UCI with other PUSCHs.

[0069] In a third stage of the multi-stage contention resolution procedure, the UE may resolve any overlap between any UCI and uplink data transmissions remaining after the first two stages. For example, if a low priority PUCCH, a high priority PUCCH, a low priority PUSCH, and a high priority PUSCH are included in different time units (e.g., slots, subslots, mixed numerology between PUCCH and PUSCH), the UE 115 may use the time unit of the high priority HARQ-ACK to resolve the overlapping channels.

[0070] However, some intra-UE multiplexing procedures may fail to resolve any overlap between one or more channels carrying UCI when at least one overlapping channel is scheduled with repeated transmission. For example, as long as there is a PUCCH with repeated transmission across multiple slots, UE 115 may refrain from multiplexing different UCI types to resolve any overlap between channels. In addition, when UE 115 transmits a first PUCCH (e.g., repeated transmission) and a second PUCCH (e.g., repeated transmission or single slot transmission), for each slot of the overlapping slots, UE 115-a may follow a UCI type priority rule, where UE 115 may determine which PUCCH to transmit based on the priority of the UCI type associated with each PUCCH. For example, HARQ-ACK may have a higher priority than a scheduling request (SR), which may have a higher priority than a CSI with a relatively higher priority, which may have a higher priority than a CSI with a relatively lower priority.

[0071] In addition to the prioritization levels (e.g., priority index 0 and priority index 1), the UE 115 may use additional prioritization rules in a multi-stage contention resolution procedure, which may be based on UCI type. For example, if two overlapping PUCCHs have different UCI type priorities, the UE 115 may transmit the corresponding UCI with a higher priority UCI type than the other PUCCH. If two overlapping PUCCHs have the same UCI type priority, the UE 115 may transmit the PUCCH that starts in an earlier slot (e.g., the UE 115 may prioritize channels based on the starting time or slot of the channel) and drop the PUCCH that starts in a later slot. However, such prioritization rules may increase signaling overhead and degrade communication quality, especially when the channels are scheduled with repeated transmissions, since many channels are canceled or dropped compared to the transmitted channels.

[0072] The wireless communication system 100 may support resolving overlap channels between repeated transmissions of an uplink control channel carrying a UCI and an uplink data transmission. For example, the network entity 105 may schedule multiple repeated transmissions of a first UCI that may conflict with one or more overlapping uplink transmissions, and the first UCI and the one or more uplink transmissions may be associated with different priority indices. The scenario may trigger one or more stages of a multi-stage contention resolution procedure, which may include a prioritization procedure, an intra-UE multiplexing procedure, or a combination thereof. In the first stage of the multi-stage contention resolution procedure, the UE 115 may resolve overlaps between one or more of the first UCI, the second UCI, or at least a portion of the one or more overlapping uplink transmissions, and the first UCI and the second UCI may share the same priority index, and the resolution may be based on a difference in a starting slot index or a UCI type.

[0073] In a second stage of the multi-stage contention resolution procedure, the UE 115 may resolve any overlap between any overlapping UCIs having different priority indexes. In a third stage of the multi-stage contention resolution procedure, the UE 115 may resolve any overlap between any UCIs and uplink data transmissions remaining after the first two stages based on the respective priority indexes of the UCIs and uplink data transmissions. Based on the multi-stage contention resolution procedure, the UE 115 may selectively drop or transmit the first UCI or at least a portion of one or more overlapping uplink transmissions.

[0074] 2 illustrates an example of a wireless communication system 200 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. In some examples, the wireless communication system 200 may implement or be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 115-a and a network entity 105a, which may be examples of corresponding devices described herein. In some examples, the UE 115-a may perform a multi-stage contention resolution procedure to resolve overlapping channel transmissions. As described herein, the multi-stage contention resolution procedure may alternatively be referred to as a multi-stage overlap resolution procedure because it addresses conflicts resulting from scheduling overlaps.

[0075] The network entity 105-a and the UE 115-a may communicate over a wireless communication link 205 (e.g., an uplink). In some examples, the network entity 105-a may schedule uplink transmissions (e.g., a PUCCH transmission carrying UCI, a PUSCH transmission carrying uplink data) for the UE 115-a to perform over the wireless communication link 205. For example, the network entity 105-a may schedule two PUCCH transmissions that overlap in time such that the PUCCH transmissions collide. In addition, the overlapping PUCCHs may be scheduled with a repeat transmission. To resolve overlapping channels (e.g., overlapping PUCCHs, overlapping PUCCHs and PUSCHs) when at least one overlapping PUCCH is scheduled with a repeat transmission, the UE 115-a may perform a multi-stage contention resolution procedure, which may include a prioritization procedure (e.g., a repeat transmission prioritization procedure), an intra-multiplexing procedure, or a combination thereof.

[0076] In some cases, the network entity 105-a may schedule multiple UCIs 210 (e.g., PUCCH transmissions) and uplink data transmissions for the UE 115-a. For example, the network entity 105-a may schedule UCI 210-a (e.g., a first UCI), UCI 210-b (e.g., a second UCI), UCI 210-c (e.g., a third UCI), and uplink data 215, where UCI 210-a may be scheduled with one or more repeated transmissions. In some cases, one or more repeated transmissions of UCI 210-a may overlap with UCI 210-b, UCI 210-c, uplink data 215, or any combination thereof.

[0077] In some examples, UCI 210-a may overlap with UCI 210-b, and UCI 210-a and UCI 210-b share the same priority index. In some cases, UE 115-a may resolve overlaps or PUCCH transmissions, PUSCH transmissions, or both of the same priority index. For example, UCI 210-a and UCI 210-b may share priority index 0 (e.g., indicating low priority) or priority index 1 (e.g., indicating high priority). In some cases, UE 115-a may perform a first stage of a multi-stage contention resolution procedure independently for each priority index. Because UCI 210-a is scheduled with recurring transmissions and has a given priority (e.g., priority X), UE 115-a may perform the first stage to determine whether UCI 210-a or UCI 210-b should be prioritized, and the first stage may include a prioritization procedure based on a starting slot index and a priority of the UCI type. In some examples, the starting slot index may correspond to the time (e.g., slot) at which each UCI 210 is scheduled to be transmitted. For example, UCI 210-b may have an earlier starting slot than UCI 210-a. The priority of the UCI types may indicate that HARQ-ACK has higher priority than SR, which has higher priority than high-priority CSI, which has higher priority than low-priority CSI (e.g., HARQ-ACK>SR>high-priority CSI>low-priority CSI). That is, a UCI 210 carrying a HARQ-ACK may be prioritized over a UCI 210 carrying a SR, etc.

[0078] If two different overlapping UCIs 210 share the same priority index (e.g., priority Y) that is different from the priority index shared by UCIs 210-a and UCIs 210-b, and none of the overlapping UCIs 210 with priority Y are scheduled with repetitive transmission, UE 115-a may perform an intra-UE multiplexing procedure to resolve the overlap, regardless of whether UCI 210-a is scheduled with repetitive transmission. Thus, UE 115-a may apply different prioritization rules (e.g., for intra-UE multiplexing procedure or prioritization procedure) to UCIs 210 with different priorities. In addition, after UE 115-a resolves the overlap for UCIs 210 with the same priority index (e.g., priority X or priority Y), any scheduled UCIs 210 with the same priority index may no longer overlap.

[0079] In some cases, the UCI 210-a may have a different priority index than the UCI 210-c and the uplink data 215. Thus, the UE 115-a continues the multi-stage contention resolution procedure to resolve the scheduling overlap of the UCI 210 with different priorities. For example, the UE 115-a may perform a second stage of the multi-stage contention resolution procedure to resolve the overlap between the UCI 210-a and the UCI 210-c, where the UCI 210-a and the UCI 210-c may be associated with different priority indices. That is, the priority index of the UCI 210-a may be different from the priority index of the UCI 210-c. Because the UCI 210-a is scheduled with recurring transmission, the UE 115-a may resolve the overlap between the UCI 210-a and the UCI 210-c by dropping the UCI 210 with the lower priority index. For example, if UCI 210-a has a higher priority than UCI 210-c, then UE 115-a may selectively drop UCI 210-c in favor of UCI 210-a. If not (e.g., if UCI 210-a has a lower priority index than UCI 210-c), then UE 115-a may drop UCI 210-a in favor of UCI 210-a. Dropping (e.g., selectively dropping) UCI ​​210 or some other data may include canceling transmission of UCI 210, refraining from transmitting UCI 210, or removing UCI 210 from a memory, buffer, or storage of UE 115-a, among other forms of dropping a transmission.

[0080] The UE 115-a may perform a second stage of the multi-stage contention resolution procedure for each time unit (e.g., slot, subslot) associated with the high priority HARQ-ACK. For example, if the high priority HARQ-ACK is subslot-based, the UE 115-a may perform the second stage of the multi-stage contention resolution procedure for each subslot in which any overlap occurs. If the high priority HARQ-ACK is slot-based, the UE 115-a may perform the second stage of the multi-stage contention resolution procedure for each slot in which any overlap occurs.

[0081] In some examples, the UCI 210-a and the uplink data 215 may be associated with different priority indices. Thus, the UE 115-a may continue the multi-stage contention resolution procedure to resolve any scheduling overlap between the UCI 210-a and the uplink data 215. For example, the UE 115-a may perform a third stage of the multi-stage contention resolution procedure to resolve the overlap between the UCI 210-a and the uplink data 215, and the UCI 210-a and the uplink data 215 may be associated with different priority indices. That is, the priority index of the UCI 210-a may be different from the priority index of the uplink data 215. If the remaining PUCCH still has a repeat transmission (e.g., the UCI 210-a), the UE 115-a may drop the UCI 210-a or the uplink data 215 with a lower priority index. That is, the UE 115-a may perform a third stage of the multi-stage contention resolution procedure based on the difference in priority index between the UCI 210-a and the uplink data 215. For example, if the UCI 210-a has a higher priority than the uplink data 215, the UE 115-a may selectively drop the uplink data 215 in favor of the UCI 210-a. Otherwise (e.g., if the uplink data 215 has a higher priority than the UCI 210-a), the UE 115-a may drop the UCI 210-a in favor of the uplink data 215. In some examples, the UE 115-a may resolve overlaps for PUCCH transmissions of different priority indexes during the second stage.

[0082] The UE 115-a may perform a third stage of the multi-stage contention resolution procedure for each time unit (e.g., slot, sub-slot) associated with the high priority HARQ-ACK. For example, if the high priority HARQ-ACK is sub-slot based, the UE 115-a may perform a third stage of the multi-stage contention resolution procedure for each sub-slot in which any overlap occurs. If the high priority HARQ-ACK is slot based, the UE 115-a may perform a third stage of the multi-stage contention resolution procedure for each slot in which any overlap occurs. In some cases, the UE 115-a may resolve overlaps for PUCCH and PUSCH transmissions of different priority indices during the third stage.

[0083] The UE 115-a may transmit the UCI 210-a, the UCI 210-b, the UCI 210-c, or at least a portion of the uplink data 215 to the network entity 105-a according to one or more stages of a multi-stage contention resolution procedure (e.g., a prioritization procedure and intra-UE multiplexing). For example, the UE 115-a may multiplex downlink HARQ-ACK information with or without a scheduling request and one or more CSI reports in the same PUCCH. In some other examples, the UE 115-a may drop one or more CSI reports and include only downlink HARQ-ACK information with or without a scheduling request in the PUCCH.

[0084] In some examples, the UE 115-a may transmit the UCI 210-a to the network entity 105-a if the UCI 210-a has a higher priority than the UCI 210-c or the uplink data 215. In some other examples, if the UCI 210-a and the UCI 210-b have the same priority index, the UE 115-a may multiplex the UCI 210 into one PUCCH and transmit the PUCCH to the network entity 105-a. In some examples, a portion of the UCI 210-a may overlap with a portion of the UCI 210-b, the UCI 210-c, or the uplink data 215. For example, if a portion of each of UCI 210-a and uplink data 215 overlap and UCI 210-a has a higher priority index than uplink data 215, UE 115-b may partially cancel uplink data 215 such that the portion having overlap is canceled, and the remainder of uplink data 215 may be transmitted in addition to the higher priority UCI 210-a. Additionally, in each stage of the multi-stage contention resolution procedure, if UE 115-a drops a PUCCH with repeat transmission due to a PUCCH having a relatively lower UCI type priority in the first stage or associated with a relatively lower priority index in the second and third stages, UE 115-a may drop any repeat transmission of any overlapping PUCCH or PUCCHs and still transmit repeat transmissions of any non-overlapping PUCCHs.

[0085] Each stage of the multi-stage contention resolution procedure may result in a resulting channel (e.g., a resulting PUCCH) that may be different from the overlapping channel. For example, if the UE 115-a drops a repeat transmission of the UCI 210-a based on the priority index of the UCI 210-b being higher than the priority index of the UCI 210-a, the UE 115-a may transmit the UCI 210-b on the resulting channel. In another example, if the UCI 210-a and the UCI 210-b have the same priority index, and the UE 115-a performs intra-UE multiplexing to multiplex the UCI 210-a and the UCI 210-b into one PUCCH, the PUCCH may be the resulting new channel. In some cases, the resulting channel may overlap with other channels that have the same priority index (e.g., as the UCI 210-a, the UCI 210-b, and the resulting channel). The UE 115-a may then resolve this new overlap in another stage of the multi-stage contention resolution procedure based on the priority of the corresponding overlapping channels.

[0086] However, in some examples, the resulting channel of a stage of the multi-stage contention resolution procedure may not overlap with the UCI 210 with repeat transmission having the same priority as the resulting channel. That is, the UE 115-a may not expect the resulting channel of a stage of the multi-stage contention resolution procedure to overlap with another PUCCH resource with repeat transmission. If the resulting channel is a result from a first stage of the multi-stage contention resolution procedure, the UE 115-a may not expect the resulting channel to overlap with another PUCCH with repeat transmission having the same priority. If the resulting channel is a result from a second stage of the multi-stage contention resolution procedure, the UE 115-a may not expect the resulting channel to overlap with any other PUCCH with repeat transmission, regardless of whether the priority of the other PUCCH with repeat transmission is the same as or different from the resulting channel. For example, in some cases, after the corresponding overlap with UCI 210-a is resolved, UCI 210-b and UCI 210-c both have no repeat transmissions, and UCI 210-b and UCI 210-c cannot contend with other UCIs 210.

[0087] In performing the multi-stage contention resolution procedure described herein, the UE 115-a may follow the timeline 220 so that the UE 115-a has time to determine which overlapping UCI 210 or uplink data 215 should be prioritized. For example, when the network entity 105-a schedules two overlapping UCIs 210, which may trigger the UE 115-a to perform an intra-UE multiplexing or prioritization procedure, the network entity 105-a may use the timeline 220 to give the UE 115-a enough time to perform the procedure. In some examples, for an intra-UE multiplexing procedure, a reference time 225 may be defined, which may indicate the time of the earliest overlap between the UCIs 210. Any uplink grant 235 (e.g., scheduling the transmission of the uplink data 215) may then be issued for at least the time Tproc,2 Any downlink grant 240 and corresponding physical downlink shared channel (PDSCH) 245 may arrive before the reference time 225 by at least a time T proc,1 The timeline 220 may arrive before the reference time 225 only if the uplink grant 235 and the downlink grant 240 arrive before the reference time 225 (e.g., within a certain processing time). Thus, as long as the uplink grant 235 and the downlink grant 240 arrive before the reference time 225 (e.g., within a certain processing time), the UE 115-a may maintain the ability to multiplex the overlapping UCI 210. In some examples, any transmission of the PUSCH 230 (which may carry, e.g., uplink data 215), the ACK 250, the CSI 255, the SR 260, or any combination thereof (which may be carried, e.g., in the UCI 210) may be performed by the UE 115-a after the reference time 225 according to a multi-stage contention resolution procedure. In addition, the timeline 220 may apply to intra-UE multiplexing procedures across different priorities.

[0088] 3 illustrates an example of a multi-stage contention resolution procedure 300 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. In some examples, the multi-stage contention resolution procedure 300 may be implemented by aspects of the wireless communications systems 100 and 200. For example, the multi-stage contention resolution procedure 300 may include a prioritization procedure (e.g., a repeated transmission prioritization procedure), intra-UE multiplexing, or both, and the UE may use the multi-stage contention resolution procedure 300 to resolve overlapping PUCCHs or overlapping PUCCHs and PUSCHs.

[0089] As described herein, the UE may use a multi-stage contention resolution procedure to resolve overlaps between PUCCHs (e.g., carrying UCI) or between PUCCHs and PUSCHs (e.g., carrying uplink data). If overlapping PUCCHs are scheduled with repeated transmissions by a network entity, the UE may first resolve overlapping PUCCHs with the same priority index and then resolve overlapping PUCCHs, PUSCHs, or both with different priority indexes, where the resolution may include a prioritization procedure, intra-UE multiplexing, or both.

[0090] In the example of FIG. 3, the network entity may schedule four channels (e.g., PUCCHs) for transmission by the UE, including a high priority HARQ-ACK 305 with two repeat transmissions in slot 330-a (e.g., slot n) and slot 330-b (e.g., slot n+1), a high priority SR 310 in slot 330-b, a low priority CSI 315, and a low priority HARQ-ACK 320. To resolve overlapping channels, the UE may first apply a first stage of a multi-stage contention resolution procedure to overlapping PUCCHs with the same priority index, independently for each priority index. That is, the UE may apply the first stage to the high priority channels (e.g., the high priority HARQ-ACK 305 and the high priority SR 310 with repeat transmissions) and separately to the low priority channels (e.g., the low priority CSI 315 and the low priority HARQ-ACK 320).

[0091] The first stage of the multi-stage contention resolution procedure for the high priority channel may be based on the difference in starting slot index or UCI type, where an earlier starting slot index may have priority over a later starting slot index, and the UCI types may be prioritized in the order of HARQ-ACK, SR, and CSI. Thus, the high priority HARQ-ACK 305 with repeat transmission may be prioritized over the high priority SR 310 because the HARQ-ACK has a higher priority UCI type than the SR, and the UE may drop the high priority SR 310. In addition, since the overlapping low priority channels do not have repeat transmissions, the UE may perform intra-UE multiplexing on the low priority CSI 315 and the low priority HARQ-ACK 320 to resolve the overlap, and the UE may multiplex the low priority CSI 315 and the low priority HARQ-ACK 320 into the resulting PUCCH. Thus, after applying the first stage of the multi-stage contention resolution procedure to the high priority channel and intra-UE multiplexing to the low priority channel, the resulting channel may include a high priority HARQ-ACK 305 with repeat transmissions in slots 330-a and 330-b, and a low priority HARQ-ACK+CSI 325 in slot 330-b. The UE may expect the resulting channel to not overlap with another PUCCH with repeat transmissions associated with the same priority index as the resulting channel.

[0092] To resolve overlap between the high priority HARQ-ACK 305 and the low priority HARQ-ACK+CSI 325, the UE may perform a second stage of a multi-stage contention resolution procedure for channels with different priorities, with the high priority HARQ-ACK 305 involving two repeated transmissions over the slot 330. For the repeated transmissions, the UE may drop or cancel the low priority HARQ-ACK+CSI 325 in favor of transmitting the high priority HARQ-ACK 305 based on the priority of the channels (e.g., the UE transmits the higher priority channel).

[0093] 4 illustrates an example of a multi-stage contention resolution procedure 400 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. In some examples, the multi-stage contention resolution procedure 400 may be implemented by aspects of the wireless communications systems 100 and 200. For example, the multi-stage contention resolution procedure 400 may include a prioritization procedure (e.g., a repeated transmission prioritization procedure), intra-UE multiplexing, or both, and the UE may use the multi-stage contention resolution procedure 400 to resolve overlapping PUCCHs or overlapping PUCCHs and PUSCHs.

[0094] As described herein, the UE may use a multi-stage contention resolution procedure to resolve overlaps between PUCCHs (e.g., carrying UCI) or PUCCHs (e.g., carrying uplink data) and PUSCHs. If overlapping PUCCHs are scheduled with repeated transmissions by a network entity, the UE may first resolve overlapping PUCCHs with the same priority index and then resolve overlapping PUCCHs, PUSCHs, or both with different priority indexes, where the resolution may include a prioritization procedure, intra-UE multiplexing, or both.

[0095] In the example of FIG. 4, the network entity may schedule four channels (e.g., PUCCHs) for transmission by the UE, including a low priority HARQ-ACK 405 with two repeat transmissions in slot 430-a (e.g., slot n) and slot 430-b (e.g., slot n+1), a low priority CSI 410 in slot 430-b, a high priority SR 415, and a high priority HARQ-ACK 320. To resolve overlapping channels, the UE may apply a first stage of a multi-stage contention resolution procedure to overlapping PUCCHs with the same priority index, independently for each priority index. That is, the UE may apply the first stage to the low priority channels (e.g., low priority HARQ-ACK 405 and low priority CSI 410 with repeat transmissions) and separately to the high priority channels (e.g., high priority SR 415 and high priority HARQ-ACK 420).

[0096] The first stage of the multi-stage contention resolution procedure for low priority channels may be based on the difference in starting slot index or UCI type, where an earlier starting slot index may have priority over a later starting slot index, and the UCI types may be prioritized in the following order: HARQ-ACK, SR, and CSI. In this manner, the low priority HARQ-ACK 405 with repeat transmission may be prioritized over the low priority CSI 410, since the HARQ-ACK has a higher priority UCI type than the CSI. Thus, the UE may drop the low priority CSI 410. In addition, since the overlapping high priority channels do not have repeat transmissions, the UE may perform an intra-UE multiplexing procedure on the high priority SR 415 and the high priority HARQ-ACK 420 to resolve the overlap, and the UE may multiplex the high priority SR 415 and the high priority HARQ-ACK 420 into the same resulting PUCCH. Thus, after applying the first stage of the multi-stage contention resolution procedure to the high priority channel and the first intra-UE multiplexing to the low priority channel, the resulting channel may include a low priority HARQ-ACK 405 with repeated transmissions in slots 430-a and 430-b, and a high priority HARQ-ACK+SR 425 in slot 430-b.

[0097] To resolve overlap between the low priority HARQ-ACK 405 and the high priority HARQ-ACK+SR 425, the UE may perform a second stage of a multi-stage contention resolution procedure for channels with different priorities, with the low priority HARQ-ACK 405 involving two repeated transmissions over the slot 430. For the repeated transmissions, the UE may at least partially cancel the low priority HARQ-ACK 405 in favor of transmitting the high priority HARQ-ACK+SR 425 based on the priority of the channels (e.g., the UE transmits the higher priority channel).

[0098] 5 illustrates an example of a multi-stage contention resolution procedure 500 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. In some examples, the multi-stage contention resolution procedure 500 may be implemented by aspects of the wireless communications systems 100 and 200. For example, the multi-stage contention resolution procedure 500 may include a prioritization procedure (e.g., a repeated transmission prioritization procedure), intra-UE multiplexing, or both, and the UE may use the multi-stage contention resolution procedure 500 to resolve overlapping PUCCHs carrying UCI, or overlapping PUCCHs and PUSCHs carrying uplink data.

[0099] In some examples, the network entity may schedule two or more repeat transmissions of a PUCCH that overlap with a PUCCH or PUSCH having different priorities. This may trigger the UE to drop the repeat transmissions of the two or more PUCCHs or to drop the second PUCCH or PUSCH based on the corresponding priority index. In some examples, the PUCCH may carry a HARQ-ACK transmission, and the repeat transmissions may be subslot-based. That is, the network entity may schedule multiple repeat transmissions of the HARQ-ACK transmission across multiple subslots 505. A slot may be divided into seven subslots, each having two symbols, or into two subslots, each having seven symbols. For example, a slot may include two subslots 505, subslot 505-a (e.g., subslot 0) and subslot 505-b (e.g., subslot 1), each of which may include seven symbols.

[0100] The network entity may schedule a low priority HARQ-ACK 510 with repeat transmissions in each of sub-slots 505-a and 505-b, and a single high priority HARQ-ACK 515 spanning both sub-slots 505. That is, the high priority HARQ-ACK 515 may overlap with repeat transmissions of both the low priority HARQ-ACK 515 in sub-slots 505-a and 505-b. To eliminate the overlap, the UE may at least partially cancel both the repeat transmissions of the low priority HARQ-ACK 510 and the transmission of the high priority HARQ-ACK 515 if the UE performed a prioritization procedure before intra-UE multiplexing that may enable the UE to eliminate overlapping channels, and some of the channels may be scheduled with repeat transmissions and some without. In this manner, the network entity may schedule multiple repeat transmissions of the low priority HARQ-ACK 510 across different subslots 505, and the UE may transmit any low priority HARQ-ACK 510 repeat transmissions that do not overlap with any other channels (e.g., in this case, the high priority HARQ-ACK 515). This allows multiple repeat transmissions to be scheduled by the network entity and transmitted by the UE even though other repeat transmissions may be canceled.

[0101] Additionally or alternatively, the network entity may schedule a high priority HARQ-ACK 520 with repeat transmissions in each of sub-slots 505-c and 505-d, and a single low priority PUSCH 525 spanning both sub-slots 505. That is, the low priority PUSCH 525 may overlap with both repeat transmissions of sub-slot 505-c and the high priority HARQ-ACK 520 in sub-slot 505-c. To eliminate the overlap, the UE may at least partially cancel the low priority PUSCH 525 and transmit both repeat transmissions of the high priority HARQ-ACK 520 if the UE performed a prioritization procedure before intra-UE multiplexing that may enable the UE to eliminate overlapping channels, some of the channels may be scheduled with repeat transmissions and some without.

[0102] 6 illustrates an example of a multi-stage contention resolution procedure 600 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. In some examples, the multi-stage contention resolution procedure 600 may be implemented by aspects of the wireless communications systems 100 and 200. For example, the multi-stage contention resolution procedure 600 may include a prioritization procedure (e.g., a repeated transmission prioritization procedure), intra-UE multiplexing, or both, and the UE may use the multi-stage contention resolution procedure 600 to resolve overlapping PUCCHs carrying UCI, or overlapping PUCCHs and PUSCHs carrying uplink data.

[0103] In some examples, a network entity may schedule overlapping PUCCHs to be transmitted by a UE, and the overlapping PUCCHs may have the same priority index or different priority indexes. As described with reference to FIG. 2, any overlapping PUCCHs within a given time unit (e.g., slot, subslot) may fill an intra-UE multiplexing timeline. In some examples, the high priority channel and the low priority channel may be configured with different time units. For example, the high priority channel may be configured with a subslot-based time length, and the low priority channel may be configured with a slot-based time length. Alternatively, the high priority channel may be configured with a slot-based time length, and the low priority channel may be configured with a subslot-based time length. When the overlapping high priority channel and the low priority channel are configured with different time units, the UE may use a prioritization procedure (e.g., a repeat transmission prioritization procedure), intra-UE multiplexing, or a combination thereof to identify the time unit in which to resolve the overlapping channels, which may be the time unit corresponding to the high priority channel.

[0104] In determining whether to associate overlapping high and low priority channels (e.g., overlapping PUCCH or overlapping PUCCH and PUSCH) with a high priority time unit (e.g., slot, sub-slot), the UE may use a set of rules to associate a low priority channel with a high priority time unit. In some examples, the association may be based on the first overlapping high priority time unit as the time unit for the low priority channel. That is, the low priority channel may be associated with the first overlapping high priority time unit that includes any overlapping high priority channel. In some other examples, the association may be based on the first overlapping high priority time unit that includes a high priority HARQ-ACK. If no HARQ-ACK transmission is scheduled, the association may be based on the first overlapping high priority time unit regardless of the UCI type. In some cases, the association may be based on the last overlapping high priority time unit. That is, the time unit associated with the last high priority channel that overlaps with another channel may be associated with the low priority channel.

[0105] The UE may associate a low priority channel with a high priority time unit using association conditions at different stages during a multi-stage contention resolution procedure. In some examples, the UE may associate a low priority channel with a high priority time unit before resolving any overlapping channels having the same priority (e.g., before resolving a group of low priority or high priority overlapping channels). Thus, the UE may associate each overlapping low priority channel with a high priority time unit. In some examples, two overlapping low priority channels may be associated with two different high priority time units. In such a case, although the two low priority channels overlap, the UE may refrain from multiplexing the two low priority channels together in an intra-UE multiplexing procedure because they are associated with different high priority time units.

[0106] In some cases, the UE may associate a low priority channel with a high priority time unit after performing a collision resolution procedure (e.g., a prioritization procedure or an intra-UE multiplexing procedure) for a group of overlapping channels that share the same low priority. That is, any resulting / remaining low priority channels may not overlap with each other when the UE associates the low priority channel with the high priority time unit. In this manner, the UE may multiplex UCI together in the overlapping low priority channels before associating the low priority channel with the high priority time unit, and the resulting channel of the multiplexing may be associated with the high priority time unit.

[0107] In the example of FIG. 6, a network entity may schedule multiple channels to be transmitted by a UE over a high priority time unit. The high priority time unit may include a slot or sub-slot, and the slot may be divided into sub-slot 605-a (e.g., sub-slot 0) and sub-slot 605-b (e.g., sub-slot 1). For example, the network entity may schedule a low priority HARQ-ACK 610 spanning sub-slot 605-a and sub-slot 605-b (e.g., the entire slot), a low priority CSI 615 in sub-slot 605-b, a high priority HARQ-ACK 620-a (e.g., high priority HARQ-ACK1, or a first high priority HARQ-ACK) in sub-slot 605-a, and a high priority HARQ-ACK 620-b (e.g., high priority HARQ-ACK2, or a second high priority HARQ-ACK) in sub-slot 605-b. In some examples, the high priority HARQ-ACK 620-b may be a repeated transmission of the high priority HARQ-ACK 620-a. In some examples, the high priority HARQ-ACK 620-a and the high priority HARQ-ACK 620-b may be different transmissions.

[0108] In some cases, based on identifying overlapping channels in sub-slot 605, the UE may first resolve overlapping channels having the same low priority. For example, since the low priority channels (e.g., low priority HARQ-ACK 610 and low priority CSI 615) do not have repeated transmissions and share the same low priority, the UE may perform intra-UE multiplexing to multiplex the low priority HARQ-ACK 610 and the low priority CSI 615 into the low priority HARQ-ACK+CSI 625 (e.g., the same channel). After performing intra-UE multiplexing, the UE may determine how to associate the resulting low priority HARQ-ACK+CSI 625 with a high priority time unit (e.g., sub-slot 605-a or sub-slot 605-b). For example, the UE may associate the low priority HARQ-ACK+CSI 625 with sub-slot 605-a, which is the time unit associated with the first overlapping high priority channel (e.g., high priority HARQ-ACK 620-a). Thus, the UE may multiplex a low priority HARQ-ACK 610 and a low priority CSI 615 into sub-slot 605-a (eg, rather than across the entire slot).

[0109] In some examples, the UE may associate low priority channels (e.g., low priority HARQ-ACK 610 and low priority CSI 615) with high priority time units before resolving any overlapping channels, and each low priority channel may be associated with a different high priority time unit. For example, the UE may associate low priority HARQ-ACK 620 with sub-slot 605-a based on the first overlapping high priority time unit that includes a high priority HARQ-ACK (e.g., high priority HARQ-ACK 610-a), and the UE may associate low priority CSI 615 with sub-slot 605-a based on the last overlapping high priority time unit. The UE may then use a multi-stage contention resolution procedure to independently resolve overlapping channels on each sub-slot 605. Thus, the time in the multi-stage contention resolution procedure at which the UE associates low priority channels with high priority time units may affect the outcome of the overlapping channel resolution.

[0110] FIG. 7 illustrates an example of a process flow 700 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. The process flow 700 may implement or be implemented by aspects of the wireless communication systems 100 and 200. For example, the process flow 700 may show operations between the UE 115-b and the network entity 105-b, which may be examples of corresponding devices described herein. In the following description of the process flow 700, the operations between the UE 115-b and the network entity 105-b may be transmitted in a different order than the example order shown, or the operations performed by the UE 115-b and the network entity 105-b may be performed in a different order or at different times. Some operations may also be omitted from the process flow 700, and other operations may be added to the process flow 700.

[0111] At 705, the UE 115-b may identify one or more scheduling overlaps associated with one or more repeated transmissions of the first PUCCH. That is, the network entity 105-b may schedule multiple overlapping PUCCH transmissions carrying UCI, PUSCH transmissions carrying uplink data, or both for the UE 115-b, where at least one of the PUCCHs may be scheduled with repeated transmissions. The PUCCH and PUSCH may overlap in time, causing a collision or scheduling conflict. This scenario may trigger one or more stages of a multi-stage contention resolution procedure, which may include a prioritization procedure, an intra-UE multiplexing procedure, or a combination thereof. The multi-stage contention resolution procedure may alternatively be referred to as a multi-stage overlap resolution procedure because it addresses conflicts resulting from scheduling overlaps.

[0112] At 707, the UE 115-b may perform a first stage of a multi-stage contention resolution procedure. In the first stage, the UE 115-b may resolve any overlapping PUCCHs or repeated transmissions of PUCCHs of the same priority index. During the first stage, at 710, the UE 115-b may first apply a first prioritization procedure (e.g., a repeated transmission prioritization procedure) or a first intra-UE multiplexing procedure to a group of overlapping PUCCHs carrying UCIs with the same low priority index (e.g., associated with or having a priority index X, where X indicates low priority). Thus, the UE 115-b may first independently resolve overlapping PUCCHs for their low priority index (e.g., X). In some examples, the first prioritization procedure may be based on a set of prioritization rules that may indicate that UE 115-b prioritizes the PUCCH based on a starting slot index (e.g., the time when the PUCCH is scheduled to begin transmission) or a UCI type priority (e.g., the priority of the type of UCI, including HARQ-ACK, SR, or CSI, carried in the PUCCH).

[0113] In some examples, during the first stage, UE 115-b may apply a first intra-UE multiplexing procedure to a group of overlapping PUCCHs having a low priority index (e.g., having priority index X) with repetitive transmission, if applicable. That is, if at least one of the overlapping PUCCHs is scheduled with repetitive transmission, UE 115-b may multiplex the UCI of the overlapping PUCCHs into one PUCCH to eliminate overlaps.

[0114] During the first stage, at 715, the UE 115-b may apply a second prioritization procedure or a second intra-UE multiplexing procedure for groups of overlapping PUCCHs having the same high priority index (e.g., associated with or having a priority index Y, where Y indicates a low priority). Thus, the UE 115-b may independently resolve overlapping PUCCHs for a high priority index (e.g., Y). In some examples, the second prioritization procedure may be based on a set of prioritization rules that may indicate that the UE 115-b prioritizes the PUCCHs based on a starting slot index (e.g., a time when the PUCCH is scheduled to start being transmitted) or a UCI type priority (e.g., a priority of a type of UCI, including HARQ-ACK, SR, or CSI, carried in the PUCCH).

[0115] In some examples, during the first stage, UE 115-b may apply a second intra-UE multiplexing procedure to a group of overlapping PUCCHs having the same high priority (e.g., having priority index X) with repetitive transmission, if applicable. That is, if at least one of the overlapping PUCCHs is scheduled with repetitive transmission, UE 115-b may multiplex the UCI of the overlapping PUCCHs into one PUCCH to eliminate overlaps.

[0116] At 720, the UE 115-b may perform a second stage of a multi-stage contention resolution procedure to resolve any overlapping PUCCHs carrying repeated transmissions of UCI or PUCCHs of different priority indices. For example, the UE 115-b may apply a third prioritization procedure to any overlapping PUCCHs having different priorities (e.g., a low priority PUCCH and a high priority PUCCH). If any of the overlapping PUCCHs are scheduled with repeated transmissions, the UE 115-b may resolve any overlap between the PUCCH with repeated transmission and other PUCCHs based on the priority of each PUCCH. For example, the UE 115-b may at least partially cancel or drop the overlapping PUCCHs with lower priority indices.

[0117] After the third prioritization procedure during the second stage, the UE 115-b may apply a third intra-UE multiplexing procedure among PUCCHs with different priorities. If any of the overlapping PUCCHs is not scheduled with repetitive transmission, the UE 115-a may multiplex the UCI of the overlapping PUCCHs into one PUCCH to eliminate the overlap.

[0118] At 725, the UE 115-b may perform a third stage of a multi-stage contention resolution procedure to resolve any overlapping PUCCHs carrying UCI and PUSCHs carrying uplink data, which may be associated with different priority indices from the PUCCHs and PUSCHs. That is, during the third stage, the UE 115-b may resolve any overlapping PUCCHs and PUSCHs remaining after the first and second stages. The UE 115-b may apply a fourth prioritization procedure to any overlapping PUCCHs and PUSCHs having different priorities. If the overlapping PUCCHs are scheduled with recurring transmissions, the UE 115-b may resolve the overlap between the PUCCHs and PUSCHs based on the respective priorities of the PUCCHs and PUSCHs. For example, the UE 115-b may at least partially cancel or drop the PUSCH if the PUSCH has a lower priority than the PUCCH.

[0119] After the fourth prioritization procedure of the third stage, the UE 115-b may apply a fourth intra-UE multiplexing procedure to overlapping PUCCH and PUSCH with different priorities. If there is no scheduling with repetitive transmission in the PUCCH, the UE 115-b may piggyback the UCI in the PUCCH onto the PUSCH to eliminate the overlap.

[0120] At 730, based on resolving overlaps in accordance with the multi-stage contention resolution procedure, the UE 115-b may selectively transmit at least a portion of a PUCCH (e.g., UCI) or PUSCH (e.g., uplink data) transmission to the network entity 105-b in accordance with the prioritization procedure and intra-UE multiplexing.

[0121] 8 illustrates a block diagram 800 of a device 805 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the disclosure. The device 805 may be an example of an aspect of a UE 115 described herein. The device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. The device 805 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

[0122] The receiver 810 may provide a means for receiving information, such as packets, user data, control information, or any combination thereof, associated with various traffic channels (e.g., a control channel, a data channel, a traffic channel associated with managing overlap between repeated transmissions of an uplink control channel and an uplink data transmission). The information may be passed to other components of the device 805. The receiver 810 may utilize a single antenna or a set of multiple antennas.

[0123] The transmitter 815 may provide a means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel associated with managing overlap between repeated transmissions of an uplink control channel and an uplink data transmission), user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 within a transceiver module. The transmitter 815 may utilize a single antenna or a set of multiple antennas.

[0124] The communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be examples of means for performing various aspects of managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions described herein. For example, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0125] In some examples, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof, may be implemented in hardware (e.g., in a communications management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0126] Additionally or alternatively, in some examples, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software). If implemented in code executed by a processor, the functions of the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as a means for performing, or in some cases supporting, the functions described in this disclosure).

[0127] In some examples, the communications manager 820 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communications manager 820 may receive information from the receiver 810 and transmit information to the transmitter 815, or may be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations described herein.

[0128] For example, the communications manager 820 may be configured as or otherwise support a means for performing one or more stages of a multi-stage overlap resolution procedure based on a scheduling overlap between one or more repeated transmissions of a first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI. The one or more stages of the multi-stage overlap resolution procedure may include a first stage, a second stage, and a third stage. The first stage may be based on a difference between the overlapping UCIs of the same priority index, where the overlapping UCIs include one or more of the first UCI, a second UCI associated with a priority index of the first UCI, or at least a portion of the one or more overlapping uplink transmissions. The second stage may be based on overlap resolution between the first UCI and a third UCI associated with a priority index different from the priority index of the first UCI, where the first UCI and the third UCI are associated with one or more overlapping uplink transmissions. The third stage may be based on overlap resolution between the first UCI and an uplink data transmission associated with a priority index different from a priority index of the first UCI, the first UCI and the uplink data transmission being associated with one or more overlapping uplink transmissions. The communications manager 820 may be configured as or otherwise support a means for transmitting at least a portion of the first UCI or the one or more overlapping uplink transmissions according to one or more stages of a multi-stage overlap resolution procedure.

[0129] By including or configuring the communications manager 820 according to examples described herein, the device 805 (e.g., a processor controlling or otherwise coupled to the receiver 810, the transmitter 815, the communications manager 820, or a combination thereof) may support techniques for managing overlapping uplink control channel repeat transmissions and uplink data transmissions, which may increase the number of repeat transmissions of a channel that a UE may transmit using the transmitter 815 instead of dropping, thereby increasing the transmission success rate and allowing a network entity to schedule more repeat transmissions.

[0130] 9 illustrates a block diagram 900 of a device 905 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the disclosure. The device 905 may be an example of aspects of the device 805 or UE 115 described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

[0131] The receiver 910 may provide a means for receiving information, such as packets, user data, control information, or any combination thereof, associated with various traffic channels (e.g., a control channel, a data channel, a traffic channel associated with managing overlap between repeated transmissions of an uplink control channel and an uplink data transmission). The information may be passed to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.

[0132] The transmitter 915 can provide a means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 can transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel associated with managing overlap between repeated transmissions of an uplink control channel and an uplink data transmission), user data, control information, or any combination thereof. In some examples, the transmitter 915 may be co-located with the receiver 910 within a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.

[0133] The device 905 or various components thereof may be examples of means for performing various aspects of managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions as described herein. For example, the communications manager 920 may include an overlap resolution component 925, a transmission component 930, or any combination thereof. The communications manager 920 may be an embodiment of aspects of the communications manager 820 described herein. In some examples, the communications manager 920 or various components thereof may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910 and transmit information to the transmitter 915, or may be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations described herein.

[0134] The overlap resolution component 925 may be configured as or otherwise support a means for performing one or more stages of a multi-stage overlap resolution procedure based on a scheduling overlap between one or more repeated transmissions of a first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI. The one or more stages of the multi-stage overlap resolution procedure may include a first stage, a second stage, and a third stage. The first stage component 935 may be configured as or otherwise support a means for performing a first stage based on a difference between overlapping UCIs of the same priority index, the overlapping UCIs including one or more of the first UCI, a second UCI associated with a priority index of the first UCI, or at least a portion of the one or more overlapping uplink transmissions. The second stage component 940 may be configured as or otherwise support a means for performing the second stage based on overlap resolution between the first UCI and a third UCI associated with a priority index different from the priority index of the first UCI, the first UCI and the third UCI being associated with one or more overlapping uplink transmissions. The third stage component 945 may be configured as or otherwise support a means for performing the third stage based on overlap resolution between the first UCI and an uplink data transmission associated with a priority index different from the priority index of the first UCI, the first UCI and the uplink data transmission being associated with one or more overlapping uplink transmissions. The transmitting component 930 may be configured as or otherwise support a means for transmitting at least a portion of the first UCI or one or more overlapping uplink transmissions according to one or more stages of a multi-stage overlap resolution procedure.

[0135] FIG. 10 illustrates a block diagram 1000 of a communications manager 1020 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, according to one or more aspects of the disclosure. The communications manager 1020 may be an example of an aspect of the communications manager 820, the communications manager 920, or both, described herein. The communications manager 1020, or various components thereof, may be an example of a means for performing various aspects of managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, as described herein. For example, the communications manager 1020 may include an overlap resolution component 1025, a transmission component 1030, a first stage component 1035, a second stage component 1040, a third stage component 1045, an uplink grant receiving component 1050, a downlink transmission receiving component 1055, a time unit allocation component 1060, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0136] The overlap resolution component 1025 may be configured as or otherwise support a means for performing one or more stages of a multi-stage overlap resolution procedure based on a scheduling overlap between one or more repeated transmissions of a first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI. The one or more stages of the multi-stage overlap resolution procedure may include a first stage, a second stage, and a third stage. The first stage component 1035 may be configured as or otherwise support a means for performing the first stage based on a difference between overlapping UCIs of the same priority index, the overlapping UCIs including one or more of the first UCI, a second UCI associated with a priority index of the first UCI, or at least a portion of the one or more overlapping uplink transmissions. The second stage component 1040 may be configured as or otherwise support a means for performing the second stage based on overlap resolution between the first UCI and a third UCI associated with a priority index different from the priority index of the first UCI, the first UCI and the third UCI being associated with one or more overlapping uplink transmissions. The third stage component 1045 may be configured as or otherwise support a means for performing the third stage based on overlap resolution between the first UCI and an uplink data transmission associated with a priority index different from the priority index of the first UCI, the first UCI and the uplink data transmission being associated with one or more overlapping uplink transmissions. The transmitting component 1030 may be configured as or otherwise support a means for transmitting at least a portion of the first UCI or one or more overlapping uplink transmissions according to one or more stages of the multi-stage overlap resolution procedure.

[0137] In some examples, to support performing one or more stages of a multi-stage duplicate resolution procedure, the first stage component 1035 may be configured as or otherwise support a means for performing the first stage separately for each priority index of a set of multiple priority indexes.

[0138] In some examples, to support performing one or more stages of a multi-stage overlap resolution procedure, the second stage component 1040 may be configured as or otherwise support a means for selectively dropping either one repeat transmission of the one or more repeat transmissions of the first UCI or the third UCI during the second stage, the dropping being based on a priority index of the first UCI and a priority index of the third UCI.

[0139] In some examples, to support performing one or more stages of a multi-stage overlap resolution procedure, the third stage component 1045 may be configured as or otherwise support a means for selectively dropping either a repeat transmission of one of the one or more repeat transmissions of the first UCI or an uplink data transmission during the third stage, the dropping being based on a priority index of the first UCI and a priority index of the uplink data transmission.

[0140] In some examples, to support transmitting at least a portion of the first UCI, the transmitting component 1030 may be configured with or otherwise support a means for selectively dropping one repeat transmission of the one or more repeat transmissions of the first UCI and transmitting a remaining portion of the one or more repeat transmissions of the first UCI.

[0141] In some examples, the uplink grant receiving component 1050 may be configured as or otherwise support a means for receiving an uplink grant for an uplink data transmission within a first processing time defined for the UE. In some examples, the downlink transmission receiving component 1055 may be configured as or otherwise support a means for receiving a downlink transmission that triggers one or more of the first UCI, the second UCI, or the third UCI within a second processing time defined for the UE. In some examples, one or both of the second UCI or the third UCI do not have a repeat transmission.

[0142] In some examples, to support performing one or more stages of a multi-stage overlap resolution procedure, the second stage component 1040 may be configured as or otherwise support a means for dropping a set of multiple repeat transmissions of the one or more repeat transmissions of the first UCI during the second stage when the third UCI is scheduled to overlap with a set of multiple repeat transmissions of the one or more repeat transmissions of the first UCI and the priority index of the first UCI indicates a lower priority than the priority index of the third UCI.

[0143] In some examples, to support performing one or more stages of a multi-stage overlap resolution procedure, the second stage component 1040 may be configured with, or may possibly support, a means for dropping the third UCI during the second stage when the third UCI is scheduled to overlap with a set of multiple repeated transmissions of the one or more repeated transmissions of the first UCI and the priority index of the first UCI indicates a higher priority than the priority index of the second UCI.

[0144] In some examples, to support performing one or more stages of a multi-stage overlap resolution procedure, the third stage component 1045 may be configured with, or may possibly support, a means for dropping, during the third stage, the set of multiple repeat transmissions of the one or more repeat transmissions of the first UCI when an uplink data transmission is scheduled to overlap with a set of multiple repeat transmissions of the one or more repeat transmissions of the first UCI and the priority index of the first UCI indicates a lower priority than the priority index of the uplink data transmission.

[0145] In some examples, to support performing one or more stages of a multi-stage overlap resolution procedure, the third stage component 1045 may be configured as, or may possibly support, a means for dropping an uplink data transmission during the third stage when the uplink data transmission is scheduled to overlap with a set of multiple repeated transmissions of the one or more repeated transmissions of the first UCI and the priority index of the first UCI indicates a higher priority than the priority index of the uplink data transmission.

[0146] In some examples, one or more of the first UCI, the second UCI, the third UCI, or the uplink data transmission are scheduled using a first time unit that is longer than the second time unit, and another of the first UCI, the second UCI, or the uplink data transmission is scheduled using the second time unit.

[0147] In some examples, the time unit allocation component 1060 may be configured with or otherwise support a means for allocating one or more of the first UCI, the second UCI, the third UCI, or an uplink data transmission to a time period corresponding to the second time unit prior to performing the first stage of the multi-stage overlap resolution procedure.

[0148] In some examples, the time unit allocation component 1060 may be configured as or otherwise support a means for allocating one or more of the first UCI, the second UCI, the third UCI, or the uplink data transmission to a time period corresponding to a second time unit between performing the first stage and performing the second stage of the multi-stage overlap resolution procedure.

[0149] In some examples, the first stage is based on the difference in starting slot index or UCI type between overlapping UCIs of the same priority index.

[0150] 11 illustrates an illustration of a system 1100 including a device 1105 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the disclosure. The device 1105 may be or may include an embodiment of components of a device 805, a device 905, or a UE 115 described herein. The device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1105 may include components for two-way voice and data communication, including components for transmitting and receiving communications, such as a communications manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, code 1135, and a processor 1140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1145).

[0151] The I / O controller 1110 may manage input and output signals for the device 1105. The I / O controller 1110 may also manage peripheral devices that are not integrated with the device 1105. In some cases, the I / O controller 1110 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1110 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I / O controller 1110 may represent or be able to interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 1110 may be implemented as part of a processor, such as the processor 1140. In some cases, a user may interact with the device 1105 through the I / O controller 1110 or through hardware components controlled by the I / O controller 1110 .

[0152] In some cases, the device 1105 may include a single antenna 1125. However, in some other cases, the device 1105 may have two or more antennas 1125, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 1115 may communicate bidirectionally via one or more antennas 1125, wired links, or wireless links as described herein. For example, the transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1115 may also include a modem for modulating packets and providing the modulated packets to the one or more antennas 1125 for transmission, and for demodulating packets received from the one or more antennas 1125. The transceiver 1115, or the transceiver 1115 and one or more antennas 1125, may be an example of the transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination or components thereof described herein.

[0153] The memory 1130 may include random access memory (RAM) and read-only memory (ROM). The memory 1130 may store computer-readable computer-executable code 1135 including instructions that, when executed by the processor 1140, cause the device 1105 to perform various functions described herein. The code 1135 may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some cases, the code 1135 may not be directly intended for the processor 1140, but may (e.g., when compiled and executed) cause a computer to perform functions described herein. In some cases, the memory 1130 may include a basic I / O system (BIOS) that may control basic hardware or software operations, such as interactions with peripheral components or devices, among other things.

[0154] The processor 1140 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a GPU, 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 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated with the processor 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions). For example, the device 1105 or components of the device 1105 may include the processor 1140 and the memory 1130 coupled or coupled to the processor 1140, where the processor 1140 and the memory 1130 are configured to perform various functions described herein.

[0155] For example, the communications manager 1120 may be configured as or otherwise support a means for performing one or more stages of a multi-stage overlap resolution procedure based on a scheduling overlap between one or more repeated transmissions of a first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI. The one or more stages of the multi-stage overlap resolution procedure may include a first stage, a second stage, and a third stage. The first stage may be based on a difference between the overlapping UCIs of the same priority index, where the overlapping UCIs include one or more of the first UCI, a second UCI associated with a priority index of the first UCI, or at least a portion of the one or more overlapping uplink transmissions. The second stage may be based on overlap resolution between the first UCI and a third UCI associated with a priority index different from the priority index of the first UCI, where the first UCI and the third UCI are associated with one or more overlapping uplink transmissions. The third stage is based on overlap resolution between the first UCI and an uplink data transmission associated with a priority index different from the priority index of the first UCI, where the first UCI and the uplink data transmission are associated with one or more overlapping uplink transmissions. The communications manager 1120 may be configured as or otherwise support a means for transmitting at least a portion of the first UCI or the one or more overlapping uplink transmissions according to one or more stages of a multi-stage overlap resolution procedure.

[0156] By including or configuring a communications manager 1120 according to examples described herein, the device 1105 may support techniques for managing overlapping uplink control channel repeat transmissions and uplink data transmissions, which may increase the number of repeat transmissions of a channel that a UE may transmit using the transmitter 1115 instead of dropping, thereby increasing the transmission success rate and allowing network entities to schedule more repeat transmissions.

[0157] In some embodiments, the communications manager 1120 can be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the transceiver 1115, the one or more antennas 1125, or any combination thereof. Although the communications manager 1120 is shown as a separate component, in some embodiments, one or more functions described with respect to the communications manager 1120 may be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions for the processor 1140 to cause the device 1105 to perform various aspects of managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, as described herein, or the processor 1140 and the memory 1130 may be otherwise configured to perform or support such operations.

[0158] FIG. 12 illustrates a flow chart illustrating a method 1200 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. The operations of method 1200 may be implemented by a UE or components thereof as described herein. For example, the operations of method 1200 may be performed by a UE 115 as described with reference to FIGS. 1-11. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using dedicated hardware.

[0159] At 1205, the method may include performing one or more stages of a multi-stage overlap resolution procedure based at least in part on a scheduling overlap between one or more repeated transmissions of the first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI. The operations of 1205 may be performed according to embodiments disclosed herein. In some examples, aspects of the operations of 1205 may be performed by overlap resolution component 1025 as described with reference to FIG.

[0160] At 1210, the method may include transmitting the first UCI or at least a portion of the one or more overlapping uplink transmissions according to one or more stages of a multi-stage overlap resolution procedure. The operations of 1210 may be performed according to embodiments disclosed herein. In some embodiments, aspects of the operations of 1210 may be performed by the transmitting component 1030 described with reference to FIG.

[0161] FIG. 13 illustrates a flow chart illustrating a method 1300 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. The operations of method 1300 may be implemented by a UE or components thereof as described herein. For example, the operations of method 1300 may be performed by a UE 115 as described with reference to FIGS. 1-11. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using dedicated hardware.

[0162] At 1305, the method may include performing one or more stages of a multi-stage overlap resolution procedure based at least in part on a scheduling overlap between one or more repeated transmissions of the first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI. The one or more stages of the multi-stage overlap resolution procedure may include a first stage, a second stage, and a third stage. The operations of 1305 may be performed according to embodiments disclosed herein. In some examples, aspects of the operations of 1305 may be performed by an overlap resolution component 1025 as described with reference to FIG. 10.

[0163] At 1310, the method may include performing a first stage of a multi-stage overlap resolution procedure, the first stage being based at least in part on a difference between overlapping UCIs of the same priority index, the overlapping UCIs including one or more of a first UCI, a second UCI associated with a priority index of the first UCI, or at least a portion of one or more overlapping uplink transmissions. The operations of 1310 may be performed according to embodiments disclosed herein. In some examples, aspects of the operations of 1310 may be performed by an overlap resolution component 1025 as described with reference to FIG. 10.

[0164] At 1315, the method may include performing a first stage of a multi-stage overlap resolution procedure, the second stage being based at least in part on overlap resolution between the first UCI and a third UCI associated with a priority index different from the priority index of the first UCI and associated with the first and third UCI and one or more overlapping uplink transmissions. The operations of 1315 may be performed according to embodiments disclosed herein. In some examples, aspects of the operations of 1315 may be performed by overlap resolution component 1025 as described with reference to FIG. 10.

[0165] At 1320, the method may include performing a third stage of a multi-stage overlap resolution procedure, the third stage being based at least in part on overlap resolution between the first UCI and an uplink data transmission associated with a priority index different from a priority index of the first UCI, where the first UCI and the uplink data transmission are associated with one or more overlapping uplink transmissions. The operations of 1320 may be performed according to embodiments disclosed herein. In some examples, aspects of the operations of 1320 may be performed by overlap resolution component 1025 as described with reference to FIG. 10.

[0166] At 1325, the method may include transmitting the first UCI or at least a portion of the one or more overlapping uplink transmissions according to one or more stages of a multi-stage overlap resolution procedure. The operations of 1325 may be performed according to embodiments disclosed herein. In some embodiments, aspects of the operations of 1325 may be performed by the transmitting component 1030 described with reference to FIG.

[0167] FIG. 14 illustrates a flow chart illustrating a method 1400 that supports managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in accordance with one or more aspects of the present disclosure. The operations of method 1400 may be performed by a UE or components thereof as described herein. For example, the operations of method 1400 may be performed by a UE 115 as described with reference to FIGS. 1-11. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using dedicated hardware.

[0168] At 1405, the method may include performing one or more stages of a multi-stage overlap resolution procedure based at least in part on a scheduling overlap between one or more repeated transmissions of the first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI, where one or more of the first UCI, the second UCI, the third UCI, or the uplink data transmission may be scheduled using a first time unit that is longer than the second time unit, and another of the first UCI, the second UCI, or the uplink data transmission may be scheduled using the second time unit. The operations of 1405 may be performed according to embodiments disclosed herein. In some examples, aspects of the operations of 1405 may be performed by the overlap resolution component 1025 as described with reference to FIG. 10.

[0169] At 1410, the method may include allocating one or more of the first UCI, the second UCI, the third UCI, or the uplink data transmission to a time period corresponding to the second time unit prior to performing the first stage of the multi-stage overlap resolution procedure. The operations of 1410 may be performed according to embodiments disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a time unit allocation component 1060, as described with reference to FIG. 10.

[0170] At 1415, the method may include allocating one or more of the first UCI, the second UCI, the third UCI, or the uplink data transmission to a time period corresponding to a second time unit between performing the first stage and performing the second stage of the multi-stage overlap resolution procedure. The operations of 1415 may be performed according to embodiments disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a time unit allocation component 1060, as described with reference to FIG. 10.

[0171] At 1420, the method may include transmitting the first UCI or at least a portion of the one or more overlapping uplink transmissions according to one or more stages of a multi-stage overlap resolution procedure. The operations of 1420 may be performed according to embodiments disclosed herein. In some embodiments, aspects of the operations of 1420 may be performed by the transmitting component 1030 described with reference to FIG.

[0172] The following provides a summary of aspects of the disclosure.

[0173] Aspect 1: A method of wireless communication in a UE, comprising: one or more stages of a multi-stage overlap resolution procedure based at least in part on a scheduling overlap between one or more repeated transmissions of a first UCI and one or more overlapping uplink transmissions associated with a priority index different from the first UCI, the first stage being based at least in part on a difference between the overlapping UCIs of the same priority index, the overlapping UCIs including one or more of the first UCI, a second UCI associated with a priority index of the first UCI, or at least a portion of the one or more overlapping uplink transmissions; and a second stage being based at least in part on a scheduling overlap between the first UCI and one or more repeated transmissions of a first UCI and one or more overlapping uplink transmissions associated with a priority index different from the priority index of the first UCI. a second stage based at least in part on overlap resolution between the first UCI and an uplink data transmission associated with a priority index different from a priority index of the first UCI, where the first UCI and the uplink data transmission are associated with one or more overlapping uplink transmissions; and transmitting at least a portion of the first UCI or the one or more overlapping uplink transmissions in accordance with the one or more stages of the multi-stage overlap resolution procedure.

[0174] Aspect 2: The method of aspect 1, wherein performing one or more stages of a multi-stage duplicate resolution procedure includes performing a first stage separately for each priority index of the multiple priority indexes.

[0175] Aspect 3: The method of aspect 1 or 2, wherein performing one or more stages of a multi-stage overlap resolution procedure further includes selectively dropping either one repeat transmission of the one or more repeat transmissions of the first UCI or the third UCI during a second stage, wherein the dropping is based at least in part on a priority index of the first UCI and a priority index of the third UCI.

[0176] Aspect 4: The method of any of aspects 1 to 3, wherein performing one or more stages of a multi-stage overlap resolution procedure further includes selectively dropping either one of a repeat transmission of the one or more repeat transmissions of the first UCI or an uplink data transmission during a third stage, wherein the dropping is based at least in part on a priority index of the first UCI and a priority index of the uplink data transmission.

[0177] Aspect 5: A method as described in any of aspects 1 to 4, wherein transmitting at least a portion of the first UCI includes selectively dropping one repeat transmission of the one or more repeat transmissions of the first UCI and transmitting a remaining portion of the one or more repeat transmissions of the first UCI.

[0178] Aspect 6: A method according to any of aspects 1 to 5, further comprising: receiving an uplink grant for an uplink data transmission within a first processing time defined for the UE; and receiving a downlink transmission triggering one or more of the first UCI, the second UCI, or the third UCI within a second processing time defined for the UE.

[0179] Aspect 7: The method of any of aspects 1 to 6, wherein one or both of the second UCI or the third UCI does not have a repeat transmission.

[0180] Aspect 8: A method according to any of aspects 1 to 7, wherein performing one or more stages of a multi-stage overlap resolution procedure further includes dropping, during the second stage, more than one repeat transmission of the one or more repeat transmissions of the first UCI when the third UCI is scheduled to overlap with more than one repeat transmission of the one or more repeat transmissions of the first UCI and a priority index of the first UCI indicates a lower priority than the priority index of the third UCI.

[0181] Aspect 9: A method as described in any of aspects 1 to 8, wherein performing one or more stages of a multi-stage overlap resolution procedure further includes dropping the third UCI during the second stage when the third UCI is scheduled to overlap with multiple repeated transmissions of the one or more repeated transmissions of the first UCI and a priority index of the first UCI indicates a higher priority than a priority index of the second UCI.

[0182] Aspect 10: A method according to any of aspects 1 to 9, wherein performing one or more stages of a multi-stage overlap resolution procedure further includes dropping, during a third stage, the multiple repeat transmissions of the one or more repeat transmissions of the first UCI when an uplink data transmission is scheduled to overlap with the multiple repeat transmissions of the one or more repeat transmissions of the first UCI and a priority index of the first UCI indicates a lower priority than a priority index of the uplink data transmission.

[0183] Aspect 11: A method according to any of aspects 1 to 10, wherein performing one or more stages of a multi-stage overlap resolution procedure further includes dropping the uplink data transmission during a third stage when the uplink data transmission is scheduled to overlap with multiple repeated transmissions of the one or more repeated transmissions of the first UCI and a priority index of the first UCI indicates a higher priority than a priority index of the uplink data transmission.

[0184] Aspect 12: A method according to any of aspects 1 to 11, wherein one or more of the first UCI, the second UCI, the third UCI, or the uplink data transmission are scheduled using a first time unit that is longer than the second time unit, and another of the first UCI, the second UCI, or the uplink data transmission is scheduled using the second time unit.

[0185] Aspect 13: The method of aspect 12, further comprising allocating one or more of the first UCI, the second UCI, the third UCI, or the uplink data transmission to a time period corresponding to the second time unit prior to performing the first stage of the multi-stage overlap resolution procedure.

[0186] Aspect 14: The method of aspect 12 or 13, further comprising allocating one or more of the first UCI, the second UCI, the third UCI, or the uplink data transmission to a time period corresponding to a second time unit between performing the first stage and performing the second stage of the multi-stage overlap resolution procedure.

[0187] Example 15: The method of any of Examples 1 to 14, wherein the first stage is based at least in part on a difference in starting slot index or UCI type between overlapping UCIs of the same priority index.

[0188] Aspect 16: An apparatus comprising at least one processor and a memory coupled to the at least one processor, the memory storing instructions for causing the at least one processor to cause a UE to perform a method according to any of aspects 1-15.

[0189] Embodiment 17: An apparatus comprising at least one means for carrying out the method according to any one of embodiments 1 to 15.

[0190] Aspect 18: A non-transitory computer-readable medium storing code, the code comprising instructions for at least one processor to execute a method according to any of aspects 1-15.

[0191] It should be noted that the methods described herein are descriptions of possible implementations, that the acts and steps may be rearranged or otherwise modified, and that other implementations are possible. Additionally, aspects from two or more of these methods may be combined.

[0192] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described as examples and LTE, LTE-A, LTE-A Pro, or NR terminology may be used throughout much of the description, the techniques described herein may be applicable to other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies, including future systems and radio technologies not expressly mentioned herein.

[0193] The information and signals described herein may be represented using any of a wide variety of technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0194] The various example blocks and components described with respect to the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, a GPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. 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).

[0195] The functions described herein may be implemented in hardware, software executed by a processor, or any combination thereof. Software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. When implemented in software executed by a processor, the functions may be stored on or transmitted over a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed such that parts of the functions are implemented in different physical locations.

[0196] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, Electrically Erasable Programmable ROM (EEPROM), Flash memory, phase-change 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 general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer readable media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer readable media.

[0197] As used herein, including within the claims, "or" as used in a list of items (including a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or C means, for example, A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, the phrase "based on" as used herein should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" is to be interpreted in the same way as the phrase "based at least in part on". As used herein, the term "and / or", when used in a list of two or more items, means that any one of the listed items may be employed alone, or any combination of two or more of the listed items may be employed. For example, if a composition is described as containing components A, B, and / or C, the composition may contain only A, only B, only C, a combination of A and B, a combination of A and C, a combination of B and C, or a combination of A, B, and C.

[0198] The terms "determine" or "determining" or "identify" or "identifying" encompass various activities, and thus "determining" or "identifying" can include calculating, computing, processing, deriving, investigating, looking up (such as via looking in a table, database, or another data structure), or ascertaining, etc. "Determining" or "identifying" can also include receiving (receiving information or signaling, e.g., receiving information or signaling to determine, receiving information or signaling to identify, etc.) or accessing (such as accessing data in a memory or accessing information), etc. "Determining" or "identifying" can also include resolving, obtaining, selecting, choosing, establishing, and other similar acts.

[0199] In the accompanying figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between the similar components. If only a first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of a second reference label, or other subsequent reference label.

[0200] The description set forth herein with respect to the accompanying drawings describes exemplary configurations and does not necessarily represent all examples that may be implemented or fall within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purposes of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0201] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications of the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. 1. An apparatus for wireless communications for managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions in a user equipment (UE), comprising: at least one processor; a memory coupled to the at least one processor; wherein the memory includes instructions, and the at least one processor causes the UE to: one or more stages of a multi-stage overlap resolution procedure based at least in part on a scheduling overlap between multiple repeated transmissions of a first uplink control information and one or more overlapping uplink transmissions associated with a different priority index than the first uplink control information, a first stage based at least in part on deduplication between overlapping uplink control information of the same priority index, the overlapping uplink control information including the first uplink control information and second uplink control information associated with a priority index of the first uplink control information; a second stage based at least in part on overlap de-interleaving between the first uplink control information and third uplink control information associated with a priority index different from the priority index of the first uplink control information, the first uplink control information and the third uplink control information being associated with the one or more overlapping uplink transmissions; a third stage based at least in part on overlap de-interleaving between the first uplink control information and an uplink data transmission associated with a priority index different from the priority index of the first uplink control information, wherein the first uplink control information and the uplink data transmission are associated with the one or more overlapping uplink transmissions; and performing one or more stages of a multi-stage overlap elimination procedure, including: transmitting the first uplink control information or at least a portion of the one or more overlapping uplink transmissions according to the one or more stages of the multi-stage overlap resolution procedure. Includes instructions for Device.

2. The instructions for performing the one or more stages of the multi-stage overlap resolution procedure may further include the at least one processor instructing the UE to:

2. The apparatus of claim 1, for performing said first step separately for each priority index of a plurality of priority indexes.

3. The instructions for performing the one or more stages of the multi-stage overlap resolution procedure may further include the at least one processor instructing the UE to:

2. The apparatus of claim 1, wherein during the second stage, selectively dropping either one repeated transmission of the one or more repeated transmissions of the first uplink control information or the third uplink control information, the dropping being based at least in part on the priority index of the first uplink control information and the priority index of the third uplink control information.

4. The instructions for performing the one or more stages of the multi-stage overlap resolution procedure may further include the at least one processor instructing the UE to:

2. The apparatus of claim 1, wherein during the third stage, selectively dropping either one repeated transmission of the one or more repeated transmissions of the first uplink control information or the uplink data transmission, the dropping being based at least in part on the priority index of the first uplink control information and the priority index of the uplink data transmission.

5. The instructions for transmitting at least the portion of the first uplink control information may be transmitted by the at least one processor to the UE:

2. The apparatus of claim 1, wherein the apparatus is for selectively dropping one repeat transmission of the one or more repeat transmissions of the first uplink control information and transmitting a remaining portion of the one or more repeat transmissions of the first uplink control information.

6. The instructions further include causing the at least one processor to: receiving an uplink grant for the uplink data transmission within a first processing time defined for the UE; for receiving, within a second processing time defined for the UE, a downlink transmission that triggers one or more of the first uplink control information, the second uplink control information, or the third uplink control information.

10. The apparatus of claim 1.

7. The apparatus of claim 1 , wherein one or both of the second uplink control information or the third uplink control information does not have repeated transmissions.

8. The instructions for performing the one or more stages of the multi-stage overlap resolution procedure may further include the at least one processor instructing the UE to:

2. The apparatus of claim 1, wherein during the second stage, the apparatus is for dropping the multiple repeat transmissions of the one or more repeat transmissions of the first uplink control information when the third uplink control information is scheduled to overlap with multiple repeat transmissions of the one or more repeat transmissions of the first uplink control information and the priority index of the first uplink control information indicates a lower priority than the priority index of the third uplink control information.

9. The instructions for performing the one or more stages of the multi-stage overlap resolution procedure may further include the at least one processor instructing the UE to:

2. The apparatus of claim 1, for dropping the third uplink control information during the second stage when the third uplink control information is scheduled to overlap with multiple repeated transmissions of the one or more repeated transmissions of the first uplink control information and the priority index of the first uplink control information indicates a higher priority than the priority index of the second uplink control information.

10. The instructions for performing the one or more stages of the multi-stage overlap resolution procedure may further include the at least one processor instructing the UE to:

2. The apparatus of claim 1, wherein during the third stage, the apparatus is for dropping the multiple repeat transmissions of the one or more repeat transmissions of the first uplink control information when the uplink data transmission is scheduled to overlap with multiple repeat transmissions of the one or more repeat transmissions of the first uplink control information and the priority index of the first uplink control information indicates a lower priority than the priority index of the uplink data transmission.

11. The instructions for performing the one or more stages of the multi-stage overlap resolution procedure may further include the at least one processor instructing the UE to:

2. The apparatus of claim 1, wherein the apparatus is for dropping the uplink data transmission during the third stage when the uplink data transmission is scheduled to overlap with multiple repeated transmissions of the one or more repeated transmissions of the first uplink control information and the priority index of the first uplink control information indicates a higher priority than the priority index of the uplink data transmission.

12. one or more of the first uplink control information, the second uplink control information, the third uplink control information, or the uplink data transmission are scheduled using a first time unit that is longer than a second time unit, and another of the first uplink control information, the second uplink control information, or the uplink data transmission is scheduled using the second time unit; The instructions further include causing the at least one processor to: causing the one or more of the first uplink control information, the second uplink control information, the third uplink control information, or the uplink data transmission to be allocated to a time period corresponding to the second time unit before performing the first stage of the multi-stage overlap resolution procedure; The instructions further include causing the processor to cause the UE to:

2. The apparatus of claim 1, wherein the one or more of the first uplink control information, the second uplink control information, the third uplink control information, or the uplink data transmission are allocated to a time period corresponding to the second time unit between performing the first stage and performing the second stage of the multi-stage overlap resolution procedure.

13. The apparatus of claim 1 , wherein the first step is based at least in part on a difference in starting slot index or uplink control information type between the overlapping uplink control information of the same priority index.

14. 1. A method of wireless communications for managing overlap between repeated uplink control channel transmissions and uplink data transmissions in a user equipment (UE), comprising: one or more stages of a multi-stage overlap resolution procedure based at least in part on a scheduling overlap between multiple repeated transmissions of a first uplink control information and one or more overlapping uplink transmissions associated with a different priority index than the first uplink control information, a first stage based at least in part on deduplication between overlapping uplink control information of the same priority index, the overlapping uplink control information including the first uplink control information and second uplink control information associated with a priority index of the first uplink control information; a second stage based at least in part on overlap de-interleaving between the first uplink control information and third uplink control information associated with a priority index different from the priority index of the first uplink control information, the first uplink control information and the third uplink control information being associated with the one or more overlapping uplink transmissions; a third stage based at least in part on overlap de-interleaving between the first uplink control information and an uplink data transmission associated with a priority index different from the priority index of the first uplink control information, wherein the first uplink control information and the uplink data transmission are associated with the one or more overlapping uplink transmissions; and performing one or more stages of a multi-stage overlap elimination procedure, including: transmitting the first uplink control information or at least a portion of the one or more overlapping uplink transmissions according to the one or more stages of the multi-stage overlap resolution procedure; A method comprising:

15. A non-transitory computer-readable storage medium storing code for wireless communications for managing overlap between repeated transmissions of an uplink control channel and uplink data transmissions, the code including instructions, the instructions causing at least one processor to: one or more stages of a multi-stage overlap resolution procedure based at least in part on a scheduling overlap between multiple repeated transmissions of a first uplink control information and one or more overlapping uplink transmissions associated with a different priority index than the first uplink control information, a first stage based at least in part on deduplication between overlapping uplink control information of the same priority index, the overlapping uplink control information including the first uplink control information and second uplink control information associated with a priority index of the first uplink control information; a second stage based at least in part on overlap de-interleaving between the first uplink control information and third uplink control information associated with a priority index different from the priority index of the first uplink control information, the first uplink control information and the third uplink control information being associated with the one or more overlapping uplink transmissions; a third stage based at least in part on overlap de-interleaving between the first uplink control information and an uplink data transmission associated with a priority index different from the priority index of the first uplink control information, wherein the first uplink control information and the uplink data transmission are associated with the one or more overlapping uplink transmissions; and performing one or more stages of a multi-stage overlap elimination procedure, including: transmitting the first uplink control information or at least a portion of the one or more overlapping uplink transmissions according to the one or more stages of the multi-stage overlap resolution procedure. A non-transitory computer-readable storage medium.

Images