Physical layer cross-link interference measurement and reporting

Abstract

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for physical layer cross link interference (CLI) measurement and reporting.

Description

Technical Field

[0001] Several aspects of this disclosure relate to wireless communication, and more specifically to techniques for physical layer measurement and reporting of cross-link interference. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. These wireless communication systems can employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include the 3GPP Long Term Evolution (LTE) system, LTE-A Advanced (LTE-A) system, Code Division Multiple Access (CDMA) system, Time Division Multiple Access (TDMA) system, Frequency Division Multiple Access (FDMA) system, Orthogonal Frequency Division Multiple Access (OFDMA) system, Single Carrier Frequency Division Multiple Access (SCFDMA) system, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system.

[0003] In some examples, a radio multiple access communication system may include multiple base stations (BSs), each capable of simultaneously supporting communication from multiple communication devices (also known as user equipment (UEs)). In LTE or LTE-A networks, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in next-generation, new radio (NR), or 5G networks), a radio multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (DUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit-receive points (TRPs), etc.) communicating with multiple central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a set of one or more distributed units communicating with a central unit may define an access node (e.g., which may be referred to as a base station, a 5G NB, a next-generation NodeB (gNB or gNodeB), a TRP, etc.). A base station or distributed unit may communicate with a group of UEs on downlink channels (e.g., for transmission from a base station or to a UE) and uplink channels (e.g., for transmission from a UE to a base station or distributed unit).

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, country, region, and even global levels. New Radio (NR) (e.g., 5G) is an example of an emerging telecommunications standard. NR is a set of enhancements to the LTE mobile standard released by 3GPP. It is designed to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on both the downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0005] However, with the continued growth in demand for mobile broadband access, further improvements to NR and LTE technologies are needed. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0006] The systems, methods, and apparatuses of this disclosure each have several aspects, none of which is solely responsible for their desired properties. Without limiting the scope of this disclosure as set forth in the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," those skilled in the art will understand how the features of this disclosure provide advantages including improved communication between access points and stations in a wireless network.

[0007] Certain aspects of this disclosure provide a method for wireless communication by a user equipment (UE). The method generally includes: receiving a resource configuration indicating time-frequency cross-link interference (CLI) measurement resources for physical layer measurements of CLI caused by uplink transmissions made by one or more other UEs during a downlink time slot of the UE; receiving a reporting configuration indicating a time resource for CLI reporting timing; measuring at least one CLI metric based on measurements performed at the measurement timing according to the resource configuration; and reporting the at least one CLI metric at the reporting timing according to the reporting configuration.

[0008] Certain aspects of this disclosure provide a method for wireless communication by a network entity. The method generally includes: signaling to a user equipment (UE) a resource configuration indicating time-frequency cross-link interference (CLI) measurement resources for physical layer measurements of CLI caused by uplink transmissions performed by one or more other UEs during the UE's downlink time slot; signaling to the UE a reporting configuration indicating a time resource for CLI reporting timing; and receiving from the UE a report of at least one CLI metric based on a measurement performed at the measurement timing according to the resource configuration, wherein the report is received at a reporting timing according to the reporting configuration.

[0009] Various aspects of this disclosure provide components, apparatus, processors, and computer-readable media for performing the methods described herein.

[0010] 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 illustrate in detail some exemplary features of one or more aspects. However, these features only indicate some of the various ways in which the principles of each aspect can be employed. Attached Figure Description

[0011] To gain a more detailed understanding of the foregoing features of this disclosure, reference can be made to several aspects which have been briefly outlined above, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only some typical aspects of this disclosure and should not be considered as limiting its scope, as the description may acknowledge other equally valid aspects.

[0012] Figure 1 It is a block diagram that conceptually illustrates an example telecommunications system according to certain aspects of this disclosure.

[0013] Figure 2 It is a block diagram that conceptually illustrates the design of an example base station (BS) and user equipment (UE) according to certain aspects of this disclosure.

[0014] Figure 3 Examples of frame formats for New Radio (NR) systems according to certain aspects of this disclosure are provided.

[0015] Figure 4 This example illustrates how cross-link interference can occur when an uplink subframe of one UE overlaps with a downlink subframe of another UE.

[0016] Figure 5A and Figure 5B Examples of cross-link interference that can be measured and reported according to certain aspects of this disclosure are illustrated.

[0017] Figure 6 Example operations of wireless communication performed by a user equipment (UE) according to certain aspects of this disclosure are illustrated.

[0018] Figure 7 Example operations of wireless communication by network entities according to certain aspects of this disclosure are illustrated.

[0019] Figure 8 Examples of physical layer CLI measurement resources and reporting configurations are provided according to certain aspects of this disclosure.

[0020] Figures 9A to 9C Examples of minimum timing delays reported by physical layer CLI measurements according to certain aspects of this disclosure are provided.

[0021] For ease of understanding, the same reference numerals are used where possible to denote the same elements common in the accompanying drawings. Elements disclosed in one aspect are intended to be usefully used in other aspects without specific description. Detailed Implementation

[0022] Several aspects of this disclosure relate to wireless communications, and more specifically to techniques for physical layer measurement and reporting of cross-link interference (CLI).

[0023] Compared to higher-level (e.g., layer 3) CLI reporting mechanisms, the techniques presented in this paper can provide greater flexibility and faster reporting because they only perform physical layer processing and avoid inter-layer communication for each CLI report.

