Resource management for communication with ambient internet of things (AIOT) devices

Abstract

Methods, systems, and devices for wireless communication are described. According to the techniques described herein, a device (e.g., a reader) can receive an indication of resources for reading artificial intelligence of things (AIoT) data from an AIoT device and the device can receive signaling activating a subset of a first set of resources. The device can transmit a query to the AIoT device and receive a response from the AIoT device via the activated subset of resources, the response indicating AIoT data (e.g., collected by the AIoT device) of the AIoT device. In some cases, the device can receive signaling indicating a second set of resources for reporting the AIoT data to a network entity. In some cases, the device can transmit a request for the first set of resources, the activated subset of resources, the second set of resources, or any combination thereof.

Description

Technical Field

[0001] The following pertains to wireless communication, including resource management for communication with Ambient Internet of Things (AIoT) 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, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE).

[0003] Some wireless communication systems may include one or more Ambient Internet of Things (AIoT) devices (e.g., tag devices, backscatter UEs (BUEs), passive UEs (PUEs), passive Internet of Things (IoT) devices), which may be low-complexity and low-power (e.g., ultra-low power) devices that wirelessly transmit data. In some cases, transmitting AIoT data may increase the complexity within the wireless communication system and the likelihood of signal collisions. Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting resource management for communication with Ambient Internet of Things (AIoT) devices. For example, the described technology provides a device (e.g., a user equipment (UE), a network entity), which may be referred to as a "reader," for receiving an indication of a first set of resources for transmitting AIoT data between the AIoT device and the reader. The reader may additionally receive signaling activating a subset of resources in the first set of resources. For example, the reader may receive signaling activating resources in the first set of resources for communication between the device (e.g., the reader) and the AIoT device, these resources including one or more query resources and one or more response resources. The reader may send a query to the AIoT device (e.g., request) for AIoT data via the activated subset of resources, and may receive a response from the AIoT device (e.g., in response to the query) indicating AIoT data via the activated subset of resources. In some cases, if the reader is a UE, the reader may receive signaling indicating a second set of resources for transmitting AIoT data to a network entity. In some examples, the first resource set, the second resource set, or both may be associated with a dedicated radio bearer (e.g., a signaling radio bearer (SRB) or a data radio bearer (DRB)) used for AIoT data communication. Additionally or alternatively, the reader (e.g., the UE) may (e.g., to a network entity) send a request for the first resource set, a request indicating preferred resources to be included in the activated resource subset, a request for the second resource set, or any combination thereof, and the reader may receive, based on such request, an indication of activation of the first resource set, an indication of activation of a resource subset, or an indication of activation of the second resource set, respectively.

[0005] A method for wireless communication by a device is described. The method may include: conveying signaling for activating at least a subset of resources in a resource set for communication between the device and an AIoT device, the resource set including one or more query resources and one or more response resources; sending a query for AIoT data to the AIoT device via the query resources in the activated resource subset; and receiving an indication of the AIoT data from the AIoT device in response to the query and via the response resources in the activated resource subset.

[0006] A device for wireless communication is described. The device may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories (e.g., operative, communicative, functional, electronic, or electrical ground). The one or more processors may be able to operate individually or jointly to execute code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the device to: communicate signaling for activating at least a subset of resources in a resource set for communication between the device and an AIoT device, the resource set including one or more query resources and one or more response resources; send a query for AIoT data to the AIoT device via the query resources in the activated resource subset; and receive an indication of the AIoT data from the AIoT device in response to the query and via the response resources in the activated resource subset.

[0007] Another device for wireless communication is described. The device may include: components for conveying signaling for activating at least a subset of resources in a resource set for communication between the device and an AIoT device, the resource set including one or more query resources and one or more response resources; components for sending a query for AIoT data to the AIoT device via the query resources in the activated resource subset; and components for receiving an indication of AIoT data from the AIoT device in response to the query and via the response resources in the activated resource subset.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by at least one processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) to: convey signaling for activating at least a subset of resources in a resource set for communication between the device and an AIoT device, the resource set including one or more query resources and one or more response resources; sending a query for AIoT data to the AIoT device via the query resources in the activated resource subset; and receiving an indication for the AIoT data from the AIoT device in response to the query and via the response resources in the activated resource subset.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending AIoT information indicating AIoT data to a network entity based on a received instruction on AIoT data.

[0010] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving control signaling indicating a second set of resources associated with a dedicated radio bearer for the AIoT data, wherein the AIoT information may be transmitted via one or more resources in the second set of resources.

[0011] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, dedicated radio bearers include SRBs, DRBs, or both.

[0012] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, transmitting AIoT information indicating AIoT data may include operations, features, components, or instructions for transmitting AIoT information via a dedicated packet data unit (PDU) session associated with an AIoT service flow.

[0013] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing operations based on Radio Resource Control (RRC) idle or RRC inactive states, wherein AIoT information may be transmitted via a small data transmission scheme based on operations based on RRC idle or RRC inactive states.

[0014] In some examples of the methods, devices, and nontransitory computer-readable media described herein, AIoT information may be transmitted based on one or more configured time resources, one or more configured frequency resources, periodicity of uplink timing, modulation and decoding scheme (MCS), synchronization signal block (SSB), AIoT data size satisfying a threshold size, or any combination thereof.

[0015] Some examples of the methods, devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: operations based on an RRC idle state or an RRC inactive state; and establishing an RRC connection based on AIoT data and operations based on an RRC idle state or an RRC inactive state, wherein AIoT information may be transmitted based on the established RRC connection.

[0016] Some examples of the methods, devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving requests to query AIoT devices based on operations according to an RRC idle state or an RRC inactive state, wherein the query may be sent based on the request and an RRC connection may be established based on the request.

[0017] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the request includes an RRC recovery message, and the AIoT information includes an RRC recovery complete message.

[0018] In some examples of the methods, devices, and nontransitory computer-readable media described herein, the RRC connection may be further established based on a reason for establishment associated with an AIoT data report, a reason for recovery associated with an AIoT data report, or both.

[0019] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: operating according to an RRC connection state; storing the AIoT data in a data buffer; sending a buffer status report corresponding to the data buffer based on operating according to the RRC connection state; and receiving control signaling instructing one or more resources based on the buffer status report, wherein the AIoT information may be sent via one or more resources.

[0020] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: operating according to an RRC connection state; sending a Random Access (RACH) message requesting one or more resources for AIoT data transmission based on operating according to an RRC connection state; and receiving control signaling instructing the one or more resources based on the RACH message, wherein the AIoT information may be transmitted via one or more resources.

[0021] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending AIoT information indicating AIoT data to a core network entity based on received instructions regarding AIoT data.

[0022] Some examples of the methods, devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling that configures a set of resources for AIoT data reading, wherein signaling that activates at least a subset of the resources may be based on control signaling.

[0023] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, control signaling configures the transmit power for a query, the periodicity associated with one or more query resources, a first time resource associated with one or more query resources, a first frequency resource associated with one or more query resources, first beam information associated with one or more query resources, first code information associated with one or more query resources, a second time resource associated with one or more response resources, a second frequency resource associated with one or more response resources, a second beam information associated with one or more response resources, a second code information associated with one or more response resources, the number of repetitions of a query associated with a query session, a timer associated with a query session, or any combination thereof.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a request for resources for communication between the apparatus and the AIoT device, wherein receiving control signaling may be based on the request.

[0025] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the request may be sent based on a first amount of AIoT data to be reported, a second number of AIoT devices detected at the device, or both.

[0026] In some examples of the methods, devices, and nontransitory computer-readable media described herein, control signaling includes broadcast signaling, dedicated signaling for the device, or both.

[0027] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the set of resources used for communication between the device and the AIoT device may be shared for a set of multiple devices used for AIoT data reading, may be shared for a set of multiple AIoT devices, may be dedicated to the device for AIoT data reading, may be dedicated to the AIoT device, may be shared with non-AIoT communication, may be dedicated to AIoT data reading, or any combination thereof.

[0028] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, signaling that activates at least a subset of resources may include operations, features, components, or instructions for receiving RRC signaling, Media Access Control (MAC) Control Element (CE) signaling, Downlink Control Information signaling, Paging signaling, or any combination thereof that activates at least a subset of resources.

[0029] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: sending an indication to one or more preferred resources in a set of resources for communication between the apparatus and the AIoT device, wherein the activated subset of resources may be based on the indicated one or more preferred resources.

[0030] A method for wireless communication by a network entity is described. The method may include: sending a first signaling that configures a set of resources for communication between the device and an AIoT device, the resource set including one or more query resources and one or more response resources; sending a second signaling that activates at least a subset of resources in the resource set for the device; and receiving AIoT information indicating AIoT data associated with the AIoT device based on activating at least a subset of resources for the device.

[0031] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories (e.g., operative ground, communicative ground, functional ground, electronic ground, or electrical ground). The one or more processors may be able to operate individually or collectively to execute code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the network entity to: send a first signaling configuring a set of resources for communication between a device and an AIoT device, the resource set including one or more query resources and one or more response resources; send a second signaling to activate at least a subset of resources in the resource set for the device; and receive AIoT information indicating AIoT data associated with the AIoT device based on activating at least a subset of resources for the device.

[0032] Another network entity for wireless communication is described. This network entity may include: components for transmitting first signaling configuring a set of resources for communication between the device and an AIoT device, the resource set including one or more query resources and one or more response resources; components for transmitting second signaling for activating at least a subset of resources in the resource set for the device; and components for receiving AIoT information indicating AIoT data associated with the AIoT device based on activating at least a subset of resources for the device.

[0033] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by at least one processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) to: send a first signaling to configure a set of resources for communication between the device and an AIoT device, the resource set including one or more query resources and one or more response resources; send a second signaling to activate at least a subset of resources in the resource set for the device; and receive AIoT information indicating AIoT data associated with the AIoT device based on activating at least the subset of resources for the device.

[0034] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving a request for resources for communication between the device and the AIoT device, wherein a first signaling indicating a set of resources is sent, a second signaling activating at least a subset of resources is sent, or both may be based on the request.

[0035] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of one or more preferred resources from a set of resources for communication between the device and the AIoT device, wherein the activated subset of resources may be based on the indicated one or more preferred resources.

[0036] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: transmitting control signaling indicating a second set of resources associated with a dedicated radio bearer for receiving AIoT data, wherein the AIoT information indicating the AIoT data may be received via one or more resources in the second set of resources.

[0037] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending AIoT information indicating AIoT data to a core network entity based on AIoT information indicating AIoT data. Attached Figure Description

[0038] Figure 1 and Figure 2 An example of a wireless communication system supporting resource management for communication with environmental Internet of Things (AIoT) devices, according to one or more aspects of this disclosure, is shown.

[0039] Figure 3An example of a process flow supporting resource management for communication with AIoT devices, according to one or more aspects of this disclosure, is shown.

[0040] Figure 4 and Figure 5 A block diagram of a device supporting resource management for communication with AIoT devices, according to one or more aspects of this disclosure, is shown.

[0041] Figure 6 A block diagram of a communication manager supporting resource management for communication with AIoT devices, according to one or more aspects of this disclosure, is shown.

[0042] Figure 7 A diagram is shown of a system including a device that supports resource management for communication with AIoT devices, according to one or more aspects of this disclosure.

[0043] Figure 8 and Figure 9 A block diagram of a device supporting resource management for communication with AIoT devices, according to one or more aspects of this disclosure, is shown.

[0044] Figure 10 A block diagram of a communication manager supporting resource management for communication with AIoT devices, according to one or more aspects of this disclosure, is shown.

[0045] Figure 11 A diagram is shown of a system including a device that supports resource management for communication with AIoT devices, according to one or more aspects of this disclosure.

