WO2025231715A1

WO2025231715A1 - Control signaling of a continuous wave emitter

Info

Publication number: WO2025231715A1
Application number: PCT/CN2024/091942
Authority: WO
Inventors: Zhikun WU; Le LIU; Luanxia YANG; Kazuki Takeda; Mingxi YIN; Yuchul Kim
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2024-05-09
Filing date: 2024-05-09
Publication date: 2025-11-13
Anticipated expiration: 2026-11-09

Abstract

Methods, systems, and devices for method for wireless communication are described. A wireless device may receive a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof. The wireless device may then transmit the continuous wave waveform during the one or more occasions in accordance with the configuration information.

Description

CONTROL SIGNALING OF A CONTINUOUS WAVE EMITTER

FIELD OF TECHNOLOGY

The following relates to method for wireless communication, including control signaling of a continuous wave emitter.

BACKGROUND

Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the 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, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies 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 communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .

SUMMARY

The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

A method for wireless communications by a wireless device is described. The method may include receiving a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof and transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information.

A wireless device for wireless communications is described. The wireless device may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the wireless device to receive a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof and transmit the continuous wave waveform during the one or more occasions in accordance with the configuration information.

Another wireless device for wireless communications is described. The wireless device may include means for receiving a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof and means for transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information.

A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to receive a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof and transmit the continuous wave waveform during the one or more occasions in accordance with the configuration information.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, receiving the control signal may include operations, features, means, or instructions for receiving the control signal indicating a configuration associated with the time domain parameter for periodic continuous wave waveform transmission, where the configuration includes at least one of an offset, a periodicity value, a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.

Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a downlink control information signal enabling or disabling a continuous waveform transmission, where transmitting the continuous wave waveform may be in accordance with the downlink control information signal enabling the continuous waveform transmission.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the downlink control information signal includes an indication of at least one of a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, receiving the control signal may include operations, features, means, or instructions for receiving the control signal indicating a configuration for a resource pool that includes the one or more occasions, where the time domain parameter may be associated with one or more time domain resources included in the resource pool and associated with the one or more occasions, and the frequency domain parameter may be associated with one or more frequency domain resources included in the resource pool and associated with the one or more occasions or both.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, transmitting the continuous wave waveform may include operations, features, means, or instructions for transmitting the continuous wave waveform during each reader to energy harvesting device occasion of the one or more occasions associated with the resource pool.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, transmitting the continuous wave waveform may include operations, features, means, or instructions for transmitting the continuous wave waveform during one or more energy harvesting device to reader occasions associated with the resource pool for communications from the energy harvesting device to the reader.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, transmitting the continuous wave waveform may include operations, features, means, or instructions for transmitting the continuous wave waveform during, prior to or after the one or more energy harvesting device to reader occasions for communications from the energy harvesting device to the reader or during, prior to or after the one or more energy harvesting device to reader occasions for communications from the reader to the energy harvesting device.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, receiving the control signal may include operations, features, means, or instructions for receiving the control signal indicating a configuration associated with a second wireless device, where the control signal including a physical reader to device channel communication message.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the frequency domain parameter includes at least one of a subcarrier spacing index, a physical resource block index, a device to reader subchannel index, an ambient intelligence of things (A-IoT) band index, an A-IoT carrier index, an uplink band indication, a downlink band indication, a quantity of reader to device continuous wave tones, a frequency spacing between two tones, a discrete subcarrier indication, a contiguous subcarrier indication, a frequency domain spacing between two sets of contiguous subcarriers, a type of waveform, an indication of waveform modulation, an indication of overlayed sequence, or any combination.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, receiving the control signal may include operations, features, means, or instructions for receiving the control signal indicating a configuration associated with the spatial domain parameter associated with the continuous wave waveform, where the configuration indicates precoder information associated with the continuous wave waveform, beam information associated with the continuous wave waveform, or both.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the continuous wave waveform includes energy harvesting continuous wave transmission.

In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, a continuous wave emitter included in the wireless device is controlled by a network entity, a user equipment (UE) , or both.

Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a wireless communications system that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure.

FIG. 2 shows an example of a wireless communications system that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure.

FIGs. 3A, 3B and 3C show examples of communication timelines that support control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure.

FIG. 4 shows an example of a process flow that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure.

FIGs. 5 and 6 show block diagrams of devices that support control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure.

FIG. 7 shows a block diagram of a communications manager that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure.

FIG. 8 shows a diagram of a system including a device that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure.

FIGs. 9 through 11 show flowcharts illustrating methods that support control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure.

DETAILED DESCRIPTION

A wireless communications system may support wireless communications devices (such as ambient internet of things (A-IoT) devices) . Often, wireless communications devices may use continuous wave waveforms (CWs) for transmission. For energy harvesting device to reader transmission, the transmitter may use continuous wave waveforms for backscattering. However, for reader to energy harvesting device transmission, additional continuous wave waveforms for radio frequency energy harvesting may be needed to activate the device and receive the reader to energy harvesting device transmission. In some cases, the network entity may include a continuous wave emitter. In some cases, a UE may include a continuous wave emitter. In such cases, the network entity may control the continuous wave emitter using a Uu link or an A-IoT link. Signaling techniques for UEs including a continuous wave emitter may be under developed.

One or more aspects of the present disclosure is directed to control signaling techniques for UEs including continuous wave emitters. A continuous wave emitter may receive a control signal that includes configuration information indicating one or more occasions for communications between a reader and an energy harvesting device. The continuous wave emitter then transmits the continuous wave waveform during the one or more occasions in accordance with the configuration information. In some examples, a continuous wave emitter can be controlled by a network entity via dedicated signaling (via Uu link or A-IoT link) . In some examples, the continuous wave emitter can be controlled by the network entity using control signaling. In some examples, the continuous wave emitter can be controlled by a UE (via PC5 link or another interface) . In some examples, the continuous wave emitter can be controlled by a combination of a network entity and a UE. Additionally, or alternatively, a continuous wave emitter can leverage signaling designed for A-IoT resource pool. Additionally, or alternatively, a continuous wave emitter may leverage A-IoT link message towards a second wireless device (e.g., nearby tag) . It is to be understood that a continuous wave waveform and a continuous wave have been used interchangeably in this disclosure.

Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to communication timelines and a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to control signaling of a continuous wave emitter.

