Uplink collision handling for multi-transmit-receive communications

Abstract

Systems, devices, and methods are provided for handling uplink (UL) collisions in a multi-transmit-receive point (mTRP) communication scenario. A wireless communication method may be performed based on the mTRP UL prioritization configuration. For example, a wireless communication method performed by a user equipment (UE) may include receiving a first indication to schedule a first uplink (UL) communication associated with a first transmit configuration indicator (TCI) state and a first TRP; receiving a second indication to schedule a second UL communication associated with a second TCI state and a second TRP, where the second UL communication is scheduled to at least partially overlap with the first UL communication in time, and where the first UL communication and the second UL communication are scheduled for at least one of a same component carrier (CC) or a same frequency band; and transmitting the first UL communication based on the mTRP UL prioritization configuration.

Description

Background Art

[0001] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system may include multiple base stations (BSs), each of which simultaneously supports communication for multiple communication devices, which may also be referred to as user equipment (UE).

[0002] To meet the growing demand for extended mobile broadband connections, wireless communication technology is evolving from long-term evolution (LTE) technology to next-generation new radio (NR) technology, which may be referred to as the fifth generation (5G). For example, NR is designed to provide lower latency, higher bandwidth or higher throughput, and higher reliability compared to LTE. NR is designed to operate on a wide array of spectrum bands, for example, from low-frequency bands below about 1 gigahertz (GHz) and mid-frequency bands from about 1 GHz to about 6 GHz to high-frequency bands such as millimeter wave (mmWave) bands. NR is also designed to operate across different spectrum types, from licensed spectrum to unlicensed spectrum and shared spectrum. Spectrum sharing enables operators to have the opportunity to aggregate spectrum to dynamically support high-bandwidth services. Spectrum sharing can extend the benefits of NR technology to operating entities that may not have access to licensed spectrum.

[0003] It may be desirable or advantageous to align uplink (UL) communications at a BS based on the BS timing configuration. For example, in orthogonal multiple access where different UEs may communicate in consecutive time resources (e.g., time slots), and / or in orthogonal multiple access where different UEs may be configured to communicate with a BS simultaneously but in different frequency resources (e.g., carriers, subcarriers), proper timing alignment of the UE with the BS may reduce or avoid intra-cell interference. The UE may compensate for delays (e.g., propagation delays) in UL communications sent to the BS by determining and applying a timing advance to the UL communications.

[0004] In a multiple transmit receive point (mTRP) communication scenario, a UE may be scheduled to communicate with one or more transmit receive points (TRPs). In some aspects, the TRPs may be located at different physical locations. In other aspects, the TRPs may be co-located. Although the TRPs may not be in the same location, the communications sent by the TRPs may be sent in the same logical cell (including, for example, the same frequency resources). In a single downlink control information (DCI) mTRP communication, DCI from one of the TRPs may schedule communications for each of the multiple TRPs. In a multiple DCI (mDCI) mTRP (mTRP) communication, each TRP may send DCI to the UE to schedule communications. Summary of the invention

[0005] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. The sole purpose of this summary is to present some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to more specific embodiments presented later.

[0006] In some instances, a user equipment (UE) in a multiple transmit receive point (mTRP) communication scenario may be instructed, configured and / or otherwise scheduled to send two uplink (UL) communications simultaneously. In some instances, the UE may not be able to send the two UL communications simultaneously. For example, in some aspects, the two UL communications may be associated with or configured with a TCI state that cannot be sent simultaneously. In other aspects, the two UL communications may be associated with or configured with the same TCI state, and the UL communications may not be sent simultaneously. This scenario may be referred to as a scheduling conflict, or conflict. The present disclosure describes methods, mechanisms, and systems for handling UL conflicts in mTRP communication scenarios. In some aspects, the methods and mechanisms described herein may be performed based on an mTRP UL prioritization configuration. In some aspects, the mTRP UL prioritization configuration may indicate or configure the priority of the conflicting UL communications based on the UL channel type, the associated TCI state, the received TRP, the timing, and / or the indication or scheduling mechanism.

[0007] According to one aspect of the present disclosure, a wireless communication method performed by a user equipment (UE) includes: receiving a first indication of scheduling a first uplink (UL) communication associated with a first transmit configuration indicator (TCI) state and a first transmit receive point (TRP); receiving a second indication of scheduling a second UL communication associated with a second TCI state and a second TRP, wherein the second UL communication is scheduled to at least partially overlap with the first UL communication in time, and wherein the first UL communication and the second UL communication are scheduled for at least one of the same component carrier (CC) or the same frequency band; and sending the first UL communication based on a multi-TRP (mTRP) UL prioritization configuration.

[0008] According to one aspect of the present disclosure, a UE includes: a memory device; a transceiver; and a processor in communication with the memory device and the transceiver, wherein the UE is configured to: receive a first indication of a first uplink (UL) communication scheduled to be associated with a first transmit configuration indicator (TCI) state and a first transmit receive point (TRP); receive a second indication of a second UL communication scheduled to be associated with a second TCI state and a second TRP, wherein the second UL communication is scheduled to at least partially overlap with the first UL communication in time, and wherein the first UL communication and the second UL communication are scheduled for at least one of the same component carrier (CC) or the same frequency band; and send the first UL communication based on a multi-TRP (mTRP) UL prioritization configuration.

[0009] According to one aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon, wherein the program code includes instructions that can be executed by a processor of a user equipment (UE) to cause the UE to: receive a first indication of a first uplink (UL) communication scheduled to be associated with a first transmit configuration indicator (TCI) state and a first transmit receive point (TRP); receive a second indication of a second UL communication scheduled to be associated with a second TCI state and a second TRP, wherein the second UL communication is scheduled to at least partially overlap with the first UL communication in time, and wherein the first UL communication and the second UL communication are scheduled for at least one of the same component carrier (CC) or the same frequency band; and send the first UL communication based on a multi-TRP (mTRP) UL prioritization configuration.

[0010] According to one aspect of the present disclosure, a UE includes: a component for receiving a first indication of scheduling a first uplink (UL) communication associated with a first transmit configuration indicator (TCI) state and a first transmit reception point (TRP); a component for receiving a second indication of scheduling a second UL communication associated with a second TCI state and a second TRP, wherein the second UL communication is scheduled to at least partially overlap with the first UL communication in time, and wherein the first UL communication and the second UL communication are scheduled for at least one of the same component carrier (CC) or the same frequency band; and a component for sending the first UL communication based on a multi-TRP (mTRP) UL prioritization configuration.

[0011] After reading the following description of specific exemplary aspects in conjunction with the accompanying drawings, other aspects, features, and embodiments will become apparent to those of ordinary skill in the art. Although each feature may be discussed below with respect to certain aspects and accompanying drawings, all aspects may include one or more of the advantageous features discussed herein. In other words, although one or more aspects may be discussed as having certain advantageous features, one or more of such features may also be used according to the various aspects discussed herein. In a similar manner, although the exemplary aspects may be discussed below as aspects of devices, systems, or methods, it should be understood that such exemplary aspects may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1A A wireless communication network according to some aspects of the present disclosure is illustrated.

[0013] Figure 1B is a diagram illustrating an example decomposed BS architecture according to some aspects of the present disclosure.

[0014] Figure 2 A communication scenario utilizing a reconfigurable smart surface according to some aspects of the present disclosure is illustrated.

[0015] Figure 3 is a diagram of an example uplink (UL) scheduling conflict in a multiple transmission reception point (mTRP) communication scenario according to aspects of the present disclosure.

[0016] Figure 4 A transmission frame of a communication network according to some embodiments of the present disclosure is illustrated.

[0017] Figure 5 is a signaling diagram of a multiple transmission reception point (mTRP) communication method according to some aspects of the present disclosure.

[0018] Figure 6 A block diagram of a base station (BS) is illustrated according to some aspects of the present disclosure.

[0019] Figure 7 A block diagram illustrating a user equipment (UE) according to some aspects of the present disclosure is shown.

[0020] Figure 8 is a flow chart of a method of wireless communication according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0021] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a comprehensive understanding of the various concepts, the detailed description includes specific details. However, it is apparent to those skilled in the art that these concepts may be practiced without these specific details. In some aspects, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0022] The present disclosure as a whole relates to wireless communication systems, which are also referred to as wireless communication networks. In various aspects, various techniques and devices can be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, global mobile communication systems (GSM) networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0023] OFDMA networks may implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are either known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between a group of telecommunications associations with the goal of defining globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the UMTS mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution from LTE, 4G, 5G, NR and beyond wireless technologies, where access to the wireless spectrum is shared between networks using a range of new and different radio access technologies or radio air interfaces.

[0024] Specifically, 5G networks consider various deployments, various spectrums, and various services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to (1) ultra-high density (e.g., about 1M nodes / km) 2 (1) provide coverage for the massive Internet of Things (IoT) with ultra-low complexity (e.g., about 10 bits / second), ultra-low energy (e.g., about 10+ years battery life), and deep coverage with the ability to reach challenging locations; (2) provide coverage including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond), and for users with extensive mobility or lack of mobility; and (3) provide coverage with enhanced mobile broadband (including very high capacity (e.g., about 10Tbps / km 2 ), coverage of very high data rates (e.g., multi-Gbps rates, 100+Mbps user experienced rates), and deep awareness with advanced discovery and optimization).

[0025] 5G NR communication systems can be implemented using optimized OFDM-based waveforms with scalable parameter sets and transmission time intervals (TTIs); with a common, flexible framework to efficiently multiplex services and features using dynamic low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and with advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5G NR and the scaling of subcarrier spacing can effectively address the operation of various services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, the subcarrier spacing may appear at 15kHz on bandwidths (BW) such as 5MHz, 10MHz, 20MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, the subcarrier spacing may appear at 30kHz on 80MHz / 100MHz BW. For various other indoor broadband implementations, TDD is used on the unlicensed portion of the 5GHz band, and the subcarrier spacing may appear at 60kHz on 160MHz BW. Finally, for various deployments that transmit using the mmWave component at 28GHz TDD, the subcarrier spacing may appear at 120kHz on 500MHz BW. In some aspects, the frequency bands used for 5G NR are divided into multiple different frequency ranges: frequency range one (FR1), frequency range two (FR2), and FR2x. The FR1 band includes a band of 7GHz or lower (e.g., between about 410MHz and about 7125MHz). The FR2 band includes a band in the millimeter wave range between about 24.25GHz and about 52.6GHz. The FR2x band includes a band in the millimeter wave range between about 52.6GHz and about 71GHz. Compared to the FR1 band, the mmWave band may have a shorter range but a higher bandwidth. Additionally, 5G NR may support different subcarrier spacing sets for different frequency ranges.

[0026] 5G NR's scalable parameter sets facilitate scalable TTIs for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also envisions a self-contained integrated subframe design with UL / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive UL / downlink (which can be flexibly configured on a per-cell basis to dynamically switch between UL and downlink to meet current business needs).

[0027] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) performing base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also known as an independent BS or a monolithic BS) or a decomposed base station.

[0028] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0029] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0030] The various other aspects and features of the present disclosure are further described below. It should be apparent that the teachings herein can be embodied in various forms, and any specific structure, function, or both disclosed herein are merely representative and not restrictive. Based on the teachings herein, it should be understood by those of ordinary skill in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice a method. In addition, such a device can be implemented or such a method can be practiced using other structures, functionality, or structures and functionality other than or different from one or more of the aspects set forth herein. For example, the method can be implemented as a part of a system, device, device, and / or as an instruction stored on a computer-readable medium for execution on a processor or computer. In addition, one aspect can include at least one element of a claim.

