WO2025232817A1

WO2025232817A1 - Methods and apparatus for autonomous cross link interference reporting in mobile communications

Info

Publication number: WO2025232817A1
Application number: PCT/CN2025/093352
Authority: WO
Inventors: Sumaila Anning MAHAMA; Mohammed S Aleabe AL-IMARI
Original assignee: MediaTek Inc
Current assignee: MediaTek Inc
Priority date: 2024-05-10
Filing date: 2025-05-08
Publication date: 2025-11-13
Anticipated expiration: 2026-11-10

Abstract

Various solutions for autonomous cross link interference (CLI) reporting with respect to user equipment (UE) and network apparatus in mobile communications are described. The UE may receive a report triggering threshold defined based on a downlink (DL) channel quality on one or more partitioned symbols. The UE may determine whether to transmit a CLI report based on an interference experienced during a DL reception on the one or more partitioned symbols and the report triggering threshold. With the report triggering threshold configured by the network node, the UE may proactively detect and report severe blockage caused by uplink (UL) transmission from nearby UEs without dedicated CLI measurement resources, thereby reducing reporting delay and achieving enhanced resource efficiency.

Description

METHODS AND APPARATUS FOR AUTONOMOUS CROSS LINK INTERFERENCE REPORTING IN MOBILE COMMUNICATIONS

CROSS REFERENCE TO RELATED PATENT APPLICATION (S)

The present disclosure is part of a non-provisional application claiming the priority benefit of U.S. Patent Application No. 63/645,197, filed 10 May 2024, the content of which herein being incorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure is generally related to mobile communications and, more particularly, to autonomous cross link interference (CLI) reporting with respect to user equipment (UE) and network apparatus in mobile communications.

BACKGROUND

Unless otherwise indicated herein, approaches described in this section are not prior art to the claims listed below and are not admitted as prior art by inclusion in this section.

3rd Generation Partnership Project (3GPP) Release 19 enables full-duplex operation, allowing simultaneous transmission and reception on overlapping time resources with a base station. This boosts maximum data throughput and reduces latency. However, this concurrency among multiple UEs can cause UE-to-UE cross link interference (CLI) . CLI occurs when a UE receiving downlink data is interfered with by another UE transmitting uplink data, or vice versa.

There are currently two UE-to-UE CLI measurement schemes: sounding reference signal-reference signal received power (SRS-RSRP) and CLI-received signal strength indicator (CLI-RSSI) . The SRS-RSRP scheme measures average power on specific SRS resources, and the CLI-RSSI scheme measures average power over a specific time-frequency region. Both schemes require the configuration of CLI measurement resources. Specifically, the SRS-RSRP scheme requires the configuration of SRS resources for both the aggressor and victim UEs, while the CLI-RSSI scheme involves configuring time and frequency resources for the victim UE. This results in a significant resource overhead, and the UE is unable to report the presence of CLI without the configuration of CLI measurement resource. Furthermore, as the measurements for both schemes are filtered at layer (L3) , a considerable reporting delay is introduced. Consequently, there is a need to provide proper schemes for CLI reporting.

SUMMARY

The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

An objective of the present disclosure is to propose solutions or schemes that address the aforementioned issues pertaining to autonomous cross link interference (CLI) reporting with respect to user equipment (UE) and network apparatus in mobile communications.

In one aspect, a method may involve an apparatus receiving a report triggering threshold defined based on a downlink (DL) channel quality on one or more partitioned symbols. The method may also involve the apparatus determining whether to transmit a CLI report based on an interference experienced during a DL reception on the one or more partitioned symbols and the report triggering threshold.

In another aspect, an apparatus may comprise a transceiver which, during operation, wirelessly communicates with a network node of a wireless network. The apparatus may also comprise a processor communicatively coupled to the transceiver. The processor, during operation, may perform operations comprising receiving, via the transceiver, a report triggering threshold defined based on a DL channel quality on one or more partitioned symbols. The processor, during operation, may further perform operations comprising determining whether to transmit a CLI report based on an interference experienced during a DL reception on the one or more partitioned symbols and the report triggering threshold.

