Techniques for performing passive internet of things communications

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a grant from a network entity that allocates a set of resources for use by the UE. Additionally, the UE may explicitly or implicitly receive an indication received at the UE regarding granting communication with the UE and an energy harvesting device (e.g., passive Internet of Things (IoT) communication of an energy harvesting device), wherein the communications include at least one of an energy provision transmission to the energy harvesting device, a data transmission to the energy harvesting device, or a data reception from the energy harvesting device. In accordance with the grant, the UE may communicate with the energy harvesting device.

Description

Technical Field

[0001] The following relates to wireless communications, including techniques for performing passive IoT communications. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE).

[0003] Some wireless communication systems may support communication between energy transmitter devices and energy harvesting devices. The energy harvesting device may harvest energy from energy signals transmitted by the energy transmitter device in order to obtain sufficient power to exchange signals with the energy transmitter device. The technology used to support energy harvesting devices may be improved. Summary of the invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses that support technology for performing passive IoT communications. In general, the technology described herein provides a method for allocating resources for passive IoT communications in a wireless communication system. For example, a user equipment (UE) may receive a grant from a network entity to allocate a set of resources for use by the UE. Additionally, the UE may (e.g., implicitly or explicitly) receive an indication that the grant received at the UE is related to communication between the UE and an energy harvesting device. The communication between the UE and the energy harvesting device may include energy provision transmission to the energy harvesting device (e.g., sent by the UE or a network entity), data reception from the energy harvesting device, data transmission to the energy harvesting device, or a combination thereof. The UE may communicate with the energy harvesting device based on the grant.

[0005] A method for wireless communication at a UE is described. The method may include: receiving a grant from a network entity to allocate a set of resources for use by the UE; receiving an indication that the grant received at the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device; and communicating with the energy harvesting device in accordance with the grant.

[0006] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a grant from a network entity to allocate a set of resources for use by the UE; receive an indication that the grant received at the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device; and communicate with the energy harvesting device based on the grant.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving a grant from a network entity to allocate a set of resources for use by the UE; a component for receiving an indication that the grant received at the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device; and a component for communicating with the energy harvesting device in accordance with the grant.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: receiving a grant from a network entity to allocate a set of resources for use by the UE; receiving an indication that the grant received at the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device; and communicating with the energy harvesting device in accordance with the grant.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving an indication may include an operation, feature, component, or instruction for receiving a message explicitly indicating a grant related to communication between the UE and the energy harvesting device, where the message may be a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE) message, or a downlink control information (DCI) message.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the indication may include receiving a message indicating a set of multiple resources dedicated to energy harvesting communications and identifying the grant of operations, features, components, or instructions related to these communications between the UE and the energy harvesting device based on the set of multiple resources including the set of resources.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a message indicating a time range, a frequency range, or a combination thereof to which the grant is applicable, wherein the resource set may be located within the time range, the frequency range, or a combination thereof.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be an RRC message, a MAC-CE message, or a DCI message.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of resources related to communications between a UE and an energy harvesting device includes a duration greater than 14 symbols.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second grant from a network entity allocating a second set of resources for communications between the UE and the energy harvesting device and receiving a message indicating a time range, a frequency range, or a combination thereof to which the grant and the second grant are applicable, wherein the resource set and the second set of resources may be located within the time range, the frequency range, or a combination thereof.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of resources and the second set of resources may be adjacent within the time range.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a frequency resource set of the resource set may be different from a second frequency resource set of the second resource set.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be an RRC message, a MAC-CE message, or a DCI message.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a message indicating whether the UE may want to send an energy offer transmission to the energy harvesting device to power on the energy harvesting device.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the resource set includes one or more uplink configured time slots, one or more downlink configured time slots, or a combination thereof for communication between the UE and the energy harvesting device.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating with an energy harvesting device may include operations, features, components, or instructions for sending an energy offering transmission to the energy harvesting device in accordance with a grant to power on the energy harvesting device, wherein the UE sends the energy offering transmission in a downlink configured time slot, an uplink configured time slot, or both.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a UE sends an energy offer transmission to an energy harvesting device in one or more resources of a resource set adjacent to a data signal sent to or received from the energy harvesting device.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating with an energy harvesting device may include operations, features, components, or instructions for receiving a data signal from the energy harvesting device in accordance with a grant, wherein the UE receives the data signal in a downlink configured time slot, an uplink configured time slot, or both.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating with an energy harvesting device may include operations, features, components, or instructions for sending a data signal to the energy harvesting device in accordance with a grant, wherein the UE sends the data signal in a downlink configured time slot, an uplink configured time slot, or both.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the grant may be an uplink grant or a downlink grant related to communications between the UE and the energy harvesting device.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UE communicates with the energy harvesting device according to time division duplexing, frequency division duplexing, or a combination thereof.

[0026] A method of wireless communication at a network entity is described. The method may include: sending a grant that allocates a set of resources for use by a UE; and sending an indication that the grant sent to the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmissions to the energy harvesting device, data transmissions to the energy harvesting device, or data receptions from the energy harvesting device.

[0027] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a grant allocating a set of resources for use by a UE; and send an indication that the grant sent to the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device.

[0028] Another apparatus for wireless communication at a network entity is described. The apparatus may include means for sending a grant allocating a set of resources for use by a UE, and means for sending an indication that the grant sent to the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmissions to the energy harvesting device, data transmissions to the energy harvesting device, or data receptions from the energy harvesting device.

[0029] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: send a grant allocating a set of resources for use by a UE; and send an indication that the grant sent to the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmissions to the energy harvesting device, data transmissions to the energy harvesting device, or data receptions from the energy harvesting device.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an indication may include operations, features, components, or instructions for sending a message explicitly indicating that the grant is related to communication between the UE and the energy harvesting device, where the message may be an RRC message, a MAC-CE message, or a DCI message.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an indication may include operations, features, components, or instructions for sending a message indicating a set of multiple resources dedicated to energy harvesting communications, wherein the set of resources implicitly indicates that the grant is related to communication between the UE and the energy harvesting device based on the set of resources being included in the set of multiple resources.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a message indicating a time range, a frequency range, or a combination thereof to which the grant is applicable, wherein the resource set may be located within the time range, the frequency range, or a combination thereof.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be an RRC message, a MAC-CE message, or a DCI message.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of resources related to communications between a UE and an energy harvesting device includes a duration greater than 14 symbols.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second grant allocating a second set of resources for communications between the UE and the energy harvesting device and sending a message indicating a time range, a frequency range, or a combination thereof to which the grant and the second grant are applicable, wherein the resource set and the second set of resources may be within the time range, the frequency range, or a combination thereof.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of resources and the second set of resources may be adjacent within the time range.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a frequency resource set of the resource set may be different from a second frequency resource set of the second resource set.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be an RRC message, a MAC-CE message, or a DCI message.

[0039] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a message indicating whether the UE may want to send an energy offer transmission to the energy harvesting device to power on the energy harvesting device.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the resource set includes one or more uplink configured time slots, one or more downlink configured time slots, or a combination thereof for communication between the UE and the energy harvesting device.

[0041] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an energy offering transmission prior to the set of resources to power on the energy harvesting device, wherein the network entity sends the energy offering transmission in a downlink configured time slot, an uplink configured time slot, or both.

[0042] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a data signal from an energy harvesting device, wherein the network entity receives the data signal in a downlink configured time slot, an uplink configured time slot, or both.

[0043] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a data signal to an energy harvesting device, wherein the network entity sends the data signal in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the grant may be an uplink grant or a downlink grant related to communications between the UE and the energy harvesting device.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a network entity configures a UE to communicate with an energy harvesting device according to time division duplexing, frequency division duplexing, or a combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 An example of a wireless communication system supporting techniques for performing passive Internet of Things (IoT) communications in accordance with one or more aspects of the present disclosure is illustrated.

[0047] Figure 2 An example of a wireless communication system supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is illustrated.

[0048] Figure 3 An example of a resource allocation scheme supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is illustrated.

[0049] Figure 4An example of a resource allocation scheme supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is illustrated.

[0050] Figure 5 An example of a process flow supporting techniques for performing passive IoT communications in accordance with one or more aspects of the present disclosure is illustrated.

[0051] Figure 6 and Figure 7 A block diagram of a device supporting techniques for performing passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0052] Figure 8 A block diagram of a communication manager supporting techniques for performing passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0053] Fig. 9 A diagram of a system including a device supporting techniques for performing passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0054] Fig.10 and Fig.11 A block diagram of a device supporting techniques for performing passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0055] Fig.12 A block diagram of a communication manager supporting techniques for performing passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0056] Fig.13 A diagram of a system including a device supporting techniques for performing passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0057] Figures 14 to 17 A flow chart illustrating a method of supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0058] Some wireless communication systems may support communication between a communication device (e.g., a network entity, a user equipment (UE), an RFID reader, or some other energy transmitter device) and an energy harvesting device. The energy harvesting device may be a low-power or passive communication device (e.g., a radio frequency identifier (RFID) tag, a passive Internet of Things (IoT) device, or some other energy harvesting device) that uses energy harvested from a signal to power one or more components of the energy harvesting device and communicate with the energy transmitter device. The energy transmitter device may be a communication device that may send an energy offer transmission (e.g., an energy signal) to the energy harvesting device, which may be harvested by the energy harvesting device to support communication of other signals between the energy transmitter device, the energy harvesting device, and / or some other communication device. For example, the energy harvesting device may perform passive IoT communication by sending an information signal (e.g., a backscattered information signal) to the energy transmitter using energy harvested from the energy offer transmission or receiving the information signal.

