User equipment (UE)-to-UE interference avoidance and mitigation

Abstract

A method implemented in a network node in communication with a first user equipment, UE. The method includes determining that a distance between the first UE and a second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE Cross Link Interference, CLI, between the first UE and the second UE; and performing the action based on the determination.

Description

[0001] USER EQUIPMENT (UE)-TO-UE INTERFERENCE AVOIDANCE AND MITIGATION

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to User Equipment (UE)-to-UE interference avoidance and mitigation.

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between WDs. The 3 GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] 3GPP NR Standard

[0007] New radio (NR) standard as specified in, e.g., 3GPP Technical Report (TR) 38.300 is being designed to provide service for multiple use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), and machine type communication (MTC). Each of these services has different technical requirements. For example, the general requirement for eMBB is high data rate with moderate latency and moderate coverage, while URLLC service requires a low latency and high reliability transmission but perhaps for moderate data rates.

[0008] An NR slot consists of several OFDM symbols, according to current agreements either 7 or 14 symbols (OFDM subcarrier spacing < 60 kHz) and 14 symbols (OFDM subcarrier spacing > 60 kHz). FIG. 1 shows a slot with 14 OFDM symbols. In FIG. 1 Tsand Tsymbdenote the slot and OFDM symbol duration, respectively.

[0009] Different types of duplex communication modes

[0010] Different types of duplex communication modes are illustrated in Figures 2A-D (collectively FIG. 2). FIG. 2A shows FDD, FIG. 2B shows TDD, FIG. 2C shows SBFD, and FIG. 2D shows IBFD. FIGS. 3A-B (collectively FIG. 3) show a comparison of TDD operations. FIG. 3 A shows Static TDD in channel 1 and 2, and FIG. 3B shows static TDD in channel 2 and Dynamic TDD in channel 1. To support the many types of targeted use cases with varying requirements, different duplex communication modes are discussed in 3GPP standardization. Moreover, the same device may be capable of operating using different duplex modes, for e.g., to achieve different overall communication performance based on its needs.

[0011] Transmission and reception from a wireless communication device, e.g., a network node or a User Equipment (UE) in a cellular system, can be multiplexed in the frequency domain or in the time domain (or combinations thereof). The most relevant duplex modes are discussed below.

[0012] Duplex communication modes

[0013] • Frequency Division Duplex (FDD), as illustrated in FIG. 2A, implies that transmission (TX) and reception (RX) take place in different, sufficiently separated carriers. Thus, FDD may require paired spectrum. In cases of FDD operation, there are two carrier frequencies, one for uplink (UL) transmission and one for downlink (DL) transmission. At least with respect to the UE in a cellular communication system, FDD can be either full duplex (FD-FDD) or half duplex (HD-FDD). In the FD-FDD case, a UE can transmit and receive simultaneously, while in HD-FDD operation, the UE cannot transmit and receive simultaneously (the network node is still capable of simultaneous RX / TX though, e.g., receiving from one UE while simultaneously transmitting to another UE). In LTE, a HD-FDD terminal is monitoring / receiving in the DL except when explicitly being instructed to transmit in a certain subframe.

[0014] • Time Division Duplex (TDD), as illustrated in FIG. 2B, implies that TX and RX take place within the same carrier in different, non-overlapping time slots. Thus, TDD can operate in unpaired spectrum. In case of TDD operation, there may be only a single carrier frequency and UL and DL transmissions are always separated in time also on a cell basis. As the same carrier frequency is used for UL and DL transmission, both the network node and the UEs may need to switch from TX to RX and vice versa. A common aspect of any TDD system is to provide the possibility for a sufficiently large guard time where neither DL nor UL transmissions occur. This may be required to avoid interference between UL and DL transmissions. For NR, this guard time is provided by special slots, which are split into three parts: symbols for DL, a guard period (GP), and symbols for UL. The remaining slots are either allocated to UL or DL transmission. The only interference existing in this configuration is among transmissions happening on the same link, inside the own channel, and from an adjacent channel, if synchronization is also assumed among different operators. This is shown in FIG. 3 A, where the two networks deployed in channels 1 and 2 are synchronized and will suffer only from in-channel and adjacent channel interference from the same link. Interference links are further described in FIG. 4A. This option is, e.g., used by operators in Europe and recommended in regulations, and may require entire carrier bandwidth or all carriers in the same frequency band to be utilizing the same DL transmission or UL reception directions.

[0015] • Dynamic TDD describes a mode of operation in which a network adapts the DL / UL subframe pattern according to traffic conditions. This causes interference between different links (uplink and downlink), and it is referred to as Cross Link Interference (CLI), BS-to-BS and UE-to-UE, as it is shown in FIG. 4B as indicated at (b). CLI interference happens inside the same operator and inter-operators. Figure 3B provides an example. Specifically, the deployment on channel 1 requires additional UL slots to serve UL traffic, and to do that the TDD patterns of BS1 and BS2 are adjusted to increase UL ratio. Due to that, the deployment will suffer, inside the own network, from BS-to-BS and UE-to-UE interference in slots 2 and 3. In addition, these patterns used in channel 1 are unsynchronized with respect to the static TDD pattern used in channel 2. Due to that, the deployment in channel 1 will suffer from BS-to-BS and UE-to-UE interference from the adjacent channel, in slots 2, 3 and 4. On channel 2 instead, the deployment will suffer from UE-to-UE interference from the adjacent channel in slots 2, 3 and 4, but only from same link interference inside channel 2.

[0016] • Sub-Band Full Duplex (SBFD), as illustrated in FIG. 2C, is being studied in 3GPP Release 18 as a part of the 5G- Advanced standardization. In case of SBFD operation, a portion of a wide bandwidth carrier, termed sub-band, may be used for a different communication direction than that of the rest of the carrier. Correspondingly, different non-overlapping sub-bands are used for DL and UL. This is unlike the conventional TDD operation wherein the entire bandwidth of the carrier may always be used either for DL or UL. SBFD operation can also be performed across different carriers within the same frequency band, wherein one or more carriers within a frequency band may be used for a different communication direction than that of the other carriers, which is again unlike conventional TDD operation wherein all carriers within a frequency band are always used for the same communication direction. In the 3GPP Release 18 study, the scope has been limited such that during SBFD communication, only network nodes transmit DL and receive UL simultaneously using corresponding non-overlapping subbands. An individual UE is scheduled in only one direction (DL or UL) at a time, following conventional HD TDD operation. However, for future 3 GPP releases, SBFD operation at UEs wherein a UE transmits UL and receives DL simultaneously using corresponding non-overlapping sub-bands is also being discussed as a potential study topic. Interference links affecting a SBFD Rel. 18 deployments are shown in FIG. 4C.

[0017] • Single frequency full duplex (SFFD) or In-band Full Duplex (IBFD), as illustrated in FIG. 2D, has also been proposed to be studied in 3GPP standardization. It was discussed but excluded from the scope of Release 18, and it is now again being discussed during scoping discussions for future releases. In case of SFFD operation, the entire bandwidth of the same carrier in a single carrier system or all carriers in a multicarrier system can be simultaneously used for DL and UL operations, as shown in FIG. 4D. In other words, the same time and frequency resources can be used for both TX and RX at the same device. Similar to SBFD operation, SFFD operation is also being discussed for both network nodes and UEs.

[0018] 5G positioning in Rel. 16

[0019] 3 GPP has specified in Release 16 the positioning architecture, together with positioning signals and measurements for 5G NR.

[0020] In 5G positioning architecture, the Local Management Function (LMF), which is in charge of positioning, and is in 5G core network, receives measurements and assistance information from the next generation radio access network (NG-RAN), the network nodes and the UEs, via the access and mobility management function (AMF) to compute the positions of the UEs. The NR Positioning Protocol Annex (NRPPa) protocol carries the positioning information between NG-RAN and LMF over the next generation control plane interface (NG-C). The positioning manager 24 (e.g., via LMF ) configures the UE using the LTE positioning protocol (LPP) via AMF. The NG RAN configures the UE using radio resource control (RRC) protocol over LTE-Uu and NR-Uu.

[0021] NR Rel. 16 supports two positioning reference signals:

[0022] Downlink positioning reference signal (DL-PRS). PRS is specifically designed to deliver the highest possible levels of accuracy, coverage, and interference avoidance and suppression. It is designed to be received from potentially distant neighboring base stations for position estimation. Among other features, the PRS can be transmitted in beams. The beam structure of the PRS improves coverage especially for mm-wave deployments and also allows for Angle of Departure (AoD) estimation. The DL PRS is designed to allow the UE to perform accurate Time of Arrival (TOA) measurements in presence of interfering DL PRSs from nearby nodes. Uplink sounding reference signal (UL-SRS). SRS for positioning has a lot in common with SRS for communications, but they are configured differently for their different purposes. It is designed to have enough range to reach not only the serving network node, but also the neighboring network node involved in the positioning process.

[0023] Positioning measurements have been standardized also in Release 16, not only for the serving cell, but also for neighbor cells.

[0024] Multiple DL measurements based in PRS can be configured in the UE by positioning manager 24 (e.g., via LMF):

[0025] DL PRS Received Signal Time Difference (RSTD), UE Rx-Tx time difference, PRS-based Reference Signal Received Power (PRS-RSRP) measurements. The UE may also report additional Radio Resource Management (RRM) measurements.

[0026] UL measurements can be configured by positioning manager 24 (e.g., via LMF) and reported by network node:

[0027] UL Relative Time of Arrival (UL-RTOA), gNB Rx-Tx time difference, Sounding Reference Signal RSRP (SRS-RSRP), Azimuth and Zenith of Angle of Arrival (A-AoA and Z-AoA, respectively).

