Device triggered backscatter communication

Abstract

Methods, systems, and devices for wireless communication are described. The described techniques provide signaling for configuring an energy scheduling request or a communication scheduling request from a semi-passive user equipment (UE) to a network. The semi-passive UE may send a message indicating the UE category type to a serving network entity (e.g., indicating that the UE is a semi-passive UE). The network entity may send control signaling indicating a configuration for the UE to send an energy scheduling request or a communication scheduling request. The UE may send an energy scheduling request or a communication scheduling request according to the configuration. In response to the energy scheduling request, the network entity may indicate resources for the energy transfer signal, and the UE may monitor and receive the energy transfer signal in the indicated resources. In response to a communication scheduling request, the network entity may indicate resources for data transmission.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. patent application No. 17 / 746,797, entitled “DEVICE TRIGGERING BACKSCATTER COMMUNICATIONS,” filed by Wang et al. on May 17, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including device-triggered backscatter communications. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. 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 use 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 for a communication device, which may be referred to as a user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting device-triggered backscatter communications. For example, the described technology provides signaling for configuring an energy scheduling request or a communication scheduling request from a semi-passive user equipment (UE) to a network. A semi-passive UE may send a message indicating a UE category type of the UE to a serving network entity (e.g., indicating that the UE is a semi-passive UE). In response, the network entity may send control signaling indicating a configuration for the UE to send an energy scheduling request or a communication scheduling request. The UE may send an energy scheduling request or a communication scheduling request according to the configuration. In response to the energy scheduling request, the network entity may indicate resources for energy transfer signals, and the UE may monitor and receive energy transfer signals in the indicated resources. The UE may use the energy transfer signal to perform energy harvesting. In response to the communication scheduling request, the network entity may indicate resources for data transmission. The UE may use the indicated resources to communicate data transmission.

[0006] A method for wireless communication at a UE is described. The method may include: sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; receiving control signaling indicating a set of resources for sending an energy scheduling request associated with energy harvesting based on the first control message; sending the energy scheduling request associated with energy harvesting via the set of resources; and monitoring a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor, a memory coupled to the at least one processor, and instructions stored in the memory. The instructions may be executable by the at least one processor to cause the UE to: send a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; receive control signaling indicating a set of resources for sending an energy scheduling request associated with energy harvesting based on the first control message; send an energy scheduling request associated with energy harvesting via the set of resources; and monitor a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; a component for receiving control signaling indicating a set of resources for sending an energy scheduling request associated with energy harvesting based on the first control message; a component for sending the energy scheduling request associated with energy harvesting via the set of resources; and a component for monitoring a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to perform the following operations: sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; receiving control signaling indicating a set of resources for sending an energy scheduling request associated with energy harvesting based on the first control message; sending the energy scheduling request associated with energy harvesting via the set of resources; and monitoring a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving the second control message indicating the scheduling information for the energy transfer signal based on the monitoring; and performing energy harvesting using the energy transfer signal according to the scheduling information.

[0011] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, sending the energy scheduling request may include operations, features, components, or instructions for performing the following: sending an indication to distinguish the energy scheduling request from a communication scheduling request.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control signaling indicating the set of resources used to send the energy scheduling request indicates a joint configuration for energy scheduling requests and communication scheduling requests.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: sending a communication scheduling request according to the joint configuration; sending an indication to distinguish the communication scheduling request from the energy scheduling request; and monitoring a third control message indicating scheduling information for data transmission based on the communication scheduling request.

[0014] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, sending the energy scheduling request may include operations, features, components, or instructions for performing the following: sending the energy scheduling request using a waveform based on a random access channel preamble.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the energy scheduling request using the waveform based on the random access channel preamble may include operations, features, components, or instructions for performing the following: sending the energy scheduling request using random access channel resources.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the energy scheduling request may include operations, features, components, or instructions for performing the following: sending the energy scheduling request using a waveform based on one or more of the following: a Barker code, a Zadoff-Chu sequence, or a constant amplitude zero autocorrelation waveform.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing: detecting, based on the monitoring, that there is no response to the energy scheduling request within a fixed time period; and sending a second energy scheduling request based on the absence of the response to the energy scheduling request within the fixed time period.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: repeating the sending of the energy scheduling request up to a fixed number of times until the UE receives the second control message indicating scheduling information for the energy transfer signal.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving an indication of the fixed number of times.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving, via the control signaling, an indication of a separate set of resources for sending a communication scheduling request; sending the communication scheduling request via the separate set of resources; and monitoring a third control message indicating scheduling information for data transmission based on the communication scheduling request.

[0021] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: Sending the energy scheduling request may be based on one or more of: a battery status of the UE, a power input signal strength of the UE, an energy level of one or more communication tasks at the UE, or an energy level of one or more sensor tasks at the UE.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UE category indicates that the UE includes passive radio circuitry and active radio circuitry.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for transitioning to an energy harvesting state based on sending the energy scheduling request.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: sending a communication scheduling request; and transitioning from an active radio state using the active radio circuit to a passive radio state using the passive radio circuit based at least in part on sending the communication scheduling request.

[0025] A method for wireless communication at a network entity is described. The method may include: receiving a first control message from a UE indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; sending control signaling to the UE indicating a set of resources for sending an energy scheduling request associated with energy harvesting based on the first control message; receiving an energy scheduling request associated with energy harvesting from the UE via the set of resources; and sending a second control message to the UE indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0026] An apparatus for wireless communication at a network entity is described. The apparatus may include at least one processor, a memory coupled to the at least one processor, and instructions stored in the memory. The instructions may be executable by the at least one processor to cause the network entity to: receive a first control message indicating a UE category associated with the UE from a UE, wherein the UE category is associated with energy harvesting; send control signaling to the UE indicating a set of resources for sending an energy scheduling request associated with energy harvesting based on the first control message; receive an energy scheduling request associated with energy harvesting from the UE via the set of resources; and send a second control message indicating scheduling information for an energy transfer signal to the UE based on the energy scheduling request.

[0027] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for receiving a first control message from a UE indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; a component for sending to the UE control signaling indicating a set of resources for sending an energy scheduling request associated with energy harvesting based on the first control message; a component for receiving an energy scheduling request associated with energy harvesting from the UE via the set of resources; and a component for sending to the UE a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0028] 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 perform the following operations: receiving a first control message from a UE indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; sending to the UE control signaling indicating a resource set for sending an energy scheduling request associated with energy harvesting based on the first control message; receiving an energy scheduling request associated with energy harvesting from the UE via the resource set; and sending to the UE a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for performing the following: sending the energy transfer signal according to the scheduling information.

[0030] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, receiving the energy scheduling request may include operations, features, components, or instructions for receiving an indication to distinguish the energy scheduling request from a communication scheduling request.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control signaling indicating the set of resources used to send the energy scheduling request indicates a joint configuration for energy scheduling requests and communication scheduling requests.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving a communication scheduling request according to the joint configuration; receiving an indication to distinguish the communication scheduling request from the energy scheduling request; and sending a third control message indicating scheduling information for data transmission based on the communication scheduling request.

[0033] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, receiving the energy scheduling request may include operations, features, components, or instructions for performing the following: receiving the energy scheduling request using a waveform based on a random access channel preamble.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the energy scheduling request using the waveform based on the random access channel preamble may include operations, features, components, or instructions for performing the following: receiving the energy scheduling request using random access channel resources.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the energy scheduling request may include operations, features, components, or instructions for performing the following: receiving the energy scheduling request using a waveform based on one or more of the following: a Barker code, a Zadoff-Chu sequence, or a constant amplitude zero autocorrelation waveform.

[0036] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for performing: sending an indication to the UE to repeat the sending of the energy scheduling request a fixed number of times.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: sending, through the control signaling, an indication of a separate set of resources for sending a communication scheduling request; receiving the communication scheduling request from the UE via the separate set of resources; and sending a third control message indicating scheduling information for data transmission based on the communication scheduling request.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UE category indicates that the UE includes passive radio circuitry and active radio circuitry.

[0039] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for transitioning from a listening state to an active radio state based on receiving the energy scheduling request. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 An example of a wireless communication system supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 2 An example of a block diagram of user equipment supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 3 An example of a wireless communication system supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is illustrated.

[0043] Figure 4 An example of a process flow supporting device-triggered backscatter communications in accordance with one or more aspects of the present disclosure is illustrated.

[0044] Figure 5 and Figure 6 A block diagram of a device supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown.

[0045] Figure 7 A block diagram of a communications manager supporting device-triggered backscatter communications in accordance with one or more aspects of the present disclosure is shown.

[0046] Figure 8 A diagram of a system including a device supporting device-triggered backscatter communications in accordance with one or more aspects of the present disclosure is shown.

[0047] Fig. 9 and Fig.10A block diagram of a device supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown.

[0048] Fig.11 A block diagram of a communications manager supporting device-triggered backscatter communications in accordance with one or more aspects of the present disclosure is shown.

[0049] Fig.12 A diagram of a system including a device supporting device-triggered backscatter communications in accordance with one or more aspects of the present disclosure is shown.