[0024] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various processes or components may be appropriately omitted, substituted, or added to the various examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with reference to some examples may be combined in other examples. For example, the apparatus or practice may be implemented using any number of aspects set forth herein. Furthermore, the scope of this disclosure is intended to cover apparatus or methods that utilize other structures, functions, or structures and functions besides those set forth herein, or different from those set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims. The term "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 more preferred or advantageous than other aspects.

[0025] The technologies described in this article can be used in various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. CDMA networks can implement wireless technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers the IS-2000, IS-95, and IS-856 standards. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS).

[0026] New Radio (NR) is an emerging wireless communication technology developed in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are UMTS versions using EUTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP 2). The technologies described herein can be used in the aforementioned wireless networks and radio technologies, as well as other wireless networks and radio technologies. For clarity, although various aspects may be described herein using terms commonly associated with 3G and / or 4G wireless technologies, many aspects of this disclosure can be applied to other generation-based communication systems, such as 5G and later, including NR technology.

[0027] New Radio (NR) access (e.g., 5G technology) can support a variety of wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmW) targeting high carrier frequencies (e.g., 25 GHz or higher), massive machine-type communication (mMTC) targeting non-backward compatible MTC technologies, and / or mission-critical services targeting ultra-reliable low-latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different Transmit Time Intervals (TTIs) to meet their respective Quality of Service (QoS) requirements. Furthermore, these services can coexist in the same subframe.

[0028] Example wireless communication system

[0029] Figure 1 An example wireless communication network 100 (e.g., an NR / 5G network) is illustrated, in which various aspects of this disclosure can be implemented. For example, wireless network 100 may include: UE 120, which is configured to perform... Figure 6 Operation 600 for physical layer CLI measurement and reporting. Similarly, wireless network 100 may include: base station 110, which is configured to perform... Figure 7 Operation 700 is used to configure the UE for physical layer CLI measurements and reporting.

[0030] like Figure 1 As shown, the wireless network 100 may include multiple base stations (BS) 110 and other network entities. A BS may be a station communicating with a user equipment (UE). Each BS 110 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a NodeB (NB) and / or the NodeB subsystem serving that coverage area, depending on the context in which the term is used. In NR systems, the term "cell" is interchangeable with Next Generation NodeB (gNB), New Radio Base Station (NR BS), 5G NB, Access Point (AP), or Transmitter Receiver Point (TRP). In some examples, the cell may not be fixed, and the geographic area of ​​the cell may move depending on the location of the mobile BS. In some examples, base stations may use any suitable transport network to interconnect with each other and / or with one or more other base stations or network nodes (not shown) in the wireless communication network 100 via various types of backhaul interfaces such as direct physical connections, wireless connections, virtual networks, etc.

[0031] Typically, any number of wireless networks can be deployed within a given geographical area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, wireless interface, etc. A frequency can also be referred to as a carrier, subcarrier, channel, tone, subband, etc. Each frequency can support a single RAT within a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5GRAT networks can be deployed.

[0032] Base stations (BSs) can provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells. A macrocell can cover a relatively large geographical area (e.g., a radius of several kilometers) and allows unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographical area and allows unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographical area (e.g., a home) and allows restricted access for UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in a home, etc.). A BS for a macrocell can be called a macro BS. A BS for a picocell can be called a pico BS. A BS for a femtocell can be called a femto BS or a home BS. Figure 1 In the example shown, base stations 110a, 110b, and 110c can be macro base stations for macro cells 102a, 102b, and 102c, respectively. BS 110x can be a pico BS for pico cell 102x. Base stations 110y and 110z can be femto base stations for femto cells 102y and 102z, respectively. A BS can support one or more (e.g., three) cells.

[0033] The wireless communication network 100 may also include relay stations. A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., a BS or a UE) and transmits data and / or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions from other UEs. Figure 1 In the example shown, relay station 110r can communicate with BS110a and UE 120r to facilitate communication between BS 110a and UE 120r. A relay station can also be referred to as a relay BS, relay station, etc.

[0034] Wireless network 100 can be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, and repeaters. These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 20 watts), while pico BSs, femto BSs, and repeaters can have lower transmit power levels (e.g., 1 watt).

[0035] The wireless communication network 100 can support synchronous or asynchronous operation. For synchronous operation, the base stations (BSs) can have similar frame timings, and transmissions from different BSs can be approximately time-aligned. For asynchronous operation, the BSs can have different frame timings, and transmissions from different BSs can be time-disaligned. The techniques described herein can be used for both synchronous and asynchronous operations.

[0036] Network controller 130 can be coupled to a group of BSs and provide coordination and control over these BSs. Network controller 130 can communicate with BS 110 via backhaul. BS 110 can also communicate with each other via wireless or wired backhaul (e.g., directly or indirectly).

[0037] UEs 120 (e.g., 120x, 120y, etc.) can be distributed throughout the wireless network 100, and each UE can be fixed or mobile. UE can also be referred to as: mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical equipment, biosensor / device, wearable devices such as smartwatches, smart clothes, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets, etc.), entertainment devices (e.g., music devices, video devices, satellite radios, etc.), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, GPS devices, gaming devices, augmented reality devices (augmented reality (AR), extended reality (XR), or virtual reality (VR)), or any other suitable device configured to communicate via wireless or wired media.

[0038] Some UEs can be considered Machine-Type Communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity to or from a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices, which can be narrowband IoT (NB-IoT) devices.

