L1 initiation and adaptation of L2 CLI reports

Abstract

A method for wireless communication at a UE is disclosed herein. The method includes receiving a DCI for initiating a MAC-CE CLI report. The method also includes transmitting one or more MAC-CE CLI reports based on the DCI.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 816,289, filed on July 29, 2022, entitled “L1 ACTIVATION AND ADAPTATION OF L2 CLI 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 interference measurement reporting by a user equipment (UE). Background Art

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

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, 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). Certain 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] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not a comprehensive review of all contemplated aspects. This summary is neither intended to identify the 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 for wireless communication at a user equipment (UE) are provided. The apparatus is configured to: receive downlink control information (DCI) for initiating a medium access control element (MAC-CE) cross-link interference (CLI) report; and send one or more MAC-CE CLI reports based on the DCI.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus for wireless communication at a network node are provided. The apparatus is configured to: send downlink control information (DCI) for initiating a medium access control element (MAC-CE) cross-link interference (CLI) report; and receive one or more MAC-CE CLI reports based on the DCI.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features described in full 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 are only indicative of 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 UE in an access network.

[0016] Figure 4A , Figure 4B and Figure 4C An example diagram illustrating full-duplex wireless communication.

[0017] Figure 5Examples of in-band full-duplex (IBFD) resources and sub-band frequency division duplex (FDD) resources for full-duplex communication are illustrated.

[0018] Figure 6 An example set of time and frequency resources including both half-duplex periods and full-duplex periods is illustrated.

[0019] Figure 7 A diagram depicting examples of different types of interference is illustrated.

[0020] Figure 8 is a diagram illustrating an example of downlink control information (DCI) associated with an aperiodic (AP) channel state information (CSI) report.

[0021] Fig. 9 is a diagram illustrating an example of DCI associated with semi-persistent (SP) CSI reporting.

[0022] Fig.10 is a diagram illustrating an example of a Medium Access Control Element (MAC-CE) associated with SP CSI reporting.

[0023] Fig.11 is a diagram illustrating an example of selection of an AP trigger state for AP cross-link interference (CLI) reporting.

[0024] Fig.12 A diagram including an example of applying the timing of parameter updates for CLI reporting.

[0025] Fig.13 is a diagram depicting a timeline of joint initiation of CLI measurement resources and L2 CLI reporting.

[0026] Fig.14 It is a communication flow chart between UE and base station.

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

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

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

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

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

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

[0033] When a first UE (e.g., an interfered UE) sends and receives data on the same frequency band, the first UE may experience CLI from a second UE (e.g., an interfering UE). CLI may affect the reliability of communication at the first UE. Various aspects presented herein provide efficient triggering of CLI reports by UEs so that base stations and / or UEs can adjust send / receive parameters to mitigate the impact of CLI. In order to provide such efficiency, layer 1 (L1) (e.g., DCI-based) activation and deactivation of CLI reports based on layer 2 (L2) (MAC-CE) are disclosed herein. In an example, a UE receives a DCI for initiating a MAC-CE CLI report. The UE sends one or more MAC-CE CLI reports based on the DCI. Compared to the initiation of a MAC-CE CLI report by L2 signaling, when the MAC-CE CLI report is triggered by a DCI, the initiation of the MAC-CE CLI report may be faster. Since the UE may be able to send a MAC-CE CLI report to a base station more quickly via the activation of a MAC-CE CLI report by a DCI, the base station and / or UE may be able to adjust the send / receive parameters more quickly to mitigate the impact of CLI.

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

[0035] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements 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.

[0036] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic piece, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions or any combination thereof.

[0037] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. 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.

[0038] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, 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) equipment or systems in conjunction with one or more technologies herein. In some practical environments, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0039] The deployment of a communication system (such as a 5G NR system) may be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)), or one or more units (or one or more components) that perform base station functionality may 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 (e.g., a gNB), a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) may be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

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

[0041] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. 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.

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

[0043] 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 interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive signals from one or more of the other units or to transmit signals to one or more of the other units on a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or transmit signals to one or more of the other units on a wireless transmission medium.

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

[0045] 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) coding and decoding, scrambling, modulation, demodulation, etc.) at least in part according to a functional split such as 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.

[0046] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane communications 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).

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

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

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

[0050] 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 or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. 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).

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

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

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

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

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

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

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

[0058] 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 processes 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 processing, 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 positioning 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 positioning of the UE 104. The NG-RAN may determine the positioning of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, positioning estimates, 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.

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

[0060] Reference again Figure 1 In some aspects, the UE 104 may include an L2 CLI reporting component 198 configured to receive a DCI for initiating a MAC-CE CLI report and to send one or more MAC-CE CLI reports based on the DCI. In some aspects, the base station 102 may include a report receiving component 199 configured to send a DCI for initiating a MAC-CE CLI report and to receive one or more MAC-CE CLI reports based on the DCI. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

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

[0062] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (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 conventional or extended. For conventional CPs, each time slot may include 14 symbols, and for extended CPs, each time slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0063]

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

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

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

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

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

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

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

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

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

[0073] 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 channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

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

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

[0076] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent 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 corresponding transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

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

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

[0079] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The L2 CLI reporting component 198 combines various aspects.

[0080] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The report receiving component 199 combines various aspects.

[0081] FIG. 4A to FIG. 4C Various modes of full-duplex communication are illustrated. Full-duplex communication supports sending and receiving information in a time-overlapping manner on the same frequency band. In this way, spectral efficiency can be improved relative to that of half-duplex communication, which supports sending or receiving information in one direction at a time without overlapping uplink and downlink communications. Due to the simultaneous Tx / Rx nature of full-duplex communication, a UE or base station may experience self-interference caused by signal leakage from its local transmitter to its local receiver. In addition, a UE or base station may also experience interference from other devices, such as transmission (sometimes referred to as CLI) from a second UE or a second base station. Such interference (e.g., self-interference or interference caused by other devices) may affect communication quality, or even cause information loss.

[0082] Figure 4A A first example 400 of full-duplex communication is shown, where a first base station 402a is in full-duplex communication with a first UE 404a and a second UE 406a. The first UE 404a and the second UE 406a may be configured for half-duplex communication or full-duplex communication. Figure 4A A first UE 404a performing downlink reception and a second UE 406a performing uplink transmission are illustrated. The second UE 406a may send a first uplink signal to the first base station 402a and other base stations (such as a second base station 408a adjacent to the second UE 406a). The first base station 402a sends a downlink signal to the first UE 404a concurrently (e.g., overlapping at least partially in time) with receiving an uplink signal from the second UE 406a. The first base station 402a may experience self-interference at the receiving antenna where it is receiving an uplink signal from the second UE 406a, which is caused by receiving at least part of the downlink signal sent to the first UE 404a. The first base station 402a may experience additional interference (e.g., CLI) caused by a signal from the second base station 408a. Interference may also occur at the first UE 404a (e.g., CLI) based on a signal from the second base station 408a and an uplink signal from the second UE 406a.

[0083] Figure 4B A second example 410 of full-duplex communication is shown, in which a first base station 402b is in full-duplex communication with a first UE 404b. In this example, the first UE 404b also operates in full-duplex mode. The first base station 402b and the first UE 404b receive and transmit communications that overlap in time and are located in the same frequency band. The base station and the UE can each experience self-interference because the signal transmitted from the device leaks to a receiver at the same device (e.g., received by the receiver). The first UE 404b can experience additional interference (e.g., CLI) based on one or more signals transmitted from the second UE 406b and / or the second base station 408b adjacent to the first UE 404b.

[0084] Figure 4C A third example 420 of full-duplex communication is shown, where a first UE 404c sends and receives full-duplex communications with a first base station 402c and a second base station 408c. The first base station 402c and the second base station 408c may be used as multiple transmit receive points (multiple TRPs) for UL and DL communications with the first UE 404c. The second base station 408c may also exchange communications with a second UE 406c. Figure 4C In the embodiment of the present invention, the first UE 404c may send an uplink signal to the first base station 402c, which overlaps in time with receiving a downlink signal from the second base station 408c. As a result of receiving at least part of the first signal while receiving the second signal, the first UE 404c may experience self-interference, for example, when the UE is trying to receive a signal from the second base station 408c, the uplink signal of the UE going to the first base station 402c may leak to the receiver of the UE (e.g., be received by the receiver). The first UE 404c may experience additional interference (e.g., CLI) from the second UE 406c.

[0085] Full-duplex communications may be in the same frequency band. Uplink and downlink communications may be in different frequency sub-bands, in the same frequency sub-band, or in partially overlapping frequency sub-bands. Figure 5 A first example 500 and a second example 510 of an in-band full-duplex (IBFD) resource and a third example 520 of a sub-band full-duplex resource are illustrated. In IBFD, signals may be sent and received in overlapping times and overlapping frequencies. As shown in the first example 500, the time and frequency allocation of the transmit resource 502 may completely overlap with the time and frequency allocation of the receive resource 504. In the second example 510, the time and frequency allocation of the transmit resource 512 may partially overlap with the time and frequency allocation of the receive resource 514.

[0086] IBFD is in contrast to sub-band FDD, where transmit and receive resources can overlap in time using different frequencies, as shown in the third example 520. In the third example 520, UL, transmit resources 522 are separated from receive resources 524 by a guard band 526. The guard band can be a frequency resource or a gap in a frequency resource provided between the transmit resources 522 and the receive resources 524. Using a guard band to separate the transmit frequency resources from the receive frequency resources can help reduce self-interference. Transmit resources and receive resources that are immediately adjacent to each other can be considered to have a guard bandwidth of 0. Since the output signal from the wireless device can extend beyond the transmit resource, the guard band can reduce the interference experienced by the wireless device. Sub-band FDD can also be referred to as "flexible duplexing".

[0087] If full-duplex operation is used for a UE or a device implementing UE functionality, the transmit resources 502, 512, and 522 may correspond to uplink resources, and the receive resources 504, 514, and 524 may correspond to downlink resources. Alternatively, if full-duplex operation is used for a base station or a device implementing base station functionality, the transmit resources 502, 512, and 522 may correspond to downlink resources, and the receive resources 504, 514, and 524 may correspond to uplink resources.

