Techniques for environmental internet of things device access and data reporting

Abstract

Methods, systems, and devices for wireless communication are described. The techniques described herein provide query and response techniques for AIoT device access and data reporting. The reader wireless device may send a first query message for powering on one or more AIoT devices. The AIoT device harvesting sufficient energy from the first query message may send a first response message to the reader wireless device. The reader wireless device may send a second query message indicating the resource allocation to the AIoT device. The AIoT device may send a second response message indicating the AIoT device identifier and the data to the reader wireless device using the resources of the resource allocation.

Description

Technical Field

[0001] The following content relates to wireless communication, including technologies for accessing and reporting data for environmental IoT devices. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described technology relates to improved methods, systems, devices, and apparatuses supporting technologies for access and data reporting of Ambient Internet of Things (AIoT) devices. For example, the described technology provides query and response techniques for AIoT device access and data reporting. A reader wireless device can send a first query message to power on one or more AIoT devices. An AIoT device that has collected sufficient power from the first query message can send a first response message to the reader wireless device. The reader wireless device can send a second query message to the AIoT device indicating resource allocation. The AIoT device can use the allocated resources to send a second response message to the reader wireless device indicating the AIoT device identifier and data.

[0004] A method for wireless communication by a reader wireless device is described. The method may include: sending a first query message associated with powering on one or more Ambient Internet of Things (AIoT) devices within the coverage area of ​​the reader wireless device; receiving a first response message from a first AIoT device among the one or more AIoT devices, indicating a preamble for AIoT device access, based on sending the first query message; sending a second query message to the first AIoT device, indicating resource allocation, in response to receiving the first response message; and receiving a second response message from the first AIoT device, indicating an AIoT device identifier and AIoT device data, based on sending the second query message, wherein the second response message is received on a resource corresponding to the resource allocation.

[0005] A reader wireless device for wireless communication is described. The reader wireless device may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the reader wireless device to: send a first query message associated with powering on one or more Ambient Internet of Things (AIoT) devices within the coverage area of ​​the reader wireless device; receive a first response message from a first AIoT device among the one or more AIoT devices indicating a preamble for AIoT device access based on sending the first query message; send a second query message to the first AIoT device indicating resource allocation in response to receiving the first response message; and receive a second response message from the first AIoT device indicating an AIoT device identifier and AIoT device data based on sending the second query message, wherein the second response message is received on a resource corresponding to the resource allocation.

[0006] Another reader wireless device for wireless communication is described. The reader wireless device may include: components for transmitting a first query message associated with powering on one or more Ambient Internet of Things (AIoT) devices within the coverage area of ​​the reader wireless device; components for receiving a first response message from a first AIoT device among the one or more AIoT devices, indicating a preamble for AIoT device access, based on transmitting the first query message; components for transmitting a second query message to the first AIoT device, indicating resource allocation, in response to receiving the first response message; and components for receiving a second response message from the first AIoT device, indicating an AIoT device identifier and AIoT device data, based on transmitting the second query message, wherein the second response message is received on a resource corresponding to the resource allocation.

[0007] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: send a first query message associated with powering on one or more Ambient Internet of Things (AIoT) devices within the coverage area of ​​a reader wireless device; receive a first response message from a first AIoT device among the one or more AIoT devices, indicating a preamble for AIoT device access, based on sending the first query message; send a second query message to the first AIoT device, indicating resource allocation, in response to receiving the first response message; and receive a second response message from the first AIoT device, indicating an AIoT device identifier and AIoT device data, based on sending the second query message, wherein the second response message is received on a resource corresponding to the resource allocation.

[0008] The methods described herein, reader wireless devices, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for receiving a third query message from a network entity that instructs the reader wireless device to send a first query message.

[0009] In some examples of the methods described herein, reader wireless devices, and non-transitory computer-readable media, the third query message includes resource configurations for the reader wireless device to communicate with one or more AIoT devices.

[0010] The methods described herein, reader wireless devices, and some examples of nontransitory computer-readable media may also include features, components, or instructions for sending AIoT device data to network entities.

[0011] The methods described herein, some examples of reader wireless devices and nontransitory computer-readable media may also include operations, features, components or instructions for retransmitting a second query message to a first AIoT device based on the reader wireless device's failure to receive a second response message.

[0012] The methods described herein, reader wireless devices, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for retransmitting a second query message to a first AIoT device after a defined duration.

[0013] In some examples of the methods described herein, reader wireless devices, and nontransitory computer-readable media, the second response message may also include indications of the category of the first AIoT device, the capabilities of the first AIoT device, the energy state of the AIoT device, data requests, or combinations thereof.

[0014] The methods described herein, reader wireless devices, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for sending a fourth query message to a first AIoT device in response to receiving a second response message, the fourth query message being partially based on indication information to indicate a second resource allocation.

[0015] In some examples of the methods described herein, reader wireless devices, and nontransitory computer-readable media, resource allocation can be based on contention-based resources or contention-free resources.

[0016] The methods described herein, reader wireless devices, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for: determining the number of AIoT devices within the coverage area of ​​the reader wireless device in response to receiving a quantity first response message from one or more AIoT devices; and determining resource allocation based on the number of AIoT devices.

[0017] In some examples of the methods, reader wireless devices, and nontransitory computer-readable media described herein, the preamble indicates the category of the first AIoT device, the capabilities of the first AIoT device, data requirements, or a combination thereof.

[0018] In some examples of the methods, reader wireless devices, and nontransitory computer-readable media described herein, the first response message may be one of a set of predefined preamble messages, and each predefined preamble message in the set indicates the category of the first AIoT device, the capabilities of the first AIoT device, data requirements, or a combination thereof.

[0019] In some examples of the methods described herein, reader wireless devices, and non-transitory computer-readable media, the first query message may be a wake-up signaling.

[0020] A method for wireless communication by an Ambient Internet of Things (AIoT) wireless device is described. The method may include: receiving from a reader wireless device a first query message associated with powering on the AIoT device; in response to receiving the first query message, sending to the reader wireless device a first response message indicating a preamble for AIoT device access; based on sending the first response message, receiving from the reader wireless device a second query message indicating resource allocation; and in response to receiving the second query message, sending to the reader wireless device a second response message indicating an AIoT device identifier and AIoT device data, wherein the second response message uses resources corresponding to the resource allocation.

[0021] An Ambient Internet of Things (AIoT) wireless device for wireless communication is described. The AIoT wireless device may include: one or more memories storing processor-executable code; and one or more processors coupled to the memories. The processors may operate individually or jointly to execute the code to cause the AIoT wireless device to: receive from a reader wireless device a first query message associated with powering on the AIoT device; in response to receiving the first query message, send to the reader wireless device a first response message indicating a preamble for AIoT device access; based on sending the first response message, receive from the reader wireless device a second query message indicating resource allocation; and in response to receiving the second query message, send to the reader wireless device a second response message indicating an AIoT device identifier and AIoT device data, wherein the second response message uses resources corresponding to the resource allocation.

[0022] Another Ambient Internet of Things (AIoT) wireless device for wireless communication is described. This AIoT wireless device may include: components for receiving from a reader wireless device a first query message associated with powering on the AIoT device; components for sending to the reader wireless device a first response message indicating a preamble for AIoT device access in response to receiving the first query message; components for receiving from the reader wireless device a second query message indicating resource allocation based on sending the first response message; and components for sending to the reader wireless device a second response message indicating an AIoT device identifier and AIoT device data in response to receiving the second query message, wherein the second response message uses resources corresponding to the resource allocation.

[0023] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive from a reader wireless device a first query message associated with powering on an AIoT device; in response to receiving the first query message, send to the reader wireless device a first response message indicating a preamble for AIoT device access; based on sending the first response message, receive from the reader wireless device a second query message indicating resource allocation; and in response to receiving the second query message, send to the reader wireless device a second response message indicating an AIoT device identifier and AIoT device data, wherein the second response message uses resources corresponding to the resource allocation.

[0024] In some examples of the methods described herein, AIoT devices, and nontransitory computer-readable media, the second response message also includes indications of the AIoT device’s category, capabilities, energy state, data requirements, or combinations thereof.

[0025] The methods described herein, AIoT devices, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for receiving a fourth query message from a reader wireless device based on sending a second response message, the fourth query message being partially based on indication information to indicate a second resource allocation.

[0026] In the methods described herein, AIoT devices, and some examples of nontransitory computer-readable media, resource allocation can be based on contested or non-contested resources.