[0039] Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, often referred to as tones, bins, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25, 2.5, 5, 10, or 20MHz, there can be 1, 2, 4, 8, or 16 subbands respectively.

[0040] While many aspects of the examples described herein can be associated with LTE technology, many aspects of this disclosure can be applied to other wireless communication systems such as NR. NR can utilize OFDM with CP on both the uplink and downlink, and includes support for half-duplex operation using TDD. Beamforming can be supported, and beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. MIMO configuration in DL can support up to 8 transmit antennas, where up to 8 streams are transmitted in multi-layer DL, and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE can be supported. Up to 8 serving cells can support aggregation of multiple cells.

[0041] In some scenarios, air interface access can be scheduled. For example, a scheduling entity (e.g., base station (BS), node B, eNB, gNB, etc.) can allocate resources for communication between some or all devices and apparatuses within its service area or cell. The scheduling entity can be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. In other words, for scheduled communication, subordinate entities can utilize resources allocated by one or more scheduling entities.

[0042] A base station is not the only entity that can act as a scheduling entity. In some examples, a UE can act as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs can utilize the resources scheduled by that UE for wireless communication. In some examples, a UE can act as a scheduling entity in a peer-to-peer (P2P) network and / or a mesh network. In the mesh network example, in addition to communicating with a scheduling entity, UEs can also communicate directly with each other.

[0043] Back Figure 1 This diagram illustrates various potential deployments across different deployment scenarios. For example, in... Figure 1 In the diagram, a solid line with a double arrow indicates a desired transmission between the UE and the serving BS, which is a BS designated to serve the UE on the downlink and / or uplink. A thin dashed line with a double arrow indicates interference transmission between the UE and the BS. Other lines exemplify component-to-component (e.g., UE-to-UE) communication options.

[0044] Figure 2 For example (e.g., in) Figure 1 Example components of BS 110a and UE 120a in the wireless communication network 100, which can be used to implement aspects of this disclosure.

[0045] In BS 110a, transmit processor 220 can receive data from data source 212 and control information from controller / processor 240. The control information can be used for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GCPDCCH), etc. Data can be used for the Physical Downlink Shared Channel (PDSCH), etc. Processor 220 can process the data and control information (e.g., encoding and symbol mapping) to obtain data symbols and control symbols, respectively. Transmit processor 220 can also generate reference symbols, such as for the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Cell-Specific Reference Signal (CRS). Transmit (TX) Multiple-Input Multiple-Output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols (if applicable) and can provide an output symbol stream to modulators (MODs) 232a-232t. Each modulator 232 can process its own output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator can further process the output sample stream (e.g., convert to analog, amplify, filter, and up-convert) to obtain a downlink signal. The downlink signals from modulators 232a-232t can be transmitted via antennas 234a-234t, respectively.

[0046] In UE 120a, antennas 252a-252r can receive downlink signals from BS 110a and can provide received signals to demodulators (DEMODs) in transceivers 254a-254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain input samples. Each demodulator can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain received symbols from all demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. Receiver processor 258 can process the detected symbols (e.g., demodulate, deinterleave, and decode), provide decoded data of UE 120a to data sink 260, and provide decoding control information to controller / processor 280.

[0047] On the uplink, at UE 120a, transmit processor 264 can receive and process data from data source 262 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from controller / processor 280 (e.g., for the Physical Uplink Control Channel (PUCCH)). Transmit processor 264 can also generate reference symbols for reference signals (e.g., sounding reference signals (SRS)). If applicable, the symbols from transmit processor 264 can be pre-coded by TX MIMO processor 266, further processed by demodulators in transceivers 254a-254r (e.g., for SC-FDM, etc.), and transmitted to BS 110a. At BS 110a, uplink signals from UE 120a can be received by antenna 234, processed by modulator 232, detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120a. The receiver processor 238 can provide decoded data to the data sink 239 and decoded control information to the controller / processor 240.

[0048] Memory 242 and 282 can store data and program code of BS 110a and UE 120a, respectively. Scheduler 244 can schedule UE to transmit data on downlink and / or uplink.

[0049] The controller / processor 280 and / or other processors and modules at UE 120a may perform or direct the execution of processes according to the techniques described herein. For example, the controller / processor 280 and / or other processors and modules at UE 120a may perform (or be used by UE 120a to perform) Figure 6Operation 600. Similarly, the controller / processor 240 and / or other processors and modules at BS 110a can perform or direct the execution of processes described herein. For example, the controller / processor 240 and / or other processors and modules at BS 110a can perform (or be used by BS 121a to perform) Figure 7 Operation 700. Although shown at the controller / processor, other components of UE 120a or BS 110a may be used to perform the operations described herein.

[0050] The embodiments discussed herein can include various interval and timing deployments. For example, in LTE, the basic transmit time interval (TTI), or packet duration, is a 1ms subframe. In NR, the subframe is still 1ms, but the basic TTI is called a slot. Depending on the subcarrier spacing, a subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16 slots). NR RBs are 12 consecutive frequency subcarriers. NR can support a basic subcarrier spacing of 15kHz and can define other subcarrier spacings relative to the basic subcarrier spacing, such as 30kHz, 60kHz, 120kHz, 240kHz, etc. Symbol and slot lengths are scaled with the subcarrier spacing. The CP length also depends on the subcarrier spacing.

