Support of efficient energy transfer

Abstract

An apparatus, a method, and a computer program product for supporting an energy harvesting (EH) wireless device are provided. An example method may include receiving energy harvesting information associated with at least one second network entity. The example method may also include transmitting, for the at least one second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for the energy transfer, where the first set of preferred resources is associated with a first metric above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric lower than the first threshold, where the first threshold is based on the energy harvesting information, and where the first threshold is independent of a second threshold for data communication.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems with energy transfer between devices. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0005] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus are provided at a first network entity (e.g., such as a user equipment (UE) or a base station). The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to: receive energy harvesting information associated with at least one second network entity. The at least one processor may be configured to: send, for the at least one second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for the energy transfer, wherein the first set of preferred resources is associated with a first metric that is higher than a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is lower than the first threshold, wherein the first threshold is based on the energy harvesting information, and wherein the first threshold is independent of a second threshold for data communication.

[0006] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a first network entity (e.g., such as a UE or a base station) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to: receive first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for the energy transfer from a second network entity, wherein the first set of preferred resources is associated with a first metric above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric below the first threshold, wherein the first threshold is based on energy harvesting information associated with the first network entity, and wherein the first threshold is independent of a second threshold for data communication. The at least one processor may be configured to: apply the first set of preferred resources to the energy harvesting, or suppress the application of the first set of non-preferred resources to the energy harvesting.

[0007] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0009] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0010] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0011] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0012] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0014] Figure 4 Example aspects of sidelink communications between devices are illustrated.

[0015] Figure 5 An example of resource reservation for sidelink communications is illustrated.

[0016] Figure 6 is a diagram illustrating a timing diagram of a UE adopting a sensing mechanism.

[0017] Fig. 7A and Figure 7B is a diagram illustrating inter-UE coordination between UEs.

[0018] Figure 8 is a diagram illustrating example backscatter communications.

[0019] Fig. 9 is a diagram illustrating example backscatter communications between a reader and a tag with an Interrogator (Reader) - Talk First (ITF) process.

[0020] Fig.10 is a diagram illustrating example communications between wireless devices.

[0021] Fig.11 is a diagram illustrating example threshold values.

[0022] Fig.12 is a flow chart of a wireless communication method.

[0023] Fig.13 is a flow chart of a wireless communication method.

[0024] Fig.14 is a flow chart of a wireless communication method.

[0025] Fig.15 is a flow chart of a wireless communication method.

[0026] Fig.16 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0027] Fig.17is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0028] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0029] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0031] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0032] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0033] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0034] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0035] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. 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.

[0036] Figure 11 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0037] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0038] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0039] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to a functional split (such as that defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0040] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based on functional splitting such as lower layer functional splitting. In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0041] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0042] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0043] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0044] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0045] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0046] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0047] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) that is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0048] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0049] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0050] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

[0051] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU.

[0052] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0053] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0054] Reference again Figure 1 , in some aspects, the UE 104 or the base station 102 may include a coordination component 198. In some aspects, the coordination component 198 may be configured to receive energy harvesting information associated with at least one second network entity. In some aspects, the coordination component 198 may be further configured to send, for the at least one second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on the energy harvesting information, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, the coordination component 198 may be configured to receive, from the second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer, wherein the first set of preferred resources is associated with a first metric that is above the first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on the energy harvesting information associated with the first network entity, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, coordination component 198 can be further configured to apply the first set of preferred resources for energy harvesting, or to refrain from applying the first set of non-preferred resources for energy harvesting.

[0055] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0056] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. For another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0057] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). The disclosure of one communication term includes the disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the second network node is configured to receive, obtain, or decode information provided, sent, output, transmitted, or sent by the first network node.

[0058] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling).

[0059] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of equal size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0060]

[0061] Table 1: Parameter set, SCS and CP

[0062] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0063] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0064] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0065] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0066] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0067] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0068] Figure 3375. The Controller / Processor 375 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0069] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0070] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0071] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0072] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0073] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0074] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0075] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0076] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The coordination component 198 is used to execute various aspects.

[0077] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The coordination component 198 is used to execute various aspects.

[0078] Figure 4 An example 400 of sidelink communication between devices as presented herein is illustrated. The communication may be based on a sidelink structure. For example, a first UE 402 may send a sidelink transmission 410, for example, including a control channel (e.g., PSCCH) and / or a corresponding data channel (e.g., PSSCH), which may be received by a second UE 406 and / or a third UE 408. The sidelink transmission 410 may be received directly from the first UE 402, for example, without having to be sent through a base station.

[0079] In addition to operating as a receiving device, the first UE 402, the second UE 406 and / or the third UE 408 can also each be capable of operating as a transmitting device. Therefore, the second UE 406 is shown as sending a side link transmission 412 received by the first UE 402. Each of the side link transmissions 410 and 412 can be broadcast or multicast to nearby devices. For example, the first UE 402 can send communications intended to be received by other UEs within the range 401 of the first UE 402. In other examples, one or more side link transmissions in the side link transmissions 410 and 412 can be multicast to nearby devices, which are group members. In other examples, one or more side link transmissions in the side link transmissions 410 and 412 can be unicast from one UE to another UE.

[0080] The sidelink transmission may provide sidelink control information (SCI) including information to facilitate decoding of the corresponding data channel. For example, a transmitting device (sometimes referred to as an "initiating device", "transmitting UE", or "initiating UE") may send an SCI that includes information that a receiving device (sometimes referred to as a "target device", "receiving UE", or "target UE") may use to avoid interference. For example, the SCI may indicate reserved time resources and / or reserved frequency resources to be occupied by data transmission, and may be indicated in a control message from the transmitting device. The number of TTIs and RBs to be occupied by the data transmission may be indicated in a control message from the first UE 402. In some examples, the SCI may be used by a receiving device to avoid interference by refraining from transmitting on occupied resources during data transmission.

[0081] One or more of the first UE 402, the second UE 406, and / or the third UE 408 may include a Figure 1 A coordination component similar to the coordination component 198 described above.

[0082] Sidelink communications enable a first UE to communicate directly with another UE. For example, the first UE and the other UE can communicate without routing the communication through a base station. Sidelinks can be beneficial for vehicle-based communications (e.g., V2V, V2I, V2N, V2P, C-V2X, etc.) that allow a vehicle UE to communicate directly with another UE or a pedestrian UE. When dealing with V2X communications, power consumption of the vehicle UE may not be an issue.

[0083] However, it may be beneficial to implement a power saving mode for some devices. Two examples of power saving modes include partial sensing or random selection and discontinuous reception (DRX). In DRX or partial sensing, the UE may skip sensing for resource reservations for part of the time. For example, skipped sensing may save battery power at the UE.

[0084] The sidelink communication may be based on different types or modes of resource allocation mechanisms. In a first resource allocation mode (which may be referred to herein as "Mode 1"), centralized resource allocation may be provided by a network entity. For example and with reference to Figure 1 In an example of sidelink communication, the base station 102 / 180 may determine resources for sidelink communication, and may allocate resources to different UEs for sidelink transmission. In this first mode, the UE receives a sidelink resource allocation from the base station 102 / 180. In a second resource allocation mode (which may be referred to as "mode 2" in this article), a distributed resource allocation may be provided. In mode 2, each UE may autonomously determine resources for sidelink transmission. In order to coordinate the selection of sidelink resources by each UE, each UE may use sensing technology to monitor the resource reservations of other sidelink UEs, and may select resources for sidelink transmission from unreserved resources. A device communicating based on a sidelink may determine one or more radio resources used by other devices in the time domain and the frequency domain in order to select transmission resources that avoid conflicts with other devices. Sidelink transmission and / or resource reservation may be periodic or aperiodic, wherein the UE may reserve resources for transmission in the current time slot and up to two future time slots.

[0085] Thus, in this second mode (e.g., Mode 2), each UE may autonomously select resources for sidelink transmission, e.g., without a central entity (such as a base station indicating resources for the device). A first UE may reserve the selected resources in order to inform other UEs about the resources that the first UE intends to use for sidelink transmission.

[0086] In some examples, resource selection for sidelink communication can be based on a sensing mechanism. For example, before selecting resources for data transmission, the UE can first determine whether the resources have been reserved by other UEs.

[0087] For example, as part of a sensing mechanism for resource allocation mode 2, a UE may determine (e.g., sense) whether a selected side link resource has been reserved by other UEs before selecting a side link resource for data transmission. If the UE determines that the side link resource has not been reserved by other UEs, the UE may use the selected side link resource for transmitting data, for example, in a PSSCH transmission. The UE may estimate or determine which radio resources (e.g., side link resources) may be in use and / or reserved by other UEs by detecting and decoding side link control information (SCI) sent by other UEs. The UE may estimate or determine which radio resources are in use and / or reserved by other UEs using a sensing-based resource selection algorithm. The UE may receive an SCI from another UE, the SCI including reservation information based on a resource reservation field included in the SCI. The UE may continuously monitor (e.g., listen) and decode the SCI from a peer UE. The SCI may include reservation information, for example, indicating that a particular UE has selected a time slot and RB for future transmission. The UE may exclude resources used and / or reserved by other UEs from the candidate resource set used by the UE for sidelink transmission, and the UE may select / reserve resources for sidelink transmission from resources that are not used and thus form the candidate resource set. The UE may continuously perform sensing on the SCI with resource reservations in order to maintain a candidate resource set from which the UE may select one or more resources for sidelink transmission. Once the UE selects a candidate resource, the UE may send an SCI indicating its own reservation of resources for sidelink transmission. The number of resources (e.g., subchannels per subframe) reserved by the UE may depend on the size of the data to be sent by the UE. Although this example is described with respect to a UE receiving reservation information from another UE, the reservation information may also be received from an RSU or other device communicating based on a sidelink.

[0088] Figure 5 500 is an example showing reserved time resources and frequency resources for sidelink transmissions as proposed herein. For example, the resources may be included in a sidelink resource pool. Resource allocation for each UE may be in units of one or more subchannels in the frequency domain (e.g., subchannels SC 1 to SC 4) and may be based on a time slot in the time domain (e.g., time slots "1" to 8). The UE may also use resources in the current time slot to perform an initial transmission and may reserve resources in future time slots for retransmissions. Figure 5In the example shown in , two different future time slots are reserved by UE1 and UE2 for retransmission. Resource reservation may be limited to a window of predefined time slots and subchannels, such as a window of 8 time slots by 4 subchannels as shown in example 500, which provides a total of 32 available resource blocks. This window may also be referred to as a resource selection window.

