Cross-BWP / CC UE SIM reporting

Abstract

An apparatus, a method, and a computer program product for SIM reporting are provided. An example method may include receiving scheduling information for a PUCCH transmission from a second network entity; and generating SIM information based on the set of full-duplex transmit and receive beam pairs, where the SIM information comprises information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full duplex transmit and receive beam pair comprises a respective transmit beam associated with a respective TCI state and a respective receive beam associated with a respective TCI state.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 17 / 935,066, entitled “CROSS BWP / CC UE SIM REPORT” and filed on September 23, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems with self-interference measurement (SIM) reporting. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. 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] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to receive scheduling information for a physical uplink control channel (PUCCH) transmission from a second network entity. The at least one processor may be configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each corresponding full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state. The at least one processor may be configured to send feedback information corresponding to the transmission to the second network entity in the PUCCH transmission. The at least one processor may be configured to send a SIM report to the second network entity at a position after the feedback information in the PUCCH transmission, wherein the SIM report includes information indicating the SIM information.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a UE are provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each corresponding beam in the set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state, wherein the SIM information is associated with at least one component carrier (CC), and wherein the SIM information is associated with multiple bandwidth parts (BWPs). The at least one processor may be configured to send a SIM report including information indicating the SIM information to a second network entity.

[0009] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a UE are provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each corresponding beam in the set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state, wherein the SIM information is associated with multiple resource blocks (RBs) or multiple subbands (SBs). The at least one processor may be configured to send a SIM report including information indicating the SIM information to a second network entity.

[0010] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a UE are provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each corresponding full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state, and wherein the SIM information is associated with multiple component carriers (CCs). The at least one processor may be configured to send a SIM report including information indicating the SIM information to a second network entity.

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

[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 downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 2Cis 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 uplink (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 and a user equipment (UE) in an access network.

[0018] Figure 4A is a diagram illustrating an example full-duplex operation.

[0019] Figure 4B is a diagram illustrating an example full-duplex operation.

[0020] Figure 4C is a diagram illustrating an example full-duplex operation.

[0021] Figure 5A is a diagram illustrating example communications between a full-duplex network entity and a half-duplex UE.

[0022] Figure 5B is a diagram illustrating example communications between a full-duplex network entity and a full-duplex UE.

[0023] Figure 5C is a diagram illustrating example communications between a half-duplex network entity and a full-duplex UE.

[0024] Figure 5D is a diagram illustrating an example full-duplex integrated access and backhaul (IAB).

[0025] Figure 6 is a diagram illustrating example communications between network entities and a UE.

[0026] Figure 7 is a diagram illustrating an example self-interference measurement (SIM) report.

[0027] Figure 8 is a diagram illustrating an example SIM report with statistical values.

[0028] Fig. 9 is a diagram illustrating example sub-bands (SBs) used for SIM reporting.

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

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

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

[0032] Fig.13 is a flow chart of a method of wireless communication.

[0033] Fig.14 is a flow chart of a method of wireless communication.

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

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

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

[0037] Fig.18 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0038] Fig.19 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

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

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

[0041] As an example, an element, or any part of an element, or any combination of elements, may 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 may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, or any combination thereof.

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

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

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

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

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

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

[0048] 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 referred to as signals) via a wired or wireless transmission medium. Each of the 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 or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0049] 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), or service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signal transmission.

[0050] 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.) according to a functional split (such as that defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

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

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

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

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

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

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

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

[0058] 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 - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "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, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

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

[0061] 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 may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

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

[0063] 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 core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, positioning estimates, and optional speed calculations 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 / location 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.

[0064] 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 in UE 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.

[0065] Reference again Figure 1 In some aspects, the UE 104 may include a SIM component 198. The SIM component 198 may be configured to receive scheduling information for a physical uplink control channel (PUCCH) transmission from a second network entity. The SIM component 198 may be further configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state. The SIM component 198 may be further configured to send feedback information corresponding to the transmission to the second network entity in a PUCCH transmission. The SIM component 198 may be further configured to send a SIM report to the second network entity at a position after the feedback information in the PUCCH transmission, wherein the SIM report includes information indicating the SIM information.

[0066] The SIM component 198 may be configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with a plurality of component carriers (CCs). The SIM component 198 may be further configured to send a SIM report including information indicating the SIM information to a second network entity.

[0067] The SIM component 198 may be configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, wherein the SIM information is associated with at least one component carrier (CC), and wherein the SIM information is associated with a plurality of bandwidth parts (BWPs). The SIM component 198 may be further configured to send a SIM report including information indicating the SIM information to a second network entity.

[0068] The SIM component 198 may be configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs). The SIM component 198 may be further configured to send a SIM report including information indicating the SIM information to a second network entity.

[0069] In certain aspects, the base station 102 may include a SIM component 199. In some aspects, the SIM component 199 may be configured to send scheduling information for a physical uplink control channel (PUCCH) transmission to the first network entity. In some aspects, the SIM component 199 may be configured to receive feedback information corresponding to the transmission from the first network entity in the PUCCH transmission. In some aspects, the SIM component 199 may be configured to receive a self-interference measurement (SIM) report from the first network entity at a position subsequent to the feedback information, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state.

[0070] In some aspects, the SIM component 199 may be configured to establish a communication interface with the first network entity. In some aspects, the SIM component 199 may be configured to receive a SIM report indicating self-interference measurement (SIM) information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with a plurality of component carriers (CCs).

[0071] In some aspects, the SIM component 199 may be configured to establish a communication interface with the first network entity. In some aspects, the SIM component 199 may be configured to receive a SIM report indicating self-interference measurement (SIM) information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with at least one component carrier (CC), and wherein the SIM information is associated with a plurality of bandwidth parts (BWPs).

[0072] In some aspects, the SIM component 199 may be configured to establish a communication interface with the first network entity. In some aspects, the SIM component 199 may be configured to receive a SIM report indicating self-interference measurement (SIM) information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs).

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

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

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

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

[0077] 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 equally sized subframes (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.

[0078]

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

[0080] 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. Therefore, for normal CP and parameter set μ, there are 14 symbols / slot and 2μ slots / 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).

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

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

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

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

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

[0086] 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 transfer 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.

[0087] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided 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 combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state 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 for transmission using a corresponding spatial stream.

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

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

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

[0091] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the 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.

[0092] UL transmissions are processed at the base station 310 in a manner similar to that described in connection 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 the RX processor 370.

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

[0094] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the SIM component 198.

[0095] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Various aspects related to the SIM component 199.

[0096] In some wireless communication systems, full-duplex (FD) capability (supporting simultaneous UL or DL ​​transmissions) may be present at a network entity (such as a base station), a UE, or both a network entity and a UE. For example, at the UE, an UL transmission may be sent from a first panel of the UE while a simultaneous DL reception may be received at a second panel of the UE. The first panel and the second panel may be different panels of an antenna on the UE. In another example, at the base station, an UL reception may be received from a first panel of the base station while a simultaneous DL transmission may be sent at a second panel of the base station. The first panel and the second panel may be different panels of an antenna on the base station.

[0097] By supporting FD, the latency of communication can be potentially reduced. For example, it is possible for the UE to receive DL signals in the time slot assigned to UL, which can achieve latency savings. In addition, by supporting FD, the spectrum efficiency of each cell and each UE can be improved because the resource utilization on the spectrum can be more efficient.

