Simultaneous multi-panel uplink transmission

Abstract

The present disclosure relates to a method performed by a user equipment (UE), the method including receiving a scheduling configuration that configures the UE to perform multiple transmissions on multiple uplink (UL) resources, selecting multiple antenna panels for the multiple transmissions based on a mapping of multiple UL resources to antenna panels, and resolving time domain overlap for at least two of the multiple transmissions such that no more than one transmission is transmitted by each panel at a given time over a same component carrier (CC) on a per-panel basis. The present disclosure also relates to another method and UE.

Description

[Background technology]

[0001] Wireless communication networks provide an integrated communications platform and telecommunications services to wireless user devices. Exemplary telecommunications services include telephony, data (e.g., voice, audio, and / or video data), messaging, Internet access, and / or other services. Wireless communication networks have radio access nodes that exchange wireless signals with wireless user devices using radio network protocols such as those described in various telecommunications standards promulgated by the 3rd Generation Partnership Project (3GPP). Exemplary wireless communication networks include Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal Frequency Division Multiple Access (OFDMA) networks, Long Term Evolution (LTE), and Fifth Generation New Radio (5G NR). Wireless communication networks facilitate mobile broadband services using technologies such as OFDM, Multiple Input Multiple Output (MIMO), advanced channel coding, Massive MIMO, beamforming, and / or other features. Summary of the Invention

[0002] According to one aspect of the present disclosure, a method performed by a user equipment (UE) is disclosed that includes receiving a scheduling configuration that configures the UE to perform multiple transmissions on multiple uplink (UL) resources, selecting multiple antenna panels for the multiple transmissions based on a mapping of the multiple UL resources to the antenna panels, and resolving time-domain overlap for at least two of the multiple transmissions such that no more than one transmission is transmitted by each panel at a given time over a same component carrier (CC) on a per-panel basis.

[0003] The foregoing implementations can be implemented using a computer system including a computer-implemented method, a non-transitory computer-readable medium storing computer-readable instructions for performing the computer-implemented method, and a computer memory interoperably coupled with a hardware processor configured to execute the computer-implemented method or the instructions stored in the non-transitory computer-readable medium. Each of these and other implementations can optionally include one or more of the following features.

[0004] In some implementations, resolving the time domain overlap includes the UE determining that at least two transmissions are scheduled on a first antenna panel of the plurality, and the UE multiplexing the at least two transmissions such that the at least two transmissions are transmitted by the first antenna panel using a first UL resource of the plurality.

[0005] In some implementations, resolving the time domain overlap includes the UE dropping at least a portion of one of the at least two transmissions.

[0006] In some implementations, resolving the time domain overlap is based on signaling received from a network serving the UE, the signaling indicating which of at least two of the multiple transmissions to transmit on a per-panel basis. The signaling may be received via a downlink control information (DCI) signal or a radio resource control (RRC) signal and may indicate that a first transmission associated with multiple transmission / reception points (m-TRPs) is to be prioritized over an overlapping second transmission associated with a single TRP (s-TRP).

[0007] In some implementations, resolving the time domain overlap includes the UE determining that at least two transmissions include a recurring physical uplink control channel (PUCCH) transmission and a physical uplink shared channel (PUSCH) transmission scheduled during a first time period on a first antenna panel of the plurality, and the UE dropping the PUSCH transmission over the first antenna panel during the first time period.

[0008] According to another aspect of the present disclosure, a method performed by a UE is disclosed, the method including: receiving a scheduling configuration that configures the UE to perform multiple transmissions on multiple UL resources, selecting a plurality of antenna panels for the multiple transmissions based on a mapping of the UL resources to antenna panels, the multiple transmissions including two transmissions, the plurality of antenna panels including two antenna panels, each of the two panels corresponding to one of the two transmissions, and performing the two transmissions via the two panels.

[0009] The foregoing implementations can also be implemented using a computer system including a computer-implemented method, a non-transitory computer-readable medium storing computer-readable instructions for performing the computer-implemented method, and a computer memory interoperably coupled with a hardware processor configured to execute the computer-implemented method or the instructions stored in the non-transitory computer-readable medium. Each of these and other implementations can optionally include one or more of the following features.

[0010] In some implementations, the two transmissions are performed based on whether the two transmissions overlap in the time domain, based on whether the two transmissions overlap in the frequency domain, or based on an RRC parameter.

[0011] In some implementations, the two transmissions include two PUSCH transmissions, two PUCCH transmissions, or a PUSCH transmission and a PUCCH transmission.

[0012] In some implementations, performing the two transmissions includes the UE performing one of the two transmissions associated with a higher priority.

[0013] In some implementations, performing the two transmissions includes the UE performing one of the two transmissions that starts earlier in time or frequency, and the UE dropping the other one of the two transmissions.

[0014] In some implementations, performing the two transmissions includes the UE performing one of the two transmissions that corresponds to a preferred panel.

[0015] In some implementations, the two transmissions include two PUSCHs, and performing the two transmissions includes the UE performing one of the two transmissions that includes uplink control information (UCI).

[0016] In some implementations, the two transmissions include two PUCCHs, and performing the two transmissions includes the UE performing one of the two transmissions that includes the UCI having the higher priority.

[0017] In some implementations, the two transmissions include two PUSCHs, and performing the two transmissions includes the UE performing one of the two PUSCH transmissions using a larger size modulation and coding scheme (MCS) or using a larger size transport block (TB).

[0018] In some implementations, the two transmissions include a PUSCH and a PUCCH, and performing the two transmissions is based on signaling received from a network serving the UE. The signaling may indicate which of the two transmissions to transmit or may indicate that a first of the two transmissions associated with an m-TRP is prioritized over a second of the two transmissions associated with an s-TRP.

[0019] According to another aspect of the present disclosure, a UE is disclosed that includes a receiver that receives a scheduling configuration that configures the UE to perform multiple transmissions on multiple UL resources, and a processor that selects multiple antenna panels for the multiple transmissions based on a mapping of the multiple UL resources to the antenna panels, and resolves time domain overlap for at least two of the multiple transmissions on a per-panel basis such that no more than one transmission is transmitted by each panel at a given time over a same CC.

