Probability indication for interference management

Abstract

A first network node may identify at least one of a probability of use or an interference probability for each Rx beam of the first network node in a plurality of Tx-Rx beam pairs associated with the first network node and a second network node. The usage probability may include a usage metric indicating a likelihood of using the beam. The interference probability may include an interference metric indicating a likelihood that a Tx beam of the second network node interferes with an Rx beam of the first network node. The first network node may send a first indication of the probability of use or the probability of interference for each Rx beam in the plurality of Tx-Rx beam pairs. The second network node may receive the first indication and adjust beam scheduling for at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs based on the received first indication.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 663,415, filed on May 13, 2022, entitled “PROBABILITY INDICATION FOR INTERFERENCE MANAGEMENT,” 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 a scheduling system for minimizing interference between wireless transmissions. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Some 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 city, country, region, and even global levels. 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. 5G NR 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. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents the summary of the invention of one or more aspects in order to provide a basic understanding of these aspects. The summary of the invention is not a broad overview of all contemplated aspects, and is neither intended to identify the key elements or essential elements of all aspects, nor to delimit the scope of any or all aspects. Its only 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] When one network node receives a first transmission at the same time as another network node transmits a second transmission, the first transmission and the second transmission may interfere with each other. For example, a first transmission transmitted from a first network node to a second network node may interfere with a second transmission transmitted from a third network node to a fourth network node. Such situations may occur more frequently when network nodes are capable of full-duplex (FD) simultaneous uplink / downlink transmission. For example, a first transmission transmitted from a first network node to a second network node may interfere with a second transmission transmitted from a third network node to the first network node. Such interference may occur whenever any part of a transmit (Tx) beam is transmitted during a time period overlapping with a time period in which a receive (Rx) beam is received. For example, such interference may occur between a base station (BS) Tx beam and a BS Rx beam, between a BS Tx beam and a user equipment (UE) Rx beam, between a UE Tx beam and a BS Rx beam, or between a UE Tx beam and a UE Rx beam.

[0008] The first network node may identify at least one of a usage probability or an interference probability of each Rx beam of the first network node in a plurality of Tx-Rx beam pairs associated with the first network node and the second network node. The usage probability may include a usage metric indicating the likelihood of using the beam. The interference probability may include an interference metric indicating the likelihood that the Tx beam of the second network node interferes with the Rx beam of the first network node. The first network node may send a first indication of the usage probability or the interference probability for each Rx beam in the plurality of Tx-Rx beam pairs. The second network node may receive the first indication and adjust beam scheduling for at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs based on the received first indication.

[0009] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may have a memory and at least one processor, the at least one processor being coupled to the memory and configured to: identify at least one of a usage probability or an interference probability of each Rx beam of the first network node in a plurality of Tx-Rx beam pairs associated with the first network node and the second network node. The usage probability may include a usage metric indicating the likelihood of using the beam. The interference probability may include an interference metric indicating the likelihood that the Tx beam of the second network node interferes with the Rx beam of the first network node. The at least one processor may also be configured to: send a first indication of at least one of the usage probability or the interference probability for each Rx beam in the plurality of Tx-Rx beam pairs to the second network node.

[0010] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may have a memory and at least one processor, the at least one processor being coupled to the memory and configured to: receive from a second network node a first indication of at least one of a usage probability or an interference probability of each Rx beam of the second network node in a plurality of Tx-Rx beam pairs. The usage probability may include a usage metric indicating the likelihood of using the beam. The interference probability may include an interference metric indicating the likelihood that the Tx beam of the first network node interferes with the Rx beam of the second network node. The at least one processor may also be configured to: adjust beam scheduling for at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs based on the received first indication.

[0011] To achieve the foregoing and related purposes, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0018] Figure 4 is a network connection flowchart illustrating an example of two BS devices that may respectively have Rx beams and Tx beams that may interfere with each other.

[0019] Figure 5 is a network connection flowchart illustrating an example of another two BS devices which may respectively have Rx beams and Tx beams that may interfere with each other.

[0020] Figure 6 is a network connection flowchart illustrating an example of a UE and a BS which may respectively have Rx beams and Tx beams which may interfere with each other.

[0021] Figure 7 is a network connection flowchart illustrating another example of a UE and a BS which may respectively have Rx beams and Tx beams which may interfere with each other.

[0022] Figure 8 is a network connection flowchart illustrating an example of a UE and a UE that may respectively have Rx beams and Tx beams that may interfere with each other.

[0023] Fig. 9 is a network connection flowchart illustrating another example of a UE and a UE which may respectively have an Rx beam and a Tx beam which may interfere with each other.

[0024] Fig.10 is a network connection flowchart illustrating an example of a BS and a UE which may respectively have Rx beams and Tx beams which may interfere with each other.

[0025] Fig.11 is a network connection flowchart illustrating another example of a BS and a UE which may respectively have Rx beams and Tx beams which may interfere with each other.

[0026] Fig.12 is a network connection flowchart illustrating an example of a UE and a UE that may respectively have Rx beams and Tx beams that may interfere with each other.

[0027] Fig.13 is a network connection flowchart illustrating another example of a UE and a UE which may respectively have an Rx beam and a Tx beam which may interfere with each other.

[0028] Fig.14is a flow chart of a method of wireless communication at a wireless device according to various aspects of the present disclosure.

[0029] Fig.15 is a flow chart of another method of wireless communications at a wireless device in accordance with various aspects of the present disclosure.

[0030] Fig.16 is a flow chart of another method of wireless communications at a wireless device in accordance with various aspects of the present disclosure.

[0031] Fig.17 is a flow chart of another method of wireless communications at a wireless device in accordance with various aspects of the present disclosure.

[0032] Fig.18 is a diagram illustrating an example of a hardware implementation of an example apparatus.

[0033] Fig.19 is a diagram illustrating another example of a hardware implementation for an example apparatus. DETAILED DESCRIPTION

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

[0035] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, 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.

[0036] 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 it is referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be widely interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0037] Therefore, in one or more example embodiments, the described functions can be implemented with hardware, software or any combination thereof. If implemented with software, the function can be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), an optical disk storage device, a magnetic disk storage device, other magnetic storage devices, a combination of various types of computer-readable media, or any other medium that can be used to store instructions or data structure forms of computer executable code that can be accessed by a computer.

[0038] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and situations. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, specific implementations and / or uses 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 / purchasing equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not specifically relate to use cases or applications, the innovation described may have various types of applicability. Specific implementations can 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 aspects of the described innovation. In some actual settings, the device 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 innovations described herein are intended to be practiced in a variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0039] 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. As 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 group 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 group of one or more components, a second processing entity, etc.

[0040] As described herein, different terms may be used in various aspects to describe the transmission 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, send, output, transmit, 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, sent, output, transmitted, or sent by the first network node.

[0041] 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, which 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.

[0042] 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 these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals on a wired transmission medium or send signals to one or more of the other units. 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 on a wireless transmission medium.

[0043] 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). CU 110 may be implemented to communicate with DU 130 as needed for network control and signaling.

[0044] 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 at least in part 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.

[0045] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional 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 plane 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).

[0046] 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 .

[0047] 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.

[0048] 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 creation of RAN management policies (such as A1 policies).

[0049] 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 transmission diversity. The communication link may pass through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The 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 for DL ​​compared to UL). The component carrier 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).

[0050] 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.

[0051] 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.

[0052] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0053] 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.

[0054] In view of the above, unless otherwise specified, if the term "below 6 GHz" or the like is used in this document, 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" or the like is used in this document, 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.

[0055] 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 best 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.

[0056] 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 transmit receive point (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, a clustered (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or clustered base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0057] 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), service 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.

[0058] 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.

[0059] Refer again Figure 1 In some aspects, the UE 104 may have a probability interface component 198 configured to determine the probability of use and / or interference of the beam of the Tx-Rx pair, and / or adjust the beam scheduling to minimize the interference probability. In some aspects, the base station (BS) 102 may similarly have a probability interface component 199 configured to determine the probability of use and / or interference of the beam of the Tx-Rx pair, and / or adjust the beam scheduling to minimize the interference probability. The BS 102 may transmit a Tx beam that may interfere with the Rx beam received by the BS 102, by another BS, or by another UE. The Tx beam may be received by another BS or by another UE. The Rx beam may be transmitted by another BS or by another UE. The UE 104 may transmit a Tx beam that may interfere with the Rx beam received by the BS 102, by another BS, or by another UE. The Tx beam may be received by another BS or by another UE. The Rx beam may be sent by yet another BS or by yet another UE.

[0060] One or more probability interface components (such as the probability interface component 198 of UE 104 or the probability interface component 199 of BS102) may be configured to determine the probability of use and / or interference probability of the beam of the Tx-Rx pair and adjust the beam scheduling to minimize interference. When the probability of use or the probability of interference reaches or exceeds a threshold, the probability interface component may adjust the beam scheduling and implement the scheduling on a suitable wireless device (such as a wireless device that sends a Tx beam, a wireless device that receives an Rx beam, or a wireless device that schedules a Tx beam or an Rx beam). Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. Each UE in the UE 104 of BS102 may be referred to as a wireless device or a network node.

[0061] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 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 may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0062] 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 the same 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) spread 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 time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0063]

[0064] 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. Accordingly, 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 is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. 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).

[0065] A resource grid may be used to represent the 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 plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0066] 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).

[0067] 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 specific 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 specific 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 called 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 such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0068] 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 structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0069] 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 additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0070] Figure 3375. The Controller / Processor 375 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.

[0071] 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 transmission channel, forward error correction (FEC) decoding / decoding of the transmission 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-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded 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., a pilot) in the time and / or frequency domain, and then the individual streams are merged together 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.

[0072] 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 converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). 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 most likely signal constellation point 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 base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0073] 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 performing error detection using ACK and / or NACK protocols to support HARQ operations.

[0074] 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.

[0075] Channel estimates derived by the channel estimator 358 from 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.

[0076] 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 corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to an Rx processor 370.

[0077] 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.

[0078] At least one of the Tx processor 368, the Rx processor 356, and the controller / processor 359 may be configured to perform Figure 1 The probability interface component 198 combines various aspects.

[0079] At least one of the Tx processor 316, the Rx processor 370, and the controller / processor 375 may be configured to perform Figure 1 The probability interface component 199 combines various aspects.

[0080] A network node such as a BS and / or a UE (also referred to as a wireless device) may be configured to have FD capabilities. That is, such a wireless device may be configured to simultaneously transmit a Tx beam and receive an Rx beam. Such a device may be configured to perform simultaneous UL / DL transmission using any suitable frequency band (e.g., a frequency band in frequency range 1 (FR1), frequency range 2 (FR2), frequency range 4 (FR4), and frequency range 5 (FR5)). Different associated aspects of the protocol may also perform similar functionality. FD capabilities may be configured for a BS, a UE, or both. For example, a UE may be configured to use one panel to perform UL transmission and another panel to perform DL reception. In addition, a BS may be configured to use one panel to receive a UL beam and another panel to send a DL beam. FD capabilities may depend on a wireless device having one or more hardware and / or software configurations (such as having two different antennas or using beam separation). The UL / DL beams of a single wireless device may even interfere with each other, resulting in self-interference or spurious echo between the UL and DL beams of the same device (e.g., caused by direct leakage from the transmitter to the receiver, or by reflectors reflecting the signal back to the receiving panel).

[0081] Configuring a device with FD capability can provide many benefits, such as latency reduction. It is possible to receive DL signals in UL-only time slots, which can achieve latency savings. FD capability can also enhance the spectral efficiency (SE) of each cell or each UE configured with FD capability. By configuring a device to handle both UL transmissions and DL transmissions simultaneously, resources can be used more efficiently and coverage for the device can be enhanced.

[0082] Multiple simultaneous UL / DL transmission scenarios can be implemented by a BS or UE configured for FD capability. Figure 1104 in the embodiment may be configured to simultaneously receive DL transmissions from BS 102 and to simultaneously send UL transmissions to another BS. Additionally or alternatively, UE 104 may be configured to simultaneously send UL transmissions to BS 102 while another UE 104 receives DL transmissions from the same BS 102. Additionally or alternatively, UE 104 may be configured to simultaneously send UL transmissions and receive DL transmissions from the same BS 102. Additionally or alternatively, UE 104 may be configured to simultaneously send sidelink transmissions to another UE 104 while receiving another sidelink transmission from the same UE. Additionally or alternatively, UE 104 may be configured to simultaneously send sidelink transmissions to another UE 104 while receiving another sidelink transmission from yet another UE.

[0083] However, as the number of transmissions increases, the risk of the transmissions interfering with each other also increases. Figure 4 A network connection flow diagram 400 illustrating an example of a BS 404 and a BS 406 that may have a Tx beam 414 that may interfere with an Rx beam 412 is shown. The network connection flow diagram 400 has a wireless device 402 (which may be a BS or a UE), the BS 404, the BS 406, and another wireless device 408 (which may also be a BS or a UE). When the BS 406 transmits the Tx beam 414 to the wireless device 408, the Tx beam 414 may interfere with the Rx beam 412 transmitted from the wireless device 402 to the BS 404. The network connection flow diagram 400 illustrates a use case for inter-gNB or inter-BS cross link interference (CLI), where usage probability information of gNB / BS beams may be transmitted via inter-gNB or inter-BS messaging to reduce potential interference between Tx-Rx beams.

[0084] In order to determine which possible Tx beams from BS 406 may interfere with the Rx beam transmitted to BS 404, BS 406 may be configured to communicate with BS 404 using interference communication 410. For example, BS 406 may send a list of Tx beams that BS 406 can transmit to BS 404, BS 404 may send a list of Rx beams that BS 404 can receive to BS 406, BS 404 may send a Tx-Rx matrix with known interference levels to BS 406, which BS 406 may use to determine which Tx beams may interfere with the Rx beam of BS 404; or BS 404 may send a Tx-Rx matrix with known interference probabilities to BS 406, which BS 406 may use to determine which Tx beams may have a high probability of interfering with the Rx beam of BS 404. BS 404 and BS 406 may also use the interfering communication 410 signal to configure a series of tests to have BS 406 send one or more measurement RS Tx beams 414 while BS 404 receives Rx beams 412 to determine which Tx beams 414 may interfere with BS 404's Rx beams 412 and to what extent.

[0085] In other words, for inter-gNB or inter-BS interference measurement, a measurement RS may be transmitted from an aggressor gNB (e.g., BS 406) while a victim gNB (e.g., BS 404) receives the transmission to measure actual interference. For example, BS 406 may be configured to transmit a measurement RS for each possible Tx-Rx beam pair between BS 406 and BS 404, respectively. For each Tx-Rx beam pair, BS 404 may be configured to measure 422 interference levels to determine which Tx beams may interfere with the Rx beam transmitted to BS 404 and / or to what extent. The interference level may be measured in a variety of ways, such as a percentage of inaccurate received Rx beams, a number of inaccurate data sets per time window (e.g., bits per second or bytes per minute), a Boolean measurement indicating whether an incoming Rx beam transmission has failed based on a measurable metric, a number of failed incoming packets over a period of time, or a number of sub-time windows within a larger time window where the received Rx beam has more than a threshold amount of inaccuracy (e.g., 16 seconds out of every minute, the received Rx beam has more than 10% inaccurate bits). BS 404 may send 424 at least some of the measurement results to BS 406.

