Techniques for prioritizing and processing conflicting read and write commands for passive devices

Abstract

Methods, systems, and devices for wireless communication are described. A passive device (e.g., a radio frequency identifier (RFID) tag) can be configured to receive a first query associated with a first operation to be performed at the passive device and a second query associated with a second operation to be performed at the passive device, wherein the first operation and the second operation are associated with a first priority level and a second priority level, respectively. The first operation and the second operation can include a write operation, a read operation, or both. The passive device can send a message indicating a status of the first operation, the second operation, or both to the first query device, the second query device, or both, and can perform one of the first operation or the second operation according to the first priority level and the second priority level and based on sending the message.

Description

Technical Field

[0001] The following relates to wireless communications, including techniques for prioritizing and handling conflicting read and write commands to passive devices. Background Art

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

[0003] Some wireless communication systems may include passive devices such as radio frequency identifier (RFID) tags or passive Internet of Things (IoT) devices to perform certain operations, such as location tracking and identification. To communicate with a passive device, an inquiry device (e.g., UE, network entity) sends a signal or inquiry to the passive device to instruct the passive device to perform a read or write operation. Passive devices such as RFID tags may include relatively low complexity devices with limited resources and processing power, and therefore may perform a limited number of read operations or write operations at a time. Summary of the invention

[0004] The described technology relates to support for the technology of prioritizing and processing the conflicting read commands and write commands for passive devices. In general, the aspects of the present disclosure support the technology of signaling and configuration for solving the relative priority of read operations and write operations at passive devices. Specifically, the aspects of the present disclosure relate to the rules and conditions for determining the relative priority between the read operation and the write operation to be performed at the passive device, and the signaling of the state or relative priority of the read / write operation from the passive device for indicating the conflicting. For example, the passive device can receive multiple queries for performing a separate read operation or write operation, wherein the separate read operation or write operation is associated with different priorities. The priority can be explicitly signaled via the query, determined based on the type of operation to be performed (e.g., the write operation can take precedence over the read operation), determined based on the identifier of the query device sending the query, or any combination of these operations. In this example, the passive device can send a message to the query device sending the query to indicate the state of the scheduled read / write operation (e.g., indicating which operation will be performed), and one of the operations can be performed according to the relative priority.

[0005] A method for wireless communication at a passive device is described. The method may include: receiving a first query associated with a first operation to be performed at the passive device from a first querying device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both; receiving a second query associated with a second operation to be performed at the passive device from the first querying device or the second querying device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both; sending a message indicating a status of the first operation, the second operation, or both to the first querying device, the second querying device, or both; and performing one of the first operation or the second operation according to the first priority level and the second priority level and based on sending the message.

[0006] An apparatus for wireless communication at a passive device is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive a first query associated with a first operation to be performed at the passive device from a first querying device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both; receive a second query associated with a second operation to be performed at the passive device from the first querying device or the second querying device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both; send a message indicating a status of the first operation, the second operation, or both to the first querying device, the second querying device, or both; and perform one of the first operation or the second operation according to the first priority level and the second priority level and based on sending the message.

[0007] Another apparatus for wireless communication at a passive device is described. The apparatus may include: a component for receiving a first query associated with a first operation to be performed at the passive device from a first querying device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both; a component for receiving a second query associated with a second operation to be performed at the passive device from the first querying device or the second querying device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both; a component for sending a message to the first querying device, the second querying device, or both indicating a status of the first operation, the second operation, or both; and a component for performing one of the first operation or the second operation according to the first priority level and the second priority level and based on sending the message.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a passive device is described. The code may include instructions executable by a processor to: receive a first query associated with a first operation to be performed at the passive device from a first querying device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both; receive a second query associated with a second operation to be performed at the passive device from the first querying device or the second querying device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both; send a message indicating a status of the first operation, the second operation, or both to the first querying device, the second querying device, or both; and perform one of the first operation or the second operation according to the first priority level and the second priority level and based on sending the message.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a first priority level via a first query and receiving a second priority level via a second query, wherein sending the message may be based on the first priority level, the second priority level, or both.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first priority level may be based on a first operation including a first write operation, and a second priority level may be based on a second operation including a second read operation.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for prioritizing a first operation over a second read operation based on a first priority level being greater than a second priority level, wherein sending the message may be performed based on a priority ranking, and wherein performing one of the first operation or the second operation includes performing the first operation based on the priority ranking.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: receiving control signaling indicating a priority configuration that can be used to determine a priority level associated with an operation to be performed at the passive device from the first querying device, the second querying device, or the additional wireless device, and determining a first priority level, a second priority level, or both based on the priority configuration, wherein sending the message, performing one of the first operation or the second operation, or both, can be performed based on determining the first priority level, the second priority level, or both.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a priority configuration includes one or more rules, one or more conditions, or both for determining a priority level associated with an operation to be performed at a passive device, and determining a first priority level, a second priority level, or both can be performed based on one or more rules, one or more conditions, or both.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first priority level may be based on a first operation type associated with the first operation, and the second priority level may be based on a second operation type associated with the second operation.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a second query may be received from a second querying device, the first priority level may be based on a first identifier associated with the first querying device, and the second priority level may be based on a second identifier associated with the second querying device.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a message to at least a second querying device based on the first priority level being greater than the second priority level, wherein the message includes an indication that the passive device may be busy performing the first operation.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a message to at least a first querying device based on the first priority level being less than a second priority level, wherein the message includes an indication that the passive device may have received a second query for a second operation having a higher priority than the first operation.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending, via a message, an indication of a first priority level, a second priority level, a first operation type associated with a first operation, a second operation type associated with a second operation, a first identifier associated with a first querying device, a second identifier associated with a second querying device, or any combination thereof.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a second query may be received from a first querying device, and the methods, apparatus, and non-transitory computer-readable media may include additional operations, features, components, or instructions for receiving instructions to stop the first operation and perform a second operation via the second query, wherein the passive device performs the second operation based on the instructions.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a set of multiple messages according to a periodicity, the set of multiple messages associated with a queue of operations to be performed by the passive device, the set of multiple messages including messages indicating a status of a first operation, a second operation, or both.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a set of multiple messages according to a periodicity, wherein sending the set of multiple messages may be based on receiving the set of multiple signals.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message includes an indication that the passive device may be busy performing a first operation, and the methods, apparatus, and non-transitory computer-readable media may include additional operations, features, components, or instructions for performing the following operations: receiving a request for an identifier associated with the first querying device from a second querying device and in response to the message, and sending a second message to the second querying device based on receiving the request, the second message indicating the identifier associated with the first querying device.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing one of a first operation or a second operation includes performing the first operation at a first time, and the methods, apparatus, and non-transitory computer-readable media may include additional operations, features, components, or instructions for performing the second operation at a second time after the first time based on the second priority level being less than the first priority level.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing one of the first write operation or the second write operation may include operations, features, components, or instructions for adjusting one or more operating parameters at the passive device.

[0025] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, performing one of the first read operation or the second read operation may include operations, features, components, or instructions for sending a data message to the first querying device, the second querying device, or both.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the passive device includes a radio frequency identifier tag, a passive component of a wireless device, or both, and the first querying device, the second querying device, or both include a UE, a network entity, or both.

[0027] A method for wireless communication at a querying device is described. The method may include sending a first query to a passive device associated with a first operation to be performed at the passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both; and receiving a message from the passive device based on the first query indicating a status of the first operation, a second operation associated with a second priority level, or both, wherein the status is based on the first priority level, the second priority level, or both, and wherein the second operation includes a second write operation, a second read operation, or both.

[0028] An apparatus for wireless communication at a querying device is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: send a first query associated with a first operation to be performed at the passive device to a passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both; and receive a message from the passive device based on the first query indicating a status of the first operation, a second operation associated with a second priority level, or both, wherein the status is based on the first priority level, the second priority level, or both, and wherein the second operation includes a second write operation, a second read operation, or both.

[0029] Another apparatus for wireless communication at an inquiry device is described. The apparatus may include: means for sending a first inquiry associated with a first operation to be performed at the passive device to a passive device, wherein the first operation is associated with a first priority level and comprises a first write operation, a first read operation, or both; and means for receiving a message from the passive device based on the first inquiry indicating a status of the first operation, a second operation associated with a second priority level, or both, wherein the status is based on the first priority level, the second priority level, or both, and wherein the second operation comprises a second write operation, a second read operation, or both.

[0030] A non-transitory computer-readable medium storing code for wireless communication at an inquiry device is described. The code may include instructions executable by a processor to: send a first inquiry associated with a first operation to be performed at the passive device to a passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both; and receive a message from the passive device indicating a status of the first operation, a second operation associated with a second priority level, or both based on the first inquiry, wherein the status is based on the first priority level, the second priority level, or both, and wherein the second operation includes a second write operation, a second read operation, or both.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a second message from a passive device, the second message including an indicator associated with a second querying device and a request to stop an operation initiated by the second querying device to be performed at the passive device; and sending a third message to the second querying device indicating a request to cause the second querying device to stop the operation initiated by the second querying device based on the second message.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a first priority level via a first query, wherein receiving the message may be based on the first priority level.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first priority level may be based on a first operation comprising a first write operation or a first read operation, and wherein a second priority level may be based on a second operation comprising a second write operation or a second read operation, and wherein the first priority level may be based on a first operation type associated with the first operation, and wherein the second priority level may be based on a second operation type associated with the second operation.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling to a passive device, the control signaling indicating a priority configuration that can be used to determine a priority level associated with an operation to be performed at the passive device, wherein receiving the message can be based on the priority configuration.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a message from a passive device based on the first priority level being less than the second priority level, wherein the message includes an indication that the second operation may have a higher priority than the first operation.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a message from a passive device based on a first priority level being less than a second priority level, wherein the message includes an indication that the second operation may have a higher priority than the first operation, wherein the second operation may be associated with a second querying device.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: sending a request for an identifier associated with a second querying device to the passive device and in response to a message; receiving a second message from the passive device based on sending the request, the second message indicating the identifier associated with the second querying device; and sending a third message to the second querying device based on receiving the second message, the third message including a second request for the second querying device to stop the second operation.

[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second query associated with a second operation to the passive device, wherein the second query includes instructions to cause the passive device to cease the first operation and perform the second operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 An example of a wireless communication system supporting techniques for prioritizing and handling conflicting read and write commands to a passive device in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 2 An example of a wireless communication system supporting techniques for prioritizing and handling conflicting read and write commands to a passive device in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Figure 3 Examples of resource configurations supporting techniques for prioritizing and handling conflicting read and write commands to passive devices in accordance with one or more aspects of the present disclosure are illustrated.

[0042] Figure 4 An example of a process flow supporting techniques for prioritizing and handling conflicting read and write commands to passive devices in accordance with one or more aspects of the present disclosure is illustrated.

[0043] Figure 5 An example of a process flow supporting techniques for prioritizing and handling conflicting read and write commands to passive devices in accordance with one or more aspects of the present disclosure is illustrated.

[0044] Figure 6 Examples of resource configurations supporting techniques for prioritizing and handling conflicting read and write commands to passive devices in accordance with one or more aspects of the present disclosure are illustrated.

[0045] Figure 7 An example of a process flow supporting techniques for prioritizing and handling conflicting read and write commands to passive devices in accordance with one or more aspects of the present disclosure is illustrated.

[0046] Figure 8 An example of a process flow supporting techniques for prioritizing and handling conflicting read and write commands to passive devices in accordance with one or more aspects of the present disclosure is illustrated.

[0047] Fig. 9 and Fig.10A block diagram of a device supporting techniques for prioritizing and handling conflicting read and write commands to a passive device in accordance with one or more aspects of the present disclosure is shown.

[0048] Fig.11 A block diagram of a communications manager supporting techniques for prioritizing and handling conflicting read and write commands to passive devices in accordance with one or more aspects of the present disclosure is shown.

[0049] Fig.12 A diagram of a system including devices supporting techniques for prioritizing and handling conflicting read and write commands to passive devices is shown in accordance with one or more aspects of the present disclosure.

[0050] Fig.13 and Fig.14 A block diagram of a device supporting techniques for prioritizing and handling conflicting read and write commands to a passive device in accordance with one or more aspects of the present disclosure is shown.

[0051] Fig.15 A block diagram of a communications manager supporting techniques for prioritizing and handling conflicting read and write commands to passive devices in accordance with one or more aspects of the present disclosure is shown.

[0052] Fig.16 A diagram of a system including devices supporting techniques for prioritizing and handling conflicting read and write commands to passive devices is shown in accordance with one or more aspects of the present disclosure.

[0053] Figures 17 to 20 A flow chart illustrating a method supporting techniques for prioritizing and handling conflicting read and write commands to passive devices in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0054] Some wireless communication systems may include passive devices such as radio frequency identifier (RFID) tags, passive Internet of Things (IoT) devices, etc. to perform certain operations, such as location tracking and identification. In order to communicate with a passive device, an inquiry device (e.g., user equipment (UE), a network entity) may send a signal or inquiry to the passive device to instruct the passive device to perform a write operation and / or a read operation. A write operation may include unidirectional signaling from the inquiry device to the passive device to configure or adjust the parameters of the passive device. In contrast, a read operation may include bidirectional signaling between the inquiry device and the passive device, wherein the inquiry device sends an inquiry or message and receives or "reads" some response signaling returned from the passive device.

[0055] Passive devices (e.g., RFID tags, passive IoT devices, hybrid devices with passive and active components) may include relatively low complexity devices with limited resources and processing power. Thus, a passive device may only be able to perform a limited number of read operations or write operations at a time. In addition, some current wireless communication systems do not provide any signaling or other mechanisms to resolve conflicting (e.g., overlapping) read operations and write operations at a passive device. Thus, when multiple queries are received for performing read and / or write operations, it may not be clear which read / write operation the passive device expects to perform.

[0056] Therefore, aspects of the present disclosure are directed to signaling and other mechanisms for determining and resolving relative priorities for write operations and read operations at a passive device. Specifically, aspects of the present disclosure are directed to rules and conditions for determining relative priorities between write operations and read operations to be performed at a passive device, and signaling from a passive device for indicating the status or relative priority of conflicting read / write operations. In addition, the techniques described herein support signaling between a querying device and a passive device, as well as signaling between multiple querying devices, which can be used to preempt operations to be performed at a passive device.

[0057] For example, a passive device may receive multiple queries for performing a separate read operation or write operation, wherein the separate read operation or write operation is associated with different priorities. Queries may be received from the same or different query devices. Priority may be explicitly signaled via a query, determined based on the type of operation to be performed (e.g., a write operation may take precedence over a read operation), determined based on an identifier of the query device that sends the query, or any combination of these operations. In this example, a passive device may send a message to the query device that sends the query to indicate the state of the scheduled read / write operation (e.g., indicating which operation will be performed), and may perform one of the operations according to the corresponding priority. In some implementations, a passive device may periodically send (e.g., broadcast) the state of a passive device, which indicates whether the passive device is busy performing an operation, the relative priority of the scheduled operation, etc.

