Network power saving modes associated with cross-link interference

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a first network entity may generate a message including information associated with a network energy saving (NES) mode of the first network entity, associated with timing of cross-link interference (CLI) measurement resources. The first network entity may send the message to a second network entity. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 377,170, filed on September 26, 2022, entitled “NETWORK ENERGY SAVINGS MODE ASSOCIATED WITH CROSS-LINK INTERFERENCE,” and U.S. Non-Provisional Patent Application No. 18 / 364,267, filed on August 2, 2023, entitled “NETWORK ENERGY SAVINGS MODE ASSOCIATED WITH CROSS-LINK INTERFERENCE,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communications and techniques and apparatus for messaging for network power saving modes associated with cross-link interference. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems employ multiple-access technologies that 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), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), time division synchronous code division multiple access (TD-SCDMA), 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 communication for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink and uplink communications. "Downlink" (or "DL") refers to the communication link from a base station to a UE, and "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables diverse UEs to communicate at the city, national, regional, and / or global levels. New Radio (NR), also 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 improving spectral efficiency, reducing costs, improving service, leveraging new spectrum, and integrating better with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink and 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. Furthermore, it supports beamforming, multiple-input, multiple-output (MIMO) antenna technology, and carrier aggregation. As demand for mobile broadband access continues to increase, further improvements to LTE, NR, and other radio access technologies remain essential. Summary of the Invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a first network entity. The method may include generating a message including information associated with timing of a cross-link interference (CLI) measurement resource and associated with a network energy saving (NES) mode of the first network entity. The method may include sending the message to a second network entity.

[0008] Some aspects described herein relate to a method of wireless communication performed by a second network entity. The method may include receiving a message including information associated with a timing of a CLI measurement resource and an NES mode of a first network entity. The method may include performing CLI measurements based at least in part on the information and an energy state of the second network entity.

[0009] Some aspects described herein relate to an apparatus for a first network entity for wireless communication. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or collectively, to generate a message including information associated with the timing of a CLI measurement resource and an NES mode of the first network entity. The one or more processors may be configured, individually or collectively, to send the message to a second network entity.

[0010] Some aspects described herein relate to an apparatus for a second network entity for wireless communication. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or collectively, to receive a message including information associated with a timing of a CLI measurement resource and an NES mode of a first network entity. The one or more processors may be configured, individually or collectively, to perform CLI measurements based, at least in part, on the information and an energy state of the second network entity.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a first network entity. The instruction set, when executed by one or more processors of the first network entity, may cause the first network entity to generate a message including information associated with the timing of a CLI measurement resource and an NES mode of the first network entity. The instruction set, when executed by the one or more processors of the first network entity, may cause the first network entity to send the message to a second network entity.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a second network entity. The set of instructions, when executed by one or more processors of the second network entity, may cause the second network entity to receive a message including information associated with a timing of a CLI measurement resource and an NES mode of a first network entity. The set of instructions, when executed by the one or more processors of the second network entity, may cause the second network entity to perform CLI measurements based at least in part on the information and an energy state of the second network entity.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for generating a message including information associated with timing of CLI measurement resources and associated with a network access mode (NES) mode of the apparatus. The apparatus may include means for sending the message to another apparatus.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a message including information associated with a timing of a CLI measurement resource and an NES mode of another apparatus. The apparatus may include means for performing CLI measurements based at least in part on the information and an energy state of the apparatus.

[0015] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the drawings and description.

[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the following detailed description may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for achieving the same purposes 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 figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations of the claims.

[0017] While various aspects are described in this disclosure through illustration of certain examples, those skilled in the art will appreciate that such aspects can be implemented in many different arrangements and scenarios. The techniques 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 non-module-based devices (e.g., end-user devices, vehicles, communications devices, computing devices, industrial equipment, retail / shopping devices, medical devices, 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. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The various aspects described herein are intended to be practiced in a wide variety of 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 enable a detailed understanding of the above-described features of the present disclosure, a more particular description, briefly summarized above, may be obtained by reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to 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 network entity (eg, 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 decomposed base station according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of using a transmission inactivity period according to the present disclosure.

[0023] Figures 5A to 5C is a diagram illustrating an example of full-duplex communication according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of a full-duplex communication mode according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of transmitting information associated with a network entity network energy saving (NES) mode according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example of exchanging information about an NES mode according to the present disclosure.

[0027] Figure 9 is a diagram illustrating an example of NES pattern information associated with a cross-link interference measurement resource according to the present disclosure.

[0028] Figure 10 is a diagram illustrating an example process performed, for example, by a first network entity according to the present disclosure.

[0029] Figure 11 is a diagram illustrating an example process performed, for example, by a second network entity according to the present disclosure.

[0030] Figure 12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0031] 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 scope of the present disclosure will be fully conveyed to those skilled in the art. It will be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is realized independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to realize a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0032] Several aspects of telecommunications systems will now be presented with reference to various devices and techniques. These devices and techniques are described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RATs, 4G RATs, and / or post-5G (e.g., 6G) RATs.

[0034] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. Wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. Wireless network 100 may include a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). Wireless network 100 may also include one or more network entities, such as base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and / or other network entities. Base station 110 is a network entity that communicates with UE 120. Base stations 110 (sometimes referred to as BSs) may include, for example, NR base stations, LTE base stations, entity Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, and / or transmit / receive points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving that coverage area, depending on the context in which the term is used.

[0035] Base stations 110 may provide communication coverage for macro cells, pico cells, femto cells, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A base station 110 used for a macro cell may be referred to as a macro base station. A base station 110 used for a pico cell may be referred to as a pico base station. A base station 110 used 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 macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (eg, three) cells.

[0036] In some examples, cells may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile base station 110 (e.g., a mobile base station). In some examples, base stations 110 may interconnect with each other and / or one or more other base stations 110 or network entities in wireless network 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0037] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a single device configured to perform one or more functions, such as those described herein with respect to base station 110. In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same or different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not another. In this manner, a single device may include more than one base station.