[0028] The 3 GPP standard supports the above measurements in all supported bands, in FR1 and FR2.

[0029] There is wide number of standardized positioning methods. They are normally split within two groups: 1) the RAT-dependent, which are based on measurements of NR signals (from serving or neighbor cells); 2) the RAT -independent, e.g. assisted GNSS, Bluetooth, WLAN, sensor based. Also hybrid options are considered.

[0030] Some examples of the standardized methods are: network-assisted GNSS methods;

[0031] DL Time Difference of Arrival (DL-TDOA): based on RSTD and optional PRS-RSRP;

[0032] DL Angle of Departure (DL-AoD): based on PRS-RSRP;

[0033] UL-TDOA: based on UL-RTOA and SRS-RSRP;

[0034] UL-AoA: based on A-AoA and Z-AoA and SRS-RSRP measurements;

[0035] Multi -RTT: based on gNB Rx-Tx and UE Rx-Tx time difference measurements and PRS-RSRP, SRS-RSRP, A-AoA, and Z-AoA measurements.

[0036] 3GPP Rel. 18 Sidelink Positioning

[0037] In 3GPP Rel. -18, NR positioning framework has been enhanced and improved as compared with prior releases. A framework for sideling positioning has been defined, based on measurements of range and directions between devices and not only network nodes and UEs. This framework builds on Release 16 positioning and sidelink communications work. Use cases of interest include V2X, public safety, industrial loT, commercial.

[0038] On the architecture side there is a new protocol for device-to-device positioning and signaling, SLPP (Sidelink Positioning Protocol).

[0039] A new sidelink reference signal, SL-PRS (Sidelink PRS), has been standardized. For that, new measurements have been defined for time delay (SL RSTD, UE Rx-Tx, RTOA), direction (AoA), power (RSRP). New positioning methods have also been added SL-RTT, SL-TDOA, SL-AoA. This positioning framework allows for both absolute positioning and relative positioning and ranging (where one UE is located with respect to another). Also hybrid SL, DL and UL positioning is possible, by combining measurements from the different nodes. This offers increased opportunities for accurate line of sight measurements, which is important because the availability of line of sight measurements is a limiting factor for wireless positioning in general.

[0040] When a network operates in Dynamic TDD, SBFD or IBFD duplex modes it can happen that UEs transmitting UL during a symbol or slot, which is used for DL by the same or other network nodes, of the same or other operators, interfere with other UEs receiving DL in the same network, and / or in adjacent channels / bands, generating UE-to- UE Cross-Link Interference (CLI). This interference is usually less disruptive than the BS- to-BS interference, due to the relatively lower UE transmit power compared to network node transmit power. However, if two UEs happen to be at a close mutual distance and the first one is scheduled UL while the second one is scheduled DL at the same time, CLI from the first UE can impact DL performance of the second UE. Such UE-to-UE CLI can be:

[0041] Co-channel UE-UE CLI: The UL from the UEs in the SBFD / SFFD / DTDD network interferes with other UEs attempting to receive DL in the same network. In case of SBFD / SFFD network, UE-to-UE CLI can come from the same cell or from a different cell (see FIG. 5, which shows co-channel UE-to-UE CLI in one cell, and FIG. 6, which shows co-channel UE-to-UE CLI from different cells (same operator)). In case of DTDD UE-to-UE CLI comes only from another cell (FIG. 6).

[0042] Adjacent channel UE-UE CLI: The UL from the UEs in one SBFD / SFFD / DTDD network interferes with other UEs receiving DL in adjacent channels / bands / networks (see FIG. 7, which shows adjacent channel UE-to-UE CLI). In results reported, e.g., in 3GPP TR38.858, where adjacent channel UE-to-UE CLI is specifically studied, it was shown that if users are uniformly distributed in a wide coverage area, their chance to be close to each other and be scheduled in opposite directions at the same time is low, and UE-to-UE CLI does not damage DL performance. However, if UEs are close to each other and clustered in such a way that their distance is e.g. always less than 50 m, DL performance of legacy TDD UEs can be impacted by UE- to-UE CLI, especially DL edge users performance (5%-tile throughput).

[0043] As a result, the UE-to-UE CLI does not only impact DL UEs in DTDD / SBFD / SFFD networks, but also in TDD networks, in case said TDD network is neighbor to a DTDD / SBFD / SFFD second network.

[0044] An option for detecting if a UE is affected by UE-to-UE CLI is to analyze measurement reports from the UE in terms of RS SI (Received Signal Strength Indicator) (CLI-RSSI). This is an indicator that includes the co-channel non-serving cell signal, adjacent channel interference and even the thermal noise within the specified band. However, even if a UE reports a low RSSI, it may not be possible to know if this is caused by UE-to-UE CLI, and by what aggressor UE. More information like the relative position with respect to other UEs would provide more insight about if the UE may be victim of UE-to-UE CLI, before making scheduling decisions.

[0045] SUMMARY

[0046] Some embodiments advantageously provide methods, systems, and apparatuses for UE-to-UE interference avoidance and mitigation.

[0047] Described herein are solutions to estimate the relative distance between UEs, and in case a pair of UEs are estimated to have a relative distance below a threshold, SBFD / DTDD / SFFD network nodes should take scheduling strategies oriented to avoid appearance of UE-to-UE CLI, e.g., not to schedule the two UEs in UL and DL at the same time, or to make the potential victim DL more robust to additional sources of interference, e.g., schedule the DL of the UE victim of UE-to-UE CLI, with lower MCS (Modulation and Coding Scheme), fewer MIMO layers, adaptive power control, include repetitions, etc. Also, a TDD network would benefit from the approaches described herein, since if this TDD network is neighbor to a DTDD / SBFD / SFFD second network, its UEs may be victim of adjacent channel UE-to-UE CLI. The said relative position of pairs of users is to be evaluated taking advantage of positioning techniques, architecture, protocols, measurements and methods, e.g., as introduced during 3 GPP Releases 16 and 18, and which can be further extended for the UE-to-UE interference avoidance and mitigation use case. In particular, a bistatic localization framework, such as that provided by 5G positioning features specified in 3 GPP Release 16 and lately extended in 3 GPP Release 18 for the sidelink case. The positioning framework should be extended to evaluate the relative distance between UEs. Bistatic and monostatic localization is also an important use case considered for ICAS (Integrated Sensing and Communication), so the corresponding framework and features can also be used / extended to derive the relative distance between UEs, based on which scheduling decisions are to be made. Overall, UE- to-UE CLI avoidance and mitigation can be seen as another use case for positioning or ICAS.

[0048] Approaches described herein can help a DTDD / SBFD / SFFD network become aware of UEs at risk of suffering from UE-to-UE interference in DL and avoid this from happening, or reduce its impact, so that DL performance is not jeopardized. Some embodiments can also help a TDD network with neighbor DTDD / SBFD / SFFD network, become aware of UEs at risk of suffering adjacent channel UE-to-UE interference in DL avoid it happening, or reduce its impact.

[0049] According to one aspect of the present disclosure, a method implemented in a network node in communication with a first user equipment, UE, is provided. The method comprises determining that a distance between the first UE and a second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE- to-UE Cross Link Interference, CLI, between the first UE and the second UE; and performing the action based on the determination.

[0050] According to one or more embodiments of this aspect, determining whether the distance is below the threshold comprises: transmitting, to a positioning manager, one or both of positioning information corresponding to relative positions of the first UE and the second UE, and measurement information; and receiving an indication from the positioning manager indicating that the distance between the first UE and the second UE is below the threshold.

[0051] According to one or more embodiments of this aspect, determining whether the distance is below the threshold is based on receiving, from the first UE, one or more of: a downlink positioning reference signal measurement; a sidelink positioning reference signal; a measurement; and an uplink sounding reference signal.

[0052] According to one or more embodiments of this aspect, the action comprises scheduling the first UE and the second UE to avoid one of the first UE and the second UE being in Uplink, UL, when the other of the first UE and the second UE is in Downlink, DL.

[0053] According to one or more embodiments of this aspect, the action comprises one or more of: reducing a Modulating and Coding Scheme, MCS; reducing a number of Multiple Input Multiple Output, MIMO, layers; adapting a transmission power; and configuring one of the first UE and the second UE with repetitions.

[0054] According to one or more embodiments of this aspect, method further comprises: requesting a Received Signal Strength Indicator, RS SI, report from each of the first UE and second UE, the determination that the distance is below the threshold associated with the RSSI reports, allows the determination that one of the two UEs is vulnerable to UE-UE CLI.

[0055] According to one or more embodiments of this aspect, determining that the distance is below the threshold comprises receiving an indication from a second network node associated with the second UE that the distance between the first UE and the second UE is below the threshold; and the action comprising sharing, with the second network node, one or both of scheduling information and future scheduling plans.

[0056] According to one or more embodiments of this aspect, determining whether the distance is below the threshold is based on receiving, from a second network node associated with the second UE, information associated with the second UE that comprises one or more of: positioning information and measurements.

[0057] According to another aspect of the present disclosure, a network node in communication with a first UE is provided. The network node is configured to: determine that a distance between the first UE and a second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE CLI between the first UE and the second UE; and perform the action based on the determination.

[0058] According to one or more embodiments of this aspect, determining whether the distance is below the threshold comprises: transmitting, to a positioning manager, one or both of positioning information corresponding to relative positions of the first UE and the second UE, and measurement information; and receiving an indication from the positioning manager indicating that the distance between the first UE and the second UE is below the threshold.