[0046] Figures 12 to 15 A flowchart illustrating a method for resource management supporting communication with AIoT devices, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0047] Some wireless communication systems may include one or more Ambient Internet of Things (AIoT) devices (e.g., tag devices, backscattered UEs (BUEs), passive UEs (PUEs), passive IoT devices), which may be relatively low-complexity and low-power (e.g., ultra-low-power) devices that wirelessly transmit AIoT data. In some cases, the AIoT device may be passive, such that it does not include active radio communication components. For example, the AIoT device may communicate by reflecting, refraction, backscattering, or otherwise modulating incident ambient radio signals (such as ambient radio signals from network entities or user equipment (UEs)). In some cases, one or more devices (e.g., UEs, network entities) operating as "readers" or "reader devices" may receive or otherwise read AIoT data from the AIoT device. For example, a reader may receive AIoT data via a query and response process that includes the AIoT device. However, due to the increased resource and signaling overhead in the wireless communication system, reading data from the AIoT device may potentially interfere with other communications, such as communications between other devices in the wireless communication system.

[0048] According to the techniques described herein, a reader device (e.g., a UE, a network entity) may receive an indication of a first set of resources for communicating AIoT data between an AIoT device and the reader device. The reader device may determine an active subset of resources within the first set of resources. For example, the reader device may receive signaling activating a subset of resources in the first set for communication between the reader device and one or more AIoT devices. The activated resources may include one or more query resources and one or more response resources. The reader device may send a query for AIoT data to the AIoT device via the activated subset of resources (e.g., via query resources) and may receive a response from the AIoT device (e.g., in response to the query message) indicating AIoT data via the activated subset of resources (e.g., via response resources). In some cases, if the reader device is a UE, the reader device may receive signaling indicating a second set of resources for sending AIoT data to a network entity. In some cases, the first set of resources, the second set of resources, or both may be associated with a dedicated radio bearer (e.g., a signaling radio bearer (SRB), a data radio bearer (DRB)) for AIoT data communication. Additionally or alternatively, the reader device (e.g., the UE) may (e.g., to a network entity) send a request for a first resource set, a request indicating preferred resources to be included in an activated subset of resources, a request for a second resource set, or any combination thereof. The reader device may receive, based on such a request, an indication for the first resource set, activation of a resource subset, or an indication for the second resource set.

[0049] 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 a process flow. The aspects of this disclosure are further illustrated and described by means of, and with reference to, apparatus diagrams, system diagrams, and flowcharts relating to resource management for communication with AIoT devices.

[0050] Figure 1 An example of a wireless communication system 100 supporting resource management for communication with AIoT devices 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.

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

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

[0053] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, or computing system may include disclosures that UE 115, network entity 105, device, equipment, or computing system is a node. 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.

[0054] 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. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

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

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

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

[0058] 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 of IAB node 104. (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.

[0059] 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 resource management for communication with AIoT devices as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0060] 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 unit, station, terminal, or client, etc. UE 115 may also include or be referred to as personal electronic devices, such as: cellular phones, personal digital assistants (PDAs), multimedia / entertainment devices (e.g., radios, MP3 players, or video devices), cameras, gaming devices, navigation / positioning devices (e.g., GNSS (Global Navigation Satellite System) devices based on, for example, GPS (Global Positioning System), BeiDou, GLONASS or Galileo, ground-based devices, etc.), tablet computers, laptop computers, personal computers, netbooks, smartbooks, personal computers, smart devices, wearable devices (e.g., smartwatches, smart clothing, smart glasses, virtual reality goggles, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), drones, robots / robotic devices, vehicles, vehicle equipment, meters (e.g., parking timers, electricity meters, gas meters, water meters), monitors, air pumps, electrical appliances (e.g., kitchen appliances, washing machines, dryers), location tags, medical / healthcare devices, implants, sensors / actuators, displays, or any other suitable devices configured to communicate via wireless or wired media. 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 can be implemented in a variety of objects such as appliances or vehicles, meters, etc.

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

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

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

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

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

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

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

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

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

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

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

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

[0073] Some UEs 115 (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 entities 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 UEs 115 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 charging. In one aspect, the techniques disclosed herein are applicable to MTC or IoT UEs. MTC or IoT UE can include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UE, NB-IoT (also known as CAT NB1) UE, and other types of UE. eMTC and NB-IoT can refer to future technologies that can evolve from or are based on these technologies. For example, eMTC can include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), and mMTC (massive MTC), while NB-IoT can include eNB-IoT (enhanced NB-IoT) and FeNB-IoT (further enhanced NB-IoT).

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

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

[0076] 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 this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, 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.

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

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

[0079] The wireless communication system 100 can also operate using the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0080] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency 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 frequency bands may be combined with component carriers operating with licensed frequency 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.

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

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

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

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

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

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

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

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

[0089] In some cases, the wireless communication system 100 may include an AIoT device 185 that can communicate with one or more devices via one or more resources 186. In some cases, the AIoT device may communicate via modulated incident signals, as described herein.

[0090] According to the techniques described herein, a device (e.g., UE 115, network entity 105) may receive an indication of a first set of resources for communicating AIoT data between AIoT device 185 and the device, and may receive signaling to activate a subset of resources in the first set of resources. For example, the device may receive signaling to activate a subset of resources in the first set of resources for communication between the device and AIoT device 185. The device (e.g., a reader) may send a query to AIoT device 185 for (e.g., request) AIoT data via the activated subset of resources, and may receive a response from AIoT device 185 (e.g., in response to the query message) indicating AIoT data via the activated subset of resources. The wireless communication system 100 may support radio resource management to enable the reader to communicate effectively with AIoT device 185. For example, radio resource management may improve the coexistence (e.g., reduce collisions) between AIoT data communication and other communications within the wireless communication system 100 (e.g., communication between UE 115 and network entity 105).

[0091] Figure 2 An example of a wireless communication system 200 supporting resource management for communication with AIoT devices, according to one or more aspects of this disclosure, is shown. In some cases, aspects of the wireless communication system 200 may be implemented as described herein. Figure 1The described aspects of the wireless communication system 100, or those that may be implemented therein, are relevant. For example, the wireless communication system 200 may include a core network 250, network entity 105-a, UE 115-a, and AIoT device 215, which may be, respectively, as described herein with respect to… Figure 1 Examples of the core network 130, network entity 105, UE 115, and AIoT device 185 described herein. In some cases, network entity 105-a, UE 115-a, and AIoT device 215 may perform communications associated with AIoT data via one or more configuration resources.

[0092] As used herein, the term "device" may refer to UE 115-a, network entity 105-a, or both. A "device" may operate as a "reader" or "reader device" that receives AIoT data from one or more AIoT devices 215. As used herein, the term "RAN" may refer to network entity 105-a, core network 250, or both. For example, a device that receives control signaling from the RAN may include network entity 105-a that receives control signaling from core network 250, UE 115-a that receives control signaling from network entity 105-a, or both.

[0093] In some cases, the wireless communication system 200 may include an AIoT device 215 (e.g., a tag, BUE, PUE), where the AIoT device 215 may be an example of a passive device. For example, the AIoT device 215 may not be equipped with active RF components. In some cases, the AIoT device 215 may perform data transmission (e.g., conveying AIoT data) based on modulating incident RF signals transmitted by one or more environmental transmitters (e.g., UE 115-a, network entity 105-a, other UE 115, other network entity 105). For example, the AIoT device 215 may reflect, refract, backscatter, or otherwise modulate incident environmental radio signals to convey AIoT data to the device. In some cases, the AIoT device 215 may additionally or alternatively use environmental RF signals as an energy resource for harvesting energy.

[0094] As an example, a device implementing Radio Frequency Identification (RFID) technology can be considered an AIoT device. However, RFID devices may be associated with a relatively short read range (e.g., a few meters). For instance, to receive AIoT data from an RFID device, the reader device may be located within the relatively short read range of the RFID device. This relatively short read range can make large-scale deployment of RFID devices with seamless coverage challenging. Wireless communication system 200 can leverage different designs of IoT devices that enable ambient power to improve AIoT device coverage.

[0095] In some cases, Internet of Things (IoT) devices (e.g., where AIoT devices are a subset) may have one or more categories. For example, a first category of IoT devices (e.g., Type A devices) may include IoT devices without batteries (e.g., without energy storage capacity) and therefore may rely on an external power source. A second category of IoT devices (e.g., Type B devices) may include devices with relatively limited energy storage (e.g., supercapacitors or conventional capacitors), where the relatively limited energy storage may not be manually replaced or recharged (e.g., instead charged by solar energy or environmental signaling). A third category of IoT devices (e.g., Type C devices) may include IoT devices that may have typical energy storage capacity (e.g., similar to UE 115) and may be able to perform normal data communication (e.g., RF data communication, sending RF signaling). In some cases, AIoT device 215 may be classified into a first category, a second category, a third category, or may support different modes corresponding to any combination thereof.

[0096] In some cases, the wireless communication system 200 may support one or more topologies for AIoT communication within the wireless communication system. For example, in a first topology (e.g., topology 1), network entity 105-a may directly read AIoT data from AIoT device 215. For instance, network entity 105-a may send a query 235-a to AIoT device 215 and may receive a response 240-a from AIoT device 215 to the query 235-a, the response 240-a indicating the AIoT data from AIoT device 215.

[0097] In the second topology, network entity 105-a can indirectly read AIoT data from AIoT device 215 via one or more intermediate nodes. For example, the one or more intermediate nodes may include any device capable of communicating with AIoT device 215, including repeaters, IAB devices, repeaters, UE 115 (e.g., including UE 115-a), or any combination thereof. For example, UE 115-a can read AIoT data from AIoT device 215 by sending a query 235-b to AIoT device 215 (e.g., in some cases, based on receiving a query request 230 from network entity 105-a) and receiving a response 240-b indicating AIoT data from AIoT device 215. UE 115-a may send AIoT information 245, including AIoT data, read from AIoT device 215 to network entity 105-a. In some cases, the second topology may support applications such as smart homes, UE-based inventory, UE-based tracking, or any combination thereof.

[0098] In some cases, the wireless communication system 200 may include initiator 205, initiator 210, or both. For example, initiator 205 or initiator 210 may request to read AIoT data from AIoT device 215. In a first case (e.g., topology 2a), initiator 205 may provide input (e.g., connected to network entity 105-a via the core network) to core network 250 (e.g., a core network entity), network entity 105-a, or both to read AIoT data. In the first case, the request for reading can be transmitted to UE 115-a via core network 250 and network entity 105-a. Therefore, core network 250 may identify uplink traffic arising from the read request (e.g., including query signaling, response signaling, and AIoT data signaling) and may route the read request to UE 115-a.

[0099] In the second scenario, the initiator 210 may be a user of UE 115-a and may request read access to AIoT device 215. In some examples of this second scenario, the read request may be scheduled by core network 250, network entity 105-a, or both (e.g., based on a resource request from UE 115-a). For example, core network 250, network entity 105-a, or both may communicate authentication, accounting, or signaling associated with the requested read access (e.g., this signaling may occur infrequently). Additionally or alternatively, network entity 105-a and UE 115-a may communicate one or more resources or configurations for the requested read access, wherein the number or overhead of these communications may be reduced via configuration at network entity 105-a, configuration at UE 115-a, or both. Therefore, core network 250 may identify uplink traffic arising from a read request (e.g., including signals, AIoT data) and may route the read request to UE 115-a.

[0100] As described herein, a device in the wireless communication system 200 (e.g., a reader, a reader device) can read AIoT data from the AIoT device 215. The device can read the data by sending a query 235 to the AIoT device 215 and receiving a response 240. In some cases, this may be referred to as a query / response process or reading AIoT data. In some cases, the query / response process may include one or more iterations of sending a query 235 to the AIoT device 215, receiving a response 240 from the AIoT device, or both.

