Self-interference measurement reporting

Abstract

A UE in FD operation can receive scheduling information including timing information for reporting a self-interference measurement, and transmit a self-interference measurement report including the self-interference measurement based on the scheduling information received from a network node. The UE can send a request for the self-interference measurement report to the network node prior to receiving the scheduling information.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 17 / 819,604, filed on August 12, 2022, entitled “SELF-INTERFERENCE MEASUREMENT REPORT,” 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 communications including network configuration and / or user equipment (UE) requesting self-interference measurement reports at the UE. 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 are provided. The apparatus may include a user equipment (UE) configured to receive scheduling information including timing information for reporting self-interference measurements, and to send a self-interference measurement report including the self-interference measurement based on the scheduling information received from a network node.

[0008] In one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus may include a network node configured to send scheduling information for a UE, the scheduling information including timing information for reporting a self-interference measurement, and receive a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node.

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

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

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

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

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

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

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

[0016] Figure 4A , Figure 4B and Figure 4C is an example of a different type of full-duplex (FD) mode for wireless communications.

[0017] Figure 5A , Figure 5B , Figure 5C and Figure 5D is an example of FD deployment for wireless communication.

[0018] Figure 6 is the FD configuration for self-interference measurement at the UE side.

[0019] Figure 7 is a call flow diagram of a method of wireless communication.

[0020] Figure 8 is a flow chart of a method of wireless communication.

[0021] Fig. 9 is a flow chart of a method of wireless communication.

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

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

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

[0025] Fig.13 is a diagram illustrating an example of a hardware implementation for an example network entity.

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

[0027] The network may instruct a user equipment (UE) operating in full duplex (FD) mode to obtain a self-interference measurement report and transmit it to a network node. In some aspects of the present disclosure, the instruction may include timing information for reporting the self-interference measurement report in the scheduling information for uplink transmission. The UE may be configured to receive scheduling information including timing information for reporting the self-interference measurement, and to send a self-interference measurement report including the self-interference measurement based on the scheduling information. The network may reduce or save communication overhead by using scheduling information associated with uplink transmission to instruct the self-interference measurement report.

[0028] Additionally, the UE may transmit a request for a self-interference measurement report to initiate a self-interference measurement report.

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

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

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

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

[0033] 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 various 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.

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

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

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

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

[0038] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface 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.

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

[0040] 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.) at least in part according to a functional split such as those 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.

[0041] 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 or physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, 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).

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

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

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

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

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

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

[0048] 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, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0049] The 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 frequency 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, currently higher frequency bands are being explored to extend 5G NR operation 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.

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

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

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

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

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

[0055] Reference again Figure 1 In some aspects, the UE 104 may include a self-interference measurement reporting component 198, which is configured to receive scheduling information including timing information for reporting self-interference measurements, and send a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. In some aspects, the base station 102 may include a self-interference measurement report configuration component 199, which is configured to send scheduling information for the UE, the scheduling information including timing information for reporting self-interference measurements, and receive a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. Although the following description may focus on 5GNR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0056] 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 2DFIG280 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 may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full 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). Note that the following description also applies to the 5G NR frame structure as TDD.

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

[0058]

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

[0060] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example 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).

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

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

[0063] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer 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.

[0064] like Figure 2C As 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.

[0065] Figure 2DExamples 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.

[0066] Figure 3 370 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.

[0067] 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 onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel 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.

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

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

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

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

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

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

[0074] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform a combined Figure 1 198. At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform a combined Figure 1 Various aspects of the self-interference measurement report configuration component 199.

[0075] In some aspects, at least one base station and one or more UEs may support various duplex communication modes, including full-duplex (FD) mode and half-duplex (HD) mode. FD mode may refer to simultaneous communication of one or more uplink (UL) transmissions or one or more downlink (DL) communications at a base station or UE, which may be associated with various aspects of the process within the same frequency, different frequency sub-bands, or partially overlapping in the frequency domain. HD mode may support sending or receiving information in one direction at a time without overlapping uplink and downlink communications.

[0076] In FD mode, at least one base station and one or more UEs may send and receive UL / DL communications simultaneously (e.g., at least partially overlapping in time). In one example, a base station in FD mode and a UE in FD mode may send and receive UL / DL communications simultaneously. That is, the base station may transmit DL transmissions to the UE while the UE transmits UL transmissions to the base station. In another example, a base station in FD mode may simultaneously send UL / DL communications to multiple UEs and receive UL / DL communications from multiple UEs. That is, the base station may transmit DL transmissions to a first UE while receiving UL transmissions from a second UE. In yet another example, a UE in FD mode may receive DL transmissions from a first base station while transmitting UL transmissions to a second base station. That is, a UE in FD mode may receive DL transmissions from a first base station while transmitting UL transmissions to a second base station.

[0077] The FD capability may exist at the base station or the UE. That is, at least one of the base station or the UE may have the ability to support FD mode communications. For example, the UE may have multiple panels facing different directions (e.g., two antennas facing the front of the UE and two antennas facing the back of the UE), and the antenna panel facing the front may be configured to send / receive beams that are different from the beams sent / received via the antenna panel facing the back. Therefore, the UE may have the ability to simultaneously support UL transmission from one antenna panel and DL reception in another antenna panel. For another example, the base station may have the ability to support UL reception by forming a first beam at a first set of antenna panels and simultaneously support DL transmission by forming a second beam at a second set of antenna panels.

[0078] In some aspects, the FD capability of one or more UEs or base stations may depend on various factors, such as interference, beam separation, antenna separation, isolation, etc. In one aspect, one or more UEs or base stations may support FD mode communication based on the ability to perform beam separation. For example, a base station may determine that a UE can support FD mode communication based on the UE's ability to separate UL beams and DL beams. On the other hand, one or more UEs or base stations may support FD mode communication based on self-interference between DL transmissions and / or UL transmissions. That is, the self-interference caused by the simultaneous transmission of DL / UL signals may hinder the UE's ability to support FD mode communication. On the other hand, clutter echoes caused by the reflection of radio signals at surfaces or obstacles may affect the UE's ability to support FD mode communication.

[0079] FD mode communication can reduce network latency and increase spectrum efficiency by exchanging uplink and downlink communications at overlapping times and in the same frequency band. For example, a UE or base station can receive a signal without waiting until the transmission ends, which can reduce latency. FD communication can also enable an increase in spectrum efficiency, which refers to the rate of information that can be exchanged on a given spectrum or bandwidth, and improves the efficiency of resource utilization. The base station can operate in FD mode, which can enable an increase in spectrum efficiency per cell. Each UE can operate in FD mode, which can enable an increase in spectrum efficiency per UE.

[0080] Figure 4A , Figure 4B and Figure 4C400, 420 and 440 are examples of different types of FD modes for wireless communication. Due to the simultaneous Tx / Rx nature of full-duplex communication, a UE or network node may experience self-interference caused by signal leakage from its local transmitter to its local receiver. In addition, the UE or network node may also experience interference from other devices, such as transmissions from a second UE or a second network node. Such interference (e.g., self-interference or interference caused by other devices) may affect the quality of communication, or even cause information loss. The first example 400 illustrates a first network node 402 and a second network node 404 and a UE 406 in FD mode. The first network node 402 and the second network node 404 may be in FD mode or HD mode. The UE 406 may have FD capabilities to simultaneously communicate UL / DL transmissions with the first network node 402 and the second network node 404. For example, the UE 406 may receive DL transmissions from the first network node 402 and simultaneously send UL transmissions to the second network node 404. UE 406 may receive DL transmissions from first network node 402 via first antenna panel 401a, and transmit UL transmissions to second network node 404 via second antenna panel 401b. Here, first network node 402 may be a first TRP, and second network node 404 may be a second TRP. UE 406 may experience self-interference due to receiving at least a portion of an uplink signal while receiving a downlink signal, e.g., when UE 406 is attempting to receive a signal from another network node, the UE's uplink signal to second network node 404 may leak to (e.g., be received by) the UE's receiver. UE 406 may experience additional interference due to signals from other devices.

[0081] The second example 420 illustrates a network node 422 operating in FD mode and a first UE 426 and a second UE 428. In one aspect, when sending a DL transmission to the first UE 426 in FD mode, the network node 422 in FD mode can simultaneously (e.g., at least partially overlapping in time) receive an UL signal from the second UE 428. The first UE 426 and the second UE 428 can also operate in FD mode or can operate in HD mode. For example, the network node 422 can send a DL transmission to the first UE 426 and receive a UL transmission from the second UE 428 at the same time. The network node 422 can send a DL transmission to the first UE 426 via a DL beam and receive a UL transmission from the second UE 428 via a UL beam. Due to receiving at least a portion of the downlink signal while receiving the uplink signal, the network node 422 may experience self-interference, for example, when the network node 422 is attempting to receive a signal from another UE, the network node's downlink signal to the first UE 426 may leak to (e.g., be received by) the network node's receiver. The network node 422 may experience additional interference due to signals from other devices.

[0082] The third example 440 illustrates a network node 442 in FD mode and a UE 446 in FD mode. In one aspect, the network node 442 in FD mode may receive uplink transmissions simultaneously (e.g., at least partially overlapping in time) while transmitting downlink transmissions with the UE 446. In one aspect, the network node 442 and the UE 446 may support FD mode. For example, the network node 442 may send DL transmissions to the UE 446 and receive UL transmissions from the UE 446 simultaneously. For example, the network node 442 may send DL transmissions to the UE 446 via a DL beam and receive UL transmissions from the UE 446 via a UL beam. The network node 442 and / or the UE 446 may experience self-interference, for example, as combined with Figure 4A and Figure 4B As described in the examples.

[0083] Figure 5A , Figure 5B , Figure 5C and Figure 5Dis an example of an FD deployment for wireless communications. An FD deployment may include various combinations of FD network nodes or at least one of HD network nodes configured with at least one of an FD UE or an HD UE. At least one network node or UE may experience interference, such as cross-link interference (CLI) or self-interference. In one aspect, when one network entity transmits a Tx beam and another network entity is receiving an Rx beam, CLI may occur between more than one network entity (e.g., a network node or UE). On the other hand, when a network entity (e.g., a network node or UE) operating in FD mode transmits a Tx beam while receiving an Rx beam, self-interference may occur at the network entity. The transmitted signal may cause self-interference to the received signal. Such interference may be more common when transmitting or receiving resources in FR2 because many wireless devices can use these resources. Such interference may prevent the receiving device from successfully decoding the received signal.

[0084] Figure 5A The first FD deployment 500 includes network nodes (e.g., a first network node 502 and a second network node 504) and UEs (e.g., a first UE 510, a second UE 512, a third UE 514, and a fourth UE 516). The first FD deployment 500 may illustrate an example of a wireless communication system including a first cell having the first network node 502 communicating with the first UE 510 and the second UE 512, which may experience CLI when the first network node 502 operates in the FD mode, and a second cell having the second network node 504 communicating with the third UE 514 and the fourth UE 516, which may experience CLI when the second network node 504 operates in the FD mode.

[0085] In one aspect, each of the first UE 510 and the second UE 512 may be an HD UE, and the first network node 502 may be an FD network node. The first network node 502 may include one or more TRPs. The first network node 502 may have at least two antenna panels: a first antenna panel configured to communicate with the first UE 510 and a second antenna panel configured to communicate with the second UE 512. Each of these antenna panels may operate independently of one another. The first network node 502 may be configured to communicate with the first UE 510 and the second UE 512 simultaneously (i.e., the communication transmission has overlapping resources). In one example, the first network node 502 may perform Rx by receiving a signal from the first UE 510, and may perform Rx by receiving a signal from the second UE 512 at the same time (i.e., simultaneous reception mode). In another example, the first network node 502 may perform Tx by sending a signal to the first UE 510, and may perform Tx by sending a signal to the second UE 512 at the same time (e.g., simultaneous transmission mode). In another example, the first network node 502 may perform Tx by transmitting a signal to the first UE 510, and may simultaneously perform Rx by receiving a signal from the second UE 512. In another example, the first network node 502 may perform Rx by receiving a signal from the first UE 510, and may simultaneously perform Tx by transmitting a signal to the second UE 512. In the case where the first network node 502 performs Rx by receiving a signal from the first UE 510 and performs Tx by transmitting a signal to the second UE 512, the first network node 502 may experience self-interference from Rx and Tx, and the second UE 512 may experience CLI from uplink transmission by the first UE 510.

[0086] On the other hand, each of the third UE 514 and the fourth UE 516 may be an HD UE, and the second network node 504 may be an FD network node. The second network node 504 may include one or more TRPs. The second network node 504 may have at least two antenna panels: a first antenna panel configured to communicate with the third UE 514 and a second antenna panel configured to communicate with the fourth UE 516. Each of these antenna panels may operate independently of each other. The second network node 504 may be configured to communicate with the third UE 514 and the fourth UE 516 simultaneously (i.e., the communication transmission has overlapping resources). In one example, the second network node 504 may perform Rx by receiving a signal from the third UE 514, and may perform Rx by receiving a signal from the fourth UE 516 at the same time (i.e., simultaneous reception mode). In another example, the second network node 504 may perform Tx by sending a signal to the third UE 514, and may perform Tx by sending a signal to the fourth UE 516 at the same time (e.g., simultaneous transmission mode). In another example, the second network node 504 may perform Tx by transmitting a signal to the third UE 514, and may simultaneously perform Rx by receiving a signal from the fourth UE 516. In another example, the second network node 504 may perform Rx by receiving a signal from the third UE 514, and may simultaneously perform Tx by transmitting a signal to the fourth UE 516. In the case where the second network node 504 performs Rx by receiving a signal from the third UE 514 and performs Tx by transmitting a signal to the fourth UE 516, the second network node 504 may experience self-interference from Rx and Tx, and the fourth UE 516 may experience CLI from uplink transmission by the third UE 514.

[0087] Figure 5B 5 is a second FD deployment 520 including FD network nodes (e.g., first network node 522 and second network node 524) and FD UEs (e.g., first UE 530 and second UE 532). The second FD deployment 520 may illustrate an example of a wireless communication system including a first cell having a first network node 522 in communication with the first UE 530 and the second UE 532, which may experience CLI when the first network node 522 operates in FD mode. The first network node 522 may experience CLI from the second network node 524.

