WO2024230744A1

WO2024230744A1 - Methods and apparatus for cross-link interference rejection in mobile communications

Info

Publication number: WO2024230744A1
Application number: PCT/CN2024/091762
Authority: WO
Inventors: Bruno Eugene R. CLERCKX; Mohammed S Aleabe AL-IMARI; Francesc Boixadera-Espax
Original assignee: MediaTek Singapore Pte Ltd; MediaTek Inc
Current assignee: MediaTek Singapore Pte Ltd; MediaTek Inc
Priority date: 2023-05-08
Filing date: 2024-05-08
Publication date: 2024-11-14
Anticipated expiration: 2025-11-08

Abstract

Various solutions for cross-link interference (CLI) rejection with respect to user equipment and network node in mobile communications are described. An apparatus may receive assistant information from a network node. The assistant information may indicate reference signals transmitted by at least one another apparatus. The apparatus may perform a measurement for CLI according to the assistant information. The apparatus may perform a CLI rejection according to the measurement.

Description

METHODS AND APPARATUS FOR CROSS-LINK INTERFERENCE REJECTION 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/500,638, filed 08 May 2023, 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 cross-link interference (CLI) rejection 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.

In wireless communication environments, wireless signals transmitted or broadcast by network nodes or apparatuses in a wireless network may cause cross-link-interference (CLI) to neighboring network nodes or apparatuses in the neighboring areas. In addition, for a sub-band full-duplex (SBFD) capable communication apparatus (e.g., a user equipment (UE) ) , the leakage of uplink (UL) transmission may contaminate downlink (DL) reception and become an interference to the communication apparatus. Therefore, CLI rejection is an important operation to a communication apparatus in the wireless network.

However, the victim UE may only perform CLI rejection according to the received data without information for CLI. It may lead to lower performance and lower CLI rejection capability of the victim UE. For example, the victim UE only can build a covariance of interference by averaging the observed data to reject CLI.

Accordingly, how to improve CLI rejection in the wireless communication environments becomes an important issue for the newly developed wireless communication network.

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.

One objective of the present disclosure is to propose schemes, concepts, designs, systems, methods and apparatus pertaining to cross-link interference (CLI) rejection with respect to user equipment and network apparatus in mobile communications. It is believed that the above-described issue would be avoided or otherwise alleviated by implementing one or more of the proposed schemes described herein.

In one aspect, a method may involve an apparatus receiving assistant information from a network node of a wireless network, wherein the assistant information indicates reference signals transmitted by at least one another apparatus. The method may also involve the apparatus performing a measurement for CLI according to the assistant information. The method may further involve the apparatus performing a CLI rejection according to the measurement.

In another aspect, a method may involve a network node transmitting assistant information to a user equipment (UE) , wherein the assistant information indicates reference signals transmitted by at least one another UE. The method may also involve the apparatus receiving a measurement report associated with the assistant information from the UE.

In another aspect, an apparatus may involve a transceiver which, during operation, wirelessly communicates with at least one network node. The apparatus may also involve a processor communicatively coupled to the transceiver such that, during operation. The processor may receive, via the transceiver, assistant information from the network node, wherein the assistant information indicates reference signals transmitted by at least one another apparatus. The processor may also perform a measurement for CLI according to the assistant information. The processor may further perform a CLI rejection according to the measurement.

It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as 5^th Generation System (5GS) and 4G EPS mobile networking, the proposed concepts, schemes and any variation (s) /derivative (s) thereof may be implemented in, for and by other types of wireless and wired communication technologies, networks and network topologies such as, for example and without limitation, Ethernet, Universal Terrestrial Radio Access Network (UTRAN) , E-UTRAN, Global System for Mobile communications (GSM) , General Packet Radio Service (GPRS) /Enhanced Data rates for Global Evolution (EDGE) Radio Access Network (GERAN) , Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro, IoT, Industrial IoT (IIoT) , Narrow Band Internet of Things (NB-IoT) , 6th Generation (6G) , and any future-developed networking technologies. 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 for a CLI rejection procedure 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 an example process in accordance with another 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 cross-link interference (CLI) rejection with respect to user equipment 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 of a wireless communication environment having two types of interference in accordance with implementations of the present disclosure. The wireless communication environment may comprise at least two gNBs 110 and 120 (i.e., network nodes) and at least three UEs 130, 140 and 150. The gNB 110 may transmit downlink (DL) signals to the UE 140 and the UE 130 may transmit uplink (UL) signals to the gNB 110. The UE 150 may transmit UL signals to the gNB 120.

