Scheduling conflict handling with multiple transmit-receive points

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a first scheduling message from a first transmit receive point (TRP) and a second scheduling message from a second TRP. The UE may detect a scheduling conflict based at least in part on a first scheduled communication of the first scheduling message and a second scheduled communication of the second scheduling message overlapping in time. The UE may selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This Patent Application claims priority to U.S. Patent Application No. 18 / 189,817, filed March 24, 2023, entitled “SCHEDULING COLLISION HANDLING WITH MULTIPLE TRANSMIT RECEIVE POINTS,” assigned to the assignee of the present application. The disclosure of the priority application is considered part of the disclosure of this Patent Application and is hereby incorporated by reference into this Patent Application. TECHNICAL FIELD

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatuses for handling collisions with multiple transmit receive points. BACKGROUND

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0005] A wireless network can include one or more network nodes that support communications for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE can communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to communications from network nodes to UEs, and “uplink” (or “UL”) refers to communications from UEs to network nodes. Some wireless networks can support device-to-device communications, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among others).

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different UEs to communicate on a municipal, national, regional, and / or global level. New Radio (NR), which can be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and support beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. SUMMARY

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method can include receiving a first scheduling message from a first transmission reception point (TRP) and a second scheduling message from a second TRP. The method can include detecting a conflict based at least in part on a first scheduled communication of the first scheduling message and a second scheduled communication of the second scheduling message overlapping in time. The method can include selectively transmitting one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the conflict.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE can include a memory and one or more processors coupled to the memory. The one or more processors can be configured to receive a first scheduling message from a first transmission reception point (TRP) and a second scheduling message from a second TRP. The one or more processors can be configured to detect a conflict based at least in part on a first scheduled communication of the first scheduling message and a second scheduled communication of the second scheduling message overlapping in time. The one or more processors can be configured to selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the conflict.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, can cause the UE to receive a first scheduling message from a first TRP and a second scheduling message from a second TRP. The set of instructions, when executed by the one or more processors of the UE, can cause the UE to detect a collision based at least in part on a first scheduled communication of the first scheduling message and a second scheduled communication of the second scheduling message overlapping in time. The set of instructions, when executed by the one or more processors of the UE, can cause the UE to selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the collision.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for receiving a first scheduling message from a first TRP and a second scheduling message from a second TRP. The apparatus can include means for detecting a collision based at least in part on a first scheduled communication of the first scheduling message and a second scheduled communication of the second scheduling message overlapping in time. The apparatus can include means for selectively transmitting one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the collision.

[0011] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, UE, base station, network entity, network node, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

[0012] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be readily utilized as bases for modifying or designing other for carrying the same purposes thereof. Such equivalent constructions are not to depart from the scope of the appended claims. The present disclosure also specifically describes features, the phenomenon of which is disclosed, in terms of their organization, method of operation, and use of associated advantages. Each of the drawings in the accompanying drawings is provided for illustrative and descriptive purposes, and is not a limitation on the definition of the claims.

[0013] While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. Techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating described aspects and features can include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is intended that aspects described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying sizes, shapes, and constitution. BRIEF DESCRIPTION OF DRAWINGS

[0014] To more fully understand the aspects of the present disclosure, a more

[0015] Figure 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0016] Figure 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0017] Figure 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

[0018] Figure 4 illustrates an example logical architecture of a distributed random access network, in accordance with the present disclosure.

[0019] Figure 5 is a diagram illustrating an example of multi-transmission reception point communication, in accordance with the present disclosure.

[0020] Figure 6FIG. 1 is a diagram illustrating an example of a wireless communication system in accordance with the present disclosure.

[0021] Figure 7 FIG. 2 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

[0022] Figure 8 FIG. 3 is a diagram of an example apparatus for wireless communication in accordance with the present disclosure. DETAILED DESCRIPTION

[0023] A user equipment (UE) can communicate with multiple transmission reception points (TRPs) controlled by a network entity. The multiple TRPs can coordinate to avoid conflicts in scheduling communications and providing grants to the UE. In one scenario, the multiple TRPs can dynamically coordinate use of resources to avoid conflicts. The multiple TRPs can use fast backhaul between the TRPs. In another scenario, the multiple TRPs can use conservative scheduling with slow coordination. For example, if the UE cannot simultaneously receive multiple unicast physical downlink shared channel (PDSCH) communications, the TRPs coordinate to communicate with the UE using time division multiplexing (TDM). One technique is for a first TRP to use even time slots and a second TRP to use odd time slots. This technique would work at the expense of throughput because if the first TRP does not use even time slots, the second TRP cannot use even time slots and time slots are wasted. If many time slots are wasted, throughput decreases and latency increases. In either scenario, each TRP has a responsibility to avoid scheduling conflicts in which one scheduled communication would overlap in time (e.g., same time slot) with another scheduled communication.

[0024] According to various aspects described herein, the TRPs can not follow requirements for inter-TRP coordination (e.g., orthogonality) and can allow for scheduling conflicts at the UE. A scheduling conflict can occur if a scheduled communication from a first TRP overlaps in time with a scheduled communication from a second TRP. A scheduling conflict can occur if a service operation exceeds the UE’s capability to transmit or receive the scheduled communications. In some aspects, the TRPs can schedule communications that overlap in time and the UE can detect and handle the scheduling conflict. The UE can detect the scheduling conflict based at least in part on scheduling messages (e.g., downlink control information (DCI) in a physical downlink control channel message (PDCCH), radio resource control (RRC) configuration) from the multiple TRPs. The UE can handle the scheduling conflict by adjusting the communications. This can include dropping one or both scheduled communications or degrading one or both scheduled communications. By accounting for and handling scheduling conflicts from multiple TRPs, the UE can not be prevented from using resources reserved by a second TRP for a first TRP. More time slots are used and fewer signaling resources are wasted. This improves throughput for the multiple TRPs and reduces latency.

[0025] Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art will appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using, in addition to or in place of the aspects set forth herein, other structures, functionalities, or structures and functions disclosed with respect to the various aspects of the present disclosure. It will be understood that any aspect of the disclosure disclosed herein can be embodied by one or more elements of a claim.

[0026] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms, among other examples (collectively referred to as “elements”). These elements can be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0027] While aspects can be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

[0028] Figure 1is a diagram illustrating an example of a wireless network 100, in accordance with this disclosure. The wireless network 100 can be or include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution, LTE) network, among other examples. The wireless network 100 can include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one UE 120, or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network nodes 110 are network nodes that communicate with the UEs 120. As illustrated, the network nodes 110 can include one or more network nodes. For example, the network nodes 110 can be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network nodes 110 can be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network nodes 110 are configured to utilize a protocol stack that is physically or logically distributed across two or more nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0029] In some examples, the network nodes 110 are or include network nodes (such as RUs) that communicate with UEs 120 via radio access links. In some examples, the network nodes 110 are or include network nodes (such as DUs) that communicate with other network nodes 110 via a front-haul link or a mid-haul link. In some examples, the network nodes 110 are or include network nodes (such as CUs) that communicate with other network nodes 110 via a mid-haul link or with a core network via a backhaul link. In some examples, the network nodes 110 (such as aggregated network nodes 110 or disaggregated network nodes 110) can include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network nodes 110 can include, for example, an NR base station, an LTE base station, a NodeB, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a TRP, a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 can interconnect with each other and / or to one or more other network nodes 110 in the wireless network 100 using any suitable transport network, such as a direct physical connection, an air interface, or a virtual network. The transport network can include one or more wired or wireless links between the network nodes 110.

