Non-overlapping cross-link interference reference signal transmission and reception windows
By configuring non-overlapping transmit and receive windows for network nodes, the self-interference problem in cross-link interference measurement between network nodes in full-duplex mode is solved, improving measurement accuracy and communication efficiency, and enhancing the spectrum utilization of the wireless communication system.
Patent Information
- Application Number
- CN202380030673.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-04
- Filing Date
- 2023-03-29
- Publication Date
- 2024-11-12
AI Technical Summary
In existing wireless communication systems, the configuration method for cross-link interference measurement reference signals between network nodes suffers from self-interference and insufficient measurement accuracy. Especially in full-duplex mode, the overlap of the transmitting and receiving windows leads to severe interference, affecting communication quality.
By configuring non-overlapping transmit and receive windows for network nodes, it is ensured that the CLI measurement reference signaling of network nodes does not interfere with itself in full-duplex mode. The instruction set is stored on a non-transient computer-readable medium to guide the central network entity and network nodes in configuration, so as to achieve non-overlapping transmit and receive windows in time.
It improves the accuracy of CLI measurements between network nodes, reduces self-interference, enhances communication efficiency and spectrum utilization, and improves network communication quality.
Smart Images

Figure CN118947162A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 657,881, filed on April 4, 2022, entitled “NON-OVERLAPPED CROSS-LINK INTERFERENCE REFERENCE SIGNALTRANSMISSION AND RECEPTION WINDOWS,” which is hereby expressly incorporated herein by reference. Technical Field
[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for non-overlapping cross-link interference reference signal transmit and receive windows. Background Art
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.
[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention
[0007] Some aspects described herein relate to a method of wireless communication performed by a central network entity. The method may include: configuring a network node with a first configuration indicating one or more transmission windows for cross-link interference (CLI) measurement reference signaling between network nodes. The method may include: configuring the network node with a second configuration indicating multiple reception windows for CLI measurement reference signaling between network nodes, wherein the one or more transmission windows are configured to not overlap with each reception window of the multiple reception windows.
[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include: receiving a first configuration indicating one or more transmit windows for inter-network node CLI measurement reference signaling. The method may include: receiving a second configuration indicating one or more receive windows for inter-network node CLI measurement reference signaling, wherein the one or more transmit windows are configured to not overlap with each of the one or more receive windows.
[0009] Some aspects described herein relate to an apparatus of a central network entity for wireless communication. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to cause the central network entity to configure a first configuration for a network node indicating one or more transmission windows for inter-network node CLI measurement reference signaling. The one or more processors may be configured to cause the central network entity to configure a second configuration for the network node indicating multiple reception windows for inter-network node CLI measurement reference signaling, wherein the one or more transmission windows are configured to not overlap with each of the multiple reception windows.
[0010] Some aspects described herein relate to an apparatus of a network node for wireless communication. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to cause the network node to: receive a first configuration indicating one or more send windows for inter-network node CLI measurement reference signaling. The one or more processors may be configured to cause the network node to: receive a second configuration indicating one or more receive windows for inter-network node CLI measurement reference signaling, wherein the one or more send windows are configured to not overlap with each of the one or more receive windows.
[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a central network entity. The set of instructions, when executed by one or more processors of the central network entity, may cause the central network entity to configure a first configuration for a network node indicating one or more transmission windows for inter-network node CLI measurement reference signaling. The set of instructions, when executed by one or more processors of the central network entity, may cause the central network entity to configure a second configuration for the network node indicating multiple reception windows for inter-network node CLI measurement reference signaling, wherein the one or more transmission windows are configured to not overlap with each of the multiple reception windows.
[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to: receive a first configuration indicating one or more transmission windows for inter-network node CLI measurement reference signaling. The instruction set, when executed by one or more processors of the network node, may cause the network node to: receive a second configuration indicating one or more reception windows for inter-network node CLI measurement reference signaling, wherein the one or more transmission windows are configured to not overlap with each of the one or more reception windows.
[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for configuring a first configuration for a network node indicating one or more transmit windows for inter-network node CLI measurement reference signaling. The apparatus may include: means for configuring a second configuration for the network node indicating multiple receive windows for inter-network node CLI measurement reference signaling, wherein the one or more transmit windows are configured to not overlap with each of the multiple receive windows.
[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: a means for receiving a first configuration indicating one or more transmit windows for inter-network node CLI measurement reference signaling. The apparatus may include: a means for receiving a second configuration indicating one or more receive windows for inter-network node CLI measurement reference signaling, wherein the one or more transmit windows are configured to not overlap with each of the one or more receive windows.
[0015] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated by the accompanying drawings.
[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.
[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.
[0020] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.
[0021] Figure 3 is a diagram illustrating an example of a radio access network according to the present disclosure.
[0022] Figure 4 is a diagram illustrating an example of an integrated access and backhaul (IAB) network architecture according to the present disclosure.
[0023] Figure 5 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.
[0024] FIG. 6A to FIG. 6D is a diagram illustrating an example of full-duplex (FD) communication according to the present disclosure.
[0025] Figure 7 is a diagram illustrating an example of configuration and signaling of a synchronization signal block (SSB) between half-duplex IAB nodes according to the present disclosure.
[0026] Figure 8 is a diagram illustrating an example of configuration of a transmission window and a reception window for transmission and measurement of a cross-link interference (CLI) measurement reference signal (RS) between network nodes (e.g., between gNBs) according to the present disclosure.
[0027] Fig. 9 is a diagram illustrating an example of signaling associated with configuration of a transmission window and a reception window for inter-network node CLI measurement reference signaling according to the present disclosure.
[0028] Fig.10 is a diagram illustrating an example process performed, for example, by a central network entity according to the present disclosure.
[0029] Fig.11 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.
[0030] Fig.12is a diagram of an example apparatus for wireless communications according to the present disclosure.
[0031] Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION
[0032] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality, or structures and functionality other than the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims.
[0033] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a 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.
[0034] Although aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).
[0035] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.
[0036] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femto cell (e.g., UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.
[0037] In some examples, the cells may not necessarily be stationary, and the geographic area of the cells may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).
[0038] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communications between BS 110a and UE 120d. Base station 110 that relays communications may be referred to as a relay station, relay base station, relay, or the like.
[0039] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).
[0040] The network controller 130 may be coupled to or communicate with a set of base stations 110 and may provide coordination and control for these base stations. The network controller 130 may communicate with the base stations 110 via a backhaul communication link, a midhaul communication link, or a fronthaul communication link. In some aspects, the network controller 130 may include a central network entity, such as a central unit (CU) or an operation, administration, and maintenance (OAM) function. The network controller 130 may be implemented using hardware, software, or a combination of hardware and software. The base stations 110 may communicate with each other directly or indirectly via a wireless backhaul communication link or a wired backhaul communication link.
[0041] UE 120 may be distributed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.
[0042] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0043] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0044] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.
[0045] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. 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). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes occur 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).
[0046] 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 FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.
[0047] In view of the above examples, unless otherwise specifically stated, it should be understood that the term "below 6 GHz", etc., if used herein, can be broadly referred to as frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that the term "millimeter wave", etc., if used herein, can be broadly referred to as frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.
[0048] In some aspects, a central network entity (such as a network controller 130 or a base station 110) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: configure a first configuration for a network node indicating one or more transmit windows for inter-network node CLI measurement reference signaling; and configure a second configuration for the network node indicating multiple receive windows for inter-network node CLI measurement reference signaling, wherein the one or more transmit windows are configured to not overlap with each of the multiple receive windows. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0049] In some aspects, a network node, such as a base station 110, may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: receive a first configuration indicating one or more transmit windows for inter-network node CLI measurement reference signaling; and receive a second configuration indicating one or more receive windows for inter-network node CLI measurement reference signaling, wherein the one or more transmit windows are configured to not overlap with each of the one or more receive windows. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.
[0050] As indicated above, Figure 1 Other examples can be found in the Figure 1 The examples described are different.
[0051] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).
[0052] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modulators) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).
[0053] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the base station 110 and / or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.
[0054] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.
[0055] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.
[0056] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 3 to 13 ) or any aspect of any of the methods described herein.
[0057] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 20). Figures 3 to 13 ) or any aspect of any of the methods described herein.
[0058] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with configuring a transmission and reception window for CLI measurement reference signaling between network nodes, as described in more detail elsewhere herein. Figure 2 Any other component of the Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example, Fig.10 The process of 1000 Fig.11 The process 1100 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.
[0059] In some aspects, the central network entity includes: means for configuring a first configuration for a network node indicating one or more transmission windows for cross-link interference (CLI) measurement reference signaling between network nodes; and / or means for configuring a second configuration for a network node indicating multiple reception windows for CLI measurement reference signaling between network nodes, wherein the one or more transmission windows are configured to not overlap with each of the multiple reception windows. In some aspects, the means for the central network entity to perform the operations described herein may include, for example, one or more of the communication manager 140, the controller / processor 290, or the memory 292. In some aspects, such means may include information about Figure 3 One or more components or functions described in connection with FIG. 6 .
[0060] In some aspects, the network node includes: a first configuration component for receiving one or more transmission windows for inter-network node CLI measurement reference signaling; and / or a second configuration component for receiving one or more reception windows for inter-network node CLI measurement reference signaling, wherein the one or more transmission windows are configured to not overlap with each of the one or more reception windows. In some aspects, the components for the network node to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.
[0061] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.
[0062] As indicated above, Figure 2 Other examples can be found in the Figure 2 The examples described are different.
[0063] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components 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 RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station.
[0064] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as a CU, one or more distributed units (DUs), or one or more radio units (RUs). In some examples, a CU may be implemented within a radio access network (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 the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.
[0065] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed 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)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of the decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.
[0066] Figure 3 is a diagram illustrating an example 300 of a radio access network according to the present disclosure.
[0067] As shown by reference numeral 305, a conventional (e.g., 3G, 4G, or LTE) radio access network may include a plurality of base stations 310 (e.g., access nodes (ANs)), wherein each base station 310 communicates with a core network via a wired backhaul link 315 (such as a fiber optic connection). The base stations 310 may communicate with UEs 320 via access links 325 (which may be wireless links). In some aspects, Figure 3 The base station 310 shown may be Figure 1 The base station 110 is shown. In some aspects, Figure 3 The UE 320 shown may be Figure 1 UE 120 is shown.
[0068] As shown by reference numeral 330, the radio access network may include a wireless backhaul network, sometimes referred to as an IAB network. In an IAB network, at least one base station is an anchor base station 335 that communicates with a core network via a wired backhaul link 340 (such as a fiber optic connection). The anchor base station 335 may also be referred to as an IAB donor (or IAB-donor). The IAB network may include one or more non-anchor base stations 345, sometimes referred to as relay base stations or IAB nodes (or IAB-nodes). The non-anchor base station 345 may communicate directly or indirectly with the anchor base station 335 via one or more backhaul links 350 (e.g., via one or more non-anchor base stations 345) to form a backhaul path to the core network for carrying backhaul traffic. The backhaul link 350 may be a wireless link. The anchor base station 335 and / or the non-anchor base station 345 may communicate with one or more UEs 355 via an access link 360 (which may be a wireless link for carrying access traffic). In some aspects, Figure 3 The anchor base station 335 and / or the non-anchor base station 345 shown may be Figure 1 The base station 110 is shown. In some aspects, Figure 3 The UE 355 shown may be Figure 1 UE 120 is shown.
[0069] As shown by reference numeral 365, in some aspects, a radio access network including an IAB network may use millimeter wave technology and / or directional communication (e.g., beamforming) for communication between base stations and / or UEs (e.g., between two base stations, between two UEs, and / or between a base station and a UE). For example, a wireless backhaul link 370 between base stations may use millimeter wave signals to carry information and / or may use beamforming to be directed toward a target base station. Similarly, a wireless access link 375 between a UE and a base station may use millimeter wave signals and / or may be directed toward a target wireless node (e.g., a UE and / or a base station). In this way, inter-link interference may be reduced.
[0070] Figure 3 The configuration of the base station and UE in is shown as an example, and other examples are also contemplated. For example, Figure 3 The one or more base stations illustrated in the example may be replaced by one or more UEs communicating via a UE-to-UE access network (e.g., a peer-to-peer network or a device-to-device network). In this case, the anchor node may refer to a UE that communicates directly with a base station (e.g., an anchor base station or a non-anchor base station).
[0071] As indicated above, Figure 3 Other examples can be found in the Figure 3 The examples described are different.
[0072] Figure 4is a diagram illustrating an example 400 of an IAB network architecture according to the present disclosure.
[0073] like Figure 4 As shown, the IAB network may include an IAB donor 405 (shown as an IAB-donor) connected to the core network via a wired connection (shown as a wired backhaul). For example, the NG interface of the IAB donor 405 may terminate at the core network. Additionally or alternatively, the IAB donor 405 may be connected to one or more devices of the core network that provide a core access and mobility management function (AMF) and / or to one or more devices that provide OAM functions. In some aspects, the IAB donor 405 may include a base station 110, such as an anchor base station, as described above in conjunction with Figure 3 As described. As shown in the figure, the IAB donor 405 may include a CU, and the CU may perform access node controller (ANC) functions and / or AMF functions. In some aspects, the CU, the IAB donor 405 or the OAM function may be referred to as a central network entity in this article. The CU may configure the DU of the IAB donor 405 and / or may configure one or more IAB nodes 410 (e.g., a mobile terminal (MT) and / or a DU of an IAB node 410) connected to the core network via the IAB donor 405. Therefore, the CU of the IAB donor 405 may control and / or configure the entire IAB network connected to the core network via the IAB donor 405, such as by using a control message and / or a configuration message (e.g., a radio resource control (RRC) configuration message or an F1 application protocol (F1-AP) message). In some aspects, the link between the CU and the DU may be referred to as an F1 interface.
[0074] like Figure 4As further shown, the IAB network may include IAB nodes 410 (shown as IAB-node 1, IAB-node 2, and IAB-node 3) connected to the core network via an IAB donor 405. As shown, the IAB node 410 may include an MT function (sometimes also referred to as a UE function (UEF)) and may include a DU function (sometimes also referred to as an access node function (ANF)). The MT function of an IAB node 410 (e.g., a child node) may be controlled and / or scheduled by another IAB node 410 (e.g., a parent node of the child node) and / or by an IAB donor 405. The DU function of an IAB node 410 (e.g., a parent node) may control and / or schedule other IAB nodes 410 (e.g., a child node of the parent node) and / or UE 120. Therefore, the DU may be referred to as a scheduling node or a scheduling component, and the MT may be referred to as a scheduled node or a scheduled component. In some aspects, the IAB donor 405 may include a DU function but not an MT function. That is, the IAB donor 405 may configure, control and / or schedule the communication of the IAB node 410 and / or the UE 120. The UE 120 may include only the MT function and not the DU function. That is, the communication of the UE 120 may be controlled and / or scheduled by the IAB donor 405 and / or the IAB node 410 (e.g., the parent node of the UE 120).
[0075] When a first node controls and / or schedules communications for a second node (e.g., when the first node provides a DU function for the MT function of the second node), the first node may be referred to as the parent node of the second node, and the second node may be referred to as the child node of the first node. The child node of the second node may be referred to as the grandchild node of the first node. Thus, the DU function of the parent node may control and / or schedule communications for the child node of the parent node. The parent node may be an IAB donor 405 or an IAB node 410, and the child node may be an IAB node 410 or a UE 120. Communications of the MT function of the child node may be controlled and / or scheduled by the parent node of the child node.
[0076] like Figure 4 As further shown, the link between the UE 120 (e.g., which has only MT functionality but not DU functionality) and the IAB donor 405, or between the UE 120 and the IAB node 410, may be referred to as an access link 415. The access link 415 may be a wireless access link that provides the UE 120 with radio access to the core network via the IAB donor 405 and, optionally, via one or more IAB nodes 410. Thus, Figure 4 The network illustrated in may be referred to as a multi-hop network or a wireless multi-hop network. In some aspects, the access link 415 between the UE 120 and the IAB donor 405 or between the UE 120 and the IAB node 410 may be referred to as a Uu interface.
[0077] like Figure 4 As further shown, the link between the IAB donor 405 and the IAB node 410 or between two IAB nodes 410 may be referred to as a backhaul link 420, and is sometimes referred to as an Xn interface. The backhaul link 420 may be a wireless backhaul link that provides radio access to the core network to the IAB node 410 via the IAB donor 405 and optionally via one or more other IAB nodes 410. In the IAB network, network resources (e.g., time resources, frequency resources, and / or space resources) for wireless communication may be shared between the access link 415 and the backhaul link 420. In some aspects, the backhaul link 420 may be a primary backhaul link or an auxiliary backhaul link (e.g., a backup backhaul link). In some aspects, if the primary backhaul link fails, becomes congested and / or becomes overloaded, etc., the auxiliary backhaul link may be used. For example, if the primary backhaul link between the IAB node 2 and the IAB node 1 fails, the backup link 425 between the IAB node 2 and the IAB node 3 may be used for backhaul communication. As used herein, a node or wireless node may refer to an IAB donor 405 or an IAB node 410. In some aspects, in conjunction with Figure 4 One or more of the network nodes described (e.g., one or more of a CU node (e.g., IAB donor 405 or similar node), a DU node (e.g., IAB donor 405, IAB node 410 or similar node), an MT node (e.g., IAB node 410 or similar node)) may be capable of operating in a full-duplex mode, wherein one or more of the network nodes simultaneously transmits downlink signals and receives uplink signals. Aspects of full-duplex operation are described below in conjunction with Figure 5 A to Figure 5 D describes in more detail.
[0078] As indicated above, Figure 4 Other examples can be found in the Figure 4 The examples described are different.
[0079] Figure 55 is a diagram illustrating an example disaggregated base station architecture 500 according to the present disclosure. The disaggregated base station architecture 500 may include a CU 510 that may communicate directly with a core network 520 via a backhaul link, or indirectly with the core network 520 through one or more disaggregated control units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 525 via an E2 link, or a non-real-time (non-RT) RIC 515 associated with a service management and orchestration (SMO) framework 505, or both. The CU 510 may communicate with one or more DUs 530 via respective midhaul links, such as via an F1 interface. Each of the DUs 530 may communicate with one or more RUs 540 via respective fronthaul links. Each of the RUs 540 may communicate with one or more UEs 120 via respective RF access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 540.
[0080] Each unit in the unit (including CU 510, DU 530, RU 540) and near-RT RIC 525, non-RT RIC515 and SMO framework 505) may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or send signals, data or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit in the unit or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more units in the other units via a transmission medium. In some examples, each unit in the unit may include a wired interface and a wireless interface, the wired interface is configured to receive signals or send signals to one or more units in the other units through a wired transmission medium, and the wireless interface may include a receiver, a transmitter or a transceiver (such as an RF transceiver), which is configured to receive signals or send signals to one or more units in the other units through a wireless transmission medium, or both.
[0081] In some aspects, the CU 510 may host one or more higher layer control functions. Such control functions may include RRC functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by the CU 510. The CU 510 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 510 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, the CU 510 may be implemented to communicate with the DU 530 for network control and signaling.
[0082] Each DU 530 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 540. In some aspects, the DU 530 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, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 530 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 530 or with control functions hosted by the CU 510.
[0083] Each RU 540 may implement lower layer functionality. In some deployments, the RU 540 controlled by the DU 530 may correspond to a logical node that hosts radio frequency (RF) processing functions or low PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc., based at least in part on functional splitting (e.g., functional splitting defined by 3GPP), such as lower layer functional splitting. In this architecture, each RU 540 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 540 may be controlled by the corresponding DU 530. In some scenarios, this configuration may enable each DU 530 and CU 510 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).
[0084] The SMO framework 505 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 505 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 505 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 590) 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 510, DU 530, RU 540, non-RT RIC 515, and near-RTRIC 525. In some specific implementations, the SMO framework 505 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 511, via the O1 interface. Additionally, in some implementations, the SMO framework 505 can communicate directly with each of the one or more RUs 540 via a corresponding O1 interface. The SMO framework 505 can also include a non-RT RIC 515 configured to support the functionality of the SMO framework 505.
[0085] The non-RT RIC 515 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 525. The non-RT RIC 515 may be coupled to or in communication with the near-RT RIC 525 (such as via an A1 interface). The near-RT RIC 525 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 510, one or more DUs 530, or both, and the O-eNB with the near-RT RIC 525.
[0086] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 525, the non-RT RIC 515 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 525 and may be received from a non-network data source or from a network function at the SMO framework 505 or the non-RT RIC 515. In some examples, the non-RT RIC 515 or the near-RT RIC 525 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 515 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 505 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).
[0087] As indicated above, Figure 5 Other examples can be found in the Figure 5 The examples described are different.
[0088] FIG. 6A to FIG. 6D600, 610, 620, 630 are diagrams illustrating examples of full-duplex (FD) communication according to the present disclosure. FD communication is a communication that uses overlapping time resources at a single node (such as a UE or a base station) to transmit and receive. For example, the UE or base station may use the same time resources, such as via frequency division multiplexing (FDM) or space division multiplexing (SDM) to perform transmission and reception. "FDM" refers to performing two or more communications using different frequency resource allocations. "SDM" refers to performing two or more communications using different spatial parameters (such as different transmit configuration indicators (TCI) states corresponding to beams). SDM communication may use overlapping time resources and frequency resources, and FDM communication may use overlapping time resources and spatial resources (i.e., overlapping beam parameters, TCI states, etc.). The TCI state indicates the spatial parameters used for communication. For example, the TCI state used for communication may identify a source signal (such as a synchronization signal block, a channel state information reference signal, etc.) and a spatial parameter to be derived from the source signal for the purpose of transmitting or receiving communication. For example, the TCI state may indicate a quasi-co-location (QCL) type. The QCL type may indicate one or more spatial parameters to be derived from the source signal. The source signal may be referred to as a QCL source. FD communications may include dynamic services (such as scheduled by downlink control information (DCI)) and / or semi-static services. Semi-static services are services associated with semi-persistent resources (such as resources configured by semi-persistent scheduling (SPS) or configured grants (CG)).
[0089] Fig. 6A Example 600 includes UE1 602 and two network nodes (e.g., TRPs) 604-1, 604-2, where UE1 602 is transmitting uplink transmissions to network node 604-1 and receiving downlink transmissions from network node 604-2. In some aspects, the network node 604 (sometimes referred to as a network node) described in conjunction with FIG. 6 may be a base station (e.g., in conjunction with Figure 1 and Figure 2 The base station 110 and / or the combination Figure 3 one of the base stations 310, 335, 345), a TRP associated with (eg, managed by) a base station or other network node, and Figure 4 In some aspects, the UE 602 described in conjunction with FIG. 6 may be a UE 602 that is configured to provide a plurality of IABs to the user. Figure 1 , Figure 2 and Figure 4 The UE120, combined with Figure 3 One of the UEs 320, 355, or a similar UE. Fig. 6AIn the example 600 of , FD is enabled for UE1 602 but not for network nodes 604-1, 604-2. Therefore, network nodes 604-1 and 604-2 are half-duplex (HD) network nodes.
[0090] Figure 6B Example 610 includes two UEs (UE1 602-1 and UE2 602-2), a network node 604-1, and a network node 604-2. UE1 602-1 is receiving a downlink transmission from the network node 604-1, and UE2 602-2 is sending an uplink transmission to the network node 604-1. Figure 6B In example 610, FD is enabled for network node 604-1 but not for UE1 602-1 and UE2 602-2. Therefore, UE1 602-1 and UE2 602-2 are half-duplex UEs.
[0091] Figure 6C Example 620 includes UE1 602 and network node 604, where UE1 602 is receiving downlink transmissions from network node 604 and UE1 602 is sending uplink transmissions to network node 604. Figure 6C In example 620, FD is enabled for both UE1 602 and network node 604. Figure 6C In example 620, UE1 602 and network node 604 communicate using a beam pair. The beam pair may include a downlink beam and an uplink beam. For example, UE1 602 may communicate with network node 604 using a beam pair including a downlink beam at UE1 602 (i.e., a receive beam) and an uplink beam at UE1 602 (i.e., a transmit beam). Network node 604 may use a downlink beam at network node 604 (i.e., a transmit beam) to send communications received via the downlink beam of UE1 602, and may use an uplink beam at network node 604 (i.e., a receive beam) to receive communications sent via the uplink beam of UE1 602.
[0092] Figure 6C Example 630 includes a base station 110 and a cell (such as in combination with Figure 1 The two network nodes 604-1 and 604-2 associated with the cell 102 are shown in FIG. The network nodes 604-1 and 604-2 may be co-located (e.g., located at the same device, such as at the base station 110 or other device), or may be non-co-located (e.g., located separately from each other and / or from the base station 110, and thus may be independent devices).
[0093] exist FIG. 6A to FIG. 6DIn FIG. 6 , interference is indicated by a dashed line. Interference may occur between network nodes of examples 600 , 610 , 620 , 630 (referred to as CLI). Fig. 6A In , the downlink transmission of network node 604-2 interferes with the uplink transmission of network node 604-1. Figure 6B In the example, the uplink reception of network node 604-1 may be interfered by the transmission from network node 604-2. The CLI between network nodes 604 is referred to herein as inter-network node CLI. Figure 6B In some examples, the uplink transmission of UE2 602-2 may interfere with the downlink transmission of UE1 602-1 (not shown). Fig.6D In the example, the uplink transmission of UE2 602-2 interferes with the downlink transmission of UE1 602-1. In some cases, self-interference may occur. Self-interference occurs when the transmission of a node interferes with the receiving operation of the node. For example, self-interference may occur due to the reception of radiated energy from the transmitting antenna by the receiving antenna, crosstalk between components, etc. Figure 6C Examples of self-interference at UE 602 (from uplink transmission to downlink reception) and at network node 604 (from downlink transmission to uplink reception) are shown in FIG. It should be noted that the above-described CLI and self-interference conditions may occur in both HD and FD deployments.
[0094] A network node (e.g., one of network devices 604) operating in FD mode may yield certain benefits, such as reduced latency due to downlink transmissions being able to be sent in uplink time slots, etc., as well as enhanced spectral efficiency, more efficient resource utilization, and coverage enhancement. Figure 6B The detection of the CLI measurement reference signal (RS) may be important for FD operation because the network node may be interfered by other network nodes, thereby affecting the operation of the network node. The technology described herein provides the configuration of the sending window and receiving window for CLI measurement reference signal (RS) transmission and measurement between network nodes. In the FD network node (such as Figure 6B At network node 604-1), the send window may not overlap with the receive window, as described in more detail below.
[0095] As indicated above, FIG. 6A to FIG. 6D Provided as one or more examples. Other examples may be related to FIG. 6A to FIG. 6D The examples described are different.
[0096] Figure 7700 is a diagram illustrating the configuration and signaling of a synchronization signal block (SSB) between half-duplex IAB nodes according to the present disclosure. As shown, example 700 includes an IAB donor 705 (e.g., IAB donor 405) and IAB nodes 715 and 720 (e.g., IAB node 410). In addition, example 700 includes a UE (e.g., UE 120). In a given column of the table of example 700, the horizontal dimension represents time. The rows in the table correspond to DU functions, MT functions, or UE functions of the corresponding entities 705, 715, 720 or UE.
[0097] SSBs may be used for detection of IAB donors and / or nodes, such as for initial access (such as by a UE), configuration or implementation of an IAB network, discovery of IAB nodes, and network node-to-node CLI measurements. An SSB transmission configuration (STC) may indicate a configuration for a network node (such as an IAB donor 705 or an IAB node 715 or 720) to transmit an SSB. For example, the STC may indicate an SSB center frequency, an SSB subcarrier spacing, an SSB transmission periodicity, an SSB transmission timing offset (which may be in half-frames in some examples), an index of one or more SSBs to be transmitted, and a physical cell identifier associated with the STC.
[0098] A network node (e.g., IAB node 715 or 720, or UE) may monitor or measure an SSB based at least in part on an SSB-based radio resource monitoring measurement timing configuration (SMTC). The SMTC may indicate a window in which the network node is to monitor or measure an SSB. Such a window is referred to herein as a receive window. The SMTC may indicate a periodicity associated with the receive window, a timing offset associated with the SMTC window, a duration associated with the SMTC window, a set of physical cell identifiers to be measured, and / or one or more SSBs to be measured (e.g., an index of an SSB).
[0099] In example 700, as shown by reference numeral 725, the IAB donor 705 and the IAB nodes 715 and 720 may transmit SSBs (according to STCs) that may be monitored by the UE (according to SMTCs). For example, the DUs of the IAB donor 705 and the IAB nodes 715 and 720 may be configured to transmit SSBs. As shown by reference numeral 730, the IAB donor 705 and the IAB nodes 715 and 720 may transmit SSBs (according to corresponding STCs) for IAB node detection. For example, the DUs of the IAB donor 705 and the IAB nodes 715 and 720 may be configured to transmit SSBs. The MTs of the IAB nodes 715 and 720 may be configured to monitor SSBs according to one or more SMTCs. For example, up to four SSB transmission times may be configured for the transmission of SSBs for IAB node detection or measurement. Such constraints may create difficulties in dense cell deployments because a CU (eg, IAB donor 705) may have to configure STCs for cells in a large area without initially knowing which cells are within range of each other.
[0100] An IAB STC (e.g., an STC associated with an IAB node or an IAB donor) may be configured at a DU of an IAB node or a DU of an IAB donor for measurement by an MT of an IAB node (e.g., an MT of an adjacent IAB node). The IAB STC may be different from those STCs used for initial access by a UE. The IAB STC information element may include STC information (e.g., STC) of a DU of an IAB node or a DU of an IAB donor. An adjacent IAB node MT may perform discovery and measurement of a DU of an IAB node or a DU of an IAB donor based at least in part on an SSB sent in an STC window identified by the STC information. For example, an IAB node MT may perform discovery and measurement in an SMTC window corresponding to an STC window of a DU, wherein the STC window is identified by the STC information. There may be up to 5 STC configurations. This may include 1 STC configuration for access (such as by a UE) and 4 STC configurations for backhaul (such as for discovery or CLI measurement of an IAB donor and / or node). The STC information may be sent from the CU of the IAB donor to the DU of the IAB node or the DU of the IAB donor via the F1 interface. For example, the IAB information of the CU of the IAB donor may be sent as the IAB STC information. The STC information may also be transmitted from the DU of the IAB node or the DU of the IAB donor to the CU of the IAB donor, via the F1 SETUP REQUEST to the serving cell information element to the IAB information IAB-DU element to the IAB STC information.
[0101] In some examples, an SMTC information element (e.g., an SSB-MTC3-r16 information element) may be used to instruct an MT of an IAB node to measure an adjacent IAB node DU or an IAB donor DU SSB transmission. For example, the information element may be different from the information element used for UE initial access. If an SMTC list exists, for cells indicated in the pci-List parameter in each SSB-MTC3 element of the SMTC list in the same MeasObjectNR, the MT of the IAB node may establish an additional synchronization signal (SS) block measurement timing configuration (also abbreviated as SMTC) according to the received periodicityAndOffset parameter in each SSB-MTC3 configuration (such as using the same conditions as smtc1 to identify the system frame number and subframe for the SMTC opportunity), and may use the duration and ssb-ToMeasure parameters from each SSB-MTC3 configuration.
[0102] In some aspects, a network node (such as one or more of the network nodes or central network entities described herein) may be configured for remote interference management (RIM). RIM may involve the transmission of RS on RIM transmission resources. RIM transmission resources (which may be referred to as transmission windows in this article) may be defined by timing, frequency position, and sequence within a RIM RS cycle. A network node may be assigned one or more base station set identifiers, each of which is mapped to a RIM resource. The timing may be defined as the last X symbols before the end of the downlink transmission, where X is the RS duration. Code division multiplexing (CDM) RS may be configured in the same timing. A central network entity such as OAM may configure a receiving window (sometimes referred to as a RIM receiving timing or monitoring window) per network node. The central network entity may activate or deactivate monitoring of one or more receiving windows. There may be no requirement that the receiving window and the transmitting window do not overlap in time. For example, the monitoring timing may be allowed to overlap in time with the RIM transmission resource, which may be problematic for the FD network node.
[0103] As indicated above, Figure 7 Other examples can be found in the Figure 7 The examples described are different.
[0104] The above techniques may have certain limitations for network nodes operating in FD mode. For example, RIM-based configuration may not enforce that the receive window and the transmit window do not overlap, which may lead to self-interference of CLI measurements between network nodes. As another example, the techniques described above for configuration of CLI measurements based on IAB donor / node SSB (e.g., in conjunction with Figure 7The above) is constrained to 4 transmission times, which may not be sufficient in dense deployments. Therefore, conventional techniques for CLI measurement between network nodes may cause self-interference (thereby degrading the quality of CLI measurement) or may be constrained such that they are not sufficient for dense network deployments.
[0105] Figure 8 800 is a diagram illustrating an example of configuration of a sending window and a receiving window for CLI measurement RS transmission and measurement between network nodes (e.g., between gNBs) according to the present disclosure. The techniques and apparatus described herein enable configuration of separate sending windows and receiving windows for a network node group. The sending window of the network node group is shown by reference numeral 805. The receiving window of a single network node (exemplified as network node 1) in the network node group is shown by reference numeral 810. It can be seen that the sending window 815 of network node 1 does not overlap with any receiving window of network node 1. Therefore, self-interference at network node 1 is avoided, which improves the accuracy of CLI measurement.
[0106] As further shown in the figure, N network nodes may be included in the network node group. Each network node may be configured with a corresponding sending window. Network node 1 may be configured with multiple receiving windows. Each sending window may be associated with a corresponding receiving window in the multiple receiving windows, because each sending window overlaps with a receiving window in the multiple receiving windows.
[0107] As shown by reference numeral 820, each transmit window may be separated by a certain length of time. In example 800, there are Y ms between each transmit window. In some aspects, the start of a first transmit window may be separated from the start of a next transmit window by Y ms. Y may be configurable, as described in more detail elsewhere herein. In addition, the transmit window of a given network node may be associated with a period indicated by reference numeral 825.
[0108] Reference numeral 830 shows a granular view of resources (e.g., in some examples, symbols) of a send window and a receive window. A send window of network node 3 and an associated receive window of network node 1 are shown. CLI measurement RS send resources are shown as dot fills. Symbols associated with the reception of CLI measurement RS are shown as square patterned fills. Symbols associated with other communications such as control communications are shown as diamond hatch fills. The protection period for network node 3 to prepare for the transmission of CLI measurement RS and return to the transmission of other communications is shown by white fill on each side of the CLI measurement RS send resource. As shown by reference numeral 835, in example 800, network node 3 uses the same beam for transmission on each CLI measurement RS transmit resource in the send window. For example, for a periodic send window, the network node may use a beam for transmission at each opportunity in the send window according to a first configuration (e.g., where the first opportunity of the send window uses a different beam than the second opportunity of the send window). In some other aspects, the network node 3 may use multiple beams for transmission (such as using a different beam on each CLI measurement RS transmission resource, or using a first beam on a first CLI measurement RS transmission resource group and a second beam on a second CLI measurement RS transmission resource group). Transmission or reception using multiple beams in a single window (e.g., a transmission window or a reception window) is referred to herein as beam sweeping. For example, the network node may use beam sweeping to transmit in one or more transmission windows.
[0109] As shown, there are 10 symbols for CLI measurement RS detection within the receive window. The number of symbols used for CLI measurement RS detection within a given receive window may be configurable. In some aspects, the network node 1 may perform beam scanning in the receive window. For example, the network node 1 may generate a plurality of different receive beams within the receive window (such as generating a different beam on each resource associated with the reception of the CLI measurement RS, or generating a first beam on a first resource group associated with the reception of the CLI measurement RS and generating a second beam on a second resource group associated with the reception of the CLI measurement RS). Therefore, the network node may use beam scanning in a specific receive window to receive reference signaling. In some aspects, if the send window uses beam scanning for a resource group, the corresponding receive window may use a single beam for the resource group. In some aspects, if the send window uses a single beam for a resource group, the corresponding receive window may use beam scanning for the resource group. In some aspects, a periodic receive window may use a beam at each occasion of the receive window to receive reference signaling (wherein a first occasion of the receive window may be associated with a different beam than a beam associated with a second occasion of the receive window).
[0110] The arrangement shown in example 800 may provide reduced overhead relative to some other arrangements, such as the arrangement shown in example 700. For example, if N=7, Y=100 ms, there are 64 SSB (e.g., CLI measurement RS) beams per network node, and if there is 1 transmit beam per transmit window and 1 receive beam per receive window, then example 800 may be associated with an overhead of N x slot duration / Y=0.88%. The full SSB beam scan delay may be calculated as Y x 64^2 (since there are 64 transmit beams and 64 receive beams), which may be equal to a delay of 6.8 minutes.
[0111] As indicated above, Figure 8 Other examples can be found in the Figure 8 The examples described are different.
[0112] Fig. 9 1 is a diagram illustrating an example 900 of signaling associated with configuration of a sending window and a receiving window for CLI measurement reference signaling between network nodes according to the present disclosure. As shown, the example 900 includes a central network entity 905 (e.g., a base station 110, a network controller 130, a base station 310, an anchor base station 335, a non-anchor base station 345, an IAB donor 405, a CU 510, a DU 530, an RU 540, a network node 604) and a network node group including network nodes (e.g., a base station 110, a base station 310, a non-anchor base station 345, an IAB node 410, an MT function of an IAB node 410 or a base station 110, a DU function of an IAB node 410 or a base station 110, a DU 530, a network node 604). For clarity, the description of the example 900 focuses on the above-mentioned network nodes so that the signaling between the network node group and the central network entity 905 can be clearly explained with reference to a single network node. It should be understood that signaling described as between a network node and the central network entity 905 may also occur between any other network node in the group of network nodes and the central network entity 905. For example, the operations described with respect to example 900 may be performed by any network node in the group of network nodes.
[0113] The description of example 900 relates to "CLI measurement reference signaling between network nodes". "CLI measurement reference signaling between network nodes" includes sending one or more reference signals in a sending window. "Receiving CLI measurement reference signaling between network nodes" includes monitoring (e.g., determining whether a reference signal is received), measuring (e.g., determining interference measurement), or receiving one or more reference signals in resources of a receiving window. In some aspects, the one or more reference signals may include one or more SSBs. In some aspects, the one or more reference signals may include reference signals other than SSBs.
[0114] As used herein, "network node" may refer to an IAB node, a DU, a base station, a TRP, an RU, etc. In addition, "network node" may be used to refer to a cell provided by a network node. For example, the techniques described herein may be used to configure a first configuration and a second configuration for a cell of a network node, and to perform reference signaling and reception of reference signaling. For example, reference numeral 910 may relate to configuration of a first configuration of a cell. Reference numeral 920 may relate to configuration of a second configuration of a cell. Reference numeral 930 may relate to activation or deactivation of a first configuration or a second configuration of a cell. Reference numerals 940 and 950 may relate to sending or receiving reference signaling by a cell.
[0115] As indicated by reference numeral 910, the central network entity 905 may configure the first configuration to the network node. For example, the central network entity 905 may send (e.g., directly or via a radio unit) configuration information indicating the first configuration to the network node. In some aspects, the central network entity 905 may send the first configuration via RRC signaling, MAC signaling, an F1 interface, etc. In some aspects, the first configuration may be based at least in part on information provided by the network node. For example, the network node may send information indicating one or more parameters of the first configuration to the central network entity 905. In such examples, the central network entity 905 may generate the first configuration based at least in part on the one or more parameters.
[0116] The first configuration may indicate one or more sending windows for CLI measurement reference signaling between network nodes. "One or more sending windows" may refer to periodic sending windows, or to a single instance of a sending window. For example, a "sending window" may be a periodic sending window with multiple opportunities. As another example, a "sending window" may be a single opportunity of a set of sending windows that occur periodically.
[0117] The first configuration may indicate a parameter set. In some aspects, the parameter set may indicate the duration of the send window. For example, the duration may be expressed according to resources (such as the number of symbols, the number of time slots, etc.). In some aspects, the parameter set may indicate the periodicity of the send window. For example, the parameter set may indicate the period in which the send window (or multiple send windows) appears. In some aspects, the parameter set may indicate the time offset associated with the send window. For example, the parameter set may indicate the time offset relative to the reference time, and the send window (for example, each opportunity of the send window) may be located at least in part based on the time offset. In some aspects, the parameter set may indicate the frequency position associated with the send window. For example, the parameter set may indicate the frequency position parameter center frequency of the send window, the subcarrier associated with the send window, the resource block associated with the send window, the subchannel associated with the send window, the resource pool associated with the send window, etc.
[0118] In some aspects, a parameter set may indicate a reference signal resource of a transmission window. An example of how to indicate a reference signal resource is described below. For example, a parameter set may indicate a reference signal resource identifier associated with a reference signal resource, such as an SSB index. In some aspects, a parameter set may indicate a time and frequency position of a reference signal resource, such as a start and length indicator value or one or more frequency position parameters of the frequency position parameters described above. In some aspects, a parameter set may indicate a sequence identifier of a reference signal resource. For example, a parameter set may indicate a sequence for generating a network node inter-CLI measurement reference signal transmitted on a reference signal resource. In some aspects, a parameter set may indicate a subcarrier spacing of a reference signal resource, such as information using a parameter set index or another form of indicating a subcarrier spacing. In some aspects, a parameter set may indicate transmit beam information associated with a reference signal resource. For example, a parameter set may indicate quasi-co-location information associated with a reference signal resource, such as a source reference signal, quasi-co-location parameters (e.g., Doppler spread, Doppler shift, spatial transmission parameters, spatial reception parameters, etc.), SSB index, etc. In some examples, the transmit beam information may indicate a set of SSB indices corresponding to a set of transmit beams for a transmit window (e.g., the network node will transmit 4 CLI measurement RS resources in a transmit window with the same transmit beam as the transmit beams for SSB #5, 10, 15, and 20 for the network node). In some aspects, a parameter set may indicate a power parameter associated with a reference signal resource. For example, a parameter set may indicate an absolute power value, or may indicate an offset relative to another power parameter (such as a transmit power parameter for an SSB or a physical downlink shared channel). In some aspects, a parameter set may indicate repetition information associated with a reference signal resource. For example, a parameter set may indicate the number of reference signal resources (e.g., adjacent reference signal resources) or reference signal resource groups to have the same transmit beam, the same sequence identifier, the same subcarrier spacing, a phase continuity condition (e.g., so that each reference signal resource in the reference signal resource can be received using the same phase determination, which can be based at least in part on a phase tracking reference signal), or a combination thereof.
[0119] In some aspects, the parameter set may be the same for each transmit window configured for the network node (e.g., each opportunity of a periodic transmit window, or each transmit window of a plurality of transmit windows of a periodic configuration of a transmit window). In some other aspects, the parameter set may be different across transmit windows. For example, the parameter set may be based at least in part on a mode (e.g., using a first transmit beam set in a first transmit window, using a second transmit beam set in a second transmit window, using a first transmit beam set in a third transmit window, using a second transmit beam set in a fourth transmit window, and so on).
[0120] In some aspects, the parameter set may be explicitly signaled to the network node, such as to a gNB-DU of the network node. Additionally or alternatively, the network node may determine one or more parameters in the parameter set. For example, the network node (e.g., the gNB-DU) may implicitly derive one or more parameters based at least in part on a rule (e.g., the reference signal resources and identifiers may be derived from a cell identifier associated with the reference signal transmitting network node). Thus, the network node may determine one or more parameters implicitly indicated by information associated with the network node.
[0121] As shown by reference numeral 920, the central network entity 905 may configure the second configuration to the network node. For example, the central network entity 905 may send (e.g., directly or via a radio unit) configuration information indicating the second configuration to the network node. In some aspects, the central network entity 905 may send the second configuration via RRC signaling, MAC signaling, an F1 interface, etc. In some aspects, the second configuration may be based at least in part on information provided by the network node. For example, the network node may send information indicating one or more parameters of the second configuration to the central network entity 905. In such examples, the central network entity 905 may generate the second configuration based at least in part on the one or more parameters.
[0122] The second configuration may indicate one or more receive windows for inter-network node CLI measurement reference signaling. "One or more receive windows" may refer to a periodic receive window, or a single instance of a receive window. For example, a "receive window" may be a periodic receive window with multiple opportunities. As another example, a "receive window" may be a single opportunity of a set of periodically occurring receive windows.
[0123] The second configuration may indicate a parameter set. In some aspects, the parameter set may indicate the duration of the receiving window. For example, the duration may be expressed according to resources (such as the number of symbols, the number of time slots, etc.). In some aspects, the parameter set may indicate the periodicity of the receiving window. For example, the parameter set may indicate the period in which the receiving window (or multiple receiving windows) appears. In some aspects, the parameter set may indicate the time offset associated with the receiving window. For example, the parameter set may indicate the time offset relative to the reference time, and the receiving window (for example, each opportunity of the receiving window) may be located at least in part based on the time offset. In some aspects, the parameter set may indicate the frequency position associated with the receiving window. For example, the parameter set may indicate the frequency position parameter center frequency of the receiving window, the subcarrier associated with the receiving window, the resource block associated with the receiving window, the subchannel associated with the receiving window, the resource pool associated with the receiving window, etc.
[0124] In some aspects, the parameter set may indicate one or more RS sequence identifiers associated with the network node inter-CLI measurement reference signaling in the receive window. For example, the parameter set may indicate a set of RS sequence identifiers that the network node is to measure in the transmit window, which may reduce the sequence detection error rate. In some aspects, the parameter set may indicate one or more parameters associated with the RS sequence identifier in the one or more RS sequence identifiers. For example, the parameter set may indicate one or more parameters associated with each RS sequence identifier in the one or more RS sequence identifiers. In some aspects, one or more parameters for an RS sequence identifier may indicate a transmitter identifier associated with the reference signal sequence identifier (e.g., a transmitting cell identifier, a gNB-DU identifier, etc.), resources associated with the reference signal sequence identifier (such as the number of RS resources, the time position of the resources, the frequency position of the resources, etc., where the time position and the frequency position are described elsewhere herein), receive beam information associated with the reference signal sequence identifier (wherein the receive beam information may include a source reference signal, quasi-co-location parameters (e.g., Doppler spread, Doppler shift, spatial transmit parameters, spatial receive parameters, etc.), SSB index, etc.), transmit power associated with the reference signal sequence identifier (such as absolute transmit power or transmit power offset), or repetition information associated with the reference signal sequence identifier. Thus, the central network entity 905 may provide parameters associated with receiving inter-network node CLI measurement reference signaling, which enables the network nodes to efficiently receive and / or measure such reference signaling, thereby improving the accuracy of CLI measurements and improving network communications.
[0125] In some aspects, the parameter set may be the same for each receive window configured for the network node (e.g., each opportunity of a periodic receive window, or each receive window in a plurality of receive windows of a periodic configuration of receive windows). In some other aspects, the parameter set may be different across receive windows. For example, the parameter set may be based at least in part on a mode (e.g., using a first receive beam set in a first receive window, using a second receive beam set in a second receive window, using a first receive beam set in a third receive window, using a second receive beam set in a fourth receive window, and so on).
[0126] In some aspects, a set of parameters associated with one or more receive windows may be explicitly signaled to a network node, such as to a gNB-DU of the network node. Additionally or alternatively, the network node may determine one or more parameters in the set of parameters. For example, the network node (e.g., the gNB-DU) may implicitly derive the one or more parameters based at least in part on a rule (e.g., deriving a transmitting cell identifier of a transmitting network node associated with the receive window from a reference signal position and identifier). Thus, the network node may determine one or more parameters implicitly indicated by information associated with the network node.
[0127] As above combined Figure 8 As described, the central network entity 905 may configure the sending window and receiving window of the network node group so that the sending window and receiving window at a given network node do not overlap with each other. For example, the central network entity 905 may configure one or more sending windows and multiple receiving windows to the first network node. Each receiving window in the multiple receiving windows may be associated with a corresponding network node in the network node group. The central network entity 905 may configure a receiving window that overlaps with one or more sending windows (e.g., one sending window in the one or more sending windows, or the opportunity of a periodic sending window in the one or more sending windows) in time to the second network node. For example, the central network node may configure a receiving window that overlaps with one or more sending windows of the first network node in time for each network node other than the first network node in the network node group. For example, in the case where there are three network nodes, the central network node may configure the sending window of the first network node, the first receiving window of the second network node may be configured to overlap with the sending window, and the second receiving window of the third network node may be configured to overlap with the sending window. Therefore, the first receiving window and the second receiving window are associated with the first network node at least in part based on the first network node having a sending window that overlaps with the first receiving window and the second window.
[0128] In some aspects, a network node i in a group of N network nodes may be configured with a send window i by a first configuration. Network node i may also be configured with a receive window [1 ... i-1, i+1 ... n] by a second configuration (because network node i is not configured with a receive window that overlaps with send window i). Each receive window in the receive window [1 ... i-1, i+1 ... n] may overlap with a send window [1 ... i-1, i+1 ... n] in a corresponding network node [1 ... i-1, i+1 ... n]. It should be noted that i may be any value between 1 and n and including both.
[0129] In some aspects, the central network entity 905 may provide (e.g., directly or via a radio unit) signaling to activate or deactivate the first configuration or the second configuration, as shown by reference numeral 930. For example, the signaling may include RRC signaling, MAC signaling, F1 signaling, etc. In some aspects, the central network entity 905 may configure a plurality of first configurations or a plurality of second configurations, and may activate or deactivate a first configuration or a second configuration selected from the plurality of first configurations or the plurality of second configurations.
[0130] As indicated by reference numeral 940, the network node may send inter-network node CLI measurement reference signaling according to the first configuration. For example, the network node may send one or more reference signals (e.g., SSB and / or another form of RS) in one or more transmission windows according to the parameter set indicated by the first configuration.
[0131] As indicated by reference numeral 950, the network node may receive inter-network node CLI measurement reference signaling according to the second configuration. For example, the network node may measure or monitor one or more reference signals (e.g., SSB and / or another form of RS) in one or more reception windows according to the parameter set indicated by the first configuration. Thus, the FD network node may perform inter-network node CLI measurements without causing self-interference at the FD network node, which improves the efficiency of CLI measurements and inter-gNB communications.
[0132] As indicated above, Fig. 9 Other examples can be found in the Fig. 9 The examples described are different.
[0133] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a central network entity according to the present disclosure. The example process 1000 is an example of a central network entity (e.g., base station 110, network controller 130, base station 310, anchor base station 335, non-anchor base station 345, IAB donor 405, CU 510, DU 530, RU 540, network device 604, central network entity 905) performing operations associated with non-overlapping CLI measurement reference signal transmission and reception windows.
[0134] like Fig.10 As shown, in some aspects, process 1000 may include: configuring a first configuration for a network node indicating one or more transmission windows for CLI measurement reference signaling between network nodes (block 1010). For example, a central network entity (e.g., using Fig.12The depicted communication manager 140 and / or configuration component 1208) may configure a first configuration for a network node indicating one or more transmission windows for inter-network node CLI measurement reference signaling, as described above. In some aspects, a central network entity may transmit the first configuration. For example, the central network entity may provide the first configuration for a radio unit to transmit.
[0135] like Fig.10 As further shown, in some aspects, process 1000 may include: configuring, for a network node, a second configuration indicating a plurality of receive windows for inter-network node CLI measurement reference signaling, wherein the one or more transmit windows are configured to not overlap with each of the plurality of receive windows (block 1020). For example, a central network entity (e.g., using Fig.12 The depicted communication manager 140 and / or configuration component 1208) may configure a second configuration for the network node indicating a plurality of receive windows for inter-network node CLI measurement reference signaling, wherein the one or more transmit windows are configured to not overlap with each of the plurality of receive windows, as described above. In some aspects, the central network entity may transmit the second configuration. For example, the central network entity may provide the second configuration for the radio unit to transmit.
[0136] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0137] In a first aspect, each receive window of a plurality of receive windows is associated with a respective network node of a plurality of network nodes comprising the network node.
[0138] In a second aspect, alone or in combination with the first aspect, the network node is a first network node, and wherein the method further comprises configuring a specific receive window for the second network node that temporally overlaps with one or more transmit windows of the first network node.
[0139] In a third aspect, alone or in combination with one or more of the first and second aspects, the network node is a first network node, and wherein the method further comprises: configuring, for each network node of the plurality of network nodes other than the first network node, a receiving window that temporally overlaps with one or more sending windows of the first network node.
[0140] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a specific receive window of the plurality of receive windows is associated with the corresponding network node based at least in part on the corresponding network node having a transmit window overlapping with the specific receive window.
[0141] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, one or more transmission windows are periodic, and wherein the first configuration indicates the use of a beam to transmit CLI measurement reference signaling between network nodes at each opportunity in the one or more transmission windows.
[0142] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, a first opportunity of one or more transmission windows is associated with a beam different from a beam associated with a second opportunity of one or more transmission windows.
[0143] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the first configuration indicates that inter-network node CLI measurement reference signaling is sent using beam scanning in one or more sending windows.
[0144] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the second configuration indicates that inter-network node CLI measurement reference signaling is received using beam scanning in a specific receiving window of multiple receiving windows.
[0145] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, a specific reception window among the multiple reception windows is periodic, and wherein the second configuration indicates the use of a beam at each opportunity in the specific reception window to receive inter-network node CLI measurement reference signaling.
[0146] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, a first occasion of a particular receive window is associated with a beam different from a beam associated with a second occasion of the particular receive window.
[0147] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 1000 includes: the duration of the sending window, the periodicity of the sending window, the time offset associated with the sending window, the frequency position associated with the sending window, the reference signal resource of the sending window, the time and frequency position of the reference signal resource, the sequence identifier of the reference signal resource, the subcarrier spacing of the reference signal resource, the transmit beam information associated with the reference signal resource, the power parameter associated with the reference signal resource, or the information associated with the reference signal resource.
[0148] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the parameter set is different for a first occasion of the sending window than for a second occasion of the sending window.
[0149] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the parameter set is explicitly indicated by configuration signaling.
[0150] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, at least one parameter in the parameter set is implicitly indicated by information associated with the network node.
[0151] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the process 1000 includes: activating or deactivating inter-network node CLI measurement reference signaling according to a first configuration.
[0152] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the second configuration includes a set of parameters for a receive window indication in multiple receive windows, including at least one of: the duration of the receive window, the periodicity of the receive window, the time offset associated with the receive window, the frequency position associated with the receive window, one or more reference signal sequence identifiers associated with the network node inter-CLI measurement reference signaling in the receive window, or one or more parameters associated with a reference signal sequence identifier among the one or more reference signal sequence identifiers.
[0153] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the one or more parameters include at least one of: a transmitter identifier associated with a reference signal sequence identifier, a resource associated with a reference signal sequence identifier, receive beam information associated with a reference signal sequence identifier, a transmit power associated with a reference signal sequence identifier, or information associated with a reference signal sequence identifier.
[0154] In an eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, the parameter set is different for a first occasion of the receive window than for a second occasion of the receive window.
[0155] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the parameter set is explicitly indicated by configuration signaling.
[0156] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, at least one parameter in the parameter set is implicitly indicated by information associated with the network node.
[0157] In a twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, process 1000 includes activating or deactivating reception of inter-network node CLI measurement reference signaling according to a second configuration.
[0158] In a twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, configuring the first configuration further comprises sending the first configuration, and configuring the second configuration further comprises sending the second configuration.
[0159] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more blocks of the blocks of process 1000 may be executed in parallel.
[0160] Fig.11 1 is a diagram illustrating an example process 1100 performed, for example, by a network node according to the present disclosure. The example process 1100 is an example of a network node (e.g., base station 110, base station 310, non-anchor base station 345, IAB node 410, MT function of IAB node 410 or base station 110, DU function of IAB node 410 or base station 110, DU 530, network device 604) performing operations associated with non-overlapping CLI measurement reference signal transmission and reception windows.
[0161] like Fig.11 As shown, in some aspects, process 1100 may include receiving a first configuration indicating one or more transmission windows for CLI measurement reference signaling between network nodes (block 1110). For example, a network node (e.g., using Fig.13 The depicted communications manager 150 and / or receiving component 1302) can receive a first configuration indicating one or more transmission windows for inter-network node CLI measurement reference signaling, as described above.
[0162] like Fig.11 As further shown, in some aspects, process 1100 may include receiving a second configuration indicating one or more receive windows for inter-network node CLI measurement reference signaling, wherein the one or more transmit windows are configured to not overlap with each of the one or more receive windows (block 1120). Fig.13 The depicted communications manager 150 and / or receiving component 1302) may receive a second configuration indicating one or more receive windows for inter-network node CLI measurement reference signaling, wherein the one or more transmit windows are configured to not overlap with each of the one or more receive windows, as described above.
[0163] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0164] In a first aspect, the one or more transmission windows are periodic, and wherein the first configuration indicates that one beam is used to transmit inter-network node CLI measurement reference signaling at each opportunity of the one or more transmission windows.
[0165] In a second aspect, either alone or in combination with the first aspect, a first opportunity of the one or more transmit windows is associated with a beam different from a beam associated with a second opportunity of the one or more transmit windows.
[0166] In a third aspect, alone or in combination with one or more of the first and second aspects, the first configuration indicates that inter-network node CLI measurement reference signaling is sent using beam scanning in one or more sending windows.
[0167] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the second configuration indicates that the inter-network node CLI measurement reference signaling is received using beam scanning in a specific receiving window of the one or more receiving windows.
[0168] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a specific reception window among the one or more reception windows is periodic, and wherein the second configuration indicates the use of a beam to receive inter-network node CLI measurement reference signaling at each opportunity in the specific reception window.
[0169] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, a first opportunity of a particular receive window is associated with a beam different from a beam associated with a second opportunity of the particular receive window.
[0170] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1100 includes: duration of a transmit window, periodicity of the transmit window, a time offset associated with the transmit window, a frequency position associated with the transmit window, a reference signal resource of the transmit window, a time and frequency position of the reference signal resource, a sequence identifier of the reference signal resource, a subcarrier spacing of the reference signal resource, transmit beam information associated with the reference signal resource, a power parameter associated with the reference signal resource, or information associated with the reference signal resource.
[0171] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the parameter set is different for a first occasion of the sending window than for a second occasion of the sending window.
[0172] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, a parameter set is explicitly indicated by configuration signaling.
[0173] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, at least one parameter in the parameter set is implicitly indicated by information associated with the network node.
[0174] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 1100 includes: receiving a signal to activate or deactivate CLI measurement reference signaling between network nodes according to a first configuration; and sending CLI measurement reference signaling between network nodes based at least in part on the first configuration.
[0175] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the second configuration indicates a set of parameters for a receive window in one or more receive windows, the set of parameters comprising at least one of: the duration of the receive window, the periodicity of the receive window, the time offset associated with the receive window, the frequency position associated with the receive window, one or more reference signal sequence identifiers associated with the network node inter-CLI measurement reference signaling in the receive window, or one or more parameters associated with a reference signal sequence identifier in one or more reference signal sequence identifiers.
[0176] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the one or more parameters include at least one of the following: a transmitter identifier associated with a reference signal sequence identifier, a resource associated with a reference signal sequence identifier, receive beam information associated with a reference signal sequence identifier, a transmit power associated with a reference signal sequence identifier, or information associated with a reference signal sequence identifier.
[0177] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the parameter set is different for a first occasion of the receive window than for a second occasion of the receive window.
[0178] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the parameter set is explicitly indicated by configuration signaling.
[0179] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, at least one parameter in the parameter set is implicitly indicated by information associated with the network node.
[0180] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 1100 includes: receiving signaling for activating or deactivating CLI measurement reference signaling between network nodes according to a second configuration; and receiving CLI measurement reference signaling between network nodes based at least in part on the second configuration.
[0181] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, process 1100 includes: sending CLI measurement reference signaling between network nodes according to a first configuration; or receiving CLI measurement reference signaling between network nodes according to a second configuration.
[0182] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.
[0183] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a central network entity, or a central network entity may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and sending component 1204. As further shown, apparatus 1200 may include a communication manager 140. Communication manager 140 may include one or more of configuration component 1208, etc.
[0184] In some aspects, the apparatus 1200 may be configured to perform Figures 3 to 9 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein (such as Fig.10 In some aspects, Fig.12 The device 1200 and / or one or more components shown may include a combination of Figure 2 One or more components of the central network entity. Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.
[0185] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network entity.
[0186] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the central network entity. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.
[0187] The configuration component 1208 or the sending component 1204 can configure a first configuration for the network node indicating one or more sending windows for inter-network node CLI measurement reference signaling. The configuration component 1208 or the sending component 1204 can configure a second configuration for the network node indicating multiple receiving windows for inter-network node CLI measurement reference signaling, wherein the one or more sending windows are configured to not overlap with each of the multiple receiving windows.
[0188] Configuration component 1208 can activate or deactivate inter-network node CLI measurement reference signaling according to the first configuration.
[0189] Configuration component 1208 can activate or deactivate reception of inter-network node CLI measurement reference signaling according to the second configuration.
[0190] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The component set (one or more components) shown may be described as being executable by Fig.12 Another component shown may be a collection of components that perform one or more functions.
[0191] Fig.13 1 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network node, or a network node may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and transmitting component 1304. As further shown, apparatus 1300 may include a communication manager 150. Communication manager 150 may include measurement component 1308, among other things.
[0192] In some aspects, the apparatus 1300 may be configured to perform Figures 3 to 9 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more of the processes described herein (such as Fig.11 In some aspects, Fig.13 The device 1300 and / or one or more components shown may include a combination of Figure 2 One or more components of the network node. Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.
[0193] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network node.
[0194] The transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1306. In some aspects, one or more other components of the device 1300 may generate communications and may provide the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1306. In some aspects, the transmitting component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network node. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.
[0195] The receiving component 1302 may receive a first configuration indicating one or more transmit windows for inter-network node CLI measurement reference signaling. The receiving component 1302 may receive a second configuration indicating one or more receive windows for inter-network node CLI measurement reference signaling, wherein the one or more transmit windows are configured to be non-overlapping with each of the one or more receive windows.
[0196] The receiving component 1302 can receive a signal to activate or deactivate inter-network node CLI measurement reference signaling according to a first configuration, and send inter-network node CLI measurement reference signaling based at least in part on the first configuration.
[0197] The receiving component 1302 can receive signaling to activate or deactivate reception of inter-network node CLI measurement reference signaling according to a second configuration, and the inter-network node CLI measurement reference signaling is received based at least in part on the second configuration.
[0198] The sending component 1304 can send inter-network node CLI measurement reference signaling according to the first configuration.
[0199] The CLI measurement component 1308 can receive inter-network node CLI measurement reference signaling according to the second configuration.
[0200] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The component set (one or more components) shown may be described as being executable by Fig.13 Another component shown may be a collection of components that perform one or more functions.
[0201] The following provides an overview of some aspects of the disclosure:
[0202] Aspect 1: A method of wireless communication performed by a central network entity, comprising: configuring a first configuration for a network node indicating one or more sending windows for cross-link interference (CLI) measurement reference signaling between network nodes; and configuring a second configuration for the network node indicating multiple receiving windows for CLI measurement reference signaling between network nodes, wherein the one or more sending windows are configured to not overlap with each of the multiple receiving windows.
[0203] Aspect 2: The method according to aspect 1, wherein each of the plurality of receiving windows is associated with a corresponding network node among a plurality of network nodes including the network node.
[0204] Aspect 3: The method according to aspect 2, wherein the network node is a first network node, and wherein the method further comprises: configuring a specific receiving window for the second network node that temporally overlaps with the one or more sending windows of the first network node.
[0205] Aspect 4: A method according to Aspect 2, wherein the network node is a first network node, and wherein the method further comprises: configuring a receiving window for each of the multiple network nodes except the first network node that temporally overlaps with the one or more sending windows of the first network node.
[0206] Aspect 5: The method according to aspect 2, wherein a specific receive window among the plurality of receive windows is associated with the corresponding network node based at least in part on the corresponding network node having a transmit window that overlaps with the specific receive window.
[0207] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the one or more sending windows are periodic, and wherein the first configuration indicates the use of a beam to send the inter-network node CLI measurement reference signaling at each opportunity in the one or more sending windows.
[0208] Aspect 7: The method according to aspect 6, wherein a first opportunity of the one or more transmission windows is associated with a beam different from a beam associated with a second opportunity of the one or more transmission windows.
[0209] Aspect 8: The method according to any one of aspects 1 to 7, wherein the first configuration indicates the use of beam scanning to send the inter-network node CLI measurement reference signaling in the one or more sending windows.
[0210] Aspect 9: The method according to any one of aspects 1 to 8, wherein the second configuration indicates that the inter-network node CLI measurement reference signaling is received using beam scanning in a specific reception window among the multiple reception windows.
[0211] Aspect 10: A method according to any one of Aspects 1 to 9, wherein a specific receiving window among the multiple receiving windows is periodic, and wherein the second configuration indicates using a beam to receive the inter-network node CLI measurement reference signaling at each opportunity in the specific receiving window.
[0212] Aspect 11: The method according to aspect 10, wherein the first opportunity of the specific reception window is associated with a beam different from the beam associated with the second opportunity of the specific reception window.
[0213] Aspect 12: A method according to any one of Aspects 1 to 10, wherein for a sending window in the one or more sending windows, the first configuration indication includes a set of parameters of at least one of the following: the duration of the sending window, the periodicity of the sending window, the time offset associated with the sending window, the frequency position associated with the sending window, the reference signal resource of the sending window, the time and frequency position of the reference signal resource, the sequence identifier of the reference signal resource, the subcarrier spacing of the reference signal resource, the sending beam information associated with the reference signal resource, the power parameter associated with the reference signal resource, or the repetition information associated with the reference signal resource.
[0214] Aspect 13: The method according to aspect 12, wherein the parameter set for a first occasion of the sending window is different from that for a second occasion of the sending window.
[0215] Aspect 14: The method according to Aspect 12, wherein the parameter set is explicitly indicated by configuration signaling.
[0216] Aspect 15: The method according to aspect 12, wherein at least one parameter in the parameter set is implicitly indicated by information associated with the network node.
[0217] Aspect 16: The method according to any one of Aspects 1 to 15 further includes: activating or deactivating inter-network node CLI measurement reference signaling according to the first configuration.
[0218] Aspect 17: A method according to any one of Aspects 1 to 16, wherein the second configuration indicates a receive window in the multiple receive windows and includes a parameter set of at least one of the following: the duration of the receive window, the periodicity of the receive window, the time offset associated with the receive window, the frequency position associated with the receive window, one or more reference signal sequence identifiers associated with the network node inter-CLI measurement reference signaling in the receive window, or one or more parameters associated with a reference signal sequence identifier among the one or more reference signal sequence identifiers.
[0219] Aspect 18: A method according to Aspect 17, wherein the one or more parameters include at least one of the following: a transmitter identifier associated with the reference signal sequence identifier, a resource associated with the reference signal sequence identifier, receive beam information associated with the reference signal sequence identifier, a transmit power associated with the reference signal sequence identifier, or repetition information associated with the reference signal sequence identifier.
[0220] Aspect 19: The method according to aspect 17, wherein the parameter set for a first occasion of the receiving window is different from that for a second occasion of the receiving window.
[0221] Aspect 20: The method according to Aspect 17, wherein the parameter set is explicitly indicated by configuration signaling.
[0222] Aspect 21: The method according to aspect 17, wherein at least one parameter in the parameter set is implicitly indicated by information associated with the network node.
[0223] Aspect 22: The method according to any one of Aspects 1 to 21, further comprising: activating or deactivating reception of the inter-network node CLI measurement reference signaling according to the second configuration.
[0224] Aspect 23: A method of wireless communication performed by a network node, comprising: receiving a first configuration indicating one or more sending windows for cross-link interference (CLI) measurement reference signaling between network nodes; and receiving a second configuration indicating one or more receiving windows for CLI measurement reference signaling between network nodes, wherein the one or more sending windows are configured to not overlap with each of the one or more receiving windows.
[0225] Aspect 24: The method according to Aspect 23, wherein the one or more sending windows are periodic, and wherein the first configuration indicates that the inter-network node CLI measurement reference signaling is sent using one beam at each opportunity of the one or more sending windows.
[0226] Aspect 25: The method according to aspect 24, wherein a first opportunity of the one or more transmission windows is associated with a beam different from a beam associated with a second opportunity of the one or more transmission windows.
[0227] Aspect 26: The method according to aspect 24, wherein the first configuration indicates the use of beam scanning to send the inter-network node CLI measurement reference signaling in the one or more sending windows.
[0228] Aspect 27: The method according to any one of Aspects 23 to 26, wherein the second configuration indicates that the inter-network node CLI measurement reference signaling is received using beam scanning in a specific reception window among the one or more reception windows.
[0229] Aspect 28: A method according to any one of Aspects 23 to 27, wherein a specific receiving window among the one or more receiving windows is periodic, and wherein the second configuration indicates using a beam to receive the inter-network node CLI measurement reference signaling at each opportunity in the specific receiving window.
[0230] Aspect 29: The method according to aspect 28, wherein the first occasion of the specific reception window is associated with a beam different from the beam associated with the second occasion of the specific reception window.
[0231] Aspect 30: A method according to any one of Aspects 23 to 29, wherein, for a sending window in the one or more sending windows, the first configuration indication includes a set of parameters of at least one of the following: the duration of the sending window, the periodicity of the sending window, the time offset associated with the sending window, the frequency position associated with the sending window, the reference signal resource of the sending window, the time and frequency position of the reference signal resource, the sequence identifier of the reference signal resource, the subcarrier spacing of the reference signal resource, the sending beam information associated with the reference signal resource, the power parameter associated with the reference signal resource, or the repetition information associated with the reference signal resource.
[0232] Aspect 31: The method according to aspect 30, wherein the parameter set for a first occasion of the sending window is different from that for a second occasion of the sending window.
[0233] Aspect 32: The method according to Aspect 30, wherein the parameter set is explicitly indicated by configuration signaling.
[0234] Aspect 33: The method according to aspect 30, wherein at least one parameter in the parameter set is implicitly indicated by information associated with the network node.
[0235] Aspect 34: The method according to any one of Aspects 23 to 33 further includes: receiving a signal for activating or deactivating CLI measurement reference signaling between network nodes according to the first configuration; and sending CLI measurement reference signaling between network nodes based at least in part on the first configuration.
[0236] Aspect 35: A method according to any one of Aspects 23 to 34, wherein the second configuration indicates a receive window in the one or more receive windows and includes a set of parameters of at least one of: the duration of the receive window, the periodicity of the receive window, the time offset associated with the receive window, the frequency position associated with the receive window, one or more reference signal sequence identifiers associated with the inter-network node CLI measurement reference signaling in the receive window, or one or more parameters associated with a reference signal sequence identifier among the one or more reference signal sequence identifiers.
[0237] Aspect 36: A method according to Aspect 35, wherein the one or more parameters include at least one of the following: a transmitter identifier associated with the reference signal sequence identifier, a resource associated with the reference signal sequence identifier, receive beam information associated with the reference signal sequence identifier, a transmit power associated with the reference signal sequence identifier, or repetition information associated with the reference signal sequence identifier.
[0238] Aspect 37: The method according to aspect 35, wherein the parameter set for a first occasion of the receiving window is different from that for a second occasion of the receiving window.
[0239] Aspect 38: The method according to Aspect 35, wherein the parameter set is explicitly indicated by configuration signaling.
[0240] Aspect 39: The method according to aspect 35, wherein at least one parameter in the parameter set is implicitly indicated by information associated with the network node.
[0241] Aspect 40: The method according to any one of Aspects 23 to 39 further includes: receiving signaling for activating or deactivating reception of the CLI measurement reference signaling between network nodes according to the second configuration; and receiving CLI measurement reference signaling between network nodes based at least in part on the second configuration.
[0242] Aspect 41: The method according to any one of Aspects 23 to 40 further includes: sending CLI measurement reference signaling between network nodes according to the first configuration; or receiving CLI measurement reference signaling between network nodes according to the second configuration.
[0243] Aspect 42: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 41.
[0244] Aspect 43: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 41.
[0245] Aspect 44: An apparatus for wireless communication, comprising: at least one means for performing the method according to one or more of aspects 1 to 41.
[0246] Aspect 45: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 41.
[0247] Aspect 46: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 41.
[0248] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.
[0249] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads implemented, procedures and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be clear that the systems and / or methods described herein can be implemented by different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.
[0250] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.
[0251] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).
[0252] Any element, action or instruction used herein should not be interpreted as critical or necessary unless clearly described as such. Moreover, as used herein, the articles "one" and "a kind of" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").
Claims
1. An apparatus for wireless communication at a central network entity, comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to cause the central network entity to: configuring, for a network node, a first configuration indicating one or more transmission windows for cross-link interference (CLI) measurement reference signaling between network nodes; and A second configuration indicating a plurality of receiving windows for inter-network node CLI measurement reference signaling is configured for the network node, wherein the one or more sending windows are configured to not overlap with each of the plurality of receiving windows.
2. The apparatus of claim 1 , wherein to configure the first configuration, the one or more processors are configured to cause the central network entity to send the first configuration, and wherein to configure the second configuration, the one or more processors are configured to cause the central network entity to send the second configuration. 3 . The apparatus of claim 1 , wherein each of the plurality of receive windows is associated with a corresponding network node of a plurality of network nodes.
4. The apparatus of claim 3, wherein the network node is a first network node, and wherein the one or more processors are configured to cause the central network entity to: A specific receive window is configured for the second network node that overlaps in time with the one or more send windows of the first network node.
5. The apparatus of claim 3, wherein the network node is a first network node, and wherein the one or more processors are configured to cause the central network entity to: A receiving window is configured for each of the plurality of network nodes except the first network node, which temporally overlaps with the one or more sending windows of the first network node.
6. The apparatus of claim 3, wherein a particular receive window of the plurality of receive windows is associated with the corresponding network node based at least in part on the corresponding network node having a transmit window that overlaps with the particular receive window.
7. The apparatus according to claim 1, wherein the one or more sending windows are periodic, and wherein the first configuration indicates that the inter-network node CLI measurement reference signaling is sent using one beam at each opportunity of the one or more sending windows.
8. The apparatus according to claim 1, wherein the first configuration indicates that the inter-network node CLI measurement reference signaling is sent using beam scanning in the one or more sending windows.
9. The apparatus according to claim 1, wherein the second configuration indicates that the inter-network node CLI measurement reference signaling is received using beam scanning in a specific reception window among the plurality of reception windows.
10. The apparatus according to claim 1, wherein a specific reception window among the plurality of reception windows is periodic, and wherein the second configuration indicates to use one beam to receive the inter-network node CLI measurement reference signaling at each opportunity in the specific reception window.
11. The apparatus according to claim 1, wherein, for a sending window in the one or more sending windows, the first configuration indication comprises a parameter set of at least one of the following: the duration of the send window, the periodicity of the sending window, a time offset associated with the send window, a frequency position associated with the transmit window, The reference signal resource of the sending window, The time and frequency position of the reference signal resource, a sequence identifier of the reference signal resource, the subcarrier spacing of the reference signal resources, transmit beam information associated with the reference signal resource, a power parameter associated with the reference signal resource, or repetition information associated with the reference signal resource.
12. The apparatus of claim 1, wherein the one or more processors are further configured to cause the central network entity to send signaling for activating or deactivating inter-network node CLI measurement reference signaling according to the first configuration.
13. The apparatus of claim 1 , wherein the second configuration indicates a parameter set comprising at least one of the following for a receive window in the plurality of receive windows: the duration of the receive window, the periodicity of the receive window, a time offset associated with the receive window, a frequency position associated with the receive window, one or more reference signal sequence identifiers associated with the inter-network node CLI measurement reference signaling in the reception window, or One or more parameters associated with a reference signal sequence identifier of the one or more reference signal sequence identifiers.
14. The apparatus of claim 13, wherein the one or more parameters include at least one of: a transmitter identifier associated with the reference signal sequence identifier, a resource associated with the reference signal sequence identifier, receive beam information associated with the reference signal sequence identifier, a transmit power associated with the reference signal sequence identifier, or repetition information associated with the reference signal sequence identifier.
15. The apparatus of claim 1, wherein the one or more processors are further configured to cause the central network entity to send signaling for activating or deactivating reception of inter-network node CLI measurement reference signaling according to the second configuration.
16. An apparatus for wireless communication at a network node, comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to cause the network node to: receiving a first configuration indicating one or more transmission windows for cross-link interference (CLI) measurement reference signaling between network nodes; as well as receiving a second configuration indicating one or more receive windows for inter-network node CLI measurement reference signaling, The one or more sending windows are configured to not overlap with each receiving window of the one or more receiving windows.
17. The apparatus according to claim 16, wherein the one or more sending windows are periodic, and wherein the first configuration indicates that the inter-network node CLI measurement reference signaling is sent using one beam at each opportunity of the one or more sending windows.
18. The apparatus according to claim 16, wherein the second configuration indicates that the inter-network node CLI measurement reference signaling is received using beam scanning in a specific receiving window among the one or more receiving windows.
19. The apparatus according to claim 16, wherein a specific receiving window among the one or more receiving windows is periodic, and wherein the second configuration indicates to use one beam to receive the inter-network node CLI measurement reference signaling at each opportunity in the specific receiving window.
20. The apparatus of claim 16, wherein the one or more processors are further configured to cause the network node to receive a signal to activate or deactivate inter-network node CLI measurement reference signaling according to the first configuration; and Inter-network node CLI measurement reference signaling is sent based at least in part on the first configuration.
21. The apparatus of claim 16, wherein the one or more processors are further configured to cause the network node to: Sending inter-network node CLI measurement reference signaling according to the first configuration; or Inter-network node CLI measurement reference signaling is received according to the second configuration.
22. A method of wireless communication performed by a central network entity, comprising: configuring, for a network node, a first configuration indicating one or more transmission windows for cross-link interference (CLI) measurement reference signaling between network nodes; as well as A second configuration indicating a plurality of receiving windows for inter-network node CLI measurement reference signaling is configured for the network node, wherein the one or more sending windows are configured to not overlap with each of the plurality of receiving windows.
23. The method of claim 22, wherein each of the plurality of receive windows is associated with a corresponding network node of a plurality of network nodes.
24. The method of claim 23, wherein the network node is a first network node, and wherein the method further comprises: A specific receive window is configured for the second network node that overlaps in time with the one or more send windows of the first network node.
25. The method of claim 23, wherein the network node is a first network node, and wherein the method further comprises: A receiving window is configured for each of the plurality of network nodes except the first network node, which temporally overlaps with the one or more sending windows of the first network node.
26. The method of claim 23, wherein a particular receive window of the plurality of receive windows is associated with the corresponding network node based at least in part on the corresponding network node having a transmit window that overlaps with the particular receive window.
27. A method of wireless communication performed by a network node, comprising: receiving a first configuration indicating one or more transmission windows for cross-link interference (CLI) measurement reference signaling between network nodes; as well as A second configuration indicating one or more receive windows for inter-network node CLI measurement reference signaling is received, wherein the one or more transmit windows are configured to not overlap with each of the one or more receive windows.
28. The method according to claim 27, wherein the one or more sending windows are periodic, and wherein the first configuration indicates that the inter-network node CLI measurement reference signaling is sent using one beam at each opportunity of the one or more sending windows.
29. The method of claim 28, wherein a first opportunity of the one or more transmit windows is associated with a beam that is different from a beam associated with a second opportunity of the one or more transmit windows.
30. The method of claim 28, wherein the first configuration indicates that the inter-network node CLI measurement reference signaling is sent using beam scanning in the one or more sending windows.