[0050] Figures 13 to 18 A flow chart illustrating a method of supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0051] Some devices, such as user equipment (UE), Internet of Things (IoT) devices, or radio frequency identifier (RFID) devices, may be configured to perform energy harvesting, which means that the device may harvest energy from the environment (e.g., solar energy, heat, or radio frequency (RF) radiation). Specifically, some devices may harvest energy from RF radiation. For example, some devices may include a dedicated receiver architecture (e.g., a dedicated antenna and energy harvesting circuitry) for harvesting energy from its environment. Some UEs may be configured as passive devices, which means that the UE may harvest energy in the air and power transmit and receive circuits, where the transmitted signals may be backscatter modulated. Some passive UEs may be configured as semi-passive devices, which means that the UE includes a battery and may perform backscatter-based communications (e.g., passive communications initiated by a reader or network entity) and active communications (e.g., UE-powered communications that may be initiated by the UE). Currently, there is no signaling defined for a semi-passive UE to request energy transfer resources or communication resources.

[0052] The present disclosure relates to signaling for energy scheduling requests or communication scheduling requests from a semi-passive UE to a network. A semi-passive UE may send a message indicating a UE category type of the UE to a serving network entity (e.g., indicating that the UE is a semi-passive UE). In response, the network entity may send control signaling indicating a configuration for the UE to send an energy scheduling request or a communication scheduling request. The UE may send an energy scheduling request according to the configuration. For example, if the UE determines that the battery level of the UE is below a threshold, or if the determined energy level of the UE is below a threshold for a communication or sensor task at the UE, the UE may send an energy scheduling request. In response to the energy scheduling request, the network entity may indicate resources for energy transfer signals, and the UE may monitor and receive energy transfer signals in the indicated resources. The UE may use the energy transfer signal to perform energy harvesting. The UE may also send a communication scheduling request according to the configuration. In response to the communication scheduling request, the network entity may indicate resources for data transmission. For example, the UE may send a communication scheduling request based on determining that the UE has data queued to report to the network. The UE may use the indicated resources to communicate data transmission.

[0053] Aspects of the present disclosure are first described in the context of wireless communication systems. Aspects of the present disclosure are further illustrated by and described with reference to block diagrams and process flows. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams involving device-triggered backscatter communications.

[0054] Figure 1 An example of a wireless communication system 100 supporting device-triggered backscatter 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).

[0055] 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, among other names. 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), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area, and the network entity 105 and the UE 115 may support signal communications over the geographic area according to one or more radio access technologies (RATs).

[0056] 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 in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein can communicate with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

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

[0058] 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 directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 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), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0059] 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, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0060] 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)).

[0061] The functional split between CU 160, DU 165, and RU 170 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 170. 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., radio resource control (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 may each 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 the other of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions 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.

[0062] 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 the 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 host entities or IAB hosts. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a host network entity 105 (e.g., a host base station 140). One or more host network entities 105 (e.g., IAB hosts) 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 terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB host. 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.

[0063] For example, an access network (AN) or RAN may include an access node (e.g., an IAB host), communications between an IAB node 104 and one or more UEs 115. The IAB host may facilitate a connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB host may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB host may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB host and the IAB node 104 may communicate via an F1 interface according to a protocol defining a signaling message (e.g., an F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link), and may communicate with other CUs 160 (e.g., CUs 160 associated with an alternative IAB host) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0064] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB host may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB host may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0065] For example, the IAB node 104 may be referred to as a parent node that supports child IAB node communications and as a child node associated with the IAB host. The IAB host may include a CU 160 having a wired or wireless connection to the core network 130 (e.g., a backhaul communication link 120), and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB host may relay transmissions to the UE 115 via the IAB node 104, and may directly signal the transmissions to the UE 115. The CU 160 of the IAB host may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB host to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling on the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB host, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0066] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support device-triggered backscatter 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 disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0067] UE 115 may include or may be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, station, terminal, or client, among other examples. 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 multimedia / entertainment device (e.g., a radio, an MP3 player, a video device), a camera, a gaming device, a navigation / positioning device (e.g., a GNSS (Global Navigation Satellite System) device based on, for example, GPS (Global Positioning System), BeiDou, GLONASS or Galileo, ground-based equipment, etc.), a tablet computer, a laptop computer, a netbook, a smartbook, a personal computer, a smart device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a drone, a robot / robotic device, a vehicle, an in-vehicle device, a meter (e.g., a parking meter, an electric meter, a gas meter, a water meter), a monitor, a gas pump, an appliance (e.g., a kitchen appliance, a washing machine, a dryer), a location tag, a medical / health care device, an implant, a sensor / actuator, a display, or any other suitable device configured to communicate via a wireless or wired medium. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an IoT device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various items such as appliances, or vehicles, meters, etc.

[0068] 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 relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, and other examples, such as Figure 1 shown.

[0069] 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 collection of RF spectrum resources having a defined physical layer structure for supporting 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) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (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 portion 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).

[0070] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0071] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, among other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in TDD mode).

[0072] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz) of a carrier of a particular radio access technology. A device (e.g., a network entity 105, a UE 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0073] The signal waveform sent on the carrier may be composed of 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 resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The amount 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, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0074] One or more numerologies for a carrier may be supported, where the numerologies may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0075] 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 Δfmax 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).

[0076] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into multiple 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 multiple symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, the time slot may also be divided into multiple mini-time slots containing 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.

[0077] A subframe, a slot, a mini-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 transmit 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 bursts of shortened TTIs (sTTIs)).

[0078] 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)) for 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 candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded 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 .

[0079] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., via a carrier), and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0080] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0081] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

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

[0083] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0084] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide 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, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging. In one aspect, the technology disclosed herein may be applicable to MTC or IoT UEs. MTC or IoT UE may include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UE, NB-IoT (also known as CAT NB1) UE, and other types of UE. eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), and mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT) and FeNB-IoT (further enhanced NB-IoT).

[0085] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way 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 saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating with 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 subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0086] 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 or 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 applications or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency are used interchangeably herein.

[0087] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via 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 communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication 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, a group of UEs 115 communicating via D2D communication 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 of resources for D2D communication. In some other examples, D2D communications may occur between UEs 115 without involving network entity 105 .

[0088] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[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 for 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. 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). Typically, 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 is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide service 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 in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0091] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, there may be even greater atmospheric attenuation and a shorter range for the propagation of EHF transmissions than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0092] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 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) in conjunction with component carriers operating in a licensed band. Operations in an unlicensed spectrum may include other examples such as downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions.

[0093] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that 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 transmitted via the antenna ports.

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

[0095] 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 steer 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 conveyed via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed 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 the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0096] The network entity 105 or 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 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 network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

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

[0098] 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 configured set of 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 be precoded or non-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).

[0099] 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).

[0100] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate on a logical channel. The MAC layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may 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 may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between a UE 115 and a network entity 105 or a core network 130. At the PHY layer, a transport channel may be mapped to a physical channel.

[0101] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0102] The UE 115 may belong to different categories of UE 115 types, including active radio UE 115 , semi-passive radio UE 115 , and passive radio UE 115 . Example active radio UEs 115 include: eMBB UEs 115 configured to operate at 100 MHz bandwidth and 2.3 Gbps via 1 transmitter port and 4 receiver ports; Release 17 reduced capability UEs 115 configured to operate at 20 MHz bandwidth and 150 Mbps via 1 transmitter port and 1 or 2 receiver ports; Release 18 reduced capability UEs 115 configured to operate at 5 or 1.4 MHz and 3 Mbps via 1 transmitter port and 1 receiver port; eMTC Cat-M1 UEs configured to operate at 1.4 MHz and 1 Mbps via 1 transmitter port and 1 receiver port; Narrowband (NB) IoT UEs configured to operate at 180 kHz and 25 kbps via 1 transmitter port and 1 receiver port. Passive radio UEs may include passive IoT UEs 115. A semi-passive UE 115 may include both active and passive radio circuitry.A reduced capability UE 115 may operate at a smaller bandwidth with fewer antenna ports and at a reduced peak rate, resulting in a lower cost and lower power UE category.

[0103] Radio frequency identifier (RFID) is a rapidly growing technology that can impact many industries due to the potential for applications such as inventory and asset management, IoT, sustainable sensor networks (e.g., in factories), agriculture, and smart homes. RFID technology includes a small transponder or "tag" that transmits an information-bearing signal when a signal is received at the tag. RFID tags can operate without batteries or with low operating cost batteries, and can be associated with low maintenance and long life. Passive RFID devices can harvest energy in the air and power the transmit / receive circuits, where the transmitted signal can be backscatter modulated. Semi-passive or active RFID tags can be associated with higher costs than passive RFID tags.

[0104] Wireless communication systems (such as wireless communication system 100) may include industry solutions other than eMBB. For example, URLLC, MTC, 5G and above may be extended to support passive IoT. For example, some communication systems (such as wireless communication system 100) may manage passive IoT devices. Potential use cases for RFID-type sensors (e.g., passive IoT devices) may include asset management, logistics, warehousing, and manufacturing. The network entity 105 may: read or write information stored on a passive IoT device; provide energy to a passive IoT device; reflect information-bearing signals from a passive IoT; or read signals reflected by a passive IoT to decode information sent by the IoT.

[0105] Passive and semi-passive radio UEs may include energy harvesting circuits configured to harvest energy from RF radiation. For example, the energy harvesting UE 115 may be an RFID tag, an IoT device, or a semi-passive UE 115. In order to harvest RF energy, the energy harvesting UE 115 may include an RF energy harvesting circuit. RF power harvesting and input power at the power harvesting circuit may be non-linear (e.g., due to a diode). Typical input power may be greater than -20 dB. In some examples, -10 dB may be associated with turning on the power harvesting circuit. RF energy harvesting may be more efficient at lower frequencies due to diode junction capacitance and resistance (e.g., caused by frequency selective conversion efficiency).