[0059] According to one or more embodiments of this aspect, determining whether the distance is below the threshold is based on receiving, from the first UE, one or more of: a downlink positioning reference signal measurement; a sidelink positioning reference signal; a measurement; and an uplink sounding reference signal.

[0060] According to one or more embodiments of this aspect, the action comprises scheduling the first UE and the second UE to avoid one of the first UE and the second UE being in UL when the other of the first UE and the second UE is in DL.

[0061] According to one or more embodiments of this aspect, the action comprises one or more of: reducing a MCS; reducing a number of MIMO layers; adapting a transmission power; and configuring one of the first UE and the second UE with repetitions.

[0062] According to one or more embodiments of this aspect, the network node is further configured to: request an RS SI report from each of the first UE and second UE, the determination that the distance is below the threshold associated with the RSSI reports, allows the determination that one of the two UEs is vulnerable to UE-UE CLI.

[0063] According to one or more embodiments of this aspect, determining that the distance is below the threshold comprises receiving an indication from a second network node associated with the second UE that the distance between the first UE and the second UE is below the threshold; and the action comprising sharing, with the second network node, one or both of scheduling information and future scheduling plans.

[0064] According to one or more embodiments of this aspect, determining whether the distance is below the threshold is based on receiving, from a second network node associated with the second UE, information associated with the second UE that comprises one or more of: positioning information and measurements.

[0065] According to another aspect of the present disclosure, a method implemented in a user UE in communication with a network node is provided. The method comprises causing transmission, to the network node, positioning information corresponding to a position of the UE, the positioning information being configured for use by the network node to determine whether a distance between the UE and another UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE- to-UE CLI between the UE and the other UE; and communicating with the network node based on the determination.

[0066] According to one or more embodiments of this aspect, the positioning information comprises one or more of: a downlink positioning reference signal measurement; a sidelink positioning reference signal; a measurement; and an uplink sounding reference signal. According to one or more embodiments of this aspect, the method further comprises: causing transmission of a downlink positioning reference signal; receiving and measure an uplink sounding reference signals transmitted by the other UE; and reporting the corresponding measurement.

[0067] According to one or more embodiments of this aspect, in response to transmitting the positioning information, the UE receives scheduling configured to avoid one of the UE and the other UE being in UL when the other of the UE and the other UE is in DL.

[0068] According to one or more embodiments of this aspect, responsive to transmitting the positioning information, the communicating with the network node is based on one or more of: a reduced MCS; a reduced number of MIMO layers; an adapted transmission power; and the UE being configured with repetitions.

[0069] According to one or more embodiments of this aspect, the method further comprises causing transmission of an RSSI report configured for use by the network node to determine whether the UEs are vulnerable to UE-UE CLI.

[0070] According to another aspect of the present disclosure, a UE in communication with a network node is provided. The UE is configured to: cause transmission, to the network node, of positioning information corresponding to a position of the UE, the positioning information being configured for use by the network node to determine whether a distance between the UE and another UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE CLI between the UE and the other UE; and communicate with the network node based on the determination.

[0071] According to one or more embodiments of this aspect, the positioning information comprises one or more of: a downlink positioning reference signal measurement; a sidelink positioning reference signal; a measurement; and an uplink sounding reference signal.

[0072] According to one or more embodiments of this aspect, the UE is further configured to: cause transmission of a downlink positioning reference signal; receive and measure an uplink sounding reference signals transmitted by the other UE; and report the measurement of the uplink sounding reference signals.

[0073] According to one or more embodiments of this aspect, in response to transmitting the positioning information, the UE receives scheduling configured to avoid one of the UE and the other UE being in UL when the other of the UE and the other UE is in DL.

[0074] According to one or more embodiments of this aspect, responsive to transmitting the positioning information, the communicating with the network node is based on one or more of: a reduced MCS; a reduced number of MIMO layers; an adapted transmission power; and the UE being configured with repetitions.

[0075] According to one or more embodiments of this aspect, the UE is further configured to cause transmission of an RSSI report configured for use by the network node to determine whether the threshold the UE is vulnerable to UE-UE CLI.

[0076] According to another aspect of the present disclosure, a method implemented in a positioning manager e.g. local management function, LMF, in 3 GPP positioning architecture, configured to communicate with a network node and a first UE is provided. The method comprises: receiving positioning information corresponding to relative positions of the first UE and a second UE; and determining based on the positioning information whether a distance between the first UE and the second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE- to-UE CLI between the first UE and the second UE, the first UE and the second UE one of belonging to a same network or belonging to different networks; and transmitting, to the network node , an indication that the distance is below the threshold.

[0077] According to one or more embodiments of this aspect, the indication comprises identifying which of the first UE and the second UE is vulnerable to the UE-to-UE CLI, the network node being associated with the identified one of the first UE and the second UE.

[0078] According to one or more embodiments of this aspect, the method further comprises estimating a position of UEs associated to neighboring cells of neighboring networks.

[0079] According to another aspect of the present disclosure, a positioning manager (e.g. LMF in 3 GPP positioning architecture)configured to communicate with a network node and a first UE is provided. The positioning manager is configured to: receive positioning information corresponding to relative positions of the first UE and a second UE; and determine, based on the positioning information, whether a distance between the first UE and the second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE CLI between the first UE and the second UE, the first UE and the second UE one of belonging to a same network or belonging to different networks; and cause transmission, to the network node , of an indication that the distance is below the threshold.

[0080] According to one or more embodiments of this aspect, the indication comprises identifying which of the first UE and the second UE is vulnerable to the UE-to-UE CLI, the network node being associated with the identified one of the first UE and the second UE.

[0081] According to one or more embodiments of this aspect, the positioning manager is further configured to estimate a position of UEs associated to neighboring cells of neighboring networks.

[0082] BRIEF DESCRIPTION OF THE DRAWINGS

[0083] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0084] FIG. l is a diagram of an NR slot;

[0085] FIGS. 2A-2D are diagrams of different types of duplex communication modes;

[0086] FIGS. 3A-3B are diagrams of TDD operations;

[0087] FIG. 4A-4D is a diagram of TDD operation options and interference cases;

[0088] FIG. 5 is a diagram of co-channel UE-to-UE CLI in one cell;

[0089] FIG. 6 is a diagram of co-channel UE-to-UE CLI from different cells (same operator);

[0090] FIG. 7 is a diagram of adjacent channel UE-to-UE CLI (different operators / networks);

[0091] FIG. 8 is a schematic diagram of an example network architecture illustrating a communication system according to the principles in the present disclosure;

[0092] FIG. 9 is a block diagram of several entities from FIG. 8 according to some embodiments of the present disclosure;

[0093] FIG. 10 is a flowchart of an example process in a network node according to some embodiments of the present disclosure; and

[0094] FIG. 11 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure;

[0095] FIG. 12 is a flowchart of an example process in a positioning manager according to some embodiments of the present disclosure;

[0096] FIG. 13 is a flowchart of another example process in a network node according to some embodiments of the present disclosure; and

[0097] FIG. 14 is a flowchart of another example process in a user equipment according to some embodiments of the present disclosure; FIG. 15 is a flowchart of another example process in a positioning manager according to some embodiments of the present disclosure;

[0098] FIG. 16 is flowchart of an example process for UE-to-UE interference avoidance according to some embodiments of the present disclosure; and

[0099] FIG. 17 is a diagram of an example procedure to compute the relative distance between UE1 and UE2 according to some embodiments of the present disclosure.

[0100] DETAILED DESCRIPTION

[0101] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to UE-to-UE interference avoidance and mitigation. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0102] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0103] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication. In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0104] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0105] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of wireless device capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0106] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0107] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0108] In some embodiments, the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B, or one or both of A and B . In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and / or A, B, C or a combination thereof.

[0109] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0110] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0111] Some embodiments provide UE-to-UE interference avoidance and mitigation. Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 8 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBS, eNBS, gNBS or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0112] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0113] The communication system 10 may comprise a positioning manager 24 (e.g., LMF) in communication with the network node 16.

[0114] A network node 16 is configured to include an interference mitigation unit (IMU) 32, which is configured to perform one or more network node 16 functions described herein, including functions related to UE-to-UE interference avoidance and mitigation. A user equipment 22 is configured to include a positioning unit 34, which is configured to perform one or more user equipment 22 functions described herein, including functions related to UE-to-UE interference avoidance and mitigation.

[0115] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 9. In a communication system 10, a positioning manager (e.g., LMF) 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The positioning manager 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0116] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by positioning manager 24. Processor 44 corresponds to one or more processors 44 for performing positioning manager 24 functions described herein. The positioning manager 24 includes memory 46 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 48 and / or the host application 50 may include instructions that, when executed by the processor 44 and / or processing circuitry 42, causes the processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to positioning manager 24. The instructions may be software associated with the positioning manager 24.

[0117] The software 48 may be executable by the processing circuitry 42. The processing circuitry 42 of the positioning manager 24 may include a control unit 54 configured to facilitate positioning of communication devices in the communication system 10.

[0118] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the positioning manager 24 and with the UE 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0119] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0120] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include IMU 32 configured to perform one or more network node 16 functions described herein, including functions related to UE-to- UE interference avoidance and mitigation.

[0121] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0122] The hardware 80 of the UE 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Thus, the UE 22 may further comprise software 90, which is stored in, for example, memory 88 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the UE 22. The client application 92 may interact with the user to generate the user data that it provides.

[0123] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 86 corresponds to one or more processors 86 for performing UE 22 functions described herein. The UE 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 84 of the user equipment 22 may include a positioning unit 34 configured to perform one or more UE 22 functions described herein, including functions related to UE-to-UE interference avoidance and mitigation.

