Enhanced cross-link interference and self-interference reporting

Abstract

The present disclosure provides systems, methods, and devices for wireless communication that support enhanced cross-link interference (CLI) and self-interference (SI) reporting. In a first aspect, an apparatus for wireless communication includes: at least one processor; and a memory coupled to the at least one processor. The at least one processor is configured to: generate cross-link interference information corresponding to cross-link interference (CLI); and transmitting CLI report information including the one or more CLI reports. Each CLI report corresponds to a respective serving cell of the one or more serving cells, and each CLI report includes a respective CLI information. Each CLI report of the one or more CLI reports includes a respective report type indication, and each respective report type indication indicates whether the CLI information includes actual CLI information or estimated CLI information. Other aspects and features are also claimed and described.

Description

Technical Field

[0001] Aspects of the present disclosure generally relate to wireless communication systems, and more particularly, to enhanced cross-link interference (CLI) and self-interference (SI) reporting. Some features enable and provide improved communication, including CLI and SI estimation and reporting for multiple cells.

[0002] Introduction

[0003] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcasting, etc. These wireless networks can be multi-access networks capable of supporting multiple users by sharing available network resources. Such networks can be multi-access networks that support communication for multiple users by sharing available network resources.

[0004] A wireless communication network may include several components. These components may include wireless communication devices such as a base station (or Node B) that can support communication for several user equipments (UEs). The UEs can communicate with the base station via a downlink and an uplink. The downlink (or forward link) refers to the communication link from the base station to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the base station.

[0005] The base station may send data and control information to the UE on the downlink, or receive data and control information from the UE on the uplink. On the downlink, the transmission from the base station may encounter interference caused by transmissions from neighboring base stations or other radio frequency (RF) transmitters. On the uplink, the transmission from the UE may encounter interference from other UEs communicating with neighboring base stations or from uplink transmissions of other wireless RF transmitters. Such interference may degrade the performance on both the downlink and the uplink.

[0006] Due to the continuous growth in the demand for mobile broadband access, with more UEs accessing remote wireless communication networks and more short-range wireless systems deployed in the community, the likelihood of interference and congested networks is also increasing. Research and development continue to advance wireless technologies to not only meet the growing demand for mobile broadband access, but also enhance and improve the user experience of mobile communication. Summary of the Invention

[0007] Some aspects of the present disclosure are summarized below to provide a basic understanding of the technologies discussed. This summary of the invention is not an exhaustive overview of all the expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor to depict the scope of any or all aspects of the present disclosure. The sole purpose of this summary of the invention is to present some concepts of one or more aspects of the present disclosure in a general form, as a prelude to the more detailed embodiments that are given later.

[0008] In one aspect of the present disclosure, a device for wireless communication includes: at least one processor; and a memory coupled to the at least one processor. The at least one processor is configured to: generate cross-link interference information corresponding to cross-link interference (CLI), where the cross-link interference corresponds to one or more serving cells; and transmit CLI report information including one or more CLI reports, where each CLI report in the one or more CLI reports corresponds to a respective serving cell in the one or more serving cells, where each CLI report in the one or more CLI reports includes respective CLI information in the CLI information corresponding to the respective serving cell corresponding to the respective CLI report, where each CLI report in the one or more CLI reports includes a respective report type indication, and where each respective report type indication indicates whether the respective CLI information included in the respective CLI report corresponding to the respective CLI information includes respective actual CLI information or respective estimated CLI information.

[0009] In another aspect of the present disclosure, a device for wireless communication includes: at least one processor; and a memory coupled to the at least one processor. The at least one processor is configured to: receive, from a second network node, CLI report information including one or more cross-link interference (CLI) reports, where each CLI report in the one or more CLI reports corresponds to a respective serving cell in the one or more serving cells, where each CLI report in the one or more CLI reports includes respective CLI information in the CLI information corresponding to the respective serving cell corresponding to the respective CLI report, where each CLI report in the one or more CLI reports includes a respective report type indication, and where each respective report type indication indicates whether the respective CLI information included in the respective CLI report corresponding to the respective CLI information includes respective actual CLI information or respective estimated CLI information; determine, based on the CLI report information, a remedial action configured to reduce the CLI for the second network node; and operate based on the remedial action.

[0010] In another aspect of the present disclosure, an apparatus for wireless communication includes: a transmitter; a receiver; at least one processor; and a memory coupled to the at least one processor. The at least one processor is configured to: generate self-interference information corresponding to self-interference (SI), where the self-interference corresponds to interference caused by the transmitter and received at the receiver; and transmit SI report information including one or more SI reports, where each SI report of the one or more SI reports includes corresponding SI information of the SI information, where each SI report of the one or more SI reports includes a corresponding report type indication, and where each corresponding report type indication indicates whether the corresponding SI information included in the corresponding SI report corresponding to the corresponding SI information includes corresponding actual SI information or corresponding estimated SI information.

[0011] In another aspect of the present disclosure, an apparatus for wireless communication includes: at least one processor; and a memory coupled to the at least one processor. The at least one processor is configured to: receive, from a second network node, SI report information including one or more SI reports, where each SI report of the one or more SI reports includes corresponding SI information of the SI information, where each SI report of the one or more SI reports includes a corresponding report type indication, and where each corresponding report type indication indicates whether the corresponding SI information included in the corresponding SI report corresponding to the corresponding SI information includes corresponding actual SI information or corresponding estimated SI information; determine, based on the SI report information, a remedial action configured to reduce SI for the second network node; and operate based on the remedial action.

[0012] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description below can be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructs do not depart from the scope of the appended claims. The characteristics (both the organization and the method of operation) of the concepts disclosed herein and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the drawings provided is for the purpose of illustration and description and is not a definition of the limitations of the claims.

[0013] While aspects and specific implementations are described herein by way of some examples, those skilled in the art will understand that additional specific implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, packaging arrangements. For example, aspects and / or uses can be implemented via integrated chips and other non-module-component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, a wide variety of applicability of the described innovations can occur. The scope of specific implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to the scope of aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical environments, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] A further understanding of the nature and advantages of the present disclosure can be realized by referring to the following drawings. In the drawings, like components or features may have the same reference numerals. Additionally, various components of the same type can be distinguished by adding a dash and a second label used to differentiate between like components after the reference numeral. If only the first reference numeral is used in the specification, the description applies to any one of the like components having the same first reference numeral, regardless of the second reference numeral.

[0015] Figure 1 is a block diagram illustrating details of an example wireless communication system in accordance with one or more aspects.

[0016] Figure 2 is a block diagram illustrating examples of a base station and a user equipment (UE) in accordance with one or more aspects.

[0017] Figure 3A is a diagram illustrating a first example of full-duplex operation.

[0018] Figure 3B is a diagram illustrating a second example of full-duplex operation.

[0019] Figure 3C It is a diagram of a third example of full - duplex operation.

[0020] Figure 3D It is a diagram of a fourth example of full - duplex operation.

[0021] Figure 3E It is a diagram of a fifth example of full - duplex operation.

[0022] Figure 3F It is a diagram of a sixth example of full - duplex operation.

[0023] Figure 4 It is a block diagram illustrating an example wireless communication system that supports enhanced cross - link interference (CLI) or self - interference (SI) reporting according to one or more aspects.

[0024] Figure 5 It is a flowchart illustrating an example process that supports enhanced channel CLI or SI reporting according to one or more aspects.

[0025] Figure 6 It is a block diagram illustrating an example of CLI or SI estimation according to one or more aspects.

[0026] Figures 7A to 10B They are block diagrams each illustrating an example CLI or SI reporting format according to one or more aspects.

[0027] Figure 11A It is a block diagram illustrating a sub - band configuration for CLI or SI estimation according to one or more aspects.

[0028] Figure 11B and Figure 11C It is a block diagram illustrating an example of CLI or SI estimation for a sub - band according to one or more aspects.

[0029] Figures 12A to 13B They are block diagrams each illustrating an example CLI or SI reporting format according to one or more aspects.

[0030] Figure 14 It is a flowchart illustrating an example process that supports enhanced CLI or SI reporting according to one or more aspects.

[0031] Figure 15 It is a flowchart illustrating an example process that supports enhanced CLI or SI reporting according to one or more aspects.

[0032] Figure 16 It is a block diagram of an example UE that supports enhanced CLI or SI reporting according to one or more aspects.

[0033] Figure 17It is a block diagram of an example base station that supports enhanced CLI or SI reports according to one or more aspects.

[0034] The same reference numerals and names in different figures represent the same elements. Detailed Description

[0035] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. On the contrary, the detailed description includes specific details for providing a thorough understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every instance and that in some instances, for the sake of clarity, well-known structures and components are shown in block diagram form.

[0036] The present disclosure generally relates to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various embodiments, the techniques and apparatuses may be used in wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth-generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems, or devices), and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0037] CDMA networks may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards.

[0038] For example, a TDMA network may implement radio technologies such as Global System for Mobile Communications (GSM). The 3rd Generation Partnership Project (3GPP) defines the standards for the GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network (RAN) (also known as GERAN). GERAN is the radio component of GSM / EDGE together with the network connecting base stations (such as the Ater and Abis interfaces) and base station controllers (the A interface, etc.). The radio access network represents the component of the GSM network through which telephone calls and packet data are routed from the Public Switched Telephone Network (PSTN) and the Internet to the subscriber's mobile phone (also known as the user terminal or user equipment (UE)) and from the subscriber's mobile phone to the PSTN and the Internet. The network of a mobile phone operator may include one or more GERANs, which may be coupled to the UTRAN in the case of a UMTS / GSM network. Additionally, the operator network may also include one or more LTE networks, or one or more other networks. Various different network types may use different Radio Access Technologies (RATs) and RANs.

[0039] An OFDMA network may implement radio technologies such as evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These radio technologies and standards are known or under development. For example, 3GPP is a cooperation among telecommunications standards bodies aimed at defining globally applicable third-generation (3G) mobile phone specifications. 3GPP LTE is a 3GPP initiative aimed at improving the UMTS mobile phone standard. 3GPP may define the specifications for next-generation mobile networks, mobile systems, and mobile devices. Certain aspects of the present disclosure may be described with reference to LTE, 4G, or 5G NR technologies; however, the description is not intended to be limited to a specific technology or application, and one or more aspects described with reference to one technology may be understood to apply to another technology. Additionally, one or more aspects of the present disclosure may relate to shared access to the radio spectrum between networks using different radio access technologies or radio air interfaces.

[0040] The 5G network is expected to have diverse deployments, diverse spectrums, and diverse services and devices enabled by a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for the 5G NR network, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to provide coverage (1) to massive Internet of Things (IoT) with ultra-high density (e.g., about 1M nodes / km 2 ), ultra-low complexity (e.g., about 10s bits per second), ultra-low power consumption (e.g., about 10+ year battery life), and deep coverage with the ability to reach challenging locations; (2) including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond (ms)), and users with a wide range of mobility or lack of mobility; and (3) providing enhanced mobile broadband with enhanced coverage including extremely high capacity (e.g., about 10 Tbps / km 2 ), extremely high data rates (e.g., multi-Gbps rates, 100+ Mbps user experience rate), and deep awareness with advanced discovery and optimization.

[0041] Devices, networks, and systems can be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is typically (interchangeably) referred to as the "sub-6 GHz" band. A similar naming issue sometimes occurs for FR2, where in documents and articles, FR2 is typically (interchangeably) referred to as the "millimeter wave" (mmWave) band, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunication Union (ITU) as the "mmWave" band.

[0042] Taking the above aspects into account, unless otherwise specifically stated, it should be understood that if used in this document, terms such as "sub-6 GHz" can generally represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if used in this document, terms such as "mmWave" can broadly represent frequencies that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

[0043] 5G NR devices, networks, and systems can be implemented to use waveform features based on optimized OFDM. These features can include scalable parameter sets and transmission time intervals (TTIs); a common flexible framework for efficiently multiplexing services and features using dynamic, low-latency time-division duplex (TDD) designs or frequency-division duplex (FDD) designs; and advanced radio technologies such as massive multiple-input multiple-output (MIMO), robust mmWave transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5G NR and the scaling of subcarrier spacing can efficiently address the operation of various services across different spectrums and different deployments. For example, in various outdoor and macro-coverage deployments with less than 3 GHz FDD or TDD implementations, the subcarrier spacing may occur at 15 kHz, such as over bandwidths of 1 MHz, 5 MHz, 10 MHz, 20 MHz, etc. For other various outdoor and small cell coverage deployments with TDD greater than 3 GHz, the subcarrier spacing may occur at 30 kHz over an 80 MHz / 100 MHz bandwidth. For other various indoor broadband implementations using TDD in the unlicensed portion of the 5 GHz band, the subcarrier spacing may occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments with transmission via mmWave components under TDD at 28 GHz, the subcarrier spacing can occur at 120 kHz over a 500 MHz bandwidth.

[0044] The scalable parameter sets of 5G NR contribute to scalable TTIs for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. The efficient multiplexing of long and short TTIs allows transmissions to start at symbol boundaries. 5G NR also anticipates self-contained integrated subframe designs, where uplink or downlink scheduling information, data, and acknowledgments are in the same subframe. Self-contained integrated subframes support communication in unlicensed or contention-based shared spectrums, and adaptive uplink or downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic demands.

[0045] For clarity, certain aspects of the devices and technologies may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in parts of the description below; however, the description is not intended to be limited to 5G applications.

[0046] In addition, it should be understood that in operation, a wireless communication network adapted according to the concepts herein may operate using any combination of licensed or unlicensed spectrum depending on load and availability. Accordingly, it will be apparent to those of ordinary skill in the art that the systems, apparatuses, and methods described herein may be applied to other communication systems and applications in addition to the specific examples provided.

[0047] While aspects and specific implementations are described herein by way of illustration of some examples, those skilled in the art will understand that additional specific implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, packaging arrangements. For example, a specific implementation or use may be implemented via an integrated chip or other non-module component-based device (e.g., an end-user device, a vehicle, a communication device, a computing device, an industrial device, a retail or point-of-purchase device, a medical device, an AI-enabled device, etc.). While some examples may or may not specifically be directed to a use case or application, a wide variety of applicability of the described innovations may occur. The scope of specific implementations can range from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems that incorporate one or more of the described aspects. In some practical environments, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described aspects. It is intended that the innovations described herein be implemented in a wide variety of specific implementations of different sizes, shapes, and configurations, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user devices, etc.

[0048] Figure 1 is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. The wireless network 100 may include, for example, a 5G wireless network. As recognized by those skilled in the art, Figure 1 the components that appear in are likely to have related corresponding components in other network arrangements, including, for example, cellular-style network arrangements as well as non-cellular-style network arrangements (e.g., device-to-device or peer-to-peer or ad-hoc network arrangements, etc.).