[0106] Passive IoT devices may not include a battery, may not support RFID tag initiated data traffic (e.g., reader wakes up first), may support backscatter communications without active RF components, may support cyclic redundancy check (CRC) without forward error correction, and may have limited range (e.g., due to the lack of active radio components). Semi-passive UE 115 may include low-cost and low-power active radio circuitry to trigger backscatter-based communications. Compared to passive IoT devices, semi-passive UE 115 may perform coarse synchronization, may perform low-power forward error correction for uplink transmissions, operate primarily using backscatter, and may be more reliable and have a longer range.

[0107] The semi-passive UE 115 may send a message indicating the UE category type of the UE 115 to the serving network entity 105 (e.g., indicating that the UE 115 is a semi-passive UE 115). In response, the network entity 105 may send control signaling indicating a configuration for the UE 115 to send an energy scheduling request or a communication scheduling request. The UE 115 may send the energy scheduling request according to the configuration. For example, if the UE 115 determines that the battery level of the UE 115 is below a threshold, or if the determined energy level of the UE 115 is below a threshold for a communication or sensor task at the UE 115, the UE 115 may send the energy scheduling request. In response to the energy scheduling request, the network entity 105 may indicate resources for energy transfer signals, and the UE 115 may monitor and receive energy transfer signals in the indicated resources. The UE 115 may use the energy transfer signal to perform energy harvesting. The UE 115 may also send a communication scheduling request according to the configuration. In response to the communication scheduling request, the network entity 105 may indicate resources for data transmission. For example, UE 115 may send a communication scheduling request based on determining that UE 115 has data queued to report to the network. UE 115 may communicate the data transmission using the indicated resources.

[0108] Figure 2 An example of a block diagram 200 of a semi-passive UE 115-a supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is illustrated. In some examples, the block diagram 200 may implement aspects of the wireless communication system 100. The semi-passive UE 115-a may be an example of a UE 115 as described herein.

[0109] The semi-passive UE 115-a may include a passive radio circuit 205, an active radio circuit 210, and an energy harvesting circuit 215. The energy harvesting circuit 215 may harvest energy from the environment or from a dedicated energy transfer signal 235 (such as an energy transfer signal received in response to an energy scheduling request from the semi-passive UE 115-a). The passive radio circuit 205 may be used for reader-initiated communications 230, similar to passive IoT devices. The passive radio circuit 205 may use backscatter to respond to reader-initiated communications. The active radio circuit 210 may be used for communications 220 initiated by the semi-passive UE 115-a (e.g., initiated by an RFID tag). For example, the active radio circuit 210 may be used to convey energy scheduling or communication scheduling signals, such as energy scheduling requests and communication scheduling requests.

[0110] The active radio circuit 210 may communicate primarily based on backscatter. The active radio circuit 210 may be used under a duty cycle constraint (e.g., X transmissions within s within Y seconds or X mJ used within a certain period of time (e.g., hours or days)). The duty cycle constraint may be configured by the reader (e.g., the network entity 105) based on the battery capacity of the semi-passive UE 115-a. In some cases, the duty cycle constraint may be pre-configured for the semi-passive UE 115-a before the semi-passive UE 115-a establishes a link with the reader. For communications that exceed the duty cycle constraint of the active radio circuit 210, the semi-passive UE 115-a may switch to using the passive radio circuit 205. The semi-passive UE 115-a may indicate to the reader whether the semi-passive UE 115-a is switching to backscatter-based communication, or the semi-passive UE 115-a may use the passive radio circuit 205 to monitor signals after transmitting using the active radio circuit 210. The passive radio circuit 205 or the active radio circuit 210 may be used to receive a communication scheduling signal 225 from a reader or network entity 105 .

[0111] Semi-passive UE 115-a may actively generate signals and may perform coarse synchronization for random access channel (RACH) procedures.Active radio circuitry 210 may be less complex than other classes of UEs, and output power of active radio communications 220 may be less than other classes of UEs.

[0112] Figure 3 An example of a wireless communication system 300 that supports device-triggered backscatter communications according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 can implement aspects of the wireless communication system 100. The wireless communication system 300 can include a UE 115-b, which can be an example of a UE 115 as described herein. The wireless communication system 300 can include a network entity 105-a, which can be an example of a network entity 105 as described herein.

[0113] UE 115-b may communicate with network entity 105-a using communication link 125-a, which may be an example of an NR or LTE link between UE 115-b and network entity 105-a. Communication link 125-a may include a bidirectional link that implements both uplink communication and downlink communication. For example, UE 115-b may use communication link 125-a to send uplink signal 345 (such as uplink control signal or uplink data signal) to network entity 105-a, and network entity 105-a may use communication link 125-a to send downlink signal 350 (such as downlink control signal or downlink data signal) to UE 115-b.

[0114] As described herein, UE 115-b may be a semi-passive UE.Network entity 105-a and UE 115-b may configure resources or formats for sending energy scheduling request 315 or communication scheduling request 320 from UE 115-b to network entity 105-a.

[0115] In some cases, UE 115-b may be configured to send an energy scheduling request 315 based on one or more trigger conditions. For example, if the battery charge state of UE 115-b is below a threshold (e.g., 10% of the battery rated capacity), UE 115-b may send the energy scheduling request 315. As another example, if the ambient signal strength of UE 115-b is below a threshold (e.g., Pin<-20dBm) or below the sensitivity of the energy harvesting circuit of UE 115-b, UE 115-b may send the energy scheduling request 315. As another example, if the battery charge state of UE 115-b is below a threshold, and the ambient signal strength of UE 115-b is below a threshold or the ambient signal strength of UE 115-b is below the sensitivity of the energy harvesting circuit of UE 115-b, UE 115-b may send the energy scheduling request 315. As another example, if the UE 115-b has insufficient energy for an expected or scheduled traffic transmission, or the battery level (plus the energy harvested at the current power level) cannot sustain the next traffic transmission, the UE 115-b may send the energy scheduling request 315. As another example, if there is insufficient energy at the UE 115-b to perform a sensor or integrated circuit task (e.g., obtaining a temperature reading using Y mJ), the UE 115-b may send the energy scheduling request 315. As another example, if there is insufficient energy to perform X energy scheduling requests 315 or communication scheduling requests 320, the UE 115-b may send the energy scheduling request 315 (e.g., the UE 115-b may maintain an energy level for sending X energy scheduling requests 315 or communication scheduling requests 320).

[0116] In some cases, the UE 115-b may be configured to send the communication scheduling request 320 based on one or more trigger conditions. For example, if data or traffic becomes available at the UE 115-b (e.g., a temperature reading becomes available for reporting), the UE 115-b may send the communication scheduling request 320. As another example, the UE 115-b may send the communication scheduling request 320 for an energy status report (e.g., reporting a low battery level, requesting a battery replacement, a battery discharge report, a deep discharge request, or reporting a battery memory problem).

[0117] UE 115-b may send a first control message 305 indicating a UE category associated with UE 115-b. For example, the UE category may indicate that UE 115-b is a semi-passive UE that includes energy harvesting circuits, passive radio circuits, and active radio circuits. In response, network entity 105-a may send control signaling that configures resources for UE 115-b for UE 115-b to send energy scheduling request 315 or communication scheduling request 320.

[0118] In some cases, the control signaling 310 may be configured for a unified configuration of scheduling requests (e.g., the same resources may be configured for the energy scheduling request 315 and the communication scheduling request 320). When the UE 115-b sends the energy scheduling request 315 and the communication scheduling request 320, the UE 115-b may send an indication (e.g., via backscatter communication) of whether the scheduling request is the energy scheduling request 315 or the communication scheduling request 320.

[0119] In some cases, the control signaling 310 may configure two types of scheduling requests (e.g., different resources may be configured for the energy scheduling request 315 and the communication scheduling request 320). When the network entity 105-a receives the energy scheduling request 315 or the communication scheduling request 320 via the corresponding communication resources, the network entity 105-a may schedule resources for the energy transfer signal 325 or resources for the communication 330. The network entity 105-a may send a second control message 335 in response to the energy scheduling request 315 indicating scheduling information for the energy transfer signal 325. Accordingly, the UE 115-b may use the energy transfer signal 325 to monitor and perform energy harvesting. The network entity 105-a may send a third control message 340 in response to the communication scheduling request 320 indicating scheduling information for the communication 330. The UE 115-b may desire to receive the energy transfer signal 325, receive or send the communication 330, receive the second control message 335, or receive the third control message 340 using passive circuits.

[0120] In some cases, the network entity 105-a may schedule another device (e.g., another UE 115) that is spatially closer to the UE 115-b to send an energy transfer signal to the UE 115-b. The energy transfer signal sent by the device that is spatially closer to the UE 115-b than the network entity 105-a may deliver more energy to the UE 115-b than the energy transfer signal sent by the network entity 105-a, which is caused by the range constraints of the energy transfer signal and energy harvesting. In some cases, the UE 115-b may send a scheduling request (e.g., an energy scheduling request 315 or a communication scheduling request 320) to a device other than the network entity 105-a. For example, the UE 115-b may send a scheduling request (e.g., an energy scheduling request 315 or a communication scheduling request 320) to another UE 115 via a sidelink communication link. The other UE 115 may forward the scheduling request received from UE 115-b to the network entity, and the network entity may send a response to the scheduling request (e.g., scheduling information for energy transfer signal 325 or communication 330) to UE 115-b directly or via the other UE 115. In some cases, the other UE 115 may reserve and schedule energy transfer signal 325 or resources for communication 330 in response to the scheduling request (e.g., energy scheduling request 315 or communication scheduling request 320) received from UE 115-b. For example, UE 115-b and the other UE may operate in sidelink mode 2.