FIG. 1 shows an example of a wireless communications system 100 that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105) , one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .

The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105) , as shown in FIG. 1.

As described herein, a node of the wireless communications 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, a node may be a UE 115. As another example, a 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 yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link (s) 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via backhaul communication link (s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a 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 one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .

In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and 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, a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an 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) system, such as an SMO system 180, or any combination thereof. An 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 transmission reception point (TRP) . One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) . In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

The split of functionality between a CU 160, a DU 165, and an 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, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper 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 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs) , or some combination thereof, and the DUs 165, RUs 170, or both 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 a DU 165 and an 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 multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) . In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.

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

For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB node (s) 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) . The IAB donor and IAB node (s) 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) . Additionally, or alternatively, the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.

IAB node (s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) . A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node (s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node (s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node (s) 104) . Additionally, or alternatively, IAB node (s) 104 may also be referred to as parent nodes or child nodes to other IAB node (s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node (s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node (s) 104) to receive signaling from a parent IAB node (e.g., the IAB node (s) 104) , and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.

For example, IAB node (s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link (s) 120) to the core network 130 and may act as a parent node to IAB node (s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node (s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an F1 interface to IAB node (s) 104, and the IAB node (s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165) . That is, data may be relayed to and from IAB node (s) 104 via signaling via an NR Uu interface to MT of IAB node (s) 104 (e.g., other IAB node (s) ) . Communications with IAB node (s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node (s) 104.

In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support test 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., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .

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

The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125. For example, a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR) . Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105) .

In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT) .

The communication link (s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .

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 the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) . Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

Signal waveforms transmitted via a carrier may be made up 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 employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity 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) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having 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 for the UE 115 may be restricted to one or more active BWPs.

The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of T_s=1/(Δf_max·N_f) seconds, for which Δf_max may represent a supported subcarrier spacing, and N_f may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource 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) .

Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N_f) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

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 communications system 100 and may be referred to as a transmission time interval (TTI) . In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .

Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. 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 the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE) .

A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) ) . In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

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 for different types of devices.

In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105) . In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105) . The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

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

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

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

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

In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) . In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.

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 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (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 the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.

The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may 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 a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

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 the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .

A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.

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

In some examples, transmissions by a device (e.g., by a network entity 105 or a 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 a network entity 105 to a UE 115) . The UE 115 may report feedback that indicates 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 sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded. The 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 type codebook, a linear combination type codebook, a port selection type codebook) . Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170) , a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .

A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive 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 receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) . The 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 a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .

The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link (s) 125, a 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 in relatively poor radio conditions (e.g., low signal-to-noise conditions) . In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

A wireless communications system may support communications between different types of devices. The devices may include a passive A device, a semi-passive B device, an active C device, an active C+ device and an NB IoT device. The devices may operate according to parameters defined in Table 1.

Table 1

Some wireless communications systems may support communications between radio frequency identification (RFID) reader and tag. A tag may include an envelop detector and receive carrier wave from reader. In a wireless communications system supporting ambient internet of things (A-IoT) , a network entity 105 may communicate with a UE 115 and a tag. In some examples, the UE may act as a reader in this example. A tag can may be associated with energy harvesting and energy storage.

A wireless communications system may support communications between a first device (1 uW) , a second device (100 uW) and a third device (100 uW) . For communications between an energy harvesting device and a reader, continuous wave may be used for backscattering, which can be used for energy harvesting. In some cases, using continuous wave for backscattering may not be sufficient. Assuming small frequency shift for device to reader (e.g., for communications between an energy harvesting device and a reader) backscattering, an emitter may transmit the continuous wave for backscattering in the same spectrum as device to reader communications.

Additionally, or alternatively, the continuous wave for backscattering may use single-tone waveform for easy interference cancellation. However, for reader to device transmission of the devices described herein (e.g., a first device (1 uW) , a second device (100 uW) and a third device (100 uW) ) , additional continuous wave for radio frequency energy harvesting may be needed to activate the device and receive the reader to device communications. Assuming same antenna is shared for radio frequency energy harvesting and reader to device communication reception, the continuous wave for energy harvesting can be transmitted in the same spectrum as reader to device communications. In some examples, the continuous wave for energy harvesting may use same waveform as reader to device communications for efficient power conversion (i.e., no new waveform) .

One or more aspects of the present disclosure provide for a procedure based on continuous wave for radio frequency energy harvesting used for one or more devices. In some examples, the wireless communications system 100 may support continuous wave inside topology and continuous wave outside topology. The continuous wave inside/outside topology may be network controlled. For continuous wave (for device to reader or energy harvesting) emitter located outside of topology, a continuous wave emitter may be included in a network entity 105. In some examples, a continuous wave emitter may be included in a UE 115. In such cases, the continuous wave emitter may be controlled by network via Uu link or via A-IoT link. One or more aspects depicted herein provide for techniques for transmitting control signaling to a continuous wave emitter.

In some examples, a continuous wave emitter may be included in a wireless device (e.g., a UE 115) . The wireless device may receive a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof. The wireless device may then transmit the continuous wave waveform during the one or more occasions in accordance with the configuration information.