[0101] The device can read AIoT data from the AIoT device via a resource set (e.g., dedicated resources, configuration resources), which includes one or more query resources and one or more response resources. For example, query resources can be configured to convey a query 235 for AIoT data, and response resources can be configured to convey a response 240 that includes or otherwise indicates AIoT data. The device can send query 235 via a query resource or a set of query resources among one or more query resources, and can receive response 240 via a response resource or a set of response resources among one or more response resources. In some cases, the RAN (e.g., core network 250, network entity 105-a) can send a resource configuration 225 to the device (e.g., network entity 105-a, UE 115-a) indicating a resource set configured for the device to read AIoT data from the AIoT device 215. In some cases, the resource set may include one or more resources otherwise used for uplink, sidelink, or both.

[0102] The RAN can configure one or more aspects of the resource set via resource configuration 225. For example, resource configuration 225 can configure transmit power for query 235, periodicity associated with one or more query resources, time resources associated with one or more query resources, frequency resources associated with one or more query resources, beam information (e.g., beam weights, beam directions) associated with one or more query resources, code information (e.g., modulation and decoding scheme (MCS) index) associated with one or more query resources, or any combination thereof. Additionally or alternatively, resource configuration 225 can configure time resources associated with one or more response resources, frequency resources associated with one or more response resources, beam information associated with one or more response resources, code information associated with one or more response resources, or any combination thereof.

[0103] Additionally or alternatively, resource configuration 225 may indicate the number of repetitions of query 235 associated with a query session, wherein the query session may be a time duration for sending one or more instances of query 235. Resource configuration 225 may also indicate the time duration of the query session (e.g., a timer, a window). For example, a device, AIoT device 215, or both may initiate a query session and may terminate the query session within (or after) the time duration from the start of the query session.

[0104] In some cases, the RAN may send resource configuration 225 (e.g., configuring a resource set to a device) via one or more signaling methods. For example, the RAN may indicate a resource set (e.g., shared resources) to a device via broadcast signaling, where one or more other devices (e.g., other UE 115, other network entity 105) may also receive the indication of the resource set. Additionally or alternatively, the RAN may indicate a resource set (e.g., dedicated resources) to a device via dedicated signaling directed to the device (e.g., DCI message reception, System Information (SI) signaling). For example, the RAN may send RRC signaling, MAC control element (CE), DCI, or any combination thereof indicating resource configuration 225.

[0105] In some cases, various devices may use a resource set. For example, a resource set may be shared (e.g., collectively owned) by one or more devices (e.g., including the device) to read AIoT data from one or more AIoT devices 215. As another example, a resource set may be dedicated to a device (e.g., dedicated only to the device) for reading AIoT data from one or more AIoT devices 215. For example, if communication between the device and AIoT device 215 has a relatively high priority (e.g., associated with a relatively high risk of slow or failed communication), the resource set may be dedicated to reducing latency and improving the reliability of AIoT data reading.

[0106] In some cases, resource sets can support various communications. For example, a resource set can be shared with other non-AIoT communication purposes (e.g., shared), or it can be dedicated solely to AIoT communication purposes. If a resource set is dedicated to AIoT communication purposes, it can be dedicated to that device or shared among one or more devices (e.g., as described above). In some cases, dedicating a resource set to a device for reading AIoT data can result in reduced uplink interference from other devices.

[0107] As described herein, the RAN may indicate a set of resources to a device (e.g., a reader), and the RAN may activate (e.g., indicate activation) a subset of resources in the configured set of resources for the reader to use to read AIoT data. For example, the RAN may indicate (e.g., configure) a set of resources (e.g., a resource pool) to the device, and may indicate one or more indices corresponding to one or more resources in the set of resources to be activated as part of the activation subset.

[0108] The RAN can indicate a resource set and activate a resource subset via one or more methods. In one example, the RAN can indicate a resource set to the reader via resource configuration 225 and can activate the resource subset (e.g., or deactivate other resources) using lower-layer (e.g., Layer 1 (L1), Layer 2 (L2)) dedicated signaling. In another example, the RAN can broadcast the resource set to multiple devices including the device (e.g., via a System Information Block (SIB)) and can indicate activated (e.g., deactivated) resources by sending one or more paging messages to the device. In some cases, the RAN can configure a common resource set for AIoT communication and can activate a specific resource subset for a particular reader from the common resource set. In some cases, the RAN can send a paging message based on a query for AIoT device 215 determined by the RAN. In some cases, the device can send an indication of one or more preferred resources in the resource set for activation, and the RAN can send a resource activation to the device based on the preferred resources to activate a resource subset, such that the subset may include one or more preferred resources among the preferred resources.

[0109] In some cases, the reader may request a set of resources from the RAN via resource request 220 (e.g., before reading AIoT data from AIoT device 215). For example, the device may request one or more time resources, frequency resources, beam resources (e.g., beam weights, beam directions, beam codebooks), code fields (e.g., MCS indexes), or any combination thereof from the RAN for reading AIoT data. In some cases, the device may send resource request 220 to the RAN based on the lack of resources configured for the device or activated for reading AIoT data for the device.

[0110] In some other cases, the device may be configured using one or more resources for reading AIoT data, but additional resources may be requested via resource request 220 based on, for example, detecting a large number of AIoT devices for reading AIoT data. For example, the device may detect (e.g., determine that it is operable) the number of AIoT devices (e.g., including AIoT device 215) within the reader's AIoT reading range that meets a threshold number of AIoT devices. The reader may send resource request 220 to the RAN based on the number of AIoT devices meeting (e.g., exceeding) the threshold number of AIoT devices. In some cases, a relatively large number of AIoT devices may result in a relatively large amount of AIoT data to be read by the device. The device may request additional resources via resource request 220 to handle the relatively large amount of AIoT data. Additionally or alternatively, the device may send resource request 220 based on detecting or otherwise determining that the amount of AIoT data to be read meets (e.g., exceeds) a threshold amount of AIoT data.

[0111] The device can send query 235 to AIoT device 215 having unaudited AIoT data to be reported via an activated subset of resources (e.g., a query resource). AIoT device 215 can send or otherwise transmit at least a portion of the unaudited AIoT data to the device via response 240 (e.g., via the activated subset of resources (e.g., a response resource)). In some examples, AIoT device 215 may use reflection, refraction, backscattering, transmission, or any other technique to transmit AIoT data to the reader (e.g., via response 240). In some cases, the activated resource can be an example of a query resource, a response resource, or both (e.g., it may support either or both of query 235 and response 240).

[0112] The device (e.g., a reader) can report AIoT data to the RAN (e.g., after reading AIoT data from AIoT device 215). For example, the device can report AIoT information 245 to the RAN, where AIoT information 245 includes AIoT data. If the device is network entity 105-a, the device can send AIoT information 245 directly to the core network 250.

[0113] In some cases, the device can handle the communication of AIoT information 245 in a manner similar to how the device can handle the communication of user payloads. For example, the device can report AIoT information 245 to the RAN via user plane signaling, upper-layer signaling, application layer signaling, control plane signaling, non-access stratum (NAS) signaling, or any combination thereof. The device can generate signaling indicating AIoT information 245 based on AIoT data read from AIoT device 215. In some cases, the device configuration, the application layer associated with the device, or both can specify the format used to report AIoT information 245.

[0114] In some cases, the reader may report AIoT information to the RAN via reporting resources (e.g., configuration resources, a second resource set). For example, reporting resources may include dedicated radio bearers for AIoT data reporting (e.g., delivery). In some cases, the dedicated radio bearer may be a dedicated signaling radio bearer (SRB) (e.g., for RRC and NAS signaling). As another example, the dedicated radio bearer may be a dedicated AIoT data radio bearer (DRB). Additionally or alternatively, the device may transmit AIoT information via a dedicated (e.g., special) Packet Data Unit (PDU) session, allowing the RAN to monitor the traffic flow of AIoT information (e.g., the amount of reported AIoT data) based on the dedicated PDU session.

[0115] In some cases (e.g., if the device is operating in an RRC inactive state), reporting resources may include one or more configured (e.g., pre-configured) resources associated with reporting AIoT data. For example, reporting resources may include one or more configured time resources, one or more configured frequency resources, periodicity of uplink timing for reporting AIoT data, MCS for reporting AIoT data, or any combination thereof. Reporting resources may additionally or alternatively indicate a synchronization signal block associated with the uplink timing, enabling the device to monitor and synchronize with the synchronization signal block. Additionally or alternatively, reporting resources may indicate a threshold size for AIoT data. For example, if the size of the AIoT data to be reported is below a threshold size, the device may transmit AIoT data while operating in an RRC inactive state.

[0116] In some cases, a device (e.g., UE 115-a) may report AIoT information 245 to the RAN when operating in RRC connected state (e.g., RRC_CONNECTED). In RRC connected state, the device may send a buffer status report to the RAN to request reporting resources (e.g., uplink resources) for reporting AIoT data. For example, the buffer status report may be associated with a buffer used to store AIoT data at the device. Additionally or alternatively, when operating in RRC connected state, the device may send a random access (RACH) message to the RAN to request reporting resources.

[0117] In some cases, the device can read AIoT data and report AIoT information to the RAN while operating in an RRC inactive state (e.g., RRC_INACTIVE, RRC_IDLE). For example, when operating in an RRC inactive state, the device can receive a query request 230 from the RAN, for example, as part of an RRC recovery message. The device can establish an RRC connection with the RAN based on the RRC recovery message (e.g., before or after completing the reading of AIoT data from AIoT device 215), and can include the AIoT data in an RRC recovery completion message sent to the RAN in association with establishing the RRC connection.

[0118] In some cases, the reader can establish or restore an RRC connection with the RAN (e.g., enter RRC_CONNECTED mode, perform an RRC establishment or RRC recovery procedure from an RRC inactive state) to report AIoT data. In some such cases, the device can indicate the reason for establishing or restoring the RRC connection (e.g., access reason, recovery reason, establishment reason), where the reason can be for AIoT services (e.g., for reporting AIoT data). In some cases, the reason value can indicate AIoT data. The reader can include the indication of the reason in an RRC establishment message, an RRC recovery message, or some other RRC message.

[0119] Figure 3 An example of a process flow 300 supporting resource management for communication with AIoT devices, according to one or more aspects of this disclosure, is shown. In some cases, aspects of process flow 300 may be implemented as described in the reference. Figure 1 and Figure 2 The described aspects of the wireless communication system, or those that can be implemented therein, are relevant. For example, process flow 300 may include network entity 105-b, UE 115-b, and AIoT device 315, which may be respectively as described herein with respect to… Figure 1 and Figure 2 Examples of network entity 105, UE 115, and AIoT devices (e.g., AIoT device 185, AIoT device 215) described herein. Additionally, UE 115-b may be as described herein with respect to... Figure 1 and Figure 2 Examples of the described devices (e.g., reader devices). In some cases, UE 115-b, network entity 105-b, and AIoT device 315 may communicate signaling associated with AIoT data based on one or more sets of configuration resources.

[0120] In the following description of process flow 300, operations may be performed in a different order than those shown, or other operations may be added to or removed from process flow 300. For example, some operations may be omitted from process flow 300, some operations may be performed in a different order or at different times, or other operations may be added to process flow 300. Although UE 115-b and network entity 105-b are shown as performing operations of process flow 300, some aspects of some operations may also be performed by one or more other wireless devices or network devices. For example, operations performed by UE 115-b may alternatively be performed by network entity 105, and operations performed by network entity 105-b may alternatively be performed by core network 130 (e.g., as described herein with respect to...). Figure 1 (As described).