[0121] The waveform type used for the energy scheduling request 315 or the communication scheduling request 320 may be configured in the control signaling 310 or may be predefined. In some cases, the waveform type may be based on a physical random access channel (PRACH) process (e.g., a Zadoff-Chu sequence). In some cases, the waveform type used for the energy scheduling request 315 or the communication scheduling request 320 may include pre-serving several Zadoff-Chu sequences for the UE 115-b. In some cases, the energy scheduling request 315 or the communication scheduling request 320 may be sent using the PRACH resources for the UE 115-b. In some cases, the waveform type used for the energy scheduling request 315 or the communication scheduling request 320 may include a special or dedicated time domain preamble. In some cases, the waveform type used for the energy scheduling request 315 or the communication scheduling request 320 may include a Barker code, a Zadoff-Chu sequence, or a constant amplitude zero autocorrelation (CAZAC) waveform.

[0122] In some cases, if UE 115-b does not receive second control message 335 or third control message 340 in response to energy scheduling request 315 or communication scheduling request 320, respectively, UE 115-b may repeat the transmission of energy scheduling request 315 or communication scheduling request 320 within a defined duration. In some cases, the duration may be predefined. In some cases, the duration may be configured in control signaling 310.

[0123] In some cases, if UE 115-b does not receive second control message 335 or third control message 340 in response to energy scheduling request 315 or communication scheduling request 320, respectively, UE 115-b may repeat the transmission of energy scheduling request 315 or communication scheduling request 320 a defined or fixed number of times. In some cases, the defined or fixed number of times may be predefined. In some cases, the defined or fixed number of times may be configured in control signaling 310.

[0124] In some cases, if UE 115-b does not receive second control message 335 or third control message 340 in response to energy scheduling request 315 or communication scheduling request 320, respectively, UE 115-b may repeat the transmission of energy scheduling request 315 or communication scheduling request 320 after a defined duration. In some cases, the defined duration may be predefined. In some cases, the defined duration may be configured in control signaling 310.

[0125] Figure 4 An example of a process flow 400 for supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is illustrated. The process flow 400 may include a UE 115-c, which may be an example of a UE 115 as described herein. The process flow 400 may include a network entity 105-b, which may be an example of a network entity 105 as described herein. In the following description of the process flow 400, operations between the network entity 105-b and the UE 115-c may be performed in an order different from the example order shown, or operations performed by the network entity 105-b and the UE 115-c may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400.

[0126] At 405, the UE 115-c may send a first control message to the network entity 105-b indicating a UE category associated with the UE 115-c, wherein the UE category is associated with energy harvesting. In some cases, the UE category indicated in the first control message at 405 indicates that the UE 115-c includes passive radio circuitry and active radio circuitry.

[0127] At 410 , the UE 115 - c may receive control signaling from the network entity 105 - b indicating a set of resources for sending an energy scheduling request associated with energy harvesting based at least in part on the first control message.

[0128] At 415, the UE 115-c may send an energy scheduling request associated with energy harvesting via the set of resources to the network entity 105-b. In some examples, at 415, the UE 115-c may send an indication with the energy scheduling request that distinguishes the energy scheduling request from a communication scheduling request.

[0129] In some cases, sending the energy scheduling request at 415 includes sending the energy scheduling request using a waveform based on a random access channel preamble. In some cases, sending the energy scheduling request at 415 includes sending the energy scheduling request using random access channel resources.

[0130] In some cases, sending the energy scheduling request at 415 includes sending the energy scheduling request using a waveform based on one or more of: a Barker code, a Zadoff-Chu sequence, or a constant amplitude zero autocorrelation waveform.

[0131] In some cases, sending the energy scheduling request at 415 is based on one or more of: a battery status of UE 115-c, a power input signal strength of UE 115-c, an energy level of one or more communication tasks at UE 115-c, or an energy level of one or more sensor tasks at UE 115-c.

[0132] In some cases, the UE 115 - c may transition to the energy harvesting state based on sending the energy scheduling request at 415 .

[0133] At 420 , the UE 115 - c may monitor for a second control message indicating scheduling information for the energy transfer signal based on the energy scheduling request.

[0134] At 425 , the network entity 105 - b may send a second control message indicating scheduling information for the energy transfer signal to the UE 115 - c based on the energy scheduling request.

[0135] In some cases, the UE 115-c may detect an absence of a response to the energy scheduling request within the fixed time period based on the monitoring at 420. The UE 115-c may send a second energy scheduling request based on the absence of a response to the energy scheduling request within the fixed time period. In some cases, the UE 115-c may receive an indication of the fixed time period (e.g., using control signaling at 410).

[0136] In some cases, the UE 115-c may repeat the transmission of the energy scheduling request up to a fixed number of times until the UE 115-c receives a second control message indicating scheduling information for the energy transfer signal. In some cases, the UE 115-c may receive an indication of the fixed number of times (e.g., using control signaling at 410).

[0137] At 430 , the network entity 105 - b may send the energy transfer signal according to the scheduling information indicated in the second control message at 425 .

[0138] At 435 , the UE 115 - c may perform energy harvesting using the energy transfer signal.

[0139] In some cases, the control signaling at 410 may indicate a configuration for sending a communication scheduling request. For example, the control signaling at 410 may indicate a joint configuration for an energy scheduling request and a communication scheduling request.

[0140] In some cases, the UE 115-c may send a communication scheduling request to the network entity 105-b according to the joint configuration at 440. In some examples, the UE 115-c may send an indication that distinguishes the communication scheduling request from the energy scheduling request.

[0141] In some cases, the UE 115 - c may transition from an active radio state using active radio circuitry to a passive radio state using passive radio circuitry based on sending the communication scheduling request at 440 .

[0142] In some cases, at 445 , the UE 115 - c may monitor for a third control message indicating scheduling information for data transmission based on the communication scheduling request at 440 .

[0143] In some cases, at 450 , the network entity 105 - b may send a third control message indicating scheduling information for data transmission based on the communication scheduling request at 440 .

[0144] In some cases, at 455 , the network entity 105 - b and the UE 115 - c may communicate data transmission according to the scheduling information sent at 450 .

[0145] In some cases, at 410, the network entity 105-b may send, via control signaling, an indication of a separate set of resources for sending a communication scheduling request. In some cases, at 440, the UE 115-c may send a communication scheduling request to the network entity 105-b via the separate set of resources. At 445, the UE 115-c may monitor for a third control message indicating scheduling information for data transmission based on the communication scheduling request at 440. At 450, the network entity 105-b may send a third control message indicating scheduling information for data transmission based on the communication scheduling request at 440. At 455, the network entity 105-b and the UE 115-c may communicate data transmission according to the scheduling information sent at 450.

[0146] In some cases, the network entity 105-b may schedule another device (e.g., another UE 115) that is spatially closer to the UE 115-c to send an energy transfer signal to the UE 115-c. The energy transfer signal sent by the device that is spatially closer to the UE 115-c than the network entity 105-b may deliver more energy to the UE 115-c than the energy transfer signal sent by the network entity 105-b, which is caused by the range constraints of the energy transfer signal and energy harvesting. In some cases, the UE 115-c may send a scheduling request (e.g., the energy scheduling request at 415 or the communication scheduling request at 440) to a device other than the network entity 105-b. For example, the UE 115-c may send a scheduling request (e.g., the energy scheduling request at 415 or the communication scheduling request at 440) to another UE 115 via a sidelink communication link. The other UE 115 may forward the scheduling request received from the UE 115-c to the network entity, and the network entity may send a response to the scheduling request (e.g., the energy scheduling request at 415 or the communication scheduling request at 440) to the UE 115-c directly or via the other UE 115. In some cases, the other UE 115 may reserve and schedule energy transfer signals or resources for communication in response to the scheduling request received from the UE 115-c (e.g., the energy scheduling request at 415 or the communication scheduling request at 440). For example, the UE 115-c and the other UE 115 may operate in sidelink mode 2.

[0147] Figure 5 A block diagram 500 of a device 505 supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0148] Receiver 510 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 device-triggered backscatter communications). The information may be communicated to other components of device 505. Receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0149] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to device-triggered backscatter communications), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0150] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of device-triggered backscatter communications as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0151] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit), software (e.g., executed by a processor), or any combination thereof. The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present 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).

[0152] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured to or otherwise support means for performing the functionality described in the present disclosure).

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

[0154] According to examples as disclosed herein, the communication manager 520 may support wireless communications at a UE. For example, the communication manager 520 may be configured to or otherwise support a component for sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting. The communication manager 520 may be configured to or otherwise support a component for receiving control signaling indicating a resource set for sending an energy scheduling request associated with energy harvesting based on the first control message. The communication manager 520 may be configured to or otherwise support a component for sending an energy scheduling request associated with energy harvesting via a resource set. The communication manager 520 may be configured to or otherwise support a component for monitoring a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0155] By including or configuring the communication manager 520 according to the examples described herein, the device 505 (e.g., a processor controlling or otherwise coupled to the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof) can support techniques for reducing power consumption and more efficiently utilizing communication resources by configuring signaling for energy scheduling requests or communication scheduling requests from semi-passive UEs.

[0156] Figure 6A block diagram 600 of a device 605 supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or 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).

[0157] 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 device-triggered backscatter 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.

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