[0051] Figure 3 This is a diagram illustrating an example of NR frame format 600. The transmission timeline for each of the downlink and uplink can be divided into radio frame units. Each radio frame can have a predetermined duration (e.g., 10 ms) and can be divided into 10 subframes, each 1 ms in number, indexed from 0 to 9. Depending on the subcarrier spacing, each subframe can include a variable number of time slots. Depending on the subcarrier spacing, each time slot can include a variable number of symbol periods (e.g., 7 or 14 symbols). An index can be assigned to the symbol periods within each time slot. A mini-slot is a sub-slot structure (e.g., 2, 3, or 4 symbols).

[0052] Each symbol in a time slot can indicate the link direction of data transmission (e.g., DL, UL, or flexible), and the link direction can be dynamically switched for each subframe. The link direction can be based on the time slot format. Each time slot can include DL / UL data as well as DL / UL control information.

[0053] In NR, a synchronization signal (SS) block (SSB) is transmitted. The SS block includes the PSS, SSS, and double-symbol PBCH. The SS block can be transmitted at fixed time slot positions, for example... Figure 3The symbols shown are 0-3. The UE can use PSS and SSS for cell search and acquisition. PSS provides half-frame timing, and SS provides CP length and frame timing. PSS and SSS can provide cell identity. PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frames, SS burst set period, system frame number, etc.

[0054] Further system information, such as Residual Minimal System Information (RMSI), System Information Block (SIB), and Other System Information (OSI), can be transmitted on the Physical Downlink Shared Channel (PDSCH) in some subframes.

[0055] Example Physical Layer (Layer 1) CLI Measurement and Reporting

[0056] Several aspects of this disclosure relate to wireless communications, and more specifically to techniques for physical layer measurement and reporting of cross-link interference (CLI). Compared to conventional CLI reporting mechanisms, the CLI reporting mechanism proposed herein, by relying solely on physical layer processing, offers greater flexibility and faster reporting.

[0057] like Figure 4 As shown, if nearby UEs have different UL-DL slot formats, one UE (victim) may receive UL transmissions from another UE (intruder), a phenomenon known as Cross-Link Interference (CLI). In the example shown, UE1 is the intruder, and the CLI appears within the UL symbol (i.e., the interference symbol) of the intruder (UE1) that conflicts with the DL symbol of the victim (UE2). CLI can be caused by any UL transmission from the intruder UE, including PUCCH, PUSCH, RACH preamble, and SRS transmissions.

[0058] In some cases, CLI measurements can be configured at the victim UE, typically at a higher layer, for interference management. For example, a Layer 3 measurement and reporting mechanism for CLI can be defined. In this case, measurements could be based on the Detection Reference Signal (SRS) Received Power (RSRP) of the configured SRS measurement resources and the CLI Received Signal Strength Indicator (RSSI) of the configured CLI RSSI measurement resources. Measurement resource configuration typically includes the periodicity, frequency (RB), and OFDM symbols for the measurement CLI.

[0059] Although Figure 4 The illustration illustrates the conceptual relationship between the time slots of the intruder UE and the victim UE; however, in reality, timing differences may exist between them due to various propagation delays. Whether the victim UE can receive its DL serving cell signal / channel and whether it can also measure CLI resources in the same symbol can depend on the UE's capabilities.

[0060] Typically, the victim UE does not need to know the intruder's TDD UL / DL configuration (i.e., time slot format) or SRS transmission configuration. To measure CLI, the victim UE only needs to follow the CLI measurement resource configuration signaled by the network. The victim UE doesn't even need to know the identity of the intruder UE associated with each configured CLI measurement resource. In practice, the network should be responsible for configuring CLI measurement resources to match the intruder UE's TDD UL / DL or SRS transmission configuration (although this may not be a requirement).

[0061] like Figure 5A As shown, CLI can occur between UEs in different cells. Figure 5B As shown, CLI can occur between UEs within the same cell.

[0062] As previously mentioned, some systems can utilize CLI measurement metrics including SRS-RSRP and CLI-RSSI. SRS-RSRP is typically reported as the linear average of the power contribution of the SRS measured on the configured resource elements within the considered measurement frequency bandwidth in the time resources at the configured measurement time. CLI-RSSI is typically reported as the linear average of the total received power observed only in certain OFDM symbols of the configured resource elements used by the UE for measurement, in the measurement bandwidth.

[0063] Traditional systems typically only support Layer 3 reporting mechanisms, which are sufficient to measure the long-term energy of CLI measurement resources. However, due to the dynamic TDD configuration of intruder UEs, Layer 3 CLI reporting is not flexible or fast enough for measuring dynamic CLI.

[0064] However, several aspects of this disclosure propose a CLI physical layer (layer 1) measurement and reporting method that, compared to a conventional layer 3 framework, is more flexible and faster because it relies solely on physical layer processing without the need for additional inter-layer (i.e., between layer 1 and layer 3) communication for each CLI report.

[0065] Figure 6 and Figure 7 Examples of operations that can be performed by the UE and network entities respectively to perform physical layer CLI measurements and reports according to aspects of this disclosure are illustrated.

[0066] Figure 6 Example operation 600 of a UE performing wireless communication according to certain aspects of this disclosure is illustrated. For example, operation 600 can be performed by... Figure 1 UE 120 execution for physical layer CLI measurements and reporting.