[0031] In a multiple transmit receive point (mTRP) communication scenario, a UE may be scheduled to communicate with one or more transmit receive points (TRPs). In some aspects, the TRPs may be located at different physical locations. In other aspects, the TRPs may be co-located. Although the TRPs may not be in the same location, the communications sent by the TRPs may be sent in the same logical cell (including, for example, the same frequency resources). In a single DCI mTRP communication, DCI from one of the TRPs may schedule communications for each of the multiple TRPs. In a multi-DCI (mDCI) mTRP (mTRP) communication, each TRP may send DCI to the UE to schedule communications.

[0032] In some aspects, one or more of the serving cells may be configured for mDCI mTRP communication, and one or more cells may be configured for single DCI mTRP communication or single TRP communication. If the cell configuration indicates two control resource set (CORESET) pool index values ​​and two timing advance groups (TAGs), the cell may be configured for mDCI mTRP communication. For example, an mDCI mTRP cell may be configured with two CORESET pool index values ​​and two TAG indicators. A single DCI mTRP cell or a single TRP cell configuration may indicate a single TAG indicator and / or a single CORESET pool index value. When a cell is configured for mDCI mTRP communication, a UL signal on the cell may be sent to one TRP among multiple TRPs.

[0033] In mTRP communications, simultaneous DL and / or UL communications associated with different TRPs may be multiplexed via time domain multiplexing (TDM), frequency domain multiplexing (FDM), and / or spatial domain multiplexing (SDM). For example, in spatial domain multiplexing, the UE may use the same frequency resources and time resources to send and / or receive mTRP communications using different spatial filters for each communication. In some aspects, a spatial filter may refer to a scheme or configuration that enables an antenna element array to adjust the phase of a signal from each antenna element, producing a focused beam directed along a plane or axis. The phase shifting process to produce a focused beam may be referred to as beamforming. In some aspects, the UE may use two different spatial filters to simultaneously send and / or receive communications to different TRPs. In some aspects, the UE may use different antenna panels or antenna arrays to perform simultaneous transmissions.

[0034] In some aspects, spatial filtering may be transparent to the receiving device, so that the receiving device does not need to know the spatial configuration of the receiving beam to process and decode the received signal. In other aspects, the transmitting device may indicate the beam configuration to the receiving device for processing, filtering, etc. The beam indication may inform the receiving device that, for example, the physical uplink shared channel (PUSCH) communication is sent using the same spatial filter as the corresponding UL reference signal (e.g., DMRS) sent with it. In some aspects, the transmitting device may use one or more transmission configuration indicator (TCI) states to indicate beam parameters or characteristics. The TCI state may indicate information about the spatial characteristics of the reference signal and / or beam. The wireless communication device may be configured with several candidate TCI states. In some aspects, a subset of candidate TCI states may be activated or assigned to different DL and / or UL resources. For example, the TCI state and other beam parameters may be dynamically indicated between the UE and the TRP. In some aspects, the network may indicate the TCI state for DL ​​communication in the DCI via the TRP. Similarly, for example, the network may indicate the TCI state to be used for scheduled UL communication in the scheduling DCI.

[0035] As described above, mTRP communications may be scheduled by sDCI or mDCI. In sDCI, a single DCI from a single TRP may be used to schedule DL and / or UL communications from multiple TRPs. Therefore, in some aspects, sDCI may include or indicate more than one TCI state. In some instances, the UE in the mTRP communication scenario may be indicated, configured and / or otherwise scheduled to send two UL communications simultaneously. In some instances, the UE may not be configured to or may not be able to send the two UL communications simultaneously. For example, in some aspects, the two UL communications may be associated with or configured with a TCI state that cannot be sent simultaneously. In other aspects, the two UL communications may be associated with or configured with the same TCI state, and these UL communications may not be sent simultaneously. This scenario may be referred to as a scheduling conflict, or conflict. In some cases, a conflict may cause or result in an error situation in which both communications are not sent. This may reduce the efficiency of network resource usage, increase latency, and use of higher power at the UE.

[0036] The present disclosure describes methods, mechanisms, and systems for handling UL conflicts in mTRP scenarios. In some aspects, the methods and mechanisms described herein may be performed based on an mTRP prioritization configuration. In some aspects, the mTRP prioritization configuration may be configured at the network and / or at the UE. For example, the UE may be pre-configured with a hard-coded rule set to determine the priority of conflicting UL communications in an mTRP scenario. The mTRP prioritization configuration may indicate or configure the priority of conflicting UL communications based on UL channel type (e.g., PUSCH, SRS, PRACH, etc.), associated TCI state, received TRP, timing, and / or indication or scheduling mechanism (e.g., DCI scheduled, RRC configured, etc.).

[0037] The scheme and mechanism of the present disclosure advantageously facilitate the simultaneous transmission of multiple panels of UL mTRP communication. Therefore, the throughput and / or reliability of UL communication can be improved. In addition, the unified TCI indication scheme described herein can reduce network overhead, so that a single DCI can indicate multiple TCI states, and the TCI state can be mapped to other beam parameters for UL communication.

[0038] Figure 1AA wireless communication network 100 according to some aspects of the present disclosure is illustrated. The network 100 may be a 5G network. The network 100 includes several base stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. The BSs 105 may be stations that communicate with UEs 115 (labeled 115a, 115b, 115c, 115d, 115e, 115f, 115g, 115h, and 115k, respectively), and may also be referred to as evolved B nodes (eNBs), next generation eNBs (gNBs), access points, etc. Each BS 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to that particular geographic coverage area of ​​the BS 105 and / or a BS subsystem serving that coverage area, depending on the context in which the term is used.

[0039] BS 105 may provide communication coverage for macro cells or small cells (such as pico cells or femto cells) and / or other types of cells. Macro cells generally cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as pico cells) will generally cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as femto cells) will also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1A In the example shown, BS 105d and 105e may be conventional macro BSs, while BS 105a-105c may be macro BSs with one of three-dimensional (3D), full-dimensional (FD), or massive MIMO capabilities. BS 105a-105c may utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. BS 105f may be a small cell BS, which may be a home node or a portable access point. BS 105 may support one or more (e.g., two, three, four, etc.) cells.

[0040] Network 100 may support synchronous operation or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.

[0041] UE 115 is dispersed throughout the wireless network 100, and each UE 115 may be stationary or mobile. UE 115 may also be referred to as a terminal, a mobile station, a subscriber unit, a station, and the like. UE 115 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, and the like. In one aspect, UE 115 may be a device including a universal integrated circuit card (UICC). In another aspect, UE may be a device that does not include a UICC. In some aspects, UE 115 that does not include a UICC may also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a-115d is an example of a mobile smart phone type device that accesses the network 100. UE 115 may also be a machine that is specifically configured for connected communications (including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), and the like). UE 115e-115h are examples of various machines configured for communication to access network 100. UE 115i-115k are examples of vehicles equipped with wireless communication devices configured for communication to access network 100. UE 115 may be able to communicate with any type of BS, whether macro BS, small cell, etc. Figure 1A In the present disclosure, a lightning bolt (e.g., a communication link) indicates a wireless transmission between a UE 115 and a serving BS 105 (which is a BS designated to serve the UE 115 on a downlink (DL) and / or uplink (UL)), a desired transmission between BSs 105, a backhaul transmission between BSs, or a sidelink transmission between UEs 115.

[0042] In operation, BS 105a-105c uses 3D beamforming and cooperative spatial techniques (such as coordinated multi-point (CoMP) or multiple connections) to serve UEs 115a and 115b. Macro BS 105d can perform backhaul communications with BS 105a-105c and small cell BS 105f. Macro BS 105d can also send multicast services that UEs 115c and 115d subscribe to and receive. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.

[0043] The BSs 105 may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs 105 (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communications with the UEs 115. In various examples, the BSs 105 may communicate with each other directly or indirectly (e.g., through the core network) via a backhaul link (e.g., X1, X2, etc.), which may be a wired communication link or a wireless communication link.

[0044] The network 100 may also support mission-critical communications using ultra-reliable and redundant links for mission-critical devices, such as UE 115e, which may be a drone. The redundant communication links with UE 115e may include links from macro BSs 105d and 105e, and a link from a small cell BS 105f. Other machine-type devices, such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device), may communicate through the network 100 directly with BSs such as small cell BS 105f and macro BS 105e, or through communication with another user device, such as UE 115f that communicates temperature measurement information to a smart meter (UE 115g), which then reports to the network through the small cell BS 105f, which relays its information to the network, in a multi-action size configuration. The network 100 may also provide additional network efficiency through dynamic low latency TDD / FDD communications, such as V2V, V2X, C-V2X communications between UE 115i, 115j, or 115k and other UEs 115 and / or vehicle-to-infrastructure (V2I) communications between UE 115i, 115j, or 115k and BS 105.

[0045] In some implementations, the network 100 utilizes an OFDM-based waveform for communication. An OFDM-based system may divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, frequency bins, etc. Each subcarrier may be modulated with data. In some aspects, the subcarrier spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may depend on the system BW. The system BW may also be divided into subbands. In other aspects, the subcarrier spacing and / or the duration of the TTI may be scalable.

[0046] In some aspects, BS 105 may assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS 105 to UE 115, and UL refers to the transmission direction from UE 115 to BS 105. The communication may be in the form of a radio frame. A radio frame may be divided into a plurality of subframes or time slots, for example, about 10. Each time slot may also be divided into micro-time slots. In FDD mode, simultaneous UL transmissions and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band. In TDD mode, UL transmissions and DL transmissions occur in different time periods using the same frequency band. For example, a subset of subframes in a radio frame (e.g., a DL subframe) may be used for DL ​​transmission, and another subset of subframes in a radio frame (e.g., a UL subframe) may be used for UL transmission.

[0047] DL subframes and UL subframes may also be divided into several zones. For example, each DL subframe or UL subframe may have a predefined zone for the transmission of reference signals, control information, and data. Reference signals are predetermined signals that facilitate communication between BS 105 and UE 115. For example, reference signals may have a specific pilot pattern or structure, wherein pilot tones may span an operational BW or frequency band, and each pilot tone is located at a predefined time and a predefined frequency. For example, BS 105 may send a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable UE 115 to estimate a DL channel. Similarly, UE 115 may send a sounding reference signal (SRS) to enable BS 105 to estimate an UL channel. Control information may include resource assignments and protocol controls. Data may include protocol data and / or operational data. In some aspects, BS 105 and UE 115 may communicate using self-contained subframes. Self-contained subframes may include a portion for DL ​​communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a longer duration for DL ​​communications than for UL communications. A UL-centric subframe may include a longer duration for UL communications than for UL communications.

[0048] In some aspects, the network 100 may be an NR network deployed on a licensed spectrum. The BS 105 may send synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in the network 100 to facilitate synchronization. The BS 105 may broadcast system information associated with the network 100 (e.g., including a master information block (MIB), residual system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some aspects, the BS 105 may broadcast the PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB), and may broadcast the RMSI and / or OSI on a physical downlink shared channel (PDSCH). The MIB may be sent on a physical broadcast channel (PBCH).

[0049] In some aspects, a UE 115 attempting to access the network 100 may perform an initial cell search by detecting the PSS from the BS 105. The PSS may enable synchronization of period timing and may indicate a physical layer identification value. The UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identification value that may be combined with the physical layer identification value to identify a cell. The PSS and SSS may be located in the center portion of a carrier or at any suitable frequency within a carrier.

[0050] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESET) for physical downlink control channel (PDCCH) monitoring, physical UL control channel (PUCCH), physical UL shared channel (PUSCH), power control, and SRS.

