Cross-link interference measurement and reporting

By configuring the UE to perform CLI measurements and reports on non-periodic resources through physical layer signaling, the false detection problem caused by the inflexibility of CLI measurement resources in the prior art is solved, and more accurate and dynamic CLI reporting is achieved, supporting SBFD operation.

CN123125997APending Publication Date: 2026-11-17ALCATEL LUCENT SHANGHAI BELL CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090827.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-02-16
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing methods for measuring and reporting cross-link interference lack flexibility and dynamism, and periodic measurement resources may lead to false detections and inaccurate estimates of CLI.

Method used

Configure the UE to perform CLI measurements on aperiodic resources and report CLI measurements on secondary resources by configuring physical layer signaling. Resource indication is performed using DCI format 5_0 or a modified legacy DCI format, enabling aperiodic and faster CLI measurements and reporting.

Benefits of technology

It improves the accuracy and flexibility of CLI measurements, enabling dynamic adjustment at the TTI or time slot level, reducing CLI false detections, and supporting the optimization of SBFD operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125997A_ABST
    Figure CN123125997A_ABST
Patent Text Reader

Abstract

Some examples provide an apparatus (10, 110) including: components (11, 15) for receiving configuration information (502) from an access node (120) via physical layer signaling, the configuration information being used to configure the apparatus to: perform at least one cross-link interference CLI measurement on at least one first resource (503) and report at least one CLI measurement via at least one second resource (504); components for performing (11) at least one CLI measurement based at least in part on the configuration information; and components for reporting (11, 15) at least one CLI measurement based at least in part on the configuration information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Examples of this disclosure relate to CLI measurement and reporting of cross-link interference. Some examples relate to apparatus, methods, and computer programs for CLI measurement and reporting. Background Technology

[0002] Routine CLI measurements and reporting are not optimal. Routine CLI measurements and reporting can be limited to performing periodic CLI measurements and their periodic reporting.

[0003] In some cases, improved CLI measurement and reporting may be desired. In others, greater flexibility and control over when CLI measurements and reporting occur may be desired. In still others, non-periodic CLI measurement and reporting may be desired. In some situations, dynamic CLI measurement and reporting may be desired. Summary of the Invention

[0004] According to various, but not all, examples of the invention are provided as described in the appended claims. Any examples and features described herein that do not fall within the scope of the independent claims are to be construed as examples that facilitate understanding of various embodiments of the invention.

[0005] According to various, but not necessarily all, examples, an apparatus is provided that includes: A component for receiving configuration information from an access node via physical layer signaling, the configuration information being used to configure the device as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; A component for performing at least one CLI measurement based at least in part on configuration information; and A component used to report at least one CLI measurement based at least in part on configuration information.

[0006] Based on various, but not all, examples, a method is provided, including: At the device, configuration information is received from the access node via physical layer signaling. This configuration information is used to configure the device as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; Perform at least one CLI measurement, based at least in part on configuration information; and Report at least one CLI measurement, based at least in part on configuration information.

[0007] According to various, but not all, examples, a chipset is provided that includes a processing circuitry system configured to perform the methods mentioned above.

[0008] Based on various, but not all, examples, modules, circuit systems, devices, user equipment, and / or systems are provided that include means for performing the methods mentioned above.

[0009] According to various, but not all, examples, a computer program is provided that includes instructions that, when executed by a device, cause the device to perform: Configuration information is received from the access node via physical layer signaling. This configuration information is used to configure the device as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; Perform at least one CLI measurement, based at least in part on configuration information; and Report at least one CLI measurement, based at least in part on configuration information.

[0010] According to several, but not all, examples, an apparatus is provided that includes: At least one processor; and At least one memory, storing instructions that, when executed by at least one processor, cause the device to at least: Configuration information is received from the access node via physical layer signaling. This configuration information is used to configure the device as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; Perform at least one CLI measurement, based at least in part on configuration information; and Report at least one CLI measurement, based at least in part on configuration information.

[0011] Based on various, but not all, examples, a non-transitory computer-readable medium is provided that utilizes instruction encoding, which, when executed by at least one processor, causes at least the following to be performed: Configuration information is received from the access node via physical layer signaling. This configuration information is used to configure the device as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; Perform at least one CLI measurement, based at least in part on configuration information; and Report at least one CLI measurement, based at least in part on configuration information.

[0012] According to various, but not all, examples, an apparatus is provided that includes: A component for enabling the transmission of configuration information to a user equipment (UE) via physical layer signaling, the configuration information being used to configure the UE as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; A component for receiving at least one CLI measurement from a UE, based at least in part on configuration information.

[0013] Based on various, but not all, examples, a method is provided, including: This enables the transmission of configuration information to the User Equipment (UE) via physical layer signaling. This configuration information is used to configure the UE as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; At least one CLI measurement is received from the UE, based at least in part on configuration information.

[0014] According to various, but not all, examples, a chipset is provided that includes a processing circuitry system configured to perform the methods mentioned above.

[0015] Based on various, but not all, examples, modules, circuit systems, devices, access nodes, and / or systems are provided that include means for performing the methods mentioned above.

[0016] Based on various, but not all, examples, a computer program is provided, including instructions that, when executed by a device, cause the device to perform: This enables the transmission of configuration information to the User Equipment (UE) via physical layer signaling. This configuration information is used to configure the UE as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; At least one CLI measurement is received from the UE, based at least in part on configuration information.

[0017] According to various, but not all, examples, an apparatus is provided that includes: At least one processor; and At least one memory stores instructions that, when executed by at least one processor, cause the device to at least: This enables the transmission of configuration information to the User Equipment (UE) via physical layer signaling. This configuration information is used to configure the UE as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; At least one CLI measurement is received from the UE, based at least in part on configuration information.

[0018] Based on various, but not all, examples, a non-transitory computer-readable medium is provided that utilizes instruction encoding, which, when executed by at least one processor, causes at least the following to be performed: This enables the transmission of configuration information to the User Equipment (UE) via physical layer signaling. This configuration information is used to configure the UE as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; At least one CLI measurement is received from the UE, based at least in part on configuration information.

[0019] The following sections of this “Summary of the Invention” section describe various features that, with necessary modifications, may serve as features of any example described in the preceding sections of this “Summary of the Invention” section. The description of the function should also be considered as disclosing any components suitable for performing the function, or any instructions stored in at least one memory that, when executed by at least one processor, cause the device to perform the function.

[0020] In some, but not all, examples, the configuration information includes at least one of the following indications: At least one first resource, on which at least one CLI measurement will be performed; At least one second resource, through which at least one CLI measurement will be reported; At least one parameter for configuring the execution of at least one CLI measurement; or At least one parameter for configuring a report of at least one CLI measurement.

[0021] In some, but not all, examples, the configuration information includes: Information indicating at least one resource; and At least one indicator, the at least one indicator indicating the device: Use at least one resource to perform at least one CLI measurement, or Use at least one resource to report at least one CLI measurement.

[0022] In some, but not all, examples, at least one primary resource includes at least one of the following: At least one time-domain resource, on which at least one CLI measurement will be performed; At least one time-domain location, at which at least one CLI measurement will be performed; At least one duration, during which at least one CLI measurement will be performed; At least one frequency domain resource, on which at least one CLI measurement will be performed; or At least one reference signal resource.

[0023] In some, but not all, examples, the at least one second resource includes at least one of the following: At least one time-domain resource, using which at least one CLI measurement will be reported; At least one time-domain location, at which at least one CLI measurement will be reported; and At least one frequency domain resource, using which at least one CLI measurement will be reported.

[0024] In some, but not all, examples, at least one CLI measurement is reported via at least one of the following: Physical layer signaling; or Uplink Control Information (UCI).

[0025] In some, but not all, examples include at least one of the following CLI measurements: User equipment (UE) to UE CLI measurement; Non-periodic CLI measurement; At least one signal strength measurement of one or more signals received on at least one first resource; or At least one power measurement of at least one reference signal.

[0026] In some, but not all, examples, the apparatus further includes: components for receiving configuration information for: configuring periodic resources for periodically transmitting reference signals; and Configuration information for configuring the device to perform at least one CLI measurement includes configuration information for: configuring the device to perform at least one CLI measurement on at least one periodic resource instead of transmitting a reference signal on at least one periodic resource.

[0027] In some, but not all, examples, the device also includes: Components for receiving configuration information for the following: periodic resources for the device to periodically transmit reference signals; and Configuration information for configuring the device to perform at least one CLI measurement includes configuration information for defining at least one periodic resource of a periodic resource as at least one first resource.

[0028] In some, but not all, examples, receiving this configuration information via physical layer signaling includes: Receive configuration information via a first physical layer signal for: configuring the device to perform at least one CLI measurement on at least one first resource; and Configuration information is received via a second physical layer signal for configuring the device to report at least one CLI measurement on at least one second resource.

[0029] In some, but not all, examples, physical layer signaling is scrambled based at least in part on one or more of the following: Identifier; Identifiers used to identify devices; UE-specific identifier; An identifier used to identify the UE group; or Temporary wireless network identifier.

[0030] In some, but not all, examples, the device is included in the user equipment (UE).

[0031] In some, but not all, examples, the access node includes a component for applying an interference suppression scheme based at least in part on at least one received CLI measurement.