[0124] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 9 and independently, the surrounding network topology may be that of FIG. 8.

[0125] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0126] Although FIGS. 8 and 9 show various “units” such as IMU 32, and positioning unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0127] FIG. 10 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the IMU 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 is configured to transmit positioning information corresponding to relative positions of the UE and a second UE to a LMF (Block SI 16). Network node 16 is configured to receive an indication from the LMF that a distance between UE 22 and the second UE 22 is below a threshold, the threshold corresponding to a risk of UE-to-UE CLI between the UE 22 and the second UE 22 (Block SI 18). Network node 16 is configured to perform an action based on the indication (Block S120).

[0128] In some embodiments, the action comprises scheduling the UE 22 and the second UE 22 to avoid one of the UE 22 and the second UE 22 being in UL when the other is in DL.

[0129] In some embodiments, the action comprises at least one of: reducing MCS; reducing a number of MIMO layers; adapting a transmission power; and adding repetitions.

[0130] In some embodiments, the action comprises requesting and monitoring a RSSI.

[0131] FIG. 11 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 84 (including the positioning unit 34), processor 86, radio interface 82 and / or communication interface 60. User equipment 22 is configured to transmit positioning information corresponding to relative positions of the UE to an LMF, the positioning information being usable by the LMF to determine that a distance between UE 22 and the second UE 22 is below a threshold (Block S122). User equipment 22 is configured to communicate with the network node based on the determination (Block S124).

[0132] In some embodiments, the communicating with the network node comprises being scheduled to avoid one of the UE 22 and the second UE 22 being in UL, when the other is in DL.

[0133] In some embodiments, the communicating with the network node 16 is based on at least one of: a reduced MCS; a reduced a number of MIMO layers; an adapted transmission power; and added repetitions.

[0134] FIG. 12 is a flowchart of an example process in a positioning manager 24(e.g., LMF), according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of positioning manager 24 such as by one or more of processing circuitry 42 (including the control unit 54), processor 44, and / or communication interface 40. Positioning manager 24 is configured to receive positioning information corresponding to relative positions of the UE 22 and a second UE 22 (Block S126). Positioning manager 24 is configured to transmit to the network node 16 an indication that a distance between UE 22 and the second UE 22 is below a threshold, the threshold corresponding to a risk of UE-to-UE CLI between the UE 22 and the second UE, the indication being configured to cause the network node to perform at least one action (Block S128).

[0135] In some embodiments, the action comprises scheduling the UE 22 and the second UE 22 to avoid one of the UE 22 and the second UE 22 being in UL when the other is in DL.

[0136] In some embodiments, the action comprises at least one of reducing MCS; reducing a number of MIMO layers; adapting a transmission power; and adding repetitions.

[0137] In some embodiments, the action comprises requesting and monitoring a RSSI.

[0138] FIG. 13 is a flowchart of another example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the IMU 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 is configured to determine (Block S130) that a distance between the first UE (22) and a second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE Cross Link Interference, CLI, between the first UE (22) and the second UE. Network node 16 is configured to perform (Block SI 32) the action based on the determination.

[0139] In some embodiments, determining whether the distance is below the threshold comprises: transmitting, to a positioning manager 24, one or both of positioning information corresponding to relative positions of the first UE 22 and the second UE, and measurement information; and receiving an indication from the positioning manager indicating that the distance between the first UE 22 and the second UE is below the threshold.

[0140] In some embodiments, determining whether the distance is below the threshold is based on receiving, from the first UE 22, one or more of a downlink positioning reference signal measurement; a sidelink positioning reference signal; a measurement; and an uplink sounding reference signal. In some embodiments, the action comprises scheduling the first UE 22 and the second UE to avoid one of the first UE 22 and the second UE being in Uplink, UL, when the other of the first UE 22 and the second UE is in Downlink, DL.

[0141] In some embodiments, the action comprises one or more of reducing a Modulating and Coding Scheme, MCS; reducing a number of Multiple Input Multiple Output, MIMO, layers; adapting a transmission power; and configuring one of the first UE 22 and the second UE with repetitions.

[0142] In some embodiments, the network node 16 is further configured to: request a Received Signal Strength Indicator, RS SI, report from each of the first UE 22 and second UE, the determination that the distance is below the threshold being based on the RSSI reports. That is, the determination that the distance is below the threshold associated with the RSSI reports may be used as part of a determination that one of the two UEs is vulnerable to UE-UE CLI.

[0143] In some embodiments, determining that the distance is below the threshold comprises receiving an indication from a second network node associated with the second UE that the distance between the first UE and the second UE is below the threshold; and the action comprising sharing, with the second network node, one or both of scheduling information and future scheduling plans.

[0144] In some embodiments, determining whether the distance is below the threshold is based on receiving, from a second network node associated with the second UE, information associated with the second UE that comprises one or more of positioning information and measurements.

[0145] FIG. 14 is a flowchart of another example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 84 (including the positioning unit 34), processor 86, radio interface 82 and / or communication interface 60. User equipment 22 is configured to cause (Block SI 34) transmission, to the network node 16, positioning information corresponding to a position of the UE 22, the positioning information being configured for use by the network node to determine whether a distance between the UE 22 and another UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE Cross Link Interference, CLI, between the UE 22 and the other UE. User equipment 22 is configured to communicate (Block S136) with the network node 16 based on the determination. In some embodiments, the positioning information comprises one or more of: a downlink positioning reference signal measurement; a sidelink positioning reference signal; a measurement; and an uplink sounding reference signal.

[0146] In some embodiments, the UE 22 is further configured to: cause transmission of a downlink positioning reference signal; receive and measure an uplink sounding reference signals transmitted by the other UE; and report the measurement of the uplink sounding reference signals.

[0147] In some embodiments, in response to transmitting the positioning information, the UE receives scheduling configured to avoid one of the UE 22 and the other UE being in Uplink, UL, when the other of the UE 22 and the other UE is in Downlink, DL.

[0148] In some embodiments, responsive to transmitting the positioning information, the communicating with the network node 16 is based on one or more of: a reduced Modulating and Coding Scheme, MCS; a reduced number of Multiple Input Multiple Output, MIMO, layers; an adapted transmission power; and the UE 22 being configured with repetitions.

[0149] In some embodiments, the UE 22 is further configured to cause transmission of a Received Signal Strength Indicator, RS SI, report configured for use by the network node 16 to determine whether the distance is below the threshold.

[0150] FIG. 15 is a flowchart of another example process in a positioning manager 24 (e.g., LMF), according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of positioning manager 24 such as by one or more of processing circuitry 42 (including the control unit 54), processor 44, and / or communication interface 40. Positioning manager 24 is configured to receive (SI 38) positioning information corresponding to relative positions of the first UE 22 and a second UE. Positioning manager 24 is configured to determine (S140) based on the positioning information whether a distance between the first UE 22 and the second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE Cross Link Interference, CLI, between the first UE 22 and the second UE, the first UE 22 and the second UE one of belonging to a same network or belonging to different networks. Positioning manager 24 is configured to transmit (S142), to the network node 16, an indication that the distance is below the threshold In some embodiments, the indication comprises identifying which of the first UE 22 and the second UE is vulnerable to the UE-to-UE CLI, the network node being associated with the identified one of the first UE 22 and the second UE.

[0151] In some embodiments, the positioning manager 24 is further configured to estimate a position of UEs associated to neighboring cells of neighboring networks.

[0152] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for UE-to-UE interference avoidance and mitigation. One or more UE 22 functions described below may be performed by one or more of processing circuitry 84, processor 86, positioning unit 34, etc. One or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, IMU 32, etc.

[0153] FIG. 16 is an example flowchart for UE-to-UE interference avoidance. The UEs’ positions in own and neighbor cells are estimated (Block SI 50). The relative distance between the UEs in their own and neighbor cells is estimated (Block SI 52). Scheduling decisions are made to avoid or reduce UE-to-UE CLI (Block SI 54).

[0154] In some embodiments, one operator network deploying Dynamic TDD, SBFD or SFFD. DL PRS and UL SRS are configured to be transmitted and received by network nodes and UEs 22 in the network. If UEs 22 are sidelink capable, also SL PRS can be transmitted and received by UEs 22. For the case of SBFD, DL PRS may be limited to the configured DL subbands and UL SRS are limited to the configured UL subband. For sidelink capable UEs 22 SL PRS are limited to the UL subband configured for the transmitting UE. From a measuring UE’s point of view, this SL PRS is transmitted from node with a BWP (Bandwidth Part) that is the same size as said first UE’s UL subband size.

[0155] Non-Limiting example embodiments include:

