Scheduling and resource allocation for devices with energy harvesting capability

Abstract

Methods, systems, and devices for wireless communication are described. Energy harvesting (EH) capable devices, such as ambient Internet of Things (AIoT) devices, can be used for applications such as inventory tracking, sensing, positioning, or command systems. The EH capable devices can include a plurality of functions stored in memory. An interrogating device can send a modification command (e.g., a write command) to the EH capable device that modifies two or more functions, where the functions are stored in non-contiguous memory locations in the EH capable device. In some examples, the modification command can indicate (e.g., via bits corresponding to a memory bank of the EH capable device) which functions are to be written / modified. In some examples, an initial request can indicate the functions or memory locations to be written, which can reduce the size of the modification command. Additionally or alternatively, a new deactivation command can be introduced to deactivate and / or activate the EH capable device.

Description

Technical Field

[0001] This disclosure relates to wireless communications, including scheduling and resource allocation for devices with energy harvesting capabilities. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A 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 Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described technology relates to improved methods, systems, devices, and apparatuses for scheduling and resource allocation for devices with energy harvesting (EH) capabilities. EH-capable devices, such as environmental Internet of Things (AIoT) devices, can be used in various applications, such as inventory tracking, sensing, positioning, or command systems. EH-capable devices may include multiple functions stored in memory. An interrogating device may send modification commands (e.g., write commands) to an EH-capable device that modify two or more functions, where the functions are stored in non-contiguous memory locations within the EH-capable device. In some examples, the modification command may indicate (e.g., via bits corresponding to the memory bank of the EH-capable device) which functions will be written / modified. In some examples, an initial request may indicate the functions or memory locations to be written, which can reduce the size of the modification command. Additionally or alternatively, new deactivation commands may be introduced to deactivate the EH-capable device by indicating or for a predetermined amount of time.

[0004] A method for wireless communication by an EH-capable device is described. The method may include: receiving a control message indicating a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; sending an acknowledgment in response to the control message, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; and receiving, based on the acknowledgment, the modification command for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device.

[0005] An EH-capable device for wireless communication is described. The EH-capable device may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the EH-capable device: receives a control message indicating a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; sends an acknowledgment in response to the control message, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; and, based on the acknowledgment, receives the modification command for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device.

[0006] Another device with EH capability for wireless communication is described. The EH-capable device may include: components for receiving a control message indicating a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; components for sending an acknowledgment in response to the control message, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; and components for receiving, based on the acknowledgment, the modification command for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device.

[0007] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive a control message indicating a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; send an acknowledgment in response to the control message, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; and receive, based on the acknowledgment, the modification command for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device.

[0008] In some examples of the methods described herein, devices with EH capability, and nontransitory computer-readable media, receiving the control message may include operations, features, components, or instructions for receiving the control message that includes instructions for modifying the two or more functions.

[0009] Some examples of the methods described herein, EH-capable devices, and nontransitory computer-readable media may also include operations, features, components, or instructions for: receiving a switching signal indicating a switch from a first operating mode to a second operating mode, wherein the first operating mode may be associated with an instruction based on a control message for a function to be modified, and the second operating mode may be associated with an instruction based on a modification command for those functions to be modified, or wherein the first operating mode may be associated with the instruction based on a modification command for those functions to be modified, and the second operating mode may be associated with the instruction based on a control message for those functions to be modified.

[0010] In some examples of the methods described herein, EH-enabled devices, and nontransitory computer-readable media, receiving the control message may include operations, features, components, or instructions for receiving an indication of a communication resource for sending the acknowledgment, wherein the acknowledgment may be sent via the communication resource.

[0011] In some examples of the methods described herein, devices with EH capability, and nontransitory computer-readable media, receiving the modification command may include operations, features, components, or instructions for receiving the modification command that includes instructions for the two or more functions to be modified.

[0012] Some examples of the methods described herein, EH-capable devices, and nontransitory computer-readable media may also include operations, features, components, or instructions for: receiving a random number request via the control message; and sending an instruction for a random number via the acknowledgment and based on the random number request, wherein the modification command includes the random number.

[0013] The methods described herein, some examples of EH-capable devices and nontransitory computer-readable media may also include operations, features, components or instructions for receiving a deactivation command, wherein the deactivation command includes an indication of the duration of the deactivation.

[0014] The methods described herein, examples of EH-enabled devices, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for: receiving a deactivation command and an indication of one or more wake-up signal monitoring times; and monitoring wake-up signals during such one or more wake-up signal monitoring times.

[0015] The methods described herein, some examples of EH-capable devices and nontransitory computer-readable media may also include operations, features, components or instructions for receiving a second control message configuring a mode for deactivation and activation of the EH-capable device, wherein the mode includes an activation mode and a deactivation mode for the EH-capable device, the mode cycling between the activation mode and the deactivation mode.

[0016] A method for wireless communication by a wireless communication device is described. The method may include: sending a control message to a device with EH capability, instructing the device to send a modification command, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the device with EH capability; receiving an acknowledgment from the device with EH capability in response to the control message, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; and sending the modification command to the device with EH capability and based on the acknowledgment for the two or more functions of the device with EH capability stored in the non-contiguous memory location of the device with EH capability.

[0017] A wireless communication device for wireless communication is described. The wireless communication device may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the wireless communication device: sends a control message to an EH-capable device instructing a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; receives an acknowledgment from the EH-capable device in response to the control message, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; and sends the modification command to the EH-capable device and based on the acknowledgment for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device.

[0018] Another wireless communication device for wireless communication is described. This wireless communication device may include: components for sending a control message to a device with EH capability, instructing the device to send a modification command, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the device with EH capability; components for receiving an acknowledgment from the device with EH capability in response to the control message, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; and components for sending the modification command to the device with EH capability and, based on the acknowledgment, the modification command for the two or more functions of the device with EH capability stored in the non-contiguous memory location of the device with EH capability.

[0019] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: send a control message to an EH-capable device instructing a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; receive an acknowledgment from the EH-capable device in response to the control message, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; and send the modification command to the EH-capable device and based on the acknowledgment for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device.

[0020] In some examples of the methods, wireless communication devices, and nontransitory computer-readable media described herein, sending the control message may include operations, features, components, or instructions for sending the control message that includes instructions for the two or more functions to be modified.

[0021] Some examples of the methods, wireless communication devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a switching signal to the EH-capable device indicating a switch from a first operating mode to a second operating mode, wherein the first operating mode may be associated with an instruction based on a control message for a function to be modified, and the second operating mode may be associated with an instruction based on a modification command for those functions to be modified, or wherein the first operating mode may be associated with the instruction based on a modification command for those functions to be modified, and the second operating mode may be associated with the instruction based on a control message for those functions to be modified.

[0022] In some examples of the methods, wireless communication devices, and nontransitory computer-readable media described herein, sending the control message may include operations, features, components, or instructions for sending an indication to a communication resource for sending the acknowledgment, wherein the acknowledgment may be sent via the communication resource.

[0023] In some examples of the methods, wireless communication devices, and nontransitory computer-readable media described herein, sending the modification command may include operations, features, components, or instructions for sending the modification command that includes instructions for the two or more functions to be modified.

[0024] Some examples of the methods, wireless communication devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a random number request via the control message; and receiving an indication of a random number via the acknowledgment and based on the random number request, wherein the modification command includes the random number.

[0025] The methods, wireless communication devices, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending a deactivation command to the EH-capable device, wherein the deactivation command includes an indication of the duration of the deactivation.

[0026] Some examples of the methods, wireless communication devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a deactivation command to the EH-capable device and an indication of one or more wake-up signal monitoring times; and sending a wake-up signal during the one or more wake-up signal monitoring times.

[0027] Some examples of the methods, wireless communication devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second control message to the EH-capable device configuring a mode for deactivation and activation of the EH-capable device, wherein the mode includes an activation mode and a deactivation mode for the EH-capable device, and the mode cycles between the activation mode and the deactivation mode. Attached Figure Description

[0028] Figure 1 An example of a wireless communication system supporting the scheduling and resource allocation of devices with energy harvesting (EH) capabilities, according to one or more aspects of this disclosure, is shown.

[0029] Figure 2 An example of a wireless communication system supporting scheduling and resource allocation for devices with EH capability, according to one or more aspects of this disclosure, is shown.

[0030] Figure 3 An example of a wireless communication system supporting scheduling and resource allocation for devices with EH capability, according to one or more aspects of this disclosure, is shown.

[0031] Figure 4 An example of a signaling timing diagram supporting scheduling and resource allocation for devices with EH capabilities, according to one or more aspects of this disclosure, is shown.

[0032] Figure 5 An example of a timing diagram supporting scheduling and resource allocation for devices with EH capabilities, according to one or more aspects of this disclosure, is shown.

[0033] Figure 6 An example of a process flow supporting the scheduling and resource allocation of devices with EH capability, according to one or more aspects of this disclosure, is shown.

[0034] Figure 7 and Figure 8 A block diagram of a device supporting scheduling and resource allocation for a device with EH capability is shown, according to one or more aspects of this disclosure.

[0035] Figure 9 A block diagram is shown that supports a communication manager for scheduling and resource allocation of devices with EH capability, according to one or more aspects of this disclosure.

[0036] Figure 10 A diagram is shown illustrating a system comprising devices supporting scheduling and resource allocation for devices with EH capabilities, according to one or more aspects of this disclosure.

[0037] Figure 11 and Figure 12 A block diagram of a device supporting scheduling and resource allocation for a device with EH capability is shown, according to one or more aspects of this disclosure.

[0038] Figure 13 A block diagram is shown that supports a communication manager for scheduling and resource allocation of devices with EH capability, according to one or more aspects of this disclosure.