[0067] Operation 600 begins at 602 with the receipt of resource configuration indicating time-frequency cross-link interference (CLI) measurement resources for physical layer measurements of CLI caused by uplink transmissions made by one or more other UEs during the UE's downlink time slots. At 604, the UE receives a report configuration indicating the timing of CLI reporting. In some cases, the resource configuration indicates that the CLI measurement resource type is periodic, semi-persistent, or aperiodic, and the report configuration indicates that the CLI measurement report type is periodic, semi-persistent, or aperiodic.

[0068] At 606, the UE measures at least one CLI metric based on measurements performed at the measurement timing according to resource configuration. At 608, the UE reports at least one CLI metric at the reporting timing according to reporting configuration. As will be described in more detail below, in some cases, the UE may determine the reporting timing for reporting the measured CLI metric based on the association between resource configuration and reporting configuration.

[0069] Figure 7 Example operation 700 illustrates wireless communication between network entities, and can be considered as an example of... Figure 6 This is a supplement to operation 600. For example, operation 700 can be... Figure 1 The base station 110 (e.g., gNB) performs the configuration (execution). Figure 6 The UE (600) is used for physical layer CLI measurements and reporting.

[0070] Operation 700 begins at 702 by signaling to the User Equipment (UE) a resource configuration indicating time-frequency cross-link interference (CLI) measurement resources for physical layer measurements of CLI caused by uplink transmissions made by one or more other UEs during the UE's downlink time slot. At 704, the network entity signals to the UE a reporting configuration of time resources indicating CLI reporting timing. At 706, the network entity receives a report from the UE of at least one CLI metric based on measurements performed at the measurement timing according to the resource configuration, wherein the report is received at the reporting timing according to the reporting configuration.

[0071] As described above, CLI measurement resource configuration and reporting configuration enable the UE (i.e., the victim UE) to perform Layer 1 CLI measurements and reports.

[0072] Typically, CLI measurement resource configuration indicates to the UE the time-frequency resources, time-domain periodicity, and offsets (e.g., slot / symbol offsets) of the measurement resources to be received. If the resource is a reference signal, the configuration may also indicate the parameters used to generate the reference signal and the mapping of the sequence to the configured time-frequency resources.

[0073] CLI reporting configuration typically indicates the time-domain timing at which the UE should perform (and / or report) measurements. CLI reporting configuration typically includes the periodicity and offset of the measurement timing.

[0074] CLI measurement resource configuration and CLI reporting configuration can be configured independently. Both configurations can indicate periodic, semi-persistent, and periodic types. If the CLI measurement resource configuration indicates that the CLI resource type is aperiodic, then aperiodic CLI measurement resources can be triggered by the PDCCH. If the CLI reporting configuration indicates that the CLI report type is aperiodic, then aperiodic CLI measurement reports can be triggered by the PDCCH.

[0075] In some cases, the network can associate resource configuration with reporting configuration, enabling the UE to measure resources and send reports to the network at the associated reporting time.

[0076] Figure 8 An example is shown with an association between CLI measurement resource configuration i and CLI report configuration j, so the UE will measure the resources used for CLI measurement resource configuration j and send a report at the reporting time of each CLI report configuration j.

[0077] The network can indicate the association between CLI resource configurations and CLI reporting configurations based on various options. According to the first option, the network can include the resource configuration ID of the configured CLI measurement resource in the reporting configuration. Alternatively or additionally, the network can include the report configuration ID of the CLI reporting configuration in the CLI resource configuration.

[0078] In some cases, it may be possible to associate a specific type of CLI report configuration with only a specific type of CLI resource configuration. Generally, more semi-static CLI measurement resources can be used for both semi-static and dynamic CLI reports, but not vice versa. The association between CLI resource configurations and CLI report configurations can be considered valid in the following situations:

[0079] If the CLI resource type is periodic, the associated CLI report type can be periodic, semi-persistent, or aperiodic;

[0080] If the CLI resource type is semi-persistent, the associated CLI report type can be either semi-persistent or aperiodic; and

[0081] If the CLI resource type is non-periodic, then the associated CLI report type can only be non-periodic.

[0082] If neither the CLI resource type nor the CLI report type is aperiodic, then the latest CLI measurement resource that can be used to generate the report can have a minimum timing interval before the report is generated, such as... Figure 9A As shown. The interval can be defined in milliseconds (ms), time slots, or symbols. In this case, CLI measurement resources and reports are not dynamically configured for the UE. To accommodate the minimum processing time required by the UE (i.e., the victim UE) to process resources and generate reports, a minimum delay is required between the nearest available resources for report generation.

[0083] In some cases, the minimum timing interval may depend on the CLI metric type (e.g., RSSI or RSRP). For example, for CLI RSSI, the minimum timing interval can be the same as or smaller than that for CLI RSRP, because RSSI is generally simpler to calculate than CLI RSRP.

[0084] If both the CLI resource type and the CLI report type are non-periodic, then a first minimum timing interval may exist between the PDCCH that triggers the resource and the report, and a second minimum timing interval may exist between the triggered resource and the report, such as... Figure 9B As shown above, the interval can be defined in milliseconds, time slots, or symbols.

[0085] First time interval (in) Figure 9B The first timing interval (marked as minimum) is used to accommodate the minimum processing time for PDCCH decoding, resource processing, and report generation. The second timing interval is to accommodate the minimum resource processing and report generation time. It is not necessary to define a minimum interval between PDCCH and resources. This is because if the UE cannot decode the PDCCH fast enough, it can only buffer some DL samples for potential resource reception. The second timing interval (in...) Figure 9B The minimum timing interval (2) marked in the middle can be considered the most critical timeline requirement, in order to allow the UE sufficient time to calculate CLI measurement metrics. For CLI RSSI, Figure 9B Each minimum timing interval shown can be the same as or smaller for CLI RSRP.