[0098] Figure 4A 4 is a diagram illustrating an example full-duplex operation. Figure 4A As illustrated, the FD TRP 404 of the network entity may be sending DL communications to the FD UE 402 while simultaneously receiving UL communications from the FD UE 402. The FD UE 402 may be sending UL communications to the FDTRP 404 while simultaneously receiving DL communications from the FDTRP 404.

[0099] Figure 4B 4 is a diagram illustrating an example full-duplex operation. Figure 4B As illustrated, the FD TRP 414 of the network entity may be sending DL communications to the first UE 412A while receiving UL communications from the second UE 412B. In some aspects, the first UE 412A and the second UE 412B may be half-duplex (HD) and may not support FD operation. In some aspects, the first UE 412A and the second UE 412B may support FD operation and may be operating in HD mode.

[0100] Figure 4C 4 is a diagram illustrating an example full-duplex operation. Figure 4C As illustrated, the FD UE 422 may be connected to the first TRP 424A and the second TRP 424B simultaneously. The FD UE 422 may be receiving DL communications from the first TRP 424A while sending UL communications to the second TRP 424B. In some aspects, the first TRP 424A and the second TRP 424B may be HD and may not support FD operation. In some aspects, the first TRP 424A and the second TRP 424B may support FD operation and may be operating in HD mode.

[0101] Figure 5A 5 is a diagram illustrating example communications between a full-duplex network entity and a half-duplex UE. Figure 5A 500 in FIG. 5 , two TRPs (TRP 504A and TRP 504B) operating in full-duplex mode and four UEs (UE 502A, UE 502B, UE 502C, and UE 502D) operating in half-duplex mode are shown in the depicted example. When TRP 504A may be simultaneously sending downlink data to UE 502B and receiving uplink data from UE 502A, self-interference between uplink reception and downlink transmission at TRP 504A may occur. For example, a receiver at a TRP may receive the transmitted downlink signal as interference to the uplink signal. Similarly, self-interference between uplink reception and downlink transmission at TRP 504B may occur. In some aspects, because UE 502B may be receiving downlink data and UE 502A may be sending uplink data at the same time, the transmission from UE 502A may cause cross link interference (CLI) to the downlink signal being received by UE 502B. Similarly, the transmission from UE 502C may cause CLI to the downlink signal being received by UE 502D. In addition, because TRP 504B may also be receiving uplink data from UE 502C and sending downlink data to UE 502D, CLI between TRP 504A and TRP 504B may occur.

[0102] Figure 5B 5 is a diagram illustrating example communications between a full-duplex network entity and a full-duplex UE. Figure 5A514A and 514B) operating in full-duplex mode and two UEs (UE 512A and 512B) operating in full-duplex mode. TRP 514A may be sending a downlink transmission to UE 512A while receiving an uplink transmission from UE 512A. TRP 514A may also be sending a downlink transmission to UE 512B. Self-interference from uplink transmission to downlink reception at UE 512A may occur. Self-interference from downlink transmission to uplink reception at TRP 514A may also occur. If TRP 514B is transmitting at the same time, CLI may also occur at TRP 514A.

[0103] Figure 5C 5 is a diagram illustrating an example communication between a half-duplex network entity and a full-duplex UE. Figure 5C As illustrated, TRP 524A and TRP 524B may be operating in HD mode, and UE 522A and UE 522B may be operating in FD mode. UE 522A may be simultaneously sending uplink transmissions to TRP 524A and receiving downlink transmissions from TRP 524B. At the same time, UE 522B may be receiving downlink transmissions from TRP 524B. Self-interference from uplink transmission to downlink reception at UE 522A may occur. CLI may also occur for UE 522B because UE 522B may receive uplink transmissions from UE 522A while receiving downlink transmissions from TRP 524B.

[0104] Figure 5D 5 is a diagram illustrating an example full-duplex integrated access and backhaul (IAB). Figure 5D530 in , two TRPs (TRP 534A and TRP 534B) operating in full-duplex mode and four UEs (UE 532A, UE 532B, UE 532C, and UE 532D) operating in half-duplex mode are shown in the depicted example. TRP 534A and TRP 534B may be IAB nodes belonging to the same parent node 536. When TRP 534A may be simultaneously sending downlink data to UE 532A and receiving uplink data from UE 532B, self-interference between uplink reception and downlink transmission at TRP 534A may occur. For example, a receiver at a TRP may receive the transmitted downlink signal as interference to the uplink signal. Similarly, self-interference between uplink reception and downlink transmission at TRP 534B may occur. In addition, because TRP 534B may also be receiving uplink data from UE 532C and sending downlink data to UE 532D, CLI between TRP 534A and TRP 534B may occur.

[0105] As previously described, an FD network node (such as a base station or UE in a cellular network) can communicate simultaneously with two half-duplex panels using the same radio resources in UL and DL. Due to the simultaneous Tx / Rx nature of FD communication, the UE may experience self-interference caused by signal leakage from the transmitting panel to the receiving panel. Such interference (e.g., self-interference or interference caused by other devices) may affect the quality of communication, or even cause information loss. Therefore, beam separation and other suppression methods can be used to support FD capabilities. There may also be cluster echoes from surrounding objects (which may be referred to as "cluster interference"). Therefore, due to this potential high interference, a UE capable of FD communication may not always operate in FD mode. The aspects provided herein may enable the UE to report self-interference measurements (SIM) to a network entity across different component carriers (CCs) or bandwidth parts (BWPs) of each beam pair, which may enable UE SIM to be mitigated and then FD operating performance to be improved. Carrier aggregation may be a mechanism by which multiple frequency blocks (which may be referred to as "CCs") are assigned to the same UE. As used herein, the term "BWP" may refer to a set of physical RBs that are continuous on a carrier. The RB may be selected from a subset of common RBs for a parameter set. As used herein, the term "self-interference measurement (SIM)" may refer to one or more measurements based on a SIM metric such as a received signal strength indicator (RSSI), a reference signal received power (RSRP), or other measurements and related measurement statistics related to self-interference transmitted from a transmit antenna panel to a receive antenna panel at a device (e.g., a UE operating in full-duplex mode).

[0106] In some aspects, a base station may send a beamformed signal to a UE in one or more directions. The UE may receive a beamformed signal from the base station in one or more receive directions. The UE may also send a beamformed signal to the base station. The base station may receive a beamformed signal from the UE in one or more receive directions. The base station and the UE may perform beam training to determine the best receive direction and transmit direction for each of the base station and the UE. The transmit direction and receive direction of the base station may or may not be the same. The transmit direction and receive direction of the UE may or may not be the same. The term "beam" may be additionally referred to as a "spatial filter". Beamforming may be additionally referred to as "spatial filtering".

[0107] In response to different conditions, the UE may determine to switch beams. The beam at the UE may be used for reception of downlink communications and / or transmission of uplink communications. In some examples, the base station may transmit a transmission that triggers the beam switching of the UE. The TCI state that may correspond to the beam may include quasi-co-location (QCL) information, which the UE may use to derive timing / frequency errors and / or transmit / receive spatial filtering for transmitting / receiving signals. If the properties of the channel for transmitting symbols on one antenna port can be inferred from the channel for transmitting symbols on another antenna port, the two antenna ports are referred to as quasi-co-location. The base station may indicate the TCI state to the UE as a transmission configuration that indicates the QCL relationship between a signal (e.g., a reference signal) and a signal to be transmitted / received. For example, the TCI state may indicate the QCL relationship between a DL RS in an RS set and a PDSCH / PDCCH DM-RS port. The TCI state may provide information about different beam selections used by the UE to send / receive various signals.

