Cross link interference (CLI) reporting based on physical uplink shared channel (PUSCH) measurement in full duplex

Abstract

A victim user equipment (UE) may experience cross-link interference (CLI) from aggressor UE's Physical Uplink Shared Channel (PUSCH) transmissions, or self-interference (SI) from the victim UE's transmitter's PUSCH transmissions. This disclosure provides configurations for measurement resources and CLI reporting to mitigate CLI. The base station can transmit configurations for measurement resources, including Channel State Information Interference Measurement (CSI-IM) resources, and CLI reporting. The CSI-IM resources are matched with the aggressor UE's PUSCH symbols or Demodulation Reference Signal (DMRS) symbols. The victim UE measures CLI or SI on the CSI-IM resources. The victim UE reports CLI or SI to the base station according to the CLI reporting configuration. The base station can schedule transmissions to mitigate CLI or SI.

Description

Technical Field

[0001] This disclosure generally relates to communication systems, and more specifically, to cross-link interference measurement in full-duplex communication. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple-access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMB) initiative issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., scalability with the Internet of Things (IoT), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0004] The following is a brief overview of one or more aspects to provide a basic understanding of them. This overview is not a comprehensive summary of all anticipated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the detailed descriptions that follow.

[0005] In one aspect of this disclosure, a method, non-transitory computer-readable medium, and apparatus for a victim user equipment (UE) are provided. The method may include configuring measurement resources, including channel state information interference measurement (CSI-IM) resources, and configuring cross-link interference (CLI) reports from a base station. The CSI-IM resources may be matched with a physical uplink shared channel (PUSCH) symbol or demodulation reference signal (DMRS) symbol of the aggressor UE. The method may include measuring CLI or self-interference (SI) on the CSI-IM resources. The method may include reporting CLI or SI to the base station according to the CLI reporting configuration.

[0006] In some implementations, CLI or SI includes values ​​for each DMRS symbol.

[0007] In some implementations, CLI or SI includes the average value on the DMRS symbol.

[0008] In some implementations, the configuration of measurement resources includes the ratio of the Energy Per Resource Element (EPRE) of a PUSCH symbol to the EPRE of a DMRS symbol. Measuring the CLI or SI may include adjusting the CLI based on this ratio. The configuration of measurement resources may include multiple CSI-IM resources and a list of scaling values, each scaling value corresponding to one CSI-IM resource.

[0009] In some implementations, the configuration for receiving measurement resources and CLI reports includes an indication of the PUSCH bandwidth for dynamically scheduled PUSCH transmissions for the aggressor UE.

[0010] In some implementations, the configuration of measurement resources includes aperiodic CSI-IM resources matched to the PUSCH bandwidth.

[0011] In some implementations, the CLI report configuration indicates a non-periodic CLI report for subband CLI corresponding to the frequency domain allocation of PUSCH transmission.

[0012] In some implementations, the configuration of measurement resources includes periodic or semi-persistent CSI-IM, wherein the frequency domain allocation of the CSI-IM changes over time slots. CLIs or SIs on the measurement CSI-IM resources may cyclically cycle over a sequence of frequency domain allocations. CLIs or SIs on the measurement CSI-IM resources may follow a deterministic finite state machine with parameters configured by the configuration of the measurement resources. The frequency domain allocation of the CSI-IM resources may follow predefined rules based on a time slot format.

[0013] In some implementations, the configuration of receiving measurement resources includes receiving Group Common Downlink Control Information (DCI) that dynamically schedules PUSCH transmissions for the aggressor UE.

[0014] In some implementations, the group common DCI includes a first portion that schedules PUSCH transmissions and a second portion that includes one or more blocks, each block indicating a CSI-IM resource set, wherein the victim UE is configured with an index corresponding to one of the one or more blocks.

[0015] In some implementations, the method further includes: using pre-configured rules, based on the victim UE's PUSCH radio resource control (RRC) configuration, to determine one or more DMRS locations within resources for the aggressor UE's PUSCH transmissions; and determining a mapping between one or more DMRS locations and CSI-IM resources.

[0016] In some implementations, the victim UE is configured with CSI-IM resource sets covering different symbols at different DMRS locations. Determining the mapping may include selecting CSI-IM resource sets covering one or more DMRS locations.

[0017] In some implementations, the victim UE is configured with a mapping between CSI-IM resource sets and DMRS locations.

[0018] In some implementations, receiving the configuration of measurement resources includes: receiving one or more semi-persistent scheduling (SPS) configurations for CSI-IM resources, each SPS configuration corresponding to a corresponding configuration grant for PUSCH transmission for the aggressor UE; and receiving a group common DCI that activates one of the SPS DL configurations and its corresponding UL configuration grant.

[0019] In some implementations, configuring the received measurement resources includes configuring the received semi-persistent CSI-IM resources. The periodicity and offset of the semi-persistent CSI-IM resources can be matched to the configuration permissions of the aggressor UE. The semi-persistent CSI-IM resources can be activated by a Media Access Control (MAC) control element (CE). The semi-persistent CSI-IM resources can be activated by a common DCI comprising one or more blocks, each block indicating the set of CSI-IM resources to be activated. The victim UE can be configured with an index corresponding to one of the one or more blocks.

[0020] In some implementations, reporting CLI to the base station includes determining to discard the report when the CLI value is less than a configured threshold.

[0021] In some implementations, reporting CLI to the base station includes reporting CLI regardless of whether a PUSCH transmission occurs on the CSI-IM resource.

[0022] In some implementations, receiving the configuration of measurement resources includes: receiving one or more semi-persistent scheduling (SPS) configurations for CSI-IM resources, each SPS configuration corresponding to a corresponding configuration permission for PUSCH transmissions for the aggressor UE; receiving the configuration of the semi-persistent CSI-IM resources, wherein the periodicity and offset of the semi-persistent CSI-IM resources are matched with the configuration permission of the aggressor UE; and receiving the configuration based on the semi-persistent CSI-IM resources to activate one of the SPS DL configurations and a group of common DCIs reported by CLI.

[0023] In some implementations, the configuration of the received measurement resources includes the configuration of the received semi-persistent CSI-IM resources and the Transmission Configuration Indicator (TCI) status of the CSI-IM, which indicates the Quasi-Cooperative Positioning (QCL) spatial reception parameters.

[0024] In some implementations, the configuration of the measurement resource indicates the TCI status associated with each semi-persistent CSI-IM resource. The measurement CLI may include, for each instance of the semi-persistent CSI-IM resource, using the TCI status associated with each semi-persistent CSI-IM resource.

[0025] In some implementations, the configuration of the measurement resource indicates a list of TCI states associated with the semi-persistent CSI-IM resource. The measurement CLI may include cycling through the list of TCI states for multiple instances of the semi-persistent CSI-IM resource.

[0026] In some implementations, the configuration of the measurement resource indicates a sequence of TCI state lists associated with the semi-persistent CSI-IM resource, wherein the measurement CLI includes cycling through multiple instances of the semi-persistent CSI-IM resource on the TCI state list. The victim UE can use one of the TCI state lists for each instance of the semi-persistent CSI-IM resource.

[0027] In some implementations, reporting CLI to the base station includes determining to discard the report when the CLI value is less than a configured threshold.

[0028] In some implementations, the CLI value is an average of CLI values ​​for the same QCL space reception parameters, and the report includes a pair of CLI values ​​and QCL space reception parameters.

[0029] In some implementations, the CLI value is the average of the CLI values ​​of all QCL space reception parameters.

[0030] In some implementations, the method further includes transmitting an indication of whether the victim UE supports one or more of the following: CLI or SI measurements in CSI-IM resources; a common DCI for PUSCH configuration; a common DCI for triggering CLI measurements and reporting; an explicit or implicit indication of CSI-IM resources in a common DCI; a common DCI for triggering configuration permission in the uplink; a common DCI for triggering SPS in the downlink; a common DCI for triggering semi-persistent CSI-IM resources; a common DCI for triggering semi-persistent CLI reporting; a QCL for CLI measurements; or a different QCL for the timing of semi-persistent CSI-IM measurements.

[0031] In another aspect, a method, non-transitory computer-readable medium, and apparatus for a base station are provided. The method may include a configuration for transmitting PUSCH transmissions, including PUSCH symbols and DMRS symbols, to an aggressor UE. The method may include a configuration for transmitting measurement resources, including CSI-IM resources, and CLI reports to a victim UE. The CSI-IM resources are matched with the PUSCH symbols or DMRS symbols of the aggressor UE. The method may include receiving CLI or SI measurements based on the configuration of the measurement resources.

[0032] In some implementations, CLI or SI measurements include values ​​for each DMRS symbol.

[0033] In some implementations, the CLI or SI measurement includes an average value on the DMRS symbol.

[0034] In some implementations, the configuration of measurement resources includes the ratio of the EPRE of the PUSCH symbol to the EPRE of the DMRS symbol.

[0035] In some implementations, the configuration of measurement resources includes multiple CSI-IM resources and a list of scaling values, with each scaling value corresponding to a CSI-IM resource.

[0036] In some implementations, the configuration of measurement resources includes an indication of the PUSCH bandwidth for dynamically scheduled PUSCH transmissions for the aggressor UE.

[0037] In some implementations, the configuration of measurement resources includes aperiodic CSI-IM resources matched to the PUSCH bandwidth.

[0038] In some implementations, the CLI report configuration indicates an aperiodic CLI report corresponding to the frequency domain allocation of the PUSCH transmission for subband CLI.

[0039] In some implementations, the configuration of measurement resources includes periodic or semi-persistent CSI-IM, wherein the frequency domain allocation of the CSI-IM resources changes over time slots.

[0040] In some implementations, CLI or SI measurements are cyclically performed on a frequency domain allocation sequence.

[0041] In some implementations, CLI or SI measurements follow a deterministic finite state machine with parameters configured by the configuration of the measurement resources.

[0042] In some implementations, CSI-IM resource frequency domain allocation follows predefined rules based on time slot format.

[0043] In some implementations, the configuration of measurement resources includes group common DCI for dynamically scheduling PUSCH transmissions for the aggressor UE.

[0044] In some implementations, the group common DCI includes a first portion that schedules PUSCH transmissions and a second portion that includes one or more blocks, each block indicating a CSI-IM resource set. The victim UE may be configured with an index corresponding to one of the one or more blocks.

[0045] In some implementations, the configuration of measurement resources includes: one or more SPS DL configurations for CSI-IM resources, each SPS DL configuration corresponding to a corresponding configuration license for a PUSCH transmission for an aggressor UE; and a group common DCI activating one of the SPSDL configurations and its corresponding UL configuration license.