[0086] The measurement results may be used to populate or update the values ​​of the Tx-Rx matrix indicating the interference level for each Tx-Rx combination (e.g., Tx of beam #1 and Rx of beam #1, Tx of beam #1 and Rx of beam #2, Tx of beam #1 and Rx of beam #3). Beams may be classified into frequency bands or channel sets, such as frequency bands marked in FR1 or FR2 (e.g., n1, n74). As an example, a victim BS (such as BS 404) may indicate to an aggressor BS (such as BS 406) that a high-interference DL beam (i.e., the Tx beam of the aggressor gNB, or Tx beam 414) is prohibited from being used to protect the RRC U symbols of the victim BS. Additionally or alternatively, the BS may indicate to a neighbor BS the probability of use of each DL / UL beam at the BS. In other words, the victim BS may indicate the probability of use of each UL beam and the aggressor BS may indicate the probability of use of each DL beam that may be used in a semi-static Tx / Rx opportunity or during a future time window. The probability of use may be a measure indicating the likelihood that a wireless device will use a beam. The likelihood may be expressed in a variety of ways, such as as a likelihood within a time window (e.g., 60% of the time in a five-minute time window) or as a percentage of the total beams used (e.g., 60% of all beams used).

[0087] For example, the usage probability of BS 406 sending Tx beam #1 may be 50%, while the usage probability of BS 404 receiving Rx beam #2 may be 80%. The usage probability may be calculated by, for example, analyzing the total number of beams sent and / or received by the wireless device within a time window (e.g., one hour, one day, one week, or one month). The usage probability may be measured as a measure of the number of beams of one type sent or received within the time window or the number of beam groups sent or received. The usage probability may be tracked by a wireless device (such as a UE or BS) and may be saved to a memory accessible to the wireless device. Such a wireless device may be configured to dynamically update the usage probability of various beams periodically (such as daily or weekly). The usage probability may also be calculated by a function of a time window (e.g., every Monday from 5:00 a.m. to 6:00 a.m., every federal holiday, or during each annual special event). The device may identify or save usage probabilities associated with thresholds, such as a usage probability that exceeds a usage threshold (e.g., exceeds 30% of a time window), a usage probability that is less than a usage threshold (e.g., less than 90% of a time window), or a usage probability that is between two thresholds (e.g., less than 90% of a time window and exceeds 30% of a time window).

[0088] The BS 404 may identify 432 a usage probability of each Rx beam of each Tx-Rx beam pair. Additionally or alternatively, the BS 404 may identify 432 a usage probability of each Rx beam of each Tx-Rx beam pair, wherein the Rx beam has a measured interference level that meets or exceeds a minimum threshold, such as 10% or greater than 100 bytes per minute or greater than 15% of the time window. Alternatively or additionally, the BS 406 may identify 434 a usage probability of each Tx beam of each Tx-Rx beam pair. Alternatively or additionally, the BS 406 may identify 434 a usage probability of each Tx beam of each Tx-Rx beam pair, wherein the Tx beam has caused a measured interference level of at least one Rx beam, wherein the measured interference level meets or exceeds the minimum threshold. The BS 404 may transmit 442 the usage probability of each Rx beam of each Tx-Rx beam pair to the BS 406 , and / or the BS 406 may transmit 442 the usage probability of each Tx beam of each Tx-Rx beam pair to the BS 404 .

[0089] If the usage probability of using a particular beam in a time window is high, the neighbor gNB or BS may be configured to avoid using an incompatible or high-interference beam in the opposite direction on resources or through negotiation between gNBs or BSs. For example, using the usage probability information, BS 406 can adjust 454 the beam scheduling for Tx beam 414 of BS 406 or Rx beam 412 of BS 404. In one aspect, the victim gNB may indicate that the usage probability of UL beam #2 in the time window is 80%, and the aggressor gNB may be configured to avoid using an incompatible DL beam #1 in the opposite direction that may cause high interference to UL beam #2 on the RRC U symbol of the victim gNB. In other words, with respect to the network connection flow chart 400, BS 404 may send 442 the usage probability to BS 406 that the usage probability of UL Rx beam 412 in the time window is 80%. Then, the BS 406 may adjust 454 the beam scheduling of the incompatible DL Tx beam 414 for the UL Rx beam 412 to avoid interfering with the high probability UL Rx beam 412. In another example, the victim gNB may indicate to the aggressor gNB that the probability of use of UL beam #2 in the time window is 80%, and the aggressor gNB may send a scheduling notification or suggestion signaling to the victim gNB to reduce the probability of use of UL beam #2 so that its DL beam #1 for URLLC service can be scheduled. In other words, with respect to the network connection flow chart 400, the BS 404 may send 442 the usage probability to the BS 406, and the probability of use of UL Rx beam 412 in the time window is 80%. BS 406 may be configured to recognize that it will transmit an incompatible DL Tx beam 414 during the same time window and may adjust 454 beam scheduling for BS 404 and send 462 scheduling notification or suggestion signaling to BS 404 to reduce the probability of use of the incompatible UL Rx beam 412 .

[0090] The threshold of the usage probability may be configured from the control unit (CU) so that the gNB or BS may be configured to reduce the likelihood of interference when the usage probability reaches or exceeds the usage threshold. For example, the BS 406 may send 442 an increased usage probability value for the BS 406 to use the Tx beam 414 interfering with the Rx beam 412. In response, the BS 404 may be configured to identify that the increased usage probability value exceeds the usage threshold, and in response, may adjust 452 the beam scheduling to use the Rx beam 412 that is not susceptible to the interference of the Tx beam 414. Alternatively, the BS 404 may be configured to send 462 a scheduling notification to the BS 406 to reduce the usage probability of the Tx beam 414 interfering with the Rx beam 412 in response to determining that the increased usage probability value exceeds the usage threshold. Such configuration may enable the BS 404 and / or BS 406 to adjust 452, 454 the beam scheduling, respectively, in response to determining that the usage probability reaches or exceeds the usage threshold, to avoid using incompatible or high-interference beams in the opposite direction on such resources.

[0091] BS 404 or BS 406 or both BS 404 and BS 406 may be configured to adjust 452, 454 beam scheduling based on the interference level measured for each Tx-Rx beam pair and the probability of use of the Rx beam, the probability of use of the Tx beam, or the probability of use of both beams of the Tx-Rx beam pair to minimize the probability of interference. For example, BS 404 may be configured to avoid scheduling the Rx beam during a time window in which it is known that BS 406 has a high probability of use of one or more Tx beams that interfere with the conflicting Rx beam (e.g., a probability of use that reaches or exceeds a usage threshold). Additionally or alternatively, BS 404 may be configured to send 462 a scheduling notification to BS 406 to avoid sending one or more conflicting Tx beams during a time window in which BS 404 has a high probability of use of receiving the conflicting Rx beam. Additionally or alternatively, BS 406 may be configured to avoid scheduling one or more conflicting Tx beams during a time window in which BS 404 may have a high probability of use for Rx interfered by one or more conflicting Tx beams. Additionally or alternatively, BS 406 may be configured to send 462 a scheduling notification to BS 404 to avoid sending the one or more conflicting Rx beams during a time window in which BS 406 may have a high probability of use for Tx that interferes with one or more conflicting Rx beams. Adjusting the probability of use of a beam downward may mean not using the beam at all (e.g., 0%), which may be appropriate when the probability of use of the conflicting beam is at or close to 100%. Adjusting the probability of use of a beam upward may mean using the beam (e.g., 100%) during the entire time period, which may be appropriate when there is no measured interference between the beam and any other beam with a non-zero probability of use in the Tx-Rx matrix of the measured interference level.

[0092] Figure 5 A network connection flow diagram 500 is shown illustrating an example of a BS 504 and a BS 506 that may have a Tx beam 514 that may interfere with an Rx beam 512. The network connection flow diagram 500 has a wireless device 502 (which may be a BS or a UE), a BS 504, a BS 506, and another wireless device 508 (which may also be a BS or a UE). Figure 4 , when BS 506 transmits Tx beam 514 to wireless device 508, Tx beam 514 may interfere with Rx beam 512 transmitted from wireless device 502 to BS 504. Network connection flow diagram 500 illustrates a use case for inter-gNB or inter-BS CLI, where interference probability information of gNB / BS beams may be transmitted via inter-gNB or inter-BS messaging to reduce potential interference between Tx-Rx beams.

[0093] In order to determine which possible Tx beams from BS 506 may interfere with the Rx beam transmitted to BS 504, BS 506 may be configured to communicate with BS 504 using interference communication 510 to determine which Tx beams from BS 506 may interfere with the Rx beam transmitted to BS 504. For example, BS 506 may send a list of Tx beams that BS 506 can transmit to BS 504, BS 504 may send a list of Rx beams that BS 504 can receive to BS 506, BS 504 may send a Tx-Rx matrix with known interference levels to BS 506 so that BS 506 knows which Tx beams may interfere with the Rx beams of BS 504; or BS 504 may send a Tx-Rx matrix with known interference probabilities to BS 506 so that BS 506 knows which Tx beams have a high probability of causing interference to the Rx beams of BS 504. BS 504 and BS 506 may also use the interference communication 510 signal to configure a series of tests to have BS 506 send one or more measurement RS Tx beams 514 while BS 504 receives Rx beams 512 to determine which Tx beams 514 may interfere with BS 504's Rx beams 512 and to what extent.

[0094] In other words, for inter-gNB or inter-BS interference measurement, a measurement RS may be transmitted from an aggressor gNB (e.g., BS 506) while a victim gNB (e.g., BS 504) receives the transmission to measure actual interference. For example, BS 406 may be configured to transmit a measurement RS for each possible Tx-Rx beam pair between BS 406 and BS 404, respectively. For each Tx-Rx beam pair, BS 504 may be configured to measure 522 the interference level to determine which Tx beams may interfere with the Rx beam transmitted to BS 504 and / or to what extent. The interference level may be measured in a variety of ways, such as a percentage of inaccurate received Rx beams, a number of inaccurate data sets per time window (e.g., bits per second or bytes per minute), a Boolean measurement indicating whether an incoming Rx beam transmission has failed based on a measurable metric, a number of failed incoming packets over a period of time, or a number of sub-time windows within a larger time window where the received Rx beam has more than a threshold amount of inaccuracy (e.g., 16 seconds out of every minute, the received Rx beam has more than 10% inaccurate bits). BS 504 may send 524 at least some of the measurement results to BS 506.

[0095] The measurement results may be used to populate or update the values ​​of the Tx-Rx matrix indicating the interference level for each Tx-Rx combination. Additionally or alternatively, the gNB or BS may indicate to the neighbor gNB or BS the interference probability of each DL / UL beam at the gNB or BS. For example, a victim gNB may be configured to indicate the interference probability that a DL beam from an aggressor gNB will interfere with a UL beam of the victim gNB, which beam may be used in a semi-static Tx / Rx scenario or during a future time window. The interference probability may be a measure indicating the likelihood that a Tx beam interferes with an Rx beam. The likelihood may be expressed in a variety of ways, such as as a likelihood within a time window (e.g., 60% of the time in a five minute time window) or as a percentage of the total beams used (e.g., 60% of all beams are interfered).

[0096] For example, the probability of interference for Rx beam #1 received by BS 504 during a time window in which BS 506 is transmitting Tx beam #3 may be 50%, while the probability of interference for Rx beam #3 received by BS 504 during a time window in which BS 506 is transmitting Tx beam #3 may be 80%. In another example, the victim gNB may indicate that 80% of the time during the time window, the UL beam is interfered with by the DL beam of one or more aggressor gNBs. The interference probability may be calculated in any suitable manner, such as by a function of a percentage of the time window (e.g., 50% of the time in a one minute period the Tx beam is interfered with by the Rx beam) or by a function of a percentage of data units (e.g., the Tx beam is interfered with by 50% of the received packets of the Rx beam). The device may be configured to identify or save the interference probability associated with the threshold. For example, an interference probability value that reaches or exceeds an interference threshold (e.g., greater than 50% of the time window), an interference probability value that reaches or is less than an interference threshold (e.g., less than 90% of the time window), or an interference probability value between two thresholds (e.g., greater than 50% of the time window and less than 90% of the time window). For example, the interference probability can be determined by analyzing the Rx beam during a time period in which the Tx beam is also being transmitted, and calculating how many received packets failed during the time period, or how many transmitted bits were inaccurate during the time period. The interference probability can be saved as a probability specific to a wireless device that transmits an RS Tx beam, specific to a wireless device that receives an Rx beam, specific to a pair of wireless devices having a Tx beam and an Rx beam, respectively, specific to the type of any of the aforementioned wireless devices, or can be saved as a probability specific to a beam type (e.g., n81 or n258). The wireless device may be configured to dynamically update the interference probability of a Tx-Rx pair periodically, such as daily or weekly, or in response to a trigger, such as when the location of the receiving wireless device or the transmitting wireless device moves at least a threshold distance.

[0097] The BS 504 may identify 532 an interference probability for each Rx beam of each Tx-Rx beam pair. Additionally or alternatively, the BS 504 may identify 532 an interference probability for each Rx beam of each Tx-Rx beam pair, where the Rx beam has a measured interference level that meets or exceeds a minimum threshold, such as 10% or greater than 100 bytes per minute or greater than 15% of the time window. Alternatively or additionally, the BS 506 may identify 534 an interference probability for each Tx beam of each Tx-Rx beam pair. Alternatively or additionally, the BS 506 may identify 534 an interference probability for each Tx beam of each Tx-Rx beam pair, where the Tx beam has caused a measured interference level that meets or exceeds a minimum threshold. The BS 504 may send 542 the interference probability of each Rx beam of each Tx-Rx beam pair to the BS 506, and / or the BS 506 may send 542 the interference probability of each Tx beam of each Tx-Rx beam pair to the BS 504. The BS 504 may generate a Tx-Rx matrix of interference probabilities for each Tx of the BS 506 that interferes with the Rx of the BS 504 with an interference level that reaches or exceeds the interference level threshold.

[0098] If the probability of interference for a particular beam is high (i.e., meets or exceeds an interference threshold) in a time window, the neighbor gNB or BS may be configured to avoid using an incompatible or high-interfering beam in the opposite direction on resources or through negotiation between gNBs or BSs. For example, using the interference probability information, BS 406 can adjust 454 the beam scheduling for Tx beam 414 of BS 406 or Rx beam 412 of BS 404. In one aspect, the neighbor aggressor gNB may be configured to avoid using such interfering DL beam in the opposite direction in future time windows. During the time window in which the victim gNB receives UL beam #2 and the aggressor gNB transmits DL beam #1, the victim gNB may indicate the interference probability (e.g., an interference probability of 80%) to the aggressor gNB. In response, the aggressor gNB may be configured to avoid using an incompatible DL beam #1 in the opposite direction on the RRC U symbols of the victim gNB that may be indicated as causing interference to UL beam #2 for a certain amount of time (e.g., 80% of the time). In other words, with respect to the network connection flowchart 500, the BS 504 may send 532 an interference probability (e.g., an interference probability of 80%) for the pair of Rx beam 512 and Tx beam 514 to the BS 506. In response, the BS 506 may adjust 554 the beam scheduling so that the Tx beam 514 does not overlap with the reception of the Rx beam 512. Alternatively, the aggressor gNB may send a scheduling notification or suggestion signaling to the victim gNB not to use UL beam #2 to receive data so that its DL beam #1 for URLLC service may be scheduled. In other words, with respect to the network connection flowchart 500, the BS 506 may adjust 554 the beam scheduling of the BS 504 and send 562 a scheduling notification or suggestion signaling to the BS 504 not to use the incompatible Rx beam 512 during a period of time so that the BS 506 may send its Tx beam 514 during the period of time without interfering with the incompatible Rx beam 512.

[0099] The threshold of the interference probability can be configured from the control unit (CU) so that the gNB or BS can be configured to trigger actions to reduce the possibility of interference when the interference probability reaches or exceeds the interference threshold.

[0100] BS 504 or BS 506 or both BS 504 and BS 506 may be configured to adjust 552, 554 the beam scheduling based on the interference level measured for each Tx-Rx beam pair and the interference probability of the Rx beam, the interference probability of the Tx beam, or the interference probability of both beams of the Tx-Rx beam pair to minimize the interference probability. For example, BS 504 may be configured to avoid scheduling the conflicting Rx beam during a time window in which it is known that BS 506 is sending a Tx with a high interference probability that interferes with the conflicting Rx beam. Additionally or alternatively, BS 504 may be configured to send 562 a scheduling notification to BS 506 to avoid sending the conflicting Tx beam during a time window in which BS 504 is sending an Rx beam with a high interference probability for the conflicting Tx beam. Additionally or alternatively, BS 506 may be configured to avoid scheduling a conflicting Tx beam during a time window in which BS 504 may be using an Rx beam with a high probability of interference for the conflicting Tx beam to receive data. Additionally or alternatively, BS 506 may be configured to send 562 a scheduling notification to BS 504 to avoid sending the conflicting Rx beam during a time window in which BS 506 may be scheduled to send a Tx with a high probability of interference for the conflicting Rx beam. Adjusting the probability of use of a beam downward may mean not using the beam at all (e.g., 0% probability of use), which may be appropriate when the probability of interference of the conflicting beam is at or near 100%. Adjusting the probability of use of a beam upward may mean using the beam during the entire time period (e.g., 100% probability of use), which may be appropriate when there is no measured interference between the beam and any other beam in the Tx-Rx matrix of the measured interference level.

[0101] Figure 6 A network connection flow diagram 600 illustrating an example of a UE 602 and a BS 606 that may have a Tx beam 614 that may interfere with an Rx beam 612 is shown. The network connection flow diagram 600 has the UE 602, the BS 604, the BS 606, and a wireless device 608 that may be a BS or a UE. When the BS 606 transmits the Tx beam 614 to the wireless device 608, the Tx beam 614 may interfere with the Rx beam 612 transmitted from the BS 604 to the UE 602. The network connection flow diagram 600 illustrates a use case for neighbor BS to serving UE interference, where usage probability assistance information of BS beams may be provided via inter-BS messaging to reduce potential interference between Tx-Rx beams.

[0102] To determine which possible Tx beams from the BS 606 may interfere with the Rx beam transmitted to the UE 602, the BS 606 may be configured to communicate with the BS 604 using interference communication 610. For example, the BS 606 may send to the BS 604 a list of Tx beams that the BS 606 can transmit to the wireless device 608. The BS 604 may send to the BS 606 a list of Rx beams that the UE 602 can receive from the BS 604. The BS 604 may send to the BS 606 a Tx-Rx matrix of known interference levels for the UE 602 (or a device type similar to the device type of the UE 602) so that the BS 606 knows which Tx beams may interfere with the Rx beam of the UE 602. In addition, BS 604 may send a Tx-Rx matrix of known interference probabilities to BS 606 so that BS 606 knows which Tx beams have a high probability of interfering with the Rx beam of UE 602 (or a device type similar to the device type of UE 602). BS 604 and BS 606 may also use the interference communication 610 signal to configure a series of tests to have BS 606 send one or more measurement RS Tx beams 614 while UE 602 receives Rx beams 612 to determine which Tx beams 614 may interfere with the Rx beam 612 of UE 602 and to what extent.

[0103] Although a measurement RS can be transmitted from the aggressor gNB to the victim UE to measure the actual interference, Figure 4Similar to BS 404 and BS 406 in the UE 602, a Tx-Rx matrix of known interference levels or known interference probabilities for similar UEs (e.g., UEs of the same brand and model) may be used to estimate which Tx beams from BS 606 may interfere with the Rx beams transmitted to UE 602. Additionally or alternatively, a test UE 602 may be used to generate such a Tx-Rx matrix, which may be configured to analyze how much interference various Rx beams 612 may receive when various Tx beams 614 are transmitted from BS 606. BS 606 may be configured to transmit measurement RSs for each Tx of a known Tx-Rx beam pair between BS 606 and UE 602. For each Tx-Rx beam pair, UE 602 may be configured to measure 622 interference levels to determine which Tx beams interfere with the Rx beams transmitted to UE 602. The interference level may be measured in a variety of ways, such as the percentage of inaccurate received Rx beams, the number of inaccurate data sets per time window (e.g., bits per second or bytes per minute), a Boolean measurement indicating whether an incoming Rx beam transmission has failed, the number of failed incoming packets over a period of time, or the number of sub-time windows within a larger time window where the received Rx beam has more than a threshold number of inaccuracies (e.g., 16 seconds per minute where the received Rx beam has more than 10% inaccurate bits). The UE 602 may send 623 at least some of the measurement results to the BS 604, which may send 625 at least some of the measurement results to the BS 606. As described above, the measurement results may be used to populate a Tx-Rx matrix indicating the interference level for each Tx-Rx combination.

[0104] The BS 604 may identify 632 a usage probability of each Rx beam of each Tx-Rx beam pair. Additionally or alternatively, the BS 604 may identify 632 a usage probability of each Rx beam of each Tx-Rx beam pair, where the Rx beam has a measured interference level that meets or exceeds a threshold interference measurement, such as 10% or greater than 100 bytes per minute or greater than 15% of the time window. Alternatively or additionally, the BS 606 may identify 634 a usage probability of each Tx beam of each Tx-Rx beam pair. Alternatively or additionally, the BS 606 may identify 634 a usage probability of each Tx beam of each Tx-Rx beam pair, where the Tx beam has caused a measured interference level that meets or exceeds a threshold interference measurement. The BS 604 may transmit 642 the usage probability of each Rx beam of the known Tx-Rx beam pair to the BS 606 , and / or the BS 606 may transmit 642 the usage probability of each Tx beam of the known Tx-Rx beam pair to the BS 604 .

[0105] If the neighbor gNB or BS has a high usage probability (e.g., 80% usage probability) of using a particular DL beam in a time window, the serving gNB or BS may avoid scheduling an incompatible DL beam (i.e., a DL beam that receives high interference from the particular DL beam) for its served UE during the same time window. For example, the BS 606 may identify 634 the usage probability (e.g., 80% usage probability) of using the Tx beam 614 within the time window and may send 642 the probability to the BS 604. Then, in response, the BS 604 may avoid scheduling the Rx beam 612 to the UE 602 that receives high interference from the Tx beam 614 during the same time window. The BS 604 or BS 606 can determine whether the particular Rx beam 612 of the UE 602 is likely to be interfered with by the Tx beam 614 of the BS 606 based on the SSB report or layer 1 reference signal received power (L1-RSRP) generated by the BS 604. Such a report may be sent by BS 604 to BS 606 so that BS 606 may adjust 654 the beam scheduling for UE 602, BS 606, or BS 604. Additionally or alternatively, if the probability of use of a particular DL beam of a neighbor gNB or BS is high (e.g., 80% probability of use) during the time window, the serving gNB or BS may be configured to send a suggestion signal to the neighbor gNB or BS to reduce the probability of use of the conflicting beam. Such a situation may be triggered to occur in response to the serving gNB or base station being configured to send a URLLC message. For example, BS 606 may identify 634 the probability of use of Tx beam 614 during the time window. BS 606 may send 642 the probability to BS 604. The BS 604 may be configured to send a URLLC message to the UE 602 using the Rx beam 612 during the time window, knowing that the Rx beam is the Rx beam interfered by the Tx beam 614 (i.e., the measured interference level reaches or exceeds the threshold interference level). The BS 604 may then adjust 652 the beam scheduling to cause the BS 606 to transmit the Tx beam 614 during a different time window, and may send 662 such a scheduling notification to the BS 606 to change its transmission of the Tx beam 614 to a different time window.

[0106] BS 604 or BS 606 or both BS 604 and BS 606 may be configured to adjust 652, 654 beam scheduling based on the measured 622 interference level of each Tx-Rx beam pair and the probability of use of the Rx beam, the probability of use of the Tx beam, or the probability of use of both beams of the Tx-Rx beam pair to minimize the probability of interference. For example, BS 604 may be configured to avoid scheduling the Rx beam during a time window when it is known that BS 606 has a high probability of use of one or more Tx beams that interfere with the conflicting Rx beam (e.g., a probability of use that reaches or exceeds a usage threshold). Additionally or alternatively, BS 604 may be configured to send 662 a scheduling notification to BS 606 to avoid sending one or more conflicting Tx beams during a time window when BS 604 has a high probability of use of sending the conflicting Rx beam. Additionally or alternatively, the BS 606 may be configured to avoid scheduling the one or more conflicting Tx beams 614 during a time window in which the BS 604 may have a high probability of using the Rx beam 612 to the UE 602 interfered by the one or more conflicting Tx beams 614. Additionally or alternatively, the BS 606 may be configured to send 662 a scheduling notification to the BS 604 during a time window in which the BS 606 may have a high probability of using the Tx beam 614 for interfering with the one or more conflicting Rx beams 612 sent to the UE 602 to avoid sending the one or more conflicting Rx beams to the UE 602. Additionally or alternatively, the BS 604 and the BS 606 may exchange one or more beam schedules by sending 662 a scheduling notification including the beam schedules. Adjusting the probability of use of a beam downward may mean not using the beam at all (e.g., 0% probability of use), which may be appropriate when the probability of use of the conflicting beam is at or near 100%. Adjusting the probability of use of a beam upward may mean using the beam during the entire time period (e.g., 100% probability of use), which may be appropriate if there is no measured interference between the beam and any other beam with a non-zero probability of use in the Tx-Rx matrix of the measured interference level.

[0107] Figure 7 A network connection flow diagram 700 is shown illustrating an example of a UE 702 and a BS 706 that may have a Tx beam 714 that may interfere with an Rx beam 712. The network connection flow diagram 700 has the UE 702, the BS 704, the BS 706, and a wireless device 708 that may be a BS or a UE. Figure 6, when BS 706 transmits Tx beam 714 to wireless device 708, Tx beam 714 may interfere with Rx beam 712 transmitted from BS 704 to UE 702. Network connection flow diagram 700 illustrates a use case for neighbor gNB to serving UE interference, where interference probability information of gNB beams may be provided via inter-gNB messaging.

[0108] Similar to Figure 6 In order to determine which possible Tx beams from BS 706 may interfere with the Rx beam transmitted to UE 702, BS 706 can be configured to communicate with BS 704 using interference communication 710. For example, BS 706 may send a list of Tx beams that BS 706 is capable of transmitting to BS 704, BS 704 may send a list of Rx beams that UE 702 is capable of receiving to BS 706, BS 704 may send a Tx-Rx matrix of known interference levels of UE 702 (or a device type similar to the device type of UE 702) to BS 706 so that BS 706 knows which Tx beams may interfere with the Rx beams of UE 702, and / or BS 704 may send a Tx-Rx matrix of known interference probabilities to BS 706 so that BS 706 knows which Tx beams have a high probability of causing interference to the Rx beams of UE 702 (or a device type similar to the device type of UE 702). BS 704 and BS 706 may also use the interference communication 710 signal to configure a series of tests to have BS 706 transmit one or more measurement RSTx beams 714 while UE 702 receives Rx beams 712 to determine which Tx beams 714 may interfere with UE 702's Rx beam 712 and to what extent.

[0109] Although the measurement RS can be transmitted from the aggressor gNB and the victim UE receives the signal to measure the actual interference, Figure 4Similar to BS 404 and BS 406 in the UE 702, a Tx-Rx matrix of known interference levels or known interference probabilities for similar UEs (e.g., UEs of the same brand and model) may be used to estimate which Tx beams from BS 706 may interfere with the Rx beams transmitted to UE 702. Additionally or alternatively, a test UE 702 may be used to generate such a Tx-Rx matrix, which may be configured to analyze how much interference various Rx beams 712 may receive when various Tx beams 714 are transmitted from BS 706. BS 706 may be configured to transmit a measurement RS for each Tx of a known Tx-Rx beam pair between BS 706 and UE 702. For each Tx-Rx beam pair, UE 702 may be configured to measure 722 interference levels to determine which Tx beams interfere with the Rx beams transmitted to UE 702. As described above, the interference level may be measured in a variety of ways. UE 702 may send 723 at least some of the measurement results to BS 704, which may send 725 at least some of the measurement results to BS 706. As described above, the measurement results may be used to populate a Tx-Rx matrix indicating interference levels for each Tx-Rx combination.

[0110] The BS 704 may identify 732 an interference probability for each Rx beam of each Tx-Rx beam pair. Additionally or alternatively, the BS 704 may identify 732 an interference probability for each Rx beam of each Tx-Rx beam pair, where the Rx beam has a measured interference level that meets or exceeds a minimum threshold, such as at least 10% or at least 100 bytes per minute or at least 15% of the time window. Alternatively or additionally, the BS 706 may identify 734 an interference probability for each Tx beam of each Tx-Rx beam pair. Alternatively or additionally, the BS 706 may identify 734 an interference probability for each Tx beam of each Tx-Rx beam pair, where the Tx beam has caused a measured interference level that meets or exceeds the minimum threshold. The BS 704 may transmit 742 the interference probability of each Rx beam of each Tx-Rx beam pair to the BS 706 , and / or the BS 706 may transmit 742 the interference probability of each Tx beam of each Tx-Rx beam pair to the BS 704 .

[0111] If the probability of interference for a particular DL beam of a particular gNB or BS is high (e.g., meets or exceeds an interference level threshold) for a particular DL beam of a served UE, the serving gNB or BS may be configured, in response, to avoid scheduling the served UE that receives high interference from the DL beam of the particular neighbor gNB or BS during the time window in which the particular DL beam is transmitted. For example, when the BS 704 transmits the Rx beam 712 to the UE 702, the BS 706 may identify 734 that the probability of interference for the particular Tx beam 714 is above 80% and may transmit 742 the probability to the BS 704. Additionally or alternatively, when the BS 706 transmits the Tx beam 714 to the wireless device 708, the BS 704 may identify 732 that the probability of interference for the particular Rx beam 712 is above 80%. In response, BS 704 may be configured to adjust 752 the beam scheduling for Rx beam 712 to avoid transmitting Rx beam 712 to UE 702 during the time window in which BS 706 is transmitting the interfering Tx beam 714 .

[0112] The BS 704 or BS 706 can determine whether the Rx beam 712 of the UE 702 is interfered by the Tx beam 714 of the BS 706 based on the SSB report or layer 1 reference signal received power (L1-RSRP) generated by the BS 704. Such a report can be sent by the BS 704 to the BS 706 so that in response, the BS 706 can adjust 754 the beam scheduling for the UE 702 or BS 706. Additionally or alternatively, if the interference probability of a particular DL beam of a particular gNB or BS is high (e.g., reaches or exceeds an interference level threshold) for a particular DL beam of the serving UE, the serving gNB or BS can be configured to, in response, send a suggestion signal to a neighbor gNB or BS to request that the particular DL beam not be transmitted during a given time window. Such a situation can be triggered to occur in response to the serving gNB or base station being configured to send a URLLC message. For example, when the BS 704 transmits the Rx beam 712 to the UE 702, the BS 706 may identify 734 that the probability of interference for the specific Tx beam 714 is higher than 80%, and may send 742 the probability to the BS 704. Additionally or alternatively, when the BS 706 transmits the Tx beam 714 to the wireless device 708, the BS 704 may identify 732 that the probability of interference for the specific Rx beam 712 is higher than 80%. In response, the BS 704 may be configured to adjust 752 the beam scheduling so that the BS 706 transmits the interfering Tx beam 714 during a different time window, and may send 762 such a scheduling notification to the BS 706 to change its transmission of the Tx beam 714 to a different time window so as not to overlap with the time window of the Rx beam 712.

[0113] BS 704 or BS 706 or both BS 704 and BS 706 may be configured to adjust 752, 754 the beam scheduling based on the interference level measured for each Tx-Rx beam pair and the interference probability of the Rx beam, the interference probability of the Tx beam, or the interference probability of the two beams of the Tx-Rx beam pair to minimize the interference probability. For example, BS 704 may be configured to avoid scheduling the Rx beam during a time window in which it is known that BS 706 has a high probability of using one or more Tx beams that interfere with the conflicting Rx beam. Additionally or alternatively, BS 704 may be configured to send 762 a scheduling notification to BS 706 to avoid sending one or more conflicting Tx beams during a time window in which BS 704 has a high probability of using the conflicting Rx beam to UE 702. Additionally or alternatively, the BS 706 may be configured to avoid scheduling the one or more conflicting Tx beams 714 during a time window in which the BS 704 may have a high probability of using the Rx beam 712 to transmit to the UE 702 interfered by the one or more conflicting Tx beams 714. Additionally or alternatively, the BS 706 may be configured to send 762 a scheduling notification to the BS 704 during a time window in which the BS 706 may have a high probability of using the Tx beams that interfere with the one or more conflicting Rx beams transmitted to the UE 702 to avoid transmitting the one or more conflicting Rx beams to the UE 702. Adjusting the probability of use of a beam downward may mean not using the beam at all (e.g., 0% probability of use), which may be appropriate when the probability of use of the conflicting beam is at or near 100%. Adjusting the probability of use of a beam upward may mean using the beam during the entire time period (e.g., 100% probability of use), which may be appropriate if there is no measured interference between the beam and any other beam with a non-zero probability of use in the Tx-Rx matrix of the measured interference level.

[0114] Figure 8 A network connection flow diagram 800 illustrating an example of a UE 802 and a UE 808 that may have a Tx beam 814 that may interfere with an Rx beam 812 is shown. The network connection flow diagram 800 has the UE 802, the BS 804, the BS 806, and the UE 808. When the UE 808 transmits the Tx beam 814 to the BS 806, the Tx beam 814 may interfere with the Rx beam 812 transmitted from the BS 804 to the UE 802. The devices may be configured to perform inter-UE CLI mitigation to minimize possible interference between the Tx beam 814 from the UE 808 and the Rx beam 812 to the UE 802. In other words, the network connection flow diagram 800 illustrates a use case for inter-UE CLI mitigation. The UE UL beam ID may be used to indicate the probability of use of UE beam assist information from the UE to the gNB.

[0115] In order to determine which possible Tx beams from UE 808 may interfere with the Rx beam transmitted to UE 802 , BS 806 may be configured to communicate with BS 804 using interference communication 810 . For example, BS 806 may send a list of Tx beams that UE 808 can send to BS 806 to BS 804, BS 804 may send a list of Rx beams that UE 802 can receive to BS 806, BS 804 may send a Tx-Rx matrix of known interference levels of UE 802 (or a device type similar to the device type of UE 802) to BS 806 so that BS 806 knows which Tx beams may interfere with the Rx beams of UE 802, and / or BS 804 may send a Tx-Rx matrix of known interference probabilities to BS 806 so that BS 806 knows which Tx beams have a high probability of causing interference to the Rx beams of UE 802 (or a device type similar to the device type of UE 802). BS 804 and BS 806 may also use the interfering communication 810 signal to configure a series of tests to cause UE 808 to send one or more measurement RS Tx beams 814 while UE 802 receives Rx beam 812 to determine which Tx beams 814 may interfere with UE 802's Rx beam 812 and to what extent.

[0116] Although the measurement signal can be transmitted from the offending UE while the victim UE receives the signal for measuring the actual interference, Figure 4 Similar to BS 404 and BS 406 in FIG. 8 , a Tx-Rx matrix with known interference levels or known interference probabilities for similar UEs (e.g., UEs of the same brand and model) may be used to estimate which Tx beams from UE 808 may interfere with the Rx beams transmitted to UE 802. Additionally or alternatively, a test UE 802 may be used to generate such a Tx-Rx matrix, which may be configured to analyze how much interference various Rx beams 812 may receive when various Tx beams 814 are transmitted from UE 808. For each possible Tx-Rx beam pair, UE 802 may be configured to measure 822 the interference level to determine which Tx beams 814 interfere with the Rx beams 812 transmitted to UE 802. As explained above, the interference level may be measured in a variety of ways. UE 802 may send 823 at least some of the measurement results to BS 804, which may send 825 at least some of the measurement results to BS 806. As described above, the measurement results may be used to populate a Tx-Rx matrix indicating interference levels for each Tx-Rx combination.

[0117] The BS 804 may identify 832 the usage probability of each Rx beam of each Tx-Rx beam pair. Additionally or alternatively, the BS 806 may identify 834 the usage probability of each Tx beam of each Tx-Rx beam pair. The exact UE UL beam ID usage probability of the UE 808 may be reported or sent 842 to the BS 804 or reported or sent to the BS 806. This may avoid inter-UE CLI. In other words, the UE 808 may send the derived UL beam ID usage probability to the BS 806. Additionally or alternatively, the BS 806 may send the derived UL beam ID usage probability of the UE 808 to the BS 804. For example, the UE 808 may report or send 842 the usage probability of the spatial filter corresponding to the SRS resource ID mapped to a given beam indication DL RS. Additionally or alternatively, UE 808 may report or send 842 a probability of use of a spatial filter corresponding to an SRS resource ID, regardless of which DL RS the SRS resource ID is mapped to. Alternatively or additionally, BS 806 may report or send 842 one or both of the above-mentioned usage probabilities. Such usage probabilities may be reported or sent 842 as a function of a previous time window (e.g., in milliseconds). Based on such information, BS 804 and / or BS 806 may adjust 854 a beam scheduling for UE 808 and / or UE 802 that produces a low CLI for its neighbor UE 802 in the time window.

[0118] If the probability of use of a UE of a neighbor gNB or BS using a particular UL beam in a time window is high (e.g., 80% probability of use), the serving gNB or BS may be configured to avoid scheduling an incompatible DL beam (i.e., a DL beam that receives high interference from the particular UL beam) for its served UE during the same time window. For example, the BS 806 may identify 834 the probability of use of a Tx beam 814 to be transmitted by the UE 808 in the time window as being at or above 80%, and may send 842 the probability to the BS 804. In response, the BS 804 may be configured to adjust 852 the beam scheduling to transmit the incompatible Rx beam 812 (i.e., a beam that receives at least a threshold level of interference from the Tx beam 814) in a different time window. Additionally or alternatively, if the probability of use of a UE of a neighbor gNB or BS using a particular UL beam in a time window is high, the serving gNB or BS may be configured to send a suggestion signal to the neighbor gNB or BS to request that the UL beam be scheduled during a different time window. Such a situation may be triggered to occur in response to the serving gNB or base station being configured to send a URLLC message. For example, the BS 806 may identify 834 the probability of use of the Tx beam 814 to be sent by the UE 808 in the time window as being at or above 80%, and may send 842 the probability to the BS 804. The BS 804 may also be configured to send a URLLC message to the UE 802 in the form of an Rx beam 812 in the same time window. In response, the BS 804 may be configured to adjust 852 the beam scheduling to send the incompatible Tx beam 814 during a different time window. The BS 804 may then send 862 a scheduling notification of the new beam scheduling to the BS 806 to change the time at which the UE 808 sends the Tx beam 814, or to reduce the probability of use of sending the Tx beam 814 during the time window to be at or below a threshold.

[0119] BS 804 or BS 806 or both BS 804 and BS 806 may be configured to adjust 852, 854 beam scheduling based on the measured interference level of each Tx-Rx beam pair and the probability of use of the Rx beam, the probability of use of the Tx beam, or the probability of use of both beams of the Tx-Rx beam pair to minimize the probability of interference. For example, BS 804 may be configured to avoid scheduling the Rx beam during a time window in which it is known that UE 808 has a high probability of use of one or more Tx beams that interfere with the conflicting Rx beam. Additionally or alternatively, BS 804 may be configured to send 862 a scheduling notification to BS 806 during a time window in which BS 804 has a high probability of use of the conflicting Rx beam to UE 802 to avoid scheduling one or more conflicting Tx beams to be sent from UE 808. Additionally or alternatively, the BS 806 may be configured to avoid scheduling the one or more conflicting Tx beams 814 from the UE 808 during a time window in which the BS 804 may have a high probability of using the Rx beam 812 to the UE 802 interfered by the one or more conflicting Tx beams 814. Additionally or alternatively, the BS 806 may be configured to send 862 a scheduling notification to the BS 804 during a time window in which the UE 808 may have a high probability of using the Tx beam 812 for interfering with the one or more conflicting Rx beams sent to the UE 802, so as to avoid sending the one or more conflicting Rx beams to the UE 802. Adjusting the probability of use of a beam downward may mean not using the beam at all (e.g., 0% probability of use), which may be appropriate when the probability of use of the conflicting beam is at or near 100%. Adjusting the probability of use of a beam upward may mean using the beam during the entire time period (e.g., 100% probability of use), which may be appropriate if there is no measured interference between the beam and any other beam with a non-zero probability of use in the Tx-Rx matrix of the measured interference level.

[0120] In one aspect, UE 808 may transmit a Tx beam 814 that interferes with an Rx beam 812 received by UE 802, where both UE 808 and UE 802 may communicate with the same BS in FD mode. For example, both BS 804 and BS 806 may be represented by BS 805 in FD mode, where UE 808 may transmit Tx beam 814 to BS 805, and BS 805 transmits Rx beam 812 to UE 802. In some instances, the functions of BS 804 and BS 806 may be performed by a single BS 805.

[0121] For example, the BS 805 may generate a Tx-Rx matrix of known interference levels for the Tx beam 814 of the UE 808 that may interfere with the Tx beam 812 of the UE 802, or may schedule a series of tests to have the UE 808 transmit one or more measurement RS Tx beams 814 while the UE 802 receives the Rx beam 812 to determine which Tx beams 814 may interfere with the Rx beam 812 of the UE 802 and to what extent. The UE 802 may measure 822 the interference level of any Rx beam 812 that is interfered by the Tx beam 814 transmitted from the UE 808. The UE 802 may transmit 823 one or more interference levels to the BS 805, which may determine which Rx beams 812 are severely interfered by the Tx beam 814 of the UE 808. The BS 805 may identify 832 the usage probability of each Rx beam of each Tx-Rx beam pair, and may identify 834 the usage probability of each Tx beam of each Tx-Rx beam pair that can be used for scheduling. Additionally or alternatively, the BS 805 may simply adjust 852, 854 the beam scheduling for both the UE 808 and the UE 802 to minimize the interference of the Tx beam 814 of the UE 808 with the Rx beam 812 of the UE 802. Since the BS 805 is able to schedule such beams for both the UE 802 and the UE 808, the BS 805 is able to quickly and efficiently adjust 852, 854 the beam scheduling for the UE 802 and the UE 808.

[0122] Fig. 9 A network connection flow diagram 900 illustrating an example of a UE 902 and a UE 908 that may have a Tx beam 914 that may interfere with an Rx beam 912 is shown. The network connection flow diagram 900 has the UE 902, the BS 904, the BS 906, and the UE 908. When the UE 908 transmits a Tx beam 914 to the BS 906, the Tx beam 914 may interfere with the Rx beam 912 transmitted from the BS 904 to the UE 902. The devices may be configured to perform inter-UE CLI mitigation to minimize possible interference between the Tx beam 914 from the UE 908 and the Rx beam 912 to the UE 902. In other words, the network connection flow diagram 900 illustrates a use case for inter-UE CLI mitigation.

[0123] In order to determine which possible Tx beams from UE 908 may interfere with the Rx beam transmitted to UE 902, BS 906 may be configured to communicate with BS 904 using interference communication 910. For example, BS 906 may send a list of Tx beams that UE 908 can send to BS 906 to BS 904, BS 904 may send a list of Rx beams that UE 902 can receive to BS 906, BS 904 may send a Tx-Rx matrix of known interference levels of UE 902 (or a device type similar to the device type of UE 902) to BS 906 so that BS 906 knows which Tx beams may interfere with the Rx beams of UE 902, or BS 904 may send a Tx-Rx matrix of known interference probabilities to BS 906 so that BS 906 knows which Tx beams have a high probability of causing interference to the Rx beams of UE 902 (or a device type similar to the device type of UE 902). BS 904 and BS 906 may also use the interfering communication 910 signal to configure a series of tests to cause UE 908 to send one or more measurement RS Tx beams 914 while UE 902 receives Rx beams 912 to determine which Tx beams 914 may interfere with UE 902's Rx beam 912 and to what extent.

[0124] Although the measurement signal can be transmitted from the offending UE while the victim UE receives the signal for measuring the actual interference, Figure 8 808 and UE 802 in the test UE 902 may use more Tx-Rx matrices of known interference levels or known interference probabilities for similar UEs (e.g., UEs of the same brand and model) to estimate which Tx beams from UE 908 may interfere with the Rx beams transmitted to UE 902. Additionally or alternatively, the test UE 902 may be used to generate such a Tx-Rx matrix, which may be configured to analyze how much interference various Rx beams 912 may receive when various Tx beams 914 are transmitted from UE 908. For each Tx-Rx beam pair, UE 902 may be configured to measure 922 interference levels to determine which Tx beams interfere with the Rx beams transmitted to UE 902. As explained above, the interference levels may be measured in a variety of ways. UE 902 may send 923 at least some of the measurement results to BS 904, which may send 925 at least some of the measurement results to BS 906. As described above, the measurement results may be used to populate a Tx-Rx matrix indicating the interference level for each Tx-Rx combination.

[0125] The BS 904 may identify 932 an interference probability for each Rx beam of each Tx-Rx beam pair. Additionally or alternatively, the BS 906 may identify 934 an interference probability for each Tx beam of each Tx-Rx beam pair. For example, the interference probability for each Tx-Rx beam pair may be derived by analyzing data from the constructed Tx-Rx matrix, or by retrieving such data from a database having pre-constructed Tx-Rx matrices for UEs of the same type as the UE 902 and the UE 908, respectively. The identified interference probability may be used to minimize interference between the Tx beam of the UE 908 and the Rx beam of the UE 902.

[0126] If the interference probability of a particular UL beam of a neighbor UE to a DL beam of a serving UE is high (e.g., at or above an interference probability threshold), the serving gNB or BS may be configured to avoid scheduling an incompatible DL beam for its serving UE during the same time window. For example, when the BS 904 transmits an Rx beam 912 to the UE 902, the BS 906 may identify 934 that the interference probability of the Tx beam 914 to be transmitted by the UE 908 is at or above 80%, and may transmit 942 the probability to the BS 904. Additionally or alternatively, when the UE 908 transmits the Tx beam 914, the BS 904 may identify 932 that the interference probability of the Rx beam 912 received by the UE 902 is at or above 80%. In response, the BS 904 may be configured to adjust 952 the beam scheduling to transmit the incompatible Rx beam 912 in a different time window. Additionally or alternatively, if a particular UL beam of a neighbor UE has a high probability of interference with a DL beam of a serving UE (e.g., at or above an interference probability threshold), the serving gNB or BS may be configured to send a suggestion signal to the neighbor gNB or BS to request that the UL beam be scheduled during a different time window. Such a situation may be triggered to occur in response to the serving gNB or base station being configured to send a URLLC message. For example, when the BS 904 sends an Rx beam 912 to the UE 902, the BS 906 may identify 934 that the interference probability of the Tx beam 914 to be sent by the UE 908 is at or above 80%, and may send 942 the probability to the BS 904. Additionally or alternatively, when the UE 908 sends a Tx beam 914, the BS 904 may identify 932 that the interference probability of the Rx beam 912 received by the UE 902 is at or above 80%. The BS 904 may also be configured to send a URLLC message to the UE 902 in the form of an Rx beam 912 in the same time window as the UE 908 is configured to send the Tx beam 914. In response, the BS 904 may be configured to adjust 952 the beam scheduling to send the incompatible Tx beam 914 during a different time window. The BS 904 may then send 962 a scheduling notification of the new beam scheduling to the BS 906 to change the time at which the UE 908 sends the Tx beam 914, or to reduce the usage probability of sending the Tx beam 914 during the time window to be at or below a threshold.

[0127] BS 904 or BS 906 or both BS 904 and BS 906 may be configured to adjust 952, 954 beam scheduling based on the interference level measured for each Tx-Rx beam pair and the interference probability of the Rx beam, the interference probability of the Tx beam, or the interference probability of the two beams of the Tx-Rx beam pair to minimize the interference probability. For example, BS 904 may be configured to avoid scheduling the Rx beam during a time window in which it is known that UE 908 has a high probability of using one or more Tx beams that interfere with the conflicting Rx beam. Additionally or alternatively, BS 904 may be configured to send 962 a scheduling notification to BS 906 during a time window in which BS 904 has a high probability of using the conflicting Rx beam to UE 902 to avoid scheduling one or more conflicting Tx beams to be sent from UE 908. Additionally or alternatively, the BS 906 may be configured to avoid scheduling the one or more conflicting Tx beams 914 from the UE 908 during a time window in which the BS 904 may have a high probability of using the Rx beam 912 to the UE 902 interfered by the one or more conflicting Tx beams 914. Additionally or alternatively, the BS 906 may be configured to send 962 a scheduling notification to the BS 904 during a time window in which the UE 908 may have a high probability of using the Tx beam 912 for interfering with the one or more conflicting Rx beams sent to the UE 902, so as to avoid sending the one or more conflicting Rx beams to the UE 902. Adjusting the probability of use of a beam downward may mean not using the beam at all (e.g., 0% probability of use), which may be appropriate when the probability of use of the conflicting beam is at or near 100%. Adjusting the probability of use of a beam upward may mean using the beam during the entire time period (e.g., 100% probability of use), which may be appropriate if there is no measured interference between the beam and any other beam with a non-zero probability of use in the Tx-Rx matrix of the measured interference level.

[0128] In one aspect, UE 908 may transmit a Tx beam 914 that interferes with an Rx beam 912 received by UE 902, where both UE 908 and UE 902 may communicate with the same BS in FD mode. For example, both BS 904 and BS 906 may be represented by BS 905 in FD mode, where UE 908 may transmit Tx beam 914 to BS 905, and BS 905 transmits Rx beam 912 to UE 902. The functions of BS 904 and BS 906 may be performed by a single BS 905.

[0129] For example, the BS 905 may generate a Tx-Rx matrix of known interference levels for the Tx beam 914 of the UE 908 that may interfere with the Tx beam 912 of the UE 902, or may schedule a series of tests to have the UE 908 transmit one or more measurement RS Tx beams 914 while the UE 902 receives the Rx beam 912 to determine which Tx beams 914 may interfere with the Rx beam 912 of the UE 902 and to what extent. The UE 902 may measure 922 the interference level of any Rx beam 912 that is interfered by the Tx beam 914 transmitted from the UE 908. The UE 902 may transmit 923 the one or more interference levels to the BS 905, which may determine which Rx beams 912 are severely interfered by the Tx beam 914 of the UE 908. The BS 905 may identify 932 the interference probability of each Rx beam of each Tx-Rx beam pair, and / or may identify 934 the interference probability of each Tx beam of each Tx-Rx beam pair that can be used for scheduling. Additionally or alternatively, the BS 905 may simply adjust 952, 954 the beam scheduling for both the UE 908 and the UE 902 to minimize the interference of the Tx beam 914 of the UE 908 to the Rx beam 912 of the UE 902. Such scheduling may be based on the interference probability identified for at least one Tx-Rx beam pair in the Tx-Rx beam pair. Since the BS 905 is able to schedule such beams for both the UE 902 and the UE 908, the BS 905 is able to quickly and efficiently adjust 952, 954 the beam scheduling for the UE 902 and the UE 908.

[0130] Fig.10 A network connection flow diagram 1000 is shown illustrating an example of a BS 1004 and a UE 1008 that may have a Tx beam 1014 that may interfere with an Rx beam 1012. The network connection flow diagram 1000 has a wireless device 1002 (which may be a BS or a UE), a BS 1004, a BS 1006, and a UE 1008. When the UE 1008 transmits a Tx beam 1014 to the BS 1004, the Tx beam 1014 may interfere with the Rx beam 1012 transmitted from the wireless device 1002 to the BS 1006. The network connection flow diagram 1000 illustrates a use case for a neighbor UE interfering with the serving gNB interface. The UE UL beam ID may be used to indicate the probability of use of UE beam assistance information from the UE to the gNB.

[0131] In order to determine which possible Tx beams from UE 1008 may interfere with the Rx beam transmitted to BS1004, BS1006 may be configured to communicate with BS1004 using interference communication 1010. For example, BS1006 may send a list of Tx beams that UE1008 can transmit to BS1004 to BS1004, BS1004 may send a list of Rx beams that wireless device 1002 can transmit to BS1004 to BS1006, BS1004 may send a Tx-Rx matrix of known interference levels of Rx beams transmitted to BS1004 to BS1006 so that BS1006 knows which Tx beams may interfere with the Rx beams of BS1004, and / or BS1004 may send a Tx-Rx matrix of known interference probabilities to BS1006 so that BS1006 knows which Tx beams have a high probability of causing interference to the Rx beams of BS1004. BS1004 and BS1006 may also configure a series of tests using the interfering communication 1010 signal to cause UE 1008 to send one or more measurement signal Tx beams 1014 while BS1004 receives Rx beams 1012 to determine which Tx beams 1014 may interfere with BS1004's Rx beam 1012 and to what extent.

[0132] In some aspects, a measurement RS may be transmitted from an aggressor UE while a victim gNB or BS receives the transmission to measure actual interference. For example, BS1006 may be configured to receive Tx beam 1014 from UE 1008 while BS1004 receives Rx beam 1012 from wireless device 1002 to determine how such signals may interfere with various Rx beams transmitted to BS1004. For each Tx-Rx beam pair, BS 1004 may be configured to measure 1022 interference levels to determine which Tx beams interfere with the Rx beams transmitted to BS1004. As described above, interference levels may be measured in a variety of ways. BS1004 may send 1025 at least some of the measurement results to BS1006. As described above, the measurement results may be used to populate a Tx-Rx matrix indicating the interference level for each Tx-Rx combination. Such a matrix may be used in the future by BS 1004 or sent to any other device such as BS 1006 to communicate which Tx beam signals from UEs of type UE 1008 may interfere with Rx beam signals received by BS 1004 .

[0133] The BS 1004 may identify 1032 a usage probability of each Rx beam of each Tx-Rx beam pair. Additionally or alternatively, the BS 1004 may identify 1032 a usage probability of each Rx beam of each Tx-Rx beam pair, wherein the Rx beam has a measured interference level that meets or exceeds a minimum threshold, such as at least 10% or at least 100 bytes per minute or at least 15% of the time window. Alternatively or additionally, the BS 1006 may identify 1034 a usage probability of each Tx beam of each Tx-Rx beam pair. Alternatively or additionally, the BS 1006 may identify 1034 a usage probability of each Tx beam of each Tx-Rx beam pair, wherein the Tx beam has caused a measured interference level that meets or exceeds a minimum threshold. The BS 1004 may transmit 1042 the usage probability of each Rx beam of each Tx-Rx beam pair to the BS 1006 , and / or the BS 1006 may transmit 1042 the usage probability of each Tx beam of each Tx-Rx beam pair to the BS 1004 .

[0134] For example, the exact UE UL beam ID usage probability may be reported to BS1004 or reported to BS1006. This may avoid neighbor UEs from interfacing to the serving gNB. In other words, UE 1008 may send the derived UL beam ID usage probability to BS1006. BS1006 may send the derived UL beam ID usage probability of UE 1008 to BS1004. For example, UE 1008 may be configured to report the usage probability of the spatial filter corresponding to the SRS resource ID mapped to a given beam indication DL RS. Additionally or alternatively, UE 1008 may be configured to report the usage probability of the spatial filter corresponding to the SRS resource ID, regardless of which DL RS the SRS resource ID is mapped to. Alternatively or additionally, BS1006 may report one or both of the above usage probabilities. Such usage probabilities may be reported as a function of a previous time window (e.g., in milliseconds). Based on such information, the serving or neighbor gNB can avoid scheduling decisions with high neighbor UE to serving gNB interference scenarios in the time window.

[0135] If the probability of use of a particular UL beam of a neighbor UE is high (e.g., at or above a threshold) within the time window, the serving gNB or BS may be configured to avoid scheduling the UL beam from the wireless device during the time window. For example, the BS 1006 may indicate 1034 that the UE 1008 sends a probability of use of the Tx beam 1014 to the BS 1006 within the time window as 80%, and may send 1042 the probability to the BS 1004. Then, in response, the BS 1004 may avoid scheduling the Rx beam 1012 from the wireless device 1002 to the BS 1004 that receives high interference from the Tx beam 1014 during the same time window. Additionally or alternatively, if the probability of use of a particular UL beam of a neighbor UE is high (e.g., at or above a threshold) within the time window, the serving gNB or BS may be configured to send a suggestion signal to the neighbor gNB or BS to reduce the probability of use of the conflicting beam. For example, the BS 1006 may identify 1034 the usage probability of the UE 1008 sending the Tx beam 1014 to the BS 1006 within the time window as 80%, and may send 1042 the probability to the BS 1004. Then, in response, the BS 1004 may adjust 1052 the beam scheduling to enable the UE 1008 to send the Tx beam 1014 during a different time window, and may send 1062 such a scheduling notification to the BS 1006 to change the scheduling of the Tx beam 1014 from the UE 1008 to the different time window.

[0136] BS1004 or BS1006 or both BS1004 and BS1006 may be configured to adjust 1052, 1054 the beam scheduling based on the measured interference level of each Tx-Rx beam pair and the probability of use of the Rx beam, the probability of use of the Tx beam, or the probability of use of both beams of the Tx-Rx beam pair to minimize the probability of interference. For example, BS1004 may be configured to avoid scheduling the Rx beam during a time window in which it is known that UE 1008 has a high probability of use of one or more Tx beams that interfere with the conflicting Rx beam. Additionally or alternatively, BS1004 may be configured to send 1062 a scheduling notification to BS1006 to avoid sending one or more conflicting Tx beams during a time window in which BS1004 has a high probability of use of the conflicting Rx beam received from the wireless device 1002. Additionally or alternatively, the BS 1006 may be configured to avoid scheduling the one or more conflicting Tx beams 1014 during a time window in which the BS 1004 may have a high probability of using the Rx beam 1012 from the wireless device 1002 interfered by the one or more conflicting Tx beams 1014. Additionally or alternatively, the BS 1006 may be configured to send 1062 a scheduling notification to the BS 1004 during a time window in which the BS 1006 may have a high probability of using the Tx beams that interfere with the one or more conflicting Rx beams sent from the wireless device 1002 to avoid receiving the one or more conflicting Rx beams from the wireless device 1002. Adjusting the probability of use of a beam downward may mean not using the beam at all (e.g., 0% probability of use), which may be appropriate when the probability of use of the conflicting beam is at or near 100%. Adjusting the probability of use of a beam upward may mean using the beam during the entire time period (e.g., 100% probability of use), which may be appropriate if there is no measured interference between the beam and any other beam with a non-zero probability of use in the Tx-Rx matrix of the measured interference level.

[0137] Fig.11 A network connection flow diagram 1100 illustrating an example of a BS 1104 and a UE 1108 that may have a Tx beam 1114 that may interfere with an Rx beam 1112 is shown. The network connection flow diagram 1100 has a wireless device 1102 (which may be a BS or a UE), a BS 1104, a BS 1106, and a UE 1108. When the UE 1108 transmits a Tx beam 1114 to the BS 1106, the Tx beam 1114 may interfere with the Rx beam 1112 transmitted from the wireless device 1102 to the BS 1104. The network connection flow diagram 1100 illustrates a use case for a neighbor UE interfering with a serving gNB interface.

[0138] To determine which possible Tx beams from the UE 1108 may interfere with the Rx beam transmitted to the wireless device 1102, the BS 1106 may be configured to communicate with the BS 1104 using interference communication 1110. For example, the BS 1106 may send to the BS 1104 a list of Tx beams that the UE 1108 is capable of transmitting to the BS 1104, the BS 1104 may send to the BS 1106 a list of Rx beams that the wireless device 1102 is capable of transmitting to the BS 1104, the BS 1104 may send to the BS 1106 a Tx-Rx matrix of known interference levels for the Rx beams transmitted to the BS 1104 so that the BS 1106 knows which Tx beams are likely to interfere with the Rx beams of the BS 1104, and / or the BS 1104 may send to the BS 1106 a Tx-Rx matrix of known interference probabilities so that the BS 1106 knows which Tx beams have a high probability of interfering with the Rx beams of the BS 1104. BS1104 and BS1106 may also use the interfering communication 1110 signal to configure a series of tests to have UE 1108 send one or more measurement signal Tx beams 1114 while BS1104 receives Rx beams 1112 to determine which Tx beams 1114 may interfere with BS1104's Rx beam 1112 and to what extent.

[0139] In some aspects, a measurement RS may be transmitted from an aggressor UE while a victim gNB or BS receives the transmission to measure the actual interference. For example, BS1106 may be configured to receive Tx beam 1114 from UE 1108 while BS1104 receives Rx beam 1112 from wireless device 1102 to determine how such signals may interfere with various Rx beams transmitted to BS1104. For each Tx-Rx beam pair, BS 1104 may be configured to measure 1122 the interference level to determine which Tx beams interfere with the Rx beam transmitted to BS1104. As described above, the interference level may be measured in a variety of ways. BS1104 may send 1125 at least some of the measurement results to BS1106. As described above, the measurement results may be used to populate a Tx-Rx matrix indicating the interference level for each Tx-Rx combination. Such a matrix may be used in the future by BS 1104 or sent to any other device such as BS 1106 to communicate which Tx beam signals from UEs of type UE 1108 may interfere with Rx beam signals received by BS 1104 .

[0140] The BS 1104 may identify 1132 an interference probability for each Rx beam of each Tx-Rx beam pair. Additionally or alternatively, the BS 1104 may identify 1132 an interference probability for each Rx beam of each Tx-Rx beam pair, where the Rx beam has a measured interference level that meets or exceeds a minimum threshold, such as at least 10% or at least 100 bytes per minute or at least 15% of the time window. Alternatively or additionally, the BS 1106 may identify 1134 an interference probability for each Tx beam of each Tx-Rx beam pair. Alternatively or additionally, the BS 1106 may identify 1134 an interference probability for each Tx beam of each Tx-Rx beam pair, where the Tx beam has caused a measured interference level that meets or exceeds a minimum threshold. The BS 1104 may transmit 1142 the interference probability of each Rx beam of each Tx-Rx beam pair to the BS 1106 , and / or the BS 1106 may transmit 1142 the interference probability of each Tx beam of each Tx-Rx beam pair to the BS 1104 .

[0141] If the interference probability of a specific UL beam (Tx beam 1114) of a neighbor UE (UE1108) is high (~80%) for the UL beam (Rx beam 1112) of the serving gNB (BS1104) in a time window, the serving gNB (BS1104) may be configured to avoid scheduling the UL beam (Rx beam 1112) from a wireless device (wireless device 1102) that receives high interference from the UL beam (Tx beam 1114) of the specific neighbor UE in the time window, similar to some of the above aspects. Additionally or alternatively, if the interference probability of a particular UL beam (Tx beam 1114) of a neighbor gNB (BS1104) is high (e.g., ~80%) for the UL beam (Rx beam 1112) of the serving gNB (BS1106) in the time window, the serving gNB (BS1104) may be configured to send a suggestion signal to the neighbor gNB (BS1106) to request that the UL beam usage probability of the neighbor gNB be reduced to a threshold value less than the conflicting beam (Tx beam 1114) so ​​that the serving gNB (BS1104) can schedule the conflicting UL (Rx beam 1112) without the neighbor gNB (BS1106) using the interfering UL beam (Tx beam 1114) for transmission, similar to some of the above aspects.

[0142] BS1104 or BS1106 or both BS1104 and BS1106 may be configured to adjust 1152, 1154 the beam scheduling based on the interference level measured for each Tx-Rx beam pair and the interference probability of the Rx beam, the interference probability of the Tx beam, or the interference probability of both beams of the Tx-Rx beam pair to minimize the interference probability. For example, BS1104 may be configured to avoid scheduling the Rx beam during a time window in which it is known that UE 1108 is transmitting using a Tx beam with a high interference probability for the conflicting Rx beam. Additionally or alternatively, BS1104 may be configured to send 1162 a scheduling notification to BS1106 to avoid transmitting one or more conflicting Tx beams during a time window in which BS1104 is scheduled to receive an Rx beam 1112 with a high interference probability for the conflicting Tx beam 1114. Additionally or alternatively, the BS 1106 may be configured to avoid scheduling the one or more conflicting Tx beams 1114 during a time window in which the BS 1104 may be scheduled to receive an Rx beam 1112 having a high probability of interference with the one or more conflicting Tx beams 1114. Additionally or alternatively, the BS 1106 may be configured to send 1162 a scheduling notification to the BS 1104 to avoid receiving the one or more conflicting Rx beams from the wireless device 1102 during a time window in which the BS 1106 may have a UE 1108 that is transmitting a Tx beam 1114 having a high probability of interference with the Rx beam 1112 received by the BS 1104. Adjusting the probability of use of a beam downward may mean not using the beam at all (e.g., 0% probability of use), which may be appropriate when the probability of use of the conflicting beam is at or near 100%. Adjusting the probability of use of a beam upward may mean using the beam during the entire time period (e.g., 100% probability of use), which may be appropriate if there is no measured interference between the beam and any other beam with a non-zero probability of use in the Tx-Rx matrix of the measured interference level.

[0143] Fig.12 A network connection flow diagram 1200 illustrating an example of UE 1202, UE 1204, and UE 1206 each communicating using SL transmissions, some of which may interfere with each other, is shown. When UE 1202 transmits a Tx beam 1212 to UE 1204 via SL transmission, the Tx beam 1212 may interfere with an Rx beam 1214 transmitted from UE 1204 to UE 1206 via SL transmission. The network connection flow diagram 1200 illustrates a UE SL system in which the probability of using UE beam assistance may be transmitted from a UE to a neighbor UE using SL transmission.

[0144] Although UE 1202 and UE 1206 are shown as using UE 1204 as an intermediary to pass communications to each other, UE 1202 and UE 1206 may be configured to directly pass communications to each other via another SL connection without using UE 1204 as an intermediary. For example, UE 1202 and UE 1206 may be configured to directly pass interface communications 1210 and 1211 to each other without using UE 1204 as an intermediary, and UE 1202 and UE 1206 may be configured to directly send 1242, 1244 probabilities to each other without using UE 1204 as an intermediary.

[0145] In order to determine which possible Tx beams 1212 from UE 1202 may interfere with the Rx beam 1214 transmitted to UE 1206, UE 1202 may be configured to communicate with UE 1206 directly or to communicate with UE 1206 via UE 1204 as an intermediary. That is, UE 1202 may use interface communication 1210 with UE 1204, and UE 1206 may use interface communication 1211 with UE 1204 to determine which SL Tx beams from UE 1202 may interfere with the Rx beam transmitted to UE 1206. For example, UE 1202 may send a list of Tx beams that UE 1202 can transmit to UE 1206, UE 1206 may send a list of Rx beams that UE 1206 can receive, UE 1206 may send a Tx-Rx matrix with known interference levels so that UE 1202 knows which Tx beams may interfere with the Rx beams of UE 1206; or UE 1206 may send a Tx-Rx matrix with known interference probabilities so that UE 1202 knows which Tx beams have a high probability of causing interference to the Rx beams of UE 1206. UE 1202 and UE 1206 may also configure a series of tests using the interference communication 1210 , 1211 signals to cause UE 1202 to send one or more measurement RS Tx beams 1212 while UE 1206 receives Rx beams 1214 to determine which Tx beams 1212 may interfere with UE 1206's Rx beam 1214 and to what extent.

[0146] In other words, a measurement signal may be transmitted from the offending UE, while the victim UE receives a signal measuring the actual interference. For example, UE 1202 may be configured to send a measurement RS for each possible Tx-Rx beam pair between UE 1202 and UE 1206, respectively. For each Tx-Rx beam pair, UE 1206 may be configured to measure 1222 the interference level to determine which Tx beams from UE 1202 interfere with the Rx beam transmitted to UE 1206 and / or to what extent. As explained above, the interference level may be measured in a variety of ways. UE 1206 may send at least some of the measurement results 1223, 1225 to UE 1202 directly or via an intermediary UE 1204 device.

[0147] The measurement results may be used to populate a Tx-Rx matrix indicating the interference level for each Tx-Rx combination. The Tx-Rx matrix may be saved as a matrix template for any UE of the same type as UE 1202 and UE 1206, respectively, or may be configured to transmit and receive along the same spectrum as UE 1202 and UE 1206, respectively.

[0148] The UE 1202 may identify 1232 a probability of use of each Rx beam of each Tx-Rx beam pair. Additionally or alternatively, the UE 1206 may identify 1234 a probability of use of each Rx beam of each Tx-Rx beam pair, wherein the Rx beam has a measured interference level that meets or exceeds a minimum threshold, such as at least 10% or at least 100 bytes per minute or at least 15% of the time window. Alternatively or additionally, the UE 1202 may identify 1232 a probability of use of each Tx beam of each Tx-Rx beam pair. Alternatively or additionally, the UE 1202 may identify 1232 a probability of use of each Tx beam of each Tx-Rx beam pair, wherein the Tx beam has caused a measured interference level that meets or exceeds a minimum threshold. UE 1206 may send 1244 the usage probability of each Rx beam of each Tx-Rx beam pair to UE 1202, and / or UE 1202 may send 1242 the usage probability of each Tx beam of each Tx-Rx beam pair to UE 1206. The usage probability may be directly sent between UE 1202 and UE 1206 via another SL connection.

[0149] If the usage probability of a particular beam is high in the time window, the neighbor UE may be configured to avoid using incompatible or high-interference beams in the opposite direction on resources or through negotiation between UEs. For example, UE 1202 may indicate the usage probability of each of its SL forward link / reverse link beams to its neighbor UE 1206 via SL, or vice versa. Such a situation may occur for Mode 2 resource allocations that may not have any scheduling controlled by the gNB. In a case where the SL Tx beam 1212 (e.g., beam #1) of a neighbor UE 1202 heading to UE 1204 may interfere with UE 1204 transmitting an SLRx beam 1214 (e.g., beam #3) to UE 1216, UE 1206 may adjust 1254 its beam scheduling to change its own beam (e.g., beam #3) to some other beam (e.g., beam #2) on which the SL Tx beam 1212 (e.g., beam #1) of the neighbor UE 1202 has a lower impact (i.e., the interference level for that Tx-Rx pair is below a threshold level). In the case where the SL Tx beam 1212 (e.g., beam #1) of a neighbor UE 1202 to UE 1204 may interfere with UE 1204 sending SL Rx beam 1214 (e.g., beam #3) to UE 1216, UE 1206 may adjust 1254 its beam scheduling to send 1264 a scheduling notification to UE 1204, which may then be sent 1262 by UE 1204 to UE 1202 to instruct UE 1202 to reduce its probability of using beam #1 for the time window. UE 1206 may send 1264 the scheduling notification directly to UE 1202 via another SL beam.

[0150] Using the usage probability information, UE 1202 can adjust 1252 the beam scheduling for UE 1202 or UE 1206, or UE 1206 can adjust 1254 the beam scheduling for UE 1202 or UE 1206. For example, if the victim UE (e.g., UE 1206) indicates (e.g., by sending 1244, 1242 the usage probability) that the usage probability of SL beam #2 in the time window is 80%, the aggressor UE (e.g., UE 1202) can be configured to avoid using an incompatible SL beam #1 (e.g., Tx beam 1212) in the opposite direction that may cause high interference to SL beam #2 (e.g., Rx beam 1214) on the victim UE's communication. Alternatively, if the victim UE (e.g., UE 1206) indicates that the probability of usage of UL beam #2 in the time window is 80%, the offender UE (e.g., UE 1202) may send 1262, 1264 scheduling notification or suggestion signaling to the victim UE (e.g., UE 1206) to reduce the probability of usage of SL beam #2 (e.g., Rx beam 1214) so ​​that its SL beam #1 (e.g., Tx beam 1212) can be scheduled.

[0151] UE 1202 or UE 1206 or both UE 1202 and UE 1206 may be configured to adjust 1252, 1254 beam scheduling based on the measured interference level of each Tx-Rx beam pair and the probability of use of the Rx beam, the probability of use of the Tx beam, or the probability of use of both beams of the Tx-Rx beam pair to minimize the probability of interference. For example, UE 1206 may be configured to avoid scheduling the Rx beam during a time window in which it is known that UE 1202 has a high probability of use of one or more Tx beams that interfere with the conflicting Rx beam. Additionally or alternatively, UE 1206 may be configured to send 1264, 1262 scheduling notifications to UE 1202 during a time window in which UE 1206 has a high probability of use of receiving the conflicting Rx beam to avoid sending one or more conflicting Tx beams. Additionally or alternatively, UE 1202 may be configured to avoid scheduling one or more conflicting Tx beams during a time window in which UE 1206 may have a high probability of using Rx that is interfered by one or more conflicting Tx beams. Additionally or alternatively, UE 1202 may be configured to send 1262, 1264 scheduling notifications to UE 1206 during a time window in which UE 1202 may have a high probability of using Tx that interferes with one or more conflicting Rx beams to avoid sending the one or more conflicting Rx beams. Adjusting the probability of use of a beam downward may mean not using the beam at all (e.g., 0% probability of use). Adjusting the probability of use of a beam upward may mean always using the beam (e.g., 100% probability of use).

[0152] Fig.13 A network connection flow diagram 1300 illustrating an example of UE 1302, UE 1304, and UE 1306 each communicating using SL transmissions, some of which may interfere with each other, is shown. When UE 1302 transmits a Tx beam 1312 to UE 1304 via SL transmission, Tx beam 1312 may interfere with an Rx beam 1314 transmitted from UE 1304 to UE 1306 via SL transmission. The network connection flow diagram 1300 illustrates a UE SL system in which UE beam-assisted interference probabilities may be transmitted from a UE to a neighbor UE using SL transmission.

[0153] Although UE 1302 and UE 1306 are shown as using UE 1304 as an intermediary to pass communications to each other, UE 1302 and UE 1306 may be configured to directly pass communications to each other via another SL connection without using UE 1304 as an intermediary. For example, UE 1302 and UE 1306 may be configured to directly pass interface communications 1310 and 1311 to each other without using UE 1304 as an intermediary, and UE 1302 and UE 1306 may be configured to directly send 1342, 1344 probabilities to each other without using UE 1304 as an intermediary.

[0154] In order to determine which possible Tx beams 1312 from UE 1302 may interfere with the Rx beam 1314 transmitted to UE 1306, UE 1302 may be configured to communicate with UE 1306 directly or via UE 1304 as an intermediary. That is, UE 1302 may use interface communication 1310 with UE 1304, and UE 1306 may use interface communication 1311 with UE 1304 to determine which SL Tx beams from UE 1302 may interfere with the Rx beam transmitted to UE 1306. For example, UE 1302 may send a list of Tx beams that UE 1302 can transmit to UE 1306, UE 1306 may send a list of Rx beams that UE 1306 can receive to UE 1302, UE 1306 may send a Tx-Rx matrix with known interference levels to UE 1302 so that UE 1302 knows which Tx beams may interfere with the Rx beams of UE 1306; or UE 1306 may send a Tx-Rx matrix with known interference probabilities to UE 1302 so that UE 1302 knows which Tx beams have a high probability of causing interference to the Rx beams of UE 1306. UE 1302 and UE 1306 may also use the interference communication 1310, 1311 signals to set up a series of tests to have UE 1302 send one or more measurement RS Tx beams 1312 while UE 1306 receives Rx beams 1314 to determine which Tx beams 1312 may interfere with UE 1306's Rx beam 1314 and to what extent.

[0155] In other words, a measurement signal may be transmitted from the offending UE, while the victim UE receives a signal measuring the actual interference. For example, UE 1302 may be configured to send a measurement RS for each possible Tx-Rx beam pair between UE 1302 and UE 1306, respectively. For each Tx-Rx beam pair, UE 1306 may be configured to measure 1322 the interference level to determine which Tx beams from UE 1302 may interfere with the Rx beam transmitted to UE 1306 and / or to what extent. As explained above, the interference level may be measured in a variety of ways. UE 1306 may send at least some of the measurement results 1323, 1325 to UE 1302 directly or via an intermediary UE 1304 device.

[0156] The measurement results may be used to populate a Tx-Rx matrix indicating the interference level for each Tx-Rx combination. The Tx-Rx matrix may be saved as a matrix template for any UE of the same type as UE 1302 and UE 1306, respectively, or may be configured to transmit and receive along the same spectrum as UE 1302 and UE 1306, respectively.

[0157] The UE 1302 may identify 1332 an interference probability for each Tx beam of each Tx-Rx beam pair. Additionally or alternatively, the UE 1306 may identify 1334 an interference probability for each Rx beam of each Tx-Rx beam pair, where the Rx beam has a measured interference level that meets or exceeds a minimum threshold, such as at least 10% or at least 100 bytes per minute or at least 15% of the time window. Alternatively or additionally, the UE 1302 may identify 1332 an interference probability for each Tx beam of each Tx-Rx beam pair. Alternatively or additionally, the UE 1302 may identify 1332 an interference probability for each Tx beam of each Tx-Rx beam pair, where the Tx beam has caused a measured interference level that meets or exceeds a minimum threshold. UE 1306 may send 1344 the interference probability of each Rx beam of each Tx-Rx beam pair to UE 1302, and / or UE 1302 may send 1342 the interference probability of each Tx beam of each Tx-Rx beam pair to UE 1306. The interference probability may be sent directly between UE 1302 and UE 1306 via another SL connection.

[0158] If the interference probability of a particular beam is high in the time window, the neighbor UE may be configured to avoid using incompatible or high-interference beams in the opposite direction on resources or through negotiation between UEs. For example, UE 1302 may indicate the interference probability of each of its SL forward link / reverse link beams to its neighbor UE 1306 via SL, or vice versa. Such a situation may occur for Mode 2 resource allocations that may not have any scheduling controlled by the gNB. In a situation where the SL Tx beam 1312 (e.g., beam #1) of a neighbor UE 1302 destined to UE 1304 may have a high interference probability on the SL Rx beam 1314 (e.g., beam #3) of UE 1304 destined to UE 1316, UE 1306 may adjust 1354 its beam scheduling to change its own beam (e.g., beam #3) to some other beam (e.g., beam #2) on which the SL Tx beam 1312 (e.g., beam #1) of the neighbor UE 1302 has a lower impact (i.e., the interference probability of the Tx-Rx pair is below a threshold level). In the case where the SL Tx beam 1312 (e.g., beam #1) of a neighbor UE 1302 to UE 1304 may have a high probability of interference with the SLRx beam 1314 (e.g., beam #3) that UE 1304 sends to UE 1316, UE 1306 may adjust 1354 its beam scheduling to send 1364 a scheduling notification to UE 1304, which may then be sent 1362 by UE 1304 to UE 1302 to instruct UE 1302 to reduce its probability of using beam #1 for the time window. UE 1306 may send 1364 the scheduling notification directly to UE 1302 via another SL beam.

[0159] Using the usage probability information, UE 1302 is able to adjust 1352 beam scheduling for UE 1302 or UE 1306, or UE 1306 is able to adjust 1354 beam scheduling for UE 1302 or UE 1306. For example, if a victim UE (e.g., UE 1306) indicates (e.g., by sending 1344, 1342 interference probabilities) that the interference probability of SL beam #2 is 80% for SL beam #1 (e.g., Tx beam 1312) from an aggressor UE (e.g., UE 1302) in a time window, the aggressor UE (e.g., UE 1302) may be configured to avoid using an incompatible SL beam #1 (e.g., Tx beam 1312) in the opposite direction that may have a high interference probability with SL beam #2 (e.g., Rx beam 1314) in the communication with the victim UE. Alternatively, if the victim UE (e.g., UE 1306) indicates that the interference probability of UL beam #2 for UL beam #1 of the aggressor UE (e.g., UE 1302) in the time window is 80%, the aggressor UE (e.g., UE 1302) may send 1362, 1364 scheduling notification or suggestion signaling to the victim UE (e.g., UE 1306) to reduce the probability of using SL beam #2 (e.g., Rx beam 1314) so ​​that its SL beam #1 (e.g., Tx beam 1312) can be scheduled.

[0160] UE 1302 or UE 1306 or both UE 1302 and UE 1306 may be configured to adjust 1352, 1354 the beam scheduling based on the interference level measured for each Tx-Rx beam pair and the interference probability of the Rx beam, the interference probability of the Tx beam, or the interference probability of both beams of the Tx-Rx beam pair to minimize the interference probability. UE 1306 may be configured to avoid scheduling the Rx beam during a time window in which it is known that UE 1302 has a high probability of using one or more Tx beams that interfere with the conflicting Rx beam. UE 1306 may be configured to send 1364, 1362 a scheduling notification to UE 1302 during a time window in which UE 1306 has a high probability of using the conflicting Rx beam to avoid sending one or more conflicting Tx beams. UE 1302 may be configured to avoid scheduling one or more conflicting Tx beams during a time window in which UE 1306 may have a high probability of using Rx that is interfered by one or more conflicting Tx beams. UE 1302 may be configured to send 1362, 1364 scheduling notifications to UE 1306 during a time window in which UE 1302 may have a high probability of using Tx that interferes with one or more conflicting Rx beams to avoid sending the one or more conflicting Rx beams. Adjusting the probability of use of a beam downward may mean not using the beam at all (e.g., 0% probability of use). Adjusting the probability of use of a beam upward may mean always using the beam (e.g., 100% probability of use).

[0161] Fig.14 1400 is a flow chart of a method of wireless communication at a wireless device. The method may be performed by any wireless device, such as UE 104, BS 102, BS 504, UE 602, BS 604, UE 702, BS 704, UE 802, BS 804, UE 902, BS 904, BS 1004, BS 1104, UE 1206, UE 1204, UE 1306, UE 1304, apparatus 1804, network entity 1802, or network entity 1902. The method may enable the wireless device to minimize potential interference from a Tx beam to an Rx beam by adjusting at least one beam scheduling.

[0162] At 1402, the first wireless device may identify a usage probability of each Rx beam of the first wireless device in a plurality of Tx-Rx beam pairs associated with the first wireless device and a second wireless device, wherein the usage probability may include a usage metric indicating a likelihood of using the beam. Figure 4404 in the BS 404 may identify 432 a usage probability of each Rx beam 412 of the BS 404 in a plurality of Tx-Rx beam pairs between the BS 404 and the BS 406. Alternatively, the first wireless device may identify an interference probability of each Rx beam of the first wireless device in a plurality of Tx-Rx beam pairs associated with the first wireless device and the second wireless device, wherein the interference probability may include an interference metric indicating a likelihood that the Tx beam of the second wireless device interferes with the Rx beam of the first wireless device. For example, Figure 5 The BS 504 in the BS 404 may identify 532 the interference probability of each Rx beam 412 of the BS 404 in the plurality of Tx-Rx beam pairs between the BS 404 and the BS 406. Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0163] At 1404, the first wireless device may send a first indication of a probability of use of each Rx beam in a plurality of Tx-Rx beam pairs to the second wireless device. Figure 4 BS 404 in the wireless device may send 442 to BS 406 a first indication of a probability of use of the identified 432 for each Rx beam 412 in a plurality of Tx-Rx beam pairs between BS 404 and BS 406. Alternatively, the first wireless device may send a first indication of an interference probability for each Rx beam in a plurality of Tx-Rx beam pairs to a second wireless device. For example, Figure 5 BS 504 in the BS 506 may send 542 to BS 506 a first indication of the identified 532 interference probability of each Rx beam 512 in a plurality of Tx-Rx beam pairs between BS 504 and BS 506. In addition, 1404 may be Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0164] Fig.15 1500 is a flow chart of a method of wireless communication at a wireless device. The method may be performed by any wireless device, such as UE 104, BS 102, BS 504, UE 602, BS 604, UE 702, BS 704, UE 802, BS 804, UE 902, BS 904, BS 1004, BS 1104, UE 1206, UE 1204, UE 1306, UE 1304, apparatus 1804, network entity 1802, or network entity 1902. The method may improve the ability of the wireless device to minimize potential interference from a Tx beam to an Rx beam by adjusting at least one beam schedule.

[0165] At 1502, the first wireless device may receive a plurality of measurement RSs associated with a plurality of Tx-Rx beam pairs from a second wireless device. Figure 4 BS 404 in the embodiment may receive a plurality of measurement RSs in the form of Tx beams 414 transmitted from BS 406 from BS 406. The plurality of measurement RSs in the form of Tx beams 414 may be associated with a plurality of Tx-Rx beam pairs between BS 404 and BS 406. At least one of the interference levels measured 422 for each Tx-Rx beam pair in the plurality of Tx-Rx beam pairs between BS 404 and BS 406 may be based on the plurality of Tx beams 414 transmitted from BS 406. In addition, 1502 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0166] At 1504, the first wireless device may measure an interference level of each Rx beam of the first wireless device in a plurality of Tx-Rx beam pairs or an interference level of each Tx beam of the second wireless device in a plurality of Tx-Rx beam pairs. Figure 4 BS 404 in the embodiment may measure the interference level of Rx beam 412 of BS 404 for each of a plurality of Tx-Rx beam pairs associated with BS 404 and BS 406. Alternatively, in another aspect, Figure 4 BS 404 in 406 may measure the interference level of Tx beam 414 of BS 406 for each of a plurality of Tx-Rx beam pairs associated with BS 404 and BS 406. In addition, 1504 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0167] At 1506, the first wireless device may identify at least one of a usage probability or an interference probability of each Rx beam of the first wireless device in a plurality of Tx-Rx beam pairs associated with the first wireless device and the second wireless device. Figure 4 BS 404 in 406 may identify 432 a usage probability of each Rx beam 412 of BS 404 for each Tx-Rx beam pair associated with BS 404 and BS 406. Alternatively, in another aspect, Figure 5 BS 504 in 506 may identify 532 the interference probability of each Rx beam 512 of BS 504 for each Tx-Rx beam pair associated with BS 504 and BS 506. In addition, 1506 may be composed of Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0168] At 1508, the first wireless device may receive from the second wireless device an indication of at least one of a usage probability or an interference probability for each Tx beam in the plurality of Tx-Rx beam pairs. Figure 4 BS 404 in the embodiment may receive from BS 406 an indication of the identified 434 probability of use of each Tx beam 414 in a plurality of Tx-Rx beam pairs between BS 404 and BS 406. A second indication of the measured 422 interference level for each Tx beam 414 may be associated with the received indication of the identified 434 probability of use of each Tx beam 414 in a plurality of Tx-Rx beam pairs between BS 404 and BS 406. Alternatively, in another aspect, Figure 5 The BS 504 in the BS 506 may receive from the BS 506 an indication of an identified 534 interference probability for each Tx beam 514 in a plurality of Tx-Rx beam pairs between the BS 504 and the BS 506. The second indication of the measured 522 interference level for each Tx beam 514 may be associated with the received indication of the identified 534 probability of use for each Tx beam 514 in a plurality of Tx-Rx beam pairs between the BS 504 and the BS 506. In addition, 1508 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0169] At 1510, the first wireless device may send a first indication of at least one of a usage probability or an interference probability of each Rx beam in a plurality of Tx-Rx beam pairs to the second wireless device. Figure 4 BS 404 in may send 442 to BS 406 an indication of the probability of use of each Rx beam of each Tx-Rx beam pair associated with BS 404 and BS 406. Alternatively, in another aspect, Figure 5 BS 504 in the example may send 542 to BS 506 an indication of the interference probability for each Rx beam of each Tx-Rx beam pair associated with BS 504 and BS 506. In addition, 1510 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0170] At 1512, the first wireless device may send a second indication of the measured interference level of each Rx beam or Tx beam in the plurality of Tx-Rx beam pairs to the second wireless device. Figure 4 BS 404 in the BS 406 may send 424 to BS 406 a second indication of the measured 422 interference level of each Rx beam 412 in a plurality of Tx-Rx beam pairs between BS 404 and BS 406. Alternatively, Figure 4BS 404 in the BS 406 may send 424 to BS 406 a second indication of the measured 422 interference level of each Tx beam 414 in the plurality of Tx-Rx beam pairs between BS 404 and BS 406. In addition, 1512 may be Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0171] At 1514, the first wireless device may receive a beam schedule for at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs from the second wireless device. Figure 4 BS 404 in the example may receive a beam scheduling notification sent 862 for at least one of the Tx-Rx beam pairs from BS 406. BS 406 may send 442 an increased probability of using Tx beam 414 of BS 406 using interfering Rx beam 412. In addition, 1514 may be sent by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0172] At 1516, the first wireless device may reduce the usage probability of at least one Rx beam based on the beam scheduling, or send a third indication to reduce the usage probability of at least one Tx beam based on the beam scheduling. For example, the BS 404 may reduce the usage probability of at least one Rx beam 412 associated with at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs by adjusting 452 the beam scheduling of the Rx beam 412 based on the increased usage probability sent 442. Alternatively, at 1516, the BS 404 may send 462 a scheduling notification to the BS 406 to reduce the usage probability of the Tx beam 414 interfering with the Rx beam 412 based on the adjustment 452 of the beam scheduling of the Tx beam 414. In addition, 1516 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0173] In some aspects, the interference level of each Tx-Rx beam pair in the plurality of Tx-Rx beam pairs may be based on the inter-node CLI. Figure 4 The measured 422 interference level for each Tx-Rx beam pair of the plurality of Tx-Rx beam pairs between the BS 404 and the BS 406 may be based on the inter-node CLI.