In yet another aspect, a method may involve a network node transmitting a report triggering threshold defined based on a DL channel quality on one or more partitioned symbols to a UE. The method may further involve the network node receiving a CLI report based on the report triggering threshold from the UE.

It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro, 5th Generation (5G) , New Radio (NR) , Internet-of-Things (IoT) and Narrow Band Internet of Things (NB-IoT) , Industrial Internet of Things (IIoT) , and 6th Generation (6G) , the proposed concepts, schemes and any variation (s) /derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies. Thus, the scope of the present disclosure is not limited to the examples described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.

FIG. 1 is a diagram depicting an example scenario of a communication environment in which various solutions and schemes in accordance with the present disclosure may be implemented.

FIG. 2 is a diagram depicting an example scenario under schemes in accordance with implementations of the present disclosure.

FIG. 3 is a block diagram of an example communication system in accordance with an implementation of the present disclosure.

FIG. 4 is a flowchart of an example process in accordance with an implementation of the present disclosure.

FIG. 5 is a flowchart of another example process in accordance with an implementation of the present disclosure.
DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.
Overview

Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to autonomous cross link interference (CLI) reporting with respect to user equipment (UE) and network apparatus in mobile communications. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.

FIG. 1 illustrates an example scenario 100 under schemes in accordance with implementations of the present disclosure. Scenario 100 involves at least one network node and a UE, which may be a part of a wireless communication network (e.g., an LTE network, a 5G/NR network, an IoT network or a 6G network) . Scenario 100 illustrates the network framework. The UE may connect to the network side. The network side may comprise one or more network nodes.

In scenario 100, the UE may be configured with a framework for autonomously triggering and reporting UE-to-UE CLI via medium access control -control element (MAC-CE) . The reporting framework enables the UE to report a blockage event to the network node without dedicated CLI measurement resources and may be triggered based on channel conditions on partitioned symbols. More specifically, the network node may configure the UE with a report triggering threshold, which may be configured by a radio resource control (RRC) configuration and is defined/determined based on a downlink (DL) channel quality on one or more partitioned symbols. The DL channel quality may be associated with a channel estimation error and/or an error rate on the partitioned symbols. In the present disclosure, a symbol is considered as a partitioned symbol if it includes both DL and uplink (UL) resources. Conversely, if a symbol contains only DL or only UL resources, it is considered as a non-partitioned symbol. As shown in FIG. 2, the sub-band full duplex (SBFD) symbol 210 is a partitioned symbol, while the DL symbol 220 and UL symbol 230 are non-partitioned symbols.

After receiving the report triggering threshold from the network node, the UE may determine whether to transmit a CLI report (also referred to as the UE-to-UE CLI report) by checking if a trigger condition is met. The trigger condition is satisfied when the interference experienced during any DL reception on the partitioned symbols exceeds the report triggering threshold. The DL reception on the partitioned symbols may be associated with a reception of demodulation reference signal (DMRS) for physical downlink shared channel (PDSCH) , a DMRS for physical downlink control channel (PDCCH) , a PDSCH reception, or other DL receptions.

In one embodiment, when the report triggering threshold is defined/determined based on the channel estimation error on the partitioned symbols, the UE may be triggered to transmit the CLI report if the channel estimation error experienced during a PDSCH DMRS reception on partitioned symbols becomes greater than the report triggering threshold.

In one embodiment, when the report triggering threshold is defined/determined based on the channel estimation error on the partitioned symbols, the UE may be triggered to transmit the CLI report if the channel estimation error experienced during a PDCCH DMRS reception on partitioned symbols becomes greater than the report triggering threshold.

In one embodiment, when the report triggering threshold is defined/determined based on the error rate on the partitioned symbols, the UE may be triggered to transmit the CLI report if the error rate experienced during a PDSCH reception on partitioned symbols becomes greater than the report triggering threshold.