[0159] The device 605 or its various components may be examples of components for performing various aspects of device-triggered backscatter communications as described herein. For example, the communication manager 620 may include a UE category indication manager 625, an energy scheduling request configuration manager 630, an energy scheduling request manager 635, an energy transfer signal scheduling manager 640, or any combination thereof. The communication manager 620 may be an example of various aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0160] According to the examples disclosed herein, the communication manager 620 may support wireless communication at the UE. The UE category indication manager 625 may be configured to or otherwise support a component for sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting. The energy scheduling request configuration manager 630 may be configured to or otherwise support a component for receiving control signaling indicating a resource set for sending an energy scheduling request associated with energy harvesting based on the first control message. The energy scheduling request manager 635 may be configured to or otherwise support a component for sending an energy scheduling request associated with energy harvesting via a resource set. The energy transfer signal scheduling manager 640 may be configured to or otherwise support a component for monitoring a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0161] Figure 7 A block diagram 700 of a communication manager 720 supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of means for performing various aspects of device-triggered backscatter communications as described herein. For example, the communication manager 720 may include a UE category indication manager 725, an energy scheduling request configuration manager 730, an energy scheduling request manager 735, an energy transfer signal scheduling manager 740, an energy harvesting manager 745, a communication scheduling request configuration manager 750, a communication scheduling request manager 755, a communication scheduling manager 760, a RACH resource manager 765, a passive radio state manager 770, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0162] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. The UE category indication manager 725 may be configured to or otherwise support a component for sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting. The energy scheduling request configuration manager 730 may be configured to or otherwise support a component for receiving control signaling indicating a resource set for sending an energy scheduling request associated with energy harvesting based on the first control message. The energy scheduling request manager 735 may be configured to or otherwise support a component for sending an energy scheduling request associated with energy harvesting via a resource set. The energy transfer signal scheduling manager 740 may be configured to or otherwise support a component for monitoring a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0163] In some examples, the energy transfer signal scheduling manager 740 may be configured or otherwise support means for receiving the second control message indicating the scheduling information for the energy transfer signal based on the monitoring. In some examples, the energy harvesting manager 745 may be configured or otherwise support means for performing energy harvesting using the energy transfer signal according to the scheduling information.

[0164] In some examples, to support sending the energy scheduling request, the energy scheduling request manager 735 may be configured or otherwise support means for sending an indication that distinguishes the energy scheduling request from a communication scheduling request.

[0165] In some examples, the control signaling indicating the set of resources used to send the energy scheduling request indicates a joint configuration for an energy scheduling request and a communication scheduling request.

[0166] In some examples, the communication scheduling request manager 755 may be configured or otherwise support means for sending a communication scheduling request in accordance with the joint configuration. In some examples, the communication scheduling request manager 755 may be configured or otherwise support means for sending an indication to distinguish the communication scheduling request from the energy scheduling request. In some examples, the communication scheduling manager 760 may be configured or otherwise support means for monitoring a third control message indicating scheduling information for data transmission based on the communication scheduling request.

[0167] In some examples, to support sending the energy scheduling request, the energy scheduling request manager 735 may be configured or otherwise support means for sending the energy scheduling request using a waveform based on a random access channel preamble.

[0168] In some examples, to support sending the energy scheduling request using the waveform based on the random access channel preamble, the RACH resource manager 765 may be configured or otherwise support means for sending the energy scheduling request using random access channel resources.

[0169] In some examples, to support sending the energy scheduling request, the energy scheduling request manager 735 may be configured to or otherwise support means for sending the energy scheduling request using a waveform based on one or more of the following: a Barker code, a Zadoff-Chu sequence, or a constant amplitude zero autocorrelation waveform.

[0170] In some examples, the energy transfer signal scheduling manager 740 may be configured or otherwise support means for detecting, based on the monitoring, that there is no response to the energy scheduling request within a fixed time period. In some examples, the energy scheduling request manager 735 may be configured or otherwise support means for sending a second energy scheduling request based on the absence of the response to the energy scheduling request within the fixed time period.

[0171] In some examples, the energy scheduling request manager 735 may be configured or otherwise support means for repeating the transmission of the energy scheduling request up to a fixed number of times until the UE receives the second control message indicating scheduling information for the energy transfer signal.

[0172] In some examples, the energy scheduling request manager 735 may be configured or otherwise support means for receiving an indication of the fixed number of times.

[0173] In some examples, the communication scheduling request configuration manager 750 may be configured to or otherwise support a means for receiving an indication of a separate set of resources for sending a communication scheduling request via the control signaling. In some examples, the communication scheduling request manager 755 may be configured to or otherwise support a means for sending the communication scheduling request via the separate set of resources. In some examples, the communication scheduling manager 760 may be configured to or otherwise support a means for monitoring a third control message indicating scheduling information for data transmission based on the communication scheduling request.

[0174] In some examples, sending the energy scheduling request is based on one or more of: a battery status of the UE, a power input signal strength of the UE, an energy level of one or more communication tasks at the UE, or an energy level of one or more sensor tasks at the UE.

[0175] In some examples, the UE category indicates that the UE includes passive radio circuitry and active radio circuitry.

[0176] In some examples, energy harvesting manager 745 may be configured or otherwise support means for transitioning to an energy harvesting state based on sending the energy scheduling request.

[0177] In some examples, the communication scheduling request manager 755 may be configured or otherwise support means for sending a communication scheduling request. In some examples, the passive radio state manager 770 may be configured or otherwise support means for transitioning from an active radio state using the active radio circuit to a passive radio state using the passive radio circuit based at least in part on sending the communication scheduling request.

[0178] Figure 8 A diagram of a system 800 including a device 805 supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein, or include components of these devices. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. 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 845).

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

[0180] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired link, or a wireless link as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 815 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 825 for transmission, and for demodulating packets received from one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825 may be examples of transmitters 515, transmitters 615, receivers 510, receivers 610, or any combination thereof or any components thereof as described herein.

[0181] The memory 830 may include random access memory (RAM) and read-only memory (ROM). The memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform various functions described herein. The code 835 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 835 may not be directly executable by the processor 840, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 830 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0182] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a GPU, 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 840 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 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) to enable the device 805 to perform various functions (e.g., functions or tasks that support device-triggered backscatter communications). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0183] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. For example, the communication manager 820 may be configured to or otherwise support a component for sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting. The communication manager 820 may be configured to or otherwise support a component for receiving control signaling indicating a resource set for sending an energy scheduling request associated with energy harvesting based on the first control message. The communication manager 820 may be configured to or otherwise support a component for sending an energy scheduling request associated with energy harvesting via a resource set. The communication manager 820 may be configured to or otherwise support a component for monitoring a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0184] By including or configuring a communication manager 820 according to examples as described herein, the device 805 may support techniques for achieving improved communication reliability, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing power by configuring signaling for energy scheduling requests or communication scheduling requests from semi-passive UEs.

[0185] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions that are executable by the processor 840 to cause the device 805 to perform various aspects of device-triggered backscatter communications as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0186] Fig. 9 A block diagram 900 of a device 905 supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0187] The receiver 910 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 the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0188] The transmitter 915 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 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 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0189] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of device-triggered backscatter communications as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0190] In some examples, the communication manager 920, the receiver 910, the transmitter 915, 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, a GPU, an ASIC, an FPGA or other programmable logic device, a microprocessor, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports means for performing the functions described herein. 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).

[0191] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured to or otherwise support means for performing the functionality described in the present disclosure).

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

[0193] According to the examples disclosed herein, the communication manager 920 may support wireless communication at a network entity. For example, the communication manager 920 may be configured to or otherwise support a component for receiving a first control message indicating a UE category associated with the UE from a UE, wherein the UE category is associated with energy harvesting. The communication manager 920 may be configured to or otherwise support a component for sending to the UE control signaling indicating a resource set for sending an energy scheduling request associated with energy harvesting based on the first control message. The communication manager 920 may be configured to or otherwise support a component for receiving an energy scheduling request associated with energy harvesting from the UE via a resource set. The communication manager 920 may be configured to or otherwise support a component for sending to the UE a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0194] By including or configuring the communication manager 920 according to the examples described herein, the device 905 (e.g., a processor controlling or otherwise coupled to the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof) may support techniques for reducing power consumption and more efficiently utilizing communication resources by configuring signaling for energy scheduling requests or communication scheduling requests from semi-passive UEs.

[0195] Fig.10 A block diagram 1000 of a device 1005 supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or 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).

[0196] Receiver 1010 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 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 fiber) interfaces, wireless interfaces, or any combination thereof.

[0197] The transmitter 1015 may provide means for outputting (e.g., sending, providing, conveying, transmitting) 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 fiber) 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.

[0198] The device 1005 or its various components may be examples of components for performing various aspects of device-triggered backscatter communications as described herein. For example, the communication manager 1020 may include a UE category indication manager 1025, an energy scheduling request configuration manager 1030, an energy scheduling request manager 1035, an energy transfer signal scheduling manager 1040, or any combination thereof. The communication manager 1020 may be an example of various aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to use or otherwise cooperate with the receiver 1010, the transmitter 1015, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0199] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at a network entity. The UE category indication manager 1025 may be configured to or otherwise support a component for receiving a first control message indicating a UE category associated with the UE from the UE, wherein the UE category is associated with energy harvesting. The energy scheduling request configuration manager 1030 may be configured to or otherwise support a component for sending control signaling to the UE indicating a resource set for sending an energy scheduling request associated with energy harvesting based on the first control message. The energy scheduling request manager 1035 may be configured to or otherwise support a component for receiving an energy scheduling request associated with energy harvesting from the UE via a resource set. The energy transfer signal scheduling manager 1040 may be configured to or otherwise support a component for sending a second control message indicating scheduling information for an energy transfer signal to the UE based on the energy scheduling request.

