Timing control for inter-user equipment measurements involved in non-terrestrial networks
By dynamically calculating and reporting the timing information of CLI measurement resources in the NTN system, the problem of rapid change in offset timing between CLI measurement resources and DL channels is solved, effective management of CLI is realized, and the stability and efficiency of the communication system are improved. .
Patent Information
- Application Number
- CN202380030678.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-13
- Filing Date
- 2023-03-16
- Publication Date
- 2024-11-12
AI Technical Summary
In non-terrestrial network (NTN) systems, the offset timing between the cross-link interference (CLI) measurement resource and the downlink (DL) channel or resource changes rapidly, resulting in the offset between the DL transmission and the CLI measurement resource. Timing is difficult to calculate and manage dynamically, affecting the stability and efficiency of the communication system.
By configuring the reception (Rx) timing parameters of CLI measurement resources between the user equipment (UE) and the network node, dynamically calculate and report the timing information of the CLI measurement resources, so that the network node can adjust the transmission time of the DL channel or resource, avoiding CLI Overlapping with DL channels or resources enables effective management of CLI.
It effectively avoids interference from CLI on the DL channel, improves the stability and efficiency of the communication system, and ensures the reliability of the DL channel and the dynamic adaptability of the system.
Smart Images

Figure CN118947071A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. patent application serial number 17 / 659,166, entitled “TIMING CONTROL FOR INTER-USER EQUIPMENT MEASUREMENTS INVOLVED IN NON-TERRESTRIAL NETWORKS” and filed on April 13, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field
[0003] The present disclosure relates generally to communication systems, and more particularly to a non-terrestrial network (NTN) communication system with cross-link interference (CLI) between user equipments (UEs). Background Art
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention
[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.
[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may have a first UE with a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to obtain at least one parameter associated with receive (Rx) timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with a CLI between the first UE and at least one second UE. The at least one processor may be further configured to avoid receiving one or more service downlink (DL) channels or resources from a network node during the Rx timing based on at least one parameter. The one or more service DL channels or resources may overlap with at least one symbol of the one or more CLI measurement resources.
[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may have a first network node with a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to configure at least one parameter associated with receive (Rx) timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with a CLI between at least one first UE configured to communicate with the first network node and at least one second UE configured to communicate with the second network node. The first network node may include a first terrestrial network (TN) and the second network node may include a second non-terrestrial network (NTN). Alternatively, the first network node may include a first NTN and the second network node may include a second TN. Alternatively, the first network node may include a first NTN and the second network node may include a second NTN different from the first NTN.
[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.
[0011] Figure 2A is a diagram illustrating an example of a first frame according to aspects of the present disclosure.
[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to aspects of the present disclosure.
[0013] Figure 2C is a diagram illustrating an example of a second frame according to aspects of the present disclosure.
[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to aspects of the present disclosure.
[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.
[0016] Figure 4 is a diagram illustrating an example of a wireless communication system with user equipment configured to communicate with a TN network node and / or an NTN network node.
[0017] Figure 5 is a network connection flow diagram illustrating an aggressor network node and a victim network node configured to minimize CLI between an aggressor UE and a victim UE.
[0018] Figure 6 is a diagram illustrating an example of CLI resources symbol-aligned with a victim UE.
[0019] Figure 7 is a diagram illustrating an example of CLI resources that are not symbol-aligned with a victim UE.
[0020] Figure 8 is a network connection flow diagram illustrating a victim network node configured to determine CLI timing parameters based on timing information received from an aggressor network node.
[0021] Fig. 9 is a network connection flow diagram illustrating a victim UE configured to provide a CLI timing report to a victim network node based on measured Rx timing of CLI resources.
[0022] Fig.10 is a network connection flow diagram illustrating a victim UE configured to provide a CLI timing report to an aggressor network node based on measured Rx timing of CLI resources.
[0023] Fig.11 is a flow chart of a method of wireless communication.
[0024] Fig.12 is a flow chart of another method of wireless communication.
[0025] Fig.13 is a flow chart of another method of wireless communication.
[0026] Fig.14 is a flow chart of another method of wireless communication.
[0027] Fig.15 is a flow chart of another method of wireless communication.
[0028] Fig.16 is a flow chart of another method of wireless communication.
[0029] Fig.17 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.
[0030] Fig.18 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION
[0031] A downlink (DL) transmission from a first network node to a first user equipment (UE) may fail if a cross-link interference (CLI) measurement resource from a second UE to a second network node overlaps with a DL channel or resource of the DL transmission. Network devices such as user equipment (UE) and network nodes may schedule transmissions using an offset timing between the DL transmission and the CLI measurement resource to minimize or even prevent such overlap. However, the offset timing between the DL transmission and the CLI measurement resource may change rapidly in a non-terrestrial network (NTN) system because the positional relationship between the terrestrial UE and the NTN is unstable.
[0032] Dynamic fast calculation of offset timing between DL transmission and CLI measurement resources can be implemented in the NTN system by configuring the UE to analyze the receive (Rx) timing of the CLI measurement resources and report the relevant calculation to the network node. The first UE can obtain at least one parameter associated with the Rx timing of one or more CLI measurement resources. The one or more CLI measurement resources can be associated with the CLI between the first UE and at least one second UE. The first UE can also avoid receiving one or more service DL channels or resources from the network node during the Rx timing based on at least one parameter. The one or more service DL channels or resources can overlap with at least one symbol of the one or more CLI measurement resources.
[0033] The network node may configure at least one parameter associated with the Rx timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with the CLI between at least one first UE configured to communicate with the first network node and at least one second UE configured to communicate with the second network node. (a) the first network node includes a first TN and the second network node includes a second NTN, (b) the first network node includes a first NTN and the second network node includes a second TN, or (c) the first network node includes a first NTN and the second network node includes a second NTN different from the first NTN. The network node may also output at least one parameter associated with the Rx timing of the one or more CLI measurement resources to the at least one first UE.
[0034] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.
[0035] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0036] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a process, a function or any combination thereof.
[0037] Therefore, in one or more example aspects, specific implementations and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.
[0038] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.
[0039] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NRBS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.
[0040] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0041] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0042] Figure 11 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.
[0043] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive signals on a wired transmission medium or send signals to one or more of the other units. In addition, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units on a wireless transmission medium.
[0044] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 110. CU110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.
[0045] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split (such as a functional split defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.
[0046] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting such as lower layer functional splitting. In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture such as a vRAN architecture.
[0047] The SMO framework 105 may be configured to support RAN deployment and pre-configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 111 via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .
[0048] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.
[0049] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).
[0050] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component may be indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmission diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).
[0051] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
[0052] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.
[0053] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).
[0054] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.
[0055] In view of the above, unless otherwise specifically stated, if the term "below 6 GHz" or the like is used in this document, it can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" or the like is used in this document, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.
[0056] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.
[0057] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access backhaul (IAB) node, a relay node, a sidelink node, a clustered (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or clustered base stations may be referred to as a next generation (NG) RAN (NG-RAN).
[0058] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are shown as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.
[0059] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.
[0060] See again Figure 1 In some aspects, the UE 104 may be configured to obtain at least one parameter associated with the Rx timing of one or more CLI measurement resources, and avoid receiving one or more service DL channels or resources from the network node during the Rx timing based on the at least one parameter using the CLI control component 198. In some aspects, the base station 102 may be configured to configure at least one parameter associated with the Rx timing of one or more CLI measurement resources, and output at least one parameter associated with the Rx timing of one or more CLI measurement resources to the UE using the CLI control component 199. Although the following description may focus on NTN network nodes and systems, the concepts described herein may be applicable to other similar fields, such as systems with conflicting UL and DL symbols. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.
[0061] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.
[0062] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.
[0063]
[0064] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).
[0065] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
[0066] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).
[0067] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also called SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.
[0068] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.
[0069] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.
[0070] Figure 3 370 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0071] The transmit (Tx) processor 316 and receive (Rx) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transmission channel, forward error correction (FEC) decoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The Tx processor 316 handles the mapping of the signal constellation diagram based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Subsequently, each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.
[0072] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (Rx) processor 356. The Tx processor 368 and the Rx processor 356 implement layer 1 functionality associated with various signal processing functions. The Rx processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the Rx processor 356. The Rx processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.
[0073] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.
[0074] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0075] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 may be used by the Tx processor 368 to select appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the Tx processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.
[0076] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to an Rx processor 370.
[0077] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.
[0078] At least one of the Tx processor 368, the Rx processor 356, and the controller / processor 359 may be configured to perform Figure 1 The CLI control component 198 combines various aspects.
[0079] At least one of the Tx processor 316, the Rx processor 370, and the controller / processor 375 may be configured to perform Figure 1 The CLI controls component 199 in conjunction with various aspects.
[0080] Figure 4 4 is a diagram 400 of a wireless communication system having a first NTN network node 402, a second NTN network node 404, a first TN network node 406, a second TN network node 408, a first UE 412, and a second UE 414. The network nodes may include any of a CU, a DU, a RU, or a combination thereof, such as Figure 1 102 in the base station 102. The NTN network node may have a satellite including a network node or a high altitude platform including a network node (i.e., operating as a network device), such as a drone, a balloon, or an airplane. The NTN may be deployed in a frequency band (e.g., FR3) also used for the TN. For example, both the TN network node and the NTN network node may communicate using Ku-band TDD, such as IAB equipment and common phase error (CPE) equipment. In addition, the first NTN network node 402 and the second NTN network node 404 may share the same resources, and / or the first TN network node 406 and the second TN network node 408 may share the same resources. In other words, two or more of the signal 403, the signal 405, the signal 407, the signal 409, the signal 413, or the signal 415 may share the same resources, such as the same frequency band or sub-band.
[0081] The first UE 412 and the second UE 414 may share the logical cell 420, so that the Tx signal from the second UE 414 may interfere with the Rx signal received by the first UE 412. For example, in the case where the first UE 412 is configured to communicate with the first TN network node 406 and the second UE 414 is configured to communicate with the second NTN network node 404, the Tx signal 415 from the second UE 414 may interfere with the Rx signal 407 to the first UE 412. For another example, in the case where the first UE 412 is configured to communicate with the first NTN network node 402 and the second UE 414 is configured to communicate with the second TN network node 408, the Tx signal 415 from the second UE 414 may interfere with the Rx signal 403 to the first UE 412. For another example, in the case where the first UE 412 is configured to communicate with the first NTN network node 402 and the second UE 414 is configured to communicate with the second NTN network node 404, the Tx signal 415 from the second UE 414 may interfere with the Rx signal 403 to the first UE 412. For another example, in the case where the first UE 412 is configured to communicate with the first TN network node 406 and the second UE 414 is configured to communicate with the second TN network node 408, the Tx signal 415 from the second UE 414 may interfere with the Rx signal 407 to the first UE 412. In other words, CLI may occur between two devices connected to two systems, such as a device connected to the TN and a device connected to the NTN, two devices connected to different NTNs, or two devices connected to different TNs.
[0082] The CLI measurement timing between the first UE 412 configured to communicate with the first TN network node 406 and the second UE 414 configured to communicate with the second TN network node 408 may be handled using a constant measurement timing relative to the UE's serving cell DL timing, because the positional relationship between the first UE 412 and the first TN network node 406 and the positional relationship between the second UE 414 and the second TN network node 408 may be relatively stable. In other words, due to the stable positional relationship of the aggressor UE and the victim UE, a constant offset may be a valid assumption for CLI measurement in the TN. However, in the case where one of the UEs is configured to communicate with an NTN network node, or in the case where both UEs are configured to communicate with two different NTN network nodes, a constant offset may not be a valid assumption. Since NTN network devices move quickly on satellites, drones, or aircraft, the relative timing offset between the two devices may change dynamically over time at a fast pace that is difficult to adapt to. In other words, for CLI measurements involved in NTN, if the aggressor UE and victim UE are connected to different network devices in TN and NTN or to different NTNs, the constant offset assumption may not be valid.
[0083] In addition, different network nodes (such as a TN network node and an NTN network node or two different NTN network nodes) may have different conflicting UL and DL symbols. In one aspect, different semi-static TDD UL and DL time slot formats may be configured to address different UL and DL throughput requirements. On the other hand, dynamic TDD may be enabled on one or both network nodes to improve a better balance of UL and DL throughput. On the other hand, the round-trip time (RTT) conversion rate may be different between one network node and another network node due to different mobility (e.g., an NTN network node may move faster relative to a TN network node, or one NTN network node may move faster relative to another NTN network node), which may result in timing asynchrony between the two network nodes.
[0084] As mentioned above, due to the stable position relationship of the aggressor UE and the victim UE, a constant offset may be a valid assumption for CLI measurement in a TN. Figure 55 is a network connection flow diagram 500 illustrating an aggressor UE 502, an aggressor network node 504, a victim network node 506, and a victim UE 508. The aggressor network node 504 and the victim network node 506 may be TN network nodes having a stable positional relationship with respect to the aggressor UE 502 and the victim UE 508, respectively. At 512, the aggressor network node 504 may schedule UL Tx 526 for the aggressor UE 502, such as UL transmissions (e.g., PUSCH, PUCCH) from the aggressor UE 502 to the aggressor network node 504. The aggressor network node 504 may output a UL Tx schedule 522, such as a DCI scheduling the UL Tx 526, to the aggressor UE 502. The aggressor network node 504 may also output a CLI resource configuration 523 to the victim network node 506 to indicate the UL Tx 526 used by the aggressor UE 502 .
[0085] At 514, the victim network node 506 may configure the victim UE 508 with CLI measurement resources (e.g., time and frequency locations and sequences) that may correspond to the UL Tx 526. The measurement resources may correspond to the UL Tx 526 of the aggressor UE 502 to its serving base station (such as the aggressor network node 504). The victim network node 506 may output the CLI resource configuration 524 to the victim UE 508 to inform the victim UE 508 of the UL Tx 526 that may serve as the RS CLI to the victim UE 508. At 516, the victim UE 508 may measure the CLI measurement resources corresponding to the UL Tx 526, for example, in terms of SRS, reference signal received power (RSRP), or received signal strength indicator (RSSI) with respect to the UL Tx 526. In one aspect, when the victim UE 508 measures SRS-RSRP and / or CLI-RSSI, the network may be configured to apply a constant offset relative to the downlink reference timing of the serving cell. The victim UE 508 may send a measurement report 528 to the victim network node 506 as a result. The victim network node 506 may forward at least a portion of the measurement report 528 to the aggressor network node 504 as a measurement report 529.
[0086] At 518, the aggressor network node 504 may schedule UL Tx 532 from the aggressor UE 502, and at 519, the victim network node 506 may schedule DL Rx 533 to the victim UE 508 according to the measurement report result. The network may consider the CLI measurement report when scheduling the aggressor UE 502 and the victim UE 508. Depending on the importance of the specification of the victim or aggressor UE, the network may avoid UL transmission from the aggressor UE 502 and allocate resources for DL reception of the victim UE 508, or may avoid DL scheduling for the victim UE 508 and may allocate resources for UL transmission of the aggressor UE 502, or may allocate resources to both the aggressor UE 502 and the victim UE 508 and allow the CLI to exist in the CLI at or below the threshold. For example, in response to the network determining that DL Rx 533 has a higher priority than UL Tx 532, the victim network node 506 may output an Rx schedule 531 for DL Rx 533 having an earlier time period and / or a more reliable frequency, and the aggressor network node 504 may output a Tx schedule 530 for UL Tx 532 having a later time period and / or a less reliable frequency. On the other hand, in response to the network determining that UL Tx 532 has a higher priority than DL Rx 533, the aggressor network node 504 may output a Tx schedule 530 for UL Tx 532 having an earlier time period and / or a more reliable frequency, and the victim network node 506 may output an Rx schedule 531 for DL Rx 533 having a later time period and / or a less reliable frequency. On the other hand, in response to the network determining that the CLI impact of UL Tx 526 is equal to or below a threshold, the aggressor network node 504 may output a Tx schedule 530 for UL Tx 532 having resources overlapping with DL Rx 533, and the victim network node 506 may output an Rx schedule 531 for DL Rx 533 having resources overlapping with UL Tx 532.
[0087] The CLI resources may or may not be aligned with the symbols or time slots of the serving cell DL of the victim UE. Figure 66 is a diagram 600 illustrating an example of UL Tx / CLI 632 of an aggressor UE 630 aligned with symbol 610 of a victim UE 620 having a set of scheduled resources. The victim UE 620 is scheduled to receive data from symbols 0 to 9, idle during symbol 10, and upload data from symbols 11 to 13. However, the UL Tx / CLI 632 from the aggressor UE 630 is scheduled between symbols 2 to 6. In response to the UL Tx / CLI 632 of the aggressor UE 630 interfering with symbols 622 in symbols 2 to 6 from the victim UE 620, the network configuring the UL Tx / CLI 632 may be configured to not schedule any DL channels or resources (e.g., PDSCH, PDCCH, CSI-RS) during symbols 2 to 6 for the victim UE 620. In other words, the network may be configured to prioritize CLI over serving cell DL. Similarly, in response to UL Tx / CLI 632 of aggressor UE 630 interfering with symbol 622 of symbols 2 to 6 from victim UE 620 , victim UE 620 may be configured to not receive DL channels or resources during symbols 2 to 6 for victim UE 620 .
[0088] The timing offset between the CLI of the aggressor UE and the serving cell DL of the victim UE may be constant. For example, the CLI from the aggressor UE 630 may be constantly offset by two symbols from the symbols of the victim UE 620, so that any CLI measurement resource corresponding to an UL transmission from the aggressor UE 630 scheduled during one time slot may have a constant timing offset of two symbols. However, the difference between the CLI timing and the UE serving cell DL timing may not be constant, especially in systems with one or more NTN network nodes, such as Figure 4 A system with a first NTN network node 402 and a second NTN network node 404 is shown in diagram 400 of FIG. 4. The difference between the timing offset at a CLI and the next CLI may be larger than several time slots.
[0089] Furthermore, the CLI resources may not be aligned with the symbols or time slots of the serving cell DL of the victim UE. Figure 7 7 is a diagram 700 illustrating an example of a UL Tx / CLI 732 of an aggressor UE 730 that is not aligned with a symbol 710 of a victim UE 720 having a set of scheduled resources. Figure 6 The victim UE 620 in Figure 7The victim UE 720 in FIG. 7 is scheduled to receive data from symbols 0 to 9, idle during symbol 10, and upload data from symbols 11 to 13. However, a UL Tx / CLI 732 corresponding to the UL transmission from the aggressor UE 730 is scheduled between a portion of symbol 2 to a portion of symbol 7 in the symbol 710 of the victim UE 720. Although the UL Tx / CLI 732 may be five symbols long, the UL Tx / CLI 732 may interfere with the six symbols 722 from symbol 2 to symbol 7 of the victim UE 720 because the start of the UL Tx / CLI 732 may overlap with the symbol 2 portion of the symbol 710 of the victim UE 720 and the end of the UL Tx / CLI 732 may overlap with the symbol 7 portion of the symbol 710 of the victim UE 720. In response to the UL Tx / CLI 732 of the aggressor UE 730 interfering with any symbol 722 from symbols 2 to 7 from the victim UE 720, the network configuring the UL Tx / CLI 732 may be configured to not schedule any DL channels or resources (e.g., PDSCH, PDCCH, CSI-RS) during symbols 2 to 7 for the victim UE 720. In other words, the network may be configured to prioritize CLI over serving cell DL. Similarly, in response to the UL Tx / CLI 732 corresponding to the UL transmission of the aggressor UE 730 interfering with the symbol 722 from symbols 2 to 7 from the victim UE 720, the victim UE 720 may be configured to not receive DL channels or resources during symbols 2 to 7 for the victim UE 720.
[0090] The network node, the UE, or both may be configured to calculate and send timing parameters to each other to improve the ability to calculate dynamically changing timing offsets of CLI measurement resources. Figure 8 A network connection flow diagram 800 illustrating a victim network node 806 configured to determine a CLI timing parameter based on timing information received from an aggressor network node 804 is shown. The network connection flow diagram 800 has an aggressor UE 802, an aggressor network node 804, a victim network node 806, and a victim UE 808. The aggressor UE 802 and the victim UE 808 may share the same logical cell, such as Figure 44, wherein the aggressor network node 804 and the victim network node 806 may be connected to a logical cell 420 in the aggressor network node 804 such that a transmitted signal from the aggressor UE 802 may interfere with a received signal to the victim UE 808. At least one of the aggressor network node 804 and the victim network node 806 may have an NTN TRP or transceiver such that a measurement timing of a CLI measurement resource from the aggressor UE 802 is dynamic relative to a serving cell DL timing of the victim UE 808. The aggressor network node 804 and the victim network node 806 may be functionally connected to each other via a fronthaul link, a midhaul link, or a backhaul link to allow data transmission of parameters.
[0091] In order to determine the timing of the CLI measurement resources corresponding to the UL transmission from the aggressor UE 802 relative to the serving cell DL timing of the victim UE 808, the aggressor UE 802 may be configured to report its location to the network. Based on the report, the network may derive the timing offset between the CLI measurement resources and the serving cell DL timing of the UE. At 812, the aggressor UE 802 may be configured to determine its location, for example, via GNSS updates, and send the UE location 822 to the aggressor network node 804. At 814, the aggressor network node 804 may determine the timing information using the obtained location of the aggressor UE 802, and may output the timing information 824 to the victim network node 806.
[0092] In some aspects, at 813, the victim UE 808 may be configured to determine its location, e.g., via GNSS updates, and may be configured to send its UE location 823 to the victim network node 806. At 815, the victim network node 806 may use the UE location 823 of the victim UE 808 to determine timing information to estimate the location of the aggressor UE 802, rather than having the timing information derived by the aggressor network node 804.
[0093] The timing information may include any information suitable for the victim network node 806 to determine the serving cell DL timing of the victim UE 808 relative to the serving cell DL timing of the aggressor UE 802. For example, the timing information may include the system timing of the aggressor network node 804 or the difference between the system timing of the victim network node 806 and the system timing of the aggressor network node 804. The timing information may include a timing delay between the aggressor UE 802 and the aggressor network node 804. The timing information may include an estimated distance between the aggressor UE 802 and the transceiver or TRP of the aggressor network node 804. The timing information 824 may include the location of the aggressor network node 804 or information (e.g., ephemeris information) that may be used to determine the location of the aggressor network node 804.
[0094] At 816, the victim network node 806 may be configured to determine one or more timing parameters based on the timing information 824. For example, the timing parameters may include a system timing difference between the victim network node 806 and the aggressor network node 804. The timing parameters may include a timing delay between the aggressor UE 802 and a base station of the aggressor UE. In one aspect, the victim network node 806 may be configured to use the location of the aggressor network node 804 to determine a timing delay between the aggressor UE 802 and the aggressor network node 804 by estimating that the location of the aggressor UE 802 is the same as the location of the victim UE 808. The timing parameters may include a timing delay between the victim UE 808 and the victim network node 806. Such a timing delay may be determined based on the location of the victim UE 808 or an estimated distance between the victim UE 808 and a transceiver or TRP of the victim network node 806. While the timing parameters may also include propagation delays between the victim UE 808 and the aggressor UE 802, such distances may be ignored in some aspects. The timing parameters may also include an initial offset (e.g., an offset between CLI measurement resources corresponding to UL transmissions of the aggressor UE 802 and the victim UE 808 at a previous time), a slew rate for linearly modeling changes over time, a formula configured to model high-order changes in the initial timing offset, or a set of variables of a formula configured to model high-order changes in the initial timing offset. Such variables may be used by any entity having such a formula to calculate the current timing offset between the serving cell DL timing of the victim UE 808 and the serving cell UL timing of the aggressor UE 802. Since these timing parameters may not share the same dynamic characteristics, the timing offset between the CLI measurement resources corresponding to the UL transmissions of the aggressor UE 802 and the serving cell DL timing of the victim UE 808 may change over time.
[0095] Such parameters may be used to determine a varying timing offset between CLI measurement resources corresponding to the UL transmission of the aggressor UE 802 and the serving cell DL timing of the victim UE 808. The victim network node 806 may be configured to output one or more of the timing parameters as timing parameters 826 to the aggressor network node 804 and / or output one or more of the timing parameters as timing parameters 827 to the victim UE 808. Based on the derived timing offset, the victim network node 806, the aggressor network node 804, or the victim UE 808 may reduce the CLI. For example, at 819, the victim network node 806 may skip scheduling a serving DL (e.g., PDCCH, PDSCH, CSI-RS) that overlaps with symbols of the UL Tx 828. In other words, the victim network node 806 may schedule the DL Rx 829 to not use the same channel or resource (i.e., CLI measurement resource) as the UL Tx 828 of the aggressor UE 802. On the other hand, at 820, the victim UE 808 may skip receiving service DL (e.g., PDCCH, PDSCH, CSI-RS, SPS PDSCH, periodic CSI-RS, SPS SCI-RS) that overlaps with the UL Tx 828 corresponding to the UL transmission of the aggressor UE 802 (i.e., the CLI measurement resources of the aggressor UE 802). In other words, the victim UE 808 may avoid receiving any portion of the DL Rx 829 that uses the same channel or resource that overlaps with the UL Tx 828 corresponding to the UL transmission of the aggressor UE 802. On the other hand, at 818, the aggressor network node 804 may be configured to skip scheduling UL transmissions for the aggressor UE 802 that use the same channel or resource that overlaps with the DL Rx 829 of the victim UE 808.
[0096] In another aspect, the network may be configured to request the victim UE to measure a timing offset of the CLI measurement resource. Fig. 9 9 is a network connection flow diagram 900 illustrating a victim UE 906 configured to provide a CLI timing report to a victim network node 908 based on a measured Rx timing of a CLI measurement resource corresponding to a UL Tx 924 of an aggressor UE. The network connection flow diagram 900 has an aggressor UE 902, an aggressor network node 904, a victim UE 906, and a victim network node 908. The aggressor UE 902 and the victim UE 906 may share the same logical cell, such as Figure 44. The aggressor network node 904 and the victim network node 908 may be connected to the logical cell 420 in the aggressor network node 904, so that the transmission signal from the aggressor UE 902 may interfere with the reception signal to the victim UE 906. At least one of the aggressor network node 904 and the victim network node 908 may have an NTN TRP or transceiver, so that the measurement timing of the CLI measurement resource from the aggressor UE 902 is dynamic relative to the serving cell DL timing of the victim UE 906. The aggressor network node 904 and the victim network node 908 may not be functionally connected to each other via a fronthaul link, a midhaul link, or a backhaul link, which may prevent the aggressor network node 904 and the victim network node 908 from providing timing parameters, such as Figure 8 Timing parameters 826 in.
[0097] The aggressor network node 904 may be configured to schedule the transmission of UL channels or reference signals from the aggressor UE 902 to the aggressor network node 904 that may interfere with the Rx transmission of the victim UE 906. The aggressor network node may output a UL Tx schedule 923 (e.g., DCI) that schedules UL Tx 924 to the aggressor UE 902, and may output a UL Tx schedule 928 that schedules UL Tx 929. In response to determining that one or more Rx transmissions to the victim UE 906 were not successfully received (e.g., the victim network node 908 obtained a NACK from the victim UE 906), the victim network node 908 may be configured to send a CLI resource configuration 922 to the victim UE 906. Such a configuration may be, for example, a DCI that triggers a periodic or aperiodic CLI measurement resource. The periodic CLI measurement resource may occur at layer 3, while the aperiodic CLI measurement resource may occur at layer 1. The DCI triggering the aperiodic CLI measurement may indicate the starting symbol at which the victim UE 906 should measure UL Tx 924, for example, by providing an offset or by referencing an RRC with an offset list. Figure 6 The UL Tx / CLI 632 in the DCI may have an offset of two symbols to indicate that the UL Tx / CLI 632 starts at symbol 2 of the symbol 610 instead of symbol 0. Such DCI may also provide a sub-symbol timing offset, or the sub-symbol timing offset may be provided in a separate signal such as a MAC control element (MAC-CE). For example, Figure 7UL Tx / CLI 732 in the DCI may have an offset of 8 microseconds to indicate that UL Tx / CLI 732 starts 8 microseconds in symbol 2 of symbol 710. In some aspects, sub-symbol timing is not provided in the DCI or a separate signal, and the victim UE 906 may be configured to derive the sub-symbol timing at 912 by searching for the symbol offset provided by the DCI. In other aspects, sub-symbol timing is not provided in the DCI or a separate signal, and the victim UE 906 may be configured to use the symbol timing of the DCI as a rough estimate of the timing of the CLI measurement resources corresponding to the UL Tx 924 of the aggressor UE. The DCI may also provide SRS resources to the victim UE 906 to provide a CLI measurement report 926 (i.e., a CLI timing report). In another aspect, the configuration may be an RRC that provides periodic SRS resources to the UE to provide a CLI measurement report 926. The victim network node 908 may also be configured to output RS Rx 925 to the victim UE 906, which the victim UE 906 may use as a reference for the UL Tx 924 from the aggressor UE 902. The CLI resource configuration 922 may also include a timing reference, such as a previous timing offset.
[0098] At 912, the victim UE 906 may measure the Rx timing of the CLI measurement resource corresponding to the UL Tx 924. The victim UE 906 may be configured to measure the timing of the CLI measurement resource corresponding to the UL Tx 924 (e.g., when the CLI starts and stops) and compare it with the symbol slot timing of the reference signal (such as RS Rx 925 obtained from the victim network node 908). The victim UE 906 may also be configured to measure the interference level of the RS Rx 925 as a threshold metric. On the other hand, the victim UE 906 may be configured to calculate the timing of the CLI measurement resource corresponding to the UL Tx 924 by estimating the position of the aggressor UE 902 to be the same as the position of the victim UE 906 and determining the TRP or the position of the transceiver of the aggressor network node 904 by using the ephemeris information of the aggressor network node 904. In other words, the victim UE 906 may calculate the channel delay from the aggressor UE 902 to the aggressor network node 904 by estimating the location of the aggressor UE 902 and the TRP or the location of the transceiver of the aggressor network node 908, and calculate the timing of the CLI measurement resource corresponding to the UL Tx 924 by calculating the channel delay from the victim UE 906 to the victim network node 904 and the corresponding timing reference. The corresponding timing reference may include the timing reference of the aggressor network node 904 serving the aggressor UE 902, which may be different from the timing reference of the victim network node 908 serving the victim UE 906. The victim network node 908 may consider the difference between the corresponding timing references to determine the Rx timing of the DL Rx 930 compared to the UL Tx 929 (i.e., the CLI measurement resource).
[0099] The victim UE 906 may send a CLI measurement report 926 to the victim network node 908, the report including at least a portion of the measurement results, such as a timing offset between the serving cell DL timing of the victim UE 906 and the CLI measurement resource corresponding to the UL Tx 924 timing. The timing report may include an initial offset, a conversion rate for linearly modeling changes over time, a formula configured to model high-order changes in the initial timing offset, or a variable set of a formula configured to model high-order changes in the initial timing offset. The report may be included in UE assistance information (UAI) of the victim UE 906. The victim network node 908 may configure a formula configured to model high-order changes in the initial timing offset, and the victim UE 906 may be configured to provide coefficient values of the formula to the victim network node 908.
[0100] Based on the timing report, the victim UE 906 or the victim network node 908 may reduce the CLI. For example, at 914, the victim UE 906 may skip receiving the service DL that overlaps with the CLI measurement resource of the UL Tx 929 corresponding to the aggressor UE 902. In other words, the victim UE 906 may avoid receiving any portion of the DL Rx 930 that uses the same channel or resource that overlaps with the CLI measurement resource of the UL Tx 929 corresponding to the aggressor UE 902. On the other hand, at 915, the victim network node 908 may skip scheduling the service DL that overlaps with the symbol of the CLI measurement resource corresponding to the UL Tx 929. In other words, the victim network node 908 may schedule the DL Rx 930 not to use the same channel or resource as the CLI measurement resource of the UL Tx 929 corresponding to the aggressor UE 902. The victim network node 908 may identify symbols where CLI measurement resources corresponding to UL Tx 929 may overlap with possible DL Rx 930 and avoid scheduling DL channels or resources for the victim UE 906 .
[0101] The victim network node 908 may be configured to acknowledge receipt of the CLI measurement report 926 by providing an updated CLI resource configuration 927 to the victim UE 906. The updated CLI resource configuration 927 may include scheduling of DL Rx 930 that does not overlap with resources of the CLI measurement resources corresponding to the UL Tx 929 and / or may include RSSI measurement resources for use by the victim UE 906 with the CLI measurement resources corresponding to the UL Tx 929.
[0102] In some aspects, the aggressor network node and the victim network node may not be configured to communicate with each other using a fronthaul connection, a midhaul connection, or a backhaul connection. Fig.10 A network connection flow diagram 1000 illustrating a victim UE 1006 configured to provide a CLI measurement report 1027 (e.g., a CLI timing report) to an aggressor network node 1004 based on a measured Rx timing of a UL Tx 1024 is shown. The network connection flow diagram 1000 has an aggressor UE 1002, an aggressor network node 1004, a victim UE 1006, and a victim network node 1008, similar to Fig. 9 902, aggressor network node 904, victim UE 906 and victim network node 908 in the embodiment.
[0103] Similar to Fig. 9900, the aggressor network node 1004 may be configured to schedule the transmission of CLI measurement resources from the aggressor UE 1002 to the aggressor network node 1004 that may interfere with the Rx transmission of the victim UE 1006. The aggressor network node may output a UL Tx schedule 1023 that schedules UL Tx 1024 to the aggressor UE 1002, and may output a UL Tx schedule 1028 that schedules UL Tx 1030. Similarly, the victim network node 1008 may be configured to send a CLI resource configuration 1022 to the victim UE 1006. The victim network node 1008 may also be configured to output a RS Rx 1025 to the victim UE 1006, which the victim UE 1006 may use as a reference for the UL Tx 1024 from the aggressor UE 1002.
[0104] At 1012, the victim UE 1006 may similarly measure the Rx timing of the UL Tx 1024 and may send a CLI measurement report 1026 including at least a portion of the measurement results to the victim network node 1008. Fig. 9 Unlike the victim UE 906 in the embodiment, at 1014, the victim UE 1006 may be configured to switch its network node to communicate with the aggressor network node 1004. In other words, the victim UE 1006 may be configured to support communication with both the aggressor network node 1004 and the victim network node 1008. In the case where one network node is a TN and the other network node is an NTN, the victim UE 1006 may be configured to support both NTN and TN. In the case where one network node is an NTN and the other network node is a different NTN, the victim UE 1006 may be configured to support more than one NTN. The victim UE 1006 may be configured to report inter-UE measurement results when it switches to communicate with the aggressor network node 1004.
[0105] For example, in the case where the victim network node 1008 is NTN and the aggressor network node 1004 is TN, the victim UE 1006 may operate in NTN mode, measure interference from the aggressor UE 1002 at 1012, switch to TN mode to communicate with the aggressor network node 1004, and send a CLI measurement report 1027 to the aggressor network node 1004. This configuration may report interference measurement results from the NTN network system to the TN serving base station. On the other hand, in the case where the victim network node 1008 is TN and the aggressor network node 1004 is NTN, the victim UE 1006 may operate in TN mode, measure interference from the aggressor UE 1002 at 1012, switch to NTN mode to communicate with the aggressor network node 1004, and send a CLI measurement report 1027 to the aggressor network node 1004. This configuration may report interference measurement results from the TN network system to the NTN serving base station. On the other hand, in the case where the victim network node 1008 is configured to communicate using the NTN 1 network and the aggressor network node 1004 is configured to communicate using the NTN 2 network different from NTN 1, the victim UE 1006 may operate in the NTN 1 mode, measure interference from the aggressor UE 1002 at 1012, switch to the NTN 2 mode to communicate with the aggressor network node 1004, and send a CLI measurement report 1027 to the aggressor network node 1004. Such a configuration may report interference measurement results from the NTN 1 network system to the NTN 2 serving base station. At 1017, the victim UE 1006 may be configured to switch the network node back to the victim network node 1008.
[0106] Based on the timing report, the aggressor network node 1004 may reduce the CLI. For example, at 1016, the aggressor network node 1004 may be configured to skip scheduling UL transmissions for the aggressor UE 1002 that use the same channel or resource that overlaps with the DL Rx 1031 of the victim UE 1006. The aggressor network node 1004 may then output a UL Tx schedule 1028 (e.g., a modified CLI schedule) for the UL Tx 1030 that does not use the same channel or resource that overlaps with the DL Rx 1031 of the victim UE 1006, and the victim network node 1008 may output a DL Rx schedule 1029 to the victim UE 1006 to schedule the reception of the DL Rx 1031 that may not have been successfully received by the victim UE 1006 if it were not for the UL Tx schedule 1028.
[0107] Fig.111100 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 412, UE 414, UE 808, UE 906, UE 1006; device 1704). At 1102, a first UE may obtain at least one parameter associated with Rx timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with CLI between the first UE and at least one second UE. For example, 1102 may be performed by Figure 8 The victim UE 808 in the embodiment may obtain the timing parameter 827 associated with the Rx timing of the UL Tx 828. The UL Tx 828 is associated with the CLI between the victim UE 808 and the aggressor UE 802. In addition, 1102 may be performed by Fig.17 Component 198 in is executed.
[0108] At 1104, the first UE may avoid receiving one or more serving DL channels or resources from the first network node during the Rx timing based on at least one parameter. The one or more serving DL channels or resources may overlap with at least one symbol of the one or more CLI measurement resources. For example, 1104 may be performed by Figure 8 The victim UE 808 in the embodiment of the present invention performs the UE avoiding receiving DL Rx 829 from the victim network node 806 during the Rx timing of UL Tx 828 (ie, CLI measurement resource) based on the timing parameter 827. The DL Rx 829 may overlap with at least one symbol of UL Tx 828, such as Figure 6 Symbols 2 to 6 of symbols 610 in , where the victim UE 620 is at symbol 622 and the aggressor UE is at UL Tx / CLI 632. In addition, 1104 may be composed of Fig.17 Component 198 in is executed.
[0109] Fig.12 1200 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 412, UE 414, UE 808, UE 906, UE 1006; device 1704). At 1202, a first UE may send a UE position associated with Rx timing to a first network node. For example, Figure 8 The victim UE 808 in the embodiment may be configured to send a UE location of an estimated location of the aggressor UE 802 that sends UL Tx 828 to the victim network node 806. In addition, 1202 may be configured to send a UE location of an aggressor UE 802 that estimates the location of the aggressor UE 802 that sends UL Tx 828 to the victim network node 806. Fig.17 Component 198 in is executed.
[0110] At 1204, the first UE may obtain at least one parameter associated with Rx timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with CLI between the first UE and at least one second UE. For example, 1204 may be performed by Figure 8 828 is associated with the CLI between the victim UE 808 and the aggressor UE 802. In addition, 1204 may be performed by the victim UE 808 in the embodiment of the present invention, and the victim UE may obtain the timing parameter 827 associated with the Rx timing of the UL Tx 828. The UL Tx 828 is associated with the CLI between the victim UE 808 and the aggressor UE 802. Fig.17 Component 198 in is executed.
[0111] At 1206, the first UE may avoid receiving one or more serving DL channels or resources from the first network node during the Rx timing based on at least one parameter. The one or more serving DL channels or resources may overlap with at least one symbol of the one or more CLI measurement resources. For example, 1206 may be performed by Figure 8 The victim UE 808 in the embodiment of the present invention performs the UE to avoid receiving DL Rx 829 from the victim network node 806 during the Rx timing of UL Tx 828 based on the timing parameter 827. The DL Rx 829 may overlap with at least one symbol of UL Tx 828, such as Figure 6 6, wherein the victim UE 620 is at symbol 622 and the aggressor UE is at UL Tx / CLI 632. In addition, 1206 may be composed of Fig.17 Component 198 in is executed.
[0112] At 1208, the first UE may obtain at least one parameter associated with Rx timing by receiving at least one parameter associated with Rx timing from the first network node. Figure 8 The victim UE 808 in the embodiment may obtain the timing parameter 827 associated with UL Tx 828 from the victim network node 806. In addition, 1208 may be Fig.17 Component 198 in is executed.
[0113] At 1210, the first UE may send inter-UE measurement results to a second network node communicating with at least one second UE based on at least one parameter associated with Rx timing of one or more CLI measurement resources. In addition, (a) the first network node includes a first TN and the second network node includes a second NTN, (b) the first network node includes the first NTN and the second network node includes the second TN, or (c) the first network node includes the first NTN and the second network node includes a second NTN different from the first NTN. For example, Fig.10The victim UE 1006 in the embodiment may be configured to send a CLI measurement report 1027 to the aggressor network node 1004 based on the parameters associated with the Rx timing of the UL Tx 1024 measured at 1012. In addition, the victim network node 1008 may include a TN, such as Figure 4 The first TN network node 406 in the embodiment, and the aggressor network node 1004 may include an NTN, such as Figure 4 The second NTN network node 404 in the embodiment. Alternatively, the victim network node 1008 may include an NTN, such as Figure 4 The first NTN network node 402 in the embodiment, and the aggressor network node 1004 may include a TN, such as Figure 4 Alternatively, the victim network node 1008 may include a first NTN, such as Figure 4 The first NTN network node 402 in the embodiment, and the aggressor network node 1004 may include a second NTN, such as Figure 4 The second NTN network node 404 in. In addition, 1210 can be Fig.17 Component 198 in is executed.
[0114] At 1212, the first UE may measure one or more CLI measurement resources during the Rx timing of the one or more CLI measurement resources. For example, Fig.10 The victim UE 1006 in the UL Tx 1024 may measure the Rx timing at 1012 during the Rx timing of the UL Tx 1024. In addition, 1212 may be determined by Fig.17 Component 198 in is executed.
[0115] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 412, UE 414, UE 808, UE 906, UE 1006; device 1704). At 1302, a first UE may receive SRS resources from a second UE as CLI measurement resources. For example, Fig. 9 The victim UE 906 in the embodiment may be configured to receive UL Tx 924 from the aggressor UE 902 as an SRS resource. The victim UE 906 may treat UL Tx 924 as a CLI measurement resource and may send a measurement of the Rx timing of the SRS resource in a CLI measurement report 926. Fig.17 Component 198 in is executed.
[0116] At 1304, the first UE may measure the Rx timing of one or more CLI measurement resources. For example, 1304 may be performed by Fig. 9The victim UE 906 in the embodiment may measure the Rx timing of the UL Tx 924 at 912. In addition, 1304 may be performed by Fig.17 Component 198 in is executed.
[0117] At 1306, the first UE may send an indication of Rx timing to the first network node. For example, 1306 may be performed by Fig. 9 The victim UE 906 in the embodiment may send a CLI measurement report 926 for the Rx timing of the UL Tx 924 to the victim network node 908. In addition, 1306 may be performed by Fig.17 Component 198 in is executed.
[0118] At 1308, the first UE may send an indication of the Rx timing by sending a UAI including an indication of the Rx timing. For example, 1308 may be performed by Fig. 9 The victim UE 906 in the embodiment may send a CLI measurement report 926 by sending a UAI including the measurement result of Rx timing at 912. In addition, 1308 may be performed by Fig.17 Component 198 in is executed.
[0119] At 1310, the first UE may measure the Rx timing of one or more CLI measurement resources by calculating the Rx timing based on the channel delay of the first UE, the channel delay of at least one second UE, and the corresponding timing reference. For example, 1310 may be performed by Fig. 9 The victim UE 906 in the embodiment may measure the Rx timing of the UL Tx 924 by calculating the Rx timing based on the channel delay of the victim UE 906, the channel delay of the aggressor UE 902, and the corresponding timing reference from the CLI resource configuration 922. In addition, 1310 may be performed by Fig.17 Component 198 in is executed.
[0120] At 1312, the first UE may send an indication of the Rx timing to the first network node by sending a measurement of the Rx timing using the SRS resource. Fig. 9 The victim UE 906 in the embodiment may use the SRS resource provided by the CLI resource configuration 922 to send a CLI measurement report 926 to the victim network node 908. In addition, 1312 may be performed by Fig.17 Component 198 in is executed.
[0121] At 1314, the first UE may measure the Rx timing of one or more CLI measurement resources using a trigger offset, the trigger offset indicating a starting symbol for measuring the CLI. Fig. 9The victim UE 906 in the embodiment may measure the Rx timing of the UL Tx 924 at 912 using the trigger offset indicated in the CLI resource configuration 922, the trigger offset indicating the starting symbol of the CLI to be measured, such as Figure 6 The offset of two symbols for UL Tx / CLI 632 in 1314 can be Fig.17 Component 198 in is executed.
[0122] At 1316, the first UE may receive a DCI from the first network node that triggers the Rx timing to be measured as an aperiodic CLI measurement. For example, 1316 may be performed by Fig. 9 The victim UE 906 in the embodiment may receive a DCI as part of a CLI resource configuration 922 from a victim network node 908, which triggers a ULTx 924 to be measured as an aperiodic CLI measurement. In addition, 1316 may be performed by Fig.17 Component 198 in is executed.
[0123] At 1318, the first UE may receive a sub-symbol timing offset from the first network node. The Rx timing of one or more CLI measurement resources is measured using a sub-symbol timing offset indicating an offset from a starting symbol for measuring CLI. For example, 1318 may be performed by Fig. 9 The victim UE 906 in the embodiment may receive a sub-symbol timing offset as part of a CLI resource configuration 922 from a victim network node 908. The sub-symbol timing offset may indicate an offset from a starting symbol for measuring the CLI, for example, Figure 7 UL Tx / CLI 732 in symbol 710 may have a sub-symbol timing offset of 8 microseconds in symbol 2. In addition, 1318 may be Fig.17 Component 198 in is executed.
[0124] At 1320, the first UE may analyze the start symbol to calculate the sub-symbol timing offset. The Rx timing of one or more CLI measurement resources may be measured using a trigger offset indicating the start symbol of the CLI to be measured. For example, 1320 may be determined by Fig. 9 The victim UE 906 in the example may analyze the starting symbol to calculate the sub-symbol timing offset at 912. The victim UE 906 may measure the symbol indicating the trigger offset, which indicates the starting symbol of the CLI to be measured, such as Figure 7 The trigger offset for the two symbols of UL Tx / CLI 732 in 1320 can be Fig.17 Component 198 in is executed.
[0125] Fig.141400 is a flowchart of a method of wireless communication. The method may be performed by a base station (e.g., base station 102, 310; network node 402, 404, 406, 408, 506, 806, 908, 1008; network entity 1702). At 1402, a first network node may configure at least one parameter associated with Rx timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with a CLI between at least one first UE configured to communicate with the first network node and at least one second UE configured to communicate with the second network node. (a) the first network node includes a first TN and the second network node includes a second NTN, (b) the first network node includes a first NTN and the second network node includes a second TN, or (c) the first network node includes a first NTN and the second network node includes a second NTN different from the first NTN. For example, 1402 may be performed by Figure 8 The victim network node 806 in the embodiment may be executed, and the victim network node may configure at least one timing parameter associated with the Rx timing of the UL Tx 828 at 816. The UL Tx 828 may be associated with a CLI between the victim UE 808 configured to communicate with the victim network node 806 and the aggressor UE 802 configured to communicate with the aggressor network node 804. In addition, the victim network node 806 may include a TN, such as Figure 4 The first TN network node 406 in the embodiment, and the aggressor network node 804 may include an NTN, such as Figure 4 The second NTN network node 404 in the embodiment. Alternatively, the victim network node 806 may include an NTN, such as Figure 4 The first NTN network node 402 in the embodiment, and the aggressor network node 804 may include a TN, such as Figure 4 Alternatively, the victim network node 806 may include a first NTN, such as Figure 4 The first NTN network node 402 in the embodiment, and the aggressor network node 804 may include a second NTN, such as Figure 4 The second NTN network node 404 in. In addition, 1402 can be Fig.18 Component 199 in is executed.
[0126] At 1404, the first network node may output at least one parameter associated with one or more CLI measured Rx timings to at least one first UE. For example, 1404 may be performed by Figure 8 The victim network node 806 in the embodiment may be configured to output a timing parameter 827 associated with the Rx timing of the UL Tx 828 to the victim UE 808. In addition, 1404 may be performed by Fig.18 Component 199 in is executed.
[0127] Fig.15 1500 is a flow chart of a method of wireless communication. The method may be performed by a base station (e.g., base station 102, 310; network node 402, 404, 406, 408, 506, 806, 908, 1008; network entity 1702). At 1502, a first network node may obtain a UE position from at least one first UE. At least one parameter associated with Rx timing is configured based on the UE position. For example, 1502 may be performed by Figure 8 The victim network node 806 in the embodiment may be configured to provide a UE location 823 from the victim UE 808. The timing parameters 826 and 827 may be configured at 816 based on the UE location 823. In addition, 1502 may be performed by Fig.18 Component 199 in is executed.
[0128] At 1504, the first network node may configure at least one parameter associated with Rx timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with CLI between at least one first UE configured to communicate with the first network node and at least one second UE configured to communicate with the second network node. For example, 1504 may be performed by Figure 8 806 in the victim network node, which may configure at least one timing parameter associated with the Rx timing of UL Tx 828 at 816. UL Tx 828 may be associated with a CLI between a victim UE 808 configured to communicate with the victim network node 806 and an aggressor UE 802 configured to communicate with the aggressor network node 804. In addition, 1504 may be performed by Fig.18 Component 199 in is executed.
[0129] At 1506, the first network node may output at least one parameter associated with the Rx timing of the one or more CLI measurements to at least one first UE. For example, 1506 may be performed by Figure 8 The victim network node 806 in the embodiment may be configured to output the timing parameter 827 associated with the Rx timing of the UL Tx 828 to the victim UE 808. In addition, 1506 may be performed by Fig.18 Component 199 in is executed.
[0130] At 1508, the first network node may avoid sending one or more serving DL channels or resources to at least one first UE during the Rx timing. The one or more serving DL channels or resources may overlap with at least one symbol of the one or more CLI measurement resources. For example, 1508 may be performed by Figure 8The victim network node 806 in the embodiment may be configured to avoid scheduling a service DL overlapping with the Rx timing of the UL Tx 828 at 819. In addition, 1508 may be performed by Fig.18 Component 199 in is executed.
[0131] At 1510, the first network node may obtain an indication of Rx timing from at least one first UE. At least one parameter associated with the Rx timing may be configured based on the indication of the Rx timing. For example, 1510 may be configured by Figure 8 806 in the victim network node 808, the victim network node may be configured to obtain a UE position 823 from the victim UE 808, the UE position may be used to determine the timing delay between the aggressor UE 802 and the aggressor network node 804 by estimating the position of the aggressor UE using the UE position 823. The victim network node 806 may use the UE position 823 to configure the timing parameters at 816. In addition, 1510 may be performed by Fig.18 Component 199 in is executed.
[0132] At 1512, the first network node may output SRS resources to at least one first UE, wherein the indication of Rx timing is obtained from the at least one first UE via the SRS resources. Fig. 9 The victim network node 908 in the embodiment may be configured to output the SRS resource to the victim UE 906 as part of the CLI resource configuration 922 output. In addition, 1512 may be performed by Fig.18 Component 199 in is executed.
[0133] At 1514, the first network node may obtain an indication of Rx timing from at least one first UE by obtaining a UAI including an indication of Rx timing. For example, 1514 may be performed by Fig. 9 The victim network node 908 in the embodiment may be configured to obtain the CLI measurement report 926 from the victim US 906 by obtaining the UAI including the CLI measurement report 926. In addition, 1514 may be performed by Fig.18 Component 199 in is executed.
[0134] Fig.161600 is a flow chart of a method of wireless communication. The method may be performed by a base station (e.g., base station 102, 310; network node 402, 404, 406, 408, 506, 806, 908, 1008; network entity 1702). At 1602, a first network node may configure at least one parameter associated with Rx timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with CLI between at least one first UE configured to communicate with the first network node and at least one second UE configured to communicate with the second network node. For example, 1602 may be performed by Figure 8 The victim network node 806 in the embodiment may be configured at 816 with at least one timing parameter associated with the Rx timing of UL Tx 828. UL Tx 828 may be associated with a CLI between a victim UE 808 configured to communicate with the victim network node 806 and an aggressor UE 802 configured to communicate with the aggressor network node 804. In addition, 1602 may be performed by Fig.18 Component 199 in is executed.
[0135] At 1604, the first network node may output at least one parameter associated with the Rx timing of one or more CLI measurements to at least one first UE. For example, 1604 may be performed by Figure 8 The victim network node 806 in the embodiment may be configured to output a timing parameter 827 associated with the Rx timing of the UL Tx 828 to the victim UE 808. In addition, 1604 may be performed by Fig.18 Component 199 in is executed.
[0136] At 1606, the first network node may output, to at least one first UE, an indication of aperiodic CLI measurement of at least one CLI measurement resource of the one or more CLI measurement resources. For example, 1606 may be performed by the victim network node 908, which may be configured to output an indication of aperiodic CLI measurement to the victim UE 906 as part of the CLI resource configuration 922 of the UL Tx 924. In addition, 1606 may be performed by Fig.18 Component 199 in is executed.
[0137] At 1608, the first network node may output an indication of the aperiodic CLI measurement to the at least one first UE, which includes outputting a DCI including the indication of the aperiodic CLI measurement to the at least one first UE. For example, 1608 may be performed by the victim network node 908, which may be configured to output the DCI including the indication of the aperiodic CLI measurement to the victim UE 906 as part of the CLI resource configuration 922 of the UL Tx 924. In addition, 1608 may be performed by Fig.18 Component 199 in is executed.
[0138] At 1610, the first network node may output a trigger offset to at least one first UE. The trigger offset may indicate a starting symbol of at least one CLI measurement resource of the one or more CLI measurement resources to be measured. For example, 1610 may be performed by a victim network node 908, which may be configured to output a trigger offset to a victim UE 906 as part of a CLI resource configuration 922. The trigger offset may indicate a starting symbol of a UL Tx 924 to be measured at 912. For example, Figure 6 The offset of two symbols of UL Tx / CLI 632 in 1610 can be Fig.18 Component 199 in is executed.
[0139] At 1612, the first network node may output a sub-symbol timing offset to at least one first UE. The sub-symbol timing offset may indicate an offset from a starting symbol of at least one CLI measurement resource of the one or more CLI measurement resources to be measured. For example, 1612 may be performed by a victim network node 908, which may be configured to output the sub-symbol timing offset to the victim UE 906 as part of a CLI resource configuration 922 output. The sub-symbol timing offset may indicate an offset from a starting symbol of the UL Tx 924 to be measured at 912. For example, a sub-symbol timing offset of 8 microseconds may be used to indicate an offset from a starting symbol of the UL Tx 924 to be measured at 912. Figure 7 The sub-symbol offset of the starting symbol 2 of UL Tx / CLI 732 in 1612. In addition, 1612 can be obtained by Fig.18 Component 199 in is executed.
[0140] Fig.171700 is an example of a hardware implementation of an exemplary device 1704. The device 1704 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 1304 may include a cellular baseband processor 1724 (also referred to as a modem) coupled to one or more transceivers 1722 (e.g., a cellular RF transceiver). The cellular baseband processor 1724 may include on-chip memory 1724'. In some aspects, the device 1704 may also include one or more subscriber identity module (SIM) cards 1720 and an application processor 1706 coupled to a secure digital (SD) card 1708 and a screen 1710. The application processor 1706 may include on-chip memory 1706'. In some aspects, the device 1704 may also include a Bluetooth module 1712, a WLAN module 1714, an SPS module 1716 (e.g., a GNSS module), one or more sensor modules 1718 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1726, a power supply 1730, and / or a camera 1732. The Bluetooth module 1712, the WLAN module 1714, and the SPS module 1716 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (Rx)). The Bluetooth module 1712, the WLAN module 1714, and the SPS module 1716 may include their own dedicated antennas and / or communicate using an antenna 1780. The cellular baseband processor 1724 communicates with the UE 104 and / or with the RU associated with the network entity 1702 through the transceiver 1722 via one or more antennas 1780. The cellular baseband processor 1724 and the application processor 1706 may each include a computer-readable medium / memory 1724', 1706', respectively. The additional memory module 1726 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1724', 1706', 1726 may be non-transitory. The cellular baseband processor 1724 and the application processor 1706 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1724 / application processor 1706, enables the cellular baseband processor 1724 / application processor 1706 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1724 / application processor 1706 when executing the software.The cellular baseband processor 1724 / application processor 1706 may be a component of the UE 350 and may include the memory 360 and / or at least one of the Tx processor 368, the Rx processor 356, and the controller / processor 359. In one configuration, the device 1704 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1724 and / or the application processor 1706, while in another configuration, the device 1704 may be the entire UE (e.g., see. Figure 3 UE 350) and includes additional modules of device 1704.
[0141] As described above, component 198 is configured to obtain at least one parameter associated with the Rx timing of one or more CLI measurement resources, and avoid receiving one or more service DL channels or resources from the network node during the Rx timing based on the at least one parameter. Component 198 may be within the cellular baseband processor 1724, the application processor 1706, or both the cellular baseband processor 1724 and the application processor 1706. Component 198 may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, device 1704 may include a variety of components configured for various functions. In one configuration, the apparatus 1704 (and specifically the cellular baseband processor 1724 and / or the application processor 1706) includes: means for obtaining at least one parameter associated with Rx timing of one or more CLI measurement resources; means for avoiding receiving one or more service DL channels or resources from the first network node during the Rx timing based on the at least one parameter; means for sending a UE position associated with the Rx timing; means for measuring the Rx timing of one or more CLI measurement resources; means for sending an indication of the Rx timing; means for receiving SRS resources; means for sending an indication of the Rx timing by sending a measurement of the Rx timing using the SRS resources; means for measuring the Rx timing of one or more CLI measurement resources by calculating the Rx timing based on a channel delay of the first UE, a channel delay of at least one second UE, and a corresponding timing reference; means for measuring the Rx timing of the one or more CLI measurement resources by using a trigger offset indicating a start symbol of the CLI to be measured a component for measuring the Rx timing of one or more CLI measurement resources by using the sub-symbol timing offset indicating the offset from the starting symbol of the CLI to be measured; a component for analyzing the starting symbol to calculate the sub-symbol timing offset; a component for measuring the Rx timing of one or more CLI measurement resources using the triggering offset indicating the starting symbol of the CLI to be measured; a component for sending an indication of the Rx timing by sending a UAI including an indication of the Rx timing; a component for obtaining at least one parameter associated with the Rx timing by receiving at least one parameter associated with the Rx timing from a first network node; a component for sending an inter-UE measurement result based on at least one parameter associated with the Rx timing of the one or more CLI measurement resources; and a component for measuring the one or more CLI measurement resources during the Rx timing of the one or more CLI measurement resources.A means may be a component 198 of the apparatus 1704 configured to perform the functions recited by the means. As described above, the apparatus 1704 may include a Tx processor 368, an Rx processor 356, and a controller / processor 359. Thus, in one configuration, these means may be the Tx processor 368, the Rx processor 356, and the controller / processor 359 configured to perform the functions recited by these means.
[0142] Fig.18 1800 is a diagram illustrating an example of a hardware implementation for a network entity 1802. The network entity 1802 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1802 may include at least one of a CU 1810, a DU 1830, or a RU 1840. For example, depending on the layer functionality handled by the component 199, the network entity 1802 may include a CU 1810; both a CU 1810 and a DU 1830; each of the CU 1810, the DU 1830, and the RU 1840; the DU 1830; both a DU 1830 and a RU 1840; or a RU 1840. The CU 1810 may include a CU processor 1812. The CU processor 1812 may include an on-chip memory 1812'. In some aspects, the CU 1810 may also include an additional memory module 1814 and a communication interface 1818. CU 1810 communicates with DU 1830 via a midhaul link such as an F1 interface. DU 1830 may include a DU processor 1832. DU processor 1832 may include on-chip memory 1832'. In some aspects, DU 1830 may also include an additional memory module 1834 and a communication interface 1838. DU 1830 communicates with RU 1840 via a fronthaul link. RU 1840 may include a RU processor 1842. RU processor 1842 may include on-chip memory 1842'. In some aspects, RU 1840 may also include an additional memory module 1844, one or more transceivers 1846, an antenna 1880, and a communication interface 1848. RU 1840 communicates with UE 104. On-chip memory 1812', 1832', 1842' and additional memory modules 1814, 1834, 1844 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1812, 1832, 1842 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.
[0143] As described above, component 199 is configured to configure at least one parameter associated with the Rx timing of one or more CLI measurement resources, and output at least one parameter associated with the Rx timing of one or more CLI measurement resources to the UE. Component 199 may be within one or more processors of one or more of CU 1810, DU 1830, and RU 1840. Component 199 may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1802 may include a variety of components configured for various functions. In one configuration, the network entity 1802 includes: a component for configuring at least one parameter associated with the Rx timing of one or more CLI measurement resources; a component for outputting at least one parameter associated with the Rx timing of one or more CLI measurement resources to at least one first UE; a component for obtaining a UE position from at least one first UE; a component for outputting SRS resources to at least one first UE; a component for obtaining an indication of Rx timing from at least one first UE by obtaining a UAI including an indication of Rx timing; a component for outputting an indication of aperiodic CLI measurement of at least one CLI measurement resource among the one or more CLI measurement resources to at least one first UE; a component for outputting an indication of aperiodic CLI measurement to at least one first UE by outputting a DCI including an indication of aperiodic CLI measurement to at least one first UE; a component for outputting a trigger offset to at least one first UE; a component for outputting a sub-symbol timing offset to at least one first UE; and a component for avoiding sending one or more service DL channels or resources to at least one first UE during Rx timing, wherein the component of the one or more service DL channels or resources overlaps with at least one symbol of the one or more CLI measurement resources. The means may be a component 199 of the network entity 1802 configured to perform the functions recited by the means. As described above, the network entity 1802 may include a Tx processor 316, an Rx processor 370, and a controller / processor 375. Thus, in one configuration, the means may be the Tx processor 316, the Rx processor 370, and the controller / processor 375 configured to perform the functions recited by the means.
[0144] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of various blocks in a sample order, but are not limited to the specific order or hierarchy provided.
[0145] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, references to elements in the singular form do not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, then the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The wording "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."
[0146] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.
[0147] A device configured to "output" data (such as, transmit, signal or message) may, for example, transmit the data with a transceiver, or may transmit the data to a device that transmits the data. A device configured to "obtain" data (such as, transmit, signal or message) may, for example, receive the data with a transceiver, or may obtain the data from a device that receives the data.
[0148] A "serving DL channel" may include frequencies / wavelengths of the electromagnetic spectrum used by a network node of a UE's serving cell to transmit from the network node's transceiver to the UE, such as Figure 2B DL channel of diagram 230 in FIG.
[0149] "Resource" may include any portion of the electromagnetic spectrum defined in the time domain, such as FIG. 2A to FIG. 2D resource block.
[0150] Cross-link interference or "CLI" may include interference that occurs when one wireless device is using resources to transmit while another wireless device is using the same resources or serving DL channel to receive. Such resource overlap may reduce the ability or likelihood of a device such as a UE to successfully decode the Rx signal using the overlapping resources.
[0151] The "CLI measurement resource" may include a Tx signal that can cause CLI to a serving DL channel of the UE. The CLI measurement resource may include a PUCCH or a PUSCH.
[0152] When two UEs share a cell such that a Tx signal from one UE causes CLI to an Rx signal to another UE, the UE transmitting the Tx signal may be referred to as an “aggressor UE” and the UE receiving the Rx signal may be referred to as a “victim UE”.
[0153] UE assistance information or "UAI" may include any information element (IE) provided by the UE that can be used to determine the timing delay of the UE, such as delay budget report, connected mode DRX cycle length, overheat assistance information, or timing offset between Tx and Rx signals using overlapping resources.
[0154] The "Rx timing" may include the start time and the end time of the wireless signal received by the UE.
[0155] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.
[0156] Aspect 1 is a method for wireless communication at a first UE, the method comprising obtaining at least one parameter associated with Rx timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with CLI between the first UE and at least one second UE. The method may also include avoiding receiving one or more service DL channels or resources from a first network node during the Rx timing based on the at least one parameter. The one or more service DL channels or resources may overlap with at least one symbol of the one or more CLI measurement resources.
[0157] Aspect 2 is a method according to aspect 1, the method further comprising sending a UE position associated with the Rx timing to the first network node.
[0158] Aspect 3 is a method according to any one of aspects 1 and 2, the method further comprising measuring the Rx timing of the one or more CLI measurement resources. The method may also include sending an indication of the Rx timing to the first network node.
[0159] Aspect 4 is a method according to aspect 3, the method further comprising receiving an SRS resource from the second UE as the CLI measurement resource.Sending the indication of the Rx timing may include sending a measurement of the Rx timing of the SRS resource.
[0160] Aspect 5 is a method according to any one of Aspects 3 to 4, wherein measuring the Rx timing of the one or more CLI measurement resources may include calculating the Rx timing based on the channel delay of the first UE, the channel delay of the at least one second UE and the corresponding timing reference.
[0161] Aspect 6 is a method according to any one of aspects 3 to 5, wherein the Rx timing of the one or more CLI measurement resources is measured using a trigger offset indicating a starting symbol at which the CLI is to be measured.
[0162] Aspect 7 is a method according to aspect 6, the method further comprising receiving, from the first network node, a DCI triggering the Rx timing measured as a non-periodic CLI measurement.
[0163] Aspect 8 is a method according to any one of aspects 6 to 7, the method further comprising receiving a sub-symbol timing offset from the first network node. The Rx timing of the one or more CLI measurement resources may be measured using the sub-symbol timing offset indicating an offset from the starting symbol for measuring the CLI.
[0164] Aspect 9 is a method according to any one of aspects 6 to 7, the method further comprising analyzing the start symbol to calculate a sub-symbol timing offset. The Rx timing of the one or more CLI measurement resources may be measured using the trigger offset indicating the start symbol of the CLI to be measured.
[0165] Aspect 10 is a method according to any one of aspects 3 to 9, wherein sending the indication of the Rx timing may include sending a UAI with the indication of the Rx timing.
[0166] Aspect 11 is a method according to any one of aspects 1 to 10, wherein obtaining the at least one parameter associated with the Rx timing may include receiving the at least one parameter associated with the Rx timing from the first network node.
[0167] Aspect 12 is a method according to any one of Aspects 1 to 11, wherein the at least one parameter associated with the Rx timing of the one or more CLI measurement resources may include an initial timing offset, a conversion rate for linearly modeling changes, or at least one of a set of variables in a formula configured to model higher-order changes of the initial timing offset.
[0168] Aspect 13 is a method according to any one of Aspects 1 to 12, the method further comprising sending an inter-UE measurement result to a second network node communicating with the at least one second UE based on the at least one parameter associated with the Rx timing of the one or more CLI measurement resources.
[0169] Aspect 14 is a method according to Aspect 13, wherein (a) the first network node includes a first TN and the second network node includes a second NTN, (b) the first network node includes a first NTN and the second network node includes a second TN, or (c) the first network node includes a first NTN and the second network node includes the second NTN different from the first NTN.
[0170] Aspect 15 is a method according to any one of aspects 1 to 14, wherein the one or more serving DL channels or resources include at least one of a PDCCH, a PDSCH or a CSI-RS.
[0171] Aspect 16 is a method according to any one of Aspects 1 to 15, the method further comprising measuring the one or more CLI measurement resources during the Rx timing of the one or more CLI measurement resources.
[0172] Aspect 17 is a method for wireless communication at a first network node, the method comprising configuring at least one parameter associated with Rx timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with a CLI between at least one first UE configured to communicate with the first network node and at least one second UE configured to communicate with a second network node. (a) the first network node includes a first TN and the second network node includes a second NTN, (b) the first network node includes a first NTN and the second network node includes a second TN, or (c) the first network node includes a first NTN and the second network node includes a second NTN different from the first NTN. The method may also include outputting the at least one parameter associated with the Rx timing of the one or more CLI measurement resources to the at least one first UE.
[0173] Aspect 18 is a method according to aspect 17, the method further comprising obtaining a UE position from the at least one first UE. The at least one parameter associated with the Rx timing may be configured based on the UE position.
[0174] Aspect 19 is a method according to any one of aspects 16 to 17, the method further comprising obtaining an indication of the Rx timing from the at least one first UE. The at least one parameter associated with the Rx timing may be configured based on the indication of the Rx timing.
[0175] Aspect 20 is a method according to aspect 19, the method further comprising outputting SRS resources to the at least one first UE. The indication of the Rx timing may be obtained from the at least one first UE via the SRS resources.
[0176] Aspect 21 is a method according to any one of aspects 19 to 20, wherein obtaining the indication of the Rx timing from the at least one first UE may include obtaining a UAI having the indication of the Rx timing.
[0177] Aspect 22 is a method according to any one of Aspects 19 to 21, wherein the indication of the Rx timing may include at least one of an initial timing offset, a conversion rate for linearly modeling changes, or a variable set of a formula configured to model higher-order changes of the initial timing offset.
[0178] Aspect 23 is a method according to any one of aspects 17 to 22, the method also comprising outputting an indication of aperiodic CLI measurement of at least one CLI measurement resource of the one or more CLI measurement resources to the at least one first UE.
[0179] Aspect 24 is a method according to aspect 23, wherein outputting the indication of the aperiodic CLI measurement to the at least one first UE may include outputting a DCI having the indication of the aperiodic CLI measurement to the at least one first UE.
[0180] Aspect 25 is a method according to any one of aspects 23 to 24, the method further comprising outputting a trigger offset to the at least one first UE. The trigger offset may indicate a starting symbol of the at least one CLI measurement resource in the one or more CLI measurement resources to be measured.
[0181] Aspect 26 is a method according to aspect 25, the method further comprising outputting a sub-symbol timing offset to the at least one first UE. The sub-symbol timing offset may indicate an offset from the starting symbol of the at least one CLI measurement resource to be measured in the one or more CLI measurement resources.
[0182] Aspect 27 is a method for wireless communication at a first network node, the method comprising configuring at least one parameter associated with Rx timing of one or more CLI measurement resources. The one or more CLI measurement resources may be associated with a CLI between at least one first UE configured to communicate with the first network node and at least one second UE configured to communicate with a second network node. (a) the first network node includes a first TN and the second network node includes a second NTN, (b) the first network node includes a first NTN and the second network node includes a second TN, or (c) the first network node includes a first NTN and the second network node includes a second NTN different from the first NTN. The method may also include avoiding sending one or more service DL channels or resources to the at least one first UE during the Rx timing. The one or more service DL channels or resources may overlap with at least one symbol of the one or more CLI measurement resources.
[0183] Aspect 28 is a method according to aspect 27, wherein the one or more serving DL channels or resources may include at least one of a PDCCH, a PDSCH, or a CSI-RS.
[0184] Aspect 29 is a device for wireless communication, wherein the device is used to implement the method as described in any one of Aspects 1 to 28.
[0185] Aspect 30 is an apparatus for wireless communication, the apparatus comprising means for implementing the method as described in any one of aspects 1 to 28.
[0186] Aspect 31 may be combined with any of aspects 29 to 30 and further comprises at least one of a transceiver or an antenna coupled to at least one processor of the apparatus.
[0187] Aspect 32 is a non-transitory computer-readable medium storing computer-executable code, which, when executed by at least one processor, causes the at least one processor to implement the method as described in any one of aspects 1 to 28.
Claims
1. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: obtaining at least one parameter associated with a receive (Rx) timing of one or more cross-link interference (CLI) measurement resources associated with a CLI between the first UE and at least one second UE; and Receiving one or more serving downlink (DL) channels or resources from the first network node during the Rx timing is avoided based on the at least one parameter, the one or more serving DL channels or resources overlapping with at least one symbol of the one or more CLI measurement resources.
2. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor, wherein the at least one processor is further configured to send the UE location associated with the Rx timing to the first network node via the transceiver.
3. The apparatus of claim 1 , wherein the at least one processor is further configured to: measuring the Rx timing of the one or more CLI measurement resources; and An indication of the Rx timing is sent to the first network node.
4. The apparatus of claim 3, wherein the at least one processor is further configured to: A sounding reference signal (SRS) resource is received from the second UE as the CLI measurement resource, wherein sending the indication of the Rx timing includes sending a measurement of the Rx timing of the SRS resource.
5. The apparatus of claim 3, wherein the at least one processor is further configured to measure the Rx timing of the one or more CLI measurement resources by calculating the Rx timing based on a channel delay of the first UE, a channel delay of the at least one second UE, and a corresponding timing reference.
6. The apparatus of claim 3, wherein the Rx timing of the one or more CLI measurement resources is measured using a trigger offset indicating a start symbol at which the CLI is to be measured.
7. The apparatus of claim 6, wherein the at least one processor is further configured to receive downlink control information (DCI) from the first network node triggering the Rx timing measured as an aperiodic CLI measurement.
8. The apparatus of claim 6, wherein the at least one processor is further configured to receive a sub-symbol timing offset from the first network node, wherein the Rx timing of the one or more CLI measurement resources is measured using the sub-symbol timing offset indicating an offset from the start symbol at which the CLI is to be measured.
9. The apparatus of claim 6, wherein the at least one processor is further configured to analyze the start symbol to calculate a sub-symbol timing offset, wherein the Rx timing of the one or more CLI measurement resources is measured using the trigger offset indicating the start symbol at which the CLI is to be measured.
10. The apparatus of claim 3, wherein the at least one processor is further configured to send the indication of the Rx timing by sending UE Assistance Information (UAI) including the indication of the Rx timing.
11. The apparatus according to claim 1, wherein the at least one processor is further configured to obtain the at least one parameter associated with the Rx timing by receiving the at least one parameter associated with the Rx timing from the first network node.
12. The apparatus of claim 1 , wherein the at least one parameter associated with the Rx timing of the one or more CLI measurement resources comprises at least one of an initial timing offset, a slew rate for linearly modeling variations, or a set of variables of a formula configured to model higher order variations of the initial timing offset.
13. The apparatus of claim 1, wherein the at least one processor is further configured to send an inter-UE measurement result to a second network node communicating with the at least one second UE based on the at least one parameter associated with the Rx timing of the one or more CLI measurement resources.
14. The apparatus of claim 13, wherein the first network node comprises a first terrestrial network (TN) and the second network node comprises a second non-terrestrial network (NTN), the first network node comprises a first NTN and the second network node comprises a second TN, or the first network node comprises the first NTN and the second network node comprises the second NTN different from the first NTN.
15. The apparatus of claim 1, wherein the one or more serving DL channels or resources comprise at least one of a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), or a channel state information reference signal (CSI-RS).
16. The apparatus of claim 1, wherein the at least one processor is further configured to measure the one or more CLI measurement resources during the Rx timing of the one or more CLI measurement resources.
17. An apparatus for wireless communication at a first network node, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: configuring at least one parameter associated with receive (Rx) timing of one or more cross-link interference (CLI) measurement resources, The one or more CLI measurement resources are associated with a CLI between at least one first user equipment (UE) configured to communicate with the first network node and at least one second UE configured to communicate with the second network node, and (a) the first network node comprises a first terrestrial network (TN) and the second network node comprises a second non-terrestrial network (NTN), (b) the first network node comprises a first NTN and the second network node comprises a second TN, or (c) the first network node comprises the first NTN and the second network node comprises the second NTN different from the first NTN; as well as The at least one parameter associated with the Rx timing of the one or more CLI measurement resources is output to the at least one first UE.
18. The apparatus of claim 17, further comprising a transceiver coupled to the at least one processor, wherein the at least one processor is further configured to obtain a UE location from the at least one first UE, wherein the at least one parameter associated with the Rx timing is configured based on the UE location.
19. The apparatus of claim 17, wherein the at least one processor is further configured to obtain an indication of the Rx timing from the at least one first UE, wherein the at least one parameter associated with the Rx timing is configured based on the indication of the Rx timing.
20. The apparatus of claim 19, wherein the at least one processor is further configured to: A sounding reference signal (SRS) resource is output to the at least one first UE, wherein the indication of the Rx timing is obtained from the at least one first UE via the SRS resource.
21. The apparatus of claim 19, wherein the at least one processor is further configured to obtain the indication of the Rx timing from the at least one first UE by obtaining UE Assistance Information (UAI) including the indication of the Rx timing.
22. The apparatus of claim 19, wherein the indication of the Rx timing comprises at least one of an initial timing offset, a slew rate for linearly modeling variations, or a set of variables of a formula configured to model higher order variations of the initial timing offset.
23. The apparatus of claim 17, wherein the at least one processor is further configured to output, to the at least one first UE, an indication of an aperiodic CLI measurement of at least one CLI measurement resource of the one or more CLI measurement resources.
24. The apparatus of claim 23, wherein the at least one processor is further configured to output the indication of the non-periodic CLI measurement to the at least one first UE by outputting downlink control information (DCI) including the indication of the non-periodic CLI measurement to the at least one first UE.
25. The apparatus of claim 23, wherein the at least one processor is further configured to output a trigger offset to the at least one first UE, wherein the trigger offset indicates a starting symbol of at least one CLI measurement resource among the one or more CLI measurement resources to be measured.
26. The apparatus of claim 25, wherein the at least one processor is further configured to output a sub-symbol timing offset to the at least one first UE, wherein the sub-symbol timing offset indicates an offset from the starting symbol of the at least one CLI measurement resource among the one or more CLI measurement resources to be measured.
27. The apparatus of claim 17, wherein the at least one processor is further configured to: Avoid transmitting one or more serving downlink (DL) channels or resources to the at least one first UE during the Rx timing, wherein the one or more serving DL channels or resources overlap with at least one symbol of the one or more CLI measurement resources.
28. The apparatus of claim 27, wherein the one or more serving DL channels or resources comprise at least one of a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), or a channel state information reference signal (CSI-RS).
29. A method of wireless communication at a first user equipment (UE), the method comprising: obtaining at least one parameter associated with a receive (Rx) timing of one or more cross-link interference (CLI) measurement resources associated with a CLI between the first UE and at least one second UE; and Receiving one or more serving downlink (DL) channels or resources from the first network node during the Rx timing is avoided based on the at least one parameter, the one or more serving DL channels or resources overlapping with at least one symbol of the one or more CLI measurement resources.
30. A method of wireless communication at a first network node, the method comprising: configuring at least one parameter associated with receive (Rx) timing of one or more cross-link interference (CLI) measurement resources, The one or more CLI measurement resources are associated with a CLI between at least one first user equipment (UE) configured to communicate with the first network node and at least one second UE configured to communicate with a second network node, (a) the first network node comprises a first terrestrial network (TN) and the second network node comprises a second non-terrestrial network (NTN), (b) the first network node comprises a first NTN and the second network node comprises a second TN, or the first network node comprises the first NTN and the second network node comprises the second NTN different from the first NTN; as well as The at least one parameter associated with the Rx timing of the one or more CLI measurement resources is output to the at least one first UE.