In one embodiment, the report triggering threshold may be defined/determined based on multiple DL channel quality factors on the partitioned symbols, and the trigger condition is met when the interference related to at least one of those factors, experienced during any DL reception on the partitioned symbols, exceeds the report triggering threshold. For example, when the report triggering threshold is defined/determined based on the channel estimation error and the error rate on partitioned symbols, the UE may be triggered to transmit the CLI report if the report triggering threshold is exceeded by any of the following experienced on partitioned symbols: channel estimation error during PDSCH DMRS reception, channel estimation error during PDCCH DMRS reception, or the error rate during PDSCH reception.

In the foregoing embodiments, when triggered to transmit the CLI report, the MAC entity of the UE may first check for available resources on the uplink-shared channel (UL-SCH) for a new transmission. If sufficient resources are available on the UL-SCH to accommodate the CLI report MAC-CE and its associated sub-header, the MAC entity of the UE may instruct an internal procedure (e.g., multiplexing and assembly procedure) to generate the CLI report MAC-CE for transmission to the network node. This ensures that the CLI report is only sent when adequate transmission capacity is present, thereby preventing unnecessary transmission failures or resource collisions.

Configured with the report triggering threshold by the network node, the UE may detect, without dedicated CLI measurement resources, that the interference level experienced during any DL reception has exceeded the threshold. Consequently, the UE may report the detected interference value to the network node as UE-to-UE CLI using MAC-CE (i.e., via layer 2 (L2) signaling) .

In another embodiment, scenario 100 may provide a framework for autonomously triggering and reporting UE-to-UE CLI via RRC. To be specific, the UE is configured with a timer (e.g., T310 timer) in addition to the report triggering threshold, and the decision to transmit a CLI report is determined by checking if the trigger condition is met in conjunction with the configured timer. In one embodiment, if the trigger condition is met (i.e., the interference experienced during the DL reception on the partitioned symbols exceeds the report triggering threshold) , the UE may start the configured timer. While the timer is running, the UE may continuously monitor the trigger condition. If, at any point while the timer is still active (i.e., still running) , the trigger condition is no longer met, the UE may stop the timer and determine not to transmit the CLI report to the network node. On the other hand, if the timer expires (i.e., running out) and the trigger condition remains satisfied, the UE may transmit the CLI report to the network node. In one embodiment, the CLI report may be conveyed within the uplink (UL) -dedicated control channel (DCCH) -message class. For example, the CLI report may be included within a failure information message. To specifically identify the nature of the CLI report, a new definition for the parameter "FailureType" may be introduced, such as defining "cliBlockage" as the failure type for a CLI report. In another example, a dedicated new message, for example named "cliBlockageInformation, " may be defined for the purpose of the CLI reporting. The UE may then utilize this newly defined message to inform the network node about a potential blockage event that it has detected.

In the foregoing embodiments, the UE may monitor, detect, and report severe CLI without dedicated CLI measurement resources. Since sounding reference signal-reference signal received power (SRS-RSRP) or CLI-received signal strength indicator (CLI-RSSI) measurement resources are not needed, the network node may allocate these resources for other uses, such as data transmission or reception, thus improving resource efficiency. Furthermore, this serves as a protective mechanism in situations where the UE is not configured with dedicated CLI measurement resources, allowing the UE to proactively detect and report severe blockage caused by UL transmission from nearby UEs and protect itself independently of network CLI measurement resource configuration.
Illustrative Implementations

FIG. 3 illustrates an example communication system 300 having an example communication apparatus 310 and an example network apparatus 320 in accordance with an implementation of the present disclosure. Each of communication apparatus 310 and network apparatus 320 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to autonomous CLI reporting with respect to UE and network apparatus in mobile communications, including scenarios/schemes described above as well as processes 400 and 500 described below.