[0174] In some aspects, the usage probability corresponds to a first probability over a first time window, and the interference probability corresponds to a second probability over a second time window. Figure 4 The identified usage probability 432 of may correspond to a first probability over a first time window, and Figure 5 The identified 532 interference probability of may correspond to a second probability over a second time window.

[0175] In some aspects, the usage probability is associated with a usage threshold, and the interference probability is associated with an interference threshold. Figure 4 The identified 432 usage probability may be associated with a usage threshold, and Figure 5 The identified 532 interference probability may be associated with an interference threshold.

[0176] In some aspects, the first indication of at least one of a usage probability or an interference probability for each Rx beam in the plurality of Tx-Rx beam pairs is associated with at least one of a usage probability being greater than a usage threshold or an interference level being greater than an interference threshold. Figure 4 The usage probability of the identified 432 for each Rx beam 412 in the plurality of Tx-Rx beam pairs between BS 404 and BS 406 may be associated with the usage probability of the identified 432 being greater than a usage threshold. Alternatively, Figure 5 The identified 532 interference probability of each Rx beam 512 in the plurality of Tx-Rx beam pairs between the BS 504 and the BS 506 may be associated with the identified 532 usage probability being greater than a usage threshold.

[0177] In some aspects, the first wireless device is a first BS or a first UE and the second wireless device is a second BS or a second UE. Figure 4 BS 404 is BS, Figure 8 UE 802 in is a UE, Figure 4 BS 406 is BS, and Figure 8 UE808 in the figure is UE.