[0032] In some, but not all, examples, the access node includes a component for adjusting the subband non-overlapping full-duplex SBFD operating mode based at least in part on at least one received CLI measurement.

[0033] In some, but not all, examples, the access node includes: a component for causing configuration information for sending to a second UE via physical layer signaling for configuring the UE to send transmissions via at least one first resource.

[0034] According to various, but not all, embodiments, an apparatus is provided comprising: components for performing at least a portion of one or more methods described herein. The description of functions and / or actions should also be considered as disclosing any components suitable for performing those functions and / or actions. The functions and / or actions described herein can be performed in any suitable manner and using any suitable method.

[0035] Although the examples and optional features described above are presented separately, it should be understood that they are provided in all possible combinations and permutations and are included within the scope of this disclosure. It should be understood that various examples may include any or all of the features described with respect to other examples, and vice versa. Furthermore, it should be understood that any one, several, or all of the features may be implemented / included therein / performed by any means, method, and / or computer program instructions, as appropriate, in any combination. The description of the function should also be considered as disclosing any components suitable for performing that function. Attached Figure Description

[0036] Some examples will now be described with reference to the accompanying drawings, in which:

[0037] Figure 1 Examples of the topics described in this article are shown;

[0038] Figure 2 This article presents another example of the subject matter described herein;

[0039] Figure 3 This article presents another example of the subject matter described herein;

[0040] Figure 4 This article presents another example of the subject matter described herein;

[0041] Figure 5 This article presents another example of the subject matter described herein;

[0042] Figure 6 This article presents another example of the subject matter described herein;

[0043] Figure 7 This article presents another example of the subject matter described herein;

[0044] Figure 8 This article presents another example of the subject matter described herein;

[0045] Figure 9 This article presents another example of the subject matter described herein;

[0046] Figure 10 This article presents another example of the subject matter described herein;

[0047] Figure 11 This article presents another example of the subject matter described herein; and

[0048] Figure 12 This shows another example of the subject matter described in this article.

[0049] The accompanying drawings are not drawn to scale. For clarity and simplicity, some features and views in the drawings may be shown schematically or enlarged to scale. For example, the dimensions of some elements in the drawings may be enlarged relative to other elements to aid illustration. Similar reference numerals are used in the drawings to indicate similar features. For clarity, not all reference numerals are necessarily shown in all drawings.

[0050] In the specification and figures, reference numerals without subscripts (e.g., 123) can be used as general references to features or feature classes / sets. Reference numerals with subscripts (e.g., 123_1) can be used as specific references, for example, to distinguish different instances of a feature or feature class / set. abbreviations

[0051] 3GPP Third Generation Partnership Project

[0052] 5G (Fifth Generation)

[0053] 6G sixth generation

[0054] C-RNTI (Cellular Radio Network Temporary Identifier)

[0055] CLI Cross-Link Interference

[0056] CLI-RNTI Cross-Link Interference Wireless Network Temporary Identifier

[0057] DCI Downlink Control Information

[0058] DL downlink

[0059] FDU Flexible Full-Duplex

[0060] gNB Next Generation Node B

[0061] NR New Radio

[0062] PDCCH (Physical Downlink Control Channel)

[0063] PDSCH (Physical Downlink Shared Channel)

[0064] PRB (Physical Resource Block)

[0065] PUCCH (Physical Uplink Control Channel)

[0066] PUSCH Physical Uplink Shared Channel

[0067] RNTI (Non-Real-Time Identifier for Wireless Networks)

[0068] RRC (Radio Resource Control)

[0069] RSRP reference signal received power

[0070] RSSI Received Signal Strength Indicator

[0071] SBFD Subband Non-overlapping Full-Duplex

[0072] SFI-RNTI Slot Format Indicates Temporary Identifier for Wireless Networks

[0073] SP-RNTI Semi-Persistent CSI Wireless Network Temporary Identifier

[0074] SRS Detection Reference Signal

[0075] TDD (Time Division Duplex)

[0076] TTI Transmission Time Interval

[0077] UE User Equipment

[0078] UL uplink Detailed Implementation

[0079] Figure 1 An example of a network 100 suitable for use with the examples of this disclosure is schematically shown. The network (also referred to as an NW) includes multiple network nodes, including: a terminal node 110 (also referred to as a user equipment UE), an access node 120 (also referred to as a base station BS), and one or more core network nodes 130. Terminal node 110 and access node 120 communicate with each other. In some, but not all, examples, one or more core network nodes 130 may communicate with each other. In some, but not all, examples, one or more access nodes 120 may communicate with each other.

[0080] In this example, network 100 is a wireless telecommunications network, namely a radio access network (RAN), in which at least some terminal nodes 110 and access nodes 120 communicate with each other by transmitting / receiving radio waves.

[0081] Network / RAN 100 may be a cellular network comprising multiple cells 122, each cell being served by access node 120. Access node 120 includes a cellular radio transceiver. Terminal node 110 includes a cellular radio transceiver.

[0082] In the specific examples shown and discussed below, network 100 is a new radio NR network of the 3rd Generation Partnership Project (3GPP) and its fifth-generation 5G technology. In other examples, network 100 can be a network above 5G, such as the next-generation (i.e., sixth-generation 6G) wireless network currently evolving (i.e., NR network and its evolution towards 5G technology).

[0083] The interface between terminal node 110 and access node 120 is a wireless interface 124 (e.g., a Uu interface). The interface between access node 120 and one or more core network nodes 130 is a backhaul interface 128 (e.g., an S1 and / or next-generation NG interface). The interface between one or more location servers 140 and one or more core network nodes 130 is a backhaul interface 132 (e.g., an NLs interface).

[0084] Depending on the specific deployment scenario, access node 120 can be a RAN node, such as an NG-RAN node. An NG-RAN node can be a gNodeB (gNB), which provides NG user plane and control plane protocol termination to the UE. The gNB connects to the 5G core (5GC) via the NG interface, and more specifically, to the Access and Mobility Management Function (AMF) via the NG control plane NG-C interface, and to the User Plane Function (UPF) via the NG user plane NG-U interface. Access nodes 120 can interconnect with each other via Xn interface 126.

[0085] Cellular network 100 can be configured to operate in licensed or unlicensed frequency bands (especially unlicensed frequency bands, which rely on the transmitting device to sense the radio resources / medium before starting transmission, such as via the Listen-After-Speak (LBT) procedure; and the 60 GHz unlicensed frequency band, in which beamforming may be required to achieve the desired coverage).

[0086] Access node 120 can be deployed in NG standalone operation / scenarios. Access node 120 can be deployed in NG non-standalone operation / scenarios. Access node 120 can be deployed in carrier aggregation (CA) operation / scenarios. Access node 120 can be deployed in dual-connectivity DC operation / scenarios, i.e., multiple radio access technologies – dual-connectivity MR-DC or NR-DC. Access node 120 can be deployed in multi-connectivity MC operation / scenarios.

[0087] In this non-standalone / dual-connectivity deployment, access nodes 120 can interconnect with each other via X2 or Xn interfaces, and connect to the Evolved Packet Core (EPC) via the S1 interface, or to the 5GC via the NG interface.

[0088] Access node 120 is a network element in the network responsible for wirelessly transmitting to or receiving from terminal node 110 in one or more cells 122. Access node 120 is a network terminal of the wireless link. Each access node can host one or more Transmitter / Receiver Points (TRPs).

[0089] Access node 120 can be implemented as a single network device or have a split architecture that is decomposed / distributed across two or more RAN nodes, such as a central unit (CU), a distributed unit (DU), and a remote radio head (RRH), which use different functional split architectures and different interfaces.

[0090] Terminal node 110 is a user-side network element that terminates a radio link in the network. This terminal node is a device that allows access to network services. The functions of terminal node 110 can also be performed by a mobile terminal MT, which is part of the Integrated Access and Backhaul (IAB) node. Terminal node 110 can be referred to as a user equipment (UE) mobile terminal or mobile station.

[0091] The term "user equipment" can be used to specify a mobile device that includes components for authentication / encryption, such as a smart card or a Subscriber Identity Module (SIM). The SIM / SIM card can be a memory chip, module, or Universal Subscriber Identity Module (USIM). In some examples, the term "user equipment" can be used to specify a location / position tag, a super / smart sensor, or a mobile device that includes circuitry embedded as part of the user equipment for authentication / encryption, such as a software SIM.

[0092] In the following description: The terminal node can be abbreviated as UE 110; Access nodes or RAN nodes can be abbreviated as gNB or BS 120; and Network nodes (especially those such as UEs or BSs) can be simply referred to as network nodes (NW nodes).

[0093] Before describing the example implementation in detail, the evolution of duplex operation in the new radio NR, referred to as subband non-overlapping full-duplex, will be discussed, as will cross-link interference CLIs, such as UE-to-UE CLIs, that may occur under SBFD deployment.

[0094] The 3GPP 5G NR third-generation partnership program currently supports two duplex modes: Frequency Division Duplex (FDD) for paired frequency bands and Time Division Duplex (TDD) for unpaired frequency bands. In TDD, time-domain resources are separated between the downlink and uplink. Allocating limited durations for the uplink in TDD results in reduced coverage, increased latency, and reduced capacity.