[0088] The first UE 530 may be an FD UE, the second UE 532 may be an HD UE, and the first network node 522 may be an FD network node. The first network node 522 may include one or more TRPs. The first network node 522 may have at least three antenna panels: a first antenna panel and a second antenna panel configured to communicate with the first UE 530, and a third antenna panel configured to communicate with the second UE 532. Each of these antenna panels may operate independently of one another. The first network node 522 may be configured to communicate with the first UE 530 and the second UE 532 simultaneously (i.e., the communication transmission has overlapping resources). In one example, the first network node 522 may perform Rx and Tx (e.g., FD mode) by receiving a signal from the first UE 530 and sending another signal to the first UE 530, and may perform Rx simultaneously by receiving a signal from the second UE 532 (i.e., simultaneous reception mode). In another example, the first network node 522 may perform Rx and Tx (e.g., FD mode) by receiving a signal from the first UE 530 and transmitting another signal to the first UE 530, and may simultaneously perform Tx (e.g., simultaneous transmission mode) by transmitting a signal to the second UE 532. The first network node 522 may experience self-interference from overlapping Rx and Tx, and the second UE 532 may experience CLI from uplink transmission performed by the first UE 530. In addition, the first UE 530 operating in the FD mode may experience self-interference from overlapping Rx and Tx at the first UE 530 side.

[0089] Figure 5C 5 is a third FD deployment 540 including an HD network node (e.g., a first network node 542) and an FD UE (e.g., a first UE 550). For example, the first UE 550 may be connected to the first network node 542 and the second network node 544 using a multi-TRP (mTRP) configuration. Here, the first network node 542 and the second network node 544 may be TRPs, and the first UE 550 may be configured to communicate with a network (e.g., a base station) through multiple TRPs including the first network node 542 and the second network node 544.

[0090] The first UE 550 may have at least two antenna panels: a first antenna panel configured to communicate with the first network node 542 and a second antenna panel configured to communicate with the second network node 544. The first UE 550 may concurrently send an uplink signal to the second network node 544 while receiving a downlink signal from the first network node 542. Due to the simultaneous communication of the first signal and the second signal, the first UE 550 may experience self-interference. For example, an uplink signal sent by the UE's transmitter may be leaked to (or received by) the UE's receiver, and the first UE 550 may experience self-interference at a receiving antenna that receives a downlink signal from the first network node 542, the self-interference being caused by some uplink signals sent to the second network node 544. The first UE 550 may cause additional interference (CLI) to the second UE 552.

[0091] The second network node 544 may have at least two antenna panels: a first antenna panel configured to communicate with the first UE 550 and a second antenna panel configured to communicate with the second UE 552. Each of these antenna panels may operate independently of one another. The second network node 544 may be configured to communicate with the first UE 550 and the second UE 552 simultaneously (i.e., the communication transmission has overlapping resources). In one example, the second network node 544 may perform Rx by receiving a signal from the first UE 550, and may perform Tx simultaneously by transmitting a signal to the second UE 552. In the case where the second network node 544 performs Rx by receiving a signal from the first UE 550 and performs Tx by transmitting a signal to the second UE 552 simultaneously, the second network node 544 may experience self-interference from Rx and Tx, and the second UE 552 may experience CLI from the uplink transmission performed by the first UE 550.

[0092] Figure 5D5 is a fourth FD deployment 560 including FD IAB nodes (e.g., a first IAB node 562 and a second IAB node 564). The fourth FD deployment 560 may illustrate an example of a wireless communication system including a first cell having a first IAB node 562 in communication with a first UE 570 and a second UE 572, which may experience CLI when the first IAB node 562 operates in FD mode, and a second cell having a second IAB node 564 in communication with a third UE 574 and a fourth UE 576, which may experience CLI when the second IAB node 564 operates in FD mode. In one aspect, each of the first UE 570 and the second UE 572 may be an HD UE and the first IAB node 562 may be an FD IAB, and each of the third UE 574 and the fourth UE 576 may be an HD UE and the second IAB node 564 may be an FD IAB. The first IAB node 562 and the second IAB node 564 may be connected to a parent node 561 (eg, a base station or a parent IAB node), and the first IAB node 562 may experience a CLI from the second IAB node 564 .

[0093] The first IAB node 562 and the second IAB node 564 may be components of a base station. The first IAB node 562 and the second IAB node 564 may have an IAB mobile terminal (IAB MT) that may be configured to communicate with the parent node 561, and may have an IAB DU that may be configured to communicate with its child UEs (e.g., the first UE 570, the second UE 572, the third UE 574, or the fourth UE 576). Each of the IAB MT and the IAB DU may have an antenna panel that operates independently of other antenna panels.

[0094] The first IAB node 562 may be configured to simultaneously operate its child link and parent link. In one aspect, the first IAB node 562 may perform Rx with its IAB MT by receiving a signal from the parent node 561, and may perform Rx with its IAB DU by receiving a signal from its child UE (e.g., the first UE 570) (i.e., simultaneous reception mode). On the other hand, the first IAB node 562 may perform Tx with its IAB MT by sending a signal to the parent node 561, and may perform Tx with its IAB DU by sending a signal to its child UE (e.g., the first UE 570) (e.g., simultaneous transmission mode). On the other hand, the first IAB node 562 may perform Tx with its IAB MT by sending a signal to the parent node 561, and may perform Rx with its IAB DU by receiving a signal from its child UE (e.g., the first UE 570) (e.g., simultaneous transmission mode). On the other hand, the first IAB node 562 can perform Rx with its IAB MT by receiving signals from the parent node 561, and can simultaneously perform Tx with its IAB DU by sending signals to its child UE (e.g., the first UE 570). The simultaneous transmissions may have overlapping resources (e.g., overlapping time periods and overlapping frequency bands).

[0095] In one aspect, the first IAB node 562 can support simultaneous operation of each of the aforementioned four aspects of FD transmission. When the first IAB node 562 is in a simultaneous transmission mode or a simultaneous reception mode, the first IAB node 562 does not experience self-interference. However, when one panel of the first IAB node 562 operates in Tx mode and another panel of the first IAB node 562 operates in Rx mode, the first IAB node 562 may experience self-interference. For example, an IAB MT may operate in Rx mode by receiving a signal from a parent node 561, while an IAB DU operates in Tx mode by sending a signal to its child UE (e.g., the first UE 570). When the first IAB node 562 acts as an intermediate layer between its child UE (e.g., the first UE 570) and the parent node 561, this situation may occur when the child UE (e.g., the first UE 570) performs DL Rx from the parent node 561 via the first IAB node 562. If the IAB MT receives a signal from the parent node 561 while the IAB DU transmits a signal to its child UE (e.g., the first UE 570), self-interference may occur at the first IAB node 562. In other words, the transmitted signal from the IAB DU to its child UE (e.g., the first UE 570) may interfere with the first IAB node 562 successfully decoding the received signal from the parent node 561 at the IAB MT.

[0096] On the other hand, the first IAB node 562 (e.g., the IAB DU of the first IAB node 562) may have at least two antenna panels: a first antenna panel configured to communicate with the first UE 570 and a second antenna panel configured to communicate with the second UE 572. Each of these antenna panels can operate independently of each other. The first IAB node 562 may be configured to communicate with the first UE 570 and the second UE 572 simultaneously (i.e., the communication transmission has overlapping resources). In one example, the first IAB node 562 can perform Rx by receiving a signal from the first UE 570, and can perform Rx by receiving a signal from the second UE 572 at the same time (i.e., simultaneous reception mode). In another example, the first IAB node 562 can perform Tx by sending a signal to the first UE 570, and can perform Tx by sending a signal to the second UE 572 at the same time (e.g., simultaneous transmission mode). In another example, the first IAB node 562 may perform Tx by transmitting a signal to the first UE 570, and may simultaneously perform Rx by receiving a signal from the second UE 572. In another example, the first IAB node 562 may perform Rx by receiving a signal from the first UE 570, and may simultaneously perform Tx by transmitting a signal to the second UE 572. In the case where the first IAB node 562 performs Rx by receiving a signal from the first UE 570 and performs Tx by transmitting a signal to the second UE 572, the first IAB node 562 may experience self-interference from Rx and Tx, and the second UE 572 may experience CLI from uplink transmission by the first UE 570.

[0097] On the other hand, the second IAB node 564 (e.g., the IAB DU of the second IAB node 564) may have at least two antenna panels: a first antenna panel configured to communicate with the third UE 574 and a second antenna panel configured to communicate with the fourth UE 576. Each of these antenna panels can operate independently of each other. The second IAB node 564 may be configured to communicate with the third UE 574 and the fourth UE 576 simultaneously (i.e., the communication transmission has overlapping resources). In one example, the second IAB node 564 can perform Rx by receiving a signal from the third UE 574, and can perform Rx by receiving a signal from the fourth UE 576 at the same time (i.e., simultaneous reception mode). In another example, the second IAB node 564 can perform Tx by sending a signal to the third UE 574, and can perform Tx by sending a signal to the fourth UE 576 at the same time (e.g., simultaneous transmission mode). In another example, the second IAB node 564 may perform Tx by transmitting a signal to the third UE 574, and may simultaneously perform Rx by receiving a signal from the fourth UE 576. In another example, the second IAB node 564 may perform Rx by receiving a signal from the third UE 574, and may simultaneously perform Tx by transmitting a signal to the fourth UE 576. In the case where the second IAB node 564 performs Rx by receiving a signal from the third UE 574 and performs Tx by transmitting a signal to the fourth UE 576, the second IAB node 564 may experience self-interference from Rx and Tx, and the fourth UE 576 may experience CLI from uplink transmission by the third UE 574.

[0098] Figure 6 600 is an FD configuration for self-interference measurement at the UE side. The FD configuration 600 includes a first network node 602, a second network node 604, and a UE 610. For example, the UE 610 may be connected to the first network node 602 and the second network node 604 using an mTRP configuration. Here, the first network node 602 and the second network node 604 may be TRPs, and the UE 610 may be configured to communicate with a network (e.g., a base station) through a plurality of TRPs including the first network node 602 and the second network node 604.

[0099] UE 610 may have at least two antenna panels: a first antenna panel configured to communicate with first network node 602 and a second antenna panel configured to communicate with second network node 604. UE 610 may concurrently send uplink signals to first network node 602 while receiving downlink signals from second network node 604. Due to the simultaneous communication of the first signal and the second signal, UE 610 may experience self-interference. For example, an uplink signal sent by a transmitter of the UE may be leaked to (or received by) a receiver of the UE, and UE 610 may experience self-interference at a receiving antenna receiving a downlink signal from second network node 604, the self-interference being caused by some uplink signals sent to first network node 602.

[0100] refer to Figure 6 , UE 610 may have three antenna panels: a first antenna panel 611 configured to communicate with a first network node 602, and a second antenna panel 612 and a third antenna panel 613 configured to communicate with a second network node 604. For example, UE 610 may be configured to send an uplink transmission (e.g., PUSCH) to the first network node 602 using the first antenna panel 611, and may be configured to receive a downlink transmission (e.g., PDSCH) from the second network node 604 using at least one of the second antenna panel 612 or the third antenna panel 613. In one example, an uplink transmission sent by UE 610 may be sent to the first network node 602 via a Tx beam 620. In another example, a downlink transmission received by UE 610 may be received from the second network node 604 via at least one of a first Rx beam 622 or a second Rx beam 624.

[0101] For the UE 610 operating in the FD mode, uplink transmissions to the first network node 602 may cause self-interference to downlink transmissions from the second network node 604. For example, uplink transmissions to the first network node 602 using the Tx beam 620 may cause self-interference (e.g., first self-interference 632 or second self-interference 634) to downlink transmissions from the second network node 604 using at least one of the first Rx beam 622 or the second Rx beam 624. In one example, the UE 610 may be configured to receive downlink transmissions via the first Rx beam 622 associated with the second antenna panel 612, and uplink transmissions to the first network node 602 may cause self-interference to downlink transmissions received at the second antenna panel 612 using the first Rx beam 622. In another example, the UE 610 may be configured to receive downlink transmissions via a second Rx beam 624 associated with the third antenna panel 613, and uplink transmissions to the first network node 602 may cause self-interference to downlink transmissions received at the third antenna panel 613 using the second Rx beam 624.

[0102] The UE 610 may be configured to obtain or generate a self-interference measurement report associated with the uplink transmission and to send the generated self-interference measurement report to the network. The network may receive the self-interference measurement report from the UE and control the scheduling of the uplink transmission via the first network node 602 and the downlink transmission via the second network node 604 to reduce or minimize the self-interference caused at the UE 610 operating in the FD mode and to improve the network throughput of the downlink signal to the UE 610.

[0103] In some aspects, the network (e.g., the first network node 602) may configure the UE to use scheduling information associated with the uplink transmission to obtain and send a self-interference measurement report caused by the uplink transmission. The network may reduce or save communication overhead by using the scheduling information associated with the uplink transmission to command the self-interference measurement report. That is, instead of transmitting a separate or dedicated configuration / instruction for transmitting the self-interference measurement report, the first network node 602 may include timing information associated with the self-interference measurement report in the scheduling information of the uplink transmission, and the UE 610 may obtain and send the self-interference measurement report based on the scheduling information of the uplink transmission including the timing information associated with the self-interference measurement report.

[0104] For example, the first network node 602 may include at least timing information in scheduling information of an uplink transmission (e.g., one or more PUSCH opportunities) to identify an uplink transmission subject to self-interference measurement (e.g., a specific PUSCH opportunity). The UE may receive scheduling information associated with an uplink transmission (e.g., one or more PUSCH opportunities), identify at least one uplink transmission subject to self-interference measurement (e.g., a specific PUSCH opportunity), measure self-interference caused by the identified at least one uplink transmission using at least one antenna panel associated with an Rx beam, and report the self-interference measurement to the network.

[0105] In one aspect, the network may indicate a specific PUSCH or a specific time slot for self-interference measurement, which may be configured for PUSCH with or without repeated aperiodic scheduling. That is, the scheduling information may be a dynamic grant of aperiodic PUSCH opportunities, and the timing information associated with the self-interference measurement may indicate a specific PUSCH in the aperiodic PUSCH opportunity. The UE may obtain and report a self-interference report caused by a specific PUSCH indicated by the timing information included in the scheduling information.

[0106] On the other hand, the network may configure the UE to report, for example, multiple PUSCH opportunities within a time window for self-interference measurement, which may be PUSCH with or without repeated periodic scheduling. That is, the scheduling information may be a configuration grant of a semi-persistent or periodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate the time window for the self-interference measurement. The UE may obtain and report a self-interference report caused by one or more PUSCH opportunities within the time window indicated by the timing information associated with the self-interference measurement included in the scheduling information.

[0107] On the other hand, the scheduling information may or may not configure Rx quasi co-location (QCL) information associated with self-interference measurement. The Rx QCL information associated with self-interference measurement may indicate an Rx beam to be used for self-interference measurement, and thus the Rx QCL information may indicate at least one antenna panel for measuring self-interference.