[0058] Aspects of the disclosure are first described in the context of a wireless communication system. Additional aspects of the disclosure are described in the context of example resource configurations and example process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to techniques for prioritizing and handling conflicting read and write commands to passive devices.

[0059] Figure 1An example of a wireless communication system 100 supporting techniques for prioritizing and handling conflicting read and write commands for a passive device in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

[0061] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown in FIG.

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

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

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

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

[0066] The functional split between 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, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 can be 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 are performed by different ones of CU 160, DU 165, or RU 170). CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

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

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

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

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

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

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

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

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

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

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

[0077] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers for a particular radio access technology (e.g., 1.4 megahertz (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., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

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

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

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

[0081] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of 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., N) time slots. f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

[0083] Physical channels may be multiplexed according to various techniques to communicate using carriers. Physical control channels and physical data channels may be multiplexed via downlink carriers for signaling, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may 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 sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

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

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

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

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

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

[0089] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 kilohertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about 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 may be sufficient to penetrate the structure so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0090] The wireless communication system 100 can utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to adopt license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entities 105 and UE 115 can use carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be performed based on carrier aggregation configurations (e.g., LAA) in combination with component carriers operating using licensed bands. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, etc.

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

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

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

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

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

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

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

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

[0099] UE 115 and network entity 105 may support retransmission of data to increase the possibility of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technology for improving the possibility of correctly receiving data via a communication link (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 the throughput at the MAC layer under 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 may provide HARQ feedback in a specific time slot for data received via the previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0100] In some implementations, the wireless communication system 100 may include one or more passive devices. Passive devices may include, but are not limited to, RFID tags, passive IoT devices, hybrid devices including passive and active components, passive components of additional active / inquiring devices (e.g., passive components of UE 115), or any combination thereof. For example, in some implementations, the UE 115 of the wireless communication system 100 may act as a passive device.

[0101] In some aspects, the wireless communication system 100 can support signaling and other mechanisms for determining and resolving relative priorities for write operations and read operations at a passive device. Specifically, the wireless communication system 100 can support rules and conditions for determining relative priorities between write operations and read operations to be performed at a passive device, and signaling from the passive device for indicating the status or relative priority of conflicting read / write operations. In addition, the wireless communication system 100 can support signaling between a passive device and an inquiry device and between multiple inquiry devices, which can be used to preempt operations to be performed at a passive device.

[0102] For example, a passive device of the wireless communication system 100 (e.g., an RFID tag, a passive IoT device, a hybrid device including a passive component and an active component, a passive component of another active device (such as a UE 115)) can receive multiple queries for performing separate read operations or write operations, wherein the separate read operations or write operations are associated with different priorities. The queries can be received from the same or different querying devices. For example, the passive device can receive a first query for a first operation (e.g., a first read operation or a write operation) from a first UE 115, and receive a second query for a second operation (e.g., a second read operation or a write operation) from a second UE 115. Additionally or alternatively, the passive device can receive separate queries for separate read operations or write operations from the same UE 115. The priority associated with the operation to be performed at the passive device can be explicitly signaled via the query, determined based on the type of operation to be performed (e.g., a write operation can take precedence over a read operation), determined based on an identifier of the querying device sending the query, or any combination of these operations. In this example, the passive device may send a message to the querying device (eg, UE 115) that sent the query to indicate the status of the scheduled read / write operations (eg, indicating which operation will be performed), and may perform one of the operations according to the corresponding priority.

[0103] In some specific implementations, the wireless communication system 100 can support signaling between devices, which can be used to preempt the execution of read / write operations at passive devices using higher priority operations. For example, the query device can send a query for a read operation to the passive device, and then can send a separate query for the passive device to perform a higher priority read operation, thereby preempting the original read operation. Similarly, the technology described herein can implement communication between query devices (e.g., between UE115, between the network and UE 115), which enables the query device to request other query devices to pause or suspend operations at the passive device to allow the execution of higher priority operations at the corresponding passive device. Additionally, in some aspects, the passive device of the wireless communication system 100 can periodically send (e.g., broadcast) messages indicating whether the corresponding passive device is busy performing an operation, indicating the relative priority of the read / write operation scheduled at the corresponding passive device, etc.

[0104] The technology described herein can enable passive devices such as RFID tags, passive IoT devices, etc. to determine the relative priority of read operations and write operations to be performed at the passive devices, thereby improving the speed and efficiency with which the passive devices can perform read operations and write operations. Thus, the technology described herein can improve the efficiency and latency of services and applications (such as location tracking services) associated with passive devices within a wireless communication system. In addition, the technology described herein can enable a querying device to quickly and efficiently determine the status of a corresponding passive device (e.g., whether each passive device is available or busy), thereby facilitating the ability of a querying device to identify passive devices that can be used for wireless communication.

[0105] Figure 2 An example of a wireless communication system 200 that supports techniques for prioritizing and handling conflicting read commands and write commands to passive devices in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the wireless communication system 200 may implement aspects of the wireless communication system 100, or may be implemented by these aspects. Specifically, the wireless communication system 200 may support signaling, configuration, and other mechanisms that enable passive devices to determine the relative priority of read operations and write operations to be performed at the respective passive devices, such as with respect to Figure 1 described.

[0106] The wireless communication system 200 may include a network entity 105-a, a first UE 115-a (e.g., a first RF source, RF source 1), a second UE 115-b (e.g., a second RF source, RF source 2), one or more passive devices 205, a third UE 115-c (e.g., a first reader, reader 1), and a fourth UE 115-d (e.g., a second reader, reader 2). In some aspects, the passive devices 205 (e.g., passive IoT devices) may include lower complexity devices (e.g., <100 μW devices) such as RFID tags, passive IoT devices, hybrid devices including passive and active components, passive components of an inquiry / active device (e.g., passive components of UE 115), etc. For example, the passive device 205 may include a battery-free or limited energy storage (e.g., capacitor) device capable of wireless communication.

[0107] As used herein, the term "passive device" may be used to refer to a device that may utilize passive signaling to perform transmissions by the passive device 205, utilize actively powered radio signals to perform transmissions by the passive device 205, or both. In this regard, the passive device 205 may receive power for performing transmissions from radio frequency signals received from other devices, a power source associated with the passive device 205, or both, as will be described in further detail herein. Additionally, as used herein, the terms "inquiry device," "reader," "RF source," or any combination thereof may refer to a wireless device (e.g., UE 115, network entity 105, IAB node, etc.) configured to communicate with the passive device 205, such as by sending signals (e.g., inquiries, commands) to the passive device 205, receiving / reading signals from the passive device 205, etc. Thus,

[0108] The passive device 205 may be used to support various services and applications within the wireless communication system 200, such as identification, tracking, etc. Other use cases that may be supported or facilitated by the passive device 205 may include power supply, security applications, access control or access connectivity management, positioning services, etc. The passive device 205 may be capable of communicating in different frequency ranges, such as the UHF range.

[0109] UE 115 can use communication link 210 to communicate with network entity 105-a, which can be an example of a NR or LTE link between the corresponding UE 115 and the network entity 105-a. In some cases, communication link 210 may include an example of an access link (e.g., a Uu link), which may include a bidirectional link that implements both uplink communication and downlink communication. For example, a first UE 115-a can use communication link 210-a to send an uplink signal (such as an uplink control signal or an uplink data signal) to one or more components of the first network entity 105-a, and one or more components of the first network entity 105-a can use communication link 210-a to send a downlink signal (such as a downlink control signal or a downlink data signal) to the first UE 115-a. Similarly, a second UE 115-a and network entity 105-a can communicate with each other using communication link 210-b. Additionally, the third UE 115-c, the fourth UE 115-d, or both may communicate with the network entity 105-a using the communication link 210. Additionally, in some aspects, each of the UEs 115 may communicate with each other via a communication link, such as a sidelink communication link or a PC5 link.

[0110] In some aspects, one or more passive devices 205 may be grouped into a set 220 of passive devices 205. For example, Figure 2, the first set 220-a of passive devices 205 may include a first passive device 205-a, a second passive device 205-b, and a third passive device 205-c, and the second set 220-b of passive devices 205 may include a fourth passive device 205-d and a fifth passive device 205-e. The passive devices 205 may be grouped into the set 220 of passive devices based on the type, capability, geographic location, type of service / application supported, etc. of the passive devices. In some aspects, the first UE 115-a, the second UE 115-b, or both may communicate with the passive device 205 via a communication link 215. The communication link 215 may be an example of a PC5 link, a Uu link, etc. Similarly, the third UE 115-c and the fourth UE 115-d may communicate with the passive device 205 via communication links 245-a and 245-b, respectively, where the communication link 245 may be an example of a PC5 or Uu link.

[0111] In some aspects, the corresponding wireless devices (e.g., network entity 105-a, UE 115, passive device 205) of the wireless communication system 200 can communicate with each other via energy harvesting and backscatter communication. For example, the passive device 205 can support the energy harvesting enabled communication service (EHECS) in 5GS. The terms "forward communication" and "backscatter communication" can refer to the relative communication direction between the querying device and the passive device 205. For example, in the context of backscatter communication, the first UE 115-a (e.g., the querying device) can send a signal or query to the first passive device 205-a via the forward link of the communication link 215, and the first passive device 205-a can send a backscatter message via the backscatter link of the communication link 215.

[0112] For purposes of this disclosure, the terms "inquiry device", "active device" and similar terms may be used interchangeably to refer to a wireless device that is configured to send commands or inquiries to a passive device. In addition, the terms "inquiry device", "active device" and similar terms may be used broadly to refer to a wireless device that sends signals and / or receives signals from a passive device 205, and thus may include an "RF source" and a "reader" or both. In this regard, an inquiring device may include a UE 115, a network entity 105, an IAB node, etc.

[0113] As previously noted herein, in some implementations, the passive device 205 may include relatively low complexity devices that may or may not include a power amplifier and / or a battery. In some cases, the passive device 205 may include an antenna (e.g., a dipole antenna) and other circuits (e.g., an integrated circuit, a chip, a load) for facilitating wireless communication. In some aspects, the range over which the passive device 205 may send a message (e.g., a backscattered signal) may depend on the manner in which the respective passive device 205 is powered. For example, in some cases, the passive device 205 may not include a power source, but may instead receive power from wireless communications received from an inquiry device, and may send a far-field signal or modulate a reflected signal using power absorbed or extracted from a signal received from the inquiry device. In such cases, the range of such a passive device 205 may be limited to less than ten meters.

[0114] In some aspects, the passive device 205 can use a rectifier to receive or generate power for wireless communication and other operations, wherein the rectifier may include a diode and a capacitor. For example, the passive device 205 can receive a signal from an inquiry device (e.g., UE 115, network entity 105-a) via an antenna, wherein the power absorbed from the antenna is directed to a power rectifier. In this example, the power rectifier converts the power absorbed from the antenna into rectified power, which can be directed back to the antenna to send a message (e.g., send a backscatter signal). In some cases, the power rectifier can exhibit an energy-saving efficiency of approximately thirty percent.

[0115] The power absorbed by the antenna of the passive device 205 can be directed from the antenna to the power rectifier via an amplitude shift keying (ASK) or phase shift keying (PSK) modulator. In order to perform signal modulation within the passive device 205, the ASK modulator can present two different states. In a first state (e.g., a matched load state), the integrated circuit or antenna resistance of the ASK modulator matches the backscattered power (e.g., the radiated power matches or is equal to the power absorbed by the integrated circuit). In contrast, in a second state (e.g., an unmatched load state or an open circuit state), the integrated circuit or antenna resistance of the ASK modulator does not match the backscattered power. The modulation efficiency of the ASK modulator can be defined by Modulation Efficiency = Practical / Idealized Radiation Power.

[0116] The query device (e.g., UE 115, network entity 105-a) and the passive device 205 can communicate with each other by exchanging unmodulated signals or waves (e.g., commands) with modulated signals or waves. Specifically, the query device can send a continuous wave (CW) signal to the passive device 205 to power on the corresponding passive device 205, and can send a modulated command or packet to instruct the passive device 205 to perform a write operation, a read operation, or both. In addition, the passive device 205 can convert the power absorbed from the CW signal (e.g., the power absorbed from the unmodulated signal) to send a modulated wave or message as a response to the received command.

[0117] For example, Figure 2 An interrogator (e.g., reader)-first-talk (ITF) communication procedure between an inquiry device (e.g., RF source, reader, interrogator) and a passive device 205 is illustrated. For example, a first UE 115-a may send a signal 225 to a first passive device 205-a. The signal 225 may include a CW portion 230 and a command 235. The first CW portion 230-a may power up the first passive device 205-a (e.g., turn on the passive device 205-a). The first CW portion 230-a may span more than 400 μs. As shown in FIG. Figure 2 As shown in , the first CW portion 230-a (e.g., the unmodulated portion of the signal 225) can cause the voltage of the integrated circuit of the passive device 205-a (e.g., a tag) to increase to above the turn-on voltage. Subsequently, the signal 225 can include a command 235-a (≥-20dBm) to provide information and power to the first passive device 205-a. For example, the command 235-a can instruct the first passive device 205-a to perform a read operation, a write operation, or both. The signal can include a second CW portion 230-b (≥-20dBm) to maintain the "on" or active state of the first passive device 205-a.

[0118] Continue to refer Figure 220dBm) can provide power and carrier for signal modulation to be performed by the first passive device 205-a. For example, in the context of a read operation to be performed by the first passive device 205-a, the first passive device 205-a can utilize the third CW portion 230-c to send a response 240 (e.g., a backscattered signal) to the third UE 115-c, where the third UE 115-c can perform a full-duplex read for the response 240. The signal can include: a fourth CW portion 230-d (≥-20dBm) for maintaining an "on" or active state of the first passive device 205-a and a command 235-b (≥-20dBm) to provide information and power to the first passive device 205-a, as described herein. Subsequently, after the signal 225 ends, the voltage of the first passive device 205 - a may decrease to below the turn-on voltage, and the first passive device 205 - a may return to an inactive state.

[0119] Although Figure 2 It is shown and described as including an RF source device (e.g., UE 115-a, 115-b) and a separate reader device (e.g., UE 115-c, 115-d), but this is for illustrative purposes only and is not to be considered a limitation of the present disclosure unless otherwise noted herein. For example, in some cases, the first UE 115-a can act as an RF source (e.g., a power source) that provides a signal / power to the passive device 205, and an interrogator / reader that receives (e.g., "reads") a backscattered signal or response 240 sent by the passive device 205. In other words, in some implementations, the first UE 115-a can act as both an RF source 1 and a reader 1.

[0120] The passive device 205 of the wireless communication system 200 may be configured to perform various types of operations, including write operations and read operations. A write operation may include one-way signaling from an inquiring device (e.g., UE 115-a, 115-b) to the passive device 205 to configure or adjust a parameter of the passive device 205. For example, a write operation may be used to change some information at the passive device 205 or adjust a parameter or characteristic at the passive device 205, such as an identifier associated with the passive device 205, a type or frequency of measurements performed by the passive device 205.