[0027] In some examples of the methods, AIoT devices, and nontransitory computer-readable media described herein, the preamble indicates the category of the AIoT device, the capabilities of the AIoT device, the data requirements, or a combination thereof.

[0028] In some examples of the methods, AIoT devices, and nontransitory computer-readable media described herein, the first response message may be one of a set of predefined preamble messages, and each predefined preamble message in the set indicates the category of the AIoT device, the capabilities of the AIoT device, data requirements, or a combination thereof.

[0029] In the methods described herein, in some examples of AIoT devices and in non-transitory computer-readable media, the first query message may be a wake-up signaling. Attached Figure Description

[0030] Figure 1 An example of a wireless communication system supporting technologies for (AIoT) device access and data reporting, according to one or more aspects of this disclosure, is shown.

[0031] Figure 2 An example of a wireless communication system supporting technologies for AIoT device access and data reporting, according to one or more aspects of this disclosure, is shown.

[0032] Figure 3 An example of a process flow supporting technologies for AIoT device access and data reporting, according to one or more aspects of this disclosure, is shown.

[0033] Figure 4 An example of a resource allocation diagram supporting technologies for AIoT device access and data reporting, according to one or more aspects of this disclosure, is shown.

[0034] Figure 5 and Figure 6 A block diagram of a device supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure is shown.

[0035] Figure 7 A block diagram of a communication manager supporting technologies for AIoT device access and data reporting, according to one or more aspects of this disclosure, is shown.

[0036] Figure 8 A diagram is shown of a system including a device that supports technologies for AIoT device access and data reporting, according to one or more aspects of this disclosure.

[0037] Figure 9 and Figure 10 A block diagram of a device supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure is shown.

[0038] Figure 11 A block diagram of an action response component supporting technologies for AIoT device access and data reporting, according to one or more aspects of this disclosure, is shown.

[0039] Figure 12 A diagram is shown of a system including a device that supports technologies for AIoT device access and data reporting, according to one or more aspects of this disclosure.

[0040] Figures 13 to 15 A flowchart illustrating a method for supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure is shown. Detailed Implementation

[0041] Some wireless communication systems may include Ambient Internet of Things (AIoT) devices. AIoT devices may include various passive devices capable of harvesting energy by transmitting and receiving power from other devices. For example, a radio reference (RF) source device or reader wireless device may communicate with one or more AIoT devices, which may be referred to as tags, passive user equipment (PUE), or backscatter UE (BUE). In some examples, the RF source device or reader wireless device may be a network entity or user equipment (UE). The reader wireless device may transmit a carrier wave, and the AIoT device may harvest energy from the transmitted carrier wave. Additionally, after harvesting sufficient power, the AIoT device may transmit data to the reader wireless device via a backscatter link to the reader wireless device. One issue with communication between the reader wireless device and the AIoT device is the procedures and signaling used for AIoT device access and data reporting. Current technologies may not support AIoT device access and data reporting.

[0042] Technologies used for AIoT device access and data reporting may include query and response protocols. For example, a reader wireless device may send a first query message to power on one or more AIoT devices within its coverage area. In some examples, the first query message may include wake-up signaling, such as low-power wake-up signaling. An AIoT device that has collected sufficient power from the first query message may send a first response message to the reader wireless device, indicating a preamble for AIoT device access. In some examples, the first response message may include information indicating the AIoT device's category, capacity, energy state, and data requirements. In some examples, the first response message is one of a set of predefined preamble messages, and each predefined preamble message may indicate the AIoT device's category, capabilities, energy state, data requirements, or a combination thereof.

[0043] In response to receiving a first response message from an AIoT device, the reader wireless device may send a second query message to the AIoT device, and the second query message may indicate resource allocation. In some examples, the reader wireless device may retransmit the second query message to the AIoT device after a defined duration. In response to receiving the second query command, the AIoT device may use the allocated resources to send a second response message indicating the AIoT device identifier and data. In some examples, the second response message may include information indicating the AIoT device's category, capacity, energy status, and data requirements. In some examples, the reader wireless device may send an additional query command indicating a second resource allocation based on the information in the second response message.

[0044] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are also described in the context of process flow and resource allocation diagrams. The aspects of this disclosure are further illustrated and described by means of and reference to apparatus diagrams, system diagrams, and flowcharts related to technologies used for AIoT device access and data reporting.

[0045] Figure 1 An example of a wireless communication system 100 supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure is shown. 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 under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

[0051] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across 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, 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, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

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

[0053] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 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 DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with 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 node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, 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 IAB node 104) may be configured to operate according to the techniques described herein.

[0054] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the techniques described herein for AIoT device access and data reporting. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

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

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

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

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

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

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

[0062] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search for control regions to obtain control information based on 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 concatenated manner. The aggregation level of control channel candidates 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 set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0063] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 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 use the same or different radio access technologies to provide coverage for various coverage areas 110.

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

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

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

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

[0068] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

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

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

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

[0072] Wireless communication system 100 may include AIoT devices. AIoT devices may include various passive devices capable of harvesting energy by transmitting and receiving power from other devices. For example, a radio reference (RF) source device or reader wireless device may communicate with one or more AIoT devices, such as tags. In some examples, the RF source device or reader wireless device may be network entity 105 or UE 115. The reader wireless device may transmit a carrier wave, and the AIoT device may harvest energy from the transmitted carrier wave. Additionally, after harvesting sufficient power, the AIoT device may transmit data to the reader wireless device via a backscatter link to the reader wireless device. One issue with communication between the reader wireless device and the AIoT device is the procedures and signaling used for AIoT device access and data reporting. Current technology may not support AIoT device access and data reporting.

[0073] Technologies used for AIoT device access and data reporting may include query and response technologies. For example, a reader wireless device may send a first query message to power on one or more AIoT devices within its coverage area. In some examples, the first query message may include wake-up signaling, such as low-power wake-up signaling. An AIoT device that has collected sufficient power from the first query message may send a first response message to the reader wireless device, indicating a preamble for AIoT device access. In some examples, the first response message may include information indicating the AIoT device's category, capacity, energy state, and data requirements. In some examples, the first response message is one of a set of predefined preamble messages, and each predefined preamble message may indicate the AIoT device's category, capabilities, energy state, data requirements, or a combination thereof.

[0074] In response to receiving a first response message from an AIoT device, the reader wireless device may send a second query message to the AIoT device, and the second query message may indicate resource allocation. In some examples, the reader wireless device may retransmit the second query message to the AIoT device after a defined duration. In response to receiving the second query command, the AIoT device may use the allocated resources to send a second response message indicating the AIoT device identifier and data. In some examples, the second response message may include information indicating the AIoT device's category, capacity, energy status, and data requirements. In some examples, the reader wireless device may send an additional query command indicating a second resource allocation based on the information in the second response message.

[0075] Figure 2 An example of a wireless communication system 200 supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 includes a UE 115-a, which may be an example of UE 115 as described herein. The wireless communication system 200 may also include a network entity 105-a, which may be an example of network entity 105 as described herein. The wireless communication system 200 also includes AIoT devices 205-a and 205-b.

[0076] AIoT device 205-a can communicate with network entity 105-a using communication link 125-b, and UE 115-a can communicate with network entity 105-a using communication link 125-a. Communication link 125-b can be an example of an NR or LTE link between AIoT device 205-a and network entity 105-a. Communication link 125-a can be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication links 125-a and 125-b can include bidirectional links that enable both uplink and downlink communication. For example, AIoT device 205-a can use communication link 125-b to send uplink signals (e.g., uplink transmission), such as uplink control signals or uplink data signals, to network entity 105-a, and network entity 105-a can use communication link 125-b to send downlink signals (e.g., downlink transmission), such as downlink control signals or downlink data signals, to AIoT device 205-a. UE 115-a can use communication link 125-a to send uplink signals (e.g., uplink transmission), such as uplink control signals or uplink data signals, to network entity 105-a, and network entity 105-a can use communication link 125-a to send downlink signals (e.g., downlink transmission), such as downlink control signals or downlink data signals, to UE 115-a.

[0077] AIoT device 205-a can communicate with UE 115-a using communication link 135-a, and AIoT device 205-b can communicate with UE 115-a using communication link 135-b. These communication links can be examples of communication link 135 as described herein. For example, communication links 135-a and 135-b can be sidelink communication links and can support bidirectional communication between AIoT device 205-a and UE 115-a, and between AIoT device 205-b and UE 115-a.