[0121] At 320, UE 115-b may transmit signaling to request resources for AIoT data communication. UE 115-b may request the RAN to: configure a set of resources for AIoT data communication, activate at least a subset of resources in that set for communication between UE 115-b and AIoT device 315, or both. For example, UE 115-b may send a request for resources for communication between UE 115-b and AIoT device 315 (e.g., to network entity 105-b). In some cases, UE 115-b may send the request based on a first amount of AIoT data to be reported, a second number of AIoT devices detected at the device (e.g., by the device) (e.g., including AIoT device 315), or both. For example, UE 115-b may send the request if it can access (e.g., is storing, and can be received via query / response) a certain amount of AIoT data that meets a threshold amount of AIoT data. Additionally or alternatively, if UE 115-b detects (e.g., determines to be operational) a certain number of AIoT devices (e.g., including AIoT device 315) within the area that meet the threshold number of AIoT devices, UE 115-b may send the request.

[0122] Additionally or alternatively, UE 115-b may (e.g., to network entity 105-b) send indications of one or more preferred resources from a set of resources for communication between UE 115-b and AIoT device 315. For example, UE 115-b may prefer one or more resources from a first set of resources based on one or more metrics associated with UE 115-b and AIoT device 315. For example, one or more metrics may include the location of UE 115-b, AIoT device 315, or both; the communication technology implemented by UE 115-b, AIoT device 315, or both (e.g., 4G, 5G, 6G); or a combination thereof.

[0123] At position 325, network entity 105-b may send control signaling to UE 115-b (e.g., as described herein relative to...). Figure 2 The described resource configuration 225) indicates that the control signaling may indicate information associated with resources used for communication related to AIoT data. In some cases, receiving control signaling is based on a request sent by UE 115-b at 320. Additionally or alternatively, UE 115-b may receive control signaling via broadcast signaling, dedicated signaling for UE 115-b, or both.

[0124] In some cases, control signaling may include one or more control messages. For example, as part of control signaling, network entity 105-b may send (e.g., and UE 115-b may receive) a first signaling that indicates (e.g., configures) a set of resources for communication between UE 115-b and AIoT device 315. In some cases, the resource set may include one or more query resources and one or more response resources, as described herein with respect to... Figure 2 As described. As part of control signaling, network entity 105-b may also send (e.g., and UE 115-b may receive) a second signaling that activates at least a subset of resources in the resource set (e.g., indicates activation of the at least subset of resources) for UE 115-b to use for communication between UE 115-b and AIoT device 315. In some cases, the activated subset of resources may be based on one or more indicated preferred resources.

[0125] Control signaling can configure one or more aspects of communication (e.g., resources) between UE 115-b and AIoT device 315. For example, control signaling can configure transmit power for queries against AIoT data from UE 115-b to AIoT device 315, periodicity associated with one or more query resources, time resources associated with one or more query resources, frequency resources associated with one or more query resources, beam information (e.g., beam weight, beam direction, beam codebook) associated with one or more query resources, code information (e.g., MCS index) associated with one or more query resources, or any combination thereof. Control signaling can additionally or alternatively configure time resources associated with one or more response resources, frequency resources associated with one or more response resources, beam information associated with one or more response resources, code information associated with one or more response resources, the number of repetitions of queries associated with a query session, timers associated with a query session, or any combination thereof (e.g., as described herein with respect to...). Figure 2 (As described).

[0126] In some cases, the resource set used for communication between UE 115-b and AIoT device 315 may be shared by multiple devices (e.g., UE 115, network entity 105, or a combination thereof) for AIoT data reading, shared by multiple AIoT devices (e.g., including AIoT device 315), or both. Additionally or alternatively, the resource set may be dedicated to AIoT data reading by UE 115-b, may be dedicated to AIoT device 315, may be shared with non-AIoT communication, may be dedicated to AIoT data reading, or any combination thereof.

[0127] As described herein, control signaling may include signaling that activates at least a subset of resources in the resource set for communication associated with AIoT data. In some cases, signaling that activates at least a subset of resources may include RRC signaling, MAC-CE signaling, DCI signaling, paging signaling, or any combination thereof.

[0128] At 330, UE 115-b may receive (e.g., from network entity 105-b) a request to AIoT device 315 to query AIoT data. In some cases, UE 115-b may receive the query request based on operation according to an RRC idle state or an RRC inactive state. Additionally or alternatively, UE 115-b may establish an RRC connection (e.g., with network entity 105-b) based on receiving the request. In some cases, the request may include an RRC recovery message.

[0129] At 335, UE 115-b can send a query for AIoT data to AIoT device 315. For example, UE 115-b can send a query based on a request to send a query. UE 115-b can send a query to AIoT device 315 via one or more query resources in the activated subset of resources.

[0130] At 340, UE 115-b may receive (e.g., in response to a query) an indication of AIoT data from AIoT device 315. AIoT device 315 may transmit (e.g., send, indicate, signal notification) the indication of AIoT data to UE 115-b via one or more response resources in an activated subset of resources. In some cases, the indication of AIoT data may be transmitted to UE 115-b via one or more methods, including reflecting, refraction, backscattering, or otherwise modulating incident ambient radio signals, such as ambient radio signals from network entity 105-b, UE 115-b, other network entity 105, other UE 115, or any combination thereof.

[0131] At 345, UE 115-b can store AIoT data in a data buffer. For example, the data buffer can be dedicated to AIoT data, or it can be shared for both AIoT data and other data (e.g., it can store AIoT data and other types of data, such as uplink data). In some cases, UE 115-b can store AIoT data in the data buffer based on its RRC connection state (e.g., RRC_CONNECTED).

[0132] At 350, UE 115-b may send a request for reporting resources (e.g., resources for transmitting AIoT data to network entity 105-b). In some cases, the request for reporting resources may include a buffer status report corresponding to a data buffer used to store AIoT data. In some cases (e.g., when UE 115-b is operating in RRC connected state), the request for reporting resources may include a RACH message requesting one or more resources for transmitting AIoT data.

[0133] At 355, UE 115-b may receive control signaling indicating a second resource set (e.g., a reporting resource) for transmitting AIoT data from UE 115-b to network entity 105-b. In some cases, the second resource set may be associated with a dedicated radio bearer for AIoT data, wherein the dedicated radio bearer may include an SRB, DRB, or both. In some cases, UE 115-b may receive control signaling indicating the second resource set based on a buffer status report. For example, if a buffer status report indicates that UE 115-b is storing a certain amount of AIoT data that satisfies a threshold amount of AIoT data, network entity 105-b may send control signaling indicating the second resource set to UE 115-b. Additionally or alternatively, UE 115-b may receive control signaling indicating one or more resources based on network entity 105-b receiving a RACH message from UE 115-b.

[0134] At 360, UE 115-b may (e.g., to network entity 105-b) send AIoT information indicating AIoT data. For example, UE 115-b may send AIoT information to network entity 105-b based on receiving an indication of AIoT data from AIoT device 315 and via one or more resources in a second resource set. Additionally, network entity 105-b may receive AIoT information indicating AIoT data associated with AIoT device 315 based on activating at least a subset of resources for UE 115-b, because UE 115-b may receive the indication of AIoT data via one or more resources in the activated resource subset.

[0135] UE 115-b may transmit AIoT information to network entity 105-b via one or more methods. For example, UE 115-b may transmit AIoT information via a dedicated PDU session (e.g., a special PDU session) associated with the AIoT service flow. For example, network entity 105-b may monitor the service flow status of AIoT information based on the dedicated PDU session. In some cases, UE 115-b may transmit AIoT information via a small data transmission scheme, for example, based on UE 115-b's operation according to RRC idle state or RRC inactive state. For example, UE 115-b may transmit AIoT information via a small data transmission scheme to reduce signaling overhead, allow UE 115-b to avoid moving to an RRC connected state, reduce UE 115-b's power consumption, or any combination thereof.

[0136] Alternatively or additionally, UE 115-b may establish an RRC connection (e.g., with network entity 105-b) based on receiving an indication of AIoT data from AIoT device 315, operating according to an RRC idle state or an RRC inactive state, or both. Alternatively or additionally, UE 115-b may establish an RRC connection based on an establishment reason associated with an AIoT data report, a recovery reason associated with an AIoT data report, or both.

[0137] UE 115-b can send AIoT information based on the establishment of an RRC connection. For example, in some cases (e.g., if a request from network entity 105-b to AIoT device 315 for querying UE 115-b includes an RRC recovery message), UE 115-b can send AIoT information to network entity 105-b via an RRC recovery completion message corresponding to the completion of the establishment of the RRC connection.

[0138] In some cases, UE 115-b may transmit AIoT information based on one or more configuration parameters (e.g., configured by network entity 105-b to UE 115-b). For example, UE 115-b may transmit AIoT information based on one or more aspects of a second resource set (e.g., reporting resources). For example, UE 115-b may transmit AIoT information based on (e.g., and the second resource set may be configured to indicate) one or more configured time resources, one or more configured frequency resources, periodicity of uplink timing, MCS, synchronization signal block, data size of AIoT information satisfying a threshold size, or any combination thereof.

[0139] In some cases, network entity 105 can operate as a reader for AIoT device 315. Network entity 105-b can send (e.g., to core network 130) AIoT information indicating AIoT data based on an indication received from AIoT device 315 for AIoT data.

[0140] For example, at 365, network entity 105-b can send queries directly to AIoT device 315. Network entity 105-b can also send queries via query resources that are activated for a subset of resources (e.g., those activated for network entity 105-b).

[0141] At 370, network entity 105-b may receive instructions for AIoT data from AIoT device 315 (e.g., in response to a query and via a response resource in an activated subset of resources). Network entity 105-b may send AIoT information, including the AIoT data, to core network 130.

[0142] Figure 4 A block diagram 400 of a device 405 supporting resource management for communication with AIoT devices according to one or more aspects of this disclosure is shown. Device 405 may be an example of aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Device 405, or one or more components of device 405 (e.g., receiver 410, transmitter 415, and communication manager 420), may include at least one processor that 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).

[0143] Receiver 410 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 resource management for communication with AIoT devices). The information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0144] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to resource management for communication with AIoT devices). In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0145] The communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of resource management for communication with AIoT devices as described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0146] In some examples, the communication manager 420, receiver 410, transmitter 415, 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).

[0147] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in software (e.g., code executed by the processor) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, graphics processing unit (GPU), neural processing unit (NPU), ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

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

[0149] According to the examples disclosed herein, the communication manager 420 may support wireless communication. For example, the communication manager 420 may be capable of, configured to, or operable to support components for performing the following operations: transmitting signaling for activating at least a subset of resources in a resource set for communication between the device and the AIoT device, the resource set including one or more query resources and one or more response resources. The communication manager 420 may be capable of, configured to, or operable to support components for performing the following operations: sending a query for AIoT data to the AIoT device via a query resource in the activated resource subset. The communication manager 420 may be capable of, configured to, or operable to support components for performing the following operations: receiving an indication of AIoT data from the AIoT device in response to the query and via a response resource in the activated resource subset.

[0150] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., controlling receiver 410, transmitter 415, communication manager 420, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for more efficient utilization of communication resources. For example, a reader (e.g., UE 115, network entity 105) implementing the techniques described herein can communicate with AIoT devices via resources configured for the purpose of communicating with AIoT devices, which can increase the reliability of communication and reduce communication errors. Therefore, the techniques described herein can provide more efficient utilization of communication resources (e.g., due to reduced interference and communication errors). Device 405 can correspondingly reduce the processing resources associated with retransmissions for AIoT data reading.

[0151] Figure 5 A block diagram 500 of a device 505 supporting resource management for communication with AIoT devices according to one or more aspects of this disclosure is shown. Device 505 may be an example of aspects of device 405 or 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 that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0152] 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 resource management for communication with AIoT devices). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0153] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to resource management for communication with AIoT devices). 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.