[0020] According to another aspect of the present disclosure, a UE is disclosed that includes: a receiver that receives a scheduling configuration that configures the UE to perform multiple transmissions on multiple UL resources, a processor that selects multiple antenna panels for the multiple transmissions based on a mapping of the multiple UL resources to antenna panels, the multiple transmissions including two transmissions, the multiple antenna panels including two antenna panels, each of the two panels corresponding to one of the two transmissions, and a transmitter that performs the two transmissions via the two panels.

[0021] Details of one or more implementations of these UEs and methods are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of these systems and methods will become apparent from the description and drawings, and from the claims. [Brief description of the drawings]

[0022] [Figure 1] 1 illustrates a wireless network according to some implementations.

[0023] [Diagram 2] 1 is a flowchart illustrating an example method for resolving time domain overlap, according to some implementations.

[0024] [Diagram 3] 1 illustrates an example for resolving time domain overlap on a panel-by-panel basis according to some implementations.

[0025] [Figure 4] 13 illustrates another example for resolving time domain overlap on a panel-by-panel basis according to some implementations.

[0026] [Diagram 5] 10A-10C each illustrate a flowchart of an example method according to some implementations. [Figure 6] 10A-10C each illustrate a flowchart of an example method according to some implementations.

[0027] [Figure 7] 1 illustrates a UE according to some implementations.

[0028] [Figure 8] 1 illustrates an access node according to some implementations. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029] To increase network coverage, reliability, and data rates, some wireless communication networks support multiple transmit / receive point (multi-TRP or m-TRP) operation. In these networks, one or more base stations may act as or otherwise utilize multiple TRPs to communicate with UEs. To facilitate multi-TRP operation, the TRP (e.g., base station) and UE may each include multiple antennas or antenna panels, with each panel having multiple antenna elements or beams. A UE that includes multiple panels is referred to as a multi-panel UE.

[0030] In general, there are two different operation modes for multi-TRP: single DCI and multi-DCI. In single DCI mode, the base station can trigger the UE to transmit one or more PUSCH repetitions (among other uplink [UL] data) towards two TRPs based on one DCI. In multi-DCI mode, the base station can trigger the UE to transmit one or more PUSCH transmissions and / or one or more PUCCH transmissions towards two TRPs based on multiple DCIs. In some scenarios, the transmissions can be scheduled such that there is a time overlap between different transmissions (which may be configured for transmissions from a single panel or multiple panels of the UE). However, existing networks do not address how a multi-panel UE operates in such scenarios where there is a time overlap between UL transmissions. This can lead to communication failures since existing 3GPP specifications do not support simultaneous transmission of PUCCH and / or PUSCH.

[0031] This disclosure describes systems and methods for resolving overlapping UL transmissions over one or more antenna panels of a multi-panel UE. The UL transmissions include those that overlap in the time domain and may occur (i) across the same panel, i.e., on a per-panel basis, or (ii) across multiple panels, i.e., on a cross-panel basis. The UL transmissions also include those transmitted on an s-TRP or (ii) an m-TRP. Among other advantages, the disclosed methods and systems improve throughput and / or reliability of UL communications.

[0032] 1 illustrates a wireless network 100 according to some implementations. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B over an air interface 108. The UE 102 and the base station 104 communicate using a system that supports control for managing access of the UE 102 to the network via the base station 104.

[0033] In some implementations, the wireless network 100 may be a non-standalone (NSA) network incorporating LTE and 5G New NR communication standards defined by 3GPP technical specifications. For example, the wireless network 100 may be an Evolved Universal Terrestrial Radio Access (E-UTRA)-NR dual connectivity (EN-DC) network or an NR-EUTRA dual connectivity (NE-DC) network. However, the wireless network 100 may also be a standalone (SA) network incorporating only 5G NR. Additionally, other types of communication standards are possible, including future 3GPP systems (e.g., sixth generation (6G)) systems, Institute of Electrical and Electronics Engineers (IEEE) 802.11 technologies (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11-2007, IEEE 802.11n, IEEE 802.11-2012, IEEE 802.11ac, or other current or future developed IEEE 802.11 technologies), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc. Although aspects may be described herein using terminology generally associated with 5G NR, aspects of the present disclosure may be applied to other systems, such as systems subsequent to 3G, 4G, and / or 5G (e.g., 6G).

[0034] In wireless network 100, UE 102 and any other UE in the system may be, for example, a laptop computer, a smartphone, a tablet computer, a machine type device such as a smart meter or a dedicated device for healthcare, an intelligent transportation system, or any other wireless device with or without a user interface. In network 100, base stations 104 provide UE 102 with network connectivity to a wider network (not shown). This UE 102 connectivity is provided via an air interface 108 within a base station coverage area provided by base station 104. In some implementations, such a wider network may be a wide area network operated by a cellular network provider or may be the Internet. Each base station coverage area associated with a base station 104 is supported by an antenna integrated with the base station 104. The coverage area is divided into multiple sectors associated with a particular antenna. Such sectors may be physically associated with a fixed antenna or may be assigned to a physical area with tunable antennas or antenna settings that can be adjusted in a beamforming process used to direct signals to a particular sector.

[0035] The UE 102 includes a control circuit 110 coupled to a transmit circuit 112 and a receive circuit 114. The transmit circuit 112 and the receive circuit 114 may each be coupled to one or more antennas. The control circuit 110 may include various combinations of application specific and baseband circuits. The transmit circuit 112 and the receive circuit 114 may be adapted to transmit and receive data, respectively, and may include radio frequency (RF) circuitry or front-end module (FEM) circuitry.

[0036] In various implementations, aspects of the transmit circuitry 112, receive circuitry 114, and control circuitry 110 may be integrated in various ways to implement the operations described herein. The control circuitry 110 may be adapted or configured to perform various operations, such as those described elsewhere in this disclosure in connection with a UE.

[0037] The transmitting circuitry 112 may perform various operations described herein. Additionally, the transmitting circuitry 112 may transmit multiple multiplexed uplink physical channels. The multiple uplink physical channels may be multiplexed by Time Division Multiplexing (TDM) or Frequency Division Multiplexing (FDM) with carrier aggregation. The transmitting circuitry 112 may be configured to receive block data from the control circuitry 110 for transmission over the air interface 108.

[0038] The receiving circuitry 114 may perform various operations described herein. Additionally, the receiving circuitry 114 may receive multiple multiplexed downlink physical channels from the air interface 108 and relay the physical channels to the control circuitry 110. The multiple downlink physical channels may be multiplexed by TDM or FDM with carrier aggregation. The transmitting circuitry 112 and the receiving circuitry 114 may transmit and receive both control data and content data (e.g., messages, images, videos, etc.) structured within data blocks carried by the physical channels.