[0051] After obtaining the MIB, RMSI, and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may send a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL grant, temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. Upon receiving the random access response, the UE 115 may send a connection request to the BS 105 and the BS 105 may respond with a connection response. The connection response may indicate contention resolution. In some examples, the random access preamble, the RAR, the connection request, and the connection response may be referred to as message 1 (MSG1), message 2 (MSG2), message 3 (MSG3), and message 4 (MSG4), respectively. In some examples, the random access process may be a two-step random access procedure, where the UE 115 may send a random access preamble and a connection request in a single transmission, and the BS 105 may respond by sending a random access response and a connection response in a single transmission.

[0052] After establishing the connection, UE 115 and BS 105 may enter a normal operation phase, in which operational data may be exchanged. For example, BS 105 may schedule UE 115 for UL communication and / or DL ​​communication. BS 105 may send UL scheduling grant and / or DL ​​scheduling grant to UE 115 via PDCCH. Scheduling grant may be sent in the form of DL control information (DCI). BS 105 may send DL communication signals (e.g., carrying data) to UE 115 via PDSCH according to the DL scheduling grant. UE 115 may send UL communication signals to BS 105 via PUSCH and / or PUCCH according to the UL scheduling grant. The connection may be referred to as an RRC connection. When UE 115 actively exchanges data with BS 105, UE 115 is in an RRC connected state.

[0053] In an example, after establishing a connection with BS 105, UE 115 may initiate an initial network attachment procedure with network 100. BS 105 may coordinate with various network entities or fifth generation core (5GC) entities, such as access and mobility function (AMF), serving gateway (SGW) and / or packet data network gateway (PGW), to complete the network attachment procedure. For example, BS 105 may coordinate with network entities in 5GC to identify UE, authenticate UE and / or authorize UE to transmit and / or receive data in network 100. In addition, AMF may assign a set of tracking areas (TAs) to UE. Once the network attachment procedure is successful, a context is established in AMF for UE 115. After successfully attaching to the network, UE 115 may move around the current TA. For tracking area update (TAU), BS 105 may request UE 115 to periodically update network 100 with the location of UE 115. Alternatively, UE 115 may report the location of UE 115 to network 100 only when entering a new TA. The TAU allows the network 100 to quickly locate and page the UE 115 when an incoming data packet or call for the UE 115 is received.

[0054] In some aspects, BS 105 may communicate with UE 115 using hybrid automatic repeat request (HARQ) technology to improve communication reliability, for example, to provide URLLC services. BS 105 may schedule UE 115 for PDSCH communication by sending DL grant in PDCCH. BS 105 may send DL data packets to UE 115 according to the scheduling in PDSCH. DL data packets may be sent in the form of transport blocks (TBs). If UE 115 successfully receives the DL data packet, UE 115 may send HARQ ACK to BS 105. Conversely, if UE 115 fails to successfully receive the DL transmission, UE 115 may send HARQ NACK to BS 105. Upon receiving HARQ NACK from UE 115, BS 105 may retransmit the DL data packet to UE 115. The retransmission may include the same decoded version of the DL data as the initial transmission. Alternatively, the retransmission may include a decoded version of the DL data different from the initial transmission. The UE 115 may apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding. The BS 105 and the UE 115 may also apply HARQ to UL communications using a substantially similar mechanism as DL HARQ.

[0055] In some aspects, the network 100 may operate on a system BW or a component carrier (CC) BW. The network 100 may divide the system BW into multiple BWPs (e.g., parts). The BS 105 may dynamically assign the UE 115 to operate on a specific BWP (e.g., a specific part of the system BW). The assigned BWP may be referred to as an active BWP. The UE 115 may monitor the active BWP to find signaling information from the BS 105. The BS 105 may schedule the UE 115 to perform UL or DL ​​communications in the active BWP. In some aspects, the BS 105 may assign a pair of BWPs within the CC to the UE 115 for UL and DL communications. For example, the BWP pair may include one BWP for UL communication and one BWP for DL ​​communication.

[0056] In some aspects, network 100 may operate on a shared channel, which may include a shared frequency band and / or an unlicensed frequency band. For example, network 100 may be an NR-U network operating on an unlicensed frequency band. In such aspects, BS 105 and UE 115 may be operated by multiple network operation entities. In order to avoid conflicts, BS 105 and UE 115 may adopt a listen-before-talk (LBT) procedure to monitor a transmit opportunity (TXOP) in a shared channel. TXOP may also be referred to as COT. The goal of LBT is to protect reception at the receiver from interference. For example, a transmitting node (e.g., BS 105 or UE 115) may perform LBT before transmitting in a channel. When LBT passes, the transmitting node may continue to transmit. When LBT fails, the transmitting node may prohibit transmitting in the channel.

[0057] LBT may be based on energy detection (ED) or signal detection. For LBT based on energy detection, when the signal energy measured from the channel is below a threshold, the result of LBT is passed. Conversely, when the signal energy measured from the channel exceeds a threshold, the result of LBT is a failure. For LBT based on signal detection, when a channel reservation signal (e.g., a predetermined preamble signal) is not detected in the channel, the result of LBT is passed. In addition, LBT may be in a variety of modes. The LBT mode may be, for example, type 4 (CAT4) LBT, type 2 (CAT2) LBT, or type 1 (CAT1) LBT. CAT1 LBT is referred to as a no-LBT mode, in which no LBT is performed before transmission. CAT2 LBT refers to LBT without a random backoff period. For example, a transmitting node may determine a channel measurement in a time interval and determine whether the channel is available based on a comparison of the channel measurement with an ED threshold. CAT4 LBT refers to an LBT with a random backoff and a variable contention window (CW). For example, the sending node may draw a random number and back off for a duration in a certain time unit based on the drawn random number.

[0058] Figure 1B A diagram illustrating an example disaggregated base station 102 architecture is shown. The disaggregated base station 102 architecture may include one or more central units (CUs) 150 that may communicate directly with a core network 104 via a backhaul link, or indirectly with the core network 104 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 145 associated with a service management and orchestration (SMO) framework 135, or both. The CU 150 may communicate with one or more distributed units (DUs) 130 via respective midhaul links, such as an F1 interface. The DU 130 may communicate with one or more radio units (RUs) 140 via respective fronthaul links. The RU 140 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 140.

[0059] Each of the units (i.e., CU 150, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 145, and SMO framework 135) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.

[0060] In some aspects, the CU 150 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 150. The CU 150 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 150 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 150 may be implemented to communicate with the DU 130 for network control and signaling.

[0061] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) coding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 150.

[0062] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional partitioning (such as lower layer functional partitioning). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs. In some specific implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 150 in a cloud-based RAN architecture (such as a vRAN architecture).

[0063] The SMO framework 135 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 135 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 135 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 150, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 135 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. In addition, in some specific implementations, the SMO framework 135 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 135 may also include a non-RT RIC 145 configured to support the functionality of the SMO framework 135 .

[0064] The non-RT RIC 145 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 145 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 150, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0065] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 145 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 135 or the non-RT RIC 145. In some examples, the non-RT RIC 145 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 145 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 135 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0066] See again Figure 1A In some aspects, one or more of the UEs 115 may be configured to communicate with two or more of the BSs 105 in a multiple transmit receive point (mTRP) communication scenario. For example, the UE 115 may be configured with a first frequency band or cell, where the cell is configured for communication on more than one TRP. The UE 115 may receive DL communications (e.g., DCI, PDSCH, DL reference signals) from each TRP. The UE 115 may also send UL communications to one or more of the TRPs.

[0067] Figure 2 A multi-transmit-receive point (mTRP) communication scenario 200 is illustrated in accordance with aspects of the present disclosure. The communication scenario 200 involves a first TRP 205a, a second TRP 205b, and a UE 215. In some aspects, one or both of the TRPs 205 may be one or more BSs in the BSs 105 of the network 100. In other aspects, one or both of the TRPs 205 may be another type of wireless node or wireless communication device configured to communicate with one or more UEs in the network. In some aspects, the UE 215 may be one of the UEs 115 of the network 100. For simplicity, Figure 2 One UE 215 and two TRPs 205 are illustrated, but a greater number of UEs 215 (e.g., about 2, 3, 4, 5, 6, 7, 8, 9, 10, or more) and / or TRPs 205 (e.g., about 2, 3, 4, or more) may be supported. In scenario 200, TRPs 205 and UEs 215 communicate with each other on at least one radio frequency band. For example, TRPs 205 may be configured to communicate with UEs 215 on one or more cells corresponding to one or more frequency bands. In some aspects, each of the one or more cells corresponds to a component carrier (CC). In other aspects, each of the one or more cells corresponds to a bandwidth part (BWP). One or more cells may include a primary cell (PCell) or a specific cell (SpCell).

[0068] In some aspects, one or two of the TRPs 205 may be capable of generating multiple directional transmit beams in multiple beams or spatial directions (e.g., about 2, 4, 8, 16, 32, 64, or more), and may select a transmit beam or beam direction to communicate with the UE 215 based on the location of the UE 215 relative to the location of the TRP 205 and / or any other environmental factors (e.g., surrounding reflectors and / or scatterers). For example, the second TRP 205b may select a transmit beam that provides the best quality (e.g., has the highest received signal strength) for transmission to the UE 215. The TRP 205b may also select a receive beam that provides the best quality (e.g., has the highest received signal strength) for reception from the UE 215. Figure 2 As illustrated, TRP 205b may generate three beams 204a, 204b, and 204c. TRP 205b may determine, for example, based on a beam discovery or beam selection process, that it may utilize beam 204b or beam 204c to communicate with UE 215.

[0069] As described above, one or both of the TRPs 205 may schedule a UE 215 for UL or DL ​​communications on a frequency band. For purposes of this disclosure, a frequency band may include, for example, a component carrier (CC) and / or a bandwidth part (BWP). In single-DCI mTRP communications, DCI from one of the TRPs (e.g., TRP 205a) may schedule communications for a first TRP 205a and a second TRP 205b. In multi-DCI (mDCI) mTRP communications, each TRP 205 may send DCI to a UE 215 to schedule communications. Figure 2An mDCI mTRP communication scenario may be illustrated, whereby the first TRP 205a schedules DL communication and / or UL communication with the UE 215 via the first communication link 207, and the second TRP 205b schedules DL communication and / or UL communication with the UE 215 via the second communication link 208. In some aspects, the UE 215 may be configured to use carrier aggregation to communicate with one or both TRPs in the TRP 205 using one or more serving cells. The serving cells may include, for example, a primary cell (PCell), one or more secondary cells (SCells), a PUCCH secondary cell (PSCell), and / or a specific cell (SpCell). In some aspects, one or more serving cells in the serving cell may be configured for mDCI mTRP communication, and one or more cells may be configured for single TRP communication. If the cell configuration indicates two CORESET pool index values ​​and two timing advance groups (TAGs), the cell may be configured for mDCI mTRP communication. For example, the mDCI cell may indicate two CORESETPoolIndex values ​​and two TAG indicators. A single TRP cell configuration may indicate a single TAG indicator and / or a single CORESETPoolIndex value.

[0070] In some aspects, sDCI and / or mDCI may be associated with a format and may include one or more fields or parameters to indicate to the UE one or more parameters for the UL channel or communication. For example, the DCI may include frequency resource assignments, time resource assignments, beam-related parameters, power control parameters, and / or any other appropriate or relevant information for the UE to send UL communications in the UL channel. For example, the DCI may indicate one or more TCI code points, TCI states, power control (PC) commands, frequency allocations for scheduled UL communications, time allocations for scheduled UL communications, antenna port indications, and / or any other relevant parameters for UL communications. In addition, RRC messages and / or MAC-CEs may be used to configure or activate UL communications. In some aspects, the RRC message may configure one or more CORESET pool index values, TAGs, and / or any other cell configurations associated with the UL channel or configuration.