[0108] The TCI state may be defined to represent at least one source RS to provide a reference (eg, UE assumption) for determining a quasi co-location (QCL) or spatial filter. For example, the TCI state may define a QCL assumption between a source RS and a target RS.

[0109] Figure 6 is a diagram 600 illustrating example communications between a network entity 604 and a UE 602. In some aspects, the network entity 604 may be implemented as a converged base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. In some aspects, the network entity 604 may be implemented in a converged or monolithic base station architecture, or alternatively in a disaggregated base station architecture, and may include one or more of a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC.

[0110] like Figure 6As illustrated, the UE 602 may receive scheduling information 606 for a PUCCH transmission from a network entity 604. Upon receiving the scheduling information 606 for the PUCCH transmission, the UE 602 may send an ACK / NACK feedback 610 to the network entity 604 in the PUCCH transmission. At 608, the UE 602 may generate SIM information based on at least one SIM metric such as RSSI or RSRP. In some aspects, the UE 602 may autonomously (e.g., without explicit instructions from the network) report the generated SIM information in a SIM report 612 per full-duplex transmit / receive (Tx / Rx) beam pair (e.g., and corresponding TCI state), with additional piggyback bits piggybacked at the end of the ACK / NACK feedback 610 in the PUCCH transmission. In some aspects, the SIM report 612 may be piggybacked at the end of the ACK / NACK feedback 610 without the network entity 604 configuring the size or location of the SIM report 612 in the PUCCH transmission. In some aspects, the SIM information generated at 608 may include SIM information for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs.

[0111] In some aspects, upon receiving the SIM report 612, the network entity 604 may accordingly perform blind detection on the SIM report 612. In some aspects, the network entity 604 may configure one or more bits on the ACK / NACK feedback 610 so that the UE 602 may piggyback the SIM report 612 (which may be the latest version of the SIM information) including an indication of the generated SIM information (e.g., indicating the measured SI metric per full-duplex Tx / Rx beam pair) to the ACK / NACK feedback 610. In some aspects, the network entity may not perform blind detection because the one or more bits carrying the SIM report 612 on the ACK / NACK feedback 610 may be configured by the network entity 604. As used herein, the term "piggybacking" may refer to a mechanism of attaching one or more bits carrying other data to an ACK / NACK transmission. The ACK / NACK transmission may be delayed to piggyback the one or more bits. In some aspects, the network entity 604 may configure the size and location of the SIM report 612 in the PUCCH transmission, and the UE 602 may attach the SIM report 612 to the ACK / NACK feedback 610 based on the size and location configured by the network entity 604. In some aspects, the SIM report 612 may include information indicating the SIM information generated at 608. For example, in some aspects, the SIM report 612 may include a statistical value, i.e., an average, a median, or a weighted average of multiple SIM metrics over a time window (e.g., configured by the network entity 604). In some aspects, to include the information indicating the SIM information generated at 608, the SIM report 612 may include the same information as the SIM information generated at 608. In some aspects, to include the information indicating the SIM information generated at 608, the SIM report 612 may include less information than the SIM information generated at 608. In some aspects, the SIM information generated at 608 may not be reported at a first time instant, and the UE 602 may generate a newer version of the SIM information at a second time instant later than the first time instant. In some aspects, the SIM report 612 may include a statistical value associated with a set of downlink RBs or a set of downlink SBs. In some aspects, the statistical value may include at least one of an average, a median, or a weighted average of a plurality of SIM metrics over a time window (e.g., configured by the network entity 604). In some aspects, the SIM report 612 may include various other statistical values ​​associated with the SIM information generated at 608. In some aspects, the SIM report 612 may be generated based on one or more rules and may include information indicating the SIM information generated at 608. For example, the SIM report 612 may indicate the SIM information generated at 608 and may include one or more bits indicating whether the measured SIM is above a threshold, etc.

[0112] In some aspects, the SIM report 612 may be a cross-CC UE SIM report. In some aspects, at 608, a report of the measured SI metric per full-duplex Tx / Rx beam pair may be measured on multiple CCs, and the UE 602 may generate and signal a multi-CC report (as a SIM report 612) for the network entity 604 to schedule DL and UL communications 614 on different CCs. For example, for a frequency division multiplexing (FDM) FD UE, the UL Tx may be on a first CC (CC1). CC 1 may have a different leakage interference level to the DL RB / SB if the DL BW is at the RB / SB of CC1 compared to the DL BW at the RB / SB of another CC (e.g., CC N). Information about the interference levels at different CCs may help the network entity 604 schedule DL and UL communications 614 on the same or different CCs for the FDM FD UE. In some aspects, the UE 602 may generate SIM information and report on a MAC control element (MAC-CE) active CC (e.g., a CC indicated as active based on the MAC-CE) (in a SIM report 612). In some aspects, the UE 602 may generate SIM information and report on all CCs (in a SIM report 612). In some aspects, the UE 602 may generate SIM information and report on a set of CCs indicated by the network entity 604 (in a SIM report 612). In some aspects, the UE 602 may generate SIM information and report on a set of CCs recommended by the UE 602 (in a SIM report 612).

[0113] In some aspects, the SIM report 612 may be a cross-BWP UE SIM report. In some aspects, a report of the measured SI metric per full-duplex Tx / Rx beam pair may be measured on a BWP for each measured CC, and the UE 602 may generate and signal a multi-BWP report (e.g., SIM report 612) for the network entity 604 to schedule DL and UL communications 614 on different BWPs. For example, for an FDM FD UE, UL Tx may be on a first BWP (BWP1). BWP 1 may have a different leakage interference level to the DL RB / SB if the DL BW is at the RB / SB of BWP1 compared to the DL BW at the RB / SB of another BWP (e.g., BWP N). Information about interference levels at different BWPs may help the network entity 604 schedule DL and UL communications 614 on the same or different BWPs for the FDM FD UE. In some aspects, the UE 602 may generate SIM information and report (in the SIM report 612) on the active BWP. In some aspects, the UE 602 may generate SIM information and report on all BWPs (in the SIM report 612). In some aspects, the UE 602 may generate SIM information and report on a set of BWPs indicated by the network entity 604 (in the SIM report 612). In some aspects, the UE 602 may generate SIM information and report on a set of BWPs recommended by the UE 602 (in the SIM report 612).

[0114] In some aspects, the SIM report 612 may be an N RB / SB UE SIM report, where N is a positive integer. For example, the UE 602 may report N adjacent or non-adjacent DL RBs / SBs around the UL Tx RB. The N DL RBs / SBs may be associated with one or more BWPs or CCs. In some aspects, the N DL RBs / SBs may belong to the same BWP or the same CC. In some aspects, the N DL RBs / SBs may belong to multiple BWPs or multiple CCs. In some aspects, the number of N may be configured by the network entity 604. In some aspects, the SB may be configured by the network entity 604 and may be configured as part of a frequency allocation.