[0039] 1 also illustrates a base station 104. In an implementation, the base station 104 may be a NG Radio Access Network (RAN) or a 5G RAN, an E-UTRAN, a non-terrestrial cell, or a legacy RAN such as a UTRAN or a GERAN. As used herein, terms such as "NG RAN" may refer to a base station 104 operating in a NR or 5G wireless network 100, and terms such as "E-UTRAN" may refer to a base station 104 operating in a LTE or 4G wireless network 100. The UE 102 utilizes connections (or channels) 106A, 106B, each of which includes a physical communication interface or layer.

[0040] The base station 104 circuitry may include a control circuit 116 coupled to a transmit circuit 118 and a receive circuit 120. The transmit circuit 118 and the receive circuit 120 may each be coupled to one or more antennas that may be used to facilitate communication over the air interface 108. The transmit circuit 118 and the receive circuit 120 may be adapted to transmit and receive data, respectively, to any UE connected to the base station 104. The transmit circuit 118 may transmit a downlink physical channel that includes multiple downlink subframes. The receive circuit 120 may receive multiple uplink physical channels from various UEs, including the UE 102.

[0041] In FIG. 1, the one or more channels 106A, 106B are depicted as air interfaces enabling a communicative coupling and may conform to a cellular communication protocol such as a GSM protocol, a CDMA network protocol, a UMTS protocol, a 3GPP LTE protocol, an Advanced Long Term Evolution (LTE-A) protocol, an LTE-based access to unlicensed spectrum (LTE-U), a 5G protocol, a NR protocol, an NR-based access to unlicensed spectrum (NR-U) protocol, and / or any of the other communication protocols described herein. In an implementation, the UE 102 may directly exchange communication data over the ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink control channel (PSCCH), a physical sidelink downlink channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0042] In line with the above description, existing systems do not address simultaneous UL transmissions in multi-panel (e.g., two panels), multi-TRP (e.g., two TRP) scenarios. Various implementations described herein provide solutions in these scenarios, including (i) when PUSCH overlaps with PUCCH on the same panel in a multi-panel multi-TRP transmission, (ii) when PUCCH overlaps with PUCCH on the same panel in a multi-panel multi-TRP transmission, and (iii) when PUCCH and PUSCH are scheduled to be transmitted simultaneously to different TRPs on different panels. In the following description, implementations that resolve overlaps on the same panel are considered on a "per-panel" basis, and implementations that resolve overlaps on different panels are considered on a "cross-panel" basis.

[0043] 2 is a flow chart illustrating an example workflow 200 for resolving time domain overlap in multi-panel multi-TRP UL transmissions, according to some implementations. The following description assumes that the method 200 is performed by a UE 102, although one skilled in the art will readily appreciate that other suitable devices or systems may be used to perform the method 200.

[0044] In step 202, workflow 200 begins for a given period (e.g., a slot or subslot). In subsequent steps of workflow 200, time domain overlap of UL transmissions is resolved on a per-panel basis and on a cross-panel basis for the given period. As described in more detail below, workflow 200 resolves the time domain overlap of UL transmissions such that no more than one UL transmission is transmitted by each of a panel of UEs 102 at a given time over the same CC.

[0045] In step 204, the UE 102 determines an association (or mapping) between each UL resource (e.g., resources for PUCCH and / or PUSCH transmission) and one or more of the UE 102's N antenna panels, where "N" represents the maximum number of available uplink panels of the UE 102. The association between a UL resource and an antenna panel indicates that the UL resource is transmitted through that panel. In one example, the association is provided to the UE 102 by a base station (e.g., base station 104) via a scheduling configuration signal. In another example, the UE 102 can select the mapping between the UL resource and the antenna panel. Specifically, the UE 102 can select which antenna panel is used to transmit which UL resource. In yet another example, the UE 102 is configured to select a fixed antenna panel for a particular channel. For example, the UE 102 can be configured to always use a fixed panel for a particular channel, or can be configured to use both or all panels for that channel (e.g., PUCCH).

[0046] Once the UE 102 has determined the mapping between UL resources and antenna panels for a given period of time, the UE 102 moves to steps 206-212. Steps 206-212 represent a loop for resolving time domain overlap on a per-panel basis. In one example, an iteration of the loop is performed for each of the N antenna panels of the UE 102. In another example, an iteration of the loop is performed for each of the N antenna panels scheduled to transmit UL transmissions during the given period of time.

[0047] In step 206, the UE 102 initializes a counter i used to track the number of panels for which contention has been resolved. Specifically, the UE 102 sets the counter value to 0, where each counter value corresponds to a panel of the UE 102. For example, a value of 0 corresponds to panel #0 of the UE 102. In step 208, the UE 102 determines whether the current value of the counter is less than the maximum number of panels (i.e., maxULPanels or N panels). If the current counter value is less than the maximum number of panels, the UE 102 moves to step 210 to resolve any conflicts for UL transmissions scheduled on the panel corresponding to the current counter value. In another example, the UE 102 determines whether the current value of the counter is less than the number of panels used for UL transmissions in a given period.

[0048] In some implementations, resolving overlaps of UL transmissions on a panel may include dropping one or more of the UL transmissions or multiplexing one or more of the UL transmissions. For example, assuming there are two overlapping UL transmissions, the UE 102 may drop one of the transmissions or multiplex the transmissions together. Note that when a channel is dropped, either the entire transmission for the channel may be dropped or only the overlapping transmission occasion may be dropped. In some implementations, the UE 102 may select between dropping and multiplexing based on several factors, including (1) the type of UL transmission (e.g., PUCCH vs. PUSCH), (2) whether the UL transmission is repetitive, and / or (3) whether there is sufficient time for multiplexing.

[0049] As an example, when one of the transmissions is a PUCCH repeated transmission and the other transmission is a PUSCH transmission, the UE 102 saves the PUCCH transmission and drops the overlapping PUSCH transmission. As another example, if the PUSCH and PUCCH overlap, the PUCCH may be multiplexed on the PUSCH, provided that the timeline required for multiplexing (according to the 3GPP specifications) is met. If there are multiple PUSCHs that overlap with the PUCCH, one of the PUSCHs may be selected by the UE 102 for multiplexing. In yet another example, if the PUSCH and PUCCH overlap, the PUSCH may be dropped without UCI multiplexing. Specifically, if a PUSCH transmission without an UL-shared channel (UL-SCH) overlaps with a PUCCH transmission that includes positive scheduling request (SR) information, the UE 102 does not transmit the PUSCH.