[0039] Figure 14 A diagram is shown illustrating a system comprising devices supporting scheduling and resource allocation for devices with EH capabilities, according to one or more aspects of this disclosure.

[0040] Figure 15 and Figure 16 A flowchart illustrating a method for scheduling and resource allocation for devices with EH capability, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0041] Some wireless communication systems can support the deployment of Ambient Internet of Things (AIoT) devices, which may include relatively low-power and low-complexity devices capable of harvesting energy from various sources, such as radio frequency waves, solar energy, thermal energy, or other environmental sources. Devices with energy harvesting (EH) capabilities, such as AIoT devices, can be used in applications such as inventory tracking, sensing, positioning, or command systems. For example, for command systems, EH-capable devices can be used in applications such as controlling irrigation systems, dispensing medication, or providing alarms. EH-capable devices can perform backscatter-based communication (e.g., transmitting data) by backscattering an interrogation signal received from another wireless communication device (e.g., a reader device). The term "interrogation signal" can refer to a signal received at an EH-capable device from another wireless communication device that provides energy to enable the EH-capable device to transmit a signal, for example, via backscatter modulation.

[0042] Devices with EH capability can include multiple functions stored in memory. An interrogating device can issue a write command to modify a portion of the memory of an EH-capable device or an erase command to erase a portion of the memory. To initiate a write or erase command, the interrogator can send a request for a random number. The EH-capable device can send an acknowledgment including the random number, and the write or erase command can include this random number as a security check. Some EH-capable devices can include multiple functions stored in memory, and when these functions are stored in non-contiguous memory locations within the EH-capable device, a single write or erase command may not be able to modify more than one but fewer than all of the functions. Furthermore, an interrogating device can issue a "kill" command to permanently disable an EH-capable device; however, there is currently no command to temporarily disable an EH-capable device.

[0043] The interrogating device may send modification commands (e.g., write commands) to an EH-capable device that modify two or more functions, where the functions are stored in non-contiguous memory locations within the EH-capable device. In some examples, the modification command may indicate (e.g., via bits corresponding to the memory bank of the EH-capable device) which functions will be written / modified. In some examples, the initial request may indicate the functions or memory locations to be written, which can reduce the size of the modification command. In some examples, the initial request may indicate resources (e.g., time and / or frequency resources) for the EH-capable device to send acknowledgment of the request. Indicating which functions can be written in the request (e.g., a downlink control information (DCI) control message) can reduce the size of the modification command and thereby reduce power consumption at the EH-capable device. Additionally or alternatively, new deactivation commands may be introduced to deactivate the EH-capable device for a predetermined amount of time.

[0044] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated by reference to signaling timing diagrams, timing diagrams, process flow diagrams, apparatus diagrams, system diagrams, and flowcharts relating to the scheduling and resource allocation of devices with energy harvesting capabilities, and are described with reference to these diagrams.

[0045] Figure 1An example of a wireless communication system 100 supporting scheduling and resource allocation for devices with energy harvesting capabilities, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0046] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0047] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

[0048] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or 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, apparatus, device, 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 UE 115. As another example, a node may be 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 UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

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

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

[0051] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) such as CU 160, a Distributed Unit (DU) such as DU 165, a Radio Unit (RU) such as RU 170, a RAN Intelligent Controller (RIC) such as 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 SMO system 180, or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0052] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) may connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or a combination thereof, and DU 165, RU 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 CU 160. Additionally or alternatively, a protocol stack functional split may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

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

[0054] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

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

[0056] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes operate as repeaters, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0057] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating 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 coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0058] In some examples, such as in carrier aggregation configurations, a carrier may have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

[0059] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0060] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for a carrier for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0061] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0062] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0063] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

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

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

[0066] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE 115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE 115 (e.g., a particular UE).

[0067] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

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

[0069] Some UE 115 devices (such as MTC or IoT devices) can be relatively low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or instruments to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0070] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0071] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private 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 prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

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

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

[0074] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is 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 these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0075] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0076] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation 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, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0077] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0078] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0079] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0080] Wireless communication system 100 can support the deployment of devices with EH capability, such as AIoT devices or radio frequency identification (RFID) devices. For example, one or more UEs 115 can be EH-capable devices. EH-capable devices, such as AIoT devices, can be used for various applications. For example, two groups of AIoT devices can be defined, where group A can be defined based on the adoption environment (e.g., indoor, outdoor, or indoor / outdoor), and group B can be defined based on functionality or application (e.g., inventory tracking, sensing, positioning, or command systems). EH-capable devices can perform backscatter-based communication (e.g., transmitting data) by backscattering interrogation signals received from another wireless communication device (e.g., a reader device, such as UE 115 or network entity 105).

[0081] A device with EH capability may include multiple functions stored in memory. An interrogating device may issue a write command to modify a portion of the memory of the EH-capable device or an erase command to erase a portion of the memory. An interrogating device (e.g., UE 115 or network entity 105) may send a modification command to the EH-capable device to modify two or more functions, where the functions are stored in non-contiguous memory locations within the EH-capable device. In some examples, the modification command may indicate (e.g., via bits corresponding to the memory bank of the EH-capable device) which functions will be written / modified. In some examples, an initial request may indicate the functions or memory locations to be written, which can reduce the size of the modification command. In some examples, the initial request may indicate resources (e.g., time and / or frequency resources) for the EH-capable device to send acknowledgment of the request. Indicating which functions can be written in a request (e.g., a DCI-like control message) can reduce the size of the modification command and thereby reduce power consumption at the EH-capable device. Additionally or alternatively, a new deactivation command may be introduced to deactivate the EH-capable device by indicating or for a predetermined amount of time.

[0082] Figure 2 An example of a wireless communication system 200 supporting scheduling and resource allocation for devices with energy harvesting capabilities, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may implement aspects of the wireless communication system 100.

[0083] Wireless communication system 200 may include network device 205, which may be an example of UE 115 or network entity 105 as described herein. Network device 205 may also be referred to as a wireless communication device. Network device 205 may be an example of an energy transfer device or an RFID reader. Wireless communication system 200 may include device 210 with EH capability. Device 210 with EH capability may be UE 115 as described herein. Device 210 with EH capability may be able to perform backscatter-based communication. In some examples, device 210 with EH capability may be an example of an IoT device, an AIoT device, an RFID tag, or any combination thereof. Device with EH capability can harvest energy over the air (e.g., via receiving an interrogation signal 215) and power a transmit / receive circuit 225 to transmit a response signal 220 to the interrogation signal by using the energy from the interrogation signal. The response signal 220 transmitted by the RFID device may be backscatter modulated (e.g., referred to as a backscatter response). In some examples, the RFID device may be semi-passive or active and may include an energy storage device (e.g., a battery). In some examples, the wireless communication system may support a dual-site architecture, in which one network device (e.g., network device 205) sends an energy transfer signal (e.g., an interrogation signal 215) to a device 210 with EH capability, and another network device may receive a response signal 220 (e.g., be able to communicate with the device with EH capability).

[0084] Devices with EH capability can be passive, semi-passive, or active. Table 1 below shows the characteristics of passive, semi-passive, and active EH-capable devices. Example applications for passive EH-capable devices include access cards or proximity cards. Example applications for semi-passive EH-capable devices include electronic toll collection or pallet tracking. Example applications for active EH-capable devices include large asset tracking or livestock tracking.

[0085] Table 1

[0086] Due to insufficient link budgets and poor communication reliability, passive EH-capable devices may have short-range capabilities (e.g., less than 10 meters). For example, the maximum transmit power of network device 205 may be limited for the transmit frequency band. For example, the effective isotropic radiated power (EIRP) of the network device may be 36 dBm. As another example, the weak backscattered signal reflected by a passive EH-capable device can limit its range. Since passive EH-capable devices are power-limited, the reflected signal power intensity is approximately inversely proportional to the fourth power of the distance. Another issue affecting the range of passive EH-enabled devices can be interference from other reader devices, other tags, and / or other communication systems. Cyclic Redundancy Check (CRC) can be used for error detection of signals involving passive EH-enabled devices.

[0087] As described herein, AIoT devices (such as device 210 with EH capability) can be used in both indoor and outdoor environments for command systems. For example, Table 2 shows different example use cases for indoor AIoT devices and the parameters associated with these use cases. Table 3 shows different example use cases for outdoor AIoT devices and the parameters associated with these use cases.

[0088] Table 2

[0089] Table 3

[0090] In some examples, network device 205 may send a write command to device 210 with EH capability. The write command may allow a query device (e.g., network device 205) to write a word to reserved memory, Electronic Product Code (EPC) memory, Tag Identifier (TID) memory, or user memory of device 210 with EH capability. Before sending the write command, network device 205 may send a random number request (also known as Req_RN) to the device with EH capability. Device 210 with EH capability may generate a random number and may send an acknowledgment of the random number request, including the random number. The write command may include this random number as a security check. In some examples, device 210 with EH capability may send a response to the write command. Table 4 shows examples of information included in the write command, and Table 5 shows examples of information included in the response to the write command. As shown in Table 4, the write command may include a field indicating that the command is a write command, an indication of the memory to be modified, an address pointer within the memory, a data field to be written to the indicated address, a random number, and a CRC field. As shown in Table 5, a response from device 210 with EH capability may include a header indicating that the write command was successful, a random number as a security check, and a CRC field.

[0091] Table 4

[0092] Table 5