[0095] SBFD is an evolution of NR full-duplex operation, allowing simultaneous downlink (DL) and uplink (UL) transmissions on different Physical Resource Blocks (PRBs) within unpaired broadband NR cells. On the gNB side within a conventional TDD band, both downlink and uplink exist simultaneously, i.e., full-duplex. The set of PRBs assigned to a specific link direction is called a subband, and this type of duplex is represented as Subband Non-overlapping Full-Duplex "SBFD". SBFD can also be called Flexible Full-Duplex (FDU).

[0096] Therefore, transmission time slots can have non-overlapping downlink (DL) subbands and (multiple) uplink (UL) subbands. These time slots are called SBFD time slots. However, there can also be time slots where the entire frequency band is used for either DL or UL, i.e., non-SBFD time slots.

[0097] There are two time slot types for DL ​​and UL transmissions: • Non-SBFD time slots, during which the entire frequency band is used for DL ​​or UL (i.e., conventional / full DL / UL time slots). • SBFD time slot, during which both non-overlapping DL subbands and (multiple) UL subbands exist.

[0098] SBFD introduces several types of cross-link interference CLI, which are called co-channel subband CLI and co-channel subband CLI.

[0099] Figure 2 Various intra-channel CLIs and cross-channel CLIs are schematically illustrated.

[0100] Figure 2 The diagram illustrates four types of CLIs that can occur in an SBFD deployment with the same frequency domain partitioning (i.e., non-overlapping frequency resources): 1. gNB self-interference 2. Intra-cell UE-to-UE co-channel subband CLI 3. Inter-cell CLI between UEs on the same channel subband (from non-overlapping frequency resources) 4. Inter-band CLI (from non-overlapping frequency resources) between gNB and gNB co-channel subbands.

[0101] In addition to the CLI types mentioned above, in cases of different frequency domain allocations in adjacent cells, the system may also suffer from co-channel CLI transmissions on overlapping frequency resources. In this regard, Figure 2 The diagram also schematically illustrates two types of CLIs that can occur in SBFD deployments with different frequency domain partitions (i.e., overlapping frequency resources): 5. In-band CLI (from overlapping frequency resources) between gNB and gNB co-channels 6. Inter-cell UE-to-UE subband shared channel CLI (from overlapping frequency resources)

[0102] The UE-to-UE CLI issue can occur in dynamic TDD deployments, where cells can choose TDD frame configurations in an inconsistent manner. CLIs can exist in a deployment if a given time slot is selected for two or more gNBs with opposite link directions. In this case, CLIs are generated in neighboring cells, hence the common term "inter-cell UE-to-UE CLI."

[0103] In SBFD operation, not only can UEs between cells cause CLI, but UEs within the same cell can also cause CLI, depending on whether the transmission in the UL subband of the harassing UE is leaked into the DL subband of another UE.

[0104] Figure 3 The diagram illustrates the UE-to-UE CLI. Specifically, Figure 3 The diagram illustrates various UE-to-UE co-channel cross-link interference types in an SBFD deployment.

[0105] Figure 3 A portion of network 100 is shown, including UE 110 and access node 120.