[0078] AIoT devices 205-a and 205-b can be examples of ultra-low complexity and ultra-low power devices that offer several orders of magnitude lower complexity and power consumption than existing enhanced machine-type communication (eMTC) and narrowband Internet of Things (NB-IoT) devices. One example of AIoT devices 205-a and 205-b can be a Type A battery-free device without energy storage capabilities, potentially relying entirely on the availability of an external power source. Another example of AIoT devices 205-a and 205-b can be a Type B device with limited energy storage capabilities, such as supercapacity or conventional capacity that does not require manual replacement or recharging.

[0079] In some examples, AIoT devices 205-a and 205-b can be devices referred to as tags, backscattered UEs (BUEs), or passive UEs (PUEs), which are passive devices without active RF components. A PUE can perform data transmission based on modulating incident RF signals emitted by an ambient transmitter, such as UE 115-a or network entity 105-a. The ambient RF signal can be used as a signal resource for backscattering and as an energy resource for harvesting. Radio frequency identification (RFID) devices are an example of existing battery-free technology with a read range of several meters.

[0080] In some examples, AIoT devices 205-a and 205-b can harvest energy from different sources, such as dedicated RF sources, ambient RF sources, or environmental conditions (such as solar energy). In some examples, UE 115-a can be an RF source for both AIoT devices 205-a and 205-b, and network entity 105-a can be an RF source for AIoT device 205-a. UE 115-a can transmit carriers to AIoT devices 205-a and 205-b, and both devices can harvest energy from the carriers transmitted by UE 115-a. Network entity 105-a can transmit carriers to AIoT device 205-a, and AIoT device 205-a can harvest energy from those carriers.

[0081] In some examples, UE 115-a can be a reader for AIoT devices 205-a and 205-b, and network entity 105-a can be a reader for AIoT device 205-a. The reader wireless device (e.g., UE 115-a and network entity 105-a) can perform signaling procedures for AIoT device (e.g., AIoT device 205-a and AIoT device 205-b) access and for data reporting from AIoT devices (e.g., AIoT device 205-a and AIoT device 205-b) to the reader wireless device (e.g., UE 115-a and network entity 105-a). AIoT devices 205-a and 205-b can be within the coverage area 240 of UE 115-a to receive energy from UE 115-a. In some cases, the AIoT device may be referred to as a tag, AIoT device access may be referred to as tag access, and AIoT device reporting may be referred to as tag data reporting. In some examples, the signaling processes for the AIoT device access phase and the data reporting phase may include a query and response model with multiple rounds of query messages sent by the reader wireless device and multiple response messages sent by the AIoT device. In some cases, power boosting and query message repetition may be enabled during tag access and data reporting.

[0082] refer to Figure 2UE 115-a, acting as a reader, can send a first query message 215-a to AIoT device 205-a via link 135-a, and AIoT device 205-a can send a first response message 220-a to UE 115-a. In response to receiving the first response message 220-a, UE 115-a can send one or more second query messages 225-a to AIoT device 205-a via link 135-a, and AIoT device 205-a can send one or more second first response messages 230-a to UE 115-a. Similarly, UE 115-a, acting as a reader, can send a first query message 215-b to AIoT device 205-b via link 135-b, and AIoT device 205-b can send a first response message 220-b to UE 115-a. In response to receiving a first response message 220-b, UE 115-a may send one or more second query messages 225-b to AIoT device 205-b via link 135-b, and AIoT device 205-b may send one or more second first response messages 230-b to UE 115-a. In some cases, network entity 105-a, acting as a reader, may send a first query message 215-c to AIoT device 205-a via link 125-a, and AIoT device 205-a may send a first response message 220-c to network entity 105-a. In response to receiving a first response message 220-c, network entity 105-a may send one or more second query messages 225-c to AIoT device 205-a via link 125-b, and AIoT device 205-a may send one or more second first response messages 230-c to network entity 105-a. In some cases, network entity 105-a may send a query message 210 to UE 115-a via link 125-a to notify UE 115-a to act as a reader, and UE 115-a may send a message 235 indicating AIoT data to network entity 105-a via link 125-a.

[0083] Figure 3 An example of a process flow 300 supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure is shown. In some examples, process flow 300 may implement as described in reference respectively. Figure 1 and Figure 2 The described aspects of the wireless communication systems 100 and 200, or aspects implemented by these aspects. For example, process flow 300 may be implemented by network entity 105-b, which may be as described in the reference. Figure 1 and Figure 2An example of network entity 105 as described. Process flow 300 can be implemented by AIoT device 205-c, which can be as shown in the reference. Figure 2 Examples of AIoT devices 205-a and 205-b are described. Process flow 300 can be implemented by reader wireless device 305, which can be as described in reference respectively. Figure 1 and 2 Examples of network entity 105 and UE 115 or some other wireless device are described. An example using network entity 105 as the reader may be referred to as topology one, and an example using UE 115 as the reader may be referred to as topology two.

[0084] In some examples, the operations illustrated in process flow 300 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. Alternative examples are possible, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0085] At 310, reader wireless device 305 can receive a query message or query command from network entity 105-b to notify reader wireless device 305 to query AIoT devices. In some examples, the query message received by reader wireless device 305 from network entity 105-b may notify reader wireless device 305 to send a first query message to one or more AIoT devices within the coverage area of ​​reader wireless device 305, as described herein. In some examples, the query message received by reader wireless device 305 from network entity 105-b may include resource configuration for reader wireless device 305 to communicate with one or more AIoT devices. For example, network entity 105-b may pre-configure reader wireless device 305 for communicating with AIoT devices. In some examples, the query message may be a paging-like message.

[0086] At point 315, reader wireless device 305 may send a first query message or a first query command associated with power-on to one or more AIoT devices (e.g., AIoT device 205-c) within the coverage area of ​​reader wireless device 305. In some examples, the first query message may include a wake-up signal, such as low-power wake-up signaling (LP-WUS). The first query message may be a power source for the AIoT devices (e.g., AIoT device 205-c) within the coverage area of ​​reader wireless device 305. The AIoT devices (e.g., AIoT device 205-c) within the coverage area of ​​reader wireless device 305 may collect energy from the first query message to be powered on and enter an operational state.

[0087] At 320, the reader wireless device 305 can receive a first response message from one or more AIoT devices, specifically AIoT device 205-c, indicating a preamble for AIoT device access. AIoT device 205-c can collect sufficient energy from a first query message and successfully receive the first query message. In some cases, the set of AIoT devices can each collect sufficient energy and successfully receive the first query message and send a first response message. The first response message can also be considered an initial tag response. The first response message can indicate a tag-type preamble message for AIoT device access and for congestion avoidance. In some cases, the first response message can be similar to or analogous to a Message-1 (msg1 or msgA) Physical Random Access Channel (PRACH) preamble sent by the UE to initiate a random access procedure for connecting to a network entity via the Uu interface. The first response message can be similar to a PRACH preamble because the purpose of the first response message (e.g., a tag-type preamble message) is the same as that of the PRACH preamble. That is, the purpose of the first response message can be for tag access, congestion avoidance, and for the reader wireless device to detect AIoT devices. The first response message may differ from the PRACH preamble. For example, the waveform and possible sequence / length of the first response message may differ from the waveform and sequence / length of the old PRACH preamble. Additionally, the entire physical channel of the first response message may differ from the physical channel of the old PRACH preamble.

[0088] In some examples, the preamble of the first response message may indicate the category of the AIoT device 205-c, the capabilities of the AIoT device 205-c, the state of energy of the AIoT device 205-c, data requirements, or a combination thereof. In some examples, the first response message may be one of a set of predefined preamble messages. Each predefined preamble message in the set may indicate the category of the AIoT device 205-c, the capabilities of the AIoT device 205-c, the state of energy of the AIoT device 205-c, data requirements, or a combination thereof.

[0089] At 325, reader wireless device 305 may, in response to receiving the first response message, send a second query message or command instructing resource allocation to AIoT device 205-c. In some examples, reader wireless device 305 may allocate resources to detected AIoT devices (e.g., AIoT device 205-c) whose tag class preambles have been successfully received by reader wireless device 305. Resources may be pre-configured by network entity 105-b. Resources may be allocated to detected AIoT devices, and congestion avoidance may be considered. In some cases, resource allocation may be contention-free or contention-based. In some cases, the second query message may be similar to or analogous to message two (msg2) received by the UE as part of the random access channel (RACH) procedure for connecting to a network entity via the Uu interface. The second query message may be similar to message two of the RACH procedure because the purpose of the second query message is the same as that of the PRACH preamble. In other words, the purpose of the second query message can be to allocate resources for AIoT devices to report AIoT data, similar to the uplink grant resource allocation function in the Random Access Response (RAR) of message two in the RACH procedure. The second query message can differ from message two in the RACH procedure because AIoT does not have a random access response message. The resource allocation in the second query message can also differ from the uplink grant format in message two RAR.