FIG. 2 shows an example of a wireless communications system 200 that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure. The wireless communications system 200 may implement or may be implemented by aspects of the wireless communications system 100. For example, the wireless communications system 200 may include a wireless device 115-a (e.g., UE) , a network entity 105-a, an A-IoT device 220 and a reader 225, which may be examples of corresponding devices described with reference to FIG. 1. In some examples, the reader 225 may be or may be included in a network entity 105. Additionally, or alternatively, the wireless device 115-a may include a continuous wave emitter.

The network entity 105-a may transmit a control signal 205 that includes configuration information. In some examples, the configuration information may indicate one or more occasions for communications between a reader 225 and an energy harvesting device. The energy harvesting device may harvest energy from the continuous waveform, and may be, for example, an A-Iot device 220. In some cases, the configuration information may further indicate a time domain parameter associated with a continuous wave waveform 215, a frequency domain parameter associated with the continuous wave waveform 215, or a spatial domain parameter associated with the continuous wave waveform 215, or any combination thereof. The wireless device 115-amay include a continuous wave emitter. The continuous wave emitter may transmit the continuous wave waveform 215 during the one or more occasions in accordance with the configuration information.

In some cases, the continuous wave emitter may be controlled by the network entity 105-a via dedicated signaling (e.g., control signal 205) (via Uu link or A-IoT link) . For periodic continuous wave transmission between reader 225 and the energy harvesting device (A-IoT 220) , the network entity 105-a may configure periodic reader 225 to device (A-IoT 220) continuous wave transmission via a signal. The signal may include at least one of an RRC signaling, a system information block, a paging message, a physical reader to device channel (PRDCH) , or any combination thereof. In some examples, the signal may include an indication of an offset, a periodicity, a start, an end, and a duration of each transmission instance. For example, the wireless device 115-a may receive the control signal 205 indicating a configuration associated with the time domain parameter for periodic continuous wave waveform 215 transmission, where the configuration may include at least one of an offset, a periodicity value, a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof. In some examples, the network entity 105 may further use bitmap to denote which NR slot/symbol include a transmission for reader 225 to device (A-IoT 220) continuous wave, for each transmission instance. In some cases, the wireless communications system 200 may support the re-use or extension of sidelink resource allocation mode 1.

In some examples, the continuous wave transmission may include a semi-persistent reader 225 to device (A-IoT 220) continuous wave transmission. In this case, in addition to receiving a control signal 205, the wireless device 115-a may receive a reader 225 to device (A-IoT 220) downlink control information signal (or PRDCH) to enable or disable the reader 225 to device (A-IoT 220) continuous wave transmission. In some examples, the downlink control information may be included in the control signal 205 or in a different signal received at the wireless device 115-a. For example, the wireless device 115-a may receive a downlink control information signal enabling or disabling a continuous waveform transmission, where transmitting the continuous wave waveform 215 is in accordance with the downlink control information signal enabling the continuous waveform transmission. In such cases, the network entity 105-a may use paging to turn on and/or turn off the continuous wave emitter (e.g., offset and/or duration may be pre-defined or indicated in paging message) .

For dynamic reader 225 to device (A-IoT 220) continuous wave transmission, the network entity 105-a may use downlink control information signal (or PRDCH) to enable the reader 225 to device (A-IoT 220) continuous wave transmission. In such cases, the downlink control information signal may indicate a start, an end, and a duration of each transmission instance. For instance, the wireless device 115-a may receive a downlink control information signal enabling or disabling a continuous waveform transmission. The downlink control information signal may further include an indication of at least one of a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof. Alternatively, the duration of each transmission instance and the start of each transmission instance may be pre-defined.

In some examples, different from NR configured grants, physical uplink shared channels and physical uplink control channels, duration of each reader 225 to device (A-IoT 220) transmission instance may be larger than 1 slot. In some examples, the network entity 105-a may transmit the control signal in accordance with a new downlink control information format, a new radio network temporary identifier value, or both. In some cases, the continuous wave emitter in the wireless device may support individual searching space for downlink control information and may be used for resource scheduling. In some examples, the downlink control information designed for an intermediate node may be reused for a continuous wave emitter, with signaling modification.

As one example, the wireless device 115-a may use the configuration information to transmit a continuous wave waveform 215 during slot k to k+2. The wireless device 115-a may be configured to transmit the continuous wave waveform 215 with a periodicity of p. During the following transmission opportunity, the wireless device 115-a may transmit continuous wave waveform 215 during slot k+p to k+p+2.

In some examples, the wireless device 115-a may receive a frequency domain configuration including a frequency domain parameter. The frequency domain parameter may include at least one of a subcarrier spacing index (1 or multiple) , a physical resource block index, a device (A-IoT 220) to reader 225 subchannel (or subband) index, an A-IoT band index, an A-IoT carrier index, an uplink band indication, a downlink band indication, a quantity of reader 225 to device (A-IoT 220) continuous wave tones, a frequency spacing between two tones, a discrete subcarrier indication, a contiguous subcarrier indication, an indication of a quantity of contiguous subcarriers (e.g., a frequency chunk) , a frequency domain spacing between two sets of contiguous subcarriers, a type of waveform (DFT-S-OFDM) , an indication of waveform modulation, an indication of overlayed sequence (M, ZC, gold, random, multi-sine, etc. ) , or any combination thereof. In some examples, multi-sine may describe phase for each subcarrier and may be the same or increasing pi by each subcarrier. The wireless device 115-a may generate a continuous waveform in accordance with the frequency domain configuration including the frequency domain parameter.

