Inter-gnb CLI mitigation based on detection or sensing

Abstract

The present disclosure provides apparatus, methods, and computer program products for CLI mitigation. An example method may include receiving scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a second network entity. The example method may also include performing one or more actions based on the sensing operation for the one or more UL transmissions.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 815,899, filed on July 28, 2022, entitled “DETECTION OR SENSING-BASED INTER-GNB CLI MITIGATION,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems with cross-link interference (CLI) mitigation. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a first network entity. The memory and the at least one processor coupled to the memory may be configured to perform a sensing operation for the one or more UL transmissions. The memory and the at least one processor coupled to the memory may be configured to send a result of the sensing operation to a second network entity. The memory and the at least one processor coupled to the memory may be configured to receive scheduling information for one or more UL transmissions associated with the UE and the network entity. The memory and the at least one processor coupled to the memory may be configured to perform a sensing operation for the one or more UL transmissions. The memory and the at least one processor coupled to the memory may be configured to send a result of the sensing operation to the network entity.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a second network entity via backhaul signaling or over-the-air (OTA) signaling. The memory and the at least one processor coupled to the memory may be configured to perform one or more actions based on sensing operations for the one or more UL transmissions. The memory and the at least one processor coupled to the memory may be configured to receive scheduling information for DL ​​transmissions associated with one or more UEs. The memory and the at least one processor coupled to the memory may be configured to perform one or more actions based on sensing operations for the one or more UL transmissions based on the scheduling information, and the DL transmission overlaps with the one or more UL transmissions in timing based on dynamic time division duplexing (TDD) or full duplexing.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 is a diagram illustrating an example full-duplex at a network entity.

[0017] Figure 5 is a diagram illustrating an example sub-band full-duplex.

[0018] Figure 6 is a diagram illustrating an example CLI.

[0019] Figure 7 is a diagram illustrating an example CLI.

[0020] Figure 8 is a diagram illustrating example communications between network entities and a UE.

[0021] Fig. 9 is a diagram illustrating example signaling between two network entities.

[0022] Fig.10 is a diagram illustrating example sensing-based CLI mitigation between network entities.

[0023] Fig.11 is a diagram illustrating example sensing-based CLI mitigation between network entities.

[0024] Fig.12 is a diagram illustrating example sensing-based CLI mitigation between network entities.

[0025] Fig.13 is a diagram illustrating example sensing-based CLI mitigation between network entities.

[0026] Fig.14 is a diagram illustrating example sensing-based CLI mitigation between network entities.

[0027] Fig.15is a flow chart of a method of wireless communication.

[0028] Fig.16 is a flow chart of a method of wireless communication.

[0029] Fig.17 is a flow chart of a method of wireless communication.

[0030] Fig.18 is a flow chart of a method of wireless communication.

[0031] Fig.19 is a flow chart of a method of wireless communication.

[0032] Fig. 20 are diagrams illustrating examples of hardware implementations of example devices and / or network entities.

[0033] Fig.21 is a diagram illustrating an example of a hardware implementation of an example network entity.

[0034] Fig. 22 is a diagram illustrating example sensing-based CLI mitigation between network entities.

[0035] Fig.23 is a diagram illustrating example sensing-based CLI mitigation between network entities. DETAILED DESCRIPTION

[0036] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring such concepts.

[0037] Several aspects of telecommunication systems are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0038] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0039] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0040] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

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

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

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

[0044] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

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

[0046] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may 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 unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

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

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

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

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

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

[0052] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to YxMHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to YMHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0053] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0054] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0055] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, 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). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0056] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0057] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0058] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the optimal receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0059] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU.

[0060] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0061] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term "UE" may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0062] Reference again Figure 1 In some aspects, the UE 104 may include a sensing component 198. The sensing component 198 may be configured to receive scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a first network entity. The sensing component 198 may be configured to perform sensing operations for the one or more UL transmissions. The sensing component 198 may be configured to send a result of the sensing operation to a second network entity. The sensing component 198 may be configured to receive scheduling information for one or more UL transmissions associated with the UE and the network entity. The sensing component 198 may be configured to perform sensing operations for the one or more UL transmissions. The sensing component 198 may be configured to send a result of the sensing operation to the network entity.

[0063] In certain aspects, the base station 102 may include a sensing component 199. The sensing component 199 may be configured to receive scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a second network entity via backhaul signaling or over-the-air (OTA) signaling. The sensing component 199 may be configured to perform one or more actions based on sensing operations for the one or more UL transmissions. The sensing component 199 may be configured to receive scheduling information for DL ​​transmissions associated with one or more UEs. The sensing component 199 may be configured to perform one or more actions based on sensing operations for one or more UL transmissions based on the scheduling information, the DL transmissions overlapping in timing with the one or more UL transmissions based on dynamic TDD or full duplex.

[0064] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0065] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. For another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0066] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0067] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2 to 61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling).

[0068] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of equal size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0069]

[0070] Table 1: Parameter set, SCS and CP

[0071] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0072] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0073] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0074] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

[0075] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb teeth. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0076] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may be used to carry, among other things, a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0077] Figure 3370 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0078] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0079] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to a controller / processor 359, which implements layer 3 and layer 2 functionality.

[0080] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0081] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0082] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0083] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0084] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0085] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The sensing component 198 is used to perform various aspects.

[0086] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The sensing component 199 is used to perform various aspects.

[0087] In some wireless communication systems, full-duplex (FD) capability (supporting simultaneous UL or DL ​​transmission) may be present at a base station, a UE, or both a base station and a UE. For example, at the UE, an UL transmission may be sent from a first panel of the UE, while a simultaneous DL reception may be received at a second panel of the UE. The first panel and the second panel may be different panels of an antenna on the UE. In another example, at the base station, an UL reception may be received from a first panel of the base station, while a simultaneous DL transmission may be sent at a second panel of the base station. The first panel and the second panel may be different panels of an antenna on the base station. By supporting FD, the latency of communication may potentially be reduced. For example, it is possible for a UE to receive a DL signal in a time slot assigned to UL, which may achieve latency savings. In addition, by supporting FD, the spectrum efficiency of each cell and each UE may be improved because resource utilization on the spectrum may be more efficient.

[0088] Subband (SB) non-overlapping full duplex and dynamic / flexible time division duplex (TDD) can be used in wireless communication systems to improve spectrum efficiency and throughput by dynamically changing the UL or DL ​​transmission direction. However, inter-network entity and inter-UE CLI may occur, which may be intra-subband CLI or inter-subband CLI. A victim UE or a victim network entity may receive a transmission from an aggressor UE or an aggressor network entity that is not targeted at the victim. For example, CLI may occur when the UL / DL symbol from the aggressor collides with the UL / DL symbol of the victim.

[0089] Figure 4 4 is a diagram illustrating an example full-duplex at a network entity. Figure 4As illustrated, at the network entity 410, due to the simultaneous Tx and Rx operations, there may be self-interference between Tx and Rx at the network entity 410. Similarly, at the network entity 402, the network entity 402 may communicate with the UE 404 and the UE 406. In some aspects, the network entity 402 may transmit to both the UE 404 and the UE 406 simultaneously. In some aspects, the network entity 402 may receive from both the UE 404 and the UE 406 simultaneously. In the case of full duplex, the network entity 402 may transmit to the UE 404 and receive from the UE 406 simultaneously, and self-interference or clutter between the transmission and reception may occur.