[0030] In some examples, a network node 110 can provide communication coverage for a particular geographic area. In Third Generation Partnership Project (3GPP), the term "cell" can refer to a coverage area of a network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used. A network node 110 can be a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell can cover a relatively large geographic area (e.g., several kilometers in radius) and can allow unrestricted access by UEs 120 with service subscriptions. A pico cell can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UEs 120 with service subscriptions. A femto cell can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UEs 120 associated with the femto cell, such as UEs 120 in a closed subscriber group (CSG). A network node 110 for a macro cell can be referred to as a macro network node. A network node 110 for a pico cell can be referred to as a pico network node. A network node 110 for a femto cell can be referred to as a femto network node or a home network node. In Figure 1 In the illustrated example, network node 110a can be a macro network node for a macro cell 102a, network node 110b can be a pico network node for a pico cell 102b, and network node 110c can be a femto network node for a femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, cells can not necessarily be stationary, and the geographic area of the cells can move according to the location of a mobile network node 110 (e.g., a mobile network node).

[0031] In some aspects, the term “base station” or “network node” can refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a “base station” or “network node” can refer to a CU, a DU, a RU, a near-real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term “base station” or “network node” can refer to one device configured to perform one or more functions, such as those described herein in connection with network node 110. In some aspects, the term “base station” or “network node” can refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which can be located in the same geographic location or different geographic locations) can be configured to perform at least a portion of a function, or to repeat at least a portion of the function, and the term “base station” or “network node” can refer to any one or more of these different devices. In some aspects, the term “base station” or “network node” can refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term “base station” or “network node” can refer to one of a base station function and not another base station function. In this way, a single device can include more than one base station.

[0032] Wireless network 100 can include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110). A relay station can be a UE 120 that can relay transmissions for other UEs 120. In Figure 1 In the example shown in FIG. 1, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d in order to facilitate communication between network node 110a and UE 120d. A network node 110 that relays

[0033] Wireless network 100 can be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 can have different transmit power levels, different coverage areas, and / or different impacts on interference in wireless network 100. For example, macro network nodes can have a high transmit power level (e.g., 5 to 40 watts), whereas pico network nodes, femto network nodes, and relay network nodes can have a lower transmit power level (e.g., 0.1 to 2 watts).

[0034] A network controller 130 can couple to or communicate with a set of network nodes 110 and can provide coordination and control for the network nodes 110. The network controller 130 can communicate with the network nodes 110 via a backhaul communication link or a metro communication link. The network nodes 110 can also communicate with one another directly via wireless backhaul communication links or indirect via wired backhaul communication links. In some aspects, the network controller 130 can be a CU or a core network device, or can include a CU or a core network device.

[0035] The UEs 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. A UE 120 can include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. A UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device that is configured to communicate via a wireless or wired medium.

[0036] Some UEs 120 can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and / or eMTC UEs can include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, that can communicate with a network node, another device (e.g., remote device), or some other entity. A

[0037] Generally, any number of wireless networks 100 can be deployed in a given geographic area. Each wireless network 100 can support a particular RAT and can operate on one or more frequencies. A RAT can be referred to as a radio technology, an air interface, etc. A frequency can be referred to as a carrier, a frequency channel, etc. Each frequency channel can support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0038] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with one another). For example, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110. Communication between vehicles, also referred to as V2V communication, can be performed using a vehicle-to-everything (V2X) protocol. For example, V2X communication can include V2V communication, Vehicle-to-Infrastructure (V2I) communication, and / or Vehicle-to-Network (V2N) communication. In some examples, a V2X protocol can be used for safety messages transmitted by UEs 120. In some examples, V2X communication can be performed using a PC5 interface.

[0039] Devices of wireless network 100 can use the electromagnetic spectrum for communications. The electromagnetic spectrum can be subdivided, according to frequency or wavelength, into various classes, bands, channels, etc. For example, devices of wireless network 100 can operate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often (interchangeably) referred to as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0040] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Bands that fall within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. Moreover, higher bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-l (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0041] With the above examples in mind, it should be understood that, unless specifically stated otherwise, if the term “sub-6 GHz” or the like is used herein, the term can refer to frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. Also, it should be understood that, unless specifically stated otherwise, if the term “millimeter wave” or the like is used herein, the term can refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a, or FR4-l, and / or FR5, or can be within the EHF band. It is contemplated that frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-l, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0042] In some aspects, a UE (e.g., UE 120) can include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 can receive a first scheduling message from a first TRP and a second scheduling message from a second TRP. The communications manager 140 can detect a scheduling conflict based at least in part on a first scheduled communication of the first scheduling message and a second scheduled communication of the second scheduling message overlapping in time. The communications manager 140 can selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict. Additionally, or alternatively, the communications manager 140 can perform one or more other operations described herein.

[0043] As indicated above, Figure 1 are provided as examples. Other examples can differ from what is described with respect to Figure 1 the examples described with respect to

[0044] Figure 2is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100, in accordance with the present disclosure. The network node 110 can be equipped with a set of antennas 234a through 234t, such as T antennas (T > 1). The UE 120 can be equipped with a set of antennas 252a through 252r, such as R antennas (R > 1). The network node 110 of example 200 includes one or more radio front end components, such as antennas 234 and modem 232. In some examples, the network node 110 can include an interface, communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 can not include radio frequency components that facilitate direct communication with UEs 120, such as one or more CUs or one or more DUs.

[0045] At the network node 110, a transmit processor 220 can receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 can select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 can process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCSs selected for the UE 120 and can provide data symbols for the UE 120. The transmit processor 220 can process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 can generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of corresponding modems 232 (e.g., T modems), shown as modems 232a through 232t. Each output symbol stream can be provided to a modulator component (shown as MOD) of the modems 232, for example. Each modem 232 can use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a respective modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or upconvert) to obtain a downlink signal. The modems 232a through 232t can transmit a set of downlink signals (e.g., T downlink signals) via a set of corresponding antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.

[0046] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) can receive the downlink signals from network nodes 110 and / or other network nodes 110 and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 can use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 can use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from modems 254, can perform MIMO detection on the received symbols if applicable, and can provide detected symbols. A receive processor 258 can process (e.g., demodulate and decode) the detected symbols, can provide decoded data for UE 120 to a data sink 260, and can provide decoded control information and system information to a controller / processor 280. The term “controller / processor” can refer to one or more controllers, one or more processors, or combinations thereof. A channel processor can determine reference signal received power (RSRP) parameters, receive signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or CQI parameters, among other examples. In some examples, one or more components of UE 120 can be included in a housing 284.

[0047] Network controller 130 can include communication unit 294, controller / processor 290, and memory 292. Network controller 130 can include, for example, one or more devices in a core network. Network controller 130 can communicate with network node 110 via communication unit 294.

[0048] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) can include or be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array can include one or more antenna elements (within a single housing or multiple housings), a set of co-planar antenna elements, a set of non-co-planar antenna elements, and / or one or more antenna elements coupled to one or more transmit and / or receive components (such as, for example, one or more components of a modem 254 and / or a modem 254 in FIG. 2). Figure 2 ​

[0049] On the uplink, at UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, modems 254 of UE 120 can include modulators and demodulators. In some examples, UE 120 includes a transceiver. The transceiver can include any combination of antenna 252, modems 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (for example, with reference to Figures 2 to 8 ) and can operate in a similar manner.