[0121] In contrast, a read operation may include bidirectional signaling between an inquiring device and a passive device 205, where the inquiring device sends a query or message and receives or “reads” some response signaling returned from the passive device 205. For example, in the context of a read operation, the first UE 115-a may send a query to the passive device 205 to request some information from the passive device 205, and the passive device 205 may return information or data (e.g., a response 240, a backscattered signal) in response to the query, such as data, type of control information, measurements performed by the passive device 205, the location of the passive device 205, sensed information, or any combination thereof.

[0122] The response 240 from the passive device 205 may include any type of data or information and may depend on the type of passive device 205. The types of data / information that may be included within the response 240 from the passive device 205 may include, but are not limited to, location information associated with the respective passive device 205 (e.g., current location), sensing / metering / measurement information collected or acquired by the passive device 205, expiration information (e.g., expiration date) for the item or product associated with the passive device 205 (e.g., a passive device 205 associated with a load of particles may indicate expiration information associated with the particles), the type of item or product associated with the passive device 205, the color of the item or product associated with the passive device 205, the data buffer size for data to be transmitted from the passive device 205 (e.g., the passive device 205 may indicate how much data it has to transmit), the memory size of the passive device 205, tag information, etc.

[0123] For example, in some cases, the passive device 205 may be configured to perform health-related measurements on a user or patient, including heartbeat measurements, blood pressure measurements, temperature measurements, blood oxygen measurements, etc. In this example, the response 240 may indicate a measurement performed by the passive device 205, a change (e.g., a rate of change) in a measurement performed by the passive device 205, an alert when a measurement meets a predefined threshold, etc.

[0124] However, as previously noted herein, passive devices 205 such as RFID tags, passive IoT devices, etc. may include relatively low complexity devices with limited resources and processing power. Thus, the passive device 205 may be able to perform a limited number of read operations or write operations at one time. For example, some passive devices 205 may be able to perform a single write operation or a single read operation at any given time. Thus, in some wireless communication systems, when the corresponding passive device receives a query or command to perform different operations, it may not be clear which operation the passive device 205 will perform. In other words, some wireless communication systems do not provide any signaling or other mechanisms to resolve conflicting (e.g., overlapping) read operations and write operations at the passive device 205. Thus, when multiple queries for performing read and / or write operations are received, it may not be clear which read / write operation the passive device 205 expects to perform.

[0125] Thus, aspects of the present disclosure are directed to signaling and other mechanisms for determining and resolving relative priorities for write operations and read operations at a passive device 205. Specifically, aspects of the present disclosure are directed to rules and conditions for determining relative priorities between write operations and read operations to be performed at a passive device 205, and signaling from the passive device 205 for indicating the status or relative priority of conflicting read / write operations. In addition, the techniques described herein support signaling between a passive device 205 and an inquiring device, as well as signaling between multiple inquiring devices, which can be used to preempt operations to be performed at a passive device 205.

[0126] In some specific implementations, as will be further described in detail herein, the passive device 205 can be configured to give priority to operations with higher priority levels (e.g., read operations, write operations) over operations with lower priority levels. That is, the passive device 205 can be configured to perform higher priority operations before lower priority operations. The relative priorities of the read command and the write command can be determined or signaled according to a plurality of specific implementations. Specifically, the read command and the write command can be explicitly signaled, determined based on the relative priority between the types of the read command and the write command, determined based on the priority of the query device that initiates the corresponding read / write operation, determined based on the satisfaction of one or more conditions, or any combination of these operations.

[0127] For example, in some cases, a querying device (e.g., UE 115, network entity 105-a) may send a message or query initiating a read command, a write command, or both, where the commands / queries indicate a priority level associated with the corresponding operation. In other words, when writing and / or transmitting data to a passive device 205 (e.g., an RFID tag, a passive IoT device, a hybrid device including passive and active components), each command / query or set of commands may be associated with a corresponding priority level, which may be explicitly or implicitly indicated via the command / query. Additionally, when reading from a passive device 205, each data query read from the passive device 205 may be associated with a corresponding priority level. For example, referring to Figure 2 , commands 235 - a , 235 - b may initiate a read operation, a write operation, or both to be performed by the passive device 205 , wherein the commands 235 - a , 235 - b indicate a priority level associated with the respective operation initiated by the command 235 .

[0128] In some cases, read operations and write operations can be associated with different priority levels. For example, in some cases, write operations can be associated with a higher priority level than read operations. Write operations can be given a higher priority level because write operations are used to configure / adjust system parameters at the passive device 205 that will be used for subsequent read operations. In contrast, in other specific implementations, read operations can be associated with a higher priority level than write operations.

[0129] In some respects, the priority level associated with a read operation and a write operation can vary based on the type of operation to be performed (e.g., the type of data to be read or written). For example, compared with a type B read operation and / or write operation, a type A read operation and / or write operation can be associated with a higher priority level. In such cases, the command / query for the read / write operation can indicate the type of operation to be performed (e.g., type A, type B, ..., type n), wherein the passive device 205 can be configured to determine the relative priority level of the operation based on the corresponding operation type. The type of operation can be based on multiple factors, including the type of data to be read / written by the corresponding operation, the service / application supported by the corresponding operation, etc.

[0130] In some aspects, the priority level associated with the operation to be performed at the passive device 205 can be based on the type of data to be processed / returned by the passive device 205 (e.g., operations associated with positioning data can have a higher priority level than operations associated with data size or metadata on the RFID buffer). Additionally or alternatively, the priority level associated with the operation to be performed at the passive device 205 can be based on the corresponding application associated with the operation / measurement to be performed by the passive device 205 (e.g., a medical tag performing sensory measurements for a patient can be associated with a higher priority level than other types of operations used for other applications or other contexts).

[0131] In some implementations, the priority level for a given operation (e.g., an operation priority or a session priority) can be based on the highest priority level of the associated data (e.g., a data type) to be processed, retrieved, or returned during the operation / session. For example, the first passive device 205-a can be commanded or queried to perform an operation (e.g., a session) that includes reading or writing data of type A, type B, and type C (e.g., commands / information of types A, B, and C), where data types A, data types B, and data types C are associated with different priority levels. In this example, the priority level of the operation / session can include the highest priority level associated with data types A, B, and C. In other words, the highest priority level of data types A, B, or C can determine the operation priority level (session priority level).

[0132] In additional or alternative specific implementations, the operation / session priority may be determined independently of the priority level associated with the data type. In other words, the operation may be associated with a first granularity of priority level, wherein the data type / information to be executed / returned during the corresponding operation may be associated with a second granularity of priority level of the QoS parameter. For example, continuing the above example, the first passive device 205-a may be commanded or queried to perform an operation (e.g., a session) including reading or writing data of type A, type B, and type C, wherein data type A has a higher priority than data types B and C, and data type B has a higher priority than data type C (e.g., A priority>B priority>C priority). In this example, after determining to prioritize the operation, the first passive device 205-a may then execute / retrieve the data type according to the priority level of the corresponding data type. Thus, the first passive device 205-a may first read or write data type A, then read / write data type B, and then read / write data type C.

[0133] In some aspects, the priority level associated with the operation and / or data type to be read / written can be based on other parameters, such as QoS metrics, physical requirements associated with reliability (e.g., a desire to perform a read or write operation at a certain error rate, BLER requirements, etc.), latency requirements, etc. For example, a higher QoS metric can be associated with a higher priority level than a lower QoS metric. Similarly, an operation with a lower error rate or lower latency requirement can be associated with a higher priority level than an operation with a higher error rate or higher latency requirement.

[0134] In an additional or alternative specific implementation, the priority level associated with the operation (e.g., read operation, write operation) to be performed by the passive device 205 can be determined based on the query device requesting the corresponding operation to be performed. In this regard, the passive device 205 can determine the relative priority of the read / write operation based on the identifier associated with the query device from which the command / query is received. For example, an operation initiated by the first UE 115-a may take precedence over an operation initiated by the second UE 115-b (e.g., performed before the operation initiated by the second UE). In other words, a read / write operation initiated by the first UE 115-a can be associated with a higher priority than an operation initiated by the second UE 115-b. In this regard, the command / query sent by the query device to initiate an operation at the passive device 205 may include an identifier associated with the corresponding query device so that the passive device 205 can determine the relative priority level of the initiated operation.

[0135] In some cases, a passive device 205 (e.g., an RFID tag, a passive IoT device, a hybrid device including passive and active components) can be configured by a control unit (e.g., a network entity 105-a, a base station, a gNB) to follow the order, commands, and inquiries of certain querying devices (e.g., RF sources, readers, interrogators) on other wireless devices. For example, in some cases, the network entity 105-a can send control signaling to the passive device 205, wherein the control signaling instructs the passive device 205 to prioritize operations initiated by the first UE 115-a over operations initiated by the second UE 115-b.

[0136] Similarly, in some cases, the passive device 205 may be configured with one or more priority configurations that are used to determine the relative priority between different operations or the relative priority between commands / queries received from the querying device. As used herein, the term "priority configuration" may be used to refer to a set of rules, conditions, or other parameters for determining the priority level of an operation / query and resolving conflicts between operations. For example, the first passive device 205-a may receive control signaling (e.g., a query or command for a write operation) from the network entity 105-a, the first UE 115-a, or both, wherein the control signaling indicates a priority configuration that may be used by the first passive device 205-a to determine the priority level of a read operation and a write operation to be performed by the first passive device 205-a. In this example, the priority configuration may include a condition or rule for determining a priority level associated with an operation and / or a query / command.

[0137] For example, the priority configuration may cause the first passive device 205-a to assign or determine a higher priority level associated with a write operation than a read operation. By way of another example, the priority configuration may cause the first passive device 205-a to assign or determine a higher priority level associated with a first operation initiated by the first UE 115-a than a second operation initiated by the second UE 115-b, wherein the first operation and the second operation are associated with the same operation type. In addition, unless the operation initiated by the second UE 115-b is associated with an operation type having a higher priority level (e.g., giving priority to a type A operation initiated by the second UE 115-b over a type B operation initiated by the first UE 115-a), the priority configuration may cause the first passive device 205-a to assign or determine a higher priority level associated with the operation initiated by the first UE 115-a.

[0138] In some aspects, the techniques described herein may enable an inquiring device to take over or preempt an operation initiated at the passive device 205 with other higher priority operations. For example, an inquiring device (e.g., a UE 115, a network entity 105, a gNB, a control unit programmable logic controller (PLC) in a sidelink) may communicate a message to an RF source (or reader) indicating whether to cancel reading from the passive device 205, or whether to write / read some other information with a different priority level or type of operation.

[0139] In other words, an inquiry device (e.g., UE 115) may initiate a read / write operation at the passive device 205, and may subsequently take over, cancel, or preempt the previously initiated operation with a different (e.g., higher priority) operation (e.g., the same inquiry device transmits an inquiry / command to the RFID tag for an operation with a higher priority level than the previously initiated operation). In addition, a first inquiry device (e.g., a first UE 115-a) may initiate a read / write operation at the passive device 205, and a second inquiry device (e.g., a second UE 115-b) may take over or preempt the initial operation with a different, higher priority operation. Preemption of a read / write operation at the passive device 205 may be triggered, where a new read operation of a certain type of data may cancel an old read operation with a different (e.g., lower) priority level.

[0140] About Figure 3 and Figure 4 The preemption of read / write operations by the same querying device is further shown and described in detail. Figure 3 and Figure 5 Preemption of read / write operations by different querying devices is shown and described in further detail.

[0141] Furthermore, to facilitate timely and efficient execution of higher priority operations to be performed at the passive device 205, the respective wireless devices (e.g., the passive device 205, the UE 115, the network entity 105-a) may be configured to exchange information about the initiated operations with each other in order to coordinate or negotiate which operations are to be prioritized / performed at the respective passive devices 205. Specifically, the querying device may be configured to request (from the passive device) identifiers associated with other querying devices so that the querying devices may coordinate and / or negotiate with each other regarding which operations are to be performed and / or prioritized at the passive device 205.

[0142] For example, the first UE 115-a may send a query for a read operation or a write operation to be performed at the first passive device 205-a to the first passive device 205-a, and the first passive device 205-a may respond with a message indicating that the first passive device 205-a is busy with another higher priority operation. In this example, the first UE 115-a may send a request for an identifier of a query device that initiates another higher priority operation to the first passive device 205-a. Continuing with the same example, upon receiving the request, the first passive device 205-a may send a response message indicating that the second UE 115-b is the query device that initiates another higher priority operation. Subsequently, upon receiving the identifier of the second UE 115-b, the first UE 115-a may communicate with the second UE 115-b to coordinate or negotiate which operation will be prioritized / performed at the first passive device 205-a. For example, the first UE 115-a may request information associated with a priority level for an operation initiated by the second UE 115-b, indicate the priority level of an operation to be initiated by the first UE 115-a, request the second UE 115-b to stop or postpone an operation previously initiated by the second UE 115-b, or any combination thereof.

[0143] In an additional or alternative specific implementation, information indicating an inquiry device that has initiated an operation at a passive device can be communicated by a control unit (e.g., a PLC in a side link) or other centralized unit (such as a network entity 105-a). For example, a first UE 115-a can send an inquiry for a read operation or a write operation to be performed at the first passive device 205-a to the first passive device 205-a, and the first passive device 205-a can respond with a message indicating that the first passive device 205-a is busy with another higher priority operation. In this example, the first UE 115-a can send a request for an identifier of an inquiry device that initiated another higher priority operation to the first passive device 205-a. Continuing with the same example, upon receiving the request, the first passive device 205-a can send a response message to the network entity 105-a, wherein the response message indicates that the second UE 115-b is the inquiry device that initiated another higher priority operation. The response message can additionally indicate the priority level of the corresponding operation initiated by the first UE 115-a and the second UE 115-b. In this example, the network entity 105-a may relay the response message to the first UE 115-a and / or send a message to the second UE 115-b requesting the second UE 115-b to stop or postpone the operation previously initiated by the second UE 115-b. In this regard, in some embodiments, the network entity 105-a (or other control / centralized unit) may receive information associated with different operations to be performed at the passive device 205, and may coordinate or otherwise determine which operations should be given a higher priority, and may accordingly instruct the querying device to stop, postpone, or re-initiate the operation.

[0144] In some aspects, the passive devices 205 of the wireless communication system 200 may be configured to backscatter signals to an inquiry device (e.g., a UE 115, a network entity 105), wherein the backscattered signals indicate the status of the corresponding passive device 205. That is, the passive device 205 may send or broadcast a message indicating whether the corresponding passive device 205 is subscribed, whether the passive device 205 is being read by another inquiry device (e.g., another RF source / reader), etc. In this regard, the passive device 205 may send or broadcast a message associated with a queue of operations to be performed by the corresponding passive device 205 to inform the inquiry device whether the corresponding passive device 205 is busy (e.g., whether the corresponding passive device is subscribed).