[0038] The wireless network 100 may include one or more relay stations. A relay station is a network entity that can receive transmissions of data from an upstream station (e.g., a network entity or UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or network entity). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in FIG, BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communications may be referred to as a relay station, relay base station, relay, etc.

[0039] The wireless network 100 may be a heterogeneous network having network entities including different types of BSs, 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 in communication with a set of network entities and may provide coordination and control for these network entities. The network controller 130 may communicate with the base station 110 via a backhaul communication link. The network entities may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link.

[0041] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UEs 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UEs 120 may be cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablet computers, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices, biometric devices, wearable devices (e.g., smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings or smart bracelets)), entertainment devices (e.g., music devices, video devices, and / or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, and / or any other suitable device configured to communicate via a wireless medium.

[0042] Some UEs 120 may be considered 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 network entity, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UE 120 may be included within 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, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0043] Generally speaking, 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. A RAT may be referred to as a radio technology, air interface, etc. A 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) can communicate directly (e.g., without using a network entity as an intermediary to communicate with each other) using one or more sidelink channels. For example, the UEs 120 can 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, the UEs 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0045] Devices in wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in wireless network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been identified as frequency ranges designated 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 (and interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with FR2, which is often (and interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being distinct from the extremely high frequency (EHF) band (30 GHz - 300 GHz), which is identified as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0047] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term can be broadly construed to mean frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly construed to mean frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies, may be within FR2, FR4, FR4-a, 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 first network entity (e.g., base station 110) may include a communications manager 150. As described in greater detail elsewhere herein, communications manager 150 may generate a message including information associated with timing of cross-link interference (CLI) measurement resources and associated with a network energy saving (NES) mode for the first network entity. Communications manager 150 may send the message to a second network entity. Additionally or alternatively, communications manager 150 may perform one or more other operations described herein.

[0049] In some aspects, the second network entity (e.g., base station 110) may include a communications manager 150. As described in greater detail elsewhere herein, communications manager 150 may receive a message including information associated with the timing of CLI measurement resources and an NES mode of the first network entity. Communications manager 150 may perform CLI measurements based at least in part on the information and the energy state of the second network entity. Additionally or alternatively, communications manager 150 may perform one or more other operations described herein.

[0050] As indicated above, Figure 1 are provided as examples. 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 communication between a network entity (e.g., base station 110) and a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1).

[0052] At base station 110, transmit processor 220 may receive data intended for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Base station 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. 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., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as 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 modems) (shown as modems 232a through 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 also process (e.g., convert to analog, amplify, filter, and / or frequency upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. Modems 232a through 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 through 234t).

[0053] At UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from 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 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 the 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 modem 254, perform MIMO detection on the received symbols if applicable, and 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 a data sink 260, and may provide decoded control information and system information to a 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, among other things, 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. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0054] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292 (eg, one or more memories). The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with network entities via the communication unit 294.

[0055] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 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. The antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or 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 UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from a controller / processor 280. 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 a TX MIMO processor 266, as applicable, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to a network entity. In some examples, the modem 254 of UE 120 may include a modulator and a demodulator. In some examples, the UE 120 may include 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 (eg, one or more memories) to perform operations described herein (eg, with reference to Figures 4 to 12 ) any aspects of any of the methods described.

[0057] At a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. The network entity may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. The network entity may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the network entity's modem 232 may include a modulator and a demodulator. In some examples, the network entity may include 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 herein (e.g., reference 240). Figures 4 to 12 ) any aspects of any of the methods described.

[0058] A controller / processor of a network entity (eg, controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2 Any other component of the may perform one or more techniques for indicating an NES mode associated with CLI measurements, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the may perform or direct e.g. Figure 10 The process of 1000 Figure 11 1100 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for the network entity and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing 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 the network entity and / or UE 120, may cause the one or more processors, UE 120, and / or the network entity to perform or direct, for example, Figure 10 The process of 1000 Figure 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, a first network entity (e.g., base station 110) includes means for generating (e.g., using controller / processor 240, memory 242) a message including information associated with the timing of CLI measurement resources and associated with the NES mode of the first network entity; and / or means for sending the message to a second network entity (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, memory 242). In some aspects, means for the first network entity to perform the operations described herein may include, for example, communications manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, scheduler 246, or any combination thereof.

[0060] In some aspects, the second network entity (e.g., base station 110) includes means for receiving a message including information associated with the timing of CLI measurement resources and the NES mode of the first network entity (e.g., using antenna 234, modem 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242); and / or means for performing CLI measurements based at least in part on the information and the energy state of the second network entity (e.g., using antenna 234, modem 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242). In some aspects, the means for the second network entity to perform the operations described herein may include, for example, the communications manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, memory 242, the scheduler 246, or any combination thereof.

[0061] In some aspects, a single processor may perform all of the functions described as being performed by the one or more processors. In some aspects, the one or more processors may collectively perform a set of functions. For example, a first set of processor(s) of the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of processor(s) of the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. References to "one or more processors" should be understood to refer to the combination Figure 2 Any one or more processors described. References to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as in conjunction with Figure 2 For example, functions described as being performed by one or more memories may be performed by the same subset of the one or more memories or by a different subset of the one or more memories.

[0062] Although Figure 2 The blocks in FIG. 2 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.

[0063] As indicated above, Figure 2are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0064] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

[0065] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality) can be implemented in a converged architecture or a disaggregated architecture. For example, a base station (such as a node B, an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a transport proxy (TRP), or a cell) can be implemented as a converged base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0066] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across 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 (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0067] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0068] The decomposed base station 300 architecture may include one or more CUs 310, which may communicate directly with the core network 320 via backhaul links or indirectly through one or more decomposed base station units (such as near-RT RTRICs 325 via E2 links, non-RT RTRICs 315 associated with the service management and orchestration (SMO) framework 305, or both). The CUs 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as the F1 interface. The DUs 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul, midhaul, and backhaul links may generally be referred to as "communication links." The RUs 340 may communicate with corresponding UEs 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. The DUs 330 and RUs 340 may also be referred to as "O-RAN DUs (O-DUs)" and "O-RAN RUs (O-RUs)," respectively. A network entity may include a CU, DU, RU, or any combination of CUs, DUs, and RUs. A network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CUs, DUs, and RUs. A network entity may also include a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, mobile station, sensor / actuator, other wireless device, or any combination thereof.