[0200] Fig.11 A block diagram 1100 of a communication manager 1120 supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of means for performing various aspects of device-triggered backscatter communications as described herein. For example, the communication manager 1120 may include a UE category indication manager 1125, an energy scheduling request configuration manager 1130, an energy scheduling request manager 1135, an energy transfer signal scheduling manager 1140, an energy transfer signal manager 1145, a communication scheduling request configuration manager 1150, a communication scheduling request manager 1155, a communication scheduling manager 1160, a RACH resource manager 1165, an active radio state manager 1170, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication 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.

[0201] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at a network entity. The UE category indication manager 1125 may be configured to or otherwise support a component for receiving a first control message indicating a UE category associated with the UE from the UE, wherein the UE category is associated with energy harvesting. The energy scheduling request configuration manager 1130 may be configured to or otherwise support a component for sending control signaling to the UE indicating a resource set for sending an energy scheduling request associated with energy harvesting based on the first control message. The energy scheduling request manager 1135 may be configured to or otherwise support a component for receiving an energy scheduling request associated with energy harvesting from the UE via a resource set. The energy transfer signal scheduling manager 1140 may be configured to or otherwise support a component for sending a second control message indicating scheduling information for an energy transfer signal to the UE based on the energy scheduling request.

[0202] In some examples, energy transfer signal manager 1145 may be configured or otherwise support means for sending the energy transfer signal according to the scheduling information.

[0203] In some examples, to support receiving the energy scheduling request, the energy scheduling request manager 1135 may be configured or otherwise support means for receiving an indication to distinguish the energy scheduling request from a communication scheduling request.

[0204] In some examples, the control signaling indicating the set of resources used to send the energy scheduling request indicates a joint configuration for an energy scheduling request and a communication scheduling request.

[0205] In some examples, the communication scheduling request manager 1155 may be configured or otherwise support means for receiving a communication scheduling request in accordance with the joint configuration. In some examples, the communication scheduling request manager 1155 may be configured or otherwise support means for receiving an indication to distinguish the communication scheduling request from the energy scheduling request. In some examples, the communication scheduling manager 1160 may be configured or otherwise support means for sending a third control message indicating scheduling information for data transmission based on the communication scheduling request.

[0206] In some examples, to support receiving the energy scheduling request, the energy scheduling request manager 1135 may be configured or otherwise support means for receiving the energy scheduling request using a waveform based on a random access channel preamble.

[0207] In some examples, to support receiving the energy scheduling request using the waveform based on the random access channel preamble, the RACH resource manager 1165 may be configured or otherwise support means for receiving the energy scheduling request using random access channel resources.

[0208] In some examples, to support receiving the energy scheduling request, the energy scheduling request manager 1135 may be configured or otherwise support means for receiving the energy scheduling request using a waveform based on one or more of the following: a Barker code, a Zadoff-Chu sequence, or a constant amplitude zero autocorrelation waveform.

[0209] In some examples, the energy transfer signal scheduling manager 1140 may be configured or otherwise support means for sending an indication to the UE of a fixed number of times to repeat the transmission of the energy scheduling request.

[0210] In some examples, the communication scheduling request configuration manager 1150 may be configured to or otherwise support a means for sending, via the control signaling, an indication of a separate set of resources for sending a communication scheduling request. In some examples, the communication scheduling request manager 1155 may be configured to or otherwise support a means for receiving the communication scheduling request from the UE via the separate set of resources. In some examples, the communication scheduling manager 1160 may be configured to or otherwise support a means for sending, based on the communication scheduling request, a third control message indicating scheduling information for data transmission.

[0211] In some examples, the UE category indicates that the UE includes passive radio circuitry and active radio circuitry.

[0212] In some examples, active radio state manager 1170 may be configured or otherwise support means for transitioning from the listening state to the active radio state based on receiving the energy scheduling request.

[0213] Fig.12A diagram of a system 1200 including a device 1205 supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a network entity 105 as described herein, or include components of these devices. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition of communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, a code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0214] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1210 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1215, from a wired receiver), and for demodulating a signal. Where applicable, transceiver 1210 or transceiver 1210 and one or more antennas 1215 or wired interfaces may be examples of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or any 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).

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

[0216] Processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, ASIC, GPU, CPU, FPGA, microcontroller, programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1235. Processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to enable device 1205 to perform various functions (e.g., functions or tasks that support device-triggered backscatter communications). For example, device 1205 or a component of device 1205 may include processor 1235 and memory 1225 coupled to processor 1235, and processor 1235 and memory 1225 are configured to perform various functions described herein. Processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions (e.g., by executing code 1230) to perform functions of device 1205.

[0217] In some examples, bus 1240 may support communications of a protocol layer of a protocol stack (e.g., within the protocol layer). In some examples, bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communications performed within a component of device 1205 or between different components of device 1205 that may be co-located or located in different locations (e.g., where device 1205 may refer to a system where one or more of communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one of the different components or divided between the different components).

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

[0219] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at a network entity. For example, the communication manager 1220 may be configured to or otherwise support a component for receiving a first control message indicating a UE category associated with the UE from a UE, wherein the UE category is associated with energy harvesting. The communication manager 1220 may be configured to or otherwise support a component for sending to the UE control signaling indicating a resource set for sending an energy scheduling request associated with energy harvesting based on the first control message. The communication manager 1220 may be configured to or otherwise support a component for receiving an energy scheduling request associated with energy harvesting from the UE via a resource set. The communication manager 1220 may be configured to or otherwise support a component for sending to the UE a second control message indicating scheduling information for an energy transfer signal based on the energy scheduling request.

[0220] By including or configuring a communication manager 1220 according to examples as described herein, the device 1205 may support techniques for achieving improved communication reliability, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing power by configuring signaling for energy scheduling requests or communication scheduling requests from semi-passive UEs.

[0221] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1235, the memory 1225, the code 1230, the transceiver 1210, or any combination thereof. For example, the code 1230 may include instructions that are executable by the processor 1235 to cause the device 1205 to perform various aspects of device-triggered backscatter communications as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0222] Fig.13 A flowchart illustrating a method 1300 for supporting device-triggered backscatter communication according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 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 1305, the method may include sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting. The operations of 1305 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The described UE category indication manager 725 is executed.

[0224] At 1310, the method may include receiving control signaling indicating a set of resources for sending an energy scheduling request associated with energy harvesting based at least in part on a first control message. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 7 The described energy scheduling requests configuration manager 730 to perform.

[0225] At 1315, the method may include sending an energy scheduling request associated with energy harvesting via the resource set. The operations of 1315 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 7 The energy scheduling request manager 735 described above is executed.

[0226] At 1320, the method may include monitoring a second control message indicating scheduling information for the energy transfer signal based at least in part on the energy scheduling request. The operations of 1320 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Figure 7 The energy transfer signal schedule manager 740 described above is executed.

[0227] Fig.14 A flowchart illustrating a method 1400 for supporting device-triggered backscatter communication according to one or more aspects of the present disclosure is shown. 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 8 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.

[0228] At 1405, the method may include sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting. The operations of 1405 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The described UE category indication manager 725 is executed.

[0229] At 1410, the method may include receiving control signaling indicating a set of resources for sending an energy scheduling request associated with energy harvesting based at least in part on a first control message. 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 7 The described energy scheduling requests configuration manager 730 to perform.

[0230] At 1415, the method may include sending an energy scheduling request associated with energy harvesting via the resource set. 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 to Figure 7 The energy scheduling request manager 735 described above is executed.

[0231] At 1420, the method may include monitoring a second control message indicating scheduling information for the energy transfer signal based at least in part on the energy scheduling request. The operations of 1420 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Figure 7 The energy transfer signal schedule manager 740 described above is executed.

[0232] At 1425, the method may include receiving a second control message indicating scheduling information for the energy transfer signal based at least in part on the monitoring. The operations of 1425 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1425 may be performed as described in reference to Figure 7 The energy transfer signal schedule manager 740 described above is executed.

[0233] At 1430, the method may include performing energy harvesting using the energy transfer signal according to the scheduling information. The operations of 1430 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1430 may be performed as described in reference to Figure 7 The energy harvesting manager 745 described above is executed.

[0234] Fig.15 A flow chart illustrating a method 1500 for supporting device-triggered backscatter communication according to one or more aspects of the present disclosure is shown. 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 in reference to Figures 1 to 8 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.

[0235] At 1505, the method may include sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting. The operations of 1505 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 7 The described UE category indication manager 725 is executed.

[0236] At 1510, the method may include receiving control signaling indicating a set of resources for sending an energy scheduling request associated with energy harvesting based at least in part on a first control message. 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 7 The described energy scheduling requests configuration manager 730 to perform.

[0237] At 1515, the method may include receiving, via control signaling, an indication of a separate set of resources for sending a communication scheduling request. 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 7 The described communication schedule requires configuration manager 750 to execute.

[0238] At 1520, the method may include sending an energy scheduling request associated with energy harvesting via a resource set. 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 7 The energy scheduling request manager 735 described above is executed.

[0239] At 1525, the method may include monitoring a second control message indicating scheduling information for the energy transfer signal based at least in part on the energy scheduling request. The operations of 1525 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described in reference to Figure 7 The energy transfer signal schedule manager 740 described above is executed.

[0240] At 1530, the method may include sending a communication scheduling request via a separate set of resources. The operations of 1530 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1530 may be performed as described in reference to Figure 7 The communication scheduling request manager 755 described above is executed.

