Backhaul and over-the-air signaling for inter-user equipment cross-link interference management

Abstract

Aspects of the present disclosure relate to backhaul and over-the-air signaling for inter-user equipment cross-link interference management. A first network entity serving victim user equipment (UE) receives an SRS configuration for inter-cell cross-link interference (CLI) measurements from a second network entity serving one or more attacker UEs. The first network entity also receives additional information associated with the sounding reference signal (SRS) configuration indicating which UEs (or beams of UEs) may be used within the next P milliseconds. The first network entity may then combine this information with the CLI reported by the victim UE for coordinated scheduling and beamforming, link adaptation, etc. in order to reduce the CLI.

Description

[0001] Related applications

[0002] This application claims priority to U.S. Patent Application No. 63 / 493,588, filed March 31, 2023, entitled "Backhaul and Over-the-Air Signaling for Inter-User Equipment Cross-Link Interference Management," the entire disclosure of which is incorporated herein by reference. This application also claims priority to U.S. Patent Application No. 63 / 493,578, filed March 31, 2023, entitled "Inter-User Equipment Cross-Link Interference Management," the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] This disclosure relates to wireless communications, and more specifically to cross-link interference (CLI) management between user equipment (UEs). Background Technology

[0004] A wireless communication system may include one or more network communication devices, such as base stations, which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (e.g., base station) may support wireless communication with one or more user communication devices, which may also be referred to as UE or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)). Furthermore, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth-generation (6G)).

[0005] In wireless communication systems, various data and control information can be transmitted from one device to another, such as from a UE to a base station (e.g., a gNB), or from a base station (e.g., a gNB) to a UE. Given the various network communication devices and user communication devices in a wireless communication system and their proximity to each other, interference may occur when these devices transmit data or control information. Summary of the Invention

[0006] This disclosure relates to methods, apparatus, and systems supporting backhaul and over-the-air (OTA) signaling for cross-link interference management between user equipment (UEs). Typically, the techniques discussed herein provide one or both of new backhaul or OTA signaling that allow a first network entity (e.g., a first base station) serving a victim UE to obtain additional information from a second network entity (e.g., a second base station) serving an attacker UE. The first network entity (e.g., the first base station) receives a probe reference signal (SRS) configuration from the second network entity (e.g., the second base station), the SRS configuration indicating associations between multiple resources and multiple devices (e.g., UEs). The first network entity transmits a CLI report configuration to at least one of the multiple devices. The first network entity receives CLI reports from the at least one device according to the CLI report configuration, each CLI report containing multiple CLI measurements associated with the multiple resources. The first network entity transmits a CLI report information element (IE) to the second network entity, the CLI report information element indicating, based on the CLI reports and the associations between the multiple resources and the multiple devices, that one or more of the multiple devices caused excessive CLI. By obtaining the CLI results indicating one or more devices that cause excessive CLI, the first network entity can use the CLI results to coordinate scheduling and beamforming, link adaptation, etc., to reduce the excessive CLI.

[0007] Some embodiments of the methods and apparatus described herein may further include: receiving from a network entity a first signaling instruction indicating an SRS configuration, the SRS configuration indicating associations between multiple resources and multiple devices; transmitting to a first device a second signaling instruction indicating a CLI report configuration; receiving from the first device, according to the CLI report configuration, a third signaling instruction indicating a CLI report, wherein the CLI report includes multiple CLI measurement results associated with the multiple resources; and transmitting to the network entity a fourth signaling instruction indicating a CLI report IE, the CLI report IE indicating, based on the CLI report and the associations between the multiple resources and the multiple devices, that one or more of the multiple devices cause excessive CLI.

[0008] In some embodiments of the methods and apparatus described herein, one or more of the plurality of devices causing the excessive CLI are determined by: determining that one or more CLI measurement results associated with one or more of the plurality of resources are excessive; determining one or more of the plurality of devices associated with the one or more of the plurality of resources based on the association between the plurality of resources and the plurality of devices; and inferring that the one or more of the devices causes the excessive CLI. Additionally or alternatively, determining that the one or more CLI measurement results are excessive includes comparing the CLI measurement results with a CLI threshold. Additionally or alternatively, each of the plurality of resources includes one or more of at least one symbol or at least one resource element. Additionally or alternatively, the SRS configuration further includes an indication of the association between the plurality of resources and a plurality of transmit beams of the plurality of devices; the method and apparatus further determine that one or more of the plurality of transmit beams of one or more of the plurality of devices causes the excessive CLI; and the CLI report IE further indicates that one or more of the plurality of transmit beams of the one or more devices causes the excessive CLI. Alternatively or additionally, the method and apparatus receive an activation or deactivation indication associated with the SRS configuration; and in response to determining that the activation or deactivation indication indicates deactivation, instruct the first device to deactivate the CLI report. Alternatively or additionally, one or more of the plurality of devices causing the excessive CLI are determined by: receiving a pattern associated with the plurality of devices from the network entity, wherein the pattern includes a plurality of fields, each of which is associated with one of the plurality of devices; determining that the device associated with the field transmits SRS in response to a field in the pattern equaling a first value; and determining that the device does not transmit the SRS in response to a field in the pattern equaling a second value. Alternatively or additionally, the pattern includes a bitmap field or is otherwise associated with it; each of the plurality of fields is a bit in the bitmap field; the first value is '1'; and the second value is '0'. Alternatively or additionally, the method and apparatus receive the pattern via a backhaul interface or over-the-air (OTA) via a fifth signaling. Alternatively, each of the plurality of CLI measurements is at least one of co-channel SRS reference received power (SRS-RSRP) or co-channel CLI received signal strength indication (CLI-RSSI). Alternatively, each of the plurality of CLI measurements is a co-channel SRS-RSRP; and the one or more of the plurality of devices causing the excessive CLI are obtained by: obtaining one or more adjacent channel leakage ratio (ACLR) values ​​associated with the one or more of the plurality of devices; and calculating adjacent channel CLI by combining the co-channel SRS-RSRP and ACLR values.Alternatively or additionally, the method and apparatus receive a fifth signaling indicating the ACLR value from the network entity. Alternatively or additionally, calculating the adjacent channel CLI includes at least one of the following: dividing the co-channel SRS-RSRP value by the associated ACLR value in the real number domain; or subtracting the ACLR value from the co-channel SRS-RSRP value in the logarithmic or decibel domain. Alternatively or additionally, the apparatus and the network entity are a base station or a transmit-receive point (TRP). Alternatively or additionally, the CLI threshold is indicated by core network functions, by an Operations, Administration, and Maintenance (OAM) entity, by standards, or according to an implementation scheme. Alternatively or additionally, the CLI report is associated with the physical layer, the Media Access Control (MAC) layer, or the Radio Resource Control (RRC) layer.

[0009] Some implementations of the methods and apparatus described herein may further include: obtaining a Radio Network Temporary Identifier (RNTI) associated with the Physical Network Link Control Channel (PNCCH); receiving multiple over-the-air (OTA) signals associated with the PNCCH from a network entity; and descrambling the multiple OTA signals by applying the RNTI.

[0010] In some implementations of the methods and apparatus described herein, the RNTI is indicated by at least one of the following: by a standard, by the core network, by the network entity on the backhaul interface, by the network entity in a broadcast signal, by the network entity in a system information block, or by an OAM entity. Alternatively, the methods and apparatus obtain an identifier (ID); and descramble the plurality of OTA signals by applying the RNTI and the ID. Alternatively, the ID is a cell ID associated with the network entity. Alternatively, obtaining the ID involves receiving additional signaling indicating the ID from at least one of the core network, the network entity, or the Orthogonal Access and Backhaul (OAB). Alternatively, the PNCCH is mapped to at least one of the Network Link Transport Channel (NCH), Network Link Logical Control Channel (NCCH), Common Control Channel (CCCH), or Broadcast Control Channel (BCCH).

[0011] Some implementations of the methods and apparatus described herein may further include: transmitting a first signaling to a network entity indicating an SRS configuration, the SRS configuration indicating associations between multiple resources and multiple devices; and receiving from the network entity a second signaling indicating a CLI report IE, the CLI report IE indicating, based on the CLI report and the associations between the multiple resources and the multiple devices, that one or more of the multiple devices cause excessive CLI.

[0012] In some embodiments of the methods and apparatus described herein, each of the plurality of resources includes at least one symbol or one or more of at least one resource element. Additionally or alternatively, the SRS configuration further includes an indication of the association between the plurality of resources and a plurality of transmit beams of the plurality of devices; and the CLI report IE further indicates that the one or more of the plurality of transmit beams of the one or more devices caused the excessive CLI. Additionally or alternatively, the methods and apparatus transmit an activation or deactivation indication associated with the SRS configuration. Additionally or alternatively, the methods and apparatus transmit third signaling to the network entity indicating one or more ACLR values ​​associated with one or more of the plurality of devices. Additionally or alternatively, each of the devices and the network entity is a base station or a TRP. Additionally or alternatively, the CLI report is associated with a physical layer, MAC layer, or RRC layer.

[0013] Some implementations of the methods and apparatus described herein may further include: scrambling multiple OTA signals associated with the PNCCH by applying an RNTI associated with the PNCCH; and transmitting the multiple OTAs to a network entity.

[0014] In some implementations of the methods and apparatus described herein, the RNTI is indicated by at least one of the following: by a standard, by the core network, by the network entity on the backhaul interface, by the network entity in a broadcast signal, by the network entity in a system information block, or by an OAM entity. Alternatively, the method and apparatus obtain an ID; and scramble the plurality of OTA signals by applying the RNTI and the ID. Alternatively, the ID is a cell ID associated with the apparatus. Alternatively, the PNCCH is mapped to at least one of NCH, NCCH, CCCH, or BCCH. Attached Figure Description

[0015] Figure 1 Examples of wireless communication systems for backhaul and air signaling, supported by aspects of this disclosure, for cross-link interference management between user equipment.

[0016] Figure 2 This describes an example of a combination in a UE according to aspects of this disclosure.

[0017] Figure 3 This document describes an example of a timeline for the transmission of reference signals for backhaul and air signaling, which is supported by aspects of this disclosure for cross-link interference management between user equipment.

[0018] Figure 4This describes an example of a fixed allocation of resource elements (REs) to mode ID numbers for backhaul and air signaling used for cross-link interference management between user equipment, in accordance with aspects of this disclosure.

[0019] Figure 5 This describes an example of variable allocation of RE to mode ID numbers for backhaul and air signaling in support of aspects of this disclosure for cross-link interference management between user equipment.

[0020] Figure 6 This document describes an example of an architecture and backhaul interface for backhaul and air signaling used for cross-link interference management between user equipment, based on aspects of this disclosure.

[0021] Figure 7 This describes examples of entities and relationships within links in an example system supporting backhaul and air signaling for cross-link interference management between user equipment, based on aspects of this disclosure.

[0022] Figure 8 This describes examples of mappings in new and existing channels for backhaul and air signaling used for cross-link interference management between user equipment, based on aspects of this disclosure.

[0023] Figure 9 This document describes an example of OTA signaling to the UE that supports backhaul and over-the-air signaling for cross-link interference management between user equipment, based on aspects of this disclosure.

[0024] Figure 10 This illustration illustrates an example of a block diagram of an apparatus for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure.

[0025] Figures 11 to 20 A flowchart illustrating a method for backhaul and air signaling for cross-link interference management between user equipment, based on aspects of this disclosure. Detailed Implementation

[0026] In wireless communication systems, Time Division Duplex (TDD) refers to a scheme for allocating radio resources in the downlink and uplink in the time domain. In a TDD system, at any given time on a given frequency, a base station transmits signals to one or more subscriber devices, or vice versa, but usually not both. In conventional cellular systems employing static TDD, the TDD modes are fully synchronized and typically identical to avoid interference from a single network entity (e.g., a base station) when receiving signals in the uplink of a nearby cell while transmitting them in the downlink to another network entity (e.g., a base station). However, with dynamic TDD, where different TDD modes can be used in different cells, interference can occur from one UE to another. If this is not addressed through appropriate inter-UE interference management techniques, it degrades performance.

[0027] Similarly, in wireless communication systems, Subband Full-Duplex (SBFD) refers to a scheme in which one or more UEs are configured to transmit uplink signals in a subband on a downlink symbol, or vice versa. One or more UEs may not be expected to have full-duplex capability on a subband, but network entities (e.g., base stations) may support full-duplex communication on a subband.

[0028] When using dynamic TDD or SBFD in a cell, especially for beamforming at millimeter-wave frequencies, the interference caused by one UE to another can be significant, depending on the beamforming configuration at both the attacker UE and the victim UE. For example, if the attacker UE happens to transmit an uplink signal using a spatially guided transmit (Tx) beam directed toward the victim UE, and the victim UE happens to receive a downlink signal on the same time-frequency resource using a spatially guided receive (Rx) beam directed toward the attacker UE, then the uplink signal may cause excessive interference to the downlink signal.

[0029] Typically, the techniques discussed herein provide one or both of new backhaul or OTA signaling that allows a first network entity serving a victim UE (e.g., a first base station) to obtain additional information from a second network entity serving an attacker UE (e.g., a second base station). The first network entity can then use this additional information, along with CLI results reported by the victim UE, to coordinate scheduling and beamforming, link adaptation, etc., to reduce the reported CLI. In one or more embodiments, the first network entity serving the victim UE receives an SRS configuration for inter-cell CLI measurements from a second network entity serving one or more attacker UEs. The first network entity also receives additional information associated with the SRS configuration, indicating which UEs (or UE beams) can be used in the next P milliseconds. The first network entity can then combine this information with the CLI reported by the victim UE to coordinate scheduling and beamforming, link adaptation, etc., to reduce CLI. Additionally or alternatively, the first network entity receives ACLR information from the second network entity, which, along with the reported CLI, can be used to estimate adjacent channel interference, which can then be used for scheduling and link adaptation in adjacent channels to reduce CLI.

[0030] Using the techniques discussed in this paper, inter-UE CLI can be managed by network entities. Existing CLI frameworks do not specify how serving cells should use reported CLI results for scheduling and link adaptation, and further do not address adjacent channel interference. The techniques discussed in this paper address these shortcomings in existing CLI frameworks using one or both of the methods described in backhaul or OTA signaling.

[0031] The aspects of this disclosure are described in the context of a wireless communication system. Reference is made to apparatus diagrams and flowcharts for further illustration and description of these aspects.

[0032] Figure 1This description illustrates an example of a wireless communication system 100 supporting backhaul and air signaling for cross-link interference management between user equipment, according to aspects of this disclosure. The wireless communication system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A (LTE-Advanced) network. In some other embodiments, the wireless communication system 100 may be a 5G network, such as a New Radio (NR) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or include other suitable radio access technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0033] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or be referred to as a network node, base station, network element, radio access network (RAN), base transceiver station, access point, NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Network entity 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entity 102 and UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[0034] Network entity 102 can provide a geographic coverage area 112, wherein network entity 102 can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within geographic coverage area 112. For example, network entity 102 and UE 104 can support wireless communication of signals associated with the services (e.g., voice, video, packet data, messaging, broadcasting, etc.) according to one or more radio access technologies. In some embodiments, network entity 102 can be mobile, for example, a satellite associated with a non-terrestrial network. In some embodiments, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas 112 can be associated with different network entities 102. The information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0035] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some embodiments, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine-Type Communication (MTC) device, and other instances thereof. In some embodiments, UE 104 may be fixed within the wireless communication system 100. In some other embodiments, UE 104 may be mobile within the wireless communication system 100.

[0036] One or more UEs 104 may be devices of different forms or with different capabilities. Figure 1 This section describes some examples of UE 104. UE 104 can communicate with various types of devices, such as network entity 102, other UEs 104, or network equipment (e.g., core network 106, packet data network 108, relay device, integrated access and backhaul (IAB) node, or another network device), such as... Figure 1 As shown in the diagram. Alternatively, UE 104 may support communication with other network entities 102 or UE 104, which may be used as repeaters in the wireless communication system 100.

[0037] UE 104 may also support direct wireless communication with other UE 104 via communication link 114. For example, UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a side link. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0038] Network entity 102 may support communication with core network 106 or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N6, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some embodiments, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other embodiments, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some embodiments, one or more network entities 102 may include sub-components, such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transmitting entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0039] In some implementations, network entity 102 may be configured as a decomposed architecture, which may be configured to utilize protocol stacks physically or logically distributed across two or more network entities 102, 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, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0040] An RU may also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 102 in the decomposed RAN architecture may be co-located, or one or more components of network entity 102 may be located in distributed locations (e.g., individual physical locations). In some implementations, one or more network entities 102 in the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0041] The functional partitioning among CU, DU, and RU can be flexible and can depend on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU to support different functionalities. For example, a protocol stack functional partitioning can be used between the CU and DU, such that the CU can support one or more layers of the protocol stack, and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host higher-level protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-level protocol layer functionalities and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each can be at least partially controlled by the CU.

[0042] Alternatively, a functional partitioning of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack, and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional partitioning between the CU and DU, or between the DU and RU, can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by different of the CU, DU, or RU).

[0043] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some embodiments, the midhaul or fronthaul communication links can be implemented according to the interfaces (e.g., channels) between layers of the protocol stack supported by the respective network entity 102 communicating via such communication links.

[0044] Core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), and may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Functions (AMF)), and user plane entities that route packets or interconnections to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), User Plane Functions (UPF)) or location management functions (LMF) of control plane entities that manage location services. In some embodiments, the control plane entities may manage one or more non-access stratum (NAS) functions of UE 104 served by one or more network entities 102 associated with core network 106, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.).

[0045] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N6, or another network interface). Packet data network 108 may include application server 118. In some embodiments, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session or similar) with core network 106 via network entity 102. Core network 106 may use the established session (e.g., an established PDU session) to route traffic (e.g., control information, data, and the like) between UE 104 and application server 118. A PDU session may be an instance of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0046] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, network entity 102 and UE 104 may support different resource structures. For example, network entity 102 and UE 104 may support different frame structures. In some embodiments, such as in 4G, network entity 102 and UE 104 may support a single frame structure. In some other embodiments, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 may support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 may support various frame structures based on one or more parameter sets.

