L2 CLI measurement and reporting

Abstract

The present disclosure provides an apparatus, a method, and a computer program product for cross-link interference (CLI) measurement. An example method may include receiving, from a second network entity, a configuration of a set of semi-persistent (SP) or periodic (P) (SP / P) CLI measurement resources for Layer 2 (L2) CLI measurements, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types comprising at least one of: a zero power sounding reference signal (ZP SRS), a channel state information (CSI) interference measurement (CSI IM) resource, a non-zero power (NZP) CSI reference signal (CSI RS), or a combination of the NZP CSI RS and a CSI IM, wherein the one or more measurement resource types are associated with at least one respective CLI reporting metric or are not associated with the respective CLI reporting metric.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 818,958, filed on August 10, 2022, entitled “L2 CLI MEASUREMENT AND REPORTING,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems having cross-link interference (CLI). 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, or even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. 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 is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive a configuration of a semi-persistent (SP) or periodic (P) (SP / P) CLI measurement resource set for layer 2 (L2) cross-link interference (CLI) measurement from a second network entity, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types including at least one of the following: a zero power sounding reference signal (ZPSRS), a channel state information (CSI) interference measurement (CSI IM) resource, a non-zero power (NZP) CSI reference signal (CSI RS), or a combination of the NZP CSI RS and the CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric. The memory and the at least one processor coupled to the memory may be further configured to receive a first activation associated with the SP / P CLI measurement resource set from the second network entity. The memory and the at least one processor coupled to the memory may be further configured to generate CLI measurement information based on the SP / P CLI measurement resource set and the first activation. The memory and the at least one processor coupled to the memory may be further configured to send the CLI measurement information to the second network entity.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to send a configuration of an SP / P CLI measurement resource set for L2 CLI measurement to a second network entity, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resource, NZP CSI RS, or a combination of the NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric. The memory and the at least one processor coupled to the memory may be further configured to send a first activation associated with the SP / P CLI measurement resource set to the second network entity. The memory and the at least one processor coupled to the memory may be further configured to receive CLI measurement information based on the SP / P CLI measurement resource set and the first activation.

[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 is a diagram illustrating an example full-duplex operation.

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

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

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

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

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

[0022] Fig. 6A is a diagram illustrating the first type of full-duplex communication.

[0023] Figure 6B is a diagram illustrating the second type of full-duplex communication.

[0024] Figure 7 is a diagram illustrating an example time slot format for full-duplex communications.

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

[0026] Fig. 9 is a diagram illustrating an example timing configuration.

[0027] Fig.10 is a diagram illustrating an example timing configuration.

[0028] Fig.11 is a diagram illustrating an example timing configuration.

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

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

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

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

[0033] Fig.16 are diagrams illustrating examples of hardware implementations for example devices and / or network entities.

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

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

[0036] Several aspects of the telecommunication system are also 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 can 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.

[0037] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system" including 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, gate logic, 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, procedures, functions, or any combination thereof.

[0038] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions 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. By way of 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.

[0039] 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 / or 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, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in combination with one or more technologies herein. In some actual settings, the equipment incorporating the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0040] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using various components or constituent parts. 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.

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

[0042] 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 utilized 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. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

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

[0044] 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 transmit 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 on a wired transmission medium or to transmit signals to one or more of the other units. In addition, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals on a wireless transmission medium or to transmit signals to one or more of the other units, or both.

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

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

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

[0048] 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 to instantiate 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 .

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

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

[0051] 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 referred to as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also referred to 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., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0052] 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 side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link 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.

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

[0054] 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 (interchangeably) referred to 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).

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

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

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

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

[0059] 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, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signal can 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, an NR signal (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.

[0060] 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 devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terms. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0061] Reference again Figure 1 In some aspects, the UE 104 may include a CLI component 198. In some aspects, the CLI component 198 may be configured to receive a configuration of a semi-persistent (SP) or periodic (P) (SP / P) CLI measurement resource set for layer 2 (L2) cross-link interference (CLI) measurement from a second network entity, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types including at least one of the following: a zero power sounding reference signal (ZP SRS), a channel state information (CSI) interference measurement (CSI IM) resource, a non-zero power (NZP) CSI reference signal (CSI RS), or a combination of a NZP CSI RS and a CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with a corresponding CLI report metric. In some aspects, the CLI component 198 may be further configured to receive a first activation associated with the SP / P CLI measurement resource set from the second network entity. In some aspects, the CLI component 198 may be further configured to generate CLI measurement information based on the SP / P CLI measurement resource set and the first activation. In some aspects, CLI component 198 may be further configured to send the CLI measurement information to the second network entity.

[0062] In certain aspects, the base station 102 may include a CLI component 199. In some aspects, the CLI component 199 may be configured to send a configuration of a SP / P CLI measurement resource set for L2 CLI measurement to a second network entity, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with a corresponding CLI report metric. In some aspects, the CLI component 199 may be further configured to send a first activation associated with the SP / P CLI measurement resource set to the second network entity. In some aspects, the CLI component 199 may be further configured to receive CLI measurement information based on the SP / P CLI measurement resource set and the first activation.

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

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

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

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

[0067] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (1ms) of the same size. 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 time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0068]

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

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

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

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

[0073] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each RE group (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 bandwidth and the number of RBs in the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

[0074] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first one or 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.

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

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

[0077] 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) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Subsequently, each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived based on reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0078] 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 symbol on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on the channel estimate calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0080] Similar to the functions 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.

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

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

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

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

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

[0086] As used herein, the term "SP / P" refers to semi-persistent or periodic. As used herein, the term "associated with" can be used to refer to a scenario in which a CLI measurement resource is configured for measurement based on a first set of one or more CLI reporting metrics and not for measurement based on a second set of one or more CLI reporting metrics. The CLI measurement resource may be referred to as "associated with" the first set of one or more CLI reporting metrics. In some aspects, the measurement resource may be an SRS (e.g., zero power (ZP) SRS), a CSI-IM, an NZP CSI-RS, or a combination of an NZP CSI-RS and a CSI-IM for CLI measurement. In some aspects, the CLI reporting metric may be a reference signal received power (RSRP), a received signal strength indicator (RSSI), or a signal to interference plus noise ratio (SINR). As used herein, the term "activation" may refer to activation for activating a CLI measurement resource, activation for sending CLI measurement information, or joint activation for activating a CLI measurement resource and sending CLI measurement information. As used herein, the term "deactivation" may refer to deactivation for deactivating CLI measurement resources, deactivation for sending CLI measurement information, or a joint deactivation for deactivating CLI measurement resources and sending CLI measurement information. In some aspects, the UE may decode an activation or deactivation and may make one or more changes based on the activation or deactivation according to a timing configuration. The process in which the UE decodes an activation and makes one or more changes based on the activation or deactivation may be referred to as "application" of the activation or deactivation. The term "timing configuration" may refer to a configuration representing the timing of UE behavior (e.g., timing associated with decoding an activation and making one or more changes based on the activation or deactivation), which may be configured at the UE without network signaling. The timing configuration may represent the application of the activation or deactivation after some amount of time, such as after one of the following: a first number of time slots independent of a capability associated with the UE or a second number of time slots based on the capability. As used herein, the term "CLI measurement information" may refer to one or more CLI reports that may each include CLI measurements generated based on one (or at least one) CLI report metric (such as RSRP, RSSI, SINR, etc.). As used herein, the term "layer 2" or "L2" may refer to the MAC layer and the logical link control (LLC) layer. As used herein, the term "CLI measurement resources" may refer to resources used for CLI measurement.

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

[0088] Subband (SB) non-overlapping full-duplex and dynamic / flexible time division duplex (TDD) can be used in wireless communication systems to improve spectrum efficiency and throughput by dynamically changing the UL or DL ​​transmission direction. However, CLI between network entities and UEs may occur, which may be intra-subband CLI or inter-subband CLI. The victim UE or victim network entity may receive transmissions from the attacker UE or attacker network entity that are not targeted at the victim. For example, CLI may occur when the UL / DL symbol from the attacker conflicts with the UL / DL symbol of the victim. The various aspects provided herein may be beneficial to solving CLI, thereby improving the overall efficiency in the communication system.

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

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

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

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

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

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

[0095] Full-duplex operation may be in the form of in-band full-duplex (IBFD) or sub-band frequency division duplex (FDD) (otherwise known as "flexible duplex"). Fig. 6A As shown in diagram 600 in FIG. 1 , for IBFD, transmission and reception may occur simultaneously (eg, overlap in time) and on the same frequency resources (eg, using overlapping frequency resources). Fig. 6A As shown, in some examples, the IBFD time / frequency resources for downlink 602A and the IBFD time / frequency resources for uplink 604A can completely overlap. In other examples, the IBFD time / frequency resources for downlink 602B and the IBFD time / frequency resources for uplink 604B can partially overlap, such as Fig. 6A shown.

[0096] For sub-band FDD, as exemplified in the second type of full-duplex communication (sub-band FDD) Figure 6BAs shown in diagram 610 in FIG. 1 , transmission and reception may occur simultaneously (e.g., at least partially overlap in time), but on different frequency resources. Downlink resources 602C may be separated from uplink resources 604C in the frequency domain. For example, this separation may be referred to as a guard band 606 and may provide a frequency gap or frequency separation between downlink resources 602C and uplink resources 604C.

[0097] Figure 7 700 is a diagram illustrating an example time slot format for full-duplex communication. The time slot format may include a "D+U" time slot, where the frequency band may be used for both UL and DL transmissions. DL transmissions and UL transmissions may occur in overlapping frequency bands (intra-band full-duplex) or adjacent frequency bands (sub-band full-duplex). In a "D+U" symbol, an HD UE may transmit in the UL frequency band or receive in the DL frequency band. In a "D+U" symbol, an FD UE may transmit in the UL frequency band and receive in the DL frequency band in the same time slot. A "D+U" time slot may include a DL symbol, a UL symbol, or a full-duplex symbol.