[0093] In some examples, network device 205 may send a block write command to device 210 with EH capability. The block write command may allow a querying device (e.g., network device 205) to write multiple words into reserved memory, EPC memory, TID memory, or user memory of device 210 with EH capability using a single command. The block write command may be applicable to a single memory bank. Before sending the block write command, network device 205 may send a random number request to device 210 with EH capability, similar to the procedure used to send the write command. Table 6 shows examples of information included in the block write command, and Table 7 shows examples of information included in the response to the block write command. As shown in Table 6, the block write command may include a field indicating that the command is a block write command, an indication of the memory bank to be modified, an address pointer within the memory bank indicating the starting address where the block write begins, an indicator of the number of words to be written, a data field to be written to the indicated address, a random number, and a CRC field. As shown in Table 7, the response from device 210 with EH capability may include a header indicating success of the block write command, a random number, and a CRC field as a security check.

[0094] Table 6

[0095] Table 7

[0096] In some examples, network device 205 may send a block erase command to device 210 with EH capability. The block erase command may allow a device (e.g., network device 205) to erase multiple words in reserved memory, EPC memory, TID memory, or user memory of device 210 with EH capability using a single command. The block erase command may be applied to a single memory bank. Before sending the block erase command, network device 205 may send a random number request to device 210 with EH capability, similar to the procedure used to send a write command. Table 8 shows examples of information included in the block erase command, and Table 9 shows examples of information included in the response to the block erase command. As shown in Table 8, the block erase command may include fields indicating that the command is a block erase command, an indication of the memory bank to be erased, an address pointer within the memory bank indicating the starting address for the start of the block erase, an indicator of the number of words to be erased, a random number, and a CRC field. As shown in Table 9, the response from device 210 with EH capability may include a header indicating success of the block erase command, a random number as a security check, and a CRC field.

[0097] Table 8

[0098] Table 9

[0099] In some examples, network device 205 may send a cancellation command to device 210 with EH capability. The cancellation command allows a querying device (e.g., network device 205) to re-enable a re-enabled tag (e.g., the device with EH capability). To cancel or re-enable device 210 with EH capability, network device 205 may follow a multi-step process. For example, network device 205 may issue two cancellation commands: a first cancellation command containing the 16 most significant bits (MSB) of the cancellation password of device 210 with EH capability and a 16-bit random number (indicated by device 210 with EH capability in response to a request from network device 205, similar to a write command as described herein), and a second cancellation command including the 16 least significant bits (LSB) of the cancellation password of device 210 with EH capability and a distinct 16-bit random number (indicated by device 210 with EH capability in response to a request from network device 205, similar to a write command as described herein). For example, the cancellation password may be predefined or known to network device 205. For example, just before issuing each cancel command, network device 205 may issue a Req_RN to obtain a new 16-bit random number, similar to the procedure used for write commands as described herein. The procedure for canceling or re-enabling device 210 with EH capability can be the same, except that when canceling device 210 with EH capability, the re-enabling bit in the second cancel command can be set to zero, and when re-enabling device 210 with EH capability, the re-enabling bit in the second cancel command can be set to a non-zero value. Table 10 shows an example of information included in the first cancel command, Table 11 shows an example of information included in the second cancel command, Table 12 shows an example of a response to the first cancel command, and Table 13 shows an example of a response to a successful second cancel command.

[0100] Table 10

[0101] Table 11

[0102] Table 12

[0103] Table 13

[0104] For AIoT devices, the network may have a need to modify information stored on the AIoT device in a manner similar to a write command or block write command, or similar to DCI format 1_X in NR. The network may also need to deactivate or activate the AIoT device. Permanent deactivation is similar to a cancel command, and temporary deactivation is similar to Discontinuous Receive (DRX) in NR.

[0105] Just like in RFID, write commands, block write commands, and erase commands can be used within a specified memory location. However, for AIoT devices, in some examples, the network may need to modify more than one function stored in non-contiguous memory locations at the AIoT device.