[0108] In one option, the scheduling information may configure Rx QCL information associated with the self-interference measurement. Based on the Rx QCL information associated with the self-interference measurement, the UE may obtain a self-interference measurement report and send the self-interference measurement report to the network node. That is, the UE may measure the self-interference caused by the uplink transmission (e.g., a specific PUSCH opportunity) at the antenna panel associated with the Rx beam corresponding to the Rx QCL indicated by the scheduling information.

[0109] In another option, the scheduling information may not configure the Rx QCL information associated with the self-interference measurement. Based on the scheduling information not including the Rx QCL information associated with the self-interference measurement, the UE may determine at least one antenna panel for which self-interference is to be measured, and obtain a self-interference measurement report based on an uplink transmission (e.g., a specific PUSCH opportunity) indicated by the timing information of the scheduling information.

[0110] In one aspect, for each measured UL resource, the UE may add an indication or specify the Rx beam QCL information for the self-interference measurement. That is, the UE may include an indication of the QCL information of the Rx beam used to measure the self-interference measurement. For each self-interference measurement on a PUSCH occasion, the UE may include the QCL information of the Rx beam used to measure the corresponding self-interference measurement in the self-interference measurement report. For example, the indication of the QCL information of the Rx beam may include dynamic grant (DG) downlink (DL) control information (DCI) or radio resource control (RRC) DL beam configuration.

[0111] In some aspects, scheduling information including timing information for self-interference measurements and UE self-interference measurement reports may be based on a UE request. That is, the UE may send a request for self-interference measurements, and the network may configure scheduling information for commanding self-interference measurements based on the request for self-interference measurements received from the UE.

[0112] In one aspect, the UE may request an uplink transmission to perform self-interference measurement. For example, the UE may request that the uplink transmission used to measure the self-interference is one of a periodic uplink transmission resource, an aperiodic uplink transmission resource, or a semi-persistent UL transmission resource (e.g., an activated MAC-CE). Based on the request received from the UE, the network may schedule at least one of the periodic uplink transmission resource, the aperiodic uplink transmission resource, or the semi-persistent UL transmission resource, and include timing information to command the UE to measure the self-interference caused by the scheduled uplink opportunity, and report the self-interference measurement to the network.

[0113] On the other hand, the UE may request self-interference measurements and reports for an uplink beam / panel, a downlink beam / panel, or an uplink and downlink beam / panel pair. That is, the UE may identify or indicate at least one of an uplink beam / panel or a downlink beam / panel, and the network may schedule an uplink transmission opportunity subject to self-interference measurement, or indicate an Rx beam / antenna panel for measuring self-interference caused by a scheduled uplink transmission opportunity. In one example, the UE may indicate at least one recommended Tx beam / antenna panel for sending an uplink transmission (e.g., a PUSCH opportunity) subject to self-interference measurement, or at least one Tx beam / antenna panel that is not recommended for sending an uplink transmission (e.g., a PUSCH opportunity) subject to self-interference measurement. In another example, the UE may indicate at least one recommended Rx beam / antenna panel for measuring self-interference measurements caused by uplink transmissions subject to self-interference measurements (e.g., PUSCH opportunities), or at least one Rx beam / antenna panel that is not recommended for measuring self-interference measurements caused by uplink transmissions subject to self-interference measurements (e.g., PUSCH opportunities).

[0114] In another aspect, at least one Tx or Rx beam / antenna panel or a pair of Tx and Rx beam / antenna panel recommended or not recommended for self-interference measurement reporting may be determined in various ways.

[0115] In one example, the UE may select or identify at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair that is recommended or not recommended for self-interference measurement reporting based on previous measurements of the beam / antenna panels or derived from these previous measurements. That is, based on previous measurements of the Rx and Tx beam / antenna panels, the UE may have a specific understanding of the Rx beam / antenna panels and Tx beam / antenna panels of the corresponding network node, and the UE may indicate to the network node at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair that may be most likely or least likely to be used for uplink transmission and / or downlink transmission. By indicating at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair that is recommended or not recommended for self-interference measurement reporting based on previous measurements of the beam / antenna panels or derived from these previous measurements, the network and the UE may obtain a self-interference measurement report that may be most relevant to the actual data transmission environment.

[0116] In another example, the UE may select or identify at least one Tx or Rx beam / antenna panel or Tx and Rx beam / antenna panel pair that is recommended or not recommended for self-interference measurement reporting based on a machine learning (ML) algorithm or derived from these machine learning (ML) algorithms. That is, the UE may cause the ML algorithm to be trained to estimate at least one Tx or Rx beam / antenna panel or Tx and Rx beam / antenna panel pair that may be most likely or least likely to be used for uplink transmission and / or downlink transmission based on various network conditions (e.g., previous measurements of the beam / antenna panel). Based on the output of the ML algorithm regarding at least one Tx or Rx beam / antenna panel or Tx and Rx beam / antenna panel pair that may be most likely or least likely to be used for uplink transmission and / or downlink transmission, the UE may indicate at least one Tx or Rx beam / antenna panel or Tx and Rx beam / antenna panel pair that is recommended or not recommended for self-interference measurement reporting, and the network and the UE may obtain a self-interference measurement report that may be most relevant to the actual data transmission environment.

[0117] In another aspect, the UE may request that self-interference measurement be configured for dedicated subbands or component carriers. That is, uplink transmission and reception transmission may be configured for certain subbands or certain component carriers, and the UE may request self-interference measurement and further indicate that the request is configured for certain subbands or certain component carriers that may be associated with self-interference.

[0118] In some aspects, based on the UE's self-interference measurement report or ML algorithm results, the UE may be configured to transmit a recommendation for a network configuration for future communications. That is, based on the results of the self-interference measurement, the UE may gain an understanding of the network environment and the self-interference caused by the FD operation. In one example, the UE may send a recommendation for certain information associated with the network configuration based on the results of the self-interference report. In another example, the UE may cause the ML algorithm to be trained to estimate the recommended network configuration based on the results of the self-interference measurement report, and send a recommendation for certain information associated with the network configuration estimated by the ML algorithm.

[0119] In one example, the UE may provide an indication of recommended and / or restricted beams or beam pairs for the UE to operate in FD mode, and the network node may configure the UE to operate in FD mode using these beams or beam pairs based on the recommended and / or restricted beams or beam pairs indicated by the UE. The indication of the recommended and / or restricted beams or beam pairs may be based on a self-interference measurement report obtained by the UE.

[0120] In another example, the UE may further indicate additional information associated with each of the recommended and / or restricted beams or beam pairs. For example, the UE may further indicate the following information associated with each of the recommended and / or restricted beams or beam pairs: a bandwidth part (BWP) identifier (ID) or component carrier ID associated with each of the recommended and / or restricted beams or beam pairs; a timing scheme for self-interference measurement (e.g., a measurement timing aligned with downlink timing or uplink self-interference Rx timing); the number of time slots or symbols before the current time at which the self-interference is measured (e.g., indicating that the self-interference is measured M time slots / symbols ago); or a time window for applying the recommended and / or restricted beams or beam pairs (e.g., indicating that the recommended and / or restricted beams or beam pairs are applicable to the future N time slots in the time window).

[0121] Figure 7 700 is a call flow diagram of a method of wireless communication. The call flow diagram 700 may include a UE 702 and a network node 704. Here, the network node 704 may be a TRP, and the UE 702 may be connected to the network node 704 (e.g., the first network node 602) and another network node (e.g., the second network node 604) using an mTRP configuration. The UE 702 may receive scheduling information including timing information for reporting self-interference measurements from the network node 704, and send a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node 704. In one aspect, the timing information may command the UE 702 to obtain a self-interference measurement report. The UE 702 may send a request for a self-interference measurement report, and the self-interference measurement may be triggered or initiated based on the request sent by the UE 702. The UE 702 may also send a recommendation or restriction on at least one of a Tx beam / antenna panel for UL transmission or an Rx beam / antenna panel for DL ​​transmission based on the self-interference measurement report. The network node 704 may receive the self-interference measurement report from the UE 702 and control scheduling of uplink transmissions via the network node 704 to reduce or minimize self-interference induced at the UE 702 and improve network throughput of downlink signals to the UE 702 .

[0122] At 706, the UE 702 may use an ML algorithm to estimate a recommendation or restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel. That is, the UE 702 may cause the ML algorithm to be trained to estimate at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair that may be most likely or least likely to be used for uplink transmission and / or downlink transmission based on various network conditions (e.g., previous measurements of the beam / antenna panel). Based on the output of the ML algorithm regarding at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair that may be most likely or least likely to be used for uplink transmission and / or downlink transmission, the UE 702 may indicate that at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair is recommended or not recommended for self-interference measurement reporting, and the network node 704 and the UE 702 may obtain a self-interference measurement report that may be most relevant to the actual data transmission environment.

[0123] At 708, UE 702 may send a request for a self-interference measurement report to network node 704 before receiving the scheduling information. Network node 704 may receive the request for the self-interference measurement report before sending the scheduling information. That is, UE 702 may send a request for self-interference measurement, and network node 704 may configure scheduling information that commands the self-interference measurement based on the request for self-interference measurement received from UE 702. For example, UE 702 may request that the uplink transmission for measuring self-interference be one of a periodic uplink transmission resource, an aperiodic uplink transmission resource, or a semi-persistent UL transmission resource (e.g., an activated MAC-CE).

[0124] In one aspect, the request for the self-interference measurement report may request one or more of the following: periodic resources for self-interference measurement, non-periodic resources for self-interference measurement, semi-persistent resources for self-interference measurement, a first measurement of a first beam or a first panel dedicated to the uplink, a second measurement of a second beam or a second panel dedicated to the downlink, or a third measurement of a third beam or a third panel for the uplink and downlink. That is, the UE 702 may identify or indicate at least one of an uplink beam / panel or a downlink beam / panel, and the network node 704 may schedule an uplink transmission opportunity subject to self-interference measurement, or indicate an Rx beam / antenna panel for measuring self-interference caused by the scheduled uplink transmission opportunity. In one example, the UE 702 may indicate at least one recommended Tx beam / antenna panel for sending an uplink transmission (e.g., a PUSCH opportunity) subject to self-interference measurement, or at least one Tx beam / antenna panel that is not recommended for sending an uplink transmission (e.g., a PUSCH opportunity) subject to self-interference measurement. In another example, UE 702 may indicate at least one recommended Rx beam / antenna panel for measuring self-interference measurements caused by uplink transmissions (e.g., PUSCH opportunities) subject to self-interference measurements, or at least one Rx beam / antenna panel that is not recommended for measuring self-interference measurements caused by uplink transmissions (e.g., PUSCH opportunities) subject to self-interference measurements.

[0125] In another aspect, the request for the self-interference measurement report may indicate at least one subband or component carrier. That is, the uplink transmission and reception transmission may be configured for certain subbands or certain component carriers, and the UE 702 may request the self-interference measurement and further indicate that the request is configured for certain subbands or certain component carriers that may be related to self-interference.

[0126] In another aspect, the request for the self-interference measurement report may include a recommendation or restriction on at least one of a Tx beam / antenna panel for sending at least one uplink transmission or an Rx beam / antenna panel for obtaining self-interference measurements.

[0127] In one example, a recommendation or restriction on at least one of a Tx beam / antenna panel or an Rx beam / antenna panel may be based on previous measurements of multiple Tx beams / antenna panels including a Tx beam / antenna panel or multiple Rx beams / antenna panels including an Rx beam / antenna panel. That is, based on previous measurements of Rx and Tx beam / antenna panels, the UE 702 may have a specific understanding of the Rx beam / antenna panels and Tx beam / antenna panels of the corresponding network node, and the UE 702 may indicate to the network node 704 at least one Tx or Rx beam / antenna panel or a pair of Tx and Rx beam / antenna panels that may be most or least likely to be used for uplink transmission and / or downlink transmission. By indicating at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair that is recommended or not recommended for self-interference measurement reporting based on previous measurements of the beam / antenna panel or derived from these previous measurements, the network node 704 and the UE 702 can obtain a self-interference measurement report that is likely to be most relevant to the actual data transmission environment.

[0128] In another example, an ML algorithm can be used at 706 to estimate recommendations or restrictions on at least one of a Tx beam / antenna panel for transmitting at least one uplink transmission or an Rx beam / antenna panel for obtaining self-interference measurements.

[0129] At 710, the network node 704 may send scheduling information for the UE 702, the scheduling information including timing information for reporting self-interference measurements. The UE 702 may receive the scheduling information including the timing information for reporting self-interference measurements. Here, the scheduling information may be received based on the request for self-interference measurement reporting sent to the network node 704 at 708. For example, the network node 704 may include at least timing information in the scheduling information for uplink transmissions (e.g., one or more PUSCH opportunities) to identify uplink transmissions (e.g., specific PUSCH opportunities) subject to self-interference measurements. Based on the request received from the UE 702 at 708, the network node 704 may schedule at least one of periodic uplink transmission resources, aperiodic uplink transmission resources, or semi-persistent UL transmission resources, and include timing information to command the UE 702 to measure self-interference caused by the scheduled uplink opportunities, and report the self-interference measurements to the network node 704.

[0130] In one aspect, the scheduling information may instruct the UE 702 to provide self-interference measurements for one or more of the following: a PUSCH opportunity, a dynamic grant of a scheduled aperiodic PUSCH, a PUSCH opportunity with repetition, a PUSCH opportunity without repetition, a time slot or multiple PUSCH opportunities within a time window. The network node 704 may indicate a specific PUSCH or a specific time slot for self-interference measurements, which may be configured for a PUSCH with or without aperiodic scheduling. That is, the scheduling information may be a dynamic grant of an aperiodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate a specific PUSCH in the aperiodic PUSCH opportunity. The UE 702 may obtain and report a self-interference report caused by a specific PUSCH indicated by the timing information included in the scheduling information.

[0131] On the other hand, the scheduling information may instruct the UE 702 to provide self-interference measurements for multiple PUSCH opportunities based on a configuration grant for scheduling periodic PUSCH, and the indication identifies a time window for measuring self-interference. The network node 704 may configure the UE 702 to report, for example, multiple PUSCH opportunities within a time window for self-interference measurement, which may be PUSCH with or without repeated periodic scheduling. That is, the scheduling information may be a configuration grant for a semi-persistent or periodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate the time window for the self-interference measurement. The UE 702 may obtain and report a self-interference report caused by one or more PUSCH opportunities within a time window indicated by the timing information associated with the self-interference measurement included in the scheduling information.