When the transmission (Tx) and reception (Rx) operations between gNBs are performed concurrently or substantially concurrently, or are partially or fully overlapped in time, the gNB-to-gNB DL-UL interference (which is one type of CLI interference) may occur. For example, the DL signals from the gNB 110 may interfere the UL signals from the UE 150. Similarly, when the Tx and Rx operations between UEs are performed concurrently or substantially concurrently, or are partially or fully overlapped in time, the UE-to-UE UL-DL interference (which is another type of CLI interference) may occur. In an example, the UL signals from the UE 130 may interfere the DL signals from the gNB 110, i.e., intra-cell inter-UE CLI. In another example, the UL signals from the UE 150 may interfere the DL signals from the gNB 110, i.e., inter-cell inter-UE CLI.

In Release 18, 3rd Generation Partnership Project (3GPP) carried out a study on non-overlapping subband full-duplex (SBFD) at the gNB side. In non-overlapping SBFD networks (where the time-division duplexing (TDD) carrier is partitioned between UL and DL in certain symbols and slots) , interference may occur between cooperative devices, i.e., inter-subband CLI. For example, the UL transmission of the UE 130 (named as an aggressor UE) may interfere the DL transmission of the UE 140 (named as a victim UE) . In addition, in the implementations of the present disclosure, the inter-subband CLI may be occurred in half-duplex (HD) UEs scenario or full-duplex (FD) UEs scenario.

In such communication environment, the gNBs 110 and 120, and the UEs 130, 140 and 150 may implement various schemes pertaining to CLI rejection in accordance with the present disclosure, as described below. It is noteworthy that, while the various proposed schemes may be individually or separately described below, in actual implementations some or all of the proposed schemes may be utilized or otherwise implemented jointly. Of course, each of the proposed schemes may be utilized or otherwise implemented individually or separately.

FIG. 2 illustrates an example scenario 200 for a CLI rejection procedure in accordance with implementations of the present disclosure. Scenario 200 involves at least an aggressor UE, a victim UE and a network node (e.g., a (macro/micro) base station) of a serving cell which may be a part of a wireless network (e.g., an LTE network, a 5G/NR network, an IoT network or a 6G network) . Referring to FIG. 2, in step S210, the victim UE (e.g., the UE 140) may receive assistant information associated with at least one aggressor UE (e.g., UE 130) from the network node (e.g., the gNB 110) .

In step S220, the victim UE may perform a measurement for CLI according to the assistant information. In addition, the victim UE may perform a CLI rejection according to the measurement.

The victim UE may receive the assistant information from the network node through a broadcast message or a high lay signaling (e.g., radio resource control (RRC) configuration) .

The assistant information may indicate the reference signals transmitted by at least one aggressor UE (e.g., UE 130) . For example, the assistant information may indicate at least one of a time-domain location and a frequency-domain location of the reference signals transmitted by the aggressor UE. The reference signals may comprise at least one of a sounding reference signal (SRS) and an uplink-demodulation reference signal (UL-DMRS) .

Specifically, the victim UE can obtain the SRS and UL-DMRS configuration of the aggressor UE according to the assistant information. The SRS and UL-DMRS configuration may be long term and stable. Then, the victim UE can listen to the source of interference according to the SRS and UL- DMRS configuration to obtain the information on the source of interference. In addition, the victim UE may obtain some information on the directions of the interference according to the assistant information, e.g., the UE may capture the information from the covariance matrices which are measured according to the assistant information. That is, when the victim UE performs the measurement for CLI of the aggressor UE according to the assistant information, the victim UE may listen to the source of the CLI, estimate the channel, store samples, and/or build a robust receiver to reject the CLI from the aggressor UE. The victim UE may reject the CLI through an interference rejection combining (IRC) technology, e.g., linear minimum mean square error (MMSE) .

When the victim UE performs the CLI rejection continuously, higher complexity and power consumption may be generated. Therefore, in order to reduce higher complexity and power consumption of the victim UE, the network node may further transmit the assistant information to the victim UE to indicate whether a scheduled DL resource is interfered by CLI or not. Then, the victim UE can determine whether to activate/deactivate the CLI rejection according to the assistance information. When the victim UE determines that a received DL resource is not interfered by CLI (i.e., the DL reception is CLI-free) according to the assistant information, the victim UE may deactivate the CLI rejection on the DL resource. For example, if the network node determines that there are no UL users (i.e., no aggressor UEs) , the assistant information from the network node may indicate that the scheduled DL resource is not interfered by CLI. Then, the victim UE may not activate the CLI rejection according to the assistance information. In another example, if the network node determines that the aggressor UE is sufficiently far apart from each other, for instance when used together with other CLI management strategy (e.g., scheduling) . The network node may expect the resulting CLI to be marginal.