[0050] In some examples, if the PUSCH and PUCCH overlap, the PUCCH may be dropped partially or completely. The non-dropped portion of the PUCCH, if any, may be multiplexed onto the PUSCH. If the UCI in the PUCCH transmission is to be multiplexed onto the overlapping PUSCH transmission, the UE 102 multiplexes only Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) information, if any, from the UCI in the PUSCH transmission. If the UE 102 multiplexes aperiodic or semi-persistent channel state information (CSI) reports in the PUSCH, the UE 102 does not transmit the PUCCH. Other example multiplexing / dropping rules are described in 3GPP TS 38.213, Section 9.

[0051] In some implementations, the UE 102 is configured to receive signaling indicating which of the overlapping resources are preserved and which are dropped for each panel. The signaling may be implicit (e.g., DCI) or may be explicit, such as via RRC signaling. As an example, the signaling may indicate to the UE 102 that uplink transmissions associated with a multi-TRP are prioritized over overlapping uplink transmissions associated with a single-TRP.

[0052] In some implementations, when time domain overlap is resolved for the panel, UE 102 moves to step 212. In step 212, UE 102 increments a counter (i = i + 1) and returns to step 208 to determine whether contention has been resolved for all panels. This loop is executed until contention is resolved for all panels. In particular, when it is determined in step 208 that "i < maxULPanels" is "No", method 200 proceeds to resolve time domain overlap on a cross-panel basis as shown in steps 214 and 216.

[0053] In step 214, UE 102 determines whether it can perform simultaneous multi-panel transmission (SMPTx). That is, UE 102 determines whether there is time domain overlap between multiple uplink channels on a cross-panel basis. In some implementations, this determination may be limited to overlap between transmissions on the same CC, but simultaneous transmissions on different CCs may not be considered overlap. In addition to this determination, in some implementations, UE 102 may be configured to receive RRC parameters for enabling / disabling a certain type of SMPTx (e.g., simultaneous PUSCH or simultaneous PUCCH). In such implementations, UE 102 performs SMPTx only when the RRC parameters enable UE 102 to perform SMPTx and when UE 102 determines that there is no cross-panel time domain overlap.

[0054] If the UE 102 can and is enabled to perform SMPTx ("Yes" at step 214), the method 200 ends at step 218 without further processing. Otherwise, if the UE 102 must resolve cross-panel overlap ("No" at step 214), the UE 102 determines which uplink transmissions are to be kept and which are to be dropped according to one or more predefined rules at step 216. Since the predefined rules may vary for different types of SMPTx (e.g., two PUSCHs, two PUCCHs, or one PUSCH and one PUCCH), the UE 102 determines which type of SMPTx to perform and then applies the rules accordingly. The UE 102 may determine which rules to apply by itself or based on RRC signaling received from the base station.

[0055] In some implementations, when the type of SMPTx is multiple PUSCHs on different panels, the UE 102 is configured to first determine whether the overlapping PUSCH transmissions satisfy one of one or more time domain conditions. Under a first time domain condition, the UE 102 transmits two PUSCHs only if they have the same time domain resource allocations (TDRAs), i.e., they span the same symbols. Under a second time domain condition, the UE 102 transmits two PUSCHs only if one of the PUSCHs is within the other one in the time domain. Under a third time domain condition, the UE 102 transmits two PUSCHs even if the TDRAs of the two PUSCHs only partially overlap.

[0056] In some implementations, the UE 102 is configured to further determine whether the overlapping PUSCH transmissions satisfy one or more frequency domain conditions. Specifically, subject to one or more of the time domain conditions described above, the UE 102 is configured to further determine whether the overlapping PUSCH transmissions satisfy one of the one or more frequency domain conditions. Under a first frequency domain condition, the UE 102 transmits the two PUSCHs if they are configured with frequency division multiplexing (FDM) without overlap in the frequency domain. Under a second frequency domain condition, the UE 102 transmits the two PUSCHs if they are configured with FDM in which partial or complete overlap is allowed in the frequency domain. Under a third frequency domain condition, the UE 102 transmits the two PUSCHs only if they are configured with spatial division multiplexing (SDM), e.g., multiplexed across multiple panels with the same frequency domain resource allocation (FDRA), i.e., complete frequency domain overlap.

[0057] In some implementations, the UE 102 may select which of the above time domain and / or frequency domain conditions to implement based on UE capability signaling received from the base station, for example via RRC parameters.

[0058] However, if the overlapping PUSCH transmissions do not satisfy the specified time domain condition and / or the specified frequency domain condition, the UE 102 cannot transmit both PUSCHs but needs to drop at least one PUSCH transmission or multiplex one PUSCH transmission into another PUSCH transmission. To this end, in such a scenario, the UE 102 is configured to select at least one of the following options: In a first option, the UE 102 does not transmit either of the two PUSCHs; In a second option, the UE 102 transmits the PUSCH associated with the higher priority; In a third option, the UE 102 transmits a PUSCH that starts earlier in time (and / or frequency) and drops the other PUSCH.

[0059] In a fourth option, the UE 102 transmits a PUSCH associated with a given panel, such as a fixed panel and a preferred panel (e.g., a panel with a better beam quality or a higher reported Layer 1 reference signal received power [L1-RSRP]). In a fifth option, the UE 102 transmits a PUSCH associated with a UCI. In a sixth option, the UE 102 transmits a PUSCH using a larger size modulation and coding scheme (MCS) or a larger transport block (TB) size. The selection of a PUSCH to transmit may be based on a combination of these options. For example, if both PUSCH transmissions include UCI, the UE 102 may make a selection based on different criteria. Such criteria may be that the UE selects a PUSCH that includes a HARQ-ACK, selects a PUSCH that starts earlier, or selects a PUSCH associated with a preferred panel (e.g., a panel predetermined by the base station or the UE 102).