[0145] For the purposes of this disclosure, the term "status message" may be used to refer to a signal or message sent / broadcasted by a passive device 205 that indicates whether the corresponding passive device 205 is busy / booked. In other words, the status message may convey information associated with the status of the passive device 205 (e.g., whether the passive device 205 is available or busy / booked), information associated with a queue of operations to be performed by the passive device 205, etc. The status message may indicate the number of operations in the queue of operations to be performed by the passive device 205, the type of operations in the queue, the priority level of the operations in the queue, an identifier of the querying device that initiated the operation (e.g., the ID of the RF source, the ID of the reader), whether the corresponding operations in the queue are with the same device for the RF source / reader or with different devices for the RF source and the reader, or any combination of these.

[0146] In some cases, status messages indicating the status of the passive device 205 or a queue may be sent periodically, aperiodically, etc. For example, the first passive device 205-a may send status messages associated with a queue of operations to be performed by the first passive device 205-a according to an aperiodicity. In this example, the periodicity may be preconfigured at the first passive device 205-a, signaled to the first passive device 205-a (e.g., via a write query / command), or both.

[0147] The mechanism by which a passive device 205 sends a status message associated with the state / queue of the corresponding passive device 205 may be based on whether the corresponding passive device 205 includes a separate power source. Specifically, a passive device 205 that includes a separate power source may be able to send a status message associated with the state / queue of operation by itself (e.g., without receiving a signal / power from an inquiry device). In other words, in this example, the first passive device 205-a may include a power source and / or an active or semi-active RF component that is capable of independently sending a signal and generating a waveform (without backscatter). In contrast, a passive device 205 that does not include a separate power source may receive a signal / power from an inquiry device (e.g., UE 115, network entity 105-a, centralized unit, RF transmitter) to enable the passive device 205 to send a status message.

[0148] For example, where the first passive device 205-a includes a power source, the first passive device 205-a may autonomously send / broadcast a status message associated with the state / queue of the first passive device 205-a to notify neighboring query devices of the availability of the first passive device 205-a. By way of another example, the second passive device 205-b may not include a power source. In this example, the first UE 115-a and / or the second UE 115-b (RF source) may periodically or aperiodically send an RF source signal to provide the second passive device 205-b with power that can be used to send (e.g., backscatter) a status message associated with the state / queue of the second passive device 205-b.

[0149] The techniques described herein may enable a passive device 205, such as an RFID tag, to determine the relative priority of read operations and write operations to be performed at the passive device 205, thereby improving the speed and efficiency with which the passive device 205 is able to perform read operations and write operations. As a result, the techniques described herein may improve the efficiency and latency of services and applications (such as location tracking services) associated with the passive devices 205 within the wireless communication system 200. In addition, the techniques described herein may enable a querying device (e.g., a UE 115, a network entity 105-a) to quickly and efficiently determine the status of the corresponding passive devices 205 (e.g., whether each passive device 205 is available or busy), thereby facilitating the querying device's ability to identify the passive devices 205 that are available for wireless communication.

[0150] Figure 3 An example of a resource configuration 300 supporting techniques for prioritizing and handling conflicting read commands and write commands for a passive device in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the resource configuration 300 can implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, or both. Specifically, the resource configuration 300 illustrates signaling between a passive device and an RF source that enables the passive device to determine and signal relative priorities between read operations and write operations, as described in reference to FIG. Figure 1-Figure 2 and other aspects described.