[0132] On the other hand, the scheduling information may include RX QCL information for self-interference measurement, and the RX beam may be associated with the Rx QCL information. Here, the Rx QCL information may be associated with at least one of the DG DCI or the RRC DL beam configuration. The scheduling information may or may not configure the Rx QCL information associated with the self-interference measurement. The Rx QCL information associated with the self-interference measurement may indicate the Rx beam to be used for the self-interference measurement, and thus the Rx QCL information may indicate at least one antenna panel for measuring the self-interference.

[0133] In one option, the scheduling information may configure Rx QCL information associated with self-interference measurement. Based on the Rx QCL information associated with the self-interference measurement, the UE 702 may obtain a self-interference measurement report and send the self-interference measurement report to the network node 704. That is, the UE 702 may measure the self-interference caused by uplink transmission (e.g., a specific PUSCH opportunity) at an antenna panel associated with an Rx beam corresponding to the Rx QCL indicated by the scheduling information.

[0134] In another option, the scheduling information may not configure the Rx QCL information associated with the self-interference measurement. Based on the scheduling information not including the Rx QCL information associated with the self-interference measurement, the UE 702 may determine at least one antenna panel for measuring self-interference, and obtain a self-interference measurement report based on an uplink transmission (e.g., a specific PUSCH opportunity) indicated by the timing information of the scheduling information.

[0135] At 712, UE 702 may send at least one uplink transmission. Network node 704 may receive at least one uplink transmission. UE 702 may have at least two antenna panels: a first antenna panel configured to communicate with network node 704 and a second antenna panel configured to communicate with another network node. UE 702 may concurrently send uplink signals to network node 704 while receiving downlink signals from another network node. Due to the simultaneous communication of the first signal and the second signal, UE 702 may experience self-interference. For example, an uplink signal sent by a transmitter of the UE may be leaked to (or received by) a receiver of the UE, and UE 702 may experience self-interference at a receive antenna receiving a downlink signal from another network node, the self-interference being caused by some uplink signals sent to the first base station.

[0136] At 714, the UE 702 may measure the self-interference of the uplink transmission using at least one Rx beam at the UE 702 and during the time indicated by the scheduling information. Here, the UE 702 may be configured to measure the self-interference caused by at least one uplink transmission sent at 712 based on the time information indicated by the scheduling information received at 710.

[0137] In one aspect, the scheduling information may be a dynamic grant of aperiodic PUSCH opportunities, and the UE 702 may measure the self-interference caused by a specific PUSCH in the aperiodic PUSCH opportunities indicated by the time information of the scheduling information received at 710. In another aspect, the scheduling information may be a configuration grant of semi-persistent or periodic PUSCH opportunities, and the UE 702 may measure the self-interference caused by one or more PUSCH opportunities within a time window indicated by the timing information included in the scheduling information.

[0138] In some aspects, the scheduling information may or may not configure Rx QCL information associated with self-interference measurement. In one aspect, the scheduling information received at 710 may include Rx QCL information associated with self-interference measurement, and the UE 702 may obtain self-interference measurement at an antenna panel associated with an Rx beam corresponding to the Rx QCL information received at 710. That is, the UE 702 may measure self-interference caused by uplink transmission (e.g., a specific PUSCH opportunity) at an antenna panel associated with an Rx beam corresponding to the Rx QCL indicated by the scheduling information.

[0139] On the other hand, the scheduling information received at 710 may not include Rx QCL information associated with self-interference measurement. Based on the scheduling information not including Rx QCL information associated with self-interference measurement, UE 702 may determine at least one antenna panel for which self-interference is to be measured, and obtain a self-interference measurement report based on an uplink transmission (e.g., a specific PUSCH opportunity) indicated by the timing information of the scheduling information.

[0140] At 716, UE 702 may send a self-interference measurement report including the self-interference measurement based on the scheduling information received at 710 from network node 704. Network node 704 may receive a self-interference measurement report including the self-interference measurement based on the scheduling information received at 710 from network node 704.

[0141] In the case where the scheduling information received at 710 may not configure the Rx QCL information associated with the self-interference measurement, for each measured UL resource, the UE 702 may add an indication or specify the Rx beam QCL information for the self-interference measurement. That is, the UE 702 may include an indication of the QCL information of the Rx beam used to measure the self-interference measurement. For each self-interference measurement of the PUSCH opportunity, the UE 702 may include the QCL information of the Rx beam used to measure the corresponding self-interference measurement in the self-interference measurement report. For example, the indication of the QCL information of the Rx beam may include the DG DCI or the DL beam configuration.

[0142] At 718, the UE 702 may estimate a recommendation or restriction on at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on the self-interference measurement report using an ML algorithm. That is, the UE 702 may train the ML algorithm to estimate a recommended network configuration based on the result of the self-interference measurement report, and send a recommendation for certain information associated with the network configuration estimated by the ML algorithm at 720.

[0143] At 720, the UE 702 may send a recommendation or restriction for at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on the self-interference measurement report. The network node 704 may receive a recommendation or restriction for at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on the self-interference measurement report.

[0144] The recommendation or restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel may also include at least one information associated with at least one of the Tx beam / antenna panel or the Rx beam / antenna panel, the at least one information including at least one of the following: BWP ID, CC ID, the measurement timing scheme used, at least one self-interference previously measured before one or more symbols, or a time window for applying the recommendation or the restriction after one or more symbols. That is, based on the results of the self-interference measurement, the UE 702 can obtain an understanding of the network environment and the self-interference caused by the FD operation. In one example, the UE 702 can send a recommendation for certain information associated with the network configuration based on the results of the self-interference report. In another example, the UE 702 can cause the ML algorithm to be trained to estimate the recommended network configuration based on the results of the self-interference measurement report, and send a recommendation for certain information associated with the network configuration estimated by the ML algorithm at 718.

[0145] In one example, the UE 702 may provide an indication of recommended and / or restricted beams or beam pairs for the UE 702 to operate in the FD mode, and the network node 704 may configure the UE 702 to operate in the FD mode using the recommended and / or restricted beams or beam pairs indicated by the UE 702. The indication of the recommended and / or restricted beams or beam pairs may be based on a self-interference measurement report obtained by the UE 702.

[0146] In another example, the UE 702 may further indicate additional information associated with each of the recommended and / or restricted beams or beam pairs. For example, the UE 702 may further indicate the following information associated with each of the recommended and / or restricted beams or beam pairs: a bandwidth part (BWP) identifier (ID) or component carrier ID associated with each of the recommended and / or restricted beams or beam pairs; a timing scheme for self-interference measurement (e.g., a measurement timing aligned with downlink timing or uplink self-interference Rx timing); the number of time slots or symbols before the current time at which the self-interference is measured (e.g., indicating that the self-interference is measured M time slots / symbols ago); or a time window for applying the recommended and / or restricted beams or beam pairs (e.g., indicating that the recommended and / or restricted beams or beam pairs are applicable to the future N time slots in the time window).

[0147] Figure 8 800 is a flowchart of a method for wireless communication. The method may be performed by a UE (e.g., UE 104 / 610 / 702; device 1204). The UE may be connected to a network node (e.g., a first network node 602) and another network node (e.g., a second network node 604) using an mTRP configuration. The UE may receive scheduling information including timing information for reporting self-interference measurements from the network node, and send a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. In one aspect, the timing information may command the UE to obtain a self-interference measurement report. The UE may send a request for a self-interference measurement report, and may trigger or initiate a self-interference measurement based on the request sent by the UE. The UE may also send a recommendation or restriction on at least one of a Tx beam / antenna panel for UL transmission or an Rx beam / antenna panel for DL ​​transmission based on the self-interference measurement report.

[0148] At 806, the UE may use an ML algorithm to estimate a recommendation or restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel. That is, the UE may cause the ML algorithm to be trained to estimate at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair that may be most likely or least likely to be used for uplink transmission and / or downlink transmission based on various network conditions (e.g., previous measurements of the beam / antenna panel). Based on the output of the ML algorithm regarding at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair that may be most likely or least likely to be used for uplink transmission and / or downlink transmission, the UE may indicate at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair that is recommended or not recommended for self-interference measurement reporting, and the network node and the UE may obtain a self-interference measurement report that may be most relevant to the actual data transmission environment. For example, at 706 , UE 702 can use an ML algorithm to estimate a recommendation or restriction for at least one of a Tx beam / antenna panel or an Rx beam / antenna panel. Additionally, 806 can be performed by self-interference measurement reporting component 198 .

[0149] At 808, the UE may send a request for a self-interference measurement report to the network node before receiving the scheduling information. That is, the UE may send a request for self-interference measurement, and the network node may configure scheduling information for commanding self-interference measurement based on the request for self-interference measurement received from the UE. For example, the UE may request that the uplink transmission used to measure self-interference be one of a periodic uplink transmission resource, an aperiodic uplink transmission resource, or a semi-persistent UL transmission resource (e.g., an activated MAC-CE). For example, at 708, the UE 702 may send a request for a self-interference measurement report to the network node 704 before receiving the scheduling information. In addition, 808 may be performed by the self-interference measurement reporting component 198.

[0150] In one aspect, the request for a self-interference measurement report may request one or more of the following: periodic resources for self-interference measurement, non-periodic resources for self-interference measurement, semi-persistent resources for self-interference measurement, a first measurement of a first beam or a first panel dedicated to the uplink, a second measurement of a second beam or a second panel dedicated to the downlink, or a third measurement of a third beam or a third panel for the uplink and downlink. That is, the UE may identify or indicate at least one of an uplink beam / panel or a downlink beam / panel, and the network node may schedule an uplink transmission opportunity subject to self-interference measurement, or indicate an Rx beam / antenna panel for measuring self-interference caused by the scheduled uplink transmission opportunity. In one example, the UE may indicate at least one recommended Tx beam / antenna panel for sending an uplink transmission (e.g., a PUSCH opportunity) subject to self-interference measurement, or at least one Tx beam / antenna panel that is not recommended for sending an uplink transmission (e.g., a PUSCH opportunity) subject to self-interference measurement. In another example, the UE may indicate at least one recommended Rx beam / antenna panel for measuring self-interference measurements caused by uplink transmissions subject to self-interference measurements (e.g., PUSCH opportunities), or at least one Rx beam / antenna panel that is not recommended for measuring self-interference measurements caused by uplink transmissions subject to self-interference measurements (e.g., PUSCH opportunities).

[0151] In another aspect, the request for the self-interference measurement report may indicate at least one subband or component carrier. That is, the uplink transmission and reception transmission may be configured for certain subbands or certain component carriers, and the UE may request self-interference measurement and further indicate that the request is configured for certain subbands or certain component carriers that may be related to self-interference.

[0152] In another aspect, the request for the self-interference measurement report may include a recommendation or restriction on at least one of a Tx beam / antenna panel for sending at least one uplink transmission or an Rx beam / antenna panel for obtaining self-interference measurements.

[0153] In one example, a recommendation or restriction on at least one of a Tx beam / antenna panel or an Rx beam / antenna panel may be based on previous measurements of multiple Tx beams / antenna panels including a Tx beam / antenna panel or multiple Rx beam / antenna panels including an Rx beam / antenna panel. That is, based on previous measurements of Rx and Tx beam / antenna panels, the UE may have a specific understanding of the Rx beam / antenna panel and the Tx beam / antenna panel of the corresponding network node, and the UE may indicate to the network node at least one Tx or Rx beam / antenna panel or a pair of Tx and Rx beam / antenna panels that may be most likely or least likely to be used for uplink transmission and / or downlink transmission. By indicating at least one Tx or Rx beam / antenna panel or a pair of Tx and Rx beam / antenna panels that are recommended or not recommended for self-interference measurement reporting based on previous measurements of beam / antenna panels or derived from these previous measurements, the network node and the UE may obtain a self-interference measurement report that may be most relevant to the actual data transmission environment.

[0154] In another example, an ML algorithm can be used at 806 to estimate recommendations or restrictions on at least one of a Tx beam / antenna panel for transmitting at least one uplink transmission or an Rx beam / antenna panel for obtaining self-interference measurements.

[0155] At 810, the UE may receive scheduling information including timing information for reporting self-interference measurements. Here, the scheduling information may be received based on the request for self-interference measurement report sent to the network node at 808. For example, the network node may include at least timing information in the scheduling information of the uplink transmission (e.g., one or more PUSCH opportunities) to identify the uplink transmission (e.g., a specific PUSCH opportunity) subject to self-interference measurement. Based on the request received from the UE at 808, the network node may schedule at least one of periodic uplink transmission resources, aperiodic uplink transmission resources, or semi-persistent UL transmission resources, and include timing information to command the UE to measure the self-interference caused by the scheduled uplink opportunity, and report the self-interference measurement to the network node. For example, at 710, the UE 702 may receive scheduling information including timing information for reporting self-interference measurements. In addition, 810 may be performed by the self-interference measurement reporting component 198.

[0156] In one aspect, the scheduling information may instruct the UE to provide self-interference measurements for one or more of the following: a PUSCH opportunity, a dynamic grant of a scheduled aperiodic PUSCH, a PUSCH opportunity with repetition, a PUSCH opportunity without repetition, a time slot or multiple PUSCH opportunities within a time window. The network node may indicate a specific PUSCH or a specific time slot for self-interference measurement, which may be configured for a PUSCH with or without aperiodic scheduling. That is, the scheduling information may be a dynamic grant of a non-periodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate a specific PUSCH in the non-periodic PUSCH opportunity. The UE may obtain and report a self-interference report caused by a specific PUSCH indicated by the timing information included in the scheduling information.

[0157] On the other hand, the scheduling information may instruct the UE to provide self-interference measurements for multiple PUSCH opportunities based on a configuration grant for scheduling periodic PUSCH, and the indication identifies a time window for measuring self-interference. The network node may configure the UE to report, for example, multiple PUSCH opportunities within a time window for self-interference measurements, which may be PUSCH with or without repeated periodic scheduling. That is, the scheduling information may be a configuration grant for a semi-persistent or periodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate the time window for the self-interference measurement. The UE may obtain and report a self-interference report caused by one or more PUSCH opportunities within a time window indicated by the timing information associated with the self-interference measurement included in the scheduling information.

[0158] On the other hand, the scheduling information may include RX QCL information for self-interference measurement, and the RX beam may be associated with the Rx QCL information. Here, the Rx QCL information may be associated with at least one of the DG DCI or the RRC DL beam configuration. The scheduling information may or may not configure the Rx QCL information associated with the self-interference measurement. The Rx QCL information associated with the self-interference measurement may indicate the Rx beam to be used for the self-interference measurement, and thus the Rx QCL information may indicate at least one antenna panel for measuring the self-interference.