[0178] Fig.16 1600 is a flow chart of a method of wireless communication at a wireless device. The method may be performed by any wireless device, such as UE 104, BS 102, BS 506, BS 606, BS 706, BS 806, BS 906, BS 1006, BS 1106, UE 1206, UE 1202, UE 1204, UE 1302, UE 1304, apparatus 1804, network entity 1802, or network entity 1902. The method may enable the wireless device to minimize potential interference from a Tx beam to an Rx beam by adjusting at least one beam scheduling.

[0179] At 1602, the second wireless device may receive, from the first wireless device, a first indication of a probability of use of each Rx beam of the first wireless device in a plurality of Tx-Rx beam pairs. Figure 4BS 406 in the second wireless device may receive, from BS 404, a transmission 442 of a first indication of a probability of use of the identified 432 for each Rx beam 412 in a plurality of Tx-Rx beam pairs between BS 404 and BS 406. Alternatively, at 1602, the second wireless device may receive, from the first wireless device, a first indication of an interference probability for each Rx beam of the first wireless device in the plurality of Tx-Rx beam pairs. For example, Figure 5 BS 506 in the BS 504 may receive a transmission 542 of a first indication of an interference probability of each Rx beam 512 identified 532 in a plurality of Tx-Rx beam pairs between BS 504 and BS 506. In addition, 1602 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0180] At 1604, the second wireless device may adjust beam scheduling for a plurality of Tx-Rx beam pairs based on the received first indication. Figure 4 The BS 406 in the BS 404 may adjust 454 the beam scheduling for the multiple Tx-Rx beam pairs based on the received first indication of the identified 432 usage probability of each Rx beam 412 in the multiple Tx-Rx beam pairs between the BS 404 and the BS 406. Alternatively, Figure 5 The BS 506 in the BS 504 may adjust 554 the beam scheduling for the plurality of Tx-Rx beam pairs based on the first indication of the identified 532 interference probability of each Rx beam 512 in the plurality of Tx-Rx beam pairs between the BS 506 and the BS 504. In addition, 1604 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0181] Fig.17 1700 is a flow chart of a method of wireless communication at a wireless device. The method may be performed by any wireless device, such as UE 104, BS 102, BS 504, UE 602, BS 604, UE 702, BS 704, UE 802, BS 804, UE 902, BS 904, BS 1004, BS 1104, UE 1206, UE 1204, UE 1306, UE 1304, apparatus 1804, network entity 1802, or network entity 1902. The method may improve the ability of the wireless device to minimize potential interference from a Tx beam to an Rx beam by adjusting at least one beam schedule.