[0154] Device 505 or its various components may be examples of parts for performing various aspects of resource management for communication with AIoT devices as described herein. For example, communication manager 520 may include AIoT resource configuration component 525, AIoT query component 530, AIoT response component 535, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use receiver 510, transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or integrate in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0155] According to the examples disclosed herein, the communication manager 520 may support wireless communication. The AIoT resource configuration component 525 is capable of, configured to, or operable to support components for performing the following operations: transmitting signaling for activating at least a subset of resources in a resource set for communication between the device and the AIoT device, the resource set including one or more query resources and one or more response resources. The AIoT query component 530 is capable of, configured to, or operable to support components for performing the following operations: sending a query for AIoT data to the AIoT device via a query resource in the activated resource subset. The AIoT response component 535 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication of AIoT data from the AIoT device in response to a query and via a response resource in the activated resource subset.

[0156] Figure 6 A block diagram 600 is shown of a communication manager 620 supporting resource management for communication with AIoT devices according to one or more aspects of this disclosure. The communication manager 620 may be an example of aspects of the communication manager 420, communication manager 520, or both as described herein. The communication manager 620 or its various components may be examples of parts for performing various aspects of resource management for communication with AIoT devices as described herein. For example, the communication manager 620 may include an AIoT resource configuration component 625, an AIoT query component 630, an AIoT response component 635, an AIoT information component 640, an operation status component 645, an RRC connection component 650, an AIoT data buffer component 655, a random access component 660, 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).

[0157] According to the examples disclosed herein, the communication manager 620 may support wireless communication. The AIoT resource configuration component 625 is capable of, configured to, or operable to support components for performing the following operations: transmitting signaling for activating at least a subset of resources in a resource set for communication between the device and the AIoT device, the resource set including one or more query resources and one or more response resources. The AIoT query component 630 is capable of, configured to, or operable to support components for performing the following operations: sending a query for AIoT data to the AIoT device via a query resource in the activated resource subset. The AIoT response component 635 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication of AIoT data from the AIoT device in response to a query and via a response resource in the activated resource subset.

[0158] In some examples, the AIoT information component 640 is capable of, configured to perform, or is operable to support components for performing the following operations: sending AIoT information indicating AIoT data to network entities based on received indications of AIoT data.

[0159] In some examples, the AIoT resource configuration component 625 is capable of, configured to perform, or is operable to support components for performing the following operations: receiving control signaling indicating a second set of resources associated with a dedicated radio bearer for AIoT data, wherein the AIoT information is transmitted via one or more resources in the second set of resources.

[0160] In some examples, the dedicated radio bearer includes SRB, DRB, or both.

[0161] In some examples, in order to support the transmission of AIoT information indicating AIoT data, the AIoT information component 640 is capable of, configured to perform, or is operable to support components for performing the following operations: transmitting AIoT information via a dedicated PDU session associated with the AIoT service flow.

[0162] In some examples, the operation state component 645 is capable of, configured to perform, or is operable to support components for performing the following operations: operating according to an RRC idle state or an RRC inactive state, wherein AIoT information is transmitted via a small data transmission scheme based on operating according to an RRC idle state or an RRC inactive state.

[0163] In some examples, AIoT information is transmitted based on one or more configured time resources, one or more configured frequency resources, the periodicity of uplink timing, modulation and decoding schemes, synchronization blocks, the data size of AIoT data meeting a threshold size, or any combination thereof.

[0164] In some examples, the operation state component 645 is capable of, configured to perform, or is operable to support components for performing the following operations: operating according to an RRC idle state or an RRC inactive state. In some examples, the RRC connection component 650 is capable of, configured to perform, or is operable to support components for performing the following operations: establishing an RRC connection based on AIoT data and operating according to an RRC idle state or an RRC inactive state, wherein AIoT information is transmitted based on the established RRC connection.

[0165] In some examples, the AIoT query component 630 is capable of, configured to perform, or is operable to support components for performing the following operations: receiving requests for querying AIoT devices based on an RRC idle state or an RRC inactive state, wherein the query is sent based on the request and the RRC connection is established based on the request.

[0166] In some examples, the request includes an RRC recovery message, and the AIoT information includes an RRC recovery complete message.

[0167] In some examples, RRC connections are further established based on the establishment reason associated with the AIoT data report, the recovery reason associated with the AIoT data report, or both.

[0168] In some examples, the operation status component 645 is capable of, configured to, or operable to support components for performing the following operations: operating according to the RRC connection status. In some examples, the AIoT data buffer component 655 is capable of, configured to, or operable to support components for performing the following operations: storing AIoT data in a data buffer. In some examples, the AIoT data buffer component 655 is capable of, configured to, or operable to support components for performing the following operations: sending a buffer status report corresponding to the data buffer based on the RRC connection status. In some examples, the AIoT resource configuration component 625 is capable of, configured to, or operable to support components for performing the following operations: receiving control signaling indicative of one or more resources based on the buffer status report, wherein AIoT information is sent via one or more resources.

[0169] In some examples, the operation state component 645 is capable of, configured to, or able to operate to support components for performing the following operations: operating according to the RRC connection state. In some examples, the random access component 660 is capable of, configured to, or able to operate to support components for performing the following operations: sending a random access message requesting one or more resources for AIoT data transmission based on the RRC connection state. In some examples, the AIoT resource configuration component 625 is capable of, configured to, or able to operate to support components for performing the following operations: receiving control signaling indicating one or more resources based on a RACH message, wherein AIoT information is transmitted via one or more resources.

[0170] In some examples, the AIoT information component 640 is capable of, configured to perform, or is operable to support components for performing the following operations: sending AIoT information indicating AIoT data to a core network entity based on received indications of AIoT data.

[0171] In some examples, the AIoT resource configuration component 625 is capable of, configured to perform, or is operable to support components for performing the following operations: receiving control signaling that configures a set of resources for AIoT data reading, wherein signaling that activates at least a subset of resources is based on the control signaling.

[0172] In some examples, control signaling configures the transmit power for a query, the periodicity associated with one or more query resources, the first time resource associated with one or more query resources, the first frequency resource associated with one or more query resources, the first beam information associated with one or more query resources, the first code information associated with one or more query resources, the second time resource associated with one or more response resources, the second frequency resource associated with one or more response resources, the second beam information associated with one or more response resources, the second code information associated with one or more response resources, the number of repetitions of a query associated with a query session, the timer associated with a query session, or any combination thereof.

[0173] In some examples, the AIoT resource configuration component 625 is capable of, configured to perform, or is operable to support components for performing the following operations: sending a request for resources for communication between the device and the AIoT device, wherein control signaling is received based on the request.

[0174] In some examples, the request is sent based on a first amount of AIoT data to be reported, a second number of AIoT devices detected at the device, or both.

[0175] In some examples, control signaling includes broadcast signaling, dedicated signaling for the device, or both.

[0176] In some examples, the set of resources used for communication between the device and the AIoT device is shared by a set of multiple devices used for AIoT data reading, shared by a set of multiple AIoT devices, dedicated to the device for AIoT data reading, dedicated to the AIoT device, shared with non-AIoT communication, dedicated to AIoT data reading, or any combination thereof.

[0177] In some examples, in order to support the communication of signaling that activates at least a subset of resources, the AIoT resource configuration component 625 is capable of, configured to perform, or is operable to support components for performing the following operations: receiving RRC signaling, MAC-CE signaling, DCI signaling, paging signaling, or any combination thereof that activates at least a subset of resources.

[0178] In some examples, the AIoT resource configuration component 625 is capable of, configured to perform, or is operable to support components for performing the following operations: sending an indication of one or more preferred resources in a set of resources for communication between the device and the AIoT device, wherein the activated subset of resources is based on the indicated one or more preferred resources.

[0179] Figure 7 A diagram is shown of a system 700 including device 705 supporting resource management for communication with AIoT devices, according to one or more aspects of this disclosure. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or may include components thereof. Device 705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, at least one memory 730, code 735, and at least one processor 740. 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 745).

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

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

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

[0183] At least one processor 740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, GPUs, NPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., functions or tasks supporting resource management for communication with AIoT devices). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, wherein at least one processor 740 and at least one memory 730 are configured to perform the various functions described herein. In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 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 740 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 740) and memory circuitry (which may include at least one memory 730)) 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 740 or a processing system including at least one processor 740 may be configured, capable of being configured, or operable to cause device 705 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 730 or otherwise.

[0184] According to the examples disclosed herein, the communication manager 720 may support wireless communication. For example, the communication manager 720 is capable of, configured to, or operable to support components for performing the following operations: transmitting signaling for activating at least a subset of resources in a resource set for communication between the device and the AIoT device, the resource set including one or more query resources and one or more response resources. The communication manager 720 is capable of, configured to, or operable to support components for performing the following operations: sending a query for AIoT data to the AIoT device via a query resource in the activated resource subset. The communication manager 720 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication of AIoT data from the AIoT device in response to the query and via a response resource in the activated resource subset.

[0185] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support techniques for improved communication reliability and improved inter-device coordination. For example, a reader (e.g., UE 115) implementing the techniques described herein can communicate with AIoT devices via resources configured for the purpose of communicating with AIoT devices, which can increase communication reliability and reduce communication errors. Therefore, the techniques described herein can provide more efficient utilization of communication resources (e.g., due to reduced interference and communication errors) and more efficient coordination between readers, AIoT devices, and other devices in the wireless communication system.

[0186] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 715, one or more antennas 725, or any combination thereof, or otherwise cooperating with them. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or executed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause device 705 to perform various aspects of resource management for communication with AIoT devices as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0187] Figure 8A block diagram 800 of a device 805 supporting resource management for communication with AIoT devices according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of network entity 105 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that 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).

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

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

[0190] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of resource management for communication with AIoT devices as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

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

[0192] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in software executed by at least one processor (e.g., executed by the processor). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, GPU, NPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

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

[0194] According to the examples disclosed herein, the communication manager 820 may support wireless communication. For example, the communication manager 820 may be capable of, configured to, or operable to support components for performing the following operations: conveying signaling for activating at least a subset of resources in a resource set for communication between the device and the AIoT device, the resource set including one or more query resources and one or more response resources. The communication manager 820 may be capable of, configured to, or operable to support components for performing the following operations: sending a query for AIoT data to the AIoT device via a query resource in the activated resource subset. The communication manager 820 may be capable of, configured to, or operable to support components for performing the following operations: receiving an indication of AIoT data from the AIoT device in response to the query and via a response resource in the activated resource subset.

[0195] Additionally or alternatively, the communication manager 820 may support wireless communication according to the examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for performing the following operations: sending a first signaling configuration of a resource set for communication between a device and an AIoT device, the resource set including one or more query resources and one or more response resources. The communication manager 820 may be capable of, configured to, or operable to support components for performing the following operations: sending a second signaling for activating at least a subset of resources in the resource set for the device. The communication manager 820 may be capable of, configured to, or operable to support components for performing the following operations: receiving AIoT information indicating AIoT data associated with an AIoT device based on activating at least a subset of resources for the device.

[0196] By including or configuring a communication manager 820 according to examples as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for more efficient utilization of communication resources. For example, network entity 105 implementing the techniques described herein can communicate with AIoT devices or readers separately via resources configured for the purpose of communicating with AIoT devices or readers, which can increase the reliability of communication and reduce communication errors. Therefore, the techniques described herein can provide more efficient utilization of communication resources (e.g., due to reduced interference and communication errors).