[0069] Each of the units (e.g., CU 310, DU 330, RU 340, as well as near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units, or an associated processor or controller that provides instructions to the communication interface of these units, may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface configured to receive or transmit signals to one or more of the other units via the wired transmission medium. Additionally, these units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or transmit signals, or both, to one or more of the other units over the wireless transmission medium.

[0070] In some aspects, the CU 310 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 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 units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0071] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of the following, at least in part according to a functional split (such as that defined by 3GPP): a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, the DU 330 may also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0072] Lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functionality or low-PHY layer functionality (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and CU 310 in a cloud-based RAN architecture, such as a vRAN architecture.

[0073] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 310, DU 330, RU 340, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0074] The non-RT RIC 315 can be configured to include logic that enables 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 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions via an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0075] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and employ AI / ML models to execute corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or by creating RAN management policies (such as A1 policies).

[0076] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0077] Figure 4 is a diagram illustrating an example 400 of using a transmission inactivity period according to the present disclosure.

[0078] While NR generally offers significant energy efficiency improvements per gigabyte over previous generations (e.g., LTE), new NR use cases requiring high data rates and / or the adoption of millimeter-wave frequencies may involve more network sites, greater network density, more network antennas, greater bandwidth, and / or more frequency bands. This could potentially result in a more efficient wireless network that still has higher energy requirements and / or generates more emissions than previous generations. Furthermore, energy accounts for a significant portion of the cost of operating a wireless network. For example, according to some estimates, energy costs are approximately one-quarter of the total cost of operating a wireless network, and over 90% of network operating costs are spent on energy (e.g., fuel and electricity). A significant portion of energy consumption and / or energy costs comes from powering the RAN, which accounts for approximately half of the energy consumed by the wireless network. Consequently, networks are being designed to be more energy-efficient and environmentally responsible. These designs may include the use of sleep states by network entities, where they occasionally power down radio components or other components (partially or completely) to reduce energy consumption.

[0079] In some aspects, a network entity may have the opportunity to enter NES mode. During NES mode, the network entity may reduce power consumption. The network entity may reduce power consumption by adapting transmission and / or reception in the time, frequency, spatial, and / or power domains using one or more techniques. This may include adjusting (e.g., reducing) transmit power, the number of antenna elements (and associated panels or transmit / receive units (TxRUs)) used, and / or the operating bandwidth. Beam selection may also be adjusted, such as by selecting narrower beams or disabling some beam directions. This reduction in transmit power may be part of entering a sleep state, in which the network entity enters a transmit-inactive state or a receive-inactive state. In contrast, an active or awake state may include processing (e.g., decoding and / or demodulating) downlink signals, uplink signals, and / or channels. The amount of power consumed by the network entity during the awake state may be scaled (increased or decreased) based at least in part on the number of component carriers (CCs), resource utilization, the number of antenna ports, the number of spatial layers, and / or the number of antenna elements.

[0080] Example 400 illustrates how a network entity can ramp down power from an active state to a sleep state and ramp back up again. As the time between active states increases, more components can be shut down (power down) to conserve more power, including radio components used for transmission and / or reception (radio components). For example, the network entity can shut down the radio frequency (RF) portion and / or the broadband portion of the transmit chain so that the network entity does not transmit any communications. Switching between a transmit (downlink) active state (transmitting) and a transmit inactive state (not transmitting) can represent a discontinuous transmission (DTX) mode of operation for the network entity. During the inactive transmission state, no downlink transmission occurs, and the network entity can enter a sleep state. During the active transmission state, downlink transmission is possible, and the network entity cannot enter a sleep state. Switching between a receive (uplink) active state (receiving) and a receive inactive state (not receiving) can represent a discontinuous reception (DRX) mode of operation for the network entity.

[0081] Network entities can reduce power by varying amounts. For example, sleep states can include different sleep levels, such as microsleep, light sleep, or deep sleep. Compared to the active state, microsleep allows the network entity to use a reduced amount of power for the radio. This power reduction can be significantly less than the power reduction of deep sleep (for example, the power reduction of deep sleep can be 14 times that of microsleep). However, microsleep can have a very short transition time (for example, less than 1 millisecond (ms)) and can use very little transition energy. Light sleep can be a sleep level between microsleep and deep sleep, with a power reduction of, for example, half that of deep sleep. Light sleep can have a slower transition time than microsleep (for example, 6 ms), but can still be faster than deep sleep. Light sleep can cause the network entity to use additional transition energy (relative power vs. ms), which can be approximately 20 times that of microsleep. Deep sleep can have the longest sleep period and / or the greatest energy reduction. Deep sleep may also have the longest transition time (eg, 20 ms) and cause the network entity to use the greatest amount of energy to transition (eg, approximately 100 times the transition energy of micro sleep).

[0082] In some aspects, the NES mode may also include an energy harvesting (EH) mode. In EH mode, the network entity may obtain energy from an alternative source other than the conventional power source. The alternative source may include renewable energy sources such as solar, vibration, or thermal energy.

[0083] As indicated above, Figure 4 are provided as examples. Other examples may be used with respect to Figure 4 The examples described are different.

[0084] Figures 5A to 5C is a diagram illustrating an example of full-duplex (FD) communication according to the present disclosure. Figure 5A The first full-duplex scenario 500 depicted in FIG includes UE1 502 and two base stations (eg, network entities or TRPs) 504-1, 504-2, where UE1 502 is transmitting uplink transmissions to base station 504-1 and receiving downlink transmissions from base station 504-2. Figure 5A In the first full-duplex scenario 500, FD is enabled for UE1 502 but not for base stations 504-1, 504-2. Figure 5B The second full-duplex scenario 510 depicted in FIG includes two UEs (shown as UE1 502-1 and UE2 502-2) and a base station 504, where UE1 502-1 is receiving downlink transmissions from the base station 504 and UE2 502-2 is sending uplink transmissions to the base station 504. In the second full-duplex scenario 510, FD is enabled for the base station 504, but is not enabled for UE1 502-1 and UE2 502-2. Figure 5C 5. A third full-duplex scenario 520 including UE1 502 and base station 504 is depicted in FIG, where UE1 502 is receiving downlink transmissions from base station 504 and UE1 502 is sending uplink transmissions to base station 504. In the third full-duplex scenario 520, FD is enabled for both UE1 502 and base station 504.