[0059] In some cases, the UE may receive one or more resource grants allocated for the communication to be performed by the UE from the network entity. However, the UE may not be able to distinguish between resource grants dedicated to passive IoT communication and resource grants dedicated to other communications (e.g., new radio (NR) communication). Additionally, in some communication systems, the network entity may not be able to allocate grants for resources that last long enough to support passive IoT communication. For example, in some systems, the network entity may allocate grants that are no longer than 14 symbols (or 1 time slot). However, the passive IoT communication procedure may last for a duration greater than 14 symbols (e.g., 0.5 ms to tens of ms). Therefore, the network entity may not be able to provide a continuous grant duration to support a complete passive IoT communication procedure, thereby limiting the deployment of the passive IoT communication procedure. Additionally or alternatively, the UE or network entity may not be able to easily obtain continuous uplink or downlink time slots in a time domain duplex (TDD) system, thereby affecting the scheduling of passive IoT communication because passive IoT communication may be longer than several time slots.

[0060] This article describes technologies, systems, and devices for improving specific implementations of passive IoT communications in wireless communication systems by improving resource allocation methods for passive IoT communications. For example, a UE may receive a resource grant from a network entity that allocates a set of resources for use by the UE. Additionally, the UE may receive an indication from the network entity that the received grant is related to communications between the UE and an energy harvesting device, wherein these communications may include energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, data reception from the energy harvesting device, or a combination thereof. In some examples, the UE may receive the indication via explicit signaling (e.g., radio resource control (RRC), medium access control (MAC) control element (MAC-CE), or downlink control information (DCI) signaling). Alternatively, the UE may receive the indication via implicit signaling. In an example of implicit signaling, a network entity may configure a resource pool dedicated to passive IoT communications. The network entity may then send a grant indicating resources from the resource pool, and the UE may therefore identify that the grant is for passive IoT communications. Therefore, the UE may communicate with the energy harvesting device based on the grant.

[0061] In some aspects, a network entity may configure a passive IoT communication to indicate a grant of resources that support a complete passive IoT communication procedure. For example, in some cases, a UE may receive a resource grant from a network entity indicating a set of resources for communication between the UE and an energy harvesting device, wherein the set of resources persists for a duration greater than 14 symbols. In some other aspects, the UE may receive multiple resource grants from a network entity to support communication between the UE and the energy harvesting device. Additionally or alternatively, the UE may receive a message indicating a time range and / or frequency range to which each individual resource grant applies and / or a time range and / or frequency range to which multiple resource grants apply. For example, the UE may receive a message indicating that a set of resources allocated by multiple grants is within a time range, a frequency range, or both.

[0062] In some specific implementations, to support coherent passive IoT communications, a network entity may configure one or more uplink resources, one or more downlink resources, or a combination thereof that can be used by the UE, the network entity, or both to support passive IoT communications (e.g., energy provision transmission to an energy harvesting device, data transmission to an energy harvesting device, data reception from an energy harvesting device, or a combination thereof).

[0063] Thus, a network entity may allocate one or more uplink grants and / or one or more downlink grants to a UE (or some other network device) to perform passive IoT communication. The network entity may indicate whether the one or more uplink grants and the one or more downlink grants are dedicated to passive IoT communication. In some cases, the uplink grant and / or downlink grant may indicate resources longer than 14 symbols. In some cases, the network entity may indicate continuous wave (e.g., energy providing transmission) information, such as the duration of the continuous wave, to the UE before indicating a data signal to and from the energy harvesting device. Additionally or alternatively, the network entity, the UE, or both may power on the energy harvesting device (e.g., send an energy providing signal) in an uplink time slot, a downlink time slot, or both. Additionally or alternatively, the network entity, the UE, or both may communicate data signals with the energy harvesting device in an uplink time slot, a downlink time slot, or both.

[0064] Various aspects of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages, among others. The techniques employed by the described communication device may enable improved implementation of passive IoT communications in wireless communication systems such as NR systems. Thus, the UE may perform passive IoT communications with high efficiency and reduced cost. For example, by receiving an indication that the received resource grant is dedicated to passive IoT communications, the UE may communicate with the energy harvesting device more efficiently than if the UE did not receive such an indication, because the UE may not yet know the waveform and modulation / demodulation scheme to be adopted according to the received resource grant. Thus, the UE may be able to charge the energy harvesting device more efficiently. Additionally, the network entity may configure the UE to send and / or receive signals in a downlink configured time slot, an uplink configured time slot, or both to perform IoT communications, resulting in reduced latency, increased throughput, and increased resource utilization efficiency.

[0065] Various aspects of the disclosure are first described in the context of wireless communication systems. Various aspects are then described with reference to resource allocation schemes and process flows. Various aspects of the disclosure are further illustrated by and described with reference to device diagrams, system diagrams, and flow diagrams related to techniques for performing passive IoT communications.

[0066] Figure 1An example of a wireless communication system 100 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0067] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0068] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices that take different form factors or have different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be capable of communicating with various types of devices, such as Figure 1 105 or other UEs 115 or network entities 105 shown in FIG.

[0069] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0070] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other on the backhaul links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0071] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0072] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0073] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., RRC, service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and each may be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0074] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0075] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the techniques for performing passive IoT communications as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0076] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0077] like Figure 1 As shown, the UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as repeaters, as well as network entities 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc.

[0078] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive", or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0079] The signal waveform sent on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate for the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE115.

[0080] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0081] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of micro time slots including one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0082] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0083] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of the control channel candidates may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with the coding information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0084] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0085] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0086] Some UEs 115 may be configured to employ a mode of operation that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power conservation techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0087] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

[0088] In some examples, UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communications may be within a coverage area 110 of a network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communications configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, multiple groups of UEs 115 communicating via D2D communications may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0089] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered via the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. The IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0090] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). In general, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range length is about one decimeter to one meter. The UHF waves may be blocked or redirected by buildings and environmental features, and these waves may be referred to as clusters, but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0091] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as a 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) combined with component carriers operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0092] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0093] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such technology may be referred to as spatial multiplexing. Multiple signals may be, for example, sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0094] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0095] The network entity 105 or the UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device such as the network entity 105, or by a receiving device such as the UE 115) beam directions for later transmission or reception by the network entity 105.

[0096] Some signals (such as data signals associated with a particular receiving device) may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device such as receiving network entity 105 or receiving UE 115). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0097] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a set of configured beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0098] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0099] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reorganization to communicate on the logical channel. The MAC layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration and maintenance of the RRC connection of the radio bearer that supports user plane data between UE115 and the network entity 105 or the core network 130. At the PHY layer, the transport channel can be mapped to the physical channel.

[0100] The wireless communication system 100 may support passive IoT communications between an energy harvesting device 185 and a UE 115, a network entity 105, or a combination thereof. Examples of energy harvesting devices 185 include RFID tags, passive IoT devices, and UE 115 (e.g., low power or low complexity UE 115), as well as other energy harvesting devices. That is, the energy harvesting device 185 may be a communication device that performs wireless communications using (e.g., at least in part) energy harvested from received energy providing transmissions. For example, the UE 115 and / or the network entity 105 may send an energy providing transmission to the energy harvesting device 185, which may be harvested by the energy harvesting device 185 to support communication of other signals (e.g., information signals) between the energy harvesting device 185 and the UE 115, or between the energy harvesting device 185 and the network entity 105, or a combination thereof. For example, the energy harvesting device 185 may harvest and use energy from an energy providing transmission (e.g., from the UE 115 and / or the network entity 105) to charge one or more components of the energy harvesting device 185 and to communicate with the UE 115 and / or the network entity 105 (e.g., process received information signals, transmit information signals, backscatter information signals).

[0101] In an ultra-high frequency RFID system, a UE 115 (which may also be referred to as a reader or interrogator) may continuously occupy a channel in an industrial, scientific, and medical (ISM) band for a duration of less than 0.4 s. In some examples, the UE 115 may enable full-duplex functionality, wherein the UE 115 operating in full-duplex functionality may transmit an unmodulated single-frequency modulation wave and simultaneously receive a backscattered signal from the energy harvesting device 185. When performing passive IoT communication, the UE 115 may transmit or receive signals (e.g., energy providing transmissions) in a continuous wave format between packets (e.g., query packets, confirmation packets). In some examples, the energy harvesting device 185 may need to be powered on in order to be able to perform passive IoT communication with the UE 115. Therefore, the UE 115 may power on the energy harvesting device 185 by transmitting an energy providing transmission in a continuous wave (e.g., for a duration of 400 μs to 800 μs) before the UE 115 or the energy harvesting device 185 starts passive IoT communication. The energy harvesting device 185 may communicate with the UE 115 after receiving the energy providing transmission in a continuous wave.

[0102] In some cases, a passive IoT communication system such as an ultra-high frequency RFID system may be incompatible with the wireless communication system 100 because the passive IoT communication system and the wireless communication system 100 may operate on different frequency bands. For example, some systems may operate in a licensed frequency band, and the ultra-high frequency RFID system may operate in a different frequency band (e.g., an ISM band). Additionally, interference may not be defined between the passive IoT communication system and the wireless communication system 100. Therefore, techniques for implementing passive IoT communication and other communications in the wireless communication system 100 may be improved.

[0103] In some examples, UE 115 may receive one or more resource grants from network entity 105, and UE 115 may perform passive IoT communication and / or other wireless communication (e.g., NR communication) based on receiving the one or more resource grants. In some cases, UE 115 may not be able to distinguish between received resource grants dedicated to passive IoT communication and resource grants dedicated to other communications. Passive IoT communication may employ waveforms and modulation / demodulation methods that are different from waveforms and modulation / demodulation methods used for other communications (e.g., NR communications). Because UE 115 may not be able to distinguish between resource grants dedicated to passive IoT communication and resource grants dedicated to other communications, UE 115 may not be able to identify the waveform type and modulation / demodulation method to be employed.

[0104] Additionally or alternatively, the network entity 105 may not be able to support resource allocation for continuous duration grants for passive IoT communication procedures. For example, passive IoT communication procedures may last for a duration of 0.5 ms to tens of ms. However, the network entity 105 may not be able to grant resource allocations for a duration longer than 14 symbols, which may be significantly less than the duration of the passive IoT communication procedures. Therefore, the network entity 105 may not be able to provide continuous grant durations for passive IoT communication procedures.