[0098] Figure 8 800 is a diagram illustrating an example communication between a network entity 804 and a UE 802. In some aspects, the network entity 804 may be implemented as a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. In some aspects, the network entity 804 may be implemented in a converged or monolithic base station architecture, or alternatively in a decomposed base station architecture, and may include one or more of a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In some aspects, the UE 802 may be a victim UE. In some aspects, the UE 802 may be an attacker UE.

[0099] like Figure 8As shown, UE 802 may receive configuration of CLI measurement resources 806 from network entity 804. In some aspects, the configuration of CLI measurement resources 806 may configure different types of CLI measurement resources, such as SRS (e.g., zero power (ZP) SRS), CSI-IM, NZP CSI-RS, or a combination of NZP CSI-RS+CSI-IM for CLI measurement. In some aspects, the resource type is not associated with a CLI reporting metric (e.g., RSRP, RSSI, SINR, etc.). In some aspects, the resource type is not associated with a CLI reporting metric. By way of example, NZP CSI-RS may be associated with CLI-SINR, ZP-CSI RS or CSI-IM may be associated with CLI-RSSI or CLI-RSRP, a combination of CSI RS and CSI-IM may be associated with CLI-RSSI, CLI-RSSI, or CLI-RSRP, and an SRS used for CLI measurement (e.g., ZP SRS) may be associated with CLI-RSSI, CLI-RSSI, or CLI-RSRP.

[0100] In some aspects, the configuration 806 of the CLI measurement resources may configure the CLI measurement resources into CLI measurement resource subsets, where each resource subset may include one or more CLI measurement resources. In some aspects, different resources in the same CLI measurement resource subset may be associated with different beams (which may also be referred to as "spatial filters").

[0101] In response to different conditions, the beam can be switched. For example, a transmit configuration indication (TCI) state change can be sent by the base station so that the UE can switch to a new beam for the TCI state. The TCI state change enables the UE to find the best UE receive beam corresponding to the TCI state from the base station and switch to such a beam. Switching beams can allow an enhanced or improved connection between the UE and the base station by ensuring that the transmitter and receiver communicate using the same configured beam set. The TCI state may include quasi-co-location (QCL) information, which the UE can use to derive timing / frequency errors and / or transmit / receive spatial filtering for transmitting / receiving signals. If the properties of the channel for transmitting symbols on one antenna port can be inferred from the channel for transmitting symbols on another antenna port, the two antenna ports are referred to as quasi-co-located. The base station may indicate the TCI state to the UE as a transmit configuration, which indicates the QCL relationship between a signal (e.g., a reference signal) and a signal to be transmitted / received. For example, the TCI state may indicate the QCL relationship between the DL RS and the PDSCH / PDCCH DM-RS port in one RS set. The TCI state may provide information about different beam selections used by the UE to send / receive various signals. Under the unified TCI framework, different types of common TCI states may be indicated. For example, type 1 TCI may be a joint DL / UL common TCI state to indicate a common beam for at least one DL channel or RS and at least one UL channel or RS. Type 2 TCI may be a separate DL (e.g., separate from UL) common TCI state to indicate a common beam for more than one DL channel or RS. Type 3 TCI may be a separate UL common TCI state to indicate a common beam for more than one UL channel / RS. Type 4 TCI may be a separate DL single channel or RS TCI state to indicate a beam for a single DL channel or RS. Type 5 TCI may be a separate UL single channel or RS TCI state to indicate a beam for a single UL channel or RS. Type 6 TCI may include UL spatial relationship information (e.g., such as a sounding reference signal (SRS) resource indicator (SRI)) to indicate the beam used for a single UL channel or RS. Example RSs may be SSBs, tracking reference signals (TRS) and associated CSI-RS for tracking, CSI-RS for beam management, CSI-RS for CQI management, DM-RS associated with non-UE-dedicated reception on PDSCH, and a subset of the control resource set (CORESET) (which may be the full set), etc. A TCI state may be defined to represent at least one source RS to provide a reference (e.g., UE assumption) for determining a quasi co-location (QCL) or spatial filter. For example, a TCI state may define a QCL assumption between a source RS and a target RS. The QCL may be of different types.Regarding QCL types, QCL type A may include Doppler shift, Doppler spread, average delay, and delay spread; QCL type B may include Doppler shift and Doppler spread; QCL type C may include Doppler shift and average delay; and QCL type D may include spatial Rx parameters (e.g., associated with beam information such as beamforming properties used to find a beam).

[0102] As another example, a spatial relationship change (such as a spatial relationship update) may trigger the UE to switch beams. Beamforming may be applied to uplink channels, such as but not limited to PUCCH. Beamforming may be based on configuring one or more spatial relationships between uplink signals and downlink signals. The spatial relationship may indicate that the UE may use the same beam as it uses to receive the corresponding downlink signal to send the uplink signal.

[0103] In some aspects, the configuration of CLI measurement resources 806 may configure CLI measurement resources (which may still be referred to as a "set of CLI measurement resources") without indicating that the set of CLI measurement resources is a set. In some aspects where the configuration of CLI measurement resources 806 may configure CLI measurement resources without indicating that the set of CLI measurement resources is a set, an activation (such as an activation 808 sent from the network entity 804 to the UE 802) may activate different resources in the set of CLI measurement resources. In some aspects, the activation 808 may be a MAC control element (MAC CE).

[0104] In some aspects where the configuration of CLI measurement resources 806 may configure the CLI measurement resources as a set of CLI measurement resources, activation 808 may activate a different subset of the configured CLI measurement resources. In some aspects, activation 808 may be a joint activation for CLI measurement and reporting. In some aspects where activation 808 is a joint activation for CLI measurement and reporting, UE 802 may activate CLI measurement resources at 810, perform CLI measurements at 812, and send measurement results 814 based on activation 808. In some aspects, there may be a one-to-one mapping between SP CLI measurement resources or resource subsets and corresponding L2 CLI reports. For example, SP CLI measurement resource type A 850 may be mapped one-to-one to L2 CLI report A 852.

[0105] In some aspects, activation 808 may be an activation for CLI measurement, and there may be a separate activation for CLI reporting (e.g., activation 811). In some aspects where activation 808 may be an activation for CLI measurement and there may be an activation 811 for CLI reporting, the UE 802 may activate CLI measurement resources at 810 based on activation 808 and perform CLI measurement at 812, then send measurement results 814 based on activation 811. In some aspects, multiple reports may share the same measurement resource. For example, SP CLI measurement resource type A 860 may be shared by L2 CLI report A 862A and L2 CLI report B 862B.

[0106] In some aspects, activation 808 may activate the set of one or more CLI measurement resources at a set level. For example, activation 808 may include an identifier (ID) associated with the set, and upon receiving activation 808, UE 802 may activate the entire set accordingly. In some aspects, activation 808 may activate the set of one or more CLI measurement resources at a subset level. For example, activation 808 may activate the set of one or more CLI measurement resources at a subset level. For example, activation 808 may include a bitmap, wherein each bit in the bitmap corresponds to a resource in the set. For example, a bitmap with entry "1100" may indicate that the first two resources are activated and the second two resources are not activated. In some aspects, activation 808 may activate the set of one or more CLI measurement resources at a single resource level. For example, activation 808 includes one or more resource IDs of resources to be activated or one or more resource IDs of resources that are not being activated.

[0107] In some aspects, activation 808 may be a MAC-CE and may include QCL (which may correspond to TCI state and spatial relationship) information for the resource. In some aspects where activation 808 may set a level to activate the set of one or more CLI measurement resources, activation 808 may be a MAC-CE including QCL information (such as a QCL information list), where each entry in the list maps to one CLI measurement resource. For example, activation 808 may be activating SP SRS or SP CSI-RS. In some aspects where activation 808 can activate a set of one or more CLI measurement resources at a subset level or a resource level, activation 808 can be a MAC-CE that includes: (1) QCL information for the resources to be activated (such as a list of QCL information), wherein each entry in the list maps to one CLI measurement resource being activated; (2) QCL information for the resources to be activated and QCL update information for already active resources (such as a list of QCL information), wherein each entry in the list maps to one CLI measurement resource being activated; and a second list of QCL update information, wherein each entry in the list maps to one active CLI measurement resource; or (3) QCL information for all resources in the set of one or more CLI measurement resources regardless of whether the resources are being activated.

[0108] In some aspects, the UE 802 and the network entity 804 may communicate (e.g., by sending or receiving a transmission 816) based on the measurement results 814. For example, the network entity 804 may determine that the CLI is not large based on the measurement results 814, and continue to send or receive (e.g., schedule the transmission or reception) the transmission 816. In some aspects, the network entity 804 may send a deactivation 818 to deactivate at least one resource in the set of one or more CLI measurement resources. In some aspects, the deactivation 818 may be a joint deactivation that also deactivates reporting of the measurement results. In some aspects, the network entity 804 may also send a deactivation 820 to deactivate reporting based on the measurement of at least one resource in the set of one or more CLI measurement resources.

[0109] In some aspects, there may be a timing configuration associated with activation 808, activation 811, deactivation 818, or deactivation 820. For example, the timing configuration may represent an amount of time that the UE 802 may use to decode the activation or deactivation and make one or more changes to the UE behavior based on the activation or deactivation. In some aspects, the same timing configuration may be applied to both activation and deactivation. In some aspects, different timing configurations may be applied to activation and deactivation.