[0115] Figure 7 700 is a diagram illustrating an example SIM report. Figure 7 As illustrated, TRP 704A may correspond to network entity 604 and UE 602 may correspond to UE 702. A second TRP 704B may exist. UE 702 may send SIM report 706, which may correspond to SIM report 612, to TRP 704A.

[0116] Figure 8800 is a diagram illustrating an example SIM report with statistical values. In some aspects, a UE SIM report (e.g., in 830) (which may correspond to SIM report 612) may report the statistical values ​​of the SI metric for each full-duplex Tx / Rx beam pair on one or more adjacent (or non-adjacent) DL SBs (DLSB 804, DL SB 814, and DL SB 824) of each UL Tx (e.g., PUSCH opportunity (e.g., PUSCH opportunity 802, PUSCH opportunity 812, and PUSCH opportunity 822) in a time window (to reflect the different leakage interference levels from the UL Tx to each adjacent DL SB in FDM UE FD mode). The time window may be configured by the network entity 604.

[0117] Fig. 9 9 is a diagram illustrating an example SB for a SIM report (which may correspond to SIM report 612). Fig. 9 As illustrated, there may be DL SB 902, DL SB 906, and DL SB 908 around UL opportunity 904, and there may be a DL SB overlapping with UL opportunity 904. There may be DL SB 912, DL SB 914, and DL SB 918 around UL opportunity 916, and there may be a DL SB overlapping with UL opportunity 916. There may be DL SB 922, DL SB 926, and DL SB 928 around UL opportunity 924, and there may be a DL SB overlapping with UL opportunity 924. The statistics in the SIM report may be reported on the neighboring SBs of each UL opportunity in the time window. For example, for all "neighboring SB+1" SBs (e.g., 902, 914, and 922) of each opportunity, the measured self-interference may be averaged over three UL opportunities, where each UL opportunity has a leaked received signal strength indicator (RSSI) value measured at the neighboring SB+1. In another example, for all UL Tx SBs per opportunity, SI may be averaged over three UL opportunities, each with a reference signal received power (RSRP) value measured at an overlapping DL SB. +Y / -Y adjacent SBs may be averaged together or separately.

[0118] Fig.10 1000 is a flow chart of a method of wireless communication. The method may be performed by a first network entity such as a UE (eg, UE 104, UE 602, or device 1804).

[0119] At 1002, the first network entity may receive scheduling information for PUCCH transmission from the second network entity. For example, UE 602 may receive scheduling information 606 for PUCCH transmission from the second network entity (e.g., network entity 604). In some aspects, 1002 may be performed by SIM component 198.

[0120] At 1004, the first network entity may generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state. For example, the UE 602 may generate (e.g., at 608) SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state. In some aspects, 1004 may be performed by the SIM component 198. In some aspects, the plurality of RBs may be a group of downlink RBs around one or more uplink RBs, or the plurality of SBs may be a group of downlink SBs around one or more uplink RBs. In some aspects, the at least one SIM for each beam in the group of beams may include a statistic associated with the at least one SIM and the group of downlink RBs or the group of downlink SBs. In some aspects, the statistic may include at least one of an average, a median, or a weighted average of a plurality of SIM metrics over a time window (e.g., configured by a second network entity). In some aspects, the number of the plurality of RBs or the plurality of SBs is based on a configuration from a second network entity. In some aspects, the plurality of RBs or the plurality of SBs is configured based on a frequency allocation configuration from a second network entity.

[0121] At 1006, the first network entity may send feedback information corresponding to the transmission to the second network entity in a PUCCH transmission. For example, UE 602 may send feedback information corresponding to the transmission to the second network entity in a PUCCH transmission (e.g., 610). In some aspects, 1006 may be performed by SIM component 198.

[0122] At 1008, the first network entity may send a SIM report to the second network entity at a location after the feedback information in the PUCCH transmission, wherein the SIM report includes information indicating the SIM information. For example, UE 602 may send a SIM report (e.g., SIM report 612) to the second network entity at a location after the feedback information in the PUCCH transmission, wherein the SIM report includes information indicating the SIM information. In some aspects, 1008 may be performed by SIM component 198. In some aspects, the location is adjacent to the feedback information. In some aspects, the first network entity may receive information indicating the location from the second network entity. In some aspects, the first network entity may receive information indicating the size of the SIM report from the second network entity.

[0123] Fig.11 1100 is a flow chart of a method of wireless communication. The method may be performed by a first network entity such as a UE (eg, UE 104, UE 602; device 1804).

[0124] At 1102, the first network entity may generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, and wherein the SIM information is associated with a plurality of CCs. For example, the UE 602 may generate (e.g., at 608) SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, and wherein the SIM information is associated with a plurality of CCs. In some aspects, 1102 may be performed by the SIM component 198. In some aspects, the plurality of CCs may correspond to a set of medium access control (MAC) control element (MAC-CE) active CCs (e.g., CCs activated by MAC-CE). In some aspects, the plurality of CCs may correspond to all CCs associated with the second network entity. In some aspects, the plurality of CCs may correspond to a set of CCs indicated by the second network entity. In some aspects, the plurality of CCs may correspond to a set of CCs recommended by the first network entity. In some aspects, the plurality of RBs may be a set of downlink RBs around one or more uplink RBs, or the plurality of SBs may be a set of downlink SBs around one or more uplink RBs. In some aspects, the at least one SIM for each beam in the set of beams may include a statistic associated with the at least one SIM and the set of downlink RBs or the set of downlink SBs. In some aspects, the statistic may include at least one of an average, a median, or a weighted average of a plurality of SIM metrics over a time window (e.g., configured by the second network entity). In some aspects, the number of the plurality of RBs or the plurality of SBs is based on a configuration from the second network entity. In some aspects, the plurality of RBs or the plurality of SBs is configured based on a frequency allocation configuration from the second network entity.

[0125] At 1104, the first network entity may send a SIM report including information indicating the SIM information to the second network entity. For example, UE 602 may send a SIM report (e.g., SIM report 612) including information indicating the SIM information to the second network entity. In some aspects, 1104 may be performed by SIM component 198.

[0126] Fig.121200 is a flow chart of a method of wireless communication. The method may be performed by a first network entity such as a UE (eg, UE 104, UE 602, or device 1804).

[0127] At 1202, the first network entity may generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, wherein the SIM information is associated with at least one CC, and wherein the SIM information is associated with a plurality of BWPs. For example, the UE 602 may generate (e.g., at 608) SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, wherein the SIM information is associated with at least one CC, and wherein the SIM information is associated with a plurality of BWPs. In some aspects, 1202 may be performed by SIM component 198. In some aspects, the plurality of BWPs may correspond to a set of active BWPs. In some aspects, the plurality of BWPs may correspond to all BWPs associated with the second network entity. In some aspects, the plurality of BWPs may correspond to a set of BWPs indicated by the second network entity. In some aspects, the plurality of BWPs may correspond to a set of BWPs recommended by the first network entity. In some aspects, the plurality of RBs may be a set of downlink RBs around one or more uplink RBs, or the plurality of SBs may be a set of downlink SBs around one or more uplink RBs. In some aspects, the at least one SIM for each beam in the set of beams may include a statistic associated with the at least one SIM and the set of downlink RBs or the set of downlink SBs. In some aspects, the statistic may include at least one of an average, a median, or a weighted average of a plurality of SIM metrics over a time window (e.g., configured by the second network entity). In some aspects, the number of the plurality of RBs or the plurality of SBs is based on a configuration from the second network entity. In some aspects, the plurality of RBs or the plurality of SBs is configured based on a frequency allocation configuration from the second network entity.

[0128] At 1204, the first network entity may send a SIM report including information indicating the SIM information to the second network entity. For example, UE 602 may send a SIM report (e.g., SIM report 612) including information indicating the SIM information to the second network entity. In some aspects, 1204 may be performed by SIM component 198.

[0129] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a first network entity such as a UE (eg, UE 104, UE 602, or device 1804).

[0130] At 1302, the first network entity may generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs). For example, the UE 602 may generate (e.g., at 608) SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs). In some aspects, 1302 may be performed by the SIM component 198. In some aspects, the plurality of RBs is a group of downlink RBs around one or more uplink RBs, or the plurality of SBs is a group of downlink SBs around one or more uplink RBs. In some aspects, the group of downlink RBs or the group of downlink SBs is adjacent to one or more uplink RBs in the frequency domain and overlaps with one or more uplink RBs in a time window. In some aspects, the at least one SIM for each corresponding beam in the group of beams includes a statistical value associated with the at least one SIM and the group of downlink RBs or the group of downlink SBs. In some aspects, the statistical value includes at least one of an average value, a median value, or a weighted average value of multiple SIM metrics over a time window. In some aspects, the number of the plurality of RBs or the plurality of SBs is based on a configuration from a second network entity. In some aspects, the plurality of RBs or the plurality of SBs is configured based on a frequency allocation configuration from a second network entity.