[0151] Resource configuration 300 illustrates a configuration in which a passive device (eg, Figure 2 2 and 3. In particular, resource configuration 300 illustrates communication between a first querying device 305-a, a second querying device 305-b, and a passive device.

[0152] At 310, the first querying device 305-a may send a query or command to start or initiate a first operation (e.g., a first read operation, a first write operation) at the passive device, where the first operation is associated with a first priority level (priority 1). For example, the first querying device 305-a may send the CW portion 230 of the query to power up the passive device, such as Figure 2 As previously described herein, the priority level of the first operation can be explicitly or implicitly signaled via the query at 310 and / or determined based on the type of operation, a priority or identifier associated with the first querying device 305-a, based on a priority configuration, or any combination thereof. At 315, the first querying device 305-a sends a query or command for the first operation. For example, the first querying device can send a command 235-a for the first operation, such as Figure 2 As shown in .

[0153] At 320, the second querying device 305-b may send a query or command to start or initiate a second operation (e.g., a second read operation, a second write operation) at the passive device, wherein the second operation is associated with a second priority level (priority 2) that is less than the first priority level (e.g., priority 2 < priority 1). For example, the second querying device 305-b may send the CW portion 230 of the query to power up the passive device, such as Figure 2 As previously described herein, the priority level of the second operation can be explicitly or implicitly signaled via the query at 320 and / or determined based on the type of operation, a priority or identifier associated with the second querying device 305-b, based on a priority configuration, or any combination thereof.

[0154] At 325, the passive device may send a response message to the second querying device 305-b, wherein the response message indicates that the passive device is busy communicating with another reader / querying device for an operation / session having a higher priority. In other words, the passive device may indicate to the second querying device 305-b that the passive device is prioritizing a first operation initiated by the first querying device 305-a over a second operation initiated by the second querying device 305-b.

[0155] At 330, 335, 340, or any combination thereof, the passive device may perform a first operation. For example, in the context of a write operation, the passive device may configure or modify one or more operating parameters of the passive device. In contrast, in the context of a read operation, the passive device may send signals to the first querying device 305-a (or a related reader device), where the signals indicate measurements performed by the passive device, the location of the passive device, etc.

[0156] You can refer to Figure 4 and Figure 5 To further understand Figure 3 The signaling and operations shown and described in .

[0157] Figure 4 An example of a process flow 400 supporting techniques for prioritizing and handling conflicting read commands and write commands to a passive device in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the process flow 400 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the resource configuration 300, or any combination thereof. Specifically, the process flow 400 illustrates signaling between an inquiring device and a passive device that enables the inquiring device to preempt a previously initiated read / write operation with a higher priority operation, as described in reference to FIG. Figure 1-Figure 3 and other aspects described.

[0158] Process flow 400 may include a passive device 405 and an inquiry device 410, which may be a reference device. Figure 1-Figure 3 Examples of passive devices, UE 115, network entity 105, and other wireless devices described herein. For example, passive device 405 may include an example of a passive component of an RFID tag or query device, such as Figure 2 Similarly, the query device 410 may include an example of a network entity 105-a, a UE 115, or both, such as Figure 2 shown and described in .

[0159] In some examples, the operations illustrated in process flow 400 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code (e.g., software) executed by a processor, or any combination thereof. The following alternative examples may be implemented in which some of the steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added.

[0160] At 415, the passive device 405 may send or broadcast a message indicating information associated with a state or queue of operations to be performed at the passive device 405. In other words, the passive device 405 may send a message indicating whether the passive device 405 is available or whether the passive device is booked / busy. In some cases, at 405, the passive device 405 may send a message according to a periodicity, which may be preconfigured, signaled to the passive device 405 (e.g., via a write operation), or both. In addition, in some cases, the passive device 405 may send a message at 415 based on receiving (e.g., from the query device 410 or other device, such as the network entity 105) a certain RF signal that provides power for the passive device 405 to transmit a signal.

[0161] At 420, the querying device 410 may send a signal or message to the passive device 405 to start a first operation (operation 1) at the passive device 405. The first operation may include a read operation or a write operation to be performed by the passive device, wherein the first operation is associated with the second priority level (priority 2). For example, the querying device 410 may send the CW portion 230 of the query to power up the passive device, such as Figure 2 As previously described herein, the priority level of the first operation can be explicitly or implicitly signaled via the message at 420 and / or determined based on the type of operation, a priority or identifier associated with the querying device 410, based on a priority configuration, or any combination thereof. In some aspects, the querying device 410 can send the message at 420 based on receiving a message associated with the state / queue of the passive device 405 at 415.

[0162] At 425, the query device 410 may send a query or command for the first operation. For example, the query device 410 may send a command 235-a for the first operation, such as Figure 2 Thus, querying device 410 may send a query at 425 based on sending a message at 420 for initiating the first operation. In some aspects, the query at 420 may indicate an operation type associated with the first operation, a priority level associated with the first operation, or both.

[0163] At 430, the querying device 410 may send a message (e.g., a query, a command) for the passive device 405 to perform a second operation (operation 2) having a higher priority (priority 1) than the first operation (e.g., priority 1>priority 2). In other words, the querying device 410 may instruct the passive device to stop the current session (e.g., stop or refrain from performing the first operation) in order to start a new read / write operation (e.g., operation 2). Thus, the querying device 410 may effectively preempt the original first operation in place of the second operation having a higher priority.

[0164] In the event that the passive device 405 prioritizes the second operation over the first operation, the passive device 405 may add the first operation (Operation 1) to a queue of operations to be performed by the passive device 405. In this regard, Operation 1 may be stored in a queue or memory such that the passive device 405 may perform Operation 1 after Operation 2 is completed.

[0165] At 435, the passive device 405 may perform a second operation (operation 2). For example, in the context of a write operation, the passive device 405 may configure or modify one or more operating parameters of the passive device 405. In contrast, in the context of a read operation, the passive device 405 may send signals to the querying device 410 (or a related reader device), where the signals indicate measurements performed by the passive device 405, the location of the passive device 405, etc.

[0166] In the event that the passive device 405 prioritizes operation 2 over operation 1, the passive device 405 may add operation 1 to a queue of operations to be performed by the passive device 405. In this regard, operation 1 may be stored in a queue or memory such that the passive device 405 may perform operation 1 after operation 2 is completed.

[0167] The techniques described herein may enable a querying device to preempt or take over a previous operation initiated at the passive device 405. Specifically, Figure 4 As shown in , techniques described herein may enable an inquiring device 410 to preempt another operation previously initiated by the inquiring device 410 at the passive device 405 .

[0168] Figure 5An example of a process flow 500 supporting techniques for prioritizing and handling conflicting read commands and write commands to a passive device in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the process flow 500 can implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the resource configuration 300, or any combination thereof. Specifically, the process flow 500 illustrates signaling between an inquiring device and a passive device that enables the inquiring device to preempt a read / write operation previously initiated by another inquiring device with a higher priority operation, as described in reference to FIG. Figure 1-Figure 4 and other aspects described.

[0169] The process flow 500 may include a passive device 505, a first querying device 510-a, and a second querying device 510-b, wherein the passive device, the first querying device, and the second querying device may be reference devices. Figure 1-Figure 4 Examples of passive devices, UE 115, network entity 105, and other wireless devices described herein. For example, passive device 505 may include an example of a passive component of an RFID tag or query device, such as Figure 2 Additionally, the first querying device 510-a may include an example of the first UE 115-a, the third UE 115-c, or both, such as Figure 2 Similarly, the second querying device 510_b may include an example of a second UE 115_b, a fourth UE 115-d, or both, such as Figure 2 shown and described in .

[0170] In some examples, the operations illustrated in process flow 500 can be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. The following alternative examples can be implemented in which some of the steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added.

[0171] At 515, the passive device 505 may send or broadcast a message indicating information associated with the status or queue of operations to be performed at the passive device 505 to the first query device 510-a, the second query device 510-b, or both. In other words, the passive device 505 may send a message indicating whether the passive device 505 is available or whether the passive device is booked / busy. In some cases, at 405, the passive device 505 may send a message according to a periodicity, where the periodicity may be preconfigured, signaled to the passive device 505 (e.g., via a write operation), or both. In addition, in some cases, the passive device 505 may send a message based on receiving a certain RF signal at 515 (e.g., from the first query device 510-a, the second query device 510-b, or other devices, such as the network entity 105) that provides power to the passive device 505 to transmit a signal.

[0172] At 520, the first querying device 510-a may send a signal or message to the passive device 505 to initiate a first operation (operation 1) at the passive device 505. The first operation may include a read operation or a write operation to be performed by the passive device 505, wherein the first operation is associated with a first priority level (priority 1). For example, the first querying device 510-a may send the CW portion 230 of the query to power up the passive device, such as Figure 2 As previously described herein, the priority level of the first operation can be explicitly or implicitly signaled via the message at 520 and / or determined based on the type of operation, a priority or identifier associated with the first querying device 510-a, based on a priority configuration, or any combination thereof. In some aspects, the first querying device 510-a can send the message at 520 based on receiving a message associated with the state / queue of the passive device 505 at 515.

[0173] At 525, the first querying device 510-a may send a query or command for the first operation. For example, the first querying device 510-a may send a command 235-a for the first operation, such as Figure 2 Thus, the first querying device 510-a may send a query at 520 based on sending a message at 520 to initiate the first operation and / or receiving a message at 515 associated with the state / queue of the passive device 505. In some aspects, the query at 525 may indicate an operation type associated with the first operation (e.g., Type A), a priority level associated with the first operation, or both.

[0174] At 530, the second querying device 510-b may send a message (e.g., a query, a command) for the passive device 505 to perform a second operation (operation 2) having a lower priority (priority 2) than the first operation (e.g., priority 1 > priority 2). In other words, the second querying device 510-b may attempt to preempt the first operation at the passive device 505 by sending a query for the second operation. However, in some implementations, the passive device 505 may be configured to prioritize higher priority operations over lower priority operations, and thus may prioritize operation 1 over operation 2 (e.g., perform operation 1 before operation 2). In some aspects, the second querying device 510-b may send the message at 530 based on receiving a message associated with the state / queue of the passive device 505 at 515.

[0175] At 535, the passive device 505 may send a response message to the second querying device 510-b, wherein the response message indicates that the passive device 505 is busy communicating with another reader / querying device for an operation / session with a higher priority. In other words, the passive device 505 may indicate to the second querying device 510-b that the passive device 505 is prioritizing operation 1 initiated by the first querying device 510-a over operation 2 initiated by the second querying device 510-b. In some implementations, the passive device 505 may send a response message to both the first querying device and the second querying device 510 so that the querying device 510 can predict or expect the behavior of the passive device 505.

[0176] In the event that the passive device 505 prioritizes operation 1 over operation 2, the passive device 505 may add operation 2 to a queue of operations to be performed by the passive device 505. In this regard, operation 2 may be stored in a queue or memory such that the passive device 505 may perform operation 2 after operation 1 is completed.

[0177] At 540, the second querying device 510-b may send a message (e.g., a query, a command) for the passive device 505 to perform a third operation (Operation 3). In some aspects, the third operation may be associated with an operation type (Type 3) having a higher priority than other operation types. In other words, an operation associated with Type B may have a higher priority than an operation associated with Type A. In this regard, Operation 3 may have a higher priority level (e.g., Priority 1) than both Operation 1 and Operation 2. Op 3 >Priority Ops 1 and 2 Thus, the passive device 505 may be configured to prioritize operation 3 over operations 1 and 2. Thus, the second querying device 505 - b may effectively preempt operation 1 previously initiated by the first querying device 510 - a .

[0178] At 545, the passive device 505 may send a message to the first querying device 510-a, wherein the message indicates that the passive device 505 will stop performing (or refrain from performing) the first operation due to the fact that the passive device 505 received a query for a higher priority operation. In other words, the passive device 505 may indicate that operation 1 has been preempted by a higher priority operation. In some cases, the passive device 505 may additionally send a message to the second querying device 510-b at 545 to indicate that the passive device 505 will prioritize operation 3.

[0179] In the event that the passive device 505 prioritizes operation 3 over operation 1 (and operation 2), the passive device 505 may add operation 1 to a queue of operations to be performed by the passive device 505. Furthermore, due to the fact that operation 1 is associated with a higher priority than operation 2, operation 1 may be added to the queue before operation 2. In this regard, operation 1 may be stored in a queue or memory such that the passive device 505 may perform operation 1 after operation 2 is completed.

[0180] At 550, the second query device 510_b may send a query or command for the third operation. For example, the second query device 510_b may send a command 235-a for the first operation, such as Figure 2 Thus, the second querying device 510-b may send a query at 550 based on sending a message for initiating the third operation at 540, receiving a response message at 545, or both. In some aspects, the query at 545 may indicate an operation type associated with the third operation (e.g., type b), a priority level associated with the third operation, or both.

[0181] At 555, the passive device 505 may perform a third operation (operation 3). For example, in the context of a write operation, the passive device 505 may configure or modify one or more operating parameters of the passive device 505. In contrast, in the context of a read operation, the passive device 505 may send signals to the second querying device 510-b (or a related reader device), where the signals indicate measurements performed by the passive device 505, the location of the passive device 405, etc.

[0182] The techniques described herein may enable the query device 510 to preempt or take over a previous operation initiated at the passive device 505. Specifically, Figure 5 As shown in , techniques described herein may enable a second querying device 510 - b to preempt another operation previously initiated at a passive device 505 by a first querying device 510 - a .

[0183] Figure 6An example of a resource configuration 600 supporting techniques for prioritizing and handling conflicting read commands and write commands for a passive device in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the resource configuration 600 can implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, or both. Specifically, the resource configuration 600 illustrates signaling between a passive device and an RF source that enables the passive device to determine and signal relative priorities between read operations and write operations, as described in reference to FIG. Figure 1-Figure 5 and other aspects described.

[0184] Resource configuration 600 illustrates a configuration in which a passive device (eg, Figure 2 6 and one or more querying devices 605. Specifically, resource configuration 600 illustrates communication between a first querying device 605-a, a second querying device 605-b, and a passive device.

[0185] At 610, the first querying device 605-a may send a query or command to start or initiate a first operation (e.g., a first read operation, a first write operation) at the passive device, where the first operation is associated with a second priority level (priority 2). For example, the first querying device 605-a may send the CW portion 230 of the query to power up the passive device, such as Figure 2 As previously described herein, the priority level of the first operation can be explicitly or implicitly signaled via the query at 610 and / or determined based on the type of operation, a priority or identifier associated with the first querying device 605-a, based on a priority configuration, or any combination thereof. At 615, the first querying device 605-a sends a query or command for the first operation. For example, the first querying device can send a command 235-a for the first operation, such as Figure 2 As shown in .

[0186] At 620, the second querying device 605-a may send a query or command to start or initiate a second operation (e.g., a second read operation, a second write operation) at the passive device, wherein the second operation is associated with a first priority level (priority 1) that is higher than the first priority level (e.g., priority 1 > priority 2). For example, the second querying device 605-a may send the CW portion 230 of the query to power up the passive device, such as Figure 2As previously described herein, the priority level of the second operation can be explicitly or implicitly signaled via the query at 620 and / or determined based on the type of operation, a priority or identifier associated with the second querying device 605-b, based on a priority configuration, or any combination thereof.

[0187] At 625, the passive device may send a response message to the first querying device 605-b, wherein the response message indicates that the passive device has received a query for a higher priority operation and will therefore stop, cancel, or postpone the first operation initiated by the first querying device 605-a. In other words, the passive device may indicate to the first querying device 605-b that the passive device is prioritizing the second operation initiated by the second querying device 605-b over the first operation initiated by the first querying device 605-a.

[0188] At 630, 635, and 640, the passive device may cancel or otherwise refrain from performing the first operation initiated by the first querying device 605-a. The passive device may cancel or refrain from performing the first operation at 630-640 based on receiving a query for a higher priority operation at 620, sending a response message to the first querying device 605-a at 625, or both.

[0189] At 645, 650, or both, the passive device may perform a second operation. For example, in the context of a write operation, the passive device may configure or modify one or more operating parameters of the passive device. In contrast, in the context of a read operation, the passive device may send signals to a second querying device 605-b (or an associated reader device), where the signals indicate measurements performed by the passive device, the location of the passive device, etc.

[0190] You can refer to Figure 7 and Figure 8 To further understand Figure 6 The signaling and operations shown and described in .

[0191] Figure 7 An example of a process flow 700 supporting techniques for prioritizing and handling conflicting read commands and write commands for a passive device in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the process flow 700 can implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the resource configuration 600, or any combination thereof. Specifically, the process flow 700 illustrates signaling between an inquiring device and a passive device that enables the inquiring device to preempt a read / write operation previously initiated by another inquiring device with a higher priority operation, as described in reference to FIG. Figure 1-Figure 6 and other aspects described.

[0192] The process flow 700 may include a passive device 705, a first querying device 710-a, and a second querying device 710-b, wherein the passive device, the first querying device, and the second querying device may be reference devices. Figure 1-Figure 6 Examples of passive devices, UE 115, network entity 105, and other wireless devices described herein. For example, passive device 705 may include an example of a passive component of an RFID tag or query device, such as Figure 2 Additionally, the first querying device 710-a may include an example of the first UE 115-a, the third UE 115-c, or both, such as Figure 2 Similarly, the second querying device 710-b may include an example of a second UE 115-b, a fourth UE 115-d, or both, such as Figure 2 shown and described in .

[0193] In some examples, the operations illustrated in process flow 700 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code (e.g., software) executed by a processor, or any combination thereof. The following alternative examples may be implemented in which some of the steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added.

[0194] At 715, the passive device 705 may send or broadcast a message indicating information associated with a status or queue of operations to be performed at the passive device 705 to the first querying device 710-a, the second querying device 710-b, or both. In other words, the passive device 705 may send a message indicating whether the passive device 705 is available or whether the passive device is booked / busy. In some cases, at 405, the passive device 705 may send the message according to a periodicity, where the periodicity may be preconfigured, signaled to the passive device 705 (e.g., via a write operation), or both. In addition, in some cases, the passive device 705 may send the message based on receiving (e.g., from the first querying device 710-a, the second querying device 710-b, or other devices, such as the network entity 105) a certain RF signal that provides power for the passive device 705 to transmit the signal at 715.

[0195] At 720, the first querying device 710-a may send a signal or message to the passive device 705 to initiate a first operation (operation 1) at the passive device 705. The first operation may include a read operation or a write operation to be performed by the passive device 705, wherein the first operation is associated with a first priority level (priority 1). For example, the first querying device 710-a may send the CW portion 230 of the query to power up the passive device, such as Figure 2 As previously described herein, the priority level of the first operation can be explicitly or implicitly signaled via the message at 720 and / or determined based on the type of operation, a priority or identifier associated with the first querying device 710-a, based on a priority configuration, or any combination thereof. In some aspects, the first querying device 710-a can send the message at 720 based on receiving a message associated with the state / queue of the passive device 705 at 715.

[0196] At 725, the first querying device 710-a may send a query or command for the first operation. For example, the first querying device 710-a may send a command 235-a for the first operation, such as Figure 2 Thus, the first querying device 710-a may send a query at 720 based on sending a message at 720 to initiate the first operation and / or receiving a message at 715 associated with the state / queue of the passive device 705. In some aspects, the query at 725 may indicate an operation type associated with the first operation (e.g., Type A), a priority level associated with the first operation, or both.

[0197] At 730, the second querying device 710-b may send a message (e.g., a query, a command) for the passive device 705 to perform a second operation (operation 2) having the same or higher priority (e.g., priority 1) than the first operation. In other words, the second querying device 710-b may attempt to preempt the first operation at the passive device 705 by sending a query for the second operation. In some aspects, the second querying device 710-b may send the message at 730 based on receiving a message associated with the state / queue of the passive device 705 at 715.

[0198] At 735, the passive device 705 may send a response message to the second querying device 710-b, wherein the response message indicates that the passive device 705 is busy communicating with another reader / querying device for an operation / session with a higher priority. In other words, the passive device 705 may indicate to the second querying device 710-b that the passive device 705 is prioritizing operation 1 initiated by the first querying device 710-a over operation 2 initiated by the second querying device 710-b. In some implementations, the passive device 705 may send a response message to both the first querying device and the second querying device 710 so that the querying device 710 can predict or expect the behavior of the passive device 705.

[0199] At 740, the second querying device 710-b may send a request for an identification or identifier associated with a previously initiated operation that was prioritized at the passive device 705. In other words, the second querying device 710-b may request a reader ID associated with the querying device 710 (e.g., the first querying device 710-a) that initiated operation 1 that took precedence over operation 2. The second querying device 710-b may send the request at 740 based on sending the query / message at 730, receiving the response message at 735, or both.

[0200] At 745, the passive device 705 may send a message indicating an identifier associated with the first querying device 710-a to the second querying device 710-b. In other words, the passive device 705 may send a message indicating the reader ID of the first querying device 710-a. The passive device 705 may send a message indicating the current reader ID at 745 based on (e.g., in response to) receiving the request at 740.

[0201] At 750, the second querying device 710-b may send a message to the first querying device 710-a, wherein the message indicates that the second querying device 710-b has an operation to be performed with the passive device 705 that has the same or higher priority as the operation previously initiated by the first querying device 710-a. In this regard, in some cases, the message at 750 may include a request or instruction for the first querying device 710-a to stop, cancel, or postpone the first operation so that the passive device 705 can perform or prioritize the second operation initiated by the second querying device 710-b. In some cases, the message at 750 may indicate information associated with the second operation, such as a priority level, an operation type, an identifier associated with the second querying device 710-b, or any combination thereof. In addition, the second querying device 710-b may send the message at 750 based on receiving an identifier (e.g., a reader ID) associated with the first querying device 710-a at 745.

[0202] Upon receiving the message at 750, the first query device 710-a and the second query device 710-b may coordinate or negotiate which operation will be performed / prioritized at the passive device 705. In some specific implementations, the first query device 710-a may stop, cancel, or postpone the first operation in response to the message at 750. In such cases, the first query device 710-a may send a message to the passive device 705 to stop, cancel, or postpone the first operation. Additionally, in some cases, the first query device 710-a and / or the passive device 705 may send a message to the second query device 710-b indicating that the first operation has been postponed. In this regard, the second query device 710-b may send a query to the passive device 705 to re-initiate the second operation (operation 2).

[0203] Techniques described herein may enable the passive device 705 and the inquiring device 710 to exchange information with each other (eg, an identifier or reader ID of the inquiring device 710 ) to enable the inquiring device 710 to coordinate or negotiate which operations are to be performed at the passive device 705 and / or prioritized.

[0204] Figure 8 An example of a process flow 800 supporting techniques for prioritizing and handling conflicting read commands and write commands for a passive device in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the process flow 700 can implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the resource configuration 600, the process flow 700, or any combination thereof. Specifically, the process flow 800 illustrates signaling between an inquiring device and a passive device that enables the inquiring device to preempt a read / write operation previously initiated by another inquiring device with a higher priority operation, as described in reference to FIG. Figure 1-Figure 7 and other aspects described.

[0205] Process flow 800 may include a passive device 805, a first querying device 810-a, a second querying device 810-b, and a network entity 105-b, wherein the passive device, the first querying device, the second querying device, and the network entity may be reference Figure 1-Figure 7 Examples of passive devices, UE 115, network entity 105, and other wireless devices described herein. For example, passive device 805 may include an example of a passive component of an RFID tag or query device, such as Figure 2 Additionally, the first querying device 810-a may include an example of the first UE 115-a, the third UE 115-c, or both, such as Figure 2Similarly, the second querying device 810-b may include an example of a second UE 115-b, a fourth UE 115-d, or both, as shown and described in 2. Similarly, Figure 8 The network entity 105-b illustrated in FIG. 1 may include Figure 2 An example of a network entity 105 - a is shown and described in .

[0206] In some examples, the operations illustrated in process flow 800 can be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code (e.g., software) executed by a processor, or any combination thereof. The following alternative examples can be implemented in which some of the steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added.

[0207] At 815, the passive device 805 may send or broadcast a message indicating information associated with a status or queue of operations to be performed at the passive device 805 to the first querying device 810-a, the second querying device 810-b, or both. In other words, the passive device 805 may send a message indicating whether the passive device 805 is available or whether the passive device is booked / busy. In some cases, at 405, the passive device 805 may send a message according to a periodicity, where the periodicity may be preconfigured, signaled to the passive device 805 (e.g., via a write operation), or both. In addition, in some cases, the passive device 805 may send a message based on receiving a certain RF signal at 815 (e.g., from the first querying device 810-a, the second querying device 810-b, the network entity 105-b, etc.) that provides power for the passive device 805 to transmit a signal.

[0208] At 820, the first querying device 810-a may send a signal or message to the passive device 805 to initiate a first operation (operation 1) at the passive device 805. The first operation may include a read operation or a write operation to be performed by the passive device 805, wherein the first operation is associated with a first priority level (priority 1). For example, the first querying device 810-a may send the CW portion 230 of the query to power up the passive device, such as Figure 2 . As previously described herein, the priority level of the first operation can be explicitly or implicitly signaled via the message at 820 and / or determined based on the type of operation, a priority or identifier associated with the first querying device 810-a, based on a priority configuration, or any combination thereof. In some aspects, the first querying device 810-a can send the message at 820 based on receiving the message associated with the state / queue of the passive device 805 at 815.

[0209] At 825, the first querying device 810-a may send a query or command for the first operation. For example, the first querying device 810-a may send a command 235-a for the first operation, such as Figure 2 Thus, the first querying device 810-a may send a query at 820 based on sending a message at 820 to initiate the first operation and / or receiving a message at 815 associated with the state / queue of the passive device 805. In some aspects, the query at 825 may indicate an operation type associated with the first operation (e.g., Type A), a priority level associated with the first operation, or both.

[0210] At 830, the second querying device 810-b may send a message (e.g., a query, a command) for the passive device 805 to perform a second operation (operation 2) having the same or higher priority (e.g., priority 1) than the first operation. In other words, the second querying device 810-b may attempt to preempt the first operation at the passive device 805 by sending a query for the second operation. In some aspects, the second querying device 810-b may send the message at 830 based on receiving a message associated with the state / queue of the passive device 805 at 815.

[0211] At 835, the passive device 805 may send a response message to the second querying device 810-b, wherein the response message indicates that the passive device 805 is busy communicating with another reader / querying device for an operation / session with a higher priority. In other words, the passive device 805 may indicate to the second querying device 810-b that the passive device 805 is prioritizing operation 1 initiated by the first querying device 810-a over operation 2 initiated by the second querying device 810-b. In some implementations, the passive device 805 may send a response message to both the first querying device and the second querying device 810 so that the querying device 810 can predict or expect the behavior of the passive device 805.

[0212] At 840, the second querying device 810-b may send a request for an identification or identifier associated with a previously initiated operation that was prioritized at the passive device 805. In other words, the second querying device 810-b may request a reader ID associated with the querying device 810 (e.g., the first querying device 810-a) that initiated operation 1 that took precedence over operation 2. The second querying device 810-b may send the request at 840 based on sending the query / message at 830, receiving the response message at 835, or both.

[0213] At 845, the passive device 805 may send a message indicating an identifier associated with the first querying device 810-a to the second querying device 810-b, the network entity 105-b, or both. In other words, the passive device 805 may send a message indicating the reader ID of the first querying device 810-a. The passive device 805 may send a message indicating the current reader ID at 845 based on (e.g., in response to) receiving the request at 840.

[0214] At 850, the network entity 105-b may send a message to the first querying device 810-a, wherein the message indicates that the second querying device 810-b has an operation to be performed with the passive device 805 having the same or higher priority as the operation previously initiated by the first querying device 810-a. In this regard, in some cases, the message at 850 may include a request or instruction for the first querying device 810-a to stop, cancel, or postpone the first operation so that the passive device 805 can perform or prioritize the second operation initiated by the second querying device 810-b. In some cases, the message at 850 may indicate information associated with the second operation, such as a priority level, an operation type, an identifier associated with the second querying device 810-b, or any combination thereof. In addition, the network entity 105-b may send the message at 850 based on receiving an identifier (e.g., a reader ID) associated with the first querying device 810-a at 845.

[0215] At 855 , the first querying device 810 - a may send a message to the passive device 805 to stop, cancel, or postpone the first operation. The first querying device 810 - a may send the message at 855 based on receiving the message at 850 .

[0216] At 860, the first querying device 810-a may send a message to the second querying device 810-b, the network entity 105-b, or both, wherein the message indicates that the first querying device 810-a has canceled or postponed the first operation. In this regard, the first querying device 810-a may send the message at 860 based on receiving the message at 850, sending the message at 855, or both.

[0217] In some aspects, the second querying device 810 - b may send a query to the passive device 805 to re-initiate the second operation after receiving the message at 860 indicating that the first querying device 810 - a canceled or postponed the first operation (operation 2 ).

[0218] Techniques described herein may enable the passive device 805 and the inquiring device 810 to exchange information with each other (eg, an identifier or reader ID of the inquiring device 810 ) to enable the inquiring device 810 to coordinate or negotiate which operations are to be performed at the passive device 805 and / or prioritized.

[0219] Fig. 9 A block diagram 900 of a device 905 supporting techniques for prioritizing and handling conflicting read and write commands for a passive device in accordance with one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of a passive device (e.g., an RFID tag, a passive IoT device, a hybrid device including passive and active components, a passive component of a UE 115) as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0220] Receiver 910 may provide means for receiving information associated with various information channels (e.g., control channels, data channels, information channels related to techniques for prioritizing and handling conflicting read commands and write commands to passive devices), such as packets, user data, control information, or any combination thereof. The information may be communicated to other components of device 905. Receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0221] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to techniques for prioritizing and handling conflicting read commands and write commands for passive devices), user data, control information, or any combination thereof. In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0222] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for prioritizing and handling conflicting read and write commands for passive devices as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

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

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

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