[0110] In some aspects, when UE 802 receives an activation command (e.g., activation 808) for SP CLI measurement resources / resource sets, and when UE 802 may send a PUCCH with HARQ-ACK information in time slot n corresponding to the PDSCH carrying the command, corresponding actions and UE assumptions (including QCL assumptions) may be applied starting from the first time slot that is one of the following time slots: 1) time slot Afterwards; 2) Time slot Afterwards; 3) Time slot After that, where X depends on the UE capability; or 4) time slot After that, where X<3 and Y depends on the UE capability. Parameters μ may represent the number of slots per subframe used for the subcarrier spacing represented by μ. Slot n may be the slot associated with the confirmation of activation.

[0111] In some aspects, when UE 802 receives a deactivation command (e.g., deactivation 818) for SP CLI measurement resources / resource sets, and when UE 802 may send a PUCCH with HARQ-ACK information in time slot n corresponding to the PDSCH carrying the command, corresponding actions and UE assumptions (including QCL assumptions) may be applied starting from the first time slot after: 1) time slot Afterwards; 2) Time slot Afterwards; 3) Time slot After that, where X depends on the UE capability; or 4) time slot After that, where X<3 and Y depends on the UE capability. Parameters μ may represent the number of slots per subframe used for the subcarrier spacing represented by μ. Slot n may be the slot associated with the confirmation of deactivation.

[0112] Fig. 9 900 is a diagram illustrating an example timing configuration. Fig. 9 As shown, when receiving the activation in DL MAC-CE 902, the UE may send a HARQ ACK (eg, ACK 906). The time slot in which the UE sends the ACK 906 may be time slot n 904. The first time slot thereafter starts applying the corresponding actions and timing configuration 908 of the UE assumptions (including QCL assumptions), and the UE may activate the corresponding measurement resources at 910 .

[0113] In some aspects, the timing configuration for activation (e.g., activation 811) or deactivation (deactivation 820) of L2 CLI reporting can be the same, where the same timing configuration is applied to both activation and deactivation. In some aspects, the timing configuration for activation (e.g., activation 811) or deactivation (deactivation 820) of L2 CLI reporting can be different, where different timing configurations can be applied to activation and deactivation. In some aspects, when UE 802 is to send a PUCCH with HARQ-ACK information in time slot "n" corresponding to the PDSCH carrying the activation command (e.g., activation 811) for L2 CLI reporting, the indicated L2 CLI reporting can be applied starting from the first time slot after the following time slots: 1) time slot Afterwards; 2) Time slot Afterwards; 3) Time slot After that, where X depends on the UE capability; or 4) time slot Thereafter, where X<3 and Y depends on UE capabilities. Wherein different timing configurations may be applied for activation and deactivation. In some aspects, when UE 802 is to send a PUCCH with HARQ-ACK information in time slot "n" corresponding to a PDSCH deactivation command (e.g., deactivate 820) carrying an L2 CLI report, the indicated L2 CLI report may be applied starting from the first time slot after: 1) time slot Afterwards; 2) Time slot Afterwards; 3) Time slot After that, where X depends on the UE capability; or 4) time slot After that, where X<3 and Y depends on the UE capabilities.

[0114] In some aspects where activation 808 is a joint activation of L2 CLI measurement resources and reporting, the same timing configuration may be associated with the activation of the measurement resources and the activation of the reporting. For example, when UE 802 may send a PUCCH with HARQ-ACK information in time slot n corresponding to the PDSCH carrying the command, the corresponding actions and UE assumptions (including QCL assumptions) may be applied starting from the first time slot after: 1) time slot Afterwards; 2) Time slot Afterwards; 3) Time slot After that, where X depends on the UE capability; or 4) time slot Thereafter, where X<3 and Y depends on the UE capabilities. In some aspects where activation 808 is a joint activation of L2 CLI measurement resources and reporting, different timing configurations may be associated with the activation of measurement resources and the activation of reporting. In some aspects, a less stringent timing configuration among the different timing configurations may be used by the UE for both the activation of measurement resources and the activation of reporting. For example, if The timing configuration is associated with the activation of the CLI measurement resource and The timing configuration is associated with the activation of the CLI report, then you can apply Because this is a less stringent timing configuration. In some aspects, the more stringent timing configuration among the different timing configurations may be used by the UE for both activation of measurement resources and activation of reporting. For example, if The timing configuration is associated with the activation of the CLI measurement resource and The timing configuration is associated with the activation of the CLI report, then you can apply Because this is a stricter timing configuration. In some aspects, the timing configuration associated with activation of CLI measurement resources may apply. In some aspects, the timing configuration associated with activation of CLI reporting may apply.

[0115] In some aspects where deactivation 818 is a joint deactivation of activating L2 CLI measurement resources and reporting, the same timing configuration may be associated with the deactivation of measurement resources and the deactivation of reporting. For example, when UE 802 may send a PUCCH with HARQ-ACK information in time slot n corresponding to the PDSCH carrying the command, the corresponding actions and UE assumptions (including QCL assumptions) may be applied starting from the first time slot after: 1) time slot Afterwards; 2) Time slot Afterwards; 3) Time slot After that, where X depends on the UE capability; or 4) time slot Thereafter, where X<3 and Y depends on the UE capabilities. In some aspects where deactivation 818 is deactivation of joint activation of L2 CLI measurement resources and reporting, different timing configurations may be associated with deactivation of measurement resources and deactivation of reporting. In some aspects, a less stringent timing configuration among the different timing configurations may be used by the UE for both deactivation of measurement resources and deactivation of reporting. For example, if The timing configuration is associated with the deactivation of CLI measurement resources and If the timing configuration is associated with the deactivation of CLI reporting, you can apply Because this is a less stringent timing configuration. In some aspects, the more stringent timing configuration among the different timing configurations may be used by the UE for both deactivation of measurement resources and deactivation of reporting. For example, if The timing configuration is associated with the deactivation of CLI measurement resources and The timing configuration is related to the deactivation of CLI reports, then you can apply Because this is a stricter timing configuration. In some aspects, the timing configuration associated with the deactivation of CLI measurement resources may apply. In some aspects, the timing configuration associated with the deactivation of L2 CLI reporting may apply.

[0116] In some aspects, if the UE 802 has an active SP CLI measurement resource configuration, the activated configuration may be considered active when the corresponding DL bandwidth part (BWP) is active. When the corresponding DL BWP is inactive, the SP CLI measurement resource configuration may be considered suspended. In some aspects, if the UE 802 is configured with carrier deactivation, the semi-persistent CLI measurement resource / resource set may also be deactivated. If the UE 802 is in active L2 CLI reporting and has not received a deactivation command (e.g., deactivate 818 or deactivate 820), L2 CLI reporting may be performed when the BWP in which reporting is configured to be on is the active BWP, otherwise L2 CLI reporting may be suspended.

[0117] Fig.10 1000 is a diagram illustrating an example timing configuration. In some aspects, the SP CLI measurement resource set may contain one or more resources and different resources may have different time slot offsets. In some aspects, when L2 CLI reporting is activated (e.g., based on activation 808 or activation 811), some of the opportunities for resources in the SP CLI measurement resource set (e.g., at 1002) may occur before a first time slot in which L2 CLI reporting is considered active based on the timing configuration. In some aspects, the first L2 CLI report may include measurements since the occurrence of some of the resources in the first epoch (e.g., may include measurements since the first occurrence of time slots 1004 and 1006). In some aspects, if some of the resources are before the first active time slot, the first L2 CLI report does not include measurements since the first epoch (e.g., may not include measurements since the first occurrence of time slots 1004 and 1006).

[0118] Fig.111100 is a diagram illustrating an example timing configuration. In some aspects, the SP CLI measurement resource set may contain one or more resources and different resources may have different time slot offsets. In some aspects, when L2 CLI reporting is disabled (e.g., based on disable 818 or disable 82-), some of the timings of the resources (e.g., 1104 and 1106) in the SP CLI measurement resource set may occur after the first time slot in which the L2 CLI reporting is considered inactive based on the timing configuration. In some aspects, the last L2 CLI report may include measurements since the occurrence of some of the resources in the last epoch (e.g., may include measurements since the last occurrence of time slot 1102). In some aspects, if some resources are inactive after setting, then the last L2 CLI report does not include measurements since the last epoch (e.g., may not include measurements since the last occurrence of time slot 1102).

[0119] Fig.12 1200 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, UE 802; device 1604). The UE may include at least one processor coupled to a memory.

[0120] At 1202, the UE may receive a configuration of a set of SP / P CLI measurement resources for L2 CLI measurement from a second network entity, wherein the set of SP / P CLI measurement resources is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric. For example, the UE 802 may receive a configuration of a set of SP / P CLI measurement resources for L2 CLI measurement from a second network entity (e.g., 806), wherein the set of SP / P CLI measurement resources is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric. In some aspects, 1202 may be performed by the CLI component 198.

[0121] At 1204, the UE may receive a first activation associated with the SP / P CLI measurement resource set from a second network entity. For example, UE 802 may receive a first activation associated with the SP / P CLI measurement resource set from a second network entity (e.g., 808). In some aspects, 1204 may be performed by CLI component 198.

[0122] At 1206, the UE may generate CLI measurement information based on the SP / P CLI measurement resource set and the first activation. For example, the UE 802 may generate CLI measurement information based on the SP / P CLI measurement resource set and the first activation (e.g., at 812). In some aspects, 1206 may be performed by the CLI component 198.

[0123] At 1208, the UE may send the CLI measurement information to the second network entity. For example, UE 802 may send the CLI measurement information (eg, 814) to the second network entity. In some aspects, 1206 may be performed by CLI component 198.

[0124] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, UE 802; device 1604). The UE may include at least one processor coupled to a memory.