[0241] At 1535, the method may include monitoring a third control message indicating scheduling information for data transmission based at least in part on the communication scheduling request. The operations of 1535 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1535 may be performed as described in reference to Figure 7 The communication schedule manager 760 described above is executed.

[0242] Fig.16 A flowchart illustrating a method 1600 for supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. 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 4 as well as Figures 9 to 12 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.

[0243] At 1605, the method may include receiving a first control message from the UE indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting. The operations of 1605 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The described UE category indication manager 1125 is executed.

[0244] At 1610, the method may include sending control signaling to the UE indicating a set of resources for sending an energy scheduling request associated with energy harvesting based at least in part on the first control message. 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.11 The described energy scheduling requests configuration manager 1130 to perform.

[0245] At 1615, the method may include receiving an energy scheduling request associated with energy harvesting from the UE via the resource set. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.11 The energy scheduling request manager 1135 described above is executed.

[0246] At 1620, the method may include sending a second control message indicating scheduling information for the energy transfer signal to the UE based at least in part on the energy scheduling request. The operations of 1620 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig.11 The energy transfer signal schedule manager 1140 described above is executed.

[0247] Fig.17 A flowchart illustrating a method 1700 for supporting device-triggered backscatter communications according to one or more aspects of the present disclosure is shown. 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 4 as well as Figures 9 to 12 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.

[0248] At 1705, the method may include receiving a first control message from the UE indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.11 The described UE category indication manager 1125 is executed.

[0249] At 1710, the method may include sending control signaling to the UE indicating a set of resources for sending an energy scheduling request associated with energy harvesting based at least in part on the first control message. 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.11The described energy scheduling requests configuration manager 1130 to perform.

[0250] At 1715, the method may include receiving an energy scheduling request associated with energy harvesting from the UE via the resource set. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.11 The energy scheduling request manager 1135 described above is executed.

[0251] At 1720, the method may include sending a second control message indicating scheduling information for the energy transfer signal to the UE based at least in part on the energy scheduling request. The operations of 1720 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig.11 The energy transfer signal schedule manager 1140 described above is executed.

[0252] At 1725, the method may include sending an energy transfer signal according to the scheduling information. The operations of 1725 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1725 may be performed as described in reference to Fig.11 The energy transfer signal manager 1145 described above is executed.

[0253] Fig.18 A flowchart illustrating a method 1800 for supporting device-triggered backscatter communication according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 4 as well as Figures 9 to 12 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.

[0254] At 1805, the method may include receiving a first control message from the UE indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting. The operations of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.11 The described UE category indication manager 1125 is executed.

[0255] At 1810, the method may include sending control signaling to the UE indicating a set of resources for sending an energy scheduling request associated with energy harvesting based on the first control message. The operations of 1810 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.11The described energy scheduling requests configuration manager 1130 to perform.

[0256] At 1815, the method may include sending, via control signaling, an indication of a separate set of resources for sending a communication scheduling request associated with energy harvesting based at least in part on the first control message. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.11 The described communication schedule requests configuration manager 1150 to execute.

[0257] At 1820, the method may include receiving an energy scheduling request associated with energy harvesting from a UE via a resource set. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described in reference to Fig.11 The energy scheduling request manager 1135 described above is executed.

[0258] At 1825, the method may include sending a second control message indicating scheduling information for the energy transfer signal to the UE based at least in part on the energy scheduling request. The operations of 1825 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1825 may be performed as described in reference to Fig.11 The energy transfer signal schedule manager 1140 described above is executed.

[0259] At 1830, the method may include receiving a communication scheduling request from the UE via a separate resource set. The operations of 1830 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1830 may be performed as described in reference to Fig.11 The communication scheduling request manager 1155 described is executed.

[0260] At 1835, the method may include sending a third control message indicating scheduling information for data transmission based at least in part on the communication scheduling request. The operations of 1835 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1835 may be performed as described in reference to Fig.11 The communication schedule manager 1160 described is executed.

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

[0262] Aspect 1: A method for performing wireless communication at a UE, comprising: sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; receiving control signaling indicating a resource set for sending an energy scheduling request associated with energy harvesting based at least in part on the first control message; sending an energy scheduling request associated with energy harvesting via the resource set; and monitoring a second control message indicating scheduling information for an energy transfer signal based at least in part on the energy scheduling request.

[0263] Aspect 2: The method according to aspect 1 also includes: receiving the second control message indicating the scheduling information for the energy transfer signal based at least in part on the monitoring; and performing energy harvesting using the energy transfer signal according to the scheduling information.

[0264] Aspect 3: The method according to any one of Aspects 1 to 2, wherein sending the energy scheduling request comprises: sending an indication to distinguish the energy scheduling request from a communication scheduling request.

[0265] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the control signaling indicating the resource set used to send the energy scheduling request indicates a joint configuration for an energy scheduling request and a communication scheduling request.

[0266] Aspect 5: The method according to Aspect 4 further includes: sending a communication scheduling request based on the joint configuration; sending an indication to distinguish the communication scheduling request from the energy scheduling request; and monitoring a third control message indicating scheduling information for data transmission based at least in part on the communication scheduling request.

[0267] Aspect 6: The method according to any one of aspects 1 to 5, wherein sending the energy scheduling request comprises: sending the energy scheduling request using a waveform based at least in part on a random access channel preamble.

[0268] Aspect 7: The method according to aspect 6, wherein sending the energy scheduling request using the waveform based at least in part on the random access channel preamble includes: sending the energy scheduling request using random access channel resources.

[0269] Aspect 8: A method according to any one of Aspects 1 to 7, wherein sending the energy scheduling request includes: sending the energy scheduling request using a waveform based at least in part on one or more of the following: a Barker code, a Zadoff-Chu sequence, or a constant amplitude zero autocorrelation waveform.

[0270] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: detecting, at least in part based on the monitoring, that there is no response to the energy scheduling request within a fixed time period; and sending a second energy scheduling request, at least in part based on the absence of the response to the energy scheduling request within the fixed time period.

[0271] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: repeating the sending of the energy scheduling request up to a fixed number of times until the UE receives the second control message indicating scheduling information for the energy transfer signal.

[0272] Aspect 11: The method according to aspect 10 further includes: receiving an indication of the fixed number of times.

[0273] Aspect 12: The method according to any one of Aspects 1 to 11 further includes: receiving an indication of a separate set of resources for sending a communication scheduling request through the control signaling; sending the communication scheduling request via the separate set of resources; and monitoring a third control message indicating scheduling information for data sending based at least in part on the communication scheduling request.

[0274] Aspect 13: A method according to any one of Aspects 1 to 12, wherein sending the energy scheduling request is based at least in part on one or more of: a battery status of the UE, a power input signal strength of the UE, an energy level of one or more communication tasks at the UE, or an energy level of one or more sensor tasks at the UE.

[0275] Aspect 14: The method according to any one of aspects 1 to 13, wherein the UE category indicates that the UE includes passive radio circuitry and active radio circuitry.

[0276] Aspect 15: The method according to aspect 14 further comprises: transitioning to an energy harvesting state based at least in part on sending the energy scheduling request.

[0277] Aspect 16: The method according to any one of Aspects 14 to 15 also includes: sending a communication scheduling request; and transitioning from an active radio state using the active radio circuit to a passive radio state using the passive radio circuit based at least in part on sending the communication scheduling request.

[0278] Aspect 17: A method for performing wireless communications at a network entity, comprising: receiving a first control message from a UE indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; sending control signaling to the UE indicating a resource set for sending an energy scheduling request associated with energy harvesting based at least in part on the first control message; receiving an energy scheduling request associated with energy harvesting from the UE via the resource set; and sending a second control message to the UE indicating scheduling information for an energy transfer signal based at least in part on the energy scheduling request.

[0279] Aspect 18: The method according to Aspect 17 further includes: sending the energy transfer signal according to the scheduling information.

[0280] Aspect 19: The method according to any one of Aspects 17 to 18, wherein receiving the energy scheduling request comprises: receiving an indication to distinguish the energy scheduling request from a communication scheduling request.

[0281] Aspect 20: The method according to any one of Aspects 17 to 19, wherein the control signaling indicating the resource set used to send the energy scheduling request indicates a joint configuration for energy scheduling request and communication scheduling request.

[0282] Aspect 21: The method according to Aspect 20 further includes: receiving a communication scheduling request based on the joint configuration; receiving an indication to distinguish the communication scheduling request from the energy scheduling request; and sending a third control message indicating scheduling information for data transmission based at least in part on the communication scheduling request.

[0283] Aspect 22: The method according to any one of aspects 17 to 21, wherein receiving the energy scheduling request comprises: receiving the energy scheduling request using a waveform based at least in part on a random access channel preamble.

[0284] Aspect 23: The method according to aspect 22, wherein receiving the energy scheduling request using the waveform based at least in part on the random access channel preamble includes: receiving the energy scheduling request using random access channel resources.

[0285] Aspect 24: A method according to any one of Aspects 17 to 23, wherein receiving the energy scheduling request includes: receiving the energy scheduling request using a waveform based at least in part on one or more of the following: a Barker code, a Zadoff-Chu sequence, or a constant amplitude zero autocorrelation waveform.

[0286] Aspect 25: The method according to any one of aspects 17 to 24 further includes: sending an indication to the UE of a fixed number of times to repeat the sending of the energy scheduling request.

[0287] Aspect 26: The method according to any one of Aspects 17 to 25 further includes: sending an indication of a separate set of resources for sending a communication scheduling request through the control signaling; receiving the communication scheduling request from the UE via the separate set of resources; and sending a third control message indicating scheduling information for data sending based at least in part on the communication scheduling request.