[0197] Figure 9A block diagram 900 of a device 905 supporting resource management for communication with AIoT devices according to one or more aspects of this disclosure is shown. Device 905 may be an example of aspects of device 805 or network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0200] Device 905 or its various components may be examples of parts for performing various aspects of resource management for communication with AIoT devices as described herein. For example, communication manager 920 may include AIoT resource configuration component 925, AIoT query component 930, AIoT response component 935, AIoT information component 940, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or integrate in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0201] According to the examples disclosed herein, the communication manager 920 may support wireless communication. The AIoT resource configuration component 925 is capable of, configured to, or operable to support components for performing the following operations: transmitting signaling for activating at least a subset of resources in a resource set for communication between the device and the AIoT device, the resource set including one or more query resources and one or more response resources. The AIoT query component 930 is capable of, configured to, or operable to support components for performing the following operations: sending a query for AIoT data to the AIoT device via a query resource in the activated resource subset. The AIoT response component 935 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication of AIoT data from the AIoT device in response to the query and via a response resource in the activated resource subset.

[0202] Additionally or alternatively, the communication manager 920 may support wireless communication according to the examples disclosed herein. The AIoT resource configuration component 925 is capable of, configured to, or operable to support components for performing the following operations: sending a first signaling for configuring a resource set for communication between a device and an AIoT device, the resource set including one or more query resources and one or more response resources. The AIoT resource configuration component 925 is capable of, configured to, or operable to support components for performing the following operations: sending a second signaling for activating at least a subset of resources in the resource set for the device. The AIoT information component 940 is capable of, configured to, or operable to support components for performing the following operations: receiving AIoT information indicating AIoT data associated with an AIoT device based on activating at least a subset of resources for the device.

[0203] Figure 10 A block diagram 1000 is shown of a communication manager 1020 supporting resource management for communication with AIoT devices according to one or more aspects of this disclosure. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of parts for performing various aspects of resource management for communication with AIoT devices as described herein. For example, the communication manager 1020 may include an AIoT resource configuration component 1025, an AIoT query component 1030, an AIoT response component 1035, an AIoT information component 1040, an operation status component 1045, an RRC connection component 1050, an AIoT data buffer component 1055, a random access component 1060, or any combination thereof. These components, or each of their 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), and such communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0204] According to the examples disclosed herein, the communication manager 1020 may support wireless communication. The AIoT resource configuration component 1025 is capable of, configured to, or operable to support components for performing the following operations: transmitting signaling for activating at least a subset of resources in a resource set for communication between the device and the AIoT device, the resource set including one or more query resources and one or more response resources. The AIoT query component 1030 is capable of, configured to, or operable to support components for performing the following operations: sending a query for AIoT data to the AIoT device via a query resource in the activated resource subset. The AIoT response component 1035 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication of AIoT data from the AIoT device in response to the query and via a response resource in the activated resource subset.

[0205] In some examples, the AIoT information component 1040 is capable of, configured to perform, or is operable to support components for performing the following operations: sending AIoT information indicating AIoT data to network entities based on received indications of AIoT data.

[0206] In some examples, the AIoT resource configuration component 1025 is capable of, configured to perform, or is operable to support components for performing the following operations: receiving control signaling indicating a second set of resources associated with a dedicated radio bearer for AIoT data, wherein the AIoT information is transmitted via one or more resources in the second set of resources.

[0207] In some examples, the dedicated radio bearer includes SRB, DRB, or both.

[0208] In some examples, in order to support the transmission of AIoT information indicating AIoT data, the AIoT information component 1040 is capable of, configured to perform, or is operable to support components for performing the following operations: transmitting AIoT information via a dedicated PDU session associated with the AIoT service flow.

[0209] In some examples, the operation state component 1045 is capable of, configured to perform, or is operable to support components for performing the following operations: operating according to an RRC idle state or an RRC inactive state, wherein AIoT information is transmitted via a small data transmission scheme based on operating according to an RRC idle state or an RRC inactive state.

[0210] In some examples, AIoT information is sent based on one or more configured time resources, one or more configured frequency resources, uplink timing periodicity, MCS, synchronization signal blocks, AIoT data size meeting a threshold size, or any combination thereof.

[0211] In some examples, the operation state component 1045 is capable of, configured to, or operable to support components for performing the following operations: operating according to an RRC idle state or an RRC inactive state. In some examples, the RRC connection component 1050 is capable of, configured to, or operable to support components for performing the following operations: establishing an RRC connection based on AIoT data and operating according to an RRC idle state or an RRC inactive state, wherein AIoT information is transmitted based on the established RRC connection.

[0212] In some examples, the AIoT query component 1030 is capable of, configured to perform, or is operable to support components for performing the following operations: receiving requests for querying AIoT devices based on an RRC idle state or an RRC inactive state, wherein the query is sent based on the request and the RRC connection is established based on the request.

[0213] In some examples, the request includes an RRC recovery message, and the AIoT information includes an RRC recovery complete message.

[0214] In some examples, RRC connections are further established based on the establishment reason associated with the AIoT data report, the recovery reason associated with the AIoT data report, or both.

[0215] In some examples, the operation status component 1045 is capable of, configured to, or operable to support components for performing the following operations: operating according to the RRC connection status. In some examples, the AIoT data buffer component 1055 is capable of, configured to, or operable to support components for performing the following operations: storing AIoT data in a data buffer. In some examples, the AIoT data buffer component 1055 is capable of, configured to, or operable to support components for performing the following operations: sending a buffer status report corresponding to the data buffer based on the RRC connection status. In some examples, the AIoT resource configuration component 1025 is capable of, configured to, or operable to support components for performing the following operations: receiving control signaling indicative of one or more resources based on the buffer status report, wherein AIoT information is sent via one or more resources.

[0216] In some examples, the operation state component 1045 is capable of, configured to, or able to operate to support components for performing the following operations: operating according to the RRC connection state. In some examples, the random access component 1060 is capable of, configured to, or able to operate to support components for performing the following operations: sending a random access message requesting one or more resources for AIoT data transmission based on the RRC connection state. In some examples, the AIoT resource configuration component 1025 is capable of, configured to, or able to operate to support components for performing the following operations: receiving control signaling indicating one or more resources based on a RACH message, wherein AIoT information is transmitted via one or more resources.

[0217] In some examples, the AIoT information component 1040 is capable of, configured to perform, or is operable to support components for performing the following operations: sending AIoT information indicating AIoT data to a core network entity based on received indications of AIoT data.

[0218] In some examples, the AIoT resource configuration component 1025 is capable of, configured to perform, or is operable to support components for performing the following operations: receiving control signaling that configures a set of resources for AIoT data reading, wherein signaling that activates at least a subset of resources is based on the control signaling.

[0219] In some examples, control signaling configures the transmit power for a query, the periodicity associated with one or more query resources, the first time resource associated with one or more query resources, the first frequency resource associated with one or more query resources, the first beam information associated with one or more query resources, the first code information associated with one or more query resources, the second time resource associated with one or more response resources, the second frequency resource associated with one or more response resources, the second beam information associated with one or more response resources, the second code information associated with one or more response resources, the number of repetitions of a query associated with a query session, the timer associated with a query session, or any combination thereof.

[0220] In some examples, the AIoT resource configuration component 1025 is capable of, configured to perform, or is operable to support components for performing the following operations: sending a request for resources for communication between the device and the AIoT device, wherein control signaling is received based on the request.

[0221] In some examples, the request is sent based on a first amount of AIoT data to be reported, a second number of AIoT devices detected at the device, or both.

[0222] In some examples, control signaling includes broadcast signaling, dedicated signaling for the device, or both.

[0223] In some examples, the set of resources used for communication between the device and the AIoT device is shared by a set of multiple devices used for AIoT data reading, shared by a set of multiple AIoT devices, dedicated to the device for AIoT data reading, dedicated to the AIoT device, shared with non-AIoT communication, dedicated to AIoT data reading, or any combination thereof.

[0224] In some examples, in order to support the communication of signaling that activates at least a subset of resources, the AIoT resource configuration component 1025 is capable of, configured to perform, or is operable to support components for performing the following operations: receiving RRC signaling, MAC-CE signaling, DCI signaling, paging signaling, or any combination thereof that activates at least a subset of resources.

[0225] In some examples, the AIoT resource configuration component 1025 is capable of, configured to perform, or is operable to support components for performing the following operations: sending an indication of one or more preferred resources in a set of resources for communication between the device and the AIoT device, wherein the activated subset of resources is based on the indicated one or more preferred resources.

[0226] Additionally or alternatively, the communication manager 1020 may support wireless communication according to examples disclosed herein. In some examples, the AIoT resource configuration component 1025 is capable of, configured to, or operable to support components for performing the following operations: sending a first signaling for configuring a resource set for communication between a device and an AIoT device, the resource set including one or more query resources and one or more response resources. In some examples, the AIoT resource configuration component 1025 is capable of, configured to, or operable to support components for performing the following operations: sending a second signaling for activating at least a subset of resources in the resource set for the device. The AIoT information component 1040 is capable of, configured to, or operable to support components for performing the following operations: receiving AIoT information indicating AIoT data associated with an AIoT device based on activating at least a subset of resources for the device.

[0227] In some examples, the AIoT resource configuration component 1025 is capable of, configured to perform, or is operable to support components for performing: receiving requests for resources for communication between the device and the AIoT device, wherein a first signaling indicating a set of resources is sent, a second signaling activating at least a subset of resources is sent, or both are based on the request.

[0228] In some examples, the AIoT resource configuration component 1025 is capable of, configured to perform, or is operable to support components for performing the following operations: receiving an indication of one or more preferred resources in a set of resources for communication between the device and the AIoT device, wherein the activated subset of resources is based on the indicated one or more preferred resources.

[0229] In some examples, the AIoT resource configuration component 1025 is capable of, configured to perform, or is operable to support components for performing the following operations: transmitting control signaling indicating a second set of resources associated with a dedicated radio bearer for receiving AIoT data, wherein AIoT information indicating the AIoT data is received via one or more resources in the second set of resources.

[0230] In some examples, the AIoT information component 1040 is capable of, configured to perform, or is operable to support components for performing the following operations: sending AIoT information indicating AIoT data to core network entities based on AIoT information indicating AIoT data.

[0231] Figure 11A diagram of a system 1100 including a device 1105 supporting resource management for communication with AIoT devices, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or network entity 105 as described herein, or may include components thereof. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1105 may include components supporting output and acquisition of communication, such as a communication manager 1120, a transceiver 1110, an antenna 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may communicate electronically or otherwise (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1140).

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

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

[0234] At least one processor 1135 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, GPUs, NPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1135 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into one or more processors in at least one processor 1135. At least one processor 1135 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1125) to cause device 1105 to perform various functions (e.g., functions or tasks supporting resource management for communication with AIoT devices). For example, device 1105 or components of device 1105 may include at least one processor 1135 and at least one memory 1125 coupled to one or more processors in at least one processor 1135, wherein at least one processor 1135 and at least one memory 1125 are configured to perform the various functions described herein. At least one processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1130) to perform the functions of device 1105. At least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1105 (such as within one or more memories of at least one memory 1125). In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1135 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1135) and memory circuitry (which may include at least one memory 1125)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1135 or a processing system including at least one processor 1135 may be configured, configured to, or operated to cause the device 1105 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and 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 1125 or otherwise.

[0235] In some examples, bus 1140 may support communication at protocol layers (e.g., within a protocol layer) in a protocol stack. In some examples, bus 1140 may support communication associated with logical channels of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1105, or communication performed between different components of device 1105 that are co-addressable or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, at least one memory 1125, code 1130 and at least one processor 1135 may be located in one component of different components or partitioned between different components).

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

[0237] According to the examples disclosed herein, the communication manager 1120 may support wireless communication. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for performing the following operations: transmitting signaling for activating at least a subset of resources in a resource set for communication between the device and the AIoT device, the resource set including one or more query resources and one or more response resources. The communication manager 1120 may be capable of, configured to, or operable to support components for performing the following operations: sending a query for AIoT data to the AIoT device via a query resource in the activated resource subset. The communication manager 1120 may be capable of, configured to, or operable to support components for performing the following operations: receiving an indication of AIoT data from the AIoT device in response to the query and via a response resource in the activated resource subset.