[0125] At 1302, the UE may receive a configuration of a set of SP / P CLI measurement resources for L2 CLI measurement from a second network entity, wherein the set of SP / P CLI measurement resources is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric. For example, the UE 802 may receive a configuration of a set of SP / P CLI measurement resources for L2 CLI measurement from a second network entity (e.g., 806), wherein the set of SP / P CLI measurement resources is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric. In some aspects, 1302 may be performed by the CLI component 198. In some aspects, the one or more measurement resource types are not associated with corresponding CLI reporting metrics. In some aspects, the one or more measurement resource types are associated with the at least one corresponding CLI reporting metric, wherein the ZPSRS is associated with RSRP, RSSI or SINR, wherein the NZP CSI RS is associated with RSSI and RSRP, wherein the CSI IM is associated with RSSI or RSRP, and wherein the combination is associated with RSSI, RSRP and SINR. In some aspects, the configuration of the SP / P CLI measurement resource set indicates one or more time and frequency resources, and wherein the configuration of the SP / P CLI measurement resource set indicates the one or more time and frequency resources as a resource set. In some aspects, the configuration is active when a downlink BWP associated with the configuration is active. In some aspects, the configuration is inactive when a carrier associated with the configuration is deactivated. In some aspects, the configuration is inactive when a BWP associated with the configuration is deactivated.

[0126] At 1304, the UE may receive a first activation associated with the SP / P CLI measurement resource set from a second network entity. For example, UE 802 may receive a first activation associated with the SP / P CLI measurement resource set from a second network entity (e.g., 808). In some aspects, 1304 may be performed by CLI component 198. In some aspects, the first activation indicates one or more time and frequency resources associated with the SP / P CLI measurement resource set, and wherein a configuration of the SP / P CLI measurement resource set does not indicate the one or more time and frequency resources as a resource set. In some aspects, the first activation is a MAC CE, and wherein the first activation includes an ID of the SP / P CLI measurement resource set, and wherein the first activation is configured to activate the SP / P CLI measurement resource set. In some aspects, the first activation includes a list including respective QCL information mapped to each respective resource in the SP / P CLI measurement resource set. In some aspects, the first activation is a MAC CE, and wherein the first activation includes a bitmap associated with the SP / P CLI measurement resource set and is configured to activate a subset of the SP / P CLI measurement resource set, wherein each bit in the bitmap corresponds to a respective resource in the SP / P CLI measurement resource set. In some aspects, the first activation is configured to activate a subset of the SP / P CLI measurement resource set, and wherein the first activation includes: respective QCL information mapped to each respective resource in the SP / P CLI measurement resource set, or respective QCL information mapped to each respective resource in the subset of CLI SP / P CLI measurement resources. In some aspects, the first activation is configured to activate a subset of the SP / P CLI measurement resource set, and wherein the first activation includes a first list of QCL information and a second list of QCL update information, wherein each respective QCL information in the first list is mapped to a respective resource in the subset of SP / P CLI measurement resources, and wherein each respective QCL update information in the second list is mapped to a respective resource of a second active subset of the SP / P CLI measurement resource set. In some aspects, the first activation is a MAC CE, and wherein the first activation includes one or more resource IDs, wherein each respective resource ID in the resource IDs is associated with a respective resource in the set of SP / P CLI measurement resources, and wherein the first activation is configured to activate the respective resource. In some aspects, the first activation includes a list of QCL information, and wherein each respective QCL information in the list is mapped to a respective resource in the set of SP / P CLI measurement resources.

[0127] At 1305, the UE may receive a second activation. For example, UE 802 may receive a second activation (e.g., 811). In some aspects, 1310 may be performed by CLI component 198. In some aspects, the first activation is a first MAC CE, wherein the at least one processor is configured to: receive a second activation, wherein to send CLI measurement information, the at least one processor is configured to send CLI measurement information based on the second activation, and wherein the second activation is a second MAC CE different from the first MAC CE. In some aspects, to send the CLI measurement information, the at least one processor is configured to send the CLI measurement information based on the second activation.

[0128] At 1306, the UE may generate CLI measurement information based on the SP / P CLI measurement resource set and the first activation. For example, the UE 802 may generate CLI measurement information based on the SP / P CLI measurement resource set and the first activation (e.g., at 812). In some aspects, 1306 may be performed by the CLI component 198.

[0129] At 1308, the UE may send the CLI measurement information to the second network entity. For example, UE 802 may send the CLI measurement information (eg, 814) to the second network entity. In some aspects, 1308 may be performed by CLI component 198.

[0130] At 1312, the UE may receive a first deactivation associated with the set of SP / P CLI measurement resources. For example, the UE 802 may receive a first deactivation associated with the set of SP / P CLI measurement resources (e.g., 818). In some aspects, 1312 may be performed by the CLI component 198.

[0131] At 1314, the UE may receive a second deactivation configured to deactivate generation of second CLI measurement information based on the SP / P CLI measurement resource set. For example, the UE 802 may receive a second deactivation configured to deactivate generation of second CLI measurement information based on the SP / P CLI measurement resource set (e.g., 820). In some aspects, 1314 may be performed by the CLI component 198.

[0132] In some aspects, a first timing configuration associated with the first deactivation is equivalent to a second timing configuration associated with the first activation. In some aspects, the first timing configuration associated with the first deactivation is different from the second timing configuration associated with the first activation. In some aspects, the first timing configuration is associated with the first deactivation and the second timing configuration is associated with the first activation, and wherein the second timing configuration represents application of the first activation after one of: a first number of time slots independent of a capability associated with the first network entity, or a second number of time slots based on the capability. In some aspects, the second number is equal to one of: or wherein X is a first positive integer based on capabilities, wherein Y is a second positive integer based on capabilities, wherein Z is a third positive integer independent of capabilities, wherein n is associated with time slot n, time slot n is associated with an acknowledgement (ACK) associated with the first activation, and wherein represents the number of time slots for each subframe of the subcarrier spacing represented by μ. In some aspects, the first timing configuration is associated with the first deactivation and the second timing configuration is associated with the first activation, and wherein the first timing configuration represents application of the first deactivation after one of: a first number of time slots independent of a capability associated with the first network entity, or a second number of time slots based on the capability. In some aspects, the second number is equal to one of: or wherein X is a first positive integer based on the capabilities, wherein Y is a second positive integer based on the capabilities, wherein Z is a third positive integer independent of the capabilities, wherein n is associated with time slot n, time slot n is associated with an acknowledgement (ACK) associated with the first deactivation, and wherein represents the number of time slots for each subframe of the subcarrier spacing represented by μ. In some aspects, the first timing configuration associated with the second deactivation is equivalent to the second timing configuration associated with the second activation. In some aspects, the first timing configuration associated with the second deactivation is different from the second timing configuration associated with the second activation. In some aspects, the first timing configuration is associated with the second deactivation and the second timing configuration is associated with the second activation, and wherein the second timing configuration represents the application of the second activation after one of: a first number of time slots independent of a capability associated with the first network entity, or a second number of time slots based on the capability. In some aspects, the second number is equal to one of: or wherein X is a first positive integer based on the capabilities, wherein Y is a second positive integer based on the capabilities, wherein Z is a third positive integer independent of the capabilities, wherein n is associated with time slot n, time slot n is associated with an acknowledgement (ACK) associated with the second activation, and wherein represents the number of time slots for each subframe of the subcarrier spacing represented by μ. In some aspects, the first timing configuration is associated with the second deactivation and the second timing configuration is associated with the second activation, and wherein the first timing configuration represents application of the second deactivation after one of: a first number of time slots independent of a capability associated with the first network entity, or a second number of time slots based on the capability. In some aspects, the second number is equal to one of: or wherein X is a first positive integer based on the capabilities, wherein Y is a second positive integer based on the capabilities, wherein Z is a third positive integer independent of the capabilities, wherein n is associated with time slot n, time slot n is associated with an acknowledgement (ACK) associated with the second deactivation, and wherein Represents the number of time slots for each subframe of the subcarrier spacing represented by μ. In some aspects, the timing configuration is associated with the second activation, and wherein at least one resource that is earlier in time than the application of the second activation based on the timing configuration is included in the measurement set or excluded from the measurement set. In some aspects, the timing configuration is associated with the second deactivation, and wherein at least one resource that is earlier in time than the application of the second deactivation based on the timing configuration is included in the measurement set or excluded from the measurement set. In some aspects, the joint activation in the first MAC CE includes a first activation and a second activation, and wherein the joint deactivation in the second MAC CE includes a first deactivation and a second deactivation, wherein the first timing configuration is associated with the first activation, the second timing configuration is associated with the second activation, the third timing configuration is associated with the first deactivation, and the fourth timing configuration is associated with the second deactivation. In some aspects, the first timing configuration is equivalent to the second timing configuration, and wherein the third timing configuration is equivalent to the fourth timing configuration. In some aspects, the UE may apply one of the first timing configuration or the second timing configuration based on one of the following: a first less strict timing configuration in the first timing configuration or the second timing configuration, the first timing configuration, the second timing configuration, or a first more strict timing configuration in the first timing configuration or the second timing configuration. In some aspects, the UE may apply one of the third timing configuration or the fourth timing configuration based on one of the following: a second less strict timing configuration in the third timing configuration or the fourth timing configuration, the third timing configuration, the fourth timing configuration, or a second more strict timing configuration in the third timing configuration or the fourth timing configuration.

[0133] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 804, network entity 1602, network entity 1702).

[0134] At 1402, the network entity may send a configuration of a set of SP / P CLI measurement resources for L2 CLI measurement to a second network entity, wherein the set of SP / P CLI measurement resources is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric. For example, the network entity 804 may send a configuration of a set of SP / P CLI measurement resources for L2 CLI measurement to a second network entity (e.g., UE 802) (e.g., 806), wherein the set of SP / P CLI measurement resources is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric. In some aspects, 1402 may be performed by CLI component 199 .

[0135] At 1404, the network entity may send a first activation associated with the SP / P CLI measurement resource set to a second network entity. For example, the network entity 804 may send a first activation associated with the SP / P CLI measurement resource set (e.g., 808) to a second network entity (e.g., UE 802). In some aspects, 1404 may be performed by the CLI component 199.