[0088] Figure 6 An example device 602 is illustrated that includes a separate panel (e.g., antenna panel) for simultaneous transmission and reception in full-duplex operation. For example, device 602 is illustrated as including panel #1 and panel #2. In some examples, panel #1 can be used for downlink transmission. Downlink transmission can be at both edges of the frequency band, such as illustrated in 600 and 610. Panel #2 can be used for uplink reception, such as using frequency resources within the frequency band (such as in the middle of the frequency band). Such as in combination with Figure 5 The described sub-band full-duplex operation can be associated with an isolation of greater than 40 dB. Figure 5 As shown, the downlink resources and the uplink resources may be located in different parts of a frequency band, with a guard band between the uplink and downlink parts of the frequency band. Figure 6An example set of time and frequency resources 600 including both half-duplex periods and full-duplex periods is illustrated. For example, time period 620 includes half-duplex resources for downlink data, e.g., both panel #1 and panel #2 can receive downlink data during time period 620. Time period 620 includes sub-band full-duplex resources for uplink transmission (e.g., PUSCH) and downlink reception (e.g., downlink data), e.g., during time period 630, panel #1 can receive downlink data and panel #2 can transmit PUSCH. Time period 640 includes half-duplex resources for uplink data, e.g., both panel #1 and panel #2 can transmit PUSCH during time period 640. Figure 6 Also included is a graph 610 showing signal power versus frequency, which illustrates leakage of uplink and downlink signals outside of the frequency range provided in the sub-band full-duplex resources of time period 630 .

[0089] When a time slot has a frequency band for both uplink transmission and downlink transmission, the time slot format may be referred to as a "D+U" time slot. Downlink transmission and uplink transmission may occur in overlapping frequency resources (e.g., in-band full-duplex resources), or may occur in adjacent or slightly separated frequency resources (e.g., sub-band full-duplex resources), such as Figure 5 As shown. In a particular D+U symbol, a half-duplex device can transmit in the uplink frequency band or receive in the downlink frequency band. In a particular D+U symbol, a full-duplex device can transmit in the uplink frequency band and receive in the downlink frequency band (e.g., in the same symbol or in the same time slot). A D+U time slot can include downlink-only symbols, uplink-only symbols, and full-duplex symbols. For example, in Figure 6 In the embodiment, time period 620 may extend for one or more symbols (e.g., only downlink symbols), time period 640 may extend for one or more symbols (e.g., only uplink symbols), and time period 630 may extend for one or more symbols (e.g., full-duplex symbols or D+U symbols).

[0090] Figure 7Included are a first diagram 702 and a second diagram 704 illustrating examples of different interference sources for a UE. In the first diagram 702, a first UE 706A may be receiving a DL transmission from a first base station 708A associated with a first cell 710A. The first UE 706A may be operating in a half-duplex mode. The first base station 708A may be operating in a full-duplex mode (e.g., SBFD / IBFD). Therefore, the first base station 708A may be receiving UL transmissions from a second UE 712A on overlapping time resources (or on the same frequency resources) and sending DL transmissions to the first UE 706A. For example, the first base station 708A may simultaneously send DL communications and receive UL communications. The first UE 706A may experience inter-cell interference from a second base station 714A associated with another cell. The first UE 706A may also experience intra-cell CLI from the second UE 712A. The first UE 706A may be referred to as an "interfered UE", and the second UE 712A may be referred to as an "interfering UE". If the first UE 706A is operating in full-duplex mode, the first UE 706A may experience self-interference (SI).

[0091] In the second diagram 704, the communication may be based on dynamic TDD. The first UE 706B may be receiving DL transmissions from a first base station 708B associated with a first cell 710B. The first UE 706B may be operating in half-duplex mode. The first base station 708B may be operating in full-duplex mode (e.g., SBFD / IBFD). The second UE 712B may be sending UL transmissions to a second base station 714B associated with a second cell 716B, which may be adjacent to the first cell 710B. The first UE 706B may experience inter-cell CLI from the second UE 712B. The first UE 706B may be referred to as an "interfered UE", while the second UE 712B may be referred to as an "interfering UE". If the first UE 706A is operating in full-duplex mode, the first UE 706B may experience SI.

[0092] Some UL business models may have a periodic pattern. Therefore, the interfered UE may experience CLI or SI with a periodic pattern. The base station may configure the interfered UE to report CLI (also known as layer 2 (L2) reporting) via UL MAC-CE in order to reduce reporting overhead and obtain accurate semi-static interference measurements. Compared with layer 3 (L3) reporting, L2 reporting can be faster and more dynamic. The base station may configure semi-persistent measurement resources for CLI / SI measurements. For example, the base station may configure the interfering UE with a semi-persistent (e.g., periodic) SRS resource set. The base station may activate / deactivate semi-persistent SRS via MAC-CE and may indicate a predefined Tx power (e.g., maximum power P_cmax). The base station may configure the interfered UE with semi-persistent channel state information interference measurement (CSI-IM) resources. The base station may activate / deactivate semi-persistent CSI-IM resources via MAC-CE.

[0093] The base station may also configure L2 event-based CLI / SI reporting, where the interfered UE reports one or more CLI values ​​via MAC-CE based on the triggering event. The base station may define the CLI triggering event and the CLI reports the MAC-CE content of the interfered UE. The base station may jointly utilize MAC-CE to trigger CSI-IM and CLI reporting. The interfered UE may measure CLI based on Tx power and coupling loss (CL). If the coupling loss is known, the UE may estimate CLI for different Tx powers.

[0094] The base station may trigger CSI reporting by the UE in different ways. In one example, the base station may send DCI on PUSCH to the UE, which triggers AP CSI reporting by the UE. In another example, the base station may send DCI on PUSCH to the UE, which triggers semi-persistent CSI reporting by the UE. In yet another example, the base station may send MAC-CE on PUCCH to the UE, which triggers semi-persistent CSI reporting by the UE.

[0095] Figure 8800 is an example of an example of triggering a non-periodic CSI report based on DCI. The base station may send a DCI 802 (e.g., such as "DCI format 0_1") to the UE on the PUSCH, which triggers the UE to send an aperiodic CSI report to the base station. The DCI 802 may include a CSI request field 804, which indicates whether the DCI includes a request for a CSI report. The CSI request field 804 may be configured with a bit set for providing an indication. As an example, the CSI request field may be between zero and six bits wide. If the CSI request field 804 includes all zero bits (e.g., the CSI request field 804 includes "000000"), the DCI 802 may not request a CSI report, and the DCI 802 may schedule a PUSCH transmission containing UL data.

[0096] If the CSI request field 804 includes non-zero bits, the CSI request field 804 may point to a code point from the set of active DCI code points 806A. In an example, the CSI request field 804 may point to DCI code point n 807. As an example, when the CSI request field 804 is six bits wide, the active DCI code points 806A may include 64 code points (e.g., Sc=2 6 =64). The active DCI code point 806A, together with the inactive DCI code point 806B, belongs to a configured set of DCI code points 806. The configured set of DCI code points 806 may include up to one hundred and twenty-eight DCI code points. The configured set of DCI code points 806 may be configured for the UE in the RRC configuration. The UE may receive a MAC-CE message that provides a sub-selection to indicate active DCI code points 806A and / or inactive DCI code points 806B from a set of RRC configured DCI code points. As an example, from a larger RRC configured set of 128 code points, a subset of up to 64 code points may be initiated. The DCI 802 may be associated with a cell radio network temporary identifier (C-RNTI). For example, the base station may utilize the C-RNTI to scramble a cyclic redundancy check (CRC) of the DCI 802. The UE may interpret the DCI (eg, DCI 802 ) differently depending on the type of radio network temporary identifier (RNTI) used to scramble the DCI.

[0097] DCI code point n 807 (or another DCI code point in active DCI code point 806A) may point to a non-periodic trigger state 808 in the non-periodic trigger state 810 configured by RRC communication. The non-periodic trigger state 808 may be defined as a list of non-periodic CSI report settings identified by one or more CSI report setting identifiers (IDs) 812A to 812B. The non-periodic trigger state 808 may include up to sixteen non-periodic CSI report settings, and thus, the non-periodic trigger state 808 may trigger up to sixteen CSI reports. For each CSI report setting ID in CSI report setting IDs 812A to 812B, the UE may calculate the CSI and include the calculated CSI in the scheduled PUSCH transmission to the base station.

[0098] The DCI 802 may also include other fields 814. The other fields 814 may include an identifier for the DCI format, a carrier indicator, a UL / shared uplink (SUL) indicator, a bandwidth part indicator, a frequency domain resource assignment, a time domain resource assignment, a frequency hopping flag, a modulation and coding scheme, a new data indicator, a redundancy version, a HARQ process number, a first DL assignment index, a second DL assignment index, a transmit power control (TPC) command for a scheduled PUSCH, an SRS resource indicator, precoding information and number of layers, an antenna port, an SRS request, code block group (CBG) transmission information, a phase tracking reference signal (PTRS) DM-RS association, a beta offset indicator, a DM-RS sequence initialization, and / or a UL shared channel (UL-SCH) indicator.

[0099] Fig. 9 900 is a diagram illustrating an example of DCI-based SP CSI report triggering. The base station may send DCI 902 (e.g., "DCI format 0_1") to the UE on the PUSCH, which triggers the UE to send a semi-persistent CSI report to the base station. The DCI 902 may include a CSI request field 904. The CSI request field 904 may be configured to be between zero and six bits wide.

[0100] If the CSI request field 904 includes non-zero bits, the CSI request field 904 may point to a code point in the DCI code points 906. In an example, the CSI request field 904 may point to the DCI code point n 907. When the CSI request field 904 is six bits wide, the DCI code points 906 may include 64 code points (e.g., Sc=2 6=64). Unlike DCI-based aperiodic CSI report triggering, for DCI-based semi-persistent CSI report triggering, the number of code points may be fixed, i.e., no MAC-CE subselection may occur to select active DCI code points from a set of DCI code points. DCI 902 may be associated with a semi-persistent CSI RNTI. For example, a base station may scramble the CRC of DCI 902 using the semi-persistent CSI RNTI. The UE may interpret the DCI in different ways (e.g., DCI 0_1) depending on the type of RNTI used to scramble the DCI. DCI scrambled with a semi-persistent CSI RNTI for CRC may be used for semi-persistent CSI activation / deactivation, and UL data may not be multiplexed on the semi-persistent PUSCH.