[0071] In some instances, the UE may be instructed and / or configured to send two UL communications to two different TRPs during the same time period. For example, the UE may be configured for SDM mTRP communications, and the two UL communications may be scheduled or indicated during the same time period and using the same frequency resources. In another aspect, communications may be scheduled for different parts of the same inter-band CC, or UL communications may be scheduled for different CCs within the same frequency band. However, in some instances, the two UL communications may not be sent at the same time. For example, in some aspects, UL communications may be indicated using different TCI states that cannot be sent at the same time. In other aspects, UL communications may be indicated using the same TCI state and overlapping frequency resources so that the two overlapping UL communications may not be sent at the same time. Scheduling, indicating and / or activating two UL channels that cannot be sent at the same time during the same time period may be referred to as a conflict or scheduling conflict.

[0072] Figure 3 A UL mTRP scheduling conflict scenario 300 is illustrated. The scenario 300 may illustrate a communication link between a UE, a first TRP (TRP1), and a second TRP (TRP2). The UE may be configured for mTRP communications with both TRP1 and TRP2. The dashed line may refer to a communication link. In some aspects, the UE is configured to communicate with two TRPs using a single CC. In some aspects, the single CC may be intra-band (within the same frequency band) or inter-band (across two frequency bands). In other aspects, TRP1 may communicate with the UE using a first CC, and TRP2 may communicate with the UE using a second CC, wherein the first CC and the second CC are in the same frequency band. In some aspects, the two TRPs may communicate with the UE using the same logical cell. In other aspects, TRP1 may communicate with the UE using a first cell (e.g., a primary cell / special cell), and TRP2 may communicate with the UE using a second cell (e.g., a secondary cell). In some aspects, the mTRP communication scenario may use frequency division multiplexing (FDM), time division multiplexing (TDM), or space division multiplexing (SDM).

[0073] The UE may receive DCI 302 from TRP1 that schedules PUSCH 304. In some aspects, DCI 302 may be mDCI that schedules PUSCH 304 to be sent back to TRP1. In other aspects, DCI 302 may be sDCI that schedules PUSCH 304 to be sent to TRP2 or sent back to TRP1. The UE may also be instructed, configured, or otherwise scheduled to send SRS 306 to TRP2. However, as an alternative or in addition to SRS 306, other UL communications and / or UL channels are also contemplated. For example, the UL may be instructed or configured to send PRACH, PUCCH, and / or any other suitable UL channel. As shown, SRS 306 at least partially coincides or overlaps with PUSCH 304 in time. In addition, as described above, PUSCH 304 and SRS 306 may be scheduled on the same or overlapping frequency resources, in intra-band frequency resources, and / or within the same CC. In addition, the DCI 302 may indicate or be associated with a first TCI state, such that the UE sends PUSCH 304 to TRP1, for example, based on an appropriate spatial filter. Similarly, the SRS 306 may be configured or indicated with a second TCI state for transmission to TRP2 using an appropriate spatial filter. In some aspects, the UE may not be able to simultaneously transmit PUSCH 304 and SRS 306 using the first TCI state and the second TCI state. Therefore, the PUSCH 304 and SRS 306 may be described as conflicting, or having an UL scheduling conflict.

[0074] The present disclosure describes methods, schemes, and mechanisms for resolving, avoiding, and / or handling UL conflicts in mTRP communication scenarios based on mTRP prioritization configuration. In some aspects, the mTRP prioritization configuration indicates or assigns different priorities to PUSCH 304 and SRS 306 based on, for example, UL channel type, corresponding TRP, TCI state, time assignment, and / or any other suitable parameters of UL communication. Figure 5 and Figure 8 A method for handling UL conflicts in mTRP communication scenarios is illustrated and described.

[0075] Figure 4 4 is a timing diagram illustrating a transmit frame structure 400 according to some embodiments of the present disclosure. The transmit frame structure 400 may be employed by a BS (such as BS 105) and a UE (such as UE 115) in a network (such as network 100) for communication. In particular, the BS may communicate with the UE using the time-frequency resources configured as shown in the transmit frame structure 400. Figure 44. In the example of FIG. 4, the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. The transmit frame structure 400 includes a radio frame 402. The duration of the radio frame 402 may vary according to various embodiments. In one example, the radio frame 402 may have a duration of approximately ten milliseconds. The radio frame 402 includes M subframes 404, where M may be any suitable positive integer. In one example, M may be approximately 10.

[0076] Each subframe 404 may include N slots 406, where N is any suitable positive number including 1. Each slot 406 includes a plurality of subcarriers 418 in frequency and a plurality of symbols 416 in time. The number of subcarriers 418 and / or the number of symbols 416 in a slot 406 may vary according to various implementations, for example, based on channel bandwidth, subcarrier spacing (SCS), and / or cyclic prefix (CP). One subcarrier 418 in frequency and one symbol 416 in time form one resource element (RE) 420 for transmission.