[0046] In some implementations, the configuration of measurement resources includes the configuration of semi-persistent CSI-IM resources. The periodicity and offset of the semi-persistent CSI-IM resources can be matched with the configuration permissions of the aggressor UE.

[0047] In some implementations, the semi-persistent CSI-IM resource is activated by MAC-CE.

[0048] In some implementations, semi-persistent CSI-IM resources are activated by a group common DCI comprising one or more blocks, each block indicating a set of CSI-IM resources to be activated, wherein the victim UE is configured with an index corresponding to one of the one or more blocks.

[0049] In some implementations, receiving CLI or SI measurements based on the configuration of measurement resources includes filtering CLI or SI based on whether the aggressor UE transmitted a PUSCH transmission.

[0050] In some implementations, the configuration of measurement resources includes: one or more SPS configurations for CSI-IM resources, each SPS configuration corresponding to a corresponding configuration permission for PUSCH transmissions for the aggressor UE; configuration of semi-persistent CSI-IM resources, wherein the periodicity and offset of the semi-persistent CSI-IM resources are matched with the configuration permission of the aggressor UE; and activation of one of the SPS DL configurations and a group of common DCIs reported by CLI based on the configuration of the semi-persistent CSI-IM resources.

[0051] In some implementations, the configuration of measurement resources includes the configuration of semi-persistent CSI-IM resources and the TCI status of CSI-IM indicating QCL spatial reception parameters.

[0052] In some implementations, the configuration of the measurement resources indicates the TCI status associated with each semi-persistent CSI-IM resource.

[0053] In some implementations, the configuration of the measurement resource indicates a list of TCI states associated with the semi-persistent CSI-IM resource.

[0054] In some implementations, the configuration indication of the measurement resource is a sequence of TCI status lists associated with the semi-persistent CSI-IM resource.

[0055] In some implementations, CLI is measured as an average of CLI values ​​for the same QCL spatial reception parameters, and the report includes a pair of CLI values ​​and QCL spatial reception parameters.

[0056] In some implementations, CLI is measured as the average of CLI values ​​across all QCL space reception parameters.

[0057] In some implementations, the method may further include receiving an indication of whether the victim UE supports one or more of the following: CLI or SI measurements in CSI-IM resources; a common DCI for PUSCH configuration; a common DCI for triggering CLI measurements and reporting; an explicit or implicit indication of CSI-IM resources in a common DCI; a common DCI for triggering configuration permission in the uplink; a common DCI for triggering SPS in the downlink; a common DCI for triggering semi-persistent CSI-IM resources; a common DCI for triggering semi-persistent CLI reporting; a QCL for CLI measurements; or a different QCL for the timing of semi-persistent CSI-IM measurements.

[0058] In one aspect of this disclosure, a method, non-transitory computer-readable medium, and apparatus for an aggressor UE are provided. The method may include receiving a Group Common Digital Interface (DCI). The DCI may include a first portion scheduling PUSCH transmissions for the aggressor UE and a second portion comprising one or more blocks, each block indicating a CSI-IM resource set for one or more victim UEs. The method may include determining a PUSCH configuration based on the DCI. The method may include transmitting PUSCH transmissions based on the PUSCH configuration.

[0059] In some implementations, the group common DCI dynamically schedules PUSCH transmissions for the intruder UE.

[0060] In some implementations, the group public DCI activates configuration permissions for the aggressor UE and corresponding SPS DL configurations for one or more victim UEs.

[0061] In some implementations, group public DCI activation enables configuration permissions for the aggressor UE and configuration of corresponding semi-persistent CSI-IM resources for one or more victim UEs.

[0062] In some implementations, the method also includes transmitting an indication that the aggressor UE supports a group public DCI for triggering configuration permission in the uplink.

[0063] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect can be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0064] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network according to certain aspects of this description.

[0065] Figure 2A This is a diagram illustrating an example of the first frame according to certain aspects of this description.

[0066] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to certain aspects of this description.

[0067] Figure 2C This is a diagram illustrating an example of the second frame according to certain aspects of this description.

[0068] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to certain aspects of this description.

[0069] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network according to certain aspects of this description.

[0070] Figure 4A , Figure 4B and Figure 4C An exemplary mode of full-duplex communication is shown.

[0071] Figure 5A and Figure 5B An example of an in-band full-duplex (IBFD) resource is shown.

[0072] Figure 5C An example of resources for subband full-duplex communication is shown.

[0073] Figure 6 This is an example that includes time and frequency resources for full-duplex resources.

[0074] Figure 7A and Figure 7B Examples of intra-cell and inter-cell interference are shown.

[0075] Figure 8 Example resources for the first UE and the second UE are shown.

[0076] Figure 9 Example group common downlink control information (DCI) is shown.

[0077] Figure 10 This is a message diagram illustrating an example message used for reporting Cross-Link Interference (CLI) using dynamic scheduling.

[0078] Figure 11 This is a message diagram illustrating an example message used for CLI reporting with semi-persistent scheduling.

[0079] Figure 12 This is a conceptual data flow diagram illustrating the data flow between different parts / components in an example BS.

[0080] Figure 13 This is a conceptual data flow diagram illustrating the data flow between different parts / components in an example UE.

[0081] Figure 14 This is a flowchart of an example method for CLI reporting for a UE.

[0082] Figure 15 This is a flowchart of an example method for configuring a victim UE to report via CLI based on the transmission of the aggressor UE.

[0083] Figure 16This is a flowchart of an example method for transmitting the Physical Uplink Shared Channel (PUSCH) from an aggressor UE. Detailed Implementation

[0084] The detailed description following, illustrated with reference to the accompanying drawings, is intended as a description of various configurations and not as representing only the configurations in which the concepts described herein can be practiced. For the purpose of providing a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid confusion with these concepts. Although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0085] Full-duplex communication allows wireless communication devices to transmit and receive simultaneously. In-band full-duplex (IBFD) refers to transmission and reception on the same time and frequency resources. Uplink (UL) and downlink (DL) can share the same IBFD time and frequency resources, which may include fully overlapping or partially overlapping resources. Subband frequency division duplex (SBFD) refers to simultaneous transmission and reception on different frequency resources. In the frequency domain, DL resources can be separate from UL resources. In the access network, base stations and / or user equipment (UEs) may be able to support IBFD or SBFD.

[0086] The presence of full-duplex devices in the access network can lead to UEs experiencing different types of interference. Inter-cell interference can include interference from other gNBs and can occur even in the absence of full-duplex devices. Channel State Information (CSI) measurements can be used to measure inter-cell interference. Inter-cell cross-link interference (CLI) can occur between UEs in adjacent cells. Intra-cell CLI can occur between UEs in the same cell. For example, uplink transmissions from an aggressor UE can interfere with the downlink reception of a victim UE. In the case of full-duplex UEs, self-interference (SI) can be considered a special case of intra-cell CLI, where the UE's transmitter acts as an aggressor UE interfering with the downlink reception of the UE's receiver.

[0087] In one aspect, this disclosure provides measurement and reporting of CLI and / or SI based on PUSCH transmissions by an aggressor UE. A PUSCH transmission may include PUSCH symbols and demodulation reference signal (DMRS) symbols. Measurement of PUSCH transmissions can provide more accurate CLI measurements than other uplink reference signals (e.g., sounding reference signals (SRS)) because CLI may be affected by power control used for PUSCH transmissions. The power of DMRS symbols can be based on PUSCH power control. However, DMRS symbols can be transmitted using known sequences that can be used for measurement. Therefore, CLI measurements based on DMRS symbols of PUSCH transmissions can provide an accurate representation of the CLI experienced due to PUSCH transmissions. In another aspect, this disclosure provides a victim UE configuration based on the PUSCH configuration of the aggressor UE, such that the victim UE is configured with Channel State Information Interference Measurement (CSI-IM) resources that match the DMRS symbols of the PUSCH transmissions. The victim UE can use the CSI-IM resources to measure CLI from PUSCH transmissions and generate CLI reports. At least in the case of CLI within a cell, the base station may be able to schedule the aggressor UE and / or victim UE to mitigate the impact of CLI.

[0088] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0089] For example, an element, any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or others.

[0090] Therefore, in one or more example embodiments, the described functionality can be implemented as hardware, software, or any combination thereof. If implemented as software, the functionality can be stored on or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium can be any available medium accessible by a computer. By way of example, and not limitation, such a computer-readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures.

[0091] Figure 1 This diagram illustrates an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes base station 102, UE 104, evolved packet core (EPC) 160, and another core network (e.g., 5G core (5GC) 190). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0092] One or more of UEs 104 (e.g., UE 104b) may include a CLI component 140 that measures CLI and / or SI based on a configuration and reports CLI / SI to base station 102. CLI component 140 may include a configuration component 142 configured to receive measurement resources, including Channel State Information Interference Measurement (CSI-IM) resources that match the Physical Uplink Shared Channel (PUSCH) symbols or Demodulation Reference Signal (DMRS) symbols of the aggressor UE (e.g., UE 104a). CLI component 140 may include a measurement component 144 configured to measure Cross-Link Interference (CLI) or Self-Interference (SI) on the CSI-IM resources. CLI component 140 may include a reporting component 146 configured to report CLI or SI to the base station. In some implementations, CLI component 140 may optionally include a DMRS component configured to map DMRS locations to CSI-IM resources. In some implementations, CLI component 140 may optionally include capability component 149, which is configured to transmit indications of one or more capabilities of UE 104 related to CLI measurement and reporting.

[0093] One or more of UEs 104 (e.g., UE 104a) may include a PUSCH component 198 that transmits PUSCH transmissions in response to Group Common Downlink Control Information (DCI) indicating CSI-IM resources for a victim UE (e.g., UE 104b). The PUSCH component 198 may receive the Group Common DCI (e.g., from a base station). The Group Common DCI may include a first portion scheduling PUSCH transmissions for an aggressor UE and a second portion comprising one or more blocks, each block indicating a CSI-IM resource set for one or more victim UEs. The PUSCH component 198 may determine a PUSCH configuration based on the Group Common DCI. The PUSCH component 198 may transmit PUSCH transmissions based on the PUSCH configuration. In some implementations, a full-duplex UE may include a CLI component 140 and a PUSCH component 198. The full-duplex UE may measure the SI of PUSCH transmissions from the configured CSI-IM resource set and report that SI to base station 102.