[0288] Aspect 27: The method according to any one of aspects 17 to 26, wherein the UE category indicates that the UE includes passive radio circuitry and active radio circuitry.

[0289] Aspect 28: The method of aspect 27, further comprising: transitioning from a listening state to an active radio state based at least in part on receiving the energy scheduling request.

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

[0291] Aspect 30: An apparatus for wireless communication at a UE, the apparatus comprising: at least one means for performing the method according to any one of aspects 1 to 16.

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

[0293] Aspect 32: An apparatus for performing wireless communications at a network entity, the apparatus comprising: at least one processor; a memory coupled to the at least one processor; and instructions, the instructions being stored in the memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of Aspects 17 to 28.

[0294] Aspect 33: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one means for performing the method according to any one of aspects 17 to 28.

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

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

[0297] 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 techniques described 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, including future systems and radio technologies.

[0298] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips 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.

[0299] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, GPU, FPGA or other programmable logic device, discrete gate or transistor logic, 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, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0300] The functions described herein can be implemented in hardware, software executed by a processor, or any combination thereof. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether it is described in software, firmware, middleware, microcode, hardware description language, or other terms. If implemented in software executed by a processor, the function can be stored on a computer-readable medium as one or more instructions or codes, 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 can be implemented using software, firmware, hard wiring, or any combination thereof executed by a processor. The features that implement the functions can also be physically located at different locations, including being distributed so that the parts that implement the functions are implemented at different physical locations.

[0301] Computer-readable media include both non-transient computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another.Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer.As an example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase change memory, compact disk (CD) ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or can be used to carry or store instructions or data structure forms of desired program code components and can be accessed by general or special-purpose computers or general or special-purpose processors.Any connection is appropriately referred to as computer-readable media.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of computer-readable media. 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.

[0302] As used herein (including in the claims), "or" used in a listing of items (e.g., a listing of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive listing, so that, for example, a listing 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" may 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". As used herein, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items may be employed individually, or any combination of two or more of the listed items may be employed. For example, if a composition is described as comprising components A, B, and / or C, the composition can comprise A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.

[0303] 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, etc. 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.

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

[0305] 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 "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described technology. However, these 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 described examples.

[0306] 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. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the UE to: sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; receiving control signaling indicating a set of resources for sending an energy scheduling request associated with energy harvesting based at least in part on the first control message; sending an energy scheduling request associated with energy harvesting via the set of resources; as well as Monitoring for a second control message indicating scheduling information for an energy transfer signal is performed based at least in part on the energy scheduling request.

2. The apparatus of claim 1 , wherein the instructions are further executable by the at least one processor to cause the UE to: receiving, based at least in part on the monitoring, a second control message indicating the scheduling information for the energy transfer signal; and Energy harvesting is performed using the energy transfer signal according to the scheduling information.

3. The apparatus of claim 1 , wherein the instructions for sending the energy scheduling request are executable by the at least one processor to cause the UE to: An indication is sent that distinguishes the energy scheduling request from a communication scheduling request. 4 . The apparatus according to claim 1 , wherein the control signaling indicating the set of resources used to send the energy scheduling request indicates a joint configuration for energy scheduling request and communication scheduling request.

5. The apparatus of claim 4, wherein the instructions are further executable by the at least one processor to cause the UE to: sending a communication scheduling request according to the joint configuration; sending an indication to distinguish the communication scheduling request from the energy scheduling request; and Monitoring for a third control message indicating scheduling information for data transmission is performed based at least in part on the communication scheduling request.

6. The apparatus of claim 1, wherein the instructions for sending the energy scheduling request are executable by the at least one processor to cause the UE to: The energy scheduling request is transmitted using a waveform based at least in part on a random access channel preamble.

7. The apparatus of claim 6, wherein the instructions for transmitting the energy scheduling request using the waveform based at least in part on the random access channel preamble are executable by the at least one processor to cause the UE to: The energy scheduling request is sent using random access channel resources.

8. The apparatus of claim 1, wherein the instructions for sending the energy scheduling request are executable by the at least one processor to cause the UE to: The energy scheduling request is sent using a waveform based at least in part on one or more of: a Barker code, a Zadoff-Chu sequence, or a constant amplitude zero autocorrelation waveform.

9. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: detecting, based at least in part on the monitoring, an absence of a response to the energy dispatch request within a fixed time period; and A second energy scheduling request is sent based at least in part on an absence of the response to the energy scheduling request within the fixed time period.

10. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: The sending of the energy scheduling request is repeated up to a fixed number of times until the UE receives the second control message indicating scheduling information for the energy transfer signal.

11. The apparatus of claim 10, wherein the instructions are further executable by the at least one processor to cause the UE to: An indication of the fixed number of times is received.

12. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: receiving, via the control signaling, an indication of a separate set of resources for transmitting a communication scheduling request; sending the communication scheduling request via the separate set of resources; and Monitoring for a third control message indicating scheduling information for data transmission is performed based at least in part on the communication scheduling request.

13. An apparatus according to claim 1, wherein sending the energy scheduling request is based at least in part on one or more of: a battery status of the UE, a power input signal strength of the UE, an energy level of one or more communication tasks at the UE, or an energy level of one or more sensor tasks at the UE.

14. The apparatus of claim 1, wherein the UE category indicates that the UE includes passive radio circuitry and active radio circuitry.

15. The apparatus of claim 14, wherein the instructions are further executable by the at least one processor to cause the UE to: Transitioning to an energy harvesting state is based at least in part on sending the energy scheduling request.

16. The apparatus of claim 14, wherein the instructions are further executable by the at least one processor to cause the UE to: sending a communication scheduling request; and Transitioning from an active radio state using the active radio circuitry to a passive radio state using the passive radio circuitry is based at least in part on sending the communication scheduling request.

17. An apparatus for wireless communication at a network entity, the apparatus comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the network entity to: receiving, from a user equipment (UE), a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; sending control signaling to the UE indicating a set of resources for sending an energy scheduling request associated with energy harvesting based at least in part on the first control message; receiving an energy scheduling request associated with energy harvesting from the UE via the set of resources; as well as A second control message indicating scheduling information for an energy transfer signal is sent to the UE based at least in part on the energy scheduling request.

18. The apparatus of claim 17, wherein the instructions are further executable by the at least one processor to cause the network entity to: The energy transfer signal is sent according to the scheduling information.

19. The apparatus of claim 17, wherein the instructions for receiving the energy scheduling request are executable by the at least one processor to cause the network entity to: An indication is received to distinguish the energy scheduling request from a communication scheduling request.

20. The apparatus of claim 17, wherein the control signaling indicating the set of resources for sending the energy scheduling request indicates a joint configuration for energy scheduling request and communication scheduling request.

21. The apparatus of claim 20, wherein the instructions are further executable by the at least one processor to cause the network entity to: receiving a communication scheduling request according to the joint configuration; receiving an indication to distinguish the communication scheduling request from the energy scheduling request; and A third control message indicating scheduling information for data transmission is transmitted based at least in part on the communication scheduling request.

22. The apparatus of claim 17, wherein the instructions for receiving the energy scheduling request are executable by the at least one processor to cause the network entity to: The energy scheduling request is received using a waveform based at least in part on a random access channel preamble.

23. The apparatus of claim 22, wherein the instructions for receiving the energy scheduling request using the waveform based at least in part on the random access channel preamble are executable by the at least one processor to cause the network entity to: The energy scheduling request is received using random access channel resources.

24. The apparatus of claim 17, wherein the instructions for receiving the energy scheduling request are executable by the at least one processor to cause the network entity to: The energy scheduling request is received using a waveform based at least in part on one or more of: a Barker code, a Zadoff-Chu sequence, or a constant amplitude zero autocorrelation waveform.

25. The apparatus of claim 17, wherein the instructions are further executable by the at least one processor to cause the network entity to: An indication is sent to the UE to repeat the sending of the energy scheduling request a fixed number of times.

26. The apparatus of claim 17, wherein the instructions are further executable by the at least one processor to cause the network entity to: sending, by the control signaling, an indication of a separate set of resources for sending a communication scheduling request; receiving the communication scheduling request from the UE via the separate set of resources; and A third control message indicating scheduling information for data transmission is transmitted based at least in part on the communication scheduling request.

27. The apparatus of claim 17, wherein the UE category indicates that the UE includes passive radio circuitry and active radio circuitry.

28. The apparatus of claim 27, wherein the instructions are further executable by the at least one processor to cause the network entity to: Transitioning from a listening state to an active radio state is based at least in part on receiving the energy scheduling request.

29. A method for wireless communication at a user equipment (UE), the method comprising: sending a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; receiving control signaling indicating a set of resources for sending an energy scheduling request associated with energy harvesting based at least in part on the first control message; sending an energy scheduling request associated with energy harvesting via the set of resources; as well as Monitoring for a second control message indicating scheduling information for an energy transfer signal is performed based at least in part on the energy scheduling request.

30. A method for wireless communication at a network entity, the method comprising: receiving, from a user equipment (UE), a first control message indicating a UE category associated with the UE, wherein the UE category is associated with energy harvesting; sending control signaling to the UE indicating a set of resources for sending an energy scheduling request associated with energy harvesting based at least in part on the first control message; receiving an energy scheduling request associated with energy harvesting from the UE via the set of resources; as well as A second control message indicating scheduling information for an energy transfer signal is sent to the UE based at least in part on the energy scheduling request.

Images