[0182] At 1702, the second wireless device may transmit a plurality of measurement RSs associated with a plurality of Tx-Rx beam pairs to the first wireless device. For example, BS 406 may transmit a plurality of measurement RSs in the form of Tx beams 414 associated with a plurality of Tx-Rx beam pairs between BS 404 and BS 406 to BS 404. The second indication of the interference level measured 422 for each Rx beam 412 or each Tx beam of the plurality of Tx-Rx beam pairs between BS 406 and BS 404 may be based on the plurality of measurement RSs in the form of Tx beams 414 transmitted from BS 406. In addition, 1702 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0183] At 1704, the second wireless device may send an indication of at least one of a probability of use or an interference probability for each Tx beam in the plurality of Tx-Rx beam pairs to the first wireless device. For example, the BS 406 may send 442 to the BS 404 an indication of an identified 434 probability of use for each Tx beam 414 in the plurality of Tx-Rx beam pairs between the BS 404 and the BS 406. The second indication of the measured 422 interference level for each Tx beam 414 may be associated with the sent 442 indication of the identified 434 probability of use for each Tx beam 414 in the plurality of Tx-Rx beam pairs between the BS 404 and the BS 406. Alternatively, in another aspect, the BS 506 may send 542 to the BS 504 an indication of an identified 534 probability of interference for each Tx beam 514 in the plurality of Tx-Rx beam pairs between the BS 504 and the BS 506. The second indication of the measured 522 interference level for each Tx beam 514 may be associated with the transmitted 542 indication of the identified 534 probability of use of each Tx beam 514 in the plurality of Tx-Rx beam pairs between the BS 504 and the BS 506. Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0184] At 1706, the second wireless device may receive from the first wireless device a first indication of at least one of a usage probability or an interference probability of each Rx beam of the first wireless device in a plurality of Tx-Rx beam pairs. Figure 4 BS 406 in may receive, from BS 404, a transmission 424 of an indication of an identified 432 probability of use of each Rx beam 412 of BS 404 for each Tx-Rx beam pair associated with BS 404 and BS 406. Alternatively, in another aspect, Figure 5BS 506 in the embodiment may receive, from BS 504, a transmission 542 of an indication of an identified 532 interference probability for each Rx beam 512 of BS 504 for each Tx-Rx beam pair associated with BS 504 and BS 506. In addition, 1706 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0185] At 1708, the second wireless device may receive from the first wireless device a second indication of a measured interference level for each Rx beam in the plurality of Tx-Rx beam pairs or a measured interference level for each Tx beam of the second wireless device in the plurality of Tx-Rx beam pairs. Figure 4 BS 406 in BS 404 may receive, from BS 404, a transmission 424 of an indication of a measured 422 interference level for each Rx beam 412 in a plurality of Tx-Rx beam pairs between BS 404 and BS 406. Alternatively, Figure 4 BS 406 in the BS 404 may receive from BS 404 a transmission 424 of a second indication of the measured 422 interference level of each Tx beam 414 in the plurality of Tx-Rx beam pairs between BS 404 and BS 406. In addition, 1708 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0186] At 1710, the second wireless device may adjust beam scheduling for at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs based on the received first indication. Figure 4 The BS 406 in the BS 404 may adjust 454 the beam scheduling for the multiple Tx-Rx beam pairs based on the transmitted 424 measurement of the measured 422 interference level of each Rx beam 412 in the multiple Tx-Rx beam pairs between the BS 404 and the BS 406. Alternatively, Figure 4 The BS 406 in the BS 404 may adjust 454 the beam scheduling for the multiple Tx-Rx beam pairs based on the transmitted 424 measurement of the measured 422 interference level of each Tx beam 414 in the multiple Tx-Rx beam pairs between the BS 404 and the BS 406. In addition, 1710 may be performed by Fig.18 Probabilistic interface components in 198 or Fig.19 The probability interface component 199 in is implemented.