[0090] At 330, AIoT device 205-c may send a second response message to reader wireless device 305, indicating the AIoT device identifier and AIoT device data. The second response message is sent on a resource corresponding to the resource allocation. In some examples, the second response message includes indications of the AIoT device 205-c's category, capabilities, energy state, data requirements, or a combination thereof.

[0091] At 335, the reader wireless device 305 can send a query message or command indicative of resource allocation to the AIoT device 205-c. In some examples, the reader wireless device 305 can retransmit the second query message if it fails to receive the second response message. In some cases, the reader wireless device 305 can retransmit the second query message after a defined duration. In some examples, the reader wireless device 305 can send a query message indicative of second resource allocation based on indication information received in the second response message.

[0092] At 340, AIoT device 205-c can use the resources allocated in the query message at 335 to send a response message to reader wireless device 305 indicating the AIoT device identifier and AIoT device data. In some examples, the response message includes indications of the AIoT device 205-c's category, capabilities, energy state, data requirements, or a combination thereof.

[0093] At 345, the reader wireless device 305 can send a query message or command to the AIoT device 205-c indicating the allocation of resources for tag data reporting.

[0094] At 350, AIoT device 205-c can use the resources allocated in the query message to send a response message to reader wireless device 305 indicating the AIoT device identifier and AIoT device data. In some examples, the response message includes indications of the AIoT device 205-c's category, capabilities, energy state, data requests, or a combination thereof.

[0095] The first query message at 315, the first response message at 320, the second query message at 325, and the second response message at 330 can be considered together as the AIoT device access phase or the tag access phase. The query message and response message at 335 can be considered together as the AIoT device data reporting phase or the tag data reporting phase. The query message at 345 and the response message at 350 can be considered together as the AIoT device data reporting phase or the tag data reporting phase. During the data reporting phase, the reader wireless device 305 can send multi-round query messages for large amounts of AIoT data. The AIoT device 205-c can use tag information to indicate tag data requests in the response messages. The reader wireless device 305 can provide resource allocation to the AIoT device 205-c based on the tag data requests. The query messages or commands at 315, 325, 335, and 345 can instruct the AIoT device 205-c to perform actions such as waking up the device with the first query message at 315, allocating resources with the second query message at 325, and reporting tag data with the query messages at 335 and 345. The query message may include fields indicating action commands.

[0096] At 355, reader wireless device 305 can transmit AIoT device 205-c data to network entity 105-b. In some examples, reader wireless device 305 can reassemble AIoT device data or tag data into UE data before transmitting to network entity 105-b. In some cases, reader wireless device 305 can transmit AIoT device data from several AIoT devices to network entity 105-b, and the corresponding AIoT device data can be associated with a corresponding AIoT device identifier.

[0097] In some examples, reader wireless device 305 may determine the number of AIoT devices within its coverage area in response to receiving a quantity first response message from one or more AIoT devices. Reader wireless device 305 may determine resource allocation for second query messages and data reporting query messages based on the number of AIoT devices. For example, the number of detected AIoT devices may affect contention-based resource allocation. The second query message in the tag access phase and the query message in the tag data reporting phase may indicate resource allocation to the detected or selected AIoT devices. Reader wireless device 305 may allocate resources provided by network entity 105-b to the detected or selected AIoT devices in both the tag access and tag data reporting phases. In the tag data reporting phase, in each query message, reader wireless device 305 may indicate resources for AIoT data reporting. The allocated resources may be contention-based resources configured for the set of detected or selected AIoT devices, or they may be contention-free resources associated with one of the AIoT devices to avoid congestion. If the number of detected or selected AIoT devices is large, such as exceeding the available resources, the reader wireless device 305 can configure contention-based resources for the AIoT devices without associating resources with one of the AIoT devices. If the number of detected or selected AIoT devices is equal to or less than the number of available resources, the reader wireless device 305 can configure contention-free resources for the AIoT devices. Contention-free resources may be more efficient for fast AIoT data delivery. Contention-free resources are associated with one of the selected, identified AIoT devices.

[0098] Figure 4 An example of a resource allocation diagram 400 supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure is shown. In some examples, the resource allocation diagram 400 may be implemented as described in reference to [references to other diagrams]. Figure 1 and Figure 2 The described aspects of the wireless communication systems 100 and 200, or aspects thereof, are implemented. For example, the resource allocation diagram 400 can be implemented by a reader wireless device, which can be as shown in the reference. Figure 2 An example of a described reader wireless device.

[0099] In some examples, resource allocation diagram 400 includes resources 405-a, 405-b, 405-c, 405-d, 405-e, and 405-f. Resources 405-a, 405-b, 405-c, 405-d, 405-e, and 405-f may represent resource configurations indicated by network entity 105-b to reader wireless device 305. In some examples, reader wireless device 305 may associate a non-contested resource (e.g., resource 405-a) with AIoT device 205-c, and reader wireless device 305 may associate a non-contested resource (e.g., resource 405-d) with another detected AIoT device. In another example, reader wireless device 305 can associate a detected AIoT device with contention-based resources (e.g., resources 405-a, 405-b, 405-c, 405-d, 405-e, and 405-f). Contention-based resource allocation allows AIoT device 205-c to select one resource from a pool of resources shared with other AIoT devices (e.g., resources 405-a, 405-b, 405-c, 405-d, 405-e, and 405-f).

[0100] In some examples, reader wireless device 305 can determine the number of AIoT devices within its coverage area in response to receiving a first response message from one or more AIoT devices. For example, reader wireless device 305 can detect three AIoT devices (e.g., tag 1, tag 2, and tag 3). For a second query message, reader wireless device 305 can determine a resource allocation 410, where a first uncontested resource is associated with tag 1, a second uncontested resource is associated with tag 2, a third uncontested resource is associated with tag 3, and the remaining resources are contention-based resources.

[0101] In some cases, reader wireless device 305 can assign dedicated resources to AIoT device 205-c for tag response messages. If AIoT device 205-c indicates additional data to be reported during a query session via a response message, reader wireless device 305 can assign dedicated resources to AIoT device 205-c for providing that data in the response message. In some cases, reader wireless device 305 can assign resources to AIoT device 205-c in time division multiplexing (TDM), frequency division multiplexing (FDM), and space division multiplexing (SDM) modes. For example, the resources allocated to AIoT device 205-c can be distributed in the time domain to reduce collisions when multiple AIoT devices respond using response messages within the allocated resources. In another example, the resources allocated to AIoT device 205-c can be frequency-shifted in backscatter for AIoT data reporting. Network entity 105-b can provide resource configurations in the time domain, frequency domain, or beam domain as resource pre-configuration.

[0102] In some examples, AIoT device 205-c may use a preamble or class preamble of a first response message to implicitly indicate its category, capabilities, energy state, data requirements, or a combination thereof. In some examples, the first response message may be one of a set of predefined preamble messages. Each predefined preamble message in the set may indicate a category, capabilities, energy state, data requirements, or a combination thereof. In some cases, AIoT device 205-c may be configured using a pooled partition of predefined preamble or class preamble messages. Preamble messages may be group-based and may be configured by network entity 105-b. AIoT devices may select which groups of preamble messages implicitly indicate their category, capabilities, energy state, data requirements, or a combination thereof. In some cases, dedicated resources or more resources (e.g., longer time slots) with frequency shifts in backscatter may be assigned to AIoT devices indicating advanced capabilities for larger AIoT data reporting.

[0103] In some cases, implicit indications can be used as early indications for improved resource allocation from reader wireless device 305. Preambles or preamble-like groups can be based on different AIoT data sizes, whether the AIoT device supports frequency shifting in backscatter, whether the AIoT device supports multi-slot transmission, or whether the AIoT device is active or passive AIoT. For example, if the AIoT device has a potentially large amount of AIoT data to transmit to reader wireless device 305, the AIoT device can select a preamble or preamble-like group associated with a large AIoT data size.