[0105] Additionally or alternatively, the network entity 105 may allocate resource grants to UE 115 in an FDD system or a TDD system for passive IoT communication between UE 115 and energy harvesting device 185. In a TDD system, UE 115 may communicate different signals on the same frequency band by utilizing separate time slots. For example, in a TDD system, UE 115 may perform downlink communication and uplink communication on the same frequency channel by receiving a downlink signal during a first time slot (e.g., a downlink time slot) and sending an uplink signal during a second time slot (e.g., an uplink time slot) different from the first time slot. In an FDD system, UE 115 may communicate different signals during the same time slot by utilizing separate frequency bands. For example, a UE 115 in an FDD system may perform downlink communication and uplink communication during the same time slot by receiving a downlink signal on a first frequency channel (e.g., a downlink frequency band) and sending an uplink signal on a second frequency channel (e.g., an uplink frequency band) different from the first channel. In some cases, the network entity 105 or the UE 115 may not be able to easily obtain continuous uplink or downlink time slots in a TDD system.

[0106] According to the examples disclosed herein, the wireless communication system 100 may support passive IoT communication between the energy harvesting device 185 and the UE 115 and / or the network entity 105 (e.g., or some other network device). For example, the UE 115 may receive a grant from the network entity 105 to allocate a set of resources for use by the UE 115. Additionally, the UE 115 may receive (e.g., implicitly and / or explicitly) an indication that the grant received at the UE 115 is dedicated to communication between the UE 115 and the energy harvesting device 185. In some cases, the grant may indicate that the resources occupy more than 14 symbols. In some cases, the UE 115 may receive an indication of a time range, a frequency range, or both over which passive IoT communication may occur. In some cases, the UE 115 may be configured to perform passive IoT communication in a time slot configured for uplink, a time slot configured for downlink, or a combination thereof. The communication may include energy provision transmission to the energy harvesting device 185, data transmission to the energy harvesting device 185, data reception from the energy harvesting device 185, or a combination thereof. Based on the grant, the UE 115 may communicate with the energy harvesting device 185 (e.g., using the set of resources included in the grant).

[0107] Figure 2 An example of a wireless communication system 200 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement reference Figure 1Various aspects of the wireless communication system 100 described above may be implemented by various aspects of the wireless communication system. For example, the wireless communication system 200 may include a network entity 105-a, a UE 115-a, and an energy harvesting device 185-a. In some examples, the network entity 105-a may be a reference Figure 1 The example of the network entity 105 and the UE 115-a may be referenced Figure 1 In some examples, the energy harvesting device 185-a may be a reference Figure 1 Examples of energy harvesting devices 185 or UE 115. The wireless communication system 200 may support wireless communications (e.g., communications between a network entity 105-a and a UE 115-a) that may support passive IoT communications between energy transfer devices (e.g., between a network entity 105-a and an energy harvesting device 185-a, between a UE 115 and an energy harvesting device 185-a, or a combination thereof), resulting in increased communication reliability, reduced latency, increased throughput and data rates, reduced power consumption, and improved (e.g., more efficient) power harvesting, among other benefits.

[0108] The wireless communication system 200 may support communication between the network entity 105-a, the UE 115-a, and the energy harvesting device 185-a. The UE 115-a may communicate with the energy harvesting device 185-a via corresponding communication links 210 (these communication links may be reference Figure 1 125) to communicate signals with energy harvesting device 185-a and network entity 105-. For example, network entity 105-a may communicate with UE 115-a over communication link 210-a, UE 115-a and energy harvesting device 185-a may communicate using communication link 210-b and communication link 210-c, and network entity 105 and energy harvesting device 185-a may communicate using communication link 210-d and communication link 210-e.

[0109] To support communication between the UE 115-a and the energy harvesting device 185-a, the UE 115-a and / or the network entity 105-a may be configured to perform wireless power transfer to the energy harvesting device 185-a. In some examples, the UE 115-a may send an energy providing transmission 215-a (e.g., a continuous wave) to the energy harvesting device 185-a via the communication link 210-b, and the energy harvesting device 185-a may perform energy harvesting operations to harvest energy from the energy providing transmission 215-a for use in powering one or more components of the energy harvesting device 185-a. In other examples, the network entity 105-a may send an energy providing transmission 215-b to the energy harvesting device 185-a via the communication link 210-e, and the energy harvesting device 185-a may perform energy harvesting operations to harvest energy from the energy providing transmission 215-b for use in powering one or more components of the energy harvesting device 185-a.

[0110] In some examples, the network entity 105-a may allocate one or more grants to the UE 115-a in a TDD system, an FDD system, or some other communication system (e.g., a combination of a TDD system and an FDD system). For example, the network entity 105-a may send a passive IoT communication configuration 220 indicating one or more grants and / or one or more parameters of the grant to the UE 115-a. In some aspects, the network entity 105-a may explicitly indicate the resources to be used by the UE 115-a for passive IoT communication (e.g., explicitly indicating that the configured grant is for passive IoT communication). For example, the network entity 105-a may send a grant that allocates a set of resources for use by the UE 115-a. Additionally, the network entity 105-a may send an indication that the grant is to be used for passive IoT communication (e.g., a passive IoT communication configuration 220 or some other message). In some cases, the network entity 105-a may explicitly indicate that the grant is related to communication between the UE 115-a and the energy harvesting device 185-a (e.g., sending energy provision transmission 215-a, sending data signal 225-a, receiving data signal 225-b). For example, the network entity 105-a may send a message indicating that the grant is related to communication between the UE 115-a and the energy harvesting device 185-a (e.g., passive IoT communication configuration 220) via an RRC message, a MAC-CE message, a DCI message, or some other control message.

[0111] In other aspects, the network entity 105-a may implicitly indicate that the grant is for passive IoT communication. For example, in some examples, the network entity 105-a may indicate a set of time resources, a set of frequency resources, or both dedicated to passive IoT communication by constructing a resource pool in the passive IoT communication configuration 220 or some other message and indicating the resource pool to the UE 115-a. In such examples, the network entity 105-a may send a grant (e.g., in the passive IoT communication configuration 220, or some other message) for a set of resources allocated for use by the UE 115-a. The UE 115-a may then determine whether the set of resources associated with the grant corresponds to a set of time resources, a set of frequency resources, or both dedicated to passive IoT communication. If the resources included in the resource pool include the set of resources indicated in the grant, the UE 115-a may identify that the grant is related to passive IoT communication between the UE 115-a and the energy harvesting device 185-a.

[0112] In some aspects, and as referenced Figure 3 In more detail, the passive IoT communication configuration 220 may indicate a time range, a frequency range, or both to which a grant or passive IoT grant set applies, wherein the time range, the frequency range, or both may be included in the resource set indicated in the grant. The network entity 105-a may send the passive IoT communication configuration 220 in an RRC message, a MAC-CE message, a DCI message, or some other control message. In some cases, the network entity 105 may indicate one or more grants in the same message or in different messages as an explicit indication that the one or more grants are related to passive IoT communication, an implicit indication that the one or more grants are related to passive IoT communication, an indication of a time range, an indication of a frequency range, etc.

[0113] In some aspects, and as referenced Figure 3In more detail, the network entity 105-a may send a first grant and a second grant for communication between the UE 115-a and the energy harvesting device 185-a. The first grant may allocate a first set of resources for use by the UE 115-a, and the second grant may allocate a second set of resources for communication between the UE 115-a and the energy harvesting device 185-a. In such aspects, the network entity 105-a may send a message indicating a first time range and / or frequency range to which the first grant applies and a second time range and / or frequency range to which the second grant applies, and / or indicating a time range and / or frequency range to which the first grant and the second grant apply, wherein the first resource set and the second resource set are located in the time range and / or the frequency range. The network entity 105-a may send the message via explicit signaling or implicit signaling. In some aspects, the first resource set and the second resource set may be adjacent in the time range, meaning that the resources are located in consecutive time slots. Additionally or alternatively, the frequency resource set in the first resource set may be different from the second frequency resource set in the second resource set, meaning that the frequency resources allocated by the first grant and the second grant may be different.

[0114] In some specific implementations, and as referenced Figure 4 In more detail, UE 115-a may receive a grant of allocated resources for UE 115-a to use for passive IoT communication, where the grant may be an uplink grant, a downlink grant, or a combination thereof. That is, network entity 105-a may indicate a grant to UE 115-a that spans one or more uplink configured time slots or symbols for passive IoT transmission, and one or more downlink resources in a downlink configured time slot or symbol for passive IoT reception, passive IoT transmission, or both. For example, UE 115-a may receive a grant allocating resources to UE 115-a, and receive an indication that the grant is dedicated to passive IoT communication. Based on the grant, UE 115-a may send data signal 225-a in a downlink configured time slot, an uplink configured time slot, or both based on the grant. Thus, UE 115-a may be configured with continuous downlink and / or uplink configuration resources allocated for passive IoT communications such as passive IoT transmission (e.g., transmitting energy to provide transmission 215-a, transmitting data signal 225-a) or passive IoT reception (e.g., receiving data signal 225-b).

[0115] In some examples, UE 115-a may perform passive IoT communication in a single-station scenario, which may also be referred to as a co-located dual-station scenario. In such examples, UE 115-a may send an energy signal (e.g., energy providing transmission 215) and send and / or receive backscattered signals (e.g., data signal 225, data signal 225-b) with energy harvesting device 185. That is, UE 115-a may be used as an RF source and perform backscatter reception in a single-station scenario. In other examples, UE 115-a or network entity 105-a may perform passive IoT communication in a dual-station scenario. In some such examples, UE 115-a may send an energy providing transmission 215-a to energy harvesting device 185-a, and network entity 105-a may send and / or receive backscattered signals (e.g., data signal 225-a, data signal 225-b) with energy harvesting device 185. In other such examples, the network entity 105 - a may send an energy providing transmission 215 - b to the energy harvesting device 185 - a , and the UE 115 - a may send and / or receive backscattered signals (e.g., data signal 225 - c , data signal 225 - d ) with the energy harvesting device 185 .