In addition, in some situations (e.g., at least one of an inaccurate or partial feedback, an irregular SRS and/or DM-RS transmission, a dynamic interference, and a frequency selective) , the network node may not have enough information to accurately determine whether the DL resource is interfered by CLI or not, or to determine which CLI management method is suitable for victim UE currently. Therefore, the victim UE may further report at least one of channel quality information (CQI) and a CLI-handling capability to the network node. The network node may configure or adopt a suitable CLI management method (e.g., at least one of a CLI rejection, a scheduling, a precoding matrix indicator (PMI) recommendation, a PMI restriction, a rank recommendation, a rank restriction and a friendly PMI) according to the CQI and CLI-handling capability from the victim UE to mitigate the CLI of the victim UE.

In an implementation, the CQI may comprise a first report for a receiver with CLI (e.g., CLI-robust receiver) and a second report for a receiver without CLI (e.g., non-CLI-robust receiver) . In another implementation, the PMI or rank indicator (RI) may further comprise a first report for a receiver with CLI and a second report for a receiver without CLI. In addition, the CQI may comprise at least one of a wideband CQI for a receiver without CLI, a delta wideband CQI for a receiver with CLI, a subband CQI for a receiver without CLI, and a delta subband CQI for a receiver with CLI.

The CLI-handling capability may be part of capability report of the victim UE. The support of advanced receiver can be reported as a UE capability. In an example, the CLI-handling capability may be a quantitative gain, e.g., an Rx gain of the victim UE or the gain of CLI-robust receiver over non-CLI-robust receiver.

The victim UE may also determine the PMI recommendation or rank recommendation according to the CLI rejection result. For example, the victim UE may perform the CLI rejection to remove/reject major interferer, and then perform PMI recommendation for remaining CLI (e.g., second major interferer) .

Illustrative Implementations

FIG. 3 illustrates an example communication system 300 having at least 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 CLI rejection, including the various schemes described above with respect to various proposed designs, concepts, schemes and methods described above and with respect to user equipment and network apparatus in mobile communications, including scenarios/schemes described above as well as process 400 and process 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 reliability enhancements 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.

In some implementations, processor 312 may receive, via transceiver 316, assistant information from network apparatus 320 of a wireless network, wherein the assistant information may indicate reference signals transmitted by at least one another apparatus. Processor 312 may perform a measurement for CLI according to the assistant information. Processor 312 may perform a CLI rejection according to the measurement.

In some implementations, the assistant information may be received through a broadcast message or a high layer signaling.

In some implementations, the assistant information may indicate at least one of a time-domain location and a frequency-domain location of the reference signals.

In some implementations, the reference signals may comprise at least one of an SRS and an UL-DMRS.

In some implementations, the assistant information may indicate whether a scheduled DL resource is interfered by CLI or not. Processor 312 may determine whether to activate the CLI rejection according to the assistance information.

In some implementations, processor 312 may receive, via transceiver 316, a resource that is not interfered by CLI. Processor 312 may deactivate the CLI rejection on the resource.

In some implementations, processor 312 may report, via transceiver 316, at least one of CQI and a CLI-handling capability to network apparatus 320. Processor 312 may receive, via transceiver 316, a configuration for CLI management from network apparatus 320 in response to the reporting.

In some implementations, the CQI may comprise a first report for a receiver with CLI and a second report for a receiver without CLI.

In some implementations, the CQI may comprise at least one of a wideband CQI for a receiver without CLI, a delta wideband CQI for a receiver with CLI, a subband CQI for a receiver without CLI and a delta subband CQI for a receiver with CLI.

In some implementations, processor 322 may transmit, via transceiver 326, assistant information to communication apparatus 310, wherein the assistant information indicates reference signals transmitted by at least one another UE. Processor 322 may receive, via transceiver 326, a measurement report associated with the assistant information from communication apparatus 310.

In some implementations, the assistant information may be transmitted through a broadcast message or a high layer signaling.

In some implementations, the assistant information may indicate whether a scheduled DL resource is interfered by CLI or not. Processor 322 may indicate whether to activate the CLI rejection in the assistance information.

In some implementations, processor 322 may receive, via transceiver 326, at least one of CQI and a CLI-handling capability from communication apparatus 310. Processor 322 may transmit, via transceiver 326, a configuration for CLI management to communication apparatus 310 in response to the receiving.

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 CLI rejection with 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, 420 and 430. 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 410, process 400 may involve processor 312 of communication apparatus 310 receiving, via transceiver 316, assistant information from a network node, wherein the assistant information may indicate reference signals transmitted by at least one another apparatus. Process 400 may proceed from 410 to 420.

At 420, process 400 may involve processor 312 performing a measurement for CLI according to the assistant information. Process 400 may proceed from 420 to 430.

At 430, process 400 may involve processor 312 performing a CLI rejection according to the measurement.

In some implementations, process 400 may involve processor 312 determining whether to activate the CLI rejection according to the assistance information.

In some implementations, process 400 may involve processor 312 receiving, via transceiver 316, a resource that is not interfered by CLI. Process 400 may involve processor 312 deactivating the CLI rejection on the resource.