[0089] A first UE ("UE1") may reserve a subchannel (e.g., SC 1) in a current time slot (e.g., time slot 1) for its initial data transmission 502, and may reserve additional future time slots within the window for data retransmissions (e.g., a first data retransmission 504 and a second data retransmission 506). For example, the first UE may reserve subchannel SC 3 at time slot 3 and SC 2 at time slot 4 for future retransmissions, as shown in FIG. Figure 5 As shown. The first UE then sends information about which resources are being used and / or reserved by it to other UEs. The first UE can do so by including reservation information in the reserved resource field of the SCI (e.g., the first level SCI (SCI 1)). There may be a second level SCI (SCI 2). As an example, SCI 2 may be mapped to consecutive RBs in the PSSCH starting from the first symbol associated with the PSSCH DM-RS. The format of SCI 2 may be indicated in the first level SCI. SCI 1 may be sent in the PSCCH. Multiple resource elements (REs) may be derived based on SCI 1. The starting position of SCI 2 may be defined and known to the UE. In some aspects, the UE may not blindly decode SCI 2. The SCI 2 format may include one or more of a HARQ process identifier (ID), a new data indicator (NDI), a source ID, a destination ID, a CSI report trigger, etc. The SCI 2 format associated with multicast may also include an area ID indicating the location of the transmitter and a communication range for transmitting feedback.

[0090] Figure 5 The example shows that the second UE ("UE2") reserves resources in subchannels SC 3 and SC 4 at time slot "1" for current data transmission 508, reserves first data retransmission 510 using subchannels SC 3 and SC 4 at time slot 4, and reserves second data retransmission 512 using subchannels SC "1" and SC 2 at time slot 7, as shown in FIG. Figure 5 Similarly, the second UE may send resource usage and reservation information to other UEs, such as using the reserved resource field in the SCI.

[0091] The third UE may select resources for sending its data taking into account resources reserved by other UEs within the resource selection window. The third UE may first decode the SCI within a time period to identify which resources are available (e.g., candidate resources). For example, the third UE may exclude resources reserved by UE1 and UE2, and may select other available subchannels and time slots from the candidate resources for its transmission and retransmission, which may be based on the number of adjacent subchannels to which the data to be sent (e.g., packets) can be adapted.

[0092] Although Figure 5 It is illustrated that resources are reserved for initial transmission and two retransmissions, but the reservation may be used for initial transmission and a single retransmission or only for initial transmission.

[0093] The UE may determine an associated signal measurement (such as RSRP) for each resource reservation received by another UE. The UE may consider that the reserved resources in the transmission for which the UE measures an RSRP below a threshold are available for use by the UE. The UE may perform signal / channel measurements on sidelink resources that have been reserved and / or used by other UEs, such as by measuring the RSRP of a message (e.g., SCI) that reserves sidelink resources. Based at least in part on the signal / channel measurements, the UE may consider using / reusing sidelink resources that have been reserved by other UEs. For example, if the measured RSRP reaches or exceeds a threshold, the UE may exclude the reserved resources from the candidate resource set, and if the measured RSRP of the message for the reserved resources is below a threshold, the UE may consider that the reserved resources will be available. When the message for the reserved resources has an RSRP below a threshold, the UE may include these resources in the candidate resource set and may use / reuse such reserved resources because the low RSRP indicates that the other UE is far away and reusing these resources is unlikely to cause interference to the UE. A higher RSRP indicates that the transmitting UE that reserved the resources is potentially closer to the UE, and if the UE selects the same resources, the transmitting UE may experience a higher level of interference.

[0094] For example, the UE may determine a candidate resource set (e.g., by monitoring SCIs from other UEs and removing from the candidate resource set resources reserved by other UEs in signals for which the UE measured an RSRP above a threshold). The UE may also select N resources for transmission and / or retransmission of a TB. For example, the UE may randomly select N resources from a previously determined candidate resource set. For each transmission, the UE may reserve future time and frequency resources for the initial transmission and up to two retransmissions. The UE may reserve resources by sending an SCI indicating resource reservation. For example, in Figure 5 In the example in , the second UE may send an SCI that reserves resources for current data transmission 508 , first data retransmission 510 , and second data retransmission 512 .

[0095] There may be a timeline for sensing-based resource selection. For example, a UE may sense and decode SCI received from other UEs during a sensing window (e.g., a duration prior to resource selection). Based on the sensing history during the sensing window, the UE may maintain a set of available candidate resources by excluding resources reserved by other UEs from the set of candidate resources. The UE may select resources from its set of available candidate resources and send an SCI reserving resources selected by the UE for sidelink transmission (e.g., PSSCH transmission). There may be a time gap between the UE's selection of resources and the UE sending the SCI reserving the resources.