[0106] Intra-cell UE-to-UE co-channel subband CLI (from Figure 2 The “2” is schematically shown between the disturbed UE110_2 and the disturber UE110_1 (where both UEs are served by the same gNB 120_1).

[0107] Inter-UE to UE co-channel subband CLI (from Figure 2 The “3” or “6” is schematically shown between the disturbed UE 110_2 and the disturbing UE 110_4 (where the UE is served by different gNB 120_1 and gNB 120_2).

[0108] Next, we will discuss CLI measurements.

[0109] Release 16 introduced a UE-to-UE CLI measurement framework to support Dynamic Time Division Duplex (TDD). Release 16 also standardized two types of UE-to-UE cross-link interference measurements. One CLI measurement involves measuring the Reference Signal Received Power (RSRP) of the Sounding Reference Signal (SRS), also known as SRS-RSRP. The other CLI measurement involves measuring the Reference Signal Strength Indicator (RSSI) for a given set of resources, also known as CLI-RSSI.

[0110] SRS-RSRP can be defined (according to version 16) as a linear average of the power contribution (in [W]) of the resource element carrying SRS. SRS-RSRP can be measured on the configured resource element within the considered measurement frequency bandwidth at the configured measurement time.

[0111] CLI-RSSI can be defined (according to version 16) as a linear average of total received power (in [W]) that is observed only in the following: on the configured OFDM symbols of the configured measurement time resources (one or more), and in the configured measurement bandwidth from all sources (including co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).

[0112] Typically, (according to version 16) for CLI-RSSI, the UE is configured with a continuous resource set via higher-layer signaling, such as Layer 3L3 signaling, such as RRC signaling, in which measurements are expected to be performed. The resource configuration can be described as the RSSI-ResourceConfigCLI field as set forth in 3GPP TS 38.331 V16.15.1.

[0113] Basically, currently, the UE is configured via RRC messages based on the initial PRB, multiple PRBs (i.e., the measured bandwidth), and multiple symbols across the measurement.

[0114] In this regard, CLI-RSSI measurement resources are currently configured via RRC messages according to specific time, frequency domain, and periodicity (and other parameters). Similarly, SRS-RSRP measurement resources are configured via RRC messages following a specific SRSConfig (also periodic).

[0115] Using such periodic measurement resources may lead to the following problem: the periodic measurement resources may not overlap with the actual PUSCH allocation of the offending UE. This can be referred to as "CLI false detection." Therefore, this may result in incorrect / inaccurate estimation of the CLI state, such as... Figure 4 As shown.

[0116] Figure 4 The diagram schematically illustrates periodic CLI-RSSI measurements and potential “CLI false detections” in an SBFD deployment. Here, the UE (e.g., such as...) Figure 3 The UE #2 is configured to periodically measure CLI-RSSI (i.e., in the example shown, in time slots 1, 3, and 5...).

[0117] In this example, in the first time slot, there are no scheduled UL PUSCH transmissions overlapping with the configured periodic CLI-RSSI measurement resources. In this regard, transmissions from other UEs (e.g., Figure 3 The UL PUSCH transmissions of UE #1 and UE #3 do not overlap with the (first) periodic CLI-RSSI measurement. Therefore, no CLI will be measured. Similarly, in the fifth time slot, there are no UL PUSCH transmissions that overlap with the (third) configured CLI-RSSI measurement. Therefore, no CLI will be measured. Only in the third time slot is there a partial overlap between the UL PUSH (i.e., PUSCH UE #1) and the (second) periodic CLI-RSSI measurement.

[0118] Therefore, using periodic measurement resources (e.g., CL-RSSI resources) for UEs performing victim / CLI measurements may lead to issues where the periodic measurement resources do not overlap with the actual PUSCH resource allocation of the offending UE. This can result in false CLI detections and incorrect / inaccurate estimations of the CLI status, such as... Figure 4 As shown.

[0119] If CLI-RSSI resources are configured to fully encompass the UL subband, this will not provide CLI information about individual offending UEs. L3 measurements do not provide time-domain information; therefore, the gNB receiving the L3 CLI measurement report will be unable to estimate which UE is the offending UE / the UE with the strongest interference. Furthermore, averaging the measured CLI-RSSI over the configured resources when the offending UE is allocated only a small portion of the configured CLI-RSS resources may result in a low CLI level determination.

[0120] In SBFD deployments, CLIs can be generated due to intra-cell transmissions (see [link]). Figure 2 Interference component #2). Therefore, for a gNB, it would be advantageous to know the CLI at the transmission time interval (TTI) or time slot level. The gNB knows the UL allocation in its own cell, so the gNB can infer which UEs in its cell are transmitting when performing / conducting measurements.

[0121] The service gNB needs to be aware of the DL UE CLI status so that it can apply one or more CLI suppression schemes. Therefore, it is desirable to perform CLI measurements and report these measurements to the gNB for optimal SBFD operation.

[0122] Various examples of this disclosure present methods and apparatus for configuring CLI measurement resources.

[0123] In some, but not all, examples of this disclosure, CLI measurement resources for measuring both time and frequency domain resources can be configured to ensure that the resources overlap with a particular UL transmission.

[0124] Some, but not all, examples in this disclosure relate to UE-to-UE CLI measurements and reporting. Some, but not all, examples in this disclosure relate to configuring a UE to perform CLI measurements and report its CLI measurement results.

[0125] Attached Figure (i.e., Figure 5-11 The diagram shows devices 10 and 110, which include: Component 11 is used to receive configuration information 502 501 from access node 120 via physical layer signaling, the configuration information 502 being used to configure the device as follows: Perform at least one cross-link interference CLI measurement on at least one first resource 503, and At least one CLI measurement is reported via at least one second resource 504; Component 11 for enabling at least one CLI measurement to be performed based at least partially on configuration information; and Component 11 is used to report at least one CLI measurement based at least in part on configuration information.

[0126] Figure 5 A flowchart illustrating an example of method 500 according to this disclosure is shown schematically.

[0127] Figure 5 The component box is functional, and the described functionality can be derived from a single physical entity (such as a reference). Figure 11 The described function can also be performed by a computer program (such as reference 2010). Figure 12 The computer program described is used to implement this. Figure 5 It can be considered to demonstrate multiple methods, in a sense, Figure 5 This can be interpreted as demonstrating one or more actions performed by / at multiple participants / entities (e.g., (victim) UE 110 and (service) gNB 120). Therefore, Figure 5 This can be considered as illustrating multiple individual methods performed by each of the corresponding individual participants / entities among multiple participants / entities.

[0128] Figure 5 The boxes shown can represent actions in a method, functions performed by a device, and / or instruction / code portions in a computer program.

[0129] In box 501, UE 110 receives configuration information 502 from access node 120. This configuration information is received via physical layer signaling (i.e., Layer 1 (L1) signaling, such as DCI).

[0130] Configuration information 502 includes information for configuring the UE to perform CLI measurements on the first resource 503.

[0131] In some examples, the UE is configured to perform at least one of the following CLI measurements: UE to UE CLI measurements (such as) Figure 2 (2, 3, or 6 in the text) Non-periodic CLI measurement; Signal strength measurement of one or more signals received on the first resource (e.g., CLI-RSSI—examples of which will be referenced below). Figure 8 (Discussion); or Power measurement of the reference signal (e.g., SRS-RSRP—examples of which will be referenced below) Figure 9 discuss).

[0132] The first resource can be at least one time-domain resource and / or frequency-domain resource. In this respect, the first resource effectively defines when (i.e., at what time and location) and at what frequency / frequency range the UE will perform CLI measurements.

[0133] In some examples, the first resource includes at least one of the following: Time-domain resources, on which CLI measurements will be performed; The time-domain location at which CLI measurements will be performed; Duration during which CLI measurements will be performed; Frequency domain resources, on which CLI measurements will be performed; or One or more reference signal resources (e.g., time / frequency information that enables the UE to determine when and where to measure the RS, and the sequence ID of the RSRP that enables the measurement of the RS. Such RS resources may include time-domain information of the RS [start position within the time slot, number of symbols (duration)], frequency-domain information of the RS [frequency offset, bandwidth, transmission comb], and / or sequence identifier).

[0134] In some examples, instead of the gNB providing one or more parameters to the UE via configuration information 502 (which is received via L1 signaling such as DCI), the gNB may indicate a trigger state via DCI that points to a pre-configured SRS configuration (e.g., pre-configured via RRC).

[0135] In some examples, the configuration information includes one or more parameters for configuring the execution of CLI measurements. These parameters may involve indicating one or more of the following: The CLI measures the starting time and position (e.g., the "startPosition" parameter). CLI measures the time range / duration (e.g., the "nrofSymbols" parameter). CLI measurements will begin at the frequency position (e.g., the "startPRB" parameter), and The frequency range / bandwidth measured by CLI (e.g., the "nrofPRB" parameter).

[0136] Using physical layer L1 signaling (e.g., DCI) to configure the UE to perform CLI measurements can advantageously enable the execution of aperiodic CLI measurements. It can also allow for the configuration of faster / more dynamic CLI measurements, such as at the TTI or slot-level granularity.

[0137] In some examples, the UE is pre-configured with periodic resources for periodically transmitting reference signals (such as SRS). In this regard, the UE may have previously (e.g., particularly via RRC signaling) received configuration information for configuring periodic resources for the UE to periodically transmit reference signals. In this case, in some examples, configuration information 502 received in block 501 via L1 signaling for configuring the device to perform CLI measurements may include configuring the device to perform CLI measurements on one of the periodic resources instead of transmitting reference signals on that periodic resource. In this regard, configuration information 502 received in block 501 via L1 signaling can effectively override previously configured periodic transmissions of reference signals via assigned / scheduled periodic resources, and alternatively, one of those assigned / scheduled periodic resources can be used as the first resource 103 for performing CLI measurements. This will be discussed below. Figure 10 An example is described of reconfiguring / reusing previously configured assigned / scheduled periodic resources.

[0138] Configuration information 502 also includes information for configuring the UE to report CLI measurements via a second resource 504. The second resource can be at least one time-domain resource and / or frequency-domain resource. In this respect, the second resource effectively defines when (i.e., at what time and location) and at what frequency / frequency range the UE reports measurements.

[0139] In some examples, the second resource includes at least one of the following: Time-domain resources, CLI measurements using these time-domain resources will be reported; The time-domain location, at which CLI measurements will be reported; and Frequency domain resources, CLI measurements using these frequency domain resources will be reported.

[0140] In some examples, the configuration information includes an indication of a second resource through which CLI measurements will be reported. In some examples, the configuration information includes one or more parameters for configuring the reporting of CLI measurements. These parameters may involve indications of one or more of the following: CLI measurements will be reported at the time and location. CLI measurements will be reported at frequency locations. The type of report to be reported (e.g., the "reportType" parameter), and The metric to be reported (e.g., the “measurementMetric” parameter).

[0141] In some examples, configuration information 502, including indications of measurement resource 503 and reporting resource 504, is transmitted to the UE via a single physical layer / L1 message. In some examples, configuration information 502 is transmitted to the UE via two or more physical layer / L1 messages (e.g., a first L1 message including indications of measurement resource 503 and a second L1 message including indications of reporting resource 504).

[0142] Using physical layer (L1) signaling (e.g., DCI) to configure UE reporting CLI measurements can advantageously enable the execution of aperiodic CLI measurement reporting. It can also allow for faster / more dynamic CLI measurement reporting configuration, for example, at the TTI or time slot level.

[0143] In some examples, physical layer signaling used to send configuration information uses scrambled identifiers, such as identifiers used to provide a unique UE identifier (e.g., a temporary radio network identifier such as a cell radio network temporary identifier (C-RNTI)), or identifiers used to identify UE groups / associated with UE groups.

[0144] In some examples, configuration information is transmitted to the UE via DCI. In this regard, the DCI can: 1) Indicates resources used for CLI measurement purposes; and 2) Indicate the resources used for CLI reporting purposes.

[0145] In some examples, a new DCI format may be used in this regard. For example, as a non-limiting example, DCI format 5_0 is used to notify one or more UEs of CLI measurements and CLI reports.

[0146] In some examples, a modified legacy DCI format may be used. In this regard, a legacy DCI format may be used that includes indicators for informing the UE that the time / frequency resource indicated in the DCI will be used for a CLI measurement or CLI report. This legacy DCI format may be further modified to include an indication of another time / frequency resource that will be used for a CLI measurement or CLI report.

[0147] In block 505, the UE performs CLI measurements based on the configuration information received in block 501. In this respect, the UE performs CLI measurements on the configured first resource.

[0148] In block 506, the UE reports CLI measurements based on the configuration information received in block 501. In this regard, the UE reports CLI measurements to the access node via the configured second resource.

[0149] In some examples, CLI measurements are reported via physical layer signaling, such as uplink control information (UCI).

[0150] In some examples, the gNB applies interference suppression schemes based at least in part on received CLI measurement reports. In this respect, the gNB may adjust the SBFD's operating mode based at least in part on at least one received CLI measurement.

[0151] In some examples, such as about Figure 7 As shown, to avoid "CLI false detection" and ensure that CLI measurements are performed on resources overlapping with PUSCH transmissions from a specific (scratching) UE (i.e., to enable determination of the amount of interference from the scratching UE to the victim UE, where both UEs are served by the gNB), the gNB can send configuration information to the scratching UE via physical layer signaling. This configuration information is used to configure the scratching UE to transmit via the first resource 503. In this respect, the scratching UE is scheduled to transmit via the same resource that the victim UE is configured (in block 501) to use for CLI measurement.

[0152] Figure 6 and Figure 7 An example of a scheme for overlapping PUSCH and CLI measurements is illustrated to enable gNB120 to determine how many CLIs were created on one or more second (victim) UEs 110_2 by a UL PUSCH transmission from the first (scratcher) UE 110_1.

[0153] The gNB uses a UL DCI to indicate to the first UE 110_1 the resources for uplink transmission on the UL subband. This UL DCI is scrambled with a C-RNTI for the first UE 110_1 (the kth UE in the gNB's cell).

[0154] The gNB uses a DCI, in this example UL DCI 502 (or a new DCI format, or an existing DCI with a new purpose, as will be discussed further below), where UL DCI 502 does not schedule DL / UL transmissions (as is conventional), but rather indicates at least one aperiodic CLI measurement to one or more second UEs 110_2. In this respect, UL DCI 502 may indicate to one or more second (victim) UEs 110_2 a previously allocated "copy," i.e., resources for uplink transmissions on the UL subband indicated in the ULDCI for the first (scratcher) UE. In this respect, such resources indicated in UL DCI 502 correspond to measurement resources 503 for performing one or more CLI measurements.

[0155] One or more second UEs 110_2 can be promptly notified via UL DCI 502 (which can be scrambled with C-RNTI or CLI-RNTI, as discussed further below), and then CLI measurements can be performed on the assigned resources.

[0156] DCI 502 also includes further configuration information about the resource 504 that will be used for CLI reporting, as well as other reporting-related parameters.

[0157] As mentioned above, DCI 502 (indicating configuration information for configuring one or more second UE 110_2 to measure and report CLI) can be a new DCI format or an existing (albeit modified) DCI that can be reused. New DCI format

[0158] In some examples, such as in standards, new DCI formats are specified specifically for CLI purposes. As a non-limiting example, a new DCI could be added to TS38.212: DCI format 5_0 Used to notify one or more UEs of CLI measurements and CLI reports.

[0159] Such a DCI (e.g., DCI format 5_0) will include at least information about CLI measurement resource 503 and CLI reporting resource 504. For example, the time-domain location where the measured CLI is reported is indicated by, for example, a CLI-to-report parameter. This parameter may also indicate the duration from the indicated CLI measurement resource (or the time slot containing the indicated CLI measurement resource) to the reporting resource (or the time slot containing the reporting resource).

[0160] DCI can be UE-specific (e.g., if the DCI is scrambled using C-RNTI) or it can be a group-common DCI. For the latter, a new RNTI can be used to notify the set of UEs; such an RNTI can be called a cross-link interference, or "CLI-RNTI". This new RNTI can be added to already defined RNTIs, such as: Slot Format Indicator Radio Network Temporary Identifier (SFI-RNTI), Semi-Persistent CSI Radio Network Temporary Identifier (SP-RNTI), etc. Reusing existing DCI formats

[0161] Existing DCI formats (both existing UL DCI and existing DL DCI) can be reused to support CLI measurements through the following modifications / additions: a. Add an identifier, such as a flag or a 1-bit indication, to indicate that the received DCI is for CLI purposes, i.e., for CLI measurement and CLI reporting. This is useful for UE-specific DCIs (scrambled with C-RNTI). Alternatively, existing DCIs can be scrambled with the CLI-RNTI defined above, so that the UE (or multiple UEs) receiving the DCI knows that the DCI contains information about CLI measurement and CLI reporting. b. Attach new configuration information or parameters that at least indicate the time-frequency resources used for CLI measurements or CLI reporting. Typically, the existing DCI schedules only one set of resources for transmission. For example, DCI format 0_1 ​​points to a specific time and frequency resource for the scheduled PUSCH transmission. If DCI format 0_1 ​​is used for CLI purposes, the existing time / frequency assignment can be used to indicate the resource used for CLI reporting (i.e., reporting resource 504), but additional parameters are required to indicate CLI measurement resource 503.

[0162] Currently, aperiodic CSI-RS reporting is supported in NR, where the UE can measure CSI-RS "on demand" upon receiving a UL DCI (DCI format 0_1). This DCI contains the field "CSI Request" and an index pointing to one of the pre-configured CSI-RS in the CSI-AperiodicTriggerStateList. Therefore, the DCI contains information about the measurement resources and configuration for measuring the CSI-RS. The DCI also contains information indicating which resources the UE will use to send the required CSI report. For example, time information (i.e., the k2 parameter) is indicated by "time domain resource assignment." Further details about aperiodic CSI-RS can be found in TS38.214, section 5.2.3.

[0163] The UL DCI (DCI format 0_1) used to support non-periodic CSI-RS reporting can be modified as discussed above to support non-periodic CLI measurements and CLI reporting.

[0164] Unlike the aperiodic CSI-RS framework, CLI measurement resources can be dynamically changed based on the UL allocation of the offending UE. Therefore, the (modified) DCI used for CLI measurements and CLI reporting should: 1) Pointing to measurement resource 503, and 2) Indicates the resource used to send the report 504.