[0116] By implementing a specific implementation of resource allocation methods for passive IoT communication in the wireless communication system 200, the communication characteristics of signals communicated between the network entity 105-a, the UE 115-a, and the energy harvesting device 185-a can be improved. For example, by (e.g., implicitly or explicitly) receiving an indication that resources received in a grant are dedicated to passive IoT communication, the UE 115-a can determine to employ a waveform and modulation / demodulation scheme to efficiently perform passive IoT communication, thereby achieving power savings and reduced latency, among other benefits. Additionally, the reliability, throughput, and data rate of the signal can be improved, among other benefits.

[0117] Figure 3 An example of a resource allocation scheme 300 supporting techniques for performing passive IoT communication according to one or more aspects of the present disclosure is illustrated. The resource allocation scheme 300 may be implemented by referring to Figure 1 and Figure 2 Various aspects of the wireless communication systems 100 and 200 described above may be implemented by various aspects of these wireless communication systems. For example, the resource allocation scheme 300 may be implemented by referring to Figure 2 The UE 115-a or network entity 105-a (which may be reference Figure 1 The example of the corresponding device described above is implemented.

[0118] As reference Figure 2As discussed, UE 115-a may perform passive IoT communication with energy harvesting device 185-a in an FDD system, a TDD system, or some other system by allocating one or more grants in a continuous time slot set. In some examples, UE 115 may communicate with energy harvesting device 185 over a frequency range, such as a frequency range on uplink band 320. UE 115 may receive one or more grants for passive IoT communication. For example, UE 115 may receive passive IoT grant 305-a, passive IoT grant 305-b, passive IoT grant 305-c, and passive IoT grant 305-d. Each passive IoT grant in passive IoT grant 305 may be dedicated to passive IoT communication with one or more energy harvesting devices. In some examples, the frequencies of the grants may be the same. Alternatively, the frequencies of the grants may be different. For example, the UE 115 may receive the passive IoT grants 305, where each of the passive IoT grants 305 is an allocated set of resources for the UE 115 to use to perform passive IoT communications.

[0119] In some aspects, the UE 115 may (e.g., explicitly or implicitly) receive an indication that one or more passive IoT grants 305 are dedicated to passive IoT communication by the UE 115. Thus, the UE 115 may use the one or more passive IoT grants 305 to perform passive IoT communication procedures (e.g., send energy to the energy harvesting device 185, send and / or receive data signals from the energy harvesting device 185). In some cases, the passive IoT grants 305 may be adjacent to each other to support continuous passive IoT communication.

[0120] In some cases, the passive IoT communication procedure may last for a duration greater than 14 symbols (e.g., greater than a time slot). For example, the passive IoT communication procedure may last for a duration of 0.5 ms to tens of ms, which may be a duration greater than 14 symbols. In some aspects, the UE 115 may receive an indication including an explicit or implicit message indicating a time range, a frequency range, or both to which one or more of the passive IoT grants 305 may be applicable in order to support the passive IoT communication procedure. In such aspects, the resources included in the one or more passive IoT grants 305 may be within the indicated time range, frequency range, or both. For example, the UE 115 may receive a passive IoT grant 305 for use by the UE 115. The UE 115 may also receive an indication of a time-frequency range for each allocated grant and / or a time range for all allocated grants combined that are dedicated to passive IoT communication. The set of resources included in each passive IoT grant 305 may be of duration greater than 14 symbols, and / or the set of resources associated with all configured grants (eg, passive IoT grants 305) may be of duration greater than 14 symbols.

[0121] In some cases, the UE 115 may receive the time range, frequency range, or both in an RRC message, a MAC-CE message, and / or a DCI message. In some cases, the UE 115 may receive the time range, frequency range, or both in the same message or in a different message than the message indicating one or more grants. Thus, the UE 115 may communicate with the energy harvesting device 185 using the passive IoT grant 305 to perform a passive IoT communication procedure.

[0122] Figure 4 An example of a resource allocation scheme 400 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is illustrated. The resource allocation scheme 400 may be implemented with reference to Figure 1 The wireless communication system 100 and / or reference Figure 2 The various aspects of the wireless communication system 200 described above may be implemented by various aspects of these wireless communication systems. For example, the resource allocation scheme 400 may be implemented by referring to Figure 2 The UE 115-a, network entity 105-a or energy harvesting device 185-a (which may be reference Figure 1 In some cases, the techniques described with reference to resource allocation scheme 400 may be combined with the techniques described with reference to resource allocation scheme 300.

[0123] In some examples, UE 115 may perform passive IoT communication in an FDD scheme. Alternatively, UE 115 may perform passive IoT communication in a TDD scheme. In a TDD system including a resource allocation scheme 400, the network entity 105 may configure one or more downlink time slots 405 (e.g., downlink symbols) and one or more uplink time slots 410 (e.g., uplink symbols) for communications performed by UE 115. For example, the network entity 105 may configure downlink time slots 405-a, downlink time slots 405-b, downlink time slots 405-c, downlink time slots 405-c, downlink time slots 405-d, downlink time slots 405-e, downlink time slots 405-f, downlink time slots 405-g, and downlink time slots 405-h. Additionally, the network entity 105 may configure uplink time slots 410-a and uplink time slots 405-b. In some examples, the network entity 105 may configure the downlink time slot 405 and the uplink time slot 410 so that the downlink time slot 405 and the uplink time slot 410 are continuous in the time domain. In other examples, the downlink time slot 405 and the uplink time slot 410 may be non-contiguous in the time domain. In some aspects, the downlink time slot 405 and the uplink time slot 410 may occupy the same frequency domain, such as frequency band 415. In other aspects, the downlink time slot 405 and the uplink time slot 410 may occupy different frequencies.

[0124] In some examples, UE 115 may receive a grant allocating a set of resources to be used by UE 115, and UE 115 may also receive an indication that the grant is related to passive IoT communication. The set of resources allocated by the grant may include one or more downlink configured time slots (e.g., one or more downlink time slots in downlink time slots 405), one or more uplink configured time slots (e.g., one or more uplink time slots in uplink time slots 410), or a combination of one or more downlink configured time slots and one or more uplink configured time slots for communication between UE 115 and energy harvesting device 185.

[0125] In some aspects, the network entity 105 or some other network device may transmit (e.g., send) an energy offering transmission to the energy harvesting device 185. In other aspects, the UE 115 may transmit an energy offering transmission to the energy harvesting device 185. The network entity 105 or the UE 115 may power up (e.g., turn on) an energy harvesting device 185 that is currently off or has low battery life by transmitting an unmodulated wave (such as an energy offering transmission) for a duration, so that the energy harvesting device 185 turns on to communicate data signals with the UE 115 and / or the network entity 105. In some examples, the UE 115 may receive a grant allocating a set of resources, and the network entity 105 or the UE 115 may power up the energy harvesting device 185 according to the grant. For example, the UE 115 may receive a grant allocating one or more downlink time slots 405 and / or one or more uplink time slots 410 for passive IoT communication, and the UE 115 may also receive an indication that the grant is related to passive IoT communication. The UE 115 may receive a message indicating whether the UE 115 is to send an energy signal (e.g., an energy offering transmission) to the energy harvesting device 185 to power on the energy harvesting device 185. If the UE 115 receives a message indicating that the UE 115 is to send an energy offering transmission to the energy harvesting device 185 to power on the energy harvesting device 185, the UE 115 may use one or more downlink time slots 405 allocated in the one or more passive IoT grants to send the energy offering transmission. Additionally or alternatively, the UE 115 may use one or more uplink time slots 410 to send the energy offering transmission. If the UE 115 does not receive a message indicating that the UE 115 is to send an energy offering transmission to the energy harvesting device 185, the network entity 105 or another energy transmission device in the wireless communication system may send an energy offering transmission to the energy harvesting device 185 during the downlink time slot 405, the uplink time slot 410, or both to power on the energy harvesting device 185. In some cases, the network entity 105 may send an indication to the UE 115 that the network entity 105 or another energy transmitting device in the wireless communication system may send an energy supply transmission to the energy harvesting device 185 during the downlink time slot 405, the uplink time slot 410, or both, but before data communication occurs between the energy harvesting device 185, the UE 115, and / or the network entity 105 to power on the energy harvesting device 185.

[0126] In some aspects, the UE 115 may transmit data signals to the energy harvesting device 185 in one or more downlink configured time slots, one or more uplink configured time slots, or a combination thereof in accordance with one or more passive IoT grants. Additionally or alternatively, the UE 115 may receive data signals in one or more downlink configured time slots, one or more uplink configured time slots, or a combination thereof in accordance with one or more passive IoT grants. In some examples, the UE 115 may perform passive IoT communication by transmitting an energy providing transmission to the energy harvesting device 185 in one or more resources in a resource set that are adjacent to a data signal transmitted to or received from the energy harvesting device 185. For example, the UE 115 may indicate one or more grants in an uplink time slot 410 and a downlink time slot 405, wherein the uplink time slot 410 and the downlink time slot 405 are adjacent to each other. In accordance with the grant, the UE 115 may send an energy offering transmission to the energy harvesting device 185 in a subset of time slots including the uplink time slot 410, the downlink time slot 405, or both, wherein the subset of time slots used to send the energy offering transmission is adjacent to a data signal that the energy harvesting device 185 may transmit or receive, as described in reference to Figure 2 For example, UE 115 may send energy to provide transmission in one or more downlink time slots in downlink time slot 405 (e.g., downlink time slot 405-d and downlink time slot 405-e), and UE 115 may send or receive one or more data signals (e.g., backscatter signals) in one or more adjacent time slots (e.g., downlink time slot 405-b and downlink time slot 405-c or uplink time slot 410-a and uplink time slot 410-b).

[0127] Figure 5 An example of a process flow 500 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is illustrated. The process flow 500 may be performed by referring to Figure 1 The wireless communication system 100 and / or the reference Figure 2 The wireless communication system 200 described above can be implemented in various aspects. For example, the UE 115-b can be as shown in FIG. Figure 1 The UE 115 and the reference Figure 2 The example of UE 115-a and network entity 105-b may be as shown in reference Figure 1 The network entity 105 and the reference Figure 2 Similarly, the energy harvesting device 185-b may be an example of a network entity 105-a as described above. Figure 1 The energy harvesting device 185 and the reference Figure 2Examples of energy harvesting devices 185-a described. The following alternative examples may be implemented in which some of the steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or additional steps may be added.

[0128] At 505, the network entity 105-b may send a grant of a set of resources (e.g., time resources, frequency resources) allocated for use by UE 115-b, and UE 115-b may receive the grant. In some aspects, the grant may be an uplink grant. Alternatively, the grant may be a downlink grant. The grant may include resources dedicated to communications to be performed by UE 115-b, such as passive IoT communications or other communications (e.g., NR communications). In some examples, a set of resources related to passive IoT communications between UE 115-b and an energy harvesting device may last for a duration greater than 14 symbols. In some examples, the network entity 105-b may send a second grant allocating a second set of resources for communications between UE 115-b and energy harvesting device 185-b, and UE 115-b may receive the second grant. In some examples, the set of frequency resources in the resource set may be different from the second set of frequency resources in the second resource set. Additionally or alternatively, the resource set and the second resource set may be adjacent in time. In some aspects, the resource set, the second resource set, or both may include one or more uplink configured time slots, one or more downlink configured time slots, or a combination of one or more uplink configured time slots and one or more downlink configured time slots for communication between UE 115-b and energy harvesting device 185-a.

[0129] At 510, the network entity 105-b may send a grant association indication indicating that the grant received at 505 is related to the communication between the UE 115-b and the energy harvesting device 185-b, and the UE 115-b may receive the grant association indication. The communication between the UE 115-b and the energy harvesting device 185-b may include at least one of energy provision transmission to the energy harvesting device 185-b, data transmission to the energy harvesting device 185-b, or data reception from the energy harvesting device 185-b. In some examples, the network entity 105-b may send the grant association indication explicitly or implicitly. For example, the network entity 105-b may send a message explicitly indicating that the grant received at 505 is related to the communication between the UE 115-b and the energy harvesting device 185-b, and the UE 115-b may receive the message, wherein the message may be an RRC message, a MAC-CE message, or a DCI message. In other examples, the network entity 105-b may send a message indicating a plurality of resources dedicated to energy harvesting communications, and the UE 115-b may receive the message. That is, the network entity 105-b may implicitly send a grant association indication by constructing a resource pool and indicating the resource pool to the UE 115-b. In some aspects, the UE 115-b may receive a message indicating a time range, a frequency range, or both to which the grant applies. In such aspects, the set of resources allocated by the grant may be within the time range, the frequency range, or both. In other aspects, the UE 115-b may receive a message indicating a time range, a frequency range, or both to which the grant and the second grant apply. In such other aspects, the set of resources allocated by the grant and the second set of resources allocated by the second grant may be within the time range, the frequency range, or a combination thereof. In some examples, the message may be an RRC message, a MAC-CE message, or a DCI message.

[0130] At 515, UE 115-b may identify communications associated with the resource grant received at 505. For example, if UE 115-b receives a message indicating a plurality of resources dedicated to energy harvesting communications at 510, UE 115-b may identify that the grant is related to communications between UE 115-b and energy harvesting device 185-b based on the plurality of resources comprising a set of resources. Thus, UE 115-b may know to adopt a passive IoT communication strategy for transmission or reception.

[0131] At 520, UE 115-b may send an energy offering transmission, and energy harvesting device 185-b may receive the energy offering transmission. In some examples, UE 115-b may receive a message indicating whether UE 115-b is to send an energy offering transmission to energy harvesting device 185-b to power on the energy harvesting device, and UE 115-b may send the energy offering transmission based on receiving the message. UE 115-b may send an energy offering transmission to energy harvesting device 185-b to power on energy harvesting device 185-b. In some examples, UE 115-b may send an energy offering transmission to energy harvesting device 185-b based on the grant received at 505, wherein UE 115-b may send the energy offering transmission in a time slot configured for the downlink, a time slot configured for the uplink, or both. Additionally or alternatively, the UE 115 - b may send an energy offering transmission to the energy harvesting device 185 - b in one or more resources in the resource set adjacent to a data signal sent to or received from the energy harvesting device 185 - b.

[0132] At 525, the network entity 105-b may send an energy offering transmission, and the energy harvesting device 185-b may receive the energy offering transmission. The network entity 105-b may send the energy offering transmission using the same or similar technology as the technology that the UE 115-b may use to send the energy offering transmission. In some cases, the network entity 105-b and the UE 115-b may both send the energy offering transmission to the energy harvesting device 185-b at the same time or at different times. Alternatively, one of the network entity 105-b or the UE 115-b may send the energy offering transmission.

[0133] At 530, UE 115-b may communicate data signaling with energy harvesting device 185-b based on the grant received at 505. In some examples, UE 115-b may communicate with energy harvesting device 185-b by receiving a data signal from energy harvesting device 185-b based on the grant. UE 115-b may receive the data signal in a time slot configured for the downlink, a time slot configured for the uplink, or both. In other examples, UE 115-b may communicate with energy harvesting device 185-b by sending a data signal to energy harvesting device 185-b in a time slot configured for the downlink, a time slot configured for the uplink, or both.

[0134] At 535, the network entity 105-b may communicate data signaling with the energy harvesting device 185-b. In some examples, the network entity 105-b may communicate with the energy harvesting device 185-b by receiving a data signal from the energy harvesting device 185-b. In other examples, the network entity 105-b may communicate with the energy harvesting device 185-b by sending a data signal to the energy harvesting device 185-b. In some cases, both the network entity 105-b and the UE 115-b may perform data communications with the energy harvesting device 185-b at the same time or at different times. Alternatively, one of the network entity 105-b or the UE 115-b may perform data communications using energy provided transmission.

[0135] In some cases, the energy harvesting device 185-b may send a data signal to the UE 115-b, and the UE 115-b may relay the data signal to the network entity 105-b. Similarly, the energy harvesting device 185-b may send a data signal to the network entity 105-b, and the network entity 105-b may relay the data signal to the UE 115-b. In some cases, the UE 115-a may receive a data signal from the network entity 105-b and may relay the data signal to the energy harvesting device 185-b. Similarly, the UE 115-a may send a data signal to the network entity 105-b, and the network entity 105-b may relay the data signal to the energy harvesting device 185-b.

[0136] Figure 6 A block diagram 600 of a device 605 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0137] Receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for performing passive IoT communications). The information may be communicated to other components of device 605. Receiver 610 may utilize a single antenna or a set of multiple antennas.