Communication apparatus 310 may be a part of an electronic apparatus, which may be a UE such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus. For instance, communication apparatus 310 may be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Communication apparatus 310 may also be a part of a machine type apparatus, which may be an IoT, NB-IoT, or IIoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus. For instance, communication apparatus 310 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. Alternatively, communication apparatus 310 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. Communication apparatus 310 may include at least some of those components shown in FIG. 3 such as a processor 312, for example. Communication apparatus 310 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device) , and, thus, such component (s) of communication apparatus 310 are neither shown in FIG. 3 nor described below in the interest of simplicity and brevity.

Network apparatus 320 may be a part of a network apparatus, which may be a network node such as a satellite, a base station, a small cell, a router or a gateway. For instance, network apparatus 320 may be implemented in an eNodeB in an LTE network, in a gNB in a 5G/NR, IoT, NB-IoT or IIoT network or in a satellite or base station in a 6G network. Alternatively, network apparatus 320 may be implemented in the form of one or more IC chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network apparatus 320 may include at least some of those components shown in FIG. 3 such as a processor 322, for example. Network apparatus 320 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device) , and, thus, such component (s) of network apparatus 320 are neither shown in FIG. 3 nor described below in the interest of simplicity and brevity.

In one aspect, each of processor 312 and processor 322 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 312 and processor 322, each of processor 312 and processor 322 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor 312 and processor 322 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of processor 312 and processor 322 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks including autonomous CLI reporting in a device (e.g., as represented by communication apparatus 310) and a network (e.g., as represented by network apparatus 320) in accordance with various implementations of the present disclosure.

In some implementations, communication apparatus 310 may also include a transceiver 316 coupled to processor 312 and capable of wirelessly transmitting and receiving data. In some implementations, communication apparatus 310 may further include a memory 314 coupled to processor 312 and capable of being accessed by processor 312 and storing data therein. In some implementations, network apparatus 320 may also include a transceiver 326 coupled to processor 322 and capable of wirelessly transmitting and receiving data. In some implementations, network apparatus 320 may further include a memory 324 coupled to processor 322 and capable of being accessed by processor 322 and storing data therein. Accordingly, communication apparatus 310 and network apparatus 320 may wirelessly communicate with each other via transceiver 316 and transceiver 326, respectively. To aid better understanding, the following description of the operations, functionalities and capabilities of each of communication apparatus 310 and network apparatus 320 is provided in the context of a mobile communication environment in which communication apparatus 310 is implemented in or as a communication apparatus or a UE and network apparatus 320 is implemented in or as a network node of a communication network.
Illustrative Processes

FIG. 4 illustrates an example process 400 in accordance with an implementation of the present disclosure. Process 400 may be an example implementation of above scenarios/schemes, whether partially or completely, with respect to autonomous CLI reporting of the present disclosure. Process 400 may represent an aspect of implementation of features of communication apparatus 310. Process 400 may include one or more operations, actions, or functions as illustrated by one or more of blocks 410 to 420. Although illustrated as discrete blocks, various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 400 may be executed in the order shown in FIG. 4 or, alternatively, in a different order. Process 400 may be implemented by communication apparatus 310 or any suitable UE or machine type devices. Solely for illustrative purposes and without limitation, process 400 is described below in the context of communication apparatus 310. Process 400 may begin at block 410.

At block 410, process 400 may involve processor 312 of communication apparatus 310 receiving, via transceiver 316, a report triggering threshold from a network node (e.g., network apparatus 320) . Specifically, the report triggering threshold is defined based on a DL channel quality on one or more partitioned symbols. Process 400 may proceed from block 410 to block 420.

At block 420, process 400 may involve processor 312 of communication apparatus 310 determining whether to transmit a CLI report based on an interference experienced during a DL reception on the one or more partitioned symbols and the report triggering threshold.

In some implementations, the DL channel quality is associated with a channel estimation error on the one or more partitioned symbols.

In some implementations, the DL reception may include a PDSCH DMRS reception. Process 400 may further involve processor 312 transmitting, via transceiver 316, the CLI report in an event that the channel estimation error experienced during the PDSCH DMRS reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold.