[0094] In one aspect, one or more of base stations 102 may include a scheduling component 120 that performs the actions of a base station as described herein (e.g., scheduling a victim UE to measure CLI and scheduling an aggressor UE to transmit PUSCH transmissions). For example, scheduling component 120 may include: a PUSCH scheduler 122 configured to transmit PUSCH transmissions including PUSCH symbols and demodulation reference signal (DMRS) symbols to the aggressor UE; scheduling component 120 may include a CSI-IM scheduler configured to transmit measurement resources to the victim UE, including Channel State Information Interference Measurement (CSI-IM) resources matching the PUSCH symbols or DMRS symbols of the PUSCH transmissions; and scheduling component 120 may include a reporting component 126 configured to receive CLI or SI measurements based on the measurement resource configuration.

[0095] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can be connected to EPC 160 interface via backhaul link 132 (e.g., S1 interface). Backhaul link 132 can be wired or wireless. Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can be connected to 5GC 190 interface via backhaul link 184. Backhaul link 184 can be wired or wireless. Among other functions, base station 102 can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, location, and warning message delivery. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC160 or 5GC 190) via backhaul link 134 (e.g., X2 interface). Backhaul link 134 can be wired or wireless.

[0096] Base station 102 can wirelessly communicate with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolution Node B (eNB) (HeNB), which can provide services to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link 112 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. Communication link 112 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. Base station 102 / UE 104 can use spectrum allocated up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier bandwidth in carrier aggregation used for transmission in each direction, with a total carrier aggregation of up to Yx MHz (x component carriers). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetrical with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), while the secondary component carrier may be referred to as the secondary cell (SCell).

[0097] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and Physical Sidelink Feedback Channel (PSFCH). D2D communication can be achieved through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0098] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0099] Cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, cell 102' can employ NR and use the same 5 GHz unlicensed spectrum as Wi-Fi AP 150. Employing NR in unlicensed spectrum can extend the coverage of the access network and / or increase its capacity.

[0100] Base station 102—whether it is a small cell 102' or a large cell (e.g., a macro base station)—may include an eNB, gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, can operate in one or more frequency bands within the electromagnetic spectrum.

[0101] Based on frequency / wavelength, the electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. In 5G NR, the two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the intermediate frequency band (IF). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "Sub-6 GHz" band. Similar naming issues sometimes arise with FR2; although it differs from the Extremely High Frequency (EHF) band (30GHz-300GHz) defined as a "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the "millimeter wave" (mmW) band in documents and articles.

[0102] In light of the foregoing, unless otherwise specifically stated, it should be understood that the terms "Sub-6 GHz," as used herein, can broadly refer to frequencies that may be less than 6 GHz, fall within FR1, or include intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that the terms "millimeter wave," as used herein, can broadly refer to frequencies that may include intermediate frequency bands, fall within FR2, or fall within the EHF band. Communication using millimeter wave radio bands suffers from extremely high path loss and short range. The millimeter wave base station 180 can utilize beamforming 182 with the UE 104 to compensate for path loss and short range.

[0103] Base station 180 can transmit beamformed signals to UE 104 in one or more transmission directions 182'. UE 104 can receive beamformed signals from base station 180 in one or more reception directions 182'. UE 104 can also transmit beamformed signals to base station 180 in one or more transmission directions. Base station 180 can receive beamformed signals from UE 104 in one or more reception directions. Base station 180 / UE 104 can perform beamtraining to determine the optimal reception and transmission directions for each base station 180 / UE 104. The transmission and reception directions of base station 180 can be the same or different. The transmission and reception directions for UE 104 can be the same or different.

[0104] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166 connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0105] 5GC 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. Typically, AMF 192 provides QoS streaming and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services.

[0106] A base station may also be referred to as a gNB, Node B, Evolved Node B (eNB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transceiver Point (TRP), or some other suitable terminology. Base station 102 provides UE 104 with access to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some of UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or some other suitable term.

[0107] Figures 2A to 2D This is a resource diagram showing example frame structures and channels that can be used for uplink, downlink, and sidelink transmissions to UE 104, including CLI component 140. Figure 2A Figure 200 shows an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be FDD, where, for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either DL or UL; or it can be TDD, where, for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both DL and UL. Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and X is flexibly used between DL / UL, and subframe 3 is configured with slot format 34 (primarily UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and UL respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format via the received Slot Format Indicator (SFI) (dynamically via DL Control Information (DCI) or semi-statically / statically via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0108] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may contain 7, 4, or 2 symbols. Depending on the time slot configuration, each time slot may contain 7 or 14 symbols. For time slot configuration 0, each time slot may contain 14 symbols, while for time slot configuration 1, each time slot may contain 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) OFDM (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high throughput) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained cases; limited to a single stream). The number of time slots within a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols / slots and 2... μ Each time slot / subframe. Subcarrier spacing and symbol length / duration are functions of a parameter set. Subcarrier spacing can be equal to 2.μ *15kHz, where μ is the parameter set from 0 to 5. Therefore, parameter set μ = 0 has a subcarrier spacing of 15kHz, while parameter set μ = 5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A to 2D Examples are provided for slot configuration 0 with 14 symbols per slot and parameter set μ=0 with 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is approximately 66.7 μs.

[0109] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) that extends 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0110] As in Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulated RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration). x (Where 100x is the port number, but other DM-RS configurations are also possible) and Channel State Information Reference Signal (CSI-RS). RS can also include Beam Measurement RS (BRS), Beam Refinement RS (BRRS), and Phase Tracking RS (PT-RS).

[0111] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising four consecutive REs in an OFDM symbol. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. UE 104 uses the PSS to determine subframe / symbol timing and the Physical Layer Identifier. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The UE uses the SSS to determine the Physical Layer Cell Identifier Group Number and the radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH) carrying the Primary Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the number of Restricted Frames (RBs) and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Blocks (SIBs)) that are not transmitted through the PBCH, and paging messages.

[0112] like Figure 2C As shown, some REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are also possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or second symbols preceding the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. Although not shown, the UE can transmit a Sounding Reference Signal (SRS). The base station can use the SRS for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0113] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and can additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0114] Figure 3This is a block diagram of base station 310 communicating with UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, while Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0115] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be segmented into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying the time-domain OFDM symbol stream. The OFDM streams are spatially precoded to produce multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0116] At UE 350, each receiver 354RX receives signals through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on this information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on channel estimates calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 2 and layer 3 functions.

[0117] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the EPC 160 or 5GC 190. The controller / processor 359 is also responsible for error detection to support HARQ operation using ACK and / or NACK protocols.

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

[0119] The TX processor 368 can use the channel estimate derived from the reference signal or feedback transmitted from the base station 310 by the channel estimator 358 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0120] At base station 310, UL transmission is processed in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals through its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides this information to the RX processor 370.

[0121] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection to support HARQ operation using ACK and / or NACK protocols.

[0122] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform operations related to... Figure 1 Aspects related to CLI component 140 and / or PUSCH component 198.

[0123] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform operations related to... Figure 1 The aspects related to the scheduling component 120.

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

[0125] Figure 4AA first example of full-duplex communication 400 is shown, wherein a first base station 402a communicates in full-duplex with a first UE 404a and a second UE 406a. The first base station 402a is a full-duplex base station, while the first UE 404a and the second UE 406a can be configured as half-duplex or full-duplex UEs. The second UE 406a can transmit a first uplink signal to the first base station 402a and other base stations (such as a second base station 408a near the second UE 406a). The first base station 402a transmits downlink signals to the first UE 404a while simultaneously receiving uplink signals from the second UE 406a. Base station 402a may experience self-interference at the receiving antenna that is receiving uplink signals from UE 406a, which is receiving some of the downlink signals being transmitted to UE 404a. Base station 402a may experience additional interference due to signals from the second base station 408a. Interference may also occur at the first UE 404a based on the following signals: the signals originating from the second base station 408a and the uplink signals from the second UE 406a.

[0126] Figure 4B A second example of full-duplex communication 410 is shown, wherein a first base station 402b communicates with a first UE 404b in full-duplex mode. In this example, the first base station 402b is a full-duplex base station, and the first UE 404b is a full-duplex UE. The first base station 402b and UE 404b can simultaneously receive and transmit communications that overlap temporally in the same frequency band. The base station and the UE may each experience self-interference, where transmitted signals from the devices are leaked to receivers at the same devices. The first UE 404b may experience additional interference based on one or more signals transmitted from a second UE 406b and / or a second base station 408b near the first UE 404b.

[0127] Figure 4C A third example of full-duplex communication 420 is shown, wherein a first UE 404c is a full-duplex UE communicating with a first base station 402c and a second base station 408c. The first base station 402c and the second base station 408c can be used as multiple transmit and receive points (multi-TRPs) for UL and DL communication with UE 404c. The second base station 408c can communicate with a second UE 406c. Figure 4CIn this configuration, the first UE 404c can simultaneously transmit uplink signals to the first base station 402c and receive downlink signals from the second base station 408c. Due to the simultaneous communication of the first and second signals, the first UE 404c may experience self-interference; for example, the uplink signal may leak to the UE's receiver (e.g., be received by the UE's receiver). The first UE 404c may also experience additional interference from the second UE 406c.

[0128] Figures 5A to 5B The first example 500 and the second example 510 of in-band full-duplex (IBFD) resources are shown. Figure 5C Example 520 of subband full-duplex resources is shown. In IBDF, signals can be transmitted and received on overlapping times and overlapping frequencies. As shown in the first example 500, the time and frequency allocation of UL resource 502 can completely overlap with the time and frequency allocation of DL resource 504. In the second example 510, the time and frequency allocation of UL resource 512 can partially overlap with the time and frequency allocation of DL resource 514.

[0129] IBFD is the opposite of Subband FD (SBFD). In Subband FD, uplink and downlink resources can overlap in time using different frequencies, such as... Figure 5C As shown. Figure 5C As shown, UL resource 522 is separated from DL resource 524 by guard band 526. The guard band can be a frequency resource or a gap between UL resource 522 and DL resource 524. Separating UL and DL frequency resources using a guard band can help reduce self-interference. UL and DL resources adjacent to each other correspond to a guard band width of 0. Since, for example, output signals from the UE transmitter may extend beyond the UL resource, the guard band can reduce interference experienced by the UE. Subband FD can also be referred to as "flexible duplex".

[0130] Figure 6 An example set of time and frequency resources 600, including both half-duplex and full-duplex time periods, is shown. For example, time period 620 includes half-duplex resources for downlink data. Time period 620 includes sub-band full-duplex resources for uplink transmission (e.g., PUSCH) and downlink reception (e.g., downlink data). Time period 640 includes half-duplex resources for uplink data.