[0060] The rules for the SMPTx of multiple PUCCHs are similar to those described above for the SMPTx of multiple PUSCHs. For example, under a first time domain condition, the UE 102 transmits two PUCCHs only if they have the same TDRA, i.e., if they span the same symbol. Under a second time domain condition, the UE 102 transmits two PUCCHs only if one of the PUCCHs is within the other one in the time domain. Under a third time domain condition, the UE 102 transmits two PUCCHs even if the TDRAs of the two PUCCHs only partially overlap. Similarly, the rules for multiple PUSCH transmission based on the frequency domain condition may also be applied to PUCCHs.

[0061] If the overlapping PUCCH transmissions do not satisfy the specified time domain condition and / or the specified frequency domain condition, the UE 102 cannot transmit both PUCCHs but must drop at least one PUCCH transmission or multiplex one PUCCH transmission into another PUCCH transmission. To this end, the UE 102 may select at least one of several options similar to those described above for the SMPTx of the PUSCH. In a first option, the UE 102 does not transmit either of the two PUCCHs. In a second option, the UE 102 transmits the PUCCH associated with the higher priority. In a third option, the UE 102 transmits a PUCCH that starts earlier in time (and / or frequency) and drops the other PUCCH. In a fourth option, the UE 102 transmits PUCCHs associated with a given panel, such as a fixed panel and a preferred panel (e.g., a panel with a better beam quality or a higher reported Layer 1 reference signal received power [L1-RSRP]). In a fifth option, the UE 102 transmits a PUCCH including a UCI with a higher priority, where the priority of the UCI is ranked as HARQ-ACK>SR>CSI. In a sixth option, the UE 102 transmits a PUCCH with a larger size MCS or with a larger size TB. The selection of a PUCCH to transmit may be based on a combination of these options.

[0062] The rules for the SMPTx of PUCCH and PUSCH are also similar to those described above for the SMPTx of multiple PUSCHs. These rules include rules under the time domain and frequency domain conditions described above. If the time domain and / or frequency domain conditions are not met, the UE 102 may select at least one of several options similar to those described above for the SMPTx of PUSCH. In a first option, the UE 102 does not transmit either the PUCCH or the PUSCH. In a second option, the UE 102 transmits one of the PUCCH and the PUSCH associated with a higher priority. In a third option, the UE 102 transmits one of the PUCCH and the PUSCH that starts earlier in time (and / or frequency) and drops the other one.

[0063] In a fourth option, the UE 102 transmits one of the PUCCH and PUSCH associated with a given panel, such as a fixed panel and a preferred panel. In a fifth option, the UE 102 resolves cross-panel overlaps by employing one or more rules that are applied to resolve panel-wise overlaps. As an example of the fifth option, when one of the SMPTx is a PUCCH repetitive transmission and the other transmission is a non-repetitive PUSCH transmission, the UE 102 saves the PUCCH transmission and drops the overlapping PUSCH transmission. As another example of the fifth option, when the PUSCH and PUCCH overlap, the PUCCH may be multiplexed on the PUSCH, provided that the required timeline for multiplexing (according to the 3GPP specification) is met. In a sixth option, the UE 102 prioritizes transmissions associated with an m-TRP over transmissions associated with an s-TRP. The selection between PUSCH and PUCCH transmissions may also be based on a combination of these options.

[0064] These scenarios assume that the UE 102 is configured for two simultaneous UL transmissions, although the previous description may apply to some implementations in which the UE 102 is configured for three or more simultaneous transmissions. After the UL transmission overlaps are resolved, the workflow 200 ends at step 218.

[0065] Although the workflow 200 includes both per-panel and cross-panel based processing, some implementations can be either per-panel or cross-panel based. For example, some implementations can resolve time domain overlaps only on a per-panel basis, and some implementations can resolve time domain overlaps only on a cross-panel basis. Additionally, while the workflow 200 described above performs cross-panel processing only after completion of per-panel processing, in some implementations, cross-panel processing can be performed earlier than or in parallel with per-panel processing.

[0066] FIG. 3 illustrates an example 300 of resolving overlapping UL transmissions according to some implementations. In this example, the UE 102 is a multi-panel UE that includes two panels (labeled Panel 1 and Panel 2). Additionally, the UE 102 communicates with two TRPs (labeled TRP1 and TRP2). In this example, the UE 102 receives a separate DCI from each TRP that schedules a PUSCH transmission on a respective one of the panels of the UE 102. As shown in FIG. 3, two PUSCH transmissions are scheduled in the same slot (slot 2) across the two panels of the UE 102. Additionally, the UE 102 is scheduled to perform PUCCH transmissions in consecutive slots (slot 1 and slot 2), with the PUCCH transmission in slot 2 on panel 2 being a repeat of the PUCCH transmission in slot 1 on panel 1.

[0067] As shown in FIG. 3, one of the PUCCH repetitions overlaps with PUSCH 1 in slot 2 on panel 1. This overlap is on a per-panel basis. To resolve the overlap on panel 1, the UE 102 is configured to execute a workflow 200 for resolving UL transmission overlaps. In this example, the resolution is to drop PUSCH 1 while keeping the overlapping PUCCH (e.g., based on the rule that if a PUCCH with repetitions overlaps with a PUSCH without repetitions, the PUSCH is dropped). After dropping PUSCH 1 to resolve the overlap on a per-panel basis on panel 1, there is no cross-panel overlap between panel 1 and panel 2.

[0068] FIG. 4 illustrates an example 400 of resolving overlapping UL transmissions according to some implementations. In this example, the UE 102 is a multi-panel UE that includes two panels (labeled Panel 1 and Panel 2). Additionally, the UE 102 communicates with two TRPs (labeled TRP1 and TRP2). In this example, the UE 102 receives a DCI (DCI_1) from TRP1 that schedules a PUCCH transmission on Panel 1. The UE 102 also receives two DCIs (DCI_2 and DCI_3) from TRP1 and TRP2 that schedule PUSCH, PUSCH1 and PUSCH2, respectively, on the two panels of the UE 102. Thus, the PUCCH is a single-TRP transmission and the two PUSCH transmissions are multi-TRP transmissions. All transmissions in FIG. 4 are scheduled in the same slot (Slot 1).

[0069] As can be seen from FIG. 4, one of the PUSCH transmissions, PUSCH1, overlaps with a PUCCH transmission on panel 1. This overlap is on a per-panel basis. To resolve the overlap on panel 1, the UE 102 is configured to prioritize PUSCH transmissions, which are multi-TRP transmissions, over PUCCH transmissions, which are single-TRP transmissions. Thus, for panel 1, PUSCH1 is preserved, but PUCCH is either partially or completely dropped or multiplexed on PUSCH1. After resolving the panel-wise overlap on panel 1 between PUCCH and PUSCH1, there remains a cross-panel overlap to be resolved between PUSCH1 on panel 1 and PUSCH2 on panel 2. To resolve this cross-panel overlap, the UE 102 may implement one or more of the options provided above according to time domain and / or frequency domain conditions.

