Prioritization and timing for cross-link interference reporting
By reporting channel status to network entities based on CSI and CLI measurements in a wireless communication system, optimizing the generation and transmission of CLI reports, solving the problem of low CLI processing efficiency in the prior art, and improving the system throughput and reliability.
Patent Information
- Application Number
- CN202380035851.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-29
- Filing Date
- 2023-04-11
- Publication Date
- 2024-12-03
AI Technical Summary
When existing wireless communication systems deal with cross-link interference (CLI), it is difficult to efficiently perform CLI measurements and reports, resulting in frequent transmission failures and retransmissions, reducing throughput and increasing overhead.
User equipment (UE) reports channel status feedback to network entities based on channel status information (CSI) and CLI measurements, including CLI measurements, and conducts reporting configurations based on priority and time resources of CLI measurements to optimize the generation and generation of CLI reports and send.
Through efficient CLI measurement and reporting mechanisms, CLI is reduced, throughput and efficiency of communication systems is improved, overhead is reduced, and communication reliability is improved.
Smart Images

Figure CN119072947A_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims priority to U.S. patent application No. 17 / 733,835, entitled “PRIORITIZATION AND TIMING FOR CROSS-LINK INTERFERENCE REPORTING,” filed by Ibrahim et al. on April 29, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field
[0003] The following relates to wireless communications, including prioritization and timing for cross-link interference (CLI) reporting. Background Art
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).
[0005] A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as user equipment (UE). As the number of UEs in a wireless communication system increases, the number of connections and signaling in the wireless communication system may increase, and interference between UEs may increase. For example, communication between a UE and a network entity may interfere with communication between another UE and the network entity, or communication between a UE and a network entity may interfere with communication between another UE and another network entity. Improved techniques for minimizing interference in a wireless communication system may be desirable. Summary of the invention
[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting cross-link interference (CLI) reporting. In general, the described technology provides techniques for generating and reporting CLI to facilitate minimizing CLI at a network entity or user equipment (UE). In one aspect, a UE may report a channel state feedback (CSF) to a network entity based on a channel state information (CSI) measurement and a CLI measurement. In another aspect, a UE may explicitly report a CLI measurement to a network entity. The report of the CLI measurement may include a first set of fields and a second set of fields, the first set of fields including an indicator for the CLI measurement, and the second set of fields including a CLI measurement value. In yet another aspect, a UE may report a signal to interference plus noise ratio (SINR) to a network entity based on the CLI measurement, and the network entity may trigger the UE to perform additional CLI measurements on signals received from other UEs based on the SINR. In yet another aspect, a UE may generate the report using a CLI measurement based on whether the UE is allocated sufficient time to generate and send the report. For example, the content of the CLI report may differ based on whether the UE is allocated sufficient time to generate and send the report. In yet another aspect, the UE may identify an appropriate priority for reporting the CLI to the network entity.
[0007] A method for wireless communication at a user equipment (UE) is described. The method may include: reporting to a network entity a capability of the UE corresponding to a first duration for report generation at the UE; receiving signaling indicating a reporting configuration including a first set of resources for cross-link interference measurements; determining, based on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in the reporting configuration for reporting cross-link measurements; and sending a report based on the determination.
[0008] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: report to a network entity a capability of the UE corresponding to a first duration for report generation at the UE; receive signaling indicating a reporting configuration including a first set of resources for cross-link interference measurements; determine, based on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in the reporting configuration for reporting cross-link measurements; and send a report based on the determination.
[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for reporting to a network entity a capability of the UE corresponding to a first duration for report generation at the UE; means for receiving signaling indicating a reporting configuration including a first set of resources for cross-link interference measurements; means for determining, based on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in the reporting configuration for reporting cross-link measurements; and means for sending a report based on the determination.
[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: report to a network entity a capability of the UE corresponding to a first duration for report generation at the UE; receive signaling indicating a reporting configuration including a first set of resources for cross-link interference measurement; determine, based on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in the reporting configuration for reporting cross-link measurement; and send a report based on the determination.
[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the first duration may be less than or equal to the second duration, the method also comprising generating a report based on performing cross-link interference measurements on the first set of resources.
[0012] Some examples of methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the first duration may be greater than the second duration. The method may also include generating a report based on previous cross-link interference measurements, dummy values, null values, or combinations thereof.
[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying, based on time resources allocated for sending reports to a network entity, a reference time resource corresponding to an end of a time window within which cross-link interference measurements are to be performed.
[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the time difference between the reference time resource and the time resource allocated for sending the report can be the same value or a smaller value for the cross-link interference report than for the channel state information report.
[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a reporting configuration includes a second set of resources for channel state information channel measurements, and the methods, apparatus, and non-transitory computer-readable media may include additional operations, features, components, or instructions for: generating channel state feedback based on cross-link interference measurements performed on the first set of resources and channel state information channel measurements performed on the second set of resources, wherein sending the report includes sending the channel state feedback in the report.
[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first set of resources used for cross-link interference measurements may be offset in time from a second set of resources used for channel state information channel measurements within a threshold.
[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that a second duration allocated in a reporting configuration for reporting to a network entity corresponds to a time between a time resource allocated for sending a report and a latest time resource allocated for a cross-link interference measurement or a channel state information channel measurement.
[0018] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, the first duration for report generation may be for cross-link interference measurement, and the method, apparatus, and non-transitory computer-readable medium may include additional operations, features, components, or instructions for: identifying a third duration for report generation for channel state information channel measurement. The method may also include determining that the first duration and the third duration may both be less than or equal to a second duration allocated in a reporting configuration for reporting to a network entity, wherein sending the channel state feedback in the report may be based on the determination.
[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the latency class corresponds to a latency class used for beam reporting by a UE.
[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the latency class may be based on capabilities of the UE, a subcarrier spacing of a bandwidth portion used for communicating with a network entity, or a combination thereof.
[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the latency class can be low latency or high latency and can be based on the amount of cross-link interference measurements to be reported, the amount of frequency bands associated with the cross-link interference measurements to be reported, the amount of resources used for the cross-link interference measurements to be reported, or a combination thereof.
[0022] A method for wireless communication at a UE is described. The method may include: receiving signaling from a network entity indicating a cross-link interference reporting configuration including a resource set for cross-link interference measurement; generating a first report based on performing cross-link interference measurement on the resource set; and sending the first report or a second report to the network entity in a time resource based on comparing a first priority of the first report with a second priority of the second report.
[0023] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive signaling from a network entity indicating a cross-link interference report configuration including a resource set for cross-link interference measurement; generate a first report based on performing cross-link interference measurement on the resource set; and send the first report or the second report to the network entity in a time resource based on comparing a first priority of the first report with a second priority of the second report.
[0024] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving signaling from a network entity indicating a cross-link interference reporting configuration including a resource set for cross-link interference measurement; means for generating a first report based on performing cross-link interference measurement on the resource set; and means for sending the first report or the second report to the network entity in a time resource based on comparing a first priority of the first report with a second priority of the second report.
[0025] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive signaling from a network entity indicating a cross-link interference reporting configuration including a resource set for cross-link interference measurement; generate a first report based on performing cross-link interference measurement on the resource set; and send the first report or the second report to the network entity in a time resource based on comparing a first priority of the first report with a second priority of the second report.
[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first priority of the first report may be the same as the priority of a channel state information report without a reference signal received power measurement or a signal to interference plus noise ratio measurement.
[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first priority of the first report may be lower than the priority of the channel state information report.
[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first priority of the first report may be configurable, and the methods, apparatus, and non-transitory computer-readable media may also include additional operations, features, components, or instructions for: receiving a control message indicating the first priority of the first report from a network entity. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Figure 1 An example of a wireless communication system supporting prioritization and timing for CLI reporting in accordance with one or more aspects of the present disclosure is illustrated.
[0030] Figure 2 Examples of different types of full-duplex operations in accordance with one or more aspects of the present disclosure are illustrated.
[0031] Figure 3 An example of full-duplex operation at a first network entity according to one or more aspects of the present disclosure is illustrated.
[0032] Figure 4 An example of full-duplex operation at a first network entity and a first user equipment (UE) according to one or more aspects of the present disclosure is illustrated.
[0033] Figure 5 An example of full-duplex operation at a first UE according to one or more aspects of the present disclosure is illustrated.
[0034] Figure 6 Examples of channel state information (CSI) reporting configurations in accordance with one or more aspects of the present disclosure are illustrated.
[0035] Figure 7 An example of a CSI interference measurement (CSI-IM) configuration according to one or more aspects of the present disclosure is illustrated.
[0036] Figure 8 Examples of timing for CSI reporting in accordance with one or more aspects of the present disclosure are illustrated.
[0037] Fig. 9 Examples of interference from other network entities on communications at a UE and interference from another UE on communications at the UE according to one or more aspects of the present disclosure are illustrated.
[0038] Fig.10 An example of inter-cell interference at a UE including interference at a UE in one cell from another UE in another cell according to one or more aspects of the present disclosure is illustrated.
[0039] Fig.11An example of intra-cell CLI in sub-band full duplex (SBFD) or in-band full duplex (IBFD) according to one or more aspects of the present disclosure is illustrated.
[0040] Fig.12 An example of a SBFD timeslot format according to one or more aspects of the present disclosure is illustrated.
[0041] Fig.13 An example of a sounding reference signal (SRS) configuration according to one or more aspects of the present disclosure is illustrated.
[0042] Fig.14 An example of a wireless communication system supporting CLI report configuration and payload design according to one or more aspects of the present disclosure is illustrated.
[0043] Fig.15 An example of a CLI report configuration in accordance with one or more aspects of the present disclosure is illustrated.
[0044] Fig.16 An example of a CLI from an unknown aggressor in accordance with one or more aspects of the present disclosure is illustrated.
[0045] Fig.17 An example of a process flow supporting CLI report configuration and payload design in accordance with one or more aspects of the present disclosure is illustrated.
[0046] Fig.18 and Fig.19 A block diagram of a device supporting prioritization and timing for CLI reporting in accordance with one or more aspects of the present disclosure is shown.
[0047] Fig. 20 A block diagram of a communications manager supporting prioritization and timing for CLI reporting is shown in accordance with one or more aspects of the present disclosure.
[0048] Fig.21 A diagram of a system including a device supporting prioritization and timing for CLI reporting is shown in accordance with one or more aspects of the present disclosure.
[0049] Fig. 22 and Fig.23 A flow chart illustrating a method of supporting prioritization and timing for CLI reporting in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION
[0050] As the number of user equipment (UE) in a wireless communication system increases, the number of connections and signaling in the wireless communication system may increase, and interference between UEs may increase. Interference across links or across connections in a wireless communication system may be referred to as cross-link interference (CLI), and high CLI may result in frequent failed transmissions or excessive retransmissions (e.g., which may reduce throughput and increase overhead). Therefore, it may be appropriate for a wireless communication system to support techniques for minimizing CLI to improve throughput and reduce overhead. In order to minimize CLI, some wireless communication systems may support techniques for configuring or scheduling communications with a UE based on CLI measurements captured at the UE. However, in some aspects, techniques for generating and reporting CLI measurements may be underdeveloped, and it may be challenging for a wireless communication system to minimize CLI without CLI measurements or without certain information related to CLI measurements.
[0051] The techniques described herein are provided for efficiently performing CLI measurements and reporting based on CLI measurements to facilitate techniques for minimizing CLI at a network entity or UE. In one aspect, a UE may report a channel state feedback (CSF) to a network entity based on a channel state information (CSI) measurement and a CLI measurement. In another aspect, a UE may explicitly report a CLI measurement to a network entity. The report of the CLI measurement may include a first set of fields and a second set of fields, the first set of fields including an indicator for the CLI measurement, and the second set of fields including a CLI measurement value. In yet another aspect, a UE may report a signal to interference plus noise ratio (SINR) to a network entity based on the CLI measurement, and the network entity may trigger the UE to perform additional CLI measurements on signals received from other UEs based on the SINR. In yet another aspect, a UE may generate the report using CLI measurements based on whether the UE is allocated sufficient time to generate and send the report. For example, the content of the CLI report may be different based on whether the UE is allocated sufficient time to generate and send the report relative to a measurement opportunity. In yet another aspect, a UE may identify an appropriate priority for reporting CLI to a network entity.
[0052] Various aspects of the disclosure are first described in the context of a wireless communication system. Examples of processes and signaling exchanges that support prioritization and timing for CLI reports are then described. Various aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to prioritization and timing for CLI reports.
[0053] Figure 1An example of a wireless communication system 100 supporting prioritization and timing for CLI reporting according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).
[0054] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In different examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).
[0055] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be capable of communicating with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.
[0056] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.
[0057] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). In some examples, the network entities 105 may communicate with each other over the backhaul communication links 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .
[0058] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).
[0059] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0060] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.
[0061] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a collection of independent antennas for relaying communications with the UE 115, or may share the same antenna of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.
[0062] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support CLI report configuration and payload design as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).
[0063] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.
[0064] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 as shown in .
[0065] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).
[0066] In some examples (such as in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by UE 115. A carrier may operate in a stand-alone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-stand-alone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).
[0067] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115 (e.g., physical downlink control channel (PDCCH) transmissions, physical downlink shared channel (PDSCH) transmissions, channel state information (CSI) reference signal (CSI-RS) transmissions), uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105 (e.g., physical uplink control channel (PUCCH) transmissions, physical uplink shared channel (PUSCH) transmissions, or sounding reference signal (SRS) transmissions), or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).
[0068] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications over a particular carrier bandwidth or may be configurable to support communications over one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.
[0069] The signal waveform transmitted over the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.
[0070] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.
[0071] The time interval of the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).
[0072] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro-time slots including one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.
[0073] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a certain amount of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).
[0074] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .
[0075] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.
[0076] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
[0077] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.
[0078] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.
[0079] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may be unable or not configured to receive transmissions from the network entity 105 for other reasons. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .
[0080] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.
[0081] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be transported by user plane entities, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0082] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is about one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmission using lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
[0083] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may have even greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.
[0084] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as network entities 105 and UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands can be based on a carrier aggregation configuration (e.g., LAA) combined with component carriers operating in licensed bands. Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.
[0085] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.
[0086] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).
[0087] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer layer or the PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly for transmission on a logical channel. The MAC layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between a UE 115 and a network entity 105 or a core network 130. At the PHY layer, a transport channel may be mapped to a physical channel.
[0088] Some UEs 115 or network entities 105 in the wireless communication system 100 may be configured to adopt an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the network entity 105 or UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some network entities 105 or UE 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.
[0089] As a supplement or alternative to half-duplex mode, some network entities 105 or UE 115 may support full-duplex mode. Full-duplex mode may refer to a mode that supports bidirectional communication via simultaneous transmission and reception (e.g., in the same or overlapping frequency range). This bidirectional communication may be referred to as full-duplex communication. Full-duplex communication is a technology that can theoretically double the link capacity by enabling a radio network node to transmit and receive simultaneously on the same frequency and time resources. Full-duplex breaks the half-duplex operation constraints in which transmission and reception are different in time or frequency. Full-duplex network nodes, such as network entities 105, UE 115, or both in a cellular network, can use the same radio resources to communicate with two half-duplex panels simultaneously in uplink and downlink. For example, UE 115 can send uplink transmission from a panel at UE 115, and UE 115 can receive downlink transmission at another panel at UE 115. Similarly, the network entity 105 may receive uplink transmissions at one panel at the network entity 105 , and the network entity 105 may send downlink transmissions from another panel at the network entity 105 .
[0090] Thus, a device equipped with multiple TRPs that support the ability to transmit and receive simultaneously using the same time-frequency radio resources (e.g., different associated aspects of uplink or downlink transmissions and processes in frequency range 2 (FR2)) may be referred to as a full-duplex capable device (e.g., a full-duplex UE 115 or a full-duplex network entity 105). The device may also be capable of operating in full-duplex mode and retreating to half-duplex mode. In some cases, full-duplex capability may be conditioned on beam separation and other factors (e.g., self-interference between downlink and uplink and clutter echoes at the device). However, full-duplex communications may provide latency reduction (e.g., because it is possible to receive downlink signals in uplink-only time slots, which may achieve latency savings), spectral efficiency enhancement (e.g., per cell or per UE 115), more efficient resource utilization, and coverage enhancement with continuous uplink or downlink transmission or repetition.
[0091] Figure 2Examples of different types of full-duplex operations 200 according to one or more aspects of the present disclosure are illustrated. The first type of full-duplex operation 200-a may be referred to as in-band full-duplex (IBFD) operation. When the first type of full-duplex operation 200-a is supported, the UE 115 or network device 105 may transmit and receive on the same time and frequency resources. For example, the downlink and uplink may share the same IBFD time or frequency source (e.g., with full or partial overlap between the downlink and uplink). The second type of full-duplex operation 200-b may be referred to as sub-band frequency division duplex (FDD) operation, sub-band full-duplex (SBFD), or flexible duplex operation. When the second type of full-duplex operation 200-b is supported, the UE 115 or network device 105 may transmit and receive at the same time but on different frequency resources. In some cases, downlink resources may be separated from uplink resources in the frequency domain (e.g., by a guard band).
[0092] Figure 3 An example of full-duplex operation 300 at a first network entity 105 in accordance with one or more aspects of the present disclosure is illustrated. The first network entity 105 may receive uplink transmissions from a first UE 115 and send downlink transmissions to a second UE. The second UE 115 may experience CLI from the uplink transmissions from the first UE 115, and the first network entity 105 may experience CLI from the second network entity 105. The first network entity 105 may also experience self-interference from full-duplex operation because the first network entity 105 may simultaneously receive uplink transmissions from the first UE 115 and send downlink transmissions to the second UE. Communications between the first network entity 105 and the first UE 115 and the second UE 115 may be conducted on non-overlapping uplink and downlink subbands (e.g., SBFD).
[0093] Figure 4An example of full-duplex operation 400 at a first network entity 105 and a first UE 115 in accordance with one or more aspects of the present disclosure is illustrated. The first network entity 105 may communicate with the first UE 115 and the second UE 115 with partially overlapping uplink and downlink transmissions. The second UE 115 may experience CLI from uplink transmissions from the first UE 115, and the first network entity 105 may experience CLI from the second network entity 105. The first network entity 105 may also experience self-interference from the full-duplex operation because the first network entity 105 may simultaneously receive uplink transmissions from the first UE 115 and send downlink transmissions to the second UE 115. The first UE 115 may also experience self-interference from the full-duplex operation because the first UE 115 may simultaneously receive downlink transmissions from the first network entity 105 and send uplink transmissions to the first network entity 105.
[0094] Figure 5 An example of full-duplex operation 500 at a first UE 115 in accordance with one or more aspects of the present disclosure is illustrated. The first UE 115 may be a SBFD UE 115 and may communicate with multiple transmit and receive points (TRPs) with fully overlapping uplink and downlink transmissions. The second UE 115 may experience CLI from uplink transmissions from the first UE 115, and the second network entity 105 may experience CLI from downlink transmissions from the first network entity 105. The first UE 115 may experience self-interference from full-duplex operation because the first UE 115 may simultaneously receive downlink transmissions from the first network entity 105 and send uplink transmissions to the second network entity 105.
[0095] In wireless communication system 100 , to minimize CLI from network entity 105 to communication at UE 115 , UE 115 may perform channel state information (CSI) measurements on a CSI reference signal (CSI-RS) received from network entity 105 .
[0096] Figure 6An example of a CLI report configuration 600 according to one or more aspects of the present disclosure is illustrated. The CSI report configuration 600 may include a non-zero power (NZP) CSI-RS resource configuration for channel measurement (e.g., on a channel measurement resource (CMR)). The NZP CSI-RS resource configuration for channel measurement may indicate at least one resource set (e.g., an NZP CMR resource set), and the resource set may include resources on which the UE 115 may perform CMR. The CSI report configuration 600 may also include a zero power (ZP) CSI-RS resource configuration for interference measurement (IM) (e.g., on an IM resource (IMR)). The ZP CSI-RS resource configuration for CSI-IM may indicate at least one resource set, and the resource set may include resources for the UE 115 to perform CSI-IM. The CSI report configuration 600 may also include a NZP CSI-RS resource configuration for IM. The NZP CSI-RS resource configuration for CSI-IM may indicate at least one resource set, and the resource set may include resources for performing CSI-IM for UE 115. CSI reporting configuration 600 may also include a codebook configuration indicating measurements for UE 115 to report (e.g., channel quality indicator (CQI), rank indicator (RI), etc.), and CSI reporting configuration 600 may include a reporting configuration type indicating whether UE 115 is to report CSI periodically, semi-persistently, or aperiodically.
[0097] Figure 7 An example of a CSI-IM configuration 700 according to one or more aspects of the present disclosure is illustrated. CSI-IM resources may be configured for interference measurement to achieve the purpose of accurate CSI reporting reflecting inter-cell interference. Multiple modes for CSI-IM resources may be supported. A first mode (e.g., mode 0) may consist of two consecutive resource elements in two consecutive symbols. A second mode (e.g., mode 1) may consist of four consecutive resource elements in one symbol. The size of the CSI-IM resource in the frequency may be configured based on the starting resource block and the number of resource blocks. The CSI report configuration may include a CSI-IM resource set for interference measurement. The configured resources may be used by UE 115 to measure interference.
[0098] As described, the UE 115 in the wireless communication system 100 may also be configured with resources for channel measurement. The UE 115 may receive a CSI-RS from a network entity 105 (e.g., connected to the UE 115), and the UE 115 may perform channel measurement on the CSI-RS. In some cases, the UE 115 may be configured to report a reference signal received power (RSRP) measurement of the CSI-RS. For RSRP reporting, the UE 115 may report the number of reference signals reported (e.g., 1, 2, 3, or 4 according to a higher layer configuration) and different CSI-RS resource indicators (CRIs) or synchronization signal block (SSB) resource indicators (SSBRIs) for each reporting setting. The wireless communication system 100 (e.g., an NR system) may classify CSI report settings into wideband and subband frequency granularity. Beam reporting may be classified as wideband frequency granularity CSI.
[0099] In some cases, whether for reporting channel measurements, interference measurements, or both, UE 115 may be configured with appropriate resources for reporting CSI. In particular, the resources configured for reporting CSI may provide UE 115 with sufficient time to perform CSI measurements, generate CSI reports, and send CSI reports. In some examples, the resources for reporting CSI may be determined based on CSI reference resources. For example, assuming a hypothetical PDSCH transmission scheduled in a CSI reference resource, some CSI parameters (e.g., CQI) may be calculated. The CSI reference resource may define a set of attributes (e.g., reference signal overhead, bandwidth, precoding, etc.) of the hypothetical PDSCH transmission. The CSI reference resource may define a downlink time slot as a timing reference for determining the end of a measurement window (e.g., in which a CSI measurement is to be performed). After the CSI reference resource (e.g., reference time slot), no subsequent channel and interference measurements may be included in the CSI report.
[0100] In some examples, the CSI reference resources in the time domain of the CSI report in uplink time slot n' may be composed of a single downlink time slot nn CSI,ref Definition. For periodic and semi-persistent CSI reporting, if a single CSI-RS or SSB resource is configured for channel measurement, then nn CSI,ref Can be greater than or equal to The minimum value of nn such that the CSI reference resource corresponds to a valid downlink slot, where μ refers to the subcarrier spacing (SCS). In addition, for periodic and semi-persistent CSI reporting, if multiple CSI-RS or SSB resources are configured for channel measurement, then nn CSI,ref is greater than or equal to The minimum value of , such that the CSI reference resource corresponds to a valid downlink time slot. Once the UE 115 performs CSI measurements in the measurement window based on the CSI reference resource, the UE 115 may send a CSI report in an uplink control information (UCI) payload. The UCI may be transmitted on the PUCCH or PUSCH and may consist of one part or two parts depending on the amount and type of report (e.g., wideband versus subband reporting). The payload size of CSI Part 1 may be fixed (e.g., using zero padding), and the payload size of CSI Part 2 may be derived from the information in CSI Part 1.
[0101] Figure 8 An example of timing for CSI reporting 800 according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may specify timing requirements for CSI processing to ensure that the UE 115 has sufficient time to generate a CSI report. In some cases, the UE 115 may support ultra-low latency reporting for some special cases (e.g., defined in CSI calculation latency requirement 1). In other cases, there may be three latency classes (e.g., requirement 2): a low latency class (Z1), a high latency class (Z2), and a latency class for beam reporting (Z3). The Xi value used for CSI reporting may depend on the reporting UE capabilities. In addition, the latency class for CSI reporting may assign values to Z and Z', such as Figure 8 exemplified. The Z value may be an amount of symbols and may correspond to a time for processing control information in the PDCCH to determine a time to perform CSI measurements and a time to perform and report CSI measurements. The Z′ value may also be an amount of symbols and may correspond to a time to perform and report CSI measurements. Thus, the UE 115 may be configured with a duration greater than or equal to Z for processing control information, performing CSI measurements, and reporting CSI measurements, and the UE 115 may be configured with a duration greater than or equal to Z′ for performing CSI measurements and reporting CSI measurements.
[0102] In addition to minimizing CLI from the network entity 105 to communications at the UE 115, it may be appropriate to minimize CLI from other UEs 115 to communications at the UE 115. For example, it may be appropriate to support techniques for handling or managing inter-network entity and inter-UE CLI handling. If the UE 115 is operating in half-duplex mode and the network entity 105 is operating in SBFD or IBFD mode, one or more interference sources may be present at the UE 115. For example, the UE 115 may experience inter-cell interference from other network entities 105, intra-cell CLI interference from UEs 115 in the same cell, or inter-cell CLI from UEs in neighboring cells. In addition, a full-duplex UE 115 may experience self-interference.
[0103] Fig. 9 Examples of interference 900 from other network entities 105 on communications at a UE 115 and interference 900 from another UE 115 on communications at the UE 115 are illustrated in accordance with one or more aspects of the present disclosure.
[0104] Fig.10 An example of inter-cell interference 1000 at a UE 115 including interference at one UE 115 in one cell from another UE 115 in another cell is illustrated in accordance with one or more aspects of the present disclosure.
[0105] Fig.11 An example of intra-cell CLI 1100 in SBFD or IBFD according to one or more aspects of the present disclosure is illustrated. In SBFD, the network entity 105 may configure downlink transmissions to a UE 115 on frequency domain resources that are adjacent to frequency domain resources configured for uplink transmissions from another UE 115. In an example SBFD scenario, a first UE 115 may transmit an uplink transmission in the middle of a band, and a second UE 115 may receive a downlink transmission from the network entity 105 on adjacent frequency resources. The uplink transmission of the first UE 115 may cause CLI to the downlink reception at the second UE 115. The CLI may be caused by energy leakage due to timing and frequency misalignment between the first UE 115 and the second UE 115 or by automatic gain control (AGC) mismatch (e.g., if the AGC at the second UE 115 is driven by the downlink serving cell signal of the second UE 115 but the CLI from the first UE 115 is strong enough to saturate the AGC at the second UE 115).
[0106] Fig.12 An example of an SBFD slot format 1200 according to one or more aspects of the present disclosure is illustrated. The SBFD slot format may be defined as a "D+U" slot, which may be a slot in which a band is used for both uplink and downlink transmissions. Downlink and uplink transmissions may occur in overlapping bands (e.g., IBFD) or adjacent bands (e.g., SBFD). In a given "D+U" symbol, a half-duplex UE 115 may transmit in the uplink band or receive in the downlink band. In a given "D+U" symbol, a full-duplex UE 115 may transmit in the uplink band and / or receive in the downlink band in the same slot. A "D+U" slot may contain only downlink symbols, only uplink symbols, or full-duplex symbols.
[0107] The wireless communication system 100 may support techniques for mitigating or minimizing inter-UE CLI. The first UE 115 may be configured to receive SRS from the second UE 115, and the first UE 115 may report CLI measurements performed on these SRS to the network entity. The SRS may refer to an uplink reference signal sent by the second UE 115.
[0108] Fig.13 An example of an SRS configuration 1300 according to one or more aspects of the present disclosure is illustrated. The SRS configuration may indicate the mapping of the SRS to the physical resources in the resource block. In time, in some examples, the SRS resource may span up to four symbols and may be configured in the last six symbols of the time slot. In other examples, the SRS may span one or more symbols and may be configured in different symbols in the time slot. In frequency, the SRS may be transmitted in a comb mode (e.g., a comb-2SRS mode including an SRS mapped to every other subcarrier, and a comb-4SRS mode including an SRS mapped to every fourth subcarrier) and may be configured with a comb offset. The SRS configuration may also indicate the time and frequency configuration for the SRS. The time and frequency configuration may indicate whether the second UE 115 is to send a periodic, aperiodic or semi-persistent SRS. The time and frequency configuration may also indicate the periodicity and slot offset, the sounding bandwidth in the BWP, and the frequency hopping mode for SRS transmission.
[0109] Techniques described herein are provided for efficiently performing CLI measurements and reporting based on the CLI measurements to facilitate techniques for minimizing CLI at a network entity 105 or a UE 115. In one aspect, the UE 115 may report a CSF to the network entity 105 based on the CSI measurement and the CLI measurement. In another aspect, the UE 115 may explicitly report the CLI measurement to the network entity 105. The report of the CLI measurement may include a first set of fields and a second set of fields, the first set of fields including an indicator for the CLI measurement, the second set of fields including the CLI measurement value. In yet another aspect, the UE 115 may report an SINR to the network entity 105 based on the CLI measurement, and the network entity 105 may trigger the UE 115 to perform additional CLI measurements on signals received from other UEs based on the SINR. In yet another aspect, the UE 115 may generate the report using the CLI measurement based on whether the UE 115 is allocated sufficient time to generate and send the report. For example, the content of the CLI report may vary based on whether the UE 115 is allocated sufficient time to generate and send the report. In yet another aspect, the UE 115 may identify an appropriate priority for reporting the CLI to the network entity 105.
[0110] Fig.14An example of a wireless communication system 1400 that supports prioritization and timing for CLI reporting in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 1400 includes a network entity 105-a, which can be an example of a network entity 105 in accordance with aspects of the present disclosure. The wireless communication system 1400 also includes a UE 115-a and a UE 115-b, which can be examples of a UE 115 in accordance with aspects of the present disclosure. The wireless communication system 1400 can implement aspects of the wireless communication system 100. For example, the wireless communication system 1400 can support efficient techniques for performing and reporting CLI measurements to minimize CLI (e.g., inter-UE CLI measurements and mitigation).
[0111] UE 115-a may report CLI on PUSCH or PUCCH (e.g., in a layer one (L1) CLI framework). In one aspect, described techniques are provided for supporting different options for CLI reporting configuration, characteristics of CLI reporting payloads, and use of CLI-SINR to determine contributions of known and unknown CLI sources. Different options for CLI reporting configuration may treat CLI reporting as a special case of CSI reporting, reporting explicit CLI (e.g., received signal strength indicator (RSSI), RSRP, etc.), or reporting CSF based on CLI measurements (e.g., CSF taking CLI into account). In another aspect, described techniques are provided for establishing central processing unit (CPU) and timing requirements for CLI reporting, rules for defining reference resources for CLI reporting, and priority rules for CLI reporting.
[0112] exist Fig.14 , network entity 105-a may send a reporting configuration 1405 to UE 115-a, which configures UE 115-a to report CLI measurements to network entity 105-a or to report to network entity 105-a based on CLI measurements. Network entity 105-a may also send an SRS configuration 1410 to UE 115-b, which configures UE 115-b to send SRS 1415 to UE 115-a, and UE 115-b may send SRS 1415 to UE 115-a based on SRS configuration 1410. UE 115-a may receive SRS 1415, perform CLI measurements on SRS 1415, and send a CLI report 1420 to network entity 105-a based on the CLI measurements performed on SRS 1415. As mentioned, to capture the impact of CLI, the UE 115-a may be configured to report explicit CLI (e.g., explicit CLI measurements such as RSRP or CLI-RSSI) or a CSF based on CLI measurements.
[0113] Fig.15An example of a CLI report configuration 1500 in accordance with one or more aspects of the present disclosure is illustrated. A first CLI configuration 1500-a may be used to configure a UE 115-a to report an explicit CLI, and a second CLI configuration 1500-b may be used to configure a UE 115-a to report a CSF based on CLI measurements. Thus, a CLI report 1420 may be a report carrying an explicit CLI or may be a CSI report based on CLI measurements.
[0114] If UE 115-a is to report explicit CLI, the wireless communication system 1400 may define the CLI report payload, priority, CPU requirements, and timing requirements for the CLI report. Explicit CLI may be referred to as a special type of CSI report, and the report quantity field in the report configuration 1405 may indicate that UE 115-a is to report CLI measurements. For example, the report configuration 1405 may indicate that UE 115-a is to send a CSI report with CLI (e.g., CLI-RSRP, CLI-RSSI, CLI-SINR, etc.) based on the report quantity configured in the report configuration 1405. In some examples, the CLI report or CSI report with CLI may be similar to a CSI-based beam report (e.g., the same payload structure as the payload structure configured by the CRI-RSRP report quantity may be used). For example, UE 115-a may report up to a specified amount of CLI measurements (e.g., four), and the CLI measurements may correspond to different CLI measurement resources, subbands, or receive beams that are quasi-co-located with the beam used for CLI measurements.
[0115] In some cases, the CLI report may be associated with a threshold (e.g., maximum) amount of CLI measurements (e.g., four). In other cases, the CLI report may be associated with more than the threshold amount of CLI measurements, but the UE 115-a may report only a threshold amount of CLI measurements among the performed CLI measurements (e.g., report only four of the CLI measurements according to a preconfigured rule). For example, the UE 115-a may perform a CLI measurement set, and the UE 115-a may select up to a threshold amount of CLI measurements from the CLI measurement set to report. The UE 115-a may report up to a threshold amount of CLI measurements, including worst-case CLI measurements (e.g., reporting four worst-case (highest) CLI measurements). Additionally or alternatively, the UE 115-a may report up to a threshold amount of CLI measurements, including worst-case CLI measurements per subband for different beams used for CLI measurements (e.g., beams that are quasi-co-located with a beam indicated for CLI measurements).
[0116] Instead of including the CRI field in the CLI report, UE 115-a may indicate the CLI resource on which the CLI measurement (e.g., the CLI value) was performed, a subband indicator indicating which subband corresponds to the CLI measurement, or a quasi-co-site (QCL) indicator indicating which receive beam was used to perform the CLI measurement. For frequency range 1 (FR1), if the CLI measurement is based on a PUSCH based on an aggressor codebook (e.g., transmitted from a PUSCH of UE 115-b), UE 115-a (e.g., a victim UE 115) may try different combiners and may report the worst case CLI or report which transmit precoding matrix indicators (TPMIs) UE 115-b should avoid (e.g., in this case, UE 115-a may be able to identify which ports are being used at UE 115-b). Table 1 illustrates an example of a mapping order of CLI fields for one report for CLI reporting.
[0117] Table 1: Mapping order of CLI fields for a report for CLI reporting
[0118]
[0119] In Table 1, the first field set may correspond to or include one or more CLI resource indicators, subband indicators, QCL indicators, or TPMI limits, and the second field set may include CLI values (e.g., RSRP, RSSI, or SINR) for CLI measurements (e.g., four CLI measurements). For example, CLI resource indicator, subband indicator, or QCL indicator #1 may correspond to RSRP #1 (e.g., may indicate a CLI resource, subband, or beam associated with an RSRP measurement). In some cases, the CLI report 1420 may be configured to include CLI measurements that exceed a threshold amount (e.g., four). If the amount of CLI measurements performed by UE 115-a reaches a threshold amount, the CLI report 1420 may consist of one part. If the amount of CLI measurements performed by UE 115-a is greater than a threshold amount, the CLI report 1420 may consist of more than one part (e.g., two parts). For example, the remaining CLI measurements may be included in CLI part 2. CLI part 1 may have a fixed size, and CLI part 1 may include CLI measurements up to the fixed size, wherein the remaining CLI measurements are included in CLI part 2.
[0120] If UE 115-a is to report CSF based on CLI measurement, UE 115-a may be configured with NZP-CSI-RS for channel measurement and other CSI-RS for interference measurement. For example, UE 115-a may be configured with CSI-RS (e.g., CSI-IM) for interference measurement for inter-cell interference and CSI-RS or ZP-SRS (e.g., CSI-IM or ZP-SRS) for interference measurement for inter-UE interference or CLI. UE 115-a may also be configured with NZP-CSI-RS for measuring downlink spatial division multiplexing (DL-SDM) interference. After performing CSI interference measurement and CLI measurement, UE 115-a may report CSF considering the impact of CLI or CLI measurement. In such cases, CLI report 1420 may be a CSI report that may include a CSF payload and may be associated with the same priority, CPU requirement, or timing requirement associated with any CSI report (e.g., a CSI report independent of CLI measurement).
[0121] If UE 115-a is capable of reporting explicit CLI and reporting CSF based on CLI measurement, UE 115-a may determine whether to report explicit CLI or report CSF based on CLI measurement based on the CSI reporting amount (e.g., a flag or metric) included in the reporting configuration 1405. If UE 115-a or CLI report 1420 is configured with CLI measurement resources and the CSI reporting amount fails to indicate explicit CLI reporting (e.g., indicates CSI reporting amount), UE 115-a may report CSF based on CLI measurement. Additionally or alternatively, UE 115-a may determine whether to report explicit CLI or report CSF based on CLI measurement based on a dedicated CLI framework for explicit CLI reporting. For example, if UE 115-a receives the second CLI configuration 1500-b, UE 115-a may report explicit CLI. Otherwise, UE 115-a may report CSF based on CLI measurement.
[0122] In some aspects, the CLI framework in the wireless communication system 1400 may support RSSI-CLI and RSRP-CLI measurements. In some cases, it may be appropriate for UE 115-a to report CLI-SINR measurements to the network entity 105-a. The signal measured by UE 115-a may correspond to one or more NZP-CLI-SRS to be measured. The reference signal (e.g., CLI-SRS) sent by UE 115-b (e.g., an aggressor) may be known or distinguishable to UE 115-a, and UE 115-a may descramble the signal and measure the RSRP of these signals. However, interference at UE 115-a may also come from all other interfering signals, which may include uplink transmissions from unknown aggressors (e.g., intra-cell or inter-cell CLI) and / or interference from neighboring cells. Therefore, CLI-SINR can capture the ratio of known CLI to unknown interference plus noise. For example, UE 115-a may then use RSRP and the measured RSSI to determine CLI-SINR (e.g., subtract RSRP from RSSI).
[0123] In the wireless communication system 1400, the network entity 105-a may configure the UE 115-a (e.g., the victim UE 115) to measure and report CLI-SINR, where the CLI-SINR may be based on one or more CLI-SRS resources from one or more known aggressor UEs 115. The network entity 105-a may use the CLI-SINR report to calculate the impact of unknown interference at the UE 115-a. The network entity 105-a may then trigger additional CLI measurements from other potential in-cell aggressor UEs 115 at the UE 115-a (e.g., if the unknown interference at the UE 115-a is high or meets an interference threshold). In some examples, unknown interference at a cell edge UE 115 may indicate the presence of inter-cell CLI.
[0124] Fig.16An example of CLI 1600 from an unknown aggressor according to one or more aspects of the present disclosure is illustrated. UE 115-a may be configured to report CLI-SINR to identify different interference contributions (e.g., intra-cell CLI, inter-cell CLI, or interference from neighbor cells). Network entity 105-a may configure UE 115-a (e.g., victim UE 115) to measure CLI-SINR based on one or more CLI-SRS from known intra-cell aggressors. For example, UE 115-a may descramble all CLI-SRS and measure CLI-SINR to calculate the impact of residual interference. If network entity 105-a determines that the residual interference is high, network entity 105-a may trigger UE 115-c (e.g., unknown aggressor) to send SRS to UE 115-a. UE 115-a may then report the CLI from UE 115-b and the CLI from UE 115-c to network entity 105-a, and network entity 105-a may schedule communications at UE 115-a based on the CLI from UE 115-b and the CLI from UE 115-c.
[0125] In addition to generating an appropriate payload for the CLI report 1420 to allow the network entity 105-a to minimize CLI, the wireless communication system 1400 may also support appropriate CPU and timing requirements for CLI reporting and appropriate prioritization of CLI reporting. It can be assumed that the CLI report 1420 occupies a single CPU similar to the beam report (e.g., requiring a single processor to perform CLI measurements and generate the CLI report 1420). In addition, when the UE 115-a is configured to report CLI, the calculation delay for reporting CLI may be based on the latency class of the UE 115-a. In one example, the latency class for CLI reporting may be the same as the latency class for beam reporting and may depend on the reported capabilities of the UE 115-a (e.g., Z3 defined in CSI calculation delay requirement 2). In another example, the latency class for CLI reporting may be defined as a separate latency class (e.g., from beam reporting). In this example, the CLI latency class may be defined to depend on the reported capabilities of UE 115-a for CLI processing, or the CLI latency class may be defined as a fixed value that may vary with SCS(μ). In yet another example, the latency class for CLI reporting may be defined as a low latency class or a high latency class, and may depend on the amount of CLI measurements to be reported, wideband versus subband CLI reporting, or whether the CLI report 1420 is based on a single CLI resource or multiple CLI resources. In any of the examples, UE 115-a may be configured to perform CLI measurements and send CLI reports 1420 based on the latency class of UE 115-a, so that UE 115-a has sufficient time to receive SRS, perform CLI measurements on SRS, generate CLI reports 1420, and send CLI reports 1420. If UE 115-a determines that there is insufficient time to generate and send CLI report 1420, UE 115-a may send dummy values, null values, or outdated CLI measurements in CLI report 1420. Otherwise, UE 115-a may perform CLI measurements on SRS 1415 and send the CLI measurements in CLI report 1420.
[0126] In some examples, UE 115-a may be configured with a CLI reference resource that defines a window within which UE 115-a may perform CLI measurements for CLI reporting 1420. In particular, the CLI reference resource may be the last resource within which UE 115-a may perform CLI measurements for CLI reporting 1420. In some examples, for periodic or semi-persistent CLI reporting, the time domain of the reference CLI resource may be defined according to the same rules as for CSI reporting (e.g., for CLI reporting, n CLI,rwf =n CSI,ref)。In other examples, for periodic or semi-persistent CLI reporting, the time domain of the reference CLI resource may be defined based on CLI measurements associated with lower complexity compared to CSI measurements. For example, the CLI report may be configured with a CLI reference resource corresponding to n CLI,ref , where n CLI,ref may be different from n CSI,ref . If a single resource is configured for CLI measurement, n CLI,ref may be the minimum value greater than or equal to such that the CLI reference resource corresponds to a valid downlink time slot. If multiple resources are configured for CLI measurement, n CLI,ref may be the minimum value greater than or equal to such that the CLI reference resource corresponds to a valid downlink time slot.
[0127] In some aspects, if UE 115-a is configured to report CSF based on CLI measurements, the CLI measurement resource and the CSI-IM resource may be assumed to be in the same time slot, or the CLI measurement resource may be in a different time slot from the CSI-RS used for CSI-IM. When UE 115-a reports CSF based on the CLI resource and the CLI resource is in a different time slot from the CSI-IM resource, the timing requirement for reporting CSF (e.g., Z, Z′, or the reference resource) may correspond to the minimum time used for calculating the report (e.g., CLI report 1420). In some examples, the timing requirement (e.g., Z, Z′, or the reference resource) may be derived based on the CSI resource, and the CLI resource may be expected to be within a predefined time offset of the CSI resource (e.g., <X symbols). In other examples, the timing requirement may be based on the latest time slot carrying the reference signal (e.g., CSI or CLI resource) for CSI or CLI. For example, for periodic or semi-persistent CSI reporting based on CLI, UE 115-a may determine whether the reference time slot meets the minimum timing requirement based on the CSI resource, the CLI resource, or both. In yet other examples, different timing requirements may be considered for CSI and CLI, and additional timing requirements may be for the CLI resource.
[0128] In addition to techniques for identifying appropriate timing for reporting CLI or reporting based on CLI, UE115-a may also support techniques for prioritizing CSI reports and CLI reports. For example, the wireless communication system 1400 may define a priority for a CSI report with CLI or a CSI report generated based on CLI (e.g., associated with a CLI report amount). In one example, a CSI report with CLI may have the same priority as a CSI report that does not carry L1-RSRP or L1-SINR (e.g., for CLI, k=1). For example, a CSI report that carries L1-RSRP or L1-SINR may be assigned a priority value (e.g., k) 0, and a CSI report that does not carry L1-RSRP or L1-SINR, a CLI-based CSI report, or a CLI report may be assigned a priority value (e.g., k) one, where a lower value of k indicates a higher priority. In another example, a CSI report with CLI may have a lower priority than a CSI report (e.g., for CLI, k=2). In yet another example, CSI reporting with CLI may have a configurable priority in RRC (eg, in the RRC configuration message, for CLI, "k" is configurable).
[0129] Fig.17 An example of a process flow 1700 for supporting prioritization and timing for CLI reporting in accordance with one or more aspects of the present disclosure is illustrated. The process flow 1700 includes a network entity 105-a, which may be a reference Figures 1 to 16 The process flow 1700 also includes UE 115-a and UE 115-b, which may be reference UEs. Figures 1 to 16 An example of UE 115 is depicted. Process flow 1700 may implement aspects of wireless communication system 100 or wireless communication system 1400. For example, process flow 1700 may support efficient techniques for performing and reporting CLI measurements to minimize CLI (eg, inter-UE CLI measurement and mitigation).
[0130] In the following description of process flow 1700, the signaling exchanged between network entity 105-a, UE 115-a, and UE 115-b may be exchanged in an order different from the example order shown, or the operations performed by network entity 105-a, UE 115-a, and UE 115-b may be performed in a different order or at a different time. Some operations may also be omitted from process flow 1700, and other operations may be added to process flow 1700.
[0131] The process flow 1700 may illustrate an example of CLI reporting according to the L1 CLI framework. The L1 CLI framework may provide maximum flexibility and may accommodate dynamic CLI. However, the L1 CLI framework may increase L1 control signaling overhead. L1 CLI measurements and reports may be triggered by dedicated DCI or group common DCI. The aggressor UE 115 may be configured with aperiodic, semi-persistent, or periodic NZP-SRS resources (e.g., CLI transmission resources), and the victim UE 115 may be configured with aperiodic, semi-persistent, or periodic CLI measurement resources. The UE 115-a may support aperiodic, semi-persistent, or periodic CLI reporting based on timing (e.g., timing behavior) or CLI resources (e.g., L1 CLI reporting). The UE 115-a may support subband-based CLI measurements or reports, and the UE 115-a may support beam-based CLI measurements or reports (e.g., using beams quasi-co-located for CLI measurement resources).
[0132] At 1705, the network entity 105-a may send an RRC configuration for SRS (e.g., an RRC configuration for aperiodic, semi-persistent, or periodic NZP-SRS) that configures the UE 115-b to send the SRS to the UE 115-a. At 1710, the network entity 105-a may send an RRC configuration for CLI measurement resources (e.g., an RRC configuration for aperiodic, semi-persistent, or periodic CLI measurement resources) that is used for the UE 115-a to monitor the SRS from the UE 115-b. At 1715, network entity 105-a may send downlink control information (DCI) that triggers UE 115-b to send SRS (e.g., a dedicated or group-common DCI trigger for NZP-SRS), and, at 1720, network entity 105-a may send DCI that triggers UE 115-a to perform CLI measurements and reports based on the SRS (e.g., a dedicated or group-common DCI trigger for CLI measurements or reports). At 1725, UE 115-b may then send an SRS (e.g., NZP-SRS) to be received by UE 115-a, and UE 115-a may perform CLI measurements on the SRS. Based on the CLI measurements performed on the SRS, at 1730, UE 115-a may then send a CLI report (e.g., an L1 CLI report) to network entity 105-a.
[0133] Fig.18A block diagram 1800 of a device 1805 supporting prioritization and timing for CLI reporting according to one or more aspects of the present disclosure is shown. The device 1805 may be an example of aspects of a UE 115 as described herein. The device 1805 may include a receiver 1810, a transmitter 1815, and a communication manager 1820. The device 1805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0134] The receiver 1810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to prioritization and timing for CLI reports, data channels, information channels). The information may be communicated to other components of the device 1805. The receiver 1810 may utilize a single antenna or a set of multiple antennas.
[0135] The transmitter 1815 may provide means for transmitting signals generated by other components of the device 1805. For example, the transmitter 1815 may transmit information associated with various information channels (e.g., control channels related to prioritization and timing for CLI reports, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 1815 may be co-located with the receiver 1810 in a transceiver module. The transmitter 1815 may utilize a single antenna or a set of multiple antennas.
[0136] The communication manager 1820, the receiver 1810, the transmitter 1815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of prioritization and timing for CLI reports as described herein. For example, the communication manager 1820, the receiver 1810, the transmitter 1815, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.
[0137] In some examples, the communication manager 1820, the receiver 1810, the transmitter 1815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0138] Additionally or alternatively, in some examples, the communication manager 1820, the receiver 1810, the transmitter 1815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1820, the receiver 1810, the transmitter 1815, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).
[0139] In some examples, communication manager 1820 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1810, transmitter 1815, or both. For example, communication manager 1820 may receive information from receiver 1810, transmit information to transmitter 1815, or integrate with receiver 1810, transmitter 1815, or both in combination to obtain information, output information, or perform various other operations as described herein.
[0140] The communication manager 1820 may support wireless communications at a UE according to examples as disclosed herein. For example, the communication manager 1820 may be configured to or otherwise support a component for reporting to a network entity a capability of the UE corresponding to a first duration for report generation at the UE. The communication manager 1820 may be configured to or otherwise support a component for receiving signaling indicating a reporting configuration including a first set of resources for cross-link interference measurements. The communication manager 1820 may be configured to or otherwise support a component for determining, based on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in a reporting configuration for reporting cross-link measurements. The communication manager 1820 may be configured to or otherwise support a component for sending a report based on a determination.
[0141] Additionally or alternatively, the communication manager 1820 may support wireless communications at a UE according to examples as disclosed herein. For example, the communication manager 1820 may be configured to or otherwise support a component for receiving signaling from a network entity indicating a cross-link interference report configuration including a resource set for cross-link interference measurement. The communication manager 1820 may be configured to or otherwise support a component for generating a first report based on performing cross-link interference measurements on the resource set. The communication manager 1820 may be configured to or otherwise support a component for sending a first report or a second report to the network entity in a time resource based on comparing a first priority of the first report with a second priority of the second report.
[0142] By including or configuring the communication manager 1820 according to the examples as described herein, the device 1805 (e.g., a processor controlling or otherwise coupled to the receiver 1810, the transmitter 1815, the communication manager 1820, or a combination thereof) may support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources. In particular, because the device 1805 may support efficient techniques for performing CLI and reporting based on CLI measurements, the network entity may be able to schedule communications at the UE based on the reports to minimize CLI at the device 1805. As a result, communications at the device 1805 may be more reliable and may avoid excessive retransmissions, resulting in reduced processing, reduced power consumption, and more efficient utilization of communication resources.
[0143] Fig.19 A block diagram 1900 of a device 1905 supporting prioritization and timing for CLI reporting according to one or more aspects of the present disclosure is shown. The device 1905 may be an example of aspects of the device 1805 or UE 115 as described herein. The device 1905 may include a receiver 1910, a transmitter 1915, and a communication manager 1920. The device 1905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0144] The receiver 1910 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to prioritization and timing for CLI reports, data channels, information channels). The information may be communicated to other components of the device 1905. The receiver 1910 may utilize a single antenna or a set of multiple antennas.
[0145] The transmitter 1915 may provide means for transmitting signals generated by other components of the device 1905. For example, the transmitter 1915 may transmit information associated with various information channels (e.g., control channels related to prioritization and timing for CLI reports, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 1915 may be co-located with the receiver 1910 in a transceiver module. The transmitter 1915 may utilize a single antenna or a set of multiple antennas.
[0146] The device 1905 or its various components may be examples of components for performing various aspects of prioritization and timing for CLI reporting as described herein. For example, the communication manager 1920 may include a UE capability manager 1925, a configuration manager 1930, a timing manager 1935, a reporting manager 1940, a priority manager 1945, or any combination thereof. The communication manager 1920 may be an example of various aspects of the communication manager 1820 as described herein. In some examples, the communication manager 1920 or its various components may be configured to use or otherwise cooperate with the receiver 1910, the transmitter 1915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1920 may receive information from the receiver 1910, transmit information to the transmitter 1915, or be integrated with the receiver 1910, the transmitter 1915, or both in combination to obtain information, output information, or perform various other operations as described herein.
[0147] The communication manager 1920 may support wireless communications at a UE according to examples as disclosed herein. The UE capability manager 1925 may be configured to or otherwise support a component for reporting to a network entity a capability of the UE corresponding to a first duration for report generation at the UE. The configuration manager 1930 may be configured to or otherwise support a component for receiving signaling indicating a report configuration including a first set of resources for cross-link interference measurements. The timing manager 1935 may be configured to or otherwise support a component for determining, based on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in a report configuration for reporting cross-link measurements. The reporting manager 1940 may be configured to or otherwise support a component for sending a report based on a determination.
[0148] Additionally or alternatively, the communication manager 1920 may support wireless communications at a UE according to examples as disclosed herein. The configuration manager 1930 may be configured to or otherwise support a component for receiving signaling from a network entity indicating a cross-link interference report configuration including a resource set for cross-link interference measurement. The report manager 1940 may be configured to or otherwise support a component for generating a first report based on performing cross-link interference measurements on the resource set. The priority manager 1945 may be configured to or otherwise support a component for sending a first report or a second report to the network entity in a time resource based on comparing a first priority of the first report with a second priority of the second report.
[0149] Fig. 20A block diagram 2000 of a communication manager 2020 supporting prioritization and timing for CLI reports in accordance with one or more aspects of the present disclosure is shown. The communication manager 2020 may be an example of aspects of the communication manager 1820, the communication manager 1920, or both as described herein. The communication manager 2020 or its various components may be examples of means for performing various aspects of prioritization and timing for CLI reports as described herein. For example, the communication manager 2020 may include a UE capability manager 2025, a configuration manager 2030, a timing manager 2035, a reporting manager 2040, a priority manager 2045, a reference resource manager 2050, a CSF manager 2055, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).
[0150] The communication manager 2020 may support wireless communications at a UE according to examples as disclosed herein. The UE capability manager 2025 may be configured to or otherwise support a component for reporting to a network entity a capability of the UE corresponding to a first duration for report generation at the UE. The configuration manager 2030 may be configured to or otherwise support a component for receiving signaling indicating a report configuration including a first set of resources for cross-link interference measurements. The timing manager 2035 may be configured to or otherwise support a component for determining, based on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in a report configuration for reporting cross-link measurements. The reporting manager 2040 may be configured to or otherwise support a component for sending a report based on a determination.
[0151] In some examples, the timing manager 2035 may be configured to or otherwise support a component for determining that the first duration is less than or equal to the second duration, the method also including. In some examples, the reporting manager 2040 may be configured to or otherwise support a component for generating a report based on performing cross-link interference measurements on the first resource set.
[0152] In some examples, the timing manager 2035 may be configured to or otherwise support a component for determining that the first duration is greater than the second duration, the method also comprising. In some examples, the reporting manager 2040 may be configured to or otherwise support a component for generating a report based on a previous cross-link interference measurement, a dummy value, a null value, or a combination thereof.
[0153] In some examples, reference resource manager 2050 may be configured or otherwise support means for identifying reference time resources corresponding to an end of a time window within which cross-link interference measurements are to be performed based on time resources allocated for sending reports to network entities.
[0154] In some examples, the time difference between the reference time resource and the time resource allocated for sending the report is the same value or a smaller value for the cross-link interference report as for the channel state information report.
[0155] In some examples, the reporting configuration includes a second set of resources for channel state information channel measurements, and the CSF manager 2055 can be configured to or otherwise support means for generating channel state feedback based on cross-link interference measurements performed on the first set of resources and channel state information channel measurements performed on the second set of resources, wherein sending the report includes. In some examples, the reporting configuration includes a second set of resources for channel state information channel measurements, and the CSF manager 2055 can be configured to or otherwise support means for sending the channel state feedback in the report.
[0156] In some examples, a first set of resources used for cross-link interference measurements is offset in time from a second set of resources used for channel state information channel measurements within a threshold.
[0157] In some examples, the timing manager 2035 may be configured as or otherwise support a component for determining that a second duration allocated in a reporting configuration for reporting to a network entity corresponds to a time between time resources allocated for sending a report and a latest time resource allocated for a cross-link interference measurement or a channel state information channel measurement.
[0158] In some examples, the first duration for report generation is for cross-link interference measurement, and the timing manager 2035 may be configured to or otherwise support means for identifying a third duration for report generation for channel state information channel measurement, the method also comprising. In some examples, the first duration for report generation is for cross-link interference measurement, and the timing manager 2035 may be configured to or otherwise support means for determining that both the first duration and the third duration are less than or equal to a second duration allocated in a report configuration for reporting to a network entity, wherein sending the channel state feedback in the report is based on the determination.
[0159] In some examples, the latency class corresponds to the latency class used for beam reporting by the UE.
[0160] In some examples, the latency class is based on the capabilities of the UE, the subcarrier spacing of the bandwidth portion used for communicating with the network entity, or a combination thereof.
[0161] In some examples, the latency class is low latency or high latency and is based on the amount of cross-link interference measurements to be reported, the amount of frequency bands associated with the cross-link interference measurements to be reported, the amount of resources used for the cross-link interference measurements to be reported, or a combination thereof.
[0162] Additionally or alternatively, the communication manager 2020 may support wireless communications at the UE according to examples as disclosed herein. In some examples, the configuration manager 2030 may be configured to or otherwise support a component for receiving signaling from a network entity indicating a cross-link interference report configuration including a resource set for cross-link interference measurement. In some examples, the report manager 2040 may be configured to or otherwise support a component for generating a first report based on performing cross-link interference measurements on the resource set. The priority manager 2045 may be configured to or otherwise support a component for sending a first report or a second report to the network entity in a time resource based on comparing a first priority of the first report with a second priority of the second report.
[0163] In some examples, the first priority of the first report is the same as the priority of a channel state information report without a reference signal received power measurement or a signal to interference plus noise ratio measurement.
[0164] In some examples, the first priority of the first report is lower than the priority of the channel state information report.
[0165] In some examples, the first priority of the first report is configurable, and priority manager 2045 may be configured as or otherwise support means for receiving a control message from the network entity indicating the first priority of the first report.
[0166] Fig.21 A diagram of a system 2100 including a device 2105 supporting prioritization and timing for CLI reporting according to one or more aspects of the present disclosure is shown. The device 2105 may be an example of a device 1805, a device 1905, or a UE 115 as described herein or include a component of the device 1805, a device 1905, or a UE 115. The device 2105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 2105 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 2120, an input / output (I / O) controller 2110, a transceiver 2115, an antenna 2125, a memory 2130, a code 2135, and a processor 2140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 2145).
[0167] I / O controller 2110 can manage input and output signals of device 2105. I / O controller 2110 can also manage peripheral devices that are not integrated into device 2105. In some cases, I / O controller 2110 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 2110 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 2110 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 2110 may be implemented as part of a processor (such as processor 2140). In some cases, a user may interact with device 2105 via I / O controller 2110 or via hardware components controlled by I / O controller 2110.
[0168] In some cases, the device 2105 may include a single antenna 2125. However, in some other cases, the device 2105 may have more than one antenna 2125, which can send or receive multiple wireless transmissions concurrently. The transceiver 2115 can communicate bidirectionally via one or more antennas 2125, wired or wireless links, as described herein. For example, the transceiver 2115 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 2115 may also include a modem, which is used to modulate packets, provide the modulated packets to one or more antennas 2125 for transmission, and demodulate packets received from one or more antennas 2125. The transceiver 2115 or the transceiver 2115 and one or more antennas 2125 can be examples of transmitters 1815, transmitters 1915, receivers 1810, receivers 1910, or any combination or components thereof as described herein.
[0169] The memory 2130 may include random access memory (RAM) and read-only memory (ROM). The memory 2130 may store computer-readable, computer-executable code 2135 including instructions that, when executed by the processor 2140, cause the device 2105 to perform various functions described herein. The code 2135 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 2135 may not be directly executable by the processor 2140, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 2130 may include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0170] The processor 2140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 2140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 2140. The processor 2140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 2130) to enable the device 2105 to perform various functions (e.g., various functions or tasks supporting prioritization and timing for CLI reports). For example, the device 2105 or a component of the device 2105 may include a processor 2140 and a memory 2130 coupled to or coupled to the processor 2140, and the processor 2140 and the memory 2130 are configured to perform the various functions described herein.
[0171] The communication manager 2120 may support wireless communications at a UE according to examples as disclosed herein. For example, the communication manager 2120 may be configured to or otherwise support a component for reporting to a network entity a capability of the UE corresponding to a first duration for report generation at the UE. The communication manager 2120 may be configured to or otherwise support a component for receiving signaling indicating a reporting configuration including a first set of resources for cross-link interference measurements. The communication manager 2120 may be configured to or otherwise support a component for determining, based on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in a reporting configuration for reporting cross-link measurements. The communication manager 2120 may be configured to or otherwise support a component for sending a report based on a determination.
[0172] Additionally or alternatively, the communication manager 2120 may support wireless communications at a UE according to examples as disclosed herein. For example, the communication manager 2120 may be configured to or otherwise support a component for receiving signaling from a network entity indicating a cross-link interference report configuration including a resource set for cross-link interference measurement. The communication manager 2120 may be configured to or otherwise support a component for generating a first report based on performing cross-link interference measurements on the resource set. The communication manager 2120 may be configured to or otherwise support a component for sending a first report or a second report to the network entity in a time resource based on comparing a first priority of the first report with a second priority of the second report.
[0173] By including or configuring the communication manager 2120 according to the examples as described herein, the device 2105 can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources. In particular, since the device 2105 can support efficient techniques for performing CLI and reporting based on CLI measurements, the network entity can be able to schedule communications at the UE based on the reports to minimize CLI at the device 2105. As a result, communications at the device 2105 can be more reliable and excessive retransmissions can be avoided, resulting in reduced processing, reduced power consumption, and more efficient utilization of communication resources.
[0174] In some examples, the communication manager 2120 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 2115, one or more antennas 2125, or any combination thereof. Although the communication manager 2120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 2120 may be supported or performed by the processor 2140, the memory 2130, the code 2135, or any combination thereof. For example, the code 2135 may include instructions that are executable by the processor 2140 to cause the device 2105 to perform various aspects of prioritization and timing for CLI reports as described herein, or the processor 2140 and the memory 2130 may be otherwise configured to perform or support such operations.
[0175] Fig. 22 A flow chart illustrating a method 2200 for supporting prioritization and timing for CLI reporting according to one or more aspects of the present disclosure is shown. The operations of the method 2200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2200 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 21 The described functions may be performed by the UE 115. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0176] At 2205, the method may include reporting to the network entity the capabilities of the UE corresponding to the first duration for report generation at the UE. The operations of 2205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2205 may be performed as described in reference to Fig. 20 The UE capability manager 2025 described here performs.
[0177] At 2210, the method may include receiving signaling indicating a reporting configuration including a first set of resources for cross-link interference measurement. The operations of 2210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2210 may be performed as described in reference to Fig. 20 The configuration manager 2030 described here performs.
[0178] At 2215, the method may include determining, based on the latency class of the UE, whether a first duration for report generation at the UE is greater than a second duration allocated in a reporting configuration for reporting cross-link measurements. The operations of 2215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2215 may be performed as described in reference to Fig. 20 The time manager 2035 described here performs.
[0179] At 2220, the method may include sending a report based on the determination. The operations of 2220 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2220 may be performed as described in reference to Fig. 20 The report manager 2040 described here performs.
[0180] Fig.23 A flow chart illustrating a method 2300 for supporting prioritization and timing for CLI reporting according to one or more aspects of the present disclosure is shown. The operations of the method 2300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 21 The described functions may be performed by the UE 115. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0181] At 2305, the method may include receiving signaling from a network entity indicating a cross-link interference reporting configuration including a resource set for cross-link interference measurement. The operations of 2305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2305 may be performed as described in reference to Fig. 20 The configuration manager 2030 described here performs.
[0182] At 2310, the method may include generating a first report based on performing cross-link interference measurements on the resource set. The operations of 2310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2310 may be performed as described in reference Fig. 20 The report manager 2040 described here performs.
[0183] At 2315, the method may include sending the first report or the second report to the network entity in the time resource based on comparing the first priority of the first report with the second priority of the second report. The operations of 2315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2315 may be performed as described in reference to Fig. 20 The priority manager 2045 described here performs.
[0184] The following provides an overview of various aspects of the disclosure:
[0185] Aspect 1: A method for performing wireless communications at a UE, comprising: reporting to a network entity a capability of the UE corresponding to a first duration for report generation at the UE; receiving signaling indicating a reporting configuration including a first set of resources for cross-link interference measurements; determining, at least in part based on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in the reporting configuration for reporting the cross-link measurements; and sending a report based at least in part on the determination.
[0186] Aspect 2: The method according to aspect 1 also includes: determining that the first duration is less than or equal to the second duration, and the method also includes: generating the report based at least in part on performing the cross-link interference measurement on the first resource set.
[0187] Aspect 3: The method according to any one of Aspects 1 to 2 also includes: determining that the first duration is greater than the second duration, and the method also includes: generating the report at least in part based on previous cross-link interference measurements, dummy values, null values, or a combination thereof.
[0188] Aspect 4: The method according to any one of Aspects 1 to 3 further includes: identifying a reference time resource corresponding to the end of a time window within which the cross-link interference measurement is to be performed based at least in part on a time resource allocated for sending the report to the network entity.
[0189] Aspect 5: The method according to aspect 4, wherein the time difference between the reference time resource and the time resource allocated for sending the report is the same value or a smaller value for a cross-link interference report than for a channel state information report.
[0190] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the reporting configuration includes a second resource set for channel state information channel measurement, and the method further includes: generating channel state feedback based at least in part on cross-link interference measurements performed on the first resource set and the channel state information channel measurement performed on the second resource set, wherein sending the report includes: sending the channel state feedback in the report.
[0191] Aspect 7: The method according to aspect 6, wherein the first resource set used for cross-link interference measurement and the second resource set used for channel state information channel measurement are offset in time within a threshold.
[0192] Aspect 8: The method according to any one of Aspects 6 to 7 further includes: determining that the second duration allocated in the reporting configuration for reporting to the network entity corresponds to the time between the time resources allocated for sending the report and the latest time resources allocated for the cross-link interference measurement or the channel state information channel measurement.
[0193] Aspect 9: A method according to any one of Aspects 6 to 8, wherein the first duration for report generation is for the cross-link interference measurement, and the method also includes: a third duration for report generation for the channel state information channel measurement identifier, and the method also includes: determining that both the first duration and the third duration are less than or equal to the second duration allocated in the reporting configuration for reporting to the network entity, wherein sending the channel state feedback in the report is at least partially based on the determination.
[0194] Aspect 10: A method according to any one of Aspects 1 to 9, wherein the latency class corresponds to a latency class used for beam reporting by the UE.
[0195] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the latency class is based at least in part on the capability of the UE, the subcarrier spacing of the bandwidth portion used for communicating with the network entity, or a combination thereof.
[0196] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the latency class is low latency or high latency and is based at least in part on the amount of cross-link interference measurements to be reported, the amount of frequency bands associated with the cross-link interference measurements to be reported, the amount of resources used for the cross-link interference measurements to be reported, or a combination thereof.
[0197] Aspect 13: A method for performing wireless communications at a UE, comprising: receiving signaling from a network entity indicating a cross-link interference reporting configuration including a resource set for cross-link interference measurement; generating a first report based at least in part on performing the cross-link interference measurement on the resource set; and sending the first report or the second report to the network entity in a time resource based at least in part on comparing a first priority of the first report with a second priority of the second report.
[0198] Aspect 14: The method according to aspect 13, wherein the first priority of the first report is the same as the priority of a channel state information report without reference signal received power measurement or signal to interference plus noise ratio measurement.
[0199] Aspect 15: The method according to any one of aspects 13 to 14, wherein the first priority of the first report is lower than the priority of a channel state information report.
[0200] Aspect 16: The method according to any one of aspects 13 to 15, wherein the first priority of the first report is configurable, and the method further comprises: receiving a control message indicating the first priority of the first report from the network entity.
[0201] Aspect 17: An apparatus for performing wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to enable the apparatus to perform a method according to any one of Aspects 1 to 12.
[0202] Aspect 18: An apparatus for wireless communication at a UE, comprising at least one component for performing the method according to any one of aspects 1 to 12.
[0203] Aspect 19: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 12.
[0204] Aspect 20: An apparatus for performing wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 13 to 16.
[0205] Aspect 21: An apparatus for wireless communication at a UE, comprising at least one component for performing a method according to any one of aspects 13 to 16.
[0206] Aspect 22: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 13 to 16.
[0207] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0208] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.
[0209] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.
[0210] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0211] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.
[0212] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transported from one place to another.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0213] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."
[0214] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
[0215] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.
[0216] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific implementation includes specific details to provide an understanding of the technology. However, the technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.
[0217] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: reporting, to a network entity, capabilities of the UE corresponding to a first duration for report generation at the UE; receiving signaling indicating a reporting configuration including a first set of resources for cross-link interference measurement; determining, based at least in part on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in the reporting configuration for reporting the cross-link measurement; as well as A report is sent based at least in part on the determination.
2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: determining that the first duration is less than or equal to the second duration; and The report is generated based at least in part on performing the cross-link interference measurement on the first set of resources.
3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: determining that the first duration is greater than the second duration; and The report is generated based at least in part on a previous cross-link interference measurement, a dummy value, a null value, or a combination thereof.
4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A reference time resource corresponding to an end of a time window within which the cross-link interference measurement is to be performed is identified based at least in part on a time resource allocated for sending the report to the network entity.
5. The apparatus of claim 4, wherein a time difference between the reference time resource and the time resource allocated for sending the report is the same value or a smaller value for a cross-link interference report than for a channel state information report.
6. The apparatus of claim 1 , wherein the reporting configuration comprises a second set of resources for channel state information channel measurements, and the instructions are further executable by the processor to cause the apparatus to: generating channel state feedback based at least in part on a cross-link interference measurement performed on the first set of resources and the channel state information channel measurement performed on the second set of resources, wherein sending the report comprises: The channel state feedback is sent in the report.
7. The apparatus of claim 6, wherein the first set of resources used for cross-link interference measurement and the second set of resources used for channel state information channel measurement are offset in time within a threshold.
8. The apparatus of claim 6, wherein the instructions are further executable by the processor to cause the apparatus to: Determining that the second duration allocated in the reporting configuration for reporting to the network entity corresponds to a time between a time resource allocated for sending the report and a latest time resource allocated for the cross-link interference measurement or the channel state information channel measurement.
9. The apparatus of claim 6, wherein the first duration for report generation is for the cross-link interference measurement, and wherein the instructions are further executable by the processor to cause the apparatus to: a third duration for report generation for the channel state information channel measurement identifier; and Determining that both the first duration and the third duration are less than or equal to the second duration allocated in the reporting configuration for reporting to the network entity, wherein sending the channel state feedback in the report is based at least in part on the determination.
10. The apparatus of claim 1, wherein the latency class corresponds to a latency class used for beam reporting by the UE.
11. The apparatus of claim 1 , wherein the latency class is based at least in part on the capabilities of the UE, a subcarrier spacing of a bandwidth portion used for communicating with the network entity, or a combination thereof.
12. An apparatus according to claim 1, wherein the latency class is low latency or high latency and is based at least in part on the amount of cross-link interference measurements to be reported, the amount of frequency bands associated with the cross-link interference measurements to be reported, the amount of resources used for the cross-link interference measurements to be reported, or a combination thereof.
13. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving signaling from a network entity indicating a cross-link interference reporting configuration including a set of resources for cross-link interference measurement; generating a first report based at least in part on performing the cross-link interference measurement on the set of resources; as well as Sending the first report or the second report to the network entity in a time resource based at least in part on comparing a first priority of the first report to a second priority of the second report.
14. The apparatus of claim 13, wherein the first priority of the first report is the same as a priority of a channel state information report without a reference signal received power measurement or a signal to interference plus noise ratio measurement.
15. The apparatus of claim 13, wherein the first priority of the first report is lower than a priority of a channel state information report.
16. A method for wireless communication at a user equipment (UE), the method comprising: reporting, to a network entity, capabilities of the UE corresponding to a first duration for report generation at the UE; receiving signaling indicating a reporting configuration including a first set of resources for cross-link interference measurement; determining, based at least in part on a latency class of the UE, whether the first duration for report generation at the UE is greater than a second duration allocated in the reporting configuration for reporting the cross-link measurement; as well as A report is sent based at least in part on the determination.
17. The method according to claim 16, further comprising: determining that the first duration is less than or equal to the second duration; as well as The report is generated based at least in part on performing the cross-link interference measurement on the first set of resources.
18. The method according to claim 16, further comprising: determining that the first duration is greater than the second duration; as well as The report is generated based at least in part on a previous cross-link interference measurement, a dummy value, a null value, or a combination thereof.
19. The method according to claim 16, further comprising: A reference time resource corresponding to an end of a time window within which the cross-link interference measurement is to be performed is identified based at least in part on a time resource allocated for sending the report to the network entity.
20. The method of claim 19, wherein a time difference between the reference time resource and the time resource allocated for sending the report is the same value or a smaller value for a cross-link interference report than a channel state information report.
21. The method of claim 16, wherein the reporting configuration comprises a second resource set for channel state information channel measurement, the method further comprising: generating channel state feedback based at least in part on a cross-link interference measurement performed on the first set of resources and the channel state information channel measurement performed on the second set of resources; and The channel state feedback is sent in the report.
22. The method of claim 21, wherein the first set of resources used for cross-link interference measurements and the second set of resources used for channel state information channel measurements are offset in time within a threshold.
23. The method according to claim 21, further comprising: Determining that the second duration allocated in the reporting configuration for reporting to the network entity corresponds to a time between a time resource allocated for sending the report and a latest time resource allocated for the cross-link interference measurement or the channel state information channel measurement.
24. The method of claim 21, wherein the first duration for report generation is for the cross-link interference measurement, the method further comprising: a third duration for report generation for the channel state information channel measurement identifier; as well as Determining that both the first duration and the third duration are less than or equal to the second duration allocated in the reporting configuration for reporting to the network entity, wherein sending the channel state feedback in the report is based at least in part on the determination.
25. The method of claim 16, wherein the latency class corresponds to a latency class used for beam reporting by the UE.
26. The method of claim 16, wherein the latency class is based at least in part on the capabilities of the UE, a subcarrier spacing of a bandwidth portion used for communicating with the network entity, or a combination thereof.
27. A method according to claim 16, wherein the latency class is low latency or high latency and is based at least in part on the amount of cross-link interference measurements to be reported, the amount of frequency bands associated with the cross-link interference measurements to be reported, the amount of resources used for the cross-link interference measurements to be reported, or a combination thereof.
28. A method for wireless communication at a user equipment (UE), the method comprising: receiving signaling from a network entity indicating a cross-link interference reporting configuration including a set of resources for cross-link interference measurement; generating a first report based at least in part on performing the cross-link interference measurement on the set of resources; as well as Sending the first report or the second report to the network entity in a time resource based at least in part on comparing a first priority of the first report to a second priority of the second report.
29. The method of claim 28, wherein the first priority of the first report is the same as a priority of a channel state information report without a reference signal received power measurement or a signal to interference plus noise ratio measurement.
30. The method of claim 28, wherein the first priority of the first report is lower than a priority of a channel state information report.