[0090] Figure 5 5 is a diagram 500 illustrating an example sub-band full duplex (SBFD). In sub-band full duplex, transmission resources (e.g., DL resources 502 and DL resources 506) and reception resources (e.g., UL resources 504) may overlap in time using different frequencies. Base station 512 may transmit to UE 514 using DL resources 502 and DL resources 506 while receiving from UE 516 using UL resources 504. In contrast, in-band full duplex (IBFD) may transmit and receive based on resources that overlap in time and in frequency. By using SBFD, UL duty cycle may be increased, which may result in reduced latency (e.g., it may be possible to receive DL signals in UL time slots, which may achieve latency savings) and improved UL coverage, enhanced system capacity / resource utilization / spectral efficiency, and flexible and dynamic UL / DL resource adaptation based on UL / DL traffic in a robust manner.

[0091] Figure 6 6 is a diagram illustrating an example CLI. A first UE 602 may be within a first cell 606 and served by a first network entity 604, and a second UE 608 may be within a second cell 612 and served by a second network entity 610. CLI may occur between UEs at the cell edges of nearby cells because UEs at the cell edges of nearby cells may be in close proximity to each other. Figure 6As illustrated, a first UE 602 and a second UE 608 are located at the cell edges of a first cell 606 and a second cell 612, respectively. The first UE 602 and the second UE 608 may communicate with a first network entity 604 and a second network entity 610, respectively. For example, the first UE 602 may send an UL transmission 614 to the first network entity 604, while the second UE 608 receives a DL transmission 616 from the second network entity 610. In some aspects, the UL transmission 614 to the first network entity 604 may also be received by the second UE 608, which may cause inter-UE CLI. Therefore, at the second UE 608, one or more symbols of the UL transmission 614 may collide with one or more symbols of the DL transmission 616. In addition to inter-UE CLI, inter-network entity CLI may also occur. For example, the first network entity 604 may receive a DL transmission 616 while receiving the UL transmission 614. Therefore, at the first network entity 604, one or more symbols of the UL transmission 614 may collide with one or more symbols of the DL transmission 616. The first network entity 604 may be referred to as a "victim network entity" because the first network entity 604 may be receiving transmissions that are not intended to be received by the first network entity 604, which transmissions interfere with transmissions intended to be received by the first network entity 604. Similarly, the second UE 608 may be referred to as a "victim UE". The second network entity 610 may be referred to as an "aggressor network entity" because the transmissions from the second network entity 610 may cause CLI to another network entity. Similarly, the first UE 602 may be referred to as an "aggressor UE". Various aspects provided herein may provide mechanisms for reducing CLI between network entities operating in full-duplex mode, thereby increasing the overall efficiency and throughput of the communication system.

[0092] Figure 7 FIG. 7 is a diagram illustrating an example CLI. Figure 7 As illustrated, the CLI may be within the same cell or in different cells (intra-cell or inter-cell), within the same SB or in different SBs (intra-SB or inter-SB), between UEs (inter-UE), or between network entities (inter-network entities, which may be further referred to as inter-gNB). For example, in a communication system, there may be an inter-SB intra-cell inter-UE CLI 702. There may also be an inter-SB inter-cell and inter-UE CLI 704. There may also be an inter-SB inter-network entity CLI 706.

[0093] Figure 8800 is a diagram illustrating example communications between network entities 802A and 802B and UEs 804A and 804B. In some aspects, network entity 802A and network entity 802B may be implemented as a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. In some aspects, network entity 802A and network entity 802B may be implemented in a converged or monolithic base station architecture, or alternatively in a decomposed base station architecture, and may include one or more of a CU, DU, RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In some aspects, UE 804A and UE 804B may be located on the cell edge of network entity 802A and network entity 802B, respectively.

[0094] like Figure 8 As illustrated, network entity 802A may send DCI 807 to UE 804A to schedule DL transmission 814. In some aspects, network entity 802B may send DCI 806 to UE 804B to schedule UL transmission 812. Network entity 802B may also send scheduling information 808 of UL transmission 812 to network entity 802A (e.g., which may be scheduling information included in DCI 806). As used herein, the term "scheduling information" may refer to information related to scheduling of DL transmission or UL transmission (e.g., information about time and frequency resources, or other information). In some aspects, UL transmission 812 may overlap in time with DL transmission 814. Network entity 802A may be an aggressor and network entity 802B may be a victim. In some aspects, network entity 802A may send scheduling information 808 of DL transmission 814 to network entity 802B (e.g., which may be scheduling information included in DCI 807).

[0095] At 810, the Figures 9 to 16 In various aspects described, the network entity 802A, the network entity 802B, the UE 804A, or the UE 804B may perform sensing. In some aspects, if the sensing is performed at the UE 804A or the UE 804B, the results of the sensing may be sent to the network entity 802A or the network entity 802B. In some aspects, based on the sensing, the network entity 802A or the network entity 802B may or may not adjust the transmission of the UL transmission 812 or adjust the reception of the DL transmission 814. As used herein, the term "sensing" or "sensing operation" may refer to measuring various metrics of one or more transmissions between other UEs, other network entities, or other UEs and other network entities, such as reference signal received power (RSRP) or received signal strength indicator (RSSI).

[0096] In some aspects, the aggressor network entity 802A may perform sensing for UL transmissions 812 from the UE 804B. In some aspects, the aggressor network entity 802A may perform sensing based on the victim network entity 802B having a higher priority than the aggressor network entity 802A (e.g., based on a higher priority of RRC U symbols of the victim network entity 802B). In some aspects, to facilitate sensing, scheduling information 808 may be sent from the victim network entity 802B to the aggressor network entity 802A based on backhaul (BH) signaling (e.g., via an Xn interface or an F1 interface) or over-the-air (OTA) signaling.

[0097] Fig. 9 9 is a diagram illustrating example signaling between two network entities. Fig. 9 As illustrated, if the first network entity 902A and the second network entity 902B belong to the same CU, F1 signaling may be used (e.g., to send scheduling information 808). If the first network entity 902A and the second network entity 902B belong to different CUs, F1 signaling or Xn signaling may be used (e.g., to send scheduling information 808).

[0098] Re-reference Figure 8 In some aspects, to perform sensing at 810, the aggressor network entity 802A may measure (e.g., measure reference signal received power (RSRP) or received signal strength indicator (RSSI)) DCI (e.g., DCI 806) that schedules UL traffic of the victim network entity 802B. In some aspects, if the measured RSRP or RSSI is below a threshold, the aggressor network entity 802A may proceed with a DL transmission 814 that may overlap with the UL transmission 812. In some aspects, if the measured RSRP or RSSI is above a threshold, the aggressor network entity 802A may adjust the transmission of the DL transmission 814 based on one or more of: backing off the transmit power associated with the DL transmission 814 in a time window that overlaps with the UL transmission 812; switching the transmit beam of the DL transmission 814 (e.g., switching to not spatially overlap with the transmit beam associated with the UL transmission 812); or refraining from scheduling (or canceling) the DL transmission 814 in a time window that overlaps with the UL transmission 812.