[0096] In resource allocation mode 2, higher layers may request the UE 104, including the coordination component 198, to determine a subset of resources from which the higher layers may select resources for PSSCH / PSCCH transmissions. Figure 6 An example timing diagram 600 illustrates a UE that may be triggered to select resources for sidelink transmission in response to a resource selection trigger 650. The timing diagram shows a method for sensing resource reservations from other UEs (such as in conjunction with Figure 5 For example, resource selection trigger 650 may include data for transmission. Figure 6 The resource selection may also be applied by other side link devices. In response to the resource selection trigger 650, the UE may consider the signal received within the sensing window 602 of the duration T_0 and determine the information received within the sensing window 602 (e.g., SCI with resource reservation). For example, the UE may determine which resources have been used by other UEs or reserved by the UE during the sensing window 602. The UE may expect that the previously used resources may also be used by another UE in the future. The signal received in the sensing window may include an SCI indicating a resource reservation for resources within the resource selection window 604 after the resource selection trigger 650. Based on past resource usage and / or resource reservation (e.g., "sensing" of resources), the UE may determine which resources are scheduled for use and / or determine which resources are not scheduled for use. For example, based on resource sensing during the sensing window 602, the UE may determine that the first resource 606 and the second resource 608 may be reserved during the time slot associated with the resource selection trigger 650 and / or during the future time slot. The UE may exclude candidate resources reserved by other UEs from the candidate resource set when selecting sidelink transmission resources. In some examples, the UE may exclude candidate resources reserved by another UE and satisfying one or more conditions (such as a reservation signal satisfying an RSRP threshold). The UE may select resources 610 for transmission.

[0097] In some wireless communication systems, a receiving UE may perform sensing and then notify a transmitting UE (along with other UEs) of resources available for transmission based on the sensing results. For example, the receiving UE may be a smart phone with higher processing power and higher battery capacity than the transmitting UE, which may be a smart watch with limited battery capacity and limited processing power. Therefore, it may be more efficient for the receiving UE with higher processing power to perform sensing of the transmitting UE with higher battery capacity.

[0098] In some instances, multiple UEs may transmit simultaneously and may not receive overlapping communications (e.g., SCI indicating resource reservations) from each other and / or from the base station. Such UEs may miss or be unaware of other UEs' transmissions and sidelink reservations. As a result, two UEs may reserve the same resource blocks for future sidelink transmissions, which may result in resource conflicts. Resource conflicts may occur for sidelink transmissions that at least partially overlap in time and at least partially overlap in frequency.

[0099] To reduce or avoid resource conflicts in such instances, and to improve sidelink communications between UEs, the UEs may coordinate among themselves by generating and sharing inter-UE coordination information with other UEs. Fig. 7A 7 is a diagram illustrating an exchange of inter-UE coordination information, in which a first UE ("UE-A") 712 sends inter-UE coordination information 716 to a second UE ("UE-B") 714. In some aspects, the sending of the inter-UE coordination information may include resource reservation forwarding by UE-A.

[0100] The inter-UE coordination information 716 may include information based on: sensing information of the UE (e.g., resource reservations of other UEs sensed by UE 712 (e.g., UE-A)), inter-UE coordination information from another UE, poor, undesirable, or non-preferred resources for UE-A 712 (e.g., resources subject to high interference), resources that are preferred or better than other resources for UE-A 712, etc.

[0101] The inter-UE coordination information 716 may indicate candidate resources for sidelink transmission or preferred resources for transmission by UE-B 714. In some aspects, the information indicating preferred resources for UE-B's transmission may be referred to as "type A" inter-UE coordination information. UE-A 712 may use the inter-UE coordination information 716 to inform UE-B 714 about which subchannels and time slots may be used for communication with UE-A 712 and / or which subchannels and time slots may not be used because they are occupied or reserved by UE-A 712 and / or other UEs. UE-A may indicate a set of resources that may be more preferred for UE-B's transmission based on UE-A's evaluation. Candidate resources may indicate a resource group from which UE-B 714 (e.g., UE-B) may select for sidelink transmission 718. As illustrated, the sidelink transmission 718 may be used for UE-A 712 or for one or more different UEs, such as UE-C 719. In some aspects, UE-A may be a potential receiver of UE-B's transmissions, and the inter-UE coordination information may enable Mode 2 resource allocation based on resource availability from the perspective of the potential receiver, which may address reception challenges for hidden nodes. In some aspects, the inter-UE coordination information 716 may indicate resources for sidelink transmissions, e.g., specific resources on which UE-B 714 will send sidelink transmissions 718, rather than candidate resources that UE-B 714 may select.

[0102] In some aspects, the inter-UE coordination information 716 may indicate a set of resources that may not be preferred for UE-B's transmission, such as resources that may not be available for UE-B to use to transmit a sidelink transmission based on UE-A's evaluation. In some aspects, information indicating non-preferred resources for UE-B's transmission may be referred to as "Type B" inter-UE coordination information.

[0103] In some aspects, the inter-UE coordination information 716 may indicate a half-duplex collision. For example, the inter-UE coordination information 716 may indicate a collision in time and / or frequency between two transmitting UEs, where the two transmitting UEs are unable to receive the other's corresponding transmission in half-duplex mode. In some aspects, the inter-UE coordination information 716 may indicate a conflict in time and / or frequency between resources (e.g., reserved resources). In some aspects, information indicating a collision / conflict in resources may be referred to as "Type C" inter-UE coordination information.

[0104] Based at least in part on the inter-UE coordination information 716 from UE-A 712, UE 704 may make better decisions about resources to use and / or reserve for its sidelink transmissions 718 to avoid resource conflicts. UE-A 712 may share its inter-UE coordination information 716 with multiple UEs, and UE-B 714 may receive the inter-UE coordination information 716 from multiple UEs. The inter-UE coordination information 716 may be sent in any of a variety of ways.

[0105] UE-A 712 may send inter-UE coordination information 716 in PSFCH, for example, indicating a resource conflict or a half-duplex conflict. UE-A 712 may send inter-UE coordination information 716 in SCI. For example, UE-A 712 may send shared sensing information, candidate resource information for sidelink transmission, or specific resources for sidelink transmission in SCI-2 sent in PSSCH. For example, the first part of SCI (e.g., SCI-1) may be sent in PSCCH, and the second part of SCI (e.g., SCI-2) may be sent in PSSCH. UE-A 712 may send inter-UE coordination information 716, for example, in a medium access control-control element (MAC-CE) on PSSCH. UE-A 712 may send inter-UE coordination information 716 in a new physical channel (e.g., different from PSCCH, PSSCH, PSFCH, etc.). For example, UE-A 712 may send inter-UE coordination information 716 in a physical channel configured for or dedicated to inter-UE configuration information. UE-A 712 may send inter-UE coordination information 716 in RRC signaling.

[0106] In some aspects, UE-A 712 may periodically send inter-UE coordination information 716. In some aspects, UE-A 712 may send aperiodic inter-UE coordination information 716 in response to a trigger. In other examples, the trigger may be based on the occurrence of an event, such as the occurrence / detection of a resource conflict, the occurrence / detection of a half-duplex conflict, etc. For example, if UE-A 712 detects a resource conflict, UE-A 712 may respond by sending inter-UE coordination information 716.

[0107] UE-B 714 may utilize the inter-UE coordination information 716 in various ways. If the inter-UE coordination information 716 includes information about resources that are preferred for transmission by UE-B 714 and / or resources that are not preferred for transmission by UE-B 714, UE 704 may select resources to be used for its sidelink transmission resource selection or resource reselection based on both the sensing results of UE-B (if available) and the received inter-UE coordination information 716 according to a first option. In a second option, UE-B 714 may select resources to be used for its sidelink transmission resource selection or resource reselection based on the received inter-UE coordination information 716 rather than based on sensing. In a third option, UE-B 714 may select resources to be used for its sidelink transmission resource selection or resource reselection based on the received inter-UE coordination information 716 (which may allow UE-B to use or not use sensing in conjunction with the inter-UE coordination information 716).

[0108] Figure 7B 7 is a diagram 750 illustrating the exchange of inter-UE coordination information that UE 702 may provide to multiple UEs. Figure 7B , UE 702 may be more capable of performing sensing than UE 704, UE 706, or UE 708. For example, UE 702 (which may be a receiving UE that receives transmissions from UE 704, UE 706, or UE 708) may have higher processing power and / or higher battery capacity than UE 704, UE 706, or UE 708. Therefore, it may be more efficient for UE 702 with higher battery capacity / processing power to perform sensing and send (e.g., multicast) resource availability information 722 to UE 704, UE 706, and UE 708. In addition, UE 702 may have information about UE 704, UE 706, and UE 708 based on measuring RSRP of signals on incoming links. For example, UE 702 can measure RSRP on a link between UE 702 and UE 704, a link between UE 702 and UE 706, and a link between UE 702 and UE 708. By measuring different links, UE 702 can better identify available resources.

[0109] In some cases, based on the sensing, the receiving UE 702 may identify a first set of available resources that may be less than a threshold amount of resources for transmission 724 from UE 704 to UE 702 (e.g., determined to be inappropriately small by comparing the size of the available resources to an availability threshold).

[0110] In addition to higher-capability devices, wireless communications may also support devices with reduced capabilities (RedCap). In other examples, examples of higher-capability devices include advanced smart phones, V2X devices, URLLC devices, eMBB devices, and the like. In other examples, devices with reduced capabilities may include wearable devices (e.g., such as smart watches, augmented reality glasses, virtual reality glasses, health and medical monitoring devices, etc.), industrial wireless sensor networks (IWSNs) (e.g., such as pressure sensors, humidity sensors, motion sensors, thermal sensors, accelerometers, actuators, etc.), surveillance cameras, low-end smart phones, and the like. For example, an NR communication system may support both higher-capability devices and devices with reduced capabilities. Devices with reduced capabilities may be referred to as NR light devices, low-layer devices, lower-layer devices, and the like. UEs with reduced capabilities may communicate based on various types of wireless communications. For example, smart wearable devices may send or receive communications based on low-power wide area networks (LPWA) / mMTC, loose IoT devices may send or receive communications based on URLLC, and sensors / cameras may send or receive communications based on eMBB, and the like.

[0111] In addition to devices with reduced capabilities, devices with lower capabilities than devices with reduced capabilities, including lower power consumption and less complex structures, may also be included in the wireless communication system. In some wireless communication systems, passive wireless devices (such as zero-power passive IoT wireless devices) may be included. Such passive wireless devices may not have active RF components, and may perform transmission based on backscatter communication, and may perform reception based on envelope detection or envelope detectors. Backscatter communication can modulate information on an incoming RF signal (which may be a carrier that can carry communications between other devices) by adapting the antenna load impedance. Passive wireless devices may be battery-free or battery-assisted. For example, a passive wireless device may operate based on energy harvesting from incoming radio waves with or without a battery as an additional power source. Passive wireless devices may have low power consumption, such as between 1 microwatt and 1000 microwatts. Such passive wireless devices may be devices for inventory management, wireless sensors, etc. Passive devices may use backscatter communication to communicate with another network entity (such as a base station).

[0112] Backscatter communication can realize radio frequency identification (RFID). For example, a reader can transmit a continuous waveform signal and an inquiry command. An RF tag (which is a passive wireless device) can harvest energy from a continuous waveform signal and can respond to inquiries by changing its input impedance (e.g., between a conjugate match and a strong mismatch), thereby modulating the backscatter signal. RFID is a rapidly developing technology that affects many industries due to its potential for inventory / asset management inside and outside warehouses, IoT, sustainable sensor networks in factories and / or agriculture, and smart homes. RFID may include a small transponder that transmits an information-bearing signal when a signal is received, which may be referred to as a tag. RFID can operate with low operating expenditure (OPEX) without a battery and can use a small amount of resources. RFID can use less maintenance and can have a long life cycle.

[0113] In some aspects, the term "resource" may refer to a time and frequency resource that a wireless device may monitor. In some aspects, the term "preferred resource" may be used interchangeably with "suitable resource", and the term "non-preferred resource" may be used interchangeably with "unsuitable resource". In some aspects, a preferred resource or non-preferred resource may be any resource known to the wireless device (e.g., based on a coordination message, a resource allocated to the wireless device, etc.). The wireless device may determine that some resources are preferred or non-preferred for data communication, and determine that some resources are preferred or non-preferred for energy harvesting. As used herein, the term "preferred resource for data communication" may refer to a time and frequency resource that may be indicated by a network entity (such as a UE or gNB) to a second network entity for data transmission. The term "non-preferred resource for data communication" may refer to a time and frequency resource that may be indicated by a network entity (such as a UE or gNB) to a second network entity to avoid data transmission. In some aspects, a non-preferred resource may be used by the second network entity for data transmission despite not being preferred (which may result in worse performance). The term "preferred resources for energy transfer" may refer to time and frequency resources that may be indicated by a network entity (such as a UE or gNB) to a second network entity for energy transfer or energy harvesting. The term "non-preferred resources for energy transfer" may refer to time and frequency resources that may be indicated by a network entity (such as a UE or gNB) to a second network entity to avoid energy transfer or energy harvesting. In some aspects, non-preferred resources may be used by the second network entity for energy transfer despite not being preferred (which may result in worse performance). In some aspects, preference may be based on available resources, while non-preference may be based on unavailable resources. In some aspects, both preferred and non-preferred resources may be available. As used herein, the term "energy transfer" may be used interchangeably with "energy harvesting" to refer to a process in which a wireless device (which may be referred to as an "energy harvesting wireless device") uses a carrier transmitted by another wireless device (which may be referred to as a "power provider wireless device") to obtain energy. In some aspects, preferred resources for data communication may be preferred for energy transfer or non-preferred for energy transfer. In some aspects, non-preferred resources for data communication may be preferred for energy transfer or non-preferred for energy transfer. In some aspects, a preferred resource for energy transfer may be preferred for data communication or non-preferred for data communication. In some aspects, a non-preferred resource for energy transfer may be preferred for data communication or non-preferred for data communication. An example of an energy harvesting (EH) device may be an RF tag, and an example of a power provider (PP) wireless device may be an RF interrogator (which may also be referred to as an "RF reader").

[0114] Figure 8 8 is a diagram illustrating example backscatter communications. Figure 8As shown, the RF reader 802 may send a continuous wave (CW) 804A for powering up the RF tag 806. Based on the continuous wave 804A, the RF tag 806 may be powered up. The RF reader 802 may also send a wave carrying a modulation command 804B to the RF tag 806 (e.g., by modulating the CW). Based on the energy collected from the wave carrying the modulation command 804B, the RF tag may send (e.g., by modulation and reflection) a modulation response 808 to the RF reader.

[0115] Fig. 9 9 is a diagram illustrating an example backscatter communication between a reader and a tag with an interrogator (reader)-talk first (ITF) process. Fig. 9 As shown, CW can be sent by the reader to power on the tag. After the tag is powered on, the reader can send a command and then maintain CW to keep the tag turned on.

[0116] If the wireless device is a PP UE to other sidelinks / wearables / UEs in the network, the PP-UE may transmit the best resources for each of the specific UEs it is assisting (e.g., when those UEs are utilizing a time-switched energy harvesting architecture). In some aspects, the concept of inter-UE coordination may be extended to indicate UEs with preferred or non-preferred resources for data communication or energy transfer (e.g., that may be used to power EH UEs). For example, a PP UE may notify one or more EH UEs that some time and frequency resources (e.g., which may carry another transmission) may be used as an energy source, even if those time and frequency resources do not carry a dedicated energy signal. In some aspects, a PP UE may be assigned to power multiple EH UEs, each of which may be located at a different location and may be at a different distance from the PP UE. The charging rates of the EH UEs may be the same or different. The energy harvested or charging rate at the EH wireless device may be: P=ηP tx |h| 2 Watt or E = PT joule, where η represents the RF-DC conversion efficiency, P tx represents the Tx radiated power, h represents the channel coefficient (small-scale fading and large-scale fading), and T represents the total allocation time. If η is higher, more energy can be collected and accumulated over time. The RF-DC conversion efficiency η may depend on the circuit design, antenna efficiency, the efficiency of the voltage multiplier to convert RF to DC, the accuracy of the impedance matching between the antenna and the voltage multiplier, etc. Increasing the transmit radiated power P tx ,The transferred power can also be increased. Increasing the charging time T can increase the accumulated energy at the EH wireless device.

[0117] Fig.10 1 is a diagram 1000 illustrating example communications between wireless devices. Fig.10 As shown, one or more power provider wireless devices including a first power provider wireless device 1002, a non-EH wireless device 1006, and one or more energy harvesting wireless devices including a wireless device 1004A and a wireless device 1004B are illustrated. In some aspects, the non-EH wireless device 1006 may be a PP wireless device, or may not be a PP wireless device (e.g., an auxiliary device). In some aspects, one or more power provider wireless devices may be network entities, such as UEs, base stations, or other types of devices in a wireless communication network. In some aspects, one or more energy harvesting wireless devices may be network entities, such as UEs, base stations, or other types of devices in a wireless communication network. In some aspects, the network entity may be implemented in an aggregated or monolithic base station architecture, or alternatively in a decomposed base station architecture, and may include one or more of a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In some aspects, communication between one or more power provider wireless devices or one or more energy harvesting wireless devices can be downlink communication (e.g., including downlink configuration or dynamic grant), uplink communication (e.g., including uplink configuration or dynamic grant), sidelink communication, backhaul communication, etc.

[0118] In some aspects, a PP wireless device (such as wireless device 1002) may send at least one resource information message 1014 to an EH wireless device (e.g., EH wireless device 1004A or EH wireless device 1004B) based on the information 1008 about the EH wireless device, and the at least one resource information message may carry information indicating a preferred set of resources (e.g., time and frequency resources) for energy transfer. In some aspects, the information 1008 about the wireless device may be received from the EH wireless device 1004A, the EH wireless device 1004B, or the wireless device 1006. For example, the information 1008 may be received in a message 1008A from the wireless device 1004A. As another example, the information 1008 may be received in a message 1008B from the wireless device 1004B. As another example, the information 1008 may be received in a message 1008C from the wireless device 1006. The wireless device 1006 may have received the information 1008 in a message 1008D from the EH wireless device 1004B or in a message 1008E from the EH wireless device 1004A. In some aspects, the message 1008A, the message 1008B, the message 1008C, the message 1008D, or the message 1008E may be carried in the SCI.

[0119] In some aspects, the information 1008 may include distance, path loss, amount of transmitted power, charging rate, discharging rate, EH circuit, EH circuit architecture, RF to DC conversion efficiency η, EH parameters (such as charging band or charging frequency), charging rate for powering on or communicating, etc. In some aspects, at 1012, a preferred set of resources for energy transfer may be determined by a PP wireless device (e.g., wireless device 1002). The preferred set of resources for energy transfer may be determined based on a threshold (e.g., a resource-based metric greater than a threshold), which may be based on an expected energy at an EH wireless device (e.g., EH wireless device 1004A or EH wireless device 1004B). The threshold or metric may be based on one or more of a reference signal received power (RSRP), a received signal strength indicator (RSSI), a reference signal received quality (RSRQ), or a signal to noise plus interference ratio (SINR). In some aspects, the threshold may be determined by the EH wireless device (e.g., the EH wireless device 1004A or the EH wireless device 1004B) and sent to the PP wireless device when the EH wireless device RRC connects. In some aspects, the threshold may be based at least in part on information 1008, such as distance, path loss, amount of transmit power, charging rate, discharge rate, EH circuit, EH circuit architecture, RF to DC conversion efficiency η, EH parameters (such as charging band or charging frequency), charging rate for power-on or communication, etc. In some aspects, in addition to the preferred resources for energy transfer, the PP wireless device (e.g., the wireless device 1002) may also determine non-preferred resources for energy transfer at 1012 (e.g., based on a threshold, such as a metric including RSRP, RSSI, or RSSI below a threshold) and send information indicating the non-preferred resources for energy transfer (e.g., as part of at least one resource information message 1014). In some aspects, the at least one resource information message 1014 may be sent from the wireless device 1002 to the wireless device 1004A in a message 1014A. In some aspects, at least one resource information message 1014 may be sent from wireless device 1002 to wireless device 1004B in message 1014B. In some aspects, at least one resource information message 1014 may be sent from wireless device 1002 to wireless device 1006 in message 1014C. Wireless device 1006 may in turn send at least one resource information message 1014 to wireless device 1004A in message 1014E or send at least one resource information message 1014 to wireless device 1004B in message 1014D. In some aspects, message 1014A, message 1014B, message 1014C, message 1014D, or message 1014E may be carried in an SCI.

[0120] In some aspects, the preferred resources for energy transfer may provide sufficient energy for the EH wireless device (e.g., the EH wireless device 1004A or the EH wireless device 1004B), and the non-preferred resources for energy transfer may provide insufficient energy for the EH wireless device. In some aspects, the threshold may be determined so that the charging rate can meet the minimum input power at the EH wireless device. In some aspects, the EH wireless device may transmit a request for the charging rate to the PP wireless device (or another wireless device). In some aspects, different charging rates may be mapped to thresholds of different values. In some aspects, the requested charging rate may be changed dynamically (e.g., in layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling, where L1 can be a PHY layer, L2 can be a MAC layer or a logical link control layer, and L3 can be a network layer). The L1 signaling can be control information, the L2 signaling can be MAC-CE, and the L3 signaling can be RRC signaling.

[0121] In some aspects, in place of the wireless device 1002, the non-EH wireless device 1006 may also determine preferred or non-preferred resources for energy transfer at 1012 and send at least one resource information message 1014, which may include information indicating preferred or non-preferred resources for energy transfer for one or more EH wireless devices (e.g., wireless device 1004A or wireless device 1004B). In some aspects, the wireless device 1002 may send at least one resource information message 1014 to the non-EH wireless device 1006, which may include preferred or non-preferred resources for energy transfer for one or more EH wireless devices (e.g., wireless device 1004A or wireless device 1004B). In some aspects, the preferred or non-preferred resources for energy transfer for the wireless device 1004A may be different or the same as the preferred or non-preferred resources for the wireless device 1004B. In some aspects, at least one resource information message 1014 may include preferred or non-preferred resources for energy transfer of the wireless device 1004A or preferred or non-preferred resources for the wireless device 1004B in the same information or different information. In some aspects, the wireless device 1002 or the non-EH wireless device 1006 may power one or more EH wireless devices (e.g., the wireless device 1004A or the wireless device 1004B). In some aspects, the preferred resources for energy transfer may carry data communications that are not intended for one or more EH wireless devices (e.g., the wireless device 1004A or the wireless device 1004B) and may still be preferred for energy transfer. In some aspects, the wireless device 1002 or the wireless device 1006 may also determine (e.g., at 1012) preferred resources for data communication of one or more EH wireless devices (e.g., the wireless device 1004A or the wireless device 1004B) or non-preferred resources for data communication based on another threshold (e.g., which may also be determined based on the information 1008, such as distance, path loss, amount of transmitted power, charging rate, discharging rate, EH circuit, EH circuit architecture, RF to DC conversion efficiency η, EH parameters (such as charging band or charging frequency), charging rate for powering up or communicating, etc.). For example, in some examples where the preferred resources for energy transfer carry data communication that is not intended for the one or more EH wireless devices, these resources may be preferred for energy transfer but may not be preferred for data communication of the one or more EH wireless devices.

[0122] In some aspects, there may be a dedicated master device, such as wireless device 1002 or another device (e.g., which may be a dedicated node, a programmable logic controller (PLC), a primary UE, a master UE, a base station, or other device) that may be responsible for determining a threshold, determining preferred or non-preferred resources, or sending at least one resource information message 1014 (after receiving information about the EH wireless device and the PP wireless device).

[0123] Fig.11 1100 is a diagram illustrating example threshold values. Fig.11 As shown, RSRP thresholds are included as examples. In some aspects, the RSRP threshold used to determine preferred or non-preferred resources for energy transfer resources may be greater than, equal to, or less than the RSRP threshold used to determine preferred or non-preferred resources for data communication. For example, the RSRP threshold used for energy transfer may be based on whether the energy signal is generated based on a configuration known to the EH wireless device, so that the receiver can eliminate the energy signal. For example, if the energy signal is generated based on a configuration known to the EH wireless device, the energy signal can still be transmitted even if there is data about the current resource or conflict. As Fig.11 As shown, 1102 may be an RSRP threshold for determining whether a resource is preferred for data communication of a first EH wireless device. RSRP threshold 1104 may be a delta value between an RSRP threshold for determining whether a resource is preferred for data communication and an RSRP threshold for determining whether a resource is preferred for energy transfer. There may be different RSRP thresholds 1108 and RSRP thresholds 1110 for determining whether a resource is preferred for energy transfer of other EH wireless devices. In some aspects, the RSRP threshold for determining a preferred resource for energy transfer may be greater than or equal to the RSRP threshold for determining a preferred resource for data communication because the EH wireless device may use higher energy for efficient charging.

[0124] In some aspects, at 1012, the wireless device 1002 or the wireless device 1006 may determine the preferred or non-preferred resources for energy transfer after determining the preferred or non-preferred resources for data communication and based on the preferred or non-preferred resources for data communication. In some aspects, at 1012, the wireless device 1002 or the wireless device 1006 may determine the preferred or non-preferred resources for data communication after determining the preferred or non-preferred resources for energy transfer and based on the preferred or non-preferred resources for energy transfer.

[0125] In some aspects, the RSRP threshold for determining a preferred or non-preferred resource for energy transfer resources or the RSRP threshold for determining a preferred or non-preferred resource for data communication may be based on a priority or quality of service (QoS) 1010 of the data communication. In some aspects, the intended recipient of the data communication may be different from one or more EH wireless devices. In some aspects, the priority or QoS 1010 may be sent from the wireless device 1004A to the wireless device 1002 in a message 1010A. In some aspects, the priority or QoS 1010 may be sent from the wireless device 1004B to the wireless device 1002 in a message 1010B. In some aspects, the priority or QoS 1010 may be sent from the wireless device 1006 to the wireless device 1002 in a message 1010C. The wireless device 1006 may receive the priority or QoS 1010 from the wireless device 1004A in a message 1011E, or from the wireless device 1004B in a message 1010F. In some aspects, the priority or QoS 1010 may be sent from another wireless device 1050 to the wireless device 1002. In some aspects, the message 1010A, the message 1010B, the message 1010C, the message 1010D, the message 1010E, or the message 1010F may be carried in the SCI.

[0126] In some aspects, the remaining packet delay budget for data communication may be indicated to the wireless device 1002 or the wireless device 1006 (e.g., via SCI 1 or SCI 2). In some aspects, the remaining packet delay budget for data at the EH wireless device may be signaled from the EH device to the wireless device 1002 or the wireless device 1006.

[0127] In some aspects, the RSRP threshold used to determine preferred or non-preferred resources for energy transfer resources or the RSRP threshold used to determine preferred or non-preferred resources for data communication may also be based on the charging rate to be used at the EH wireless device.

[0128] In some aspects, based on at least one resource information message 1014, one or more EH wireless devices (e.g., wireless device 1004A or wireless device 1004B) may use information indicating preferred or non-preferred resources for energy transfer or data communication at 1018 to: 1) avoid energy resources that are not preferred (e.g., as if the energy resource is data where conflicts are not allowed because the data receiver may not be able to parse the data from the energy), 2) eliminate energy signals that may be non-preferred (e.g., based on knowing the energy resource configuration), or 3) use resources for energy transfer or data communication (e.g., resources used to carry the transmission). In some aspects, at least one resource information message 1014 may be sent based on an SCI. In some aspects, the SCI associated with the transmission may indicate whether the transmission is an energy signal or a data signal. In some aspects, the SCI may be used to broadcast the configuration of energy resources to enable elimination by the EH wireless device. In some aspects, the sending of at least one resource information message 1014 or the determination of non-preferred or preferred resources may be triggered by a request (e.g., request or report 1011), which may be sent in layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling, where L1 may be a PHY layer, L2 may be a MAC layer or a logical link control layer, and L3 may be a network layer. L1 signaling may be control information, L2 signaling may be MAC-CE, and L3 signaling may be RRC signaling. In some aspects, the request or report 1011 may be sent from the wireless device 1004A to the wireless device 1002 in message 1011A. In some aspects, the request or report 1011 may be sent from the wireless device 1004B to the wireless device 1002 in message 1011B. In some aspects, the request or report 1011 may be sent from the wireless device 1006 to the wireless device 1002 in message 1011C. Wireless device 1006 may receive request or report 1011 in message 1011E from wireless device 1004A or in message 1011D from wireless device 1004B. In some aspects, message 1011A, message 1011B, message 1011C, message 1011D, or message 1011E may be carried in an SCI.