[0101] DCI code point n 907 (or another DCI code point in DCI code point 906) may point to a semi-persistent trigger state 908 in a semi-persistent trigger state 909 defined by RRC communication. Semi-persistent trigger state 908 may be defined as a semi-persistent CSI reporting setting identified by CSI reporting setting ID 910. Unlike the aperiodic CSI reporting trigger based on DCI, semi-persistent trigger state 908 may trigger a single CSI report. Semi-persistent trigger state 908 may include a mapping to a single semi-persistent CSI reporting setting. The code point of CSI request field 904 may be mapped to a semi-persistent CSI reporting setting configured in RRC communication (without MAC-CE sub-selection). For CSI reporting setting ID 910, the UE may calculate CSI and include the calculated CSI in the scheduled PUSCH transmission to the base station.

[0102] DCI 902 may also include other fields 912, which may include the above Figure 8 The activation and deactivation of CSI reporting may be based on the data in the other fields 912. For example, the HARQ process number (i.e., HARQ process ID) and the redundancy version in the other fields 912 may be used for both activation and deactivation of CSI reporting, and the modulation and coding scheme and resource block indication in the other fields 912 may be used for activation of CSI reporting.

[0103] Fig.101000 is a diagram illustrating an example of a MAC-CE based semi-persistent CSI report triggering. The base station may send a MAC-CE 1002 on a PUCCH to a UE, which triggers the UE to send a semi-persistent CSI report to the base station. The MAC-CE 1002 may include a BWP ID 1004. The MAC-CE 1002 may include a serving cell ID 1006, i.e., an ID of a component carrier (CC) on which the UE will send a CSI report. The BWP ID 1004, the serving cell ID 1006, and a reserved bit "R" may form the first octet within the MAC-CE 1002. The MAC-CE 1002 may include a S i Field 1008 (eg, S 0 , S 1 , S 2 and S 3 ). i Field 1008 may indicate the activation / deactivation status of the semi-persistent CSI reporting configuration within csi-ReportConfigToAddModList. 0 may refer to a reporting configuration including PUCCH resources for semi-persistent CSI reporting in a BWP corresponding to BWP ID 1004 and having the lowest CSI-ReportConfigId in the list with type set to semiPersistentOnPUCCH, S 1 may refer to the reporting configuration with the second lowest CSI-ReportConfigId, S 2 may refer to the reporting configuration with the third lowest CSI-ReportConfigId, and S 3 May refer to the reporting configuration with the fourth lowest CSI-ReportConfigId. If the number of reporting configurations is less than i+1, the MAC entity may ignore the Si field. i The fields within field 1008 may be set to "1" to indicate that the corresponding semi-persistent CSI reporting configuration will be enabled. i The fields within field 1008 may be set to 0 to indicate that the corresponding semi-persistent CSI reporting configuration is to be disabled. i Field 1008 and four reserved bits R may form the second octet within MAC-CE 1002 .

[0104] Wireless communication systems can be configured to share available system resources and provide various telecommunication services (e.g., telephone, video, data, messaging, broadcasting, etc.) based on multiple access technologies that support communication with multiple users. Full-duplex operation (in which wireless devices exchange uplink and downlink communications that overlap in time) can achieve more efficient use of the wireless spectrum. Full-duplex operation may include simultaneous transmission and reception within the same frequency range. In some examples, the frequency range may be a mmW frequency range, such as frequency range 2 (FR2). In some examples, the frequency range may be a frequency range below 6 GHz, such as frequency range 1 (FR1). Full-duplex communication can reduce latency. For example, full-duplex operation may enable a UE to receive a downlink signal in an uplink-only timeslot, which may reduce latency in downlink communications. Full-duplex communication can improve spectral efficiency, for example, spectral efficiency per cell or per UE. Full-duplex communication can achieve more efficient use of wireless resources.

[0105] When a first UE (e.g., an interfered UE) transmits and receives data on the same frequency band, the first UE may experience CLI from a second UE (e.g., an interfering UE). CLI may affect the communication reliability at the first UE. Efficient triggering of CLI reporting by the UE is needed so that the base station and / or the UE can adjust the transmission / reception parameters to mitigate the impact of CLI.

[0106] To improve the efficiency of information exchange about CLI and addressing CLI, L1 (DCI-based) activation and deactivation of L2 (MAC-CE) based CLI reporting is disclosed herein. L1 activation / deactivation may be based on a DCI associated with an RNTI for AP or SP CSI reporting. L1 activation / deactivation of L2 CLI reporting may be faster than L2 activation of L2 CLI reporting. Techniques for parameter adaptation of L2 CLI reporting (e.g., adaptation of wideband to subband, adaptation of subband to be reported, other CLI reporting parameters such as periodicity, etc.) are also disclosed herein.

[0107] In an example, the UE receives L1 signaling, such as DCI, for initiating MAC-CE CLI reporting. The UE sends one or more MAC-CE CLI reports based on the DCI. Compared with the initiation of MAC-CE CLI reporting by L2 signaling, when the MAC-CE CLI report is triggered by DCI, the initiation of the MAC-CE CLI report may be faster. Since the UE may be able to send the MAC-CE CLI report to the base station more quickly via the initiation of MAC-CE CLI reporting by DCI, the base station and / or the UE may be able to adjust the transmission / reception parameters more quickly to mitigate the impact of CLI.

[0108] Fig.141400 is a communication flow diagram illustrating an example communication between a UE 1402 and a base station 1404. The UE 1402 may be an interfered UE that is experiencing CLI from one or more UEs in proximity to the UE 1402. In an example, the UE 1402 may be operating in a full-duplex mode such as SBFD or IBFD. At 1406, the base station 1404 sends a DCI (alternatively referred to as UE-specific DCI or L1 signaling) to the UE 1402 for activating (or deactivating) L2 CLI reporting on the UL MAC-CE. In an example, the DCI may be a DCI format 0_1, such as DCI 802 or DCI 902.

[0109] In one aspect, the DCI sent at 1406 may be associated with an RNTI that is configured or dedicated to triggering L2 CLI reporting. For example, the base station 1404 may utilize the new RNTI to scramble the CRC of the DCI. The new RNTI may be different from the C-RNTI or the semi-persistent CSI RNTI (SP-CSI RNTI). The CSI request field in the DCI (e.g., a CSI request field similar to the CSI request field 804 or the CSI request field 904) may include one or more bits indicating that L2 CLI reporting (also known as MAC-CE CLI reporting) will be activated or deactivated. In this regard, at 1408, the base station 1404 may configure the L2 trigger state list via RRC communication. The L2 trigger state may include a single L2 CLI report setting (i.e., include a mapping to the single L2 CLI report setting).

[0110] In one aspect, the DCI sent at 1406 may be associated with an SP-CSI RNTI. The SP-CSI RNTI may trigger an L2CLI report. Additionally, since the DCI is not used to schedule UL-SCH transmissions, the SP-CSI RNTI may also trigger an SP CSI report. In an example, a subset of trigger states (i.e., a subset of semi-persistent trigger states 909) may be reserved for L2 CLI reporting. For example, at 1408, the base station 1404 may reserve a subset of trigger states via RRC communications. In an example, trigger states one to forty-eight may be reserved for semi-persistent CSI reporting, while trigger states forty-nine to sixty-four may be reserved for L2 CLI reporting. This is merely an example for illustrating the concept, and the subsets of trigger states for semi-persistent CSI reporting and for L2 CLI reporting may be different. In this example, if the DCI includes an indication of trigger state fifty-five, the UE 1402 is notified that L2 CLI reporting will be utilized instead of SP CSI reporting.

[0111] In another example, at 1410, the base station 1404 may send a MAC-CE to the UE 1402. The MAC-CE may select a subset of trigger states reserved for L2CLI reporting (e.g., a subset of semi-persistent trigger states 909). The DCI sent at 1406 may include one or more bits that select a trigger state in the subset of trigger states. In an example, a bit in the CSI request field 904 may select a trigger state.

[0112] In another example, a field in the DCI sent at 1406 may be used to distinguish between semi-persistent CSI reporting and L2CLI reporting. The DCI may not be used to schedule UL-SCH. For example, one or more of the other fields 912 may be used to trigger L2CLI reporting. The activation and deactivation of SP CSI reporting may be determined based on a combination of fields of the DCI.

[0113] In one aspect, the DCI sent at 1406 may be associated with a C-RNTI. The C-RNTI may trigger an L2 CLI report. In an example, a subset of trigger states (i.e., a subset of aperiodic trigger states 810) may be reserved for L2 CLI reporting. For example, at 1408, the base station 1404 may reserve a subset of trigger states via RRC communication. In an example, trigger states one to forty-eight may be reserved for aperiodic CSI reporting, while trigger states forty-nine to sixty-four may be reserved for L2 CLI reporting. This is merely an example to illustrate the concept, and the subsets of trigger states for aperiodic CSI reporting and for L2 CLI reporting may be different.

[0114] In another example, at 1410, the base station 1404 may send a MAC-CE configured or dedicated for a sub-selection of code points for L2 CLI reporting to the UE 1402. The MAC-CE may indicate a subset of code points reserved for L2 CLI reporting (e.g., a subset of the configured DCI code point set 806). Fig.11 , a first diagram 1102 depicting MAC-CE sub-selection for CLI reporting is illustrated. A second diagram 1104 depicting MAC-CE sub-selection for CSI and CLI reporting is also illustrated. A MAC-CE (e.g., the MAC-CE sent at 1410) may indicate the number of codepoints active for CSI reporting (Sc_csi). The remaining codepoints (Sc_cli) are active for L2 CLI reporting.

[0115] At 1412, UE 1402 may perform measurements on the (initiated) CLI measurement resources based on the DCI received at 1406 from base station 1404. For example, the measurements may include received signal strength indicator (RSSI) measurements on the (initiated) CLI measurement resources. At 1414, UE 1402 may send one or more L2 CLI reports on a UL MAC-CE to base station 1404. The one or more L2 CLI reports may include measurements.