[0099] Fig.10 FIG. 1000 is a diagram illustrating such an example sensing-based CLI mitigation between network entities. Fig.10As illustrated, the victim network entity may send a PDCCH beam for DL ​​transmission. Based on the measured RSRP or RSSI, the aggressor network entity may identify whether the DL transmission has low interference or high interference to the UL beam, and may avoid sending a DL beam that overlaps with the victim network entity's PUSCH on a U symbol scheduled via PDCCH due to the sensed high CLI (based on the measured RSRP or RSSI being above a threshold). Similarly, Fig.11 11 is a diagram illustrating an example sensing-based inter-network entity CLI mitigation. The aggressor network entity may scan the Rx beams and identify one or more DL / Rx beams (e.g., a subset of DL beams) that have low interference to the UL beam, and the aggressor network entity may accordingly transmit the subset of DL beams without transmitting other DL beams.

[0100] In some aspects, to perform sensing at 810, the aggressor network entity 802A may measure scheduled UL traffic (e.g., UL transmission 812) of the victim network entity 802B. In some aspects, if the measured RSRP or RSSI is below a threshold, the aggressor network entity 802A may proceed with DL transmission 814, which may overlap with the UL transmission 812. In some aspects, if the measured RSRP or RSSI is above a threshold, the aggressor network entity 802A may adjust the transmission of the DL transmission 814 based on one or more of: backing off the transmit power associated with the DL transmission 814 in a time window that overlaps with the UL transmission 812; switching the transmit beam of the DL transmission 814 (e.g., switching to not spatially overlap with the transmit beam associated with the UL transmission 812); or refraining from scheduling (or canceling) the DL transmission 814 in a time window that overlaps with the UL transmission 812. In some aspects, if the UL traffic is a periodic configuration grant (CG) or other semi-persistent or periodic transmission (e.g., SRS), the aggressor network entity 802A may sense the first symbol of each CG opportunity or each semi-persistent or periodic opportunity. The scheduled CG opportunities may be included in the scheduling information 808.

[0101] In some aspects, sensing may be performed at UE 804A, and the results of the sensing may be sent from UE 804A to network entity 802A. In some aspects, sensing at UE 804A may be based on DCI 806 or SSB associated with network entity 802B. In some aspects, to facilitate sensing at UE 804A, UE 804A may receive scheduling information 808 from network entity 802A. Fig. 22 2200 is a diagram illustrating an example sensing-based CLI mitigation between network entities. Fig. 22 As illustrated, the UE performing and reporting the sensing may be a UE served by the aggressor network entity.

[0102] In some aspects, the victim network entity 802B may perform sensing at 810. In some aspects, the victim network entity 802B may perform sensing based on the aggressor network entity 802A having a higher priority than the victim network entity 802B (e.g., based on a higher priority of the RRC U symbol of the aggressor network entity 802A). In some aspects, to facilitate sensing, scheduling information 808 may be sent from the aggressor network entity 802A to the victim network entity 802B based on BH signaling (e.g., via an Xn interface or an F1 interface) or OTA signaling. In some aspects, the sensing may be based on measuring the RSRP or RSSI of the DCI 807 or measuring the RSRP or RSSI of the DL traffic (e.g., DL transmission 814). In some aspects, if the DL traffic is a periodic CG or other semi-persistent or periodic transmission (e.g., CSI-RS), the victim network entity 802B may sense the first symbol of each CG opportunity or each semi-persistent or periodic opportunity. The scheduled CG opportunities may be included in the scheduling information 808. In some aspects, if the measured RSRP or RSSI is below a threshold, the victim network entity 802B may proceed with the UL transmission 812, which may overlap with the DL transmission 814. In some aspects, if the measured RSRP or RSSI is above a threshold, the victim network entity 802B may adjust the reception of the UL transmission 812 based on one or more of: switching the receive beam of the UL transmission 812 (e.g., switching to not spatially overlap with the transmit beam associated with the DL transmission 814); or refraining from scheduling (or canceling) the UL transmission 812 in a time window that overlaps with the DL transmission 814.

[0103] Fig.12 1200 is a diagram illustrating an example sensing-based CLI mitigation between network entities. Fig.12 As illustrated, the aggressor network entity may transmit a PDCCH beam, and the victim network entity may have a UL / Rx beam (e.g., the illustrated UL beam) with low or high interference to the DL beam. The victim network entity may (e.g., based on a high sensing CLI) not receive a UL overlapping with the PDSCH of the aggressor network entity via the illustrated UL beam on a D symbol scheduled via the PDCCH.

[0104] Fig.13 1300 is a diagram illustrating an example sensing-based inter-network entity CLI mitigation. The victim network entity scans UL beams and identifies a UL / Rx beam (e.g., a subset UL beam) having low interference to a DL beam, and the victim network entity may receive a UL overlapping with a PDSCH of an aggressor network entity via a subset of UL beams (low sensing CLI) on a D symbol scheduled via PDCCH.

[0105] In some aspects, sensing may be performed at UE 804B, and the results of the sensing may be sent from UE 804B to network entity 802B. In some aspects, the sensing at UE 804B may be based on DCI 807 or SSB associated with network entity 802A. In some aspects, to facilitate sensing at UE 804B, UE 804B may receive scheduling information 808 from network entity 802B. Fig.23 2300 is a diagram illustrating an example sensing-based CLI mitigation between network entities. Fig.23 As illustrated, the UE performing and reporting the sensing may be a UE served by a victim network entity.

[0106] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 802A, network entity 2002, network entity 2102).

[0107] At 1402, a network entity may receive scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a second network entity via backhaul signaling or over-the-air (OTA) signaling. For example, network entity 802A may receive scheduling information 808 for one or more UL transmissions (e.g., 812) associated with one or more neighboring UEs and network entity 802B via backhaul signaling or over-the-air (OTA) signaling. In some aspects, 1402 may be performed by sensing component 199.

[0108] At 1406, the network entity may perform one or more actions based on the sensing operation for the one or more UL transmissions. For example, the network entity 802A may perform one or more actions (e.g., adjust the transmission of the DL transmission 814 or continue the transmission) based on the sensing operation for the one or more UL transmissions (e.g., 812). In some aspects, 1406 may be performed by the sensing component 199. In some aspects, the one or more actions may be one or more of: continuing the DL transmission; backing off the transmission power associated with the DL transmission in a time window associated with the one or more UL transmissions; switching a first transmission beam of the DL transmission to be non-overlapping with a second transmission beam associated with the one or more UL transmissions; or refraining from scheduling the DL transmission in a time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic TDD or full duplex.

[0109] Fig.15 1500 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 802A, network entity 2002, network entity 2102).