[0049] Figure 1The illustrated wireless network 100 includes a number of base stations 105 and other network entities. A base station can be a station that communicates with a UE and can also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, etc. Each base station 105 can provide communication coverage for a specific geographical area. In 3GPP, the term "cell" can refer to the specific geographical coverage area of a base station or the base station subsystem serving that coverage area, depending on the context in which the term is used. In a particular implementation of the wireless network 100 herein, the base stations 105 can be associated with the same operator or different operators (e.g., the wireless network 100 can include multiple operator wireless networks). Additionally, in a particular implementation of the wireless network 100 herein, the base stations 105 can use one or more frequencies in the same frequency as an adjacent cell (e.g., one or more frequency bands in licensed spectrum, unlicensed spectrum, or a combination thereof) to provide wireless communication. In some examples, a separate base station 105 or UE 115 can be operated by more than one network operation entity. In some other examples, each base station 105 and UE 115 can be operated by a single network operation entity.

[0050] The base station can provide communication coverage for macro cells or small cells (such as pico cells or femto cells) or other types of cells. A macro cell generally covers a relatively large geographical area (e.g., with a radius of several kilometers) and can allow unrestricted access by UEs having a service subscription with the network provider. A small cell (such as a pico cell) generally covers a relatively small geographical area and can allow unrestricted access by UEs having a service subscription with the network provider. A small cell (such as a femto cell) generally also covers a relatively small geographical area (e.g., a home) and can provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.) in addition to unrestricted access. The base station for a macro cell can be referred to as a macro base station. The base station for a small cell can be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a to 105c are macro base stations implemented using one of 3-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105a to 105c utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. A base station can support one or more (e.g., two, three, four, etc.) cells.

[0051] Wireless network 100 may support synchronous or asynchronous operations. For synchronous operations, the base stations may have similar frame timings, and transmissions from different base stations may be approximately aligned in time. For asynchronous operations, the base stations may have different frame timings, and transmissions from different base stations may not be aligned in time. In some cases, the network may be enabled or configured to handle dynamic switching between synchronous and asynchronous operations.

[0052] UEs 115 are scattered throughout the wireless network 100, and each UE can be stationary or mobile. It should be understood that although in the standards and specifications promulgated by 3GPP, mobile devices are generally referred to as UEs, such devices may additionally or otherwise be referred to by those skilled in the art as mobile stations (MSs), subscriber stations, mobile units, subscriber units, radio units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, cell phones, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle components, vehicle devices, or vehicle modules, or some other suitable term. In this document, a "mobile" device or UE does not necessarily have the ability to move and can be stationary. Some non-limiting examples of mobile devices may include specific implementations such as one or more UEs 115, including mobile phones, cellular phones, smartphones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, and personal digital assistants (PDAs). Mobile devices can additionally be IoT or "Internet of Everything" (IoE) devices, such as cars or other transportation vehicles, satellite radios, global positioning system (GPS) devices, global navigation satellite system (GNSS) devices, logistics controllers, drones, multi-rotor helicopters, quad-rotor helicopters, smart energy or security devices, solar panels or solar cell arrays, city lighting, tap water, or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smartwatches, health or fitness trackers, mammalian implantable devices, posture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, gaming consoles, etc.; and digital home or smart home devices, such as home audio, video, and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE can be a device that includes a universal integrated circuit card (UICC). In another aspect, a UE can be a device that does not include a UICC. In some aspects, a UE that does not include a UICC can also be referred to as an IoE device. Figure 1The illustrated specific implementations of UEs 115a through 115d are examples of mobile smart phone-type devices that access the wireless network 100. The UEs can also be machines specifically configured for connectivity communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. Figure 1 The illustrated UEs 115e through 115k are examples of various machines that access the wireless network 100 and are configured for communication.

[0053] A mobile device, such as UE 115, may be capable of communicating with any type of base station, whether a macro base station, a pico base station, a femto base station, a relay station, etc. In Figure 1 it, the communication link (represented as lightning) indicates a wireless transmission between the UE and the serving base station (which is the base station designated to serve the UE on the downlink or uplink), a desired transmission between base stations, and a backhaul transmission between base stations. The UE can operate as a base station or other network node in some scenarios. The backhaul communication between the base stations of the wireless network 100 can be carried out using wired or wireless communication links.

[0054] In operation, at the wireless network 100, base stations 105a through 105c use 3D beamforming and cooperative spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity, to serve UEs 115a and 115b. Macro base station 105d performs backhaul communication with base stations 105a through 105c and the small cell (base station 105f). Macro base station 105d also transmits multicast services subscribed to and received by UEs 115c and 115d. Such multicast services can include mobile TV or streaming video, or can include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or Gray alerts.

[0055] The wireless network 100 in a specific implementation supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as this UE 115e acting as a drone. The redundant communication links with the UE 115e include links from macro base stations 105d and 105e and small cell base station 105f. Other machine type devices such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device) can communicate directly with base stations such as small cell base station 105f and macro base station 105e through the wireless network 100, or communicate in a multi-hop configuration by communicating with another user device that relays its information to the network. For example, UE 115f communicates temperature measurement information to smart meter UE 115g, and then reports it to the network through small cell base station 105f. The wireless network 100 can also provide additional network efficiency through dynamic, low-latency TDD communication or low-latency FDD communication (such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i to 115k communicating with macro base station 105e).

[0056] Figure 2 is a block diagram illustrating examples of base station 105 and UE 115 according to one or more aspects. Base station 105 and UE 115 can be Figure 1 any one of the base stations in and one of the UEs in. For a restricted association scenario (as described above), base station 105 can be Figure 1 small cell base station 105f in, and UE 115 can be UE 115c or 115d operating in the service area of base station 105f, which will be included in the list of accessible UEs of small cell base station 105f for accessing small cell base station 105f. Base station 105 can also be some other type of base station. As Figure 2 shown, base station 105 can be equipped with antennas 234a to 234t, and UE 115 can be equipped with antennas 252a to 252r for facilitating wireless communication.

[0057] At base station 105, transmit processor 220 may receive data from data source 212 and receive control information from controller 240, such as a processor. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. Additionally, transmit processor 220 may process (e.g., encode and symbol map) the data and control information respectively to obtain data symbols and control symbols. Transmit processor 220 may also generate, for example, reference symbols for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), and cell-specific reference signals. Transmit (TX) MIMO processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, or reference symbols (if applicable), and may provide an output symbol stream to modulators (MOD) 232a through 232t. For example, the spatial processing performed on the data symbols, control symbols, or reference symbols may include precoding. Each modulator 232 may process the corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Additionally or alternatively, each modulator 232 may process the output sample stream (e.g., perform analog-to-digital conversion, amplification, filtering, and upconversion on it) to obtain a downlink signal. The downlink signals from modulators 232a through 232t may be transmitted via antennas 234a through 234t respectively.

[0058] At UE 115, antennas 252a through 252r may receive the downlink signals from base station 105, and may provide the received signals to demodulators (DEMOD) 254a through 254r respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the corresponding received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain the received symbols. MIMO detector 256 may obtain the received symbols from demodulators 254a through 254r, perform MIMO detection on the received symbols when needed, and provide the detected symbols. Receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide the decoded data for UE 115 to data sink 260, and provide the decoded control information to controller 280, such as a processor.

[0059] On the uplink, at the UE 115, the transmit processor 264 may receive and process data from the data source 262 (e.g., for the physical uplink shared channel (PUSCH)) and control information from the controller 280 (e.g., for the physical uplink control channel (PUCCH)). Additionally, the transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be pre-coded by the TX MIMO processor 266 when needed, further processed by the modulators 254a to 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 when needed, and further processed by the receive processor 238 to obtain the decoded data and control information transmitted by the UE 115. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller 240.

[0060] The controllers 240 and 280 may direct operations at the base station 105 and the UE 115, respectively. The controller 240 or other processors and modules at the base station 105 or the controller 280 or other processors and modules at the UE 115 may execute or direct the execution of various processes for the techniques described herein, such as executing or directing Figure 14 and Figure 15 the illustrated execution, or executing or directing the execution of other processes for the techniques described herein. The memories 242 and 282 may store data and program codes for the base station 105 and the UE 115, respectively. The scheduler 244 may schedule the UE for data transmission on the downlink or uplink.

[0061] In some cases, the UE 115 and the base station 105 may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, the UE 115 or the base station 105 may traditionally perform a medium sensing process to compete for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-talk or listen-before-transmit (LBT) process (such as an idle channel assessment (CCA)) before communication to determine whether the shared channel is available. In some embodiments, the CCA may include an energy detection process to determine whether there is any other active transmission. For example, a device may infer that a change in the received signal strength indicator (RSSI) of a power meter indicates that the channel is occupied. Specifically, signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. The CCA may also include the detection of a specific sequence indicating the use of the channel. For example, another device may transmit a specific preamble before transmitting a data sequence. In some cases, the LBT process may include a wireless node adjusting its own backoff window based on the amount of energy detected on the channel or the acknowledgment / negative acknowledgment (ACK / NACK) feedback for its own transmitted packets (as an indication of a collision).

[0062] The deployment of a communication system (such as a 5G New Radio (NR) system) may be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functionality may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc.) may be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

[0063] 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 also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0064] Base station type operations or network designs 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 configurations such as those 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.

[0065] Figure 3A , Figure 3B and Figure 3C An example of full-duplex communication mode is shown. Figure 3A In FIG. 1 , full-duplex base station and half-duplex UE operation are shown. Figure 3B In FIG. 1 , a full-duplex base station and a full-duplex UE operation are shown, and in FIG. Figure 3C , full-duplex UE operation (e.g., sub-band full-duplex (SBFD) UE operation) utilizing a full-duplex base station with multiple TRPs is shown. Full-duplex operation corresponds to sending and / or receiving data via multiple antennas at the same time. Half-duplex operation corresponds to sending or receiving data via a single antenna at a specific time.

[0066] Figure 3A , Figure 3B and Figure 3CIllustrates the interference caused by full-duplex operation. For illustration, external interference (e.g., channel-link interference or cross-link interference) and self-interference can be caused during full-duplex operation. External interference is caused by external sources such as nearby UEs or base stations. Self-interference is caused by the device itself performing multiple operations. Self-interference can be caused by leakage, such as when the transmission energy from the transmitting antenna is received directly or indirectly (e.g., through reflection) by the receiving antenna.

[0067] In Figure 3A , Figure 3B and Figure 3C , multiple TRPs are illustrated, such as a first TRP (TRP1) and a second TRP (TRP2). The first TRP and the second TRP can include or correspond to the same base station (such as the same gNB) or correspond to different base stations. In Figure 3A , Figure 3B and Figure 3C , the first TRP (TRP1) can operate in the same frequency band or different frequency bands. For example, the first TRP (TRP1) can operate in a first frequency band such as FR 4 or 60 GHz, and the second TRP (TRP2) can operate in a second frequency band such as FR 2 or 28 GHz.

[0068] Additionally, Figure 3A , Figure 3B and Figure 3C illustrate multiple UEs, such as a first UE (UE1) and a second UE (UE2). In some specific implementations, the UE is a full-duplex capable UE with a multi-antenna module. Figure 3A , Figure 3B and Figure 3C further depicts the signal paths between the TRP and the UE.

[0069] Referring to Figure 3A , Figure 3A illustrates an example diagram 300 for a first type of full-duplex communication. Referring to Figure 3A , diagram 300 illustrates two signal paths (beam paths) between the TRP and the UE and example interference. In the example illustrated in Figure 3A , the first TRP (TRP1) transmits downlink data to the first UE (UE1) via a first signal path, and the first TRP (TRP1) receives uplink data from the second UE (UE2) via a second signal path. The first TRP and the UE experience interference. For example, the first TRP experiences self-interference from simultaneous transmission and reception. Additionally, the device receives interference caused by other nearby devices. For example, the operation of the second TRP 2 can interfere with all other nodes such as Figure 3AInterference is caused at the illustrated first UE and first TRP. Additionally, the transmission of uplink data by the second UE can cause interference at the first UE (as shown in the figure) and at the second TRP. Operations at the second TRP can also cause interference at other devices such as at Figure 3A the illustrated first TRP.

[0070] Refer to Figure 3B , Figure 3B which illustrates an example diagram 310 for a second type of full-duplex communication. Refer to Figure 3B , diagram 310 illustrates three signal paths (beam paths) between a TRP and a UE and example interference. In Figure 3B the illustrated example, the first TRP (TRP1) transmits downlink data to the first UE (UE1) via the first signal path, and the first TRP (TRP1) receives uplink data from the first UE (UE1) via the second signal path. Additionally, the first TRP (TRP1) transmits downlink data to the second UE (UE2) via the third signal path. The first TRP experiences interference. For example, the first TRP experiences self-interference from simultaneous transmission and reception and from the operations of the second TRP and the UE. Additionally, other devices can receive interference caused by the operations of other nearby devices, as described in reference Figure 3A .

[0071] Refer to Figure 3C , Figure 3C which illustrates an example diagram 320 for a third type of full-duplex communication. Refer to Figure 3C , diagram 320 illustrates three signal paths (beam paths) between a TRP and a UE and example interference. In Figure 3C the illustrated example, the first TRP (TRP1) receives uplink data from the first UE (UE1) via the first signal path. The second TRP (TRP2) transmits downlink data to the first UE via the second signal path and transmits downlink data to the second UE (UE2) via the third signal path. These devices can receive interference caused by their own full-duplex operations and / or the operations of other nearby devices, as described in references Figure 3A and Figure 3B .

[0072] Figure 3D , Figure 3E and Figure 3F illustrate examples of full-duplex communication operations. In Figure 3D and Figure 3F in-band full-duplex (IBFD) operations are shown, and in Figure 3ESub-band full-duplex operation is shown. In-band full-duplex (IBFD) operation corresponds to transmitting and receiving on the same time and frequency resources. As Figure 3D shown in illustration 330 of Figure 3E and illustration 340 of Figure 3D and Figure 3E shown, the downlink and uplink resources share the same time and frequency resources. The downlink and uplink resources may completely or partially overlap, as shown in Figure 3F and Figure 3F respectively. Sub-band full-duplex operation, often referred to as frequency-division duplexing (FDD) or flexible duplexing, corresponds to simultaneously transmitting and receiving data on different frequency resources. As Figure 3F shown in illustration 350 of Figure 3F the downlink resources are separated from the uplink resources by a relatively "thin" guard band. For illustrative purposes, the guard band in Figure 3F is enlarged. In other embodiments, the guard band may also be omitted from the SBFD operation. In current wireless standard specifications, using different frequency domain resources for the uplink and downlink is the common practice to distinguish SBFD operation from paired spectrum operation (e.g., IBFD operation).

[0073] Although operating in full-duplex provides a greatly increased throughput, the increased operations of concurrent transmitting and receiving result in increased leakage and interference. Specifically, full-duplex operations (such as Figures 3A to 3F those full-duplex operations) can increase cross-link interference and self-interference, which can lead to reception errors and channel link failures. Current networks may employ cross-link interference and / or self-interference reporting to mitigate some of this interference and error. However, current methods are only able to provide the network with the configurations that are experiencing significant interference (e.g., specific cells and / or times), and are unable to indicate configurations that are not experiencing significant interference or predict configurations that will not experience significant interference in the future. Additionally, attempting to measure and report interference for all possible configurations will greatly increase the signaling overhead and reduce the battery life due to the UE physically measuring interference for additional channels and / or at additional times.