[0131] At 1304, the first network entity may send a SIM report including information indicating the SIM information to the second network entity. For example, UE 602 may send a SIM report (e.g., SIM report 612) including information indicating the SIM information to the second network entity. In some aspects, 1304 may be performed by SIM component 198.

[0132] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a second network entity (eg, base station 102, network entity 604, network entity 1802, network entity 1902).

[0133] At 1402, the network entity may send scheduling information for PUCCH transmission to the first network entity. For example, the network entity 604 may send scheduling information 606 for PUCCH transmission to the first network entity (eg, UE 602). In some aspects, 1402 may be performed by the SIM component 199.

[0134] At 1404, the network entity may receive feedback information corresponding to the transmission from the first network entity in a PUCCH transmission. For example, the network entity 604 may receive feedback information corresponding to the transmission from the first network entity in a PUCCH transmission (e.g., 610). In some aspects, 1404 may be performed by the SIM component 199. In some aspects, the plurality of RBs may be a group of downlink RBs around one or more uplink RBs, or the plurality of SBs may be a group of downlink SBs around one or more uplink RBs. In some aspects, the at least one SIM for each beam in the group of beams may include a statistical value associated with the at least one SIM and the group of downlink RBs or the group of downlink SBs. In some aspects, the statistical value may include at least one of an average, a median, or a weighted average of a plurality of SIM metrics over a time window (e.g., configured by the second network entity). In some aspects, the number of the plurality of RBs or the plurality of SBs is based on a configuration from the second network entity. In some aspects, the plurality of RBs or the plurality of SBs is configured based on a frequency allocation configuration from the second network entity.

[0135] At 1406, the network entity may receive a SIM report from the first network entity at a location after the feedback information, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state. For example, the network entity 604 may receive a SIM report (e.g., SIM report 612) from the first network entity at a location after the feedback information, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state. In some aspects, 1406 may be performed by the SIM component 199. In some aspects, the location is adjacent to the feedback information. In some aspects, the second network entity may send information indicating the location to the first network entity. In some aspects, the second network entity may send information indicating a size of the SIM report to the first network entity.

[0136] Fig.15 1500 is a flow chart of a method of wireless communication. The method may be performed by a second network entity (eg, base station 102, network entity 604, network entity 1802, network entity 1902).

[0137] At 1502, a network entity may establish a communication interface with a first network entity. For example, network entity 604 may establish a communication interface with a first network entity (e.g., UE 602) (e.g., which enables sending scheduling information 606 for PUCCH transmission). In some aspects, 1502 may be performed by SIM component 199.

[0138] At 1504, the network entity may receive a SIM report indicating SIM information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, and wherein the SIM information is associated with a plurality of CCs. For example, the network entity 604 may receive a SIM report (e.g., SIM report 612) indicating SIM information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, and wherein the SIM information is associated with a plurality of CCs. In some aspects, 1504 may be performed by the SIM component 199. In some aspects, the plurality of CCs may correspond to a set of medium access control (MAC) control element (MAC-CE) active CCs. In some aspects, the plurality of CCs may correspond to all CCs associated with the second network entity. In some aspects, the plurality of CCs may correspond to a set of CCs indicated by the second network entity. In some aspects, the plurality of CCs may correspond to a set of CCs recommended by the first network entity. In some aspects, the plurality of RBs may be a set of downlink RBs around one or more uplink RBs, or the plurality of SBs may be a set of downlink SBs around one or more uplink RBs. In some aspects, the at least one SIM for each beam in the set of beams may include a statistic associated with the at least one SIM and the set of downlink RBs or the set of downlink SBs. In some aspects, the statistic may include at least one of an average, a median, or a weighted average of a plurality of SIM metrics over a time window (e.g., configured by the second network entity). In some aspects, the number of the plurality of RBs or the plurality of SBs is based on a configuration from the second network entity. In some aspects, the plurality of RBs or the plurality of SBs are configured based on a frequency allocation configuration from the second network entity.

[0139] Fig.16 1600 is a flow chart of a method of wireless communication. The method may be performed by a second network entity (eg, base station 102, network entity 604, network entity 1802, network entity 1902).

[0140] At 1602, a network entity may establish a communication interface with a first network entity. For example, network entity 604 may establish a communication interface with a first network entity (e.g., UE 602) (e.g., which enables sending scheduling information 606 for PUCCH transmission). In some aspects, 1602 may be performed by SIM component 199.

[0141] At 1604, the network entity may receive a SIM report indicating SIM information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, and wherein the SIM information is associated with at least one CC, and wherein the SIM information is associated with a plurality of BWPs. For example, the network entity 604 may receive a SIM report (e.g., SIM report 612) indicating SIM information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, and wherein the SIM information is associated with at least one CC, and wherein the SIM information is associated with a plurality of BWPs. In some aspects, 1604 may be performed by SIM component 199. In some aspects, the plurality of BWPs may correspond to a set of active BWPs. In some aspects, the plurality of BWPs may correspond to all BWPs associated with the second network entity. In some aspects, the plurality of BWPs may correspond to a set of BWPs indicated by the second network entity. In some aspects, the plurality of BWPs may correspond to a set of BWPs recommended by the first network entity. In some aspects, the plurality of RBs may be a set of downlink RBs around one or more uplink RBs, or the plurality of SBs may be a set of downlink SBs around one or more uplink RBs. In some aspects, the at least one SIM for each beam in the set of beams may include a statistic associated with the at least one SIM and the set of downlink RBs or the set of downlink SBs. In some aspects, the statistic may include at least one of an average, a median, or a weighted average of a plurality of SIM metrics over a time window (e.g., configured by the second network entity). In some aspects, the number of the plurality of RBs or the plurality of SBs is based on a configuration from the second network entity. In some aspects, the plurality of RBs or the plurality of SBs is configured based on a frequency allocation configuration from the second network entity.