[0159] In one option, the scheduling information may configure Rx QCL information associated with the self-interference measurement. Based on the Rx QCL information associated with the self-interference measurement, the UE may obtain a self-interference measurement report and send the self-interference measurement report to the network node. That is, the UE may measure the self-interference caused by the uplink transmission (e.g., a specific PUSCH opportunity) at the antenna panel associated with the Rx beam corresponding to the Rx QCL indicated by the scheduling information.

[0160] In another option, the scheduling information may not configure the Rx QCL information associated with the self-interference measurement. Based on the scheduling information not including the Rx QCL information associated with the self-interference measurement, the UE may determine at least one antenna panel for which self-interference is to be measured, and obtain a self-interference measurement report based on an uplink transmission (e.g., a specific PUSCH opportunity) indicated by the timing information of the scheduling information.

[0161] At 812, the UE may send at least one uplink transmission at the UE. The UE may have at least two antenna panels: a first antenna panel configured to communicate with a network node and a second antenna panel configured to communicate with another network node. The first UE may concurrently send an uplink signal to the network node while receiving a downlink signal from another network node. Due to the simultaneous communication of the first signal and the second signal, the UE may experience self-interference. For example, an uplink signal sent by a transmitter of the UE may be leaked to (or received by) a receiver of the UE, and the UE may experience self-interference at a receiving antenna that receives a downlink signal from another network node, the self-interference being caused by some uplink signals sent to the first base station. For example, at 712, the UE 702 may send at least one uplink transmission. In addition, 812 may be performed by a self-interference measurement reporting component 198.

[0162] At 814, the UE may measure the self-interference of the uplink transmission using at least one Rx beam at the UE and during the time indicated by the scheduling information. Here, the UE may be configured to measure the self-interference caused by at least one uplink transmission sent at 812 based on the time information indicated by the scheduling information received at 810. For example, at 714, the UE 702 may measure the self-interference of the uplink transmission using at least one Rx beam at the UE 702 and during the time indicated by the scheduling information. In addition, 814 may be performed by the self-interference measurement reporting component 198.

[0163] In one aspect, the scheduling information may be a dynamic grant of aperiodic PUSCH opportunities, and the UE may measure the self-interference caused by a specific PUSCH in the aperiodic PUSCH opportunities indicated by the time information of the scheduling information received at 810. In another aspect, the scheduling information may be a configuration grant of semi-persistent or periodic PUSCH opportunities, and the UE may measure the self-interference caused by one or more PUSCH opportunities within a time window indicated by the timing information included in the scheduling information.

[0164] In some aspects, the scheduling information may or may not configure Rx QCL information associated with self-interference measurement. In one aspect, the scheduling information received at 810 may include Rx QCL information associated with self-interference measurement, and the UE may obtain self-interference measurement at an antenna panel associated with an Rx beam corresponding to the Rx QCL information received at 810. That is, the UE may measure self-interference caused by uplink transmission (e.g., a specific PUSCH opportunity) at an antenna panel associated with an Rx beam corresponding to the Rx QCL indicated by the scheduling information.

[0165] On the other hand, the scheduling information received at 810 may not include Rx QCL information associated with self-interference measurement. Based on the scheduling information not including Rx QCL information associated with self-interference measurement, the UE may determine at least one antenna panel for which self-interference is to be measured, and obtain a self-interference measurement report based on an uplink transmission (e.g., a specific PUSCH opportunity) indicated by the timing information of the scheduling information.

[0166] At 816, the UE may send a self-interference measurement report including a self-interference measurement based on the scheduling information received from the network node at 810. The network node may receive a self-interference measurement report including a self-interference measurement based on the scheduling information received from the network node at 810. In the case where the scheduling information received at 810 may not configure the Rx QCL information associated with the self-interference measurement, for each measured UL resource, the UE may add an indication or specify the Rx beam QCL information used for the self-interference measurement. That is, the UE may include an indication of the QCL information of the Rx beam used to measure the self-interference measurement. For each self-interference measurement of the PUSCH opportunity, the UE may include the QCL information of the Rx beam used to measure the corresponding self-interference measurement in the self-interference measurement report. For example, the indication of the QCL information of the Rx beam may include the DG DCI or the DL beam configuration. For example, at 716, the UE 702 may send a self-interference measurement report including a self-interference measurement based on the scheduling information received from the network node 704 at 710. Moreover, 816 can be performed by self-interference measurement reporting component 198 .

[0167] At 818, the UE may use an ML algorithm to estimate a recommendation or restriction for at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on the self-interference measurement report. That is, the UE may cause the ML algorithm to be trained to estimate a recommended network configuration based on the result of the self-interference measurement report, and send a recommendation for certain information associated with the network configuration estimated by the ML algorithm at 820. For example, at 718, the UE may use an ML algorithm to estimate a recommendation or restriction for at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on the self-interference measurement report. In addition, 818 may be performed by the self-interference measurement reporting component 198.

[0168] At 820, the UE may send a recommendation or restriction for at least one of the Tx beam / antenna panel for uplink transmission or the Rx beam / antenna panel for downlink transmission based on the self-interference measurement report. The network node may receive a recommendation or restriction for at least one of the Tx beam / antenna panel for uplink transmission or the Rx beam / antenna panel for downlink transmission based on the self-interference measurement report. For example, at 720, the UE 702 may send a recommendation or restriction for at least one of the Tx beam / antenna panel for uplink transmission or the Rx beam / antenna panel for downlink transmission based on the self-interference measurement report. In addition, 820 may be performed by the self-interference measurement reporting component 198.

[0169] The recommendation or restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel may also include at least one information associated with at least one of the Tx beam / antenna panel or the Rx beam / antenna panel, the at least one information including at least one of the following: BWP ID, CC ID, the measurement timing scheme used, at least one self-interference previously measured before one or more symbols, or a time window for applying the recommendation or the restriction after one or more symbols. That is, based on the results of the self-interference measurement, the UE can obtain an understanding of the network environment and the self-interference caused by the FD operation. In one example, the UE may send a recommendation for certain information associated with the network configuration based on the results of the self-interference report. In another example, the UE may cause the ML algorithm to be trained to estimate the recommended network configuration based on the results of the self-interference measurement report, and send a recommendation for certain information associated with the network configuration estimated by the ML algorithm at 818.

[0170] In one example, the UE may provide an indication of recommended and / or restricted beams or beam pairs for the UE to operate in FD mode, and the network node may configure the UE to operate in FD mode using these beams or beam pairs based on the recommended and / or restricted beams or beam pairs indicated by the UE. The indication of the recommended and / or restricted beams or beam pairs may be based on a self-interference measurement report obtained by the UE.

[0171] In another example, the UE may further indicate additional information associated with each of the recommended and / or restricted beams or beam pairs. For example, the UE may further indicate the following information associated with each of the recommended and / or restricted beams or beam pairs: a bandwidth part (BWP) identifier (ID) or component carrier ID associated with each of the recommended and / or restricted beams or beam pairs; a timing scheme for self-interference measurement (e.g., a measurement timing aligned with downlink timing or uplink self-interference Rx timing); the number of time slots or symbols before the current time at which the self-interference is measured (e.g., indicating that the self-interference is measured M time slots / symbols ago); or a time window for applying the recommended and / or restricted beams or beam pairs (e.g., indicating that the recommended and / or restricted beams or beam pairs are applicable to the future N time slots in the time window).

[0172] Fig. 9 900 is a flowchart of a method for wireless communication. The method may be performed by a UE (e.g., UE 104 / 610 / 702; device 1204). The UE may be connected to a network node (e.g., a first network node 602) and another network node (e.g., a second network node 604) using an mTRP configuration. The UE may receive scheduling information including timing information for reporting self-interference measurements from the network node, and send a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. In one aspect, the timing information may command the UE to obtain a self-interference measurement report. The UE may send a request for a self-interference measurement report, and may trigger or initiate a self-interference measurement based on the request sent by the UE. The UE may also send a recommendation or restriction on at least one of a Tx beam / antenna panel for UL transmission or an Rx beam / antenna panel for DL ​​transmission based on the self-interference measurement report.

[0173] At 910, the UE may receive scheduling information including timing information for reporting self-interference measurements. Here, the scheduling information may be received based on the request for self-interference measurement report sent to the network node at 908. For example, the network node may include at least timing information in the scheduling information of the uplink transmission (e.g., one or more PUSCH opportunities) to identify the uplink transmission (e.g., a specific PUSCH opportunity) subject to self-interference measurement. Based on the request received from the UE at 908, the network node may schedule at least one of periodic uplink transmission resources, aperiodic uplink transmission resources, or semi-persistent UL transmission resources, and include timing information to command the UE to measure the self-interference caused by the scheduled uplink opportunity, and report the self-interference measurement to the network node. For example, at 710, the UE 702 may receive scheduling information including timing information for reporting self-interference measurements. In addition, 910 may be performed by the self-interference measurement reporting component 198.

[0174] In one aspect, the scheduling information may instruct the UE to provide self-interference measurements for one or more of the following: a PUSCH opportunity, a dynamic grant of a scheduled aperiodic PUSCH, a PUSCH opportunity with repetition, a PUSCH opportunity without repetition, a time slot or multiple PUSCH opportunities within a time window. The network node may indicate a specific PUSCH or a specific time slot for self-interference measurement, which may be configured for a PUSCH with or without aperiodic scheduling. That is, the scheduling information may be a dynamic grant of a non-periodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate a specific PUSCH in the non-periodic PUSCH opportunity. The UE may obtain and report a self-interference report caused by a specific PUSCH indicated by the timing information included in the scheduling information.

[0175] On the other hand, the scheduling information may instruct the UE to provide self-interference measurements for multiple PUSCH opportunities based on a configuration grant for scheduling periodic PUSCH, and the indication identifies a time window for measuring self-interference. The network node may configure the UE to report, for example, multiple PUSCH opportunities within a time window for self-interference measurements, which may be PUSCH with or without repeated periodic scheduling. That is, the scheduling information may be a configuration grant for a semi-persistent or periodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate the time window for the self-interference measurement. The UE may obtain and report a self-interference report caused by one or more PUSCH opportunities within a time window indicated by the timing information associated with the self-interference measurement included in the scheduling information.

[0176] On the other hand, the scheduling information may include RX QCL information for self-interference measurement, and the RX beam may be associated with the Rx QCL information. Here, the Rx QCL information may be associated with at least one of the DG DCI or the RRC DL beam configuration. The scheduling information may or may not configure the Rx QCL information associated with the self-interference measurement. The Rx QCL information associated with the self-interference measurement may indicate the Rx beam to be used for the self-interference measurement, and thus the Rx QCL information may indicate at least one antenna panel for measuring the self-interference.

[0177] In one option, the scheduling information may configure Rx QCL information associated with the self-interference measurement. Based on the Rx QCL information associated with the self-interference measurement, the UE may obtain a self-interference measurement report and send the self-interference measurement report to the network node. That is, the UE may measure the self-interference caused by the uplink transmission (e.g., a specific PUSCH opportunity) at the antenna panel associated with the Rx beam corresponding to the Rx QCL indicated by the scheduling information.

[0178] In another option, the scheduling information may not configure the Rx QCL information associated with the self-interference measurement. Based on the scheduling information not including the Rx QCL information associated with the self-interference measurement, the UE may determine at least one antenna panel for which self-interference is to be measured, and obtain a self-interference measurement report based on an uplink transmission (e.g., a specific PUSCH opportunity) indicated by the timing information of the scheduling information.

[0179] At 916, the UE may send a self-interference measurement report including a self-interference measurement based on the scheduling information received from the network node at 910. The network node may receive a self-interference measurement report including a self-interference measurement based on the scheduling information received from the network node at 910. In the case where the scheduling information received at 910 may not configure the Rx QCL information associated with the self-interference measurement, for each measured UL resource, the UE may add an indication or specify the Rx beam QCL information used for the self-interference measurement. That is, the UE may include an indication of the QCL information of the Rx beam used to measure the self-interference measurement. For each self-interference measurement of the PUSCH opportunity, the UE may include the QCL information of the Rx beam used to measure the corresponding self-interference measurement in the self-interference measurement report. For example, the indication of the QCL information of the Rx beam may include the DG DCI or the DL beam configuration. For example, at 716, the UE 702 may send a self-interference measurement report including a self-interference measurement based on the scheduling information received from the network node 704 at 710. Moreover, 916 can be performed by the self-interference measurement reporting component 198 .

[0180] Fig.101000 is a flowchart of a method for wireless communication. The method may be performed by a network node (e.g., a base station 102 / 602 / 704; a network entity 1302 / 1460). Here, the network node may be a TRP, and the UE may be connected to the network node (e.g., a first network node 602) and another network node (e.g., a second network node 604) using an mTRP configuration. The network node may send scheduling information including timing information for reporting self-interference measurements to the UE, and receive a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. The network node may receive a request for a self-interference measurement report from the UE, and may trigger or initiate a self-interference measurement based on the request received from the UE. The network node may also send a recommendation or restriction on at least one of a Tx beam / antenna panel for UL transmission or an Rx beam / antenna panel for DL ​​transmission based on the self-interference measurement report. The network node may receive the self-interference measurement report from the UE and control scheduling of uplink transmissions via the network node to reduce or minimize self-interference induced at the UE and improve network throughput of downlink signals to the UE.

[0181] At 1008, the network node may receive a request for a self-interference measurement report before sending the scheduling information. That is, the UE may send a request for self-interference measurement, and the network node may configure scheduling information for commanding self-interference measurement based on the request for self-interference measurement received from the UE. For example, the UE may request that the uplink transmission for measuring self-interference be one of a periodic uplink transmission resource, an aperiodic uplink transmission resource, or a semi-persistent UL transmission resource (e.g., an activated MAC-CE). For example, at 708, the network node 704 may receive a request for a self-interference measurement report before sending the scheduling information. In addition, 1008 may be performed by a self-interference measurement report configuration component 199.

[0182] In one aspect, the request for a self-interference measurement report may request one or more of the following: periodic resources for self-interference measurement, non-periodic resources for self-interference measurement, semi-persistent resources for self-interference measurement, a first measurement of a first beam or a first panel dedicated to the uplink, a second measurement of a second beam or a second panel dedicated to the downlink, or a third measurement of a third beam or a third panel for the uplink and downlink. That is, the UE may identify or indicate at least one of an uplink beam / panel or a downlink beam / panel, and the network node may schedule an uplink transmission opportunity subject to self-interference measurement, or indicate an Rx beam / antenna panel for measuring self-interference caused by the scheduled uplink transmission opportunity. In one example, the UE may indicate at least one recommended Tx beam / antenna panel for sending an uplink transmission (e.g., a PUSCH opportunity) subject to self-interference measurement, or at least one Tx beam / antenna panel that is not recommended for sending an uplink transmission (e.g., a PUSCH opportunity) subject to self-interference measurement. In another example, the UE may indicate at least one recommended Rx beam / antenna panel for measuring self-interference measurements caused by uplink transmissions subject to self-interference measurements (e.g., PUSCH opportunities), or at least one Rx beam / antenna panel that is not recommended for measuring self-interference measurements caused by uplink transmissions subject to self-interference measurements (e.g., PUSCH opportunities).