[0074] In the aspects described herein, virtual cross-link interference and self-interference determination and reporting are disclosed to enhance the interference information provided to the network and enable the network to perform meaningful remedial actions that can avoid or reduce interference, including internal and external interference caused by full-duplex operation. Virtual cross-link interference and self-interference determination include: estimating cross-link interference and self-interference in the frequency domain and / or time domain based on previous interference measurement results and / or estimates. This can greatly reduce the operations at the UE and reduce battery consumption by reducing the actual interference measurement operations. Additionally, virtual interference estimation for future time slots can enable the network to schedule future transmissions, which will reduce or avoid interference from full-duplex operations.

[0075] In addition, enhanced CLI and SI reporting formats are disclosed to enable efficient signaling of additional interference information and to provide an indication of which CLI measurements or reports are actual (e.g., measured) and which CLI measurements or reports are virtual (e.g., estimated or derived). Accordingly, the devices of the network can more efficiently participate in full-duplex operation while reducing interference. Consequently, network throughput can be increased and network overhead and errors can be reduced.

[0076] Figure 4 An example of a wireless communication system 400 that supports enhanced cross-link interference (CLI) reporting or self-interference (SI) reporting in accordance with aspects of the present disclosure is illustrated. In some examples, wireless communication system 400 may implement aspects of wireless communication system 100. For example, wireless communication system 400 may include a network (such as one or more network entities) and one or more UEs (such as UE 115 (also referred to as the first UE) and second UE 403). As Figure 4 illustrated by the example of, the network entity includes a corresponding base station, such as base station 105. Alternatively, the network entity may include or correspond to a different network device (e.g., not a base station). Enhanced CLI or SI reporting can reduce latency and increase throughput by reducing interference and reception errors and enabling more robust full-duplex operation. Accordingly, network and device performance can be improved.

[0077] Base station 105, UE 115, and second UE 403 may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band. Similar naming issues sometimes arise with respect to FR2, although different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" (mmWave) band, FR2 is generally (interchangeably) referred to as the "mmWave" band in various documents and articles.

[0078] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used herein, terms such as "below 6 GHz" can generally represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if used herein, terms such as "mmWave" can generally represent frequencies that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

[0079] It should be noted that for some data channels, the SCS can be equal to 15 kHz, 30 kHz, 60 kHz, or 120 kHz. The base station 105 and the UE 115 can be configured to communicate via one or more component carriers (CCs), such as the representative first CC 481, second CC 482, third CC 483, and fourth CC 484. Although four CCs are shown, this is for illustration only, and more or fewer than four CCs can be used. One or more CCs can be used to convey control channel transmissions, data channel transmissions, and / or sidelink channel transmissions.

[0080] Such transmissions can include a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), or a physical sidelink feedback channel (PSFCH). Such transmissions can be scheduled by an aperiodic grant and / or a periodic grant.

[0081] Each periodic grant can have a corresponding configuration, such as configuration parameters / settings. The periodic grant configuration can include configured grant (CG) configuration and settings. Additionally or alternatively, one or more periodic grants (e.g., their CGs) can have or be assigned a CC ID, such as an expected CC ID.

[0082] Each CC can have a corresponding configuration, such as configuration parameters / settings. The configuration can include bandwidth, bandwidth part, HARQ process, TCI state, RS, control channel resources, data channel resources, or a combination thereof. Additionally or alternatively, one or more CCs can have or be assigned a cell ID or a bandwidth part (BWP) ID. The cell ID can include a unique cell ID for the CC, a virtual cell ID, or a specific cell ID for a particular CC among multiple CCs. Additionally or alternatively, one or more CCs can have or be assigned a HARQ ID. Each CC can also have a corresponding management function, such as beam management or BWP switching functionality. In some specific implementations, two or more CCs are quasi-co-located such that the CCs have the same beam and / or the same symbol.

[0083] In some specific implementations, control information may be conveyed via base station 105, UE 115, and second UE 403. For example, control information may be conveyed using any of the following: MAC-CE transmission, RRC transmission, DCI (downlink control information) transmission, UCI (uplink control information) transmission, SCI (sidelink control information) transmission, another transmission, or a combination thereof.

[0084] UE 115 may include various components (e.g., structures, hardware components) for performing one or more functions described herein. For example, these components may include processor 402, memory 404, transmitter 410, receiver 412, encoder 413, decoder 414, CLI manager 415, CLI estimator 416, and antennas 252a through 252r. Processor 402 may be configured to execute instructions stored at memory 404 to perform the operations described herein. In some specific implementations, processor 402 includes or corresponds to controller / processor 280, and memory 404 includes or corresponds to memory 282. Memory 404 may also be configured to store CLI information data 406, CLI report information 408, reporting configuration information 442, setting data 444, or a combination thereof, as further described herein.

[0085] CLI information 406 includes or corresponds to data associated with or corresponding to a CLI. For example, CLI information 406 may include CLI value information such as RSRP value, RSSI value, SNR value, SINR value, confidence value, and aggregation value, or a combination thereof. As another example, CLI information 406 may include historical information or current information (e.g., non-historical information). Additionally or alternatively, CLI information 406 may include CLI information for multiple serving cells, multiple subbands, multiple BWPs, multiple CLI report IDs, or a combination thereof.

[0086] CLI report information 408 includes or corresponds to data associated with or corresponding to CLI reporting and report transmission. For example, CLI report information 408 may include or correspond to one or more CLI reports. A CLI report may include one or more indications or groups of information. By way of illustration, a CLI report may include an indication of an actual CLI report or a virtual CLI report, a bitmap indicating serving cells, a serving cell indication identifying one or more serving cells, a report type information indication of the type of CLI information included, the CLI information itself, one or more indications of the amount of reporting per cell or group, etc.

[0087] The reporting configuration information 442 includes or corresponds to data indicating or corresponding to the CLI reporting configuration. For example, the reporting configuration information 442 may include or correspond to reporting timing information, reporting type information, reporting format information, reporting history length, reporting resource information, reporting threshold information, per serving cell reporting information, bandwidth part information, subband information, or a combination thereof.

[0088] The setting data 444 includes or corresponds to data associated with enhanced CLI or SI reporting operations. The setting data 444 may include one or more types of enhanced CLI or SI reporting operation modes and / or thresholds or conditions for switching between enhanced CLI or SI reporting modes and / or their configurations. For example, the setting data 444 may have data indicating different thresholds and / or conditions for different enhanced CLI or SI reporting modes (such as fixed length field mode, variable length field mode, CLI-only mode, SI-only, CLI and SI mode, etc., or a combination thereof).

[0089] The UE 115 may also include self-interference (SI) information data, such as the interference caused by the device to itself. For example, the concurrent operation of the transmitter 410 may cause self-interference at the receiver 412. The SI information data may include or correspond to SI value information, such as RSRP value, RSSI value, SNR value, SINR value, confidence value, and aggregation value, or a combination thereof. As another example, the SI information data may include historical information or current information (e.g., non-historical information). Additionally or alternatively, the SI information data may include SI information for multiple serving cells, multiple subbands, multiple BWPs, multiple SI reporting IDs, or a combination thereof. In some specific implementations, the SI information data may be included in the CLI information 406.

[0090] The transmitter 410 is configured to send data to one or more other devices, while the receiver 412 is configured to receive data from one or more other devices. For example, the transmitter 410 may send data via a network (such as a wired network, a wireless network, or a combination thereof), and the receiver 412 may receive data via the network. For example, the UE 115 may be configured to send and / or receive data via: direct device-to-device connection, local area network (LAN), wide area network (WAN), modem-to-modem connection, Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the foregoing, or any other communication network now known or later developed that allows two or more electronic devices to communicate therein. In some specific implementations, the transmitter 410 and the receiver 412 may be replaced by a transceiver. Additionally or alternatively, the transmitter 410 or the receiver 412 may include or correspond to one or more components of the UE 115 described with reference to Figure 2 the foregoing.

[0091] The encoder 413 and the decoder 414 can be configured to encode and decode data for transmission. The CLI manager 415 (or CLI reporting manager) can be configured to perform CLI determination and reporting operations. For example, the CLI manager 415 can be configured to determine and / or measure CLI information for CLI reporting. By way of illustration, the CLI manager 415 can determine the actual CLI value and generate a CLI report based on the actual CLI value or the measured CLI value. The CLI manager 415 can also be configured to perform SI determination and reporting operations.

[0092] The CLI estimator 416 can be configured to perform CLI estimation operations such as CLI prediction, CLI extrapolation, and CLI interpolation. For example, the CLI estimator 416 can be configured to estimate CLI values in the time domain and the frequency domain. By way of illustration, the CLI estimator 416 can predict the CLI value of a future time slot based on the historical CLI value and / or the current CLI value of a specific serving cell. As another illustration, the CLI estimator 416 can predict the CLI value of the current time slot or a future time slot based on the historical CLI value and / or the current CLI value of different serving cells. The CLI estimator 416 can also be configured to perform SI estimation operations such as SI prediction, SI extrapolation, and SI interpolation.

[0093] The second UE 403 can include one or more elements similar to the UE 115. In some embodiments, the UE 115 and the second UE 403 are different types of UEs. For example, either UE can be of higher quality or have different operating constraints. By way of illustration, one of the UEs can have a larger form factor or be a current generation device and thus have more advanced capabilities and / or reduced battery constraints, higher processing constraints, etc.

[0094] The base station 105 includes a processor 430, a memory 432, a transmitter 434, a receiver 436, an encoder 437, a decoder 438, a CLI manager 439, a remediation manager 440, and antennas 234a through 234t. The processor 430 can be configured to execute instructions stored in the memory 432 to perform the operations described herein. In some embodiments, the processor 430 includes or corresponds to the controller / processor 240, and the memory 432 includes or corresponds to the memory 242. Similar to the UE 115 and as further described herein, the memory 432 can be configured to store CLI information data 406, CLI report data 408, reporting configuration information 442, setting data 444, or a combination thereof.

[0095] The transmitter 434 is configured to send data to one or more other devices, and the receiver 436 is configured to receive data from one or more other devices. For example, the transmitter 434 may send data via a network (such as a wired network, a wireless network, or a combination thereof), and the receiver 436 may receive data via the network. For example, the UE and / or the base station 105 may be configured to send and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network that allows two or more electronic devices to communicate and that is known now or developed later. In some specific embodiments, the transmitter 434 and the receiver 436 may be replaced by a transceiver. Additionally or alternatively, the transmitter 434 or the receiver 436 may include or correspond to one or more components of the UE 115 described with reference to Figure 2 as described.

[0096] The encoder 437 and the decoder 438 may include the same functionality as described with reference to the encoder 413 and the decoder 414, respectively. The CLI manager 439 may include similar functionality as described with reference to the CLI manager 415. The remediation manager 440 may be configured to determine CLI remediation operations and perform CLI and / or SI remediation operations. For example, the remediation manager 440 may be configured to determine a remediation action for a base station device or a UE. As another example, the remediation manager 440 may be configured to provide a remediation determination to one or more other devices.

[0097] During operation of the wireless communication system 400, the network (e.g., the base station 105) may determine that the UE 115 has an enhanced CLI reporting capability. For example, the UE 115 may send a message 448 that includes an improved enhanced CLI reporting indicator 490 (e.g., an enhanced CLI reporting capability indicator). The indicator 490 may indicate the enhanced CLI reporting capability for one or more communication modes (such as downlink, uplink, etc.). In some specific embodiments, a network entity (e.g., the base station 105) transmits control information to indicate to the UE 115 that enhanced CLI reporting operations and / or a specific type of enhanced CLI reporting operation will be used. For example, in some specific embodiments, a configuration transmission 450 is sent to the UE 115. The configuration transmission 450 may include or indicate settings for using enhanced CLI reporting operations or for adjusting or implementing a specific type of enhanced CLI reporting operation. For example, the configuration transmission 450 may include CLI reporting information 408, reporting configuration information 442 (as indicated by the example of Figure 4 ), set data 444, or any combination thereof.

[0098] During operation, the devices of the wireless communication system 400 perform enhanced CLI reporting operations. For example, the network and the UE 115 may have a full-duplex mode of enhanced CLI reporting (e.g., SBFD mode) to exchange transmissions via uplink and / or downlink communications, as Figure 4 illustrated by the example of. This enhanced CLI reporting enables the devices to adjust full-duplex operation to reduce CLI. In addition to actual CLI reporting, enhanced CLI reporting may also be achieved by reporting virtual CLI reports (estimated CLI reports). These estimated CLI reports may provide additional information for future time slots and other serving cells. Additionally, enhanced CLI reporting may be achieved by reporting an indication for virtual CLI reports and actual CLI reports to distinguish such CLI reports. Such an indication may allow for greater flexibility in CLI reporting and reporting multiple CLI reports and types in one transmission.

[0099] In Figure 4 the example of, the devices of the network may participate in one or more first transmissions 452. For example, one or more of the base station 105, the UE 115, and / or the second UE 403 may each transmit a transmission of the first transmission 452. In some embodiments, the UE 115 is monitoring one or more of the first transmissions 452. The operation of the devices of the network may cause the devices of the network (such as the UE 115) to experience CLI. In Figure 4 the example of, the UE 115 experiences CLI caused by the first transmission. The UE 115 determines CLI information 406 based on one or more of the first transmissions 452. The first transmission 452 may include or correspond to a broadcast message, an RRC message, a DCI transmission, a PDCCH, a PDSCH, a PUCCH, a PUSCH, an SCI, an SL-MAC-CE, or an SL-RRC message.

[0100] The UE 115 generates CLI report information 408 based on the CLI information 406, and the UE 115 sends the CLI report information 408 to the base station 105 in a CLI report transmission 454. For example, the UE 115 reports multiple CLI reports in the CLI report transmission 454, each CLI report corresponding to the CLI information 406. By way of illustration, the UE 115 may report one or more CLI reports per serving cell, one or more actual CLI reports, one or more virtual CLI reports, etc. The UE 115 may determine the configuration or layout of the CLI report transmission 454 based on the reporting configuration information 442. Figures 7A to 13B illustrates an exemplary configuration or layout of the CLI report transmission 454.

[0101] Base station 105 receives CLI report transmission 454. The base station 105 (such as its remediation manager 440) can determine one or more remediation actions based on the CLI report information 408 of the CLI report transmission 454. For example, the base station 105 can parse the CLI report transmission 454 based on the CLI report configuration indicated by the configuration transmission 450 to determine the CLI information of the CLI report information 408 or the CLI information indicated by the CLI report information 406. Then, the base station 105 can generate remediation information based on the CLI information 406 or the CLI report information 408. For illustration, the base station 105 can send a remediation indication 456 including a remediation action or remediation information. The remediation indication 456 can be sent to another base station, UE 115, or second UE 403.