[0106] In RFID, a cancel command can be used to permanently disable or re-enable an RFID device. However, for AIoT devices, the network may need to temporarily disable them (e.g., as in NR's DRX). However, monitoring the Physical Downlink Control Channel (PDCCH) for DCIs that indicate modifications to multiple functions or temporary disabling of AIoT devices can be computationally intensive and power-intensive for AIoT devices.

[0107] Therefore, as described herein, to avoid latency associated with multiple write or erase commands, the querying device may send a modification command (e.g., a write command or an erase command) to an EH-capable device that modifies (e.g., writes or erases) two or more functions, wherein the functions are stored in non-contiguous memory locations within the EH-capable device. Additionally or alternatively, a new deactivation command may be introduced to deactivate the EH-capable device for a predetermined amount of time.

[0108] Figure 3 Examples of wireless communication systems 300 supporting scheduling and resource allocation for devices with energy harvesting capabilities, according to one or more aspects of this disclosure, are shown. Wireless communication system 300 may implement aspects of wireless communication system 100 or wireless communication system 200. For example, wireless communication system 300 includes network device 205-a, which may be an example of network device 205 as described herein. As another example, wireless communication system 300 includes device 210-a with EH capability, which may be an example of device 210 with EH capability as described herein.

[0109] Network device 205-a may send a modification command 320 (e.g., a command to write or erase two or more functions) to device 210-a with EH capability. In some examples, network device 205-a may send a control message 310 to device 210-a with EH capability before sending the modification command 320, and device 210-a with EH capability may send an acknowledgment 315 in response to the control message 310. Network device 205-a may send the modification command 320 based on the acknowledgment 315. For example, control message 310 may include a random number request, acknowledgment 315 may indicate a random number generated by device 210-a with EH capability, and modification command 320 may indicate a random number as a security check.

[0110] In some examples, network device 205-a can be reused for modification command 320, as shown in the reference. Figure 2 The write commands or block write commands described in Tables 4 through 7 are used, for example, if the EH-capable device 210-a supports only one function, or if the network device 205-a needs to modify a single function or set of functions located in a contiguous memory location of the EH-capable device 210-a. As another example, if the EH-capable device 210-a supports more than one function, the network device 205-a can use the commands described in the references... Figure 2 The block write command described in Tables 6 and 7 is used as modification command 320 to modify all functions in the same memory bank of the device 210-a with EH capability (e.g., setting the memory bank field as shown in Table 6 to "11").

[0111] In some examples, network device 205-a may modify two or more functions located in non-contiguous memory locations of EH-capable device 210-a in modification command 320. In some such examples, the user memory of EH-capable device 210-a may be partitioned based on the number of functions supported by EH-capable device 210-a, and the number of bits in modification command 320 indicating the functions to be modified may depend on the maximum number of functions that EH-capable device 210-a can support among all EH-capable devices in the same category. In some examples, modification command 320 may be similar to a block write command as described with reference to Table 6, except that the number of bits used for the bank field may be increased to indicate different functions or different combinations of functions of EH-capable device 210-a to be modified in modification command 320. In some examples, modification command 320 may resemble a block write command as described with reference to Table 6, except that new bit fields (e.g., after the bank field) may be added to indicate different functions or combinations of functions of the EH-capable device 210-a to be modified in modification command 320, for example, as shown in Table 14. In some examples, modification command 320 may resemble a block write command as described with reference to Table 6, except that multiple bit fields may be used to indicate the location of each function, for example, as shown in Table 15. For example, for functions of network device 205-a not modified via modification command 320, the word pointer and / or word count fields may be set to default values ​​(e.g., all "0"), and for functions of network device 205-a modified via modification command 320, the word pointer and / or word count fields may be set to different values.

[0112] Table 14

[0113] Table 15

[0114] Continued from Table 15

[0115] In some examples, the resources for EH-capable device 210-a to send a response to modification command 320 may be similar to those for a response to an RFID read command. For example, the resources for EH-capable device 210-a to send a response to modification command 320 may be predefined or preconfigured relative to the resources used for the corresponding modification command 320 (e.g., the time gap between the start position of modification command 320 and response 325, and the frequency offset relative to the modification command, may be predefined or preconfigured). For example, if EH-capable device 210-a successfully receives modification command 320, it may directly use a tag response to send response 325 indicating that it has successfully received modification command 320. If EH-capable device 210-a does not successfully receive modification command 320, it may not send response 325, thereby indicating to network device 205-a that it has not successfully received the modification command.

[0116] In some examples, control message 310 may indicate which functions will be modified by modification command 320. For example, control message 310 may be a DCI-like signal. Modification command 320 may be a separate data channel indicating the modification data. Control message 310 may indicate which resource is available for EH-capable device 210-a to monitor modification command 320 (e.g., control message 310 may schedule modification command 320). Control message 310 may indicate the resources used for acknowledgment 315 and / or response 325 (e.g., both time and frequency resources, or only time, in which case the frequency offset may be predefined or preconfigured). In some examples, the starting point of response 325 may be preconfigured with reference to modification command 320, and / or the starting point of acknowledgment 315 may be preconfigured with reference to control message 310 (e.g., the duration between response 325 and modification command 320 or between acknowledgment 315 and control message 310 may be based on the minimum time interval between the reception of control / data signals and the corresponding response). In some examples, the frequency offset between response 325 and modification command and / or between acknowledgment 315 and control message 310 can be preconfigured. In some examples, the mapping rules for resources used for responses (e.g., acknowledgment 315 and / or response 325) can be predefined with reference to control / data messages (e.g., control message 310 and modification command 320).

[0117] In some examples, control message 310 may include bits indicating whether control message 310 is for a read command or a write command (e.g., modification command 320). For example, a value "0" may indicate a read command, and a value "1" may indicate a write command. As another example, one scrambling sequence may be used to indicate a read command, and another scrambling sequence may indicate a write command. As yet another example, different monitoring timings may be configured for control messages used for read and write commands.

[0118] In some examples, if the EH-capable device 210-a successfully receives the modification command 320 after receiving the control message 310 indicating which functions will be modified, the EH-capable device 210-a may send a response 325 (e.g., an acknowledgment). For example, the response 325 may be a sequence-based acknowledgment or a one-bit acknowledgment. In some examples, if the EH-capable device 210-a does not successfully receive the modification command 320 after receiving the control message 310 indicating which functions will be modified, the EH-capable device 210-a may not send a response 325.

[0119] In some examples, the signaling or configuration may be based on either control message 310 or modification command 320 indicating which functions will be modified. For example, modification command 320 indicating which functions will be modified may be referred to as "Type 1," and control message 310 indicating which functions will be modified may be referred to as "Type 2." Network device 205-a and EH-capable device 210-a may negotiate or communicate whether Type 1 or Type 2 will be used. For example, handover signal 330 may be used to indicate a handover from Type 1 to Type 2, and vice versa. In some examples, handover signaling may be based on a handover request 335 from EH-capable device 210-a.

[0120] As another example, within Type 2, whether control message 310 indicates whether time and / or frequency resources for response 325 (e.g., referred to as "Type 2.1") or whether the resources for response 325 are negotiated or communicated between network device 205-a and device 210-a with EH capability based on predefined mapping rules (e.g., referred to as "Type 2.2") can be negotiated or communicated.

[0121] For example, in some examples, network device 205-a may start as type 2.2 (e.g., type 2.2 may be the default), and network device 205-a may send a handover signal 330 to indicate a switch to type 2.1. For example, if device 210-a with EH capability can decode control messages 310 with minimal repeated success, network device 205-a may send a handover signal 330 to indicate a switch to type 2.1. As another example, if the energy state of device 210-a with EH capability is better than a threshold (e.g., device 210-a with EH capability has more stored energy or an energy conversion efficiency higher than a threshold), network device 205-a may switch from type 2.2 to type 2.1. In some examples, device 210-a with EH capability may send a handover request 335, and a handover signal 330 indicating a switch to type 2.1 or indicating a switch to type 2.1 may respond to the handover request 335. In some examples, device 210-a with EH capability can send EH feedback to network device 205-a, and network device 205-a can determine whether to switch to type 2.1 based on the EH feedback.

[0122] In some examples, network device 205-a may start as type 2.1 (e.g., type 2.1 may be the default), and network device 205-a may send a handover signal 330 to indicate a switch to type 2.2. For example, if the number of control signals sent by device 210-a with EH capability without response exceeds a threshold, network device 205-a may trigger a switch to type 2.2. As another example, if the energy state of device 210-a with EH capability is worse than a threshold (e.g., the stored energy or energy conversion efficiency of device 210-a with EH capability is below a threshold), network device 205-a may switch from type 2.1 to type 2.2. In some examples, device 210-a with EH capability may send a handover request 335, and handover signal 330 may confirm the handover.

[0123] In some examples, network device 205-a can use as referenced. Figure 2 The cancellation command described in Tables 10 to 13 is used to deactivate device 210-a with EH capability. For example, the cancellation command can be used on network device 205-a to permanently deactivate device 210-a with EH capability. As another example, to deactivate device 210-a with EH capability for a period of time, network device 205-a may first issue a cancellation command, and then issue a reactivation command. The reactivation command following the cancellation command can be used for infrequent deactivation and activation.

[0124] In some examples, network device 205-a may send a new deactivation / activation command 340. The command code used for the deactivation / activation command 340 may be different (e.g., a reservation code in RFID) to distinguish it from a cancellation command. In some examples, if device 210-a with EH capability has sufficient power to maintain a clock at device 210-a with EH capability, the deactivation / activation command 340 may indicate the duration (e.g., how long) for device 210-a with EH capability to remain deactivated or activated. For example, Table 16 shows examples of information included in a deactivation / activation command 340 that includes a field indicating the duration of deactivation / activation.

[0125] Table 16

[0126] In some examples (e.g., if the device 210-a with EH capability does not have enough power to maintain the clock at the device 210-a with EH capability), the deactivation / activation command 340 may be split into a deactivation command (e.g., deactivation / activation command 340) and an activation command (e.g., a second deactivation / activation command 345). For example, the deactivation / activation command 340 may include an indication of duration, but the network device 205-a may also send a second deactivation / activation command 345 to activate the device 210-a with EH capability after deactivating the device 210-a with EH capability. As another example, the deactivation / activation command 340 may remove the bit field indicating the duration (e.g., how long) for which the device 210-a with EH capability should remain deactivated or activated, and may also send a second deactivation / activation command 345 to activate the device 210-a with EH capability after deactivating the device 210-a with EH capability. For example, Table 17 shows an example of information included in the deactivation / activation command 340, which removes the field indicating the duration of the deactivation / activation.

[0127] Table 17

[0128] In some examples, network device 205-a can use a device- or group-specified sequence to disable and activate devices with EH capability, similar to wake-up signals (WUS) and sleep signals. For example, disable / activate command 340 can instruct a device with EH capability to enter sleep mode, during which the device with EH capability can monitor a second disable / activate command 345 that can act as a WUS.

[0129] In some examples, network device 205-a may, for example, configure or pre-configure activation and / or deactivation durations for EH-capable devices via deactivation / activation command 340 (e.g., similar to DRX in NR). For example, if EH-capable device 210-a has sufficient power to maintain the clock at EH-capable device 210-a, the EH-capable device may be activated and deactivated according to the type or duration indicated in deactivation / activation command 340. For example, if the clock change of EH-capable device 210-a is N time slots between each synchronization duration, EH-capable device 210-a may be configured to enter the activation state N time slots in advance and enter the deactivation state N time slots out of advance.

[0130] Figure 4 An example of a signaling timing diagram 400 supporting scheduling and resource allocation for an energy harvesting device, according to one or more aspects of this disclosure, is shown. The signaling timing diagram 400 may implement aspects of wireless communication system 100, wireless communication system 200, or wireless communication system 300.

[0131] As described herein, in some examples, such as example signaling timing diagram 405, network device 205 may start with type 2.2 (e.g., type 2.2 may be the default), and network device 205 may send a switching signal 330 to indicate a switch to type 2.1. For example, network device 205 may send a type 2.2 control message 410 (e.g., as referenced). Figure 3 The described control message 410), and the EH-enabled device 210 can send a response 415 indicating that the control message 410 has been correctly received. The network device 205 can then send a type 2.2 control message 420 (e.g., as described in reference...). Figure 3 The described control message 310), and the EH-capable device 210 can send a response 425 indicating that the control message 420 has been correctly received. At time T1, after sending the response 425, the EH-capable device 210 can determine that the energy state of the EH-capable device 210 is better than a threshold. Therefore, the EH-capable device 210 can send a switching request 430 (e.g., as described in reference). Figure 3 The described handover request 335), and in response, network device 205 may send a handover indication 435 (e.g., as described in reference). Figure 3 The described switching signal 330). Device 210 with EH capability can send an acknowledgment 440 to the switching indication 435. Network device 205 can then send a type 2.1 control message 445 (e.g., as referenced). Figure 3 The control message described is 310.

[0132] As described herein, in some examples, such as example signaling timing diagram 450, network device 205 may start in type 2.1 (e.g., type 2.1 may be the default), and network device 205 may send a switching signal 330 to indicate a switch to type 2.2. For example, network device 205 may send a type 2.1 control message 455 (e.g., as referenced). Figure 3 The described control message 310), and the EH-enabled device 210 can send a response 460 indicating that the control message 455 has been correctly received. The network device 205 can then send a type 2.1 control message 465 (e.g., as described in reference...). Figure 3 The described control message 310), and the EH-capable device 210 can send a response 470 indicating that the control message 465 has been correctly received. At time T1, after sending the response 425, the EH-capable device 210 can determine that the energy state of the EH-capable device 210 is worse than a threshold. Therefore, the EH-capable device 210 can send a switching request 475 (e.g., as described in reference). Figure 3 The described handover request 335), and in response, network device 205 may send a handover indication 480 (e.g., as described in reference). Figure 3 The described switching signal 330). Device 210 with EH capability can send an acknowledgment 485 to the switching indication 480. Network device 205 can then send a type 2.2 control message 490 (e.g., as referenced). Figure 3 The control message described is 310.

[0133] Figure 5 An example of a timing diagram 500 supporting scheduling and resource allocation for a device with energy harvesting capabilities, according to one or more aspects of this disclosure, is shown. The timing diagram 500 may implement aspects of wireless communication system 100, wireless communication system 200, or wireless communication system 300.

[0134] In some examples, such as timing diagram 505, a first disable / activate command 510 disables the EH-capable device 210, and a second disable / activate command 515 activates the EH-capable device 210. Therefore, the EH-capable device 210 can be inactive for duration 520. For example, if the EH-capable device 210 does not have sufficient power to maintain its clock, a subsequent disable / activate command can be used.

[0135] In some examples, such as timing diagram 525, if the EH-capable device 210 has sufficient power to maintain the clock, the deactivation / activation command 530 can instruct a deactivation duration 540. After the deactivation duration 540, the EH-capable device 210 can re-enter the active state.

[0136] In some examples, such as timing diagram 550, network devices can be configured with periodic activation and deactivation patterns. For instance, device 210 with EH capability can be active during duration 560, and device 210 with EH capability can be deactivated during duration 565. Protection duration 555 separates the duration 560 during which device 210 with EH capability is active from the duration 565 during which device 210 with EH capability is deactivated, to accommodate potential clock variations between device 210 with EH capability and network device 205.

[0137] Figure 6 An example of a process flow 600 supporting scheduling and resource allocation for devices with EH capability, according to one or more aspects of this disclosure, is shown. Process flow 600 may include network device 205-b, which may be an example of network device 205 as described herein. Process flow 600 may include device 210-b with EH capability, which may be an example of device 210 with EH capability as described herein. In the following description of process flow 600, operations between network device 205-b and device 210-b with EH capability may be sent in a different order than the example order shown, or operations performed by network device 205-b and device 210-b with EH capability may be performed in a different order or at different times. Some operations may also be omitted from process flow 600, and other operations may be added to process flow 600.