[0156] 1. A method for a network deploying Dynamic TDD, SBFD or SFFD, to take advantage of, e.g., 3GPP Rel. 16 and 18 5G positioning architecture, signaling and measurements, to derive the position of UEs 22 in the same or different cells, in the same operator, based on standardized or not standardized, RAT-dependent or hybrid positioning methods. a. Based on standardized measurements of DL PRS and / or UL SRS reported to positioning manager 24 (e.g., via LMF), positioning information should be processed and the scope of LMF may have to be extended, in order to derive the relative distance between one or more pairs of UEs 22. b. If the UEs 22 are sidelink capable, based on standardized measurements of SL PRS, the relative position between one or more pairs of UEs 22 can be derived, based on defined positioning methods. Two UEs 22 of a pair can be associated to the same or different cells. This relative distance between one or more pairs of UEs 22 is reported to the LMF. c. If two UEs 22 are close by, but they are not in line of sight, their impact on UE-UE CLI would be reduced, and to improve the accuracy for these cases, SL, DL and / or UL positioning measurements can also be combined. As a non-limiting example embodiment, a UE 22 may be configured to receive and measure a DL PRS and a SL PRS, then both can be reported, and also their RSTD. d. UEs 22 can be configured to measure multiple kinds of reference signals, DL PRS, UL SRS, SL PRS, etc., in order to reduce the overhead to identify UE- to-UE CLI issues. e. In another embodiment, a first UE 22 is configured to transmit PRS (referred to as UE-PRS). i. In case of a SBFD UE 22, the UE-PRS is limited to the UL subband configured for said first UE. From a measuring UE’s 22 point of view, this UE- PRS is transmitted from a network node with a BWP that is the same size as said first UE’s UL subband size. ii. At least one second UE 22 is configured to measure at least said UE-PRS transmission from said first UE 22 and to provide to the network (LSF) the corresponding positioning related reports. iii. Said positioning related reports include at least the reference signal received power (PRS-RSRP) of said PRS transmission from said first UE 22. iv. Said positioning related reports can include receive timing related measurement to said UE-PRS transmission from said first UE 22. As a nonlimiting example embodiment, said receive timing related measurement to said UE- PRS transmission from said first UE 22 is a UE Rx-Tx time difference. Other standardized or not-standardized measurements can be reported. v. If said second UE 22 is additionally configured to measure at least one DL-PRS transmission from the network, said positioning related reports include at least DL PRS Received Signal Time Difference (RSTD) between said UE-PRS transmission from said first UE 22 and said at least one DL-PRS transmission from the network. f. In another embodiment, a first UE 22 is configured to transmit UL- SRS. At least one second UE 22 is configured to measure at least the UL-SRS transmission from said first UE 22 and to provide to the network the corresponding positioning related reports. i. Said positioning related reports include at least the reference signal received power (SRS-RSRP) of said SRS transmission from said first UE 22. ii. Said positioning related reports can include receive timing related measurement to said UL-SRS transmission from said first UE 22. As a nonlimiting example embodiment, said receive timing related measurement to said UL-SRS transmission from said first UE 22 is a UE Rx-Tx time difference. Also other standardized measurement reports could be included. g. If the estimated relative distance between a pair of UEs 22 is below a certain threshold, the pair of UEs 22 are flagged as “UEs at risk of being victim / aggressor of UE-to-UE CLI.” h. The positioning manager 24 (e.g., via LMF) reports at least the following to the serving network node 16 of the UEs 22: i. information on the UE 22 or UEs 22 at risk of UE-to-UE CLI. ii. If the two UEs 22 are attached to different network nodes 16, the information on the network node 16 to which the other victim / aggressor UE 22 is associated.

[0157] 2. The same as Example 1, but a UE 22 may also, contain an independent positioning function based on GNSS (e.g., GPS) and thus be able to report its position. The UE 22 with an independent positioning function may also make use of assistance information obtained from the network.

[0158] 3. The method further comprises a procedure for the network node 16 to make scheduling decisions based on information on estimated relative position between pairs of UEs 22, received by positioning manager 24 (e.g., via LMF). a. If the two UEs 22 are associated to the same cell, and the network is SBFD or SFFD, the network node 16 can: 1. act proactively and not schedule them at the same time in

[0159] UL and DL. ii. Act proactively and improve the robustness to interference of the DL of the UE 22 victim of UE-to-UE CLI, e.g. by reducing MCS or the number of MIMO layers, activating power adaptation or beam adaptation mechanisms, or introducing repetitions. iii. Act reach vely and reschedule the two UEs 22 so that they are not allocated UL and DL at the same time, if and when the DL UE RSSI reports are below a threshold. iv. Act reactively to change the schedule policy and improve robustness to interference of the DL UE by reducing MCS, or the number of MIMO layers, activating power adaptation or beam adaptation, or introducing repetitions, if the DL UE RSSI reports are below a threshold. b. If the two UEs 22 are associated one to the serving cell and one to a neighbor cell, and the network is DTDD, SBFD, DFFD, each network node 16 can take for its UE 22 at risk of UE-to-UE CLI, any of the following actions: i. If the network node 16 is to schedule DL a UE 22 at risk of UE-to-UE CLI, then it is potential victim of UE-to-UE CLI. In this case, include in the scheduling decision the RSSI information reported by the flagged UE 22. If the Reported RSSI is below a threshold, the network node 16 can change the DL / UL scheduling allocation to avoid potential UE-to-UE CLI from the close UE 22 associated to the neighbor cell, or to improve robustness to interference e.g. by reducing MCS, or increasing allocated power, or reducing MIMO layers, or adding repetitions, etc. ii. The DL / UL scheduling allocation can be shared with the neighbor network node 16, so that it is taken into account for the scheduling allocation of the neighbor UE 22, by the neighbor network node 16. iii. If any scheduling information is received by a network node 16, after sharing by neighbor network node 16, this should be considered to avoid scheduling the two UEs 22 at the same time and so avoid UE-to-UE CLI. iv. If both network nodes 16 share information some kind of prioritization on which one to consider should be implemented. As non-limiting example embodiments of possible prioritization criteria, the more recent scheduling information, or the information of the UE 22 allocating DL could be prioritized. v. A set of neighbor network nodes 16 can coordinate to share a scheduling plan over a future number of slots for UEs 22 that are at risk of suffering UE-to-UE CLI. The scheduling plan avoids simultaneously scheduling UEs 22 that create / experience CLI.

[0160] 4. The same method in (1) can be further extended to UEs 22 associated to cells belonging to different operators, to avoid adjacent channel UE-to-UE CLI. It is assumed a multi -operator network where at least one of the neighboring operators deploys Dynamic TDD, SBFD or SFFD. In this case not only a UE 22 served by a DTDD, SBFD or SFFD network may be victim of UE-to-UE CLI, but also a legacy UE 22 served by a legacy TDD network, which is neighbor to a DTDD, SBFD or SFFD network. As a result, the following embodiments apply to users in TDD, DTDD, SBFD or SFFD networks. a. Some level of exchange of information between neighbor operators is allowed to facilitate the relative positioning of close UEs 22 associated to cells of different operators: i. As a nonlimiting example embodiment, SRS positioning positions from UEs 22 in neighbor cells, in neighbor networks are shared between network nodes 16 from different operators, so that positioning methods, e.g. UL-AoA, can be applied to derive positioning information as in (1). ii. UEs 22 of different operators can be configured to measure multiple kinds of reference signals, DL PRS, UL SRS, SL PRS, etc., from UEs 22 of other operators, in order to reduce the overhead to identify UE-to-UE CLI issues. iii. As a nonlimiting example embodiment, if UEs 22 of the two different operators are sidelink capable, they can rely on sidelink positioning protocol to derive their relative distance, which is then reported to their respective positioning manager 24 (e.g., via LMF). Since the two UEs 22 are attached to different operators, as nonlimiting example embodiment, depending on the kind and level of information shared between the two operators, the UEs 22 can be configured to exchange SL PRS as if they were out of coverage, thus following UE 22 autonomous SL PRS resource allocation, or following the network centric resource allocation approach. Then each UE 22 could report its measurement to its network LSF. iv. As another nonlimiting example embodiment, a first UE 22 in operator 1 is configured to transmit a UE-PRS. At least one second UE 22 in operator 2 is configured to be able to measure at least said UE-PRS transmission from said first UE 22 and to provide to the network (its network LSF) the corresponding positioning related reports.

[0161] 1. Said positioning related reports include at least the reference signal received power (PRS-RSRP) of said UE-PRS transmission from said first UE 22. Said positioning related reports can include receive timing related to said UE-PRS transmission from said first UE 22. As a nonlimiting example embodiment, said receive timing related measurement to said UE-PRS transmission from said first UE 22 is a UE Rx-Tx time difference, or other standardized measurements.