[0077] BS (e.g. Figure 1A The BS 105 in the example may schedule the UE (eg, Figure 1A BS 105 may schedule UE 115 to monitor PDCCH transmission by instantiating a search space associated with CORESET 412. The search space may also be instantiated with an associated CORESET 414. Thus, Figure 4 As illustrated in the example of , within time slot 406 that is part of the search space for UE 115 to monitor control information from BS 105, there are two CORESETs, and therefore two monitoring opportunities.

[0078] Although Figure 4 Two CORESETs 412 and 414 are illustrated, but for purposes of simplicity of illustration and discussion, it will be appreciated that embodiments of the present disclosure may extend to more CORESETs, such as about 3, 4, or more. Each CORESET may include a resource set spanning a particular number of subcarriers 418 and a plurality of symbols 416 (e.g., about 1, 2, or 3) within a time slot 406. As an alternative to multiple different CORESETs within a time slot 406, one or more of the many CORESETs may be in a different time slot than the other CORESETs. Each CORESET has an associated mapping of control channel elements (CCEs) to resource element groups (REGs). A REG may include a group of REs 420. A CCE defines how DL control channel data may be sent.

[0079] The BS 105 may configure one or more search spaces for the UE 115 by associating a CORESET 412 with a starting position (e.g., a starting time slot 406), a symbol 416 position within a time slot 406, a periodicity or time pattern, and a candidate mapping rule. For example, the search space may include candidate sets mapped to CCEs with aggregation levels 1, 4, 4, 8, and / or 12 CCEs. As an example, the search space may include a CORESET 412 starting at the first symbol 416 indexed within the starting time slot 406. The search space may also include a CORESET 414 starting at a later symbol index within the starting time slot 406. The exemplary search space may have a periodicity of approximately 5 time slots and may have candidates with aggregation levels of 1, 4, 4, and / or 8.

[0080] UE 115 may perform blind decoding in the search space to search for DL ​​control information (e.g., slot format information and / or scheduling information) from the BS. In some examples, the UE may search a subset of the search space based on certain rules associated with, for example, the channel estimation and / or blind decoding capabilities of the UE. One such example of DL control information that UE 115 may blindly decode is the PDCCH from BS 105.

[0081] like Figure 4 As shown, CORESET 412 and CORESET 414 may be at different frequencies from each other. The CORESETs may be non-contiguous as shown, or they may be contiguous. The frequency ranges of CORESET 412 and CORESET 414 may or may not overlap (e.g., Figure 4 In some aspects, the frequency offset between CORESETs is a multiple of six RBs, or some other offset. Figure 4 In an example of , each of CORESET 412 and CORESET 414 may carry a different PDCCH transmission (or not at all, even for a portion of the search space of UE 115). CORESET 412 and CORESET 414 may have other characteristics that differ from each other, not just frequency (or instead of frequency). For example, they may differ in CCE to REG mapping and / or REG bundling. Alternatively, they may also be associated with different TCI states and, thus, different beams. In addition, the CCE index for PDCCH monitoring opportunities may differ across CORESETs. Other forms of diversity between CORESETs may also be implemented, including some combination of different characteristics (e.g., all of the above differences together or a subset thereof).

[0082] Figure 5is a signaling diagram illustrating a method 500 for mTRP communication according to some aspects of the present disclosure. The method 500 is employed by a first TRP (TRP1), a second TRP (TRP2), and a UE 515. In some aspects, one or both of the TRPs may be one of the BSs 105 in the network 100. In other aspects, one or both of the TRPs may be another type of wireless node or connection point. In some aspects, these TRPs may be referred to as network devices or network entities. In some aspects, one or both of the TRPs may include a converged BS, and / or one or more portions of a decomposed BS, as described above with respect to Figure 1B In some aspects, UE 515 may be one of UEs 115 of network 100. UE 515 may be configured to perform mTRP communications with both TRP1 and TRP2. However, it should be understood that UE 515 may be configured to perform mTRP communications with more than two TRPs (including three, four, five, six, and / or any other suitable number of TRPs).

[0083] As described above, UE 515 may be configured for single DCI (sDCI) mTRP communication or multi-DCI (mDCI) mTRP communication. In sDCI mTRP communication, UE 515 may receive scheduling DCI from one of TRP1 or TRP2 for DL ​​and / or UL communication transmitted with TRP 1 and TRP2. In mDCI mTRP communication, UE 515 may receive scheduling DCI from each of TRP1 or TRP2 for DL ​​and / or UL communication with each corresponding TRP. In some aspects, UE 515 is configured to communicate with two TRPs using a single CC. In some aspects, a single CC may be intra-band (within the same frequency band) or inter-band (across two frequency bands). In other aspects, TRP1 may communicate with the UE using a first CC, and TRP2 may communicate with the UE using a second CC, wherein the first CC and the second CC are in the same frequency band. In some aspects, the two TRPs may communicate with UE 515 using the same logical cell. In other aspects, TRP1 may use a first cell (e.g., a primary cell / special cell of a first physical cell index) to communicate with UE 515, and TRP2 may use a second cell (e.g., a secondary cell of a second physical cell index) to communicate with UE 515. In some aspects, the mTRP communication scenario may use frequency division multiplexing (FDM), time division multiplexing (TDM), or space division multiplexing (SDM).

[0084] At action 502, the UE 515 receives from TRP1 a first indication associated with a first UL communication scheduled for a first time period 503. In some aspects, the first indication may include a first DCI that schedules the first UL communication for the first time period 503 on a first set of frequency resources. In some aspects, the first DCI may indicate a first TCI state and an UL transmission using a first TRP (e.g., TRP1). In other aspects, the UE 515 may receive a different DCI, MAC-CE, RRC message, and / or any other suitable type of activation, configuration, and / or otherwise instructing the UE 515 to transmit the first UL communication. In some aspects, action 502 includes receiving more than one of a first DCI, a second DCI, a MAC-CE, an RRC message, and / or a combination thereof. In some aspects, the same field of the first DCI may indicate both the first TCI state and the UL transmission for TRP1. In other aspects, the first DCI may indicate the first TCI state, and the second DCI may indicate the UL transmission for TRP1. In some aspects, the method 500 may further include the UE 515 receiving an RRC configuration indicating a CORESET pool index, and the CORESET pool index value may be associated with TRP1.

[0085] At action 504, the UE 515 receives from TRP2 a second indication associated with a second UL communication scheduled for the second time period 505. The second time period 505 overlaps at least partially in time with the first time period 503. In some aspects, the second indication may include a DCI that schedules a second UL communication for the second time period 505 on a second set of frequency resources. The second set of frequency resources may be the same or different from the first set of frequency resources. For example, the first frequency resource and the second frequency resource may be associated with at least one of the same CC and / or the same frequency band, as described above. In some aspects, the DCI may indicate a second TCI state and an UL transmission for a second TRP (e.g., TRP2). In other aspects, the UE 515 may receive different DCIs, MAC-CEs, RRC messages, and / or any other suitable type of activation, configuration, and / or otherwise instructing the UE 515 to send a second UL communication. In some aspects, action 504 includes receiving more than one of a third DCI, a fourth DCI, a MAC-CE, an RRC message, and / or a combination thereof. In some aspects, the same field of the DCI received at act 504 may indicate both the second TCI state and the UL transmission for TRP2. In other aspects, the DCI may indicate the second TCI state, and a different DCI may indicate the UL transmission for TRP2. In some aspects, the method 500 may also include the UE 515 receiving an RRC configuration indicating a CORESET pool index, and the CORESET pool index value may be associated with TRP2.

[0086] Based on the coincidence and time of the first and second UL communications indicated at actions 502 and 504, and based on their corresponding indicated TCI states, the first UL communication may conflict with the second UL communication in time. In other words, the first UL communication and the second UL communication may not be sent simultaneously by the UE. For example, the first and second TCI states may not be configured for or may not be sent simultaneously using the frequency resources indicated for the UL communication. Therefore, at action 506, the UE 515 determines the prioritization of the first UL communication and the second UL communication based on the mTRP UL prioritization configuration. In some aspects, the mTRP UL prioritization configuration may include a set of hard-coded or pre-configured rules that can be used to prioritize conflicting UL communications in mTRP communication scenarios. In other aspects, the mTRP UL prioritization configuration may be semi-static and / or dynamically configurable so that the prioritization configuration can be updated or modified by the network.

[0087] The mTRP UL prioritization configuration may configure the UE 515 to assign priority to or prioritize UL communications based on one or more of: a UL channel type associated with the UL communications, indicated frequency resources indicated for the UL communications, indicated time resources indicated for the UL communications, a type of information associated with the UL communications (e.g., what information will be carried in each channel), a TRP associated with the UL communications, an indicated type of UL communications (e.g., DCI scheduled, RRC configured, MAC-CE activated, etc.), and / or any other suitable prioritization.

[0088] In this regard, in one aspect, the first UL communication is associated with a first UL channel type, and the second UL communication is associated with a second UL channel type that is different from the first UL channel type. In some aspects, the mTRP Ul prioritization configuration indicates that the first uplink channel type has a higher priority than the second uplink channel type. In some aspects, the mTRPUL prioritization configuration may specify PRACH as having a higher priority than PUCCH. In some aspects, the mTRP UL prioritization configuration may specify PUCCH as having a higher priority than PUSCH. In another aspect, the mTRP UL prioritization configuration may specify PUSCH as having a higher priority than SRS. In other aspects, the mTRP UL prioritization configuration may specify PUCCH as having a higher priority than PRACH. In other aspects, the mTRP UL prioritization configuration may specify PUSCH as having a higher priority than PUCCH.

[0089] In another aspect, the mTRP UL priority of the first UL communication and the second UL communication may be based on a combination of UL channel type and information carried in or associated with the first and second UL communications. In some aspects, the mTRP UL prioritization configuration may specify PRACH as having a higher priority than PUCCH carrying HARQ-ACK information, scheduling request (SR) and / or link recovery request (LRR) and / or PUSCH transmission carrying HARQ-ACK information. In some aspects, the mTRP UL prioritization configuration may specify PUCCH carrying HARQ-ACK information, SR and / or LRR and / or PUSCH transmission carrying HARQ-ACK information as having a higher priority than PUCCH transmission carrying channel state information (CSI) and / or PUSCH transmission carrying CSI. In another aspect, the mTRP UL prioritization configuration may specify PUCCH transmission carrying channel state information (CSI) and / or PUSCH transmission carrying CSI as having a higher priority than PUSCH transmission not including HARQ-ACK information or CSI. In another aspect, the mTRP UL prioritization configuration may designate a PUCCH transmission carrying channel state information (CSI) and / or a PUSCH transmission carrying CSI as having a higher priority than a PUSCH transmission on a Pcell for a type 2 random access procedure. In another aspect, the mTRP UL prioritization configuration may designate a PUSCH transmission on a Pcell for a type 2 random access procedure and / or a PUSCH transmission without HARQ-ACK information or CSI as having a higher priority than an SRS transmission. In some aspects, the mTRP UL prioritization configuration may designate a non-periodic SRS as having a higher priority than a semi-persistent and / or periodic SRS. In some aspects, the mTRP UL prioritization configuration may designate a non-periodic SRS as having a higher priority than a serving cell or than a PRACH transmission on a Pcell. However, in lieu of or in addition to the prioritization explicitly mentioned above, the present invention also contemplates other prioritizations. For example, in some aspects, the mTRP UL prioritization configuration may indicate that a PUSCH transmission carrying HARQ-ACK information or CSI has a higher priority than a PUCCH transmission with HARQ-ACK information. In another aspect, the mTRP UL prioritization configuration may indicate that aperiodic SRS has a higher priority than a PUSCH that does not include HARQ-ACK and / or CSI.

[0090] In another example, the mTRP UL prioritization configuration may cause the UE 515 to assign priorities based on the TRP associated with the UL communication. For example, in some aspects, a first UL communication is associated with TRP1 and a second UL communication is associated with TRP2. The TRP associated with each UL communication may be indicated based on a TCI state indicated in a scheduling DCI and / or a CORESET pool index associated with, indicated for, or configured for the UL communication. In some aspects, UL communications associated with a TCI state of a smaller ID or number may be prioritized by the UE 515 for transmission.

[0091] In another aspect, the mTRP UL prioritization configuration may cause the UE 515 to assign a priority based on the indication type of each of the first indication and the second indication. For example, the first indication may be associated with the first indication type, and the second indication may be associated with the second indication type. In one example, the first indication type may be a DCI that schedules a first UL communication, and the second indication type may be an RRC message or MAC-CE that configures and / or activates one or more opportunities for an UL channel associated with a second UL communication. In some aspects, the mTRP UL prioritization configuration may cause the UE 515 to assign a higher priority to the first UL communication scheduled by the DCI. In other aspects, the mTRP UL prioritization configuration may assign a higher priority to the second UL communication configured by the RRC and / or the second UL communication activated by the MAC-CE. In some aspects, the mTRP UL prioritization configuration may cause the UE 515 to assign a higher priority to the UL communication activated by the MAC-CE than to the UL communication configured by the RRC.

[0092] In another aspect, the mTRP UL prioritization configuration may cause the UE 515 to assign priorities based on the time domain allocation for the first UL communication and the second UL communication. For example, in some aspects, the mTRP UL prioritization configuration may cause the UE 515 to assign relative priorities based on the start symbol, end symbol and / or duration of the first UL communication and the second UL communication. For example, the mTRP indication may cause the UE 515 to prioritize the first UL communication based on the first UL communication having an earlier start symbol than the second UL communication. In another aspect, the mTRP indication may cause the UE 515 to prioritize the first UL communication based on the first UL communication having an earlier end symbol relative to the second UL communication. In another aspect, the mTRP indication may cause the UE 515 to prioritize the first UL communication based on the first UL communication having a shorter duration or a longer duration relative to the second UL communication. In some aspects, the mTRP UL prioritization configuration may cause the UE 515 to prioritize the UL communication based on a combination of time domain allocation parameters. For example, if the first UL communication and the second UL communication are scheduled for the same starting symbol, the UE 515 may prioritize the UL communication with an earlier ending symbol or a later ending symbol. In another aspect, if the first UL communication and the second UL communication are associated with the same starting symbol, the UE 515 may prioritize the UL communication with a longer duration or a shorter duration.

[0093] In some aspects, the mTRP UL prioritization configuration may cause the UE 515 to prioritize UL communications based on a combination of the parameters indicated above. For example, the UE 515 may first use the UL channel type to determine the priority, but if the UL channel type priorities are the same, then the TRP, TCI, indication type, and / or time domain allocation may be considered. In another aspect, the UE 515 may first use the indication type to determine the UL priority, but if the indication type priority is the same for both the first UL communication and the second UL communication, then the time domain allocation may be used.

[0094] At action 508, the UE 515 sends a first UL communication to TRP1 based on the mTRP UL prioritization configuration. In some aspects, the method 500 may include sending all of the two conflicting UL communications. In this regard, as indicated by the dotted line of action 510, the UE 515 may send a second UL communication to TRP2 based on the UL prioritization configuration. In some aspects, the UE 515 may send the second UL communication based on the same TCI state as the first UL communication. For example, the UE 515 may use the first TCI state to send the second UL communication. In other aspects, the UE 515 may use the second TCI state to send the second UL communication. The UE 515 may use one or more of the above parameters or prioritization schemes (including indication type, UL channel type, time domain parameters, TRP and / or TCI state ID) to select a single TCI state for sending both the first UL communication and the second UL communication. In some aspects, the transmission of the first UL communication and the second UL communication may be performed using different time domains and / or different frequency domain resources for each configuration. For example, the UE 515 may use FDM or TDM to send the first UL communication and the second UL communication using the same TCI state. In some aspects, the TCI state of the UL channels may be reset or updated by selecting a single TCI state for two UL channels associated with the UL communications.

[0095] In another aspect, instead of sending the first UL communication at act 508, the method 500 may include preventing sending either the first UL communication or the second UL communication based on the first UL communication conflicting with the second UL communication. In this regard, the UE 515 may treat the conflict of UL communications that cannot be sent simultaneously in the mTRP communication scenario as an error condition.

[0096] Figure 6 6 is a block diagram of an exemplary BS 600 according to some aspects of the present disclosure. BS 600 may be such as Figure 1A discussed in BS 105 and / or Figure 2 and Figure 5 . For example, BS 600 may be configured as one TRP among multiple TRPs in a network configured to communicate with at least one UE (such as one of UEs 115, 215, 515 and / or 700). As shown, BS 600 may include a processor 602, a memory 604, an mTRP priority module 608, a transceiver 610 including a modem subsystem 612 and an RF unit 614, and one or more antennas 616. These elements may be coupled to each other. The term "coupled" may refer to direct or indirect coupling or connection to one or more intervening elements. For example, these elements may communicate directly or indirectly with each other, for example, via one or more buses.

[0097] The processor 602 may have various features as a particular type of processor. For example, these features may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 602 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0098] The memory 604 may include cache memory (e.g., cache memory of the processor 602), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, the memory 604 may include a non-transitory computer-readable medium. The memory 604 may store instructions 606. The instructions 606 may include instructions that, when executed by the processor 602, cause the processor 602 to perform the operations described herein (e.g., Figure 2 and Figure 5 Instructions 606 may also be referred to as program code. Program code may be used to cause the wireless communication device to perform these operations, for example, by causing one or more processors (such as processor 602) to control or command the wireless communication device to do so. The terms "instructions" and "code" should be broadly interpreted to include any type of computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, procedures, etc. "Instructions" and "code" may include a single computer-readable statement or multiple computer-readable statements.

[0099] The mTRP priority module 608 may be implemented via hardware, software, or a combination thereof. For example, the mTRP priority module 608 may be implemented as a processor, circuit, and / or instructions 606 stored in the memory 604 and executed by the processor 602. In some examples, the mTRP priority module 608 may be integrated within the modem subsystem 612. For example, the mTRP priority module 608 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 612. The mTRP priority module 608 may communicate with one or more components of the BS 600 to implement various aspects of the present disclosure, such as, Figure 2 and Figure 5 all aspects.

[0100] In some aspects, the mTRP priority module 608 is configured to send or cause the transceiver 610 to send an indication of UL communications associated with the TCI state and TRP. In some aspects, the first UL communication is scheduled to overlap at least partially in time with the second UL communication associated with the second TRP and the second TCI state. In some aspects, the first UL communication and the second UL communication may be scheduled on at least one of the same CC or the same frequency band. In another aspect, the mTRP priority module 608 is configured to receive the first UL communication based on the mTRP UL prioritization configuration. In some aspects, the mTRP priority module 608 may be configured to cause the transceiver 610 to send the mTRP UL prioritization configuration to at least one UE. In other aspects, the mTRP priority module 608 is configured to send or cause the transceiver 610 to send the indication by sending a DCI including a scheduling grant associated with the first UL communication, a TCI state indication, and / or any other parameters. In other aspects, the mTRP priority module 608 is configured to send or cause the transceiver 610 to send the indication by sending an RRC configuration, a MAC-CE, and / or any other suitable indication that configures, activates, or otherwise indicates the first UL communication.

[0101] In some aspects, the mTRP priority module 608 may be configured to perform one or more aspects of the method 500 .

[0102] As shown, the transceiver 610 may include a modem subsystem 612 and an RF unit 614. The transceiver 610 may be configured to communicate bidirectionally with other devices, such as UE 115 and / or BS 600 and / or another core network element. The modem subsystem 612 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC decoding scheme, a turbo decoding scheme, a convolutional decoding scheme, a digital beamforming scheme, etc.). The RF unit 614 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / encoded data (e.g., RRC tables for channel access configuration, scheduling grants, channel access configuration activation, RRC configuration, PDSCH data, PDCCH DCI, etc.) from the modem subsystem 612 (for outbound transmission) or from another source (such as UE 115, 215 and / or UE 700). The RF unit 614 may be further configured to perform analog beamforming in conjunction with digital beamforming. Although shown as integrated together in transceiver 610, modem subsystem 612 and / or RF unit 614 may be separate devices that are coupled together at BS 600 to enable BS 600 to communicate with other devices.

[0103] The RF unit 614 may provide modulated and / or processed data, such as data packets (or more generally, data messages that may contain one or more data packets and other information), to the antenna 616 for transmission to one or more other devices. The antenna 616 may also receive data messages sent from other devices and provide the received data messages for processing and / or demodulation at the transceiver 610. The transceiver 610 may provide the demodulated and decoded data (e.g., channel sensing reports, PUCCH UCI, PUSCH data, etc.) to the timing mTRP priority module 608 for processing. The antenna 616 may include multiple antennas of similar design or different design to maintain multiple transmission links.

[0104] In one aspect, the BS 600 may include multiple transceivers 610 that implement different RATs (e.g., NR and LTE). In one aspect, the BS 600 may include a single transceiver 610 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 610 may include various components, where different combinations of components may implement different RATs.

[0105] Furthermore, in some aspects, the processor 602 is coupled to the memory 604 and the transceiver 610. The processor 602 is configured to communicate a plurality of channel access configurations with the second wireless communication device via the transceiver 610. The processor 602 is further configured to communicate a scheduling grant with the second wireless communication device via the transceiver 610 for communicating a communication signal in an unlicensed frequency band, wherein the scheduling grant includes an indication of a first channel access configuration in the plurality of channel access configurations. The processor 602 is further configured to communicate the communication signal with the second wireless communication device in the unlicensed frequency band via the transceiver 610 based on the first channel access configuration.

[0106] Figure 7 700 is a block diagram of an exemplary UE 700 according to some aspects of the present disclosure. The UE 700 may be Figure 1A UE 115 as discussed in Figure 2 UE 215 discussed in, or as Figure 5 515 discussed in . As shown, UE 700 may include a processor 702, a memory 704, an mTRP priority module 708, a transceiver 710 including a modem subsystem 712 and a radio frequency (RF) unit 714, and one or more antennas 716. These elements may be coupled to each other. The term "coupled" may refer to being directly or indirectly coupled or connected to one or more intervening elements. For example, these elements may communicate directly or indirectly with each other, such as via one or more buses.

[0107] The processor 702 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 702 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0108] Memory 704 may include cache memory (e.g., cache memory of processor 702), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one aspect, memory 704 includes a non-transitory computer-readable medium. Memory 704 may store or have recorded thereon instructions 706. Instructions 706 may include instructions that, when executed by processor 702, cause processor 702 to perform operations in conjunction with aspects of the present disclosure (e.g., Figure 2 and Figure 5 Instructions 706 may also be referred to as code, which may be broadly interpreted to include any type of computer-readable statements, such as discussed above with respect to FIG. 9 .

[0109] The mTRP priority module 708 may be implemented via hardware, software, or a combination thereof. For example, the mTRP priority module 708 may be implemented as a processor, circuit, and / or instructions 706 stored in the memory 704 and executed by the processor 702. In some aspects, the mTRP priority module 708 may be integrated within the modem subsystem 712. For example, the mTRP priority module 708 may be implemented by a combination of software components (e.g., executed by a DSP or a general purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 712. The mTRP priority module 708 may communicate with one or more components of the UE 700 to implement various aspects of the present disclosure, such as, Figure 2 and Figure 5 all aspects.

[0110] In some aspects, the mTRP priority module 708 is configured to receive, via the transceiver 710, an indication of a first UL communication associated with a first TCI state and a first TRP. In another aspect, the mTRP priority module 708 is further configured to receive, via the transceiver 710, an indication of a second UL communication associated with a second TCI state and a second TRP. In some aspects, the first UL communication is scheduled to overlap at least partially in time with the second UL communication. In some aspects, the first UL communication and the second UL communication may be scheduled on at least one of the same CC or the same frequency band. In another aspect, the mTRP priority module 708 is configured to send the first UL communication based on the mTRP UL prioritization configuration. In this regard, the mTRP priority module 708 may be configured to select or determine one of the first UL communication or the second UL communication based on the mTRP UL prioritization configuration, based on one or more of the indication type, the associated TCI state, the associated TRP, the UL channel type, the time domain for UL communication, the associated CORESET pool index, and / or any other suitable parameters as described herein, so as to prioritize one UL communication over other conflicting UL communications. In some aspects, the mTRP priority module 708 may be configured to cause the transceiver 710 to receive the mTRP UL prioritization configuration from, for example, a network entity. In other aspects, the mTRP priority module 708 is configured to receive or cause the transceiver 710 to receive these indications by receiving one or more DCIs including a scheduling grant associated with the first UL communication, a TCI state indication, and / or any other parameters. In other aspects, the mTRP priority module 708 is configured to receive or cause the transceiver 710 to receive such indications by receiving one or more of an RRC configuration, a MAC-CE, and / or any other suitable indication that configures, activates, or otherwise indicates UL communications.

[0111] In some aspects, the mTRP priority module 708 may be configured to perform one or more aspects of the method 500 .

[0112] As shown, the transceiver 710 may include a modem subsystem 712 and an RF unit 714. The transceiver 710 may be configured to communicate bidirectionally with other devices, such as BSs 105 and 600. The modem subsystem 712 may be configured to modulate and / or encode data from the memory 704 and / or the mTRP priority module 708 according to a modulation and coding scheme (MCS) (e.g., a low-density parity check (LDPC) decoding scheme, a turbo decoding scheme, a convolutional decoding scheme, a digital beamforming scheme, etc.). The RF unit 714 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data (e.g., channel sensing reports, PUCCH UCI, PUSCH data, etc.) transmitted from another source, such as a UE 115, a BS 105, or an anchor. The RF unit 714 may be further configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 710, the modem subsystem 712 and the RF unit 714 may be separate devices that are coupled together at the UE 700 to enable the UE 700 to communicate with other devices.

[0113] The RF unit 714 may provide modulated and / or processed data, such as data packets (or more generally, data messages that may include one or more data packets and other information), to the antenna 716 for transmission to one or more other devices. The antenna 716 may also receive data messages sent from other devices. The antenna 716 may provide the received data messages for processing and / or demodulation at the transceiver 710. The transceiver 710 may provide demodulated and decoded data (e.g., RRC tables for channel access configuration, scheduling grants, channel access configuration activation, timing advance configuration, RRC configuration, PUSCH configuration, SRS resource configuration, PUCCH configuration, BWP configuration, PDSCH data, PDCCH DCI, etc.) to the mTRP priority module 708 for processing. The antenna 716 may include multiple antennas with similar designs or different designs to maintain multiple transmission links.

[0114] In one aspect, the UE 700 may include multiple transceivers 710 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 700 may include a single transceiver 710 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 710 may include various components, where different combinations of components may implement different RATs.

[0115] Furthermore, in some aspects, the processor 702 is coupled to the memory 704 and the transceiver 710. The processor 702 is configured to communicate one or more timing advance configurations and / or one or more cell configurations with the second wireless communication device via the transceiver 710. The processor 702 may be further configured to: select one or more reference cells for communicating in the mTRP communication scenario; and determine one or more reference timings and / or one or more timing advances based on the one or more reference cells.

[0116] Figure 8 800 according to some aspects of the present disclosure. Various aspects of the method 800 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for performing blocks. In one aspect, a UE (such as one of UEs 115, 515, and / or 700) may utilize one or more components (such as a processor 702, a memory 704, an mTRP priority module 708, a transceiver 710, a modem 712, an RF unit 714, and one or more antennas 716) to perform blocks of the method 800. The method 800 may be performed in accordance with Figure 5 In some aspects, the network entity may include the above with respect to Figure 1A and 1B The described aggregated BS and / or decomposed BS. The network entity may be configured as one of the multiple transmit-receive points (TRPs) in the mTRP communication scenario. Therefore, various aspects of method 800 may be described with reference to one or more TRPs and one or more UEs. As shown, method 800 includes a plurality of enumerated boxes, but various aspects of method 800 may include additional boxes before, after, and between these enumerated boxes. In some aspects, one or more of the enumerated boxes may be omitted or performed in a different order.

[0117] At box 810, the UE receives a first indication for scheduling or configuring a first UL communication associated with a first TCI state and a first TRP. In some aspects, the UE may receive the first indication from the first TRP. In other aspects, the UE may receive the first indication from a TRP different from the first TRP, such as a second TRP. In this regard, in some aspects, the first indication may include sDCI or mDCI. In some aspects, the first indication may include a DCI that includes a scheduling grant for the first UL communication. For example, the scheduling grant may schedule or indicate a PUSCH, a PUCCH, and / or a combination thereof. In other aspects, the first indication may include a control message or control signal, such as an RRC message or a MAC-CE. In some aspects, the control signal may configure a semi-static UL channel, such as a PUCCH or an SRS.

[0118] At box 820, the UE receives a second indication for scheduling or configuring a second UL communication associated with a second TCI state and a second TRP. In some aspects, the UE may receive the second indication from the second TRP. In other aspects, the UE may receive the second indication from a TRP different from the second TRP (such as the first TRP). In this regard, in some aspects, the second indication may include sDCI or mDCI. In some aspects, the second indication may include a DCI that includes a scheduling grant for the second UL communication. For example, the scheduling grant may schedule or indicate a PUSCH, a PUCCH, and / or a combination thereof. In other aspects, the first indication may include a control message or control signal, such as an RRC message or a MAC-CE. In some aspects, the control signal may configure a semi-static UL channel, such as a PUCCH or an SRS.

[0119] In some aspects, the second UL communication is scheduled to overlap the first UL communication at least partially in time. In some aspects, the second UL communication may completely overlap with the first UL communication. In other aspects, the second UL communication may only partially overlap with the first UL communication. In another aspect, the first UL communication and the second UL communication are scheduled for at least one of the same CC or the same frequency band. For example, the first UL communication may be scheduled or indicated for the same CC, wherein the CC is an inter-band CC. For example, the inter-band CC may occupy at least a portion of the first frequency band and at least a portion of the second frequency band different from the first frequency band. In some aspects, the first UL communication may be scheduled for a portion of the CC in the first frequency band, and the second UL communication may be scheduled for a portion of the CC in the second frequency band. In another example, the first UL communication may be scheduled or indicated for the first CC, and the second UL communication may be scheduled or indicated for the second CC different from the first CC. In some aspects, the first CC and the second CC may be in the same frequency band.

[0120] In another aspect, the first TCI state and the second TCI state may not be used by the UE for simultaneous UL transmission. For example, the first TCI state and the second TCI state may be different TCI states, and the UE may not use the first TCI state and the second TCI state to simultaneously transmit the first UL communication and the second UL communication in the indicated frequency resources. Thus, the method 800 may include the UE determining or selecting at least one of the first UL communication or the second UL communication based on the mTRP UL prioritization configuration.

[0121] At block 830, the UE sends a first UL communication based on the mTRP UL prioritization configuration. In some aspects, the UE may send the first UL communication to the first TRP. In some aspects, the UE selects and sends the first UL communication based on one or more of a channel type of the first UL communication, a type of information carried in the first UL communication, a time domain allocation for the first UL communication, a TCI state associated with the first UL communication, and / or a TRP associated with the first UL communication.

[0122] In this regard, in one aspect, the first UL communication is associated with a first UL channel type, and the second UL communication is associated with a second UL channel type that is different from the first UL channel type. In some aspects, the mTRP Ul prioritization configuration indicates that the first uplink channel type has a higher priority than the second uplink channel type. In some aspects, the mTRPUL prioritization configuration may specify PRACH as having a higher priority than PUCCH. In some aspects, the mTRP UL prioritization configuration may specify PUCCH as having a higher priority than PUSCH. In another aspect, the mTRP UL prioritization configuration may specify PUSCH as having a higher priority than SRS. In other aspects, the mTRP UL prioritization configuration may specify PUCCH as having a higher priority than PRACH. In other aspects, the mTRP UL prioritization configuration may specify PUSCH as having a higher priority than PUCCH.

[0123] In another aspect, the mTRP UL priority of the first UL communication and the second UL communication may be based on a combination of UL channel type and information carried in or associated with the first and second UL communications. In some aspects, the mTRP UL prioritization configuration may specify PRACH as having a higher priority than PUCCH carrying HARQ-ACK information, scheduling request (SR) and / or link recovery request (LRR) and / or PUSCH transmission carrying HARQ-ACK information. In some aspects, the mTRP UL prioritization configuration may specify PUCCH carrying HARQ-ACK information, SR and / or LRR and / or PUSCH transmission carrying HARQ-ACK information as having a higher priority than PUCCH transmission carrying channel state information (CSI) and / or PUSCH transmission carrying CSI. In another aspect, the mTRP UL prioritization configuration may specify PUCCH transmission carrying channel state information (CSI) and / or PUSCH transmission carrying CSI as having a higher priority than PUSCH transmission not including HARQ-ACK information or CSI. In another aspect, the mTRP UL prioritization configuration may designate a PUCCH transmission carrying channel state information (CSI) and / or a PUSCH transmission carrying CSI as having a higher priority than a PUSCH transmission on a Pcell for a type 2 random access procedure. In another aspect, the mTRP UL prioritization configuration may designate a PUSCH transmission on a Pcell for a type 2 random access procedure and / or a PUSCH transmission without HARQ-ACK information or CSI as having a higher priority than an SRS transmission. In some aspects, the mTRP UL prioritization configuration may designate a non-periodic SRS as having a higher priority than a semi-persistent and / or periodic SRS. In some aspects, the mTRP UL prioritization configuration may designate a non-periodic SRS as having a higher priority than a serving cell or than a PRACH transmission on a Pcell. However, in lieu of or in addition to the prioritization explicitly mentioned above, the present invention also contemplates other prioritizations. For example, in some aspects, the mTRP UL prioritization configuration may indicate that a PUSCH transmission carrying HARQ-ACK information or CSI has a higher priority than a PUCCH transmission with HARQ-ACK information. In another aspect, the mTRP UL prioritization configuration may indicate that aperiodic SRS has a higher priority than a PUSCH that does not include HARQ-ACK and / or CSI.

[0124] In another example, the mTRP UL prioritization configuration may cause the UE to assign priorities based on the TRP associated with the UL communication. For example, in some aspects, a first UL communication is associated with a first TRP and a second UL communication is associated with a second TRP. The TRP associated with each UL communication may be indicated based on a TCI state indicated in a scheduling DCI and / or a CORESET pool index associated with, indicated for, or configured for the UL communication. In some aspects, UL communications associated with a TCI state with a smaller ID or number may be prioritized by the UE for transmission.

[0125] In another aspect, the mTRP UL prioritization configuration may cause the UE to assign a priority based on the indication type of each of the first indication and the second indication. For example, the first indication may be associated with the first indication type, and the second indication may be associated with the second indication type. In one example, the first indication type may be a DCI that schedules a first UL communication, and the second indication type may be an RRC message or MAC-CE that configures and / or activates one or more opportunities for a UL channel associated with a second UL communication. In some aspects, the mTRP UL prioritization configuration may cause the UE to assign a higher priority to the first UL communication scheduled by the DCI. In other aspects, the mTRP UL prioritization configuration may assign a higher priority to the second UL communication configured by the RRC and / or the second UL communication activated by the MAC-CE. In some aspects, the mTRP UL prioritization configuration may cause the UE to assign a higher priority to the UL communication activated by the MAC-CE than to the UL communication configured by the RRC.

[0126] In another aspect, the mTRP UL prioritization configuration may cause the UE to assign priorities based on the time domain allocation for the first UL communication and the second UL communication. For example, in some aspects, the mTRP UL prioritization configuration may cause the UE to assign relative priorities based on the start symbol, end symbol and / or duration of the first UL communication and the second UL communication. For example, the mTRP indication may cause the UE to prioritize the first UL communication based on the first UL communication having an earlier start symbol than the second UL communication. In another aspect, the mTRP indication may cause the UE to prioritize the first UL communication based on the first UL communication having an earlier end symbol relative to the second UL communication. In another aspect, the mTRP indication may cause the UE to prioritize the first UL communication based on the first UL communication having a shorter duration or a longer duration relative to the second UL communication. In some aspects, the mTRP UL prioritization configuration may cause the UE to prioritize UL communications based on a combination of time domain allocation parameters. For example, if the first UL communication and the second UL communication are scheduled for the same start symbol, the UE may prioritize the UL communication with an earlier end symbol or a later end symbol. In another aspect, if the first UL communication and the second UL communication are associated with the same starting symbol, the UE may prioritize the UL communication having a longer duration or a shorter duration.

[0127] In some aspects, the mTRP UL prioritization configuration may enable the UE to prioritize UL communications based on a combination of the parameters indicated above. For example, the UE may first use the UL channel type to determine the priority, but if the UL channel type priorities are the same, then the TRP, TCI, indication type and / or time domain allocation may be considered. In another aspect, the UE may first use the indication type to determine the UL priority, but if the indication type priority is the same for both the first UL communication and the second UL communication, then the time domain allocation may be used.

[0128] In another aspect, the method 800 may also include the UE sending a second UL communication. In some aspects, the UE may send the second UL communication based on the same TCI state as the first UL communication. For example, the UE may use the first TCI state to send the second UL communication. In other aspects, the UE may use the second TCI state to send the second UL communication. The UE may use one or more of the above parameters or prioritization schemes (including indication type, UL channel type, time domain parameters, TRP and / or TCI state ID) to select a single TCI state for sending both the first UL communication and the second UL communication. In some aspects, different time domains and / or different frequency domain resources may be used for each configuration to perform the transmission of the first UL communication and the second UL communication. For example, the UE may use FDM or TDM to send the first UL communication and the second UL communication using the same TCI state. In some aspects, by selecting a single TCI state for two UL channels associated with the UL communication, the TCI state of the UL channel may be reset or updated.

[0129] In another aspect, instead of sending the first UL communication at block 830, the method 800 may include preventing sending either the first UL communication or the second UL communication based on the first UL communication conflicting with the second UL communication. In this regard, the UE may treat the conflict of UL communications that cannot be sent simultaneously in the mTRP communication scenario as an error condition.

[0130] Method 800 may include Figure 5 One or more steps, actions or other aspects illustrated and described above.

[0131] Exemplary Aspects of the Disclosure

[0132] Aspect 1. A wireless communication method performed by a user equipment (UE), the method comprising: receiving a first indication of a first uplink (UL) communication scheduled to be associated with a first transmit configuration indicator (TCI) state and a first transmit receive point (TRP); receiving a second indication of a second UL communication scheduled to be associated with a second TCI state and a second TRP, wherein the second UL communication is scheduled to at least partially overlap with the first UL communication in time, and wherein the first UL communication and the second UL communication are scheduled for at least one of the same component carrier (CC) or the same frequency band; and sending the first UL communication based on a multi-TRP (mTRP) UL prioritization configuration.

[0133] Aspect 2. A method according to Aspect 1, wherein: the first UL communication is associated with a first UL channel type; the second UL communication is associated with a second UL channel type different from the first UL channel type; and the mTRPUL prioritization configuration indicates that the first UL channel type has a higher priority than the second UL channel type.

[0134] Aspect 3. A method according to aspect 2, wherein: the first UL communication includes first information having a first information type; and the mTRP UL prioritization indicates that the first UL communication has a higher priority than the second UL communication based on the first UL channel type and the first information type.

[0135] Aspect 4. A method according to any one of Aspects 1 to 3, wherein: the mTRP UL prioritization configuration indicates that the first TRP has a higher priority than the second TRP.

[0136] Aspect 5. A method according to Aspect 4, wherein: the first TRP is associated with a first control resource set (CORESET) pool index or at least one of the first TCI state; the second TRP is associated with a second CORESET pool index or at least one of the second TCI state; and the mTRP UL prioritization configuration indicates that at least one of the first CORESET pool index or the first TCI state has a higher priority than at least one of the second CORESET pool index or the second TCI state.

[0137] Aspect 6. A method according to any one of Aspects 1 to 5, wherein: the first indication for scheduling the first UL communication includes downlink control information (DCI), the downlink control information (DCI) including a scheduling grant for the first UL communication; the second indication for scheduling the second UL communication includes at least one of a radio resource control (RRC) message or a medium access control element (MAC-CE) for scheduling the second UL communication; and the mTRP UL prioritization configuration indicates that the first indication has a higher priority than the second indication based on the first indication including the scheduling grant and the second indication including the at least one of the RRC message or the MAC-CE.

[0138] Aspect 7. A method according to any one of Aspects 1 to 6, wherein: the first UL communication is associated with a first time domain allocation; the second UL communication is associated with a second time domain allocation; and the mTRP UL prioritization configuration indicates that the first time domain allocation has a higher priority than the second time domain allocation.

[0139] Aspect 8. A method according to any one of Aspects 1 to 7, wherein: the sending of the first UL communication includes sending the first UL communication to the first TRP; and the method also includes: sending the second UL communication to the second TRP simultaneously with the first UL communication and based on the first TCI state.

[0140] Aspect 9. The method of aspect 8 further comprises selecting the first TCI state for the first UL communication and the second UL communication based on at least one of: a UL channel type associated with the first UL communication; a CORESET pool index associated with the first UL communication; or an indication type associated with the first UL communication. Information and signals may be represented using any of a variety of different techniques and technologies.

[0141] Aspect 10. A user equipment (UE), the user equipment (UE) comprising: a memory device; a transceiver; and a processor, the processor communicating with the memory device and the transceiver, wherein the UE is configured to perform the actions according to any one of aspects 1 to 9.

[0142] Aspect 11. A non-transitory computer readable medium having program code recorded thereon, wherein the program code comprises a program code executable by a processor of a user equipment (UE) to cause the UE to perform actions according to any one of aspects 1 to 9.

[0143] Aspect 10. A user equipment (UE), comprising means for performing actions according to any one of aspects 1 to 9.

[0144] For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0145] Aspects may utilize a general purpose processor, DSP, ASIC, 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 to implement or execute various illustrative blocks and modules described in conjunction with the disclosure herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).

[0146] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination thereof. The features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations. In addition, as used herein (including in the claims), "or" used in an item enumeration (e.g., followed by an item enumeration such as "at least one of" or "one or more of") indicates an inclusive enumeration, such that, for example, an enumeration of [at least one of A, B, or C] means: A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0147] As those skilled in the art will understand by now and depending on the specific application at hand, many modifications, substitutions and changes may be made to the materials, devices, configurations and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the specific aspects illustrated and described herein (as they are only some examples of the present disclosure), but should be fully equivalent to the attached claims and their functional equivalents.