[0070] 5 illustrates a flowchart of an example method 500 according to some implementations. Method 500 may be performed by UE 102 of FIG. 1 or any suitable system, environment, software, hardware, or combination of systems, environments, software, and hardware, as appropriate. Additionally, although the steps of method 500 are numbered in sequence, implementations of the method need not perform the steps in the numbered order. Some implementations may perform these steps in a different order or in parallel.

[0071] In step 502, the UE receives a scheduling configuration that configures the UE to perform multiple transmissions on multiple UL resources.

[0072] In step 504, the UE selects antenna panels for transmissions based on the UL resource mappings to antenna panels.

[0073] In step 506, the UE resolves time domain overlap for at least two of the multiple transmissions on a per-panel basis such that no more than one transmission is transmitted by each panel over the same CC at a given time.

[0074] In some implementations, resolving the time domain overlap may include a further step of the UE determining, in step 506, that the at least two transmissions are scheduled on a first antenna panel of the plurality, and a further step of the UE multiplexing the at least two transmissions such that the at least two transmissions are transmitted by the first antenna panel using a first UL resource of the plurality.

[0075] In some implementations, resolving the time domain overlap may be a further step in which the UE drops at least a portion of one of the at least two transmissions in step 506.

[0076] In some implementations, resolving the time domain overlap is based on signaling received from a network serving the UE in step 506, the signaling indicating which of at least two of the multiple transmissions to transmit on a per-panel basis. The signaling may be a DCI signal or an RRC signal. The signaling may indicate that a first transmission associated with an m-TRP is prioritized over an overlapping second transmission associated with an s-TRP.

[0077] In some implementations, resolving the time domain overlap in step 506 may be a further step of the UE determining that the at least two transmissions include a repeat PUCCH transmission and a PUSCH transmission scheduled during a first time on a first antenna panel of the plurality, and may be a further step of the UE dropping the PUSCH transmission via the first antenna panel during the first time.

[0078] 6 illustrates a flowchart of an example method 600 according to some implementations. Method 600 may be performed by UE 102 of FIG. 1 or any suitable system, environment, software, hardware, or combination of systems, environments, software, and hardware, as appropriate. Additionally, although the steps of method 500 are numbered sequentially, implementations of the method need not perform the steps in the numbered order. Some implementations may perform these steps in a different order or in parallel.

[0079] In step 602, the UE receives a scheduling configuration that configures the UE to perform multiple transmissions on multiple UL resources.

[0080] In step 604, based on the multiple UL resource mappings to antenna panels, select multiple antenna panels for the multiple transmissions, where the multiple transmissions include two transmissions and the multiple antenna panels include two antenna panels, each of the two panels corresponding to one of the two transmissions.

[0081] In step 606, the UE performs two transmissions on the two panels.

[0082] In some implementations, performing the two transmissions in step 606 may further comprise the UE performing the two transmissions based on whether the two transmissions overlap in the time domain or the UE performing the two transmissions based on whether the two transmissions overlap in the frequency domain. The two transmissions in step 606 may be performed based on RRC parameters.

[0083] In some implementations, the two transmissions performed in step 606 may include two PUSCH transmissions, two PUCCH transmissions, or a PUSCH transmission and a PUCCH transmission.

[0084] In some implementations, performing the two transmissions in step 606 may further be a step of the UE performing one of the two transmissions associated with a higher priority.

[0085] In some implementations, performing the two transmissions in step 606 may further comprise the UE performing one of the two transmissions that starts earlier in time or frequency, and the UE dropping the other of the two transmissions.

[0086] In some implementations, performing the two transmissions in step 606 may further be a step of the UE performing one of the two transmissions corresponding to the preferred panel.

[0087] In some implementations, the two transmissions may both be PUCCHs, and performing the two transmissions in step 606 may further be a step of the UE performing one of the two transmissions that includes UCI with a higher priority.

[0088] In some implementations, the two transmissions may both be PUSCHs, and performing the two transmissions in step 606 may further be the UE performing one of the two transmissions using a larger sized MCS or a larger sized TB.

[0089] In some implementations, the two transmissions may include a PUCCH and a PUSCH, and performing the two transmissions in step 606 may be based on signaling received from a network serving the UE, the signaling indicating which of the two transmissions to transmit. For example, the signaling may indicate that a first of the two transmissions associated with an m-TRP is prioritized over a second of the two transmissions associated with an s-TRP.

[0090] 7 illustrates a UE 700 according to some implementations. The UE 700 may be similar to and substantially interchangeable with the UE 102 of FIG. 1 and may be configured to perform the methods 500 and 600 illustrated in FIG. 5 and FIG. 6.

[0091] The UE 700 may be any mobile or non-mobile computing device, such as a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a pressure sensor, a thermometer, a motion sensor, an accelerometer, an inventory sensor, a voltage / current meter, etc.), a video device (e.g., a camera, a video camera, etc.), a wearable device (e.g., a smart watch), a relaxed-IoT device, etc.

[0092] The UE 700 may include a processor 702, an RF interface circuit 704, a memory / storage device 706, a user interface 708, a sensor 710, a driver circuit 712, a power management integrated circuit (PMIC) 714, an antenna structure 716, and a battery 718. The components of the UE 700 may be implemented as an integrated circuit (IC), a portion thereof, a separate electronic device, or other module, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 7 is intended to show a high-level view of some of the components of the UE 700. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0093] The components of UE 700 may be coupled to various other components via one or more interconnects 720, which may represent any type of interface, input / output, bus (local, system or expansion), transmission line, trace, optical connection, etc. that may allow various circuit components (on a common or different chips or chipsets) to interact with one another.

[0094] The processor 702 may include processor circuitry such as, for example, a baseband processor circuit (BB) 722A, a central processing unit circuit (CPU) 722B, and a graphics processing unit circuit (GPU) 722C. The processor 702 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from the memory / storage 706 to cause the UE 700 to perform the operations described herein.