[0102] Then, the device receiving the remediation indication 456 can adjust the settings or configuration to reduce the CLI at the UE 115. For example, the UE 115 receives the remediation indication 456 and can adjust the configured grants, time slot format, BWP, etc. to avoid CLI. As another example, the UE 115 can adjust the transmit power or beam parameters to reduce the CLI. Additionally or alternatively, other devices can adjust the configuration or settings to reduce the CLI at the UE 115. For example, the second UE 403 can adjust one or more of the configurations or settings discussed above to reduce the CLI at the UE 115 or the CLI experienced by that UE. Although Figure 4 the examples are for CLI, in other embodiments, the device can additionally or alternatively report and remediate SI. The SI can be reported together with the CLI (e.g., in the same report or transmission) or reported outside of the CLI (e.g., in another report or transmission).

[0103] Accordingly, the network (e.g., base station 105, UE 115, and second UE 403) can be able to more efficiently and effectively utilize the available spectrum by resolving the problems caused by CLI or SI resulting from full-duplex operation. Improved spectrum utilization through enhanced CLI or SI reporting can increase throughput and reduce latency, which can lead to reduced link failures. Accordingly, network performance and experience can be improved due to increased speed and reduced failures.

[0104] Refer to Figure 5 , Figure 5 which is a timing diagram 500 of a wireless communication system supporting enhanced CLI or SI reporting according to one or more aspects. Figure 5 The example of

[0105] Figure 5 corresponds to an example of enhanced CLI or SI reporting for non-periodic or periodic CLI or SI reporting operations. Figure 1 、 Figure 2 andFigure 4 Devices similar to the described device, such as UE 115, a second UE 503 (e.g., second UE 403), and network entities (e.g., base station 105). Figure 5 The device may include one or more of the components described as Figure 2 and Figure 4 In Figure 5 these devices may utilize antennas 252a to 252r, a transmitter 410, a receiver 412, an encoder 413, and / or a decoder 414, or may utilize antennas 234a to 234t, a transmitter 434, a receiver 436, an encoder 437, and / or a decoder 438, to convey and receive transmissions according to the maximum number of per-band resource elements. In some specific implementations, the network entity may include or correspond to a single base station (e.g., base station 105), multiple base stations, or multiple TRPs in any combination thereof.

[0106] At 510, base station 105 sends CLI configuration information to UE 115. For example, base station 105 may send a signaling transmission including the CLI configuration information. As Figure 5 illustrated by the example of

[0107] base station 105 sends RRC signaling (e.g., an RRC transmission or message) including CLI report configuration information to UE 115 and optionally to a second UE 503. Figure 4 As described with reference to Figures 7A to 13B the CLI configuration information (e.g., report configuration information 442) may include or indicate a CLI report setting and indicate a CLI report format, such as the CLI report format depicted as

[0108] For example, the CLI configuration information may indicate a CLI report transmission type, serving cell information, sub-band cell information, CLI report condition or threshold information, bandwidth part information (e.g., type or size), CLI report type, CLI report timing, or a combination thereof. As another example, the CLI configuration information may include information about CLI determination or CLI estimation. By way of illustration, the CLI configuration information may indicate CLI measurement resources. The downlink transmission may include or correspond to an RRC message, a MAC-CE, DCI, PDCCH, or PDSCH.

[0109] At 515, the UE and the second UE 503 may transmit or receive transmissions, such as operating in a full-duplex mode. For example, the second UE 503 may transmit transmissions to the UE 115 and / or the base station 104. The UE 115 may also transmit transmissions during this time. Additionally or alternatively, the UE 115 may receive energy from other transmissions while monitoring transmissions from the second UE 503, or may receive energy from transmissions from the second UE 503 while monitoring transmissions from the base station 105. Accordingly, the UE 115 may experience a CLI from the transmission at 510 or a CLI associated with that transmission, which is from the second UE 503.

[0110] At 520, the UE 115 may determine actual CLI information. For example, the UE 115 may determine CLI measurement resources and determine (e.g., measure) the CLI for the CLI measurement resources to generate an actual CLI value, a measured CLI value, or a non-historical CLI value. The actual CLI value may include or correspond to the measured CLI value of the actually received transmission and may be referred to as a current value or a non-historical value. As will be described in more detail below, the UE 115 may determine an indication of the CLI measurement resources or resources to be measured or receive such an indication from the network (such as the base station 105).

[0111] The UE 115 may determine actual CLI information based on non-historical CLI information that only corresponds to the respective serving cell corresponding to the respective CLI measurement. As an illustrative example, the UE 115 may measure the CLI received signal strength indicator (CLI-RSSI) for a specific serving cell in a specific time slot and generate an actual CLI-RSSI for that specific time slot and that specific serving cell based on the measured CLI-RSSI. Additionally or alternatively, the UE 115 may determine or measure the CLI based on transmission power information for transmission and coupling loss (CL) information.

[0112] At 525, the UE 115 may determine estimated CLI information. For example, the UE 115 may determine or estimate the CLI based on the actual CLI information and optionally based on other actual CLI information or estimated CLI information. The estimated CLI indication may include or correspond to a predicted CLI indication in the time domain or an extrapolated or interpolated CLI indication in the frequency domain. The estimated CLI indication is not merely generated based on the measured CLI. As will be described in more detail below, the UE 115 may determine or receive from the network an indication of the LCI to be predicted or estimated.

[0113] The UE 115 may determine or estimate virtual CLI information based on at least one of the following: historical CLI information corresponding only to the respective serving cell corresponding to the respective measurement, or historical CLI information or non-historical CLI information corresponding to one or more serving cells different from the respective serving cell corresponding to the measurement. As an illustrative example, the UE 115 may measure the CLI received signal strength indicator (CLI-RSSI) in a particular time slot for a particular serving cell and predict the CLI-RSSI in a future time slot for that particular serving cell based on the measured CLI-RSSI to generate a second determined CLI. As another illustrative example, the UE 115 may measure the CLI received signal strength indicator (CLI-RSSI) in one or more serving cells and extrapolate or interpolate the measured CLI-RSSI to one or more other serving cells to generate a second determined CLI, where the CLI report information includes the second determined CLI. Although examples were given above for RSSI, in other specific implementations, the UE 115 may determine or measure RSRP, SNR, SINR, confidence values, etc. or combinations thereof.

[0114] The UE 115 may determine the resources (also referred to as measurement resources) for measuring the CLI based on UE determination or network indication. In a specific implementation where the network indicates the resources, the UE 115 may receive CLI configuration information indicating the CLI measurement resources, where the CLI measurement is performed during at least one of the CLI measurement resources in the CLI measurement resources. For example, the CLI configuration information received at 510 may indicate or identify the resources for use by the UE 115. Alternatively, in a specific implementation where the UE 115 determines the resources, the UE 115 may determine one or more CLI measurement resources based on one or more CLI measurement conditions. Optionally, the UE 115 may determine whether to estimate the CLI value for an additional serving cell or time slot based on a window of past measurements or a threshold amount of past measurements. In some such specific implementations, the UE 115 may determine the window of past measurements based on a CLI measurement timer.

[0115] At 530, the UE 115 sends the CLI report information to the base station 105. For example, the CLI manager 415 of the UE 115 may generate multiple CLI reports and include these CLI reports in the CLI report transmission, and the UE 115 may send the CLI report transmission to the base station 104 in an uplink transmission. The CLI report transmission may include one report per serving cell or multiple reports per serving cell. Alternatively, the CLI report transmission may include one CLI report.

[0116] In some specific implementations, UE 115 may determine whether to report the estimated CLI value based on a threshold confidence level of the estimated CLI value. For example, in response to determining that the confidence level of the estimated CLI value is greater than or equal to the threshold confidence level, UE 115 may generate CLI report information based on the estimated CLI, such as including a specific estimated CLI value / report in the CLI report information. UE 115 may suppress including or excluding one or more specific estimated CLI values / reports that do not meet the threshold confidence level in the CLI report information.

[0117] At 535, the base station 105 determines remediation information based on the CLI report transmission received at 530. For example, the base station 105 may receive and parse the CLI report transmission to determine or identify the CLI report and its CLI information. The base station 105 (such as its remediation manager 440) may identify one or more CLI values to be remediated, such as based on a threshold or other conditions, and may determine one or more actions to reduce the CLI for the identified CLI values. The base station 105 may generate remediation information that indicates such actions to reduce the CLI for the identified CLI values.

[0118] At 540, the base station 105 may send the remediation information to the UE 115. For example, the base station 105 may send remediation information indicating a specific configuration change for the UE 115. By way of illustration, the base station 105 may send DCI, MAC CE, or RRC signaling to indicate a configuration change for the UE 115. The change may include a configuration adjustment or setting modification as described in reference Figure 4 As an illustrative, non-limiting example, the change may include a change in the slot setting (e.g., slot format), transmission timing (e.g., configured grant timing, dynamic grant timing, etc.), transmission power, beam information, or a combination thereof.

[0119] At 545, the base station 105 may send the remediation information to the second UE 503. For example, the base station 105 may send the remediation information or a second remediation information to the second UE 503. By way of illustration, the base station 105 may send the same remediation information to the second UE 503 as that sent to the first UE 105, or may send different remediation information to the second UE 503. After receiving the remediation information, one or more of the UEs may modify their operations or transmit or receive parameters to reduce the CLI for the UE 115.

[0120] Optionally, base station 105 may perform one or more additional operations. For example, instead of sending a remediation indication including remediation information, base station 105 may adjust the configuration or settings of base station 105. Alternatively, base station 105 may send a remediation indication including remediation information to another base station (such as a base station of another cell or cell group). Then, this other base station may relay the remediation indication (or its remediation information) or send a second remediation indication based on the received remediation indication. For example, another base station may send a remediation indication to UEs of another cell group to reduce the CLI caused by the inter-UE CLI (inter-cell CLI) from another cell group.

[0121] Although examples have been described with reference to CLI Figure 5 in other embodiments, the device may report CLI and SI or only report SI. For example, UE 115 may determine one or more actual SI values and / or virtual SI values, and base station 105 may determine a remediation action to reduce the SI at UE 115. Accordingly, in Figure 5 's example, the devices of the network may be able to have a more flexible utilization of the full-duplex time slot configuration by using enhanced CLI or SI reporting.

[0122] Reference Figure 6 , Figure 6 is a block diagram 600 illustrating an example of CLI estimation according to one or more aspects. Figure 6 's example may include or correspond to an example of CLI prediction, CLI extrapolation, or interpolation performed by a UE (such as UE 115). As described above, the estimation of CLI may include: the estimation of CLI based on non-historical CLI information corresponding only to the corresponding serving cell corresponding to the corresponding CLI report; historical CLI information corresponding only to the corresponding serving cell corresponding to the corresponding CLI report; or historical CLI information or non-historical CLI information corresponding to one or more serving cells different from the corresponding serving cell corresponding to the corresponding CLI report.

[0123] In Figure 6 's example, block diagram 600 depicts the transmit bands (also referred to as frequency bands) for two component carriers (also referred to as serving cells) over four time periods. These two component carriers include a first component carrier 612 (CC1) and a second component carrier 614 (CC0). In Figure 6 's example, these four time periods include a first time slot 622, a second time slot 624, a third time slot 626, and a fourth time slot 628.

[0124] Each frequency band may have multiple sub-bands. In Figure 6In the example, the transmission band (such as its bandwidth) includes an uplink sub-band 634, a first downlink sub-band 632, and a second downlink sub-band 636 located between two downlink sub-bands. Although sub-bands 632 to 636 are shown as covering the frequency band of the first component carrier 612 (CC1) for the first time slot 622, in Figure 6 each time slot has the same sub-band configuration.

[0125] During operation, the device can determine the actual CLI measurement for a specific channel (such as a specific component carrier) and for a specific time (such as a specific time slot). As Figure 6 illustrated in the example, the device determines (such as measures) the CLI for two downlink sub-bands (632 and 636) of the first component carrier 612 during the second time slot 624. The measurement of the CLI generates an actual CLI measurement result, and the actual CLI value can be determined as the actual CLI measurement result or based on the actual CLI measurement result. For illustration, the device determines a first actual CLI 642 (non-historical CLI) and a second actual CLI 644 based on the measurement results of two downlink sub-bands (632 and 636) of the first component carrier 612 during the second time slot 624.

[0126] In some specific implementations, the device can determine (such as estimate or predict) the CLI measurement result for other combinations of carriers and time slots. As Figure 6 illustrated in the example, the device determines (such as estimates or predicts) multiple virtual CLIs based on historical CLI information or non-historical CLI information for another component carrier. For example, the device can estimate a first virtual CLI 652 for the first downlink sub-band 632 and the fourth time slot 628 based on the first actual CLI 642 for the second time slot 624, and the device can estimate a second virtual CLI 654 for the third downlink sub-band 636 and the fourth time slot 628 based on the second actual CLI 644 for the second time slot 624. The generation of the first virtual CLI 652 and the second virtual CLI 654 can be referred to as predicted CLI or estimated CLI in the time domain. That is, the virtual CLI is estimated based on historical measurement results or previous measurement results for an earlier time slot on the same component carrier.

[0127] As another example, the device may estimate a third virtual CLI 662 for a corresponding first downlink subband of a second component carrier 614 during a second time slot 624 based on a first actual CLI 642, and the device may estimate a fourth virtual CLI 664 for a corresponding second downlink subband of the second component carrier 614 during the second time slot 624 based on a second actual CLI 642. The generation of the third virtual CLI 662 and the fourth virtual CLI 664 may be referred to as extrapolating or interpolating the CLI or estimating the CLI in the frequency domain. That is, virtual CLIs are estimated based on non-historical measurement results or current measurement results on different component carriers.

[0128] In some such embodiments, virtual CLIs may be generated based on additional CLIs. By way of illustration, virtual CLIs may be determined based on historical CLIs for different component carriers or based on both historical CLIs for the same component carrier and current CLIs for different component carriers. For example, a fifth virtual CLI 672 may be determined based on a first virtual CLI 652, and a sixth virtual CLI 674 may be determined based on a second virtual CLI 654.

[0129] Although examples have been described with reference to CLIs Figure 6 in other embodiments, the device may estimate SI in a manner similar to the techniques described for CLIs. For example, UE 115 may determine predicted or extrapolated / interpolated virtual SI values in the time domain and / or the frequency domain.

[0130] Figures 7A to 13B Examples illustrate different formats for reporting CLI report information. Figures 7A to 13B Each illustrates a block diagram of an exemplary CLI report format structure that illustrates the layout of different bit groups (e.g., fields) including CLI report information. As an illustrative example, two different formats for indicating or identifying the serving cell associated with a CLI report of CLI information are illustrated. As Figure 7A illustrated, the first format includes a bitmap that identifies the serving cell, such as by association with the configured serving cells, as indicated by a list of serving cells configured for the device. As Figure 7B illustrated, the second format includes one or more serving cell identifier indications (e.g., serving cell identifier (ID) fields) that are used to indicate or identify the serving cell associated with a CLI report of CLI information.