[0131] When a time slot has frequency bands used for both uplink and downlink transmissions, the time slot format can be called a "D+U" time slot. Downlink and uplink transmissions can occur in overlapping frequency resources, such as... Figure 5A and 5BAs shown (e.g., in-band full-duplex resources), or it can occur in adjacent or slightly separated frequency resources, such as Figure 5C As shown (e.g., sub-band full-duplex resources). In a specific D+U symbol, a half-duplex device can transmit in the uplink band or receive in the downlink band. In a specific D+U symbol, for example, in the same symbol or the same time slot, a full-duplex device can transmit in the uplink band and receive in the downlink band. D+U time slots can include downlink-only symbols, uplink-only symbols, and full-duplex symbols. For example, in Figure 6 In this context, time period 620 may extend one or more symbols (e.g., downlink symbols only), time period 640 may extend one or more symbols (e.g., uplink symbols only), and time period 630 may extend one or more symbols (e.g., full-duplex symbols or D+U symbols).

[0132] Figure 7A An example communication system 700 with a full-duplex base station 702 is shown, which includes intra-cell cross-link interference (CLI) caused by UE 706 to UE 704 located within the same cell coverage 710, and inter-cell interference from base station 708 outside the cell coverage 710. Figure 7B An example communication system 750 is illustrated, showing inter-cell cross-link interference from UE 716 that interferes with the downlink reception of UE 714. UE 714 is in cell coverage 720 of base station 712, and UE 716 is in cell coverage 722 of base station 718. Although not shown, a full-duplex UE may cause self-interference in its own downlink reception.

[0133] In Subband Full-Duplex (SBFD), a base station can configure downlink transmission to a UE in frequency domain resources adjacent to those used for uplink transmission to another UE. For example, in Figure 7A In this context, frequency resources used for downlink transmission to UE 704 can be adjacent to frequency resources used for uplink transmission from UE 706.

[0134] Base stations can use CLI / SI measurements to make scheduling decisions for future time slots. Typically, SRS power control and Tx power differ from PUSCH. CLI / SI based on SRS measurements may not accurately represent CLI / SI from PUSCH. For example, PUSCH transmission power can be represented by the following expression.

[0135]

[0136] For comparison, SRS power can be expressed by the following expression.

[0137]

[0138] If srs-PowerControlAdjustmentStates indicates the same power state for both SRS and PUSCH, then the SRS power control adjustment h(.) = f(.), but they can also be different. Additionally, the offset Δ TF,b,f,c (i) It may only apply to PUSCH. Therefore, the power of PUSCH and SRS may differ, resulting in a CLI measurement based on SRS that differs from the CLI caused by PUSCH. Therefore, in one aspect, this disclosure provides CLI and SI measurements based on PUSCH transmissions that may include DMRS symbols and PUSCH symbols.

[0139] Figure 8 This is a diagram illustrating example resource 800 for a first UE (UE1) and a second UE (UE2). The first UE can transmit PUSCH transmissions on UL subband 820 and can be considered the aggressor UE. The second UE (UE2) can receive downlink transmissions (such as PDSCH) on DL BWP 810, which may include one or more DL subbands 812, 814. The second UE can be considered the victim UE.

[0140] On one hand, the base station can configure CSI-IM resources for the victim UE on the same symbols where the PUSCH is configured for the aggressor UE. The victim UE's CSI-IM resources can be configured to match the aggressor UE's PUSCH DMRS mode. For example, a first UE can be configured with a DMRS mode that includes DMRS on symbols 830 and 832 within the UL subband 820. A second UE can be configured with CSI-IM resources 840 and 842 corresponding to symbols 830 and 832. Therefore, the second UE can measure CLI based on the DMRS transmitted by the first UE. In some implementations, a single full-duplex UE can be configured with both a PUSCH DMRS mode and CSI-IM resources for performing SI measurements.

[0141] The configuration of PUSCH DMRS mode and CSI-IM resources can depend on the type of scheduling. For dynamically licensed ULs, assuming flexible PUSCH allocation, the base station can configure non-periodic CSI-IM and non-periodic CLI reporting for the victim UE. For configuration-licensed ULs, the base station can configure semi-persistent or periodic CSI-IM resources for the victim UE to match the periodic transmissions of the aggressor UE.

[0142] A victim UE can be configured with multiple CSI-IM resources to match PUSCHDMRS symbols from one or more aggressors. When a UE is configured with multiple CSI-IM resources for CLI / SI, there may be multiple options for reporting CLI / SI. In the first option, the victim UE can report the CLI / SI value for each DMRS symbol. This first option can provide all available information but may consume uplink bandwidth for reporting. In the second option, the victim UE can report the average CLI / SI value across the configured DMRS symbols. Compared to the first option, this option can provide sufficient information for scheduling while reducing the size of the CLI / SI report.

[0143] On one hand, PUSCH Energy Per Resource Element (EPRE) and DMRS EPRE can be different. DMRS-based interference measurements can be adjusted to account for the difference between PUSCH EPRE and DMRS EPRE. When a base station configures a victim UE to measure CLI based on the perpetrator UE's PUSCH DMRS, the base station can inform the victim UE of the ratio between PUSCH EPRE and DMRS EPRE. For example, the base station can indicate in the CLI reporting configuration that scaling is required to account for PUSCH EPRE and DMRS EPRE. As another example, if the victim UE is configured to measure the average CLI on CSI-IM resources corresponding to DMRS symbols from multiple perpetrators, the CLI reporting configuration can include a list of scaling values, each corresponding to a CSI-IM resource in the resource set. That is, the victim UE can apply different scaling values ​​to each CSI-IM resource to account for different ratios of PUSCH EPRE to DMRS EPRE for different perpetrator UEs. The following table can be used to adjust the CLI / SI measurement of EPRE.

[0144] Table 6.2.2-1: Ratio of PUSCH EPRE to DM-RS EPRE

[0145] Number of DM-RS CDM groups without data DM-RS Configuration Type 1 DM-RS Configuration Type 2 1 0dB 0dB 2 -3dB -3dB 3 - -4.77dB

[0146] For dynamic, license-based UL scheduling, PUSCH frequency allocation can change over time slots. In one aspect, the base station can configure the victim UE to measure CLI based on the PUSCH bandwidth. For example, the base station can configure aperiodic CSI-IM resources for the victim UE to match the PUSCH bandwidth. As another example, the base station can configure aperiodic CLI reporting for the victim UE, where the victim UE measures the subband CLI corresponding to the perpetrator UE's PUSCH frequency allocation. As yet another example, the base station can configure periodic or semi-persistent CSI-IM resources, where the frequency allocation of the CSI-IM resources changes over time slots. For example, the base station can transmit an RRC configuration for CSI-IM resources that includes a frequency domain allocation sequence. The victim UE can cycle through the frequency domain allocation sequence for each time slot. As another example of changing CSI-IM resources, the frequency domain allocation of CSI-IM resources can follow a deterministic finite state machine. The base station can transmit an RRC configuration that includes the parameters of the finite state machine. For example, the victim UE can measure wideband CSI in a first state and narrowband CSI in a second state. The UE can change the state based on whether the measured CSI meets a threshold. As another example of altering CSI-IM resources, the frequency domain allocation of CSI-IM resources can follow predefined rules based on the time slot format. For instance, each time slot format can be associated with a mapping from time slot number to frequency domain resources.

[0147] On one hand, CLI measurements based on PUSCH transmissions can involve scheduling both the aggressor UE and the victim UE. In some implementations, the base station can send a public message that triggers a PUSCH transmission from the aggressor UE and triggers CLI measurements and reports from one or more victim UEs via a DCI. Figure 9 An example group common DCI 900 is shown. The group common DCI 900 may include a first portion 910 that schedules PUSCH transmissions and a second portion 920 that includes one or more blocks 922 (e.g., blocks 922a, 922b, ..., 922n). The first portion 910 may include uplink permission fields, such as DCI format 0_1. The first portion 910 may include all fields or a subset thereof. The second portion 920 may use blocks 922 to explicitly indicate the CSI-IM resources for each UE. Each block 922 may indicate a set of CSI-IM resources. Each victim UE may be configured with an index 924 corresponding to one of the one or more blocks. Each victim UE may generate a CLI report based on the set of CSI-IM resources in the block 922 corresponding to the respective victim UE's index 924. For example, a victim UE may be configured with an index 924 pointing to block 922a. Block 922a may indicate the set of CSI-IM resources used by the victim UE to measure CLI.

[0148] In some implementations, the group common DCI 900 may implicitly indicate CSI-IM resources. That is, the group common DCI 900 may not include the second part 920. The first part 910 may still include all fields of DCI format 0_1 ​​or a subset thereof for configuring PUSCH transmissions for the aggressor UE. The victim UE may use pre-configured rules and / or PUSCH RRC configuration to determine the DMRS location of the PUSCH transmission from the aggressor UE. For example, the victim UE may determine the mapping between DMRS and CSI-IM resources based on CSI-IM resources in an RRC configuration dedicated to CLI measurements. The base station may configure CSI-IM resources for the victim UE on different symbols covering different DMRS locations. If more than one CSI-IM resource is configured on the same symbol, the victim UE may select measurement resources based on pre-configured rules. For example, the UE may use frequency domain resources corresponding to previous transmissions. As another example, the victim UE can determine the mapping between DMRS and CSI-IM resources based on the CSI-IM resources configured in the RRC and the pre-configured mapping between the CSI-IM resource index and the DMRS time and frequency location.

[0149] Figure 10 This is a message diagram 1000 illustrating an example message for CLI reporting using dynamic scheduling. Base station 102 can be a serving base station for both aggressor UE 104a and victim UE 104b. Both aggressor UE 104a and victim UE 104b can transmit UE capabilities 1010, 1012, indicating the corresponding capabilities of UE 104a regarding CLI reporting. Base station 102 can configure aggressor UE 104a via RRC signaling 1020. For example, RRC signaling 1020 can instruct a PUSCH configuration indicating DMRS mode. Base station 102 can configure victim UE 104b via RRC signaling 1022. For example, RRC signaling 1022 can instruct one or more CSI-IM resource sets and indices 924. Base station 102 can transmit a group common DCI 900 to both aggressor UE 104a and victim UE 104b. Group common DCI 900 can instruct the aggressor UE 104a to use PUSCH resources. Group common DCI 900 can instruct the victim UE 104b to use CSI-IM resources. The aggressor UE 104a can transmit PUSCH 1040 based on Group common DCI 900. The victim UE 104b can receive PUSCH 1040 as interference 1042. The victim UE 104b can measure the interference 1042 from PUSCH 1040 on the CSI-IM resources. The victim UE 104b can generate a CLI report 1050 based on this measurement.