[0095] In some implementations, the baseband processor circuitry 722A may access a communication protocol stack 724 in the memory / storage device 706 to communicate over a 3GPP-compliant network. In general, the baseband processor circuitry 722A may access a communication protocol stack to perform user plane functions at the physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), and PDU layers, and perform user plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layers. In some implementations, PHY layer operations may additionally / alternatively be performed by components of the RF interface circuitry 704. The baseband processor circuitry 722A may generate or process baseband signals or waveforms that carry information in a 3GPP-compliant network. In some implementations, a waveform for NR may be based on cyclic prefix orthogonal frequency division multiplexing (OFDM) "CP-OFDM" in the uplink or downlink and discrete Fourier transform spread OFDM "DFT-S-OFDM" in the uplink.

[0096] The memory / storage 706 may include one or more non-transitory computer-readable media (e.g., communication protocol stack 724) that include instructions that may be executed by one or more of the processors 702 to cause the UE 700 to perform various operations described herein. The memory / storage 706 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 700. In some implementations, some of the memory / storage 706 may be located on the processor 702 itself (e.g., L1 and L2 caches), while other memory / storage 706 may be external to the processor 702 but accessible via a memory interface. The memory / storage 706 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid state memory, or any other type of memory device technology.

[0097] The RF interface circuitry 704 may include transceiver circuitry and a radio frequency front end module (RFEM) that enable the UE 700 to communicate with other devices over a radio access network. The RF interface circuitry 704 may include various elements disposed in the transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, combiner circuits, control circuits, etc.

[0098] In the receive path, the RFEM may receive a radiated signal from the air interface via the antenna structure 716 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to a transceiver receiver that downconverts the RF signal to a baseband signal that is provided to a baseband processor of the processor 702.

[0099] In the transmit path, the transmitter of the transceiver upconverts baseband signals received from the baseband processor and provides an RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated over the air interface via the antenna 716. In various implementations, the RF interface circuitry 704 may be configured to transmit / receive signals to comply with NR access technologies.

[0100] The antenna 716 may include antenna elements that convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. The antenna elements may be arranged in one or more antenna panels. The antenna 716 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input multiple-output communications. The antenna 716 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna 716 may have one or more panels designed for a particular frequency band, including bands in FR1 or FR2.

[0101] User interface circuitry 708 includes various input / output (I / O) devices designed to enable user interaction with UE 700. User interface 708 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, including, among others, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying or otherwise communicating information, such as sensor readings, actuator position(s), or other similar information. The output device circuitry may include any number or combination of audio or visual displays, including, among others, one or more simple visual outputs / indicators (e.g., binary status indicators such as light emitting diodes "LEDs" and multi-character visual outputs), or more complex outputs such as display devices or touch screens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.), where output such as text, graphics, multimedia objects, etc. are generated or created from operation of the UE700.

[0102] The sensors 710 may include devices, modules, or subsystems that are intended to detect events or changes in their environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others, inertial measurement units including accelerometers, gyroscopes, or magnetometers, microelectromechanical or nanoelectromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers, level sensors, temperature sensors (e.g., thermistors), pressure sensors, image capture devices (e.g., cameras or lensless apertures), light detection and ranging sensors, proximity sensors (e.g., infrared detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers, microphones or other similar audio capture devices, etc.

[0103] The driver circuitry 712 may include software and hardware elements that operate to control particular devices embedded in, attached to, or otherwise communicatively coupled to the UE 700. The driver circuitry 712 may include individual drivers that enable other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 700. For example, the driver circuitry 712 may include a display driver that controls and enables access to a display device, a touchscreen driver that controls and enables access to a touchscreen interface, a sensor driver that obtains sensor readings of the sensor circuitry 728 and controls and enables access to the sensor circuitry 728, a driver that obtains actuator positions of or controls and enables access to electromechanical components, a camera driver that controls and enables access to an embedded image capture device, an audio driver that controls and enables access to one or more audio devices.

[0104] The PMIC 714 may manage the power supplied to various components of the UE 700. In particular, with respect to the processor 702, the PMIC 714 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0105] In some implementations, the PMIC 714 may control or otherwise be a part of various power saving mechanisms of the UE 700. The battery 718 may power the UE 700, although in some examples the UE 700 may be mounted and deployed at a fixed location and may have a power source coupled to a power grid. The battery 718 may be a lithium ion battery, a metal air battery such as a zinc air battery, an aluminum air battery, a lithium air battery, or the like. In some implementations, such as vehicle-based applications, the battery 718 may be a typical automotive lead acid battery.

[0106] 8 illustrates an access node 800 (e.g., a base station or a gNB) according to some implementations. The access node 800 may be similar to and substantially interchangeable with the base station 104. The access node 800 may include a processor 802, an RF interface circuit 804, a core network (CN) interface circuit 806, a memory / storage circuit 808, and an antenna structure 810.

[0107] The components of the access node 800 may be coupled to various other components via one or more interconnects 812. The processor 802, RF interface circuitry 804, memory / storage circuitry 808 (including communication protocol stack 814), antenna structure 810, and interconnects 812 may be similar to the similarly named elements shown and described with respect to Figure 7. For example, the processor 802 may include processor circuitry such as a baseband processor circuitry (BB) 816A, a central processing unit circuitry (CPU) 816B, and a graphics processing unit circuitry (GPU) 816C.

[0108] The CN interface circuitry 806 may provide connectivity to a core network, e.g., a fifth generation core network (5GC), using a 5GC compliant network interface protocol, such as a Carrier Ethernet protocol or some other suitable protocol. Network connectivity may be provided to / from the access node 800 via optical fiber or wireless backhaul. The CN interface circuitry 806 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 806 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0109] As used herein, the terms "access node", "access point", etc. may refer to equipment that provides wireless baseband functionality for data and / or voice connectivity between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, TRPs, etc., and may include terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" etc. may refer to an access node 800 operating in a NR or 5G system (e.g., gNB), and the term "E-UTRAN node" may refer to an access node 800 operating in a LTE or 4G system (e.g., eNB). According to various implementations, the access node 800 may be implemented as one or more of a macrocell base station and / or a dedicated physical device such as a femtocell, picocell, or other like cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0110] In some implementations, all or part of the access node 800 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In a V2X scenario, the access node 800 may be or operate as a "road side unit." The term "Road Side Unit" or "RSU" may refer to any transportation infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, and an RSU implemented in or by a UE may be referred to as a "UE type RSU," an RSU implemented in or by an eNB may be referred to as an "eNB type RSU," an RSU implemented in or by a gNB may be referred to as a "gNB type RSU," etc.