[0131] Reference Figure 7A, illustrates a first example 700 of a CLI report format for reporting or indicating CLI report information. In the first example 700, the CLI report format includes seven (7) eight (8)-bit octets (e.g., rows). Bit markers 716 are also illustrated with the CLI report format in Figure 7A for identifying the bits of the octets and indicating the amount of bits for each octet or field.

[0132] The first octet of the CLI report format includes a bitmap 720 for indicating which serving cells have a CLI report in the CLI report information, where each corresponding bit of the bitmap 720 indicates whether the CLI report includes a corresponding report corresponding to the corresponding serving cell in one or more serving cells. As Figure 7A illustrated by the example of, the bitmap 720 may include or correspond to a Ci field. The Ci field may be used to indicate the presence of a CLI report and additional octets and fields. For example, for a corresponding serving cell, the first bit value may indicate the inclusion of a CLI report, and the second bit value may indicate the exclusion of a CLI report. Although in Figure 7A the example of the Ci field is 7 bits long, in other examples the Ci field may be longer or shorter.

[0133] The CLI report format can include or indicate multiple CLI and / or SI reports, such as one CLI report and / or one SI report for each serving cell identified in the bitmap 720. In a specific implementation where SI is included and SI is separate from the CLI, a second bitmap similar to the bitmap 720 may be included for indicating the presence of an SI report.

[0134] In Figure 7A the example of, the CLI report format supports one CLI report per serving cell. In other examples, such as Figures 9A to 10B the example of, other CLI report formats may support multiple CLI reports per serving cell. Each CLI report may include an octet for reporting a CLI value and one or more groups for reporting a CLI report type. For example, rows two and three (octets two and three) correspond to a first CLI report for a first serving cell 742 (such as C1). The octet for reporting the CLI value may include or correspond to a CLI value field 730 (e.g., a CLI level field).

[0135] The first CLI report includes a first report type indication and a second report type indication. The first report type indication (e.g., a virtual indication bit or V bit) indicates whether the CLI information includes actual CLI information or virtual (e.g., estimated) CLI information. As Figure 7AAs illustrated by the example of, the CLI report format includes a first report type indication field 722 for indicating a first report type indication (e.g., V-bit indicator) and a second report type indication field 728 for indicating a second report type indication. The second report type indication (e.g., CLI report ID field) indicates the report type or report identifier (ID). In some specific implementations, the CLI report format includes one or more reserved bits or reserved bit 726.

[0136] Reference Figure 7B , illustrates a second example 702 of the CLI report format, which is used to report or indicate CLI report information. In the second example 702, the CLI report format includes six (6) eight (8)-bit octets (e.g., rows). Bit markers 716 are also illustrated together with the CLI report format in Figure 7B to identify the bits of the octets and indicate the amount of bits of each octet or field.

[0137] Compared with Figure 7A the first example 700 of, Figure 7B the second example 702 of includes many of the same indications and fields as Figure 7A the first example 700 of. For example, the second example 702 includes a virtual report indication or an actual report indication (e.g., 722), a CLI report type indication (e.g., 728), a CLI value indication (e.g., 730), reserved bits (e.g., 724), etc. However, Figure 7B the second example 702 of does not include the bitmap 720. Instead, Figure 7B the second example 702 of includes one or more extension indications and one or more indications of the serving cell identifier, such as the serving cell identifier field 734. By way of illustration, the CLI report format of the second example 702 explicitly includes or identifies the serving cell of the CLI report included in the CLI report information, and the extension indication 732 (e.g., Ec bit or field) is configured to indicate whether an additional CLI report is included. For example, the first bit value (e.g., 1) indicates that at least one additional CLI report is included, and the second bit value (e.g., 0) indicates that no additional CLI report is included or that the current CLI report is the last CLI report in the CLI report information.

[0138] In some specific implementations, the CLI report format of the second example 702 also includes a bandwidth part (BWP) indication, such as a BWP identifier indication. As Figure 7BAs illustrated by the example of, the CLI report format includes a BWP indication for each CLI report, and the BWP indication is included in the BWP ID field 736, which is in the same octet as the serving cell identifier indication and field. The BWP indication may indicate or identify the BWP associated with the CLI report and value. The BWP field enables the UE to report CLI values for different BWPs.

[0139] Reference Figure 8A and Figure 8B , illustrate an example CLI report format that supports a single report ID configuration. In Figure 8A , a single CLI report ID is used and the single CLI report ID is indicated by separate signaling (such as pre-configuration). In Figure 8B , the CLI report format includes a single CLI report ID indication that is used to indicate the report ID configuration for all serving cells or all CLI reports.

[0140] In Figure 8A , a third example 800 of the CLI report format is illustrated. The third example 800 depicts a CLI report format that is reporting CLI reports for three serving cells (a first CLI report for a first serving cell, a second CLI report for a second serving cell, and a third CLI report for a third serving cell). For illustration, the bitmap 720 of the third example indicates that the CLI report information includes CLI reports for the first serving cell (C1), the third serving cell (C3), and the fourth serving cell (C4). Specifically, the third example 800 includes a first CLI report for the first serving cell, a second CLI report for the third serving cell, and a third CLI report for the fourth serving cell. The first CLI report has a first CLI value indicated by the first CLI value field 730A, the second CLI report has a second CLI value indicated by the second CLI value field 730B, and the third CLI report has a third CLI value indicated by the third CLI value field 730C.

[0141] Each of the first CLI report, the second CLI report, and the third CLI report has the same CLI report type. However, the CLI report type is static and pre-configured by the network or area in the third example 800. For illustration, the CLI report format does not include a CLI report ID indication (e.g., a CLI report ID field) that indicates the CLI report type for each CLI report included in the CLI report information, as in Figure 7A and Figure 7BAs in the previous example. Instead, the network or device manufacturer may indicate the CLI report type to the UE before generating and sending the CLI report. Such a format lacking an explicit indication of the CLI report type can greatly reduce CLI overhead. The network may still change the CLI report type, or the UE may cycle through the various CLI report types in subsequent CLI reports.

[0142] In Figure 8B a fourth example 802 of a CLI report format is illustrated. The fourth example 802 depicts a CLI report format that is reporting CLI reports for three serving cells (a first CLI report for a first serving cell, a second CLI report for a third serving cell, and a third CLI report for a fourth serving cell). Similar to Figure 8A the third example 800, each of the first CLI report, the second CLI report, and the third CLI report has the same CLI report type. However, Figure 8B the fourth example 802 of the CLI report format includes an indication of the CLI report type. By way of illustration, the second octet of the CLI report format includes a single CLI report ID indication (e.g., a CLI report ID field) that indicates the CLI report type for each CLI report included in the CLI report information. Compared to the static CLI report type of Figure 8A the third example 800, Figure 8B the fourth example 802 enables dynamic adjustment of the CLI report type and provides flexibility to the UE in reporting CLI (and / or SI).

[0143] Although Figure 8A and Figure 8B the example CLI report formats include a bitmap for indicating serving cell information or indication, in other embodiments, the CLI report format may utilize Figure 7B the serving cell identifier indication without having a CLI report ID indication as in Figure 8A or without having a single CLI report ID indication as in Figure 8B .

[0144] Referring to Figure 9A and Figure 9B and Figure 10A and Figure 10B example CLI report formats that support multiple CLI reports per serving cell are illustrated. Figure 9A and Figure 9B have a CLI report format similar to Figure 7A the first example 700, and Figure 10A and Figure 10B have a CLI report format similar to Figure 7BCLI report format for the second example 702. For example, Figure 9A and Figure 9B uses a bitmap to indicate serving cells and which serving cells have CLI reports, and Figure 10A and Figure 10B uses serving cell identifiers to indicate serving cells.

[0145] In Figure 9A an example is illustrated of a fifth example 900 of the CLI report format. The fifth example 900 depicts a CLI report format that uses a bitmap for serving cell indication and has a structure similar to that of Figure 7A the first example 700 of Figure 9A However, in Figure 9A the fifth example 900 of Figure 7A the CLI report format also includes one or more termination indications. Specifically, in

[0146] the example of Figure 9B a CLI report format includes a termination bit 912 for each CLI report. Compared with Figure 9A the first example 700 of Figure 9B the termination bit 912 utilizes or replaces one of the previously reserved bits in the octet that includes the CLI report ID field. Based on the value of the termination bit 912, the CLI report format includes a second octet for the corresponding CLI report for the serving cell, and the second octet includes CLI value information (e.g., CLI level field).

[0147] For illustration, Figure 9B the CLI report format of Figure 9BIn the example, the value of the first termination bit 912A is 0, and thus the first termination bit 912A indicates a negative termination indication and includes at least one additional CLI report for the first serving cell. The value of the second termination bit 912B is 1, and thus the second termination bit 912B indicates a positive termination indication and the corresponding second CLI report is the last CLI report for the first serving cell. The values of the third termination bit 912C and the fourth termination bit 912D are also 1 because each of the second serving cell and the third serving cell has only a single CLI report.

[0148] Reference Figure 10A and Figure 10B , illustrates an example CLI report format that supports a single report ID configuration. In Figure 8A , a single CLI report ID is used and the single CLI report ID is indicated by separate signaling (such as pre-configuration). In Figure 8B , the CLI report format includes a single CLI report ID indication that is used to indicate the report ID configuration for all serving cells or all CLI reports.

[0149] In Figure 10A , the sixth example 1000 of the CLI report format is illustrated. The sixth example 1000 depicts a CLI report format that uses a serving cell identifier for serving cell indication and has a structure similar to the second example 702 of Figure 7B . However, in the sixth example 1000 of Figure 10A , the CLI report format further includes one or more termination indications. Specifically, in the example of Figure 10A , the CLI report format includes a termination bit 912 for each CLI report. Compared with the second example 702 of Figure 7B , the termination bit 912 utilizes or replaces one of the previously reserved bits in the octet that includes the CLI report ID field. Based on the value of the termination bit 912, the CLI report format includes a second octet for the corresponding CLI report for the serving cell, and the second octet includes CLI value information (such as a CLI level field).

[0150] Reference Figure 10B , provides an example 1002 of the CLI report format of Figure 10A . In the example 1002 of Figure 10B , a value of 1 for the termination bit (T bit) indicates that the corresponding CLI report is the last CLI report for the corresponding serving cell, and a value of 0 for the termination bit (T bit) indicates that the corresponding CLI report is not the last CLI report for the corresponding serving cell and at least one CLI report is included in the report information for the corresponding serving cell.

[0151] For illustration,Figure 10B The CLI report format for Figure 10B includes one or more CLI reports for two serving cells (such as for C1 and C2). The first serving cell includes a plurality (e.g., two) of CLI reports, and the second serving cell includes a single CLI report. The first CLI report for the first serving cell corresponds to the second octet or row and the third octet or row, and the second CLI report corresponds to the fourth octet or row and the fifth octet or row. In Figure 10B the example of Figure 10B , the value of the first termination bit 912A is 0, and thus the first termination bit indicates a negative termination indication and includes at least one additional CLI report for the first serving cell. The value of the second termination bit 912B is 1, and thus the second termination bit indicates an affirmative termination indication and the corresponding second CLI report is the last CLI report for the first serving cell. The value of the third termination bit 912C is also 1 because the second serving cell has only a single CLI report.

[0152] Refer to Figures 11A to 11C which illustrates an example of CLI sub-band estimation. In Figure 11A an example of sub-band configuration 1100 for a specific serving cell is illustrated. In Figure 11B a first example of in-band CLI estimation for sub-band extrapolation is illustrated, and in Figure 11C a second example of cross-band CLI estimation for sub-band extrapolation is illustrated.

[0153] In Figure 11A an example of sub-band configuration 1100 for a specific serving cell is illustrated, which has five sub-bands with one uplink sub-band located between four downlink sub-bands. As Figure 11A the example of Figure 11A illustrates, the sub-band configuration includes a first downlink sub-band 1132, a second downlink sub-band 1134, an uplink sub-band 1136, a third downlink sub-band 1138, or a fourth downlink sub-band 1140.

[0154] In Figure 11B a first example of CLI extrapolation 1102 is illustrated. The first example of CLI extrapolation 1102 includes: measuring two CLI values and determining an actual CLI value based on the measurement results, and generating two virtual CLI values based on extrapolating the corresponding actual CLI value. As Figure 11B the example of Figure 11B illustrates, a first CLI measurement result 1142 is generated for the second downlink sub-band 1134 based on the CLI measurement result for the second downlink sub-band 1134, and a second CLI measurement result 1144 is generated for the fourth downlink sub-band 1140 based on the CLI measurement result for the fourth downlink sub-band 1140. After generating the actual CLI value, the virtual CLI value or the estimated CLI value can be determined at least based on the actual CLI value.

[0155] Figure 11B The first CLI extrapolation example 1102 includes ipsilateral extrapolation. That is, a first CLI estimate 1152 is generated for the first downlink subband 1132 based on the first CLI value or the first CLI measurement result 1142 for the second downlink subband 1134, and a second CLI estimate 1154 is generated for the third downlink subband 1138 based on the second CLI value or the second CLI measurement result 1144 for the fourth downlink subband 1140. Additional virtual CLI values or estimated CLI values can be determined based at least on the actual CLI value and / or the estimated CLI value.

[0156] In Figure 11C a second CLI extrapolation example 1104 is illustrated. Similar to the first CLI extrapolation example 1102, the second CLI extrapolation example 1104 includes: measuring two CLI values and determining an actual CLI value based on the measurement results, and generating two virtual CLI values based on extrapolating the corresponding actual CLI value. As Figure 11C illustrated by the example of

[0157] Figure 11C the second CLI extrapolation example 1104 includes reverse extrapolation or cross-side extrapolation. That is, a first CLI estimate 1152 is generated for the second downlink subband 1134 based on the first CLI value or the first CLI measurement result 1142 for the third downlink subband 1138, and a second CLI estimate 1154 is generated for the first downlink subband 1132 based on the second CLI value or the second CLI measurement result 1144 for the fourth downlink subband 1140. Additional virtual CLI values or estimated CLI values can be determined based at least on the actual CLI value and / or the estimated CLI value.

[0158] Refer to Figure 12A and Figure 12B and Figure 13A and Figure 13B, illustrates an example CLI report format that supports selectively including CLI value information. For example, based on one or more conditions, the CLI level fields for one or more serving cells can be excluded or omitted in the CLI report format to save space. The exclusion of the CLI field is signaled by an indication (such as a separate indicator or field) or by a specific value of an existing field. In some specific implementations, it may be useful to notify the network or other devices of the absence of interference (or no significant interference or actionable interference, such as interference below a threshold level) for a particular CLI report or a particular CLI report ID.