[0129] In some aspects, the sending of at least one resource information message 1014 or the determination of non-preferred or preferred resources may be triggered based on information about one or more conditions associated with the EH wireless device (which may be included in the request or report 1011). The one or more conditions may include at least one of a decrease or increase in charging rate by a certain amount (e.g., the request or report 1011 may include charging rate information), a decrease or increase in discharging rate by a certain amount (e.g., the request or report 1011 may include discharging rate information), movement to another location or area of ​​the PP wireless device or the EH wireless device (e.g., may include movement information), or a change in an EH parameter such as an operating band, frequency range, RF tuning, or BW or resource pool (e.g., the request or report 1011 may include radio operation change information). The term "radio operation change" may refer to at least one of a change in operating band, a change in frequency range or RF tuning, a change in BW or resource pool, etc. The term "charge rate change information" may refer to a charge rate change, a predicted charge rate change, statistics related to a charge rate change, or time information (e.g., a timestamp or duration) associated with a charge rate change or a predicted charge rate change. The term "discharge rate change information" may refer to a discharge rate change, a predicted discharge rate change, statistics related to a discharge rate change, or time information (e.g., a timestamp or duration) associated with a discharge rate change or a predicted discharge rate change.

[0130] In some aspects, at least one resource information message 1014 may be a multiplexed message including an inter-UE coordination message. In some aspects, at least one resource information message 1014 may include information indicating preferred resources for energy transfer and preferred resources for data communication. In some aspects, at least one resource information message 1014 may include information indicating non-preferred resources for energy transfer and information indicating preferred resources for data communication. In some aspects, at least one resource information message 1014 may include preferred information indicating preferred resources for energy transfer and information indicating non-preferred resources for data communication. In some aspects, at least one resource information message 1014 may include information indicating non-preferred resources for energy transfer and information indicating non-preferred resources for data communication. In some aspects, the information may be multiplexed before encoding (e.g., in the raw bit level) or after encoding (e.g., in the RE or RB allocation level or in the RB set allocated for different information). In some aspects, at least one resource information message 1014 may include information indicating preferred or non-preferred resources for energy transfer or information indicating preferred or non-preferred resources for data communication. In some aspects, separate messages of 1014 may be transmitted to different EH wireless devices, such as wireless device 1004A and wireless device 1004B. In some aspects, at least one resource information message 1014 may include one or more bits to distinguish information indicating preferred or non-preferred resources for energy transfer from information indicating preferred or non-preferred resources for data communication.