[0110] At 1502, a network entity may receive scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a second network entity via backhaul signaling or over-the-air (OTA) signaling. For example, network entity 802A may receive scheduling information 808 for one or more UL transmissions (e.g., 812) associated with one or more neighboring UEs and network entity 802B via backhaul signaling or over-the-air (OTA) signaling. In some aspects, 1502 may be performed by sensing component 199. In some aspects, the scheduling information is received via backhaul signaling. In some aspects, the scheduling information is received via OTA signaling.

[0111] At 1504, the network entity may perform a sensing operation for one or more UL transmissions, or receive a result of a sensing operation for one or more UL transmissions from a UE, wherein the UE is served by the first network entity and is different from one or more neighboring UEs. For example, at 810, the network entity 802A may perform a sensing operation for one or more UL transmissions, or receive a result of a sensing operation for one or more UL transmissions from a UE, wherein the UE is served by the first network entity and is different from one or more neighboring UEs, and wherein the sensing operation is based on a DCI or another DL transmission including scheduling information. In some aspects, 1504 may be performed by the sensing component 199. In some aspects, the sensing operation is based on measuring RSRP or RSSI of a DCI associated with scheduling information, and wherein one or more actions correspond to one or more of the following based on the RSSI or RSRP being above a threshold: backing off a transmit power associated with a DL transmission in a time window associated with one or more UL transmissions; switching a first transmit beam of a DL transmission to not overlap with a second transmit beam associated with the one or more UL transmissions; or suppressing scheduled DL transmissions in a time window associated with one or more UL transmissions, and wherein the DL transmissions overlap with the one or more UL transmissions in the time domain based on dynamic TDD or full-duplex. In some aspects, the sensing operation is based on measuring RSRP or RSSI of a DCI associated with scheduling information, and wherein one or more actions correspond to sending a DL transmission in a time window associated with one or more UL transmissions based on the RSSI or RSRP being below a threshold, and wherein the DL transmissions overlap with the one or more UL transmissions in the time domain based on dynamic TDD or full-duplex. In some aspects, the sensing operation is based on measuring RSRP or RSSI of one or more UL transmissions, and wherein one or more actions correspond to one or more of the following based on the RSSI or RSRP being above a threshold: backing off a transmit power associated with a DL transmission in a time window associated with the one or more UL transmissions; switching a first transmit beam of a DL transmission to not overlap with a second transmit beam associated with the one or more UL transmissions; or refraining from scheduling a DL transmission in a time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic TDD or full-duplex. In some aspects, the sensing operation is based on measuring RSRP or RSSI with the one or more UL transmissions, and wherein one or more actions correspond to transmitting a DL transmission in a time window associated with the one or more UL transmissions based on the RSSI or RSRP being below a threshold, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic TDD or full-duplex.In some aspects, the result of the sensing operation is based on the RSRP or RSSI of the DCI associated with the scheduling information, and wherein the one or more actions correspond to one or more of the following based on the RSSI or RSRP being above a threshold: backing off the transmit power associated with the DL transmission in a time window associated with the one or more UL transmissions; switching a first transmit beam of the DL transmission to not overlap with a second transmit beam associated with the one or more UL transmissions; or suppressing the scheduled DL transmission in a time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic TDD or full-duplex. In some aspects, the result of the sensing operation is based on the RSRP or RSSI of the DCI associated with the scheduling information, and wherein the one or more actions correspond to transmitting the DL transmission in a time window associated with the one or more UL transmissions based on the RSSI or RSRP being below a threshold, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic TDD or full-duplex. In some aspects, the result of the sensing operation is based on the RSRP or RSSI of the SSB associated with the second network entity, and wherein the one or more actions correspond to one or more of the following based on the RSSI or RSRP being above a threshold: backing off a transmit power associated with a DL transmission in a time window associated with one or more UL transmissions; switching a first transmit beam of the DL transmission to not overlap with a second transmit beam associated with the one or more UL transmissions; or refraining from scheduling the DL transmission in a time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic TDD or full-duplex. In some aspects, the result of the sensing operation is based on the RSRP or RSSI of the SSB associated with the second network entity, and wherein the one or more actions correspond to transmitting the DL transmission in a time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic TDD or full-duplex, based on the RSSI or RSRP being below a threshold.

[0112] At 1506, the network entity may perform one or more actions based on the sensing operation for the one or more UL transmissions. For example, the network entity 802A may perform one or more actions (e.g., adjust the transmission of the DL transmission 814 or continue the transmission) based on the sensing operation for the one or more UL transmissions (e.g., 812). In some aspects, 1506 may be performed by the sensing component 199.

[0113] Fig.16 1600 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 802B, network entity 2002, network entity 2102).

[0114] At 1602, a network entity may receive scheduling information for DL ​​transmissions associated with one or more UEs. For example, network entity 802B may send scheduling information 808 for DL ​​transmissions (e.g., 814) associated with one or more UEs. In some aspects, 1602 may be performed by sensing component 199.

[0115] At 1606, the network entity may perform one or more actions based on sensing operations for one or more UL transmissions based on dynamic TDD or full duplex based on the scheduling information, the DL transmission overlapping in timing with the one or more UL transmissions based on dynamic TDD or full duplex. For example, the network entity 802B may perform one or more actions based on sensing operations for one or more UL transmissions (e.g., 812) based on the scheduling information (e.g., adjusting reception of the UL transmission 812 or continuing the reception), the DL transmission overlapping in timing with the one or more UL transmissions based on dynamic TDD or full duplex. In some aspects, 1606 may be performed by the sensing component 199.

[0116] Fig.17 1700 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 802B, network entity 2002, network entity 2102).

[0117] At 1702, a network entity may receive scheduling information for DL ​​transmissions associated with one or more UEs. For example, network entity 802B may send scheduling information 808 for DL ​​transmissions (e.g., 814) associated with one or more UEs. In some aspects, 1702 may be performed by sensing component 199. In some aspects, the scheduling information is sent via backhaul signaling. In some aspects, the scheduling information is sent via over-the-air (OTA) signaling.