[0142] Fig.171700 is a flow chart of a method of wireless communication. The method may be performed by a second network entity (eg, base station 102, network entity 604, network entity 1802, network entity 1902).

[0143] At 1702, a network entity may establish a communication interface with a first network entity. For example, network entity 604 may establish a communication interface with a first network entity (e.g., UE 602) (e.g., which enables sending scheduling information 606 for PUCCH transmission). In some aspects, 1702 may be performed by SIM component 199.

[0144] At 1704, the network entity may receive a SIM report indicating SIM information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, and wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs). For example, the network entity 604 may receive a SIM report (e.g., SIM report 612) indicating SIM information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, and wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs). In some aspects, 1704 may be performed by SIM component 199. In some aspects, the plurality of RBs is a group of downlink RBs around one or more uplink RBs, or the plurality of SBs is a group of downlink SBs around one or more uplink RBs. In some aspects, the group of downlink RBs or the group of downlink SBs is adjacent to one or more uplink RBs in the frequency domain and overlaps with one or more uplink RBs in a time window. In some aspects, the at least one SIM for each corresponding beam in the group of beams includes a statistical value associated with the at least one SIM and the group of downlink RBs or the group of downlink SBs. In some aspects, the statistical value includes at least one of an average value, a median value, or a weighted average value of multiple SIM metrics over a time window. In some aspects, the number of the plurality of RBs or the plurality of SBs is based on a configuration from a second network entity. In some aspects, the plurality of RBs or the plurality of SBs is configured based on a frequency allocation configuration from a second network entity.

[0145] Fig.181800 is a diagram illustrating an example of a hardware implementation for an apparatus 1804. The apparatus 1804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 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 apparatus 1804 may also include one or more subscriber identity module (5IM) cards 1820 and an application processor 1806 coupled to a secure digital (5D) 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, a satellite system 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 supply 1830, and / or a camera 1832. The Bluetooth module 1812, the WLAN module 1814, and the satellite system module 1816 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1824 communicates with the UE 104 and / or 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 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 the 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 herein. The computer-readable medium / memory may 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 following: 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 applications) and include only the cellular baseband processor 1824 and / or the application processor 1806, and in another configuration, the device 1804 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 1804.

[0146] As discussed herein, the SIM component 198 may be configured to receive scheduling information for a physical uplink control channel (PUCCH) transmission from a second network entity. The SIM component 198 may be further configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state. The SIM component 198 may be further configured to send feedback information corresponding to the transmission to the second network entity in a PUCCH transmission. The SIM component 198 may be further configured to send a SIM report to the second network entity at a position after the feedback information in the PUCCH transmission, wherein the SIM report includes information indicating the SIM information.

[0147] The SIM component 198 may be configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with a plurality of component carriers (CCs). The SIM component 198 may be further configured to send a SIM report including information indicating the SIM information to a second network entity.

[0148] The SIM component 198 may be configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, wherein the SIM information is associated with at least one component carrier (CC), and wherein the SIM information is associated with a plurality of bandwidth parts (BWPs). The SIM component 198 may be further configured to send a SIM report including information indicating the SIM information to a second network entity.

[0149] The SIM component 198 may be configured to generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs). The SIM component 198 may be further configured to send a SIM report including information indicating the SIM information to a second network entity.

[0150] The SIM component 198 may be within the cellular baseband processor 1824, the application processor 1806, or both the cellular baseband processor 1824 and the application processor 1806. The SIM component 198 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of these operations. As shown, the device 1804 may include a variety of components configured for various functions. In one configuration, the device 1804 (and specifically the cellular baseband processor 1824 and / or the application processor 1806) includes a component for receiving scheduling information for PUCCH transmission from a second network entity. In some aspects, the apparatus 1804 may also include a component for generating SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with a respective TCI state. In some aspects, the apparatus 1804 may also include a component for sending feedback information corresponding to the transmission to the second network entity in a PUCCH transmission. In some aspects, the apparatus 1804 may also include a component for sending a SIM report to the second network entity at a position after the feedback information in the PUCCH transmission, wherein the SIM report includes information indicating the SIM information. In some aspects, the apparatus 1804 may also include means for generating SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, and wherein the SIM information is associated with a plurality of component carriers (CCs). In some aspects, the apparatus 1804 may also include means for generating SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, wherein the SIM information is associated with at least one component carrier (CC), and wherein the SIM information is associated with a plurality of bandwidth parts (BWPs).In some aspects, the apparatus 1804 may also include a component for generating SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with a respective TCI state, wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs). In some aspects, the apparatus 1804 may also include a component for sending a SIM report including information indicating the SIM information to a second network entity. The component may be a SIM component 198 of the apparatus 1804 configured to perform the functions recited by the component. As described herein, the apparatus 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.

[0151] 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 SIM 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 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of the processors 1912, 1932, 1942 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described herein. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0152] As discussed herein, the SIM component 199 may be configured to send scheduling information for a physical uplink control channel (PUCCH) transmission to the first network entity. In some aspects, the SIM component 199 may be configured to receive feedback information corresponding to the transmission from the first network entity in the PUCCH transmission. In some aspects, the SIM component 199 may be configured to receive a self-interference measurement (SIM) report from the first network entity at a position subsequent to the feedback information, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state.

[0153] In some aspects, the SIM component 199 may be configured to establish a communication interface with the first network entity. In some aspects, the SIM component 199 may be configured to receive a SIM report indicating self-interference measurement (SIM) information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with a plurality of component carriers (CCs).

[0154] In some aspects, the SIM component 199 may be configured to establish a communication interface with the first network entity. In some aspects, the SIM component 199 may be configured to receive a SIM report indicating self-interference measurement (SIM) information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with at least one component carrier (CC), and wherein the SIM information is associated with a plurality of bandwidth parts (BWPs).

[0155] In some aspects, the SIM component 199 may be configured to establish a communication interface with the first network entity. In some aspects, the SIM component 199 may be configured to receive a SIM report indicating self-interference measurement (SIM) information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs).

[0156] The SIM 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 SIM component 199 may be one or more hardware components specifically configured to perform the stated process / algorithms, implemented by one or more processors configured to perform the stated process / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of these operations. 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 sending scheduling information for a PUCCH transmission to the first network entity. In some aspects, the network entity 1902 may also include a component for receiving feedback information corresponding to the transmission from the first network entity in the PUCCH transmission. In some aspects, the network entity 1902 may also include a component for receiving a SIM report from the first network entity at a position subsequent to the feedback information, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with a respective TCI state. In some aspects, the network entity 1902 may also include a component for establishing a communication interface with the first network entity. In some aspects, the network entity 1902 may also include a component for receiving a SIM report indicating SIM information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with a plurality of component carriers (CCs). In some aspects, the network entity 1902 may also include a component for receiving a SIM report indicating SIM information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with the respective TCI state, and wherein the SIM information is associated with at least one component carrier (CC), and wherein the SIM information is associated with multiple bandwidth parts (BWPs).In some aspects, the network entity 1902 may also include means for receiving a SIM report indicating SIM information from the first network entity, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective TCI state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs). The means may be a SIM component 199 of the network entity 1902 configured to perform the functions recited by the means. As described herein, the network entity 1902 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the means.

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