[0131] Fig.12 1200 is a flow chart of a wireless communication method. The method may be performed by a first network entity (eg, UE 104, wireless device 1002, wireless device 1006, base station 102, network entity 1602, network entity 1702, apparatus 1604).

[0132] At 1210, the network entity may receive energy harvesting information associated with at least one second network entity. For example, the wireless device 1002 may receive energy harvesting information associated with at least one second network entity (e.g., wireless device 1004A or wireless device 1004B) (e.g., 1008). In some aspects, 1210 may be performed by the coordination component 198.

[0133] At 1230, the network entity may send first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer to at least one second network entity, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information, and wherein the first threshold is independent of the second threshold for data communication. For example, the wireless device 1002 may send first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer to at least one second network entity (e.g., in a resource information message 1014), wherein the first set of preferred resources is associated with a first metric that is above the first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, 1230 may be performed by coordination component 198.

[0134] Fig.13 1300 is a flow chart of a wireless communication method. The method may be performed by a first network entity (eg, UE 104, wireless device 1002, wireless device 1006, base station 102, network entity 1602, network entity 1702, apparatus 1604).

[0135] At 1310, the network entity may receive energy harvesting information associated with at least one second network entity. For example, the wireless device 1002 may receive energy harvesting information (e.g., 1008) associated with at least one second network entity (e.g., the wireless device 1004A or the wireless device 1004B). In some aspects, 1310 may be performed by the coordination component 198. In some aspects, the energy harvesting information includes one or more of: information about at least one energy harvesting circuit associated with the at least one second network entity, at least one efficiency associated with the at least one second network entity, at least one charging band or at least one charging frequency associated with the at least one second network entity, or at least one specified charging rate associated with the at least one second network entity.

[0136] At 1314, the network entity may determine a first threshold based on the energy harvesting information. For example, the wireless device 1002 may determine the first threshold based on the energy harvesting information (e.g., as part of 1012). In some aspects, 1314 may be performed by the coordination component 198. In some aspects, the first threshold is based on one or more of: at least one priority or at least one quality of service (QoS) associated with at least one transmission enabled by energy transfer or at least one specified charging rate. In some aspects, the network entity may receive at least one priority or at least one QoS associated with at least one transmission via signaling from at least one second network entity or a separate SCI. In some aspects, at 1312, the network entity (e.g., the wireless device 1002) may receive at least one priority or at least one QoS associated with at least one transmission via signaling from at least one second network entity (e.g., 1010A or 1010B) or a separate SCI (e.g., 1010D). In some aspects, 1312 may be performed by the coordination component 198.

[0137] At 1316, the network entity can determine a first set of preferred resources for energy transfer and a first set of non-preferred resources for energy transfer. For example, the wireless device 1002 can determine (e.g., as part of 1012) a first set of preferred resources for energy transfer and a first set of non-preferred resources for energy transfer. In some aspects, 1316 can be performed by the coordination component 198.

[0138] At 1318, the network entity may determine, for at least one second network entity, a second set of preferred resources for data communication or a second set of non-preferred resources for data communication, wherein the second set of preferred resources for data communication is associated with a third metric above a second threshold, and wherein the second set of non-preferred resources for data communication is associated with a fourth metric below the second threshold. For example, the wireless device 1002 may determine (e.g., as part of 1012) a second set of preferred resources for data communication or a second set of non-preferred resources for data communication for at least one second network entity, wherein the second set of preferred resources for data communication is associated with a third metric above a second threshold, and wherein the second set of non-preferred resources for data communication is associated with a fourth metric below the second threshold. In some aspects, 1318 may be performed by the coordination component 198. In some aspects, the metric is one of a reference signal received power (RSRP), a received signal strength indicator (RSSI), a reference signal received quality (RSRQ), or a signal to noise plus interference ratio (SINR). In some aspects, RSRP, RSSI, RSRQ, or SINR may be associated with L1 or L3.

[0139] In some aspects, the network entity may determine the first set of preferred resources for energy transfer and the first set of non-preferred resources for energy transfer based on the second set of preferred resources for data communication or the second set of non-preferred resources for data communication (e.g., after it). For example, the wireless device 1002 may determine the first set of preferred resources for energy transfer and the first set of non-preferred resources for energy transfer based on the second set of preferred resources for data communication or the second set of non-preferred resources for data communication (e.g., after it). In some aspects, in order to determine the second set of preferred resources for data communication or the second set of non-preferred resources for data communication, the network entity may determine the second set of preferred resources for data communication or the second set of non-preferred resources for data communication based on the first set of preferred resources for energy transfer and the first set of non-preferred resources for energy transfer (e.g., after it). For example, the wireless device 1002 may determine the second set of preferred resources for data communication or the second set of non-preferred resources for data communication based on the first set of preferred resources for energy transfer and the first set of non-preferred resources for energy transfer (e.g., after it).

[0140] In some aspects, the first information or the second information may be sent via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling based on the request (e.g., 1011). L1 may be a PHY layer, L2 may be a MAC layer or a logical link control layer, and L3 may be a network layer. L1 signaling may be control information, L2 signaling may be MAC-CE, and L3 signaling may be RRC signaling.

[0141] At 1320, the network entity may receive at least one report indicating charging rate change information, discharging rate change information, moving information, or radio operation change information via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling. For example, the wireless device 1002 may receive at least one report (e.g., 1011) indicating charging rate change information, discharging rate change information, moving information, or radio operation change information via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling. In some aspects, 1320 may be performed by the coordination component 198. In some aspects, the network entity may send the first information based on the charging rate change information, the discharging rate change information, the moving information, or the radio operation change information.

[0142] At 1330, the network entity may send first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer to at least one second network entity, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information, and wherein the first threshold is independent of the second threshold for data communication. For example, the wireless device 1002 may send first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer to at least one second network entity (e.g., in a resource information message 1014), wherein the first set of preferred resources is associated with a first metric that is above the first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, 1330 may be performed by coordination component 198. In some aspects, to send the first information, the network entity may send the first information to at least one second network entity (e.g., wireless device 1004A or wireless device 1004B) or a third network entity (e.g., wireless device 1006), wherein the at least one second network entity is at least one energy harvesting network entity and the third network entity is a non-energy harvesting network entity.

[0143] At 1332, the network entity may send second information indicating a second set of preferred resources for data communication or a second set of non-preferred resources for data communication. For example, the wireless device 1002 may send (e.g., in at least one resource information message 1014) second information indicating a second set of preferred resources for data communication or a second set of non-preferred resources for data communication. In some aspects, 1332 may be performed by the coordination component 198. In some aspects, the network entity may send the second information indicating the second set of preferred resources for data communication or the second set of non-preferred resources for data communication to at least one second network entity (e.g., wireless device 1004A or wireless device 1004B). In some aspects, the network entity may send the second information to at least one second network entity (e.g., wireless device 1004A or wireless device 1004B) or a third network entity (e.g., wireless device 1006), wherein the at least one second network entity is at least one energy harvesting network entity and the third network entity is a non-energy harvesting network entity. In some aspects, at least one second network entity corresponds to a single network entity (e.g., one of the wireless device 1004A or the wireless device 1004B), and the network entity may multiplex the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of preferred resources for energy transfer, and wherein the second information indicates a second set of preferred resources for data communication. In some aspects, at least one second network entity corresponds to a single network entity (e.g., one of the wireless device 1004A or the wireless device 1004B), and the network entity may multiplex the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of non-preferred resources for energy transfer, and wherein the second information indicates a second set of preferred resources for data communication. In some aspects, at least one second network entity corresponds to a single network entity (e.g., one of the wireless device 1004A or the wireless device 1004B), and the network entity may multiplex the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of preferred resources for energy transfer, and wherein the second information indicates a second set of non-preferred resources for data communication. In some aspects, at least one second network entity corresponds to a single network entity (e.g., one of wireless device 1004A or wireless device 1004B), and the network entity may multiplex first information and second information at a bit level or a RE level, wherein the first information indicates a first set of non-preferred resources for energy transfer and wherein the second information indicates a second set of non-preferred resources for data communication.

[0144] Fig.14 1400 is a flow chart of a wireless communication method. The method may be performed by a first network entity (eg, UE 104, wireless device 1004A or wireless device 1004B, base station 102, network entity 1602, network entity 1702, apparatus 1604).