Claims

1. A wireless communication method performed by a user equipment (UE), the method comprising: receiving a first indication scheduling a first uplink (UL) communication associated with a first transmit configuration indicator (TCI) state and a first transmit reception point (TRP); receiving a second indication of scheduling a second UL communication associated with a second TCI state and a second TRP, wherein the second UL communication is scheduled to at least partially overlap in time with the first UL communication, and wherein the first UL communication and the second UL communication are scheduled for at least one of a same component carrier (CC) or a same frequency band; and The first UL communication is sent based on a multi-TRP (mTRP) UL prioritization configuration.

2. The method according to claim 1, wherein: The first UL communication is associated with a first UL channel type; The second UL communication is associated with a second UL channel type different from the first UL channel type; and The mTRP UL prioritization configuration indicates that the first UL channel type has a higher priority than the second UL channel type.

3. The method according to claim 2, wherein: The first UL communication includes first information having a first information type; and The mTRP UL prioritization indicates that the first UL communication has a higher priority than the second UL communication based on the first UL channel type and the first information type.

4. The method according to claim 1, wherein: The mTRP UL prioritization configuration indicates that the first TRP has a higher priority than the second TRP.

5. The method according to claim 4, wherein: The first TRP is associated with at least one of a first control resource set (CORESET) pool index or the first TCI state; The second TRP is associated with at least one of a second CORESET pool index or the second TCI state; and The mTRP UL prioritization configuration indicates that at least one of the first CORESET pool index or the first TCI state has a higher priority than at least one of the second CORESET pool index or the second TCI state.