[0150] Figure 11 This is a message diagram 1100 illustrating an example message for CLI reporting using semi-persistent scheduling. Base station 102 can be a serving base station for both aggressor UE 104a and victim UE 104b. Both aggressor UE 104a and victim UE 104b can transmit UE capabilities 1010, 1012, which indicate the corresponding capabilities of UE 104 regarding CLI reporting.

[0151] On one hand, Group Common DCI 900 can be used to activate Configuration Grant (CG) 1120 in UL and Semi-Persistent Scheduling (SPS) 1122 in DL. Typically, in SPS, PDSCH transmissions are scheduled by RRC messages. SPS uses DCI for activation. Similarly, for CG, the base station uses RRC messages to schedule uplink transmissions. There are two types of UL CGs: Type 1 provides semi-static scheduling without DCI triggers, while Type 2 provides semi-static scheduling with DCI triggers. To characterize the CLI of CG UL transmissions from the aggressor UE to the victim UE's DL transmissions, the base station can pair UL CGs from one or more aggressor UEs with SPS scheduling for the victim. In an implementation, the base station can group the victim and aggressor UEs based on whether the scheduled UL CGs and DL SPSs overlap in the time domain. The base station can send Group Common DCI 900 to activate both CG UL (Type-2) transmissions from one or more aggressor UEs and SPS DL scheduling for one or more victim UEs. In another implementation, the base station can configure a semi-persistent CSI-IM resource 1124 for the victim UE to measure CLI from the aggressor UE. The periodicity and offset of the SP CSI-IM resource 1124 can be selected to match CG UL transmissions from the aggressor UE. The SP CSI-IM resource 1124 can be activated via MAC-CE 1126. In some implementations, a group common DCI 900 can trigger the semi-persistent CSI-IM resource 1124 and semi-persistent CLI reporting. The group common DCI 900 may include a second portion 920 having multiple blocks 922. Each victim UE can be configured with an index 924 pointing to one of the blocks 922. Each block 922 may include a CLI request field indicating which set of CSI-IM resources should be used for CLI measurement.

[0152] On one hand, the victim UE can use different Quasi-Cooperative Location (QCL) spatial relationship parameters (this can be referred to as QCL Type D) to measure CLI. The base station can configure semi-persistent CSI-IM resources for the victim UE to measure CLI. The base station can define Transmission Configuration Indicator (TCI) states for CSI-IM that indicate the QCL spatial relationship parameters. In some implementations, the base station can define a list of TCI states for a set of CSI-IM resources. Each TCI state in the list can correspond to one CSI-IM resource in the set. The same TCI state can be used in all measurement instances for the semi-persistent CSI-IM resource set. In some implementations, the base station can define a list of TCI states for a set of CSI-IM resources. All resources in the set can use one of the TCI states. The victim UE can cycle through the list of TCI states in measurement instances. For example, the victim UE can use a first TCI state for a first measurement instance, a second TCI state for a second measurement instance, and so on. Therefore, the victim UE can provide information about the spatial relationship between the victim UE and the aggressor UE. For example, the base station can select the TCI state that experiences the least amount of downlink transmission in CLI. In some implementations, the base station can define a sequence of TCI state lists for a set of CSI-IM resources. The victim UE can cycle through the sequence of TCI state lists for multiple measurement instances of the semi-persistent CSI-IM resources. The victim UE can use one of the TCI state lists for each instance of the semi-persistent CSI-IM resources.

[0153] In some implementations, the base station can configure semi-persistent CLI reports based on semi-persistent CSI-IM resources for the victim UE. If the measured CLI is less than a threshold, the UE can discard the semi-persistent CLI report. In some implementations, when the victim UE measures CLIs for different QCL spatial relationship parameters, the victim UE can average the CLI values ​​for the same QCL spatial relationship parameter. In each report, the victim UE can report all pairs (CLI value, QCL-D), or the victim UE can report one pair in each report and cycle through different pairs across multiple reports. In some implementations, the victim UE can average the CLI values ​​for all QCL spatial relationship parameters and report a single CLI value to the base station.

[0154] In some implementations, a group common DCI can be used to activate DL SPS. As discussed above, for UL CG type-1, the base station does not send a DCI to activate UL transmissions. For example, based on the transmission buffer of the aggressor UE, the aggressor UE may or may not transmit PUSCH transmissions. The base station can send a group common DCI 900 to activate SPS scheduling for one or more victim UEs. The base station can configure a semi-persistent CSI-IM resource for the victim UE to measure the CSI of CG UL from the aggressor UE. The periodicity and offset of the semi-persistent CSI-IM resource can be selected to match ULCG transmissions from one or more aggressor UEs. In some implementations, the base station can filter CLI reports based on the presence of a PUSCH transmission from one of the aggressor UEs at the configured measurement time. In some implementations, each victim UE can discard the configured CLI report if the measured CLI value is less than a threshold (which may indicate that the aggressor UE is not transmitting PUSCH transmissions using UL CG). Therefore, CLI measurements can accurately indicate interference caused by actual PUSCH transmissions.

[0155] Figure 12 This is a conceptual data flow diagram 1200 illustrating the data flow between different components / assemblies in an example base station 1202, which may be an example of a base station 102 including a scheduling component 120. The scheduling component 120 may include a PUSCH scheduler 122, a CSI-IM scheduler 124, and a reporting component 126. In some embodiments, the scheduling component 120 may optionally include a capability receiver 1210 for receiving indications of UE capabilities 1010, 1012. In some embodiments, the scheduling component 120 may optionally include a decoder for decoding received PUSCH. The scheduling component 120 may also include a receiver component 1250 and a transmitter component 1252. The receiver component 1250 may include, for example, an RF receiver for receiving signals described herein. The transmitter component 1252 may include, for example, an RF transmitter for transmitting signals described herein. In some implementations, the receiver assembly 1250 and the transmitter assembly 1252 may coexist in the transceiver.

[0156] Receiver component 1250 can receive uplink signals from multiple UEs 104. For example, receiver component 1250 can receive PUSCH from the aggressor UE 104a and CLI reports from the victim UE 104b. Receiver component 1250 can receive UE capabilities 1010 and 1012 from any UE. Receiver component 1250 can provide CLI reports to reporting component 126. Receiver component 1250 can provide UE capabilities to capability receiver 1210. Receiver component 1250 can provide PUSCH to decoder 1220.

[0157] Capability receiver 1210 can receive one or more indications of UE capabilities 1010, 1012. Capability receiver 1210 can determine whether a UE is a victim UE or an aggressor UE based on the received capabilities. In some implementations, a UE can be either a victim UE or an aggressor UE. The role of a particular UE can vary based on scheduling within a specific time slot. Additionally, for a full-duplex UE, when scheduled to transmit and receive in the same time slot, the UE can be considered both an aggressor UE and a victim UE. Capability receiver 1210 can provide the aggressor UE's capabilities to PUSCH scheduler 122. Capability receiver 1210 can provide the victim UE's capabilities to CSI-IM scheduler 124.

[0158] Decoder 1220 can receive PUSCH from the aggressor UE via receiver component 1250. Decoder 1220 can attempt to decode the received PUSCH based on the PUSCH configuration. Decoder 1220 can determine the decoding status (ACK or NACK) of the PUSCH based on whether the decoding was successful. Decoder 1220 can provide the decoding status to PUSCH scheduler 122 to indicate whether the PUSCH should be retransmitted.

[0159] PUSCH scheduler 122 can receive the UE capabilities of the aggressor UE from capability receiver 1210. PUSCH scheduler 122 can receive power control information from reporting component 126. PUSCH scheduler 122 can receive ACK / NACK for PUSCH from decoder 1220. PUSCH scheduler 122 can also receive other information for scheduling, such as channel estimation, scheduling requests, or buffer status reports. PUSCH scheduler 122 can determine the PUSCH configuration for the aggressor UE based on available information. For example, given constraints imposed by power control information and channel conditions, PUSCH scheduler 122 can determine the amount of resources available for transmitting data. PUSCH scheduler 122 can schedule the aggressor UE to transmit one or more PUSCH transmissions. For example, PUSCH scheduler 122 can transmit an RRC message to the aggressor UE via transmitter component 1252. In some embodiments, depending on the UE capabilities, PUSCH scheduler 122 can transmit a group common DCI 900, where the first portion 910 can indicate PUSCH parameters.

[0160] CSI-IM scheduler 124 may receive UE capabilities of one or more victim UEs from capability receiver 1210. CSI-IM scheduler 124 may receive indications of PUSCH scheduling from PUSCH scheduler 122. CSI-IM scheduler 124 may configure one or more victim UEs to measure CLI based on scheduled PUSCH transmissions. Specifically, CSI-IM scheduler 124 may transmit a victim UE RRC configuration indicating one or more CSI-IM resource sets corresponding to the DMRS symbols of the PUSCH transmission. The victim UE RRC configuration may also indicate a CLI reporting configuration. In some implementations, CSI-IM scheduler 124 may transmit a group common DCI 900 or second part 920 to indicate a specific CSI-IM resource set for PUSCH transmissions.

[0161] Reporting component 126 can receive CLI reports from one or more victim UEs 104. Reporting component 126 can determine the impact of cross-link interference on the victim UEs. In some implementations, reporting component 126 can adjust scheduling based on CLI reports. For example, reporting component 126 can provide power control information for PUSCH transmissions, which can limit the CLI experienced by the victim UE.

[0162] Figure 13 This is a conceptual data flow diagram 1300 illustrating the data flow between different parts / components in example UE 1304, which may be an example of UE 104 (e.g., victim UE 104b) and includes CLI component 140.

[0163] Such as about Figure 1 The CLI component 140 discussed may include a configuration component 142, a measurement component 144, and a reporting component 146. In some embodiments, the CLI component 140 may include a DMRS component 148. In some embodiments, the CLI component 140 may include a capability component 149. The CLI component 140 may also include a receiver component 1370 and a transmitter component 1372. The receiver component 1370 may include, for example, a radio frequency (RF) receiver for receiving the signals described herein. The transmitter component 1372 may include, for example, an RF transmitter for transmitting the signals described herein. In some embodiments, the receiver component 1370 and the transmitter component 1372 may coexist in a transceiver.