[0047] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a regular cyclic prefix. The first parameter set (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular or extended cyclic prefix. A fourth parameter set (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a regular cyclic prefix. A fifth parameter set (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.

[0048] Time intervals for organizing resources (e.g., communication resources) can be based on frames (also known as radio frames). Each frame may have a duration, such as 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, such as 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0049] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., a certain quantity) of time slots. Each time slot may contain a certain number (e.g., a certain quantity) of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on a parameter set. For a regular cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both regular and extended cyclic prefixes may depend on the parameter set. It should be understood that references to a first parameter set (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and time slots.

[0050] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410MHz to 7.125GHz), FR2 (24.25GHz to 52.6GHz), FR3 (7.125GHz to 24.25GHz), FR4 (52.6GHz to 114.25GHz), FR4a or FR4-1 (52.6GHz to 71GHz), and FR5 (114.25GHz to 300GHz). In some embodiments, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some embodiments, FR1 can be used by network entity 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other equipment or devices, for short-range, high-data-rate capabilities.

[0051] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with: a first parameter set (e.g., μ = 0) containing a 15 kHz subcarrier spacing; a second parameter set (e.g., μ = 1) containing a 30 kHz subcarrier spacing; and a third parameter set (e.g., μ = 2) containing a 60 kHz subcarrier spacing. FR2 may be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 may be associated with: a third parameter set (e.g., μ = 2) containing a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., μ = 3) containing a 120 kHz subcarrier spacing.

[0052] In one or more implementations, network entity 102 transmits an SRS configuration and CLI report configuration 120 to UE 104. The SRS configuration includes an indication of a set of resources (e.g., symbols) associated with multiple devices. UE 104 includes a CLI measurement system 122 that performs CLI measurements on each of the multiple resource subsets indicated in the SRS configuration. UE 104 transmits a CLI report 124 to network entity 102 containing one or more results of the CLI measurements. Network entity 102 transmits a CLI report IE 126 obtained from CLI report 124 to network entity 128 (which is another network entity 102). CLI report IE 126 indicates one or more other UEs 104 that caused excessive CLI for UE 104, allowing network entity 128 to coordinate scheduling and beamforming, link adaptation, etc., to reduce excessive CLI.

[0053] The communication between devices discussed herein, such as between UE 104 and network entity 102, is performed using any of a variety of signaling. For example, such signaling can be any of a variety of messages, requests, or responses, such as trigger messages, configuration messages, etc. As another example, such signaling can be any of a variety of signaling media or protocols on which messages are transmitted, such as any combination of Radio Resource Control (RRC), Downlink Control Information (DCI), Uplink Control Information (UCI), Sidelink Control Information (SCI), Media Access Control Element (MAC-CE), Sidelink Positioning Protocol (SLPP), PC5 Radio Resource Control (PC5-RRC), etc.

[0054] Time Division Duplex (TDD) can be used in NR deployments. In TDD, time-domain resources are divided between downlink and uplink. Allocating limited duration for uplinks in TDD results in reduced coverage, increased latency, and reduced capacity. An enhancement to this constraint on regular TDD operation is the ability to allow both downlink and uplink to coexist, also known as full-duplex, for example, non-overlapping full-duplex subbands at the network entity (e.g., gNB) side within a regular TDD band.

[0055] NR TDD allows for dynamic or flexible allocation of downlink and uplink in NR time and CLI handling, as well as in Remote Interference Management (RIM). The techniques discussed in this paper also consider CLI handling between network entities (e.g., gNBs) of the same or different operators to enable dynamic or flexible TDD in wireless networks. Depending on the deployment scenario, inter-network entity (e.g., gNB) CLI may result from adjacent channel CLI, co-channel CLI, or both. CLI can also be network entity-to-network entity (e.g., gNB-to-gNB) CLI.

[0056] The duplex evolution in the domain discussed above provides enhanced uplink (UL) coverage, reduced latency, improved system capacity, and improved configuration flexibility for NR TDD operations in unpaired spectrum.

[0057] In one or more implementations, this paper discusses duplex evolution that supports NR TDD in unpaired spectrum.

[0058] In one or more embodiments, the techniques discussed herein assume duplex enhancement at the network entity (e.g., gNB) side. Additionally or alternatively, the techniques discussed herein assume half-duplex operation at the UE side. Furthermore or alternatively, the techniques discussed herein assume no limitation on the frequency range.

[0059] One or more implementation schemes consider at least one of the following: applicable and relevant deployment scenarios; evaluation methods for duplex enhancement; subband non-overlapping full-duplex and potential enhancements to dynamic or flexible TDD; possible schemes and their feasibility and performance; solutions for CLI handling and management between network entities (e.g., between gNBs) and between UEs; intra-subband CLI and inter-subband CLI in the case of subband non-overlapping full-duplex; or the performance of the identified scheme and the impact of its coexistence in co-channel and adjacent channels on traditional operation.

[0060] In wireless communication systems, TDD refers to a scheme for allocating radio resources in the downlink and uplink in the time domain. In a TDD system, at any given time on a given frequency, a base station transmits signals to one or more subscriber devices, or vice versa, but usually not both. In conventional cellular systems employing static TDD, the TDD modes are fully synchronized and typically identical to avoid interference from one base station in a nearby cell (when transmitting in the downlink) to another base station (when receiving in the uplink). However, if dynamic TDD is used, where different TDD modes can be used in different cells, interference can occur from one UE to another, thus degrading performance if not addressed with appropriate inter-UE interference management techniques.

[0061] One type of duplex enhancement is Subband Full-Duplex (SBFD), in which one or more UEs can be configured to transmit uplink signals in a subband on a downlink symbol, or vice versa. One or more UEs may not have full-duplex capability on a subband, but network entities (e.g., base stations) may have duplex enhancement for communication on a subband.

[0062] When such duplex enhancements are employed in a cell, especially for beamforming at millimeter-wave frequencies, the interference caused by one UE to the other can be significant, depending on the beamforming configurations at both the attacker and victim UEs. For example, if the attacker UE happens to transmit an uplink signal using a spatially guided transmit (Tx) beam directed towards the victim UE, and the victim UE happens to receive a downlink signal on the same time-frequency resource using a spatially guided receive (Rx) beam directed towards the attacker UE, then the uplink signal may cause excessive interference to the downlink signal. This interference can be avoided through appropriate signaling and coordination within the UE.

[0063] SRS configuration information can be provided from the second UE to the first UE. The first UE can be configured to measure SRS and report SRS-RSRP to its serving cell. The CLI specification in Rel-16 allows intra-cell UE-to-UE CLI measurements, but does not include specifications for inter-cell CLI measurements.

[0064] For UE-to-UE CLI mitigation purposes, the following potential enhancements are considered. For L1 / L2 UE-to-UE CLI reporting, periodic, semi-persistent, and aperiodic reporting are considered. For L1 / L2 UE-to-UE CLI measurement, periodic, semi-persistent, or aperiodic measurement resources are considered.

[0065] For UE-to-UE co-channel CLI processing, consider enhancing the UL power control mechanism. For example, use the existing UL power control mechanism as a baseline.

[0066] For UE-to-UE subband CLI measurements, consider the following: In one or more implementations, consider the victim UE measuring RSSI within the downlink (DL) subband. Additionally or alternatively, consider the victim UE measuring the attacker UE's RSRP within the UL subband. Additionally or alternatively, consider the victim UE measuring RSSI within the UL subband.

[0067] It should be noted that if CLI is measured only within the DL BWP, this does not preclude the UE from measuring CLI in the UL subband when the UL subband is confined within the DL BWP.

[0068] One problem to be addressed is that a cell may be serving a potentially large number of UEs at a time. Providing SRS configuration information to each potential victim UE from an increasing number of potential attacker UEs may become inefficient or impractical. Furthermore, especially in the case of inter-UE CLI between cells, it is unclear at each communication which interfering UE will be interfering. This problem may be further exacerbated if a given attacker UE uses more than one Tx beam for its UL transmission.

[0069] The number of CLI measurements across multiple UEs is proportional to the square of the number of UEs multiplied by the square of the number of potential beams (per UE). This can be a large number when there are multiple cells nearby, multiple UEs in each cell, or multiple potential beams per UE, requiring proper coordination and resource allocation during measurement and communication.

[0070] This paper discusses the coordinated configuration of reference signals, as well as coordinated scheduling and beamforming. Several additional signaling methods are also proposed, such as ACLR indication and backhaul or OTA signaling for transmitting semi-static and dynamic information.

[0071] When different TDD DL or UL modes are used between adjacent cells, UL transmission in one cell may interfere with DL reception in another cell: this is called Cross-Link Interference (CLI). To mitigate CLI, network entities (e.g., gNBs) can exchange and coordinate their intended TDD DL-UL configurations via the Xn and F1 interfaces, and victim UEs can be configured to perform CLI measurements. Two types of CLI measurements are: SRS-RSRP measurement, where the UE measures SRS-RSRP through the SRS resources of one or more attacker UEs; and CLI-RSSI measurement, where the UE measures the total received power observed through RSSI resources. Layer 3 filtering is applied to CLI measurement results and supports both event-triggered and periodic reporting.

[0072] The SRS reference signal received power (SRS-RSRP) is defined as the linear average of the power contribution (e.g., in [W]) of the resource element carrying the sounding reference signal (SRS). SRS-RSRP can be measured using configured resource elements within the considered measurement frequency bandwidth at a configured measurement time point. For frequency range 1, the reference point for SRS-RSRP can be the UE's antenna connector. For frequency range 2, SRS-RSRP can be measured based on the combined signal from the antenna element corresponding to a given receiver branch. For both frequency ranges 1 and 2, if receiver diversity is used by the UE, the reported SRS-RSRP value may not be lower than the corresponding SRS-RSRP of any of the individual receiver branches. SRS-RSRP may be applicable within the RRC_CONNECTED frequency band.

[0073] The CLI Received Signal Strength Indicator (CLI-RSSI) is defined as the linear average of the total received power (e.g., in [W]) observed only in configured OFDM symbols within the configured measurement time resources of the configured measurement bandwidth from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc. For frequency range 1, the reference point for RSSI can be the UE's antenna connector. For frequency range 2, CLI-RSSI can be measured based on the combined signal from the antenna element corresponding to a given receiver branch. For both frequency ranges 1 and 2, if receiver diversity is used by the UE, the reported CLI-RSSI value may not be lower than the corresponding CLI-RSSI of any of the individual receiver branches. CLI-RSSI may be applicable within the RRC_CONNECTED frequency band.

[0074] Regarding the mode indication for inter-UE CLI measurements, in order to measure CLI among multiple UEs, it is expected that each UE measures CLI from any of the other UEs. In a system with N UEs, if half-duplex technology is used, then there exists a first UE transmitting a reference signal and a second UE performing CLI measurements on the resource associated with the reference signal, where N(N-1) = O(N) 2 ( ) different combinations.

[0075] Figure 2 Example 200 of the combinations in a UE according to aspects of this disclosure is described. As illustrated, the number of Tx / Rx combinations in N UEs is O(N). 2 In urban areas and other congested locations, the number of CLIs can be potentially large. In Example 200, inter-cell CLIs between UEs are indicated by solid arrows, while intra-cell CLIs between UEs are indicated by dashed arrows.

[0076] Furthermore, in the presence of beamforming, such as in FR2 or mmWave bands, each transmitting UE can apply M different candidate Tx beams, and each receiving UE can apply M different candidate Rx beams. This produces an O(M) Tx-Rx beam pair between every two UEs. 2 There are ) combinations. This produces a total of O(N) combinations across multiple N UEs. 2 M 2 M reference signals are used for beam-based CLI measurements, each applying M candidate beams for either UL Tx or DL ​​Rx. For example, if each reference signal uses one symbol (per beam per UE), then this translates to the number of symbols required for CLI measurements, or generally the resource and latency overhead of CLI measurements.

[0077] If CLI measurements are infrequent, the resource and latency overhead can be negligible in the long run. However, UEs may need to perform CLI measurements frequently to account for factors such as mobility and environmental changes affecting the effective channels within the UE.

[0078] There exists a way to reduce the overhead to below O(N). 2 M 2 This can be done in a way that allows multiple UEs to simultaneously perform measurements on the same reference signal from a transmitting UE. For example, if multiple UEs simultaneously perform measurements on the same reference signal from a transmitting UE, then the number of times the UE transmits can be reduced from O(N). 2 This reduces the total cost from O(NlogN) to O(NlogN), as discussed in more detail below. 2 M 2 ) decreased to O(M 2 NlogN).

[0079] In order to reduce the measurement overhead from O(N) 2The computation time is reduced to O(NlogN), considering multiple N network entities in the vicinity (e.g., gNB). Each network entity is assigned T bits (b T-1 The bitmap is ...b1b0)2, where T is the order of log2N. CLI measurements are performed in T time intervals 0, 1, ..., T-1, where during each time interval j, a reference signal is transmitted by each UE with the j-th bit in the assigned bitmap equal to 1, and a reference signal is received by each UE with the j-th bit in the assigned bitmap equal to 0 to perform the measurement. Since multiple UEs can transmit the reference signal simultaneously, the resources allocated to the reference signal can be multiplexed in the frequency domain (FDM) to prevent collisions.

[0080] This method provides that, for every two UEs having assigned bitmaps a and b, there exists at least one time interval j, wherein one UE transmits and the other UE receives. Therefore, for Each CLI time interval ensures that every channel between any two UEs is measured by at least one of the two UEs. If the channels are reciprocal and the UEs can transmit CLI measurement results, then... One time interval is sufficient.

[0081] In some cases, transmitting CLI measurement results within a UE may be impractical. Therefore, it may be desirable to allow each UE to measure the channel to and from any of the other UEs, without relying on channel reciprocity. For this purpose, T additional time intervals can be used, where in each time interval j, a reference signal is transmitted via each UE with the j-th bit in the assignment bitmap equal to 0, and the reference signal is received via each UE with the j-th bit in the assignment bitmap equal to 1 to perform the measurement. In this case, the first T time intervals may be referred to as the first round, and the second T time intervals may be referred to as the second round.

[0082] Alternatively, two consecutive time intervals may be associated with an index j∈{0,1,…,T-1}, wherein in the first time interval, a reference signal is transmitted via each UE having a bit of 1 in the assigned bitmap, and a reference signal is received via each UE having a bit of 0 in the assigned bitmap to perform a measurement; and conversely, in the second time interval, a reference signal is transmitted via each UE having a bit of 0 in the assigned bitmap, and a reference signal is received via each UE having a bit of 1 in the assigned bitmap to perform a measurement.

[0083] The two alternatives are equivalent, i.e., two rounds of T intervals versus T groups of two consecutive intervals, meaning the order of reference signal transmission in one is the same as the arrangement of reference signal transmissions in the other. Therefore, both alternatives are expected to require similar amounts of time and frequency resources. Other arrangements or configurations of reference signal transmissions may also be used.

[0084] By using the above methods, in total Each time interval is sufficient for each UE to receive a reference signal from any other UE within at least one time interval.

[0085] In each time interval, the total O(M) can be used 2 M reference signal resources (e.g., symbols) are used to measure the interference of each of the M candidate Tx beams applied by the attacker UE to each of the M candidate Rx beams applied by the victim network entity (e.g., gNB). Details of Tx / Rx beamforming in each time interval are discussed in more detail below. The total overhead of beam-based CLI measurements across all UEs can then be calculated using O(M) reference signal resources (e.g., symbols) to measure the interference of each of the attacker UE's M candidate Tx beams to each of the M candidate Rx beams applied by the victim network entity (e.g., gNB). 2 Achieve the overhead of NlogN.

[0086] Figure 3 Example 300 illustrates a timeline for the transmission of reference signals for backhaul and air signaling used in cross-link interference management between user equipment, in accordance with aspects of this disclosure. Example 300 illustrates a timeline for the transmission of reference signals by multiple UEs according to the method discussed herein.

[0087] The timeline in Example 300 is based on a two-round alternative, namely, a first round 302 associated with a reference signal transmitted by a UE having a 1 in the i-th bit of its assignment bitmap, and a second round 304 associated with a reference signal transmitted by a UE having a 0 in the i-th bit of its assignment bitmap. Each round may include T time intervals, referred to as resource timings, as illustrated at 306. Each resource timing may include reference signal transmission for Tx and / or Rx beam scanning. For Tx beam scanning, a first beamforming configuration or spatial filter on the Tx side may change from one reference signal (resource) to another, while a second beamforming configuration or spatial filter on the Rx side may remain fixed. Conversely, for Rx beam scanning, a first beamforming configuration or spatial filter on the Tx side may remain fixed, while a second beamforming configuration or spatial filter on the Rx side may change from one reference signal (resource) to another.

[0088] The timelines based on other alternative reference signal arrangements are basically similar in principle, except that the order in which the reference signals are transmitted may be different.

[0089] In each resource time slot, multiple N UEs are partitioned into two groups: Tx UEs, which transmit a reference signal during the resource time slot, and Rx UEs, which receive the reference signal and perform measurements on it during the resource time slot. In one or more embodiments, a UE does not change from Tx mode to Rx mode within a resource time slot, or vice versa. However, it should be noted that resource time slots are a concept that may not be mapped to consecutive time resources; for example, a UE may change from Tx mode to Rx mode between two non-consecutive partitions of a resource time slot. Non-consecutive resource mapping of resource time slots can be another instance of alternative permutations of reference signals, which is expected to produce similar amounts of time and frequency resources.

[0090] Regarding the mode indication for SRS-RSRP measurements based on the above method, in one or more embodiments, the UE may receive an SRS configuration containing information about resources allocated to the SRS. The UE may further receive an indication of a bitmap associated with the SRS configuration. The UE may receive the bitmap in the SRS configuration or via separate signaling. The UE may also receive CLI reports, such as the configuration of an SRS-RSRP report.

[0091] The UE can determine which symbols will be used to transmit SRS and which symbols will be used for CLI measurements based on the bitmap.

[0092] In one or more embodiments, the UE may determine 2MT symbols for SRS transmission, where M represents one or both of the number of candidate Tx beams for SRS transmission or the number of Rx beams for CLI (e.g., SRS-RSRP) measurements, and T represents the length of the bitmap.

[0093] The 2MT symbols include a first plurality of MT symbols and a second plurality of MT symbols. In the first plurality of MT symbols:

[0094] • If the first bit in the bitmap is equal to '1', then the UE can use the first M symbols to transmit SRS, and if the first bit in the bitmap is equal to '0', then the UE can use the first M symbols to measure CLI from other UEs;

[0095] • If the second bit in the bitmap is equal to '1', then the UE can use a second set of M symbols to transmit SRS; and if the second bit in the bitmap is equal to '0', then the UE can use a second set of M symbols to measure CLI from other UEs;...

[0096] • If the Tth bit in the bitmap is equal to '1', then the UE can use the Tth Mth symbols to transmit SRS, and if the Tth bit in the bitmap is equal to '0', then the UE can use the Tth Mth symbols to measure CLI from other UEs.

[0097] In the second or more MT symbols:

[0098] • If the first bit in the bitmap is equal to '0', then the UE can use the first M symbols to transmit SRS, and if the first bit in the bitmap is equal to '1', then the UE can use the first M symbols to measure CLI from other UEs;

[0099] • If the second bit in the bitmap is equal to '0', then the UE can use a second set of M symbols to transmit SRS; and if the second bit in the bitmap is equal to '1', then the UE can use a second set of M symbols to measure CLI from other UEs;...

[0100] • If the Tth bit in the bitmap is equal to '0', then the UE can use the Tth Mth symbols to transmit SRS, and if the Tth bit in the bitmap is equal to '1', then the UE can use the Tth Mth symbols to measure CLI from other UEs.

[0101] For each set of M symbols, the UE can apply M different Tx beams to SRS transmission or M different Rx beams to CLI measurement. If both Tx and Rx beam scanning are performed, the method can be modified to use multiple M... 2 One symbol, not multiple M symbols. If beam scanning is not performed, the method can be achieved by setting M=1.

[0102] The UE can transmit a CLI report containing measurement results to the serving network entity (e.g., gNB). The CLI report can contain up to N-1 CLI measurement results, such as SRS-RSRP values, where N represents the total number of UEs configured with SRS and CLI reports. The CLI report can further contain an index associated with each of the CLI measurement results. A first index indicates which UE the CLI report is associated with. A second index indicates a beam index, such as an integer in the range 0, 1, ..., M-1.

[0103] Alternatively, the UE may determine the MT symbol for SRS transmission, wherein:

[0104] • If the first bit in the bitmap is equal to '1', then the UE can use the first M symbols to transmit SRS, and if the first bit in the bitmap is equal to '0', then the UE can use the first M symbols to measure CLI from other UEs;

[0105] • If the second bit in the bitmap is equal to '1', then the UE can use a second set of M symbols to transmit SRS; and if the second bit in the bitmap is equal to '0', then the UE can use a second set of M symbols to measure CLI from other UEs;...

[0106] • If the Tth bit in the bitmap is equal to '1', then the UE can use the Tth Mth symbols to transmit SRS, and if the Tth bit in the bitmap is equal to '0', then the UE can use the Tth Mth symbols to measure CLI from other UEs.

[0107] Regarding resource element (RE) allocation, the resources used by different UEs transmitting SRS during resource timings can be multiplexed in one or both of the time and frequency domains. Any or both of these multiplexing schemes provide resource orthogonality in OFDM-based communications, which is useful for accurate channel and interference measurements. However, each multiplexing scheme has its advantages and disadvantages.

[0108] Time division multiplexing (TDM) allows more frequency resources to be used for each reference signal, thus allowing for more accurate measurements. However, the time overhead and delay can be too high. In practice, at most a few REs per symbol per resource block (RB) are allocated to a single reference signal.

[0109] Frequency domain multiplexing (FDM) reduces time overhead and delay by allowing multiple reference signals to be transmitted on a single time resource (e.g., OFDM symbol).

[0110] Typically, the RRC configures and assigns REs for each reference signal. These REs usually remain fixed as long as the configuration is valid. For example, this means that some subcarriers in the RB are assigned to the SRS, and they will not change over time as long as the SRS configuration is valid.

[0111] This fixed RE allocation can be inefficient for at least some of the SRS methods discussed in this paper. In the methods discussed in this paper, a number of symbols are configured and allocated for multiple UEs to transmit SRS in each resource opportunity. However, different subsets of UEs may transmit SRS in each resource opportunity. For example, when N is a power of 2, N / 2 UEs transmit SRS in each resource opportunity, while other N / 2 UEs may perform measurements on the SRS.

[0112] It should be noted that since SRS can be transmitted on a single symbol, the terms subcarrier and RE are used interchangeably in this document.

[0113] It should also be noted that the terms "mode ID number" and "mode bitmap" are used interchangeably in the methods discussed herein. However, it should also be noted that the mode ID number used in the methods discussed herein can be used to determine the frequency domain resource allocation for one or both of SRS transmissions or measurements, while the mode bitmap can be used for time domain resource allocation. In various implementations, the mode ID number and mode bitmap can be directly associated through configuration or standard specifications. For example, a binary representation of the mode ID number can be used as the mode bitmap, or vice versa. Alternatively, the mode ID number for frequency domain resource allocation and the mode bitmap for time domain resource allocation can be indicated or determined separately.

[0114] In one or more implementations, the RE allocated to each UE is fixed. In some instances, the RE may be determined based on the mode ID number configured for the UE. For example, a UE with mode ID number 0 is allocated a first subset of subcarriers, a UE with mode ID number 1 is allocated a second subset of subcarriers, and so on. These subsets may be non-overlapping. When the UE transmits SRS on a symbol, the UE uses the allocated subcarriers for SRS transmission.

[0115] Figure 4 Example 400 illustrates a fixed allocation of REs to mode IDs for backhaul and air signaling used for cross-link interference management between user equipment, in accordance with aspects of this disclosure. Example 400 illustrates a fixed allocation of REs to four mode IDs. The RE assigned to mode ID 0 is represented by a diagonal line from the lower left to the upper right, the RE assigned to mode ID 1 is represented by sparse dots, the RE assigned to mode ID 2 is represented by a diagonal line from the upper left to the lower right, and the RE assigned to mode ID 4 is represented by dense dots.

[0116] A UE may not transmit SRS on certain REs allocated to it for SRS transmission. One example is when the UE is in Rx mode during a resource timing event. Another example is when the UE's SRS transmission is deactivated. In this case, different implementation schemes are possible for the UE using the REs. The following are example implementation schemes.

[0117] In one or more implementations, the UE may not use the RE and may leave it empty, for example, allocating zero energy or power to signals on the symbol. Specifically, uplink transmissions by the UE on the symbol or downlink communications by the UE on the symbol may be punctured at the RE. The transmitter of the signal may perform rate matching around the RE.

[0118] Alternatively, the UE may use REs for communication instead of SRS transmission. The UE may use REs based on the premise that communication will not interfere with CLI measurements. This implementation attempts to use unused REs for other purposes.

[0119] Alternatively, the gNB can configure, schedule, or trigger SRS transmissions on unused REs. SRS can be used for one or both of intra-cell or inter-cell UE-to-UE CLI measurements. Since the UE in Rx mode is performing measurements on the associated symbol, it can also perform inter-cell interference (ICI) if it is informed of the configuration parameters of the reference signal. This allows for uniform CLI, ICI, or Channel State Information (CSI) measurements by multiplexing SRS and other RSs on different REs of the symbol.

[0120] Similarly, other nearby UEs can interrupt their communication on subcarriers on the symbol and perform rate matching.

[0121] In one or more embodiments, the first UE may interrupt communication at an RE on which the second UE is configured to transmit SRS. Communication may be interrupted regardless of whether the second UE is transmitting on an RE in the current resource time, for example, even if the second UE is in Rx mode in the current resource time, or if the SRS transmission by the second UE may be deactivated.

[0122] Alternatively, the first UE may interrupt communication around the RE only if the second UE intends to use the RE for SRS transmission during the current resource time.

[0123] Regarding variable allocation, in one or more implementations, REs are not assigned to individual UE SRSs. Instead, each UE determines whether to use an RE and which REs to use based on configuration information (e.g., a mode ID number configured for the UE).

[0124] In one instance, multiple UEs transmitting on a symbol or in a resource timing containing a symbol are ordered based on their mode ID numbers. The first UE in the ordering list then uses a first subset of subcarriers, the second UE in the ordering list uses a second subset of subcarriers, and so on. Since the multiple UEs and therefore the ordering list differ between one resource timing and another, the subcarriers used by each UE at one time may differ from those used by the UE at another. Nevertheless, as long as the configuration information is provided to the UE performing CLI measurements, the UE can unambiguously determine which REs are associated with which UE.

[0125] As a numerical example, consider multiple UEs configured with N=8 SRS. Each UE is configured with a mode ID number between (000)2 and (111)2. Assuming the most significant bit (MSB) is prioritized for bit mapping to resource timings without loss of generality, for example: in the first resource timing of the first round, the UE with mode ID number (1xx)2 transmits SRS; in the second resource timing of the first round, the UE with mode ID number (x1x)2 transmits SRS; in the third resource timing of the first round, the UE with mode ID number (xx1)2 transmits SRS; in the first resource timing of the second round, the UE with mode ID number (0xx)2 transmits SRS; in the second resource timing of the second round, the UE with mode ID number (x0x)2 transmits SRS; and in the third resource timing of the second round, the UE with mode ID number (xx0)2 transmits SRS.

[0126] Therefore, the RE allocation in each of the three resource opportunities in each round is different. For example, in the first resource opportunity of the first round, a UE with the following mode ID number transmits SRS (in ascending order): {4,5,6,7}; in the third resource opportunity of the second round, a UE with the following mode ID number transmits SRS (in ascending order): {0,2,4,6}.

[0127] As can be seen, UEs with mode IDs 4 and 6 transmit SRS in both of these instance resource times, but their positions in the sorting list are different. Therefore, the subsets of subcarriers they use in these instance resource times are also different.

[0128] Figure 5 Example 500 illustrates the variable allocation of REs to mode IDs for backhaul and air signaling in support of aspects of this disclosure for cross-link interference management between user equipment. Example 500 illustrates the variable allocation of REs to eight mode IDs. In the first resource opportunity of the first round, the RE assigned to mode ID 4 is described using a diagonal line from the lower left to the upper right, the RE assigned to mode ID 5 is described using a sparse point, the RE assigned to mode ID 6 is described using a diagonal line from the upper left to the lower right, and the RE assigned to mode ID 7 is described using a dense point. In the third resource opportunity of the second round, the RE assigned to mode ID 0 is described using a diagonal line from the lower left to the upper right, the RE assigned to mode ID 2 is described using a sparse point, the RE assigned to mode ID 4 is described using a diagonal line from the upper left to the lower right, and the RE assigned to mode ID 6 is described using a dense point.

[0129] Regarding the configuration of RE allocation, in one or more implementations, for fixed RE allocation, REs (subcarriers) in each RB on a symbol can be assigned to each mode ID number. This is feasible when the number of mode ID numbers N is not greater than the number of REs per RB.

[0130] Alternatively, REs (subcarriers) in every 2nd RB, every 3rd RB, etc., on a symbol can be assigned to each mode ID number. This allows the number of mode ID numbers N to be greater than the number of REs per RB.

[0131] In one instance, such allocation can be configured by indicating several pattern ID numbers. Furthermore, the configuration can instruct REs to be allocated in each RB, every second RB, every third RB, and so on.

[0132] In another instance, the density ρ of REs per RB can be indicated. If ρ is greater than or equal to 1, then at least one RE per RB is assigned to each pattern ID number. This assignment is possible if N is less than or equal to the number of REs per RB. If ρ is less than 1, then REs in every ρ-th RB on the symbol are assigned to each pattern ID number.

[0133] In both instances, the configuration can indicate which REs in each RB are assigned to each pattern ID number, for example, by indicating the start RB number, start RE number, end RE number, etc. Furthermore, the configuration can indicate whether the assigned REs are consecutive or follow a pattern, such as a comb pattern.

[0134] Alternatively, the above method can be extended to the case of variable RE allocation, where N / 2 RE sets can be assigned to N pattern ID numbers on symbols in each resource timing.

[0135] Alternatively, a combination of methods may be used.

[0136] In the descriptions of various implementation schemes, the UE can use the mode ID number to determine which resources to use in the time and frequency domains. In the time domain, the UE can use the mode ID number to determine when it is in Tx or Rx mode. In the frequency domain, the UE can use the mode ID number to determine which REs to use based on a variable RE allocation method.

[0137] In one or more implementations, the UE may use the same mode ID number to determine which resources are used for SRS transmission or CLI measurement in either or both of the time and frequency domains.

[0138] Alternatively, the UE may use a first mode ID number (or similar parameter) to determine time-domain resources (symbols) and a second mode ID number (or similar parameter) to determine frequency-domain resources (subcarriers or REs) for one or both of SRS transmissions or CLI measurements.

[0139] Regarding alternative resource mode parameters, in one or more implementations, a mode ID number, indicated by a base of 0, 1, ..., N-1, can be used as a 'bit string' or bitmap to determine which resources are allocated to which UE's SRS. For example, a '1' (or '0') value in a bit position (or code point) of the mode ID number can indicate a Tx mode (or Rx mode).

[0140] Alternatively, the resource mode parameter may include a bit sequence, a sequence of {'Tx', 'Rx'}, etc., instead of a cardinality. The sequence can then be similarly used as a 'bit string' or a bitmap.

[0141] Regarding beam repetition, for beam-based SRS Tx / Rx, the number L of SRS (resources) in each resource opportunity can be determined based on the number of one or both of the Tx or Rx beams for the UE configured with SRS. The number of one or both of the Tx or Rx beams can refer to the number per UE, per antenna port, per physical antenna, etc.

[0142] In a symmetrical isomorphic scenario, consider that each of N UEs configured with SRS can use any one of M candidate Tx beams for SRS transmission and any one of M candidate Rx beams for SRS reception and CLI measurements. The M 'candidate' beams may not be all beams supported by the UE for one or both of Tx or Rx, but rather beams that have been shown to be suitable for DL ​​or UL communication with the gNB serving the UE during CSI or beam acquisition.

[0143] This generates the M of the Tx-Rx beam between each transmitting UE and each receiving UE. 2 This combination is called symmetric because the number of Tx beams is equal to the number of Rx beams, and it is called isomorphic because the number is the same across the UE.

[0144] In this case, L can be set to M. 2 A full Tx or Rx beam scan in each resource opportunity between the Tx UE and Rx UE used for the resource opportunity. M 2 The beam combination can be in any arbitrary order, but the UE should be aware of the ordering and therefore it should be determined based on one or both of the specifications or configuration.

[0145] One possible ordering is the Rx-priority beam scan between any of the Tx UEs and any of the Rx UEs in the resource timing, as follows:

[0146] • For the first M SRS, the Tx UE is fixed to transmit the first Tx beam of the M SRS, while the Rx UE uses M different Rx beams, each of which is used to receive one of the M SRS.

[0147] For the second M SRS, the Tx UE is fixed to transmit the second Tx beam for the M SRS, while the Rx UE uses M different Rx beams, each used to receive one of the M SRS;...

[0148] • For the Mth SRS, the Tx UE is fixed to transmit the Mth Tx beam of the M SRS, while the Rx UE uses M different Rx beams, each of which is used to receive one of the M SRS.

[0149] Another prioritization method can be referred to as a Tx-priority beam scan between any of the Tx UEs and any of the Rx UEs in the resource timing, as follows:

[0150] • For the first M SRS, the Tx UE uses M different Tx beams, each of which is used to transmit one of the M SRSs, while the Rx UE is fixed to receive the first Rx beam of the M SRSs.

[0151] For the second M SRS, the Tx UE uses M different Tx beams, each used to transmit one of the M SRSs, while the Rx UE is fixed to receive the second Rx beam of the M SRSs;...

[0152] • For the Mth SRS, the Tx UE uses M different Tx beams, each of which is used to transmit one of the M SRSs, while the Rx UE is fixed to receive the Mth Rx beam of the M SRSs.

[0153] It should be noted that other types of sorting can be used, but these two sorting methods may be more practical.

[0154] Configuration or specifications can indicate whether Rx-first or Tx-first beam scanning will be applied to each UE. This can be indicated by the parameter Beam-Sweeping-Type, which takes values ​​from {'RxFirst', 'TxFirst'}, etc. Alternatively, if the repetition parameter is configured, it can be interpreted as indicating Rx-first or Tx-first based on standard specifications.

[0155] In this case, the configuration may also indicate one or more of the following parameters: the number of SRS (resources) L, from which the UE can determine that the M value is equal to The number of beams M can be interpreted by the UE as either or both of the number of Tx beams and the number of Rx beams; the number of Tx beams M; or the number of Rx beams M.

[0156] Regarding the asymmetric isomorphic scenario, the difference between this scenario and the previous scenario (symmetric isomorphism) lies in the number M of the Tx beams. tx The number of Rx beams M rx They can be different. However, the number across UEs is the same, hence the term 'isomorphic'.

[0157] In this case, L can be set to M. tx M rx A full Tx or Rx beam scan in each resource timing between the Tx UE and Rx UE for the resource timing.

[0158] Similar to symmetrical scenarios, the UE should be aware of M tx M rx How are beam combinations ordered? For asymmetric scenarios, Rx-priority beam scanning and Tx-priority beam scanning are similarly defined, except that Tx UE applications M... tx One of the beams, and Rx UE application M rx In addition to one of the beams.

[0159] In this case, the configuration may also indicate one or more of the following parameters: the number of SRS (resources) L; the number of Tx beams M. tx ; or the number of Rx beams M rx .

[0160] Regarding the asymmetric heterogeneous scenario, the difference between this scenario and the previous scenario (symmetric isogeneous) lies in the number M of the Tx beams. tx Or the number of Rx beams M rx One or both of them can be different across UE.

[0161] In this scenario, one UE might complete beam scanning faster than another. For example, if UEi has M... tx,i There are Tx beams, and UE j has M tx,j Tx beams, and if M tx,i >M tx,j Therefore, in resource situations where both UEs are in Tx mode, UEj may complete Tx beam scanning faster than UEi (e.g., with fewer SRS transmissions).

[0162] In this case, the bottleneck is the maximum number of beams, for example, the maximum number of Tx beams across the UE for SRS transmission and the maximum number of Rx beams across the UE for SRS reception and measurement.

[0163] Therefore, in one or more implementations, L can be set as M. tx M rx M tx Set to the maximum M across all UEs tx,i And M rx Set to the maximum M across all UEs rx,i .