[0050] At network node 110, the uplink signals from UE 120 and / or other UEs can be received by antennas 234, processed by modems 232 (e.g., demodulator components (shown as DEMOD) of modems 232), detected by MIMO detector 236 if applicable, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 can include communication unit 244 and can communicate with network controller 130 via communication unit 244. Network node 110 can include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modems 232 of network node 110 can include modulators and demodulators. In some examples, network node 110 includes a transceiver. The transceiver can include any combination of antenna 234, modems 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (for example, with reference to Figures 2 to 8 ) and can operate in a similar manner.

[0051] As described in more detail elsewhere in this document, the controller / processor of the network entity (e.g., controller / processor 240 of network node 110), the controller / processor 280 of UE 120, and / or Figure 2 Any other component may execute one or more techniques associated with handling scheduling conflicts using multiple TRPs. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 7 The operation of process 700 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions may cause the one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation and / or interpretation). Figure 7 The operation of process 700 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.

[0052] In some aspects, the UE (e.g., UE 120) includes components for receiving a first scheduling message from a first TRP and a second scheduling message from a second TRP; components for detecting scheduling conflicts based at least in part on the temporal overlap of the communication of the first scheduling message and the communication of the second scheduling message; and / or components for selectively transmitting one or more of the first scheduling communication or the second scheduling communication based at least in part on the detection of a scheduling conflict. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TXMIMO processor 266, a controller / processor 280, or a memory 282.

[0053] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0054] As indicated above, Figure 2 are provided as examples. Other examples can differ from what is described with respect to Figure 2 the described examples.

[0055] Deployments of communication systems, such as 5G NR systems, can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, network entity, mobility element of a network, RAN node, core network node, network element, base station, or network equipment can be implemented in an aggregated architecture or a disaggregated architecture. For example, a base station, such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, and the like, or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a disaggregated base station. A “network entity” or “network node” can refer to a disaggregated base station or one or more units of a disaggregated base station, such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof.

[0056] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A disaggregated base station (e.g., a disaggregated network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some examples, a CU can be implemented within a network node, and one or more DUs can be co-located with the CU or, alternatively, can be geographically or virtually spread throughout one or more other network nodes. The DUs can be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs can also be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

[0057] Base station type operations or network designs can take into account the aggregated nature of base station functionality. For example, a disaggregated base station can be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)) to facilitate scaling of a communication system by separating base station functionality into one or more units that can be deployed individually. A disaggregated base station can include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0058] Figure 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 can include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 can communicate with one or more DUs 330 via respective fronthaul links, such as over an Fl interface. Each of the DUs 330 can communicate with one or more RUs 340 via respective front-haul links. Each of the RUs 340 can communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 can be served by multiple RUs 340 simultaneously.

[0059] Each of the units, including the CU 310, the DUs 330, the RUs 340, as well as the near-RT RIC 325, the non-RT RIC 315, and the SMO framework 305, can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to one or more communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission media. In some examples, each of the units can include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium, and a wireless interface, which can include a receiver, a transmitter, or a transceiver such as a RF transceiver, configured to receive or transmit signals to one or more of the other units over a wireless transmission medium, or both.

[0060] In some aspects, the CU 310 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bi-directionally with the CU-CP units via an interface, such as an El interface. The CU 310 can be implemented to communicate with the DUs 330 as needed for network control and signaling.

[0061] Each DU 330 can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 can 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, at least in part according to a functional split, such as a functional split defined by 3GPP. In some aspects, the one or more high PHY layers can be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 can also host one or more low PHY layers, such as implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which can also be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0062] Each RU 340 can implement lower layer functionality. In some deployments, the RUs 340 controlled by the DUs 330 can correspond to logical nodes that host RF processing functions or low PHY layer functions based on a functional split (e.g., a functional split defined by 3GPP), such as a lower layer functional split, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, among other examples. In such an architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 340 can be controlled by the corresponding DUs 330. In some scenarios, this configuration can enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0063] The SMO framework 305 can 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 305 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform, such as an Open Cloud (O-Cloud) platform 390, to perform network element lifecycle management, such as instantiating virtualized network elements, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, the CU 310, the DUs 330, the RUs 340, the non-RT RIC 315, and the near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of a 4G RAN, such as an Open eNB (O-eNB) 311, via an Ol interface. Additionally, in some implementations, the SMO framework 305 can directly communicate with each of the one or more RUs 340 via a respective Ol interface. The SMO framework 305 can also include the non-RT RIC 315 configured to support functionality of the SMO framework 305.

[0064] The non-RT RIC 315 can be configured to include logical 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 steering of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to, or communicate with, the near-RT RIC 325, such as via an Al interface. The near-RT RIC 325 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions via an interface, such as via an E2 interface, that connects one or more CUs 310, one or more DUs 330, or both, and an O-eNB with the near-RT RIC 325.

[0065] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received at the SMO framework 305 or the non-RT RIC 315 from non-network data sources or from network functions. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305, such as reconfiguration via an Ol interface, or through creation of RAN management policies, such as Al interface policies.

[0066] As indicated above, Figure 3 are provided as examples. Other examples can differ from what is described with respect to Figure 3 the examples described with respect to

[0067] Figure 4 An example logical architecture of a distributed RAN 400 according to the present disclosure is illustrated.

[0068] The 5G access node 405 can include an access node controller 410. The access node controller 410 can be a CU of the distributed RAN 400. In some aspects, a backhaul interface to a 5G core network 415 can terminate at the access node controller 410. The 5G core network 415 can include a 5G control plane component 420 and a 5G user plane component 425 (e.g., a 5G gateway), and a backhaul interface for one or both of the 5G control plane and the 5G user plane can terminate at the access node controller 410. Additionally, or alternatively, a backhaul interface to one or more neighbor access nodes 430 (e.g., another 5G access node 405 and / or an LTE access node) can terminate at the access node controller 410.

[0069] The access node controller 410 can include one or more TRPs 435 and / or can communicate with one or more TRPs (e.g., via an Fl control (Fl-C) interface and / or an Fl user (Fl-U) interface). The TRPs 435 can include a DU and / or a RU of the distributed RAN 400. In some aspects, the TRPs 435 can correspond to the TRPs 435 described above in connection with Figure 1 the network node 110 described above. For instance, different TRPs 435 can be included in different network nodes 110. Additionally, or alternatively, multiple TRPs 435 can be included in a single network node 110. In some aspects, a network node 110 can include a CU (e.g., the access node controller 410) and / or one or more DUs (e.g., one or more TRPs 435). In some cases, a TRP 435 can be referred to as a cell, a panel, an antenna array, or an array.

[0070] The TRPs 435 can be connected to a single access node controller 410 or multiple access node controllers 410. In some aspects, there can be a dynamic configuration of split logical functions within the architecture of the distributed RAN 400, referred to elsewhere herein as functional split. For example, the PDCP layer, the RLC layer, and / or the MAC layer can be configured to be terminated in the access node controller 410 or the TRP 435.

[0071] In some aspects, multiple TRPs 435 can transmit communications (e.g., a same communication or different communications) in a same transmission time interval (TTI) (e.g., a slot, a mini-slot, a subframe, or a symbol) or different TTIs using different quasi co-location (QCL) relationships (e.g., different spatial parameters, different transmission configuration indicator (TCI) states, different precoding parameters, and / or different beamforming parameters). In some aspects, a TCI state can be used to indicate one or more QCL relationships. The TRPs 435 can be configured to provide service to a UE 120 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs 435).