In some examples, if the continuous wave emitter is controlled by dedicated signaling, then the frequency domain configuration including frequency domain parameter may be included in the control signal 205 (e.g., downlink control signal, an RRC, a system information block, a PRDCH, etc. ) . In some examples, the continuous wave emitter can be controlled by a UE (via PC5 link or another interface) . In some examples, the continuous wave emitter can be controlled by a combination of a network entity and a UE. The control signal 205, as depicted herein, may include spatial-domain information. In some examples, if the network entity 105-a is aware of an appropriate precoder or beam for the continuous wave emitter to use when communicating with a target device, then the network entity 105-a may include such information in the control signal 205. For example, the wireless device may receive the control signal indicating a configuration associated with the spatial domain parameter associated with the continuous wave waveform 215. In some cases, the configuration may indicate precoder information associated with the continuous wave waveform 215, beam information associated with the continuous wave waveform 215, or both. On the other hand, if the network entity 105-a is not aware of the appropriate precoder or beam, then the control signal 205 may indicate the continuous wave emitter to use precoder-cycling or random-beamforming. In such cases, the cycle may be long enough so that A-IoT backscatter transmission can be finished within the time that the continuous wave emitter uses a particular precoder or beamforming. The wireless device 115-a may generate a continuous waveform in accordance with the spatial domain configuration including the spatial domain parameter.

In some cases, the techniques depicted herein may be applied for energy harvesting continuous wave transmissions. In some cases, the network entity 105-a may indicate whether the continuous wave emitter is to transmit a continuous wave for energy harvesting or backscatter link data transmission by new signaling in downlink control information, MAC control element, RRC, radio network temporary identifier, searching space, waveform indication, etc. In some examples, the network entity 105-amay communicate according to a spectrum, a discontinuous reception and transmission, a power, a bandwidth, and other related capabilities of the continuous wave emitter. In some examples, the continuous wave emitter may transmit periodic or semi-static synchronization signal.

FIGs. 3A, 3B and 3C show examples of communication timelines 300, 305 and 310 that support control signaling of continuous wave emitter in accordance with one or more aspects of the present disclosure. The communication timelines 300, 305 and 310 may implement or may be implemented by aspects of the wireless communications system 100 and the wireless communications system 200. For example, the communication timelines 300, 305 and 310 may implement or may be implemented by a wireless device (e.g., UE) including a continuous wave emitter and a network entity 105, which may be examples of corresponding devices described with reference to FIG. 1. FIGs. 3A, 3B and 3C depict reader to device communication 350-a, 350-b and 350-c and device to reader communication 355-a, 355-b, and 355-c.

In some examples, a continuous wave emitter may leverage signaling designed for an A-IoT resource pool (or a set of resources) . As described with reference to FIG. 2, a continuous wave emitter may receive a control signal including configuration information and may transmit a continuous wave waveform in accordance with the configuration information. In some examples, a continuous wave emitter may be configured with A-IoT resource pool (in time domain) . information. As described in FIG. 3A, there may be a guard period 360 between a reader to device communication 350-a and a device to reader communication 355-a. At 315, the continuous wave emitter may transmit reader to device continuous wave waveform in all slots or symbols of A-IoT resource pool. For instance, the wireless device may receive the control signal indicating a configuration for a resource pool that includes the one or more occasions. In some examples, the time domain parameter may be associated with one or more time domain resources included in the resource pool and associated with the one or more occasions, and the frequency domain parameter may be associated with one or more frequency domain resources included in the resource pool and associated with the one or more occasions or both. The continuous wave emitter may transmit the continuous wave waveform during each reader to energy harvesting device occasion of the one or more occasions associated with the resource pool. This technique may be associated with high pow consumption. If A-IoT resource pool is not contiguous in the time domain, then the continuous wave emitter may or may not transmit a continuous wave in a gap between resources of the resource pool. A continuous wave emitter may transmit using a single tone if the continuous wave emitter transmits continuous wave waveform in A-IoT forward link (e.g., to support reader to device communication 350 (350-a, 350-b, 350-c) ) .

In some examples, the continuous wave emitter may transmit reader to device continuous wave waveform in slots or symbols corresponding to device to reader communication occasions 355 (e.g., 355-a, 355-b, 355-c) of the resource pool. At 320, the continuous wave emitter may transmit the continuous wave waveform during one or more energy harvesting device to reader occasions associated with the resource pool for communications from the energy harvesting device to the reader. For example, the energy harvesting device to reader occasion may occur during a set of one or more slots, and the continuous wave emitter may transmit the continuous wave waveform during the set of one or more slots.

In some examples, the continuous wave emitter may transmit reader to device continuous wave waveform in transmit occasions corresponding to device to reader communication occasions. At 325, the continuous wave emitter may transmit the continuous wave waveform during, prior to or after the one or more energy harvesting device to reader occasions for communications from the energy harvesting device to the reader or during, prior to or after the one or more energy harvesting device to reader occasions for communications from the reader to the energy harvesting device. In some examples, the time before or after the device to reader communication occasions may be predefined. Additionally, or alternatively, whether to use pre-defined value or dynamically configured value can also be indicated by the network entity. In case of FIG. 3A, some duration before reader to device communication for continuous wave transmission (for energy harvesting) may be pre-defined or configured from network entity. In some cases, this may also be re-use/extension of sidelink resource allocation mode 2. In some cases, an A-IoT resource pool configuration can be dynamically configured (via downlink control information) , periodically (via RRC, system information block) , semi-persistent (via RRC/system information block and dynamically enabled or disabled via downlink control information) . In some cases, an A-IoT resource pool configuration may include an offset, start, end, bitmap, and period.

In some examples, a continuous wave emitter may leverage an A-IoT link message towards other tag (e.g., nearby tag) . For example, a continuous wave emitter may decode an A-IoT on-off keying (OOK) signal. For example, the continuous wave emitter may decode full or partial (e.g., control/head portion of a message) reader to device packet towards other tag. As depicted in FIG. 3B, the continuous wave emitter may receive the control signal indicating a configuration associated with a second wireless device, where the control signal includes a physical reader to device channel communication message.