[0165] The latter can be supported using the same principles as those for aperiodic CSI-RS measurements. New parameters indicating the time and frequency allocation of the PUSCH to be measured (e.g., PUSCH transmissions from the interfering UE) are included in the DCI. These new parameters are used by the measuring UE to configure aperiodic CLI-RSSI measurement resources, specifically such as: startPosition, nrOfSymbols, startPRB, and nrofPRBs for CLI-RSSI measurement configuration.

[0166] gNB can be used to: New DCI for CLI purposes; Existing DCI (e.g., existing UL DCI or existing DL DCI) with C-RNTI scrambling (for individual UE configuration) and a 1-bit indication for CLI measurements; or Existing DCIs (e.g., existing UL DCIs or existing DL DCIs) are scrambled with CLI-RNTI (for UE group configuration).

[0167] DCI format 0_1 ​​can be used to trigger CLI-RSSI measurements. Typically, this DCI is used for PUSCH scheduling. However, when modified, for example, by appropriate indication, this DCI can be used for CLI measurement triggering. Between the configurations defined in the DCI, PUSCH time and frequency resources are defined by the fields “frequency domain resource assignment” and “time domain resource assignment”, respectively. These conventional parameters are then used to allocate PUSCH transport resources, which will contain CLI measurement reports, i.e., CLI report resource 504. New fields, such as “frequency domain CLI resource assignment” and “time domain CLI resource assignment”, can be added to this DCI and used to indicate measurement resources 503.

[0168] It should be noted that in the current specification, CLI-RSSI configurations are assumed to be continuous in time and frequency. Therefore, it can be assumed that the facility-disrupting PUSCH allocation is also continuous in time and frequency (i.e., type 1 frequency allocation). However, with the enhancements to CLI-RSSI measurement resources currently being considered in 3GPP, it is also possible that CLI-RSSI resources are not necessarily continuous in time and frequency. Therefore, in some possible examples, non-continuous PUSCH allocations (i.e., type 0 frequency allocations) may also be used with the examples of this disclosure.

[0169] In some examples, the details of the CLI report are pre-configured via RRC. In this regard, gNB configures different reporting parameters separately for each reporting configuration. In some examples, the following parameters are defined via RRC: reportType, measurementMetric, broadband or subband measurement, guard band measurement resources, spatial information, etc. The DCI then points to one of the possible reporting configurations via the "CLI request" field.

[0170] Figure 8 The diagram illustrates dynamic CLI-RSSI allocation based on DCI.

[0171] like Figure 8 As illustrated in the upper part, the first UE is assigned PUSCH resources via DCI instruction. This can be done in a conventional / traditional manner.

[0172] As in Figure 8 As schematically shown in the lower part, UE #2 is assigned CLI measurement resources 505 (which correspond in time and frequency resources to those assigned to the PUSCH transmission for UE #1) and CLI reporting resources 506 via DCI indication 502. In this respect, DCI indication 502 provides an explicit indication of the time and frequency resources for CLI measurement and CLI reporting.

[0173] Figure 9 The diagram illustrates an aperiodic SRS-RSRP measurement based on DCI.

[0174] like Figure 9 As schematically shown in the upper part, UE #1 is configured to send aperiodic SRS via DCI instruction.

[0175] like Figure 9 As schematically shown in the lower part, UE #2 is configured with CLI measurement resources 505 (which correspond in time and frequency resources to the time and frequency resources used for aperiodic SRS transmission of UE #1) and CLI reporting resources 506 via DCI instruction 502.

[0176] In some examples, DCI Instruction 502 provides explicit indication of the time and frequency resources used for CLI measurements and CLI reporting.

[0177] In some examples, the DCI can point to a specific SRS resource and measure SRS-RSRP, instead of relying on the PUSCH resource used to measure CLI-RSSI.

[0178] In some examples, gNB uses the following options to trigger CLI measurements based on aperiodic SRS: - Use the new DCI format; or - Using existing DCI scrambled with CLI-RNTI, make (multiple) notified UEs understand that this is not an aperiodic SRS trigger, but an aperiodic SRS-RSRP measurement trigger; or - Use the existing DCI scrambled with C-RNTI and add a new field (1 bit) to indicate whether the SRS is for CLI measurements or traditional SRS transmission.

[0179] Regarding instructions for measuring resources, in some examples, the gNB can: - Reuse the "SRS request" field to point to the SRS-RSRP measurement resource. If an existing DCI is used, this can be combined with one of the above indications to send a signaling notification; otherwise, the UE will assume that an aperiodic SRS transmission has been triggered. This field exists in existing UL and DL DCIs (see Table 7.3.1.1.2-24 of TS38.212). - Add a "CLI SRS-RSRP request field" to the new DCI format.

[0180] Regarding instructions for reporting resources, in some examples, gNB can: - The new DCI includes time and frequency assignments that specify which resources should include reports. For example, the "CLI-to-report" field can indicate the duration from the SRS measurement resource (or the time slot containing the indicated SRS measurement resource) to the reporting resource (or the time slot containing the reporting resource). Alternatively, the time / frequency assignments for the UL DCI can be included as part of the new DCI. - If using an existing UL DCI—the time / frequency assignment field in the UL DCI can be reused to point to a PUSCH resource that will include CLI reports. - If using existing DL DCI—DL DCI time resources can be indicated for reuse by reinterpreting the existing “PDSCH-to-HARQ_feedback” field. Therefore, the UE interprets it as the time interval (number of symbols) between performing a CLI measurement and reporting a CLI measurement, rather than indicating where HARQ feedback should be sent. Frequency resources used for CLI reporting can be indicated by the “PUCCH resource indicator” field. Reporting of CLI measurements can occur on the resources indicated by the DL DCI time / frequency assignment.

[0181] In some examples, the gNB refers to a specific configuration regarding how the UE should accurately perform SRS-RSRP measurements. This configuration may include indications such as: measurement beam, allowing measurements on the guard band, reporting absolute power or power ratio (UL subband / guard band), and a measurement scaling factor for deriving leakage interference, etc.