[0187] In some aspects, the interference level of each Tx-Rx beam pair in the plurality of Tx-Rx beam pairs may be based on the inter-node CLI. Figure 4The measured interference level 422 for each Tx-Rx beam pair in the plurality of Tx-Rx beam pairs between the BS 404 and the BS 406 may be based on the inter-node CLI.

[0188] In some aspects, the usage probability corresponds to a first probability over a first time window, and the interference probability may correspond to a second probability over a second time window. Figure 4 The usage probability identified in 434 may correspond to a first probability over a first time window, and Figure 5 The identified interference probability 534 in may correspond to a second probability over a second time window.

[0189] In some aspects, the usage probability may be associated with a usage threshold, and the interference probability may be associated with an interference threshold. Figure 4 The usage probability identified in 434 may be associated with a usage threshold, and Figure 5 The interference probability identified 534 in may be associated with an interference threshold.

[0190] In some aspects, the first indication of at least one of a usage probability or an interference probability for each Rx beam in the plurality of Tx-Rx beam pairs may be associated with at least one of a usage probability being greater than a usage threshold or an interference level being greater than an interference threshold. Figure 4 The usage probability of the identified 434 of each Tx beam 414 in the plurality of Tx-Rx beam pairs between BS 404 and BS 406 in the BS 404 may be associated with the usage probability of the identified 434 being greater than a usage threshold. Alternatively, Figure 5 The identified 534 interference probability of each Tx beam 514 in the plurality of Tx-Rx beam pairs between the BS 504 and the BS 506 in the BS 504 may be associated with the identified 534 usage probability being greater than a usage threshold.