[0104] In some cases, the reader wireless device 305 may not be able to determine whether all AIoT devices in the coverage area have completed their corresponding data reporting. The reader wireless device 305 may also be unable to determine which AIoT devices in the coverage area might have data to report. Additionally, AIoT devices may experience transient radio malfunctions, resulting in less power harvested and erroneous transmissions. In some examples, the automatic transmission of query messages can help AIoT devices harvest power, acquire resources, and recover from failed transmissions. Timers (e.g., query message retransmission timers) can be introduced to control the automatic transmission of query messages during the tag data reporting phase. The query retransmission timer can be started when a second query message is transmitted. The reader wireless device 305 can decide whether to send an additional query message after the second query message has been sent. For example, AIoT device 205-c may indicate in a second response message or a later response message that more pending AIoT data should be transmitted using tag information indication. In some cases, a certain number of AIoT devices may indicate in a second response message or a later response message that more pending data should be transmitted using tag information indication. When the query retransmission timer expires, the reader wireless device 305 can automatically send a query command indicating resource allocation.

[0105] Figure 5 A block diagram 500 of a device 505 supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure is shown. Device 505 may be an example of various aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505 or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520) may include at least one processor, which may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0106] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for AIoT device access and data reporting). The information may be transmitted to other components of device 505. Receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0107] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to technologies used for AIoT device access and data reporting, including packets, user data, control information, or any combination thereof. In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0108] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the technologies for AIoT device access and data reporting as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

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

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

[0111] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0112] According to the examples disclosed herein, the communication manager 520 may support wireless communication. For example, the communication manager 520 is capable of, configured to, or operable to support components for sending a first query message associated with powering on one or more AIoT devices within the coverage area of ​​the reader wireless device. The communication manager 520 is capable of, configured to, or operable to support components for receiving a first response message indicating a preamble for AIoT device access from a first AIoT device among one or more AIoT devices based on sending the first query message. The communication manager 520 is capable of, configured to, or operable to support components for sending a second query message indicating resource allocation to the first AIoT device in response to receiving the first response message. The communication manager 520 is capable of, configured to, or operable to support components for receiving a second response message indicating an AIoT device identifier and AIoT device data from the first AIoT device based on sending the second query message, wherein the second response message is received on a resource corresponding to the resource allocation.

[0113] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources.

[0114] Figure 6 A block diagram 600 illustrates a device 605 supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0115] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for AIoT device access and data reporting). The information may be transmitted to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0116] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to technologies used for AIoT device access and data reporting, including packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0117] Device 605 or its various components may be examples of parts used to perform various aspects of the technologies for AIoT device access and data reporting as described herein. For example, communication manager 620 may include a first query message manager 625, a first response message manager 630, a second query message manager 635, a second response message manager 640, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0118] According to the examples disclosed herein, the communication manager 620 may support wireless communication. The first query message manager 625 is capable of, configured to, or operable to support components for sending a first query message associated with powering on one or more AIoT devices within the coverage area of ​​the reader wireless device. The first response message manager 630 is capable of, configured to, or operable to support components for receiving a first response message indicating a preamble for AIoT device access from a first AIoT device among one or more AIoT devices based on the sending of the first query message. The second query message manager 635 is capable of, configured to, or operable to support components for sending a second query message indicating resource allocation to the first AIoT device in response to receiving the first response message. The second response message manager 640 is capable of, configured to, or operable to support components for receiving a second response message indicating an AIoT device identifier and AIoT device data from the first AIoT device based on the sending of the second query message, wherein the second response message is received on a resource corresponding to the resource allocation.

[0119] Figure 7 A block diagram 700 illustrates a communication manager 720 supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of the technologies for AIoT device access and data reporting as described herein. For example, the communication manager 720 may include a first query message manager 725, a first response message manager 730, a second query message manager 735, a second response message manager 740, a third query message manager 745, an AIoT device data manager 750, an AIoT device quantity manager 755, a resource allocation manager 760, a fourth query message manager 765, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0120] According to the examples disclosed herein, the communication manager 720 may support wireless communication. The first query message manager 725 is capable of, configured to, or operable to support components for sending a first query message associated with powering on one or more AIoT devices within the coverage area of ​​the reader wireless device. The first response message manager 730 is capable of, configured to, or operable to support components for receiving a first response message indicating a preamble for AIoT device access from a first AIoT device among one or more AIoT devices based on the sending of the first query message. The second query message manager 735 is capable of, configured to, or operable to support components for sending a second query message indicating resource allocation to the first AIoT device in response to receiving the first response message. The second response message manager 740 is capable of, configured to, or operable to support components for receiving a second response message indicating an AIoT device identifier and AIoT device data from the first AIoT device based on the sending of the second query message, wherein the second response message is received on a resource corresponding to the resource allocation.

[0121] In some examples, the third query message manager 745 is capable of, configured to, or able to operate to support components for receiving a third query message from a network entity that notifies the reader wireless device to send a first query message.

[0122] In some examples, the third query message includes resource configurations for the reader wireless device to communicate with one or more AIoT devices.

[0123] In some examples, the AIoT device data manager 750 is capable of, configured to, or able to operate to support components for sending AIoT device data to network entities.

[0124] In some examples, the second query message manager 735 is capable of, configured to, or able to operate to support components for retransmitting the second query message to the first AIoT device based on the reader wireless device's failure to receive the second response message.

[0125] In some examples, the second query message manager 735 is capable of, configured to, or able to operate to support components for retransmitting the second query message to the first AIoT device after a defined duration.

[0126] In some examples, the second response message also includes indications of the first AIoT device’s category, capabilities, energy status, data requirements, or a combination thereof.

[0127] In some examples, the fourth query message manager 765 is capable of, configured to, or operable to support components for sending a fourth query message to the first AIoT device in response to receiving a second response message, the fourth query message being partially based on indication information to indicate a second resource allocation.

[0128] In some examples, resource allocation is based on either contested or non-contested resources.

[0129] In some examples, the AIoT device quantity manager 755 is capable of, configured to, or operable to support components for determining the number of AIoT devices within the coverage area of ​​the reader wireless device in response to receiving a quantity first response message from one or more AIoT devices. In some examples, the resource allocation manager 760 is capable of, configured to, or operable to support components for determining resource allocation based on the number of AIoT devices.

[0130] In some examples, the preamble indicates the category of the first AIoT device, the capabilities of the first AIoT device, the data requirements, or a combination thereof.

[0131] In some examples, the first response message is one of a set of predefined preamble messages. In some examples, each predefined preamble message in the set may indicate the category of the first AIoT device, the capabilities of the first AIoT device, data requirements, or a combination thereof.

[0132] In some examples, the first query message is a wake-up signaling.

[0133] Figure 8 A diagram of a system 800 including a device 805 supporting technologies for AIoT device access and data reporting, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

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

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

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

[0137] At least one processor 840 may include a smart hardware device (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic component, discrete hardware component, or any combination thereof). In some cases, at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting technologies for AIoT device access and data reporting). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, wherein at least one processor 840 and at least one memory 830 are configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 830 or otherwise.

[0138] According to the examples disclosed herein, the communication manager 820 may support wireless communication. For example, the communication manager 820 is capable of, configured to, or operable to support components for sending a first query message associated with powering on one or more AIoT devices within the coverage area of ​​a reader wireless device. The communication manager 820 is capable of, configured to, or operable to support components for receiving a first response message from a first AIoT device among one or more AIoT devices, indicating a preamble for AIoT device access, based on sending the first query message. The communication manager 820 is capable of, configured to, or operable to support components for sending a second query message to the first AIoT device, indicating resource allocation, in response to receiving the first response message. The communication manager 820 is capable of, configured to, or operable to support components for receiving a second response message from the first AIoT device, indicating an AIoT device identifier and AIoT device data, based on sending the second query message, wherein the second response message is received on a resource corresponding to the resource allocation.

[0139] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support techniques for improving communication reliability, utilizing communication resources more efficiently, and improving coordination between devices.

[0140] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 815, one or more antennas 825, or any combination thereof, or otherwise cooperating with them. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported by or executed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause device 805 to perform various aspects of the technologies for AIoT device access and data reporting as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0141] Figure 9A block diagram 900 illustrates a device 905 supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure. Device 905 may be an example of various aspects of an AIoT device as described herein. Device 905 may include an input component 910, an output component 915, and an action response component 920. Device 905 or one or more components of device 905 (e.g., input component 910, output component 915, and action response component 920) may include at least one processor, which may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0142] Input component 910 manages input signals of device 905. For example, input component 910 may identify input signals based on interaction with a modem, keyboard, mouse, touchscreen, or similar device. These input signals may be associated with user input or processing at other components or devices. In some cases, input component 910 may utilize an operating system (such as iOS). ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® The input component 910 can transmit aspects of these input signals to other components of the device 905 for processing. For example, the input component 910 can send input signals to the action response component 920 to support technologies for AIoT device access and data reporting. In some cases, the input component 910 can be as described in the reference... Figure 12 The components of the described I / O controller 1210.