6. The method according to claim 1, wherein: The first indication scheduling the first UL communication comprises downlink control information (DCI), the downlink control information (DCI) comprising a scheduling grant for the first UL communication; The second indication to schedule the second UL communication comprises at least one of a radio resource control (RRC) message or a medium access control element (MAC-CE) to schedule the second UL communication; and The mTRP UL prioritization configuration indicates that the first indication has a higher priority than the second indication based on the first indication including the scheduling grant and the second indication including the at least one of the RRC message or the MAC-CE.

7. The method according to claim 1, wherein: The first UL communication is associated with a first time domain allocation; The second UL communication is associated with a second time domain allocation; and The mTRP UL prioritization configuration indicates that the first time domain allocation has a higher priority than the second time domain allocation.

8. The method of claim 1, wherein: The sending the first UL communication comprises sending the first UL communication to the first TRP; and The method further comprises: The second UL communication is sent to the second TRP simultaneously with the first UL communication and based on the first TCI state.

9. The method of claim 8, further comprising selecting the first TCI state for the first UL communication and the second UL communication based on at least one of: a UL channel type associated with the first UL communication; a CORESET pool index associated with the first UL communication; or An indication type associated with the first UL communication.

10. A user equipment (UE), the user equipment (UE) comprising: Memory devices; Transceiver; and a processor in communication with the memory device and the transceiver, wherein the UE is configured to: receiving a first indication scheduling a first uplink (UL) communication associated with a first transmit configuration indicator (TCI) state and a first transmit reception point (TRP); receiving a second indication of scheduling a second UL communication associated with a second TCI state and a second TRP, wherein the second UL communication is scheduled to at least partially overlap in time with the first UL communication, and wherein the first UL communication and the second UL communication are scheduled for at least one of a same component carrier (CC) or a same frequency band; and The first UL communication is sent based on a multi-TRP (mTRP) UL prioritization configuration.