[0138] Transmitter 615 may provide means for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to the technology used to perform passive IoT communications). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0139] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the techniques for performing passive IoT communications as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0140] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0141] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0142] In some examples, communication manager 620 may be configured to use receiver 610, transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in conjunction with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0143] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a UE. For example, the communication manager 620 may be configured to or otherwise support components for receiving a grant of a set of resources allocated for use by the UE from a network entity. The communication manager 620 may be configured to or otherwise support components for receiving an indication that a grant received at the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device. The communication manager 620 may be configured to or otherwise support components for communicating with the energy harvesting device based on the grant.

[0144] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof or otherwise coupled thereto) may support techniques for reducing power consumption and more efficiently utilizing communication resources, thereby supporting increased communication reliability, increased throughput and data rates, and reduced latency, among other benefits, for example by receiving indications that allow the device 605 to know the waveform and modulation / demodulation scheme to be employed to communicate with the energy harvesting device based on a received resource grant.

[0145] Figure 7 A block diagram 700 of a device 705 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0146] Receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for performing passive IoT communications). The information may be communicated to other components of device 705. Receiver 710 may utilize a single antenna or a set of multiple antennas.

[0147] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to the technology used to perform passive IoT communications). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.

[0148] Device 705 or its various components may be examples of components for performing various aspects of the techniques for performing passive IoT communications as described herein. For example, communication manager 720 may include a grant receiving component 725, an energy harvesting indication component 730, an energy harvesting communication component 735, or any combination thereof. Communication manager 720 may be an example of various aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use receiver 710, transmitter 715, or both, or otherwise cooperate with them to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated with receiver 710, transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0149] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. The grant receiving component 725 may be configured to or otherwise support components for receiving a grant of a set of resources allocated for use by the UE from a network entity. The energy harvesting indication component 730 may be configured to or otherwise support components for receiving indications of grants received at the UE related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmissions to the energy harvesting device, data transmissions to the energy harvesting device, or data receptions from the energy harvesting device. The energy harvesting communication component 735 may be configured to or otherwise support components for communicating with the energy harvesting device in accordance with the grant.

[0150] Figure 8A block diagram 800 of a communication manager 820 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of the techniques for performing passive IoT communications as described herein. For example, the communication manager 820 may include a grant receiving component 825, an energy harvesting indication component 830, an energy harvesting communication component 835, an energy harvesting identification component 840, a resource message component 845, a resource message component 850, an energy transmitter message component 855, an energy harvesting communication component 860, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0151] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. A grant receiving component 825 may be configured to or otherwise support components for receiving a grant of a set of resources allocated for use by the UE from a network entity. An energy harvesting indication component 830 may be configured to or otherwise support components for receiving indications of a grant received at the UE related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmissions to the energy harvesting device, data transmissions to the energy harvesting device, or data receptions from the energy harvesting device. An energy harvesting communication component 835 may be configured to or otherwise support components for communicating with the energy harvesting device in accordance with the grant.