[0143] Output component 915 manages the output signals of device 905. For example, output component 915 can receive signals from other components of device 905 (such as action response component 920) and can send these signals to other components or devices. In some specific examples, output component 915 can send output signals for display in a user interface, for storage in a database or data repository, for further processing at a server or server cluster, or for any other process at any number of devices or systems. In some cases, output component 915 may be as described in the reference... Figure 12 The components of the described I / O controller 1210.

[0144] Action response component 920, input component 910, output component 915, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of the technologies for AIoT device access and data reporting as described herein. For example, action response component 920, input component 910, output component 915, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

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

[0146] Additionally or alternatively, the action response component 920, input component 910, output component 915, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the action response component 920, input component 910, output component 915, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0147] In some examples, the action response component 920 may be configured to use or otherwise cooperate with the input component 910, the output component 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, sending). For example, the action response component 920 may receive information from the input component 910, transmit information to the output component 915, or be integrated in combination with the input component 910, the output component 915, or both to acquire information, output information, or perform various other operations as described herein.

[0148] According to the examples disclosed herein, the action response component 920 may support wireless communication. For example, the action response component 920 is capable of, configured to, or operable to support components for receiving a first query message from a reader wireless device associated with powering on an AIoT device. The action response component 920 is capable of, configured to, or operable to support components for sending a first response message to the reader wireless device in response to receiving the first query message, indicating a preamble for AIoT device access. The action response component 920 is capable of, configured to, or operable to support components for receiving a second query message from the reader wireless device based on sending the first response message, indicating a resource allocation. The action response component 920 is capable of, configured to, or operable to support components for sending a second response message to the reader wireless device in response to receiving the second query message, indicating an AIoT device identifier and AIoT device data, wherein the second response message uses resources corresponding to the resource allocation.

[0149] By including or configuring a motion response component 920 according to an example as described herein, device 905 (e.g., control input component 910, output component 915, motion response component 920 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption, and utilizing communication resources more efficiently.

[0150] Figure 10 A block diagram 1000 of a device 1005 supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure is shown. Device 1005 may be an example of a device 905 as described herein or an aspect of an AIoT device. Device 1005 may include an input component 1010, an output component 1015, and an action response component 1020. Device 1005 or one or more components of device 1005 (e.g., input component 1010, output component 1015, and action response component 1020) may include at least one processor, which may be coupled to at least one memory to support the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0151] Input component 1010 manages input signals of device 1005. For example, input component 1010 may identify input signals based on interaction with a modem, keyboard, mouse, touchscreen, or similar device. These input signals may be associated with user input or processing at other components or devices. In some cases, input component 1010 may utilize an operating system (such as iOS). ® ANDROID ® MS-DOS ® MS-WINDOWS ®OS / 2 ® UNIX ® LINUX ® The input component 1010 may transmit aspects of these input signals to other components of the device 1005 for processing. For example, the input component 1010 may send input signals to the action response component 1020 to support technologies for AIoT device access and data reporting. In some cases, the input component 1010 may be as described in the reference... Figure 12 The components of the described I / O controller 1210.

[0152] Output component 1015 manages the output signals of device 1005. For example, output component 1015 can receive signals from other components of device 1005 (such as action response component 1020) and can send these signals to other components or devices. In some specific examples, output component 1015 can send output signals for display in a user interface, for storage in a database or data repository, for further processing at a server or server cluster, or for any other process at any number of devices or systems. In some cases, output component 1015 may be as described in the reference... Figure 12 The components of the described I / O controller 1210.

[0153] Device 1005 or its various components may be examples of parts used to perform various aspects of the technologies for AIoT device access and data reporting as described herein. For example, action response component 1020 may include a first query message manager 1025, a first response message manager 1030, a second query message manager 1035, a second response message manager 1040, or any combination thereof. Action response component 1020 may be examples of aspects of action response component 920 as described herein. In some examples, action response component 1020 or its various components may be configured to use or otherwise cooperate with input component 1010, output component 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, action response component 1020 may receive information from input component 1010, transmit information to output component 1015, or be integrated in combination with input component 1010, output component 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0154] According to the examples disclosed herein, the action response component 1020 may support wireless communication. The first query message manager 1025 is capable of, configured to, or operable to support components for receiving a first query message from the reader wireless device associated with powering on an AIoT device. The first response message manager 1030 is capable of, configured to, or operable to support components for sending a first response message to the reader wireless device in response to receiving the first query message, indicating a preamble for AIoT device access. The second query message manager 1035 is capable of, configured to, or operable to support components for receiving a second query message from the reader wireless device in response to sending the first response message, indicating a resource allocation. The second response message manager 1040 is capable of, configured to, or operable to support components for sending a second response message to the reader wireless device in response to receiving the second query message, indicating an AIoT device identifier and AIoT device data, wherein the second response message uses resources corresponding to the resource allocation.

[0155] Figure 11 A block diagram 1100 is shown of an action response component 1120 supporting technologies for AIoT device access and data reporting according to one or more aspects of this disclosure. Action response component 1120 may be an example of aspects of action response component 920, action response component 1020, or both as described herein. Action response component 1120 or its various components may be examples of parts for performing various aspects of the technologies for AIoT device access and data reporting as described herein. For example, action response component 1120 may include a first query message manager 1125, a first response message manager 1130, a second query message manager 1135, a second response message manager 1140, a fourth query message manager 1145, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0156] According to the examples disclosed herein, the action response component 1120 may support wireless communication. The first query message manager 1125 is capable of, configured to, or operable to support components for receiving a first query message from the reader wireless device associated with powering on an AIoT device. The first response message manager 1130 is capable of, configured to, or operable to support components for sending a first response message to the reader wireless device in response to receiving the first query message, indicating a preamble for AIoT device access. The second query message manager 1135 is capable of, configured to, or operable to support components for receiving a second query message from the reader wireless device in response to sending the first response message, indicating a resource allocation. The second response message manager 1140 is capable of, configured to, or operable to support components for sending a second response message to the reader wireless device in response to receiving the second query message, indicating an AIoT device identifier and AIoT device data, wherein the second response message uses resources corresponding to the resource allocation.

[0157] In some examples, the second response message also includes indications of the AIoT device’s category, capabilities, energy status, data requirements, or a combination thereof.

[0158] In some examples, the fourth query message manager 1145 is capable of, configured to, or able to operate to support components for receiving a fourth query message from a reader wireless device based on sending a second response message, the fourth query message being partially based on indication information to indicate a second resource allocation.

[0159] In some examples, resource allocation is based on either contested or non-contested resources.

[0160] In some examples, the preamble indicates the category of the AIoT device, the capabilities of the AIoT device, the data requirements, or a combination thereof.

[0161] In some examples, the first response message is one of a set of predefined preamble messages. In some examples, each predefined preamble message in the set may indicate the category of the AIoT device, the capabilities of the AIoT device, data requirements, or a combination thereof.

[0162] In some examples, the first query message is a wake-up signaling.

[0163] Figure 12A diagram of a system 1200 including a device 1205 supporting technologies for AIoT device access and data reporting, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or AIoT as described herein, or may include components thereof. Device 1205 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a motion response component 1220, an I / O controller 1210, a database controller 1215, at least one memory 1225, at least one processor 1230, and a database 1235. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1240).

[0164] I / O controller 1210 manages input signals 1245 and output signals 1250 of device 1205. I / O controller 1210 can also manage peripheral devices not integrated into device 1205. In some cases, I / O controller 1210 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1210 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, it may be another known operating system. Additionally or alternatively, the I / O controller 1210 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1210 may be implemented as part of a processor. In some examples, a user may interact with device 1205 via the I / O controller 1210 or via hardware components controlled by the I / O controller 1210.

[0165] Database controller 1215 manages data storage and processing in database 1235. Database 1235 may be located external to device 1205, may be temporarily or permanently connected to device 1205, or may be a data storage component of device 1205. In some cases, users may interact with database controller 1215. In other cases, database controller 1215 may operate automatically without user interaction. Database 1235 may be an example of a persistent data repository, a single database, a distributed database, multiple distributed databases, a database management system, or an emergency backup database.

[0166] Memory 1225 may include random access memory (RAM) and ROM. Memory 1225 may store computer-readable, computer-executable software including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, in addition to this, memory 1225 may also contain a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0167] Processor 1230 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1230 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1230. Processor 1230 may be configured to execute computer-readable instructions stored in memory 1225 to perform various functions (e.g., functions or tasks supporting technologies for AIoT device access and data reporting).