[0159] Such an indication of the absence of a CLI value or level is different from indicating the absence of a CLI report, such as by indicating the serving cell bitmap (Ci field) of the absent CLI report. For illustration, when there are no measurements for a particular serving cell or when the UE has not completed the CLI measurement during the generation of CLI report information, the UE may not include that particular CLI report in the CLI report information and in the transmission for the particular serving cell. Alternatively, in Figures 12A to 13B 's example, the UE may include the CLI report in the CLI report information but exclude the CLI value or CLI level information of such CLI reports that meet one or more conditions (e.g., having a CLI value below a threshold). Thus, including a CLI report but not indicating a CLI (or SI) value for that report can reduce overhead while still providing information to the network (e.g., a positive CLI indication).

[0160] In Figure 12A , the CLI report format includes a P bit 1212 that is used to indicate whether a CLI value (e.g., a CLI value field such as a CLI level) is included in the CLI report format. In Figure 12B provides Figure 12A an example of the CLI report format.

[0161] Referring to Figure 12A , illustrates a seventh example 1200 of the CLI report format. The seventh example depicts a CLI report format that uses a bitmap for serving cell indication and has a structure similar to the first example 700 of Figure 7A . However, in Figure 12A 's seventh example 1200, the CLI report format also includes one or more CLI value indications, such as one CLI value indication per CLI report or serving cell. Specifically, in Figure 12A 's example, the CLI report format includes a P bit 1212 for each CLI report. Similar to Figure 7ACompared with the first example 700, the P bit 1212 utilizes or replaces one of the previously reserved bits in the previously reserved octets including the CLI report ID field. Based on the value of the P bit 1212, the CLI report format includes a second octet for the corresponding CLI report for the serving cell, and the second octet includes CLI value information (e.g., CLI level field).

[0162] Reference Figure 12B , provides Figure 12A an example of the CLI report format. In Figure 12B the example, a value of 1 for the P bit 1212 indicates that the CLI report includes a CLI value, and a value of 0 for the P bit 1212 indicates that the CLI report does not include a CLI value. For illustration, Figure 12B the CLI report format includes two CLI reports (such as for C1 and C2). The first CLI report corresponds to a single octet (the second octet or row), and the second CLI report corresponds to two octets (the third octet or row and the fourth octet or row). Based on the first P bit 1212A having a value of 0, the UE signals or indicates that the CLI report format does not include the CLI value (CLI level field) for the first CLI report. Based on the second P bit 1214A having a value of 1, the UE signals or indicates that the CLI report format includes the CLI value (CLI level field) for the second CLI report.

[0163] Reference Figure 13A and Figure 13B illustrate additional example CLI report formats that support selective inclusion of CLI value information. In Figure 13A and Figure 13B , the CLI report format uses the value of the CLI report ID field to indicate whether the CLI value (e.g., CLI value field, such as CLI level) is included in the CLI report format. For example, a value of all zeros (such as 000000 or 0000000) can be used for the CLI report ID field to indicate in the CLI report type or configuration field that the CLI level field is not included. As illustrated, such a format can save one octet per serving cell or per CLI report.

[0164] In Figure 13A , the eighth example 1300 of the CLI report format is illustrated. The eighth example depicts a CLI report format that uses a bitmap for serving cell indication and has a structure similar to the first example 700 of Figure 7A . However, in Figure 13A the eighth example 1300 of Figure 13AThe CLI report format increases the size of the CLI report ID field 1312 and uses special values of the CLI report ID field 1312 to indicate whether CLI values (e.g., CLI value fields such as CLI level) are not included for each CLI report. Compared with Figure 7A the first example 700, the CLI report ID field 1312 has 1 additional bit 7 instead of 6, and this additional bit can accommodate additional special values or multiple additional special values to provide additional indications. When the CLI report ID field 1312 has a value indicating a specific CLI report type, the corresponding CLI value (CLI level field) for the corresponding CLI report is included in the CLI report format. When the CLI report ID field 1312 has a special value that does not indicate a specific CLI report type, the corresponding CLI value (CLI level field) for the corresponding CLI report is excluded from the CLI report format. Figure 13B Examples are provided.

[0165] Reference Figure 13B provides Figure 13A an example of the CLI report format. In Figure 13B the example, the value 0000000 of the CLI report ID field 1312 indicates that the CLI report does not include the CLI value. For illustration, Figure 13B the CLI report format includes two CLI reports (such as for C1 and C2). The first CLI report corresponds to a single octet (the second octet or row) and the second CLI report corresponds to two octets (the third octet or row and the fourth octet or row). Based on the first CLI report ID field 1312A having the value 0000000, the UE signals or indicates that the CLI report format does not include the CLI value (CLI level field) for the first CLI report. Based on the second CLI report ID field 1312B having a value other than 0000000 (such as 0101010), the UE signals or indicates that the CLI report format includes the CLI value (CLI level field) for the second CLI report.

[0166] Additionally, although Figures 12A to 13B the two options for selectively including CLI values are shown as having a bitmap 720 for serving cell indication, in other embodiments, a serving cell ID field type report format can be used. For example, the report format of Figure 7B can be used. In some such embodiments, the report format may also include a BWP field.

[0167] In some embodiments, the UE or the network may use or set a threshold for reporting CLI values or including CLI reports or values in CLI report information or transmissions. For example, the UE may measure or estimate a specific CLI (such as for a serving cell or sub-band) and compare the CLI value with the threshold. The UE may then report only CLI values that are above the threshold. In such embodiments, the UE may use any of the reporting formats described previously (e.g., MAC CE or layer 2 format).

[0168] Additionally, in some embodiments, the UE or the network may set multiple conditions or thresholds. For example, the UE or the network may set conditions (or multiple conditions) separately for each serving cell. By way of illustration, serving cell A may have a first condition that is different from serving cell B, and as an illustrative example, this may be based on distance or transmit power. As another example, the UE or the network may set conditions for each group of serving cells. Additionally or alternatively, the UE or the network may set different conditions for measured CLI and estimated CLI, and optionally different conditions for predicted CLI and interpolated CLI and / or extrapolated CLI. The network may set the conditions or thresholds, such as via RRC configuration, or may indicate to the UE how to calculate the conditions or thresholds. Alternatively, the UE may determine the conditions or thresholds based on UE criteria or standards or regional settings.

[0169] Although Figures 7A to 13B the examples are for CLI, in other embodiments, the device may use the same or a similar reporting format for SI. The SI may be reported together with the CLI (e.g., in the same report or transmission) or reported outside of the CLI (e.g., in another report or transmission).

[0170] Figure 14 is a flowchart illustrating example blocks performed by a wireless communication device (e.g., a UE or a base station) configured according to an aspect of the present disclosure. These example blocks will also be described with reference to Figure 16 the UE 115 illustrated in Figure 16 is a block diagram illustrating a UE 115 configured according to an aspect of the present disclosure. The UE 115 includes the structure, hardware, and components illustrated for the UE 115 of Figure 2 and / or Figure 4 For example, the UE 115 includes a controller / processor 280 that operates to execute logic or computer instructions stored in a memory 282 and to control the components of the UE 115 that provide the features and functionality of the UE 115. The UE 115 transmits and receives signals under the control of the controller / processor 280 via wireless radio components 1601a to 1601r and antennas 252a to 252r. The wireless radio components 1601a to 1601r include various components and hardware, as inFigure 2 As illustrated for UE 115, it includes modulators / demodulators 254a to 254r, MIMO detector 256, receive processor 258, transmit processor 264, and TX MIMO processor 266. As Figure 16 illustrated by the example of, memory 282 stores CLI report logic 1602, CLI measurement logic 1603, CLI estimation logic 1604, CLI information data 1605, CLI report configuration information data 1606, CLI measurement resource information data 1607, and setting data 1608. The data (1602 to 1608) stored in memory 282 may include or correspond to the data (406, 408, 442, and / or 444) stored in Figure 4 memory 404 of.

[0171] At block 1400, a wireless communication device (such as a UE) generates cross-link interference information corresponding to cross-link interference (CLI), where the cross-link interference corresponds to one or more serving cells. For example, a UE (e.g., UE 115) may determine CLI information 406 based on measurements or monitoring of transmissions during a first transmission 452 for Figure 4 .

[0172] The CLI information may include or correspond to Figure 4 CLI information 406 of or Figure 4 CLI report information 408 of. For illustration, UE 115 receives one or more of the first transmissions 452 via radio components 1601a to 1601r and antennas 252a to 252r, and CLI manager 415 may determine one or more actual CLI values based on the transmission. As another illustration, CLI estimator 416 may determine one or more virtual CLI values based on the transmission.

[0173] At block 1401, the UE transmits CLI report information including one or more CLI reports, where each CLI report in the one or more CLI reports corresponds to a respective serving cell in one or more serving cells. Each CLI report in the one or more CLI reports includes the respective CLI information in the CLI information corresponding to the respective serving cell corresponding to the respective CLI report. Each CLI report in the one or more CLI reports includes a respective report type indication, and each respective report type indication indicates whether the respective CLI information included in the respective CLI report corresponding to the respective CLI information includes respective actual CLI information or respective estimated CLI information. For example, UE 115 may send CLI report information to a network device (such as base station 105). The CLI report information may include or correspond to Figure 4 CLI report transmission 454 of or refer toFigure 5 One or more of the described CLI report transmissions. By way of illustration, a transmitter of UE 115 (e.g., transmit processor 264 or transmitter 410) transmits CLI report transmission 454 via radio components 1601a to 1601r and antennas 252a to 252r using a transmission bandwidth for transmission.

[0174] In other embodiments, a wireless communication device (e.g., a UE or a base station) may perform additional blocks (or the wireless communication device may be configured to further perform additional operations). For example, a wireless communication device (e.g., UE 115) may perform one or more of the operations described above (such as those referenced Figure 4 , Figure 5 , Figure 6 , Figure 11A and Figure 11B ). As another example, a wireless communication device (e.g., UE 115) may perform one or more of the aspects given below.

[0175] In a first aspect, the corresponding actual CLI information is based on only the corresponding non-historical CLI information corresponding to the corresponding serving cell to which the corresponding CLI report corresponds, and wherein the corresponding estimated CLI information is based on at least one of: only the corresponding historical CLI information corresponding to the corresponding serving cell to which the corresponding CLI report corresponds, or the corresponding historical CLI information or corresponding non-historical CLI information corresponding to one or more serving cells different from the corresponding serving cell to which the corresponding CLI report corresponds.

[0176] In a second aspect, either alone or in combination with the first aspect, the network node is configured to receive one or more resources, and wherein, to generate the CLI information, the network node is configured to generate the CLI information based on the one or more resources.

[0177] In a third aspect, either alone or in combination with one or more of the above aspects, the one or more resources include one or more CLI measurement resources, and wherein the CLI information includes: received signal strength indicator (RSSI) information; reference signal received power (RSRP) information; or signal-to-noise ratio information.

[0178] In a fourth aspect, either alone or in combination with one or more of the above aspects, the corresponding CLI information included in each corresponding CLI report included in the one or more CLI reports includes a corresponding CLI value that indicates the CLI corresponding to the corresponding serving cell to which the corresponding CLI report corresponds.

[0179] In a fifth aspect, either alone or in combination with one or more of the above aspects, the CLI reporting information includes a plurality of CLI reports for a specific serving cell among the one or more serving cells.

[0180] In a sixth aspect, either alone or in combination with one or more of the above aspects, the CLI reporting information includes per-band a plurality of CLI reports for a specific serving cell among the one or more serving cells.

[0181] In a seventh aspect, either alone or in combination with one or more of the above aspects, the per-band plurality of CLI reports includes sub-band CLI reports.

[0182] In an eighth aspect, either alone or in combination with one or more of the above aspects, in order to generate the CLI information, the network node generates the corresponding CLI information in the CLI information for each corresponding serving cell corresponding to each corresponding CLI report based on: only non-historical CLI information corresponding to the corresponding serving cell corresponding to the corresponding CLI report; only historical CLI information corresponding to the corresponding serving cell corresponding to the corresponding CLI report; or historical CLI information or non-historical CLI information corresponding to one or more serving cells different from the corresponding serving cell corresponding to the corresponding CLI report.

[0183] In a ninth aspect, either alone or in combination with one or more of the above aspects, the corresponding historical CLI information corresponds to a window of past measurements or a threshold amount of past measurements.

[0184] In a tenth aspect, either alone or in combination with one or more of the above aspects, the window of past measurements corresponds to a CLI measurement timer.

[0185] In an eleventh aspect, either alone or in combination with one or more of the above aspects, the corresponding estimated CLI information corresponds to a confidence level greater than or equal to a threshold confidence level.

[0186] In a twelfth aspect, either alone or in combination with one or more of the above aspects, the network node: receives remediation information configured to reduce the CLI at the first network node; and sends or receives a second transmission based on the remediation information.

[0187] In a thirteenth aspect, either alone or in combination with one or more of the above aspects, the network node: receives configuration information that includes information indicating a remediation action for a second node, where the configuration information is configured to reduce the CLI at the first network node; and operates based on the configuration information.

[0188] In a fourteenth aspect, either alone or in combination with one or more of the above aspects, the length indicated by each corresponding report type is one bit.

[0189] In a fifteenth aspect, either alone or in combination with one or more of the above aspects, the CLI report information includes a bitmap, where each corresponding bit of the bitmap indicates whether the CLI report information includes a corresponding report for a corresponding serving cell among the one or more serving cells.

[0190] In a sixteenth aspect, either alone or in combination with one or more of the above aspects, the CLI report information includes a single corresponding CLI report for each corresponding serving cell among the one or more serving cells, and where the one or more CLI reports include each single corresponding CLI report for each corresponding serving cell among the one or more serving cells.

[0191] In a seventeenth aspect, either alone or in combination with one or more of the above aspects, each corresponding CLI report among the one or more CLI reports includes information indicating a CLI report identifier (ID).

[0192] In an eighteenth aspect, either alone or in combination with one or more of the above aspects, each corresponding CLI report among the one or more CLI reports includes a corresponding first bit group and a corresponding second bit group, where each corresponding first bit group includes the corresponding report ID and the corresponding report type indication corresponding to the corresponding CLI report to which the corresponding first bit group corresponds, and where each corresponding second bit group includes the corresponding CLI information corresponding to the corresponding CLI report to which the corresponding second bit group corresponds.

[0193] In a nineteenth aspect, either alone or in combination with one or more of the above aspects, each corresponding first bit group is a corresponding first octet, and each corresponding second bit group is a corresponding second octet.

[0194] In a twentieth aspect, either alone or in combination with one or more of the above aspects, each corresponding CLI report among the one or more CLI reports includes a corresponding third bit group, where each corresponding third bit group includes a corresponding extension indication and at least one of the following: information indicating the corresponding serving cell to which the corresponding CLI report corresponds or information indicating a corresponding bandwidth part (BWP) identifier (ID) to which the corresponding CLI report corresponds.

[0195] In a twenty - first aspect, either alone or in combination with one or more of the above aspects, each corresponding extension indication indicates whether the CLI report information includes or excludes subsequent CLI reports relative to the corresponding CLI report to which the corresponding extension indication corresponds.