11. The UE according to claim 10, wherein: The first UL communication is associated with a first UL channel type; The second UL communication is associated with a second UL channel type different from the first UL channel type; and The mTRP UL prioritization configuration indicates that the first UL channel type has a higher priority than the second UL channel type.

12. The UE according to claim 11, wherein: The first UL communication includes first information having a first information type; and The mTRP UL prioritization indicates that the first UL communication has a higher priority than the second UL communication based on the first UL channel type and the first information type.

13. The UE according to claim 10, wherein: The mTRP UL prioritization configuration indicates that the first TRP has a higher priority than the second TRP.

14. The UE according to claim 13, wherein: The first TRP is associated with at least one of a first control resource set (CORESET) pool index or the first TCI state; The second TRP is associated with at least one of a second CORESET pool index or the second TCI state; and The mTRP UL prioritization configuration indicates that at least one of the first CORESET pool index or the first TCI state has a higher priority than at least one of the second CORESET pool index or the second TCI state.

15. The UE according to claim 10, wherein: The first indication scheduling the first UL communication comprises downlink control information (DCI), the downlink control information (DCI) comprising a scheduling grant for the first UL communication; The second indication to schedule the second UL communication comprises at least one of a radio resource control (RRC) message or a medium access control element (MAC-CE) to schedule the second UL communication; and The mTRP UL prioritization configuration indicates that the first indication has a higher priority than the second indication based on the first indication including the scheduling grant and the second indication including the at least one of the RRC message or the MAC-CE.

16. The UE according to claim 10, wherein: The first UL communication is associated with a first time domain allocation; The second UL communication is associated with a second time domain allocation; and The mTRP UL prioritization configuration indicates that the first time domain allocation has a higher priority than the second time domain allocation.

17. The UE according to claim 10, wherein: The UE is configured to send the first UL communication to the first TRP; and The UE is further configured to: The second UL communication is sent to the second TRP simultaneously with the first UL communication and based on the first TCI state.

18. The UE of claim 17, wherein the UE is further configured to select the first TCI state for the first UL communication and the second UL communication based on at least one of: a UL channel type associated with the first UL communication; a CORESET pool index associated with the first UL communication; or An indication type associated with the first UL communication.

19. A non-transitory computer readable medium having program code recorded thereon, wherein the program code comprises instructions executable by a processor of a user equipment (UE) to cause the UE to: receiving a first indication scheduling a first uplink (UL) communication associated with a first transmit configuration indicator (TCI) state and a first transmit reception point (TRP); receiving a second indication of scheduling a second UL communication associated with a second TCI state and a second TRP, wherein the second UL communication is scheduled to at least partially overlap in time with the first UL communication, and wherein the first UL communication and the second UL communication are scheduled for at least one of a same component carrier (CC) or a same frequency band; and The first UL communication is sent based on a multi-TRP (mTRP) UL prioritization configuration.

20. The non-transitory computer readable medium of claim 19, wherein: The first UL communication is associated with a first UL channel type; The second UL communication is associated with a second UL channel type different from the first UL channel type; and The mTRP UL prioritization configuration indicates that the first UL channel type has a higher priority than the second UL channel type.

21. The non-transitory computer readable medium of claim 20, wherein: The first UL communication includes first information having a first information type; and The mTRP UL prioritization indicates that the first UL communication has a higher priority than the second UL communication based on the first UL channel type and the first information type.

22. The non-transitory computer readable medium of claim 19, wherein: The mTRP UL prioritization configuration indicates that the first TRP has a higher priority than the second TRP.

23. The non-transitory computer readable medium of claim 22, wherein: The first TRP is associated with at least one of a first control resource set (CORESET) pool index or the first TCI state; The second TRP is associated with at least one of a second CORESET pool index or the second TCI state; and The mTRP UL prioritization configuration indicates that at least one of the first CORESET pool index or the first TCI state has a higher priority than at least one of the second CORESET pool index or the second TCI state.

24. The non-transitory computer readable medium of claim 19, wherein: The first indication scheduling the first UL communication comprises downlink control information (DCI), the downlink control information (DCI) comprising a scheduling grant for the first UL communication; The second indication to schedule the second UL communication comprises at least one of a radio resource control (RRC) message or a medium access control element (MAC-CE) to schedule the second UL communication; and The mTRP UL prioritization configuration indicates that the first indication has a higher priority than the second indication based on the first indication including the scheduling grant and the second indication including the at least one of the RRC message or the MAC-CE.

25. The non-transitory computer readable medium of claim 19, wherein: The first UL communication is associated with a first time domain allocation; The second UL communication is associated with a second time domain allocation; and The mTRP UL prioritization configuration indicates that the first time domain allocation has a higher priority than the second time domain allocation.

26. The non-transitory computer readable medium of claim 19, wherein: The program code includes instructions for causing the UE to send the first UL communication to the first TRP; and The program code also includes instructions for causing the UE to perform the following operations: The second UL communication is sent to the second TRP simultaneously with the first UL communication and based on the first TCI state.

27. The non-transitory computer readable medium of claim 26, wherein the program code further comprises instructions for causing the UE to select the first TCI state for the first UL communication and the second UL communication based on at least one of: a UL channel type associated with the first UL communication; a CORESET pool index associated with the first UL communication; or An indication type associated with the first UL communication.

28. A user equipment (UE), the user equipment (UE) comprising: means for receiving a first indication for scheduling a first uplink (UL) communication associated with a first transmit configuration indicator (TCI) state and a first transmit reception point (TRP); means for receiving a second indication of scheduling a second UL communication associated with a second TCI state and a second TRP, wherein the second UL communication is scheduled to at least partially overlap in time with the first UL communication, and wherein the first UL communication and the second UL communication are scheduled for at least one of a same component carrier (CC) or a same frequency band; and Means for sending the first UL communication based on a multi-TRP (mTRP) UL prioritization configuration.

29. The UE according to claim 28, wherein: The first UL communication is associated with a first UL channel type; The second UL communication is associated with a second UL channel type different from the first UL channel type; and The mTRP UL prioritization configuration indicates that the first UL channel type has a higher priority than the second UL channel type.

30. The UE according to claim 28, wherein: The first indication scheduling the first UL communication comprises downlink control information (DCI), the downlink control information (DCI) comprising a scheduling grant for the first UL communication; The second indication to schedule the second UL communication comprises at least one of a radio resource control (RRC) message or a medium access control element (MAC-CE) to schedule the second UL communication; and The mTRP UL prioritization configuration indicates that the first indication has a higher priority than the second indication based on the first indication including the scheduling grant and the second indication including the at least one of the RRC message or the MAC-CE.

Images