[0162] 2. If the second UE 22 from operator 2 is configured to receive DL-PRS from its network and UE-PRS from neighbor UEs 22, attached to adjacent networks, both measurements and their RSTD can be reported to the network LSF. v. As another non-limiting example embodiment, a first UE 22 in operator 1 is configured to transmit UL-SRS. At least one second UE 22 in operator 2 is configured to be able to measure at least the UL-SRS transmission from said first UE 22 and to provide to its network LSF the corresponding positioning related reports. Said positioning related reports include at least the reference signal received power (SRS- RSRP) of said UL-SRS transmission from said first UE 22. Said positioning related reports can include receive timing related measurement to said SRS transmission from said first UE 22. As a nonlimiting example embodiment, said receive timing related measurement to said SRS transmission from said first UE 22 is a UE Rx-Tx time difference, or other standardized measurements. b. The LMF scope should be further extended to manage measurements, calculation and information of positions of UEs 22 belonging to another network, and relative distance between UEs 22 of the own network and of the other operator. c. Positioning manager 24 (e.g., via LMFjcommunicates to the network node 16 in its own operator the UE 22 who is at risk of adjacent channel UE-to- UE CLI.

[0163] 5. The method in Example 4, further comprising a procedure for the network node 16 to make scheduling decisions based on the information received by the LMF. a. If the UE 22 is to be scheduled DL, it is at risk to be victim of UE- to-UE CLI. If the RSSI reports are below threshold, the DL scheduling allocation is modified to try to avoid adjacent channel UE-to-UE CLI, or to improve robustness to interference, e.g. reduce MCS, or MIMO layers, add repetitions, etc.

[0164] Case 1: 1 operator

[0165] In a one operator deployment, co-channel UE-to-UE CLI may appear inside the same cell, for SBFD and SFFD deployments, and between UEs 22 in different cells for DTDD, SBFD, and SFFD deployments. In said one operator network scenario, deploying Dynamic TDD, SBFD or SFFD, DL PRS and UL SRS are configured to be transmitted and received by network nodes 16 and UEs 22 in the network. If UEs 22 are sidelink capable, also SL PRS can be transmitted and received by UEs 22. For the case of SBFD, DL PRS are limited to the configured DL subbands and UL SRS are limited to the configured UL subband. For sidelink capable UEs SL PRS are limited to the UL subband configured for the transmitting UE 22. From a measuring UE’s 22 point of view, this SL PRS is transmitted from node with a BWP (Bandwidth Part) that is the same size as said first UE’s 22 UL subband size.

[0166] Following the flowchart described in FIG. 16, the three blocks shown therein can be detailed as discussed in the following sections:

[0167] Estimate UEs 22’ s positions, in own and neighbor cells

[0168] 3GPP has specified in Release 16 positioning signals and measurements for 5G NR. In 3GPP Release 18 the positioning framework has been extended to sidelink positioning. NR positioning framework has provided not only enablers for precise positioning as such (like specific reference signal, DL PRS, UL SRS, SL PRS, and improved architecture and protocols), but has also introduced some new positioning methods (as for example, multi-cell round trip time (multi-RTT) measurements, multiple antenna beam measurements to enable downlink angle of departure (DL-AoD) and uplink angle of arrival (UL-AoA) and SL-RTT, SL-TDOA, SL-AoA ).

[0169] Some embodiments rely on the available positioning architecture and protocols, signaling, measurements and methods, so that in a given DTDD, SBFD or SFFD network, position information of UEs 22 in a given serving cell and in the neighbor cells, can be derived. Localization is also a use case for ICAS, so that also ICAS framework and corresponding developed features can be used to reach to the information that may be needed by some embodiments.

[0170] In 3GPP Release 16 positioning architecture, the positioning manager 24 (e.g., via LMF) entity is in charge of computing the position of the UEs 22 in the context of the Radio Access Network. The LMF can achieve positioning information by means of standardized or not standardized positioning methods, or by means of GNSS methods independently reported by the UE 22, or with the assistance of further information obtained from the network, i.e. using hybrid methods.

[0171] The UEs 22 are configured to report measurements to the positioning manager 24 (e.g., via LMF) for the purpose above described. These measurements are based on observation of standardized positioning specific reference signals, the DL PRS and the UL SRS. In addition, taking advantage of Release 18 positioning improvements in the area of sidelink positioning, for the case of UEs 22 sidelink capable, SL PRS can also be used and measured by other UEs 22.

[0172] To reduce overhead in the identification of position of UEs 22, and to overcome inaccuracies due to line of sight vs non-line of sight measurements, as an improvement to currently available NR positioning framework, UEs 22 should be configured to be able to monitor multiple kinds of reference signals, SL PRS, DL PRS and UL SRS, and report measurements about power, time delay, and directions, and relative measurements, like RSTD. Also, UEs 22 can be configured to transmit PRS, which can be received by other UEs 22 as if those were transmitted by the network. By means of all these measurements reported to positioning manager 24 (e.g., LMF) it is possible to derive the relative distance between UEs 22 through known standardized and nonstandardized positioning methods.

[0173] Estimate relative distance between UEs 22 in own and neighbor cells

[0174] The scope of the LMF of a DTDD / SBFD / SFFD network is to be extended. The LMF, based on the collected positioning information from the UEs 22 computes the relative distance between multiple pairs of UEs 22 in the same cell and in different cells. A non-limiting example of how the relative distance between two UEs 22 associated to the same network node 16 can be computed by simple trigonometry, assuming knowledge that can be derived by standardized DL / UL measurements, is given in FIG. 17.

[0175] Distance d3 between UE1 22 and UE2 22 can be computed as follows: d3= d + d2— 2d1d2(cos [sin

[0176] For sidelink capable UEs 22, which are configured to transmit and measure SL PRS, 3GPP Release 19 has also included a positioning use case to compute relative distance between devices, which can be reused.

[0177] Once derived, relative position information between pairs of UEs 22, the positioning manager 24 (e.g., via LMF) identifies those pairs of UEs 22 which are at a distance below a certain threshold. Said threshold can vary depending on the kind of deployment, frequency range of operation, etc. The UEs 22 which are at a distance lower than the given threshold are flagged as at “risk of being victim-aggressor of UE-to-UE CLI”, depending on whether they are allocated for DL or UL. Specifically, if they are allocated for DL they are potential victim of LE-to-UE CLI and when they are allocated to UL they are potential aggressors.

[0178] If the pair of UEs 22 are attached to the same network node 16 (SBFD / SFFD cases), this network node 16 is informed of the fact that these two specific UEs 22 are at risk of UE-to-UE CLI.

[0179] If the UEs 22 are attached to different network nodes 16 (DTDD / SBFD / SFFD cases) of the same network, so that they are attached to different cells, each network node 16 is informed of:

[0180] The UE 22 attached to the network node 16, which is at risk of UE-to-UE CLI,

[0181] The network node 16 to which the other UE 22 of the pair is attached, and which is potential victim / aggressor of the UE-to-UE CLI.

[0182] Make scheduling decisions to avoid UE-to-UE CLI

[0183] The actions to take to avoid UE-to-UE CLI interference, in an SBFD / SFFD or DTDD network, vary depending on whether the pair of UEs 22 victim-aggressor of UE-to- UE CLI are associated to the same cell or to different cell.

[0184] If the two UEs 22 are associated to the same cell (SBFD / SFFD cases), as shown in FIG. 5, the network node 16 can decide to:

[0185] Act proactively and never schedule these two UEs 22 in the same time UL and DL.

[0186] Act proactively and increase the robustness to interference of the DL from the UE 22 victim of potential UE-to-UE CLI, by for example reducing the MCS, reducing the number of MIMO layers, adapt the transmission power, or adding repetitions.

[0187] Act reactively, and monitor the RS SI report from the two UEs 22, if they are below a given threshold, it can be assumed that UE-to-UE CLI is among the causes of the poor performance, and the scheduling allocation is changed so that they are not allocated UL and DL at the same time, or the robustness to interference of the DL from the UE 22 victim of potential UE-to-UE CLU, by for example reducing the MCS, reducing the number of MIMO layers, adapt the transmission power, or adding repetitions.

[0188] If the two UEs 22 are associated to different cells (DTDD / SBFD / SFFD cases) of the same network, as shown in FIG. 6, each network node 16 can act independently or start actions to coordinate with the network node 16 to which the other UE 22 of the pair is associated:

[0189] If the UE 22 is to be scheduled DL (as UE1 22 in FIG. 6), it is potentially a victim of UE-to-UE CLI, and unless information is exchanged with the neighbor network node 16, there is no information available on the UL resource allocation of the potential aggressor, and vice-versa, the UL UE2 22 has no information available on the resource allocation of the potential victim UE1 22.

[0190] The following actions are possible at the two network nodes 16: o RS SI reports are monitored, if they are below a given threshold, each network node 16 may decide, without coordinating with the neighbor network node 16, to modify the scheduling strategy e.g. by changing in time the resource allocation of its UE 22, assuming UE-to-UE CLI is the cause of the low RSSI; by reducing the MCS, reducing the number of MIMO layer, adapting the power, or introducing repetitions of the DL to the victim UE 22, to increase robustness to interference. o In some cases, where RSSI is low, the DL resource allocation of UE1 22 can be shared with BS2 (e.g., a network node 16), or the UL resource allocation of UE2 22 can be shared with BS1 (e.g., a network node 16), so that the network nodes 16 can take it into account this information and not schedule the UEs 22 at the same time. o If any information is shared by a network node 16 about the allocation of its UE 22, this should be considered to avoid potential UE-to-UE CLI. o If both the network nodes 16 are sharing information, one should be prioritized over the other to have the second network node 16 adapt to the scheduling decision of the first network node 16. Some nonlimiting examples with criteria for prioritization could be the most recent scheduling message, or the allocation of the DL, since it is the victim, etc. o A set of neighbor network nodes 16 can co-ordinate to share a scheduling plan over a future number of slots for UEs 22 that are at risk of CLI. The scheduling plan avoids simultaneously scheduling UEs 22 that create / experience CLI.

[0191] Case 2: 2 operators

[0192] In a scenario with two operators, there may exist co-channel UE-to-UE CLI inside one cell for SBFD / SFFD deployments, and between UEs 22 in different cells for DTDD / SBFD / SFFD deployments, but also adjacent channel UE-to-UE CLI has to be addressed. In this case, also UEs 22 of a TDD network may be victim of adjacent channel UE-to-UE CLI, if said TDD network is neighbor to a DTDD / SBFD / SFFD network, where UL is deployed in DL synchronized slots. As a result, principles of embodiments described above for DTDD / SBFD / SFFD network should be extended in this multioperator case also for TDD networks.

[0193] Estimate UEs’ 22 positions, in own and neighbor cells of neighbor operator

[0194] Some embodiments rely on the available NR positioning architecture, protocols, signaling, methods and measurements, e.g., as defined in 3GPP Release 16 and 18, or on ICAS framework and associated features.

[0195] In a multi-operator scenario, the LMF scope may have to be extended so that also the position of UEs 22 in neighbor cells of neighbor operator can be estimated. This means that the LMF of each network may have to be able to manage and derive positioning information not only of UEs 22 in its own network, but also in neighbor cells of neighbor operators.

[0196] For this purpose, different levels of cooperation and information sharing between the two operators can be envisioned. For example, the network can be configured to be able to measure UL SRS from UEs 22 in the neighbor operator, and based on these measurements, positioning methods can be applied similarly to the case of 1 operator. For this purpose, UL SRS positions should be shared between operators.

[0197] Another possible option is that sidelink capable UEs 22 in the two operators are configured to measure the SL PRS sent by UEs 22 from other operators. The SL resource allocation can be network centric or UE 22 autonomous, depending on the kind of coordination that is envisaged for the two operators. Similarly, UEs 22 in the neighbor operators can be configured to send and measure PRS or SRS also from other operators.

[0198] These reference signals are then measured by UEs 22 in another operator. Power, time-delay or direction measurements could be reported. Each UE 22 reports the observed measurements to its own LSF, which then estimates the relative distance between its UEs 22 and the UEs 22 of the other operator, and if any of the UEs 22 in its network is at risk of suffering UE-to-UE CLI.

[0199] Estimate relative distance between UEs 22 in own and neighbor cells of neighbor operator

[0200] In a multi-operator deployment, the scope of the LMF of a TDD / DTDD / SBFD / SFFD network may be extended in such a way that the LMF, based on the collected positioning information, computes the relative distance between UEs 22 of one operator and those of the other. The positioning manager 24 (e.g., via LMF) identifies pairs of UEs 22 which are at a distance below a certain threshold, which can vary depending on the deployment, frequency range of operation, etc. The UEs 22 which are at a distance lower than the given threshold are flagged as at risk of being victim-aggressor of adjacent channel UE-to-UE CLI. The LMF finally informs the network node 16 of its network of the UE 22 that is a potential victim of adjacent channel UE-to-UE CLI.

[0201] Make scheduling decisions to avoid UE-to-UE CLI

[0202] The UE 22 reports RSSI, which are monitored by the network node 16. If the RSSI reports are below a given threshold, the BS1 (e.g., network node 16) of operator 1, as depicted in FIG. 7, assumes that the DL performance may be affected by adjacent channel UE-to-UE CLI and adjusts accordingly the scheduling strategies, by e.g. rescheduling in time UE1 22, in the hope that in the new time allocation it is not flagged at risk anymore, or improving the robustness of the DL to UE1 22 (e.g. reducing MCS or MIMO layers, adapting the transmission power, adding repetitions)

[0203] New capability requirements for some embodiments include:

[0204] Capability of UEs 22 to send PRS (UE-PRS);

[0205] Capability of UEs 22 to measure UL-SRS;

[0206] Capability of UEs 22 to be configured to measure multiple kinds of reference signals, DL-PRS, UE-PRS, UL-SRS, SL PRS and potentially combine measurements to be reported to the network;

[0207] Extension of LMF functionalities to include the abilities to calculate relative distance between multiple pairs of UEs 22, associated to same and different cells in the same operator.

[0208] Extension of LMF functionalities to include the ability to manage and derive positioning information of UEs 22 in other networks and derive the relative distance from them to UEs 22 in the own network.

[0209] Capability of LMF to share information with network nodes 16 about UEs 22 at risk of UE-to-UE CLI, co-channel and adjacent channel.

[0210] Capability of network nodes 16 to share scheduling information with neighbor network nodes 16 in the same network, in case they detect impact of UE-to-UE CLI.

[0211] Capabilities of network nodes 16 to share and coordinate scheduling plans where UEs 22 at risk of suffering UE-to-UE CLI are not scheduling in UL and DL at the same time. Example:

[0212] Example Al . A network node 16 configured to communicate with a user equipment, UE, 22 the network node 16 configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: transmit positioning information corresponding to relative positions of the UE 22 and a second UE to a Local Management Function, LMF; receive an indication from the LMF that a distance between UE and the second UE is below a threshold, the threshold corresponding to a risk of UE-to-UE Cross Link Interference, CLI between the UE and the second UE; and perform an action based on the indication.

[0213] Example A2. The network node 16 of Example Al, wherein the action comprises scheduling the UE 22 and the second UE to avoid one of the UE 22 and the second UE being in Uplink, UL, when the other is in Downlink, DL.

[0214] Example A3. The network node 16 of Example Al, wherein the action comprises at least one of: reducing Modulating and Coding Scheme, MCS; reducing a number of Multiple Input Multiple Output, MIMO, layers; adapting a transmission power; and adding repetitions.

[0215] Example A4. The network node 16 of Example Al, wherein the action comprises monitoring a Received Signal Strength Indicator, RSSI.

[0216] Example BL A method implemented in a network node 16, the method comprising: transmitting positioning information corresponding to relative positions of a UE 22 and a second UE to a Local Management Function, LMF; receiving an indication from the LMF that a distance between UE 22 and the second UE is below a threshold, the threshold corresponding to a risk of UE-to-UE Cross Link Interference, CLI between the UE 22 and the second UE; and performing an action based on the indication.

[0217] Example B2. The method of Example Bl, wherein the action comprises scheduling the UE 22 and the second UE to avoid one of the UE and the second UE being in Uplink, UL, when the other is in Downlink, DL.

[0218] Example B3. The method of Example Bl, wherein the action comprises at least one of: reducing Modulating and Coding Scheme, MCS; reducing a number of Multiple Input Multiple Output, MIMO, layers; adapting a transmission power; and adding repetitions.

[0219] Example B4. The method of Example Bl, wherein the action comprises monitoring a Received Signal Strength Indicator, RSSI. Example Cl . A user equipment, UE 22, configured to communicate with a network node, the UE 22 configured to, and / or comprising a radio interface and / or processing circuitry configured to: transmit positioning information corresponding to relative positions of the UE to a Local Management Function, LMF, the positioning information being usable by the LMF to determine that a distance between UE 22 and the second UE is below a threshold; and communicate with the network node 16 based on the determination.

[0220] Example C2. The UE 22 of Example Cl, wherein the communicating with the network node 16 comprises being scheduled to avoid one of the UE 22 and the second UE being in Uplink, UL, when the other is in Downlink, DL.

[0221] Example C3. The UE 22 of Example Cl, wherein the communicating with the network node 16 is based on at least one of a reduced Modulating and Coding Scheme, MCS; a reduced a number of Multiple Input Multiple Output, MIMO, layers; an adapted transmission power; and added repetitions.

[0222] Example DI . A method implemented in a user equipment (UE) 22, the method comprising: transmitting positioning information corresponding to relative positions of the UE 22 to a Local Management Function, LMF, the positioning information being usable by the LMF to determine that a distance between UE 22 and the second UE is below a threshold; and communicating with the network node 16 based on the determination.

[0223] Example D2. The method of Example DI, wherein the communicating with the network node 16 comprises being scheduled to avoid one of the UE 22 and the second UE being in Uplink, UL, when the other is in Downlink, DL.

[0224] Example D3. The method of Example DI, wherein the communicating with the network node 16 is based on at least one of: a reduced Modulating and Coding Scheme, MCS; a reduced a number of Multiple Input Multiple Output, MIMO, layers; an adapted transmission power; and added repetitions.

[0225] Example El A local management function, LMF, configured to communicate with a network node 16 and a user equipment, UE, 22 the LMF comprising processing circuitry configured to: receive positioning information corresponding to relative positions of the UE 22 and a second UE; and transmit to the network node 16 an indication that a distance between UE 22 and the second UE is below a threshold, the threshold corresponding to a risk of UE-to-UE Cross Link Interference, CLI between the UE 22 and the second UE, the indication being configured to cause the network node 16 to perform at least one action. Example E2. The LMF of Example El, wherein the action comprises scheduling the UE 22 and the second UE to avoid one of the UE 22 and the second UE being in Uplink, UL, when the other is in Downlink, DL.

[0226] Example E3. The LMF of Example El, wherein the action comprises at least one of: reducing Modulating and Coding Scheme, MCS; reducing a number of Multiple Input Multiple Output, MIMO, layers; adapting a transmission power; and adding repetitions.

[0227] Example E4. The LMF of Example El, wherein the action comprises monitoring a Received Signal Strength Indicator, RS SI.

[0228] Example Fl A method implemented by a local management function, LMF, configured to communicate with a network node 16 and a user equipment, UE, 22 the method comprising: receiving positioning information corresponding to relative positions of the UE 22 and a second UE; and transmitting to the network node 16 an indication that a distance between UE 22 and the second UE is below a threshold, the threshold corresponding to a risk of UE-to-UE Cross Link Interference, CLI between the UE 22 and the second UE, the indication being configured to cause the network node 16 to perform at least one action.

[0229] Example F2. The method of Example Fl, wherein the action comprises scheduling the UE 22 and the second UE to avoid one of the UE 22 and the second UE being in Uplink, UL, when the other is in Downlink, DL.

[0230] Example F3. The method of Example Fl, wherein the action comprises at least one of: reducing Modulating and Coding Scheme, MCS; reducing a number of Multiple Input Multiple Output, MIMO, layers; adapting a transmission power; and adding repetitions.

[0231] Example F4. The method of Example Fl, wherein the action comprises monitoring a Received Signal Strength Indicator, RSSI.

[0232] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0233] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0234] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0235] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0236] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows. Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0237] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0238] Abbreviations that may be used in the preceding description include:

[0239] Abbreviation Explanation

[0240] Ao A Angle of Arrival

[0241] AoD Angle of Departure

[0242] BS Base Station

[0243] BWP Bandwidth Part

[0244] CLI Cross Link Interference

[0245] DL Downlink

[0246] DTDD Dynamic TDD

[0247] LMF Local Management Function

[0248] MCS Modulation and Coding Scheme

[0249] MIMO Multiple Input Multiple Output

[0250] PRS Positioning Reference Signal

[0251] RSRP Reference Signal Received Power RS SI Received Signal Strength Indicator

[0252] RSTD Received Signal Time Difference

[0253] RTT Round Trip Time

[0254] SBFD Subband Full Duplex

[0255] SFFD Single Frequency Full Duplex

[0256] SL Sidelink

[0257] SRS Sounding Reference Signal

[0258] TDD Time Division Duplex

[0259] TDOA Time Difference of Arrival

[0260] UE User Equipment

[0261] UL Uplink

[0262] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A method implemented in a network node (16) in communication with a first user equipment, UE, (22) the method comprising: determining (S130) that a distance between the first UE (22) and a second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE Cross Link Interference, CLI, between the first UE (22) and the second UE; and performing (SI 32) the action based on the determination.

2. The method of Claim 1, wherein determining whether the distance is below the threshold comprises: transmitting, to a positioning manager (24), one or both of positioning information corresponding to relative positions of the first UE (22) and the second UE, and measurement information; and receiving an indication from the positioning manager indicating that the distance between the first UE (22) and the second UE is below the threshold.