[0111] In the description herein, for convenience, various components may be described as performing a task or tasks. Such descriptions should be construed to include the phrase "configured to." It is expressly intended that the description of a component as being configured to perform one or more tasks does not enforce 35 U.S.C. 112(f) interpretation of the component.

[0112] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more of the operations, techniques, processes, or methods as described in the example section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below. As another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below in the example section.

[0113] Any of the above examples may be combined with any other example (or combination of examples) unless otherwise stated. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0114] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated, and it is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

1. 1. A method performed by a user equipment (UE), the method comprising: receiving a scheduling configuration that configures the UE to perform multiple transmissions on multiple uplink (UL) resources; selecting antenna panels for the transmissions based on the UL resource mappings to antenna panels; resolving time domain overlap for at least two of the plurality of transmissions on a per-panel basis such that no more than one transmission is transmitted by each panel at a given time over the same component carrier; A method comprising:

2. Resolving the time domain overlap for the at least two transmissions on a panel-by-panel basis comprises: determining that the at least two transmissions are scheduled on a first antenna panel of the plurality; and multiplexing the at least two transmissions such that the at least two transmissions are transmitted by the first antenna panel using a first UL resource of the plurality.

3. Resolving the time domain overlap for the at least two transmissions on a panel-by-panel basis comprises:

2. The method of claim 1, further comprising: dropping at least a portion of one of the at least two transmissions.

4. 2. The method of claim 1, wherein resolving the time domain overlap for the at least two transmissions is based on signaling received from a network serving the UE, the signaling indicating which of the at least two of the multiple transmissions to transmit on a per-panel basis.

5. The method of claim 4 , wherein the signaling is received via a Downlink Control Information (DCI) signal or a Radio Resource Control (RRC) signal.

6. 5. The method of claim 4, wherein the signaling indicates that a first transmission associated with a multiple transmission / reception point (m-TRP) is prioritized over an overlapping second transmission associated with a single TRP (s-TRP).

7. Resolving the time domain overlap for the at least two transmissions on a panel-by-panel basis comprises: determining that the at least two transmissions include repeated physical uplink control channel (PUCCH) transmissions and physical uplink shared channel (PUSCH) transmissions scheduled during a first time on a first antenna panel of the plurality; dropping, during the first time, the PUSCH transmission via the first antenna panel, the method of claim 1. **Claim 8** A method performed by a user equipment (UE), the method comprising: receiving a scheduling configuration that configures the UE to perform a plurality of transmissions on a plurality of uplink (UL) resources; selecting, based on the plurality of UL resource mappings to antenna panels, a plurality of antenna panels for the plurality of transmissions, the plurality of transmissions including two transmissions, the plurality of antenna panels including two antenna panels, each of the two panels corresponding to one of the two transmissions; performing the two transmissions via the two panels; A method. **Claim 9** Performing the two transmissions comprises: performing the two transmissions based on whether the two transmissions overlap in a time domain, the method of claim 8. **Claim 10** Performing the two transmissions comprises: performing the two transmissions based on whether the two transmissions overlap in a frequency domain, the method of claim 8. **Claim 11** Performing the two transmissions comprises: performing the two transmissions based on radio resource control (RRC) parameters, the method of claim 8. **Claim 12** The two transmissions are: two physical uplink shared channel (PUSCH) transmissions, two physical uplink control channel (PUCCH) transmissions, or a PUSCH transmission and a PUCCH transmission, the method of claim 8. **Claim 13** Performing the two transmissions comprises: performing one of the two transmissions associated with a higher priority, the method of claim 12. **Claim 14** Performing the two transmissions comprises: performing one of the two transmissions that starts earlier in time or frequency; and dropping the other one of the two transmissions, the method of claim 12. **Claim 15** Performing the two transmissions includes: The method of claim 12 including performing one of the two transmissions corresponding to a preferred panel.

16. The two transmissions include two PUSCHs, and performing the two transmissions includes:

13. The method of claim 12, comprising performing one of the two transmissions including uplink control information (UCI).

17. The two transmissions include two PUCCHs, and performing the two transmissions includes:

13. The method of claim 12, comprising performing one of the two transmissions that includes uplink control information (UCI) having a higher priority.

18. The two transmissions include two PUSCHs, and performing the two transmissions includes:

13. The method of claim 12, comprising performing one of the two PUSCH transmissions using a larger size modulation and coding scheme (MCS) or using a larger size transport block (TB).

19. The two transmissions are The method of claim 8 , comprising a PUSCH transmission and a PUCCH transmission.

20. 20. The method of claim 19, wherein performing the two transmissions is based on signaling received from a network serving the UE, the signaling indicating which of the two transmissions to transmit.

21. 21. The method of claim 20, wherein the signaling indicates that a first of the two transmissions associated with a multiple transmission / reception point (m-TRP) is prioritized over a second of the two transmissions associated with a single TRP (s-TRP).

22. A user equipment (UE), a receiver for receiving a scheduling configuration that configures the UE to perform multiple transmissions on multiple uplink (UL) resources; 1. A processor comprising: selecting a plurality of antenna panels for the plurality of transmissions based on the plurality of UL resource mappings to antenna panels; a processor that resolves time domain overlap for at least two of the plurality of transmissions on a per-panel basis such that no more than one transmission is transmitted by each panel at a given time over the same component carrier; A user equipment (UE) comprising:

23. A user equipment (UE), a receiver for receiving a scheduling configuration that configures the UE to perform multiple transmissions on multiple uplink (UL) resources; a processor that selects, based on the plurality of UL resource mappings to antenna panels, a plurality of antenna panels for the plurality of transmissions, the plurality of transmissions including two transmissions, the plurality of antenna panels including two antenna panels, each of the two panels corresponding to one of the two transmissions; a transmitter for performing the two transmissions through the two panels; A user equipment (UE) comprising:

24. 22. A non-transitory computer storage medium encoded with instructions that, when executed by one or more computers, cause the one or more computers to perform the method of any one of claims 1 to 21.

25. 22. A system comprising one or more computers and one or more storage devices having stored thereon instructions operable, when executed by the one or more computers, to cause the one or more computers to perform the method of any one of claims 1 to 21.

Images