[0138] At 605, device 210-b with EH capability can receive from network device 205-b a control message requesting the sending of a modification command to device 210-b with EH capability. The modification command may be associated with modifying two or more functions stored in non-contiguous memory locations of device 210-b with EH capability.

[0139] At 610, device 210-b with EH capability can send an acknowledgment to network device 205-b in response to a control message, which indicates permission to send modification commands for modifying two or more functions.

[0140] At 615, the device 210-b with EH capability can receive, from network device 205-b and based on acknowledgment, modification commands for two or more functions of the device 210-b with EH capability stored in a non-contiguous memory location of the device 210-b with EH capability.

[0141] In some examples, the control message at 605 may include instructions for modifying two or more functions.

[0142] In some examples, device 210-b with EH capability may receive a switching signal from network device 205-b indicating a switch from a first operating mode to a second operating mode, wherein the first operating mode is associated with a control message-based indication of a function to be modified and the second operating mode is associated with a modification command-based indication of a function to be modified, or wherein the first operating mode is associated with a modification command-based indication of a function to be modified and the second operating mode is associated with a control message-based indication of a function to be modified.

[0143] In some examples, the control message at 605 may include an indication of a communication resource for sending an acknowledgment, wherein the acknowledgment is sent via the communication resource.

[0144] In some examples, the control message at 605 may include an indication of a communication resource for sending a response to a modification command, and the EH-enabled device 210-b may send a response indicating successful reception of the modification command via the communication resource.

[0145] In some examples, the modification command at 615 can indicate two or more functions to be modified.

[0146] In some examples, the control message at 605 may include a random number request, the acknowledgment at 610 may include an indication of a random number based on the random number request, and the modification command at 615 may include a random number.

[0147] In some examples, device 210-b with EH capability can receive a deactivation command from network device 205-b, wherein the deactivation command includes an indication of the duration of the deactivation. Device 210-b with EH capability can enter a deactivated state based on the deactivation command and remain deactivated for the specified duration.

[0148] In some examples, device 210-b with EH capability can receive a deactivation command and an indication of one or more WUS monitoring events from network device 205-b. Device 210-b with EH capability can monitor WUS during one or more WUS monitoring events, and network device 205-b can send a WUS during one of the one or more WUS monitoring events to activate device 210-b with EH capability (e.g., triggering the device with EH capability to enter an active state from a deactivated state).

[0149] In some examples, device 210-b with EH capability can receive from network device 205-b a second control message configuring a mode for deactivating and activating device 210-b with EH capability, wherein the mode includes an activation mode and a deactivation mode for device 210-b with EH capability, and the mode cycles between the activation mode and the deactivation mode. Device 210-b with EH capability can cycle between the activation mode and the deactivation mode according to the mode for deactivating and activating device 210-b with EH capability.

[0150] Figure 7 A block diagram 700 is shown of a device 705 supporting scheduling and resource allocation for an energy-harvesting device according to one or more aspects of this disclosure. Device 705 may be an example of various aspects of UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, communication manager 720), may include at least one processor coupled to at least one memory to individually or jointly support or implement the described techniques. Device 705 may also include one or more processors, memory coupled to the one or more processors, and instructions stored in the memory that can be executed by the one or more processors to enable the one or more processors to perform the scheduling and resource allocation discussed herein for the energy-harvesting device features. Each of these components may communicate with each other (e.g., via one or more buses).

[0151] Receiver 710 may provide components 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 scheduling and resource allocation for devices with energy harvesting capabilities). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0152] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to scheduling and resource allocation for devices with energy harvesting capabilities). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0153] The communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be examples of components used to perform various aspects of scheduling and resource allocation for a device with energy harvesting capabilities as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0154] In some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0155] Additionally or alternatively, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) (e.g., referred to as processor executable code) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, to support components for performing the functions described in this disclosure).

[0156] In some examples, the communication manager 720 may be configured to use a receiver 710, a transmitter 715, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated in combination with the receiver 710, the transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0157] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for receiving a control message indicating a request to send a modification command to an EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device. The communication manager 720 may be capable of, configured to, or operable to support components for sending an acknowledgment in response to a control message, the acknowledgment indicating permission to send the modification command for modifying two or more functions. The communication manager 720 may be capable of, configured to, or operable to support components for receiving, based on an acknowledgment, a modification command for two or more functions stored in a non-contiguous memory location of an EH-capable device.

[0158] By including or configuring a communication manager 720 according to an example as described herein, device 705 (e.g., controlling receiver 710, transmitter 715, communication manager 720 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption and utilizing communication resources more efficiently.

[0159] Figure 8 A block diagram 800 of a device 805 supporting scheduling and resource allocation for an energy harvesting device according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of device 705 or UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, communication manager 820), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0160] Receiver 810 may provide components 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 scheduling and resource allocation for devices with energy harvesting capabilities). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0161] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 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 scheduling and resource allocation for devices with energy harvesting capabilities). In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0162] Device 805 or its various components may be examples of parts for performing various aspects of scheduling and resource allocation for devices with energy harvesting capabilities as described herein. For example, communication manager 820 may include modification command instruction manager 825, confirmation manager 830, modification command manager 835, or any combination thereof. Communication manager 820 may be examples of aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use receiver 810, transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0163] Communication manager 820 can support wireless communication according to the examples disclosed herein. Modification command instruction manager 825 is capable of, configured to, or operable to support components for receiving control messages indicating a request to send a modification command to an EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device. Acknowledgment manager 830 is capable of, configured to, or operable to support components for sending an acknowledgment in response to a control message, the acknowledgment indicating permission to send a modification command for modifying two or more functions. Modification command manager 835 is capable of, configured to, or operable to support components for receiving, based on an acknowledgment, modification commands for two or more functions stored in a non-contiguous memory location of the EH-capable device.

[0164] In some cases, the modification command instruction manager 825, the confirmation manager 830, and the modification command manager 835 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least part of a processor. The processor may be coupled to memory and execute instructions stored in memory that enable the processor to perform or facilitate the features of the modification command instruction manager 825, the confirmation manager 830, and the modification command manager 835 discussed herein. The transceiver processor may co-locate with and / or communicate with (e.g., instruct its operation) the transceiver of the device. The radio processor may co-locate with and / or communicate with (e.g., instruct its operation) the radio components of the device (e.g., NR radio components, LTE radio components, Wi-Fi radio components). The transmitter processor may co-locate with and / or communicate with (e.g., instruct its operation) the transmitter of the device. The receiver processor may co-locate with and / or communicate with (e.g., instruct its operation) the receiver of the device.

[0165] Figure 9 A block diagram 900 is shown of a communication manager 920 supporting scheduling and resource allocation for an energy-harvesting device according to one or more aspects of this disclosure. The communication manager 920 may be an example of a communication manager 720, a communication manager 820, or aspects thereof as described herein. The communication manager 920 or its various components may be examples of parts for performing various aspects of scheduling and resource allocation for an energy-harvesting device as described herein. For example, the communication manager 920 may include a modification command instruction manager 925, a confirmation manager 930, a modification command manager 935, a function instruction manager 940, a confirmation resource instruction manager 945, a random number request manager 950, a random number generator manager 955, a deactivation command manager 960, a WUS manager 965, a switching signal manager 970, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0166] Communication manager 920 can support wireless communication according to the examples disclosed herein. Modification command instruction manager 925 is capable of, configured to, or operable to support components for receiving control messages indicating a request to send a modification command to an EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device. Acknowledgment manager 930 is capable of, configured to, or operable to support components for sending an acknowledgment in response to a control message, the acknowledgment indicating permission to send the modification command for modifying two or more functions. Modification command manager 935 is capable of, configured to, or operable to support components for receiving, based on an acknowledgment, modification commands for two or more functions stored in a non-contiguous memory location of the EH-capable device.

[0167] In some examples, in order to support the reception of control messages, the function indication manager 940 is able to be configured or operated to support components for receiving control messages that include indications for two or more functions to be modified.

[0168] In some examples, the switching signal manager 970 is capable of, configured to, or operable to support components for receiving a switching signal indicating a switch from a first operating mode to a second operating mode, wherein the first operating mode is associated with a control message-based indication of a function to be modified, and the second operating mode is associated with a modification command-based indication of a function to be modified, or wherein the first operating mode is associated with a modification command-based indication of a function to be modified, and the second operating mode is associated with a control message-based indication of a function to be modified.

[0169] In some examples, in order to support receiving control messages, the acknowledgment resource indicator manager 945 is capable, configured, or operable to support components for receiving indications for communication resources used to send acknowledgments, wherein the acknowledgments are sent via the communication resources.

[0170] In some examples, in order to support receiving modification commands, the function instruction manager 940 is able to be configured or operated to support components for receiving modification commands that include instructions for two or more functions to be modified.

[0171] In some examples, the random number request manager 950 is capable of, configured to, or operable to support components for receiving random number requests via control messages. In some examples, the random number generator manager 955 is capable of, configured to, or operable to support components for sending an indication of a random number via acknowledgment and based on a random number request, wherein the modification command includes the random number.

[0172] In some examples, the deactivation command manager 960 is capable of, configured to, or able to operate to support components for receiving deactivation commands, wherein the deactivation command includes an indication of the duration of the deactivation.

[0173] In some examples, the deactivation command manager 960 is capable of, configured to, or operable to support components for receiving deactivation commands and instructions for one or more WUS monitoring events. In some examples, the WUS manager 965 is capable of, configured to, or operable to support components for monitoring WUS during one or more WUS monitoring events.