[0226] According to the examples disclosed herein, the communication manager 920 can support wireless communication at the passive device. For example, the communication manager 920 can be configured to or otherwise support a component for receiving a first query associated with a first operation to be performed at the passive device from a first query device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The communication manager 920 can be configured to or otherwise support a component for receiving a second query associated with a second operation to be performed at the passive device from a first query device or a second query device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both. The communication manager 920 can be configured to or otherwise support a component for sending a message indicating the status of the first operation, the second operation, or both to the first query device, the second query device, or both. The communication manager 920 can be configured to or otherwise support a component for performing one of the first operation or the second operation according to the first priority level and the second priority level and based on sending the message.

[0227] By including or configuring a communication manager 920 according to the examples described herein, the device 905 (e.g., a processor that controls or otherwise couples to the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof) can support techniques that enable a passive device (such as an RFID tag) to determine the relative priority of read operations and write operations to be performed at the passive device, thereby improving the speed and efficiency with which the passive device can perform read operations and write operations. As a result, the techniques described herein can improve the efficiency and latency of services and applications (such as location tracking services) associated with passive devices within a wireless communication system. In addition, the techniques described herein can enable an inquiry device to quickly and efficiently determine the status of a corresponding passive device (e.g., whether each passive device is available or busy), thereby facilitating the ability of the inquiry device to identify passive devices that can be used for wireless communication.

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

[0229] The receiver 1010 may provide means for receiving information associated with various information channels (e.g., control channels, data channels, information channels related to techniques for prioritizing and handling conflicting read commands and write commands for passive devices), such as packets, user data, control information, or any combination thereof. The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0230] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to techniques for prioritizing and handling conflicting read commands and write commands for passive devices), user data, control information, or any combination thereof. In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0231] Device 1005 or its various components may be examples of components for performing various aspects of the technology for prioritizing and processing conflicting read commands and write commands for passive devices as described herein. For example, communication manager 1020 may include query reception manager 1025, status message transmission manager 1030, operation manager 1035, or any combination thereof. Communication manager 1020 may be an example of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0232] According to the examples disclosed herein, the communication manager 1020 can support wireless communication at the passive device. The query reception manager 1025 can be configured to or otherwise support a component for receiving a first query associated with a first operation to be performed at the passive device from a first query device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The query reception manager 1025 can be configured to or otherwise support a component for receiving a second query associated with a second operation to be performed at the passive device from a first query device or a second query device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both. The status message sending manager 1030 can be configured to or otherwise support a component for sending a message indicating the status of the first operation, the second operation, or both to the first query device, the second query device, or both. The operation manager 1035 can be configured to or otherwise support a component for performing one of the first operation or the second operation according to the first priority level and the second priority level and based on sending the message.

[0233] Fig.11 A block diagram 1100 of a communication manager 1120 supporting techniques for prioritizing and handling conflicting read and write commands for passive devices according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of the techniques for prioritizing and handling conflicting read and write commands for passive devices as described herein. For example, the communication manager 1120 may include a query reception manager 1125, a status message transmission manager 1130, an operation manager 1135, a control signaling reception manager 1140, a prioritization manager 1145, a signal reception manager 1150, a request reception manager 1155, a message transmission manager 1160, an operation parameter manager 1165, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0234] According to examples as disclosed herein, the communication manager 1120 may support wireless communication at a passive device. The query reception manager 1125 may be configured to or otherwise support a component for receiving a first query associated with a first operation to be performed at a passive device from a first query device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. In some examples, the query reception manager 1125 may be configured to or otherwise support a component for receiving a second query associated with a second operation to be performed at a passive device from a first query device or a second query device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both. The status message sending manager 1130 may be configured to or otherwise support a component for sending a message indicating the status of the first operation, the second operation, or both to the first query device, the second query device, or both. The operation manager 1135 may be configured to or otherwise support a component for performing one of the first operation or the second operation based on the first priority level and the second priority level and sending the message.

[0235] In some examples, the query reception manager 1125 can be configured or otherwise support components for receiving a first priority level via a first query. In some examples, the query reception manager 1125 can be configured or otherwise support components for receiving a second priority level via a second query, wherein sending the message is based on the first priority level, the second priority level, or both. In some examples, the first priority level is based on a first operation including a first write operation. In some examples, the second priority level is based on a second operation including a second read operation.

[0236] In some examples, the priority manager 1145 can be configured to or otherwise support components for prioritizing a first operation over a second read operation based on a first priority level being greater than a second priority level, wherein sending the message is based on the priority ranking, and wherein performing one of the first operation or the second operation includes performing the first operation based on the priority ranking.

[0237] In some examples, the control signaling reception manager 1140 can be configured to or otherwise support components for receiving control signaling from the first querying device, the second querying device, or the additional wireless device, the control signaling indicating a priority configuration that can be used to determine a priority level associated with an operation to be performed at the passive device. In some examples, the prioritization manager 1145 can be configured to or otherwise support components for determining a first priority level, a second priority level, or both based on the priority configuration, wherein sending the message, performing one of the first operation or the second operation, or both, is based on determining the first priority level, the second priority level, or both.

[0238] In some examples, the priority configuration includes one or more rules, one or more conditions, or both for determining a priority level associated with an operation to be performed at the passive device. In some examples, determining the first priority level, the second priority level, or both is based on one or more rules, one or more conditions, or both.

[0239] In some examples, the first priority level is based on a first operation type associated with the first operation. In some examples, the second priority level is based on a second operation type associated with the second operation. In some examples, the second query is received from a second querying device. In some examples, the first priority level is based on a first identifier associated with the first querying device. In some examples, the second priority level is based on a second identifier associated with the second querying device.

[0240] In some examples, the status message sending manager 1130 can be configured or otherwise support components for sending a message to at least a second querying device based on the first priority level being greater than the second priority level, wherein the message includes an indication that the passive device is busy performing the first operation. In some examples, the status message sending manager 1130 can be configured or otherwise support components for sending a message to at least a first querying device based on the first priority level being less than the second priority level, wherein the message includes an indication that the passive device has received a second query for a second operation having a higher priority than the first operation.

[0241] In some examples, the status messaging manager 1130 can be configured to or otherwise support components for sending, via a message, an indication of a first priority level, a second priority level, a first operation type associated with a first operation, a second operation type associated with a second operation, a first identifier associated with a first querying device, a second identifier associated with a second querying device, or any combination thereof.

[0242] In some examples, a second query is received from the first querying device, and the signal reception manager 1150 can be configured or otherwise support components for receiving instructions to cease the first operation and perform a second operation via the second query, wherein the passive device performs the second operation based on the instructions.

[0243] In some examples, the status messaging manager 1130 may be configured to or otherwise support components for sending a set of multiple messages on a periodic basis, the set of multiple messages associated with a queue of operations to be performed by the passive device, the set of multiple messages including messages indicating the status of a first operation, a second operation, or both.

[0244] In some examples, signal reception manager 1150 may be configured or otherwise support components for receiving a set of multiple signals according to a periodicity, wherein sending the set of multiple messages is based on receiving the set of multiple signals.

[0245] In some examples, the message includes an indication that the passive device is busy performing the first operation, and the request reception manager 1155 can be configured to or otherwise support components for receiving a request for an identifier associated with the first querying device from the second querying device and in response to the message. In some examples, the message includes an indication that the passive device is busy performing the first operation, and the message transmission manager 1160 can be configured to or otherwise support components for sending a second message to the second querying device based on receiving the request, the second message indicating the identifier associated with the first querying device.

[0246] In some examples, the first operation may be performed at a first time, and operations manager 1135 may be configured or otherwise support components for performing the second operation at a second time after the first time based on the second priority level being less than the first priority level.

[0247] In some examples, to support performing one of the first write operation or the second write operation, operating parameter manager 1165 can be configured or otherwise support components for adjusting one or more operating parameters at the passive device.

[0248] In some examples, to support performing one of the first read operation or the second read operation, messaging manager 1160 may be configured or otherwise support components for sending a data message to the first querying device, the second querying device, or both.

[0249] In some examples, the passive device includes an RFID tag, a passive component of a wireless device, or both. In some examples, the first querying device, the second querying device, or both include a UE, a network entity, or both.

[0250] Fig.12 A diagram of a system 1200 including a device 1205 supporting techniques for prioritizing and handling conflicting read and write commands for a passive device according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a passive device as described herein or may include components of these devices. The device 1205 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1205 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, and a processor 1240. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245).

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

[0252] In some cases, the device 1205 may include a single antenna 1225. However, in some other cases, the device 1205 may have more than one antenna 1225 that may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1215 may communicate bidirectionally via one or more antennas 1225, a wired or wireless link, as described herein. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1215 may also include a modem to modulate a packet, provide the modulated packet to one or more antennas 1225 for transmission, and demodulate the packet received from the one or more antennas 1225. The transceiver 1215 or the transceiver 1215 and the one or more antennas 1225 may be examples of transmitters 915, transmitters 1015, receivers 910, receivers 1010, or any combination thereof or components thereof as described herein.

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

[0254] Processor 1240 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) to enable device 1205 to perform various functions (e.g., functions or tasks that support techniques for prioritizing and processing conflicting read operations and write operations for passive devices). For example, device 1205 or a component of device 1205 may include processor 1240 and memory 1230 coupled to or coupled to processor 1240, and processor 1240 and memory 1230 are configured to perform various functions described herein.

[0255] According to the examples disclosed herein, the communication manager 1220 can support wireless communication at the passive device. For example, the communication manager 1220 can be configured to or otherwise support a component for receiving a first query associated with a first operation to be performed at the passive device from a first query device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The communication manager 1220 can be configured to or otherwise support a component for receiving a second query associated with a second operation to be performed at the passive device from a first query device or a second query device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both. The communication manager 1220 can be configured to or otherwise support a component for sending a message indicating the status of the first operation, the second operation, or both to the first query device, the second query device, or both. The communication manager 1220 can be configured to or otherwise support a component for performing one of the first operation or the second operation according to the first priority level and the second priority level and based on sending the message.

[0256] By including or configuring a communication manager 1220 according to an example as described herein, the device 1205 can support a technique that enables a passive device (such as an RFID tag) to determine the relative priority of a read operation and a write operation to be performed at the passive device, thereby improving the speed and efficiency with which the passive device can perform the read operation and the write operation. Thus, the techniques described herein can improve the efficiency and latency of services and applications (such as location tracking services) associated with passive devices within a wireless communication system. In addition, the techniques described herein can enable an inquiry device to quickly and efficiently determine the state of a corresponding passive device (e.g., whether each passive device is available or busy), thereby facilitating the ability of an inquiry device to identify passive devices that can be used for wireless communication.

[0257] In some examples, the communication manager 1220 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1215, one or more antennas 1225, or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 can be supported or performed by the processor 1240, the memory 1230, the code 1235, or any combination thereof. For example, the code 1235 can include instructions executable by the processor 1240 to cause the device 1205 to perform various aspects of the techniques for prioritizing and handling conflicting read operations and write operations for passive devices as described herein, or the processor 1240 and the memory 1230 can be otherwise configured to perform or support such operations.