[0116] In one aspect, at 1408, the base station 1404 may configure the UE 1402 with multiple CLI reporting configurations. At 1406, the DCI received by the UE 1402 may trigger the UE 1402 to send more than one L2 CLI report. At 1416, the base station 1404 may send a DCI (e.g., a DCI associated with a new RNTI, SP-CSI RNTI, or C-RNTI as described above) that disables one or more L2 CLI reports based on the L2 CLI report received by the base station 1404 at 1414. At 1418, the UE 1402 may disable one or more of the L2 CLI reports based on the DCI received at 1416.

[0117] The CLI experienced by the UE may be dynamic due to changes in the locations of other UEs around the UE. Thus, in one aspect, at 1420, the base station 1404 may send a parameter adaptation to the UE 1402 via a DCI (e.g., a DCI associated with a new RNTI, SP-CSI RNTI, or C-RNTI as described above) based on the L2 CLI report received by the base station 1404 at 1414. The parameter adaptation may include one or more of a wideband versus subband reporting indication (i.e., reporting granularity), a sub-selection of subbands to report, an update to a CLI reporting threshold (e.g., an update to a threshold to be met for L2 CLI reporting to occur), and / or a type D quasi-co-location (QCL-D) update to measurement resources. At 1422, the UE 1402 may apply the parameter adaptation to the L2 CLI report such that one or more subsequent L2 reports reported by the UE 1402 are based on the parameter adaptation. In an example, the parameter adaptation may cause the UE 1402 to change from wideband CLI reporting to subband CLI reporting. The UE 1402 may apply parameter adaptation in a faster manner compared to disabling one or more L2 CLI reports.

[0118] In one aspect, the base station 1404 may signal the parameter adaptation via a field in the DCI that initiates L2 CLI reporting (e.g., other fields 814 and 912 in DCI 802 and DCI 902, respectively). In an example, if at 1420, the UE 1402 receives an activation DCI for activated L2 CLI reporting, the UE 1402 may interpret the activation DCI as signaling parameter adaptation for activated L2 CLI reporting. Thus, at 1422, the UE 1402 may apply the parameter adaptation. Thus, subsequent L2 CLI reporting is based on the parameters in the parameter adaptation.

[0119] In one aspect, at 1408, UE 1402 can receive an adaptive parameter list (eg, a list of parameter adaptations described above) from base station 1404 via RRC communication. In this aspect, at 1424, UE 1402 is configured with the adaptive parameter list.

[0120] In an example, the adaptability parameter list may include a list of subbands or subband combinations to be reported in the L2 CLI report. For example, the list may indicate that (1) subband 1 and subband 2 are to be reported, (2) subband 1 is to be reported, or (3) subband 2 is to be reported. In one aspect, after the first initiation of L2 CLI reporting, the adaptability parameter list has an entry enabled by default (e.g., the first entry - subband 1 and subband 2). Thus, when the UE 1402 receives the DCI at 1406, the DCI triggers the UE 1402 to send an L2 CLI report based on subband 1 and subband 2. On the other hand, after the first initiation of L2 CLI reporting, the DCI received by the UE 1402 at 1406 specifies an entry in the adaptability parameter list (e.g., subband 1).

[0121] As indicated above, the UE 1402 may receive a parameter adaptation sent by the UE 1402 at 1420. The UE 1402 may apply the parameter adaptation at a time determined based on various factors. At 1423, the UE 1402 may send one (or more) L2 CLI reports based on the parameter adaptation. Fig.12 A first diagram 1202, a second diagram 1204, and a third diagram 1206 are illustrated that illustrate different ways of determining when a UE 1402 is to apply parameter adaptation (also referred to as parameter updating).

[0122] In one aspect illustrated in the first diagram 1202, the UE 1402 may apply the parameter update after a minimum of X_μ symbols 1208 occurring after the UE 1402 receives a DCI carrying the parameter update (e.g., the DCI received by the UE 1402 at 1420), e.g., where X_μ is an integer. The minimum X_μ symbols 1208 may vary depending on the SCS of the BWP.

[0123] In one aspect illustrated in the second diagram 1204, the UE 1402 may apply the parameter update after a minimum of Y_μ time slots 1210 from the time slot carrying the DCI with the parameter update, where Y_μ is an integer. In the example, the DCI may be received by the UE 1402 at time slot 1212, and the DCI including the parameter update is received at time slot 1214. The UE 1402 may apply the parameter update indicated by the DCI received in time slot 1214 at time slot 1216. However, for time slots occurring within the minimum of Y_μ time slots 1210, the UE 1402 applies the parameters specified by the DCI received at time slot 1212.

[0124] In one aspect illustrated in the third diagram 1206, the UE 1402 may access the table 1218 based on the parameter type indicated in the parameter update and the SCS. The table 1218 may have a first dimension corresponding to different types of parameters (e.g., wideband versus subband reporting indication, subselection of subbands to report, etc.) and a second dimension corresponding to different SCSs. Each entry in the table may include an application time for the parameter update. For example, entry 1220 of the table 1218 may include an application time for the QCL-D update, and entry 1222 of the table 1218 may include a wideband versus subband reporting update application time.

[0125] In one aspect, the base station 1404 may enable / disable CLI measurement resources and L2 CLI reporting separately. This may be useful if the same CLI measurement resources can be used for L1 CLI reporting. Fig.13 At 1426, the base station 1404 may send an activation of one or more CLI measurement resources separately from the DCI that activates L2 CLI reporting at 1406. The activation may be sent via MAC-CE. At 1428, the UE 1402 activates one or more CLI measurement resources.

[0126] In one aspect, the base station 1404 may jointly initiate CLI measurement resources and L2 CLI reporting via the DCI sent at 1406. In this regard, the UE 1402 may initiate CLI measurement resources and may jointly start L2 CLI reporting at 1428. In one example, there may be a one-to-one correspondence between L2 CLI reports and associated CLI measurement resources, i.e., CLI measurement resources are not shared between L2 CLI reports.

[0127] In another example, CLI measurement resources may be shared between one or more L2 CLI reports. For example, a first L2 CLI report and a second L2 CLI report may share the same CLI measurement resources. Fig.13, depicts a diagram 1300 illustrating sharing of CLI measurement resources. At 1302, a base station 1404 may send L1 signaling to initiate the CLI measurement resources and a first L2 CLI report using the CLI measurement resources. At 1304, the base station 1404 may send L1 signaling to initiate a second CLI report using the CLI measurement resources. At 1306, the base station 1404 may send L1 signaling to deactivate the first CLI report. The CLI measurement resources may remain active. At 1308, the base station 1404 may send L1 signaling to deactivate the second CLI report. Since the CLI measurement resources are no longer used for CLI reporting, the CLI measurement resources may be deactivated.

[0128] Fig.15 1500 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104, UE 350, UE 1402, device 1904). In an example, the method may be performed by the above-mentioned L2 CLI reporting component 198. The method may be associated with various advantages for the UE, such as faster triggering of MAC-CE CLI reporting.

[0129] At 1502, the UE receives a DCI for initiating MAC-CE CLI reporting. Fig.14 , UE 1402 may receive a DCI for initiating an L2 CLI report sent by base station 1404 at 1406. In another example, the DCI may be Figure 8 and Fig. 9 DCI 802 or DCI 902 in.

[0130] At 1504, the UE sends one or more MAC-CE CLI reports based on the DCI. Fig.14 At 1414, UE 1402 may send one or more L2CLI reports on the UL MAC-CE.

[0131] Fig.16 1600 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104, UE 350, UE 1402, device 1904). In an example, the method (including various configurations described below) may be performed by the above-mentioned L2 CLI reporting component 198. The method may be associated with various advantages for the UE, such as faster triggering of MAC-CE CLI reporting.

[0132] At 1610, the UE receives a DCI for initiating MAC-CE CLI reporting. Fig.14 , UE 1402 may receive a DCI for initiating an L2 CLI report sent by base station 1404 at 1406. In another example, the DCI may be Figure 8 and Fig. 9 DCI 802 or DCI 902 in.

[0133] At 1618, the UE sends one or more MAC-CE CLI reports based on the DCI. Fig.14 At 1414, UE 1402 may send one or more L2CLI reports on the UL MAC-CE.

[0134] In some aspects, at 1602, the UE may receive one or more configurations for MAC-CE CLI reporting prior to a DCI, wherein the DCI activates the previously received configurations for the MAC-CE CLI reporting. Fig.14 At 1408, the UE 1402 may receive an RRC communication including configurations for MAC-CE CLI reporting, and at 1406, the DCI may initiate these configurations.

[0135] In some aspects, at 1612, the UE may perform one or more measurements based on the DCI before sending the one or more MAC-CE CLI reports, wherein the one or more MAC-CE CLI reports include the one or more measurements. Fig.14 At 1412, the UE 1402 may perform measurements based on the DCI sent by the base station 1404 at 1406. In an example, at 1414, the L2 CLI report sent by the UE 1402 may report the measurements.

[0136] In some aspects, at 1622, the UE may receive a second DCI for disabling the MAC-CE CLI reporting. Fig.14 At 1416, the UE 1402 may receive a DCI for disabling L2 CLI reporting. In an example, the DCI may be Figure 8 and Fig. 9 DCI 802 or DCI 902 in.

[0137] In some aspects, the DCI may be based on an RNTI associated with a MAC-CE CLI report, wherein the RNTI may be different from at least one other RNTI used for aperiodic CSI reporting, wherein a CSI request field in the DCI may indicate that the MAC-CE CLI report is to be initiated, and wherein a trigger state configured in the RRC may include a mapping to an L2 CLI reporting setting. For example, referring to Fig.14 , the DCI sent at 1406 may be associated with the new RNTI. Figure 8, the CSI request field 804 may indicate that MAC-CE CLI reporting will be initiated. Figure 8 , the aperiodic trigger state 808 may include a mapping to the CSI report setting ID 812A. In another example, the aperiodic trigger state 808 may include a mapping to the CSI report setting ID 812B.