[0164] Receiver component 1370 can receive downlink signals, such as RRC signaling 1022 or group common DCI 900. Receiver component 1370 can receive crosslink interference, such as interference 1042 from PUSCH 1040. Receiver component 1370 can provide RRC signaling 1022 and group common DCI 900 to configuration component 142. Receiver component 1370 can provide crosslink interference to measurement component 144.

[0165] Configuration component 142 can receive RRC signaling 1020 from receiver component 1370. Configuration component 142 can extract RRC configuration parameters from RRC signaling 1020, for example, by decoding the RRC signaling. For example, configuration component 142 can extract the slot format, one or more CSI-IM configurations (such as FD allocation sequences or finite state machine parameters), group common DCI index 924, and / or one or more SPS configurations. Configuration component 142 can receive group common DCI 900 from receiver component 1370. For dynamic scheduling, configuration component 142 can determine the CSI-IM resource set based on block 922 corresponding to index 924 or implicitly based on first portion 910. For SPS scheduling, configuration component 142 can determine the active SPS configuration and / or semi-persistent CSI-IM resources based on group common DCI 900. In either case, configuration component 142 can determine the CSI-IM resources to be measured. Configuration component 142 can provide the CSI-IM resources to measurement component 144. In some implementations, the RRC configuration and / or group common DCI 900 may not explicitly indicate CSI-IM resources. Instead, the RRC configuration and / or group common DCI 900 may indicate the PUSCH configuration of one or more aggressor UEs 104a (e.g., first part 910). In these implementations, configuration component 142 may provide the PUSCH configuration to DMRS component 148. Configuration component 142 may also determine CLI reporting configuration. CLI reporting configuration may include CLI values ​​for transmitting CLI reports and the quantity and type of uplink resources. Configuration component 142 may provide the CLI reporting configuration to reporting component 146.

[0166] DMRS component 148 can receive PUSCH configuration from configuration component 142. DMRS component 148 can determine CSI-IM resources based on the PUSCH configuration. For example, DMRS component 148 can determine the DMRS location indicated in the PUSCH configuration, or determine the DMRS location based on pre-configured rules (e.g., according to slot format). DMRS component 148 can be configured with sets of CSI-IM resources on different symbols covering different DMRS locations. DMRS component 148 can select CSI-IM resources configured to cover the DMRS locations of PUSCH 1040. If more than one CSI-IM resource is configured on the same symbol, DMRS component 148 can select the CSI-IM resource based on pre-configured rules. Alternatively, DMRS component 148 can be configured with a mapping between CSI-IM resource indices and the time and frequency locations of DMRS. DMRS component 148 can provide the selected CSI-IM resource to measurement component 144.

[0167] Measurement component 144 can receive CSI-IM resources from configuration component 142 and / or DMRS component 148. Measurement component 144 can perform measurements on the CSI-IM resources. Base station 102 can avoid transmitting on CSI-IM resources, therefore any signal received on CSI-IM resources can be considered cross-link interference. In one aspect, measurement component 144 can measure Received Signal Strength Indicator (RSSI) to capture the amount of cross-link interference. In some embodiments, measurement component 144 can measure Reference Signal Received Power (RSRP). In some embodiments, measurement component 144 can adjust the measured CLI value based on the ratio of PUSCH EPRE to DMRS EPRE.

[0168] Reporting component 146 can transmit CLI reports based on reporting configuration and measurements. For example, reporting component 146 can determine multiple CLI values ​​to be reported. If instructed by the reporting configuration, reporting component 146 can average the measured values. Reporting component 146 can determine the uplink resources used for CLI reporting based on the reporting configuration. Reporting component 146 can transmit CLI reports via transmitter component 1372.

[0169] As described herein, capability component 149 may transmit indications of one or more capabilities of UE 1304 related to CLI reporting. For example, capability component 149 may transmit an RRC message indicating whether UE 1304 is capable of performing any of the actions described herein. Example capabilities that may be reported include: CLI or SI measurements in CSI-IM resources; common DCIs for PUSCH configuration; common DCIs for triggering CLI measurements and reporting; explicit or implicit indications of CSI-IM resources in common DCIs; common DCIs for triggering configuration permission in the uplink; common DCIs for triggering SPS in the downlink; common DCIs for triggering semi-persistent CSI-IM resources; common DCIs for triggering semi-persistent CLI reporting; QCLs for CLI measurements; or different QCLs for the timing of semi-persistent CSI-IM measurements.

[0170] Figure 14 This is a flowchart of an example method 1400 for a victim UE to report a CLI. Method 1400 can be performed by a UE (such as UE 104, which may include memory 360, and may be the entire UE 104 or components of UE 104, such as CLI component 140, TX processor 368, RX processor 356, or controller / processor 359). Method 1400 can be performed by CLI component 140 communicating with scheduling component 120 of base station 102. Optional blocks are shown in dashed lines.

[0171] In block 1410, method 1400 may optionally include an indication of transmitting one or more capabilities of the UE. In some implementations, for example, UE 104, TX processor 368, or controller / processor 359 may execute CLI component 140 or capability component 149 to transmit an indication of one or more capabilities of the UE. Example capabilities may include whether the victim UE supports one or more of the following: CLI or SI measurements in CSI-IM resources; a common DCI for PUSCH configuration; a common DCI for triggering CLI measurements and reporting; an explicit or implicit indication of CSI-IM resources in a common DCI; a common DCI for triggering configuration permission in the uplink; a common DCI for triggering SPS in the downlink; a common DCI for triggering semi-persistent CSI-IM resources; a common DCI for triggering semi-persistent CLI reporting; a QCL for CLI measurements; or a different QCL for the timing of semi-persistent CSI-IM measurements. Therefore, the UE 104, TX processor 368, or controller / processor 359 executing CLI component 140 or capability component 149 can provide components for transmitting instructions of one or more capabilities of the UE.

[0172] In block 1420, method 1400 may include receiving configuration of measurement resources from a base station, the measurement resources including channel CSI-IM resources matching the PUSCH symbols or DMRS symbols of the aggressor UE. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may execute CLI component 140 or configuration component 142 to receive configuration of measurement resources from base station 102, the measurement resources including channel CSI-IM resources matching the PUSCH symbols or DMRS symbols of the aggressor UE.

[0173] In some implementations, within sub-block 1422, block 1420 may optionally include an indication of the PUSCH bandwidth for receiving dynamically scheduled PUSCH transmissions for the aggressor UE. The configuration of measurement resources may include aperiodic CSI-IM resources matched to the PUSCH bandwidth. The configuration of CLI reports may indicate aperiodic CLI reports for sub-band CLIs corresponding to the frequency domain allocation of the PUSCH transmissions.

[0174] In some implementations, within sub-block 1424, block 1420 may optionally include a receive group common DCI 900 that dynamically schedules PUSCH transmissions for the aggressor UE. The group common DCI 900 may include a first portion 910 scheduling PUSCH transmissions and a second portion 920 including one or more blocks 922, each indicating a CSI-IM resource set. The victim UE may be configured with an index corresponding to one of the one or more blocks. Therefore, the second portion 920 of the group common DCI 900 may explicitly indicate a CSI-IM resource set. In some implementations, the group common DCI 900 may not include the second portion 920, and method 1400 may include optional blocks 1430 and 1440 to determine CSI-IM resources.

[0175] In some implementations, within sub-block 1426, block 1420 may optionally include receiving one or more SPS configurations for CSI-IM resources, each SPS configuration corresponding to a corresponding configuration permission for a PUSCH transmission for the aggressor UE. For example, one or more SPS configurations may be received as an RRC message indicating SPS scheduling for a PDSCH transmission for the victim UE. Within sub-block 1428, block 1420 may optionally include receiving a group common DCI for one of the active SPS configurations and its corresponding configuration permission.

[0176] In some implementations, the configuration for receiving measurement resources in block 1420 may include a configuration for receiving semi-persistent CSI-IM resources. The periodicity and offset of the semi-persistent CSI-IM resources may be matched to the configuration permissions of the aggressor UE. The semi-persistent CSI-IM resources may be activated by MAC-CE. Alternatively, the semi-persistent CSI-IM resources may be activated by a public DCI 900 comprising one or more blocks 922. In this case, each block 922 may indicate the set of CSI-IM resources to be activated. The victim UE may be configured with an index corresponding to one of the one or more blocks. The block may include a CLI request field indicating which set of CSI-IM resources to activate. Thus, the victim UE may determine the set of CSI-IM resources to activate based on the group public DCI 900. The CLI report configuration may correspond to the activated set of CSI-IM resources. In some implementations, the public DCI may also activate an SPS configuration for SPS scheduling for PDSCH.

[0177] In view of the foregoing, the UE 104, RX processor 356, or controller / processor 359 executing CLI component 140 or configuration component 142 may provide components for configuring measurement resources to receive measurement resources from the base station, the measurement resources including channel CSI-IM resources that match the PUSCH symbol or DMRS symbol of the aggressor UE.

[0178] In block 1430, method 1400 may optionally include determining one or more DMRS locations within a resource for a PUSCH transmission for the aggressor UE based on the victim UE's PUSCH RRC configuration. Block 1430 may respond to receiving a group common DCI 900 including the first portion 910. For example, in some embodiments, UE 104, TX processor 368, or controller / processor 359 may execute CLI component 140 or DMRS component 148 to determine one or more DMRS locations within a resource for a PUSCH transmission for the aggressor UE based on the victim UE's PUSCH RRC configuration. For example, the victim UE and the aggressor UE may share a PUSCH RRC configuration. Thus, the victim UE can determine the temporal location of DMRS symbols within a PUSCH transmission. Therefore, UE 104, TX processor 368, or controller / processor 359 executing CLI component 140 or DMRS component 148 may provide components for determining one or more DMRS locations within a resource for a PUSCH transmission for the aggressor UE based on the victim UE's PUSCH RRC configuration.

[0179] In block 1440, method 1400 may optionally include determining a mapping between one or more DMRS locations and CSI-IM resources. In some implementations, for example, UE 104, TX processor 368, or controller / processor 359 may execute CLI component 140 or DMRS component 148 to determine a mapping between one or more DMRS locations and CSI-IM resources. For example, a victim UE may be configured with sets of CSI-IM resources on different symbols covering different DMRS locations. Determining the mapping may include selecting sets of CSI-IM resources covering one or more DMRS locations. As another example, a victim UE may be configured with a mapping between sets of CSI-IM resources and DMRS locations. Therefore, UE 104, TX processor 368, or controller / processor 359 executing CLI component 140 or DMRS component 148 may provide components for determining a mapping between one or more DMRS locations and CSI-IM resources.