[0174] In some examples, the deactivation command manager 960 is capable of, configured to, or operable to support components for receiving a second control message configured for deactivation and activation of a device with EH capability, wherein the configuration includes an activation mode and a deactivation mode for the device with EH capability, and the configuration cycles between the activation mode and the deactivation mode.

[0175] In some cases, the Modify Command Indicator Manager 925, Confirmation Manager 930, Modify Command Manager 935, Function Indicator Manager 940, Confirmation Resource Indicator Manager 945, Random Number Request Manager 950, Random Number Generator Manager 955, Deactivate Command Manager 960, WUS Manager 965, and Switching Signal Manager 970 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least part of a processor. The processor may be coupled to memory and execute instructions stored in memory that enable the processor to perform or facilitate the features of the Modify Command Indicator Manager 925, Confirmation Manager 930, Modify Command Manager 935, Function Indicator Manager 940, Confirmation Resource Indicator Manager 945, Random Number Request Manager 950, Random Number Generator Manager 955, Deactivate Command Manager 960, WUS Manager 965, and Switching Signal Manager 970 discussed herein.

[0176] Figure 10A diagram is shown of a system 1000 including a device 1005 supporting scheduling and resource allocation for an energy harvesting device, according to one or more aspects of this disclosure. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or may include components thereof. Device 1005 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1020, an input / output (I / O) controller (e.g., I / O controller 1010), a transceiver 1015, one or more antennas 1025, at least one memory 1030, code 1035, and at least one processor 1040. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1045).

[0177] I / O controller 1010 manages the input and output signals of device 1005. I / O controller 1010 can also manage peripheral devices not integrated into device 1005. In some cases, I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1010 may be implemented as part of one or more processors, such as at least one processor 1040. In some cases, a user may interact with the device 1005 via the I / O controller 1010 or via hardware components controlled by the I / O controller 1010.

[0178] In some cases, device 1005 may include a single antenna. However, in other cases, device 1005 may have more than one antenna, which can concurrently transmit or receive multiple wireless transmissions. Transceiver 1015 may communicate bidirectionally via one or more antennas 1025 using a wired or wireless link as described herein. For example, transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. Transceiver 1015, or transceiver 1015 and one or more antennas 1025, may be an example of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination thereof or components thereof as described herein.

[0179] At least one memory 1030 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1030 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1035. Code 1035 may include instructions that, when executed by at least one processor 1040, cause device 1005 to perform the various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1035 may not be directly executable by at least one processor 1040, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1030 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0180] At least one processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1040. At least one processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting scheduling and resource allocation for devices with energy harvesting capabilities). For example, device 1005 or components of device 1005 may include at least one processor 1040 and at least one memory 1030 coupled to or coupled to at least one processor 1040, the at least one processor 1040 and the at least one memory 1030 being configured to perform the various functions described herein. In some examples, at least one processor 1040 may include multiple processors, and at least one memory 1030 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1040 may be a component of a processing system, which may refer to a machine (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1040) and memory circuitry (which may include at least one memory 1030)) or component that receives or receives input and processes the input 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, at least one processor 1040 or a processing system including at least one processor 1040 may be configured, capable of being configured, or operable to cause device 1005 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 1035 (e.g., processor-executable code) stored in at least one memory 1030 or otherwise executing the code.

[0181] The communication manager 1020 may support wireless communication according to examples disclosed herein. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for receiving control messages indicating a request to send a modification command to an EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device. The communication manager 1020 may be capable of, configured to, or operable to support components for sending an acknowledgment in response to a control message, the acknowledgment indicating permission to send the modification command for modifying two or more functions. The communication manager 1020 may be capable of, configured to, or operable to support components for receiving, based on an acknowledgment, a modification command for two or more functions stored in a non-contiguous memory location of an EH-capable device.

[0182] By including or configuring a communication manager 1020 according to the examples described herein, device 1005 can support technologies for reducing latency, lowering power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and enhancing processing power.

[0183] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 1015, one or more antennas 1025, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or executed by at least one processor 1040, at least one memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions that can be executed by at least one processor 1040 to cause device 1005 to perform various aspects of scheduling and resource allocation for a device with energy harvesting capabilities as described herein, or at least one processor 1040 and at least one memory 1030 may be otherwise configured to perform or support such operations individually or jointly.

[0184] Figure 11A block diagram 1100 of a device 1105 supporting scheduling and resource allocation for an energy-harvesting device according to one or more aspects of this disclosure is shown. In some examples, device 1105 may be an example of aspects of network entity 105 as described herein. In some examples, device 1105 may be an example of aspects of UE 115 as described herein. For example, device 1105 may be an example of network device 205 as described herein. Device 1105 may include receiver 1110, transmitter 1115, and communication manager 1120. Device 1105 or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, communication manager 1120) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Device 1105 may also include one or more processors, memory coupled to one or more processors, and instructions stored in the memory that can be executed by one or more processors to enable one or more processors to perform the scheduling and resource allocation discussed herein for the features of an energy-harvesting device. Each of these components can communicate with each other (e.g., via one or more buses).

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

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

[0187] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be examples of components used to perform various aspects of scheduling and resource allocation for a device with energy harvesting capabilities as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0188] In some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0189] Additionally or alternatively, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) (e.g., referred to as processor executable code) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0190] In some examples, the communication manager 1120 may be configured to use a receiver 1110, a transmitter 1115, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or integrate with the receiver 1110, the transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0191] Communication manager 1120 may support wireless communication according to examples disclosed herein. For example, communication manager 1120 may be capable of, configured to, or operable to support components for sending a control message to an EH-capable device instructing a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device. Communication manager 1120 may be capable of, configured to, or operable to support components for receiving an acknowledgment from the EH-capable device in response to a control message, the acknowledgment indicating permission to send the modification command for modifying two or more functions. Communication manager 1120 may be capable of, configured to, or operable to support components for sending, to an EH-capable device and, based on an acknowledgment, a modification command for two or more functions stored in a non-contiguous memory location of the EH-capable device.

[0192] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 (e.g., controlling receiver 1110, transmitter 1115, communication manager 1120 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption and utilizing communication resources more efficiently.

[0193] Figure 12A block diagram 1200 is shown of a device 1205 supporting scheduling and resource allocation for an energy harvesting device, according to one or more aspects of this disclosure. Device 1205 may be an example of aspects of device 1105 or network entity 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. Device 1205 or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, communication manager 1220) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0196] Device 1205 or its various components may be examples of parts for performing various aspects of scheduling and resource allocation for devices with energy harvesting capabilities as described herein. For example, communication manager 1220 may include modification command instruction manager 1225, confirmation manager 1230, modification command manager 1235, or any combination thereof. Communication manager 1220 may be examples of aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use receiver 1210, transmitter 1215, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0197] Communication manager 1220 can support wireless communication according to the examples disclosed herein. Modification command instruction manager 1225 is capable of, configured to, or operable to support components for sending a control message to an EH-capable device instructing a request to send a modification command to an EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device. Acknowledgment manager 1230 is capable of, configured to, or operable to support components for receiving an acknowledgment from an EH-capable device in response to a control message, the acknowledgment indicating permission to send a modification command for modifying two or more functions. Modification command manager 1235 is capable of, configured to, or operable to support components for sending, to an EH-capable device and based on an acknowledgment, modification commands for two or more functions stored in a non-contiguous memory location of the EH-capable device.

[0198] In some cases, the modification command instruction manager 1225, the confirmation manager 1230, and the modification command manager 1235 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least part of a processor. The processor may be coupled to memory and execute instructions stored in memory that enable the processor to perform or facilitate the features of the modification command instruction manager 1225, the confirmation manager 1230, and the modification command manager 1235 discussed herein. The transceiver processor may co-locate with and / or communicate with (e.g., instruct its operation) the transceiver of the device. The radio processor may co-locate with and / or communicate with (e.g., instruct its operation) the radio components of the device (e.g., NR radio components, LTE radio components, Wi-Fi radio components). The transmitter processor may co-locate with and / or communicate with (e.g., instruct its operation) the transmitter of the device. The receiver processor may co-locate with and / or communicate with (e.g., instruct its operation) the receiver of the device.

[0199] Figure 13 A block diagram 1300 is shown of a communication manager 1320 supporting scheduling and resource allocation for an energy-harvesting device according to one or more aspects of this disclosure. The communication manager 1320 may be an example of a communication manager 1120, a communication manager 1220, or aspects thereof as described herein. The communication manager 1320 or its various components may be examples of parts for performing various aspects of scheduling and resource allocation for an energy-harvesting device as described herein. For example, the communication manager 1320 may include a modification command instruction manager 1325, a confirmation manager 1330, a modification command manager 1335, a function instruction manager 1340, a confirmation resource instruction manager 1345, a random number request manager 1350, a random number receiving manager 1355, an EH-capable device deactivation manager 1360, a WUS manager 1365, a switching signal manager 1370, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). Communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0200] Communication manager 1320 can support wireless communication according to the examples disclosed herein. Modification command instruction manager 1325 is capable of, configured to, or operable to support components for sending a control message to an EH-capable device instructing a request to send a modification command to an EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device. Acknowledgment manager 1330 is capable of, configured to, or operable to support components for receiving an acknowledgment from an EH-capable device in response to a control message, the acknowledgment indicating permission to send a modification command for modifying two or more functions. Modification command manager 1335 is capable of, configured to, or operable to support components for sending, to an EH-capable device and based on an acknowledgment, modification commands for two or more functions stored in a non-contiguous memory location of the EH-capable device.

[0201] In some examples, to support the sending of control messages, the function indication manager 1340 is capable of, configured to, or operable to support components for sending control messages that include indications of two or more functions to be modified.