[0118] At 1704, the network entity may perform a sensing operation for one or more UL transmissions, or receive a result of a sensing operation for one or more UL transmissions from at least one of the one or more UEs. For example, at 810, the network entity 802B may perform a sensing operation for one or more UL transmissions, or receive a result of a sensing operation for one or more UL transmissions from at least one of the one or more UEs. In some aspects, 1704 may be performed by the sensing component 199. In some aspects, the sensing operation is based on measuring RSRP or RSSI of a DCI associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to one or more of the following based on the RSSI or RSRP being above a threshold: switching a first transmit beam of the one or more UL transmissions to be non-overlapping with a second transmit beam associated with the DL transmission, or refraining from scheduling the one or more UL transmissions in a time window associated with the DL transmission. In some aspects, the sensing operation is based on measuring RSRP or RSSI of a DCI associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to receiving the one or more UL transmissions based on the RSSI or RSRP being below a threshold. In some aspects, the sensing operation is based on measuring the RSRP or RSSI of a first symbol of an SPS opportunity associated with a DL transmission associated with a second network entity, and wherein one or more actions correspond to one or more of the following based on the RSSI or RSRP being above a threshold: switching a first transmit beam of one or more UL transmissions to not overlap with a second transmit beam associated with the DL transmission, or refraining from scheduling one or more UL transmissions in a time window associated with the DL transmission. In some aspects, the sensing operation is based on measuring the RSRP or RSSI of a first symbol of an SPS opportunity, and wherein one or more actions correspond to receiving one or more UL transmissions based on the RSSI or RSRP being below a threshold. In some aspects, the result of the sensing operation is based on the RSRP or RSSI of a DCI associated with a DL transmission associated with the second network entity, and wherein one or more actions correspond to one or more of the following based on the RSSI or RSRP being above a threshold: switching a first transmit beam of one or more UL transmissions to not overlap with a second transmit beam associated with the DL transmission, or refraining from scheduling one or more UL transmissions in a time window associated with the DL transmission. In some aspects, the result of the sensing operation is based on RSRP or RSSI of DCI associated with DL transmissions associated with the second network entity, and wherein the one or more actions correspond to receiving one or more UL transmissions based on the RSSI or RSRP being below a threshold.In some aspects, the result of the sensing operation is based on the RSRP or RSSI of the SSB, and wherein the one or more actions correspond to one or more of the following based on the RSSI or RSRP being above a threshold: switching a first transmit beam of one or more UL transmissions to not overlap with a second transmit beam associated with a DL transmission, or refraining from scheduling one or more UL transmissions in a time window associated with the DL transmission. In some aspects, the result of the sensing operation is based on the RSRP or RSSI of the SSB associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to receiving the one or more UL transmissions based on the RSSI or RSRP being below a threshold.

[0119] At 1706, the network entity may perform one or more actions based on sensing operations for one or more UL transmissions based on dynamic TDD or full duplex based on the scheduling information, the DL transmission overlapping in timing with the one or more UL transmissions based on dynamic TDD or full duplex. For example, the network entity 802B may perform one or more actions based on sensing operations for one or more UL transmissions (e.g., 812) based on the scheduling information (e.g., adjusting reception of the UL transmission 812 or continuing the reception), the DL transmission overlapping in timing with the one or more UL transmissions based on dynamic TDD or full duplex. In some aspects, 1706 may be performed by the sensing component 199.

[0120] Fig.18 1800 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, UE 804A; apparatus 2004).

[0121] At 1802, a UE may receive scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a first network entity. For example, UE 804A may receive scheduling information 808 for one or more UL transmissions associated with one or more neighboring UEs and network entity 802B. In some aspects, 1802 may be performed by sensing component 198.

[0122] At 1804, the UE may perform sensing operations for one or more UL transmissions based on the DL transmission, which overlaps with one or more UL transmissions in timing based on dynamic TDD or full duplex. For example, at 810, the UE 804A may perform sensing operations for one or more UL transmissions based on the DL transmission, which overlaps with one or more UL transmissions in timing based on dynamic TDD or full duplex. In some aspects, 1804 may be performed by the sensing component 198.

[0123] At 1806, the UE may send the results of the sensing operation to the second network entity. For example, at 810, UE 804A may send the results of the sensing operation to network entity 802A. In some aspects, 1806 may be performed by sensing component 198.

[0124] Fig.19 1900 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, UE 804B; device 2004).

[0125] At 1902, a UE may receive scheduling information for a DL transmission associated with another UE and a network entity. For example, UE 804B may receive scheduling information 808 for a DL transmission associated with another UE 804A and a network entity 802A. In some aspects, 1902 may be performed by sensing component 198.

[0126] At 1904, the UE may perform a sensing operation for one or more UL transmissions based on the scheduling information, the DL transmissions overlapping in timing with the one or more UL transmissions based on dynamic TDD or full duplex. For example, at 810, the UE 804B may perform a sensing operation for one or more UL transmissions based on the scheduling information, the DL transmissions overlapping in timing with the one or more UL transmissions based on dynamic TDD or full duplex. In some aspects, 1904 may be performed by the sensing component 198.

[0127] At 1906, the UE may send the results of the sensing operation to the network entity. For example, at 810, UE 804B may send the results of the sensing operation to network entity 802B. In some aspects, 1906 may be performed by sensing component 198.

[0128] Fig. 202000 is an example of a hardware implementation of an example device 2004. The device 2004 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 2004 may include a cellular baseband processor 2024 (also referred to as a modem) coupled to one or more transceivers 2022 (e.g., a cellular RF transceiver). The cellular baseband processor 2024 may include on-chip memory 2024'. In some aspects, the device 2004 may also include one or more subscriber identity module (SIM) cards 2020 and an application processor 2006 coupled to a secure digital (SD) card 2008 and a screen 2010. The application processor 2006 may include on-chip memory 2006'. In some aspects, the device 2004 may also include a Bluetooth module 2012, a WLAN module 2014, a satellite system module 2016 (e.g., a GNSS module), one or more sensor modules 2018 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; a light detection and ranging (LIDAR), a radio-aided detection and ranging (RADAR), a sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 2026, a power source 2030, and / or a camera 2032. The Bluetooth module 2012, the WLAN module 2014, and the satellite system module 2016 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 2024 communicates with the UE 104 and / or with the RU associated with the network entity 2002 through the transceiver 2022 via one or more antennas 2080. The cellular baseband processor 2024 and the application processor 2006 may each include a computer-readable medium / memory 2024', 2006', respectively. The additional memory module 2026 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 2024', 2006', 2026 may be non-transitory. The cellular baseband processor 2024 and the application processor 2006 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software enables the cellular baseband processor 2024 / application processor 2006 to perform various functions described herein when executed by the cellular baseband processor 2024 / application processor 2006. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 2024 / application processor 2006 when executing the software. The cellular baseband processor 2024 / application processor 2006 may be a component of the UE 350 and may include at least one of the memory 360 and / or the TX processor 368, the RX processor 356, and the controller / processor 359.In one configuration, the apparatus 2004 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 2024 and / or the application processor 2006, and in another configuration, the apparatus 2004 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 2004.

[0129] As discussed herein, the sensing component 198 may be configured to receive scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a first network entity. The sensing component 198 may be configured to perform a sensing operation for one or more UL transmissions based on a DL transmission, which overlaps with one or more UL transmissions in timing based on dynamic TDD or full duplex. The sensing component 198 may be configured to send the result of the sensing operation to a second network entity. The sensing component 198 may be configured to receive scheduling information for a DL transmission associated with another UE and a network entity. The sensing component 198 may be configured to perform a sensing operation for one or more UL transmissions based on the scheduling information, which overlaps with one or more UL transmissions in timing based on dynamic TDD or full duplex. The sensing component 198 may be configured to send the result of the sensing operation to the network entity. The sensing component 198 may be within the cellular baseband processor 2024, the application processor 2006, or both the cellular baseband processor 2024 and the application processor 2006. The sensing component 198 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. As shown, the device 2004 may include multiple components configured for various functions. In one configuration, the device 2004 (and specifically, the cellular baseband processor 2024 and / or the application processor 2006) includes a component for receiving scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a first network entity. In some aspects, the device 2004 may also include a component for performing a sensing operation for one or more UL transmissions based on the scheduling information, the DL transmission overlapping with one or more UL transmissions in timing based on dynamic TDD or full-duplex. In some aspects, the device 2004 may also include a component for sending the result of the sensing operation to the second network entity. In some aspects, the device 2004 may also include a component for receiving scheduling information for one or more UL transmissions associated with the UE and the network entity. In some aspects, the device 2004 may also include a component for performing a sensing operation for one or more UL transmissions. In some aspects, the device 2004 may also include a component for sending a result of the sensing operation to a network entity. The component may be a sensing component 198 of the device 2004 configured to perform the functions recited by the component. As described herein, the device 2004 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, these components may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recited by the component.