[0183] In another aspect, the request for the self-interference measurement report may indicate at least one subband or component carrier. That is, the uplink transmission and reception transmission may be configured for certain subbands or certain component carriers, and the UE may request self-interference measurement and further indicate that the request is configured for certain subbands or certain component carriers that may be related to self-interference.

[0184] On the other hand, the request for the self-interference measurement report may include a recommendation or restriction on at least one of a Tx beam / antenna panel for sending at least one uplink transmission or an Rx beam / antenna panel for obtaining self-interference measurements. Based on the request for the self-interference measurement report received from the UE, the network node may configure the UE to obtain a self-interference measurement report that may be most relevant to the actual data transmission environment.

[0185] In one example, a recommendation or restriction on at least one of a Tx beam / antenna panel or an Rx beam / antenna panel may be based on previous measurements of multiple Tx beams / antenna panels including a Tx beam / antenna panel or multiple Rx beam / antenna panels including an Rx beam / antenna panel. That is, based on previous measurements of Rx and Tx beam / antenna panels, the UE may have a specific understanding of the Rx beam / antenna panel and the Tx beam / antenna panel of the corresponding network node, and the UE may indicate to the network node at least one Tx or Rx beam / antenna panel or a pair of Tx and Rx beam / antenna panels that may be most likely or least likely to be used for uplink transmission and / or downlink transmission. By indicating at least one Tx or Rx beam / antenna panel or a pair of Tx and Rx beam / antenna panels that are recommended or not recommended for self-interference measurement reporting based on previous measurements of beam / antenna panels or derived from these previous measurements, the network node and the UE may obtain a self-interference measurement report that may be most relevant to the actual data transmission environment.

[0186] In another example, an ML algorithm may be used to estimate a recommendation or restriction for at least one of a Tx beam / antenna panel for transmitting at least one uplink transmission or an Rx beam / antenna panel for obtaining self-interference measurements. The ML algorithm may be trained to estimate at least one Tx or Rx beam / antenna panel or a Tx and Rx beam / antenna panel pair that may be most or least likely to be used for uplink transmissions and / or downlink transmissions based on various network conditions at the UE (e.g., previous measurements of the beam / antenna panel).

[0187] At 1010, the network node may send scheduling information for the UE, the scheduling information including timing information for reporting self-interference measurements. Here, the scheduling information may be received based on the request for self-interference measurement report sent to the network node at 1008. For example, the network node may include at least timing information in the scheduling information for uplink transmissions (e.g., one or more PUSCH opportunities) to identify uplink transmissions (e.g., specific PUSCH opportunities) subject to self-interference measurements. Based on the request received from the UE at 1008, the network node may schedule at least one of periodic uplink transmission resources, aperiodic uplink transmission resources, or semi-persistent UL transmission resources, and include timing information to command the UE to measure the self-interference caused by the scheduled uplink opportunities, and report the self-interference measurements to the network node. For example, at 710, the network node 704 may send scheduling information for the UE 702, the scheduling information including timing information for reporting self-interference measurements. In addition, 1010 may be performed by the self-interference measurement report configuration component 199.

[0188] In one aspect, the scheduling information may instruct the UE to provide self-interference measurements for one or more of the following: a PUSCH opportunity, a dynamic grant of a scheduled aperiodic PUSCH, a PUSCH opportunity with repetition, a PUSCH opportunity without repetition, a time slot or multiple PUSCH opportunities within a time window. The network node may indicate a specific PUSCH or a specific time slot for self-interference measurement, which may be configured for a PUSCH with or without aperiodic scheduling. That is, the scheduling information may be a dynamic grant of a non-periodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate a specific PUSCH in the non-periodic PUSCH opportunity. The UE may obtain and report a self-interference report caused by a specific PUSCH indicated by the timing information included in the scheduling information.

[0189] On the other hand, the scheduling information may instruct the UE to provide self-interference measurements for multiple PUSCH opportunities based on a configuration grant for scheduling periodic PUSCH, and the indication identifies a time window for measuring self-interference. The network node may configure the UE to report, for example, multiple PUSCH opportunities within a time window for self-interference measurements, which may be PUSCH with or without repeated periodic scheduling. That is, the scheduling information may be a configuration grant for a semi-persistent or periodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate the time window for the self-interference measurement. The UE may obtain and report a self-interference report caused by one or more PUSCH opportunities within a time window indicated by the timing information associated with the self-interference measurement included in the scheduling information.

[0190] On the other hand, the scheduling information may include RX QCL information for self-interference measurement, and the RX beam may be associated with the Rx QCL information. Here, the Rx QCL information may be associated with at least one of the DG DCI or the RRC DL beam configuration. The scheduling information may or may not configure the Rx QCL information associated with the self-interference measurement. The Rx QCL information associated with the self-interference measurement may indicate the Rx beam to be used for the self-interference measurement, and thus the Rx QCL information may indicate at least one antenna panel for measuring the self-interference.

[0191] In one option, the scheduling information may configure Rx QCL information associated with the self-interference measurement. Based on the Rx QCL information associated with the self-interference measurement, the UE may obtain a self-interference measurement report and send the self-interference measurement report to the network node. That is, the UE may measure the self-interference caused by the uplink transmission (e.g., a specific PUSCH opportunity) at the antenna panel associated with the Rx beam corresponding to the Rx QCL indicated by the scheduling information.

[0192] In another option, the scheduling information may not configure the Rx QCL information associated with the self-interference measurement. Based on the scheduling information not including the Rx QCL information associated with the self-interference measurement, the UE may determine at least one antenna panel for which self-interference is to be measured, and obtain a self-interference measurement report based on an uplink transmission (e.g., a specific PUSCH opportunity) indicated by the timing information of the scheduling information.

[0193] At 1012, the network node may receive at least one uplink transmission. The UE may have at least two antenna panels: a first antenna panel configured to communicate with the network node and a second antenna panel configured to communicate with another network node. The first UE may concurrently send an uplink signal to the network node while receiving a downlink signal from another network node. Due to the simultaneous communication of the first signal and the second signal, the UE may experience self-interference. For example, an uplink signal sent by a transmitter of the UE may be leaked to (or received by) a receiver of the UE, and the UE may experience self-interference at a receiving antenna that receives a downlink signal from another network node, the self-interference being caused by some uplink signals sent to the first base station. For example, at 712, the network node 704 may receive at least one uplink transmission. In addition, 1012 may be performed by a self-interference measurement report configuration component 199.

[0194] At 1016, the network node may receive a self-interference measurement report including a self-interference measurement based on the scheduling information received from the network node at 1010. In the case where the scheduling information received at 1010 may not configure the Rx QCL information associated with the self-interference measurement, for each measured UL resource, the UE may add an indication or specify the Rx beam QCL information for the self-interference measurement. That is, the UE may include an indication of the QCL information of the Rx beam used to measure the self-interference measurement. For each self-interference measurement of the PUSCH opportunity, the UE may include the QCL information of the Rx beam used to measure the corresponding self-interference measurement in the self-interference measurement report. For example, the indication of the QCL information of the Rx beam may include a DG DCI or a DL beam configuration. For example, at 716, the network node 704 may receive a self-interference measurement report including a self-interference measurement based on the scheduling information received from the network node 704 at 710. In addition, 1016 may be performed by the self-interference measurement report configuration component 199.

[0195] At 1020, the network node may receive a recommendation or restriction for at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on the self-interference measurement report. For example, at 720, the network node 704 may receive a recommendation or restriction for at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on the self-interference measurement report. In addition, 1020 may be performed by the self-interference measurement report configuration component 199.

[0196] The recommendation or restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel may also include at least one information associated with at least one of the Tx beam / antenna panel or the Rx beam / antenna panel, the at least one information including at least one of the following: BWP ID, CC ID, the measurement timing scheme used, at least one self-interference previously measured before one or more symbols, or a time window for applying the recommendation or the restriction after one or more symbols. That is, based on the results of the self-interference measurement, the UE can obtain an understanding of the network environment and the self-interference caused by the FD operation. In one example, the UE may send a recommendation for certain information associated with the network configuration based on the results of the self-interference report. In another example, the UE may cause the ML algorithm to be trained to estimate the recommended network configuration based on the results of the self-interference measurement report, and send a recommendation for certain information associated with the network configuration estimated by the ML algorithm at 818.

[0197] In one example, the UE may provide an indication of recommended and / or restricted beams or beam pairs for the UE to operate in FD mode, and the network node may configure the UE to operate in FD mode using these beams or beam pairs based on the recommended and / or restricted beams or beam pairs indicated by the UE. The indication of the recommended and / or restricted beams or beam pairs may be based on a self-interference measurement report obtained by the UE.

[0198] In another example, the UE may further indicate additional information associated with each of the recommended and / or restricted beams or beam pairs. For example, the UE may further indicate the following information associated with each of the recommended and / or restricted beams or beam pairs: a bandwidth part (BWP) identifier (ID) or component carrier ID associated with each of the recommended and / or restricted beams or beam pairs; a timing scheme for self-interference measurement (e.g., a measurement timing aligned with downlink timing or uplink self-interference Rx timing); the number of time slots or symbols before the current time at which the self-interference is measured (e.g., indicating that the self-interference is measured M time slots / symbols ago); or a time window for applying the recommended and / or restricted beams or beam pairs (e.g., indicating that the recommended and / or restricted beams or beam pairs are applicable to the future N time slots in the time window).

[0199] Fig.11 1100 is a flowchart of a method for wireless communication. The method may be performed by a network node (e.g., a base station 102 / 602 / 704; a network entity 1302 / 1460). Here, the network node may be a TRP, and the UE may be connected to the network node (e.g., a first network node 602) and another network node (e.g., a second network node 604) using an mTRP configuration. The network node may send scheduling information including timing information for reporting self-interference measurements to the UE, and receive a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. The network node may receive a request for a self-interference measurement report from the UE, and may trigger or initiate a self-interference measurement based on the request received from the UE. The network node may also send a recommendation or restriction on at least one of a Tx beam / antenna panel for UL transmission or an Rx beam / antenna panel for DL ​​transmission based on the self-interference measurement report. The network node may receive the self-interference measurement report from the UE and control scheduling of uplink transmissions via the network node to reduce or minimize self-interference induced at the UE and improve network throughput of downlink signals to the UE.

[0200] At 1110, the network node may send scheduling information for the UE, the scheduling information including timing information for reporting self-interference measurements. Here, the scheduling information may be received based on a request for a self-interference measurement report sent to the network node. For example, the network node may include at least timing information in scheduling information for uplink transmissions (e.g., one or more PUSCH opportunities) to identify uplink transmissions (e.g., specific PUSCH opportunities) subject to self-interference measurements. Based on the request received from the UE, the network node may schedule at least one of periodic uplink transmission resources, aperiodic uplink transmission resources, or semi-persistent UL transmission resources, and include timing information to command the UE to measure the self-interference caused by the scheduled uplink opportunities, and report the self-interference measurements to the network node. For example, at 710, the network node 704 may send scheduling information for the UE 702, the scheduling information including timing information for reporting self-interference measurements. In addition, 1110 may be performed by the self-interference measurement report configuration component 199.

[0201] In one aspect, the scheduling information may instruct the UE to provide self-interference measurements for one or more of the following: a PUSCH opportunity, a dynamic grant of a scheduled aperiodic PUSCH, a PUSCH opportunity with repetition, a PUSCH opportunity without repetition, a time slot or multiple PUSCH opportunities within a time window. The network node may indicate a specific PUSCH or a specific time slot for self-interference measurement, which may be configured for a PUSCH with or without aperiodic scheduling. That is, the scheduling information may be a dynamic grant of a non-periodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate a specific PUSCH in the non-periodic PUSCH opportunity. The UE may obtain and report a self-interference report caused by a specific PUSCH indicated by the timing information included in the scheduling information.

[0202] On the other hand, the scheduling information may instruct the UE to provide self-interference measurements for multiple PUSCH opportunities based on a configuration grant for scheduling periodic PUSCH, and the indication identifies a time window for measuring self-interference. The network node may configure the UE to report, for example, multiple PUSCH opportunities within a time window for self-interference measurements, which may be PUSCH with or without repeated periodic scheduling. That is, the scheduling information may be a configuration grant for a semi-persistent or periodic PUSCH opportunity, and the timing information associated with the self-interference measurement may indicate the time window for the self-interference measurement. The UE may obtain and report a self-interference report caused by one or more PUSCH opportunities within a time window indicated by the timing information associated with the self-interference measurement included in the scheduling information.

[0203] On the other hand, the scheduling information may include RX QCL information for self-interference measurement, and the RX beam may be associated with the Rx QCL information. Here, the Rx QCL information may be associated with at least one of the DG DCI or the RRC DL beam configuration. The scheduling information may or may not configure the Rx QCL information associated with the self-interference measurement. The Rx QCL information associated with the self-interference measurement may indicate the Rx beam to be used for the self-interference measurement, and thus the Rx QCL information may indicate at least one antenna panel for measuring the self-interference.

[0204] In one option, the scheduling information may configure Rx QCL information associated with the self-interference measurement. Based on the Rx QCL information associated with the self-interference measurement, the UE may obtain a self-interference measurement report and send the self-interference measurement report to the network node. That is, the UE may measure the self-interference caused by the uplink transmission (e.g., a specific PUSCH opportunity) at the antenna panel associated with the Rx beam corresponding to the Rx QCL indicated by the scheduling information.

[0205] In another option, the scheduling information may not configure the Rx QCL information associated with the self-interference measurement. Based on the scheduling information not including the Rx QCL information associated with the self-interference measurement, the UE may determine at least one antenna panel for which self-interference is to be measured, and obtain a self-interference measurement report based on an uplink transmission (e.g., a specific PUSCH opportunity) indicated by the timing information of the scheduling information.