[0152] In some examples, to support receiving the indication, the energy harvesting indication component 830 may be configured to or otherwise support a component for receiving a message explicitly indicating that the grant is related to communication between the UE and the energy harvesting device, wherein the message is an RRC message, a MAC-CE message, or a DCI message.

[0153] In some examples, to support receiving the indication, the energy harvesting indication component 830 may be configured or otherwise support a component for receiving a message indicating a set of multiple resources dedicated to energy harvesting communications. In some examples, to support receiving the indication, the energy harvesting identification component 840 may be configured or otherwise support a component for identifying the grant related to communication between the UE and the energy harvesting device based on the set of multiple resources including a resource set.

[0154] In some examples, resource message component 845 may be configured or otherwise support components for receiving a message indicating a time range, frequency range, or a combination thereof to which the grant applies, where the resource set is within the time range, frequency range, or a combination thereof.

[0155] In some examples, the message is an RRC message, a MAC-CE message, or a DCI message.

[0156] In some examples, a set of resources related to communications between a UE and an energy harvesting device includes a duration greater than 14 symbols.

[0157] In some examples, grant receiving component 825 can be configured or otherwise support components for receiving a second grant from a network entity allocating a second set of resources for communications between the UE and the energy harvesting device. In some examples, resource message component 850 can be configured or otherwise support components for receiving a message indicating a time range, a frequency range, or a combination thereof to which the grant and the second grant apply, wherein the set of resources and the second set of resources are within the time range, the frequency range, or a combination thereof.

[0158] In some examples, the set of resources and the second set of resources are adjacent within the time range.

[0159] In some examples, the frequency resource set of the resource set is different from the second frequency resource set in the second resource set.

[0160] In some examples, the message is an RRC message, a MAC-CE message, or a DCI message.

[0161] In some examples, energy transmitter message component 855 may be configured or otherwise support components for receiving a message indicating whether the UE is to send an energy offer transmission to the energy harvesting device to power on the energy harvesting device.

[0162] In some examples, the resource set includes one or more uplink configured time slots, one or more downlink configured time slots, or a combination thereof for communication between the UE and the energy harvesting device.

[0163] In some examples, to support communication with an energy harvesting device, the energy harvesting communication component 860 may be configured as or otherwise support components for sending an energy offering transmission to the energy harvesting device in accordance with the grant to power on the energy harvesting device, wherein the UE sends the energy offering transmission in a downlink configured time slot or an uplink configured time slot, or both.

[0164] In some examples, the UE sends an energy offer to the energy harvesting device in one or more resources in the resource set that are adjacent to a data signal sent to or received from the energy harvesting device.

[0165] In some examples, to support communication with the energy harvesting device, the energy harvesting communication component 860 may be configured as or otherwise support components for receiving a data signal from the energy harvesting device in accordance with the grant, wherein the UE receives the data signal in a downlink configured time slot, an uplink configured time slot, or both.

[0166] In some examples, to support communication with an energy harvesting device, the energy harvesting communication component 860 may be configured as or otherwise support components for sending a data signal to the energy harvesting device in accordance with the grant, wherein the UE sends the data signal in a downlink configured time slot, an uplink configured time slot, or both.

[0167] In some examples, the grant is an uplink grant or a downlink grant related to communications between the UE and the energy harvesting device.

[0168] In some examples, the UE communicates with the energy harvesting device based on time division duplexing, frequency division duplexing, or a combination thereof.

[0169] Fig. 9 A diagram of a system 900 including a device 905 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein, or include components thereof. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945).

[0170] I / O controller 910 can manage input and output signals of device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize a computer such as a , or other known operating systems. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor such as processor 940. In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0171] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. As described herein, the transceiver 915 may communicate bidirectionally via one or more antennas 925, wired or wireless links. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for: modulating packets to provide the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

[0172] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 935 may not be directly executable by the processor 940, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 930 may include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0173] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to enable the device 905 to perform various functions (e.g., functions or tasks that support technology for performing passive IoT communications). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0174] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a UE. For example, the communication manager 920 may be configured to or otherwise support components for receiving a grant from a network entity to allocate a set of resources for use by the UE. The communication manager 920 may be configured to or otherwise support components for receiving an indication that a grant received at the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device. The communication manager 920 may be configured to or otherwise support components for communicating with the energy harvesting device based on the grant.

[0175] By including or configuring the communication manager 920 according to the examples described herein, the device 905 can support techniques for improving resource allocation for passive IoT communications in wireless communication systems, thereby facilitating improved communication reliability, reduced latency, increased throughput, reduced power consumption, improved (e.g., more efficient) power harvesting, more efficient use of communication resources, improved coordination between devices, and extended battery life, among other benefits.

[0176] In some examples, the communication manager 920 may be configured to use the transceiver 915, one or more antennas 925, or any combination thereof, or otherwise cooperate with them to perform various operations (e.g., receive, monitor, transmit). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that can be executed by the processor 940 to cause the device 905 to perform various aspects of the techniques for performing passive IoT communications as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0177] Fig.10 A block diagram 1000 of a device 1005 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0178] Receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information such as user data associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0179] The transmitter 1015 may provide means for outputting (e.g., sending, providing, transmitting, conveying) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0180] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the techniques for performing passive IoT communications as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0181] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in this disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0182] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0183] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0184] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. For example, the communication manager 1020 may be configured to or otherwise support components for sending a grant of a resource set allocated for use by a UE. The communication manager 1020 may be configured to or otherwise support components for sending an indication that the grant sent to the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device.

[0185] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof or otherwise coupled thereto) may support techniques for reducing power consumption and more efficiently utilizing communication resources, thereby supporting increased communication reliability, increased throughput and data rates, and reduced latency, among other benefits, for example by receiving indications that allow the device 1005 to know, based on a received resource grant, a waveform and modulation / demodulation scheme to be employed to communicate with an energy harvesting device.

[0186] Fig.11 A block diagram 1100 of a device 1105 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0187] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0188] The transmitter 1115 may provide means for outputting (e.g., sending, providing, transmitting, conveying) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0189] Device 1105 or its various components may be examples of components for performing various aspects of the techniques for performing passive IoT communications as described herein. For example, communication manager 1120 may include a grant sending component 1125, an energy harvesting indication component 1130, or any combination thereof. Communication manager 1120 may be an example of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using receiver 1110, transmitter 1115, or both or otherwise cooperate with them. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in combination with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0190] According to examples as disclosed herein, the communication manager 1120 can support wireless communications at a network entity. The grant sending component 1125 can be configured to or otherwise support components for sending a grant of a resource set allocated for use by the UE. The energy harvesting indication component 1130 can be configured to or otherwise support components for sending an indication that the grant sent to the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device.

[0191] Fig.12 A block diagram 1200 of a communication manager 1220 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of components for performing various aspects of the techniques for performing passive IoT communications as described herein. For example, the communication manager 1220 may include a grant sending component 1225, an energy harvesting indication component 1230, a resource message component 1235, an energy transmitter message component 1240, an energy harvesting communication component 1245, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), and these communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0192] According to examples as disclosed herein, the communication manager 1220 can support wireless communications at a network entity. The grant sending component 1225 can be configured to or otherwise support components for sending a grant of a set of resources allocated for use by the UE. The energy harvesting indication component 1230 can be configured to or otherwise support components for sending an indication that the grant sent to the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device.

[0193] In some examples, to support sending the indication, the energy harvesting indication component 1230 may be configured to or otherwise support components for sending a message explicitly indicating that the grant is related to communication between the UE and the energy harvesting device, wherein the message is an RRC message, a MAC-CE message, or a DCI message.

[0194] In some examples, to support sending the indication, the energy harvesting indication component 1230 may be configured as or otherwise support components for sending a message indicating a set of multiple resources dedicated to energy harvesting communications, wherein the set of resources implicitly indicates that the grant is related to communication between the UE and the energy harvesting device based on the resource set being included in the set of multiple resources.

[0195] In some examples, resource message component 1235 may be configured or otherwise support components for sending a message indicating a time range, frequency range, or a combination thereof to which the grant applies, where the resource set is within the time range, frequency range, or a combination thereof.

[0196] In some examples, the message is an RRC message, a MAC-CE message, or a DCI message.

[0197] In some examples, a set of resources related to communications between a UE and an energy harvesting device includes a duration greater than 14 symbols.

[0198] In some examples, grant sending component 1225 can be configured or otherwise support components for sending a second grant that allocates a second set of resources for communication between the UE and the energy harvesting device. In some examples, resource message component 1235 can be configured or otherwise support components for sending a message indicating a time range, a frequency range, or a combination thereof to which the grant and the second grant apply, wherein the resource set and the second set of resources are within the time range, the frequency range, or a combination thereof.

[0199] In some examples, the set of resources and the second set of resources are adjacent within the time range.

[0200] In some examples, the frequency resource set in the resource set is different from the second frequency resource set in the second resource set.

[0201] In some examples, the message is an RRC message, a MAC-CE message, or a DCI message.

[0202] In some examples, energy transmitter message component 1240 may be configured or otherwise support components for sending a message indicating whether the UE is to send an energy offer transmission to the energy harvesting device to power on the energy harvesting device.

[0203] In some examples, the resource set includes one or more uplink configured time slots, one or more downlink configured time slots, or a combination thereof for communication between the UE and the energy harvesting device.

[0204] In some examples, the energy harvesting communications component 1245 may be configured or otherwise support components for sending an energy offering transmission prior to a set of resources to power on the energy harvesting device, wherein the network entity sends the energy offering transmission in a downlink configured time slot, an uplink configured time slot, or both.

[0205] In some examples, energy harvesting communications component 1245 can be configured or otherwise support components for receiving data signals from an energy harvesting device, where the network entity receives the data signals in a downlink configured time slot, an uplink configured time slot, or both.

[0206] In some examples, energy harvesting communications component 1245 can be configured or otherwise support components for sending data signals to the energy harvesting device, where the network entity sends the data signals in a downlink configured time slot, an uplink configured time slot, or both.