[0145] At 1410, the network entity may receive first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer from a second network entity, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information associated with the first network entity, and wherein the first threshold is independent of the second threshold for data communication. For example, the wireless device 1004A may receive first information (e.g., 1014) indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer from a second network entity, wherein the first set of preferred resources is associated with a first metric that is above the first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information associated with the first network entity, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, 1410 may be performed by coordination component 198.

[0146] At 1430, the network entity may apply the first set of preferred resources to energy harvesting or refrain from applying the first set of non-preferred resources to energy harvesting. For example, the wireless device 1004A may apply (e.g., at 1018) the first set of preferred resources to energy harvesting or refrain from applying the first set of non-preferred resources to energy harvesting. In some aspects, 1430 may be performed by the coordination component 198.

[0147] Fig.15 1500 is a flow chart of a wireless communication method. The method may be performed by a first network entity (eg, UE 104, wireless device 1004A or wireless device 1004B, base station 102, network entity 1602, network entity 1702, apparatus 1604).

[0148] At 1502, the network entity may send at least one priority or at least one QoS associated with at least one transmission to a second network entity. For example, the wireless device 1004A may (e.g., in 1010A) send at least one priority or at least one QoS associated with at least one transmission to the second network entity. In some aspects, 1502 may be performed by the coordination component 198.

[0149] At 1504, the network entity may send at least one report (e.g., 1011) indicating charging rate change information, discharging rate change information, movement information, or radio operation change information via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling. In some aspects, 1504 may be performed by coordination component 198.

[0150] At 1510, the network entity may receive first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer from a second network entity, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information associated with the first network entity, and wherein the first threshold is independent of the second threshold for data communication. For example, the wireless device 1004A may receive first information (e.g., 1014) indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer from a second network entity, wherein the first set of preferred resources is associated with a first metric that is above the first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information associated with the first network entity, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, 1510 may be performed by the coordination component 198. In some aspects, the metric may be one of a reference signal received power (RSRP), a received signal strength indicator (RSSI), or a signal to noise and interference ratio (SINR). In some aspects, the first threshold is based on one or more of: at least one priority or at least one quality of service (QoS) associated with at least one transmission enabled by the energy transfer or the specified charging rate. In some aspects, the energy harvesting information includes one or more of: information about an energy harvesting circuit associated with the first network entity, an efficiency associated with the first network entity, a charging band or charging frequency associated with the first network entity, or a specified charging rate associated with the first network entity.

[0151] At 1512, the network entity may receive second information from the second network entity indicating a second set of preferred resources for data communication or a second set of non-preferred resources for data communication, wherein the second set of preferred resources for data communication is associated with a third metric above a second threshold, and wherein the second set of non-preferred resources for data communication is associated with a fourth metric below the second threshold. For example, the wireless device 1004A may receive second information from the second network entity indicating a second set of preferred resources for data communication or a second set of non-preferred resources for data communication (e.g., in 1014), wherein the second set of preferred resources for data communication is associated with a third metric above a second threshold, and wherein the second set of non-preferred resources for data communication is associated with a fourth metric below the second threshold. In some aspects, 1512 may be performed by the coordination component 198.

[0152] At 1530, the network entity may apply the first set of preferred resources to energy harvesting or refrain from applying the first set of non-preferred resources to energy harvesting. For example, the wireless device 1004A may apply (e.g., at 1018) the first set of preferred resources to energy harvesting or refrain from applying the first set of non-preferred resources to energy harvesting. In some aspects, 1430 may be performed by the coordination component 198.

[0153] Fig.161600 is a diagram illustrating an example of a hardware implementation for an apparatus 1604. The apparatus 1604 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1604 may include a cellular baseband processor 1624 (also referred to as a modem) coupled to one or more transceivers 1622 (e.g., a cellular RF transceiver). The cellular baseband processor 1624 may include on-chip memory 1624'. In some aspects, the apparatus 1604 may also include one or more subscriber identity module (SIM) cards 1620 and an application processor 1606 coupled to a secure digital (SD) card 1608 and a screen 1610. The application processor 1606 may include on-chip memory 1606'. In some aspects, the device 1604 may also include a Bluetooth module 1612, a WLAN module 1614, a satellite system module 1616 (e.g., a GNSS module), one or more sensor modules 1618 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1626, a power source 1630, and / or a camera 1632. The Bluetooth module 1612, the WLAN module 1614, and the satellite system module 1616 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1624 communicates with the UE 104 and / or with a RU associated with the network entity 1602 through the transceiver 1622 via one or more antennas 1680. The cellular baseband processor 1624 and the application processor 1606 may each include a computer-readable medium / memory 1624', 1606', respectively. The additional memory module 1626 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1624', 1606', 1626 may be non-transitory. The cellular baseband processor 1624 and the application processor 1606 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1624 / application processor 1606, enables the cellular baseband processor 1624 / application processor 1606 to perform the various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1624 / application processor 1606 when executing the software. The cellular baseband processor 1624 / application processor 1606 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368 , the RX processor 356 , and the controller / processor 359 .In one configuration, the device 1604 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1624 and / or the application processor 1606, and in another configuration, the device 1604 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 1604.

[0154] As discussed herein, the coordination component 198 may be configured to receive energy harvesting information associated with at least one second network entity. In some aspects, the coordination component 198 may be further configured to send, for the at least one second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on the energy harvesting information, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, the coordination component 198 may be configured to receive, from the second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer, wherein the first set of preferred resources is associated with a first metric that is above the first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on the energy harvesting information associated with the first network entity, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, the coordination component 198 may be further configured to apply the first set of preferred resources for energy harvesting, or to refrain from applying the first set of non-preferred resources for energy harvesting. The coordination component 198 may be within the cellular baseband processor 1624, the application processor 1606, or within both the cellular baseband processor 1624 and the application processor 1606. The coordination component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the foregoing. As shown, the device 1604 may include a variety of components configured for various functions. In one configuration, the device 1604 (and in particular the cellular baseband processor 1624 and / or the application processor 1606) includes a component for receiving energy harvesting information associated with at least one second network entity. In some aspects, the apparatus 1604 may also include a component for sending, to at least one second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, the apparatus 1604 may also include a component for sending the first information based on a request via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling.In some aspects, the device 1604 may also include a component for sending the first information based on the charging rate change information, the discharging rate change information, the movement information, or the radio operation change information. In some aspects, the device 1604 may also include a component for receiving first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer from a second network entity, wherein the first set of preferred resources is associated with a first metric that is higher than a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is lower than the first threshold, wherein the first threshold is based on energy harvesting information associated with the first network entity, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, the device 1604 may also include a component for applying the first set of preferred resources to energy harvesting or suppressing the application of the first set of non-preferred resources to energy harvesting. In some aspects, the device 1604 may also include a component for determining the first threshold based on the energy harvesting information. In some aspects, the device 1604 may also include a component for determining a second set of preferred resources for data communication or a second set of non-preferred resources for data communication for at least one second network entity, wherein the second set of preferred resources for data communication is associated with a third metric above a second threshold, and wherein the second set of non-preferred resources for data communication is associated with a fourth metric below the second threshold. In some aspects, the device 1604 may also include a component for determining a first set of preferred resources for energy transfer and a first set of non-preferred resources for energy transfer based on (e.g., after) the second set of preferred resources for data communication or the second set of non-preferred resources for data communication. In some aspects, the device 1604 may also include a component for determining a second set of preferred resources for data communication or a second set of non-preferred resources for data communication based on (e.g., after) the first set of preferred resources for energy transfer and the first set of non-preferred resources for energy transfer. In some aspects, the device 1604 may also include a component for sending a second information indicating a second set of preferred resources for data communication or a second set of non-preferred resources for data communication for at least one second network entity. In some aspects, the device 1604 may also include a component for sending the second information to at least one second network entity or a third network entity, wherein the at least one second network entity is at least one energy harvesting network entity and the third network entity is a non-energy harvesting network entity. In some aspects, the device 1604 may also include a component for multiplexing the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of preferred resources for energy transfer, and wherein the second information indicates a second set of preferred resources for data communication. In some aspects, the device 1604 may also include a component for multiplexing the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of non-preferred resources for energy transfer, and wherein the second information indicates a second set of preferred resources for data communication.In some aspects, the device 1604 may also include a component for multiplexing the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of preferred resources for energy transfer, and wherein the second information indicates a second set of non-preferred resources for data communication. In some aspects, the device 1604 may also include a component for multiplexing the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of non-preferred resources for energy transfer, and wherein the second information indicates a second set of non-preferred resources for data communication. In some aspects, the device 1604 may also include a component for sending the first information to at least one second network entity or a third network entity, wherein the at least one second network entity is at least one energy harvesting network entity, and the third network entity is a non-energy harvesting network entity. In some aspects, the device 1604 may also include a component for receiving at least one priority or at least one QoS associated with at least one transmission via signaling from at least one second network entity or a separate SCI. In some aspects, the device 1604 may also include a component for receiving at least one priority or at least one QoS associated with at least one transmission via signaling from at least one second network entity or a separate SCI. In some aspects, the device 1604 may also include a component for receiving at least one report indicating charging rate change information, discharging rate change information, movement information, or radio operation change information via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling. In some aspects, the device 1604 may also include a component for receiving second information indicating a second set of preferred resources for data communication or a second set of non-preferred resources for data communication from a second network entity, wherein the second set of preferred resources for data communication is associated with a third metric above a second threshold, and wherein the second set of non-preferred resources for data communication is associated with a fourth metric below the second threshold. In some aspects, the device 1604 may also include a component for sending at least one priority or at least one QoS associated with at least one transmission to the second network entity. In some aspects, the device 1604 may also include a component for sending at least one report indicating charging rate change information, discharging rate change information, movement information, or radio operation change information via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling. The means may be a coordination component 198 of the apparatus 1604 configured to perform the functions recited by the means. As described herein, the apparatus 1604 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recited by the means.