[0085] As indicated above, Figures 5A to 5C Provide some examples. Other examples can be found in the Figures 5A to 5C The examples described are different.

[0086] Figure 6 6 is a diagram illustrating an example of a full-duplex communication mode 600 according to the present disclosure. In a first mode 602, a first network entity (shown as BS1) and a second network entity (shown as BS2) may be full-duplex devices (e.g., may be capable of communicating in full-duplex). A first UE (shown as UE1) and a second UE (shown as UE2) may be half-duplex UEs (e.g., may not be capable of communicating in full-duplex). The first network entity may perform a downlink transmission to the first UE, and may receive an uplink transmission from the second UE at the first network entity. The first network entity may experience system information (SI) from downlink to uplink based at least in part on the downlink transmission to the first UE and the uplink transmission received from the second UE. The first network entity may experience CLI from the second network entity. CLI may also occur when network entities configure different time division duplex (TDD) uplink and downlink time slots for nearby UEs. For example, the first UE may experience CLI from the second network entity and the second UE. If a downlink symbol of a first UE collides with at least one uplink symbol of a second UE, the first UE may be considered a "victim UE" and the second UE may be considered an "aggressor UE."

[0087] In the second mode 604, the first network entity and the second network entity may be full-duplex devices. The first UE and the second UE may be full-duplex UEs. The first network entity may perform downlink transmissions to the first UE, and the first network entity may receive uplink transmissions from the first UE. The first UE may experience SI from uplink to downlink based at least in part on the downlink transmissions from the first network entity and the uplink transmissions to the first network entity. The first UE may experience CLI from the second network entity and the second UE. CLI may occur between two UEs on the same cell or different cells.

[0088] In a third mode 606, the first UE and the second UE may be full-duplex UEs and may communicate in a multiple TRP (multi-TRP) configuration. The first network entity may receive uplink transmissions from the first UE, and the second network entity may perform downlink transmissions to the first UE and the second UE. The first UE may experience SI from uplink to downlink based at least in part on the uplink transmissions to the first network entity and the downlink transmissions from the second network entity.

[0089] A victim UE may measure CLI from an aggressor UE. The aggressor UE may not transmit anything dedicated to CLI measurement by the victim UE and may not be aware of whether uplink transmissions are measured by the victim UE. If the network entity configures one or more CLI measurement resources for CLI measurement, the victim UE may measure CLI.

[0090] CLI measurements for a network entity's NES mode (e.g., power reduction, EH mode) may differ from CLI measurements for the network entity's non-NES mode (e.g., normal operating mode, non-power reduction, non-EH mode). During NES mode, the network entity may use less bandwidth (e.g., 5 MHz instead of 20 MHz) and lower transmit power than during non-NES mode. If CLI is measured during non-NES mode, the CLI measurement may be inaccurate when the network entity operates in NES mode. Similarly, if CLI is measured during NES mode, the CLI measurement may be inaccurate when the network entity operates in non-NES mode. Inaccurate CLI reporting can lead to inaccurate scheduling and transmit power adjustments, which may degrade communications with increased interference and waste power due to overpowered transmissions. Degraded communications waste power, processing resources, and signaling resources.

[0091] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0092] Figure 7 is a diagram illustrating example 700 of transmitting information associated with a network entity's NES mode according to the present disclosure. Example 700 illustrates a first network entity 710 (e.g., base station 110) and a second network entity 720 (e.g., base station 110) that can communicate with each other via a wireless network (e.g., wireless network 100). When network entity 720 is measuring CLI that affects its communications, network entity 720 can be considered a "victim" network entity, while network entity 710 can be considered an "aggressor" network entity that is transmitting and causing the CLI. Network entity 710 can transmit a CLI reference signal (CLI-RS) so that network entity 720 can measure the CLI.

[0093] According to various aspects described herein, network entity 710 may transmit a message containing information associated with the network entity's NES mode. The NES mode information may be associated with the timing of CLI measurement resources, including a transmit window or receive window for a CLI-RS or CLI opportunity used to measure CLI. Specifically, the information regarding the NES mode may correspond to when CLI measurements are performed, providing network entity 720 with information regarding whether network entity 710 is in NES mode or non-NES mode when CLI measurements are performed. This information may include transmit power status (e.g., downlink (DL) power backoff), the number of antenna elements or panels, the operating bandwidth for DL ​​and uplink (UL) communications, a subset of beam directions, a combination of information elements (e.g., a subset of beam directions with a specific power backoff at a subset of frequency resources within the operating bandwidth), and / or other information regarding the state of network entity 710 during NES mode. This information may also indicate an EH state and details regarding the EH state (e.g., duration, periodicity, energy harvesting rate, alternative power source). This information may indicate the full-duplex mode of the network entity 710, including whether the network entity 710 operates in half-duplex mode, full-duplex mode, or sub-band full-duplex mode (SBFD) mode (where subbands in different directions are frequency-division multiplexed in the same time slot). This information may indicate the uplink / downlink subband configuration, such as the uplink / downlink time slot mode.

[0094] The network entity 720 may measure CLI at the CLI measurement resource and send a CLI report based at least in part on the CLI measurement and information regarding the NES mode of the network entity 710. Because the network entity 710 provides NES mode information associated with the timing of the CLI measurements, the network entity 720 may provide more accurate CLI reports for different NES operating modes of the network entity 710. This improves communication and conserves power and signaling resources. In some aspects, the network entity 710 may perform CLI measurements during NES mode.