[0164] Similar to the previous scenario, the UE should be aware of M tx M rx How are beam combinations ordered? For asymmetric scenarios, Rx-priority beam scanning and Tx-priority beam scanning are similarly defined, except that Tx UE applications M... tx One of the beams, and Rx UE application M rx In addition to one of the beams.

[0165] In one or more implementations, a UE with a smaller number of Tx or Rx beams than the maximum value can use the corresponding resources across all beam scans. For example, in a Tx-priority beam scan, a UE with a smaller number of Tx or Rx beams can use the corresponding resources across all beam scans. tx The number of Tx beams M tx,i At UE i: If the UE uses M tx The first M of a set of SRS resources tx,i If there are SRS resources, then the UE uses M tx The first M in all other sets of SRS resources tx,i One SRS resource; if the UE uses M tx The last M in a set of SRS resources tx,i If there are SRS resources, then the UE uses M tx The last M in all other sets of the SRS resources tx,i One SRS resource.

[0166] The configuration may also indicate one or more of the following parameters: the number of SRS (resources) L; the number of Tx beams M. tx The number of Rx beams M rx ; multiple Tx beams associated with each UE i or mode ID number i; or multiple Rx beams M associated with each UE i or mode ID number i. rx,i .

[0167] If all UEs are notified of individual M across all UEs tx,i and M rx,iThey might be able to determine the number of SRS resources for each resource opportunity by identifying which UEs are in Tx mode and which are in Rx mode. For example, when a large number of UEs with Tx beams are in Rx mode during a resource opportunity, a smaller number of SRS resources can be allocated to that resource opportunity. However, this approach could lead to undesirable excessive complexity in real-world scenarios.

[0168] Regarding symmetrical heterogeneous scenarios, this scenario can be regarded as a special case of asymmetrical heterogeneous scenarios.

[0169] Regarding CLI reporting, the UE can be configured to measure and report CLI results, such as SRS-RSRP. The CLI can be measured at Layer 3 (as specified in Release 16) or at one or both of Layer 1 and Layer 2 (L1 / L2). The UE then measures the CLI and reports it to the serving network entity (e.g., gNB).

[0170] Upon receiving a CLI report, a first network entity (e.g., gNB) may generate a message containing one or more of the reported CLIs in a CLI report IE. The network entity (e.g., gNB) may then send the CLI report IE to a second network entity (e.g., gNB) that serves at least one attacker UE or one or both of core network functions (e.g., Access and Mobility Management Function (AMF)).

[0171] The CLI report IE may contain one or more CLI measurement fields. Each CLI measurement field is generated based on the CLI reported by the UE and contains one or more of the following parameters: the value of the interference associated with the attacker UE, such as SRS-RSRP; or the associated beam ID or SRS resource index.

[0172] In one or more implementations, a network entity (e.g., a gNB) may periodically send CLI reports (IEs). For example, a network entity (e.g., a gNB) may generate and send a CLI report (IE) at the end of each SRS transmission and measurement cycle. More generally, a network entity (e.g., a gNB) may generate and send a CLI report at the end of each P cycle of SRS transmission and measurement (e.g., at the end of each 2TP resource opportunity).

[0173] Alternatively, a network entity (e.g., a gNB) may send a CLI report IE when certain conditions are met. An example is shown below.

[0174] In the first instance, if the reported CLI (e.g., SRS-RSRP) exceeds a threshold, the network entity (e.g., gNB) can generate and send a CLI report IE containing the reported CLI. The threshold can be determined based on at least one of the following: configuration signaling within the network entity (e.g., gNB), the core network, or the implementation scheme.

[0175] In the second instance, if the reported CLI increases (or decreases) by more than the 'incremental CLI' value compared to the associated previously reported value, then the network entity (e.g., gNB) can generate and send a CLI report IE containing the new reported CLI. The 'incremental CLI' threshold can be determined based on at least one of the following: configuration signaling within the network entity (e.g., gNB), the core network, or the implementation scheme.

[0176] In the third instance, if the duration since the last CLI report of a free network entity (e.g., gNB) exceeds the CLI report validity expiration threshold, then the network entity (e.g., gNB) may generate and send a CLI report IE based on the latest reported CLI. Generally, the expiration period can be calculated from the last CLI report IE, the expiration period from the last CLI report IE containing a CLI reported by a UE, and so on. The CLI report IE validity expiration threshold may be determined based on configuration signaling within the network entity (e.g., gNB), or at least one of the core network or implementation scheme.

[0177] In another implementation, a combination of methods may be used. For example, a network entity (e.g., a gNB) may send CLI reports (IEs) periodically or when one or both of the following conditions are met.

[0178] Regarding CLI handling, if a network entity (e.g., a gNB) receives a CLI report (IE), it can take action to mitigate the negative impact of CLIs on UEs that cause excessive CLIs. In one or more implementations, the network entity (e.g., a gNB) can reduce the UL Tx power associated with the attacker UE on all beams or specifically on high-interference beams.

[0179] However, if a core network function, such as the AMF, receives a CLI report, the core network function can send signaling via backhaul (e.g., NG interface) to the network entity (e.g., gNB) serving the UE that caused the excessive CLI.

[0180] In one or more implementations, the core network may send a UL power control message or IE to a network entity (e.g., a gNB) via an NG interface, wherein the message or IE may include an indication to reduce the UE transmit power by a certain amount. The indication may be applied to all UL transmissions to the network entity (e.g., the gNB). In response, the network entity (e.g., the gNB) may signal one or more UEs to reduce the UL transmit power by the indicated amount when transmitting UL signals containing SRS.

[0181] Alternatively, the indication may be associated with a beam ID, SRS resource indication (SRI), etc. In response, a network entity (e.g., a gNB) may signal to one or more UEs to reduce the UL transmit power by the indicated amount when applying a Tx beam (spatial filter) that is the same Tx beam associated with the indicated beam ID or SRI. This UL power reduction may be applied to any or all UL signals that include an SRS associated with the beam ID or SRI.

[0182] If the UL power control message or IE associates UL transmit reduction parameters with a beam ID or SRI, then the message or IE may include multiple such indications. In response, a network entity (e.g., a gNB) may signal one or more UEs to reduce the UL transmit power associated with a first SRI by a first amount, reduce the UL transmit power associated with a second SRI by a second amount, and so on, as indicated by the message.

[0183] In some implementations, a network entity (e.g., a gNB) may be unable to comply with the indicated UL transmit power reduction. This could be because, for example, the network entity (e.g., the gNB) wants to maintain a minimum UL transmit power for communicating with the UE.

[0184] If a network entity (e.g., a gNB) is unable to reduce the UL transmit power by one or more indicated amounts, it may send a negative acknowledgment (NACK) message or IE containing one or more indications of the amount of UL transmit power reduction that cannot be applied. If a smaller reduction amount is possible, the network entity (e.g., a gNB) may indicate that amount in the NACK message or IE. Alternatively, the network entity (e.g., a gNB) may send an acknowledgment (ACK) message or IE containing one or more indications of the amount of UL transmit power reduction that can be applied. In some instances, a message or IE may carry one or more ACK or NACK indications associated with one or more UL transmit power reduction amounts indicated in the UL power control message or IE. No ACK / NACK message or IE may be interpreted as an ACK or NACK for the entire UL power control message.

[0185] Regarding activation or deactivation signaling, the UE may receive signaling to activate or deactivate one or both of SRS transmission or measurement. Activation or deactivation messages or IEs may include one or more of the following parameters: a value for activation or on (ON) or deactivation or off (OFF); and indications associated with SRS transmission configuration, SRS-RSRP reporting configuration, etc.

[0186] Upon receiving a message, the UE may initiate or cease transmitting or measuring one or both of the SRS associated with the indicated SRS transmission configuration, SRS-RSRP reporting configuration, etc., depending on whether one or both of the SRS transmission or measurement is activated or deactivated.

[0187] In some implementations, activation or deactivation messages can be used to initiate or deactivate both SRS transmission and SRS-RSRP reporting for the UE.

[0188] In addition, the gNB can receive backhaul or OTA signaling for activating or deactivating CLI reports to other network entities (e.g., gNBs) or to the core network. Activation or deactivation messages or IEs may include one or more of the following parameters: values ​​for activation, on / off, deactivation, or shutdown; indications associated with SRS configuration; and indications associated with CLI reporting periodic or conditional parameters.

[0189] Upon receiving a message, a network entity (e.g., a gNB) may initiate or cease sending at least one of the CLI report IEs associated with the indicated SRS configuration, CLI report periodicity, or CLI report condition parameters, depending on whether the CLI report is activated or deactivated.

[0190] Regarding mode indication for a large number of UEs, when implementing the method discussed above, it can be assumed that multiple time and frequency resources are assigned to multiple N UEs for transmitting SRS for CLI acquisition purposes.

[0191] However, allocating resources to a fixed set of UEs has drawbacks. In cells with a large number of UEs that do not communicate frequently, assigning resources to each UE leads to significant underutilization of SRS resources or frequent changes to SRS configuration information. This is particularly problematic in the case of inter-cell UE CLI, where configuration information is exchanged or updated via backhaul.

[0192] As an alternative, multiple time-frequency resources can be used for K UEs, where K can be arbitrarily large, but resources are only allocated from the multiple time-frequency resources to a smaller number of N UEs for SRS transmission. This method aims to reduce the resource overhead for SRS transmission without requiring frequent updates to SRS configuration information in the gNB.

[0193] Various implementation schemes operate as follows. A second network entity (e.g., gNB) serving a potential attacker UE configures one or more SRSs suitable for accommodating N UEs. The second network entity (e.g., gNB) sends SRS configuration information to a first network entity (e.g., gNB) serving a potential victim UE. This information is semi-static and may not be updated frequently. The second network entity (e.g., gNB) may also indicate to the first network entity (e.g., gNB) as many as possible K UEs that can transmit SRS according to the SRS configuration. The second network entity (e.g., gNB) may then indicate to the first network entity (e.g., gNB) which of the K UEs uses which of the resources according to the SRS configuration. The second network entity (e.g., gNB) may indicate at any time a subset of the K UEs comprising N UEs, where N may be significantly less than K. The first network entity (e.g., gNB) may then use the indication to notify the UEs so that they determine which attacker UEs' CLIs will be measured. Alternatively, the first gNB may use the information without directly notifying the victim UE.

[0194] Further details are as follows.

[0195] In one or more embodiments, a first network entity (e.g., gNB) may receive SRS configuration from a second network entity (e.g., gNB), wherein the configuration message contains a bitmap of length K associated with the SRS configuration, wherein its maximum N bits are set to '1'. The SRS configuration may assign any of the following numbers of symbols according to the methods discussed above: T, 2T, MT, 2MT, M 2 T or 2M 2 T. In each case, T can be the bit width of the parameter in the SRS configuration, and M can be one or both of the number of Tx candidate beams for SRS transmission or the number of Rx candidate beams for CLI measurements. In some implementations, N can be equal to 2. T Or, equivalently, T can be of order log2N.

[0196] Then, each bit in the bitmap can be associated with 1, 2, M, 2M, M 2 Or 2M 2 Each SRS symbol is associated with a UE. If a bit equals a first value, such as '1', it indicates that the UE using the associated SRS symbol can transmit SRS on the configured SRS resources; otherwise, a second value, such as '0', indicates that the UE cannot transmit SRS on the configured SRS resources. The indication can be associated with a duration, such as P milliseconds, the period of a frame, or a time slot. The value of P can also be indicated in the message.

[0197] Alternatively, the maximum value of the MN bits is set to '1', where each plurality of M bits can be coupled to N=2T The symbol used by one of the M transmit beams is associated with the symbol used by the UE.

[0198] Alternatively, a bitmap may contain S smaller bitmaps, each of which may be associated with one of K durations of P milliseconds, frames, or time slots. The value of one or both of K or P may be configured (semi-static) or indicated (dynamic) among network entities (e.g., gNBs).

[0199] Alternatively, instructions from a second network entity (e.g., gNB) to an attacker UE may be transmitted directly to the victim UE via network entity-to-UE (e.g., gNB-to-UE OTA) signaling, as discussed in more detail below.

[0200] Regarding the mode indication used for coordinating scheduling and beamforming, regardless of whether the SRS-based CLI configuration follows the CLI framework specified in version 16 or the techniques discussed herein, if the victim UE or the network entity scheduling the victim UE (e.g., gNB) does not know when to schedule a given attacker UE to make an uplink transmission, then the SRS-RSRP obtained and reported to the network can only be considered as a worst-case CLI.

[0201] In the case of intra-cell UE-to-gNB communication, the situation may be simple: the serving network entity (e.g., gNB) has the scheduling information of the attacker UE and can use that information to schedule communication with the victim UE. However, in the case of inter-cell communication, the network entity serving the victim UE (e.g., gNB) does not know when the attacker UE can transmit uplink signals that might interfere with the victim UE's downlink signals.

[0202] In the above discussion, several implementation schemes and examples are discussed based on the mode indication used for transmitting SRS or measuring CLI (e.g., SRS-RSRP). The indicated mode can be used by the UE to determine the resources assigned to SRS transmission in one or both of the time domain or frequency domain.

[0203] The following section discusses methods for indicating the UL transmission mode of the UE. It should be noted that mode indication is generally distinguished as follows.

[0204] The first and second mode indications discussed above (e.g., mode indications for inter-UE CLI measurements and mode indications for a large number of UEs) indicate which potential attacker UEs use which resources and / or according to which SRS configuration to transmit SRS. These mode indications can be used for CLI measurements (e.g., SRS-RSRP) performed by one or more potential victim UEs. The result is the acquisition of inter-UE CLI information, which can then be used for various CLI disposition methods, such as UL power reduction as previously described.

[0205] The third mode instruction discussed below indicates which potential attacker UE (whose CLI has been measured by one or more potential victim UEs) uses which resources to transmit UL signals to its serving network entity (e.g., gNB). The result here is to handle CLI by coordinating one or both of the scheduling or beamforming in UE communications (specifically, the attacker UE's UL transmission and the victim UE's DL reception).

[0206] The various implementation schemes discussed below operate as follows. A second network entity (e.g., gNB) serving a potential attacker UE configures one or more SRSs for N active UEs, a total of K UEs, or one or more of the M Tx beams for each UE. The second network entity (e.g., gNB) sends the SRS configuration information to a first network entity (e.g., gNB) serving a potential victim UE. This information is semi-static and may not be updated frequently. The second network entity (e.g., gNB) may also indicate to the first network entity (e.g., gNB) that up to N or K UEs can transmit SRS according to the SRS configuration. The second network entity (e.g., gNB) may then indicate to the first network entity (e.g., gNB) which of the N or K UEs uses which of the resources for uplink transmission, and / or which of the M Tx beams is applied to each UE. The indication may be explicitly or implicitly associated with the SRS configuration. The first network entity (e.g., gNB) may then use the indication for coordinating one or both of scheduling or beamforming.

[0207] The following are examples of how the first gNB can use instructions for one or both of coordination scheduling or beamforming.

[0208] Example 1: If UE1 has reported a transitional CLI from UE2, and if a second network entity (e.g., gNB) has indicated that UE2 is about to transmit an uplink signal, then the first network entity (e.g., gNB) can avoid scheduling downlink communication with UE1.

[0209] Example 2: If UE1 has reported an overcurrent CLI associated with UE2’s Tx beam, and if a second network entity (e.g., gNB) has indicated that UE2 is about to transmit uplink signals when applying the Tx beam, then the first network entity (e.g., gNB) may avoid scheduling downlink communication with UE1.

[0210] Example 3: If UE1 has reported an overcurrent CLI from UE2 when it is using a certain Rx beam, and if a second network entity (e.g., gNB) has indicated that UE2 is about to transmit an uplink signal, then the first network entity (e.g., gNB) can avoid scheduling downlink communication with UE1 through the Rx beam.

[0211] Example 4: If UE1 has reported a transitional CLI associated with UE2’s Tx beam when it is applying a certain Rx beam, and if a second network entity (e.g., gNB) has indicated that UE2 is about to transmit uplink signals when applying the Tx beam, then the first network entity (e.g., gNB) can avoid scheduling downlink communication with UE1 through the Rx beam.

[0212] Example 5: If UE1 has reported an overcurrent CLI from UE2, and if a second network entity (e.g., gNB) has indicated that UE2 is about to transmit an uplink signal on one or both of certain time or frequency resources, then the first network entity (e.g., gNB) may avoid scheduling downlink communication with UE1 on one or both of the time or frequency resources.

[0213] Instances of time resources include symbols, time slots, subframes, frames, multiple frames, etc. The associated information exchanged between network entities (e.g., gNBs) can be semi-static or dynamic.

[0214] Examples of frequency resources include carriers, component carriers (CC), bandwidth portions (BWP), subbands, frequency ranges, and one or more PRBs. The associated information exchanged within a gNB can be semi-static or dynamic.

[0215] Further details are as follows.

[0216] In one or more implementations, a first network entity (e.g., gNB) may receive SRS configuration from a second network entity (e.g., gNB), wherein the configuration message contains a bitmap associated with one or more of N active UEs, a total of K UEs, or M Tx beams for each UE. The first network entity (e.g., gNB) may then receive SRS configuration associated with 1, 2, M, 2M, M. 2 Or 2M 2 A dynamic indication of the bitmap associated with each SRS symbol. If a bit equals a first value, such as '1', it indicates that the UE using the associated SRS symbol can transmit uplink signals; otherwise, a second value, such as '0', indicates that the UE cannot transmit uplink signals. The indication can be associated with a duration, such as P milliseconds, the period of a frame, or a time slot. The value of P can also be indicated in the message.

[0217] Alternatively, the maximum value of the MN bits is set to '1', where each plurality of M bits can be coupled with M=2. T The symbol used by one of the M transmit beams is associated with the symbol used by the UE.

[0218] Alternatively, the bitmap may include S smaller bitmaps, each of which may be associated with one of K durations of P milliseconds, frames, or time slots. The values ​​of K and / or P may be configured (semi-static) or indicated (dynamic) among network entities (e.g., gNBs).

[0219] Alternatively, instructions from a second network entity (e.g., gNB) to an attacker UE may be transmitted directly to the victim UE via network entity-to-UE (e.g., gNB-to-UE OTA) signaling, as discussed in more detail below.