[0182] Regarding instructions for measurement / reporting configuration, in some examples, gNB: - A pre-configured set of RRC parameters, for example, the new SRS-CLIReportInfo IE. - DCI will include a pointer to one of the RRC configurations.

[0183] In the implementation of performing aperiodic SRS CLI measurements and CLI reporting, the aggressor UE will receive aperiodic SRS triggers via DCI (as traditionally supported). One or more victim UEs will receive indications of aperiodic SRS measurements on specific SRS resources. In this implementation, the network is expected to pre-configure SRS trigger states among multiple UEs so that at least one common configuration exists to ensure that measurement resources overlap with aperiodic SRS transmissions.

[0184] Figure 10 The illustration schematically shows the conversion of a periodic SRS transmission to a “zero-power” SRS (ZP-SRS) using DCI indication, and the measurement of CLI in the resources assigned to one of the periodic SRS transmissions in the periodic SRS transmission.

[0185] In this implementation, the gNB configures the same periodic SRS resources (period, offset, comb, duration, etc.) for a group of K UEs. In the example shown, K = 3, meaning the group consists of UE #1, UE #2, and UE #3. It should be noted that this configuration may not be optimal for traditional SRS transmission purposes (channel estimation, beam management, etc.), but it is useful / attractive from the perspective of UE-to-UE CLI measurements.

[0186] To perform CLI measurements, the gNB uses a new DCI to notify a subset of UEs (K-1 UEs) to silence their periodic SRS transmissions and, alternatively, perform CLI measurements on the same resources. In other words, SRS transmissions with an initial configuration known as Non-Zero Power SRS (NZP-SRS) are switched to Zero Power (ZP-SRS) via a DCI indication. For example, the new DCI may include a field for this purpose, "ZP SRS Indicator". This new configuration can then be applied to the next SRS transmission timing (given its periodicity). The notified UEs are assumed to be measuring SRS-RSRP on those resources (ZP-SRS resources).

[0187] The UE can know exactly which resources to measure because those resources were originally configured using SRS resource configuration.

[0188] By enabling this measurement to be performed and receiving its measurement report, the gNB can know the individual CLIs generated by the K-1 UEs in the k-th UE pair group.

[0189] The gNB can select different sets of UEs to notify each time an SRS occurs, in order to determine the intra-cell UE-to-UE mapping for each UE.

[0190] In some examples, DCI 502 also includes information about which resources should be used for CLI reporting. This reporting can occur before the next SRS timing or after the SRS-RSRP timing (and possibly several SRS-RSRP measurements). In the latter case, the UE should report the slot index along with each CLI measurement.

[0191] like Figure 10 As shown, at one point, the gNB (wanting to know how many CLIs were created by UE #1) dynamically instructs UE #2 and UE #3 via DCI instructions 502_1 and 502_2 to mute their next SRS transmission and instead perform CLI measurements 505_1 and 505_2. The gNB also dynamically instructs UE #2 and UE #3 via DCI instructions (not shown) on CLI reporting resources that will be used to report their respective CLI measurements (not shown).

[0192] Similarly, the gNB (wanting to know how many CLIs were created by UE #2) dynamically instructs UE #1 and UE #3 to mute their next SRS transmission via DCI instructions 502_3 and 502_4, and instead performs CLI measurements 505_3 and 505_4. The gNB also dynamically instructs UE #1 and UE #3 via DCI instructions (not shown) on CLI reporting resources that will be used to report their respective CLI measurements (not shown).

[0193] Figure 11 The illustration schematically shows the means for performing the actions described in this disclosure and Figure 5-10 A block diagram of the apparatus 10 showing the methods, processes, procedures, and signaling is provided. In this respect, in the methods shown and described, the apparatus can perform the role of UE 110 or gNB 120. Figure 11 The component box is functional, and the described functionality can be performed by a single physical entity.

[0194] The device includes a controller 11, which may be provided within a device such as a UE 110 or gNB 120.

[0195] The controller 11 can be implemented by a computing device, particularly those such as those mentioned above. In some, but not all, examples, the device can be implemented as a chip, chipset, circuit system, or module, i.e., any of the foregoing. For example, device 10 can be a module. For example, the controller 11 of device 10 can be a module.

[0196] As used in this article, "module" refers to a unit or device that excludes certain parts / components that will be added by the end-user manufacturer or user.

[0197] The controller 11 can be implemented as a controller circuit system. The controller 11 can be implemented solely in hardware, can have some aspects of software including independent firmware, or can be a combination of hardware and software (including firmware).

[0198] The controller 11 can be implemented using instructions that enable hardware functions, for example, by using executable instructions of a computer program 14 in a general-purpose or special-purpose processor 12, which can be stored on a computer-readable storage medium 13 (e.g., a memory or a disk) for execution by such a processor 12.

[0199] Processor 12 is configured to read from and write to memory 13. Processor 12 may also include output and input interfaces, wherein data and / or commands are output by processor 12 via the output interface and data and / or commands are input to processor 12 via the input interface. The device may be coupled to or include one or more other components 15 (especially, for example, radio transceivers, sensors, input / output user interface elements, and / or other modules / devices / components for inputting and outputting data / commands).

[0200] Memory 13 stores instructions, such as a computer program 14 including such instructions (e.g., computer program instructions / code), which controls the operation of device 10 when loaded into processor 12. The instructions of computer program 14 enable the device to perform the operations described in this disclosure and... Figure 5-10 The methods, processes, and program logic and routines shown are illustrated. Processor 12 is capable of loading and executing computer programs 14 by reading memory 13.

[0201] Instructions can be included in a computer program, a non-transitory computer-readable medium, a computer program product, or a machine-readable medium. As used herein, "non-transitory" refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., RAM and ROM). In some, but not all, examples, computer program instructions may be distributed across more than one computer program.

[0202] Although memory 13 is shown as a single component / circuit system, it can be implemented as one or more separate component / circuit systems, some or all of which may be integrated / removable and / or provide permanent / semi-permanent / dynamic / cached storage.

[0203] Although processor 12 is shown as a single component / circuit system, it can be implemented as one or more separate component / circuit systems, some or all of which can be integrated / removable. Processor 12 can be a single-core or multi-core processor.

[0204] The apparatus may include those for implementing the present disclosure and Figure 5 -10 One or more components of the methods, processes, and procedures shown. It is contemplated that the functionality of these components may be combined in one or more components, or performed by other components with equivalent functionality. The description of the functionality should also be considered as disclosing any parts suitable for performing that functionality.

[0205] Where a structural feature has been described, it may be replaced by a component that performs one or more functions of that structural feature, whether or not the function or these functions are explicitly or implicitly described.

[0206] While examples of the device have been described above from the perspective of various components, it should be understood that these components may be implemented as corresponding controllers or circuit systems, or otherwise controlled by corresponding controllers or circuit systems (such as one or more processing elements or processors of the device). In this regard, each of the aforementioned components may be one or more of any device, component, or circuit system implemented in hardware, software, or a combination of hardware and software, configured to perform the corresponding functions of the various components described above.

[0207] The device can be, for example, a client device, a server device, a UE, a mobile cellular phone, a base station in a mobile cellular communication system, a wireless communication device, a handheld portable electronic device, a location / positioning tag, a super tag, etc. The device can be implemented by a computing device, especially those mentioned above. However, in some examples, the device can be implemented as a chip, chipset, circuit system, or module, i.e., for any of the aforementioned purposes.

[0208] In one example, the device is implemented on a handheld portable electronic device, such as a mobile phone, mobile communication device, wearable computing device, or personal digital assistant, which may additionally provide one or more audio / text / video communication functions (e.g., telecommunications, video communication, and / or text transmission (Short Message Service (SMS) / Multimedia Messaging Service (MMS) / email) functions), interactive / non-interactive viewing functions (e.g., web browsing, navigation, TV / program viewing functions), music recording / playback functions (e.g., Mobile Image Experts Group-1 Audio Layer 3 (MP3) or other formats and / or (frequency modulation / amplitude modulation) radio broadcast recording / playback), data download / send data functions, image capture functions (e.g., using (e.g., a built-in) digital camera), and gaming functions, or any combination thereof.

[0209] In some examples, device 10 includes: At least one processor 12; and At least one memory 13 stores instructions that, when executed by at least one processor 12, cause the device to at least: Configuration information is received from the access node via physical layer signaling. This configuration information is used to configure the device as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; At least one CLI measurement is performed based on this configuration information, in part; and Report at least one CLI measurement, based at least in part on this configuration information.

[0210] The device can be provided within UE 110.

[0211] In an example where the device is provided within gNB 120, the device includes: At least one processor 12; and At least one memory 13 stores instructions that, when executed by at least one processor 12, cause the device to at least: This enables the transmission of configuration information to the User Equipment (UE) via physical layer signaling. This configuration information is used to configure the UE as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; At least one CLI measurement is received from the UE, based at least in part on configuration information.

[0212] The examples described above are used as enabling components for the following systems: telecommunications systems; tracking systems; automotive systems; electronic systems including consumer electronics; distributed computing systems; media systems for generating or presenting media content, including audio, video, and audiovisual content, as well as mixed reality, mediated reality, virtual reality, and / or augmented reality; personal systems including personal health systems or personal fitness systems; navigation systems; user interfaces, also known as human-machine interfaces; networks including cellular, non-cellular, and optical networks; self-organizing networks; the Internet; the Internet of Things (IoT); vehicle-to-everything (V2X) networks; virtualized networks; and related software and services.

[0213] According to the examples of this disclosure, the device can be provided in an electronic device, such as a mobile terminal. However, it should be understood that the mobile terminal is merely an exemplary illustration of an electronic device that can benefit from the embodiments of this disclosure and should not be construed as limiting the scope of this disclosure. Although in some implementation examples the device can be provided in a mobile terminal, other types of electronic devices, such as, but not limited to, mobile communication devices, handheld portable electronic devices, wearable computing devices, portable digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptops, cameras, video recorders, GPS devices, and other types of electronic systems, can readily adopt the examples of this disclosure. Furthermore, devices can readily adopt the examples of this disclosure, whether or not they are intended to provide mobility.

[0214] Figure 12 A computer program 14 that can be transmitted via delivery mechanism 20 is shown. Delivery mechanism 20 can be any suitable delivery mechanism, such as a machine-readable medium, computer-readable medium, non-transitory computer-readable storage medium, computer program product, storage device, solid-state storage, recording medium such as optical disc read-only memory (CD-ROM) or digital multifunction disc (DVD), or an article of manufacture that includes or tangibly implements computer program 14. The delivery mechanism can be a signal configured to reliably transmit the computer program. The device can receive, propagate, or transmit the computer program in the form of computer data signals.

[0215] In some examples of this disclosure, a computer program is provided, including instructions that, when executed by a device (e.g., device 10 or UE 110), cause the device to perform at least the following operations or to cause the following operations to be performed: Configuration information is received from the access node via physical layer signaling. This configuration information is used to configure the device as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; At least one CLI measurement is performed based on this configuration information, in part; and Report at least one CLI measurement, based at least in part on this configuration information.

[0216] In some examples of this disclosure, a computer program is provided, including instructions that, when executed by a device (e.g., device 10 or gNB 120), cause the device to perform at least the following operations: This enables the transmission of configuration information to the User Equipment (UE) via physical layer signaling. This configuration information is used to configure the UE as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; At least one CLI measurement is received from the UE, based at least in part on configuration information.

[0217] References to “computer program,” “computer-readable storage medium,” “computer program product,” “tangibly implemented computer program,” or “controller,” “computer,” “processor,” etc., should be understood to encompass not only computers with different architectures, such as single / multiprocessor architectures and sequential (von Neumann) / parallel architectures, but also special-purpose circuits, such as field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), signal processing devices, and other devices. References to computer programs, instructions, code, etc., should be understood to include software or firmware for programmable processors, such as programmable content for hardware devices, whether that programmable content is for processor instructions or for configuration settings for fixed-function devices, gate arrays, or programmable logic devices, etc.