In some examples, a reader to device continuous wave transmission may at least cover a device to reader transmission from another tag (e.g., start after reader to device continuous wave transmission, start after reader to device continuous wave transmission with delay, start before reader to device continuous wave transmission with and/or end after reader to device continuous wave transmission) . In this case, the continuous wave waveform transmission cover device to reader ambiguity window 375, as shown at 335. As used herein, the term “window” refers to a certain amount of time.

In some examples, a device to radio transmission window for a tag can be dynamically configured in reader to device packet. Alternatively, without device to radio transmission window, continuous wave emitter may emit a continuous wave according to default values map to control types (e.g., if the device to reader communication is associated with ACK/NACK, then the continuous wave can be short) . In some examples, a device to reader resource (window) can be pre-defined (e.g., using T1_min 365 and T1_max 370, which may each represent an amount of time) , or can be dynamically configured in a reader to device packet, as shown at 330.

Similarly, as depicted in FIG. 3C, T1_min_CW and T1_max_CW may each represent an amount of time and their values may be predefined or may be defined by dynamically configuring T1_CW. The values for T_CW_before 380 and/or T_CW_after 385 may be predefined if reader to device (may be with ambiguity window 375) resource is configured by device to reader. In some examples, the continuous wave emitter may transmit a continuous wave when a reader to device packet is received from an associated reader.

In some examples, a continuous wave emitter may transmit a continuous wave when a received reader to device packet is received from an associated (configured by reader) tag. In some cases, the continuous wave emitter may be controlled by leveraging A-IoT resource pool signaling. In some cases, the reader to device continuous wave may determine continuous wave tone’s frequency according to resource pool configuration. For example, a tone for reader to device continuous wave may be located in the middle of device to radio transmission occupied bandwidth (6^th subcarrier, 7^th subcarrier, 6.5 subcarrier of physical resource block in the middle of occupied bandwidth) . In some examples, subchannel can be sub-band, device to reader occupied band, etc.

If the continuous wave emitter is controlled by A-IoT link message towards other tag, then the continuous wave emitter may decide reader to device continuous wave transmission tone’s frequency according to resource block or subcarriers where forward link packet is received (e.g., in the middle) .

FIG. 4 shows an example of a process flow 400 that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure. The process flow 400 includes a wireless device 115-b, an energy harvesting device 405 (e.g., A-IoT device) , and a network entity 105-b, which may be examples of the corresponding devices as described with respect to FIGs. 1 and 2. In the following description of the process flow 400, the operations between the wireless device 115-b, the energy harvesting device 405, and the network entity 105-b may be performed in a different order than the example order shown. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time. Although depicted as UEs, it is to be understood that a continuous wave emitter may be included in other devices. Additionally, or alternatively, the wireless device and/or the network entity 105-b may be configured to operate as a reader communicating with the energy harvesting device 405.

At 410, the wireless device 115-b may receive a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof.

At 415, the wireless device 115-b may identify the time domain parameter, frequency domain parameter and spatial domain parameter indicated in the control signal.

At 420, the wireless device 115-b may transmit, to the energy harvesting device 405, the continuous wave waveform during the one or more occasions in accordance with the configuration information. At 425, the energy harvesting device 405 and the network entity 105-b may communicate based on receiving the continuous wave waveform.

FIG. 5 shows a block diagram 500 of a device 505 that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, the communications manager 520) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 510 may provide a 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 control signaling of a continuous wave emitter) . Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

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

The communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be examples of means for performing various aspects of control signaling of a continuous wave emitter as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

In some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .

Additionally, or alternatively, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications 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, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .

In some examples, the communications manager 520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for receiving a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof. The communications manager 520 is capable of, configured to, or operable to support a means for transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information.

By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources.

FIG. 6 shows a block diagram 600 of a device 605 that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a device 505 or a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one of more components of the device 605 (e.g., the receiver 610, the transmitter 615, the communications manager 620) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 610 may provide a 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 control signaling of a continuous wave emitter) . Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

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

The device 605, or various components thereof, may be an example of means for performing various aspects of control signaling of a continuous wave emitter as described herein. For example, the communications manager 620 may include a control signal component 625 a continuous wave waveform component 630, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The control signal component 625 is capable of, configured to, or operable to support a means for receiving a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof. The continuous wave waveform component 630 is capable of, configured to, or operable to support a means for transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information.

FIG. 7 shows a block diagram 700 of a communications manager 720 that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure. The communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein. The communications manager 720, or various components thereof, may be an example of means for performing various aspects of control signaling of a continuous wave emitter as described herein. For example, the communications manager 720 may include a control signal component 725, a continuous wave waveform component 730, a transmission enabling component 735, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) .

The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The control signal component 725 is capable of, configured to, or operable to support a means for receiving a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof. The continuous wave waveform component 730 is capable of, configured to, or operable to support a means for transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information.

In some examples, to support receiving the control signal, the control signal component 725 is capable of, configured to, or operable to support a means for receiving the control signal indicating a configuration associated with the time domain parameter for periodic continuous wave waveform transmission, where the configuration includes at least one of an offset, a periodicity value, a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.

In some examples, the transmission enabling component 735 is capable of, configured to, or operable to support a means for receiving a downlink control information signal enabling or disabling a continuous waveform transmission, where transmitting the continuous wave waveform is in accordance with the downlink control information signal enabling the continuous waveform transmission.

In some examples, the downlink control information signal includes an indication of at least one of a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.

In some examples, to support receiving the control signal, the control signal component 725 is capable of, configured to, or operable to support a means for receiving the control signal indicating a configuration for a resource pool that includes the one or more occasions, where the time domain parameter is associated with one or more time domain resources included in the resource pool and associated with the one or more occasions, and the frequency domain parameter is associated with one or more frequency domain resources included in the resource pool and associated with the one or more occasions or both.

In some examples, to support transmitting the continuous wave waveform, the continuous wave waveform component 730 is capable of, configured to, or operable to support a means for transmitting the continuous wave waveform during each reader to energy harvesting device occasion of the one or more occasions associated with the resource pool.