[0095] As indicated by reference numeral 725, the network entity 710 may generate the message. As indicated by reference numeral 730, the network entity 710 may send the message. In some aspects, the message may include a CLI measurement configuration that configures the network entity 720 to perform CLI measurements. The CLI measurement configuration may indicate a first set of CLI measurement resources (e.g., time and frequency resources, reference signals) for an NES mode of the network entity 710 and a second set of CLI measurement resources for a non-NES mode of the network entity 710.

[0096] Network entity 710 may send this message based at least in part on a triggering event (e.g., an energy level exceeding an energy threshold, a dynamic change in EH mode or NES mode). Network entity 710 may send this message via backhaul or over-the-air (OTA). If network entity 710 and network entity 720 belong to the same CU, F1 signaling may be used. If network entity 710 and network entity 720 belong to two CUs, F1 signaling or Xn signaling may be used. Network entity 710 may use a central coordinator for network entity 710 and network entity 720. Network entity 710 may use semi-static signaling (e.g., a semi-static switching mode for NES mode).

[0097] As indicated by reference numeral 735, the network entity 720 may perform CLI measurements based at least in part on the information in the message regarding the NES mode of the network entity 710. The network entity 720 may use different CLI measurement resources based at least in part on the NES mode of the network entity 710. If the network entity 720 is in the NES mode, the network entity 710 may use fewer, more, or different CLI measurement resources than when the network entity 710 is in a non-NES mode.

[0098] In some aspects, the network entity 720 may perform CLI measurements based at least in part on an energy state (e.g., NES operating mode, energy level, energy consumption level, energy harvesting level, energy consumption history) of the network entity 720. If the network entity 720 is in NES mode, the network entity 720 may not perform CLI measurements or may perform CLI measurements in a different manner.

[0099] As shown by reference numeral 740, the network entity 720 may transmit a CLI report indicating one or more of the CLI measurements. In some aspects, the CLI report may indicate the NES operating mode (NES mode or non-NES mode) of the network entity 710 for the CLI measurements included in the CLI report. The NES operating mode may be associated with the timing of the CLI measurements. One set of CLI measurements may be indicated as being performed during the NES mode of the network entity 710, and another set of CLI measurements may be indicated as being performed during the non-NES mode of the network entity 710.

[0100] In some aspects, the CLI report may indicate the operating mode of the network entity 720 (e.g., NES mode, non-NES mode, receive mode). That is, when measuring CLI, the network entity 720 may also operate in NES mode. The receive mode of the network entity 720 may include the network entity 720 operating in a different bandwidth for the NES mode or EH mode of the network entity 720 than for the non-NES mode or non-EH mode of the network entity 720. The network entity 720 may operate with a reduced number of antenna elements or antenna panels (e.g., turning off some antenna elements that affect beamforming) or with a subset of receive beams (e.g., measuring CLI in specific receive beams). The CLI report may indicate the energy status of the network entity 720 or other information, such as the reduced number of antenna elements, operating bandwidth, beam subset, or other information regarding the NES operating mode of the network entity 720 used for CLI measurement. The CLI report may indicate the full-duplex mode of the network entity 710 and / or the network entity 720 used for CLI measurement.

[0101] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0102] Figure 8 are diagrams illustrating examples 800 , 802 , 804 , and 806 of exchanging information regarding NES modes according to the present disclosure.

[0103] Network entity 710 may exchange information regarding the NES mode with network entity 720 in various ways. The information regarding the NES mode may be associated with a CLI measurement opportunity. Example 800 illustrates that network entity 710 (DU) is about to send a CLI-RS to network entity 720 (DU). Network entity 710 may send a message containing information regarding the NES mode of network entity 710 to a CU (CU1) of network entity 710. CU1 may send the message to a CU (CU2) of network entity 720 via the internet, cloud, or core network. CU2 may send the message to network entity 720 (DU). CU2 may also send a CLI measurement configuration (e.g., resource timing / frequency, metrics) to network entity 720. The information regarding the NES mode of network entity 710 may be sent within or along with the CLI measurement configuration.

[0104] Example 802 shows that network entity 710 can send the message to CU1 via the F1 interface. CU1 can send the message directly to CU2 via the Xn interface. CU2 can send the message to network entity 720 via the F1 interface. Similarly, network entity 720 can send a CLI report or another message with information about the NES mode of network entity 710 to network entity 720 via the CU and Xn interfaces.

[0105] Example 804 shows that network entity 710 and network entity 720 may share the same CU (CU1). Network entity 710 may send the message to network entity 720 via CU1. Network entity 720 may also send information to network entity 710 via CU1.

[0106] Example 806 shows a central coordinator for network entity 710 and network entity 720. CU1 can send the message to CU2 via the central coordinator. CU2 can also send information to CU1 via the central coordinator.

[0107] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0108] Figure 9 is a diagram illustrating an example 900 of NES mode information associated with CLI measurement resources according to the present disclosure.

[0109] In some aspects, network entity 720 (the victim) may perform CLI measurements based at least in part on the NES mode of network entity 710 (the aggressor). This may include when network entity 710 is in NES mode or non-NES mode. NES mode may include EH mode, and non-NES mode may include non-EH mode. Network entity 720 may receive a message (e.g., in a CLI measurement configuration) with information regarding the NES mode of network entity 710. Using this information, network entity 720 may perform CLI measurements based at least in part on the NES operating mode of network entity 710, whether the NES operating mode is NES mode or non-NES mode. That is, network entity 720 may perform NES-dependent measurements or EH-dependent measurements. There may be one CLI measurement for non-NES mode or non-EH mode and another CLI measurement for NES mode or EH mode.

[0110] The network entity 720 may use CLI measurement resources (e.g., time and frequency resources for CLI measurement opportunities, specific CLI-RSs) to perform CLI measurements. Example 900 illustrates a CLI-RS transmitted during EH mode and a CLI-RS transmitted during non-EH mode. The network entity 720 may record, for a CLI measurement of a CLI-RS, whether the CLI measurement was made during EH mode or non-EH mode of the network entity 710. The network entity 720 may use CLI measurement resources specific to EH mode and different CLI measurement resources specific to non-EH mode. By differentiating CLI-RSs based at least in part on EH mode, the network entity 720 may provide more accurate CLI reporting.