[0220] Regarding ACLR indication, the methods discussed above focus on co-channel interference, such as interference caused by a signal being transmitted on the same channel. However, when using duplex enhancement (SBFD, dynamic TDD), adjacent channel interference can also be significant.

[0221] A major problem with obtaining adjacent channel interference (OLI) is that it is not as straightforward as obtaining it from a reference signal. One method for obtaining OII is by measuring RSSI, which uses the basic assumption that a single dominant interference is causing the interference. Unlike RSRP-type interference measurements, RSSI-type measurements do not allow for the differentiation of contributions from multiple signals with comparable received signal strength. Alternatively, OII can be calculated by dividing co-channel interference by ACLR in the real number domain. Alternatively, OII can be calculated by subtracting ACLR from co-channel interference in the logarithmic or decibel domain.

[0222] In one or more embodiments, an attacker UE or a network entity serving the attacker UE (e.g., a gNB) may indicate one or more values ​​of the neighboring channel leakage ratio (ACLR) to a neighboring network entity (e.g., a gNB) or the victim UE it is serving.

[0223] In one instance, a first network entity (e.g., gNB) may receive from a second network entity (e.g., gNB) the ACLR value corresponding to the worst-case ACLR among a plurality of M UEs. The message from the second network entity (e.g., gNB) may further include T, 2T, MT, 2MT, M 2 T or 2M 2 The indication of the association of SRS configuration on T symbols, where T = log2N.

[0224] In another example, a first network entity (e.g., gNB) may receive multiple N ACLR values ​​from a second network entity (e.g., gNB), where each ACLR value may be associated with one of N UEs. Messages from the second network entity (e.g., gNB) may further include T, 2T, MT, 2MT, M... 2 T or 2M2 The indication of the association of SRS configuration on T symbols, where T = log2N.

[0225] In one or more implementations, the ACLR value associated with the attacker UE can be reported by the UE as a capability parameter to a second network entity (e.g., gNB). The second network entity (e.g., gNB) can then indicate the ACLR value associated with the attacker UE, or the worst-case ACLR value associated with multiple attacker UEs, to a first network entity (e.g., gNB). The first network entity (e.g., gNB) can then combine this information with co-channel interference results reported by the victim network entity (e.g., gNB), such as SRS-RSRP, to obtain adjacent channel interference (e.g., adjacent channel CLI-RSSI) or worst-case adjacent channel interference (e.g., worst-case adjacent channel CLI-RSSI).

[0226] Alternatively, the ACLR value associated with the attacker UE can be measured by a second network entity (e.g., gNB). The second network entity (e.g., gNB) can then indicate the ACLR value associated with the attacker UE, or the worst-case ACLR value associated with multiple attacker UEs, to the first network entity (e.g., gNB). The first network entity (e.g., gNB) can then combine this information with co-channel interference results reported by the victim network entity (e.g., gNB), such as SRS-RSRP, to obtain adjacent channel interference (e.g., adjacent channel CLI-RSSI) or worst-case adjacent channel interference (e.g., worst-case adjacent channel CLI-RSSI).

[0227] Regarding backhaul signaling and OTA signaling, the signaling discussed above (e.g., regarding ACLR indication) allows network entities (e.g., gNB) to coordinate CLI measurements for UEs, scheduling among UEs in different cells, and beamforming, etc. Various implementation methods utilize signaling from network entities (e.g., gNB) for one or both of semi-static configuration information and dynamic signaling.

[0228] One candidate for signaling is the backhaul, such as the Xn or NG interface. In this case, the message may be an IE containing a bitmap of length N, MN, SN, etc. The IE may further contain an indication associated with the SRS configuration, which can be transmitted separately over the same backhaul interface.

[0229] Figure 6Example 600 illustrates the NG-RAN architecture and backhaul interface for backhaul and air signaling supporting cross-link interference management between user equipment, according to aspects of this disclosure. Example 600 illustrates the NG-RAN architecture and backhaul interface in 5G NR. The NG interface is shown with solid lines, and the Xn interface is shown with dashed lines. Example 600 includes the AMF or User Plane Function (UPF) component of the 5G core (5GC) at 602, and the gNB and enhanced LTE eNB (ng-eNB) in the NG-RAN at 604.

[0230] One problem with backhaul signaling is that the medium may be too slow to dynamically transmit such scheduling and beamforming information. UEs are potentially mobile, and their traffic can be bursty or dynamic. Furthermore, scheduling a large number of UEs may cause the serving network entity (e.g., gNB) to indicate different candidate Tx beams for the uplink transmission of any given UE.

[0231] Therefore, in addition to or alternatively, information can be transmitted over the air (OTA).

[0232] OTA signaling can be implemented through the physical control channel in a network entity (e.g., gNB).

[0233] In one or more implementations, OTA signaling can be executed via a new physical control channel (referred to herein as the Physical Network Link Control Channel (PNCCH)).

[0234] Figure 7 Example 700 illustrates the relationships between entities and links in an example system supporting backhaul and over-the-air signaling for cross-link interference management between user equipment, according to aspects of this disclosure. Wired interfaces are illustrated with solid lines, and wireless interfaces are illustrated with dashed arrow lines. Example 700 illustrates a system including network entities 702 and 704, which signal to the core network or AMF 706 via the NG interface, signal to each other via the Xn interface, and conduct OTA signaling with each other. Furthermore, UE 708 is illustrated as signaling to network entity 702 via uplink and downlink signaling, and to UE 710 via sidelink signaling.

[0235] The Physical Control Channel (PNCCH) can be mapped to one or both of the existing or new transport and logical channels at higher layers.

[0236] In some instances, the PNCCH may be mapped to one or both of the Network Link Transport Channel (NCH) or the Network Link Logical Control Channel (NCCH). Alternatively, the PNCCH may be mapped to one or both of existing transport or logical channels, such as the CCCH and BCCH.

[0237] Figure 8 Example 800 illustrates a mapping of new and existing channels for backhaul and air signaling in support of aspects of this disclosure for cross-link interference management between user equipment. Example 800 illustrates channel mapping for network links used for OTA signaling between gNBs. As illustrated, the PNCCH can be mapped to one or more of the NCCH at 802, the CCCH at 804, or the BCCH at 806.

[0238] Alternatively, OTA signaling can be performed via existing channels, such as the Physical Downlink Control Channel (PDCCH). It should be noted that while downlink control signaling is generally intended for reception by the UE, the PDCCH is not designed to prevent its reuse for transmission to other network entities (e.g., gNBs), especially where the channel can provide a faster channel compared to backhaul interfaces, such as Xn, in terms of either higher data rates or lower latency.

[0239] In either case, when a first network entity (e.g., gNB) intends to transmit a physical control signal to a second network entity (e.g., gNB), the first network entity (e.g., gNB) may scramble the signal using a Radio Network Temporary Identifier (RNTI) known to the second network entity (e.g., gNB). The second network entity (e.g., gNB) may also be informed of other configuration information for receiving OTA signaling, such as resources used by the first network entity (e.g., gNB) for transmitting signals.

[0240] The new RNTI is referred to in this paper as the Network Link RNTI (NL-RNTI). In several instances, the NL-RNTI may be the new RNTI or an existing RNTI reused to scramble OTA signaling.

[0241] In one instance, NL-RNTI can be assigned to any or all OTA signaling within a network entity (e.g., a gNB) via a standard specification. A first network entity (e.g., a gNB) then scrambles the OTA signaling via NL-RNTI, and a second network entity (e.g., a gNB) receives and descrambles the signal via NL-RNTI. In this scenario, any or all communication among multiple network entities (e.g., gNBs) can be descrambled by any one of the network entities (e.g., gNBs).

[0242] By extension, multiple NL-RNTIs can be assigned to OTA signaling within a network entity (e.g., a gNB) via standard specifications. If no further coordination is performed, each network entity (e.g., a gNB) can attempt to receive OTA signaling from any other network entity (e.g., a gNB) by descrambling the signal using any or all of the multiple NL-RNTIs.

[0243] In another example, multiple NL-RNTIs can be assigned to OTA signaling within a gNB via standard specifications, but further coordination is needed to indicate which NL-RNTI will be used for communication between or within a specific network entity (e.g., gNB). For instance, a network entity (e.g., gNB) within a cluster can use one NL-RNTI for OTA signaling within the cluster's network entities (e.g., gNBs). In this case, each network entity (e.g., gNB) within the cluster can descramble OTA signals from any other network entity (e.g., gNB) within the cluster. In this way, communication across different clusters is separated by assigning different NL-RNTIs.

[0244] In some instances, coordination for assigning NL-RNTI to OTA signaling channels can be implemented via communication on the backhaul interface. In one instance, NL-RNTI can be assigned by a core network function, such as an AMF, via the NG interface. In this case, the AMF can indicate the NL-RNTI to one or both of the first network entity (e.g., gNB) that transmits the OTA signal or the second network entity (e.g., gNB) that receives the OTA signal.

[0245] In another instance, a first network entity (e.g., a gNB) transmitting an OTA signal may indicate an NL-RNTI for the OTA signaling channel to a second network entity (e.g., a gNB) intended to receive the OTA signal. The indication can be sent via the Xn interface.

[0246] Conversely, in another instance, a second network entity (e.g., gNB) intended to receive OTA signals from the first v can indicate the NL-RNTI for the OTA signaling channel to the first network entity (e.g., gNB). The indication can be sent via the Xn interface.

[0247] In several instances, OTA signaling is transmitted via a digital c consisting of the following two parts. init Scrambling is performed: NL-RNTI and ID. In this case, the generator of the scrambling sequence c(i) can be started as follows:

[0248] c init =n RNTI ·2 15 +n ID

[0249] Where n RNTI It is an NL-RNTI used for OTA signaling, and n ID It's an ID.

[0250] In one instance, the ID may be a cell ID associated with a first network entity (e.g., gNB) that transmits the OTA signal, a second network entity (e.g., gNB) that receives the OTA signal, or a combination thereof.

[0251] In other instances, IDs can be assigned via signaling on the backhaul. In one instance, IDs are assigned by core network functions, such as the AMF, via the NG interface. In another instance, a first network entity (e.g., a gNB) transmitting an OTA signal can indicate to a second network entity (e.g., a gNB) intended to receive the OTA signal an ID associated with the first network entity (e.g., the gNB), such as a cell ID. In yet another instance, a second network entity (e.g., a gNB) intended to receive an OTA signal from the first network entity (e.g., the gNB) can indicate to the first network entity (e.g., the gNB) an ID associated with the second network entity (e.g., the gNB), such as a cell ID.

[0252] OTA signaling control channels, such as PNCCH, can follow similar principles for resource allocation and other configurations as those used for PDCCH. Information regarding resource allocation and other configurations can be transmitted backhaul to network entities (e.g., gNB).

[0253] In one instance, a core network function, such as an AMF, may indicate resource allocation and other configuration information to one or both of a first network entity (e.g., a gNB) or a second network entity (e.g., a gNB). The indication may be signaled via one or more NG interfaces.

[0254] In another instance, a first network entity (e.g., gNB) intended to transmit OTA signals can instruct a second network entity (e.g., gNB) intended to receive OTA signals via the Xn interface to allocate resources and other configuration information for the OTA signaling control channel.

[0255] Regarding OTA without backhaul, in the description of several implementations and examples of OTA signaling, it is assumed that OTA signaling is used to transmit dynamic information, such as mode indications for CLI measurements, mode indications for coordination scheduling and beamforming, ACLR indications, etc. However, semi-static information, such as the configuration of reference signals, can be transmitted through backhaul, such as Xn and NG interfaces, in network entities (e.g., gNBs) and the core network.

[0256] In addition, or alternatively, OTA signaling can also be used to exchange semi-static configurations and instructions. A first network entity (e.g., gNB) intended to transmit an OTA signal may indicate in a System Information Block (SIB), Master Information Block (MIB), etc., how to receive the OTA signal or how to establish a control channel (e.g., PNCCH or PDCCH). In one example, a second network entity (e.g., gNB) intended to receive an OTA signal may detect a Synchronization Signal Block (SSB) from the first network entity (e.g., gNB), decode one or both of the MIB or SIB received from the first network entity (e.g., gNB), and then receive the OTA signal. Similar signaling can be used in the opposite direction, for example, communication from the second network entity (e.g., gNB) back to the first network entity (e.g., gNB).

[0257] In other instances, once the second network entity (e.g., gNB) decodes one or both of the MIB or SIB received from the first network entity (e.g., gNB), the second network entity (e.g., gNB) can initiate OTA signaling from the first network entity (e.g., gNB), such as random access signaling on a random access channel (RACH), to establish an OTA channel, such as PNCCH or PDCCH. The channel can then be used for bidirectional or unidirectional communication between the two network entities (e.g., gNB). In one instance, the RACH can be dedicated to OTA signaling, in which case the second network entity (e.g., gNB) does not need to contend with the UE for transmitting the RACH preamble to the first network entity (e.g., gNB). In another instance, the second network entity (e.g., gNB) can obtain information about the RACH used by the UE from the Physical Broadcast Channel (PBCH) broadcast by the first network entity (e.g., gNB).

[0258] Alternatively, semi-static information can be exchanged among network entities (e.g., gNBs) through a combination of backhaul and OTA signaling.

[0259] The method for network entity-to-network entity (e.g., gNB-to-gNB) OTA signaling can be extended to network entity-to-UE (e.g., gNB-to-UE) OTA signaling. The following figure illustrates an OTA signaling scenario where a UE (referred to as UE1) receives signals from a gNB (referred to as gNB2) that is never serving the UE.

[0260] Figure 9Example 900 illustrates OTA signaling to the UE for backhaul and over-the-air signaling supporting cross-link interference management between user equipments, according to aspects of this disclosure. Wired interfaces are illustrated with solid lines, and wireless interfaces are illustrated with dashed arrow lines. Example 900 illustrates OTA signaling from a network entity 904 (e.g., a gNB) not serving UE 902 to UE 902. It also illustrates network entities 904 and 906 signaling to the core network or AMF 908 via the NG interface, and to each other via the Xn interface. Furthermore, it illustrates UE 902 signaling to network entity 906 via uplink and downlink signaling.

[0261] It should be noted that the difference between the “OTA link” from network entity 904 (e.g., gNB2) to UE 902 and the downlink between network entity 906 (e.g., gNB1) and UE 902 is that the latter is established through initial access and RRC connection establishment. The downlink is paired with an uplink, which can be duplexed in the time or frequency domain (e.g., TDD or FDD). However, an OTA link is not necessarily preceded by initial access or RRC connection establishment. Instead, in some instances, UE 902 may receive signals broadcast by network entity 904 (e.g., gNB2).

[0262] The implementation schemes discussed in this article can be extended to utilize direct OTA links between the UE and non-serving network entities (e.g., gNBs), some of which are discussed below. It should be noted that extensions of other scenarios, implementation schemes, and examples not listed below are straightforward.

[0263] Regarding the extension of mode indication for inter-UE CLI measurements among a large number of UEs, several implementation schemes and examples can be extended to utilize direct network entity-UE (e.g., gNB-UE) OTA links for mode indication for inter-UE CLI measurements.

[0264] In various instances, network entity 904 (e.g., gNB2) configures SRS for a total of K UEs, from which a maximum of N UEs can be instructed to transmit SRS. Network entity 904 (e.g., gNB2) then configures network entity 906 (e.g., gNB1) with inter-cell UE-to-UE CLI (SRS-RSRP) reporting based on measured SRS. UE 902 can then be notified which of the total K UEs will transmit SRS during a specific time period.

[0265] In one or more implementations, UE 902 is notified via backhaul signaling. In this case, network entity 904 (e.g., gNB2) may indicate to network entity 906 (e.g., gNB1) which UEs will transmit SRS directly (via Xn signaling) or indirectly (via NG signaling) via backhaul signaling. For example, the indication may include a bitmap of length K, where the maximum N bits are set to '1'. Upon receiving the indication from network entity 904 (e.g., gNB2), network entity 906 (e.g., gNB1) may relay the information to UE 902 by transmitting downlink control signals, such as DCI messages.

[0266] Alternatively, UE 902 may be notified via network entity-to-network entity (e.g., gNB-gNB) OTA signaling. In this case, network entity 904 (e.g., gNB2) may indicate to network entity 906 (e.g., gNB1) which UEs will transmit SRS via OTA signaling (e.g., the network link control channel as previously proposed). For example, the indication may include a bitmap of length K, where the maximum N bits are set to '1'. Upon receiving the indication from network entity 904 (e.g., gNB2), network entity 906 (e.g., gNB1) may relay the information to UE 902 by transmitting downlink control signals, such as DCI messages.

[0267] Alternatively, UE 902 may be notified via OTA signaling between network entity 906 and UE (e.g., gNB-UE). In this case, network entity 906 (e.g., gNB1) does not need to relay information from network entity 904 (e.g., gNB2) to UE 902. Instead, network entity 904 (e.g., gNB2) may broadcast a mode indication over the air, which UE 902 may receive directly.

[0268] Regarding the implementation of OTA signaling from a network entity to a UE (e.g., gNB to UE), similar to the case of a network entity-to-network entity (e.g., gNB-gNB) OTA link, in several instances, UE 902 may assign an existing or new RNTI via network signaling or standard specifications. Then, in several instances, UE 902 may combine the RNTI with an ID to descramble and decode OTA signals from a non-serving network entity 904 (e.g., gNB2). In several instances, the ID may be a cell ID associated with the non-serving network entity 904 (e.g., gNB2), which may be signaled to the UE indirectly (e.g., through a network entity 906 (e.g., gNB1) serving UE 902) or directly (e.g., through signal broadcast by the non-serving network entity 904 (e.g., gNB2)).

[0269] Regarding the techniques discussed in this article, the following should be noted.

[0270] The text and flowcharts can be arranged to describe different steps or actions in the example implementation plan.

[0271] In practice, each configuration can be provided by one or more configurations. Earlier configurations may provide a subset of parameters, while later configurations may provide another subset. Additionally or alternatively, later configurations may override values ​​provided by earlier configurations or pre-configurations.

[0272] Configuration can be provided through one or more of the following methods: Xn / NG signaling, Radio Resource Control (RRC) signaling, Media Access Control (MAC) signaling, physical layer signaling such as Downlink Control Information (DCI) messages, or others. Configuration may include pre-configured or semi-static configurations provided by at least one of the standards, vendors, networks, or operators (e.g., OAM). Each parameter value received by configuring or indicating its value can override previous values ​​for similar parameters.