[0138] In some aspects, the DCI may be based on the RNTI that triggers the MAC-CE CLI report, where the RNTI may be equal to at least one other RNTI used for semi-persistent CSI reporting. Fig.14 , the DCI sent at 1406 may be associated with the SP-CSIRNTI. In another example, reference Fig. 9 , SP-CSI RNTI can be associated with DCI 902.

[0139] In some aspects, a DCI may be associated with multiple trigger states, where a subset of the multiple trigger states is used for MAC-CE CLI reporting. Fig.14 , the DCI sent at 1406 may be associated with a trigger state, and the RRC communication at 1408 may indicate a subset of trigger states for MAC-CE CLI reporting.

[0140] In some aspects, at 1606, the UE may receive a MAC-CE indicating a subset of a plurality of trigger states for the MAC-CE CLI report, wherein the DCI may include an indication of one or more of the plurality of trigger states for the MAC-CE CLI report. For example, referring to Fig.14 , UE 1402 may receive a MAC-CE sent by base station 1404 at 1410, wherein the MAC-CE indicates a triggering state for MAC-CE-CLI reporting. Fig.11 , the second diagram 1104 depicts MAC-CE sub-selection for CSI and CLI reporting.

[0141] In some aspects, one or more DCI field values ​​in the DCI may indicate whether at least one of the MAC-CE CLI report or the SP CSI report is to be enabled. Fig. 9 , the other fields 912 may include a value indicating whether at least one of MAC-CE CLI reporting or SP CSI reporting is to be enabled.

[0142] In some aspects, the DCI may be based on the RNTI that triggers the MAC-CE CLI report, where the RNTI may be equal to at least one other RNTI used for aperiodic CSI reporting. Fig.14, the DCI sent at 1406 may be equivalent to the C-RNTI used for APCSI reporting.

[0143] In some aspects, a DCI may be associated with multiple trigger states, where a subset of the multiple trigger states may be used for MAC-CE CLI reporting. Figure 8 , the DCI 802 may be associated with the aperiodic trigger state 810, and a subset of the trigger states (eg, the aperiodic trigger state 808) may be used for MAC-CE CLI reporting.

[0144] In some aspects, at 1608, the UE may receive a MAC-CE indicating that a subset of the plurality of code points in the DCI is used for the MAC-CE CLI report. Fig.14 , UE 1402 may receive a MAC-CE sent by base station 1404 at 1410, wherein the MAC-CE indicates a subset of the plurality of code points for MAC-CE CLI reporting. In another example, reference Fig.11 , the second diagram 1104 depicts MAC-CE sub-selection for CSI and CLI reporting.

[0145] In some aspects, at 1604, the UE may receive one or more CLI report configurations prior to receiving the DCI and via RRC communication, wherein the one or more MAC-CE CLI reports may be based on the one or more CLI report configurations. Fig.14 , UE 1402 may receive a CLI report configuration sent by base station 1404 at 1408, and an L2 CLI report sent by UE 1402 at 1414 may be based on the CLI report configuration.

[0146] In some aspects, at 1624, the UE may receive a second DCI for deactivating the first MAC-CE CLI report or for activating the second MAC-CE CLI report. Fig.14 , UE 1402 may receive a DCI sent by base station 1404 at 1406, and the DCI may deactivate the first MAC-CE CLI reporting or activate the second MAC-CE CLI reporting.

[0147] In some aspects, the DCI includes one or more fields including one or more parameters for a MAC-CE CLI report, and at 1620, the UE may update the MAC-CE CLI report based on the one or more parameters. Figure 8 and Fig. 9, other fields 814 in DCI 802 and / or other fields 912 in DCI 902 may include parameters for CLI reporting. Fig.14 At 1422 , the UE may apply parameter adaptation included in the DCI sent by the base station 1404 at 1420 .

[0148] In some aspects, the one or more parameters may include one or more of: an indication for wideband reporting or subband reporting; a subselection of one or more subbands to report; an update to a CLI reporting threshold; or a QCL-D update to a measurement resource. Fig.14 , UE 1402 may receive parameter adaptation sent by base station 1404, and the parameter adaptation may include one or more of an indication for wideband reporting or subband reporting; a sub-selection of one or more subbands to be reported; an update to a CLI reporting threshold; or a QCL-D update to measurement resources.

[0149] In some aspects, the one or more CLI report configurations may include a list including the one or more parameters, wherein the DCI may indicate a parameter of the one or more parameters, or the list indicates a default parameter. Fig.14 , UE 1402 may receive a CLI report configuration including an adaptive parameter list via RRC communication at 1408. For example, UE 1402 may receive a DCI sent by base station 1404 at 1406, wherein the DCI may indicate a parameter in the adaptive parameter list.

[0150] In some aspects, updating the MAC-CE CLI report based on the one or more parameters occurs at a time that may be based on one of: a first number of symbols from the DCI; a second number of time slots from the time slot carrying the DCI; or a type of SCS and the one or more parameters. Fig.12 , the first diagram 1202, the second diagram 1204 and the third diagram 1206 respectively illustrate updating the MAC-CE CLI report based on time, where the time may be based on one of the following: a first number of symbols from the DCI; a second number of time slots from the time slot carrying the DCI; or the type of SCS and one or more parameters.

[0151] In some aspects, at 1614, the UE may receive a MAC-CE for initiating one or more CLI measurement resources for the one or more MAC-CE CLI reports. Fig.14, UE 1402 may receive a MAC-CE sent by base station 1404 at 1410, wherein the MAC-CE is used to activate one or more CLI measurement resources. For example, at 1428, UE 1402 may activate CLI measurement resources.

[0152] In some aspects, at 1616, the UE may perform measurements on the one or more CLI measurement resources based on the MAC-CE for initiating the one or more CLI measurement resources. Fig.14 At 142 , UE 1402 may perform measurements on the CLI measurement resources initiated at 1428 .

[0153] In some aspects, the DCI may also enable one or more CLI measurement resources for the one or more MAC-CE CLI reports. Fig.14 , UE 1402 may receive a DCI sent by base station 1404 at 1406 , wherein the DCI initiates CLI measurement resources at 1428 .

[0154] In some aspects, the one or more CLI measurement resources may be shared between the one or more MAC-CE CLI reports, or each of the one or more CLI measurement resources may be utilized by a different MAC-CE CLI report in the one or more MAC-CE CLI reports. Fig.14 , the CLI measurement resources initiated at 1428 may or may not be shared by different L2 CLI reports. In another example, reference Fig.13 , diagram 1300 illustrates sharing of CLI measurement resources.

[0155] Fig.17 1700 is a flow chart of a wireless communication method. The method may be performed by a network node (e.g., base station 102, base station 310, base station 1404, network entity 1902). In an example, the method may be performed by the report receiving component 199 described above. The method may be associated with various advantages for the network node, such as faster reception of MAC-CE CLI reports.

[0156] At 1702, the network node sends a DCI for initiating MAC-CE CLI reporting. Fig.14 At 1406, the base station 1404 may send a DCI for initiating L2 CLI reporting. In another example, the DCI may be Figure 8 and Fig. 9 DCI 802 or DCI 902 in.

[0157] At 1704, the network node receives one or more MAC-CE CLI reports based on the DCI. Fig.14 , base station 1404 may receive one or more L2 CLI reports sent by UE 1402 at 1414.

[0158] Fig.18 1800 is a flow chart of a wireless communication method. The method may be performed by a network node (e.g., base station 102, base station 310, base station 1404, network entity 1902). In an example, the method (including various configurations described below) may be performed by the report receiving component 199 described above. The method may be associated with various advantages for the network node, such as faster reception of MAC-CECLI reports.

[0159] At 1810, the network node sends a DCI for initiating MAC-CE CLI reporting. Fig.14 At 1406, the base station 1404 may send a DCI for initiating L2 CLI reporting. In another example, the DCI may be Figure 8 and Fig. 9 DCI 802 or DCI 902 in.

[0160] At 1814, the network node receives one or more MAC-CE CLI reports based on the DCI. Fig.14 , base station 1404 may receive one or more L2 CLI reports sent by UE 1402 at 1414.

[0161] In some aspects, at 1802, the network node may send one or more configurations for a MAC-CE CLI report prior to the DCI, wherein the DCI may initiate a previously sent configuration for the MAC-CE CLI report. Fig.14 At 1408, base station 1404 may send an RRC communication including configurations for MAC-CE CLI reporting, and the DCI sent at 1406 may initiate these configurations.

[0162] In some aspects, one or more measurements may be performed based on the DCI, wherein one or more MAC-CECLI reports may include the one or more measurements. Fig.14 , at 1412 , one or more measurements are performed based on the DCI sent at 1406 .

[0163] In some aspects, at 1816, the network node may send a second DCI for disabling MAC-CE CLI reporting. Fig.14At 1416, the base station 1404 may send a DCI to disable MAC-CE CLI reporting. In an example, the DCI may be Figure 8 and Fig. 9 DCI 802 or DCI 902 in.

[0164] In some aspects, the DCI may be based on an RNTI associated with a MAC-CE CLI report, wherein the RNTI may be different from at least one other RNTI used for AP CSI reporting, wherein a CSI request field in the DCI may indicate that the MAC-CE CLI report is to be initiated, and wherein a trigger state configured in the RRC may include a mapping to a L2 CLI reporting setting. For example, referring to Fig.14 , the DCI sent at 1406 may be associated with the new RNTI. Figure 8 , the CSI request field 804 may indicate that MAC-CE CLI reporting will be initiated. Figure 8 , the non-periodic trigger state 808 may include a mapping to the CSI report setting ID 812A.

[0165] In some aspects, the DCI may be based on the RNTI that triggers the MAC-CE CLI report, where the RNTI may be equal to at least one other RNTI used for semi-persistent CSI reporting. Fig.14 , the DCI sent at 1406 may be associated with the SP-CSIRNTI. In another example, reference Fig. 9 , SP-CSI RNTI can be associated with DCI 902.