[0130] Fig.21 2100 is a diagram illustrating an example of a hardware implementation of a network entity 2102. The network entity 2102 may be a BS, a component of a BS, or may implement BS functionality. The network entity 2102 may include at least one of a CU 2110, a DU 2130, or a RU 2140. For example, depending on the layer functionality handled by the sensing component 199, the network entity 2102 may include a CU 2110; both a CU 2110 and a DU 2130; each of the CU 2110, the DU 2130, and the RU 2140; the DU 2130; both a DU 2130 and a RU 2140; or a RU 2140. The CU 2110 may include a CU processor 2112. The CU processor 2112 may include an on-chip memory 2112'. In some aspects, the CU 2110 may also include an additional memory module 2114 and a communication interface 2118. CU 2110 communicates with DU 2130 via a midhaul link, such as an F1 interface. DU 2130 may include a DU processor 2132. DU processor 2132 may include on-chip memory 2132'. In some aspects, DU 2130 may also include an additional memory module 2134 and a communication interface 2138. DU 2130 communicates with RU 2140 via a fronthaul link. RU 2140 may include a RU processor 2142. RU processor 2142 may include on-chip memory 2142'. In some aspects, RU 2140 may also include an additional memory module 2144, one or more transceivers 2146, an antenna 2180, and a communication interface 2148. RU 2140 communicates with UE 104. On-chip memory 2112', 2132', 2142' and additional memory modules 2114, 2134, 2144 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of the processors 2112, 2132, 2142 is responsible for general processing, including the execution of software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described herein. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0131] As discussed herein, the sensing component 199 may be configured to receive scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a second network entity via backhaul signaling or over-the-air (OTA) signaling. The sensing component 199 may be configured to perform one or more actions based on sensing operations for one or more UL transmissions. The sensing component 199 may be configured to receive scheduling information for DL ​​transmissions associated with one or more UEs. The sensing component 199 may be configured to perform one or more actions based on sensing operations for one or more UL transmissions based on the scheduling information, the DL transmission overlapping with one or more UL transmissions in timing based on dynamic TDD or full duplex. The sensing component 199 may be within one or more processors of one or more of the CU 2110, DU 2130, and RU 2140. The sensing component 199 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination of the above. The network entity 2102 may include a variety of components configured for various functions. In one configuration, the network entity 2102 includes a component for receiving scheduling information for one or more UL transmissions associated with one or more neighboring UEs and a second network entity. In some aspects, the network entity 2102 may also include a component for performing one or more actions based on a sensing operation for one or more UL transmissions. In some aspects, the network entity 2102 may also include a component for performing a sensing operation for one or more UL transmissions. In some aspects, the network entity 2102 may also include a component for receiving a result of a sensing operation for one or more UL transmissions from a UE, wherein the UE is served by a first network entity and is different from one or more neighboring UEs, and wherein the sensing operation is based on a DCI or another DL transmission including scheduling information. In some aspects, the network entity 2102 may include a component for receiving scheduling information for UL transmissions associated with one or more UEs. In some aspects, the network entity 2102 may also include a component for performing one or more actions based on a sensing operation for one or more UL transmissions based on the scheduling information, the DL transmission overlapping in timing with one or more UL transmissions based on dynamic TDD or full duplex. In some aspects, the network entity 2102 may also include a component for performing a sensing operation for one or more UL transmissions. In some aspects, the network entity 2102 may further include means for receiving results of sensing operations for one or more UL transmissions from at least one of the one or more UEs.The means may be a sensing component 199 of the network entity 2102 configured to perform the functions recited by the means.As described herein, the network entity 2102 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the components may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the components.

[0132] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0133] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, references to elements in the singular form do not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, then the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0134] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0135] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0136] Aspect 1 is a device for wireless communication at a first network entity, the device comprising: a memory; and at least one processor coupled to the memory, and at least partially based on information stored in the memory, the at least one processor is configured to: receive scheduling information for one or more uplink (UL) transmissions associated with one or more neighboring user equipment (UE) and a second network entity via backhaul signaling or over-the-air (OTA) signaling; and perform one or more actions based on sensing operations for the one or more UL transmissions.

[0137] Aspect 2: The apparatus according to any one of aspects 1, wherein the at least one processor is further configured to: perform the sensing operation based on the one or more UL transmissions.

[0138] Aspect 3 is an apparatus according to any one of Aspects 1 to 2, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink (DL) control information (DCI) associated with the scheduling information, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: backing off the transmit power associated with the DL transmission in a time window associated with the one or more UL transmissions; switching a first transmit beam of the DL transmission to be non-overlapping with a second transmit beam associated with the one or more UL transmissions; or suppressing scheduling of the DL transmission in the time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

[0139] Aspect 4 is an apparatus according to any one of Aspects 1 to 3, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink (DL) control information (DCI) associated with the scheduling information, and wherein the one or more actions correspond to: sending a DL transmission in a time window associated with the one or more UL transmissions based on the RSSI or the RSRP being lower than a threshold, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

[0140] Aspect 5 is an apparatus according to any one of Aspects 1 to 4, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of the one or more UL transmissions, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: backing off the transmission power associated with a downlink (DL) transmission in a time window associated with the one or more UL transmissions; switching a first transmission beam of the DL transmission to be non-overlapping with a second transmission beam associated with the one or more UL transmissions; or suppressing scheduling of the DL transmission in the time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

[0141] Aspect 6 is an apparatus according to any one of Aspects 1 to 5, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of the one or more UL transmissions, and wherein the one or more actions correspond to: sending a downlink (DL) transmission in a time window associated with the one or more UL transmissions based on the RSSI or the RSRP being lower than a threshold, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

[0142] Aspect 7 is an apparatus according to any one of Aspects 1 to 6, wherein the at least one processor is further configured to: receive a result of the sensing operation for the one or more UL transmissions from a UE, wherein the UE is served by the first network entity and is different from the one or more neighboring UEs, and wherein the sensing operation is based on downlink control information (DCI) or another downlink (DL) transmission including the scheduling information.

[0143] Aspect 8 is an apparatus according to any one of Aspects 1 to 7, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink (DL) control information (DCI) associated with the scheduling information, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: backing off the transmit power associated with the DL transmission in a time window associated with the one or more UL transmissions; switching a first transmit beam of the DL transmission to be non-overlapping with a second transmit beam associated with the one or more UL transmissions; or suppressing scheduling of the DL transmission in the time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