[0202] In some examples, the switching signal manager 1370 is capable of, configured to, or operable to support components for sending a switching signal to an EH-enabled device instructing a switch to a second operating mode, wherein the first operating mode is associated with a control message-based instruction for a function to be modified, and the second operating mode is associated with a modification command-based instruction for a function to be modified, or wherein the first operating mode is associated with a modification command-based instruction for a function to be modified, and the second operating mode is associated with a control message-based instruction for a function to be modified.

[0203] In some examples, in order to support the sending of control messages, the acknowledgment resource indicator manager 1345 is capable, configured, or operable to support components for sending indications to communication resources for sending acknowledgments, wherein the acknowledgments are sent via the communication resources.

[0204] In some examples, to support the sending of modification commands, the function instruction manager 1340 is able to be configured or operated to support components for sending instructions for two or more functions to be modified.

[0205] In some examples, the random number request manager 1350 is capable of, configured to, or operable to support components for sending random number requests via control messages. In some examples, the random number receiving manager 1355 is capable of, configured to, or operable to support components for receiving an indication of a random number via acknowledgment and based on a random number request, wherein the modification command includes the random number.

[0206] In some examples, the device deactivation manager 1360 with EH capability is capable of, configured to, or able to operate to support components for sending deactivation commands to devices with EH capability, wherein the deactivation command includes an indication of the duration of the deactivation.

[0207] In some examples, the EH-capable device deactivation manager 1360 is capable of, configured to, or operable to support components for sending deactivation commands to EH-capable devices and indicating one or more WUS monitoring events. In some examples, the WUS manager 1365 is capable of, configured to, or operable to support components for sending WUS during one or more WUS monitoring events.

[0208] In some examples, the device deactivation manager 1360 with EH capability is capable of, configured to, or operable to support components for sending a second control message to the device with EH capability, configuring a type of deactivation and activation for the device with EH capability, wherein the type includes an activation mode and a deactivation mode for the device with EH capability, the type cycling between the activation mode and the deactivation mode.

[0209] In some cases, the Modification Command Indication Manager 1325, Confirmation Manager 1330, Modification Command Manager 1335, Function Indication Manager 1340, Confirmation Resource Indication Manager 1345, Random Number Request Manager 1350, Random Number Receiver Manager 1355, EH-capable Device Deactivation Manager 1360, WUS Manager 1365, and Switching Signal Manager 1370 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least part of a processor. The processor may be coupled to memory and execute instructions stored in memory that enable the processor to perform or facilitate the features of the Modification Command Indication Manager 1325, Confirmation Manager 1330, Modification Command Manager 1335, Function Indication Manager 1340, Confirmation Resource Indication Manager 1345, Random Number Request Manager 1350, Random Number Receiver Manager 1355, EH-capable Device Deactivation Manager 1360, WUS Manager 1365, and Switching Signal Manager 1370 discussed herein.

[0210] Figure 14A diagram of a system 1400 including device 1405 supporting scheduling and resource allocation for devices with energy harvesting capabilities, according to one or more aspects of this disclosure, is shown. Device 1405 may be an example of device 1105, device 1205, or network entity 105 as described herein, or a component including such devices or network entities. Device 1405 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1405 may include components supporting output and enabling communication, such as a communication manager 1420, a transceiver 1410, one or more antennas 1415, at least one memory 1425, code 1430, and at least one processor 1435. These components may communicate electronically or otherwise (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1440).

[0211] Transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1410 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1410 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1405 may include one or more antennas 1415 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1410 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1415, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1410 may include one or more processors or one or more memory components, or be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1410, or transceiver 1410 and one or more antennas 1415, or transceiver 1410 and one or more antennas 1415, and one or more processors or one or more memory components (e.g., at least one processor 1435, at least one memory 1425, or both), may be included in a chip or chip assembly mounted in device 1405. In some examples, transceiver 1410 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0212] At least one memory 1425 may include RAM, ROM, or any combination thereof. At least one memory 1425 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1430. Code 1430 may include instructions that, when executed by one or more processors in at least one processor 1435, cause device 1405 to perform the various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by a processor in at least one processor 1435, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1425 may include a BIOS, etc., which controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0213] At least one processor 1435 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1435. At least one processor 1435 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1425) to cause device 1405 to perform various functions (e.g., functions or tasks supporting scheduling and resource allocation for devices with energy harvesting capabilities). For example, device 1405 or components of device 1405 may include at least one processor 1435 and at least one memory 1425 coupled to one or more processors in at least one processor 1435, wherein at least one processor 1435 and at least one memory 1425 are configured to perform the various functions described herein. At least one processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1430) host functions for performing the functions of device 1405. At least one processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within one or more memories of at least one memory 1425). In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1435 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1435) and memory circuitry (which may include at least one memory 1425)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1435 or a processing system including at least one processor 1435 may be configured, configured to be configured to, or be operable to cause the device 1405 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1425 or otherwise executing code.

[0214] In some examples, bus 1440 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 1440 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1405, or communication performed between different components of device 1405 that are co-addressable or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, at least one memory 1425, code 1430 and at least one processor 1435 may be located in one component of different components or partitioned between different components).

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

[0216] Communication manager 1420 may support wireless communication according to examples disclosed herein. For example, communication manager 1420 may be capable of, configured to, or operable to support components for sending a control message to an EH-capable device instructing a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device. Communication manager 1420 may be capable of, configured to, or operable to support components for receiving an acknowledgment from the EH-capable device in response to a control message, the acknowledgment indicating permission to send the modification command for modifying two or more functions. Communication manager 1420 may be capable of, configured to, or operable to support components for sending, to an EH-capable device and, based on an acknowledgment, a modification command for two or more functions stored in a non-contiguous memory location of the EH-capable device.

[0217] By including or configuring a communication manager 1420 according to the examples described herein, device 1405 can support technologies for reducing latency, lowering power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and enhancing processing power.

[0218] In some examples, the communication manager 1420 may be configured to use or otherwise coordinate with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, acquire, monitor, output, transmit). Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, one or more processors in at least one processor 1435, one or more memories in at least one memory 1425, code 1430, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1435, at least one memory 1425, code 1430, or any combination thereof). For example, code 1430 may include instructions that can be executed by one or more processors of at least one processor 1435 to cause device 1405 to perform various aspects of scheduling and resource allocation for a device with energy harvesting capabilities as described herein, or at least one processor 1435 and at least one memory 1425 may be otherwise configured to perform or support such operations individually or jointly.

[0219] Figure 15 A flowchart illustrating a method 1500 for scheduling and resource allocation for an energy-harvesting device, according to one or more aspects of this disclosure, is shown. Operation of method 1500 may be implemented by a UE or its components as described herein. For example, operation of method 1500 may be performed by, as referenced... Figures 1 to 10 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0220] At 1505, the method may include: receiving a control message indicating a request to send a modification command to an EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device. The operation of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 9 The described modification command is executed by Manager 925.

[0221] At 1510, the method may include: sending an acknowledgment in response to a control message, the acknowledgment indicating permission to send a modification command for modifying two or more functions. The operation of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be derived from references... Figure 9 The described confirmation manager 930 is used to execute this.

[0222] At 1515, the method may include: receiving, based on an acknowledgment, a modification command for two or more functions of an EH-capable device stored in a non-contiguous memory location of the EH-capable device. The operation of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to [reference needed]. Figure 9 The described modification is executed using Command Manager 935.

[0223] Figure 16 A flowchart illustrating a method 1600 for scheduling and resource allocation for an energy harvesting device, according to one or more aspects of this disclosure, is shown. Operation of method 1600 may be implemented by a network entity or its components as described herein. For example, operation of method 1600 may be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0224] At 1605, the method may include: sending a control message to an EH-capable device instructing a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device. The operation of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference]. Figure 13 The described modification command is executed by Manager 1325.

[0225] At 1610, the method may include: receiving an acknowledgment from an EH-capable device in response to a control message, the acknowledgment indicating permission to send a modification command for modifying two or more functions. Operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1610 may be provided by reference to... Figure 13 The described confirmation manager 1330 is used to execute this.

[0226] At 1615, the method may include: sending, based on an acknowledgment, a modification command for two or more functions stored in a non-contiguous memory location of the EH-capable device to the EH-capable device. The operation of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be provided by reference to [reference needed]. Figure 13 The described modification is used to execute command manager 1335.

[0227] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at an EH-capable device, the method comprising: receiving a control message indicating a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; sending an acknowledgment in response to the control message, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; and receiving the modification command for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device, at least in part based on the acknowledgment.

[0228] Aspect 2: According to the method of aspect 1, receiving the control message includes: receiving the control message including an indication of the two or more functions to be modified.

[0229] Aspect 3: According to the method of aspect 2, the method further includes: receiving a switching signal indicating a switch from a first operating mode to a second operating mode, wherein the first operating mode is associated with an instruction based on a control message for a function to be modified, and the second operating mode is associated with an instruction based on a modification command for the function to be modified, or wherein the first operating mode is associated with the instruction based on the modification command for the function to be modified, and the second operating mode is associated with the instruction based on a control message for the function to be modified.

[0230] Aspect 4: The method according to any one of Aspects 1 to 3, wherein receiving the control message includes: receiving an indication for a communication resource for sending the acknowledgment, wherein the acknowledgment is sent via the communication resource.

[0231] Aspect 5: The method according to any one of Aspects 2 to 4, wherein receiving the modification command comprises: receiving the modification command including an indication of the two or more functions to be modified.

[0232] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: receiving a random number request via the control message; and sending an indication of a random number via the acknowledgment and based on the random number request, wherein the modification command includes the random number.