[0273] Although the IAB is frequently cited, the techniques discussed in this article may be applicable to wireless relay nodes and other types of wireless communication entities.

[0274] L1 / L2 control signaling can refer to control signaling in Layer 1 (physical layer) or Layer 2 (data link layer). Specifically, L1 / L2 control signaling can refer to L1 control signaling (such as one or more DCI messages or UCI messages) or L2 control signaling (such as MAC messages). The format and interpretation of L1 / L2 control signaling can be determined by at least one of standards, configurations, or other control signaling.

[0275] This document refers to Message or Message Element (IE). 'IE' is an acronym frequently used in LTE and NR specifications to refer to configurations at Layer 3 and higher. An IE can be contained within a message moving from one layer to another or from one entity to another. Additionally or alternatively, an IE can be contained within another IE. In the discussion herein, the terms 'IE' and 'message' are used interchangeably when a message directly or indirectly contains an IE.

[0276] In fact, any parameter discussed in this article may appear as a linear function of the parameter described in the signaling or specification.

[0277] This article discusses measurements for performing beam training on a reference signal. Alternatively, in some implementations, measurements may be performed on resources not necessarily configured for the reference signal, but instead the node may measure the received signal power and obtain the Received Signal Strength Indicator (RSSI), etc.

[0278] Beam indication is frequently mentioned in this discussion. In fact, according to standard specifications, beam indication can refer to the indication of a reference signal by an ID or indicator, a resource associated with the reference signal, spatial relation information containing information about the reference signal, or the reciprocity of the reference signal (in the case of beam correspondence).

[0279] Although SRS is used for inter-UE CLI measurements, other reference signals (such as the new type of cross-link interference reference signal (CLI-RS)) can be used for the same purpose.

[0280] In some scenarios, the terms antenna, panel, and antenna panel are used interchangeably. An antenna panel can be hardware for transmitting and / or receiving radio signals at frequencies below 6 GHz, such as frequency range 1 (FR1), or above 6 GHz, such as frequency range 2 (FR2), or millimeter wave (mmWave). In some embodiments, the antenna panel may comprise an array of antenna elements, where each antenna element is connected to hardware, such as a phase shifter that allows a control module to apply spatial parameters to the transmission and / or reception of signals. The resulting radiation pattern may be referred to as a beam, which may be single-peaked or non-single-peak, and may allow devices (e.g., UE, node, network entity) to amplify signals transmitted or received from one or more spatial directions.

[0281] In some scenarios, antenna panels may or may not be virtualized as antenna ports in the specification. Antenna panels can be connected to the baseband processing module via radio frequency (RF) chains for both transmit (outbound) and receive (inbound) directions. The device's capabilities regarding the number of antenna panels, their duplex capabilities, their beamforming capabilities, etc., may be transparent or opaque to other devices. In some implementations, capability information may be transmitted via signaling, or in others, capability information may be provided to the device without signaling. Where such information is available to other devices, such as a CU, it can be used for signaling or local decision-making.

[0282] In some scenarios, an antenna panel can be a physical or logical antenna array containing a set of antenna elements or antenna ports that share a common or significant portion of an RF chain (e.g., in-phase / quadrature (I / Q) modulators, analog-to-digital (A / D) converters, local oscillators, phase-shift networks). An antenna panel can also be a logical entity having physical antennas mapped to logical entities. The mapping from physical antennas to logical entities can vary depending on the implementation. Communication (receiving or transmitting) on ​​at least a subset of the antenna elements or antenna ports (also referred to herein as active elements) of the antenna panel for radiating energy requires biasing or energizing the RF chain, resulting in current consumption or power dissipation (including power amplifier / low-noise amplifier (LNA) power consumption associated with the antenna elements or antenna ports) in devices (e.g., nodes) associated with the antenna panel. The phrase "active for radiating energy" as used herein is not intended to be limited to transmitting functions and also covers receiving functions. Therefore, the active antenna elements used for radiating energy can be coupled simultaneously or sequentially to a transmitter to transmit radio frequency energy or to a receiver to receive radio frequency energy, or typically to a transceiver to perform its intended function. Communication on the active elements of the antenna panel enables the generation of radiation patterns or beams.

[0283] In some scenarios, depending on the implementation, a "panel" may have at least one of the following functionalities as an operational role: a unit for independently controlling its Tx beam, a unit for independently controlling its transmit power, and a unit for independently controlling its transmit timing. The "panel" may be transparent to another node (e.g., a next-hop neighbor). Under certain conditions, another node or network entity may assume that the mapping between the device's physical antennas and the logical entity "panel" remains unchanged. For example, the condition may include up to the next update or report from the device, or include a duration during which the network entity assumes the mapping will not change. The device may report its capabilities regarding the "panel" to the network entity. Device capabilities may include at least the number of "panels". In one implementation, the device may support transmission from one beam within the panel; for multiple panels, more than one beam (one beam per panel) may be used for transmission. In another implementation, UL transmission may be supported / used with more than one beam per panel.

[0284] In some scenarios, antenna ports are defined such that the channel transmitting symbols on the antenna port can be inferred from the channel transmitting another symbol on the same antenna port.

[0285] If the large-scale properties of a channel transmitting symbols on one antenna port can be inferred from the channel transmitting symbols on another antenna port, then the two antenna ports are called quasi-co-located (QCL). Large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and the spatial Rx parameter. The two antenna ports can be quasi-located with respect to subsets of the large-scale properties, and different subsets of the large-scale properties can be indicated by the QCL type. The QCL type can indicate which channel properties are the same between two reference signals (e.g., at the two antenna ports). Therefore, the reference signals can be linked to each other with respect to what assumptions the devices can make about their channel statistics or QCL properties. For example, the qcl type can take one of the following values. Other qcl types can be defined based on a combination of one or more large-scale properties:

[0286] -'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}

[0287] -'QCL-TypeB': {Doppler frequency shift, Doppler spread}

[0288] -'QCL-TypeC': {Doppler shift, average delay}

[0289] -'QCL-TypeD': {space Rx parameter}.

[0290] Spatial Rx parameters may include one or more of the following: angle of arrival (AoA), dominant AoA, average AoA, angle spread, power angle spectrum (PAS) of AoA, average AoD (angle of departure), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, spatial channel correlation, etc.

[0291] QCL-Type A, QCL-Type B, and QCL-Type C are applicable to all carrier frequencies, but QCL-Type D may only be applicable to higher carrier frequencies (e.g., mmWave, FR2, and higher), where the device may essentially be unable to perform omnidirectional transmission; for example, the device will need to form a beam for directional transmission. For QCL-Type D between two reference signals A and B, reference signal A is considered spatially co-located with reference signal B, and the device may assume that reference signals A and B can be received using the same spatial filter (e.g., with the same Rx beamforming weights).

[0292] An "antenna port" in an implementation may be a logical port corresponding to a beam (generated by beamforming) or a physical antenna on the device. In some implementations, a physical antenna may be directly mapped to a single antenna port, where the antenna port corresponds to an actual physical antenna. Alternatively, a set or subset of physical antennas, or an antenna set, antenna array, or antenna subarray, may be mapped to one or more antenna ports after applying composite weights, cyclic delays, or both to the signal on each physical antenna. A physical antenna set may have antennas from a single module or panel or from multiple modules or panels. Weights may be fixed, such as in an antenna virtualization scheme, such as cyclic delay diversity (CDD). The procedure used to derive the antenna port from the physical antenna may be device-specific and transparent to other devices.

[0293] In some scenarios, the TCI state (Transmission Configuration Indicator) associated with a target transmission can indicate parameters used to configure the quasi-co-location relationship between the target transmission (e.g., the target RS of the demodulation (DM)-RS port of the target transmission during the transmission timing) and the source reference signal (e.g., SSB / CSI-RS / SRS) with respect to the quasi-co-location type parameters indicated in the corresponding TCI state. The TCI describes which reference signals are used as QCL sources and what QCL properties can be derived from each reference signal. The device can receive configurations of multiple transmission configuration indicator states of the serving cell for transmission on the serving cell (e.g., between the serving gNB and the smart repeater). In some described embodiments, the TCI state includes at least one source RS to provide a reference for determining the QCL and / or spatial filtering (device assumption).

[0294] In some scenarios, if the device is configured with a separate DL / UL TCI via RRC signaling, then a UL TCI status is provided. The UL TCI status may include a source reference signal that provides a reference for determining the UL spatial domain transmission filters in or across the configured CC / BWP set (e.g., Physical Uplink Shared Channel (PUSCH) or Dedicated Physical Uplink Control Channel (PUCCH) resources based on Dynamic Licensing / Configuration Licensing).

[0295] In some described implementations, if the device is configured with a joint DL / UL TCI via RRC signaling (e.g., a joint TCI or individual DL / UL TCI configuration based on RRC signaling), then a joint DL / UL TCI state is provided. The joint DL / UL TCI state refers at least to a common source reference RS used to determine both the DL QCL information and the UL spatial transmission filter. The source RS determined from the indicated joint (or common) TCI state provides a QCL type D indication (e.g., for device-specific PDCCH / Physical Downlink Shared Channel (PDSCH)) and is used to determine the CC or UL spatial transmission filter across the configured CC / BWP set (e.g., for UE-specific PUSCH / PUCCH). In one instance, the UL spatial transmission filter is derived from the RS of DL QCL type D in the joint TCI state. The spatial settings of the UL transmission can be based on the spatial relationships of the source RSs configured with a qcl-Type set to "typeD" in the joint TCI state.

[0296] In some scenarios, spatial relationship information associated with a target transmission can indicate parameters used to configure the spatial setup between the target transmission and a reference RS (e.g., SSB / CSI-RS / SRS). For example, the apparatus can use the same spatial domain filter used to receive a reference RS (e.g., a DL RS, such as an SSB / CSI-RS) to transmit the target transmission. In another instance, the apparatus can use the same spatial domain transmission filter used to transmit a reference RS (e.g., a UL RS, such as an SRS) to transmit the target transmission. The apparatus can receive multiple spatial relationship information configurations of the serving cell to perform transmission on the serving cell.

[0297] In some scenarios, if the device is configured with a separate DL / UL TCI via RRC signaling, then a UL TCI status is provided. The UL TCI status may include a source reference signal that provides a reference for determining the UL spatial domain transmission filter in or across the configured CC / BWP set (e.g., PUSCH based on dynamic licensing / configuration licensing, dedicated PUCCH resources).

[0298] In some scenarios, if the device is configured with a joint DL / UL TCI via RRC signaling (e.g., a joint TCI or individual DL / UL TCI configuration based on RRC signaling), then a joint DL / UL TCI state is provided. The joint DL / UL TCI state refers at least to a common source reference RS used to determine both the DL QCL information and the UL spatial transmission filter. The source RS determined from the indicated joint (or common) TCI state provides a QCL type D indication (e.g., for device-specific PDCCH / PDSCH) and is used to determine the CC or the UL spatial transmission filter spanning the configured CC / BWP set (e.g., for UE-specific PUSCH / PUCCH). In one instance, the UL spatial transmission filter is derived from the RS of DL QCL type D in the joint TCI state. The spatial settings of the UL transmission can be determined based on the spatial relationships of the source RSs configured with a qcl-Type set to "typeD" in the joint TCI state.

[0299] Therefore, in one or more embodiments, the techniques discussed herein introduce new signaling that allows for CLI processing between UEs by exchanging a small amount of SRS configuration associated with several UEs. A focus is placed on L1 / L2 aspects to propose methods for reducing SRS resources and for joint SRS transmission and CLI measurements by multiple UEs.

[0300] Alternatively, the UE receives an SRS configuration for inter-cell CLI measurements, where the SRS configuration contains information on joint resource allocation for several UEs. The UE also receives a CLI (SRS-RSRP) report configuration. The UE then determines which resources in the joint resource allocation are associated with the UE or the UE's beam and performs CLI measurements on those resources. Measurements on resources associated with the same UE (or the same beam of the UE) can be combined to improve measurement accuracy. The CLI results are then reported to the serving cell for scheduling and link adaptation.

[0301] Alternatively, the techniques discussed herein introduce one or both of a new backhaul or OTA signaling, which allows a first network entity serving the victim UE (e.g., a first gNB) to obtain additional information from a second network entity serving the attacker UE (e.g., a second gNB). The first network entity can then use this additional information, along with CLI results reported by the victim UE, for coordinating scheduling and beamforming, link adaptation, etc.

[0302] Alternatively or concurrently, a first network entity serving the victim UE (e.g., a first gNB) receives SRS configuration for inter-cell CLI measurements from a network entity serving multiple attacker UEs (e.g., a second gNB). Furthermore, in one or more embodiments, the first network entity receives additional information associated with the SRS configuration, indicating which UEs (or their beams) are available in the next P milliseconds. The first network entity can then combine this information with CLIs reported by the victim UE for coordinated scheduling and beamforming, link adaptation, etc. Alternatively or concurrently, the first network entity receives ACLR information from a second network entity, which, together with the reported CLIs, can be used to estimate adjacent channel interference, which can then be used for scheduling and link adaptation in adjacent channels.

[0303] Figure 10 This illustration illustrates an example of a block diagram 1000 of an apparatus 1002 supporting backhaul and air signaling for cross-link interference management between user equipment, according to aspects of this disclosure. Apparatus 1002 may be an example of network entity 102 as described herein. Apparatus 1002 may also be referred to as a device. Apparatus 1002 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Apparatus 1002 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 1004, memory 1006, transceiver 1008, and I / O controller 1010. These components may communicate electronically or be otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0304] Processor 1004, memory 1006, transceiver 1008, or various combinations thereof, or various components thereof, may be instances of components for performing various aspects of the present disclosure as described herein. For example, processor 1004, memory 1006, transceiver 1008, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0305] In some embodiments, processor 1004, memory 1006, transceiver 1008, or various combinations or components thereof may be implemented in hardware (e.g., as a communication management circuitry system). The hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured or otherwise supporting elements for performing the functions described herein. In some embodiments, processor 1004 and memory 1006 coupled to processor 1004 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 1006 are executed by processor 1004).

[0306] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured to, or otherwise support: receiving from a network entity a first signaling indicating an SRS configuration, the SRS configuration indicating associations between multiple resources and multiple devices; transmitting to a first device a second signaling indicating a CLI report configuration; receiving from the first device, according to the CLI report configuration, a third signaling indicating a CLI report, wherein the CLI report includes multiple CLI measurements associated with the multiple resources; and transmitting to the network entity a fourth signaling indicating a CLI report IE, the CLI report IE indicating, based on the CLI report and the associations between the multiple resources and the multiple devices, that one or more of the multiple devices cause excessive CLI.

[0307] Additionally or alternatively, the processor 1004 may be configured to or otherwise support: determining one or more of the plurality of devices causing the excessive CLI by: determining one or more CLI measurement results that are excessive and associated with one or more of the plurality of resources; determining one or more of the plurality of devices that are associated with one or more of the plurality of resources based on the association between the plurality of resources and the plurality of devices; and inferring that one or more of the devices causes the excessive CLI; wherein determining one or more CLI measurement results that are excessive includes comparing the CLI measurement results with a CLI threshold; wherein each of the plurality of resources includes at least one symbol or at least one resource element. One or more of the elements; wherein: the SRS configuration further includes an indication of the association between the plurality of resources and the plurality of transmit beams of the plurality of devices; the processor is configured to cause the device to determine that one or more of the plurality of transmit beams of one or more of the plurality of devices causes the excessive CLI; and the CLI report IE further indicates that one or more of the plurality of transmit beams of one or more of the devices causes the excessive CLI; wherein the processor is configured to cause the device to: receive an activation or deactivation indication associated with the SRS configuration; and in response to determining that the activation or deactivation indication indicates deactivation, instruct the first device to deactivate the CLI report; wherein the determination is made by the following To one or more of the plurality of devices of the over-CLI: receive from the network entity a pattern associated with the plurality of devices, wherein the pattern includes a plurality of fields, each of which is associated with one of the plurality of devices; determine that the device associated with the field transmits SRS in response to a field in the pattern being equal to a first value; and determine that the device does not transmit the SRS in response to a field in the pattern being equal to a second value; wherein: the pattern includes a bitmap field or is otherwise associated with it; each of the plurality of fields is a bit in the bitmap field; the first value is '1'; and the second value is '0'; wherein the processor is configured to enable the device to pass backhaul. One or more of the interfaces or over-the-air (OTA) receive the mode via a fifth signaling; wherein each of the plurality of CLI measurements is at least one of co-channel SRS-RSRP or co-channel CLI-RSSI; wherein: each of the plurality of CLI measurements is co-channel SRS-RSRP; and the one or more of the plurality of devices causing the excessive CLI are obtained by: obtaining one or more ACLR values ​​associated with the one or more of the plurality of devices; and calculating the adjacent channel CLI by combining the co-channel SRS-RSRP and the ACLR values; wherein the processor is configured to receive a fifth signaling indicating the ACLR value from the network entity;The calculation of the adjacent channel CLI includes at least one of the following: dividing the co-channel SRS-RSRP value by the associated ACLR value in the real number domain; or subtracting the ACLR value from the co-channel SRS-RSRP value in the logarithmic or decibel domain; wherein each of the device and the network entity is a base station or a TRP; wherein the CLI threshold is indicated by a core network function, by an OAM entity, by a standard, or according to an implementation scheme; wherein the CLI report is associated with a physical layer, MAC layer, or RRC layer.

[0308] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured to, or otherwise support: obtaining an RNTI associated with a PNCCH; receiving multiple OTA signals associated with the PNCCH from a network entity; and descrambling the multiple OTA signals by applying the RNTI.

[0309] Additionally or alternatively, the processor 1004 may be configured to support, or otherwise support, that: wherein the RNTI is indicated by at least one of a standard, by the core network, by the network entity on the backhaul interface, by the network entity in a broadcast signal, by the network entity in a system information block, or by an OAM entity; wherein the processor is configured to: obtain an ID; descramble the plurality of OTA signals by applying the RNTI and the ID; wherein the ID is a cell ID associated with the network entity; wherein obtaining the ID is receiving additional signaling indicating the ID from at least one of the core network, the network entity, or the OAB; wherein the PNCCH is mapped to at least one of NCH, NCCH, CCCH, or BCCH.