[0136] At 1406, the network entity may receive CLI measurement information based on the SP / P CLI measurement resource set and the first activation. For example, the network entity 804 may receive CLI measurement information (e.g., 814) based on the SP / P CLI measurement resource set and the first activation. In some aspects, 1406 may be performed by the CLI component 199.

[0137] Fig.15 1500 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 804, network entity 1602, network entity 1702).

[0138] At 1502, the network entity may send a configuration of a set of SP / P CLI measurement resources for L2 CLI measurement to a second network entity, wherein the set of SP / P CLI measurement resources is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric. For example, the network entity 804 may send a configuration of a set of SP / P CLI measurement resources for L2 CLI measurement to a second network entity (e.g., UE 802) (e.g., 806), wherein the set of SP / P CLI measurement resources is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric. In some aspects, 1502 may be performed by CLI component 199. In some aspects, the one or more measurement resource types are not associated with corresponding CLI report metrics. In some aspects, the one or more measurement resource types are associated with the at least one corresponding CLI report metric, wherein ZP SRS is associated with RSRP, RSSI, or SINR, wherein NZP CSI RS is associated with RSSI and RSRP, wherein CSI IM is associated with RSSI or RSRP, and wherein the combination is associated with RSSI, RSRP, and SINR. In some aspects, the configuration of the SP / P CLI measurement resource set indicates one or more time and frequency resources, and wherein the configuration of the SP / P CLI measurement resource set indicates the one or more time and frequency resources as a resource set.

[0139] At 1504, the network entity may send a first activation associated with the SP / P CLI measurement resource set to a second network entity. For example, the network entity 804 may send a first activation associated with the SP / P CLI measurement resource set to a second network entity (e.g., UE 802) (e.g., 808). In some aspects, 1504 may be performed by the CLI component 199. In some aspects, the first activation indicates one or more time and frequency resources associated with the SP / P CLI measurement resource set, and wherein a configuration of the SP / P CLI measurement resource set does not indicate the one or more time and frequency resources as a resource set. In some aspects, the first activation is a MAC CE, and wherein the first activation includes an ID of the SP / P CLI measurement resource set, and wherein the first activation is configured to activate the SP / P CLI measurement resource set. In some aspects, the first activation includes a list including respective QCL information mapped to each respective resource in the SP / P CLI measurement resource set. In some aspects, the first activation is a MAC CE, and wherein the first activation includes a bitmap associated with the SP / P CLI measurement resource set and is configured to activate a subset of the SP / P CLI measurement resource set, wherein each bit in the bitmap corresponds to a respective resource in the SP / P CLI measurement resource set. In some aspects, the first activation is configured to activate a subset of the SP / P CLI measurement resource set, and wherein the first activation includes: respective QCL information mapped to each respective resource in the SP / P CLI measurement resource set, or respective QCL information mapped to each respective resource in the subset of CLI SP / P CLI measurement resources. In some aspects, the first activation is configured to activate a subset of the SP / P CLI measurement resource set, and wherein the first activation includes a first list of QCL information and a second list of QCL update information, wherein each respective QCL information in the first list is mapped to a respective resource in the subset of SP / P CLI measurement resources, and wherein each respective QCL update information in the second list is mapped to a respective resource of a second active subset of the SP / P CLI measurement resource set. In some aspects, the first activation is a MAC CE, and wherein the first activation includes one or more resource IDs, wherein each respective resource ID in the resource IDs is associated with a respective resource in the set of SP / P CLI measurement resources, and wherein the first activation is configured to activate the respective resource. In some aspects, the first activation includes a list of QCL information, and wherein each respective QCL information in the list is mapped to a respective resource in the set of SP / P CLI measurement resources.

[0140] At 1505, the network entity may send a second activation. For example, the network entity 804 may send the second activation (e.g., 811). In some aspects, 1508 may be performed by the CLI component 199. In some aspects, the first activation is a first MAC CE, wherein the at least one processor is configured to: send the second activation, wherein the CLI measurement information is received based on the second activation, and wherein the second activation is a second MAC CE different from the first MAC CE.

[0141] At 1506, the network entity may receive CLI measurement information based on the SP / P CLI measurement resource set and the first activation. For example, the network entity 804 may receive CLI measurement information (e.g., 814) based on the SP / P CLI measurement resource set and the first activation. In some aspects, 1506 may be performed by the CLI component 199.

[0142] At 1508, the network entity may send a first deactivation associated with the set of SP / P CLI measurement resources. For example, the network entity 804 may send a first deactivation associated with the set of SP / P CLI measurement resources (e.g., 818). In some aspects, 1508 may be performed by the CLI component 199.

[0143] At 1510, the network entity may send a second deactivation configured to deactivate generation of second CLI measurement information based on the SP / P CLI measurement resource set. For example, the network entity 804 may send a second deactivation configured to deactivate generation of second CLI measurement information based on the SP / P CLI measurement resource set (e.g., 820). In some aspects, 1510 may be performed by the CLI component 199.

[0144] Fig.161600 is a diagram illustrating an example of a hardware implementation for an apparatus 1604. The apparatus 1604 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1604 may include a cellular baseband processor 1624 (also referred to as a modem) coupled to one or more transceivers 1622 (e.g., a cellular RF transceiver). The cellular baseband processor 1624 may include on-chip memory 1624'. In some aspects, the apparatus 1604 may also include one or more subscriber identity module (SIM) cards 1620 and an application processor 1606 coupled to a secure digital (SD) card 1608 and a screen 1610. The application processor 1606 may include on-chip memory 1606'. In some aspects, the device 1604 may also include a Bluetooth module 1612, a WLAN module 1614, a satellite system module 1616 (e.g., a GNSS module), one or more sensor modules 1618 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; a light detection and ranging (LIDAR), a radio-aided detection and ranging (RADAR), a sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1626, a power supply 1630, and / or a camera 1632. The Bluetooth module 1612, the WLAN module 1614, and the satellite system module 1616 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1624 communicates with the UE 104 and / or with a RU associated with the network entity 1602 through the transceiver 1622 via one or more antennas 1680. The cellular baseband processor 1624 and the application processor 1606 may each include a computer-readable medium / memory 1624', 1606', respectively. The additional memory module 1626 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1624', 1606', 1626 may be non-transitory. The cellular baseband processor 1624 and the application processor 1606 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1624 / application processor 1606, enables the cellular baseband processor 1624 / application processor 1606 to perform the various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1624 / application processor 1606 when executing the software. The cellular baseband processor 1624 / application processor 1606 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 1604 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1624 and / or the application processor 1606, and in another configuration, the device 1604 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 1604.

[0145] As discussed herein, the CLI component 198 may be configured to receive a configuration of a semi-persistent (SP) or periodic (P) (SP / P) CLI measurement resource set for layer 2 (L2) cross-link interference (CLI) measurement from a second network entity, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types including at least one of: a zero power sounding reference signal (ZP SRS), a channel state information (CSI) interference measurement (CSI IM) resource, a non-zero power (NZP) CSI reference signal (CSI RS), or a combination of an NZP CSI RS and a CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with a corresponding CLI report metric. In some aspects, the CLI component 198 may be further configured to receive a first activation associated with the SP / P CLI measurement resource set from the second network entity. In some aspects, the CLI component 198 may be further configured to generate CLI measurement information based on the SP / P CLI measurement resource set and the first activation. In some aspects, the CLI component 198 may be further configured to send the CLI measurement information to the second network entity. The CLI component 198 may be within the cellular baseband processor 1624, the application processor 1606, or both the cellular baseband processor 1624 and the application processor 1606. The CLI component 198 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer readable medium for implementation by one or more processors, or some combination of the above operations. As shown, the device 1604 may include a variety of components configured for various functions. In one configuration, the apparatus 1604 (and specifically, the cellular baseband processor 1624 and / or the application processor 1606) includes a component for receiving a configuration of an SP / P CLI measurement resource set for L2 CLI measurement from a second network entity, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with a corresponding CLI report metric. In some aspects, the apparatus 1604 may also include a component for receiving a first activation associated with the SP / P CLI measurement resource set from the second network entity. In some aspects, the apparatus 1604 may also include a component for generating CLI measurement information based on the SP / P CLI measurement resource set and the first activation. In some aspects, the apparatus 1604 may also include a component for sending the CLI measurement information to the second network entity.In some aspects, the apparatus 1604 may also include a component for receiving a second activation. In some aspects, the apparatus 1604 may also include a component for receiving a first deactivation associated with the SP / P CLI measurement resource set. In some aspects, the apparatus 1604 may also include a component for receiving a second deactivation configured to deactivate generation of second CLI measurement information based on the SP / P CLI measurement resource set. In some aspects, the apparatus 1604 may also include a component for applying one of the first timing configuration or the second timing configuration based on one of the following: a first less strict timing configuration in the first timing configuration or the second timing configuration, the first timing configuration, the second timing configuration, or a first more strict timing configuration in the first timing configuration or the second timing configuration. In some aspects, the apparatus 1604 may also include a component for applying one of the third timing configuration or the fourth timing configuration based on one of the following: a second less strict timing configuration in the third timing configuration or the fourth timing configuration, the third timing configuration, the fourth timing configuration, or a second more strict timing configuration in the third timing configuration or the fourth timing configuration. These components may be a CLI component 198 of the apparatus 1604 configured to perform the functions recited by the components. As described herein, the apparatus 1604 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the components may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the components.