[0072] As indicated above, Figure 4 are provided as examples. Other examples can differ from what is described with respect to Figure 4 the examples described.

[0073] Figure 5 is a diagram illustrating an example 500 of multi-TRP communication (sometimes referred to as multi-panel communication) in accordance with the present disclosure. As Figure 5 shown, multiple TRPs can communicate with a same UE 120. The TRPs can correspond to the TRPs 435 described above in connection with Figure 4 the network node 110 described above.

[0074] A number of TRPs (shown as TRP 505 and TRP 510) can communicate with the same UE 120 in a coordinated manner (e.g., using coordinated multipoint transmission) to improve reliability and / or increase throughput. The TRPs can coordinate such communication via an interface between the TRPs (e.g., a backhaul interface and / or an access node controller 410). This interface can have a smaller latency and / or a higher capacity when the TRPs are co-located at the same network node 110 (e.g., when the TRPs are different antenna arrays or panels of the same network node 110), and the interface can have a larger latency and / or a lower capacity when the TRPs are at different network nodes 110 (as compared to being co-located). Different TRPs can communicate with the UE 120 using different QCL relationships (e.g., different TCI states), different DMRS ports, and / or different layers (e.g., of a multi-layer communication).

[0075] In a first multi-TRP transmission mode (e.g., Mode 1), a single PDCCH can be used to schedule a single PDSCH for a downlink data communication. In this case, multiple TRPs (e.g., TRP 505 and TRP 510) can transmit communications to the UE 120 on the same PDSCH. For example, a single codeword with different spatial layers for different TRPs can be used to transmit the communications (e.g., where one codeword is mapped to a first set of layers transmitted by the TRP 505 and mapped to a second set of layers transmitted by the TRP 510). As another example, multiple codewords can be used to transmit the communications, where different codewords are transmitted by different TRPs (e.g., using different sets of layers). In either case, different TRPs can use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, the TRP 505 can use a first QCL relationship or a first TCI state for a first set of DMRS ports corresponding to a first set of layers, and the TRP 510 can use a second (different) QCL relationship or a second (different) TCI state for a second (different) set of DMRS ports corresponding to a second (different) set of layers. In some aspects, a TCI state in DCI (e.g., transmitted on a PDCCH, such as DCI format 1 0 or DCI format 1 1) can indicate the first QCL relationship (e.g., by indicating the first TCI state) and the second QCL relationship (e.g., by indicating the second TCI state). The first TCI state and the second TCI state can be indicated using a TCI field in the DCI. Generally, in this multi-TRP transmission mode (e.g., Mode 1), the TCI field can indicate a single TCI state (for single-TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed herein).

[0076] In a second multi-TRP transmission mode (e.g., Mode 2), multiple PDCCHs can be used to schedule downlink data communications for multiple corresponding PDSCHs (e.g., one PDCCH for each PDSCH). In this case, a first PDCCH can schedule a first codeword to be transmitted by TRP 505, and a second PDCCH can schedule a second codeword to be transmitted by TRP 510. Further, a first DCI (e.g., transmitted by TRP 505) can schedule a first PDSCH communication associated with a first set of DMRS ports having a first QCL relationship (e.g., indicated by a first TCI state) for TRP 505, and a second DCI (e.g., transmitted by second TRP 510) can schedule a second PDSCH communication associated with a second set of DMRS ports having a second QCL relationship (e.g., indicated by a second TCI state) for TRP 510. In this case, the DCI (e.g., of DCI format 1 0 or DCI format 1 1) can indicate a corresponding TCI state for the TRP corresponding to the DCI. The TCI field of the DCI indicates the corresponding TCI state (e.g., the TCI field of the first DCI indicates the first TCI state and the TCI field of the second DCI indicates the second TCI state).

[0077] The multiple TRPs can coordinate to avoid conflicts in scheduling communications and providing grants to the UE. In one scenario, the multiple TRPs can dynamically coordinate the use of resources to avoid conflicts. The multiple TRPs can use fast backhaul between the TRPs. In another scenario, the multiple TRPs can use conservative scheduling with slow coordination (RRC level). For example, if the UE cannot receive multiple unicast PDSCH communications simultaneously, the TRPs coordinate to communicate with the UE using TDM. One technique is for TRP 505 to use even time slots and for TRP 510 to use odd time slots. This technique would work, but at the expense of throughput, because if TRP 505 does not use even time slots, TRP 510 cannot use even time slots, and time slots are wasted. If many time slots are wasted, the throughput decreases and the latency increases. In either scenario, it is the responsibility of each TRP to avoid scheduling conflicts, i.e., when one scheduled communication would overlap in time (e.g., same time slot) with another scheduled communication.

[0078] As indicated above, Figure 5 are provided as examples. Other examples can differ from what is described Figure 5 with respect to the examples described in this regard.

[0079] Figure 6 is a diagram illustrating an example 600 associated with detecting and handling scheduling conflicts, in accordance with the present disclosure. As Figure 6As shown, a first TRP 605 (e.g., TRP 435, TRP 505) and a second TRP 610 (e.g., TRP 435, TRP 510) of a network entity (e.g., network node 110) can communicate with a UE 620 (e.g., UE 120) in a wireless communication network (e.g., wireless network 100).

[0080] According to various aspects described herein, a TRP can not follow requirements for inter-TRP coordination (e.g., orthogonality) and can account for scheduling conflicts at the UE. A scheduling conflict can occur if a scheduled communication from a first TRP overlaps in time with a scheduled communication from a second TRP. A scheduling conflict can occur if a service operation exceeds the UE’s capability to transmit or receive the scheduled communications. In some aspects, a TRP can schedule communications that overlap in time, and the UE can detect and handle the conflict. The UE can detect a scheduling conflict based at least in part on scheduling messages (e.g., DCI in PDCCH communications) from multiple TRPs. The UE can handle the scheduling conflict by adjusting the communications. This can include dropping or degrading the scheduled communications. By accounting for and handling scheduling conflicts, the UE can not be prevented from using resources reserved by a second TRP for a first TRP. More time slots are used, and fewer signaling resources are wasted. This improves throughput for multiple TRPs and reduces latency.

[0081] As shown by reference number 625, TRP 605 can transmit a first scheduling message, and TRP 610 can transmit a second scheduling message. The first scheduling message can include DCI in a physical uplink control channel (PUCCH) communication or an RRC message scheduling a configured grant (CG) occasion, a semi-persistent scheduling (SPS) occasion, or a periodic resource. The second scheduling message can include DCI in a PUCCH communication or an RRC message scheduling a CG occasion, an SPS occasion, or a periodic resource. UE 620 can receive the first scheduling message and the second scheduling message. UE 620 can be configured to expect that scheduling conflicts can occur between multiple TRPs, such as between TRP 605 and TRP 610.

[0082] In some aspects, the first scheduling message can include a first DCI (e.g., in a first PDCCH communication), and the second scheduling message can include a second DCI (e.g., in a second PDCCH communication). In some aspects, the first scheduling message can include a first RRC message, and the second scheduling message can include a second RRC message. The first RRC message can configure the UE 620 with a first configuration, such as a CG configuration or an SPS configuration. The second RRC message can configure the UE 620 with a second configuration, such as a CG configuration or an SPS configuration. In some aspects, the UE 620 can receive a DCI from a TRP that overrides a previous RRC configuration for the TRP. The scheduling message can indicate an uplink grant and / or a downlink grant.