[0310] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured to, or otherwise support: transmitting to a network entity a first signaling indicating an SRS configuration indicating associations between multiple resources and multiple devices; and receiving from the network entity a second signaling indicating a CLI report IE, the CLI report IE indicating, based on the CLI report and the associations between the multiple resources and the multiple devices, that one or more of the multiple devices cause excessive CLI.

[0311] Additionally or alternatively, the processor 1004 may be configured to support: each of the plurality of resources comprising at least one symbol or one or more of at least one resource element; wherein: the SRS configuration further includes an indication of the association between the plurality of resources and a plurality of transmit beams of the plurality of devices; and the CLI report IE further indicates that the one or more of the plurality of transmit beams of the one or more devices causes the excessive CLI; wherein the processor is configured to cause the device to: transmit an activation or deactivation indication associated with the SRS configuration; wherein the processor is configured to cause the device to transmit third signaling to the network entity indicating one or more ACLR values ​​associated with one or more of the plurality of devices; wherein the device and each of the network entities is a base station or a TRP; wherein the CLI report is associated with a physical layer, MAC layer, or RRC layer.

[0312] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured to, or otherwise support: scrambling a plurality of OTA signals associated with the PNCCH by applying an RNTI associated with the PNCCH; and transmitting the plurality of OTAs to a network entity.

[0313] Additionally or alternatively, the processor 1004 may be configured to, or otherwise support, that: wherein the RNTI is indicated by at least one of a standard, by the core network, by the network entity on the backhaul interface, by the network entity in a broadcast signal, by the network entity in a system information block, or by an OAM entity; wherein the processor is configured to: obtain an ID; scramble the plurality of OTA signals by applying the RNTI and the ID; wherein the ID is a cell ID associated with the device; wherein the PNCCH is mapped to at least one of NCH, NCCH, CCCH, or BCCH.

[0314] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured or otherwise support a component for: receiving from a network entity a first signaling indicating an SRS configuration indicating associations between multiple resources and multiple devices; transmitting to a first device a second signaling indicating a CLI report configuration; receiving from the first device, according to the CLI report configuration, a third signaling indicating a CLI report, wherein the CLI report includes multiple CLI measurements associated with the multiple resources; and transmitting to the network entity a fourth signaling indicating a CLI report IE, the CLI report IE indicating, based on the CLI report and the associations between the multiple resources and the multiple devices, that one or more of the multiple devices cause excessive CLI.

[0315] Additionally or alternatively, the processor 1004 may be configured to or otherwise support: determining one or more of the plurality of devices causing the excessive CLI by: determining one or more CLI measurement results that are excessive and associated with one or more of the plurality of resources; determining one or more of the plurality of devices that are associated with one or more of the plurality of resources based on the association between the plurality of resources and the plurality of devices; and inferring that one or more of the devices causes the excessive CLI; wherein determining one or more CLI measurement results that are excessive includes comparing the CLI measurement results with a CLI threshold; wherein each of the plurality of resources includes at least one symbol or at least one of the resource elements. Multiple; wherein: the SRS configuration further includes an indication of the association between the multiple resources and multiple transmit beams of the multiple devices; the method further includes determining that one or more of the multiple transmit beams of one or more of the multiple devices cause the excessive CLI; and the CLI report IE further indicates that one or more of the multiple transmit beams of one or more devices cause the excessive CLI; it further includes: receiving an activation or deactivation indication associated with the SRS configuration; and in response to determining that the activation or deactivation indication indicates deactivation, instructing the first device to deactivate a CLI report; wherein the one or more of the multiple devices causing the excessive CLI are determined by: from the A network entity receives a pattern associated with the plurality of devices, wherein the pattern includes a plurality of fields, each of which is associated with one of the plurality of devices; determines that the device associated with the field transmits an SRS in response to a field in the pattern equaling a first value; and determines that the device does not transmit the SRS in response to a field in the pattern equaling a second value; wherein: the pattern includes a bitmap field or is otherwise associated with it; each of the plurality of fields is a bit in the bitmap field; the first value is '1'; and the second value is '0'; it further includes receiving the pattern via a fifth signaling through one or more of the backhaul interface or over-the-air (OTA); wherein the plurality of CLI measurements Each is at least one of co-channel SRS-RSRP or co-channel CLI-RSSI; wherein: each of the plurality of CLI measurements is co-channel SRS-RSRP; and one or more of the plurality of devices causing the excessive CLI are obtained by: obtaining one or more ACLR values ​​associated with the one or more of the plurality of devices; and calculating the neighboring channel CLI by combining the co-channel SRS-RSRP and the ACLR value; further comprising receiving a fifth signaling from the network entity indicating the ACLR value; wherein calculating the neighboring channel CLI includes at least one of: dividing the co-channel SRS-RSRP value by the associated ACLR value in the real number field;Alternatively, the ACLR value can be subtracted from the co-channel SRS-RSRP value in the logarithmic or decibel domain; wherein each of the devices and network entities implementing the method is a base station or TRP; wherein the CLI threshold is indicated by core network functions, by an OAM entity, by standards, or according to the implementation scheme; wherein the CLI report is associated with the physical layer, MAC layer, or RRC layer.

[0316] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured or otherwise support a mechanism for: obtaining an RNTI associated with a PNCCH; receiving a plurality of OTA signals associated with the PNCCH from a network entity; and descrambling the plurality of OTA signals by applying the RNTI.

[0317] Additionally or alternatively, the processor 1004 may be configured to support, or otherwise support, the following: wherein the RNTI is indicated by at least one of a standard, by the core network, by the network entity on the backhaul interface, by the network entity in a broadcast signal, by the network entity in a system information block, or by an OAM entity; further comprising: obtaining an ID; descrambling the plurality of OTA signals by applying the RNTI and the ID; wherein the ID is a cell ID associated with the network entity; wherein obtaining the ID is receiving additional signaling indicating the ID from at least one of the core network, the network entity, or the OAB; wherein the PNCCH is mapped to at least one of NCH, NCCH, CCCH, or BCCH.

[0318] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured or otherwise support a component for: transmitting to a network entity a first signaling indicating an SRS configuration indicating associations between a plurality of resources and a plurality of devices; and receiving from the network entity a second signaling indicating a CLI report IE, the CLI report IE indicating, based on the CLI report and the associations between the plurality of resources and the plurality of devices, that one or more of the plurality of devices cause excessive CLI.

[0319] Additionally or alternatively, the processor 1004 may be configured to support: each of the plurality of resources includes at least one symbol or one or more of at least one resource element; wherein: the SRS configuration further includes an indication of the association between the plurality of resources and the plurality of transmit beams of the plurality of devices; and the CLI report IE further indicates that the one or more of the plurality of transmit beams of the one or more devices causes the excessive CLI; it further includes: transmitting an activation or deactivation indication associated with the SRS configuration; it further includes transmitting third signaling to the network entity indicating one or more ACLR values ​​associated with one or more of the plurality of devices; wherein each of the device implementing the method and the network entity is a base station or a TRP; wherein the CLI report is associated with the physical layer, MAC layer, or RRC layer.

[0320] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured or otherwise support a component for: scrambling a plurality of OTA signals associated with the PNCCH by applying an RNTI associated with the PNCCH; and transmitting the plurality of OTAs to a network entity.

[0321] Additionally or alternatively, the processor 1004 may be configured to support, or otherwise support, that the RNTI is indicated by at least one of a standard, by the core network, by the network entity on the backhaul interface, by the network entity in a broadcast signal, by the network entity in a system information block, or by an OAM entity; further comprising: obtaining an ID; scrambling the plurality of OTA signals by applying the RNTI and the ID; wherein the ID is a cell ID associated with a device implementing the method; wherein the PNCCH is mapped to at least one of NCH, NCCH, CCCH, or BCCH.

[0322] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured to, or otherwise support: transmitting to a UE a first signaling instruction indicating an SRS configuration for inter-cell CLI measurements, wherein the SRS configuration includes an indication of a resource set associated with a plurality of devices; transmitting to the UE a second signaling instruction indicating a CLI report configuration associated with the SRS configuration; and receiving from the UE a third signaling instruction indicating a CLI report, wherein the CLI report includes one or more results of CLI measurements performed on each of a plurality of subsets of resources according to the CLI report configuration, wherein each of the plurality of subsets is associated with one of the plurality of devices.

[0323] Additionally or alternatively, the processor 1004 may be configured to support: each of the plurality of subsets includes one or more of at least one symbol or at least one resource element; the CLI report further includes an indication of the association between each of the one or more results and one of the plurality of devices; each of the plurality of subsets is further associated with the transmit beam of one of the plurality of devices; the CLI report further includes an indication of the association between each of the one or more results and the transmit beam of one of the plurality of devices; the processor is configured to cause the device to: transmit to the UE a fourth signaling indicating activation or deactivation associated with at least one of the SRS configuration or the CLI report configuration; wherein: the CLI is co-channel interference; and each of the one or more results is at least one of SRS-RSRP or CLI-RSSI; wherein the device is a network entity; wherein each of the devices is a UE served by at least one of the network entities of the device or a neighboring serving cell; wherein the CLI report is associated with the physical layer, MAC layer, or RRC layer.

[0324] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured or otherwise support a component for: transmitting to a UE a first signaling instruction indicating an SRS configuration for inter-cell CLI measurements, wherein the SRS configuration includes an indication of a resource set associated with a plurality of devices; transmitting to the UE a second signaling instruction indicating a CLI report configuration associated with the SRS configuration; and receiving from the UE a third signaling instruction indicating a CLI report, wherein the CLI report includes one or more results of CLI measurements performed on each of a plurality of subsets of resources according to the CLI report configuration, wherein each of the plurality of subsets is associated with one of the plurality of devices.

[0325] Additionally or alternatively, the processor 1004 may be configured to support: each of the plurality of subsets includes one or more of at least one symbol or at least one resource element; the CLI report further includes an indication of the association between each of the one or more results and one of the plurality of devices; each of the plurality of subsets is further associated with the transmit beam of one of the plurality of devices; the CLI report further includes an indication of the association between each of the one or more results and the transmit beam of one of the plurality of devices; it further includes: transmitting to the UE a fourth signaling indicating activation or deactivation associated with at least one of the SRS configuration or the CLI report configuration; wherein: the CLI is co-channel interference; and each of the one or more results is at least one of SRS-RSRP or CLI-RSSI; wherein the method is implemented by a network entity; wherein each of the devices is a UE served by at least one of the devices implementing the method or a network entity of a neighboring serving cell; wherein the CLI report is associated with a physical layer, MAC layer, or RRC layer. Processor 1004 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some embodiments, processor 1004 may be configured to operate a memory array using a memory controller. In some other embodiments, the memory controller may be integrated into processor 1004. Processor 1004 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1006) to cause device 1002 to perform various functions of this disclosure.

[0326] Processor 1004 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some embodiments, processor 1004 may be configured to operate a memory array using a memory controller. In some other embodiments, the memory controller may be integrated into processor 1004. Processor 1004 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1006) to cause device 1002 to perform various functions of this disclosure.

[0327] Memory 1006 may include random access memory (RAM) and read-only memory (ROM). Memory 1006 may store computer-readable, computer-executable code containing instructions that, when executed by processor 1004, cause device 1002 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some embodiments, the code may not be directly executable by processor 1004, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some embodiments, memory 1006 may, in particular, include a basic I / O system (BIOS) that controls basic hardware or software operation, such as interaction with peripheral components or devices.

[0328] I / O controller 1010 manages the input and output signals of device 1002. I / O controller 1010 can also manage peripheral devices not integrated into device 1002. In some embodiments, I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some embodiments, I / O controller 1010 may utilize an operating system, such as... Or another known operating system. In some embodiments, the I / O controller 1010 may be implemented as a processor, such as a portion of processor 1004. In some embodiments, a user may interact with device 1002 via the I / O controller 1010 or via hardware components controlled by the I / O controller 1010.

[0329] In some embodiments, device 1002 may include a single antenna 1012. However, in other embodiments, device 1002 may have more than one antenna 1012 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 1008 may communicate bidirectionally via one or more antennas 1012, wired or wireless links as described herein. For example, transceiver 1008 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 1008 may also include a modem to modulate packets, provide modulated packets to one or more antennas 1012 for transmission, and demodulate packets received from one or more antennas 1012.

[0330] In some implementations, device 1002 may be a UE, and processor 1004 may support wireless communication at device 1002 according to examples disclosed herein. Processor 1004 may be configured to, or otherwise support: receiving from a network entity a first signaling instruction indicating an SRS configuration for inter-cell CLI measurements, wherein the SRS configuration includes an indication of a resource set associated with a plurality of devices; receiving from the network entity a second signaling instruction indicating a CLI report configuration associated with the SRS configuration; performing CLI measurements on each of a plurality of subsets of resources according to the CLI report configuration, wherein each of the plurality of subsets is associated with one of the plurality of devices; and transmitting to the network entity a third signaling instruction indicating a CLI report including one or more results of the CLI measurements.

[0331] Additionally or alternatively, the processor 1004 may be configured to or otherwise support: each of the plurality of subsets includes one or more of at least one symbol or at least one resource element; the CLI report further includes an indication of the association between each of the one or more results and one of the plurality of devices; each of the plurality of subsets is further associated with the transmit beam of one of the plurality of devices; the CLI report further includes an indication of the association between each of the one or more results and the transmit beam of one of the plurality of devices; wherein a subset of resources associated with a device is determined by: determining a pattern associated with the device, wherein the pattern includes a plurality of fields, Each of the fields is further associated with one of the plurality of subsets; determining that the resource associated with the field is in the subset in response to a field in the pattern equaling a first value; and determining that the resource associated with the field is not in the subset in response to a field in the pattern equaling a second value; wherein: the pattern includes or is associated with a bitmap field; each of the plurality of fields is a bit in the bitmap field; the first value is '1'; and the second value is '0'; wherein the processor is configured to cause the device to: receive from the network entity a fourth signaling indicating activation or deactivation associated with at least one of the SRS configuration or the CLI report configuration; and respond to the fourth signaling Instructions to deactivate: Do not perform the CLI measurement; or do not transmit the CLI report to the network entity; wherein a subset of resources associated with the device is determined by: receiving from the network entity a fourth signaling indicating a mode associated with the plurality of devices, wherein the mode includes a plurality of fields, each of which is associated with one of the plurality of devices; determining that the device associated with the field transmits SRS in response to a field in the mode equaling a first value; and determining that the device associated with the field does not transmit SRS in response to a field in the mode equaling a second value; wherein: the mode includes or is associated with a bitmap field; each of the plurality of fields is a bit in a bitmap field; the first value is '1'; and the second value is '0'; wherein the processor is configured to allow the device to receive the pattern from at least one of the network entity or an additional network entity serving at least a subset of the device; wherein: the CLI is co-channel interference; and each of the one or more results is at least one of SRS-RSRP or CLI-RSSI; wherein: the CLI is adjacent channel interference; each of the one or more results is CLI-RSSI; and each of the one or more results measured by the CLI is obtained by: measuring co-channel interference associated with the device; obtaining ACLR associated with the device; and calculating adjacent channel interference by combining the co-channel interference with the ACLR;Obtaining the ACLR includes receiving a message containing the value of the ACLR; calculating the adjacent channel interference includes at least one of the following: dividing the co-channel interference by the ACLR in the real number domain; or subtracting the ACLR from the co-channel interference in the logarithmic or decibel domain; wherein the device is a UE; wherein each of the devices is a UE served by at least one of a network entity or a network entity of a neighboring serving cell; wherein the CLI report is associated with the physical layer, MAC layer, or RRC layer.

[0332] For example, processor 1004 may support wireless communication at device 1002 according to an example disclosed herein. Processor 1004 may be configured or otherwise support a component for: receiving from a network entity a first signaling indicating an SRS configuration for inter-cell CLI measurements, wherein the SRS configuration includes an indication of a resource set associated with a plurality of devices; receiving from the network entity a second signaling indicating a CLI report configuration associated with the SRS configuration; performing CLI measurements on each of a plurality of subsets of resources according to the CLI report configuration, wherein each of the plurality of subsets is associated with one of the plurality of devices; and transmitting to the network entity a third signaling indicating a CLI report including one or more results of the CLI measurements.

[0333] Additionally or alternatively, the processor 1004 may be configured to or otherwise support: each of the plurality of subsets includes one or more of at least one symbol or at least one resource element; the CLI report further includes an indication of the association between each of the one or more results and one of the plurality of devices; each of the plurality of subsets is further associated with a transmit beam of one of the plurality of devices; the CLI report further includes an indication of the association between each of the one or more results and a transmit beam of one of the plurality of devices; wherein a subset of resources associated with a device is determined by: determining a pattern associated with the device, wherein the pattern includes a plurality of fields, the Each of the fields is further associated with one of the plurality of subsets; in response to a field in the pattern being equal to a first value, it is determined that the resource associated with the field is in the subset; and in response to a field in the pattern being equal to a second value, it is determined that the resource associated with the field is not in the subset; wherein: the pattern includes or is associated with a bitmap field; each of the plurality of fields is a bit in the bitmap field; the first value is '1'; and the second value is '0'; it further includes: receiving from the network entity a fourth signaling indicating activation or deactivation associated with at least one of the SRS configuration or the CLI reporting configuration; and in response to the fourth signaling indicating deactivation: not performing the CLI. Measurement; or not transmitting the CLI report to the network entity; wherein a subset of resources associated with the device is determined by: receiving from the network entity a fourth signaling indicating a mode associated with the plurality of devices, wherein the mode includes a plurality of fields, each of which is associated with one of the plurality of devices; determining that the device associated with the field transmits SRS in response to a field in the mode being equal to a first value; and determining that the device associated with the field does not transmit SRS in response to a field in the mode being equal to a second value; wherein: the mode includes or is associated with a bitmap field; each of the plurality of fields is a bit in a bitmap field; the first value is '1'; and the second value is '0'; and its The method further includes receiving the pattern from at least one of the network entity or an additional network entity serving at least a subset of the device; wherein: the CLI is co-channel interference; and each of the one or more results is at least one of SRS-RSRP or CLI-RSSI; wherein: the CLI is adjacent channel interference; each of the one or more results is CLI-RSSI; and each of the one or more results measured by the CLI is obtained by: measuring co-channel interference associated with the device; obtaining ACLR associated with the device; and calculating adjacent channel interference by combining the co-channel interference with the ACLR; wherein obtaining the ACLR includes receiving a message containing the value of the ACLR;The calculation of the adjacent channel interference includes at least one of the following: dividing the co-channel interference by the ACLR in the real number domain; or subtracting the ACLR from the co-channel interference in the logarithmic or decibel domain; wherein the method is implemented by the UE; wherein each of the means is a UE served by at least one of the network entities or network entities of adjacent serving cells; wherein the CLI report is associated with the physical layer, MAC layer, or RRC layer. Processor 1004 may include intelligent hardware means (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic means, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some embodiments, processor 1004 may be configured to operate a memory array using a memory controller. In some other embodiments, the memory controller may be integrated into processor 1004. Processor 1004 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1006) to cause means 1002 to perform various functions of this disclosure.