[0155] Fig.171700 is a diagram illustrating an example of a hardware implementation for a network entity 1702. The network entity 1702 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1702 may include at least one of a CU 1710, a DU 1730, or a RU 1740. For example, depending on the layer functionality handled by the component 198, the network entity 1702 may include a CU 1710; both a CU 1710 and a DU 1730; each of the CU 1710, the DU 1730, and the RU 1740; the DU 1730; both a DU 1730 and a RU 1740; or a RU 1740. The CU 1710 may include a CU processor 1712. The CU processor 1712 may include an on-chip memory 1712'. In some aspects, the CU 1710 may also include an additional memory module 1714 and a communication interface 1718. CU 1710 communicates with DU 1730 via a midhaul link, such as an F1 interface. DU 1730 may include a DU processor 1732. DU processor 1732 may include on-chip memory 1732'. In some aspects, DU 1730 may also include additional memory modules 1734 and a communication interface 1738. DU 1730 communicates with RU 1740 via a fronthaul link. RU 1740 may include a RU processor 1742. RU processor 1742 may include on-chip memory 1742'. In some aspects, RU 1740 may also include additional memory modules 1744, one or more transceivers 1746, antenna 1780, and communication interface 1748. RU 1740 communicates with UE 104. On-chip memory 1712', 1732', 1742' and additional memory modules 1714, 1734, 1744 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1712, 1732, 1742 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described herein. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0156] As discussed herein, the coordination component 198 may be configured to receive energy harvesting information associated with at least one second network entity. In some aspects, the coordination component 198 may be further configured to send, for the at least one second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on the energy harvesting information, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, the coordination component 198 may be configured to receive, from the second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer, wherein the first set of preferred resources is associated with a first metric that is above the first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on the energy harvesting information associated with the first network entity, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, the coordination component 198 may be further configured to apply the first set of preferred resources for energy harvesting, or to refrain from applying the first set of non-preferred resources for energy harvesting. The coordination component 198 may be within one or more processors of one or more of the CU 1710, the DU 1730, and the RU 1740. The coordination component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. The network entity 1702 may include a variety of components configured for various functions. In one configuration, the network entity 1702 may include a component for receiving energy harvesting information associated with at least one second network entity. In some aspects, the network entity 1702 may also include a component for sending a first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer to the at least one second network entity, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on the energy harvesting information, and wherein the first threshold is independent of the second threshold for data communication. In some aspects, the network entity 1702 may also include a component for sending the first information based on the request via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling. In some aspects, the network entity 1702 may also include a component for sending the first information based on the charging rate change information, the discharging rate change information, the movement information, or the radio operation change information.In some aspects, the network entity 1702 may also include a component for receiving first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer from a second network entity, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information associated with the first network entity, and wherein the first threshold is independent of a second threshold for data communication. In some aspects, the network entity 1702 may also include a component for applying the first set of preferred resources to energy harvesting or refraining from applying the first set of non-preferred resources to energy harvesting. In some aspects, the network entity 1702 may also include a component for determining the first threshold based on the energy harvesting information. In some aspects, the network entity 1702 may also include a component for determining a second set of preferred resources for data communication or a second set of non-preferred resources for data communication for at least one second network entity, wherein the second set of preferred resources for data communication is associated with a third metric that is above the second threshold, and wherein the second set of non-preferred resources for data communication is associated with a fourth metric that is below the second threshold. In some aspects, the network entity 1702 may also include a component for determining a first set of preferred resources for energy transfer and a first set of non-preferred resources for energy transfer based on (e.g., after) a second set of preferred resources for data communication or a second set of non-preferred resources for data communication. In some aspects, the network entity 1702 may also include a component for determining a second set of preferred resources for data communication and a second set of non-preferred resources for data communication based on (e.g., after) a first set of preferred resources for energy transfer or a first set of non-preferred resources for energy transfer. In some aspects, the network entity 1702 may also include a component for sending second information indicating a second set of preferred resources for data communication or a second set of non-preferred resources for data communication to at least one second network entity. In some aspects, the network entity 1702 may also include a component for sending second information to at least one second network entity or a third network entity, wherein the at least one second network entity is at least one energy harvesting network entity and the third network entity is a non-energy harvesting network entity. In some aspects, the network entity 1702 may also include a component for multiplexing the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of preferred resources for energy transfer, and wherein the second information indicates a second set of preferred resources for data communication. In some aspects, the network entity 1702 may also include a component for multiplexing the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of non-preferred resources for energy transfer, and wherein the second information indicates a second set of preferred resources for data communication.In some aspects, the network entity 1702 may also include a component for multiplexing the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of preferred resources for energy transfer, and wherein the second information indicates a second set of non-preferred resources for data communication. In some aspects, the network entity 1702 may also include a component for multiplexing the first information and the second information at a bit level or a RE level, wherein the first information indicates a first set of non-preferred resources for energy transfer, and wherein the second information indicates a second set of non-preferred resources for data communication. In some aspects, the network entity 1702 may also include a component for sending the first information to at least one second network entity or a third network entity, wherein the at least one second network entity is at least one energy harvesting network entity, and the third network entity is a non-energy harvesting network entity. In some aspects, the network entity 1702 may also include a component for receiving at least one priority or at least one QoS associated with at least one transmission via signaling or a separate SCI from at least one second network entity. In some aspects, the network entity 1702 may also include a component for receiving at least one priority or at least one QoS associated with at least one transmission via signaling or a separate SCI from at least one second network entity. In some aspects, the network entity 1702 may also include a component for receiving at least one report indicating charging rate change information, discharging rate change information, movement information, or radio operation change information via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling. In some aspects, the network entity 1702 may also include a component for receiving second information indicating a second set of preferred resources for data communication or a second set of non-preferred resources for data communication from a second network entity, wherein the second set of preferred resources for data communication is associated with a third metric above a second threshold, and wherein the second set of non-preferred resources for data communication is associated with a fourth metric below the second threshold. In some aspects, the network entity 1702 may also include a component for sending at least one priority or at least one QoS associated with at least one transmission to the second network entity. In some aspects, the network entity 1702 may also include a component for sending at least one report indicating charging rate change information, discharging rate change information, movement information, or radio operation change information via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling. The means may be a coordination component 198 of the network entity 1702 configured to perform the functions recited by the means. As described herein, the network entity 1702 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the means.

[0157] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0158] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0159] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0160] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0161] Aspect 1 is a first network entity for wireless communication, the first network entity comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: receive energy harvesting information associated with at least one second network entity; and send first information indicating a first group of preferred resources for energy transfer or a first group of non-preferred resources for the energy transfer to the at least one second network entity, wherein the first group of preferred resources is associated with a first metric that is higher than a first threshold for energy harvesting, wherein the first group of non-preferred resources is associated with a second metric that is lower than the first threshold, wherein the first threshold is based on the energy harvesting information, and wherein the first threshold is independent of a second threshold for data communication.

[0162] Aspect 2 is the first network entity according to aspect 1, wherein the at least one processor is configured to: determine the first threshold based on the energy harvesting information.

[0163] Aspect 3 is a first network entity according to any one of Aspects 1-2, wherein the at least one processor is configured to: determine a second set of preferred resources for the data communication or a second set of non-preferred resources for the data communication for the at least one second network entity, wherein the second set of preferred resources for the data communication is associated with a third metric higher than the second threshold, and wherein the second set of non-preferred resources for the data communication is associated with a fourth metric lower than the second threshold.

[0164] Aspect 4 is a first network entity according to any one of aspects 1-3, wherein each of the first metric, the second metric, the third metric, or the fourth metric is one of a reference signal received power (RSRP), a received signal strength indicator (RSSI), or a signal to noise and interference ratio (SINR).

[0165] Aspect 5 is a first network entity according to any one of Aspects 1-4, wherein the at least one processor is configured to: determine the first group of preferred resources for the energy transfer and the first group of non-preferred resources for the energy transfer based on the second group of preferred resources for the data communication or the second group of non-preferred resources for the data communication.

[0166] Aspect 6 is a first network entity according to any one of Aspects 1-4, wherein, in order to determine the second group of preferred resources for the data communication or the second group of non-preferred resources for the data communication, the at least one processor is configured to: determine the second group of preferred resources for the data communication or the second group of non-preferred resources for the data communication based on the first group of preferred resources for the energy transfer and the first group of non-preferred resources for the energy transfer.

[0167] Aspect 7 is a first network entity according to any one of Aspects 1-6, wherein the at least one processor is configured to: send second information indicating the second set of preferred resources for the data communication or the second set of non-preferred resources for the data communication to the at least one second network entity.

[0168] Aspect 8 is a first network entity according to any one of Aspects 1-7, wherein, in order to send the second information, the at least one processor is configured to: send the second information to the at least one second network entity or the third network entity, wherein the at least one second network entity is at least one energy harvesting network entity, and the third network entity is a non-energy harvesting network entity.

[0169] Aspect 9 is a first network entity according to any one of Aspects 1-8, wherein the at least one second network entity corresponds to a single network entity, and wherein, in order to send the first information and the second information, the at least one processor is configured to: multiplex the first information and the second information at a bit level or a resource element (RE) level, wherein the first information indicates the first group of preferred resources for the energy transfer, and wherein the second information indicates the second group of preferred resources for the data communication.

[0170] Aspect 10 is a first network entity according to any one of Aspects 1-8, wherein the at least one second network entity corresponds to a single network entity, and wherein the at least one processor is configured to: multiplex the first information and the second information at a bit level or a resource element (RE) level, wherein the first information indicates the first group of non-preferred resources for the energy transfer, and wherein the second information indicates the second group of preferred resources for the data communication.

[0171] Aspect 11 is a first network entity according to any one of Aspects 1-8, wherein the at least one second network entity corresponds to a single network entity, and wherein the at least one processor is configured to: multiplex the first information and the second information at a bit level or a resource element (RE) level, wherein the first information indicates the first group of preferred resources for the energy transfer, and wherein the second information indicates the second group of non-preferred resources for the data communication.

[0172] Aspect 12 is a first network entity according to any one of Aspects 1-8, wherein the at least one second network entity corresponds to a single network entity, and wherein the at least one processor is configured to: multiplex the first information and the second information at a bit level or a resource element (RE) level, wherein the first information indicates the first set of non-preferred resources for the energy transfer, and wherein the second information indicates the second set of non-preferred resources for the data communication.

[0173] Aspect 13 is a first network entity according to any one of Aspects 1-12, wherein, in order to send the first information, the at least one processor is configured to: send the first information to the at least one second network entity or the third network entity, wherein the at least one second network entity is at least one energy harvesting network entity, and the third network entity is a non-energy harvesting network entity.

[0174] Aspect 14 is a first network entity according to any one of Aspects 1-13, wherein the energy harvesting information includes one or more of the following: information about at least one energy harvesting circuit associated with the at least one second network entity, at least one efficiency associated with the at least one second network entity, at least one charging band or at least one charging frequency associated with the at least one second network entity, or at least one specified charging rate associated with the at least one second network entity.

[0175] Aspect 15 is a first network entity according to any one of Aspects 1-14, wherein the first threshold is based on one or more of the following: at least one priority or at least one quality of service (QoS) associated with at least one transmission enabled by the energy transfer or the at least one specified charging rate.

[0176] Aspect 16 is a first network entity according to any one of Aspects 1-15, wherein the at least one processor is configured to: receive the at least one priority or the at least one QoS associated with the at least one transmission via signaling or separate sidelink control information (SCI) from the at least one second network entity.

[0177] Aspect 17 is the first network entity according to any one of aspects 1-16, wherein the second threshold is based on one or more of: at least one priority or at least one quality of service (QoS) associated with the data communication.

[0178] Aspect 18 is a first network entity according to any one of Aspects 1-17, wherein, in order to send the first information, the at least one processor is configured to send the first information based on a request via layer 1 (L1) signaling, layer 2 (L2) signaling or layer 3 (L3) signaling.

[0179] Aspect 19 is a first network entity according to any one of Aspects 1-18, wherein the at least one processor is configured to: receive at least one report indicating charging rate change information, discharging rate change information, moving information or radio operation change information via layer 1 (L1) signaling, layer 2 (L2) signaling or layer 3 (L3) signaling; and send the first information based on the charging rate change information, the discharging rate change information, the moving information or the radio operation change information.