[0083] As shown by reference number 630, the UE 620 can detect a scheduling conflict of the first scheduled communication of the first scheduling message and the second scheduled communication of the second scheduling message. A scheduling conflict can occur if the first scheduled communication and the second scheduled communication overlap in time, such as in the same slot. The UE 620 can detect the scheduling conflict by comparing the scheduling messages. For example, by comparing the timing (e.g., the time resources of the grant) of the first scheduled communication indicated by the first DCI to the timing of the second scheduled communication indicated by the second DCI, the UE 620 can detect the scheduling conflict from the DCIs.

[0084] In some aspects, the UE 620 can further detect the scheduling conflict based at least in part on a capability of the UE to handle messages that overlap in time. For example, the UE 620 can receive two scheduling messages from the TRP 605 and the TRP 610 for scheduled communications that overlap in time but can be frequency division multiplexed (FDMed). However, if the scheduled communications have a total rank of 4 and the UE 620 has a capability of a maximum rank of 3, the UE 620 cannot handle both scheduled communications and there will be a scheduling conflict.

[0085] An example of a scheduling conflict that exceeds a UE capability can include simultaneously receiving two unicast PDSCH communications. As a scheduling event, the UE 620 can receive a DCI from a TRP that schedules two time overlapping PDSCH communications. The UE 620 can not have a capability to receive two partially overlapping unicast PDSCH communications. Another example of a scheduling conflict that exceeds a UE capability can include simultaneously transmitting simultaneous PUCCH communications. As a scheduling event, the UE 620 can receive a DCI from a TRP that schedules two time overlapping PUCCH communications. The scheduling message can or can not conflict with the scheduled communications (e.g., the DCI).

[0086] In some aspects, one of the scheduling messages can be an RRC message, and the other scheduling message can be a DCI. For the mix of scheduling message types, there are different scenarios. In a first scenario, the TRPs can be coordinated such that there will be no scheduling conflict. That is, one TRP communicates to the other TRP about its downlink or uplink transmissions for the UE's RRC configuration, such that the other TRP will not make a dynamic scheduling decision that causes a conflict. From the perspective of the UE 620, any scheduling conflict is handled as an error case. In a second scenario, the UE 620 can treat the RRC configured downlink or uplink transmissions the same as the dynamically granted downlink or uplink transmissions. That is, the TRPs can independently configure the RRC downlink or uplink resources, and rely on conflict detection by the UE 620 to resolve any scheduling conflicts. Given that both are RRC configured, the conflict information is known in advance. However, since the TRPs can transmit dynamic grants to replace the configured grants, a potential conflict from the RRC configuration can not conflict later. Thus, the conflict detection is still dynamic. In a third scenario, there can be a reason for the dynamic grant since there is coordination between the TRPs for the RRC configured resources, and one TRP still transmits a dynamic downlink or uplink grant that causes a scheduling conflict. The reason can be that the dynamic grant is for high priority traffic. The UE 620 can allow the dynamic granted communication to take priority and drop the RRC configured scheduled communication.

[0087] In some aspects, both of the scheduling messages can be RRC messages. When the scheduling messages are RRC messages, there are different scenarios. In a first scenario, the TRPs can be coordinated such that there will be no conflict between the two scheduled communications that are scheduled as part of the RRC configuration. That is, the TRPs communicate with each other when configuring the resources (e.g., schedule the communications such that scheduling conflicts from the RRC configured resources are not allowed). From the perspective of the UE 620, a scheduling conflict will be handled as an error case. In a second scenario, the RRC scheduling messages can be treated the same as the DCI scheduling messages. That is, the TRPs can independently configure the resources, and rely on conflict detection at the UE 620 to resolve the scheduling conflicts. Given that the communications with both TRPs are RRC configured, the conflict information is known in advance. However, since the TRPs can transmit dynamic grants to replace the configured grants, a conflict from the RRC configuration can not conflict later. Thus, the conflict detection is still dynamic.

[0088] The UE 620 can handle the scheduling conflict. As shown by reference number 635, the UE 620 can selectively transmit the first scheduled communication or the second scheduled communication based at least in part on the detection of the scheduling conflict. In some aspects, if there is a scheduling conflict and the UE is not capable of handling both scheduled communications, the UE 620 can transmit either the first scheduled communication or the second scheduled communication (not both scheduled communications). That is, the UE 620 can drop one or both of the scheduled communications. Dropping a scheduled communication can include refraining from transmitting the scheduled communication. In some aspects, the UE 620 can drop a scheduled communication with a lower priority after comparing priorities (e.g., TRP priorities). The TRP priority can be determined based at least in part on the TRP indicator. The TRP priority can be fixed (e.g., TRP 605 has a higher priority than TRP 610) or time-varying (e.g., TRP 605 has priority in odd time slots and TRP 610 has priority in even time slots).

[0089] In some aspects, the UE 620 can drop a scheduled communication based at least in part on a configured rule. For example, the UE 620 can drop a scheduled communication with a lower traffic priority after comparing traffic priorities. The UE 620 can drop a scheduled communication with a lower spectral efficiency (e.g., MCS, rank) after comparing spectral efficiencies. The UE 620 can drop a scheduled communication with a more stringent delay budget after comparing delay budgets. This can include prioritizing a scheduled communication with more retransmissions. The UE 620 can drop a scheduled communication for a TRP with a lower throughput after comparing TRP throughputs. This can include observing the load of the TRPs, where a TRP with a lower spectral efficiency can be less loaded such that more resources can be scheduled. In some aspects, the UE 620 can drop one or both scheduled communications. For example, when overlapping PDSCH communications are not supported, the UE 620 can drop both PDSCH communications if there is at least a partial overlap.

[0090] In some aspects, the UE 620 can degrade the first scheduled communication and / or the second scheduled communication. Degradation can include modulating or demodulating portions of the scheduled communications that do not overlap with the other scheduled communication, and not modulating or demodulating portions of the scheduled communications that overlap with the other scheduled communication. For example, in the case of a spatial layer collision (where both scheduled communications use the same DMRS port), the UE 620 can demodulate the non-colliding spatial layers and collect log likelihood ratios (LLRs). In some aspects, degrading the scheduled communications can include changing a physical uplink shared channel (PUSCH) grant for the scheduled communications to a PUCCH grant. For example, if the UE 620 is not able to transmit a PUCCH communication and a PUSCH communication, but there is a first PUCCH grant and a second PUCCH grant, the UE 620 can upgrade one of the PUCCH grants to a PUSCH grant. The UE 620 can then degrade back to the two PUCCH grants (e.g., ignore the uplink grant or operate as if the uplink grant was not decoded).

[0091] After degradation, the transmission / reception can fall back in terms of UE capability. The dropping method can be considered a special case of degradation, where one or both scheduled communications are degraded to cancellation. Degradation can have different interpretations for different collisions. For example, if the UE 620 is not able to receive overlapping scheduled communications, the UE 620 can degrade to receive each scheduled communication only on the non-overlapping portions. Thus, the non-overlapping portions are not contaminated by the other scheduled communication.

[0092] In some aspects, the UE 620 can be configured with multiple candidate resources for uplink communications, rather than having a single resource assigned and expecting the UE 620 to detect a scheduling collision and drop a scheduled communication. The TRPs 605 and / or 610 can schedule multiple resources at a time. The UE 620 can selectively transmit the first scheduled first communication and / or the second scheduled communication by selecting an additional transmission resource and transmitting the first scheduled first communication and the second scheduled communication using the additional transmission resource. The additional transmission resource can be shared by multiple UEs, each of which can use the additional transmission resource due to a scheduling collision. The sharing of resources allows for more efficient use of resources.