[0334] Figure 11 This document describes a flowchart illustrating a method 1100 for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure. Operation of method 1100 can be implemented by means of apparatus or components thereof as described herein. For example, operation of method 1100 can be performed by means of... Figures 1 to 10 The described network entity 102 performs this function. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the device may use dedicated hardware to perform aspects of the described function.

[0335] At 1105, the method may include receiving first signaling from a network entity indicating an SRS configuration, the SRS configuration indicating an association between multiple resources and multiple devices. Operation 1105 may be performed according to the examples described herein. In some embodiments, aspects of operation 1105 may be as described regarding... Figure 1 The described device is used to perform this action.

[0336] At 1110, the method may include transmitting a second signaling to the first device instructing a CLI report configuration. Operation 1110 may be performed according to the examples described herein. In some embodiments, aspects of operation 1110 may be determined by, as per [reference to...] Figure 1 The described device is used to perform this action.

[0337] At 1115, the method may include receiving third signaling from a first device, instructing a CLI report according to a CLI report configuration, wherein the CLI report includes multiple CLI measurement results associated with multiple resources. Operation 1115 may be performed according to the examples described herein. In some embodiments, aspects of operation 1115 may be provided by, as per [reference to...] Figure 1 The described device is used to perform this action.

[0338] At 1120, the method may include transmitting a fourth signaling to a network entity instructing a CLI reporting IE, the CLI reporting IE indicating that one or more of the plurality of devices caused excessive CLI based on CLI reports and associations between multiple resources and multiple devices. Operation 1120 may be performed according to examples as described herein. In some embodiments, aspects of operation 1120 may be as described regarding... Figure 1 The described device is used to perform this action.

[0339] Figure 12 This document describes a flowchart illustrating a method 1200 for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure. Operation of method 1200 can be implemented by means of apparatus or components thereof as described herein. For example, operation of method 1200 can be performed by means of... Figures 1 to 10 The described network entity 102 performs this function. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the device may use dedicated hardware to perform aspects of the described function.

[0340] At 1205, the method may include determining one or more CLI measurement results associated with one or more of a plurality of resources. Operation 1205 may be performed according to examples as described herein. In some embodiments, aspects of operation 1205 may be as described regarding... Figure 1 The described device is used to perform this action.

[0341] At 1210, the method may include determining one or more of the plurality of devices associated with one or more of the plurality of resources based on the association between the plurality of resources and the plurality of devices. Operation 1210 may be performed according to the examples described herein. In some embodiments, aspects of operation 1210 may be as described with respect to... Figure 1 The described device is used to perform this action.

[0342] At 1215, the method may include inferring one or more of the devices causing an excessive CLI. Operation 1215 may be performed according to the examples described herein. In some embodiments, aspects of operation 1215 may be determined by, as per [reference to...] Figure 1 The described device is used to perform this action.

[0343] Figure 13This document describes a flowchart of method 1300 for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure. Operation of method 1300 can be implemented by means of apparatus or components thereof as described herein. For example, operation of method 1300 can be performed by means of... Figures 1 to 10 The described network entity 102 performs this function. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the device may use dedicated hardware to perform aspects of the described function.

[0344] At 1305, the method may include receiving an activation or deactivation indication associated with the SRS configuration. Operation 1305 may be performed according to the examples described herein. In some implementations, aspects of operation 1305 may be as described regarding... Figure 1 The described device is used to perform this action.

[0345] At 1310, the method may include instructing a first device to deactivate a CLI report in response to determining an activation or deactivation indication. Operation 1310 may be performed according to examples as described herein. In some embodiments, aspects of operation 1310 may be as described regarding... Figure 1 The described device is used to perform this action.

[0346] Figure 14 This document describes a flowchart illustrating a method 1400 for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure. Operation of method 1400 can be implemented by means of apparatus or components thereof as described herein. For example, operation of method 1400 can be performed by means of... Figures 1 to 10 The described network entity 102 performs this function. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the device may use dedicated hardware to perform aspects of the described function.

[0347] At 1405, the method may include receiving from a network entity a pattern associated with a plurality of devices, wherein the pattern includes a plurality of fields, each of which is associated with one of the plurality of devices. Operation 1405 may be performed according to the examples described herein. In some embodiments, aspects of operation 1405 may be provided by, as per [the description of the embodiments]... Figure 1 The described device is used to perform this action.

[0348] At 1410, the method may include determining, in response to a field in the pattern equaling a first value, that a device associated with the field transmits an SRS. Operation 1410 may be performed according to examples as described herein. In some embodiments, aspects of operation 1410 may be as described regarding... Figure 1 The described device is used to perform this action.

[0349] At 1415, the method may include determining that the device does not transmit SRS in response to a field in the pattern equaling a second value. Operation 1415 may be performed according to the examples described herein. In some embodiments, aspects of operation 1415 may be as described regarding Figure 1 The described device is used to perform this action.

[0350] Figure 15 This document describes a flowchart illustrating a method 1500 for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure. Operation of method 1500 can be implemented by means of apparatus or components thereof as described herein. For example, operation of method 1500 can be performed by means of... Figures 1 to 10 The described network entity 102 performs this function. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the device may use dedicated hardware to perform aspects of the described function.

[0351] At 1505, the method may include obtaining the RNTI associated with the PNCCH. Operation 1505 may be performed according to the instances described herein. In some implementations, aspects of operation 1505 may be determined by, as per [reference to...] Figure 1 The described device is used to perform this action.

[0352] At 1510, the method may include receiving multiple OTA signals associated with the PNCCH from a network entity. Operation 1510 may be performed according to the examples described herein. In some implementations, aspects of operation 1510 may be as described regarding... Figure 1 The described device is used to perform this action.

[0353] At 1515, the method may include descrambling multiple OTA signals by applying RNTI. Operation 1515 may be performed according to the examples described herein. In some implementations, aspects of operation 1515 may be as described regarding Figure 1 The described device is used to perform this action.

[0354] Figure 16 This document describes a flowchart illustrating a method 1600 for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure. Operation of method 1600 can be implemented by means of apparatus or components thereof as described herein. For example, operation of method 1600 can be performed by means of... Figures 1 to 10 The described network entity 102 performs this function. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the device may use dedicated hardware to perform aspects of the described function.

[0355] At 1605, the method may include obtaining the ID. Operation 1605 may be performed according to an example as described herein. In some implementations, aspects of operation 1605 may be as described regarding Figure 1 The described device is used to perform this action.

[0356] At 1610, the method may include descrambling multiple OTA signals by applying RNTI and ID. Operation 1610 may be performed according to the examples described herein. In some implementations, aspects of operation 1610 may be as described regarding... Figure 1 The described device is used to perform this action.

[0357] Figure 17 This document describes a flowchart of method 1700 for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure. Operation of method 1700 can be implemented by means of apparatus or components thereof as described herein. For example, operation of method 1700 can be performed by means of... Figures 1 to 10 The described network entity 102 performs this function. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the device may use dedicated hardware to perform aspects of the described function.

[0358] At 1705, the method may include transmitting first signaling to a network entity indicating an SRS configuration, said SRS configuration indicating an association between multiple resources and multiple devices. Operation 1705 may be performed according to examples as described herein. In some embodiments, aspects of operation 1705 may be as described regarding... Figure 1 The described device is used to perform this action.

[0359] At 1710, the method may include receiving a second signaling from a network entity instructing a CLI reporting IE, the CLI reporting IE indicating, based on CLI reports and associations between multiple resources and multiple devices, that one or more of the multiple devices caused excessive CLI. Operation 1710 may be performed according to the examples described herein. In some embodiments, aspects of operation 1710 may be as described regarding... Figure 1 The described device is used to perform this action.

[0360] Figure 18 This document describes a flowchart illustrating a method 1800 for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure. Operation of method 1800 can be implemented by means of apparatus or components thereof as described herein. For example, operation of method 1800 can be performed by means of... Figures 1 to 10 The described network entity 102 performs this function. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the device may use dedicated hardware to perform aspects of the described function.

[0361] At 1805, the method may include transmitting an activation or deactivation indication associated with the SRS configuration. Operation 1805 may be performed according to the examples described herein. In some embodiments, aspects of operation 1805 may be as described regarding Figure 1 The described device is used to perform this action.

[0362] Figure 19 This document describes a flowchart illustrating a method 1900 for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure. Operation of method 1900 can be implemented by means of apparatus or components thereof as described herein. For example, operation of method 1900 can be performed by means of... Figures 1 to 10 The described network entity 102 performs this function. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the device may use dedicated hardware to perform aspects of the described function.

[0363] At 1905, the method may include scrambling multiple OTA signals associated with the PNCCH by applying an RNTI associated with the PNCCH. Operation 1905 may be performed according to the examples described herein. In some implementations, aspects of operation 1905 may be as described regarding Figure 1 The described device is used to perform this action.

[0364] At 1910, the method may include transmitting multiple OTAs to a network entity. Operation 1910 may be performed according to the examples described herein. In some implementations, aspects of operation 1910 may be as described regarding... Figure 1 The described device is used to perform this action.

[0365] Figure 20 This document describes a flowchart of a method 2000 for backhaul and air signaling supporting cross-link interference management between user equipment, based on aspects of this disclosure. Operation of method 2000 can be implemented by means of apparatus or components thereof as described herein. For example, operation of method 2000 can be performed by means of... Figures 1 to 10 The described network entity 102 performs this function. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the device may use dedicated hardware to perform aspects of the described function.

[0366] At operation 2005, the method may include obtaining an ID. Operation 2005 may be performed according to an instance as described herein. In some implementations, aspects of operation 2005 may be determined by, as per [the relevant documentation]... Figure 1 The described device is used to perform this action.

[0367] At operation 2010, the method may include scrambling multiple OTA signals by applying RNTI and ID. Operation 2010 may be performed according to the examples described herein. In some implementations, aspects of operation 2010 may be as described regarding... Figure 1 The described device is used to perform this action.

[0368] It should be noted that the methods described herein describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0369] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device designed to perform the functions described herein, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor may be a microprocessor, but alternatively, 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 incorporating a DSP core, or any other such configuration).

[0370] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, these functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and embodiments are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including distribution such that portions of the function are implemented in different physical locations.

[0371] Computer-readable media include both non-transitory computer storage media and communication media, wherein the communication media includes any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer. By way of example and without limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory media that can be used to carry or store required program code elements in the form of instructions or data structures and is accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.

[0372] Any connection may be appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, optical fiber, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), then coaxial cable, optical fiber, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0373] As used herein, the word "or," as used in the claims, and in a list of items (e.g., a list of items beginning with phrases such as "at least one of," "one or more of," or "one or two of"), indicates a comprehensive list such that a list of at least one of, for example, 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). As another example, a list of one or both of A or B means A or B or AB. Similarly, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on." Furthermore, as used herein, a "set" may comprise one or more elements.

[0374] The terms “transmit,” “receive,” or “transmit” when referring to a network entity can refer to any part of a network entity (e.g., a base station, CU, DU, RU) of the RAN that communicates with another device (e.g., directly or via one or more other network entities).

[0375] The descriptions set forth herein, taken in conjunction with the accompanying drawings, illustrate exemplary configurations and do not represent all instances that may be implemented or that are within the scope of the claims. The term "example" as used herein means "as an instance, example, or illustration" and is not "preferred" or "superior to other examples." The detailed descriptions contain specific details intended to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and apparatuses are shown in block diagram form to avoid obscuring the concept of the described examples.

[0376] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A device for wireless communication, comprising: processor; and A memory coupled to the processor, the processor being configured to enable the device to: Receive a first signaling from a network entity indicating the configuration of a probe reference signal (SRS), the SRS configuration indicating the association of multiple resources with multiple devices; Transmit a second signaling instruction to the first device indicating the configuration of the cross-link interference CLI report; According to the CLI report configuration, a third signaling instructing a CLI report is received from the first device, wherein the CLI report includes multiple CLI measurement results associated with the plurality of resources; and A fourth signaling instruction is transmitted to the network entity to indicate a CLI reporting information element (IE), the CLI reporting IE indicating, based on the CLI report and the association between the plurality of resources and the plurality of devices, that one or more of the plurality of devices caused excessive CLI.

2. The device of claim 1, wherein one or more of the plurality of devices causing the excessive CLI are determined by: Determine that one or more CLI measurement results associated with one or more of the plurality of resources are excessive; Based on the association between the plurality of resources and the plurality of devices, determine one or more of the plurality of devices associated with one or more of the plurality of resources; and It is inferred that one or more of the devices cause the excessive CLI.

3. The device of claim 1, wherein each of the plurality of resources comprises at least one symbol or one or more of at least one resource element.

4. The device according to claim 1, wherein: The SRS configuration further includes an indication of the association between the plurality of resources and the plurality of transmit beams of the plurality of devices; The processor is configured to cause the device to determine that one or more of the plurality of transmit beams from one or more of the plurality of devices cause the excessive CLI; and The CLI report IE further indicates that one or more of the plurality of transmit beams of the one or more devices caused the excessive CLI.

5. The device of claim 1, wherein the processor is configured to cause the device to: Receive an activation or deactivation indication associated with the SRS configuration; and In response to determining that the activation or deactivation indication indicates deactivation, the first device is instructed to deactivate the CLI report.

6. The device of claim 1, wherein one or more of the plurality of devices causing the excessive CLI are determined by: Receive a pattern associated with the plurality of devices from the network entity, wherein the pattern includes a plurality of fields, each of which is associated with one of the plurality of devices; In response to a field in the pattern being equal to a first value, it is determined that the device associated with the field transmits an SRS; and The device determines that it does not transmit the SRS in response to the field in the mode being equal to a second value.

7. The device according to claim 6, wherein: The pattern includes bitmap fields or is otherwise associated with them; Each of the plurality of fields is a bit in the bitmap field; The first value is '1'; and The second value is '0'.

8. The device of claim 1, wherein each of the plurality of CLI measurements is at least one of co-channel SRS reference signal received power SRS-RSRP or co-channel CLI received signal strength indication CLI-RSSI.

9. The device according to claim 1, wherein: Each of the multiple CLI measurement results is the co-channel SRS reference signal received power (SRS-RSRP); and One or more of the plurality of devices that lead to the excessive CLI are obtained through the following: Obtain one or more adjacent channel leakage ratio (ACLR) values ​​associated with one or more of the plurality of devices; and The neighboring channel CLI is calculated by combining the co-channel SRS-RSRP and ACLR values.

10. A device for wireless communication, comprising: processor; and A memory coupled to the processor, the processor being configured to enable the device to: Obtain the Radio Network Temporary Identifier (RNTI) associated with the Physical Network Link Control Channel (PNCCH); Receive multiple over-the-air (OTA) signals associated with the PNCCH from network entities; The RNTI is used to descramble the multiple OTA signals.

11. The device of claim 10, wherein the RNTI is indicated by at least one of the following: by a standard, by a core network, by the network entity on a backhaul interface, by the network entity in a broadcast signal, by the network entity in a system information block, or by an operation, management, and maintenance OAM entity.

12. The device of claim 10, wherein the processor is configured to: Obtain the identifier ID, wherein the ID is the cell ID associated with the network entity; The multiple OTA signals are descrambled by applying the RNTI and the cell ID.

13. The device of claim 10, wherein the processor is configured to: Receive additional signaling indicating the identifier ID from at least one of the core network, the network entity, or the orthogonal access and backhaul OAB; and The multiple OTA signals are descrambled by applying the RNTI and the ID.

14. The apparatus of claim 10, wherein the PNCCH is mapped to at least one of the network link transport channel NCH, network link logical control channel NCCH, common control channel CCCH, or broadcast control channel BCCH.

15. A device for wireless communication, comprising: processor; and A memory coupled to the processor, the processor being configured to enable the device to: A first signaling instruction is transmitted to a network entity to indicate the configuration of a Detection Reference Signal (SRS), the SRS configuration indicating the association between multiple resources and multiple devices; and The network entity receives a second signaling instruction indicating cross-link interference CLI report information element IE, the CLI report IE indicating, based on the CLI report and the association between the plurality of resources and the plurality of devices, that one or more of the plurality of devices are causing excessive CLI.

16. The device of claim 15, wherein each of the plurality of resources comprises at least one symbol or one or more of at least one resource element.

17. The apparatus according to claim 15, wherein: The SRS configuration further includes an indication of the association between the plurality of resources and the plurality of transmit beams of the plurality of devices; and The CLI report IE further indicates that one or more of the plurality of transmit beams of the one or more devices caused the excessive CLI.

18. A device for wireless communication, comprising: processor; and A memory coupled to the processor, the processor being configured to enable the device to: Multiple over-the-air (OTA) signals associated with the Physical Network Link Control Channel (PNCCH) are scrambled by applying the Radio Network Temporary Identifier (RNTI) associated with the PNCCH. The multiple OTAs are transmitted to the network entities.

19. The device of claim 18, wherein the RNTI is indicated by at least one of the following: by a standard, by a core network, by the network entity on a backhaul interface, by the network entity in a broadcast signal, by the network entity in a system information block, or by an operation, management, and maintenance OAM entity.

20. The apparatus of claim 18, wherein the processor is configured to: Obtain the identifier ID, wherein the ID is the cell ID associated with the device; The multiple OTA signals are scrambled by applying the RNTI and the ID.

Images