[0191] In some aspects, the first wireless device is a first BS or a first UE and the second wireless device may be a second BS or a second UE. Figure 4 BS 404 is BS, Figure 8 UE 802 in is a UE, Figure 4 BS 406 is BS, and Figure 8 UE 808 in is a UE.

[0192] Fig.181800 is an example of a hardware implementation of an example device 1804. The device 1804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 1804 may include a cellular baseband processor 1824 (also referred to as a modem) coupled to one or more transceivers 1822 (e.g., a cellular RF transceiver). The cellular baseband processor 1824 may include on-chip memory 1824'. In some aspects, the device 1804 may also include one or more subscriber identity module (SIM) cards 1820 and an application processor 1806 coupled to a secure digital (SD) card 1808 and a screen 1810. The application processor 1806 may include on-chip memory 1806'. In some aspects, the device 1804 may also include a Bluetooth module 1812, a WLAN module 1814, an SPS module 1816 (e.g., a GNSS module), one or more sensor modules 1818 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1826, a power source 1830, and / or a camera 1832. The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 may include an on-chip transceiver (TRx) (or in some cases, only a receiver (Rx)). The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 may include their own dedicated antennas and / or communicate using an antenna 1880. The cellular baseband processor 1824 communicates with the UE 104 and / or with the RU associated with the network entity 1802 through the transceiver 1822 via one or more antennas 1880. The cellular baseband processor 1824 and the application processor 1806 may each include a computer-readable medium / memory 1824', 1806', respectively. The additional memory module 1826 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1824', 1806', 1826 may be non-transitory. The cellular baseband processor 1824 and the application processor 1806 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1824 / application processor 1806, enables the cellular baseband processor 1824 / application processor 1806 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1824 / application processor 1806 when executing the software.The cellular baseband processor 1824 / application processor 1806 may be a component of the UE 350 and may include the memory 360 and / or at least one of the Tx processor 368, the Rx processor 356, and the controller / processor 359. In one configuration, the device 1804 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1824 and / or the application processor 1806, while in another configuration, the device 1804 may be the entire UE (e.g., see. Figure 3 UE 350) and includes additional modules of device 1804.

[0193] As described above, the component 198 of the first network node may be configured to: identify at least one of a usage probability or an interference probability of each Rx beam of the first network node in a plurality of Tx-Rx beam pairs associated with the first network node and the second network node. The usage probability may include a usage metric indicating the likelihood of using the beam. The interference probability may include an interference metric indicating the likelihood that the Tx beam of the second network node interferes with the Rx beam of the first network node. The component 198 may also be configured to: send a first indication of the usage probability or the interference probability for each Rx beam in the plurality of Tx-Rx beam pairs. The second network node may receive the first indication and adjust the beam scheduling for at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs based on the received first indication. The component 198 may be within the cellular baseband processor 1824, the application processor 1806, or within both the cellular baseband processor 1824 and the application processor 1806. Component 198 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, device 1804 may include multiple components configured for various functions. In one configuration, device 1804 (specifically, cellular baseband processor 1824 and / or application processor 1806) includes: a component for measuring the interference level of the Rx beam of the first wireless device or the interference level of the Tx beam of the second wireless device for each of a plurality of Tx-Rx beam pairs associated with a first wireless device and a second wireless device; a component for identifying at least one of the usage probability or the interference probability of each Rx beam of the first wireless device in the plurality of Tx-Rx beam pairs; a component for sending to the second wireless device a first indication of at least one of the usage probability or the interference probability of each Rx beam in the plurality of Tx-Rx beam pairs or a first indication of at least one of the usage probability or the interference probability of each Rx beam in the plurality of Tx-Rx beam pairs. a component for receiving, from a first wireless device, a first indication of at least one of a usage probability or an interference probability of each Rx beam of the first wireless device in the plurality of Tx-Rx beam pairs or a second indication of a measured interference level of each Rx beam in the plurality of Tx-Rx beam pairs or a measured interference level of each Tx beam in the plurality of Tx-Rx beam pairs for the second wireless device; a component for adjusting beam scheduling for at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs based on the received first indication or the received second indication;a means for receiving, from the second wireless device, a plurality of measurement RSs associated with the plurality of Tx-Rx beam pairs, wherein at least one of the measured interference levels for each Tx-Rx beam pair in the plurality of Tx-Rx beam pairs is based on the plurality of measurement RSs; a means for receiving, from the second wireless device, an indication of at least one of the usage probability or the interference probability for each Tx beam in the plurality of Tx-Rx beam pairs, wherein the second indication of the measured interference level for each Tx beam is associated with the received indication of the at least one of the usage probability or the interference probability for each Tx beam in the plurality of Tx-Rx beam pairs; and a means for transmitting, from the second wireless device, a measurement RS associated with the plurality of Tx-Rx beam pairs. The wireless communication device comprises a wireless communication device for receiving a beam scheduling for at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs; a component for reducing the usage probability of at least one Rx beam associated with at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs based on the beam scheduling; a component for sending a third indication of reducing the usage probability of at least one Tx beam associated with at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs to the second wireless device based on the beam scheduling; and a component for sending a plurality of measurement reference signals (RS) associated with the plurality of Tx-Rx beam pairs to the first wireless device, wherein each Rx of the plurality of Tx-Rx beam pairs is used for the measurement reference signals (RS). The second indication of the measured interference level of the Tx beam or each Tx beam is based on the multiple measurement RSs; a component for sending an indication of at least one of the usage probability or the interference probability of each Tx beam in the multiple Tx-Rx beam pairs to the first wireless device, wherein the second indication of the measured interference level of each Tx beam is associated with the sent indication of at least one of the usage probability or the interference probability of each Tx beam in the multiple Tx-Rx beam pairs; a component for identifying at least one of the usage probability or the interference probability of each Rx beam of the first network node in the multiple Tx-Rx beam pairs associated with the first network node and the second network node; a component for sending an indication of at least one of the usage probability or the interference probability of each Rx beam of the first network node to the second wireless device; A component for the network node to send a first indication of at least one of the usage probability or the interference probability of each Rx beam in the plurality of Tx-Rx beam pairs; a component for receiving a plurality of measurement RSs associated with the plurality of Tx-Rx beam pairs from the second network node; a component for measuring the interference level of each Rx beam of the first network node in the plurality of Tx-Rx beam pairs or the interference level of each Tx beam of the second network node in the plurality of Tx-Rx beam pairs; a component for sending a second indication of the measured interference level of each Rx beam in the plurality of Tx-Rx beam pairs or the measured interference level of each Tx beam in the plurality of Tx-Rx beam pairs to the second network node;A means for receiving an indication of at least one of the usage probability or the interference probability for each Tx beam in the plurality of Tx-Rx beam pairs from the second network node; a means for receiving a beam schedule for at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs from the second network node; a means for reducing the usage probability of the at least one Rx beam associated with at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs based on the beam schedule; a means for receiving a beam schedule for at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs from the second network node; and a means for sending a third indication to reduce the usage probability of the at least one Tx beam associated with the plurality of Tx-Rx beam pairs to the second network node based on the beam schedule. The means may be a component 198 of the apparatus 1804 configured to perform the functions recited by the means. As described above, the device 1804 may include a Tx processor 368, an Rx processor 356, and a controller / processor 359. Thus, in one configuration, the component 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. ;

[0194] Fig.191900 is a diagram illustrating an example of a hardware implementation for a network entity 1902. The network entity 1902 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1902 may include at least one of a CU 1910, a DU 1930, or a RU 1940. For example, depending on the layer functionality handled by the component 199, the network entity 1902 may include a CU 1910; both a CU 1910 and a DU 1930; each of the CU 1910, the DU 1930, and the RU 1940; the DU 1930; both a DU 1930 and a RU 1940; or a RU 1940. The CU 1910 may include a CU processor 1912. The CU processor 1912 may include an on-chip memory 1912'. In some aspects, the CU 1910 may also include an additional memory module 1914 and a communication interface 1918. CU 1910 communicates with DU 1930 via a midhaul link, such as an F1 interface. DU 1930 may include a DU processor 1932. DU processor 1932 may include on-chip memory 1932'. In some aspects, DU 1930 may also include an additional memory module 1934 and a communication interface 1938. DU 1930 communicates with RU 1940 via a fronthaul link. RU 1940 may include a RU processor 1942. RU processor 1942 may include on-chip memory 1942'. In some aspects, RU 1940 may also include an additional memory module 1944, one or more transceivers 1946, an antenna 1980, and a communication interface 1948. RU 1940 communicates with UE 104. On-chip memory 1912', 1932', 1942' and additional memory modules 1914, 1934, 1944 can each be considered as a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each processor in processor 1912, 1932, 1942 is responsible for general processing, including executing software stored on computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0195] As described above, the component 199 at the first network node may be configured to receive from the second network node a first indication of at least one of a probability of use or a probability of interference of each Rx beam of the second network node in a plurality of Tx-Rx beam pairs. The probability of use may include a usage metric indicating the likelihood of using the beam. The probability of interference may include an interference metric indicating the likelihood that the Tx beam of the first network node interferes with the Rx beam of the second network node. The component 199 may also be configured to adjust the beam scheduling for at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs based on the received first indication. The component 199 may be within one or more processors of one or more of the CU 1910, the DU 1930, and the RU 1940. The component 199 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. The network entity 1902 may include a variety of components configured for various functions. In one configuration, the network entity 1902 includes: a component for measuring, for each Tx-Rx beam pair in a plurality of Tx-Rx beam pairs associated with a first wireless device and a second wireless device, an interference level of an Rx beam of the first wireless device or an interference level of a Tx beam of the second wireless device; a component for identifying at least one of a usage probability or an interference probability of each Rx beam of the first wireless device in the plurality of Tx-Rx beam pairs; a component for sending to the second wireless device a first indication of at least one of the usage probability or the interference probability of each Rx beam in the plurality of Tx-Rx beam pairs or a second indication of the measured interference level of each Rx beam in the plurality of Tx-Rx beam pairs or a measured interference level of each Tx beam in the plurality of Tx-Rx beam pairs; and a component for transmitting from the first wireless device to the second wireless device a first indication of at least one of the usage probability or the interference probability of each Rx beam in the plurality of Tx-Rx beam pairs. A component for receiving a first indication of at least one of a usage probability or an interference probability of each Rx beam of the first wireless device in a plurality of Tx-Rx beam pairs or a second indication of a measured interference level of each Rx beam in the plurality of Tx-Rx beam pairs or a measured interference level of each Tx beam in the plurality of Tx-Rx beam pairs of the second wireless device; a component for adjusting beam scheduling for at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs based on the received first indication or the received second indication; a component for receiving a plurality of measurement RSs associated with the plurality of Tx-Rx beam pairs from the second wireless device, wherein at least one of the measured interference levels for each Tx-Rx beam pair in the plurality of Tx-Rx beam pairs is based on the plurality of measurement RSs;a component for receiving, from the second wireless device, an indication of at least one of the usage probability or the interference probability for each Tx beam in the plurality of Tx-Rx beam pairs, wherein the second indication of the measured interference level for each Tx beam is associated with the received indication of the usage probability or the interference probability for each Tx beam in the plurality of Tx-Rx beam pairs; a component for receiving, from the second wireless device, a beam scheduling for at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs; and a component for reducing interference with at least one of the plurality of Tx-Rx beam pairs based on the beam scheduling. a component for reducing the usage probability of at least one Rx beam associated with a Tx-Rx beam pair; a component for sending a third indication to the second wireless device based on the beam scheduling to reduce the usage probability of at least one Tx beam associated with at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs; a component for sending a plurality of measurement reference signals (RS) associated with the plurality of Tx-Rx beam pairs to the first wireless device, wherein the second indication of the measured interference level for each Rx beam or each Tx beam of the plurality of Tx-Rx beam pairs is based on the plurality of measurement RSs; and a component for means for sending an indication of at least one of the usage probability or the interference probability for each Tx beam in the plurality of Tx-Rx beam pairs to the first wireless device, wherein the second indication of the measured interference level for each Tx beam is associated with the sent indication of at least one of the usage probability or the interference probability for each Tx beam in the plurality of Tx-Rx beam pairs; means for receiving a first indication of at least one of the usage probability or the interference probability for each Rx beam of the second network node in the plurality of Tx-Rx beam pairs from a second network node; means for adjusting the usage probability or the interference probability for each Rx beam of the second network node based on the received first indication A component for beam scheduling of at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs; a component for sending a plurality of measurement RSs associated with the plurality of Tx-Rx beam pairs to the second network node; a component for receiving from the second network node a second indication of a measured interference level of each Rx beam in the plurality of Tx-Rx beam pairs or a measured interference level of each Tx beam of the first network node in the plurality of Tx-Rx beam pairs; a component for adjusting the beam scheduling for the at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs based on the second indication;and means for sending an indication of at least one of the usage probability or the interference probability of each Tx beam in the plurality of Tx-Rx beam pairs to the second network node. The means may be a component 199 of the network entity 1902 configured to perform the functions recited by the means. As described above, the network entity 1902 may include a Tx processor 316, an Rx processor 370, and a controller / processor 375. Therefore, in one configuration, the means may be a Tx processor 316, an Rx processor 370, and a controller / processor 375 configured to perform the functions recited by the means. ;

[0196] 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 can be rearranged based on design preferences. In addition, some blocks can be merged or omitted. The attached method claims provide the elements of each block in a sample order, but are not meant to be limited to the specific order or hierarchy presented.

[0197] 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 can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein the elements mentioned in the singular are not intended to represent "one and only one" (unless specifically so stated), but "one or more". Terms such as "if", "when ......" and "while ......" should be interpreted as "under the conditions of ......", rather than meaning an immediate time relationship or reaction. That is, these phrases, such as "when ......", do not mean an 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, 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 specifically stated, 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, and 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 include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. In addition, regardless of whether such disclosure is explicitly recited in the claims, nothing disclosed herein is intended to be disclosed to the public. Words such as "module," "mechanism," "element," and "device" 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..." 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, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

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

[0199] Aspect 1 is a method for wireless communication at a network node, the method comprising: identifying at least one of a usage probability or an interference probability of each Rx beam of the first network node in a plurality of Tx-Rx beam pairs associated with a first network node and a second network node. The usage probability may include a usage metric indicating the likelihood of using the beam. The interference probability may include an interference metric indicating the likelihood that the Tx beam of the second network node interferes with the Rx beam of the first network node. The method may also include: sending a first indication of at least one of the usage probability or the interference probability of each Rx beam in the plurality of Tx-Rx beam pairs to the second network node.

[0200] Aspect 2 is a method according to aspect 1, wherein the method may further include: receiving a plurality of measurement RSs associated with the plurality of Tx-Rx beam pairs from the second network node. The method may further include: measuring the interference level of each Rx beam of the first network node in the plurality of Tx-Rx beam pairs or the interference level of each Tx beam of the second network node in the plurality of Tx-Rx beam pairs. At least one of the measured interference levels for each Tx-Rx beam pair in the plurality of Tx-Rx beam pairs may be based on the plurality of measurement RSs. The method may further include: sending a second indication of the measured interference level of each Rx beam in the plurality of Tx-Rx beam pairs or the measured interference level of each Tx beam in the plurality of Tx-Rx beam pairs to the second network node.

[0201] Aspect 3 is a method according to aspect 2, wherein the method may further include: receiving from the second network node an indication of at least one of the usage probability or the interference probability of each Tx beam in the plurality of Tx-Rx beam pairs. The second indication of the measured interference level of each Tx beam may be associated with the received first indication of the at least one of the usage probability or the interference probability of each Tx beam in the plurality of Tx-Rx beam pairs.

[0202] Aspect 4 is a method according to any one of aspects 2 and 3, wherein the interference level of each Tx-Rx beam pair in the plurality of Tx-Rx beam pairs may be based on an inter-node CLI.