[0206] At 1116, the network node may receive a self-interference measurement report including a self-interference measurement based on the scheduling information received from the network node at 1110. In the case where the scheduling information received at 1110 may not configure the Rx QCL information associated with the self-interference measurement, for each measured UL resource, the UE may add an indication or specify the Rx beam QCL information for the self-interference measurement. That is, the UE may include an indication of the QCL information of the Rx beam used to measure the self-interference measurement. For each self-interference measurement of the PUSCH opportunity, the UE may include the QCL information of the Rx beam used to measure the corresponding self-interference measurement in the self-interference measurement report. For example, the indication of the QCL information of the Rx beam may include a DG DCI or a DL beam configuration. For example, at 716, the network node 704 may receive a self-interference measurement report including a self-interference measurement based on the scheduling information received from the network node 704 at 710. In addition, 1116 may be performed by the self-interference measurement report configuration component 199.

[0207] Fig.121200 is a diagram illustrating an example of a hardware implementation for an apparatus 1204. The apparatus 1204 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1204 may include a cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., a cellular RF transceiver). The cellular baseband processor 1224 may include on-chip memory 1224'. In some aspects, the apparatus 1204 may also include one or more subscriber identity module (SIM) cards 1220 and an application processor 1206 coupled to a secure digital (SD) card 1208 and a screen 1210. The application processor 1206 may include on-chip memory 1206'. In some aspects, the device 1204 may also include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., a GNSS module), one or more sensor modules 1218 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement 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 1226, a power source 1230, and / or a camera 1232. The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include their own dedicated antennas and / or communicate using an antenna 1280. The cellular baseband processor 1224 communicates with the UE 104 and / or with the RU associated with the network entity 1202 through the transceiver 1222 via one or more antennas 1280. The cellular baseband processor 1224 and the application processor 1206 may each include a computer-readable medium / memory 1224', 1206', respectively. The additional memory module 1226 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1224', 1206', 1226 may be non-transitory. The cellular baseband processor 1224 and the application processor 1206 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1224 / application processor 1206, enables the cellular baseband processor 1224 / application processor 1206 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1224 / application processor 1206 when executing the software.The cellular baseband processor 1224 / application processor 1206 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1204 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1224 and / or the application processor 1206, and in another configuration, the device 1204 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1204.

[0208] As discussed above, the self-interference measurement reporting component 198 is configured to receive scheduling information including timing information for reporting self-interference measurements, and to send a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. The self-interference measurement reporting component 198 can be within the cellular baseband processor 1224, the application processor 1206, or within both the cellular baseband processor 1224 and the application processor 1206. The self-interference measurement reporting component 198 can be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. As shown, the device 1204 may include a variety of components configured for various functions. In one configuration, the apparatus 1204 (and in particular the cellular baseband processor 1224 and / or the application processor 1206) includes: a component for receiving scheduling information including timing information for reporting self-interference measurements; and a component for sending a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. In one configuration, the scheduling information instructs the UE to provide self-interference measurements for one or more of the following: a PUSCH opportunity, a dynamic grant for scheduling aperiodic PUSCH, a PUSCH opportunity with repetitions, a PUSCH opportunity without repetitions, and multiple PUSCH opportunities within a time slot or time window. In one configuration, the scheduling information instructs the UE to provide self-interference measurements for multiple PUSCH opportunities based on a configured grant for scheduling periodic PUSCH, and the indication identifies a time window for measuring self-interference. In one configuration, the device 1204 (and in particular the cellular baseband processor 1224 and / or the application processor 1206) also includes: a component for sending at least one uplink transmission at the UE; and a component for measuring self-interference of the uplink transmission using at least one Rx beam at the UE and during a time indicated by the scheduling information. In one configuration, the scheduling information includes RX QCL information for self-interference measurement, and the RX beam is associated with the Rx QCL information. In one configuration, the Rx QCL information is associated with at least one of the DG DCI or RRC DL beam configuration. In one configuration, the device 1204 (and in particular the cellular baseband processor 1224 and / or the application processor 1206) also includes a component for sending a request for a self-interference measurement report to a network node before receiving the scheduling information, wherein the scheduling information is received based on the request for the self-interference measurement report sent to the network node.In one configuration, a request for a self-interference measurement report requests one or more of: periodic resources for self-interference measurement, non-periodic resources for self-interference measurement, semi-persistent resources for self-interference measurement, a first measurement for a first beam or a first panel dedicated to an uplink, a second measurement for a second beam or a second panel dedicated to a downlink, or a third measurement for a third beam or a third panel for both the uplink and the downlink.

[0209] In one configuration, the request for a self-interference measurement report indicates at least one subband or component carrier. In one configuration, the request for a self-interference measurement report includes a recommendation or restriction for at least one of a Tx beam / antenna panel for sending at least one uplink transmission or an Rx beam / antenna panel for obtaining self-interference measurements. In one configuration, the recommendation or restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel is based on previous measurements of multiple Tx beams / antenna panels including the Tx beam / antenna panel or multiple Rx beam / antenna panels including the Rx beam / antenna panel. In one configuration, the device 1204 (and in particular the cellular baseband processor 1224 and / or the application processor 1206) also includes a component for using an ML algorithm to estimate the recommendation or restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel. In one configuration, the apparatus 1204 (and in particular the cellular baseband processor 1224 and / or the application processor 1206) further comprises a component for sending a recommendation or restriction for at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on a self-interference measurement report. In one configuration, the apparatus 1204 (and in particular the cellular baseband processor 1224 and / or the application processor 1206) further comprises a component for estimating a recommendation or restriction for at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on a self-interference measurement report using an ML algorithm. In one configuration, the recommendation or restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel also includes at least one information associated with at least one of the Tx beam / antenna panel or the Rx beam / antenna panel, the at least one information including at least one of the following: BWP ID, CCID, measurement timing scheme used, at least one self-interference previously measured before one or more symbols, or a time window for applying the recommendation or the restriction after one or more symbols. The component can be a self-interference measurement reporting component 198 of the device 1204 configured to perform the functions recorded by the component. As described above, the device 1204 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component can be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recorded by the component.

[0210] Fig.131300 is a diagram illustrating an example of a hardware implementation for a network entity 1302. The network entity 1302 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1302 may include at least one of a CU 1310, a DU 1330, or a RU 1340. For example, depending on the layer functionality handled by the self-interference measurement report configuration component 199, the network entity 1302 may include a CU 1310; both a CU 1310 and a DU 1330; each of the CU 1310, the DU 1330, and the RU 1340; the DU 1330; both a DU 1330 and a RU 1340; or a RU 1340. The CU 1310 may include a CU processor 1312. The CU processor 1312 may include an on-chip memory 1312'. In some aspects, the CU 1310 may also include an additional memory module 1314 and a communication interface 1318. CU 1310 communicates with DU 1330 via a midhaul link, such as an F1 interface. DU 1330 may include a DU processor 1332. DU processor 1332 may include on-chip memory 1332'. In some aspects, DU 1330 may also include an additional memory module 1334 and a communication interface 1338. DU 1330 communicates with RU 1340 via a fronthaul link. RU 1340 may include a RU processor 1342. RU processor 1342 may include on-chip memory 1342'. In some aspects, RU 1340 may also include an additional memory module 1344, one or more transceivers 1346, an antenna 1380, and a communication interface 1348. RU 1340 communicates with UE 104. On-chip memory 1312', 1332', 1342' and additional memory modules 1314, 1334, 1344 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1312, 1332, 1342 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 above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0211] As discussed above, the self-interference measurement report configuration component 199 is configured to send scheduling information for the UE, the scheduling information including timing information for reporting self-interference measurement, and receive a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. The self-interference measurement report configuration component 199 can be within one or more processors of one or more of the CU1310, DU 1330, and RU 1340. The self-interference measurement report configuration component 199 can be one or more hardware components, which are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination of the above. The network entity 1302 may include a variety of components configured for various functions. In one configuration, the network entity 1302 includes: a component for sending scheduling information for a user UE, the scheduling information including timing information for reporting self-interference measurement; and a component for receiving a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. In one configuration, the scheduling information instructs the UE to provide self-interference measurements for one or more of: a PUSCH opportunity, a dynamic grant for scheduling aperiodic PUSCH, a PUSCH opportunity with repetitions, a PUSCH opportunity without repetitions, multiple PUSCH opportunities within a time slot or time window. In one configuration, the scheduling information instructs the UE to provide self-interference measurements for multiple PUSCH opportunities based on a configured grant for scheduling periodic PUSCH, and the indication identifies a time window for measuring self-interference. In one configuration, the network entity 1302 also includes a component for receiving at least one uplink transmission at the UE, wherein the scheduling information includes Rx QCL information associated with the self-interference measurement, and the Rx QCL information is associated with an Rx beam used to measure self-interference of the uplink transmission. In one configuration, the Rx QCL information is associated with at least one of a DG DCI or an RRC DL beam configuration. In one configuration, the network entity 1302 also includes a component for receiving a request for a self-interference measurement report before sending the scheduling information, wherein the scheduling information is sent based on the received request for the self-interference measurement report. In one configuration, the request for the self-interference measurement report requests one or more of the following: periodic resources for self-interference measurement, aperiodic resources for self-interference measurement, semi-persistent resources for self-interference measurement, a first measurement for a first beam or a first panel dedicated to the uplink, a second measurement for a second beam or a second panel dedicated to the downlink, or a third measurement for a third beam or a third panel for the uplink and the downlink. In one configuration, the request for the self-interference measurement report indicates at least one subband or component carrier.In one configuration, the request for the self-interference measurement report includes a recommendation or restriction for at least one of a Tx beam / antenna panel for sending at least one uplink transmission or an Rx beam / antenna panel for obtaining self-interference measurements. In one configuration, the network entity 1302 also includes a component for receiving a recommendation or restriction for at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on the self-interference measurement report. In one configuration, the recommendation or restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel also includes at least one information associated with at least one of the Tx beam / antenna panel or the Rx beam / antenna panel, the at least one information including at least one of the following: BWP ID, CC ID, measurement timing scheme used, at least one self-interference previously measured before one or more symbols, or a time window for applying the recommendation or the restriction after one or more symbols. The component can be a self-interference measurement report configuration component 199 of the network entity 1302 configured to perform the functions recorded by the component. As described above, the network entity 1302 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the components may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the components.

[0212] Fig.14 1400 is an example of a hardware implementation for a network entity 1460. In one example, the network entity 1460 may be within the core network 120. The network entity 1460 may include a network processor 1412. The network processor 1412 may include an on-chip memory 1412'. In some aspects, the network entity 1460 may also include an additional memory module 1414. The network entity 1460 communicates directly (e.g., backhaul link) or indirectly (e.g., through RIC) with the CU 1402 via a network interface 1480. The on-chip memory 1412' and the additional memory module 1414 may each be considered as a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 1412 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0213] As discussed above, the self-interference measurement report configuration component 199 is configured to send scheduling information for the UE, the scheduling information including timing information for reporting self-interference measurements, and receive a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. The self-interference measurement report configuration component 199 can be within the processor 1412. The self-interference measurement report configuration component 199 can be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination of the above. The network entity 1460 may include a variety of components configured for various functions. In one configuration, the network entity 1460 includes: a component for sending scheduling information for a user UE, the scheduling information including timing information for reporting self-interference measurements; and a component for receiving a self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. In one configuration, the scheduling information instructs the UE to provide self-interference measurements for one or more of: a PUSCH opportunity, a dynamic grant for scheduling aperiodic PUSCH, a PUSCH opportunity with repetition, a PUSCH opportunity without repetition, multiple PUSCH opportunities within a time slot or time window. In one configuration, the scheduling information instructs the UE to provide self-interference measurements for multiple PUSCH opportunities based on a configured grant for scheduling periodic PUSCH, and the indication identifies a time window for measuring self-interference. In one configuration, the network entity 1460 also includes a component for receiving at least one uplink transmission at the UE, wherein the scheduling information includes Rx QCL information associated with the self-interference measurement, and the Rx QCL information is associated with an Rx beam used to measure self-interference of the uplink transmission. In one configuration, the Rx QCL information is associated with at least one of a DGDCI or an RRC DL beam configuration. In one configuration, the network entity 1460 further comprises means for receiving a request for a self-interference measurement report prior to sending the scheduling information, wherein the scheduling information is sent based on the received request for the self-interference measurement report. In one configuration, the request for the self-interference measurement report requests one or more of: a periodic resource for self-interference measurement, an aperiodic resource for self-interference measurement, a semi-persistent resource for self-interference measurement, a first measurement for a first beam or a first panel dedicated to an uplink, a second measurement for a second beam or a second panel dedicated to a downlink, or a third measurement for a third beam or a third panel for both the uplink and the downlink. In one configuration, the request for the self-interference measurement report indicates at least one subband or component carrier.In one configuration, the request for the self-interference measurement report includes a recommendation or restriction for at least one of a Tx beam / antenna panel for sending at least one uplink transmission or an Rx beam / antenna panel for obtaining self-interference measurements. In one configuration, the network entity 1460 also includes a component for receiving a recommendation or restriction for at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on the self-interference measurement report. In one configuration, the recommendation or restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel also includes at least one information associated with at least one of the Tx beam / antenna panel or the Rx beam / antenna panel, the at least one information including at least one of the following: BWP ID, CCID, measurement timing scheme used, at least one self-interference previously measured before one or more symbols, or a time window for applying the recommendation or the restriction after one or more symbols. The component can be a self-interference measurement report configuration component 199 of the network entity 1460 configured to perform the functions recorded by the component.

[0214] In some aspects of the present disclosure, a UE may receive scheduling information including timing information for reporting a self-interference measurement, and send a self-interference measurement report including the self-interference measurement based on the scheduling information received from a network node. The network node may send scheduling information for the UE, the scheduling information including timing information for reporting a self-interference measurement, and receive the self-interference measurement report including the self-interference measurement based on the scheduling information received from the network node. The UE may send a request for a self-interference measurement report to the network node before receiving the scheduling information, wherein the scheduling information is received based on the request for the self-interference measurement report sent to the network node.

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

[0216] 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 an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

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

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

[0219] Aspect 1 is a method for wireless communication at a UE, the method comprising: receiving scheduling information including timing information for reporting self-interference measurements; and sending a self-interference measurement report including the self-interference measurements based on the scheduling information received from a network node.

[0220] Aspect 2 is a method according to aspect 1, wherein the scheduling information indicates that the UE provides the self-interference measurement for one or more of the following: PUSCH opportunities, dynamic grant of scheduling non-periodic PUSCH, PUSCH opportunities with repetitions, PUSCH opportunities without repetitions, and multiple PUSCH opportunities within a time slot or time window.

[0221] Aspect 3 is a method according to aspect 2, wherein the scheduling information indicates that the UE provides the self-interference measurement for the multiple PUSCH opportunities based on the configuration grant of the scheduling periodic PUSCH, and the indication identifies the time window for measuring the self-interference.