[0093] As indicated above, Figure 6 are provided as examples. Other examples can differ from what is described with respect to Figure 6 the examples described with respect to

[0094] Figure 7is a diagram illustrating an example process 700 performed, for example, by a UE, in accordance with aspects of the present disclosure. Example process 700 is an example where the UE (e.g., UE 120, UE 620) performs operations associated with handling scheduling conflicts with multiple TRPs.

[0095] As further shown, in some aspects, process 700 can include detecting a scheduling conflict based at least in part on the first scheduled communication of the first scheduling message and the second scheduled communication of the second scheduling message overlapping in time (block 720). For example, the UE (e.g., using reception component 802 and / or communication manager 806, depicted in FIG. 8) can detect a scheduling conflict based at least in part on the first scheduled communication of the first scheduling message and the second scheduled communication of the second scheduling message overlapping in time, as described above. Figure 7 As further shown, in some aspects, process 700 can include selectively transmitting one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict (block 730). For example, the UE (e.g., using transmission component 804 and / or communication manager 806, depicted in FIG. 8) can selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict, as described above. Figure 8 As further shown, in some aspects, process 700 can include detecting a scheduling conflict based at least in part on the first scheduled communication of the first scheduling message and the second scheduled communication of the second scheduling message overlapping in time (block 720). For example, the UE (e.g., using reception component 802 and / or communication manager 806, depicted in FIG. 8) can detect a scheduling conflict based at least in part on the first scheduled communication of the first scheduling message and the second scheduled communication of the second scheduling message overlapping in time, as described above.

[0096] As further shown, in some aspects, process 700 can include detecting a scheduling conflict based at least in part on the first scheduled communication of the first scheduling message and the second scheduled communication of the second scheduling message overlapping in time (block 720). For example, the UE (e.g., using reception component 802 and / or communication manager 806, depicted in FIG. 8) can detect a scheduling conflict based at least in part on the first scheduled communication of the first scheduling message and the second scheduled communication of the second scheduling message overlapping in time, as described above. Figure 7 As further shown, in some aspects, process 700 can include selectively transmitting one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict (block 730). For example, the UE (e.g., using transmission component 804 and / or communication manager 806, depicted in FIG. 8) can selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict, as described above. Figure 8 As further shown, in some aspects, process 700 can include selectively transmitting one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict (block 730). For example, the UE (e.g., using transmission component 804 and / or communication manager 806, depicted in FIG. 8) can selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict, as described above.

[0097] As further shown, in some aspects, process 700 can include selectively transmitting one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict (block 730). For example, the UE (e.g., using transmission component 804 and / or communication manager 806, depicted in FIG. 8) can selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict, as described above. Figure 7 As further shown, in some aspects, process 700 can include selectively transmitting one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict (block 730). For example, the UE (e.g., using transmission component 804 and / or communication manager 806, depicted in FIG. 8) can selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict, as described above. Figure 8 As further shown, in some aspects, process 700 can include selectively transmitting one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict (block 730). For example, the UE (e.g., using transmission component 804 and / or communication manager 806, depicted in FIG. 8) can selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict, as described above.

[0098] Process 700 can include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0099] In a first aspect, the UE is configured to expect that a scheduling conflict can occur between multiple TRPs.

[0100] In a second aspect, alone or in combination with the first aspect, detecting the scheduling conflict includes detecting the scheduling conflict further based at least in part on a capability of the UE to handle messages overlapping in time.

[0101] In a third aspect, alone or in combination with one or more of the first and second aspects, the first scheduling message includes a first DCI and the second scheduling message includes a second DCI.

[0102] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first scheduling message includes a first RRC message and the second scheduling message includes a DCI.

[0103] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the DCI overrides an earlier RRC message from the second TRP that schedules the communication.

[0104] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, selectively transmitting one or more of the first scheduled communication or the second scheduled communication includes transmitting the second scheduled communication instead of the first scheduled communication based at least in part on a priority of the second scheduled communication.

[0105] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the first scheduling message includes a first RRC message and the second scheduling message includes a second RRC message.

[0106] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, selectively transmitting one or more of the first scheduled communication or the second scheduled communication includes dropping or degrading one or more of the first scheduled communication or the second scheduled communication.

[0107] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, dropping or degrading one or more of the first scheduled communication or the second scheduled communication includes dropping one or more of the first scheduled communication or the second scheduled communication.

[0108] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, dropping one or more of the first scheduled communication or the second scheduled communication includes dropping the first scheduled communication or the second scheduled communication based at least in part on a comparison of a priority of the first TRP and a priority of the second TRP.

[0109] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, dropping one or more of the first scheduled communication or the second scheduled communication includes dropping the first scheduled communication or the second scheduled communication based at least in part on a rule for selecting a communication for transmission.

[0110] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, dropping one or more of the first scheduled communication or the second scheduled communication includes dropping the first scheduled communication or the second scheduled communication based at least in part on a comparison of a priority of the first scheduled communication and a priority of the second scheduled communication.

[0111] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, dropping one or more of the first scheduled communication or the second scheduled communication includes dropping the first scheduled communication or the second scheduled communication based at least in part on a comparison of a spectral efficiency of the first scheduled communication and a spectral efficiency of the second scheduled communication.

[0112] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, dropping one or more of the first scheduled communication or the second scheduled communication includes dropping the first scheduled communication or the second scheduled communication based at least in part on a comparison of a delay budget for the first scheduled communication and a delay budget for the second scheduled communication.

[0113] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, dropping one or more of the first scheduled communication or the second scheduled communication includes dropping the first scheduled communication or the second scheduled communication based at least in part on a comparison of a throughput of the first TRP and a throughput of the second TRP.

[0114] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, dropping one or more of the first scheduled communication or the second scheduled communication includes dropping both the first scheduled communication and the second scheduled communication.

[0115] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, dropping or degrading one or more of the first scheduled communication or the second scheduled communication includes degrading one or more of the first scheduled communication or the second scheduled communication.

[0116] In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, degrading one or more of the first scheduled communication or the second scheduled communication includes demodulating non-overlapping portions of one or more of the first scheduled communication or the second scheduled communication and not demodulating overlapping portions.

[0117] In the nineteenth aspect, degrading one or more of the communications of the first schedule or the communications of the second schedule, either alone or in combination with one or more of the first to eighteenth aspects, includes changing the first schedule message or the second schedule message from a PUSCH grant to a PUCCH grant.

[0118] In the twentieth aspect, selectively transmitting one or more of the first scheduled communications or the second scheduled communications, either alone or in combination with one or more of the first to nineteenth aspects, includes: selecting an additional transmission resource, and using the additional transmission resource to transmit the first scheduled communications and the second scheduled communications.

[0119] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes, boxes, or boxes in a different manner. Alternatively, two or more boxes in the process 700 may be executed in parallel.

[0120] Figure 8 This is a diagram illustrating an example device 800 for wireless communication according to the present disclosure. Device 800 may be a UE (e.g., UE 120, UE 620), or a UE may include device 800. In some aspects, device 800 includes a receiving component 802, a transmitting component 804, and / or a communication manager 806 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 806 is combined with... Figure 1 The described communication manager 140. As shown, device 800 can communicate with another device 808 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 802 and transmitting component 804.