[0207] In some examples, the grant is an uplink grant or a downlink grant related to communications between the UE and the energy harvesting device.

[0208] In some examples, the network entity configures the UE to communicate with the energy harvesting device according to time division duplexing, frequency division duplexing, or a combination thereof.

[0209] Fig.13 A diagram of a system 1300 including a device 1305 supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein, or include components thereof. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communications may include communications through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support output and acquisition of communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0210] As described herein, the transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem for modulating a signal, providing the modulated signal for transmission (e.g., through one or more antennas 1315, through a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and demodulating the signal. Where applicable, transceiver 1310 or transceiver 1310 and one or more antennas 1315 or wired interfaces may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0211] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may include BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0212] Processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1335. Processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) to enable device 1305 to perform various functions (e.g., functions or tasks that support technology for performing passive IoT communications). For example, device 1305 or a component of device 1305 may include processor 1335 and memory 1325 coupled to processor 1335, the processor 1335 and memory 1325 being configured to perform the various functions described herein. Processor 1335 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality (e.g., by executing code 1330) to perform the functions of device 1305.

[0213] In some examples, bus 1340 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1305, or communications performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of these different components or divided between different components).

[0214] In some examples, communication manager 1320 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 may manage delivery of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1320 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in collaboration with other network entities 105. In some examples, communication manager 1320 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0215] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to or otherwise support components for sending a grant of a resource set allocated for use by a UE. The communication manager 1320 may be configured to or otherwise support components for sending an indication that the grant sent to the UE is related to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device.

[0216] By including or configuring the communication manager 1320 according to the examples described herein, the device 1305 can support techniques for reducing power consumption and more efficiently utilizing communication resources, such as by receiving indications that allow the device 1305 to know the waveform and modulation / demodulation scheme to be employed to communicate with the energy harvesting device based on a received resource grant, thereby supporting increased communication reliability, increased throughput and data rates, and reduced latency, among other benefits.

[0217] In some examples, the communication manager 1320 may be configured to use or otherwise cooperate with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, obtain, monitor, output, transmit). Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1335, the memory 1325, the code 1330, the transceiver 1310, or any combination thereof. For example, the code 1330 may include instructions executable by the processor 1335 to cause the device 1305 to perform various aspects of the techniques for performing passive IoT communications as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0218] Fig.14 1400 is a flowchart of a method 1400 for supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described herein. Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0219] At 1405, the method may include receiving a grant from a network entity to allocate a resource set for use by the UE. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The grant receiving component 825 is executed.

[0220] At 1410, the method may include receiving an indication of a grant received at the UE relating to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmissions to the energy harvesting device, data transmissions to the energy harvesting device, or data receptions from the energy harvesting device. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The energy collection instruction component 830 is executed.

[0221] At 1415, the method may include communicating with the energy harvesting device in accordance with the grant. The operations of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference Figure 8 The energy harvesting communication component 835 is used to perform the above operation.

[0222] Fig.15 1 is a flowchart of a method 1500 for supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described herein. Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0223] At 1505, the method may include receiving a grant from a network entity to allocate a resource set for use by the UE. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The grant receiving component 825 is executed.

[0224] At 1510, the method may include receiving an indication of a grant received at the UE relating to communications between the UE and an energy harvesting device, wherein the communications include at least one of energy provision transmissions to the energy harvesting device, data transmissions to the energy harvesting device, or data receptions from the energy harvesting device. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8The energy collection instruction component 830 is executed.

[0225] At 1515, the method may include receiving a message indicating a time range, a frequency range, or a combination thereof to which the grant applies, wherein the resource set is located within the time range, the frequency range, or a combination thereof. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The resource message component 845 is used to execute.

[0226] At 1520, the method may include communicating with the energy harvesting device in accordance with the grant. The operations of 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 8 The energy harvesting communication component 835 is used to perform the above operation.

[0227] Fig.16 1600 is a flowchart of a method 1600 for supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 The network entity performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0228] At 1605, the method may include sending a grant allocating a resource set for use by the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.12 The grant sending component 1225 is executed.

[0229] At 1610, the method may include sending an indication that a grant sent to the UE is related to communications between the UE and the energy harvesting device, wherein the communications include at least one of energy provision transmissions to the energy harvesting device, data transmissions to the energy harvesting device, or data receptions from the energy harvesting device. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.12 The energy collection instruction component 1230 is executed.

[0230] Fig.171700 is a flowchart of a method 1700 for supporting techniques for performing passive IoT communications according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0231] At 1705, the method may include sending a grant allocating a resource set for use by the UE. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.12 The grant sending component 1225 is executed.

[0232] At 1710, the method may include sending an indication that a grant sent to the UE is related to communications between the UE and the energy harvesting device, wherein the communications include at least one of energy provision transmissions to the energy harvesting device, data transmissions to the energy harvesting device, or data receptions from the energy harvesting device. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.12 The energy collection instruction component 1230 is executed.

[0233] At 1715, the method may include sending a second grant allocating a second set of resources for communication between the UE and the energy harvesting device. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.12 The grant sending component 1225 is executed.

[0234] At 1720, the method may include sending a message indicating a time range, a frequency range, or a combination thereof to which the grant and the second grant apply, wherein the resource set and the second resource set are located within the time range, the frequency range, or a combination thereof. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig.12 The resource message component 1235 is used to execute.

[0235] The following provides an overview of various aspects of the disclosure:

[0236] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving a grant of a set of resources allocated for use by the UE from a network entity; receiving an indication that the grant received at the UE is related to communication between the UE and an energy harvesting device, wherein the communication comprises at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device; and communicating with the energy harvesting device based on the grant.

[0237] Aspect 2: A method according to Aspect 1, wherein receiving the indication further comprises: receiving a message explicitly indicating that the grant is related to the communication between the UE and the energy harvesting device, wherein the message is a radio resource control message, a medium access control (MAC) control element (MAC-CE) message, or a downlink control information message.

[0238] Aspect 3: A method according to any one of Aspects 1 to 2, wherein receiving the indication further comprises: receiving a message indicating a plurality of resources dedicated to energy harvesting communications; and identifying that the grant is related to the communication between the UE and the energy harvesting device based at least in part on the plurality of resources including the resource set.

[0239] Aspect 4: According to the method described in any one of Aspects 1 to 3, the method further includes: receiving a message indicating a time range, a frequency range, or a combination thereof to which the grant applies, wherein the resource set is located within the time range, the frequency range, or a combination thereof.

[0240] Aspect 5: The method according to aspect 4, wherein the message is a radio resource control message, a medium access control (MAC) control element (MAC-CE) message, or a downlink control information message.

[0241] Aspect 6: The method according to any one of aspects 1 to 5, wherein the set of resources related to the communication between the UE and the energy harvesting device includes a duration greater than 14 symbols.

[0242] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: receiving a second grant from the network entity to allocate a second resource set for the communication between the UE and the energy harvesting device; and receiving a message indicating the time range, frequency range, or a combination thereof to which the grant and the second grant apply, wherein the resource set and the second resource set are within the time range, the frequency range, or a combination thereof.

[0243] Aspect 8: The method according to aspect 7, wherein the resource set and the second resource set are adjacent within the time range.

[0244] Aspect 9: The method according to any one of aspects 7 to 8, wherein the frequency resource set in the resource set is different from the second frequency resource set in the second resource set.

[0245] Aspect 10: The method according to any one of aspects 7 to 9, wherein the message is a radio resource control message, a medium access control (MAC) control element (MAC-CE) message or a downlink control information message.

[0246] Aspect 11: The method according to any one of aspects 1 to 10, further comprising: receiving a message indicating whether the UE is to send the energy providing transmission to the energy harvesting device to power on the energy harvesting device.

[0247] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the resource set includes one or more uplink configured time slots, one or more downlink configured time slots, or a combination thereof for the communication between the UE and the energy harvesting device.

[0248] Aspect 13: A method according to any one of Aspects 1 to 12, wherein communicating with the energy harvesting device further comprises: sending the energy provision transmission to the energy harvesting device in accordance with the grant to power on the energy harvesting device, wherein the UE sends the energy provision transmission in a time slot configured for a downlink or a time slot configured for an uplink, or both.

[0249] Aspect 14: The method according to Aspect 13, wherein the UE sends the energy provision signal to the energy harvesting device in one or more resources in the resource set that are adjacent to the data signal sent to or received from the energy harvesting device.

[0250] Aspect 15: A method according to any one of Aspects 1 to 14, wherein communicating with the energy harvesting device further comprises: receiving a data signal from the energy harvesting device according to the grant, wherein the UE receives the data signal in a time slot configured for a downlink, a time slot configured for an uplink, or both.

[0251] Aspect 16: A method according to any one of Aspects 1 to 15, wherein communicating with the energy harvesting device further comprises: sending a data signal to the energy harvesting device according to the grant, wherein the UE sends the data signal in a time slot configured for a downlink, a time slot configured for an uplink, or both.

[0252] Aspect 17: The method according to any one of aspects 1 to 16, wherein the grant is an uplink grant or a downlink grant related to the communication between the UE and the energy harvesting device.

[0253] Aspect 18: The method according to any one of aspects 1 to 17, wherein the UE communicates with the energy harvesting device according to time division duplexing, frequency division duplexing, or a combination thereof.

[0254] Aspect 19: A method for wireless communication at a network entity, the method comprising: sending a grant of a set of resources allocated for use by a UE; and sending an indication that the grant sent to the UE is related to communication between the UE and an energy harvesting device, wherein the communication includes at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device.

[0255] Aspect 20: A method according to Aspect 19, wherein sending the indication further comprises: sending a message explicitly indicating that the grant is related to the communication between the UE and the energy harvesting device, wherein the message is a radio resource control message, a medium access control (MAC) control element (MAC-CE) message, or a downlink control information message.