[0166] In some aspects, a DCI may be associated with multiple trigger states, where a subset of the multiple trigger states may be used for MAC-CE CLI reporting. Fig.14 , the DCI sent at 1406 may be associated with a trigger state, and the RRC communication at 1408 may indicate a subset of trigger states for MAC-CE CLI reporting.

[0167] In some aspects, at 1806, the network node may send a MAC-CE indicating that a subset of a plurality of trigger states are available for the MAC-CE CLI report, wherein the DCI may include an indication of one or more of the plurality of trigger states for the MAC-CE CLI report. For example, referring to Fig.14 At 1410, the base station may send a MAC-CE indicating a triggering state for a MAC-CE-CLI report. Fig.11 , the second diagram 1104 depicts MAC-CE sub-selection for CSI and CLI reporting.

[0168] In some aspects, one or more DCI field values ​​in the DCI may indicate whether at least one of the MAC-CE CLI reporting or the semi-persistent CSI reporting is to be enabled. Fig. 9 , the other fields 912 may include a value indicating whether at least one of MAC-CE CLI reporting or semi-persistent CSI reporting is to be enabled.

[0169] In some aspects, the DCI may be based on the RNTI that triggers the MAC-CE CLI report, where the RNTI may be equal to at least one other RNTI used for aperiodic CSI reporting. Fig.14 , the DCI sent at 1406 may be equivalent to the C-RNTI used for aperiodic CSI reporting.

[0170] In some aspects, a DCI may be associated with multiple trigger states, where a subset of the multiple trigger states may be used for MAC-CE CLI reporting. Figure 8 , the DCI 802 may be associated with the aperiodic trigger state 810, and a subset of the trigger states (eg, the aperiodic trigger state 808) may be used for MAC-CE CLI reporting.

[0171] In some aspects, at 1808, the network node may send a MAC-CE indicating that a subset of the plurality of code points in the DCI may be used for the MAC-CE CLI report. Fig.14 At 1410, the base station 1404 may send a MAC-CE indicating a subset of the plurality of code points for a MAC-CE CLI report. Fig.11 , the second diagram 1104 depicts MAC-CE sub-selection for CSI and CLI reporting.

[0172] In some aspects, at 1804, the network node may send one or more CLI report configurations prior to sending the DCI and via RRC communication, wherein the one or more MAC-CE CLI reports may be based on the one or more CLI report configurations. Fig.14 At 1408, the base station 1404 may send a CLI report configuration via RRC communication, and the L2 CLI report received by the base station 1404 may be based on the CLI report configuration.

[0173] In some aspects, at 1818, the network node may send a second DCI for disabling the first MAC-CE CLI report or for enabling the second MAC-CE CLI report. Fig.14At 1406, the base station 1404 may send a DCI to disable the first MAC-CE CLI report or to enable the second MAC-CE CLI report.

[0174] In some aspects, the DCI may include one or more fields including one or more parameters for a MAC-CE CLI report, wherein the MAC-CE CLI report may be updated based on the one or more parameters. Figure 8 and Fig. 9 , other fields 814 in DCI 802 and / or other fields 912 in DCI 902 may include parameters for CLI reporting. Fig.14 At 1420, the base station 1404 may send a parameter adaptation, and at 1422, the parameter adaptation may be applied.

[0175] In some aspects, the one or more parameters may include one or more of: an indication for wideband reporting or subband reporting; a subselection of one or more subbands to report; an update to a CLI reporting threshold; or a QCL-D update to a measurement resource. Fig.14 At 1420, the base station 1404 may send a parameter adaptation, which may include an indication for wideband reporting or subband reporting; a sub-selection of one or more subbands to report; an update to a CLI reporting threshold; or one or more of a QCL-D update to measurement resources.

[0176] In some aspects, the one or more CLI report configurations may include a list including the one or more parameters, wherein the DCI may indicate a parameter of the one or more parameters, or the list indicates a default parameter. Fig.14 At 1408, the base station 1404 may send a CLI report configuration including an adaptive parameter list via RRC communication.

[0177] In some aspects, the MAC-CE CLI report may be updated based on the one or more parameters at a time based on one of: a first number of symbols from the DCI; a second number of time slots from the time slot carrying the DCI; or a type of SCS and the one or more parameters. Fig.12 , the first diagram 1202, the second diagram 1204 and the third diagram 1206 respectively illustrate updating the MAC-CE CLI report based on a time that can be based on one of the following: a first number of symbols from the DCI; a second number of time slots from the time slot carrying the DCI; or a type of SCS and one or more parameters.

[0178] In some aspects, at 1812, the network node may send a MAC-CE for initiating one or more CLI measurement resources for the one or more MAC-CE CLI reports. Fig.14 At 1410, the base station 1404 may send a MAC-CE, wherein the MAC-CE is used to activate one or more CLI measurement resources. For example, at 1428, the CLI measurement resource may be activated.

[0179] In some aspects, the DCI may also enable one or more CLI measurement resources for the one or more MAC-CE CLI reports. Fig.14 The DCI sent at 1406 may initiate one or more CLI measurement resources for the one or more MAC-CE CLI reports.

[0180] In some aspects, the one or more CLI measurement resources may be shared between the one or more MAC-CE CLI reports, or each of the one or more CLI measurement resources may be utilized by a different MAC-CE CLI report in the one or more MAC-CE CLI reports. Fig.14 , the CLI measurement resources initiated at 1428 may or may not be shared by different L2 CLI reports. In another example, reference Fig.13 , diagram 1300 illustrates sharing of CLI measurement resources.

[0181] Fig.191900 is a diagram illustrating an example of a hardware implementation for an apparatus 1904. The apparatus 1904 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1904 may include a cellular baseband processor 1924 (also referred to as a modem) coupled to one or more transceivers 1922 (e.g., a cellular RF transceiver). The cellular baseband processor 1924 may include on-chip memory 1924'. In some aspects, the apparatus 1904 may also include one or more subscriber identity module (SIM) cards 1920 and an application processor 1906 coupled to a secure digital (SD) card 1908 and a screen 1910. The application processor 1906 may include on-chip memory 1906'. In some aspects, the device 1904 may also include a Bluetooth module 1912, a WLAN module 1914, an SPS module 1916 (e.g., a GNSS module), one or more sensor modules 1918 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio for positioning, and / or other technologies), an additional memory module 1926, a power source 1930, and / or a camera 1932. The Bluetooth module 1912, the WLAN module 1914, and the SPS module 1916 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1912, the WLAN module 1914, and the SPS module 1916 may include their own dedicated antennas and / or communicate using antennas 1980. The cellular baseband processor 1924 communicates with the UE 104 and / or with the RU associated with the network entity 1902 through the transceiver 1922 via one or more antennas 1980. The cellular baseband processor 1924 and the application processor 1906 may each include a computer-readable medium / memory 1924', 1906', respectively. The additional memory module 1926 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1924', 1906', 1926 may be non-transitory. The cellular baseband processor 1924 and the application processor 1906 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1924 / application processor 1906, enables the cellular baseband processor 1924 / application processor 1906 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1924 / application processor 1906 when executing the software.The cellular baseband processor 1924 / application processor 1906 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 1904 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1924 and / or the application processor 1906, while in another configuration, the device 1904 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1904.

[0182] As discussed above, the L2 CLI reporting component 198 is configured to receive a DCI for initiating MAC-CE CLI reporting and to send one or more MAC-CE CLI reports based on the DCI. The L2 CLI reporting component 198 may be further configured to perform a combined Figures 8 to 14 Described and / or by Fig.14 Any of the aspects of the UE execution in . The L2 CLI reporting component 198 may be within the cellular baseband processor 1924, the application processor 1906, or within both the cellular baseband processor 1924 and the application processor 1906. The L2 CLI reporting component 198 may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1904 may include multiple components configured for various functions. In one configuration, the device 1904 (and specifically, the cellular baseband processor 1924 and / or the application processor 1906) includes: a component for receiving a DCI for initiating a MAC-CE CLI report; and a component for sending one or more MAC-CE CLI reports based on the DCI. The device 1904 may also include a component for performing a combined Figures 8 to 14 Described and / or by Fig.14 1904. The component may be an L2CLI reporting component 198 of the apparatus 1904 configured to perform the functions recited by the component. As described above, the apparatus 1904 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recited by the component.

[0183] Fig. 202000 is a diagram illustrating an example of a hardware implementation for a network entity 2002. The network entity 2002 may be a BS, a component of a BS, or may implement BS functionality. The network entity 2002 may include at least one of a CU 2010, a DU 2030, or a RU 2040. For example, depending on the layer functionality processed by the report receiving component 199, the network entity 2002 may include a CU 2010; both a CU 2010 and a DU 2030; each of a CU 2010, a DU 2030, and a RU 2040; a DU 2030; both a DU 2030 and a RU 2040; or a RU 2040. The CU 2010 may include a CU processor 2012. The CU processor 2012 may include an on-chip memory 2012'. In some aspects, the CU 2010 may also include an additional memory module 2014 and a communication interface 2018. CU2010 communicates with DU 2030 via a midhaul link (such as an F1 interface). DU 2030 may include a DU processor 2032. DU processor 2032 may include on-chip memory 2032'. In some aspects, DU 2030 may also include additional memory modules 2034 and communication interface 2038. DU 2030 communicates with RU 2040 via a fronthaul link. RU 2040 may include a RU processor 2042. RU processor 2042 may include on-chip memory 2042'. In some aspects, RU 2040 may also include additional memory modules 2044, one or more transceivers 2046, antenna 2080, and communication interface 2048. RU 2040 communicates with UE 104. On-chip memory 2012', 2032', 2042' and additional memory modules 2014, 2034, 2044 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of the processors 2012, 2032, 2042 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0184] As discussed above, the report receiving component 199 is configured to send a DCI for initiating MAC-CE CLI reporting and receive one or more MAC-CE CLI reports based on the DCI. The report receiving component 199 may be further configured to perform a combined Figures 8 to 14 Described and / or by Fig.14Any of the aspects performed by the base station in. The report receiving component 199 may be within one or more processors of one or more of the CU 2010, the DU 2030, and the RU 2040. The report receiving component 199 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 2002 may include multiple components configured for various functions. In one configuration, the network entity 2002 includes: a component for sending a DCI for initiating a MAC-CE CLI report; and a component for receiving one or more MAC-CE CLI reports based on the DCI. The network entity 2002 may also include a component for performing a combined Figures 8 to 14 Described and / or by Fig.14 2002. The components may be a report receiving component 199 of the network entity 2002 configured to perform the functions recited by the components. As described above, the network entity 2002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the components 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.