[0144] Aspect 9 is an apparatus according to any one of Aspects 1 to 8, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink (DL) control information (DCI) associated with the scheduling information, and wherein the one or more actions correspond to: sending a DL transmission in a time window associated with the one or more UL transmissions based on the RSSI or the RSRP being below a threshold.

[0145] Aspect 10 is an apparatus according to any one of Aspects 1 to 9, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a synchronization signal block (SSB) associated with the second network entity, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: backing off the transmission power associated with a downlink (DL) transmission in a time window associated with the one or more UL transmissions; switching a first transmission beam of the DL transmission to be non-overlapping with a second transmission beam associated with the one or more UL transmissions; or suppressing scheduling of the DL transmission in the time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

[0146] Aspect 11 is an apparatus according to any one of Aspects 1 to 10, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a synchronization signal block (SSB) associated with the second network entity, and wherein the one or more actions correspond to: sending a downlink (DL) transmission in a time window associated with the one or more UL transmissions based on the RSSI or the RSRP being lower than a threshold, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

[0147] Aspect 12 is an apparatus according to any one of aspects 1 to 11, wherein the scheduling information is received via the backhaul signaling.

[0148] Aspect 13 is an apparatus according to any one of aspects 1 to 12, wherein the scheduling information is received via the OTA signaling.

[0149] Aspect 14 is an apparatus according to any one of aspects 1 to 13, the apparatus further comprising: a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna can be configured to receive the scheduling information.

[0150] Aspect 15 is a device for performing wireless communications at a first network entity, the device comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receive scheduling information for downlink (DL) transmissions associated with one or more user equipment (UE); and perform one or more actions based on sensing operations for one or more uplink (UL) transmissions based on the scheduling information, the DL transmissions overlapping in timing with the one or more UL transmissions based on dynamic time division duplex (TDD) or full duplex.

[0151] Aspect 16 is the apparatus of aspect 15, wherein the at least one processor is further configured to perform the sensing operation for the one or more UL transmissions.

[0152] Aspect 17 is an apparatus according to any one of Aspects 15 to 16, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of DL control information (DCI) associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: switching a first transmission beam of the one or more UL transmissions to be non-overlapping with a second transmission beam associated with the DL transmission; or suppressing scheduling of the one or more UL transmissions in a time window associated with the DL transmission.

[0153] Aspect 18 is an apparatus according to any one of Aspects 15 to 17, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of DL control information (DCI) associated with the DL transmission associated with a second network entity, and wherein the one or more actions correspond to: receiving the one or more UL transmissions based on the RSSI or the RSRP being below a threshold.

[0154] Aspect 19 is an apparatus according to any one of Aspects 15 to 18, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a first symbol of a semi-persistent scheduling (SPS) opportunity associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: switching a first transmission beam of the one or more UL transmissions to be non-overlapping with a second transmission beam associated with the DL transmission; or suppressing scheduling of the one or more UL transmissions in a time window associated with the DL transmission.

[0155] Aspect 20 is an apparatus according to any one of Aspects 15 to 19, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a first symbol of a semi-persistent scheduling (SPS) opportunity, and wherein the one or more actions correspond to: receiving the one or more UL transmissions based on the RSSI or the RSRP being below a threshold.

[0156] Aspect 21 is an apparatus according to any one of aspects 15 to 20, wherein the at least one processor is further configured to: receive a result of the sensing operation for the one or more UL transmissions from at least one UE of the one or more UEs.

[0157] Aspect 22 is an apparatus according to any one of Aspects 15 to 21, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink control information (DCI) associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: switching a first transmission beam of the one or more UL transmissions to be non-overlapping with a second transmission beam associated with the DL transmission; or suppressing scheduling of the one or more UL transmissions in a time window associated with the DL transmission.

[0158] Aspect 23 is an apparatus according to any one of Aspects 15 to 22, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink (DL) control information (DCI) associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to: receiving the one or more UL transmissions based on the RSSI or the RSRP being below a threshold.

[0159] Aspect 24 is an apparatus according to any one of Aspects 15 to 23, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a synchronization signal block (SSB), and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: switching a first transmission beam of the one or more UL transmissions to be non-overlapping with a second transmission beam associated with a DL transmission; or suppressing scheduling of the one or more UL transmissions in a time window associated with the DL transmission.

[0160] Aspect 25 is an apparatus according to any one of Aspects 15 to 24, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a synchronization signal block (SSB) associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to: receiving the one or more UL transmissions based on the RSSI or the RSRP being below a threshold.

[0161] Aspect 26 is an apparatus according to any one of aspects 15 to 25, wherein the scheduling information is sent via backhaul signaling.

[0162] Aspect 27 is an apparatus according to any one of aspects 15 to 26, wherein the scheduling information is sent via over-the-air (OTA) signaling.

[0163] Aspect 28 is an apparatus according to any one of aspects 15 to 27, the apparatus further comprising: a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna can be configured to send the scheduling information.

[0164] Aspect 29 is a device for performing wireless communications at a user equipment (UE), the device comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receive scheduling information for one or more uplink (UL) transmissions associated with one or more neighboring user equipment (UE) and a first network entity; perform a sensing operation for the one or more UL transmissions based on a downlink (DL) transmission, the DL transmission overlapping in timing with the one or more UL transmissions based on dynamic time division duplex (TDD) or full duplex; and send a result of the sensing operation to a second network entity.

[0165] Aspect 30 is an apparatus for performing wireless communications at a user equipment (UE), the apparatus comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receive scheduling information for a downlink (DL) transmission associated with another UE and a network entity; perform a sensing operation for one or more uplink (UL) transmissions based on the scheduling information, the DL transmissions overlapping in timing with the UL transmissions based on dynamic time division duplex (TDD) or full duplex; and send a result of the sensing operation to the network entity.

[0166] Aspect 31 is an apparatus for wireless communication at a device, the apparatus comprising: a memory and at least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to perform a method according to any one of aspects 1 to 28. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0167] Aspect 32 is an apparatus for wireless communication, the apparatus comprising: means for performing the method according to any one of aspects 1 to 28.

[0168] Aspect 33 is a non-transitory computer-readable medium, the non-transitory computer-readable medium comprising: instructions, which, when executed by a device, cause the device to perform the method according to any one of aspects 1 to 28.

[0169] Aspect 34 is an apparatus for wireless communication at a device, the apparatus comprising: a memory and at least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to perform a method according to any one of aspects 29 to 30. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0170] Aspect 35 is an apparatus for wireless communication, the apparatus comprising: means for performing a method according to any one of aspects 29 to 30.

[0171] Aspect 36 is a non-transitory computer-readable medium, the non-transitory computer-readable medium comprising: instructions, the instructions, when executed by an apparatus, causing the apparatus to perform the method according to any one of aspects 29 to 30.

Claims

1. An apparatus for wireless communication at a first network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving scheduling information for one or more uplink (UL) transmissions associated with one or more neighboring user equipment (UE) and a second network entity via backhaul signaling or over-the-air (OTA) signaling; as well as One or more actions are performed based on the sensing operations for the one or more UL transmissions.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: The sensing operation is performed for the one or more UL transmissions.