[0258] Fig.13 A block diagram 1300 of a device 1305 supporting techniques for prioritizing and handling conflicting read and write commands for a passive device according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of aspects of a querying device (e.g., UE 115, network entity 105) as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0261] The communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the techniques for prioritizing and handling conflicting read and write commands for passive devices as described herein. For example, the communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

[0264] In some examples, communication manager 1320 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 can receive information from receiver 1310, transmit information to transmitter 1315, or integrate with receiver 1310, transmitter 1315, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0265] According to examples as disclosed herein, the communication manager 1320 can support wireless communications at the querying device. For example, the communication manager 1320 can be configured to or otherwise support components for sending a first query associated with a first operation to be performed at the passive device to the passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The communication manager 1320 can be configured to or otherwise support components for receiving a message indicating a status of the first operation, a second operation associated with a second priority level, or both from the passive device based on the first query, wherein the status is based on the first priority level, the second priority level, or both, and wherein the second operation includes a second write operation, a second read operation, or both.

[0266] By including or configuring a communication manager 1320 according to the examples described herein, the device 1305 (e.g., a processor that controls or otherwise couples to the receiver 1310, the transmitter 1315, the communication manager 1320, or a combination thereof) can support techniques that enable a passive device (such as an RFID tag) to determine the relative priority of read operations and write operations to be performed at the passive device, thereby improving the speed and efficiency with which the passive device can perform read operations and write operations. As a result, the techniques described herein can improve the efficiency and latency of services and applications (such as location tracking services) associated with passive devices within a wireless communication system. In addition, the techniques described herein can enable an inquiry device to quickly and efficiently determine the status of a corresponding passive device (e.g., whether each passive device is available or busy), thereby facilitating the ability of the inquiry device to identify passive devices that can be used for wireless communication.

[0267] Fig.14 A block diagram 1400 of a device 1405 supporting techniques for prioritizing and handling conflicting read and write commands for a passive device according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of aspects of the device 1305 or a querying device (e.g., a UE 115, a network entity 105) as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. The device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0270] Device 1405 or its various components may be examples of components for performing various aspects of the technology for prioritizing and processing conflicting read commands and write commands for passive devices as described herein. For example, communication manager 1420 may include query transmission manager 1425, status message reception manager 1430, or any combination thereof. Communication manager 1420 may be an example of various aspects of communication manager 1320 as described herein. In some examples, communication manager 1420 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 1410, transmitter 1415, or both. For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or integrate with receiver 1410, transmitter 1415, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0271] According to examples as disclosed herein, the communication manager 1420 can support wireless communications at the querying device. The query sending manager 1425 can be configured to or otherwise support components for sending a first query associated with a first operation to be performed at the passive device to the passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The status message receiving manager 1430 can be configured to or otherwise support components for receiving a message indicating a status of the first operation, a second operation associated with a second priority level, or both from the passive device based on the first query, wherein the status is based on the first priority level, the second priority level, or both, and wherein the second operation includes a second write operation, a second read operation, or both.

[0272] Fig.15 A block diagram 1500 of a communication manager 1520 supporting techniques for prioritizing and handling conflicting read commands and write commands for passive devices according to one or more aspects of the present disclosure is shown. The communication manager 1520 can be an example of aspects of the communication manager 1320, the communication manager 1420, or both as described herein. The communication manager 1520 or its various components can be examples of components for performing various aspects of the techniques for prioritizing and handling conflicting read commands and write commands for passive devices as described herein. For example, the communication manager 1520 can include a query transmission manager 1525, a status message reception manager 1530, a message reception manager 1535, a request transmission manager 1540, a prioritization manager 1545, a control signaling transmission manager 1550, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0273] According to examples as disclosed herein, the communication manager 1520 can support wireless communications at the querying device. The query sending manager 1525 can be configured to or otherwise support components for sending a first query associated with a first operation to be performed at the passive device to the passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The status message receiving manager 1530 can be configured to or otherwise support components for receiving a message indicating a status of the first operation, a second operation associated with a second priority level, or both from the passive device based on the first query, wherein the status is based on the first priority level, the second priority level, or both, and wherein the second operation includes a second write operation, a second read operation, or both.

[0274] In some examples, the message receiving manager 1535 may be configured to or otherwise support a component for receiving a second message from the passive device, the second message including an indicator associated with the second querying device and a request to stop an operation initiated by the second querying device to be performed at the passive device. In some examples, the request sending manager 1540 may be configured to or otherwise support a component for sending a third message to the second querying device based on the second message, the third message indicating a request to cause the second querying device to stop an operation initiated by the second querying device.

[0275] In some examples, query sending manager 1525 can be configured or otherwise support components for sending a first priority level via a first query, where receiving the message is based on the first priority level.

[0276] In some examples, wherein the first priority level is based on a first operation comprising a first write operation or a first read operation, and wherein the second priority level is based on a second operation comprising a second write operation or a second read operation. In some examples, wherein the first priority level is based on a first operation type associated with the first operation, and wherein the second priority level is based on a second operation type associated with the second operation.

[0277] In some examples, the control signaling sending manager 1550 can be configured to or otherwise support components for sending control signaling to a passive device, the control signaling indicating a priority configuration that can be used to determine a priority level associated with an operation to be performed at the passive device, wherein receiving the message is based on the priority configuration.

[0278] In some examples, the status message reception manager 1530 may be configured to or otherwise support components for receiving a message from a passive device based on the first priority level being less than the second priority level, wherein the message includes an indication that the second operation has a higher priority than the first operation. In some examples, the status message reception manager 1530 may be configured to or otherwise support components for receiving a message from a passive device based on the first priority level being less than the second priority level, wherein the message includes an indication that the second operation has a higher priority than the first operation, wherein the second operation is associated with a second querying device.

[0279] In some examples, request sending manager 1540 may be configured or otherwise support components for sending a request for an identifier associated with a second querying device to the passive device in response to the message. In some examples, message receiving manager 1535 may be configured or otherwise support components for receiving a second message from the passive device based on sending the request, the second message indicating an identifier associated with the second querying device. In some examples, request sending manager 1540 may be configured or otherwise support components for sending a third message to the second querying device based on receiving the second message, the third message including a second request for the second querying device to stop the second operation.

[0280] In some examples, the query sending manager 1525 can be configured or otherwise support components for sending a second query associated with a second operation to the passive device, where the second query includes instructions to cause the passive device to cease the first operation and perform the second operation.

[0281] Fig.16 A diagram of a system 1600 including a device 1605 supporting techniques for prioritizing and handling conflicting read and write commands for passive devices according to one or more aspects of the present disclosure is shown. The device 1605 may be an example of a device 1305, a device 1405, or a querying device (e.g., a UE 115, a network entity 105) as described herein or include a component of these devices. The device 1605 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1605 may include components that support output and obtain communications, such as a communication manager 1620, a transceiver 1610, an antenna 1615, a memory 1625, a code 1630, and a processor 1635. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1640).

[0282] The transceiver 1610 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1610 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1610 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1605 may include one or more antennas 1615, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1610 may also include a modem to modulate a signal, provide a modulated signal for sending (e.g., via one or more antennas 1615, via a wired transmitter), receive a modulated signal (e.g., from one or more antennas 1615, from a wired receiver), and demodulate the signal. The transceiver 1610 or the transceiver 1610 and one or more antennas 1615 or wired interfaces (where applicable) may be examples of transmitter 1315, transmitter 1415, receiver 1310, receiver 1410, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

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

[0284] Processor 1635 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, processor 1635 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1635. Processor 1635 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1625) to enable device 1605 to perform various functions (e.g., functions or tasks that support techniques for prioritizing and processing conflicting read operations and write operations for passive devices). For example, device 1605 or a component of device 1605 may include processor 1635 and memory 1625 coupled to processor 1635, and processor 1635 and memory 1625 are configured to perform various functions described herein. Processor 1635 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software, such as an operating system, virtual machine, or container instance) that can host functionality (e.g., by executing code 1630) to perform the functions of device 1605.

[0285] In some examples, bus 1640 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1640 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1605 or between different components of device 1605 that may be co-located or may be located in different locations (e.g., where device 1605 may refer to a system in which one or more of communication manager 1620, transceiver 1610, memory 1625, code 1630, and processor 1635 may be located in one of the different components or divided between the different components).

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

[0287] According to examples as disclosed herein, the communication manager 1620 can support wireless communications at the querying device. For example, the communication manager 1620 can be configured to or otherwise support components for sending a first query associated with a first operation to be performed at the passive device to the passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The communication manager 1620 can be configured to or otherwise support components for receiving a message from the passive device indicating a status of the first operation, a second operation associated with a second priority level, or both based on the first query, wherein the status is based on the first priority level, the second priority level, or both, and wherein the second operation includes a second write operation, a second read operation, or both.

[0288] By including or configuring the communication manager 1620 according to the example described herein, the device 1605 can support the technology that enables the passive device (such as RFID tag) to determine the relative priority of the read operation and the write operation to be performed at the passive device, thereby improving the speed and efficiency of the passive device to perform the read operation and the write operation. Thus, the technology described herein can improve the efficiency and delay of the services and applications (such as location tracking services) associated with the passive devices in the wireless communication system. In addition, the technology described herein can enable the query device to quickly and efficiently determine the state of the corresponding passive device (such as whether each passive device is available or busy), thereby promoting the ability of the query device to identify the passive devices that can be used for wireless communication.

[0289] In some examples, the communication manager 1620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1610, one or more antennas 1615 (e.g., where applicable), or any combination thereof. Although the communication manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1620 can be supported or performed by the processor 1635, the memory 1625, the code 1630, the transceiver 1610, or any combination thereof. For example, the code 1630 may include instructions executable by the processor 1635 to cause the device 1605 to perform various aspects of the techniques for prioritizing and handling conflicting read operations and write operations for passive devices as described herein, or the processor 1635 and the memory 1625 may be otherwise configured to perform or support such operations.

[0290] Fig.17 A method 1700 is shown that illustrates a technique for supporting prioritization and handling of conflicting read commands and write commands for a passive device according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE as described in reference to Figures 1 to 12 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0291] At 1705, the method may include receiving, from a first querying device, a first query associated with a first operation to be performed at a passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.11 The described query is received by the manager 1125 for execution.

[0292] At 1710, the method may include receiving a second query associated with a second operation to be performed at the passive device from the first querying device or the second querying device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.11 The described query is received by the manager 1125 for execution.

[0293] At 1715, the method may include sending a message indicating a status of the first operation, the second operation, or both to the first querying device, the second querying device, or both. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.11 The described status message is sent to manager 1130 for execution.

[0294] At 1720, the method may include performing one of the first operation or the second operation based on the first priority level and the second priority level and based on sending the message. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig.11 The described operations are performed by the operation manager 1135.

[0295] Fig.18 A method 1800 is shown that illustrates a technique for supporting prioritization and handling of conflicting read commands and write commands for a passive device according to one or more aspects of the present disclosure. The operations of the method 1800 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 12 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0296] At 1805, the method may include receiving, from a first querying device, a first query associated with a first operation to be performed at a passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.11 The described query is received by the manager 1125 for execution.

[0297] At 1810, the method may include receiving a first priority level via a first query. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.11 The described query is received by the manager 1125 for execution.

[0298] At 1815, the method may include receiving a second query associated with a second operation to be performed at the passive device from the first querying device or the second querying device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.11 The described query is received by the manager 1125 for execution.

[0299] At 1820, the method may include receiving a second priority level via a second query. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described in reference to Fig.11 The described query is received by the manager 1125 for execution.

[0300] At 1825, the method may include sending a message indicating a status of the first operation, the second operation, or both to the first querying device, the second querying device, or both, wherein sending the message is based on the first priority level, the second priority level, or both. The operations of 1825 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1825 may be performed as described in reference to Fig.11 The described status message is sent to manager 1130 for execution.

[0301] At 1830, the method may include performing one of the first operation or the second operation based on the first priority level and the second priority level and based on sending the message. The operations of 1830 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1830 may be performed as described in reference to Fig.11 The described operations are performed by the operation manager 1135.

[0302] Fig.19 A method 1900 is shown that illustrates a technique for supporting prioritization and handling of conflicting read commands and write commands for a passive device according to one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 12 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0303] At 1905, the method may include receiving control signaling from the first querying device, the second querying device, or the additional wireless device, the control signaling indicating a priority configuration that can be used to determine a priority level associated with an operation to be performed at the passive device. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.11 The control signaling reception manager 1140 described herein is executed.

[0304] At 1910, the method may include receiving, from a first querying device, a first query associated with a first operation to be performed at a passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.11 The described query is received by the manager 1125 for execution.

[0305] At 1915, the method may include receiving a second query associated with a second operation to be performed at the passive device from the first querying device or the second querying device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.11 The described query is received by the manager 1125 for execution.

[0306] At 1920, the method may include determining a first priority level, a second priority level, or both according to the priority configuration. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Fig.11 The described prioritization manager 1145 is executed.

[0307] At 1925, the method may include sending a message indicating a status of the first operation, the second operation, or both to the first querying device, the second querying device, or both. The operations of 1925 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1925 may be performed as described in reference to Fig.11 The described status message is sent to manager 1130 for execution.

[0308] At 1930, the method may include performing one of a first operation or a second operation based on the first priority level and the second priority level and based on sending the message, wherein sending the message, performing one of the first operation or the second operation, or both, is based on determining the first priority level, the second priority level, or both. The operations of 1930 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1930 may be performed as described in reference to Fig.11 The described operations are performed by the operation manager 1135.

[0309] Fig. 20 A method 2000 is shown that illustrates a technique for supporting prioritization and handling of conflicting read commands and write commands for a passive device in accordance with one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 8 as well as Figures 13 to 16 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0310] At 2005, the method may include sending a first query associated with a first operation to be performed at the passive device to the passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.15 The described query is sent to the manager 1525 for execution.

[0311] At 2010, the method may include receiving a message from the passive device indicating a status of a first operation, a second operation associated with a second priority level, or both based on the first query, wherein the status is based on the first priority level, the second priority level, or both, and wherein the second operation includes a second write operation, a second read operation, or both. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by as described in reference to Fig.15 The described status message receiving manager 1530 is executed.

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

[0313] Aspect 1: A method for wireless communication at a passive device, comprising: receiving a first query associated with a first operation to be performed at the passive device from a first querying device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both; receiving a second query associated with a second operation to be performed at the passive device from the first querying device or a second querying device, wherein the second operation is associated with a second priority level and includes a second write operation, a second read operation, or both; sending a message indicating a status of the first operation, the second operation, or both to the first querying device, the second querying device, or both; and performing one of the first operation or the second operation according to the first priority level and the second priority level and at least partially based on sending the message.

[0314] Aspect 2: The method according to Aspect 1 also includes: receiving the first priority level via the first query; and receiving the second priority level via the second query, wherein sending the message is at least partially based on the first priority level, the second priority level, or both.