[0180] In block 1450, method 1400 may include measuring CLI or SI on CSI-IM resources. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may execute CLI component 140 or measurement component 144 to measure CLI or SI on CSI-IM resources. In some implementations, the configuration of the measurement resources includes a ratio of EPRE of the PUSCH symbol to EPRE of the DMRS symbol. In subblock 1452, block 1450 may optionally include adjusting the CLI based on this ratio. For example, the configuration of the measurement resources may include a list of multiple CSI-IM resources and scaling values, each scaling value corresponding to a CSI-IM resource having an associated ratio for the aggressor UE. The victim UE may adjust the measurement of each CSI-IM resource based on the corresponding scaling factor.

[0181] In some implementations, where the configuration of measurement resources includes periodic or semi-persistent CSI-IM, the frequency domain allocation of CSI-IM can change over time slots. In sub-block 1454, block 1450 may include cycling over the frequency domain allocation sequence. Alternatively, in sub-block 1456, block 1450 may include following a deterministic finite state machine with parameters configured by the configuration of the measurement resources. As yet another example, the CSI-IM resource frequency domain allocation may follow predefined rules based on a time slot format, and the victim UE may measure CLI or CSI based on the time slot's CSI-IM resource frequency domain allocation.

[0182] In some implementations, the configuration of measurement resources may include the configuration of semi-persistent CSI-IM resources and the TCI state of the CSI-IM indicating QCL spatial reception parameters. The TCI state may be associated with each semi-persistent CSI-IM resource. The measurement CLI may include using the TCI state associated with each semi-persistent CSI-IM resource for each instance of the semi-persistent CSI-IM resource. In some implementations, the configuration of measurement resources may indicate a list of TCI states associated with the semi-persistent CSI-IM resources. The measurement CLI may include cycling through the TCI state list for multiple instances of the semi-persistent CSI-IM resources. In some implementations, the configuration of measurement resources may indicate a sequence of TCI state lists associated with the semi-persistent CSI-IM resources. The measurement CLI may include cycling through the TCI state list for multiple instances of the semi-persistent CSI-IM resources. The victim UE may use one of the TCI state lists for each instance of the semi-persistent CSI-IM resource. In view of the foregoing, the UE 104, RX processor 356, or controller / processor 359 executing CLI component 140 or measurement component 144 may provide components for measuring CLI or SI on CSI-IM resources.

[0183] In block 1460, method 1400 may include reporting CLI or SI to the base station according to the CLI report configuration. In some implementations, for example, UE 104, TX processor 368, or controller / processor 359 may execute CLI component 140 or reporting component 146 to report CLI or SI to the base station according to the CLI report configuration. For example, depending on the CLI report configuration, CLI or SI may include a value for each DMRS symbol or an average value across DMRS symbols. In some implementations, in sub-block 1456, block 1450 may include determining to discard a report when the CLI value is less than a configured threshold. For example, the CLI value may be the average of CLI values ​​for the same QCL spatial reception parameter, and the report may include pairs of CLI values ​​and QCL spatial reception parameters. In some implementations, only pairs of CLI values ​​that satisfy the configured threshold may be included. In other implementations, the CLI value may be the average of CLI values ​​across all QCL spatial reception parameters. Therefore, the UE 104, TX processor 368, or controller / processor 359 executing CLI component 140 or capability component 149 can provide components for reporting CLI or SI to the base station according to the CLI reporting configuration.

[0184] Figure 15 This is a flowchart of example method 1500, which is used by a base station to schedule a PUSCH for an aggressor UE and a corresponding CSI-IM for a victim UE to perform CLI reporting. Method 1500 can be performed by a base station (such as base station 102, which may include memory 376, and may be the entire base station 102 or components of base station 102, such as scheduling component 120, TX processor 316, RX processor 370, or controller / processor 375). Method 1500 can be performed by scheduling component 120, which communicates with CLI component 140 of victim UE 104b and PUSCH component of aggressor UE 104a.

[0185] In block 1510, method 1500 may optionally include receiving an indication of one or more capabilities of the UE. In some implementations, for example, base station 102, RX processor 370, or controller / processor 375 may execute scheduling component 120 or capability receiver 1210 to receive an indication of one or more capabilities of the UE. The UE may be an aggressor UE 104a, a victim UE 104b, or both. Therefore, base station 102, RX processor 370, or controller / processor 375 executing scheduling component 120 or capability receiver 1210 may provide components for receiving an indication of one or more capabilities of the UE.

[0186] In block 1520, method 1500 may include a configuration for transmitting PUSCH transmissions including PUSCH symbols and DMRS symbols to an aggressor UE. In some embodiments, for example, base station 102, TX processor 316, or controller / processor 375 may execute scheduling component 120 or PUSCH scheduler 122 to configure the transmission of PUSCH transmissions including PUSCH symbols and DMRS symbols to an aggressor UE. Therefore, base station 102, TX processor 316, or controller / processor 375 executing scheduling component 120 or PUSCH scheduler 122 may provide components for configuring the transmission of PUSCH transmissions including PUSCH symbols and DMRS symbols to an aggressor UE.

[0187] In block 1530, method 1500 may include transmitting to the victim UE the configuration of measurement resources including CSI-IM resources and the configuration of CLI reports. In some implementations, for example, base station 102, TX processor 316, or controller / processor 375 may execute scheduling component 120 or CSI-IM scheduler 124 to transmit to the victim UE the configuration of measurement resources including CSI-IM resources and the configuration of CLI reports. Therefore, base station 102, TX processor 316, or controller / processor 375 executing scheduling component 120 or CSI-IM scheduler 124 may provide components for transmitting to the victim UE the configuration of measurement resources including CSI-IM resources and the configuration of CLI reports.

[0188] In block 1540, method 1500 may include receiving CLI or SI measurements based on the configuration of measurement resources. In some embodiments, for example, base station 102, RX processor 370, or controller / processor 375 may execute scheduling component 120 or reporting component 126 to receive CLI or SI measurements based on the configuration of measurement resources. In some embodiments, in sub-block 1542, block 1540 may include filtering CLI or SI based on whether an aggressor UE transmitted a PUSCH transmission. For example, reporting component 126 may determine whether decoder 1220 received a PUSCH transmission corresponding to CLI or SI and ignore reported CLI or SI values ​​that do not correspond to received PUSCH transmissions. Therefore, base station 102, RX processor 370, or controller / processor 375 executing scheduling component 120 or reporting component 126 may provide components for receiving CLI or SI measurements based on the configuration of measurement resources.

[0189] Figure 16This is a flowchart of an example method 1600 for an aggressor UE to transmit PUSCH based on a group common DCI. Method 1600 can be performed by a UE (such as UE 104, which may include memory 360, and may be the entire UE 104 or components of UE 104, such as PUSCH component 198, TX processor 368, RX processor 356, or controller / processor 359). Method 1600 can be performed by PUSCH component 198 communicating with scheduling component 120 of base station 102. Optional blocks are shown in dashed lines.

[0190] In block 1610, method 1600 may optionally include transmitting an indication that the aggressor UE supports a group common DCI for triggering configuration permission in the uplink. In some implementations, for example, UE 104, TX processor 368, or controller / processor 359 may execute PUSCH component 198 or capability component 149 to transmit an indication that the aggressor UE supports a group common DCI for triggering configuration permission in the uplink. Thus, UE 104, TX processor 368, or controller / processor 359 executing PUSCH component 198 or capability component 149 may provide components for transmitting an indication that the aggressor UE supports a group common DCI for triggering configuration permission in the uplink.

[0191] In block 1620, method 1600 may include receiving a group common DCI, which includes a first portion scheduling PUSCH transmissions for an aggressor UE and a second portion including one or more blocks indicating a CSI-IM resource set for one or more victim UEs. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may execute PUSCH component 198 to receive a group common DCI 900, which includes a first portion 910 scheduling PUSCH transmissions for an aggressor UE and a second portion 920 including one or more blocks 922 indicating a CSI-IM resource set for one or more victim UEs. Thus, UE 104, RX processor 356, or controller / processor 359 executing PUSCH component 198 may provide components for configuring measurement resources from a base station that include channel CSI-IM resources matching the PUSCH symbols or DMRS symbols of the aggressor UE.

[0192] In block 1630, method 1600 may include determining the PUSCH configuration based on the group common DCI. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may execute PUSCH component 198 to determine the PUSCH configuration based on the group common DCI 900. Therefore, UE 104, RX processor 356, or controller / processor 359 executing PUSCH component 198 may provide components for determining the PUSCH configuration based on the group common DCI.

[0193] In block 1640, method 1600 may include transmitting PUSCH transmissions based on PUSCH configuration. In some implementations, for example, UE 104, TX processor 368, or controller / processor 359 may execute PUSCH component 198 to transmit PUSCH transmissions based on PUSCH configuration. Therefore, UE 104, TX processor 368, or controller / processor 359 executing PUSCH component 198 may provide components for transmitting PUSCH transmissions based on PUSCH configuration.

[0194] The foregoing description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein, unless specifically stated otherwise, reference to elements in the singular form is not intended to mean “one and only one,” but rather “one or more.” The word “exemplary” as used herein means “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless otherwise specifically stated, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of elements throughout the various aspects described herein that are known to or will be known thereafter by those skilled in the art are expressly incorporated herein by reference and are intended to be included in the claims. Furthermore, nothing disclosed herein is intended to be donated to the public domain, whether or not such disclosure is expressly stated in the claims. The terms "module", "mechanism", "element", "device", etc., cannot replace the term "part". Therefore, no claim element is to be interpreted as a part plus function unless the element is expressly stated using the phrase "part for...".

Claims

1. A method for wireless communication for a second user equipment (UE), comprising: The configuration of measurement resources, including Channel State Information Interference Measurement (CSI-IM) resources, and the configuration of Cross-Link Interference (CLI) reports are received from the node, wherein the CSI-IM resources are matched with the Physical Uplink Shared Channel (PUSCH) symbols or Demodulation Reference Signal (DMRS) symbols of the first UE. Measure CLI or self-interference (SI) on CSI-IM resources based on the configuration of measurement resources; and Report CLI or SI to the node according to the CLI reporting configuration.

2. The method according to claim 1, wherein, The CLI or SI includes a value for each DMRS symbol.

3. The method according to claim 1, wherein, The CLI or SI includes the average value on the DMRS symbol.

