Aspects for cross-link interference measurement
By employing L1, PHY layer or L2, MAC layer signaling configurations in wireless communication systems, flexible and efficient reporting of cross-link interference measurements is achieved, solving the problems of time delay and insufficient acquisition in existing technologies and improving system performance.
Patent Information
- Application Number
- CN202380031733.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-07
- Filing Date
- 2023-03-14
- Publication Date
- 2024-11-29
AI Technical Summary
In existing technologies, cross-link interference measurement methods are not flexible enough with higher-layer signaling, resulting in long delays and difficulty in capturing beam-level cross-link interference, especially in dynamically changing scenarios where timely responses are not possible.
By configuring communication equipment to perform cross-link interference measurement and reporting through lower-layer signaling, such as L1, PHY layer or L2, MAC layer signaling, the measurement flexibility is increased and the latency is reduced. Cross-link interference measurement and reporting can be performed using periodic, semi-persistent or non-periodic resources and signaling methods.
It improves the flexibility and timeliness of cross-link interference measurement, enhances the data rate, spectrum efficiency and resource utilization of wireless communication systems, and improves network operation and efficiency.
Smart Images

Figure CN119054222A_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims priority to U.S. patent application No. 17 / 715,715, entitled “ASPECTS FOR CROSS-LINK INTERFERENCE MEASUREMENT,” filed by Bai et al. on April 7, 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 aspects for cross-link interference measurements. Background Art
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. 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). A wireless multiple access communication system may include one or more network entities, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). In some examples of wireless communication systems, adjacent communication devices may send or receive communications concurrently, which may cause cross-link interference. Summary of the invention
[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting aspects for cross-link interference measurements. For example, the described technology provides cross-link interference measurements and reports performed by a communication device such as a user equipment (UE). In some examples, the UE may receive control signaling from a network entity indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities. The UE may generate a cross-link interference report based on the control signaling and a trigger for the cross-link interference measurement. The cross-link interference report may indicate the cross-link interference measurement of at least one receive beam in the set of receive beams. The UE may send a cross-link interference report to the network entity.
[0006] A method for wireless communication at a UE is described. The method may include: receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities; generating a cross-link interference report indicating the cross-link interference measurement for at least one receive beam in the set of receive beams based on the control signaling and a trigger for the cross-link interference measurement; and sending the cross-link interference report to a network entity.
[0007] 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 executable by the processor to cause the apparatus to perform the following operations: receive control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities; based on the control signaling and a trigger for the cross-link interference measurement, generate a cross-link interference report indicating the cross-link interference measurement for at least one receive beam in the set of receive beams; and send the cross-link interference report to a network entity.
[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities; a component for generating a cross-link interference report indicating the cross-link interference measurement for at least one receive beam in the set of receive beams based on the control signaling and a trigger for the cross-link interference measurement; and a component for sending the cross-link interference report to a network entity.
[0009] 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 perform the following operations: receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities; based on the control signaling and a trigger for cross-link interference measurement, generating a cross-link interference report indicating the cross-link interference measurement for at least one receive beam in the set of receive beams; and sending the cross-link interference report to a network entity.
[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: performing a cross-link interference measurement procedure at an opportunity in the set of cross-link interference measurement opportunities to generate the cross-link interference measurement using a receive beam in the set of receive beams corresponding to the opportunity, wherein the trigger includes the opportunity.
[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a downlink control information (DCI) message indicating a timing in the set of cross-link interference measurement timings and a receive beam corresponding to the timing, and performing a cross-link interference measurement procedure at the timing to generate the cross-link interference measurement using the receive beam, wherein the trigger includes the timing indicated by the DCI message.
[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DCI message may be scrambled with a radio network temporary identifier (RNTI) instructing the UE to generate the cross-link interference measurement, the cross-link interference report being sent on an uplink shared channel.
[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities may include operations, features, components, or instructions for: receiving a medium access control element (MAC-CE) indicating the set of cross-link interference measurement opportunities and the set of receive beams; and the method also includes: performing a cross-link interference measurement procedure at an opportunity in a set of cross-link interference measurement opportunities to generate a cross-link interference measurement using a receive beam in a set of receive beams corresponding to the opportunity, wherein the trigger includes a timing indicated by the MAC-CE.
[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a confirmation message in response to a MAC-CE, wherein the cross-link interference report may be sent on an uplink control channel based on at least an offset from sending the confirmation message.
[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing a cross-link interference measurement procedure to generate a cross-link interference measurement based on a UE detecting an event, wherein the event comprises a trigger.
[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a cross-link interference report may include operations, features, components, or instructions for sending an uplink control information message including a cross-link interference report on an uplink control channel.
[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a scheduling request to a network entity; and receiving control signaling indicating uplink resources of a shared channel in response to the scheduling request, wherein sending a cross-link interference report includes sending a MAC-CE including the cross-link interference report on the uplink resources of the shared channel.
[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, at least one receive beam includes a default receive beam, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for: selecting a default receive beam for cross-link interference measurement based on an offset between a DCI message and a timing indicated by a DCI message for cross-link interference measurement being less than a threshold offset, wherein the default receive beam may be different from a second receive beam in a set of receive beams that may be associated with the timing.
[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending UE capability signaling indicating the threshold offset to the network entity.
[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the threshold offset includes a first offset value and a second offset value, and the second offset value can be based on whether the DCI message and the opportunity indicated by the DCI message can be associated with the same subcarrier spacing.
[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying a quasi-co-site (QCL) relationship of a downlink signal received at a UE, where a network entity communicates with the UE via a single transmit-receive point; and performing a measurement procedure at an opportunity in a set of cross-link interference measurement opportunities to generate a cross-link interference measurement based on the downlink signal overlapping the QCL relationship with the opportunity.
[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying a first QCL relationship for a downlink signal received at a UE, wherein a network entity communicates with the UE via a single transmit-receive point; and performing a measurement procedure at an opportunity in a set of cross-link interference measurement opportunities to generate a cross-link interference measurement based on the downlink signal not overlapping with the opportunity using a second QCL relationship associated with a minimum control resource set (CORESET) identifier.
[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for selecting at least one receive beam from a set of receive beams for cross-link interference measurement based on: for a single DCI message operation with a set of multiple transmit-receive points, a transmit configuration indicator (TCI) code point having a lowest identifier value and identifying a set of multiple TCI states corresponding to a set of multiple transmit-receive points; for multiple DCI message operations with a set of multiple transmit-receive points, a TCI state associated with a most recently monitored CORESET for each CORESET pool; for a single frequency network (SNF) operation, a TCI code point having a lowest identifier value; and for a cross-carrier scheduling operation, a TCI code point having a lowest identifier value.
[0024] A method for wireless communication at a network entity is described. The method may include: outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by a UE to generate a cross-link interference report; and obtaining a cross-link interference report indicating a cross-link interference measurement of at least one receive beam in the set of receive beams from the UE.
[0025] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: output control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by a UE to generate a cross-link interference report; and obtain a cross-link interference report indicating a cross-link interference measurement of at least one receive beam in the set of receive beams from the UE.
[0026] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by a UE to generate a cross-link interference report; and a component for obtaining a cross-link interference report indicating a cross-link interference measurement of at least one receive beam in the set of receive beams from the UE.
[0027] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to perform the following operations: output control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by a UE to generate a cross-link interference report; and obtain a cross-link interference report indicating a cross-link interference measurement of at least one receive beam in the set of receive beams from the UE.
[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a DCI message indicating an opportunity in a set of cross-link interference measurement opportunities and a receive beam corresponding to the opportunity, wherein the cross-link interference measurement can be generated using the receive beam at least in part in response to a trigger including the opportunity indicated by the DCI message.
[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DCI message may be scrambled with an RNTI that instructs the UE to generate a cross-link interference measurement, the cross-link interference report being obtained on an uplink shared channel.
[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities may include operations, features, components, or instructions for: outputting a MAC-CE indicating a set of cross-link interference measurement opportunities and a set of receive beams, wherein the cross-link interference measurement may be generated using at least one receive beam at least in part in response to a triggering of an opportunity in the set of cross-link interference measurement opportunities indicated by the MAC-CE.
[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining a confirmation message in response to a MAC-CE, wherein the cross-link interference report may be sent on an uplink control channel based on at least an offset from sending the confirmation message.
[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a cross-link interference measurement of a cross-link interference report may be generated based on an event detected at a UE.
[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining a cross-link interference report may include operations, features, components, or instructions for obtaining uplink control information including a cross-link interference report on an uplink control channel.
[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining a scheduling request from a UE; and outputting control signaling indicating uplink resources of a shared channel in response to the scheduling request, wherein obtaining a cross-link interference report includes obtaining a MAC-CE including a cross-link interference report on the uplink resources of the shared channel.
[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining UE capability signaling indicating a threshold offset for an offset between a DCI message and a timing indicated by the DCI message for cross-link interference measurement.
[0036] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above in order to better understand the subsequent specific embodiments. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as the basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not deviate from the scope of protection of the attached claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood according to the following description. Each figure is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.
[0037] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, each embodiment and / or use can be generated via an integrated chip embodiment and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. The scope of specific implementation can range from chip-level or module components to non-module, non-chip-level specific implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovation. In some actual settings, the equipment in conjunction with the aspects and features must also include other components and features for the specific implementation and practice of the embodiments protected and described by the claims. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] Figure 1 An example of a wireless communication system supporting various aspects for cross-link interference measurements in accordance with one or more aspects of the present disclosure is illustrated.
[0039] Figure 2 An example of a network architecture supporting various aspects for cross-link interference measurements in accordance with one or more aspects of the present disclosure is illustrated.
[0040] Figure 3A An example of a wireless communication system supporting various aspects for cross-link interference measurements in accordance with one or more aspects of the present disclosure is illustrated.
[0041] Figure 3B An example of a Medium Access Control Element (MAC-CE) supporting various aspects for cross-link interference measurements in accordance with one or more aspects of the present disclosure is illustrated.
[0042] Figures 4 to 6 Each illustrates an example of a timing diagram supporting various aspects for cross-link interference measurement according to one or more aspects of the present disclosure.
[0043] Figure 7 and Figure 8 Each illustrates an example of a process flow supporting various aspects for cross-link interference measurement according to one or more aspects of the present disclosure.
[0044] Fig. 9 and Fig.10 A block diagram of a device supporting various aspects for cross-link interference measurement in accordance with one or more aspects of the present disclosure is shown.
[0045] Fig.11 A block diagram of a communications manager supporting aspects for cross-link interference measurements in accordance with one or more aspects of the present disclosure is shown.
[0046] Fig.12 A diagram of a system including a device supporting aspects for cross-link interference measurement in accordance with one or more aspects of the present disclosure is shown.
[0047] Fig.13 and Fig.14 A block diagram of a device supporting various aspects for cross-link interference measurement in accordance with one or more aspects of the present disclosure is shown.
[0048] Fig.15 A block diagram of a communications manager supporting aspects for cross-link interference measurements in accordance with one or more aspects of the present disclosure is shown.
[0049] Fig.16 A diagram of a system including a device supporting aspects for cross-link interference measurement in accordance with one or more aspects of the present disclosure is shown.
[0050] Figures 17 to 21 A flow chart illustrating a method for supporting aspects for cross-link interference measurements in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION
[0051] In some wireless communication systems, a communication device such as a user equipment (UE) or a network entity may support wireless communication through one or more radio access technologies. Examples of radio access technologies may include fourth generation (4G) systems (such as long term evolution (LTE) systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). In such cases, the communication device may operate in half-duplex mode or full-duplex mode or a combination thereof. In half-duplex mode, the communication device may send or receive communication during a time period (such as a transmit time interval (TTI) that may span one or more time resources (e.g., symbols, mini-slots, time slots, etc.). In full-duplex mode, the communication device may simultaneously send and receive communication during the time period. That is, the communication received by the communication device may overlap with the communication sent by the communication device in the time domain. For example, the symbol occupied by the received signal may overlap with the symbol occupied by the transmitted signal.
[0052] In some examples, adjacent communication devices (e.g., UE, network entity) may concurrently perform full-duplex communication or half-duplex time division duplex (TDD) so that the communication received by the first communication device may overlap in time with the communication sent by the second communication device (e.g., adjacent communication device). In such an example, the communication sent by the second communication device may interfere with the communication received at the first communication device. Such interference may be referred to as cross-link interference. In some examples, cross-link interference may degrade the wireless communication between the first communication device and the network. Therefore, in order to mitigate the impact of cross-link interference, the network may configure the first communication device to measure and report cross-link interference.
[0053] In some examples, a network may configure a communication device (e.g., a UE) to perform cross-link interference reporting via higher layer (e.g., Layer 3 (L3), radio resource control (RRC) layer) signaling. However, in some examples, higher layer signaling may be relatively inflexible and associated with increased latency (e.g., relative to lower layer signaling) due to updating higher layer cross-link interference configurations. Therefore, higher layer cross-link interference reporting may not be suitable (or less suitable) for scenarios where cross-link interference changes dynamically relative to increased latency associated with higher layer configuration signaling. In addition, higher layer cross-link interference measurements may lack spatial granularity, such that higher layer cross-link interference reports may not be able to capture beam-level cross-link interference.
[0054] Various aspects of the present disclosure generally relate to techniques for cross-link interference measurement, and more specifically to techniques for configuring a communication device (such as a UE) to measure and report cross-link interference via lower layer (e.g., Layer 1 (L1), physical (PHY) layer, Layer 2 (L2), medium access control (MAC) layer) signaling. For example, a network may configure a communication device to measure and report cross-link interference periodically, semi-persistently, or aperiodically, thereby increasing flexibility and reducing latency of cross-link interference reporting (e.g., relative to higher layer cross-link interference reporting). Additionally or alternatively, a network may increase the granularity of cross-link interference reporting by configuring a communication device to measure and report cross-link interference based on one or more transmit configuration indicator (TCI) states associated with resources configured to perform cross-link interference measurements (e.g., which may also be referred to herein as beams, receive beams (for downlink or sidelink at the UE), transmit beams (for uplink or sidelink at the UE), beam configurations, or beam configuration states or modes).
[0055] For example, the network may configure one or more resources for the communication device to perform cross-link interference measurements (e.g., on a reference signal sent by another communication device), and each of the configured resources may be associated with a transmission configuration indicator state to be used by the communication device to perform cross-link interference measurements. The configured resources may be periodic, semi-persistent, or aperiodic. Additionally or alternatively, the network may configure one or more resources for the communication device to send a cross-link interference report (e.g., indicating the measured cross-link interference). The network may configure the communication device to report cross-link interference periodically, semi-persistently, or aperiodically. For example, the network may configure periodic resources for the communication device (e.g., via RRC signaling), and the communication device may send cross-link interference reports via these periodic resources. Additionally or alternatively, the network may trigger the communication device to send a cross-link interference report aperiodically, for example, via a downlink control information (DCI) message or signaling. Additionally or alternatively, the network may configure a semi-persistent resource for the communication device for sending a cross-link interference report that may be activated (e.g., triggered), such as via a medium access control element (MAC-CE) or DCI message or signaling. Additionally or alternatively, the network may configure the communication device to send a report based on an event, such that the cross-link interference measurement meets (or fails to meet) a threshold.
[0056] Certain aspects of the subject matter described herein can be implemented to achieve one or more of the following potential advantages. The techniques employed by the communication device can provide benefits and enhancements to the operation of the communication device, including enabling cross-link interference measurement and reporting via lower layer signaling. In addition, as described herein, aspects for cross-link interference measurement can support higher data rates, spectrum efficiency enhancements, and efficient resource utilization, thereby improving throughput and reliability. Therefore, such techniques can lead to improved network operation and network efficiency, as well as other benefits.
[0057] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are also described in the context of a network architecture, another wireless communication system, a MAC-CE, timing diagrams, and process flows. Aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow charts related to cross-link interference measurement.
[0058] Figure 1 An example of a wireless communication system 100 supporting aspects for cross-link interference measurement 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).
[0059] 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 various 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, and the network entity 105 and the UE 115 may support signal communication over the geographic area according to one or more radio access technologies (RATs).
[0060] 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 can communicate with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.
[0061] 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 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, a 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 a second node.
[0062] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul 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 directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 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 .
[0063] 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, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).
[0064] 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. 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)).
[0065] The functional split between CU 160, DU 165, and RU 170 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 170. 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., 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, 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 the other of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions 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.
[0066] 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 the 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 host entities or IAB hosts. 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 host network entity 105 (e.g., a host base station 140). One or more host network entities 105 (e.g., IAB hosts) 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 terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB host. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas 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.
[0067] In the case where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support aspects for cross-link interference measurement 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).
[0068] 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 appliances or vehicles, meters, etc.
[0069] 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 shown.
[0070] 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 the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).
[0071] The signal waveform sent on 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 using MCM technology, 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), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate for 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 of communications with UE 115.
[0072] 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, T s =1 / (Δf max ·N f ) seconds sampling period, 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. The 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).
[0073] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into multiple 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 multiple 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 also be divided into multiple mini time slots containing 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.
[0074] A subframe, a slot, a mini-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 transmit time interval (TTI). In some examples, the TTI duration (e.g., the number 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 bursts of shortened TTIs (sTTIs)).
[0075] 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) for 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., control resource sets) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for 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 the control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format having a given payload size. The search space set may include: a common search space set configured for transmitting control information to multiple UEs 115, and a UE-specific search space set for transmitting control information to a specific UE 115.
[0076] 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 a logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. 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, as well as other examples.
[0077] 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.
[0078] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable or 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 applications or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency are used interchangeably herein.
[0079] In some examples, the UE 115 can 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 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 conducted between UEs 115 without involving network entity 105 .
[0080] 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 stratum (NAS) functions, such as mobility, authentication, and bearer management for 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 delivered via the user plane entity, 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.
[0081] 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 approximately 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 the 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 ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0082] The wireless communication system 100 can utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands 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 use carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in combination with component carriers operating in licensed bands. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.
[0083] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can 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, 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 can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.
[0084] 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 at a particular orientation 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 the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).
[0085] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.
[0086] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.
[0087] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).
[0088] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).
[0089] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reorganization to communicate on the logical channel. The MAC layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can 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 can provide the establishment, configuration and maintenance of the RRC connection of the radio bearer that supports user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, the transport channel can be mapped to the physical channel.
[0090] The wireless communication system 100 may support aspects for cross-link interference measurement. For example, the UE 115 may receive control signaling from the network entity 105 indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities. The UE 115 may generate a cross-link interference report based on the control signaling and the triggering of the cross-link interference measurement. The cross-link interference report may indicate the cross-link interference measurement of at least one receive beam in the set of receive beams. The UE 115 may send the cross-link interference report to the network entity 105. In some examples, by sending the cross-link interference report to the network entity 105, the UE 115 may provide one or more enhancements to the cross-link interference mitigation performed by the network, as well as other benefits.
[0091] Figure 2An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with the core network 130-a via a backhaul link 120-a, or indirectly with the core network 130-a through one or more disaggregated network entities 105 (e.g., a near-RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RUs 170-a may be associated with respective coverage areas 110-a and may communicate with the UEs 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.
[0092] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.
[0093] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to process user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.
[0094] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented with an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.
[0095] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with RU 170-a may be controlled by the corresponding DU 165-a. In some examples, this configuration may enable DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).
[0096] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.
[0097] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).
[0098] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).
[0099] The network architecture 200 may support aspects for cross-link interference measurement and reporting. In some examples, a network entity (e.g., CU 160-a, DU 165-a, RU 170-a, etc.) may configure UE 115-a to perform cross-link interference reporting via higher layer signaling. In some examples of higher layer cross-link interference reporting, CU 160-a may obtain a cross-link interference report from UE 115-a via DU165-a. However, in some examples, transmitting a cross-link interference report between CU 160-a and DU 165-a (e.g., via a fronthaul communication link 168-a) may result in increased latency relative to lower layer (e.g., L1, PHY layer, L2, MAC layer) signaling, where information may be obtained by DU 165-a from UE 115.
[0100] Therefore, the network can configure UE 115-a to report cross-link interference measurements via lower layer signaling. In some examples, these techniques can reduce the delay associated with cross-link interference reports. For example, a network entity (e.g., DU 165-a, RU 170-a) can output control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for UE 115-a to generate a cross-link interference report. The network entity (e.g., DU 165-a, RU 170-a) can obtain a cross-link interference report indicating a cross-link interference measurement for at least one receive beam in the set of receive beams from UE 115-a. In some examples, in response to receiving a cross-link interference report, a network entity (e.g., CU 160-a, DU 165-a, RU 170-a, etc.) can perform one or more cross-link interference mitigation techniques. Such techniques can improve the reliability of wireless communication between UE 115-a and the network.
[0101] Figure 3A An example of a wireless communication system 300 that supports aspects for cross-link interference measurement according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 can implement or be implemented by one or more aspects of the wireless communication system 100. For example, the wireless communication system 300 may include one or more UEs 315 (e.g., UE 315-a, UE 315-b, and UE 315-c), which may be reference Figure 1 The wireless communication system 300 may also include one or more network entities 305 (eg, network entity 305-a and network entity 305-b), which may be as described in reference Figure 1 The network entity 305 and the UE 315 may communicate within one or more coverage areas 310 (e.g., coverage area 310-a, coverage area 310-b), which may be as described in reference to Figure 1 or Figure 2 An example of a coverage area 110 is described. Figure 3A In the example of , network entity 305-a can serve a cell providing coverage area 310-a, and network entity 305-b can serve a cell providing coverage area 310-b. Wireless communication system 300 can include features for improving communication between UE 315 and the network, as well as other benefits.
[0102] exist Figure 3A In the example of , UE 315 and network entity 305 can communicate via one or more communication links. For example, UE 315-a can send communications (e.g., uplink communications) to network entity 305-a via communication link 330-a, and UE 315-c can send communications to network entity 305-b via communication link 330-c. Additionally or alternatively, UE 315-b can send communications to network entity 305-a via communication link 330-b and receive communications from network entity 305-a via communication link 320. Figure 3A In the example of , communication link 330 may be an example of an uplink, and communication link 320 may be an example of a downlink. Communication link 330 and communication link 320 may each be as shown in reference Figure 1 An example of a communication link 125 is described.
[0103] In some examples, adjacent communication devices (e.g., at least two of UE 315-a, UE 315-b, and UE 315-c) may concurrently perform half-duplex TDD communication (or full-duplex communication) such that downlink communications received by a first communication device may overlap in time with uplink communications sent by a second communication device (e.g., an adjacent communication device). For example, network entity 305-a and network entity 305-b may concurrently perform full-duplex communication such that uplink communications sent by UE 315-c to network entity 305-b (e.g., a serving cell of UE 315-c) may overlap in time with downlink communications received by UE 315-b from network entity 305-a (e.g., a serving cell of UE 315-b).
[0104] Although UE 315-b and UE 315-c may communicate through different cells, UE 315-b and UE 315-c may be spatially positioned such that uplink communications sent by UE 315-c may interfere with downlink communications received at UE 315-b. For example, uplink communications sent by UE 315-c may cause cross-link interference 325-b (e.g., inter-cell cross-link interference) at UE 315-b. Additionally or alternatively, network entity 305-a may perform full-duplex communication such that uplink communications sent by UE 315-a to network entity 305-a may overlap in time with downlink communications received by UE 315-b from network entity 305-a. In such an example, uplink communications sent by UE 315-a may interfere with downlink communications received at UE 315-b. That is, uplink communications sent by UE 315-a may cause cross-link interference 325-a (e.g., intra-cell cross-link interference) at UE 315-b. In some examples, cross-link interference 325-a and cross-link interference 325-b may degrade downlink communications received at UE 315-b.
[0105] To mitigate (e.g., control) cross-link interference (e.g., in a dynamic TDD scheme), the network may employ a cross-link interference measurement and reporting scheme in which the network may enable UE 315-b (e.g., a downlink UE) to measure cross-link interference from neighboring UE 315 and report the measured interference to the network. For example, the network may configure UE 315-b to measure cross-link interference 325-a (e.g., from UE 315-a) and cross-link interference 325-b (e.g., from UE 315-c), and report the cross-link interference measurements to the network. In some examples of cross-link interference reporting, the network may configure UE 315-a (e.g., an uplink UE) to send a reference signal (e.g., a sounding reference signal (SRS)) to be received and measured by UE 315-b (e.g., a peer, neighbor, or sidelink UE, which may be a downlink UE from network entity 305-a). For example, UE 315-a may transmit an SRS, and UE 315-b may receive and measure the strength of the resulting interference. That is, UE 315-b may measure the interference caused by the concurrent transmission of the SRS by UE 315-a and the downlink transmission by the network entity 305-a. In some examples, UE 315-b (e.g., a downlink UE) may report the cross-link interference measurement as (e.g., based on) a received power measurement, such as a power measurement (e.g., a reference signal received power (RSRP) measurement, such as a synchronization signal reference signal received power (SS-RSRP) measurement) or a signal strength measurement (e.g., a received signal strength indicator (CLI-RSSI) measurement, such as a cross-link interference received signal strength indicator (CLI-RSSI) measurement).
[0106] In some examples, the network (e.g., network entity 305-a) may schedule communications for UE 315-b (or UE 315-a) based on cross-link inference reports. For example, to reduce the impact of cross-link interference 325-a, the network may schedule UE 315-a to send uplink communications on time and frequency resources that are different from the time and frequency resources allocated to UE 315-b to receive downlink communications, thereby reducing (e.g., avoiding) cross-link interference at UE 315-b (e.g., intra-cell cross-link interference). Additionally or alternatively, network entity 305-a and network entity 305-b may coordinate the scheduling of UE 315-b and UE 315-c so that the resources scheduled by UE 315-b for downlink reception may be orthogonal to the resources scheduled by UE 315-c for uplink transmission, thereby reducing (e.g., avoiding) cross-link interference at UE 315-b (e.g., inter-cell cross-link interference). For scenarios, use cases, or examples where a full-duplex network entity concurrently serves downlink UEs and uplink UEs, the downlink UEs may have an increased likelihood of experiencing intra-cell cross-link interference (e.g., relative to inter-cell cross-link interference). For example, relative to UE 315-b, UE 315-b may have an increased likelihood of experiencing intra-cell cross-link interference from UE 315-a.
[0107] In some examples, the network may configure UE 315-b to measure and report cross-link interference via higher layer (e.g., L3, RRC layer) signaling. However, in some examples, UE 315 may move throughout coverage area 310-a or coverage area 310-b (or both), which may result in dynamic changes in cross-link interference that may not be captured by higher layer cross-link interference reports. That is, the latency associated with higher layer cross-link interference reports may not be suitable for scenarios where cross-link interference changes dynamically.
[0108] In some examples of higher layer cross-link interference reporting, the network may configure UE 315-b (e.g., a downlink UE) to periodically (or based on one or more predefined trigger conditions) report cross-link interference measurements. In such an example, the network (e.g., a DU of the network) may obtain (e.g., collect) a cross-link interference report from UE 315-b, which may then be transmitted (e.g., sent, signaled, output) to a CU of the network. In some examples, transmitting information from UE 315-b (e.g., a cross-link interference report) between the CU and the DU may result in increased latency (e.g., additional latency) relative to lower layer (e.g., L1, PHY layer, L2, MAC layer) signaling, where the information may be obtained (e.g., collected) by the DU from UE 315-b. Additionally or alternatively, as part of a higher layer cross-link interference report, UE 315-b may be configured to filter cross-link interference measurements (e.g., perform higher layer filtering). However, in some examples, such filtering may not be suitable for beam switching (e.g., relatively fast beam switching) in response to changes in measured cross-link interference (e.g., over a period of time). For example, configuration (e.g., reconfiguration) of beams used for wireless communication with a network via higher layer signaling (e.g., via RRC configuration) may be inflexible and associated with latency that may not be suitable for scenarios where channel conditions change dynamically, such as due to fluctuating cross-link interference.
[0109] As described herein, some aspects for cross-link interference measurements can provide one or more enhancements to cross-link interference reporting (e.g., an enhanced cross-link interference framework can be provided), thereby increasing cross-link interference mitigation (e.g., processing, control) within the wireless communication system 300. For example, a network can configure UE 315-b to perform cross-link interference measurements and reporting via lower layer signaling. In some examples, the lower layer cross-link interference report can capture the cross-link interference experienced by UE 315-b (e.g., current cross-link interference). Additionally or alternatively, the lower layer cross-link interference report can enable the network to request cross-link interference information (e.g., cross-link interference report) for beam selection with reduced latency (e.g., relatively low latency), such as based on traffic conditions.
[0110] In some examples of lower layer cross-link interference reporting, the network may configure UE 315-b with one or more resources for performing cross-link interference measurements on a reference signal (e.g., SRS) sent by another UE 315 (e.g., UE 315-a). Additionally or alternatively, the network may configure UE 315-b with one or more resources for sending cross-link interference reports (e.g., indicating cross-link interference measurements). The network may configure UE 315-b to measure cross-link interference periodically, semi-persistently, or aperiodically. For example, the network may configure UE 315-b to use periodic resources, semi-persistent resources, or aperiodic resources (e.g., dynamic resources) for cross-link interference reporting. Additionally or alternatively, the network may configure UE 315-b to send cross-link interference reports periodically, semi-persistently, or aperiodically. For example, the network may configure UE 315-b with periodic reporting, semi-persistent reporting, or aperiodic reporting (i.e., with one or more report types) for cross-link interference. In some examples, the network may configure a combination of cross-link interference resources (e.g., periodic resources, semi-persistent resources, or aperiodic resources) and reporting types (e.g., periodic reporting, semi-persistent reporting, or aperiodic reporting) for UE 315-b according to Table 1 below:
[0111]
[0112] According to Table 1, "yes" may indicate that the corresponding combination of resources and reporting types may be suitable (e.g., applicable) for cross-link interference reporting. For example, according to Table 1, the network may configure UE 315-b to use periodic resources and periodic reporting types for cross-link interference reporting. Additionally or alternatively, "no" may indicate that the corresponding combination of resources and reporting types may not be suitable (e.g., may not be applicable) for cross-link interference reporting. For example, according to Table 1, the network may avoid configuring UE 315-b to use semi-persistent resources and periodic reporting types for cross-link interference reporting.
[0113] In some examples, the network may configure resources (e.g., cross-link interference resources) for performing cross-link interference measurements for UE 315-b via control signaling. For example, UE 315-b may receive control signaling 335 indicating a set of cross-link interference resources (e.g., a set of cross-link interference measurement opportunities). The set of cross-link interference resources may include SRS resources (e.g., L1 SRS resources), RSSI resources (e.g., L1 RSSI resources), or both. In some examples, the set of cross-link interference resources may be associated with a set of receive beams (e.g., TCI states, beam configurations, beam configuration states, or beams only). For example, each cross-link interference resource (e.g., of a configured set of cross-link interference resources) may be associated with a TCI state that UE 315-b is to use to determine a receive beam for performing cross-link interference measurements. In some examples, UE 315-b may determine a receive beam for performing cross-link interference measurements on one or more configured cross-link interference resources based on a quasi-co-location (QCL) relationship of an associated TCI state.
[0114] In some examples, the network may indicate a TCI state corresponding to a cross-link interference resource (or multiple cross-link interference resources) via control signaling. For example, the network may configure a TCI state corresponding to one or more periodic cross-link interference resources via RRC signaling (e.g., RRC configuration). Additionally or alternatively, the network may configure a TCI state corresponding to one or more semi-persistent cross-link interference resources via MAC-CE. For example, the network may configure a semi-persistent cross-link interference resource for UE 315-b via control signaling (e.g., via RRC configuration), and may update (e.g., dynamically update) the TCI state associated with each configured cross-link interference resource via MAC-CE (e.g., a MAC-CE indicating that one or more cross-link interference resources or one or more cross-link interference resource sets (e.g., a list) are activated or deactivated). Additionally or alternatively, the network may configure a TCI state corresponding to one or more semi-persistent cross-link interference resources via DCI. For example, the network may configure cross-link interference resources (or cross-link interference resource sets) and corresponding TCI states for UE 315-b via control signaling (e.g., via RRC configuration). In some examples, each cross-link interference resource (or resource set) may be configured with a trigger state, which may be indicated via DCI (e.g., dynamically indicated, updated).
[0115] In some examples, UE 315-b may be unable to switch to a beam associated with a TCI state for a configured resource. In such an example, UE 315-b may determine a default TCI state (e.g., a default beam) for performing cross-link interference measurements based on one or more rules (e.g., one or more rules configured by the network). For example, the network may send an indication (e.g., DCI) for configuring UE 315-b (e.g., non-periodically) to perform cross-link interference reporting on a reference signal sent by another UE 315. In such an example, if the scheduling offset between the resource on which UE 315-b receives the DCI and the resource on which UE 315-b is configured to perform cross-link interference measurements fails to meet a threshold (e.g., fails to exceed the threshold, is relatively shorter than the threshold), UE 315-b may determine to use a default TCI state (e.g., based on one or more rules) to perform cross-link interference measurements.
[0116] UE 315-b may generate a cross-link interference report 340 indicating a cross-link interference measurement of at least one receive beam in the set of receive beams. In some examples, UE 315-b may generate cross-link interference report 340 based on control signaling 335 and a trigger for cross-link interference measurement. UE 315-b may report the measured cross-link interference to network entity 305-a. For example, UE 315-b may send cross-link interference report 340 (e.g., indicating the measured cross-link interference) to network entity 305-a.
[0117] In some examples, UE 315-b may determine to send a cross-link interference report based on one or more rules (e.g., events). For example, if one or more cross-link interference measurements meet a threshold, UE 315-b may send an event-triggered report. Additionally or alternatively, the network may configure UE 315-b with an activation mechanism for semi-persistent cross-link interference reporting. For example, the network may configure UE 315 (e.g., via RRC signaling) semi-persistent resources (e.g., one or more semi-persistent resource lists) for reporting cross-link interference measurements. In such an example, the network may activate (or deactivate) the configured resources via MAC-CE.
[0118] Figure 3B An example of a MAC-CE 301 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is illustrated. Figure 3B In the example of , MAC-CE 301 may be transmitted between one or more of UE 315 and one or more of network entities 305, as shown in reference Figure 3AFor example, the network entity 305-a may activate (or deactivate) resources configured for cross-link interference reporting via MAC-CE 301. In some examples, by activating resources (e.g., semi-persistent resources) via MAC-CE 301, the network may trigger UE 315-b to send a cross-link interference report (e.g., cross-link interference report 340).
[0119] In some examples, the MAC-CE 301 may include an activation or deactivation (A / D) field (e.g., A / D field 350), which may indicate to the UE 315-b whether to activate or deactivate semi-persistent resources (e.g., semi-persistent cross-link interference resources) configured for the UE 315-b (e.g., via RRC signaling). In some examples, the A / D field 350 may be set to 1 to indicate activation, and may be set to 0 (e.g., or another value different from 1) to indicate deactivation. Additionally or alternatively, the MAC-CE 301 may include a serving cell identifier field (e.g., serving cell ID field 355), which may indicate an identifier of a serving cell that the MAC-CE 301 may apply. In some examples, the length of the serving cell ID field 355 may be five bits. Additionally or alternatively, the MAC-CE 301 may include a BWP ID field 360, which may indicate a downlink field that the MAC-CE 301 may apply. For example, the BWP ID field 360 may indicate a bandwidth part to be applied as a code point (e.g., of a DCI bandwidth part indicator field) to identify the bandwidth part in which the indicated resources (e.g., frequency resources) may be located. In some examples, the BWP ID field 360 may be two bits.
[0120] Additionally or alternatively, the MAC-CE 301 may include a semi-persistent cross-link interference resource set ID field (e.g., the SP CLI RS resource set ID field 365), which may include an index of a cross-link interference resource set (e.g., a cross-link interference resource set), which includes semi-persistent cross-link interference resources that can be activated or deactivated by the MAC-CE 301 (e.g., based on the value of the A / D field 350). In some examples, the cross-link interference resource set may be a non-zero power cross-link interference resource set including semi-persistent non-zero power cross-link interference resources. In some examples, each cross-link interference resource set (e.g., corresponding to the index provided by the SP CLI resource set ID field 365) may be configured at the UE 315-b via a higher layer parameter (e.g., via an NZP-CLI-RS-ResourceSet information element (IE)). For example, the parameter may indicate a resource set (e.g., a non-zero power cross-link interference resource), a corresponding identifier of the resource, and one or more set-specific parameters. In some examples, the semi-persistent cross-link interference resource set identifier field (e.g., the SP CLI-RS resource set ID field 365) may include one or more TCI state ID fields 370 (e.g., TCI state ID field 370-a and TCI state ID field 370-b). Each TCI state ID field 370 may include an identifier of a QCL source that may be used as a resource within a cross-link interference resource set (e.g., corresponding to an index provided by the SP CLI resource set ID field 365). For example, the TCI state ID field 370-a may indicate a first TCI state for a first resource of a cross-link interference resource set, while the TCI state ID field 370-b may indicate a first TCI state for an Nth resource of a cross-link interference resource set. It should be understood that the names of the IEs and fields described herein may vary based on the specific implementation of one or more devices (e.g., the UE 315, the network entity 305, or both), and the examples described herein should not be considered to be limited to the scope covered by the claims or the present disclosure.
[0121] Figure 4 An example of a timing diagram 400 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 400 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 300. For example, the timing diagram 400 may be implemented by a UE and a network entity, which may be as described in reference to Figure 1 and Figure 2 and Figure 3A Examples of corresponding devices described. Figure 4In the example of FIG. 1 , the network entity may be a CU 160, a DU 165 or a RU 170, a base station 140, an IAB node 104, a transmission-reception point or one or more other network nodes, as shown in FIG. Figure 1 , Figure 2 and Figure 3A The timing diagram 400 may include features for improving communications between a UE and a network, among other advantages.
[0122] like Figure 4 As illustrated in the example of , a network (e.g., one or more network entities) may configure a communication device (e.g., UE) to perform cross-link interference measurements and reports via lower layer (e.g., L1, PHY layer, L2, MAC layer) signaling. In some examples, the network may configure the UE to perform cross-link interference measurements and reports aperiodically, for example, via dynamic signaling (e.g., DCI). For example, the network may send a DCI 405 indicating (e.g., triggering) the UE to measure and report cross-link interference. In some examples, the DCI 405 may indicate the UE to measure and report cross-link interference via a field included in the DCI 405 (such as a CLI trigger status field). For example, the CLI trigger status field may indicate an index of a trigger state for a cross-link interference resource that can be configured (e.g., pre-configured) for the UE (e.g., via RRC signaling). In some examples, each trigger state may indicate one or more cross-link interference resources (e.g., cross-link interference resources 410) on which the UE can perform cross-link interference measurements. Additionally or alternatively, the CLI trigger status field may indicate a resource type (e.g., a periodic resource, a semi-persistent resource, or an aperiodic resource) that may be used by the UE to report cross-link interference measurements. For example, the network may indicate one or more frequency domain resources, such as a physical uplink shared channel (PUSCH) resource. In some examples, the indicated PUSCH resource (e.g., PUSCH resource 415) may be periodic, semi-persistent, or aperiodic. In some examples, multiple trigger states for performing cross-link interference measurements may be configured at the UE (e.g., via RRC signaling), and the DCI 405 may indicate an index of a trigger state to be used by the UE (e.g., via the CLI trigger status field), thereby activating cross-link interference reporting.
[0123] In some examples, the network may indicate a time offset 425 between the DCI 405 and the cross-link interference resource 410. Additionally or alternatively, the network may indicate another time offset (not shown) between the cross-link interference resource 410 and the PUSCH resource 415 (or other resource on which the cross-link interference may be reported to the network). In some examples, the cross-link interference resource 410 may be associated with a TCI state. For example, the network may indicate a TCI state corresponding to each cross-link interference resource 410 configured for the UE. In such an example, the UE may use the TCI state (e.g., a QCL relationship associated with the TCI state) to determine (e.g., identify, select) a beam for performing cross-link interference measurements on the corresponding cross-link interference resource 410. For example, in response to receiving an indication to perform cross-link interference measurements on the cross-link interference resource 410 (e.g., via the DCI 405), the UE may switch to a beam (e.g., a receive beam) associated with the TCI state configured for the cross-link interference resource 410 (e.g., to perform cross-link interference measurements).
[0124] However, in some examples, the UE may not be able to switch to a beam associated with the TCI state of the configured resource (e.g., the cross-link interference resource 410). For example, if the time offset 425 between the DCI 405 and the cross-link interference resource 410 (e.g., the triggered aperiodic cross-link interference resource) fails to meet (e.g., fails to exceed) the aperiodic cross-link interference beam switching delay threshold (e.g., threshold 430), the UE may not be able to switch to the beam associated with the TCI state of the cross-link interference resource 410. In some examples, the threshold 430 may be based on one or more capabilities of the UE (e.g., UE capabilities). For example, the UE may send a message such as UE capability signaling to the network indicating a threshold offset (e.g., threshold 430) of the offset between the DCI 405 and the timing indicated by the DCI 405 (e.g., the cross-link interference resource 410). Additionally or alternatively, the threshold may have an increased delay, for example if DCI 405 (e.g., a DCI that triggers cross-link interference measurement and reporting) is associated with a subcarrier spacing difference from a cross-link interference resource 410 (e.g., a non-periodic cross-link interference resource triggered by DCI 405).
[0125] In some examples, if the time offset 425 fails to meet (e.g., fails to exceed) the threshold 430, the UE may determine a default receive beam (e.g., a default TCI state) for performing cross-link interference measurements based on one or more rules (e.g., configured by the network). In some examples, the rule for determining the default receive beam (e.g., a non-periodic cross-link interference default beam rule) may be the same rule as the rule that may be used to determine a default beam for performing channel state information measurements (e.g., for performing channel state information measurements on non-periodic channel state information reference signal resources). In some examples, the UE may be configured to operate in a single transmit-receive point mode. In such an example, if the non-periodic cross-link interference resource (e.g., the cross-link interference resource 410) overlaps (e.g., in time, frequency, or both time and frequency) with a downlink transmission scheduled for the UE (e.g., a known downlink signal), the UE may determine the receive beam based on the QCL relationship (e.g., assumption) of the scheduled downlink transmission. Additionally or alternatively, the UE may determine a receive beam based on a QCL relationship (eg, assumption) associated with a control resource set, such as a control resource set associated with a relatively lowest identifier in a relatively later monitoring time slot.
[0126] In some examples, the UE may be configured to operate in a multiple transmit-receive point (mTRP) mode (e.g., a single DCI multiple transmit-receive point mode (sDCI mTRP) or a multiple DCI multiple transmit-receive point mode (mDCI mTRP)), a single frequency network (SFN) mode (e.g., associated with a single frequency network control resource set (CORESET)), or a cross-carrier scheduling mode (e.g., associated with cross-component carrier (cross-CC) scheduling). In some examples, the UE may determine a receive beam based on the same rules that may be used to determine a default beam for performing channel state information measurements (e.g., for performing channel state information measurements on non-periodic channel state information reference signal resources).
[0127] In some examples, if the UE is configured to operate in a single DCI multiple transmit-receive point mode, the UE may determine a receive beam based on a TCI state (e.g., a QCL relationship associated with the TCI state) identified by a code point including multiple (e.g., two) TCI states (e.g., a TCI state code point associated with a relatively lowest identifier). That is, for a single DCI multiple transmit-receive point operation, the UE may determine a receive beam based on a TCI code point having a relatively lowest identifier value and identifying multiple TCI states corresponding to multiple transmit-receive points.
[0128] Additionally or alternatively, if the UE is configured to operate in a multi-DCI multi-transmit-receive point mode, the UE may determine a receive beam (e.g., via CORESETpool IE) based on a TCI state (e.g., a QCL relationship associated with the TCI state) corresponding to each of a plurality of control source set pools (e.g., a set or group of control resource sets) configured for the UE. That is, for multiple DCI multi-transmit-receive point operations, the UE may determine a receive beam based on a TCI state associated with a most recently (e.g., most recently) monitored control resource set for each control resource set pool configured at the UE.
[0129] Additionally or alternatively, if the UE is configured to operate in a single frequency network mode (e.g., associated with a single frequency network control resource set), the UE may determine the receive beam based on a TCI state (e.g., a QCL relationship associated with the TCI state) identified by a code point (e.g., a single frequency network TCI state code point associated with a relatively lowest identifier). Additionally or alternatively, if the UE is configured to operate in a cross-carrier scheduling mode, the UE may determine the receive beam based on a TCI state (e.g., a QCL relationship associated with the TCI state) identified by a code point (e.g., a TCI state code point associated with a relatively lowest identifier). That is, for single frequency network operation or cross-carrier scheduling operation (or both), the UE may determine the receive beam based on the TCI code point with the relatively lowest identifier value. In some examples, by configuring the UE to perform cross-link interference measurements and reporting aperiodically via lower layer signaling, the network can provide one or more enhancements to techniques for cross-link interference measurements and reporting, as well as other benefits.
[0130] Figure 5 An example of a timing diagram 500 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 500 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 300. For example, the timing diagram 500 may be implemented by a UE and a network entity, which may be as described in reference to Figure 1 and Figure 2 and Figure 3A Examples of corresponding devices described. Figure 5 In the example of , the network entity may be an example of such a network entity, which may be an example of a CU 160, a DU 165 or a RU 170, a base station 140, an IAB node 104, a transmission-reception point or one or more other network nodes, as shown in reference Figure 1 , Figure 2 and Figure 3ATiming diagram 500 may include features for improving communications between a UE and a network, among other advantages.
[0131] In some examples, a network (e.g., one or more network entities) may configure a communication device (e.g., a UE) to semi-persistently perform cross-link interference measurements and reports. In such examples, the network may configure the UE to send a cross-link interference report (e.g., a semi-persistent cross-link interference report) on a physical uplink channel (e.g., a physical uplink control channel (PUCCH) or a PUSCH). For example, Figure 5 As illustrated in the example of , the network may instruct (e.g., trigger) the UE to perform semi-persistent cross-link interference reporting on one or more PUSCH resources 515 (e.g., PUSCH resource 515-a or PUSCH resource 515-b) via DCI 505. That is, DCI 505 may trigger (e.g., activate) the UE's semi-persistent cross-link interference reporting. In some examples, the cross-link interference report (e.g., semi-persistent cross-link interference report) may be activated by a DCI, which may be scrambled by a radio network temporary identifier (RNTI) configured at the UE for cross-link interference reporting (e.g., indicated to the UE via an SP-CLI-RNTI IE). For example, a semi-persistent cross-link interference request field (e.g., identified by a specific field value) may be included in the DCI 505 (e.g., activating the DCI), and the DCI 505 may be scrambled by the RNTI configured at the UE for cross-link interference reporting. In such an example, the semi-persistent cross-link interference request field can activate one or more semi-persistent cross-link interference trigger states of multiple semi-persistent cross-link interference trigger states that can be configured for the UE. For example, the semi-persistent cross-link interference request field can activate one or more semi-persistent cross-link interference trigger states associated with (e.g., linked to) parameters (e.g., higher layer parameters of the CLI-ReportConfig IE) that can indicate (e.g., specify) corresponding semi-persistent cross-link interference resources (e.g., cross-link interference resources 510-a and cross-link interference resources 510-b) and reporting configurations (e.g., cross-link interference reporting configurations).
[0132] Additionally or alternatively, the network may activate (e.g., trigger) semi-persistent cross-link interference reporting on one or more PUSCH resources 515 (e.g., PUSCH resource 515-a or PUSCH resource 515-b) by configuring the UE with a semi-persistent cross-link interference trigger state in the same list as that which may be used to indicate a semi-persistent channel state information trigger state. That is, the network may use common signaling to trigger the UE to perform semi-persistent cross-link interference reporting and channel state information reporting. In such an example, the DCI 505 (e.g., the triggering DCI) may be scrambled using the same RNTI that may be used to scramble the DCI used to trigger the channel state information report.
[0133] In some examples, if DCI 505 (e.g., triggering DCI) is scrambled using the same RNTI as the DCI that can be used to scramble the triggered channel state information report, a semi-persistent cross-link interference trigger state can be indicated via the same field that can be used to indicate the semi-persistent channel state information trigger state. For example, a common trigger state field (e.g., corresponding to the same trigger state list configured for the UE) can be used to indicate both the semi-persistent cross-link interference trigger state and the semi-persistent channel state information trigger state. In other examples, the trigger state field used to indicate the semi-persistent cross-link interference trigger state can be different from the trigger state field used to indicate the semi-persistent channel state information trigger state. For example, DCI 505 can include a semi-persistent cross-link interference trigger state field and a semi-persistent channel state information trigger state field (e.g., which can correspond to the same trigger state list configured at the UE). Additionally or alternatively, if DCI 505 (e.g., triggering DCI) is scrambled using the same RNTI as that used to scramble the DCI that triggers the channel state information report, the semi-persistent cross-link interference trigger state can be indicated via a trigger state field that is different from the trigger state field used to indicate the semi-persistent channel state information trigger state. In some examples, by configuring the UE to semi-persistently perform cross-link interference measurements and reporting via lower layer signaling, the network can provide one or more enhancements to techniques for cross-link interference measurements and reporting, as well as other benefits.
[0134] Figure 6 An example of a timing diagram 600 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 600 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 300. For example, the timing diagram 600 may be implemented by a UE and a network entity, which may be as described in reference to Figure 1 and Figure 3A Examples of corresponding devices described. Figure 6 In the example of FIG. 1 , the network entity may be a CU 160, a DU 165 or a RU 170, a base station 140, an IAB node 104, a transmission-reception point or one or more other network nodes, as shown in FIG. Figure 1 The timing diagram 600 may include features for improving communications between a UE and a network, among other advantages.
[0135] like Figure 6 As illustrated in the example of , the network may instruct (e.g., trigger) the UE to perform semi-persistent cross-link interference reporting on one or more PUCCH resources 615 (e.g., PUCCH resource 615-a or PUCCH resource 615-b) via MAC-CE 605. For example, MAC-CE 605 (e.g., activating MAC-CE) may activate (or deactivate) a set of cross-link interference reporting configuration identifiers (e.g., indicated via CLI-ReportConfig IE) that may be suitable for (e.g., applicable to) semi-persistent cross-link interference reporting. In some examples, such cross-link interference reporting may occur (e.g., take effect) after (e.g., approximately 3 ms later) an acknowledgment message (e.g., ACK 606) sent by the UE (e.g., in response to receiving MAC-CE 605). For example, cross-link interference resources (e.g., cross-link interference resource 610-a and cross-link interference resource 610-b) may be activated by MAC-CE 605 and may occur after a time offset 620, which may be measured from the end time of the time slot including ACK606.
[0136] In some examples, the network may activate semi-persistent cross-link interference reporting on the PUCCH via a MAC-CE dedicated to cross-link interference reporting. For example, MAC-CE 605 may be different from the MAC-CE used to activate semi-persistent channel state information reporting. That is, the MAC-CE type used to trigger the cross-link interference report may be different from the MAC-CE type used to trigger the channel state information report. Additionally or alternatively, the network may activate semi-persistent cross-link interference reporting on the PUCCH via the same MAC-CE that may be used to activate the semi-persistent channel state information report. In such an example, the configuration for configuring the parameters for cross-link interference reporting for the UE (e.g., indicated via CLI-ReportConfig IE) and the configuration for configuring the parameters for channel state information reporting for the UE (e.g., indicated via CSI-ReportConfig IE) may share the same identifier space. For example, resources for semi-persistent cross-link interference reporting and resources for semi-persistent channel state information reporting may be configured via the same resource set identifier list. That is, the MAC-CE 605 may include a resource set identifier field (e.g., a semi-persistent cross-link interference resource set identifier field or a semi-persistent channel state information reference signal resource set identifier field), which may include an index of a resource set (e.g., one of multiple resource sets included in a list configured for the UE), and the resource set may correspond to a cross-link interference resource set (e.g., NZP-CLI-ResourceSet IE), a channel state information reference signal resource set (e.g., NZP-CSI-RS-ResourceSet IE), or a channel state information interference measurement resource set (e.g., CSI-IM-ResourceSet IE).
[0137] The cross-link interference resource set can be as shown in reference Figure 3B Examples of cross-link interference resource sets described herein. For example, a cross-link interference resource set may include resources for performing cross-link interference measurements (e.g., non-zero power cross-link interference resources). Additionally or alternatively, a channel state information reference signal resource set may be a reference signal resource set. Figure 3B Examples of channel state information reference signal resource sets described herein. For example, the channel state information reference signal resource set may include non-zero power channel state information reference signal resources. Additionally or alternatively, the channel state information interference measurement resource set may be as referenced Figure 3B Examples of described channel state information interference measurement resource sets. For example, a channel state information interference measurement resource set may include channel state information interference measurement resources.
[0138] Figure 7An example of a process flow 700 that supports aspects for cross-link interference measurement according to one or more aspects of the present disclosure is illustrated. The process flow 700 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 300. For example, the process flow 700 may include a network entity 705 and one or more UEs 715 (e.g., UE 715-a and UE 715-b), which may be as described in reference to Figure 1 , Figure 2 and Figure 3A Examples of corresponding devices described herein. Process flow 700 may be implemented by network entity 705, UE 715, or both. In the following description of process flow 700, operations between network entity 705 and UE 715 may occur in a different order or at a different time than shown. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700. Process flow 700 may include features for improving communication between UE 715 and the network, as well as other advantages.
[0139] In some examples, UE 715-a can be configured to send cross-link interference reports based on one or more rules (e.g., events). That is, a cross-link interference report (such as a higher layer cross-link interference report or a lower layer cross-link interference report) can be event triggered. For higher layer cross-link interference reports (e.g., L3 cross-link interference reports), UE 715-a can be configured with resources (e.g., periodic resources) for performing cross-link interference measurements on reference signals (e.g., SRS) sent from other UEs. In such an example, if the value of the measurement metric (e.g., measured cross-link interference metric, RSRP metric, RSSI metric) of a resource in the resource list meets a threshold (e.g., exceeds a threshold, fails to exceed a threshold), UE 715-a can determine to report the measured cross-link interference metric.
[0140] In some examples, UE 715-a can be triggered to send a report (or multiple reports) indicating multiple cross-link interference metrics (e.g., corresponding to multiple cross-link interference measurements) collected over a period of time. In some examples, the duration can start based on satisfying an entry condition: if the measured cross-link interference metric satisfies a threshold (e.g., exceeds a threshold, fails to exceed a threshold), the entry condition can be satisfied (e.g., the report can be triggered to start). In some examples, UE 715-a can consider the hysteresis of the system before determining whether the cross-link interference metric satisfies the threshold. For example, UE 715-a can subtract a value corresponding to one or more previous measurements (e.g., hysteresis) from the cross-link interference metric before comparing the cross-link interference metric to the threshold. In some examples, the duration can end based on satisfying an exit (e.g., exit) condition: if the measured cross-link interference metric fails to satisfy a threshold (e.g., fails to exceed a threshold), the exit condition can be satisfied (e.g., the report can be triggered to end). In some examples, UE 715-a can consider the hysteresis of the system before determining whether the cross-link interference metric satisfies the threshold. For example, UE 715-a may add a value corresponding to one or more previous measurements (e.g., a hysteresis) to the cross-link interference metric before comparing the cross-link interference metric to a threshold.
[0141] In some examples, the network may configure one or more parameters for cross-link interference reporting for UE 715-a. For example, the network may configure a timeToTrigger parameter for UE 715-a that indicates the duration between the time when the entry condition can be met and the time when the cross-link interference report can be sent. Additionally or alternatively, the network may configure a reportedMetric parameter (e.g., RSRP, RSSI) for UE 715-a indicating a cross-link interference metric to be indicated in a cross-link interference report. Additionally or alternatively, the network may configure a maxReportCLI parameter for UE 715-a indicating the number of cross-link interference measurements (or cross-link interference metrics) to be indicated via a cross-link interference report. In some examples, if the number of cross-link measurements that meet a threshold is relatively higher than the value of the maxReportCLI parameter, UE 715-a may determine the number of cross-link measurements reported equal to the value of the maxReportCLI parameter. In some examples, UE 715 - a may be configured to select a number of cross-link interference measurements (e.g., to be indicated via a cross-link interference report) based on a corresponding value of each cross-link interference measurement (e.g., satisfying a threshold).
[0142] Additionally or alternatively, the network may configure UE 715-a with a reportInterval parameter indicating the periodicity with which cross-link interference reports may be sent by UE 715-a (e.g., during a duration between when an entry condition is satisfied and when a leave condition is satisfied). Additionally or alternatively, the network may configure UE 715-a with a reportAmount parameter indicating the number of reports that may be sent (e.g., during a duration between when an entry condition is satisfied and when a leave condition is satisfied). Additionally or alternatively, the network may configure UE 715-a with a reportOnLeave metric indicating whether a report may be sent in response to a leave condition being satisfied.
[0143] In some examples of lower layer cross-link interference reporting (e.g., L2 cross-link interference reporting, L1 cross-link interference reporting), UE 715-b may be configured with cross-link interference resources (e.g., periodic resources, semi-persistent resources, non-periodic resources) for event-triggered cross-link interference reporting. That is, the network may configure one or more parameters for event-triggered cross-link interference reporting for UE 715-a. In some examples, the parameters for event-triggered cross-link interference reporting may be common to both cross-link interference reporting and channel state information reporting. For example, the network may configure UE 715-a with parameters indicating that UE 715-a reports a cross-link interference metric via a cross-link interference report, such as an RSRP metric (e.g., indicated via an L1-SRS-RSRP IE) or an RSSI metric (e.g., indicated via an L1-CLI-RSSI IE).
[0144] like Figure 7 As illustrated in the example of , UE 715-a can report cross-link interference based on a trigger. For example, UE 715-a can be configured with resources (e.g., periodic resources, semi-persistent resources, or non-periodic resources) for performing cross-link interference measurements on reference signals (e.g., SRS) sent from other UEs (such as UE 715-b). In such an example, if the value of the measured cross-link interference (e.g., the value of the cross-link interference metric) meets a threshold (e.g., exceeds the threshold, fails to exceed the threshold), UE 715-a can determine to report the cross-link interference measurement. For example, at 720, UE 715-a can perform cross-link interference measurements on reference signals sent from UE 715-b. The value of the cross-link interference metric corresponding to the cross-link interference measurement can meet the threshold (e.g., exceeds the threshold, fails to exceed the threshold). Therefore, at 725, a cross-link interference report can be triggered for UE 715-a.
[0145] In some examples (e.g., once triggered), UE 715-a may send a cross-link interference report via lower layer signaling. For example, UE 715-a may send a cross-link interference report as uplink control information on a periodic or semi-persistent resource (e.g., a periodic or semi-persistent resource dedicated to cross-link interference reporting). In some examples, if UE 715-a reports a cross-link interference report as uplink control information, UE 715-a may determine whether to send the cross-link interference report together with (or not with) the channel state information report, for example, based on the respective priorities of the cross-link interference report and the channel state information report. Additionally or alternatively, UE 715-a may send a cross-link interference report via MAC-CE in an uplink grant requested by UE 715-a via a scheduling request (e.g., on resources indicated via the uplink grant). For example, at 730, in response to triggering a cross-link interference report, UE 715-a may send a scheduling request to network entity 705. At 735, UE 715-a may receive uplink grant scheduling resources on which UE 715-a may send a report indicating a cross-link interference metric.
[0146] At 745, the network entity 705 may perform one or more cross-link interference mitigation techniques based on receiving a cross-link interference report (e.g., via a MAC-CE sent at 740). For example, the network entity 705 may instruct UE 715-a (or UE 715-b) to perform beam switching so that the cross-link interference experienced by UE 715-a (e.g., due to uplink transmissions from UE 715-b) can be reduced. Additionally or alternatively, the network may schedule downlink transmissions of UE 715-a and uplink transmissions of UE 715-b so that the downlink transmissions and the uplink transmissions may be non-overlapping, thereby reducing cross-link interference at UE 715-b. In some examples, the network entity 705 may adjust TDM operations performed at UE 715-a (or UE 715-b) so that the cross-link interference at UE 715-a can be reduced.
[0147] Figure 8 An example of a process flow 800 that supports aspects for cross-link interference measurement according to one or more aspects of the present disclosure is illustrated. The process flow 800 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 300. For example, the process flow 800 may include a network entity 805 and a UE 815, which may be reference entities. Figure 1 and Figure 3AExamples of corresponding devices described. Process flow 800 can be implemented by network entity 805, UE 815, or both. In the following description of process flow 800, operations between network entity 805 and UE 815 may occur in a different order or at a different time than shown. Some operations may also be omitted from process flow 800, and other operations may be added to process flow 800. Process flow 800 may include features for improving communication between UE 815 and the network, as well as other advantages.
[0148] At 820, UE 815 may receive control signaling indicating a set of cross-link interference measurement opportunities (e.g., cross-link interference resources) and a set of receive beams associated with the set of cross-link interference measurement opportunities. In some examples, the trigger may be as described in reference to FIG. Figure 5 An example of a trigger described. For example, the cross-link interference measurement opportunity may be a periodic cross-link interference resource. Therefore, UE 815 may be triggered to send a cross-link interference report based on the cross-link interference opportunity included in the group. Additionally or alternatively, the cross-link interference measurement opportunity may be an aperiodic cross-link interference resource indicated to UE 815 via DCI. In such an example, UE 815 may be triggered to send a cross-link interference report based on DCI. Additionally or alternatively, the cross-link interference measurement opportunity may be a semi-persistent cross-link interference resource (e.g., configured by the network for UE 815) indicated to UE 815 via DCI scrambled with an RNTI for cross-link interference reporting. In such an example, UE 815 may be triggered to send a cross-link interference report based on DCI. Additionally or alternatively, the cross-link interference measurement opportunity may be a semi-persistent cross-link interference resource indicated to UE 815 via MAC-CE. In such an example, UE 815 may be triggered to send a cross-link interference report based on MAC-CE.
[0149] At 825, UE 815 may generate a cross-link interference report based on the control signaling and the triggering of the cross-link interference measurement. In some examples, the cross-link interference report may indicate the cross-link interference measurement of at least one receive beam in the set of receive beams. At 830, UE 815 may send a cross-link interference report to network entity 805. In some examples, UE 815 may send a cross-link interference report on an uplink control channel (e.g., PUCCH), for example via an uplink control information message. Additionally or alternatively, UE 815 may send a cross-link interference report on an uplink shared channel (e.g., PUSCH). For example, UE 815 may send a cross-link interference report on a physical uplink shared channel in response to sending a scheduling request.
[0150] Fig. 9 A block diagram 900 of a device 905 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0151] The receiver 910 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to aspects for cross-link interference measurements), user data, control information, or any combination thereof. The information may be communicated to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.
[0152] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to aspects for cross-link interference measurements), user data, control information, or any combination thereof. In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.
[0153] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of aspects for cross-link interference measurement as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.
[0154] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). 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, configured to or otherwise support 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 of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0155] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, 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 920, the receiver 910, the transmitter 915, 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).
[0156] In some examples, the communication manager 920 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 can receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
[0157] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a UE (e.g., device 905). For example, the communication manager 920 may be configured to or otherwise support components for the following operations: receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities. The communication manager 920 may be configured to or otherwise support components for the following operations: based on the control signaling and the triggering of the cross-link interference measurement, generating a cross-link interference report indicating a cross-link interference measurement for at least one receive beam in the set of receive beams. The communication manager 920 may be configured to or otherwise support components for sending a cross-link interference report to a network entity.
[0158] By including or configuring a communications manager 920 according to examples as described herein, a device 905 (e.g., a processor controlling or otherwise coupled to a receiver 910, a transmitter 915, a communications manager 920, or a combination thereof) may support techniques for reducing processing and more efficiently utilizing communications resources.
[0159] Fig.10A block diagram 1000 of a device 1005 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0160] The receiver 1010 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to aspects for cross-link interference measurements), user data, control information, or any combination thereof. The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a set of multiple antennas.
[0161] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to aspects for cross-link interference measurements), user data, control information, or any combination thereof. In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a set of multiple antennas.
[0162] Device 1005 or its various components may be examples of components for performing various aspects of aspects for cross-link interference measurement as described herein. For example, communication manager 1020 may include measurement opportunity indication component 1025, measurement component 1030, reporting component 1035, or any combination thereof. Communication manager 1020 may be an example of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated with receiver 1010, transmitter 1015, or both in combination to obtain information, output information, or perform various other operations as described herein.
[0163] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a UE (e.g., device 1005). The measurement opportunity indication component 1025 may be configured to or otherwise support components for the following operations: receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities. The measurement component 1030 may be configured to or otherwise support components for the following operations: based on the control signaling and the triggering of the cross-link interference measurement, generating a cross-link interference report indicating a cross-link interference measurement for at least one receive beam in the set of receive beams. The reporting component 1035 may be configured to or otherwise support components for sending a cross-link interference report to a network entity.
[0164] Fig.11 A block diagram 1100 of a communication manager 1120 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of aspects for cross-link interference measurement as described herein. For example, the communication manager 1120 may include a measurement opportunity indication component 1125, a measurement component 1130, a reporting component 1135, a threshold offset component 1140, a QCL relationship component 1145, a receive beam component 1150, an acknowledgment message component 1155, an uplink control information message component 1160, a scheduling request component 1165, an uplink resource indication component 1170, or any combination thereof. Each of these components may communicate directly or indirectly (e.g., via one or more buses) with each other.
[0165] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a UE. The measurement opportunity indication component 1125 may be configured to or otherwise support a component for receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities. The measurement component 1130 may be configured to or otherwise support a component for the following operations: based on the control signaling and the triggering of the cross-link interference measurement, generating a cross-link interference report indicating a cross-link interference measurement for at least one receive beam in the set of receive beams. The reporting component 1135 may be configured to or otherwise support a component for sending a cross-link interference report to a network entity.
[0166] In some examples, measurement component 1130 may be configured as or otherwise support components for performing a cross-link interference measurement procedure at a timing in the set of cross-link interference measurement timings to generate a cross-link interference measurement using a receive beam in the set of receive beams corresponding to the timing, wherein the trigger includes the timing.
[0167] In some examples, the measurement opportunity indication component 1125 may be configured to or otherwise support a component for: receiving a DCI message indicating a timing in the set of cross-link interference measurement opportunities and a receive beam corresponding to the timing. In some examples, the measurement component 1130 may be configured to or otherwise support a component for: performing a cross-link interference measurement procedure at the timing to generate a cross-link interference measurement using a receive beam, wherein the trigger includes the timing indicated by the DCI message. In some examples, the DCI message is scrambled with an RNTI that indicates the UE to generate a cross-link interference measurement, and the cross-link interference report is sent on an uplink shared channel.
[0168] In some examples, to support receiving control signaling indicating the set of cross-link interference measurement opportunities and the set of receive beams associated with the set of cross-link interference measurement opportunities, the measurement opportunity indication component 1125 may be configured as or otherwise supports components for the following operations: receiving a MAC-CE indicating the set of cross-link interference measurement opportunities and the set of receive beams; and the method also includes. In some examples, to support receiving control signaling indicating the set of cross-link interference measurement opportunities and the set of receive beams associated with the set of cross-link interference measurement opportunities, the measurement component 1130 may be configured as or otherwise supports components for the following operations: performing a cross-link interference measurement procedure at an opportunity in the set of cross-link interference measurement opportunities to generate a cross-link interference measurement using a receive beam in the set of receive beams corresponding to the opportunity, wherein the trigger includes the opportunity indicated by the MAC-CE.
[0169] In some examples, confirmation message component 1155 may be configured as or otherwise support components for the following operations: sending a confirmation message in response to a MAC-CE, wherein the cross-link interference report is sent on an uplink control channel according to at least an offset from sending the confirmation message. In some examples, measurement component 1130 may be configured as or otherwise support components for the following operations: performing a cross-link interference measurement procedure to generate a cross-link interference measurement based on the UE detecting an event, wherein the event includes the trigger. In some examples, to support sending a cross-link interference report, uplink control information message component 1160 may be configured as or otherwise support components for the following operations: sending an uplink control information message including a cross-link interference report on an uplink control channel.
[0170] In some examples, scheduling request component 1165 may be configured or otherwise support means for sending a scheduling request to a network entity. In some examples, uplink resource indication component 1170 may be configured or otherwise support means for: receiving control signaling indicating uplink resources of a shared channel in response to the scheduling request, wherein sending the cross-link interference report includes sending a MAC-CE including the cross-link interference report on the uplink resources of the shared channel.
[0171] In some examples, at least one receive beam includes a default receive beam, and the threshold offset component 1140 may be configured as or otherwise support a component for selecting a default receive beam for cross-link interference measurement based on an offset between a DCI message and a timing indicated by a DCI message for cross-link interference measurement being less than a threshold offset, wherein the default receive beam is different from a second receive beam in the set of receive beams associated with the timing.
[0172] In some examples, threshold offset component 1140 may be configured as or otherwise support means for sending UE capability signaling indicating a threshold offset to a network entity. In some examples, the threshold offset includes a first offset value and a second offset value. In some examples, the second offset value is based on the DCI message and whether the opportunity indicated by the DCI message is associated with the same subcarrier spacing.
[0173] In some examples, QCL relation component 1145 may be configured to or otherwise support means for identifying a QCL relation for a downlink signal received at a UE, wherein a network entity communicates with the UE via a single transmit-receive point. In some examples, measurement component 1130 may be configured to or otherwise support means for performing a measurement procedure at an opportunity in the set of cross-link interference measurement opportunities to generate a cross-link interference measurement based on the downlink signal overlapping the opportunity using the QCL relation.
[0174] In some examples, QCL relation component 1145 may be configured to or otherwise support means for identifying a first QCL relation for a downlink signal received at a UE, wherein a network entity communicates with the UE via a single transmit-receive point. In some examples, measurement component 1130 may be configured to or otherwise support means for performing a measurement procedure at an opportunity in the set of cross-link interference measurement opportunities to generate a cross-link interference measurement based on the downlink signal not overlapping the opportunity using a second QCL relation associated with a lowest control resource set identifier.
[0175] In some examples, for a single DCI message operation having a set of multiple transmit-receive points, receive beam component 1150 may be configured as or otherwise support components for selecting at least one receive beam from the set of receive beams for cross-link interference measurement based on a transmit configuration indicator code point having a lowest identifier value and identifying a set of multiple transmit configuration indicator states corresponding to the set of multiple transmit-receive points.
[0176] In some examples, for multiple DCI message operations for a set of multiple transmit-receive points, receive beam component 1150 may be configured as or otherwise support components for selecting at least one receive beam in the set of receive beams for cross-link interference measurement based on a transmit configuration indicator state associated with a most recently monitored control resource set for each control resource set pool. In some examples, for single frequency network operations, receive beam component 1150 may be configured as or otherwise support components for selecting at least one receive beam in the set of receive beams for cross-link interference measurement based on a transmit configuration indicator code point having a lowest identifier value. In some examples, for cross-carrier scheduling operations, receive beam component 1150 may be configured as or otherwise support components for selecting at least one receive beam in the set of receive beams for cross-link interference measurement based on a transmit configuration indicator code point having a lowest identifier value.
[0177] Fig.12A diagram of a system 1200 including a device 1205 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a UE 115 as described herein or include a component of these devices. The device 1205 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1205 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, and a processor 1240. 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 1245).
[0178] I / O controller 1210 can manage input and output signals for device 1205. I / O controller 1210 can also manage peripheral devices that are not integrated into device 1205. In some cases, I / O controller 1210 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1210 can utilize an operating system (such as ) or another known operating system. Additionally or alternatively, I / O controller 1210 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1210 may be implemented as part of a processor (such as processor 1240). In some cases, a user may interact with device 1205 via I / O controller 1210 or via hardware components controlled by I / O controller 1210.
[0179] In some cases, the device 1205 may include a single antenna 1225. However, in some other cases, the device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1215 may communicate bidirectionally via one or more antennas 1225, a wired link, or a wireless link as described herein. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1215 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1225 for transmission, and for demodulating packets received from one or more antennas 1225. The transceiver 1215, or the transceiver 1215 and one or more antennas 1225 may be examples of transmitters 915, transmitters 1015, receivers 910, receivers 1010, or any combination thereof or any components thereof as described herein.
[0180] The memory 1230 may include random access memory (RAM) and read-only memory (ROM). The memory 1230 may store computer-readable, computer-executable code 1235 including instructions that, when executed by the processor 1240, cause the device 1205 to perform various functions described herein. The code 1235 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1235 may not be directly executable by the processor 1240, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, the memory 1230 may also include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0181] Processor 1240 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, processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) to enable device 1205 to perform various functions (e.g., various functions or tasks supporting aspects of cross-link interference measurement). For example, device 1205 or a component of device 1205 may include processor 1240 and memory 1230 coupled to or coupled to processor 1240, and processor 1240 and memory 1230 are configured to perform various functions described herein.
[0182] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a UE (e.g., device 1205). For example, the communication manager 1220 may be configured to or otherwise support components for receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities. The communication manager 1220 may be configured to or otherwise support components for generating a cross-link interference report indicating a cross-link interference measurement for at least one receive beam in the set of receive beams based on the control signaling and a trigger for the cross-link interference measurement. The communication manager 1220 may be configured to or otherwise support components for sending a cross-link interference report to a network entity.
[0183] By including or configuring the communications manager 1220 according to examples as described herein, the device 1205 may support techniques for improving communications reliability, reducing latency, improving user experience associated with reduced processing, more efficiently utilizing communications resources, improving coordination between devices, and improving utilization of processing power.
[0184] In some examples, the communication manager 1220 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1215, one or more antennas 1225, or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1240, the memory 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions that are executable by the processor 1240 to cause the device 1205 to perform various aspects of the aspects for cross-link interference measurement as described herein, or the processor 1240 and the memory 1230 may be otherwise configured to perform or support such operations.
[0185] Fig.13 A block diagram 1300 of a device 1305 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0186] Receiver 1310 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1305. In some examples, receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.
[0187] The transmitter 1315 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1305. For example, the transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1315 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1315 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include a modem or be coupled to a modem.
[0188] The communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of aspects for cross-link interference measurement as described herein. For example, the communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.
[0189] In some examples, the communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in this disclosure. In some examples, a processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0190] Additionally or alternatively, in some examples, the communication manager 1320, the receiver 1310, the transmitter 1315, 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 1320, the receiver 1310, the transmitter 1315, 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).
[0191] In some examples, communication manager 1320 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 can receive information from receiver 1310, transmit information to transmitter 1315, or be integrated in conjunction with receiver 1310, transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.
[0192] According to examples as disclosed herein, the communication manager 1320 may support wireless communication at a network entity (e.g., device 1305). For example, the communication manager 1320 may be configured to or otherwise support a component for the following operations: outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by the UE to generate a cross-link interference report. The communication manager 1320 may be configured to or otherwise support a component for the following operations: obtaining a cross-link interference report indicating a cross-link interference measurement of at least one receive beam in the set of receive beams from the UE.
[0193] By including or configuring the communication manager 1320 according to the examples described herein, the device 1305 (e.g., a processor controlling or otherwise coupled to the receiver 1310, the transmitter 1315, the communication manager 1320, or a combination thereof) can support techniques for reducing processing and more efficiently utilizing communication resources.
[0194] Fig.14 A block diagram 1400 of a device 1405 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of aspects of the device 1305 or the network entity 105 as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. The device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0195] Receiver 1410 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1405. In some examples, receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.
[0196] The transmitter 1415 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1405. For example, the transmitter 1415 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1415 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1415 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include a modem or be coupled to a modem.
[0197] Device 1405 or its various components may be examples of components for performing various aspects of aspects for cross-link interference measurement as described herein. For example, communication manager 1420 may include control signaling component 1425, measurement indication component 1430, or any combination thereof. Communication manager 1420 may be an example of various aspects of communication manager 1320 as described herein. In some examples, communication manager 1420 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 1410, transmitter 1415, or both. For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or be integrated in combination with receiver 1410, transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.
[0198] According to examples as disclosed herein, the communication manager 1420 may support wireless communications at a network entity (e.g., device 1405). The control signaling component 1425 may be configured to or otherwise support means for outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by the UE to generate a cross-link interference report. The measurement indication component 1430 may be configured to or otherwise support means for obtaining a cross-link interference report from the UE indicating a cross-link interference measurement of at least one receive beam in the set of receive beams.
[0199] Fig.15 A block diagram 1500 of a communication manager 1520 supporting aspects for cross-link interference measurement in accordance with one or more aspects of the present disclosure is shown. The communication manager 1520 can be an example of aspects of the communication manager 1320, the communication manager 1420, or both as described herein. The communication manager 1520 or its various components can be examples of means for performing various aspects of aspects for cross-link interference measurement as described herein. For example, the communication manager 1520 can include a control signaling component 1525, a measurement indication component 1530, a measurement opportunity component 1535, a UE capability indication component 1540, an acknowledgement component 1545, a control information component 1550, a scheduling component 1555, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.
[0200] According to examples as disclosed herein, the communication manager 1520 may support wireless communications at a network entity. The control signaling component 1525 may be configured to or otherwise support means for the following operations: outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by the UE to generate a cross-link interference report. The measurement indication component 1530 may be configured to or otherwise support means for the following operations: obtaining a cross-link interference report indicating a cross-link interference measurement of at least one receive beam in the set of receive beams from the UE.
[0201] In some examples, the measurement opportunity component 1535 may be configured to or otherwise support means for: outputting a DCI message indicating an opportunity in the set of cross-link interference measurement opportunities and a receive beam corresponding to the opportunity, wherein the cross-link interference measurement is generated using the receive beam at least in part in response to a trigger including the opportunity indicated by the DCI message. In some examples, the DCI message is scrambled with an RNTI that instructs the UE to generate the cross-link interference measurement, and the cross-link interference report is obtained on an uplink shared channel.
[0202] In some examples, to support outputting control signaling indicating the set of cross-link interference measurement opportunities and the set of receive beams associated with the set of cross-link interference measurement opportunities, the measurement opportunity component 1535 may be configured as or otherwise support components for the following operations: outputting a MAC-CE indicating the set of cross-link interference measurement opportunities and the set of receive beams, wherein the cross-link interference measurement is generated using at least one receive beam at least in part in response to a triggering of an opportunity in the set of cross-link interference measurement opportunities indicated by the MAC-CE.
[0203] In some examples, confirmation component 1545 may be configured or otherwise support means for obtaining a confirmation message in response to a MAC-CE, wherein the cross-link interference report is sent on an uplink control channel according to at least an offset from sending the confirmation message.
[0204] In some examples, the cross-link interference measurement of the cross-link interference report is generated based on an event detected at the UE. In some examples, to support obtaining the cross-link interference report, the control information component 1550 may be configured as or otherwise support means for: obtaining uplink control information including the cross-link interference report on an uplink control channel.
[0205] In some examples, scheduling component 1555 may be configured or otherwise support means for obtaining a scheduling request from the UE. In some examples, scheduling component 1555 may be configured or otherwise support means for: outputting control signaling indicating uplink resources of a shared channel in response to the scheduling request, wherein obtaining a cross-link interference report includes obtaining a MAC-CE including a cross-link interference report on the uplink resources of the shared channel.
[0206] In some examples, UE capability indication component 1540 may be configured to or otherwise support means for obtaining UE capability signaling indicating a threshold offset for an offset between a DCI message and a timing indicated by the DCI message for cross-link interference measurement.
[0207] Fig.16 A diagram of a system 1600 including a device 1605 supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The device 1605 may be an example of a device 1305, a device 1405, or a network entity 105 as described herein, or include components thereof. The device 1605 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1605 may include components that support output and acquisition of communications, such as a communication manager 1620, a transceiver 1610, an antenna 1615, a memory 1625, a code 1630, and a processor 1635. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1640).
[0208] The transceiver 1610 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1610 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1610 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1605 may include one or more antennas 1615 that are capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1610 may also include a modem for modulating a signal, providing the modulated signal for transmission (e.g., via one or more antennas 1615, via a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1615, from a wired receiver), and demodulating the signal. Where applicable, transceiver 1610 or transceiver 1610 and one or more antennas 1615 or wired interfaces may be examples of transmitter 1315, transmitter 1415, receiver 1310, receiver 1410, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).
[0209] Memory 1625 may include RAM and ROM. Memory 1625 may store computer-readable, computer-executable code 1630 including instructions that, when executed by processor 1635, cause device 1605 to perform various functions described herein. Code 1630 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1630 may not be directly executable by processor 1635, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1625 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0210] Processor 1635 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, processor 1635 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1635. Processor 1635 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1625) to enable device 1605 to perform various functions (e.g., various functions or tasks supporting aspects of cross-link interference measurement). For example, device 1605 or a component of device 1605 may include processor 1635 and memory 1625 coupled to processor 1635, and processor 1635 and memory 1625 are configured to perform various functions described herein. Processor 1635 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality (e.g., by executing code 1630) to perform the functions of device 1605.
[0211] In some examples, bus 1640 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1640 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1605 or between different components of device 1605 that may be co-located or located in different locations (e.g., where device 1605 may refer to a system, where one or more of communication manager 1620, transceiver 1610, memory 1625, code 1630, and processor 1635 may be located in one of the different components or divided between the different components).
[0212] In some examples, the communication manager 1620 can manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1620 can manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1620 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with the UE 115 in collaboration with the other network entities 105. In some examples, the communication manager 1620 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.
[0213] According to examples as disclosed herein, the communication manager 1620 may support wireless communication at a network entity (e.g., device 1605). For example, the communication manager 1620 may be configured to or otherwise support a component for the following operations: outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by the UE to generate a cross-link interference report. The communication manager 1620 may be configured to or otherwise support a component for the following operations: obtaining a cross-link interference report indicating a cross-link interference measurement of at least one receive beam in the set of receive beams from the UE.
[0214] By including or configuring the communication manager 1620 according to examples as described herein, the device 1605 can support techniques for improving communication reliability, reducing latency, improving user experience associated with reduced processing, more efficiently utilizing communication resources, improving coordination between devices, and improving utilization of processing.
[0215] In some examples, the communication manager 1620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1610, one or more antennas 1615 (where applicable), or any combination thereof. Although the communication manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1620 may be supported or performed by the processor 1635, the memory 1625, the code 1630, the transceiver 1610, or any combination thereof. For example, the code 1630 may include instructions that are executable by the processor 1635 to cause the device 1605 to perform various aspects of the aspects for cross-link interference measurement as described herein, or the processor 1635 and the memory 1625 may be otherwise configured to perform or support such operations.
[0216] Fig.17 A flowchart illustrating a method 1700 for supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set 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.
[0217] At 1705, the method may include receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.11 The described measurement opportunity indication component 1125 performs.
[0218] At 1710, the method may include generating a cross-link interference report indicating a cross-link interference measurement for at least one receive beam in the set of receive beams based on the control signaling and the triggering of the cross-link interference measurement. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.11 The measurement component 1130 performs.
[0219] At 1715, the method may include sending a cross-link interference report to a network entity. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.11 The described reporting component 1135 is executed.
[0220] Fig.18 A flowchart illustrating a method 1800 for supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set 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.
[0221] At 1805, the method may include receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.11 The described measurement opportunity indication component 1125 performs.
[0222] At 1810, the method may include performing a cross-link interference measurement procedure at an opportunity in the set of cross-link interference measurement opportunities to generate a cross-link interference measurement using a receive beam in the set of receive beams corresponding to the opportunity, wherein the trigger includes the opportunity. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.11 The measurement component 1130 performs.
[0223] At 1815, the method may include generating a cross-link interference report indicating a cross-link interference measurement for at least one receive beam in the set of receive beams based on the control signaling and the triggering of the cross-link interference measurement. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.11 The measurement component 1130 performs.
[0224] At 1820, the method may include sending a cross-link interference report to a network entity. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described in reference to Fig.11 The described reporting component 1135 is executed.
[0225] Fig.19 A flowchart illustrating a method 1900 for supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set 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.
[0226] At 1905, the method may include receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.11 The described measurement opportunity indication component 1125 performs.
[0227] At 1910, the method may include receiving a DCI message indicating an opportunity in the set of cross-link interference measurement opportunities and a receive beam corresponding to the opportunity. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.11 The described measurement opportunity indication component 1125 performs.
[0228] At 1915, the method may include performing a cross-link interference measurement procedure at the opportunity to generate a cross-link interference measurement using a receive beam, wherein the trigger includes an opportunity indicated by a DCI message. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.11 The measurement component 1130 performs.
[0229] At 1920, the method may include generating a cross-link interference report indicating a cross-link interference measurement for at least one receive beam in the set of receive beams based on the control signaling and the triggering of the cross-link interference measurement. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Fig.11 The measurement component 1130 performs.
[0230] At 1925, the method may include sending a cross-link interference report to a network entity. The operations of 1925 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1925 may be performed as described in reference to Fig.11 The described reporting component 1135 is executed.
[0231] Fig. 20 A flow chart illustrating a method 2000 for supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 8 as well as Figures 13 to 16 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.
[0232] At 2005, the method may include outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by the UE to generate a cross-link interference report. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.15 The control signaling component 1525 is used to execute.
[0233] At 2010, the method may include obtaining, from the UE, a cross-link interference report indicating a cross-link interference measurement of at least one receive beam in the set of receive beams. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.15 The measurement instruction component 1530 performs.
[0234] Fig.21 A flowchart illustrating a method 2100 for supporting aspects for cross-link interference measurement according to one or more aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2100 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 8 as well as Figures 13 to 16 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.
[0235] At 2105, the method may include outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by the UE to generate a cross-link interference report. The operations of 2105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed as described in reference to Fig.15 The control signaling component 1525 is used to execute.
[0236] At 2110, the method may include outputting a DCI message indicating an opportunity in the set of cross-link interference measurement opportunities and a receive beam corresponding to the opportunity, wherein the cross-link interference measurement is generated using the receive beam at least in part in response to a trigger including the opportunity indicated by the DCI message. The operations of 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed as described in reference to Fig.15 The measurement opportunity component 1535 executes.
[0237] At 2115, the method may include obtaining from the UE a cross-link interference report indicating a cross-link interference measurement of at least one receive beam in the set of receive beams. The operations of 2115 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed as described in reference to Fig.15 The measurement instruction component 1530 performs.
[0238] The following provides an overview of various aspects of the disclosure:
[0239] Aspect 1: A method for performing wireless communications at a UE, the method comprising receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities; generating a cross-link interference report indicating the cross-link interference measurement for at least one receive beam in the set of receive beams based at least in part on the control signaling and a trigger for the cross-link interference measurement; and sending the cross-link interference report to a network entity.
[0240] Aspect 2: According to the method described in Aspect 1, the method also includes: executing a cross-link interference measurement procedure at a timing in the set of cross-link interference measurement timings to generate the cross-link interference measurement using a receiving beam in the set of receiving beams corresponding to the timing, wherein the trigger includes the timing.
[0241] Aspect 3: According to the method described in Aspect 1, the method also includes: receiving a DCI message indicating a timing in the set of cross-link interference measurement timings and a receiving beam corresponding to the timing; and executing a cross-link interference measurement procedure at the timing to generate the cross-link interference measurement using the receiving beam, wherein the trigger includes the timing indicated by the DCI message.
[0242] Aspect 4: The method according to aspect 3, wherein the DCI message is scrambled with an RNTI instructing the UE to generate the cross-link interference measurement, and the cross-link interference report is sent on an uplink shared channel.
[0243] Aspect 5: A method according to Aspect 1, wherein receiving the control signaling indicating the set of cross-link interference measurement opportunities and the set of receive beams associated with the set of cross-link interference measurement opportunities includes: receiving a MAC-CE indicating the set of cross-link interference measurement opportunities and the set of receive beams; and the method also includes: executing a cross-link interference measurement procedure at a timing in the set of cross-link interference measurement opportunities to generate the cross-link interference measurement using the receive beam in the set of receive beams corresponding to the timing, wherein the trigger includes the timing indicated by the MAC-CE.
[0244] Aspect 6: According to the method of aspect 5, the method also includes: sending a confirmation message in response to the MAC-CE, wherein the cross-link interference report is sent on an uplink control channel according to at least an offset from sending the confirmation message.
[0245] Aspect 7: The method according to aspect 1, the method also includes: performing a cross-link interference measurement procedure to generate the cross-link interference measurement based at least in part on the UE detecting an event, wherein the event includes the trigger.
[0246] Aspect 8: The method according to aspect 7, wherein sending the cross-link interference report includes: sending an uplink control information message including the cross-link interference report on an uplink control channel.
[0247] Aspect 9: According to the method described in Aspect 7, the method also includes: sending a scheduling request to the network entity; and receiving control signaling indicating uplink resources of a shared channel in response to the scheduling request, wherein sending the cross-link interference report includes sending a MAC-CE including the cross-link interference report on the uplink resources of the shared channel.
[0248] Aspect 10: A method according to Aspect 1, wherein the at least one receive beam includes a default receive beam, and the method further includes: selecting the default receive beam for the cross-link interference measurement based at least in part on an offset between a DCI message and a timing indicated by the DCI message for the cross-link interference measurement being less than a threshold offset, wherein the default receive beam is different from a second receive beam associated with the timing in the set of receive beams.
[0249] Aspect 11: According to the method according to aspect 10, the method further includes: sending UE capability signaling indicating the threshold offset to the network entity.
[0250] Aspect 12: A method according to any one of Aspects 10 to 11, wherein the threshold offset includes a first offset value and a second offset value, and the second offset value is at least partially based on whether the DCI message and the timing indicated by the DCI message are associated with the same subcarrier spacing.
[0251] Aspect 13: According to the method described in any one of Aspects 1 to 12, the method further includes: identifying a QCL relationship of a downlink signal received at the UE, wherein the network entity communicates with the UE via a single transmit-receive point; and performing a measurement procedure at a timing in the set of cross-link interference measurement timings to generate the cross-link interference measurement based at least in part on the overlap of the downlink signal with the timing using the QCL relationship.
[0252] Aspect 14: According to the method described in any one of Aspects 1 to 12, the method further includes: identifying a first QCL relationship of a downlink signal received at the UE, wherein the network entity communicates with the UE via a single transmit-receive point; and performing a measurement procedure at a timing in the set of cross-link interference measurement timings to generate the cross-link interference measurement based at least in part on the fact that the downlink signal does not overlap with the timing using a second QCL relationship associated with a lowest CORESET identifier.
[0253] Aspect 15: According to the method described in any one of Aspects 1 to 12, the method further includes: selecting the at least one receive beam from the set of receive beams for the cross-link interference measurement based at least in part on: for a single DCI message operation with multiple transmit-receive points, a TCI code point having the lowest identifier value and identifying multiple TCI states corresponding to the multiple transmit-receive points; for multiple DCI message operations with multiple transmit-receive points, a TCI state associated with a most recently monitored CORESET of each CORESET pool; for SFN operations, a TCI code point having the lowest identifier value; and for cross-carrier scheduling operations, a TCI code point having the lowest identifier value.
[0254] Aspect 16: A method for performing wireless communications at a network entity, the method comprising: outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by a UE to generate a cross-link interference report; and obtaining from the UE the cross-link interference report indicating a cross-link interference measurement of at least one receive beam in the set of receive beams.
[0255] Aspect 17: According to the method described in Aspect 16, the method also includes: outputting a DCI message indicating a timing in the set of cross-link interference measurement timings and a receiving beam corresponding to the timing, wherein the cross-link interference measurement is generated using the receiving beam at least in part in response to a trigger including the timing indicated by the DCI message.
[0256] Aspect 18: The method according to aspect 17, wherein the DCI message is scrambled with an RNTI instructing the UE to generate the cross-link interference measurement, and the cross-link interference report is obtained on an uplink shared channel.
[0257] Aspect 19: A method according to Aspect 16, wherein the outputting the control signaling indicating the set of cross-link interference measurement opportunities and the set of receiving beams associated with the set of cross-link interference measurement opportunities includes: outputting a MAC-CE indicating the set of cross-link interference measurement opportunities and the set of receiving beams, wherein the cross-link interference measurement is generated using the at least one receiving beam at least in part in response to a trigger including an opportunity in the set of cross-link interference measurement opportunities indicated by the MAC-CE.
[0258] Aspect 20: The method according to aspect 19 further comprises: obtaining a confirmation message in response to the MAC-CE, wherein the cross-link interference report is sent on an uplink control channel according to at least an offset from sending the confirmation message.
[0259] Aspect 21: The method of aspect 16, wherein the cross-link interference measurement of the cross-link interference report is generated based at least in part on an event detected at the UE.
[0260] Aspect 22: The method according to aspect 21, wherein obtaining the cross-link interference report comprises: obtaining uplink control information including the cross-link interference report on an uplink control channel.
[0261] Aspect 23: According to the method described in Aspect 21, the method also includes: obtaining a scheduling request from the UE; and outputting control signaling indicating uplink resources of a shared channel in response to the scheduling request, wherein obtaining the cross-link interference report includes obtaining a MAC-CE including the cross-link interference report on the uplink resources of the shared channel.
[0262] Aspect 24: The method according to aspect 16 further comprises: obtaining UE capability signaling, the UE capability signaling indicating a threshold offset for an offset between a DCI message and a timing indicated by the DCI message for the cross-link interference measurement.
[0263] Aspect 25: An apparatus for performing wireless communications at a UE, the apparatus 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 1 to 15.
[0264] Aspect 26: An apparatus for wireless communication at a UE, the apparatus comprising at least one means for performing the method according to any one of aspects 1 to 15.
[0265] Aspect 27: 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 15.
[0266] Aspect 28: An apparatus for wireless communication at a network entity, the apparatus 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 16 to 24.
[0267] Aspect 29: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing the method according to any one of aspects 16 to 24.
[0268] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 16 to 24.
[0269] It should be noted that the methods described herein describe possible implementations, and that the various 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.
[0270] 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 described techniques 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.
[0271] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips 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.
[0272] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0273] 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 via a computer-readable medium. Other examples and specific implementations are within the scope of the present 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.
[0274] Computer-readable medium includes both non-transient computer storage medium and communication medium, including any medium that facilitates computer program to be transmitted 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 or other magnetic storage device, or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.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.
[0275] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with 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 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".
[0276] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, searching (such as via searching in a table, database, or other data structure), ascertaining, etc. 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.
[0277] 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.
[0278] 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 embodiments include specific details to provide an understanding of the described technology. However, these 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 described examples.
[0279] 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. Thus, 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, which are stored in the memory and can be executed by the processor to cause the device to perform the following operations: receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities; generating a cross-link interference report indicating the cross-link interference measurement for at least one receive beam in the set of receive beams based at least in part on the control signaling and the triggering of the cross-link interference measurement; as well as The cross-link interference report is sent to a network entity.
2. The apparatus according to claim 1, wherein the instructions are further executable by the processor to cause the apparatus to perform the following operations: A cross-link interference measurement procedure is performed at an opportunity in the set of cross-link interference measurement opportunities to generate the cross-link interference measurement using a receive beam in the set of receive beams corresponding to the opportunity, wherein the trigger includes the opportunity.
3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to perform the following operations: receiving a downlink control information message indicating an opportunity in the set of cross-link interference measurement opportunities and a receive beam corresponding to the opportunity; and A cross-link interference measurement procedure is performed at the opportunity to generate the cross-link interference measurement using the receive beam, wherein the trigger comprises the opportunity indicated by the downlink control information message.
4. The apparatus of claim 3, wherein the downlink control information message is scrambled with a radio network temporary identifier instructing the UE to generate the cross-link interference measurement, the cross-link interference report being sent on an uplink shared channel.
5. The apparatus of claim 1 , wherein the instructions for receiving the control signaling indicating the set of cross-link interference measurement opportunities and the set of receive beams associated with the set of cross-link interference measurement opportunities are executable by the processor to cause the apparatus to: receiving a medium access control element indicating the set of cross-link interference measurement opportunities and the set of receive beams; and the apparatus further comprising: A cross-link interference measurement procedure is performed at an opportunity in the set of cross-link interference measurement opportunities to generate the cross-link interference measurement using a receive beam in the set of receive beams corresponding to the opportunity, wherein the trigger includes the opportunity indicated by the medium access control control element.
6. The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to perform the following operations: An acknowledgement message is sent in response to the medium access control element, wherein the cross-link interference report is sent on an uplink control channel according to at least an offset from sending the acknowledgement message.
7. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A cross-link interference measurement procedure is performed to generate the cross-link interference measurement based at least in part on the UE detecting an event, wherein the event includes the trigger.
8. The apparatus of claim 7, wherein the instructions for sending the cross-link interference report are executable by the processor to cause the apparatus to: An uplink control information message including the cross-link interference report is sent on an uplink control channel.
9. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to perform the following operations: sending a scheduling request to the network entity; and Control signaling indicating uplink resources of a shared channel is received in response to the scheduling request, wherein sending the cross-link interference report includes sending a medium access control control element including the cross-link interference report on the uplink resources of the shared channel.
10. The apparatus of claim 1, wherein the at least one receive beam comprises a default receive beam, and the instructions are further executable by the processor to cause the apparatus to: The default receive beam for the cross-link interference measurement is selected at least in part based on an offset between a downlink control information message and a timing indicated by the downlink control information message for the cross-link interference measurement being less than a threshold offset, wherein the default receive beam is different from a second receive beam in the set of receive beams associated with the timing.
11. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to perform the following operations: UE capability signaling indicating the threshold offset is sent to the network entity.
12. The device according to claim 10, wherein: The threshold offset includes a first offset value and a second offset value, and The second offset value is based at least in part on the downlink control information message and whether the opportunities indicated by the downlink control information message are associated with a same subcarrier spacing.
13. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a quasi co-location relationship of downlink signals received at the UE, wherein the network entity communicates with the UE via a single transmit-receive point; and A measurement procedure is performed at an opportunity in the set of cross-link interference measurement opportunities to generate the cross-link interference measurement using the quasi co-site relationship based at least in part on the downlink signal overlapping the opportunity.
14. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a first quasi co-location relationship of downlink signals received at the UE, wherein the network entity communicates with the UE via a single transmit-receive point; and A measurement procedure is performed at an opportunity in the set of cross-link interference measurement opportunities to generate the cross-link interference measurement based at least in part on the downlink signal not overlapping the opportunity using a second quasi co-site relationship associated with a lowest control resource set identifier.
15. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The at least one receive beam in the set of receive beams for the cross-link interference measurement is selected based at least in part on: for a single downlink control information message operation with multiple transmit-receive points, a transmit configuration indicator code point having a lowest identifier value and identifying a plurality of transmit configuration indicator states corresponding to the plurality of transmit-receive points; for multiple downlink control information message operations at multiple transmit-receive points, a transmit configuration indicator state associated with a most recently monitored control resource set of each control resource set pool; For single frequency network operation, the transmit configuration indicator code point with the lowest identifier value; as well as For cross-carrier scheduling operation, the transmission configuration indicator code point with the lowest identifier value.
16. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and Instructions, which are stored in the memory and can be executed by the processor to cause the device to perform the following operations: outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by a user equipment (UE) to generate a cross-link interference report; as well as The cross-link interference report indicating a cross-link interference measurement for at least one receive beam in the set of receive beams is obtained from the UE.
17. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: Output a downlink control information message indicating a timing in the set of cross-link interference measurement timings and a receive beam corresponding to the timing, wherein the cross-link interference measurement is generated using the receive beam at least in part in response to a trigger including the timing indicated by the downlink control information message.
18. The apparatus of claim 17, wherein the downlink control information message is scrambled with a radio network temporary identifier that instructs the UE to generate the cross-link interference measurement, the cross-link interference report being obtained on an uplink shared channel.
19. The apparatus of claim 16, wherein the instructions for outputting the control signaling indicating the set of cross-link interference measurement opportunities and the set of receive beams associated with the set of cross-link interference measurement opportunities are executable by the processor to cause the apparatus to: Outputting a medium access control control element indicating the set of cross-link interference measurement opportunities and the set of receive beams, wherein the cross-link interference measurement is generated using the at least one receive beam at least in part in response to a trigger including an opportunity in the set of cross-link interference measurement opportunities indicated by the medium access control control element.
20. The apparatus of claim 19, wherein the instructions are further executable by the processor to cause the apparatus to: An acknowledgement message is obtained in response to the medium access control control element, wherein the cross-link interference report is sent on an uplink control channel according to at least an offset from sending the acknowledgement message.
21. The apparatus of claim 16, wherein the cross-link interference measurement of the cross-link interference report is generated based at least in part on an event detected at the UE.
22. The apparatus of claim 21, wherein the instructions for obtaining the cross-link interference report are executable by the processor to cause the apparatus to: Uplink control information including the cross-link interference report is obtained on an uplink control channel.
23. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: Obtaining a scheduling request from the UE; and Control signaling indicating uplink resources of a shared channel is output in response to the scheduling request, wherein obtaining the cross-link interference report comprises obtaining a medium access control control element including the cross-link interference report on the uplink resources of the shared channel.
24. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: UE capability signaling is obtained, the UE capability signaling indicating a threshold offset for an offset between a downlink control information message and a timing indicated by the downlink control information message for the cross-link interference measurement.
25. A method for wireless communication at a user equipment (UE), the method comprising: receiving control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities; generating a cross-link interference report indicating the cross-link interference measurement for at least one receive beam in the set of receive beams based at least in part on the control signaling and the triggering of the cross-link interference measurement; as well as The cross-link interference report is sent to a network entity.
26. The method according to claim 25, further comprising: A cross-link interference measurement procedure is performed at an opportunity in the set of cross-link interference measurement opportunities to generate the cross-link interference measurement using a receive beam in the set of receive beams corresponding to the opportunity, wherein the trigger includes the opportunity.
27. The method according to claim 25, further comprising: receiving a downlink control information message indicating an opportunity in the set of cross-link interference measurement opportunities and a receive beam corresponding to the opportunity; as well as A cross-link interference measurement procedure is performed at the opportunity to generate the cross-link interference measurement using the receive beam, wherein the trigger comprises the opportunity indicated by the downlink control information message.
28. A method for wireless communication at a network entity, the method comprising: outputting control signaling indicating a set of cross-link interference measurement opportunities and a set of receive beams associated with the set of cross-link interference measurement opportunities for use by a user equipment (UE) to generate a cross-link interference report; as well as The cross-link interference report indicating a cross-link interference measurement for at least one receive beam in the set of receive beams is obtained from the UE.
29. The method according to claim 28, further comprising: Output a downlink control information message indicating a timing in the set of cross-link interference measurement timings and a receive beam corresponding to the timing, wherein the cross-link interference measurement is generated using the receive beam at least in part in response to a trigger including the timing indicated by the downlink control information message.
30. The method of claim 29, wherein the downlink control information message is scrambled with a radio network temporary identifier instructing the UE to generate the cross-link interference measurement, the cross-link interference report being obtained on an uplink shared channel.