3. The method of any of Claims 1-2, wherein the determining whether the distance is below the threshold is based on receiving, from the first UE (22), one or more of: a downlink positioning reference signal measurement; a sidelink positioning reference signal; a measurement; and an uplink sounding reference signal.

4. The method of any of Claims 1-3, wherein the action comprises scheduling the first UE (22) and the second UE to avoid one of the first UE (22) and the second UE being in Uplink, UL, when the other of the first UE (22) and the second UE is in Downlink, DL.

5. The method of any of Claims 1-4, wherein the action comprises one or more of: reducing a Modulating and Coding Scheme, MCS;reducing a number of Multiple Input Multiple Output, MIMO, layers; adapting a transmission power; and configuring one of the first UE (22) and the second UE with repetitions.

6. The method of any of Claims 1-5, further comprising: requesting a Received Signal Strength Indicator, RS SI, report from each of the first UE (22) and second UE, the determination that the distance is below the threshold being based on the RSSI reports.

7. The method of any of Claims 1-6, wherein: determining that the distance is below the threshold comprises receiving an indication from a second network node associated with the second UE that the distance between the first UE (22) and the second UE is below the threshold; and the action comprising sharing, with the second network node, one or both of scheduling information and future scheduling plans.

8. The method of any of Claims 1-7, wherein determining whether the distance is below the threshold is based on receiving, from a second network node associated with the second UE, information associated with the second UE that comprises one or more of: positioning information and measurements.

9. A network node (16) in communication with a first user equipment, UE, (22) the network node (16) comprising processing circuitry (68) configured to: determine that a distance between the first UE (22) and a second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE- to-UE Cross Link Interference, CLI, between the first UE (22) and the second UE; and perform the action based on the determination.

10. The network node (16) of Claim 9, wherein determining whether the distance is below the threshold comprises: transmitting, to a positioning manager (24), one or both of positioning information corresponding to relative positions of the first UE (22) and the second UE, and; and receiving an indication from the positioning manager indicating that the distance between the first UE (22) and the second UE is below the threshold.

11. The network node (16) of any of Claims 9-10, wherein the determining whether the distance is below the threshold is based on receiving, from the first UE (22), one or more of: a downlink positioning reference signal measurement; a sidelink positioning reference signal; a measurement; and an uplink sounding reference signal.

12. The network node (16) of any of Claims 9-11, wherein the action comprises scheduling the first UE (22) and the second UE to avoid one of the first UE (22) and the second UE being in Uplink, UL, when the other of the first UE (22) and the second UE is in Downlink, DL.

13. The network node (16) of any of Claims 9-12, wherein the action comprises one or more of: reducing a Modulating and Coding Scheme, MCS; reducing a number of Multiple Input Multiple Output, MIMO, layers; adapting a transmission power; and configuring one of the first UE (22) and the second UE with repetitions.

14. The network node (16) of any of Claims 9-13, wherein the processing circuitry (68) is further configured to: request a Received Signal Strength Indicator, RS SI, report from each of the first UE (22) and second UE, the determination that the distance is below the threshold being based on the RS SI reports.

15. The network node (16) of any of Claims 9-14, wherein: determining that the distance is below the threshold comprises receiving an indication from a second network node associated with the second UE that the distance between the first UE and the second UE is below the threshold; and the action comprising sharing, with the second network node, one or both of scheduling information and future scheduling plans.

16. The network node (16) of any of Claims 9-15, wherein determining whether the distance is below the threshold is based on receiving, from a second network node associated with the second UE, information associated with the second UE that comprises one or more of: positioning information and measurements.

17. A method implemented in a user equipment, UE, (22) in communication with a network node (16), the method comprising: causing (S134) transmission, to the network node (16), positioning information corresponding to a position of the UE (22), the positioning information being configured for use by the network node to determine whether a distance between the UE (22) and another UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE Cross Link Interference, CLI, between the UE (22) and the other UE; and communicating (SI 36) with the network node (16) based on the determination.

18. The method of Claim 17, wherein the positioning information comprises one or more of: a downlink positioning reference signal measurement; a sidelink positioning reference signal; a measurement; and an uplink sounding reference signal.

19. The method of any of Claims 17-18, further comprising: causing transmission of a downlink positioning reference signal; receiving and measuring an uplink sounding reference signals transmitted by the other UE; and reporting the corresponding measurement.

20. The method of any of Claims 17-19, wherein, in response to transmitting the positioning information, the UE (22) receives scheduling configured to avoid one of the UE (22) and the other UE being in Uplink, UL, when the other of the UE (22) and the other UE is in Downlink, DL.

21. The method of any of Claims 17-20, wherein, responsive to transmitting the positioning information, the communicating with the network node (16) is based on one or more of: a reduced Modulating and Coding Scheme, MCS; a reduced number of Multiple Input Multiple Output, MIMO, layers; an adapted transmission power; and the UE (22) being configured with repetitions.

22. The method of any of Claims 17-21, further comprising causing transmission of a Received Signal Strength Indicator, RSSI, report configured for use by the network node (16) to determine whether the distance is below the threshold.

23. A user equipment, UE, (22) in communication with a network node, the UE comprising processing circuitry (84) configured to: cause transmission, to the network node (16), of positioning information corresponding to a position of the UE (22), the positioning information being configured for use by the network node (16) to determine whether a distance between the UE (22) and another UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE Cross Link Interference, CLI, between the UE (22) and the other UE; and communicate with the network node (16) based on the determination.

24. The UE (22) of Claim 23, wherein the positioning information comprises one or more of: a downlink positioning reference signal measurement; a sidelink positioning reference signal; a measurement; and an uplink sounding reference signal.

25. The UE (22) of any of Claims 23-24, wherein the processing circuitry (84) is further configured to: cause transmission of a downlink positioning reference signal; receive and measure an uplink sounding reference signals transmitted by the other UE; andreport the measurement of the uplink sounding reference signals.

26. The UE (22) of any of Claims 23-25, wherein, in response to transmitting the positioning information, the UE (22) receives scheduling configured to avoid one of the UE (22) and the other UE being in Uplink, UL, when the other of the UE (22) and the other UE is in Downlink, DL.

27. The UE (22) of any of Claims 23-26, wherein, responsive to transmitting the positioning information, the communicating with the network node (16) is based on one or more of: a reduced Modulating and Coding Scheme, MCS; a reduced number of Multiple Input Multiple Output, MIMO, layers; an adapted transmission power; and the UE (22) being configured with repetitions.

28. The UE (22) of any of Claims 23-27, wherein the processing circuitry (84) is further configured to cause transmission of a Received Signal Strength Indicator, RSSI, report configured for use by the network node (16) to determine whether the distance is below the threshold.

29. A method implemented in a positioning manager (24) configured to communicate with a network node (16) and a first user equipment, UE, (22) the method comprising: receiving (SI 38) positioning information corresponding to relative positions of the first UE (22) and a second UE; determining (S140) based on the positioning information whether a distance between the first UE (22) and the second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE Cross Link Interference, CLI, between the first UE (22) and the second UE, the first UE (22) and the second UE one of belonging to a same network or belonging to different networks; and transmitting (S142), to the network node (16), an indication that the distance is below the threshold.

30. The method of Claim 29, wherein the indication comprises identifying which of the first UE (22) and the second UE is vulnerable to the UE-to-UE CLI, the network node being associated with the identified one of the first UE (22) and the second UE.

31. The method of any of Claims 29-30, further comprising estimating a position of UEs associated to neighboring cells of neighboring networks.

32. A positioning manager (24) configured to communicate with a network node (16) and a first user equipment, UE, (22) the positioning manager (24) comprising processing circuitry configured to: receive positioning information corresponding to relative positions of the first UE (22) and a second UE; and determine, based on the positioning information, whether a distance between the first UE (22) and the second UE is below a threshold, the threshold being associated with whether to trigger an action to mitigate UE-to-UE Cross Link Interference, CLI, between the first UE (22) and the second UE, the first UE (22) and the second UE one of belonging to a same network or belonging to different networks; and cause transmission, to the network node (16), of an indication that the distance is below the threshold.

33. The positioning manager (24) of Claim 32, wherein the indication comprises identifying which of the first UE (22) and the second UE is vulnerable to the UE-to-UE CLI, the network node being associated with the identified one of the first UE (22) and the second UE.

34. The positioning manager (24) of any of Claims 32-33, wherein the processing circuitry is further configured to estimate a position of UEs associated to neighboring cells of neighboring networks.

Images