[0086] If the CLI resource type is not aperiodic and the CLI report type is aperiodic, then the most recent resource available for generating the report can also have been available before that report. Figure 9C The minimum timing interval is marked as 3. The interval can be defined in milliseconds, time slots, or symbols.

[0087] In this case, CLI measurement resources can be semi-persistent or periodic. The reason for defining a minimum timing interval of 3 is still because the UE needs sufficient time to compute CLI measurement metrics. The reason for not defining a minimum timing interval between the PDCCH (triggering aperiodic reports) and the reports (i.e., indicated by the dashed lines in the diagram) is because the UE is always able to compute CLI measurement metrics for semi-persistent / periodic resources, regardless of whether it receives a PDCCH. Therefore, it can generate a report, and then send the triggered report once the UE decodes the triggering PDCCH. As with the other cases described above, the minimum timing interval of 3 for CLIRSSI can be the same as or smaller than that for CLI RSRP.

[0088] When the CLI measurement resource type is not aperiodic (i.e., periodic or semi-persistent), there may be time-domain measurement limitations for CLI measurements. For example, with limitations configured, the UE may only be allowed to use the most recent transmission of the CLI measurement resource before a defined timing interval. Without limitations configured, the UE may be allowed to use any transmission of the CLI measurement resource before a defined timing interval.

[0089] As proposed in this paper, physical layer CLI measurements and reporting can allow for faster and more flexible CLI reporting, which can enable faster adaptation on the network side. For example, the gNB can reallocate resources and / or adaptively schedule to account for dynamic TDD configuration changes of intruder UEs.

[0090] The methods disclosed herein include one or more steps or actions for implementing the method. The method steps and / or actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of a particular step and / or action may be modified without departing from the scope of the claims.

[0091] As used herein, the phrase “at least one” in relation to a list of items means any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).

[0092] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, derivation, investigation, searching (e.g., searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Additionally, "determine" can include parsing, selecting, picking, building, etc.

[0093] 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 of the claims, wherein, unless specifically stated otherwise, singular elements are not intended to mean “one and only one,” but rather “one or more.” Unless specifically stated otherwise, the term “some” means one or more. All structural and functional equivalents of elements of the various aspects described herein that are known to or will be known hereafter 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 offered to the public, whether or not such disclosure is expressly stated in the claims. No claim element is interpreted pursuant to 35 U.SC 112(f) unless the element is expressly stated using the phrase “component” or, in the case of a method claim, using the phrase “step.”

[0094] The various operations described above can be performed by any suitable component capable of performing the corresponding function. Components may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. For example, the processor controller / processor 280 of UE 120 can be configured to perform… Figure 6 The operation is 600, and Figure 2 The controller / processor 240 of the BS 110 shown can be configured to execute Figure 7 Operation 700.

[0095] The component for receiving may include Figure 2 The receiver shown is (e.g., one or more antennas or a receiver processor). Components for transmitting may include... Figure 2 The transmitter shown is (e.g., one or more antennas or a transmitter processor). The components for determining, processing, disposing, and applying may include a processing system, which may include... Figure 2 One or more processors of the UE 120 and / or one or more processors of the BS 110 shown.

[0096] In some cases, a device may have an interface (output component) that outputs frames to be transmitted rather than the actual transmitted frames. For example, a processor may output frames to a radio frequency (RF) front end for transmission via a bus interface. Similarly, a device may have an interface (acquisition component) that receives frames from another device rather than the actual received frames. For example, a processor may acquire (or receive) frames from an RF front end via a bus interface for reception.

[0097] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor can be a microprocessor, but optionally, it can be any commercially available processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0098] If implemented in hardware, an example hardware configuration could include a processing system in a wireless node. This processing system could be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus could include any number of interconnect buses and bridges. The bus can link various circuits together, including processors, machine-readable media, and bus interfaces. The bus interface can be used to connect network adapters, etc., to the processing system via the bus. The network adapter can be used to implement signal processing functions at the physical (PHY) layer. In user terminal 120 (see...) Figure 1 In this case, the user interface (e.g., keyboard, display, mouse, joystick, etc.) can also be connected to the bus. The bus can also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and will not be described further. The processor can be implemented using one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Those skilled in the art will recognize how best to implement the described functions of the processing system based on the specific application and the overall design constraints imposed on the system as a whole.

[0099] If implemented in software, these functionalities can be stored or transmitted as one or more instructions or code on a computer-readable medium. Software should be interpreted broadly as instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor, allowing the processor to read information from and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. For example, a machine-readable medium may include a transmission line, a carrier wave modulated by data, and / or a computer-readable storage medium on which instructions separate from the wireless node are stored, all accessible to the processor via a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, such as in the case of a cache and / or a general-purpose register file. Examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, disks, optical disks, hard disks, or any other suitable storage media, or any combination thereof. Machine-readable media may be contained in a computer program product.