[0196] In a twenty-second aspect, either alone or in combination with one or more of the above aspects, each respective first bit group is a respective first octet, each respective second bit group is a respective second octet, and each respective third bit group is a respective third octet.

[0197] In a twenty-third aspect, either alone or in combination with one or more of the above aspects, the CLI report information includes bandwidth part (BWP) information for each of the one or more serving cells.

[0198] In a twenty-fourth aspect, either alone or in combination with one or more of the above aspects, the CLI report information includes a single respective CLI report for each respective serving cell of the one or more serving cells, wherein the one or more CLI reports include each single respective CLI report for each respective serving cell of the one or more serving cells, and wherein the CLI report information excludes information indicating any CLI report identifier (ID) for the one or more CLI reports.

[0199] In a twenty-fifth aspect, either alone or in combination with one or more of the above aspects, based on a CLI report configuration indication in downlink control information (DCI) or in a media access control control element (MAC CE), the CLI report information excludes information indicating any CLI report ID for the one or more CLI reports.

[0200] In a twenty-sixth aspect, either alone or in combination with one or more of the above aspects, the CLI report information includes one or more CLI reports for each respective serving cell of the one or more serving cells.

[0201] In a twenty-seventh aspect, either alone or in combination with one or more of the above aspects, each respective CLI report of the one or more CLI reports includes a respective termination indication that indicates whether the respective CLI report corresponding to the respective termination indication is the last CLI report for the respective serving cell corresponding to the respective CLI report.

[0202] In a twenty-eighth aspect, each respective CLI report of the one or more CLI reports includes information indicating a CLI report identifier (ID).

[0203] In a twenty-ninth aspect, either alone or in combination with one or more of the above aspects, the CLI reporting information includes at least one of the following: information indicating the corresponding serving cell to which each corresponding CLI report corresponds or information indicating the corresponding bandwidth part (BWP) identifier (ID) to which each corresponding CLI report corresponds.

[0204] In a thirtieth aspect, either alone or in combination with one or more of the above aspects, the CLI reporting information includes information indicating a single CLI report identifier (ID) that indicates the CLI report configuration for each of the one or more serving cells.

[0205] In a thirty-first aspect, either alone or in combination with one or more of the above aspects, in order to generate the CLI information, the network node is configured to: generate a first CLI for one or more first subbands of a time slot based on CLI measurement information for the one or more first subbands; and generate a second CLI for one or more second subbands of the time slot by extrapolating based on the first CLI, where at least one of the one or more first subbands is adjacent to at least one of the one or more second subbands.

[0206] In a thirty-second aspect, either alone or in combination with one or more of the above aspects, in order to generate the CLI information, the network node is configured to: generate a first CLI for one or more first subbands of a time slot based on CLI measurement information for the one or more first subbands, where the one or more first subbands are consecutive subbands; and generate a second CLI for one or more second subbands of the time slot by extrapolating based on the first CLI, where the one or more second subbands are consecutive subbands and are separated from the one or more first subbands.

[0207] In a thirty-third aspect, either alone or in combination with one or more of the above aspects, the corresponding CLI information included in each corresponding CLI report included in the one or more CLI reports includes a corresponding CLI value that indicates the CLI corresponding to the corresponding serving cell to which the corresponding CLI report corresponds, and where the network node is configured to: determine whether a particular corresponding CLI value meets a condition, where the condition corresponds to a CLI level threshold for each serving cell or group of serving cells; and based on the particular CLI value meeting the condition, determine to include the particular corresponding CLI value in the CLI reporting information; or based on the particular CLI value not meeting the condition, determine not to include the particular corresponding CLI value in the CLI reporting information.

[0208] In a thirty-fourth aspect, either alone or in combination with one or more of the above aspects, each respective CLI report among the one or more CLI reports includes a respective unit indicator, and wherein a particular value of the respective unit indicator indicates that the corresponding respective CLI report information does not include the corresponding respective CLI value.

[0209] In a thirty-fifth aspect, either alone or in combination with one or more of the above aspects, each respective CLI report among the one or more CLI reports includes a respective multi-bit field, and wherein a particular value of the respective multi-bit field indicates that the corresponding respective CLI report information does not include the corresponding respective CLI value.

[0210] In a thirty-sixth aspect, either alone or in combination with one or more of the above aspects, the network node is configured to: generate self-interference information corresponding to self-interference (SI), wherein the self-interference corresponds to interference caused by a transmitter of the first network node and received at a receiver of the first network node; and transmit SI report information including one or more SI reports, wherein each SI report among the one or more SI reports includes respective SI information of the SI information, wherein each SI report among the one or more SI reports includes a respective report type indicator, and wherein each respective report type indicator indicates whether the respective SI information included in the respective SI report corresponding to the respective SI information is respective actual SI information or respective estimated SI information.

[0211] In a thirty-seventh aspect, either alone or in combination with one or more of the above aspects, the SI report information is transmitted together with the CLI report information.

[0212] In a thirty-eighth aspect, either alone or in combination with one or more of the above aspects, each SI report among the one or more SI reports corresponds to a time period.

[0213] In a thirty-ninth aspect, either alone or in combination with one or more of the above aspects, each SI report among the one or more SI reports corresponds to a respective serving cell among one or more serving cells.

[0214] In another aspect, a device includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to: generate self-interference information corresponding to self-interference (SI), where the self-interference corresponds to interference caused by the transmitter and received at the receiver; and transmit SI report information including one or more SI reports, where each SI report of the one or more SI reports includes corresponding SI information of the SI information, where each SI report of the one or more SI reports includes a corresponding report type indicator, and where each corresponding report type indicator indicates whether the corresponding SI information included in the corresponding SI report corresponding to the corresponding SI information includes corresponding actual SI information or corresponding estimated SI information.

[0215] In some such aspects, the network node is configured to: generate cross-link interference (CLI) information corresponding to cross-link interference, where the cross-link interference corresponds to one or more serving cells; and transmit CLI report information including one or more CLI reports, where each CLI report of the one or more CLI reports corresponds to a corresponding serving cell of the one or more serving cells, where each CLI report of the one or more CLI reports includes corresponding CLI information of the CLI information corresponding to the corresponding serving cell corresponding to the corresponding CLI report, where each CLI report of the one or more CLI reports includes a corresponding report type indicator, and where each corresponding report type indicator indicates whether the corresponding CLI information included in the corresponding CLI report corresponding to the corresponding CLI information includes corresponding actual CLI information or corresponding estimated CLI information.

[0216] In some such aspects, the CLI report information is transmitted together with the SI report information. Additionally, any one of the first aspect to the thirty-ninth aspect may be combined with the other above aspects.

[0217] Accordingly, the wireless communication device may perform improved CLI reporting operations for the wireless communication device. By performing enhanced CLI and / or SI reporting, throughput can be increased and latency can be reduced.

[0218] Figure 15 is a flowchart illustrating example blocks performed by a wireless communication device (e.g., a UE or a network entity such as a base station) configured according to an aspect of the present disclosure. These example blocks will also be described with reference to the base station 105 as Figure 17 illustrated. Figure 17 is a block diagram illustrating a base station 105 configured according to an aspect of the present disclosure. The base station 105 includes as for Figure 2 and / or Figure 4The structure, hardware, and components exemplified by base station 105. For example, base station 105 includes a controller / processor 240 that operates to execute logic or computer instructions stored in a memory 242 and controls the components of base station 105 that provide the features and functionality of base station 105. Base station 105 transmits and receives signals under the control of controller / processor 240 via radio components 1701a to 1701t and antennas 234a to 234t. Radio components 1701a to 1701t include various components and hardware for base station 105 as exemplified by Figure 2 including modulators / demodulators 232a to 232t, MIMO detector 236, receive processor 238, transmit processor 220, and TX MIMO processor 230. As exemplified by the example of Figure 17 , memory 242 stores resource allocation logic 1702, resource element mapping logic 1703, broadcast logic 1704, resource allocation information data 1705, timing information data 1706, time slot configuration data 1707, and setup data 1708. The data (1702 to 1708) stored in memory 242 may include or correspond to the data (406, 408, 442, and / or 444) stored in Figure 4 memory 432 of

[0219] At block 1500, a wireless communication device such as a network device (e.g., base station 105) receives cross-link interference (CLI) report information including one or more CLI reports from a second network node. Each of the one or more CLI reports corresponds to a respective serving cell among one or more serving cells, and each of the one or more CLI reports includes respective CLI information corresponding to the respective serving cell to which the respective CLI report in the CLI information corresponds. Each of the one or more CLI reports includes a respective report type indicator, and each respective report type indicator indicates whether the respective CLI information included in the respective CLI report corresponding to the respective CLI information includes respective actual CLI information or respective estimated CLI information. For example, base station 105 may receive CLI report transmission 454 including CLI report information 408 from UE 115 and / or second UE 403.

[0220] At block 1501, the wireless communication device determines a remediation action configured to reduce the CLI for the second network node based on the CLI report information. For example, remediation manager 440 of base station 105 may determine one or more remediation actions for base station 105 and optionally for one or more UEs (such as UE 115 and / or second UE 403).

[0221] At block 1502, the wireless communication device operates based on the remediation action. For example, the base station 105 may send remediation information in the remediation indication 456 to one or more UEs (e.g., UE 115 and / or second UE 403). By way of illustration, a transmitter of the base station 105 (e.g., transmit processor 220 / TX MIMO processor 230 or transmitter 434) uses the transmit bandwidth for transmission to send the remediation indication 456 via radio components 1701a to 1701t and antennas 234a to 234t.

[0222] In other embodiments, a wireless communication device (e.g., such as a UE or a base station) may perform additional blocks (or the wireless communication device may be configured to further perform additional operations). For example, the wireless communication device may perform one or more operations as described with reference to Figure 4 , Figure 5 , Figure 6 , Figure 11A and Figure 11B . As another example, the wireless communication device may perform one or more aspects as described with reference to Figure 14 .

[0223] In a first aspect, to operate based on the remediation action, the network node is configured to: send remediation information to the second network node or to a third network node, the remediation information being configured to reduce the CLI at the second network node.

[0224] In a second aspect, either alone or in combination with the first aspect, to operate based on the remediation action, the network node is configured to: send configuration information, where the configuration information includes a remediation action configured to reduce the CLI at the second network node.

[0225] In a third aspect, either alone or in combination with one or more of the above aspects, to operate based on the remediation action, the network node is configured to: send second CLI information to a base station, the second CLI information being based on the CLI report information, the second CLI information being configured to enable the base station to generate remediation information to reduce the CLI for the second network node.

[0226] In a fourth aspect, either alone or in combination with one or more of the above aspects, to operate based on the remediation action, the network node is configured to: generate remediation information for a third network node based on the CLI report information; and send the remediation information to a base station, the remediation information indicating a remediation action for the third network node, the remediation action being configured to reduce the CLI at the second network node.

[0227] In a fifth aspect, either alone or in combination with one or more of the above aspects, for operating based on the remedial action, a network node is configured to: receive, from the second network node, SI report information including one or more SI reports, where each SI report of the one or more SI reports includes corresponding SI information of the SI information, where each SI report of the one or more SI reports includes a corresponding report type indication, and where each corresponding report type indication indicates whether the corresponding SI information included in the corresponding SI report corresponding to the corresponding SI information includes corresponding actual SI information or corresponding estimated SI information; determine, based on the SI report information, a second remedial action configured to reduce SI for the second network node; and operate based on the second remedial action.

[0228] In another aspect, a device includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to: receive, from a second network node, SI report information including one or more SI reports, where each SI report of the one or more SI reports includes corresponding SI information of the SI information, where each SI report of the one or more SI reports includes a corresponding report type indication, and where each corresponding report type indication indicates whether the corresponding SI information included in the corresponding SI report corresponding to the corresponding SI information includes corresponding actual SI information or corresponding estimated SI information; determine, based on the SI report information, a remedial action configured to reduce SI for the second network node; and operate based on the remedial action.

[0229] In some such aspects, the network node is configured to: receive, from the second network node, CLI report information including one or more cross-link interference (CLI) reports, where each CLI report of the one or more CLI reports corresponds to a corresponding serving cell among one or more serving cells, where each CLI report of the one or more CLI reports includes corresponding CLI information in the CLI information corresponding to the corresponding serving cell corresponding to the corresponding CLI report, where each CLI report of the one or more CLI reports includes a corresponding report type indication, and where each corresponding report type indication indicates whether the corresponding CLI information included in the corresponding CLI report corresponding to the corresponding CLI information includes corresponding actual CLI information or corresponding estimated CLI information;

[0230] In some such aspects, the at least one processor is configured to: determine, based on the CLI report information, a remedial action configured to reduce CLI for the second network node; and operate based on the remedial action.

[0231] In some such aspects, the CLI reporting information is sent together with the SI reporting information. Additionally, any one of the first to thirty-ninth aspects may be combined with the other above aspects.

[0232] Accordingly, the wireless communication device may perform improved CLI reporting operations for the wireless communication device. By performing enhanced CLI and / or SI reporting, throughput can be increased and latency can be reduced.

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

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

[0235] Those skilled in the art should understand that any one of a variety of different technologies and techniques can be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0236] This article refers to Figures 1 to 17 The components, functional blocks, and modules described herein include processors, electronic devices, hardware devices, electronic components, logic circuits, memories, software code, firmware code, etc., or any combination thereof. Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, and / or functions, etc., regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other terms. Additionally, the features discussed herein may be implemented via dedicated processor circuitry, via executable instructions, or a combination thereof.

[0237] Those skilled in the art will further understand that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the present disclosure may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each particular application, but such specific implementation decisions should not be construed as causing a departure from the scope of the present disclosure. Those skilled in the art will also readily recognize that the order or combination of the components, methods, or interactions described herein is merely exemplary, and the components, methods, or interactions of the various aspects of the present disclosure may be combined or performed in ways other than those illustrated and described herein.

[0238] The various illustrative logical, logical blocks, modules, circuits, and algorithmic processes described in connection with the specific implementations disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been described generally in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0239] The hardware and data processing apparatus for implementing or executing the various illustrative logical, logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be realized using a general-purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine. In some specific implementations, the processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some specific implementations, specific processes and methods may be performed by circuitry specific to a given function.

[0240] In one or more aspects, the described functionality can be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and structural equivalents thereof, or any combination thereof. The specific implementations of the subject matter described in this specification can also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by, or to control the operation of, a data processing apparatus.

[0241] If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. The processes of the methods or algorithms disclosed herein may be implemented in a processor-executable software module that may reside on a computer-readable medium. A computer-readable medium includes both a computer storage medium and a communication medium including any medium that can be implemented to transfer a computer program from one place to another. The storage medium may be any available medium accessible by a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer. Additionally, any connection may be properly termed a computer-readable medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, operations of a method or algorithm may be as a code and instruction set or any combination of a code and instruction set that resides on a machine-readable medium and a computer-readable medium, which may be incorporated into a computer program product.