[0111] As indicated above, Figure 9 are provided as examples. Other examples can be found in the Figure 9 The examples described are different.

[0112] Figure 10 is a diagram illustrating an example process 1000 performed, for example, by a first network entity according to the present disclosure. Example process 1000 is an example in which a first network entity (eg, base station 110, network entity 710) performs operations associated with indicating an NES mode associated with CLI measurements.

[0113] like Figure 10 As shown in , in some aspects, process 1000 may include generating a message including information associated with a timing of a CLI measurement resource and associated with an NES mode of a first network entity (block 1010). For example, the first network entity (e.g., using Figure 12 The communication manager 1208 and / or message component 1210 depicted in FIG may generate a message including information associated with the timing of the CLI measurement resource, the NES mode associated with the first network entity, as described above, for example with reference to Figure 7 、 Figure 8 and Figure 9 As stated.

[0114] like Figure 10 As further shown, in some aspects, process 1000 may include sending the message to a second network entity (block 1020). For example, a first network entity (e.g., using Figure 12 The communication manager 1208 and / or sending component 1204 depicted in FIG may send the message to the second network entity, as described above, for example with reference to FIG. Figure 7 、 Figure 8 and Figure 9 described.

[0115] 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.

[0116] In a first aspect, the message includes a CLI resource measurement configuration.

[0117] In a second aspect, alone or in combination with the first aspect, the CLI resource measurement configuration indicates a first set of CLI measurement resources for a NES mode of the first network entity and a second set of CLI measurement resources for a non-NES mode of the first network entity.

[0118] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1000 includes receiving a CLI report from the second network entity indicating a NES operating mode of the second network entity.

[0119] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the message indicates a full-duplex mode of the first network entity, a subband configuration of the first network entity, or a combination thereof.

[0120] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1000 includes receiving a CLI report from the second network entity indicating a full-duplex mode of the second network entity.

[0121] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, sending the message comprises sending the message based at least in part on detection of a triggering event.

[0122] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, sending the message includes sending the message via wireless signaling.

[0123] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, sending the message includes sending the message via a backhaul between the first network entity and the second network entity.

[0124] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, sending the message includes sending the message via a central coordinator.

[0125] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, sending the message includes sending the message via a CU of the first network entity.

[0126] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 1000 includes performing CLI measurements when the first network entity is in the NES mode.

[0127] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the NES mode includes power adaptation, operating bandwidth, number of antenna elements, beam selection, or any combination thereof.

[0128] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the NES mode comprises an EH mode, and the non-NES mode comprises a non-EH mode.

[0129] although Figure 10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Figure 10 The blocks depicted may include 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 1000 may be performed in parallel.

[0130] Figure 11 1 is a diagram illustrating an example process 1100, performed, for example, by a second network entity, in accordance with the present disclosure. Example process 1100 is an example in which a second network entity (e.g., base station 110, network entity 720) performs operations associated with measuring and reporting CLI based, at least in part, on NES mode information from a first network entity.

[0131] like Figure 11 As shown in , in some aspects, process 1100 may include receiving a message including information associated with a timing of a CLI measurement resource and associated with an NES mode of a first network entity (block 1110). For example, a second network entity (e.g., using Figure 12 The communication manager 1208 and / or receiving component 1202 depicted in FIG may receive a message including information associated with the timing of the CLI measurement resource, the NES mode associated with the first network entity, as described above, for example with reference to Figure 7 、 Figure 8 and Figure 9 described.

[0132] like Figure 11 As further shown, in some aspects, process 1100 may include performing a CLI measurement based at least in part on the information and the energy state of the second network entity (block 1120). For example, the second network entity (e.g., using Figure 12 The communication manager 1208 and / or the measurement component 1212 depicted in FIG may perform CLI measurements based at least in part on the information and the energy state of the second network entity, as described above, for example with reference to FIG. Figure 7 、 Figure 8 and Figure 9 described.

[0133] 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.

[0134] In a first aspect, performing CLI measurements includes adjusting the CLI measurements during the NES mode of the first network entity.

[0135] In a second aspect, alone or in combination with the first aspect, performing the CLI measurement includes using a first CLI measurement configuration during the NES mode of the first network entity and using a second CLI measurement configuration during a non-NES mode of the first network entity.

[0136] In a third aspect, alone or in combination with one or more of the first and second aspects, the message includes a CLI resource measurement configuration.

[0137] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the CLI resource measurement configuration indicates a first set of CLI measurement resources for the NES mode of the first network entity and a second set of CLI measurement resources for the non-NES mode of the first network entity, and performing the CLI measurement includes: measuring CLI using the first set of CLI measurement resources during the NES mode and measuring CLI using the second set of CLI measurement resources during the non-NES mode.

[0138] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1100 includes sending, from the second network entity, a CLI report indicating an NES operating mode of the second network entity.

[0139] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 1100 includes sending, from the second network entity, a CLI report indicating a full duplex mode of the second network entity associated with performance of the CLI measurement.

[0140] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the message indicates a full-duplex mode of the first network entity, a subband configuration of the first network entity, or a combination thereof.

[0141] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 1100 includes sending a CLI report indicating a subset of antenna elements used to measure CLI.

[0142] although Figure 11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Figure 11 The blocks depicted may include additional blocks, fewer blocks, different blocks, or blocks arranged differently than those depicted. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0143] Figure 12is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a network entity (e.g., base station 110, network entity 710, network entity 720), or a network entity may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which 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 transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 1208. Communication manager 1208 may control and / or otherwise manage one or more operations of receiving component 1202 and / or transmitting component 1204. In some aspects, communication manager 1208 may include a communication manager 1208 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entities described. The communication manager 1208 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communications manager 1208 can be configured to perform one or more of the functions described as being performed by the communications manager 150. In some aspects, the communications manager 1208 can include a receiving component 1202 and / or a sending component 1204. The communications manager 1208 can include a messaging component 1210 and / or a measurement component 1212, among other things.

[0144] In some aspects, the apparatus 1200 may be configured to perform the Figures 1 to 9 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein, such as Figure 10 The process of 1000 Figure 11 In some aspects, Figure 12 The device 1200 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the first network entity described. Figure 12 One or more of the components shown may be combined 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 code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0145] Receive component 1202 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from device 1206. Receive component 1202 may provide the received communications to one or more other components of device 1200. In some aspects, receive component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to the one or more other components of device 1200. In some aspects, receive component 1202 may include in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described first network entity.

[0146] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1206. In some aspects, one or more other components of the apparatus 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the apparatus 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) on ​​the generated communications and may transmit the processed signals to the apparatus 1206. In some aspects, the transmitting component 1204 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described first network entity. In some aspects, the transmitting component 1204 can be co-located with the receiving component 1202 in a transceiver.

[0147] In some aspects, the network entity can be a first network entity. Message component 1210 can generate a message including information associated with the timing of the CLI measurement resource and associated with the NES mode of the first network entity. Sending component 1204 can send the message to the second network entity.

[0148] Receiving component 1202 can receive a CLI report from the second network entity indicating an NES operating mode of the second network entity. Receiving component 1202 can receive a CLI report from the second network entity indicating a full-duplex mode of the second network entity. When the first network entity is in NES mode, measuring component 1212 can perform CLI measurements.

[0149] In some aspects, the network entity can be a second network entity. Receiving component 1202 can receive a message including information associated with the timing of the CLI measurement resource and the NES mode of the first network entity. Measuring component 1212 can perform CLI measurements based at least in part on the information and the energy state of the second network entity.

[0150] The transmitting component 1204 may transmit a CLI report from the second network entity indicating an NES operating mode of the second network entity. The transmitting component 1204 may transmit a CLI report from the second network entity indicating a full-duplex mode of the second network entity associated with the performance of the CLI measurement. The transmitting component 1204 may transmit a CLI report indicating a subset of antenna elements used to measure the CLI.

[0151] Figure 12 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 12 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 12 Two or more components shown may be implemented in a single component, or Figure 12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The illustrated set of component(s) executable is described as consisting of Figure 12 Another collection of components shown performs one or more functions.

[0152] The following provides an overview of some aspects of the disclosure:

[0153] Aspect 1: A method of wireless communication performed by a first network entity, the method comprising: generating a message including information associated with timing of a cross-link interference (CLI) measurement resource and associated with a network energy saving (NES) mode of the first network entity; and sending the message to a second network entity.

[0154] Aspect 2: The method according to aspect 1, wherein the message includes a CLI resource measurement configuration.

[0155] Aspect 3: The method according to aspect 2, wherein the CLI resource measurement configuration indicates a first set of CLI measurement resources for the NES mode of the first network entity and a second set of CLI measurement resources for the non-NES mode of the first network entity.

[0156] Aspect 4: The method according to any one of aspects 1 to 3, further comprising: receiving a CLI report indicating an NES operation mode of the second network entity from the second network entity.

[0157] Aspect 5: The method according to any one of aspects 1 to 4, wherein the message indicates a full-duplex mode of the first network entity, a subband configuration of the first network entity, or a combination thereof.

[0158] Aspect 6: The method according to any one of aspects 1 to 5, further comprising: receiving a CLI report indicating a full-duplex mode of the second network entity from the second network entity.

[0159] Aspect 7: The method according to any one of aspects 1 to 6, wherein sending the message comprises: sending the message based at least in part on the detection of a triggering event.

[0160] Aspect 8: The method according to any one of aspects 1 to 7, wherein sending the message comprises sending the message via wireless signaling.

[0161] Aspect 9: The method according to any one of aspects 1 to 8, wherein sending the message comprises: sending the message via a backhaul between the first network entity and the second network entity.

[0162] Aspect 10: The method according to any one of aspects 1 to 9, wherein sending the message comprises: sending the message via a central coordinator.

[0163] Aspect 11: The method according to any one of aspects 1 to 10, wherein sending the message comprises: sending the message via a central unit (CU) of the first network entity.

[0164] Aspect 12: The method according to any one of Aspects 1 to 11, further comprising: performing CLI measurement when the first network entity is in the NES mode.

[0165] Aspect 13: The method according to any one of aspects 1 to 12, wherein the NES mode includes power adaptation, operating bandwidth, number of antenna elements, beam selection, or any combination thereof.

[0166] Aspect 14: The method according to any one of aspects 1 to 13, wherein the NES mode comprises an energy harvesting (EH) mode, and the non-NES mode comprises a non-EH mode.

[0167] Aspect 15: A method of wireless communication performed by a second network entity, the method comprising: receiving a message including information associated with timing of a cross-link interference (CLI) measurement resource and associated with a network energy saving (NES) mode of a first network entity; and performing CLI measurements based at least in part on the information and an energy state of the second network entity.

[0168] Aspect 16: The method according to aspect 15, wherein performing the CLI measurement includes adjusting the CLI measurement during the NES mode of the first network entity.

[0169] Aspect 17: The method according to aspect 15 or 16, wherein performing the CLI measurement includes: using a first CLI measurement configuration during the NES mode of the first network entity and using a second CLI measurement configuration during the non-NES mode of the first network entity.

[0170] Aspect 18: The method according to any one of aspects 15 to 17, wherein the message includes a CLI resource measurement configuration.

[0171] Aspect 19: A method according to Aspect 18, wherein the CLI resource measurement configuration indicates a first set of CLI measurement resources for the NES mode of the first network entity and a second set of CLI measurement resources for the non-NES mode of the first network entity, and wherein performing the CLI measurement includes: using the first set of CLI measurement resources to measure CLI during the NES mode and using the second set of CLI measurement resources to measure CLI during the non-NES mode.

[0172] Aspect 20: The method according to any one of aspects 15 to 19, further comprising: sending a CLI report indicating an NES operation mode of the second network entity from the second network entity.

[0173] Aspect 21: The method according to any one of aspects 15 to 20, further comprising: sending, from the second network entity, a CLI report indicating a full-duplex mode of the second network entity associated with the performing of the CLI measurement.

[0174] Aspect 22: The method according to any one of aspects 15 to 21, wherein the message indicates a full-duplex mode of the first network entity, a subband configuration of the first network entity, or a combination thereof.

[0175] Aspect 23: The method according to any one of aspects 15 to 22, further comprising: sending a CLI report indicating a subset of antenna elements used to measure CLI.

[0176] Aspect 24: An apparatus for wireless communication at a device, the apparatus comprising: a processor; one or more memories coupled to the processor; and instructions stored in the one or more memories and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 23.

[0177] Aspect 25: A device for wireless communication, the device comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors being configured individually or collectively to execute the method according to one or more of Aspects 1 to 23.

[0178] Aspect 26: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 23.

[0179] Aspect 27: 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 23.

[0180] Aspect 28: 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 23.

[0181] The foregoing disclosure provides illustration and description, but 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 the aspects.

[0182] 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 to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, 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 apparent 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 the various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0183] As used herein, "satisfying a threshold" may mean that a value is 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.