[0233] Aspect 7: The method according to any one of aspects 1 to 6, the method further comprising: receiving a deactivation command, wherein the deactivation command includes an indication of the duration of the deactivation.

[0234] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: receiving a deactivation command and an indication of one or more WUS monitoring times; and monitoring WUS during the one or more WUS monitoring times.

[0235] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: receiving a second control message configuring a mode for deactivation and activation of the device having EH capability, wherein the mode includes an activation mode and a deactivation mode for the device having EH capability, the mode cycling between the activation mode and the deactivation mode.

[0236] Aspect 10: A method for performing wireless communication at a wireless communication device, the method comprising: sending to a device having EH capability a control message instructing a request to send a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; receiving an acknowledgment from the EH-capable device in response to the control message, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; and sending to the EH-capable device, and at least in part based on the acknowledgment, the modification command for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device.

[0237] Aspect 11: According to the method of aspect 10, sending the control message includes: sending the control message including an indication of the two or more functions to be modified.

[0238] Aspect 12: The method according to aspect 11, the method further comprising: sending a switching signal to the EH-capable device indicating a switch from a first operating mode to a second operating mode, wherein the first operating mode is associated with an indication based on a control message for a function to be modified, and the second operating mode is associated with an indication based on a modification command for the function to be modified, or wherein the first operating mode is associated with the indication based on the modification command for the function to be modified, and the second operating mode is associated with the indication based on a control message for the function to be modified.

[0239] Aspect 13: The method according to any one of Aspects 10 to 12, wherein sending the control message comprises: sending an indication for a communication resource for sending the acknowledgment, wherein the acknowledgment is sent via the communication resource.

[0240] Aspect 14: The method according to any one of Aspects 11 to 13, wherein sending the modification command comprises: sending the modification command including an indication of the two or more functions to be modified.

[0241] Aspect 15: The method according to any one of Aspects 10 to 14, the method further comprising: sending a random number request via the control message; and receiving an indication of a random number via the acknowledgment and based on the random number request, wherein the modification command includes the random number.

[0242] Aspect 16: The method according to any one of Aspects 10 to 15, the method further comprising: sending a deactivation command to the device having EH capability, wherein the deactivation command includes an indication of the duration of the deactivation.

[0243] Aspect 17: The method according to any one of Aspects 10 to 16, the method further comprising: sending a deactivation command and an indication of one or more WUS monitoring times to the device having EH capability; and sending WUS during the one or more WUS monitoring times.

[0244] Aspect 18: The method according to any one of Aspects 10 to 17, the method further comprising: sending a second control message to the device having EH capability, configuring a mode for deactivation and activation of the device having EH capability, wherein the mode includes an activation mode and a deactivation mode for the device having EH capability, the mode cycling between the activation mode and the deactivation mode.

[0245] Aspect 19: An EH-capable device for wireless communication, the EH-capable device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to enable the EH-capable device to perform a method according to any one of Aspects 1 to 9.

[0246] Aspect 20: An EH-capable device for wireless communication, the EH-capable device comprising at least one component for performing the method according to any one of aspects 1 to 9.

[0247] Aspect 21: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 9.

[0248] Aspect 22: A wireless communication device for wireless communication, the wireless communication device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the wireless communication device to perform a method according to any one of aspects 10 to 18.

[0249] Aspect 23: A wireless communication device for wireless communication, the wireless communication device comprising at least one component for performing the method according to any one of aspects 10 to 18.

[0250] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 10 to 18.

[0251] It should be noted that the methods described herein describe possible specific implementations. Operations and steps may be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods may be combined.

[0252] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0254] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a 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 combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

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

[0256] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible 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, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0257] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0258] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing 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 “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0259] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0260] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0261] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

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

Claims

1. A device with energy harvesting (EH) capability, the device with energy harvesting (EH) capability comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors coupled to one or more memories, wherein the one or more processors are capable of operating individually or jointly to execute the code to enable the EH-enabled device: Receive a control message that instructs the sending of a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; In response to the control message, an acknowledgment is sent, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; as well as The modification command for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device is received at least in part based on the confirmation.

2. The EH-capable device according to claim 1, wherein the one or more processors are individually or jointly configured to cause the EH-capable device to receive the control message by individually or jointly configuring the EH-capable device to perform the following operations: Receive the control message which includes instructions for the two or more functions to be modified.

3. The device with EH capability according to claim 2, wherein the one or more processors are further configured individually or collectively to enable the device with EH capability to: The system receives a switching signal indicating a switch from a first operating mode to a second operating mode, wherein the first operating mode is associated with a control message-based instruction for a function to be modified, and the second operating mode is associated with a modification command-based instruction for the function to be modified; or wherein the first operating mode is associated with the modification command-based instruction for the function to be modified, and the second operating mode is associated with the control message-based instruction for the function to be modified.

4. The EH-capable device of claim 1, wherein the one or more processors are individually or jointly configured to cause the EH-capable device to receive the control message by individually or jointly configuring the EH-capable device to perform the following operations: Receive an instruction for a communication resource for sending the acknowledgment, wherein the acknowledgment is sent via the communication resource.

5. The EH-capable device of claim 1, wherein the one or more processors are individually or jointly configured to cause the EH-capable device to receive the modification command by individually or jointly causing the EH-capable device to perform the following operations: Receive the modification command, which includes instructions on the two or more functions to be modified.

6. The device with EH capability according to claim 1, wherein the one or more processors are individually or collectively further configured to enable the device with EH capability to: Receive random number requests via the control message; and The instruction for a random number is sent via the confirmation and based on the random number request, wherein the modification command includes the random number.

7. The device with EH capability according to claim 1, wherein the one or more processors are further configured individually or collectively to enable the device with EH capability to: Receive a deactivation command, wherein the deactivation command includes an indication of the duration of the deactivation.

8. The device with EH capability according to claim 1, wherein the one or more processors are individually or collectively further configured to enable the device with EH capability: Receive deactivation commands and instructions on when to monitor one or more wake-up signals; and The wake-up signal is monitored during one or more wake-up signal monitoring periods.

9. The device with EH capability according to claim 1, wherein the one or more processors are further configured individually or collectively to enable the device with EH capability to: A second control message is received configuring a mode for deactivating and activating the device with EH capability, wherein the mode includes an activation mode and a deactivation mode of the device with EH capability, and the mode cycles between the activation mode and the deactivation mode.

10. A wireless communication device, the wireless communication device comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors coupled to one or more memories, wherein the one or more processors are capable of operating individually or jointly to execute the code to enable the wireless communication device: A control message is sent to a device with energy harvesting (EH) capability, requesting a modification command to be sent to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; In response to the control message, an acknowledgment is received from the EH-capable device, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; as well as The modification command for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device is sent to the EH-capable device and at least in part based on the confirmation.

11. The wireless communication device of claim 10, wherein the one or more processors are individually or jointly configured to cause the wireless communication device to transmit the control message by being individually or jointly configured to cause the wireless communication device to perform the following operations: Send the control message which includes instructions for the two or more functions to be modified.

12. The wireless communication device of claim 11, wherein the one or more processors are further configured individually or collectively to cause the wireless communication device to: Send a switching signal to the EH-capable device, indicating a switch from a first operating mode to a second operating mode, wherein the first operating mode is associated with a control message-based indication of a function to be modified, and the second operating mode is associated with a modification command-based indication of the function to be modified, or wherein the first operating mode is associated with the modification command-based indication of the function to be modified, and the second operating mode is associated with the control message-based indication of the function to be modified.

13. The wireless communication device of claim 10, wherein the one or more processors are individually or jointly configured to cause the wireless communication device to transmit the control message by being individually or jointly configured to cause the wireless communication device to perform the following operations: Send an instruction for a communication resource used to send the acknowledgment, wherein the acknowledgment is sent via the communication resource.

14. The wireless communication device of claim 10, wherein the one or more processors are individually or jointly configured to cause the wireless communication device to send the modification command by individually or jointly configuring the wireless communication device to perform the following operations: Send the modification command, which includes instructions on the two or more functions to be modified.

15. The wireless communication device of claim 10, wherein the one or more processors are further configured individually or collectively to cause the wireless communication device to: Send a random number request via the control message; and The confirmation is received in connection with the random number request, and the instruction for a random number is received, wherein the modification command includes the random number.

16. The wireless communication device of claim 10, wherein the one or more processors are further configured individually or collectively to cause the wireless communication device to: Send a deactivation command to the device with EH capability, wherein the deactivation command includes an indication of the duration of the deactivation.

17. The wireless communication device of claim 10, wherein the one or more processors are further configured individually or collectively to cause the wireless communication device to: Send a deactivation command and an indication of the timing for monitoring one or more wake-up signals to the EH-enabled device; and A wake-up signal is sent during one or more wake-up signal monitoring periods.

18. The wireless communication device of claim 10, wherein the one or more processors are further configured individually or collectively to cause the wireless communication device to: A second control message is sent to the device with EH capability to configure a mode for deactivating and activating the device with EH capability, wherein the mode includes an activation mode and a deactivation mode of the device with EH capability, and the mode cycles between the activation mode and the deactivation mode.

19. A method for wireless communication at a device with energy harvesting (EH) capability, the method comprising: Receive a control message that instructs the sending of a modification command to the EH-capable device, the modification command being associated with modifying two or more functions stored in a non-contiguous memory location of the EH-capable device; In response to the control message, an acknowledgment is sent, the acknowledgment indicating permission to send the modification command for modifying the two or more functions; as well as The modification command for the two or more functions of the EH-capable device stored in the non-contiguous memory location of the EH-capable device is received at least in part based on the confirmation.

20. The method of claim 19, wherein receiving the control message comprises: Receive the control message which includes instructions for the two or more functions to be modified.

Images