[0185] When a first UE (e.g., an interfered UE) transmits and receives data on the same frequency band, the first UE may experience CLI from a second UE (e.g., an interfering UE). CLI may affect the communication reliability at the first UE. Efficient triggering of CLI reporting by the UE is needed so that the base station and / or the UE can adjust the transmission / reception parameters to mitigate the impact of CLI.

[0186] To address these issues, L1 (e.g., DCI-based) activation and deactivation of L2 (MAC-CE) based CLI reporting is disclosed herein. The L1 activation / deactivation may be based on a DCI associated with an RNTI used for AP or SP CSI reporting or based on a new RNTI. L1 activation / deactivation of L2 CLI reporting may be faster than L2 activation of L2 CLI reporting. Techniques for parameter adaptation of L2 CLI reporting (e.g., adaptation of wideband to subband, adaptation of subband to be reported, other CLI reporting parameters such as periodicity, etc.) are also disclosed herein.

[0187] In an example, the UE receives a DCI for initiating a MAC-CE CLI report. The UE sends one or more MAC-CE CLI reports based on the DCI. When the MAC-CE CLI report is triggered by the DCI, the initiation of the MAC-CE CLI report may be faster than the initiation of the MAC-CE CLI report by L2 signaling. Since the UE may be able to send a MAC-CE CLI report to the base station more quickly via the initiation of the MAC-CE CLI report by the DCI, the base station and / or the UE may be able to adjust the transmission / reception parameters more quickly to mitigate the impact of the CLI.

[0188] 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 each block in a sample order, but are not limited to the specific order or hierarchy provided.

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

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

[0191] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, but are not limiting.

[0192] Aspect 1 is a method for wireless communication at a user equipment (UE), the method comprising: receiving downlink control information (DCI) for initiating a medium access control element (MAC-CE) cross-link interference (CLI) report; and sending one or more MAC-CE CLI reports based on the DCI.

[0193] Aspect 2 is a method according to aspect 1, the method further comprising: receiving one or more configurations for the MAC-CE CLI report before the DCI, wherein the DCI initiates the previously received configuration for the MAC-CE CLI report.

[0194] Aspect 3 is a method according to any one of Aspects 1 to 2, the method further comprising: performing one or more measurements based on the DCI before sending the one or more MAC-CE CLI reports, wherein the one or more MAC-CE CLI reports include the one or more measurements.

[0195] Aspect 4 is a method according to any one of aspects 1 to 3, the method further comprising: receiving a second DCI for deactivating the MAC-CE CLI report.

[0196] Aspect 5 is a method according to any one of Aspects 1 to 4, wherein the DCI is based on a radio network temporary identifier (RNTI) associated with the MAC-CE CLI report, wherein the RNTI is different from at least one other RNTI used for non-periodic channel state information (AP CSI) reporting, wherein a channel state information (CSI) request field in the DCI indicates that the MAC-CE CLI report will be initiated, and wherein a trigger state configured in a radio resource control (RRC) includes a mapping to an L2 CLI report setting.

[0197] Aspect 6 is a method according to any one of aspects 1 to 4, wherein the DCI is based on a radio network temporary identifier (RNTI) that triggers the MAC-CECLI report, wherein the RNTI is equivalent to at least one other RNTI used for semi-persistent channel state information (SP CSI) reporting.

[0198] Aspect 7 is a method according to aspect 6, wherein the DCI is associated with a plurality of trigger states, wherein a subset of the plurality of trigger states is used for the MAC-CE CLI reporting.

[0199] Aspect 8 is a method according to Aspect 6, the method further comprising: receiving a MAC-CE indicating a subset of multiple trigger states for the MAC-CE CLI report, wherein the DCI includes an indication of one or more trigger states of the multiple trigger states for the MAC-CE CLI report.

[0200] Aspect 9 is a method according to aspect 6, wherein one or more DCI field values ​​in the DCI indicate whether at least one of the MAC-CE CLI report or the SP CSI report is to be enabled.

[0201] Aspect 10 is a method according to any one of aspects 1 to 4, wherein the DCI is based on a radio network temporary identifier (RNTI) that triggers the MAC-CECLI report, wherein the RNTI is equivalent to at least one other RNTI used for non-periodic channel state information (AP CSI) reporting.

[0202] Aspect 11 is a method according to aspect 10, wherein the DCI is associated with a plurality of trigger states, wherein a subset of the plurality of trigger states is used for the MAC-CE CLI reporting.

[0203] Aspect 12 is a method according to any one of aspects 10 to 11, the method further comprising: receiving a MAC-CE indicating that a subset of the plurality of code points in the DCI is used for the MAC-CE CLI report.

[0204] Aspect 13 is a method according to any one of Aspects 1 to 12, the method further comprising: receiving one or more CLI report configurations before receiving the DCI and via radio resource control (RRC) communication, wherein the one or more MAC-CE CLI reports are based on the one or more CLI report configurations.

[0205] Aspect 14 is a method according to any one of aspects 1 to 3 and 5 to 13, the method further comprising: receiving a second DCI for deactivating the first MAC-CE CLI report or for activating the second MAC-CE CLI report.

[0206] Aspect 15 is a method according to any one of Aspects 13 to 14, wherein the DCI includes one or more fields, the one or more fields include one or more parameters for the MAC-CE CLI report, and the method further includes: updating the MAC-CE CLI report based on the one or more parameters.

[0207] Aspect 16 is a method according to Aspect 15, wherein the one or more parameters include one or more of the following: an indication for broadband reporting or subband reporting; a sub-selection of one or more subbands to be reported; an update to a CLI reporting threshold; or a quasi-co-location type D (QCL-D) update to measurement resources.

[0208] Aspect 17 is a method according to any one of Aspects 15 to 16, wherein the one or more CLI report configurations include a list, the list includes the one or more parameters, wherein the DCI indicates a parameter among the one or more parameters, or the list indicates a default parameter.

[0209] Aspect 18 is a method according to any one of Aspects 15 to 17, wherein updating the MAC-CE CLI report based on the one or more parameters occurs at a time based on one of: a first number of symbols from the DCI; a second number of time slots from the time slot carrying the DCI; or a subcarrier spacing (SCS) and the type of the one or more parameters.

[0210] Aspect 19 is a method according to any one of Aspects 1 to 18, the method further comprising: receiving a MAC-CE for initiating one or more CLI measurement resources for the one or more MAC-CE CLI reports; and performing measurements on the one or more CLI measurement resources based on the MAC-CE for initiating the one or more CLI measurement resources.

[0211] Aspect 20: The method according to any one of aspects 1 to 18, wherein the DCI further enables one or more CLI measurement resources for the one or more MAC-CE CLI reports.

[0212] Aspect 21 is a method according to aspect 20, wherein the one or more CLI measurement resources are shared between the one or more MAC-CE CLI reports, or each of the one or more CLI measurement resources is utilized by a different MAC-CE CLI report among the one or more MAC-CE CLI reports.

[0213] Aspect 22 is an apparatus for wireless communication at a user equipment (UE), the apparatus comprising a memory and at least one processor, the at least one processor being coupled to the memory and being configured to perform a method according to any one of Aspects 1 to 21 based at least in part on information stored in the memory.

[0214] Aspect 23 is an apparatus for wireless communication, the apparatus comprising means for performing a method according to any one of aspects 1 to 21.

[0215] Aspect 24 is an apparatus according to aspect 22 or 23, the apparatus further comprising at least one transceiver, the at least one transceiver being configured to: receive the DCI for initiating the MAC-CE CLI report; and send the one or more MAC-CE CLI reports based on the DCI.

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

[0217] Aspect 26 is a method for wireless communication at a network node, the method comprising: sending downlink control information (DCI) for initiating a medium access control element (MAC-CE) cross-link interference (CLI) report; and receiving one or more MAC-CE CLI reports based on the DCI.

[0218] Aspect 27 is a method according to aspect 26, the method further comprising: sending one or more configurations for the MAC-CE CLI report before the DCI, wherein the DCI initiates the previously sent configurations for the MAC-CE CLI report.

[0219] Aspect 28 is a method according to any one of aspects 26 to 27, wherein one or more measurements are performed based on the DCI, wherein the one or more MAC-CE CLI reports include the one or more measurements.

[0220] Aspect 29 is a method according to any one of aspects 26 to 28, the method further comprising: sending a second DCI for deactivating the MAC-CE CLI report.

[0221] Aspect 30 is a method according to any one of Aspects 26 to 29, wherein the DCI is based on a radio network temporary identifier (RNTI) associated with the MAC-CE CLI report, wherein the RNTI is different from at least one other RNTI used for non-periodic channel state information (AP CSI) reporting, wherein a channel state information (CSI) request field in the DCI indicates that the MAC-CE CLI report will be initiated, and wherein a trigger state configured in a radio resource control (RRC) includes a mapping to an L2 CLI reporting setting.

[0222] Aspect 31 is a method according to any one of aspects 26 to 29, wherein the DCI is based on a radio network temporary identifier (RNTI) that triggers the MAC-CE CLI report, wherein the RNTI is equivalent to at least one other RNTI used for semi-persistent channel state information (SP CSI) reporting.

[0223] Aspect 32 is a method according to aspect 31, wherein the DCI is associated with a plurality of trigger states, wherein a subset of the plurality of trigger states is used for the MAC-CE CLI reporting.

[0224] Aspect 33 is a method according to Aspect 31, the method further comprising: sending a MAC-CE indicating a subset of multiple trigger states for the MAC-CE CLI report, wherein the DCI includes an indication of one or more trigger states of the multiple trigger states for the MAC-CE CLI report.

[0225] Aspect 34 is a method according to aspect 31, wherein one or more DCI field values ​​in the DCI indicate whether at least one of the MAC-CE CLI reporting or the SP CSI reporting is to be enabled.