In some examples, to support transmitting the continuous wave waveform, the continuous wave waveform component 730 is capable of, configured to, or operable to support a means for transmitting the continuous wave waveform during one or more energy harvesting device to reader occasions associated with the resource pool for communications from the energy harvesting device to the reader.

In some examples, to support transmitting the continuous wave waveform, the continuous wave waveform component 730 is capable of, configured to, or operable to support a means for transmitting the continuous wave waveform during, prior to or after the one or more energy harvesting device to reader occasions for communications from the energy harvesting device to the reader or during, prior to or after the one or more energy harvesting device to reader occasions for communications from the reader to the energy harvesting device.

In some examples, to support receiving the control signal, the control signal component 725 is capable of, configured to, or operable to support a means for receiving the control signal indicating a configuration associated with a second wireless device, where the control signal including a physical reader to device channel communication message.

In some examples, the frequency domain parameter includes at least one of a subcarrier spacing index, a physical resource block index, a device to reader subchannel index, an A-IoT band index, an A-IoT carrier index, an uplink band indication, a downlink band indication, a quantity of reader to device continuous wave tones, a frequency spacing between two tones, a discrete subcarrier indication, a contiguous subcarrier indication, a frequency domain spacing between two sets of contiguous subcarriers, a type of waveform, an indication of waveform modulation, an indication of overlayed sequence, or any combination.

In some examples, to support receiving the control signal, the control signal component 725 is capable of, configured to, or operable to support a means for receiving the control signal indicating a configuration associated with the spatial domain parameter associated with the continuous wave waveform, where the configuration indicates precoder information associated with the continuous wave waveform, beam information associated with the continuous wave waveform, or both. In some examples, the continuous wave waveform includes energy harvesting continuous wave transmission. In some examples, a continuous wave emitter included in the wireless device is controlled by a network entity, a UE, or both.

FIG. 8 shows a diagram of a system 800 including a device 805 that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure. The device 805 may be an example of or include components of a device 505, a device 605, or a UE 115 as described herein. The device 805 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) . The device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input/output (I/O) controller, such as an I/O controller 810, a transceiver 815, one or more antennas 825, at least one memory 830, code 835, and at least one processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845) .

The I/O controller 810 may manage input and output signals for the device 805. The I/O controller 810 may also manage peripherals not integrated into the device 805. In some cases, the I/O controller 810 may represent a physical connection or port to an external peripheral. In some cases, the I/O controller 810 may utilize an operating system such as or another known operating system. Additionally, or alternatively, the I/O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller 810 may be implemented as part of one or more processors, such as the at least one processor 840. In some cases, a user may interact with the device 805 via the I/O controller 810 or via hardware components controlled by the I/O controller 810.

In some cases, the device 805 may include a single antenna. However, in some other cases, the device 805 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bi-directionally via the one or more antennas 825 using wired or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825, may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.

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

The at least one processor 840 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) . In some cases, the at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 840. The at least one processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting control signaling of a continuous wave emitter) . For example, the device 805 or a component of the device 805 may include at least one processor 840 and at least one memory 830 coupled with or to the at least one processor 840, the at least one processor 840 and the at least one memory 830 configured to perform various functions described herein.

In some examples, the at least one processor 840 may include multiple processors and the at least one memory 830 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 840 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 840) and memory circuitry (which may include the at least one memory 830) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 840 or a processing system including the at least one processor 840 may be configured to, configurable to, or operable to cause the device 805 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 835 (e.g., processor-executable code) stored in the at least one memory 830 or otherwise, to perform one or more of the functions described herein.

The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for receiving a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof. The communications manager 820 is capable of, configured to, or operable to support a means for transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information.

By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, and improved utilization of processing capability.

In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the at least one processor 840 to cause the device 805 to perform various aspects of control signaling of a continuous wave emitter as described herein, or the at least one processor 840 and the at least one memory 830 may be otherwise configured to, individually or collectively, perform or support such operations.

FIG. 9 shows a flowchart illustrating a method 900 that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure. The operations of the method 900 may be implemented by a UE or its components as described herein. For example, the operations of the method 900 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At 905, the method may include receiving a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof. The operations of 905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed by a control signal component 725 as described with reference to FIG. 7.

At 910, the method may include transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information. The operations of 910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed by a continuous wave waveform component 730 as described with reference to FIG. 7.

FIG. 10 shows a flowchart illustrating a method 1000 that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure. The operations of the method 1000 may be implemented by a UE or its components as described herein. For example, the operations of the method 1000 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At 1005, the method may include receiving a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof. The operations of 1005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed by a control signal component 725 as described with reference to FIG. 7.

At 1010, the method may include receiving a downlink control information signal enabling or disabling a continuous waveform transmission, where transmitting the continuous wave waveform is in accordance with the downlink control information signal enabling the continuous waveform transmission. The operations of 1010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed by a transmission enabling component 735 as described with reference to FIG. 7.

At 1015, the method may include transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information. The operations of 1015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed by a continuous wave waveform component 730 as described with reference to FIG. 7.

FIG. 11 shows a flowchart illustrating a method 1100 that supports control signaling of a continuous wave emitter in accordance with one or more aspects of the present disclosure. The operations of the method 1100 may be implemented by a UE or its components as described herein. For example, the operations of the method 1100 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At 1105, the method may include receiving a control signal including configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof. The operations of 1105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed by a control signal component 725 as described with reference to FIG. 7.

At 1110, the method may include receiving a configuration for a resource pool that includes the one or more occasions, where the time domain parameter is associated with one or more time domain resources included in the resource pool and associated with the one or more occasions, and the frequency domain parameter is associated with one or more frequency domain resources included in the resource pool and associated with the one or more occasions or both. The operations of 1110 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed by a control signal component 725 as described with reference to FIG. 7.