[0256] Aspect 21: A method according to any one of Aspects 19 to 20, wherein sending the indication further comprises: sending a message indicating a plurality of resources dedicated to energy harvesting communications, wherein the resource set implicitly indicates that the grant is related to the communication between the UE and the energy harvesting device based at least in part on the resource set being included in the plurality of resources.

[0257] Aspect 22: According to any one of Aspects 19 to 21, the method further includes: sending a message indicating a time range, a frequency range, or a combination thereof to which the grant applies, wherein the resource set is located within the time range, the frequency range, or a combination thereof.

[0258] Aspect 23: The method according to aspect 22, wherein the message is a radio resource control message, a medium access control (MAC) control element (MAC-CE) message or a downlink control information message.

[0259] Aspect 24: The method according to any one of aspects 19 to 23, wherein the set of resources related to the communication between the UE and the energy harvesting device includes a duration greater than 14 symbols.

[0260] Aspect 25: According to the method described in any one of Aspects 19 to 24, the method further includes: sending a second grant to allocate a second resource set for the communication between the UE and the energy harvesting device; and sending a message indicating the time range, frequency range, or a combination thereof to which the grant and the second grant apply, wherein the resource set and the second resource set are within the time range, the frequency range, or a combination thereof.

[0261] Aspect 26: The method according to Aspect 25, wherein the resource set and the second resource set are adjacent within the time range.

[0262] Aspect 27: A method according to any one of Aspects 25 to 26, wherein the frequency resource set of the resource set is different from the second frequency resource set of the second resource set.

[0263] Aspect 28: The method according to any one of aspects 25 to 27, wherein the message is a radio resource control message, a medium access control (MAC) control element (MAC-CE) message or a downlink control information message.

[0264] Aspect 29: According to any one of aspects 19 to 28, the method further comprises: sending a message indicating whether the UE is to send the energy providing transmission to the energy harvesting device to power on the energy harvesting device.

[0265] Aspect 30: A method according to any one of Aspects 19 to 29, wherein the resource set includes one or more uplink configured time slots, one or more downlink configured time slots, or a combination thereof for the communication between the UE and the energy harvesting device.

[0266] Aspect 31: According to the method described in any one of Aspects 19 to 30, the method further includes: sending the energy provision transmission before the resource set to power on the energy harvesting device, wherein the network entity sends the energy provision transmission in a downlink configured time slot, an uplink configured time slot, or both.

[0267] Aspect 32: According to the method described in any one of Aspects 19 to 31, the method further includes: receiving a data signal from the energy harvesting device, wherein the network entity receives the data signal in a time slot configured for a downlink, a time slot configured for an uplink, or both.

[0268] Aspect 33: According to the method described in any one of Aspects 19 to 32, the method further includes: sending a data signal to the energy harvesting device, wherein the network entity sends the data signal in a time slot configured for a downlink, a time slot configured for an uplink, or both.

[0269] Aspect 34: A method according to any one of aspects 19 to 33, wherein the grant is an uplink grant or a downlink grant related to the communication between the UE and the energy harvesting device.

[0270] Aspect 35: The method according to any one of aspects 19 to 34, wherein the network entity configures the UE to communicate with the energy harvesting device according to time division duplexing, frequency division duplexing, or a combination thereof.

[0271] Aspect 36: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 18.

[0272] Aspect 37: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing a method according to any one of aspects 1 to 18.

[0273] Aspect 38: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 18.

[0274] Aspect 39: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 19 to 35.

[0275] Aspect 40: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 19 to 35.

[0276] Aspect 41: A non-transitory computer-readable medium storing a code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 19 to 35.

[0277] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0278] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0279] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0280] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0281] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features implementing the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0282] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to transfer from one place to another.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0283] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0284] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0285] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0286] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the technology. However, the technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0287] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving a grant from a network entity allocating a set of resources for use by the UE; receiving an indication that the grant received at the UE relates to communication between the UE and an energy harvesting device, wherein the communication comprises at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device; as well as Communicating with the energy harvesting device based on the grant.

2. The method of claim 1 , wherein receiving the indication further comprises: A message is received that explicitly indicates that the grant is related to the communication between the UE and the energy harvesting device, wherein the message is a radio resource control message, a medium access control (MAC) control element (MAC-CE) message, or a downlink control information message.

3. The method of claim 1 , wherein receiving the indication further comprises: receiving a message indicating a plurality of resources dedicated to energy harvesting communications; as well as The grant is identified as being related to the communication between the UE and the energy harvesting device based at least in part on the plurality of resources comprising the set of resources.

4. The method according to claim 1, further comprising: A message is received indicating a time range, a frequency range, or a combination thereof to which the grant applies, wherein the set of resources is within the time range, the frequency range, or the combination thereof.

5. The method of claim 1, wherein the set of resources related to the communication between the UE and the energy harvesting device comprises a duration greater than 14 symbols.

6. The method according to claim 1, further comprising: receiving from the network entity a second grant allocating a second set of resources for the communication between the UE and the energy harvesting device; as well as A message is received indicating a time range, a frequency range, or a combination thereof to which the grant and the second grant apply, wherein the resource set and the second resource set are within the time range, the frequency range, or the combination thereof.

7. The method according to claim 1, further comprising: A message is received indicating whether the UE is to send the energy offer transmission to the energy harvesting device to power on the energy harvesting device.

8. The method of claim 1, wherein the resource set comprises one or more uplink configured time slots, one or more downlink configured time slots, or a combination thereof for the communication between the UE and the energy harvesting device.

9. The method of claim 1 , wherein communicating with the energy harvesting device further comprises: The energy offering transmission is sent to the energy harvesting device in accordance with the grant to power on the energy harvesting device, wherein the UE sends the energy offering transmission in a downlink configured time slot or an uplink configured time slot or both.

10. The method of claim 1, wherein communicating with the energy harvesting device further comprises: A data signal is received from the energy harvesting device in accordance with the grant, wherein the UE receives the data signal in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

11. The method of claim 1 , wherein communicating with the energy harvesting device further comprises: A data signal is sent to the energy harvesting device according to the grant, wherein the UE sends the data signal in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

12. A method for wireless communication at a network entity, the method comprising: sending a grant allocating a set of resources for use by a user equipment (UE); as well as An indication is sent that the grant sent to the UE is related to communication between the UE and an energy harvesting device, wherein the communication includes at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device.

13. The method according to claim 12, further comprising: The energy offering transmission is sent prior to the set of resources to power on the energy harvesting device, wherein the network entity sends the energy offering transmission in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

14. The method according to claim 12, further comprising: A data signal is received from the energy harvesting device, wherein the network entity receives the data signal in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

15. The method according to claim 12, further comprising: A data signal is sent to the energy harvesting device, wherein the network entity sends the data signal in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

16. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a grant from a network entity allocating a set of resources for use by the UE; receiving an indication that the grant received at the UE relates to communication between the UE and an energy harvesting device, wherein the communication comprises at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device; as well as Communicating with the energy harvesting device based on the grant.

17. The apparatus of claim 16, wherein the instructions for receiving the indication are further executable by the processor to cause the apparatus to: A message is received that explicitly indicates that the grant is related to the communication between the UE and the energy harvesting device, wherein the message is a radio resource control message, a medium access control (MAC) control element (MAC-CE) message, or a downlink control information message.

18. The apparatus of claim 16, wherein the instructions for receiving the indication are further executable by the processor to cause the apparatus to: receiving a message indicating a plurality of resources dedicated to energy harvesting communications; and The grant is identified as being related to the communication between the UE and the energy harvesting device based at least in part on the plurality of resources comprising the set of resources.

19. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: A message is received indicating a time range, a frequency range, or a combination thereof to which the grant applies, wherein the set of resources is within the time range, the frequency range, or a combination thereof.

20. The apparatus of claim 16, wherein the set of resources related to the communication between the UE and the energy harvesting device comprises a duration greater than 14 symbols.

21. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: receiving from the network entity a second grant allocating a second set of resources for the communication between the UE and the energy harvesting device; and A message is received indicating a time range, a frequency range, or a combination thereof to which the grant and the second grant apply, wherein the resource set and the second resource set are within the time range, the frequency range, or a combination thereof.

22. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: A message is received indicating whether the UE is to send the energy offer transmission to the energy harvesting device to power on the energy harvesting device.

23. The apparatus of claim 16, wherein the resource set comprises one or more uplink configured time slots, one or more downlink configured time slots, or a combination thereof for the communication between the UE and the energy harvesting device.

24. The apparatus of claim 16, wherein the instructions for communicating with the energy harvesting device are further executable by the processor to cause the apparatus to: The energy offering transmission is sent to the energy harvesting device in accordance with the grant to power on the energy harvesting device, wherein the UE sends the energy offering transmission in a downlink configured time slot or an uplink configured time slot or both.

25. The apparatus of claim 16, wherein the instructions for communicating with the energy harvesting device are further executable by the processor to cause the apparatus to: A data signal is received from the energy harvesting device in accordance with the grant, wherein the UE receives the data signal in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

26. The apparatus of claim 16, wherein the instructions for communicating with the energy harvesting device are further executable by the processor to cause the apparatus to: A data signal is sent to the energy harvesting device according to the grant, wherein the UE sends the data signal in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

27. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending a grant allocating a set of resources for use by a user equipment (UE); as well as An indication is sent that the grant sent to the UE is related to communication between the UE and an energy harvesting device, wherein the communication includes at least one of energy provision transmission to the energy harvesting device, data transmission to the energy harvesting device, or data reception from the energy harvesting device.

28. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to: The energy offering transmission is sent prior to the set of resources to power on the energy harvesting device, wherein the network entity sends the energy offering transmission in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

29. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to: A data signal is received from the energy harvesting device, wherein the network entity receives the data signal in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

30. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to: A data signal is sent to the energy harvesting device, wherein the network entity sends the data signal in a time slot of a downlink configuration, a time slot of an uplink configuration, or both.

Images