[0218] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor (including digital signal processors), software, and memory (including multiple memory), which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g. firmware) to operate, but may be absent when not required for operation.

[0219] The definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" also covers only the implementation of hardware circuitry or processors and their accompanying software and / or firmware. The term "circuit system" also covers, for example and if applicable to elements of a particular claim, a baseband integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or networking device.

[0220] The boxes shown in the accompanying drawings may represent steps in the method and / or code portions in computer program 14. The illustration of a specific order of boxes does not imply a required or preferred order, and the order and arrangement of boxes can vary. Furthermore, some boxes may be omitted.

[0221] Where a structural feature has been described, it may be replaced by a component that performs one or more functions of that structural feature, whether or not the function or these functions are explicitly or implicitly described.

[0222] It should be understood that Figure 3 and 6 Each box and combination of boxes shown, as well as the additional functions described above, can be implemented by various components, such as hardware, firmware, and / or software including one or more computer program instructions. For example, one or more of the functions described above can be implemented by appropriately configured means (such as means including components for performing the functions described above [e.g., ...). Figure 11 [As shown]) to perform. One or more of the above functions / functionalities can be performed by a properly configured computer program (such as a computer program [e.g. Figure 12 As shown, the program includes computer program instructions that implement the functions described above, and these instructions can be stored in a storage device and executed by a processor.

[0223] It should be understood that any such computer program instructions can be loaded onto a computer or other programmable device (i.e., hardware) to produce a machine, such that when executed on the programmable device, these instructions create components for implementing the functions / functionality specified in the box. These computer program instructions can also be stored in a computer-readable medium that can instruct the programmable device to operate in a particular manner, causing the instructions stored in the computer-readable medium to produce an article of manufacture, including instruction components that implement the functions / functionality specified in the box. The computer program instructions can also be loaded onto the programmable device to cause a series of operational actions to be performed on the programmable device, thereby producing a computer-implemented process, such that the instructions executed on the programmable device provide actions for implementing the functions / functionality specified in the box.

[0224] Various, but not all, examples of this disclosure may take the form of methods, apparatus, or computer programs. Therefore, various, but not all, examples may be implemented in hardware, software, or a combination of hardware and software.

[0225] Various, but not all, examples of this disclosure are described using flowchart illustrations and schematic block diagrams. It should be understood that each block (in the flowchart illustrations and block diagrams) and combinations of blocks can be implemented by computer program instructions of a computer program. These program instructions can be provided to one or more processors, processing circuits, or controllers such that instructions executing on the processor, processing circuit, or controller create components for implementing the functions specified in the one or more blocks, i.e., enabling the method to be implemented by a computer. The computer program instructions can be executed by a processor to cause the processor to perform a series of operation blocks / steps / actions, thereby producing a computer-implemented process, such that instructions executing on the processor provide blocks / steps for implementing the functions specified in the one or more blocks.

[0226] Therefore, a box supports: combinations of components for performing a specified function; combinations of actions for performing a specified function; and computer program instructions / algorithms for performing a specified function. It should also be understood that each box and combination of boxes can be implemented by a dedicated hardware system performing the specified function or action, or by a combination of dedicated hardware and computer program instructions.

[0227] Various, but not all, examples of this disclosure provide methods and corresponding apparatuses, including various modules, components, or circuit systems that provide functionality for performing / applying the actions of the method. These modules, components, or circuit systems may be implemented as hardware or as software or firmware executed by a computer processor. In the case of firmware or software, examples of this disclosure may be provided as computer program products including computer-readable storage structures on which computer program instructions (i.e., software or firmware) are implemented for execution by a computer processor.

[0228] Although this article uses specific terms, they are used only in a general and descriptive sense, not for restrictive purposes.

[0229] The features described above can be used in combinations other than those explicitly described.

[0230] Although functions have been described with reference to specific features, these functions can be performed by other features regardless of whether they are described.

[0231] Although features have been described with reference to specific examples, these features may exist in other examples, whether or not they are described. Therefore, a feature described with respect to one example / aspect of this disclosure may include any or all features described with respect to another example / aspect of this disclosure, and vice versa, provided that they do not contradict each other.

[0232] A description of features (such as means or components of means) configured to perform a function or for performing a function should also be considered as disclosing a method for performing that function. For example, a description of a means configured to perform one or more actions or for performing one or more actions should also be considered as disclosing a method for performing one or more actions with or without that means. Similarly, a description of a method for performing a function or implementing a function should also be considered as disclosing a means or component of a means or component configured to perform / implement that function, or a part for performing / implementing that function.

[0233] The term "comprising" is used herein in an inclusive rather than exclusive sense. That is, any reference to X that includes Y indicates that X may include only one Y, or may include more than one Y. In some cases, "at least one" or "one or more" may be used to emphasize the inclusive meaning, but the omission of these terms should not be taken as an inference of any exclusive meaning. If the intention is to use "comprising" with an exclusive meaning, it will be clearly indicated in the context by referring to "including only one..." or by using "consisting of...".

[0234] In this specification, the terms “connection,” “coupling,” and “communication,” and their derivatives, mean operationally connected / coupled / in communication. It should be understood that any number or combination of intermediate components (including no intermediate components) may be present to provide direct or indirect connection / coupling / communication. Any such intermediate component may include hardware and / or software components.

[0235] As used herein, the term "determine" (and its grammatical variations) can include, but is not limited to: evaluation, calculation, operation, processing, derivation, measurement, investigation, identification, lookup (e.g., searching in a table, database, or other data structure), ascertainment, etc. Additionally, "determine" can include receiving (e.g., receiving information), retrieving / accessing (e.g., retrieving / accessing data in memory), obtaining, etc. Furthermore, "determine" can include parsing, selecting, picking, building, inferring, etc.

[0236] As used herein, descriptions of actions should also be considered as disclosing enabling, and / or causing, and / or controlling the action. For example, a description of transmitting information should also be considered as disclosing enabling, and / or causing, and / or controlling the transmission of information. Similarly, for example, a description of a means of transmitting information should also be considered as disclosing at least one component or controller of the means for enabling, and / or causing, and / or controlling the means of transmitting the information.

[0237] The term "component" as used in the specification and claims may refer to one or more individual elements configured to perform the corresponding one or more functions, or it may refer to several elements performing such one or more functions. Furthermore, the several functions described in the claims may be performed by the same individual components or the same combination of components. For example, the performance of such one or more functions may be caused by a processor in the device that executes instructions stored in the memory of the device.

[0238] Unless explicitly stated otherwise (unless the context requires otherwise), references to parameters or parameter values ​​should be understood as referring to "data indicating the relevant parameter / value," "data defining the relevant parameter / value," or "data representing the relevant parameter / value." Data can indicate the relevant parameter / value in any way and can indicate the relevant parameter / value directly or indirectly.

[0239] Various examples have been referenced in this specification. Descriptions of features or functionalities of an example indicate that such features or functionalities exist in that example. Whether explicitly stated or not, the terms “example” or “for example,” “can” or “may” are used herein to indicate that such features or functionalities exist at least in the described example, whether or not they are described as examples, and that they may, but not all, exist in some or all of the other examples. Therefore, “example,” “for example,” “can,” or “may” refers to a specific instance of a class of examples. The properties of that instance may be properties only of that instance, or properties of the class, or properties of a subclass of the class, which includes some but not all instances of the class.

[0240] In this specification, references to “a / an / that” [feature, element, component, part…] are used in an inclusive rather than exclusive sense and should be interpreted as “at least one” [feature, element, component, part…] unless otherwise expressly stated. That is, any reference to X including one / that Y indicates that X may include only one Y or may include more than one Y, unless the context clearly indicates the opposite. If the use of “a” or “that” with an exclusive meaning is intended, it will be clearly stated in the context. In some cases, the use of “at least one” or “one or more” may be used to emphasize an inclusive meaning, but the omission of these terms should not be construed as inferring any exclusive meaning.

[0241] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, wherein a list of two or more elements connected by “and” or “or” means at least any one element, or at least any two or more elements, or at least all elements.

[0242] The presence of a feature (or combination of features) in a claim is a reference to that feature (or combination of features) itself, and also a reference to a feature (equivalent feature) that achieves substantially the same technical effect. Equivalent features include, for example, variant features that achieve substantially the same result in substantially the same manner. Equivalent features include, for example, features that perform substantially the same function in substantially the same manner to achieve substantially the same result.

[0243] In this specification, various examples of using adjectives or adjective phrases to describe example features have been referenced. Such descriptions of example features indicate that the feature exists exactly as described in some examples, and substantially as described in others.

[0244] In the foregoing description, the described apparatus may alternatively or additionally include apparatuses that, in some other examples, include distributed systems of apparatuses, such as client / server apparatus systems. In examples where the provided apparatuses form (or the methods are implemented as) a distributed system, each apparatus that forms a component and / or part of the system provides (or implements) one or more features that collectively implement the embodiments of this disclosure. In some examples, the apparatuses are reconfigured by an entity other than their original manufacturer to implement the embodiments of this disclosure, which is achieved by providing additional software, for example, by a user downloading such software, which, when executed, causes the apparatus to implement the embodiments of this disclosure (such implementation is either entirely implemented by the apparatuses or as part of the apparatus system mentioned above).

[0245] The foregoing description illustrates some examples of this disclosure; however, those skilled in the art will recognize possible alternative structural and methodological features that provide equivalent functionality to specific examples of such structures and features described above, and these have been omitted from the foregoing description for the sake of brevity and clarity. Nevertheless, unless such alternative structural or methodological features are explicitly excluded in the foregoing description of the examples of this disclosure, the foregoing description should be construed as implicitly including references to such alternative structural and methodological features that provide equivalent functionality.

[0246] However, while efforts have been made in the foregoing specification to draw attention to those features considered particularly important in the examples disclosed herein, it should be understood that the applicant claims protection for any patentable features or combinations of features mentioned above and / or shown in the figures, whether or not they have been specifically emphasized.

[0247] The examples and appended claims of this disclosure may be suitably combined in any manner apparent to a person skilled in the art. Separate references to “example,” “in some examples,” and / or similar expressions in the specification do not refer to the same examples and are not mutually exclusive unless so stated and / or otherwise readily apparent to a person skilled in the art from the description. For example, a feature, structure, process, block, step, action, etc., described in one example may be included in other examples, but is not necessarily included.

[0248] Although examples have been described with reference to various examples in the preceding paragraphs, it should be understood that modifications may be made to the given examples without departing from the scope of the claims.

[0249] Each claim is incorporated herein as further disclosure, and the claims are embodiments of this disclosure. Furthermore, although the claims herein are provided to include specific referential relationships, it is contemplated that any claim may refer to any other claim, and any alternative embodiments that may arise from combining, integrating, and / or omitting and / or changing the referential relationships of the various claims, any such alternative embodiments and their equivalents are also within the scope of this disclosure.

Claims

1. An apparatus comprising: A component for receiving configuration information from an access node via physical layer signaling, the configuration information being used to configure the device as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; Components for performing at least one CLI measurement based at least in part on the configuration information; as well as A component for reporting the at least one CLI measurement based at least in part on the configuration information.

2. The apparatus according to any one of the preceding claims, wherein the configuration information includes at least one indication of at least one of the following: The at least one first resource, on which the at least one CLI measurement will be performed; The at least one second resource, via which the at least one CLI measurement will be reported; At least one parameter for configuring the execution of the at least one CLI measurement; or At least one parameter for configuring the report of the at least one CLI measurement.

3. The apparatus according to any one of the preceding claims, wherein the configuration information includes: Information indicating at least one resource; as well as At least one indicator, which indicates the device: Use the at least one resource to perform the at least one CLI measurement, or Use the at least one resource to report the at least one CLI measurement.

4. The apparatus according to any one of the preceding claims, wherein the at least one first resource comprises at least one of the following: At least one time-domain resource, on which the at least one CLI measurement will be performed; At least one time-domain location, at which the at least one CLI measurement will be performed; At least one duration, during which the at least one CLI measurement will be performed; At least one frequency domain resource, on which the at least one CLI measurement will be performed; or At least one reference signal resource.

5. The apparatus according to any one of the preceding claims, wherein the at least one second resource comprises at least one of the following: At least one time-domain resource, using which the at least one time-domain resource will be reported; At least one time-domain location, at which the at least one CLI measurement will be reported; as well as At least one frequency domain resource, using which the at least one CLI measurement will be reported.

6. The apparatus according to any one of the preceding claims, wherein the at least one CLI measurement is reported via at least one of the following: Physical layer signaling; or Uplink Control Information (UCI).

7. The apparatus according to any one of the preceding claims, wherein the at least one CLI measurement comprises at least one of the following: User equipment (UE) to UE CLI measurement; Non-periodic CLI measurement; At least one signal strength measurement of one or more signals received on the at least one first resource; or At least one power measurement of at least one reference signal.

8. The apparatus according to any one of the preceding claims further comprises: A component for receiving configuration information for the following: configuring periodic resources for the device to periodically transmit reference signals; as well as The configuration information for configuring the device to perform at least one CLI measurement includes configuration information for: configuring the device to perform at least one CLI measurement on the at least one periodic resource instead of transmitting the reference signal on the periodic resource.

9. The apparatus according to any one of the preceding claims further comprises: A component for receiving configuration information for the following: configuring periodic resources for the device to periodically transmit reference signals; as well as The configuration information for configuring the device to perform at least one CLI measurement includes configuration information for defining at least one periodic resource of the periodic resource as the at least one first resource.

10. The apparatus according to any one of the preceding claims, wherein receiving the configuration information via physical layer signaling comprises: Receive configuration information via a first physical layer signal for: configuring the device to perform the at least one CLI measurement on the at least one first resource; as well as Configuration information is received via a second physical layer signal for configuring the device to report the at least one CLI measurement on the at least one second resource.

11. The apparatus according to any one of the preceding claims, wherein the physical layer signaling is scrambled at least in part based on one or more of the following: Identifier; Identifier used to identify the device; UE-specific identifier; An identifier used to identify the UE group; or Temporary wireless network identifier.

12. A user equipment (UE), the UE comprising the means of any one of the preceding claims.

13. A method comprising: At the device, configuration information is received from the access node via physical layer signaling. This configuration information is used to configure the device as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; The at least one CLI measurement is performed based at least in part on the configuration information; and The at least one CLI measurement is reported based at least in part on the configuration information.

14. A computer program comprising instructions that, when executed by a device, cause the device to perform the method according to claim 13.

15. An apparatus comprising: A component for enabling the transmission of configuration information to a user equipment (UE) via physical layer signaling, the configuration information being used to configure the UE as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; A component for receiving at least one CLI measurement from the UE based at least in part on the configuration information.

16. The apparatus of claim 15, further comprising: Components for applying an interference suppression scheme based at least in part on the received at least one CLI measurement.

17. The apparatus according to claim 15 or 16, further comprising: A component for adjusting the subband non-overlapping full-duplex SBFD operating mode based at least in part on the received at least one CLI measurement.

18. The apparatus according to claim 15, 16 or 17, further comprising: A component for causing configuration information for sending to a second UE via physical layer signaling for: configuring the UE to send transmissions via the at least one first resource.

19. An access node comprising the means according to any one of claims 15 to 18.

20. A method comprising: This enables the transmission of configuration information to the User Equipment (UE) via physical layer signaling, the configuration information being used to configure the UE as follows: Perform at least one cross-link interference CLI measurement on at least one first resource, and At least one CLI measurement was performed via at least one second resource report; The at least one CLI measurement is received from the UE based at least in part on the configuration information.

21. A computer program comprising instructions that, when executed by a device, cause the device to perform the method according to claim 20.