[0222] Aspect 4 is a method according to any one of Aspects 1 to 3, the method further comprising: sending at least one uplink transmission at the UE; and measuring the self-interference of the uplink transmission using at least one Rx beam at the UE and during the time indicated by the scheduling information.

[0223] Aspect 5 is a method according to aspect 4, wherein the scheduling information includes RX QCL information for the self-interference measurement, and the RX beam is associated with the Rx QCL information.

[0224] Aspect 6 is a method according to aspect 5, wherein the Rx QCL information is associated with at least one of DG DCI or RRC DL beam configuration.

[0225] Aspect 7 is a method according to any one of Aspects 1 to 6, the method further comprising: sending a request for the self-interference measurement report to the network node before receiving the scheduling information, wherein the scheduling information is received based on the request for the self-interference measurement report sent to the network node.

[0226] Aspect 8 is a method according to Aspect 7, wherein the request for the self-interference measurement report requests one or more of the following: periodic resources for the self-interference measurement, non-periodic resources for the self-interference measurement, semi-persistent resources for the self-interference measurement, a first measurement of a first beam or a first panel dedicated to an uplink, a second measurement of a second beam or a second panel dedicated to a downlink, or a third measurement of a third beam or a third panel for the uplink and the downlink.

[0227] Aspect 9 is a method according to any one of aspects 7 and 8, wherein the request for the self-interference measurement report indicates at least one subband or component carrier.

[0228] Aspect 10 is a method according to any one of Aspects 7 to 9, wherein the request for the self-interference measurement report includes a recommendation or restriction on at least one of a Tx beam / antenna panel for sending at least one uplink transmission or an Rx beam / antenna panel for obtaining the self-interference measurement.

[0229] Aspect 11 is a method according to Aspect 10, wherein the recommendation or the restriction on at least one of the Tx beam / antenna panel or the Rx beam / antenna panel is based on previous measurements of multiple Tx beam / antenna panels including the Tx beam / antenna panel or multiple Rx beam / antenna panels including the Rx beam / antenna panel.

[0230] Aspect 12 is a method according to any one of Aspects 10 and 11, the method further comprising: using an ML algorithm to estimate the recommendation or the restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel.

[0231] Aspect 13 is a method according to any one of Aspects 1 to 12, the method further comprising: sending a recommendation or restriction on at least one of the Tx beam / antenna panel for uplink transmission or the Rx beam / antenna panel for downlink transmission based on the self-interference measurement report.

[0232] Aspect 14 is a method according to Aspect 13, and the method also includes: using an ML algorithm to estimate the recommendation or the restriction for at least one of the Tx beam / antenna panel for the uplink transmission or the Rx beam / antenna panel for the downlink transmission based on the self-interference measurement report.

[0233] Aspect 15 is a method according to any one of Aspects 13 and 14, wherein the recommendation or the restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel also includes at least one information associated with the Tx beam / antenna panel or the Rx beam / antenna panel, and the at least one information includes at least one of the following: BWP ID, CC ID, the measurement timing scheme used, at least one self-interference previously measured before one or more symbols, or a time window for applying the recommendation or the restriction after one or more symbols.

[0234] Aspect 16 is an apparatus for wireless communication, the apparatus comprising at least one processor coupled to a memory and configured to implement any one of aspects 1 to 15, the apparatus further comprising a transceiver coupled to the at least one processor.

[0235] Aspect 17 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 15.

[0236] Aspect 18 is a 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 15.

[0237] Aspect 19 is a method for performing wireless communications at a network node, the method comprising: sending scheduling information for a user UE, the scheduling information comprising timing information for reporting self-interference measurements; and receiving a self-interference measurement report comprising the self-interference measurement based on the scheduling information received from the network node.

[0238] Aspect 20 is a method according to Aspect 19, wherein the scheduling information indicates that the UE provides the self-interference measurement for one or more of the following: a PUSCH opportunity, a dynamic grant of scheduling aperiodic PUSCH, the PUSCH opportunity with repetition, the PUSCH opportunity without repetition, and multiple PUSCH opportunities within a time slot or time window.

[0239] Aspect 21 is a method according to aspect 20, wherein the scheduling information indicates that the UE provides the self-interference measurement for the multiple PUSCH opportunities based on the configuration grant of the scheduling periodic PUSCH, and the indication identifies the time window for measuring the self-interference.

[0240] Aspect 22 is a method according to any one of Aspects 19 to 21, the method further comprising: receiving at least one uplink transmission at the UE, wherein the scheduling information includes Rx QCL information associated with the self-interference measurement, and the Rx QCL information is associated with an Rx beam used to measure the self-interference of the uplink transmission.

[0241] Aspect 23 is a method according to aspect 22, wherein the Rx QCL information is associated with at least one of DG DCI or RRC DL beam configuration.

[0242] Aspect 24 is a method according to any one of Aspects 19 to 23, the method further comprising: receiving a request for the self-interference measurement report before sending the scheduling information, wherein the scheduling information is sent based on the received request for the self-interference measurement report.

[0243] Aspect 25 is a method according to Aspect 24, wherein the request for the self-interference measurement report requests one or more of the following: periodic resources for the self-interference measurement, non-periodic resources for the self-interference measurement, semi-persistent resources for the self-interference measurement, a first measurement of a first beam or a first panel dedicated to an uplink, a second measurement of a second beam or a second panel dedicated to a downlink, or a third measurement of a third beam or a third panel for the uplink and the downlink.

[0244] Aspect 26 is a method according to any one of aspects 24 and 25, wherein the request for the self-interference measurement report indicates at least one subband or component carrier.

[0245] Aspect 27 is a method according to any one of Aspects 24 to 26, wherein the request for the self-interference measurement report includes a recommendation or restriction on at least one of a Tx beam / antenna panel for sending at least one uplink transmission or an Rx beam / antenna panel for obtaining the self-interference measurement.

[0246] Aspect 28 is a method according to any one of Aspects 19 to 27, the method further comprising: receiving a recommendation or restriction on at least one of a Tx beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission based on the self-interference measurement report.

[0247] Aspect 29 is a method according to Aspect 28, wherein the recommendation or the restriction for at least one of the Tx beam / antenna panel or the Rx beam / antenna panel also includes at least one information associated with the Tx beam / antenna panel or the Rx beam / antenna panel, and the at least one information includes at least one of the following: BWP ID, CC ID, the measurement timing scheme used, at least one self-interference previously measured before one or more symbols, or a time window for applying the recommendation or the restriction after one or more symbols.

[0248] Aspect 30 is an apparatus for wireless communication, the apparatus comprising at least one processor coupled to a memory and configured to implement any one of aspects 19 to 29, the apparatus further comprising a transceiver coupled to the at least one processor.

[0249] Aspect 31 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 19 to 29.

[0250] Aspect 32 is a 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 19 to 29.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving scheduling information including timing information for reporting self-interference measurements; as well as A self-interference measurement report including the self-interference measurement is sent based on the scheduling information received from a network node.

2. The apparatus of claim 1 , further comprising a transceiver coupled to the at least one processor, The scheduling information instructs the UE to provide the self-interference measurement for one or more of the following: Physical Uplink Shared Channel (PUSCH) timing, Scheduling dynamic grants of aperiodic PUSCH, having repeated PUSCH opportunities, said PUSCH opportunities having no duplication, time slot, or Multiple PUSCH opportunities within a time window.

3. The apparatus according to claim 2, wherein the scheduling information instructs the UE to provide the self-interference measurement for the plurality of PUSCH opportunities based on a configuration grant for scheduling periodic PUSCH, and the indication identifies the time window for measuring the self-interference.

4. The apparatus of claim 1 , wherein the at least one processor is further configured to: transmitting at least one uplink transmission at the UE; and Self-interference of the uplink transmission is measured at the UE and during a time indicated by the scheduling information using at least one receive (RX) beam. 5 . The apparatus of claim 4 , wherein the scheduling information includes RX quasi co-location (QCL) information for the self-interference measurement, and the RX beam is associated with the Rx QCL information.

6. The apparatus of claim 5, wherein the Rx QCL information is associated with at least one of a dynamic grant (DG) downlink (DL) control information (DCI) or a radio resource control (RRC) DL beam configuration.

7. The apparatus of claim 1, wherein the at least one processor is further configured to: sending a request for the self-interference measurement report to the network node before receiving the scheduling information, Wherein the scheduling information is received based on the request for the self-interference measurement report sent to the network node.

8. The apparatus of claim 7, wherein the request for the self-interference measurement report requests one or more of the following: a periodic resource for said self-interference measurement; aperiodic resource for said self-interference measurement; A semi-persistent resource for said self-interference measurement; a first measurement of a first beam or a first panel dedicated to uplink; a second measurement of a second beam or a second panel dedicated to the downlink; or A third measurement of a third beam or a third panel for the uplink and the downlink.

9. The apparatus of claim 7, wherein the request for the self-interference measurement report indicates at least one subband or component carrier.

10. The apparatus of claim 7, wherein the request for the self-interference measurement report comprises a recommendation or restriction on at least one of: transmitting at least one transmit (Tx) beam / antenna panel for uplink transmission; or The Rx beam / antenna panel for the self-interference measurement is obtained.

11. An apparatus according to claim 10, wherein the recommendation or the limitation on at least one of the Tx beam / antenna panel or the Rx beam / antenna panel is based on previous measurements of multiple Tx beam / antenna panels including the Tx beam / antenna panel or multiple Rx beam / antenna panels including the Rx beam / antenna panel.

12. The apparatus of claim 10, wherein the at least one processor is further configured to: A machine learning (ML) algorithm is used to estimate the recommendation or the restriction for the at least one of the Tx beam / antenna panel or the Rx beam / antenna panel.

13. The apparatus of claim 1, wherein the at least one processor is further configured to: A recommendation or restriction on at least one of a transmit (Tx) beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission is sent based on the self-interference measurement report.

14. The apparatus of claim 13, wherein the at least one processor is further configured to: The recommendation or the restriction for the at least one of the Tx beam / antenna panel for the uplink transmission or the Rx beam / antenna panel for the downlink transmission is estimated based on the self-interference measurement report using a machine learning (ML) algorithm.

15. The apparatus of claim 13, wherein the recommendation or the restriction on the at least one of the Tx beam / antenna panel or the Rx beam / antenna panel further comprises at least one information associated with the at least one of the Tx beam / antenna panel or the Rx beam / antenna panel, the at least one information comprising at least one of the following: Bandwidth Part (BWP) Identifier (ID); Component Carrier (CC) ID; the measurement timing scheme used; at least one self-interference previously measured one or more symbols before; or A time window for applying the recommendation or the restriction after one or more symbols.

16. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: sending scheduling information for a user equipment (UE), the scheduling information including timing information for reporting self-interference measurements; and A self-interference measurement report including the self-interference measurement is received based on the scheduling information received from the network node.

17. The apparatus of claim 16, further comprising a transceiver coupled to the at least one processor, The scheduling information instructs the UE to provide the self-interference measurement for one or more of the following: Physical Uplink Shared Channel (PUSCH) timing, Scheduling dynamic grants of aperiodic PUSCH, having repeated PUSCH opportunities, said PUSCH opportunities having no duplication, time slot, or Multiple PUSCH opportunities within a time window.

18. The apparatus of claim 17, wherein the scheduling information instructs the UE to provide the self-interference measurement for the plurality of PUSCH opportunities based on a configuration grant for scheduling periodic PUSCH, and the indication identifies the time window for measuring the self-interference.

19. The apparatus of claim 16, wherein the at least one processor is further configured to: receiving at least one uplink transmission at the UE, The scheduling information includes receive (RX) quasi co-location (QCL) information associated with the self-interference measurement, and the Rx QCL information is associated with an Rx beam used to measure the self-interference of the uplink transmission.

20. The apparatus of claim 19, wherein the Rx QCL information is associated with at least one of a dynamic grant (DG) downlink (DL) control information (DCI) or a radio resource control (RRC) DL beam configuration.

21. The apparatus of claim 16, wherein the at least one processor is further configured to: receiving a request for the self-interference measurement report before sending the scheduling information, Wherein the scheduling information is sent based on the received request for the self-interference measurement report.

22. The apparatus of claim 21 , wherein the request for the self-interference measurement report requests one or more of the following: a periodic resource for said self-interference measurement; aperiodic resource for said self-interference measurement; A semi-persistent resource for said self-interference measurement; a first measurement of a first beam or a first panel dedicated to uplink; a second measurement of a second beam or a second panel dedicated to the downlink; or A third measurement of a third beam or a third panel for the uplink and the downlink.

23. The apparatus of claim 21, wherein the request for the self-interference measurement report indicates at least one subband or component carrier.

24. The apparatus of claim 21 , wherein the request for the self-interference measurement report comprises a recommendation or restriction on at least one of: transmitting at least one transmit (Tx) beam / antenna panel for uplink transmission; or The Rx beam / antenna panel for the self-interference measurement is obtained.

25. The apparatus of claim 16, wherein the at least one processor is further configured to: A recommendation or restriction for at least one of a transmit (Tx) beam / antenna panel for uplink transmission or an Rx beam / antenna panel for downlink transmission is received based on the self-interference measurement report.

26. The apparatus of claim 25, wherein the recommendation or the restriction on the at least one of the Tx beam / antenna panel or the Rx beam / antenna panel further comprises at least one information associated with the at least one of the Tx beam / antenna panel or the Rx beam / antenna panel, the at least one information comprising at least one of: Bandwidth Part (BWP) Identifier (ID); Component Carrier (CC) ID; the measurement timing scheme used; at least one self-interference previously measured one or more symbols before; or A time window for applying the recommendation or the restriction after one or more symbols.

27. A method of wireless communication at a user equipment (UE), the method comprising: receiving scheduling information including timing information for reporting self-interference measurements; as well as A self-interference measurement report including the self-interference measurement is sent based on the scheduling information received from a network node.

28. The method according to claim 27, further comprising: sending a request for the self-interference measurement report to the network node before receiving the scheduling information, Wherein the scheduling information is received based on the request for the self-interference measurement report sent to the network node.

29. A method for wireless communication at a network node, the method comprising: sending scheduling information for a user equipment (UE), the scheduling information including timing information for reporting self-interference measurements; as well as A self-interference measurement report including the self-interference measurement is received based on the scheduling information received from the network node.

30. The method according to claim 29, further comprising: receiving a request for the self-interference measurement report before sending the scheduling information, Wherein the scheduling information is sent based on the received request for the self-interference measurement report.

Images