[0238] Additionally or alternatively, the communication manager 1120 may support wireless communication according to the examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for performing the following operations: sending a first signaling configuration of a resource set for communication between a device and an AIoT device, the resource set including one or more query resources and one or more response resources. The communication manager 1120 may be capable of, configured to, or operable to support components for performing the following operations: sending a second signaling for activating at least a subset of resources in the resource set for the device. The communication manager 1120 may be capable of, configured to, or operable to support components for performing the following operations: receiving AIoT information indicating AIoT data associated with an AIoT device based on activating at least a subset of resources for the device.

[0239] By including or configuring a communication manager 1120 according to the examples described herein, device 1105 can support techniques for improved communication reliability and improved inter-device coordination. For example, network entity 105 implementing the techniques described herein can communicate with AIoT devices or readers separately via resources configured for the purpose of communicating with AIoT devices or readers, which can increase communication reliability and reduce communication errors. Therefore, the techniques described herein can provide more efficient use of communication resources (e.g., due to reduced interference and communication errors) and more efficient coordination among any combination of these or other devices in network entities, readers, AIoT devices, or wireless communication systems.

[0240] In some examples, the communication manager 1120 may be configured to use or otherwise cooperate with transceiver 1110, one or more antennas 1115 (e.g., where applicable) or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by transceiver 1110, one or more processors in at least one processor 1135, one or more memories in at least one memory 1125, code 1130, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1135, at least one memory 1125, code 1130, or any combination thereof). For example, code 1130 may include instructions that can be executed by one or more of at least one processor 1135 to cause device 1105 to perform various aspects of resource management for communication with AIoT devices as described herein, or at least one processor 1135 and at least one memory 1125 may be otherwise configured to perform or support such operations individually or jointly.

[0241] Figure 12 A flowchart illustrating a method 1200 for resource management supporting communication with an AIoT device, according to various aspects of this disclosure, is shown. Operation of method 1200 may be implemented by a UE or network entity or its components as described herein. For example, operation of method 1200 may be implemented by, as referenced... Figures 1 to 7 The UE 115 described or as referenced Figure 1 and Figure 2 as well as Figures 8 to 11 The described network entity 105 performs the function. In some examples, the UE or network entity may execute a set of instructions to control the functional elements of the UE or network entity to perform the described function. Additionally or alternatively, the UE or network entity may use dedicated hardware to perform aspects of the described function.

[0242] At 1205, the method may include: conveying signaling for activating at least a subset of resources in a resource set for communication between the device and the AIoT device, the resource set including one or more query resources and one or more response resources. The operation of block 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1205 may be provided by reference to [reference needed]. Figure 6 and Figure 10 The described AIoT resource configuration component 625 or AIoT resource configuration component 1025 is executed.

[0243] At 1210, the method may include: sending a query for AIoT data to the AIoT device via a query resource in the activated subset of resources. The operation of block 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1210 may be provided by reference to [reference needed]. Figure 6 and Figure 10 The described AIoT query component 630 or AIoT query component 1030 is executed.

[0244] At 1215, the method may include: receiving an indication of AIoT data from an AIoT device in response to a query and via a response resource in the activated subset of resources. The operation of block 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1215 may be provided by reference to [reference needed]. Figure 6 and Figure 10 The described AIoT response component 635 or AIoT response component 1035 performs this action.

[0245] Figure 13 A flowchart illustrating a method 1300 for resource management supporting communication with an AIoT device, according to various aspects of this disclosure, is shown. Operation of method 1300 may be implemented by a UE or network entity or its components as described herein. For example, operation of method 1300 may be implemented by, as referenced... Figures 1 to 7 The UE 115 described or as referenced Figure 1 and Figure 2 as well as Figures 8 to 11 The described network entity 105 performs the function. In some examples, the UE or network entity may execute a set of instructions to control the functional elements of the UE or network entity to perform the described function. Additionally or alternatively, the UE or network entity may use dedicated hardware to perform aspects of the described function.

[0246] At 1305, the method may include: receiving control signaling configuring a set of resources for AIoT data reading. The operation of block 1305 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1305 may be provided by reference to [reference needed]. Figure 6 and Figure 10 The described AIoT resource configuration component 625 or AIoT resource configuration component 1025 is executed.

[0247] At 1310, the method may include: conveying signaling for activating at least a subset of resources in a resource set for communication between the device and the AIoT device, the resource set including one or more query resources and one or more response resources, wherein the signaling for activating at least the resource subset is based at least in part on control signaling. 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]. Figure 6 and Figure 10 The described AIoT resource configuration component 625 or AIoT resource configuration component 1025 is executed.

[0248] At 1315, the method may include: sending a query for AIoT data to the AIoT device via a query resource in the activated subset of resources. 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 6 and Figure 10 The described AIoT query component 630 or AIoT query component 1030 is executed.

[0249] At 1320, the method may include: receiving an indication of AIoT data from an AIoT device in response to a query and via a response resource in the activated subset of resources. 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 6 and Figure 10 The described AIoT response component 635 or AIoT response component 1035 performs this action.

[0250] Figure 14 A flowchart illustrating a method 1400 for resource management supporting communication with an AIoT device, according to various aspects of this disclosure, is shown. Operation of method 1400 may be implemented by a network entity or its components as described herein. For example, operation of method 1400 may be implemented by, as referenced... Figure 1 and Figure 2 as well as Figures 8 to 11 The described network entity 105 is executed. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0251] At 1405, the method may include: sending first signaling configuring a set of resources for communication between the device and the AIoT device, the set of resources including one or more query resources and one or more response resources. The operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference needed]. Figure 10 The described AIoT resource configuration component 1025 is executed.

[0252] At 1410, the method may include: sending a second signaling for activating at least a subset of resources in the resource set for the device. The operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference needed]. Figure 10The described AIoT resource configuration component 1025 is executed.

[0253] At 1415, the method may include: receiving AIoT information indicating AIoT data associated with an AIoT device, based at least in part on activating at least a subset of resources for the device. 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 derived from references... Figure 10 The described AIoT information component 1040 is executed.

[0254] Figure 15 A flowchart illustrating a method 1500 for resource management supporting communication with an AIoT device, according to various aspects of this disclosure, is shown. The operation of method 1500 may be implemented by a network entity or its components as described herein. For example, the operation of method 1500 may be implemented by, as referenced... Figure 1 and Figure 2 as well as Figures 8 to 11 The described network entity 105 is executed. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0255] At 1505, the method may include: receiving a request for resources for communication between the device and the AIoT device. The operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 10 The described AIoT resource configuration component 1025 is executed.

[0256] At 1510, the method may include: sending first signaling configuring a set of resources for communication between the device and the AIoT device, the set of resources including one or more query resources and one or more response resources. The operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to [reference needed]. Figure 10 The described AIoT resource configuration component 1025 is executed.

[0257] At 1515, the method may include: sending a second signaling for activating at least a subset of resources in the resource set for the device, wherein sending a first signaling indicating the resource set, sending a second signaling to activate at least a subset of resources, or both are at least partially based on the request. 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 10 The described AIoT resource configuration component 1025 is executed.

[0258] At 1520, the method may include: receiving AIoT information indicating AIoT data associated with an AIoT device, based at least in part on activating at least a subset of resources for the device. The operation of block 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1520 may be derived from references... Figure 10 The described AIoT information component 1040 is executed.

[0259] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a device, the method comprising: conveying signaling for activating at least a subset of resources in a resource set for communication between the device and an AIoT device, the resource set including one or more query resources and one or more response resources; sending a query for AIoT data to the AIoT device via the query resources in the activated resource subset; and receiving an indication of the AIoT data from the AIoT device in response to the query and via the response resources in the activated resource subset.

[0260] Aspect 2: According to the method of aspect 1, the method further includes: sending AIoT information indicating the AIoT data to a network entity based at least in part on an indication received of the AIoT data.

[0261] Aspect 3: According to the method of aspect 2, the method further includes: receiving control signaling indicating a second set of resources associated with a dedicated radio bearer for the AIoT data, wherein the AIoT information is transmitted via one or more resources in the second set of resources.

[0262] Aspect 4: According to the method of aspect 3, the dedicated radio bearer includes SRB, DRB, or both.

[0263] Aspect 5: The method according to any one of Aspects 3 to 4, wherein sending the AIoT information indicating the AIoT data includes: sending the AIoT information via a dedicated PDU session associated with the AIoT service flow.

[0264] Aspect 6: The method according to any one of Aspects 2 to 5, the method further comprising: operating according to an RRC idle state or an RRC inactive state, wherein the AIoT information is transmitted via a small data transmission scheme based at least in part on operating according to the RRC idle state or the RRC inactive state.

[0265] Aspect 7: According to the method of aspect 6, the AIoT information is transmitted at least in part based on one or more configured time resources, one or more configured frequency resources, periodicity of uplink timing, MCS, SSB, the data size of the AIoT data meeting a threshold size, or any combination thereof.

[0266] Aspect 8: The method according to any one of Aspects 2 to 7, the method further comprising: operating according to an RRC idle state or an RRC inactive state; and establishing an RRC connection based at least in part on the AIoT data and operating according to the RRC idle state or the RRC inactive state, wherein the AIoT information is transmitted at least in part based on the established RRC connection.

[0267] Aspect 9: The method according to aspect 8, the method further comprising: receiving a request to query the AIoT device based at least in part on operation based on the RRC idle state or the RRC inactive state, wherein the query is sent at least in part based on the request and the RRC connection is established at least in part based on the request.

[0268] Aspect 10: According to the method of aspect 9, wherein the request includes an RRC recovery message and the AIoT information includes an RRC recovery completion message.

[0269] Aspect 11: The method according to any one of Aspects 8 to 10, wherein the RRC connection is further established at least in part based on an establishment reason associated with the AIoT data report, a recovery reason associated with the AIoT data report, or both.

[0270] Aspect 12: The method according to any one of Aspects 2 to 11, the method further comprising: operating according to an RRC connection state; storing the AIoT data in a data buffer; transmitting a buffer status report corresponding to the data buffer based at least in part on operating according to the RRC connection state; and receiving control signaling instructing one or more resources based at least in part on the buffer status report, wherein the AIoT information is transmitted via the one or more resources.

[0271] Aspect 13: The method according to any one of Aspects 2 to 12, the method further comprising: operating according to an RRC connection state; sending a RACH message requesting one or more resources for AIoT data transmission based at least in part on operating according to the RRC connection state; and receiving control signaling instructing the one or more resources based at least in part on the random access message, wherein the AIoT information is transmitted via the one or more resources.

[0272] Aspect 14: The method according to any one of Aspects 1 to 13, the method further comprising: sending AIoT information indicating the AIoT data to a core network entity based at least in part on an indication received of the AIoT data.

[0273] Aspect 15: The method according to any one of Aspects 1 to 14, the method further comprising: receiving control signaling that configures the resource set for AIoT data reading, wherein the signaling that activates at least a subset of the resources is at least partially based on the control signaling.

[0274] Aspect 16: The method according to aspect 15, wherein the control signaling configures the transmit power of the query, the periodicity associated with the one or more query resources, the first time resource associated with the one or more query resources, the first frequency resource associated with the one or more query resources, the first beam information associated with the one or more query resources, the first code information associated with the one or more query resources, the second time resource associated with the one or more response resources, the second frequency resource associated with the one or more response resources, the second beam information associated with the one or more response resources, the second code information associated with the one or more response resources, the number of repetitions of the query associated with the query session, the timer associated with the query session, or any combination thereof.

[0275] Aspect 17: The method according to any one of Aspects 15 to 16, the method further comprising: sending a request for resources for the communication between the device and the AIoT device, wherein receiving the control signaling is at least in part based on the request.