[0184] 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 the various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. The disclosure of each aspect includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items (including a single member). By way of example, “at least one of a, b, or c” is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of 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).

[0185] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects 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 projects and can be used interchangeably with "one or more". If you only want to refer to one project, you will use the phrase "only one" or similar terms. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms that do not limit the elements they modify (for example, an element "having" A may also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A method of wireless communication performed by a first network entity, the method comprising: generating a message including information associated with timing of a cross link interference (CLI) measurement resource and associated with a network energy saving (NES) mode of the first network entity; as well as The message is sent to the second network entity.

2. The method of claim 1, wherein the message comprises a CLI resource measurement configuration.

3. The method of claim 2, wherein the CLI resource measurement configuration indicates a first set of CLI measurement resources for the NES mode of the first network entity and a second set of CLI measurement resources for a non-NES mode of the first network entity.

4. The method according to claim 1, further comprising: A CLI report is received from the second network entity indicating a NES operating mode of the second network entity. 5 . The method of claim 1 , wherein the message indicates a full-duplex mode of the first network entity, a subband configuration of the first network entity, or a combination thereof.

6. The method according to claim 1, further comprising: A CLI report is received from the second network entity indicating a full-duplex mode of the second network entity.

7. The method of claim 1 , wherein sending the message comprises: The message is sent based at least in part on detection of a triggering event.

8. The method of claim 1, wherein sending the message comprises: The message is sent via wireless signaling.

9. The method of claim 1 , wherein sending the message comprises: The message is sent via a backhaul between the first network entity and the second network entity.

10. The method of claim 1, wherein sending the message comprises: The message is sent via a central coordinator.

11. The method of claim 1 , wherein sending the message comprises: The message is sent via a Central Unit (CU) of the first network entity.

12. The method according to claim 1, further comprising: CLI measurements are performed when the first network entity is in the NES mode.

13. The method of claim 1, wherein the NES mode comprises power adaptation, operating bandwidth, number of antenna elements, beam selection, or any combination thereof.

14. The method of claim 1, wherein the NES mode comprises an energy harvesting (EH) mode and the non-NES mode comprises a non-EH mode.

15. A method of wireless communication performed by a second network entity, the method comprising: receiving a message including information associated with timing of a cross-link interference (CLI) measurement resource, associated with a network energy saving (NES) mode of a first network entity; as well as A CLI measurement is performed based at least in part on the information and an energy state of the second network entity.

16. The method of claim 15, wherein performing the CLI measurement comprises: The CLI measurements are adjusted during the NES mode of the first network entity.

17. The method of claim 15, wherein performing the CLI measurement comprises: A first CLI measurement configuration is used during the NES mode of the first network entity and a second CLI measurement configuration is used during a non-NES mode of the first network entity.

18. The method of claim 15, wherein the message comprises a CLI resource measurement configuration.

19. The method of claim 18, wherein the CLI resource measurement configuration indicates a first set of CLI measurement resources for the NES mode of the first network entity and a second set of CLI measurement resources for a non-NES mode of the first network entity, and wherein performing the CLI measurements comprises: The CLI is measured using the first set of CLI measurement resources during the NES mode and the CLI is measured using the second set of CLI measurement resources during the non-NES mode.

20. The method according to claim 15, further comprising: A CLI report is sent from the second network entity indicating a NES operating mode of the second network entity.

21. The method according to claim 15, further comprising: A CLI report is sent from the second network entity indicating a full duplex mode of the second network entity associated with the performing of the CLI measurement.

22. The method of claim 15, wherein the message indicates a full-duplex mode of the first network entity, a subband configuration of the first network entity, or a combination thereof.

23. The method according to claim 15, further comprising: A CLI report is sent indicating the subset of antenna elements used to measure the CLI.

24. An apparatus of a first network entity for wireless communication, the apparatus comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to: generating a message including information associated with timing of a cross link interference (CLI) measurement resource and associated with a network energy saving (NES) mode of the first network entity; as well as The message is sent to the second network entity.

25. The apparatus of claim 24, wherein the message comprises a CLI resource measurement configuration.

26. The apparatus of claim 25, wherein the CLI resource measurement configuration indicates a first set of CLI measurement resources for the NES mode of the first network entity and a second set of CLI measurement resources for a non-NES mode of the first network entity.

27. The apparatus of claim 24, wherein the one or more processors are individually or collectively configured to: receive a CLI report from the second network entity indicating a NES operation mode of the second network entity.

28. An apparatus of a second network entity for wireless communication, the apparatus comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to: receiving a message including information associated with timing of a cross-link interference (CLI) measurement resource, associated with a network energy saving (NES) mode of a first network entity; and A CLI measurement is performed based at least in part on the information and an energy state of the second network entity.

29. The apparatus of claim 28, wherein the one or more processors that perform the CLI measurements are individually or collectively configured to adjust the CLI measurements during the NES mode of the first network entity.

30. The apparatus of claim 28, wherein the one or more processors that perform the CLI measurements are individually or collectively configured to use a first CLI measurement configuration during the NES mode of the first network entity and to use a second CLI measurement configuration during a non-NES mode of the first network entity.

Images