In some implementations, process 400 may involve processor 312 reporting, via transceiver 316, at least one of CQI and a CLI-handling capability to the network node. Process 400 may involve processor 312 receiving, via transceiver 316, a configuration for CLI management from the network node in response to the reporting.

FIG. 5 illustrates an example process 500 in accordance with another implementation of the present disclosure. Process 500 may be an example implementation of above scenarios/schemes, whether partially or completely, with respect to CLI rejection with the present disclosure. Process 500 may represent an aspect of implementation of features of network apparatus 320. Process 500 may include one or more operations, actions, or functions as illustrated by one or more of blocks 510 and 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 be implemented by network apparatus 320 or any base stations or network nodes. Solely for illustrative purposes and without limitation, process 500 is described below in the context of network apparatus 320. Process 500 may begin at block 510.

At 510, process 500 may involve processor 322 of network apparatus 320 transmitting, via transceiver 326, assistant information to a UE, wherein the assistant information indicates reference signals transmitted by at least one another UE. Process 500 may proceed from 510 to 520.

At 520, process 500 may involve processor 322 receiving, via transceiver 326, a measurement report associated with the assistant information from the UE.

In some implementations, process 500 may involve processor 322 indicating whether to activate the CLI rejection in the assistance information.

In some implementations, process 500 may involve processor 322 receiving, via transceiver 326, at least one of CQI and a CLI-handling capability from the UE. Process 500 may involve processor 322 transmitting, via transceiver 326, a configuration for CLI management to the UE in response to the receiving.

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., “a system 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 “A or 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, an assistant information from a network node, wherein the assistant information indicates reference signals transmitted by at least one another apparatus; and

performing, by the processor, a measurement for cross-link interference (CLI) according to the assistant information; and

performing, by the processor, a CLI rejection according to the measurement.
The method of Claim 1, wherein the assistant information is received through a broadcast message or a high layer signaling.
The method of Claim 1, wherein the assistant information indicates at least one of a time-domain location and a frequency-domain location of the reference signals.
The method of Claim 1, wherein the reference signals comprise at least one of a sounding reference signal (SRS) and an uplink-demodulation reference signal (UL-DMRS) .
The method of Claim 1, wherein the assistant information indicates whether a scheduled downlink (DL) resource is interfered by CLI or not and the method further comprises:

determining, by the processor, whether to activate the CLI rejection according to the assistance information.
The method of Claim 1, further comprises:

receiving, by the processor, a resource that is not interfered by CLI; and

deactivating, by the processor, the CLI rejection on the resource.
The method of Claim 1, further comprising:

reporting, by the processor, at least one of channel quality information (CQI) and a CLI-handling capability to the network node.
The method of Claim 7, further comprising:

receiving, by the processor, a configuration for CLI management from the network node in response to the reporting.
The method of Claim 7, wherein the CQI comprises a first report for a receiver with CLI and a second report for a receiver without CLI.
The method of Claim 7, wherein the CQI comprises at least one of a wideband CQI for a receiver without CLI, a delta wideband CQI for a receiver with CLI, a subband CQI for a receiver without CLI and a delta subband CQI for a receiver with CLI.
A method, comprising:

transmitting, by a processor of a network node, an assistant information to a user equipment (UE) , wherein the assistant information indicates reference signals transmitted by at least one another UE; and

receiving, by the processor, a measurement report associated with the assistant information from the UE.
The method of Claim 11, wherein the assistant information is transmitted through a broadcast message or a high layer signaling.
The method of Claim 11, wherein the assistant information indicates at least one of a time-domain location and a frequency-domain location of the reference signals.
The method of Claim 11, wherein the assistant information indicates whether a scheduled downlink (DL) resource is interfered by CLI or not and the method further comprises:

indicating, by the processor, whether to activate the CLI rejection in the assistance information.
The method of Claim 11, further comprising:

receiving, by the processor, at least one of channel quality information (CQI) and a CLI-handling capability from the UE.
The method of Claim 15, further comprising:

transmitting, by the processor, a configuration for CLI management to the UE in response to the receiving.
The method of Claim 15, wherein the CQI comprises a first report for a receiver with CLI and a second report for a receiver without CLI.
The method of Claim 15, wherein the CQI comprises at least one of a wideband CQI for a receiver without CLI, a delta wideband CQI for a receiver with CLI, a subband CQI for a receiver without CLI and a delta subband CQI for a receiver with CLI.
An apparatus, comprising:

a transceiver which, during operation, wirelessly communicates with at least one network node; and

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

receiving, via the transceiver, an assistant information from the network node, wherein the assistant information indicates reference signals transmitted by at least one another apparatus;

performing a measurement for cross-link interference (CLI) according to the assistant information; and

performing a CLI rejection according to the measurement.
The apparatus of Claim 19, wherein the processor is further configured to perform operations comprising:

determining whether to activate the CLI rejection according to the assistance information.