[0100] Software modules can include single or multiple instructions and can be distributed across several different code segments, within different programs, and across multiple storage media. Computer-readable media can include multiple software modules. Software modules include instructions that, when executed by a device such as a processor, cause the processing system to perform various functions. Software modules can include issue and receive modules. Each software module can reside in a single storage device or be distributed across multiple storage devices. For example, a software module can be loaded from a hard disk into RAM upon the occurrence of a triggering event. During the execution of a software module, the processor can load some instructions into a cache to improve access speed. Then, one or more cache lines can be loaded into a general-purpose register file for processor execution. When referring to the functionality of a software module below, it should be understood that such functionality is implemented by the processor when executing instructions from that software module.

[0101] Furthermore, any connection is appropriately referred to as computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. The disks and discs used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. A disk, where a magnetic disk typically reproduces data magnetically, and a disc, where data is optically reproduced using a laser. Therefore, in some aspects, computer-readable media can include non-transitory computer-readable media (e.g., tangible media). Furthermore, in other aspects, computer-readable media can include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0102] Therefore, some aspects may include computer program products for performing the operations described herein. For example, such computer program products may include computer-readable media on which instructions are stored (and / or encoded) that can be executed by one or more processors to perform the operations described herein. Figures 6 to 7 The instructions for the operation are shown in the figure.

[0103] Furthermore, it should be understood that modules and / or other suitable components for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by the user terminal and / or base station. For example, such a device can be coupled to a server to facilitate the transfer of components for performing the methods described herein. Optionally, the various methods described herein can be provided via storage devices (e.g., RAM, ROM, physical storage media such as CDs or floppy disks), such that the user terminal and / or base station can obtain the various methods when the storage device is coupled to or provided to the device. Furthermore, any other suitable techniques for providing the methods and techniques described herein to the device can be utilized.

[0104] It should be understood that the claims are not limited to the precise configuration and components described above. Various modifications, alterations, and variations may be made to the arrangement, operation, and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication by a user equipment (UE), comprising: Receive resource configuration indicating time-frequency cross-link interference CLI measurement resources, which are used for physical layer measurements of CLI caused by uplink transmissions by one or more other UEs during the downlink time slot of the UE; Receive a report configuration for a time resource indicating the timing of a report, the timing of which is used for physical layer reporting by the CLI; Based on the measurements performed at the measurement time according to the resource configuration, at least one CLI metric is measured; as well as According to the reporting configuration, the at least one CLI metric is reported at a reporting timing, wherein the reporting timing occurs at a first minimum timing interval after the most recent measurement resource available for measuring the reported CLI metric, wherein the first minimum timing interval depends at least in part on the type of the reported CLI metric.

2. The method as described in claim 1, wherein, The resource configuration also indicates parameters for generating a reference signal sequence and for mapping the sequence to the configured time-frequency resources.

3. The method of claim 1, wherein: The resource configuration indicates that the CLI measures the type of resource as periodic, semi-persistent, or aperiodic; and The report configuration indicates whether the CLI measurement report type is periodic, semi-persistent, or non-periodic.

4. The method of claim 1, further comprising: Based on the association between the resource configuration and the report configuration, the timing for reporting the measured CLI metrics is determined.

5. The method of claim 4, wherein, The association is indicated by the following: The resource configuration ID of the configuration resource provided in the report configuration; or The report configuration ID provided in the resource configuration.

6. The method of claim 4, wherein: If the CLI measurement resource is of a periodic type, the allowed types of associated CLI reports include periodic, semi-persistent, or non-periodic types. If the CLI measurement resource is semi-persistent, then the permitted types of the associated CLI report include either semi-persistent or non-periodic types; and If the CLI measurement resource is non-periodic, then the allowed types of associated CLI reports include non-periodic types.

7. The method of claim 1, wherein, The first minimum timing interval for the Received Signal Strength Indicator (RSSI) CLI type is less than the first minimum timing interval for the Reference Received Power (RSRP) CLI type.

8. The method of claim 1, wherein, If both the CLI measurement resource type and the CLI measurement report type are aperiodic, the reporting timing occurs at the second minimum timing interval after the physical downlink control channel (PDCCH) that triggers the CLI measurement resource.

9. The method of claim 8, wherein, The second minimum timing interval depends at least in part on the type of CLI metric reported.

10. The method of claim 9, wherein, The second minimum timing interval for the received signal strength indicator of type RSSICLI is less than the second minimum timing interval for the reference signal received power of type RSRP CLI.

11. The method of claim 1, wherein: When the CLI measurement resource type is not aperiodic, the configuration indicates whether time-domain measurement restrictions are configured for CLI measurements; When restrictions are configured, the UE is allowed to use only the most recent transmission opportunity of the measurement resources prior to the first minimum timing interval; as well as When no restrictions are configured, the UE is allowed to use not only the most recent transmission timing of the measurement resources prior to the first minimum timing interval.

12. A method for wireless communication by a network entity, comprising: The system sends a signal to the user equipment (UE) to notify the resource configuration of the time-frequency cross-link interference CLI measurement resources, which are used for physical layer measurements of CLI caused by uplink transmissions performed by one or more other UEs during the downlink time slot of the UE. The UE is notified of the reporting configuration of the time resources indicating the timing of the report, which is used for physical layer reporting by CLI; as well as The UE receives a report of at least one CLI metric, the at least one CLI metric being based on a measurement performed at a measurement timing according to the resource configuration, wherein the report is received at a reporting timing according to the report configuration, wherein the reporting timing occurs after a first minimum timing interval following the most recent measurement resource available for measuring the reported CLI metric, wherein the first minimum timing interval depends at least in part on the type of the reported CLI metric.