At 1115, the method may include transmitting the continuous wave waveform during each reader to energy harvesting device occasion of the one or more occasions associated with the resource pool. The operations of 1115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1115 may be performed by a continuous wave waveform component 730 as described with reference to FIG. 7.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communications at a wireless device, comprising: receiving a control signal comprising configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof; and transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information.

Aspect 2: The method of aspect 1, wherein receiving the control signal further comprises: receiving the control signal indicating a configuration associated with the time domain parameter for periodic continuous wave waveform transmission, wherein the configuration comprises at least one of an offset, a periodicity value, a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.

Aspect 3: The method of any of aspects 1 through 2, further comprising: receiving a downlink control information signal enabling or disabling a continuous waveform transmission, wherein transmitting the continuous wave waveform is in accordance with the downlink control information signal enabling the continuous waveform transmission.

Aspect 4: The method of aspect 3, wherein the downlink control information signal comprises an indication of at least one of a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.

Aspect 5: The method of any of aspects 1 through 4, wherein receiving the control signal further comprises: receiving the control signal indicating a configuration for a resource pool that comprises the one or more occasions, wherein the time domain parameter is associated with one or more time domain resources included in the resource pool and associated with the one or more occasions, and the frequency domain parameter is associated with one or more frequency domain resources included in the resource pool and associated with the one or more occasions or both.

Aspect 6: The method of aspect 5, wherein transmitting the continuous wave waveform further comprises: transmitting the continuous wave waveform during each reader to energy harvesting device occasion of the one or more occasions associated with the resource pool.

Aspect 7: The method of any of aspects 5 through 6, wherein transmitting the continuous wave waveform further comprises: transmitting the continuous wave waveform during one or more energy harvesting device to reader occasions associated with the resource pool for communications from the energy harvesting device to the reader.

Aspect 8: The method of any of aspects 5 through 7, wherein transmitting the continuous wave waveform further comprises: transmitting the continuous wave waveform during, prior to or after the one or more energy harvesting device to reader occasions for communications from the energy harvesting device to the reader or during, prior to or after the one or more energy harvesting device to reader occasions for communications from the reader to the energy harvesting device.

Aspect 9: The method of any of aspects 1 through 8, wherein receiving the control signal further comprises: receiving the control signal indicating a configuration associated with a second wireless device, wherein the control signal comprising a physical reader to device channel communication message.

Aspect 10: The method of any of aspects 1 through 9, wherein the frequency domain parameter comprises at least one of a subcarrier spacing index, a physical resource block index, a device to reader subchannel index, an ambient intelligence of things (A-IoT) band index, an A-IoT carrier index, an uplink band indication, a downlink band indication, a quantity of reader to device continuous wave tones, a frequency spacing between two tones, a discrete subcarrier indication, a contiguous subcarrier indication, a frequency domain spacing between two sets of contiguous subcarriers, a type of waveform, an indication of waveform modulation, an indication of overlayed sequence, or any combination.

Aspect 11: The method of any of aspects 1 through 10, wherein receiving the control signal further comprises: receiving the control signal indicating a configuration associated with the spatial domain parameter associated with the continuous wave waveform, wherein the configuration indicates precoder information associated with the continuous wave waveform, beam information associated with the continuous wave waveform, or both.

Aspect 12: The method of any of aspects 1 through 11, wherein the continuous wave waveform comprises energy harvesting continuous wave transmission.

Aspect 13: The method of any of aspects 1 through 11, wherein a continuous wave emitter included in the wireless device is controlled by a network entity, a user equipment (UE) , or both.

Aspect 14: A wireless device for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the wireless device to perform a method of any of aspects 1 through 12.

Aspect 15: A wireless device for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 12.

Aspect 16: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 12.

It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications 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, as well as other systems and radio technologies not explicitly mentioned herein.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU) , a neural processing unit (NPU) , an 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 the alternative, the processor may be any processor, controller, microcontroller, or state machine. A 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 in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”

As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “acomponent” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”

The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A wireless device, comprising:

one or more memories storing processor-executable code; and

one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the wireless device to:

receive a control signal comprising configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof; and

transmit the continuous wave waveform during the one or more occasions in accordance with the configuration information.
The wireless device of claim 1, wherein, to receive the control signal, the one or more processors are individually or collectively further operable to execute the code to cause the wireless device to:

receive the control signal indicating a configuration associated with the time domain parameter for periodic continuous wave waveform transmission, wherein the configuration comprises at least one of an offset, a periodicity value, a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.
The wireless device of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the wireless device to:

receive a downlink control information signal enabling or disabling a continuous waveform transmission, wherein transmitting the continuous wave waveform is in accordance with the downlink control information signal enabling the continuous waveform transmission.
The wireless device of claim 3, wherein the downlink control information signal comprises an indication of at least one of a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.
The wireless device of claim 1, wherein, to receive the control signal, the one or more processors are individually or collectively further operable to execute the code to cause the wireless device to:

receive the control signal indicating a configuration for a resource pool that comprises the one or more occasions, wherein the time domain parameter is associated with one or more time domain resources included in the resource pool and associated with the one or more occasions, and the frequency domain parameter is associated with one or more frequency domain resources included in the resource pool and associated with the one or more occasions or both.
The wireless device of claim 5, wherein, to transmit the continuous wave waveform, the one or more processors are individually or collectively further operable to execute the code to cause the wireless device to:

transmit the continuous wave waveform during each reader to energy harvesting device occasion of the one or more occasions associated with the resource pool.
The wireless device of claim 5, wherein, to transmit the continuous wave waveform, the one or more processors are individually or collectively further operable to execute the code to cause the wireless device to:

transmit the continuous wave waveform during one or more energy harvesting device to reader occasions associated with the resource pool for communications from the energy harvesting device to the reader.
The wireless device of claim 5, wherein, to transmit the continuous wave waveform, the one or more processors are individually or collectively further operable to execute the code to cause the wireless device to:

transmit the continuous wave waveform during, prior to or after the one or more energy harvesting device to reader occasions for communications from the energy harvesting device to the reader or during, prior to or after the one or more energy harvesting device to reader occasions for communications from the reader to the energy harvesting device.
The wireless device of claim 1, wherein, to receive the control signal, the one or more processors are individually or collectively further operable to execute the code to cause the wireless device to:

receive the control signal indicating a configuration associated with a second wireless device, wherein the control signal comprising a physical reader to device channel communication message.
The wireless device of claim 1, wherein the frequency domain parameter comprises at least one of a subcarrier spacing index, a physical resource block index, a device to reader subchannel index, an ambient intelligence of things (A-IoT) band index, an A-IoT carrier index, an uplink band indication, a downlink band indication, a quantity of reader to device continuous wave tones, a frequency spacing between two tones, a discrete subcarrier indication, a contiguous subcarrier indication, a frequency domain spacing between two sets of contiguous subcarriers, a type of waveform, an indication of waveform modulation, an indication of overlayed sequence, or any combination.
The wireless device of claim 1, wherein, to receive the control signal, the one or more processors are individually or collectively further operable to execute the code to cause the wireless device to:

receive the control signal indicating a configuration associated with the spatial domain parameter associated with the continuous wave waveform, wherein the configuration indicates precoder information associated with the continuous wave waveform, beam information associated with the continuous wave waveform, or both.
The wireless device of claim 1, wherein the continuous wave waveform comprises energy harvesting continuous wave transmission.
The wireless device of claim 1, wherein a continuous wave emitter included in the wireless device is controlled by a network entity, a user equipment (UE) , or both.
A method for wireless communications at a wireless device, comprising:

receiving a control signal comprising configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof; and

transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information.
The method of claim 14, wherein receiving the control signal further comprises:

receiving the control signal indicating a configuration associated with the time domain parameter for periodic continuous wave waveform transmission, wherein the configuration comprises at least one of an offset, a periodicity value, a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.
The method of claim 14, further comprising:

receiving a downlink control information signal enabling or disabling a continuous waveform transmission, wherein transmitting the continuous wave waveform is in accordance with the downlink control information signal enabling the continuous waveform transmission.
The method of claim 16, wherein the downlink control information signal comprises an indication of at least one of a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.
The method of claim 14, wherein receiving the control signal further comprises:

receiving the control signal indicating a configuration for a resource pool that comprises the one or more occasions, wherein the time domain parameter is associated with one or more time domain resources included in the resource pool and associated with the one or more occasions, and the frequency domain parameter is associated with one or more frequency domain resources included in the resource pool and associated with the one or more occasions or both.
The method of claim 18, wherein transmitting the continuous wave waveform further comprises:

transmitting the continuous wave waveform during each reader to energy harvesting device occasion of the one or more occasions associated with the resource pool.
The method of claim 18, wherein transmitting the continuous wave waveform further comprises:

transmitting the continuous wave waveform during one or more energy harvesting device to reader occasions associated with the resource pool for communications from the energy harvesting device to the reader.
The method of claim 18, wherein transmitting the continuous wave waveform further comprises:

transmitting the continuous wave waveform during, prior to or after the one or more energy harvesting device to reader occasions for communications from the energy harvesting device to the reader or during, prior to or after the one or more energy harvesting device to reader occasions for communications from the reader to the energy harvesting device.
The method of claim 14, wherein receiving the control signal further comprises:

receiving the control signal indicating a configuration associated with a second wireless device, wherein the control signal comprising a physical reader to device channel communication message.
The method of claim 14, wherein the frequency domain parameter comprises at least one of a subcarrier spacing index, a physical resource block index, a device to reader subchannel index, an ambient intelligence of things (A-IoT) band index, an A-IoT carrier index, an uplink band indication, a downlink band indication, a quantity of reader to device continuous wave tones, a frequency spacing between two tones, a discrete subcarrier indication, a contiguous subcarrier indication, a frequency domain spacing between two sets of contiguous subcarriers, a type of waveform, an indication of waveform modulation, an indication of overlayed sequence, or any combination.
The method of claim 14, wherein receiving the control signal further comprises:

receiving the control signal indicating a configuration associated with the spatial domain parameter associated with the continuous wave waveform, wherein the configuration indicates precoder information associated with the continuous wave waveform, beam information associated with the continuous wave waveform, or both.
The method of claim 14, wherein the continuous wave waveform comprises energy harvesting continuous wave transmission.
A wireless device for wireless communications, comprising:

means for receiving a control signal comprising configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof; and

means for transmitting the continuous wave waveform during the one or more occasions in accordance with the configuration information.
The wireless device of claim 26, wherein the means for receiving the control signal further comprise:

means for receiving the control signal indicating a configuration associated with the time domain parameter for periodic continuous wave waveform transmission, wherein the configuration comprises at least one of an offset, a periodicity value, a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.
The wireless device of claim 26, further comprising:

means for receiving a downlink control information signal enabling or disabling a continuous waveform transmission, wherein transmitting the continuous wave waveform is in accordance with the downlink control information signal enabling the continuous waveform transmission.
The wireless device of claim 28, wherein the downlink control information signal comprises an indication of at least one of a start of each transmission instance, an end of each transmission instance, a duration of each transmission instance, or any combination thereof.
A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to:

receive a control signal comprising configuration information indicating one or more occasions for communications between a reader and an energy harvesting device, the configuration information further indicating a time domain parameter associated with a continuous wave waveform, a frequency domain parameter associated with the continuous wave waveform, or a spatial domain parameter associated with the continuous wave waveform, or any combination thereof; and

transmit the continuous wave waveform during the one or more occasions in accordance with the configuration information.