In some implementations, the DL reception may include a PDCCH DMRS reception. Process 400 may further involve processor 312 transmitting, via transceiver 316, the CLI report in an event that the channel estimation error experienced during the PDCCH DMRS reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold.

In some implementations, the DL channel quality is associated with an error rate on the one or more partitioned symbols.

In some implementations, the DL reception comprises a PDSCH reception. Process 400 may involve processor 312 transmitting, via transceiver 316, the CLI report in an event that the error rate experienced during the PDSCH reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold.

In some implementations, the CLI report is transmitted via a MAC-CE through a UL-SCH.

In some implementations, process 400 may also involve processor 312 receiving a configuration associated with a timer via transceiver 316. Process 400 may further involve processor 312 starting the timer in an event that the interference experienced during the DL reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold. Specifically, whether to transmit the CLI report is further determined based on the timer.

In some implementations, process 400 may also involve processor 312 determining whether the interference experienced during the DL reception on the one or more partitioned symbols is greater than the report triggering threshold while the timer is running.

In some implementations, process 400 may also involve processor 312 stopping the timer in an event that the interference experienced during the DL reception on the one or more partitioned symbols is determined to be not greater than the report triggering threshold. Further, process 400 may involve processor 312 not transmitting the CLI report.

In some implementations, process 400 may also involve processor 312 transmitting, via transceiver 316, the CLI report in an event that the interference experienced during the DL reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold while the timer runs out.

In some implementations, the CLI report is transmitted via an RRC signaling.

In some implementations, the CLI report is transmitted inside a UL-DCCH-message class.

In some implementations, the one or more partitioned symbols comprise an SBFD symbol.

FIG. 5 illustrates another example process 500 in accordance with an implementation of the present disclosure. Process 500 may be an example implementation of above scenarios/schemes, whether partially or completely, with respect to autonomous CLI reporting in mobile communications. Process 500 may represent an aspect of implementation of features of network apparatus 320 or any suitable network node. Process 500 may include one or more operations, actions, or functions as illustrated by one or more of blocks 510 to 520. Although illustrated as discrete blocks, various blocks of process 500 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 500 may be executed in the order shown in FIG. 5 or, alternatively, in a different order. Process 500 may begin at block 510.

At block 510, process 500 may involve processor 322 of network apparatus 320 transmitting, via transceiver 326, a report triggering threshold defined based on a DL channel quality on one or more partitioned symbols to a UE (e.g., communication apparatus 310) . Process 500 may proceed from block 510 to block 520.

At block 520, process 500 may involve processor 322 receiving, via transceiver 326, a CLI report based on the report triggering threshold from the UE.

In some implementations, the report triggering threshold is defined based on a channel estimation error experienced during a PDSCH DMRS reception on the one or more partitioned symbols.

In some implementations, the report triggering threshold is defined based on a channel estimation error experienced during a PDCCH DMRS reception on the one or more partitioned symbols.

In some implementations, the report triggering threshold is defined based on an error rate experienced during a PDSCH reception on the one or more partitioned symbols.

In some implementations, process 500 may further involve processor 322 of network apparatus 320 transmitting, via transceiver 326, a configuration associated with a timer to the UE. The CLI report from the UE is further based on the timer.

In some implementations, the CLI report is transmitted via an RRC signaling.
Additional Notes

The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected" , or "operably coupled" , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable" , to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Further, with respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to, ” the term “having” should be interpreted as “having at least, ” the term “includes” should be interpreted as “includes but is not limited to, ” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an, " e.g., “a” and/or “an” should be interpreted to mean “at least one” or “one or more; ” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two recitations, " without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “asystem having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “Aor B” will be understood to include the possibilities of “A” or “B” or “A and B. ”

From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Claims

A method, comprising:

receiving, by a processor of an apparatus, a report triggering threshold defined based on a downlink (DL) channel quality on one or more partitioned symbols; and