[0146] Fig.171700 is a diagram illustrating an example of a hardware implementation for a network entity 1702. The network entity 1702 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1702 may include at least one of a CU 1710, a DU 1730, or a RU 1740. For example, depending on the layer functionality handled by the CLI component 199, the network entity 1702 may include a CU 1710; both the CU 1710 and the DU 1730; each of the CU 1710, the DU 1730, and the RU 1740; the DU 1730; both the DU 1730 and the RU 1740; or the RU 1740. The CU 1710 may include a CU processor 1712. The CU processor 1712 may include an on-chip memory 1712'. In some aspects, the CU 1710 may also include an additional memory module 1714 and a communication interface 1718. CU 1710 communicates with DU 1730 via a midhaul link, such as an F1 interface. DU 1730 may include a DU processor 1732. DU processor 1732 may include on-chip memory 1732'. In some aspects, DU 1730 may also include an additional memory module 1734 and a communication interface 1738. DU 1730 communicates with RU 1740 via a fronthaul link. RU 1740 may include a RU processor 1742. RU processor 1742 may include on-chip memory 1742'. In some aspects, RU 1740 may also include an additional memory module 1744, one or more transceivers 1746, an antenna 1780, and a communication interface 1748. RU 1740 communicates with UE 104. On-chip memory 1712', 1732', 1742' and additional memory modules 1714, 1734, 1744 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1712, 1732, 1742 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described herein. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0147] As discussed herein, the CLI component 199 may be configured to send a configuration of a SP / P CLI measurement resource set for L2 CLI measurements to a second network entity, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSIIM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with a corresponding CLI report metric. In some aspects, the CLI component 199 may be further configured to send a first activation associated with the SP / P CLI measurement resource set to the second network entity. In some aspects, the CLI component 199 may be further configured to receive CLI measurement information based on the SP / P CLI measurement resource set and the first activation. The CLI component 199 may be within one or more processors of one or more of the CU 1710, the DU 1730, and the RU 1740. The CLI component 199 may be one or more hardware components 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 operations. The network entity 1702 may include a variety of components configured for various functions. In one configuration, the network entity 1702 includes a component for sending a configuration of an SP / P CLI measurement resource set for L2 CLI measurement to a second network entity, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with a corresponding CLI report metric. In some aspects, the network entity 1702 may also include a component for sending a first activation associated with the SP / P CLI measurement resource set to the second network entity. In some aspects, the network entity 1702 may further include means for receiving CLI measurement information based on the SP / P CLI measurement resource set and the first activation. In some aspects, the network entity 1702 may further include means for sending a second activation, wherein the CLI measurement information is received based on the second activation. In some aspects, the network entity 1702 may further include means for sending a second activation, wherein the CLI measurement information is received based on the second activation, and wherein the second activation is a second MAC CE different from the first MAC CE. In some aspects, the network entity 1702 may further include means for sending a first deactivation associated with the SP / P CLI measurement resource set.In some aspects, the network entity 1702 may also include a second deactivation component for sending a second CLI measurement information configured to be deactivated based on the SP / P CLI measurement resource set. These components may be a CLI component 199 of the network entity 1702 configured to perform the functions recited by the components. As described herein, the network entity 1702 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the component may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the components.

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

[0149] 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 specifically stated, 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 specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to those 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" cannot replace the word "component". Therefore, no claim element will be interpreted as a functional component unless the element is explicitly stated using the phrase "component for..."

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

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

[0152] Aspect 1 is a first network entity for wireless communication, the first network entity comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receive a configuration of an SP / P CLI measurement resource set for L2 CLI measurement from a second network entity, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of the NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric; receive a first activation associated with the SP / P CLI measurement resource set from the second network entity; generate CLI measurement information based on the SP / P CLI measurement resource set and the first activation; and send the CLI measurement information to the second network entity.

[0153] Aspect 2 is the first network entity according to aspect 1, wherein the one or more measurement resource types are not associated with the corresponding CLI reporting metrics.

[0154] Aspect 3 is a first network entity according to any one of Aspects 1 to 2, wherein the one or more measurement resource types are associated with the at least one corresponding CLI reporting metric, wherein the ZP SRS is associated with RSRP, RSSI or SINR, wherein the NZP CSI RS is associated with the RSSI and the RSRP, wherein the CSI IM is associated with the RSSI or the RSRP, and wherein the combination is associated with the RSSI, the RSRP and the SINR.

[0155] Aspect 4 is a first network entity according to any one of Aspects 1 to 3, wherein the configuration of the SP / P CLI measurement resource set indicates one or more time and frequency resources, and wherein the configuration of the SP / P CLI measurement resource set indicates the one or more time and frequency resources as a resource set.

[0156] Aspect 5 is a first network entity according to any one of Aspects 1 to 4, wherein the first activation indication is one or more time and frequency resources associated with the SP / P CLI measurement resource set, and wherein the configuration of the SP / P CLI measurement resource set does not indicate the one or more time and frequency resources as a resource set.

[0157] Aspect 6 is a first network entity according to any one of Aspects 1 to 5, wherein the first activation is a first MAC CE, wherein the at least one processor is configured to: receive a second activation, wherein in order to send the CLI measurement information, the at least one processor is configured to send the CLI measurement information based on the second activation, and wherein the second activation is a second MAC CE different from the first MAC CE.

[0158] Aspect 7 is a first network entity according to any one of Aspects 1 to 6, wherein the first activation is a MACCE, and wherein the first activation includes an ID of the SP / P CLI measurement resource set, and wherein the first activation is configured to activate the SP / P CLI measurement resource set.

[0159] Aspect 8 is a first network entity according to any one of aspects 1 to 7, wherein the first activation comprises corresponding QCL information mapped to each corresponding resource in the SP / P CLI measurement resource set.

[0160] Aspect 9 is a first network entity according to any one of aspects 1 to 8, wherein the first activation comprises a list including the corresponding QCL information mapped to each corresponding resource in the SP / P CLI measurement resource set.

[0161] Aspect 10 is a first network entity according to any one of Aspects 1 to 6, wherein the first activation is a MACCE, and wherein the first activation includes a bitmap associated with the SP / P CLI measurement resource set and is configured to activate a subset of the SP / P CLI measurement resource set, wherein each bit in the bitmap corresponds to a corresponding resource in the SP / P CLI measurement resource set.

[0162] Aspect 11 is a first network entity according to any one of Aspects 1 to 6 and 10, wherein the first activation is configured to activate a subset of the SP / P CLI measurement resource set, and wherein the first activation includes: corresponding QCL information mapped to each corresponding resource in the SP / P CLI measurement resource set, or corresponding QCL information mapped to corresponding resources in the subset of CLI SP / P CLI measurement resources.

[0163] Aspect 12 is a first network entity according to any one of Aspects 1 to 6 and 10, wherein the first activation is configured to activate a subset of the SP / P CLI measurement resource set, and wherein the first activation includes a first list of QCL information and a second list of QCL update information, wherein each corresponding QCL information in the first list is mapped to a corresponding resource in the subset of SP / P CLI measurement resources, and wherein each corresponding QCL update information in the second list is mapped to a corresponding resource of a second active subset in the SP / P CLI measurement resource set.

[0164] Aspect 13 is a first network entity according to any one of Aspects 1 to 6, wherein the first activation is a MACCE, and wherein the first activation includes one or more resource identifiers (IDs), wherein each corresponding resource ID in the resource IDs is associated with a corresponding resource in the SP / P CLI measurement resource set, and wherein the first activation is configured to activate the corresponding resource.

[0165] Aspect 14 is a first network entity according to any one of aspects 1 to 6 and 13, wherein the first activation includes a list of QCL information, and wherein each corresponding QCL information in the list is mapped to the corresponding resource in the SP / P CLI measurement resource set.

[0166] Aspect 15 is a first network entity according to any one of Aspects 1 to 14, wherein the at least one processor is configured to: receive a second activation, wherein in order to send the CLI measurement information, the at least one processor is configured to send the CLI measurement information based on the second activation; receive a first deactivation associated with the SP / P CLI measurement resource set; and receive a second deactivation configured to deactivate the generation of second CLI measurement information based on the SP / P CLI measurement resource set.

[0167] Aspect 16 is a first network entity according to any one of aspects 1 to 15, wherein a first timing configuration associated with the first deactivation is equivalent to a second timing configuration associated with the first activation.

[0168] Aspect 17 is a first network entity according to any one of aspects 1 to 15, wherein a first timing configuration associated with the first deactivation is different from a second timing configuration associated with the first activation.

[0169] Aspect 18 is a first network entity according to any one of Aspects 1 to 17, wherein a first timing configuration is associated with the first deactivation and a second timing configuration is associated with the first activation, and wherein the second timing configuration indicates application of the first activation after one of: a first number of time slots independent of a capability associated with the first network entity, or a second number of time slots based on the capability.

[0170] Aspect 19 is the first network entity according to any one of aspects 1 to 18, wherein the second number is equal to one of the following: or wherein X is a first positive integer based on the capability, wherein Y is a second positive integer based on the capability, wherein Z is a third positive integer independent of the capability, wherein n is associated with a time slot n associated with an acknowledgement (ACK) associated with the first activation, and wherein represents the number of time slots per subframe used for the subcarrier spacing represented by μ.

[0171] Aspect 20 is a first network entity according to any one of Aspects 1 to 20, wherein a first timing configuration is associated with the first deactivation and a second timing configuration is associated with the first activation, and wherein the first timing configuration indicates application of the first deactivation after one of: a first number of time slots independent of a capability associated with the first network entity, or a second number of time slots based on the capability.

[0172] Aspect 21 is a first network entity according to any one of aspects 1 to 20, wherein the second number is equal to one of the following: or wherein X is a first positive integer based on the capability, wherein Y is a second positive integer based on the capability, wherein Z is a third positive integer independent of the capability, wherein n is associated with a time slot n associated with an acknowledgement (ACK) associated with the first deactivation, and wherein represents the number of time slots per subframe used for the subcarrier spacing represented by μ.

[0173] Aspect 22 is a first network entity according to any one of aspects 1 to 21, wherein a first timing configuration associated with the second deactivation is equivalent to a second timing configuration associated with the second activation.