[0168] According to the examples disclosed herein, the action response component 1220 may support wireless communication. For example, the action response component 1220 is capable of, configured to, or operable to support components for receiving a first query message from a reader wireless device associated with powering on an AIoT device. The action response component 1220 is capable of, configured to, or operable to support components for sending a first response message to the reader wireless device in response to receiving the first query message, indicating a preamble for AIoT device access. The action response component 1220 is capable of, configured to, or operable to support components for receiving a second query message from the reader wireless device in response to sending the first response message, indicating a resource allocation. The action response component 1220 is capable of, configured to, or operable to support components for sending a second response message to the reader wireless device in response to receiving the second query message, indicating an AIoT device identifier and AIoT device data, wherein the second response message uses resources corresponding to the resource allocation.

[0169] By including or configuring action response component 1220 according to examples as described herein, device 1205 can support techniques for improving communication reliability, utilizing communication resources more efficiently, and improving coordination between devices.

[0170] Figure 13 A flowchart illustrating a method 1300 supporting technologies for AIoT device access and data reporting according to various aspects of this disclosure is shown. Operation of method 1300 may be implemented by a UE or its components as described herein. For example, operation of method 1300 may be performed by, as referenced... Figures 1 to 8The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0171] At 1305, the method may include sending a first query message associated with powering on one or more AIoT devices within the coverage area of ​​the reader wireless device. Operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be provided by reference to [reference needed]. Figure 7 The first query message manager 725, as described, is used to execute the query.

[0172] At 1310, the method may include receiving a first response message indicating a preamble for AIoT device access from a first AIoT device among one or more AIoT devices based on sending a first query message. Operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1310 may be provided by reference to [reference needed]. Figure 7 The first response message manager 730 described is used to execute this.

[0173] At 1315, the method may include sending a second query message instructing resource allocation to a first AIoT device in response to receiving a first response message. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be provided by reference to [reference needed]. Figure 7 The second query message manager 735, as described, is used to execute the query.

[0174] At 1320, the method may include receiving a second response message indicating an AIoT device identifier and AIoT device data from a first AIoT device based on sending a second query message, wherein the second response message is received on a resource corresponding to the resource allocation. The operation of block 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1320 may be provided by reference to [reference needed]. Figure 7 The second response message manager 740 described is used to execute this.

[0175] Figure 14 A flowchart illustrating a method 1400 supporting technologies for AIoT device access and data reporting according to various aspects of this disclosure is shown. Operation of method 1400 may be implemented by a UE or its components as described herein. For example, operation of method 1400 may be performed by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0176] At 1405, the method may include sending a first query message associated with powering on one or more AIoT devices within the coverage area of ​​the reader wireless device. Operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1405 may be provided by reference to [reference needed]. Figure 7 The first query message manager 725, as described, is used to execute the query.

[0177] At 1410, the method may include receiving a first response message indicating a preamble for AIoT device access from a first AIoT device among one or more AIoT devices based on sending a first query message. Operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1410 may be provided by reference to [reference needed]. Figure 7 The first response message manager 730 described is used to execute this.

[0178] At 1415, the method may include sending a second query message instructing resource allocation to a first AIoT device in response to receiving a first response message. The operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be provided by reference to [reference needed]. Figure 7 The second query message manager 735, as described, is used to execute the query.

[0179] At 1420, the method may include receiving a second response message indicating an AIoT device identifier and AIoT device data from a first AIoT device based on sending a second query message, wherein the second response message is received on a resource corresponding to the resource allocation. The operation of block 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1420 may be provided by reference to [reference needed]. Figure 7 The second response message manager 740 described is used to execute this.

[0180] At 1425, the method may include sending AIoT device data to a network entity. The operation of block 1425 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1425 may be derived from references... Figure 7 The AIoT device data manager 750 described is used to perform this.

[0181] Figure 15 A flowchart illustrating a method 1500 supporting technologies for AIoT device access and data reporting according to various aspects of this disclosure is shown. Operation of method 1500 can be implemented by an AIoT device or its components as described herein. For example, operation of method 1500 can be achieved by, as referenced... Figures 1 to 4 and Figures 9 to 12The described AIoT device is used to perform this function. In some examples, the AIoT device can execute a set of instructions to control the functional elements of the AIoT device to perform the described function. Additionally or alternatively, the AIoT device may use dedicated hardware to perform aspects of the described function.

[0182] At 1505, the method may include receiving a first query message from a reader wireless device associated with powering on an AIoT device. Operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1505 may be provided by reference to [reference needed]. Figure 11 The first query message manager 1125 described is used to execute it.

[0183] At 1510, the method may include sending a first response message to the reader wireless device in response to receiving a first query message, indicating a preamble for AIoT device access. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1510 may be provided by reference to [reference needed]. Figure 11 The first response message manager 1130 described is used to execute this.

[0184] At 1515, the method may include receiving a second query message indicating resource allocation from the reader wireless device based on sending a first response message. The operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be derived from references... Figure 11 The second query message manager 1135 described is used to execute this.

[0185] At 1520, the method may include sending a second response message to the reader wireless device in response to receiving the second query message, indicating an AIoT device identifier and AIoT device data, wherein the second response message uses resources corresponding to the resource allocation. The operation of block 1520 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1520 may be provided by reference to [reference needed]. Figure 11 The second response message manager 1140 described herein is used for execution.

[0186] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a reader wireless device, the method comprising: sending a first query message associated with powering on one or more Ambient Internet of Things (AIoT) devices within the coverage area of ​​the reader wireless device; receiving, at least in part based on sending the first query message, a first response message from a first AIoT device among the one or more AIoT devices indicating a preamble for AIoT device access; in response to receiving the first response message, sending a second query message to the first AIoT device indicating a resource allocation; and receiving, at least in part based on sending the second query message, a second response message from the first AIoT device indicating an AIoT device identifier and AIoT device data, wherein the second response message is received on a resource corresponding to the resource allocation.

[0187] Aspect 2: According to the method of aspect 1, the method further includes: receiving a third query message from a network entity, the third query message notifying the reader wireless device to send the first query message.

[0188] Aspect 3: According to the method of aspect 2, wherein the third query message includes resource configuration for the reader wireless device to communicate with the one or more AIoT devices.

[0189] Aspect 4: The method according to any one of Aspects 1 to 3, the method further includes: sending the AIoT device data to a network entity.

[0190] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: retransmitting the second query message to the first AIoT device at least in part based on the reader wireless device's failure to receive the second response message.

[0191] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: retransmitting the second query message to the first AIoT device after a defined duration.

[0192] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the second response message further includes indication information indicating the category of the first AIoT device, the capabilities of the first AIoT device, the energy state of the AIoT device, data requests, or a combination thereof.

[0193] Aspect 8: According to the method of aspect 7, the method further includes: sending a fourth query message to the first AIoT device in response to receiving the second response message, the fourth query message indicating a second resource allocation in part based on the indication information.

[0194] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the resource allocation is based on competing resources or non-competing resources.

[0195] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: determining the number of AIoT devices within the coverage area of ​​the reader wireless device in response to receiving a quantity first response message from the one or more AIoT devices; and determining the resource allocation based at least in part on the number of AIoT devices.

[0196] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the preamble indicates the category of the first AIoT device, the capabilities of the first AIoT device, data requirements, or a combination thereof.

[0197] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the first response message is a predefined preamble message in a set of predefined preamble messages, each of the predefined preamble messages indicating the category of the first AIoT device, the capabilities of the first AIoT device, data requirements, or a combination thereof.

[0198] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the first query message is a wake-up signaling.

[0199] Aspect 14: A method for wireless communication by an Ambient Internet of Things (AIoT) wireless device, the method comprising: receiving from a reader wireless device a first query message associated with powering on the AIoT device; in response to receiving the first query message, sending to the reader wireless device a first response message indicating a preamble for AIoT device access; receiving from the reader wireless device, at least in part based on sending the first response message, a second query message indicating a resource allocation; and in response to receiving the second query message, sending to the reader wireless device a second response message indicating an AIoT device identifier and AIoT device data, wherein the second response message uses resources corresponding to the resource allocation.

[0200] Aspect 15: According to the method of aspect 14, the second response message further includes indication information indicating the category of the AIoT device, the capabilities of the AIoT device, the energy state of the AIoT device, data requirements, or a combination thereof.