determining, by the processor, whether to transmit a cross link interference (CLI) report based on an interference experienced during a DL reception on the one or more partitioned symbols and the report triggering threshold.
The method of Claim 1, wherein the DL channel quality is associated with a channel estimation error on the one or more partitioned symbols.
The method of Claim 2, wherein the DL reception comprises at least one of a physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) reception and a physical downlink control channel (PDCCH) DMRS reception, and the method further comprises:

transmitting, by the processor, the CLI report in an event that the channel estimation error experienced during the PDSCH DMRS reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold; or

transmitting, by the processor, the CLI report in an event that the channel estimation error experienced during the PDCCH DMRS reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold.
The method of Claim 1, wherein the DL channel quality is associated with an error rate on the one or more partitioned symbols.
The method of Claim 4, wherein the DL reception comprises a physical downlink shared channel (PDSCH) reception, and the method further comprises:

transmitting, by the processor, the CLI report in an event that the error rate experienced during the PDSCH reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold.
The method of Claim 1, wherein the CLI report is transmitted via a medium access control -control element (MAC-CE) through an uplink-shared channel (UL-SCH) .
The method of Claim 1, further comprising:

receiving, by the processor, a configuration associated with a timer; and

starting, by the processor, the timer in an event that the interference experienced during the DL reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold,

wherein the determining of whether to transmit the CLI report is further based on the timer.
The method of Claim 7, further comprising:

determining, by the processor, whether the interference experienced during the DL reception on the one or more partitioned symbols is greater than the report triggering threshold while the timer is running.
The method of Claim 8, further comprising:

stopping, by the processor, the timer in an event that the interference experienced during the DL reception on the one or more partitioned symbols is determined to be not greater than the report triggering threshold; and

not transmitting, by the processor, the CLI report.
The method of Claim 8, further comprising:

transmitting, by the processor, the CLI report in an event that the interference experienced during the DL reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold while the timer runs out.
The method of Claim 10, wherein the CLI report is transmitted via a radio resource control (RRC) signaling.
The method of Claim 11, wherein the CLI report is transmitted inside an uplink (UL) -dedicated control channel (DCCH) -message class.
The method of Claim 1, wherein the one or more partitioned symbols comprise a sub-band full duplex (SBFD) symbol.
A method, comprising:

transmitting, by a processor of a network node, a report triggering threshold defined based on a downlink (DL) channel quality on one or more partitioned symbols to a user equipment (UE) ; and

receiving, by the processor, a cross link interference (CLI) report based on the report triggering threshold from the UE.
The method of Claim 14, wherein:

the report triggering threshold is defined based on a channel estimation error experienced during a physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) reception on the one or more partitioned symbols;

the report triggering threshold is defined based on the channel estimation error experienced during a physical downlink control channel (PDCCH) DMRS reception on the one or more partitioned symbols; or

the report triggering threshold is defined based on an error rate experienced during a PDSCH reception on the one or more partitioned symbols.
The method of Claim 14, wherein the CLI report is transmitted via a medium access control -control element (MAC-CE) through an uplink-shared channel (UL-SCH) .
The method of Claim 14, further comprising:

transmitting, by the processor, a configuration associated with a timer to the UE,

wherein the CLI report from the UE is further based on the timer.
The method of Claim 17, wherein the CLI report is transmitted via a radio resource control (RRC) signaling.
An apparatus, comprising:

a transceiver which, during operation, communicates wirelessly; and

a processor communicatively coupled to the transceiver such that, during operation, the processor performs operations comprising:

receiving, via the transceiver, a report triggering threshold defined based on a downlink (DL) channel quality on one or more partitioned symbols; and

determining whether to transmit a cross link interference (CLI) report based on an interference experienced during a DL reception on the one or more partitioned symbols and the report triggering threshold.
The apparatus of Claim 19, wherein during operation, the processor further performs operations comprising:

receiving, via the transceiver, a configuration associated with a timer; and

starting the timer in an event that the interference experienced during the DL reception on the one or more partitioned symbols is determined to be greater than the report triggering threshold,

wherein the determining of whether to transmit the CLI report is further based on the timer.