[0174] Aspect 23 is a first network entity according to any one of aspects 1 to 21, wherein a first timing configuration associated with the second deactivation is different from a second timing configuration associated with the second activation.

[0175] Aspect 24 is a first network entity according to any one of Aspects 1 to 23, wherein a first timing configuration is associated with the second deactivation and a second timing configuration is associated with the second activation, and wherein the second timing configuration indicates application of the second activation after one of: a first number of time slots independent of a capability associated with the first network entity, or a second number of time slots based on the capability.

[0176] Aspect 25 is the first network entity according to any one of aspects 1 to 24, wherein the second number is equal to one of the following: or wherein X is a first positive integer based on the capability, wherein Y is a second positive integer based on the capability, wherein Z is a third positive integer independent of the capability, wherein n is associated with a time slot n associated with an acknowledgement (ACK) associated with the second activation, and wherein represents the number of time slots per subframe used for the subcarrier spacing represented by μ.

[0177] Aspect 26 is a first network entity according to any one of Aspects 1 to 25, wherein a first timing configuration is associated with the second deactivation and a second timing configuration is associated with the second activation, and wherein the first timing configuration indicates application of the second deactivation after one of: a first number of time slots independent of a capability associated with the first network entity, or a second number of time slots based on the capability.

[0178] Aspect 27 is a first network entity according to any one of aspects 1 to 24, wherein the second number is equal to one of the following: or wherein X is a first positive integer based on the capability, wherein Y is a second positive integer based on the capability, wherein Z is a third positive integer independent of the capability, wherein n is associated with a time slot n associated with an acknowledgement (ACK) associated with the second deactivation, and wherein represents the number of time slots per subframe used for the subcarrier spacing represented by μ.

[0179] Aspect 28 is a first network entity according to any one of aspects 1 to 27, wherein a timing configuration is associated with the second activation, and wherein at least one resource that is earlier in time than the application of the second activation based on the timing configuration is included in the measurement set or excluded from the measurement set.

[0180] Aspect 29 is a first network entity according to any one of Aspects 1 to 28, wherein a timing configuration is associated with the second deactivation, and wherein at least one resource that is earlier in time than the application of the second deactivation based on the timing configuration is included in the measurement set or excluded from the measurement set.

[0181] Aspect 30 is a first network entity according to any one of aspects 1 to 29, wherein the joint activation in the first MAC CE includes the first activation and the second activation, and wherein the joint deactivation in the second MAC CE includes the first deactivation and the second deactivation, wherein a first timing configuration is associated with the first activation, a second timing configuration is associated with the second activation, a third timing configuration is associated with the first deactivation, and a fourth timing configuration is associated with the second deactivation.

[0182] Aspect 31 is a first network entity according to any one of aspects 1 to 30, wherein the first timing configuration is equivalent to the second timing configuration, and wherein the third timing configuration is equivalent to the fourth timing configuration.

[0183] Aspect 32 is a first network entity according to any one of Aspects 1 to 31, wherein the at least one processor is configured to: apply one of the first timing configuration or the second timing configuration based on one of the following: a first less strict timing configuration in the first timing configuration or the second timing configuration, the first timing configuration, the second timing configuration, or a first more strict timing configuration in the first timing configuration or the second timing configuration; and apply one of the third timing configuration or the fourth timing configuration based on one of the following: a second less strict timing configuration in the third timing configuration or the fourth timing configuration, the third timing configuration, the fourth timing configuration, or a second more strict timing configuration in the third timing configuration or the fourth timing configuration.

[0184] Aspect 33 is a first network entity according to any one of aspects 1 to 32, wherein the configuration is active when a downlink BWP associated with the configuration is active.

[0185] Aspect 34 is a first network entity according to any one of aspects 1 to 33, wherein the configuration is inactive when a carrier associated with the configuration is deactivated.

[0186] Aspect 35 is the first network entity according to any one of aspects 1 to 34, wherein the configuration is inactive when a BWP associated with the configuration is deactivated.

[0187] Aspect 36 is a first network entity for wireless communication, the first network entity comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: send a configuration of an SP / P CLI measurement resource set for L2 CLI measurement to a second network entity, wherein the SP / P CLI measurement resource set is associated with one or more measurement resource types including at least one of the following: ZP SRS, CSI IM resources, NZP CSI RS, or a combination of the NZP CSI RS and CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric; send a first activation associated with the SP / P CLI measurement resource set to the second network entity; and receive CLI measurement information based on the SP / P CLI measurement resource set and the first activation.

[0188] Aspect 37 is the first network entity according to aspect 36, wherein the one or more measurement resource types are not associated with the corresponding CLI reporting metrics.

[0189] Aspect 38 is a first network entity according to any one of Aspects 36 to 37, wherein the one or more measurement resource types are associated with the at least one corresponding CLI reporting metric, wherein the ZP SRS is associated with RSRP, RSSI or SINR, wherein the NZP CSI RS is associated with the RSSI and the RSRP, wherein the CSI IM is associated with the RSSI or the RSRP, and wherein the combination is associated with the RSSI, the RSRP and the SINR.

[0190] Aspect 39 is a first network entity according to any one of Aspects 36 to 38, wherein the configuration of the SP / P CLI measurement resource set indicates one or more time and frequency resources, and wherein the configuration of the SP / P CLI measurement resource set indicates the one or more time and frequency resources as a resource set.

[0191] Aspect 40 is a first network entity according to any one of Aspects 36 to 39, wherein the first activation indicates one or more time and frequency resources associated with the SP / P CLI measurement resource set, and wherein the configuration of the SP / P CLI measurement resource set does not indicate the one or more time and frequency resources as a resource set.

[0192] Aspect 41 is a first network entity according to any one of aspects 36 to 40, wherein the first activation is a first MAC CE, wherein the at least one processor is configured to: send a second activation, wherein the CLI measurement information is received based on the second activation, and wherein the second activation is a second MAC CE different from the first MAC CE.

[0193] Aspect 42 is a first network entity according to any one of aspects 36 to 41, wherein the first activation is a MAC CE, and wherein the first activation includes an ID of the SP / P CLI measurement resource set, and wherein the first activation is configured to activate the SP / P CLI measurement resource set.

[0194] Aspect 43 is a first network entity according to any one of aspects 36 to 42, wherein the first activation comprises respective QCL information mapped to each respective resource in the set of SP / P CLI measurement resources.

[0195] Aspect 44 is a first network entity according to any one of aspects 36 to 43, wherein the first activation comprises a list including the respective QCL information mapped to each respective resource in the set of SP / P CLI measurement resources.

[0196] Aspect 45 is a first network entity according to any one of Aspects 36 to 41, wherein the first activation is a MAC CE, and wherein the first activation includes a bitmap associated with the SP / P CLI measurement resource set and is configured to activate a subset of the SP / P CLI measurement resource set, wherein each bit in the bitmap corresponds to a corresponding resource in the SP / P CLI measurement resource set.

[0197] Aspect 46 is a first network entity according to any one of Aspects 36 to 41 and 45, wherein the first activation is configured to activate a subset of the SP / P CLI measurement resource set, and wherein the first activation includes: corresponding QCL information mapped to each corresponding resource in the SP / P CLI measurement resource set, or corresponding QCL information mapped to each corresponding resource in the subset of the CLI SP / P CLI measurement resources.

[0198] Aspect 47 is a first network entity according to any one of Aspects 36 to 41 and 45, wherein the first activation is configured to activate a subset of the SP / P CLI measurement resource set, and wherein the first activation includes a first list of QCL information and a second list of QCL update information, wherein each corresponding QCL information in the first list is mapped to a corresponding resource in the subset of SP / P CLI measurement resources, and wherein each corresponding QCL update information in the second list is mapped to a corresponding resource of a second active subset in the SP / P CLI measurement resource set.

[0199] Aspect 48 is a first network entity according to any one of Aspects 36 to 41, wherein the first activation is a MAC CE, and wherein the first activation includes one or more resource identifiers (IDs), wherein each corresponding resource ID of the resource IDs is associated with a corresponding resource in the SP / P CLI measurement resource set, and wherein the first activation is configured to activate the corresponding resource.

[0200] Aspect 49 is a first network entity according to any one of aspects 36 to 41 and 48, wherein the first activation comprises a list of QCL information, and wherein each corresponding QCL information in the list is mapped to the corresponding resource in the SP / P CLI measurement resource set.

[0201] Aspect 50 is a first network entity according to any one of Aspects 36 to 49, wherein the at least one processor is configured to: send a second activation, wherein the CLI measurement information is received based on the second activation; send a first deactivation associated with the SP / P CLI measurement resource set; and send a second deactivation configured to deactivate second CLI measurement information based on the SP / P CLI measurement resource set.

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

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

[0204] Aspect 53 is a 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 35.

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

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

[0207] Aspect 56 is a computer readable medium storing computer executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 36 to 50.

Claims

1. A first network entity for wireless communication, the first network entity comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving, from a second network entity, a configuration of a set of semi-persistent (SP) or periodic (P) (SP / P) CLI measurement resources for layer 2 (L2) cross-link interference (CLI) measurements, wherein the set of SP / P CLI measurement resources is associated with one or more measurement resource types including at least one of: a zero power sounding reference signal (ZP SRS), a channel state information (CSI) interference measurement (CSI IM) resource, a non-zero power (NZP) CSI reference signal (CSI RS), or a combination of the NZP CSI RS and the CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric; receiving, from the second network entity, a first activation associated with the set of SP / P CLI measurement resources; generating CLI measurement information based on the SP / P CLI measurement resource set and the first activation; as well as Sending the CLI measurement information to the second network entity.

2. The first network entity of claim 1, wherein the one or more measurement resource types are not associated with the corresponding CLI reporting metrics.