[0121] In some respects, device 800 can be configured to perform the functions described herein. Figures 1 to 6 One or more operations described herein. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 7 The process is 700. In some respects, Figure 8 The illustrated device 800 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 8 One or more components shown can be combined Figure 2implementation within one or more components described. Additionally or alternatively, one or more components of a set of components might be implemented at least partially as software stored in a memory and executed by a controller or a processor. For example, a component (or a portion of it) can be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0122] The reception component 802 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 808. The reception component 802 can provide received communications to one or more other components of the apparatus 800. In some aspects, the reception component 802 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to one or more other components of the apparatus 800. In some aspects, the reception component 802 can include one or more antennas, a modem, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described. Figure 2 The described one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or a combination thereof, of the UE.

[0123] The transmission component 804 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 808. In some aspects, one or more other components of the apparatus 800 can generate communications and can provide the generated communications to the transmission component 804 for transmission to the apparatus 808. In some aspects, the transmission component 804 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 808. In some aspects, the transmission component 804 can include one or more antennas, a modem, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described. In some aspects, the transmission component 804 can be co-located with the reception component 802 in a transceiver. Figure 2 The described one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or a combination thereof, of the UE.

[0124] The communication manager 806 can support the operations of the reception component 802 and / or the transmission component 804. For example, the communication manager 806 can receive information associated with configuring reception of communications by the reception component 802 and / or transmission of communications by the transmission component 804. Additionally or alternatively, the communication manager 806 can generate control information and / or provide control information to the reception component 802 and / or the transmission component 804 to control the reception and / or transmission of communications.

[0125] The reception component 802 can receive a first scheduling message from a first TRP and a second scheduling message from a second TRP. The communication manager 806 can detect a scheduling conflict based at least in part on a first scheduled communication of the first scheduling message and a second scheduled communication of the second scheduling message overlapping in time. The transmission component 804 can selectively transmit one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict.

[0126] Figure 8 The number and arrangement of components shown is provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown. Figure 8 than those shown. Additionally or alternatively, some of the example components described here can be implemented as part of a single component, and / or some components can be implemented as multiple components. Figure 8 Two or more of the components shown can be implemented within a single component, or Figure 8 A single component shown can be implemented as multiple, distributed components. Additionally or alternatively, Figure 8 A set of one or more components shown can be implemented to perform one or more functions described as being performed by another set of one or more components. Figure 8 one or more functions described as being performed by another set of components.

[0127] An overview of some aspects of the present disclosure is provided below:

[0128] Aspect 1 : A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a first scheduling message from a first transmission reception point (TRP) and a second scheduling message from a second TRP; detecting a scheduling conflict based at least in part on a first scheduled communication of the first scheduling message and a second scheduled communication of the second scheduling message overlapping in time; and selectively transmitting one or more of the first scheduled communication or the second scheduled communication based at least in part on detecting the scheduling conflict.

[0129] Aspect 2: The method of Aspect 1, wherein the UE is configured to expect that scheduling conflicts can occur between multiple TRPs.

[0130] Aspect 3: The method of any of Aspects 1-2, wherein detecting the scheduling conflict comprises: detecting the scheduling conflict further based at least in part on a capability of the UE to handle messages overlapping in time.

[0131] Aspect 4: The method of any of Aspects 1-3, wherein the first scheduling message comprises first downlink control information (DCI) and the second scheduling message comprises second DCI.

[0132] Aspect 5: The method of any of aspects 1-3, wherein the first scheduling message comprises a first radio resource control (RRC) message and the second scheduling message comprises downlink control information (DCI).

[0133] Aspect 6: The method of aspect 5, wherein the DCI overrides an earlier RRC message from the second TRP that schedules a communication.

[0134] Aspect 7: The method of aspect 5, wherein selectively transmitting the one or more of the first scheduled communication or the second scheduled communication comprises transmitting the second scheduled communication instead of the first scheduled communication based at least in part on a priority of the second scheduled communication.

[0135] Aspect 8: The method of any of aspects 1-3, wherein the first scheduling message comprises a first radio resource control (RRC) message and the second scheduling message comprises a second RRC message.

[0136] Aspect 9: The method of any of aspects 1-8, wherein selectively transmitting the one or more of the first scheduled communication or the second scheduled communication comprises dropping or degrading one or more of the first scheduled communication or the second scheduled communication.

[0137] Aspect 10: The method of aspect 9, wherein dropping or degrading one or more of the first scheduled communication or the second scheduled communication comprises dropping one or more of the first scheduled communication or the second scheduled communication.

[0138] Aspect 11: The method of aspect 10, wherein dropping one or more of the first scheduled communication or the second scheduled communication comprises dropping the first scheduled communication or the second scheduled communication based at least in part on a comparison of a priority of the first TRP and a priority of the second TRP.

[0139] Aspect 12: The method of aspect 10, wherein dropping one or more of the first scheduled communication or the second scheduled communication comprises dropping the first scheduled communication or the second scheduled communication based at least in part on a rule for selecting a communication for transmission.

[0140] Aspect 13: The method of aspect 10, wherein dropping one or more of the first scheduled communication or the second scheduled communication comprises dropping the first scheduled communication or the second scheduled communication based at least in part on a comparison of a priority of the first scheduled communication and a priority of the second scheduled communication.

[0141] Aspect 14: The method of aspect 10, wherein dropping one or more of the first scheduled communication or the second scheduled communication comprises dropping the first scheduled communication or the second scheduled communication based at least in part on a comparison of a spectral efficiency of the first scheduled communication and a spectral efficiency of the second scheduled communication.

[0142] Aspect 15: The method of aspect 10, wherein dropping one or more of the first scheduled communication or the second scheduled communication comprises dropping the first scheduled communication or the second scheduled communication based at least in part on a comparison of a latency budget for the first scheduled communication and a latency budget for the second scheduled communication.

[0143] Aspect 16: The method of aspect 10, wherein dropping one or more of the first scheduled communication or the second scheduled communication comprises dropping the first scheduled communication or the second scheduled communication based at least in part on a comparison of a throughput of the first TRP and a throughput of the second TRP.

[0144] Aspect 17: The method of aspect 10, wherein dropping one or more of the first scheduled communication or the second scheduled communication comprises dropping both the first scheduled communication and the second scheduled communication.

[0145] Aspect 18: The method of aspect 9, wherein dropping or degrading one or more of the first scheduled communication or the second scheduled communication comprises degrading one or more of the first scheduled communication or the second scheduled communication.

[0146] Aspect 19: The method of aspect 18, wherein degrading one or more of the first scheduled communication or the second scheduled communication comprises demodulating non-overlapping portions of one or more of the first scheduled communication or the second scheduled communication and not demodulating overlapping portions.

[0147] Aspect 20: The method of aspect 18, wherein degrading one or more of the first scheduled communication or the second scheduled communication comprises changing the first scheduling message or the second scheduling message from a physical uplink shared channel grant to a physical uplink control channel grant.

[0148] Aspect 21 : The method of any one of aspects 1-20, wherein selectively transmitting one or more of the first scheduled communication or the second scheduled communication comprises: selecting an additional transmission resource; and transmitting the first scheduled communication and the second scheduled communication using the additional transmission resource.

[0149] Aspect 22: An apparatus for wireless communication at a device, comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of aspects 1-21.

[0150] Aspect 23: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-21.

[0151] Aspect 24: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 1-21.

[0152] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-21.

[0153] Aspect 26: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 1-21.

[0154] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations are possible according to the disclosure above, or in light of the practicing of the aspects.

[0155] As used herein, the term “component” is intended to be broadly construed as hardware and / or a combination of hardware and software. “Software” shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein can be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — because software and hardware can be designed to implement the systems and / or methods, based on the description herein, without departing from the scope of the various aspects.