[0180] Aspect 20 is a first network entity according to any one of aspects 1-19, wherein the first metric is one of a reference signal received power (RSRP), a received signal strength indicator (RSSI), or a signal to noise and interference ratio (SINR).

[0181] Aspect 21 is a first network entity for wireless communication, the first network entity comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: receive first information indicating a first group of preferred resources for energy transfer or a first group of non-preferred resources for the energy transfer from a second network entity, wherein the first group of preferred resources is associated with a first metric that is higher than a first threshold for energy harvesting, wherein the first group of non-preferred resources is associated with a second metric that is lower than the first threshold, wherein the first threshold is based on energy harvesting information associated with the first network entity, and wherein the first threshold is independent of a second threshold for data communication; and apply the first group of preferred resources to the energy harvesting, or suppress the application of the first group of non-preferred resources to the energy harvesting.

[0182] Aspect 22 is a first network entity according to Aspect 21, wherein the at least one processor is configured to: receive second information indicating a second set of preferred resources for the data communication or a second set of non-preferred resources for the data communication from the second network entity, wherein the second set of preferred resources for the data communication is associated with a third metric above the second threshold, and wherein the second set of non-preferred resources for the data communication is associated with a fourth metric below the second threshold.

[0183] Aspect 23 is a first network entity according to any one of Aspects 21-22, wherein each of the first metric, the second metric, the third metric or the fourth metric is one of a reference signal received power (RSRP), a received signal strength indicator (RSSI) or a signal to noise and interference ratio (SINR).

[0184] Aspect 24 is a first network entity according to any one of Aspects 21-23, wherein the energy harvesting information includes one or more of the following: information about at least one energy harvesting circuit associated with the first network entity, efficiency associated with the first network entity, a charging band or charging frequency associated with the first network entity, or a specified charging rate associated with the first network entity.

[0185] Aspect 25 is a first network entity according to any one of Aspects 21-24, wherein the first threshold is based on one or more of: at least one priority or at least one quality of service (QoS) associated with at least one transmission enabled by the energy transfer or the specified charging rate.

[0186] Aspect 26 is a first network entity according to any one of aspects 21-25, wherein the at least one processor is configured to: send the at least one priority or the at least one QoS associated with the at least one transmission to the second network entity.

[0187] Aspect 27 is a first network entity according to any one of Aspects 21-26, wherein the at least one processor is configured to: send at least one report indicating charging rate change information, discharging rate change information, movement information, or radio operation change information via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling.

[0188] Aspect 28 is a first network entity according to any one of aspects 21-27, wherein the first metric is one of a reference signal received power (RSRP), a received signal strength indicator (RSSI), or a signal to noise and interference ratio (SINR).

[0189] Aspect 29 is a method for wireless communication implementing any one of aspects 1 to 20.

[0190] Aspect 30 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 20.

[0191] Aspect 31 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 20.

[0192] Aspect 32 is a method for implementing wireless communication of any one of aspects 21 to 28.

[0193] Aspect 33 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 21 to 28.

[0194] Aspect 34 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 21 to 28.

Claims

1. A first network entity for wireless communication, the first network entity comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving energy harvesting information associated with at least one second network entity; as well as First information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for the energy transfer is sent to the at least one second network entity, wherein the first set of preferred resources is associated with a first metric that is higher than a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is lower than the first threshold, wherein the first threshold is based on the energy harvesting information, and wherein the first threshold is independent of a second threshold for data communication.

2. The first network entity according to claim 1, wherein the at least one processor is configured to: The first threshold is determined based on the energy harvesting information.

3. The first network entity according to claim 1, wherein the at least one processor is configured to: A second set of preferred resources for the data communication or a second set of non-preferred resources for the data communication is determined for the at least one second network entity, wherein the second set of preferred resources for the data communication is associated with a third metric above the second threshold, and wherein the second set of non-preferred resources for the data communication is associated with a fourth metric below the second threshold.

4. The first network entity of claim 3, wherein each of the first metric, the second metric, the third metric, or the fourth metric is one of a reference signal received power (RSRP), a received signal strength indicator (RSSI), or a signal to noise and interference ratio (SINR).

5. The first network entity according to claim 3, wherein the at least one processor is configured to: The first set of preferred resources for the energy transfer and the first set of non-preferred resources for the energy transfer are determined based on the second set of preferred resources for the data communication or the second set of non-preferred resources for the data communication.

6. The first network entity according to claim 3, wherein: To determine the second set of preferred resources for the data communication or the second set of non-preferred resources for the data communication, the at least one processor is configured to: The second set of preferred resources for the data communication or the second set of non-preferred resources for the data communication is determined based on the first set of preferred resources for the energy transfer and the first set of non-preferred resources for the energy transfer.

7. The first network entity according to claim 3, wherein the at least one processor is configured to: Second information indicating the second set of preferred resources for the data communication or the second set of non-preferred resources for the data communication is sent to the at least one second network entity.

8. The first network entity according to claim 7, wherein: To send the second information, the at least one processor is configured to: The second information is sent to the at least one second network entity or a third network entity, wherein the at least one second network entity is at least one energy harvesting network entity and the third network entity is a non-energy harvesting network entity.

9. The first network entity of claim 7, wherein the at least one second network entity corresponds to a single network entity, and wherein: To send the first information and the second information, the at least one processor is configured to: The first information and the second information are multiplexed at a bit level or a resource element (RE) level, wherein the first information indicates the first set of preferred resources for the energy transfer, and wherein the second information indicates the second set of preferred resources for the data communication.

10. The first network entity of claim 7, wherein the at least one second network entity corresponds to a single network entity, and wherein the at least one processor is configured to: The first information and the second information are multiplexed at a bit level or a resource element (RE) level, wherein the first information indicates the first group of non-preferred resources for the energy transfer, and wherein the second information indicates the second group of preferred resources for the data communication.

11. The first network entity of claim 7, wherein the at least one second network entity corresponds to a single network entity, and wherein the at least one processor is configured to: The first information and the second information are multiplexed at a bit level or a resource element (RE) level, wherein the first information indicates the first set of preferred resources for the energy transfer, and wherein the second information indicates the second set of non-preferred resources for the data communication.

12. The first network entity of claim 7, wherein the at least one second network entity corresponds to a single network entity, and wherein the at least one processor is configured to: The first information and the second information are multiplexed at a bit level or a resource element (RE) level, wherein the first information indicates the first group of non-preferred resources for the energy transfer, and wherein the second information indicates the second group of non-preferred resources for the data communication.

13. The first network entity according to claim 1, wherein: To send the first information, the at least one processor is configured to: The first information is sent to the at least one second network entity or a third network entity, wherein the at least one second network entity is at least one energy harvesting network entity and the third network entity is a non-energy harvesting network entity.

14. The first network entity according to claim 1, wherein the energy harvesting information comprises one or more of the following: information about at least one energy harvesting circuit associated with the at least one second network entity, at least one efficiency associated with the at least one second network entity, At least one charging frequency band or at least one charging frequency associated with the at least one second network entity, or at least one specified charging rate associated with the at least one second network entity.

15. The first network entity of claim 14, wherein the first threshold is based on one or more of: at least one priority or at least one quality of service (QoS) associated with at least one transmission enabled by the energy transfer or the at least one specified charging rate.

16. The first network entity of claim 15, wherein the at least one processor is configured to: The at least one priority or the at least one QoS associated with the at least one transmission is received via signaling or separate Sidelink Control Information (SCI) from the at least one second network entity.

17. The first network entity of claim 1, wherein the second threshold is based on one or more of: at least one priority or at least one quality of service (QoS) associated with the data communication.

18. The first network entity according to claim 1, wherein: To send the first information, the at least one processor is configured to send the first information based on a request via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling.

19. The first network entity of claim 1, wherein the at least one processor is configured to: receiving at least one report indicating charging rate change information, discharging rate change information, movement information, or radio operation change information via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling; and The first information is transmitted based on the charging rate change information, the discharging rate change information, the movement information, or the radio operation change information.

20. The first network entity of claim 1, wherein the first metric is one of a reference signal received power (RSRP), a received signal strength indicator (RSSI), or a signal to noise and interference ratio (SINR).

21. A first network entity for wireless communication, the first network entity comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving, from a second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for the energy transfer, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information associated with the first network entity, and wherein the first threshold is independent of a second threshold for data communication; as well as Applying the first set of preferred resources to the energy harvesting, or refraining from applying the first set of non-preferred resources to the energy harvesting.

22. The first network entity of claim 21, wherein the at least one processor is configured to: Second information indicating a second set of preferred resources for the data communication or a second set of non-preferred resources for the data communication is received from the second network entity, wherein the second set of preferred resources for the data communication is associated with a third metric that is above the second threshold, and wherein the second set of non-preferred resources for the data communication is associated with a fourth metric that is below the second threshold.

23. The first network entity of claim 22, wherein each of the first metric, the second metric, the third metric, or the fourth metric is one of a reference signal received power (RSRP), a received signal strength indicator (RSSI), or a signal to noise and interference ratio (SINR).

24. The first network entity according to claim 21, wherein the energy harvesting information comprises one or more of the following: information about at least one energy harvesting circuit associated with the first network entity, an efficiency associated with the first network entity, a charging band or a charging frequency associated with the first network entity, or A specified charging rate associated with the first network entity.

25. The first network entity of claim 24, wherein the first threshold is based on one or more of: at least one priority or at least one quality of service (QoS) associated with at least one transmission enabled by the energy transfer or the specified charging rate.

26. The first network entity of claim 25, wherein the at least one processor is configured to: The at least one priority or the at least one QoS associated with the at least one transmission is transmitted to the second network entity.

27. The first network entity of claim 24, wherein the at least one processor is configured to: At least one report indicating charging rate change information, discharging rate change information, movement information, or radio operation change information is transmitted via layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling.

28. The first network entity of claim 21, wherein the first metric is one of a reference signal received power (RSRP), a received signal strength indicator (RSSI), or a signal to noise and interference ratio (SINR).

29. A method for wireless communication performed by a first network entity, the method comprising: receiving energy harvesting information associated with at least one second network entity; as well as First information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for the energy transfer is sent to the at least one second network entity, wherein the first set of preferred resources is associated with a first metric that is higher than a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is lower than the first threshold, wherein the first threshold is based on the energy harvesting information, and wherein the first threshold is independent of a second threshold for data communication.

30. A method for wireless communication performed by a first network entity, the method comprising: receiving, from a second network entity, first information indicating a first set of preferred resources for energy transfer or a first set of non-preferred resources for the energy transfer, wherein the first set of preferred resources is associated with a first metric that is above a first threshold for energy harvesting, wherein the first set of non-preferred resources is associated with a second metric that is below the first threshold, wherein the first threshold is based on energy harvesting information associated with the first network entity, and wherein the first threshold is independent of a second threshold for data communication; as well as Applying the first set of preferred resources to the energy harvesting, or refraining from applying the first set of non-preferred resources to the energy harvesting.

Images