[0242] Various modifications to the specific implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to some other specific implementations without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the specific implementations shown herein but are to be accorded the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0243] Additionally, those of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of description of the drawings and indicate relative positions corresponding to the orientation of the drawing on a correctly oriented page and may not reflect the correct orientation of any device as implemented.

[0244] Certain features that are described in the context of separate specific implementations in this specification may also be implemented in combination in a single specific implementation. Conversely, various features that are described in the context of a single specific implementation may also be implemented separately or in any suitable sub-combination in multiple specific implementations. Moreover, although features may have been described above as acting in certain combinations and even initially claimed as such, one or more features from the claimed combination may in some cases be excluded from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

[0245] Similarly, although operations are depicted in the figures in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed to achieve the desired result. Additionally, the figures may schematically depict one or more example processes in the form of a flowchart. However, other operations not depicted may be incorporated into the example processes schematically illustrated. For example, one or more additional operations may be performed before, after, concurrently with, or between any of the illustrated operations. In some environments, multitasking and parallel processing may be advantageous. Further, the separation of various system components in the specific implementations described above should not be construed as requiring such separation in all specific implementations, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other specific implementations also fall within the scope of the appended claims. In some cases, the acts recited in the claims may be performed in a different order and still achieve the desired result.

[0246] As used herein, the term "or" is inclusive unless restrictive language is used with respect to the listed alternatives. For example, a reference to "X is based on A or B" should be construed to include within its scope X is based on A, X is based on B, and X is based on both A and B. In this regard, a reference to "X is based on A or B" means "at least one of A or B" or "one or more of A or B" since "or" is inclusive. Similarly, a reference to "X is based on A, B, or C" should be construed to include within its scope X is based on A, X is based on B, X is based on C, X is based on A and B, X is based on A and C, X is based on B and C, and X is based on A, B, and C. In this regard, a reference to "X is based on A, B, or C" means "at least one of A, B, or C" or "one or more of A, B, or C" since "or" is inclusive. As an example of restrictive language, a reference to "X is based on only one of A or B" should be construed to include within its scope X is based on A and X is based on B, but not X is based on both A and B. Further, as used herein, the phrase "based on" should not be construed as a reference 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 construed as "at least based on A" unless stated otherwise specifically. Also, as used herein, the phrase "set" should be understood to include the possibility of a set having one member. That is, the phrase "set" should be understood in the same manner as "one or more" or "at least one".

[0247] As used herein, the term "substantially" is defined as being largely but not necessarily wholly that which is specified (and includes that which is specified; e.g., substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any of the disclosed specific embodiments, the term "substantially" may be replaced by "[percentage] within" that which is specified, where the percentage includes 0.1%, 1%, 5%, or 10%.

[0248] The foregoing description of the disclosure has been provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first network node for wireless communication, the first network node include: at least one processor; and a memory coupled to the at least one processor, wherein the at least one processor is configured to: generating cross-link interference information corresponding to cross-link interference (CLI), wherein the cross-link interference corresponds to one or more serving cells; and Sending CLI report information including one or more CLI reports, wherein each CLI report in the one or more CLI reports corresponds to a corresponding service cell among the one or more service cells, wherein each CLI report in the one or more CLI reports includes corresponding CLI information in the CLI information corresponding to the corresponding service cell to which the corresponding CLI report corresponds, wherein each CLI report in the one or more CLI reports includes a corresponding report type indication, and wherein each corresponding report type indication indicates whether the corresponding CLI information included in the corresponding CLI report corresponding to the corresponding CLI information includes corresponding actual CLI information or corresponding estimated CLI information.

2. The first network node according to claim 1, in, wherein the respective actual CLI information is based on respective non-historical CLI information corresponding only to the respective serving cell to which the respective CLI report corresponds, and wherein the respective estimated CLI information is based on at least one of: only the corresponding historical CLI information of the corresponding serving cell corresponding to the corresponding CLI report, or Relevant historical CLI information or corresponding non-historical CLI information corresponding to one or more serving cells different from the corresponding serving cell to which the corresponding CLI report corresponds.

3. The first network node of claim 1 , wherein the at least one processor is configured to receive one or more resources, and in, To generate the CLI information, the at least one processor is configured to generate the CLI information based on the one or more resources.

4. The first network node of claim 3, wherein the one or more resources include one or more CLI measurement resources, and wherein the CLI information include: Received Signal Strength Indicator (RSSI) information; Reference Signal Received Power (RSRP) information; or Signal to Interference plus Noise Ratio (SINR) information.

5. The first network node according to claim 1, wherein the respective CLI information included in each respective CLI report of the one or more CLI reports comprises a respective CLI value indicating a CLI corresponding to the respective serving cell to which the respective CLI report corresponds. 6 . The first network node according to claim 1 , wherein the CLI reporting information comprises a plurality of CLI reports for a specific serving cell among the one or more serving cells. 7 . The first network node of claim 1 , wherein the CLI reporting information comprises a plurality of CLI reports per frequency band for a specific serving cell among the one or more serving cells.

8. The first network node of claim 7, wherein the plurality of CLI reports per frequency band comprises sub-band CLI reports.

9. The first network node according to claim 1, in, In order to generate the CLI information, the at least one processor is configured to generate the corresponding CLI information corresponding to the corresponding serving cell corresponding to each corresponding CLI report in the CLI information based on the following items: Non-historical CLI information corresponding only to the corresponding serving cell corresponding to the corresponding CLI report; only the historical CLI information of the corresponding serving cell corresponding to the corresponding CLI report; or Historical CLI information or non-historical CLI information corresponding to one or more serving cells different from the corresponding serving cell to which the corresponding CLI report corresponds.

10. The first network node of claim 1, wherein the corresponding historical CLI information corresponds to a window of past measurements or a threshold amount of past measurements.

11. The first network node of claim 10, wherein the window of past measurements corresponds to a CLI measurement timer.

12. The first network node of claim 1, wherein the respective estimated CLI information corresponds to a confidence level greater than or equal to a threshold confidence level.

13. The first network node of claim 1 , wherein the at least one processor is configured to: receiving remediation information configured to reduce the CLI at the first network node; and A second transmission is sent or received based on the remediation information.

14. The first network node of claim 1 , wherein the at least one processor is configured to: receiving configuration information including information indicating a remedial action for a second node, wherein the configuration information is configured to reduce a CLI at the first network node; and An operation is performed based on the configuration information.

15. The first network node of claim 1, wherein each respective report type indication has a length of one bit.

16. The first network node according to claim 1, wherein the CLI reporting information comprises a bitmap, wherein each respective bit of the bitmap indicates whether the CLI reporting information comprises a respective report corresponding to a respective serving cell among the one or more serving cells.

17. The first network node of claim 1 , wherein the CLI reporting information comprises a single respective CLI report for each respective one of the one or more serving cells, and wherein the one or more CLI reports comprise each single respective CLI report for each respective one of the one or more serving cells.

18. The first network node of claim 17, wherein each respective CLI report of the one or more CLI reports comprises information indicating a CLI report identifier (ID).

19. The first network node according to claim 18, wherein each corresponding CLI report of the one or more CLI reports comprises a corresponding first group and a corresponding second group of bits, wherein each corresponding first group of bits comprises the corresponding report ID and the corresponding report type indication corresponding to the corresponding CLI report corresponding to the corresponding first group of bits, and wherein each corresponding second group of bits comprises the corresponding CLI information corresponding to the corresponding CLI report corresponding to the corresponding second group of bits.

20. The first network node of claim 19, wherein each respective first group of bits is a respective first octet and each respective second group of bits is a respective second octet.

21. The first network node according to claim 19, wherein each corresponding CLI report of the one or more CLI reports includes a corresponding third bit group, wherein each corresponding third bit group includes a corresponding extended indication and at least one of the following: information indicating the corresponding serving cell to which the corresponding CLI report corresponds or information indicating a corresponding bandwidth part (BWP) identifier (ID) to which the corresponding CLI report corresponds.

22. The first network node according to claim 21, wherein each respective extended indication indicates whether the CLI report information includes or excludes a subsequent CLI report relative to the respective CLI report to which the respective extended indication corresponds.

23. The first network node of claim 21, wherein each respective first group of bits is a respective first octet, each respective second group of bits is a respective second octet, and each respective third group of bits is a respective third octet.

24. The first network node of claim 1, wherein the CLI reporting information comprises bandwidth part (BWP) information for each of the one or more serving cells.

25. A first network node according to claim 1, wherein the CLI reporting information includes a single respective CLI report for each respective one of the one or more serving cells, wherein the one or more CLI reports include each single respective CLI report for each respective one of the one or more serving cells, and wherein the CLI reporting information excludes information indicating any CLI report identifier (ID) for the one or more CLI reports.

26. The first network node of claim 25, wherein the CLI report information excludes information indicating any CLI report ID for the one or more CLI reports based on a CLI report configuration indication in a downlink control information (DCI) or in a medium access control control element (MAC CE).

27. The first network node of claim 1, wherein the CLI reporting information comprises one or more CLI reports for each respective serving cell of the one or more serving cells.

28. The first network node according to claim 27, wherein each corresponding CLI report of the one or more CLI reports includes a corresponding termination indication, and the corresponding termination indication indicates whether the corresponding CLI report corresponding to the corresponding termination indication is the last CLI report for the corresponding service cell corresponding to the corresponding CLI report.

29. The first network node of claim 27, wherein each respective CLI report of the one or more CLI reports comprises information indicating a CLI report identifier (ID).

30. The first network node according to claim 29, wherein the CLI report information comprises at least one of the following: information indicating the corresponding serving cell to which each corresponding CLI report corresponds or information indicating a corresponding bandwidth part (BWP) identifier (ID) to which each corresponding CLI report corresponds.

31. The first network node of claim 27, wherein the CLI reporting information comprises information indicating a single CLI reporting identifier (ID), the single CLI reporting identifier (ID) indicating a CLI reporting configuration for each of the one or more serving cells.

32. The first network node according to claim 1, in, To generate the CLI information, the at least one processor is configured to: generating a first CLI for the one or more first subbands based on the CLI measurement information for the one or more first subbands of the time slot; and A second CLI for one or more second subbands of the time slot is generated by extrapolating based on the first CLI, wherein at least one of the one or more first subbands is adjacent to at least one of the one or more second subbands.

33. The first network node according to claim 1, in, To generate the CLI information, the at least one processor is configured to: generating a first CLI for the one or more first subbands based on CLI measurement information for the one or more first subbands of the time slot, wherein the one or more first subbands are continuous subbands; as well as A second CLI for one or more second subbands of the time slot is generated by extrapolating based on the first CLI, wherein the one or more second subbands are continuous subbands and separated from the one or more first subbands.

34. The first network node of claim 1 , wherein the respective CLI information included in each respective CLI report of the one or more CLI reports comprises a respective CLI value indicating a CLI corresponding to the respective serving cell to which the respective CLI report corresponds, and wherein the at least one processor is configured to: determining whether a particular corresponding CLI value satisfies a condition, wherein the condition corresponds to a CLI level threshold for each serving cell or serving cell group; and Based on the specific CLI value satisfying the condition, determining to include the specific corresponding CLI value in the CLI report information; or Based on the specific CLI value not satisfying the condition, it is determined not to include the specific corresponding CLI value in the CLI report information.

35. The first network node of claim 34, wherein each respective CLI report of the one or more CLI reports comprises a respective unit indicator, and wherein a particular value of the respective unit indicator indicates that the corresponding respective CLI report information does not include the corresponding respective CLI value.

36. The first network node of claim 34, wherein each respective CLI report of the one or more CLI reports comprises a respective multi-bit field, and wherein a particular value of the respective multi-bit field indicates that the corresponding respective CLI report information does not include the corresponding respective CLI value.

37. The first network node of claim 1, wherein the at least one processor is configured to: generating self-interference information corresponding to self-interference (SI), wherein the self-interference corresponds to interference caused by a transmitter of the first network node and received at a receiver of the first network node; and Send SI report information including one or more SI reports, wherein each SI report in the one or more SI reports includes corresponding SI information of the SI information, wherein each SI report in the one or more SI reports includes a corresponding report type indication, and wherein each corresponding report type indication indicates whether the corresponding SI information included in the corresponding SI report corresponding to the corresponding SI information includes corresponding actual SI information or corresponding estimated SI information.

38. The first network node according to claim 37, wherein the SI report information is sent together with the CLI report information.

39. The first network node of claim 37, wherein each of the one or more SI reports corresponds to a time period.

40. The first network node of claim 37, wherein each of the one or more SI reports corresponds to a respective serving cell of one or more serving cells.

41. A first network node for wireless communication, the first network node include: at least one processor; and a memory coupled to the at least one processor, wherein the at least one processor is configured to: receiving, from a second network node, cross-link interference (CLI) report information including one or more CLI reports, wherein each CLI report in the one or more CLI reports corresponds to a respective serving cell in one or more serving cells, wherein each CLI report in the one or more CLI reports includes respective CLI information in the CLI information corresponding to the respective serving cell to which the respective CLI report corresponds, wherein each CLI report in the one or more CLI reports includes a respective report type indication, and wherein each respective report type indication indicates whether the respective CLI information included in the respective CLI report to which the respective CLI information corresponds includes respective actual CLI information or respective estimated CLI information; determining, based on the CLI report information, a remedial action configured to reduce CLI for the second network node; as well as An operation is performed based on the remedial action.

42. The first network node according to claim 41, in, To operate based on the remedial action, the at least one processor is configured to: Remediation information is sent to the second network node or to a third network node, the remediation information being configured to reduce the CLI at the second network node.

43. The first network node according to claim 41, in, To operate based on the remedial action, the at least one processor is configured to: Configuration information is sent, wherein the configuration information includes a remedial action configured to reduce the CLI at the second network node.

44. The first network node according to claim 41, in, To operate based on the remedial action, the at least one processor is configured to: Second CLI information is sent to a base station, the second CLI information being based on the CLI report information, the second CLI information being configured to enable the base station to generate remediation information to reduce the CLI for the second network node.

45. The first network node according to claim 41, in, To operate based on the remedial action, the at least one processor is configured to: generating remediation information for a third network node based on the CLI report information; as well as The remedial information is sent to a base station, the remedial information indicating a remedial action for the third network node, the remedial action being configured to reduce the CLI at the second network node.

46. ​​The first network node according to claim 41, in, To operate based on the remedial action, the at least one processor is configured to: receiving, from the second network node, SI reporting information comprising one or more SI reports, wherein each SI report in the one or more SI reports comprises respective SI information of the SI information, wherein each SI report in the one or more SI reports comprises a respective report type indication, and wherein each respective report type indication indicates whether the respective SI information included in the respective SI report to which the respective SI information corresponds comprises respective actual SI information or respective estimated SI information; determining, based on the SI reporting information, a second remedial action configured to reduce SI for the second network node; as well as An operation is performed based on the second remedial action.

Images