[0201] Aspect 16: The method according to aspect 15, the method further comprising: receiving a fourth query message from the reader wireless device based at least in part on sending the second response message, the fourth query message being based in part on the indication information to indicate a second resource allocation.

[0202] Aspect 17: The method according to any one of Aspects 14 to 16, wherein the resource allocation is based on competing resources or non-competing resources.

[0203] Aspect 18: The method according to any one of Aspects 14 to 17, wherein the preamble indicates the category of the AIoT device, the capabilities of the AIoT device, data requirements, or a combination thereof.

[0204] Aspect 19: The method according to any one of Aspects 14 to 18, wherein the first response message is a predefined preamble message in a set of predefined preamble messages, each of the predefined preamble messages indicating the category of the AIoT device, the capabilities of the AIoT device, data requirements, or a combination thereof.

[0205] Aspect 20: The method according to any one of aspects 14 to 19, wherein the first query message is a wake-up signaling.

[0206] Aspect 21: A reader wireless device for wireless communication, the reader wireless device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the reader wireless device to perform a method according to any one of Aspects 1 to 13.

[0207] Aspect 22: A reader wireless device for wireless communication, the reader wireless device comprising at least one component for performing the method according to any one of aspects 1 to 13.

[0208] Aspect 23: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the method according to any one of aspects 1 to 13.

[0209] Aspect 24: An Ambient Internet of Things (AIoT) wireless device for wireless communication, the AIoT wireless device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the AIoT wireless device to perform a method according to any one of Aspects 14 to 20.

[0210] Aspect 25: An Ambient Internet of Things (AIoT) wireless device for wireless communication, the AIoT wireless device comprising at least one component for performing the method according to any one of aspects 14 to 20.

[0211] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform a method according to any one of aspects 14 to 20.

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

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

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

[0215] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

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

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

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

[0219] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

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

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

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

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

Claims

1. A wireless reader device, the wireless reader device comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to the one or more memories and capable of operating individually or jointly to execute the code to enable the reader wireless device: Send a first query message associated with powering on one or more Ambient Internet of Things (AIoT) devices within the coverage area of ​​the reader wireless device; At least in part, based on sending the first query message to receive a first AIoT device among the one or more AIoT devices, an indication of a preamble for AIoT device access; In response to receiving the first response message, a second query message instructing resource allocation is sent to the first AIoT device; and At least in part, the second response message is received from the first AIoT device, indicating an AIoT device identifier and AIoT device data, based on sending the second query message, wherein the second response message is received on a resource corresponding to the resource allocation.

2. The reader wireless device of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code to cause the reader wireless device to: A third query message is received from the network entity, and the third query message notifies the reader wireless device to send the first query message.

3. The reader wireless device according to claim 2, wherein the third query message includes resource configuration for the reader wireless device to communicate with the one or more AIoT devices.

4. The reader wireless device of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code to cause the reader wireless device to: Send the AIoT device data to the network entity.

5. The reader wireless device of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code to cause the reader wireless device to: The second query message is retransmitted to the first AIoT device at least in part based on the reader wireless device's failure to receive the second response message.

6. The reader wireless device of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code to cause the reader wireless device to: The second query message is resent to the first AIoT device after the defined duration.

7. The reader wireless device of claim 1, wherein the second response message further includes indication information indicating the category of the first AIoT device, the capabilities of the first AIoT device, the energy state of the AIoT device, data requests, or a combination thereof.

8. The reader wireless device of claim 7, wherein the one or more processors are individually or jointly further operable to execute the code to cause the reader wireless device to: In response to receiving the second response message, a fourth query message is sent to the first AIoT device, the fourth query message indicating a second resource allocation in part based on the indication information.

9. The reader wireless device of claim 1, wherein the resource allocation is based on contention-based resources or contention-free resources.

10. The reader wireless device of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code to cause the reader wireless device to: In response to receiving a quantity first response message from the one or more AIoT devices, the number of AIoT devices within the coverage area of ​​the reader wireless device is determined; and The resource allocation is determined at least in part based on the number of AIoT devices.

11. The reader wireless device of claim 1, wherein the preamble indicates the category of the first AIoT device, the capabilities of the first AIoT device, data requirements, or a combination thereof.

12. The reader wireless device of claim 1, wherein the first response message is one of a set of predefined preamble messages, each of the predefined preamble messages indicating the category of the first AIoT device, the capabilities of the first AIoT device, data requirements, or a combination thereof.

13. The reader wireless device according to claim 1, wherein: The first query message is a wake-up signaling message.

14. An environmental Internet of Things (AIoT) wireless device, the environmental Internet of Things (AIoT) wireless device comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the environment's Internet of Things (AIoT) wireless device: Receive a first query message associated with powering on the AIoT device from the reader wireless device; In response to receiving the first query message, a first response message is sent to the reader wireless device indicating a preamble for AIoT device access; At least in part, the second query message indicating resource allocation is received from the reader wireless device based on sending the first response message; as well as In response to receiving the second query message, a second response message indicating an AIoT device identifier and AIoT device data is sent to the reader wireless device, wherein the second response message uses resources corresponding to the resource allocation.

15. The AIoT wireless device of claim 14, wherein the second response message further includes indication information indicating the category of the AIoT device, the capabilities of the AIoT device, the energy state of the AIoT device, data requests, or a combination thereof.

16. The AIoT wireless device of claim 15, wherein the one or more processors are individually or jointly further operable to execute the code to cause the AIoT wireless device to: The fourth query message is received from the reader wireless device at least in part based on sending the second response message, the fourth query message being in part based on the indication information to indicate a second resource allocation.

17. The AIoT wireless device of claim 14, wherein the resource allocation is based on contention-based resources or contention-free resources.

18. The AIoT wireless device of claim 14, wherein the preamble indicates the category of the AIoT device, the capabilities of the AIoT device, data requirements, or a combination thereof.

19. The AIoT wireless device of claim 14, wherein the first response message is one of a set of predefined preamble messages, each of the predefined preamble messages indicating the category of the AIoT device, the capabilities of the AIoT device, data requirements, or a combination thereof.

20. The AIoT wireless device according to claim 14, wherein: The first query message is a wake-up signaling message.

21. A method for wireless communication by a reader wireless device, the method comprising: Send a first query message associated with powering on one or more Ambient Internet of Things (AIoT) devices within the coverage area of ​​the reader wireless device; At least in part, based on sending the first query message to receive a first AIoT device among the one or more AIoT devices, an indication of a preamble for AIoT device access; In response to receiving the first response message, a second query message instructing resource allocation is sent to the first AIoT device; and At least in part, the second response message is received from the first AIoT device, indicating an AIoT device identifier and AIoT device data, based on sending the second query message, wherein the second response message is received on a resource corresponding to the resource allocation.

22. The method according to claim 21, further comprising: The second query message is retransmitted to the first AIoT device at least in part based on the reader wireless device's failure to receive the second response message.

23. The method according to claim 21, further comprising: The second query message is resent to the first AIoT device after the defined duration.

24. The method of claim 21, wherein the second response message further includes indication information indicating the category of the first AIoT device, the capabilities of the first AIoT device, the energy state of the AIoT device, data requests, or a combination thereof.

25. The method according to claim 24, further comprising: In response to receiving the second response message, a fourth query message is sent to the first AIoT device, the fourth query message indicating a second resource allocation in part based on the indication information.

26. The method of claim 21, wherein the preamble indicates the category of the first AIoT device, the capabilities of the first AIoT device, data requirements, or a combination thereof.

27. A method for wireless communication by an Ambient Internet of Things (AIoT) wireless device, the method comprising: Receive a first query message associated with powering on the AIoT device from the reader wireless device; In response to receiving the first query message, a first response message is sent to the reader wireless device indicating a preamble for AIoT device access; At least in part, the second query message indicating resource allocation is received from the reader wireless device based on sending the first response message; as well as In response to receiving the second query message, a second response message indicating an AIoT device identifier and AIoT device data is sent to the reader wireless device, wherein the second response message uses resources corresponding to the resource allocation.

28. The method of claim 27, wherein the second response message further includes indication information indicating the category of the AIoT device, the capabilities of the AIoT device, the energy state of the AIoT device, data requirements, or a combination thereof.

29. The method of claim 27, wherein the preamble indicates the category of the AIoT device, the capabilities of the AIoT device, data requirements, or a combination thereof.

30. The method of claim 27, wherein the first response message is one of a set of predefined preamble messages, each of the predefined preamble messages indicating the category of the AIoT device, the capabilities of the AIoT device, data requirements, or a combination thereof.

Images