[0156] As used herein, depending on the context, “satisfies a threshold” can refer to a value that is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.

[0157] Although specific combinations of features are set forth in the claims and / or disclosed herein, those combinations are not intended to limit the disclosure of various aspects. Many of the features can be combined in ways not specifically recited in the claims and / or disclosed herein. The disclosure of various aspects includes each and every combination of the features described herein. As used herein, the phrase “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of items from among a, b, and c (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c), and is intended to cover any combination of multiple identical elements.

[0158] No element, act or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and can be used interchangeably with “one or more.” Furthermore, as used herein, the term “set” and “group” are intended to include one or more items, and can be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having” or “has / have” or any variant thereof are intended to be open-ended terms that do not limit the items to which they are applied to the items that they actually modify. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and can be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’).

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and One or more processors, coupled to the memory, are configured to: Receive a first scheduling message from a first transmit-receive point (TRP) and a second scheduling message from a second TRP; Scheduling conflicts are detected at least in part based on the temporal overlap between the communication of the first scheduler in the first scheduling message and the communication of the second scheduler in the second scheduling message; as well as The communication of the first schedule or the communication of the second schedule may be selectively sent, at least in part, based on the detection of the scheduling conflict.

2. The UE of claim 1, wherein the UE is configured to anticipate scheduling conflicts that may occur among multiple TRPs.

3. The UE of claim 1, wherein, in order to detect the scheduling conflict, the one or more processors are configured to further detect the scheduling conflict based at least in part on the UE's ability to handle time-overlapping messages.

4. The UE according to claim 1, wherein the first scheduling message includes first downlink control information (DCI), and the second scheduling message includes a second DCI.

5. The UE according to claim 1, wherein the first scheduling message includes a first radio resource control (RRC) message, and the second scheduling message includes downlink control information (DCI).

6. The UE of claim 5, wherein the DCI covers an earlier RRC message from the second TRP that scheduled the communication.

7. The UE of claim 5, wherein, in order to selectively transmit one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to transmit the second scheduled communication instead of the first scheduled communication at least in part based on the priority of the second scheduled communication.

8. The UE according to claim 1, wherein the first scheduling message includes a first radio resource control (RRC) message, and the second scheduling message includes a second RRC message.

9. The UE of claim 1, wherein, in order to selectively transmit one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to: discard one or more of the first scheduled communication or the second scheduled communication or degrade one or more of the first scheduled communication or the second scheduled communication.

10. The UE of claim 9, wherein, in order to discard one or more of the first scheduled communication or the second scheduled communication or to degrade one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to: discard one or more of the first scheduled communication or the second scheduled communication.

11. The UE of claim 10, wherein, in order to discard one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to discard the first scheduled communication or the second scheduled communication at least in part based on a comparison of the priority of the first TRP and the priority of the second TRP.

12. The UE of claim 10, wherein, in order to discard one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to discard the first scheduled communication or the second scheduled communication at least in part based on a rule for selecting the communication to be transmitted.

13. The UE of claim 10, wherein, in order to discard one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to discard the first scheduled communication or the second scheduled communication at least in part based on a comparison of the priority of the first scheduled communication and the priority of the second scheduled communication.

14. The UE of claim 10, wherein, in order to discard one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to discard the first scheduled communication or the second scheduled communication at least in part based on a comparison of the spectral efficiency of the first scheduled communication and the spectral efficiency of the second scheduled communication.

15. The UE of claim 10, wherein, in order to discard one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to discard the first scheduled communication or the second scheduled communication at least in part based on a comparison of the delay budget for the first scheduled communication and the delay budget for the second scheduled communication.

16. The UE of claim 10, wherein, in order to discard one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to discard the first scheduled communication or the second scheduled communication at least in part based on a comparison of the throughput of the first TRP and the throughput of the second TRP.

17. The UE of claim 10, wherein, in order to discard one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to discard both the first scheduled communication and the second scheduled communication.

18. The UE of claim 9, wherein, in order to discard one or more of the first scheduled communication or the second scheduled communication or to degrade one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to: degrade one or more of the first scheduled communication or the second scheduled communication.

19. The UE of claim 18, wherein, in order to degrade one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to: demodulate the non-overlapping portions of one or more of the first scheduled communication or the second scheduled communication, and not demodulate the overlapping portions.

20. The UE of claim 18, wherein, in order to degrade one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to: change the first scheduled message or the second scheduled message from a physical uplink shared channel grant to a physical uplink control channel grant.

21. The UE of claim 1, wherein, in order to selectively transmit one or more of the first scheduled communication or the second scheduled communication, the one or more processors are configured to: Select additional send resources; and The additional transmission resources are used to transmit the communication of the first schedule and the communication of the second schedule.

22. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive a first scheduling message from a first transmit-receive point (TRP) and a second scheduling message from a second TRP; Scheduling conflicts are detected at least in part based on the temporal overlap between the communication of the first scheduling in the first scheduling message and the communication of the second scheduling in the second scheduling message; as well as The communication of the first schedule or the communication of the second schedule may be selectively sent, at least in part, based on the detection of the scheduling conflict.

23. The method of claim 22, wherein selectively transmitting one or more of the first scheduled communication or the second scheduled communication comprises: The communication of the second schedule is sent at least in part based on the priority of the communication of the second schedule, rather than the communication of the first schedule.

24. The method of claim 22, wherein selectively transmitting one or more of the first scheduled communication or the second scheduled communication comprises: Discard one or more of the first scheduled communication or the second scheduled communication, or downgrade one or more of the first scheduled communication or the second scheduled communication.

25. The method of claim 24, wherein discarding one or more of the first scheduled communication or the second scheduled communication, or degrading one or more of the first scheduled communication or the second scheduled communication, comprises: Discard one or more of the communications from the first schedule or the second schedule.

26. The method of claim 25, wherein discarding one or more of the communications of the first scheduled communication or the communications of the second scheduled communication comprises: The communication of the first scheduler or the communication of the second scheduler is discarded at least in part based on the comparison result of the priority of the first TRP and the priority of the second TRP.

27. The method of claim 25, wherein discarding one or more of the communications of the first scheduled communication or the communications of the second scheduled communication comprises: The communication of the first schedule or the communication of the second schedule is discarded, at least in part, based on the rules used to select the communication to be sent.

28. The method of claim 24, wherein discarding one or more of the first scheduled communication or the second scheduled communication, or degrading one or more of the first scheduled communication or the second scheduled communication, comprises: Degrade one or more of the communications of the first scheduler or the communications of the second scheduler.

29. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions, which, when executed by one or more processors of a user equipment (UE), cause the UE to: Receive a first scheduling message from a first transmit-receive point (TRP) and a second scheduling message from a second TRP; Scheduling conflicts are detected at least in part based on the temporal overlap between the communication of the first scheduling in the first scheduling message and the communication of the second scheduling in the second scheduling message; as well as The communication of the first schedule or the communication of the second schedule may be selectively sent, at least in part, based on the detection of the scheduling conflict.

30. An apparatus for wireless communication, the apparatus comprising: A component for receiving a first scheduling message from a first transmit / receive point (TRP) and a second scheduling message from a second TRP; A component for detecting scheduling conflicts by at least partially overlapping communication between a first scheduler based on the first scheduling message and a second scheduler based on the second scheduling message in time; and Components for selectively sending one or more of the communications of the first schedule or the communications of the second schedule, at least in part based on the detection of the scheduling conflict.

Images