[0158] 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 limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean instantaneous 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 instantaneous time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents that are known or will be known later to those of ordinary skill in the art throughout the elements of the various aspects described in this disclosure are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly recorded using the phrase "component for...".

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

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

[0161] Aspect 1 is a first network entity for wireless communication, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: receive scheduling information for a physical uplink control channel (PUCCH) transmission from a second network entity; generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each corresponding full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state; send feedback information (e.g., ACK or NACK) corresponding to a transmission (e.g., a PDSCH transmission) to the second network entity in the PUCCH transmission; and send a SIM report to the second network entity at a position after the feedback information in the PUCCH transmission, wherein the SIM report includes information indicating the SIM information.

[0162] Aspect 2 is the first network entity according to aspect 1, wherein the location is adjacent to the feedback information.

[0163] Aspect 3 is the first network entity according to any one of aspects 1 to 2, wherein the at least one processor is configured to: receive information indicating the location from the second network entity.

[0164] Aspect 4 is the first network entity according to any one of aspects 1 to 3, wherein the at least one processor is configured to: receive information indicating a size of the SIM report from the second network entity.

[0165] Aspect 5 is the first network entity according to any one of aspects 1 to 4, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

[0166] Aspect 6 is a first network entity for wireless communication, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM measurement for each corresponding full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state, and wherein the SIM information is associated with multiple component carriers (CCs); and send a SIM report including information indicating the SIM information to a second network entity.

[0167] Aspect 7 is the first network entity according to aspect 6, wherein the plurality of CCs correspond to a set of medium access control (MAC) control element (MAC-CE) active CCs.

[0168] Aspect 8 is the first network entity according to any one of aspects 6 to 7, wherein the plurality of CCs correspond to all CCs associated with the second network entity.

[0169] Aspect 9 is the first network entity according to any one of aspects 6 to 8, wherein the plurality of CCs corresponds to a group of CCs indicated by the second network entity.

[0170] Aspect 10 is the first network entity according to any one of aspects 6 to 9, wherein the plurality of CCs corresponds to a set of CCs recommended by the first network entity.

[0171] Aspect 11 is the first network entity according to any one of aspects 6 to 10, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

[0172] Aspect 12 is a first network entity for wireless communication, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM measurement for each corresponding beam in the set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state, wherein the SIM information is associated with at least one component carrier (CC), and wherein the SIM information is associated with multiple bandwidth parts (BWP); and send a SIM report including information indicating the SIM information to a second network entity.

[0173] Aspect 13 is the first network entity according to aspect 12, wherein the plurality of BWPs corresponds to a set of active BWPs.

[0174] Aspect 14 is the first network entity according to any one of aspects 12 to 13, wherein the plurality of BWPs correspond to all BWPs associated with the second network entity.

[0175] Aspect 15 is the first network entity according to any one of aspects 12 to 14, wherein the plurality of BWPs corresponds to a set of BWPs indicated by the second network entity.

[0176] Aspect 16 is the first network entity according to any one of aspects 12 to 15, wherein the plurality of BWPs corresponds to a set of BWPs recommended by the first network entity.

[0177] Aspect 17 is the first network entity according to any one of aspects 12 to 16, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

[0178] Aspect 18 is a first network entity for wireless communication, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: generate SIM information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM measurement for each corresponding beam in the set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state, wherein the SIM information is associated with multiple resource blocks (RBs) or multiple subbands (SBs); and send a SIM report including information indicating the SIM information to a second network entity.

[0179] Aspect 19 is the first network entity according to aspect 18, wherein the plurality of RBs is a group of downlink RBs surrounding one or more uplink RBs, or wherein the plurality of SBs is a group of downlink SBs surrounding the one or more uplink RBs.

[0180] Aspect 20 is a first network entity according to any one of Aspects 18 to 19, wherein the set of downlink RBs or the set of downlink SBs are adjacent to the one or more uplink RBs in the frequency domain, or completely or partially overlap with the one or more uplink RBs in a time window.

[0181] Aspect 21 is a first network entity according to any one of aspects 18 to 20, wherein the SIM information comprises a statistical value associated with the at least one SIM metric and the set of downlink RBs or the set of downlink SBs.

[0182] Aspect 22 is a first network entity according to any one of aspects 18 to 21, wherein the statistical value comprises at least one of an average value, a median value or a weighted average value of multiple SIM metrics of the at least one SIM metric over a time window.

[0183] Aspect 23 is the first network entity according to any one of aspects 18 to 22, wherein the number of the plurality of RBs or the plurality of SBs is based on a configuration from the second network entity.

[0184] Aspect 24 is the first network entity according to any one of aspects 18 to 23, wherein the plurality of RBs or the plurality of SBs are configured based on a frequency allocation from the second network entity.

[0185] Aspect 25 is the first network entity according to any one of aspects 18 to 24, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

[0186] Aspect 26 is a second network entity for wireless communication, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: send scheduling information for a physical uplink control channel (PUCCH) transmission to a first network entity; receive feedback information (e.g., ACK or NACK) corresponding to a transmission (e.g., a PDSCH transmission) from the first network entity in the PUCCH transmission; and receive a self-interference measurement (SIM) report from the first network entity at a position subsequent to the feedback information, wherein the SIM information includes information indicating at least one SIM measurement for each corresponding full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state.

[0187] Aspect 27 is the second network entity according to aspect 26, wherein the location is adjacent to the feedback information.

[0188] Aspect 28 is the second network entity according to any one of aspects 26 to 27, wherein the at least one processor is configured to: send information indicating the location to the first network entity.

[0189] Aspect 29 is a second network entity according to any one of aspects 26 to 28, wherein the at least one processor is configured to: send information indicating a size of the SIM report to the first network entity.

[0190] Aspect 30 is the second network entity according to any one of aspects 26 to 29, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

[0191] Aspect 31 is a second network entity for wireless communication, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: establish a communication interface with a first network entity; and receive a SIM report indicating self-interference measurement (SIM) information from the first network entity, wherein the SIM information includes information indicating at least one SIM measurement for each corresponding full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state, and wherein the SIM information is associated with multiple component carriers (CCs).

[0192] Aspect 32 is the second network entity according to aspect 31, wherein the plurality of CCs corresponds to a set of medium access control (MAC) control element (MAC-CE) active CCs.

[0193] Aspect 33 is a second network entity according to any one of aspects 31 to 32, wherein the plurality of CCs correspond to all CCs associated with the second network entity.

[0194] Aspect 34 is a second network entity according to any one of aspects 31 to 33, wherein the plurality of CCs corresponds to a set of CCs indicated by the second network entity.

[0195] Aspect 35 is a second network entity according to any one of aspects 31 to 34, wherein the plurality of CCs corresponds to a set of CCs recommended by the first network entity.

[0196] Aspect 36 is the second network entity according to any one of aspects 31 to 35, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

[0197] Aspect 37 is a second network entity for wireless communication, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: establish a communication interface with a first network entity; and receive a SIM report indicating self-interference measurement (SIM) information from the first network entity, wherein the SIM information includes information indicating at least one SIM measurement for each corresponding full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state, and wherein the SIM information is associated with at least one component carrier (CC), and wherein the SIM information is associated with multiple bandwidth parts (BWPs).