[0226] Aspect 35 is a method according to any one of aspects 26 to 29, wherein the DCI is based on a radio network temporary identifier (RNTI) that triggers the MAC-CE CLI report, wherein the RNTI is equivalent to at least one other RNTI used for non-periodic channel state information (AP CSI) reporting.

[0227] Aspect 36 is a method according to aspect 35, wherein the DCI is associated with a plurality of trigger states, wherein a subset of the plurality of trigger states is used for the MAC-CE CLI reporting.

[0228] Aspect 37 is a method according to any one of aspects 35 to 36, the method further comprising: sending a MAC-CE indicating that a subset of the multiple code points in the DCI is used for the MAC-CE CLI report.

[0229] Aspect 38 is a method according to any one of Aspects 26 to 37, the method further comprising: sending one or more CLI report configurations before sending the DCI and via radio resource control (RRC) communication, wherein the one or more MAC-CE CLI reports are based on the one or more CLI report configurations.

[0230] Aspect 39 is a method according to any one of aspects 26 to 28 and 30 to 38, the method further comprising: sending a second DCI for deactivating the first MAC-CE CLI report or for activating the second MAC-CE CLI report.

[0231] Aspect 40 is a method according to any one of aspects 38 to 39, wherein the DCI includes one or more fields, the one or more fields including one or more parameters for the MAC-CE CLI report, wherein the MAC-CE CLI report is updated based on the one or more parameters.

[0232] Aspect 41 is a method according to Aspect 40, wherein the one or more parameters include one or more of the following: an indication for broadband reporting or subband reporting; a sub-selection of one or more subbands to be reported; an update to a CLI reporting threshold; or a quasi-co-location type D (QCL-D) update to measurement resources.

[0233] Aspect 42 is a method according to any one of Aspects 40 to 41, wherein the one or more CLI report configurations include a list, the list includes the one or more parameters, wherein the DCI indicates a parameter among the one or more parameters, or the list indicates a default parameter.

[0234] Aspect 43 is a method according to any one of Aspects 40 to 42, wherein the MAC-CE CLI report is updated based on the one or more parameters at a time based on one of the following: a first number of symbols from the DCI; a second number of time slots from the time slot carrying the DCI; or a subcarrier spacing (SCS) and the type of the one or more parameters.

[0235] Aspect 44 is a method according to any one of aspects 26 to 43, the method further comprising: sending a MAC-CE for initiating one or more CLI measurement resources for the one or more MAC-CE CLI reports.

[0236] Aspect 45 is a method according to any one of aspects 26 to 43, wherein the DCI further enables one or more CLI measurement resources for the one or more MAC-CE CLI reports.

[0237] Aspect 46 is a method according to aspect 45, wherein the one or more CLI measurement resources are shared between the one or more MAC-CE CLI reports, or each of the one or more CLI measurement resources is utilized by a different MAC-CE CLI report among the one or more MAC-CE CLI reports.

[0238] Aspect 47 is an apparatus for wireless communication at a network node, the apparatus comprising a memory and at least one processor, the at least one processor being coupled to the memory and being configured to perform a method according to any one of Aspects 26 to 46 based at least in part on information stored in the memory.

[0239] Aspect 48 is an apparatus for wireless communication, the apparatus comprising means for performing a method according to any one of aspects 26 to 46.

[0240] Aspect 49 is an apparatus according to aspect 47 or 48, the apparatus further comprising at least one transceiver configured to send a DCI for initiating a MAC-CE CLI report and to receive one or more MAC-CE CLI reports based on the DCI.

[0241] Aspect 50 is a non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform a method according to any one of aspects 26 to 46.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving downlink control information (DCI) for initiating a medium access control control element (MAC-CE) cross-link interference (CLI) report; and One or more MAC-CE CLI reports are sent based on the DCI.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: One or more configurations for the MAC-CE CLI reporting are received prior to the DCI, wherein the DCI activates the previously received configurations for the MAC-CE CLI reporting.

3. The apparatus of claim 1 , wherein the at least one processor is further configured to: Prior to sending the one or more MAC-CE CLI reports, one or more measurements are performed based on the DCI, wherein the one or more MAC-CE CLI reports include the one or more measurements.

4. The apparatus of claim 1 , wherein the at least one processor is further configured to: A second DCI for disabling the MAC-CE CLI reporting is received.

5. The apparatus of claim 1 , wherein the DCI is based on a radio network temporary identifier (RNTI) associated with the MAC-CE CLI report, wherein the RNTI is different from at least one other RNTI used for aperiodic channel state information (AP CSI) reporting, wherein a channel state information (CSI) request field in the DCI indicates that the MAC-CE CLI report is to be initiated, and wherein a trigger state configured in a radio resource control (RRC) includes a mapping to an L2 CLI reporting setting.

6. The apparatus of claim 1, wherein the DCI is based on a radio network temporary identifier (RNTI) that triggers the MAC-CE CLI reporting, wherein the RNTI is identical to at least one other RNTI used for semi-persistent channel state information (SP CSI) reporting.

7. The apparatus of claim 6, wherein the DCI is associated with a plurality of trigger states, wherein a subset of the plurality of trigger states is used for the MAC-CE CLI reporting.

8. The apparatus of claim 6, wherein the at least one processor is further configured to: A MAC-CE is received indicating a subset of a plurality of trigger states for use in the MAC-CE CLI reporting, wherein the DCI includes an indication of one or more of the plurality of trigger states for use in the MAC-CE CLI reporting.

9. The apparatus of claim 6, wherein one or more DCI field values ​​in the DCI indicate whether at least one of the MAC-CE CLI reporting or the SP CSI reporting is to be enabled.

10. The apparatus of claim 1, wherein the DCI is based on a radio network temporary identifier (RNTI) that triggers the MAC-CE CLI reporting, wherein the RNTI is identical to at least one other RNTI used for aperiodic channel state information (AP CSI) reporting.

11. The apparatus of claim 10, wherein the DCI is associated with a plurality of trigger states, wherein a subset of the plurality of trigger states is used for the MAC-CE CLI reporting.

12. The apparatus of claim 10, wherein the at least one processor is further configured to: A MAC-CE is received indicating that a subset of the plurality of codepoints in the DCI is used for the MAC-CE CLI report.

13. The apparatus of claim 1, wherein the at least one processor is further configured to: One or more CLI reporting configurations are received prior to receiving the DCI and via a radio resource control (RRC) communication, wherein the one or more MAC-CE CLI reports are based on the one or more CLI reporting configurations.

14. The apparatus of claim 13, wherein the at least one processor is further configured to: A second DCI for deactivating the first MAC-CE CLI reporting or for enabling the second MAC-CE CLI reporting is received.

15. The apparatus of claim 13, wherein the DCI comprises one or more fields comprising one or more parameters for the MAC-CE CLI report, and wherein the at least one processor is further configured to: The MAC-CE CLI report is updated based on the one or more parameters.

16. The apparatus of claim 15, wherein the one or more parameters include one or more of: Indication for wideband reporting or subband reporting, A subselection of one or more subbands to report on, Updates to the CLI reporting thresholds, or Quasi Co-location Type D (QCL-D) updates for measurement resources.

17. The apparatus of claim 15, wherein the one or more CLI report configurations comprise a list including the one or more parameters, wherein the DCI indicates a parameter of the one or more parameters, or the list indicates a default parameter.

18. The apparatus of claim 15, wherein updating the MAC-CECLI report based on the one or more parameters occurs at a time based on one of: a first number of symbols from the DCI, a second number of time slots from the time slot carrying the DCI, or Subcarrier spacing (SCS) and the type of the one or more parameters.

19. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving a MAC-CE for initiating one or more CLI measurement resources for the one or more MAC-CE CLI reports; and Measurement is performed on the one or more CLI measurement resources based on the MAC-CE used to initiate the one or more CLI measurement resources.

20. The apparatus of claim 1, wherein the DCI further enables one or more CLI measurement resources for the one or more MAC-CE CLI reports.

21. The apparatus of claim 20, wherein the one or more CLI measurement resources are shared between the one or more MAC-CE CLI reports, or each of the one or more CLI measurement resources is utilized by a different MAC-CE CLI report among the one or more MAC-CE CLI reports.

22. The apparatus according to claim 1, further comprising: At least one transceiver is coupled to the at least one processor and configured to receive the DCI and to send the one or more MAC-CE CLI reports.

23. A method of wireless communication at a user equipment (UE), the method comprising: receiving downlink control information (DCI) for initiating a medium access control control element (MAC-CE) cross-link interference (CLI) report; as well as One or more MAC-CE CLI reports are sent based on the DCI.

24. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: sending downlink control information (DCI) for initiating medium access control control element (MAC-CE) cross-link interference (CLI) reporting; and One or more MAC-CE CLI reports are received based on the DCI.

25. The apparatus of claim 24, wherein the at least one processor is further configured to: One or more configurations for the MAC-CE CLI report are sent prior to the DCI, wherein the DCI initiates the previously sent configurations for the MAC-CE CLI report.

26. The apparatus of claim 24, wherein one or more measurements are performed based on the DCI, wherein the one or more MAC-CE CLI reports include the one or more measurements.

27. The apparatus of claim 24, wherein the at least one processor is further configured to: A second DCI for disabling the MAC-CE CLI report is sent.

28. The apparatus of claim 24, wherein the DCI is based on a radio network temporary identifier (RNTI) associated with the MAC-CE CLI report, wherein the RNTI is different from at least one other RNTI used for aperiodic channel state information (AP CSI) reporting, wherein a channel state information (CSI) request field in the DCI indicates that the MAC-CE CLI report is to be initiated, and wherein a trigger state configured in a radio resource control (RRC) includes a mapping to an L2 CLI reporting setting.

29. The apparatus according to claim 24, further comprising: At least one transceiver is coupled to the at least one processor and configured to transmit the DCI and receive the one or more MAC-CE CLI reports.

30. A method for wireless communication at a network node, the method comprising: sending downlink control information (DCI) for initiating medium access control control element (MAC-CE) cross link interference (CLI) reporting; as well as One or more MAC-CE CLI reports are received based on the DCI.

Images