13. The method of claim 12, wherein, The resource configuration also indicates parameters for generating a reference signal sequence and for mapping the sequence to the configured time-frequency resources.

14. The method of claim 12, wherein: The resource configuration indicates that the CLI measures the type of resource as periodic, semi-persistent, or aperiodic; and The report configuration indicates whether the CLI measurement report type is periodic, semi-persistent, or non-periodic.

15. The method of claim 12, further comprising: Based on the association between the resource configuration and the report configuration, the timing for receiving reports of the measured CLI metrics is determined.

16. The method of claim 15, wherein, The association is indicated by the following: The resource configuration ID of the configuration resource provided in the report configuration; or The report configuration ID provided in the resource configuration.

17. The method of claim 15, wherein: If the CLI measurement resource is of a periodic type, the allowed types of associated CLI reports include periodic, semi-persistent, or non-periodic types. If the CLI measurement resource is semi-persistent, then the permitted types of the associated CLI report include either semi-persistent or non-periodic types; and If the CLI measurement resource is non-periodic, then the allowed types of associated CLI reports include non-periodic types.

18. The method of claim 12, wherein, The first minimum timing interval for the received signal strength indicator of type RSSICLI is less than the first minimum timing interval for the reference signal received power of type RSRP CLI.

19. The method of claim 12, wherein, If both the CLI measurement resource type and the CLI measurement report type are aperiodic, the reporting timing occurs at the second minimum timing interval after the physical downlink control channel (PDCCH) that triggers the CLI measurement resource.

20. The method of claim 19, wherein, The second minimum timing interval depends at least in part on the type of CLI metric reported.

21. The method of claim 20, wherein, The second minimum timing interval for the received signal strength indicator of type RSSICLI is less than the second minimum timing interval for the reference signal received power of type RSRP CLI.

22. The method of claim 12, wherein: When the CLI measurement resource type is not aperiodic, the configuration indicates whether time-domain measurement restrictions are configured for CLI measurements; When restrictions are configured, the UE is allowed to use only the most recent transmission opportunity of the measurement resources prior to the first minimum timing interval; as well as When no restrictions are configured, the UE is allowed to use not only the most recent transmission timing of the measurement resources prior to the first minimum timing interval.

23. An apparatus for wireless communication by a user equipment (UE), comprising: A component for receiving a resource configuration indicating time-frequency cross-link interference CLI measurement resources, the time-frequency cross-link interference CLI measurement resources being used for physical layer measurements of CLI caused by uplink transmissions made by one or more other UEs during the downlink time slot of the UE; A component for receiving a report configuration of a time resource indicating the timing of a report, the timing of which is used for physical layer reporting in the CLI; A component for measuring at least one CLI metric based on measurements performed at a measurement time according to the resource configuration; as well as A component for reporting the at least one CLI metric at a reporting timing according to the reporting configuration, wherein the reporting timing occurs after a first minimum timing interval following the most recent measurement resource available for measuring the reported CLI metric, wherein the first minimum timing interval depends at least in part on the type of the reported CLI metric.

24. An apparatus for wireless communication by a network entity, comprising: A component for signaling to a user equipment (UE) to indicate the resource configuration of time-frequency cross-link interference CLI measurement resources, which are used for physical layer measurements of CLI caused by uplink transmissions by one or more other UEs during the downlink time slot of the UE. A component for signaling the UE to the reporting configuration of time resources indicating the timing of a report, the reporting timing being used for physical layer reporting by CLI; as well as A component for receiving a report of at least one CLI metric from the UE, the at least one CLI metric being based on a measurement performed at a measurement timing according to the resource configuration, wherein the report is received at a reporting timing according to the reporting configuration, wherein the reporting timing occurs after a first minimum timing interval following the most recent measurement resource available for measuring the reported CLI metric, wherein the first minimum timing interval depends at least in part on the type of the reported CLI metric.

25. An apparatus for wireless communication by a user equipment (UE), comprising: At least one processor is configured to cause the UE to: Receive resource configuration of indication time-frequency cross-link interference CLI measurement resources, the CLI measurement resources being used for physical layer measurements of CLI caused by uplink transmissions by one or more other UEs during the downlink time slot of the UE; Receive a report configuration for a time resource indicating the timing of a report, the timing of which is used for physical layer reporting by the CLI; Based on the measurements performed at the measurement time according to the resource configuration, at least one CLI metric is measured; as well as The report of the at least one CLI metric is sent at a reporting timing according to the reporting configuration, wherein the reporting timing occurs at a first minimum timing interval after the most recent measurement resource available for measuring the reported CLI metric, wherein the first minimum timing interval depends at least in part on the type of the reported CLI metric.

26. An apparatus for wireless communication by a network entity, comprising: At least one processor is configured to cause the network entity to: The system sends a signal to the user equipment (UE) to notify the resource configuration of the time-frequency cross-link interference CLI measurement resources, which are used for physical layer measurements of CLI caused by uplink transmissions performed by one or more other UEs during the downlink time slot of the UE. The UE is notified of the reporting configuration of the time resources indicating the timing of the report, which is used for physical layer reporting by CLI; as well as The UE receives a report of at least one CLI metric, the at least one CLI metric being based on a measurement performed at a measurement timing according to the resource configuration, wherein the report is received at a reporting timing according to the report configuration, wherein the reporting timing occurs after a first minimum timing interval following the most recent measurement resource available for measuring the reported CLI metric, wherein the first minimum timing interval depends at least in part on the type of the reported CLI metric.

Images