[0198] Aspect 38 is the second network entity according to aspect 37, wherein the plurality of BWPs corresponds to a set of active BWPs.

[0199] Aspect 39 is the second network entity according to any one of aspects 37 to 38, wherein the plurality of BWPs correspond to all BWPs associated with the second network entity.

[0200] Aspect 40 is a second network entity according to any one of aspects 37 to 39, wherein the plurality of BWPs corresponds to a set of BWPs indicated by the second network entity.

[0201] Aspect 41 is the second network entity according to any one of aspects 37 to 40, wherein the plurality of BWPs corresponds to a set of BWPs recommended by the first network entity.

[0202] Aspect 42 is the second network entity according to any one of aspects 37 to 41, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

[0203] Aspect 43 is a second network entity for wireless communication, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: establish a communication interface with a first network entity; and receive a SIM report indicating self-interference measurement (SIM) information from the first network entity, wherein the SIM information includes information indicating at least one SIM measurement for each corresponding full-duplex transmit and receive beam pair in a set of full-duplex transmit and receive beam pairs, wherein each corresponding full-duplex transmit and receive beam pair includes a corresponding transmit beam associated with a corresponding transmit configuration indicator (TCI) state and a corresponding receive beam associated with a corresponding TCI state, and wherein the SIM information is associated with multiple resource blocks (RBs) or multiple subbands (SBs).

[0204] Aspect 44 is the second network entity according to aspect 43, wherein the plurality of RBs is a group of downlink RBs surrounding one or more uplink RBs, or wherein the plurality of SBs is a group of downlink SBs surrounding the one or more uplink RBs.

[0205] Aspect 45 is a second network entity according to any one of aspects 43 to 44, wherein the set of downlink RBs or the set of downlink SBs are adjacent to the one or more uplink RBs in the frequency domain and overlap with the one or more uplink RBs in the time window.

[0206] Aspect 46 is a second network entity according to any one of aspects 43 to 45, wherein the SIM information comprises a statistical value associated with the at least one SIM metric and the set of downlink RBs or the set of downlink SBs.

[0207] Aspect 47 is a second network entity according to any one of aspects 43 to 46, wherein the statistical value comprises at least one of an average value, a median value, or a weighted average value of multiple SIM metrics of the at least one SIM metric over a time window.

[0208] Aspect 48 is a second network entity according to any one of aspects 43 to 47, wherein the number of the plurality of RBs or the plurality of SBs is based on a configuration.

[0209] Aspect 49 is the second network entity according to any one of aspects 43 to 48, wherein the plurality of RBs or the plurality of SBs are configured based on a frequency allocation.

[0210] Aspect 50 is the second network entity according to any one of aspects 43 to 49, wherein the at least one metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

[0211] Aspect 51 is a method for wireless communication implementing any one of aspects 1 to 25.

[0212] Aspect 52 is an apparatus for wireless communication, comprising: means for implementing any one of aspects 1 to 25.

[0213] Aspect 53 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.

[0214] Aspect 54 is a method for implementing wireless communication of any one of aspects 25 to 50.

[0215] Aspect 55 is an apparatus for wireless communication, comprising: means for implementing any one of aspects 25 to 50.

[0216] Aspect 56 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 25 to 50.

Claims

1. A first network entity for wireless communication, comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving scheduling information sent for a physical uplink control channel (PUCCH) from a second network entity; generating self-interference measurement (SIM) information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state; sending, in the PUCCH sending, feedback information corresponding to the sending to the second network entity; as well as A SIM report is sent to the second network entity at a position after the feedback information in the PUCCH transmission, wherein the SIM report includes information indicating the SIM information. The first network entity according to claim 1 , wherein the location is adjacent to the feedback information. 3 . The first network entity of claim 1 , wherein the at least one processor is configured to receive information indicating the location from the second network entity. 4 . The first network entity of claim 1 , wherein the at least one processor is configured to receive information indicating a size of the SIM report from the second network entity.

5. The first network entity of claim 1, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

6. A first network entity for wireless communication, comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: generating self-interference measurement (SIM) information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective full-duplex transmit and receive beam pair in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, and wherein the SIM information is associated with a plurality of component carriers (CCs); and A SIM report including information indicative of the SIM information is sent to a second network entity.

7. The first network entity of claim 6, wherein the plurality of CCs corresponds to a set of medium access control (MAC) control element (MAC-CE) active CCs.

8. The first network entity of claim 6, wherein the plurality of CCs correspond to all CCs associated with the second network entity.

9. The first network entity of claim 6, wherein the plurality of CCs corresponds to a group of CCs indicated by the second network entity.

10. The first network entity of claim 6, wherein the plurality of CCs corresponds to a set of CCs recommended by the first network entity.

11. The first network entity of claim 6, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

12. A first network entity for wireless communication, comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: generating self-interference measurement (SIM) information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, wherein the SIM information is associated with at least one component carrier (CC), and wherein the SIM information is associated with a plurality of bandwidth parts (BWPs); as well as A SIM report including information indicative of the SIM information is sent to a second network entity.

13. The first network entity of claim 12, wherein the plurality of BWPs corresponds to a set of active BWPs.

14. The first network entity of claim 12, wherein the plurality of BWPs correspond to all BWPs associated with the second network entity.

15. The first network entity of claim 12, wherein the plurality of BWPs corresponds to a set of BWPs indicated by the second network entity.

16. The first network entity of claim 12, wherein the plurality of BWPs corresponds to a set of BWPs recommended by the first network entity.

17. The first network entity of claim 12, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

18. A first network entity for wireless communication, comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: generating self-interference measurement (SIM) information based on a set of full-duplex transmit and receive beam pairs, wherein the SIM information includes information indicating at least one SIM metric for each respective beam in the set of full-duplex transmit and receive beam pairs, wherein each respective full-duplex transmit and receive beam pair includes a respective transmit beam associated with a respective transmit configuration indicator (TCI) state and a respective receive beam associated with a respective TCI state, wherein the SIM information is associated with a plurality of resource blocks (RBs) or a plurality of subbands (SBs); and A SIM report including information indicative of the SIM information is sent to a second network entity.

19. The first network entity according to claim 18, wherein the plurality of RBs is a group of downlink RBs surrounding one or more uplink RBs, or wherein the plurality of SBs is a group of downlink SBs surrounding the one or more uplink RBs.

20. The first network entity according to claim 19, wherein the set of downlink RBs or the set of downlink SBs are adjacent to the one or more uplink RBs in the frequency domain, or completely or partially overlap with the one or more uplink RBs in a time window.

21. The first network entity of claim 19, wherein the SIM information comprises a statistical value associated with the at least one SIM metric and the set of downlink RBs or the set of downlink SBs.

22. The first network entity of claim 21, wherein the statistical value comprises at least one of an average value, a median value, or a weighted average value of a plurality of SIM metrics of the at least one SIM metric over a time window.

23. The first network entity of claim 18, wherein a number of the plurality of RBs or the plurality of SBs is based on a configuration from the second network entity.

24. The first network entity of claim 18, wherein the plurality of RBs or the plurality of SBs are configured based on a frequency allocation from the second network entity.

25. The first network entity of claim 18, wherein the at least one SIM metric comprises at least one of: a reference signal received power (RSRP) or a received signal strength indicator (RSSI).

Images