3. The first network entity of claim 1 , wherein the one or more measurement resource types are associated with the at least one corresponding CLI reporting metric, wherein the ZP SRS is associated with a reference signal received power (RSRP), a received signal strength indicator (RSSI), or a signal to interference plus noise ratio (SINR), wherein the NZP CSI RS is associated with the RSSI and the RSRP, wherein the CSI IM is associated with the RSSI or the RSRP, and wherein the combination is associated with the RSSI, the RSRP, and the SINR.

4. The first network entity of claim 1 , wherein the configuration of the SP / P CLI measurement resource set indicates one or more time and frequency resources, and wherein the configuration of the SP / P CLI measurement resource set indicates the one or more time and frequency resources as a resource set.

5. The first network entity of claim 1 , wherein the first activation indicates one or more time and frequency resources associated with the SP / P CLI measurement resource set, and wherein the configuration of the SP / P CLI measurement resource set does not indicate the one or more time and frequency resources as a resource set.

6. The first network entity of claim 1 , wherein the first activation is a first medium access control (MAC) control element (MAC CE), wherein the at least one processor is configured to: A second activation is received, wherein to send the CLI measurement information, the at least one processor is configured to send the CLI measurement information based on the second activation, and wherein the second activation is a second MAC CE different from the first MAC CE.

7. The first network entity of claim 1 , wherein the first activation is a medium access control (MAC) control element (MAC CE), and wherein the first activation includes an identifier (ID) of the SP / P CLI measurement resource set, and wherein the first activation is configured to activate the SP / P CLI measurement resource set.

8. The first network entity of claim 7, wherein the first activation comprises corresponding quasi-co-location (QCL) information mapped to each corresponding resource of the SP / P CLI measurement resource set.

9. The first network entity of claim 8, wherein the first activation comprises a list comprising the corresponding QCL information mapped to each corresponding resource in the set of SP / P CLI measurement resources.

10. The first network entity of claim 1 , wherein the first activation is a medium access control (MAC) control element (MAC CE), and wherein the first activation comprises a bitmap associated with the SP / P CLI measurement resource set and is configured to activate a subset of the SP / P CLI measurement resource set, wherein each bit in the bitmap corresponds to a respective resource in the SP / P CLI measurement resource set.

11. The first network entity of claim 1 , wherein the first activation is configured to activate a subset of the set of SP / PCLI measurement resources, and wherein the first activation comprises: The corresponding quasi-co-location (QCL) information mapped to each corresponding resource in the set of SP / P CLI measurement resources, or the corresponding QCL information mapped to each corresponding resource in the subset of CLI SP / P CLI measurement resources.

12. A first network entity according to claim 1, wherein the first activation is configured to activate a subset of the SP / PCLI measurement resource set, and wherein the first activation includes a first list of quasi-co-site (QCL) information and a second list of QCL update information, wherein each corresponding QCL information in the first list is mapped to a corresponding resource in the subset of SP / P CLI measurement resources, and wherein each corresponding QCL update information in the second list is mapped to a corresponding resource of a second active subset in the SP / PCLI measurement resource set.

13. The first network entity of claim 1 , wherein the first activation is a medium access control (MAC) control element (MAC CE), and wherein the first activation comprises one or more resource identifiers (IDs), wherein each respective one of the resource IDs is associated with a respective resource in the SP / P CLI measurement resource set, and wherein the first activation is configured to activate the respective resource.

14. The first network entity of claim 13, wherein the first activation comprises a list of quasi co-location (QCL) information, and wherein each corresponding QCL information in the list is mapped to the corresponding resource in the SP / P CLI measurement resource set.

15. The first network entity of claim 1 , wherein the at least one processor is configured to: receiving a second activation, wherein to send the CLI measurement information, the at least one processor is configured to send the CLI measurement information based on the second activation; receiving a first deactivation associated with the set of SP / P CLI measurement resources; as well as A second deactivation configured to deactivate generation of second CLI measurement information based on the set of SP / P CLI measurement resources is received.

16. The first network entity of claim 15, wherein a first timing configuration associated with the first deactivation is equivalent to a second timing configuration associated with the first activation.

17. The first network entity of claim 15, wherein a first timing configuration associated with the first deactivation is different from a second timing configuration associated with the first activation.

18. The first network entity of claim 15, wherein a first timing configuration is associated with the first deactivation and a second timing configuration is associated with the first activation, and wherein the second timing configuration indicates application of the first activation after one of: a first number of time slots independent of capabilities associated with said first network entity, or A second number of time slots based on the capability.

19. The first network entity of claim 18, wherein the second number is equal to one of: or wherein X is a first positive integer based on the capability, wherein Y is a second positive integer based on the capability, wherein Z is a third positive integer independent of the capability, wherein n is associated with a time slot n associated with an acknowledgement (ACK) associated with the first activation, and wherein represents the number of time slots per subframe used for the subcarrier spacing represented by μ.

20. The first network entity of claim 15, wherein a first timing configuration is associated with the first deactivation and a second timing configuration is associated with the first activation, and wherein the first timing configuration indicates application of the first deactivation after one of: a first number of time slots independent of capabilities associated with said first network entity, or A second number of time slots based on the capability.

21. The first network entity of claim 20, wherein the second number is equal to one of: or wherein X is a first positive integer based on the capability, wherein Y is a second positive integer based on the capability, wherein Z is a third positive integer independent of the capability, wherein n is associated with a time slot n associated with an acknowledgement (ACK) associated with the first deactivation, and wherein represents the number of time slots per subframe used for the subcarrier spacing represented by μ.

22. The first network entity of claim 15, wherein a first timing configuration associated with the second deactivation is equivalent to a second timing configuration associated with the second activation.

23. The first network entity of claim 15, wherein a first timing configuration associated with the second deactivation is different than a second timing configuration associated with the second activation.

24. The first network entity of claim 15, wherein a first timing configuration is associated with the second deactivation and a second timing configuration is associated with the second activation, and wherein the second timing configuration indicates application of the second activation after one of: a first number of time slots independent of capabilities associated with said first network entity, or A second number of time slots based on the capability.

25. The first network entity of claim 24, wherein the second number is equal to one of: or wherein X is a first positive integer based on the capability, wherein Y is a second positive integer based on the capability, wherein Z is a third positive integer independent of the capability, wherein n is associated with a time slot n associated with an acknowledgement (ACK) associated with the second activation, and wherein represents the number of time slots per subframe used for the subcarrier spacing represented by μ.

26. The first network entity of claim 15, wherein a first timing configuration is associated with the second deactivation and a second timing configuration is associated with the second activation, and wherein the first timing configuration indicates application of the second deactivation after one of: a first number of time slots independent of capabilities associated with said first network entity, or A second number of time slots based on the capability.

27. The first network entity of claim 24, wherein the second number is equal to one of: or wherein X is a first positive integer based on the capability, wherein Y is a second positive integer based on the capability, wherein Z is a third positive integer independent of the capability, wherein n is associated with a time slot n associated with an acknowledgement (ACK) associated with the second deactivation, and wherein represents the number of time slots per subframe used for the subcarrier spacing represented by μ.

28. The first network entity of claim 15, wherein a timing configuration is associated with the second activation, and wherein at least one resource that is earlier in time than application of the second activation based on the timing configuration is included in or excluded from the measurement set.

29. The first network entity of claim 15, wherein a timing configuration is associated with the second deactivation, and wherein at least one resource that is earlier in time than application of the second deactivation based on the timing configuration is included in the measurement set or excluded from the measurement set.

30. The first network entity of claim 15, wherein a joint activation in a first medium access control (MAC) control element (MACCE) comprises the first activation and the second activation, and wherein a joint deactivation in a second MAC CE comprises the first deactivation and the second deactivation, wherein a first timing configuration is associated with the first activation, a second timing configuration is associated with the second activation, a third timing configuration is associated with the first deactivation, and a fourth timing configuration is associated with the second deactivation.

31. The first network entity of claim 30, wherein the first timing configuration is equivalent to the second timing configuration, and wherein the third timing configuration is equivalent to the fourth timing configuration.

32. The first network entity of claim 30, wherein the at least one processor is configured to: Applying one of the first timing configuration or the second timing configuration based on one of: a first less strict timing configuration of the first timing configuration or the second timing configuration, the first timing configuration, the second timing configuration, or a first more strict timing configuration of the first timing configuration or the second timing configuration; and One of the third timing configuration or the fourth timing configuration is applied based on one of: a second less strict timing configuration of the third timing configuration or the fourth timing configuration, the third timing configuration, the fourth timing configuration, or a second more strict timing configuration of the third timing configuration or the fourth timing configuration.

33. The first network entity of claim 1, wherein the configuration is active when a downlink bandwidth part (BWP) associated with the configuration is active.

34. The first network entity of claim 1, wherein the configuration is inactive when a carrier associated with the configuration is deactivated.

35. The first network entity of claim 1, wherein the configuration is inactive when a bandwidth part (BWP) associated with the configuration is deactivated.

36. A method for wireless communication at a first network entity, the method comprising: receiving, from a second network entity, a configuration of a set of semi-persistent (SP) or periodic (P) (SP / P) CLI measurement resources for layer 2 (L2) cross-link interference (CLI) measurements, wherein the set of SP / P CLI measurement resources is associated with one or more measurement resource types including at least one of: a zero power sounding reference signal (ZP SRS), a channel state information (CSI) interference measurement (CSI IM) resource, a non-zero power (NZP) CSI reference signal (CSI RS), or a combination of the NZP CSI RS and the CSI IM, wherein the one or more measurement resource types are associated with at least one corresponding CLI report metric or are not associated with the corresponding CLI report metric; receiving, from the second network entity, a first activation associated with the set of SP / P CLI measurement resources; generating CLI measurement information based on the SP / P CLI measurement resource set and the first activation; as well as Sending the CLI measurement information to the second network entity.

Images