4. The method according to claim 1, wherein, The configuration of the measurement resources includes the ratio of the energy per resource element (EPRE) of the PUSCH symbol to the EPRE of the DMRS symbol, and wherein measuring CLI or SI includes adjusting the CLI based on the ratio.

5. The method according to claim 4, wherein, The configuration of the measurement resources includes multiple CSI-IM resources and a list of scaling values, with each scaling value corresponding to one CSI-IM resource.

6. The method according to claim 1, wherein, The configuration for receiving measurement resources and CLI reports includes an indication of the PUSCH bandwidth for receiving dynamically scheduled PUSCH transmissions for the first UE.

7. The method according to claim 6, wherein, The CLI report configuration instructions are for aperiodic CLI reports for subband CLIs corresponding to the frequency domain allocation of PUSCH transmissions.

8. The method according to claim 6, wherein, The configuration of measurement resources includes: periodic or semi-persistent CSI-IM, wherein the frequency domain allocation of the CSI-IM changes with time slots; or non-periodic CSI-IM resources that match the PUSCH bandwidth.

9. The method according to claim 1, wherein, The configuration of receiving measurement resources includes receiving group common downlink control information (DCI), which dynamically schedules PUSCH transmissions for the first UE.

10. The method according to claim 1, wherein, The configuration of the receiving measurement resources includes: Receive one or more semi-persistent scheduling (SPS) configurations for CSI-IM resources, each SPS configuration corresponding to a corresponding configuration permission for PUSCH transmission for the first UE; and Receive the group public DCI that activates one of the SPS configurations and the corresponding configuration license.

11. The method according to claim 1, wherein, The configuration of receiving measurement resources includes the configuration of receiving semi-persistent CSI-IM resources, wherein the periodicity and offset of the semi-persistent CSI-IM resources are matched with the configuration permission of the first UE.

12. The method according to claim 11, wherein, The semi-persistent CSI-IM resources are activated by either a Media Access Control (MAC) element (CE) or a common DCI comprising one or more blocks, each block indicating the set of CSI-IM resources to be activated, wherein the second UE is configured with an index corresponding to one of the one or more blocks.

13. The method according to claim 1, wherein, The configuration of the receiving measurement resources includes: Receive one or more semi-persistent scheduling (SPS) configurations for CSI-IM resources, each SPS configuration corresponding to a corresponding configuration permission for a PUSCH transmission for the first UE; Receive configuration of semi-persistent CSI-IM resources, wherein the periodicity and offset of the semi-persistent CSI-IM resources match the configuration permission of the first UE; and Receive configuration based on semi-persistent CSI-IM resources to activate one of the groups of public DCIs in the SPS configuration and CLI report.

14. The method according to claim 1, wherein, The configuration of the received measurement resources includes the configuration of the received semi-persistent CSI-IM resources and the Transmission Configuration Indicator (TCI) status of the CSI-IM, the TCI status indicating the Quasi-Cooperative Positioning (QCL) spatial reception parameters.

15. The method according to claim 14, wherein, The configuration indication of the measurement resource is the TCI state associated with each semi-persistent CSI-IM resource, wherein the measurement CLI includes, for each instance of the semi-persistent CSI-IM resource, the TCI state associated with each semi-persistent CSI-IM resource.

16. The method of claim 14, wherein, The measurement resource configuration indicates a list of TCI states associated with the semi-persistent CSI-IM resource, wherein the measurement CLI includes multiple instances of the semi-persistent CSI-IM resource cycling through the TCI state list.

17. The method of claim 1, further comprising transmitting an indication of whether the second UE supports one or more of the following: CLI or SI measurements in CSI-IM resources; common DCI for PUSCH configuration; Public DCIs used to trigger CLI measurements and reporting; explicit or implicit indications of CSI-IM resources in public DCIs; public DCIs used to trigger configuration permissions in the uplink; Common DCI for triggering downlink SPS; Common DCI for triggering semi-persistent CSI-IM resources; A common DCI for triggering semi-persistent CLI reports; a QCL for CLI measurements; or a different QCL for the timing of semi-persistent CSI-IM measurements.

18. A method for wireless communication of a node, comprising: Configuration for transmitting PUSCH transmission, including Physical Uplink Shared Channel (PUSCH) symbols and Demodulation Reference Signal (DMRS) symbols, to the first User Equipment (UE); The configuration of measurement resources, including Channel State Information Interference Measurement (CSI-IM) resources and Cross-Link Interference (CLI) reports, is transmitted to the second UE, wherein the CSI-IM resources are matched with the PUSCH symbols or DMRS symbols of the first UE; and Based on the configuration of measurement resources, receive measurements of cross-link interference (CLI) or self-interference (SI).

19. The method according to claim 18, wherein, The measurement of CLI or SI includes a value for each DMRS symbol.

20. The method according to claim 18, wherein, Measurements for CLI or SI include the average value on the DMRS symbol.

21. The method according to claim 18, wherein, The configuration of the measured resources includes the ratio of energy per resource element (EPRE) of the PUSCH symbol to the EPRE of the DMRS symbol.

22. The method according to claim 18, wherein, The configuration of measurement resources includes an indication of the PUSCH bandwidth for dynamically scheduled PUSCH transmissions for the first UE.

23. The method according to claim 18, wherein, The configuration of measurement resources includes group common downlink control information (DCI), which dynamically schedules PUSCH transmissions for the first UE.

24. The method according to claim 18, wherein, The configuration of measurement resources includes: One or more semi-persistent scheduling (SPS) configurations for CSI-IM resources, each SPS configuration corresponding to a corresponding configuration license for a PUSCH transmission for the first UE; and Activate one of the SPS configurations and the corresponding configuration license for the group's public DCI.

25. The method according to claim 18, wherein, The configuration of measurement resources includes the configuration of semi-persistent CSI-IM resources, wherein the periodicity and offset of the semi-persistent CSI-IM resources are matched with the configuration permission of the first UE.

26. The method according to claim 18, wherein, The configuration of measurement resources includes: One or more semi-persistent scheduling (SPS) configurations for CSI-IM resources, each SPS configuration corresponding to a corresponding configuration license for PUSCH transmission for the first UE; The configuration of semi-persistent CSI-IM resources, wherein the periodicity and offset of the semi-persistent CSI-IM resources are matched with the configuration permissions of the first UE; and Activate a group of public DCIs in the SPS configuration and CLI report based on the configuration of semi-persistent CSI-IM resources.

27. The method according to claim 18, wherein, The configuration of measurement resources includes the configuration of semi-persistent CSI-IM resources and the Transmission Configuration Indicator (TCI) status of CSI-IM that indicates the Quasi-Cooperative Positioning (QCL) spatial reception parameters.

28. The method of claim 18, further comprising receiving an indication of whether the second UE supports one or more of the following: CLI or SI measurements in CSI-IM resources; common DCI for PUSCH configuration; Public DCIs used to trigger CLI measurements and reporting; explicit or implicit indications of CSI-IM resources in public DCIs; public DCIs used to trigger configuration permissions in the uplink; Common DCI for triggering downlink SPS; Common DCI for triggering semi-persistent CSI-IM resources; A common DCI for triggering semi-persistent CLI reports; a QCL for CLI measurements; or a different QCL for the timing of semi-persistent CSI-IM measurements.

29. An apparatus for wireless communication at a second user equipment (UE), comprising: Memory, which stores executable instructions for a computer; and At least one processor, communicatively coupled to memory and configured to execute the instructions to: The configuration of measurement resources, including Channel State Information Interference Measurement (CSI-IM) resources and Cross-Link Interference (CLI) reports, is received from the node. The CSI-IM resource is matched with the Physical Uplink Shared Channel (PUSCH) symbol or Demodulation Reference Signal (DMRS) symbol of the first UE; Measure CLI or self-interference (SI) on CSI-IM resources based on the configuration of measurement resources; and Report CLI or SI to the node according to the CLI reporting configuration.

30. An apparatus for wireless communication at a node, comprising: Memory, which stores executable instructions for a computer; and At least one processor, communicatively coupled to memory and configured to execute the instructions to: Configuration for transmitting PUSCH transmission, including Physical Uplink Shared Channel (PUSCH) symbols and Demodulation Reference Signal (DMRS) symbols, to the first User Equipment (UE); The configuration of measurement resources, including Channel State Information Interference Measurement (CSI-IM) resources and Cross-Link Interference (CLI) reports, is transmitted to the second UE. The CSI-IM resource matches the PUSCH symbol or DMRS symbol of the first UE; and Based on the configuration of measurement resources, receive measurements of cross-link interference (CLI) or self-interference (SI).

31. An apparatus for wireless communication at a second user equipment (UE), comprising: Components for configuring measurement resources, including Channel State Information Interference Measurement (CSI-IM) resources, and cross-link interference (CLI) reports, to receive data from a node, wherein... The CSI-IM resource is matched with the Physical Uplink Shared Channel (PUSCH) symbol or Demodulation Reference Signal (DMRS) symbol of the first UE; Components used to measure CLI or self-interference (SI) on CSI-IM resources based on the configuration of the measurement resources; and A component used to report CLI or SI to nodes according to the CLI reporting configuration.

32. An apparatus for wireless communication at a node, comprising: A component for configuring PUSCH transmission, including Physical Uplink Shared Channel (PUSCH) symbols and Demodulation Reference Signal (DMRS) symbols, to a first user equipment (UE). A component for transmitting to the second UE the configuration of measurement resources, including Channel State Information Interference Measurement (CSI-IM) resources and the configuration of Cross-Link Interference (CLI) reports, wherein, The CSI-IM resource matches the PUSCH symbol or DMRS symbol of the first UE; and A component for receiving measurements of cross-link interference (CLI) or self-interference (SI) based on the configuration of measurement resources.

33. A computer-readable medium having one or more computer instructions recorded thereon, which, when executed by one or more processors of a second user equipment (UE), cause the one or more processors to perform a wireless communication method according to any one of claims 1-17.

34. A computer-readable medium having one or more computer instructions recorded thereon, which, when executed by one or more processors of a node, cause the one or more processors to perform a method of wireless communication according to any one of claims 18-28.

35. A computer program product comprising one or more computer instructions, which, when executed by one or more processors of a second user equipment (UE), cause the one or more processors to perform a method of wireless communication according to any one of claims 1-17.

36. A computer program product comprising one or more computer instructions, which, when executed by one or more processors of a node, cause the one or more processors to perform a method of wireless communication according to any one of claims 18-28.

Images