[0315] Aspect 3: A method according to any one of aspects 1 to 2, wherein the first priority level is based at least in part on the first operation including the first write operation, and the second priority level is based at least in part on the second operation including the second read operation.

[0316] Aspect 4: The method according to Aspect 3 also includes: prioritizing the first operation over the second read operation based at least in part on the first priority level being greater than the second priority level, wherein sending the message is based at least in part on priority sorting, and wherein performing one of the first operation or the second operation includes performing the first operation based at least in part on the priority sorting.

[0317] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: receiving control signaling from the first query device, the second query device or an additional wireless device, the control signaling indicating a priority configuration that can be used to determine a priority level associated with an operation to be performed at the passive device; and determining the first priority level, the second priority level, or both based on the priority configuration, wherein sending the message, performing one or both of the first operation or the second operation is at least partially based on determining the first priority level, the second priority level, or both.

[0318] Aspect 6: A method according to Aspect 5, wherein the priority configuration includes one or more rules, one or more conditions, or both for determining a priority level associated with an operation to be performed at the passive device, and determining the first priority level, the second priority level, or both is at least partially based on the one or more rules, the one or more conditions, or both.

[0319] Aspect 7: A method according to any one of aspects 1 to 6, wherein the first priority level is based at least in part on a first operation type associated with the first operation, and the second priority level is based at least in part on a second operation type associated with the second operation.

[0320] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the second query is received from the second query device, and the first priority level is at least partially based on a first identifier associated with the first query device, and the second priority level is at least partially based on a second identifier associated with the second query device.

[0321] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: sending the message to at least the second querying device based at least in part on the first priority level being greater than the second priority level, wherein the message includes an indication that the passive device is busy performing the first operation.

[0322] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: sending the message to at least the first query device based at least in part on the first priority level being less than the second priority level, wherein the message includes an indication that the passive device has received the second query for the second operation having a higher priority than the first operation.

[0323] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: sending an indication of the first priority level, the second priority level, the first operation type associated with the first operation, the second operation type associated with the second operation, the first identifier associated with the first query device, the second identifier associated with the second query device, or any combination thereof via the message.

[0324] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the second query is received from the first query device, and the method further includes: receiving an instruction to stop the first operation and perform the second operation via the second query, wherein the passive device performs the second operation at least in part based on the instruction.

[0325] Aspect 13: The method according to any one of Aspects 1 to 12 further includes: sending multiple messages according to a periodicity, the multiple messages being associated with a queue of operations to be performed by the passive device, the multiple messages including the message indicating the status of the first operation, the second operation, or both.

[0326] Aspect 14: The method according to aspect 13 further includes: receiving a plurality of signals according to the periodicity, wherein sending the plurality of messages is based at least in part on receiving the plurality of signals.

[0327] Aspect 15: A method according to any one of Aspects 1 to 14, wherein the message includes an indication that the passive device is busy performing the first operation, the method further comprising: receiving a request for an identifier associated with the first query device from the second query device and in response to the message; and sending a second message to the second query device based at least in part on receiving the request, the second message indicating the identifier associated with the first query device.

[0328] Aspect 16: A method according to any one of Aspects 1 to 15, wherein performing one of the first operation or the second operation includes performing the first operation at a first time, and the method further includes: performing the second operation at a second time after the first time based at least in part on the second priority level being less than the first priority level.

[0329] Aspect 17: A method according to any one of Aspects 1 to 16, wherein performing one of the first operation or the second operation includes performing one of the first write operation or the second write operation, wherein performing one of the first write operation or the second write operation includes: adjusting one or more operating parameters at the passive device.

[0330] Aspect 18: A method according to any one of Aspects 1 to 17, wherein performing one of the first operation or the second operation includes performing one of the first read operation or the second read operation, wherein performing one of the first read operation or the second read operation includes: sending a data message to the first query device, the second query device, or both.

[0331] Aspect 19: The method according to any one of aspects 1 to 18, wherein the passive device comprises a radio frequency identifier tag, a passive component of a wireless device, or both, and the first querying device, the second querying device, or both comprise a UE, a network entity, or both.

[0332] Aspect 20: A method for wireless communication at an inquiry device, comprising: sending a first query associated with a first operation to be performed at the passive device to a passive device, wherein the first operation is associated with a first priority level and includes a first write operation, a first read operation, or both; and receiving a message from the passive device indicating a status of the first operation, a second operation associated with a second priority level, or both based at least in part on the first query, wherein the status is based at least in part on the first priority level, the second priority level, or both, and wherein the second operation includes a second write operation, a second read operation, or both.

[0333] Aspect 21: The method according to Aspect 20 further includes: receiving a second message from the passive device, the second message including an indicator associated with a second query device and a request to stop an operation initiated by the second query device to be performed at the passive device; and sending a third message to the second query device based at least in part on the second message, the third message indicating the request to cause the second query device to stop the operation initiated by the second query device.

[0334] Aspect 22: The method according to any one of aspects 20 to 21, further comprising: sending the first priority level via the first query, wherein receiving the message is based at least in part on the first priority level.

[0335] Aspect 23: A method according to any one of Aspects 20 to 22, wherein the first priority level is at least partially based on the first operation including the first write operation or the first read operation, and wherein the second priority level is at least partially based on the second operation including the second write operation or the second read operation, or wherein the first priority level is at least partially based on a first operation type associated with the first operation, and wherein the second priority level is at least partially based on a second operation type associated with the second operation.

[0336] Aspect 24: The method according to any one of Aspects 20 to 23 further includes: sending control signaling to the passive device, the control signaling indicating a priority configuration that can be used to determine a priority level associated with an operation to be performed at the passive device, wherein receiving the message is at least partially based on the priority configuration.

[0337] Aspect 25: The method according to any one of Aspects 20 to 24 further includes: receiving the message from the passive device at least in part based on the first priority level being less than the second priority level, wherein the message includes an indication that the second operation has a higher priority than the first operation.

[0338] Aspect 26: The method according to any one of Aspects 20 to 25 further includes: receiving the message from the passive device at least in part based on the first priority level being less than the second priority level, wherein the message includes an indication that the second operation has a higher priority than the first operation, wherein the second operation is associated with a second querying device.

[0339] Aspect 27: The method according to Aspect 26 further includes: sending a request for an identifier associated with the second query device to the passive device and in response to the message; receiving a second message from the passive device based at least in part on sending the request, the second message indicating the identifier associated with the second query device; and sending a third message to the second query device based at least in part on receiving the second message, the third message including a second request for the second query device to stop the second operation.

[0340] Aspect 28: The method according to any one of aspects 20 to 27 further includes: sending a second query associated with the second operation to the passive device, wherein the second query includes an instruction for the passive device to stop the first operation and perform the second operation.

[0341] Aspect 29: An apparatus for wireless communication at a passive device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 19.

[0342] Aspect 30: An apparatus for wireless communication at a passive device, comprising: at least one component for performing the method according to any one of aspects 1 to 19.

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

[0344] Aspect 32: An apparatus for wireless communication at an inquiry device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 20 to 28.

[0345] Aspect 33: An apparatus for wireless communication at a querying device, comprising: at least one component for performing a method according to any one of aspects 20 to 28.

[0346] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at an inquiry device, the code comprising instructions executable by a processor to perform the method according to any one of aspects 20 to 28.

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

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

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

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

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

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

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

[0354] The terms "determine" or "determining" encompass a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Additionally, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

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

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

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

Claims

1. An apparatus for wireless communication at a passive device, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, from a first querying device, a first query associated with a first operation to be performed at the passive device, wherein the first operation is associated with a first priority level and comprises a first write operation, a first read operation, or both; receiving, from the first querying device or the second querying device, a second query associated with a second operation to be performed at the passive device, wherein the second operation is associated with a second priority level and comprises a second write operation, a second read operation, or both; sending a message indicating a status of the first operation, the second operation, or both to the first querying device, the second querying device, or both; as well as One of the first operation or the second operation is performed based at least in part on sending the message according to the first priority level and the second priority level.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: receiving the first priority level via the first query; and The second priority level is received via the second query, wherein sending the message is based at least in part on the first priority level, the second priority level, or both.

3. The apparatus of claim 1, wherein the first priority level is based at least in part on the first operation including the first write operation, and wherein the second priority level is based at least in part on the second operation including the second read operation.

4. The apparatus of claim 3, wherein the instructions are further executable by the processor to cause the apparatus to: Prioritize the first operation over the second read operation based at least in part on the first priority level being greater than the second priority level, wherein sending the message is based at least in part on a priority ranking, and wherein performing one of the first operation or the second operation includes performing the first operation based at least in part on the priority ranking.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving control signaling from the first querying device, the second querying device, or an additional wireless device, the control signaling indicating a priority configuration that can be used to determine a priority level associated with an operation to be performed at the passive device; and The first priority level, the second priority level, or both are determined according to the priority configuration, wherein sending the message, performing one or both of the first operation or the second operation is based at least in part on determining the first priority level, the second priority level, or both.

6. An apparatus according to claim 5, wherein the priority configuration includes one or more rules, one or more conditions, or both for determining a priority level associated with an operation to be performed at the passive device, wherein determining the first priority level, the second priority level, or both is at least partially based on the one or more rules, the one or more conditions, or both.

7. The apparatus of claim 1, wherein the first priority level is based at least in part on a first operation type associated with the first operation, and wherein the second priority level is based at least in part on a second operation type associated with the second operation.

8. The apparatus of claim 1 , wherein the second query is received from the second querying device, and wherein the first priority level is based at least in part on a first identifier associated with the first querying device, and wherein the second priority level is based at least in part on a second identifier associated with the second querying device.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The message is sent to at least the second querying device based at least in part on the first priority level being greater than the second priority level, wherein the message includes an indication that the passive device is busy performing the first operation.

10. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The message is sent to at least the first querying device based at least in part on the first priority level being less than the second priority level, wherein the message includes an indication that the passive device has received the second query for the second operation having a higher priority than the first operation.

11. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: An indication of the first priority level, the second priority level, a first operation type associated with the first operation, a second operation type associated with the second operation, a first identifier associated with the first querying device, a second identifier associated with the second querying device, or any combination thereof is sent via the message.

12. The apparatus of claim 1, wherein the second query is received from the first querying device, and the instructions are further executable by the processor to cause the apparatus to: An instruction to cease the first operation and to perform the second operation is received via the second query, wherein the passive device performs the second operation based at least in part on the instruction.

13. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A plurality of messages are sent according to a periodicity, the plurality of messages associated with a queue of operations to be performed by the passive device, the plurality of messages including the message indicating the status of the first operation, the second operation, or both.

14. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: A plurality of signals are received according to the periodicity, wherein sending the plurality of messages is based at least in part on receiving the plurality of signals.

15. The apparatus of claim 1, wherein the message includes an indication that the passive device is busy performing the first operation, and the instructions are further executable by the processor to cause the apparatus to: receiving, from the second querying device and in response to the message, a request for an identifier associated with the first querying device; and Based at least in part on receiving the request, a second message is sent to the second querying device, the second message indicating the identifier associated with the first querying device.

16. The device of claim 1, wherein performing one of the first operation or the second operation comprises performing the first operation at a first time, and the instructions are further executable by the processor to cause the device to: The second operation is performed at a second time after the first time based at least in part on the second priority level being less than the first priority level.

17. The device of claim 1, wherein the instructions for performing one of the first write operation or the second write operation are executable by the processor to cause the device to: One or more operating parameters at the passive device are adjusted.

18. The device of claim 1, wherein the instructions for performing one of the first read operation or the second read operation are executable by the processor to cause the device to: A data message is sent to the first querying device, the second querying device, or both.

19. The apparatus of claim 1, wherein the passive device comprises a radio frequency identifier tag, a passive component of a wireless device, or both, and wherein the first querying device, the second querying device, or both comprise a user equipment (UE), a network entity, or both.

20. An apparatus for wireless communication at a query device, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending a first query associated with a first operation to be performed at the passive device to a passive device, wherein the first operation is associated with a first priority level and comprises a first write operation, a first read operation, or both; and Receiving a message from the passive device indicating a status of the first operation, a second operation associated with a second priority level, or both based at least in part on the first query, wherein the status is based at least in part on the first priority level, the second priority level, or both, and wherein the second operation comprises a second write operation, a second read operation, or both.

21. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a second message from the passive device, the second message including an indicator associated with a second inquiring device and a request to cease an operation initiated by the second inquiring device to be performed at the passive device; and A third message is sent to the second querying device based at least in part on the second message, the third message indicating the request for the second querying device to cease the operation initiated by the second querying device.

22. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: The first priority level is sent via the first query, wherein receiving the message is based at least in part on the first priority level.

23. The device according to claim 20, wherein the first priority level is based at least in part on the first operation comprising the first write operation or the first read operation, and wherein the second priority level is based at least in part on the second operation comprising the second write operation or the second read operation, or Wherein the first priority level is based at least in part on a first operation type associated with the first operation, and wherein the second priority level is based at least in part on a second operation type associated with the second operation.

24. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling is sent to the passive device, the control signaling indicating a priority configuration usable to determine a priority level associated with an operation to be performed at the passive device, wherein receiving the message is based at least in part on the priority configuration.

25. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: The message is received from the passive device based at least in part on the first priority level being less than the second priority level, wherein the message includes an indication that the second operation has a higher priority than the first operation.

26. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: The message is received from the passive device based at least in part on the first priority level being less than the second priority level, wherein the message includes an indication that the second operation has a higher priority than the first operation, wherein the second operation is associated with a second querying device.

27. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: sending, to the passive device and in response to the message, a request for an identifier associated with the second inquiring device; receiving a second message from the passive device based at least in part on sending the request, the second message indicating the identifier associated with the second querying device; and sending a third message to the second querying device based at least in part on receiving the second message, the third message including a second request for the second querying device to cease the second operation.

28. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: A second query associated with the second operation is sent to the passive device, wherein the second query includes instructions for the passive device to cease the first operation and perform the second operation.

29. A method for wireless communication at a passive device, the method comprising: receiving, from a first querying device, a first query associated with a first operation to be performed at the passive device, wherein the first operation is associated with a first priority level and comprises a first write operation, a first read operation, or both; receiving, from the first querying device or the second querying device, a second query associated with a second operation to be performed at the passive device, wherein the second operation is associated with a second priority level and comprises a second write operation, a second read operation, or both; sending a message indicating a status of the first operation, the second operation, or both to the first querying device, the second querying device, or both; as well as One of the first operation or the second operation is performed based at least in part on sending the message according to the first priority level and the second priority level.

30. A method for wireless communication at an inquiry device, the method comprising: sending a first query associated with a first operation to be performed at the passive device to a passive device, wherein the first operation is associated with a first priority level and comprises a first write operation, a first read operation, or both; and Receiving a message from the passive device indicating a status of the first operation, a second operation associated with a second priority level, or both based at least in part on the first query, wherein the status is based at least in part on the first priority level, the second priority level, or both, and wherein the second operation comprises a second write operation, a second read operation, or both.

Images