3. An apparatus according to claim 2, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink (DL) control information (DCI) associated with the scheduling information, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: backing off the transmission power associated with the DL transmission in a time window associated with the one or more UL transmissions; switching a first transmission beam of the DL transmission to be non-overlapping with a second transmission beam associated with the one or more UL transmissions; or suppressing scheduling of the DL transmission in the time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

4. The apparatus of claim 2 , wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink (DL) control information (DCI) associated with the scheduling information, and wherein the one or more actions correspond to, based on the RSSI or the RSRP being below a threshold, sending a DL transmission in a time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

5. An apparatus according to claim 2, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of the one or more UL transmissions, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: backing off a transmission power associated with a downlink (DL) transmission in a time window associated with the one or more UL transmissions; switching a first transmission beam of the DL transmission to be non-overlapping with a second transmission beam associated with the one or more UL transmissions; or suppressing scheduling of the DL transmission in the time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplexing (TDD) or full duplexing.

6. The apparatus of claim 2, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of the one or more UL transmissions, and wherein the one or more actions correspond to, based on the RSSI or the RSRP being below a threshold, sending a downlink (DL) transmission in a time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplexing (TDD) or full duplexing.

7. The apparatus of claim 1, wherein the at least one processor is further configured to: A result of the sensing operation for the one or more UL transmissions is received from a UE, wherein the UE is served by the first network entity and is different from the one or more neighboring UEs, and wherein the sensing operation is based on downlink control information (DCI) or another downlink (DL) transmission including the scheduling information.

8. An apparatus according to claim 7, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink (DL) control information (DCI) associated with the scheduling information, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: backing off the transmission power associated with the DL transmission in a time window associated with the one or more UL transmissions; switching a first transmission beam of the DL transmission to be non-overlapping with a second transmission beam associated with the one or more UL transmissions; or suppressing scheduling of the DL transmission in the time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

9. An apparatus according to claim 7, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink (DL) control information (DCI) associated with the scheduling information, and wherein the one or more actions correspond to: sending a DL transmission in a time window associated with the one or more UL transmissions based on the RSSI or the RSRP being below a threshold.

10. An apparatus according to claim 7, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a synchronization signal block (SSB) associated with the second network entity, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: backing off the transmission power associated with a downlink (DL) transmission in a time window associated with the one or more UL transmissions; switching a first transmission beam of the DL transmission to be non-overlapping with a second transmission beam associated with the one or more UL transmissions; or suppressing scheduling of the DL transmission in the time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplexing (TDD) or full duplexing.

11. The apparatus of claim 7, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a synchronization signal block (SSB) associated with the second network entity, and wherein the one or more actions correspond to, based on the RSSI or the RSRP being below a threshold, sending a downlink (DL) transmission in a time window associated with the one or more UL transmissions, and wherein the DL transmission overlaps with the one or more UL transmissions in the time domain based on dynamic time division duplex (TDD) or full duplex.

12. The apparatus of claim 1, wherein the scheduling information is received via the backhaul signaling.

13. The apparatus of claim 1, wherein the scheduling information is received via the OTA signaling.

14. The apparatus according to claim 1, further comprising: A transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to receive the scheduling information.

15. An apparatus for wireless communication at a first network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving scheduling information for downlink (DL) transmissions associated with one or more user equipments (UEs); and One or more actions based on sensing operations for one or more uplink (UL) transmissions are performed based on the scheduling information, the DL transmissions overlapping in timing with the one or more UL transmissions based on dynamic time division duplex (TDD) or full duplex.

16. The apparatus of claim 15, wherein the at least one processor is further configured to: The sensing operation is performed for the one or more UL transmissions.

17. An apparatus according to claim 16, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of DL control information (DCI) associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: switching a first transmission beam of the one or more UL transmissions to be non-overlapping with a second transmission beam associated with the DL transmission; or suppressing scheduling of the one or more UL transmissions in a time window associated with the DL transmission.

18. The apparatus of claim 16, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of DL control information (DCI) associated with the DL transmission associated with a second network entity, and wherein the one or more actions correspond to receiving the one or more UL transmissions based on the RSSI or the RSRP being below a threshold.

19. An apparatus according to claim 16, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a first symbol of a semi-persistent scheduling (SPS) opportunity associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: switching a first transmit beam of the one or more UL transmissions to be non-overlapping with a second transmit beam associated with the DL transmission; or suppressing scheduling of the one or more UL transmissions in a time window associated with the DL transmission.

20. An apparatus according to claim 16, wherein the sensing operation is based on measuring a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a first symbol of a semi-persistent scheduling (SPS) opportunity, and wherein the one or more actions correspond to: receiving the one or more UL transmissions based on the RSSI or the RSRP being below a threshold.

21. The apparatus of claim 15, wherein the at least one processor is further configured to: A result of the sensing operation for the one or more UL transmissions is received from at least one UE of the one or more UEs.

22. An apparatus according to claim 21, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink control information (DCI) associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: switching a first transmission beam of the one or more UL transmissions to be non-overlapping with a second transmission beam associated with the DL transmission; or suppressing scheduling of the one or more UL transmissions in a time window associated with the DL transmission.

23. An apparatus according to claim 21, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of downlink (DL) control information (DCI) associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to: receiving the one or more UL transmissions based on the RSSI or the RSRP being below a threshold.

24. An apparatus according to claim 21, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a synchronization signal block (SSB), and wherein the one or more actions correspond to one or more of the following based on the RSSI or the RSRP being higher than a threshold: switching a first transmit beam of the one or more UL transmissions to be non-overlapping with a second transmit beam associated with a DL transmission; or suppressing scheduling of the one or more UL transmissions in a time window associated with the DL transmission.

25. An apparatus according to claim 21, wherein the result of the sensing operation is based on a reference signal received power (RSRP) or a received signal strength indicator (RSSI) of a synchronization signal block (SSB) associated with a DL transmission associated with a second network entity, and wherein the one or more actions correspond to: receiving the one or more UL transmissions based on the RSSI or the RSRP being below a threshold.

26. The apparatus of claim 15, wherein the scheduling information is sent via backhaul signaling.

27. The apparatus of claim 15, wherein the scheduling information is sent via over-the-air (OTA) signaling.

28. The apparatus according to claim 15, further comprising: A transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to transmit the scheduling information.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving scheduling information for one or more uplink (UL) transmissions associated with one or more neighboring user equipments (UEs) and a first network entity; performing a sensing operation for the one or more UL transmissions based on a downlink (DL) transmission, the DL transmission overlapping in timing with the one or more UL transmissions based on dynamic time division duplex (TDD) or full duplex; as well as A result of the sensing operation is sent to a second network entity.

30. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving scheduling information for a downlink (DL) transmission associated with another UE and a network entity; performing a sensing operation for one or more uplink (UL) transmissions based on the scheduling information, the DL transmissions overlapping in timing with the UL transmissions based on dynamic time division duplex (TDD) or full duplex; as well as A result of the sensing operation is sent to the network entity.

Images