[0203] Aspect 5 is a method according to any one of aspects 1 to 4, wherein the usage probability may correspond to a first probability over a first time window. The interference probability may correspond to a second probability over a second time window.

[0204] Aspect 6 is a method according to any one of aspects 1 to 5, wherein the usage probability may be associated with a usage threshold. The interference probability may be associated with an interference threshold.

[0205] Aspect 7 is a method according to any one of Aspect 6, wherein the first indication of the at least one of the usage probability or the interference probability of each Rx beam in the multiple Tx-Rx beam pairs may be associated with at least one of the usage probability being greater than the usage threshold or the interference level being greater than the interference threshold.

[0206] Aspect 8 is a method according to any one of aspects 1 to 7, wherein the first network node may be a first BS or a first UE. The second network node may be a second BS or a second UE.

[0207] Aspect 9 is a method according to aspect 8, wherein the first network node may be the first UE. The second network node may be the second BS. The first network node may be configured to operate in a network in which the second network node is configured to send at least one usage probability to a third BS configured to serve the first network node via inter-BS messaging. The usage probability may indicate a first likelihood that the second network node sends at least one Tx beam that interferes with at least one Rx beam in the plurality of Tx-Rx beam pairs.

[0208] Aspect 10 is a method according to aspect 8, wherein the first network node may be the first BS. The second network node may be the second UE. The first network node may be configured to operate in a network in which the second network node is configured to send at least one usage probability to a third BS configured to serve the second network node. The usage probability may indicate a first likelihood that the second network node transmits at least one Tx beam that interferes with at least one Rx beam in the plurality of Tx-Rx beam pairs.

[0209] Aspect 11 is a method according to aspect 8, wherein the first network node may be the first UE. The second network node may be the second UE. The first indication may include a first usage probability that the second network node sends at least one SL Tx beam that interferes with the SL Rx beams in the multiple Tx-Rx beam pairs.

[0210] Aspect 12 is a method according to aspect 8, wherein the first network node may be the first UE, and the network node device may be the second UE. The first network node may be configured to operate in a network in which the second network node is configured to send at least one usage probability to a third BS configured to serve the second network node. The usage probability may indicate a first likelihood that the second network node sends at least one Tx beam that interferes with at least one Rx beam in the plurality of Tx-Rx beam pairs.

[0211] Aspect 13 is a method according to aspect 8, wherein the first network node is the first BS and the second network node is the second BS. The method may further include: in order to send the first indication, sending the first indication of the usage probability to the second network node. The usage probability may indicate a first possibility that the second network node sends at least one Tx beam that interferes with at least one Rx beam in the plurality of Tx-Rx beam pairs.

[0212] Aspect 14 is a method according to any one of aspects 1 to 13, wherein the method may further include: receiving a beam scheduling for at least one Tx-Rx beam pair among the multiple Tx-Rx beam pairs from the second network node. The beam scheduling may include: the second network node using an increased probability of use of a Tx beam associated with the multiple Tx-Rx beam pairs, the Tx beam interfering with at least one Rx beam associated with at least one Tx-Rx beam pair among the multiple Tx-Rx beam pairs. The method may further include: reducing the probability of use of the at least one Rx beam associated with at least one Tx-Rx beam pair among the multiple Tx-Rx beam pairs based on the beam scheduling.

[0213] Aspect 15 is a method according to any one of aspects 1 to 14, wherein the method may further include: receiving a beam scheduling for at least one Tx-Rx beam pair among the multiple Tx-Rx beam pairs from the second network node. The beam scheduling may include an increased usage probability of the second network node using at least one Tx beam associated with the multiple Tx-Rx beam pairs, the at least one Tx beam interfering with at least one Rx beam associated with the multiple Tx-Rx beam pairs. The method may further include: sending a third indication to the second network node to reduce the usage probability of the at least one Tx beam associated with the multiple Tx-Rx beam pairs based on the beam scheduling.

[0214] Aspect 16 is a method for wireless communication at a first network node, the method comprising: receiving from a second network node a first indication of at least one of a usage probability or an interference probability of each Rx beam of the second network node in a plurality of Tx-Rx beam pairs. The usage probability may include a usage metric indicating the likelihood of using the beam. The interference probability may include an interference metric indicating the likelihood that the Tx beam of the first network node interferes with the Rx beam of the second network node. The method may also include: adjusting beam scheduling for at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs based on the received first indication.

[0215] Aspect 17 is a method according to aspect 16, wherein the method may further include: sending a plurality of measurement RSs associated with the plurality of Tx-Rx beam pairs to the second network node. The method may further include: receiving from the second network node a second indication of a measured interference level for each Rx beam in the plurality of Tx-Rx beam pairs or a measured interference level for each Tx beam of the first network node in the plurality of Tx-Rx beam pairs. The method may further include: in order to adjust the beam scheduling for the at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs, adjusting the beam scheduling for the at least one Tx-Rx beam pair in the plurality of Tx-Rx beam pairs based on the second indication. The second indication of the measured interference level for each Rx beam or each Tx beam of the plurality of Tx-Rx beam pairs may be based on the plurality of measurement RSs.

[0216] Aspect 18 is a method according to aspect 17, wherein the method may further include: sending an indication of at least one of the usage probability or the interference probability of each Tx beam in the plurality of Tx-Rx beam pairs to the second network node. The second indication of the measured interference level of each Tx beam may be associated with the sent first indication of at least one of the usage probability or the interference probability of each Tx beam in the plurality of Tx-Rx beam pairs.

[0217] Aspect 19 is a method according to aspect 17, wherein the interference level of each Tx-Rx beam pair in the plurality of Tx-Rx beam pairs may be based on an inter-node CLI.

[0218] Aspect 20 is a method according to any one of aspects 16 to 19, wherein the usage probability may correspond to a first probability over a first time window. The interference probability may correspond to a second probability over a second time window.

[0219] Aspect 21 is a method according to any one of aspects 16 to 20, wherein the usage probability is associated with a usage threshold, and the interference probability is associated with an interference threshold.

[0220] Aspect 22 is a method according to Aspect 21, wherein the first indication of the at least one of the usage probability or the interference probability of each Rx beam in the multiple Tx-Rx beam pairs may be associated with at least one of the usage probability being greater than the usage threshold or the interference probability being greater than the interference threshold.

[0221] Aspect 23 is a method according to any one of aspects 16 to 22, wherein the second network node may be a first BS or a first UE. The first network node may be a second BS or a second UE.

[0222] Aspect 24 is a method according to any one of aspects 16 to 23, wherein the beam scheduling may correspond to a first beam scheduling for the second network node or a second beam scheduling for the first network node.

[0223] Aspect 25 is a method according to any one of Aspects 16 to 24, wherein the method may further include: in order to adjust the beam scheduling for at least one Tx-Rx beam pair among the multiple Tx-Rx beam pairs, adjusting the usage probability of the Rx beam or the Tx beam for at least one Tx-Rx beam pair among the multiple Tx-Rx beam pairs.

[0224] Aspect 26 is an apparatus for performing wireless communications at a network node, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and being configured to implement any one of Aspects 1 to 25 based at least in part on information stored in the memory.

[0225] Aspect 27 is the apparatus of aspect 26, further comprising at least one of an antenna or a transceiver coupled to the at least one processor.

[0226] Aspect 28 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 25.

[0227] Aspect 29 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 25.

Claims

1. A first network node for wireless communication, the first network node comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: Identify a plurality of transmit (Tx)-receive (Rx) pairs associated with the first network node and the second network node at least one of a usage probability or an interference probability of each Rx beam of the first network node in a beam pair, wherein the usage probability comprises a usage metric indicating a likelihood of using the beam, and the interference probability comprises an interference metric indicating a likelihood that a Tx beam of the second network node interferes with an Rx beam of the first network node; and A first indication of at least one of the usage probability or the interference probability of each Rx beam in the plurality of Tx-Rx beam pairs is sent to the second network node.

2. The first network node according to claim 1, wherein the at least one processor is further configured to: receiving, from the second network node, a plurality of measurement reference signals (RS) associated with the plurality of Tx-Rx beam pairs; measuring an interference level of each Rx beam of the first network node in the plurality of Tx-Rx beam pairs or an interference level of each Tx beam of the second network node in the plurality of Tx-Rx beam pairs, wherein at least one of the measured interference levels for each Tx-Rx beam pair in the plurality of Tx-Rx beam pairs is based on the plurality of measurement RSs; and A second indication of the measured interference level of each Rx beam in the plurality of Tx-Rx beam pairs or the measured interference level of each Tx beam in the plurality of Tx-Rx beam pairs is sent to the second network node.

3. The first network node according to claim 2, wherein the at least one processor is further configured to: receive an indication of at least one of the usage probability or the interference probability of each Tx beam in the multiple Tx-Rx beam pairs from the second network node, wherein the second indication of the measured interference level of each Tx beam is associated with the received first indication of the at least one of the usage probability or the interference probability of each Tx beam in the multiple Tx-Rx beam pairs. 4 . The first network node of claim 2 , wherein the interference level of each of the plurality of Tx-Rx beam pairs is based on cross-link interference (CLI) between nodes. 5 . The first network node of claim 1 , wherein the utilization probability corresponds to a first probability over a first time window, and the interference probability corresponds to a second probability over a second time window. 6 . The first network node of claim 1 , wherein the usage probability is associated with a usage threshold and the interference probability is associated with an interference threshold.

7. The first network node according to claim 6, wherein the first indication of the at least one of the usage probability or the interference probability of each Rx beam in the multiple Tx-Rx beam pairs is associated with at least one of the usage probability being greater than the usage threshold or the interference level being greater than the interference threshold.

8. The first network node of claim 1, further comprising a transceiver coupled to the at least one processor, wherein the first network node is a first base station (BS) or a first user equipment (UE), and the second network node is a second BS or a second UE.

9. The first network node according to claim 8, wherein the first network node is the first UE; wherein the second network node is the second BS; and The first network node is configured to operate in a network, in which the second network node is configured to send at least one usage probability to a third BS configured to serve the first network node via inter-BS messaging, wherein the usage probability indicates a first possibility that the second network node sends at least one Tx beam that interferes with at least one Rx beam of the multiple Tx-Rx beam pairs.

10. The first network node according to claim 8, wherein the first network node is the first BS; wherein the second network node is the second UE; and The first network node is configured to operate in a network, in which the second network node is configured to send at least one usage probability to a third BS configured to serve the second network node, wherein the usage probability indicates a first possibility that the second network node sends at least one Tx beam that interferes with at least one Rx beam of the multiple Tx-Rx beam pairs.

11. The first network node according to claim 8, wherein the first network node is the first UE; wherein the second network node is the second UE; and The first indication includes a first usage probability that the second network node sends at least one SL Tx beam that interferes with the side link (SL) Rx beams of the multiple Tx-Rx beam pairs.

12. The first network node according to claim 8, wherein the first network node is the first UE; wherein the second network node is the second UE; and The first network node is configured to operate in a network, in which the second network node is configured to send at least one usage probability to a third BS configured to serve the second network node, wherein the usage probability indicates a first possibility that the second network node sends at least one Tx beam that interferes with at least one Rx beam of the multiple Tx-Rx beam pairs.

13. The first network node according to claim 8, wherein the first network node is the first BS; wherein the second network node is the second BS; and in, In order to send the first indication, the at least one processor is configured to send the first indication of the usage probability to the second network node, wherein the usage probability indicates a first likelihood that the second network node sends at least one Tx beam that interferes with at least one Rx beam of the multiple Tx-Rx beam pairs.

14. The first network node of claim 1 , wherein the at least one processor is further configured to: receiving, from the second network node, a beam schedule for at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs, wherein the beam schedule comprises an increased probability of use of a Tx beam associated with the plurality of Tx-Rx beam pairs by the second network node, the Tx beam interfering with at least one Rx beam associated with at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs; and The use probability of the at least one Rx beam associated with at least one Tx-Rx beam pair among the plurality of Tx-Rx beam pairs is reduced based on the beam scheduling.

15. The first network node of claim 1 , wherein the at least one processor is further configured to: receiving, from the second network node, a beam schedule for at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs, wherein the beam schedule comprises an increased probability of use of at least one Tx beam associated with the plurality of Tx-Rx beam pairs by the second network node, the at least one Tx beam interfering with at least one Rx beam associated with the plurality of Tx-Rx beam pairs; and A third indication to reduce the usage probability of the at least one Tx beam associated with the plurality of Tx-Rx beam pairs is sent to the second network node based on the beam scheduling.

16. A first network node for wireless communication, the first network node comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving, from a second network node, a first indication of at least one of a usage probability or an interference probability for each transmit (Tx)-receive (Rx) beam of the second network node in a plurality of transmit (Tx)-receive (Rx) beam pairs, wherein the usage probability comprises a usage metric indicating a likelihood of using the beam, and the interference probability comprises an interference metric indicating a likelihood that a Tx beam of the first network node interferes with an Rx beam of the second network node; as well as A beam scheduling for at least one Tx-Rx beam pair among the plurality of Tx-Rx beam pairs is adjusted based on the received first indication.

17. The first network node of claim 16, wherein the at least one processor is further configured to: sending a plurality of measurement reference signals (RS) associated with the plurality of Tx-Rx beam pairs to the second network node; and A second indication of a measured interference level for each Rx beam in the multiple Tx-Rx beam pairs or a measured interference level for each Tx beam of the first network node in the multiple Tx-Rx beam pairs is received from the second network node, wherein in order to adjust the beam scheduling for at least one Tx-Rx beam pair in the multiple Tx-Rx beam pairs, the at least one processor is configured to adjust the beam scheduling for at least one Tx-Rx beam pair in the multiple Tx-Rx beam pairs based on the second indication, wherein the second indication of the measured interference level for each Rx beam or each Tx beam of the multiple Tx-Rx beam pairs is based on the multiple measurement RSs.

18. The first network node according to claim 17, wherein the at least one processor is further configured to: send an indication of at least one of the usage probability or the interference probability of each Tx beam in the multiple Tx-Rx beam pairs to the second network node, wherein the second indication of the measured interference level of each Tx beam is associated with the first indication sent of at least one of the usage probability or the interference probability of each Tx beam in the multiple Tx-Rx beam pairs.

19. The first network node of claim 17, wherein the interference level of each of the plurality of Tx-Rx beam pairs is based on inter-node cross-link interference (CLI).

20. The first network node of claim 16, wherein the utilization probability corresponds to a first probability over a first time window and the interference probability corresponds to a second probability over a second time window.

21. The first network node of claim 16, further comprising a transceiver coupled to the at least one processor, wherein the usage probability is associated with a usage threshold and the interference probability is associated with an interference threshold.

22. The first network node according to claim 21, wherein the first indication of the at least one of the usage probability or the interference probability of each Rx beam in the multiple Tx-Rx beam pairs is associated with at least one of the usage probability being greater than the usage threshold or the interference probability being greater than the interference threshold.

23. The first network node of claim 16, wherein the second network node is a first base station (BS) or a first user equipment (UE), and the first network node is a second BS or a second UE.

24. The first network node according to claim 16, wherein the beam scheduling corresponds to a first beam scheduling for the second network node or a second beam scheduling for the first network node.

25. The first network node according to claim 16, wherein in order to adjust the beam scheduling for at least one Tx-Rx beam pair among the multiple Tx-Rx beam pairs, the at least one processor is configured to adjust the usage probability of the Rx beam or the Tx beam of at least one Tx-Rx beam pair among the multiple Tx-Rx beam pairs.

26. A method of wireless communication performed by a first network node, the method comprising: identifying at least one of a usage probability or an interference probability of each transmit (Tx)-receive (Rx) beam of the first network node in a plurality of transmit (Tx)-receive (Rx) beam pairs associated with the first network node and the second network node, wherein the usage probability comprises a usage metric indicating a likelihood of using the beam, and the interference probability comprises an interference metric indicating a likelihood that a Tx beam of the second network node interferes with an Rx beam of the first network node; and A first indication of at least one of the usage probability or the interference probability of each Rx beam in the plurality of Tx-Rx beam pairs is sent to the second network node.

27. The method according to claim 26, further comprising: measuring an interference level of each Rx beam of the first network node in the plurality of Tx-Rx beam pairs or an interference level of each Tx beam of the second network node in the plurality of Tx-Rx beam pairs; receiving, from the second network node, an indication of at least one of the usage probability or the interference probability of each Tx beam in the plurality of Tx-Rx beam pairs; as well as sending a second indication of the measured interference level of each Rx beam in the multiple Tx-Rx beam pairs or the measured interference level of each Tx beam in the multiple Tx-Rx beam pairs to the second network node, wherein the second indication of the measured interference level of each Tx beam is associated with the received indication of at least one of the usage probability or the interference probability of each Tx beam in the multiple Tx-Rx beam pairs.

28. The method according to claim 26, further comprising: receiving, from the second network node, a beam schedule for at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs, wherein the beam schedule comprises an increased probability of use of a Tx beam associated with the plurality of Tx-Rx beam pairs by the second network node, the Tx beam interfering with at least one Rx beam associated with the at least one Tx-Rx beam pair of the plurality of Tx-Rx beam pairs; as well as The use probability of the at least one Rx beam associated with at least one Tx-Rx beam pair among the plurality of Tx-Rx beam pairs is reduced based on the beam scheduling.

29. A method of wireless communication performed by a first network node, the method comprising: receiving, from a second network node, a first indication of at least one of a usage probability or an interference probability for each transmit (Tx)-receive (Rx) beam of the second network node in a plurality of transmit (Tx)-receive (Rx) beam pairs, wherein the usage probability comprises a usage metric indicating a likelihood of using the beam, and the interference probability comprises an interference metric indicating a likelihood that a Tx beam of the first network node interferes with an Rx beam of the second network node; as well as A beam scheduling for at least one Tx-Rx beam pair among the plurality of Tx-Rx beam pairs is adjusted based on the received first indication.

30. The method according to claim 29, further comprising: sending a plurality of measurement reference signals (RS) associated with the plurality of Tx-Rx beam pairs to the second network node; as well as A second indication of a measured interference level for each Rx beam in the multiple Tx-Rx beam pairs or a measured interference level for each Tx beam of the first network node in the multiple Tx-Rx beam pairs is received from the second network node, wherein adjusting the beam scheduling for the at least one Tx-Rx beam pair in the multiple Tx-Rx beam pairs includes adjusting the beam scheduling for the at least one Tx-Rx beam pair in the multiple Tx-Rx beam pairs based on the received second indication, wherein the second indication of the measured interference level for each Rx beam or each Tx beam in the multiple Tx-Rx beam pairs is based on the multiple measurement RSs.

Images