[0276] Aspect 18: According to the method of aspect 17, the request is sent at least in part based on a first amount of AIoT data to be reported, a second number of AIoT devices detected at the device, or both.

[0277] Aspect 19: The method according to any one of Aspects 15 to 18, wherein the control signaling includes broadcast signaling, dedicated signaling for the device, or both.

[0278] Aspect 20: The method according to any one of Aspects 1 to 19, wherein the resource set for communication between the device and the AIoT device is shared for multiple devices for AIoT data reading, shared for multiple AIoT devices, dedicated to the device for AIoT data reading, dedicated to the AIoT device, shared with non-AIoT communication, dedicated to the AIoT data reading, or any combination thereof.

[0279] Aspect 21: The method according to any one of Aspects 1 to 20, wherein conveying the signaling activating at least the subset of resources comprises: receiving RRC signaling, MAC-CE signaling, downlink control information signaling, paging signaling, or any combination thereof activating at least the subset of resources.

[0280] Aspect 22: The method according to any one of aspects 1 to 21, the method further comprising: sending an indication of one or more preferred resources in the resource set for communication between the device and the AIoT device, wherein the activated subset of resources is based at least in part on the indicated one or more preferred resources.

[0281] Aspect 23: A method for wireless communication at a network entity, the method comprising: transmitting a first signaling for configuring a resource set for communication between a device and an AIoT device, the resource set including one or more query resources and one or more response resources; transmitting a second signaling for activating at least a subset of resources in the resource set for the device; and receiving AIoT information indicating AIoT data associated with the AIoT device based at least in part on activating at least the subset of resources for the device.

[0282] Aspect 24: The method according to aspect 23, the method further comprising: receiving a request for resources for the communication between the device and the AIoT device, wherein a first signaling indicating the set of resources is sent, a second signaling activating at least a subset of the resources is sent, or both are at least partially based on the request.

[0283] Aspect 25: The method according to any one of Aspects 23 to 24, the method further comprising: receiving an indication of one or more preferred resources in the resource set for communication between the device and the AIoT device, wherein the activated subset of resources is based at least in part on the indicated one or more preferred resources.

[0284] Aspect 26: The method according to any one of Aspects 23 to 25, the method further comprising: transmitting control signaling indicating a second set of resources associated with a dedicated radio bearer for receiving the AIoT data, wherein the AIoT information of the AIoT data is received via one or more resources in the second set of resources.

[0285] Aspect 27: The method according to any one of Aspects 23 to 26, the method further comprising: sending the AIoT information indicating the AIoT data to a core network entity, at least in part based on the AIoT information indicating the AIoT data.

[0286] Aspect 28: An apparatus for wireless communication, the apparatus comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories (e.g., operatively, communicatively, functionally, electronically, or electrically) and capable of operating individually or jointly to execute the code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the apparatus to perform a method according to any one of aspects 1 to 22.

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

[0288] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by at least one processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) to perform the method according to any one of aspects 1 to 22.

[0289] Aspect 31: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories (e.g., operatively, communicatively, functionally, electronically, or electrically) and capable of operating individually or jointly to execute the code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the network entity to perform a method according to any one of Aspects 23 to 27.

[0290] Aspect 32: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 23 to 27.

[0291] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by at least one processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) to perform the method according to any one of aspects 23 to 27.

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

[0293] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied 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, including future systems and radio technologies.

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

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

[0296] The functionality described herein can be implemented using hardware, software executed by a processor, or any combination thereof. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. When implemented using software executed by a processor, the functionality 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 functionality described herein can be implemented using software executed by a processor, firmware, hardwired, or any combination thereof. Features implementing the functionality can also be physically located in various locations, including various portions distributed such that the functionality is implemented in different physical locations.

[0297] 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, phase-change memory, compact 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 is 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.

[0298] As used herein (including in the claims), the word "or" in an enumeration of items (e.g., including enumerations of items ending with phrases such as "at least one of..." or "one or more of...") indicates an inclusive enumeration, such that an enumeration of at least one of, for example, A, B, or C means, for example, 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". As used herein, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items may be used alone, or any combination of two or more of the listed items may be used. For example, if a composition is described as containing components A, B and / or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B and C.

[0299] 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 those 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".

[0300] The terms “determine” or “identify” encompass a variety of actions, and therefore, “determine” or “identify” can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), or ascertainment. Furthermore, “determine” or “identify” can include receiving (such as receiving information or signaling, e.g., receiving information or signaling for determination, receiving information or signaling for identification) or accessing (such as accessing data in memory or accessing information). Additionally, “determine” or “identify” can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0301] 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 numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

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

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

Claims

1. A device for wireless communication, the 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 device to: Signaling is transmitted to activate at least a subset of resources in a resource set for communication between the device and the Ambient Internet of Things (AIoT) device, the resource set including one or more query resources and one or more response resources; A query for AIoT data is sent to the AIoT device via the query resources in the activated subset of resources; as well as In response to the query and via response resources in the activated subset of resources, an indication of the AIoT data is received from the AIoT device.

2. The device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: AIoT information instructing the AIoT data is sent to network entities, at least in part, based on the received instructions regarding the AIoT data.

3. The device of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: Receive control signaling indicating a second set of resources associated with a dedicated radio bearer for the AIoT data, wherein the AIoT information is transmitted via one or more resources in the second set of resources.

4. The device of claim 3, wherein the dedicated radio bearer includes a signaling radio bearer, a data radio bearer, or both.

5. The device of claim 3, wherein, in order to send the AIoT information indicating the AIoT data, the one or more processors are capable of operating individually or jointly to execute the code to cause the device to: The AIoT information is transmitted via a dedicated packet data unit session associated with the AIoT service flow.

6. The device of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: Operation is performed based on a radio resource control idle state or a radio resource control inactive state, wherein the AIoT information is transmitted via a small data transmission scheme based at least in part on operation based on the radio resource control idle state or the radio resource control inactive state.

7. The device of claim 6, wherein the AIoT information is transmitted at least in part based on one or more configured time resources, one or more configured frequency resources, periodicity of uplink timing, modulation and decoding scheme, synchronization signal block, data size of the AIoT data satisfying a threshold size, or any combination thereof.

8. The device of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: Operate according to the radio resource control idle state or the radio resource control inactive state; and A radio resource control connection is established based at least in part on the AIoT data and by operating according to the radio resource control idle state or the radio resource control inactive state, wherein the AIoT information is transmitted at least in part based on the established radio resource control connection.

9. The device of claim 8, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: The request to query the AIoT device is received at least in part based on operation according to the Radio Resource Control idle state or the Radio Resource Control inactive state, wherein the query is sent at least in part based on the request, and the Radio Resource Control connection is established at least in part based on the request.

10. The device of claim 9, wherein the request includes a radio resource control recovery message, and the AIoT information includes a radio resource control recovery complete message.

11. The device of claim 8, wherein the radio resource control connection is further established at least in part based on an establishment reason associated with the AIoT data report, a recovery reason associated with the AIoT data report, or both.

12. The device of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: Operate according to the radio resource control connection status; The AIoT data is stored in a data buffer; At least in part, based on operations performed according to the radio resource control connection state, a buffer status report corresponding to the data buffer is transmitted; and Control signaling instructing one or more resources is received, at least in part, based on the buffer status report, wherein the AIoT information is transmitted via the one or more resources.

13. The device of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: Operate according to the radio resource control connection status; At least in part, it is based on operating according to the radio resource control connection state to send random access messages requesting one or more resources for AIoT data transmission; and Control signaling instructing the one or more resources is received at least in part based on the random access message, wherein the AIoT information is transmitted via the one or more resources.

14. The device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: AIoT information instructing the AIoT data is sent to the core network entity, at least in part, based on the received instructions regarding the AIoT data.

15. The device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: Receive control signaling that configures the resource set for AIoT data reading, wherein the signaling that activates at least a subset of the resources is at least partially based on the control signaling.

16. The apparatus of claim 15, wherein the control signaling is configured for the transmit power of the query, the periodicity associated with the one or more query resources, the first time resource associated with the one or more query resources, the first frequency resource associated with the one or more query resources, the first beam information associated with the one or more query resources, the first code information associated with the one or more query resources, the second time resource associated with the one or more response resources, the second frequency resource associated with the one or more response resources, the second beam information associated with the one or more response resources, the second code information associated with the one or more response resources, the number of repetitions of the query associated with a query session, the timer associated with the query session, or any combination thereof.

17. The device of claim 15, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: Sending a request for resources for the communication between the device and the AIoT device, wherein receiving the control signaling is at least in part based on the request.

18. The device of claim 17, wherein the request is sent at least in part based on a first amount of AIoT data to be reported, a second number of AIoT devices detected at the device, or both.

19. The device of claim 15, wherein the control signaling includes broadcast signaling, dedicated signaling for the device, or both.

20. The device of claim 1, wherein the resource set for communication between the device and the AIoT device is shared by multiple devices for AIoT data reading, shared by multiple AIoT devices, dedicated to the device for AIoT data reading, dedicated to the AIoT device, shared with non-AIoT communication, dedicated to the AIoT data reading, or any combination thereof.

21. The device of claim 1, wherein, in order to convey the signaling activating at least the subset of resources, the one or more processors are capable of operating individually or jointly to execute the code to cause the device to: Receive radio resource control signaling, media access control control element signaling, downlink control information signaling, paging signaling, or any combination thereof that activates at least a subset of the resources.

22. The device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the device to: Sending an indication of one or more preferred resources from the resource set for communication between the device and the AIoT device, wherein the activated subset of resources is based at least in part on the indicated one or more preferred resources.

23. A network entity for wireless communication, the network entity 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 network entity: Send a first signaling message configuring a set of resources for communication between the device and the Ambient Internet of Things (AIoT) device, the set of resources including one or more query resources and one or more response resources; Send a second signaling message for activating at least a subset of resources in the resource set for the device; as well as The AIoT information, which indicates AIoT data associated with the AIoT device, is received at least in part based on activating at least the subset of resources for the device.

24. The network entity of claim 23, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: Receive a request for resources for the communication between the device and the AIoT device, wherein a first signaling instructing the set of resources is sent, a second signaling activating at least a subset of the resources is sent, or both are at least partially based on the request.

25. The network entity of claim 23, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: Receive an indication of one or more preferred resources from the resource set for communication between the device and the AIoT device, wherein the activated subset of resources is based at least in part on the indicated one or more preferred resources.

26. The network entity of claim 23, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: Send control signaling indicating a second set of resources associated with a dedicated radio bearer for receiving the AIoT data, wherein the AIoT information of the AIoT data is received via one or more resources in the second set of resources.

27. The network entity of claim 23, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: The AIoT information indicating the AIoT data is sent to the core network entity at least in part based on the AIoT information indicating the AIoT data.

28. A method for wireless communication at a device, the method comprising: Signaling is transmitted to activate at least a subset of resources in a resource set for communication between the device and the Ambient Internet of Things (AIoT) device, the resource set including one or more query resources and one or more response resources; A query for AIoT data is sent to the AIoT device via the query resources in the activated subset of resources; as well as In response to the query and via response resources in the activated subset of resources, an indication of the AIoT data is received from the AIoT device.

29. The method according to claim 28, further comprising: AIoT information instructing the AIoT data is sent to network entities, at least in part, based on the received instructions regarding the AIoT data.

30. A method for conducting wireless communication at a network entity, the method comprising: Send a first signaling message configuring a set of resources for communication between the device and the Ambient Internet of Things (AIoT) device, the set of resources including one or more query resources and one or more response resources; Send a second signaling message for activating at least a subset of resources in the resource set for the device; as well as The AIoT information, which indicates AIoT data associated with the AIoT device, is received at least in part based on activating at least the subset of resources for the device.

Images